From chris.willing at iinet.net.au Tue Mar 1 13:59:26 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 1 Mar 2016 23:59:26 +1000 Subject: [Slackbuilds-users] Broken check Message-ID: <56D5A03E.6020402@iinet.net.au> The SlackBuild for development/check is pretty badly broken, for some reason using cmake when the README clearly instructs use of autotools. The result is a package missing several files - the checkmk executable, shared object files, man page, info page and a check.pc - all are missing. Changing the SlackBuild to use autotools as instructed results in a package containing all the intended files. Email to the listed maintainer bounced. If they see this email, please submit an updated SlackBuild using autotools so that the resulting package is usable. chris From willysr at slackbuilds.org Tue Mar 1 15:44:23 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 1 Mar 2016 22:44:23 +0700 Subject: [Slackbuilds-users] Broken check In-Reply-To: <56D5A03E.6020402@iinet.net.au> References: <56D5A03E.6020402@iinet.net.au> Message-ID: <56D5B8D7.10009@slackbuilds.org> > The SlackBuild for development/check is pretty badly broken, for some > reason using cmake when the README clearly instructs use of autotools. > The result is a package missing several files - the checkmk executable, > shared object files, man page, info page and a check.pc - all are > missing. Changing the SlackBuild to use autotools as instructed results > in a package containing all the intended files. > > Email to the listed maintainer bounced. If they see this email, please > submit an updated SlackBuild using autotools so that the resulting > package is usable. Hi I was the last one touched check and if i recall, there were a reason why i changed to cmake-based. if you can make it work with autotools, feel free to do so in your branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Tue Mar 1 22:12:59 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 2 Mar 2016 08:12:59 +1000 Subject: [Slackbuilds-users] Broken check In-Reply-To: <56D5B8D7.10009@slackbuilds.org> References: <56D5A03E.6020402@iinet.net.au> <56D5B8D7.10009@slackbuilds.org> Message-ID: <56D613EB.2090809@iinet.net.au> On 02/03/16 01:44, Willy Sudiarto Raharjo wrote: >> The SlackBuild for development/check is pretty badly broken, for some >> reason using cmake when the README clearly instructs use of autotools. >> The result is a package missing several files - the checkmk executable, >> shared object files, man page, info page and a check.pc - all are >> missing. Changing the SlackBuild to use autotools as instructed results >> in a package containing all the intended files. >> >> Email to the listed maintainer bounced. If they see this email, please >> submit an updated SlackBuild using autotools so that the resulting >> package is usable. > > Hi > > I was the last one touched check and if i recall, there were a reason > why i changed to cmake-based. > > if you can make it work with autotools, feel free to do so in your branch OK, I just pushed it. I think the problem you faced was that no configure script was supplied in the latest source tarball, so autoreconf now needs to be run first to generate it. chris From willysr at slackbuilds.org Wed Mar 2 19:42:21 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 Mar 2016 11:42:21 -0800 Subject: [Slackbuilds-users] Broken check In-Reply-To: <56D613EB.2090809@iinet.net.au> References: <56D5A03E.6020402@iinet.net.au> <56D5B8D7.10009@slackbuilds.org> <56D613EB.2090809@iinet.net.au> Message-ID: <56D7421D.7090800@slackbuilds.org> > OK, I just pushed it. > > I think the problem you faced was that no configure script was supplied > in the latest source tarball, so autoreconf now needs to be run first to > generate it. Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From titopoquito at gmail.com Sat Mar 5 16:13:09 2016 From: titopoquito at gmail.com (titopoquito) Date: Sat, 5 Mar 2016 17:13:09 +0100 Subject: [Slackbuilds-users] fbmenugen missing file, diff attached Message-ID: <56DB0595.8020401@gmail.com> Since submissions are closed anyway, I post the following here with a CC to the maintainer. The package fbmenugen is missing a file without which it is not functional. The file "schema.pl" is in the source tarball but does not get copied to "$PKG/etc/xdg/fbmenugen/" (from where it gets copied by the program to "~/.config/fbmenugen/schema.pl", depending on which user is starting the program. I would suggest to add the included LICENSE file, too. A diff file for fbmenugen.SlackBuild is attached. Cheers, Tito -------------- next part -------------- A non-text attachment was scrubbed... Name: fbmenugen.diff Type: text/x-patch Size: 499 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Mar 5 16:16:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Mar 2016 23:16:39 +0700 Subject: [Slackbuilds-users] fbmenugen missing file, diff attached In-Reply-To: <56DB0595.8020401@gmail.com> References: <56DB0595.8020401@gmail.com> Message-ID: <56DB0667.8060506@slackbuilds.org> > Since submissions are closed anyway, I post the following here with a CC > to the maintainer. > > The package fbmenugen is missing a file without which it is not > functional. The file "schema.pl" is in the source tarball but does not > get copied to "$PKG/etc/xdg/fbmenugen/" (from where it gets copied by > the program to "~/.config/fbmenugen/schema.pl", depending on which user > is starting the program. > I would suggest to add the included LICENSE file, too. > > A diff file for fbmenugen.SlackBuild is attached. applied to my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From thomas at beingboiled.info Sat Mar 5 21:59:30 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Sat, 5 Mar 2016 22:59:30 +0100 (CET) Subject: [Slackbuilds-users] Exim CVE-2016-1531 Message-ID: Dear Exim-users and SBo-admins, A new version of Exim has been released, fixing a vulnerability that allows a local privilege escalation. While the Exim from SBo doesn't include the vulnerable feature and thus *should* not be affected, the download link in the .info file needs editing and an upgrade to the current Exim 4.86.2 seems desirable. If you're still okay with Exim 4.86 you can find the archive at: ftp://ftp.exim.org/pub/exim/exim4/old/exim-4.86.tar.bz2 If you prefer to upgrade to Exim 4.86.2, simply replace exim.SlackBuild and exim.info with the attached files and build. Please note that the new version contains changes that might break your existing config. See... http://article.gmane.org/gmane.mail.exim.announce/168 ...for more information. -- -------------- next part -------------- #!/bin/sh # Slackware build script for Exim # Copyright 2012-2016 Thomas Morper, Augsburg, Germany # All rights reserved. # # Redistribution and use of this script, with or without modification, is # permitted provided that the following conditions are met: # # 1. Redistributions of this script must retain the above copyright # notice, this list of conditions and the following disclaimer. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=exim VERSION=${VERSION:-4.86.2} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) ARCH=i486 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac fi CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" else SLKCFLAGS="-O2" LIBDIRSUFFIX="" fi set -e # Check if the exim user and group exist. If not, then bail. if [ "$(id -g exim 2> /dev/null)" != "222" -o "$(id -u exim 2> /dev/null)" != "222" ]; then echo " You must have an 'exim' user and group to run this script." echo " # groupadd -g 222 exim" echo " # useradd -d /var/spool/exim -g exim -s /bin/false -u 222 exim" exit 1 fi rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$VERSION.tar.bz2 cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; # This is our custom config for an all-purpose Exim daemon. # The SQL- and LDAP-lookups will not be built by default, # but you can enable them easily by passing the directives # on the command line when calling this script, e.g. # # LOOKUP_LDAP=yes LOOKUP_SQLITE=yes \ # LOOKUP_MYSQL=yes LOOKUP_PGSQL=yes \ # sh exim.SlackBuild # cat $CWD/exim.Makefile > Local/Makefile # Use a stock config for the Exim Monitor (not built by default). cat exim_monitor/EDITME > Local/eximon.conf # Use the Exim build system to set the architecture-specific CFLAGS. # This requires "make" to run twice, in case you wonder. If you want # to use your own CFLAGS in exim.Makefile, you should put a '#' in # front of the next 3 lines. echo "CFLAGS=$SLKCFLAGS -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE" > Local/Makefile-Linux FULLECHO="" LIBDIRSUFFIX=$LIBDIRSUFFIX DESTDIR=$PKG make -e || true FULLECHO="" LIBDIRSUFFIX=$LIBDIRSUFFIX DESTDIR=$PKG make -e makefile # build & install FULLECHO="" LIBDIRSUFFIX=$LIBDIRSUFFIX DESTDIR=$PKG make -e FULLECHO="" LIBDIRSUFFIX=$LIBDIRSUFFIX DESTDIR=$PKG make -e install find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true # Rename the version specific binary to simply 'exim'. mv $PKG/usr/sbin/exim-$VERSION-* $PKG/usr/sbin/exim # Additional symlinks provide compatibility with sendmail mkdir -p $PKG/usr/lib # no LIBDIRSUFFIX here! ( cd $PKG/usr/lib; ln -s /usr/sbin/exim sendmail ) ( cd $PKG/usr/sbin; ln -s /usr/sbin/exim sendmail ) # Install accompanying scripts and configs. mkdir -p $PKG/etc/{cron.daily,logrotate.d,rc.d} install -m 0755 $CWD/contrib/rc.exim.new $PKG/etc/rc.d/rc.exim.new install -m 0755 $CWD/contrib/exim.cron $PKG/etc/cron.daily/exim.new install -m 0644 $CWD/contrib/exim.logrotate $PKG/etc/logrotate.d/exim.new # Prepare log- and spool-directories. mkdir -p $PKG/var/log/exim mkdir -p -m 0750 $PKG/var/spool/exim/ mkdir -p -m 0750 $PKG/var/spool/exim/{db,input,msglog} chown -R exim.exim $PKG/var/{log,spool}/exim mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a ABOUT ACKNOWLEDGMENTS CHANGES CONTRIBUTING LICENCE* NOTICE README* doc \ $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild # Don't use the default config - make it part of the documentation mv $PKG/etc/exim/exim.conf $PKG/usr/doc/$PRGNAM-$VERSION/example-exim.conf mv $PKG/etc/exim/aliases $PKG/usr/doc/$PRGNAM-$VERSION/example-aliases mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cat $CWD/doinst.sh > $PKG/install/doinst.sh cd $PKG /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} -------------- next part -------------- PRGNAM="exim" VERSION="4.86.2" HOMEPAGE="http://www.exim.org/" DOWNLOAD="ftp://ftp.exim.org/pub/exim/exim4/exim-4.86.2.tar.bz2" MD5SUM="1443a4a88d6b78ad9b6a681c51437b55" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="%README%" MAINTAINER="Thomas Morper" EMAIL="thomas at beingboiled.info" From willysr at slackbuilds.org Sun Mar 6 01:13:52 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Mar 2016 08:13:52 +0700 Subject: [Slackbuilds-users] Exim CVE-2016-1531 In-Reply-To: References: Message-ID: <56DB8450.5080601@slackbuilds.org> > A new version of Exim has been released, fixing a vulnerability that > allows a local privilege escalation. While the Exim from SBo doesn't > include the vulnerable feature and thus *should* not be affected, the > download link in the .info file needs editing and an upgrade to the > current Exim 4.86.2 seems desirable. > > If you're still okay with Exim 4.86 you can find the archive at: > > ftp://ftp.exim.org/pub/exim/exim4/old/exim-4.86.tar.bz2 > > If you prefer to upgrade to Exim 4.86.2, simply replace exim.SlackBuild > and exim.info with the attached files and build. Please note that the new > version contains changes that might break your existing config. See... > > http://article.gmane.org/gmane.mail.exim.announce/168 applied in my branch (updated to 4.86.2) Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From pessoal at profcavalheiro.com Sun Mar 6 16:14:57 2016 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Sun, 6 Mar 2016 13:14:57 -0300 Subject: [Slackbuilds-users] Package celt Message-ID: Dear slackbuilds.org admins and users Package celt, as provided on website, won't compile on a x86_64 system, so I made a patch to celt.SlackBuild file to solve this problem. -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ? V?W^ ??? $jY P#?????]??'p??|?????a?z???Lxs?_ ?x?????h+?zL?f???9?j`???|??<8"?????plc?]?g???\u????dE??b?Kk???MGs?%?a?M[?w\?}???Q?A??/=???L43XHp ?(Z? ~?a`~3?N??f???0????ZK ??E??X???? ??p??Es h `??(;?q??q?????????b??[y????t??R??Nu?*???=m?*g? 3o??=???@????<'s_?sF?)??%q??j??O%?jp??h?????G?z?????j?@^?J????tq?????????.?0? ?V?? From matteo.bernardini at gmail.com Sun Mar 6 16:25:09 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 6 Mar 2016 17:25:09 +0100 Subject: [Slackbuilds-users] Package celt In-Reply-To: References: Message-ID: 2016-03-06 17:14 GMT+01:00 Luis Cavalheiro : > Dear slackbuilds.org admins and users > > Package celt, as provided on website, won't compile on a x86_64 system, so I > made a patch to celt.SlackBuild file to solve this problem. hi Luis, celt builds fine here: are you by any chance using multilib? https://slackbuilds.org/faq/#multilib Matteo From pessoal at profcavalheiro.com Sun Mar 6 16:28:01 2016 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Sun, 6 Mar 2016 13:28:01 -0300 Subject: [Slackbuilds-users] Package celt In-Reply-To: References: Message-ID: Indeed I am, Matteo. Now you talked about it, I suppose that should explain why celt didn't compile without that patch I made. But since it uses LIBDIRSUFFIX to correctly set LDFLAGS, I believe it should be harmless even in a 32 bits system. 2016-03-06 13:25 GMT-03:00 Matteo Bernardini : > 2016-03-06 17:14 GMT+01:00 Luis Cavalheiro : > > Dear slackbuilds.org admins and users > > > > Package celt, as provided on website, won't compile on a x86_64 system, > so I > > made a patch to celt.SlackBuild file to solve this problem. > > hi Luis, > > celt builds fine here: are you by any chance using multilib? > > https://slackbuilds.org/faq/#multilib > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Cordialmente, Lu?s Fernando Carvalho Cavalheiro Curriculum Lattes: http://lattes.cnpq.br/3397855894525757 ResearcherID: http://www.researcherid.com/rid/J-1300-2014 ORCID: http://orcid.org/0000-0001-6097-4745 Google+: https://plus.google.com/u/0/+LuisFernandoCarvalhoCavalheiro/ Skype: mestre.cavalheiro -------------- next part -------------- An HTML attachment was scrubbed... URL: From pessoal at profcavalheiro.com Sun Mar 6 16:39:12 2016 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Sun, 6 Mar 2016 13:39:12 -0300 Subject: [Slackbuilds-users] Dead link on decklink-sdk.info Message-ID: Hello again. Download link on decklink-sdk.info is dead. I made a patch with a valid link. -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: decklink-sdk.info.patch.asc URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: decklink-sdk.info.patch Type: text/x-patch Size: 209 bytes Desc: not available URL: From willysr at slackbuilds.org Sun Mar 6 16:58:23 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Mar 2016 23:58:23 +0700 Subject: [Slackbuilds-users] Dead link on decklink-sdk.info In-Reply-To: References: Message-ID: <56DC61AF.9030906@slackbuilds.org> > Hello again. Download link on decklink-sdk.info is dead. I made a patch > with a valid link. Applied to my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From arkadiusz at drabczyk.org Sun Mar 6 20:13:38 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sun, 6 Mar 2016 20:13:38 +0000 (UTC) Subject: [Slackbuilds-users] libraries/live555 - incorrect download link on website but correct on master Message-ID: On master branch in ./libraries/live555/live555.info: DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2016.02.22.tar.gz" MD5SUM="0ffd0ebf95779da2def3672327b97841" On website (branch 14.1): DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2015.12.22.tar.gz" MD5SUM="a208e31d4c3f63c61e6f2fb1f4ea9639" The problem is that using link given on branch 14.1 gives 404 - it should point to the same location as on master. -- Arkadiusz Drabczyk From pessoal at profcavalheiro.com Sun Mar 6 21:42:35 2016 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Sun, 6 Mar 2016 18:42:35 -0300 Subject: [Slackbuilds-users] libraries/live555 - incorrect download link on website but correct on master In-Reply-To: References: Message-ID: Those look like different versions, but if slackbuild script builds it flawlessly... 2016-03-06 17:13 GMT-03:00 Arkadiusz Drabczyk : > On master branch in ./libraries/live555/live555.info: > > DOWNLOAD=" > http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2016.02.22.tar.gz > " > MD5SUM="0ffd0ebf95779da2def3672327b97841" > > On website (branch 14.1): > > DOWNLOAD=" > http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2015.12.22.tar.gz > " > MD5SUM="a208e31d4c3f63c61e6f2fb1f4ea9639" > > The problem is that using link given on branch 14.1 gives 404 - it > should point to the same location as on master. > > -- > Arkadiusz Drabczyk > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Cordialmente, Lu?s Fernando Carvalho Cavalheiro Curriculum Lattes: http://lattes.cnpq.br/3397855894525757 ResearcherID: http://www.researcherid.com/rid/J-1300-2014 ORCID: http://orcid.org/0000-0001-6097-4745 Google+: https://plus.google.com/u/0/+LuisFernandoCarvalhoCavalheiro/ Skype: mestre.cavalheiro -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Sun Mar 6 21:47:46 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 7 Mar 2016 07:47:46 +1000 Subject: [Slackbuilds-users] libraries/live555 - incorrect download link on website but correct on master In-Reply-To: References: Message-ID: <56DCA582.80402@iinet.net.au> On 07/03/16 06:13, Arkadiusz Drabczyk wrote: > On master branch in ./libraries/live555/live555.info: > > DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2016.02.22.tar.gz" > MD5SUM="0ffd0ebf95779da2def3672327b97841" > > On website (branch 14.1): > > DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2015.12.22.tar.gz" > MD5SUM="a208e31d4c3f63c61e6f2fb1f4ea9639" > > The problem is that using link given on branch 14.1 gives 404 I was overly enthusiastic about cleaning slackbuildsdirectlinks/live555 directory. I've replaced it so the given link should work again now. > - it > should point to the same location as on master. It could do that but I'm uncertain about whether 14.2 scripts are being updated at the moment (during transition to 14.2). chris From chris.willing at iinet.net.au Sun Mar 6 21:55:41 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 7 Mar 2016 07:55:41 +1000 Subject: [Slackbuilds-users] libraries/live555 - incorrect download link on website but correct on master In-Reply-To: <56DCA582.80402@iinet.net.au> References: <56DCA582.80402@iinet.net.au> Message-ID: <56DCA75D.1070900@iinet.net.au> On 07/03/16 07:47, Christoph Willing wrote: > It could do that but I'm uncertain about whether 14.2 scripts are being > updated at the moment (during transition to 14.2). Sorry, typo! I meant "... whether 14.1 scripts are being updated ..." chris From arkadiusz at drabczyk.org Sun Mar 6 21:59:14 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sun, 6 Mar 2016 21:59:14 +0000 (UTC) Subject: [Slackbuilds-users] libraries/live555 - incorrect download link on website but correct on master References: <56DCA582.80402@iinet.net.au> Message-ID: On 2016-03-06, Christoph Willing wrote: > On 07/03/16 06:13, Arkadiusz Drabczyk wrote: >> On master branch in ./libraries/live555/live555.info: >> >> DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2016.02.22.tar.gz" >> MD5SUM="0ffd0ebf95779da2def3672327b97841" >> >> On website (branch 14.1): >> >> DOWNLOAD="http://sourceforge.net/projects/slackbuildsdirectlinks/files/live555/live.2015.12.22.tar.gz" >> MD5SUM="a208e31d4c3f63c61e6f2fb1f4ea9639" >> >> The problem is that using link given on branch 14.1 gives 404 > > I was overly enthusiastic about cleaning slackbuildsdirectlinks/live555 > directory. I've replaced it so the given link should work again now. ok, the link is working now. Thx. >> - it >> should point to the same location as on master. > > It could do that but I'm uncertain about whether 14.2 scripts are being > updated at the moment (during transition to 14.2). Do you mean 14.1 scripts? I just thought that live555 was supposed to be updated on 14.1 too as source tarball for older version was missing. -- Arkadiusz Drabczyk From ryan.q at linux.com Sun Mar 6 22:05:01 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 6 Mar 2016 14:05:01 -0800 Subject: [Slackbuilds-users] libraries/live555 - incorrect download link on website but correct on master In-Reply-To: References: <56DCA582.80402@iinet.net.au> Message-ID: > Do you mean 14.1 scripts? I just thought that live555 was supposed to > be updated on 14.1 too as source tarball for older version was > missing. 14.1 is not being updated as the SBo team prepares master for 14.2. -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Mon Mar 7 09:12:44 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 07 Mar 2016 10:12:44 +0100 Subject: [Slackbuilds-users] Lilypond small corrections Message-ID: <39031bf2090e61f183adc403cf966a01@schoepfer.info> Hi, as the maintainer doesn't reply since a few days, here is my diff with some corrections. Mainly lilypond doesn't depend on mftrace(anymore), it compiles and runs without it(on 14.1 and current). Grepping through the slackbuilds-git-tree says that there's no other package which needs mftrace, mftrace and t1utils(required only by mftrace) may be considered to be removed. Regards Franzen -------------- next part -------------- A non-text attachment was scrubbed... Name: lilypond.diff Type: text/x-diff Size: 2488 bytes Desc: not available URL: From pessoal at profcavalheiro.com Mon Mar 7 09:23:35 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Mon, 7 Mar 2016 06:23:35 -0300 Subject: [Slackbuilds-users] Broken links on amrnb and amrwb packages Message-ID: <20160307062335.2a3fb2f0.pessoal@profcavalheiro.com> Hello guys. I found two more broken links on .info files, this time in amrnb and amrwb packages. Link from original .info files hit 403 error. I'm sending patches to those .info files. -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: amrnb.info.patch Type: text/x-patch Size: 515 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: amrwb.info.patch Type: text/x-patch Size: 518 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From matt at thegnuguru.org Mon Mar 7 17:25:16 2016 From: matt at thegnuguru.org (Matt Arnold) Date: Mon, 7 Mar 2016 12:25:16 -0500 Subject: [Slackbuilds-users] Patch system/debootstrap update Message-ID: Hi all -- system/debootstrap hasn't been updated in 8 or 9 years. I sent a ping to to the maintainer, and he said to go ahead and update it. So here is the patch Cheers Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-system-debootstrap-New-upstream-version-take-over-as.patch Type: text/x-diff Size: 2907 bytes Desc: not available URL: From willysr at slackbuilds.org Mon Mar 7 21:15:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 8 Mar 2016 04:15:25 +0700 Subject: [Slackbuilds-users] Lilypond small corrections In-Reply-To: <39031bf2090e61f183adc403cf966a01@schoepfer.info> References: <39031bf2090e61f183adc403cf966a01@schoepfer.info> Message-ID: <56DDEF6D.2010801@slackbuilds.org> > as the maintainer doesn't reply since a few days, here is my diff with some > corrections. Mainly lilypond doesn't depend on mftrace(anymore), it > compiles > and runs without it(on 14.1 and current). Grepping through the > slackbuilds-git-tree says that there's no other package which needs > mftrace, mftrace and t1utils(required only by mftrace) may be considered > to be removed. I had this error when building lilypond without mftrace ERROR: Please install required programs: t1asm See INSTALL.txt for more information on how to build LilyPond it works fine after i installed mftrace and all it's dependencies -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 7 21:23:58 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 8 Mar 2016 04:23:58 +0700 Subject: [Slackbuilds-users] Broken links on amrnb and amrwb packages In-Reply-To: <20160307062335.2a3fb2f0.pessoal@profcavalheiro.com> References: <20160307062335.2a3fb2f0.pessoal@profcavalheiro.com> Message-ID: <56DDF16E.6000308@slackbuilds.org> > Hello guys. I found two more broken links on .info files, this time in amrnb and amrwb packages. Link from original .info files hit 403 error. I'm sending patches to those .info files. applied to my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 7 21:27:09 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 8 Mar 2016 04:27:09 +0700 Subject: [Slackbuilds-users] Patch system/debootstrap update In-Reply-To: References: Message-ID: <56DDF22D.90306@slackbuilds.org> > system/debootstrap hasn't been updated in 8 or 9 years. I sent a ping to > to the maintainer, and he said to go ahead and update it. So here is the > patch Applied in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From marc at mos6581.de Tue Mar 8 19:04:02 2016 From: marc at mos6581.de (Marcel Saegebarth) Date: Tue, 8 Mar 2016 20:04:02 +0100 Subject: [Slackbuilds-users] Wrong UID in NetworkManager-openconnect Message-ID: <56DF2222.6090301@mos6581.de> There's a typo in the SlackBuild were it states that you should add an user with UID 320, but it should be 321 (as in the comments). 320 is already reserved for "nm-openvpn". -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Tue Mar 8 19:19:29 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 8 Mar 2016 20:19:29 +0100 Subject: [Slackbuilds-users] Wrong UID in NetworkManager-openconnect In-Reply-To: <56DF2222.6090301@mos6581.de> References: <56DF2222.6090301@mos6581.de> Message-ID: 2016-03-08 20:04 GMT+01:00 Marcel Saegebarth : > There's a typo in the SlackBuild were it states that you should add > an user with UID 320, but it should be 321 (as in the comments). > 320 is already reserved for "nm-openvpn". thanks Marcel, I committed the fix in my branch. Matteo From slackbuilds at schoepfer.info Tue Mar 8 21:28:37 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 08 Mar 2016 22:28:37 +0100 Subject: [Slackbuilds-users] Lilypond small corrections In-Reply-To: <56DDEF6D.2010801@slackbuilds.org> References: <39031bf2090e61f183adc403cf966a01@schoepfer.info> <56DDEF6D.2010801@slackbuilds.org> Message-ID: <3fc7632a3f6c47485b4228daaa729f37@schoepfer.info> >> Mainly lilypond doesn't depend on mftrace(anymore), it >> compiles >> and runs without it(on 14.1 and current). Grepping through the >> slackbuilds-git-tree says that there's no other package which needs >> mftrace, mftrace and t1utils(required only by mftrace) may be >> considered >> to be removed. > > I had this error when building lilypond without mftrace > > ERROR: Please install required programs: t1asm > > See INSTALL.txt for more information on how to build LilyPond > > it works fine after i installed mftrace and all it's dependencies I was wrong, while building lilypond i had texlive installed which contains t1utils. So, t1utils or texlive besides fontforge and guile1.8 are required, no mftrace. Regards Franzen From rworkman at slackbuilds.org Tue Mar 8 22:00:50 2016 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 8 Mar 2016 16:00:50 -0600 Subject: [Slackbuilds-users] Wrong UID in NetworkManager-openconnect In-Reply-To: <56DF2222.6090301@mos6581.de> References: <56DF2222.6090301@mos6581.de> Message-ID: <20160308160050.702193b5@home.rlworkman.net> On Tue, 8 Mar 2016 20:04:02 +0100 Marcel Saegebarth wrote: > There's a typo in the SlackBuild were it states that you should add > an user with UID 320, but it should be 321 (as in the comments). > 320 is already reserved for "nm-openvpn". Argh. Thanks, marc, for the report, and thanks, ponce, for fixing. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lynx at panix.com Thu Mar 10 01:11:57 2016 From: lynx at panix.com (Arthur W. Green) Date: Wed, 9 Mar 2016 18:11:57 -0700 Subject: [Slackbuilds-users] run libtool in doinst.sh? Message-ID: <56E0C9DD.1080500@panix.com> Hi, An SBo I'm working on installs a couple shared libraries. After making the libraries, the build output advises: libtool: warning: remember to run 'libtool --finish /usr/lib64' Is it safe to assume I should be making this call to libtool in my package's doinst.sh? \\ Arthur From baildon.research at googlemail.com Thu Mar 10 09:12:38 2016 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 10 Mar 2016 09:12:38 +0000 Subject: [Slackbuilds-users] run libtool in doinst.sh? In-Reply-To: <56E0C9DD.1080500@panix.com> References: <56E0C9DD.1080500@panix.com> Message-ID: > libtool: warning: remember to run 'libtool --finish /usr/lib64' > > Is it safe to assume I should be making this call to libtool in my > package's doinst.sh? No. It's not necessary. 'libtool --finish' is basically just ldconfig, and installpkg itself does that for you. If in doubt, check the template and grep around in the SlackBuilds repository. If something isn't in the template and isn't in any other SlackBuild, it's definitely worth asking about it here before you write the code. So, you did the right thing to ask the question Arthur :-) -D. From apatrza1 at rochester.rr.com Fri Mar 11 16:09:56 2016 From: apatrza1 at rochester.rr.com (A P) Date: Fri, 11 Mar 2016 11:09:56 -0500 Subject: [Slackbuilds-users] clamtk-5.20 requires perl-glib-1.07, but perl-glib-1.07 is broken Message-ID: <56E2EDD4.3030301@rochester.rr.com> clamtk-5.20-x86_64-1_SBo requires perl-glib (1.307) but the perl-glib reference does not exist on cpan. Attempts to use perl-glib-1.321 results in many runtime errors. Thanks, -Andy From willysr at slackbuilds.org Fri Mar 11 23:38:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Mar 2016 06:38:53 +0700 Subject: [Slackbuilds-users] clamtk-5.20 requires perl-glib-1.07, but perl-glib-1.07 is broken In-Reply-To: <56E2EDD4.3030301@rochester.rr.com> References: <56E2EDD4.3030301@rochester.rr.com> Message-ID: <56E3570D.9000708@slackbuilds.org> > clamtk-5.20-x86_64-1_SBo requires perl-glib (1.307) but the perl-glib > reference does not exist on cpan. > Attempts to use perl-glib-1.321 results in many runtime errors. just tested here on vm using sbopkg zenity: MD5SUM check for zenity-3.18.1.1.tar.xz ... OK Building package zenity-3.18.1.1-x86_64-1_SBo.tgz ... OK Installing package zenity-3.18.1.1-x86_64-1_SBo.tgz ... OK clamav: MD5SUM check for clamav-0.99.tar.gz ... OK Error occurred with build. Please check the log. clamav: MD5SUM check for clamav-0.99.tar.gz ... OK Building package clamav-0.99-x86_64-1_SBo.tgz ... OK Installing package clamav-0.99-x86_64-1_SBo.tgz ... OK perl-extutils-pkgconfig: MD5SUM check for ExtUtils-PkgConfig-1.15.tar.gz ... OK Building package perl-extutils-pkgconfig-1.15-x86_64-1_SBo.tgz ... OK Installing package perl-extutils-pkgconfig-1.15-x86_64-1_SBo.tgz ... OK perl-extutils-depends: MD5SUM check for ExtUtils-Depends-0.404.tar.gz ... OK Building package perl-extutils-depends-0.404-x86_64-1_SBo.tgz ... OK Installing package perl-extutils-depends-0.404-x86_64-1_SBo.tgz ... OK perl-glib: MD5SUM check for Glib-1.307.tar.gz ... OK Building package perl-glib-1.307-x86_64-1_SBo.tgz ... OK Installing package perl-glib-1.307-x86_64-1_SBo.tgz ... OK perl-cairo: MD5SUM check for Cairo-1.105.tar.gz ... OK Building package perl-cairo-1.105-x86_64-1_SBo.tgz ... OK Installing package perl-cairo-1.105-x86_64-1_SBo.tgz ... OK perl-pango: MD5SUM check for Pango-1.226.tar.gz ... OK Error occurred with build. Please check the log. perl-gtk2: MD5SUM check for Gtk2-1.2495.tar.gz ... OK Building package perl-gtk2-1.2495-x86_64-1_SBo.tgz ... OK Installing package perl-gtk2-1.2495-x86_64-1_SBo.tgz ... OK perl-Time-Piece: MD5SUM check for Time-Piece-1.31.tar.gz ... OK Building package perl-Time-Piece-1.31-x86_64-1_SBo.tgz ... OK Installing package perl-Time-Piece-1.31-x86_64-1_SBo.tgz ... OK perl-Text-CSV: MD5SUM check for Text-CSV-1.33.tar.gz ... OK Building package perl-Text-CSV-1.33-x86_64-1_SBo.tgz ... OK Installing package perl-Text-CSV-1.33-x86_64-1_SBo.tgz ... OK perl-Net-LibIDN: MD5SUM check for Net-LibIDN-0.12.tar.gz ... OK Building package perl-Net-LibIDN-0.12-x86_64-1_SBo.tgz ... OK Installing package perl-Net-LibIDN-0.12-x86_64-1_SBo.tgz ... OK Net-SSLeay: MD5SUM check for Net-SSLeay-1.72.tar.gz ... OK Building package Net-SSLeay-1.72-x86_64-1_SBo.tgz ... OK Installing package Net-SSLeay-1.72-x86_64-1_SBo.tgz ... OK perl-IO-Socket-SSL: MD5SUM check for IO-Socket-SSL-2.022.tar.gz ... OK Building package perl-IO-Socket-SSL-2.022-x86_64-1_SBo.tgz ... OK Installing package perl-IO-Socket-SSL-2.022-x86_64-1_SBo.tgz ... OK perl-Mozilla-CA: MD5SUM check for Mozilla-CA-20130114.tar.gz ... OK Building package perl-Mozilla-CA-20130114-x86_64-1_SBo.tgz ... OK Installing package perl-Mozilla-CA-20130114-x86_64-1_SBo.tgz ... OK perl-www-robotrules: MD5SUM check for WWW-RobotRules-6.02.tar.gz ... OK Building package perl-www-robotrules-6.02-x86_64-1_SBo.tgz ... OK Installing package perl-www-robotrules-6.02-x86_64-1_SBo.tgz ... OK perl-net-http: MD5SUM check for Net-HTTP-6.09.tar.gz ... OK Building package perl-net-http-6.09-x86_64-1_SBo.tgz ... OK Installing package perl-net-http-6.09-x86_64-1_SBo.tgz ... OK perl-IO-HTML: MD5SUM check for IO-HTML-1.001.tar.gz ... OK Building package perl-IO-HTML-1.001-x86_64-1_SBo.tgz ... OK Installing package perl-IO-HTML-1.001-x86_64-1_SBo.tgz ... OK perl-lwp-mediatypes: MD5SUM check for LWP-MediaTypes-6.02.tar.gz ... OK Building package perl-lwp-mediatypes-6.02-x86_64-1_SBo.tgz ... OK Installing package perl-lwp-mediatypes-6.02-x86_64-1_SBo.tgz ... OK perl-http-date: MD5SUM check for HTTP-Date-6.02.tar.gz ... OK Building package perl-http-date-6.02-x86_64-1_SBo.tgz ... OK Installing package perl-http-date-6.02-x86_64-1_SBo.tgz ... OK perl-html-tagset: MD5SUM check for HTML-Tagset-3.20.tar.gz ... OK Building package perl-html-tagset-3.20-x86_64-1_SBo.tgz ... OK Installing package perl-html-tagset-3.20-x86_64-1_SBo.tgz ... OK perl-html-parser: MD5SUM check for HTML-Parser-3.71.tar.gz ... OK Building package perl-html-parser-3.71-x86_64-1_SBo.tgz ... OK Installing package perl-html-parser-3.71-x86_64-1_SBo.tgz ... OK perl-encode-locale: MD5SUM check for Encode-Locale-1.05.tar.gz ... OK Building package perl-encode-locale-1.05-x86_64-1_SBo.tgz ... OK Installing package perl-encode-locale-1.05-x86_64-1_SBo.tgz ... OK perl-http-message: MD5SUM check for HTTP-Message-6.11.tar.gz ... OK Building package perl-http-message-6.11-x86_64-1_SBo.tgz ... OK Installing package perl-http-message-6.11-x86_64-1_SBo.tgz ... OK perl-http-negotiate: MD5SUM check for HTTP-Negotiate-6.01.tar.gz ... OK Building package perl-http-negotiate-6.01-x86_64-1_SBo.tgz ... OK Installing package perl-http-negotiate-6.01-x86_64-1_SBo.tgz ... OK perl-http-daemon: MD5SUM check for HTTP-Daemon-6.01.tar.gz ... OK Building package perl-http-daemon-6.01-x86_64-1_SBo.tgz ... OK Installing package perl-http-daemon-6.01-x86_64-1_SBo.tgz ... OK perl-http-cookies: MD5SUM check for HTTP-Cookies-6.01.tar.gz ... OK Building package perl-http-cookies-6.01-x86_64-1_SBo.tgz ... OK Installing package perl-http-cookies-6.01-x86_64-1_SBo.tgz ... OK perl-file-listing: MD5SUM check for File-Listing-6.04.tar.gz ... OK Building package perl-file-listing-6.04-x86_64-1_SBo.tgz ... OK Installing package perl-file-listing-6.04-x86_64-1_SBo.tgz ... OK libwww-perl: MD5SUM check for libwww-perl-6.13.tar.gz ... OK Building package libwww-perl-6.13-x86_64-1_SBo.tgz ... OK Installing package libwww-perl-6.13-x86_64-1_SBo.tgz ... OK perl-LWP-Protocol-https: MD5SUM check for LWP-Protocol-https-6.04.tar.gz ... OK Building package perl-LWP-Protocol-https-6.04-x86_64-1_SBo.tgz ... OK Installing package perl-LWP-Protocol-https-6.04-x86_64-1_SBo.tgz ... OK perl-JSON: MD5SUM check for JSON-2.90.tar.gz ... OK Building package perl-JSON-2.90-x86_64-1_SBo.tgz ... OK Installing package perl-JSON-2.90-x86_64-1_SBo.tgz ... OK clamtk: MD5SUM check for clamtk-5.20.tar.gz ... OK Building package clamtk-5.20-x86_64-1_SBo.tgz ... OK Installing package clamtk-5.20-x86_64-1_SBo.tgz ... OK there was an error while building perl-pango but i update it to the latest version (manually) and it works again -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From glenn.becker at gmail.com Sat Mar 12 14:43:47 2016 From: glenn.becker at gmail.com (Glenn Becker) Date: Sat, 12 Mar 2016 09:43:47 -0500 Subject: [Slackbuilds-users] clamtk-5.20 requires perl-glib-1.07, but perl-glib-1.07 is broken In-Reply-To: <56E3570D.9000708@slackbuilds.org> References: <56E2EDD4.3030301@rochester.rr.com> <56E3570D.9000708@slackbuilds.org> Message-ID: perl-pango is one of mine. I will update today if I can (I'm on the road). /Glenn On Fri, Mar 11, 2016 at 6:38 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > clamtk-5.20-x86_64-1_SBo requires perl-glib (1.307) but the perl-glib > > reference does not exist on cpan. > > Attempts to use perl-glib-1.321 results in many runtime errors. > > just tested here on vm using sbopkg > > zenity: > MD5SUM check for zenity-3.18.1.1.tar.xz ... OK > Building package zenity-3.18.1.1-x86_64-1_SBo.tgz ... OK > Installing package zenity-3.18.1.1-x86_64-1_SBo.tgz ... OK > > clamav: > MD5SUM check for clamav-0.99.tar.gz ... OK > Error occurred with build. Please check the log. > > clamav: > MD5SUM check for clamav-0.99.tar.gz ... OK > Building package clamav-0.99-x86_64-1_SBo.tgz ... OK > Installing package clamav-0.99-x86_64-1_SBo.tgz ... OK > > perl-extutils-pkgconfig: > MD5SUM check for ExtUtils-PkgConfig-1.15.tar.gz ... OK > Building package perl-extutils-pkgconfig-1.15-x86_64-1_SBo.tgz ... OK > Installing package perl-extutils-pkgconfig-1.15-x86_64-1_SBo.tgz ... OK > > perl-extutils-depends: > MD5SUM check for ExtUtils-Depends-0.404.tar.gz ... OK > Building package perl-extutils-depends-0.404-x86_64-1_SBo.tgz ... OK > Installing package perl-extutils-depends-0.404-x86_64-1_SBo.tgz ... OK > > perl-glib: > MD5SUM check for Glib-1.307.tar.gz ... OK > Building package perl-glib-1.307-x86_64-1_SBo.tgz ... OK > Installing package perl-glib-1.307-x86_64-1_SBo.tgz ... OK > > perl-cairo: > MD5SUM check for Cairo-1.105.tar.gz ... OK > Building package perl-cairo-1.105-x86_64-1_SBo.tgz ... OK > Installing package perl-cairo-1.105-x86_64-1_SBo.tgz ... OK > > perl-pango: > MD5SUM check for Pango-1.226.tar.gz ... OK > Error occurred with build. Please check the log. > > perl-gtk2: > MD5SUM check for Gtk2-1.2495.tar.gz ... OK > Building package perl-gtk2-1.2495-x86_64-1_SBo.tgz ... OK > Installing package perl-gtk2-1.2495-x86_64-1_SBo.tgz ... OK > > perl-Time-Piece: > MD5SUM check for Time-Piece-1.31.tar.gz ... OK > Building package perl-Time-Piece-1.31-x86_64-1_SBo.tgz ... OK > Installing package perl-Time-Piece-1.31-x86_64-1_SBo.tgz ... OK > > perl-Text-CSV: > MD5SUM check for Text-CSV-1.33.tar.gz ... OK > Building package perl-Text-CSV-1.33-x86_64-1_SBo.tgz ... OK > Installing package perl-Text-CSV-1.33-x86_64-1_SBo.tgz ... OK > > perl-Net-LibIDN: > MD5SUM check for Net-LibIDN-0.12.tar.gz ... OK > Building package perl-Net-LibIDN-0.12-x86_64-1_SBo.tgz ... OK > Installing package perl-Net-LibIDN-0.12-x86_64-1_SBo.tgz ... OK > > Net-SSLeay: > MD5SUM check for Net-SSLeay-1.72.tar.gz ... OK > Building package Net-SSLeay-1.72-x86_64-1_SBo.tgz ... OK > Installing package Net-SSLeay-1.72-x86_64-1_SBo.tgz ... OK > > perl-IO-Socket-SSL: > MD5SUM check for IO-Socket-SSL-2.022.tar.gz ... OK > Building package perl-IO-Socket-SSL-2.022-x86_64-1_SBo.tgz ... OK > Installing package perl-IO-Socket-SSL-2.022-x86_64-1_SBo.tgz ... OK > > perl-Mozilla-CA: > MD5SUM check for Mozilla-CA-20130114.tar.gz ... OK > Building package perl-Mozilla-CA-20130114-x86_64-1_SBo.tgz ... OK > Installing package perl-Mozilla-CA-20130114-x86_64-1_SBo.tgz ... OK > > perl-www-robotrules: > MD5SUM check for WWW-RobotRules-6.02.tar.gz ... OK > Building package perl-www-robotrules-6.02-x86_64-1_SBo.tgz ... OK > Installing package perl-www-robotrules-6.02-x86_64-1_SBo.tgz ... OK > > perl-net-http: > MD5SUM check for Net-HTTP-6.09.tar.gz ... OK > Building package perl-net-http-6.09-x86_64-1_SBo.tgz ... OK > Installing package perl-net-http-6.09-x86_64-1_SBo.tgz ... OK > > perl-IO-HTML: > MD5SUM check for IO-HTML-1.001.tar.gz ... OK > Building package perl-IO-HTML-1.001-x86_64-1_SBo.tgz ... OK > Installing package perl-IO-HTML-1.001-x86_64-1_SBo.tgz ... OK > > perl-lwp-mediatypes: > MD5SUM check for LWP-MediaTypes-6.02.tar.gz ... OK > Building package perl-lwp-mediatypes-6.02-x86_64-1_SBo.tgz ... OK > Installing package perl-lwp-mediatypes-6.02-x86_64-1_SBo.tgz ... OK > > perl-http-date: > MD5SUM check for HTTP-Date-6.02.tar.gz ... OK > Building package perl-http-date-6.02-x86_64-1_SBo.tgz ... OK > Installing package perl-http-date-6.02-x86_64-1_SBo.tgz ... OK > > perl-html-tagset: > MD5SUM check for HTML-Tagset-3.20.tar.gz ... OK > Building package perl-html-tagset-3.20-x86_64-1_SBo.tgz ... OK > Installing package perl-html-tagset-3.20-x86_64-1_SBo.tgz ... OK > > perl-html-parser: > MD5SUM check for HTML-Parser-3.71.tar.gz ... OK > Building package perl-html-parser-3.71-x86_64-1_SBo.tgz ... OK > Installing package perl-html-parser-3.71-x86_64-1_SBo.tgz ... OK > > perl-encode-locale: > MD5SUM check for Encode-Locale-1.05.tar.gz ... OK > Building package perl-encode-locale-1.05-x86_64-1_SBo.tgz ... OK > Installing package perl-encode-locale-1.05-x86_64-1_SBo.tgz ... OK > > perl-http-message: > MD5SUM check for HTTP-Message-6.11.tar.gz ... OK > Building package perl-http-message-6.11-x86_64-1_SBo.tgz ... OK > Installing package perl-http-message-6.11-x86_64-1_SBo.tgz ... OK > > perl-http-negotiate: > MD5SUM check for HTTP-Negotiate-6.01.tar.gz ... OK > Building package perl-http-negotiate-6.01-x86_64-1_SBo.tgz ... OK > Installing package perl-http-negotiate-6.01-x86_64-1_SBo.tgz ... OK > > perl-http-daemon: > MD5SUM check for HTTP-Daemon-6.01.tar.gz ... OK > Building package perl-http-daemon-6.01-x86_64-1_SBo.tgz ... OK > Installing package perl-http-daemon-6.01-x86_64-1_SBo.tgz ... OK > > perl-http-cookies: > MD5SUM check for HTTP-Cookies-6.01.tar.gz ... OK > Building package perl-http-cookies-6.01-x86_64-1_SBo.tgz ... OK > Installing package perl-http-cookies-6.01-x86_64-1_SBo.tgz ... OK > > perl-file-listing: > MD5SUM check for File-Listing-6.04.tar.gz ... OK > Building package perl-file-listing-6.04-x86_64-1_SBo.tgz ... OK > Installing package perl-file-listing-6.04-x86_64-1_SBo.tgz ... OK > > libwww-perl: > MD5SUM check for libwww-perl-6.13.tar.gz ... OK > Building package libwww-perl-6.13-x86_64-1_SBo.tgz ... OK > Installing package libwww-perl-6.13-x86_64-1_SBo.tgz ... OK > > perl-LWP-Protocol-https: > MD5SUM check for LWP-Protocol-https-6.04.tar.gz ... OK > Building package perl-LWP-Protocol-https-6.04-x86_64-1_SBo.tgz ... OK > Installing package perl-LWP-Protocol-https-6.04-x86_64-1_SBo.tgz ... OK > > perl-JSON: > MD5SUM check for JSON-2.90.tar.gz ... OK > Building package perl-JSON-2.90-x86_64-1_SBo.tgz ... OK > Installing package perl-JSON-2.90-x86_64-1_SBo.tgz ... OK > > clamtk: > MD5SUM check for clamtk-5.20.tar.gz ... OK > Building package clamtk-5.20-x86_64-1_SBo.tgz ... OK > Installing package clamtk-5.20-x86_64-1_SBo.tgz ... OK > > there was an error while building perl-pango but i update it to the > latest version (manually) and it works again > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Mar 12 16:38:07 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Mar 2016 23:38:07 +0700 Subject: [Slackbuilds-users] clamtk-5.20 requires perl-glib-1.07, but perl-glib-1.07 is broken In-Reply-To: References: <56E2EDD4.3030301@rochester.rr.com> <56E3570D.9000708@slackbuilds.org> Message-ID: <56E445EF.60101@slackbuilds.org> > perl-pango is one of mine. I will update today if I can (I'm on the road). already did :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From glenn.becker at gmail.com Sat Mar 12 17:35:25 2016 From: glenn.becker at gmail.com (Glenn Becker) Date: Sat, 12 Mar 2016 12:35:25 -0500 Subject: [Slackbuilds-users] clamtk-5.20 requires perl-glib-1.07, but perl-glib-1.07 is broken In-Reply-To: <56E445EF.60101@slackbuilds.org> References: <56E2EDD4.3030301@rochester.rr.com> <56E3570D.9000708@slackbuilds.org> <56E445EF.60101@slackbuilds.org> Message-ID: :) On Sat, Mar 12, 2016 at 11:38 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > perl-pango is one of mine. I will update today if I can (I'm on the > road). > > already did :) > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sat Mar 12 22:04:07 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 12 Mar 2016 23:04:07 +0100 Subject: [Slackbuilds-users] ffmpeg and "non-redistributable binary" Message-ID: <56E49257.10506@gmail.com> Hi, Some of the dependencies for _ffmpeg_ make it "non-redistributable binary". I'd like to ask what does it mean? Does it mean it's forbidden to redistribute the binary because of law restrictions? Or does it mean the binary will contain instructions that cannot be executed on, for example, previous generations of the CPU? -- Best regards, Andrzej Telszewski From softwareworks at use.startmail.com Sat Mar 12 22:07:25 2016 From: softwareworks at use.startmail.com (Black Rider) Date: Sat, 12 Mar 2016 22:07:25 +0000 (UTC) Subject: [Slackbuilds-users] ffmpeg and "non-redistributable binary" References: <56E49257.10506@gmail.com> Message-ID: El Sat, 12 Mar 2016 23:04:07 +0100, Andrzej Telszewski escribi?: > Hi, > > Some of the dependencies for _ffmpeg_ make it "non-redistributable > binary". > > I'd like to ask what does it mean? > > Does it mean it's forbidden to redistribute the binary because of law > restrictions? > > Or does it mean the binary will contain instructions that cannot be > executed on, for example, previous generations of the CPU? It means that copyright/patents can make the resulting binary non- distributable according to the law. From atelszewski at gmail.com Sat Mar 12 22:15:09 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 12 Mar 2016 23:15:09 +0100 Subject: [Slackbuilds-users] ffmpeg and "non-redistributable binary" In-Reply-To: References: <56E49257.10506@gmail.com> Message-ID: <56E494ED.5010005@gmail.com> On 12/03/16 23:07, Black Rider wrote: > El Sat, 12 Mar 2016 23:04:07 +0100, Andrzej Telszewski escribi?: > >> Hi, >> >> Some of the dependencies for _ffmpeg_ make it "non-redistributable >> binary". >> >> I'd like to ask what does it mean? >> >> Does it mean it's forbidden to redistribute the binary because of law >> restrictions? >> >> Or does it mean the binary will contain instructions that cannot be >> executed on, for example, previous generations of the CPU? > > It means that copyright/patents can make the resulting binary non- > distributable according to the law. > Thanks! > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Pozdrawiam, Best regards, Andrzej Telszewski From pessoal at profcavalheiro.com Sat Mar 12 23:20:32 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sat, 12 Mar 2016 20:20:32 -0300 Subject: [Slackbuilds-users] Error while creating nvidia-legacy340-driver package on -current Message-ID: <20160312202032.49fe1a8e.pessoal@profcavalheiro.com> Dear friends I'm using sbopkg on -master branch to create nvidia-legacy340-driver package on a Slack64 multilib current computer. After kernel upgrade from March 10th I got this error while trying to create that package: /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpci.a(names-hwdb.o): In function `pci_id_hwdb_lookup': names-hwdb.c:(.text+0xb4): undefined reference to `udev_hwdb_get_properties_list_entry' names-hwdb.c:(.text+0xc9): undefined reference to `udev_list_entry_get_next' names-hwdb.c:(.text+0xd9): undefined reference to `udev_list_entry_get_name' names-hwdb.c:(.text+0xf0): undefined reference to `udev_list_entry_get_value' names-hwdb.c:(.text+0x214): undefined reference to `udev_new' names-hwdb.c:(.text+0x221): undefined reference to `udev_hwdb_new' /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpci.a(names-hwdb.o): In function `pci_id_hwdb_free': names-hwdb.c:(.text+0x24e): undefined reference to `udev_hwdb_unref' names-hwdb.c:(.text+0x264): undefined reference to `udev_unref' collect2: error: ld returned 1 exit status Makefile:214: recipe for target '_out/Linux_x86_64/nvidia-installer' failed make: *** [_out/Linux_x86_64/nvidia-installer] Error 1 I'm using default SlackBuild files from -master branch. Until this kernel upgrade I was able to create this package with any problem. Any idea of why am I getting this errors? -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From pessoal at profcavalheiro.com Sat Mar 12 23:42:39 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sat, 12 Mar 2016 20:42:39 -0300 Subject: [Slackbuilds-users] Error while creating nvidia-legacy340-driver package on -current Message-ID: <20160312204239.5727c46a.pessoal@profcavalheiro.com> Dear friend Looks like I found by myself how to solve this issue. Reading nvidia-legacy340-driver.SlackBuild script, I found a commentary that stated nvidia-installer isn't needed by this SlackBuild. So, I commented out all lines related to nvidia-installer building and lo!, it worked! I'm sending to you a .patch file to apply to nvidia-legacy340-driver.SlackBuild file. Em 12 de 03 de 2016 ?s 20:20:32T-0300, Lu?s Fernando Carvalho Cavalheiro escreveu: > Dear friends > > I'm using sbopkg on -master branch to create nvidia-legacy340-driver package on a Slack64 multilib current computer. After kernel upgrade from March 10th I got this error while trying to create that package: > > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpci.a(names-hwdb.o): In function `pci_id_hwdb_lookup': > names-hwdb.c:(.text+0xb4): undefined reference to `udev_hwdb_get_properties_list_entry' > names-hwdb.c:(.text+0xc9): undefined reference to `udev_list_entry_get_next' > names-hwdb.c:(.text+0xd9): undefined reference to `udev_list_entry_get_name' > names-hwdb.c:(.text+0xf0): undefined reference to `udev_list_entry_get_value' > names-hwdb.c:(.text+0x214): undefined reference to `udev_new' > names-hwdb.c:(.text+0x221): undefined reference to `udev_hwdb_new' > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libpci.a(names-hwdb.o): In function `pci_id_hwdb_free': > names-hwdb.c:(.text+0x24e): undefined reference to `udev_hwdb_unref' > names-hwdb.c:(.text+0x264): undefined reference to `udev_unref' > collect2: error: ld returned 1 exit status > Makefile:214: recipe for target '_out/Linux_x86_64/nvidia-installer' failed > make: *** [_out/Linux_x86_64/nvidia-installer] Error 1 > > I'm using default SlackBuild files from -master branch. Until this kernel upgrade I was able to create this package with any problem. Any idea of why am I getting this errors? > > -- > 93 93/93 > Lu?s Fernando Carvalho Cavalheiro -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-legacy340-driver.SlackBuild.patch Type: text/x-patch Size: 1388 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From ryan.q at linux.com Sun Mar 13 00:23:17 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 13 Mar 2016 00:23:17 +0000 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160224091418.3f914aa0@shaggy.doo> References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org> <56CC47BF.2010105@gmail.com> <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo> Message-ID: > > > On 24/02/16 07:37, Kyle Guinn wrote: > > > On 2/23/16, Andrzej Telszewski wrote: > > >> On 05/02/16 13:48, Martijn Dekker wrote: > > >>> 2. The following horrible, broken and obsolete eyesore: > > >>> > > >>> find -L . \ > > >>> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm > > >>> 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \ > > >>> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm > > >>> 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > > >>> > > >>> can be replaced by: > > >>> > > >>> chmod -R a-st,u+rwX,go-w+rX . > > >> > > >> I advocate this solution. > > >> Can we switch for it? > > >> Or at least would the SlackBuild be accepted if I used this > > >> construct? > > > > > > Even shorter and simpler to understand: > > > chmod -R u+w,go-w,a+rX-st . > > > > > These 'hammer everything' solutions change permissions on files that > the find command specifically misses, which may have been set on purpose > by upstream. > > Note that I'm not adverse to submissions using a single chmod line, > many of my scripts did this in the past. It requires an extra level > of awareness though, that might be a trap for new players. For the > template, we should leave the find command in place. Bulk swapping > them out in the repo is not an option. > Erik, Are you opposed to this solution? find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -print0 | \ xargs -0 chmod 755 find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -print0 | \ xargs -0 chmod 644 It was proposed by B. Watson here: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html It seems to work the same as the current template, but is just less resource intensive ... but I don't know for sure. -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Sun Mar 13 00:46:29 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 12 Mar 2016 18:46:29 -0600 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org> <56CC47BF.2010105@gmail.com> <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo> Message-ID: <20160312184629.37f4d271@shaggy.doo> On Sun, 13 Mar 2016 00:23:17 +0000 "Ryan P.C. McQuen" wrote: > Erik, > > Are you opposed to this solution? > > find -L . \ > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > -o -perm 511 \) -print0 | \ > xargs -0 chmod 755 > find -L . \ > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > -o -perm 440 -o -perm 400 \) -print0 | \ > xargs -0 chmod 644 > > It was proposed by B. Watson here: > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html > > It seems to work the same as the current template, but is just less > resource intensive ... but I don't know for sure. I honestly thought we had agreed to make this change, that another admin (rworkman?) agreed too. I read through that thread just now and I don't see it.. so maybe it happened on IRC, or not at all. Maybe another admin, rworkman or willysr, could put forward their thoughts on this change. I don't immediately see any problems with it, except possibly the amount of arguments chmod can take? (which may actually be a bash limitation) I suppose we know the answer to that since all 18k+ files from the mame source worked fine? If that seems to be the truth, as in all of those files got hit, and not say 100 or 1000 or whatever the command line limit might be, then I'm in favor of this change. I'm not really in a position to run some tests to find out, though. If any of that sounds confusing, what I'm imagining is passing 18k+ file names to chmod, and I seem to remember that type of thing being an issue in the past. I apologize in advance if that isn't true or I'm being ignorant on exactly what's happening in the above code. -- Erik From willysr at slackbuilds.org Sun Mar 13 01:11:12 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 13 Mar 2016 08:11:12 +0700 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160312184629.37f4d271@shaggy.doo> References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org> <56CC47BF.2010105@gmail.com> <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo> <20160312184629.37f4d271@shaggy.doo> Message-ID: <56E4BE30.5020900@slackbuilds.org> >> Are you opposed to this solution? >> >> find -L . \ >> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ >> -o -perm 511 \) -print0 | \ >> xargs -0 chmod 755 >> find -L . \ >> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ >> -o -perm 440 -o -perm 400 \) -print0 | \ >> xargs -0 chmod 644 >> >> It was proposed by B. Watson here: >> >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html >> >> It seems to work the same as the current template, but is just less >> resource intensive ... but I don't know for sure. > > I honestly thought we had agreed to make this change, that another > admin (rworkman?) agreed too. I read through that thread just now and I > don't see it.. so maybe it happened on IRC, or not at all. > > Maybe another admin, rworkman or willysr, could put forward their > thoughts on this change. I don't immediately see any problems with it, > except possibly the amount of arguments chmod can take? (which may > actually be a bash limitation) I suppose we know the answer to that > since all 18k+ files from the mame source worked fine? If that seems to > be the truth, as in all of those files got hit, and not say 100 or 1000 > or whatever the command line limit might be, then I'm in favor of this > change. I'm not really in a position to run some tests to find out, > though. > > If any of that sounds confusing, what I'm imagining is passing 18k+ > file names to chmod, and I seem to remember that type of thing being an > issue in the past. I apologize in advance if that isn't true or I'm > being ignorant on exactly what's happening in the above code. I have no objection at all if it's proven to work faster and same results as the current find code. rworkman already mentioned on another thread that he doesn't oppose to this idea, but let me quote his reply on this : "I didn't see any opposition to this, and I don't have any, so if you want to make a user branch within the template repo and ping me about it, I'll be more than happy to merge it for 14.2. Once that's done, and once the current-wip branch gets merged to master (after 14.2 beta/rc announcement) and we get moving a bit heavier there, if you'd like to work up a branch to make the changes in there, we'll definitely consider it. It will probably be worth touching base with us first on that one, because you'll want to minimize the merge conflicts that we are creating while you're doing the changes there" the current condition is now current-wip branch is merged to master, Beta 2 has been announced, but no one is up for the move. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From pessoal at profcavalheiro.com Sun Mar 13 01:18:50 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sat, 12 Mar 2016 22:18:50 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E4BE30.5020900@slackbuilds.org> References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org> <56CC47BF.2010105@gmail.com> <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo> <20160312184629.37f4d271@shaggy.doo> <56E4BE30.5020900@slackbuilds.org> Message-ID: <20160312221850.1b1104f8.pessoal@profcavalheiro.com> I'd stick with find solution. If a source has more files than chmod can handle (or perhaps bash can do, since there may be a limitation on * expansion), it would fail to set desired permissions to files. Em 13 de 03 de 2016 ?s 08:11:12T+0700, Willy Sudiarto Raharjo escreveu: > >> Are you opposed to this solution? > >> > >> find -L . \ > >> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > >> -o -perm 511 \) -print0 | \ > >> xargs -0 chmod 755 > >> find -L . \ > >> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > >> -o -perm 440 -o -perm 400 \) -print0 | \ > >> xargs -0 chmod 644 > >> > >> It was proposed by B. Watson here: > >> > >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html > >> > >> It seems to work the same as the current template, but is just less > >> resource intensive ... but I don't know for sure. > > > > I honestly thought we had agreed to make this change, that another > > admin (rworkman?) agreed too. I read through that thread just now and I > > don't see it.. so maybe it happened on IRC, or not at all. > > > > Maybe another admin, rworkman or willysr, could put forward their > > thoughts on this change. I don't immediately see any problems with it, > > except possibly the amount of arguments chmod can take? (which may > > actually be a bash limitation) I suppose we know the answer to that > > since all 18k+ files from the mame source worked fine? If that seems to > > be the truth, as in all of those files got hit, and not say 100 or 1000 > > or whatever the command line limit might be, then I'm in favor of this > > change. I'm not really in a position to run some tests to find out, > > though. > > > > If any of that sounds confusing, what I'm imagining is passing 18k+ > > file names to chmod, and I seem to remember that type of thing being an > > issue in the past. I apologize in advance if that isn't true or I'm > > being ignorant on exactly what's happening in the above code. > > I have no objection at all if it's proven to work faster and same > results as the current find code. > > rworkman already mentioned on another thread that he doesn't oppose to > this idea, but let me quote his reply on this : > > "I didn't see any opposition to this, and I don't have any, so if you > want to make a user branch within the template repo and ping me > about it, I'll be more than happy to merge it for 14.2. > > Once that's done, and once the current-wip branch gets merged to > master (after 14.2 beta/rc announcement) and we get moving a bit > heavier there, if you'd like to work up a branch to make the > changes in there, we'll definitely consider it. > > It will probably be worth touching base with us first on that one, > because you'll want to minimize the merge conflicts that we are > creating while you're doing the changes there" > > the current condition is now current-wip branch is merged to master, > Beta 2 has been announced, but no one is up for the move. > > > -- > Willy Sudiarto Raharjo > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From kingbeowulf at gmail.com Sun Mar 13 04:28:06 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 12 Mar 2016 20:28:06 -0800 Subject: [Slackbuilds-users] Error while creating nvidia-legacy340-driver package on -current In-Reply-To: <20160312204239.5727c46a.pessoal@profcavalheiro.com> References: <20160312204239.5727c46a.pessoal@profcavalheiro.com> Message-ID: <56E4EC56.4060708@gmail.com> On 03/12/2016 03:42 PM, Lu?s Fernando Carvalho Cavalheiro wrote: > Dear friend > > Looks like I found by myself how to solve this issue. Reading nvidia-legacy340-driver.SlackBuild script, I found a commentary that stated nvidia-installer isn't needed by this SlackBuild. So, I commented out all lines related to nvidia-installer building and lo!, it worked! I'm sending to you a .patch file to apply to nvidia-legacy340-driver.SlackBuild file. > I've already removed the nvidia-installer section from the scripts. Just need to get it to the SBo admins. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Mar 13 04:37:12 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 13 Mar 2016 11:37:12 +0700 Subject: [Slackbuilds-users] Error while creating nvidia-legacy340-driver package on -current In-Reply-To: <56E4EC56.4060708@gmail.com> References: <20160312204239.5727c46a.pessoal@profcavalheiro.com> <56E4EC56.4060708@gmail.com> Message-ID: <56E4EE78.7070706@slackbuilds.org> > I've already removed the nvidia-installer section from the scripts. Just > need to get it to the SBo admins. you can send the updated tarball or patch to this list -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Mar 13 07:09:31 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 12 Mar 2016 23:09:31 -0800 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. Message-ID: <56E5122B.3090505@gmail.com> Attached is a diff against 14.2 master (based on about 15:00 pm PST USA) for the newest nvidia binary driver 361.28, or you can get the files here: (fast) http://www.koenigcomputers.com/sbo-testing/ (slow) http://www.linuxgalaxy.org/files/sbo-testing/ archive tarballs are in the (slow) link. So far, works on 14.2beta, but there might be a few issues due to the new GLVND libs. I tried to maintain maximum compatibility but may have misplaced/mislinked a few libs. This script is starting to get tedious. Hopefully when libglvnd ( https://github.com/NVIDIA/libglvnd ) is completed, I can simplify it a bit. As always, patch away on any bugs. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-sbo-361.28.diff Type: text/x-patch Size: 23219 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Mar 13 08:26:07 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 09:26:07 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160312221850.1b1104f8.pessoal@profcavalheiro.com> References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org> <56CC47BF.2010105@gmail.com> <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo> <20160312184629.37f4d271@shaggy.doo> <56E4BE30.5020900@slackbuilds.org> <20160312221850.1b1104f8.pessoal@profcavalheiro.com> Message-ID: <56E5241F.6090506@gmail.com> On 13/03/16 02:18, Lu?s Fernando Carvalho Cavalheiro wrote: > I'd stick with find solution. If a source has more files than chmod can handle (or perhaps bash can do, since there may be a limitation on * expansion), it would fail to set desired permissions to files. > > Em 13 de 03 de 2016 ?s 08:11:12T+0700, Willy Sudiarto Raharjo escreveu: > >>>> Are you opposed to this solution? >>>> >>>> find -L . \ >>>> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ >>>> -o -perm 511 \) -print0 | \ >>>> xargs -0 chmod 755 >>>> find -L . \ >>>> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ >>>> -o -perm 440 -o -perm 400 \) -print0 | \ >>>> xargs -0 chmod 644 >>>> >>>> It was proposed by B. Watson here: >>>> >>>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html >>>> >>>> It seems to work the same as the current template, but is just less >>>> resource intensive ... but I don't know for sure. >>> >>> I honestly thought we had agreed to make this change, that another >>> admin (rworkman?) agreed too. I read through that thread just now and I >>> don't see it.. so maybe it happened on IRC, or not at all. >>> >>> Maybe another admin, rworkman or willysr, could put forward their >>> thoughts on this change. I don't immediately see any problems with it, >>> except possibly the amount of arguments chmod can take? (which may >>> actually be a bash limitation) I suppose we know the answer to that >>> since all 18k+ files from the mame source worked fine? If that seems to >>> be the truth, as in all of those files got hit, and not say 100 or 1000 >>> or whatever the command line limit might be, then I'm in favor of this >>> change. I'm not really in a position to run some tests to find out, >>> though. >>> >>> If any of that sounds confusing, what I'm imagining is passing 18k+ >>> file names to chmod, and I seem to remember that type of thing being an >>> issue in the past. I apologize in advance if that isn't true or I'm >>> being ignorant on exactly what's happening in the above code. >> >> I have no objection at all if it's proven to work faster and same >> results as the current find code. >> >> rworkman already mentioned on another thread that he doesn't oppose to >> this idea, but let me quote his reply on this : >> >> "I didn't see any opposition to this, and I don't have any, so if you >> want to make a user branch within the template repo and ping me >> about it, I'll be more than happy to merge it for 14.2. >> >> Once that's done, and once the current-wip branch gets merged to >> master (after 14.2 beta/rc announcement) and we get moving a bit >> heavier there, if you'd like to work up a branch to make the >> changes in there, we'll definitely consider it. >> >> It will probably be worth touching base with us first on that one, >> because you'll want to minimize the merge conflicts that we are >> creating while you're doing the changes there" >> >> the current condition is now current-wip branch is merged to master, >> Beta 2 has been announced, but no one is up for the move. >> >> >> -- >> Willy Sudiarto Raharjo >> > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > So, is the single chmod: chmod -R u+w,go-w,a+rX-st . definitely lost? Why can't we use this solution? -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sun Mar 13 09:00:16 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 10:00:16 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs Message-ID: <56E52C20.7070101@gmail.com> Hi, I'm on Slackware-current and SBo master. I'm trying to build qt5 and it fails with the following error: [6/10258] CXX obj/src/3rdparty/chromium/third_party/protobuf/src/google/protobuf/compiler/protobuf_full_do_not_use.parser.o ninja: build stopped: subcommand failed. Makefile.gyp_run:766: recipe for target 'invoke_ninja' failed make[4]: *** [invoke_ninja] Error 1 make[4]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed make[3]: *** [sub-gyp_run-pro-make_first] Error 2 make[3]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' Makefile:48: recipe for target 'sub-core-make_first' failed make[2]: *** [sub-core-make_first] Error 2 make[2]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src' Makefile:44: recipe for target 'sub-src-make_first' failed make[1]: *** [sub-src-make_first] Error 2 make[1]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine' Makefile:803: recipe for target 'module-qtwebengine-make_first' failed make: *** [module-qtwebengine-make_first] Error 2 make: *** Waiting for unfinished jobs.... Please note that it's most certainly not the exact place where the build failed for the first time, as I tried single job make in the leftover source tree. Single job make seems to resume the build (it's ongoing at the moment). Any ideas on what might be the problem? It looks like ninja is only used for the build of chromium, but I might be wrong on that. -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Sun Mar 13 09:09:25 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 13 Mar 2016 10:09:25 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E52C20.7070101@gmail.com> References: <56E52C20.7070101@gmail.com> Message-ID: 2016-03-13 10:00 GMT+01:00 Andrzej Telszewski : > Hi, > > I'm on Slackware-current and SBo master. > > I'm trying to build qt5 and it fails with the following error: > > [6/10258] CXX > obj/src/3rdparty/chromium/third_party/protobuf/src/google/protobuf/compiler/protobuf_full_do_not_use.parser.o > ninja: build stopped: subcommand failed. > Makefile.gyp_run:766: recipe for target 'invoke_ninja' failed > make[4]: *** [invoke_ninja] Error 1 > make[4]: Leaving directory > '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' > Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed > make[3]: *** [sub-gyp_run-pro-make_first] Error 2 > make[3]: Leaving directory > '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' > Makefile:48: recipe for target 'sub-core-make_first' failed > make[2]: *** [sub-core-make_first] Error 2 > make[2]: Leaving directory > '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src' > Makefile:44: recipe for target 'sub-src-make_first' failed > make[1]: *** [sub-src-make_first] Error 2 > make[1]: Leaving directory > '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine' > Makefile:803: recipe for target 'module-qtwebengine-make_first' failed > make: *** [module-qtwebengine-make_first] Error 2 > make: *** Waiting for unfinished jobs.... > > Please note that it's most certainly not the exact place where the build > failed for the first time, as I tried single job make in the leftover source > tree. > > Single job make seems to resume the build (it's ongoing at the moment). > > Any ideas on what might be the problem? > > It looks like ninja is only used for the build of chromium, but I might be > wrong on that. hi Andrzej, I don't know what's happening there but, FYI, it seems I am able to build qt5 with -j23 here so I'm not sure if that is related... Matteo From matteo.bernardini at gmail.com Sun Mar 13 09:15:27 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 13 Mar 2016 10:15:27 +0100 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: <56E5122B.3090505@gmail.com> References: <56E5122B.3090505@gmail.com> Message-ID: 2016-03-13 8:09 GMT+01:00 King Beowulf : > Attached is a diff against 14.2 master (based on about 15:00 pm PST USA) > for the newest nvidia binary driver 361.28, or you can get the files here: > > (fast) http://www.koenigcomputers.com/sbo-testing/ > (slow) http://www.linuxgalaxy.org/files/sbo-testing/ > > archive tarballs are in the (slow) link. So far, works on 14.2beta, but > there might be a few issues due to the new GLVND libs. I tried to > maintain maximum compatibility but may have misplaced/mislinked a few > libs. This script is starting to get tedious. Hopefully when libglvnd > ( https://github.com/NVIDIA/libglvnd ) is completed, I can simplify it a > bit. > > As always, patch away on any bugs. hi Edward, thanks a lot for your work on this! while trying to install nvidia-driver I spotted just a small typo here (should be $PKG/usr/lib/) install -m 755 32/libGLdispatch.so.0 $PKG/usr/lib$/ I'll keep testing it on my laptop. Matteo From matteo.bernardini at gmail.com Sun Mar 13 09:27:47 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 13 Mar 2016 10:27:47 +0100 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: References: <56E5122B.3090505@gmail.com> Message-ID: 2016-03-13 10:15 GMT+01:00 Matteo Bernardini : > I'll keep testing it on my laptop. not really sure if it's something wrong here but when running ldconfig I got this output: ldconfig: /usr/lib64/libGLESv1_CM.so.1 is not a symbolic link ldconfig: /usr/lib64/libEGL.so.1 is not a symbolic link ldconfig: /usr/lib64/libGLESv2.so.2 is not a symbolic link ldconfig: /usr/lib/libGLESv1_CM.so.1 is not a symbolic link ldconfig: /usr/lib/libGLESv2.so.2 is not a symbolic link ldconfig: /usr/lib/libEGL.so.1 is not a symbolic link http://pastebin.com/Xd0uauRD I'll try to investigate further (hope I can do it this afternoon). Matteo From kingbeowulf at gmail.com Sun Mar 13 09:37:28 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 13 Mar 2016 01:37:28 -0800 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: References: <56E5122B.3090505@gmail.com> Message-ID: <56E534D8.1010905@gmail.com> On 03/13/2016 01:15 AM, Matteo Bernardini wrote: > 2016-03-13 8:09 GMT+01:00 King Beowulf : >> Attached is a diff against 14.2 master (based on about 15:00 pm PST USA) >> for the newest nvidia binary driver 361.28, or you can get the files here: >> >> (fast) http://www.koenigcomputers.com/sbo-testing/ >> (slow) http://www.linuxgalaxy.org/files/sbo-testing/ >> >> archive tarballs are in the (slow) link. So far, works on 14.2beta, but >> there might be a few issues due to the new GLVND libs. I tried to >> maintain maximum compatibility but may have misplaced/mislinked a few >> libs. This script is starting to get tedious. Hopefully when libglvnd >> ( https://github.com/NVIDIA/libglvnd ) is completed, I can simplify it a >> bit. >> >> As always, patch away on any bugs. > > hi Edward, > > thanks a lot for your work on this! > > while trying to install nvidia-driver I spotted just a small typo here > (should be $PKG/usr/lib/) > > install -m 755 32/libGLdispatch.so.0 $PKG/usr/lib$/ > > I'll keep testing it on my laptop. > > Matteo Good eye! refreshed link contents with fix. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Mar 13 09:52:59 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 13 Mar 2016 01:52:59 -0800 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: References: <56E5122B.3090505@gmail.com> Message-ID: On Sunday, March 13, 2016, Matteo Bernardini wrote: > 2016-03-13 10:15 GMT+01:00 Matteo Bernardini >: > > I'll keep testing it on my laptop. > > not really sure if it's something wrong here but when running ldconfig > I got this output: > > ldconfig: /usr/lib64/libGLESv1_CM.so.1 is not a symbolic link > > ldconfig: /usr/lib64/libEGL.so.1 is not a symbolic link > > ldconfig: /usr/lib64/libGLESv2.so.2 is not a symbolic link > > ldconfig: /usr/lib/libGLESv1_CM.so.1 is not a symbolic link > > ldconfig: /usr/lib/libGLESv2.so.2 is not a symbolic link > > ldconfig: /usr/lib/libEGL.so.1 is not a symbolic link > > http://pastebin.com/Xd0uauRD > > I'll try to investigate further (hope I can do it this afternoon). > > Matteo > ____________________________________ > Just noticed that as well. Considering its 1:52am, I'm going to sleep on it.... -Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sun Mar 13 10:09:59 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 11:09:59 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> Message-ID: <56E53C77.10504@gmail.com> On 13/03/16 10:09, Matteo Bernardini wrote: > 2016-03-13 10:00 GMT+01:00 Andrzej Telszewski : >> Hi, >> >> I'm on Slackware-current and SBo master. >> >> I'm trying to build qt5 and it fails with the following error: >> >> [6/10258] CXX >> obj/src/3rdparty/chromium/third_party/protobuf/src/google/protobuf/compiler/protobuf_full_do_not_use.parser.o >> ninja: build stopped: subcommand failed. >> Makefile.gyp_run:766: recipe for target 'invoke_ninja' failed >> make[4]: *** [invoke_ninja] Error 1 >> make[4]: Leaving directory >> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' >> Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed >> make[3]: *** [sub-gyp_run-pro-make_first] Error 2 >> make[3]: Leaving directory >> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' >> Makefile:48: recipe for target 'sub-core-make_first' failed >> make[2]: *** [sub-core-make_first] Error 2 >> make[2]: Leaving directory >> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src' >> Makefile:44: recipe for target 'sub-src-make_first' failed >> make[1]: *** [sub-src-make_first] Error 2 >> make[1]: Leaving directory >> '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine' >> Makefile:803: recipe for target 'module-qtwebengine-make_first' failed >> make: *** [module-qtwebengine-make_first] Error 2 >> make: *** Waiting for unfinished jobs.... >> >> Please note that it's most certainly not the exact place where the build >> failed for the first time, as I tried single job make in the leftover source >> tree. >> >> Single job make seems to resume the build (it's ongoing at the moment). >> >> Any ideas on what might be the problem? >> >> It looks like ninja is only used for the build of chromium, but I might be >> wrong on that. > > hi Andrzej, > > I don't know what's happening there but, FYI, it seems I am able to > build qt5 with -j23 here so I'm not sure if that is related... > > Matteo Well, for me, the RESUMED build fails with the single job too, now with the following error: ninja: Entering directory `/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core/Release' [6/10227] CC obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o FAILED: /usr/bin/gcc -MMD -MF obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o.d -DV8_DEPRECATION_WARNINGS -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC -DCHROMIUM_BUILD -DTOOLKIT_VIEWS=1 -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 -DENABLE_ONE_CLICK_SIGNIN -DENABLE_PRE_SYNC_BACKUP -DUSE_XI2_MT=2 -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DENABLE_PEPPER_CDMS -DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DUSE_UDEV -DDONT_EMBED_BUILD_METADATA -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1 -DCLD_VERSION=2 -DCLD2_DATA_SOURCE=static -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_MANAGED_USERS=1 -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 -DENABLE_LOAD_COMPLETION_HACKS=1 -DNO_PKCS11_BYPASS -DNSS_ENABLE_ECC -DUSE_UTIL_DIRECTLY -DUSE_LIBPCI=1 -DUSE_GLIB=1 -DUSE_NSS=1 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Igen -I/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/bodge -I/usr/include/libdrm -fstack-protector --param=ssp-buffer-size=4 -pthread -fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC -Wno-unused-local-typedefs -I/usr/include/nss -I/usr/include/nspr -Wno-format -Wno-unused-result -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -funwind-tables -O2 -fPIC -c /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c -o obj/src/3rdparty/chromium/net/third_party/nss/ssl/libssl.ssl3con.o /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c: In function ?ssl3_ChaCha20Poly1305?: /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15: error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member named ?pIv? aeadParams.pIv = (unsigned char *) additionalData; ^ /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15: error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member named ?ulIvLen? aeadParams.ulIvLen = 8; ^ [6/10227] RULE net_derived_sources: dafsa_7d6ccdce6c873144fc2b417bd53e3eea base/registry_controlled_domains/effective_tld_names.gperf ninja: build stopped: subcommand failed. Makefile.gyp_run:766: recipe for target 'invoke_ninja' failed make[4]: *** [invoke_ninja] Error 1 make[4]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' Makefile:63: recipe for target 'sub-gyp_run-pro-make_first' failed make[3]: *** [sub-gyp_run-pro-make_first] Error 2 make[3]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/core' Makefile:48: recipe for target 'sub-core-make_first' failed make[2]: *** [sub-core-make_first] Error 2 make[2]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src' Makefile:44: recipe for target 'sub-src-make_first' failed make[1]: *** [sub-src-make_first] Error 2 make[1]: Leaving directory '/home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine' Makefile:803: recipe for target 'module-qtwebengine-make_first' failed make: *** [module-qtwebengine-make_first] Error 2 Any suggestions on how should I try to build again? What I have now is: export JOBS=$(nproc) export NUMJOBS="-j${JOBS}" export MAKEFLAGS="$NUMJOBS" for specifying the number of jobs and: DOCS=yes EXAMPLES=yes and optional deps: - libxkbcommon - freetds - OpenAL - libwebp - wayland > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sun Mar 13 10:12:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 13 Mar 2016 17:12:53 +0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E53C77.10504@gmail.com> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> Message-ID: <56E53D25.6000801@slackbuilds.org> > Well, for me, the RESUMED build fails with the single job too, now with > the following error: best not to resume a broken build please restart the whole process as i just built Qt 5.5.1 yesterday and it went fine -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Mar 13 10:18:47 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 11:18:47 +0100 Subject: [Slackbuilds-users] fpm2 patches Message-ID: <56E53E87.7030801@gmail.com> Hi, I know that as a general rule, we don't patch and keep upstream source intact, but maybe fpm2 could be patched with the two patches I kept hidden for myself for quite some time? They are written by me. fpm2 seems to be not developed since ~2012. -- Best regards, Andrzej Telszewski -------------- next part -------------- A non-text attachment was scrubbed... Name: 01-preserve_column_width.patch Type: text/x-patch Size: 562 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 02-handle-unix-signal.patch Type: text/x-patch Size: 6978 bytes Desc: not available URL: From atelszewski at gmail.com Sun Mar 13 10:21:52 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 11:21:52 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E53D25.6000801@slackbuilds.org> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> Message-ID: <56E53F40.5060102@gmail.com> On 13/03/16 11:12, Willy Sudiarto Raharjo wrote: >> Well, for me, the RESUMED build fails with the single job too, now with >> the following error: > > best not to resume a broken build > please restart the whole process as i just built Qt 5.5.1 yesterday and > it went fine > Have you looked at my "build environment"?: export JOBS=$(nproc) export NUMJOBS="-j${JOBS}" export MAKEFLAGS="$NUMJOBS" DOCS=yes EXAMPLES=yes optional deps: - libxkbcommon - freetds - OpenAL - libwebp - wayland Is yours the same? > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski From pessoal at profcavalheiro.com Sun Mar 13 10:57:11 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sun, 13 Mar 2016 07:57:11 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E5241F.6090506@gmail.com> References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org> <56CC47BF.2010105@gmail.com> <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo> <20160312184629.37f4d271@shaggy.doo> <56E4BE30.5020900@slackbuilds.org> <20160312221850.1b1104f8.pessoal@profcavalheiro.com> <56E5241F.6090506@gmail.com> Message-ID: <20160313075711.709a18c9.pessoal@profcavalheiro.com> Let's suppose a source with a very huge number of files on it, with a very deep directory structure. If if goes bigger than bash expansion of maximum command line size chmod would fail and leave some files with unchanged permissions. I don't understand, through, why the find + xargs approach. What happened to -execdir, simpler than that? find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -execdir 755 {} \; find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -execdir {} \; Em 13 de 03 de 2016 ?s 09:26:07T+0100, Andrzej Telszewski escreveu: > On 13/03/16 02:18, Lu?s Fernando Carvalho Cavalheiro wrote: > > I'd stick with find solution. If a source has more files than chmod can handle (or perhaps bash can do, since there may be a limitation on * expansion), it would fail to set desired permissions to files. > > > > Em 13 de 03 de 2016 ?s 08:11:12T+0700, Willy Sudiarto Raharjo escreveu: > > > >>>> Are you opposed to this solution? > >>>> > >>>> find -L . \ > >>>> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > >>>> -o -perm 511 \) -print0 | \ > >>>> xargs -0 chmod 755 > >>>> find -L . \ > >>>> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > >>>> -o -perm 440 -o -perm 400 \) -print0 | \ > >>>> xargs -0 chmod 644 > >>>> > >>>> It was proposed by B. Watson here: > >>>> > >>>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html > >>>> > >>>> It seems to work the same as the current template, but is just less > >>>> resource intensive ... but I don't know for sure. > >>> > >>> I honestly thought we had agreed to make this change, that another > >>> admin (rworkman?) agreed too. I read through that thread just now and I > >>> don't see it.. so maybe it happened on IRC, or not at all. > >>> > >>> Maybe another admin, rworkman or willysr, could put forward their > >>> thoughts on this change. I don't immediately see any problems with it, > >>> except possibly the amount of arguments chmod can take? (which may > >>> actually be a bash limitation) I suppose we know the answer to that > >>> since all 18k+ files from the mame source worked fine? If that seems to > >>> be the truth, as in all of those files got hit, and not say 100 or 1000 > >>> or whatever the command line limit might be, then I'm in favor of this > >>> change. I'm not really in a position to run some tests to find out, > >>> though. > >>> > >>> If any of that sounds confusing, what I'm imagining is passing 18k+ > >>> file names to chmod, and I seem to remember that type of thing being an > >>> issue in the past. I apologize in advance if that isn't true or I'm > >>> being ignorant on exactly what's happening in the above code. > >> > >> I have no objection at all if it's proven to work faster and same > >> results as the current find code. > >> > >> rworkman already mentioned on another thread that he doesn't oppose to > >> this idea, but let me quote his reply on this : > >> > >> "I didn't see any opposition to this, and I don't have any, so if you > >> want to make a user branch within the template repo and ping me > >> about it, I'll be more than happy to merge it for 14.2. > >> > >> Once that's done, and once the current-wip branch gets merged to > >> master (after 14.2 beta/rc announcement) and we get moving a bit > >> heavier there, if you'd like to work up a branch to make the > >> changes in there, we'll definitely consider it. > >> > >> It will probably be worth touching base with us first on that one, > >> because you'll want to minimize the merge conflicts that we are > >> creating while you're doing the changes there" > >> > >> the current condition is now current-wip branch is merged to master, > >> Beta 2 has been announced, but no one is up for the move. > >> > >> > >> -- > >> Willy Sudiarto Raharjo > >> > > > > > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > So, is the single chmod: > chmod -R u+w,go-w,a+rX-st . > > definitely lost? > > Why can't we use this solution? > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From atelszewski at gmail.com Sun Mar 13 12:18:24 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 13:18:24 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E53D25.6000801@slackbuilds.org> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> Message-ID: <56E55A90.70104@gmail.com> On 13/03/16 11:12, Willy Sudiarto Raharjo wrote: >> Well, for me, the RESUMED build fails with the single job too, now with >> the following error: > > best not to resume a broken build > please restart the whole process as i just built Qt 5.5.1 yesterday and > it went fine > Are you guys up to date with the Thu Mar 10 02:46:49 UTC 2016 -current update? This update has updated mozilla-nss package. And now, if I remove mozilla-nss package, the RESUMED qt5 build fails in a different place, which leads me to thinking that mozilla-nss is used for qt5 build. And now, the previous build of qt5 fails with: /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15: error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member named ?pIv? aeadParams.pIv = (unsigned char *) additionalData; ^ /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15: error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member named ?ulIvLen? aeadParams.ulIvLen = 8; ^ which would be correct, if the SYSTEM wide header was used, that is: /usr/include/nss/pkcs11n.h because structure defined there in: typedef struct CK_NSS_AEAD_PARAMS { CK_BYTE_PTR pNonce; CK_ULONG ulNonceLen; CK_BYTE_PTR pAAD; CK_ULONG ulAADLen; CK_ULONG ulTagLen; } CK_NSS_AEAD_PARAMS; actually does not have pIv and ulIvLen fields. And I'm convinced that system header is used, because of: -I/usr/include/nss being defined when the compiler is invoked. There is this patch: qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/patches/chacha20poly1305.patch which adds the correct structure, that is: typedef struct CK_NSS_AEAD_PARAMS { CK_BYTE_PTR pIv; /* This is the nonce. */ CK_ULONG ulIvLen; CK_BYTE_PTR pAAD; CK_ULONG ulAADLen; CK_ULONG ulTagLen; } CK_NSS_AEAD_PARAMS; but I'm not sure if all of this is correctly taken into account, because if you look at: qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:45 then you have: #ifndef CKM_NSS_CHACHA20_POLY1305 #define CKM_NSS_CHACHA20_POLY1305 (CKM_NSS + 26) typedef struct CK_NSS_AEAD_PARAMS { CK_BYTE_PTR pIv; /* This is the nonce. */ CK_ULONG ulIvLen; CK_BYTE_PTR pAAD; CK_ULONG ulAADLen; CK_ULONG ulTagLen; } CK_NSS_AEAD_PARAMS; #endif so if CKM_NSS_CHACHA20_POLY1305 is already defined, then this correct struct is not taken into account. And CKM_NSS_CHACHA20_POLY1305 is defined outside, if the system headers are being used: qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c: includes: /usr/include/nss/cert.h which includes: /usr/include/nss/certt.h which includes: /usr/include/nss/pkcs11t.h which includes: /usr/include/nss/pkcs11n.h which contains faulty struct: typedef struct CK_NSS_AEAD_PARAMS { CK_BYTE_PTR pNonce; CK_ULONG ulNonceLen; CK_BYTE_PTR pAAD; CK_ULONG ulAADLen; CK_ULONG ulTagLen; } CK_NSS_AEAD_PARAMS; and the definition of CKM_NSS_CHACHA20_POLY1305. And it looks like CKM_NSS_CHACHA20_POLY1305 was not defined in the previous mozilla-nss package. I'm not sure which version it was, but if it was 3.20.1, the I cannot find CKM_NSS_CHACHA20_POLY1305 in the source. That would mean that qt5 should build fine with mozilla-nss-3.20.1, but will fail with mozilla-nss-3.23, which is actually happening to me. I hope I expressed myself clearly ;) Any ideas? -- Best regards, Andrzej Telszewski From erik at slackbuilds.org Sun Mar 13 15:05:49 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 13 Mar 2016 10:05:49 -0500 Subject: [Slackbuilds-users] fpm2 patches In-Reply-To: <56E53E87.7030801@gmail.com> References: <56E53E87.7030801@gmail.com> Message-ID: <20160313100549.6d5926f7@shaggy.doo> On Sun, 13 Mar 2016 11:18:47 +0100 Andrzej Telszewski wrote: > Hi, > > I know that as a general rule, we don't patch and keep upstream > source intact, but maybe fpm2 could be patched with the two patches I > kept hidden for myself for quite some time? They are written by me. > > fpm2 seems to be not developed since ~2012. > This is fine with me, if you want to take over maintenance. I switched to keepassx some time ago. Send a patch for the SlackBuild and info, and I'll toss it in git. -- Erik From johannes at schoepfer.info Sun Mar 13 14:34:25 2016 From: johannes at schoepfer.info (=?ISO-8859-1?Q?Johannes_Sch=F6pfer?=) Date: Sun, 13 Mar 2016 15:34:25 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc Message-ID: It would be helpful If someone could name a single reallife example, where the chmod approach fails. FranzenAm 13.03.2016 2:18 vorm. schrieb Lu?s Fernando Carvalho Cavalheiro : > > I'd stick with find solution. If a source has more files than chmod can handle (or perhaps bash can do, since there may be a limitation on * expansion), it would fail to set desired permissions to files. > > Em 13 de 03 de 2016 ?s 08:11:12T+0700, Willy Sudiarto Raharjo escreveu: > > > >> Are you opposed to this solution? > > >> > > >> find -L . \ > > >>? \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > > >>?? -o -perm 511 \) -print0 | \ > > >>?? xargs -0 chmod 755 > > >> find -L . \ > > >>? \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > > >>?? -o -perm 440 -o -perm 400 \) -print0 | \ > > >>?? xargs -0 chmod 644 > > >> > > >> It was proposed by B. Watson here: > > >> > > >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html > > >> > > >> It seems to work the same as the current template, but is just less > > >> resource intensive ... but I don't know for sure.? > > > > > > I honestly thought we had agreed to make this change, that another > > > admin (rworkman?) agreed too. I read through that thread just now and I > > > don't see it.. so maybe it happened on IRC, or not at all. > > > > > > Maybe another admin, rworkman or willysr, could put forward their > > > thoughts on this change. I don't immediately see any problems with it, > > > except possibly the amount of arguments chmod can take? (which may > > > actually be a bash limitation) I suppose we know the answer to that > > > since all 18k+ files from the mame source worked fine? If that seems to > > > be the truth, as in all of those files got hit, and not say 100 or 1000 > > > or whatever the command line limit might be, then I'm in favor of this > > > change. I'm not really in a position to run some tests to find out, > > > though. > > > > > > If any of that sounds confusing, what I'm imagining is passing 18k+ > > > file names to chmod, and I seem to remember that type of thing being an > > > issue in the past. I apologize in advance if that isn't true or I'm > > > being ignorant on exactly what's happening in the above code.? > > > > I have no objection at all if it's proven to work faster and same > > results as the current find code. > > > > rworkman already mentioned on another thread that he doesn't oppose to > > this idea, but let me quote his reply on this : > > > > "I didn't see any opposition to this, and I don't have any, so if you > > want to make a user branch within the template repo and ping me > > about it, I'll be more than happy to merge it for 14.2. > > > > Once that's done, and once the current-wip branch gets merged to > > master (after 14.2 beta/rc announcement) and we get moving a bit > > heavier there, if you'd like to work up a branch to make the > > changes in there, we'll definitely consider it. > > > > It will probably be worth touching base with us first on that one, > > because you'll want to minimize the merge conflicts that we are > > creating while you're doing the changes there" > > > > the current condition is now current-wip branch is merged to master, > > Beta 2 has been announced, but no one is up for the move. > > > > > > -- > > Willy Sudiarto Raharjo > > > > > -- > 93 93/93 > Lu?s Fernando Carvalho Cavalheiro > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From erik at slackbuilds.org Sun Mar 13 15:23:27 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 13 Mar 2016 10:23:27 -0500 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> Message-ID: <20160313102327.1773f1d9@shaggy.doo> On Sun, 13 Mar 2016 15:34:25 +0100 Johannes Sch?pfer wrote: > It would be helpful If someone could name a single reallife example, > where the chmod approach fails. It changes permissions of 700 to 755, which is something the 'find' lines don't do. The merits and circumstances behind this, or my choice of 700 as an example, do not matter and do not deserve debate. The fact is, it is undesired behavior. -- Erik From atelszewski at gmail.com Sun Mar 13 15:24:17 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 16:24:17 +0100 Subject: [Slackbuilds-users] fpm2 patches In-Reply-To: <20160313100549.6d5926f7@shaggy.doo> References: <56E53E87.7030801@gmail.com> <20160313100549.6d5926f7@shaggy.doo> Message-ID: <56E58621.4080404@gmail.com> On 13/03/16 16:05, Erik Hanson wrote: > On Sun, 13 Mar 2016 11:18:47 +0100 > Andrzej Telszewski wrote: > >> Hi, >> >> I know that as a general rule, we don't patch and keep upstream >> source intact, but maybe fpm2 could be patched with the two patches I >> kept hidden for myself for quite some time? They are written by me. >> >> fpm2 seems to be not developed since ~2012. >> > > This is fine with me, if you want to take over maintenance. I switched > to keepassx some time ago. Send a patch for the SlackBuild and info, > and I'll toss it in git. > What I was worried about, was that, SBo would not accept the patches. If you ensure me that the patches are accepted, then: - I can take over fpm2 maintenance, no problem, - we don't have to hurry, I would update the SlackBuild some time in the future, when the submission is re-enabled That means you (@Erik) don't have to be involved any more. Well, either way, if you want to cease the maintenance of fpm2, I'll take it, as I'm active user of it. -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sun Mar 13 15:28:36 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 16:28:36 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160313102327.1773f1d9@shaggy.doo> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> Message-ID: <56E58724.30805@gmail.com> On 13/03/16 16:23, Erik Hanson wrote: > On Sun, 13 Mar 2016 15:34:25 +0100 > Johannes Sch?pfer wrote: > >> It would be helpful If someone could name a single reallife example, >> where the chmod approach fails. > > It changes permissions of 700 to 755, which is something the 'find' > lines don't do. The merits and circumstances behind this, or my choice > of 700 as an example, do not matter and do not deserve debate. The fact > is, it is undesired behavior. > > I'd say it shouldn't be a problem if we change all the permissions to 755/644. It should be the job of _make install_ (or whatever else) to ensure the correct permissions of sensitive files. Or am I wrong? ;) -- Best regards, Andrzej Telszewski From pessoal at profcavalheiro.com Sun Mar 13 15:35:09 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sun, 13 Mar 2016 12:35:09 -0300 Subject: [Slackbuilds-users] fpm2 patches In-Reply-To: <20160313100549.6d5926f7@shaggy.doo> References: <56E53E87.7030801@gmail.com> <20160313100549.6d5926f7@shaggy.doo> Message-ID: <20160313123509.51e3199b.pessoal@profcavalheiro.com> Plus consider to fork original code and maintain it by yourself. Em 13 de 03 de 2016 ?s 10:05:49T-0500, Erik Hanson escreveu: > On Sun, 13 Mar 2016 11:18:47 +0100 > Andrzej Telszewski wrote: > > > Hi, > > > > I know that as a general rule, we don't patch and keep upstream > > source intact, but maybe fpm2 could be patched with the two patches I > > kept hidden for myself for quite some time? They are written by me. > > > > fpm2 seems to be not developed since ~2012. > > > > This is fine with me, if you want to take over maintenance. I switched > to keepassx some time ago. Send a patch for the SlackBuild and info, > and I'll toss it in git. > > -- > Erik > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From atelszewski at gmail.com Sun Mar 13 15:53:57 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 16:53:57 +0100 Subject: [Slackbuilds-users] fpm2 patches In-Reply-To: <20160313123509.51e3199b.pessoal@profcavalheiro.com> References: <56E53E87.7030801@gmail.com> <20160313100549.6d5926f7@shaggy.doo> <20160313123509.51e3199b.pessoal@profcavalheiro.com> Message-ID: <56E58D15.3040302@gmail.com> On 13/03/16 16:35, Lu?s Fernando Carvalho Cavalheiro wrote: > Plus consider to fork original code and maintain it by yourself. > I'm already thinking about that, but if I decided to do so, I would rewrite the application using Qt. But it's a distant future. I keep using FPM2 because it suits my needs almost exactly and does not get in the way. > Em 13 de 03 de 2016 ?s 10:05:49T-0500, Erik Hanson escreveu: > >> On Sun, 13 Mar 2016 11:18:47 +0100 >> Andrzej Telszewski wrote: >> >>> Hi, >>> >>> I know that as a general rule, we don't patch and keep upstream >>> source intact, but maybe fpm2 could be patched with the two patches I >>> kept hidden for myself for quite some time? They are written by me. >>> >>> fpm2 seems to be not developed since ~2012. >>> >> >> This is fine with me, if you want to take over maintenance. I switched >> to keepassx some time ago. Send a patch for the SlackBuild and info, >> and I'll toss it in git. >> >> -- >> Erik >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski From erik at slackbuilds.org Sun Mar 13 16:03:13 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 13 Mar 2016 11:03:13 -0500 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E58724.30805@gmail.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> Message-ID: <20160313110313.0322fbf9@shaggy.doo> On Sun, 13 Mar 2016 16:28:36 +0100 Andrzej Telszewski wrote: > On 13/03/16 16:23, Erik Hanson wrote: > > On Sun, 13 Mar 2016 15:34:25 +0100 > > Johannes Sch?pfer wrote: > > > >> It would be helpful If someone could name a single reallife > >> example, where the chmod approach fails. > > > > It changes permissions of 700 to 755, which is something the 'find' > > lines don't do. The merits and circumstances behind this, or my > > choice of 700 as an example, do not matter and do not deserve > > debate. The fact is, it is undesired behavior. > > > > > > I'd say it shouldn't be a problem if we change all the permissions to > 755/644. We shouldn't assume to know why developers do what they do, and they may have some very specific reasons behind shipping some files with certain permissions. > It should be the job of _make install_ (or whatever else) to ensure > the correct permissions of sensitive files. > > Or am I wrong? ;) They may be build time requirements, we don't know. In any case, make install wouldn't be aware that those permissions had been changed, potentially resulting in a broken package. -- Erik From erik at slackbuilds.org Sun Mar 13 16:10:59 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 13 Mar 2016 11:10:59 -0500 Subject: [Slackbuilds-users] fpm2 patches In-Reply-To: <56E58621.4080404@gmail.com> References: <56E53E87.7030801@gmail.com> <20160313100549.6d5926f7@shaggy.doo> <56E58621.4080404@gmail.com> Message-ID: <20160313111059.28246128@shaggy.doo> On Sun, 13 Mar 2016 16:24:17 +0100 Andrzej Telszewski wrote: > On 13/03/16 16:05, Erik Hanson wrote: > > On Sun, 13 Mar 2016 11:18:47 +0100 > > Andrzej Telszewski wrote: > > > >> Hi, > >> > >> I know that as a general rule, we don't patch and keep upstream > >> source intact, but maybe fpm2 could be patched with the two > >> patches I kept hidden for myself for quite some time? They are > >> written by me. > >> > >> fpm2 seems to be not developed since ~2012. > >> > > > > This is fine with me, if you want to take over maintenance. I > > switched to keepassx some time ago. Send a patch for the SlackBuild > > and info, and I'll toss it in git. > > > > What I was worried about, was that, SBo would not accept the patches. > > If you ensure me that the patches are accepted, then: > - I can take over fpm2 maintenance, no problem, > - we don't have to hurry, I would update the SlackBuild some time in > the future, when the submission is re-enabled > > That means you (@Erik) don't have to be involved any more. > Well, either way, if you want to cease the maintenance of fpm2, I'll > take it, as I'm active user of it. > We certainly allow these type of patches, and fpm2 wouldn't be the first in the repo to include this sort of thing. I would personally accept the patches blindly, since you wrote them. However, I don't have interest in maintaining the fpm2 SlackBuild anymore, so I think it would be better off in the hands of someone who clearly cares about it. You can send patches now, so the maintainer change happens in master (for 14.2) or wait for submissions to open, either is fine. -- Erik From atelszewski at gmail.com Sun Mar 13 16:17:24 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 17:17:24 +0100 Subject: [Slackbuilds-users] fpm2 patches In-Reply-To: <20160313111059.28246128@shaggy.doo> References: <56E53E87.7030801@gmail.com> <20160313100549.6d5926f7@shaggy.doo> <56E58621.4080404@gmail.com> <20160313111059.28246128@shaggy.doo> Message-ID: <56E59294.9060403@gmail.com> On 13/03/16 17:10, Erik Hanson wrote: > On Sun, 13 Mar 2016 16:24:17 +0100 > Andrzej Telszewski wrote: > >> On 13/03/16 16:05, Erik Hanson wrote: >>> On Sun, 13 Mar 2016 11:18:47 +0100 >>> Andrzej Telszewski wrote: >>> >>>> Hi, >>>> >>>> I know that as a general rule, we don't patch and keep upstream >>>> source intact, but maybe fpm2 could be patched with the two >>>> patches I kept hidden for myself for quite some time? They are >>>> written by me. >>>> >>>> fpm2 seems to be not developed since ~2012. >>>> >>> >>> This is fine with me, if you want to take over maintenance. I >>> switched to keepassx some time ago. Send a patch for the SlackBuild >>> and info, and I'll toss it in git. >>> >> >> What I was worried about, was that, SBo would not accept the patches. >> >> If you ensure me that the patches are accepted, then: >> - I can take over fpm2 maintenance, no problem, >> - we don't have to hurry, I would update the SlackBuild some time in >> the future, when the submission is re-enabled >> >> That means you (@Erik) don't have to be involved any more. >> Well, either way, if you want to cease the maintenance of fpm2, I'll >> take it, as I'm active user of it. >> > > We certainly allow these type of patches, and fpm2 wouldn't be the > first in the repo to include this sort of thing. I would personally > accept the patches blindly, since you wrote them. However, I don't have > interest in maintaining the fpm2 SlackBuild anymore, so I think it > would be better off in the hands of someone who clearly cares about it. > > You can send patches now, so the maintainer change happens in master > (for 14.2) or wait for submissions to open, either is fine. > > I'll wait for the submission to be open and then send everything and take over the maintenance. Thanks. -- Best regards, Andrzej Telszewski From baildon.research at googlemail.com Sun Mar 13 17:42:42 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 13 Mar 2016 17:42:42 +0000 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E55A90.70104@gmail.com> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> Message-ID: > /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15: > error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member > named ?pIv? > aeadParams.pIv = (unsigned char *) additionalData; > ^ > /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15: > error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member > named ?ulIvLen? > aeadParams.ulIvLen = 8; > ^ fwiw I'm getting these same errors on a clean build, no optional dependencies, -j3. -D. From atelszewski at gmail.com Sun Mar 13 18:16:18 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 19:16:18 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> Message-ID: <56E5AE72.9060206@gmail.com> On 13/03/16 18:42, David Spencer wrote: >> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15: >> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member >> named ?pIv? >> aeadParams.pIv = (unsigned char *) additionalData; >> ^ >> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15: >> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member >> named ?ulIvLen? >> aeadParams.ulIvLen = 8; >> ^ > > fwiw I'm getting these same errors on a clean build, no optional > dependencies, -j3. > So I think we arrived to the point where we actually have a problem ;) I successfully built qt5 *without* qtwebengine, now I'm building Qt Creator 3.6.0 against it; so far, so good. BTW, maybe it would be useful to add option to build qt5 without qtwebengine? I personally don't need this, but this shortens the overall build time considerably, for those in a hurry. > -D. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski From pessoal at profcavalheiro.com Sun Mar 13 18:18:08 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sun, 13 Mar 2016 15:18:08 -0300 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E5AE72.9060206@gmail.com> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5AE72.9060206@gmail.com> Message-ID: <20160313151808.5e0a5f3a.pessoal@profcavalheiro.com> If qtwebengine isn't a hard dependency, it should be better having a option to build qt5 without it - but letting qtwebengine enabled by default. Em 13 de 03 de 2016 ?s 19:16:18T+0100, Andrzej Telszewski escreveu: > On 13/03/16 18:42, David Spencer wrote: > >> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15: > >> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member > >> named ?pIv? > >> aeadParams.pIv = (unsigned char *) additionalData; > >> ^ > >> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15: > >> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member > >> named ?ulIvLen? > >> aeadParams.ulIvLen = 8; > >> ^ > > > > fwiw I'm getting these same errors on a clean build, no optional > > dependencies, -j3. > > > > So I think we arrived to the point where we actually have a problem ;) > > I successfully built qt5 *without* qtwebengine, now I'm building Qt > Creator 3.6.0 against it; so far, so good. > > BTW, maybe it would be useful to add option to build qt5 without > qtwebengine? I personally don't need this, but this shortens the overall > build time considerably, for those in a hurry. > > > -D. > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From atelszewski at gmail.com Sun Mar 13 18:23:50 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 19:23:50 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160313110313.0322fbf9@shaggy.doo> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> Message-ID: <56E5B036.7020801@gmail.com> On 13/03/16 17:03, Erik Hanson wrote: > On Sun, 13 Mar 2016 16:28:36 +0100 > Andrzej Telszewski wrote: > >> On 13/03/16 16:23, Erik Hanson wrote: >>> On Sun, 13 Mar 2016 15:34:25 +0100 >>> Johannes Sch?pfer wrote: >>> >>>> It would be helpful If someone could name a single reallife >>>> example, where the chmod approach fails. >>> >>> It changes permissions of 700 to 755, which is something the 'find' >>> lines don't do. The merits and circumstances behind this, or my >>> choice of 700 as an example, do not matter and do not deserve >>> debate. The fact is, it is undesired behavior. >>> >>> >> >> I'd say it shouldn't be a problem if we change all the permissions to >> 755/644. > > We shouldn't assume to know why developers do what they do, and they > may have some very specific reasons behind shipping some files with > certain permissions. > >> It should be the job of _make install_ (or whatever else) to ensure >> the correct permissions of sensitive files. >> >> Or am I wrong? ;) > > They may be build time requirements, we don't know. In any case, make > install wouldn't be aware that those permissions had been changed, > potentially resulting in a broken package. > > You're correct. For the moment I thought what the heck, extracting tatball is going to modify the permissions, but... With the default umask of 022, whatever the user permission bits are, they are going to survive extraction. So something like 700 will definitely stay intact. Although I have yet to come across software that actually depends on that behavior. -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sun Mar 13 18:25:45 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 19:25:45 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <20160313151808.5e0a5f3a.pessoal@profcavalheiro.com> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5AE72.9060206@gmail.com> <20160313151808.5e0a5f3a.pessoal@profcavalheiro.com> Message-ID: <56E5B0A9.8060701@gmail.com> On 13/03/16 19:18, Lu?s Fernando Carvalho Cavalheiro wrote: > If qtwebengine isn't a hard dependency, it should be better having a option to build qt5 without it - but letting qtwebengine enabled by default. > I was able to build qt5 without qtwebengine, and Qt Creator also built and runs fine. So for me it's not that hard dependency ;) > Em 13 de 03 de 2016 ?s 19:16:18T+0100, Andrzej Telszewski escreveu: > >> On 13/03/16 18:42, David Spencer wrote: >>>> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2091:15: >>>> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member >>>> named ?pIv? >>>> aeadParams.pIv = (unsigned char *) additionalData; >>>> ^ >>>> /home/software/slackware/pkg/tmpdir/qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c:2092:15: >>>> error: ?CK_NSS_AEAD_PARAMS {aka struct CK_NSS_AEAD_PARAMS}? has no member >>>> named ?ulIvLen? >>>> aeadParams.ulIvLen = 8; >>>> ^ >>> >>> fwiw I'm getting these same errors on a clean build, no optional >>> dependencies, -j3. >>> >> >> So I think we arrived to the point where we actually have a problem ;) >> >> I successfully built qt5 *without* qtwebengine, now I'm building Qt >> Creator 3.6.0 against it; so far, so good. >> >> BTW, maybe it would be useful to add option to build qt5 without >> qtwebengine? I personally don't need this, but this shortens the overall >> build time considerably, for those in a hurry. >> >>> -D. >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - http://slackbuilds.org/faq/ >>> >> >> >> -- >> Best regards, >> Andrzej Telszewski >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski From pessoal at profcavalheiro.com Sun Mar 13 18:29:32 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sun, 13 Mar 2016 15:29:32 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E5B036.7020801@gmail.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> Message-ID: <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> Well, well... sudo is a example of piece of software (personally I call sudo "piece of cr..") that relies on strange permissions: /etc/sudoers needs to be at 440. Em 13 de 03 de 2016 ?s 19:23:50T+0100, Andrzej Telszewski escreveu: > On 13/03/16 17:03, Erik Hanson wrote: > > On Sun, 13 Mar 2016 16:28:36 +0100 > > Andrzej Telszewski wrote: > > > >> On 13/03/16 16:23, Erik Hanson wrote: > >>> On Sun, 13 Mar 2016 15:34:25 +0100 > >>> Johannes Sch?pfer wrote: > >>> > >>>> It would be helpful If someone could name a single reallife > >>>> example, where the chmod approach fails. > >>> > >>> It changes permissions of 700 to 755, which is something the 'find' > >>> lines don't do. The merits and circumstances behind this, or my > >>> choice of 700 as an example, do not matter and do not deserve > >>> debate. The fact is, it is undesired behavior. > >>> > >>> > >> > >> I'd say it shouldn't be a problem if we change all the permissions to > >> 755/644. > > > > We shouldn't assume to know why developers do what they do, and they > > may have some very specific reasons behind shipping some files with > > certain permissions. > > > >> It should be the job of _make install_ (or whatever else) to ensure > >> the correct permissions of sensitive files. > >> > >> Or am I wrong? ;) > > > > They may be build time requirements, we don't know. In any case, make > > install wouldn't be aware that those permissions had been changed, > > potentially resulting in a broken package. > > > > > > You're correct. For the moment I thought what the heck, extracting > tatball is going to modify the permissions, but... > > With the default umask of 022, whatever the user permission bits are, > they are going to survive extraction. > > So something like 700 will definitely stay intact. > > Although I have yet to come across software that actually depends on > that behavior. > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From atelszewski at gmail.com Sun Mar 13 18:36:52 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 19:36:52 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> Message-ID: <56E5B344.9020402@gmail.com> On 13/03/16 19:29, Lu?s Fernando Carvalho Cavalheiro wrote: > Well, well... sudo is a example of piece of software (personally I call sudo "piece of cr..") that relies on strange permissions: /etc/sudoers needs to be at 440. > But you talk about *already* installed software, which is different situation from the time when the software is being built. > Em 13 de 03 de 2016 ?s 19:23:50T+0100, Andrzej Telszewski escreveu: > >> On 13/03/16 17:03, Erik Hanson wrote: >>> On Sun, 13 Mar 2016 16:28:36 +0100 >>> Andrzej Telszewski wrote: >>> >>>> On 13/03/16 16:23, Erik Hanson wrote: >>>>> On Sun, 13 Mar 2016 15:34:25 +0100 >>>>> Johannes Sch?pfer wrote: >>>>> >>>>>> It would be helpful If someone could name a single reallife >>>>>> example, where the chmod approach fails. >>>>> >>>>> It changes permissions of 700 to 755, which is something the 'find' >>>>> lines don't do. The merits and circumstances behind this, or my >>>>> choice of 700 as an example, do not matter and do not deserve >>>>> debate. The fact is, it is undesired behavior. >>>>> >>>>> >>>> >>>> I'd say it shouldn't be a problem if we change all the permissions to >>>> 755/644. >>> >>> We shouldn't assume to know why developers do what they do, and they >>> may have some very specific reasons behind shipping some files with >>> certain permissions. >>> >>>> It should be the job of _make install_ (or whatever else) to ensure >>>> the correct permissions of sensitive files. >>>> >>>> Or am I wrong? ;) >>> >>> They may be build time requirements, we don't know. In any case, make >>> install wouldn't be aware that those permissions had been changed, >>> potentially resulting in a broken package. >>> >>> >> >> You're correct. For the moment I thought what the heck, extracting >> tatball is going to modify the permissions, but... >> >> With the default umask of 022, whatever the user permission bits are, >> they are going to survive extraction. >> >> So something like 700 will definitely stay intact. >> >> Although I have yet to come across software that actually depends on >> that behavior. >> >> -- >> Best regards, >> Andrzej Telszewski >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski From ryan.q at linux.com Sun Mar 13 18:46:06 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 13 Mar 2016 18:46:06 +0000 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E5B344.9020402@gmail.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> Message-ID: On Sun, Mar 13, 2016 at 11:36 AM Andrzej Telszewski wrote: > On 13/03/16 19:29, Lu?s Fernando Carvalho Cavalheiro wrote: > > Well, well... sudo is a example of piece of software (personally I call > sudo "piece of cr..") that relies on strange permissions: /etc/sudoers > needs to be at 440. > > > > But you talk about *already* installed software, which is different > situation from the time when the software is being built. > How do you think it got installed in the first place? :^) The SlackBuilds we use are analogous to what the main Slackware tree uses. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Sun Mar 13 18:47:27 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 13 Mar 2016 11:47:27 -0700 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: References: <56E5122B.3090505@gmail.com> Message-ID: <56E5B5BF.5070904@gmail.com> On 03/13/2016 01:27 AM, Matteo Bernardini wrote: > 2016-03-13 10:15 GMT+01:00 Matteo Bernardini : >> I'll keep testing it on my laptop. > > not really sure if it's something wrong here but when running ldconfig > I got this output: > > ldconfig: /usr/lib64/libGLESv1_CM.so.1 is not a symbolic link > > ldconfig: /usr/lib64/libEGL.so.1 is not a symbolic link > > ldconfig: /usr/lib64/libGLESv2.so.2 is not a symbolic link > > ldconfig: /usr/lib/libGLESv1_CM.so.1 is not a symbolic link > > ldconfig: /usr/lib/libGLESv2.so.2 is not a symbolic link > > ldconfig: /usr/lib/libEGL.so.1 is not a symbolic link > > http://pastebin.com/Xd0uauRD > > I'll try to investigate further (hope I can do it this afternoon). > > Matteo Very odd. I don't know why ldconfig is complaining. These are the binary libs in the package for support of EGL. In the NVIDIA package: /sources/nvidia/361.28/NVIDIA-Linux-x86_64-361.28/ ... libGLESv1_CM.so.1 libEGL.so.1 libGLESv2.so.2 ... exist as actual files. I used https://devtalk.nvidia.com/default/topic/915640 as a guide to set up the symlinks etc as a guide. I don't have any EGL software to test it though. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Mar 13 19:00:18 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 13 Mar 2016 20:00:18 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> Message-ID: <56E5B8C2.50709@gmail.com> On 13/03/16 19:46, Ryan P.C. McQuen wrote: > > > On Sun, Mar 13, 2016 at 11:36 AM Andrzej Telszewski > > wrote: > > On 13/03/16 19:29, Lu?s Fernando Carvalho Cavalheiro wrote: > > Well, well... sudo is a example of piece of software (personally > I call sudo "piece of cr..") that relies on strange permissions: > /etc/sudoers needs to be at 440. > > > > But you talk about *already* installed software, which is different > situation from the time when the software is being built. > > > > How do you think it got installed in the first place? :^) > The point here is that, permissions of /etc/sudoers could be set after building and just before creating the package. In that case, it would not matter what the permissions of sudoers were during the build stage. And that's the whole point here ;) If all the software were setting correct permissions after building and before packing, we could build with all the permissions set to 700/600 ;) > The SlackBuilds we use are analogous to what the main Slackware tree uses. > Well, that does not mean we cannot do better than Pat :^) But as Erik said before, we cannot be sure about what the software creator meant with setting some file's permission to 700, and it's probably better to just leave it alone. Summary: - *goodbye* beloved chmod one-liner :/ - find to rule them all :/ > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski From pessoal at profcavalheiro.com Sun Mar 13 19:39:18 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Sun, 13 Mar 2016 16:39:18 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E5B8C2.50709@gmail.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> Message-ID: <20160313163918.6cf3cde1.pessoal@profcavalheiro.com> It makes sense, Ryan... Em 13 de 03 de 2016 ?s 20:00:18T+0100, Andrzej Telszewski escreveu: > On 13/03/16 19:46, Ryan P.C. McQuen wrote: > > > > > > On Sun, Mar 13, 2016 at 11:36 AM Andrzej Telszewski > > > wrote: > > > > On 13/03/16 19:29, Lu?s Fernando Carvalho Cavalheiro wrote: > > > Well, well... sudo is a example of piece of software (personally > > I call sudo "piece of cr..") that relies on strange permissions: > > /etc/sudoers needs to be at 440. > > > > > > > But you talk about *already* installed software, which is different > > situation from the time when the software is being built. > > > > > > > > How do you think it got installed in the first place? :^) > > > > The point here is that, permissions of /etc/sudoers could be set after > building and just before creating the package. > > In that case, it would not matter what the permissions of sudoers were > during the build stage. > > And that's the whole point here ;) If all the software were setting > correct permissions after building and before packing, we could build > with all the permissions set to 700/600 ;) > > > The SlackBuilds we use are analogous to what the main Slackware tree uses. > > > > Well, that does not mean we cannot do better than Pat :^) > > But as Erik said before, we cannot be sure about what the software > creator meant with setting some file's permission to 700, and it's > probably better to just leave it alone. > > Summary: > - *goodbye* beloved chmod one-liner :/ > - find to rule them all :/ > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From willysr at slackbuilds.org Sun Mar 13 22:30:15 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 14 Mar 2016 05:30:15 +0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E55A90.70104@gmail.com> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> Message-ID: <56E5E9F7.8010706@slackbuilds.org> > Are you guys up to date with the Thu Mar 10 02:46:49 UTC 2016 -current > update? Yes, my system is up to date with latest current update, but probably since i tested in my desktop, it's also filled with many packages i used so it may affect the build. let me try on a clean VM like i always do -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From eric.b.pratt at gmail.com Mon Mar 14 03:33:28 2016 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Sun, 13 Mar 2016 20:33:28 -0700 Subject: [Slackbuilds-users] Updating slackbuilds Message-ID: I have an update for a slackbuild I maintain (VICE), but the current one is building fine but it is a rather old version of the package. Do I have to wait until 14.2 opens or will submissions re-open before 14.2 for general updates? Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 14 04:05:23 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 14 Mar 2016 11:05:23 +0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: Message-ID: <56E63883.2080604@slackbuilds.org> > I have an update for a slackbuild I maintain (VICE), but the current one is > building fine but it is a rather old version of the package. Do I have to > wait until 14.2 opens or will submissions re-open before 14.2 for general > updates? It's up to you if you want to wait but if you think it needs to be pushed now, please send the tarball update to this list -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From elyk03 at gmail.com Mon Mar 14 04:10:16 2016 From: elyk03 at gmail.com (Kyle Guinn) Date: Sun, 13 Mar 2016 23:10:16 -0500 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160312184629.37f4d271@shaggy.doo> References: <56B3EC7E.5070806@slackbuilds.org> <56B49A1C.1060502@inlv.org> <56CC47BF.2010105@gmail.com> <56CD5A43.5040402@gmail.com> <20160224091418.3f914aa0@shaggy.doo> <20160312184629.37f4d271@shaggy.doo> Message-ID: On 3/12/16, Erik Hanson wrote: > On Sun, 13 Mar 2016 00:23:17 +0000 > "Ryan P.C. McQuen" wrote: > > >> Erik, >> >> Are you opposed to this solution? >> >> find -L . \ >> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ >> -o -perm 511 \) -print0 | \ >> xargs -0 chmod 755 >> find -L . \ >> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ >> -o -perm 440 -o -perm 400 \) -print0 | \ >> xargs -0 chmod 644 >> >> It was proposed by B. Watson here: >> >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-November/015210.html >> >> It seems to work the same as the current template, but is just less >> resource intensive ... but I don't know for sure. > > I honestly thought we had agreed to make this change, that another > admin (rworkman?) agreed too. I read through that thread just now and I > don't see it.. so maybe it happened on IRC, or not at all. > > Maybe another admin, rworkman or willysr, could put forward their > thoughts on this change. I don't immediately see any problems with it, > except possibly the amount of arguments chmod can take? (which may > actually be a bash limitation) I suppose we know the answer to that > since all 18k+ files from the mame source worked fine? If that seems to > be the truth, as in all of those files got hit, and not say 100 or 1000 > or whatever the command line limit might be, then I'm in favor of this > change. I'm not really in a position to run some tests to find out, > though. > > If any of that sounds confusing, what I'm imagining is passing 18k+ > file names to chmod, and I seem to remember that type of thing being an > issue in the past. I apologize in advance if that isn't true or I'm > being ignorant on exactly what's happening in the above code. What I've found in the past is that firing off a new chmod process for each file was the slowest part. The simplest way to fix it is to change '\;' to '+' so you only fire off a few processes; each process receives several filenames instead of just one. Theoretically it should be faster than piping it to xargs since you don't have to set up the pipe and start the xargs process and parse the contents of the pipe. Take a look at "Limits on size of arguments and environment" in the execve man page. Both xargs and '-exec {} +' should be aware of these limits when they start up a new process. I believe they respect ARG_MAX, not sure about any other limits. Any limits in bash shouldn't be involved in this command, and I'd really doubt that chmod has some built-in limit. I'm guessing that if you hit a limit in bash in the past, it was due to file glob expansion. But with that said, I'm still a big proponent of the single-line chmod command. I would guess that only a handful of scripts need to preserve some weird permissions, and if upstream is taking enough care to put those permissions in the tarball, then should we really be trying to sanitize them? -Kyle From eric.b.pratt at gmail.com Mon Mar 14 04:26:52 2016 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Sun, 13 Mar 2016 21:26:52 -0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: <56E63883.2080604@slackbuilds.org> References: <56E63883.2080604@slackbuilds.org> Message-ID: This update isn't critical so it can wait. But when we went from 14.0 to 14.1, the slackbuild was updated by someone other than me and I don't know why or by whom. As long as that isn't going to happen, I'll wait. On Sun, Mar 13, 2016 at 9:05 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I have an update for a slackbuild I maintain (VICE), but the current one > is > > building fine but it is a rather old version of the package. Do I have > to > > wait until 14.2 opens or will submissions re-open before 14.2 for general > > updates? > > It's up to you if you want to wait but if you think it needs to be > pushed now, please send the tarball update to this list > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 14 05:19:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 14 Mar 2016 12:19:53 +0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: <56E63883.2080604@slackbuilds.org> Message-ID: <56E649F9.1050207@slackbuilds.org> > This update isn't critical so it can wait. But when we went from 14.0 to > 14.1, the slackbuild was updated by someone other than me and I don't know > why or by whom. As long as that isn't going to happen, I'll wait. You can check the history here https://slackbuilds.org/cgit/slackbuilds/ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From eric.b.pratt at gmail.com Mon Mar 14 05:59:02 2016 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Sun, 13 Mar 2016 22:59:02 -0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: <56E649F9.1050207@slackbuilds.org> References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> Message-ID: Well, it looks like the same guy did it again in January. I thought only the maintainer could submit updates to the slackbuild. Is that incorrect? Since this appears to be happening, lets just go ahead and commit this update. It eliminates the cumbersome patch files and gets us all the latest bug fixes except for what's in the last release since that release wont build and I haven't investigated why yet. On Sun, Mar 13, 2016 at 10:19 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > This update isn't critical so it can wait. But when we went from 14.0 to > > 14.1, the slackbuild was updated by someone other than me and I don't > know > > why or by whom. As long as that isn't going to happen, I'll wait. > > You can check the history here > https://slackbuilds.org/cgit/slackbuilds/ > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: vice.tar.gz Type: application/x-gzip Size: 8231 bytes Desc: not available URL: From slackbuilds at schoepfer.info Mon Mar 14 06:00:14 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 14 Mar 2016 07:00:14 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E5B8C2.50709@gmail.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> Message-ID: <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> On 2016-03-13 20:00, Andrzej Telszewski wrote: > On 13/03/16 19:46, Ryan P.C. McQuen wrote: >> >> >> On Sun, Mar 13, 2016 at 11:36 AM Andrzej Telszewski >> > wrote: >> >> On 13/03/16 19:29, Lu?s Fernando Carvalho Cavalheiro wrote: >> > Well, well... sudo is a example of piece of software >> (personally >> I call sudo "piece of cr..") that relies on strange permissions: >> /etc/sudoers needs to be at 440. >> > >> >> But you talk about *already* installed software, which is >> different >> situation from the time when the software is being built. >> >> >> >> How do you think it got installed in the first place? :^) >> > > The point here is that, permissions of /etc/sudoers could be set after > building and just before creating the package. > > In that case, it would not matter what the permissions of sudoers were > during the build stage. In the sudo.SlackBuild permissions are set in the Makefile, also after building ... make $NUMJOBS || make || exit 1 make install DESTDIR=$PKG || exit 1 ( cd $PKG/usr/bin chmod 4711 sudo ln -sf sudo sudoedit ... This is NOT an example where the find-lines before the build do rescue the package any better than the chmod-oneliner. From willysr at slackbuilds.org Mon Mar 14 06:02:45 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 14 Mar 2016 13:02:45 +0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> Message-ID: <56E65405.5030300@slackbuilds.org> > Well, it looks like the same guy did it again in January. I thought only > the maintainer could submit updates to the slackbuild. Is that incorrect? > > Since this appears to be happening, lets just go ahead and commit this > update. It eliminates the cumbersome patch files and gets us all the > latest bug fixes except for what's in the last release since that release > wont build and I haven't investigated why yet. It was one of the admin, Matteo (ponce) During development cycle like this, we often update the SlackBuild if it's really needed for several reasons: - Fix a build failure due to changes in Slackware - Not yet updated by maintainer for a long time -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From eric.b.pratt at gmail.com Mon Mar 14 06:31:52 2016 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Sun, 13 Mar 2016 23:31:52 -0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: <56E65405.5030300@slackbuilds.org> References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> <56E65405.5030300@slackbuilds.org> Message-ID: I see. Thanks! On Sun, Mar 13, 2016 at 11:02 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Well, it looks like the same guy did it again in January. I thought only > > the maintainer could submit updates to the slackbuild. Is that > incorrect? > > > > Since this appears to be happening, lets just go ahead and commit this > > update. It eliminates the cumbersome patch files and gets us all the > > latest bug fixes except for what's in the last release since that release > > wont build and I haven't investigated why yet. > > It was one of the admin, Matteo (ponce) > During development cycle like this, we often update the SlackBuild if > it's really needed for several reasons: > - Fix a build failure due to changes in Slackware > - Not yet updated by maintainer for a long time > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon Mar 14 12:10:14 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 14 Mar 2016 13:10:14 +0100 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> <56E65405.5030300@slackbuilds.org> Message-ID: 2016-03-14 7:31 GMT+01:00 Eric Pratt : > I see. Thanks! > > On Sun, Mar 13, 2016 at 11:02 PM, Willy Sudiarto Raharjo > wrote: >> >> > Well, it looks like the same guy did it again in January. I thought >> > only >> > the maintainer could submit updates to the slackbuild. Is that >> > incorrect? >> > >> > Since this appears to be happening, lets just go ahead and commit this >> > update. It eliminates the cumbersome patch files and gets us all the >> > latest bug fixes except for what's in the last release since that >> > release >> > wont build and I haven't investigated why yet. >> >> It was one of the admin, Matteo (ponce) >> During development cycle like this, we often update the SlackBuild if >> it's really needed for several reasons: >> - Fix a build failure due to changes in Slackware >> - Not yet updated by maintainer for a long time Hi Eric, as I am using vice myself I noticed when the build broke in the last 5+ years (compiler, ffmpeg versions, etc.) and took care of fixing it or we had to remove it from the repository. as for the last update it slipped from my personal repository when merging the other fixes for current... I just had a look at your submission and I see you have rebased your modifications on your old script and not what we have in our repository, so I had to fix some things again: - the homepage isn't working anymore, so I switched to the sourceforge one; - I moved the block that defines some variables in the slackbuild lower in it because that's how we have in most of our SlackBuilds: this helps in case we had to do some automated scripting cleanups in our repository, like it often happens (this is effective if we have scripts conforming to the templates); - I added man and info file compression blocks; - as the doc directory from the sources folder is messy and the "make install" already installs a clean one in /usr/lib$LIBDIRSUFFIX/$PRGNAM/doc where it shouldn't be, I opted to move this later in /usr/doc/$PRGNAM-$VERSION and the html stuff in a subdirectory, fixing permissions (executable text files). I attach the diff over your last submission: if it's ok for you I'll commit your submission with these corrections in our git. Matteo P.S. Note that not enabling the bundled ffmpeg implies that recording videos of the emulator running from the menus doesn't work: feel free to look at the script I previously submitted. -------------- next part -------------- diff -Naur vice/slack-desc vice.new/slack-desc --- vice/slack-desc 2013-11-22 20:47:41.000000000 +0100 +++ vice.new/slack-desc 2016-03-14 08:47:56.867459895 +0100 @@ -14,6 +14,6 @@ vice: emulates the C64, the C128, the VIC20, almost all PET models, the vice: PLUS4 and the CBM-II (aka C610). vice: -vice: Homepage: http://www.viceteam.org/ +vice: Homepage: http://vice-emu.sourceforge.net/ vice: vice: diff -Naur vice/vice.SlackBuild vice.new/vice.SlackBuild --- vice/vice.SlackBuild 2016-03-13 20:36:54.000000000 +0100 +++ vice.new/vice.SlackBuild 2016-03-14 10:39:54.749268128 +0100 @@ -27,10 +27,6 @@ VERSION=${VERSION:-2.4.24} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} -CWD=$(pwd) -TMP=${TMP:-/tmp/SBo} -PKG=$TMP/package-$PRGNAM -OUTPUT=${OUTPUT:-/tmp} if [ -z "$ARCH" ]; then case "$( uname -m )" in @@ -40,6 +36,11 @@ esac fi +CWD=$(pwd) +TMP=${TMP:-/tmp/SBo} +PKG=$TMP/package-$PRGNAM +OUTPUT=${OUTPUT:-/tmp} + if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" LIBDIRSUFFIX="" @@ -115,16 +116,26 @@ find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true +find $PKG/usr/man -type f -exec gzip -9 {} \; +for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done + +rm -f $PKG/usr/info/dir +gzip -9 $PKG/usr/info/* + # Install icon and menu entries mkdir -p $PKG/usr/share/{applications,pixmaps} install -D -m 0644 $CWD/config/*.desktop $PKG/usr/share/applications install -D -m 0644 $CWD/config/vice.png $PKG/usr/share/pixmaps -# Copy the original documentation folder to the usual place +# Move the original documentation folder to the usual place +# and create a link to where vice expect it to be mkdir -p $PKG/usr/doc -cp -a doc $PKG/usr/doc/$PRGNAM-$VERSION -find $PKG/usr/doc/$PRGNAM-$VERSION -name "Makefile*" -exec rm -f {} \; -find $PKG/usr/doc/$PRGNAM-$VERSION -name "tex*" -exec rm -f {} \; +mv $PKG/usr/lib$LIBDIRSUFFIX/$PRGNAM/doc $PKG/usr/doc/$PRGNAM-$VERSION +( cd $PKG/usr/doc/$PRGNAM-$VERSION + chmod 644 * + mkdir html + mv *.html *.png *.gif *.jpg *.css html/ ) +( cd $PKG/usr/lib$LIBDIRSUFFIX/$PRGNAM ; ln -s /usr/doc/$PRGNAM-$VERSION doc ) # Copy additional program documentation cp -a AUTHORS ChangeLog COPYING FEEDBACK INSTALL NEWS README \ diff -Naur vice/vice.info vice.new/vice.info --- vice/vice.info 2016-03-12 09:38:43.000000000 +0100 +++ vice.new/vice.info 2016-03-14 08:47:18.978644421 +0100 @@ -1,7 +1,7 @@ PRGNAM="vice" VERSION="2.4.24" -HOMEPAGE="http://www.viceteam.org/" -DOWNLOAD="http://downloads.sourceforge.net/project/vice-emu/development-releases/vice-2.4.24.tar.gz?r=&ts=1457765603&use_mirror=iweb" +HOMEPAGE="http://vice-emu.sourceforge.net" +DOWNLOAD="http://downloads.sourceforge.net/vice-emu/vice-2.4.24.tar.gz" MD5SUM="bd064f09908737951ccc75e734b6720c" DOWNLOAD_x86_64="" MD5SUM_x86_64="" From bryanlharris at gmail.com Mon Mar 14 12:39:47 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Mon, 14 Mar 2016 08:39:47 -0400 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> Message-ID: Why worry so much over something so insignificant? Just do whatever Volkerding does. https://en.wikipedia.org/wiki/Perfect_is_the_enemy_of_good On Mon, Mar 14, 2016 at 2:00 AM, Franzen wrote: > On 2016-03-13 20:00, Andrzej Telszewski wrote: > >> On 13/03/16 19:46, Ryan P.C. McQuen wrote: >> >>> >>> >>> On Sun, Mar 13, 2016 at 11:36 AM Andrzej Telszewski >>> > wrote: >>> >>> On 13/03/16 19:29, Lu?s Fernando Carvalho Cavalheiro wrote: >>> > Well, well... sudo is a example of piece of software (personally >>> I call sudo "piece of cr..") that relies on strange permissions: >>> /etc/sudoers needs to be at 440. >>> > >>> >>> But you talk about *already* installed software, which is different >>> situation from the time when the software is being built. >>> >>> >>> >>> How do you think it got installed in the first place? :^) >>> >>> >> The point here is that, permissions of /etc/sudoers could be set after >> building and just before creating the package. >> >> In that case, it would not matter what the permissions of sudoers were >> during the build stage. >> > > > In the sudo.SlackBuild permissions are set in the Makefile, also > after building ... > > make $NUMJOBS || make || exit 1 > make install DESTDIR=$PKG || exit 1 > > ( cd $PKG/usr/bin > chmod 4711 sudo > ln -sf sudo sudoedit > ... > > > This is NOT an example where the find-lines before the build do rescue the > package any better than the chmod-oneliner. > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From belka at caraus.de Mon Mar 14 13:38:52 2016 From: belka at caraus.de (Eugen Wissner) Date: Mon, 14 Mar 2016 14:38:52 +0100 Subject: [Slackbuilds-users] Keepassx Message-ID: Hello, I've just updated keepassx to 2.0.2 and tested it under current. I don't know if it is ok for the maintainer. I attach a git patch. I can make a pull request if needed. regards Eugene -------------- next part -------------- diff --git a/office/keepassx/keepassx-0.4.3-gcc47.patch b/office/keepassx/keepassx-0.4.3-gcc47.patch deleted file mode 100644 index 9e26e5a..0000000 --- a/office/keepassx/keepassx-0.4.3-gcc47.patch +++ /dev/null @@ -1,12 +0,0 @@ -diff --git a/src/lib/random.cpp b/src/lib/random.cpp -index 1007172..f12dd1c 100644 ---- a/src/lib/random.cpp -+++ b/src/lib/random.cpp -@@ -19,6 +19,7 @@ - ***************************************************************************/ - - #include "random.h" -+#include - - - #if defined(Q_WS_X11) || defined(Q_WS_MAC) diff --git a/office/keepassx/keepassx.SlackBuild b/office/keepassx/keepassx.SlackBuild index 88ee918..97b462b 100644 --- a/office/keepassx/keepassx.SlackBuild +++ b/office/keepassx/keepassx.SlackBuild @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=keepassx -VERSION=${VERSION:-0.4.4} +VERSION=${VERSION:-2.0.2} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} @@ -69,20 +69,20 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; -patch -p1 < $CWD/keepassx-0.4.3-gcc47.patch - -qmake \ - QMAKE_CFLAGS="$SLKCFLAGS" \ - QMAKE_CXXFLAGS="$SLKCFLAGS" +cmake \ + -DMAKE_CFLAGS="$SLKCFLAGS" \ + -DMAKE_CXXFLAGS="$SLKCFLAGS" \ + -DCMAKE_INSTALL_PREFIX=/usr \ + -DCMAKE_BUILD_TYPE=Release make -make install INSTALL_ROOT=$PKG +make install DESTDIR=$PKG find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION -cp -a COPYING INSTALL changelog $PKG/usr/doc/$PRGNAM-$VERSION +cp -a COPYING INSTALL CHANGELOG $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install diff --git a/office/keepassx/keepassx.info b/office/keepassx/keepassx.info index f6d9b69..adb0615 100644 --- a/office/keepassx/keepassx.info +++ b/office/keepassx/keepassx.info @@ -1,8 +1,8 @@ PRGNAM="keepassx" -VERSION="0.4.4" +VERSION="2.0.2" HOMEPAGE="http:///www.keepassx.org/" -DOWNLOAD="https://www.keepassx.org/releases/0.4.4/keepassx-0.4.4.tar.gz" -MD5SUM="6022ffe1e2c59fc6f1a47544417bb0b5" +DOWNLOAD="https://www.keepassx.org/releases/2.0.2/keepassx-2.0.2.tar.gz" +MD5SUM="65d098dff663768911847a1e92d0f01d" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" From matteo.bernardini at gmail.com Mon Mar 14 15:17:12 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 14 Mar 2016 16:17:12 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E5E9F7.8010706@slackbuilds.org> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> Message-ID: 2016-03-13 23:30 GMT+01:00 Willy Sudiarto Raharjo : >> Are you guys up to date with the Thu Mar 10 02:46:49 UTC 2016 -current >> update? > > Yes, my system is up to date with latest current update, but probably > since i tested in my desktop, it's also filled with many packages i used > so it may affect the build. > > let me try on a clean VM like i always do I've tried it also on a clean vm with a single job and it seems this is where it breaks http://pastebin.com/6QcYEQVE From rob0 at slackbuilds.org Mon Mar 14 15:44:46 2016 From: rob0 at slackbuilds.org (Rob McGee) Date: Mon, 14 Mar 2016 10:44:46 -0500 Subject: [Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17 Message-ID: <20160314154446.GV23739@harrier.slackbuilds.org> Robby and I will be doing a hardware upgrade on harrier, the machine which hosts lists.slackbuilds.org, probably on Thursday this week. We're going to try filling it with green beer to see if that will improve performance. If that fails, we'll fill ourselves with green beer and revert harrier to normal (albeit with an upgraded storage array.) We'll let you know in IRC when this happens. You'll also see us disappear from IRC during the outage. :) We won't know the exact time until we're onsite, which should be during the morning of our TZ, UTC-5. If all goes as planned, most users won't notice anything, but you might see a slight delay in list posts. Also, of course, the web archive, as well as other HTTP sites we host, will be temporarily unavailable. I haven't bothered to check stats, but I suspect that our most significant sites other than this mailing list would be mirrors.slackware.com and alien.slackbook.org. We'll let you know here when it's done and will give a report on the effects of green beer. Anyone in the vicinity of Birmingham, Alabama is welcome to join in the experimentation; let us know off-list if you're available and interested. PS: As usual, "Robby and I" is shorthand for "Robby will do the work while I stand around and try to look important." -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From rworkman at slackbuilds.org Mon Mar 14 15:48:11 2016 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2016 10:48:11 -0500 Subject: [Slackbuilds-users] Server maintenance Message-ID: <20160314104811.0067763e@home.rlworkman.net> At some point on Thursday, 20160317 (probably sometime between 1500 and 2100 UTC), harrier.slackbuilds.org will be temporarily shut down for some minor maintenance work - we'll be replacing a couple of hard drives and adding another to the raid array. Because harrier hosts the SBo mailing lists, MX, and DNS, expect those things to be inaccessible for a bit. http, ftp, and rsync access to the SBo repo should be unaffected. Also note that mirrors.slackware.com is hosted on harrier, so it will also be inaccessible for a bit. If the outage will be prolonged, we'll post a note and as much explanation as possible in #slackbuilds IRC channel on freenode. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From pessoal at profcavalheiro.com Mon Mar 14 15:48:56 2016 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Mon, 14 Mar 2016 12:48:56 -0300 Subject: [Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17 In-Reply-To: <20160314154446.GV23739@harrier.slackbuilds.org> References: <20160314154446.GV23739@harrier.slackbuilds.org> Message-ID: Shame it would be at Alabama... Or shame on me for being at Brazil at this moment :-) Em 14/03/2016 12:44 PM, "Rob McGee" escreveu: > Robby and I will be doing a hardware upgrade on harrier, the machine > which hosts lists.slackbuilds.org, probably on Thursday this week. > We're going to try filling it with green beer to see if that will > improve performance. If that fails, we'll fill ourselves with green > beer and revert harrier to normal (albeit with an upgraded storage > array.) > > We'll let you know in IRC when this happens. You'll also see us > disappear from IRC during the outage. :) We won't know the exact > time until we're onsite, which should be during the morning of our > TZ, UTC-5. > > If all goes as planned, most users won't notice anything, but you > might see a slight delay in list posts. Also, of course, the web > archive, as well as other HTTP sites we host, will be temporarily > unavailable. I haven't bothered to check stats, but I suspect that > our most significant sites other than this mailing list would be > mirrors.slackware.com and alien.slackbook.org. > > We'll let you know here when it's done and will give a report on the > effects of green beer. Anyone in the vicinity of Birmingham, Alabama > is welcome to join in the experimentation; let us know off-list if > you're available and interested. > > > > PS: As usual, "Robby and I" is shorthand for "Robby will do the work > while I stand around and try to look important." > -- > Rob McGee - /dev/rob0 - rob0 at slackbuilds.org > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Mon Mar 14 15:52:05 2016 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 14 Mar 2016 10:52:05 -0500 Subject: [Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17 In-Reply-To: <20160314154446.GV23739@harrier.slackbuilds.org> References: <20160314154446.GV23739@harrier.slackbuilds.org> Message-ID: <20160314105205.0c4daab7@home.rlworkman.net> On Mon, 14 Mar 2016 10:44:46 -0500 Rob McGee wrote: > Robby and I will be doing a hardware upgrade on harrier, the machine > which hosts lists.slackbuilds.org, probably on Thursday this week. > We're going to try filling it with green beer to see if that will > improve performance. If that fails, we'll fill ourselves with green > beer and revert harrier to normal (albeit with an upgraded storage > array.) > > We'll let you know in IRC when this happens. You'll also see us > disappear from IRC during the outage. :) We won't know the exact > time until we're onsite, which should be during the morning of our > TZ, UTC-5. > > If all goes as planned, most users won't notice anything, but you > might see a slight delay in list posts. Also, of course, the web > archive, as well as other HTTP sites we host, will be temporarily > unavailable. I haven't bothered to check stats, but I suspect that > our most significant sites other than this mailing list would be > mirrors.slackware.com and alien.slackbook.org. > > We'll let you know here when it's done and will give a report on the > effects of green beer. Anyone in the vicinity of Birmingham, Alabama > is welcome to join in the experimentation; let us know off-list if > you're available and interested. > > > > PS: As usual, "Robby and I" is shorthand for "Robby will do the work > while I stand around and try to look important." And as you see, we communicate very well. So well, in fact, that we both wrote a maintenance announcement ;-) At least one other geek is planning to join us for lunch in BHM, so yeah, any others are welcome. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rob0 at slackbuilds.org Mon Mar 14 15:56:45 2016 From: rob0 at slackbuilds.org (Rob McGee) Date: Mon, 14 Mar 2016 10:56:45 -0500 Subject: [Slackbuilds-users] Server maintenance In-Reply-To: <20160314104811.0067763e@home.rlworkman.net> References: <20160314104811.0067763e@home.rlworkman.net> Message-ID: <20160314155644.GW23739@harrier.slackbuilds.org> On Mon, Mar 14, 2016 at 10:48:11AM -0500, Robby Workman wrote: > Because harrier hosts the SBo mailing lists, MX, and DNS, expect > those things to be inaccessible for a bit. http, ftp, and rsync > access to the SBo repo should be unaffected. DNS will only be slightly affected, not noticed by the end user, thanks in large part to our former hosting service, Omnicity. We will be answering queries from sites there. And speaking of thanks, it's always a good idea to give it to harrier's hosting provider, TekLinks. Good folks and an excellent facility, highly recommended if you are in the market for quality colocation services. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From willysr at slackbuilds.org Mon Mar 14 16:31:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 14 Mar 2016 23:31:25 +0700 Subject: [Slackbuilds-users] Keepassx In-Reply-To: References: Message-ID: <56E6E75D.7010701@slackbuilds.org> > I've just updated keepassx to 2.0.2 and tested it under current. I > don't know if it is ok for the maintainer. I attach a git patch. I can > make a pull request if needed. pushed to my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Mon Mar 14 16:50:39 2016 From: didier at slint.fr (Didier Spaier) Date: Mon, 14 Mar 2016 17:50:39 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> Message-ID: <56E6EBDF.2090903@slint.fr> On 14/03/2016 13:39, Bryan Harris wrote: > Why worry so much over something so insignificant? Just do whatever > Volkerding does. +1. Let me add: only make a change if there is a proven advantage, like _ old way failing (provide example), where the new one does not _ new way *significantly* faster (a few less seconds when the end user builds the package is not significant as I see it) _ guarantee that the new formula neither fails nor introduce unexpected side Shorter is *not* an advantage, more readable... well, it's readable enough as it is IMO. Maybe it wouldn't hurt to write -execdir 755 instead of -print0 | xargs -0 chmod 755 as suggested by Lu?s Fernando Carvalho Cavalheiro, as if I understand well it dosn't change the logic at all, but I wouldn't go further than that in a template (and I do not request it). Didier -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x60C03EEA.asc Type: application/pgp-keys Size: 1718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From erik at slackbuilds.org Mon Mar 14 17:29:37 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 14 Mar 2016 12:29:37 -0500 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E6EBDF.2090903@slint.fr> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> Message-ID: <20160314122937.543a6c35@shaggy.doo> On Mon, 14 Mar 2016 17:50:39 +0100 Didier Spaier wrote: > Maybe it wouldn't hurt to write > -execdir 755 Unless I'm misunderstanding the man page, this would need to be -execdir chmod 755 {} \; It seems like there's possible value there, and it doesn't deviate too far from what we (Pat) does. I haven't run speed tests on this. > instead of > -print0 | xargs -0 chmod 755 This one produces errors if there are no matching files. -- Erik From didier at slint.fr Mon Mar 14 18:43:12 2016 From: didier at slint.fr (Didier Spaier) Date: Mon, 14 Mar 2016 19:43:12 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160314122937.543a6c35@shaggy.doo> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> Message-ID: <56E70640.3070804@slint.fr> On 14/03/2016 18:29, Erik Hanson wrote: > Didier Spaier wrote: > >> Maybe it wouldn't hurt to write >> -execdir 755 > > Unless I'm misunderstanding the man page, this would need to be > -execdir chmod 755 {} \; Indeed, sorry for the mistake. Didier -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x60C03EEA.asc Type: application/pgp-keys Size: 1718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From pessoal at profcavalheiro.com Mon Mar 14 19:04:50 2016 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Mon, 14 Mar 2016 16:04:50 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E70640.3070804@slint.fr> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> <56E70640.3070804@slint.fr> Message-ID: Indeed it should be -execdir chmod 755 {} \; ...at end of command line. I was fast typing and I did this little mistake. As said, command will stop in error in "-print0 | xargs -0" form if no matching file is provided. Plus, since the sole function of this piped xargs is chmod, it is an uneeded complexity since -execdir does the same. Em 14/03/2016 3:44 PM, "Didier Spaier" escreveu: > On 14/03/2016 18:29, Erik Hanson wrote: > > Didier Spaier wrote: > > > >> Maybe it wouldn't hurt to write > >> -execdir 755 > > > > Unless I'm misunderstanding the man page, this would need to be > > -execdir chmod 755 {} \; > > Indeed, sorry for the mistake. > > Didier > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon Mar 14 20:26:01 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 14 Mar 2016 21:26:01 +0100 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: <56E5B5BF.5070904@gmail.com> References: <56E5122B.3090505@gmail.com> <56E5B5BF.5070904@gmail.com> Message-ID: here I applied this small diff to nvidia-switch to make ldconfig happy. -------------- next part -------------- --- nvidia-switch.orig 2016-03-13 06:13:38.000000000 +0100 +++ nvidia-switch 2016-03-14 21:09:40.956989151 +0100 @@ -56,17 +56,20 @@ if [ -e libEGL.so.1.0.0 ]; then mv libEGL.so.1.0.0 libEGL.so.1.0.0-xorg fi - mv libEGL.so.1-nvidia libEGL.so.1 + mv libEGL.so.1-nvidia libEGL.so.$NV_VERSION + ln -sf libEGL.so.$NV_VERSION libEGL.so.1 ln -sf libEGL.so.1 libEGL.so if [ -e libGLESv1_CM.so.1.1.0 ]; then mv libGLESv1_CM.so.1.1.0 libGLESv1_CM.so.1.1.0-xorg fi - mv libGLESv1_CM.so.1-nvidia libGLESv1_CM.so.1 + mv libGLESv1_CM.so.1-nvidia libGLESv1_CM.so.$NV_VERSION + ln -sf libGLESv1_CM.so.$NV_VERSION libGLESv1_CM.so.1 ln -sf libGLESv1_CM.so.1 libGLESv1_CM.so if [ -e libGLESv2.so.2.0.0 ]; then mv libGLESv2.so.2.0.0 libGLESv2.so.2.0.0-xorg fi - mv libGLESv2.so.2-nvidia libGLESv2.so.2 + mv libGLESv2.so.2-nvidia libGLESv2.so.$NV_VERSION + ln -sf libGLESv2.so.$NV_VERSION libGLESv2.so.2 ln -sf libGLESv2.so.2 libGLESv2.so fi @@ -78,19 +81,19 @@ ln -sf libGL.so.$GL_VERSION libGL.so mv libGL.la-xorg libGL.la fi - mv libEGL.so.1 libEGL.so.1-nvidia + mv libEGL.so.$NV_VERSION libEGL.so.1-nvidia if [ -e libEGL.so.1.0.0-xorg ]; then mv libEGL.so.1.0.0-xorg libEGL.so.1.0.0 ln -sf libEGL.so.1.0.0 libEGL.so.1 ln -sf libEGL.so.1.0.0 libEGL.so fi - mv libGLESv2.so.2 libGLESv2.so.2-nvidia + mv libGLESv2.so.$NV_VERSION libGLESv2.so.2-nvidia if [ -e libGLESv2.so.2.0.0-xorg ]; then mv libGLESv2.so.2.0.0-xorg libGLESv2.so.2.0.0 ln -sf libGLESv2.so.2.0.0 libGLESv2.so.2 ln -sf libGLESv2.so.2.0.0 libGLESv2.so fi - mv libGLESv1_CM.so.1 libGLESv1_CM.so.1-nvidia + mv libGLESv1_CM.so.$NV_VERSION libGLESv1_CM.so.1-nvidia if [ -e libGLESv1_CM.so.1.1.0-xorg ]; then mv libGLESv1_CM.so.1.1.0-xorg libGLESv1_CM.so.1.1.0 ln -sf libGLESv1_CM.so.1.1.0 libGLESv1_CM.so.1 From erik at slackbuilds.org Mon Mar 14 20:48:55 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Mon, 14 Mar 2016 15:48:55 -0500 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> <56E70640.3070804@slint.fr> Message-ID: <20160314154855.5aa3ceb4@shaggy.doo> On Mon, 14 Mar 2016 16:04:50 -0300 Luis Cavalheiro wrote: > Indeed it should be > > -execdir chmod 755 {} \; > > ...at end of command line. I was fast typing and I did this little > mistake. As said, command will stop in error in "-print0 | xargs -0" > form if no matching file is provided. Plus, since the sole function > of this piped xargs is chmod, it is an uneeded complexity since > -execdir does the same. It seems a switch from -exec to -execdir would be a good idea. I'd support it, but I was hoping someone would run some benchmarks to see if the benefit is worth it. MAME is a good target. That said, and assuming other admins are in agreement, this change would target the template only. That means we'd allow new submissions with it but would not be doing any sort of global change to the repo. That doesn't seem very viable to me. And again, would love input from other admins. I don't really wish to be a sole arbiter here. Dissent is welcome :) -- Erik From pessoal at profcavalheiro.com Mon Mar 14 21:35:18 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Mon, 14 Mar 2016 18:35:18 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160314154855.5aa3ceb4@shaggy.doo> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> <56E70640.3070804@slint.fr> <20160314154855.5aa3ceb4@shaggy.doo> Message-ID: <20160314183518.795155b6.pessoal@profcavalheiro.com> I'm with -execdir approach. I use it on my personal slackbuild scripts (hosted at https://github.com/lcavalheiro/slackbuilds - I plan to submit them to http://slackbuilds.org as soon as submissions are allowed again), and all of them build very well :-) I'm testing the tree approaches (find + xargs, find with -exec and find with -execdir) right now. As soon as I have a result I'll send it to here. Em 14 de 03 de 2016 ?s 15:48:55T-0500, Erik Hanson escreveu: > On Mon, 14 Mar 2016 16:04:50 -0300 > Luis Cavalheiro wrote: > > > Indeed it should be > > > > -execdir chmod 755 {} \; > > > > ...at end of command line. I was fast typing and I did this little > > mistake. As said, command will stop in error in "-print0 | xargs -0" > > form if no matching file is provided. Plus, since the sole function > > of this piped xargs is chmod, it is an uneeded complexity since > > -execdir does the same. > > It seems a switch from -exec to -execdir would be a good idea. I'd > support it, but I was hoping someone would run some benchmarks to see > if the benefit is worth it. MAME is a good target. > > That said, and assuming other admins are in agreement, this change > would target the template only. That means we'd allow new submissions > with it but would not be doing any sort of global change to the repo. > That doesn't seem very viable to me. > > And again, would love input from other admins. I don't really wish to > be a sole arbiter here. Dissent is welcome :) > > > -- > Erik > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From pessoal at profcavalheiro.com Mon Mar 14 22:14:07 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Mon, 14 Mar 2016 19:14:07 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160314154855.5aa3ceb4@shaggy.doo> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> <56E70640.3070804@slint.fr> <20160314154855.5aa3ceb4@shaggy.doo> Message-ID: <20160314191407.190d5752.pessoal@profcavalheiro.com> Hey guys. As ironic it looks like, the fastest approach is find + xargs. I won't rewrite my own SlackBuilds, but new ones will use find + xargs. Em 14 de 03 de 2016 ?s 15:48:55T-0500, Erik Hanson escreveu: > On Mon, 14 Mar 2016 16:04:50 -0300 > Luis Cavalheiro wrote: > > > Indeed it should be > > > > -execdir chmod 755 {} \; > > > > ...at end of command line. I was fast typing and I did this little > > mistake. As said, command will stop in error in "-print0 | xargs -0" > > form if no matching file is provided. Plus, since the sole function > > of this piped xargs is chmod, it is an uneeded complexity since > > -execdir does the same. > > It seems a switch from -exec to -execdir would be a good idea. I'd > support it, but I was hoping someone would run some benchmarks to see > if the benefit is worth it. MAME is a good target. > > That said, and assuming other admins are in agreement, this change > would target the template only. That means we'd allow new submissions > with it but would not be doing any sort of global change to the repo. > That doesn't seem very viable to me. > > And again, would love input from other admins. I don't really wish to > be a sole arbiter here. Dissent is welcome :) > > > -- > Erik > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From elyk03 at gmail.com Tue Mar 15 01:32:44 2016 From: elyk03 at gmail.com (Kyle Guinn) Date: Mon, 14 Mar 2016 20:32:44 -0500 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160314191407.190d5752.pessoal@profcavalheiro.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> <56E70640.3070804@slint.fr> <20160314154855.5aa3ceb4@shaggy.doo> <20160314191407.190d5752.pessoal@profcavalheiro.com> Message-ID: On 3/14/16, Lu?s Fernando Carvalho Cavalheiro wrote: > Hey guys. As ironic it looks like, the fastest approach is find + xargs. I > won't rewrite my own SlackBuilds, but new ones will use find + xargs. Have you tried "-exec chmod 644 {} +" or "-execdir chmod 644 {} +" ? Note the plus sign. From elyk03 at gmail.com Tue Mar 15 02:15:56 2016 From: elyk03 at gmail.com (Kyle Guinn) Date: Mon, 14 Mar 2016 21:15:56 -0500 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <56E6EBDF.2090903@slint.fr> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> Message-ID: On 3/14/16, Didier Spaier wrote: > Let me add: only make a change if there is a proven advantage, like > _ old way failing (provide example), where the new one does not I occasionally come across source tarballs where every file unintentionally has the sticky bit set. (I don't have a clue how this happens.) The find command doesn't correct this. Combine that with a badly handwritten makefile or a binary repackaging and you can easily end up with those sticky bits in the resulting package. > _ new way *significantly* faster (a few less seconds when the end user > builds the package is not significant as I see it) I remember the find command taking about 4 minutes on the kernel source, a minute or two on some larger packages like Octave. chmod -R is instant. > _ guarantee that the new formula neither fails nor introduce unexpected > side mkdir tmp cd tmp for i in {0..7}{0..7}{0..7}{0..7}; do touch $i; chmod $i $i; done $YOUR_CHMOD_COMMAND_HERE find . -exec stat --printf "%n %A\n" {} + | sort > manifest Compare manifests over different runs to see how the permissions are affected. -Kyle From pessoal at profcavalheiro.com Tue Mar 15 02:17:28 2016 From: pessoal at profcavalheiro.com (=?UTF-8?B?THXDrXM=?= Fernando Carvalho Cavalheiro) Date: Mon, 14 Mar 2016 23:17:28 -0300 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> <56E70640.3070804@slint.fr> <20160314154855.5aa3ceb4@shaggy.doo> <20160314191407.190d5752.pessoal@profcavalheiro.com> Message-ID: <20160314231728.3c059ade.pessoal@profcavalheiro.com> I've not tried with plus sign. I've tested - find ... -print0 | xargs -0 ... - find ... -exec 755 {} \; - find ... -execdir 755 {} \; Last two forms required like ten times more time than first one. On MAME case, it's a huge amount of time. Em 14 de 03 de 2016 ?s 20:32:44T-0500, Kyle Guinn escreveu: > On 3/14/16, Lu?s Fernando Carvalho Cavalheiro > wrote: > > Hey guys. As ironic it looks like, the fastest approach is find + xargs. I > > won't rewrite my own SlackBuilds, but new ones will use find + xargs. > > Have you tried "-exec chmod 644 {} +" or "-execdir chmod 644 {} +" ? > Note the plus sign. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- 93 93/93 Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: Assinatura digital OpenPGP URL: From eric.b.pratt at gmail.com Tue Mar 15 07:57:21 2016 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Tue, 15 Mar 2016 00:57:21 -0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> <56E65405.5030300@slackbuilds.org> Message-ID: I've looked over the diff but not your previous script yet. I agree with the diff so far but I do wonder about why those two blocks of variables are separated. They really look like they should be together since the logic for determining $ARCH doesn't affect the second block of variables. Shouldn't the templates be changed to group them together or is there another reason for their separation. It's a minor and purely aesthetic point, but it just didn't look right to me. I'll look at your previous script tomorrow and let you know what I think. On Mon, Mar 14, 2016 at 5:10 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2016-03-14 7:31 GMT+01:00 Eric Pratt : > > I see. Thanks! > > > > On Sun, Mar 13, 2016 at 11:02 PM, Willy Sudiarto Raharjo > > wrote: > >> > >> > Well, it looks like the same guy did it again in January. I thought > >> > only > >> > the maintainer could submit updates to the slackbuild. Is that > >> > incorrect? > >> > > >> > Since this appears to be happening, lets just go ahead and commit this > >> > update. It eliminates the cumbersome patch files and gets us all the > >> > latest bug fixes except for what's in the last release since that > >> > release > >> > wont build and I haven't investigated why yet. > >> > >> It was one of the admin, Matteo (ponce) > >> During development cycle like this, we often update the SlackBuild if > >> it's really needed for several reasons: > >> - Fix a build failure due to changes in Slackware > >> - Not yet updated by maintainer for a long time > > Hi Eric, > > as I am using vice myself I noticed when the build broke in the last > 5+ years (compiler, ffmpeg versions, etc.) and took care of fixing it > or we had to remove it from the repository. > as for the last update it slipped from my personal repository when > merging the other fixes for current... > > I just had a look at your submission and I see you have rebased your > modifications on your old script and not what we have in our > repository, so I had to fix some things again: > - the homepage isn't working anymore, so I switched to the sourceforge one; > - I moved the block that defines some variables in the slackbuild > lower in it because that's how we have in most of our SlackBuilds: > this helps in case we had to do some automated scripting cleanups in > our repository, like it often happens (this is effective if we have > scripts conforming to the templates); > - I added man and info file compression blocks; > - as the doc directory from the sources folder is messy and the "make > install" already installs a clean one in > /usr/lib$LIBDIRSUFFIX/$PRGNAM/doc where it shouldn't be, I opted to > move this later in /usr/doc/$PRGNAM-$VERSION and the html stuff in a > subdirectory, fixing permissions (executable text files). > I attach the diff over your last submission: if it's ok for you I'll > commit your submission with these corrections in our git. > > Matteo > > P.S. Note that not enabling the bundled ffmpeg implies that recording > videos of the emulator running from the menus doesn't work: feel free > to look at the script I previously submitted. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric.b.pratt at gmail.com Tue Mar 15 08:09:52 2016 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Tue, 15 Mar 2016 01:09:52 -0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> <56E65405.5030300@slackbuilds.org> Message-ID: I was going to try to go to bed, but I decided to hell with it and took a look at the script tonight. I like your ffmpeg changes so we should probably add those back in. Also, the diff you sent doesn't seem to include your previous find line for the symbol stripping. -find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ +find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ I think your version is better and we should probably go with that. If you'd like, I can put together a updated slackbuild and email it to this thread. Or if you prefer, you can make the changes in your repository and push them through on your next commit. We'll go with whatever you think is best. Thanks for all the help on this! Eric On Tue, Mar 15, 2016 at 12:57 AM, Eric Pratt wrote: > I've looked over the diff but not your previous script yet. I agree with > the diff so far but I do wonder about why those two blocks of variables are > separated. They really look like they should be together since the logic > for determining $ARCH doesn't affect the second block of variables. > Shouldn't the templates be changed to group them together or is there > another reason for their separation. It's a minor and purely aesthetic > point, but it just didn't look right to me. > > I'll look at your previous script tomorrow and let you know what I think. > > > On Mon, Mar 14, 2016 at 5:10 AM, Matteo Bernardini < > matteo.bernardini at gmail.com> wrote: > >> 2016-03-14 7:31 GMT+01:00 Eric Pratt : >> > I see. Thanks! >> > >> > On Sun, Mar 13, 2016 at 11:02 PM, Willy Sudiarto Raharjo >> > wrote: >> >> >> >> > Well, it looks like the same guy did it again in January. I thought >> >> > only >> >> > the maintainer could submit updates to the slackbuild. Is that >> >> > incorrect? >> >> > >> >> > Since this appears to be happening, lets just go ahead and commit >> this >> >> > update. It eliminates the cumbersome patch files and gets us all the >> >> > latest bug fixes except for what's in the last release since that >> >> > release >> >> > wont build and I haven't investigated why yet. >> >> >> >> It was one of the admin, Matteo (ponce) >> >> During development cycle like this, we often update the SlackBuild if >> >> it's really needed for several reasons: >> >> - Fix a build failure due to changes in Slackware >> >> - Not yet updated by maintainer for a long time >> >> Hi Eric, >> >> as I am using vice myself I noticed when the build broke in the last >> 5+ years (compiler, ffmpeg versions, etc.) and took care of fixing it >> or we had to remove it from the repository. >> as for the last update it slipped from my personal repository when >> merging the other fixes for current... >> >> I just had a look at your submission and I see you have rebased your >> modifications on your old script and not what we have in our >> repository, so I had to fix some things again: >> - the homepage isn't working anymore, so I switched to the sourceforge >> one; >> - I moved the block that defines some variables in the slackbuild >> lower in it because that's how we have in most of our SlackBuilds: >> this helps in case we had to do some automated scripting cleanups in >> our repository, like it often happens (this is effective if we have >> scripts conforming to the templates); >> - I added man and info file compression blocks; >> - as the doc directory from the sources folder is messy and the "make >> install" already installs a clean one in >> /usr/lib$LIBDIRSUFFIX/$PRGNAM/doc where it shouldn't be, I opted to >> move this later in /usr/doc/$PRGNAM-$VERSION and the html stuff in a >> subdirectory, fixing permissions (executable text files). >> I attach the diff over your last submission: if it's ok for you I'll >> commit your submission with these corrections in our git. >> >> Matteo >> >> P.S. Note that not enabling the bundled ffmpeg implies that recording >> videos of the emulator running from the menus doesn't work: feel free >> to look at the script I previously submitted. >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue Mar 15 08:13:38 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 15 Mar 2016 09:13:38 +0100 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> <56E65405.5030300@slackbuilds.org> Message-ID: 2016-03-15 9:09 GMT+01:00 Eric Pratt : > I was going to try to go to bed, but I decided to hell with it and took a > look at the script tonight. I like your ffmpeg changes so we should > probably add those back in. Also, the diff you sent doesn't seem to include > your previous find line for the symbol stripping. > > -find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF > \ > +find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" > | grep ELF \ > > I think your version is better and we should probably go with that. If > you'd like, I can put together a updated slackbuild and email it to this > thread. Or if you prefer, you can make the changes in your repository and > push them through on your next commit. We'll go with whatever you think is > best. IMHO, the first option is better: just email a new slackbuild with the modifications you think are best to this thread. thanks to you for having a look at my stuff! Matteo From slackbuilds at schoepfer.info Tue Mar 15 08:13:44 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 15 Mar 2016 09:13:44 +0100 Subject: [Slackbuilds-users] Call for Bug Fixes, Patches, etc In-Reply-To: <20160314231728.3c059ade.pessoal@profcavalheiro.com> References: <3qNPSJ4SxJz4tWm@harrier.slackbuilds.org> <20160313102327.1773f1d9@shaggy.doo> <56E58724.30805@gmail.com> <20160313110313.0322fbf9@shaggy.doo> <56E5B036.7020801@gmail.com> <20160313152932.6d6dfd0d.pessoal@profcavalheiro.com> <56E5B344.9020402@gmail.com> <56E5B8C2.50709@gmail.com> <9fe3daeeaa77133ee991e57a2f6be71f@schoepfer.info> <56E6EBDF.2090903@slint.fr> <20160314122937.543a6c35@shaggy.doo> <56E70640.3070804@slint.fr> <20160314154855.5aa3ceb4@shaggy.doo> <20160314191407.190d5752.pessoal@profcavalheiro.com> <20160314231728.3c059ade.pessoal@profcavalheiro.com> Message-ID: <56E7C438.8010706@schoepfer.info> On 15.03.2016 03:17, Lu?s Fernando Carvalho Cavalheiro wrote: > I've not tried with plus sign. I've tested > > - find ... -print0 | xargs -0 ... > - find ... -exec 755 {} \; > - find ... -execdir 755 {} \; It's all about the "+" if you compare to the xargs-approach. Here's some discussion about it http://unix.stackexchange.com/questions/41740/find-exec-vs-find-xargs-which-one-to-choose Franzen From matteo.bernardini at gmail.com Tue Mar 15 08:15:44 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 15 Mar 2016 09:15:44 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> Message-ID: 2016-03-14 16:17 GMT+01:00 Matteo Bernardini : > 2016-03-13 23:30 GMT+01:00 Willy Sudiarto Raharjo : >>> Are you guys up to date with the Thu Mar 10 02:46:49 UTC 2016 -current >>> update? >> >> Yes, my system is up to date with latest current update, but probably >> since i tested in my desktop, it's also filled with many packages i used >> so it may affect the build. >> >> let me try on a clean VM like i always do > > I've tried it also on a clean vm with a single job and it seems this > is where it breaks > > http://pastebin.com/6QcYEQVE I think it's better to hear Larry's thoughts on the matter. In the meantime, I noticed that BLFS switched to omitting qtwebengine too http://www.linuxfromscratch.org/blfs/view/svn/x/qt5.html Matteo From atelszewski at gmail.com Tue Mar 15 16:20:19 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 15 Mar 2016 17:20:19 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> Message-ID: <56E83643.9080001@gmail.com> On 15/03/16 09:15, Matteo Bernardini wrote: > 2016-03-14 16:17 GMT+01:00 Matteo Bernardini: >> >2016-03-13 23:30 GMT+01:00 Willy Sudiarto Raharjo: >>>> >>>Are you guys up to date with the Thu Mar 10 02:46:49 UTC 2016 -current >>>> >>>update? >>> >> >>> >>Yes, my system is up to date with latest current update, but probably >>> >>since i tested in my desktop, it's also filled with many packages i used >>> >>so it may affect the build. >>> >> >>> >>let me try on a clean VM like i always do >> > >> >I've tried it also on a clean vm with a single job and it seems this >> >is where it breaks >> > >> >http://pastebin.com/6QcYEQVE > I think it's better to hear Larry's thoughts on the matter. > > In the meantime, I noticed that BLFS switched to omitting qtwebengine too > > http://www.linuxfromscratch.org/blfs/view/svn/x/qt5.html > > Matteo For your information, to build qt5 without qtwebengine: - add "-skip qtwebengine" to ./configure - comment out sed -i 's|-Wl,--whole-archive.*-Wl,--no-whole-archive||' $PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig/Qt5WebEngineCore.pc in the qt5 SlackBuild. -- Best regards, Andrzej Telszewski From baildon.research at googlemail.com Tue Mar 15 16:51:19 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 15 Mar 2016 16:51:19 +0000 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E83643.9080001@gmail.com> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> Message-ID: > For your information, to build qt5 without qtwebengine: > - add "-skip qtwebengine" to ./configure > - comment out sed -i 's|-Wl,--whole-archive.*-Wl,--no-whole-archive||' > $PKG/usr/lib${LIBDIRSUFFIX}/pkgconfig/Qt5WebEngineCore.pc That's the easy part. The difficult part is to find which other packages will fail if qtwebengine is not built, and how to fix them. If we can't do that quickly and easily, then it might be easier to fix qtwebengine. -D. From ozan.turkyilmaz at gmail.com Tue Mar 15 17:09:51 2016 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Tue, 15 Mar 2016 22:09:51 +0500 Subject: [Slackbuilds-users] Slackbuilds Message-ID: Hello All, Finally fixed my computer. Now I have a notebook with SSD and clean install of Slackware-current. I have started to go over my packages right now: First of all, I can't look after ibus-anthy any more. I no longer use it. Rest of my packages: Boncuk : OK chm2pdf : OK splint : Fails to build. I'll get back to that later. aMule : OK libupnp : OK liboop : OK gnet : OK libebml : OK libmatroska: OK cbase : OK gsnmp : OK rar : OK bootchart : OK prelink : OK Chatbot-Eliza: OK fortune-ASR: OK THere are updates for kildclient and mkvtoolnix. I'll send them later. -- Ozan, BSc, BEng From willysr at slackbuilds.org Tue Mar 15 17:47:50 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Mar 2016 00:47:50 +0700 Subject: [Slackbuilds-users] Slackbuilds In-Reply-To: References: Message-ID: <56E84AC6.1010508@slackbuilds.org> > splint : Fails to build. I'll get back to that later. works fine here splint: MD5SUM check for splint-3.1.2.src.tgz ... OK Building package splint-3.1.2-x86_64-1_SBo.tgz ... OK Installing package splint-3.1.2-x86_64-1_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Mar 15 18:36:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Mar 2016 01:36:53 +0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> Message-ID: <56E85645.4080604@slackbuilds.org> > That's the easy part. > > The difficult part is to find which other packages will fail if > qtwebengine is not built, and how to fix them. > > If we can't do that quickly and easily, then it might be easier to fix > qtwebengine. and FYI, here are the packages that directly requires qt5 academic/stellarium academic/ugene audio/acousticbrainz-gui audio/qjackctl desktop/lumina desktop/qmapshack desktop/rss-guard development/fuel development/qt-creator3 development/zeal games/dustrac games/peg-e games/solarus-quest-editor games/vcmi graphics/fritzing graphics/luminance-hdr graphics/photoqt graphics/phototonic graphics/qelectrotech graphics/scantailor libraries/poppler-qt5 libraries/python3-PyQt5 libraries/qmltermwidget multimedia/obs-studio multimedia/xvst network/cmst network/otter network/qTox network/wireshark office/sigil system/zuluCrypt it doesn't count packages that optionally depends on qt5 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From larryhaja at gmail.com Tue Mar 15 21:05:56 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 15 Mar 2016 14:05:56 -0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E85645.4080604@slackbuilds.org> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> Message-ID: So, I was able to recreate the issue Matteo posted on http://pastebin.com/6QcYEQVE using all optional dependencies and adding DOCS and EXAMPLES as yes. Fortunately, I was able to create a patch that compiles qt5. The short answer of why it fails on Slackware -current is that the newer mozilla-nss package now defines CKM_NSS_CHACHA20_POLY1305 and CK_NSS_AEAD_PARAMS. They were originally defined in ssl3con.c if CKM_NSS_CHACHA20_POLY1305 wasn't defined. Also the nonce and nonce length for CK_NSS_AEAD_PARAMS, which were pIv and ulIvLen, are now renamed pNonce and ulNonceLen, respectively, in /usr/include/nss/pkcs11n.h. I'm still building qt5 but it is past the point where the error happens. I'm providing a patch to account for the updated headers in mozilla-nss package. Note that this patch won't work on Slackware 14.1. --Larry On Tue, Mar 15, 2016 at 11:36 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > That's the easy part. > > > > The difficult part is to find which other packages will fail if > > qtwebengine is not built, and how to fix them. > > > > If we can't do that quickly and easily, then it might be easier to fix > > qtwebengine. > > and FYI, here are the packages that directly requires qt5 > > academic/stellarium > academic/ugene > audio/acousticbrainz-gui > audio/qjackctl > desktop/lumina > desktop/qmapshack > desktop/rss-guard > development/fuel > development/qt-creator3 > development/zeal > games/dustrac > games/peg-e > games/solarus-quest-editor > games/vcmi > graphics/fritzing > graphics/luminance-hdr > graphics/photoqt > graphics/phototonic > graphics/qelectrotech > graphics/scantailor > libraries/poppler-qt5 > libraries/python3-PyQt5 > libraries/qmltermwidget > multimedia/obs-studio > multimedia/xvst > network/cmst > network/otter > network/qTox > network/wireshark > office/sigil > system/zuluCrypt > > it doesn't count packages that optionally depends on qt5 > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nss-update-sslv3-nonce.patch Type: text/x-patch Size: 3377 bytes Desc: not available URL: From atelszewski at gmail.com Tue Mar 15 21:11:43 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 15 Mar 2016 22:11:43 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> Message-ID: <56E87A8F.1080304@gmail.com> On 15/03/16 22:05, Larry Hajali wrote: > So, I was able to recreate the issue Matteo posted on > http://pastebin.com/6QcYEQVE using all optional dependencies and adding > DOCS and EXAMPLES as yes. Fortunately, I was able to create a patch > that compiles qt5. > > The short answer of why it fails on Slackware -current is that the newer > mozilla-nss package now defines CKM_NSS_CHACHA20_POLY1305 > and CK_NSS_AEAD_PARAMS. They were originally defined in ssl3con.c if > CKM_NSS_CHACHA20_POLY1305 wasn't defined. Also the nonce and nonce > length for CK_NSS_AEAD_PARAMS, which were pIv and ulIvLen, are now > renamed pNonce and ulNonceLen, respectively, in /usr/include/nss/pkcs11n.h. > I'm still building qt5 but it is past the point where the error > happens. I'm providing a patch to account for the updated headers in > mozilla-nss package. > > Note that this patch won't work on Slackware 14.1. > > --Larry That's more less what I've reported in my fourth e-mail :^) > > On Tue, Mar 15, 2016 at 11:36 AM, Willy Sudiarto Raharjo > > wrote: > > > That's the easy part. > > > > The difficult part is to find which other packages will fail if > > qtwebengine is not built, and how to fix them. > > > > If we can't do that quickly and easily, then it might be easier to fix > > qtwebengine. > > and FYI, here are the packages that directly requires qt5 > > academic/stellarium > academic/ugene > audio/acousticbrainz-gui > audio/qjackctl > desktop/lumina > desktop/qmapshack > desktop/rss-guard > development/fuel > development/qt-creator3 > development/zeal > games/dustrac > games/peg-e > games/solarus-quest-editor > games/vcmi > graphics/fritzing > graphics/luminance-hdr > graphics/photoqt > graphics/phototonic > graphics/qelectrotech > graphics/scantailor > libraries/poppler-qt5 > libraries/python3-PyQt5 > libraries/qmltermwidget > multimedia/obs-studio > multimedia/xvst > network/cmst > network/otter > network/qTox > network/wireshark > office/sigil > system/zuluCrypt > > it doesn't count packages that optionally depends on qt5 > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Best regards, Andrzej Telszewski From info at microlinux.fr Wed Mar 16 06:16:23 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 16 Mar 2016 07:16:23 +0100 Subject: [Slackbuilds-users] jdk vs. openjdk Message-ID: <56E8FA37.10204@microlinux.fr> Hi, I'd like to install the mathematical application GeoGebra on our local school's computers. The openjdk package is listed as a dependency, but I already have Oracle's jdk on the desktops. Is this a perfect equivalent? Or do I have to replace jdk by openjdk? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From matteo.bernardini at gmail.com Wed Mar 16 06:29:24 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 16 Mar 2016 07:29:24 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> Message-ID: 2016-03-15 22:05 GMT+01:00 Larry Hajali : > So, I was able to recreate the issue Matteo posted on > http://pastebin.com/6QcYEQVE using all optional dependencies and adding DOCS > and EXAMPLES as yes. Fortunately, I was able to create a patch that > compiles qt5. > > The short answer of why it fails on Slackware -current is that the newer > mozilla-nss package now defines CKM_NSS_CHACHA20_POLY1305 and > CK_NSS_AEAD_PARAMS. They were originally defined in ssl3con.c if > CKM_NSS_CHACHA20_POLY1305 wasn't defined. Also the nonce and nonce length > for CK_NSS_AEAD_PARAMS, which were pIv and ulIvLen, are now renamed pNonce > and ulNonceLen, respectively, in /usr/include/nss/pkcs11n.h. > I'm still building qt5 but it is past the point where the error happens. > I'm providing a patch to account for the updated headers in mozilla-nss > package. > > Note that this patch won't work on Slackware 14.1. Larry, thanks a lot for the patch! I just tested it and everything went fine. if it's ok for you I will push it to our git grabbing the occasion to include another small fix related to some other report we got (already applied to the upstream git), regarding video cropping when using vlc built over qt5 (verified also here): I just grabbed the patch from Eric's vlc build directory. I attach the diff waiting for your confirmation. Matteo -------------- next part -------------- diff -Naur qt5/patches/nss-update-sslv3-nonce.patch qt5.new/patches/nss-update-sslv3-nonce.patch --- qt5/patches/nss-update-sslv3-nonce.patch 1970-01-01 01:00:00.000000000 +0100 +++ qt5.new/patches/nss-update-sslv3-nonce.patch 2016-03-15 23:13:32.835250047 +0100 @@ -0,0 +1,44 @@ +diff -Naur qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc +--- qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc 2015-10-13 04:36:54.000000000 +0000 ++++ qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_decrypter_nss.cc 2016-03-15 11:57:53.898988200 +0000 +@@ -66,9 +66,9 @@ + AeadParams* aead_params) const { + aead_params->len = sizeof(aead_params->data.nss_aead_params); + CK_NSS_AEAD_PARAMS* nss_aead_params = &aead_params->data.nss_aead_params; +- nss_aead_params->pIv = ++ nss_aead_params->pNonce = + reinterpret_cast(const_cast(nonce.data())); +- nss_aead_params->ulIvLen = nonce.size(); ++ nss_aead_params->ulNonceLen = nonce.size(); + nss_aead_params->pAAD = + reinterpret_cast(const_cast(associated_data.data())); + nss_aead_params->ulAADLen = associated_data.size(); +diff -Naur qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc +--- qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc 2015-10-13 04:36:54.000000000 +0000 ++++ qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/quic/crypto/chacha20_poly1305_encrypter_nss.cc 2016-03-15 11:57:53.902988200 +0000 +@@ -66,9 +66,9 @@ + AeadParams* aead_params) const { + aead_params->len = sizeof(aead_params->data.nss_aead_params); + CK_NSS_AEAD_PARAMS* nss_aead_params = &aead_params->data.nss_aead_params; +- nss_aead_params->pIv = ++ nss_aead_params->pNonce = + reinterpret_cast(const_cast(nonce.data())); +- nss_aead_params->ulIvLen = nonce.size(); ++ nss_aead_params->ulNonceLen = nonce.size(); + nss_aead_params->pAAD = + reinterpret_cast(const_cast(associated_data.data())); + nss_aead_params->ulAADLen = associated_data.size(); +diff -Naur qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c +--- qt-everywhere-opensource-src-5.5.1.orig/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c 2015-10-13 04:36:52.000000000 +0000 ++++ qt-everywhere-opensource-src-5.5.1/qtwebengine/src/3rdparty/chromium/net/third_party/nss/ssl/ssl3con.c 2016-03-15 12:00:01.376986796 +0000 +@@ -2088,8 +2088,8 @@ + param.len = sizeof(aeadParams); + param.data = (unsigned char *) &aeadParams; + memset(&aeadParams, 0, sizeof(aeadParams)); +- aeadParams.pIv = (unsigned char *) additionalData; +- aeadParams.ulIvLen = 8; ++ aeadParams.pNonce = (unsigned char *) additionalData; ++ aeadParams.ulNonceLen = 8; + aeadParams.pAAD = (unsigned char *) additionalData; + aeadParams.ulAADLen = additionalDataLen; + aeadParams.ulTagLen = tagSize; diff -Naur qt5/patches/qt5.whandle.patch qt5.new/patches/qt5.whandle.patch --- qt5/patches/qt5.whandle.patch 1970-01-01 01:00:00.000000000 +0100 +++ qt5.new/patches/qt5.whandle.patch 2016-02-07 22:56:45.000000000 +0100 @@ -0,0 +1,24 @@ +From: Ulf Hermann +Date: Tue, 27 Oct 2015 14:25:42 +0000 (+0100) +Subject: WIP: Also do hide/show via WA_OutsideWSRange for native widgets +X-Git-Url: https://codereview.qt-project.org/gitweb?p=qt%2Fqtbase.git;a=commitdiff_plain;h=5ea44d1d516f0c68a6793279df5c1569ef9fadd2 + +WIP: Also do hide/show via WA_OutsideWSRange for native widgets + +Task-number: QTBUG-48321 +Change-Id: I78ef29975181ee22429c9bd4b11d96d9e68b7a9c +--- + +diff --git a/qtbase/src/widgets/kernel/qwidget.cpp b/qtbase/src/widgets/kernel/qwidget.cpp +index a006246..024005d 100644 +--- a/qtbase/src/widgets/kernel/qwidget.cpp ++++ b/qtbase/src/widgets/kernel/qwidget.cpp +@@ -7169,7 +7169,7 @@ void QWidgetPrivate::setGeometry_sys(int x, int y, int w, int h, bool isMove) + + bool needsShow = false; + +- if (q->isWindow()) { ++ if (q->isWindow() || q->windowHandle()) { + if (!(data.window_state & Qt::WindowFullScreen) && (w == 0 || h == 0)) { + q->setAttribute(Qt::WA_OutsideWSRange, true); + if (q->isVisible() && q->testAttribute(Qt::WA_Mapped)) diff -Naur qt5/qt5.SlackBuild qt5.new/qt5.SlackBuild --- qt5/qt5.SlackBuild 2016-03-14 08:31:49.044454568 +0100 +++ qt5.new/qt5.SlackBuild 2016-03-15 23:17:34.467960322 +0100 @@ -47,7 +47,7 @@ PRGNAM=qt5 VERSION=${VERSION:-5.5.1} -BUILD=${BUILD:-1} +BUILD=${BUILD:-2} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then @@ -105,6 +105,12 @@ # https://bugs.webkit.org/show_bug.cgi?id=117077 patch -p1 < $CWD/patches/platformplugin-install-path-fix.patch +# Prevent cropped video in full-screen mode (QTBUG-48321). +patch -p1 < $CWD/patches/qt5.whandle.patch + +# Patch for the newer mozilla-nss +patch -p1 < $CWD/patches/nss-update-sslv3-nonce.patch + # Limit -reduce-relocations to ix86 and x86_64. # https://bugreports.qt-project.org/browse/QTBUG-36129 if echo $ARCH | grep -q '\(i.86\|x86_64\)' 2>/dev/null; then From willysr at slackbuilds.org Wed Mar 16 07:52:45 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Mar 2016 14:52:45 +0700 Subject: [Slackbuilds-users] jdk vs. openjdk In-Reply-To: <56E8FA37.10204@microlinux.fr> References: <56E8FA37.10204@microlinux.fr> Message-ID: <56E910CD.8010607@slackbuilds.org> > I'd like to install the mathematical application GeoGebra on our local > school's computers. The openjdk package is listed as a dependency, but I > already have Oracle's jdk on the desktops. Is this a perfect equivalent? > Or do I have to replace jdk by openjdk? both works fine it's just a matter of preferences -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Wed Mar 16 08:07:25 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 16 Mar 2016 09:07:25 +0100 Subject: [Slackbuilds-users] jdk vs. openjdk In-Reply-To: <56E910CD.8010607@slackbuilds.org> References: <56E8FA37.10204@microlinux.fr> <56E910CD.8010607@slackbuilds.org> Message-ID: <56E9143D.4050205@microlinux.fr> Le 16/03/2016 08:52, Willy Sudiarto Raharjo a ?crit : > both works fine > it's just a matter of preferences Thanks Willy. I installed it with jdk, and it works fine. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From slackbuilds at schoepfer.info Wed Mar 16 08:28:25 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 16 Mar 2016 09:28:25 +0100 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E85645.4080604@slackbuilds.org> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> Message-ID: <56E91929.9010501@schoepfer.info> >> The difficult part is to find which other packages will fail if >> qtwebengine is not built, and how to fix them. >> >> If we can't do that quickly and easily, then it might be easier to fix >> qtwebengine. > > and FYI, here are the packages that directly requires qt5 A recent mscore/musescore 2.0.2 also requires qt5, mscore 1.3 from SBo is outdated. https://musescore.org/ Franzen From sbolokanov at abv.bg Wed Mar 16 11:51:17 2016 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Wed, 16 Mar 2016 13:51:17 +0200 (EET) Subject: [Slackbuilds-users] lgogdownloader changes Message-ID: <120388134.1507916.1458129077989.JavaMail.apache@nm53.abv.bg> There are important changes to lgogdownloader. Notable changes: - Changed build system to CMake (patch by: Sandy Carter) - Added support for two-step login * * https://www.gog.com/news/twostep_login_https_everywhere I have made 2 versions, since I'm not sure whether we should build in clean folder or not. With mkdir build: https://github.com/sbolokanov/sbo-clone/commit/3d1ac00720c87c90ecb3975099418f25baa08d5d With no mkdir build: https://github.com/sbolokanov/sbo-clone2/commit/feca081d8a80d6b7227143c128a7fd7e77ac2e0c -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Wed Mar 16 12:40:37 2016 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 16 Mar 2016 05:40:37 -0700 (PDT) Subject: [Slackbuilds-users] jdk vs. openjdk In-Reply-To: <56E910CD.8010607@slackbuilds.org> References: <56E8FA37.10204@microlinux.fr> <56E910CD.8010607@slackbuilds.org> Message-ID: On Wed, 16 Mar 2016, Willy Sudiarto Raharjo wrote: > both works fine > it's just a matter of preferences ... and the version of Java used to build the application. I've one tool (jgnash -- a checkbook manager) that requires Java8 support, available only through Oracle's JDK. Another Java tool I use, JabRef, will run with a java7 JDK so it's happy with openjdk. Rich From willysr at slackbuilds.org Wed Mar 16 13:00:50 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Mar 2016 20:00:50 +0700 Subject: [Slackbuilds-users] lgogdownloader changes In-Reply-To: <120388134.1507916.1458129077989.JavaMail.apache@nm53.abv.bg> References: <120388134.1507916.1458129077989.JavaMail.apache@nm53.abv.bg> Message-ID: <56E95902.8020602@slackbuilds.org> > I have made 2 versions, since I'm not sure whether we should build in clean folder or not. > With mkdir build: https://github.com/sbolokanov/sbo-clone/commit/3d1ac00720c87c90ecb3975099418f25baa08d5d > With no mkdir build: https://github.com/sbolokanov/sbo-clone2/commit/feca081d8a80d6b7227143c128a7fd7e77ac2e0c i prefer the with mkdir build can you send in the form of a patch file please? Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Mar 16 13:03:00 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Mar 2016 20:03:00 +0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> Message-ID: <56E95984.80901@slackbuilds.org> > Larry, thanks a lot for the patch! I just tested it and everything went fine. > if it's ok for you I will push it to our git grabbing the occasion to > include another small fix related to some other report we got (already > applied to the upstream git), regarding video cropping when using vlc > built over qt5 (verified also here): I just grabbed the patch from > Eric's vlc build directory. > I attach the diff waiting for your confirmation. and now Qt 5.6 is officially released any thought we should stick to 5.5 or try to update to 5.6 ? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From marc at mos6581.de Wed Mar 16 13:07:10 2016 From: marc at mos6581.de (Marcel Saegebarth) Date: Wed, 16 Mar 2016 14:07:10 +0100 Subject: [Slackbuilds-users] lgogdownloader changes In-Reply-To: <56E95902.8020602@slackbuilds.org> References: <120388134.1507916.1458129077989.JavaMail.apache@nm53.abv.bg> <56E95902.8020602@slackbuilds.org> Message-ID: <56E95A7E.1010200@mos6581.de> On 03/16/2016 02:00 PM, Willy Sudiarto Raharjo wrote: >> I have made 2 versions, since I'm not sure whether we should build in clean folder or not. >> With mkdir build: https://github.com/sbolokanov/sbo-clone/commit/3d1ac00720c87c90ecb3975099418f25baa08d5d >> With no mkdir build: https://github.com/sbolokanov/sbo-clone2/commit/feca081d8a80d6b7227143c128a7fd7e77ac2e0c > > i prefer the with mkdir build > can you send in the form of a patch file please? > > Thanks Would be nice if anyone now involved could just wait for the official maintainer updating his SlackBuild instead of having some kind of anarchy. I've all releases in scope. Thanks. -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From bch at shroggslodge.freeserve.co.uk Wed Mar 16 14:38:36 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Wed, 16 Mar 2016 14:38:36 +0000 Subject: [Slackbuilds-users] jdk vs. openjdk In-Reply-To: References: <56E8FA37.10204@microlinux.fr> <56E910CD.8010607@slackbuilds.org> Message-ID: I was led to believe that the webstart provision in OpenJDK was not as complete (probably not the correct word, but still) as in Oracle version. That may have changed with later releases perhaps. Habs On 16 March 2016 at 12:40, Rich Shepard wrote: > On Wed, 16 Mar 2016, Willy Sudiarto Raharjo wrote: > > both works fine >> it's just a matter of preferences >> > > ... and the version of Java used to build the application. I've one tool > (jgnash -- a checkbook manager) that requires Java8 support, available only > through Oracle's JDK. Another Java tool I use, JabRef, will run with a > java7 > JDK so it's happy with openjdk. > > Rich > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Wed Mar 16 14:50:50 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Wed, 16 Mar 2016 07:50:50 -0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E95984.80901@slackbuilds.org> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> <56E95984.80901@slackbuilds.org> Message-ID: Matteo, go ahead and add the additional upstream patch. Willy, I don't have a lot of time to test 5.6.0. So, I won't don't see 5.6.0 getting into the repo anytime soon. --Larry On Wed, Mar 16, 2016 at 6:03 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Larry, thanks a lot for the patch! I just tested it and everything went > fine. > > if it's ok for you I will push it to our git grabbing the occasion to > > include another small fix related to some other report we got (already > > applied to the upstream git), regarding video cropping when using vlc > > built over qt5 (verified also here): I just grabbed the patch from > > Eric's vlc build directory. > > I attach the diff waiting for your confirmation. > > and now Qt 5.6 is officially released > > any thought we should stick to 5.5 or try to update to 5.6 ? > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Mar 16 15:46:13 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Mar 2016 22:46:13 +0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> <56E95984.80901@slackbuilds.org> Message-ID: <56E97FC5.7000505@slackbuilds.org> > Willy, I don't have a lot of time to test 5.6.0. So, I won't don't see > 5.6.0 getting into the repo anytime soon. No worries 5.6.x will be a LTS release so i was just thinking it would be a good release since it will be supported for the next three years -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From eric.b.pratt at gmail.com Thu Mar 17 04:03:55 2016 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Wed, 16 Mar 2016 21:03:55 -0700 Subject: [Slackbuilds-users] Updating slackbuilds In-Reply-To: References: <56E63883.2080604@slackbuilds.org> <56E649F9.1050207@slackbuilds.org> <56E65405.5030300@slackbuilds.org> Message-ID: OK. I've gotten the merge done and tested. If I missed something, let me know. Otherwise, I think it's ready for commit. Thanks again! Eric On Tue, Mar 15, 2016 at 1:13 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2016-03-15 9:09 GMT+01:00 Eric Pratt : > > I was going to try to go to bed, but I decided to hell with it and took a > > look at the script tonight. I like your ffmpeg changes so we should > > probably add those back in. Also, the diff you sent doesn't seem to > include > > your previous find line for the symbol stripping. > > > > -find $PKG | xargs file | grep -e "executable" -e "shared object" | grep > ELF > > \ > > +find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared > object" > > | grep ELF \ > > > > I think your version is better and we should probably go with that. If > > you'd like, I can put together a updated slackbuild and email it to this > > thread. Or if you prefer, you can make the changes in your repository > and > > push them through on your next commit. We'll go with whatever you think > is > > best. > > IMHO, the first option is better: just email a new slackbuild with the > modifications you think are best to this thread. > thanks to you for having a look at my stuff! > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: vice.tar.gz Type: application/x-gzip Size: 8428 bytes Desc: not available URL: From ozan.turkyilmaz at gmail.com Thu Mar 17 16:13:33 2016 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Thu, 17 Mar 2016 21:13:33 +0500 Subject: [Slackbuilds-users] MKVtoolnix and KildClient Updates Message-ID: Patches are attached. KildClient has a new require now. -- Ozan, BSc, BEng -------------- next part -------------- A non-text attachment was scrubbed... Name: kildclient.patch Type: text/x-patch Size: 2220 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mktoolnix.patch Type: text/x-patch Size: 1071 bytes Desc: not available URL: From willysr at slackbuilds.org Thu Mar 17 18:39:45 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 18 Mar 2016 01:39:45 +0700 Subject: [Slackbuilds-users] MKVtoolnix and KildClient Updates In-Reply-To: References: Message-ID: <56EAF9F1.1050104@slackbuilds.org> > Patches are attached. KildClient has a new require now. applied to my branch already Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at gmail.com Thu Mar 17 18:41:03 2016 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Fri, 18 Mar 2016 01:41:03 +0700 Subject: [Slackbuilds-users] MKVtoolnix and KildClient Updates In-Reply-To: References: Message-ID: > Patches are attached. KildClient has a new require now. applied to my branch already thanks -- Willy Sudiarto Raharjo From atelszewski at gmail.com Thu Mar 17 18:54:36 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 17 Mar 2016 19:54:36 +0100 Subject: [Slackbuilds-users] qt5 -master and wayland optional dep Message-ID: <56EAFD6C.9060504@gmail.com> Hi, README for qt5 SlackBuild tells that *wayland* is optional dep, but not available at SBo. However, we have *wayland* at SBo in libraries category. Is it a different "wayland" that we have or should the README be corrected to say that "wayland" is actually available at SBo? -- Best regards, Andrzej Telszewski From rob0 at slackbuilds.org Thu Mar 17 19:03:13 2016 From: rob0 at slackbuilds.org (Rob McGee) Date: Thu, 17 Mar 2016 14:03:13 -0500 Subject: [Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17 In-Reply-To: <20160314154446.GV23739@harrier.slackbuilds.org> References: <20160314154446.GV23739@harrier.slackbuilds.org> Message-ID: <20160317190313.GA4447@harrier.slackbuilds.org> The hardware upgrade was completed successfully. But we did not get up on the kernel we wanted, so another reboot will take place in a short while ... this should be a less than two minute outage. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From rworkman at slackbuilds.org Fri Mar 18 04:25:35 2016 From: rworkman at slackbuilds.org (Robby Workman) Date: Thu, 17 Mar 2016 23:25:35 -0500 Subject: [Slackbuilds-users] Brief interruption in service at lists.slackbuilds.org, 2016-03-17 In-Reply-To: <20160317190313.GA4447@harrier.slackbuilds.org> References: <20160314154446.GV23739@harrier.slackbuilds.org> <20160317190313.GA4447@harrier.slackbuilds.org> Message-ID: <20160317232535.2146c334@home.rlworkman.net> On Thu, 17 Mar 2016 14:03:13 -0500 Rob McGee wrote: > The hardware upgrade was completed successfully. But we did not get > up on the kernel we wanted, so another reboot will take place in a > short while ... this should be a less than two minute outage. And that is now done as well. We had 700+ days of uptime when we shut harrier down, and here's to maybe that much more this round. Thanks for the patience, everyone - back to your regularly scheduled programming. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From larryhaja at gmail.com Fri Mar 18 12:13:01 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Fri, 18 Mar 2016 05:13:01 -0700 Subject: [Slackbuilds-users] qt5 -master and wayland optional dep In-Reply-To: <56EAFD6C.9060504@gmail.com> References: <56EAFD6C.9060504@gmail.com> Message-ID: > > README for qt5 SlackBuild tells that *wayland* is optional dep, but not > available at SBo. > > However, we have *wayland* at SBo in libraries category. > > Is it a different "wayland" that we have or should the README be corrected > to say that "wayland" is actually available at SBo? Well, Wayland wasn't available at the time when I first submitted the qt5 slackbuild. The README included in the qt5 source code says Wayland is an optional dependency. I don't see where it is auto detected by the configure script but I do see it being called. So, I guess the README could be updated to say Wayland is now just an optional dependency. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerardo.zamudio at linux.com Sat Mar 19 04:25:11 2016 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Fri, 18 Mar 2016 22:25:11 -0600 Subject: [Slackbuilds-users] Pat endorses SBo Message-ID: <56ECD4A7.3070109@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 See this LQ post: https://www.linuxquestions.org/questions/slackware-14/slackware-14-2-is- coming-but-will-the-slackbuilds-will-also-be-updated-accordingly-4175575 223/#post5517961 He's also mentioned it in the Slackware.com homepage. Guess it's time to update the FAQ? - -- Gerardo Zamudio Linux System Administrator https://gerardozamudio.mx -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJW7NSjAAoJEPbPpamee1lXnGAP/2jmivsTeoitQ0oMq2/nt2rr 1+ncJB//S6xDyDXNlHPZFiUsV4SpFFw+NfBJwg0tzG9j6GJRaU0GWDGHBcd2OHkw ZpymIHvw9XEA3boedlRJsjsaLfZDZnd+miSTx+ZYlGWWhpqZA0p+ISNM/SSnThyp vQaB8wDc1U3oNQ4niRQ2n8SXHjF3INxZW/eJukmZ9b7Xt3eCzun+xLyn1DYj+++j /GLTkkAjuKZY+tiDvVJ9jszaHlgoLKgcUE0/teR7EfdopvS1nDXWCJu61WaHTs4Y m2WBvzOiFMQpUvCk23eHtA5YC4nLI/n5CCyQBTDyRGkq2oqE3kA6FYRLRlFOWkoq eAj5P9WSDDjaYDGvxiaXIcNHZ6G5LdOerTcE/qBl+oc+IH4ok6H3X40GYRX/6sHD xPOHy9dGe6ltguHIIlQCJkQA4ZF+GwiwgEi8w8e0wOlwXHUjg7nMHCFRKfg7LVLq TLPhnEC7Vll+Ze4pnwbttWiSxeOsvPqkiK3PQaH1woYpaQtD3h8MasDvrjelsAhA sGcVE2iASysEuiOL8pJTosVcCPsEENr6NONj55WwhGvc1m2atofqNxWLZxnFsoMT tlehiGm5IR2QjgpJiXL9c0RZgaPr8EPuob3ouyn6iho0lTY7trutshRDXuAopf9E S0ZZ+0kBovL/L5LjWZ4/ =/rbT -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Mar 19 04:26:22 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 Mar 2016 11:26:22 +0700 Subject: [Slackbuilds-users] Pat endorses SBo In-Reply-To: <56ECD4A7.3070109@linux.com> References: <56ECD4A7.3070109@linux.com> Message-ID: <56ECD4EE.4020901@slackbuilds.org> > See this LQ post: > > https://www.linuxquestions.org/questions/slackware-14/slackware-14-2-is- > coming-but-will-the-slackbuilds-will-also-be-updated-accordingly-4175575 > 223/#post5517961 > > He's also mentioned it in the Slackware.com homepage. Guess it's time > to update the FAQ? have you seen the FAQ yet? :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From gerardo.zamudio at linux.com Sat Mar 19 04:31:15 2016 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Fri, 18 Mar 2016 22:31:15 -0600 Subject: [Slackbuilds-users] Pat endorses SBo In-Reply-To: <56ECD4EE.4020901@slackbuilds.org> References: <56ECD4A7.3070109@linux.com> <56ECD4EE.4020901@slackbuilds.org> Message-ID: <56ECD613.3050108@linux.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 03/18/2016 10:26 PM, Willy Sudiarto Raharjo wrote: > > have you seen the FAQ yet? :) > > I had not! You're on top of everything as always, Willy :) Thanks -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJW7NYMAAoJEPbPpamee1lXwW4P/28rV9Gsur0op8Sovx4kf5Ne Fx465VBZ5D/BFqCaGkMc5HqKJ8CF7K5WgZs2rpSHZ6e/N/XBQ2gOs9j9xQmyGDek CPoyNQIc+yJsTG8BERBjfrfCe5o8jD8/3WdU1GoWgm9bGBx+FNN5V3uVd2k5IK8b 9ogiN7Se0YLR3wJHwXhpdg0WXHTFl5nJBdllMpyhKCd4o4S6bKzvxhamzc10IjZW B6BGvjblT6dZBY15YRXSkklpEy8owNyWtQ2UsJcuRA9xqnvMHEBd+6G5t4c7iVzq V8uWhfeAnW+a+9ouIL9r0G/kEJbLvDBzddgsTJcdSdG7dlQom57i/btJT+eh8Pby dbSAM41A/i5kdNpFPADiZxz4HN3tMRyuyk4x5JKEXbTaocYSPw/zpw5nxbYg4saE JAwQcV8M5gPKgOQFjYNQ5vKsRARligWIHvk/Q91h5YddyL3ji3ApS0FNYAmT2y6k sJriwTN8LZMv40f8XJl3nBmeDYLFTUrbAFRu91Y2aTxrSSSub1ZRtl/Pk5vw3voI hgchxyZUto8pDSpMJSdzcT+nRq1oeaQ9S0/qZ3BhaFZoJS2nD47VZWYSy5Q261mY KlFZ/pLGVMWrAVYnKF6pEzCfmzYY290KkT00xmgUZWWg58JhTnhM1Ez1LYrJyZWF HBrh05q9NUEp5AGaZb9b =R/dL -----END PGP SIGNATURE----- From z.coldplayer at gmail.com Sat Mar 19 07:44:43 2016 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sat, 19 Mar 2016 11:44:43 +0400 Subject: [Slackbuilds-users] PRGNAM="calf" VERSION="0.0.60" Message-ID: Hi the program calf has a typo in its slackbuild git diff|cat diff --git a/audio/calf/calf.SlackBuild b/audio/calf/calf.SlackBuild index fe8e9ba..f148517 100644 --- a/audio/calf/calf.SlackBuild +++ b/audio/calf/calf.SlackBuild @@ -60,7 +60,7 @@ rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION -tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $VERSION.tar.gz +tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz cd $PRGNAM-$VERSION chown -R root:root . find -L . \ -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Mar 19 11:35:49 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 Mar 2016 18:35:49 +0700 Subject: [Slackbuilds-users] PRGNAM="calf" VERSION="0.0.60" In-Reply-To: References: Message-ID: <56ED3995.7040204@slackbuilds.org> > Hi the program calf has a typo in its slackbuild > > git diff|cat > diff --git a/audio/calf/calf.SlackBuild b/audio/calf/calf.SlackBuild > index fe8e9ba..f148517 100644 > --- a/audio/calf/calf.SlackBuild > +++ b/audio/calf/calf.SlackBuild > @@ -60,7 +60,7 @@ rm -rf $PKG > mkdir -p $TMP $PKG $OUTPUT > cd $TMP > rm -rf $PRGNAM-$VERSION > -tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $VERSION.tar.gz > +tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/$VERSION.tar.gz > cd $PRGNAM-$VERSION > chown -R root:root . > find -L . \ Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From titopoquito at gmail.com Sat Mar 19 14:09:51 2016 From: titopoquito at gmail.com (titopoquito) Date: Sat, 19 Mar 2016 15:09:51 +0100 Subject: [Slackbuilds-users] enblend-enfuse patch for upcoming Slackware 14.2 Message-ID: <56ED5DAF.3070703@gmail.com> Hi, my SlackBuild of enblend-enfuse refused to compile on a Slackware64-current box. An upgrade solved the problem, but I noticed that it wouldn't build with other Makeflags than "-j1", so I hardcoded and commented that, too. Cheers, Tito -------------- next part -------------- A non-text attachment was scrubbed... Name: enblend-enfuse-for-14.2.diff Type: text/x-patch Size: 1680 bytes Desc: not available URL: From kingbeowulf at gmail.com Sat Mar 19 19:07:01 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 19 Mar 2016 12:07:01 -0700 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: References: <56E5122B.3090505@gmail.com> <56E5B5BF.5070904@gmail.com> Message-ID: <56EDA355.10406@gmail.com> On 03/14/2016 01:26 PM, Matteo Bernardini wrote: > here I applied this small diff to nvidia-switch to make ldconfig happy. > > Actually, that won't really work. Nvidia now ships 2 versions of those files. The $NV_VERSION appended are the non-GLVND versions while the others are the GLVND versions. Whereas we can only have one or the other of libGL (non-GLVND in this case), libEGL and libGLES need the GLVND support libs to work. I will fiddle with it today on RC1. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sat Mar 19 21:07:31 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 19 Mar 2016 14:07:31 -0700 Subject: [Slackbuilds-users] new nvidia 361.28 ready for testing. In-Reply-To: References: <56E5122B.3090505@gmail.com> <56E5B5BF.5070904@gmail.com> Message-ID: <56EDBF93.9070902@gmail.com> On 03/14/2016 01:26 PM, Matteo Bernardini wrote: >> here I applied this small diff to nvidia-switch to make ldconfig happy. >> >> > Actually, that won't really work. ... Ignore my prior email. That patch works. I'm not sure if I need more, or less, coffee today... -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Mar 20 03:23:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 20 Mar 2016 10:23:25 +0700 Subject: [Slackbuilds-users] enblend-enfuse patch for upcoming Slackware 14.2 In-Reply-To: <56ED5DAF.3070703@gmail.com> References: <56ED5DAF.3070703@gmail.com> Message-ID: <56EE17AD.8020100@slackbuilds.org> > my SlackBuild of enblend-enfuse refused to compile on a > Slackware64-current box. An upgrade solved the problem, but I noticed > that it wouldn't build with other Makeflags than "-j1", so I hardcoded > and commented that, too. applied to my branch with minor modifications Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Mar 20 18:01:04 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 20 Mar 2016 11:01:04 -0700 Subject: [Slackbuilds-users] libbluray download URL issues (videolan.org issue) Message-ID: <56EEE560.1090504@gmail.com> FYI, I've been having trouble with wget and http://ftp.videolan.org/pub/videolan/... URLs. It just freezes during lookup. Switching to ftp://ftp.videolan.org/pub/videolan/ works as expected. So far I've wget a number of sources as I convert to 14.2RC1 and recompile everything. Not notices this elsewhere yet. But then maybe its just Comcast and OpenDNS. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Mar 20 18:29:54 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 01:29:54 +0700 Subject: [Slackbuilds-users] libbluray download URL issues (videolan.org issue) In-Reply-To: <56EEE560.1090504@gmail.com> References: <56EEE560.1090504@gmail.com> Message-ID: <56EEEC22.4030104@slackbuilds.org> > I've been having trouble with wget and > > http://ftp.videolan.org/pub/videolan/... > > URLs. It just freezes during lookup. Switching to > > ftp://ftp.videolan.org/pub/videolan/ > > works as expected. So far I've wget a number of sources as I convert > to 14.2RC1 and recompile everything. Not notices this elsewhere yet. > But then maybe its just Comcast and OpenDNS. works fine here just now (using Google DNS) http://ftp.videolan.org/pub/videolan/libbluray/0.9.2/libbluray-0.9.2.tar.bz2 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Mar 20 18:37:29 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 20 Mar 2016 11:37:29 -0700 Subject: [Slackbuilds-users] Malformed roccat-tools download link Message-ID: <56EEEDE9.4080007@gmail.com> As of yesterday: HOMEPAGE="Homepage: http://sourceforge.net/projects/roccat/" --> extra 'Homepage:' text -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Mar 20 18:40:22 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 01:40:22 +0700 Subject: [Slackbuilds-users] Malformed roccat-tools download link In-Reply-To: <56EEEDE9.4080007@gmail.com> References: <56EEEDE9.4080007@gmail.com> Message-ID: <56EEEE96.8010403@slackbuilds.org> > As of yesterday: > > HOMEPAGE="Homepage: http://sourceforge.net/projects/roccat/" > > --> extra 'Homepage:' text Fixed now :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Mar 20 21:39:58 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 20 Mar 2016 22:39:58 +0100 Subject: [Slackbuilds-users] llfuse and attic Message-ID: <56EF18AE.8010209@gmail.com> Hi, The update of llfuse in the -master from version 0.40 to 0.43 breaks compatibility with attic. Even if we considered "borg" (https://borgbackup.readthedocs.org/en/stable/) as a replacement for attic, this is what they say in the source code of borg: extras_require = { # llfuse 0.40 (tested, proven, ok), needs FUSE version >= 2.8.0 # llfuse 0.41 (tested shortly, looks ok), needs FUSE version >= 2.8.0 # llfuse 0.42 (tested shortly, looks ok), needs FUSE version >= 2.8.0 # llfuse 1.0 will break API 'fuse': ['llfuse<1.0', ], } So updating llfuse to version higher than 0.40 makes both backup programs somehow not future complete. Any suggestions on what could be done? Is it somehow possible to bundle Python library? -- Best regards, Andrzej Telszewski From kingbeowulf at gmail.com Sun Mar 20 22:56:56 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 20 Mar 2016 15:56:56 -0700 Subject: [Slackbuilds-users] A number of updates for 14.2 RC1 FINAL Message-ID: <56EF2AB8.1090007@gmail.com> Admins, Please review. These are based on yesterday's SBo-master. Rather than spam this list with binaries, tarballs are located: (fast) http://www.koenigcomputers.com/sbo-testing/ (slow) http://www.linuxgalaxy.org/files/sbo-testing/ (note: "slow" sits behind a Comcast 12-15Mbps up on a P4 2GB Slackware 14.1 via dynamic dns. YMMV. "fast" will cost me a few cents.) Important: version updates, functionality edits =============================================== system/nvidia-driver system/nvidia-kernel system/nvidia-legacy304-driver system/nvidia-legacy304-kernel system/nvidia-legacy340-driver system/nvidia-legacy340-kernel Minor: version update, minor edits, new maintainer ================================================== graphics/SweetHome3D multimedia/mlt multimedia/tovid No change. tested on 14.1 RC1 ============================= development/CImg games/jin games/sauerbraten libraries/libavc1394 libraries/libiec61883 misc/vdpauinfo multimedia/dvdauthor multimedia/mjpegtools system/qemu system/xarchiver Thanks, Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Sun Mar 20 23:13:34 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 20 Mar 2016 23:13:34 +0000 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56EF18AE.8010209@gmail.com> References: <56EF18AE.8010209@gmail.com> Message-ID: > So updating llfuse to version higher than 0.40 makes both backup programs > somehow not future complete. Took me five mins to find this. https://github.com/borgbackup/borg/commit/dd6a79553683135c3eaf3bf299ca6ccd1dcc4b3f -D. From kingbeowulf at gmail.com Sun Mar 20 23:24:42 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 20 Mar 2016 16:24:42 -0700 Subject: [Slackbuilds-users] nvidia-kernel 352.63 fix to backport to 14.1 Message-ID: <56EF313A.8040902@gmail.com> Admins, Attached is a patch to fix missing nvidia-uvm.ko compile for x86_64. I still get queries about this - I thought I submitted a patch already. New nvidia-kernel for 14.2 is fixed. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-kernel_typo.diff Type: text/x-patch Size: 719 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 21 00:22:21 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 07:22:21 +0700 Subject: [Slackbuilds-users] nvidia-kernel 352.63 fix to backport to 14.1 In-Reply-To: <56EF313A.8040902@gmail.com> References: <56EF313A.8040902@gmail.com> Message-ID: <56EF3EBD.3010105@slackbuilds.org> > Attached is a patch to fix missing nvidia-uvm.ko compile for x86_64. I > still get queries about this - I thought I submitted a patch already. Applied to my branch for 14.1 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 21 00:31:56 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 07:31:56 +0700 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56EF18AE.8010209@gmail.com> References: <56EF18AE.8010209@gmail.com> Message-ID: <56EF40FC.2010309@slackbuilds.org> > The update of llfuse in the -master from version 0.40 to 0.43 breaks > compatibility with attic. > > Even if we considered "borg" > (https://borgbackup.readthedocs.org/en/stable/) as a replacement for > attic, this is what they say in the source code of borg: > > extras_require = { > # llfuse 0.40 (tested, proven, ok), needs FUSE version >= 2.8.0 > # llfuse 0.41 (tested shortly, looks ok), needs FUSE version >= 2.8.0 > # llfuse 0.42 (tested shortly, looks ok), needs FUSE version >= 2.8.0 > # llfuse 1.0 will break API > 'fuse': ['llfuse<1.0', ], > } > > So updating llfuse to version higher than 0.40 makes both backup > programs somehow not future complete. First, borg is not in our repo (yet) Second, llfuse is considered optional for Attic Third, Attic hasn't been updated since May 2015 and it has stack of issues and pull requests that haven't been processed (probably llfuse compatibility is one of them) Fourth and probably the most important one: this update fix build failure on other package where it's considered hard dependency and probably Fifth, David has managed to find an easy fix for borg :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Mon Mar 21 07:45:14 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 21 Mar 2016 08:45:14 +0100 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56EF40FC.2010309@slackbuilds.org> References: <56EF18AE.8010209@gmail.com> <56EF40FC.2010309@slackbuilds.org> Message-ID: <56EFA68A.3060408@gmail.com> On 21/03/16 01:31, Willy Sudiarto Raharjo wrote: >> The update of llfuse in the -master from version 0.40 to 0.43 breaks >> compatibility with attic. >> >> Even if we considered "borg" >> (https://borgbackup.readthedocs.org/en/stable/) as a replacement for >> attic, this is what they say in the source code of borg: >> >> extras_require = { >> # llfuse 0.40 (tested, proven, ok), needs FUSE version >= 2.8.0 >> # llfuse 0.41 (tested shortly, looks ok), needs FUSE version >= 2.8.0 >> # llfuse 0.42 (tested shortly, looks ok), needs FUSE version >= 2.8.0 >> # llfuse 1.0 will break API >> 'fuse': ['llfuse<1.0', ], >> } >> >> So updating llfuse to version higher than 0.40 makes both backup >> programs somehow not future complete. > > First, borg is not in our repo (yet) It might be a sensible candidate to replace attic. > Second, llfuse is considered optional for Attic Spice is considered optional for QEMU, but trust me, I prefer QEMU with spice. > Third, Attic hasn't been updated since May 2015 and it has stack of > issues and pull requests that haven't been processed (probably llfuse > compatibility is one of them) I've been using Attic for quite some time and I haven't noticed any problems. llfuse was originally submitted to support Attic. It's true that Attic development is stalled. For that reason it's good idea to consider borg. > Fourth and probably the most important one: this update fix build > failure on other package where it's considered hard dependency > > and probably Fifth, David has managed to find an easy fix for borg :) > Easy or not, as you can see from the snippet I sent you, 0.40 is the best version to use. Keep in mind that it is a backup software. -- Best regards, Andrzej Telszewski From marc at mos6581.de Mon Mar 21 08:39:41 2016 From: marc at mos6581.de (Marcel Saegebarth) Date: Mon, 21 Mar 2016 09:39:41 +0100 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56EFA68A.3060408@gmail.com> References: <56EF18AE.8010209@gmail.com> <56EF40FC.2010309@slackbuilds.org> <56EFA68A.3060408@gmail.com> Message-ID: <56EFB34D.3010805@mos6581.de> On 03/21/2016 08:45 AM, Andrzej Telszewski wrote: > Easy or not, as you can see from the snippet I sent you, 0.40 is the > best version to use. Keep in mind that it is a backup software. But if it doesn't build on Slackware 14.2, it would be dropped anyway and mounting the attic archives wouldn't work anymore also. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 21 08:59:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 15:59:02 +0700 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56EFA68A.3060408@gmail.com> References: <56EF18AE.8010209@gmail.com> <56EF40FC.2010309@slackbuilds.org> <56EFA68A.3060408@gmail.com> Message-ID: <56EFB7D6.5030204@slackbuilds.org> > It might be a sensible candidate to replace attic. That's not me to decide because i don't use it it's the maintainer's job to decide about it > Spice is considered optional for QEMU, but trust me, I prefer QEMU with > spice. Again, it's not our job (as admin) to decide. it's user's job to decide which one they need Have a look on ffmpeg SlackBuild script :) > I've been using Attic for quite some time and I haven't noticed any > problems. llfuse was originally submitted to support Attic. > > It's true that Attic development is stalled. For that reason it's good > idea to consider borg. same as first comment ^^ > Easy or not, as you can see from the snippet I sent you, 0.40 is the > best version to use. Keep in mind that it is a backup software. here's what written in llfuse The Python-LLFUSE API is not yet stable and may change from one release to the other. Starting with version 0.42, Python-LLFUSE uses semantic versioning. This means changes in the API will be reflected in an increase of the major version number, i.e. the next backwards-incompatible version will be 1.0. Projects designed for e.g. version 0.42.1 of Python-LLFUSE are thus recommended to declare a dependency on llfuse >= 0.42.1, < 1.0. here's what in borg's source code llfuse<2.0 anyway, llfuse has released 1.0 but this version does introduce incompatible changes Release 1.0 (2016-03-08) Note: The 1.0 version number does not imply any special stability or an API freeze. It's a consequence of switching to semantic versioning, where backwards incompatible changes will always result in increased major version. * Fixed an overflow when accessing the *st_xtime_ns attributes of the ~llfuse.EntryAttributes class from Python on 32-bit systems. * POTENTIAL COMPATIBILITY BREAK: The ~Operations.destroy handler is now called with the global lock acquired. i will leave that to the maintainer to decide -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From laitcg at gmail.com Mon Mar 21 12:29:59 2016 From: laitcg at gmail.com (Jack S. Lai) Date: Mon, 21 Mar 2016 02:29:59 -1000 Subject: [Slackbuilds-users] A number of updates for 14.2 RC1 FINAL In-Reply-To: <56EF2AB8.1090007@gmail.com> References: <56EF2AB8.1090007@gmail.com> Message-ID: On Sun, Mar 20, 2016 at 12:56 PM, King Beowulf wrote: > Important: version updates, functionality edits > =============================================== > system/nvidia-driver > system/nvidia-kernel > > works here on RC1 -- When you want a computer system that works, just choose Linux. When you want a computer system that works, just, choose Microsoft. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgrundy at gmail.com Mon Mar 21 13:26:55 2016 From: bgrundy at gmail.com (Barry Grundy) Date: Mon, 21 Mar 2016 09:26:55 -0400 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) Message-ID: I've been slow testing my SlackBuilds, but here's what I have now: Need version bump - source is no longer available for older versions: libraries/libbde libraries/libesedb libraries/libevt libraries/libevtx libraries/libfwsi libraries/liblnk libraries/libmsiecf libraries/libolecf libraries/libqcow libraries/libregf libraries/libsigscan libraries/libsmdev libraries/libsmraw libraries/libvhdi libraries/libvmdk libraries/libvshadow Need version bump - fatal object error (compiles, but does not work - updated Sleuthkit is a dep): python/pytsk system/sleuthkit The above listed tarballs are located here: http://www.linuxleo.com/Files/14.2RC1NEW/ None of these are critical packages, so if it's a bit late for so many updates, I can wait to upload through the normal process. These two should be removed. The source is no longer available, and the new versions have a much longer list of deps that need to be added to SBo. I'll resubmit when general submission are open again. python/dfvfs python/plaso These have all been tested from master on the most recent 14.2RC1: libraries/afflib libraries/libewf libraries/liblightgrep libraries/libpff python/bencode python/binplist python/construct python/dpkt python/hachoir-core python/hachoir-metadata python/hachoir-parser python/pyparsing system/bulk_extractor system/distorm3 system/foremost system/lzip (Note lzip was not in the master repo, but built and installed fine from the 14.1 repo). system/volatility Thanks, Barry -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 21 15:10:30 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 22:10:30 +0700 Subject: [Slackbuilds-users] A number of updates for 14.2 RC1 FINAL In-Reply-To: <56EF2AB8.1090007@gmail.com> References: <56EF2AB8.1090007@gmail.com> Message-ID: <56F00EE6.8000700@slackbuilds.org> > Minor: version update, minor edits, new maintainer > ================================================== > graphics/SweetHome3D > multimedia/mlt approved > multimedia/tovid i see no change besides one line of copyright with a typo (Vancoiuver) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 21 15:19:28 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 22:19:28 +0700 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) In-Reply-To: References: Message-ID: <56F01100.3060604@slackbuilds.org> > The above listed tarballs are located here: > http://www.linuxleo.com/Files/14.2RC1NEW/ It returns: Forbidden You don't have permission to access /Files/14.2RC1NEW/ on this server. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Mon Mar 21 15:42:12 2016 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 21 Mar 2016 15:42:12 +0000 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) In-Reply-To: References: Message-ID: > These two should be removed. The source is no longer available, and the new > versions have a much longer list of deps that need to be added to SBo. I'll > resubmit when general submission are open again. > > python/dfvfs > python/plaso The awesome sbosrcarch has a copy of plaso, so we could just change DOWNLOAD instead of removing it. http://slackware.uk/sbosrcarch/by-name/python/plaso/plaso-1.2.0.tar.gz dfvfs isn't at sbosrcarch (maybe because it's quite large), but I still have a copy and can put it on SlackBuilds Direct Links if you like? Thanks -D. From bgrundy at gmail.com Mon Mar 21 16:37:47 2016 From: bgrundy at gmail.com (Barry Grundy) Date: Mon, 21 Mar 2016 12:37:47 -0400 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) In-Reply-To: <56F01100.3060604@slackbuilds.org> References: <56F01100.3060604@slackbuilds.org> Message-ID: Ah. I only tested with wget on individual files. My apologies. Please try again, it should work now. Barry On Mon, Mar 21, 2016 at 11:19 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > The above listed tarballs are located here: > > http://www.linuxleo.com/Files/14.2RC1NEW/ > > It returns: Forbidden > > You don't have permission to access /Files/14.2RC1NEW/ on this server. > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgrundy at gmail.com Mon Mar 21 16:47:59 2016 From: bgrundy at gmail.com (Barry Grundy) Date: Mon, 21 Mar 2016 12:47:59 -0400 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) In-Reply-To: References: Message-ID: On Mon, Mar 21, 2016 at 11:42 AM, David Spencer < baildon.research at googlemail.com> wrote: > > > python/dfvfs > > python/plaso > > The awesome sbosrcarch has a copy of plaso, so we could just change > DOWNLOAD instead of removing it. > http://slackware.uk/sbosrcarch/by-name/python/plaso/plaso-1.2.0.tar.gz > > dfvfs isn't at sbosrcarch (maybe because it's quite large), but I > still have a copy and can put it on SlackBuilds Direct Links if you > like? I appreciate that. I've moved on to plaso 1.4, and if the other libraries are approved for update, then I'm not sure dfvfs will compile (I'd need to test it). I'm okay with waiting, especially if the updates to the libYAL packages are approved. The SlackBuilds for the new versions are already complete (but not for all the deps). I won't be waiting long to get them uploaded when general submissions are open again. On another note, that sbosrcarch is interesting. I wish I'd have known that was there a few times past... Barry -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 21 16:48:48 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 21 Mar 2016 23:48:48 +0700 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) In-Reply-To: References: Message-ID: <56F025F0.7090709@slackbuilds.org> > I appreciate that. I've moved on to plaso 1.4, and if the other libraries > are approved for update, then I'm not sure dfvfs will compile (I'd need to > test it). I'm okay with waiting, especially if the updates to the libYAL > packages are approved. The SlackBuilds for the new versions are already > complete (but not for all the deps). I won't be waiting long to get them > uploaded when general submissions are open again. working on it now :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Mon Mar 21 17:54:48 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 21 Mar 2016 11:54:48 -0600 Subject: [Slackbuilds-users] gtkimageview cant compile. Message-ID: I cant compile gtkimageview... running slackware64 current with multilib. dont know what other info to include. thank you. gcc -DPACKAGE_NAME=\"gtkimageview\" -DPACKAGE_TARNAME=\"gtkimageview\" -DPACKAGE_VERSION=\"1.6.4\" "-DPACKAGE_STRING=\"gtkimageview 1.6.4\"" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE=\"gtkimageview\" -DVERSION=\"1.6.4\" -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -I. -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -O2 -fPIC -Wall -Werror -std=c99 -Wmissing-prototypes -MT gtkimagescrollwin.lo -MD -MP -MF .deps/gtkimagescrollwin.Tpo -c gtkimagescrollwin.c -fPIC -DPIC -o .libs/gtkimagescrollwin.o gtkimagescrollwin.c: In function 'gtk_image_scroll_win_init': gtkimagescrollwin.c:297:9: error: 'gdk_pixbuf_new_from_inline' is deprecated [-Werror=deprecated-declarations] gdk_pixbuf_new_from_inline (-1, nav_button, FALSE, NULL); ^ In file included from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:33:0, from /usr/include/gtk-2.0/gdk/gdkpixbuf.h:37, from /usr/include/gtk-2.0/gdk/gdkcairo.h:28, from /usr/include/gtk-2.0/gdk/gdk.h:33, from gtkimagescrollwin.h:27, from gtkimagescrollwin.c:41: /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:314:12: note: declared here GdkPixbuf* gdk_pixbuf_new_from_inline (gint data_length, ^ gtkimagescrollwin.c:299:9: error: 'gdk_pixbuf_new_from_inline' is deprecated [-Werror=deprecated-declarations] gdk_pixbuf_new_from_inline (-1, nav_button_hc, FALSE, NULL); ^ In file included from /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf.h:33:0, from /usr/include/gtk-2.0/gdk/gdkpixbuf.h:37, from /usr/include/gtk-2.0/gdk/gdkcairo.h:28, from /usr/include/gtk-2.0/gdk/gdk.h:33, from gtkimagescrollwin.h:27, from gtkimagescrollwin.c:41: /usr/include/gdk-pixbuf-2.0/gdk-pixbuf/gdk-pixbuf-core.h:314:12: note: declared here GdkPixbuf* gdk_pixbuf_new_from_inline (gint data_length, ^ cc1: all warnings being treated as errors Makefile:361: recipe for target 'gtkimagescrollwin.lo' failed make[2]: *** [gtkimagescrollwin.lo] Error 1 make[2]: Leaving directory '/tmp/SBo/gtkimageview-1.6.4/src' Makefile:261: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/tmp/SBo/gtkimageview-1.6.4/src' Makefile:282: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 gtkimageview: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 21 18:09:40 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 22 Mar 2016 01:09:40 +0700 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) In-Reply-To: References: Message-ID: <56F038E4.7070906@slackbuilds.org> > These two should be removed. The source is no longer available, and the > new versions have a much longer list of deps that need to be added to SBo. > I'll resubmit when general submission are open again. > > python/dfvfs missing deps: pycrypto (available in SBo) pyfsntfs (not yet available in SBo) pyvslvm (not yet available in SBo) if you can add those last two, it's enough to build the latest version of dfvfs (20160306) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Mar 21 18:14:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 22 Mar 2016 01:14:53 +0700 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: References: Message-ID: <56F03A1D.2020305@slackbuilds.org> > I cant compile gtkimageview... running slackware64 current with multilib. > dont know what other info to include. thank you. try https://slackbuilds.org/faq/#multilib it works fine on x86_64 gtkimageview: MD5SUM check for gtkimageview-1.6.4.tar.gz ... OK Building package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK Installing package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From bgrundy at gmail.com Mon Mar 21 20:22:42 2016 From: bgrundy at gmail.com (Barry Grundy) Date: Mon, 21 Mar 2016 16:22:42 -0400 Subject: [Slackbuilds-users] Tested SlackBuilds with Needed Updates (can wait) In-Reply-To: <56F038E4.7070906@slackbuilds.org> References: <56F038E4.7070906@slackbuilds.org> Message-ID: On Mon, Mar 21, 2016 at 2:09 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > missing deps: > pycrypto (available in SBo) > pyfsntfs (not yet available in SBo) > pyvslvm (not yet available in SBo) > > if you can add those last two, it's enough to build the latest version > of dfvfs (20160306) That is correct, sir. But dfvfs (for most people) is simply a dep for plaso. Even with the updated dfvfs, plaso still has a number of other new dependencies. The libYAL packages, however, are quite useful on their own, which is why I wanted to get them done. I'll certainly continue working on the full set, just wanted to make sure I got the others in before it became too much of a PITA for the admins. Thanks, Barry -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Mon Mar 21 21:24:11 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 21 Mar 2016 14:24:11 -0700 Subject: [Slackbuilds-users] freerdp fails compile on 14.2 RC1 Message-ID: after switching to RC1, I needed to rdp into a windows7 box. With 14.1 and KRDC/rdesktop all was well. Now KRDC needs another rdp client, not included. From LQ post, freerdp should do it, but it kicks compile error on gstreamer. I didn't see anything on SBo master. Hard to see stuff on the iphone in line for a Billary talk. thanks, Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Mon Mar 21 23:05:08 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 21 Mar 2016 17:05:08 -0600 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: <56F03A1D.2020305@slackbuilds.org> References: <56F03A1D.2020305@slackbuilds.org> Message-ID: doesnt work here =( On Mon, Mar 21, 2016 at 12:14 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I cant compile gtkimageview... running slackware64 current with multilib. > > dont know what other info to include. thank you. > > try > https://slackbuilds.org/faq/#multilib > > it works fine on x86_64 > > gtkimageview: > MD5SUM check for gtkimageview-1.6.4.tar.gz ... OK > Building package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK > Installing package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Mon Mar 21 23:40:57 2016 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 21 Mar 2016 23:40:57 +0000 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: References: <56F03A1D.2020305@slackbuilds.org> Message-ID: Fernando, you should use the git master for -current. See https://slackbuilds.org/cgit/slackbuilds/tree/libraries/gtkimageview -D. On 21 March 2016 at 23:05, Fernando Lopez wrote: > doesnt work here =( > > On Mon, Mar 21, 2016 at 12:14 PM, Willy Sudiarto Raharjo > wrote: >> >> > I cant compile gtkimageview... running slackware64 current with >> > multilib. >> > dont know what other info to include. thank you. >> >> try >> https://slackbuilds.org/faq/#multilib >> >> it works fine on x86_64 >> >> gtkimageview: >> MD5SUM check for gtkimageview-1.6.4.tar.gz ... OK >> Building package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK >> Installing package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK >> >> >> -- >> Willy Sudiarto Raharjo >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From fernando.lopezjr at gmail.com Mon Mar 21 23:51:46 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 21 Mar 2016 17:51:46 -0600 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: References: <56F03A1D.2020305@slackbuilds.org> Message-ID: same thing happens =( On Mon, Mar 21, 2016 at 5:40 PM, David Spencer < baildon.research at googlemail.com> wrote: > Fernando, you should use the git master for -current. > See https://slackbuilds.org/cgit/slackbuilds/tree/libraries/gtkimageview > > -D. > > > On 21 March 2016 at 23:05, Fernando Lopez > wrote: > > doesnt work here =( > > > > On Mon, Mar 21, 2016 at 12:14 PM, Willy Sudiarto Raharjo > > wrote: > >> > >> > I cant compile gtkimageview... running slackware64 current with > >> > multilib. > >> > dont know what other info to include. thank you. > >> > >> try > >> https://slackbuilds.org/faq/#multilib > >> > >> it works fine on x86_64 > >> > >> gtkimageview: > >> MD5SUM check for gtkimageview-1.6.4.tar.gz ... OK > >> Building package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK > >> Installing package gtkimageview-1.6.4-x86_64-3_SBo.tgz ... OK > >> > >> > >> -- > >> Willy Sudiarto Raharjo > >> > >> > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > >> FAQ - http://slackbuilds.org/faq/ > >> > >> > > > > > > > > -- > > > > ------------ > > Regards, > > Fernando Lopez Jr. > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Mar 22 03:01:42 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 22 Mar 2016 10:01:42 +0700 Subject: [Slackbuilds-users] freerdp fails compile on 14.2 RC1 In-Reply-To: References: Message-ID: <56F0B596.4090309@slackbuilds.org> > after switching to RC1, I needed to rdp into a windows7 box. With 14.1 and > KRDC/rdesktop all was well. Now KRDC needs another rdp client, not > included. From LQ post, freerdp should do it, but it kicks compile error on > gstreamer. I didn't see anything on SBo master. Hard to see stuff on the > iphone in line for a Billary talk. tested on x86_64 ffmpeg: MD5SUM check for ffmpeg-2.8.6.tar.xz ... OK Building package ffmpeg-2.8.6-x86_64_custom-2_SBo.tgz ... OK Installing package ffmpeg-2.8.6-x86_64_custom-2_SBo.tgz ... OK freerdp: MD5SUM check for 1.2.0-beta1+android9.tar.gz ... OK Building package freerdp-1.2.0_beta1_android9-x86_64-4_SBo.tgz ... OK Installing package freerdp-1.2.0_beta1_android9-x86_64-4_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Tue Mar 22 06:41:14 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 21 Mar 2016 23:41:14 -0700 Subject: [Slackbuilds-users] freerdp fails compile on 14.2 RC1 In-Reply-To: <56F0B596.4090309@slackbuilds.org> References: <56F0B596.4090309@slackbuilds.org> Message-ID: <56F0E90A.4040500@gmail.com> On 03/21/2016 08:01 PM, Willy Sudiarto Raharjo wrote: >> after switching to RC1, I needed to rdp into a windows7 box. With 14.1 and >> KRDC/rdesktop all was well. Now KRDC needs another rdp client, not >> included. From LQ post, freerdp should do it, but it kicks compile error on >> gstreamer. I didn't see anything on SBo master. Hard to see stuff on the >> iphone in line for a Billary talk. > > tested on x86_64 > > ffmpeg: > MD5SUM check for ffmpeg-2.8.6.tar.xz ... OK > Building package ffmpeg-2.8.6-x86_64_custom-2_SBo.tgz ... OK > Installing package ffmpeg-2.8.6-x86_64_custom-2_SBo.tgz ... OK > > freerdp: > MD5SUM check for 1.2.0-beta1+android9.tar.gz ... OK > Building package freerdp-1.2.0_beta1_android9-x86_64-4_SBo.tgz ... OK > Installing package freerdp-1.2.0_beta1_android9-x86_64-4_SBo.tgz ... OK > > oops. my bad. forgot to correctly copy script. BTW, freerdp sucks. Doesn't connect reliably and KRDC doesn't seem to work with it. I'll poke around some more and take this rant to LQ. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Mar 22 08:16:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 22 Mar 2016 15:16:02 +0700 Subject: [Slackbuilds-users] freerdp fails compile on 14.2 RC1 In-Reply-To: <56F0E90A.4040500@gmail.com> References: <56F0B596.4090309@slackbuilds.org> <56F0E90A.4040500@gmail.com> Message-ID: <56F0FF42.4010500@slackbuilds.org> > BTW, freerdp sucks. Doesn't connect reliably and KRDC doesn't seem to > work with it. I'll poke around some more and take this rant to LQ. rdesktop ? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Tue Mar 22 12:54:58 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 22 Mar 2016 12:54:58 +0000 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: References: <56F03A1D.2020305@slackbuilds.org> Message-ID: > same thing happens =( Are you sure you are doing the right thing? Run these commands (as root) mkdir /tmp/gtksv cd /tmp/gtksv wget https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/gtkimageview.SlackBuild wget https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/disable_Werror_for_gdk_pixbuf.patch wget https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/slack-desc wget http://ponce.cc/slackware/sources/repo/gtkimageview-1.6.4.tar.gz sh ./gtkimageview.SlackBuild -D. From fernando.lopezjr at gmail.com Tue Mar 22 20:27:37 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 22 Mar 2016 14:27:37 -0600 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: References: <56F03A1D.2020305@slackbuilds.org> Message-ID: yes. su. enter password. sbopkg. search: gtkimageview. install download, compile. and it breaks while compiling... I have switched to the "git current" and cleared the cached and sync the new packages. On Tue, Mar 22, 2016 at 6:54 AM, David Spencer < baildon.research at googlemail.com> wrote: > > same thing happens =( > > Are you sure you are doing the right thing? > Run these commands (as root) > > mkdir /tmp/gtksv > cd /tmp/gtksv > wget > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/gtkimageview.SlackBuild > wget > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/disable_Werror_for_gdk_pixbuf.patch > wget > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/slack-desc > wget http://ponce.cc/slackware/sources/repo/gtkimageview-1.6.4.tar.gz > sh ./gtkimageview.SlackBuild > > -D. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Tue Mar 22 21:41:54 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 22 Mar 2016 21:41:54 +0000 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: References: <56F03A1D.2020305@slackbuilds.org> Message-ID: > yes. su. enter password. sbopkg. search: gtkimageview. install download, > compile. and it breaks while compiling... ****NO**** That is NOT the right thing. For current you must use git master. DO NOT USE SBOPKG [1] USE THESE COMMANDS mkdir /tmp/gtksv cd /tmp/gtksv wget https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/gtkimageview.SlackBuild wget https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/disable_Werror_for_gdk_pixbuf.patch wget https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/slack-desc wget http://ponce.cc/slackware/sources/repo/gtkimageview-1.6.4.tar.gz sh ./gtkimageview.SlackBuild -D. [1] Yes, I know it is possible to configure sbopkg to use git master, but I don't want to confuse the OP when 14.2 will be out "real soon now". > I have switched to the "git current" and cleared the cached and sync the new > packages. > > On Tue, Mar 22, 2016 at 6:54 AM, David Spencer > wrote: >> >> > same thing happens =( >> >> Are you sure you are doing the right thing? >> Run these commands (as root) >> >> mkdir /tmp/gtksv >> cd /tmp/gtksv >> wget >> https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/gtkimageview.SlackBuild >> wget >> https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/disable_Werror_for_gdk_pixbuf.patch >> wget >> https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/slack-desc >> wget http://ponce.cc/slackware/sources/repo/gtkimageview-1.6.4.tar.gz >> sh ./gtkimageview.SlackBuild >> >> -D. >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From fernando.lopezjr at gmail.com Tue Mar 22 21:45:47 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 22 Mar 2016 15:45:47 -0600 Subject: [Slackbuilds-users] gtkimageview cant compile. In-Reply-To: References: <56F03A1D.2020305@slackbuilds.org> Message-ID: that did it. thank you very much and sorry for the confusion i thought it was the same. On Tue, Mar 22, 2016 at 3:41 PM, David Spencer < baildon.research at googlemail.com> wrote: > > yes. su. enter password. sbopkg. search: gtkimageview. install download, > > compile. and it breaks while compiling... > > ****NO**** > > That is NOT the right thing. > For current you must use git master. > DO NOT USE SBOPKG [1] > USE THESE COMMANDS > > mkdir /tmp/gtksv > cd /tmp/gtksv > wget > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/gtkimageview.SlackBuild > wget > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/disable_Werror_for_gdk_pixbuf.patch > wget > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/slack-desc > wget http://ponce.cc/slackware/sources/repo/gtkimageview-1.6.4.tar.gz > sh ./gtkimageview.SlackBuild > > -D. > > [1] Yes, I know it is possible to configure sbopkg to use git master, > but I don't want to confuse the OP when 14.2 will be out "real soon > now". > > > > > > > > I have switched to the "git current" and cleared the cached and sync the > new > > packages. > > > > On Tue, Mar 22, 2016 at 6:54 AM, David Spencer > > wrote: > >> > >> > same thing happens =( > >> > >> Are you sure you are doing the right thing? > >> Run these commands (as root) > >> > >> mkdir /tmp/gtksv > >> cd /tmp/gtksv > >> wget > >> > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/gtkimageview.SlackBuild > >> wget > >> > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/disable_Werror_for_gdk_pixbuf.patch > >> wget > >> > https://slackbuilds.org/cgit/slackbuilds/plain/libraries/gtkimageview/slack-desc > >> wget http://ponce.cc/slackware/sources/repo/gtkimageview-1.6.4.tar.gz > >> sh ./gtkimageview.SlackBuild > >> > >> -D. > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > >> FAQ - http://slackbuilds.org/faq/ > >> > > > > > > > > -- > > > > ------------ > > Regards, > > Fernando Lopez Jr. > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Wed Mar 23 07:20:44 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 23 Mar 2016 00:20:44 -0700 Subject: [Slackbuilds-users] freerdp fails compile on 14.2 RC1 In-Reply-To: <56F0FF42.4010500@slackbuilds.org> References: <56F0B596.4090309@slackbuilds.org> <56F0E90A.4040500@gmail.com> <56F0FF42.4010500@slackbuilds.org> Message-ID: <56F243CC.5080607@gmail.com> On 03/22/2016 01:16 AM, Willy Sudiarto Raharjo wrote: >> BTW, freerdp sucks. Doesn't connect reliably and KRDC doesn't seem to >> work with it. I'll poke around some more and take this rant to LQ. > > rdesktop ? > yes, works well (unlike freerdp). With KRDC gui, on 14.1, I could have rdesktop/KRDC full screen on monitor 1, and Slackware on monitor 2. rdesktop/CLI full screen turns off monitor 2. I have the 2 monitors as an extended desktop with monitor 1 as the primary (Nvidia). I was hoping to a simple GUI OOTB experience without added software. You know, like in 14.1 Did I mention how much freerdp sucks donkey balls? -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Mar 26 10:12:54 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 26 Mar 2016 17:12:54 +0700 Subject: [Slackbuilds-users] package for grab: sage Message-ID: <56F660A6.1080303@slackbuilds.org> Anyone who is interested to maintain sage please let me know NOTE: This package takes quite a long time and requires big space to build -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mherda at slackword.net Sat Mar 26 10:45:19 2016 From: mherda at slackword.net (Marcin Herda) Date: Sat, 26 Mar 2016 10:45:19 +0000 Subject: [Slackbuilds-users] i3wm and others Message-ID: <56F6683F.6020108@slackword.net> Hi all, Unfortunately, being more and more busy with work and other projects, I have less and less time on maintaining i3-related SlackBuilds. It's still a wm of my choice but think someone else will give it more love that I'm able to at the moment. All five should ideally be taken by 1 person as all of them are needed by i3wm. i3 yajl i3status perl-AnyEvent-I3 perl-AnyEvent Those two are unrelated to i3wm but feel free to grab them as well: detox dwb (a webkit based browser) On a related note, this might be of interest for a person who will take over i3. I have recently received this email: https://github.com/Boruch-Baum/morc_menu Hi, This is a heads up about a categorized application menu that I wrote for i3 - it simulates the functionality of an Openbox / Fluxbox style menu without requiring the dependencies. Currently I'm packaging it for manjaro (that's how I got introduced to i3), but it's just a few files, and it includes a Makefile, so it should be easy to install on different distributions, including slackware. I figured that since you were listed as the i3 maintainer for slackbuilds, you might be interested, and you might have suggestions where to let people know about the package. Regards, Thank you. regards Marcin From sbolokanov at abv.bg Sat Mar 26 13:33:18 2016 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Sat, 26 Mar 2016 15:33:18 +0200 (EET) Subject: [Slackbuilds-users] Xonotic update Message-ID: <1847289541.553319.1458999198064.JavaMail.apache@nm51.abv.bg> Here is Xonotic update for 0.8.1: https://github.com/sbolokanov/sbo-clone/commit/ad4158e1b27f2a02dbf0f73a7e808f501ce9a38e -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Sat Mar 26 13:35:41 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 26 Mar 2016 14:35:41 +0100 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <56F6683F.6020108@slackword.net> References: <56F6683F.6020108@slackword.net> Message-ID: <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> Hi Marcin, > Unfortunately, being more and more busy with work and other projects, > I have less and less time on maintaining i3-related SlackBuilds. It's > still a wm of my choice but think someone else will give it more love > that I'm able to at the moment. > > All five should ideally be taken by 1 person as all of them are needed > by i3wm. > i3 > yajl > i3status > perl-AnyEvent-I3 > perl-AnyEvent I'm using i3, and could maintain i3, yail and i3status. The perl-packages aren't mentioned anywhere on i3wm.org, and i don't know/use them. Do you use them, or are they just there for completeness? Franzen From mherda at slackword.net Sat Mar 26 13:50:59 2016 From: mherda at slackword.net (Marcin Herda) Date: Sat, 26 Mar 2016 13:50:59 +0000 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> References: <56F6683F.6020108@slackword.net> <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> Message-ID: <56F693C3.7050201@slackword.net> Hi Franzen, The perl packages are not hard runtime dependencies but as of i3 4.8 they are required for, among others, the functionality of saving and restoring layouts in i3. Without them i3 would lose its best, IMHO, features. regards Marcin On 03/26/2016 01:35 PM, Franzen wrote: > Hi Marcin, > >> Unfortunately, being more and more busy with work and other projects, >> I have less and less time on maintaining i3-related SlackBuilds. It's >> still a wm of my choice but think someone else will give it more love >> that I'm able to at the moment. >> >> All five should ideally be taken by 1 person as all of them are >> needed by i3wm. >> i3 >> yajl >> i3status >> perl-AnyEvent-I3 >> perl-AnyEvent > > I'm using i3, and could maintain i3, yail and i3status. > The perl-packages aren't mentioned anywhere on i3wm.org, and i don't > know/use them. Do you use them, or are they just there for completeness? > > > Franzen > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From slackbuilds at schoepfer.info Sat Mar 26 14:41:01 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 26 Mar 2016 15:41:01 +0100 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <56F693C3.7050201@slackword.net> References: <56F6683F.6020108@slackword.net> <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> <56F693C3.7050201@slackword.net> Message-ID: <0fab58f8695ffab29e7881141e817e6a@schoepfer.info> Hi Marcin, > The perl packages are not hard runtime dependencies but as of i3 4.8 > they are required for, among others, the functionality of saving and > restoring layouts in i3. Without them i3 would lose its best, IMHO, > features. Ok, i'll do that, too. Franzen From mherda at slackword.net Sat Mar 26 14:54:43 2016 From: mherda at slackword.net (Marcin Herda) Date: Sat, 26 Mar 2016 14:54:43 +0000 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <0fab58f8695ffab29e7881141e817e6a@schoepfer.info> References: <56F6683F.6020108@slackword.net> <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> <56F693C3.7050201@slackword.net> <0fab58f8695ffab29e7881141e817e6a@schoepfer.info> Message-ID: <56F6A2B3.2010508@slackword.net> Great. Thank you. Have fun! regards Marcin On 03/26/2016 02:41 PM, Franzen wrote: > Hi Marcin, > >> The perl packages are not hard runtime dependencies but as of i3 4.8 >> they are required for, among others, the functionality of saving and >> restoring layouts in i3. Without them i3 would lose its best, IMHO, >> features. > > Ok, i'll do that, too. > > Franzen > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From slackbuilds at schoepfer.info Sun Mar 27 14:59:48 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 27 Mar 2016 16:59:48 +0200 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <56F6A2B3.2010508@slackword.net> References: <56F6683F.6020108@slackword.net> <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> <56F693C3.7050201@slackword.net> <0fab58f8695ffab29e7881141e817e6a@schoepfer.info> <56F6A2B3.2010508@slackword.net> Message-ID: <5550a0b49ae72a9e5e89ff81287e47f9@schoepfer.info> Hi, here are the diffs from the updated packages i took over from Marcin. Franzen -------------- next part -------------- A non-text attachment was scrubbed... Name: yajl.diff Type: text/x-diff Size: 1837 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: perl-AnyEvent.diff Type: text/x-diff Size: 2365 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: perl-AnyEvent-I3.diff Type: text/x-diff Size: 2417 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: i3status.diff Type: text/x-diff Size: 2212 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: i3.diff Type: text/x-diff Size: 2502 bytes Desc: not available URL: From z.coldplayer at gmail.com Mon Mar 28 06:20:26 2016 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Mon, 28 Mar 2016 10:20:26 +0400 Subject: [Slackbuilds-users] package for grab: sage In-Reply-To: <56F660A6.1080303@slackbuilds.org> References: <56F660A6.1080303@slackbuilds.org> Message-ID: Hi, I'm willing to take over, this is an important component of my Slack boxes. On 26 Mar 2016 2:13 pm, "Willy Sudiarto Raharjo" wrote: > Anyone who is interested to maintain sage please let me know > > NOTE: This package takes quite a long time and requires big space to build > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 28 14:18:28 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 28 Mar 2016 21:18:28 +0700 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <5550a0b49ae72a9e5e89ff81287e47f9@schoepfer.info> References: <56F6683F.6020108@slackword.net> <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> <56F693C3.7050201@slackword.net> <0fab58f8695ffab29e7881141e817e6a@schoepfer.info> <56F6A2B3.2010508@slackword.net> <5550a0b49ae72a9e5e89ff81287e47f9@schoepfer.info> Message-ID: <56F93D34.9030303@slackbuilds.org> > here are the diffs from the updated packages i took over from Marcin. perl-AnyEvent will fail without Net-SSLeay unless you remove the make test, so i'm adding it back -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From navigium at grindcore.ch Mon Mar 28 14:36:49 2016 From: navigium at grindcore.ch (Beni) Date: Mon, 28 Mar 2016 16:36:49 +0200 Subject: [Slackbuilds-users] package for grab: sage In-Reply-To: References: <56F660A6.1080303@slackbuilds.org> Message-ID: <56F94181.2060602@grindcore.ch> Hey all, I tried to upgrade the SlackBuild to sage 7.1 but failed. I just don't understand the build process of sage well enough to patch this together. But let me know if you need testers! I'm a regular Sage user. Beni On 03/28/2016 08:20 AM, Jheengut Pritvi wrote: > Hi, I'm willing to take over, this is an important component of my > Slack boxes. > > On 26 Mar 2016 2:13 pm, "Willy Sudiarto Raharjo" > > wrote: > > Anyone who is interested to maintain sage please let me know > > NOTE: This package takes quite a long time and requires big space to > build > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From willysr at slackbuilds.org Mon Mar 28 14:40:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 28 Mar 2016 21:40:27 +0700 Subject: [Slackbuilds-users] package for grab: sage In-Reply-To: <56F94181.2060602@grindcore.ch> References: <56F660A6.1080303@slackbuilds.org> <56F94181.2060602@grindcore.ch> Message-ID: <56F9425B.4040702@slackbuilds.org> > I tried to upgrade the SlackBuild to sage 7.1 but failed. I just don't > understand the build process of sage well enough to patch this together. > But let me know if you need testers! I'm a regular Sage user. yes, it failed on pynac, which is strange since it was the same problem as in 7.0, but it built perfectly on 7.0, but eventually not in 7.1 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From navigium at grindcore.ch Mon Mar 28 14:43:09 2016 From: navigium at grindcore.ch (Beni) Date: Mon, 28 Mar 2016 16:43:09 +0200 Subject: [Slackbuilds-users] package for grab: sage In-Reply-To: <56F9425B.4040702@slackbuilds.org> References: <56F660A6.1080303@slackbuilds.org> <56F94181.2060602@grindcore.ch> <56F9425B.4040702@slackbuilds.org> Message-ID: <56F942FD.9050208@grindcore.ch> Exactly. I built 7.0 successfully and then failed with 7.1. The weirdest thing is that trying to build 7.1 (just building, not installing) broke my 7.0 install. This package is just very confusing, because it bundles every single dependency in one huge lump. On 03/28/2016 04:40 PM, Willy Sudiarto Raharjo wrote: >> I tried to upgrade the SlackBuild to sage 7.1 but failed. I just don't >> understand the build process of sage well enough to patch this together. >> But let me know if you need testers! I'm a regular Sage user. > > yes, it failed on pynac, which is strange since it was the same problem > as in 7.0, but it built perfectly on 7.0, but eventually not in 7.1 > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From slackbuilds at schoepfer.info Mon Mar 28 15:06:41 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 28 Mar 2016 17:06:41 +0200 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <56F93D34.9030303@slackbuilds.org> References: <56F6683F.6020108@slackword.net> <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> <56F693C3.7050201@slackword.net> <0fab58f8695ffab29e7881141e817e6a@schoepfer.info> <56F6A2B3.2010508@slackword.net> <5550a0b49ae72a9e5e89ff81287e47f9@schoepfer.info> <56F93D34.9030303@slackbuilds.org> Message-ID: <998dd44a46d618d933386a4221792ad9@schoepfer.info> On 2016-03-28 16:18, Willy Sudiarto Raharjo wrote: >> here are the diffs from the updated packages i took over from Marcin. > > perl-AnyEvent will fail without Net-SSLeay unless you remove the make > test, so i'm adding it back Here it builds fine with make test without Net-SSLeay, buildlog attached. While building, there comes: *** This module does not have ANY dependencies, even if it might look *** otherwise. If you are building a distribution package or have *** difficulties installing this package due to dependencies, report this *** to the packager as a bug. On the other hand, Net-SSLeay won't hurt. Franzen -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: perl-AnyEvent.buildlog URL: From willysr at slackbuilds.org Mon Mar 28 15:15:00 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 28 Mar 2016 22:15:00 +0700 Subject: [Slackbuilds-users] i3wm and others In-Reply-To: <56F93D34.9030303@slackbuilds.org> References: <56F6683F.6020108@slackword.net> <108eaf4cf5ae33e734be7b9fe2df97be@schoepfer.info> <56F693C3.7050201@slackword.net> <0fab58f8695ffab29e7881141e817e6a@schoepfer.info> <56F6A2B3.2010508@slackword.net> <5550a0b49ae72a9e5e89ff81287e47f9@schoepfer.info> <56F93D34.9030303@slackbuilds.org> Message-ID: <56F94A74.3070603@slackbuilds.org> > perl-AnyEvent will fail without Net-SSLeay unless you remove the make > test, so i'm adding it back i retested on a clean VM (previously on my desktop) and indeed it built fine without Net-SSLeay, so i remove it now (updated in my branch already) Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mfilpot at gmail.com Mon Mar 28 15:59:13 2016 From: mfilpot at gmail.com (Matthew Fillpot) Date: Mon, 28 Mar 2016 15:59:13 +0000 Subject: [Slackbuilds-users] Xonotic update In-Reply-To: <1847289541.553319.1458999198064.JavaMail.apache@nm51.abv.bg> References: <1847289541.553319.1458999198064.JavaMail.apache@nm51.abv.bg> Message-ID: SlackBuilds admins, The ownership of xonotic script can be transferred to ????? ????????? with the next submission. My son cannot currently maintain this package due to testing time restraints. On Sat, Mar 26, 2016, 7:33 AM ????? ????????? wrote: > Here is Xonotic update for 0.8.1: > > https://github.com/sbolokanov/sbo-clone/commit/ad4158e1b27f2a02dbf0f73a7e808f501ce9a38e > > -- ????? ????????? > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lems at gmx.net Mon Mar 28 18:11:48 2016 From: lems at gmx.net (Leonard Schmidt) Date: Mon, 28 Mar 2016 20:11:48 +0200 Subject: [Slackbuilds-users] Please update abduco, darkhttpd and yash Message-ID: <0Lpbqo-1a8mSJ0J5K-00fNwF@mail.gmx.com> Hello, I hope the attached patches are fine. They update misc/abduco from 0.5 to 0.6, network/darkhttpd from 1.11 to 1.12 and system/yash from 2.40 to 2.41. Leonard -------------- next part -------------- A non-text attachment was scrubbed... Name: abduco-0.5-to-0.6.diff Type: text/x-diff Size: 925 bytes Desc: abduco-0.5-to-0.6.diff URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: darkhttpd-1.11-to-1.12.diff Type: text/x-diff Size: 1227 bytes Desc: darkhttpd-1.11-to-1.12.diff URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: yash-2.40-to-2.41.diff Type: text/x-diff Size: 871 bytes Desc: yash-2.40-to-2.41.diff URL: From slackware at lemintown.eu Mon Mar 28 18:49:18 2016 From: slackware at lemintown.eu (Brian Lemin) Date: Mon, 28 Mar 2016 20:49:18 +0200 Subject: [Slackbuilds-users] weboob Message-ID: <56F97CAE.8010706@lemintown.eu> Greetings, I'd be glad to take over the weboob slackbuild since it has not been updated for years and the current maintainer has not answered me back for a couple of month now. Regards, Brian From info at microlinux.fr Tue Mar 29 04:12:08 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 29 Mar 2016 06:12:08 +0200 Subject: [Slackbuilds-users] spice vs. six Message-ID: <56FA0098.5010004@microlinux.fr> Hi, The 'spice' package should list the 'six' Python module as an explicit dependency, since it won't build without it. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Tue Mar 29 04:20:32 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 29 Mar 2016 11:20:32 +0700 Subject: [Slackbuilds-users] spice vs. six In-Reply-To: <56FA0098.5010004@microlinux.fr> References: <56FA0098.5010004@microlinux.fr> Message-ID: <259CF890-74BD-4044-8E08-CFD023AD50DA@slackbuilds.org> > The 'spice' package should list the 'six' Python module as an explicit > dependency, since it won't build without it It's already have six as a mandatory dependency Please check against master branch -- Willy Sudiarto Raharjo From info at microlinux.fr Tue Mar 29 13:25:22 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 29 Mar 2016 15:25:22 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget Message-ID: <56FA8242.8040001@microlinux.fr> Hi, Whenever I want to download some source tarball from SourceForge using wget, I get permantently redirected until eventually some mirror times out. So I have to reinvoke the command, sometimes ten times in a row, until eventually it works out. This is really getting tiresome. Do you have some workaround for this? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From chris.willing at iinet.net.au Tue Mar 29 14:09:31 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 30 Mar 2016 00:09:31 +1000 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FA8242.8040001@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> Message-ID: <56FA8C9B.5030306@iinet.net.au> On 29/03/16 23:25, Nicolas Kovacs wrote: > Hi, > > Whenever I want to download some source tarball from SourceForge using > wget, I get permantently redirected until eventually some mirror times > out. So I have to reinvoke the command, sometimes ten times in a row, > until eventually it works out. This is really getting tiresome. > > Do you have some workaround for this? I have 'content-disposition = on' in my /etc/wgetrc but in cases like you describe, I find that overriding that setting at the command line often helps i.e. wget --no-content-disposition http://whatever... chris From rshepard at appl-ecosys.com Tue Mar 29 15:53:34 2016 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 29 Mar 2016 08:53:34 -0700 (PDT) Subject: [Slackbuilds-users] Issues Building Chromium Message-ID: I'm trying to build and install chromium from the SBo site to replace Google's Chrome on a Sony Vaio laptop running -14.1/x86_64 and I'm encountering problems I have not been able to resolve. Last evening, the chromium.Slackbuild script ran for 107 minutes and halted with an error when a file in the source tree was not found. I shut down the laptop for the night. The MD5SUMs of the dowloaded .xz file and that reported on SBo are the same. This morning the laptop is _very_ slow responding so I rebooted it. Now, when I run 'time ./chromium.Slackbuild' nothing happens other than the cursor moving to the head of a new line. 'top' shows nothing hogging the CPU or memory. The script not starting is something I've not before encountered so I have no idea where to look for the reason. A clue stick is needed to figure out why these issues suddenly occurred. TIA, Rich From jebrhansen+SBo at gmail.com Tue Mar 29 15:59:57 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 29 Mar 2016 15:59:57 +0000 Subject: [Slackbuilds-users] Issues Building Chromium In-Reply-To: References: Message-ID: The chromium on SBo is extremely old. It would probably be beneficial to use Eric's slackbuild (he also provides pre-built packages). http://www.slackware.com/~alien/slackbuilds/chromium/ As to your issues, have you tried running the slackbuild directly to see if it progresses? On Tue, Mar 29, 2016, 11:53 AM Rich Shepard wrote: > I'm trying to build and install chromium from the SBo site to replace > Google's Chrome on a Sony Vaio laptop running -14.1/x86_64 and I'm > encountering problems I have not been able to resolve. > > Last evening, the chromium.Slackbuild script ran for 107 minutes and > halted with an error when a file in the source tree was not found. I shut > down the laptop for the night. The MD5SUMs of the dowloaded .xz file and > that reported on SBo are the same. > > This morning the laptop is _very_ slow responding so I rebooted it. Now, > when I run 'time ./chromium.Slackbuild' nothing happens other than the > cursor moving to the head of a new line. > > 'top' shows nothing hogging the CPU or memory. > > The script not starting is something I've not before encountered so I > have > no idea where to look for the reason. > > A clue stick is needed to figure out why these issues suddenly occurred. > > TIA, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Tue Mar 29 16:10:05 2016 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 29 Mar 2016 09:10:05 -0700 (PDT) Subject: [Slackbuilds-users] Issues Building Chromium [RESOLVED] In-Reply-To: References: Message-ID: On Tue, 29 Mar 2016, Jeremy Hansen wrote: > The chromium on SBo is extremely old. It would probably be beneficial to > use Eric's slackbuild (he also provides pre-built packages). Jeremy, Yes, the SBo version is the issue. I checked the version on another host and am now downloading Eric's version on the Sony laptop. The sluggishness seems to have resulved itself ... other than the old slackbuild script doing nothing. But, since that subdirectory no longer exists it's not a concern. Thanks for the prompt reply, Rich From 1.41421 at gmail.com Tue Mar 29 16:12:02 2016 From: 1.41421 at gmail.com (JCA) Date: Tue, 29 Mar 2016 10:12:02 -0600 Subject: [Slackbuilds-users] Issues Building Chromium In-Reply-To: References: Message-ID: A generic question on this: Why is it the case that the Chromium in SBo is updated so seldom? Why not just adopt Eric's packages? On Tue, Mar 29, 2016 at 9:59 AM, Jeremy Hansen wrote: > The chromium on SBo is extremely old. It would probably be beneficial to use > Eric's slackbuild (he also provides pre-built packages). > > http://www.slackware.com/~alien/slackbuilds/chromium/ > > As to your issues, have you tried running the slackbuild directly to see if > it progresses? > > > On Tue, Mar 29, 2016, 11:53 AM Rich Shepard > wrote: >> >> I'm trying to build and install chromium from the SBo site to replace >> Google's Chrome on a Sony Vaio laptop running -14.1/x86_64 and I'm >> encountering problems I have not been able to resolve. >> >> Last evening, the chromium.Slackbuild script ran for 107 minutes and >> halted with an error when a file in the source tree was not found. I shut >> down the laptop for the night. The MD5SUMs of the dowloaded .xz file and >> that reported on SBo are the same. >> >> This morning the laptop is _very_ slow responding so I rebooted it. >> Now, >> when I run 'time ./chromium.Slackbuild' nothing happens other than the >> cursor moving to the head of a new line. >> >> 'top' shows nothing hogging the CPU or memory. >> >> The script not starting is something I've not before encountered so I >> have >> no idea where to look for the reason. >> >> A clue stick is needed to figure out why these issues suddenly >> occurred. >> >> TIA, >> >> Rich >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From baildon.research at googlemail.com Tue Mar 29 21:37:32 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 29 Mar 2016 22:37:32 +0100 Subject: [Slackbuilds-users] Issues Building Chromium In-Reply-To: References: Message-ID: > A generic question on this: Why is it the case that the Chromium in > SBo is updated so seldom? Why not just adopt Eric's packages? The Chromium in SBo git master (ready for release with 14.2) is version 48.0.2564.97, and is almost identical to Eric's SlackBuild. The SBo script exists mostly as a convenience for people who want to manage all their packages together, or to fork and maintain their own variant. Because Eric's builds are so good, there is not much incentive to update the SBo script regularly. Another disincentive is the amount of time it takes to build Chromium. It has the longest build time in SBo, and the last time I did a test build for i486, it took 70215 seconds. That's 19 1/2 hours. I don't want to do that every week, and I doubt anybody else does either, possibly including Eric himself ;-) -D. From baildon.research at googlemail.com Tue Mar 29 21:45:02 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 29 Mar 2016 22:45:02 +0100 Subject: [Slackbuilds-users] Xonotic update In-Reply-To: References: <1847289541.553319.1458999198064.JavaMail.apache@nm51.abv.bg> Message-ID: Hi Folks, Willy applied this in his branch before he went on holiday :-) Thanks! -D. From baildon.research at googlemail.com Tue Mar 29 22:04:38 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 29 Mar 2016 23:04:38 +0100 Subject: [Slackbuilds-users] Please update abduco, darkhttpd and yash In-Reply-To: <0Lpbqo-1a8mSJ0J5K-00fNwF@mail.gmx.com> References: <0Lpbqo-1a8mSJ0J5K-00fNwF@mail.gmx.com> Message-ID: > I hope the attached patches are fine. They update misc/abduco from 0.5 > to 0.6, network/darkhttpd from 1.11 to 1.12 and system/yash from 2.40 to 2.41. Yes thanks Leonard, they are fine & applied in my branch! Cheers -D. From baildon.research at googlemail.com Tue Mar 29 22:09:10 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 29 Mar 2016 23:09:10 +0100 Subject: [Slackbuilds-users] weboob In-Reply-To: <56F97CAE.8010706@lemintown.eu> References: <56F97CAE.8010706@lemintown.eu> Message-ID: > I'd be glad to take over the weboob slackbuild since it has not been > updated for years and the current maintainer has not answered me back > for a couple of month now. Thanks Brian, please go ahead, an update would certainly be welcome (e.g. by email). Cheers -D. From 1.41421 at gmail.com Wed Mar 30 01:08:49 2016 From: 1.41421 at gmail.com (JCA) Date: Tue, 29 Mar 2016 19:08:49 -0600 Subject: [Slackbuilds-users] Issues Building Chromium In-Reply-To: References: Message-ID: I was talking about the Chromium in SlackBuilds for 14.1, which seems to be Chromium 31 - a really old version. On Tue, Mar 29, 2016 at 3:37 PM, David Spencer wrote: >> A generic question on this: Why is it the case that the Chromium in >> SBo is updated so seldom? Why not just adopt Eric's packages? > > The Chromium in SBo git master (ready for release with 14.2) is > version 48.0.2564.97, and is almost identical to Eric's SlackBuild. > The SBo script exists mostly as a convenience for people who want to > manage all their packages together, or to fork and maintain their own > variant. > > Because Eric's builds are so good, there is not much incentive to > update the SBo script regularly. Another disincentive is the amount of > time it takes to build Chromium. It has the longest build time in SBo, > and the last time I did a test build for i486, it took 70215 seconds. > That's 19 1/2 hours. I don't want to do that every week, and I doubt > anybody else does either, possibly including Eric himself ;-) > > -D. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From info at microlinux.fr Wed Mar 30 07:04:14 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Mar 2016 09:04:14 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FA8C9B.5030306@iinet.net.au> References: <56FA8242.8040001@microlinux.fr> <56FA8C9B.5030306@iinet.net.au> Message-ID: <56FB7A6E.3080406@microlinux.fr> Le 29/03/2016 16:09, Christoph Willing a ?crit : > I have 'content-disposition = on' in my /etc/wgetrc but in cases like > you describe, I find that overriding that setting at the command line > often helps i.e. > wget --no-content-disposition http://whatever... Unfortunately that doesn't seem to solve the issue. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From hba.nihilismus at gmail.com Wed Mar 30 07:26:12 2016 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Wed, 30 Mar 2016 01:26:12 -0600 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FA8242.8040001@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> Message-ID: On Tue, Mar 29, 2016 at 7:25 AM, Nicolas Kovacs wrote: > Hi, > > Whenever I want to download some source tarball from SourceForge using > wget, I get permantently redirected until eventually some mirror times > out. So I have to reinvoke the command, sometimes ten times in a row, > until eventually it works out. This is really getting tiresome. > > Do you have some workaround for this? > Maybe some servers are blocking wget's User-Agent string. Go to http://whatsmyuseragent.com, grab the User-Agent string of your web browser and use it: wget -U "User-Agent string" Check wget's man-page about "-U". - Cheers -- Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Wed Mar 30 07:52:28 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 30 Mar 2016 17:52:28 +1000 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FA8242.8040001@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> Message-ID: <56FB85BC.9040703@iinet.net.au> On 29/03/16 23:25, Nicolas Kovacs wrote: > Hi, > > Whenever I want to download some source tarball from SourceForge using > wget, I get permantently redirected until eventually some mirror times > out. So I have to reinvoke the command, sometimes ten times in a row, > until eventually it works out. This is really getting tiresome. > > Do you have some workaround for this? Do you have an example url that shows this behaviour? From info at microlinux.fr Wed Mar 30 08:15:47 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Mar 2016 10:15:47 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FB85BC.9040703@iinet.net.au> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> Message-ID: <56FB8B33.70402@microlinux.fr> Le 30/03/2016 09:52, Christoph Willing a ?crit : > Do you have an example url that shows this behaviour? Everything that contains "sourceforge" :o) -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Wed Mar 30 08:22:01 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Mar 2016 10:22:01 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FB85BC.9040703@iinet.net.au> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> Message-ID: <56FB8CA9.2090207@microlinux.fr> Le 30/03/2016 09:52, Christoph Willing a ?crit : > Do you have an example url that shows this behaviour? But seriously, here's an example. DOWNLOAD="http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2" wget -c $DOWNLOAD This results in an endless redirection loop, until eventually one of the mirrors fails. This is true for ALL the stuff downloaded from SourceForge. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From bch at shroggslodge.freeserve.co.uk Wed Mar 30 08:49:04 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Wed, 30 Mar 2016 09:49:04 +0100 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FB8CA9.2090207@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> <56FB8CA9.2090207@microlinux.fr> Message-ID: Hi all, Just reporting my experience. "This results in an endless redirection loop, until eventually one of the mirrors fails." It did not for me. Tried "wget http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2" and it worked fine. Slackware: 14.1 32-bit, wget: 1.14 (built on linux-gnu). On 30 March 2016 at 09:22, Nicolas Kovacs wrote: > Le 30/03/2016 09:52, Christoph Willing a ?crit : > > Do you have an example url that shows this behaviour? > > But seriously, here's an example. > > DOWNLOAD=" > http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 > " > > wget -c $DOWNLOAD > > This results in an endless redirection loop, until eventually one of the > mirrors fails. > > This is true for ALL the stuff downloaded from SourceForge. > > Niki > > -- > Microlinux - Solutions informatiques durables > 7, place de l'?glise - 30730 Montpezat > Web : http://www.microlinux.fr > Mail : info at microlinux.fr > T?l. : 04 66 63 10 32 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Mar 30 08:50:14 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 30 Mar 2016 10:50:14 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FB8CA9.2090207@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> <56FB8CA9.2090207@microlinux.fr> Message-ID: $ wget http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 --2016-03-30 10:42:14-- http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59 Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://nbtelecom.dl.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 [following] --2016-03-30 10:42:14-- http://nbtelecom.dl.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 Resolving nbtelecom.dl.sourceforge.net (nbtelecom.dl.sourceforge.net)... 189.45.5.78 Connecting to nbtelecom.dl.sourceforge.net (nbtelecom.dl.sourceforge.net)|189.45.5.78|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 36468 (36K) [application/octet-stream] Saving to: ?gtkcdlabel-1.15.tar.bz2? gtkcdlabel-1.15.tar.bz2 100%[=======================================================================================>] 35,61K 147KB/s in 0,2s 2016-03-30 10:42:15 (147 KB/s) - ?gtkcdlabel-1.15.tar.bz2? saved [36468/36468] maybe it's an issue related to how sourceforge roundrobin behaves your region, as here seems to work fine. my suggestion is to open a support ticket at sf (you need an account there) https://sourceforge.net/p/forge/site-support/ Matteo From info at microlinux.fr Wed Mar 30 08:52:51 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Mar 2016 10:52:51 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> <56FB8CA9.2090207@microlinux.fr> Message-ID: <56FB93E3.9080402@microlinux.fr> Le 30/03/2016 10:50, Matteo Bernardini a ?crit : > maybe it's an issue related to how sourceforge roundrobin behaves your > region, as here seems to work fine. Apparently other people have the same problem. This being said, someone suggested in a user forum to replace wget by 'curl -O -J -L', and this seems to work well. It doesn't support resuming broken downloads as 'wget -c', but at least the download doesn't stall. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Wed Mar 30 10:01:31 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Mar 2016 12:01:31 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FB93E3.9080402@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> <56FB8CA9.2090207@microlinux.fr> <56FB93E3.9080402@microlinux.fr> Message-ID: <56FBA3FB.8090700@microlinux.fr> Le 30/03/2016 10:52, Nicolas Kovacs a ?crit : > This being said, someone suggested in a user forum to replace wget by > 'curl -O -J -L', and this seems to work well. It doesn't support > resuming broken downloads as 'wget -c', but at least the download > doesn't stall. ... except now some (but not all) filenames seem to change, and resuming downloads doesn't work. Pffff. -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From baildon.research at googlemail.com Wed Mar 30 10:37:46 2016 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 30 Mar 2016 11:37:46 +0100 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FBA3FB.8090700@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> <56FB8CA9.2090207@microlinux.fr> <56FB93E3.9080402@microlinux.fr> <56FBA3FB.8090700@microlinux.fr> Message-ID: You can try the awesome sbosrcarch when a download fails. http://slackware.uk/sbosrcarch/ *THANKS* B Watson & Tadgy! I think sbotools now automatically falls back to sbosrcarch, and Willy is working on the same idea for sbopkg but it's not released yet: https://github.com/sbopkg/sbopkg/issues/12 see his 'sbosrcarch' branch -- and note he has added a 'help wanted' tag ;-) Maybe people don't remember that this same Sourceforge problem happened all the time years ago. Maybe it's a sign that the old Sourceforge really is back -- not evil, just incompetent. -D. From chris.willing at iinet.net.au Wed Mar 30 11:56:07 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 30 Mar 2016 21:56:07 +1000 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FB8CA9.2090207@microlinux.fr> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> <56FB8CA9.2090207@microlinux.fr> Message-ID: <56FBBED7.9020705@iinet.net.au> On 30/03/16 18:22, Nicolas Kovacs wrote: > Le 30/03/2016 09:52, Christoph Willing a ?crit : >> Do you have an example url that shows this behaviour? > > But seriously, here's an example. > > DOWNLOAD="http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2" > OK, now back to my earlier mention of the --no-content-disposition option - I had it the wrong way around, so for that url I have: wget --content-disposition http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 ... HTTP request sent, awaiting response... 302 Found ... HTTP request sent, awaiting response... 200 OK ... HTTP request sent, awaiting response... 200 OK Length: 36468 (36K) [application/octet-stream] Saving to: ?gtkcdlabel-1.15.tar.bz2? gtkcdlabel-1.15.tar.bz2 100%[==============================================>] 35.61K 50.2KB/s in 0.7s 2016-03-30 21:38:11 (50.2 KB/s) - ?gtkcdlabel-1.15.tar.bz2? saved [36468/36468] However with no content disposition (the default for wget), I also see a bunch of connections to different servers and finally failure: wget --no-content-disposition http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 ... ... ... 20 redirections exceeded. So the suggestion should have been to turn content-disposition on (not off) either explicitly at the command line or in /etc/wgetrc (or ~/.wgetrc) by adding the line 'content-disposition = on' BTW you can also add 'continue = on' in that file to dispense with the need for '-c' at the command line. chris From slackph at posteo.de Wed Mar 30 13:22:45 2016 From: slackph at posteo.de (Philip Lacroix) Date: Wed, 30 Mar 2016 15:22:45 +0200 Subject: [Slackbuilds-users] package for grab: sage In-Reply-To: <56F9425B.4040702@slackbuilds.org> References: <56F660A6.1080303@slackbuilds.org> <56F94181.2060602@grindcore.ch> <56F9425B.4040702@slackbuilds.org> Message-ID: <3995c5075873c4afab6eb2386c37cd30@posteo.de> Am 28.03.2016 16:40 schrieb Willy Sudiarto Raharjo: >> I tried to upgrade the SlackBuild to sage 7.1 but failed. I just don't >> understand the build process of sage well enough to patch this >> together. >> But let me know if you need testers! I'm a regular Sage user. > > yes, it failed on pynac, which is strange since it was the same problem > as in 7.0, but it built perfectly on 7.0, but eventually not in 7.1 Hello Willy and all I had some problems building Sage 7.1 as well (because of pynac) but eventually I could build and package it successfully, after tracking down and removing the following patch: build/pkgs/python2/patches/sys_path_security.patch The patch is explicitly related to this bug report to upstream: http://trac.sagemath.org/ticket/13579 I'm not sure about the actual security implications (if any) of not using the patch in our SBo context, but this is the error I had when I applied it and the build of pynac failed: "not adding directory ' ' to sys.path since it's not owned by a trusted user." Apparently, the patched python2 which is included in Sage didn't want to add the current directory to sys.path, in order to prevent the execution of python scripts from /tmp (even if I actually pointed TMP to my home directory). Anyway, Sage 7.1 seems to be working fine here. This is what I have done so far to the script itself, basing on the current version (some of the other files were also modified - meanwhile I'll do some more tests): #-----------------------------------------------# #!/bin/sh # Slackware build script for sage # Originally written by Jack Maddox # Currently maintained by Willy Sudiarto Raharjo # # (03.2016) Reviewed and updated by Philip Lacroix # # All rights reserved. # # Redistribution and use of this script, with or without modification, is # permitted provided that the following conditions are met: # # 1. Redistributions of this script must retain the above copyright # notice, this list of conditions and the following disclaimer. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR "AS IS" AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=sage VERSION=${VERSION:-7.1} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) export ARCH=i486 ;; arm*) export ARCH=arm ;; *) export ARCH=$( uname -m ) ;; esac fi CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} SAGEROOT=${SAGEROOT:-/opt/sage} set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$VERSION.tar.gz cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; PRGBIN=$PKG/$SAGEROOT/bin PRGSHR=$PKG/usr/share PRGPFL=$PKG/etc/profile.d PRGDOC=$PKG/usr/doc/$PRGNAM-$VERSION mkdir -p $PKG/$SAGEROOT $PRGSHR/{applications,pixmaps} $PRGDOC $PRGPFL # Apply FreeBSD patch to build as root (thanks to Heinz for pointing to it). patch -p0 < $CWD/sage-pynac.patch # Apply another patch to build as root. patch -p1 < $CWD/sage-build-root.patch # Remove problematic patch to the included python2. rm -f build/pkgs/python2/patches/sys_path_security.patch make # Test all examples in the documentation (over 93,000 line of input). [ "${TEST:-no}" = "yes" ] && make test # Build the pdf version of the documentation (this requires LaTeX). if [ "${PDFDOC:-no}" = "yes" ]; then ./sage -docbuild all pdf cp -av devel/sage/doc/output/pdf $PRGDOC/ fi # Install optional packages as defined by the OPTIONALSPKG flag. OPTIONALSPKG=${OPTIONALSPKG:-no} if [ "$OPTIONALSPKG" != "no" ]; then for i in ${OPTIONALSPKG}; do ./sage -i $(./sage -optional | grep ${i}) done fi cp -av build local sage $PKG/$SAGEROOT/ find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" \ | grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true # Add profile scripts. sed "s%SAGEROOT%${SAGEROOT}%" $CWD/profile.d/sage.sh > $PRGPFL/$PRGNAM.sh sed "s%SAGEROOT%${SAGEROOT}%" $CWD/profile.d/sage.csh > $PRGPFL/$PRGNAM.csh chmod 0755 $PRGPFL/* # Install scripts to SAGEROOT/bin that allow the internal sage versions of # gap, gp, singular, maxima, M2, kash, mwrank, ipython, hg, and R to be run # independently. Also add SAGEROOT/bin to PATH. if [ "${INSTALLSCRIPTS:-no}" = "yes" ]; then mkdir $PRGBIN echo "install_scripts('$PRGBIN')" | ./sage sed -i 's%$PATH:${SAGE_ROOT}%$PATH:${SAGE_ROOT}:${SAGE_ROOT}/bin%' \ $PRGPFL/$PRGNAM.sh sed -i 's%$path ${SAGE_ROOT}%$path ${SAGE_ROOT} ${SAGE_ROOT}/bin%' \ $PRGPFL/$PRGNAM.csh fi # Install sagetex to a location accessible to the system TeX installation. cp -a local/share/texmf $PRGSHR/ # Install desktop file, icon and logo. Symlink icon. desktop=sage-notebook.desktop sed "s%SAGEROOT%${SAGEROOT}%" $CWD/$desktop > $PRGSHR/applications/$desktop cp -a src/doc/common/themes/sage/static/sage{icon,logo}.png $PRGSHR/pixmaps/ icondir=$PRGSHR/icons/hicolor/16x16/apps/ ; mkdir -p $icondir ln -sf /opt/$PRGNAM/usr/share/pixmaps/sageicon.png $icondir/ # Install documentation. cp -a COPYING.txt README.md VERSION.txt $PRGDOC/ cat $CWD/$PRGNAM.SlackBuild > $PRGDOC/$PRGNAM.SlackBuild mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc sed "s%SAGEROOT%${SAGEROOT}%" $CWD/doinst.sh > $PKG/install/doinst.sh cd $PKG /sbin/makepkg -p -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} #-----------------------------------------------# Cheers Philip From info at microlinux.fr Wed Mar 30 14:17:27 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 30 Mar 2016 16:17:27 +0200 Subject: [Slackbuilds-users] Problem with SourceForge and wget In-Reply-To: <56FBBED7.9020705@iinet.net.au> References: <56FA8242.8040001@microlinux.fr> <56FB85BC.9040703@iinet.net.au> <56FB8CA9.2090207@microlinux.fr> <56FBBED7.9020705@iinet.net.au> Message-ID: <56FBDFF7.5030801@microlinux.fr> Le 30/03/2016 13:56, Christoph Willing a ?crit : > OK, now back to my earlier mention of the --no-content-disposition > option - I had it the wrong way around, so for that url I have: > > wget --content-disposition > http://downloads.sourceforge.net/project/gtkcdlabel/gtkcdlabel/1.15/gtkcdlabel-1.15.tar.bz2 I played around some more with it and found the following solution to be working more reliably. I don't know why, though: DOWNLOAD="http://downloads.sourceforge.net/$PRGNAM/${PRGNAM}_${VERSION}_src_all.tar.bz2" rm -f ${PRGNAM}_${VERSION}_src_all.tar.bz2 curl -O -J -L $DOWNLOAD Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Thu Mar 31 07:34:00 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 31 Mar 2016 09:34:00 +0200 Subject: [Slackbuilds-users] plank sources not available Message-ID: <56FCD2E8.80408@microlinux.fr> Hi, The sources for the plank package are not available on Launchpad anymore. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Thu Mar 31 07:49:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 31 Mar 2016 14:49:27 +0700 Subject: [Slackbuilds-users] plank sources not available In-Reply-To: <56FCD2E8.80408@microlinux.fr> References: <56FCD2E8.80408@microlinux.fr> Message-ID: <2CD168F4-D0FF-4037-AAF7-98F88647B7F5@slackbuilds.org> > The sources for the plank package are not available on Launchpad anymore. https://launchpadlibrarian.net/220768016/plank-0.10.1.tar.xz -- Willy Sudiarto Raharjo -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Thu Mar 31 09:55:21 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 31 Mar 2016 11:55:21 +0200 Subject: [Slackbuilds-users] plank sources not available In-Reply-To: <2CD168F4-D0FF-4037-AAF7-98F88647B7F5@slackbuilds.org> References: <56FCD2E8.80408@microlinux.fr> <2CD168F4-D0FF-4037-AAF7-98F88647B7F5@slackbuilds.org> Message-ID: <56FCF409.3040002@microlinux.fr> Le 31/03/2016 09:49, Willy Sudiarto Raharjo a ?crit : >> The sources for the plank package are not available on Launchpad anymore. > > https://launchpadlibrarian.net/220768016/plank-0.10.1.tar.xz Thanks, Willy ! -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From slackbuilds at schoepfer.info Thu Mar 31 13:04:50 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 31 Mar 2016 15:04:50 +0200 Subject: [Slackbuilds-users] letsencrypt Message-ID: <56FD2072.30405@schoepfer.info> Hi, i suggest to add the existence of https://github.com/srvrco/getssl/ to the README of the letsencrypt-package, as getssl does the same job with pure bash-code and no external dependencies. Franzen From johannes at schoepfer.info Tue Mar 15 19:29:09 2016 From: johannes at schoepfer.info (johannes at schoepfer.info) Date: Tue, 15 Mar 2016 19:29:09 -0000 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: <56E85645.4080604@slackbuilds.org> References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> Message-ID: >> The difficult part is to find which other packages will fail if >> qtwebengine is not built, and how to fix them. >> >> If we can't do that quickly and easily, then it might be easier to fix >> qtwebengine. > > and FYI, here are the packages that directly requires qt5 A recent mscore/musescore 2.0.2 also requires qt5, mscore 1.3 from SBo is outdated. https://musescore.org/ Franzen