SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Any news on when we would update to texlive 2020 ?
I submitted texlive 2020 this week to SBo and to Pat.
Unfortunately i already found an issue, e.g. xindy and probably other scripts dont't work.
Here is a fix:
Code:
--- texlive.SlackBuild.orig 2020-06-14 09:01:15.479673121 +0200
+++ texlive.SlackBuild 2020-06-14 15:18:35.713301071 +0200
@@ -161,8 +161,16 @@
chmod -R u+w,go-w,a+rX-st $PKG
# use symlinks/scripts from tlnet
-mv $PKG$TEXMFROOT/texmf-dist/linked_scripts/* $PKG/usr/bin
-rmdir $PKG$TEXMFROOT/texmf-dist/linked_scripts
+for link in $PKG$TEXMFROOT/texmf-dist/linked_scripts/* ;do \
+ if [ -e "$link" ]; then
+ ln -sf $TEXMFROOT/texmf-dist/linked_scripts/bin/${link##*/} $PKG/usr/bin/${link##*/}
+ else
+ mv $link $PKG/usr/bin/${link##*/}
+ fi
+done
+mkdir -p $PKG$TEXMFROOT/texmf-dist/bin
+mv $PKG$TEXMFROOT/texmf-dist/linked_scripts/* $PKG$TEXMFROOT/texmf-dist/bin
+mv $PKG$TEXMFROOT/texmf-dist/bin $PKG$TEXMFROOT/texmf-dist/linked_scripts
# set some paths
sed -i \
Last edited by franzen; 06-14-2020 at 08:21 AM.
Reason: fixed patch again, fixed dangling symlinks
Is this a good time to sync the lxc sysvinit scripts with the main sysvinit scripts? The lxc versions were release 2019/07/19. I'm running the 2019 lxc versions in my containers but the diffs with the 2020 main scripts continue to grow.
I submitted texlive 2020 this week to SBo and to Pat.
Unfortunately i already found an issue, e.g. xindy and probably other scripts dont't work.
Here is a fix:
Code:
--- texlive.SlackBuild.orig 2020-06-14 09:01:15.479673121 +0200
+++ texlive.SlackBuild 2020-06-14 15:18:35.713301071 +0200
@@ -161,8 +161,16 @@
chmod -R u+w,go-w,a+rX-st $PKG
# use symlinks/scripts from tlnet
-mv $PKG$TEXMFROOT/texmf-dist/linked_scripts/* $PKG/usr/bin
-rmdir $PKG$TEXMFROOT/texmf-dist/linked_scripts
+for link in $PKG$TEXMFROOT/texmf-dist/linked_scripts/* ;do \
+ if [ -e "$link" ]; then
+ ln -sf $TEXMFROOT/texmf-dist/linked_scripts/bin/${link##*/} $PKG/usr/bin/${link##*/}
+ else
+ mv $link $PKG/usr/bin/${link##*/}
+ fi
+done
+mkdir -p $PKG$TEXMFROOT/texmf-dist/bin
+mv $PKG$TEXMFROOT/texmf-dist/linked_scripts/* $PKG$TEXMFROOT/texmf-dist/bin
+mv $PKG$TEXMFROOT/texmf-dist/bin $PKG$TEXMFROOT/texmf-dist/linked_scripts
# set some paths
sed -i \
Thanks! Saw it on SBo and I hope it gets pushed to -current soon. Thanks for the fix too.
I have tried that. I'm still unable to build Pidgin 2.14.x using -current. 2.13.0 seems to build fine.
Are you using slackwares slackbuild or something else ? Seems to me that you are building manually.
I just tried it over here with same configure options as you stated and it failed the same way, but this has nothing to do with
slackware , except that it does not compile. The problem is in the pidgin code fill up a bug on pidgin.im .
Are you using slackwares slackbuild or something else ? Seems to me that you are building manually.
I just tried it over here with same configure options as you stated and it failed the same way, but this has nothing to do with slackware , except that it does not compile. The problem is in the pidgin code fill up a bug on pidgin.im .
I have tried building 2.14.x both using the SlackBuild-script from https://slackware.osuosl.org/slackwa...ce/xap/pidgin/ and manually and both compilations fail at the same point. Time to file a bug report with Pidgin.
Again, if you look at the thing closely, you will see that this is due to a nor properly declared structure in the pidgin code, so nothing do be done more here.
Again, if you look at the thing closely, you will see that this is due to a nor properly declared structure in the pidgin code, so nothing do be done more here.
I've been able to compile pidgin 2.14.1 now by enabling voice support. This requires farstream which is available on SBo.
so is clearly obsolete, as -current already has pam, and is far beyond kernel 4.14.
But it also says that the newer upower was waiting for Plasma5.
Quote:
newer upower and ConsoleKit2 have to wait for new KDE/Plasma
LQ locks down posts after a few weeks, preventing rworkman from making any edits to that post, but it does show that they had already looked at the newer upower and found that at the time, it would need to wait for Plasma5. Since Plasma5 is expected soon, it's likely to think that a upower upgrade will come with it.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
