From willysr at slackbuilds.org Mon May 1 03:45:46 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 1 May 2017 10:45:46 +0700 Subject: [Slackbuilds-users] New server for SlackBuilds.org In-Reply-To: <20170430151942.0ce1bc6b@home.rlworkman.net> References: <20170426211933.20ffcab9@home.rlworkman.net> <20170430151942.0ce1bc6b@home.rlworkman.net> Message-ID: > Sincere thanks to everyone who donated - we are honored that so > many think this little project is useful and worthy enough to > support. Without minimizing the impact of any other contributions, > we'd like single out one contributor in particular, if only due > to the fact that we were (pleasantly) surprised: > Distrowatch.com donated $400 to the effort! Thanks, Unsigned > Integer Limited :-) Adding an official public announcement: http://distrowatch.com/weekly.php?issue=20170501#donation We are pleased to announce the recipient of the April 2017 DistroWatch.com donation is SlackBuilds. The project receives US$400.00 in cash. The SlackBuilds project provides build scripts for the Slackware distribution which automate building software from upstream source code. Using SlackBuilds allows a user to quickly and easily install new applications without relying on pre-built binaries in third-party software repositories. SlackBuilds is currently trying to raise funding for new server equipment. -- 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 sam_web at yahoo.de Mon May 1 18:11:11 2017 From: sam_web at yahoo.de (Marek Srejma) Date: Mon, 1 May 2017 20:11:11 +0200 Subject: [Slackbuilds-users] Orphaned Scripts In-Reply-To: <5860303e-ce5d-8ac2-d06a-e2b42aee42c2@slackbuilds.org> References: <95873518-2a09-80ff-68d5-6e14794a5d8a@slackbuilds.org> <48398801-b7d1-63d7-df86-9df71d11bc95@yahoo.de> <5860303e-ce5d-8ac2-d06a-e2b42aee42c2@slackbuilds.org> Message-ID: <6965d9ba-f4eb-9716-ba4f-0a73a32ea915@yahoo.de> Hi Willy, also I'll take over the cclive SlackBuild. It's not on your list, but the maintainer wrote me that I can have it, because he doesn't use Slackware anymore, since 2015. Thanks. Willy Sudiarto Raharjo schrieb: >> if noboby else wants to take incron, I would do. >> >> Would it be okay if I add an /etc/rc.d/rc.incrond script in the next >> update? > Sure, that's up to maintainer's decision :) > it's yours now > > thanks > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From d.zlatanidis at gmail.com Mon May 1 18:35:09 2017 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Mon, 1 May 2017 20:35:09 +0200 Subject: [Slackbuilds-users] libspectrum Message-ID: <91545b42-e1f0-f636-6eb2-f5d3aa79132a@gmail.com> I have issue to build libspectrum 1.3.3 version, any help? rings -MT zip.lo -MD -MP -MF .deps/zip.Tpo -c zip.c -o zip.o >/dev/null 2>&1 depbase=`echo zlib.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2 -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF $depbase.Tpo -c -o zlib.lo zlib.c &&\ mv -f $depbase.Tpo $depbase.Plo libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2 -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c zlib.c -fPIC -DPIC -o .libs/zlib.o libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2 -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c zlib.c -o zlib.o >/dev/null 2>&1 /bin/sh ./libtool --tag=CC --mode=link gcc -DLIBSPECTRUM_EXPORTS -O2 -fPIC -Wall -Wwrite-strings -version-info 12:6:4 -no-undefined -L/usr/lib -o libspectrum.la -rpath /usr/lib64 bzip2.lo creator.lo crypto.lo csw.lo dck.lo ide.lo libspectrum.lo memory.lo microdrive.lo plusd.lo pzx_read.lo rzx.lo sna.lo snp.lo snapshot.lo snap_accessors.lo sp.lo symbol_table.lo szx.lo tap.lo tape.lo tape_accessors.lo tape_block.lo tape_set.lo timings.lo tzx_read.lo tzx_write.lo utilities.lo warajevo_read.lo wav.lo z80.lo z80em.lo zxs.lo zip.lo zlib.lo -laudiofile -lglib-2.0 -lm -lbz2 -lz -lgcrypt libtool: link: warning: `/usr/lib/libstdc++.la' seems to be moved libtool: link: gcc -shared -fPIC -DPIC .libs/bzip2.o .libs/creator.o .libs/crypto.o .libs/csw.o .libs/dck.o .libs/ide.o .libs/libspectrum.o .libs/memory.o .libs/microdrive.o .libs/plusd.o .libs/pzx_read.o .libs/rzx.o .libs/sna.o .libs/snp.o .libs/snapshot.o .libs/snap_accessors.o .libs/sp.o .libs/symbol_table.o .libs/szx.o .libs/tap.o .libs/tape.o .libs/tape_accessors.o .libs/tape_block.o .libs/tape_set.o .libs/timings.o .libs/tzx_read.o .libs/tzx_write.o .libs/utilities.o .libs/warajevo_read.o .libs/wav.o .libs/z80.o .libs/z80em.o .libs/zxs.o .libs/zip.o .libs/zlib.o -Wl,-rpath -Wl,/usr/lib64/../lib -Wl,-rpath -Wl,/usr/lib64/../lib -L/usr/lib /usr/lib/libaudiofile.so /usr/lib/libFLAC.so /usr/lib/libogg.so /usr/lib64/../lib/libstdc++.so /usr/lib/libglib-2.0.so -lpthread -lm -lbz2 -lz /usr/lib/libgcrypt.so /usr/lib/libgpg-error.so -O2 -Wl,-soname -Wl,libspectrum.so.8 -o .libs/libspectrum.so.8.4.6 /usr/lib/libaudiofile.so: error adding symbols: File in wrong format collect2: error: ld returned 1 exit status Makefile:554: recipe for target 'libspectrum.la' failed make[1]: *** [libspectrum.la] Error 1 make[1]: Leaving directory '/tmp/SBo/libspectrum-1.3.3' Makefile:447: recipe for target 'all' failed make: *** [all] Error 2 -- Dimitris Zlatanidis From didier at slint.fr Mon May 1 18:51:22 2017 From: didier at slint.fr (Didier Spaier) Date: Mon, 1 May 2017 20:51:22 +0200 Subject: [Slackbuilds-users] libspectrum In-Reply-To: <91545b42-e1f0-f636-6eb2-f5d3aa79132a@gmail.com> References: <91545b42-e1f0-f636-6eb2-f5d3aa79132a@gmail.com> Message-ID: <4b7b9bc0-5e8b-89c3-30b0-762dd7e7324d@slint.fr> Le 01/05/2017 ? 20:35, Dimitris Zlatanidis a ?crit : > I have issue to build libspectrum 1.3.3 version, any help? > > > rings -MT zip.lo -MD -MP -MF .deps/zip.Tpo -c zip.c -o zip.o >/dev/null 2>&1 > depbase=`echo zlib.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include > -DLIBSPECTRUM_EXPORTS -O2 -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD > -MP -MF $depbase.Tpo -c -o zlib.lo zlib.c &&\ > mv -f $depbase.Tpo $depbase.Plo > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2 > -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c > zlib.c -fPIC -DPIC -o .libs/zlib.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2 > -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c > zlib.c -o zlib.o >/dev/null 2>&1 > /bin/sh ./libtool --tag=CC --mode=link gcc -DLIBSPECTRUM_EXPORTS -O2 > -fPIC -Wall -Wwrite-strings -version-info 12:6:4 -no-undefined > -L/usr/lib -o libspectrum.la -rpath /usr/lib64 bzip2.lo creator.lo > crypto.lo csw.lo dck.lo ide.lo libspectrum.lo memory.lo microdrive.lo > plusd.lo pzx_read.lo rzx.lo sna.lo snp.lo snapshot.lo snap_accessors.lo > sp.lo symbol_table.lo szx.lo tap.lo tape.lo tape_accessors.lo > tape_block.lo tape_set.lo timings.lo tzx_read.lo tzx_write.lo > utilities.lo warajevo_read.lo wav.lo z80.lo z80em.lo zxs.lo zip.lo > zlib.lo -laudiofile -lglib-2.0 -lm -lbz2 -lz -lgcrypt > libtool: link: warning: `/usr/lib/libstdc++.la' seems to be moved > libtool: link: gcc -shared -fPIC -DPIC .libs/bzip2.o .libs/creator.o > .libs/crypto.o .libs/csw.o .libs/dck.o .libs/ide.o .libs/libspectrum.o > .libs/memory.o .libs/microdrive.o .libs/plusd.o .libs/pzx_read.o > .libs/rzx.o .libs/sna.o .libs/snp.o .libs/snapshot.o > .libs/snap_accessors.o .libs/sp.o .libs/symbol_table.o .libs/szx.o > .libs/tap.o .libs/tape.o .libs/tape_accessors.o .libs/tape_block.o > .libs/tape_set.o .libs/timings.o .libs/tzx_read.o .libs/tzx_write.o > .libs/utilities.o .libs/warajevo_read.o .libs/wav.o .libs/z80.o > .libs/z80em.o .libs/zxs.o .libs/zip.o .libs/zlib.o -Wl,-rpath > -Wl,/usr/lib64/../lib -Wl,-rpath -Wl,/usr/lib64/../lib -L/usr/lib > /usr/lib/libaudiofile.so /usr/lib/libFLAC.so /usr/lib/libogg.so > /usr/lib64/../lib/libstdc++.so /usr/lib/libglib-2.0.so -lpthread -lm > -lbz2 -lz /usr/lib/libgcrypt.so /usr/lib/libgpg-error.so -O2 > -Wl,-soname -Wl,libspectrum.so.8 -o .libs/libspectrum.so.8.4.6 > /usr/lib/libaudiofile.so: error adding symbols: File in wrong format > collect2: error: ld returned 1 exit status > Makefile:554: recipe for target 'libspectrum.la' failed > make[1]: *** [libspectrum.la] Error 1 > make[1]: Leaving directory '/tmp/SBo/libspectrum-1.3.3' > Makefile:447: recipe for target 'all' failed > make: *** [all] Error 2 Blind guess for /usr/lib/libaudiofile.so: 32-bit vs 64-bit expected? From artourter at gmail.com Mon May 1 20:52:03 2017 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 1 May 2017 21:52:03 +0100 Subject: [Slackbuilds-users] libspectrum In-Reply-To: <91545b42-e1f0-f636-6eb2-f5d3aa79132a@gmail.com> References: <91545b42-e1f0-f636-6eb2-f5d3aa79132a@gmail.com> Message-ID: You seem to be building this on a multilib system. You might want to have a look at the FAQ and see if it fixes your problem: https://slackbuilds.org/faq/#multilib Greg On 1 May 2017 at 19:35, Dimitris Zlatanidis wrote: > I have issue to build libspectrum 1.3.3 version, any help? > > > rings -MT zip.lo -MD -MP -MF .deps/zip.Tpo -c zip.c -o zip.o >/dev/null > 2>&1 > depbase=`echo zlib.lo | sed 's|[^/]*$|.deps/&|;s|\.lo$||'`;\ > /bin/sh ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include > -DLIBSPECTRUM_EXPORTS -O2 -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD > -MP -MF $depbase.Tpo -c -o zlib.lo zlib.c &&\ > mv -f $depbase.Tpo $depbase.Plo > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2 > -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c > zlib.c -fPIC -DPIC -o .libs/zlib.o > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include -I/usr/include -DLIBSPECTRUM_EXPORTS -O2 > -fPIC -Wall -Wwrite-strings -MT zlib.lo -MD -MP -MF .deps/zlib.Tpo -c > zlib.c -o zlib.o >/dev/null 2>&1 > /bin/sh ./libtool --tag=CC --mode=link gcc -DLIBSPECTRUM_EXPORTS -O2 > -fPIC -Wall -Wwrite-strings -version-info 12:6:4 -no-undefined > -L/usr/lib -o libspectrum.la -rpath /usr/lib64 bzip2.lo creator.lo > crypto.lo csw.lo dck.lo ide.lo libspectrum.lo memory.lo microdrive.lo > plusd.lo pzx_read.lo rzx.lo sna.lo snp.lo snapshot.lo snap_accessors.lo > sp.lo symbol_table.lo szx.lo tap.lo tape.lo tape_accessors.lo > tape_block.lo tape_set.lo timings.lo tzx_read.lo tzx_write.lo > utilities.lo warajevo_read.lo wav.lo z80.lo z80em.lo zxs.lo zip.lo > zlib.lo -laudiofile -lglib-2.0 -lm -lbz2 -lz -lgcrypt > libtool: link: warning: `/usr/lib/libstdc++.la' seems to be moved > libtool: link: gcc -shared -fPIC -DPIC .libs/bzip2.o .libs/creator.o > .libs/crypto.o .libs/csw.o .libs/dck.o .libs/ide.o .libs/libspectrum.o > .libs/memory.o .libs/microdrive.o .libs/plusd.o .libs/pzx_read.o > .libs/rzx.o .libs/sna.o .libs/snp.o .libs/snapshot.o > .libs/snap_accessors.o .libs/sp.o .libs/symbol_table.o .libs/szx.o > .libs/tap.o .libs/tape.o .libs/tape_accessors.o .libs/tape_block.o > .libs/tape_set.o .libs/timings.o .libs/tzx_read.o .libs/tzx_write.o > .libs/utilities.o .libs/warajevo_read.o .libs/wav.o .libs/z80.o > .libs/z80em.o .libs/zxs.o .libs/zip.o .libs/zlib.o -Wl,-rpath > -Wl,/usr/lib64/../lib -Wl,-rpath -Wl,/usr/lib64/../lib -L/usr/lib > /usr/lib/libaudiofile.so /usr/lib/libFLAC.so /usr/lib/libogg.so > /usr/lib64/../lib/libstdc++.so /usr/lib/libglib-2.0.so -lpthread -lm > -lbz2 -lz /usr/lib/libgcrypt.so /usr/lib/libgpg-error.so -O2 > -Wl,-soname -Wl,libspectrum.so.8 -o .libs/libspectrum.so.8.4.6 > /usr/lib/libaudiofile.so: error adding symbols: File in wrong format > collect2: error: ld returned 1 exit status > Makefile:554: recipe for target 'libspectrum.la' failed > make[1]: *** [libspectrum.la] Error 1 > make[1]: Leaving directory '/tmp/SBo/libspectrum-1.3.3' > Makefile:447: recipe for target 'all' failed > make: *** [all] Error 2 > > -- > Dimitris Zlatanidis > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue May 2 01:27:48 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 2 May 2017 08:27:48 +0700 Subject: [Slackbuilds-users] Orphaned Scripts In-Reply-To: <6965d9ba-f4eb-9716-ba4f-0a73a32ea915@yahoo.de> References: <95873518-2a09-80ff-68d5-6e14794a5d8a@slackbuilds.org> <48398801-b7d1-63d7-df86-9df71d11bc95@yahoo.de> <5860303e-ce5d-8ac2-d06a-e2b42aee42c2@slackbuilds.org> <6965d9ba-f4eb-9716-ba4f-0a73a32ea915@yahoo.de> Message-ID: <33787709-a028-e1cd-5f32-5b1aeb820039@slackbuilds.org> > also I'll take over the cclive SlackBuild. It's not on your list, but > the maintainer wrote me that I can have it, because he doesn't use > Slackware anymore, since 2015. Hi Marek thanks for the notification i will put the rest of his scripts on pasture just to confirm, the previous maintainer was slackmuz? -- 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 sam_web at yahoo.de Tue May 2 07:20:30 2017 From: sam_web at yahoo.de (Marek Srejma) Date: Tue, 2 May 2017 09:20:30 +0200 Subject: [Slackbuilds-users] Orphaned Scripts In-Reply-To: <33787709-a028-e1cd-5f32-5b1aeb820039@slackbuilds.org> References: <95873518-2a09-80ff-68d5-6e14794a5d8a@slackbuilds.org> <48398801-b7d1-63d7-df86-9df71d11bc95@yahoo.de> <5860303e-ce5d-8ac2-d06a-e2b42aee42c2@slackbuilds.org> <6965d9ba-f4eb-9716-ba4f-0a73a32ea915@yahoo.de> <33787709-a028-e1cd-5f32-5b1aeb820039@slackbuilds.org> Message-ID: <18ea3bda-a5f7-3a67-2bd3-32959f782024@yahoo.de> >> also I'll take over the cclive SlackBuild. It's not on your list, but >> the maintainer wrote me that I can have it, because he doesn't use >> Slackware anymore, since 2015. > Hi Marek > > thanks for the notification > i will put the rest of his scripts on pasture > > just to confirm, the previous maintainer was slackmuz? > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Hi Willy, yes, Milojevi? Petar a.k.a. slackmuz, email: petar.linog at gmail.com I emailed him and this is what he answered: > Hello, Marek > Please continue to maintain the SlackBuild. > I don't use Slackware anymore, since 2015. Thank you for your help and > the patch. From willysr at slackbuilds.org Tue May 2 09:50:55 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 2 May 2017 16:50:55 +0700 Subject: [Slackbuilds-users] Scripts to grab Message-ID: Hi, There are 3 more scripts which is orphaned by it's maintainer libraries/libquvi libraries/libquvi-scripts network/quvi those three are related to each other, so whoever want to step up should grab all of them. I have them on pasture at this moment. 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 sam_web at yahoo.de Tue May 2 10:32:40 2017 From: sam_web at yahoo.de (Marek Srejma) Date: Tue, 2 May 2017 12:32:40 +0200 Subject: [Slackbuilds-users] Scripts to grab In-Reply-To: References: Message-ID: <47d07204-9123-e789-7ec7-fc9bbd507536@yahoo.de> Willy Sudiarto Raharjo schrieb: > Hi, > > There are 3 more scripts which is orphaned by it's maintainer > libraries/libquvi > libraries/libquvi-scripts > network/quvi > > those three are related to each other, so whoever want to step up should > grab all of them. I have them on pasture at this moment. > > thanks > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Hi Willy, since cclive depends on those packages, I'd like to maintain them (if noone else wants them). Marek From willysr at slackbuilds.org Tue May 2 11:24:15 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 2 May 2017 18:24:15 +0700 Subject: [Slackbuilds-users] Scripts to grab In-Reply-To: <47d07204-9123-e789-7ec7-fc9bbd507536@yahoo.de> References: <47d07204-9123-e789-7ec7-fc9bbd507536@yahoo.de> Message-ID: <515733bc-51ad-9084-5a81-ee459d87267e@slackbuilds.org> > since cclive depends on those packages, I'd like to maintain them (if > noone else wants them). Sure, no problem i will remove them as soon as you send a submission -- 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 gen-bch at useyouresp.org.uk Tue May 2 16:08:17 2017 From: gen-bch at useyouresp.org.uk (General) Date: Tue, 2 May 2017 17:08:17 +0100 Subject: [Slackbuilds-users] Flowblade Message-ID: FAO Maintainer (cc'd slackbuilds-users) Klaatu Flowblade is several releases on now (1.12 ?). With respect to the effort involved, I was wondering if 'we' might be seeing an update to the latest version soon please? I've had a go a running the build script against 1.10 and it seemed to go ok, but I'm never too sure ;-) Which leads me to another [general] question: when getting a source of Github (of which I am not too familiar) , what happens in terms of process that leads to the md5sum's on the slackbuilds.org..... I could not see any published [by the developers] any checksums etc ? Keep up the good work everyone. It does not get said enough probably, but the time and effort that contributors and maintainers etc put in to this SlackBuilds project (and quality open source in general) is most appreciated. Thank you. Habs -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue May 2 16:28:46 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 2 May 2017 12:28:46 -0400 Subject: [Slackbuilds-users] md5sums [was: Flowblade] Message-ID: On 5/2/17, General wrote: > > Which leads me to another [general] question: when getting a source of > Github (of which I am not too familiar) , what happens in terms of process > that leads to the md5sum's on the slackbuilds.org..... I could not see any > published [by the developers] any checksums etc ? Whoever writes the SlackBuild downloads the file and calculates its md5sum. In other words, they come from the SBo maintainer, not from the upstream devs. As a user, the md5sum matching means you're using the same source as the SBo maintainer wrote his script for... but there's no 'chain of trust' beyond that. (About now, someone will chime in with 'But md5 is weak and has been exploited!', I'll leave that discussion for later...) From gen-bch at useyouresp.org.uk Tue May 2 16:47:53 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Tue, 2 May 2017 17:47:53 +0100 Subject: [Slackbuilds-users] md5sums [was: Flowblade] In-Reply-To: References: Message-ID: <20170502174753.0e02db87@dv6920ea.localdomain> On Tue, 2 May 2017 12:28:46 -0400 B Watson wrote: > On 5/2/17, General wrote: > > > > Which leads me to another [general] question: when getting a > > source of Github (of which I am not too familiar) , what happens in > > terms of process that leads to the md5sum's on the > > slackbuilds.org..... I could not see any published [by the > > developers] any checksums etc ? > > Whoever writes the SlackBuild downloads the file and calculates its > md5sum. In other words, they come from the SBo maintainer, not from > the upstream devs. > > As a user, the md5sum matching means you're using the same source as > the SBo maintainer wrote his script for... but there's no 'chain of > trust' beyond that. > > (About now, someone will chime in with 'But md5 is weak and has been > exploited!', I'll leave that discussion for later...) > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Thank you for the reply. Ahh I see. I had it in my mind that upstream/devs would post a [sourse] release as such with some checksum, so that when it arrived elsewhere it could be validated (as best one can) to not have been meddled with. Cheers. Habs From klaatu at mixedsignals.ml Tue May 2 17:39:04 2017 From: klaatu at mixedsignals.ml (klaatu at mixedsignals.ml) Date: Wed, 03 May 2017 05:39:04 +1200 Subject: [Slackbuilds-users] Flowblade In-Reply-To: References: Message-ID: Hi Habs, I can update FlowBlade, but if your build is going well, it's probably just as good as whatever I'll post. You can start editing with what you've got. I don't personally like to rush into updates on stable software. I'll do some testing of the latest FlowBlade and update the build assuming nothing crashes and burns horribly. I'd love to hear other maintainer's input about checksums from github. To my knowledge, there are none from Github upstream unless the developer goes out of their way to post them somewhere. For SBo, I just generate an md5sum based on what I've downloaded and put that into .info. Not great, I know, but at least it's a fingerprint. -klaatu On 2017-05-03 04:08, General wrote: > FAO Maintainer (cc'd slackbuilds-users) Klaatu > > Flowblade is several releases on now (1.12 ?). With respect to the > effort > involved, I was wondering if 'we' might be seeing an update to the > latest > version soon please? > > I've had a go a running the build script against 1.10 and it seemed to > go > ok, but I'm never too sure ;-) > > Which leads me to another [general] question: when getting a source of > Github (of which I am not too familiar) , what happens in terms of > process > that leads to the md5sum's on the slackbuilds.org..... I could not see > any > published [by the developers] any checksums etc ? > > Keep up the good work everyone. It does not get said enough probably, > but > the time and effort that contributors and maintainers etc put in to > this > SlackBuilds project (and quality open source in general) is most > appreciated. Thank you. > > > Habs From brent at exitstatusone.com Tue May 2 18:27:19 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 2 May 2017 12:27:19 -0600 Subject: [Slackbuilds-users] driftnet slackbuild Message-ID: <20170502182719.GA25502@gmail.com> Hello, The driftnet SlackBuild has significant new development. The new release can be found here: https://github.com/deiv/driftnet It appears that you have been inactive for quite some time. I can take over maintenance if you are no longer interested in maintaining driftnet. Thanks, Brenton From hostmaster at slackonly.com Tue May 2 19:06:19 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Tue, 2 May 2017 12:06:19 -0700 Subject: [Slackbuilds-users] Terminator SlackBuild Message-ID: Hi!, Terminator latest version is already in 1.91 and after the new updates in Slackware-current needs a upgrade. Can you please upgrade it to the latest version? A simple bump version update in SlackBuild is quite enough. I can take over maintenance if you are no longer interested in maintaining terminator. Thank you. From joshuakwood at gmail.com Tue May 2 19:39:12 2017 From: joshuakwood at gmail.com (JK Wood) Date: Tue, 2 May 2017 14:39:12 -0500 Subject: [Slackbuilds-users] driftnet slackbuild In-Reply-To: <20170502182719.GA25502@gmail.com> References: <20170502182719.GA25502@gmail.com> Message-ID: On May 2, 2017 13:27, "Brenton Earl" wrote: Hello, The driftnet SlackBuild has significant new development. The new release can be found here: https://github.com/deiv/driftnet It appears that you have been inactive for quite some time. I can take over maintenance if you are no longer interested in maintaining driftnet. Thanks, Brenton Hi Brenton, You're welcome to take over driftnet. I had some build problems the last time I took a look at it, but hopefully that's been resolved. Thanks, JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From gen-bch at useyouresp.org.uk Tue May 2 20:04:24 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Tue, 2 May 2017 21:04:24 +0100 Subject: [Slackbuilds-users] Flowblade In-Reply-To: References: Message-ID: <20170502210424.4b8232b3@dv6920ea.localdomain> Hi there Klaatu Thank you for replying. > I don't personally like to rush into updates on stable software. Yes I agree with you. My request was driven out of an annoying thing I couldnt find a solution for. The 'render with args' check and edit boxes do not show up on 'small screens' and it seems there is no config item to get FB to switch off 'small screen checking' and so [hopefully] display the render args sections. There's a few posts, but it came down to updating being a better solution with the other things changed since the 1.6. The later builds have allegedly fixed the issue. Any way, I realise there is a fair bit of work, checking and testing, so thank you for considering and I will be pleased when you get some time to have a look. Cheers Keep well Habs On Wed, 03 May 2017 05:39:04 +1200 klaatu at mixedsignals.ml wrote: > Hi Habs, > > I can update FlowBlade, but if your build is going well, it's > probably just as good as whatever I'll post. You can start editing > with what you've got. > > I don't personally like to rush into updates on stable software. I'll > do some testing of the latest FlowBlade and update the build assuming > nothing crashes and burns horribly. > > I'd love to hear other maintainer's input about checksums from > github. To my knowledge, there are none from Github upstream unless > the developer goes out of their way to post them somewhere. For SBo, > I just generate an md5sum based on what I've downloaded and put that > into .info. Not great, I know, but at least it's a fingerprint. > > -klaatu > > > > > On 2017-05-03 04:08, General wrote: > > FAO Maintainer (cc'd slackbuilds-users) Klaatu > > > > Flowblade is several releases on now (1.12 ?). With respect to the > > effort > > involved, I was wondering if 'we' might be seeing an update to the > > latest > > version soon please? > > > > I've had a go a running the build script against 1.10 and it seemed > > to go > > ok, but I'm never too sure ;-) > > > > Which leads me to another [general] question: when getting a > > source of Github (of which I am not too familiar) , what happens in > > terms of process > > that leads to the md5sum's on the slackbuilds.org..... I could not > > see any > > published [by the developers] any checksums etc ? > > > > Keep up the good work everyone. It does not get said enough > > probably, but > > the time and effort that contributors and maintainers etc put in to > > this > > SlackBuilds project (and quality open source in general) is most > > appreciated. Thank you. > > > > > > Habs From kjhambrick at gmail.com Tue May 2 20:17:20 2017 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Tue, 2 May 2017 15:17:20 -0500 Subject: [Slackbuilds-users] bump erlang-otp version 19.2 -> version 19.3 Message-ID: Ryan -- Attached are diffs to bump erlang-otp from version 19.2 to 19.3 The MD5SUMs came from http://erlang.org/download/MD5 Thanks ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- --- erlang-otp.info-19.2 2017-02-13 15:54:35.125083593 -0600 +++ erlang-otp.info 2017-05-02 04:12:03.456788417 -0500 @@ -1,10 +1,10 @@ PRGNAM="erlang-otp" -VERSION="19.2" +VERSION="19.3" HOMEPAGE="http://www.erlang.org" -DOWNLOAD="http://www.erlang.org/download/otp_src_19.2.tar.gz \ - http://www.erlang.org/download/otp_doc_man_19.2.tar.gz" -MD5SUM="7cdd18a826dd7bda0ca46d1c3b2efca6 \ - 4464aa2a63196880883de9636e177cff" +DOWNLOAD="http://www.erlang.org/download/otp_src_19.3.tar.gz \ + http://www.erlang.org/download/otp_doc_man_19.3.tar.gz" +MD5SUM="a8c259ec47bf84e77510673e1b76b6db \ + 63f115d98934f4483a0341c567193747" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -------------- next part -------------- --- erlang-otp.SlackBuild-19.2 2017-02-13 15:54:35.125083593 -0600 +++ erlang-otp.SlackBuild 2017-05-02 04:09:24.445775023 -0500 @@ -21,7 +21,7 @@ # of README in upstream PRGNAM=erlang-otp -VERSION=${VERSION:-19.2} +VERSION=${VERSION:-19.3} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} From brent at exitstatusone.com Tue May 2 20:20:58 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 2 May 2017 14:20:58 -0600 Subject: [Slackbuilds-users] zim 0.65 to 0.66 Message-ID: <20170502202058.GA1039@gmail.com> Hello, Zim 0.66 has been released. I ran into a problem building it and the solution I found was enabling UTF-8 as the system locale. As I am sure you are all aware, Slackware 14.2 does not use UTF-8 in a stock installation. Is there some way to work around this issue? I seem to remember reading somewhere that Slackware-current has moved to a UTF-8 system wide locale. Should I leave zim as is until the next release of Slackware where UTF-8 is the default? Or should I update zim and make a note in the README that UTF-8 is required? Thanks, Brenton From yalhcru at gmail.com Tue May 2 20:25:50 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 2 May 2017 16:25:50 -0400 Subject: [Slackbuilds-users] zim 0.65 to 0.66 In-Reply-To: <20170502202058.GA1039@gmail.com> References: <20170502202058.GA1039@gmail.com> Message-ID: On 5/2/17, Brenton Earl wrote: > Or should I update zim and make a note in the README that UTF-8 is > required? Is a UTF-8 locale only required at build time, or is it also required to run the program after it's installed? If it's only needed at build time, you can force it in your SlackBuild, something like: export LANG=en_US.UTF-8 ...near the top of the script. From brent at exitstatusone.com Tue May 2 20:44:44 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 2 May 2017 14:44:44 -0600 Subject: [Slackbuilds-users] zim 0.65 to 0.66 In-Reply-To: References: <20170502202058.GA1039@gmail.com> Message-ID: <20170502204444.GA2556@gmail.com> On Tue, May 02, 2017 at 04:25:50PM -0400, B Watson wrote: > Is a UTF-8 locale only required at build time, or is it also required > to run the program after it's installed? > > If it's only needed at build time, you can force it in your SlackBuild, > something like: > > export LANG=en_US.UTF-8 > > ...near the top of the script. It's a build and run time requirement. Thanks, Brent From yalhcru at gmail.com Tue May 2 20:44:52 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 2 May 2017 16:44:52 -0400 Subject: [Slackbuilds-users] zim 0.65 to 0.66 In-Reply-To: References: <20170502202058.GA1039@gmail.com> Message-ID: On 5/2/17, B Watson wrote: > Is a UTF-8 locale only required at build time, or is it also required > to run the program after it's installed? Replying to myself... It's required at both build time and run time. It's a silly bug, and seems easily fixed (even by a non-Python person like me). Diff is here: http://urchlay.naptime.net/~urchlay/src/logger.fix.diff.gz In the SlackBuild, apply it like so, just before the 'python setup.py' line: zcat $CWD/logger.fix.diff.gz | patch -p1 I haven't thoroughly tested zim with the patch applied (since I don't even know/care how to use it), but at least it builds a package, and after installing, the application starts up even with LANG=en_US or LANG=C in the environment. Hope it works OK in your testing. From brent at exitstatusone.com Tue May 2 21:04:20 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 2 May 2017 15:04:20 -0600 Subject: [Slackbuilds-users] zim 0.65 to 0.66 In-Reply-To: References: <20170502202058.GA1039@gmail.com> Message-ID: <20170502210420.GA2725@gmail.com> On Tue, May 02, 2017 at 04:44:52PM -0400, B Watson wrote: > On 5/2/17, B Watson wrote: > > > Is a UTF-8 locale only required at build time, or is it also required > > to run the program after it's installed? > > Replying to myself... > > It's required at both build time and run time. It's a silly bug, and > seems easily fixed (even by a non-Python person like me). Diff is here: > > http://urchlay.naptime.net/~urchlay/src/logger.fix.diff.gz > > In the SlackBuild, apply it like so, just before the 'python setup.py' line: > > zcat $CWD/logger.fix.diff.gz | patch -p1 > > I haven't thoroughly tested zim with the patch applied (since I don't > even know/care how to use it), but at least it builds a package, and > after installing, the application starts up even with LANG=en_US or > LANG=C in the environment. Hope it works OK in your testing. Thanks for the help. Very much appreciated. Best Regards, Brent From skaendo at excite.com Tue May 2 22:34:49 2017 From: skaendo at excite.com (Ed Ender) Date: Tue, 02 May 2017 18:34:49 -0400 Subject: [Slackbuilds-users] Terminator Message-ID: <20170502183449.10812@web004.roc2.bluetie.com> I know I'm not the maintainer, but Terminator 1.91 is still a pre-release candidate and they are asking people to use it and look for bugs. If you want, I have a SlackBuild for 1.91 in my GitHub repo that was just fixed from Alan's script. Please note that psutil and vte3 are now dependencies. https://github.com/Skaendo/slackbuilds From khronosschoty at posteo.org Wed May 3 02:18:25 2017 From: khronosschoty at posteo.org (Vasily Sora) Date: Tue, 2 May 2017 18:18:25 -0800 Subject: [Slackbuilds-users] gcc 4.9.4 and PaleMoon.SlackBuild Message-ID: <20170502181825.3d65a98b@darkstar> Hi, I know some people still have issues with compiling PaleMoon with the SlackBuild on SBo that builds Pale Moon from source; technically according to the Pale Moon wiki and devs gcc 4.7 to 4.9 series is required to build a stable Pale Moon. I was wondering if its reasonable to build a temporary gcc 4.9.4, in much the same way as autoconf is being built and used temporarily, or at least give the user the option to, and use that to build pale moon. I am testing this out right now and seeing if I can resolve any issues for people who still complain they have issues. From n0nb at n0nb.us Wed May 3 02:25:21 2017 From: n0nb at n0nb.us (Nate Bargmann) Date: Tue, 2 May 2017 21:25:21 -0500 Subject: [Slackbuilds-users] md5sums [was: Flowblade] In-Reply-To: <20170502174753.0e02db87@dv6920ea.localdomain> References: <20170502174753.0e02db87@dv6920ea.localdomain> Message-ID: <20170503022521.GD5407@n0nb.us> * On 2017 02 May 11:49 -0500, Habs wrote: > Thank you for the reply. Ahh I see. I had it in my mind that > upstream/devs would post a [sourse] release as such with some checksum, > so that when it arrived elsewhere it could be validated (as best one > can) to not have been meddled with. Some sites that host projects such as SourceForge.net do provide MD5 and SHA* sums. Whenever I upload a file for distribution to SF I make sure their calculations match mine generated locally. Other sites/projects will provide a GPG signature, etc. HTH, - Nate -- "The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true." Ham radio, Linux, bikes, and more: http://www.n0nb.us -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From hostmaster at slackonly.com Wed May 3 02:41:41 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Tue, 2 May 2017 19:41:41 -0700 Subject: [Slackbuilds-users] Terminator In-Reply-To: <20170502183449.10812@web004.roc2.bluetie.com> References: <20170502183449.10812@web004.roc2.bluetie.com> Message-ID: <3da0b296-0452-199f-a4d0-1cac14f93641@slackonly.com> > I know I'm not the maintainer, but Terminator 1.91 is still a pre-release candidate and they are asking people to use it and look for bugs. Are you have more details about that? Did you check the follow links? https://gnometerminator.blogspot.com/2017/02/terminator-191-on-time-for-change.html https://launchpad.net/terminator/gtk3/1.91 >From the Changelog: (Regression release. Did it work in gtk2? Not working for gtk3? Hopefully they'll all be fixed here.) Few of them is: enable the use of the hyper key as a modifier in shortcuts; updated the preferences window to a modern version of glade. This should result in better spacing, layout etc.; add the gruvbox light/dark palettes as themes; add subtrees to custom commands menu - just add '/' to split; fix the background transparency, also allowing per theme CSS fixes and styling tweaks; fix the regression of the initial scrollbar state not being; fix the middle mouse button not getting passed to tmux; fix oversized splitter bar hover area for Adwaita and any other theme that does this; fix the logger plugin; fix system fonts to pull values from dconf, not gconf; fix focus/z-order issue introduced by GTK3 port; > If you want, I have a SlackBuild for 1.91 in my GitHub repo that was just fixed from Alan's script. > Please note that psutil and vte3 are now dependencies. > > https://github.com/Skaendo/slackbuilds > _______________________________________________ I'm already running Terminator 1.91 (From SlackBuilds) without vte3 and I didn't found any problem until now. The changes from the original SlackBuild are only these: -VERSION=${VERSION:-1.0} +VERSION=${VERSION:-1.91} -DOCS="INSTALL COPYING RELEASING README ChangeLog" +DOCS="INSTALL COPYING README ChangeLog" -------------- next part -------------- An HTML attachment was scrubbed... URL: From northrup at yellowapple.us Wed May 3 05:38:07 2017 From: northrup at yellowapple.us (Ryan S. Northrup) Date: Wed, 03 May 2017 05:38:07 +0000 Subject: [Slackbuilds-users] bump erlang-otp version 19.2 -> version 19.3 In-Reply-To: References: Message-ID: <61F27D1B-75AC-40DA-80D9-319B030761A7@yellowapple.us> On May 2, 2017 1:17:20 PM PDT, Konrad J Hambrick wrote: >Ryan -- > >Attached are diffs to bump erlang-otp from version 19.2 to 19.3 > >The MD5SUMs came from http://erlang.org/download/MD5 > >Thanks ! > >-- kjh Awesome, thanks! I'll have a look when I get a moment. Meanwhile, if you don't mind, submitting a PR to github.com/YellowApple/slackbuilds with the relevant changes would save me a bit of work :) -- Ryan S. Northrup northrup at yellowapple.us From baildon.research at googlemail.com Wed May 3 06:50:34 2017 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 3 May 2017 07:50:34 +0100 Subject: [Slackbuilds-users] gcc 4.9.4 and PaleMoon.SlackBuild In-Reply-To: <20170502181825.3d65a98b@darkstar> References: <20170502181825.3d65a98b@darkstar> Message-ID: > I know some people still have issues with compiling PaleMoon with the > SlackBuild on SBo that builds Pale Moon from source; technically > according to the Pale Moon wiki and devs gcc 4.7 to 4.9 series is > required to build a stable Pale Moon. I was wondering if its reasonable > to build a temporary gcc 4.9.4, in much the same way as autoconf is > being built and used temporarily, or at least give the user the option > to, and use that to build pale moon. I am testing this out right now > and seeing if I can resolve any issues for people who still complain > they have issues. What are these people *thinking*? If the other admins think something based on https://github.com/idlemoor/distcc-tools/tree/master/gcc-legacy would be acceptable in the repo, I'll clean it up and submit it (but it won't be until next week). -D. From fellype at gmail.com Wed May 3 13:30:28 2017 From: fellype at gmail.com (Fellype do Nascimento) Date: Wed, 3 May 2017 10:30:28 -0300 Subject: [Slackbuilds-users] New maintainer for sayonara-player.SlackBuild In-Reply-To: <760589445.891624.1493758998668@mail.yahoo.com> References: <760589445.891624.1493758998668@mail.yahoo.com> Message-ID: <09fcb6cd-2afa-aa22-b55a-58a9bc02d69b@gmail.com> Hi all! I'm taking maintenance of sayonara-player.SlackBuild. I have authorization from the last maintainer, as indicated below. Best regards, Fellype -------- Forwarded Message -------- Subject: Assunto: Small suggestion for sayonara-player.SlackBuild Date: Tue, 2 May 2017 21:03:18 +0000 (UTC) From: edps.mundognu at gmail.com Reply-To: edps.mundognu at gmail.com To: fellype at gmail.com You can take sayonara if interested, i'm not using anymore. * if no: i can fix this. :) Enviado do Yahoo Mail no Android -------------- next part -------------- An HTML attachment was scrubbed... URL: From edps.mundognu at gmail.com Wed May 3 22:38:47 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 03 May 2017 19:38:47 -0300 Subject: [Slackbuilds-users] New maintainer for sayonara-player.SlackBuild Message-ID: Good luck Fellype! I already sent the new update to sayonara-player (version 0.9.3), after next weekend it's yours! :) Cheers, Edinaldo. From khronosschoty at posteo.org Thu May 4 01:31:38 2017 From: khronosschoty at posteo.org (Vasily Sora) Date: Wed, 3 May 2017 17:31:38 -0800 Subject: [Slackbuilds-users] gcc-legacy In-Reply-To: References: Message-ID: <20170503173138.19fb5523@darkstar> On Wed, 03 May 2017 22:38:54 +0000 slackbuilds-users-request at slackbuilds.org wrote: > What are these people *thinking*? > > If the other admins think something based on > https://github.com/idlemoor/distcc-tools/tree/master/gcc-legacy > would be acceptable in the repo, I'll clean it up and submit it (but > it won't be until next week). > > -D. If that is acceptable to the others and you are willing to clean it up, it would certainly make things easier for the PaleMoon script. I would thank you if this can be done. From chris.willing at iinet.net.au Thu May 4 01:56:59 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 4 May 2017 11:56:59 +1000 Subject: [Slackbuilds-users] gcc-legacy In-Reply-To: <20170503173138.19fb5523@darkstar> References: <20170503173138.19fb5523@darkstar> Message-ID: On 04/05/17 11:31, Vasily Sora wrote: > On Wed, 03 May 2017 22:38:54 +0000 > slackbuilds-users-request at slackbuilds.org wrote: > >> What are these people *thinking*? >> >> If the other admins think something based on >> https://github.com/idlemoor/distcc-tools/tree/master/gcc-legacy >> would be acceptable in the repo, I'll clean it up and submit it (but >> it won't be until next week). >> >> -D. > > > If that is acceptable to the others and you are willing to clean it up, > it would certainly make things easier for the PaleMoon script. I would > thank you if this can be done. > If that is included, could its use be made optional somehow please? I've just build 27.3.0 on 14.2 from the SlackBuild, changing only the version number. For my personal usage, I've seen no problems with the result yet. I understand others may have different usage patterns or frequent sites which trigger problems and therefore need something extra like this. However it would be a shame to inflict it on all those who don't. chris PS. I've seen only vague descriptions of the problems people are having when using the new PaleMoon not built with the earlier gcc version. It would be good to see something more definite about these problems so others can test/verify them. From matteo.bernardini at gmail.com Thu May 4 04:37:42 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 4 May 2017 06:37:42 +0200 Subject: [Slackbuilds-users] gcc-legacy In-Reply-To: References: <20170503173138.19fb5523@darkstar> Message-ID: 2017-05-04 3:56 GMT+02:00 Christoph Willing : > PS. I've seen only vague descriptions of the problems people are having > when using the new PaleMoon not built with the earlier gcc version. It > would be good to see something more definite about these problems so > others can test/verify them. for this might be useful the ENABLE_DEBUG parameter in the SlackBuild but, still for people experiencing crashes, have a look also at the OPTIMIZE one https://slackbuilds.org/repository/14.2/network/PaleMoon/ Matteo From s.arcus at open-t.co.uk Thu May 4 11:55:03 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 4 May 2017 12:55:03 +0100 Subject: [Slackbuilds-users] Libvirt package - small change to /etc/rc.d/rc.libvirt Message-ID: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> I have a small change to suggest for the /etc/rc.d/rc.libvirt script. The script at the moment does a 'virsh shutdown ' on all running guests, and then, after waiting only 40 seconds, it destroys all guests which are still running. I think in most circumstances this is very likely to lead to corrupted guests because: 1. Many guests will take longer than 40 seconds to shutdown, specially if they are Windows guests. 2. Some Windows guests might be trying to install updates on shutdown, which can take 10, 20 or even 60 minutes. 3. If there are a number of guests running and the host is busy trying to shut them all down at the same time, even Linux guests will still be in the process of shutting down after 40 seconds. 4. If it is a setup where users connect to guests remotely, it is possible that people are in the middle of doing work which would be lost. Would it maybe be safer to do a 'virsh managedsave ' on every running guest instead? I can see many advantages to this option, including: 1. It is much less likely for users who might use the guests remotely to loose work, as the machine state is suspended. 2. Guests stopped with 'managedsave' will start fine with the 'start' command - so no need to change any settings anywhere else, and the 'autostart' feature of libvirt will continue to work fine. 2. On my server, the 'managedsave' operation takes around 20 seconds per guest, and it is more predictable in duration than a 'shutdown', which depends on the OS in the guest, if it is installing updates etc. 4. The 'managedsave' command doesn't return immediately, so we can wait for each guest in turn and know when it is done. Or ampersand could be used on the command, and then just do a looped check on 'virsh list' lower down, waiting for the 'managedsave' on all guests to finish. 5. If my understanding is correct, the 'shutdown' command depends on the guest implementing correctly and acting on ACPI commands, while a 'managedsave' seems to be under the complete control of libvirt - which means the script would work correctly out of the box with a much wider variety of OS's and configurations on the guest side. If necessary, I suppose the script could also implement a 'reboot_guests' separate command, for people to use it to reboot all running guests - as the "stop" command wouldn't be performing a full shutdown any more. Just a suggestion in case it helps. I'm already very happy with the current script, as I used to have to write my own to shutdown kvm/qemu guests :-) From dpross1100 at msn.com Fri May 5 02:52:01 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Fri, 5 May 2017 02:52:01 +0000 Subject: [Slackbuilds-users] gcc-legacy In-Reply-To: References: <20170503173138.19fb5523@darkstar> Message-ID: I completed some tests today with SBo's PaleMoon (the from-source version). I found two sites where it segfaults consistently, no matter whether I use the ENABLE_DEBUG and OPTIMIZE=-Os or the default parameters. I also applied the workaround for the Oxygen gtk2 theme that is mentioned in the README. The sites are: https://www.yahoo.com/ and http://hfboards.hockeysfuture.com/ In both cases, just opening up the page would result in a segfault within a few seconds. For reference, this is on Slackware64-14.2 with gcc-5.3.0. Following that, I compiled gcc-4.9.4 and used it instead to build PaleMoon. Other than that change, the default parameters from the script were used. This fixed the problem, and now neither site segfaults. I also tried with the other PaleMoon ("palemoon") on SBo that repackages the official binary, and with Alien Bob's Pale Moon package. Neither of those have trouble with those two sites either. More discussion here: http://www.linuxquestions.org/questions/slackware-14/palemoon-from-source-slackbuild-4175605127/ Dan On Thu, May 04, 2017 at 06:37:42AM +0200, Matteo Bernardini wrote: > 2017-05-04 3:56 GMT+02:00 Christoph Willing : > > PS. I've seen only vague descriptions of the problems people are having > > when using the new PaleMoon not built with the earlier gcc version. It > > would be good to see something more definite about these problems so > > others can test/verify them. > > for this might be useful the ENABLE_DEBUG parameter in the SlackBuild > but, still for people experiencing crashes, have a look also at the > OPTIMIZE one > > https://slackbuilds.org/repository/14.2/network/PaleMoon/ > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From dpross1100 at msn.com Fri May 5 14:22:16 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Fri, 5 May 2017 14:22:16 +0000 Subject: [Slackbuilds-users] gcc-legacy In-Reply-To: References: <20170503173138.19fb5523@darkstar> Message-ID: I posted this on LQ as well, but I just tried compiling Pale Moon with clang/clang++ and the default flags. It works fine with no segfaults. Personally, I'd prefer this route instead of requiring a legacy gcc. Dan On Fri, May 05, 2017 at 02:52:01AM +0000, Daniel Prosser wrote: > I completed some tests today with SBo's PaleMoon (the from-source > version). I found two sites where it segfaults consistently, no matter > whether I use the ENABLE_DEBUG and OPTIMIZE=-Os or the default > parameters. I also applied the workaround for the Oxygen gtk2 theme that > is mentioned in the README. The sites are: > > https://www.yahoo.com/ and > http://hfboards.hockeysfuture.com/ > > In both cases, just opening up the page would result in a segfault > within a few seconds. For reference, this is on Slackware64-14.2 with > gcc-5.3.0. > > Following that, I compiled gcc-4.9.4 and used it instead to build > PaleMoon. Other than that change, the default parameters from the script > were used. This fixed the problem, and now neither site segfaults. I > also tried with the other PaleMoon ("palemoon") on SBo that repackages > the official binary, and with Alien Bob's Pale Moon package. Neither of > those have trouble with those two sites either. > > More discussion here: > > http://www.linuxquestions.org/questions/slackware-14/palemoon-from-source-slackbuild-4175605127/ > > Dan > > On Thu, May 04, 2017 at 06:37:42AM +0200, Matteo Bernardini wrote: > > 2017-05-04 3:56 GMT+02:00 Christoph Willing : > > > PS. I've seen only vague descriptions of the problems people are having > > > when using the new PaleMoon not built with the earlier gcc version. It > > > would be good to see something more definite about these problems so > > > others can test/verify them. > > > > for this might be useful the ENABLE_DEBUG parameter in the SlackBuild > > but, still for people experiencing crashes, have a look also at the > > OPTIMIZE one > > > > https://slackbuilds.org/repository/14.2/network/PaleMoon/ > > > > Matteo > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From rworkman at slackbuilds.org Fri May 5 14:50:08 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 5 May 2017 09:50:08 -0500 Subject: [Slackbuilds-users] Libvirt package - small change to /etc/rc.d/rc.libvirt In-Reply-To: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> References: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> Message-ID: <20170505095008.1e130300@home.rlworkman.net> On Thu, 4 May 2017 12:55:03 +0100 Sebastian Arcus wrote: > I have a small change to suggest for the /etc/rc.d/rc.libvirt script. > The script at the moment does a 'virsh shutdown ' on all > running guests, and then, after waiting only 40 seconds, it destroys > all guests which are still running. I think in most circumstances > this is very likely to lead to corrupted guests because: > > 1. Many guests will take longer than 40 seconds to shutdown, > specially if they are Windows guests. > 2. Some Windows guests might be trying to install updates on > shutdown, which can take 10, 20 or even 60 minutes. > 3. If there are a number of guests running and the host is busy > trying to shut them all down at the same time, even Linux guests will > still be in the process of shutting down after 40 seconds. > 4. If it is a setup where users connect to guests remotely, it is > possible that people are in the middle of doing work which would be > lost. > > Would it maybe be safer to do a 'virsh managedsave ' on > every running guest instead? I can see many advantages to this > option, including: > > 1. It is much less likely for users who might use the guests remotely > to loose work, as the machine state is suspended. > > 2. Guests stopped with 'managedsave' will start fine with the 'start' > command - so no need to change any settings anywhere else, and the > 'autostart' feature of libvirt will continue to work fine. > > 2. On my server, the 'managedsave' operation takes around 20 seconds > per guest, and it is more predictable in duration than a 'shutdown', > which depends on the OS in the guest, if it is installing updates etc. > > 4. The 'managedsave' command doesn't return immediately, so we can > wait for each guest in turn and know when it is done. Or ampersand > could be used on the command, and then just do a looped check on > 'virsh list' lower down, waiting for the 'managedsave' on all guests > to finish. > > 5. If my understanding is correct, the 'shutdown' command depends on > the guest implementing correctly and acting on ACPI commands, while a > 'managedsave' seems to be under the complete control of libvirt - > which means the script would work correctly out of the box with a > much wider variety of OS's and configurations on the guest side. > > If necessary, I suppose the script could also implement a > 'reboot_guests' separate command, for people to use it to reboot all > running guests - as the "stop" command wouldn't be performing a full > shutdown any more. > > Just a suggestion in case it helps. I'm already very happy with the > current script, as I used to have to write my own to shutdown > kvm/qemu guests :-) This seems like a reasonable change. Can you push it to a git repo/branch somewhere and send me a link, or else send me a patch(set) to merge? -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 matteo.bernardini at gmail.com Fri May 5 15:15:05 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 5 May 2017 17:15:05 +0200 Subject: [Slackbuilds-users] Libvirt package - small change to /etc/rc.d/rc.libvirt In-Reply-To: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> References: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> Message-ID: 2017-05-04 13:55 GMT+02:00 Sebastian Arcus : > I have a small change to suggest for the /etc/rc.d/rc.libvirt script. The > script at the moment does a 'virsh shutdown ' on all running > guests, and then, after waiting only 40 seconds, it destroys all guests > which are still running. I think in most circumstances this is very likely > to lead to corrupted guests because: > > 1. Many guests will take longer than 40 seconds to shutdown, specially if > they are Windows guests. > 2. Some Windows guests might be trying to install updates on shutdown, which > can take 10, 20 or even 60 minutes. > 3. If there are a number of guests running and the host is busy trying to > shut them all down at the same time, even Linux guests will still be in the > process of shutting down after 40 seconds. > 4. If it is a setup where users connect to guests remotely, it is possible > that people are in the middle of doing work which would be lost. > > Would it maybe be safer to do a 'virsh managedsave ' on every > running guest instead? I can see many advantages to this option, including: one potential gotcha that I can foresee with this approach might be that managedsave, creating a RAM image of the virtual machine, will need an amount of Gb of disk space in /var/lib/libvirt/qemu/save/ the same size of the RAM used by all the running virtual machines: on my 64 Gb virtualization server I don't have, for example, that amount of space in the root partition. I'm just thinking out loud, don't misunderstand me :) Matteo From melikamp at melikamp.com Fri May 5 17:30:46 2017 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Fri, 05 May 2017 10:30:46 -0700 Subject: [Slackbuilds-users] source -> bin Message-ID: <3088351.zFUrQ3OOvj@ithil> I'd like to consider switching icecat from being source-based to a binary re- package. That's OK by the SBo rules, right? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed message part. URL: From willysr at slackbuilds.org Fri May 5 17:37:13 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 May 2017 00:37:13 +0700 Subject: [Slackbuilds-users] source -> bin In-Reply-To: <3088351.zFUrQ3OOvj@ithil> References: <3088351.zFUrQ3OOvj@ithil> Message-ID: <92b04e80-8f00-5bab-2872-3070325114ba@slackbuilds.org> > I'd like to consider switching icecat from being source-based to a binary re- > package. That's OK by the SBo rules, right? Yes, that's 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 fernando.lopezjr at gmail.com Fri May 5 19:32:58 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Fri, 5 May 2017 13:32:58 -0600 Subject: [Slackbuilds-users] source -> bin In-Reply-To: <92b04e80-8f00-5bab-2872-3070325114ba@slackbuilds.org> References: <3088351.zFUrQ3OOvj@ithil> <92b04e80-8f00-5bab-2872-3070325114ba@slackbuilds.org> Message-ID: perhaps making an additional icecat-bin package... would be better... my 2 cents. On May 5, 2017 11:37 AM, "Willy Sudiarto Raharjo" wrote: > I'd like to consider switching icecat from being source-based to a binary re- > package. That's OK by the SBo rules, right? Yes, that's fine. -- Willy Sudiarto Raharjo _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From melikamp at melikamp.com Fri May 5 19:37:59 2017 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Fri, 05 May 2017 12:37:59 -0700 Subject: [Slackbuilds-users] source -> bin In-Reply-To: References: <3088351.zFUrQ3OOvj@ithil> <92b04e80-8f00-5bab-2872-3070325114ba@slackbuilds.org> Message-ID: <11157279.GSYkLesToQ@ithil> Perhaps. I haven't decided yet, but I'd like to explore the bin option because building firefox is such a pita, what with autoconf madness now too.... While gnuzilla provides binaries for x32 and x64, and they are built with appropriate options and all that. On Friday, May 05, 2017 13:32:58 Fernando Lopez wrote: > perhaps making an additional icecat-bin package... would be better... my 2 > cents. > > > On May 5, 2017 11:37 AM, "Willy Sudiarto Raharjo" > > wrote: > > I'd like to consider switching icecat from being source-based to a binary > > re- > > > package. That's OK by the SBo rules, right? > > Yes, that's fine. > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed message part. URL: From edps.mundognu at gmail.com Sat May 6 00:11:50 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Fri, 05 May 2017 21:11:50 -0300 Subject: [Slackbuilds-users] removal request: perl-Gtk2-CodeGen Message-ID: perl-Gtk2-CodeGen has the same code as SlackBuild perl-gtk2, so i'm updating dependency for "perl-Gtk2-Notify" and request removal of perl-Gtk2-CodeGen. Thanks, Edinaldo. From willysr at slackbuilds.org Sat May 6 00:32:08 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 May 2017 07:32:08 +0700 Subject: [Slackbuilds-users] Updates - 20170506.1 Message-ID: First update in May Thanks to some maintainers, we have reduced the number of scripts in pasture by taking over orphaned scripts. We still have more than 100 scripts at this moment. Let us know if you are interested to take over some of them. As you may have seen, -current is now moving on with it's basic toolchain upgraded (GCC, glibc, and kernel), so there's a chance that some of the scripts in the repository might be broken at this moment if you are running -current. If someone found a patch for -current, please make sure that it works for -stable since SBo is tested against latest -stable, not -current. Otherwise, let's keep that until next development cycle. small note: rubygem-gosu had a typo in the .info and it has been fixed in the tarball and .info at the last minute. Here's the changelog for May's first update Sat May 6 00:05:04 UTC 2017 academic/bpp-core: Added (Bio++ Core Library). academic/bpp-phyl-omics: Added (Bio++ Phylogenetic Omics Library). academic/bpp-phyl: Added (Bio++ Phylogenetic Library). academic/bpp-popgen: Added (Bio++ Population Genetics Library). academic/bpp-seq-omics: Added (Bio++ Sequence Omics Library). academic/bpp-seq: Added (Bio++ Sequence library). academic/bppsuite: Added (Bio++ program suite). academic/exonerate: Added (A generic tool for sequence alignment). academic/gwyddion: Updated for version 2.48. academic/prank-msa: Added (probabilistic alignment program). audio/aacgain: Fix DOWNLOAD url. audio/deadbeef: Updated for version 0.7.2 + new maintainer. audio/museeks: Added (cross-platform music player). audio/sayonara-player: Updated for version 0.9.3. desktop/numix-icon-theme: Updated for version 0.3.895.201704281832. desktop/variety: Added (python library). desktop/xed: Updated for version 1.4.0. desktop/zuki-themes: Updated for version 3.22.2. development/byacc: Updated for version 20170430. development/cargo-vendor: Updated for version 0.1.8. development/cycler: Script update. development/diffoscope: Updated for version 82. development/erlang-otp: Updated for version 19.3. development/git-lfs: Updated for version 2.1.0. development/gtkextra: Updated for version 3.3.3 (moved from libs). development/nwjs: Updated for version 0.22.1. development/p4: Updated for version 2016.2.1509269. development/p4d: Updated for version 2016.2.1509269. development/pylint: Updated for version 1.7.1. development/python3-cycler: Added (composable cycles for Python 3). development/python3-matplotlib: Added (Python 2D plotting library). development/sbcl: Updated for version 1.3.17. games/fuse-emulator: Updated for version 1.3.5. games/ioquake3: Added mumble support. games/larn: Added (adventure game). games/lutris: Updated for version 0.4.8. gis/navit: Updated for version R7404. gis/pyshp: Updated for version 1.2.11. graphics/CairoSVG: Updated for version 2.0.3. libraries/DateTime: Updated for version 4.2. libraries/libkml: Added (KML library). libraries/libquvi-scripts: Updated for version 0.9.20131130. libraries/libquvi: Updated for version 0.9.4, new maintainer. libraries/libspectrum: Updated for version 1.3.3. libraries/rabbitmq-c: Added (library for RabbitMQ). libraries/rocksdb: Updated for version 5.3.4. libraries/wxGTK3: Updated for version 3.0.3. libraries/xmlsec: Updated for version 1.2.24. misc/ibus-anthy: Update DOWNLOAD url. misc/ibus-qt: Update DOWNLOAD url. misc/moreutils: Updated for version 0.61. multimedia/AtomicParsley: Added (mpeg4 tag tool). multimedia/HandBrake: Updated for version 1.0.7. multimedia/acetoneiso: Updated for version 2.4. multimedia/flowblade: Updated for version 1.12.2. network/PaleMoon: Updated for version 27.3.0. network/Signal-Desktop: Updated for version 0.38.2. network/cacti-spine: Updated for version 1.1.4. network/cacti: Updated for version 1.1.4. network/cclive: Updated for version 0.9.3, new maintainer. network/driftnet: Updated for version 1.1.5, new maintainer. network/filezilla: Updated for version 3.25.2. network/heimdal: Updated for version 7.3.0. network/kea: Updated for version 1.2.0. network/nikto: Updated for version 2.1.6. network/opensmtpd: Misc cleanups. network/opera-developer: Updated for version 46.0.2573.0. network/palemoon: Updated for version 27.3.0. network/putty: Updated for version 0.69. network/quvi: Updated for version 0.9.5, new maintainer. network/slimjet: Updated for version 14.0.5.0. network/speedtest-cli: Updated for version 1.0.6. network/sslscan: Updated for version 1.11.10. network/uTox: Updated for version 0.15.0 network/youtube-dl: Updated for version 2017.05.01. office/LibreOffice: Fix csh profile script. office/etmtk: Updated for version 3.2.30. office/hunspell-id: Added (Indonesian hunspell dictionary). office/hyphen-id: Added (Indonesian hyphenation library function). office/sc-im: Updated for version 0.6.0. office/wps-office: Use local path instead of all /tmp/SBo. office/xmind: Updated for version 8update2 + new maintainer. office/xreader: Updated for version 1.4.0. perl/perl-IO-Socket-Socks: Updated for version 0.74. python/functools-lru-cache: Added (Python module). python/ipython: Note jedi dependency. python/isort: Added (sort imports alphabetically). python/path.py: Fix DOWNLAOD url. python/pyresample: Updated for version 1.5.0. python/python-fonttools: Updated for version 3.11.0. python/python-lazy-object-proxy: Updated for version 1.3.0. python/python-requestbuilder: Updated for version 0.7.1 python3-pyzmq: Updated for version 16.0.2 ruby/rubygem-gosu: Updated for version 0.12.0. system/butterfly: Updated for version 3.1.2. system/eaglemode: Updated for version 0.93.0. system/fzf: Updated for version 0.16.7. system/glances: Updated for version 2.9.1. system/incron: Updated for version 0.6.0 + new maintainer. system/kitchen-sync: Updated for version 0.58. system/lsyncd: Updated for version 2.2.2. system/mksh: Updated for version R55. system/mlterm: Updated for version 3.8.1. system/noto-emoji: Updated for version git8056f38. system/noto-fonts: added conf files. system/signify: Added (cryptographically sign and verify files). system/ttf-crosscorefonts: Update HOMEPAGE and script. system/wine-staging: Fix email address. +--------------------------+ -- 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 Sat May 6 23:02:19 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 7 May 2017 09:02:19 +1000 Subject: [Slackbuilds-users] gcc-legacy In-Reply-To: References: <20170503173138.19fb5523@darkstar> Message-ID: <5b5ce549-1cb5-f369-b921-46fd2dcb0fac@iinet.net.au> On 04/05/17 11:56, Christoph Willing wrote: > > I've just build 27.3.0 on 14.2 from the SlackBuild, changing only the > version number. For my personal usage, I've seen no problems with the > result yet. I understand others may have different usage patterns or > frequent sites which trigger problems and therefore need something extra > like this. However it would be a shame to inflict it on all those who don't. > > chris > > PS. I've seen only vague descriptions of the problems people are having > when using the new PaleMoon not built with the earlier gcc version. It > would be good to see something more definite about these problems so > others can test/verify them. > Sites https://www.yahoo.com/ and http://hfboards.hockeysfuture.com/ have since been mentioned as triggering PaleMoon crashes and I have also found the same crashing problem with those sites. I've now built PaleMoon with clang as suggested by montagdude (see http://www.linuxquestions.org/questions/slackware-14/palemoon-from-source-slackbuild-4175605127/page3.html#post5706820). I left it running overnight with the rogue sites loaded in separate tabs. All still running OK this morning. Building with clang looks like a good solution. chris From baildon.research at googlemail.com Mon May 8 10:09:58 2017 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 8 May 2017 11:09:58 +0100 Subject: [Slackbuilds-users] removal request: perl-Gtk2-CodeGen In-Reply-To: References: Message-ID: > perl-Gtk2-CodeGen has the same code as SlackBuild perl-gtk2, so i'm updating > dependency for "perl-Gtk2-Notify" and request removal of perl-Gtk2-CodeGen. Done in my branch, thanks! I bet you all thought I'd forgotten this :) Cheers -D. From ekinakoglu at gmail.com Mon May 8 13:46:10 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Mon, 8 May 2017 16:46:10 +0300 Subject: [Slackbuilds-users] kdiff3-qt In-Reply-To: <84e67600-f5b2-6535-2105-61e42514c569@gmail.com> References: <1609981a-5532-f0a0-4c00-5333f17951eb@gmail.com> <201703312032.29137.ricardo@palmtx.com.ar> <84e67600-f5b2-6535-2105-61e42514c569@gmail.com> Message-ID: <9790788a-4249-6d62-a076-6e2a885ba13f@gmail.com> Hi, Is there any plan about the kdiff3 "Qt-only" build patch which I have sent two weeks ago? Will it be incorporated in the current SlackBuild in order to enable a "Qt-only" build of kdiff3 when "qt4" argument is passed to the SlackBuild? Kind regards, Ekin On 25/04/17 21:34, Ekin Akoglu wrote: > Hi Ricardo and all, > > As I promised, attached I send a patch for the kdiff3.Slackbuild to > enable the build option for Qt4 only when "qt4" is passed as an > argument to the SlackBuild script. This enables the installation of > kdiff3 for systems without kdelibs. > > Kind regards, > > Ekin > > > On 11/04/17 11:18, Ekin Akoglu wrote: >> Hi Ricardo, >> >> Thank you for your response. Currently I just modified the script so >> that it compiles directly for only Qt. >> >> I will prepare a proper conditional compilation patch and send it to >> you for your review in short time. >> >> Best, >> >> Ekin >> >> >> On 01/04/17 02:32, Ricardo J. Barberis wrote: >>> Hi Ekin, in 2016/01/24 Michiel gave up several of his slackbuilds and I >>> promised to take kdiff3 and others, but I have been busy at work >>> lately. >>> >>> I'll try to take a look at it this weekend (there's a couple other >>> sb's I have >>> to take care of as well) and see if I can do what you nedd. >>> >>> If you have a patch or something and want to send it, I'll gladly >>> take it :) >>> >>> Cheers, >>> >>> El Viernes 31/03/2017 a las 16:25, Ekin Akoglu escribi?: >>>> This is my second take on the issue. Do you have any suggestions for a >>>> possible kdiff3-qt SlackBuild? >>>> >>>> Michiel, would you accept a patch for a conditional compilation? >>>> >>>> Best, >>>> >>>> Ekin >>>> >>>> On 23/03/17 10:10, Ekin Akoglu wrote: >>>>> Dear all, >>>>> >>>>> I prepared a Qt-only SlackBuild of kdiff3 for installing on >>>>> environments without KDE libraries. Shall I submit this as a separate >>>>> SlackBuild or Michiel, the maintainer of kdiff3, will you favor a >>>>> patch for conditional compilation to your SlackBuild. What do you >>>>> suggest? >>>>> >>>>> Best, >>>>> >>>>> Ekin >> > From willysr at slackbuilds.org Mon May 8 14:32:10 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 8 May 2017 21:32:10 +0700 Subject: [Slackbuilds-users] kdiff3-qt In-Reply-To: <9790788a-4249-6d62-a076-6e2a885ba13f@gmail.com> References: <1609981a-5532-f0a0-4c00-5333f17951eb@gmail.com> <201703312032.29137.ricardo@palmtx.com.ar> <84e67600-f5b2-6535-2105-61e42514c569@gmail.com> <9790788a-4249-6d62-a076-6e2a885ba13f@gmail.com> Message-ID: > Is there any plan about the kdiff3 "Qt-only" build patch which I have > sent two weeks ago? Will it be incorporated in the current SlackBuild in > order to enable a "Qt-only" build of kdiff3 when "qt4" argument is > passed to the SlackBuild? Hi Ekin I reviewed your patch and it seems that it's partial as it doesn't update VERSION, DOWNLOAD, and MD5SUM in .info file as you bumped the VERSION in .SlackBuild. Also, since we support only full installation of latest Slackware -stable release (14.2), we assume that kdelibs is always installed on the system. Making the script accomodate all customized system is not a good idea. This is just my personal opinion. -- 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 andrei.alexsson at gmail.com Mon May 8 20:58:39 2017 From: andrei.alexsson at gmail.com (Andrei Alexsson) Date: Mon, 8 May 2017 22:58:39 +0200 Subject: [Slackbuilds-users] Motion not building on 14.2 64-bit Message-ID: Hi, I try to compile motion: https://slackbuilds.org/repository/14.2/system/motion/ on Slackware 14.2 64-bit. However, it does not compile successful when ffmpeg is installed. Any idea how to solve this? Thank you, Andrei From willysr at slackbuilds.org Mon May 8 23:35:56 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 9 May 2017 06:35:56 +0700 Subject: [Slackbuilds-users] Motion not building on 14.2 64-bit In-Reply-To: References: Message-ID: > I try to compile motion: > https://slackbuilds.org/repository/14.2/system/motion/ on Slackware 14.2 > 64-bit. However, it does not compile successful when ffmpeg is > installed. Any idea how to solve this? Hi, Thanks for reporting. It seems we missed this one when testing ffmpeg. It's now fixed on 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 ricardo at palmtx.com.ar Tue May 9 00:14:32 2017 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Mon, 08 May 2017 21:14:32 -0300 Subject: [Slackbuilds-users] kdiff3-qt In-Reply-To: <9790788a-4249-6d62-a076-6e2a885ba13f@gmail.com> References: <1609981a-5532-f0a0-4c00-5333f17951eb@gmail.com> <201703312032.29137.ricardo@palmtx.com.ar> <84e67600-f5b2-6535-2105-61e42514c569@gmail.com> <9790788a-4249-6d62-a076-6e2a885ba13f@gmail.com> Message-ID: <51967583546960c9a4c643a1910ccb0e@palmtx.com.ar> Hi Ekin and all, Sorry this took so long, I'm reviewing your patch right now and will accomodate it to SBo standards. I will also update the other files so I can submit an update in the next few hours. Cheers, El 08/05/2017 10:46, Ekin Akoglu escribi?: > Hi, > > Is there any plan about the kdiff3 "Qt-only" build patch which I have > sent two weeks ago? Will it be incorporated in the current SlackBuild > in order to enable a "Qt-only" build of kdiff3 when "qt4" argument is > passed to the SlackBuild? > > Kind regards, > > Ekin > > > On 25/04/17 21:34, Ekin Akoglu wrote: >> Hi Ricardo and all, >> >> As I promised, attached I send a patch for the kdiff3.Slackbuild to >> enable the build option for Qt4 only when "qt4" is passed as an >> argument to the SlackBuild script. This enables the installation of >> kdiff3 for systems without kdelibs. >> >> Kind regards, >> >> Ekin >> >> >> On 11/04/17 11:18, Ekin Akoglu wrote: >>> Hi Ricardo, >>> >>> Thank you for your response. Currently I just modified the script so >>> that it compiles directly for only Qt. >>> >>> I will prepare a proper conditional compilation patch and send it to >>> you for your review in short time. >>> >>> Best, >>> >>> Ekin >>> >>> >>> On 01/04/17 02:32, Ricardo J. Barberis wrote: >>>> Hi Ekin, in 2016/01/24 Michiel gave up several of his slackbuilds >>>> and I >>>> promised to take kdiff3 and others, but I have been busy at work >>>> lately. >>>> >>>> I'll try to take a look at it this weekend (there's a couple other >>>> sb's I have >>>> to take care of as well) and see if I can do what you nedd. >>>> >>>> If you have a patch or something and want to send it, I'll gladly >>>> take it :) >>>> >>>> Cheers, >>>> >>>> El Viernes 31/03/2017 a las 16:25, Ekin Akoglu escribi?: >>>>> This is my second take on the issue. Do you have any suggestions >>>>> for a >>>>> possible kdiff3-qt SlackBuild? >>>>> >>>>> Michiel, would you accept a patch for a conditional compilation? >>>>> >>>>> Best, >>>>> >>>>> Ekin >>>>> >>>>> On 23/03/17 10:10, Ekin Akoglu wrote: >>>>>> Dear all, >>>>>> >>>>>> I prepared a Qt-only SlackBuild of kdiff3 for installing on >>>>>> environments without KDE libraries. Shall I submit this as a >>>>>> separate >>>>>> SlackBuild or Michiel, the maintainer of kdiff3, will you favor a >>>>>> patch for conditional compilation to your SlackBuild. What do you >>>>>> suggest? >>>>>> >>>>>> Best, >>>>>> >>>>>> Ekin -- Living la vida Linux! From ricardo at palmtx.com.ar Tue May 9 03:26:31 2017 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Tue, 09 May 2017 00:26:31 -0300 Subject: [Slackbuilds-users] kdiff3-qt In-Reply-To: <51967583546960c9a4c643a1910ccb0e@palmtx.com.ar> References: <1609981a-5532-f0a0-4c00-5333f17951eb@gmail.com> <201703312032.29137.ricardo@palmtx.com.ar> <84e67600-f5b2-6535-2105-61e42514c569@gmail.com> <9790788a-4249-6d62-a076-6e2a885ba13f@gmail.com> <51967583546960c9a4c643a1910ccb0e@palmtx.com.ar> Message-ID: <088a24ad31926d48fbd18a30dbd45417@palmtx.com.ar> OK, I think I've got a nice set of files ready to submit. I modified Ekin's patch and added translations for the QT4ONLY version, so any blunder is mine :) Anyone cares to try it before I send it? Thanks! El 08/05/2017 21:14, Ricardo J. Barberis escribi?: > Hi Ekin and all, > > Sorry this took so long, I'm reviewing your patch right now and will > accomodate it to SBo standards. > I will also update the other files so I can submit an update in the > next few hours. > > Cheers, > > El 08/05/2017 10:46, Ekin Akoglu escribi?: >> Hi, >> >> Is there any plan about the kdiff3 "Qt-only" build patch which I have >> sent two weeks ago? Will it be incorporated in the current SlackBuild >> in order to enable a "Qt-only" build of kdiff3 when "qt4" argument is >> passed to the SlackBuild? >> >> Kind regards, >> >> Ekin >> >> >> On 25/04/17 21:34, Ekin Akoglu wrote: >>> Hi Ricardo and all, >>> >>> As I promised, attached I send a patch for the kdiff3.Slackbuild to >>> enable the build option for Qt4 only when "qt4" is passed as an >>> argument to the SlackBuild script. This enables the installation of >>> kdiff3 for systems without kdelibs. >>> >>> Kind regards, >>> >>> Ekin >>> >>> >>> On 11/04/17 11:18, Ekin Akoglu wrote: >>>> Hi Ricardo, >>>> >>>> Thank you for your response. Currently I just modified the script so >>>> that it compiles directly for only Qt. >>>> >>>> I will prepare a proper conditional compilation patch and send it to >>>> you for your review in short time. >>>> >>>> Best, >>>> >>>> Ekin >>>> >>>> >>>> On 01/04/17 02:32, Ricardo J. Barberis wrote: >>>>> Hi Ekin, in 2016/01/24 Michiel gave up several of his slackbuilds >>>>> and I >>>>> promised to take kdiff3 and others, but I have been busy at work >>>>> lately. >>>>> >>>>> I'll try to take a look at it this weekend (there's a couple other >>>>> sb's I have >>>>> to take care of as well) and see if I can do what you nedd. >>>>> >>>>> If you have a patch or something and want to send it, I'll gladly >>>>> take it :) >>>>> >>>>> Cheers, >>>>> >>>>> El Viernes 31/03/2017 a las 16:25, Ekin Akoglu escribi?: >>>>>> This is my second take on the issue. Do you have any suggestions >>>>>> for a >>>>>> possible kdiff3-qt SlackBuild? >>>>>> >>>>>> Michiel, would you accept a patch for a conditional compilation? >>>>>> >>>>>> Best, >>>>>> >>>>>> Ekin >>>>>> >>>>>> On 23/03/17 10:10, Ekin Akoglu wrote: >>>>>>> Dear all, >>>>>>> >>>>>>> I prepared a Qt-only SlackBuild of kdiff3 for installing on >>>>>>> environments without KDE libraries. Shall I submit this as a >>>>>>> separate >>>>>>> SlackBuild or Michiel, the maintainer of kdiff3, will you favor a >>>>>>> patch for conditional compilation to your SlackBuild. What do you >>>>>>> suggest? >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Ekin -- Living la vida Linux! -------------- next part -------------- A non-text attachment was scrubbed... Name: kdiff3.tar.gz Type: application/x-gzip Size: 3460 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue May 9 04:34:51 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 8 May 2017 21:34:51 -0700 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash Message-ID: I tried upgrading to wine-2.0.1 and got during configure: ------------- checking gnutls/gnutls.h usability... yes checking gnutls/gnutls.h presence... yes checking for gnutls/gnutls.h... yes checking for -lgnutls... not found checking for gnutls_hash... no configure: error: libgnutls 32-bit development files not found, no schannel support. This is an error since --with-gnutls was requested. --------------- Oddly, I'm running wine-2.0. Trying to rec-ompile wine-2.0 also now fails with the same error. wine-2.0 compiled fine on 01-FEB-2017 (the package I am currently using). All the updates to Slackware64 14.2 and multilib are installed as of 08-MAY-2017. I'll try later with a clean VM, but does anyone have any ideas? -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 May 9 04:54:47 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 9 May 2017 11:54:47 +0700 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: References: Message-ID: > I tried upgrading to wine-2.0.1 and got during configure: > ------------- > checking gnutls/gnutls.h usability... yes > checking gnutls/gnutls.h presence... yes > checking for gnutls/gnutls.h... yes > checking for -lgnutls... not found > checking for gnutls_hash... no > configure: error: libgnutls 32-bit development files not found, no > schannel support. > This is an error since --with-gnutls was requested. > --------------- > > Oddly, I'm running wine-2.0. Trying to rec-ompile wine-2.0 also now > fails with the same error. wine-2.0 compiled fine on 01-FEB-2017 (the > package I am currently using). All the updates to Slackware64 14.2 and > multilib are installed as of 08-MAY-2017. > > I'll try later with a clean VM, but does anyone have any ideas? have you tried to reinstall gnutls just in case it was overwritten? -- 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 May 9 05:04:08 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 8 May 2017 22:04:08 -0700 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: References: Message-ID: On 05/08/2017 09:54 PM, Willy Sudiarto Raharjo wrote: >> I tried upgrading to wine-2.0.1 and got during configure: >> ------------- >> checking gnutls/gnutls.h usability... yes >> checking gnutls/gnutls.h presence... yes >> checking for gnutls/gnutls.h... yes >> checking for -lgnutls... not found >> checking for gnutls_hash... no >> configure: error: libgnutls 32-bit development files not found, no >> schannel support. >> This is an error since --with-gnutls was requested. >> --------------- >> >> Oddly, I'm running wine-2.0. Trying to rec-ompile wine-2.0 also now >> fails with the same error. wine-2.0 compiled fine on 01-FEB-2017 (the >> package I am currently using). All the updates to Slackware64 14.2 and >> multilib are installed as of 08-MAY-2017. >> >> I'll try later with a clean VM, but does anyone have any ideas? > > have you tried to reinstall gnutls just in case it was overwritten? > yes, first thing. AH....it's not gnutls that is missing but a gnutls dependency: libunistring-compat32-0.9.3-x86_64-1compat32 where did that come from and why was it missing? weird. slackpkg or I missed it. well, let see what happens... -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 ekinakoglu at gmail.com Thu May 11 13:36:55 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Thu, 11 May 2017 16:36:55 +0300 Subject: [Slackbuilds-users] openoffice.org.SlackBuild does not install menu icons Message-ID: <6ceb0d8b-4382-4290-9d9b-e87e846567ee@gmail.com> Dear all and Ryan as being the maintainer of openoffice.org, The openoffice.org.Slackbuild does not install the necessary menu icons to /usr/share/icons. I propose a patch as attached. I also did a little bit of arbitrary clean up in the script (you may disregard them). Please feel free to comment. Kind regards, Ekin -------------- next part -------------- A non-text attachment was scrubbed... Name: openoffice.org.SlackBuild.patch Type: text/x-patch Size: 1278 bytes Desc: not available URL: From ekinakoglu at gmail.com Thu May 11 13:41:33 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Thu, 11 May 2017 16:41:33 +0300 Subject: [Slackbuilds-users] kdiff3-qt In-Reply-To: <088a24ad31926d48fbd18a30dbd45417@palmtx.com.ar> References: <1609981a-5532-f0a0-4c00-5333f17951eb@gmail.com> <201703312032.29137.ricardo@palmtx.com.ar> <84e67600-f5b2-6535-2105-61e42514c569@gmail.com> <9790788a-4249-6d62-a076-6e2a885ba13f@gmail.com> <51967583546960c9a4c643a1910ccb0e@palmtx.com.ar> <088a24ad31926d48fbd18a30dbd45417@palmtx.com.ar> Message-ID: <77487d21-cb67-d059-7b81-b9757fb80ae2@gmail.com> Dear Ricardo and all, I have tested the new script and it seems to succeed in Slackware64 with and without kdelibs. Thanks. Best, Ekin On 09/05/17 06:26, Ricardo J. Barberis wrote: > OK, I think I've got a nice set of files ready to submit. > > I modified Ekin's patch and added translations for the QT4ONLY > version, so any blunder is mine :) > > Anyone cares to try it before I send it? > > Thanks! > > El 08/05/2017 21:14, Ricardo J. Barberis escribi?: >> Hi Ekin and all, >> >> Sorry this took so long, I'm reviewing your patch right now and will >> accomodate it to SBo standards. >> I will also update the other files so I can submit an update in the >> next few hours. >> >> Cheers, >> >> El 08/05/2017 10:46, Ekin Akoglu escribi?: >>> Hi, >>> >>> Is there any plan about the kdiff3 "Qt-only" build patch which I have >>> sent two weeks ago? Will it be incorporated in the current SlackBuild >>> in order to enable a "Qt-only" build of kdiff3 when "qt4" argument is >>> passed to the SlackBuild? >>> >>> Kind regards, >>> >>> Ekin >>> >>> >>> On 25/04/17 21:34, Ekin Akoglu wrote: >>>> Hi Ricardo and all, >>>> >>>> As I promised, attached I send a patch for the kdiff3.Slackbuild to >>>> enable the build option for Qt4 only when "qt4" is passed as an >>>> argument to the SlackBuild script. This enables the installation of >>>> kdiff3 for systems without kdelibs. >>>> >>>> Kind regards, >>>> >>>> Ekin >>>> >>>> >>>> On 11/04/17 11:18, Ekin Akoglu wrote: >>>>> Hi Ricardo, >>>>> >>>>> Thank you for your response. Currently I just modified the script >>>>> so that it compiles directly for only Qt. >>>>> >>>>> I will prepare a proper conditional compilation patch and send it >>>>> to you for your review in short time. >>>>> >>>>> Best, >>>>> >>>>> Ekin >>>>> >>>>> >>>>> On 01/04/17 02:32, Ricardo J. Barberis wrote: >>>>>> Hi Ekin, in 2016/01/24 Michiel gave up several of his slackbuilds >>>>>> and I >>>>>> promised to take kdiff3 and others, but I have been busy at work >>>>>> lately. >>>>>> >>>>>> I'll try to take a look at it this weekend (there's a couple >>>>>> other sb's I have >>>>>> to take care of as well) and see if I can do what you nedd. >>>>>> >>>>>> If you have a patch or something and want to send it, I'll gladly >>>>>> take it :) >>>>>> >>>>>> Cheers, >>>>>> >>>>>> El Viernes 31/03/2017 a las 16:25, Ekin Akoglu escribi?: >>>>>>> This is my second take on the issue. Do you have any suggestions >>>>>>> for a >>>>>>> possible kdiff3-qt SlackBuild? >>>>>>> >>>>>>> Michiel, would you accept a patch for a conditional compilation? >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Ekin >>>>>>> >>>>>>> On 23/03/17 10:10, Ekin Akoglu wrote: >>>>>>>> Dear all, >>>>>>>> >>>>>>>> I prepared a Qt-only SlackBuild of kdiff3 for installing on >>>>>>>> environments without KDE libraries. Shall I submit this as a >>>>>>>> separate >>>>>>>> SlackBuild or Michiel, the maintainer of kdiff3, will you favor a >>>>>>>> patch for conditional compilation to your SlackBuild. What do you >>>>>>>> suggest? >>>>>>>> >>>>>>>> Best, >>>>>>>> >>>>>>>> Ekin > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricardo at palmtx.com.ar Thu May 11 15:07:06 2017 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Thu, 11 May 2017 12:07:06 -0300 Subject: [Slackbuilds-users] kdiff3-qt In-Reply-To: <77487d21-cb67-d059-7b81-b9757fb80ae2@gmail.com> References: <088a24ad31926d48fbd18a30dbd45417@palmtx.com.ar> <77487d21-cb67-d059-7b81-b9757fb80ae2@gmail.com> Message-ID: <201705111207.06446.ricardo@palmtx.com.ar> Thank you for testing! I'll submit the update today. El Jueves 11/05/2017 a las 10:41, Ekin Akoglu escribi?: > Dear Ricardo and all, > > I have tested the new script and it seems to succeed in Slackware64 with > and without kdelibs. > > Thanks. > > Best, > > Ekin > > On 09/05/17 06:26, Ricardo J. Barberis wrote: > > OK, I think I've got a nice set of files ready to submit. > > > > I modified Ekin's patch and added translations for the QT4ONLY > > version, so any blunder is mine :) > > > > Anyone cares to try it before I send it? > > > > Thanks! > > > > El 08/05/2017 21:14, Ricardo J. Barberis escribi?: > >> Hi Ekin and all, > >> > >> Sorry this took so long, I'm reviewing your patch right now and will > >> accomodate it to SBo standards. > >> I will also update the other files so I can submit an update in the > >> next few hours. > >> > >> Cheers, > >> > >> El 08/05/2017 10:46, Ekin Akoglu escribi?: > >>> Hi, > >>> > >>> Is there any plan about the kdiff3 "Qt-only" build patch which I have > >>> sent two weeks ago? Will it be incorporated in the current SlackBuild > >>> in order to enable a "Qt-only" build of kdiff3 when "qt4" argument is > >>> passed to the SlackBuild? > >>> > >>> Kind regards, > >>> > >>> Ekin > >>> > >>> On 25/04/17 21:34, Ekin Akoglu wrote: > >>>> Hi Ricardo and all, > >>>> > >>>> As I promised, attached I send a patch for the kdiff3.Slackbuild to > >>>> enable the build option for Qt4 only when "qt4" is passed as an > >>>> argument to the SlackBuild script. This enables the installation of > >>>> kdiff3 for systems without kdelibs. > >>>> > >>>> Kind regards, > >>>> > >>>> Ekin > >>>> > >>>> On 11/04/17 11:18, Ekin Akoglu wrote: > >>>>> Hi Ricardo, > >>>>> > >>>>> Thank you for your response. Currently I just modified the script > >>>>> so that it compiles directly for only Qt. > >>>>> > >>>>> I will prepare a proper conditional compilation patch and send it > >>>>> to you for your review in short time. > >>>>> > >>>>> Best, > >>>>> > >>>>> Ekin > >>>>> > >>>>> On 01/04/17 02:32, Ricardo J. Barberis wrote: > >>>>>> Hi Ekin, in 2016/01/24 Michiel gave up several of his slackbuilds > >>>>>> and I > >>>>>> promised to take kdiff3 and others, but I have been busy at work > >>>>>> lately. > >>>>>> > >>>>>> I'll try to take a look at it this weekend (there's a couple > >>>>>> other sb's I have > >>>>>> to take care of as well) and see if I can do what you nedd. > >>>>>> > >>>>>> If you have a patch or something and want to send it, I'll gladly > >>>>>> take it :) > >>>>>> > >>>>>> Cheers, > >>>>>> > >>>>>> El Viernes 31/03/2017 a las 16:25, Ekin Akoglu escribi?: > >>>>>>> This is my second take on the issue. Do you have any suggestions > >>>>>>> for a > >>>>>>> possible kdiff3-qt SlackBuild? > >>>>>>> > >>>>>>> Michiel, would you accept a patch for a conditional compilation? > >>>>>>> > >>>>>>> Best, > >>>>>>> > >>>>>>> Ekin > >>>>>>> > >>>>>>> On 23/03/17 10:10, Ekin Akoglu wrote: > >>>>>>>> Dear all, > >>>>>>>> > >>>>>>>> I prepared a Qt-only SlackBuild of kdiff3 for installing on > >>>>>>>> environments without KDE libraries. Shall I submit this as a > >>>>>>>> separate > >>>>>>>> SlackBuild or Michiel, the maintainer of kdiff3, will you favor a > >>>>>>>> patch for conditional compilation to your SlackBuild. What do you > >>>>>>>> suggest? > >>>>>>>> > >>>>>>>> Best, > >>>>>>>> > >>>>>>>> Ekin -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From chris.willing at iinet.net.au Fri May 12 05:15:50 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 12 May 2017 15:15:50 +1000 Subject: [Slackbuilds-users] Tracking version releases Message-ID: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Hi all, I don't have a huge number of SlackBuilds to maintain but enough that its easy to lose track of upstream development and know when new versions have been released. Occasionally I do a find of .info files containing my name in the SBo file tree and go to each of the relevant websites looking for new releases. Sometimes a user sends me email about an update. Some repos can send email notifications, some have RSS feeds etc., but there doesn't seem to be a consistent mechanism for this sort of thing. There has to be a better way, so does anyone already have a better way to keep track before I write something to do it? Well, before waiting for a reply to that question, I already started writing a tool of my own to do that. It's not quite complete but close enough - my 6 SlackBuild updates this week were all due to prompting while developing/testing/documenting the thing. The new tool can currently deal with projects at github, sourceforge, pypi & libreoffice. It's been written to enable new repo modules to be added fairly easily. My real question is whether anyone knows of other repositories that should be included (and preferably have some sort of API available for access), so that modules for them can be added? I guess you should still let me know if this has already been done before I spend too much more time on it. BTW its at: https://github.com/cwilling/pvc Thanks for any tips, comments, chris From jebrhansen+SBo at gmail.com Fri May 12 05:23:42 2017 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 12 May 2017 05:23:42 +0000 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: On Fri, May 12, 2017, 1:16 AM Christoph Willing wrote: > Hi all, > > I don't have a huge number of SlackBuilds to maintain but enough that > its easy to lose track of upstream development and know when new > versions have been released. Occasionally I do a find of .info files > containing my name in the SBo file tree and go to each of the relevant > websites looking for new releases. Sometimes a user sends me email about > an update. Some repos can send email notifications, some have RSS feeds > etc., but there doesn't seem to be a consistent mechanism for this sort > of thing. There has to be a better way, so does anyone already have a > better way to keep track before I write something to do it? > > Well, before waiting for a reply to that question, I already started > writing a tool of my own to do that. It's not quite complete but close > enough - my 6 SlackBuild updates this week were all due to prompting > while developing/testing/documenting the thing. > > The new tool can currently deal with projects at github, sourceforge, > pypi & libreoffice. It's been written to enable new repo modules to be > added fairly easily. My real question is whether anyone knows of other > repositories that should be included (and preferably have some sort of > API available for access), so that modules for them can be added? > I don't have any immediate thoughts on what else to support, but maybe you could set up something like plowshare? does in regards to "modules". You have the main program that has all the binaries, then you have modules for all the various sites that you support. Plowshare has them all as separate files that are stored in a directory (either globally or per user). This could allow others to more easily add new sites. https://github.com/mcrapet/plowshare https://github.com/mcrapet/plowshare-modules-legacy > I guess you should still let me know if this has already been done > before I spend too much more time on it. > > BTW its at: > https://github.com/cwilling/pvc I'll try to find time this weekend to check it out. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Fri May 12 06:13:37 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 12 May 2017 16:13:37 +1000 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: On 12/05/17 15:23, Jeremy Hansen wrote: > I don't have any immediate thoughts on what else to support, but maybe > you could set up something like plowshare? does in regards to "modules". > You have the main program that has all the binaries, then you have > modules for all the various sites that you support. Plowshare has them > all as separate files that are stored in a directory (either globally or > per user). This could allow others to more easily add new sites. > That's almost the way I'm doing it - a single module file per site, each "absorbed" by the core at runtime. Any supplied modules would be global but user supplied modules could be supported by having the core search for more modules in some standard location (like ~/.local/share/pvc or whatever). Good idea! Thanks, chris From willysr at slackbuilds.org Fri May 12 06:20:48 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 12 May 2017 13:20:48 +0700 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: > of thing. There has to be a better way, so does anyone already have a > better way to keep track before I write something to do it? Have you checked repology? https://repology.org/metapackages/outdated-by-maintainer/chris.willing%40linux.com/ it's not up to date due to a typo in one of the script in our repo which has been fixed in my branch. By the time next public update is pushed, it should displayed outdated packages maintained by a you -- 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 Fri May 12 07:17:35 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 12 May 2017 17:17:35 +1000 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: On 12/05/17 16:20, Willy Sudiarto Raharjo wrote: >> of thing. There has to be a better way, so does anyone already have a >> better way to keep track before I write something to do it? > > Have you checked repology? > https://repology.org/metapackages/outdated-by-maintainer/chris.willing%40linux.com/ > > it's not up to date due to a typo in one of the script in our repo which > has been fixed in my branch. By the time next public update is pushed, > it should displayed outdated packages maintained by a you > No I hadn't seen that. It looks pretty good - despite a few odd little things e.g. live555 versioning string incorrectly makes it think a version from 2014 is the latest. Hmmm what to do? chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Fri May 12 07:55:48 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Fri, 12 May 2017 08:55:48 +0100 Subject: [Slackbuilds-users] Error when compiling clamav 0.99.2 against -current Message-ID: I get the following error when attempting to build clamav 0.99.2 against -current using the SBo scripts. Has anybody else seen this, or have any idea what it might mean? Searching online turns up some Fedore posts from a year ago, and it that case the llvm libraries on their system were too old. But Slackware current uses llvm-4.0.0 - which seems to be the latest. /llvm/include/llvm/Support/AlignOf.h: At global scope: ./llvm/include/llvm/Support/AlignOf.h:57:24: error: expected unqualified-id before ?alignof? static inline unsigned alignof() { return AlignOf::Alignment; } ^~~~~~~ In file included from ./llvm/include/llvm/ADT/StringMap.h:18:0, from bytecode2llvm.cpp:41: ./llvm/include/llvm/Support/Allocator.h: In member function ?void llvm::SpecificBumpPtrAllocator::DestroyAll()?: ./llvm/include/llvm/Support/Allocator.h:204:46: error: expected primary-expression before ?()); ^ ./llvm/include/llvm/Support/Allocator.h:204:39: warning: ISO C++ does not allow ?alignof? with a non-type [-Wpedantic] Ptr = Allocator.AlignPtr(Ptr, alignof()); ^~~~~~~ ./llvm/include/llvm/Support/Allocator.h:204:48: error: expected primary-expression before ?>? token Ptr = Allocator.AlignPtr(Ptr, alignof()); ^ ./llvm/include/llvm/Support/Allocator.h:204:50: error: expected primary-expression before ?)? token Ptr = Allocator.AlignPtr(Ptr, alignof()); ^ In file included from bytecode2llvm.cpp:41:0: ./llvm/include/llvm/ADT/StringMap.h: In static member function ?static llvm::StringMapEntry* llvm::StringMapEntry::Create(const char*, const char*, AllocatorTy&, InitType)?: ./llvm/include/llvm/ADT/StringMap.h:170:33: error: expected primary-expression before ?(); ^ ./llvm/include/llvm/ADT/StringMap.h:170:26: warning: ISO C++ does not allow ?alignof? with a non-type [-Wpedantic] unsigned Alignment = alignof(); ^~~~~~~ ./llvm/include/llvm/ADT/StringMap.h:170:48: error: expected primary-expression before ?>? token unsigned Alignment = alignof(); ^ ./llvm/include/llvm/ADT/StringMap.h:170:50: error: expected primary-expression before ?)? token unsigned Alignment = alignof(); ^ In file included from bytecode2llvm.cpp:69:0: ./llvm/include/llvm/Support/CommandLine.h: In member function ?void llvm::cl::alias::done()?: ./llvm/include/llvm/Support/CommandLine.h:1326:5: warning: this ?if? clause does not guard... [-Wmisleading-indentation] if (AliasFor == 0) ^~ ./llvm/include/llvm/Support/CommandLine.h:1328:7: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the ?if? addArgument(); ^~~~~~~~~~~ bytecode2llvm.cpp: In function ?void setGuard(unsigned char*)?: bytecode2llvm.cpp:2432:49: warning: ISO C++ forbids converting a string constant to ?char*? [-Wwrite-strings] cl_hash_data("md5", salt, 48, guardbuf, NULL); ^ make[5]: *** [Makefile:2153: libclamavcxx_la-bytecode2llvm.lo] Error 1 make[5]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav/c++' make[4]: *** [Makefile:1544: all] Error 2 make[4]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav/c++' make[3]: *** [Makefile:3459: all-recursive] Error 1 make[3]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav' make[2]: *** [Makefile:1162: all] Error 2 make[2]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav' make[1]: *** [Makefile:747: all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/clamav-0.99.2' make: *** [Makefile:576: all] Error 2 From matteo.bernardini at gmail.com Fri May 12 07:59:00 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 12 May 2017 09:59:00 +0200 Subject: [Slackbuilds-users] Error when compiling clamav 0.99.2 against -current In-Reply-To: References: Message-ID: 2017-05-12 9:55 GMT+02:00 Sebastian Arcus : > I get the following error when attempting to build clamav 0.99.2 against > -current using the SBo scripts. Has anybody else seen this, or have any idea > what it might mean? Searching online turns up some Fedore posts from a year > ago, and it that case the llvm libraries on their system were too old. But > Slackware current uses llvm-4.0.0 - which seems to be the latest. > > > > /llvm/include/llvm/Support/AlignOf.h: At global scope: > ./llvm/include/llvm/Support/AlignOf.h:57:24: error: expected unqualified-id > before ?alignof? > static inline unsigned alignof() { return AlignOf::Alignment; } > ^~~~~~~ > In file included from ./llvm/include/llvm/ADT/StringMap.h:18:0, > from bytecode2llvm.cpp:41: > ./llvm/include/llvm/Support/Allocator.h: In member function ?void > llvm::SpecificBumpPtrAllocator::DestroyAll()?: > ./llvm/include/llvm/Support/Allocator.h:204:46: error: expected > primary-expression before ? Ptr = Allocator.AlignPtr(Ptr, alignof()); > ^ > ./llvm/include/llvm/Support/Allocator.h:204:39: warning: ISO C++ does not > allow ?alignof? with a non-type [-Wpedantic] > Ptr = Allocator.AlignPtr(Ptr, alignof()); > ^~~~~~~ > ./llvm/include/llvm/Support/Allocator.h:204:48: error: expected > primary-expression before ?>? token > Ptr = Allocator.AlignPtr(Ptr, alignof()); > ^ > ./llvm/include/llvm/Support/Allocator.h:204:50: error: expected > primary-expression before ?)? token > Ptr = Allocator.AlignPtr(Ptr, alignof()); > ^ > In file included from bytecode2llvm.cpp:41:0: > ./llvm/include/llvm/ADT/StringMap.h: In static member function ?static > llvm::StringMapEntry* llvm::StringMapEntry::Create(const > char*, const char*, AllocatorTy&, InitType)?: > ./llvm/include/llvm/ADT/StringMap.h:170:33: error: expected > primary-expression before ? unsigned Alignment = alignof(); > ^ > ./llvm/include/llvm/ADT/StringMap.h:170:26: warning: ISO C++ does not allow > ?alignof? with a non-type [-Wpedantic] > unsigned Alignment = alignof(); > ^~~~~~~ > ./llvm/include/llvm/ADT/StringMap.h:170:48: error: expected > primary-expression before ?>? token > unsigned Alignment = alignof(); > ^ > ./llvm/include/llvm/ADT/StringMap.h:170:50: error: expected > primary-expression before ?)? token > unsigned Alignment = alignof(); > ^ > In file included from bytecode2llvm.cpp:69:0: > ./llvm/include/llvm/Support/CommandLine.h: In member function ?void > llvm::cl::alias::done()?: > ./llvm/include/llvm/Support/CommandLine.h:1326:5: warning: this ?if? clause > does not guard... [-Wmisleading-indentation] > if (AliasFor == 0) > ^~ > ./llvm/include/llvm/Support/CommandLine.h:1328:7: note: ...this statement, > but the latter is misleadingly indented as if it were guarded by the ?if? > addArgument(); > ^~~~~~~~~~~ > bytecode2llvm.cpp: In function ?void setGuard(unsigned char*)?: > bytecode2llvm.cpp:2432:49: warning: ISO C++ forbids converting a string > constant to ?char*? [-Wwrite-strings] > cl_hash_data("md5", salt, 48, guardbuf, NULL); > ^ > make[5]: *** [Makefile:2153: libclamavcxx_la-bytecode2llvm.lo] Error 1 > make[5]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav/c++' > make[4]: *** [Makefile:1544: all] Error 2 > make[4]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav/c++' > make[3]: *** [Makefile:3459: all-recursive] Error 1 > make[3]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav' > make[2]: *** [Makefile:1162: all] Error 2 > make[2]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav' > make[1]: *** [Makefile:747: all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/clamav-0.99.2' > make: *** [Makefile:576: all] Error 2 http://cgit.ponce.cc/slackbuilds/commit/?h=clamav From slackbuilds at schoepfer.info Fri May 12 08:59:57 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 12 May 2017 10:59:57 +0200 Subject: [Slackbuilds-users] Error when compiling clamav 0.99.2 against -current In-Reply-To: References: Message-ID: <1ed31f1e-14cb-de2b-f1a2-66ad606598fc@schoepfer.info> > http://cgit.ponce.cc/slackbuilds/commit/?h=clamav BTW, and not meant specially for -current, if using the milter, /usr/sbin/clamav-milter has to be startet without any options in rc.clamav. Any config has to reside in /etc/clamav-milter.conf It seems this wasn't the case in previous releases. Johannes From willysr at slackbuilds.org Fri May 12 09:05:11 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 12 May 2017 16:05:11 +0700 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: <3caaf5d6-2576-1093-5e44-837c098550a4@slackbuilds.org> > No I hadn't seen that. It looks pretty good - despite a few odd little > things e.g. live555 versioning string incorrectly makes it think a > version from 2014 is the latest. > > Hmmm what to do? There's nothing we can do except that we had to check for upstream. Different distribution have different naming rules. -- 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 Fri May 12 10:19:27 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 12 May 2017 20:19:27 +1000 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: <3caaf5d6-2576-1093-5e44-837c098550a4@slackbuilds.org> References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> <3caaf5d6-2576-1093-5e44-837c098550a4@slackbuilds.org> Message-ID: On 12/05/17 19:05, Willy Sudiarto Raharjo wrote: >> No I hadn't seen that. It looks pretty good - despite a few odd little >> things e.g. live555 versioning string incorrectly makes it think a >> version from 2014 is the latest. >> >> Hmmm what to do? > > There's nothing we can do except that we had to check for upstream. > Different distribution have different naming rules. > Actually I was wondering what to do about continuing my own little project since the repology site is so good apart from minor inconsistencies (like live555 reports). As for live555 naming conventions, all the distros mentioned at repology as packaging live555 (https://repology.org/metapackage/live555/versions) use the same convention that we and upstream use for live555. Only one distro (ALT Sisyphus) uses the convention that repology seems to favour. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From slackalaxy at gmail.com Fri May 12 10:46:39 2017 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 12 May 2017 13:46:39 +0300 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: that seems useful! The way I keep track on my updates is a bit more manual. I have a list of what I maintain in my humble blog: https://slackalaxy.com/slackbuilds/ Every couple of months or so, when I know that I have a (relatively) free weekend ahead of me, I go through the entries, visiting each web-site and checking if a new version is available. Your tool sounds really interesting, and will likely save me some hassle. Thank you. -petar 2017-05-12 8:15 GMT+03:00 Christoph Willing : > Hi all, > > I don't have a huge number of SlackBuilds to maintain but enough that > its easy to lose track of upstream development and know when new > versions have been released. Occasionally I do a find of .info files > containing my name in the SBo file tree and go to each of the relevant > websites looking for new releases. Sometimes a user sends me email about > an update. Some repos can send email notifications, some have RSS feeds > etc., but there doesn't seem to be a consistent mechanism for this sort > of thing. There has to be a better way, so does anyone already have a > better way to keep track before I write something to do it? > > Well, before waiting for a reply to that question, I already started > writing a tool of my own to do that. It's not quite complete but close > enough - my 6 SlackBuild updates this week were all due to prompting > while developing/testing/documenting the thing. > > The new tool can currently deal with projects at github, sourceforge, > pypi & libreoffice. It's been written to enable new repo modules to be > added fairly easily. My real question is whether anyone knows of other > repositories that should be included (and preferably have some sort of > API available for access), so that modules for them can be added? > > I guess you should still let me know if this has already been done > before I spend too much more time on it. > > BTW its at: > https://github.com/cwilling/pvc > > Thanks for any tips, comments, > chris > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From dickson.tim at googlemail.com Fri May 12 15:14:05 2017 From: dickson.tim at googlemail.com (Tim Dickson) Date: Fri, 12 May 2017 16:14:05 +0100 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: I have my own script to keep track of projects I maintain sbuilds for (or other stuff). It consists of a config file containing name,version,updated flag,browser,url for each project and the main script has a big case statement, where I add one-liner subscripts for each project's web page to detect the version number. eg. 'libpaper') NEWVER=`cat $TMPDLFILE|grep "title=\"stable\""|head -n1|awk -F">" '{print $2}'|awk -F"<" '{print $1}'` ;; extracts the version from libpaper's project page (which has been downloaded to $TMPDLFILE ) I extract the results generating an html report which shows on my desktop to notify me when a project has been updated (or my detection no longer seems to work). having said that, repology.org is really useful as you can search by "maintainter", and list all the projects which it thinks are out of date. regards, Tim On 12/05/2017 06:15, Christoph Willing wrote: > Hi all, > > I don't have a huge number of SlackBuilds to maintain but enough that > its easy to lose track of upstream development and know when new > versions have been released. Occasionally I do a find of .info files > containing my name in the SBo file tree and go to each of the relevant > websites looking for new releases. Sometimes a user sends me email about > an update. Some repos can send email notifications, some have RSS feeds > etc., but there doesn't seem to be a consistent mechanism for this sort > of thing. There has to be a better way, so does anyone already have a > better way to keep track before I write something to do it? > > Well, before waiting for a reply to that question, I already started > writing a tool of my own to do that. It's not quite complete but close > enough - my 6 SlackBuild updates this week were all due to prompting > while developing/testing/documenting the thing. > > The new tool can currently deal with projects at github, sourceforge, > pypi & libreoffice. It's been written to enable new repo modules to be > added fairly easily. My real question is whether anyone knows of other > repositories that should be included (and preferably have some sort of > API available for access), so that modules for them can be added? > > I guess you should still let me know if this has already been done > before I spend too much more time on it. > > BTW its at: > https://github.com/cwilling/pvc > > Thanks for any tips, comments, > chris > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > . > From s.arcus at open-t.co.uk Fri May 12 15:20:51 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Fri, 12 May 2017 16:20:51 +0100 Subject: [Slackbuilds-users] Error when compiling clamav 0.99.2 against -current In-Reply-To: References: Message-ID: <92ac8005-1a68-1e84-95c7-20e6aa58e11a@open-t.co.uk> On 12/05/17 08:59, Matteo Bernardini wrote: > 2017-05-12 9:55 GMT+02:00 Sebastian Arcus : >> I get the following error when attempting to build clamav 0.99.2 against >> -current using the SBo scripts. Has anybody else seen this, or have any idea >> what it might mean? Searching online turns up some Fedore posts from a year >> ago, and it that case the llvm libraries on their system were too old. But >> Slackware current uses llvm-4.0.0 - which seems to be the latest. >> >> >> >> /llvm/include/llvm/Support/AlignOf.h: At global scope: >> ./llvm/include/llvm/Support/AlignOf.h:57:24: error: expected unqualified-id >> before ?alignof? >> static inline unsigned alignof() { return AlignOf::Alignment; } >> ^~~~~~~ >> In file included from ./llvm/include/llvm/ADT/StringMap.h:18:0, >> from bytecode2llvm.cpp:41: >> ./llvm/include/llvm/Support/Allocator.h: In member function ?void >> llvm::SpecificBumpPtrAllocator::DestroyAll()?: >> ./llvm/include/llvm/Support/Allocator.h:204:46: error: expected >> primary-expression before ?> Ptr = Allocator.AlignPtr(Ptr, alignof()); >> ^ >> ./llvm/include/llvm/Support/Allocator.h:204:39: warning: ISO C++ does not >> allow ?alignof? with a non-type [-Wpedantic] >> Ptr = Allocator.AlignPtr(Ptr, alignof()); >> ^~~~~~~ >> ./llvm/include/llvm/Support/Allocator.h:204:48: error: expected >> primary-expression before ?>? token >> Ptr = Allocator.AlignPtr(Ptr, alignof()); >> ^ >> ./llvm/include/llvm/Support/Allocator.h:204:50: error: expected >> primary-expression before ?)? token >> Ptr = Allocator.AlignPtr(Ptr, alignof()); >> ^ >> In file included from bytecode2llvm.cpp:41:0: >> ./llvm/include/llvm/ADT/StringMap.h: In static member function ?static >> llvm::StringMapEntry* llvm::StringMapEntry::Create(const >> char*, const char*, AllocatorTy&, InitType)?: >> ./llvm/include/llvm/ADT/StringMap.h:170:33: error: expected >> primary-expression before ?> unsigned Alignment = alignof(); >> ^ >> ./llvm/include/llvm/ADT/StringMap.h:170:26: warning: ISO C++ does not allow >> ?alignof? with a non-type [-Wpedantic] >> unsigned Alignment = alignof(); >> ^~~~~~~ >> ./llvm/include/llvm/ADT/StringMap.h:170:48: error: expected >> primary-expression before ?>? token >> unsigned Alignment = alignof(); >> ^ >> ./llvm/include/llvm/ADT/StringMap.h:170:50: error: expected >> primary-expression before ?)? token >> unsigned Alignment = alignof(); >> ^ >> In file included from bytecode2llvm.cpp:69:0: >> ./llvm/include/llvm/Support/CommandLine.h: In member function ?void >> llvm::cl::alias::done()?: >> ./llvm/include/llvm/Support/CommandLine.h:1326:5: warning: this ?if? clause >> does not guard... [-Wmisleading-indentation] >> if (AliasFor == 0) >> ^~ >> ./llvm/include/llvm/Support/CommandLine.h:1328:7: note: ...this statement, >> but the latter is misleadingly indented as if it were guarded by the ?if? >> addArgument(); >> ^~~~~~~~~~~ >> bytecode2llvm.cpp: In function ?void setGuard(unsigned char*)?: >> bytecode2llvm.cpp:2432:49: warning: ISO C++ forbids converting a string >> constant to ?char*? [-Wwrite-strings] >> cl_hash_data("md5", salt, 48, guardbuf, NULL); >> ^ >> make[5]: *** [Makefile:2153: libclamavcxx_la-bytecode2llvm.lo] Error 1 >> make[5]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav/c++' >> make[4]: *** [Makefile:1544: all] Error 2 >> make[4]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav/c++' >> make[3]: *** [Makefile:3459: all-recursive] Error 1 >> make[3]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav' >> make[2]: *** [Makefile:1162: all] Error 2 >> make[2]: Leaving directory '/tmp/SBo/clamav-0.99.2/libclamav' >> make[1]: *** [Makefile:747: all-recursive] Error 1 >> make[1]: Leaving directory '/tmp/SBo/clamav-0.99.2' >> make: *** [Makefile:576: all] Error 2 > > http://cgit.ponce.cc/slackbuilds/commit/?h=clamav Thank you for pointing me in the right direction. I really have to figure out how to check the newest git commits for SBo when something doesn't work. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sat May 13 00:46:42 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 13 May 2017 07:46:42 +0700 Subject: [Slackbuilds-users] Updates - 20170513.1 Message-ID: Hi folks This time, we got LibreOffice and libreoffice updates at the same time. We also had several important updates which includes security fixes, such as flashplayer_plugins, pepperflash-plugins, and webmin. PaleMoon is now able to support multiple compilers, but unfortunately we can't ship gcclegacy494 for now as it still clashes with Slackware's GCC package. We are looking forward to see this issue fixed by next public update. IMPORTANT NOTE: Submission is now (temporarily) closed while we are migrating to the new server (Thanks to all contributors who have donated to this project). Erik, Robby, Heinz, and Ponce are doing the migration during this week and hopefully it will be ready soon. We will publish an announcement when it's completed. Sat May 13 00:01:17 UTC 2017 academic/fet: Updated for version 5.31.6. academic/sage: Update README. academic/veusz: Updated for version 1.26. academic/xiphos: Updated for version 4.0.5. audio/gmpc-plugins: Update HOMEPAGE url. audio/gmpc: Update HOMEPAGE url. audio/irispdb: Update HOMEPAGE url. audio/jost_bin: Removed (upstream is gone). audio/llcon: Update HOMEPAGE url. audio/morituri: Update HOMEPAGE url. audio/mt-daapd: Update HOMEPAGE url. audio/paprefs: Update maintainer email audio/snd: Updated for version 17.4. audio/whipper: Updated for version 0.5.1. desktop/dark-aurora-gtk-theme: Updated for version 3.20.2. desktop/obapps: Update HOMEPAGE url. desktop/plasma-applet-daisy: Update HOMEPAGE url. desktop/tint2: Updated for version 0.14.4. desktop/xed: Updated for version 1.4.1. development/Cython-Kivy: Removed (per maintainer's request). development/kdiff3: Updated for version 0.9.98 + new maintainer. development/neovim: Updated for version 0.2.0. development/nodejs: Updated for version 6.10.3. development/pandas: Updated for version 0.20.1. development/pycharm: Updated for version 2017.1.2. development/tig: Updated for version 2.2.2. games/cpat: Update HOMEPAGE url. games/ds-models: Update HOMEPAGE url. games/fortune-ASR: Update HOMEPAGE url. games/freeorion: Updated for version 0.4.7. games/glestae: Update HOMEPAGE url. gis/GMT: Updated for version 5.4.1. gis/gdal: Updated for version 2.2.0. gis/grass: Updated for version 7.2.1. graphics/opencollada: Update maintainer email graphics/opencolorio: Update maintainer email graphics/ttyload: Added (A color-coded console load graph). graphics/tuxpaint-stamps: Update email. graphics/tuxpaint: Update email. ham/direwolf: Update HOMEPAGE url. libraries/Kivy: Updated for version 1.10.0. libraries/VTK: Updated for version 7.1.1 libraries/botocore: Updated for version 1.5.48. libraries/dropbox-python: Updated for version 7.3.0. libraries/folly: Updated for version 2017.05.08.00. libraries/gconfmm: Update maintainer email libraries/glog: Updated for version 0.3.5. libraries/gstreamer-editing-services: Update HOMEPAGE url. libraries/libburn: Update HOMEPAGE url. libraries/libetpan: Updated for version 1.8. libraries/libinput: Updated for version 1.7.2. libraries/libisoburn: Update HOMEPAGE url. libraries/libisofs: Update HOMEPAGE url. libraries/liblogging: Updated for version 1.0.6. libraries/libopenshot-audio: Updated for version 0.1.4 libraries/libopenshot: Updated for version 0.1.5 libraries/libpaper: Switch to https. libraries/librelp: Updated for version 1.2.13. libraries/librra: Update HOMEPAGE url. libraries/libslack: Update maintainer email libraries/libxkbcommon: Updated for version 0.7.1. libraries/pgplot: Added (graphics subroutine library). libraries/proxygen: Updated for version 2017.05.08.00. libraries/vte3-ng: Added (enhanced vte terminal widget). libraries/wangle: Updated for version 2017.05.08.00. libraries/wcslib: Added (World Coordinate System for FITS). libraries/webkit2gtk: Updated for version 2.16.2. misc/KeePass: Updated for version 2.35. multimedia/flashplayer-plugin: Updated for version 25.0.0.171. multimedia/openshot: Updated for version 2.3.2 multimedia/opera-ffmpeg-codecs: Updated for version 58.0.3029.81. multimedia/pepperflash-plugin: Updated for version 25.0.0.171. multimedia/spotify: Updated for version 1.0.53. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 58.0. multimedia/zvbi: Fix maintainer email network/ClusterSSH: Update HOMEPAGE url. network/PaleMoon: Support different compilers. network/awscli: Updated for version 1.11.85. network/broadcom-sta: Support Linux kernel 4.9+. network/c-toxcore: Updated for version 0.1.8. network/claws-mail: Updated for version 3.15.0. network/filezilla: Update HOMEPAGE url. network/flexget: Updated for version 2.10.43. network/googler: Added (Google from the terminal). network/hydra: Remove HOMEPAGE in README. network/kivy-garden: Added (Garden tool for kivy flowers). network/nikto: Remove old patch. network/opera: Updated for version 45.0.2552.635. network/pure-ftpd: Updated for version 1.0.46. network/qTox: Updated for version 1.10.0. network/slimjet: Updated for version 14.0.6.0. network/smb4k: Updated for version 1.2.3. network/syncthing: Updated for version 0.14.27. network/vivaldi: Updated for version 1.9.818.44. network/x11vnc: Updated for version 0.9.14 network/youtube-dl: Updated for version 2017.05.07. network/znc: Updated for version 1.6.5. office/LibreOffice: Updated for version 5.3.3.2 office/calibre: Updated for version 2.84.0 office/kbbi-qt: Added (Indonesian Language Dictionary). office/keepassx: Update HOMEPAGE url. office/libreoffice-helppack: Updated for version 5.3.3. office/libreoffice-langpack: Updated for version 5.3.3. office/libreoffice: Updated for version 5.3.3. office/openoffice-langpack: Added (Language pack). office/pdfstudio11: Updated for version 11.0.7. office/texworks: Updated for version 0.6.2. perl/perl-CPAN-Perl-Releases: Updated for version 3.16. perl/perl-Gtk2-CodeGen: Removed (same code as of perl-gtk2). perl/perl-Gtk2-Notify: Updated for version 0.05. perl/perl-Inline-C: Updated for version 0.77. perl/perl-Locale-Maketext-Lexicon: Update HOMEPAGE url. perl/perl-Sidef: Updated for version 3.01. python/PyGreSQL: Updated for version 5.0.3 python/colored: Updated for version 1.3.5. python/coverage: Updated for version 4.4. python/invoke: Updated for version 0.17.0. python/monty: Updated for version 0.9.8. python/purl: Updated for version 1.3.1. python/pytest-cov: Updated for version 2.5.0. python/pytest-runner: Added (invoke py.test as a distutils command). python/python-lazy-object-proxy: Updated for version 1.3.1. python/python-m2r: Added (Markdown to reStructuredText converter). python/python-netaddr: Updated for version 0.7.19 python/regex: Updated for version 2017.04.29. python/vcversioner: Added (use vc tags to discover version numbers). ruby/rubygem-gosu: Fix typo. system/afdko: Added (Adobe Font Development Kit for OpenType). system/docker-machine: Added (machine management). system/file-roller: Updated for version 3.24.1 + new maintainer. system/fr: Updated for version 1.35. system/hashcat: Updated for version 3.5.0. system/isdct: Updated for version 3.0.4. system/letsencrypt: Updated for version 0.14.0. system/lynis: Updated for version 2.5.0. system/mlterm: Update doc installation. system/motion: Updated for version 4.0.1. system/rsyslog: Updated for version 8.26.0. system/samsung-mfp-drivers: Added README.pdfprinterrors system/sboui: Updated for version 0.3.1. system/termite: Added (a keyboard-centric VTE-based terminal). system/the_silver_searcher: Updated for version 1.0.3. system/usermin: Updated for version 1.710. system/webmin: Updated for version 1.840. system/wine-staging: Updated for version 2.7. system/wine: Updated for version 2.0.1. system/xen: XSA 213 and 214 update. system/zstd: Updated for version 1.2.0. +--------------------------+ -- 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 Sat May 13 02:01:44 2017 From: elyk03 at gmail.com (Kyle Guinn) Date: Fri, 12 May 2017 21:01:44 -0500 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> <3caaf5d6-2576-1093-5e44-837c098550a4@slackbuilds.org> Message-ID: On 5/12/17, Christoph Willing wrote: > On 12/05/17 19:05, Willy Sudiarto Raharjo wrote: >>> No I hadn't seen that. It looks pretty good - despite a few odd little >>> things e.g. live555 versioning string incorrectly makes it think a >>> version from 2014 is the latest. >>> >>> Hmmm what to do? >> >> There's nothing we can do except that we had to check for upstream. >> Different distribution have different naming rules. >> > > Actually I was wondering what to do about continuing my own little > project since the repology site is so good apart from minor > inconsistencies (like live555 reports). > > As for live555 naming conventions, all the distros mentioned at repology > as packaging live555 (https://repology.org/metapackage/live555/versions) > use the same convention that we and upstream use for live555. Only one > distro (ALT Sisyphus) uses the convention that repology seems to favour. Click the "Report" button on that page and explain the problem. Dmitry is pretty responsive about fixing versioning and package naming inconsistencies. From chris.willing at iinet.net.au Sat May 13 02:25:16 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 13 May 2017 12:25:16 +1000 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> <3caaf5d6-2576-1093-5e44-837c098550a4@slackbuilds.org> Message-ID: <4d3c563a-9965-49e8-53db-776e924ecce5@iinet.net.au> On 13/05/17 12:01, Kyle Guinn wrote: > On 5/12/17, Christoph Willing wrote: >> On 12/05/17 19:05, Willy Sudiarto Raharjo wrote: >>>> No I hadn't seen that. It looks pretty good - despite a few odd little >>>> things e.g. live555 versioning string incorrectly makes it think a >>>> version from 2014 is the latest. >>>> >>>> Hmmm what to do? >>> >>> There's nothing we can do except that we had to check for upstream. >>> Different distribution have different naming rules. >>> >> >> Actually I was wondering what to do about continuing my own little >> project since the repology site is so good apart from minor >> inconsistencies (like live555 reports). >> >> As for live555 naming conventions, all the distros mentioned at repology >> as packaging live555 (https://repology.org/metapackage/live555/versions) >> use the same convention that we and upstream use for live555. Only one >> distro (ALT Sisyphus) uses the convention that repology seems to favour. > > Click the "Report" button on that page and explain the problem. > Dmitry is pretty responsive about fixing versioning and package naming > inconsistencies. > Thanks, I've done that now. chris From dave at dawoodfall.net Sat May 13 14:32:14 2017 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 13 May 2017 15:32:14 +0100 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: References: Message-ID: <20170513143214.GT29231@Blackswan> >On 05/08/2017 09:54 PM, Willy Sudiarto Raharjo wrote: >>> I tried upgrading to wine-2.0.1 and got during configure: >>> ------------- >>> checking gnutls/gnutls.h usability... yes >>> checking gnutls/gnutls.h presence... yes >>> checking for gnutls/gnutls.h... yes >>> checking for -lgnutls... not found >>> checking for gnutls_hash... no >>> configure: error: libgnutls 32-bit development files not found, no >>> schannel support. >>> This is an error since --with-gnutls was requested. >>> --------------- >>> >>> Oddly, I'm running wine-2.0. Trying to rec-ompile wine-2.0 also now >>> fails with the same error. wine-2.0 compiled fine on 01-FEB-2017 (the >>> package I am currently using). All the updates to Slackware64 14.2 and >>> multilib are installed as of 08-MAY-2017. >>> >>> I'll try later with a clean VM, but does anyone have any ideas? >> >> have you tried to reinstall gnutls just in case it was overwritten? >> > >yes, first thing. AH....it's not gnutls that is missing but a gnutls >dependency: > >libunistring-compat32-0.9.3-x86_64-1compat32 > >where did that come from and why was it missing? weird. slackpkg or I >missed it. > >well, let see what happens... > >-Ed Hi. Did you sort this out? -Dave From dpross1100 at msn.com Sat May 13 15:53:38 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 13 May 2017 15:53:38 +0000 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: <20170513143214.GT29231@Blackswan> Message-ID: I had the same issue here. Since I don't think I need gnutls support in wine, I just edited the SlackBuild to set --with-gnutls=no. (I didn't have time to dig why further than that.) After that, the build went fine. I haven't tested it yet, but that might be an option if you know you don't need gnutls support. On May 13, 2017 10:32 AM, David Woodfall wrote: >On 05/08/2017 09:54 PM, Willy Sudiarto Raharjo wrote: >>> I tried upgrading to wine-2.0.1 and got during configure: >>> ------------- >>> checking gnutls/gnutls.h usability... yes >>> checking gnutls/gnutls.h presence... yes >>> checking for gnutls/gnutls.h... yes >>> checking for -lgnutls... not found >>> checking for gnutls_hash... no >>> configure: error: libgnutls 32-bit development files not found, no >>> schannel support. >>> This is an error since --with-gnutls was requested. >>> --------------- >>> >>> Oddly, I'm running wine-2.0. Trying to rec-ompile wine-2.0 also now >>> fails with the same error. wine-2.0 compiled fine on 01-FEB-2017 (the >>> package I am currently using). All the updates to Slackware64 14.2 and >>> multilib are installed as of 08-MAY-2017. >>> >>> I'll try later with a clean VM, but does anyone have any ideas? >> >> have you tried to reinstall gnutls just in case it was overwritten? >> > >yes, first thing. AH....it's not gnutls that is missing but a gnutls >dependency: > >libunistring-compat32-0.9.3-x86_64-1compat32 > >where did that come from and why was it missing? weird. slackpkg or I >missed it. > >well, let see what happens... > >-Ed Hi. Did you sort this out? -Dave _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From brent at exitstatusone.com Sat May 13 17:18:31 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Sat, 13 May 2017 11:18:31 -0600 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: References: <20170513143214.GT29231@Blackswan> Message-ID: <20170513171831.GA25500@gmail.com> On Sat, May 13, 2017 at 03:53:38PM +0000, Daniel Prosser wrote: > I had the same issue here. Since I don't think I need gnutls support in > wine, I just edited the SlackBuild to set --with-gnutls=no. (I didn't > have time to dig why further than that.) After that, the build went > fine. I haven't tested it yet, but that might be an option if you know > you don't need gnutls support. > On May 13, 2017 10:32 AM, David Woodfall wrote: > Try reinstalling gnutls from alien's repo. If that doesnt work, rebuild the compat32 gnutls package. There was a change to gnutls back on Jan 21, 2017. I distinctly remember having to rebuild it to get a game to run. I cannot remember the details at this point since it was a while back and I didn't take any notes. Maybe my solution is wrong but its worth a shot. Let us know how it goes. -Brent From kingbeowulf at gmail.com Sat May 13 17:32:27 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 13 May 2017 10:32:27 -0700 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: <20170513143214.GT29231@Blackswan> References: <20170513143214.GT29231@Blackswan> Message-ID: On 05/13/2017 07:32 AM, David Woodfall wrote: >> On 05/08/2017 09:54 PM, Willy Sudiarto Raharjo wrote: >>>> I tried upgrading to wine-2.0.1 and got during configure: >>>> ------------- >>>> checking gnutls/gnutls.h usability... yes >>>> checking gnutls/gnutls.h presence... yes >>>> checking for gnutls/gnutls.h... yes >>>> checking for -lgnutls... not found >>>> checking for gnutls_hash... no >>>> configure: error: libgnutls 32-bit development files not found, no >>>> schannel support. >>>> This is an error since --with-gnutls was requested. >>>> --------------- >>>> >>>> Oddly, I'm running wine-2.0. Trying to rec-ompile wine-2.0 also now >>>> fails with the same error. wine-2.0 compiled fine on 01-FEB-2017 (the >>>> package I am currently using). All the updates to Slackware64 14.2 and >>>> multilib are installed as of 08-MAY-2017. >>>> >>>> I'll try later with a clean VM, but does anyone have any ideas? >>> >>> have you tried to reinstall gnutls just in case it was overwritten? >>> >> >> yes, first thing. AH....it's not gnutls that is missing but a gnutls >> dependency: >> >> libunistring-compat32-0.9.3-x86_64-1compat32 >> >> where did that come from and why was it missing? weird. slackpkg or I >> missed it. >> >> well, let see what happens... >> >> -Ed > > Hi. Did you sort this out? > > -Dave Yes, it turns out I was missing libunistring-compat32 which it seems gnutls-compat32 now needs for wine to compile after digging through the configure logs. slackpkg+ showed that libunistring-compat32 was available but not installed from my mirror of Alienbob's multilib tree. I am not sure which version of gnutls I used in my initial compile on 01-FEB-2017 (there was a gnutls patch posted on 12-JAN-2017), and libunistring seems to have been added to compat32 on 01-MAR-2017. Again, this glitch only effected slack64 multilib, which SBo does not support ;-) and slack32 was fine. I tested compiles of both wine-2.0.1 and wine-2.7 (staging) after installing libunistring-compat32 and all is good. I an running wine-2.7 now. -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 May 13 17:38:19 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 13 May 2017 10:38:19 -0700 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: References: Message-ID: On 05/13/2017 08:53 AM, Daniel Prosser wrote: > I had the same issue here. Since I don't think I need gnutls support in > wine, I just edited the SlackBuild to set --with-gnutls=no. (I didn't > have time to dig why further than that.) After that, the build went > fine. I haven't tested it yet, but that might be an option if you know > you don't need gnutls support. > Daniel, You need the following to compile wine, depending if you have Slackware32 or Slackware64 multilib: gnutls-compat32-3.5.8-x86_64-1_slack14.2compat32 gnutls-3.5.8-x86_64-1_slack14.2 libunistring-compat32-0.9.3-x86_64-1compat32 libunistring-0.9.3-x86_64-1 -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 May 13 17:53:11 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 13 May 2017 10:53:11 -0700 Subject: [Slackbuilds-users] nividia driver, kernel download change. Message-ID: <0d633757-0b09-7738-8b3d-4c0fd71f51fd@gmail.com> Admins: I was just informed that nvidia terminated its FTP server: https://devtalk.nvidia.com/default/topic/1005867/unix-graphics-announcements-and-news/discontinuing-ftp-access-to-download-nvidia-com/ All nvidia-[legagacyxxx]-{driver, kernel}.info files need to be updated for the new download location: change ftp: to https: I'll post updates when submissions reopen. -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 May 13 18:32:01 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 13 May 2017 11:32:01 -0700 Subject: [Slackbuilds-users] Tracking version releases In-Reply-To: References: <30b42b1b-a630-a6d7-984a-374deabe222c@iinet.net.au> Message-ID: <8f76dd34-9201-95bd-7514-58010dff8481@gmail.com> On 05/11/2017 11:20 PM, Willy Sudiarto Raharjo wrote: >> of thing. There has to be a better way, so does anyone already have a >> better way to keep track before I write something to do it? > > Have you checked repology? > https://repology.org/metapackages/outdated-by-maintainer/chris.willing%40linux.com/ > > it's not up to date due to a typo in one of the script in our repo which > has been fixed in my branch. By the time next public update is pushed, > it should displayed outdated packages maintained by a you > WOW. I think I saw this mentioned before, but as I didn't maintain very many packages, I just waiting for emails about updates, or updated because I needed to on my box. repology gives a nice quick glance at version status. There are a few version numbering glitches that I will post on repologies giyhub issues page Looks like I have 28 now. yikes! -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 dpross1100 at msn.com Sat May 13 23:59:25 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 13 May 2017 23:59:25 +0000 Subject: [Slackbuilds-users] wine-2.0 and wine-2.0.1 no longer compile: missing gnutls_hash In-Reply-To: Message-ID: Thanks guys. Sure enough, I was missing libunistring-compat32. Must have been a new package that I missed somewhere along the line. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun May 14 01:20:52 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 May 2017 08:20:52 +0700 Subject: [Slackbuilds-users] nividia driver, kernel download change. In-Reply-To: <0d633757-0b09-7738-8b3d-4c0fd71f51fd@gmail.com> References: <0d633757-0b09-7738-8b3d-4c0fd71f51fd@gmail.com> Message-ID: <9634c0a7-7576-dd35-7622-6ffbe654e370@slackbuilds.org> > I was just informed that nvidia terminated its FTP server: > > https://devtalk.nvidia.com/default/topic/1005867/unix-graphics-announcements-and-news/discontinuing-ftp-access-to-download-nvidia-com/ > > All nvidia-[legagacyxxx]-{driver, kernel}.info files need to be updated > for the new download location: > > change ftp: to https: > > I'll post updates when submissions reopen. Hi Ed, I have pushed the changes to my branch. Thanks for the notifications -- 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 robby at rlworkman.net Sun May 14 05:53:42 2017 From: robby at rlworkman.net (Robby Workman) Date: Sun, 14 May 2017 00:53:42 -0500 Subject: [Slackbuilds-users] HEADS UP - server maintenance 20170514 0553 UTC Message-ID: <20170514005342.6c52ec06.robby@rlworkman.net> Just a heads-up: things may get a bit wonky with the website for a bit (but hopefully not). We've got the new git server ready to go, but mapping the existing cgit/ URLs to it has proven to be a bit tricky (although in hindsight, not really so tricky based on limited testing here). The git service will be temporarily unavailable as well. Long story short, don't trust anything to be either permanent or up-to-date for the next little while. However, if the testing goes as I hope, we'll do an official switchover for some of our infrastructure tonight. I'll reply to this mail when we have a conclusion either way. -RW From rworkman at slackbuilds.org Sun May 14 09:01:12 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 14 May 2017 04:01:12 -0500 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: <20170514005342.6c52ec06.robby@rlworkman.net> References: <20170514005342.6c52ec06.robby@rlworkman.net> Message-ID: <20170514040112.55b8e332@home.rlworkman.net> On Sun, 14 May 2017 00:53:42 -0500 Robby Workman wrote: > Just a heads-up: things may get a bit wonky with the website > for a bit (but hopefully not). We've got the new git server > ready to go, but mapping the existing cgit/ URLs to it has > proven to be a bit tricky (although in hindsight, not really > so tricky based on limited testing here). > > The git service will be temporarily unavailable as well. > > Long story short, don't trust anything to be either permanent > or up-to-date for the next little while. > > However, if the testing goes as I hope, we'll do an official > switchover for some of our infrastructure tonight. > > I'll reply to this mail when we have a conclusion either way. After a snag with gitolite's default umask of 0077 and way too much time spent figuring out that it was the problem (I'm going to blame the hour - after all, it's 0400 localtime), we are happy to announce a partial migration of SBo services to our new machine. git://slackbuilds.org/ is now git://git.slackbuilds.org/ https://slackbuilds.org/cgit/ is now https://git.slackbuilds.org/ The cgit side should be a completely seamless transition; you don't *have* to do anything at all. Thanks to some mod_rewrite magic on the existing (and the soon to be migrated) website, the old cgit/ links will continue to work indefinitely. However, for git, you'll have to make a slight edit to your config. For our repos you have cloned already, you can either edit the .git/config to fix the url or you can use git itself: git remote set-url origin git://git.slackbuilds.org/slackbuilds.git Those of you with push rights, the process is similar, and we trust that you can figure it out given the above information. All that said, it's still possible to revert this if it becomes absolutely necessary, so please try to find problems with it and let us know if you do. -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 414N at slacky.it Sun May 14 09:32:41 2017 From: 414N at slacky.it (414N) Date: Sun, 14 May 2017 11:32:41 +0200 Subject: [Slackbuilds-users] Terminator SlackBuild In-Reply-To: References: Message-ID: Hello Nikolaou, this is something that others already asked me. I?m aware of newer than 1.00 versions of Terminator and I?ve been informed that it builds ok with only a version bump on -current, however I?d prefer to wait a little time before updating the version of Terminator on SBo. My motives are the following: * as you probably know, the 1.9x versions are *beta* releases for the GTK3 port that should become the new stable when version 2.0 will be released (see the announcement ); * given that also GTK3 is a fast moving target with major releases having already broken backwards compatibility more than once, I guess that waiting a little bit more will bring no harm. Having said this, I?m really glad that it builds good on -current with no work on the current script (apart the version bump), however keep in mind that SlackBuilds on SBo are targeted to *stable* versions of Slackware only . Kindest regards Alan Alberghini SBo clone: GitHub On 02/05/2017 21:06, Panagiotis Nikolaou wrote: > Hi!, > > Terminator latest version is already in 1.91 and after the > new updates in Slackware-current needs a upgrade. > > Can you please upgrade it to the latest version? > A simple bump version update in SlackBuild is quite enough. > I can take over maintenance if you are no longer interested > in maintaining terminator. > > Thank you. > > -------------- next part -------------- An HTML attachment was scrubbed... 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 kjhambrick at gmail.com Sun May 14 12:54:50 2017 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 14 May 2017 07:54:50 -0500 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: <20170514040112.55b8e332@home.rlworkman.net> References: <20170514005342.6c52ec06.robby@rlworkman.net> <20170514040112.55b8e332@home.rlworkman.net> Message-ID: Thanks to All'Y'All ... With a quick edit to my ~/SlackBuilds/14.2/.git/config I was able to `git pull` and it seemed to work fine over Friday Nite's Update. Seems like 'No changes is Good Changes' :) -- kjh # cat 14.2/.git/config [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = git://git.slackbuilds.org/slackbuilds.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master # cd 14.2 # git pull refreshing /home/dld/slackbuilds/14.2 remote: Counting objects: 90, done. remote: Compressing objects: 100% (90/90), done. remote: Total 90 (delta 74), reused 0 (delta 0) Unpacking objects: 100% (90/90), done. >From git://git.slackbuilds.org/slackbuilds + 49a5a72...ca63159 user/bosth/updates -> origin/user/bosth/updates (forced update) + 4e8150b...8c6371d user/ponce/updates -> origin/user/ponce/updates (forced update) + aa1f4b9...89aed57 willysr -> origin/willysr (forced update) Already up-to-date. On Sun, May 14, 2017 at 4:01 AM, Robby Workman wrote: > On Sun, 14 May 2017 00:53:42 -0500 > Robby Workman wrote: > > > Just a heads-up: things may get a bit wonky with the website > > for a bit (but hopefully not). We've got the new git server > > ready to go, but mapping the existing cgit/ URLs to it has > > proven to be a bit tricky (although in hindsight, not really > > so tricky based on limited testing here). > > > > The git service will be temporarily unavailable as well. > > > > Long story short, don't trust anything to be either permanent > > or up-to-date for the next little while. > > > > However, if the testing goes as I hope, we'll do an official > > switchover for some of our infrastructure tonight. > > > > I'll reply to this mail when we have a conclusion either way. > > > After a snag with gitolite's default umask of 0077 and way too > much time spent figuring out that it was the problem (I'm going > to blame the hour - after all, it's 0400 localtime), we are > happy to announce a partial migration of SBo services to our > new machine. > > git://slackbuilds.org/ is now git://git.slackbuilds.org/ > > https://slackbuilds.org/cgit/ is now https://git.slackbuilds.org/ > > The cgit side should be a completely seamless transition; you > don't *have* to do anything at all. Thanks to some mod_rewrite > magic on the existing (and the soon to be migrated) website, > the old cgit/ links will continue to work indefinitely. > > However, for git, you'll have to make a slight edit to your > config. For our repos you have cloned already, you can either > edit the .git/config to fix the url or you can use git itself: > git remote set-url origin git://git.slackbuilds.org/slackbuilds.git > > Those of you with push rights, the process is similar, and we > trust that you can figure it out given the above information. > > All that said, it's still possible to revert this if it becomes > absolutely necessary, so please try to find problems with it > and let us know if you do. > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sun May 14 23:00:44 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 15 May 2017 01:00:44 +0200 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: References: <20170514005342.6c52ec06.robby@rlworkman.net> <20170514040112.55b8e332@home.rlworkman.net> Message-ID: On 14/05/17 14:54, Konrad J Hambrick wrote: > With a quick edit to my ~/SlackBuilds/14.2/.git/config I was able to > `git pull` and it seemed to work fine over Friday Nite's Update. Worked here just fine too. -- Best regards, Andrzej Telszewski From chris.willing at iinet.net.au Mon May 15 00:30:03 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 15 May 2017 10:30:03 +1000 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: <20170514040112.55b8e332@home.rlworkman.net> References: <20170514005342.6c52ec06.robby@rlworkman.net> <20170514040112.55b8e332@home.rlworkman.net> Message-ID: <4825f221-3d7d-81dd-d3c7-309d3fc37716@iinet.net.au> On 14/05/17 19:01, Robby Workman wrote: > Those of you with push rights, the process is similar, and we > trust that you can figure it out given the above information. > > All that said, it's still possible to revert this if it becomes > absolutely necessary, so please try to find problems with it > and let us know if you do. Should we be testing pushes yet, or just pulls? chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Mon May 15 00:41:07 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 14 May 2017 19:41:07 -0500 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: <4825f221-3d7d-81dd-d3c7-309d3fc37716@iinet.net.au> References: <20170514005342.6c52ec06.robby@rlworkman.net> <20170514040112.55b8e332@home.rlworkman.net> <4825f221-3d7d-81dd-d3c7-309d3fc37716@iinet.net.au> Message-ID: <20170514194107.51aaed39@home.rlworkman.net> On Mon, 15 May 2017 10:30:03 +1000 Christoph Willing wrote: > On 14/05/17 19:01, Robby Workman wrote: > > Those of you with push rights, the process is similar, and we > > trust that you can figure it out given the above information. > > > > All that said, it's still possible to revert this if it becomes > > absolutely necessary, so please try to find problems with it > > and let us know if you do. > > Should we be testing pushes yet, or just pulls? Business as usual other than the submit form being closed. -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 duncan_roe at acslink.net.au Mon May 15 01:13:52 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Mon, 15 May 2017 11:13:52 +1000 Subject: [Slackbuilds-users] essential patch for afdko SB Message-ID: <20170515011352.GA17895@dimstar.local.net> Hi moderators, The afdko SB needs this patch to work. Without it, the programs in it will loop indefinitely, looking for the Tools directory. Please apply when circumstances permit, Cheers ... Duncan. -----------------------------8<------------------------------ diff -u /usr/src/slackbuilds/system/afdko/afdko.SlackBuild ./afdko.SlackBuild --- /usr/src/slackbuilds/system/afdko/afdko.SlackBuild 2017-05-13 11:33:55.000000000 +1000 +++ ./afdko.SlackBuild 2017-05-13 21:22:39.000000000 +1000 @@ -24,7 +24,7 @@ PRGNAM=afdko VERSION=${VERSION:-2.5.65322} -BUILD=${BUILD:-1} +BUILD=${BUILD:-2} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then @@ -81,12 +81,12 @@ cd ../.. # Replacement for make install -mkdir -p $PKG/opt/$PRGNAM -mv Tools/linux Tools/SharedData $PKG/opt/$PRGNAM +mkdir -p $PKG/opt/$PRGNAM/Tools +mv Tools/linux Tools/SharedData $PKG/opt/$PRGNAM/Tools -mkdir -p $PKG/opt/$PRGNAM/linux/Python/Current/bin +mkdir -p $PKG/opt/$PRGNAM/Tools/linux/Python/Current/bin ln -s $(readlink -f $(type -p python)) \ - $PKG/opt/$PRGNAM/linux/Python/Current/bin/python2.7 + $PKG/opt/$PRGNAM/Tools/linux/Python/Current/bin/python2.7 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 diff -u /usr/src/slackbuilds/system/afdko/afdko.csh ./afdko.csh --- /usr/src/slackbuilds/system/afdko/afdko.csh 2017-05-13 11:33:55.000000000 +1000 +++ ./afdko.csh 2017-05-13 21:22:39.000000000 +1000 @@ -1,5 +1,5 @@ #!/bin/csh -setenv FDK_EXE /opt/afdko/linux +setenv FDK_EXE /opt/afdko/Tools/linux if ( $?PATH ) then echo :${PATH}: | grep -q :${FDK_EXE}: || setenv PATH ${PATH}:${FDK_EXE} else diff -u /usr/src/slackbuilds/system/afdko/afdko.sh ./afdko.sh --- /usr/src/slackbuilds/system/afdko/afdko.sh 2017-05-13 11:33:55.000000000 +1000 +++ ./afdko.sh 2017-05-13 21:22:39.000000000 +1000 @@ -1,5 +1,5 @@ #!/bin/sh -FDK_EXE="/opt/afdko/linux" +FDK_EXE="/opt/afdko/Tools/linux" if [ ! "$PATH" = "" ]; then echo :$PATH: | grep -q :$FDK_EXE: || PATH=$PATH:$FDK_EXE else From baildon.research at googlemail.com Mon May 15 09:33:32 2017 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 15 May 2017 10:33:32 +0100 Subject: [Slackbuilds-users] essential patch for afdko SB In-Reply-To: <20170515011352.GA17895@dimstar.local.net> References: <20170515011352.GA17895@dimstar.local.net> Message-ID: Hi Duncan, everybody -- > The afdko SB needs this patch to work. Without it, the programs in it will > loop indefinitely, looking for the Tools directory. That explains a lot!! Thanks!! I'm really sorry I broke afdko, I lost the original work I did on it when I was offline, and so I needed to re-do several reviews at the last minute on Friday night and goofed :( So big thanks for putting everything right, I'll get this and Type1_to_OTF and anything else I broke into git later today hopefully. Cheers -D. From artourter at gmail.com Mon May 15 10:56:03 2017 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 15 May 2017 11:56:03 +0100 Subject: [Slackbuilds-users] redshift In-Reply-To: References: <20170319154330.GA25924@jdiamond-nb.acadiau.ca> <8f07e624-b937-484e-1483-34d1973f6b5f@slackbuilds.org> Message-ID: Since this looks to have been abandoned, Anyone want to take this on? Otherwise I am happy to grab it and submit an update. Cheers Greg On 19 March 2017 at 17:02, Gwenhael Le Moine wrote: > I've the slackbuild to build 1.11 > I just needed some small adjustments (maybe $DOC files, it was a long time > ago) > > 2017-03-19 17:51 GMT+01:00 Willy Sudiarto Raharjo >: > >> I see that redshift in slackbuilds is at 1.8, and there it is now up > >> to 1.11. > >> > >> Is there an issue, or is it just that it hasn't been updated? > > > > Last update on redshift was 3 years ago > > https://slackbuilds.org/cgit/slackbuilds/commit/?id= > 35c78b1eedc054b9d5678de099fea9056675f0ea > > > > > > -- > > Willy Sudiarto Raharjo > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dn2010 at gmail.com Mon May 15 12:43:17 2017 From: dn2010 at gmail.com (Daniil Bratashov) Date: Mon, 15 May 2017 16:43:17 +0400 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: <20170514194107.51aaed39@home.rlworkman.net> References: <20170514005342.6c52ec06.robby@rlworkman.net> <20170514040112.55b8e332@home.rlworkman.net> <4825f221-3d7d-81dd-d3c7-309d3fc37716@iinet.net.au> <20170514194107.51aaed39@home.rlworkman.net> Message-ID: sbopkg master seems to be broken with this changes. On Mon, May 15, 2017 at 4:41 AM, Robby Workman wrote: > On Mon, 15 May 2017 10:30:03 +1000 > Christoph Willing wrote: > > > On 14/05/17 19:01, Robby Workman wrote: > > > Those of you with push rights, the process is similar, and we > > > trust that you can figure it out given the above information. > > > > > > All that said, it's still possible to revert this if it becomes > > > absolutely necessary, so please try to find problems with it > > > and let us know if you do. > > > > Should we be testing pushes yet, or just pulls? > > > Business as usual other than the submit form being closed. > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon May 15 13:10:17 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 15 May 2017 15:10:17 +0200 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: References: <20170514005342.6c52ec06.robby@rlworkman.net> <20170514040112.55b8e332@home.rlworkman.net> <4825f221-3d7d-81dd-d3c7-309d3fc37716@iinet.net.au> <20170514194107.51aaed39@home.rlworkman.net> Message-ID: 2017-05-15 14:43 GMT+02:00 Daniil Bratashov : > sbopkg master seems to be broken with this changes. just edit /etc/sbopkg/repos.d/90-SBo-master.repo substituting the string git://slackbuilds.org/slackbuilds.git with git://git.slackbuilds.org/slackbuilds.git From willysr at slackbuilds.org Mon May 15 16:02:01 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 15 May 2017 23:02:01 +0700 Subject: [Slackbuilds-users] redshift In-Reply-To: References: <20170319154330.GA25924@jdiamond-nb.acadiau.ca> <8f07e624-b937-484e-1483-34d1973f6b5f@slackbuilds.org> Message-ID: > Since this looks to have been abandoned, Anyone want to take this on? > Otherwise I am happy to grab it and submit an update. Hi Greg feel free to take over when the submission is open -- 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 May 15 16:02:37 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 15 May 2017 23:02:37 +0700 Subject: [Slackbuilds-users] git and cgit migration -- 20170514 0900 UTC In-Reply-To: References: <20170514005342.6c52ec06.robby@rlworkman.net> <20170514040112.55b8e332@home.rlworkman.net> <4825f221-3d7d-81dd-d3c7-309d3fc37716@iinet.net.au> <20170514194107.51aaed39@home.rlworkman.net> Message-ID: <81beab3d-97c4-29e7-63c8-748b14f92d3c@slackbuilds.org> >> sbopkg master seems to be broken with this changes. > > just edit /etc/sbopkg/repos.d/90-SBo-master.repo substituting the string > > git://slackbuilds.org/slackbuilds.git > > with > > git://git.slackbuilds.org/slackbuilds.git This has been fixed in sbopkg master as well, thanks to Matteo who submitted PR. -- 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 sam_web at yahoo.de Tue May 16 08:12:43 2017 From: sam_web at yahoo.de (Marek Srejma) Date: Tue, 16 May 2017 10:12:43 +0200 Subject: [Slackbuilds-users] Trouble with building LibreOffice with low space in /root Message-ID: <4b369fa9-b098-1ca9-1f2c-de1b137c3d6b@yahoo.de> Hi, when I tried to build LibreOffice , it failed because of "no free space" in my /root partition, even though I use a different partition for $TMP and $OUTPUT, which has enough free space. The reason was the usage /root/.ccache, which grew to a size of 1.6GB when it failed (which was the free space in /root). So I added the option --disable-ccache to the .configure line and then it built fine, without using any additional space in /root. I think it would be useful to have this as an additional option builtin in the SlackBuild and to mention it in the README. Marek From kava0418 at online.be Sat May 6 10:40:28 2017 From: kava0418 at online.be (Karel Venken) Date: Sat, 6 May 2017 12:40:28 +0200 Subject: [Slackbuilds-users] source -> bin In-Reply-To: <3088351.zFUrQ3OOvj@ithil> References: <3088351.zFUrQ3OOvj@ithil> Message-ID: <590DA81C.3080804@online.be> Ivan Zaigralin wrote: > I'd like to consider switching icecat from being source-based to a binary re- > package. That's OK by the SBo rules, right? > Sources are great if you want to set your own options (compiler flags, optional dependencies) or build it for another platorm (Arm) But if it is too much work to have a sources script, having binaries is better then nothing at all ;-) From andrei.alexsson at gmail.com Mon May 8 20:56:26 2017 From: andrei.alexsson at gmail.com (Andrei Alexsson) Date: Mon, 8 May 2017 22:56:26 +0200 Subject: [Slackbuilds-users] Delivery Status Notification (Failure) In-Reply-To: <5910daac.42072e0a.9159f.7cc4.GMRIR@mx.google.com> References: <0adf34db-dc8f-d8dd-2769-e71e31f78bb8@gmail.com> <5910daac.42072e0a.9159f.7cc4.GMRIR@mx.google.com> Message-ID: <9f4f640a-54d7-c740-5e33-4de500410bfe@gmail.com> Hi, I try to compile motion: https://slackbuilds.org/repository/14.2/system/motion/ on Slackware 14.2 64-bit. However, it does not compile successful when ffmpeg is installed. Any idea how to solve this? Thank you, Andrei From chris.willing at iinet.net.au Tue May 16 11:12:28 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 16 May 2017 21:12:28 +1000 Subject: [Slackbuilds-users] Trouble with building LibreOffice with low space in /root In-Reply-To: <4b369fa9-b098-1ca9-1f2c-de1b137c3d6b@yahoo.de> References: <4b369fa9-b098-1ca9-1f2c-de1b137c3d6b@yahoo.de> Message-ID: On 16/05/17 18:12, Marek Srejma wrote: > Hi, > > when I tried to build LibreOffice > , it failed > because of "no free space" in my /root partition, even though I use a > different partition for $TMP and $OUTPUT, which has enough free space. > The reason was the usage /root/.ccache, which grew to a size of 1.6GB > when it failed (which was the free space in /root). > > So I added the option --disable-ccache to the .configure line and then > it built fine, without using any additional space in /root. > > I think it would be useful to have this as an additional option builtin > in the SlackBuild and to mention it in the README. > Thanks for raising this issue. I've never noticed a problem with it myself but based on: https://wiki.documentfoundation.org/Development/BuildingOnLinux#ccache it looks like having a USE_CCACHE option, set to off by default, would be useful. chris From matteo.bernardini at gmail.com Tue May 16 12:23:14 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 16 May 2017 14:23:14 +0200 Subject: [Slackbuilds-users] Delivery Status Notification (Failure) In-Reply-To: <9f4f640a-54d7-c740-5e33-4de500410bfe@gmail.com> References: <0adf34db-dc8f-d8dd-2769-e71e31f78bb8@gmail.com> <5910daac.42072e0a.9159f.7cc4.GMRIR@mx.google.com> <9f4f640a-54d7-c740-5e33-4de500410bfe@gmail.com> Message-ID: Seems to build fine here. Can you please paste the error you got? Il 16 mag 2017 13:21, "Andrei Alexsson" ha scritto: Hi, I try to compile motion: https://slackbuilds.org/reposi tory/14.2/system/motion/ on Slackware 14.2 64-bit. However, it does not compile successful when ffmpeg is installed. Any idea how to solve this? Thank you, Andrei _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue May 16 12:56:30 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 16 May 2017 19:56:30 +0700 Subject: [Slackbuilds-users] Delivery Status Notification (Failure) In-Reply-To: References: <0adf34db-dc8f-d8dd-2769-e71e31f78bb8@gmail.com> <5910daac.42072e0a.9159f.7cc4.GMRIR@mx.google.com> <9f4f640a-54d7-c740-5e33-4de500410bfe@gmail.com> Message-ID: > Seems to build fine here. > Can you please paste the error you got? It was updated in the last public update. Previously, it did failed to build with ffmpeg this message was in moderation queue for few days -- 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 Wed May 17 13:21:03 2017 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 17 May 2017 08:21:03 -0500 Subject: [Slackbuilds-users] pycrypto download URL down | fix Message-ID: <6fad537c-3c0d-3e7b-a7cf-43d76e0316cf@linux.com> Hello The download URL for pycrypto is unavailable: https://ftp.dlitz.net/pub/dlitz/crypto/pycrypto/pycrypto-2.6.1.tar.gz An alternative download is found at https://pypi.python.org/packages/source/p/pycrypto/pycrypto-2.6.1.tar.gz Regards Gerardo Zamudio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Wed May 17 14:18:03 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 17 May 2017 15:18:03 +0100 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? Message-ID: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> I have been chasing this issue on-and-off for months, and spent a lot of time the last few days on it. I run several Slackware servers with Spamassassin on them, and I noticed a while ago that some don't use DNS blocklists. This is a very subtle problem, because SpamAssassin is not showing any errors anywhere, either with debug turned on or using --lint. Also, the Pyzor, bayes and other filters are so good, that most email gets filtered correctly anyway - so I didn't realise for a good while that the dns blocklists weren't being used. Only by running the same known spam message containing spammy links through SpamAssassin on both servers I realised that one of them was not using dns rbl's I am running SA 3.4.1 everywhere on Slackware -current and a Slackware 14.2 (both 32 and 64 bit) - none of these make a difference. I have even removed all Perl modules (and Perl) and re-installed the latest versions directly from CPAN. I tried resetting all the SpamAssassin configs to defaults, and removed all the SA rules and re-run sa-update. The only thing that has cured it eventually, at the suggestion of someone on the SpamAssassin mailing list, is manually compiling and installing SpamAssassin 3.4.1 downloaded directly from apache.org. This would suggest that the SBo scripts somehow break the dns rbl's functionality for SpamAssassin - but I'm afraid I have been unable to determine how. I'm putting this outthere in case it helps someone - or if somebody has some idea as to how we can narrow this further. Also maybe others who have SpamAssassin installed on their system might want to run the above check and provide some input, it would be really useful. From willysr at slackbuilds.org Wed May 17 15:11:46 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 17 May 2017 22:11:46 +0700 Subject: [Slackbuilds-users] pycrypto download URL down | fix In-Reply-To: <6fad537c-3c0d-3e7b-a7cf-43d76e0316cf@linux.com> References: <6fad537c-3c0d-3e7b-a7cf-43d76e0316cf@linux.com> Message-ID: <9e0ccf49-3a5d-0274-7d89-9296e36cd39e@slackbuilds.org> > The download URL for pycrypto is unavailable: > https://ftp.dlitz.net/pub/dlitz/crypto/pycrypto/pycrypto-2.6.1.tar.gz > > An alternative download is found at > https://pypi.python.org/packages/source/p/pycrypto/pycrypto-2.6.1.tar.gz Thanks for reporting it's now fixed in 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 slackbuilds at schoepfer.info Wed May 17 15:31:56 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 17 May 2017 17:31:56 +0200 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? In-Reply-To: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> References: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> Message-ID: <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> On 17.05.2017 16:18, Sebastian Arcus wrote: > I have been chasing this issue on-and-off for months, and spent a lot of > time the last few days on it. I run several Slackware servers with > Spamassassin on them, and I noticed a while ago that some don't use DNS > blocklists. Maybe your are using the providers nameserver, beside a lot others, so the providers nameserver itself may be blacklistet because of too much reqeuests, and therfore gets no(or only sometimes) answers from the dns blackalist severs. This also happens if you are using google's dns 8.8.8.8 If this is the problem, providing your own Nameserver may be the solution. Johannes From s.arcus at open-t.co.uk Wed May 17 17:17:32 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 17 May 2017 18:17:32 +0100 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? In-Reply-To: <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> References: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> Message-ID: <89603844-447d-d542-f80d-ec27f6792687@open-t.co.uk> On 17/05/17 16:31, Franzen wrote: > On 17.05.2017 16:18, Sebastian Arcus wrote: >> I have been chasing this issue on-and-off for months, and spent a lot of >> time the last few days on it. I run several Slackware servers with >> Spamassassin on them, and I noticed a while ago that some don't use DNS >> blocklists. > > Maybe your are using the providers nameserver, beside a lot others, so > the providers nameserver itself may be blacklistet because of too much > reqeuests, and therfore gets no(or only sometimes) answers from the dns > blackalist severs. This also happens if you are using google's dns 8.8.8.8 Sorry, I should have mentioned it in the original post. I am running Bind locally in caching/recursive mode. Also, if that would have been the problem, the queries get flagged as blocked by SpamAssassin in the message report - so it is quite soon obvious what is going on. I've had this in the past, before configuring Bind. What I am describing is a silent issue - no errors, no messages about queries being blocked. And that is why it took me a while to realise it was a problem, because if there is no mention in the spam report of dns rbl's - the assumption would be that the dns queries returned nothing - not that they are not working altogether. Only by passing the same known spam message through SpamAssassin on different servers did I realise that the dns rbl's weren't functional. From andrew.m.goth at gmail.com Fri May 19 19:18:17 2017 From: andrew.m.goth at gmail.com (Andy Goth) Date: Fri, 19 May 2017 14:18:17 -0500 Subject: [Slackbuilds-users] Submission status In-Reply-To: References: Message-ID: On April 13 I submitted a SlackBuild script update for Fossil version 2.2 and received the following email: New upload: fossil.tar.gz Category: Development Submission md5: eed5f9be7df09f9cf663d5b7ce84dabb What is the status of this submission? I do not see it in the pending queue, nor is it in the accepted submission list. I'm not subscribed to the list, so please Cc: me on replies. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Fri May 19 20:06:51 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 19 May 2017 22:06:51 +0200 Subject: [Slackbuilds-users] Submission status In-Reply-To: References: Message-ID: 2017-05-19 21:18 GMT+02:00 Andy Goth : > On April 13 I submitted a SlackBuild script update for Fossil version 2.2 > and received the following email: > > New upload: fossil.tar.gz > Category: Development > Submission md5: eed5f9be7df09f9cf663d5b7ce84dabb > > What is the status of this submission? I do not see it in the pending queue, > nor is it in the accepted submission list. > > I'm not subscribed to the list, so please Cc: me on replies. Hi Andy, I had a look at the notifying emails we got about the submissions and found this - - - New upload: fossil.tar.gz () Maintainer: Andy Goth Email: Category: Development Keywords: Version: 2.1 (db: 2.1) Home Page: https://www.fossil-scm.org/ Sources (32bit): http://fossil-scm.org/index.html/uv/fossil-src-2.1.tar.gz MD5SUMS (32bit): 9f32b23cecb092d42cdf11bf003ebf8d Sources (64bit): MD5SUMS (64bit): Requires: Slackware: 14.2 Submission md5: eed5f9be7df09f9cf663d5b7ce84dabb Comments: - - - looking just at it seems like it was about the same version you submitted a few days earlier and that got approved on the same day, april 13th https://git.slackbuilds.org/slackbuilds/commit/?id=e5a9375ea1cc08fa3ff8bb0d41fa948f28b295be if it's ok for you, once submissions will reopen, could you please resubmit it, rebasing your changes on what we have now in the repository? Matteo From andrew.m.goth at gmail.com Fri May 19 20:09:27 2017 From: andrew.m.goth at gmail.com (Andy Goth) Date: Fri, 19 May 2017 15:09:27 -0500 Subject: [Slackbuilds-users] Submission status In-Reply-To: References: Message-ID: Tomorrow I will be able to look into this. I'm sorry if I sent the wrong version, in which case I'll be sure to resubmit my latest (after merging in any changes you may have made). Thanks for checking. On May 19, 2017 15:06, "Matteo Bernardini" wrote: > 2017-05-19 21:18 GMT+02:00 Andy Goth : > > On April 13 I submitted a SlackBuild script update for Fossil version 2.2 > > and received the following email: > > > > New upload: fossil.tar.gz > > Category: Development > > Submission md5: eed5f9be7df09f9cf663d5b7ce84dabb > > > > What is the status of this submission? I do not see it in the pending > queue, > > nor is it in the accepted submission list. > > > > I'm not subscribed to the list, so please Cc: me on replies. > > Hi Andy, > > I had a look at the notifying emails we got about the submissions and > found this > > - - - > New upload: fossil.tar.gz () > Maintainer: Andy Goth > Email: > Category: Development > Keywords: > Version: 2.1 (db: 2.1) > Home Page: https://www.fossil-scm.org/ > Sources (32bit): http://fossil-scm.org/index.html/uv/fossil-src-2.1.tar.gz > MD5SUMS (32bit): 9f32b23cecb092d42cdf11bf003ebf8d > Sources (64bit): > MD5SUMS (64bit): > Requires: > Slackware: 14.2 > Submission md5: eed5f9be7df09f9cf663d5b7ce84dabb > Comments: > - - - > > looking just at it seems like it was about the same version you > submitted a few days earlier and that got approved on the same day, > april 13th > > https://git.slackbuilds.org/slackbuilds/commit/?id= > e5a9375ea1cc08fa3ff8bb0d41fa948f28b295be > > if it's ok for you, once submissions will reopen, could you please > resubmit it, rebasing your changes on what we have now in the > repository? > > Matteo > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat May 20 01:07:31 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 May 2017 08:07:31 +0700 Subject: [Slackbuilds-users] Updates - 20170520.1 Message-ID: Hi folks this is the first public update happening on the new machine donated by the community (Thanks to all donators who have contributed). Since we closed submissions before migrations, the changes mostly came from admins and selected maintainers who have git push access to the repository. Robby and David are working to fix HOMEPAGE and DOWNLOAD entries in all categories listed in https://repology.org/repository/slackbuilds/problems. After a new sync, most of the entries there will be gone and the rest will be fixed in the next public update. LibreOffice now include a new option to use CCACHE (disabled by default), letsencrypt is now more robust on detecting multiple vhost, enables users to activate/renew certs in all domains in the same time, and a working Apache (httpd) plugin so no downtime is required. Please make sure to grab the latest update from SBo's website and/or SBo Git repository when submitting new update. If you haven't seen anything new on the SBo, please be patient as the DNS migration take some time to propagate. Other admins will make another announcement once it's done. Sat May 20 00:00:03 UTC 2017 academic/GeoGebra: Updated homepage academic/bpp-seq-omics: Fixed VERSION in SlackBuild. academic/gresistor: Updated homepage academic/itex2mml: Updated homepage and download links academic/mendeleydesktop: Updated homepage link. academic/ncbi-blast-plus: Updated homepage link. academic/ncbi-blast: Updated homepage link. academic/qtoctave: Updated homepage link. academic/sage: Updated for version 7.6. academic/suitesparse: Updated for version 4.5.5 audio/easymp3gain: Updated homepage and download links audio/grip2: Updated homepage and download links audio/gvolwheel: Updated homepage and download links audio/horgand: Updatd homepage audio/id3v2: Updated homepage and download links audio/jackmeter: Updated homepage and download links audio/lxmusic: Updated homepage and download links audio/mixxx: Updated homepage link. audio/mp3blaster: Updated for version 3.2.6. audio/mpc: Updated homepage and download links. audio/mpd: Updated homepage and download links. audio/ncmpc: Updated homepage and download links. audio/ogmtools: Updated homepage and download links. audio/phat: Updated homepage and download links. audio/pianobar: Updated homepage link. audio/pyalsaaudio: Updated homepage link. desktop/compiz-boxmenu: Updated homepage and download links desktop/elementary-xfce: Updated homepage desktop/enlightenment: Updated homepage and download links desktop/gntp-send: Updated homepage and download links desktop/homerun: Updated homepage and download links desktop/insync-thunar: Updated homepage desktop/lumina: Updated homepage desktop/lxpanel: Updated homepage and download links desktop/menumaker: Updated for version 0.99.10. desktop/perwindowlayoutd: Updated homepage and download links. desktop/screenkey: Fixed deps. desktop/slock: Updated for version 1.4. desktop/vim-qt: Updated for version 20170421. desktop/xfce4-mount-plugin: Updated for version 1.1.2. development/Arduino: Updated homepage development/MySQL-python: Updated homepage and download links. development/arduino: Updated homepage development/bpython: Updated homepage development/bzr: Updated for version 2.7.0. development/ccl: Updated homepage development/check: Updated homepage development/checkbashisms: Updated homepage development/colordiff: Updated homepage and download links development/crosstool-ng: Updated for version 1.23.0 development/cvsd: Updated homepage and download links development/dart: Fixed arch handling. development/diffuse: Updated homepage and download links development/docutils: Updated for version 0.13.1. development/dwarf: Updated homepage development/electron: Updated homepage development/flawfinder: Updated homepage and download links development/fpc-source: Updated homepage and download links development/fpc: Updated homepage and download links development/ftjam: Updated homepage and download links development/gaphor: Updated homepage and download links development/glade: Updated homepage and download links development/gnome-common: Updated homepage and download links development/google-webdesigner: Fix VERSION. development/gplcver: Updated homepage and download links development/hopper: Updated homepage development/julia: Updated homepage development/kdesvn: Updated homepage and download links development/libretro-samples: Updated homepage development/mysql-workbench: Patched against new gdal 2.2.0. development/nedit: Updated homepage and download links. development/nose: Updated homepage and download links. development/nwjs: Fixed arch handling. development/opencl-headers: Updated homepage link. development/p4: Updated homepage and download links. development/p4d: Updated homepage and download links. development/p4v: Updated homepage and download links. development/phpDocumentor: Updated homepage and download links. development/processing: Updated homepage link. development/pycscope: Updated homepage and download links. development/pylint: Updated homepage link. development/python3-cycler: Fixed deps. development/referenceassemblies-pcl: Fixed tarball handling. games/3D-Fasteroids: Updated home page and download link games/4do-libretro: Updated homepage link games/Craft-libretro: Updated homepage games/Genesis-Plus-GX: Updated homepage games/OpenXcom: Updated homepage link. games/ardentryst: Updated homepage and download links games/beetle-bsnes-libretro: Updated homepage games/beetle-gba-libretro: Updated homepage games/beetle-lynx-libretro: Updated homepage games/beetle-ngp-libretro: Updated homepage games/beetle-pce-fast-libretro: Updated homepage games/beetle-pcfx-libretro: Updated homepage games/beetle-psx-libretro: Updated homepage games/beetle-saturn-libretro: Updated homepage games/beetle-supergrafx-libretro: Updated homepage games/beetle-vb-libretro: Updated homepage games/beetle-wswan-libretro: Updated homepage games/blastem-libretro: Updated homepage games/blobwars: Updated homepage and download links games/blueMSX-libretro: Updated homepage games/bnes-libretro: Updated homepage games/bomberclone: Updated homepage and download links games/boswars: Updated homepage and download links games/bsnes-libretro: Updated homepage games/bsnes-mercury: Updated homepage games/bzflag: Updated homepage and download links games/ckmame: Updated homepage and download links games/connectagram: Updated homepage and download links games/cubosphere: Updated homepage and download links games/cutemaze: Updated homepage and download links games/cyphesis: Updated homepage and download links games/enigma: Updated homepage and download links games/etlegacy-data: Updated homepage games/etlegacy: Updated homepage games/extremetuxracer: Updated homepage and download links games/fbalpha: Updated homepage games/fgrun: Updated homepage and download links games/fmsx-libretro: Updated homepage games/fortune-dharma: Updated homepage and download links games/gambatte-libretro: Update homepage games/glxosd: Updated homepage games/gottet: Updated homepage and download links games/gpsp-libretro: Updated homepage games/gw-libretro: Updated homepage games/hexalate: Updated homepage and download links games/icebreaker: Updated homepage and download links games/ioquake3: Updated homepage games/kildclient: Updated homepage and download links games/libretro-2048: Updated homepage games/libretro-desmume: Updated homepage games/libretro-fceumm: Updated homepage games/libretro-handy: Updated homepage games/libretro-lutro: Updated homepage games/libretro-mgba: Updated homepage games/libretro-ppsspp: Updated homepage games/libretro-prboom: Updated homepage games/libretro-reicast: Updated homepage games/libretro-vecx: Updated homepage games/libretro-yabause: Updated homepage games/lincity-ng: Updated homepage and download links games/mame2000-libretro: Updated homepage link. games/mame2010-libretro: Updated homepage link. games/mame2014-libretro: Updated homepage link. games/meteor-libretro: Updated homepage link. games/mupen64plus-libretro: Updated homepage link. games/nestopia-libretro: Updated homepage link. games/nxengine-libretro: Updated homepage link. games/pcsx-rearmed: Updated homepage link. games/peg-e: Updated homepage and download links. games/picodrive-libretro: Updated homepage link. games/pingus: Updated homepage and download links. games/pioneer: Updated homepage link. games/prosystem-libretro: Updated homepage link. games/puzzles: Updated homepage link. games/qtsixa: Updated homepage and download links. gis/OWSLib: Updated homepage link. gis/foxtrotgps: Updated homepage and download links gis/geojson: Updated for version 1.3.5. gis/libLAS: Updated homepage gis/opencpn: Updated homepage link. gis/polyline: Updated homepage link. graphics/digikam: Updated homepage and download links graphics/feh: Updated homepage and download links graphics/gthumb: Updated for version 3.4.5. graphics/kuickshow: Updated homepage graphics/luminance-hdr: Updated for version 2.5.1. graphics/mirage: Updated homepage and download links. graphics/openclipart: Updated homepage and download links. graphics/opencollada: Updated for version 1.6.47 graphics/opencolorio: Updated for version 1.0.9.20170426 graphics/openimageio: Updated for version 1.7.14 graphics/pdf2png: Updated homepage link. graphics/qelectrotech: Updated homepage link. graphics/qrencode: Updated homepage and download links. ham/chirp: Updated for version 20170510. ham/cqrlog: Updated homepage haskell/hscolour: Updated for version 1.24.1 libraries/Atlas-C++: Updated homepage and download links libraries/BeautifulSoup4: Updated homepage libraries/BeautifulSoup: Updated homepage and download links libraries/CCfits: Updated homepage and download links libraries/ConfigParser: Updated homepage libraries/GtkD: Updated homepage libraries/Impacket: Updated homepage libraries/Jinja2: Updated homepage libraries/Nevow: Updated homepage link. libraries/ORBit2: Updated homepage link. libraries/allegro4: Updated homepage and download link libraries/allegro: Updated homepage and download link libraries/aubio: Updated homepage and download links libraries/barry: Updated homepage and download links libraries/cfitsio: Updated homepage and download links libraries/chromaprint: Updated homepage libraries/cryptopp: Updated homepage and download links libraries/daq: Updated homepage and download links libraries/darcsver: Updated homepage and download links libraries/dropbox-python: Updated homepage libraries/e_dbus: Updated homepage and download links libraries/ecore: Updated homepage and download links libraries/edje: Updated homepage and download links libraries/eet: Updated homepage and download links libraries/efreet: Updated homepage and download links libraries/eina: Updated homepage and download links libraries/eio: Updated homepage and download links libraries/elementary: Updated homepage and download links libraries/embryo: Updated homepage and download links libraries/emotion: Updated homepage and download links libraries/ethumb: Updated homepage and download links libraries/evas: Updated homepage and download links libraries/fox-toolkit-devel: Updated for version 1.7.59. libraries/fox-toolkit: Updated for version 1.6.54. libraries/fpconst: Updated homepage and download links libraries/gaphas: Updated homepage and download links libraries/gdl: Updated homepage and download links libraries/gnome-python2-gconf: Updated homepage and download links libraries/goffice: Updated for version 0.10.34. libraries/gstreamermm: Updated homepage and download links libraries/gtk-aurora-engine: Updated homepage and download links libraries/gtkdatabox: Updated homepage and download links libraries/gtkglext: Updated homepage and download links libraries/gtkglextmm: Updated homepage and download links libraries/hdf: Updated homepage and download links libraries/imlib2: Updated homepage and download links libraries/libbonobo: Updated homepage and download links libraries/libbonoboui: Updated homepage and download links libraries/libbsd: Updated homepage and download links libraries/libcdaudio: Updated homepage and download links libraries/libcec: Fixed tarball handling. libraries/libcsv: Updated homepage and download links libraries/libdc1394: Updated homepage and download links libraries/libdmapsharing: Updated homepage and download links libraries/libdvbpsi: Updated for version 1.3.1. libraries/libftdi1: Updated homepage and download links libraries/libftdi: Updated homepage and download links libraries/libg15: Updated homepage and download links libraries/libg15render: Updated homepage and download links libraries/libgaminggear: Updated homepage and download links libraries/libgda: Updated homepage and download links libraries/libgit2-glib: Updated homepage and download links libraries/libgnome: Updated homepage and download links libraries/libgnomecups: Updated homepage and download links libraries/libgnomeprint: Updated homepage and download links libraries/libgnomeprintui: Updated homepage and download links libraries/libgnomeui: Updated homepage and download links libraries/libgringotts: Updated homepage and download links libraries/libicns: Updated homepage and download links libraries/libiec61883: Updated homepage and download links libraries/libkvkontakte: Updated homepage and download links libraries/libmimedir: Updated homepage and download links libraries/libmpdclient: Updated homepage and download links libraries/libmspack: Updated homepage and download links libraries/libnet: Updated homepage and download links libraries/libnice: Updated homepage and download links libraries/libopenshot-audio: Fixed maintainer email libraries/liborigin: Updated homepage and download links libraries/libr3: Fixed download. libraries/libsmf: Updated homepage and download links libraries/libtxc_dxtn: Updated homepage and download links libraries/libvmime: Updated homepage and download links libraries/libxkbcommon: Updated homepage and download links libraries/lockdev: Updated homepage libraries/logilab-astng: Updated homepage and download links libraries/logilab-common: Updated homepage and download links libraries/lua-MessagePack: Noted orphan status (no SBo maintainer). libraries/mbedtls: Updated homepage and download links. libraries/mercator: Updated homepage and download links. libraries/mujs: Updated homepage link. libraries/mysql-connector-c++: Updated for version 1.1.9. libraries/ois: Updated homepage and download links. libraries/pgtcl-ng: Updated homepage and download links. libraries/poco: Updated homepage link. libraries/polyclipping: Updated homepage and download links. libraries/pyte: Fixed deps. libraries/python-e_dbus: Updated homepage and download links. libraries/python-elementary: Updated homepage and download links. libraries/python-emotion: Updated homepage and download links. libraries/python-ethumb: Updated homepage and download links. libraries/python-evas: Updated homepage and download links. libraries/qt5-webkit: Updated homepage and download links. libraries/wxGTK3: Updated for version 3.0.3.1. misc/bodr: Updated homepage and download links misc/ciso: Updated homepage and download links misc/cups-windows: Updated homepage misc/dcc: Updated homepage misc/g15composer: Updated homepage and download links misc/g15daemon: Updated homepage and download links misc/g15stats: Updated homepage and download links misc/gnome-mime-data: Updated homepage and download links misc/kcm-fcitx: Updated homepage and download links misc/klibc: Updated homepage and download links multimedia/JSampler: Updated homepage and download links multimedia/Mopidy: Updated homepage link. multimedia/OpenLP: Updated homepage and download links. multimedia/cinelerra: Updated homepage and download links multimedia/coriander: Updated homepage and download links multimedia/gimp-gap: Updated homepage and download links multimedia/gpac: Remove old a52dec reference from README. multimedia/gst-libav: Updated homepage and download links multimedia/gst-plugins-bad: Updated homepage and download links multimedia/gst-plugins-ugly: Updated homepage and download links multimedia/gst0-ffmpeg: Updated homepage and download links multimedia/gst0-plugins-bad: Updated homepage and download links multimedia/gst0-plugins-ugly: Updated homepage and download links multimedia/iat: Updated homepage and download links multimedia/jlscp: Updated homepage and download links multimedia/lsdvd: Updated homepage and download links multimedia/mlt: Updated homepage and download links. multimedia/mpv: Updated for version 0.25.0. multimedia/mtpfs: Updated homepage and download links. multimedia/mythplugins: Updated homepage and download links. multimedia/mythtv: Updated homepage link. multimedia/obs-studio: Updated for version 18.0.2 multimedia/pngnq-s9: Updated homepage and download links. network/NetworkManager-openconnect: Updated for version 1.2.4. network/NetworkManager-openvpn: Updated for version 1.2.8. network/NetworkManager-pptp: Updated for version 1.2.4. network/NetworkManager-vpnc: Updated for version 1.2.4. network/amavisd-new: Updated homepage network/aria2: Updated for version 1.32.0. network/awscli: Updated homepage network/bitlbee: Updated homepage and download links network/btpd: Updated homepage and download links network/c-toxcore: Updated homepage network/darkstat: Updated homepage and download links network/dillo: Updated homepage and download links network/dnscrypt-proxy: Updated homepage and download links network/driftnet: Fixed tarball handling. network/dropbox: Updated homepage network/dsniff: Updated homepage and download links network/flexget: Updated homepage network/gq: Updated homepage and download links network/gtk-gnutella: Updated homepage and download links network/havp: Updated homepage and download links network/hiawatha: Updated homepage and download links network/httpie: Updated homepage network/insync: Updated homepage network/iperf: Updated homepage and download links network/konversation: Updated homepage and download links network/leechcraft: Updated homepage and download links network/lighttpd: Change some hints in README.SLACKWARE. network/megatools: Updated homepage link. network/metasploit: Updated homepage link. network/mod_ruid2: Updated homepage and download link network/munge: Updated homepage link. network/nagios: Updated homepage and download links. network/nbd: Updated for version 3.15.2 network/ngircd: Updated homepage and download links. network/nload: Updated homepage and download links. network/nrpe: Updated homepage and download links. network/nsca: Updated homepage and download links. network/nxclient: Updated homepage link. network/onioncat: Updated homepage link. network/openconnect: Updated for version 7.08. network/openrdate: Updated homepage and download links. network/openresolv: Updated homepage and download links. network/opensmtpd: Updated homepage and download links. network/owncloud-client: Updated homepage link. network/owncloud-server: Updated homepage and download links. network/pastebincl: Updated homepage and download links. network/pgl: Updated homepage and download links. network/pidgin-sound: Updated homepage and download links. network/putty: Updated homepage link. network/sshuttle: Fixed deps. network/telegram: Updated for version 1.1.2. network/weechat: Updated for version 1.8. network/wireshark: Update DOWNLOAD url. network/xtables-addons: Updated for version 2.12. office/LibreOffice: Added USE_CCACHE option (default off) office/abiword: Updated for version 3.0.2. office/ding: Updated homepage office/fbreader: Updated homepage and download links office/focuswriter: Updated homepage and download links office/gnumeric: Updated for version 1.12.34. office/moneydance: Updated for version 2017.1597. office/mupdf: Updated homepage and download links. office/openoffice-langpack: Fixed slack-desc. office/pdfstudio11: Updated homepage and download links. office/pdftk: Updated homepage and download links. office/smoffice2016: Fixed arch handling. perl/perl-YAML-LibYAML: Updated for version 0.65. python/APScheduler: Updated homepage python/Automat: Fixed deps. python/Flask-Babel: Updated homepage and download links. python/Markdown: Updated homepage link. python/MarkupSafe: Updated homepage link. python/PythonQt: Updated for version 3.1.6 python/asciimatics: Fixed deps. python/bitarray: Updated homepage and download links. python/blinker: Updated homepage python/boto3: Updated homepage python/cheroot: Fixed deps. python/decorator: Updated homepage link. python/etk.docking: Updated homepage and download links python/euca2ools: Updated for version 3.3.3 python/feedgenerator: Updated homepage python/functools-lru-cache: Fixed deps. python/gnome-python: Updated homepage and download links python/gst-python3: Updated homepage and download links python/gst-python: Updated homepage and download links python/gst0-python: Updated homepage and download links python/json-py: Updated homepage and download links python/jsonschema: Fixed deps. python/linecache2: Fixed deps. python/netifaces: Updated homepage link. python/parsel: Fixed deps. python/pelican: Updated homepage link. python/pyOpenSSL: Updated homepage link. python/pySmartDL: Updated homepage link. python/pyasn1: Updated homepage and download links. python/pycrypto: Update DOWNLOAD url. python/pycryptopp: Updated homepage link. python/pygpgme: Updated homepage and download links. python/pyrsistent: Updated homepage link. python/pysnmp: Updated homepage and download links. python/python-Levenshtein: Updated homepage and download links. python/python-autobahn: Updated for version 17.5.1. python/python-bigfloat: Updated homepage and download links. python/python-blake2: Updated homepage and download links. python/python-configargparse: Updated for version 0.12.0. python/python-demjson: Updated homepage and download links. python/python-keyring: Fixed deps. python/python-ldap: Updated homepage link. python/python-mccabe: Fixed deps. python/python-morbid: Updated homepage and download links. python/python-mpd: Updated homepage and download links. python/python-oauth2: Updated homepage and download links. python/python-parsedatetime: Updated for version 2.4. python/python-swiftclient: Updated homepage link. python/python-transaction: Updated homepage and download links. python/python-twitter: Fixed deps. python/python-txaio: Updated for version 2.7.1. python/python-urllib3: Updated homepage and download links. python/python-uuid: Updated homepage and download links. python/python-vulndb: Fixed deps. python/python-yenc: Updated homepage and download links. python/python3-decorator: Updated homepage link. python/python3-pycrypto: Update DOWNLOAD url. python/python3-simplegeneric: Updated homepage and download links. python/python3-six: Updated homepage and download links. python/pyutil: Updated homepage and download links. python/rebulk: Fixed deps. python/tempora: Fixed deps. python/txi2p: Fixed deps. python/txsocksx: Fixed deps. sbo/README: Update README. system/Type1_to_OTF: Added (OTF fonts converted from Type1 fonts). system/ack: Updated homepage system/acpi: Updated homepage and download link system/afdko: Fixed SlackBuild. system/aide: Updated homepage and download link system/asbt: Updated for version 1.8.1. system/atop: Updated homepage and download links system/cabextract: Updated homepage and download links system/ccd2iso: Updated homepage and download links system/convmv: Updated homepage and download links system/courier-prime: Updated homepage and download links system/cpu-g: Updated homepage and download links system/cups-bjnp: Updated homepage and download links system/d-feet: Updated for version 0.3.11. system/dfc: Updated homepage and download links system/dtrx: Updated homepage and download links system/eventlog: Updated homepage system/ext4magic: Updated homepage and download links system/firejail: Updated for version 0.9.46. system/fs-uae-arcade: Updated homepage and download links system/fs-uae-launcher: Updated homepage and download links system/fs-uae: Updated homepage and download links system/gconf-editor: Updated homepage and download links system/gimp-help: Updated homepage and download links system/gnome-commander: Updated homepage and download links system/gnome-terminal: Updated homepage and download links system/gnome-vfs: Updated homepage and download links system/gnomint: Updated homepage and download links system/gsmartcontrol: Updated homepage and download links system/hardinfo: Updated homepage and download links system/kbfs: Updated for version 1.0.22_20170512160033. system/kcm_touchpad: Updated homepage system/keybase: Updated for version 1.0.22. system/keylaunch: Updated homepage system/krusader: Updated for version git_20150309_13fa966. system/letsencrypt: Updated for version 0.14.1. system/libnatspec: Updated homepage and download links system/linuxconsoletools: Updated homepage and download links system/lxrandr: Updated homepage and download links system/lxsession: Updated homepage and download links system/lxtask: Updated homepage and download links system/lxterminal: Updated homepage system/ncdu: Updated homepage and download links. system/netatop: Updated homepage and download links. system/nss-pam-ldapd: Updated homepage and download links. system/nvidia-driver: Update DOWNLOAD urls. system/nvidia-kernel: Update DOWNLOAD urls. system/nvidia-legacy304-driver: Update DOWNLOAD urls. system/nvidia-legacy304-kernel: Update DOWNLOAD urls. system/nvidia-legacy340-driver: Update DOWNLOAD urls. system/nvidia-legacy340-kernel: Update DOWNLOAD urls. system/ohsnap: Updated homepage and download links. system/openrc-services: Updated for version 20170517. system/openrc: Updated for version 0.26.2. system/openscap: Updated homepage link. system/ossec-agent: Updated homepage link. system/ossec-local: Updated homepage link. system/ossec-server: Updated homepage link. system/passwordsafe: Updated homepage link. system/pgadmin3: Updated homepage link. system/polyglotman: Updated homepage and download links. system/postgresql: Updated homepage and download links. system/pwgen: Updated homepage and download links. system/qtgzmanager: Updated homepage and download links. system/salt: Updated for version 2016.11.5. system/sbotools: Updated for version 2.4. system/sysdig: Updated for version 0.16.0 system/ttf-bitstream-vera: Updated homepage and download links system/ttf-paratype-pt-fonts: Updated homepage and download links system/vagrant: Updated for version 1.9.5. system/xfe: Updated for version 1.42. system/xosd: Updated for version 2.2.14. system/zpaq: Updated for version 7.15 +--------------------------+ -- 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 rworkman at slackbuilds.org Sat May 20 03:04:27 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 19 May 2017 22:04:27 -0500 Subject: [Slackbuilds-users] All SlackBuilds.org services migrated - Sat May 20 03:04:17 UTC 2017 Message-ID: <20170519220427.66dfc822@home.rlworkman.net> As willysr mentioned in his earlier Updates mail, we have officially migrated all SlackBuilds.org services to virtual machines hosted on our new hardware provided by combined donations from our datacenter ( http://onyxlight.net ), DistroWatch ( http://distrowatch.com ), and members of the SBo community. DNS updates should be propagated to all well-behaved DNS servers by now. If the homepage doesn't look just a little bit different than it used to, then you are not seeing the new machine (hint: there's a note at the top of the page). Please take a look at the contributors page and pass along appropriate appreciation for those individuals and organizations; as I've said before, words can't adequately express just how thankful we are for the support we get from our community. If you are one of the contributors and would like a hyperlink to somewhere with your name, let us know and we'll make that happen. I'd also like to thank the other SBo admins; erik and I did the setup and configuration of the host machine, but ponce handled the lighttpd integration with cgit on the git machine, and rob0 handled the dns and helped troubleshoot some mail issues with the submit form, and pprkut, idlemoor, and willysr helped out with the website migration, database issues, testing (of course), and various other things I've surely forgotten. On that note, there's almost surely someone else who helped out and feels sad that I didn't mention them, so if you are that person, ping me and I'll fix that. As usual, we tested this pretty well before we went live with it, but we probably missed something - let us know if anything seems off. Happy Slacking! -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 kingbeowulf at gmail.com Sat May 20 03:25:59 2017 From: kingbeowulf at gmail.com (Edward Koenig) Date: Fri, 19 May 2017 20:25:59 -0700 Subject: [Slackbuilds-users] All SlackBuilds.org services migrated - Sat May 20 03:04:17 UTC 2017 In-Reply-To: <20170519220427.66dfc822@home.rlworkman.net> References: <20170519220427.66dfc822@home.rlworkman.net> Message-ID: <1CD6AE1F-1E71-4170-98FF-10813ACC0A85@gmail.com> > On May 19, 2017, at 8:04 PM, Robby Workman wrote: > > As willysr mentioned in his earlier Updates mail, we have officially > migrated all SlackBuilds.org services to virtual machines hosted on > our new hardware provided by combined donations from our datacenter > ( http://onyxlight.net ), DistroWatch ( http://distrowatch.com ), > and members of the SBo community. > > DNS updates should be propagated to all well-behaved DNS servers > by now. If the homepage doesn't look just a little bit different > than it used to, then you are not seeing the new machine (hint: > there's a note at the top of the page). > > Please take a look at the contributors page and pass along appropriate > appreciation for those individuals and organizations; as I've said > before, words can't adequately express just how thankful we are > for the support we get from our community. If you are one of the > contributors and would like a hyperlink to somewhere with your > name, let us know and we'll make that happen. > > I'd also like to thank the other SBo admins; erik and I did the > setup and configuration of the host machine, but ponce handled > the lighttpd integration with cgit on the git machine, and > rob0 handled the dns and helped troubleshoot some mail issues > with the submit form, and pprkut, idlemoor, and willysr helped > out with the website migration, database issues, testing (of > course), and various other things I've surely forgotten. On > that note, there's almost surely someone else who helped out > and feels sad that I didn't mention them, so if you are that > person, ping me and I'll fix that. > > As usual, we tested this pretty well before we went live with it, > but we probably missed something - let us know if anything seems > off. > > Happy Slacking! > > -RW > Good job everyone! I can hardly wait to update my scripts. Unfortunately I'll be on a work trip next week (Hawaii, brutal!) do updates might lag a bit. Thanks to all! -Ed From aclemons at runbox.no Sat May 20 04:30:36 2017 From: aclemons at runbox.no (Andrew Clemons) Date: Sat, 20 May 2017 16:30:36 +1200 Subject: [Slackbuilds-users] dropbear maintainence Message-ID: <20170520043034.GA7145@runbox.no> Any objections to my taking over maintenance of dropbear? According to git, Piter's last update to the slackbuild was in 2010 and the last version bump was by Willy last year. I use it and there was a security notice issued[1] with the release a couple of days ago. I have already built this version, but it would be nice to get the script updated in the repository too. [1] ?https://matt.ucc.asn.au/dropbear/CHANGES -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From rworkman at slackbuilds.org Sat May 20 04:51:23 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 19 May 2017 23:51:23 -0500 Subject: [Slackbuilds-users] dropbear maintainence In-Reply-To: <20170520043034.GA7145@runbox.no> References: <20170520043034.GA7145@runbox.no> Message-ID: <20170519235123.25d4226a@home.rlworkman.net> On Sat, 20 May 2017 16:30:36 +1200 Andrew Clemons wrote: > Any objections to my taking over maintenance of dropbear? According to > git, Piter's last update to the slackbuild was in 2010 and the last > version bump was by Willy last year. I use it and there was a security > notice issued[1] with the release a couple of days ago. I have already > built this version, but it would be nice to get the script updated in > the repository too. > > [1] ?https://matt.ucc.asn.au/dropbear/CHANGES Yep, that's fine. -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 sam_web at yahoo.de Sat May 20 08:08:08 2017 From: sam_web at yahoo.de (Marek Srejma) Date: Sat, 20 May 2017 10:08:08 +0200 Subject: [Slackbuilds-users] OpenColorIO: Broken download link Message-ID: Hi, the download link in opencolorio.info (http://sourceforge.net/projects/slackbuildsdirectlinks/files/opencolorio/OpenColorIO-1.0.9.20170426.tar.gz) seems to be broken: > |$ wget > http://sourceforge.net/projects/slackbuildsdirectlinks/files/opencolorio/OpenColorIO-1.0.9.20170426.tar.gz|| > ||URL transformed to HTTPS due to an HSTS policy|| > ||--2017-05-20 10:05:39-- > https://sourceforge.net/projects/slackbuildsdirectlinks/files/opencolorio/OpenColorIO-1.0.9.20170426.tar.gz|| > ||Resolving sourceforge.net (sourceforge.net)... 216.34.181.60|| > ||Connecting to sourceforge.net > (sourceforge.net)|216.34.181.60|:443... connected.|| > ||HTTP request sent, awaiting response... 404 Not Found|| > ||2017-05-20 10:05:40 ERROR 404: Not Found.| Marek From chris.willing at iinet.net.au Sat May 20 08:59:39 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 20 May 2017 18:59:39 +1000 Subject: [Slackbuilds-users] OpenColorIO: Broken download link In-Reply-To: References: Message-ID: <8534b7f3-cc8e-0fde-8275-03c1d7f5a09f@iinet.net.au> On 20/05/17 18:08, Marek Srejma wrote: > Hi, > > the download link in opencolorio.info > (http://sourceforge.net/projects/slackbuildsdirectlinks/files/opencolorio/OpenColorIO-1.0.9.20170426.tar.gz) > seems to be broken: Sorry about that. The link should work now. chris From z.coldplayer at gmail.com Sat May 20 09:57:30 2017 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sat, 20 May 2017 13:57:30 +0400 Subject: [Slackbuilds-users] All SlackBuilds.org services migrated - Sat May 20 03:04:17 UTC 2017 In-Reply-To: <20170519220427.66dfc822@home.rlworkman.net> References: <20170519220427.66dfc822@home.rlworkman.net> Message-ID: Happy Slacking On 20 May 2017 at 07:04, Robby Workman wrote: > As willysr mentioned in his earlier Updates mail, we have officially > migrated all SlackBuilds.org services to virtual machines hosted on > our new hardware provided by combined donations from our datacenter > ( http://onyxlight.net ), DistroWatch ( http://distrowatch.com ), > and members of the SBo community. > > DNS updates should be propagated to all well-behaved DNS servers > by now. If the homepage doesn't look just a little bit different > than it used to, then you are not seeing the new machine (hint: > there's a note at the top of the page). > > Please take a look at the contributors page and pass along appropriate > appreciation for those individuals and organizations; as I've said > before, words can't adequately express just how thankful we are > for the support we get from our community. If you are one of the > contributors and would like a hyperlink to somewhere with your > name, let us know and we'll make that happen. > > I'd also like to thank the other SBo admins; erik and I did the > setup and configuration of the host machine, but ponce handled > the lighttpd integration with cgit on the git machine, and > rob0 handled the dns and helped troubleshoot some mail issues > with the submit form, and pprkut, idlemoor, and willysr helped > out with the website migration, database issues, testing (of > course), and various other things I've surely forgotten. On > that note, there's almost surely someone else who helped out > and feels sad that I didn't mention them, so if you are that > person, ping me and I'll fix that. > > As usual, we tested this pretty well before we went live with it, > but we probably missed something - let us know if anything seems > off. > > Happy Slacking! > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Sat May 20 17:53:00 2017 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 20 May 2017 12:53:00 -0500 Subject: [Slackbuilds-users] egoboo? In-Reply-To: <7de1ec12-ae29-cac3-8dcb-1d3f1b591fa3@gmail.com> References: <7de1ec12-ae29-cac3-8dcb-1d3f1b591fa3@gmail.com> Message-ID: <20170520125300.0a22f59b@shaggy.doo> On Sat, 20 May 2017 08:48:06 -0700 David Melik wrote: > I'd like to try egoboo on Slackware64 14.2 but egoboo has a > segmentation fault... I'm sending this to the -users list in hopes that someone might be willing to take over maintenance. The version in the repo is outdated, which might be the problem. I tried to simply bump it to 2.8.1 but it seems the steps to build it have changed and I'm not really set up to troubleshoot that right now. If anyone is willing to take over, please feel free and submit a new version. Thanks! -- Erik From s.arcus at open-t.co.uk Sat May 20 19:27:01 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sat, 20 May 2017 20:27:01 +0100 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? In-Reply-To: <89603844-447d-d542-f80d-ec27f6792687@open-t.co.uk> References: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> <89603844-447d-d542-f80d-ec27f6792687@open-t.co.uk> Message-ID: <27dc5225-ef5d-2d5d-f204-280fdb4c8cc3@open-t.co.uk> On 17/05/17 18:17, Sebastian Arcus wrote: > > On 17/05/17 16:31, Franzen wrote: >> On 17.05.2017 16:18, Sebastian Arcus wrote: >>> I have been chasing this issue on-and-off for months, and spent a lot of >>> time the last few days on it. I run several Slackware servers with >>> Spamassassin on them, and I noticed a while ago that some don't use DNS >>> blocklists. >> >> Maybe your are using the providers nameserver, beside a lot others, so >> the providers nameserver itself may be blacklistet because of too much >> reqeuests, and therfore gets no(or only sometimes) answers from the >> dns blackalist severs. This also happens if you are using google's dns >> 8.8.8.8 > > Sorry, I should have mentioned it in the original post. I am running > Bind locally in caching/recursive mode. Also, if that would have been > the problem, the queries get flagged as blocked by SpamAssassin in the > message report - so it is quite soon obvious what is going on. I've had > this in the past, before configuring Bind. What I am describing is a > silent issue - no errors, no messages about queries being blocked. And > that is why it took me a while to realise it was a problem, because if > there is no mention in the spam report of dns rbl's - the assumption > would be that the dns queries returned nothing - not that they are not > working altogether. Only by passing the same known spam message through > SpamAssassin on different servers did I realise that the dns rbl's > weren't functional. A follow up on this. I've tested the issue on some more machines, and it seems that it is the Spamassassin version which is the problem. On none of the machines I had with 3.4.1 dns rbl's were working. I have one server with 3.4.0 and dns rbl's *are* working on it. I have upgraded the 7 servers I had with 3.4.1 to 4.0.0 unstable and they all work fine now. They were all Slackware 14.2-current in various states of "freshness" - up to one year old. So if you have Spamassassin 3.4.1 installed on a Slackware box, you might want to check that the dns rbl's are really working - as there were no error messages anywhere on mine. Oh, and for the sake of clarity, I kept all the configs as they were - so it wasn't a config problem. From rworkman at slackbuilds.org Sat May 20 19:36:45 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 20 May 2017 14:36:45 -0500 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? In-Reply-To: <27dc5225-ef5d-2d5d-f204-280fdb4c8cc3@open-t.co.uk> References: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> <89603844-447d-d542-f80d-ec27f6792687@open-t.co.uk> <27dc5225-ef5d-2d5d-f204-280fdb4c8cc3@open-t.co.uk> Message-ID: <20170520143645.5e6fda2d@home.rlworkman.net> On Sat, 20 May 2017 20:27:01 +0100 Sebastian Arcus wrote: > On 17/05/17 18:17, Sebastian Arcus wrote: > > > > On 17/05/17 16:31, Franzen wrote: > >> On 17.05.2017 16:18, Sebastian Arcus wrote: > >>> I have been chasing this issue on-and-off for months, and spent a > >>> lot of time the last few days on it. I run several Slackware > >>> servers with Spamassassin on them, and I noticed a while ago > >>> that some don't use DNS blocklists. > >> > >> Maybe your are using the providers nameserver, beside a lot > >> others, so the providers nameserver itself may be blacklistet > >> because of too much reqeuests, and therfore gets no(or only > >> sometimes) answers from the dns blackalist severs. This also > >> happens if you are using google's dns 8.8.8.8 > > > > Sorry, I should have mentioned it in the original post. I am > > running Bind locally in caching/recursive mode. Also, if that would > > have been the problem, the queries get flagged as blocked by > > SpamAssassin in the message report - so it is quite soon obvious > > what is going on. I've had this in the past, before configuring > > Bind. What I am describing is a silent issue - no errors, no > > messages about queries being blocked. And that is why it took me a > > while to realise it was a problem, because if there is no mention > > in the spam report of dns rbl's - the assumption would be that the > > dns queries returned nothing - not that they are not working > > altogether. Only by passing the same known spam message through > > SpamAssassin on different servers did I realise that the dns rbl's > > weren't functional. > > A follow up on this. I've tested the issue on some more machines, and > it seems that it is the Spamassassin version which is the problem. On > none of the machines I had with 3.4.1 dns rbl's were working. I have > one server with 3.4.0 and dns rbl's *are* working on it. I have > upgraded the 7 servers I had with 3.4.1 to 4.0.0 unstable and they > all work fine now. They were all Slackware 14.2-current in various > states of "freshness" - up to one year old. So if you have > Spamassassin 3.4.1 installed on a Slackware box, you might want to > check that the dns rbl's are really working - as there were no error > messages anywhere on mine. Oh, and for the sake of clarity, I kept > all the configs as they were - so it wasn't a config problem. Good catch nonetheless :-) -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 willysr at slackbuilds.org Sat May 20 19:56:21 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 May 2017 02:56:21 +0700 Subject: [Slackbuilds-users] egoboo? In-Reply-To: <20170520125300.0a22f59b@shaggy.doo> References: <7de1ec12-ae29-cac3-8dcb-1d3f1b591fa3@gmail.com> <20170520125300.0a22f59b@shaggy.doo> Message-ID: > David Melik wrote: > >> I'd like to try egoboo on Slackware64 14.2 but egoboo has a >> segmentation fault... > > I'm sending this to the -users list in hopes that someone might be > willing to take over maintenance. The version in the repo is outdated, > which might be the problem. I tried to simply bump it to 2.8.1 but it > seems the steps to build it have changed and I'm not really set up to > troubleshoot that right now. > > If anyone is willing to take over, please feel free and submit a new > version. Thanks! Hi David can you try this changes? https://git.slackbuilds.org/slackbuilds/log/?h=egoboo-review -- 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 s.arcus at open-t.co.uk Sun May 21 04:34:32 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 21 May 2017 05:34:32 +0100 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? In-Reply-To: <20170520143645.5e6fda2d@home.rlworkman.net> References: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> <89603844-447d-d542-f80d-ec27f6792687@open-t.co.uk> <27dc5225-ef5d-2d5d-f204-280fdb4c8cc3@open-t.co.uk> <20170520143645.5e6fda2d@home.rlworkman.net> Message-ID: On 20/05/17 20:36, Robby Workman wrote: > On Sat, 20 May 2017 20:27:01 +0100 > Sebastian Arcus wrote: > >> On 17/05/17 18:17, Sebastian Arcus wrote: >>> >>> On 17/05/17 16:31, Franzen wrote: >>>> On 17.05.2017 16:18, Sebastian Arcus wrote: >>>>> I have been chasing this issue on-and-off for months, and spent a >>>>> lot of time the last few days on it. I run several Slackware >>>>> servers with Spamassassin on them, and I noticed a while ago >>>>> that some don't use DNS blocklists. >>>> >>>> Maybe your are using the providers nameserver, beside a lot >>>> others, so the providers nameserver itself may be blacklistet >>>> because of too much reqeuests, and therfore gets no(or only >>>> sometimes) answers from the dns blackalist severs. This also >>>> happens if you are using google's dns 8.8.8.8 >>> >>> Sorry, I should have mentioned it in the original post. I am >>> running Bind locally in caching/recursive mode. Also, if that would >>> have been the problem, the queries get flagged as blocked by >>> SpamAssassin in the message report - so it is quite soon obvious >>> what is going on. I've had this in the past, before configuring >>> Bind. What I am describing is a silent issue - no errors, no >>> messages about queries being blocked. And that is why it took me a >>> while to realise it was a problem, because if there is no mention >>> in the spam report of dns rbl's - the assumption would be that the >>> dns queries returned nothing - not that they are not working >>> altogether. Only by passing the same known spam message through >>> SpamAssassin on different servers did I realise that the dns rbl's >>> weren't functional. >> >> A follow up on this. I've tested the issue on some more machines, and >> it seems that it is the Spamassassin version which is the problem. On >> none of the machines I had with 3.4.1 dns rbl's were working. I have >> one server with 3.4.0 and dns rbl's *are* working on it. I have >> upgraded the 7 servers I had with 3.4.1 to 4.0.0 unstable and they >> all work fine now. They were all Slackware 14.2-current in various >> states of "freshness" - up to one year old. So if you have >> Spamassassin 3.4.1 installed on a Slackware box, you might want to >> check that the dns rbl's are really working - as there were no error >> messages anywhere on mine. Oh, and for the sake of clarity, I kept >> all the configs as they were - so it wasn't a config problem. > > > Good catch nonetheless :-) Thank you! It would be really interesting if others could check their machines and report here if they are seeing the same issue at their end. To test, I just passed a mail message with a known spammy URL (detected as a spammy URL on a good machine) through spamc - and if the spam report didn't mention anything about any dns rbl test, I knew Spamassassin wasn't working correctly. From s.arcus at open-t.co.uk Sun May 21 04:37:59 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 21 May 2017 05:37:59 +0100 Subject: [Slackbuilds-users] All SlackBuilds.org services migrated - Sat May 20 03:04:17 UTC 2017 In-Reply-To: <20170519220427.66dfc822@home.rlworkman.net> References: <20170519220427.66dfc822@home.rlworkman.net> Message-ID: On 20/05/17 04:04, Robby Workman wrote: > As willysr mentioned in his earlier Updates mail, we have officially > migrated all SlackBuilds.org services to virtual machines hosted on > our new hardware provided by combined donations from our datacenter > ( http://onyxlight.net ), DistroWatch ( http://distrowatch.com ), > and members of the SBo community. > > DNS updates should be propagated to all well-behaved DNS servers > by now. If the homepage doesn't look just a little bit different > than it used to, then you are not seeing the new machine (hint: > there's a note at the top of the page). > > Please take a look at the contributors page and pass along appropriate > appreciation for those individuals and organizations; as I've said > before, words can't adequately express just how thankful we are > for the support we get from our community. If you are one of the > contributors and would like a hyperlink to somewhere with your > name, let us know and we'll make that happen. > > I'd also like to thank the other SBo admins; erik and I did the > setup and configuration of the host machine, but ponce handled > the lighttpd integration with cgit on the git machine, and > rob0 handled the dns and helped troubleshoot some mail issues > with the submit form, and pprkut, idlemoor, and willysr helped > out with the website migration, database issues, testing (of > course), and various other things I've surely forgotten. On > that note, there's almost surely someone else who helped out > and feels sad that I didn't mention them, so if you are that > person, ping me and I'll fix that. > > As usual, we tested this pretty well before we went live with it, > but we probably missed something - let us know if anything seems > off. > > Happy Slacking! Thank you everyone involved and specially the admins, who work hard to keep SBo going! From davidnchmelik at gmail.com Sun May 21 04:26:51 2017 From: davidnchmelik at gmail.com (David Melik) Date: Sat, 20 May 2017 21:26:51 -0700 Subject: [Slackbuilds-users] egoboo? In-Reply-To: References: <7de1ec12-ae29-cac3-8dcb-1d3f1b591fa3@gmail.com> <20170520125300.0a22f59b@shaggy.doo> Message-ID: On 05/20/2017 12:56 PM, Willy Sudiarto Raharjo wrote: >> David Melik wrote: >> >>> I'd like to try egoboo on Slackware64 14.2 but egoboo has a >>> segmentation fault... >> >> I'm sending this to the -users list in hopes that someone might be >> willing to take over maintenance. The version in the repo is outdated, >> which might be the problem. I tried to simply bump it to 2.8.1 but it >> seems the steps to build it have changed and I'm not really set up to >> troubleshoot that right now. >> >> If anyone is willing to take over, please feel free and submit a new >> version. Thanks! > > Hi David > > can you try this changes? > https://git.slackbuilds.org/slackbuilds/log/?h=egoboo-review d at cosmos:~/egoboo$ sudo egoboo.SlackBuild [...] patching file src/game/game.c Hunk #1 FAILED at 2052 (different line endings). 1 out of 1 hunk FAILED -- saving rejects to file src/game/game.c.rej d at cosmos:~/egoboo$ From willysr at slackbuilds.org Sun May 21 05:13:47 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 21 May 2017 12:13:47 +0700 Subject: [Slackbuilds-users] egoboo? In-Reply-To: References: <7de1ec12-ae29-cac3-8dcb-1d3f1b591fa3@gmail.com> <20170520125300.0a22f59b@shaggy.doo> Message-ID: >> https://git.slackbuilds.org/slackbuilds/log/?h=egoboo-review > > d at cosmos:~/egoboo$ sudo egoboo.SlackBuild > [...] > patching file src/game/game.c > Hunk #1 FAILED at 2052 (different line endings). > 1 out of 1 hunk FAILED -- saving rejects to file src/game/game.c.rej > d at cosmos:~/egoboo$ Hi David can you try again? or simply add --binary in the patch line 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 davidnchmelik at gmail.com Sun May 21 07:23:55 2017 From: davidnchmelik at gmail.com (David Melik) Date: Sun, 21 May 2017 00:23:55 -0700 Subject: [Slackbuilds-users] egoboo? In-Reply-To: References: <7de1ec12-ae29-cac3-8dcb-1d3f1b591fa3@gmail.com> <20170520125300.0a22f59b@shaggy.doo> Message-ID: <90df7325-62a0-53b5-c455-5b7f0df73eb8@gmail.com> On 05/20/2017 09:26 PM, David Melik wrote: > On 05/20/2017 12:56 PM, Willy Sudiarto Raharjo wrote: >>> David Melik >>> >>> wrote: >>> >>>> I'd like to try egoboo on Slackware64 14.2 but egoboo has a >>>> segmentation fault... >>> >>> I'm sending this to the -users list in hopes that someone might be >>> willing to take over maintenance. The version in the repo is outdated, >>> which might be the problem. I tried to simply bump it to 2.8.1 but it >>> seems the steps to build it have changed and I'm not really set up to >>> troubleshoot that right now. >>> >>> If anyone is willing to take over, please feel free and submit a new >>> version. Thanks! >> >> Hi David >> >> can you try this changes? >> https://git.slackbuilds.org/slackbuilds/log/?h=egoboo-review > > d at cosmos:~/egoboo$ sudo egoboo.SlackBuild > [...] > patching file src/game/game.c > Hunk #1 FAILED at 2052 (different line endings). > 1 out of 1 hunk FAILED -- saving rejects to file src/game/game.c.rej > d at cosmos:~/egoboo$ I don't normally report something until I've seen it a couple/few times. I changed that line to the below. patch --binary -p1 < $CWD/keyboard_directions.patch Then the exact same thing (same file, same error and place) happened. From dchmelik at gmail.com Sun May 21 09:01:07 2017 From: dchmelik at gmail.com (David Melik) Date: Sun, 21 May 2017 02:01:07 -0700 Subject: [Slackbuilds-users] egoboo? In-Reply-To: <841a6c28-f2ba-53e3-eecd-f63272261d15@slackbuilds.org> References: <7de1ec12-ae29-cac3-8dcb-1d3f1b591fa3@gmail.com> <20170520125300.0a22f59b@shaggy.doo> <90df7325-62a0-53b5-c455-5b7f0df73eb8@gmail.com> <841a6c28-f2ba-53e3-eecd-f63272261d15@slackbuilds.org> Message-ID: <8f8cd388-8cc1-5863-afa8-99de7a466057@gmail.com> On 05/21/2017 01:38 AM, Willy Sudiarto Raharjo wrote: >> I don't normally report something until I've seen it a couple/few times. >> I changed that line to the below. >> >> patch --binary -p1 < $CWD/keyboard_directions.patch >> >> Then the exact same thing (same file, same error and place) happened. > Hm... i guess git changed it during commit due to the original source is > (probably) written in Windows and Linux environment. > i gzip the patch for now and see if it works in your environment > > on my VM, it works (before and after) committing now. Previously, it > failed to build after i ran git commit. > > egoboo-2.8.1/src/run_astyle.sh > patching file src/game/game.c > make -C ./enet all > make[1]: Entering directory '/tmp/SBo/egoboo-2.8.1/src/enet' > gcc -Os -Iinclude -c -o host.o host.c > gcc -Os -Iinclude -c -o list.o list.c > gcc -Os -Iinclude -c -o memory.o memory.c > gcc -Os -Iinclude -c -o packet.o packet.c > gcc -Os -Iinclude -c -o peer.o peer.c > gcc -Os -Iinclude -c -o protocol.o protocol.c > gcc -Os -Iinclude -c -o unix.o unix.c > > please have another look on the branch > https://git.slackbuilds.org/slackbuilds/log/?h=egoboo-review After your recent email to me (off SlackBuilds-users for some reason,) I got the game to start... haven't gotten into trying it (going to see if some friends will play it or others in SBo games list.) From slackalaxy at gmail.com Sun May 21 09:52:27 2017 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 21 May 2017 12:52:27 +0300 Subject: [Slackbuilds-users] slack-wallpapers Message-ID: hi, I am giving the maintenance of slack-wallpapers to Skaendo from LQ. -petar From gerardo.zamudio at linux.com Sun May 21 23:27:51 2017 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sun, 21 May 2017 18:27:51 -0500 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? In-Reply-To: References: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> <89603844-447d-d542-f80d-ec27f6792687@open-t.co.uk> <27dc5225-ef5d-2d5d-f204-280fdb4c8cc3@open-t.co.uk> <20170520143645.5e6fda2d@home.rlworkman.net> Message-ID: On 05/20/2017 11:34 PM, Sebastian Arcus wrote: > > Thank you! It would be really interesting if others could check their > machines and report here if they are seeing the same issue at their end. > To test, I just passed a mail message with a known spammy URL (detected > as a spammy URL on a good machine) through spamc - and if the spam > report didn't mention anything about any dns rbl test, I knew > Spamassassin wasn't working correctly. > I use Amavis as an interface between SpamAssassin and Postfix. No issues here slack:~ # tail /var/log/maillog May 21 17:54:06 mail postfix/smtpd[15930]: NOQUEUE: reject: RCPT from static-IP_ADDRESS.bstnma.fios.verizon.net[IP_ADDRESS]: 554 5.7.1 Service unavailable; Client host [IP_ADDRESS] blocked using sbl.spamhaus.org; https://www.spamhaus.org/sbl/query/SBLCSS; from= to= proto=ESMTP helo= slack:~ # date Sun May 21 18:12:22 EST 2017 Packages are built from SBo, including Perl modules. slack:~ # ls -l /var/log/packages/ | grep -E "amavis|spam|postfix" -rw-r--r-- 1 root root 5547 Dec 30 22:59 amavisd-new-2.11.0-noarch-1_SBo -rw-r--r-- 1 root root 15453 Mar 16 12:22 postfix-3.2.0-x86_64-1_SBo -rw-r--r-- 1 root root 14088 Dec 30 20:10 spamassassin-3.4.1-x86_64-1_SBo Regards Gerardo Zamudio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Mon May 22 05:55:17 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 21 May 2017 23:55:17 -0600 Subject: [Slackbuilds-users] re-package a java program? Message-ID: Any guidelines on how to repackage a java program? Any existing buildscript examples? or anyone willing to do it for me... I'll maintain it afterwards. this is the intended victim: http://www.st.com/en/embedded-software/stsw-link007.html -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Mon May 22 06:09:39 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 22 May 2017 01:09:39 -0500 Subject: [Slackbuilds-users] re-package a java program? In-Reply-To: References: Message-ID: <20170522010939.6ea78d4a@home.rlworkman.net> On Sun, 21 May 2017 23:55:17 -0600 Fernando Lopez wrote: > Any guidelines on how to repackage a java program? Any existing > buildscript examples? > or anyone willing to do it for me... I'll maintain it afterwards. > > this is the intended victim: > http://www.st.com/en/embedded-software/stsw-link007.html Well, I was going to take a shot at it but then it wanted me to register, so nope. That said, the best way to it will likely be to package it in /opt, e.g. /opt/stsw/ or some such. -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 fernando.lopezjr at gmail.com Mon May 22 06:12:19 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 22 May 2017 00:12:19 -0600 Subject: [Slackbuilds-users] re-package a java program? In-Reply-To: <20170522010939.6ea78d4a@home.rlworkman.net> References: <20170522010939.6ea78d4a@home.rlworkman.net> Message-ID: oh shit, yeah... i forgot about registration... can it be hosted somewhere else? here you go: https://www.dropbox.com/s/zsg9akksjk29dc7/en.stsw-link007.zip?dl=0 On Mon, May 22, 2017 at 12:09 AM, Robby Workman wrote: > On Sun, 21 May 2017 23:55:17 -0600 > Fernando Lopez wrote: > > > Any guidelines on how to repackage a java program? Any existing > > buildscript examples? > > or anyone willing to do it for me... I'll maintain it afterwards. > > > > this is the intended victim: > > http://www.st.com/en/embedded-software/stsw-link007.html > > > Well, I was going to take a shot at it but then it wanted > me to register, so nope. > > That said, the best way to it will likely be to package it > in /opt, e.g. /opt/stsw/ or some such. > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dchmelik at gmail.com Mon May 22 06:18:25 2017 From: dchmelik at gmail.com (David Melik) Date: Sun, 21 May 2017 23:18:25 -0700 Subject: [Slackbuilds-users] questions for my larn SlackBuild update, game security, SlackBuild licensing Message-ID: I maintain the larn (and some other) roguelike game package and recently submitted a new version I accidentally uploaded an old revision, so must redo (actually I do have a working version, but there are more issues now.) However, I switched from an unofficial port ( https://github.com/Nebula-Mechanica/larn-linux/ ) to the official source code ( https://github.com/atsb/RL_M .) The unofficial version has a poorly-installed wrapper script (they don't link it to /usr/games/larn... the user just has to find and run larn.sh, not larn binary, though they can do that too) which I no longer use, so we may no longer need the larn-fixups.patch someone on SBo team wrote and added, or it will be different, in ways I don't know yet. The official code doesn't even 'make install,' and has a data directory, but no wrapper script linked to in /usr/games to go from there to that directory. I wrote my own wrapper script (maybe not that great either) for the official code, but it seems the earlier, unofficial one uses some environment variables that may make things easier. So, could some people more experienced with make, wrapper scripts, running & patching games with all these environment variables, etc., take a look at the unofficial and/or official, and my new version, and suggest what to do next for a wrapper and/or update larn-fixups.patch (if even needed now)? My new version is http://davidchmelik.com/homepage/math/slackbuilds/games/larn.tar.gz , which builds & runs fine for me, and if anyone at SBo is willing to any of that with my new update, for an official update in SBo, that's fine with me (just preferably let me know so I download any changes.) I'm just not sure what to do changing from the unofficial to official version, both of which seem to have some advantages and disadvantages I'm not used to dealing with. Also, should I set gid:uid games:games in all my game configure scripts (and maybe similar for graphics/academic/library software) for security? Also, what do people think of that guy who submits scripts to SBo (meikamp?) but says that, with the addition of GPL not having to be included, their scripts are (optionally) under GPL? Then they're shorter, but I'm not sure it really works with GPL, though I'd probably prefer to do it this way. D http://www.cwu.edu/~melikd/ From s.arcus at open-t.co.uk Mon May 22 07:28:22 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Mon, 22 May 2017 08:28:22 +0100 Subject: [Slackbuilds-users] Spamassassin from SBo - broken DNS RBL filtering? In-Reply-To: References: <9a26dd4f-2bf3-5ea1-ce99-8d61fc574ca2@open-t.co.uk> <54da5186-7927-1090-91d8-6ebf751b28fc@schoepfer.info> <89603844-447d-d542-f80d-ec27f6792687@open-t.co.uk> <27dc5225-ef5d-2d5d-f204-280fdb4c8cc3@open-t.co.uk> <20170520143645.5e6fda2d@home.rlworkman.net> Message-ID: <80afe402-966c-437c-4554-80555d7992ee@open-t.co.uk> On 22/05/17 00:27, Gerardo Zamudio wrote: > > > On 05/20/2017 11:34 PM, Sebastian Arcus wrote: >> >> Thank you! It would be really interesting if others could check their >> machines and report here if they are seeing the same issue at their end. >> To test, I just passed a mail message with a known spammy URL (detected >> as a spammy URL on a good machine) through spamc - and if the spam >> report didn't mention anything about any dns rbl test, I knew >> Spamassassin wasn't working correctly. >> > > > I use Amavis as an interface between SpamAssassin and Postfix. No issues > here > > slack:~ # tail /var/log/maillog > May 21 17:54:06 mail postfix/smtpd[15930]: NOQUEUE: reject: RCPT from > static-IP_ADDRESS.bstnma.fios.verizon.net[IP_ADDRESS]: 554 5.7.1 Service > unavailable; Client host [IP_ADDRESS] blocked using sbl.spamhaus.org; > https://www.spamhaus.org/sbl/query/SBLCSS; from= > to= proto=ESMTP helo= I found that dns rbl's didn't work correctly in relation to spam URl's found inside emails. Above it seems the rejection is based on the originating host, unless I'm misreading the log? From korgie at gmail.com Mon May 22 08:08:29 2017 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Mon, 22 May 2017 11:08:29 +0300 Subject: [Slackbuilds-users] re-package a java program? In-Reply-To: References: Message-ID: <73396BCF-004E-4109-B216-17C86E61EECE@gmail.com> 22 ??? 2017, 8:55 ??, ?/? Fernando Lopez ??????: > Any guidelines on how to repackage a java program? Any existing buildscript examples? Josm is helpful? > or anyone willing to do it for me... I'll maintain it afterwards. > > this is the intended victim: > http://www.st.com/en/embedded-software/stsw-link007.html > > -- > > ------------ > Regards, > Fernando Lopez Jr. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Mon May 22 19:33:44 2017 From: thedoogster at gmail.com (Doogster) Date: Mon, 22 May 2017 12:33:44 -0700 Subject: [Slackbuilds-users] "Go back and enter a valid email address" Message-ID: I just tried to submit an update to the vulksansdk SlackBuild. SlackBuilds.org rejected it with the following message: "Can not connect to E-Mail server (gmail.com). Go back and enter a valid E-Mail address." I did enter my email address (this one) correctly. From rworkman at slackbuilds.org Mon May 22 19:59:22 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 22 May 2017 14:59:22 -0500 Subject: [Slackbuilds-users] "Go back and enter a valid email address" In-Reply-To: References: Message-ID: <20170522145922.7d9a05ce@home.rlworkman.net> On Mon, 22 May 2017 12:33:44 -0700 Doogster wrote: > I just tried to submit an update to the vulksansdk SlackBuild. > SlackBuilds.org rejected it with the following message: > > "Can not connect to E-Mail server (gmail.com). > Go back and enter a valid E-Mail address." > > I did enter my email address (this one) correctly. Try again; problem fixed, I think. -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 slackbuilds at schoepfer.info Mon May 22 20:26:09 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 22 May 2017 22:26:09 +0200 Subject: [Slackbuilds-users] "Go back and enter a valid email address" In-Reply-To: <20170522145922.7d9a05ce@home.rlworkman.net> References: <20170522145922.7d9a05ce@home.rlworkman.net> Message-ID: <4d71963f877229df715ee1e6267c485d@schoepfer.info> On 2017-05-22 21:59, Robby Workman wrote: > On Mon, 22 May 2017 12:33:44 -0700 > Doogster wrote: > >> I just tried to submit an update to the vulksansdk SlackBuild. >> SlackBuilds.org rejected it with the following message: >> >> "Can not connect to E-Mail server (gmail.com). >> Go back and enter a valid E-Mail address." >> >> I did enter my email address (this one) correctly. > > > Try again; problem fixed, I think. In case this hits more maintainers As the ip has changed, i had to whitelist 208.94.237.149 to not get greylisted by my mta, to get my submission accepted. Johannes From atelszewski at gmail.com Tue May 23 19:33:12 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 23 May 2017 21:33:12 +0200 Subject: [Slackbuilds-users] Ready queue empty, but no public update Message-ID: <1cf29b64-5e7e-7bb6-5df6-dc2c2d1b34bd@gmail.com> Hi, FYI, the ready queue is empty, but there was no public update. Or am I missing something? ;-) -- Best regards, Andrzej Telszewski From thedoogster at gmail.com Tue May 23 19:39:33 2017 From: thedoogster at gmail.com (Doogster) Date: Tue, 23 May 2017 12:39:33 -0700 Subject: [Slackbuilds-users] Ready queue empty, but no public update In-Reply-To: <1cf29b64-5e7e-7bb6-5df6-dc2c2d1b34bd@gmail.com> References: <1cf29b64-5e7e-7bb6-5df6-dc2c2d1b34bd@gmail.com> Message-ID: Yeah, what happened to the vulkansdk update I submitted last night? On Tue, May 23, 2017 at 12:33 PM, Andrzej Telszewski wrote: > Hi, > > FYI, the ready queue is empty, but there was no public update. > Or am I missing something? ;-) > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Tue May 23 19:41:47 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 24 May 2017 02:41:47 +0700 Subject: [Slackbuilds-users] Ready queue empty, but no public update In-Reply-To: References: <1cf29b64-5e7e-7bb6-5df6-dc2c2d1b34bd@gmail.com> Message-ID: <86bb6992-acbf-42fb-c873-ccc28defae21@slackbuilds.org> > Yeah, what happened to the vulkansdk update I submitted last night? It's still listed in git, don't worry :) all ready/pending submission are still in place, just not showing up (for now). Once sorted, it will be visible just like it used to be. -- 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 rworkman at slackbuilds.org Tue May 23 20:18:12 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 23 May 2017 15:18:12 -0500 Subject: [Slackbuilds-users] Ready queue empty, but no public update In-Reply-To: <86bb6992-acbf-42fb-c873-ccc28defae21@slackbuilds.org> References: <1cf29b64-5e7e-7bb6-5df6-dc2c2d1b34bd@gmail.com> <86bb6992-acbf-42fb-c873-ccc28defae21@slackbuilds.org> Message-ID: <20170523151812.2623bd88@home.rlworkman.net> On Wed, 24 May 2017 02:41:47 +0700 Willy Sudiarto Raharjo wrote: > > Yeah, what happened to the vulkansdk update I submitted last > > night? > > It's still listed in git, don't worry :) > all ready/pending submission are still in place, just not showing up > (for now). Once sorted, it will be visible just like it used to be. It's fixed now; sorry - that was fallout from the previous reboot of the www VM that didn't go exactly according to plan. I deleted a shared mount because I didn't remember why it was there (perhaps the saddest part is that I didn't bother to consult the /etc/ChangeLog that has meticulous notes about why it's there) :-) -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 atelszewski at gmail.com Tue May 23 21:15:22 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 23 May 2017 23:15:22 +0200 Subject: [Slackbuilds-users] Ready queue empty, but no public update In-Reply-To: <20170523151812.2623bd88@home.rlworkman.net> References: <1cf29b64-5e7e-7bb6-5df6-dc2c2d1b34bd@gmail.com> <86bb6992-acbf-42fb-c873-ccc28defae21@slackbuilds.org> <20170523151812.2623bd88@home.rlworkman.net> Message-ID: On 23/05/17 22:18, Robby Workman wrote: > On Wed, 24 May 2017 02:41:47 +0700 > Willy Sudiarto Raharjo wrote: > >>> Yeah, what happened to the vulkansdk update I submitted last >>> night? >> >> It's still listed in git, don't worry :) >> all ready/pending submission are still in place, just not showing up >> (for now). Once sorted, it will be visible just like it used to be. > > > It's fixed now; sorry - that was fallout from the previous reboot > of the www VM that didn't go exactly according to plan. > I deleted a shared mount because I didn't remember why it was > there (perhaps the saddest part is that I didn't bother to > consult the /etc/ChangeLog that has meticulous notes about why > it's there) :-) > > -RW > Thanks ;-) -- Best regards, Andrzej Telszewski From aw.lukomski at gmail.com Tue May 23 20:51:12 2017 From: aw.lukomski at gmail.com (Adam Lukomski) Date: Tue, 23 May 2017 22:51:12 +0200 Subject: [Slackbuilds-users] problem with uploading libccd to the pending queue Message-ID: On 21.05 I uploaded libccd and fcl (which requires libccd) to the pending queue, but after a couple of minutes I realised the md5 in libccd was wrong, so I removed the submission libccd. The slackbuilds.org/remove shouted at me that the fcl depends on it and it cannot be removed but ... libccd got removed. I tried uploading it again but I keep getting File exists; a submission by the name 'libccd' is already pending approval. ... but it's not visible anywhere in the pending/approved. Is it normal or a bug caused by me? I removed fcl too, but this didn't help. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Tue May 23 21:41:40 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 23 May 2017 16:41:40 -0500 Subject: [Slackbuilds-users] problem with uploading libccd to the pending queue In-Reply-To: References: Message-ID: <20170523164140.564a1e41@home.rlworkman.net> On Tue, 23 May 2017 22:51:12 +0200 Adam Lukomski wrote: > On 21.05 I uploaded libccd and fcl (which requires libccd) to the > pending queue, but after a couple of minutes I realised the md5 in > libccd was wrong, so I removed the submission libccd. The > slackbuilds.org/remove shouted at me that the fcl depends on it and > it cannot be removed but ... libccd got removed. I tried uploading it > again but I keep getting > > File exists; a submission by the name 'libccd' is already pending > approval. > > ... but it's not visible anywhere in the pending/approved. Is it > normal or a bug caused by me? > I removed fcl too, but this didn't help. Not sure what happened, but I removed it from the pending database, so you should be able to upload a new one now. -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 aw.lukomski at gmail.com Tue May 23 21:47:01 2017 From: aw.lukomski at gmail.com (Adam Lukomski) Date: Tue, 23 May 2017 23:47:01 +0200 Subject: [Slackbuilds-users] problem with uploading libccd to the pending queue Message-ID: Everything is working now, thanks. On Tue, May 23, 2017 at 11:41 PM, Robby Workman wrote: > On Tue, 23 May 2017 22:51:12 +0200 > Adam Lukomski wrote: > > > On 21.05 I uploaded libccd and fcl (which requires libccd) to the > > pending queue, but after a couple of minutes I realised the md5 in > > libccd was wrong, so I removed the submission libccd. The > > slackbuilds.org/remove shouted at me that the fcl depends on it and > > it cannot be removed but ... libccd got removed. I tried uploading it > > again but I keep getting > > > > File exists; a submission by the name 'libccd' is already pending > > approval. > > > > ... but it's not visible anywhere in the pending/approved. Is it > > normal or a bug caused by me? > > I removed fcl too, but this didn't help. > > > Not sure what happened, but I removed it from the pending database, > so you should be able to upload a new one now. > > -RW > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Wed May 24 05:59:39 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 24 May 2017 15:59:39 +1000 Subject: [Slackbuilds-users] VLC subtitle handling vulnerability Message-ID: Just a heads up (maintainer cc'd in) about a vulnerability found in VLCs handling of subtitles: http://blog.checkpoint.com/2017/05/23/hacked-in-translation/ It's fixed in the latest 2.2.5.1 release. The build on SBo seems to be a development version though, so I'm not sure if this is relevant or not. -- Dave From chris.willing at linux.com Wed May 24 10:28:32 2017 From: chris.willing at linux.com (Christoph Willing) Date: Wed, 24 May 2017 20:28:32 +1000 Subject: [Slackbuilds-users] VLC subtitle handling vulnerability In-Reply-To: References: Message-ID: <72faf34d-be67-2d68-3767-234fef1a7f6a@linux.com> On 24/05/17 15:59, David O'Shaughnessy wrote: > Just a heads up (maintainer cc'd in) about a vulnerability found in VLCs > handling of subtitles: > > http://blog.checkpoint.com/2017/05/23/hacked-in-translation/ > > It's fixed in the latest 2.2.5.1 release. The build on SBo seems to be a > development version though, so I'm not sure if this is relevant or not. > Thanks for the report Dave. I've just pushed a new version that addresses the vulnerability (thanks to Matteo for the updated source tarball). I think we generally frown on using development versions but the official releases (including 2.2.5.1) don't yet support the version of ffmpeg we have at SBo. chris From s.arcus at open-t.co.uk Wed May 24 12:49:11 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 24 May 2017 13:49:11 +0100 Subject: [Slackbuilds-users] Libvirt package - small change to /etc/rc.d/rc.libvirt In-Reply-To: <20170505095008.1e130300@home.rlworkman.net> References: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> <20170505095008.1e130300@home.rlworkman.net> Message-ID: On 05/05/17 15:50, Robby Workman wrote: > On Thu, 4 May 2017 12:55:03 +0100 > Sebastian Arcus wrote: > >> I have a small change to suggest for the /etc/rc.d/rc.libvirt script. >> The script at the moment does a 'virsh shutdown ' on all >> running guests, and then, after waiting only 40 seconds, it destroys >> all guests which are still running. I think in most circumstances >> this is very likely to lead to corrupted guests because: >> >> 1. Many guests will take longer than 40 seconds to shutdown, >> specially if they are Windows guests. >> 2. Some Windows guests might be trying to install updates on >> shutdown, which can take 10, 20 or even 60 minutes. >> 3. If there are a number of guests running and the host is busy >> trying to shut them all down at the same time, even Linux guests will >> still be in the process of shutting down after 40 seconds. >> 4. If it is a setup where users connect to guests remotely, it is >> possible that people are in the middle of doing work which would be >> lost. >> >> Would it maybe be safer to do a 'virsh managedsave ' on >> every running guest instead? I can see many advantages to this >> option, including: >> >> 1. It is much less likely for users who might use the guests remotely >> to loose work, as the machine state is suspended. >> >> 2. Guests stopped with 'managedsave' will start fine with the 'start' >> command - so no need to change any settings anywhere else, and the >> 'autostart' feature of libvirt will continue to work fine. >> >> 2. On my server, the 'managedsave' operation takes around 20 seconds >> per guest, and it is more predictable in duration than a 'shutdown', >> which depends on the OS in the guest, if it is installing updates etc. >> >> 4. The 'managedsave' command doesn't return immediately, so we can >> wait for each guest in turn and know when it is done. Or ampersand >> could be used on the command, and then just do a looped check on >> 'virsh list' lower down, waiting for the 'managedsave' on all guests >> to finish. >> >> 5. If my understanding is correct, the 'shutdown' command depends on >> the guest implementing correctly and acting on ACPI commands, while a >> 'managedsave' seems to be under the complete control of libvirt - >> which means the script would work correctly out of the box with a >> much wider variety of OS's and configurations on the guest side. >> >> If necessary, I suppose the script could also implement a >> 'reboot_guests' separate command, for people to use it to reboot all >> running guests - as the "stop" command wouldn't be performing a full >> shutdown any more. >> >> Just a suggestion in case it helps. I'm already very happy with the >> current script, as I used to have to write my own to shutdown >> kvm/qemu guests :-) > > > This seems like a reasonable change. Can you push it to a git > repo/branch somewhere and send me a link, or else send me a > patch(set) to merge? With some delay, please find attached the suggested changes to the rc.libvirt script. I have made the following the amendments: 1. Increased the default timeout to 5 minutes (300 seconds). I think guests should be destroyed only as a last resort - as the risk of corrupting data is very high. If a quicker shutdown is needed - one should look at optimising or troubleshooting things, not destroying guests. I am half-tempted to suggest increasing this to 10 minutes actually. 2. Change the default behaviour of the "stop" option to do a managedsave on all running and paused guests - as this is safer for all guest operating systems - and the duration is more predictable (no Windows automatic updates to install during shutdown etc.) 3. Added a guests_shutdown option, for those preferring to do a full shutdown instead of a managedsave (not enough space on hdd to save ram images, for example). So rc.local_shutdown would contain: /etc/rc.d/rc.libvirt guests_shutdown /etc/rc.d/rc.libvirt stop 4. Added a guests_reboot option, to reboot all running guests. I find this really useful, as, for example, Windows guests need regular reboots to stop them from going bananas - so an option to reboot all of them at once seems like a useful addition. This doesn't wait and doesn't have a timeout - just issues the command and exits. The idea is that this wouldn't be used during a reboot, so there is no need to check when the command has finished executing. Note: when issuing the managedsave command, the guests go first through a 'paused' state, then they show up as 'shut off' in virsh --list. Thus it is impossible to tell between the guests which were already paused initially, and the ones in transition to the managedsave state, while waiting for the command to complete. Because of this, the only way to proceed is to issue a 'managedsave' on both running and already paused guests. On the other hand, 'guests_shutdown' only acts on running guests - an ACPI shutdown command is unlikely to be acted on by a paused guest anyway. I also suggest adding the following notes to libvirt-info: "The enclosed rc.libvirt script will to a 'managedsave' on all running and paused guests when issuing 'rc.libvirt stop'. Please note that this saves the RAM of each guest to the host hdd (by default under /var/lib/libvirt/qemu/save) - so make sure enough space is available. If you prefer to perform a full shutdown on all running guests instead, issue a 'rc.libvirt guests_shutdown' followed by 'rc.libvirt shutdown'. By default 'rc.libvirt stop' and 'rc.libvirt guests_shutdown' will wait a maximum of 5 minutes for all guests to shutdown, after which any guests still running will be destroyed. Adjust this to a suitable value for your system, as destroying a running guest carries a high risk of data loss! There is also a 'guests_reboot' for rebooting all running guests." -------------- next part -------------- A non-text attachment was scrubbed... Name: rc.libvirt.diff Type: text/x-patch Size: 3202 bytes Desc: not available URL: From s.arcus at open-t.co.uk Wed May 24 12:52:58 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 24 May 2017 13:52:58 +0100 Subject: [Slackbuilds-users] Libvirt package - small change to /etc/rc.d/rc.libvirt In-Reply-To: References: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> Message-ID: On 05/05/17 16:15, Matteo Bernardini wrote: > 2017-05-04 13:55 GMT+02:00 Sebastian Arcus : >> I have a small change to suggest for the /etc/rc.d/rc.libvirt script. The >> script at the moment does a 'virsh shutdown ' on all running >> guests, and then, after waiting only 40 seconds, it destroys all guests >> which are still running. I think in most circumstances this is very likely >> to lead to corrupted guests because: >> >> 1. Many guests will take longer than 40 seconds to shutdown, specially if >> they are Windows guests. >> 2. Some Windows guests might be trying to install updates on shutdown, which >> can take 10, 20 or even 60 minutes. >> 3. If there are a number of guests running and the host is busy trying to >> shut them all down at the same time, even Linux guests will still be in the >> process of shutting down after 40 seconds. >> 4. If it is a setup where users connect to guests remotely, it is possible >> that people are in the middle of doing work which would be lost. >> >> Would it maybe be safer to do a 'virsh managedsave ' on every >> running guest instead? I can see many advantages to this option, including: > > one potential gotcha that I can foresee with this approach might be > that managedsave, creating a RAM image of the virtual machine, will > need an amount of Gb of disk space in /var/lib/libvirt/qemu/save/ the > same size of the RAM used by all the running virtual machines: on my > 64 Gb virtualization server I don't have, for example, that amount of > space in the root partition. > I'm just thinking out loud, don't misunderstand me :) Thank you for spotting that. I have submitted a patch which includes a "guests_shutdown" option - for those preferring to issue a full shutdown on all running guests before doing a /etc/rc.d/rc.libvirt stop (which otherwise would do a managedsave by default on all running and paused guests). Hopefully this will keep things flexible and safe and satisfy the needs of both types of setups :-) From atelszewski at gmail.com Thu May 25 00:02:07 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 25 May 2017 02:02:07 +0200 Subject: [Slackbuilds-users] VLC subtitle handling vulnerability In-Reply-To: References: Message-ID: <962e28d5-b352-3908-3991-a45e6022c560@gmail.com> On 24/05/17 07:59, David O'Shaughnessy wrote: > Just a heads up (maintainer cc'd in) about a vulnerability found in VLCs > handling of subtitles: > > http://blog.checkpoint.com/2017/05/23/hacked-in-translation/ > > It's fixed in the latest 2.2.5.1 release. The build on SBo seems to be a > development version though, so I'm not sure if this is relevant or not. > > -- > Dave Hi, There are more players with subtitles vulnerability and the article on checkpoint seems to be misleading. Have a look at the link from first comment in LWN article: https://lwn.net/Articles/723696/ Cheers. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sat May 27 01:11:22 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 May 2017 08:11:22 +0700 Subject: [Slackbuilds-users] Updates - 20170527.1 Message-ID: Hi folks another big update for May, which is the continuation to fix repology problem entries as well as regular updates. While more projects are migrating to HTTPS, we will keep seeing some entries there, but we will fix them eventually. This update also include security fixes for vlc and kodi regarding malicious subtitle zip (http://blog.checkpoint.com/2017/05/23/hacked-in-translation/). GCC 4.9.4 (legacy) is now included as well for those who are using PaleMoon. You now have an option to compile it using legacy GCC which is recommended by upstream developer. Robby has pushed his slackware-xdm-theme for those who wanted to costumize their xdg themes. There are still other tons of updates in this batch (331 commits). have a nice weekend :) Sat May 27 00:34:06 UTC 2017 academic/arpack-ng: Updated for version 3.5.0. academic/easy_spice: Added (A Simple Frontend for SPICE). academic/reduce-algebra: Updated for version 20170516svn4052. academic/scipy3: Update HOMEPAGE. academic/scipy: Update HOMEPAGE. academic/spidey: Update HOMEPAGE. academic/sundials: Update HOMEPAGE and DOWNLOAD urls. academic/ucsc-blat: Update HOMEPAGE. academic/veusz: Updated for version 1.26.1. accessibility/speech-dispatcher: Update HOMEPAGE and DOWNLOAD urls. audio/ngjackspa: Update homepage. audio/opus: Updated for version 1.1.5. audio/qmmp: Update README. audio/sonata: Update HOMEPAGE and DOWNLOAD urls. audio/spandsp: Update HOMEPAGE and DOWNLOAD urls. audio/speex: Update HOMEPAGE. audio/tagtool: Update HOMEPAGE and DOWNLOAD urls. audio/vimpc: Update HOMEPAGE and DOWNLOAD urls. audio/volwheel: Update HOMEPAGE and DOWNLOAD urls. audio/vorbisgain: Update HOMEPAGE and DOWNLOAD urls. audio/wineasio: Update homepage. business/skrooge: Update HOMEPAGE and DOWNLOAD urls. desktop/arc-firefox-theme: Added (Arc firefox theme). desktop/arc-icon-theme: Added (Arc icon theme). desktop/catfish: Updated for version 1.4.2. desktop/i3status: Updated for version 2.11. desktop/menutray: Updated for version 0.48. desktop/qt5ct: Updated for version 0.32. desktop/slack-wallpapers: Updated for version 0.446. desktop/slackware-xdg-menu: Update HOMEPAGE. desktop/slackware-xdm-theme: Added (Custom Slackware XDM Theme). desktop/tint2: Updated for version 0.14.5. desktop/wmudmount: Update DOWNLOAD. desktop/wmudmount: Update homepage. desktop/wmweather+: Update DOWNLOAD. desktop/wmweather+: Update homepage. desktop/xed: Updated for version 1.4.2. desktop/xfce4-whiskermenu-plugin: Update HOMEPAGE. desktop/xmms-status-plugin: Update HOMEPAGE and DOWNLOAD urls. desktop/xtrascreenhacks: Update HOMEPAGE and DOWNLOAD urls. desktop/yad: Update HOMEPAGE and DOWNLOAD urls. development/Catch: Updated for version 1.9.4. development/SQLAlchemy: Updated for version 1.1.10. development/Sphinx: Updated for version 1.6.1. development/android-studio: Updated for version 2.3.2.0_162_3934792. development/cgit: Update HOMEPAGE. development/composer: Updated for version 1.4.2. development/dkms: Updated for version 1.0.1. development/gcclegacy494: Added (GCC 4.9.4 legacy). development/git-lfs: Updated for version 2.1.1. development/gr-osmosdr: Updated for version 20170421. development/jupyter-nbdime: Added (Jupyter notebook diff and merge). development/jupyter-qtconsole: Updated for version 4.3.0. development/komodo-edit: Updated for version 10.2.2. development/komodo-ide: Updated for version 10.2.2. development/mongodb-compass: Updated for version 1.6.2. development/rarian: Switch to https. development/rust: Update HOMEPAGE and DOWNLOAD urls. development/scratch: Update HOMEPAGE and DOWNLOAD urls. development/setuptools-git: Update HOMEPAGE. development/simulavr: Updated for version git20170521. development/sloccount: Update HOMEPAGE and DOWNLOAD urls. development/sqlcl: Updated for version 4.2.0.17.097.0719. development/tclvfs: Update HOMEPAGE and DOWNLOAD urls. development/teensy_loader_cli: Update HOMEPAGE and DOWNLOAD urls. development/textadept: Update HOMEPAGE. development/tkdnd: Update HOMEPAGE and DOWNLOAD urls. development/tstoolbox: Update HOMEPAGE. development/uncrustify: Added (source code beautifier). development/universal-ctags: Updated for version 923b4e4. development/wheel: Update HOMEPAGE. development/xmlstarlet: Update HOMEPAGE and DOWNLOAD urls. development/xtruss: Update homepage. development/xtruss: Update slack-desc. development/zeal: Update HOMEPAGE. development/zope.interface: Update HOMEPAGE and DOWNLOAD urls. games/QuickNES-Core: Update HOMEPAGE. games/RetroArch: Update HOMEPAGE. games/ceferino: Update homepage. games/egoboo: Updated for version 2.8.1. games/freeciv: Update DOWNLOAD url. games/larn: Updated for version 14.0.2. games/lutris: Updated for version 0.4.10. games/mame: Updated for version 0.185. games/mangband: Added (graphical dungeon adventure game). games/mednafen: Updated for version 0.9.44.1. games/ppsspp: Updated for version 1.4.1. games/qxw: Update HOMEPAGE and DOWNLOAD urls. games/roccat-tools: Update HOMEPAGE and DOWNLOAD urls. games/scummvm-libretro: Update HOMEPAGE. games/simsu: Update HOMEPAGE and DOWNLOAD urls. games/smashbattle: Update HOMEPAGE and DOWNLOAD urls. games/snes9x-libretro: Update HOMEPAGE. games/snes9x2002: Update HOMEPAGE. games/snes9x2005: Update HOMEPAGE. games/snes9x2010: Update HOMEPAGE. games/spring: Update HOMEPAGE and DOWNLOAD urls. games/stella-libretro: Update HOMEPAGE. games/tanglet: Update HOMEPAGE and DOWNLOAD urls. games/tome-ah: Added (fantasy adventure game). games/tome4: Update HOMEPAGE and DOWNLOAD urls. games/tome: Removed (use tome4 or tome-ah). games/tyrquake-libretro: Update HOMEPAGE. games/ut2004: Update HOMEPAGE. games/vba-next: Update HOMEPAGE. games/vbam-libretro: Update HOMEPAGE. games/virtualjaguar-libretro: Update HOMEPAGE. games/warsow: Update HOMEPAGE. games/worldofpadman: Update HOMEPAGE and DOWNLOAD urls. games/yae: Update DOWNLOAD. games/yae: Update homepage. gis/pytrainer: Add a patch from upstream gis/qgis: Updated for version 2.18.8. gis/qmapshack: Updated for version 1.8.1. gis/viking: Update HOMEPAGE and DOWNLOAD urls. graphics/mozjpeg: Updated for version 3.2. graphics/openimageio: Prep for GCC 7 graphics/rawstudio: Update HOMEPAGE. graphics/rawtherapee: Updated for version 5.1. graphics/screencloud: Update HOMEPAGE and DOWNLOAD urls. graphics/teighafileconverter: Update HOMEPAGE. graphics/teighaviewer: Update HOMEPAGE. graphics/textext: Update HOMEPAGE and DOWNLOAD urls. graphics/uniconvertor: Update HOMEPAGE. graphics/vulkansdk: Updated for version 1.0.49.0. graphics/xzgv: Update HOMEPAGE and DOWNLOAD urls. graphics/yagf: Update HOMEPAGE and DOWNLOAD urls. graphics/zbar: Update HOMEPAGE and DOWNLOAD urls. ham/aprx: Fixed homepage ham/xdx: Update HOMEPAGE and DOWNLOAD urls. libraries/CherryPy: Updated for version 10.2.2. libraries/Hypodermic: Updated for version 2.4. libraries/QUSB: Added (Qt wrapper classes for LibUSB 1.0). libraries/QtUsb: Added (USB library for Qt). libraries/SQLObject: Update HOMEPAGE and DOWNLOAD urls. libraries/ZConfig: Update HOMEPAGE and DOWNLOAD urls. libraries/ZODB3: Update HOMEPAGE and DOWNLOAD urls. libraries/allegro: Updated for version 5.2.1. libraries/capnproto: Updated for version 0.6.0. libraries/fcl: Added (collision library). libraries/folly: Updated for version 2017.05.22.00. libraries/hackrf: Updated for version 20170228. libraries/lensfun: Update README for optional dep. libraries/leptonica: Updated for version 1.74.2. libraries/libaacs: Updated for version 0.9.0 libraries/libccd: Added (collision detection library). libraries/libopenshot: Updated for version 0.1.6 libraries/libopusenc: Added (High-level Opus decoding library). libraries/libosmo-dsp: Updated for version 20170317. libraries/libreadline-java: Added (Java-Readline JNI-wrapper). libraries/libversion: Updated for version 1.2.0. libraries/libwacom: Updated for version 0.25. libraries/live555: Updated for version 2017.05.24 libraries/proxygen: Updated for version 2017.05.22.00. libraries/rest: Update HOMEPAGE and DOWNLOAD urls. libraries/rocksdb: Updated for version 5.3.6. libraries/simbody: Added (multibody physics API). libraries/skstream: Update HOMEPAGE and DOWNLOAD urls. libraries/sqlpp11-connector-sqlite3: Updated for version 0.24. libraries/swfdec: Update HOMEPAGE and DOWNLOAD urls. libraries/tre: Update HOMEPAGE and DOWNLOAD urls. libraries/vsqlite++: Update HOMEPAGE and DOWNLOAD urls. libraries/vte3: Updated for version 0.48.3. libraries/wangle: Updated for version 2017.05.22.00. libraries/webkit2gtk: Update HOMEPAGE and DOWNLOAD urls. libraries/webkitgtk3: Update HOMEPAGE and DOWNLOAD urls. libraries/webkitgtk: Update HOMEPAGE and DOWNLOAD urls. libraries/wfmath: Update HOMEPAGE and DOWNLOAD urls. libraries/wxsvg: Update HOMEPAGE and DOWNLOAD urls. libraries/xcb-util-xrm: Updated for version 1.2. libraries/zbase32: Update HOMEPAGE and DOWNLOAD urls. libraries/zc.lockfile: Update HOMEPAGE and DOWNLOAD urls. libraries/zdaemon: Update HOMEPAGE and DOWNLOAD urls. libraries/zfec: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.component: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.configuration: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.event: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.hookable: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.i18nmessageid: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.location: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.proxy: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.schema: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.security: Update HOMEPAGE and DOWNLOAD urls. libraries/zope.sqlalchemy: Update HOMEPAGE and DOWNLOAD urls. misc/ardesia: Updated homepage and download links misc/grc: Updated for version 1.11.1. misc/readesm: Update HOMEPAGE and DOWNLOAD urls. misc/rsibreak: Update HOMEPAGE and DOWNLOAD urls. misc/tal: Update HOMEPAGE and DOWNLOAD urls. misc/utimer: Update HOMEPAGE and DOWNLOAD urls. misc/vdpauinfo: Update HOMEPAGE and DOWNLOAD urls. misc/xclip: Update HOMEPAGE and DOWNLOAD urls. multimedia/kodi: Updated for version 17.3 multimedia/mkvtoolnix: Updated for version 12.0.0. multimedia/obs-studio: Updated for version 19.0.2 multimedia/openshot: Updated for version 2.3.3 multimedia/ripperX: Update HOMEPAGE and DOWNLOAD urls. multimedia/shotcut: Update HOMEPAGE. multimedia/spotify: Updated for version 1.0.55. multimedia/telepathy-farstream: Update HOMEPAGE and DOWNLOAD urls. multimedia/telepathy-glib: Update HOMEPAGE and DOWNLOAD urls. multimedia/telepathy-qt: Update HOMEPAGE and DOWNLOAD urls. multimedia/vlc: Updated for version 20170523_bec643e (addresses "hacked-in-translation" vulnerability) network/NetworkManager-openvpn: Updated for version 1.2.10. network/PaleMoon: Update build script. network/clipgrab: Updated for version 3.6.5. network/dropbear: Updated for version 2017.75, new maintainer. network/icecat: Updated for version 52.1.0. network/kea: Add support for botan. network/nbd: Updated for version 3.15.3 network/nextcloud-client: Added (Nextcloud Desktop Client). network/opera: Updated for version 45.0.2552.812. network/qtmib: Added (SNMP MIB Browser). network/radicale: Updated for version 1.1.2. network/rclone: Update HOMEPAGE and DOWNLOAD urls. network/rekonq: Update HOMEPAGE and DOWNLOAD urls. network/sabnzbd: Update HOMEPAGE. network/slack: Updated for version 2.6.0. network/slimjet: Updated for version 14.0.10.0. network/snmpsim: Update HOMEPAGE and DOWNLOAD urls. network/snort: Update HOMEPAGE and DOWNLOAD urls. network/sqlmap: Updated for version 1.1.5. network/sshguard: Update HOMEPAGE and DOWNLOAD urls. network/strongswan: Update HOMEPAGE and DOWNLOAD urls. network/suricata: Update HOMEPAGE. network/t38modem: Update HOMEPAGE. network/tinc: Added (VPN daemon). network/tixati: Update HOMEPAGE and DOWNLOAD urls. network/tmate: Update HOMEPAGE. network/toxcore: Update HOMEPAGE. network/tribler: Update homepage. network/twine: Updated for version 1.9.0. network/unicornscan: Update HOMEPAGE. network/vivaldi: Updated for version 1.9.818.50. network/vpnc: Update HOMEPAGE. network/vrrpd: Update HOMEPAGE and DOWNLOAD urls. network/wol: Update HOMEPAGE and DOWNLOAD urls. network/youtube-dl: Updated for version 2017.05.23. office/asymptote: Updated for version 2.41. office/hunspell-de: Updated for version 20161207. office/lyx: Updated for version 2.2.3. office/mtp2-fonts: Added (Times-compatible math TeX fonts). office/scribus: Update HOMEPAGE and DOWNLOAD urls. office/taskd: Update HOMEPAGE and DOWNLOAD urls. office/xpad: Update HOMEPAGE and DOWNLOAD urls. office/xreader: Updated for version 1.4.2. perl/perl-AnyEvent-I3: Updated for version 0.17. perl/perl-CPAN-Perl-Releases: Updated for version 3.18. perl/perl-CPANPLUS-Dist-Build: Updated for version 0.88. perl/perl-CPANPLUS: Updated for version 0.9168. perl/perl-Expect: Updated for version 1.35. perl/perl-ExtUtils-Install: Updated for version 2.10. python/Flask: Updated for version 0.12.2. python/RBTools: Update HOMEPAGE and DOWNLOAD urls. python/Scrapy: Update HOMEPAGE. python/Scrapy: Updated for version 1.4.0. python/Unidecode: Update HOMEPAGE. python/euca2ools: Updated for version 3.4.1 python/pendulum: Updated for version 1.2.1. python/pytest: Updated for version 3.1.0. python/python-fonttools: Updated for version 3.12.1. python/python-requests-kerberos: Updated for version 0.11.0. python/python-requests: Updated for version 2.14.2. python/python-slacklog: Added (Convert Slackware ChangeLog). python/python-twitter: Updated for version 3.3. python/requests-toolbelt: Updated for version 0.8.0. python/rsa: Update HOMEPAGE. python/selenium: Updated for version 3.4.2. python/shutil_which: Added (find path of executable). python/simplegeneric: Update HOMEPAGE and DOWNLOAD urls. python/six: Update HOMEPAGE and DOWNLOAD urls. python/sk1libs: Update HOMEPAGE. python/speaklater: Update HOMEPAGE and DOWNLOAD urls. python/sphinxcontrib-websupport: Added (Sphinx API for web apps). python/sqlalchemy-migrate: Updated for version 1.11.0. python/tempita: Script cleanup python/tempora: Updated for version 1.7. python/termcolor: Update HOMEPAGE. python/threadpool: Update HOMEPAGE. python/webassets: Update HOMEPAGE and DOWNLOAD urls. ruby/ruby-build: Updated for version 20170523. ruby/ruby-gist: Updated for version 4.6.1. ruby/rubygem-bundler: Updated for version 1.15.0. ruby/rubygem-cool.io: Update HOMEPAGE and DOWNLOAD urls. ruby/rubygem-fastercsv: Update HOMEPAGE and DOWNLOAD urls. ruby/rubygem-highline: Update HOMEPAGE and DOWNLOAD urls. ruby/rubygem-terminal-table: Update HOMEPAGE and DOWNLOAD urls. ruby/rubygems-update: Update HOMEPAGE and DOWNLOAD urls. ruby/sqlite3: Update HOMEPAGE and DOWNLOAD urls. system/ZoneMinder: Update HOMEPAGE and DOWNLOAD urls. system/acd_cli: Updated for version 0.3.2+3170d55. system/butterfly: Updated for version 3.1.4. system/cassandra-gui: Update README. system/daemontools: Added (djb's tools for managing UNIX services). system/docker: Disable rc script by default, update README. system/fio: Updated for version 2.20. system/gpsbabel: Updated for version 1.5.3. system/gtk-vnc: Updated for version 0.7.1. system/influxdb: Updated for version 1.2.4. system/intel-microcode: Updated for version 20170511. system/letsencrypt: Updated for version 0.14.2. system/nvme-cli: Updated for version 1.3. system/pass: Added (password store manager). system/refind: Updated for version 0.10.8. system/rng-tools: Update HOMEPAGE and DOWNLOAD urls. system/sleepd: Added (power management daemon). system/slim: Update HOMEPAGE and DOWNLOAD urls. system/spkg: Update HOMEPAGE and DOWNLOAD urls. system/swatch: Update HOMEPAGE and DOWNLOAD urls. system/syslog-ng: Update HOMEPAGE. system/trrntzip: Update HOMEPAGE and DOWNLOAD urls. system/twin: Update HOMEPAGE and DOWNLOAD urls. system/udftools: Update HOMEPAGE and DOWNLOAD urls. system/un-fonts-core: Update HOMEPAGE and DOWNLOAD urls. system/unetbootin: Updated for version 647. system/vagrant: Update HOMEPAGE. system/vbindiff: Update HOMEPAGE and DOWNLOAD urls. system/vcp: Update homepage. system/virtualbox-addons: Update HOMEPAGE. system/virtualbox-extension-pack: Update HOMEPAGE. system/virtualbox-kernel-addons: Update HOMEPAGE. system/virtualbox-kernel: Update HOMEPAGE. system/virtualbox: Update HOMEPAGE. system/wine-staging: Updated for version 2.8. system/wmconfig: Update HOMEPAGE and DOWNLOAD urls. system/xboxdrv-linux: Update HOMEPAGE and DOWNLOAD urls. system/xfsudo: Update HOMEPAGE and DOWNLOAD urls. system/xosd: Update HOMEPAGE. system/yakuake: Update HOMEPAGE and DOWNLOAD urls. +--------------------------+ -- 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 aclemons at runbox.no Sat May 27 05:56:22 2017 From: aclemons at runbox.no (Andrew Clemons) Date: Sat, 27 May 2017 17:56:22 +1200 Subject: [Slackbuilds-users] pass / password-store Message-ID: <20170527055621.GA21988@runbox.no> Is the pass slackbuild which was added with this update supposed to replace password-store[1]? They both point to the same project. [1]: https://slackbuilds.org/repository/14.2/system/password-store/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From willysr at slackbuilds.org Sat May 27 06:38:20 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 May 2017 13:38:20 +0700 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: <20170527055621.GA21988@runbox.no> References: <20170527055621.GA21988@runbox.no> Message-ID: <82e27026-917c-8eeb-b17e-e7512ffd2eec@slackbuilds.org> > Is the pass slackbuild which was added with this update supposed to > replace password-store[1]? They both point to the same project. > > [1]: https://slackbuilds.org/repository/14.2/system/password-store/ Hi Yes, it's pointing to the same project it seems it was added long time ago and use the website's URL instead of the project. I missed that. the original maintainer never updated this script since 4 years ago, so if no objection is made, i'm removing the old one and urging users to migrate to pass. -- 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 aclemons at runbox.no Sat May 27 06:58:23 2017 From: aclemons at runbox.no (Andrew Clemons) Date: Sat, 27 May 2017 18:58:23 +1200 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: <82e27026-917c-8eeb-b17e-e7512ffd2eec@slackbuilds.org> References: <20170527055621.GA21988@runbox.no> <82e27026-917c-8eeb-b17e-e7512ffd2eec@slackbuilds.org> Message-ID: <20170527065823.GC21988@runbox.no> On 2017-05-27 13:38:20 +0700, willysr at slackbuilds.org wrote: > Hi > > Yes, it's pointing to the same project > it seems it was added long time ago and use the website's URL instead of > the project. I missed that. > > the original maintainer never updated this script since 4 years ago, so > if no objection is made, i'm removing the old one and urging users to > migrate to pass. I don't mind either way. Some projects call the package pass (arch, fedora, gentoo, etc), others password-store (debian, ubuntu, bsds, etc). If you do remove password-store, can you update the dependency of my slackbuild, qtpass, to the new pacakge? Thanks, Andrew -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From lists at osh.id.au Sat May 27 08:14:16 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 27 May 2017 18:14:16 +1000 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: <82e27026-917c-8eeb-b17e-e7512ffd2eec@slackbuilds.org> References: <20170527055621.GA21988@runbox.no> <82e27026-917c-8eeb-b17e-e7512ffd2eec@slackbuilds.org> Message-ID: <11be69b7-e761-b716-f62a-d192dd5b66fc@osh.id.au> On 05/27/2017 04:38 PM, Willy Sudiarto Raharjo wrote: > the original maintainer never updated this script since 4 years ago, so > if no objection is made, i'm removing the old one and urging users to > migrate to pass. There's actually a bug in the password-store build (1.6.5) that breaks editing, so I'm all for the new one. -- Dave From dpross1100 at msn.com Sat May 27 11:08:48 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 27 May 2017 11:08:48 +0000 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: <11be69b7-e761-b716-f62a-d192dd5b66fc@osh.id.au> Message-ID: I'm for a new version too if it fixes that bug, but wouldn't it be less confusing to leave the name the same and just have the new maintainer take over? Some people don't subscribe to this list and wouldn't see the announcement. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Sat May 27 11:32:59 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 27 May 2017 12:32:59 +0100 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: <82e27026-917c-8eeb-b17e-e7512ffd2eec@slackbuilds.org> References: <20170527055621.GA21988@runbox.no> <82e27026-917c-8eeb-b17e-e7512ffd2eec@slackbuilds.org> Message-ID: > Yes, it's pointing to the same project oops! The reviewer should have spotted that! Sorry! -D. imperfect reviewer since 2016 From lists at osh.id.au Sat May 27 12:11:47 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 27 May 2017 22:11:47 +1000 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: References: Message-ID: <37bcf540-387f-ea6a-df95-2ca2264d1b90@osh.id.au> On 05/27/2017 09:08 PM, Daniel Prosser wrote: > I'm for a new version too if it fixes that bug, but wouldn't it be less > confusing to leave the name the same and just have the new maintainer > take over? Some people don't subscribe to this list and wouldn't see the > announcement. That's a good point. There will be probably be users on the "password-store" build that will never even notice that it's migrated over "pass". Seems better then to just replace the unmaintained script with the new one. -- Dave From willysr at slackbuilds.org Sat May 27 15:17:19 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 May 2017 22:17:19 +0700 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: <37bcf540-387f-ea6a-df95-2ca2264d1b90@osh.id.au> References: <37bcf540-387f-ea6a-df95-2ca2264d1b90@osh.id.au> Message-ID: <6f62d36e-895a-49b0-f348-9e4f305b4c8d@slackbuilds.org> >> I'm for a new version too if it fixes that bug, but wouldn't it be less >> confusing to leave the name the same and just have the new maintainer >> take over? Some people don't subscribe to this list and wouldn't see the >> announcement. > > That's a good point. There will be probably be users on the > "password-store" build that will never even notice that it's migrated > over "pass". Seems better then to just replace the unmaintained script > with the new one. There's always a ChangeLog in every public update also i have added "password store" and "password-store" to the keyword so they will be pointed to pass after next public update. -- 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 dpross1100 at msn.com Sat May 27 16:21:33 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 27 May 2017 16:21:33 +0000 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: <6f62d36e-895a-49b0-f348-9e4f305b4c8d@slackbuilds.org> References: <37bcf540-387f-ea6a-df95-2ca2264d1b90@osh.id.au> <6f62d36e-895a-49b0-f348-9e4f305b4c8d@slackbuilds.org> Message-ID: Well that's good, but I still think it's better not to change the name unless there's a good reason for it. And the reason for the name change in this case seems to be a simple oversight. That's just my opinion, and of course the admins can do whatever they think is best. (By the way, I tried the new version and it works well.) On Sat, May 27, 2017 at 10:17:19PM +0700, Willy Sudiarto Raharjo wrote: > >> I'm for a new version too if it fixes that bug, but wouldn't it be less > >> confusing to leave the name the same and just have the new maintainer > >> take over? Some people don't subscribe to this list and wouldn't see the > >> announcement. > > > > That's a good point. There will be probably be users on the > > "password-store" build that will never even notice that it's migrated > > over "pass". Seems better then to just replace the unmaintained script > > with the new one. > > There's always a ChangeLog in every public update > also i have added "password store" and "password-store" to the keyword > so they will be pointed to pass after next public update. > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sat May 27 16:46:57 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 May 2017 23:46:57 +0700 Subject: [Slackbuilds-users] pass / password-store In-Reply-To: References: <37bcf540-387f-ea6a-df95-2ca2264d1b90@osh.id.au> <6f62d36e-895a-49b0-f348-9e4f305b4c8d@slackbuilds.org> Message-ID: <54af5c33-52b8-918d-42b1-29da00f8e350@slackbuilds.org> > Well that's good, but I still think it's better not to change the name > unless there's a good reason for it. And the reason for the name change > in this case seems to be a simple oversight. That's just my opinion, and > of course the admins can do whatever they think is best. Done i have removed pass and updated password-store in 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 ozan.turkyilmaz at gmail.com Sun May 28 19:12:21 2017 From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=) Date: Mon, 29 May 2017 00:12:21 +0500 Subject: [Slackbuilds-users] mkvtoolnix dep wxPhyton Message-ID: Hello, How come mkvtoolnix has a dep on wsPhyton? I dont remember such things. It only uses QT5 for gui. Can one of the mods remove it? -- Ozan, BSc, BEng -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sun May 28 19:17:26 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 28 May 2017 21:17:26 +0200 Subject: [Slackbuilds-users] mkvtoolnix dep wxPhyton In-Reply-To: References: Message-ID: 2017-05-28 21:12 GMT+02:00 Ozan T?rky?lmaz : > Hello, > > How come mkvtoolnix has a dep on wsPhyton? I dont remember such things. It > only uses QT5 for gui. Can one of the mods remove it? done in my branch. Matteo From slackalaxy at gmail.com Mon May 29 17:28:59 2017 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 29 May 2017 20:28:59 +0300 Subject: [Slackbuilds-users] templates and guidelines Message-ID: Hi to all, SBo provides templates that cover different sources types, as well as slack-desc, README, etc. How about guidelines about package file install locations? Something similar to what CRUX has: https://crux.nu/Main/Handbook3-3#ntoc25 for example: - when is it advisable to install things to /opt - where should jar files go - extra binaries? should they go to /usr/libexec or /urs/lib${LIBDIRSUFFIX} It will be useful if there is a template for .desktop files, when provided by the SlackBuild maintainer. Another thing. Versioning of packages installed from git sources. Should it be the commit itself, like here: https://slackbuilds.org/repository/14.2/desktop/Window_Manager_Scripts/ or just the first 7 symbols? If so, should there be a git indicaterd somewhere: https://slackbuilds.org/repository/14.2/academic/bpp-core/ or/and the date: https://slackbuilds.org/repository/14.2/academic/cistrome-extra/ Providing proper download links to git sources has been a pain not just for me, I believe. I was so frustrated, I found it necessary to write a blog post about this, for my future reference: https://slackalaxy.com/2017/05/01/github-download-links/ Maybe there could be some instructions about this at SBo? just thinking... regards, Petar From slackph at posteo.de Mon May 29 19:55:05 2017 From: slackph at posteo.de (Philip Lacroix) Date: Mon, 29 May 2017 21:55:05 +0200 Subject: [Slackbuilds-users] zyGrib source code link Message-ID: Greetings I'm updating the SlackBuild for zyGrib, which is now at release 8.0.1. The PHP script on the official website doesn't seem to be allowing automated downloads (as with wget), hence I was considering to point the .info file to one of the Gentoo mirrors: they do provide a completely vanilla source package for zyGrib 8.0.1. However, the old release is already hosted in the SBo "direct links" repository on Sourceforge. Could the latest one be uploaded there as well? In case it is possible, this is the official link: http://zygrib.org/getfile.php?file=zyGrib-8.0.1.tgz Best regards Philip From willysr at slackbuilds.org Tue May 30 00:47:39 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 30 May 2017 07:47:39 +0700 Subject: [Slackbuilds-users] zyGrib source code link In-Reply-To: References: Message-ID: <5d45ce2d-526e-eeee-3a33-299bac63dd7c@slackbuilds.org> > However, the old release is already hosted in the SBo "direct links" > repository > on Sourceforge. Could the latest one be uploaded there as well? In case > it is > possible, this is the official link: Done -- 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 slackph at posteo.de Tue May 30 08:31:34 2017 From: slackph at posteo.de (Philip Lacroix) Date: Tue, 30 May 2017 10:31:34 +0200 Subject: [Slackbuilds-users] zyGrib source code link In-Reply-To: <5d45ce2d-526e-eeee-3a33-299bac63dd7c@slackbuilds.org> References: <5d45ce2d-526e-eeee-3a33-299bac63dd7c@slackbuilds.org> Message-ID: <34c5d9f554eeb7f275a541426fb67c02@posteo.de> Am 30.05.2017 02:47 schrieb Willy Sudiarto Raharjo: > Done Thanks, Willy! From s.arcus at open-t.co.uk Tue May 30 11:17:02 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 30 May 2017 12:17:02 +0100 Subject: [Slackbuilds-users] Motion won't compile on -current or 14.2 Message-ID: I notice that Motion has been "magically" upgraded to 4.0.1 :-) However, it doesn't compile for me on either -current or 14.2. I get several errors as below - is this an incompatibility with gcc? x86_64-slackware-linux-gcc -O2 -fPIC -D_REENTRANT -I/usr/include -DMOTION_V4L2 -DTYPE_32BIT="int" -DHAVE_BSWAP -Wall -DVERSION=\"4.0.1\" -Dsysconfdir=\"/etc\" -c -o vloopback_motion.o vloopback_motion.c vloopback_motion.c: In function ?v4l_startpipe?: vloopback_motion.c:181:26: error: storage size of ?vid_pic? isn?t known struct video_picture vid_pic; ^~~~~~~ vloopback_motion.c:182:25: error: storage size of ?vid_win? isn?t known struct video_window vid_win; ^~~~~~~ vloopback_motion.c:198:20: error: ?VIDIOCGPICT? undeclared (first use in this function); did you mean ?VIDIOC_G_FMT?? if (ioctl(dev, VIDIOCGPICT, &vid_pic) == -1) { ^~~~~~~~~~~ VIDIOC_G_FMT vloopback_motion.c:198:20: note: each undeclared identifier is reported only once for each function it appears in vloopback_motion.c:205:20: error: ?VIDIOCSPICT? undeclared (first use in this function); did you mean ?VIDIOCGPICT?? if (ioctl(dev, VIDIOCSPICT, &vid_pic) == -1) { ^~~~~~~~~~~ VIDIOCGPICT vloopback_motion.c:210:20: error: ?VIDIOCGWIN? undeclared (first use in this function); did you mean ?VIDIOCGPICT?? if (ioctl(dev, VIDIOCGWIN, &vid_win) == -1) { ^~~~~~~~~~ VIDIOCGPICT vloopback_motion.c:218:20: error: ?VIDIOCSWIN? undeclared (first use in this function); did you mean ?VIDIOCGWIN?? if (ioctl(dev, VIDIOCSWIN, &vid_win) == -1) { ^~~~~~~~~~ VIDIOCGWIN I've also tried version 3.4.1 from here(https://github.com/Motion-Project/motion/releases/tag/release-3.4.1) with the same result. Searching online, there are a few bug reports with the above error message from 2012-2013 - so either it is a regression - or an unrelated new bug. From willysr at slackbuilds.org Tue May 30 11:24:17 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 30 May 2017 18:24:17 +0700 Subject: [Slackbuilds-users] Motion won't compile on -current or 14.2 In-Reply-To: References: Message-ID: > I notice that Motion has been "magically" upgraded to 4.0.1 :-) However, > it doesn't compile for me on either -current or 14.2. I get several > errors as below - is this an incompatibility with gcc? Tested on -stable https://pastebin.com/NUYvkDa8 Tested on -current https://pastebin.com/qxMzUChT -- 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 s.arcus at open-t.co.uk Tue May 30 11:44:57 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 30 May 2017 12:44:57 +0100 Subject: [Slackbuilds-users] Motion won't compile on -current or 14.2 In-Reply-To: References: Message-ID: <80914bb8-772a-397e-6d88-af659b4c42a9@open-t.co.uk> On 30/05/17 12:24, Willy Sudiarto Raharjo wrote: >> I notice that Motion has been "magically" upgraded to 4.0.1 :-) However, >> it doesn't compile for me on either -current or 14.2. I get several >> errors as below - is this an incompatibility with gcc? > > Tested on -stable > https://pastebin.com/NUYvkDa8 > > Tested on -current > https://pastebin.com/qxMzUChT Thank you for the quick reply. I have just tested on another -current machine, and it works there. Hmm - now I have to try and figure out why it doesn't work on the first machine. They are both on -current, so I wonder what else could be causing this? From willysr at slackbuilds.org Tue May 30 12:15:42 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 30 May 2017 19:15:42 +0700 Subject: [Slackbuilds-users] Motion won't compile on -current or 14.2 In-Reply-To: <80914bb8-772a-397e-6d88-af659b4c42a9@open-t.co.uk> References: <80914bb8-772a-397e-6d88-af659b4c42a9@open-t.co.uk> Message-ID: <56d39631-136f-5805-914f-ccd0d9cfc6ab@slackbuilds.org> > Thank you for the quick reply. I have just tested on another -current > machine, and it works there. Hmm - now I have to try and figure out why > it doesn't work on the first machine. They are both on -current, so I > wonder what else could be causing this? Perhaps you can compare what 3rd party packages installed on both machines -- 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 s.arcus at open-t.co.uk Tue May 30 12:26:31 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 30 May 2017 13:26:31 +0100 Subject: [Slackbuilds-users] Motion won't compile on -current or 14.2 In-Reply-To: References: Message-ID: <63ebe72e-e7bb-6c21-5eba-d8cee3e3f59f@open-t.co.uk> On 30/05/17 12:24, Willy Sudiarto Raharjo wrote: >> I notice that Motion has been "magically" upgraded to 4.0.1 :-) However, >> it doesn't compile for me on either -current or 14.2. I get several >> errors as below - is this an incompatibility with gcc? > > Tested on -stable > https://pastebin.com/NUYvkDa8 > > Tested on -current > https://pastebin.com/qxMzUChT Thank you again for confirming it works on both -current and 14.2. I have found the problem at my end. Years ago I had to create a soft link for the videodev.h file (to cope with an old Motion bug!) - and that was preventing Motion from compiling now: /usr/include/linux/videodev.h -> /usr/include/linux/videodev2.h Once I removed the soft link, everything compiled fine. Sorry for the noise and thank you for the help. From baildon.research at googlemail.com Tue May 30 12:27:09 2017 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 30 May 2017 13:27:09 +0100 Subject: [Slackbuilds-users] templates and guidelines In-Reply-To: References: Message-ID: > Hi to all, Hi Petar and everybody, > SBo provides templates that cover different sources types, as well as > slack-desc, README, etc. How about guidelines about package file > install locations? Something similar to what CRUX has: Interesting question, thanks. Here are some personal answers, I don't want to commit any of the other admins to anything! To start, are we all happy with "guidelines" and advice and education, but not "rules"? (I am!) If a maintainer submits stuff that doesn't meet the guidelines in my head, I am happy to help when the submission is reviewed. The maintainer is the upstream software expert, and the reviewer is the downstream packaging expert, and we are partners. If the maintainer doesn't know my guidelines, that's ok, because the guidelines are not all written down, or they exist only in an old email on this list, or they are constantly evolving. *But* I don't apply the guidelines in my head consistently or transparently, and this process definitely confuses some maintainers and adds more to my workload. In my personal opinion, I need to find the time to communicate the guidelines better and open them up to community feedback. The big problem is finding some way of doing that, without just creating a huge wiki of badly edited pages that nobody has time to read. The other problem is that I don't want to share real examples of "bad" submissions in public. > It will be useful if there is a template for .desktop files, when > provided by the SlackBuild maintainer. Sometimes our guidelines evolve when we get a better understanding, and this is an interesting example. Thanks to recent help from B Watson I now understand how to validate desktop files :) So yes, we can now do a desktop template. There are also things to discuss about the perl and python templates, maybe June could be SBo Template Month :) > for example: > - when is it advisable to install things to /opt > - where should jar files go > - extra binaries? should they go to /usr/libexec or /usr/lib${LIBDIRSUFFIX} > Another thing. Versioning of packages installed from git sources. good list -- it would be great if other people have more items to add to the list? please? > Providing proper download links to git sources has been a pain not > just for me, I believe. I was so frustrated, I found it necessary to > write a blog post about this, for my future reference: > https://slackalaxy.com/2017/05/01/github-download-links/ It was pprkut who first brought the github trick to our attention ;) > Maybe there could be some instructions about this at SBo? You've made a good start :) Something I want to do is to document the best DOWNLOAD for other cases like Sourceforge, CPAN, Pypi etc etc. and I think https://twinery.org/ would be a great tool for that. But that would be a personal experiment, let's see if it's successful. Thanks Petar for the valuable feedback. It really does help us (me!) to prioritise what we need to do next. As I said above, it would be great if other people could add to the list of things that need guidelines please! Cheers -D. From yalhcru at gmail.com Tue May 30 16:56:54 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 30 May 2017 12:56:54 -0400 Subject: [Slackbuilds-users] templates and guidelines In-Reply-To: References: Message-ID: On 5/30/17, David Spencer wrote: > As I said above, it would be great if other people could add to the > list of things that need guidelines please! Ran across this recently: http://jbr.me.uk/linux/esl.html It's geared towards Debian, but it's a pretty good set of guidelines for how to write package descriptions. For us, that's slack-desc and README files. Also, my own short version: Don't blindly copy/paste from upstream's README or web site. Their description usually makes a good starting point, but you should fix any spelling/grammar errors, get rid of any hyperbole (anything that reads more like advertising copy than a factual description), and get rid of excessive detail: We don't need to know the whole history of the software, or the list of 10 platforms it's been ported to. Or, rather, users browsing the SBo package repo don't need that much detail, just to decide whether or not the package looks like something they might want to install. The place for the extra detail is inside the package, in /usr/doc/$PRGNAM-$VERSION. Also, I think these really should be rules: - README and .info file must be either plain ASCII, or UTF-8, *without BOM*! If in doubt, use the 'file' command. - The only reason to make README or .info files UTF-8 would be if there's a proper name that requires non-ASCII characters (maintainer's name, or possibly the name of the software itself, like "L??VE"). Cute Unicode bullets, or emdashes, or "smart quotes", should be replaced with ASCII equivalents (asterisk for bullets, plain hyphen for dashes, plain single or double quotes instead of ???these?? or ???these??? quotes). - slack-desc needs to be ASCII. It's going to get catted to the user's terminal when the package is installed, and there's NO WAY TO TELL what character set and encoding the user's terminal expects. Guidelines about file locations: I'd say you should only use /opt when your build is for something that might conflict with stock Slackware packages. Example, mozjpeg installs libraries and binaries with the same names as stuff from Slack's libjpeg-turbo package. If your build is a game, put the executable in /usr/games, any data files in /usr/share/games/$PRGNAM (though I've broken this "rule" myself, plenty of them install to /usr/share/$PRGNAM). Man pages for games go in section 6, /usr/man/man6, which might mean you need to patch or sed the man pages themselves (since the man page section appears in the file). If it's a game ported from Windows, which expects to be run from its own directory (which it expects to be able to write to), use a wrapper script in /usr/games, place the real game binary in /usr/libexec/$PRGNAM/. Again, plenty of examples of this "rule" being broken if you look through my builds. In fact I should go through and fix them... David doesn't want to post "bad" submissions for fear of embarrassing anyone, and I agree with that... but, I don't mind using my own "bad" builds for examples, so I may write up a little "why this was broken and how I fixed it" post pretty soon. From s.arcus at open-t.co.uk Tue May 30 19:09:05 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 30 May 2017 20:09:05 +0100 Subject: [Slackbuilds-users] Libvirt package - small change to /etc/rc.d/rc.libvirt In-Reply-To: References: <9bd71977-bd81-341c-e05b-0ccb277b54c1@open-t.co.uk> <20170505095008.1e130300@home.rlworkman.net> Message-ID: On 24/05/17 13:49, Sebastian Arcus wrote: > > On 05/05/17 15:50, Robby Workman wrote: >> On Thu, 4 May 2017 12:55:03 +0100 >> Sebastian Arcus wrote: >> >>> I have a small change to suggest for the /etc/rc.d/rc.libvirt script. >>> The script at the moment does a 'virsh shutdown ' on all >>> running guests, and then, after waiting only 40 seconds, it destroys >>> all guests which are still running. I think in most circumstances >>> this is very likely to lead to corrupted guests because: >>> >>> 1. Many guests will take longer than 40 seconds to shutdown, >>> specially if they are Windows guests. >>> 2. Some Windows guests might be trying to install updates on >>> shutdown, which can take 10, 20 or even 60 minutes. >>> 3. If there are a number of guests running and the host is busy >>> trying to shut them all down at the same time, even Linux guests will >>> still be in the process of shutting down after 40 seconds. >>> 4. If it is a setup where users connect to guests remotely, it is >>> possible that people are in the middle of doing work which would be >>> lost. >>> >>> Would it maybe be safer to do a 'virsh managedsave ' on >>> every running guest instead? I can see many advantages to this >>> option, including: >>> >>> 1. It is much less likely for users who might use the guests remotely >>> to loose work, as the machine state is suspended. >>> >>> 2. Guests stopped with 'managedsave' will start fine with the 'start' >>> command - so no need to change any settings anywhere else, and the >>> 'autostart' feature of libvirt will continue to work fine. >>> >>> 2. On my server, the 'managedsave' operation takes around 20 seconds >>> per guest, and it is more predictable in duration than a 'shutdown', >>> which depends on the OS in the guest, if it is installing updates etc. >>> >>> 4. The 'managedsave' command doesn't return immediately, so we can >>> wait for each guest in turn and know when it is done. Or ampersand >>> could be used on the command, and then just do a looped check on >>> 'virsh list' lower down, waiting for the 'managedsave' on all guests >>> to finish. >>> >>> 5. If my understanding is correct, the 'shutdown' command depends on >>> the guest implementing correctly and acting on ACPI commands, while a >>> 'managedsave' seems to be under the complete control of libvirt - >>> which means the script would work correctly out of the box with a >>> much wider variety of OS's and configurations on the guest side. >>> >>> If necessary, I suppose the script could also implement a >>> 'reboot_guests' separate command, for people to use it to reboot all >>> running guests - as the "stop" command wouldn't be performing a full >>> shutdown any more. >>> >>> Just a suggestion in case it helps. I'm already very happy with the >>> current script, as I used to have to write my own to shutdown >>> kvm/qemu guests :-) >> >> >> This seems like a reasonable change. Can you push it to a git >> repo/branch somewhere and send me a link, or else send me a >> patch(set) to merge? > > With some delay, please find attached the suggested changes to the > rc.libvirt script. I have made the following the amendments: > > 1. Increased the default timeout to 5 minutes (300 seconds). I think > guests should be destroyed only as a last resort - as the risk of > corrupting data is very high. If a quicker shutdown is needed - one > should look at optimising or troubleshooting things, not destroying > guests. I am half-tempted to suggest increasing this to 10 minutes > actually. > > 2. Change the default behaviour of the "stop" option to do a managedsave > on all running and paused guests - as this is safer for all guest > operating systems - and the duration is more predictable (no Windows > automatic updates to install during shutdown etc.) > > 3. Added a guests_shutdown option, for those preferring to do a full > shutdown instead of a managedsave (not enough space on hdd to save ram > images, for example). So rc.local_shutdown would contain: > > /etc/rc.d/rc.libvirt guests_shutdown > /etc/rc.d/rc.libvirt stop > > 4. Added a guests_reboot option, to reboot all running guests. I find > this really useful, as, for example, Windows guests need regular reboots > to stop them from going bananas - so an option to reboot all of them at > once seems like a useful addition. This doesn't wait and doesn't have a > timeout - just issues the command and exits. The idea is that this > wouldn't be used during a reboot, so there is no need to check when the > command has finished executing. > > Note: when issuing the managedsave command, the guests go first through > a 'paused' state, then they show up as 'shut off' in virsh --list. Thus > it is impossible to tell between the guests which were already paused > initially, and the ones in transition to the managedsave state, while > waiting for the command to complete. Because of this, the only way to > proceed is to issue a 'managedsave' on both running and already paused > guests. > > On the other hand, 'guests_shutdown' only acts on running guests - an > ACPI shutdown command is unlikely to be acted on by a paused guest anyway. > > I also suggest adding the following notes to libvirt-info: > > "The enclosed rc.libvirt script will to a 'managedsave' on all running > and paused guests when issuing 'rc.libvirt stop'. Please note that this > saves the RAM of each guest to the host hdd (by default under > /var/lib/libvirt/qemu/save) - so make sure enough space is available. If > you prefer to perform a full shutdown on all running guests instead, > issue a 'rc.libvirt guests_shutdown' followed by 'rc.libvirt shutdown'. > > By default 'rc.libvirt stop' and 'rc.libvirt guests_shutdown' will wait > a maximum of 5 minutes for all guests to shutdown, after which any > guests still running will be destroyed. Adjust this to a suitable value > for your system, as destroying a running guest carries a high risk of > data loss! > > There is also a 'guests_reboot' for rebooting all running guests." Has anybody had a chance to see/test this? From artourter at gmail.com Tue May 30 22:00:14 2017 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 30 May 2017 23:00:14 +0100 Subject: [Slackbuilds-users] redshift package in accepted Message-ID: Could an admin remove the redshift slackbuild from accepted, I want to submit a corrected version. Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Wed May 31 04:03:52 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 30 May 2017 23:03:52 -0500 Subject: [Slackbuilds-users] Question about git workflow In-Reply-To: <20170305194930.v45xub6ojs4vcgrw@SDF.ORG> References: <3a96c626-cfb4-e5b0-6b2f-8c1edf7d56d2@slackbuilds.org> <0d06b15e-e320-d893-4486-cf9c4bef631f@osh.id.au> <614a9f92-2e35-09d3-7107-25e8bc23c22c@slackbuilds.org> <1c77f136-3ac2-6d0e-62d2-696470406a02@slackbuilds.org> <20170305194930.v45xub6ojs4vcgrw@SDF.ORG> Message-ID: <20170530230352.6a7348d8@home.rlworkman.net> On Sun, 5 Mar 2017 19:49:30 +0000 klaatu la terible wrote: > I can't help but ask, what's the deciding factor on who gets a > branch? I'd love to be able to update my builds with git. I missed this before - send me a pubkey and desired username. -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 lems at gmx.net Wed May 31 09:35:52 2017 From: lems at gmx.net (Leonard Schmidt) Date: Wed, 31 May 2017 11:35:52 +0200 Subject: [Slackbuilds-users] ctwm 4.0.0: ctwm.path.diff.gz no longer needed Message-ID: <0Lb5nF-1deMYl0p3Z-00kdi1@mail.gmx.com> Hello, I just had a look at the willysr branch: I did not include it with my updated tarball and thought this would suffice to get it deleted, but anyway, ctwm.path.diff.gz is no longer required, and can be deleted from the .../desktop/ctwm directory. I should have mentioned this when submitting, my apologies. Best regards Leonard From willysr at slackbuilds.org Wed May 31 10:28:50 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 31 May 2017 17:28:50 +0700 Subject: [Slackbuilds-users] redshift package in accepted In-Reply-To: References: Message-ID: > Could an admin remove the redshift slackbuild from accepted, I want to > submit a corrected version. Done you can resubmit 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 willysr at slackbuilds.org Wed May 31 10:29:24 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 31 May 2017 17:29:24 +0700 Subject: [Slackbuilds-users] ctwm 4.0.0: ctwm.path.diff.gz no longer needed In-Reply-To: <0Lb5nF-1deMYl0p3Z-00kdi1@mail.gmx.com> References: <0Lb5nF-1deMYl0p3Z-00kdi1@mail.gmx.com> Message-ID: <7ae104f2-ba43-0db5-5928-1dc248980fcd@slackbuilds.org> > I just had a look at the willysr branch: > > I did not include it with my updated tarball and thought this would > suffice to get it deleted, but anyway, ctwm.path.diff.gz is no longer > required, and can be deleted from the .../desktop/ctwm directory. > > I should have mentioned this when submitting, my apologies. Hi Leonard I apologize for not spotting that change. It's now removed on my branch Thanks for noticing -- 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 slackph at posteo.de Wed May 31 11:36:48 2017 From: slackph at posteo.de (Philip Lacroix) Date: Wed, 31 May 2017 13:36:48 +0200 Subject: [Slackbuilds-users] templates and guidelines In-Reply-To: References: Message-ID: <1a57e86186c6af36321671466ce99094@posteo.de> Am 29.05.2017 19:28 schrieb Petar Petrov: > How about guidelines about package file install locations? (...) > for example: > - when is it advisable to install things to /opt Am 30.05.2017 18:56 schrieb B Watson: > Guidelines about file locations: I'd say you should only use /opt when > your build is for something that might conflict with stock Slackware > packages. Example, mozjpeg installs libraries and binaries with the > same > names as stuff from Slack's libjpeg-turbo package. Hi everybody Interesting topic. As far as I can see, there can be at least another reason for using /opt, i.e. when the software installs by default into a single directory, and does not offer any reasonable way to set different paths where the files should go to. With "reasonable" I mean something like running configure scripts, or patching makefiles. When the code itself has to be patched in order to comply with the FHS, things can start to look intricate IMHO. For example, in my updated SlackBuild for zyGrib I have managed to make it FHS- compliant, and apparently I didn't brake anything, but the software clearly wasn't designed with that in mind: by default one has to "cd" into a main directory containing everything, and run the executable from there in order to make it work properly (because of relative paths inside the code). The makefile even creates and installs a simple startup script to work around that. I wonder if for more complex software, like sage, using /opt might be the only viable (although not elegant) option? The same for some binary relases, as in the blender SlackBuild. Cheers Philip From atelszewski at gmail.com Wed May 31 21:19:33 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 31 May 2017 23:19:33 +0200 Subject: [Slackbuilds-users] Qt 5.9 LTS released Message-ID: Hi, Just to let you know, Qt 5.9 LTS has been released. If you plan to update the SBo version, pcre2 should be added to REQUIRES, otherwise, the bundled source for pcre2 will be used. Not that I built Qt 5.9 or tested it or whatever. Just a heads up. Cheers. -- Best regards, Andrzej Telszewski