[Slackbuilds-users] misc/po4a: is `su -' requirement only about kpsewhich?
In misc/po4a README it says: "WARNING: run po4a.SlackBuild as root (su -) not with only root privileges (su), otherwise test #24 will fail." I did some tests and it seems that it's enough to add /usr/share/texmf/bin/ directory to $PATH for test #24 to pass. The warning is here because in standard Slackware setup this directory which contains kpsewich is added to $PATH by /etc/profile.d/tetex.sh. I think that current warning is quite uninformative and it only hides the real reason why test #24 fails without `su -'. It could it be improved, for example: "WARNING: run po4a.SlackBuild as root (su -) not with only root privileges (su) to have /usr/share/texmf/bin/kpsewhich in $PATH, otherwise test #24 will fail." What do you think? -- Arkadiusz Drabczyk___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2
On 10/31/16, Eduardo Sanchezwrote: > The issue is that there's no mention at all in the ChangeLog: > > https://slackbuilds.org/ChangeLog.txt You make a good point. That ChangeLog only goes back to July 2, 2016, which is when Slack 14.2 was released. The removed packages were removed before that (mid-January 2016). > There is no metion of any git log on any part of the SlackBuild website. > > Any user looking to maintain its system would be at a loss. Also good points. In theory, every user reads every line of Slackware's ChangeLog, so they'd know that package XYZ got added to Slackware & therefore won't be on SBo any more. But that's like saying every user has the time/energy/skill to read the source code of all open source software they use (just plain not true). Also for these particular packages, they aren't mentioned in the Slack ChangeLog (they became part of the perl package, but none of the perl-* entries mention the modules by name). > The question is: where should I follow the SlackBuilds.org changes: at > the ChangeLog which is published and advertised at the website, or at > some git log whose mention is nowhere on the SlackBuilds.org page? I can't answer that (I speak only for myself, not the SBo team). However... The git log is actually there on the site, just not obvious. At https://slackbuilds.org/repository/14.2/ there are links at the bottom: Access to the repository is available via: ftp git cgit http rsync The git log can be found in your browser by clicking on the cgit link... or by using git to clone the URL in the git link. But the site documentation (FAQ and HOWTO) don't mention this. And, if a user's not familiar with git and/or cgit, he might have a hard time finding what he's looking for. For your missing packages, you could enter the package name in the search box on the main cgit page... if that helps any in the future. It'd be nice to add this info to the FAQ. ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Is building packages using fakeroot safe?
On 30/10/16 15:52, Jeremy Hansen wrote: David Spencer's (55020) slackrepo will automate building using overlay, ultimately keeping the build server completely clean (it starts with a clean install for every build project since it uses overlays and doesn't install the packages to the machine itself -- they're just installed to the overlay, so as soon as it's removed, you're back to a clean system) and setting up a slackpkg+ compatible repo. http://idlemoor.github.io/slackrepo/ It might be something you'd be interested in. Exactly what I was thinking of and maybe something of interest to SBo team: Built ok: wxPython-2.8.12.1-x86_64-2_sbo.txz 22:23:46 WARNING: libraries/wxPython: Files/directories were modified in the chroot /usr/lib64/python2.7/site-packages /usr/lib64/python2.7/site-packages/libxml2.pyc Built ok: youtube-dl-gui-0.3.8-x86_64-1_sbo.txz 22:24:12 WARNING: network/youtube-dl-gui: Files/directories were modified in the chroot /root/.config -- Best regards, Andrzej Telszewski ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2
About this message: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-October/017333.html > The git log has the reason. For all 4 modules: > > Removed (Included in Slackware's Perl). The issue is that there's no mention at all in the ChangeLog: https://slackbuilds.org/ChangeLog.txt There is no metion of any git log on any part of the SlackBuild website. Any user looking to maintain its system would be at a loss. The question is: where should I follow the SlackBuilds.org changes: at the ChangeLog which is published and advertised at the website, or at some git log whose mention is nowhere on the SlackBuilds.org page? Thanks, Eduardo -- Eduardo Sánchez Gauto, Abog., Th.M. Abogado - Traductor Público Matriculado Inglés - Español Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Teléfono: (0991) 755-355 - Asunción, Paraguay == ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2
On 10/31/16, Eduardo Sanchezwrote: > Now, these modules are *not* in the 14.2 repository, nor there is any > notice I can find of their removal. The git log has the reason. For all 4 modules: Removed (Included in Slackware's Perl). ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
Re: [Slackbuilds-users] ISSUE: texlive: problems downloading from tug.org
On 2016-10-30 01:33, Franzen wrote: If more people have issues with that download, i'll look for another solution. Tried from two different systems on different networks, both times: wget ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz --2016-10-29 14:20:21-- ftp://tug.org/historic/systems/texlive/2016/texlive-20160523b-source.tar.xz => 'texlive-20160523b-source.tar.xz' Resolving tug.org (tug.org)... 130.225.2.178 Connecting to tug.org (tug.org)|130.225.2.178|:21... connected. Logging in as anonymous ... Login incorrect. That's what i got from the texlive-mailinglist: Connecting to tug.org (tug.org)|130.225.2.178|:21... connected. Logging in as anonymous ... It is common for all the anon ftp slots on tug to get used up by stupid robots or whatever. Despite my limiting by IP address, etc. beside that there's also the rsync-able svn, In addition to the svn, the whole historic/ directory is available by rsync ... tug.org::historic/systems/texlive/2016/ On ctan there is http://mirrors.ctan.org/systems/texlive/Source/texlive-20160520- source.tar.xz, which is not same release tarball. Oops. I updated the directories on tug. I'm not sure if CTAN mirrors that directory continuously or only when I ask them to update. We'll see what happens in the next 24 hours or so ... --thanks, karl. So, there may be an alternative Download location soon on CTAN. It's now on CTAN :-) http://mirrors.ctan.org/systems/texlive/Source/texlive-20160523b-source.tar.xz I'll put this source in the .info-file on the next update. Johannes ___ SlackBuilds-users mailing list SlackBuilds-users@slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/