LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 11-12-2018, 05:00 AM   #211
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,439

Rep: Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489

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

Quote:
Originally Posted by Gordie View Post
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 View Post
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.
 
2 members found this post helpful.
Old 11-12-2018, 05:22 AM   #212
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,439

Rep: Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489
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
 
1 members found this post helpful.
Old 11-12-2018, 05:47 AM   #213
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Ubuntu
Posts: 1,216
Blog Entries: 3

Rep: Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214
Quote:
Originally Posted by ruario View Post
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.
Attached Thumbnails
Click image for larger version

Name:	skype test.png
Views:	29
Size:	125.4 KB
ID:	28949  
 
1 members found this post helpful.
Old 11-12-2018, 06:01 AM   #214
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,439

Rep: Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489
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.
 
1 members found this post helpful.
Old 11-12-2018, 06:11 AM   #215
Lysander666
Senior Member
 
Registered: Apr 2017
Location: The Underearth
Distribution: Slackware, Ubuntu
Posts: 1,216
Blog Entries: 3

Rep: Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214Reputation: 1214
Quote:
Originally Posted by ruario View Post
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]?
 
Old 11-12-2018, 06:32 AM   #216
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,439

Rep: Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489
Quote:
Originally Posted by Lysander666 View Post
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.

Last edited by ruario; 11-12-2018 at 06:35 AM.
 
1 members found this post helpful.
Old 11-12-2018, 09:02 AM   #217
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,712

Rep: Reputation: Disabled
Quote:
Originally Posted by ruario View Post
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.
 
Old 11-12-2018, 09:15 AM   #218
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 2,439

Rep: Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489Reputation: 1489
Quote:
Originally Posted by Didier Spaier View Post
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.
 
2 members found this post helpful.
Old 11-18-2018, 06:16 AM   #219
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware64-current
Posts: 926

Rep: Reputation: 355Reputation: 355Reputation: 355Reputation: 355
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.

Last edited by chrisretusn; 11-21-2018 at 08:07 PM.
 
3 members found this post helpful.
Old 11-21-2018, 05:02 PM   #220
PROBLEMCHYLD
Member
 
Registered: Apr 2015
Posts: 689

Rep: Reputation: Disabled
@ ruario

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


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
unkown cause for systemd failure state - systemd-logind cannot start org.freedesktop.systemd1 after server reboot mario.p Linux - Server 5 07-30-2018 03:11 AM
[SOLVED] will slackware drop newer KDE versions or go systemd rob.rice Slackware 73 04-23-2017 02:03 PM
[SOLVED] How to compile latest sources using older gcc glibc versions and run them? nirvaanr Linux - Software 4 06-08-2016 10:32 AM
[SOLVED] removing previous older kernels "vmlinuz" when updates get newer versions james2b Linux - Newbie 7 09-12-2011 05:13 AM
how to use older versions of glibc turls Programming 4 07-07-2004 04:40 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 11:07 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration