So, no more working Skype for Slackware 15? The older versions crash because the new GLIBC, the newer ones needs systemd-logind

ruario · 11-12-2018, 04:00 AM

And it would work on stable as well, if it weren't for this:

Quote:

Originally Posted by Gordie

Hmm, my computer is not looking for

Code:

/usr/share/skypeforlinux/resources/app.asar.unpacked/node_modules/slimcore/bin/sharing-indicator.nod

It is instead looking for

Code:

/usr/share/skypeforlinux/resources/app.asar.unpacked/node_modules/slimcore/bin/sharing-indicator.node

so right or wrong I did

Code:

ln -s /usr/share/skypeforlinux/resources/app.asar.unpacked/node_modules/slimcore/bin/sharing-indicator.nod /usr/share/skypeforlinux/resources/app.asar.unpacked/node_modules/slimcore/bin/sharing-indicator.node

Quote:

Originally Posted by Alien Bob

Looks you ran into a tar bug that has plagued me a lot when developing liveslak: the path "usr/share/skypeforlinux/resources/app.asar.unpacked/node_modules/slimcore/bin/sharing-indicator.node" is exactly 100 characters and it seems that the tar in Slackware 14.2 truncates the last character, only in this particular situation of 100-character filenames.
The tar in -current does not have this bug, which is why I have to generate my Live ISO images on -current.

My own 14.2 pkgtools have a number of patches, so I don't hit this issue. It is only when I installed in a VM and investigated that I saw the issue that chrisretusn and Lysander666. The mock trick is not the issue here.

ruario · 11-12-2018, 04:22 AM

Ok, I have added a workaround to my script (latest-skype.sh Version 1.1.1). I rename “usr/share/skypeforlinux” to “usr/share/skype” before packaging, to shorten the path length. It should work for you now. It does for me in a clean Slackware64 14.2 VM

Lysander666 · 11-12-2018, 04:47 AM

Quote:

Originally Posted by ruario

Ok, I have added a workaround to my script (latest-skype.sh Version 1.1.1). I rename “usr/share/skypeforlinux” to “usr/share/skype” before packaging, to shorten the path length. It should work for you now. It does for me in a clean Slackware64 14.2 VM

Great work, ruario. Skype 8.33 appears to be working now in stable. Zo likes you too.

ruario · 11-12-2018, 05:01 AM

I tested the SlackBuild from SBo and realised it did not have this issue, which massively confused me. I have since discovered that this is because the package is created and extracted by tar 1.13. The problem with my script is that I bypass makepkg for creation (so that I can create a package as a regular user) and in doing so I was using a newer tar for creation but of course, installation/extraction by installpkg was happening with 1.13. So I tweaked my script again to use tar 1.13 for creation as well (if it is available). This should be much safer and I should likely update all my other scripts that work in this way to do the same.

Lysander666 · 11-12-2018, 05:11 AM

Quote:

Originally Posted by ruario

I tested the SlackBuild from SBo and realised it did not have this issue, which massively confused me. I have since discovered that this is because the package is created and extracted by tar 1.13. The problem with my script is that I bypass makepkg for creation (so that I can create a package as a regular user) and in doing so I was using a newer tar for creation but of course, installation/extraction by installpkg was happening with 1.13. So I tweaked my script again to use tar 1.13 for creation as well (if it is available). This should be much safer and I should likely update all my other scripts that work in this way to do the same.

I see, you've updated the script again. OK, so this is the version to use for now [1.1.2]?

ruario · 11-12-2018, 05:32 AM

Quote:

Originally Posted by Lysander666

I see, you've updated the script again. OK, so this is the version to use for now [1.1.2]?

Yeah, I would. As you may or may not be aware, all of my “latest-*” scripts bypass makepkg for package creation. While this “voids the warranty” (so to speak), I do this so that I can create root owned files within a package as a non-root user. And so far I have gotten away with it. Indeed, it seems a number of people are using my scripts and also encountered no issues with my little hack, but it looks like we just hit the first real problem.

Skype has a file with a path length of exactly 100 characters. If you use tar-1.13 for both creation and extraction (as the real Pkgtools from 14.2 would) this does not cause a problem. But I have been using a newer tar for creation and tar-1.13 (used by installpkg for extraction) does not handle this well, if a file has exactly that length (100 characters).

My first workaround (changing the path name to adjust the length) is imperfect. It could fail in the future because MS/Skype could decide to move or rename files and we might re-hit this issue if they end up at 100 characters in length after my path rename. So instead (from version 1.1.2 of the script), I just use tar 1.13 (if I find it), like makepkg. This should be more future proof.

Didier Spaier · 11-12-2018, 08:02 AM

Quote:

Originally Posted by ruario

Yeah, I would. As you may or may not be aware, all of my “latest-*” scripts bypass makepkg for package creation.

Why not use fakeroot? Several distributions based on Slackware use that since years without problem.

ruario · 11-12-2018, 08:15 AM

Quote:

Originally Posted by Didier Spaier

Why not use fakeroot? Several distributions based on Slackware use that since years without problem.

One less dependency and up until this point I have never had a problem. Plus this problem is now fixed.

chrisretusn · 11-18-2018, 05:16 AM

Well it's been several updates with Steam now, all is well. I went back any had a re-look at the logs in my backups, not sure how I missed it (blind perhaps), but there are a couple of lines that read:

Code:

BCommitUpdatedFiles: failed to rename ./linux64/crashhandler.so -> ./linux64/crashhandler.so.old (error 13)
BCommitUpdatedFiles: failed to process ./linux64
Failed to apply update, reverting...

I checked that file in the backups. Well wish I had done this earlier. The user name was 1004. What the heck? That would explain things. How this happened, how it got fixed (the user name is chris now) is beyond me.

I do know that Steam is working and updating with Skype up and running, so I am going to call this problem a fluke or perhaps self inflicted one. No one else has reported this. So I am of the opinion that the there is no conflict between the "skype-dbus-mock" fixed skypeforlinux and Steam.

PROBLEMCHYLD · 11-21-2018, 04:02 PM

@ ruario

Updated Skype with your script today and all is good. Thanks

Lysander666 · 04-24-2019, 04:22 PM

Just want to say that ruario's script still seems to be working well on -current. ruario has been rather quiet of late, only one post since January. Hope you're OK ruario, it seems that life is keeping you busy!

ruario · 04-25-2019, 03:33 AM

@Lysander666 Glad it is working for you.

Yeah I have been busy with work and other stuff. Also, in my spare time I have generally been writing on the other forums I frequent (about unicycling). I'll go through that Vivaldi thread you opened now and see if there is anything useful I can add.

Lysander666 · 04-25-2019, 03:45 AM

Quote:

Originally Posted by ruario

@Lysander666 Glad it is working for you.

Yeah I have been busy with work and other stuff. Also, in my spare time I have generally been writing on the other forums I frequent (about unicycling). I'll go through that Vivaldi thread you opened now and see if there is anything useful I can add.

I'm pleased that you're OK. It's interesting to hear of the other places people frequent online. I wish I had other music fora I could go to online, but I find most fora which support my taste in music to be quite pointless to visit. I end up mostly going to other places.