From kingbeowulf at gmail.com Mon Aug 1 02:10:34 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 31 Jul 2016 19:10:34 -0700 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. Message-ID: Hello I decided to test qemu with Windows 10 (upgrade from a Windows 7 VM). Windows XP and 7 so far under various qemu version have been fine. My host is Slackware64-14.2 multilib. I get this error, and the qemu window freezes: main-loop: WARNING: I/O thread spun for 1000 iterations similar to: https://bugs.launchpad.net/qemu/+bug/1481272 If anyone has any ideas, shoot me an email. Thanks -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Mon Aug 1 05:12:32 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 1 Aug 2016 15:12:32 +1000 Subject: [Slackbuilds-users] paraview, mpich Message-ID: <1f44d16e-bdd7-d9e3-7fe3-641ea7ef9fa1@iinet.net.au> Last week I emailed the respective maintainers of the paraview and mpich SlackBuilds about updating them. In particular, the version for paraview is quite old; moreover, it appears to just repackage a personally built & hosted binary (which is no longer reachable anyway). There have been no responses to those emails yet and if there are none by, say, Thursday of this week (and no one else objects), I'd like to take over maintainership of the paraview and mpich SlackBuilds and submit up to date, "build from source" updates for them. chris From villa.ballester at gmail.com Mon Aug 1 02:41:33 2016 From: villa.ballester at gmail.com (Edgardo P) Date: Sun, 31 Jul 2016 23:41:33 -0300 Subject: [Slackbuilds-users] transmission messes up permissions Message-ID: I installed transmission in Slackware64 14.2 and changed lots of permissions, making the system unusable for non root users. I have a log from the build script, but I'm not sure if I have to attach it here or not. I could fix this partially reinstalling aaa_base, but X is broken too. From rworkman at slackbuilds.org Mon Aug 1 06:50:43 2016 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 1 Aug 2016 01:50:43 -0500 Subject: [Slackbuilds-users] transmission messes up permissions In-Reply-To: References: Message-ID: <20160801015043.2036d6a4@home.rlworkman.net> On Sun, 31 Jul 2016 23:41:33 -0300 Edgardo P wrote: > I installed transmission in Slackware64 14.2 and changed lots of > permissions, making the system unusable for non root users. > > I have a log from the build script, but I'm not sure if I have to > attach it here or not. > > I could fix this partially reinstalling aaa_base, but X is broken too. I just built transmission and the package has correct permissions throughout. I'm reasonably certain that one of these two things is the case: 1) Your normal user account has a non-standard umask setting, i.e. NOT 0022, which is fine on its own, but when you switched to root to build the package, you used "su" as as opposed to "su -" and root's umask didn't get set. 2) Your root account has a non-standard umask setting, i.e. NOT 0022, which is NOT fine. You should be able to fix it with something like this: for i in $(tar tf /tmp/transmission-2.92-x86_64-1_SBo.tgz | grep /$); do [ -d /$i ] && chmod 0755 /$i ; done chmod 1777 /tmp rm -rf /tmp/* reboot -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 gilles at click-hack.org Mon Aug 1 20:54:18 2016 From: gilles at click-hack.org (Gilles Chanteperdrix) Date: Mon, 1 Aug 2016 22:54:18 +0200 Subject: [Slackbuilds-users] upgrade to 14.2 Message-ID: <20160801205418.fv72hdh4k3kc3hj3@hermes.click-hack.org> Hi, I just upgraded to 14.2, and everything went fine. Congratulations to everyone for the good work. Among the many slackbuild packages update which worked, I had a few glitches which I thought I should report: - the exim slackbuild tries to download the 4.86.2 tarball, but this version is no longer the latest stable so the URL in the slackbuild is no longer valid, it should be: ftp://ftp.exim.org/pub/exim/exim4/old/exim-4.86.2.tar.bz2 instead of ftp://ftp.exim.org/pub/exim/exim4/exim-4.86.2.tar.bz2 - the kwalletcli package is missing a dependency on mksh. The pinentry-kwallet script is an mksh script. Regards. -- Gilles. From thomas at beingboiled.info Mon Aug 1 22:40:38 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 2 Aug 2016 00:40:38 +0200 (CEST) Subject: [Slackbuilds-users] upgrade to 14.2 In-Reply-To: <20160801205418.fv72hdh4k3kc3hj3@hermes.click-hack.org> References: <20160801205418.fv72hdh4k3kc3hj3@hermes.click-hack.org> Message-ID: On Mon, 1 Aug 2016, Gilles Chanteperdrix wrote: > - the exim slackbuild tries to download the 4.86.2 tarball, but this > version is no longer the latest stable so the URL in the slackbuild > is no longer valid, it should be: > ftp://ftp.exim.org/pub/exim/exim4/old/exim-4.86.2.tar.bz2 No more need for that because I submitted an update to Exim 4.87 just yesterday :-) -- From dpross1100 at msn.com Tue Aug 2 01:13:59 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 2 Aug 2016 01:13:59 +0000 Subject: [Slackbuilds-users] Update download link in openssh-krb5 Message-ID: Hi, The download link for openssh-krb5 gives a 404 error. Version 6.7p1 is no longer available on that site, but 7.2p2 is. I can confirm that it builds with no changes to the SlackBuild other than the version bump. Here are patches for that. Dan -------------- next part -------------- A non-text attachment was scrubbed... Name: openssh-krb5.info.patch Type: text/x-patch Size: 582 bytes Desc: openssh-krb5.info.patch URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: openssh-krb5.SlackBuild.patch Type: text/x-patch Size: 293 bytes Desc: openssh-krb5.SlackBuild.patch URL: From willysr at slackbuilds.org Tue Aug 2 01:26:35 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 2 Aug 2016 08:26:35 +0700 Subject: [Slackbuilds-users] Update download link in openssh-krb5 In-Reply-To: References: Message-ID: <21169f9d-028a-14c5-4384-db3daa9260ab@slackbuilds.org> > The download link for openssh-krb5 gives a 404 error. Version 6.7p1 is no > longer available on that site, but 7.2p2 is. I can confirm that it builds with > no changes to the SlackBuild other than the version bump. Here are patches for > that. Thanks I forgot to bump this package during development Now it's sync'ed with Slackware's OpenSSH version -- 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 jaxartes.net Tue Aug 2 02:56:58 2016 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Mon, 1 Aug 2016 19:56:58 -0700 Subject: [Slackbuilds-users] upgrade to 14.2 In-Reply-To: <20160801205418.fv72hdh4k3kc3hj3@hermes.click-hack.org> References: <20160801205418.fv72hdh4k3kc3hj3@hermes.click-hack.org> Message-ID: <02fa4a75-9473-af42-c7f4-45fd5430371f@jaxartes.net> On 01/08/16 01:54 PM, Gilles Chanteperdrix wrote: > - the kwalletcli package is missing a dependency on mksh. The > pinentry-kwallet script is an mksh script. Fixed, thanks! From s.arcus at open-t.co.uk Tue Aug 2 15:52:42 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 2 Aug 2016 16:52:42 +0100 Subject: [Slackbuilds-users] Segmentation fault when trying to build SpamAssassin Message-ID: <8ef93225-f7ee-ba37-4407-418f1bd127e8@open-t.co.uk> I am getting a segmentation fault when trying to build SpamAssassin from SBo. The machine specs are: Perl 5.22.2 Slackware 64 bits - updated about 2 weeks ago, after 14.2 release Kernel 4.4.14 The error is: ./spamassassin.SlackBuild: line 78: 1854 Segmentation fault PERL_MM_USE_DEFAULT=1 perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor INSTALLVENDORMAN1DIR=/usr/man/man1 INSTALLVENDORMAN3DIR=/usr/man/man3 I've tried on two different machines, with similar spec and software versions - and get the same error. Has anybody else seen this? As these machines were upgraded, not freshly installed, could it be something to do with older perl modules still floating about? Could anybody check to see if SpamAssassin still builds against a current install please. From willysr at slackbuilds.org Tue Aug 2 16:00:07 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 2 Aug 2016 23:00:07 +0700 Subject: [Slackbuilds-users] Segmentation fault when trying to build SpamAssassin In-Reply-To: <8ef93225-f7ee-ba37-4407-418f1bd127e8@open-t.co.uk> References: <8ef93225-f7ee-ba37-4407-418f1bd127e8@open-t.co.uk> Message-ID: > I am getting a segmentation fault when trying to build SpamAssassin from > SBo. The machine specs are: > > Perl 5.22.2 > Slackware 64 bits - updated about 2 weeks ago, after 14.2 release > Kernel 4.4.14 > > The error is: > > ./spamassassin.SlackBuild: line 78: 1854 Segmentation fault > PERL_MM_USE_DEFAULT=1 perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor > INSTALLVENDORMAN1DIR=/usr/man/man1 INSTALLVENDORMAN3DIR=/usr/man/man3 > > I've tried on two different machines, with similar spec and software > versions - and get the same error. Has anybody else seen this? As these > machines were upgraded, not freshly installed, could it be something to > do with older perl modules still floating about? Could anybody check to > see if SpamAssassin still builds against a current install please. Try this remove all perl packages from SBo and reinstall SpamAssassin along with all the deps from scratch. As ponce said many times, perl in 14.2 is not fully backward compatible with 14.1 so all perl packages must be recompiled against 14.2's perl -- 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 Tue Aug 2 19:24:25 2016 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Tue, 2 Aug 2016 14:24:25 -0500 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. In-Reply-To: References: Message-ID: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> On 07/31/2016 09:10 PM, King Beowulf wrote: > Hello > > I decided to test qemu with Windows 10 (upgrade from a Windows 7 VM). > Windows XP and 7 so far under various qemu version have been fine. My > host is Slackware64-14.2 multilib. > > I get this error, and the qemu window freezes: > > main-loop: WARNING: I/O thread spun for 1000 iterations > > similar to: https://bugs.launchpad.net/qemu/+bug/1481272 > > If anyone has any ideas, shoot me an email. Thanks > > -Ed > Hey Ed I have an issue with qemu-2.6 and Windows guests (2003, XP, 7, 2012) on physical Slackware64 14.2 and Slackware 14.2 servers. My problem is disk writes are *extremely slow*, to the point that I can't even start the installer because the "Starting Windows..." screen never goes away. I've tried it on different pieces of hardware but have not had any luck yet. In my case, qemu-2.4 works just fine on 14.1 and 14.2, so I've reverted to that. I'll do some testing over the weekend and see if I can track down what's causing this. -- 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 kingbeowulf at gmail.com Wed Aug 3 06:43:16 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 2 Aug 2016 23:43:16 -0700 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. In-Reply-To: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> References: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> Message-ID: On 08/02/2016 12:24 PM, Gerardo Zamudio wrote: .... > > Hey Ed > > I have an issue with qemu-2.6 and Windows guests (2003, XP, 7, 2012) on > physical Slackware64 14.2 and Slackware 14.2 servers. My problem is disk > writes are *extremely slow*, to the point that I can't even start the > installer because the "Starting Windows..." screen never goes away. I've > tried it on different pieces of hardware but have not had any luck yet. > In my case, qemu-2.4 works just fine on 14.1 and 14.2, so I've reverted > to that. I'll do some testing over the weekend and see if I can track > down what's causing this. > Are you host-mode or full emulation? KVM modules loaded? Note that qemu upstream fiddles with the options quite a bit. For example, for 7 and 10, I use: qemu-system-x86_64 -enable-kvm -machine accel=kvm -m 8G \ -hda windows7.img -cdrom /dev/dvd -boot order=cd \ -cpu host -smp 4 -name "Windows7pro64" -soundhw hda \ -vga std -sdl -display gtk -usb \ -netdev user,id=mynet1,hostname=win7vm,smb=/games/win32/ \ -device virtio-net-pci,netdev=mynet1,mac=52:54:00:35:a6:50 (some redundancy but meh...) also, what image file (qcow2 etc) set up is can impact performance as well as your host hard drive configuration and format. My hard drive speed with qemu-2.6 in XP, 7 and 10 is not stellar, but plenty good enough. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From cary at SDF.ORG Wed Aug 3 09:11:18 2016 From: cary at SDF.ORG (Cary) Date: Wed, 3 Aug 2016 09:11:18 +0000 Subject: [Slackbuilds-users] qemu-2.6.0-x86_64 looks for library dependency Message-ID: <20160803091118.GA24629@SDF.ORG> Hello, and thanks to everyone for maintaining the repository. After upgrading qemu from 2.4.1 to 2.6.0 on Slackware64-14.2 I got the error 'qemu-system-i386: error while loading shared libraries: libcacard.so.0: cannot open shared object file: No such file or directory' and vm would not start. Installed the libcacard slackbuild and now qemu is running again, but the README still says that library should be optional. Has something changed or did I make a mistake? -- cary at sdf.org SDF Public Access UNIX System - http://sdf.org From atelszewski at gmail.com Wed Aug 3 09:15:57 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 3 Aug 2016 11:15:57 +0200 Subject: [Slackbuilds-users] qemu-2.6.0-x86_64 looks for library dependency In-Reply-To: <20160803091118.GA24629@SDF.ORG> References: <20160803091118.GA24629@SDF.ORG> Message-ID: <64e80427-d2be-8047-9b3e-8da2331b745f@gmail.com> On 03/08/16 11:11, Cary wrote: > Hello, and thanks to everyone for maintaining the repository. > > After upgrading qemu from 2.4.1 to 2.6.0 on Slackware64-14.2 I got the error > > 'qemu-system-i386: error while loading shared libraries: libcacard.so.0: cannot open shared object file: No such file or > directory' > > and vm would not start. Installed the libcacard slackbuild and now qemu is running again, > but the README still says that library should be optional. Has something changed or did I make a mistake? > Looks like you have mistaken something ;) I'm running 2.6.0 without libcacard installed. -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Wed Aug 3 09:19:37 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 3 Aug 2016 11:19:37 +0200 Subject: [Slackbuilds-users] qemu-2.6.0-x86_64 looks for library dependency In-Reply-To: <20160803091118.GA24629@SDF.ORG> References: <20160803091118.GA24629@SDF.ORG> Message-ID: 2016-08-03 11:11 GMT+02:00 Cary : > Hello, and thanks to everyone for maintaining the repository. > > After upgrading qemu from 2.4.1 to 2.6.0 on Slackware64-14.2 I got the error > > 'qemu-system-i386: error while loading shared libraries: libcacard.so.0: cannot open shared object file: No such file or > directory' > > and vm would not start. Installed the libcacard slackbuild and now qemu is running again, > but the README still says that library should be optional. Has something changed or did I make a mistake? Hi Cary, SlackBuilds.org doesn't provide a repository of binary packages so I think you got your package elsewhere... https://slackbuilds.org/faq/#packages I suppose you got a package and not run our SlackBuild because of the error ("error while loading shared libraries"), that should come from a qemu package built against libcacard. and yes, libcacard is an optional dependency when you build qemu from source. Matteo From powtrix at gmail.com Wed Aug 3 10:19:36 2016 From: powtrix at gmail.com (powtrix) Date: Wed, 3 Aug 2016 07:19:36 -0300 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. In-Reply-To: References: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> Message-ID: About qemu/virt-manager, Any way to load the VM with two monitors? I tried to add 2 qxl devices, but the VM just loads in one monitor. The output are VGA and displayport. Em 3 de ago de 2016 03:43, "King Beowulf" escreveu: > On 08/02/2016 12:24 PM, Gerardo Zamudio wrote: > .... > > > > Hey Ed > > > > I have an issue with qemu-2.6 and Windows guests (2003, XP, 7, 2012) on > > physical Slackware64 14.2 and Slackware 14.2 servers. My problem is disk > > writes are *extremely slow*, to the point that I can't even start the > > installer because the "Starting Windows..." screen never goes away. I've > > tried it on different pieces of hardware but have not had any luck yet. > > In my case, qemu-2.4 works just fine on 14.1 and 14.2, so I've reverted > > to that. I'll do some testing over the weekend and see if I can track > > down what's causing this. > > > > Are you host-mode or full emulation? KVM modules loaded? Note that > qemu upstream fiddles with the options quite a bit. For example, for 7 > and 10, I use: > > qemu-system-x86_64 -enable-kvm -machine accel=kvm -m 8G \ > -hda windows7.img -cdrom /dev/dvd -boot order=cd \ > -cpu host -smp 4 -name "Windows7pro64" -soundhw hda \ > -vga std -sdl -display gtk -usb \ > -netdev user,id=mynet1,hostname=win7vm,smb=/games/win32/ \ > -device virtio-net-pci,netdev=mynet1,mac=52:54:00:35:a6:50 > > (some redundancy but meh...) > > also, what image file (qcow2 etc) set up is can impact performance as > well as your host hard drive configuration and format. > > My hard drive speed with qemu-2.6 in XP, 7 and 10 is not stellar, but > plenty good enough. > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Aug 3 10:51:58 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 3 Aug 2016 12:51:58 +0200 Subject: [Slackbuilds-users] qemu-2.6.0-x86_64 looks for library dependency In-Reply-To: <64e80427-d2be-8047-9b3e-8da2331b745f@gmail.com> References: <20160803091118.GA24629@SDF.ORG> <64e80427-d2be-8047-9b3e-8da2331b745f@gmail.com> Message-ID: ah, maybe I understand what probably happened: you built qemu 2.6.0 having already installed qemu 2.4.x. version 2.4.x still included libcacard, that from version 2.5.x has been moved in a separate package. so it can be that you built against it, then when you upgraded the qemu package with 2.6.0 you removed libcacard together with qemu 2.4.1. Matteo From gerardo.zamudio at linux.com Wed Aug 3 14:28:03 2016 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 3 Aug 2016 09:28:03 -0500 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. In-Reply-To: References: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> Message-ID: <2c9973e1-7218-03a8-ec6f-421229d17e4f@linux.com> On 08/03/2016 01:43 AM, King Beowulf wrote: > On 08/02/2016 12:24 PM, Gerardo Zamudio wrote: > > Are you host-mode or full emulation? KVM modules loaded? Note that > qemu upstream fiddles with the options quite a bit. For example, for 7 > and 10, I use: > > qemu-system-x86_64 -enable-kvm -machine accel=kvm -m 8G \ > -hda windows7.img -cdrom /dev/dvd -boot order=cd \ > -cpu host -smp 4 -name "Windows7pro64" -soundhw hda \ > -vga std -sdl -display gtk -usb \ > -netdev user,id=mynet1,hostname=win7vm,smb=/games/win32/ \ > -device virtio-net-pci,netdev=mynet1,mac=52:54:00:35:a6:50 > > (some redundancy but meh...) > > also, what image file (qcow2 etc) set up is can impact performance as > well as your host hard drive configuration and format. > > My hard drive speed with qemu-2.6 in XP, 7 and 10 is not stellar, but > plenty good enough. > I'm using full emulation and KVM modules are loaded. I've tried various combinations of virtual hardware (IDE, SATA, etc), disk drivers (virtio, , cache settings, image types, etc. I use virt-manager to create and manage my virtual machines. On my system I can do installpkg qemu-2.4 , and a new Windows installation is complete in less than 10 minutes removepkg qemu-2.4 installpkg qemu-2.6 , and a new Windows install is stuck in "Starting Windows..." Note that both packages were built on fresh systems using the SlackBuilds (install Slackware 14.2, build qemu-2.4, wipe drive, install Slackware 14.2, build qemu-2.6). I've tried building both packages from source on fresh systems on different hardware but I get the same results. It may have something to do with the build options. Using your example, I have the same problem on 2 different hardware : qemu-system-x86_64 -enable-kvm -machine accel=kvm -m 4G \ -hda .virtualmachines/win7.img \ -cdrom .iso/Windows7Professionalx64SP1.iso \ -boot order=cd -cpu host -smp 4 -name "Windows7pro64" \ -soundhw hda -vga std -sdl -display gtk \ -usb -netdev user,id=mynet1,hostname=win7vm \ -device virtio-net-pci,netdev=mynet1,mac=52:54:00:35:a6:50 Do you have a copy of your qemu-2.6 binary? I'm willing to give that a go. It should help me figure out if I'm doing something wrong -- 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 erik at slackbuilds.org Wed Aug 3 14:53:20 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 3 Aug 2016 09:53:20 -0500 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. In-Reply-To: <2c9973e1-7218-03a8-ec6f-421229d17e4f@linux.com> References: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> <2c9973e1-7218-03a8-ec6f-421229d17e4f@linux.com> Message-ID: <20160803095320.1aec5547@shaggy.doo> On Wed, 3 Aug 2016 09:28:03 -0500 Gerardo Zamudio wrote: > installpkg qemu-2.6 , and a new Windows install is stuck in "Starting > Windows..." I was having the same problem, and got past it by switching the video to Cirrus. -- Erik From cary at SDF.ORG Wed Aug 3 15:49:37 2016 From: cary at SDF.ORG (Cary) Date: Wed, 3 Aug 2016 15:49:37 +0000 Subject: [Slackbuilds-users] qemu-2.6.0-x86_64 looks for library dependency In-Reply-To: References: <20160803091118.GA24629@SDF.ORG> <64e80427-d2be-8047-9b3e-8da2331b745f@gmail.com> Message-ID: <20160803154937.GA15835@SDF.ORG> On Wed, Aug 03, 2016 at 12:51:58PM +0200, Matteo Bernardini wrote: > ah, maybe I understand what probably happened: you built qemu 2.6.0 > having already installed qemu 2.4.x. > version 2.4.x still included libcacard, that from version 2.5.x has > been moved in a separate package. > so it can be that you built against it, then when you upgraded the > qemu package with 2.6.0 you removed libcacard together with qemu > 2.4.1. > > Matteo > That is what ocurred. The library uninstalled with qemu-2.4.1 . It was there and I did not know but configure did. :( $ grep libc /tmp/SBo/qemu-2.[46]*/Makefile /tmp/SBo/qemu-2.4.1/Makefile:include $(SRC_PATH)/libcacard/Makefile Thank you very much Andrzej and Matteo ! -- cary at sdf.org SDF Public Access UNIX System - http://sdf.org From gerardo.zamudio at linux.com Wed Aug 3 16:31:03 2016 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 3 Aug 2016 11:31:03 -0500 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. In-Reply-To: <20160803095320.1aec5547@shaggy.doo> References: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> <2c9973e1-7218-03a8-ec6f-421229d17e4f@linux.com> <20160803095320.1aec5547@shaggy.doo> Message-ID: On 08/03/2016 09:53 AM, Erik Hanson wrote: > On Wed, 3 Aug 2016 09:28:03 -0500 > Gerardo Zamudio wrote: > > >> installpkg qemu-2.6 , and a new Windows install is stuck in "Starting >> Windows..." > > I was having the same problem, and got past it by switching the video > to Cirrus. > Shit, man. Issue resolved. I kept tackling the problem with hard disk configuration changes but didn't think video may be a problem. No idea why it works but thank you very much! -- 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 erik at slackbuilds.org Wed Aug 3 18:33:28 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 3 Aug 2016 13:33:28 -0500 Subject: [Slackbuilds-users] [Slackbulds-users] qemu-2.6.0 issue with Windows guests. In-Reply-To: References: <81fecdb3-6c2b-9314-7ead-85aadf9765d7@linux.com> <2c9973e1-7218-03a8-ec6f-421229d17e4f@linux.com> <20160803095320.1aec5547@shaggy.doo> Message-ID: <20160803133328.585d6f14@shaggy.doo> On Wed, 3 Aug 2016 11:31:03 -0500 Gerardo Zamudio wrote: > On 08/03/2016 09:53 AM, Erik Hanson wrote: > > On Wed, 3 Aug 2016 09:28:03 -0500 > > Gerardo Zamudio wrote: > > > > > >> installpkg qemu-2.6 , and a new Windows install is stuck in > >> "Starting Windows..." > > > > I was having the same problem, and got past it by switching the > > video to Cirrus. > > > > Shit, man. Issue resolved. I kept tackling the problem with hard disk > configuration changes but didn't think video may be a problem. No idea > why it works but thank you very much! Yep, same here. This was my first real attempt at getting QEMU (libvirt/virt-manager) going, to do some PCIe pass-through stuff. I googled something like qemu stuck "Starting Windows" and there was the answer, but no explanation why it works. Guess it's a regression in QEMU. -- Erik From unix_lists at f-m.fm Thu Aug 4 02:33:28 2016 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Wed, 03 Aug 2016 21:33:28 -0500 Subject: [Slackbuilds-users] I can no longer maintain Tor Message-ID: <1470278008.306446.685497097.6CC800A8@webmail.messagingengine.com> I can no longer maintain Tor. Sorry for any inconvenience. Donald Cooley From fernando.lopezjr at gmail.com Thu Aug 4 03:06:05 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 3 Aug 2016 21:06:05 -0600 Subject: [Slackbuilds-users] I can no longer maintain Tor In-Reply-To: <1470278008.306446.685497097.6CC800A8@webmail.messagingengine.com> References: <1470278008.306446.685497097.6CC800A8@webmail.messagingengine.com> Message-ID: i would like to take it... if no one else wants it... On Wed, Aug 3, 2016 at 8:33 PM, wrote: > I can no longer maintain Tor. Sorry for any inconvenience. > Donald Cooley > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Thu Aug 4 16:39:56 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 4 Aug 2016 17:39:56 +0100 Subject: [Slackbuilds-users] Segmentation fault when trying to build SpamAssassin In-Reply-To: References: <8ef93225-f7ee-ba37-4407-418f1bd127e8@open-t.co.uk> Message-ID: <307597c5-8270-ab50-618f-8ea56891b938@open-t.co.uk> On 02/08/16 17:00, Willy Sudiarto Raharjo wrote: >> I am getting a segmentation fault when trying to build SpamAssassin from >> SBo. The machine specs are: >> >> Perl 5.22.2 >> Slackware 64 bits - updated about 2 weeks ago, after 14.2 release >> Kernel 4.4.14 >> >> The error is: >> >> ./spamassassin.SlackBuild: line 78: 1854 Segmentation fault >> PERL_MM_USE_DEFAULT=1 perl Makefile.PL PREFIX=/usr INSTALLDIRS=vendor >> INSTALLVENDORMAN1DIR=/usr/man/man1 INSTALLVENDORMAN3DIR=/usr/man/man3 >> >> I've tried on two different machines, with similar spec and software >> versions - and get the same error. Has anybody else seen this? As these >> machines were upgraded, not freshly installed, could it be something to >> do with older perl modules still floating about? Could anybody check to >> see if SpamAssassin still builds against a current install please. > > Try this > remove all perl packages from SBo and reinstall SpamAssassin along with > all the deps from scratch. > > As ponce said many times, perl in 14.2 is not fully backward compatible > with 14.1 so all perl packages must be recompiled against 14.2's perl Thank you Willy and ponce. I just got round to trying this - I removed the all various CPAN dirs manually, as I previously installed modules using CPAN, then uninstalled and re-installed Perl and then re-installed all required modules. Now Spamassassin compiles fine. A bit of a pain, but it worked! Thank you From bch at shroggslodge.freeserve.co.uk Thu Aug 4 19:49:40 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Thu, 4 Aug 2016 20:49:40 +0100 Subject: [Slackbuilds-users] libofx with libxml++ present as optional dependency Message-ID: Hello slackbuild-users Slackware 14.2 64-bit I have just tried to build libofx after first installing libxml++ (optional dependency) and it failed with a few errors. If I remove the libxml++ package, libofx appears to build ok. Secondly, there is a patch applied in the build. The patch infers libofx0.9.5 and libofx source is 0.9.9 .... Is the patch required, because if the patch is commented out it still appears to build ? Sorry folks, I am able to get my head around using the builds etc, but the complexities of slackbuilds scripts, the many lines output from building and errors/warnings sometimes escapes me. Hopefully it is enough for me to just raise what I have for attention and comment. If anything else is required, let me know and I'll do my best. Regards. Peace and best wishes. Habs -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Thu Aug 4 20:12:59 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 4 Aug 2016 22:12:59 +0200 Subject: [Slackbuilds-users] libofx with libxml++ present as optional dependency In-Reply-To: References: Message-ID: 2016-08-04 21:49 GMT+02:00 : > Hello slackbuild-users > > Slackware 14.2 64-bit > > I have just tried to build libofx after first installing libxml++ (optional > dependency) and it failed with a few errors. > > If I remove the libxml++ package, libofx appears to build ok. > > Secondly, there is a patch applied in the build. The patch infers > libofx0.9.5 and libofx source is 0.9.9 .... Is the patch required, because > if the patch is commented out it still appears to build ? > > Sorry folks, I am able to get my head around using the builds etc, but the > complexities of slackbuilds scripts, the many lines output from building and > errors/warnings sometimes escapes me. Hopefully it is enough for me to just > raise what I have for attention and comment. > > If anything else is required, let me know and I'll do my best. > > Regards. Peace and best wishes. > Habs hi Habs, Niki already reported the issue related to building libofx against libxml++ a few days ago https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-July/016682.html and I already fixed it in my branch on our git https://slackbuilds.org/cgit/slackbuilds/commit/?id=ad93ab91eb1c52f95e6fe76333a171b980e3974f it will go in the main repository at the next merge (soon): if you wantto build it against libxml++, in the meantime, you can edit the SlackBuild and do that little change. Matteo From bch at shroggslodge.freeserve.co.uk Thu Aug 4 20:40:09 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Thu, 4 Aug 2016 21:40:09 +0100 Subject: [Slackbuilds-users] libofx with libxml++ present as optional dependency In-Reply-To: References: Message-ID: Thank you for the quick reply Matteo and the info provided. I am sorry, I missed the previous report of the issue. I will wait until it goes on the main repository :-). Regards and thank you Habs On 4 August 2016 at 21:12, Matteo Bernardini wrote: > 2016-08-04 21:49 GMT+02:00 : > > Hello slackbuild-users > > > > Slackware 14.2 64-bit > > > > I have just tried to build libofx after first installing libxml++ > (optional > > dependency) and it failed with a few errors. > > > > If I remove the libxml++ package, libofx appears to build ok. > > > > Secondly, there is a patch applied in the build. The patch infers > > libofx0.9.5 and libofx source is 0.9.9 .... Is the patch required, > because > > if the patch is commented out it still appears to build ? > > > > Sorry folks, I am able to get my head around using the builds etc, but > the > > complexities of slackbuilds scripts, the many lines output from building > and > > errors/warnings sometimes escapes me. Hopefully it is enough for me to > just > > raise what I have for attention and comment. > > > > If anything else is required, let me know and I'll do my best. > > > > Regards. Peace and best wishes. > > Habs > > hi Habs, > > Niki already reported the issue related to building libofx against > libxml++ a few days ago > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > 2016-July/016682.html > > and I already fixed it in my branch on our git > > https://slackbuilds.org/cgit/slackbuilds/commit/?id= > ad93ab91eb1c52f95e6fe76333a171b980e3974f > > it will go in the main repository at the next merge (soon): if you > wantto build it against libxml++, in the meantime, you can edit the > SlackBuild and do that little change. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricardo at palmtx.com.ar Thu Aug 4 21:52:11 2016 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Thu, 4 Aug 2016 18:52:11 -0300 Subject: [Slackbuilds-users] Question about new submission and updates Message-ID: <201608041852.11513.ricardo@palmtx.com.ar> Hello, I've been helping creating a slackBuild script for QOwnNotes (http://www.qownnotes.org/) and its developer offered to take care of maintainning it. It's a very rapidly developed software and the maintainer wanted to know if there's a way to automate submissions (e.g., a git pull request). The first submission could be made throught the form, but what are his possibilities for sending updates? Thank you in advance. -- 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 atelszewski at gmail.com Thu Aug 4 22:04:32 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 5 Aug 2016 00:04:32 +0200 Subject: [Slackbuilds-users] Question about new submission and updates In-Reply-To: <201608041852.11513.ricardo@palmtx.com.ar> References: <201608041852.11513.ricardo@palmtx.com.ar> Message-ID: On 04/08/16 23:52, Ricardo J. Barberis wrote: > Hello, > > I've been helping creating a slackBuild script for QOwnNotes > (http://www.qownnotes.org/) and its developer offered to take care of > maintainning it. > > It's a very rapidly developed software and the maintainer wanted to know if > there's a way to automate submissions (e.g., a git pull request). > > The first submission could be made throught the form, but what are his > possibilities for sending updates? > > Thank you in advance. > Just a note: one thing is how often you're able to send the update, another is how often SBo team update the public repository. -- Best regards, Andrzej Telszewski From gerardo.zamudio at linux.com Thu Aug 4 22:39:45 2016 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Thu, 4 Aug 2016 17:39:45 -0500 Subject: [Slackbuilds-users] Question about new submission and updates In-Reply-To: <201608041852.11513.ricardo@palmtx.com.ar> References: <201608041852.11513.ricardo@palmtx.com.ar> Message-ID: On 08/04/2016 04:52 PM, Ricardo J. Barberis wrote: > Hello, > > I've been helping creating a slackBuild script for QOwnNotes > (http://www.qownnotes.org/) and its developer offered to take care of > maintainning it. > Props to that developer for offering to maintain a SlackBuild for Slackware. Several people on this list have git access. I'm sure the admins can work something out for the QOwnNotes developer. -- 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 ricardo at palmtx.com.ar Thu Aug 4 23:07:08 2016 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Thu, 4 Aug 2016 20:07:08 -0300 Subject: [Slackbuilds-users] Question about new submission and updates In-Reply-To: References: <201608041852.11513.ricardo@palmtx.com.ar> Message-ID: <201608042007.08255.ricardo@palmtx.com.ar> El Jueves 04/08/2016, Gerardo Zamudio escribi?: > On 08/04/2016 04:52 PM, Ricardo J. Barberis wrote: > > Hello, > > > > I've been helping creating a slackBuild script for QOwnNotes > > (http://www.qownnotes.org/) and its developer offered to take care of > > maintainning it. > > Props to that developer for offering to maintain a SlackBuild for > Slackware. Yeah, the slackbuild doesn't change much so he regenerates it from templates, updating VERSION, DOWNLOAD and MD5SUM. I guess it's all automated because he maintains packages for several other distros, but I beta test it regularly so I can vouch for it :) > Several people on this list have git access. I'm sure the admins can work > something out for the QOwnNotes developer. That'd be great :) But if it can't be automated, I could from time to time submit a version that I test and use and point brave users to the "official" slackbuild on qownnotes.org (which would be modified, as right now it uses SBo as a TAG). Cheers, -- 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 fernando.lopezjr at gmail.com Thu Aug 4 23:59:21 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 4 Aug 2016 17:59:21 -0600 Subject: [Slackbuilds-users] Question about new submission and updates In-Reply-To: <201608042007.08255.ricardo@palmtx.com.ar> References: <201608041852.11513.ricardo@palmtx.com.ar> <201608042007.08255.ricardo@palmtx.com.ar> Message-ID: qownnotes looks nice... i will start using it... =) On Thu, Aug 4, 2016 at 5:07 PM, Ricardo J. Barberis wrote: > El Jueves 04/08/2016, Gerardo Zamudio escribi?: > > On 08/04/2016 04:52 PM, Ricardo J. Barberis wrote: > > > Hello, > > > > > > I've been helping creating a slackBuild script for QOwnNotes > > > (http://www.qownnotes.org/) and its developer offered to take care of > > > maintainning it. > > > > Props to that developer for offering to maintain a SlackBuild for > > Slackware. > > Yeah, the slackbuild doesn't change much so he regenerates it from > templates, > updating VERSION, DOWNLOAD and MD5SUM. > > I guess it's all automated because he maintains packages for several other > distros, but I beta test it regularly so I can vouch for it :) > > > Several people on this list have git access. I'm sure the admins can work > > something out for the QOwnNotes developer. > > That'd be great :) > > But if it can't be automated, I could from time to time submit a version > that > I test and use and point brave users to the "official" slackbuild on > qownnotes.org (which would be modified, as right now it uses SBo as a > TAG). > > Cheers, > -- > 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 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Aug 5 00:25:20 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 5 Aug 2016 07:25:20 +0700 Subject: [Slackbuilds-users] Question about new submission and updates In-Reply-To: <201608041852.11513.ricardo@palmtx.com.ar> References: <201608041852.11513.ricardo@palmtx.com.ar> Message-ID: > I've been helping creating a slackBuild script for QOwnNotes > (http://www.qownnotes.org/) and its developer offered to take care of > maintainning it. > > It's a very rapidly developed software and the maintainer wanted to know if > there's a way to automate submissions (e.g., a git pull request). > > The first submission could be made throught the form, but what are his > possibilities for sending updates? Hi Ricardo public updates are regularly pushed around weekend (my personal schedule) and unplanned schedule (critical security fix) may be pushed if necessary. The maintainer can use the submission form as usual, or git pull request is OK for me as well as long as it's just a version bump. A major change will have to go through the submission form IMHO. -- 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 alik at ejik.org Fri Aug 5 00:25:46 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 05 Aug 2016 03:25:46 +0300 Subject: [Slackbuilds-users] a question on compilation of html In-Reply-To: <20160730195544.755f1cd8@home.rlworkman.net> References: <1469925456.3535973.681460257.35A149E1@webmail.messagingengine.com> <20160730195544.755f1cd8@home.rlworkman.net> Message-ID: <1470356746.1568324.686491673.73EEA5BD@webmail.messagingengine.com> On Sun, Jul 31, 2016, at 03:55, Robby Workman wrote: > On Sun, 31 Jul 2016 03:37:36 +0300 > Alexander Verbovetsky wrote: > > > Hello, > > > > I'd like to ask for an advice. > > > > I'm doing a slackbuild for REDUCE (http://reduce-algebra.sf.net). > > > > The source contains the tex-files for REDUCE manual and during the > > build they are compiled to pdf and html. The problem is related to > > the html, which is created with TeX4ht. To have TeX4ht the user > > needs texlive. > > > > I see here 2 possibilities: > > > > 1. Compile HTML only if TeX4ht is installed and put to the README > > something like: > > ----- > > NOTE: TeX4ht (a part of the texlive package available at > > SlackBuilds.org) is used to build the REDUCE manual in HTML format. > > It is not built if TeX4ht is not found on the system. The manual in > > PDF format is built anyway. The HTML manual is also available on the > > REDUCE homepage: > > http://reduce-algebra.sourceforge.net/manual/manual.html ----- > > > > 2. Add the compiled html-manual to the source tarball. The source in > > any case will be hosted on Ryan's slackbuildsdirectlinks.sf.net > > because the source code is available via svn only. > > > > What is the right way handle this situation? > > Either approach seems fine to me, but I'd lean toward #1. Thank you! I will follow approach 1. Alexander From bryanlharris at gmail.com Fri Aug 5 18:17:31 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Fri, 5 Aug 2016 14:17:31 -0400 Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: <20160805174735.5853265.70380.2014@gmail.com> References: <20160805174735.5853265.70380.2014@gmail.com> Message-ID: Hi all, Would it be alright for me to take over maintaining the monit package? I emailed the author (forwarded below) who says he is not the maintainer anymore. I would like to "upstreamify" the package (if you take the meaning). What I want to do is make it behave "out of the box" like the monit author (and me) would like to use it normally. The main thing being to make the "monit " commands work by way of renaming the config back to the the default name hard-coded into monit. The default name is monitrc as opposed to monit.conf (Red Hat uses that name but they patched the source code to make it work right). E.g. monit summary, monit status, monit start , monit stop , etc. Those commands work with the config named monitrc, but not if the config named monit.conf. Funny thing is I emailed Willy a while back to change it to monit.conf based on the rc.monit saying monit.conf. Only now I realize I was pushing the wrong direction. I should have gone the other way. My changes are below. Or is there a better way to submit the changes? V/r, Bryan diff --git a/system/monit/doinst.sh b/system/monit/doinst.sh index 293507c..3cac70a 100644 --- a/system/monit/doinst.sh +++ b/system/monit/doinst.sh @@ -23,5 +23,5 @@ preserve_perms() { } preserve_perms etc/rc.d/rc.monit.new -config etc/monit.conf.new +config etc/monitrc.new diff --git a/system/monit/monit.SlackBuild b/system/monit/monit.SlackBuild index 8cabf18..5b6eaf3 100644 --- a/system/monit/monit.SlackBuild +++ b/system/monit/monit.SlackBuild @@ -92,7 +92,7 @@ find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | gr find $PKG/usr/man -type f -exec gzip -9 {} \; for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done -cp monitrc $PKG/etc/monit.conf.new +cp monitrc $PKG/etc/monitrc.new mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a COPYING CONTRIBUTORS README $PKG/usr/doc/$PRGNAM-$VERSION diff --git a/system/monit/monit.info b/system/monit/monit.info index e3c8549..9882485 100644 --- a/system/monit/monit.info +++ b/system/monit/monit.info @@ -6,5 +6,5 @@ MD5SUM="a1bfac0fbb83439435f8616200d2364d" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -MAINTAINER="Ricardson Williams" -EMAIL="ricardsonwilliams at yahoo.com.br" +MAINTAINER="Bryan Harris" +EMAIL="bryanlharris at gmail.com" diff --git a/system/monit/rc.monit b/system/monit/rc.monit index f1bd510..b68e373 100644 --- a/system/monit/rc.monit +++ b/system/monit/rc.monit @@ -7,8 +7,7 @@ # ### Default variables -CONFIG="/etc/monit.conf" -PIDFILE="/var/run/monit.pid" +CONFIG="/etc/monitrc" [ -x /usr/bin/monit ] || exit 1 [ -r "$CONFIG" ] || exit 1 @@ -19,17 +18,13 @@ desc="Process Monitor" start() { echo "Starting $desc ($prog): /etc/rc.d/rc.$prog start" - $prog -c $CONFIG -p $PIDFILE + $prog -c $CONFIG return $? } stop() { echo "Shutting down $desc ($prog)..." - if [ -f $PIDFILE ]; then - kill -TERM $(cat $PIDFILE) - else - killall -TERM $prog - fi + monit quit return $? } @@ -45,12 +40,7 @@ reload() { } status() { - PIDS=$(pidof $prog) - if [ "$PIDS" == "" ]; then - echo "$prog is not running!" - else - echo "$prog is running at pid(s) ${PIDS}." - fi + monit status return $? } ---------- Forwarded message ---------- From: Ricardson Date: Fri, Aug 5, 2016 at 1:47 PM Subject: Re: monit change request To: Bryan Harris , ricardsonwilliams at yahoo.com.br Hi! Bryan, You can make the changes because I'm not maintain this package anymore, I think it's possible to change th maintainer in SBO. Cheers, Obrigado, Ricardson? Sent from my BlackBerry 10 smartphone. From: Bryan Harris Sent: Friday, August 5, 2016 14:43 To: ricardsonwilliams at yahoo.com.br Subject: monit change request Hi Richardson, Would it be possible to make the following changes to the monit package on SBo? I think it would put it more inline with (A) deliver the software like the author has it and (B) it would allow commands like "monit status" to work without any additional configuration. As it currently is, if I install the package and run the monit daemon with the rc.monit script it works fine; but further monit commands don't work (monit status, monit summary, monit quit, etc.) because both the configuration file and PID file have been moved to different names than monit expects by default. As a monit user, I use those commands all the time, so I think it would be nice if those commands worked without additional configuration. Here are all the changes (below). In summary: I replaced all the PID logic in the rc.monit script with monit commands (because that same logic is built into monit) and then I renamed monit.conf to monitrc in relevant places. I also gave a monit style status for the rc.monit status option. V/r, Bryan diff --git a/system/monit/doinst.sh b/system/monit/doinst.sh index 293507c..3cac70a 100644 --- a/system/monit/doinst.sh +++ b/system/monit/doinst.sh @@ -23,5 +23,5 @@ preserve_perms() { } preserve_perms etc/rc.d/rc.monit.new -config etc/monit.conf.new +config etc/monitrc.new diff --git a/system/monit/monit.SlackBuild b/system/monit/monit.SlackBuild index 8cabf18..5b6eaf3 100644 --- a/system/monit/monit.SlackBuild +++ b/system/monit/monit.SlackBuild @@ -92,7 +92,7 @@ find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | gr find $PKG/usr/man -type f -exec gzip -9 {} \; for i in $( find $PKG/usr/man -type l ) ; do ln -s $( readlink $i ).gz $i.gz ; rm $i ; done -cp monitrc $PKG/etc/monit.conf.new +cp monitrc $PKG/etc/monitrc.new mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a COPYING CONTRIBUTORS README $PKG/usr/doc/$PRGNAM-$VERSION diff --git a/system/monit/rc.monit b/system/monit/rc.monit index f1bd510..b68e373 100644 --- a/system/monit/rc.monit +++ b/system/monit/rc.monit @@ -7,8 +7,7 @@ # ### Default variables -CONFIG="/etc/monit.conf" -PIDFILE="/var/run/monit.pid" +CONFIG="/etc/monitrc" [ -x /usr/bin/monit ] || exit 1 [ -r "$CONFIG" ] || exit 1 @@ -19,17 +18,13 @@ desc="Process Monitor" start() { echo "Starting $desc ($prog): /etc/rc.d/rc.$prog start" - $prog -c $CONFIG -p $PIDFILE + $prog -c $CONFIG return $? } stop() { echo "Shutting down $desc ($prog)..." - if [ -f $PIDFILE ]; then - kill -TERM $(cat $PIDFILE) - else - killall -TERM $prog - fi + monit quit return $? } @@ -45,12 +40,7 @@ reload() { } status() { - PIDS=$(pidof $prog) - if [ "$PIDS" == "" ]; then - echo "$prog is not running!" - else - echo "$prog is running at pid(s) ${PIDS}." - fi + monit status return $? } From willysr at slackbuilds.org Fri Aug 5 18:21:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Aug 2016 01:21:02 +0700 Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: References: <20160805174735.5853265.70380.2014@gmail.com> Message-ID: > Would it be alright for me to take over maintaining the monit package? > I emailed the author (forwarded below) who says he is not the > maintainer anymore. > > I would like to "upstreamify" the package (if you take the meaning). > What I want to do is make it behave "out of the box" like the monit > author (and me) would like to use it normally. The main thing being > to make the "monit " commands work by way of renaming the > config back to the the default name hard-coded into monit. The > default name is monitrc as opposed to monit.conf (Red Hat uses that > name but they patched the source code to make it work right). > > E.g. monit summary, monit status, monit start , monit stop > , etc. Those commands work with the config named monitrc, > but not if the config named monit.conf. > > Funny thing is I emailed Willy a while back to change it to monit.conf > based on the rc.monit saying monit.conf. Only now I realize I was > pushing the wrong direction. I should have gone the other way. > > My changes are below. Or is there a better way to submit the changes? Yeah, if the maintainer gave his permission, then feel free to submit the update via submission form as usual. i have been updating monit for some time. Glad to know we will have an active maintainer :) -- 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 bryanlharris at gmail.com Fri Aug 5 18:26:29 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Fri, 5 Aug 2016 14:26:29 -0400 Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: References: <20160805174735.5853265.70380.2014@gmail.com> Message-ID: Thanks Willy, I would be happy to, I will submit the package using the online form. PS - I was wondering why it was the latest version while the maintainer saying he's not the maintainer. V/r, Bryan On Fri, Aug 5, 2016 at 2:21 PM, Willy Sudiarto Raharjo wrote: >> Would it be alright for me to take over maintaining the monit package? >> I emailed the author (forwarded below) who says he is not the >> maintainer anymore. >> >> I would like to "upstreamify" the package (if you take the meaning). >> What I want to do is make it behave "out of the box" like the monit >> author (and me) would like to use it normally. The main thing being >> to make the "monit " commands work by way of renaming the >> config back to the the default name hard-coded into monit. The >> default name is monitrc as opposed to monit.conf (Red Hat uses that >> name but they patched the source code to make it work right). >> >> E.g. monit summary, monit status, monit start , monit stop >> , etc. Those commands work with the config named monitrc, >> but not if the config named monit.conf. >> >> Funny thing is I emailed Willy a while back to change it to monit.conf >> based on the rc.monit saying monit.conf. Only now I realize I was >> pushing the wrong direction. I should have gone the other way. >> >> My changes are below. Or is there a better way to submit the changes? > > Yeah, if the maintainer gave his permission, then feel free to submit > the update via submission form as usual. > > i have been updating monit for some time. Glad to know we will have an > active maintainer :) > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From willysr at slackbuilds.org Fri Aug 5 18:28:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Aug 2016 01:28:27 +0700 Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: References: <20160805174735.5853265.70380.2014@gmail.com> Message-ID: > I would be happy to, I will submit the package using the online form. > > PS - I was wondering why it was the latest version while the > maintainer saying he's not the maintainer. Last time i talked with him saying that he will update it but not at that moment and he gave me permission to update it. -- 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 idlemoor at slackbuilds.org Fri Aug 5 19:40:34 2016 From: idlemoor at slackbuilds.org (David Spencer) Date: Fri, 5 Aug 2016 20:40:34 +0100 Subject: [Slackbuilds-users] Updates 20160805.1 Message-ID: <2b345e86-1cac-0101-0994-e3e43cf56dde@slackbuilds.org> Your new delivery of updates, thanks to all the SBo Maintainers. Fri 5 Aug 17:17:38 UTC 2016 academic/edsim51di: Moved from development. academic/fet: Updated for version 5.30.1. academic/freechartgeany: Updated for version 2.0.3 academic/gwyddion: Updated for version 2.45. academic/maxima: Update MD5SUM. academic/sage: Updated for version 7.3. academic/wxMaxima: Updated for version 16.04.2 academic/wxmacmolplt: Updated for version 7.6.2. audio/libebur128: Fix tarball handling. audio/pogo: Updated for version 0.8.7. audio/xcfa: Update README. business/stansoft: Updated for version 7.5. desktop/LX-Colors-Revival: Added (GTK2/GTK3/Openbox themes). desktop/LX-Colors-themes: Update README. desktop/bunsen-themes: Updated for version 8.3.1. desktop/e16: Updated for version 1.0.17. desktop/kwalletcli: Added mksh dependency. desktop/moka-icon-theme: Updated for version 5.3.2. desktop/neofetch: Added (simple system information script). desktop/notification-daemon: Updated for version 3.18.2 desktop/numix-icon-theme: Updated for version 0.3.812.201606210231. desktop/paper-gtk-theme: Added (Paper Theme Suite). desktop/paper-icon-theme: Added (Paper Icons). desktop/xvkbd: Update HOMEPAGE and DOWNLOAD url. development/dpkg: Updated for version 1.18.10. development/envytools: Added (development tools for nouveau). development/flow: Updated for version 0.30.0. development/guile1.8: Use correct guile1.8. development/mutagen: Updated for version 1.34. development/p4: Updated for version 2016.1.1411799. development/p4v: Updated for version 2015.2.1315639. development/pyvim: Updated for version 0.0.19. development/spice-protocol: Updated for version 0.12.12. development/tstoolbox: Updated for version 0.11.12.8. development/vala: New maintainer. development/valgrind: Updated for version 3.11.0. games/0ad-data: Update HOMEPAGE. games/0ad: Update HOMEPAGE. games/4do-libretro: Added (Port of 4DO/libfreedo to libretro). games/CATSFC-libretro: Added (libretro port of SNES9x 1.43). games/Craft-libretro: Added (simple Minecraft clone). games/Genesis-Plus-GX: Added (enhanced port of Genesis Plus). games/QuickNES-Core: Added (libretro QuickNES core library). games/RetroArch: Added (Reference frontend for the libretro API). games/antimicro: Updated for version 2.22. games/beetle-bsnes-libretro: Added (fork of Mednafen bSNES). games/beetle-gba-libretro: Added (fork of Mednafen GBA). games/beetle-lynx-libretro: Added (fork of Mednafen Lynx). games/beetle-ngp-libretro: Added (libretro fork of Mednafen NGP). games/beetle-pce-fast-libretro: Added (fork of Mednafen PCE Fast). games/beetle-pcfx-libretro: Added (fork of Mednafen PCFX). games/beetle-psx-libretro: Added (fork of Mednafen PSX). games/beetle-supergrafx-libretro: Added (fork of Mednafen PCE Fast). games/beetle-vb-libretro: Added (libretro fork of Mednafen VB). games/beetle-wswan-libretro: Added (fork of Mednafen WonderSwan). games/blastem-libretro: Added (fast and accurate Genesis emulator). games/blueMSX-libretro: Added (libretro port of blueMSX). games/bsnes-libretro: Added (libretro fork of bsnes). games/bsnes-mercury: Added (Fork of bsnes). games/chromium-bsu: Updated for version 0.9.16 games/fceux: Updated for version 2.2.3. games/fmsx-libretro: Added (libretro port of fMSX). games/gambatte-libretro: Added (libretro port of libgambatte). games/gpsp-libretro: Added (libretro port of gpSP). games/gw-libretro: Added (Game & Watch simulators). games/instead: Updated for version 2.4.1. games/libretro-desmume: Added (Port of Desmume to libretro). games/libretro-fba: Added (libretro port of Final Burn Alpha). games/libretro-fceumm: Added (FCEUmm libretro port). games/libretro-handy: Added (Atari Lynx emulator Handy). games/libretro-lutro: Added (Lua game framework for libretro). games/libretro-mgba: Added (libretro port of mGBA). games/libretro-ppsspp: Added (fast and portable PSP emulator). games/libretro-prboom: Added (Port of prboom to libretro). games/libretro-reicast: Added (Port of reicast to libretro). games/libretro-yabause: Added (Yabause port for libretro). games/megaglest: Updated for version 3.12.0 games/meteor-libretro: Added (libretro port of Meteor GBA emulator). games/mupen64plus-libretro: Added (libretro port of Mupen64 Plus). games/nestopia-libretro: Added (Nestopia for Libretro). games/nxengine-libretro: Added (Port of NxEngine to libretro). games/openmsx-catapult: Updated for version 0.13.0. games/openmsx: Updated for version 0.13.0. games/pcsx-rearmed: Added (ARM optimized PCSX fork). games/pcsx2: Added (Playstation 2 Emulator). games/picodrive-libretro: Added (MegaDrive/MegaCD/32X emulator). games/pocketsnes-libretro: Added (ARM optimized port of SNES9x). games/ppsspp: Added (fast and portable PSP emulator). games/prosystem-libretro: Added (libretro port of ProSystem). games/scummvm-libretro: Added (ScummVM with libretro backend). games/snes9x-libretro: Added (Portable Super Nintendo emulator). games/snes9x-next: Added (Port of Snes9x 1.52+ to Libretro). games/stella-libretro: Added (Port of Stella to libretro). games/tyrquake-libretro: Added (libretro port of Tyrquake). games/vba-next: Added (Optimized port of VBA-M to Libretro). games/vbam-libretro: Added (libretro fork of VBA-M). games/virtualjaguar-libretro: Added (Virtual Jaguar libretro fork). games/warsow: Updated for version 2.1. gis/qgis: Updated for version 2.16.1. graphics/paraview: Updated for version 5.1.2 + new maintainer graphics/povray: Update Script + new maintainer. libraries/BeautifulSoup4: Updated for version 4.5.1. libraries/GitPython: Updated for version 2.0.8. libraries/botocore: Updated for version 1.4.43. libraries/jsoncpp: Updated for version 1.7.4 libraries/libofx: Fix build with c++11. libraries/libpng-legacy12: Added (old PNG library). libraries/libuchardet: Fix tarball handling. libraries/libvirt-glib: Changed from i486 to i586 on 32bit libraries/libvirt-python: Updated for version 2.1.0. libraries/libvirt: Updated for version 2.1.0. libraries/opencv: Don't build the cuda bindings. libraries/php-oci8: Added (PHP extension to access Oracle Database). libraries/plyr: Added (Wrapper around libglyr). libraries/poco: Updated for version 1.7.4. multimedia/HandBrake: Updated for version 0.10.5. multimedia/OpenPHT: Added (Plex client). multimedia/lightspark: Added (Open source flash player). network/CherryMusic: Updated for version 0.37.1. network/NetworkManager-openvpn: Updated for version 1.2.4. network/awscli: Updated for version 1.10.53. network/boxcryptor: Added (cloud encryption service). network/corebird: Updated for version 1.3. network/dropbox: Downgraded for version 6.4.14. network/exim: Updated for version 4.87. network/filezilla: Updated for version 3.20.1. network/google-cli: Fix tarball handling. network/icecat: Updated for version 38.8.0. network/krb5: Updated for version 1.14.3. network/lighttpd: Updated for version 1.4.41. network/modsecurity-apache: Updated for version 2.9.1. network/openssh-krb5: Updated for version 7.2p2. network/owncloud-client: Updated for version 2.2.2. network/phodav: Added (soup dav server). network/pidgin-sipe: Updated for version 1.21.1. network/radicale: Added (Calendar Server). network/slack: Added (messaging app for teams). network/spice-gtk: Noted the new optional dependency phodav. network/spice: Updated for version 0.13.2. network/ssllabs-scan: Remove Hardcoded path to GOROOT. network/suricata: Updated for version 3.1.1. network/tor-browser: Updated for version 6.0.3. network/transmission-remote-gtk: Updated for version 1.2. network/weechat: Updated for version 1.5. network/you-get: Updated for version 0.4.523. network/youtube-dl: Updated for version 2016.07.30. office/LibreOffice: Add spell check info to README office/evince: Updated for version 3.20.1. office/gummi: Updated for version 0.6.6 office/libreoffice-helppack: Updated for version 5.2.0. office/libreoffice-langpack: Updated for version 5.2.0. office/libreoffice: Updated for version 5.2.0. office/t-prot: Added (TOFU protection script). office/texmacs: Don't run stuff belonging to doinst.sh during make. office/texmacs: Use Guile1.8 correctly. perl/perl-Sidef: Updated for version 2.30. python/apsw: Updated for version 3.13.0_r1 python/cssselect: Updated for version 0.9.2 python/dnspython: Updated for version 1.14.0 python/filechunkio: Updated for version 1.8 python/flake8: Updated for version 3.0.3. python/lxml: Updated for version 3.6.1 python/monty: Updated for version 0.8.7. python/parsel: Updated for version 1.0.3. python/prompt_toolkit: Updated for version 1.0.4. python/pymysql: Fix tarball handling. python/python-certifi: Updated for version 2016.8.2. python/python-dateutil: Updated for version 2.5.3 python/python-keyczar: Updated for version 0.716 python/python-libnacl: Updated for version 1.4.5 python/python-magic: Updated for version 0.4.12 python/python-mccabe: Updated for version 0.5.2. python/rsa: Updated for version 3.4.2 python/rst2ansi: Added (A rst converter to ansi-decorated). python/s3cmd: Updated for version 1.6.1 python/s3transfer: Added (Amazon S3 Transfer Manager). python/sge-pygame: Updated for version 1.1. python/simplejson: Updated for version 3.8.2 python/snuggs: Updated for version 1.4.0. python/stevedore: Updated for version 1.17.0. python/w3lib: Updated for version 1.15.0. ruby/ruby-json: Updated for version 2.0.2. system/bareos-client: Added (bareos client). system/bareos: Added (managed backup and recovery). system/fcron: Remove FCRON_UID and FCRON_GID. system/keybase: Added (CLI Keybase Client). system/letsencrypt.sh: Update script. system/mpich: Updated for version 3.2 + new maintainer system/nvidia-legacy304-kernel: Don't use deprecated mtrr API system/oracle-instantclient-basic: Added (Oracle DB client). system/oracle-instantclient-devel: Added (Oracle Devel Headers). system/oracle-xe: Added (Oracle Database Express Edition). system/passwdqc: Updated for version 1.3.1. system/passwordsafe: Updated for version 0.99BETA. system/pycp: Fix tarball handling. system/pymux: Updated for version 0.12. system/qterminal: Added the missing dependency libqxt. system/redis: Updated for version 3.2.3. system/run-one: Added (run one instance of command). system/spl-solaris: Updated for version 0.6.5.7. system/xonsh: Update HOMEPAGE url. system/zfs-on-linux: Updated for version 0.6.5.7. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Fri Aug 5 21:04:02 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Fri, 5 Aug 2016 16:04:02 -0500 Subject: [Slackbuilds-users] Updates 20160805.1 In-Reply-To: <2b345e86-1cac-0101-0994-e3e43cf56dde@slackbuilds.org> References: <2b345e86-1cac-0101-0994-e3e43cf56dde@slackbuilds.org> Message-ID: Thank you ! Y'All have been busy !! -- kjh On Fri, Aug 5, 2016 at 2:40 PM, David Spencer wrote: > Your new delivery of updates, thanks to all the SBo Maintainers. > > Fri 5 Aug 17:17:38 UTC 2016 > academic/edsim51di: Moved from development. > academic/fet: Updated for version 5.30.1. > academic/freechartgeany: Updated for version 2.0.3 > academic/gwyddion: Updated for version 2.45. > academic/maxima: Update MD5SUM. > academic/sage: Updated for version 7.3. > academic/wxMaxima: Updated for version 16.04.2 > academic/wxmacmolplt: Updated for version 7.6.2. > audio/libebur128: Fix tarball handling. > audio/pogo: Updated for version 0.8.7. > audio/xcfa: Update README. > business/stansoft: Updated for version 7.5. > desktop/LX-Colors-Revival: Added (GTK2/GTK3/Openbox themes). > desktop/LX-Colors-themes: Update README. > desktop/bunsen-themes: Updated for version 8.3.1. > desktop/e16: Updated for version 1.0.17. > desktop/kwalletcli: Added mksh dependency. > desktop/moka-icon-theme: Updated for version 5.3.2. > desktop/neofetch: Added (simple system information script). > desktop/notification-daemon: Updated for version 3.18.2 > desktop/numix-icon-theme: Updated for version 0.3.812.201606210231. > desktop/paper-gtk-theme: Added (Paper Theme Suite). > desktop/paper-icon-theme: Added (Paper Icons). > desktop/xvkbd: Update HOMEPAGE and DOWNLOAD url. > development/dpkg: Updated for version 1.18.10. > development/envytools: Added (development tools for nouveau). > development/flow: Updated for version 0.30.0. > development/guile1.8: Use correct guile1.8. > development/mutagen: Updated for version 1.34. > development/p4: Updated for version 2016.1.1411799. > development/p4v: Updated for version 2015.2.1315639. > development/pyvim: Updated for version 0.0.19. > development/spice-protocol: Updated for version 0.12.12. > development/tstoolbox: Updated for version 0.11.12.8. > development/vala: New maintainer. > development/valgrind: Updated for version 3.11.0. > games/0ad-data: Update HOMEPAGE. > games/0ad: Update HOMEPAGE. > games/4do-libretro: Added (Port of 4DO/libfreedo to libretro). > games/CATSFC-libretro: Added (libretro port of SNES9x 1.43). > games/Craft-libretro: Added (simple Minecraft clone). > games/Genesis-Plus-GX: Added (enhanced port of Genesis Plus). > games/QuickNES-Core: Added (libretro QuickNES core library). > games/RetroArch: Added (Reference frontend for the libretro API). > games/antimicro: Updated for version 2.22. > games/beetle-bsnes-libretro: Added (fork of Mednafen bSNES). > games/beetle-gba-libretro: Added (fork of Mednafen GBA). > games/beetle-lynx-libretro: Added (fork of Mednafen Lynx). > games/beetle-ngp-libretro: Added (libretro fork of Mednafen NGP). > games/beetle-pce-fast-libretro: Added (fork of Mednafen PCE Fast). > games/beetle-pcfx-libretro: Added (fork of Mednafen PCFX). > games/beetle-psx-libretro: Added (fork of Mednafen PSX). > games/beetle-supergrafx-libretro: Added (fork of Mednafen PCE Fast). > games/beetle-vb-libretro: Added (libretro fork of Mednafen VB). > games/beetle-wswan-libretro: Added (fork of Mednafen WonderSwan). > games/blastem-libretro: Added (fast and accurate Genesis emulator). > games/blueMSX-libretro: Added (libretro port of blueMSX). > games/bsnes-libretro: Added (libretro fork of bsnes). > games/bsnes-mercury: Added (Fork of bsnes). > games/chromium-bsu: Updated for version 0.9.16 > games/fceux: Updated for version 2.2.3. > games/fmsx-libretro: Added (libretro port of fMSX). > games/gambatte-libretro: Added (libretro port of libgambatte). > games/gpsp-libretro: Added (libretro port of gpSP). > games/gw-libretro: Added (Game & Watch simulators). > games/instead: Updated for version 2.4.1. > games/libretro-desmume: Added (Port of Desmume to libretro). > games/libretro-fba: Added (libretro port of Final Burn Alpha). > games/libretro-fceumm: Added (FCEUmm libretro port). > games/libretro-handy: Added (Atari Lynx emulator Handy). > games/libretro-lutro: Added (Lua game framework for libretro). > games/libretro-mgba: Added (libretro port of mGBA). > games/libretro-ppsspp: Added (fast and portable PSP emulator). > games/libretro-prboom: Added (Port of prboom to libretro). > games/libretro-reicast: Added (Port of reicast to libretro). > games/libretro-yabause: Added (Yabause port for libretro). > games/megaglest: Updated for version 3.12.0 > games/meteor-libretro: Added (libretro port of Meteor GBA emulator). > games/mupen64plus-libretro: Added (libretro port of Mupen64 Plus). > games/nestopia-libretro: Added (Nestopia for Libretro). > games/nxengine-libretro: Added (Port of NxEngine to libretro). > games/openmsx-catapult: Updated for version 0.13.0. > games/openmsx: Updated for version 0.13.0. > games/pcsx-rearmed: Added (ARM optimized PCSX fork). > games/pcsx2: Added (Playstation 2 Emulator). > games/picodrive-libretro: Added (MegaDrive/MegaCD/32X emulator). > games/pocketsnes-libretro: Added (ARM optimized port of SNES9x). > games/ppsspp: Added (fast and portable PSP emulator). > games/prosystem-libretro: Added (libretro port of ProSystem). > games/scummvm-libretro: Added (ScummVM with libretro backend). > games/snes9x-libretro: Added (Portable Super Nintendo emulator). > games/snes9x-next: Added (Port of Snes9x 1.52+ to Libretro). > games/stella-libretro: Added (Port of Stella to libretro). > games/tyrquake-libretro: Added (libretro port of Tyrquake). > games/vba-next: Added (Optimized port of VBA-M to Libretro). > games/vbam-libretro: Added (libretro fork of VBA-M). > games/virtualjaguar-libretro: Added (Virtual Jaguar libretro fork). > games/warsow: Updated for version 2.1. > gis/qgis: Updated for version 2.16.1. > graphics/paraview: Updated for version 5.1.2 + new maintainer > graphics/povray: Update Script + new maintainer. > libraries/BeautifulSoup4: Updated for version 4.5.1. > libraries/GitPython: Updated for version 2.0.8. > libraries/botocore: Updated for version 1.4.43. > libraries/jsoncpp: Updated for version 1.7.4 > libraries/libofx: Fix build with c++11. > libraries/libpng-legacy12: Added (old PNG library). > libraries/libuchardet: Fix tarball handling. > libraries/libvirt-glib: Changed from i486 to i586 on 32bit > libraries/libvirt-python: Updated for version 2.1.0. > libraries/libvirt: Updated for version 2.1.0. > libraries/opencv: Don't build the cuda bindings. > libraries/php-oci8: Added (PHP extension to access Oracle Database). > libraries/plyr: Added (Wrapper around libglyr). > libraries/poco: Updated for version 1.7.4. > multimedia/HandBrake: Updated for version 0.10.5. > multimedia/OpenPHT: Added (Plex client). > multimedia/lightspark: Added (Open source flash player). > network/CherryMusic: Updated for version 0.37.1. > network/NetworkManager-openvpn: Updated for version 1.2.4. > network/awscli: Updated for version 1.10.53. > network/boxcryptor: Added (cloud encryption service). > network/corebird: Updated for version 1.3. > network/dropbox: Downgraded for version 6.4.14. > network/exim: Updated for version 4.87. > network/filezilla: Updated for version 3.20.1. > network/google-cli: Fix tarball handling. > network/icecat: Updated for version 38.8.0. > network/krb5: Updated for version 1.14.3. > network/lighttpd: Updated for version 1.4.41. > network/modsecurity-apache: Updated for version 2.9.1. > network/openssh-krb5: Updated for version 7.2p2. > network/owncloud-client: Updated for version 2.2.2. > network/phodav: Added (soup dav server). > network/pidgin-sipe: Updated for version 1.21.1. > network/radicale: Added (Calendar Server). > network/slack: Added (messaging app for teams). > network/spice-gtk: Noted the new optional dependency phodav. > network/spice: Updated for version 0.13.2. > network/ssllabs-scan: Remove Hardcoded path to GOROOT. > network/suricata: Updated for version 3.1.1. > network/tor-browser: Updated for version 6.0.3. > network/transmission-remote-gtk: Updated for version 1.2. > network/weechat: Updated for version 1.5. > network/you-get: Updated for version 0.4.523. > network/youtube-dl: Updated for version 2016.07.30. > office/LibreOffice: Add spell check info to README > office/evince: Updated for version 3.20.1. > office/gummi: Updated for version 0.6.6 > office/libreoffice-helppack: Updated for version 5.2.0. > office/libreoffice-langpack: Updated for version 5.2.0. > office/libreoffice: Updated for version 5.2.0. > office/t-prot: Added (TOFU protection script). > office/texmacs: Don't run stuff belonging to doinst.sh during make. > office/texmacs: Use Guile1.8 correctly. > perl/perl-Sidef: Updated for version 2.30. > python/apsw: Updated for version 3.13.0_r1 > python/cssselect: Updated for version 0.9.2 > python/dnspython: Updated for version 1.14.0 > python/filechunkio: Updated for version 1.8 > python/flake8: Updated for version 3.0.3. > python/lxml: Updated for version 3.6.1 > python/monty: Updated for version 0.8.7. > python/parsel: Updated for version 1.0.3. > python/prompt_toolkit: Updated for version 1.0.4. > python/pymysql: Fix tarball handling. > python/python-certifi: Updated for version 2016.8.2. > python/python-dateutil: Updated for version 2.5.3 > python/python-keyczar: Updated for version 0.716 > python/python-libnacl: Updated for version 1.4.5 > python/python-magic: Updated for version 0.4.12 > python/python-mccabe: Updated for version 0.5.2. > python/rsa: Updated for version 3.4.2 > python/rst2ansi: Added (A rst converter to ansi-decorated). > python/s3cmd: Updated for version 1.6.1 > python/s3transfer: Added (Amazon S3 Transfer Manager). > python/sge-pygame: Updated for version 1.1. > python/simplejson: Updated for version 3.8.2 > python/snuggs: Updated for version 1.4.0. > python/stevedore: Updated for version 1.17.0. > python/w3lib: Updated for version 1.15.0. > ruby/ruby-json: Updated for version 2.0.2. > system/bareos-client: Added (bareos client). > system/bareos: Added (managed backup and recovery). > system/fcron: Remove FCRON_UID and FCRON_GID. > system/keybase: Added (CLI Keybase Client). > system/letsencrypt.sh: Update script. > system/mpich: Updated for version 3.2 + new maintainer > system/nvidia-legacy304-kernel: Don't use deprecated mtrr API > system/oracle-instantclient-basic: Added (Oracle DB client). > system/oracle-instantclient-devel: Added (Oracle Devel Headers). > system/oracle-xe: Added (Oracle Database Express Edition). > system/passwdqc: Updated for version 1.3.1. > system/passwordsafe: Updated for version 0.99BETA. > system/pycp: Fix tarball handling. > system/pymux: Updated for version 0.12. > system/qterminal: Added the missing dependency libqxt. > system/redis: Updated for version 3.2.3. > system/run-one: Added (run one instance of command). > system/spl-solaris: Updated for version 0.6.5.7. > system/xonsh: Update HOMEPAGE url. > system/zfs-on-linux: Updated for version 0.6.5.7. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Fri Aug 5 21:05:20 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 5 Aug 2016 14:05:20 -0700 Subject: [Slackbuilds-users] Updates 20160805.1 In-Reply-To: References: <2b345e86-1cac-0101-0994-e3e43cf56dde@slackbuilds.org> Message-ID: > On Fri, Aug 5, 2016 at 2:40 PM, David Spencer wrote: >> >> Your new delivery of updates, thanks to all the SBo Maintainers. Congratulations to David on his first public update! -------------- next part -------------- An HTML attachment was scrubbed... URL: From edps.mundognu at gmail.com Fri Aug 5 22:41:59 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Fri, 05 Aug 2016 19:41:59 -0300 Subject: [Slackbuilds-users] dropbox version Message-ID: Hi guys, In the new update, the version of dropbox in SlackBuild script is "4.3.29", while the right is "6.4.14": VERSION=${VERSION:-6.4.14} Thank you for all and hard work! Edinaldo From willysr at slackbuilds.org Fri Aug 5 23:25:07 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Aug 2016 06:25:07 +0700 Subject: [Slackbuilds-users] dropbox version In-Reply-To: References: Message-ID: > In the new update, the version of dropbox in SlackBuild script is > "4.3.29", while the right is "6.4.14": > > VERSION=${VERSION:-6.4.14} > > Thank you for all and hard work! Thanks 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 bch at shroggslodge.freeserve.co.uk Fri Aug 5 23:37:06 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sat, 6 Aug 2016 00:37:06 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes Message-ID: Hello slackbuilds-users re: icecat 38.8.0 on Slackware 14.2 64bit I am unable to add anything extra to 'help' with this, other than to say that rather oddly, icecat keeps crashing when leaving the twitter website ( twitter.com). Firefox seems ok with it. Icecat not. Why just twitter! (there may be other sites I suppose). I have no idea, but thought it worth putting it out there to see if anyone has the same issue and before raising it with bugzilla or whatever :-) All I did was go to twitter and log in, then press the 'home' key. It dumped out (no message in xterm when I started it from that). I restarted icecat, went to twitter again and the entered a different website url (rather than pressing 'home') and same thing. Other sites (I use) via icecat are ok so far. Just twitter. That's all I know I'm afraid. Thank you for your time. Habs UK -------------- next part -------------- An HTML attachment was scrubbed... URL: From melikamp at melikamp.com Fri Aug 5 23:49:14 2016 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Fri, 05 Aug 2016 16:49:14 -0700 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: <2434931.PZMhihyFQH@ithil> Script maintainer here. I can't seem to create a Twitter account, so I can't replicate. Please try safe mode with --safe-mode If it works in safe mode, the culprit is probably an add-on. Try also moving your settings ~/.mozilla/icecat temporarily so that it starts with clean ones. On Saturday, August 06, 2016 00:37:06 bch at shroggslodge.freeserve.co.uk wrote: > Hello slackbuilds-users > > re: icecat 38.8.0 on Slackware 14.2 64bit > > I am unable to add anything extra to 'help' with this, other than to say > that rather oddly, icecat keeps crashing when leaving the twitter website ( > twitter.com). Firefox seems ok with it. Icecat not. Why just twitter! > (there may be other sites I suppose). > > I have no idea, but thought it worth putting it out there to see if anyone > has the same issue and before raising it with bugzilla or whatever :-) > > All I did was go to twitter and log in, then press the 'home' key. It > dumped out (no message in xterm when I started it from that). I restarted > icecat, went to twitter again and the entered a different website url > (rather than pressing 'home') and same thing. > > Other sites (I use) via icecat are ok so far. Just twitter. That's all I > know I'm afraid. > > Thank you for your time. > Habs > UK -------------- 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 Aug 5 23:49:32 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Aug 2016 06:49:32 +0700 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: > I am unable to add anything extra to 'help' with this, other than to say > that rather oddly, icecat keeps crashing when leaving the twitter website ( > twitter.com). Firefox seems ok with it. Icecat not. Why just twitter! > (there may be other sites I suppose). > > I have no idea, but thought it worth putting it out there to see if anyone > has the same issue and before raising it with bugzilla or whatever :-) > > All I did was go to twitter and log in, then press the 'home' key. It > dumped out (no message in xterm when I started it from that). I restarted > icecat, went to twitter again and the entered a different website url > (rather than pressing 'home') and same thing. > > Other sites (I use) via icecat are ok so far. Just twitter. That's all I > know I'm afraid. There are other people who had the same problem http://lists.gnu.org/archive/html/bug-gnuzilla/2016-01/msg00010.html -- 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 melikamp at melikamp.com Sat Aug 6 00:01:44 2016 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Fri, 05 Aug 2016 17:01:44 -0700 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: <31298452.silLR0Cyjh@ithil> Thanks Willy, May be my reading comp is failing, but it doesn't look like they tracked it beyond linking it to s cairo lib. On Saturday, August 06, 2016 06:49:32 Willy Sudiarto Raharjo wrote: > > I am unable to add anything extra to 'help' with this, other than to say > > that rather oddly, icecat keeps crashing when leaving the twitter website > > ( > > twitter.com). Firefox seems ok with it. Icecat not. Why just twitter! > > (there may be other sites I suppose). > > > > I have no idea, but thought it worth putting it out there to see if anyone > > has the same issue and before raising it with bugzilla or whatever :-) > > > > All I did was go to twitter and log in, then press the 'home' key. It > > dumped out (no message in xterm when I started it from that). I restarted > > icecat, went to twitter again and the entered a different website url > > (rather than pressing 'home') and same thing. > > > > Other sites (I use) via icecat are ok so far. Just twitter. That's all I > > know I'm afraid. > > There are other people who had the same problem > http://lists.gnu.org/archive/html/bug-gnuzilla/2016-01/msg00010.html > > > -- > Willy Sudiarto Raharjo -------------- 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 Sat Aug 6 00:11:12 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Aug 2016 07:11:12 +0700 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: <31298452.silLR0Cyjh@ithil> References: <31298452.silLR0Cyjh@ithil> Message-ID: <979077fc-f166-571d-94d3-96ea5a3aaab1@slackbuilds.org> > May be my reading comp is failing, but it doesn't look like they tracked it > beyond linking it to s cairo lib. Yes, they only went as far as that and it didn't find the real culprit what about running it from console/terminal? does that give you additional information? -- 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 edps.mundognu at gmail.com Sat Aug 6 01:34:19 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Fri, 05 Aug 2016 22:34:19 -0300 Subject: [Slackbuilds-users] perl-Sidef download link Message-ID: The link for download perl-Sidef sources is wrong: https://github.com/trizen/sidef/archive/2.0/sidef-2.30.tar.gz The correct link is: https://github.com/trizen/sidef/archive/2.30/sidef-2.30.tar.gz Thanks! From willysr at slackbuilds.org Sat Aug 6 01:37:12 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 6 Aug 2016 08:37:12 +0700 Subject: [Slackbuilds-users] perl-Sidef download link In-Reply-To: References: Message-ID: > The link for download perl-Sidef sources is wrong: > > https://github.com/trizen/sidef/archive/2.0/sidef-2.30.tar.gz > > The correct link is: > > https://github.com/trizen/sidef/archive/2.30/sidef-2.30.tar.gz Fixed 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 s.arcus at open-t.co.uk Sat Aug 6 06:49:01 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sat, 6 Aug 2016 07:49:01 +0100 Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: References: <20160805174735.5853265.70380.2014@gmail.com> Message-ID: <27e7ac95-7b8b-bc93-9d51-c98027b0b81f@open-t.co.uk> On 05/08/16 19:17, Bryan Harris wrote: > Hi all, > > Would it be alright for me to take over maintaining the monit package? > I emailed the author (forwarded below) who says he is not the > maintainer anymore. > > I would like to "upstreamify" the package (if you take the meaning). > What I want to do is make it behave "out of the box" like the monit > author (and me) would like to use it normally. The main thing being > to make the "monit " commands work by way of renaming the > config back to the the default name hard-coded into monit. The > default name is monitrc as opposed to monit.conf (Red Hat uses that > name but they patched the source code to make it work right). > > E.g. monit summary, monit status, monit start , monit stop > , etc. Those commands work with the config named monitrc, > but not if the config named monit.conf. I can't help but think that this is a little bit poor design from the part of the Monit development team. What is the point in having a fully configurable config file name and location, if half of your software is hard-coded to use a particular config file name and location? I personally would prefer the /etc/monit.conf option, as it looks standard. But I guess if there is not other way to make the extra commands work ... The other problem I have with monit at the moment is that if you do /etc/rc.d/rc.monit restart, most of the time this will kill the daemon completely. What appears to be happening is that monit is taking a long time to shut down - which means the start command is attempted while it is still shutting down - so it never starts again. Maybe this could be rectified somehow in the rc script as well? From bch at shroggslodge.freeserve.co.uk Sat Aug 6 07:50:53 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sat, 6 Aug 2016 08:50:53 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes Message-ID: Thank you for the comments. Yes it does seem to be mentioned on bugzilla. I tried the console start again and also used safe-mode. I was able to get some output (see below) which seemed to end with something listed as a segmentation fault. I will see if I can repeat it. Thank you. Habs console.error: [CustomizableUI] Custom widget with id loop-button does not return a valid node 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an existing range contains or extends higher than the new range: new 0x7f6ce0717000+0xbf798, existing 0x7f6ce05e3000+0x226168 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module /usr/lib64/icecat-38.5.2/libmozsqlite3.so could not be stored 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an existing range contains or extends higher than the new range: new 0x7f6ce0803000+0x2bc0, existing 0x7f6ce05e3000+0x226168 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module /usr/lib64/icecat-38.5.2/libmozalloc.so could not be stored 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an existing range contains or extends higher than the new range: new 0x7f6ce07dd000+0x1b860, existing 0x7f6ce05e3000+0x226168 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module /usr/lib64/icecat-38.5.2/components/libdbusservice.so could not be stored 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an existing range contains or extends higher than the new range: new 0x7f6ce06b0000+0x23720, existing 0x7f6ce05e3000+0x226168 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module /usr/lib64/icecat-38.5.2/components/libmozgnome.so could not be stored 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an existing range contains or extends higher than the new range: new 0x7f6ce068d000+0x222e0, existing 0x7f6ce05e3000+0x226168 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module /usr/lib64/icecat-38.5.2/browser/components/libbrowsercomps.so could not be stored 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: /lib64/libc.so.6|B6662863DCEBA13A731B3DA192D023DF0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: /usr/lib64/icecat-38.5.2/libxul.so|41AD907282E15602EA526D1E50C673020 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736060 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cb5eb3700 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736060 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cb5eb3700 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cb98d7c00 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1d95e0288 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77011b0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1ef7fffffff 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77011b0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736060 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0xc84ff 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736270 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccc5d56d0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0xbf08606adc 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: /usr/lib64/icecat-38.5.2/libnspr4.so|B79482673662A0D46795DE07475C87250 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccc5d56d0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736270 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f0100000014 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cdf37e000 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736270 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77012ff 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccc5d56d8 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701290 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7edd01 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cbb9ec3e0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736298 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77012f8 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7af880 2016-2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf74c1c0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7327e0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf74c1c0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7327c0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1a00712 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccc5d56d0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf736270 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7af880 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77016b1 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f0000000001 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf74c1c0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7af880 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cdf3625e0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cc9220240 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7af880 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701550 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701400 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701420 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77013eb 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf738150 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0xffff000000000000 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x100ffff 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cc9220240 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x100000009 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6c00000000 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1001100000018 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cc2a28780 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701420 2016-08-06 082016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6ccf7af880 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x746163656369 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701590 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77014b8 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77014d0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cdf38d280 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701550 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cdf364600 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7f6cdf3649c0 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef77029c8 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x7ffef7701750 Segmentation fault On 6 August 2016 at 01:11, Willy Sudiarto Raharjo wrote: > > May be my reading comp is failing, but it doesn't look like they tracked > it > > beyond linking it to s cairo lib. > > Yes, they only went as far as that and it didn't find the real culprit > what about running it from console/terminal? > does that give you additional information? > > > -- > 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 bch at shroggslodge.freeserve.co.uk Sat Aug 6 07:56:07 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sat, 6 Aug 2016 08:56:07 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: oh sorry forgot to mention, for the last message i went back to a previous version 38.5.2 to see if the problem was present as in 38.8.0...and it seems to be. i will reinstall 38.8.0 and see if i get similar. On 6 August 2016 at 08:50, wrote: > Thank you for the comments. Yes it does seem to be mentioned on bugzilla. > > I tried the console start again and also used safe-mode. > > I was able to get some output (see below) which seemed to end with > something listed as a segmentation fault. I will see if I can repeat it. > > Thank you. > Habs > > > console.error: > [CustomizableUI] > Custom widget with id loop-button does not return a valid node > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce0717000+0xbf798, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/libmozsqlite3.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce0803000+0x2bc0, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/libmozalloc.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce07dd000+0x1b860, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/components/libdbusservice.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce06b0000+0x23720, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/components/libmozgnome.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce068d000+0x222e0, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/browser/components/libbrowsercomps.so could not > be stored > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /lib64/libc.so.6|B6662863DCEBA13A731B3DA192D023DF0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/icecat-38.5.2/libxul.so|41AD907282E15602EA526D1E50C673020 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736060 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cb5eb3700 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736060 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cb5eb3700 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cb98d7c00 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x1d95e0288 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77011b0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x1ef7fffffff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77011b0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736060 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0xc84ff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0xbf08606adc > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/icecat-38.5.2/libnspr4.so|B79482673662A0D46795DE07475C87250 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f0100000014 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf37e000 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77012ff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701290 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7edd01 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cbb9ec3e0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736298 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77012f8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf74c1c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7327e0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf74c1c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7327c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1a00712 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77016b1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f0000000001 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf74c1c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf3625e0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cc9220240 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701550 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701400 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701420 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77013eb > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf738150 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0xffff000000000000 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x100ffff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cc9220240 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x100000009 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6c00000000 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x1001100000018 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cc2a28780 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701420 > 2016-08-06 082016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No > module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x746163656369 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701590 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77014b8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77014d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf38d280 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701550 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf364600 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf3649c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77029c8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701750 > Segmentation fault > > > On 6 August 2016 at 01:11, Willy Sudiarto Raharjo > wrote: > >> > May be my reading comp is failing, but it doesn't look like they >> tracked it >> > beyond linking it to s cairo lib. >> >> Yes, they only went as far as that and it didn't find the real culprit >> what about running it from console/terminal? >> does that give you additional information? >> >> >> -- >> 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 bch at shroggslodge.freeserve.co.uk Sat Aug 6 10:05:07 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Sat, 6 Aug 2016 11:05:07 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: Further A segmentation fault has occurred when leaving twitter on 38.8.0 - though I did not get as much output...only the message 'segmentation fault'. Interestingly, perhaps, it seems to be something to do with being logged in to a twitter account as when I tried and visited twitter not logged in (ie. fresh/clean install of icecat, go to twitter.com, do stuff and then go elsewhere or press 'home' key)...all was ok! As soon as logged into account and tried to go elsewhere - segmentation fault occurred. As it did when trying to log out. Anyway, I know this is not the 'bug' repository/forum for icecat, but I thought I;d share the limited observations I have had. Thank you again. Habs On 6 August 2016 at 08:56, wrote: > oh sorry forgot to mention, for the last message i went back to a previous > version 38.5.2 to see if the problem was present as in 38.8.0...and it > seems to be. > > i will reinstall 38.8.0 and see if i get similar. > > On 6 August 2016 at 08:50, wrote: > >> Thank you for the comments. Yes it does seem to be mentioned on bugzilla. >> >> I tried the console start again and also used safe-mode. >> >> I was able to get some output (see below) which seemed to end with >> something listed as a segmentation fault. I will see if I can repeat it. >> >> Thank you. >> Habs >> >> >> console.error: >> [CustomizableUI] >> Custom widget with id loop-button does not return a valid node >> 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an >> existing range contains or extends higher than the new range: new >> 0x7f6ce0717000+0xbf798, existing 0x7f6ce05e3000+0x226168 >> 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module >> /usr/lib64/icecat-38.5.2/libmozsqlite3.so could not be stored >> 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an >> existing range contains or extends higher than the new range: new >> 0x7f6ce0803000+0x2bc0, existing 0x7f6ce05e3000+0x226168 >> 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module >> /usr/lib64/icecat-38.5.2/libmozalloc.so could not be stored >> 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an >> existing range contains or extends higher than the new range: new >> 0x7f6ce07dd000+0x1b860, existing 0x7f6ce05e3000+0x226168 >> 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module >> /usr/lib64/icecat-38.5.2/components/libdbusservice.so could not be stored >> 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an >> existing range contains or extends higher than the new range: new >> 0x7f6ce06b0000+0x23720, existing 0x7f6ce05e3000+0x226168 >> 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module >> /usr/lib64/icecat-38.5.2/components/libmozgnome.so could not be stored >> 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an >> existing range contains or extends higher than the new range: new >> 0x7f6ce068d000+0x222e0, existing 0x7f6ce05e3000+0x226168 >> 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module >> /usr/lib64/icecat-38.5.2/browser/components/libbrowsercomps.so could not >> be stored >> 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: >> /lib64/libc.so.6|B6662863DCEBA13A731B3DA192D023DF0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: >> /usr/lib64/icecat-38.5.2/libxul.so|41AD907282E15602EA526D1E50C673020 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736060 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cb5eb3700 >> 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: >> /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736060 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cb5eb3700 >> 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: >> /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cb98d7c00 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x1d95e0288 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77011b0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x1ef7fffffff >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77011b0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736060 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0xc84ff >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736270 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccc5d56d0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0xbf08606adc >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: >> /usr/lib64/icecat-38.5.2/libnspr4.so|B79482673662A0D46795DE07475C87250 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccc5d56d0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736270 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f0100000014 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cdf37e000 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736270 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77012ff >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccc5d56d8 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701290 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7edd01 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cbb9ec3e0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736298 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77012f8 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7af880 >> 2016-2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf74c1c0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7327e0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf74c1c0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7327c0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x1a00712 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccc5d56d0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf736270 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7af880 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77016b1 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f0000000001 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf74c1c0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7af880 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cdf3625e0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cc9220240 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7af880 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701550 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701400 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701420 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77013eb >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf738150 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0xffff000000000000 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x100ffff >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cc9220240 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x100000009 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6c00000000 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x1001100000018 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cc2a28780 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701420 >> 2016-08-06 082016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No >> module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6ccf7af880 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x746163656369 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701590 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77014b8 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77014d0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cdf38d280 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701550 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cdf364600 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7f6cdf3649c0 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef77029c8 >> 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at >> 0x7ffef7701750 >> Segmentation fault >> >> >> On 6 August 2016 at 01:11, Willy Sudiarto Raharjo < >> willysr at slackbuilds.org> wrote: >> >>> > May be my reading comp is failing, but it doesn't look like they >>> tracked it >>> > beyond linking it to s cairo lib. >>> >>> Yes, they only went as far as that and it didn't find the real culprit >>> what about running it from console/terminal? >>> does that give you additional information? >>> >>> >>> -- >>> 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 baildon.research at googlemail.com Sat Aug 6 11:21:07 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 6 Aug 2016 12:21:07 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: This sounds a bit like http://www.linuxquestions.org/questions/slackware-14/firefox-segmentation-fault-after-dec-16-2015-a-4175561826/page3.html Maybe it's worth trying to build it with '-Os' instead of '-O2'? -D. From atelszewski at gmail.com Sat Aug 6 11:31:08 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 6 Aug 2016 13:31:08 +0200 Subject: [Slackbuilds-users] Preferred way of configuring daemon that takes command line arguments only as its configuration step Message-ID: Hi, I am writing SlackBuild for a daemon that is going to be started from /etc/rc.d My question is, what is the preferred way of configuring such a daemon, that only takes command line arguments for its configuration? The two possibilities I'm thinking of are: 1. put the configuration variables directly into the /etc/rc.d/rc.daemon script 2. put the configuration variables into /etc/daemon.conf file and later on source the file from within /etc/rc.d/rc.daemon Which way to go? -- Best regards, Andrzej Telszewski From larryhaja at gmail.com Sat Aug 6 17:02:16 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Sat, 6 Aug 2016 10:02:16 -0700 Subject: [Slackbuilds-users] Preferred way of configuring daemon that takes command line arguments only as its configuration step In-Reply-To: References: Message-ID: > > > My question is, what is the preferred way of configuring such a daemon, > that only takes command line arguments for its configuration? > > The two possibilities I'm thinking of are: > 1. put the configuration variables directly into the /etc/rc.d/rc.daemon > script > 2. put the configuration variables into /etc/daemon.conf file and later on > source the file from within /etc/rc.d/rc.daemon > > Which way to go? When I'm writing a daemon file and there is no default location that the program puts the configuration file then I put it into /etc/default and source it there from the rc file. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Sun Aug 7 04:06:42 2016 From: thedoogster at gmail.com (Doogster) Date: Sat, 6 Aug 2016 21:06:42 -0700 Subject: [Slackbuilds-users] OSSv4 patch for Slackware 14.2 In-Reply-To: <56D33E8D.4000704@riseup.net> References: <56D33E8D.4000704@riseup.net> Message-ID: I just got around to looking at this now, and the patch is no longer available. On Sun, Feb 28, 2016 at 10:38 AM, y wrote: > Hi folks > > I've noticed that the OSSv4 build 2011 package for Slackware 14.2 was > not working correctly, so after some tweaking and researching I > finally got it working. > > I've merged all previous patches into one patch. It includes > 1. gcc-5.patch > 2. remove-hal.patch > 3. rm-init-scripts.patch > 4. kmod-link.patch > 5. ossvermagic.patch > 6. linux-4.0.patch > 7. added return 1; for USB output > 8. changed grc_max and CONFIG_OSS_GRC_MAX_QUALITY to 6 in order to make use > of the "src_quality=6" setting in osscore.conf > > > ./configure --enable-libsalsa=NO --regparm > > Note that the patch now uses /usr/lib64 by default. If you're using a > 32 bit system you have to revert the change in the OSSv4 configure > file before compiling. > > Here's the raw patch: > https://paste.clickbait.eu/view/raw/2b041525 > > To get rid of the annoying stuttering I've changed a few settings in > /usr/lib64/oss/conf/osscore.conf > ---------------------------- > max_intrate=1000 > src_quality=6 > cooked_enable=0 > ----------------------------- > > Cooked mode seems to be the main cause of stuttering. > > And with pulseaudio enabled it works fine with all browsers and other > applications that do not support OSSv4 natively. > > Happy testing. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From yalhcru at gmail.com Sun Aug 7 04:19:53 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 7 Aug 2016 00:19:53 -0400 Subject: [Slackbuilds-users] OSSv4 patch for Slackware 14.2 In-Reply-To: References: <56D33E8D.4000704@riseup.net> Message-ID: On 8/7/16, Doogster wrote: > I just got around to looking at this now, and the patch is no longer > available. I'll email the guy who originally sent it to you. Sorry about the long delay in response, I've been going through a *ton* of SBo scripts since 14.2 was released. Getting close to done now though. From thedoogster at gmail.com Sun Aug 7 04:22:42 2016 From: thedoogster at gmail.com (Doogster) Date: Sat, 6 Aug 2016 21:22:42 -0700 Subject: [Slackbuilds-users] OSSv4 patch for Slackware 14.2 In-Reply-To: References: <56D33E8D.4000704@riseup.net> Message-ID: I've just sent in an update to the OSSv4 SlackBuild that changes the maintainer to you. :) On Sat, Aug 6, 2016 at 9:19 PM, B Watson wrote: > On 8/7/16, Doogster wrote: >> I just got around to looking at this now, and the patch is no longer >> available. > > I'll email the guy who originally sent it to you. > > Sorry about the long delay in response, I've been going through a *ton* > of SBo scripts since 14.2 was released. Getting close to done now though. > _______________________________________________ > 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 yalhcru at gmail.com Sun Aug 7 08:54:49 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 7 Aug 2016 04:54:49 -0400 Subject: [Slackbuilds-users] OSSv4 patch for Slackware 14.2 In-Reply-To: References: <56D33E8D.4000704@riseup.net> Message-ID: On 8/7/16, Doogster wrote: > I've just sent in an update to the OSSv4 SlackBuild that changes the > maintainer to you. :) Good deal. I had totally forgot I was supposed to be the maintainer, I made a list of my packages by grepping the .info files for my name (which missed that one of course). From willysr at slackbuilds.org Sun Aug 7 12:06:14 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 7 Aug 2016 19:06:14 +0700 Subject: [Slackbuilds-users] Updates - 20160807.1 Message-ID: <28106399-2fee-bd30-ec33-ef6876668a67@slackbuilds.org> Sun Aug 7 11:56:29 UTC 2016 academic/fet: Updated DOWNLOAD. audio/oss: new maintainer. desktop/tint2: Updated for version 0.12.12. desktop/xvkbd: Updated for version 3.7. development/komodo-edit: Added (Multi-Language Editor). development/komodo-ide: Added (Multi-Language IDE). development/sqldeveloper: Added (Oracle SQL Developer). games/CATSFC-libretro: Removed (replaced by snes9x2005). games/antimicro: Fixed tarball handling. games/ecwolf: Added (an advanced source port for Wolfenstein 3D). games/megaglest: Updated REQUIRES. games/nethack: Update MAINTAINER. games/pocketsnes-libretro: Removed (replaced by snes9x2002). games/snes9x-next: Removed (replaced by snes9x2010). games/snes9x2002: Added (ARM optimized port of SNES9x). games/snes9x2005: Added (libretro port of SNES9x 1.43). games/snes9x2010: Added (Port of Snes9x 1.52+ to Libretro). games/vbam: Updated for version r1507 + new maintainer. graphics/LDView: Updated for version 4.2. libraries/libfaketime: Added (FakeTime Preload Library). libraries/netcdf: Enable netcdf-4 support. network/dropbox: Updated for version 7.4.30. network/modsecurity-apache: Fix tarball handling. network/openssh-krb5: Updated for version 7.3p1. network/sshguard: Added (SSH brute-force attack protection). office/focuswriter: Updated for version 1.5.7 + new maintainer. perl/perl-Sidef: Update DOWNLOAD url. python/PyGreSQL: Updated for version 5.0 python/boto3: Fixed DOWNLOAD. python/prompt_toolkit: Updated for version 1.0.5. system/bareos-client: Fixed tarball handling. system/bareos: Fixed tarball handling. system/mongodb: Updated for version 3.2.8. system/monit: Update script + New Maintainer. system/oldschool-pc-fonts: Added (remake of PC text mode fonts). system/openrc-services: Updated for version 20160807. system/openrc: Updated for version 0.21.3. system/qtgzmanager: Updated for version 1.0.3. system/rmw: Updated for version 2016.08.06.01a. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Aug 7 12:34:11 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 7 Aug 2016 14:34:11 +0200 Subject: [Slackbuilds-users] Default permissions for scripts in /etc/rc.d Message-ID: <59986505-5407-7bce-2c76-875e6168e950@gmail.com> Hi, I submitted SlackBuild, which sets 0755 for a startup script in /etc/rc.d, but it was changed to 0644 by SBo team. Should I use 0644 in the future submissions? -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sun Aug 7 13:19:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 7 Aug 2016 20:19:27 +0700 Subject: [Slackbuilds-users] Default permissions for scripts in /etc/rc.d In-Reply-To: <59986505-5407-7bce-2c76-875e6168e950@gmail.com> References: <59986505-5407-7bce-2c76-875e6168e950@gmail.com> Message-ID: > I submitted SlackBuild, which sets 0755 for a startup script in > /etc/rc.d, but it was changed to 0644 by SBo team. > > Should I use 0644 in the future submissions? for default, it should be 644 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Aug 7 13:34:45 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 7 Aug 2016 15:34:45 +0200 Subject: [Slackbuilds-users] Default permissions for scripts in /etc/rc.d In-Reply-To: References: <59986505-5407-7bce-2c76-875e6168e950@gmail.com> Message-ID: <2f5d252b-68f4-51ba-7edf-f8d36a8c9f5f@gmail.com> On 07/08/16 15:19, Willy Sudiarto Raharjo wrote: >> I submitted SlackBuild, which sets 0755 for a startup script in >> /etc/rc.d, but it was changed to 0644 by SBo team. >> >> Should I use 0644 in the future submissions? > > for default, it should be 644 > Thanks. -- Best regards, Andrzej Telszewski From jebrhansen+SBo at gmail.com Sun Aug 7 16:36:40 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 07 Aug 2016 16:36:40 +0000 Subject: [Slackbuilds-users] Default permissions for scripts in /etc/rc.d In-Reply-To: <2f5d252b-68f4-51ba-7edf-f8d36a8c9f5f@gmail.com> References: <59986505-5407-7bce-2c76-875e6168e950@gmail.com> <2f5d252b-68f4-51ba-7edf-f8d36a8c9f5f@gmail.com> Message-ID: Just make sure you add the preserve_perms snippet in your doinst.sh so the user's permissions will be saved whenever they upgrade the package. On Sun, Aug 7, 2016, 9:37 AM Andrzej Telszewski wrote: > On 07/08/16 15:19, Willy Sudiarto Raharjo wrote: > >> I submitted SlackBuild, which sets 0755 for a startup script in > >> /etc/rc.d, but it was changed to 0644 by SBo team. > >> > >> Should I use 0644 in the future submissions? > > > > for default, it should be 644 > > > > Thanks. > > -- > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sun Aug 7 16:45:37 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 7 Aug 2016 18:45:37 +0200 Subject: [Slackbuilds-users] Default permissions for scripts in /etc/rc.d In-Reply-To: References: <59986505-5407-7bce-2c76-875e6168e950@gmail.com> <2f5d252b-68f4-51ba-7edf-f8d36a8c9f5f@gmail.com> Message-ID: <5d53e4ea-7d06-270d-1ab0-80281830e8dc@gmail.com> On 07/08/16 18:36, Jeremy Hansen wrote: > Just make sure you add the preserve_perms snippet in your doinst.sh so > the user's permissions will be saved whenever they upgrade the package. > Been there, done that ;-) Thanks. -- Best regards, Andrzej Telszewski From thomas at beingboiled.info Sun Aug 7 22:52:36 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Mon, 8 Aug 2016 00:52:36 +0200 (CEST) Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: <27e7ac95-7b8b-bc93-9d51-c98027b0b81f@open-t.co.uk> References: <20160805174735.5853265.70380.2014@gmail.com> <27e7ac95-7b8b-bc93-9d51-c98027b0b81f@open-t.co.uk> Message-ID: On Sat, 6 Aug 2016, Sebastian Arcus wrote: > I can't help but think that this is a little bit poor design from the part of > the Monit development team. What is the point in having a fully configurable > config file name and location, if half of your software is hard-coded to use a > particular config file name and location? There's nothing wrong or even unusual with monit's design in that respect. If you want to use the command line switch to specify a config file location other than the default you have to specify it each time. Otherwise "monit $command" simply can't know how to talk to the daemon started with "monit -c /i/want/this.conf". The -c option is propably more useful for testing and development, i.e. without affecting your running instance you can test a monit config file for syntax errors and then deploy it somewhere else. > The other problem I have with monit at the moment is that if you do > /etc/rc.d/rc.monit restart, most of the time this will kill the daemon > completely. What appears to be happening is that monit is taking a long time > to shut down - which means the start command is attempted while it is still > shutting down - so it never starts again. I can confirm this. It seems to be connected to the event notification, i.e. shutdown takes as long as is takes to send an e-mail + overhead, but I'm not entirely sure. A "sleep 4" between stop and start solved this for me so I didn't investigate any further. -- From ricardo at palmtx.com.ar Sun Aug 7 23:21:00 2016 From: ricardo at palmtx.com.ar (ricardo at palmtx.com.ar) Date: Sun, 07 Aug 2016 20:21:00 -0300 Subject: [Slackbuilds-users] komodo-edit fails on Slackware64 14.2 with sbopkg Message-ID: <1bf83ad56b138bb629080b913ba778c3@palmtx.com.ar> This only happens with sbopkg, Giuseppe's slackbuild works fine otherwise, so I'm not sure where the problem lies. komodo-edit: Found Komodo-Edit-10.0.1-17276-linux-x86_64.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for Komodo-Edit-10.0.1-17276-linux-x86_64.tar.gz ... OK Building package for komodo-edit... tar: /var/lib/sbopkg/SBo/14.2/development/komodo-edit/Komodo-Edit-10.0.1-*-linux-.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now Cleaning up... Notice how the tarball name is missing the arch value ($PKG_ARCH). This change seems to do the trick for me but I'm not sure it's the right fix, or if I should talk to sbopkg's developers instead: --- komodo-edit.orig/komodo-edit.SlackBuild 2016-08-07 09:00:06.000000000 -0300 +++ komodo-edit.new/komodo-edit.SlackBuild 2016-08-07 19:57:26.449219869 -0300 @@ -35,8 +35,8 @@ if [ -z "$ARCH" ]; then ARCH=$( uname -m ) case "$ARCH" in - i?86) PKG_ARCH=x86 ;; - x86_64) PKG_ARCH=x86_64 ;; + i?86) export PKG_ARCH=x86 ;; + x86_64) export PKG_ARCH=x86_64 ;; *) echo "Architecture not supported"; exit 0; esac fi And I guess a similar change would be needed for Komodo-IDE also :) Cheers, From kingbeowulf at gmail.com Sun Aug 7 23:54:26 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 7 Aug 2016 16:54:26 -0700 Subject: [Slackbuilds-users] libreoffice .desktop chmod errors on build Message-ID: More of an eye sore than an issue, but perhaps when checking perms omit usr/bin since it is empty? Or did I misread the script? chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-impress.desktop' chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-math.desktop' chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-xsltfilter.desktop' chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-base.desktop' chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-draw.desktop' chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-writer.desktop' chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-startcenter.desktop' chmod: cannot operate on dangling symlink './usr/share/applications/libreoffice5.2-calc.desktop' chmod: cannot operate on dangling symlink './usr/bin/libreoffice5.2' chmod: cannot operate on dangling symlink './usr/bin/spadmin' -------------- 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 Aug 8 00:54:45 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 8 Aug 2016 07:54:45 +0700 Subject: [Slackbuilds-users] komodo-edit fails on Slackware64 14.2 with sbopkg In-Reply-To: <1bf83ad56b138bb629080b913ba778c3@palmtx.com.ar> References: <1bf83ad56b138bb629080b913ba778c3@palmtx.com.ar> Message-ID: > Notice how the tarball name is missing the arch value ($PKG_ARCH). > > This change seems to do the trick for me but I'm not sure it's the right > fix, or if I should talk to sbopkg's developers instead: > > > --- komodo-edit.orig/komodo-edit.SlackBuild 2016-08-07 > 09:00:06.000000000 -0300 > +++ komodo-edit.new/komodo-edit.SlackBuild 2016-08-07 > 19:57:26.449219869 -0300 > @@ -35,8 +35,8 @@ > if [ -z "$ARCH" ]; then > ARCH=$( uname -m ) > case "$ARCH" in > - i?86) PKG_ARCH=x86 ;; > - x86_64) PKG_ARCH=x86_64 ;; > + i?86) export PKG_ARCH=x86 ;; > + x86_64) export PKG_ARCH=x86_64 ;; > *) echo "Architecture not supported"; exit 0; > esac > fi > > > And I guess a similar change would be needed for Komodo-IDE also :) Hi i push the fixes on my branch which is slightly different to what you propose, but it's based on what we have in our template https://slackbuilds.org/cgit/slackbuilds/log/?h=willysr please confirm if it's working well with you thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Aug 8 00:56:14 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 8 Aug 2016 07:56:14 +0700 Subject: [Slackbuilds-users] libreoffice .desktop chmod errors on build In-Reply-To: References: Message-ID: > More of an eye sore than an issue, but perhaps when checking perms omit > usr/bin since it is empty? Or did I misread the script? > > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-impress.desktop' > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-math.desktop' > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-xsltfilter.desktop' > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-base.desktop' > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-draw.desktop' > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-writer.desktop' > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-startcenter.desktop' > chmod: cannot operate on dangling symlink > './usr/share/applications/libreoffice5.2-calc.desktop' > chmod: cannot operate on dangling symlink './usr/bin/libreoffice5.2' > chmod: cannot operate on dangling symlink './usr/bin/spadmin' it's been like that since long time ago but it worked fine at the end -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Mon Aug 8 06:34:32 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 8 Aug 2016 00:34:32 -0600 Subject: [Slackbuilds-users] DevIL download link update. Message-ID: slackbuilds . org/repository/14.2/libraries/DevIL/ DevIL is now at github: github com/DentonW/DevIL -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryanlharris at gmail.com Mon Aug 8 12:32:13 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Mon, 8 Aug 2016 08:32:13 -0400 Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: References: <20160805174735.5853265.70380.2014@gmail.com> <27e7ac95-7b8b-bc93-9d51-c98027b0b81f@open-t.co.uk> Message-ID: Interesting re: the restart command. I think it's fixed by using "monit quit" for the implementation of /etc/rc.d/rc.monit stop --- i.e. more like what the upstream authors would do. It's instantly restarted on my machine when I do restart (using rc.monit script from my last web form submission to SBo). Can you test if it still behaves that way with the latest/current SBo package? V/r, Bryan On Sun, Aug 7, 2016 at 6:52 PM, Thomas Morper wrote: > On Sat, 6 Aug 2016, Sebastian Arcus wrote: > >> I can't help but think that this is a little bit poor design from the part of >> the Monit development team. What is the point in having a fully configurable >> config file name and location, if half of your software is hard-coded to use a >> particular config file name and location? > > There's nothing wrong or even unusual with monit's design in that respect. > If you want to use the command line switch to specify a config file > location other than the default you have to specify it each time. > Otherwise "monit $command" simply can't know how to talk to the daemon > started with "monit -c /i/want/this.conf". > > The -c option is propably more useful for testing and development, i.e. > without affecting your running instance you can test a monit config file > for syntax errors and then deploy it somewhere else. > >> The other problem I have with monit at the moment is that if you do >> /etc/rc.d/rc.monit restart, most of the time this will kill the daemon >> completely. What appears to be happening is that monit is taking a long time >> to shut down - which means the start command is attempted while it is still >> shutting down - so it never starts again. > > I can confirm this. It seems to be connected to the event notification, > i.e. shutdown takes as long as is takes to send an e-mail + overhead, but > I'm not entirely sure. A "sleep 4" between stop and start solved this for > me so I didn't investigate any further. > > -- > _______________________________________________ > 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 giuseppe.diterlizzi at gmail.com Mon Aug 8 12:43:15 2016 From: giuseppe.diterlizzi at gmail.com (Giuseppe Di Terlizzi) Date: Mon, 8 Aug 2016 14:43:15 +0200 Subject: [Slackbuilds-users] komodo-edit fails on Slackware64 14.2 with sbopkg In-Reply-To: References: <1bf83ad56b138bb629080b913ba778c3@palmtx.com.ar> Message-ID: Hi the patch works fine for me! Thanks, Joseph Giuseppe Di Terlizzi 2016-08-08 2:54 GMT+02:00 Willy Sudiarto Raharjo : > > Notice how the tarball name is missing the arch value ($PKG_ARCH). > > > > This change seems to do the trick for me but I'm not sure it's the right > > fix, or if I should talk to sbopkg's developers instead: > > > > > > --- komodo-edit.orig/komodo-edit.SlackBuild 2016-08-07 > > 09:00:06.000000000 -0300 > > +++ komodo-edit.new/komodo-edit.SlackBuild 2016-08-07 > > 19:57:26.449219869 -0300 > > @@ -35,8 +35,8 @@ > > if [ -z "$ARCH" ]; then > > ARCH=$( uname -m ) > > case "$ARCH" in > > - i?86) PKG_ARCH=x86 ;; > > - x86_64) PKG_ARCH=x86_64 ;; > > + i?86) export PKG_ARCH=x86 ;; > > + x86_64) export PKG_ARCH=x86_64 ;; > > *) echo "Architecture not supported"; exit 0; > > esac > > fi > > > > > > And I guess a similar change would be needed for Komodo-IDE also :) > > Hi > > i push the fixes on my branch which is slightly different to what you > propose, but it's based on what we have in our template > https://slackbuilds.org/cgit/slackbuilds/log/?h=willysr > > please confirm if it's working well with you > > thanks > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Mon Aug 8 13:53:08 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 8 Aug 2016 06:53:08 -0700 Subject: [Slackbuilds-users] DevIL download link update. In-Reply-To: References: Message-ID: On Sun, Aug 7, 2016 at 11:34 PM, Fernando Lopez wrote: > slackbuilds . org/repository/14.2/libraries/DevIL/ > > > DevIL is now at github: > github com/DentonW/DevIL I've looked into this, and I'm going to leave the SlackBuild as-is. Both the homepage and the download link still work. I won't change the homepage link to the GitHub page, because none of the documentation on the old homepage was moved there. The GitHub page also doesn't have any releases to link to. All the actual, versioned releases are still on Sourceforge. From jorge.giner at hotmail.com Mon Aug 8 14:37:15 2016 From: jorge.giner at hotmail.com (Jorge Giner Cordero) Date: Mon, 8 Aug 2016 16:37:15 +0200 Subject: [Slackbuilds-users] spotify new address Message-ID: Hello, it seems that the url for downloading spotify changed (there is a new version and the one referenced from the SlackBuild has been removed). See here: http://repository-origin.spotify.com/pool/non-free/s/spotify-client/ It is the first time I write to this mailing list. I don't know if it is better for this kind of things to contact the Slackbuild script maintainer directly or do it by using this mailing list... Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Mon Aug 8 15:01:06 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 8 Aug 2016 08:01:06 -0700 Subject: [Slackbuilds-users] spotify new address In-Reply-To: References: Message-ID: On Aug 8, 2016 7:37 AM, "Jorge Giner Cordero" wrote: > > Hello, it seems that the url for downloading spotify changed (there is a new version and the one referenced from the SlackBuild has been removed). See here: > > http://repository-origin.spotify.com/pool/non-free/s/spotify-client/ > > It is the first time I write to this mailing list. I don't know if it is better for this kind of things to contact the Slackbuild script maintainer directly or do it by using this mailing list... Thanks for the ping. Just contact me directly next time. -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Mon Aug 8 16:44:31 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 8 Aug 2016 09:44:31 -0700 Subject: [Slackbuilds-users] DevIL download link update. In-Reply-To: References: Message-ID: > Its better to keep it updated... the developer will stop using sourceforge at any given time... Fernando, I do not appreciate the manipulation that you just tried to pull off. For your last reply, quoted above, you removed slackbuilds-users from the recipients list and replaced it with the devil mailing list. Do not do that. I have made a very, very carefully considered decision to keep the links to the old homepage and to the Sourceforge downloads, and I have already told you why. If you do not like that, I can suggest several options. 1. You can take over ownership of DevIL. Yes, this is a serious suggestion. Just ask. 2. You can submit a ResIL SlackBuild to replace DevIL. If you do, I will be happy to orphan and retire the DevIL SlackBuild. 3. You can accept my decision. Think about those. On Mon, Aug 8, 2016 at 6:53 AM, Doogster wrote: > On Sun, Aug 7, 2016 at 11:34 PM, Fernando Lopez > wrote: >> slackbuilds . org/repository/14.2/libraries/DevIL/ >> >> >> DevIL is now at github: >> github com/DentonW/DevIL > > I've looked into this, and I'm going to leave the SlackBuild as-is. > > Both the homepage and the download link still work. > > I won't change the homepage link to the GitHub page, because none of > the documentation on the old homepage was moved there. The GitHub page > also doesn't have any releases to link to. All the actual, versioned > releases are still on Sourceforge. From fernando.lopezjr at gmail.com Mon Aug 8 17:23:17 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 8 Aug 2016 11:23:17 -0600 Subject: [Slackbuilds-users] DevIL download link update. In-Reply-To: References: Message-ID: On Mon, Aug 8, 2016 at 10:44 AM, Doogster wrote: > > Its better to keep it updated... the developer will stop using > sourceforge at any given time... > > Fernando, I do not appreciate the manipulation that you just tried to > pull off. For your last reply, quoted above, you removed > slackbuilds-users from the recipients list and replaced it with the > devil mailing list. Do not do that I didnt mean to manipulate anything... please dont over complicate things. I just replied and added Denton maybe he has something else to say. > > I have made a very, very carefully considered decision to keep the > links to the old homepage and to the Sourceforge downloads, and I have > already told you why. If you do not like that, I can suggest several > options. > > 1. You can take over ownership of DevIL. Yes, this is a serious > suggestion. Just ask. > I dont mean to take ownership of the package, we need packagers. > > 2. You can submit a ResIL SlackBuild to replace DevIL. If you do, I > will be happy to orphan and retire the DevIL SlackBuild. > Don't. Other software use this package. I dont know why but people like running old software. > > 3. You can accept my decision. > > Think about those. > Please dont fight over this, we all have different points of view and I bared mine no need to get all crazy or fight about this. I feel the correct way is to have it updated to the latest repository, because old repo is going to die any time soon with out notice. moderators any words? this is the email I sent (I see no manipulation): Fernando Lopez 10:34 AM (39 minutes ago) to *devil.imagelib*, Doogster Its better to keep it updated... the developer will stop using sourceforge at any given time... *August 2, 2014* DevIL now has a home at GitHub. It may find a more permanent home there in the future. Also feel free to Like us on Facebook. - Denton > > On Mon, Aug 8, 2016 at 6:53 AM, Doogster wrote: > > On Sun, Aug 7, 2016 at 11:34 PM, Fernando Lopez > > wrote: > >> slackbuilds . org/repository/14.2/libraries/DevIL/ > >> > >> > >> DevIL is now at github: > >> github com/DentonW/DevIL > > > > I've looked into this, and I'm going to leave the SlackBuild as-is. > > > > Both the homepage and the download link still work. > > > > I won't change the homepage link to the GitHub page, because none of > > the documentation on the old homepage was moved there. The GitHub page > > also doesn't have any releases to link to. All the actual, versioned > > releases are still on Sourceforge. > _______________________________________________ > 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 thedoogster at gmail.com Mon Aug 8 17:59:42 2016 From: thedoogster at gmail.com (Doogster) Date: Mon, 8 Aug 2016 10:59:42 -0700 Subject: [Slackbuilds-users] DevIL download link update. In-Reply-To: References: Message-ID: *When* the Sourceforge page dies, and not before, I will update the SlackBuild. It In that case it will likely go to GitHub for the homepage and Launchpad for the source tarballs. For now, the SlackBuild will be left alone, for reasons that I've already given. On Mon, Aug 8, 2016 at 10:23 AM, Fernando Lopez wrote: > On Mon, Aug 8, 2016 at 10:44 AM, Doogster wrote: > >> > Its better to keep it updated... the developer will stop using >> sourceforge at any given time... >> >> Fernando, I do not appreciate the manipulation that you just tried to >> pull off. For your last reply, quoted above, you removed >> slackbuilds-users from the recipients list and replaced it with the >> devil mailing list. Do not do that > > > I didnt mean to manipulate anything... please dont over complicate things. > I just replied > and added Denton maybe he has something else to say. > > >> >> I have made a very, very carefully considered decision to keep the >> links to the old homepage and to the Sourceforge downloads, and I have >> already told you why. If you do not like that, I can suggest several >> options. >> >> 1. You can take over ownership of DevIL. Yes, this is a serious >> suggestion. Just ask. >> > > I dont mean to take ownership of the package, we need packagers. > > >> >> 2. You can submit a ResIL SlackBuild to replace DevIL. If you do, I >> will be happy to orphan and retire the DevIL SlackBuild. >> > > Don't. Other software use this package. I dont know why > but people like running old software. > > >> >> 3. You can accept my decision. >> >> Think about those. >> > > > Please dont fight over this, we all have different points of view and I > bared mine no need to get all crazy or fight about this. > > I feel the correct way is to have it updated to the latest repository, > because old repo is going to die any time soon with out notice. > > moderators any words? > > > > > > > this is the email I sent (I see no manipulation): > Fernando Lopez > 10:34 AM (39 minutes ago) > to *devil.imagelib*, Doogster > Its better to keep it updated... the developer will stop using sourceforge > at any given time... > > *August 2, 2014* > > DevIL now has a home at GitHub. It may find a more permanent home there in > the future. Also feel free to Like us on Facebook. > > - Denton > > > >> >> On Mon, Aug 8, 2016 at 6:53 AM, Doogster wrote: >> > On Sun, Aug 7, 2016 at 11:34 PM, Fernando Lopez >> > wrote: >> >> slackbuilds . org/repository/14.2/libraries/DevIL/ >> >> >> >> >> >> DevIL is now at github: >> >> github com/DentonW/DevIL >> > >> > I've looked into this, and I'm going to leave the SlackBuild as-is. >> > >> > Both the homepage and the download link still work. >> > >> > I won't change the homepage link to the GitHub page, because none of >> > the documentation on the old homepage was moved there. The GitHub page >> > also doesn't have any releases to link to. All the actual, versioned >> > releases are still on Sourceforge. >> _______________________________________________ >> 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. > > _______________________________________________ > 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 Mon Aug 8 19:15:31 2016 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Mon, 08 Aug 2016 12:15:31 -0700 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: <56577217.u9CO2rfqRP@ithil> I still can't replicate any crash whatsoever, even in places where others report them. However, Matt tells me that crashes went away after he rebuilt with -Os. He also mentioned he's got an AMD Phenom, whereas I am using Intel CPU, which may explain why I am unable to hit this snag. I can certainly submit a fixed SlackBuild if there's a consensus -Os is an effective fix. Please let me know :) > Slackware 14.2 64bit > > Hello folks - I have been 'talking' on slackbuilds.org (SBo) about icecat > 38.8.0, which I use, about a problem I came across with it crashing. > > I've only noticed it when I was browsing the twitter.com website and more > specifically only when navigating away from that site. There may be other > situations of course. > > Even more, it would seem it happens only when logged in to twitter > account; if not logged in, then no crash when navigating away. > > Some contributors on SBo pointed out to me similar issues that they had > found reported on other sites. > > There has been some suggestion to build using a different parameter (with > '-Os' instead of '-O2'.... i do not know what that does or how?) as a *work > around*, but I have not tried it as yet. > > As this issue has been around for a while it would seem and affected > earlier releases too, is there any knowledge as to what it might be, as it > seems Firefox does not appear to suffer the same problem from my experience? > > I am sorry, but my skills do not allow me (yet) to provide the sort of > detailed info that others produce, however there is a console output below, > though relating to an earlier build of Icecat. It may be of some use. > Hopefully just raising this issue as I found it, is enough to help others > understand. If there is anything I can do (bearing in mind I use others' > build scripts [SBo] for these things), please let me know. > > If anyone has any info or if a bug report needs [re]creating, then how to ? > > Peace and best wishes. > Habs > > console.error: > [CustomizableUI] > Custom widget with id loop-button does not return a valid node > > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce0717000+0xbf798, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/libmozsqlite3.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce0803000+0x2bc0, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/libmozalloc.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce07dd000+0x1b860, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/components/libdbusservice.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce06b0000+0x23720, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/components/libmozgnome.so could not be stored > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > existing range contains or extends higher than the new range: new > 0x7f6ce068d000+0x222e0, existing 0x7f6ce05e3000+0x226168 > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > /usr/lib64/icecat-38.5.2/browser/components/libbrowsercomps.so could not be > stored > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /lib64/libc.so.6|B6662863DCEBA13A731B3DA192D023DF0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/icecat-38.5.2/libxul.so|41AD907282E15602EA526D1E50C673020 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736060 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cb5eb3700 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736060 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cb5eb3700 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cb98d7c00 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x1d95e0288 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77011b0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x1ef7fffffff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77011b0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736060 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0xc84ff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0xbf08606adc > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > /usr/lib64/icecat-38.5.2/libnspr4.so|B79482673662A0D46795DE07475C87250 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f0100000014 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf37e000 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77012ff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701290 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7edd01 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cbb9ec3e0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736298 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77012f8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf74c1c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7327e0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf74c1c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7327c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1a00712 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccc5d56d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf736270 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77016b1 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f0000000001 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf74c1c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf3625e0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cc9220240 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701550 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701400 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701420 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77013eb > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf738150 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0xffff000000000000 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x100ffff > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cc9220240 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x100000009 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6c00000000 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x1001100000018 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cc2a28780 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701420 > 2016-08-06 082016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module > at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6ccf7af880 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x746163656369 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701590 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77014b8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77014d0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf38d280 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701550 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf364600 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7f6cdf3649c0 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef77029c8 > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x7ffef7701750 > Segmentation fault > -- > http://gnuzilla.gnu.org -------------- 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 ryan.q at linux.com Mon Aug 8 19:36:55 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 8 Aug 2016 12:36:55 -0700 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: <56577217.u9CO2rfqRP@ithil> References: <56577217.u9CO2rfqRP@ithil> Message-ID: On Monday, August 8, 2016, Ivan Zaigralin wrote: > I still can't replicate any crash whatsoever, even in places where others > report them. However, Matt tells me that crashes went away after he rebuilt > with -Os. He also mentioned he's got an AMD Phenom, whereas I am using > Intel > CPU, which may explain why I am unable to hit this snag. > > I can certainly submit a fixed SlackBuild if there's a consensus -Os is an > effective fix. Please let me know :) > Seems like that would be valid, since Slackware's own Firefox build was passing that for version 43, and only removed it for versions past 43: (Changelog reference): Wed Dec 23 22:44:58 UTC 2015 a/lvm2-2.02.138-i586-1.txz: Upgraded. ap/ghostscript-9.18-i586-1.txz: Upgraded. ap/lsof-4.89-i586-1.txz: Upgraded. l/pycups-1.9.73-i586-1.txz: Upgraded. l/pycurl-7.19.5.3-i586-1.txz: Upgraded. n/NetworkManager-1.0.10-i586-1.txz: Upgraded. n/curl-7.46.0-i586-1.txz: Upgraded. n/links-2.12-i586-1.txz: Upgraded. n/obexfs-0.12-i486-1.txz: Removed. This functionality is now included in the obexftp package. n/obexftp-0.24-i586-1.txz: Upgraded. Thanks to Robby Workman. n/openobex-1.7.1-i586-1.txz: Upgraded. Thanks to Robby Workman. n/rsync-3.1.2-i586-1.txz: Upgraded. x/libXi-1.7.6-i586-1.txz: Upgraded. x/pixman-0.33.6-i586-1.txz: Upgraded. x/xorg-cf-files-1.0.6-noarch-1.txz: Upgraded. xap/mozilla-firefox-43.0.2-i586-2.txz: Rebuilt. Compile with -Os instead of -O2 to work around crash issues. Recent betas are working fine with -O2, so we'll probably be able to switch back to that again soon. Thanks to j_v. -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From bch at shroggslodge.freeserve.co.uk Mon Aug 8 20:17:11 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Mon, 8 Aug 2016 21:17:11 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: <56577217.u9CO2rfqRP@ithil> References: <56577217.u9CO2rfqRP@ithil> Message-ID: Hi Ivan Interesting. I have an AMD Phenom. I have built, rebuilt and tried earlier releases using the SBo scripts and on twitter.com (when logged in...that's crucial) it crashes out always when navigating away. I am not knowledgeable to know if it is an AMD related problem and I do not have an Intel chip to try, though I will seek one out :-) Please, for the less aware like me, what does the -O2 do and what is the difference to -Os ? Thank you for your interest and assistance. Habs On 8 August 2016 at 20:15, Ivan Zaigralin wrote: > I still can't replicate any crash whatsoever, even in places where others > report them. However, Matt tells me that crashes went away after he rebuilt > with -Os. He also mentioned he's got an AMD Phenom, whereas I am using > Intel > CPU, which may explain why I am unable to hit this snag. > > I can certainly submit a fixed SlackBuild if there's a consensus -Os is an > effective fix. Please let me know :) > > > Slackware 14.2 64bit > > > > Hello folks - I have been 'talking' on slackbuilds.org (SBo) about > icecat > > 38.8.0, which I use, about a problem I came across with it crashing. > > > > I've only noticed it when I was browsing the twitter.com website and > more > > specifically only when navigating away from that site. There may be other > > situations of course. > > > > Even more, it would seem it happens only when logged in to twitter > > account; if not logged in, then no crash when navigating away. > > > > Some contributors on SBo pointed out to me similar issues that they had > > found reported on other sites. > > > > There has been some suggestion to build using a different parameter (with > > '-Os' instead of '-O2'.... i do not know what that does or how?) as a > *work > > around*, but I have not tried it as yet. > > > > As this issue has been around for a while it would seem and affected > > earlier releases too, is there any knowledge as to what it might be, as > it > > seems Firefox does not appear to suffer the same problem from my > experience? > > > > I am sorry, but my skills do not allow me (yet) to provide the sort of > > detailed info that others produce, however there is a console output > below, > > though relating to an earlier build of Icecat. It may be of some use. > > Hopefully just raising this issue as I found it, is enough to help others > > understand. If there is anything I can do (bearing in mind I use others' > > build scripts [SBo] for these things), please let me know. > > > > If anyone has any info or if a bug report needs [re]creating, then how > to ? > > > > Peace and best wishes. > > Habs > > > > console.error: > > [CustomizableUI] > > Custom widget with id loop-button does not return a valid node > > > > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > > existing range contains or extends higher than the new range: new > > 0x7f6ce0717000+0xbf798, existing 0x7f6ce05e3000+0x226168 > > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > > /usr/lib64/icecat-38.5.2/libmozsqlite3.so could not be stored > > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > > existing range contains or extends higher than the new range: new > > 0x7f6ce0803000+0x2bc0, existing 0x7f6ce05e3000+0x226168 > > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > > /usr/lib64/icecat-38.5.2/libmozalloc.so could not be stored > > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > > existing range contains or extends higher than the new range: new > > 0x7f6ce07dd000+0x1b860, existing 0x7f6ce05e3000+0x226168 > > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > > /usr/lib64/icecat-38.5.2/components/libdbusservice.so could not be > stored > > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > > existing range contains or extends higher than the new range: new > > 0x7f6ce06b0000+0x23720, existing 0x7f6ce05e3000+0x226168 > > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > > /usr/lib64/icecat-38.5.2/components/libmozgnome.so could not be stored > > 2016-08-06 08:08:01: range_map-inl.h:91: INFO: StoreRange failed, an > > existing range contains or extends higher than the new range: new > > 0x7f6ce068d000+0x222e0, existing 0x7f6ce05e3000+0x226168 > > 2016-08-06 08:08:01: basic_code_modules.cc:70: ERROR: Module > > /usr/lib64/icecat-38.5.2/browser/components/libbrowsercomps.so could > not be > > stored > > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > > /lib64/libc.so.6|B6662863DCEBA13A731B3DA192D023DF0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > > /usr/lib64/icecat-38.5.2/libxul.so|41AD907282E15602EA526D1E50C673020 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736060 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cb5eb3700 > > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > > /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736060 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x5 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cb5eb3700 > > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > > /usr/lib64/libglib-2.0.so.0|7D36F9F9E95A6CA6B68E20EA6ABFC1940 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cb98d7c00 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x1d95e0288 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77011b0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x1ef7fffffff > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77011b0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736060 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0xc84ff > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736270 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccc5d56d0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0xbf08606adc > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: stackwalker.cc:125: INFO: Couldn't load symbols for: > > /usr/lib64/icecat-38.5.2/libnspr4.so|B79482673662A0D46795DE07475C87250 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccc5d56d0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736270 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f0100000014 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cdf37e000 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736270 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77012ff > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccc5d56d8 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x1 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701290 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7edd01 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cbb9ec3e0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736298 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77012f8 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7af880 > > 2016-2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf74c1c0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7327e0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf74c1c0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7327c0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x1a00712 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccc5d56d0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf736270 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7af880 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77016b1 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f0000000001 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf74c1c0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7af880 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cdf3625e0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cc9220240 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7af880 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701550 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701400 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701420 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77013eb > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf738150 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0xffff000000000000 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > 0x100ffff > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cc9220240 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x100000009 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6c00000000 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x1001100000018 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cc2a28780 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701420 > > 2016-08-06 082016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No > module > > at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6ccf7af880 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x746163656369 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701590 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77014b8 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77014d0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cdf38d280 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701550 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at 0x0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cdf364600 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7f6cdf3649c0 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef77029c8 > > 2016-08-06 08:08:01: basic_code_modules.cc:88: INFO: No module at > > 0x7ffef7701750 > > Segmentation fault > > -- > > http://gnuzilla.gnu.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Mon Aug 8 20:29:10 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 08 Aug 2016 22:29:10 +0200 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: <56577217.u9CO2rfqRP@ithil> Message-ID: <23876eef338aa2c91b37e61ecc772fcc@schoepfer.info> > Please, for the less aware like me, what does the -O2 do and what is > the difference to -Os ? Have a look at https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html -Os Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size. From bch at shroggslodge.freeserve.co.uk Mon Aug 8 20:36:11 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Mon, 8 Aug 2016 21:36:11 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: <23876eef338aa2c91b37e61ecc772fcc@schoepfer.info> References: <56577217.u9CO2rfqRP@ithil> <23876eef338aa2c91b37e61ecc772fcc@schoepfer.info> Message-ID: Thank you for the info. On 8 August 2016 at 21:29, Franzen wrote: > Please, for the less aware like me, what does the -O2 do and what is >> the difference to -Os ? >> > > Have a look at https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html > > -Os > Optimize for size. -Os enables all -O2 optimizations that do not typically > increase code size. It also performs further optimizations designed to > reduce > code size. > > _______________________________________________ > 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 bch at shroggslodge.freeserve.co.uk Mon Aug 8 22:16:28 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Mon, 8 Aug 2016 23:16:28 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: <56577217.u9CO2rfqRP@ithil> Message-ID: hi there all I have tried the -Os switch and it does appear to remedy the problem. Icecat no longer crashes in the scenario(s) I have documented. I wonder what the -O2 switch does differently to the -Os one. So for now that does appear to be the 'fix'. Thank you all. Habs On 8 August 2016 at 20:36, Ryan P.C. McQuen wrote: > > > On Monday, August 8, 2016, Ivan Zaigralin wrote: > >> I still can't replicate any crash whatsoever, even in places where others >> report them. However, Matt tells me that crashes went away after he >> rebuilt >> with -Os. He also mentioned he's got an AMD Phenom, whereas I am using >> Intel >> CPU, which may explain why I am unable to hit this snag. >> >> I can certainly submit a fixed SlackBuild if there's a consensus -Os is an >> effective fix. Please let me know :) >> > > Seems like that would be valid, since Slackware's own Firefox build was > passing that for version 43, and only removed it for versions past 43: > > (Changelog reference): > > Wed Dec 23 22:44:58 UTC 2015 > a/lvm2-2.02.138-i586-1.txz: Upgraded. > ap/ghostscript-9.18-i586-1.txz: Upgraded. > ap/lsof-4.89-i586-1.txz: Upgraded. > l/pycups-1.9.73-i586-1.txz: Upgraded. > l/pycurl-7.19.5.3-i586-1.txz: Upgraded. > n/NetworkManager-1.0.10-i586-1.txz: Upgraded. > n/curl-7.46.0-i586-1.txz: Upgraded. > n/links-2.12-i586-1.txz: Upgraded. > n/obexfs-0.12-i486-1.txz: Removed. > This functionality is now included in the obexftp package. > n/obexftp-0.24-i586-1.txz: Upgraded. > Thanks to Robby Workman. > n/openobex-1.7.1-i586-1.txz: Upgraded. > Thanks to Robby Workman. > n/rsync-3.1.2-i586-1.txz: Upgraded. > x/libXi-1.7.6-i586-1.txz: Upgraded. > x/pixman-0.33.6-i586-1.txz: Upgraded. > x/xorg-cf-files-1.0.6-noarch-1.txz: Upgraded. > xap/mozilla-firefox-43.0.2-i586-2.txz: Rebuilt. > Compile with -Os instead of -O2 to work around crash issues. > Recent betas are working fine with -O2, so we'll probably be > able to switch back to that again soon. Thanks to j_v. > > > -- > -Ryan > [ryanpcmcquen.org] > > > _______________________________________________ > 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 fernando.lopezjr at gmail.com Tue Aug 9 06:58:51 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 9 Aug 2016 00:58:51 -0600 Subject: [Slackbuilds-users] fontforge fails to compile Message-ID: I can download fine manually from the site... Processing fontforge fontforge: Found fontforge-20150824.tar.gz in /var/cache/sbopkg. Found cidmaps.tgz in /var/cache/sbopkg. fontforge not found in /var/cache/sbopkg. --2016-08-09 00:55:43-- http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.6.3.tar.xz Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213 Connecting to mirrors.slackware.com (mirrors.slackware.com)|207.223.116.213|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2016-08-09 00:55:43 ERROR 404: Not Found. fontforge: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue Aug 9 07:04:05 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 9 Aug 2016 09:04:05 +0200 Subject: [Slackbuilds-users] fontforge fails to compile In-Reply-To: References: Message-ID: 2016-08-09 8:58 GMT+02:00 Fernando Lopez : > I can download fine manually from the site... > > > Processing fontforge > > fontforge: > Found fontforge-20150824.tar.gz in /var/cache/sbopkg. > Found cidmaps.tgz in /var/cache/sbopkg. > fontforge not found in /var/cache/sbopkg. > --2016-08-09 00:55:43-- > http://mirrors.slackware.com/slackware/slackware-current/source/l/freetype/freetype-2.6.3.tar.xz > Resolving mirrors.slackware.com (mirrors.slackware.com)... 207.223.116.213 > Connecting to mirrors.slackware.com > (mirrors.slackware.com)|207.223.116.213|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2016-08-09 00:55:43 ERROR 404: Not Found. > > > fontforge: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: hi Fernando, I think your SBo local repository is not up-to-date as the link to the freetype tarball in the fontforge.info file has been updated a couple of weeks ago... Matteo From fernando.lopezjr at gmail.com Tue Aug 9 07:06:31 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 9 Aug 2016 01:06:31 -0600 Subject: [Slackbuilds-users] fontforge fails to compile In-Reply-To: References: Message-ID: thanks will update. On Tue, Aug 9, 2016 at 1:04 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2016-08-09 8:58 GMT+02:00 Fernando Lopez : > > I can download fine manually from the site... > > > > > > Processing fontforge > > > > fontforge: > > Found fontforge-20150824.tar.gz in /var/cache/sbopkg. > > Found cidmaps.tgz in /var/cache/sbopkg. > > fontforge not found in /var/cache/sbopkg. > > --2016-08-09 00:55:43-- > > http://mirrors.slackware.com/slackware/slackware-current/ > source/l/freetype/freetype-2.6.3.tar.xz > > Resolving mirrors.slackware.com (mirrors.slackware.com)... > 207.223.116.213 > > Connecting to mirrors.slackware.com > > (mirrors.slackware.com)|207.223.116.213|:80... connected. > > HTTP request sent, awaiting response... 404 Not Found > > 2016-08-09 00:55:43 ERROR 404: Not Found. > > > > > > fontforge: > > Would you like to continue processing the rest of the > > queue or would you like to abort? If this failed > > package is a dependency of another package in the queue > > then it may not make sense to continue. > > > > (Y)es to continue, (N)o to abort, (R)etry the build?: > > > hi Fernando, > > I think your SBo local repository is not up-to-date as the link to the > freetype tarball in the fontforge.info file has been updated a couple > of weeks ago... > > 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/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Tue Aug 9 14:50:11 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 9 Aug 2016 15:50:11 +0100 Subject: [Slackbuilds-users] Are new submission accepted yet? Message-ID: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> I've searched the list messages over the last few weeks but can't figure the answer. Is SBo open to new submissions yet - or there will be no more new stuff until next version of Slackware, or how does it work? As some of you know I've helped prepare the Navit SBo scripts, but that was just before 14.2 was released so I was told to hold fire. When should I submit it? From matteo.bernardini at gmail.com Tue Aug 9 14:56:46 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 9 Aug 2016 16:56:46 +0200 Subject: [Slackbuilds-users] Are new submission accepted yet? In-Reply-To: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> References: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> Message-ID: 2016-08-09 16:50 GMT+02:00 Sebastian Arcus : > I've searched the list messages over the last few weeks but can't figure the > answer. Is SBo open to new submissions yet - or there will be no more new > stuff until next version of Slackware, or how does it work? As some of you > know I've helped prepare the Navit SBo scripts, but that was just before > 14.2 was released so I was told to hold fire. When should I submit it? Hi Sebastian, maybe you missed Willy's message on july 24th https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-July/016643.html Matteo From thomas at beingboiled.info Tue Aug 9 23:29:30 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Wed, 10 Aug 2016 01:29:30 +0200 (CEST) Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: References: <20160805174735.5853265.70380.2014@gmail.com> <27e7ac95-7b8b-bc93-9d51-c98027b0b81f@open-t.co.uk> Message-ID: On Mon, 8 Aug 2016, Bryan Harris wrote: > Interesting re: the restart command. I think it's fixed by using > "monit quit" for the implementation of /etc/rc.d/rc.monit stop It can't be, because "monit quit" just sends a SIGTERM to the monit daemon and thus is functionally the same as a "kill $(cat monit.pid)" or similar. Your approach is still better, though. The previous rc-script would kill any monit, including user instances. Then again... "reload" works just fine and a "restart" is practically never needed, so I'd consider a few seconds of sleep between stop and start as "good enough". -- From s.arcus at open-t.co.uk Wed Aug 10 08:51:40 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 10 Aug 2016 09:51:40 +0100 Subject: [Slackbuilds-users] Are new submission accepted yet? In-Reply-To: References: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> Message-ID: On 09/08/16 15:56, Matteo Bernardini wrote: > 2016-08-09 16:50 GMT+02:00 Sebastian Arcus : >> I've searched the list messages over the last few weeks but can't figure the >> answer. Is SBo open to new submissions yet - or there will be no more new >> stuff until next version of Slackware, or how does it work? As some of you >> know I've helped prepare the Navit SBo scripts, but that was just before >> 14.2 was released so I was told to hold fire. When should I submit it? > > Hi Sebastian, > > maybe you missed Willy's message on july 24th > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-July/016643.html I certainly did - thank you for that! I confess I can't manage to read all the messages on the list - so I just did a search by subject. Thank you again for pointing it out. From rob0 at slackbuilds.org Wed Aug 10 17:35:18 2016 From: rob0 at slackbuilds.org (Rob McGee) Date: Wed, 10 Aug 2016 12:35:18 -0500 Subject: [Slackbuilds-users] Are new submission accepted yet? In-Reply-To: References: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> Message-ID: <20160810173518.GC22481@harrier.slackbuilds.org> On Wed, Aug 10, 2016 at 09:51:40AM +0100, Sebastian Arcus wrote: > On 09/08/16 15:56, Matteo Bernardini wrote: > >2016-08-09 16:50 GMT+02:00 Sebastian Arcus : > >>I've searched the list messages over the last few weeks but can't > >>figure the answer. Is SBo open to new submissions yet - or there > >>will be no more new stuff until next version of Slackware, or how > >>does it work? As some of you know I've helped prepare the Navit > >>SBo scripts, but that was just before 14.2 was released so I was > >>told to hold fire. When should I submit it? > > > >maybe you missed Willy's message on july 24th > > > >https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-July/016643.html > > I certainly did - thank you for that! I confess I can't manage to > read all the messages on the list - so I just did a search by > subject. Thank you again for pointing it out. Do we need an announcement list? If we had it I don't think it should include routine announcements like updates ... we would want something useful to people like Sebastian, with no more than a few posts per year. When submissions close, when they open, any major changes, ... Is that a good idea? I'm not convinced that it is, myself, because we also have IRC, and the /topic has this information. Also, the submission form itself would have been another way to find out. :) -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From bryanlharris at gmail.com Wed Aug 10 17:51:25 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Wed, 10 Aug 2016 13:51:25 -0400 Subject: [Slackbuilds-users] Are new submission accepted yet? In-Reply-To: <20160810173518.GC22481@harrier.slackbuilds.org> References: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> <20160810173518.GC22481@harrier.slackbuilds.org> Message-ID: The fedora people have a list called devel-anounce that you have to join if you want to be a package maintainer. It is supposed to be a low volume list (I just joined a little while ago today). But then again just talking about it on the list seems to have resolved the situation easily enough, and their entire situation over there reminds me of gov't-level amounts of bureaucracy. So I'm not sure I should be pointing to them as a good example. V/r, Bryan On Wed, Aug 10, 2016 at 1:35 PM, Rob McGee wrote: > On Wed, Aug 10, 2016 at 09:51:40AM +0100, Sebastian Arcus wrote: > > On 09/08/16 15:56, Matteo Bernardini wrote: > > >2016-08-09 16:50 GMT+02:00 Sebastian Arcus : > > >>I've searched the list messages over the last few weeks but can't > > >>figure the answer. Is SBo open to new submissions yet - or there > > >>will be no more new stuff until next version of Slackware, or how > > >>does it work? As some of you know I've helped prepare the Navit > > >>SBo scripts, but that was just before 14.2 was released so I was > > >>told to hold fire. When should I submit it? > > > > > >maybe you missed Willy's message on july 24th > > > > > >https://lists.slackbuilds.org/pipermail/slackbuilds- > users/2016-July/016643.html > > > > I certainly did - thank you for that! I confess I can't manage to > > read all the messages on the list - so I just did a search by > > subject. Thank you again for pointing it out. > > Do we need an announcement list? > > If we had it I don't think it should include routine announcements > like updates ... we would want something useful to people like > Sebastian, with no more than a few posts per year. When submissions > close, when they open, any major changes, ... > > Is that a good idea? I'm not convinced that it is, myself, because > we also have IRC, and the /topic has this information. > > Also, the submission form itself would have been another way to find > out. :) > -- > Rob McGee - /dev/rob0 - rob0 at slackbuilds.org > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Thu Aug 11 02:32:29 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 10 Aug 2016 19:32:29 -0700 Subject: [Slackbuilds-users] Are new submission accepted yet? In-Reply-To: <20160810173518.GC22481@harrier.slackbuilds.org> References: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> <20160810173518.GC22481@harrier.slackbuilds.org> Message-ID: On Wednesday, August 10, 2016, Rob McGee wrote: > > > Do we need an announcement list? > > If we had it I don't think it should include routine announcements > like updates ... we would want something useful to people like > Sebastian, with no more than a few posts per year. When submissions > close, when they open, any major changes, ... > > Is that a good idea? I'm not convinced that it is, myself, because > we also have IRC, and the /topic has this information. > > Also, the submission form itself would have been another way to find > out. :) > -- > Rob McGee - /dev/rob0 - rob0 at slackbuilds.org > > Ugh. please not anothet list! ?? Easy enough to check here, IRC or as rob mentioned, the form. Perhaps a news ticker or page or banner on web site? I'm fine though the way it is. -Ed -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Thu Aug 11 09:11:29 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 11 Aug 2016 10:11:29 +0100 Subject: [Slackbuilds-users] New submission - Navit Message-ID: <10b12ffc-908c-5935-0b8a-9b56bc28612f@open-t.co.uk> As previously mentioned on this list, I'd like to submit the package Navit (www.navit-project.org) for inclusion at SBo. I think the appropriate category would be GIS. Many thanks to David Spencer for help with testing and corrections. -------------- next part -------------- A non-text attachment was scrubbed... Name: navit.tar.gz Type: application/gzip Size: 2976 bytes Desc: not available URL: From s.arcus at open-t.co.uk Thu Aug 11 09:31:23 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 11 Aug 2016 10:31:23 +0100 Subject: [Slackbuilds-users] Are new submission accepted yet? In-Reply-To: <20160810173518.GC22481@harrier.slackbuilds.org> References: <0e295505-6057-5b00-67d4-ff69b5bf3319@open-t.co.uk> <20160810173518.GC22481@harrier.slackbuilds.org> Message-ID: <05f0da39-d050-77e0-a0fa-068d4ce4a42b@open-t.co.uk> On 10/08/16 18:35, Rob McGee wrote: > On Wed, Aug 10, 2016 at 09:51:40AM +0100, Sebastian Arcus wrote: >> On 09/08/16 15:56, Matteo Bernardini wrote: >>> 2016-08-09 16:50 GMT+02:00 Sebastian Arcus : >>>> I've searched the list messages over the last few weeks but can't >>>> figure the answer. Is SBo open to new submissions yet - or there >>>> will be no more new stuff until next version of Slackware, or how >>>> does it work? As some of you know I've helped prepare the Navit >>>> SBo scripts, but that was just before 14.2 was released so I was >>>> told to hold fire. When should I submit it? >>> >>> maybe you missed Willy's message on july 24th >>> >>> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-July/016643.html >> >> I certainly did - thank you for that! I confess I can't manage to >> read all the messages on the list - so I just did a search by >> subject. Thank you again for pointing it out. > > Do we need an announcement list? Maybe a much simpler solution would be to post important announcements as a new post, on their own - with a suitable subject line - such as "Announcement: New submissions accepted etc. etc....". That's actually what I searched for initially - by subject line. If announcements are included inside another longer post, it is more difficult to find them. Then again, this is a friendly list, and one way or another answers are always forthcoming :-) From s.arcus at open-t.co.uk Thu Aug 11 09:32:34 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 11 Aug 2016 10:32:34 +0100 Subject: [Slackbuilds-users] Version bump - syncthing 14.4 Message-ID: <7ddd3f6e-f559-1e46-e452-492737a2123c@open-t.co.uk> Please find attached a version bump (plus a few minor corrections) for syncthing -------------- next part -------------- A non-text attachment was scrubbed... Name: syncthing.tar.gz Type: application/gzip Size: 3455 bytes Desc: not available URL: From s.arcus at open-t.co.uk Thu Aug 11 09:38:34 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 11 Aug 2016 10:38:34 +0100 Subject: [Slackbuilds-users] Comments required for iperf3 submission Message-ID: I use iperf3 from time to time and find it very useful. I noticed that SBo only has iperf2 - and would like to submit scripts for iperf3. Is there much interest in this, and also, is there any reason why SBo shouldn't have iperf3? From willysr at slackbuilds.org Thu Aug 11 09:57:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 11 Aug 2016 16:57:39 +0700 Subject: [Slackbuilds-users] Version bump - syncthing 14.4 In-Reply-To: <7ddd3f6e-f559-1e46-e452-492737a2123c@open-t.co.uk> References: <7ddd3f6e-f559-1e46-e452-492737a2123c@open-t.co.uk> Message-ID: <60e1536a-15cb-fae3-7271-a7715e7397eb@slackbuilds.org> > Please find attached a version bump (plus a few minor corrections) for > syncthing Please use the submission form as usual since the submission is now open. This applies to Navit that you sent earlier -- 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 Thu Aug 11 10:29:36 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 11 Aug 2016 11:29:36 +0100 Subject: [Slackbuilds-users] Version bump - syncthing 14.4 In-Reply-To: <60e1536a-15cb-fae3-7271-a7715e7397eb@slackbuilds.org> References: <7ddd3f6e-f559-1e46-e452-492737a2123c@open-t.co.uk> <60e1536a-15cb-fae3-7271-a7715e7397eb@slackbuilds.org> Message-ID: On 11/08/16 10:57, Willy Sudiarto Raharjo wrote: >> Please find attached a version bump (plus a few minor corrections) for >> syncthing > > Please use the submission form as usual since the submission is now > open. This applies to Navit that you sent earlier Sure - thank you Willy From s.arcus at open-t.co.uk Thu Aug 11 11:55:41 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 11 Aug 2016 12:55:41 +0100 Subject: [Slackbuilds-users] Fwd: monit change request In-Reply-To: References: <20160805174735.5853265.70380.2014@gmail.com> <27e7ac95-7b8b-bc93-9d51-c98027b0b81f@open-t.co.uk> Message-ID: <223456a6-892e-9d16-c7ca-eb99aa45776e@open-t.co.uk> On 08/08/16 13:32, Bryan Harris wrote: > Interesting re: the restart command. I think it's fixed by using > "monit quit" for the implementation of /etc/rc.d/rc.monit stop --- > i.e. more like what the upstream authors would do. It's instantly > restarted on my machine when I do restart (using rc.monit script from > my last web form submission to SBo). > > Can you test if it still behaves that way with the latest/current SBo package? I just did - and it still kills monit From willysr at slackbuilds.org Thu Aug 11 14:42:33 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 11 Aug 2016 21:42:33 +0700 Subject: [Slackbuilds-users] Comments required for iperf3 submission In-Reply-To: References: Message-ID: <91973b5d-8b15-5b8d-9de3-57773e1e8f6e@slackbuilds.org> > I use iperf3 from time to time and find it very useful. I noticed that > SBo only has iperf2 - and would like to submit scripts for iperf3. Is > there much interest in this, and also, is there any reason why SBo > shouldn't have iperf3? the maintainer is no longer active i guess his last update was 6 years ago i think you can take over this package and update it to iperf3 -- 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 ts at websafe.pl Thu Aug 11 15:04:00 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 11 Aug 2016 17:04:00 +0200 Subject: [Slackbuilds-users] Comments required for iperf3 submission In-Reply-To: <91973b5d-8b15-5b8d-9de3-57773e1e8f6e@slackbuilds.org> References: <91973b5d-8b15-5b8d-9de3-57773e1e8f6e@slackbuilds.org> Message-ID: <0a6e303b-ec9d-c9e6-947e-383a62d76a5a@websafe.pl> On 11.08.2016 16:42, Willy Sudiarto Raharjo wrote: >> I use iperf3 from time to time and find it very useful. I noticed that >> SBo only has iperf2 - and would like to submit scripts for iperf3. Is >> there much interest in this, and also, is there any reason why SBo >> shouldn't have iperf3? > the maintainer is no longer active i guess > his last update was 6 years ago > i think you can take over this package and update it to iperf3 I would not update it to iperf3 but create a separate iperf3 SlackBuild, because there are iperf2 and iperf3 clients out there, and v2 is not compatible with v3. https://iperf.fr/iperf-download.php Not every platform has iperf3 available and both v2 and v3 are AFAIK still under development, so I think it would be good to have both available. Just a thought. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From s.arcus at open-t.co.uk Thu Aug 11 15:22:14 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 11 Aug 2016 16:22:14 +0100 Subject: [Slackbuilds-users] Comments required for iperf3 submission In-Reply-To: <0a6e303b-ec9d-c9e6-947e-383a62d76a5a@websafe.pl> References: <91973b5d-8b15-5b8d-9de3-57773e1e8f6e@slackbuilds.org> <0a6e303b-ec9d-c9e6-947e-383a62d76a5a@websafe.pl> Message-ID: On 11/08/16 16:04, Thomas Szteliga wrote: > On 11.08.2016 16:42, Willy Sudiarto Raharjo wrote: >>> I use iperf3 from time to time and find it very useful. I noticed that >>> SBo only has iperf2 - and would like to submit scripts for iperf3. Is >>> there much interest in this, and also, is there any reason why SBo >>> shouldn't have iperf3? >> the maintainer is no longer active i guess >> his last update was 6 years ago >> i think you can take over this package and update it to iperf3 > > > I would not update it to iperf3 but create a separate > iperf3 SlackBuild, because there are iperf2 and iperf3 > clients out there, and v2 is not compatible with v3. > > https://iperf.fr/iperf-download.php > > Not every platform has iperf3 available and both > v2 and v3 are AFAIK still under development, > so I think it would be good to have both > available. Just a thought. Yes - I think iperf2 and iperf3 are not compatible. I think having both iperf2 and iperf3 on SBo would be best. From atelszewski at gmail.com Fri Aug 12 02:44:28 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 12 Aug 2016 04:44:28 +0200 Subject: [Slackbuilds-users] lighttpd.SlackBuild needs new maintainer Message-ID: Hi, I contacted current maintainer of lighttpd, Paul Wisehart, and he said he will no longer maintain the lighttpd.SlackBuild. I'm no expert in the area, but I would like to point a few things for the new maintainer: 1. In https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/README.SLACKWARE the location of php.ini should no longer be /etc/httpd, but /etc. 2. I'm not sure about that, but since the SlackBuild allows for changing user/group, the following line in https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/conf/lighttpd.logrotate: create 0644 lighttpd lighttpd should be changed to: create 0644 @USER@ @GROUP@ or simply: create 3. Probably it would be a good idea to provide more recent configuration file example. On a side note, (lighttpd2) https://slackbuilds.org/slackbuilds/14.2/network/lighttpd2/README.SLACKWARE, also contains /etc/httpd/php.ini, which should be changed to /etc/php.ini and possibly hardcoded user name in the logrotate conf file. -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Fri Aug 12 05:22:09 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 12 Aug 2016 07:22:09 +0200 Subject: [Slackbuilds-users] lighttpd.SlackBuild needs new maintainer In-Reply-To: References: Message-ID: 2016-08-12 4:44 GMT+02:00 Andrzej Telszewski : > Hi, > > I contacted current maintainer of lighttpd, Paul Wisehart, and he said he > will no longer maintain the lighttpd.SlackBuild. > > I'm no expert in the area, but I would like to point a few things for the > new maintainer: > > 1. In > https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/README.SLACKWARE > the location of php.ini should no longer be /etc/httpd, but /etc. > > 2. I'm not sure about that, but since the SlackBuild allows for changing > user/group, the following line in > https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/conf/lighttpd.logrotate: > > create 0644 lighttpd lighttpd > > should be changed to: > > create 0644 @USER@ @GROUP@ > > or simply: > > create > > 3. Probably it would be a good idea to provide more recent configuration > file example. > > > On a side note, (lighttpd2) > https://slackbuilds.org/slackbuilds/14.2/network/lighttpd2/README.SLACKWARE, > also contains /etc/httpd/php.ini, which should be changed to /etc/php.ini > and possibly hardcoded user name in the logrotate conf file. as I use lighttpd, if it's ok I'll step up as a maintainer. Matteo P.S. thanks Andrzej, I'll have a look at it. From s.arcus at open-t.co.uk Fri Aug 12 13:43:09 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Fri, 12 Aug 2016 14:43:09 +0100 Subject: [Slackbuilds-users] lighttpd.SlackBuild needs new maintainer In-Reply-To: References: Message-ID: <3f0dc495-09f1-6332-074a-cbe063d20784@open-t.co.uk> On 12/08/16 03:44, Andrzej Telszewski wrote: > Hi, > > I contacted current maintainer of lighttpd, Paul Wisehart, and he said > he will no longer maintain the lighttpd.SlackBuild. I've been using Lighttpd on Slackware for a few years now, but I'm not an expert on the matter. It would be great if somebody who is advanced in configuring Lighttpd would take it over. Otherwise I'm happy to take it over - if that's ok with the admins. From s.arcus at open-t.co.uk Fri Aug 12 13:44:09 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Fri, 12 Aug 2016 14:44:09 +0100 Subject: [Slackbuilds-users] lighttpd.SlackBuild needs new maintainer In-Reply-To: References: Message-ID: <7a14d3a6-a32d-6d41-cf32-4c8fe800b560@open-t.co.uk> On 12/08/16 06:22, Matteo Bernardini wrote: > 2016-08-12 4:44 GMT+02:00 Andrzej Telszewski : >> Hi, >> >> I contacted current maintainer of lighttpd, Paul Wisehart, and he said he >> will no longer maintain the lighttpd.SlackBuild. >> >> I'm no expert in the area, but I would like to point a few things for the >> new maintainer: >> >> 1. In >> https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/README.SLACKWARE >> the location of php.ini should no longer be /etc/httpd, but /etc. >> >> 2. I'm not sure about that, but since the SlackBuild allows for changing >> user/group, the following line in >> https://slackbuilds.org/slackbuilds/14.2/network/lighttpd/conf/lighttpd.logrotate: >> >> create 0644 lighttpd lighttpd >> >> should be changed to: >> >> create 0644 @USER@ @GROUP@ >> >> or simply: >> >> create >> >> 3. Probably it would be a good idea to provide more recent configuration >> file example. >> >> >> On a side note, (lighttpd2) >> https://slackbuilds.org/slackbuilds/14.2/network/lighttpd2/README.SLACKWARE, >> also contains /etc/httpd/php.ini, which should be changed to /etc/php.ini >> and possibly hardcoded user name in the logrotate conf file. > > as I use lighttpd, if it's ok I'll step up as a maintainer. Sorry - I sent my email before seeing yours. That's great news! From matteo.bernardini at gmail.com Fri Aug 12 14:01:55 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 12 Aug 2016 16:01:55 +0200 Subject: [Slackbuilds-users] lighttpd.SlackBuild needs new maintainer In-Reply-To: <7a14d3a6-a32d-6d41-cf32-4c8fe800b560@open-t.co.uk> References: <7a14d3a6-a32d-6d41-cf32-4c8fe800b560@open-t.co.uk> Message-ID: https://slackbuilds.org/cgit/slackbuilds/commit/?id=f90c8d8c0e9faebc1758954f83d77a1da3064b73 From atelszewski at gmail.com Fri Aug 12 14:49:33 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 12 Aug 2016 16:49:33 +0200 Subject: [Slackbuilds-users] lighttpd.SlackBuild needs new maintainer In-Reply-To: References: <7a14d3a6-a32d-6d41-cf32-4c8fe800b560@open-t.co.uk> Message-ID: On 12/08/16 16:01, Matteo Bernardini wrote: > https://slackbuilds.org/cgit/slackbuilds/commit/?id=f90c8d8c0e9faebc1758954f83d77a1da3064b73 Nice job :) -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sat Aug 13 00:41:33 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 13 Aug 2016 07:41:33 +0700 Subject: [Slackbuilds-users] Updates - 20160813.1 Message-ID: Sat Aug 13 00:24:40 UTC 2016 academic/fet: Updated for version 5.30.2. academic/reduce-algebra: Added (portable computer algebra system). accessibility/pastebinit: Updated for version 1.5. accessibility/unclutter: Fix gcc5 warnings. accessibility/wgetpaste: Updated for version 2.28. audio/eawpats: Fix HOMEPAGE. audio/fmmidi: Updated for version 1.0.1. audio/guitarix: Updated for version 0.35.1. audio/match-vamp-plugin: Updated for version 1.0. audio/nnls-chroma: Updated for version 1.1. audio/ponymix: Updated for version 5 audio/qmidiroute: Updated for version 0.4.0. audio/sonic-visualiser: Updated for version 2.5. audio/transcribe: Fix DOWNLOAD, add libpng-legacy12 to REQUIRES. audio/vamp-plugin-sdk: Updated for version 2.6. desktop/cwp: Updated for version 1.12.1. desktop/gxkb: Updated for version 0.7.7. desktop/j4-dmenu-desktop: Updated for version 2.14. desktop/lumina: Updated for version 1.0.0-p1. desktop/obmenu-generator: Update script. desktop/sawfish: Updated for version 1.11.91. desktop/xdgmenumaker: Updated for version 0.9. desktop/xtrlock: Updated for version 2.8. development/SQLAlchemy: Add python3 support. development/bas55: Updated for version 1.10. development/conan: Added (distributed package manager). development/ex-vi: Fix build. development/fossil: Updated for version 1.35. development/kaaedit: Updated for version 0.53.0. development/komodo-edit: Fix ARCH detection. development/komodo-ide: Fix ARCH detection. development/openjdk6: Added (Open Implementation of JDK). development/openjdk8: Added (Open Implementation of JDK). development/openjdk: Updated for version 7u111b01. development/pycharm: Updated for version 2016.2.1. development/unifdef: Updated for version 2.11. development/uz80as: Added (Micro Z80 assembler). games/an: Updated for version 1.2. games/bloodcm: Added (first-person shooter game). games/burgerspace: Fix HOMEPAGE and DOWNLOAD. games/colem: Updated for version 3.7. games/cosmosmash: Fix HOMEPAGE and DOWNLOAD. games/crispy-doom: Updated for version 3.4. games/dhewm3: Updated for version 1.4.1. games/doomretro: Added (The classic, refined DOOM source port). games/eduke32: Updated for version 20160704_5811. games/fbalpha: Added (libretro port of Final Burn Alpha). games/fizmo: Updated for version 0.7.10. games/fortune_doctor_who: Updated for version 20150503. games/freedoom: Updated for version 0.10.1. games/gzdoom: Updated for version 2.1.1. games/hatari: Updated for version 1.9.0. games/innoextract: Updated for version 1.6 (Moved from system). games/koules: Update README with pulseaudio info. games/libretro-fba: Removed (replaced by fbalpha). games/libretro-lutro: Updated for version 2016.08.07_9f8464d. games/maelstrom: Fix build. games/mame: Updated for version 0.176. games/mgba: Updated for version 0.4.1. games/micropolis: Fix DOWNLOAD. games/openyahtzee: Updated for version 1.9.3. games/ostrichriders: Added (clone of the arcade game "Joust"). games/pangzero: Added (clone of arcade game "Super Pang"). games/pasang-emas: Updated for version 5.0.0. games/skulltag: Add REQUIRES=libpng-legacy12. games/smc: Update for 14.2, bump BUILD. games/sms_sdl: Fix/enhance shell script wrapper. games/stella: Updated for version 4.7.2. games/torcs: Updated for version 1.3.7. games/trigger-rally: Updated for version 0.6.4. games/vera: Updated for version 1.23. games/wordwarvi: Updated for version 1.0.2. games/xarchon: Added (fantasy-themed board game). games/xu4: Update for 14.2, bump BUILD. games/yamagi-quake2: Updated for version 5.34. games/zdbsp: Updated for version 1.19. gis/GMT: Added (Generic Mapping Tools). gis/navit: Added (gps navigation system with routing engine) graphics/mapcrafter: Added (Minecraft map renderer). graphics/mcomix: Updated for version 1.2.1. graphics/paraview: Enable Xdmf3 graphics/vsxu: Updated for version 0.5.1 libraries/CherryPy: Updated for version + new maintainer. libraries/GitPython: Add python3 support. libraries/botocore: Updated for version 1.4.44. libraries/cdk: Updated for version 5.0_20160131. libraries/compiz-plugins-experimental: Fixed REQUIRES. libraries/dropbox-python: Updated for version 6.6.2. libraries/flatzebra: Fix HOMEPAGE and DOWNLOAD. libraries/girara: Updated for version 0.2.6. libraries/jbig2dec: Updated for version 0.13. libraries/libdc1394: Updated for version 2.2.4. libraries/libfaketime: Fixed MD5SUM. libraries/libpst: Updated for version 0.6.67. libraries/live555: Updated for version 2016.08.07 libraries/ltm: Updated for version 1.0. libraries/netcdf: Fixed build with HDF4. libraries/npth: Added (New GNU Portable Threads Library). libraries/platform: Updated for version 2.0.1. libraries/qwt: Updated for version 6.1.3 libraries/tinyxml2: Updated for version 4.0.1. multimedia/aces-dev: Fixed tarball handling. multimedia/aces_container: Fixed tarball handling. multimedia/spotify: Updated for version 1.0.34.146.g28f9eda2. multimedia/vlc: Updated for version 2.2.4 multimedia/youtube-viewer: Updated for version 3.2.3. network/CherryMusic: Updated for version 0.37.2. network/awscli: Updated for version 1.10.54. network/bmon: Updated for version 3.9. network/corebird: Fixed REQUIRES. network/flexget: Updated for version 2.2.16. network/icecat: Build with -Os to prevent crashes. network/irssi_otr: Updated for version 1.0.1. network/lighttpd2: Updated for version 20151204_3a4698d. network/lighttpd: Refactor configuration, changed maintainer. network/midori: Remove libunique from REQUIRES, cleanups. network/nbd: Updated for version 3.14 network/ntop: Fixed build with rrdtool-1.6.0. network/smcroute: Fixed DOWNLOAD. network/syncthing: Updated for version 0.14.4. network/tor: Updated for version 0.2.8.6 + new maintainer. network/uget: Updated for version 2.0.8. network/vivaldi: Updated for version 1.3.551.30. network/x11vnc: Update maintainer details network/youtube-dl: Updated for version 2016.08.10. network/yturl: Updated for version 2.0.1. office/CherryTree: Updated for version 0.37.3. office/LibreOffice: Updated for version 5.2.0.4 office/convertlit: Fix lit2epub script. office/fbpdf: Updated for version 20160804. office/lyx: Updated for version 2.2.1. office/mupdf: Updated for version 1.9a. office/zathura-cb: Updated for version 0.1.5. office/zathura-djvu: Updated for version 0.2.5. office/zathura-pdf-mupdf: Updated for version 0.3.0. office/zathura-ps: Updated for version 0.2.3. office/zathura: Updated for version 0.3.6. perl/perl-extutils-makemaker: Updated for version 7.20. python/APScheduler: Updated for version 3.2.0. python/Flask-Compress: Added (compress responses in your Flask app). python/Flask-Cors: Added (Flask extension for handling CORS). python/Flask-Login: Added (User session management for Flask). python/Flask-RESTful: Added (framework for creating REST APIs). python/PyGithub: Updated for version 1.27.1. python/PythonQt: Added (Python binding for Qt). python/aniso8601: Added (library for parsing ISO 8601 strings). python/cfgparse: Added (Python Configuration Parser Module). python/euca2ools: Updated for 3.3.1 python/fasteners: Added (useful locks for Python). python/feedparser: Updated for version 5.2.1 python/flake8: Updated for version 3.0.4. python/flask-restplus: Added (Flask extn for building REST APIs). python/funcsigs: Added (Backport of the PEP 362). python/monotonic: Added (implementation of time.monotonic()). python/monty: Updated for version 0.9.0. python/pathlib: Added (Object-oriented filesystem paths). python/pyjwt: Added (JSON Web Token implementation in Python). python/python-Safe: Added (Check the password strength). python/python-certifi: Updated for version 2016.8.8. python/python-keybinder: Updated for version 0.3.1. python/python-patch: Added (library to parse+apply unified diffs). python/python-requestbuilder: Updated for version 0.5.2 python/python-requests: Updated for version 2.10.0. python/typing: Added (Type Hints for Python). system/acpi_call: Added (kernel module for calling ACPI methods). system/aha: Updated for version 0.4.9. system/etckeeper: Updated for version 1.18.5. system/isomd5sum: Updated for version 1.1.0, add Python 3 support. system/lbzip2: Fix HOMEPAGE. system/lhasa: Updated for version 0.3.1. system/linuxconsoletools: Updated for version 1.5.1. system/localepurge: Added (remove superfluous locale data). system/macutils: Fix compiler warnings. system/man-db: Updated for version 2.7.3. system/man-pages-ja: Updated for version 20160715, use ARCH=noarch. system/monit: Updated for version 5.19.0. system/rover: Updated for version 0.4.2. system/usbmon: Updated for version 6.1. system/x86_energy_perf_policy: Added (Energy Savings Policy). system/zerofree: Updated for version 1.0.4. system/zpaq: Updated for version 7.14 +--------------------------+ -- 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 alik at ejik.org Sat Aug 13 11:26:51 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 13 Aug 2016 14:26:51 +0300 Subject: [Slackbuilds-users] Updates - 20160813.1 In-Reply-To: References: Message-ID: <1471087611.3750399.694262785.6516A76A@webmail.messagingengine.com> Hello, on the page https://slackbuilds.org/repository/14.2/academic/reduce-algebra/ the keyword "psl" is destroyed by a line break. Best regards, Alexander From willysr at slackbuilds.org Sat Aug 13 14:32:10 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 13 Aug 2016 21:32:10 +0700 Subject: [Slackbuilds-users] Updates - 20160813.1 In-Reply-To: <1471087611.3750399.694262785.6516A76A@webmail.messagingengine.com> References: <1471087611.3750399.694262785.6516A76A@webmail.messagingengine.com> Message-ID: <3dc3f91b-5754-4b3b-4cc2-0c7009633ba2@slackbuilds.org> > on the page > https://slackbuilds.org/repository/14.2/academic/reduce-algebra/ > the keyword "psl" is destroyed by a line break. fixed -- 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 rshepard at appl-ecosys.com Sat Aug 13 23:47:34 2016 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 13 Aug 2016 16:47:34 -0700 (PDT) Subject: [Slackbuilds-users] php-pgsql appears not to be working Message-ID: I downloaded, built, and installed php-pgsql for php-5.6.24, yet still cannot connect to the database as I try to install an application. Firefox shows me this error: Syntax error in file: /opt/xrms/include/adodb/drivers/adodb-postgresql.inc.php ADONewConnection: Unable to load database driver Can someone point me to what I've missed doing? TIA, Rich From sombragris at sombragris.org Sat Aug 13 20:15:07 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 13 Aug 2016 16:15:07 -0400 Subject: [Slackbuilds-users] BUG: latest mame update fails checksum Message-ID: <0q93i.703382033b.20160813161507.2c5d0ce0@loli.sombragris.org> This was tested in three times. Current mame source download does not match the expected checksum. > mame: > MD5SUM check for mame0176.tar.gz ... FAILED! > Expected: 78f2b4ade458bc21d3ab95a4fbe0c03d > Found: b2aed655e1ea2bccf26bf96f189257ba > Downloading again. > MD5SUM check for mame0176.tar.gz ... FAILED! > Expected: 78f2b4ade458bc21d3ab95a4fbe0c03d > Found: b2aed655e1ea2bccf26bf96f189257ba > Source deleted. Thanks, Eduardo S?nchez -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== From sombragris at sombragris.org Sat Aug 13 20:17:58 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 13 Aug 2016 16:17:58 -0400 Subject: [Slackbuilds-users] BUG: wordwarvi source incorrectly stated Message-ID: <0q93i.2033551401.20160813161758.2bb946a3@loli.sombragris.org> While updating 'wordwarvi' I had this problem: > wordwarvi: > Found v1.0.2.tar.gz in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for v1.0.2.tar.gz ... OK > Building package for wordwarvi... > tar: /var/lib/sbopkg/SBo/14.2/games/wordwarvi/wordwarvi-1.0.2.tar.gz: > Cannot open: No such file or directory tar: Error is not recoverable: > exiting now tar: v1.0.2.tar.gz: Cannot open: No such file or directory > tar: Error is not recoverable: exiting now It seems that the source package specification is incorrect. Thanks, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== From willysr at slackbuilds.org Sun Aug 14 00:57:37 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Aug 2016 07:57:37 +0700 Subject: [Slackbuilds-users] BUG: wordwarvi source incorrectly stated In-Reply-To: <0q93i.2033551401.20160813161758.2bb946a3@loli.sombragris.org> References: <0q93i.2033551401.20160813161758.2bb946a3@loli.sombragris.org> Message-ID: <35cecf30-ada2-bfca-dca6-6e3686dab056@slackbuilds.org> > While updating 'wordwarvi' I had this problem: > >> wordwarvi: >> Found v1.0.2.tar.gz in /var/cache/sbopkg. >> Checking MD5SUM: >> MD5SUM check for v1.0.2.tar.gz ... OK >> Building package for wordwarvi... >> tar: /var/lib/sbopkg/SBo/14.2/games/wordwarvi/wordwarvi-1.0.2.tar.gz: >> Cannot open: No such file or directory tar: Error is not recoverable: >> exiting now tar: v1.0.2.tar.gz: Cannot open: No such file or directory >> tar: Error is not recoverable: exiting now > > It seems that the source package specification is incorrect. Thanks 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 willysr at slackbuilds.org Sun Aug 14 00:58:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Aug 2016 07:58:27 +0700 Subject: [Slackbuilds-users] php-pgsql appears not to be working In-Reply-To: References: Message-ID: <958ced2f-2333-acc6-3519-b9035c720748@slackbuilds.org> > I downloaded, built, and installed php-pgsql for php-5.6.24, yet still > cannot connect to the database as I try to install an application. Firefox > shows me this error: > > Syntax error in file: > /opt/xrms/include/adodb/drivers/adodb-postgresql.inc.php > ADONewConnection: Unable to load database driver > > Can someone point me to what I've missed doing? Based on the message, it seems to be a syntax error? -- 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 ts at websafe.pl Sun Aug 14 01:05:04 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 14 Aug 2016 03:05:04 +0200 Subject: [Slackbuilds-users] php-pgsql appears not to be working In-Reply-To: References: Message-ID: On 14.08.2016 01:47, Rich Shepard wrote: > I downloaded, built, and installed php-pgsql for php-5.6.24, yet still > cannot connect to the database as I try to install an application. Firefox > shows me this error: > Syntax error in file: > /opt/xrms/include/adodb/drivers/adodb-postgresql.inc.php > ADONewConnection: Unable to load database driver > Can someone point me to what I've missed doing? Have you done the following: > To enable the pgsql extension for php, go to /etc/php.d/pgsql.ini > and uncomment the line: > ; extension=pgsql.so https://slackbuilds.org/slackbuilds/14.2/libraries/php-pgsql/README Apache restarted? Sometimes, when adding extensions, you'll need to stop apache and then start. If stoppping and starting apache wont help, please show the result of phpinfo(); -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Aug 14 01:11:42 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 14 Aug 2016 03:11:42 +0200 Subject: [Slackbuilds-users] php-pgsql appears not to be working In-Reply-To: <958ced2f-2333-acc6-3519-b9035c720748@slackbuilds.org> References: <958ced2f-2333-acc6-3519-b9035c720748@slackbuilds.org> Message-ID: <49f8219e-6064-ab8f-e7a9-68055ad7304b@websafe.pl> On 14.08.2016 02:58, Willy Sudiarto Raharjo wrote: > Based on the message, it seems to be a syntax error? Yes, that's strange, because adodb has no file named adodb-postgresql.inc.php https://github.com/ADOdb/ADOdb/tree/master/drivers/ -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sun Aug 14 01:34:36 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Aug 2016 08:34:36 +0700 Subject: [Slackbuilds-users] libxml++ vs. mm-common In-Reply-To: <42137af2-f945-2e64-1a13-6f438635dedc@microlinux.fr> References: <42137af2-f945-2e64-1a13-6f438635dedc@microlinux.fr> Message-ID: > According to the README, libxml++ requires mm-common. I just compiled it > without mm-common, and it builds fine. Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Aug 14 01:36:50 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Aug 2016 08:36:50 +0700 Subject: [Slackbuilds-users] Processing In-Reply-To: References: Message-ID: > Processing is SBo is 5 years old. > > Latest version is 3.1.1 and here's diffs for .SlackBuild and .info : Since it's been more then few weeks, i suggest for you to step up as a maintainer for this script if you are using it. -- 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 Sun Aug 14 01:40:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Aug 2016 08:40:02 +0700 Subject: [Slackbuilds-users] cantarell-fonts In-Reply-To: <74261d04-f831-9c1c-40d6-6507bb68cfb9@microlinux.fr> References: <74261d04-f831-9c1c-40d6-6507bb68cfb9@microlinux.fr> Message-ID: > Two remarks on the cantarell-fonts package. > > 1. The SlackBuild specifies an ARCH. Fonts packages should be noarch. Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From molbolom at gmail.com Sun Aug 14 02:03:19 2016 From: molbolom at gmail.com (Charles Kauffman) Date: Sat, 13 Aug 2016 21:03:19 -0500 Subject: [Slackbuilds-users] Direct linking so files instead of linked so files? Message-ID: Ok, first off this is a rhetorical question. I'm away from my home computer and will have to research it from there. However, however, if anyone has any words of wisdom about this, by no means does this question need to be answerless. (My brain works in horrible ways, and this happens to work for me, so meh, make of it what you will, HAH). Anyhoo! While trying to run an app I maintain (equalx) I realized that the latest upgrade to 14.2 (which was current back those many moons ago) kind of broke because of the symlink to libpoppler. libpoppler.so.58 was the originally linked library, but now I have libpoppler.so.62. Sooo, in the offchance that certain particular routines in a library for a piece of software wouldn't need an upgrade, what could be searched in the Makefile to force it to compile using the non-linked library in order to diff and patch? Please, for the love of Pete, I'm not trying to rustle any one's jimmies if there'd be bad juju in modifying a slackbuild for something like that. I'm away from home, have a thousand things on my mind, and am a little out of my mind. Have a happy! I'm a little teacup short and stout... -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Aug 14 02:09:38 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Aug 2016 09:09:38 +0700 Subject: [Slackbuilds-users] Direct linking so files instead of linked so files? In-Reply-To: References: Message-ID: <499baea5-b7b7-0084-1e7f-4cf486d771e1@slackbuilds.org> > Ok, first off this is a rhetorical question. I'm away from my home computer > and will have to research it from there. However, however, if anyone has > any words of wisdom about this, by no means does this question need to be > answerless. (My brain works in horrible ways, and this happens to work for > me, so meh, make of it what you will, HAH). > > Anyhoo! While trying to run an app I maintain (equalx) I realized that the > latest upgrade to 14.2 (which was current back those many moons ago) kind > of broke because of the symlink to libpoppler. libpoppler.so.58 was the > originally linked library, but now I have libpoppler.so.62. Sooo, in the > offchance that certain particular routines in a library for a piece of > software wouldn't need an upgrade, what could be searched in the Makefile > to force it to compile using the non-linked library in order to diff and > patch? normally a simple rebuilt will fix the issue -- 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 molbolom at gmail.com Sun Aug 14 02:13:58 2016 From: molbolom at gmail.com (Charles Kauffman) Date: Sat, 13 Aug 2016 21:13:58 -0500 Subject: [Slackbuilds-users] Direct linking so files instead of linked so files? In-Reply-To: <499baea5-b7b7-0084-1e7f-4cf486d771e1@slackbuilds.org> References: <499baea5-b7b7-0084-1e7f-4cf486d771e1@slackbuilds.org> Message-ID: Well, took me a few seconds to find out it wasn't equalx that was the problem, but it may crop up some time so not a completely wasted question. And yeah, I know a rebuild would be necessary for something large, say Texlive (Which is where the problem lies. Hoo boy! That's going to have to wait til I'm back home), but it's something I'm curious about for something small that shouldn't need the whole cornucopia of routines within a library. On Sat, Aug 13, 2016 at 9:09 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Ok, first off this is a rhetorical question. I'm away from my home > computer > > and will have to research it from there. However, however, if anyone has > > any words of wisdom about this, by no means does this question need to be > > answerless. (My brain works in horrible ways, and this happens to work > for > > me, so meh, make of it what you will, HAH). > > > > Anyhoo! While trying to run an app I maintain (equalx) I realized that > the > > latest upgrade to 14.2 (which was current back those many moons ago) kind > > of broke because of the symlink to libpoppler. libpoppler.so.58 was the > > originally linked library, but now I have libpoppler.so.62. Sooo, in the > > offchance that certain particular routines in a library for a piece of > > software wouldn't need an upgrade, what could be searched in the Makefile > > to force it to compile using the non-linked library in order to diff and > > patch? > > normally a simple rebuilt will fix the issue > > > -- > 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 willysr at slackbuilds.org Sun Aug 14 02:21:51 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 14 Aug 2016 09:21:51 +0700 Subject: [Slackbuilds-users] Updates - 20160814.1 Message-ID: <1ce9ffaf-749b-7a55-2725-976164d2f7ec@slackbuilds.org> Sun Aug 14 02:16:18 UTC 2016 development/cppcheck: Updated for version 1.75. development/hhvm: Updated for version 3.14.4. games/ds-models: /usr/bin => /usr/games. games/mame: Fix MD5SUM. games/sdlpop: Added (Prince of Persia rewrite). games/wordwarvi: Fix script. libraries/botocore: Updated for version 1.4.46. libraries/dropbox-python: Updated for version 6.7.0. libraries/enca: Updated for version 1.18 libraries/hdf: Fixes to build script. libraries/irrlicht: Updated for version 1.8.4 libraries/libxml++: Removed dep. libraries/qt5: Rename linguist desktop file multimedia/Mopidy: Updated for version 2.0.1. multimedia/spotify: Updated for version 1.0.36.120.g536a862f. network/awscli: Updated for version 1.10.56. network/flexget: Updated for version 2.2.17. network/youtube-dl: Updated for version 2016.08.12. python/python-requests: Updated for version 2.11.0. system/cantarell-fonts: Use noarch. system/rover: Fix typo + remove config.h. +--------------------------+ -- 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 yalhcru at gmail.com Sun Aug 14 04:07:00 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 14 Aug 2016 00:07:00 -0400 Subject: [Slackbuilds-users] BUG: latest mame update fails checksum In-Reply-To: <0q93i.703382033b.20160813161507.2c5d0ce0@loli.sombragris.org> References: <0q93i.703382033b.20160813161507.2c5d0ce0@loli.sombragris.org> Message-ID: On 8/13/16, Eduardo Sanchez wrote: > This was tested in three times. > > Current mame source download does not match the expected checksum. Thanks, that was a thinko. The md5sum in the info file was for the 0.175 zip file, while I was working on the script 0.176 was released and I never got around to updating the md5sum. It's been fixed in Willy's latest update: > games/mame: Fix MD5SUM. From klaatu at member.fsf.org Sun Aug 14 05:08:59 2016 From: klaatu at member.fsf.org (Klaatu) Date: Sun, 14 Aug 2016 17:08:59 +1200 Subject: [Slackbuilds-users] Processing In-Reply-To: References: Message-ID: <45cf50e0-ff3a-193a-13e9-2c936edef3a5@member.fsf.org> I'll take Processing. I actually maintain a package for it already, privately, so it's easy for me to bring it to SBo. -klaatu On 14/08/16 13:36, Willy Sudiarto Raharjo wrote: >> Processing is SBo is 5 years old. >> >> Latest version is 3.1.1 and here's diffs for .SlackBuild and .info : > > Since it's been more then few weeks, i suggest for you to step up as a > maintainer for this script if you are using it. > > > > > _______________________________________________ > 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 klaatu at member.fsf.org Sun Aug 14 05:29:05 2016 From: klaatu at member.fsf.org (Klaatu) Date: Sun, 14 Aug 2016 17:29:05 +1200 Subject: [Slackbuilds-users] RFC: more variables In-Reply-To: References: <0q93i.703382033b.20160813161507.2c5d0ce0@loli.sombragris.org> Message-ID: It seems like the 14.2 rush has slowed down a little, so I want to take an opportunity to propose a change to the SBo templates. This probably would have better been timed BEFORE 14.2 was released, but it didn't occur to me until I was rebuilding some systems to update everything to 14.2 My idea: We use variables at the head of the SlackBuild scripts for things like program name, version number, arch, and so on. I think it would be nice to also variable-ize these values: Doc path (DOCDIR) Man path (MANDIR) Info path (INFODIR) Benefits: A SlackBuild can be quickly and reliably modified by targeting these variables either through env setting or with sed. Currently the destination of these values is hardcoded in the lower half of a SlackBuild file (when moving docemention, or gzipping man pages). Cost/Drawbacks: None? A rotential drawback is a sense of obligation to change current build scripts to conform to new template, but I'm proposing more a shift in habit than a complete immediate overhaul. What do other people think? Does this sound reasonable, even helpful? Cheers, - Klaatu From slackalaxy at gmail.com Sun Aug 14 09:22:49 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 14 Aug 2016 12:22:49 +0300 Subject: [Slackbuilds-users] RFC: more variables In-Reply-To: References: <0q93i.703382033b.20160813161507.2c5d0ce0@loli.sombragris.org> Message-ID: well, I have seen a DOCS= variable in some SlackBuilds. As for the benefits of introducing the variables you propose -- will this change make the scripts look simpler? I am really asking, not arguing :) I usually just remove the corresponding blocks of text if they are not needed. I do not mind if templates are changed following your idea, but I will not be updating my scripts just for that. -petar 2016-08-14 8:29 GMT+03:00 Klaatu : > It seems like the 14.2 rush has slowed down a little, so I want to take > an opportunity to propose a change to the SBo templates. This probably > would have better been timed BEFORE 14.2 was released, but it didn't > occur to me until I was rebuilding some systems to update everything to 14.2 > > My idea: > > We use variables at the head of the SlackBuild scripts for things like > program name, version number, arch, and so on. I think it would be nice > to also variable-ize these values: > > Doc path (DOCDIR) > Man path (MANDIR) > Info path (INFODIR) > > Benefits: A SlackBuild can be quickly and reliably modified by targeting > these variables either through env setting or with sed. Currently the > destination of these values is hardcoded in the lower half of a > SlackBuild file (when moving docemention, or gzipping man pages). > > Cost/Drawbacks: None? A rotential drawback is a sense of obligation to > change current build scripts to conform to new template, but I'm > proposing more a shift in habit than a complete immediate overhaul. > > What do other people think? Does this sound reasonable, even helpful? > > Cheers, > > - Klaatu > _______________________________________________ > 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 yalhcru at gmail.com Sun Aug 14 10:08:52 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 14 Aug 2016 06:08:52 -0400 Subject: [Slackbuilds-users] RFC: more variables In-Reply-To: References: <0q93i.703382033b.20160813161507.2c5d0ce0@loli.sombragris.org> Message-ID: On 8/14/16, Klaatu wrote: > Doc path (DOCDIR) > Man path (MANDIR) > Info path (INFODIR) Under what conditions do you want docs somewhere besides /usr/doc/$PRGNAM-$VERSION, or man pages outside of /usr/man, or info pages outside of /usr/info? Those are the standard locations... if you're doing nonstandard things, it might make sense to change them, but asking every script maintainer to change every script for something like that is probably too much. Like the previous responder said, I'm not trying to start an argument, I just don't understand why this would be worth doing. From duncan_roe at acslink.net.au Sun Aug 14 13:15:39 2016 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Sun, 14 Aug 2016 23:15:39 +1000 Subject: [Slackbuilds-users] RFC: more variables In-Reply-To: References: <0q93i.703382033b.20160813161507.2c5d0ce0@loli.sombragris.org> Message-ID: <20160814131539.GA2807@dimstar.local.net> On Sun, Aug 14, 2016 at 06:08:52AM -0400, B Watson wrote: > On 8/14/16, Klaatu wrote: > > > Doc path (DOCDIR) > > Man path (MANDIR) > > Info path (INFODIR) > > Under what conditions do you want docs somewhere besides > /usr/doc/$PRGNAM-$VERSION, or man pages outside of /usr/man, or info > pages outside of /usr/info? > > Those are the standard locations... if you're doing nonstandard things, > it might make sense to change them, but asking every script maintainer > to change every script for something like that is probably too much. > > Like the previous responder said, I'm not trying to start an argument, > I just don't understand why this would be worth doing. I think the point being made (with which I agree) is that the scripts would be more easily read if the template advised > DOCDIR=usr/doc/$PKGNAM-$VERSION Then the configure line would read > --docdir=/$DOCDIR and later you would have > mkdir -p $PKG/$DOCDIR > cp whatever $PKG/$DOCDIR (It's usually /usr/doc/$PKGNAM-$VERSION btw (by 749:29 in 14.2 source DVD)) Cheers ... Duncan. From kjhambrick at gmail.com Sun Aug 14 14:23:45 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 14 Aug 2016 09:23:45 -0500 Subject: [Slackbuilds-users] Huge 4.4.x Kernel + SBo hwinfo = Kernel Oops on scsi_tape Message-ID: All -- I am running Slackware64 + Multilib with the Huge 4.4.17 Kernel from Slackware64 Current. I installed libx86emu-1.4 and hwinfo-20.1 from the 14.2 SBo Repository and tried out hwinfo. When hwinfo tries to load the "st" module, I get the attached Kernel Oops. I checked the hwinfo man page and I don't see where I can blacklist or exclude modules from hwinfo but it may be I simply don't understand what I am reading. But IMO, a userland program shouldn't cause a Kernel Oops :) I also tried Kernels Huge 4.4.15 ( from Current ) and Huge 4.4.14 ( from 14.2 ) and I still see the same Oops in /var/log/syslog. I am not sure where to report this and I don't know whether it's a Kernel Bug or a bug in hwinfo or if it's because I am running the huge kernel, but I did find a 'work-around': Don't invoke load_module(hd_data, "st") in src/hd/block.c Attached is a patch for hwinfo.SlackBuild and an ugly patch for src/hd/block.c Maybe Y'All know the REAL cause of the bug ? Thanks for all the good work you're doing for Slackware ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- Aug 14 05:43:35 kjhlt6 kernel: [161792.006542] ------------[ cut here ]------------ Aug 14 05:43:35 kjhlt6 kernel: [161792.006546] WARNING: CPU: 4 PID: 21349 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80() Aug 14 05:43:35 kjhlt6 kernel: [161792.006547] sysfs: cannot create duplicate filename '/class/scsi_tape' Aug 14 05:43:35 kjhlt6 kernel: [161792.006548] Modules linked in: st(+) lp parport_pc sg rfcomm i2c_dev vmnet(O) ppdev parport vmw_vsock_vmci_transport vsock vmw_vmci vmmon(O) xt_nat xt_limit xt_pkttype xt_tcpudp xt_conntrack nf_log_ipv4 nf_log_common xt_LOG iptable_mangle iptable_nat nf_nat_ipv4 iptable_filter appletalk ax25 ipx p8023 p8022 psnap llc ipv6 nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables x_tables cmac bnep fuse snd_hda_codec_realtek snd_hda_codec_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core i915 btusb v4l2_common btrtl videodev joydev mxm_wmi coretemp hwmon intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel snd_hda_codec_hdmi evdev psmouse serio_raw nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) ath10k_pci ath10k_core drm_kms_helper ath drm intel_gtt mac80211 i2c_algo_bit agpgart fb_sys_fops snd_hda_intel syscopyarea sysfillrect Aug 14 05:43:35 kjhlt6 kernel: [161792.006591] CPU: 4 PID: 21349 Comm: modprobe Tainted: P W O 4.4.17 #2 Aug 14 05:43:35 kjhlt6 kernel: [161792.006593] Hardware name: Notebook P7xxDM(-G) /P7xxDM(-G) , BIOS 1.05.03LS1 09/23/2015 Aug 14 05:43:35 kjhlt6 kernel: [161792.006594] 0000000000000000 ffff880f22b67b10 ffffffff8160dda8 ffff880f22b67b58 Aug 14 05:43:35 kjhlt6 kernel: [161792.006596] ffffffff8215771a ffff880f22b67b48 ffffffff8108d6e2 ffff880ad3cea000 Aug 14 05:43:35 kjhlt6 kernel: [161792.006597] ffff88107e5c4e40 ffff8810c6115618 ffffffffc0100000 0000000000000001 Aug 14 05:43:35 kjhlt6 kernel: [161792.006599] Call Trace: Aug 14 05:43:35 kjhlt6 kernel: [161792.006603] [] dump_stack+0x4d/0x65 Aug 14 05:43:35 kjhlt6 kernel: [161792.006606] [] warn_slowpath_common+0x82/0xc0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006608] [] ? 0xffffffffc0100000 Aug 14 05:43:35 kjhlt6 kernel: [161792.006609] [] warn_slowpath_fmt+0x4c/0x50 Aug 14 05:43:35 kjhlt6 kernel: [161792.006611] [] ? kernfs_path+0x48/0x60 Aug 14 05:43:35 kjhlt6 kernel: [161792.006614] [] sysfs_warn_dup+0x62/0x80 Aug 14 05:43:35 kjhlt6 kernel: [161792.006616] [] sysfs_create_dir_ns+0x77/0x90 Aug 14 05:43:35 kjhlt6 kernel: [161792.006619] [] kobject_add_internal+0x9e/0x2d0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006621] [] ? kobject_set_name+0x3e/0x40 Aug 14 05:43:35 kjhlt6 kernel: [161792.006622] [] ? 0xffffffffc0100000 Aug 14 05:43:35 kjhlt6 kernel: [161792.006624] [] kset_register+0x46/0x70 Aug 14 05:43:35 kjhlt6 kernel: [161792.006628] [] __class_register+0xce/0x1f0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006629] [] ? 0xffffffffc0100000 Aug 14 05:43:35 kjhlt6 kernel: [161792.006633] [] init_st+0x84/0xfd [st] Aug 14 05:43:35 kjhlt6 kernel: [161792.006636] [] do_one_initcall+0x99/0x1e0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006639] [] ? free_vmap_area_noflush+0x3d/0x80 Aug 14 05:43:35 kjhlt6 kernel: [161792.006641] [] ? kmem_cache_alloc_trace+0x18b/0x1f0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006645] [] do_init_module+0x5f/0x1c3 Aug 14 05:43:35 kjhlt6 kernel: [161792.006648] [] load_module+0x1c95/0x2270 Aug 14 05:43:35 kjhlt6 kernel: [161792.006650] [] ? __symbol_put+0x50/0x50 Aug 14 05:43:35 kjhlt6 kernel: [161792.006653] [] ? kernel_read+0x41/0x60 Aug 14 05:43:35 kjhlt6 kernel: [161792.006656] [] SYSC_finit_module+0x8f/0xa0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006659] [] SyS_finit_module+0xe/0x10 Aug 14 05:43:35 kjhlt6 kernel: [161792.006661] [] entry_SYSCALL_64_fastpath+0x16/0x6a Aug 14 05:43:35 kjhlt6 kernel: [161792.006663] ---[ end trace c6f0df8827b5a76b ]--- Aug 14 05:43:35 kjhlt6 kernel: [161792.006665] ------------[ cut here ]------------ Aug 14 05:43:35 kjhlt6 kernel: [161792.006668] WARNING: CPU: 4 PID: 21349 at lib/kobject.c:240 kobject_add_internal+0x266/0x2d0() Aug 14 05:43:35 kjhlt6 kernel: [161792.006669] kobject_add_internal failed for scsi_tape with -EEXIST, don't try to register things with the same name in the same directory. Aug 14 05:43:35 kjhlt6 kernel: [161792.006670] Modules linked in: st(+) lp parport_pc sg rfcomm i2c_dev vmnet(O) ppdev parport vmw_vsock_vmci_transport vsock vmw_vmci vmmon(O) xt_nat xt_limit xt_pkttype xt_tcpudp xt_conntrack nf_log_ipv4 nf_log_common xt_LOG iptable_mangle iptable_nat nf_nat_ipv4 iptable_filter appletalk ax25 ipx p8023 p8022 psnap llc ipv6 nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ip_tables x_tables cmac bnep fuse snd_hda_codec_realtek snd_hda_codec_generic uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core i915 btusb v4l2_common btrtl videodev joydev mxm_wmi coretemp hwmon intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel snd_hda_codec_hdmi evdev psmouse serio_raw nvidia_drm(PO) nvidia_modeset(PO) nvidia(PO) ath10k_pci ath10k_core drm_kms_helper ath drm intel_gtt mac80211 i2c_algo_bit agpgart fb_sys_fops snd_hda_intel syscopyarea sysfillrect Aug 14 05:43:35 kjhlt6 kernel: [161792.006720] CPU: 4 PID: 21349 Comm: modprobe Tainted: P W O 4.4.17 #2 Aug 14 05:43:35 kjhlt6 kernel: [161792.006721] Hardware name: Notebook P7xxDM(-G) /P7xxDM(-G) , BIOS 1.05.03LS1 09/23/2015 Aug 14 05:43:35 kjhlt6 kernel: [161792.006722] 0000000000000000 ffff880f22b67b60 ffffffff8160dda8 ffff880f22b67ba8 Aug 14 05:43:35 kjhlt6 kernel: [161792.006724] ffffffff82169d08 ffff880f22b67b98 ffffffff8108d6e2 ffff880f22843c18 Aug 14 05:43:35 kjhlt6 kernel: [161792.006725] 00000000ffffffef ffff8810c6038a38 ffffffffc0100000 0000000000000001 Aug 14 05:43:35 kjhlt6 kernel: [161792.006727] Call Trace: Aug 14 05:43:35 kjhlt6 kernel: [161792.006729] [] dump_stack+0x4d/0x65 Aug 14 05:43:35 kjhlt6 kernel: [161792.006732] [] warn_slowpath_common+0x82/0xc0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006733] [] ? 0xffffffffc0100000 Aug 14 05:43:35 kjhlt6 kernel: [161792.006735] [] warn_slowpath_fmt+0x4c/0x50 Aug 14 05:43:35 kjhlt6 kernel: [161792.006737] [] ? sysfs_warn_dup+0x6a/0x80 Aug 14 05:43:35 kjhlt6 kernel: [161792.006738] [] kobject_add_internal+0x266/0x2d0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006740] [] ? kobject_set_name+0x3e/0x40 Aug 14 05:43:35 kjhlt6 kernel: [161792.006741] [] ? 0xffffffffc0100000 Aug 14 05:43:35 kjhlt6 kernel: [161792.006742] [] kset_register+0x46/0x70 Aug 14 05:43:35 kjhlt6 kernel: [161792.006744] [] __class_register+0xce/0x1f0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006745] [] ? 0xffffffffc0100000 Aug 14 05:43:35 kjhlt6 kernel: [161792.006747] [] init_st+0x84/0xfd [st] Aug 14 05:43:35 kjhlt6 kernel: [161792.006749] [] do_one_initcall+0x99/0x1e0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006751] [] ? free_vmap_area_noflush+0x3d/0x80 Aug 14 05:43:35 kjhlt6 kernel: [161792.006752] [] ? kmem_cache_alloc_trace+0x18b/0x1f0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006754] [] do_init_module+0x5f/0x1c3 Aug 14 05:43:35 kjhlt6 kernel: [161792.006756] [] load_module+0x1c95/0x2270 Aug 14 05:43:35 kjhlt6 kernel: [161792.006757] [] ? __symbol_put+0x50/0x50 Aug 14 05:43:35 kjhlt6 kernel: [161792.006759] [] ? kernel_read+0x41/0x60 Aug 14 05:43:35 kjhlt6 kernel: [161792.006761] [] SYSC_finit_module+0x8f/0xa0 Aug 14 05:43:35 kjhlt6 kernel: [161792.006762] [] SyS_finit_module+0xe/0x10 Aug 14 05:43:35 kjhlt6 kernel: [161792.006764] [] entry_SYSCALL_64_fastpath+0x16/0x6a Aug 14 05:43:35 kjhlt6 kernel: [161792.006765] ---[ end trace c6f0df8827b5a76c ]--- Aug 14 05:43:35 kjhlt6 kernel: [161792.006766] Unable register sysfs class for SCSI tapes -------------- next part -------------- A non-text attachment was scrubbed... Name: block.c-module-st-patch Type: application/octet-stream Size: 420 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: hwinfo.SlackBuild.patch Type: text/x-patch Size: 539 bytes Desc: not available URL: From klaatu at member.fsf.org Sun Aug 14 19:27:12 2016 From: klaatu at member.fsf.org (klaatu at member.fsf.org) Date: Sun, 14 Aug 2016 19:27:12 +0000 Subject: [Slackbuilds-users] RFC: more variables In-Reply-To: (message from B Watson on Sun, 14 Aug 2016 06:08:52 -0400) Message-ID: I do have a specific use-case in mind, as you might expect. In the vfx industry that I work in, my clients modify the path of components to fit in with whatever system layout they've devised. I don't know if this is common or if it's local, but it's the norm where I am. Specifically, some packages only get installed for a specific show, and must be unavailable to some other show (to keep artists from accidentally using an unsupported tool on their show, because when we archive shows, the full environment of what built that show also must be accurately recorded, just in case someone wants to make a sequel 7 years later and needs the old show assets to work). So sometimes I'm installing several packages for someone and must modify where the docs/man/info end up. What I do now is sed 's_usr/doc_/blah/usr/doc_g' (or whatever) once for docs, once for man, and possibly once for info pages. I do this on all packages about to be installed, and then I take note of what failed, and go in and manually tweak the build scripts and re-build the ones that didn't do it right. Not a big deal, but it would be "cleaner" to make the values a variable in the first place so that they can be over-ridden as needed. I also imagine it could be useful for SSD users. Personally, at home, I have /usr/doc on a non-SSD partition, but what if you didn't lay your system out like that and suddenly want to start using /usr/local/doc for all documentation to save wear and tear on your SSD drive? I don't know how common that is either, but maybe it's something that would be helpful to some users. I imagine some admins out there still differentiate between /usr and /usr/local for site-specific installs? I also realise that this is probably exactly how the concept of special build macros gets started, so if everyone hates this idea because it seems like it's starting down the path of confusing, over-abstracted build scripts, I'm happy to continue brute-forcing my build changes when needed. -klaatu -- klaatu at sdf.lonestar.org SDF Public Access UNIX System - http://sdf.lonestar.org From arkadiusz at drabczyk.org Mon Aug 15 00:01:33 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Mon, 15 Aug 2016 02:01:33 +0200 Subject: [Slackbuilds-users] Huge 4.4.x Kernel + SBo hwinfo = Kernel Oops on scsi_tape In-Reply-To: References: Message-ID: <20160815000133.GA24783@comp.a> On Sun, Aug 14, 2016 at 09:23:45AM -0500, Konrad J Hambrick wrote: > All -- > > I am running Slackware64 + Multilib with the Huge 4.4.17 Kernel from > Slackware64 Current. > > I installed libx86emu-1.4 and hwinfo-20.1 from the 14.2 SBo Repository and > tried out hwinfo. > > When hwinfo tries to load the "st" module, I get the attached Kernel Oops. > > I checked the hwinfo man page and I don't see where I can blacklist or exclude > modules from hwinfo but it may be I simply don't understand what I am reading. > > But IMO, a userland program shouldn't cause a Kernel Oops :) > > I also tried Kernels Huge 4.4.15 ( from Current ) and Huge 4.4.14 ( from 14.2 ) > and I still see the same Oops in /var/log/syslog. > > I am not sure where to report this and I don't know whether it's a Kernel Bug > or a bug in hwinfo or if it's because I am running the huge kernel, but I did > find a 'work-around':? Don't invoke load_module(hd_data, "st") in src/hd/ > block.c > > Attached is a patch for hwinfo.SlackBuild and an ugly patch for src/hd/block.c > > Maybe Y'All know the REAL cause of the bug ? > > Thanks for all the good work you're doing for Slackware ! (I also sent this message via gmane.org a couple of hours ago but it didn't make it to the list so I'm sending again directly to the list) I don't think it's a bug. I think that as you use `huge' kernel the module that hwinfo is trying to load is already statically built into the kernel, this is why you get this: sysfs: cannot create duplicate filename '/class/scsi_tape'sysfs: cannot create duplicate filename '/class/scsi_tape' Do you already have /sys/class/scsi_tape right after booting? See a similar problem here: https://www.linuxquestions.org/questions/slackware-14/please-explain-kobject_add-failed-578488/ -- Arkadiusz Drabczyk From atelszewski at gmail.com Mon Aug 15 01:15:11 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 15 Aug 2016 03:15:11 +0200 Subject: [Slackbuilds-users] Huge 4.4.x Kernel + SBo hwinfo = Kernel Oops on scsi_tape In-Reply-To: <20160815000133.GA24783@comp.a> References: <20160815000133.GA24783@comp.a> Message-ID: On 15/08/16 02:01, Arkadiusz Drabczyk wrote: > On Sun, Aug 14, 2016 at 09:23:45AM -0500, Konrad J Hambrick wrote: >> All -- >> >> I am running Slackware64 + Multilib with the Huge 4.4.17 Kernel from >> Slackware64 Current. >> >> I installed libx86emu-1.4 and hwinfo-20.1 from the 14.2 SBo Repository and >> tried out hwinfo. >> >> When hwinfo tries to load the "st" module, I get the attached Kernel Oops. >> >> I checked the hwinfo man page and I don't see where I can blacklist or exclude >> modules from hwinfo but it may be I simply don't understand what I am reading. >> >> But IMO, a userland program shouldn't cause a Kernel Oops :) >> >> I also tried Kernels Huge 4.4.15 ( from Current ) and Huge 4.4.14 ( from 14.2 ) >> and I still see the same Oops in /var/log/syslog. >> >> I am not sure where to report this and I don't know whether it's a Kernel Bug >> or a bug in hwinfo or if it's because I am running the huge kernel, but I did >> find a 'work-around': Don't invoke load_module(hd_data, "st") in src/hd/ >> block.c >> >> Attached is a patch for hwinfo.SlackBuild and an ugly patch for src/hd/block.c >> >> Maybe Y'All know the REAL cause of the bug ? >> >> Thanks for all the good work you're doing for Slackware ! > > (I also sent this message via gmane.org a couple of hours ago but it > didn't make it to the list so I'm sending again directly to the list) > > I don't think it's a bug. I think that as you use `huge' kernel the > module that hwinfo is trying to load is already statically built into > the kernel, this is why you get this: > > sysfs: cannot create duplicate filename '/class/scsi_tape'sysfs: cannot create duplicate filename '/class/scsi_tape' > > Do you already have /sys/class/scsi_tape right after booting? > > See a similar problem here: > https://www.linuxquestions.org/questions/slackware-14/please-explain-kobject_add-failed-578488/ > Arkadiusz is correct on that. It's kinda Slackware bug. Try running: $ dmesg --follow and then: $ modprobe st and you'll notice the OOPS appearing when you try to load "st" module. It happens with huge kernel, but not with generic one (I'm too running 4.4.17 from -current on 14.2). Recently there was a conversation about the problem on LQ, starting here: http://www.linuxquestions.org/questions/slackware-14/requests-for-current-20151216-a-4175561577-post5584757/ -- Best regards, Andrzej Telszewski From dpross1100 at msn.com Mon Aug 15 03:30:50 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Mon, 15 Aug 2016 03:30:50 +0000 Subject: [Slackbuilds-users] Lumina xinitrc Message-ID: Hi, I believe that the xinitrc file for lumina needs to be changed as in the attached patch. There is no Lumina-DE executable, so attempting to run startx with xwmconfig set to lumina fails. The correct name is start-lumina-desktop, and startx works after making that change. Dan -------------- next part -------------- A non-text attachment was scrubbed... Name: xinitrc.lumina.patch Type: text/x-patch Size: 390 bytes Desc: xinitrc.lumina.patch URL: From kjhambrick at gmail.com Mon Aug 15 09:09:43 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 15 Aug 2016 04:09:43 -0500 Subject: [Slackbuilds-users] Huge 4.4.x Kernel + SBo hwinfo = Kernel Oops on scsi_tape In-Reply-To: <20160815000133.GA24783@comp.a> References: <20160815000133.GA24783@comp.a> Message-ID: Thank you Arkadiusz Drabczyk Yes, /sys/class/scsi_tape exists immediately after boot and the huge kernels I tested do compile-in the "st" module code while the generic kernels make a module. These are the Kernel Configs for generic and huge 4.4.17 Kernels. > > > *# grep CONFIG_CHR_DEV_ST= > /boot/config-*-4.4.17/boot/config-generic-4.4.17:CONFIG_CHR_DEV_ST=m/boot/config-huge-4.4.17:CONFIG_CHR_DEV_ST=y* > I believe there is something odd going on in the st.c Kernel code though because in hwinfo src/hd/block.c starting at line 57 void function hd_scan_sysfs_block( ) invokes /sbin/modprobe on several other modules that are compiled into the huge kernels. This is the code in block.c that causes the Bug Dump: > > > > > > > > > > * if(hd_probe_feature(hd_data, pr_block_mods)) { PROGRESS(1, 0, "block > modules"); // load_module(hd_data, "ide-cd"); load_module(hd_data, > "ide-cd_mod"); load_module(hd_data, "ide-disk"); load_module(hd_data, > "sr_mod"); load_module(hd_data, "sd_mod");#if !defined(__s390__) && > !defined(__s390x__) load_module(hd_data, "st");#endif }* > Only the call to load_module( hd_data, "st" ) module throws the Bug text into /var/log/syslog There is another int function called int load_module_with_params( ) which takes a parameter list for the command ( in this case /sbin/modprobe ). I was going to try this: 1. blacklist the "st" module in /etc/modprobe.d/ 2. change *load_module(hd_data, "st"); *to *load_module_with_params(hd_data, "st", "-b"); // block.c ; line 65* According to what I see in the source code, this should pass the -b flag to /sbin/modprobe which should in turn eliminate the Bug Dump. Anyhow, not a big deal ( I hope ) it's simply odd that the "st" module causes the syslog entries where others don't. And given Pat's recent remark about eliminating the huge Kernels it is likely to be OBE. Thanks again. -- kjh On Sun, Aug 14, 2016 at 7:01 PM, Arkadiusz Drabczyk wrote: > On Sun, Aug 14, 2016 at 09:23:45AM -0500, Konrad J Hambrick wrote: > > All -- > > > > I am running Slackware64 + Multilib with the Huge 4.4.17 Kernel from > > Slackware64 Current. > > > > I installed libx86emu-1.4 and hwinfo-20.1 from the 14.2 SBo Repository > and > > tried out hwinfo. > > > > When hwinfo tries to load the "st" module, I get the attached Kernel > Oops. > > > > I checked the hwinfo man page and I don't see where I can blacklist or > exclude > > modules from hwinfo but it may be I simply don't understand what I am > reading. > > > > But IMO, a userland program shouldn't cause a Kernel Oops :) > > > > I also tried Kernels Huge 4.4.15 ( from Current ) and Huge 4.4.14 ( from > 14.2 ) > > and I still see the same Oops in /var/log/syslog. > > > > I am not sure where to report this and I don't know whether it's a > Kernel Bug > > or a bug in hwinfo or if it's because I am running the huge kernel, but > I did > > find a 'work-around': Don't invoke load_module(hd_data, "st") in src/hd/ > > block.c > > > > Attached is a patch for hwinfo.SlackBuild and an ugly patch for > src/hd/block.c > > > > Maybe Y'All know the REAL cause of the bug ? > > > > Thanks for all the good work you're doing for Slackware ! > > (I also sent this message via gmane.org a couple of hours ago but it > didn't make it to the list so I'm sending again directly to the list) > > I don't think it's a bug. I think that as you use `huge' kernel the > module that hwinfo is trying to load is already statically built into > the kernel, this is why you get this: > > sysfs: cannot create duplicate filename '/class/scsi_tape'sysfs: cannot > create duplicate filename '/class/scsi_tape' > > Do you already have /sys/class/scsi_tape right after booting? > > See a similar problem here: > https://www.linuxquestions.org/questions/slackware-14/ > please-explain-kobject_add-failed-578488/ > > -- > Arkadiusz Drabczyk > _______________________________________________ > 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 kjhambrick at gmail.com Mon Aug 15 09:20:22 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 15 Aug 2016 04:20:22 -0500 Subject: [Slackbuilds-users] Huge 4.4.x Kernel + SBo hwinfo = Kernel Oops on scsi_tape In-Reply-To: References: <20160815000133.GA24783@comp.a> Message-ID: Thanks for the reply Andrzej Telszewski See my reply to Arkadiusz Drabczyk, especially the part about blacklisting the "st" module in /etc/modprobe.d and changing the call in hwinfo. What I am considering does work from the command line ( man modprobe and look for the -b flag ). I created a file: /etc/modprobe.d/disable_scsi_tape.conf with a single line: blacklist st > If I simply run: `/sbin/modprobe st` I get the Bug dump in /var/log/syslog ( and dmesg ). On the other hand, after installing /etc/modprobe.d/disable_scsi_tape.conf if I run `/sbin/modprobe -b st` there is no output. I believe the change to block.c that I suggested in my other reply will 'fix' hwinfo However, since none of the other compiled-in modules in the Huge Kernel result in a Bug Dump, I now believe this is a bug in the st.c kernel code. Thanks again ! -- kjh On Sun, Aug 14, 2016 at 8:15 PM, Andrzej Telszewski wrote: > On 15/08/16 02:01, Arkadiusz Drabczyk wrote: > >> On Sun, Aug 14, 2016 at 09:23:45AM -0500, Konrad J Hambrick wrote: >> >>> All -- >>> >>> I am running Slackware64 + Multilib with the Huge 4.4.17 Kernel from >>> Slackware64 Current. >>> >>> I installed libx86emu-1.4 and hwinfo-20.1 from the 14.2 SBo Repository >>> and >>> tried out hwinfo. >>> >>> When hwinfo tries to load the "st" module, I get the attached Kernel >>> Oops. >>> >>> I checked the hwinfo man page and I don't see where I can blacklist or >>> exclude >>> modules from hwinfo but it may be I simply don't understand what I am >>> reading. >>> >>> But IMO, a userland program shouldn't cause a Kernel Oops :) >>> >>> I also tried Kernels Huge 4.4.15 ( from Current ) and Huge 4.4.14 ( from >>> 14.2 ) >>> and I still see the same Oops in /var/log/syslog. >>> >>> I am not sure where to report this and I don't know whether it's a >>> Kernel Bug >>> or a bug in hwinfo or if it's because I am running the huge kernel, but >>> I did >>> find a 'work-around': Don't invoke load_module(hd_data, "st") in src/hd/ >>> block.c >>> >>> Attached is a patch for hwinfo.SlackBuild and an ugly patch for >>> src/hd/block.c >>> >>> Maybe Y'All know the REAL cause of the bug ? >>> >>> Thanks for all the good work you're doing for Slackware ! >>> >> >> (I also sent this message via gmane.org a couple of hours ago but it >> didn't make it to the list so I'm sending again directly to the list) >> >> I don't think it's a bug. I think that as you use `huge' kernel the >> module that hwinfo is trying to load is already statically built into >> the kernel, this is why you get this: >> >> sysfs: cannot create duplicate filename '/class/scsi_tape'sysfs: cannot >> create duplicate filename '/class/scsi_tape' >> >> Do you already have /sys/class/scsi_tape right after booting? >> >> See a similar problem here: >> https://www.linuxquestions.org/questions/slackware-14/please >> -explain-kobject_add-failed-578488/ >> >> > Arkadiusz is correct on that. > It's kinda Slackware bug. > > Try running: > $ dmesg --follow > > and then: > $ modprobe st > > and you'll notice the OOPS appearing when you try to load "st" module. > > It happens with huge kernel, but not with generic one (I'm too running > 4.4.17 from -current on 14.2). > > Recently there was a conversation about the problem on LQ, starting here: > http://www.linuxquestions.org/questions/slackware-14/request > s-for-current-20151216-a-4175561577-post5584757/ > > -- > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kjhambrick at gmail.com Mon Aug 15 09:53:09 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 15 Aug 2016 04:53:09 -0500 Subject: [Slackbuilds-users] Huge 4.4.x Kernel + SBo hwinfo = Kernel Oops on scsi_tape In-Reply-To: References: <20160815000133.GA24783@comp.a> Message-ID: All -- I applied the two attached patch files to hwinfo. After installing the attached blacklist st file to /etc/modprobe.d, I no longer get the Kernel Bug Dump in Syslog when I run hwinfo with the huge Kernel. Nor do I get the Kernel Bug Dump if I invoke `modprobe -b st` as root from the commandline ( although the Bug Dump is there without -b ). Thanks for making me look :) -- kjh On Mon, Aug 15, 2016 at 4:20 AM, Konrad J Hambrick wrote: > > Thanks for the reply Andrzej Telszewski > > See my reply to Arkadiusz Drabczyk, especially the part about blacklisting > the "st" module in /etc/modprobe.d and changing the call in hwinfo. > > What I am considering does work from the command line ( man modprobe and > look for the -b flag ). > > I created a file: /etc/modprobe.d/disable_scsi_tape.conf with a single > line: > > blacklist st >> > > If I simply run: `/sbin/modprobe st` I get the Bug dump in > /var/log/syslog ( and dmesg ). > > On the other hand, after installing /etc/modprobe.d/disable_scsi_tape.conf > if I run `/sbin/modprobe -b st` there is no output. > > I believe the change to block.c that I suggested in my other reply will > 'fix' hwinfo > > However, since none of the other compiled-in modules in the Huge Kernel > result in a Bug Dump, I now believe this is a bug in the st.c kernel code. > > Thanks again ! > > -- kjh > > On Sun, Aug 14, 2016 at 8:15 PM, Andrzej Telszewski > wrote: > >> On 15/08/16 02:01, Arkadiusz Drabczyk wrote: >> >>> On Sun, Aug 14, 2016 at 09:23:45AM -0500, Konrad J Hambrick wrote: >>> >>>> All -- >>>> >>>> I am running Slackware64 + Multilib with the Huge 4.4.17 Kernel from >>>> Slackware64 Current. >>>> >>>> I installed libx86emu-1.4 and hwinfo-20.1 from the 14.2 SBo Repository >>>> and >>>> tried out hwinfo. >>>> >>>> When hwinfo tries to load the "st" module, I get the attached Kernel >>>> Oops. >>>> >>>> I checked the hwinfo man page and I don't see where I can blacklist or >>>> exclude >>>> modules from hwinfo but it may be I simply don't understand what I am >>>> reading. >>>> >>>> But IMO, a userland program shouldn't cause a Kernel Oops :) >>>> >>>> I also tried Kernels Huge 4.4.15 ( from Current ) and Huge 4.4.14 ( >>>> from 14.2 ) >>>> and I still see the same Oops in /var/log/syslog. >>>> >>>> I am not sure where to report this and I don't know whether it's a >>>> Kernel Bug >>>> or a bug in hwinfo or if it's because I am running the huge kernel, but >>>> I did >>>> find a 'work-around': Don't invoke load_module(hd_data, "st") in >>>> src/hd/ >>>> block.c >>>> >>>> Attached is a patch for hwinfo.SlackBuild and an ugly patch for >>>> src/hd/block.c >>>> >>>> Maybe Y'All know the REAL cause of the bug ? >>>> >>>> Thanks for all the good work you're doing for Slackware ! >>>> >>> >>> (I also sent this message via gmane.org a couple of hours ago but it >>> didn't make it to the list so I'm sending again directly to the list) >>> >>> I don't think it's a bug. I think that as you use `huge' kernel the >>> module that hwinfo is trying to load is already statically built into >>> the kernel, this is why you get this: >>> >>> sysfs: cannot create duplicate filename '/class/scsi_tape'sysfs: cannot >>> create duplicate filename '/class/scsi_tape' >>> >>> Do you already have /sys/class/scsi_tape right after booting? >>> >>> See a similar problem here: >>> https://www.linuxquestions.org/questions/slackware-14/please >>> -explain-kobject_add-failed-578488/ >>> >>> >> Arkadiusz is correct on that. >> It's kinda Slackware bug. >> >> Try running: >> $ dmesg --follow >> >> and then: >> $ modprobe st >> >> and you'll notice the OOPS appearing when you try to load "st" module. >> >> It happens with huge kernel, but not with generic one (I'm too running >> 4.4.17 from -current on 14.2). >> >> Recently there was a conversation about the problem on LQ, starting here: >> http://www.linuxquestions.org/questions/slackware-14/request >> s-for-current-20151216-a-4175561577-post5584757/ >> >> -- >> 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/ >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- --- hwinfo.SlackBuild-orig 2016-08-14 09:12:54.748261147 -0500 +++ hwinfo.SlackBuild 2016-08-15 04:32:12.318857525 -0500 @@ -25,7 +25,7 @@ PRGNAM=hwinfo VERSION=20.1 BUILD=${BUILD:-1} -TAG=${TAG:-_SBo} +TAG=${TAG:-_fix_st_SBo} if [ -z "$ARCH" ]; then case "$( uname -m )" in @@ -71,6 +71,10 @@ # disable regeneration of changelog and VERSION chmod -x ./git2log +# +# kjh patched-out load_module(hd_data, "st") +# +patch -p1 < ${CWD}/src-block.c-patch-for-st-bug.txt # use our CFLAGS sed -i "s/?= -O2/?= $SLKCFLAGS/" Makefile.common -------------- next part -------------- --- ./src/hd/block.c-orig 2016-08-15 04:28:34.422836861 -0500 +++ ./src/hd/block.c 2016-08-15 04:28:20.349835527 -0500 @@ -62,7 +62,7 @@ load_module(hd_data, "sr_mod"); load_module(hd_data, "sd_mod"); #if !defined(__s390__) && !defined(__s390x__) - load_module(hd_data, "st"); + load_module_with_params(hd_data, "st", "-b"); #endif } -------------- next part -------------- # kjh added the following for hwinfo to eliminate a Kernel Bug Dump # in /var/log/syslog / dmesg # # The st module is compiled into the huge kernel but if you # modprobe st when /sys/class/scsi_tape/ already exists, you'll # get a Kernel Bug Dump. # # This is definitely a kludge # # save this file as /etc/modprobe.d/disable_scsi_tape.conf # blacklist st From ryan.q at linux.com Mon Aug 15 20:17:34 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 15 Aug 2016 13:17:34 -0700 Subject: [Slackbuilds-users] Lumina xinitrc In-Reply-To: References: Message-ID: On Aug 14, 2016 8:30 PM, "Daniel Prosser" wrote: > > Hi, > > I believe that the xinitrc file for lumina needs to be changed as in the > attached patch. There is no Lumina-DE executable, so attempting to run startx > with xwmconfig set to lumina fails. The correct name is start-lumina-desktop, > and startx works after making that change. > > Dan Thanks! I will update the build. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Aug 15 23:57:14 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 16 Aug 2016 06:57:14 +0700 Subject: [Slackbuilds-users] Fwd: No Longer A Maintainer In-Reply-To: References: Message-ID: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> One of our maintainer just send me an email that he will not be maintaining his packages anymore. feel free to submit a take over submission over his packages. For your information, these are packages that Gethyn maintain: multimedia/obs-studio audio/xmms-ctl audio/wmusic games/qstat games/wmquake games/jackhammer games/ut2004 games/chocolate_duke3D games/qzdl desktop/wmxss desktop/wmwebcam desktop/wmudmount desktop/wmtimer desktop/wmweather+ desktop/Window_Manager_Scripts desktop/mimi desktop/wmblob graphics/gimp-plugin-bimp academic/wmcalc development/tyrutils-ericw development/vispatch system/wine-staging system/wmgtemp accessibility/Synkron network/purple-facebook network/gui-ufw network/pidgin-skypeweb network/uTox network/wmnd -------- Forwarded Message -------- Subject: No Longer A Maintainer Date: Mon, 15 Aug 2016 16:25:50 -0700 From: Gethyn ThomasQuail To: Willy Sudiarto Raharjo Hello, I am not going to be maintaining my SlackBuilds on SBo. I am sorry for any inconveniences this might cause, but anyone is free to pick up and contiune where I left off. Best of luck, -Gethyn -- 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 yalhcru at gmail.com Tue Aug 16 01:05:51 2016 From: yalhcru at gmail.com (B Watson) Date: Mon, 15 Aug 2016 21:05:51 -0400 Subject: [Slackbuilds-users] Fwd: No Longer A Maintainer In-Reply-To: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> References: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> Message-ID: On 8/15/16, Willy Sudiarto Raharjo wrote: > audio/wmusic > games/wmquake > desktop/wmxss > desktop/wmwebcam > desktop/wmudmount > desktop/wmtimer > desktop/wmweather+ > desktop/wmblob > academic/wmcalc > system/wmgtemp > network/wmnd I'll take these, unless someone has a burning desire to take them. They're WindowMaker dockapps, and I use WindowMaker as my "desktop". > games/chocolate_duke3D I already maintain eduke32, don't mind taking another Duke Nukem 3D game (gives me an excuse to play it more!) > games/ut2004 I'd prefer someone else take ut2004, but if nobody else wants it, I'll take it rather than see it disappear from the repo. From chris.willing at iinet.net.au Tue Aug 16 01:19:48 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 16 Aug 2016 11:19:48 +1000 Subject: [Slackbuilds-users] Fwd: No Longer A Maintainer In-Reply-To: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> References: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> Message-ID: <4bf8a12e-7d3c-3421-f2d1-96ffdc269155@iinet.net.au> On 16/08/16 09:57, Willy Sudiarto Raharjo wrote: > One of our maintainer just send me an email that he will not be > maintaining his packages anymore. feel free to submit a take over > submission over his packages. For your information, these are packages > that Gethyn maintain: > > multimedia/obs-studio > I'll take obs-studio unless someone else has strong desire for it. chris From bch at shroggslodge.freeserve.co.uk Tue Aug 16 08:57:03 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Tue, 16 Aug 2016 09:57:03 +0100 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: <56577217.u9CO2rfqRP@ithil> Message-ID: Good morning Having got latest Icecat building with the -Os switch, it seems there are some reports of [serious?] security issues with it. Here is where I first read something: https://lists.gnu.org/archive/html/bug-gnuzilla/2016-08/msg00000.html And I have seen further discussion and consternation about what to do with Icecat and perhaps not using Firefox as base etc. I'm really relatively only a 'user' so to speak, so I'm interested to know what others feel....is there a serious security risk ? I realise this is SBo and not an Icecat forum, but I wonder what the contributors (and maintainer) on SBo feel about the reports being made; should it affect whether Icecat is on SBo if its known to be 'risky', or does it not matter, should comments be made [in the info] or is it up to anyone wanting to use it to be self-aware and generally any other comments to share. If this list really is inappropriate for posts like this (whatever 'this' is), then just let me know.....but I would be interested in what more knowledgeable people on SBo feel ? Thank you and good day to all. Habs On 8 August 2016 at 23:16, wrote: > hi there all > > I have tried the -Os switch and it does appear to remedy the problem. > Icecat no longer crashes in the scenario(s) I have documented. > > I wonder what the -O2 switch does differently to the -Os one. > > So for now that does appear to be the 'fix'. Thank you all. > > > Habs > > > On 8 August 2016 at 20:36, Ryan P.C. McQuen wrote: > >> >> >> On Monday, August 8, 2016, Ivan Zaigralin wrote: >> >>> I still can't replicate any crash whatsoever, even in places where others >>> report them. However, Matt tells me that crashes went away after he >>> rebuilt >>> with -Os. He also mentioned he's got an AMD Phenom, whereas I am using >>> Intel >>> CPU, which may explain why I am unable to hit this snag. >>> >>> I can certainly submit a fixed SlackBuild if there's a consensus -Os is >>> an >>> effective fix. Please let me know :) >>> >> >> Seems like that would be valid, since Slackware's own Firefox build was >> passing that for version 43, and only removed it for versions past 43: >> >> (Changelog reference): >> >> Wed Dec 23 22:44:58 UTC 2015 >> a/lvm2-2.02.138-i586-1.txz: Upgraded. >> ap/ghostscript-9.18-i586-1.txz: Upgraded. >> ap/lsof-4.89-i586-1.txz: Upgraded. >> l/pycups-1.9.73-i586-1.txz: Upgraded. >> l/pycurl-7.19.5.3-i586-1.txz: Upgraded. >> n/NetworkManager-1.0.10-i586-1.txz: Upgraded. >> n/curl-7.46.0-i586-1.txz: Upgraded. >> n/links-2.12-i586-1.txz: Upgraded. >> n/obexfs-0.12-i486-1.txz: Removed. >> This functionality is now included in the obexftp package. >> n/obexftp-0.24-i586-1.txz: Upgraded. >> Thanks to Robby Workman. >> n/openobex-1.7.1-i586-1.txz: Upgraded. >> Thanks to Robby Workman. >> n/rsync-3.1.2-i586-1.txz: Upgraded. >> x/libXi-1.7.6-i586-1.txz: Upgraded. >> x/pixman-0.33.6-i586-1.txz: Upgraded. >> x/xorg-cf-files-1.0.6-noarch-1.txz: Upgraded. >> xap/mozilla-firefox-43.0.2-i586-2.txz: Rebuilt. >> Compile with -Os instead of -O2 to work around crash issues. >> Recent betas are working fine with -O2, so we'll probably be >> able to switch back to that again soon. Thanks to j_v. >> >> >> -- >> -Ryan >> [ryanpcmcquen.org] >> >> >> _______________________________________________ >> 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 chris.willing at iinet.net.au Tue Aug 16 11:34:42 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 16 Aug 2016 21:34:42 +1000 Subject: [Slackbuilds-users] Fwd: No Longer A Maintainer In-Reply-To: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> References: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> Message-ID: <97460e30-8b96-af18-b90c-b4c5dd89febc@iinet.net.au> On 16/08/16 09:57, Willy Sudiarto Raharjo wrote: > One of our maintainer just send me an email that he will not be > maintaining his packages anymore. feel free to submit a take over > submission over his packages. For your information, these are packages > that Gethyn maintain: > > network/uTox I'll take this one too. chris From melikamp at melikamp.com Tue Aug 16 18:05:28 2016 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Tue, 16 Aug 2016 11:05:28 -0700 Subject: [Slackbuilds-users] icecat 38.8.0 crashes In-Reply-To: References: Message-ID: <1786691.mHFlXvMcxy@ithil> Personally, I am somewhat unhappy about the gnuzilla update/security policy. The move to forties apparently is not happening because it breaks saved cookie preferences or something, but I have to question the wisdom of withholding fixes for remote code execution because of that. Having said that, I think we need to take a few factors into consideration. First of all, it's not gnuzilla's fault firefox is so insequre, it's mozilla's fault. This browser has like a million holes in it, and may be the most updated package in Slackware. Lagging a few releases behind sucks, especially when the bugs are made public, but at the same time it looks like every firefox release in the last few years had terrible security holes in it, so I don't really feel that much safer using the latest version, and neither should you. If security is very important to a user, it may be prudent to switch browsers. Also, gnuzilla has a mission and a goal, and mozilla is not making it easy. They keep putting more and more ugly stuff into firefox and changing the security policy, like with the cookies above, while gnuzilla team is committed to releasing a product which meets their rather high standards. As a volunteer effort, they've done great, and it would be completely unfair to chastise them for lagging behind mozilla, since gnizilla are not the ones breaking it it every release cycle. Finally, I believe there is a niche opening up for a firefox-based browser which is libre and meets free software distrubution guidelines like icecat, but has no extra privacy features, and passes all the mozilla pearls onto the users. Such minimal deblobbing could be potentially more robust: that is, new releases could be churned out as quickly and reliably as linux-libre. Looking at Parabola's thunderbird & seamonkey builds, I imagine something like that could be done for firefox as well. Anyone can step in and claim the glory for this one :) I don't have time to write a slackbuild like that and run it by FSF, but if anyone did it, I think I would actually switch. On Tuesday, August 16, 2016 09:57:03 bch at shroggslodge.freeserve.co.uk wrote: > Good morning > > Having got latest Icecat building with the -Os switch, it seems there are > some reports of [serious?] security issues with it. > > Here is where I first read something: > https://lists.gnu.org/archive/html/bug-gnuzilla/2016-08/msg00000.html > > And I have seen further discussion and consternation about what to do with > Icecat and perhaps not using Firefox as base etc. I'm really relatively > only a 'user' so to speak, so I'm interested to know what others feel....is > there a serious security risk ? > > I realise this is SBo and not an Icecat forum, but I wonder what the > contributors (and maintainer) on SBo feel about the reports being made; > should it affect whether Icecat is on SBo if its known to be 'risky', or > does it not matter, should comments be made [in the info] or is it up to > anyone wanting to use it to be self-aware and generally any other comments > to share. > > If this list really is inappropriate for posts like this (whatever 'this' > is), then just let me know.....but I would be interested in what more > knowledgeable people on SBo feel ? > > > Thank you and good day to all. > Habs > > On 8 August 2016 at 23:16, wrote: > > hi there all > > > > I have tried the -Os switch and it does appear to remedy the problem. > > Icecat no longer crashes in the scenario(s) I have documented. > > > > I wonder what the -O2 switch does differently to the -Os one. > > > > So for now that does appear to be the 'fix'. Thank you all. > > > > > > Habs > > > > On 8 August 2016 at 20:36, Ryan P.C. McQuen wrote: > >> On Monday, August 8, 2016, Ivan Zaigralin wrote: > >>> I still can't replicate any crash whatsoever, even in places where > >>> others > >>> report them. However, Matt tells me that crashes went away after he > >>> rebuilt > >>> with -Os. He also mentioned he's got an AMD Phenom, whereas I am using > >>> Intel > >>> CPU, which may explain why I am unable to hit this snag. > >>> > >>> I can certainly submit a fixed SlackBuild if there's a consensus -Os is > >>> an > >>> effective fix. Please let me know :) > >> > >> Seems like that would be valid, since Slackware's own Firefox build was > >> passing that for version 43, and only removed it for versions past 43: > >> > >> (Changelog reference): > >> > >> Wed Dec 23 22:44:58 UTC 2015 > >> a/lvm2-2.02.138-i586-1.txz: Upgraded. > >> ap/ghostscript-9.18-i586-1.txz: Upgraded. > >> ap/lsof-4.89-i586-1.txz: Upgraded. > >> l/pycups-1.9.73-i586-1.txz: Upgraded. > >> l/pycurl-7.19.5.3-i586-1.txz: Upgraded. > >> n/NetworkManager-1.0.10-i586-1.txz: Upgraded. > >> n/curl-7.46.0-i586-1.txz: Upgraded. > >> n/links-2.12-i586-1.txz: Upgraded. > >> n/obexfs-0.12-i486-1.txz: Removed. > >> > >> This functionality is now included in the obexftp package. > >> > >> n/obexftp-0.24-i586-1.txz: Upgraded. > >> > >> Thanks to Robby Workman. > >> > >> n/openobex-1.7.1-i586-1.txz: Upgraded. > >> > >> Thanks to Robby Workman. > >> > >> n/rsync-3.1.2-i586-1.txz: Upgraded. > >> x/libXi-1.7.6-i586-1.txz: Upgraded. > >> x/pixman-0.33.6-i586-1.txz: Upgraded. > >> x/xorg-cf-files-1.0.6-noarch-1.txz: Upgraded. > >> xap/mozilla-firefox-43.0.2-i586-2.txz: Rebuilt. > >> > >> Compile with -Os instead of -O2 to work around crash issues. > >> Recent betas are working fine with -O2, so we'll probably be > >> able to switch back to that again soon. Thanks to j_v. > >> > >> -- > >> -Ryan > >> [ryanpcmcquen.org] > >> > >> > >> _______________________________________________ > >> 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 bch at shroggslodge.freeserve.co.uk Tue Aug 16 18:51:08 2016 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Tue, 16 Aug 2016 19:51:08 +0100 Subject: [Slackbuilds-users] [Bug-gnuzilla] icecat 38.8.0 crashes In-Reply-To: <1786691.mHFlXvMcxy@ithil> References: <1786691.mHFlXvMcxy@ithil> Message-ID: Thank you for sharing your views Ivan. I just want to make clear as perhaps my previous post may have given a wrong impression. It was not my intention for what I said to be taken as criticism of Gnuzilla in any way. Peoples' efforts on projects such as Gnuzilla, SBo work and all similar I find truly amazing. I must admit I am not clear why Mozilla would not want the same as Gnuzilla and why that project would conflict with Gnuzilla ideas. Mind you, the complexities of the human condition are huge :-) Perhaps it is safe to say that it is better to just wait and see how it all pans out and what emerges. Thank you again. Peace and good will to all. Habs On 16 August 2016 at 19:05, Ivan Zaigralin wrote: > Personally, I am somewhat unhappy about the gnuzilla update/security > policy. > The move to forties apparently is not happening because it breaks saved > cookie > preferences or something, but I have to question the wisdom of withholding > fixes for remote code execution because of that. > > Having said that, I think we need to take a few factors into consideration. > First of all, it's not gnuzilla's fault firefox is so insequre, it's > mozilla's > fault. This browser has like a million holes in it, and may be the most > updated package in Slackware. Lagging a few releases behind sucks, > especially > when the bugs are made public, but at the same time it looks like every > firefox release in the last few years had terrible security holes in it, > so I > don't really feel that much safer using the latest version, and neither > should > you. If security is very important to a user, it may be prudent to switch > browsers. > > Also, gnuzilla has a mission and a goal, and mozilla is not making it easy. > They keep putting more and more ugly stuff into firefox and changing the > security policy, like with the cookies above, while gnuzilla team is > committed > to releasing a product which meets their rather high standards. As a > volunteer > effort, they've done great, and it would be completely unfair to chastise > them > for lagging behind mozilla, since gnizilla are not the ones breaking it it > every release cycle. > > Finally, I believe there is a niche opening up for a firefox-based browser > which is libre and meets free software distrubution guidelines like icecat, > but has no extra privacy features, and passes all the mozilla pearls onto > the > users. Such minimal deblobbing could be potentially more robust: that is, > new > releases could be churned out as quickly and reliably as linux-libre. > Looking > at Parabola's thunderbird & seamonkey builds, I imagine something like that > could be done for firefox as well. Anyone can step in and claim the glory > for > this one :) I don't have time to write a slackbuild like that and run it by > FSF, but if anyone did it, I think I would actually switch. > > On Tuesday, August 16, 2016 09:57:03 bch at shroggslodge.freeserve.co.uk > wrote: > > Good morning > > > > Having got latest Icecat building with the -Os switch, it seems there are > > some reports of [serious?] security issues with it. > > > > Here is where I first read something: > > https://lists.gnu.org/archive/html/bug-gnuzilla/2016-08/msg00000.html > > > > And I have seen further discussion and consternation about what to do > with > > Icecat and perhaps not using Firefox as base etc. I'm really relatively > > only a 'user' so to speak, so I'm interested to know what others > feel....is > > there a serious security risk ? > > > > I realise this is SBo and not an Icecat forum, but I wonder what the > > contributors (and maintainer) on SBo feel about the reports being made; > > should it affect whether Icecat is on SBo if its known to be 'risky', or > > does it not matter, should comments be made [in the info] or is it up to > > anyone wanting to use it to be self-aware and generally any other > comments > > to share. > > > > If this list really is inappropriate for posts like this (whatever 'this' > > is), then just let me know.....but I would be interested in what more > > knowledgeable people on SBo feel ? > > > > > > Thank you and good day to all. > > Habs > > > > On 8 August 2016 at 23:16, wrote: > > > hi there all > > > > > > I have tried the -Os switch and it does appear to remedy the problem. > > > Icecat no longer crashes in the scenario(s) I have documented. > > > > > > I wonder what the -O2 switch does differently to the -Os one. > > > > > > So for now that does appear to be the 'fix'. Thank you all. > > > > > > > > > Habs > > > > > > On 8 August 2016 at 20:36, Ryan P.C. McQuen wrote: > > >> On Monday, August 8, 2016, Ivan Zaigralin > wrote: > > >>> I still can't replicate any crash whatsoever, even in places where > > >>> others > > >>> report them. However, Matt tells me that crashes went away after he > > >>> rebuilt > > >>> with -Os. He also mentioned he's got an AMD Phenom, whereas I am > using > > >>> Intel > > >>> CPU, which may explain why I am unable to hit this snag. > > >>> > > >>> I can certainly submit a fixed SlackBuild if there's a consensus -Os > is > > >>> an > > >>> effective fix. Please let me know :) > > >> > > >> Seems like that would be valid, since Slackware's own Firefox build > was > > >> passing that for version 43, and only removed it for versions past 43: > > >> > > >> (Changelog reference): > > >> > > >> Wed Dec 23 22:44:58 UTC 2015 > > >> a/lvm2-2.02.138-i586-1.txz: Upgraded. > > >> ap/ghostscript-9.18-i586-1.txz: Upgraded. > > >> ap/lsof-4.89-i586-1.txz: Upgraded. > > >> l/pycups-1.9.73-i586-1.txz: Upgraded. > > >> l/pycurl-7.19.5.3-i586-1.txz: Upgraded. > > >> n/NetworkManager-1.0.10-i586-1.txz: Upgraded. > > >> n/curl-7.46.0-i586-1.txz: Upgraded. > > >> n/links-2.12-i586-1.txz: Upgraded. > > >> n/obexfs-0.12-i486-1.txz: Removed. > > >> > > >> This functionality is now included in the obexftp package. > > >> > > >> n/obexftp-0.24-i586-1.txz: Upgraded. > > >> > > >> Thanks to Robby Workman. > > >> > > >> n/openobex-1.7.1-i586-1.txz: Upgraded. > > >> > > >> Thanks to Robby Workman. > > >> > > >> n/rsync-3.1.2-i586-1.txz: Upgraded. > > >> x/libXi-1.7.6-i586-1.txz: Upgraded. > > >> x/pixman-0.33.6-i586-1.txz: Upgraded. > > >> x/xorg-cf-files-1.0.6-noarch-1.txz: Upgraded. > > >> xap/mozilla-firefox-43.0.2-i586-2.txz: Rebuilt. > > >> > > >> Compile with -Os instead of -O2 to work around crash issues. > > >> Recent betas are working fine with -O2, so we'll probably be > > >> able to switch back to that again soon. Thanks to j_v. > > >> > > >> -- > > >> -Ryan > > >> [ryanpcmcquen.org] > > >> > > >> > > >> _______________________________________________ > > >> 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/ > > -- > http://gnuzilla.gnu.org > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From klaatu at member.fsf.org Wed Aug 17 07:59:58 2016 From: klaatu at member.fsf.org (Klaatu) Date: Wed, 17 Aug 2016 19:59:58 +1200 Subject: [Slackbuilds-users] update/correction for kvpm Message-ID: <2856979b-ec28-509f-127d-81831cc97ccc@member.fsf.org> Can an admin change the download link for kvpm to this: http://downloads.sourceforge.net/project/kvpm/kvpm-0.9.9.tar.gz Cheers. diff -Naur output inline for reference. --- /usr/ports/system/kvpm/kvpm.info 2016-07-02 12:48:23.000000000 +1200 +++ /home/sek/code/slackbuilds.clone/system/kvpm/kvpm.info 2016-08-16 19:38:40.038218231 +1200 @@ -1,7 +1,7 @@ PRGNAM="kvpm" VERSION="0.9.9" HOMEPAGE="http://kvpm.sourceforge.net" -DOWNLOAD="http://iweb.dl.sourceforge.net/project/kvpm/kvpm-0.9.9.tar.gz" +DOWNLOAD="http://downloads.sourceforge.net/project/kvpm/kvpm-0.9.9.tar.gz" MD5SUM="ed4f41fd14803d339487a70baf3e68cc" DOWNLOAD_x86_64="" MD5SUM_x86_64="" From matteo.bernardini at gmail.com Wed Aug 17 08:31:10 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 17 Aug 2016 10:31:10 +0200 Subject: [Slackbuilds-users] update/correction for kvpm In-Reply-To: <2856979b-ec28-509f-127d-81831cc97ccc@member.fsf.org> References: <2856979b-ec28-509f-127d-81831cc97ccc@member.fsf.org> Message-ID: done in my branch. Matteo From hjensen at gmx.de Wed Aug 17 08:35:18 2016 From: hjensen at gmx.de (Henry Jensen) Date: Wed, 17 Aug 2016 10:35:18 +0200 Subject: [Slackbuilds-users] [Bug-gnuzilla] icecat 38.8.0 crashes In-Reply-To: <1786691.mHFlXvMcxy@ithil> References: <1786691.mHFlXvMcxy@ithil> Message-ID: <20160817083518.GA24843@jensen.local> Hello, On Tue, Aug 16, 2016 at 11:05:28AM -0700, Ivan Zaigralin wrote: > Finally, I believe there is a niche opening up for a firefox-based browser > which is libre and meets free software distrubution guidelines like icecat, > but has no extra privacy features, and passes all the mozilla pearls onto the > users. Such minimal deblobbing could be potentially more robust: that is, new > releases could be churned out as quickly and reliably as linux-libre. Looking > at Parabola's thunderbird & seamonkey builds, I imagine something like that > could be done for firefox as well. Anyone can step in and claim the glory for > this one :) I don't have time to write a slackbuild like that and run it by > FSF, but if anyone did it, I think I would actually switch. Parabola GNU/linux and ConnochaetOS have such a liberated mozilla based Browser based an Debian's Iceweasel. Parabola's Iceweasel is based on current Firefox, ConnochaetOS uses LTS. https://www.parabola.nu/packages/libre/i686/iceweasel/ https://connochaetos.org/slack-n-free/slack-n-free-14.2/xap/iceweasel-45.3.0-i486-1_libre.txz https://connochaetos.org/slack-n-free/source/src/iceweasel/ https://connochaetos.org/slack-n-free/source/dist/slack-n-free-14.2/iceweasel/iceweasel.SlackBuild Regards, Henry From andrew.david.strong at gmail.com Wed Aug 17 10:37:12 2016 From: andrew.david.strong at gmail.com (andrew) Date: Wed, 17 Aug 2016 20:37:12 +1000 Subject: [Slackbuilds-users] Orphaned slackbuilds..... Message-ID: <20160817103712.GA6791@ilium.andrews-corner.org> I will be taking a break from the online world for a while so I am keen to find a good home for the following slackbuilds that I am currently maintaining: * apetag * d1x-rebirth * d2x-rebirth * eyeD3 * fdkaac * glyr * l-smash * libfdk-aac * physfs Andrew -- You think that's air you're breathing now? From chris.willing at iinet.net.au Wed Aug 17 10:54:35 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 17 Aug 2016 20:54:35 +1000 Subject: [Slackbuilds-users] Orphaned slackbuilds..... In-Reply-To: <20160817103712.GA6791@ilium.andrews-corner.org> References: <20160817103712.GA6791@ilium.andrews-corner.org> Message-ID: <6feb45d6-ce0d-c30f-a035-1c0e67ba49d5@iinet.net.au> On 17/08/16 20:37, andrew wrote: > I will be taking a break from the online world for a while so I am > keen to find a good home for the following slackbuilds that I am > currently maintaining: > > * libfdk-aac Since this will become an optional build dep for the updated obs-studio SlackBuild I'm just about to upload, I'll take this one. chris From larryhaja at gmail.com Wed Aug 17 13:51:38 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Wed, 17 Aug 2016 06:51:38 -0700 Subject: [Slackbuilds-users] Orphaned slackbuilds..... In-Reply-To: <20160817103712.GA6791@ilium.andrews-corner.org> References: <20160817103712.GA6791@ilium.andrews-corner.org> Message-ID: > > * eyeD3 > * fdkaac > * physfs > I can take these. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Wed Aug 17 19:22:31 2016 From: yalhcru at gmail.com (B Watson) Date: Wed, 17 Aug 2016 15:22:31 -0400 Subject: [Slackbuilds-users] Orphaned slackbuilds..... In-Reply-To: <20160817103712.GA6791@ilium.andrews-corner.org> References: <20160817103712.GA6791@ilium.andrews-corner.org> Message-ID: On 8/17/16, andrew wrote: > * apetag > * glyr > * l-smash I'll take these. From yalhcru at gmail.com Wed Aug 17 21:10:42 2016 From: yalhcru at gmail.com (B Watson) Date: Wed, 17 Aug 2016 17:10:42 -0400 Subject: [Slackbuilds-users] Fwd: No Longer A Maintainer In-Reply-To: References: <9b71449d-e942-54d5-578b-eb55bb1ae616@slackbuilds.org> Message-ID: On 8/15/16, B Watson wrote: >> desktop/wmwebcam Hm, I said I'd take wmwebcam, but I have no way to test it (don't own a webcam). I can still make sure it builds a package correctly, but maybe someone else who actually can test-run it would take it...? From edps.mundognu at gmail.com Wed Aug 17 00:49:17 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Tue, 16 Aug 2016 21:49:17 -0300 Subject: [Slackbuilds-users] libuchardet download link Message-ID: Hello, please update the download link for "libuchardet" to: https://github.com/BYVoid/uchardet/archive/v0.0.5/uchardet-0.0.5.tar.gz The current link ( https://github.com/BYVoid/uchardet/archive/0.0.5/uchardet-0.0.5.tar.gz ) is broken. * md5sum are the same. Cheers, Edinaldo. From willysr at slackbuilds.org Wed Aug 17 23:26:21 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 18 Aug 2016 06:26:21 +0700 Subject: [Slackbuilds-users] libuchardet download link In-Reply-To: References: Message-ID: <752e880c-367e-da7b-3df0-0ce099a99aeb@slackbuilds.org> > please update the download link for "libuchardet" to: > > https://github.com/BYVoid/uchardet/archive/v0.0.5/uchardet-0.0.5.tar.gz > > > The current link ( > https://github.com/BYVoid/uchardet/archive/0.0.5/uchardet-0.0.5.tar.gz ) > is broken. 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 fernando.lopezjr at gmail.com Wed Aug 17 23:27:49 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 17 Aug 2016 17:27:49 -0600 Subject: [Slackbuilds-users] radare2 update? Message-ID: Is there any way we could update radare2 to latest 0.10.5 current in repo is 0.9.8. thank you. bcc maintainer. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Thu Aug 18 14:55:00 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Thu, 18 Aug 2016 07:55:00 -0700 Subject: [Slackbuilds-users] tmw source is missing Message-ID: Hi, I tried building tmw and it failed to download. The sources have been deleted from sourceforge and moved to either github or gitorious. I'm not sure which, but the files download page on sourceforge does give a readme. https://sourceforge.net/projects/themanaworld/files/ Thanks, --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Aug 19 11:55:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 19 Aug 2016 18:55:39 +0700 Subject: [Slackbuilds-users] tmw source is missing In-Reply-To: References: Message-ID: <69ba9ad1-8890-2cd4-8f96-7995e0beb028@slackbuilds.org> > I tried building tmw and it failed to download. The sources have been > deleted from sourceforge and moved to either github or gitorious. I'm not > sure which, but the files download page on sourceforge does give a readme. > > https://sourceforge.net/projects/themanaworld/files/ Done in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Aug 20 01:26:26 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 20 Aug 2016 08:26:26 +0700 Subject: [Slackbuilds-users] Updates - 20160820.1 Message-ID: <0dcd0ffc-098d-8fb0-ef83-acabef35b4a6@slackbuilds.org> Sat Aug 20 00:54:34 UTC 2016 academic/avogadro: Updated for version 1.2.0 academic/ent: i486 => i586. academic/pianobooster: i486 => i586. academic/wmcalc: New maintainer, minor fixes. accessibility/espeak: i486 => i586. accessibility/flite: i486 => i586. accessibility/svkbd: i486 => i586. accessibility/unclutter: i486 => i586. accessibility/xdotool: i486 => i586. accessibility/xsel: i486 => i586. audio/alsa-tools: i486 => i586. audio/alsacap: i486 => i586. audio/bristol: i486 => i586. audio/calf-ladspa: i486 => i586. audio/calf: i486 => i586. audio/caps: i486 => i586. audio/clam: i486 => i586. audio/clam_annotator: i486 => i586. audio/clam_voice2midi: i486 => i586. audio/cmt: i486 => i586. audio/connie: i486 => i586. audio/creox4: i486 => i586. audio/ecasound: i486 => i586. audio/eyeD3: Updated for version 0.7.9 audio/fIcy: i486 => i586. audio/fluidsynth-dssi: i486 => i586. audio/fmmidi: i486 => i586. audio/foo-yc20: i486 => i586. audio/ghostess: i486 => i586. audio/grip2: i486 => i586. audio/gtklick: i486 => i586. audio/horgand: i486 => i586. audio/invada_studio_plugins_lv2: i486 => i586. audio/jaaa: i486 => i586. audio/jack-keyboard: i486 => i586. audio/jack-rack: i486 => i586. audio/jack-tools: i486 => i586. audio/jack_delay: i486 => i586. audio/jackmeter: i486 => i586. audio/jalv: i486 => i586. audio/japa: i486 => i586. audio/jkmeter: i486 => i586. audio/jnoise: i486 => i586. audio/klick: i486 => i586. audio/lingot: i486 => i586. audio/lsmi: i486 => i586. audio/lv2-mda-metapiano: i486 => i586. audio/lv2dynparam1: i486 => i586. audio/lv2file: i486 => i586. audio/match-vamp-plugin: i486 => i586. audio/mda-lv2: i486 => i586. audio/mididings: i486 => i586. audio/midillo: i486 => i586. audio/millennium-plugins: i486 => i586. audio/mp3gain: i486 => i586. audio/mp3splt-gtk: Fix typo in MAINTAINER. audio/mp3splt: Fix typo in MAINTAINER. audio/mp3val: i486 => i586. audio/mpd: Updated for version 0.19.18. audio/ngjackspa: i486 => i586. audio/nnls-chroma: i486 => i586. audio/oss: i486 => i586. audio/qm-vamp-plugins: i486 => i586. audio/qmidiroute: i486 => i586. audio/rakarrack: i486 => i586. audio/rev-plugins: i486 => i586. audio/rubberband: i486 => i586. audio/sfc: i486 => i586. audio/sonic-visualiser: i486 => i586. audio/sooperlooper: i486 => i586. audio/swh-plugins-lv2: i486 => i586. audio/tap_plugins: i486 => i586. audio/tapiir: i486 => i586. audio/transcribe: i486 => i586. audio/vamp-plugin-sdk: i486 => i586. audio/vcf_plugins: i486 => i586. audio/vocoder-ladspa: i486 => i586. audio/vocoder: i486 => i586. audio/waon: i486 => i586. audio/wineasio: i486 => i586. audio/wmusic: New maintainer, minor fixes. audio/xmms-jack: i486 => i586. audio/xmms-mp4: i486 => i586. audio/xsynth-dssi: i486 => i586. audio/zita-ajbridge: i486 => i586. audio/zita-dpl1: i486 => i586. audio/zita-rev1: i486 => i586. audio/zynjacku: i486 => i586. desktop/glabels: Added (Label Designer). desktop/idesk: i486 => i586. desktop/j4-dmenu-desktop: i486 => i586. desktop/lumina: Fix xinitrc. desktop/peksystray: i486 => i586. desktop/slock: Updated for version 1.3. desktop/spectrwm: Updated for version 3.0.2. desktop/tint2: Update script. desktop/trayer-srg: i486 => i586. desktop/wmblob: New maintainer, minor fixes. desktop/wmclock: i486 => i586. desktop/wmmon: i486 => i586. desktop/wmtimer: New maintainer, minor fixes. desktop/wmudmount: Updated for version 2.2, new maintainer. desktop/wmweather+: New maintainer, minor fixes. desktop/wmxss: New maintainer, minor fixes. desktop/xtrlock: i486 => i586. development/OpenCobolIDE: Updated for version 4.7.4. development/as31: i486 => i586. development/atasm: i486 => i586. development/atom: Updated for version 1.9.8. development/cc65: i486 => i586. development/chicken: Updated for version 4.11.0. development/dhex: i486 => i586. development/ex-vi: i486 => i586. development/fsharp: Don't run cert-sync (moved to mono). development/gnulib: i486 => i586. development/hub: Updated for version 2.2.5. development/inform: i486 => i586. development/ldns: Script cleanup development/leo: Updated for version 5.3.final. development/love-legacy072: i486 => i586. development/love-legacy080: i486 => i586. development/ltrace: i486 => i586. development/mono: Updated for version 4.4.2.11. development/mutagen: Updated for version 1.34.1. development/nodejs: Updated for version 4.5.0. development/obcpl: i486 => i586. development/p4v: Updated for version 2015.2.1315639. development/pcc: i486 => i586. development/pyenchant: Updated for version 1.6.6 + new maintainer. development/referenceassemblies-pcl: Added (Reference Assemblies). development/snappy: Updated for version 1.1.3. development/sphinx_rtd_theme: Added (sphinx theme). development/spyder: Updated for version 2.3.9 development/squirrel-sql: Updated for version 3.7.1. development/srecord: i486 => i586. development/tstoolbox: Updated for version 0.12.12.8. development/unifdef: i486 => i586. development/xa: i486 => i586. development/xtruss: i486 => i586. games/adl: i486 => i586. games/aklabeth: Added (remake of Richard Garriott's Ultima prequel). games/alephone: i486 => i586. games/atari++: i486 => i586. games/atari800: i486 => i586. games/bastet: i486 => i586. games/brickout: i486 => i586. games/bstone: Added (first-person shooter game). games/burgerspace: i486 => i586. games/ceferino: i486 => i586. games/chocolate-doom: i486 => i586. games/circuslinux: i486 => i586. games/clonekeen: i486 => i586. games/colem: i486 => i586. games/cosmosmash: i486 => i586. games/defendguin: i486 => i586. games/doomretro: Adds the .desktop file and icon. games/doomseeker: i486 => i586. games/dunelegacy: i486 => i586. games/dungeon: i486 => i586. games/eduke32: Fix SDL2=auto build. games/fizmo: Fix REQUIRES. games/frotz: i486 => i586. games/glbsp: i486 => i586. games/gtkballs: i486 => i586. games/gtklife: i486 => i586. games/icebreaker: i486 => i586. games/jezzball-kazzmir: i486 => i586. games/jfsw: i486 => i586. games/jzintv: i486 => i586. games/kardsgt: i486 => i586. games/koules: i486 => i586. games/liquidwar6: i486 => i586. games/lmarbles: i486 => i586. games/madbomber: i486 => i586. games/maelstrom: i486 => i586. games/mame: i486 => i586. games/megamario: Added (Super Mario Brothers clone). games/mgba: Fixed MD5SUM. games/micropolis: i486 => i586. games/nevernoid: i486 => i586. games/nexuiz: i486 => i586. games/noteye: i486 => i586. games/o2em: i486 => i586. games/oblige-legacy4: i486 => i586. games/oblige: i486 => i586. games/odamex: i486 => i586. games/openjazz: i486 => i586. games/openmortal: i486 => i586. games/opentyrian: i486 => i586. games/openyahtzee: i486 => i586. games/ostrichriders: i486 => i586. games/pacman-arena: i486 => i586. games/penguin-command: i486 => i586. games/pentagram: i486 => i586. games/pom1: i486 => i586. games/rott: i486 => i586. games/skulltag: i486 => i586. games/smc: i486 => i586. games/sms_sdl: i486 => i586. games/snes9x: i486 => i586. games/solarwolf: i486 => i586. games/stratagus: i486 => i586. games/supermariowar: i486 => i586. games/syobonaction: i486 => i586. games/taipan: i486 => i586. games/tmw: Update DOWNLOAD url. games/torcs: i486 => i586. games/trackballs: i486 => i586. games/transfusion: i486 => i586. games/typhoon_2001: i486 => i586. games/ucr: i486 => i586. games/ufoai: i486 => i586. games/uqm: i486 => i586. games/vectoroids: i486 => i586. games/wargus: i486 => i586. games/wmquake: New maintainer, fix build. games/wolf4sdl: i486 => i586. games/xcowsay: i486 => i586. games/xroar: i486 => i586. games/xu4: i486 => i586. games/yae: i486 => i586. games/yahtzee: i486 => i586. games/yar: i486 => i586. games/z26: i486 => i586. games/zennode: i486 => i586. games/zoom: i486 => i586. games/zsnes: i486 => i586. games/ztools: i486 => i586. gis/geographiclib-python: Added (Python geodesic routines). gis/pyshp: Updated for version 1.2.9. graphics/GraphicsMagick: i486 => i586. graphics/baires: i486 => i586. graphics/fbida: Fix typo in EMAIL. graphics/fbv: i486 => i586. graphics/flpsed: i486 => i586. graphics/gifsicle: i486 => i586. graphics/graph-easy: Updated for version 0.76. graphics/imgmin: Added (Automated lossy JPEG optimization). graphics/mcomix: i486 => i586. graphics/paraview: Enable optional PythonQt embedding support graphics/psftools: i486 => i586. graphics/vuescan: Updated for version 9.5.54. libraries/aqbanking: Updated for version 5.6.12. libraries/argtable: i486 => i586. libraries/botocore: Updated for version 1.4.47. libraries/configobj: i486 => i586. libraries/crossguid: Added (cross platform C++ GUID/UUID library). libraries/dcadec: Added (DTS Coherent Acoustics decoder). libraries/flatzebra: i486 => i586. libraries/girara: i486 => i586. libraries/gwenhywfar: Updated for version 4.15.3. libraries/jbig2dec: i486 => i586. libraries/lgi: Updated for version 0.9.1. libraries/libfdk-aac: Update 32bit ARCH + new maintainer libraries/libicns: i486 => i586. libraries/libmp3splt: Fix typo in MAINTAINER. libraries/libnfs: Updated for version 1.10.0 libraries/libpst: Fix typo in MAINTAINER. libraries/libpst: i486 => i586. libraries/libsigc++-legacy12: i486 => i586. libraries/libsmf: i486 => i586. libraries/libtsm: i486 => i586. libraries/libuchardet: Fix DOWNLOAD url. libraries/libwebsockets: Added (C websocket library). libraries/ltm: i486 => i586. libraries/lvtk: i486 => i586. libraries/podofo: Updated for version 0.9.4 libraries/pyqode.core: Updated for version 2.10.0. libraries/zita-convolver: i486 => i586. misc/cwiid: i486 => i586. misc/heyu: i486 => i586. misc/jmri: Updated for version 3.10.1 + new maintainer. misc/keychain: Updated for version 2.8.3 multimedia/MediathekView: Updated for version 11. multimedia/apetag: New maintainer, minor fixes. multimedia/devedeng: Updated for version 4.8.0. multimedia/glyr: Updated for version 1.0.9, new maintainer. multimedia/gpac: Updated for version 0.6.1. multimedia/gpodder: Updated for version 3.9.0. multimedia/l-smash: Updated for version 2.9.1, new maintainer. multimedia/lsdvd: i486 => i586. multimedia/mtpfs: i486 => i586. multimedia/nted: i486 => i586. multimedia/obs-studio: Updated for version 0.15.4 + new maintainer multimedia/vitunes-mplayer: i486 => i586. network/FireWorks: Updated for version 1.3.4. network/Pafy: Updated for version 0.5.2. network/amavisd-new: Updated for version 2.11.0. network/authbind: i486 => i586. network/awscli: Updated for version 1.10.57. network/bmon: i486 => i586. network/cicb: i486 => i586. network/clamav-unofficial-sigs: Updated for version 5.4.1. network/flexget: Updated for version 2.2.20. network/httpie: Updated for version 0.9.6. network/irssi_otr: i486 => i586. network/museek+: i486 => i586. network/offlineimap: Updated for version 7.0.5. network/phpmyadmin: Updated for version 4.6.4. network/rhapsody: i486 => i586. network/socat: Updated for version 1.7.3.1 network/surf: i486 => i586. network/tor-browser: Updated for version 6.0.4. network/transmission: i486 => i586. network/tribler: i486 => i586. network/uTox: Updated for version 0.9.8 + new maintainer network/uget: i486 => i586. network/wmnd: New maintainer, minor fixes. network/youtube-dl: Updated for version 2016.08.13. office/calibre: Updated for version 2.64.0 office/convertlit: i486 => i586. office/diffpdf: Added (Compare PDF Files). office/xtrkcad: Updated for version 4.2.3b. office/zathura-cb: i486 => i586. office/zathura-djvu: i486 => i586. office/zathura-pdf-mupdf: i486 => i586. office/zathura-ps: i486 => i586. office/zathura: i486 => i586. perl/perl-Math-GMPq: Updated for version 0.41. perl/perl-Module-Build: Updated for version 0.4220. perl/perl-data-dump: i486 => i586. perl/perl-lwp-useragent-cached: i486 => i586. perl/perl-text-unaccent: i486 => i586. perl/perl-xml-fast: i486 => i586. python/Flask-Cors: Updated for version 2.1.3. python/Pygments: Updated for version 2.1.3. python/Scrapy: Updated for version 1.1.2. python/fabric: Added (tool for remote execution and deployment). python/flask-paginate: Added (Simple paginate support for flask). python/githubpy: Added (A simple GitHub v3 API SDK for Python). python/gmpy: i486 => i586. python/gunicorn: Added (WSGI HTTP Server for UNIX). python/prompt_toolkit: Updated for version 1.0.6. python/pyliblo: i486 => i586. python/pyqode.cobol: Added (Adds COBOL support to pyqode.core). python/pyqode.qt: Added (Wrapper library for PyQt and PySIde). python/python-keybinder: i486 => i586. python/python-requests-kerberos: Updated for version 0.10.0. python/python-requests: Update DOWNLOAD url. python/python3-future: Added (Python 2/3 compatibility). python/s3transfer: Updated for version 0.1.2. python/stevedore: Updated for version 1.17.1. ruby/rubygem-gosu: Updated for version 0.10.8. system/a2tools: i486 => i586. system/aha: i486 => i586. system/arc: i486 => i586. system/arj: i486 => i586. system/blake2: Updated for version 20160619. system/borgbackup: Added (deduplicating backup program). system/cbmbasic: i486 => i586. system/conky: Updated for version 1.10.4. system/cpmtools: i486 => i586. system/csh: i486 => i586. system/d52: i486 => i586. system/dar: Updated for version 2.5.5. system/ded: i486 => i586. system/dos33fsprogs: i486 => i586. system/findpkg: Updated for version 20160710. system/forkstat: Updated for version 0.01.14. system/fsv: i486 => i586. system/fsviewer: i486 => i586. system/gphotofs: i486 => i586. system/isomd5sum: i486 => i586. system/kegs: i486 => i586. system/kmscon: i486 => i586. system/kvpm: Fix download link. system/lbzip2: i486 => i586. system/lhasa: i486 => i586. system/linuxconsoletools: i486 => i586. system/lz4: i486 => i586. system/macutils: i486 => i586. system/man-db: i486 => i586. system/man-pages-es: Remove unused SLKCFLAGS. system/mlterm: Updated for version 3.7.2. system/pipemeter: i486 => i586. system/polyglotman: i486 => i586. system/read-edid: i486 => i586. system/reptyr: i486 => i586. system/rmw: Updated for version 2016.08.17.01a. system/rtirq: Use ARCH=noarch. system/sandy: i486 => i586. system/sdl-jstest: Fix typo in MAINTAINER. system/sdl-jstest: i486 => i586. system/suckless-tools: i486 => i586. system/sysdig: Updated for version 0.11.0 system/tabbed: i486 => i586. system/trackfs: i486 => i586. system/u3-tool: i486 => i586. system/unac: i486 => i586. system/unshield: i486 => i586. system/usbmon: i486 => i586. system/vcp: i486 => i586. system/vinterm: i486 => i586. system/wmgtemp: New maintainer, minor fixes. system/xautomation: i486 => i586. system/xonsh: Updated for version 0.4.5. system/zerofree: i486 => i586. +--------------------------+ -- 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 awakeyet at tutanota.de Thu Aug 18 17:50:14 2016 From: awakeyet at tutanota.de (awakeyet at tutanota.de) Date: Thu, 18 Aug 2016 18:50:14 +0100 (BST) Subject: [Slackbuilds-users] [Bug-gnuzilla] icecat 38.8.0 crashes In-Reply-To: <20160817083518.GA24843@jensen.local> References: <> <1786691.mHFlXvMcxy@ithil> <<1786691.mHFlXvMcxy@ithil>> <20160817083518.GA24843@jensen.local> Message-ID: sounds really nice, but why would we want to pass along such strongly minimalistic "un-de-freedomed" browsers along to the normal people specifically without added security features? this basically lands them back right where they started since they are immediately washed clean and then re-exposed to the filth of the world again. we have to help them but "here don't go alone, take this!" without security- without defense there is nothing worth defending. -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 17. Aug 2016 04:35 by hjensen at gmx.de: > Hello, > > On Tue, Aug 16, 2016 at 11:05:28AM -0700, Ivan Zaigralin wrote: > >> Finally, I believe there is a niche opening up for a firefox-based browser >> which is libre and meets free software distrubution guidelines like icecat, >> but has no extra privacy features, and passes all the mozilla pearls onto the >> users. Such minimal deblobbing could be potentially more robust: that is, new >> releases could be churned out as quickly and reliably as linux-libre. Looking >> at Parabola's thunderbird & seamonkey builds, I imagine something like that >> could be done for firefox as well. Anyone can step in and claim the glory for >> this one :) I don't have time to write a slackbuild like that and run it by >> FSF, but if anyone did it, I think I would actually switch. > > Parabola GNU/linux and ConnochaetOS have such a liberated mozilla based > Browser based an Debian's Iceweasel. Parabola's Iceweasel is based on > current Firefox, ConnochaetOS uses LTS. > > https://www.parabola.nu/packages/libre/i686/iceweasel > > https://connochaetos.org/slack-n-free/slack-n-free-14.2/xap/iceweasel-45.3.0-i486-1_libre.txz > https://connochaetos.org/slack-n-free/source/src/iceweasel > https://connochaetos.org/slack-n-free/source/dist/slack-n-free-14.2/iceweasel/iceweasel.SlackBuild > > Regards, > > Henry > > > > -- > http://gnuzilla.gnu.org -------------- next part -------------- An HTML attachment was scrubbed... URL: From hjensen at gmx.de Sat Aug 20 20:11:12 2016 From: hjensen at gmx.de (Henry Jensen) Date: Sat, 20 Aug 2016 22:11:12 +0200 Subject: [Slackbuilds-users] [Bug-gnuzilla] icecat 38.8.0 crashes In-Reply-To: References: < <1786691.mHFlXvMcxy@ithil> <<1786691.mHFlXvMcxy@ithil> <20160817083518.GA24843@jensen.local> Message-ID: <20160820221112.30fe3337@desktop.jensen.local> Hi, On Thu, 18 Aug 2016 18:50:14 +0100 (BST) wrote: > sounds really nice, but why would we want to pass along such strongly minimalistic > "un-de-freedomed" browsers along to the normal people specifically without added security features? this basically lands them back right where they started since they are immediately washed clean and then re-exposed to the filth of the world again. we have to help them but "here don't go alone, take this!" without security- without defense there is nothing worth defending. I don't quite understand. A libre web browser does give people a browser which does not download proprietary plugins without asking nor suggest to install non-free Addons. Privacy aware search engines are enabled by default. Why would this lead people back "to the filth"? Users of free software are not stupid. I strongly believe that people must be offered complete free/libre software. But we don't have to lecture them like children what the can and can't do. This attitude will provoke contradiction. We can suggest and recommend - but the choice should be freely made by the user. Regards, Henry From yalhcru at gmail.com Sat Aug 20 20:55:24 2016 From: yalhcru at gmail.com (B Watson) Date: Sat, 20 Aug 2016 16:55:24 -0400 Subject: [Slackbuilds-users] xmkmf on upgraded systems Message-ID: Found this a while back, forgot to send it to the list... On systems that were upgraded to 14.2 (rather than a new install), xmkmf will fail with: /usr/lib64/X11/config/site.def:44:0: fatal error: host.def: No such file or directory This is due to a bad interaction between 14.1's lesstif package and 14.2's xorg-cf-files. Pat knows about this, but hasn't had time to do anything about it yet (if he's going to for 14.2). Reinstalling xorg-cf-files will fix it, but we can also work around it in our SlackBuilds... host.def is an empty file in 14.2, so all that's needed is to "touch host.def" in the source directory, and any subdirectories containing an Imakefile. For koules, it looks like: touch host.def xlib/host.def util/host.def For most builds it's simply "touch host.def" just before running xmkmf. To test this, rm /usr/lib64/X11/config/host.def and run your build. You can put it back with touch, afterwards. Affected builds: audio/nas audio/xforge desktop/9menu desktop/ctwm desktop/root-tail desktop/vtwm desktop/wmdate desktop/wmnet desktop/xsession desktop/xxkb games/xspacewarp graphics/tgif-QPL graphics/xbmbrowser graphics/xli network/tightvnc From icaroperseo at riseup.net Sat Aug 20 21:17:30 2016 From: icaroperseo at riseup.net (Icaro Perseo) Date: Sat, 20 Aug 2016 16:17:30 -0500 Subject: [Slackbuilds-users] QupZilla missing dependency? Message-ID: <20160820211729.GA941@riseup.net> Good day! Reading the BUILDING.md file from QupZilla repository (upstream) and comparing it with qupzilla.info file from SBo, it seems to be a missing dependency: qt5-webkit. Source: https://github.com/QupZilla/qupzilla/blob/master/BUILDING.md#linux--unix Regards. -- Si deseas conocer qu? es GnuPG, su uso y aplicaciones te sugiero que visites la siguiente p?gina: https://emailselfdefense.fsf.org/es/ If you want to know what GnuPG is, its use and applications I suggest you visit the following page: https://emailselfdefense.fsf.org/ Fingerprint: 99F4 D957 9C0D 9552 73B9 34BA A453 EB5E 60A2 ADDC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dpross1100 at msn.com Sat Aug 20 21:26:23 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 20 Aug 2016 21:26:23 +0000 Subject: [Slackbuilds-users] QupZilla missing dependency? In-Reply-To: <20160820211729.GA941@riseup.net> References: <20160820211729.GA941@riseup.net> Message-ID: Are you using an old version of Qupzilla? The latest version uses Qt WebEngine, which is included in Qt5, instead of Webkit. On Saturday, August 20, 2016 04:17:30 PM Icaro Perseo wrote: > Good day! > > Reading the BUILDING.md file from QupZilla repository (upstream) and > comparing it with qupzilla.info file from SBo, it seems to be a missing > dependency: qt5-webkit. > > Source: > https://github.com/QupZilla/qupzilla/blob/master/BUILDING.md#linux--unix > > Regards. From icaroperseo at riseup.net Sat Aug 20 21:39:12 2016 From: icaroperseo at riseup.net (Icaro Perseo) Date: Sat, 20 Aug 2016 16:39:12 -0500 Subject: [Slackbuilds-users] QupZilla missing dependency? In-Reply-To: References: <20160820211729.GA941@riseup.net> Message-ID: <20160820213911.GB941@riseup.net> OMG, you're right! Thank you very much for the clarification! Regards. On Sat, Aug 20, 2016 at 09:26:23PM +0000, Daniel Prosser wrote: > Are you using an old version of Qupzilla? The latest version uses Qt > WebEngine, which is included in Qt5, instead of Webkit. > > On Saturday, August 20, 2016 04:17:30 PM Icaro Perseo wrote: > > Good day! > > > > Reading the BUILDING.md file from QupZilla repository (upstream) and > > comparing it with qupzilla.info file from SBo, it seems to be a missing > > dependency: qt5-webkit. > > > > Source: > > https://github.com/QupZilla/qupzilla/blob/master/BUILDING.md#linux--unix > > > > Regards. > > _______________________________________________ > 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/ > -- Si deseas conocer qu? es GnuPG, su uso y aplicaciones te sugiero que visites la siguiente p?gina: https://emailselfdefense.fsf.org/es/ If you want to know what GnuPG is, its use and applications I suggest you visit the following page: https://emailselfdefense.fsf.org/ Fingerprint: 99F4 D957 9C0D 9552 73B9 34BA A453 EB5E 60A2 ADDC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From duncan_roe at acslink.net.au Sun Aug 21 03:01:15 2016 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Sun, 21 Aug 2016 13:01:15 +1000 Subject: [Slackbuilds-users] My new submission was rejected by mx.partnerconsole.net Message-ID: <20160821030115.GA5739@dimstar.local.net> Hi, On trying to upload a new package, I received > duncan_roe at acslink.net.au was rejected by mx.partnerconsole.net. > Go back and enter a valid E-Mail address. but that's my subscribed address. What's happening? Cheers ... Duncan. -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html From chris.willing at iinet.net.au Sun Aug 21 06:03:07 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 21 Aug 2016 16:03:07 +1000 Subject: [Slackbuilds-users] My new submission was rejected by mx.partnerconsole.net In-Reply-To: <20160821030115.GA5739@dimstar.local.net> References: <20160821030115.GA5739@dimstar.local.net> Message-ID: <73ffdf23-46df-d297-cbe5-6f264d9c787a@iinet.net.au> On 21/08/16 13:01, Duncan Roe wrote: > Hi, > > On trying to upload a new package, I received > >> duncan_roe at acslink.net.au was rejected by mx.partnerconsole.net. >> Go back and enter a valid E-Mail address. > > but that's my subscribed address. What's happening? Pointing a browser at acslink.net.au produces a page from netregistry.com.au saying: "acslink.net.au is a parked domain The owner of this domain has yet to point it to a website or online content. This means that the domain is parked." (then more related stuff) Also, whois acslink.net.au shows that ns{1-3}.partnerconsole.net are DNS servers for that domain. Therefore rejection by mx.partnerconsole.net would imply some problem with the registration or configuration of the domain. chris From navigium at grindcore.ch Sun Aug 21 07:12:12 2016 From: navigium at grindcore.ch (Beni) Date: Sun, 21 Aug 2016 09:12:12 +0200 Subject: [Slackbuilds-users] My new submission was rejected by mx.partnerconsole.net In-Reply-To: <20160821030115.GA5739@dimstar.local.net> References: <20160821030115.GA5739@dimstar.local.net> Message-ID: <92f6eca5-8ec7-7c41-27e5-70432e9a5543@grindcore.ch> On 08/21/2016 05:01 AM, Duncan Roe wrote: > Hi, > > On trying to upload a new package, I received > >> duncan_roe at acslink.net.au was rejected by mx.partnerconsole.net. >> Go back and enter a valid E-Mail address. > > but that's my subscribed address. What's happening? I had the same problem once. In my case the reason was that the mailserver uses graylisting as a method to defend spam. This leads to it refusing the first connection of a unknown remote mailserver and waiting for it to try a second time. Most spam bots won't try again. Unfortunately the script that checks e-mail addresses on Slackbuilds uses this first connection to check whether a email is valid. The only way I had to solve this was to use another address. You you have this option, you could try to deactivate graylisting. Beni From unix_lists at f-m.fm Sun Aug 21 18:04:53 2016 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Sun, 21 Aug 2016 13:04:53 -0500 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date Message-ID: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> Is someone willing to build a perl module for me, perl-GD, and submit it to slackbuilds so that I can update shutter? The source can be found here: http://search.cpan.org/CPAN/authors/id/L/LD/LDS/GD-2.56.tar.gz I am the maintainer of shutter, the screenshot application. It is sorely outdated. However, I also have to build some new perl modules not yet available at slackbuilds.org, since shutter requires many perl modules with circular dependencies. Having said that, I am stuck on trying to build perl-GD. I have tried the perl module template provided by slackbuilds. I have tried altering it, Googling, and looking at how other distributions package it, but I cannot get it to package properly. If anyone is interested, one thing I have found is that you probably want to disable Build test since it is ostensibly error prone. See http://matrix.cpantesters.org/?dist=GD;os=linux;reports=1 If someone is interested and wants to build on what I have already done, I can send them a tarball including the README, info, etc. Also, if someone does submit a slackbuild could you send me the tarball so I can continue working on updating shutter and its dependencies? -- Regards, Donald Cooley From yalhcru at gmail.com Sun Aug 21 21:38:29 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 21 Aug 2016 17:38:29 -0400 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> Message-ID: On 8/21/16, unix_lists at f-m.fm wrote: > Is someone willing to build a perl module for me, perl-GD, and submit > it to slackbuilds so that I can update shutter? I'll take you up on that. > If anyone is interested, one thing I have found is that you probably > want to disable Build test since it is ostensibly error prone. See > http://matrix.cpantesters.org/?dist=GD;os=linux;reports=1 Yeah, the tests fail for me. I kinda want to find out why before I submit this. > Also, if someone does submit a slackbuild could you send me the tarball > so I can continue working on updating shutter and its dependencies? Here's what I've got so far: http://urchlay.naptime.net/~urchlay/src/perl-GD.tar.gz It builds, and "perl -MGD -e 1" runs successfully, meaning the module is found and loaded by perl. TAG is set to NonSBo in that build, so you won't forget it's not a real SBo build (yet). From thomas at beingboiled.info Sun Aug 21 21:51:15 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Sun, 21 Aug 2016 23:51:15 +0200 (CEST) Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> Message-ID: On Sun, 21 Aug 2016, unix_lists at f-m.fm wrote: > Is someone willing to build a perl module for me, perl-GD, and submit > it to slackbuilds so that I can update shutter? I do NOT want to become the maintainer of perl-GD, but I do know its pitfalls, so I prepared a SlackBuild for anyone willing to pick it up, see attachment. Just insert your name and e-mail address :-) Some notes... The tests don't work. The Makefile.PL doesn't work at all. The Build.PL will work but needs a patch because the use of Getopt renders the usual Build.PL options useless. My patch was made for Slackware 14.1 and also trims the required version down to 0.40 to work with what was a core module then, but since Module-Build is an external dependency now you can leave this out. I didn't have a need for the scripts and was too lazy to clean up $PKG/usr/bin, so I simply deleted it. As a careful maintainer you should not do that :-) Have fun! -- -------------- next part -------------- A non-text attachment was scrubbed... Name: perl-GD.tar.gz Type: application/octet-stream Size: 3816 bytes Desc: URL: From unix_lists at f-m.fm Sun Aug 21 22:22:12 2016 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Sun, 21 Aug 2016 17:22:12 -0500 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> Message-ID: <1471818132.3102152.701816201.0045B09D@webmail.messagingengine.com> On Sun, Aug 21, 2016, at 04:38 PM, B Watson wrote: > On 8/21/16, unix_lists at f-m.fm wrote: > > Is someone willing to build a perl module for me, perl-GD, and submit > > it to slackbuilds so that I can update shutter? > > I'll take you up on that. > > > If anyone is interested, one thing I have found is that you probably > > want to disable Build test since it is ostensibly error prone. See > > http://matrix.cpantesters.org/?dist=GD;os=linux;reports=1 > > Yeah, the tests fail for me. I kinda want to find out why before I submit > this. > > > Also, if someone does submit a slackbuild could you send me the tarball > > so I can continue working on updating shutter and its dependencies? > > Here's what I've got so far: > > http://urchlay.naptime.net/~urchlay/src/perl-GD.tar.gz > > It builds, and "perl -MGD -e 1" runs successfully, meaning the module > is found and loaded by perl. > > TAG is set to NonSBo in that build, so you won't forget it's not a real > SBo build (yet). Thanks so much for taking this on. It is very helpful. I'll look at it more tomorrow. -- Regards, Donald Cooley From yalhcru at gmail.com Sun Aug 21 22:45:14 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 21 Aug 2016 18:45:14 -0400 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: <1471818132.3102152.701816201.0045B09D@webmail.messagingengine.com> References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> <1471818132.3102152.701816201.0045B09D@webmail.messagingengine.com> Message-ID: On 8/21/16, unix_lists at f-m.fm wrote: > Thanks so much for taking this on. It is very helpful. I'll look at it > more tomorrow. I found out why 'Build test' is failing. It's using freetype, rendering a truetype font into an image, and then comparing pixel-for-pixel to a reference image. The results aren't *exactly* pixel-for-pixel identical, so the test fails... although I can't see the differences when I look at them side-by-side in an image viewer. Could be the result of the author using a different version of freetype, or freetype being built with different CFLAGS on his system, or minor differences in floating point on my CPU vs his CPU, that sort of thing. About to submit perl-GD to SBo with a patch that disables just that one test, the rest of them pass just fine. From unix_lists at f-m.fm Sun Aug 21 23:16:10 2016 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Sun, 21 Aug 2016 18:16:10 -0500 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> Message-ID: <1471821370.3109772.701843833.336E0CE7@webmail.messagingengine.com> On Sun, Aug 21, 2016, at 04:51 PM, Thomas Morper wrote: > On Sun, 21 Aug 2016, unix_lists at f-m.fm wrote: > > > Is someone willing to build a perl module for me, perl-GD, and submit > > it to slackbuilds so that I can update shutter? > > I do NOT want to become the maintainer of perl-GD, but I do know its > pitfalls, so I prepared a SlackBuild for anyone willing to pick it up, > see attachment. Just insert your name and e-mail address :-) > > Some notes... > > The tests don't work. > > The Makefile.PL doesn't work at all. Okay. I ran into these issues too. > The Build.PL will work but needs a patch because the use of Getopt > renders > the usual Build.PL options useless. No wonder I couldn't get this to build. Thanks for the confirmation. >My patch was made for Slackware 14.1 > and also trims the required version down to 0.40 to work with what was a > core module then, but since Module-Build is an external dependency now > you > can leave this out. > > I didn't have a need for the scripts and was too lazy to clean up > $PKG/usr/bin, so I simply deleted it. As a careful maintainer you should > not do that :-) > > Have fun! -- Regards, Donald Cooley From yalhcru at gmail.com Sun Aug 21 23:37:48 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 21 Aug 2016 19:37:48 -0400 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: <1471821370.3109772.701843833.336E0CE7@webmail.messagingengine.com> References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> <1471821370.3109772.701843833.336E0CE7@webmail.messagingengine.com> Message-ID: On 8/21/16, unix_lists at f-m.fm wrote: > On Sun, Aug 21, 2016, at 04:51 PM, Thomas Morper wrote: >> The Build.PL will work but needs a patch because the use of Getopt >> renders >> the usual Build.PL options useless. > > No wonder I couldn't get this to build. Thanks for the confirmation. Doesn't need a patch, just different options to Build. In fact the perl template on SBo needs to be updated. From thomas at beingboiled.info Mon Aug 22 00:31:11 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Mon, 22 Aug 2016 02:31:11 +0200 (CEST) Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> <1471821370.3109772.701843833.336E0CE7@webmail.messagingengine.com> Message-ID: On Sun, 21 Aug 2016, B Watson wrote: > Doesn't need a patch, just different options to Build. You're right. To my excuse: the use of "perl Build.PL --prefix ..." is documented and GD certainly breaks this. Thereafter I didn't investigate any further and simply patched. -- From yalhcru at gmail.com Mon Aug 22 01:47:40 2016 From: yalhcru at gmail.com (B Watson) Date: Sun, 21 Aug 2016 21:47:40 -0400 Subject: [Slackbuilds-users] perl-template needs updating Message-ID: This stuff: perl Build.PL \ prefix /usr \ installdirs vendor ./Build ./Build test ./Build install \ --destdir $PKG \ --install_path bindoc=/usr/man/man1 \ --install_path libdoc=/usr/man/man3 ...every time I've tried to use it, I get: Too early to specify a build action 'prefix'. Do 'Build prefix' instead. But this works: perl Build.PL ./Build ./Build test ./Build install \ --prefix /usr \ --installdirs vendor \ --destdir $PKG \ --install_path bindoc=/usr/man/man1 \ --install_path libdoc=/usr/man/man3 From andreas at andreasvoegele.com Mon Aug 22 06:53:40 2016 From: andreas at andreasvoegele.com (=?UTF-8?Q?Andreas_V=c3=b6gele?=) Date: Mon, 22 Aug 2016 08:53:40 +0200 Subject: [Slackbuilds-users] perl-template needs updating In-Reply-To: References: Message-ID: This works for distributions using Module::Build and Module::Build::Tiny: perl Build.PL \ --installdirs vendor \ --config installvendorman1dir=/usr/man/man1 \ --config installvendorman3dir=/usr/man/man3 ./Build ./Build test ./Build install --destdir $PKG For distributions using ExtUtils::MakeMaker: perl Makefile.PL \ INSTALLDIRS=vendor \ INSTALLVENDORMAN1DIR=/usr/man/man1 \ INSTALLVENDORMAN3DIR=/usr/man/man3 make make test make install DESTDIR=$PKG There is no need to specify both installdirs and prefix. I've built hundreds of Perl distributions with these commands (via my CPANPLUS::Dist::Slackware plugin). From yalhcru at gmail.com Mon Aug 22 15:42:12 2016 From: yalhcru at gmail.com (B Watson) Date: Mon, 22 Aug 2016 11:42:12 -0400 Subject: [Slackbuilds-users] perl-template needs updating In-Reply-To: References: Message-ID: On 8/22/16, Andreas V?gele wrote: > This works for distributions using Module::Build and > Module::Build::Tiny: > > perl Build.PL \ > --installdirs vendor \ > --config installvendorman1dir=/usr/man/man1 \ > --config installvendorman3dir=/usr/man/man3 > ./Build > ./Build test > ./Build install --destdir $PKG > > For distributions using ExtUtils::MakeMaker: > > perl Makefile.PL \ > INSTALLDIRS=vendor \ > INSTALLVENDORMAN1DIR=/usr/man/man1 \ > INSTALLVENDORMAN3DIR=/usr/man/man3 > make > make test > make install DESTDIR=$PKG > > There is no need to specify both installdirs and prefix. > > I've built hundreds of Perl distributions with these commands (via my > CPANPLUS::Dist::Slackware plugin). OK, I've only done SlackBuilds for 3 or 4, so I'll definitely bow to your experience. So, do you agree that the template code at https://slackbuilds.org/templates/perl-template.SlackBuild is broken? From baildon.research at googlemail.com Mon Aug 22 22:20:55 2016 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 22 Aug 2016 23:20:55 +0100 Subject: [Slackbuilds-users] perl-template needs updating In-Reply-To: References: Message-ID: > So, do you agree that the template code at > https://slackbuilds.org/templates/perl-template.SlackBuild is broken? I'm not an expert, but it wouldn't surprise me if the answer was Yes. When we were doing the big update for 14.2, Matteo pointed out that every SlackBuild using "Build method #2" was broken because Module::Build was removed from the perl 5.22 core. So, if new upstream versions were available that used "Build method #1", we updated them. Otherwise, we added perl-Module-Build as a dependency. But we forgot to update the perl template to say that "Build method #1" is now preferred, and "Build method #2" now requires perl-Module-Build. So if everyone agrees with Andreas' suggestions, I'll post a draft revised perl template here for discussion, and then we can get that merged. Thanks to everyone for working together to solve this problem! -D. From unix_lists at f-m.fm Tue Aug 23 03:03:59 2016 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Mon, 22 Aug 2016 22:03:59 -0500 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date Message-ID: <1471921439.3406080.703133489.20180E83@webmail.messagingengine.com> On Sun, Aug 21, 2016, at 04:38 PM, B Watson wrote: > > Here's what I've got so far: > > http://urchlay.naptime.net/~urchlay/src/perl-GD.tar.gz > > It builds, and "perl -MGD -e 1" runs successfully, meaning the module > is found and loaded by perl. > > TAG is set to NonSBo in that build, so you won't forget it's not a real > SBo build (yet). I was successfully able to build perl-Data-Random (another dependency for dropbox support for shutter). Thanks Mr. Watson. -- Regards, Donald Cooley From duncan_roe at acslink.net.au Tue Aug 23 03:16:45 2016 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Tue, 23 Aug 2016 13:16:45 +1000 Subject: [Slackbuilds-users] My new submission was rejected by mx.partnerconsole.net In-Reply-To: <73ffdf23-46df-d297-cbe5-6f264d9c787a@iinet.net.au> References: <20160821030115.GA5739@dimstar.local.net> <73ffdf23-46df-d297-cbe5-6f264d9c787a@iinet.net.au> Message-ID: <20160823031644.GA6005@dimstar.local.net> On Sun, Aug 21, 2016 at 04:03:07PM +1000, Christoph Willing wrote: > On 21/08/16 13:01, Duncan Roe wrote: > > Hi, > > > > On trying to upload a new package, I received > > > > > duncan_roe at acslink.net.au was rejected by mx.partnerconsole.net. > > > Go back and enter a valid E-Mail address. > > > > but that's my subscribed address. What's happening? > > Pointing a browser at acslink.net.au produces a page from netregistry.com.au > saying: > > "acslink.net.au is a parked domain > > The owner of this domain has yet to point it to a website or online content. > This means that the domain is parked." > (then more related stuff) > > Also, > whois acslink.net.au > shows that ns{1-3}.partnerconsole.net are DNS servers for that domain. > Therefore rejection by mx.partnerconsole.net would imply some problem with > the registration or configuration of the domain. > > chris > Hi Chris, Thank you for your reply. The "parked domain" stuff is OK I think. acslink.net.au is exclusively for email, no need for any web content. The output from "whois" is correct AFAICS. I never tried that command before - thanks for mentioning it. The thing that puzzles me is: the MX records for acslink.net.au point to partnerconsole.net but email headers always show mail coming via netregistry.net. I am raising a ticket with the domain owner, Cheers ... Duncan. From duncan_roe at acslink.net.au Tue Aug 23 03:42:51 2016 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Tue, 23 Aug 2016 13:42:51 +1000 Subject: [Slackbuilds-users] My new submission was rejected by mx.partnerconsole.net In-Reply-To: <92f6eca5-8ec7-7c41-27e5-70432e9a5543@grindcore.ch> References: <20160821030115.GA5739@dimstar.local.net> <92f6eca5-8ec7-7c41-27e5-70432e9a5543@grindcore.ch> Message-ID: <20160823034251.GB6005@dimstar.local.net> On Sun, Aug 21, 2016 at 09:12:12AM +0200, Beni wrote: > On 08/21/2016 05:01 AM, Duncan Roe wrote: > > Hi, > > > > On trying to upload a new package, I received > > > >> duncan_roe at acslink.net.au was rejected by mx.partnerconsole.net. > >> Go back and enter a valid E-Mail address. > > > > but that's my subscribed address. What's happening? > > I had the same problem once. In my case the reason was that the > mailserver uses graylisting as a method to defend spam. This leads to it > refusing the first connection of a unknown remote mailserver and waiting > for it to try a second time. Most spam bots won't try again. > > Unfortunately the script that checks e-mail addresses on Slackbuilds > uses this first connection to check whether a email is valid. The only > way I had to solve this was to use another address. You you have this > option, you could try to deactivate graylisting. > > Beni > _______________________________________________ Hi Beni, Thank you for your reply. I have encountered the "refusing the first connection of a unknown remote mailserver" syndrome in the past, and not just the first connection either. My ISP has multiple server hosts and each seems ignorant of what any of the others has already bounced. That's how it seems from the outside anyway, but they won't confirm it of course. Or the problem may be that the Slackbuilds email checker believes the MX records. These point to partnerconsole.net but email headers always show mail coming via netregistry.net. I have no idea how this works but it seems to, most of the time. I am raising a ticket with the domain owner, Cheers ... Duncan. From slackbuilds at schoepfer.info Tue Aug 23 07:22:04 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 23 Aug 2016 09:22:04 +0200 Subject: [Slackbuilds-users] My new submission was rejected by mx.partnerconsole.net In-Reply-To: <20160823034251.GB6005@dimstar.local.net> References: <20160821030115.GA5739@dimstar.local.net> <92f6eca5-8ec7-7c41-27e5-70432e9a5543@grindcore.ch> <20160823034251.GB6005@dimstar.local.net> Message-ID: <28879d741cdae9dce17f40e191440ef3@schoepfer.info> > Or the problem may be that the Slackbuilds email checker believes the > MX > records. These point to partnerconsole.net but email headers always > show mail > coming via netregistry.net. I have no idea how this works but it seems > to, most > of the time. > > I am raising a ticket with the domain owner, I assume your problem is solved if your provider disables greylisting/postscreen pregreet checks for 208.94.238.114(slackbuild submission confirm mails come from here). IPs of mx-records and sending mta don't have to be the same, most big providers have diffrent receiving and sending IPs. Johannes From erik at slackbuilds.org Tue Aug 23 15:43:52 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 23 Aug 2016 10:43:52 -0500 Subject: [Slackbuilds-users] My new submission was rejected by mx.partnerconsole.net In-Reply-To: <20160823034251.GB6005@dimstar.local.net> References: <20160821030115.GA5739@dimstar.local.net> <92f6eca5-8ec7-7c41-27e5-70432e9a5543@grindcore.ch> <20160823034251.GB6005@dimstar.local.net> Message-ID: <20160823104352.0ee878d3@shaggy.doo> On Tue, 23 Aug 2016 13:42:51 +1000 Duncan Roe wrote: > Or the problem may be that the Slackbuilds email checker believes the > MX records. These point to partnerconsole.net but email headers > always show mail coming via netregistry.net. I have no idea how this > works but it seems to, most of the time. > > I am raising a ticket with the domain owner, That is the best course of action. The submission form does what any MTA does, looks up the MX record for the @domain part of the address, connects to that server and "asks" if it's willing to accept messages for the address that was entered into the submission form. As an additional note, the address you enter on the submission form isn't tied to anything. It doesn't have the be the one you've subscribed to the -users list with, or match the one in the .info file. It's not even stored anywhere. It's used once to send you an upload confirmation email, and is included in the "new submission" notification that admins get. This is necessary because some people prefer to obfuscate their address in the .info file, making sending that confirmation impossible. We also have instances of people trying to bump or take over scripts that don't belong to them. Without their address, we can't contact them to ask if they have permission, etc. -- Erik From vlahavas at gmail.com Tue Aug 23 16:58:02 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Tue, 23 Aug 2016 19:58:02 +0300 (EEST) Subject: [Slackbuilds-users] mono SlackBuild problems Message-ID: Hi, I have noticed a couple of problems with the mono SlackBuild. While it works OK in 64bits, that is not the case for 32bits. Not sure, but probably these problems were introduced during the latest update. 1. For some weird reason, when setting ARCH=i586, it uses SLKCFLAGS="-O2 -march=i686 -mtune=i686" instead of SLKCFLAGS="-O2 -march=i586 -mtune=i686" 2. It uses a precompiled tarball of mono to build the package and this is named like this in the SlackBuild: $PRGNAM-$BIN_VERSION-$ARCH.tar.bz2 The problem is that the tarball is specifically named: mono-4.2.2.10-i486.tar.bz2 so $ARCH cannot be substituted in the filename, because it then becomes: mono-4.2.2.10-i586.tar.bz2 which is a tarball that does not exist. Because of that, the SlackBuild fails. This should be hardcoded to i486 whenever ARCH is set to i?86. Regards, George From willysr at slackbuilds.org Tue Aug 23 23:47:46 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 24 Aug 2016 06:47:46 +0700 Subject: [Slackbuilds-users] mono SlackBuild problems In-Reply-To: References: Message-ID: > 1. For some weird reason, when setting ARCH=i586, it uses > SLKCFLAGS="-O2 -march=i686 -mtune=i686" > instead of > SLKCFLAGS="-O2 -march=i586 -mtune=i686" See here https://slackbuilds.org/cgit/slackbuilds/commit/?id=0e00044ed979dfe857f147ab51bf4597a6d62a28 -- 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 Aug 24 00:07:55 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 24 Aug 2016 07:07:55 +0700 Subject: [Slackbuilds-users] mono SlackBuild problems In-Reply-To: References: Message-ID: <2ce4ce41-afaa-0b72-70a8-6f8e55b2e2fb@slackbuilds.org> > 2. It uses a precompiled tarball of mono to build the package and this > is named like this in the SlackBuild: $PRGNAM-$BIN_VERSION-$ARCH.tar.bz2 > > The problem is that the tarball is specifically named: > mono-4.2.2.10-i486.tar.bz2 > > so $ARCH cannot be substituted in the filename, because it then becomes: > mono-4.2.2.10-i586.tar.bz2 > which is a tarball that does not exist. Because of that, the SlackBuild > fails. This should be hardcoded to i486 whenever ARCH is set to i?86. Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From vlahavas at gmail.com Wed Aug 24 06:21:52 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Wed, 24 Aug 2016 09:21:52 +0300 (EEST) Subject: [Slackbuilds-users] mono SlackBuild problems In-Reply-To: References: Message-ID: On Wed, 24 Aug 2016, Willy Sudiarto Raharjo wrote: >> 1. For some weird reason, when setting ARCH=i586, it uses >> SLKCFLAGS="-O2 -march=i686 -mtune=i686" >> instead of >> SLKCFLAGS="-O2 -march=i586 -mtune=i686" > > See here > https://slackbuilds.org/cgit/slackbuilds/commit/?id=0e00044ed979dfe857f147ab51bf4597a6d62a28 OK, but I just built it in 14.2 with -O2 -march=i585 -mtune=i686 and there were no problems. I guess the gcc bug has been fixed. From willysr at slackbuilds.org Wed Aug 24 08:05:34 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 24 Aug 2016 15:05:34 +0700 Subject: [Slackbuilds-users] mono SlackBuild problems In-Reply-To: References: Message-ID: > OK, but I just built it in 14.2 with > -O2 -march=i585 -mtune=i686 > and there were no problems. I guess the gcc bug has been fixed. It should be fixed by now, but it won't hurt to leave it as it is -- 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 vlahavas at gmail.com Wed Aug 24 08:08:10 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Wed, 24 Aug 2016 11:08:10 +0300 Subject: [Slackbuilds-users] mono SlackBuild problems In-Reply-To: References: Message-ID: ???? 24 ??? 2016 11:01 ??, ? ??????? "Willy Sudiarto Raharjo" < willysr at slackbuilds.org> ??????: > > > OK, but I just built it in 14.2 with > > -O2 -march=i585 -mtune=i686 > > and there were no problems. I guess the gcc bug has been fixed. > > It should be fixed by now, but it won't hurt to leave it as it is People with an i586-only CPU might disagree with that. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Diamond at acadiau.ca Wed Aug 24 13:42:05 2016 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Wed, 24 Aug 2016 10:42:05 -0300 Subject: [Slackbuilds-users] shutter not working in 14.2: patch to fix it In-Reply-To: <20160717161548.GA8699@jdiamond-nb.acadiau.ca> References: <20160717161548.GA8699@jdiamond-nb.acadiau.ca> Message-ID: <20160824134205.GA3864@jdiamond-nb.acadiau.ca> On Sun, Jul 17, 2016 at 13:15 (-0300), Jim Diamond wrote: > Hi, > when I try to run shutter in S64-14.2 I get > Can't use 'defined(@array)' (Maybe you should just omit the defined()?) at /usr/bin/shutter line 3557. Perhaps everyone else has figured this out by now, but as much as I hate touching perl code, I found that the following changes seem to make perl happy. At least, so far it runs and I haven't seen a problem. Any perl gurus here may wish to improve my changes. $ diff /usr/bin/shutter /usr/bin/shutter.s-dist 3557c3557 < if($n_items && defined $key && defined $session_screens{$key} && @{$session_screens{$key}->{'undo'}} && scalar @{$session_screens{$key}->{'undo'}} > 1){ --- > if($n_items && defined $key && defined @{$session_screens{$key}->{'undo'}} && scalar @{$session_screens{$key}->{'undo'}} > 1){ 3562,3563c3562,3563 < < if($n_items && defined $key && defined $session_screens{$key} && $session_screens{$key}->{'redo'} && scalar @{$session_screens{$key}->{'redo'}} > 0){ --- > > if($n_items && defined $key && defined @{$session_screens{$key}->{'redo'}} && scalar @{$session_screens{$key}->{'redo'}} > 0){ Perhaps this patch could be incorporated into the slackbuild until a new version of shutter is available at SBo? Cheers. Jim From willysr at slackbuilds.org Wed Aug 24 14:02:05 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 24 Aug 2016 21:02:05 +0700 Subject: [Slackbuilds-users] mono SlackBuild problems In-Reply-To: References: Message-ID: <08c40ad1-517f-09ff-c1bc-4b0a37afbf94@slackbuilds.org> >>> OK, but I just built it in 14.2 with >>> -O2 -march=i585 -mtune=i686 >>> and there were no problems. I guess the gcc bug has been fixed. >> >> It should be fixed by now, but it won't hurt to leave it as it is > > People with an i586-only CPU might disagree with that. reverted back to 586 on x86 -- 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 1.41421 at gmail.com Wed Aug 24 19:24:39 2016 From: 1.41421 at gmail.com (JCA) Date: Wed, 24 Aug 2016 13:24:39 -0600 Subject: [Slackbuilds-users] gtkglext won't build for Slackware64 14.2 Message-ID: This is what I am getting: (cd .libs && rm -f libgtkglext-x11-1.0.so && ln -s libgtkglext-x11-1.0.so.0.0.0 libgtkglext-x11-1.0.so) creating libgtkglext-x11-1.0.la (cd .libs && rm -f libgtkglext-x11-1.0.la && ln -s ../libgtkglext-x11-1.0.la libgtkglext-x11-1.0.la) make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/gtk' Making all in m4macros make[2]: Entering directory '/tmp/SBo/gtkglext-1.2.0/m4macros' rm -f gtkglext-1.0.m4 && cp gtkglext.m4 gtkglext-1.0.m4 make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/m4macros' Making all in docs make[2]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs' Making all in reference make[3]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs/reference' Making all in gtkglext make[4]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs/reference/gtkglext' *** Scanning header files *** if grep -l '^..*$' ./gtkglext.types > /dev/null ; then \ CC="/bin/sh ../../../libtool --mode=compile gcc" LD="/bin/sh ../../../libtool --mode=link gcc" CFLAGS="-O2 -fPIC -Wall -I../../.. -I../../../gdk -I../../../gtk -I../../../gdk -I../../../gtk -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/pango-1.0 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/harfbuzz -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include" LDFLAGS="../../../gdk/libgdkglext-x11-1.0.la ../../../gtk/libgtkglext-x11-1.0.la" gtkdoc-scangobj --module=gtkglext --output-dir=. ; \ else \ cd . ; \ for i in gtkglext.args gtkglext.hierarchy gtkglext.interfaces gtkglext.prerequisites gtkglext.signals ; do \ test -f $i || touch $i ; \ done \ fi /usr/lib/libXext.so: error adding symbols: File in wrong format collect2: error: ld returned 1 exit status Linking of scanner failed: Makefile:494: recipe for target 'scan-build.stamp' failed make[4]: *** [scan-build.stamp] Error 1 make[4]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs/reference/gtkglext' Makefile:260: recipe for target 'all-recursive' failed make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs/reference' Makefile:260: recipe for target 'all-recursive' failed make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs' Makefile:363: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/gtkglext-1.2.0' Makefile:279: recipe for target 'all' failed make: *** [all] Error 2 From thedoogster at gmail.com Wed Aug 24 19:29:00 2016 From: thedoogster at gmail.com (Doogster) Date: Wed, 24 Aug 2016 12:29:00 -0700 Subject: [Slackbuilds-users] gtkglext won't build for Slackware64 14.2 In-Reply-To: References: Message-ID: The error looks like the one covered here: https://slackbuilds.org/faq/#multilib On Wed, Aug 24, 2016 at 12:24 PM, JCA <1.41421 at gmail.com> wrote: > This is what I am getting: > > (cd .libs && rm -f libgtkglext-x11-1.0.so && ln -s > libgtkglext-x11-1.0.so.0.0.0 libgtkglext-x11-1.0.so) > creating libgtkglext-x11-1.0.la > (cd .libs && rm -f libgtkglext-x11-1.0.la && ln -s > ../libgtkglext-x11-1.0.la libgtkglext-x11-1.0.la) > make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/gtk' > Making all in m4macros > make[2]: Entering directory '/tmp/SBo/gtkglext-1.2.0/m4macros' > rm -f gtkglext-1.0.m4 && cp gtkglext.m4 gtkglext-1.0.m4 > make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/m4macros' > Making all in docs > make[2]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs' > Making all in reference > make[3]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs/reference' > Making all in gtkglext > make[4]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs/reference/gtkglext' > *** Scanning header files *** > if grep -l '^..*$' ./gtkglext.types > /dev/null ; then \ > CC="/bin/sh ../../../libtool --mode=compile gcc" LD="/bin/sh > ../../../libtool --mode=link gcc" CFLAGS="-O2 -fPIC -Wall -I../../.. > -I../../../gdk -I../../../gtk -I../../../gdk -I../../../gtk > -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -pthread > -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include > -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 > -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 > -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 > -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/libpng16 -I/usr/include/pango-1.0 > -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/freetype2 -I/usr/include/libpng16 > -I/usr/include/harfbuzz -I/usr/include/glib-2.0 > -I/usr/lib64/glib-2.0/include" > LDFLAGS="../../../gdk/libgdkglext-x11-1.0.la > ../../../gtk/libgtkglext-x11-1.0.la" gtkdoc-scangobj > --module=gtkglext --output-dir=. ; \ > else \ > cd . ; \ > for i in gtkglext.args gtkglext.hierarchy gtkglext.interfaces > gtkglext.prerequisites gtkglext.signals ; do \ > test -f $i || touch $i ; \ > done \ > fi > /usr/lib/libXext.so: error adding symbols: File in wrong format > collect2: error: ld returned 1 exit status > Linking of scanner failed: > Makefile:494: recipe for target 'scan-build.stamp' failed > make[4]: *** [scan-build.stamp] Error 1 > make[4]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs/reference/gtkglext' > Makefile:260: recipe for target 'all-recursive' failed > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs/reference' > Makefile:260: recipe for target 'all-recursive' failed > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs' > Makefile:363: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/gtkglext-1.2.0' > Makefile:279: recipe for target 'all' failed > make: *** [all] Error 2 > _______________________________________________ > 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 1.41421 at gmail.com Wed Aug 24 19:38:32 2016 From: 1.41421 at gmail.com (JCA) Date: Wed, 24 Aug 2016 13:38:32 -0600 Subject: [Slackbuilds-users] gtkglext won't build for Slackware64 14.2 In-Reply-To: References: Message-ID: Yes, that fixed the build. Thank you. On Wed, Aug 24, 2016 at 1:29 PM, Doogster wrote: > The error looks like the one covered here: > > https://slackbuilds.org/faq/#multilib > > On Wed, Aug 24, 2016 at 12:24 PM, JCA <1.41421 at gmail.com> wrote: >> This is what I am getting: >> >> (cd .libs && rm -f libgtkglext-x11-1.0.so && ln -s >> libgtkglext-x11-1.0.so.0.0.0 libgtkglext-x11-1.0.so) >> creating libgtkglext-x11-1.0.la >> (cd .libs && rm -f libgtkglext-x11-1.0.la && ln -s >> ../libgtkglext-x11-1.0.la libgtkglext-x11-1.0.la) >> make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/gtk' >> Making all in m4macros >> make[2]: Entering directory '/tmp/SBo/gtkglext-1.2.0/m4macros' >> rm -f gtkglext-1.0.m4 && cp gtkglext.m4 gtkglext-1.0.m4 >> make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/m4macros' >> Making all in docs >> make[2]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs' >> Making all in reference >> make[3]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs/reference' >> Making all in gtkglext >> make[4]: Entering directory '/tmp/SBo/gtkglext-1.2.0/docs/reference/gtkglext' >> *** Scanning header files *** >> if grep -l '^..*$' ./gtkglext.types > /dev/null ; then \ >> CC="/bin/sh ../../../libtool --mode=compile gcc" LD="/bin/sh >> ../../../libtool --mode=link gcc" CFLAGS="-O2 -fPIC -Wall -I../../.. >> -I../../../gdk -I../../../gtk -I../../../gdk -I../../../gtk >> -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -pthread >> -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include >> -I/usr/include/pango-1.0 -I/usr/include/gtk-2.0 >> -I/usr/lib64/gtk-2.0/include -I/usr/include/pango-1.0 >> -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 >> -I/usr/include/libdrm -I/usr/include/gdk-pixbuf-2.0 >> -I/usr/include/libpng16 -I/usr/include/pango-1.0 >> -I/usr/include/freetype2 -I/usr/include/libpng16 >> -I/usr/include/freetype2 -I/usr/include/libpng16 >> -I/usr/include/harfbuzz -I/usr/include/glib-2.0 >> -I/usr/lib64/glib-2.0/include" >> LDFLAGS="../../../gdk/libgdkglext-x11-1.0.la >> ../../../gtk/libgtkglext-x11-1.0.la" gtkdoc-scangobj >> --module=gtkglext --output-dir=. ; \ >> else \ >> cd . ; \ >> for i in gtkglext.args gtkglext.hierarchy gtkglext.interfaces >> gtkglext.prerequisites gtkglext.signals ; do \ >> test -f $i || touch $i ; \ >> done \ >> fi >> /usr/lib/libXext.so: error adding symbols: File in wrong format >> collect2: error: ld returned 1 exit status >> Linking of scanner failed: >> Makefile:494: recipe for target 'scan-build.stamp' failed >> make[4]: *** [scan-build.stamp] Error 1 >> make[4]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs/reference/gtkglext' >> Makefile:260: recipe for target 'all-recursive' failed >> make[3]: *** [all-recursive] Error 1 >> make[3]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs/reference' >> Makefile:260: recipe for target 'all-recursive' failed >> make[2]: *** [all-recursive] Error 1 >> make[2]: Leaving directory '/tmp/SBo/gtkglext-1.2.0/docs' >> Makefile:363: recipe for target 'all-recursive' failed >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory '/tmp/SBo/gtkglext-1.2.0' >> Makefile:279: recipe for target 'all' failed >> make: *** [all] Error 2 >> _______________________________________________ >> 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 1.41421 at gmail.com Wed Aug 24 19:46:19 2016 From: 1.41421 at gmail.com (JCA) Date: Wed, 24 Aug 2016 13:46:19 -0600 Subject: [Slackbuilds-users] qcomicbook link does not exist Message-ID: The link to the qcomicbook sources, at http://qcomicbook.org/releases/qcomicbook-0.9.0.tar.gz does not exist any more. From matteo.bernardini at gmail.com Wed Aug 24 19:54:05 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 24 Aug 2016 21:54:05 +0200 Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: 2016-08-24 21:46 GMT+02:00 JCA <1.41421 at gmail.com>: > The link to the qcomicbook sources, at > > http://qcomicbook.org/releases/qcomicbook-0.9.0.tar.gz > > does not exist any more. you can find it also here http://ponce.cc/slackware/sources/repo/qcomicbook-0.9.0.tar.gz Matteo From 1.41421 at gmail.com Wed Aug 24 19:58:25 2016 From: 1.41421 at gmail.com (JCA) Date: Wed, 24 Aug 2016 13:58:25 -0600 Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: Thanks. I actually installed it from the AlienBob's repositories. I just wanted to make the Slackbuilds admins aware of the issue. On Wed, Aug 24, 2016 at 1:54 PM, Matteo Bernardini wrote: > 2016-08-24 21:46 GMT+02:00 JCA <1.41421 at gmail.com>: >> The link to the qcomicbook sources, at >> >> http://qcomicbook.org/releases/qcomicbook-0.9.0.tar.gz >> >> does not exist any more. > > you can find it also here > > http://ponce.cc/slackware/sources/repo/qcomicbook-0.9.0.tar.gz > > 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 matteo.bernardini at gmail.com Wed Aug 24 20:03:44 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 24 Aug 2016 22:03:44 +0200 Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: 2016-08-24 21:58 GMT+02:00 JCA <1.41421 at gmail.com>: > Thanks. I actually installed it from the AlienBob's repositories. I > just wanted to make the Slackbuilds admins aware of the issue. thanks to you for reporting! I have already updated it on my git branch and will go in the next public update https://slackbuilds.org/cgit/slackbuilds/commit/?id=47251c6e488807d50ae53d5f92098150aabd0096 Matteo From 1.41421 at gmail.com Wed Aug 24 20:19:55 2016 From: 1.41421 at gmail.com (JCA) Date: Wed, 24 Aug 2016 14:19:55 -0600 Subject: [Slackbuilds-users] sbsigntools link not working Message-ID: The link to the sbsigntools sources in Slackbuilds for 14.2 seems to be password-protected: --2016-08-24 14:16:47-- https://build.opensuse.org/source/home:jejb1:UEFI/sbsigntools/sbsigntools-0.7.tar.gz Resolving build.opensuse.org (build.opensuse.org)... 195.135.221.133, 2001:67c:2178:8::12 Connecting to build.opensuse.org (build.opensuse.org)|195.135.221.133|:443... connected. HTTP request sent, awaiting response... 401 Unauthorized Username/Password Authentication Failed. From matteo.bernardini at gmail.com Wed Aug 24 21:03:34 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 24 Aug 2016 23:03:34 +0200 Subject: [Slackbuilds-users] sbsigntools link not working In-Reply-To: References: Message-ID: 2016-08-24 22:19 GMT+02:00 JCA <1.41421 at gmail.com>: > The link to the sbsigntools sources in Slackbuilds for 14.2 seems > to be password-protected: > > --2016-08-24 14:16:47-- > https://build.opensuse.org/source/home:jejb1:UEFI/sbsigntools/sbsigntools-0.7.tar.gz > Resolving build.opensuse.org (build.opensuse.org)... 195.135.221.133, > 2001:67c:2178:8::12 > Connecting to build.opensuse.org > (build.opensuse.org)|195.135.221.133|:443... connected. > HTTP request sent, awaiting response... 401 Unauthorized > > Username/Password Authentication Failed. thanks for reporting: you can use http://ponce.cc/slackware/sources/repo/ccan-0.0.2.tar.gz http://ponce.cc/slackware/sources/repo/sbsigntools-0.7.tar.gz Matteo From unix_lists at f-m.fm Thu Aug 25 01:16:56 2016 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Wed, 24 Aug 2016 20:16:56 -0500 Subject: [Slackbuilds-users] shutter not working in 14.2: patch to fix it In-Reply-To: <20160824134205.GA3864@jdiamond-nb.acadiau.ca> References: <20160717161548.GA8699@jdiamond-nb.acadiau.ca> <20160824134205.GA3864@jdiamond-nb.acadiau.ca> Message-ID: <1472087816.571863.705380953.4F48899F@webmail.messagingengine.com> On Wed, Aug 24, 2016, at 08:42 AM, Jim Diamond wrote: > On Sun, Jul 17, 2016 at 13:15 (-0300), Jim Diamond wrote: > > > Hi, > > > when I try to run shutter in S64-14.2 I get > > Can't use 'defined(@array)' (Maybe you should just omit the defined()?) at /usr/bin/shutter line 3557. > > Perhaps everyone else has figured this out by now, but as much as I > hate touching perl code, I found that the following changes seem to make > perl happy. At least, so far it runs and I haven't seen a problem. > Any perl gurus here may wish to improve my changes. > > $ diff /usr/bin/shutter /usr/bin/shutter.s-dist > 3557c3557 > < if($n_items && defined $key && defined > $session_screens{$key} && @{$session_screens{$key}->{'undo'}} && scalar > @{$session_screens{$key}->{'undo'}} > 1){ > --- > > if($n_items && defined $key && defined @{$session_screens{$key}->{'undo'}} && scalar @{$session_screens{$key}->{'undo'}} > 1){ > 3562,3563c3562,3563 > < > < if($n_items && defined $key && defined > $session_screens{$key} && $session_screens{$key}->{'redo'} && scalar > @{$session_screens{$key}->{'redo'}} > 0){ > --- > > > > if($n_items && defined $key && defined @{$session_screens{$key}->{'redo'}} && scalar @{$session_screens{$key}->{'redo'}} > 0){ > > > Perhaps this patch could be incorporated into the slackbuild until a > new version of shutter is available at SBo? > > Cheers. > > Jim Hey Jim. I'll be submitting the latest stable version of shutter available very soon. -- Regards, Donald Cooley From vlahavas at gmail.com Thu Aug 25 09:06:14 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Thu, 25 Aug 2016 12:06:14 +0300 (EEST) Subject: [Slackbuilds-users] faust.SlackBuild problem Message-ID: Hi, in the faust.SlackBuild, $ARCH is never set. You'll need to add something like this close to the top: if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) ARCH=i586 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac fi Regards, George From vlahavas at gmail.com Thu Aug 25 09:09:42 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Thu, 25 Aug 2016 12:09:42 +0300 (EEST) Subject: [Slackbuilds-users] faust.SlackBuild problem In-Reply-To: References: Message-ID: On Thu, 25 Aug 2016, George Vlahavas wrote: > Hi, > > in the faust.SlackBuild, $ARCH is never set. You'll need to add something > like this close to the top: > > if [ -z "$ARCH" ]; then > case "$( uname -m )" in > i?86) ARCH=i586 ;; > arm*) ARCH=arm ;; > *) ARCH=$( uname -m ) ;; > esac > fi > > Regards, > > George > Actually there are more problems with it. CFLAGS are never set properly and libraries get installed under /usr/lib in 64bit systems... From matteo.bernardini at gmail.com Thu Aug 25 09:25:00 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 25 Aug 2016 11:25:00 +0200 Subject: [Slackbuilds-users] faust.SlackBuild problem In-Reply-To: References: Message-ID: 2016-08-25 11:09 GMT+02:00 George Vlahavas : > > On Thu, 25 Aug 2016, George Vlahavas wrote: > >> Hi, >> >> in the faust.SlackBuild, $ARCH is never set. You'll need to add something >> like this close to the top: >> >> if [ -z "$ARCH" ]; then >> case "$( uname -m )" in >> i?86) ARCH=i586 ;; >> arm*) ARCH=arm ;; >> *) ARCH=$( uname -m ) ;; >> esac >> fi >> >> Regards, >> >> George >> > > Actually there are more problems with it. CFLAGS are never set properly and > libraries get installed under /usr/lib in 64bit systems... hi George, please check the attached patch (I'll put the maintainer in cc). Matteo -------------- next part -------------- --- ./faust.SlackBuild.orig 2016-08-24 12:02:28.086919485 +0200 +++ ./faust.SlackBuild 2016-08-25 11:20:55.579483919 +0200 @@ -24,14 +24,36 @@ PRGNAM=faust VERSION=${VERSION:-0.9.58} -BUILD=${BUILD:-1} +BUILD=${BUILD:-2} TAG=${TAG:-_SBo} +if [ -z "$ARCH" ]; then + case "$( uname -m )" in + i?86) ARCH=i586 ;; + arm*) ARCH=arm ;; + *) ARCH=$( uname -m ) ;; + esac +fi + CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} +if [ "$ARCH" = "i586" ]; then + SLKCFLAGS="-O2 -march=i586 -mtune=i686" + LIBDIRSUFFIX="" +elif [ "$ARCH" = "i686" ]; then + SLKCFLAGS="-O2 -march=i686 -mtune=i686" + LIBDIRSUFFIX="" +elif [ "$ARCH" = "x86_64" ]; then + SLKCFLAGS="-O2 -fPIC" + LIBDIRSUFFIX="64" +else + SLKCFLAGS="-O2" + LIBDIRSUFFIX="" +fi + set -e rm -rf $PKG @@ -43,10 +65,48 @@ unzip $CWD/$PRGNAM-$VERSION.zip chown -R root:root . find -L . \ - \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 511 \) \ - -exec chmod 755 {} \; -o \ - \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ - -exec chmod 644 {} \; + \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ + -o -perm 511 \) -exec chmod 755 {} \; -o \ + \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ + -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; + +# Add some fixes (thanks to the fedora folks!) +# For installation in the correct location and for preserving timestamps: +# The Makefile normally puts noarch files in $prefix/lib. We change +# this to $prefix/share +sed -i \ + -e 's|/lib/|/share/|g' \ + -e 's| -r | -pr |' \ + -e 's| -m | -pm |' \ + Makefile +sed -i 's|/lib|/share|g' compiler/parser/enrobage.cpp +sed -i 's|install |install -pm 755 |' tools/faust2appls/Makefile + +# Fix optflags +sed -i "s|-O3|$SLKCFLAGS|" \ + compiler/Makefile.unix \ + architecture/osclib/faust/Makefile \ + architecture/osclib/oscpack/Makefile + +# Fix permissions +chmod -x compiler/draw/device/SVGDev.* architecture/VST/PkgInfo +chmod +x tools/faust2appls/faust2* +chmod -x tools/faust2pd/faust2* + +# Fix encoding +for i in examples syntax-highlighting; do + iconv -f iso8859-1 -t utf8 $i/README -o tmpfile + touch -r $i/README tmpfile + mv -f tmpfile $i/README +done + +# To distinguish doc files +for i in changelog license readme; do + mv architecture/osclib/faust/$i.txt architecture/osclib/faust/$i.faustOSC.txt +done +for i in CHANGES LICENSE README TODO; do + mv architecture/osclib/oscpack/$i architecture/osclib/oscpack/$i.osscpack.txt +done make PREFIX=/usr DESTDIR=$PKG make install PREFIX=/usr DESTDIR=$PKG From vlahavas at gmail.com Thu Aug 25 09:52:05 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Thu, 25 Aug 2016 12:52:05 +0300 (EEST) Subject: [Slackbuilds-users] faust.SlackBuild problem In-Reply-To: References: Message-ID: On Thu, 25 Aug 2016, Matteo Bernardini wrote: > 2016-08-25 11:09 GMT+02:00 George Vlahavas : >> >> On Thu, 25 Aug 2016, George Vlahavas wrote: >> >>> Hi, >>> >>> in the faust.SlackBuild, $ARCH is never set. You'll need to add something >>> like this close to the top: >>> >>> if [ -z "$ARCH" ]; then >>> case "$( uname -m )" in >>> i?86) ARCH=i586 ;; >>> arm*) ARCH=arm ;; >>> *) ARCH=$( uname -m ) ;; >>> esac >>> fi >>> >>> Regards, >>> >>> George >>> >> >> Actually there are more problems with it. CFLAGS are never set properly and >> libraries get installed under /usr/lib in 64bit systems... > > hi George, > > please check the attached patch (I'll put the maintainer in cc). > > Matteo > Thanks Matteo. Seems to work, but I think there are still a couple of static libraries put in /usr/share/faust/. There are several .cpp source files in there too and I'm not sure if they are supposed to be there in the package. From matteo.bernardini at gmail.com Thu Aug 25 10:01:17 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 25 Aug 2016 12:01:17 +0200 Subject: [Slackbuilds-users] faust.SlackBuild problem In-Reply-To: References: Message-ID: 2016-08-25 11:52 GMT+02:00 George Vlahavas : > > On Thu, 25 Aug 2016, Matteo Bernardini wrote: > >> 2016-08-25 11:09 GMT+02:00 George Vlahavas : >>> >>> >>> On Thu, 25 Aug 2016, George Vlahavas wrote: >>> >>>> Hi, >>>> >>>> in the faust.SlackBuild, $ARCH is never set. You'll need to add >>>> something >>>> like this close to the top: >>>> >>>> if [ -z "$ARCH" ]; then >>>> case "$( uname -m )" in >>>> i?86) ARCH=i586 ;; >>>> arm*) ARCH=arm ;; >>>> *) ARCH=$( uname -m ) ;; >>>> esac >>>> fi >>>> >>>> Regards, >>>> >>>> George >>>> >>> >>> Actually there are more problems with it. CFLAGS are never set properly >>> and >>> libraries get installed under /usr/lib in 64bit systems... >> >> >> hi George, >> >> please check the attached patch (I'll put the maintainer in cc). >> >> Matteo >> > > Thanks Matteo. Seems to work, but I think there are still a couple of static > libraries put in /usr/share/faust/. There are several .cpp source files in > there too and I'm not sure if they are supposed to be there in the package. it seems the fedora people have a patch also for that but it's for an older version of faust and doesn't apply to the new one, it has to be rewritten http://pkgs.fedoraproject.org/cgit/rpms/faust.git/plain/faust-osclib-shared.patch then also the make commands must be adapted for that adding LIBDIR and INCLUDEDIR statements http://pkgs.fedoraproject.org/cgit/rpms/faust.git/plain/faust.spec let's hear from the maintainer about it. Matteo From Jim.Diamond at acadiau.ca Thu Aug 25 11:28:46 2016 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Thu, 25 Aug 2016 08:28:46 -0300 Subject: [Slackbuilds-users] shutter not working in 14.2: patch to fix it In-Reply-To: <1472087816.571863.705380953.4F48899F@webmail.messagingengine.com> References: <20160717161548.GA8699@jdiamond-nb.acadiau.ca> <20160824134205.GA3864@jdiamond-nb.acadiau.ca> <1472087816.571863.705380953.4F48899F@webmail.messagingengine.com> Message-ID: <20160825112846.GB13083@jdiamond-nb.acadiau.ca> On Wed, Aug 24, 2016 at 20:16 (-0500), unix_lists at f-m.fm wrote: > Hey Jim. I'll be submitting the latest stable version of shutter > available very soon. Donald, that's great news. Thanks for your efforts. Jim From thomas at beingboiled.info Thu Aug 25 12:16:40 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Thu, 25 Aug 2016 14:16:40 +0200 (CEST) Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: On Wed, 24 Aug 2016, Matteo Bernardini wrote: > I have already updated it on my git branch and will go in the next public update > https://slackbuilds.org/cgit/slackbuilds/commit/?id=47251c6e488807d50ae53d5f92098150aabd0096 While you're at it, do you want to add... # Icon info in the desktop file should not have a file extension. sed -i 's/\.png$//' data/qcomicbook.desktop ...to the SlackBuild? It's just a cosmetical fix to get rid of the warning message when starting qcomicbook from the terminal. -- From matteo.bernardini at gmail.com Thu Aug 25 12:41:41 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 25 Aug 2016 14:41:41 +0200 Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: 2016-08-25 14:16 GMT+02:00 Thomas Morper : > On Wed, 24 Aug 2016, Matteo Bernardini wrote: > >> I have already updated it on my git branch and will go in the next public update >> https://slackbuilds.org/cgit/slackbuilds/commit/?id=47251c6e488807d50ae53d5f92098150aabd0096 > > While you're at it, do you want to add... > > # Icon info in the desktop file should not have a file extension. > sed -i 's/\.png$//' data/qcomicbook.desktop > > ...to the SlackBuild? It's just a cosmetical fix to get rid of the warning > message when starting qcomicbook from the terminal. that's strange: I just have this warning starting qcomicbook from the terminal here libpng warning: iCCP: known incorrect sRGB profile but it doesn't go away removing the png extension from the name of the icon in the desktop file and also the icon is showing fine in the menu (lxpanel)... Matteo From yalhcru at gmail.com Thu Aug 25 17:22:14 2016 From: yalhcru at gmail.com (B Watson) Date: Thu, 25 Aug 2016 13:22:14 -0400 Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: On 8/25/16, Matteo Bernardini wrote: > that's strange: I just have this warning starting qcomicbook from the > terminal here > > libpng warning: iCCP: known incorrect sRGB profile > > but it doesn't go away removing the png extension from the name of the > icon in the desktop file and also the icon is showing fine in the menu > (lxpanel)... A lot of stuff does that in 14.2, and it's not caused by having a .png extension in the .desktop file. It's not only Slackware, either: http://stackoverflow.com/questions/22745076/libpng-warning-iccp-known-incorrect-srgb-profile From audrius at neutrino.lt Thu Aug 25 19:59:21 2016 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Thu, 25 Aug 2016 22:59:21 +0300 Subject: [Slackbuilds-users] Request to remove obsolete build scripts Message-ID: <20160825195921.GA7504@varna> Hi, Could admins please remove the following obsolete build scripts? network/node (replaced by development/nodejs) python/pep8 (replaced by python/pycodestyle) Thanks. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From ryan.q at linux.com Thu Aug 25 20:06:33 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 25 Aug 2016 13:06:33 -0700 Subject: [Slackbuilds-users] Request to remove obsolete build scripts In-Reply-To: <20160825195921.GA7504@varna> References: <20160825195921.GA7504@varna> Message-ID: On Thursday, August 25, 2016, Audrius Ka?ukauskas audrius at neutrino.lt wrote: Hi, > > Could admins please remove the following obsolete build scripts? > > network/node (replaced by development/nodejs) > Piggybacking on this one, network/iojs may as well be removed also. ? -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricardo at palmtx.com.ar Thu Aug 25 20:48:56 2016 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Thu, 25 Aug 2016 17:48:56 -0300 Subject: [Slackbuilds-users] Request to remove obsolete build scripts In-Reply-To: <20160825195921.GA7504@varna> References: <20160825195921.GA7504@varna> Message-ID: <201608251748.56638.ricardo@palmtx.com.ar> El Jueves 25/08/2016, Audrius Ka?ukauskas escribi?: > Hi, > > Could admins please remove the following obsolete build scripts? > > network/node (replaced by development/nodejs) > python/pep8 (replaced by python/pycodestyle) > > Thanks. FYI, autopep8 still depends on pep8. On github they mention pycodestyle as a requirement but on pypi.python.org they require pep8, which is actually true: $ slp autopep8 autopep8-1.2.4-x86_64-1_SBo $ autopep8 --in-place --aggressive --aggressive test.py Traceback (most recent call last): File "/usr/bin/autopep8", line 5, in from pkg_resources import load_entry_point File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2927, in @_call_aside File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2913, in _call_aside f(*args, **kwargs) File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 2940, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 635, in _build_master ws.require(__requires__) File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 943, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib64/python2.7/site-packages/pkg_resources/__init__.py", line 829, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'pep8>=1.5.7' distribution was not found and is required by autopep8 Cheers, -- 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 ricardo at palmtx.com.ar Thu Aug 25 21:02:25 2016 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Thu, 25 Aug 2016 18:02:25 -0300 Subject: [Slackbuilds-users] Request to remove obsolete build scripts In-Reply-To: <20160825195921.GA7504@varna> References: <20160825195921.GA7504@varna> Message-ID: <201608251802.25571.ricardo@palmtx.com.ar> El Jueves 25/08/2016, Audrius Ka?ukauskas escribi?: > Hi, > > Could admins please remove the following obsolete build scripts? > > network/node (replaced by development/nodejs) > python/pep8 (replaced by python/pycodestyle) > > Thanks. Also, these should be updated to depend on nodejs, right?: $ ag "REQUIRES.*\bnode\b" /var/lib/sbopkg/SBo/14.2/*/*/*.info /var/lib/sbopkg/SBo/14.2/development/npm2tgz/npm2tgz.info 8:REQUIRES="node" /var/lib/sbopkg/SBo/14.2/network/etherpad-lite/etherpad-lite.info 8:REQUIRES="node" /var/lib/sbopkg/SBo/14.2/network/keybase-client/keybase-client.info 8:REQUIRES="node" Cheers, -- 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 thomas at beingboiled.info Thu Aug 25 22:21:41 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Fri, 26 Aug 2016 00:21:41 +0200 (CEST) Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: On Thu, 25 Aug 2016, Matteo Bernardini wrote: > that's strange: I just have this warning starting qcomicbook from the > terminal here > > libpng warning: iCCP: known incorrect sRGB profile That's interesting. I don't get a libpng warning message on Slackware 14.2. I get a different libpng warning message on Slackware 14.1 (never seen this before). I don't get a warning message on either regarding the desktop file. I've definitely seen this on 14.1 but can't reproduce it any longer. However, checking with "desktop-file-validate" confirms: /usr/share/applications/qcomicbook.desktop: error: (will be fatal in the future): value "qcomicbook.png" for key "Icon" in group "Desktop Entry" is an icon name with an extension, but there should be no extension as described in the Icon Theme Specification if the value is not an absolute path -- From d.zlatanidis at gmail.com Fri Aug 26 02:22:23 2016 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Fri, 26 Aug 2016 05:22:23 +0300 Subject: [Slackbuilds-users] Request to remove obsolete build scripts In-Reply-To: <20160825195921.GA7504@varna> References: <20160825195921.GA7504@varna> Message-ID: Hi, python/autopep8 still uses pep8 as dependency, until version 2.0 release. On 08/25/2016 10:59 PM, Audrius Ka?ukauskas wrote: > Hi, > > Could admins please remove the following obsolete build scripts? > > network/node (replaced by development/nodejs) > python/pep8 (replaced by python/pycodestyle) > > 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Fri Aug 26 04:34:13 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 26 Aug 2016 06:34:13 +0200 Subject: [Slackbuilds-users] chmod 0644 of /etc/rc.d/rc.*.new in SlackBuild Message-ID: <91a8a52f-c44a-bc40-0e2c-8dd7846f5794@gmail.com> Hi, In the example file: https://slackbuilds.org/slackbuilds/14.2/network/sshguard/sshguard.SlackBuild there is: chmod 0644 $PKG/etc/rc.d/rc.$PRGNAM.new I would say it's not necessary, because probably for that exact reason (assuming the default mandatory umask of 022 when building a package) we are using 'cat', which will make the cat'ed file 0644 by default. Is that correct? -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Fri Aug 26 05:43:25 2016 From: yalhcru at gmail.com (B Watson) Date: Fri, 26 Aug 2016 01:43:25 -0400 Subject: [Slackbuilds-users] qcomicbook link does not exist In-Reply-To: References: Message-ID: On 8/25/16, Thomas Morper wrote: >> libpng warning: iCCP: known incorrect sRGB profile > > /usr/share/applications/qcomicbook.desktop: error: (will be fatal in the > future): value "qcomicbook.png" for key "Icon" in group "Desktop Entry" is > an icon name with an extension, but there should be no extension as > described in the Icon Theme Specification if the value is not an absolute > path 2 separate issues. [note: everywhere you see me running qcomicbook from the $ prompt, I closed the qcomicbook window right after it appeared] $ qcomicbook libpng warning: iCCP: known incorrect sRGB profile $ sudo rm /usr/share/applications/qcomicbook.desktop $ qcomicbook libpng warning: iCCP: known incorrect sRGB profile The libpng error isn't due to the .desktop file warning, in other words (it happens even if I rm the desktop file). Furthermore, it still happens without the icon: $ sudo rm /usr/share/pixmaps/qcomicbook.png $ qcomicbook libpng warning: iCCP: known incorrect sRGB profile ...no surprise there actually, most applications don't bother to load their own icon (it's there for the window manager or desktop env). So I tried: $ strace -f -ostrace.out qcomicbook libpng warning: iCCP: known incorrect sRGB profile $ grep png strace.out 10616 open("/usr/lib64/qt/lib/libpng16.so.16", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) 10616 open("/usr/lib64/libpng16.so.16", O_RDONLY|O_CLOEXEC) = 3 10616 write(2, "libpng warning: iCCP: known inco"..., 51) = 51 What does that mean? Means it's *not* loading a .png file from the disk. If it were, there would have been a call like 'open("filename.png", O_RDONLY) = 3'. So what's going on here? $ find /tmp/SBo/qcomicbook-0.9.0/ -name \*.png /tmp/SBo/qcomicbook-0.9.0/data/nextframe.png /tmp/SBo/qcomicbook-0.9.0/data/qcomicbook.png /tmp/SBo/qcomicbook-0.9.0/data/fitwidth.png ... 27 more data/*.png files, not pasted here... The icons for the GUI elements in the program are PNG files, and they're most likely being compiled into the program somehow (since they don't end up installed as part of the .tgz package). So I added this to qcomicbook.SlackBuild, just before the 'cmake' command: for i in data/*.png; do mv $i $i.old.png convert $i.old.png $i rm $i.old.png done ...following the advice from the previously-mentioned stackexchange thread, to use "convert old.png new.png" to get rid of the bogus sRGB profile. After building & installing: $ qcomicbook $ Bingo, no more libpng warnings. I dunno if the maintainer will consider this worth adding to his SlackBuild, the libpng warnings are harmless anyway. From zhu.qunying at gmail.com Fri Aug 26 20:18:32 2016 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 26 Aug 2016 13:18:32 -0700 Subject: [Slackbuilds-users] xdelta download path not valid any more Message-ID: Hi, For the xdelta package, the original download link from google code is not valid any more. I found one from fedora: http://pkgs.fedoraproject.org/repo/pkgs/xdelta/xdelta-1.1.4.tar.gz/1b896c01ebf0e353b7e3c3071b05f496/xdelta-1.1.4.tar.gz -- Qun-Ying From willysr at slackbuilds.org Fri Aug 26 23:48:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 Aug 2016 06:48:39 +0700 Subject: [Slackbuilds-users] xdelta download path not valid any more In-Reply-To: References: Message-ID: <2531b674-7195-145a-9cb7-a549eb56e0ea@slackbuilds.org> > For the xdelta package, the original download link from google code is > not valid any more. I found one from fedora: > > http://pkgs.fedoraproject.org/repo/pkgs/xdelta/xdelta-1.1.4.tar.gz/1b896c01ebf0e353b7e3c3071b05f496/xdelta-1.1.4.tar.gz Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From dfc at warpmail.net Tue Aug 23 03:03:00 2016 From: dfc at warpmail.net (dfc at warpmail.net) Date: Mon, 22 Aug 2016 22:03:00 -0500 Subject: [Slackbuilds-users] Am trying to build a perl module, perl-gd, in order to bring shutter up-to-date In-Reply-To: References: <1471802693.3064662.701675785.7889145B@webmail.messagingengine.com> Message-ID: <1471921380.3405984.703127689.18B2656F@webmail.messagingengine.com> On Sun, Aug 21, 2016, at 04:38 PM, B Watson wrote: > On 8/21/16, unix_lists at f-m.fm wrote: > > Is someone willing to build a perl module for me, perl-GD, and submit > > it to slackbuilds so that I can update shutter? > > I'll take you up on that. > > > If anyone is interested, one thing I have found is that you probably > > want to disable Build test since it is ostensibly error prone. See > > http://matrix.cpantesters.org/?dist=GD;os=linux;reports=1 > > Yeah, the tests fail for me. I kinda want to find out why before I submit > this. > > > Also, if someone does submit a slackbuild could you send me the tarball > > so I can continue working on updating shutter and its dependencies? > > Here's what I've got so far: > > http://urchlay.naptime.net/~urchlay/src/perl-GD.tar.gz > > It builds, and "perl -MGD -e 1" runs successfully, meaning the module > is found and loaded by perl. > > TAG is set to NonSBo in that build, so you won't forget it's not a real > SBo build (yet). I was successfully able to build perl-Data-Random (another dependency for dropbox support for shutter). Thanks Mr. Watson. From awakeyet at tutanota.de Fri Aug 26 23:32:55 2016 From: awakeyet at tutanota.de (awakeyet at tutanota.de) Date: Sat, 27 Aug 2016 00:32:55 +0100 (BST) Subject: [Slackbuilds-users] [Bug-gnuzilla] icecat 38.8.0 crashes In-Reply-To: <20160820221112.30fe3337@desktop.jensen.local> References: <> <1786691.mHFlXvMcxy@ithil> <<1786691.mHFlXvMcxy@ithil>> <20160817083518.GA24843@jensen.local> <> <20160820221112.30fe3337@desktop.jensen.local> Message-ID: I get what you mean, but alot of people out there aren't necessarily idiots, but rather they don't have a specialty in technology.? many people, even many who use free software rather have a simple firefox/icecat browser that just comes with the evil things removed and some good things added to protect them so that they have to do the minimal amount of set up to just get it working. if it doesn't "just werk" many people just throw it right in the trash and go to an easier option. what's so great about icecat is that it IS that easier option and it's also better for security than a normal firefox browser. take away the benefit to using it and it's just some boring browser that does nothing special at all. I'm absolutely not in any way at all suggesting we take away the choice or freedom from the user, but if all the good things about icecat are removed and most smart people (who aren't good in tech) have to spend 10 million frustrating headache hours pounding their head into their computer screen searching for answers on dead forums with spiderwebs in the corners and those weird mods who delete topics with answers to obsucure questions and failing to find any answers and? desperately trying to add those good things back into firefox, they will simply just stop using icecat out of frustration. smart people who can't figure out tech will just scream and cry at their computer screens in frustration as the very last FOSS minimalistic browser with some security features in existance becomes the "generic do-nothing browser" that already exists all over the internet in many different redundant and boring forms. there are loads of browsers out there already that do "nothing but browse" so why should we de-specialize icecat? why make it so normal that it's not worth using it? I love the fact that icecat is very minimalistic, but I'm very happy that it comes what it comes with and many others are too.? we shouldn't bloat icecat to death because look at what happened to mainstream firefox, but we shouldn't gut it to death until its a hollow shell that does nothing. -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com 20. Aug 2016 16:11 by hjensen at gmx.de: > Hi, > > On Thu, 18 Aug 2016 18:50:14 +0100 (BST) > <> awakeyet at tutanota.de> > wrote: > >> sounds really nice, but why would we want to pass along such strongly minimalistic >> "un-de-freedomed" browsers along to the normal people specifically without added security features? this basically lands them back right where they started since they are immediately washed clean and then re-exposed to the filth of the world again. we have to help them but "here don't go alone, take this!" without security- without defense there is nothing worth defending. > > I don't quite understand. A libre web browser does give people a > browser which does not download proprietary plugins without asking nor > suggest to install non-free Addons. Privacy aware search engines are > enabled by default. Why would this lead people back "to the > filth"? Users of free software are not stupid. > > I strongly believe that people must be offered complete free/libre > software. But we don't have to lecture them like children what the can > and can't do. This attitude will provoke contradiction. We can suggest > and recommend - but the choice should be freely made by the user. > > > Regards, > > Henry -------------- next part -------------- An HTML attachment was scrubbed... URL: From icaroperseo at riseup.net Sat Aug 27 01:37:45 2016 From: icaroperseo at riseup.net (Icaro Perseo) Date: Fri, 26 Aug 2016 20:37:45 -0500 Subject: [Slackbuilds-users] libkate-0.4.1 link not found 404 Message-ID: <20160827013745.GA27205@riseup.net> Hi, nice day! I found this error when trying to obtain the source code for buil the package. However, I found the link to project git repository: http://git.xiph.org/?p=users/oggk/kate.git;a=summary I hope it's useful. Best regards. -- Si deseas conocer qu? es GnuPG, su uso y aplicaciones te sugiero que visites la siguiente p?gina: https://emailselfdefense.fsf.org/es/ If you want to know what GnuPG is, its use and applications I suggest you visit the following page: https://emailselfdefense.fsf.org/ Fingerprint: 99F4 D957 9C0D 9552 73B9 34BA A453 EB5E 60A2 ADDC -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From ts at websafe.pl Sat Aug 27 02:20:58 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 27 Aug 2016 04:20:58 +0200 Subject: [Slackbuilds-users] KeePass.SlackBuild Message-ID: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> Hello. The current KeePass.SlackBuild makes it impossible to create SlackBuilds for KeePass plugins and extensions , because they should be placed in: /usr/lib/KeePass-${VERSION}/ And we can't really determine the version of Keepass a user has installed in an extension SlackBuild, can we? I think going this way would not really make sense. My suggestion is to install KeePass in /usr/lib/KeePass/ or just symlink /usr/lib/KeePass to /usr/lib/KeePass-${VERSION} in doinst.sh. This would make the creation of extension/plugin SlackBuilds easier, or better - possible. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sat Aug 27 04:32:42 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 Aug 2016 11:32:42 +0700 Subject: [Slackbuilds-users] libkate-0.4.1 link not found 404 In-Reply-To: <20160827013745.GA27205@riseup.net> References: <20160827013745.GA27205@riseup.net> Message-ID: > I found this error when trying to obtain the source code for buil the package. > However, I found the link to project git repository: > > http://git.xiph.org/?p=users/oggk/kate.git;a=summary Hi Fixed in my branch Thanks for reporting -- 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 sombragris at sombragris.org Sat Aug 27 01:34:14 2016 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Fri, 26 Aug 2016 21:34:14 -0400 Subject: [Slackbuilds-users] BUG: html5lib - source not found Message-ID: <0q93i.4047defa73.20160826213414.36bd3613@loli.sombragris.org> on the html5lib, the download link gives a 404 error (not found). It is possible to work around the issue by manually search on GitHub the relevant package (which turns out to be now html5lib-python-0.90), but it is not so trivial and not intuitive to do so by an inexperienced user. This is all the more relevant since html5lib is on the dependency chain for inkscape (inkscape depends on lxml which in turn depends on this package). Thanks and best regards, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== From willysr at slackbuilds.org Sat Aug 27 04:40:57 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 27 Aug 2016 11:40:57 +0700 Subject: [Slackbuilds-users] BUG: html5lib - source not found In-Reply-To: <0q93i.4047defa73.20160826213414.36bd3613@loli.sombragris.org> References: <0q93i.4047defa73.20160826213414.36bd3613@loli.sombragris.org> Message-ID: <0880c486-8009-742e-4209-db9f6936f7ed@slackbuilds.org> > on the html5lib, the download link gives a 404 error (not found). > > It is possible to work around the issue by manually search on GitHub > the relevant package (which turns out to be now html5lib-python-0.90), > but it is not so trivial and not intuitive to do so by an inexperienced > user. > > This is all the more relevant since html5lib is on the dependency chain > for inkscape (inkscape depends on lxml which in turn depends on this > package). it has been fixed on my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Sat Aug 27 07:39:35 2016 From: yalhcru at gmail.com (B Watson) Date: Sat, 27 Aug 2016 03:39:35 -0400 Subject: [Slackbuilds-users] KeePass.SlackBuild In-Reply-To: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> References: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> Message-ID: On 8/26/16, Thomas Szteliga wrote: > they should be placed in: > > /usr/lib/KeePass-${VERSION}/ > > > And we can't really determine the version of Keepass > a user has installed in an extension SlackBuild, can we? Never used KeePass, but to play the devil's advocate... Why not? There's surely a way for a shell script to determine the version number. Maybe by running 'KeePass --version' or similar, or maybe even by just looking for the existence of /usr/lib/KeePass-* and using cut or whatever to get the version number. Not saying that's a great idea, but it's at least possible... > My suggestion is to install KeePass in > > /usr/lib/KeePass/ > > or just symlink /usr/lib/KeePass to /usr/lib/KeePass-${VERSION} > in doinst.sh. > > This would make the creation of extension/plugin SlackBuilds > easier, or better - possible. Whether or not that's a good idea partly depends on whether compiled plugins are compatible from one KeePass version to another. If they are, then your idea sounds like the best answer. If they aren't, then the user's going to have to upgrade every plugin after upgrading KeePass anyway, and if it's like e.g. perl or older versions of irssi, trying to load an old/incompatible compiled module might cause the whole thing to segfault... Not being a KeePass user I can't answer that (looks like KeePass is written in C# and built with mono, so I don't know enough to even guess), but it's something you might want to investigate before making any final decisions. I haven't got a horse in this race though. From s.arcus at open-t.co.uk Sat Aug 27 18:19:50 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sat, 27 Aug 2016 19:19:50 +0100 Subject: [Slackbuilds-users] iPerf3 build script for testing Message-ID: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> Could I ask some kind souls here to test the iPerf3 scripts I've created, before uploading them to SBo, please. -------------- next part -------------- A non-text attachment was scrubbed... Name: iperf.tar.gz Type: application/gzip Size: 2618 bytes Desc: not available URL: From fernando.lopezjr at gmail.com Sat Aug 27 21:17:21 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 27 Aug 2016 15:17:21 -0600 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> Message-ID: send them. ill test. On Aug 27, 2016 12:20 PM, "Sebastian Arcus" wrote: > > Could I ask some kind souls here to test the iPerf3 scripts I've created, before uploading them to SBo, please. > > _______________________________________________ > 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 Sat Aug 27 21:56:43 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 27 Aug 2016 23:56:43 +0200 Subject: [Slackbuilds-users] qbs maintainer Message-ID: Hi, I've been trying to reach Nikos Giotis, the maintainer of qbs SlackBuild, without success. (Well, I sent him an e-mail on Friday, but the other one I sent him when we were switching from 14.1 to 14.2). If you know that he's no longer active, I would happily take over the maintenance of qbs. -- Best regards, Andrzej Telszewski From thedoogster at gmail.com Sat Aug 27 22:53:13 2016 From: thedoogster at gmail.com (Doogster) Date: Sat, 27 Aug 2016 15:53:13 -0700 Subject: [Slackbuilds-users] KeePass.SlackBuild In-Reply-To: References: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> Message-ID: I would have suggested adding a KEEPASS_VERSION option to the plugin's SlackBuild. On Sat, Aug 27, 2016 at 12:39 AM, B Watson wrote: > On 8/26/16, Thomas Szteliga wrote: > >> they should be placed in: >> >> /usr/lib/KeePass-${VERSION}/ >> >> >> And we can't really determine the version of Keepass >> a user has installed in an extension SlackBuild, can we? > > Never used KeePass, but to play the devil's advocate... > > Why not? There's surely a way for a shell script to determine the version > number. Maybe by running 'KeePass --version' or similar, or maybe even > by just looking for the existence of /usr/lib/KeePass-* and using cut > or whatever to get the version number. Not saying that's a great idea, > but it's at least possible... > >> My suggestion is to install KeePass in >> >> /usr/lib/KeePass/ >> >> or just symlink /usr/lib/KeePass to /usr/lib/KeePass-${VERSION} >> in doinst.sh. >> >> This would make the creation of extension/plugin SlackBuilds >> easier, or better - possible. > > Whether or not that's a good idea partly depends on whether compiled > plugins are compatible from one KeePass version to another. If they are, > then your idea sounds like the best answer. If they aren't, then the > user's going to have to upgrade every plugin after upgrading KeePass > anyway, and if it's like e.g. perl or older versions of irssi, trying > to load an old/incompatible compiled module might cause the whole thing > to segfault... > > Not being a KeePass user I can't answer that (looks like KeePass > is written in C# and built with mono, so I don't know enough to even > guess), but it's something you might want to investigate before making > any final decisions. > > I haven't got a horse in this race though. > _______________________________________________ > 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 atelszewski at gmail.com Sat Aug 27 23:05:53 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 28 Aug 2016 01:05:53 +0200 Subject: [Slackbuilds-users] KeePass.SlackBuild In-Reply-To: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> References: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> Message-ID: <9855fca7-af2b-396a-84a4-4725684cc5f5@gmail.com> On 27/08/16 04:20, Thomas Szteliga wrote: > > My suggestion is to install KeePass in > > /usr/lib/KeePass/ I would vote for this solution, which seems to be the rather standard way here on SBo. So why brake it? The user itself has to know that he might need to rebuild the plugins after upgrading the main application. This sometimes happens to me, when I need to rebuild a few dependent packages, after I upgraded python3. For example :-) -- Best regards, Andrzej Telszewski From ts at websafe.pl Sat Aug 27 23:34:11 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 28 Aug 2016 01:34:11 +0200 Subject: [Slackbuilds-users] KeePass.SlackBuild In-Reply-To: References: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> Message-ID: On 27.08.2016 09:39, B Watson wrote: > On 8/26/16, Thomas Szteliga wrote: >> they should be placed in: >> /usr/lib/KeePass-${VERSION}/ >> And we can't really determine the version of Keepass >> a user has installed in an extension SlackBuild, can we? > Never used KeePass, but to play the devil's advocate... > Why not? There's surely a way for a shell script to determine the version > number. Maybe by running 'KeePass --version' or similar, or maybe even > by just looking for the existence of /usr/lib/KeePass-* and using cut > or whatever to get the version number. Not saying that's a great idea, > but it's at least possible... Sure, in a SlackBuild that's possible, but in a packaged binary not really. I'm not saying that's not possible, but how should we then name the plugin packages? keepasshttp-for-keepass-2.30.... ? and what about automated upgrades? This is why I think that's not the best way. > Whether or not that's a good idea partly depends on whether compiled > plugins are compatible from one KeePass version to another. If they are, > then your idea sounds like the best answer. If they aren't, then the > user's going to have to upgrade every plugin after upgrading KeePass > anyway, and if it's like e.g. perl or older versions of irssi, trying > to load an old/incompatible compiled module might cause the whole thing > to segfault... > Not being a KeePass user I can't answer that (looks like KeePass > is written in C# and built with mono, so I don't know enough to even > guess), but it's something you might want to investigate before making > any final decisions. Plugins for Keepass2 should be compatible with all 2.x versions. Plugins don't need to be compiled, they come mostly in the form of a plgx file: "PLGX is an optional plugin file format for KeePass ? 2.09. Instead of compiling your plugin to a DLL assembly, the plugin source code files can be packed into a PLGX file and KeePass will compile the plugin itself when loading it. The advantage of this approach is that plugins don't need to be recompiled by the plugin developers for each KeePass release anymore (as KeePass compiles the plugin itself, the generated plugin assembly references the current, correct KeePass assembly). Instead of shipping a plugin DLL assembly, you ship the PLGX." Plugin example: https://github.com/pfn/keepasshttp In the readme for keepasshttp you can find: "Non-Windows / Manual Windows installation 1. Download KeePassHttp 2. Copy it into the KeePass directory + default directory in Ubuntu14.04: /usr/lib/keepass2/ + default directory in Arch: /usr/share/keepass" -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sat Aug 27 23:43:15 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 28 Aug 2016 01:43:15 +0200 Subject: [Slackbuilds-users] KeePass.SlackBuild In-Reply-To: References: <61501ed9-bfc2-4a43-12fe-27d842395c55@websafe.pl> Message-ID: <2741e041-d686-c6b2-fe91-61186e0f9758@websafe.pl> On 28.08.2016 00:53, Doogster wrote: > I would have suggested adding a KEEPASS_VERSION option to the plugin's > SlackBuild. OK, but I don't see how this would solve the problem? Short example: Keepass v.2.30 Plugin: KeePassHttp v. 1.8.4.1 How would you name the compiled plugin package and not make tools like slackpkg/slpkg to go crazy when upgrading? As I mentioned in my previous post, other distributions have "normal" locations, like: Centos: /usr/lib/keepass Arch: /usr/share/keepass Ubuntu: /usr/lib/keepass2 -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From idlemoor at slackbuilds.org Sun Aug 28 00:16:25 2016 From: idlemoor at slackbuilds.org (David Spencer) Date: Sun, 28 Aug 2016 01:16:25 +0100 Subject: [Slackbuilds-users] Updates 20160827.1 Message-ID: <2106a313-9b31-ff95-8078-0cab99d4decc@slackbuilds.org> It's been another busy week -- thanks to everybody who contributed! Sat Aug 27 23:37:49 UTC 2016 academic/mendeleydesktop: Updated for version 1.16.2. academic/scipy3: Added (python library). academic/scipy: Updated for version 0.18.0. academic/veusz: Updated for version 1.24. accessibility/unclutter: Fix host.def issue. audio/abcde: Updated for version 2.7.2. audio/kid3: Updated for version 3.4.2. audio/python-audiotools: Updated for version 3.1.1. audio/qmmp: Updated for version 0.10.3. audio/snd: Updated for version 16.7. desktop/ambiance-radiance-flat-colors-gtk-theme: Added (gtk theme). desktop/areao43-icon-theme: Added (icon theme). desktop/florence: Added (virtual keyboard). desktop/glabels: Removed APPROVED line. desktop/gtk-theme-Albatross: Added (Desktop Suite for Xfce). desktop/gtk-theme-Blackbird: Added (Dark Desktop Suite for Xfce). desktop/gtk-theme-Bluebird: Added (Desktop Suite for Xfce). desktop/gtk-theme-Greybird: Added (Desktop Suite for Xfce). desktop/gtk-theme-Orion: Added (modern light theme). desktop/i3lock: Added (simple screen locker). desktop/lumina: Updated for version 1.0.0-p2 & xinitrc fix. desktop/pekwm: Update script. desktop/sawfish: Updated for version 1.12.0. desktop/wmwebcam: New maintainer, minor fixes. desktop/xdgurl: Added (install helper program for desktop stuff). desktop/xfce4-embed-plugin: Updated for version 1.6.0. desktop/xtrlock: Fix host.def issue. development/GitEye: Added (Desktop Git Client). development/THE: Fix html documentation. development/atom: Updated for version 1.9.9. development/cycler: Added (composable cycles in python). development/flow: Updated for version 0.31.0. development/google-go-lang: Updated for version 1.7. development/hhvm: Updated for version 3.14.5. development/mono: Fix source arch on x86. development/monodevelop-database: Removed (no longer build). development/monodevelop: Updated for version 6.0.2.73. development/neovim: Updated for version 0.1.5. development/numpy-legacy3: Added (a Python extension). development/numpy-legacy: Updated to match ATLAS version. development/numpy3: Updated for version 1.11.1 development/numpy: Updated for version 1.11.1. development/perf: Updated for version 4.4.19. development/pycharm: Updated for version 2016.2.2. development/pyenchant: Updated for version 1.6.8. development/sbcl: Updated for version 1.3.8. development/simulavr: Updated for version git20160221. development/uncrustify: Updated for version 0.63. development/universal-ctags: Updated for version f2d8a3d. games/angband: i486 -> i586. games/atanks: i486 -> i586. games/commandergenius: Added (engine for Commander Keen games). games/fuse-emulator: Updated for version 1.2.2. games/koules: Fix host.def issue. games/moria: i486 -> i586. games/rogue: i486 -> i586, update DOWNLOAD. games/stone_soup: i486 -> i586. games/tome: i486 -> i586. games/xmahjongg: Added (xmahjongg: Xmahjongg). gis/CreateCloudMap: Updated for version 0.8.0. gis/GMT: Updated for gshhg-gmt-2.3.6. gis/mapnik: Updated for version 3.0.10. gis/qgis: Updated for version 2.16.2. graphics/fig2sxd: Updated for version 0.22.1. graphics/kuickshow: i486 -> i586. graphics/pngcrush: Updated for version 1.8.4. graphics/qcomicbook: Fixed downlad link. graphics/shutter: Updated for version 0.93.1. graphics/simple-scan: Aded (simple scanning utility). graphics/xmedcon: Updated for version 0.14.1. libraries/DateTime: Updated for version 4.1.1. libraries/PySoundCard: Updated for version 0.5.2. libraries/SFML: Updated for version 2.4.0. libraries/afflib: Updated for version 3.7.7. libraries/atlas: Updated for version 3.10.3. libraries/bamf: Updated for version 0.5.3. libraries/botocore: Updated for version 1.4.48. libraries/console_bridge: Added (Robot OS Library). libraries/goffice: Updated for version 0.10.32. libraries/grantlee-qt5: Added (template engine written in Qt5). libraries/grx: i486 -> i586. libraries/html5lib: Update DOWNLOAD url. libraries/lapack-atlas: Updated for version 3.6.1. libraries/libbde: Updated for version 20160731. libraries/libburn: Updated for version 1.4.4. libraries/libesedb: Updated for version 20160622. libraries/libevt: Updated for version 20160421. libraries/libevtx: Updated for version 20160421. libraries/libewf: Updated for version 20140608. libraries/libfastjson: Added (a fork from json-c). libraries/libfsntfs: Added (libYAL NTFS library). libraries/libfvde: Added (libYAL FvDE volume library). libraries/libfwnt: Added (library to access Windows NT data types). libraries/libisoburn: Updated for version 1.4.4. libraries/libisofs: Updated for version 1.4.4. libraries/libkate: Update DOWNLOAD url. libraries/liblightgrep: Update DOWNLOAD, i486->i586. libraries/liblnk: Updated for version 20160420. libraries/libmsiecf: Updated for version 20160813. libraries/libolecf: Updated for version 20160814. libraries/libregf: Updated for version 20160424. libraries/librelp: Updated for version 1.2.12. libraries/libsmraw: Updated for version 20160424. libraries/libspectrum: Updated for version 1.2.2. libraries/libvslvm: Added (libYAL Linux LVM library). libraries/live555: Updated for version 2016.08.27 libraries/matplotlibs: Updated for version 1.5.2. libraries/pcre2: Added (Perl 5-style regular exprs. 2nd version). libraries/pies2overrides: Updated for version 2.6.7. libraries/pies: Updated for version 2.6.7. libraries/protobuf-c: Added (Protocol Buffers in C). libraries/ptypes: Added (C++ Portable Types Library). libraries/pylast: Update script and HOMEPAGE. libraries/python-xlrd: Updated for version 1.0.0. libraries/tbb: Updated for version 4.4u5. libraries/urdfdom: Added (Robot Format Header). libraries/urdfdom_headers: Added (Robot Description Format headers). libraries/uuid: Added (OSSP Universally Unique Identifier). libraries/vigra: Updated for version 1.11.0. misc/mosquitto: Updated for version 1.4.10 misc/ramdefrag: Added (so-called Memory Defragmenter). misc/subsurface: Updated for version 4.5.6. misc/xdelta: Update DOWNLOAD url. multimedia/kodi: Updated for version 16.1 network/PAC: Added (Perl Auto Connector). network/PySocks: Added (Python SOCKS client module). network/awscli: Updated for version 1.10.58. network/bitcoin: Updated for version 0.13.0. network/chrony: Updated for version 2.4. network/dianara: Added (Pump.io client written using Qt4). network/fail2ban: Updated for version 0.9.5. network/filezilla: Updated for version 3.21.0. network/flexget: Updated for version 2.3.3. network/movgrab: Updated for version 1.2.1. network/nethogs: Updated for version 0.8.5. network/openfortivpn: Added (PPP+SSL VPN tunnel client). network/pentadactyl: Updated for version 20160824. network/pure-ftpd: Updated for version 1.0.43. network/tcpflow: Added (data capture). network/telegram: Updated for version 0.10.1. network/trojita: Updated for version 0.7. network/vivaldi: Updated for version 1.3.551.38. network/you-get: Updated for version 0.4.536. network/youtube-dl: Updated for version 2016.08.22. office/CherryTree: Updated for version 0.37.4. office/calibre: Updated for version 2.65.1 office/gnumeric: Updated for version 1.12.32. office/hamster: Added (Gnome time tracker). office/hevea: Updated for version 2.29. perl/Gtk2-GladeXML: Added (perl bindings for Glade 2.x). perl/perl-Crypt-OpenSSL-Bignum: i486 -> i586. perl/perl-Crypt-OpenSSL-DSA: Added (DSA using OpenSSL). perl/perl-Crypt-OpenSSL-EC: Added (OpenSSL EC extension). perl/perl-Crypt-OpenSSL-ECDSA: Added (perl extn for OpenSSL ECDSA). perl/perl-Crypt-OpenSSL-RSA: i486 -> i586. perl/perl-Crypt-OpenSSL-Random: Updated for version 0.11. perl/perl-Data-Random: Added (Perl module to generate random data). perl/perl-Digest-GOST: Added (perl module Digest::GOST). perl/perl-Expect: Added (perl module). perl/perl-GD: Added (perl bindings for GD image library). perl/perl-Gnome2-Vte: Added (perl module Gnome2::Vte). perl/perl-Gtk2-Ex-Simple-List: Added (perl module). perl/perl-IO-Socket-Timeout: Added (IO::Socket::Timeout). perl/perl-IO-Stty: Added (perl module IO::Stty). perl/perl-IO-Tty: Updated for version 1.12. perl/perl-MailTools: Updated for version 2.18. perl/perl-Net-ARP: Added (Perl extension for creating ARP packets). perl/perl-Net-DNS-SEC: Added (DNSSEC extensions to Net::DNS). perl/perl-PerlIO-via-Timeout: Added (PerlIO::via::Timeout). perl/perl-Test-SharedFork: Updated for version 0.35. perl/perl-Test-TCP: Updated for version 2.17. perl/perl-extutils-makemaker: Updated for version 7.24. python/Flask-Cors: Updated for version 3.0.0. python/XlsxWriter: Added (write Excel 2007+ XLSX files). python/artifacts: Added (ForensicArtifacts.com Artifact Repository). python/binplist: Updated for version 0.1.5. python/colorclass: Added (ANSI color text library for Python). python/dfdatetime: Added (Digital Forensics Date and Time). python/dfvfs: Updated for version 20160108. python/distorm: Added (disassembler library). python/dulwich: Updated for version 0.14.1. python/hg-git: Updated for version 0.8.5. python/netifaces: Updated for version 0.10.5 python/pefile: Added (access Portable Executable files). python/pillowfight: Added (transition from PIL to Pillow). python/pip: Updated for version 8.1.2. python/pipdeptree: Updated for version 0.7.0. python/plaso: Updated for version 1.4.0. python/prompt_toolkit: Updated for version 1.0.7. python/pybluez: Fix download link. python/pyparsing: Updated for version 2.1.8. python/pyqode.qt: Fix .info file. python/pyresample: Updated for version 1.2.5. python/pytest: Updated for version 3.0.0. python/pytsk: Updated for version 20160721. python/requirements-detector: Updated for version 0.5.2. python/virtualenv: Updated for version 15.0.3. system/Iosevka: Updated for version 1.9.2. system/argyllcms: Updated for version 1.8.3. system/cantarell-fonts: Updated for version 0.0.25. system/crmsh: Added (cluster management shell). system/ddrescue-gui: Updated for version 1.6.1. system/distorm3: Moved to python/distorm. system/letsencrypt.sh: Fix tarball handling. system/packagekit: Added (packagekit: PackageKit). system/patchelf: Added (A utility for patching ELF binaries). system/pdsh: Added (Parallel Distributed Shell). system/pyarchey: Updated for version 0.7. system/qemu-guest-agent: Added (QEMU Guest Agent daemon). system/rsyslog: Updated for version 8.21.0. system/rxvt-unicode: Fix SlackBuild. system/sbsigntools: Fixed downlad links. system/simpleburn: Updated for version 1.8.1. system/sleuthkit: Updated for version 4.3.0. system/ttyrec: Fix HOMEPAGE. system/vagrant: Updated for version 1.8.5. system/volatility: Updated for version 2.5. system/zstd: Added (fast lossless compression). +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Aug 28 02:41:31 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 28 Aug 2016 09:41:31 +0700 Subject: [Slackbuilds-users] Request to remove obsolete build scripts In-Reply-To: <20160825195921.GA7504@varna> References: <20160825195921.GA7504@varna> Message-ID: <3ff6fe29-e16b-5546-7461-0572e9b7a3f0@slackbuilds.org> > Could admins please remove the following obsolete build scripts? > > network/node (replaced by development/nodejs) It's now removed in my branch along with some scripts updated to reflect this change. If anyone have any objection, please let us soon before 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 willysr at slackbuilds.org Sun Aug 28 02:45:16 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 28 Aug 2016 09:45:16 +0700 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> Message-ID: > send them. ill test. >> Could I ask some kind souls here to test the iPerf3 scripts I've created, > before uploading them to SBo, please. I think what Sebastian meant was *before* he submit to SBo :) he attached his SlackBuild script in his original email -- 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 Sun Aug 28 05:50:20 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 27 Aug 2016 23:50:20 -0600 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> Message-ID: lol i was on an android phone... didnt see the attachment... just got home... testing it... =) On Sat, Aug 27, 2016 at 8:45 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > send them. ill test. > > >> Could I ask some kind souls here to test the iPerf3 scripts I've > created, > > before uploading them to SBo, please. > > I think what Sebastian meant was *before* he submit to SBo :) > he attached his SlackBuild script in his original email > > -- > 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Sun Aug 28 05:57:58 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 27 Aug 2016 23:57:58 -0600 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> Message-ID: had no issues making the package... had no issues running iperf 3.1.3 on my slack current x64. On Sat, Aug 27, 2016 at 11:50 PM, Fernando Lopez wrote: > lol i was on an android phone... didnt see the attachment... just got > home... testing it... =) > > On Sat, Aug 27, 2016 at 8:45 PM, Willy Sudiarto Raharjo < > willysr at slackbuilds.org> wrote: > >> > send them. ill test. >> >> >> Could I ask some kind souls here to test the iPerf3 scripts I've >> created, >> > before uploading them to SBo, please. >> >> I think what Sebastian meant was *before* he submit to SBo :) >> he attached his SlackBuild script in his original email >> >> -- >> 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/ >> >> >> > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Sun Aug 28 06:22:18 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 28 Aug 2016 07:22:18 +0100 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> Message-ID: <565618c5-45c7-21c0-c480-36187fb836f5@open-t.co.uk> On 28/08/16 06:57, Fernando Lopez wrote: > had no issues making the package... had no issues running iperf 3.1.3 on > my slack current x64. Thank you Fernando. I have one more problem with this package. The developers keep on referring to the software on their project page as iPerf3 (but in places just iPerf) - to differentiate it from the original iPerf/iPerf2. However, the source code files and directories just use iPerf (or "iperf" - all lower case). Thus the source code archive contains a folder called iperf-x.y.z - not iperf3-x.y.z. Even the resulting binary is just called iperf. Originally I wanted to call the SBo package iPerf3 (with corresponding files - iperf3.SlackBuild etc.) - to clearly set it apart from the other iPerf. But given the above, I don't think it can be done. Could I have some thoughts on the above please? Should I leave the scripts as they are - only referring to the software as iPerf3 in the README file - and using "iperf" everywhere else? I don't even know why the developers didn't just use another name - after all, according to them, it shares no code whatsoever with the original iPerf, and it isn't backwards compatible. From andreas.guldstrand at gmail.com Sun Aug 28 09:04:27 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Sun, 28 Aug 2016 11:04:27 +0200 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: <565618c5-45c7-21c0-c480-36187fb836f5@open-t.co.uk> References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> <565618c5-45c7-21c0-c480-36187fb836f5@open-t.co.uk> Message-ID: If the other package also ships a binary with the same name, I'd say you should rename your binary to iperf3 in your SlackBuild script, so it doesn't conflict. And mention this in the README. On 28 August 2016 at 08:22, Sebastian Arcus wrote: > On 28/08/16 06:57, Fernando Lopez wrote: >> >> had no issues making the package... had no issues running iperf 3.1.3 on >> my slack current x64. > > > Thank you Fernando. I have one more problem with this package. The > developers keep on referring to the software on their project page as iPerf3 > (but in places just iPerf) - to differentiate it from the original > iPerf/iPerf2. However, the source code files and directories just use iPerf > (or "iperf" - all lower case). Thus the source code archive contains a > folder called iperf-x.y.z - not iperf3-x.y.z. Even the resulting binary is > just called iperf. Originally I wanted to call the SBo package iPerf3 (with > corresponding files - iperf3.SlackBuild etc.) - to clearly set it apart from > the other iPerf. But given the above, I don't think it can be done. > > Could I have some thoughts on the above please? Should I leave the scripts > as they are - only referring to the software as iPerf3 in the README file - > and using "iperf" everywhere else? I don't even know why the developers > didn't just use another name - after all, according to them, it shares no > code whatsoever with the original iPerf, and it isn't backwards compatible. > > _______________________________________________ > 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 flupi at mclink.it Sun Aug 28 10:06:51 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Sun, 28 Aug 2016 12:06:51 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 Message-ID: On Slackware 14.2 I get: internal compiler error: Segmentation fault when building the qt5 package. I tried rebuilding several times but I always get the same error, although in different part of the code. An example: /usr/include/c++/5.3.0/limits:1734:10: internal compiler error: Segmentation fault = round_to_nearest; Another example: /tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1151:18: internal compiler error: Segmentation fault copyIterFunc _copyIter; It is a new installation of 14.2, the system is up to date with slackpkg. I have already compiled 20 SBo packages (including webkitgtk, which is very big) without problems. The system: HP Probook (Core i7) 16 GB RAM 500 GB SSD ( I tried two different SSD, Crucial MX200 and Samsung Evo) I have checked the RAM with memtest for several hours without errors. Apart from that the system runs fine. Any ideas or suggestions? From atelszewski at gmail.com Sun Aug 28 10:43:50 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 28 Aug 2016 12:43:50 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: References: Message-ID: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> On 28/08/16 12:06, flupi at mclink.it wrote: > On Slackware 14.2 I get: > > internal compiler error: Segmentation fault > > when building the qt5 package. I tried rebuilding several times but I > always get the same error, although in different part of the code. An > example: > > /usr/include/c++/5.3.0/limits:1734:10: internal compiler error: > Segmentation fault > = round_to_nearest; > > Another example: > > /tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1151:18: > internal compiler error: Segmentation fault > copyIterFunc _copyIter; > > > It is a new installation of 14.2, the system is up to date with > slackpkg. I have already compiled 20 SBo packages (including webkitgtk, > which is very big) without problems. > > The system: > > HP Probook (Core i7) > > 16 GB RAM > > 500 GB SSD ( I tried two different SSD, Crucial MX200 and Samsung Evo) > > I have checked the RAM with memtest for several hours without errors. > > Apart from that the system runs fine. Any ideas or suggestions? > The only thing I can tell you is that I've built qt5 2 days ago just fine on clean system in VM. Maybe some of the installed packages affect the build, or rather the compiler? Maybe you could try building with llvm instead of gcc just to see what happens? > > _______________________________________________ > 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/ > > -- Best regards, Andrzej Telszewski From flupi at mclink.it Sun Aug 28 14:08:25 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Sun, 28 Aug 2016 16:08:25 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> Message-ID: <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> Il 28/08/2016 12:43, Andrzej Telszewski ha scritto: > On 28/08/16 12:06, flupi at mclink.it wrote: >> On Slackware 14.2 I get: >> >> internal compiler error: Segmentation fault >> >> when building the qt5 package. I tried rebuilding several times but I >> always get the same error, although in different part of the code. An >> example: >> >> /usr/include/c++/5.3.0/limits:1734:10: internal compiler error: >> Segmentation fault >> = round_to_nearest; >> >> Another example: >> >> /tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1151:18: >> >> internal compiler error: Segmentation fault >> copyIterFunc _copyIter; >> >> >> It is a new installation of 14.2, the system is up to date with >> slackpkg. I have already compiled 20 SBo packages (including webkitgtk, >> which is very big) without problems. >> >> The system: >> >> HP Probook (Core i7) >> >> 16 GB RAM >> >> 500 GB SSD ( I tried two different SSD, Crucial MX200 and >> Samsung Evo) >> >> I have checked the RAM with memtest for several hours without errors. >> >> Apart from that the system runs fine. Any ideas or suggestions? >> > > The only thing I can tell you is that I've built qt5 2 days ago just > fine on clean system in VM. > > Maybe some of the installed packages affect the build, or rather the > compiler? > > Maybe you could try building with llvm instead of gcc just to see what > happens? > >> >> _______________________________________________ >> 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 your suggestion: I will try as soon as I have finished the current tests. I forgot to say that I have a 64 bits system. I tried removing one 8G memory module but I still got the error. Then I swapped the other memory module but I still got the error. Therefore I think it is not RAM related. I think that a gcc bug could be the cause: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68986 From willysr at slackbuilds.org Sun Aug 28 14:10:31 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 28 Aug 2016 21:10:31 +0700 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> Message-ID: > Thank you for your suggestion: I will try as soon as I have finished > the current tests. > > I forgot to say that I have a 64 bits system. I tried removing one 8G > memory module but I still got the error. Then I swapped the other > memory module but I still got the error. > > Therefore I think it is not RAM related. I think that a gcc bug could > be the cause: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68986 many of us have successfully built qt5 in many systems and we never had this problem. did you perform a full installation ? is there any third party packages installed on your systems? -- 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 1.41421 at gmail.com Sun Aug 28 14:31:24 2016 From: 1.41421 at gmail.com (JCA) Date: Sun, 28 Aug 2016 08:31:24 -0600 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> Message-ID: For what it is worth, I built qt5 on a 64-bit system a few days ago. As it happens (because I am stupid) I built it first on a pure 64-bit 14.2, and then again on the same system after I had gone multilib. In both cases it took quite some time (it is not the fastest system in the world) but the build completely without errors. Qt5 applications seem to be OK - except for Wireshark, which when invoked from my Xfce4 menu kills my window manager - not my session, though. Interestingly, when launched by hand from an xterm, this does not happen. But, I digress. It does seem to be the case that the problem is in your setup. On Sun, Aug 28, 2016 at 8:10 AM, Willy Sudiarto Raharjo wrote: >> Thank you for your suggestion: I will try as soon as I have finished >> the current tests. >> >> I forgot to say that I have a 64 bits system. I tried removing one 8G >> memory module but I still got the error. Then I swapped the other >> memory module but I still got the error. >> >> Therefore I think it is not RAM related. I think that a gcc bug could >> be the cause: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68986 > > many of us have successfully built qt5 in many systems and we never had > this problem. > > did you perform a full installation ? > is there any third party packages installed on your systems? > > > -- > 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 flupi at mclink.it Sun Aug 28 14:45:14 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Sun, 28 Aug 2016 16:45:14 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> Message-ID: <4d8237f4-bf5e-c53d-4dae-b4ee9eadc278@mclink.it> Il 28/08/2016 16:10, Willy Sudiarto Raharjo ha scritto: >> Thank you for your suggestion: I will try as soon as I have finished >> the current tests. >> >> I forgot to say that I have a 64 bits system. I tried removing one 8G >> memory module but I still got the error. Then I swapped the other >> memory module but I still got the error. >> >> Therefore I think it is not RAM related. I think that a gcc bug could >> be the cause: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68986 > many of us have successfully built qt5 in many systems and we never had > this problem. > > did you perform a full installation ? > is there any third party packages installed on your systems? > > > > > _______________________________________________ > 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/ > Full installation, no third party packages except the following from SBo: yakuake goffice0.8 libgnomecanvas libxml++ libofx libwebp webkitgtk gnucash libdc1394 libmp4v2 faac libiec61883 libavc1394 lame amr rtmpdump schroedinger twolame x264 x265 xvidcore ffmpeg libxkbcommon unixODBC qt5 (Error) -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Aug 28 14:47:50 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 28 Aug 2016 21:47:50 +0700 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <4d8237f4-bf5e-c53d-4dae-b4ee9eadc278@mclink.it> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> <4d8237f4-bf5e-c53d-4dae-b4ee9eadc278@mclink.it> Message-ID: <7a9ade6d-c6d2-5f31-b046-40e2d7b5d0f9@slackbuilds.org> > unixODBC I am not sure whether it can be the culprit or not, but you should read unixODBC's README NOTE: This package conflict with libiodbc in Slackware. Make sure to reinstall libiodbc if you remove this package. you might want to reinstall libiodbc and try if it solved your problem -- 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 jebrhansen+SBo at gmail.com Sun Aug 28 15:01:05 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 28 Aug 2016 15:01:05 +0000 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> <565618c5-45c7-21c0-c480-36187fb836f5@open-t.co.uk> Message-ID: You can just use a SRCNAM variable, which is set different from the PRGNAM variable. This allows the source to be named a certain way but you can call the package something else. See my python3-setuptools SlackBuild for an example: https://github.com/bassmadrigal/slackbuilds/blob/master/python/python3-setuptools/python3-setuptools.SlackBuild On Sun, Aug 28, 2016, 5:04 AM Andreas Guldstrand < andreas.guldstrand at gmail.com> wrote: > If the other package also ships a binary with the same name, I'd say > you should rename your binary to iperf3 in your SlackBuild script, so > it doesn't conflict. And mention this in the README. > > On 28 August 2016 at 08:22, Sebastian Arcus wrote: > > On 28/08/16 06:57, Fernando Lopez wrote: > >> > >> had no issues making the package... had no issues running iperf 3.1.3 on > >> my slack current x64. > > > > > > Thank you Fernando. I have one more problem with this package. The > > developers keep on referring to the software on their project page as > iPerf3 > > (but in places just iPerf) - to differentiate it from the original > > iPerf/iPerf2. However, the source code files and directories just use > iPerf > > (or "iperf" - all lower case). Thus the source code archive contains a > > folder called iperf-x.y.z - not iperf3-x.y.z. Even the resulting binary > is > > just called iperf. Originally I wanted to call the SBo package iPerf3 > (with > > corresponding files - iperf3.SlackBuild etc.) - to clearly set it apart > from > > the other iPerf. But given the above, I don't think it can be done. > > > > Could I have some thoughts on the above please? Should I leave the > scripts > > as they are - only referring to the software as iPerf3 in the README > file - > > and using "iperf" everywhere else? I don't even know why the developers > > didn't just use another name - after all, according to them, it shares no > > code whatsoever with the original iPerf, and it isn't backwards > compatible. > > > > _______________________________________________ > > 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 flupi at mclink.it Sun Aug 28 15:21:10 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Sun, 28 Aug 2016 17:21:10 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <7a9ade6d-c6d2-5f31-b046-40e2d7b5d0f9@slackbuilds.org> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> <4d8237f4-bf5e-c53d-4dae-b4ee9eadc278@mclink.it> <7a9ade6d-c6d2-5f31-b046-40e2d7b5d0f9@slackbuilds.org> Message-ID: <3407d7a7-d638-3b53-02b4-16785eb7cc5c@mclink.it> Il 28/08/2016 16:47, Willy Sudiarto Raharjo ha scritto: >> unixODBC > I am not sure whether it can be the culprit or not, but you should read > unixODBC's README > > NOTE: This package conflict with libiodbc in Slackware. Make sure to > reinstall libiodbc if you remove this package. > > you might want to reinstall libiodbc and try if it solved your problem > > > > > _______________________________________________ > 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/ > I will try what you suggest. In the meantime I have extracted and attached the test snippets from the gcc bugzilla. On my 64 bit system both trigger the internal compiler error. The first line of the files contains the compiler command line. Both compile fine on a Kubuntu 16.04 (gcc 5.4.0) on the same PC (swapping the hard disk.) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- /* g++ -c -fPIC -mpreferred-stack-boundary=5 -mincoming-stack-boundary=4 tracesig.ii */ struct { char msgdata[][8]; } __thread *mythread; char *fn1() { return mythread->msgdata[1]; } -------------- next part -------------- A non-text attachment was scrubbed... Name: tracesig.c Type: text/x-csrc Size: 623 bytes Desc: not available URL: From pfeifer.felix at gmail.com Sun Aug 28 16:14:50 2016 From: pfeifer.felix at gmail.com (Felix Pfeifer) Date: Sun, 28 Aug 2016 18:14:50 +0200 Subject: [Slackbuilds-users] faust.SlackBuild problem In-Reply-To: References: Message-ID: Hi, I am on vacation. I can have a look at this in 1 to 2 weeks. Sorry! Cheers, Felix Am 25.08.2016 12:01 schrieb "Matteo Bernardini" : > 2016-08-25 11:52 GMT+02:00 George Vlahavas : > > > > On Thu, 25 Aug 2016, Matteo Bernardini wrote: > > > >> 2016-08-25 11:09 GMT+02:00 George Vlahavas : > >>> > >>> > >>> On Thu, 25 Aug 2016, George Vlahavas wrote: > >>> > >>>> Hi, > >>>> > >>>> in the faust.SlackBuild, $ARCH is never set. You'll need to add > >>>> something > >>>> like this close to the top: > >>>> > >>>> if [ -z "$ARCH" ]; then > >>>> case "$( uname -m )" in > >>>> i?86) ARCH=i586 ;; > >>>> arm*) ARCH=arm ;; > >>>> *) ARCH=$( uname -m ) ;; > >>>> esac > >>>> fi > >>>> > >>>> Regards, > >>>> > >>>> George > >>>> > >>> > >>> Actually there are more problems with it. CFLAGS are never set properly > >>> and > >>> libraries get installed under /usr/lib in 64bit systems... > >> > >> > >> hi George, > >> > >> please check the attached patch (I'll put the maintainer in cc). > >> > >> Matteo > >> > > > > Thanks Matteo. Seems to work, but I think there are still a couple of > static > > libraries put in /usr/share/faust/. There are several .cpp source files > in > > there too and I'm not sure if they are supposed to be there in the > package. > > it seems the fedora people have a patch also for that but it's for an > older version of faust and doesn't apply to the new one, it has to be > rewritten > > http://pkgs.fedoraproject.org/cgit/rpms/faust.git/plain/ > faust-osclib-shared.patch > > then also the make commands must be adapted for that adding LIBDIR and > INCLUDEDIR statements > > http://pkgs.fedoraproject.org/cgit/rpms/faust.git/plain/faust.spec > > let's hear from the maintainer about it. > > Matteo > -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Sun Aug 28 17:20:29 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 28 Aug 2016 18:20:29 +0100 Subject: [Slackbuilds-users] iPerf3 build script for testing In-Reply-To: References: <0441d654-ba7b-f1bb-72d3-ba85c4f80391@open-t.co.uk> <565618c5-45c7-21c0-c480-36187fb836f5@open-t.co.uk> Message-ID: <4275408a-3e31-085c-74e3-84fb2142f4c7@open-t.co.uk> On 28/08/16 16:01, Jeremy Hansen wrote: > You can just use a SRCNAM variable, which is set different from the > PRGNAM variable. This allows the source to be named a certain way but > you can call the package something else. > > See my python3-setuptools SlackBuild for an example: > https://github.com/bassmadrigal/slackbuilds/blob/master/python/python3-setuptools/python3-setuptools.SlackBuild Thank you Jeremy and Andreas. Both sound like good suggestions. I'll amend the scripts accordingly. From atelszewski at gmail.com Mon Aug 29 01:42:32 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 29 Aug 2016 03:42:32 +0200 Subject: [Slackbuilds-users] sphinx_rtd_theme requires Message-ID: <0277b4fc-d9ce-beef-392b-cafa87aa0ad0@gmail.com> Hi, The requires of: https://slackbuilds.org/repository/14.2/development/sphinx_rtd_theme/ should be: Sphinx and not: sphinx -- Best regards, Andrzej Telszewski From dpross1100 at msn.com Mon Aug 29 04:12:00 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Mon, 29 Aug 2016 04:12:00 +0000 Subject: [Slackbuilds-users] Missing requirement for kodi Message-ID: Hi everyone / kodi maintainer, When trying to update kodi to version 16.1, I got an error about libdcadec not being found. Apparently dcadec should be listed as a requirement for this new version. Dan From larryhaja at gmail.com Mon Aug 29 04:14:43 2016 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 28 Aug 2016 21:14:43 -0700 Subject: [Slackbuilds-users] Missing requirement for kodi In-Reply-To: References: Message-ID: It is listed in the requirements as dcadec. --Larry On Sun, Aug 28, 2016 at 9:12 PM, Daniel Prosser wrote: > Hi everyone / kodi maintainer, > > When trying to update kodi to version 16.1, I got an error about libdcadec > not > being found. Apparently dcadec should be listed as a requirement for this > new > version. > > Dan > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dpross1100 at msn.com Mon Aug 29 04:17:44 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Mon, 29 Aug 2016 04:17:44 +0000 Subject: [Slackbuilds-users] Missing requirement for kodi In-Reply-To: References: Message-ID: Huh, so it is. Somehow I missed it. Sorry about that. Dan On Sunday, August 28, 2016 09:14:43 PM you wrote: > It is listed in the requirements as dcadec. > > --Larry > > On Sun, Aug 28, 2016 at 9:12 PM, Daniel Prosser wrote: > > Hi everyone / kodi maintainer, > > > > When trying to update kodi to version 16.1, I got an error about libdcadec > > not > > being found. Apparently dcadec should be listed as a requirement for this > > new > > version. > > > > Dan From hjensen at gmx.de Mon Aug 29 11:10:51 2016 From: hjensen at gmx.de (Henry Jensen) Date: Mon, 29 Aug 2016 13:10:51 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: References: Message-ID: <20160829131051.74f9ca5e@pc-198.iww-online.de> Hi, On Sun, 28 Aug 2016 12:06:51 +0200 "flupi at mclink.it" wrote: > On Slackware 14.2 I get: > > internal compiler error: Segmentation fault I got this error several times when building big packages, such as qt5 or icedove (Thunderbird). My workaound was to pick up the build from where it stops and continue - you have to adapt the SlackBuild script for this. I think it is clearly RAM related. Either RAM is too low (I was using 8 GB) or bad. Regards, Henry From willysr at slackbuilds.org Mon Aug 29 11:27:09 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 29 Aug 2016 18:27:09 +0700 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <20160829131051.74f9ca5e@pc-198.iww-online.de> References: <20160829131051.74f9ca5e@pc-198.iww-online.de> Message-ID: <59bd860d-aa03-4884-6ca4-f5b01da96e81@slackbuilds.org> > I think it is clearly RAM related. Either RAM is too low (I was using 8 > GB) or bad. I don't think it's low RAM issue as i use 2 GB of RAM for my VM and it still built 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 willysr at slackbuilds.org Mon Aug 29 11:27:44 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 29 Aug 2016 18:27:44 +0700 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: References: Message-ID: <11411109-47d4-ed3c-c520-a2ab60f7bffd@slackbuilds.org> > I've been trying to reach Nikos Giotis, the maintainer of qbs > SlackBuild, without success. (Well, I sent him an e-mail on Friday, but > the other one I sent him when we were switching from 14.1 to 14.2). > > If you know that he's no longer active, I would happily take over the > maintenance of qbs. he just sent a submission of qbs -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Mon Aug 29 11:29:06 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 29 Aug 2016 13:29:06 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <11411109-47d4-ed3c-c520-a2ab60f7bffd@slackbuilds.org> References: <11411109-47d4-ed3c-c520-a2ab60f7bffd@slackbuilds.org> Message-ID: <552698b4-f04f-02a2-b0da-3bb4ddb6c9c7@gmail.com> On 29/08/16 13:27, Willy Sudiarto Raharjo wrote: >> I've been trying to reach Nikos Giotis, the maintainer of qbs >> SlackBuild, without success. (Well, I sent him an e-mail on Friday, but >> the other one I sent him when we were switching from 14.1 to 14.2). >> >> If you know that he's no longer active, I would happily take over the >> maintenance of qbs. > > he just sent a submission of qbs > Yep, I'm now in touch with him ;) -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Mon Aug 29 13:48:40 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 29 Aug 2016 15:48:40 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <59bd860d-aa03-4884-6ca4-f5b01da96e81@slackbuilds.org> References: <20160829131051.74f9ca5e@pc-198.iww-online.de> <59bd860d-aa03-4884-6ca4-f5b01da96e81@slackbuilds.org> Message-ID: <44022002-0383-886b-a8d1-3fee9ded0f27@gmail.com> On 29/08/16 13:27, Willy Sudiarto Raharjo wrote: >> I think it is clearly RAM related. Either RAM is too low (I was using 8 >> GB) or bad. > > I don't think it's low RAM issue as i use 2 GB of RAM for my VM and it > still built fine > This might be related to the amount of RAM, but with connection to the number of parallel jobs. When I tried to build qt5 with 4 jobs, 2GB RAM in VM was too little. Increasing the amount to 4GB solved the problem. Anyways, I don't recall getting GCC segfault, but rather a graceful message that I run out of memory. If you get segfault, then maybe it's something worth reporting to Pat? (Although running out of memory can surely be segfault cause). You guys having 8/16/24 or more cores might possibly arrive at that problem. So, try to lower the number of parallel jobs or increase the amount of RAM ;-) -- Best regards, Andrzej Telszewski From fellype at gmail.com Mon Aug 29 14:48:48 2016 From: fellype at gmail.com (Fellype do Nascimento) Date: Mon, 29 Aug 2016 11:48:48 -0300 Subject: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2 Message-ID: Hi all, When I tried to install cycler-0.10.0 and matplotlib-1.5.2, using sboinstall, I got the following errors: Failures: cycler: md5sum failure for /usr/sbo/distfiles/cycler-0.10.0.tar.gz#md5=4cb42917ac5007d1cdff6cccfe2d016b. matplotlib: md5sum failure for /usr/sbo/distfiles/matplotlib-1.5.2.tar.gz#md5=66f35e55cc15455eb37b415ae51f1e51. cycler: cycler.SlackBuild return non-zero matplotlib: matplotlib.SlackBuild return non-zero The md5sums of both packages looks to be OK, but they fail to build. Fellype From willysr at slackbuilds.org Mon Aug 29 15:29:50 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 29 Aug 2016 22:29:50 +0700 Subject: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2 In-Reply-To: References: Message-ID: <290f46f3-d974-6166-27f0-a62aece6b8a7@slackbuilds.org> > When I tried to install cycler-0.10.0 and matplotlib-1.5.2, using > sboinstall, I got the following errors: > > Failures: > cycler: md5sum failure for > /usr/sbo/distfiles/cycler-0.10.0.tar.gz#md5=4cb42917ac5007d1cdff6cccfe2d016b. > > matplotlib: md5sum failure for > /usr/sbo/distfiles/matplotlib-1.5.2.tar.gz#md5=66f35e55cc15455eb37b415ae51f1e51. > > cycler: cycler.SlackBuild return non-zero > matplotlib: matplotlib.SlackBuild return non-zero > > The md5sums of both packages looks to be OK, but they fail to build. Thanks for reporting 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 serban.udrea at skmail.ikp.physik.tu-darmstadt.de Mon Aug 29 15:41:51 2016 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Mon, 29 Aug 2016 17:41:51 +0200 Subject: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2 In-Reply-To: References: Message-ID: <41dcd93a-32a8-7998-81eb-1b09f01eb28d@skmail.ikp.physik.tu-darmstadt.de> On 08/29/2016 04:48 PM, Fellype do Nascimento wrote: > Hi all, > > When I tried to install cycler-0.10.0 and matplotlib-1.5.2, using sboinstall, I > got the following errors: > > Failures: > cycler: md5sum failure for > /usr/sbo/distfiles/cycler-0.10.0.tar.gz#md5=4cb42917ac5007d1cdff6cccfe2d016b. > matplotlib: md5sum failure for > /usr/sbo/distfiles/matplotlib-1.5.2.tar.gz#md5=66f35e55cc15455eb37b415ae51f1e51. > cycler: cycler.SlackBuild return non-zero > matplotlib: matplotlib.SlackBuild return non-zero > > The md5sums of both packages looks to be OK, but they fail to build. > ... Hello, I myself don't use sbotools thus I cannot tell much about this issue. Unfortunately sbotools is written in Perl which I never used. I tested the download links with wget before submitting and it worked well. Maybe sbotools have a problem with the link containing "...#md5=...". Best regards, Serban From artourter at gmail.com Mon Aug 29 16:47:48 2016 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 29 Aug 2016 17:47:48 +0100 Subject: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2 In-Reply-To: <290f46f3-d974-6166-27f0-a62aece6b8a7@slackbuilds.org> References: <290f46f3-d974-6166-27f0-a62aece6b8a7@slackbuilds.org> Message-ID: Well I have just build both of these an hour ago through sbopkg with issues. So it might be a build tools problem rather than a error in the sbo package. Cheers Greg On 29 August 2016 at 16:29, Willy Sudiarto Raharjo wrote: > > When I tried to install cycler-0.10.0 and matplotlib-1.5.2, using > > sboinstall, I got the following errors: > > > > Failures: > > cycler: md5sum failure for > > /usr/sbo/distfiles/cycler-0.10.0.tar.gz#md5= > 4cb42917ac5007d1cdff6cccfe2d016b. > > > > matplotlib: md5sum failure for > > /usr/sbo/distfiles/matplotlib-1.5.2.tar.gz#md5= > 66f35e55cc15455eb37b415ae51f1e51. > > > > cycler: cycler.SlackBuild return non-zero > > matplotlib: matplotlib.SlackBuild return non-zero > > > > The md5sums of both packages looks to be OK, but they fail to build. > > Thanks for reporting > > fixed on my branch > > > -- > 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 serban.udrea at skmail.ikp.physik.tu-darmstadt.de Mon Aug 29 17:00:31 2016 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Mon, 29 Aug 2016 19:00:31 +0200 Subject: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2 In-Reply-To: References: <290f46f3-d974-6166-27f0-a62aece6b8a7@slackbuilds.org> Message-ID: <3c0023d9-34c4-abc0-d27c-411ea70f29ae@skmail.ikp.physik.tu-darmstadt.de> On 08/29/2016 06:47 PM, Greg' Ar Tourter wrote: > Well I have just build both of these an hour ago through sbopkg with issues. So it > might be a build tools problem rather than a error in the sbo package. > ... Hello, Could you please let me know what issues did you encounter. Best regards, Serban Udrea From artourter at gmail.com Mon Aug 29 17:38:29 2016 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 29 Aug 2016 18:38:29 +0100 Subject: [Slackbuilds-users] Errors while building cycler-0.10.0 and matplotlib-1.5.2 In-Reply-To: <3c0023d9-34c4-abc0-d27c-411ea70f29ae@skmail.ikp.physik.tu-darmstadt.de> References: <290f46f3-d974-6166-27f0-a62aece6b8a7@slackbuilds.org> <3c0023d9-34c4-abc0-d27c-411ea70f29ae@skmail.ikp.physik.tu-darmstadt.de> Message-ID: sorry I mean *without* issues... should really check before pressing send! Greg On 29 August 2016 at 18:00, Serban Udrea < serban.udrea at skmail.ikp.physik.tu-darmstadt.de> wrote: > On 08/29/2016 06:47 PM, Greg' Ar Tourter wrote: > >> Well I have just build both of these an hour ago through sbopkg with >> issues. So it >> might be a build tools problem rather than a error in the sbo package. >> ... >> > > Hello, > > Could you please let me know what issues did you encounter. > > Best regards, > > Serban Udrea > > _______________________________________________ > 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 flupi at mclink.it Mon Aug 29 19:38:50 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Mon, 29 Aug 2016 21:38:50 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <59bd860d-aa03-4884-6ca4-f5b01da96e81@slackbuilds.org> References: <20160829131051.74f9ca5e@pc-198.iww-online.de> <59bd860d-aa03-4884-6ca4-f5b01da96e81@slackbuilds.org> Message-ID: Il 29/08/2016 13:27, Willy Sudiarto Raharjo ha scritto: >> I think it is clearly RAM related. Either RAM is too low (I was using 8 >> GB) or bad. > I don't think it's low RAM issue as i use 2 GB of RAM for my VM and it > still built fine > > > > > _______________________________________________ > 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/ > I tried various RAM configurations (8 GB, 16 GB) and swapped RAM modules and still got the error. I tested all the RAM with memtest. Maybe in a VM the conditions are different and the problem does not appear. -------------- next part -------------- An HTML attachment was scrubbed... URL: From joshuakwood at gmail.com Tue Aug 30 05:33:42 2016 From: joshuakwood at gmail.com (JK Wood) Date: Tue, 30 Aug 2016 00:33:42 -0500 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: References: <20160829131051.74f9ca5e@pc-198.iww-online.de> <59bd860d-aa03-4884-6ca4-f5b01da96e81@slackbuilds.org> Message-ID: On Aug 29, 2016 14:38, "flupi at mclink.it" wrote: > > Il 29/08/2016 13:27, Willy Sudiarto Raharjo ha scritto: >>> >>> I think it is clearly RAM related. Either RAM is too low (I was using 8 GB) or bad. >> >> I don't think it's low RAM issue as i use 2 GB of RAM for my VM and it still built fine >> >> >> >> _______________________________________________ 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/ > > I tried various RAM configurations (8 GB, 16 GB) and swapped RAM modules and still got the error. > > I tested all the RAM with memtest. Maybe in a VM the conditions are different and the problem does not appear. > > > _______________________________________________ > 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/ > > Have you checked the size of /tmp? You would think that it would give you a space error, but I've seen a full /tmp give strange compile warnings before. --JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Tue Aug 30 18:08:03 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 30 Aug 2016 20:08:03 +0200 Subject: [Slackbuilds-users] python-gflags broken link Message-ID: <81138e50-a228-0d7c-a414-7e1529ab268e@gmail.com> Hi, https://python-gflags.googlecode.com/files/python-gflags-2.0.tar.gz seems to be broken. -- Best regards, Andrzej Telszewski From flupi at mclink.it Tue Aug 30 20:35:48 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Tue, 30 Aug 2016 22:35:48 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <7a9ade6d-c6d2-5f31-b046-40e2d7b5d0f9@slackbuilds.org> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> <4d8237f4-bf5e-c53d-4dae-b4ee9eadc278@mclink.it> <7a9ade6d-c6d2-5f31-b046-40e2d7b5d0f9@slackbuilds.org> Message-ID: <89da55dc-3eba-cf8b-f2d1-ce073ffc00bd@mclink.it> Il 28/08/2016 16:47, Willy Sudiarto Raharjo ha scritto: >> unixODBC > I am not sure whether it can be the culprit or not, but you should read > unixODBC's README > > NOTE: This package conflict with libiodbc in Slackware. Make sure to > reinstall libiodbc if you remove this package. > > you might want to reinstall libiodbc and try if it solved your problem > > > > > _______________________________________________ > 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/ > Tried but no luck. -------------- next part -------------- An HTML attachment was scrubbed... URL: From flupi at mclink.it Tue Aug 30 20:38:25 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Tue, 30 Aug 2016 22:38:25 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> Message-ID: <1e0cc5cf-aa19-8405-f7a9-83bc7665375f@mclink.it> Il 28/08/2016 12:43, Andrzej Telszewski ha scritto: > On 28/08/16 12:06, flupi at mclink.it wrote: >> On Slackware 14.2 I get: >> >> internal compiler error: Segmentation fault >> >> when building the qt5 package. I tried rebuilding several times but I >> always get the same error, although in different part of the code. An >> example: >> >> /usr/include/c++/5.3.0/limits:1734:10: internal compiler error: >> Segmentation fault >> = round_to_nearest; >> >> Another example: >> >> /tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1151:18: >> >> internal compiler error: Segmentation fault >> copyIterFunc _copyIter; >> >> >> It is a new installation of 14.2, the system is up to date with >> slackpkg. I have already compiled 20 SBo packages (including webkitgtk, >> which is very big) without problems. >> >> The system: >> >> HP Probook (Core i7) >> >> 16 GB RAM >> >> 500 GB SSD ( I tried two different SSD, Crucial MX200 and >> Samsung Evo) >> >> I have checked the RAM with memtest for several hours without errors. >> >> Apart from that the system runs fine. Any ideas or suggestions? >> > > The only thing I can tell you is that I've built qt5 2 days ago just > fine on clean system in VM. > > Maybe some of the installed packages affect the build, or rather the > compiler? > > Maybe you could try building with llvm instead of gcc just to see what > happens? > >> >> _______________________________________________ >> 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/ >> >> > > I tried with clang and it compiled for a very long time without errors. There was an error at the end when building something python related because clang didn't accept/recognize one parameter. From flupi at mclink.it Tue Aug 30 20:39:09 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Tue, 30 Aug 2016 22:39:09 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: References: <20160829131051.74f9ca5e@pc-198.iww-online.de> <59bd860d-aa03-4884-6ca4-f5b01da96e81@slackbuilds.org> Message-ID: <7db831f4-d2f9-5a3f-38f6-78e446e28758@mclink.it> Il 30/08/2016 07:33, JK Wood ha scritto: > > On Aug 29, 2016 14:38, "flupi at mclink.it " > > wrote: > > > > Il 29/08/2016 13:27, Willy Sudiarto Raharjo ha scritto: > >>> > >>> I think it is clearly RAM related. Either RAM is too low (I was > using 8 GB) or bad. > >> > >> I don't think it's low RAM issue as i use 2 GB of RAM for my VM > and it still built fine > >> > >> > >> > >> _______________________________________________ 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/ > > > > I tried various RAM configurations (8 GB, 16 GB) and swapped RAM > modules and still got the error. > > > > I tested all the RAM with memtest. Maybe in a VM the conditions are > different and the problem does not appear. > > > > > > _______________________________________________ > > 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/ > > > > > > Have you checked the size of /tmp? You would think that it would give > you a space error, but I've seen a full /tmp give strange compile > warnings before. > > --JK > > > > _______________________________________________ > 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/ > There is a lot of free space (4 GB) in /tmp. -------------- next part -------------- An HTML attachment was scrubbed... URL: From flupi at mclink.it Tue Aug 30 20:42:47 2016 From: flupi at mclink.it (flupi at mclink.it) Date: Tue, 30 Aug 2016 22:42:47 +0200 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <3407d7a7-d638-3b53-02b4-16785eb7cc5c@mclink.it> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> <4d8237f4-bf5e-c53d-4dae-b4ee9eadc278@mclink.it> <7a9ade6d-c6d2-5f31-b046-40e2d7b5d0f9@slackbuilds.org> <3407d7a7-d638-3b53-02b4-16785eb7cc5c@mclink.it> Message-ID: <3307e197-4db6-14c6-f61f-c1c35d908f38@mclink.it> Il 28/08/2016 17:21, flupi at mclink.it ha scritto: > Il 28/08/2016 16:47, Willy Sudiarto Raharjo ha scritto: >>> unixODBC >> I am not sure whether it can be the culprit or not, but you should read >> unixODBC's README >> >> NOTE: This package conflict with libiodbc in Slackware. Make sure to >> reinstall libiodbc if you remove this package. >> >> you might want to reinstall libiodbc and try if it solved your problem >> >> >> >> >> _______________________________________________ >> 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/ >> > I will try what you suggest. In the meantime I have extracted and > attached the test snippets from the gcc bugzilla. > > On my 64 bit system both trigger the internal compiler error. The > first line of the files contains the compiler command line. > > Both compile fine on a Kubuntu 16.04 (gcc 5.4.0) on the same PC > (swapping the hard disk.) > > > > _______________________________________________ > 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/ > I applied the patch on the gcc bugzilla and rebuilt the system compiler. Now the two short sources compile without errors, but still I can't compile qt5. Next I tried installing the compiler from "current" but I still get the same error. Notice that the error is not random, it appears more or less always in the same two or three places. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Aug 30 21:25:45 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 31 Aug 2016 04:25:45 +0700 Subject: [Slackbuilds-users] python-gflags broken link In-Reply-To: <81138e50-a228-0d7c-a414-7e1529ab268e@gmail.com> References: <81138e50-a228-0d7c-a414-7e1529ab268e@gmail.com> Message-ID: <8ce89079-9206-6066-fd32-b0748471b2e8@slackbuilds.org> > https://python-gflags.googlecode.com/files/python-gflags-2.0.tar.gz > > seems to be broken. Fixed on my branch Thanks for reporting -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Aug 30 22:07:41 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 31 Aug 2016 05:07:41 +0700 Subject: [Slackbuilds-users] sphinx_rtd_theme requires In-Reply-To: <0277b4fc-d9ce-beef-392b-cafa87aa0ad0@gmail.com> References: <0277b4fc-d9ce-beef-392b-cafa87aa0ad0@gmail.com> Message-ID: <918ede58-82aa-171a-ff9a-a274a5cee2ca@slackbuilds.org> > The requires of: > https://slackbuilds.org/repository/14.2/development/sphinx_rtd_theme/ > > should be: Sphinx > > and not: sphinx 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 willysr at slackbuilds.org Tue Aug 30 22:10:38 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 31 Aug 2016 05:10:38 +0700 Subject: [Slackbuilds-users] radare2 update? In-Reply-To: References: Message-ID: <3830e9a3-bd59-1023-efca-1a11c0b1f2b7@slackbuilds.org> > Is there any way we could update radare2 to latest 0.10.5 current in repo > is 0.9.8. Since it's been almost 2 weeks and no response from the maintainer, you may step up and take over maintainership of this package -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Tue Aug 30 22:45:53 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 30 Aug 2016 23:45:53 +0100 Subject: [Slackbuilds-users] perl-template needs updating In-Reply-To: References: Message-ID: Hey everybody, Here for your review is the draft revised perl template that we discussed last week. The changed parts are as follows: # Build method #1 (preferred) perl Makefile.PL \ PREFIX=/usr \ INSTALLDIRS=vendor \ INSTALLVENDORMAN1DIR=/usr/man/man1 \ INSTALLVENDORMAN3DIR=/usr/man/man3 make make test make install DESTDIR=$PKG # Build method #2 # requires perl-Module-Build or perl-Module-Build-Tiny perl Build.PL \ --installdirs vendor \ --config installvendorman1dir=/usr/man/man1 \ --config installvendorman3dir=/usr/man/man3 ./Build ./Build test ./Build install \ --destdir $PKG Your suggestions (either about the code above, or about any other parts of the perl template) will be gratefully received. Thanks! -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: perl-template.SlackBuild Type: application/octet-stream Size: 5655 bytes Desc: not available URL: From Jim.Diamond at acadiau.ca Tue Aug 30 23:57:00 2016 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Tue, 30 Aug 2016 20:57:00 -0300 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <3307e197-4db6-14c6-f61f-c1c35d908f38@mclink.it> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <585eea97-836b-adf8-3fc4-22b1965bce97@mclink.it> <4d8237f4-bf5e-c53d-4dae-b4ee9eadc278@mclink.it> <7a9ade6d-c6d2-5f31-b046-40e2d7b5d0f9@slackbuilds.org> <3407d7a7-d638-3b53-02b4-16785eb7cc5c@mclink.it> <3307e197-4db6-14c6-f61f-c1c35d908f38@mclink.it> Message-ID: <20160830235700.GB12486@jdiamond-nb.acadiau.ca> On Tue, Aug 30, 2016 at 22:42 (+0200), flupi at mclink.it wrote: > I applied the patch on the gcc bugzilla and rebuilt the system compiler. > Now the two short sources compile without errors, but still I can't compile > qt5. > Next I tried installing the compiler from "current" but I still get the same > error. Notice that the error is not random, it appears more or less always > in the same two or three places. What happens if, after the build aborts because of the error, you cd into /tmp/SBo/qt5... and manually type the make (or is it cmake? or ...?) command? Will it start to compile the same source file and crash at the same place? Incidentally, I don't recall anyone bringing up the issue of the possibility that your CPU is overheating. Is that a possibility? Can you monitor the temps as you compile, from another terminal, with something like touch temp-log while true do date >> temp-log sensors >> temp-log echo >> temp-log done and see if anything ever gets too hot? I think you said it compiled under ubuntu. Perhaps ubuntu is using a different CPU power profile. Cheers. Jim From coltree at tpg.com.au Wed Aug 31 06:42:54 2016 From: coltree at tpg.com.au (Colin Tree) Date: Wed, 31 Aug 2016 16:42:54 +1000 Subject: [Slackbuilds-users] Problem building qt5 on 14.2 In-Reply-To: <1e0cc5cf-aa19-8405-f7a9-83bc7665375f@mclink.it> References: <0618caa2-4bf0-365c-40b5-18b5818c5d47@gmail.com> <1e0cc5cf-aa19-8405-f7a9-83bc7665375f@mclink.it> Message-ID: <466cc7a4-9dd1-eedf-00d2-9c5b54c31864@tpg.com.au> I used to get occasional problems which ended up heat related. CPU fan full of cruft and the temp climbing, especially when working hard, i.e. compiling. What's your ambient, try compiling at night when cooler, open the boxen and direct a fan at the M/B I've solved it with a Zalman fanless heatsink. It's massive and quiet and cool. Seems like you've tried most everything else Go well, Colin On 08/31/2016 06:38 AM, flupi at mclink.it wrote: > Il 28/08/2016 12:43, Andrzej Telszewski ha scritto: >> On 28/08/16 12:06, flupi at mclink.it wrote: >>> On Slackware 14.2 I get: >>> >>> internal compiler error: Segmentation fault >>> >>> when building the qt5 package. I tried rebuilding several times but I >>> always get the same error, although in different part of the code. An >>> example: >>> >>> /usr/include/c++/5.3.0/limits:1734:10: internal compiler error: >>> Segmentation fault >>> = round_to_nearest; >>> >>> Another example: >>> >>> /tmp/SBo/qt-everywhere-opensource-src-5.6.1/qtbase/include/QtCore/../../src/corelib/kernel/qmetatype.h:1151:18: >>> >>> internal compiler error: Segmentation fault >>> copyIterFunc _copyIter; >>> >>> >>> It is a new installation of 14.2, the system is up to date with >>> slackpkg. I have already compiled 20 SBo packages (including webkitgtk, >>> which is very big) without problems. >>> >>> The system: >>> >>> HP Probook (Core i7) >>> >>> 16 GB RAM >>> >>> 500 GB SSD ( I tried two different SSD, Crucial MX200 and >>> Samsung Evo) >>> >>> I have checked the RAM with memtest for several hours without errors. >>> >>> Apart from that the system runs fine. Any ideas or suggestions? >>> >> >> The only thing I can tell you is that I've built qt5 2 days ago just >> fine on clean system in VM. >> >> Maybe some of the installed packages affect the build, or rather the >> compiler? >> >> Maybe you could try building with llvm instead of gcc just to see >> what happens? >> >>> >>> _______________________________________________ >>> 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/ >>> >>> >> >> > I tried with clang and it compiled for a very long time without > errors. There was an error at the end when building something python > related because clang didn't accept/recognize one parameter. > > _______________________________________________ > 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 vlahavas at gmail.com Wed Aug 31 15:22:13 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Wed, 31 Aug 2016 18:22:13 +0300 (EEST) Subject: [Slackbuilds-users] ike SlackBuild problem Message-ID: Hi, the ike SlackBuild installs libraries in /usr/lib instead of /usr/lib64 in 64bit systems. You need to add this to your cmake call: -DLIBDIR=/usr/lib${LIBDIRSUFFIX} \ Regards, George From vlahavas at gmail.com Wed Aug 31 15:29:14 2016 From: vlahavas at gmail.com (George Vlahavas) Date: Wed, 31 Aug 2016 18:29:14 +0300 (EEST) Subject: [Slackbuilds-users] ssmtp - Interactive doinst script? Message-ID: Hi, is it allowed to have interaction in the doinst.sh script? The ssmtp doinst.sh launches a script that asks questions about the user setup. I don't think that is supposed to happen. I thought that the standard way to deal with that is to have some text in the README or README.SLACKWARE files that explains how to set things up. Regards, George From baildon.research at googlemail.com Wed Aug 31 22:54:27 2016 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 31 Aug 2016 23:54:27 +0100 Subject: [Slackbuilds-users] ike SlackBuild problem In-Reply-To: References: Message-ID: > the ike SlackBuild installs libraries in /usr/lib instead of /usr/lib64 in > 64bit systems. Vitor sent us the fixed SlackBuild, and it's now in my branch. That was quick! Thanks everybody! -D. From vitor at bitarus.allowed.org Wed Aug 31 20:52:27 2016 From: vitor at bitarus.allowed.org (Vitor) Date: Wed, 31 Aug 2016 21:52:27 +0100 Subject: [Slackbuilds-users] ike SlackBuild problem In-Reply-To: References: Message-ID: Hi, I will update the SlackBuild and commit with that correction after I build it and test it on my Slack64. Best regards, V?tor On 08/31/2016 04:22 PM, George Vlahavas wrote: > Hi, > > the ike SlackBuild installs libraries in /usr/lib instead of > /usr/lib64 in 64bit systems. You need to add this to your cmake call: > > -DLIBDIR=/usr/lib${LIBDIRSUFFIX} \ > > Regards, > > George