From marco.maggi-ipsu at poste.it Thu Jan 1 07:59:01 2015 From: marco.maggi-ipsu at poste.it (Marco Maggi) Date: Thu, 01 Jan 2015 08:59:01 +0100 Subject: [Slackbuilds-users] failure building GraphicsMagick 1.3.20 on 64-bit platforms because of wrong lib pathname, workaround included Message-ID: <87bnmj2apm.fsf@governatore.luna> Ciao, my first post on this list; i run Slackware64 14.1 and I am on the long path to install GNU Octave. 64-bit libraries are under "$prefix/lib64", but I also have the alien libraries under "$prefix/lib". While building GraphicsMagick 1.3.20, the linker fails to locate 64-bit libraries because the GraphicsMagick's "configure.ac" template hard-codes the pathname "$some_prefix/lib" in several places. I have filed a bug report upstream[1]. Successful builds are possible by running configure with: $ ./configure LDFLAGS='-L/usr/lib64 -L/usr/local/lib64' and it works for me if I modify "GraphicsMagick.SlackBuild" by appending such variable setting on the command line of "configure". Can this change be applied to the distributed SlackBuilds script? TIA P.S. The script "GraphicsMagick.SlackBuild" runs "configure" with the option "--disable-openmp". If I compile by hand the package without this option, everything completes successfully. What's the reason to use this option? [1] -- "Now feel the funk blast!" Rage Against the Machine - "Calm like a bomb" From marco.maggi-ipsu at poste.it Thu Jan 1 08:13:34 2015 From: marco.maggi-ipsu at poste.it (Marco Maggi) Date: Thu, 01 Jan 2015 09:13:34 +0100 Subject: [Slackbuilds-users] package "qrupdate": wrong installation permissions on some doc files Message-ID: <8761cq3olt.fsf@governatore.luna> Ciao, the package "qrupdate" version 1.1.2 is built and installed by the SlackBuilds script with files under "/usr/doc/qrupdate" with wrong permissions 0640; IMHO, this is because the script uses "cp -a" to put such files in the temporary installation directory and the upstream distribution archive contains files with permissions 0640. -- Marco Maggi From willysr at slackbuilds.org Thu Jan 1 08:58:30 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 01 Jan 2015 15:58:30 +0700 Subject: [Slackbuilds-users] package "qrupdate": wrong installation permissions on some doc files In-Reply-To: <8761cq3olt.fsf@governatore.luna> References: <8761cq3olt.fsf@governatore.luna> Message-ID: <54A50C36.7050207@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > the package "qrupdate" version 1.1.2 is built and installed by > the SlackBuilds script with files under "/usr/doc/qrupdate" > with wrong permissions 0640; IMHO, this is because the script > uses "cp -a" to put such files in the temporary installation > directory and the upstream distribution archive contains files > with permissions 0640. Fixed in my branch Thanks for reporting - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSlDDYACgkQiHuDdNczM4HwIgCfVEbooI+JJr1BN2ux95s4arFV g2IAn355wAWjcsrUERsJXGPZOyHFWmrg =gYwg -----END PGP SIGNATURE----- From thorsten.johannvorderbrueggen at t-online.de Thu Jan 1 11:14:20 2015 From: thorsten.johannvorderbrueggen at t-online.de (thorsten.johannvorderbrueggen at t-online.de) Date: Thu, 1 Jan 2015 12:14:20 +0100 Subject: [Slackbuilds-users] Updates for avr-binutils Message-ID: <20150101121420.2b1880b60372900018dc54b4@t-online.de> Hi at felix, i need some additions and updates for avr-binutils ... changes are attached Cheers & happy new year Thorsten -- thorsten.johannvorderbrueggen at t-online.de -------------- next part -------------- A non-text attachment was scrubbed... Name: avr-binutils.diff Type: application/octet-stream Size: 1501 bytes Desc: not available URL: From marco.maggi-ipsu at poste.it Thu Jan 1 11:16:51 2015 From: marco.maggi-ipsu at poste.it (Marco Maggi) Date: Thu, 01 Jan 2015 12:16:51 +0100 Subject: [Slackbuilds-users] failure building GNU Octave 3.8.2 with SuiteSparse 4.4.1, temporary workaround included Message-ID: <87zja221jw.fsf@governatore.luna> Ciao, the latest GNU Octave release 3.8.2 fails to build when interfacing with the latest SuiteSparse release 4.4.1, because SuiteSparse changed interface in multiple places: these two packages have gotten out of sync. This is known to Octave's maintainers[1][2] and a fix might be included in the next release, but for now no luck. What is SlackBuild's policy for this case? Tell users to use the latest compatible versions? Disable support for SuiteSparse in Octave's build script? SlackBuilds' build script forces the use of Octave's AMD interface by running "configure" with: WITH_AMD_INCLUDEDIR=${WITH_AMD_INCLUDEDIR:-/usr/include/amd} configure ... --with-amd-includedir=$WITH_AMD_INCLUDEDIR ... and it fails. I was able to compile Octave by changing the invocation of "configure" to: configure ... --without-amd ... it is not the ideal solution, but at least it builds. Maybe a more detailed description of dependencies should be included in the SuiteSparse and Octave pages at ? TIA [1] [2] -- Marco Maggi From marco.maggi-ipsu at poste.it Thu Jan 1 11:52:34 2015 From: marco.maggi-ipsu at poste.it (Marco Maggi) Date: Thu, 01 Jan 2015 12:52:34 +0100 Subject: [Slackbuilds-users] package "QtOctave": website unavailable, no updates since 2011, GNU Octave having experimental GUI, proposed removal Message-ID: <87vbkq1zwd.fsf@governatore.luna> Ciao, the following URLs for QtOctave do not exist anymore or have empty contents (no files distributed): on the SlackBuilds site the distribution tarball: is not the latest available. It is not immediate to find informations on this project, but it looks dead[1][2], even though the distribution at: is still available, with the latest tarball uploaded in 2011. It is a pity because it looked nice[3], but that's life. By installing the Octave package, I can run the built in experimental GUI with: $ octave --force-gui and it looks nice. As a humble user, to avoid confusion and to provide testing help in the development of the built in GUI, I propose the removal of support for the QtProject. TIA [1] [2] [3] -- Marco Maggi From thorsten.johannvorderbrueggen at t-online.de Thu Jan 1 15:24:11 2015 From: thorsten.johannvorderbrueggen at t-online.de (thorsten.johannvorderbrueggen at t-online.de) Date: Thu, 1 Jan 2015 16:24:11 +0100 Subject: [Slackbuilds-users] update for avrdude available Message-ID: <20150101162411.e5fb5daa3b60fb907997e7ae@t-online.de> Hi at schnee72, there's an update of avrdude available ... 6.0.1 to 6.1 ... it builds without problems ... Cheers Thorsten -- thorsten.johannvorderbrueggen at t-online.de From elyk03 at gmail.com Thu Jan 1 17:35:09 2015 From: elyk03 at gmail.com (Kyle Guinn) Date: Thu, 1 Jan 2015 11:35:09 -0600 Subject: [Slackbuilds-users] failure building GNU Octave 3.8.2 with SuiteSparse 4.4.1, temporary workaround included In-Reply-To: <87zja221jw.fsf@governatore.luna> References: <87zja221jw.fsf@governatore.luna> Message-ID: On 1/1/15, Marco Maggi wrote: > Ciao, > > the latest GNU Octave release 3.8.2 fails to build when interfacing > with the latest SuiteSparse release 4.4.1, because SuiteSparse changed > interface in multiple places: these two packages have gotten out of > sync. This is known to Octave's maintainers[1][2] and a fix might be > included in the next release, but for now no luck. > > What is SlackBuild's policy for this case? Tell users to use the > latest compatible versions? Disable support for SuiteSparse in Octave's > build script? This is why the latest isn't always the greatest. I have an update for all of the SuiteSparse pieces, but I abandoned it whenever it turned out Octave couldn't use the newer version. Letting upstream know that things are broken seems to me to be the best approach. Better to let them fix it correctly than for us to force it to work with patches that may not be correct. -Kyle From sbolokanov at abv.bg Thu Jan 1 18:04:21 2015 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Thu, 1 Jan 2015 20:04:21 +0200 (EET) Subject: [Slackbuilds-users] PKGTYPE=txz for the slackbulds after next Slackware release? Message-ID: <515555784.25413.1420135461078.JavaMail.apache@nm41.abv.bg> Hello there. Dunno if it has been discussed before. Is it considered moving PKGTYPE to txz as default for future slackbuilds, say after next Slackware release? PS: Happy new year -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ts at websafe.pl Fri Jan 2 06:41:12 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 02 Jan 2015 07:41:12 +0100 Subject: [Slackbuilds-users] Indirect download links in *.info Message-ID: <54A63D88.5000501@websafe.pl> Hello, I would like to create slackbuilds for some Google TTF fonts and I have a problem with the .info file. For example, the `Open Sans` font collection is nowhere available for direct download, it's distributed by Google and the Google download link is the following: http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ Downloading this with `wget` requires the flag "--content-disposition" to be set and then everything works fine - the link is being downloaded to `Open_Sans.zip`, otherwise we end up with a "download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ" file. This case "breaks" the default `sbopkg` configuration, because WGETFLAGS does not contain "--content-disposition" by default. My question is what to do in cases like this (indirect download links)? I'm asking here because in `template.info` there is: ~~~~ DOWNLOAD="direct download link(s) of application source tarball(s) ^^^^^^^^^^^^^^^^^^^^^^^ arch-independent or x86" ~~~~ I'll of course mention this issue on the `sbopkg` mailing list but please let me know if it's "legal" ;) to use an indirect download link in *.info files. If yes, then fixing `sbopkg` is simple, it would only require altering the default configuration by extending WGETFLAGS with "--content-disposition". If not, then I don't know, because handling this situation directly in the SlackBuild is "too late" (at least for `sbopkg`, because `sbopkg` will download the source and check the md5sum before the slackbuild is called). -- Thomas Szteliga https://github.com/websafe -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Fri Jan 2 06:46:53 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 02 Jan 2015 13:46:53 +0700 Subject: [Slackbuilds-users] Indirect download links in *.info In-Reply-To: <54A63D88.5000501@websafe.pl> References: <54A63D88.5000501@websafe.pl> Message-ID: <54A63EDD.5010506@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I would like to create slackbuilds for some Google TTF fonts and I > have a problem with the .info file. > > For example, the `Open Sans` font collection is nowhere available > for direct download, it's distributed by Google and the Google > download link is the following: > > http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ > > Downloading this with `wget` requires the flag > "--content-disposition" to be set and then everything works fine - > the link is being downloaded to `Open_Sans.zip`, otherwise we end > up with a > "download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ" file. > > This case "breaks" the default `sbopkg` configuration, because > WGETFLAGS does not contain "--content-disposition" by default. > > > My question is what to do in cases like this (indirect download > links)? i have uploaded the source in this URL https://sourceforge.net/projects/slackbuildsdirectlinks/files/OpenSans/ it will take some time to propagate, though - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSmPt0ACgkQiHuDdNczM4E8mwCeNXCoSpJ9nC7aeS+jyb18jiwh yGkAn0Uklbms5ZE/pFy4Zl8KvqjX8dds =ZBvT -----END PGP SIGNATURE----- From genghiskhan at gmx.ca Fri Jan 2 06:55:25 2015 From: genghiskhan at gmx.ca (Genghis Khan) Date: Fri, 2 Jan 2015 07:55:25 +0100 Subject: [Slackbuilds-users] gogglesmm new Homepage Message-ID: Goggles Music Manager has moved to http://gogglesmm.github.io. Please update your bookmarks. Latest download version 0.13.1 is available from github. From willysr at slackbuilds.org Fri Jan 2 07:22:40 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 02 Jan 2015 14:22:40 +0700 Subject: [Slackbuilds-users] gogglesmm new Homepage In-Reply-To: References: Message-ID: <54A64740.9040101@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Goggles Music Manager has moved to http://gogglesmm.github.io. > Please update your bookmarks. Latest download version 0.13.1 is > available from github. unfortunately, it will require newer fox-toolkit which we don't have in our repo they are tracking development version of fox-toolkit and increase it almost on every release - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSmR0AACgkQiHuDdNczM4FyUgCcDof/S0va2f+AGyDVftHpWlKA Pc4An18GXu9yP56SuLUB+wArUGb70oIx =RCdv -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Fri Jan 2 07:29:00 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 2 Jan 2015 01:29:00 -0600 Subject: [Slackbuilds-users] PKGTYPE=txz for the slackbulds after next Slackware release? In-Reply-To: <515555784.25413.1420135461078.JavaMail.apache@nm41.abv.bg> References: <515555784.25413.1420135461078.JavaMail.apache@nm41.abv.bg> Message-ID: <20150102012900.74e43333@home.rlworkman.net> On Thu, 1 Jan 2015 20:04:21 +0200 (EET) ????? ????????? wrote: > Dunno if it has been discussed before. > Is it considered moving PKGTYPE to txz as default for future > slackbuilds, say after next Slackware release? Nope, there are no plans to do that, for two main reasons: 1. This would increase the packaging time (quite a bit for some large packages). 2. This is easily set by you in your build environment, i.e. if you "export PKGTYPE=txz" before building, the package will be created as a txz instead of tgz. As a reasonable default, tgz is exactly that. > PS: Happy new year Thanks - you too! -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 ts at websafe.pl Fri Jan 2 07:32:07 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 02 Jan 2015 08:32:07 +0100 Subject: [Slackbuilds-users] Indirect download links in *.info In-Reply-To: <54A63EDD.5010506@slackbuilds.org> References: <54A63D88.5000501@websafe.pl> <54A63EDD.5010506@slackbuilds.org> Message-ID: <54A64977.8090709@websafe.pl> On 01/02/2015 07:46 AM, Willy Sudiarto Raharjo wrote: > i have uploaded the source in this URL > https://sourceforge.net/projects/slackbuildsdirectlinks/files/OpenSans/ OK, thank You Willy, but please check the result of this script: https://gist.github.com/websafe/c172f6a99cf2ff28f8f0 Why do the md5 sums differ? ls -l -rw-r--r-- 1 root root 1144311 Jan 2 2015 Open_Sans.zip -rw-r--r-- 1 root root 1144311 Jan 2 07:08 download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ md5sum 811d92c69a9d75e17c148b28226c6eab download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ b7b32f9e7f22b772d83117407ed48f1b Open_Sans.zip md5sum -b 811d92c69a9d75e17c148b28226c6eab *download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ b7b32f9e7f22b772d83117407ed48f1b *Open_Sans.zip I've noticed something strange for i in `seq 10`; do \ rm -f Open_Sans.zip; \ wget -q --content-disposition \ "http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ"; \ md5sum Open_Sans.zip; \ done; Result: 387a12ebc6ae95fc1d7d34ece556ab71 Open_Sans.zip 387a12ebc6ae95fc1d7d34ece556ab71 Open_Sans.zip 4b71e4dd4e82c0ae7119fce173c699c9 Open_Sans.zip 4b71e4dd4e82c0ae7119fce173c699c9 Open_Sans.zip 087871b0c521cdb33d4cf76fdd6554c4 Open_Sans.zip 087871b0c521cdb33d4cf76fdd6554c4 Open_Sans.zip 2bd0bd021b17e6c1b44885cb4cfa54f5 Open_Sans.zip 7f8d14883723c28087d352e53746635c Open_Sans.zip 7f8d14883723c28087d352e53746635c Open_Sans.zip f7b0244cc750069f99ddca02258e4118 Open_Sans.zip It's somehow Google's "fault". So in this case I'll not be able to verify, that https://sourceforge.net/projects/slackbuildsdirectlinks/files/OpenSans/ matches http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ hmmm... -- Thomas Szteliga https://github.com/websafe -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Fri Jan 2 07:47:24 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 2 Jan 2015 14:47:24 +0700 Subject: [Slackbuilds-users] Indirect download links in *.info In-Reply-To: <54A64977.8090709@websafe.pl> References: <54A63D88.5000501@websafe.pl> <54A63EDD.5010506@slackbuilds.org> <54A64977.8090709@websafe.pl> Message-ID: <17D813EC-0971-4E21-8E1B-067DC16E33B4@slackbuilds.org> > Why do the md5 sums differ? It's normal since google is like generating the Zip file on the fly You only need to check the checksum from the source i uploaded and that should suffice -- Willy Sudiarto Raharjo From yalhcru at gmail.com Fri Jan 2 08:00:46 2015 From: yalhcru at gmail.com (B Watson) Date: Fri, 2 Jan 2015 03:00:46 -0500 Subject: [Slackbuilds-users] Indirect download links in *.info In-Reply-To: <54A64977.8090709@websafe.pl> References: <54A63D88.5000501@websafe.pl> <54A63EDD.5010506@slackbuilds.org> <54A64977.8090709@websafe.pl> Message-ID: On 1/2/15, Thomas Szteliga wrote: > Why do the md5 sums differ? > It's somehow Google's "fault". Download the file, wait a couple of minutes, then download it again. Then use "unzip -l" on both copies, and you'll notice the timestamps stored inside the zip files are different. I guess they're generating the zip file on-demand? > So in this case > I'll not be able to verify, that > > https://sourceforge.net/projects/slackbuildsdirectlinks/files/OpenSans/ > > matches > > http://www.google.com/fonts/download?kit=3hvsV99qyKCBS55e5pvb3ltkqrIMaAZWyLYEoB48lSQ Sure you will. Unzip them both, then compare their contents. Can even use "diff -ar" on both extracted directories. From rworkman at slackbuilds.org Fri Jan 2 08:05:50 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 2 Jan 2015 02:05:50 -0600 Subject: [Slackbuilds-users] gogglesmm new Homepage In-Reply-To: <54A64740.9040101@slackbuilds.org> References: <54A64740.9040101@slackbuilds.org> Message-ID: <20150102020550.0f071ffd@home.rlworkman.net> On Fri, 02 Jan 2015 14:22:40 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Goggles Music Manager has moved to http://gogglesmm.github.io. > > Please update your bookmarks. Latest download version 0.13.1 is > > available from github. > > unfortunately, it will require newer fox-toolkit which we don't have > in our repo > they are tracking development version of fox-toolkit and increase it > almost on every release fox-toolkit is only used by xfe otherwise, last I looked (in fact, it was xfe that originally provided the reason for fox-toolkit's inclusion in our repo), so as long as someone is willing to verify that xfe still works with it (or at least bump xfe as needed), there's no reason to hold back gogglesmm. I'm the maintainer for both fox-toolkit and xfe, so whoever wants to be responsible for those is welcome to grab them. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Fri Jan 2 08:25:28 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 02 Jan 2015 00:25:28 -0800 Subject: [Slackbuilds-users] [Slackbiulds-users] QEMU updates Message-ID: <54A655F8.7000403@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Per the discussion on this list, I have submitted an update to qemu: - - version 2.2.0 - - LIBUSB option to toggle static build of libusb-1.0.19 - - Tested on Slackware64 14.1 USB devices listed ok in qemu monitor and in quest via 'lsusb'. Notes: - - usbredir is a hard dependency with LIBUSB=yes - - modify included 65-kvm.rules to allow udev to reset usb permisions? Ed **2015: The year of the [Slackware] Linux desktop! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSmVfcACgkQXvwMaW61dLdTmwCdEQ/ySr/NEfRby9d3xSSgi638 AP8AoJ7EoxXfJulzOC+ASpSPQOmumZQj =/SRB -----END PGP SIGNATURE----- From genghiskhan at gmx.ca Fri Jan 2 09:17:31 2015 From: genghiskhan at gmx.ca (Genghis Khan) Date: Fri, 2 Jan 2015 10:17:31 +0100 Subject: [Slackbuilds-users] gogglesmm new Homepage In-Reply-To: <54A64740.9040101@slackbuilds.org> References: , <54A64740.9040101@slackbuilds.org> Message-ID: Update homepage URL, not gogglesmm. > Sent: Friday, January 02, 2015 at 9:22 AM > From: "Willy Sudiarto Raharjo" > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] gogglesmm new Homepage > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Goggles Music Manager has moved to http://gogglesmm.github.io. > > Please update your bookmarks. Latest download version 0.13.1 is > > available from github. > > unfortunately, it will require newer fox-toolkit which we don't have > in our repo > they are tracking development version of fox-toolkit and increase it > almost on every release > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSmR0AACgkQiHuDdNczM4FyUgCcDof/S0va2f+AGyDVftHpWlKA > Pc4An18GXu9yP56SuLUB+wArUGb70oIx > =RCdv > -----END PGP SIGNATURE----- > _______________________________________________ > 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 k.venken at online.be Fri Jan 2 09:40:59 2015 From: k.venken at online.be (Karel Venken) Date: Fri, 02 Jan 2015 10:40:59 +0100 Subject: [Slackbuilds-users] gogglesmm new Homepage In-Reply-To: <20150102020550.0f071ffd@home.rlworkman.net> References: <54A64740.9040101@slackbuilds.org> <20150102020550.0f071ffd@home.rlworkman.net> Message-ID: <54A667AB.9060301@online.be> Robby Workman wrote: > On Fri, 02 Jan 2015 14:22:40 +0700 > Willy Sudiarto Raharjo wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >>> Goggles Music Manager has moved to http://gogglesmm.github.io. >>> Please update your bookmarks. Latest download version 0.13.1 is >>> available from github. >> unfortunately, it will require newer fox-toolkit which we don't have >> in our repo >> they are tracking development version of fox-toolkit and increase it >> almost on every release > > fox-toolkit is only used by xfe otherwise, last I looked (in fact, > it was xfe that originally provided the reason for fox-toolkit's > inclusion in our repo), so as long as someone is willing to verify > that xfe still works with it (or at least bump xfe as needed), > there's no reason to hold back gogglesmm. I'm the maintainer for > both fox-toolkit and xfe, so whoever wants to be responsible for > those is welcome to grab them. > > -RW I am actively using xfe. I checked the xfe website it clearly states xfe won't compile with version 1.7.x of FOX. Not sure this is going to change. If it would be intresting to know, I can give it a try this evening with the new version anyway, you'll never know, but I won't count on it. K. From k.venken at online.be Fri Jan 2 14:07:55 2015 From: k.venken at online.be (Karel Venken) Date: Fri, 02 Jan 2015 15:07:55 +0100 Subject: [Slackbuilds-users] gogglesmm new Homepage In-Reply-To: <54A667AB.9060301@online.be> References: <54A64740.9040101@slackbuilds.org> <20150102020550.0f071ffd@home.rlworkman.net> <54A667AB.9060301@online.be> Message-ID: <54A6A63B.5020007@online.be> Karel Venken wrote: > Robby Workman wrote: >> On Fri, 02 Jan 2015 14:22:40 +0700 >> Willy Sudiarto Raharjo wrote: >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>>> Goggles Music Manager has moved to http://gogglesmm.github.io. >>>> Please update your bookmarks. Latest download version 0.13.1 is >>>> available from github. >>> unfortunately, it will require newer fox-toolkit which we don't have >>> in our repo >>> they are tracking development version of fox-toolkit and increase it >>> almost on every release >> >> fox-toolkit is only used by xfe otherwise, last I looked (in fact, >> it was xfe that originally provided the reason for fox-toolkit's >> inclusion in our repo), so as long as someone is willing to verify >> that xfe still works with it (or at least bump xfe as needed), >> there's no reason to hold back gogglesmm. I'm the maintainer for >> both fox-toolkit and xfe, so whoever wants to be responsible for >> those is welcome to grab them. >> >> -RW > > I am actively using xfe. I checked the xfe website it clearly states > xfe won't compile with version 1.7.x of FOX. Not sure this is going to > change. If it would be intresting to know, I can give it a try this > evening with the new version anyway, you'll never know, but I won't > count on it. > > K. > What I found (in a clean Slackware system) - modified the Slackbuild to use fox version 1.7.50 - download, (slack)build and install fox-toolkit - download, (slack)build xfe As expected, xfe won't build as it tests for fox-toolkit 1.60, so I modified the configure to check for 1.7 instead and use this one. Next, the compiler complained in several (?) files about ... eg. missing definition for TRUE, FALSE, so I tried to fix a few files, but it seems that the API has changed and fixing would require some effort which I have not done. I have to admit, I am not good at this,... With version 1.7 still installed on my system, I set the SlackBuild 'back' to 1.6.50 (actually, the current still refers to 1.6.49) and tried to build xfe which was succesfull. So if really needed, both versions can coexist, but as said, xfe won't build out of the box with 1.7.50. FWW, If I am the only one using XFE feel free to 'abandon it' and upgrade the fox-toolkit. K. From leva at ecentrum.hu Fri Jan 2 14:46:41 2015 From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=) Date: Fri, 2 Jan 2015 15:46:41 +0100 Subject: [Slackbuilds-users] rxvt-unicode up for grabs Message-ID: <20150102144641.GG1533@serenity.local> Hi! I'm not using it anymore. Anyone willing to take over? Daniel From burningc at SDF.ORG Fri Jan 2 15:31:24 2015 From: burningc at SDF.ORG (Glenn Becker) Date: Fri, 2 Jan 2015 15:31:24 +0000 (UTC) Subject: [Slackbuilds-users] rxvt-unicode up for grabs In-Reply-To: <20150102144641.GG1533@serenity.local> References: <20150102144641.GG1533@serenity.local> Message-ID: > I'm not using it anymore. Anyone willing to take over? I'll adopt if no one else has beaten me ... :) Thx, /Glenn +---------------------------------------------+ Glenn Becker - burningc at sdf.org SDF Public Access UNIX System - http://sdf.org +---------------------------------------------+ From je at ktf.rtu.lv Sat Jan 3 08:58:44 2015 From: je at ktf.rtu.lv (=?utf-8?b?SsSBbmlz?=) Date: Sat, 03 Jan 2015 10:58:44 +0200 Subject: [Slackbuilds-users] Test for Slack version Message-ID: <20150103105844.Horde.o10vJlQSxX9Vzwy5J6F-LA2@inbox.dv.lv> Dear sirs! What do you think about the introduction of a small test for Slackware version in order to determine supported format of the package - .tgz or .txz? While not extremely important, in case if the the built packages are re-distributed among computers using some cloud services, it could save space and sometimes also time and money. Happy New Year! Janis P.S. If you like the idea, I can submit such test for your evaluation. Or it (package type setting) could have its place in sbopkg config? From willysr at slackbuilds.org Sat Jan 3 09:40:42 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Jan 2015 16:40:42 +0700 Subject: [Slackbuilds-users] Test for Slack version In-Reply-To: <20150103105844.Horde.o10vJlQSxX9Vzwy5J6F-LA2@inbox.dv.lv> References: <20150103105844.Horde.o10vJlQSxX9Vzwy5J6F-LA2@inbox.dv.lv> Message-ID: <2908793B-D8F4-4654-B1DA-27842AD4DED6@slackbuilds.org> > What do you think about the introduction of a small test for Slackware version in order to determine supported format of the package - .tgz or .txz? > > While not extremely important, in case if the the built packages are re-distributed among computers using some cloud services, it could save space and sometimes also time and money. Slackware support both formats, so no need to check it whether it's supported or not Well, unless you are running a very old Slackware release -- Willy Sudiarto Raharjo From Hullen at t-online.de Sat Jan 3 13:15:00 2015 From: Hullen at t-online.de (Helmut Hullen) Date: Sat, 3 Jan 2015 14:15:00 +0100 Subject: [Slackbuilds-users] squid options In-Reply-To: <> Message-ID: Hallo, slackbuilds-users, could it be that in the squid SBo packet the /usr/libexec/basic_*_auth files must have the suid flag? I use the "getpwnam" file, and without this flag the acl auth_param basic program /usr/libexec/basic_getpwnam_auth /etc/shadow produces strange error messages (it tells that there are not enough basic children). Viele Gruesse! Helmut From rworkman at slackbuilds.org Sat Jan 3 16:38:25 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 3 Jan 2015 10:38:25 -0600 Subject: [Slackbuilds-users] Test for Slack version In-Reply-To: <20150103105844.Horde.o10vJlQSxX9Vzwy5J6F-LA2@inbox.dv.lv> References: <20150103105844.Horde.o10vJlQSxX9Vzwy5J6F-LA2@inbox.dv.lv> Message-ID: <20150103103825.60e7049b@home.rlworkman.net> On Sat, 03 Jan 2015 10:58:44 +0200 J?nis wrote: > What do you think about the introduction of a small test for > Slackware version in order to determine supported format of the > package - .tgz or .txz? > > While not extremely important, in case if the the built packages are > re-distributed among computers using some cloud services, it could > save space and sometimes also time and money. http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-January/013369.html -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Jan 3 17:52:34 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 04 Jan 2015 00:52:34 +0700 Subject: [Slackbuilds-users] Updates - 20150103.1 Message-ID: <54A82C62.1050307@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Jan 3 17:42:20 UTC 2015 academic/qrupdate: Fix doc permission. audio/gogglesmm: Fix homepage. audio/lmms: Updated for version 1.1.0. audio/soundkonverter: Updated for version 2.1.2. desktop/lumina: Added (Desktop Environment for BSD). development/android-tools: Fix TMP. development/avr-binutils: Updated for version 2.25. development/avr-gcc: Updated for version 4.9.2. development/avr-gdb: Updated for version 7.8.1. development/avrdude: Updated for version 6.1. development/meld3: Updated for version 3.12.3. development/mysql-workbench: Add py append patch. games/bitfighter: Updated for version 019d. games/instead: Updated for version 2.2.0. games/triplea: Updated for version 1.8.0.5. gis/geopy: Updated for version 1.7.0. git/gitignore: Add .jar to .gitignore. graphics/jpegoptim: Updated for version 1.4.2. graphics/mozjpeg: Updated for version 3.0. libraries/avr-libc: Updated for version 1.8.1. libraries/gconfmm: Change email. libraries/libasyncns: Change email. libraries/libscrypt: Updated for version 1.20. libraries/libslack: Change email. libraries/libunibreak: Added (a line breaking library). libraries/libwebp: Update README. libraries/mysql-connector-c++: Downgraded to 1.1.3. misc/xcape: Added (Key Modifier). multimedia/gmtp: Fix VERSION. network/megatools: Updated for version 1.9.94. network/otter: Updated for version 0.9.04. python/PyGreSQL: Change email. python/python-sh: Updated for version 1.11. ruby/heroku-client: Updated for version 3.21.4. system/ZoneMinder: Added (video camera security and surveillance). system/qemu: Updated for version 2.2.0. system/usermin: Updated for version 1.640. system/webmin: Updated for version 1.730. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSoLGIACgkQiHuDdNczM4F8uQCdEtw+xKFE5lgPorWkIKYkPR0W 4jcAnjBywhMGNKssax49twW8wsYlwSWd =E4I6 -----END PGP SIGNATURE----- From larryhaja at gmail.com Sun Jan 4 00:32:37 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Sat, 3 Jan 2015 16:32:37 -0800 Subject: [Slackbuilds-users] COMPAT32 question In-Reply-To: References: Message-ID: Has this been signed off by the SBo admins? I see that apulse now has the "[ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" check in the ready queue. --Larry On Wed, Dec 17, 2014 at 4:53 PM, B Watson wrote: > On 12/17/14, Ryan P.C. McQuen wrote: > > Furthermore, does someone know a better way to perform this check. > > Maybe I should be relying on checking glibc or gcc ... > > That's what I'd do. In the section that checks ARCH: > > ... > elif [ "$ARCH" = "x86_64" ]; then > SLKCFLAGS="-O2 -fPIC" > LIBDIRSUFFIX="64" > [ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" > else > ... > > Doing it that way will autodetect, but still allow the user to override > with COMPAT32=no in the environment. It also avoids the use of find, > which is kinda slow and heavy. > > As to whether it's a good idea... I don't see why not. The existing > apulse.SlackBuild already has multilib-specific code, this just automates > enabling it (instead of user having to manually COMPAT32=yes). > _______________________________________________ > 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 Sun Jan 4 01:10:22 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 3 Jan 2015 17:10:22 -0800 Subject: [Slackbuilds-users] COMPAT32 question In-Reply-To: References: Message-ID: On Jan 3, 2015 4:32 PM, "Larry Hajali" wrote: > > Has this been signed off by the SBo admins? I see that apulse now has the "[ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" check in the ready queue. > Actually it has been live on SBo since 12.20: http://slackbuilds.org/cgit/slackbuilds/commit/?id=58e9ea52ff1b6b018bd0d601e43fbeb4800ff5e2 > --Larry > > On Wed, Dec 17, 2014 at 4:53 PM, B Watson wrote: >> >> On 12/17/14, Ryan P.C. McQuen wrote: >> > Furthermore, does someone know a better way to perform this check. >> > Maybe I should be relying on checking glibc or gcc ... >> >> That's what I'd do. In the section that checks ARCH: >> >> ... >> elif [ "$ARCH" = "x86_64" ]; then >> SLKCFLAGS="-O2 -fPIC" >> LIBDIRSUFFIX="64" >> [ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" >> else >> ... >> >> Doing it that way will autodetect, but still allow the user to override >> with COMPAT32=no in the environment. It also avoids the use of find, >> which is kinda slow and heavy. >> >> As to whether it's a good idea... I don't see why not. The existing >> apulse.SlackBuild already has multilib-specific code, this just automates >> enabling it (instead of user having to manually COMPAT32=yes). >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Sun Jan 4 01:14:51 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Sat, 3 Jan 2015 17:14:51 -0800 Subject: [Slackbuilds-users] COMPAT32 question In-Reply-To: References: Message-ID: On Sat, Jan 3, 2015 at 5:10 PM, Ryan P.C. McQuen wrote: > > On Jan 3, 2015 4:32 PM, "Larry Hajali" wrote: > > > > Has this been signed off by the SBo admins? I see that apulse now has > the "[ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" check in the > ready queue. > > > > Actually it has been live on SBo since 12.20: > > > http://slackbuilds.org/cgit/slackbuilds/commit/?id=58e9ea52ff1b6b018bd0d601e43fbeb4800ff5e2 > > Ok, thanks. I'll just remember to "export COMPAT32=no" in my sbopkg.conf file on my multilib system. --Larry > > --Larry > > > > On Wed, Dec 17, 2014 at 4:53 PM, B Watson wrote: > >> > >> On 12/17/14, Ryan P.C. McQuen wrote: > >> > Furthermore, does someone know a better way to perform this check. > >> > Maybe I should be relying on checking glibc or gcc ... > >> > >> That's what I'd do. In the section that checks ARCH: > >> > >> ... > >> elif [ "$ARCH" = "x86_64" ]; then > >> SLKCFLAGS="-O2 -fPIC" > >> LIBDIRSUFFIX="64" > >> [ -e /lib/libc.so.6 ] && COMPAT32="${COMPAT32:-yes}" > >> else > >> ... > >> > >> Doing it that way will autodetect, but still allow the user to override > >> with COMPAT32=no in the environment. It also avoids the use of find, > >> which is kinda slow and heavy. > >> > >> As to whether it's a good idea... I don't see why not. The existing > >> apulse.SlackBuild already has multilib-specific code, this just > automates > >> enabling it (instead of user having to manually COMPAT32=yes). > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > >> FAQ - http://slackbuilds.org/faq/ > >> > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > > > _______________________________________________ > 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 info at microlinux.fr Sun Jan 4 09:09:00 2015 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 04 Jan 2015 10:09:00 +0100 Subject: [Slackbuilds-users] Catfish not working Message-ID: <54A9032C.4010204@microlinux.fr> Hi, I just built Catfish from SBo, along with the handful of dependencies (pexpect, pyxdg, pygobject3). I'm running it in the Xfce desktop environment. The application doesn't start. When I invoke 'catfish' in a graphical terminal, I get a bunch of error messages. Here's the beginning: (catfish.py:10978): Gtk-WARNING **: Unknown property: GtkInfoBar.show-close-button Traceback (most recent call last): File "/usr/share/catfish/bin/catfish.py", line 44, in catfish.main() File "/usr/share/catfish/catfish/__init__.py", line 73, in main window = CatfishWindow.CatfishWindow() File "/usr/share/catfish/catfish_lib/Window.py", line 49, in __new__ new_object.finish_initializing(builder) File "/usr/share/catfish/catfish/CatfishWindow.py", line 210, in finish_initializing if SudoDialog.check_dependencies(['locate', 'updatedb']): File "/usr/share/catfish/catfish_lib/SudoDialog.py", line 54, in check_dependencies pexpect.TIMEOUT]) == 3: File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1418, in expect timeout, searchwindowsize) File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1433, in expect_list timeout, searchwindowsize) File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1490, in expect_loop index = searcher.search(incoming, freshlen, searchwindowsize) File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1946, in search match = s.search(buffer, searchstart) RuntimeError: internal error in regular expression engine Any idea what's wrong here? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From hostmaster at slackonly.com Sun Jan 4 10:27:29 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 04 Jan 2015 12:27:29 +0200 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54A9032C.4010204@microlinux.fr> References: <54A9032C.4010204@microlinux.fr> Message-ID: <54A91591.6020902@slackonly.com> On 01/04/2015 11:09 AM, Niki Kovacs wrote: > Hi, > > I just built Catfish from SBo, along with the handful of dependencies > (pexpect, pyxdg, pygobject3). I'm running it in the Xfce desktop > environment. > > The application doesn't start. When I invoke 'catfish' in a graphical > terminal, I get a bunch of error messages. Here's the beginning: > > (catfish.py:10978): Gtk-WARNING **: Unknown property: > GtkInfoBar.show-close-button > Traceback (most recent call last): > File "/usr/share/catfish/bin/catfish.py", line 44, in > catfish.main() > File "/usr/share/catfish/catfish/__init__.py", line 73, in main > window = CatfishWindow.CatfishWindow() > File "/usr/share/catfish/catfish_lib/Window.py", line 49, in __new__ > new_object.finish_initializing(builder) > File "/usr/share/catfish/catfish/CatfishWindow.py", line 210, in > finish_initializing > if SudoDialog.check_dependencies(['locate', 'updatedb']): > File "/usr/share/catfish/catfish_lib/SudoDialog.py", line 54, in > check_dependencies > pexpect.TIMEOUT]) == 3: > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line > 1418, in expect > timeout, searchwindowsize) > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line > 1433, in expect_list > timeout, searchwindowsize) > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line > 1490, in expect_loop > index = searcher.search(incoming, freshlen, searchwindowsize) > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line > 1946, in search > match = s.search(buffer, searchstart) > RuntimeError: internal error in regular expression engine > > Any idea what's wrong here? > > Cheers, > > Niki Hi!, Working fine here in xfce with latest slackbuilds.... From dave at dawoodfall.net Sun Jan 4 15:09:31 2015 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 4 Jan 2015 15:09:31 +0000 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54A9032C.4010204@microlinux.fr> References: <54A9032C.4010204@microlinux.fr> Message-ID: <20150104150930.GA8796@Blackswan> >Hi, > >I just built Catfish from SBo, along with the handful of dependencies >(pexpect, pyxdg, pygobject3). I'm running it in the Xfce desktop >environment. > >The application doesn't start. When I invoke 'catfish' in a graphical >terminal, I get a bunch of error messages. Here's the beginning: > >(catfish.py:10978): Gtk-WARNING **: Unknown property: >GtkInfoBar.show-close-button >Traceback (most recent call last): > File "/usr/share/catfish/bin/catfish.py", line 44, in > catfish.main() > File "/usr/share/catfish/catfish/__init__.py", line 73, in main > window = CatfishWindow.CatfishWindow() > File "/usr/share/catfish/catfish_lib/Window.py", line 49, in __new__ > new_object.finish_initializing(builder) > File "/usr/share/catfish/catfish/CatfishWindow.py", line 210, in >finish_initializing > if SudoDialog.check_dependencies(['locate', 'updatedb']): > File "/usr/share/catfish/catfish_lib/SudoDialog.py", line 54, in >check_dependencies > pexpect.TIMEOUT]) == 3: > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line >1418, in expect > timeout, searchwindowsize) > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line >1433, in expect_list > timeout, searchwindowsize) > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line >1490, in expect_loop > index = searcher.search(incoming, freshlen, searchwindowsize) > File "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line >1946, in search > match = s.search(buffer, searchstart) >RuntimeError: internal error in regular expression engine > >Any idea what's wrong here? > >Cheers, > >Niki Hi Niki, You say that that's the start of the error? Could you show us the full error? Maybe pastebin it, if it's too large for the mailing list? Thanks, Dave -- +???+???+???+???+???+???+???+???+???+???+???+???+???+???+???+ | Studioware. We provide the tools. You make the music. | | http://www.studioware.org | | irc.freenode.net #studioware | | irc.oftc.net #studioware | +???+???+???+???+???+???+???+???+???+???+???+???+???+???+???+ From info at microlinux.fr Sun Jan 4 15:59:52 2015 From: info at microlinux.fr (Niki Kovacs) Date: Sun, 04 Jan 2015 16:59:52 +0100 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <20150104150930.GA8796@Blackswan> References: <54A9032C.4010204@microlinux.fr> <20150104150930.GA8796@Blackswan> Message-ID: <54A96378.9070009@microlinux.fr> Le 04/01/2015 16:09, David Woodfall a ?crit : > You say that that's the start of the error? Could you show us the full > error? Maybe pastebin it, if it's too large for the mailing list? This *is* the full error. -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From xgizzmo at gmail.com Sun Jan 4 16:24:23 2015 From: xgizzmo at gmail.com (xgizzmo at gmail.com) Date: Sun, 4 Jan 2015 11:24:23 -0500 Subject: [Slackbuilds-users] squid options In-Reply-To: References: Message-ID: <201501041124.24173.xgizzmo@gmail.com> On Saturday 03 January 2015 08:15:00 Helmut Hullen wrote: > Hallo, slackbuilds-users, > > could it be that in the squid SBo packet the > > /usr/libexec/basic_*_auth > > files must have the suid flag? > > I use the "getpwnam" file, and without this flag the acl > > auth_param basic program /usr/libexec/basic_getpwnam_auth /etc/shadow > > produces strange error messages (it tells that there are not enough > basic children). > > Viele Gruesse! > Helmut From the man page Quote: " When used for authenticating to local UNIX shadow password databases the program must be running as root or else it won?t have sufficient permissions to access the user password database. Such use of this program is not recommended, but if you absolutely need to then make the program setuid root. " Obviously we won't do this in the slackbuild, the sysadmin can make that choice. --dsomero From Hullen at t-online.de Sun Jan 4 19:06:00 2015 From: Hullen at t-online.de (Helmut Hullen) Date: Sun, 4 Jan 2015 20:06:00 +0100 Subject: [Slackbuilds-users] squid options In-Reply-To: <201501041124.24173.xgizzmo@gmail.com> Message-ID: Hallo, David, Du meintest am 04.01.15: >> could it be that in the squid SBo packet the >> >> /usr/libexec/basic_*_auth >> >> files must have the suid flag? > From the man page Quote: > " When used for authenticating to local UNIX shadow password > databases the program must be running as root or else it won?t have > sufficient permissions to access the user password database. Such > use of this program is not recommended, but if you absolutely need > to then make the program setuid root. " > Obviously we won't do this in the slackbuild, the sysadmin can make > that choice. Ok - I'll put the "chmod" command into my "/etc/init.d/squid". Viele Gruesse! Helmut From kingbeowulf at gmail.com Sun Jan 4 19:18:28 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 04 Jan 2015 11:18:28 -0800 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54A9032C.4010204@microlinux.fr> References: <54A9032C.4010204@microlinux.fr> Message-ID: <54A99204.4040903@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/04/2015 01:09 AM, Niki Kovacs wrote: > Hi, > > I just built Catfish from SBo, along with the handful of > dependencies (pexpect, pyxdg, pygobject3). I'm running it in the > Xfce desktop environment. > > The application doesn't start. When I invoke 'catfish' in a > graphical terminal, I get a bunch of error messages. Here's the > beginning: > > (catfish.py:10978): Gtk-WARNING **: Unknown property: > GtkInfoBar.show-close-button Traceback (most recent call last): > File "/usr/share/catfish/bin/catfish.py", line 44, in > catfish.main() File "/usr/share/catfish/catfish/__init__.py", line > 73, in main window = CatfishWindow.CatfishWindow() File > "/usr/share/catfish/catfish_lib/Window.py", line 49, in __new__ > new_object.finish_initializing(builder) File > "/usr/share/catfish/catfish/CatfishWindow.py", line 210, in > finish_initializing if SudoDialog.check_dependencies(['locate', > 'updatedb']): File "/usr/share/catfish/catfish_lib/SudoDialog.py", > line 54, in check_dependencies pexpect.TIMEOUT]) == 3: File > "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1418, > in expect timeout, searchwindowsize) File > "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1433, > in expect_list timeout, searchwindowsize) File > "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1490, > in expect_loop index = searcher.search(incoming, freshlen, > searchwindowsize) File > "/usr/lib/python2.7/site-packages/pexpect/__init__.py", line 1946, > in search match = s.search(buffer, searchstart) RuntimeError: > internal error in regular expression engine > > Any idea what's wrong here? > > Cheers, > > Niki Here's asome silly thoughts, given the "Gtk-WARNING **", it look to me that catfish can't find GTK Python bindings: 1. did you install wxPython (includes wxGTK) or wxGTK? 2. did you install anything GTK+3 or Python3 related on top of GTK+2 (wxGTK3, newer wxPython)? 3. did the devs switch to Python3? its like pulling teeth to find a full dependency list from these Debian boneheads. 1.2.2 seems to require Python3. what happens if you build and run on a plain/default Slackware (e.g. a VM)? Since my main box is a fairly well "optimized" (ie buggered) up Slack64 multilib, I dont trust errors on it until I check them out on a clean Slackware VM. - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSpkgIACgkQXvwMaW61dLeE4ACgrpKvY1mWjIYPFjxHdKD1lX0O +6sAnAt3xJbIXT+qSjtk7zQRB+d3fGAa =vGWL -----END PGP SIGNATURE----- From rworkman at slackbuilds.org Sun Jan 4 19:35:14 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 4 Jan 2015 13:35:14 -0600 Subject: [Slackbuilds-users] squid options In-Reply-To: <201501041124.24173.xgizzmo@gmail.com> References: <201501041124.24173.xgizzmo@gmail.com> Message-ID: <20150104133514.7d3924ba@home.rlworkman.net> On Sun, 4 Jan 2015 11:24:23 -0500 xgizzmo at gmail.com wrote: > On Saturday 03 January 2015 08:15:00 Helmut Hullen wrote: > > Hallo, slackbuilds-users, > > > > could it be that in the squid SBo packet the > > > > /usr/libexec/basic_*_auth > > > > files must have the suid flag? > > > > I use the "getpwnam" file, and without this flag the acl > > > > auth_param basic > > program /usr/libexec/basic_getpwnam_auth /etc/shadow > > > > produces strange error messages (it tells that there are not > > enough basic children). > > > > Viele Gruesse! > > Helmut > > From the man page Quote: > " When used for authenticating to local UNIX shadow password > databases the program must be running as root or else it won?t have > sufficient permissions to access the user password database. Such use > of this program is not recommended, but if you absolutely need to > then make the program setuid root. " > > Obviously we won't do this in the slackbuild, the sysadmin can make > that choice. I suspect that you can make it sgid shadow instead and it will work just fine - I'd try that before making it suid root. -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 info at microlinux.fr Mon Jan 5 05:38:39 2015 From: info at microlinux.fr (Niki Kovacs) Date: Mon, 05 Jan 2015 06:38:39 +0100 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54A99204.4040903@gmail.com> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> Message-ID: <54AA235F.7080205@microlinux.fr> Le 04/01/2015 20:18, King Beowulf a ?crit : > 1. did you install wxPython (includes wxGTK) or wxGTK? Maybe that's the problem. I'm running wxGTK, and not wxPython. -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From khazar at gmx.us Mon Jan 5 12:55:25 2015 From: khazar at gmx.us (Genghis Khan) Date: Mon, 5 Jan 2015 13:55:25 +0100 Subject: [Slackbuilds-users] Fontconfig warning with package culmus (was: Error while installing package culmus) In-Reply-To: <20141227163207.679cbaf1@home.rlworkman.net> References: <549D957C.1040103@slackbuilds.org> <20141227125107.2c2672aa@home.rlworkman.net> , <20141227163207.679cbaf1@home.rlworkman.net> Message-ID: There are still errors and also version (2) has not changed to 3. > Sent: Sunday, December 28, 2014 at 12:32 AM > From: "Robby Workman" > To: "David Spencer" > Cc: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Fontconfig warning with package culmus (was: Error while installing package culmus) > > On Sat, 27 Dec 2014 22:18:53 +0000 > David Spencer wrote: > > > > Thanks to Ghengis Khan. > > > > Best. Commit. Message. Ever. > > > Heh. :-) > > For the sake of clarity, there were two errors here. One was a missing > "fi" that I introduced in my earlier fix ( git id 80587f16a16eb ); this > is what willysr fixed in his commit. > > The second is what I just fixed, and it is really a fix to upstream > to account for changes in fontconfig's handling of blocks. > > -RW > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From willysr at slackbuilds.org Mon Jan 5 12:57:10 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 05 Jan 2015 19:57:10 +0700 Subject: [Slackbuilds-users] Fontconfig warning with package culmus In-Reply-To: References: <549D957C.1040103@slackbuilds.org> <20141227125107.2c2672aa@home.rlworkman.net> , <20141227163207.679cbaf1@home.rlworkman.net> Message-ID: <54AA8A26.3080000@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > There are still errors and also version (2) has not changed to 3. have you run sbopkg -r ? or even better, download it directly from http://slackbuilds.org/slackbuilds/14.1/system/culmus.tar.gz - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSqiiYACgkQiHuDdNczM4EGPQCeOnpRenXv56sWWZXUJIhLFI2k 0UwAnAptsbbyFAGUsza52sgX2N3eG280 =wEm9 -----END PGP SIGNATURE----- From genghiskhan at gmx.ca Mon Jan 5 14:47:28 2015 From: genghiskhan at gmx.ca (Genghis Khan) Date: Mon, 5 Jan 2015 15:47:28 +0100 Subject: [Slackbuilds-users] Fontconfig warning with package culmus In-Reply-To: <54AA8A26.3080000@slackbuilds.org> References: <549D957C.1040103@slackbuilds.org> <20141227125107.2c2672aa@home.rlworkman.net> , <20141227163207.679cbaf1@home.rlworkman.net> , <54AA8A26.3080000@slackbuilds.org> Message-ID: Actually, in Salix OS, slapt-src -u I did made a repository update, but, at the time, I did not take into account that the mirror that I use, was not up-to-date. Thank you very much for fixing package Culmus. > Sent: Monday, January 05, 2015 at 2:57 PM > From: "Willy Sudiarto Raharjo" > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Fontconfig warning with package culmus > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > There are still errors and also version (2) has not changed to 3. > > have you run sbopkg -r ? > or even better, download it directly from > http://slackbuilds.org/slackbuilds/14.1/system/culmus.tar.gz > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSqiiYACgkQiHuDdNczM4EGPQCeOnpRenXv56sWWZXUJIhLFI2k > 0UwAnAptsbbyFAGUsza52sgX2N3eG280 > =wEm9 > -----END PGP SIGNATURE----- > _______________________________________________ > 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 vmj at linuxbox.fi Mon Jan 5 21:32:01 2015 From: vmj at linuxbox.fi (Mikko Varri) Date: Mon, 5 Jan 2015 23:32:01 +0200 Subject: [Slackbuilds-users] libncurses / libtinfo Message-ID: <20150105213201.GB21171@linuxbox.fi> Hi, I wonder if there's already a solution for this: I'm making an update for ghc slackbuild, and the ghc bindist is built against libtinfo. AFAIK, that's just libncurses split in two, right? If I add a softlink libtinfo to libncurses, ghc seems to work, i.e. libncurses already has all the symbols of libtinfo. But should I pollute the build environment like that? Also, the package installation site would need the same softlink. The other option seems to be to use patchelf to replace the linking information. But patchelf has not, yet, released a version that supports that, so ghc slackbuild should depend on git version of patchelf. Before I spend more time on it, what's your take? -vmj From rworkman at slackbuilds.org Mon Jan 5 21:59:53 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 5 Jan 2015 15:59:53 -0600 Subject: [Slackbuilds-users] libncurses / libtinfo In-Reply-To: <20150105213201.GB21171@linuxbox.fi> References: <20150105213201.GB21171@linuxbox.fi> Message-ID: <20150105155953.30abae4a@home.rlworkman.net> On Mon, 5 Jan 2015 23:32:01 +0200 Mikko Varri wrote: > I wonder if there's already a solution for this: > > I'm making an update for ghc slackbuild, and the ghc bindist is built > against libtinfo. AFAIK, that's just libncurses split in two, right? > > If I add a softlink libtinfo to libncurses, ghc seems to work, > i.e. libncurses already has all the symbols of libtinfo. But should I > pollute the build environment like that? Also, the package > installation site would need the same softlink. > > The other option seems to be to use patchelf to replace the linking > information. But patchelf has not, yet, released a version that > supports that, so ghc slackbuild should depend on git version of > patchelf. > > Before I spend more time on it, what's your take? Ideally, volkerdi would add a symlink into Slackware proper for that, since this isn't the first time something like this has occurred. However, the second best solution IMHO, and the one that will be needed for 14.1, is to create a separate "package" at SlackBuilds.org that is basically just a symlink and a README into the docs directory that explains why it's there. Feel free to submit a "libtinfo" package. :-) -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 yalhcru at gmail.com Tue Jan 6 00:33:53 2015 From: yalhcru at gmail.com (B Watson) Date: Mon, 5 Jan 2015 19:33:53 -0500 Subject: [Slackbuilds-users] libncurses / libtinfo In-Reply-To: <20150105155953.30abae4a@home.rlworkman.net> References: <20150105213201.GB21171@linuxbox.fi> <20150105155953.30abae4a@home.rlworkman.net> Message-ID: On 1/5/15, Robby Workman wrote: > Ideally, volkerdi would add a symlink into Slackware proper for that, > since this isn't the first time something like this has occurred. > However, the second best solution IMHO, and the one that will be needed > for 14.1, is to create a separate "package" at SlackBuilds.org that > is basically just a symlink and a README into the docs directory that > explains why it's there. Feel free to submit a "libtinfo" package. :-) This seems like it might be a bad idea. I can imagine some configure script detecting that libtinfo.so is found, and getting confused... Maybe for the binary build of ghc, a better solution would be to stick the libtinfo.so symlink in a private lib dir (say, /usr/lib(64)/ghc/libtinfo.so), along with the real ghc binar(y|ies), and have the ghc commands in /usr/bin actually be shell scripts that add /usr/lib/ghc to LD_LIBRARY_PATH and then exec /usr/lib/ghc/$0. This is ugly, but at least the ugly is confined to the ghc package only, and the system lib dir won't get polluted. Another idea (that may be impractical/impossible): You're using a binary build I assume because ghc is a Haskell compiler that's written in Haskell. Maybe it's worth bootstrapping it: temporarily install the binary build (in $PKG/bootstrap, if the binary build can handle being install in an arbitrary location), then use that to compile the real ghc that you're going to install with prefix=$PKG/usr, then rm -rf $PKG/bootstrap. You'd have to make the libtinfo symlink in $PKG/bootstrap and use LD_LIBRARY_PATH for bootstrapping, but hopefully you'd end up with a ghc that links to libncurses (which might require patching the ghc source, I haven't looked at it, as I do not speak Haskell). From info at microlinux.fr Tue Jan 6 08:46:01 2015 From: info at microlinux.fr (Niki Kovacs) Date: Tue, 06 Jan 2015 09:46:01 +0100 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54A99204.4040903@gmail.com> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> Message-ID: <54ABA0C9.4060109@microlinux.fr> Le 04/01/2015 20:18, King Beowulf a ?crit : > Here's asome silly thoughts, given the "Gtk-WARNING **", it look to me > that catfish can't find GTK Python bindings: > 1. did you install wxPython (includes wxGTK) or wxGTK? > 2. did you install anything GTK+3 or Python3 related on top of GTK+2 > (wxGTK3, newer wxPython)? > 3. did the devs switch to Python3? its like pulling teeth to find a > full dependency list from these Debian boneheads. 1.2.2 seems to > require Python3. I replaced wxGTK by wxPython, but I still get the exact same error. -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From baildon.research at googlemail.com Tue Jan 6 10:17:10 2015 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 6 Jan 2015 10:17:10 +0000 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54ABA0C9.4060109@microlinux.fr> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> <54ABA0C9.4060109@microlinux.fr> Message-ID: > I replaced wxGTK by wxPython, but I still get the exact same error. It looks like this: http://bugs.python.org/issue17998 which affects python-2.7.5. You could try SBo's python3? That would probably be neater than building your own python-2.7.6+ to replace Slackware's. Best regards -D. From simotrone at gmail.com Tue Jan 6 10:53:15 2015 From: simotrone at gmail.com (Simotrone) Date: Tue, 6 Jan 2015 11:53:15 +0100 Subject: [Slackbuilds-users] update ledger link Message-ID: The Homepage project link should to be https://github.com/ledger/ledger/wiki http://slackbuilds.org/repository/14.1/business/ledger The ledger package on SBo is outdated. I saw also this recent thread on ML http://lists.slackbuilds.org/pipermail/slackbuilds-users/2014-September/012960.html I wrote to Xavier to ask about maintaining (don't know if Berntsen know anything about it). sim -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Jan 6 13:06:17 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 06 Jan 2015 20:06:17 +0700 Subject: [Slackbuilds-users] update ledger link In-Reply-To: References: Message-ID: <54ABDDC9.1040604@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The Homepage project link should to be > https://github.com/ledger/ledger/wiki > > http://slackbuilds.org/repository/14.1/business/ledger Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSr3cgACgkQiHuDdNczM4G7KACbBVmcwjV+W1Axv6aFl1PEWuZK UqkAnAhxmbq04Iodqvyw5xtVHe1FE0zh =aUgj -----END PGP SIGNATURE----- From ts at websafe.pl Wed Jan 7 22:30:48 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Wed, 07 Jan 2015 23:30:48 +0100 Subject: [Slackbuilds-users] xbmc - missing tarball Message-ID: <54ADB398.1010000@websafe.pl> Hello, in the xbmc slackbuild http://slackbuilds.org/repository/14.1/multimedia/xbmc/ the location of xbmc-13.1.tar.gz has changed to http://mirrors.kodi.tv/releases/source/old/xbmc-13.1.tar.gz -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From C.J.Theunissen at differ.nl Wed Jan 7 23:31:53 2015 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Thu, 8 Jan 2015 00:31:53 +0100 (CET) Subject: [Slackbuilds-users] openjdk (7u60): build failure (depending on date). Message-ID: Running the openjdk.SlackBuild script fails currently (since Dec 30, 2014) with the error: [...] /junk/openjdk/icedtea-build/bootstrap/jdk1.6.0/bin/java -XX:-PrintVMOptions -XX:+UnlockDiagnosticVMOptions -XX:-LogVMOutput -Xmx512m -Xms512 m -XX:PermSize=32m -XX:MaxPermSize=160m -jar /junk/openjdk/icedtea-build/openjdk.build-boot/btjars/generatecurrencydata.jar -o /junk/openjdk /icedtea-build/openjdk.build-boot/lib/currency.data.temp \ < ../../../src/share/classes/java/util/CurrencyData.properties Error: time is more than 10 years from present: 1104530400000 java.lang.RuntimeException: time is more than 10 years from present: 1104530400000 at build.tools.generatecurrencydata.GenerateCurrencyData.makeSpecialCaseEntry(GenerateCurrencyData.java:285) at build.tools.generatecurrencydata.GenerateCurrencyData.buildMainAndSpecialCaseTables(GenerateCurrencyData.java:225) at build.tools.generatecurrencydata.GenerateCurrencyData.main(GenerateCurrencyData.java:154) gmake[5]: *** [/junk/openjdk/icedtea-build/openjdk.build-boot/lib/currency.data] Error 1 gmake[5]: Leaving directory `/junk/openjdk/icedtea-build/openjdk-boot/jdk/make/java/java' gmake[4]: *** [all] Error 1 gmake[4]: Leaving directory `/junk/openjdk/icedtea-build/openjdk-boot/jdk/make/java' gmake[3]: *** [all] Error 1 gmake[3]: Leaving directory `/junk/openjdk/icedtea-build/openjdk-boot/jdk/make' gmake[2]: *** [jdk-build] Error 2 gmake[2]: Leaving directory `/junk/openjdk/icedtea-build/openjdk-boot' gmake[1]: *** [build_product_image] Error 2 gmake[1]: Leaving directory `/junk/openjdk/icedtea-build/openjdk-boot' make: *** [stamps/icedtea-boot.stamp] Error 2 See also this thread: http://mail-index.netbsd.org/pkgsrc-users/2014/12/30/msg020843.html As a workaround I ran the script without problems on a virtual machine where the clock was set 10 days back. Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From willysr at slackbuilds.org Thu Jan 8 00:10:00 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 08 Jan 2015 07:10:00 +0700 Subject: [Slackbuilds-users] xbmc - missing tarball In-Reply-To: <54ADB398.1010000@websafe.pl> References: <54ADB398.1010000@websafe.pl> Message-ID: <54ADCAD8.9010206@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > in the xbmc slackbuild > http://slackbuilds.org/repository/14.1/multimedia/xbmc/ > > the location of xbmc-13.1.tar.gz has changed to > > http://mirrors.kodi.tv/releases/source/old/xbmc-13.1.tar.gz Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlStytcACgkQiHuDdNczM4HFYQCdGgq0FDWqNcSErSYX6Lef94TM Jw8An3YaLG7AlKhvL2jbkQ9BeTdnjG/I =3s61 -----END PGP SIGNATURE----- From kingbeowulf at gmail.com Thu Jan 8 03:40:27 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 07 Jan 2015 19:40:27 -0800 Subject: [Slackbuilds-users] openjdk (7u60): build failure (depending on date). In-Reply-To: References: Message-ID: <54ADFC2B.1020603@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/07/2015 03:31 PM, Kees Theunissen wrote: > Running the openjdk.SlackBuild script fails currently (since Dec > 30, 2014) with the error: > > [...] /junk/openjdk/icedtea-build/bootstrap/jdk1.6.0/bin/java > -XX:-PrintVMOptions -XX:+UnlockDiagnosticVMOptions -XX:-LogVMOutput > -Xmx512m -Xms512 m -XX:PermSize=32m -XX:MaxPermSize=160m -jar > /junk/openjdk/icedtea-build/openjdk.build-boot/btjars/generatecurrencydata.jar > -o /junk/openjdk > /icedtea-build/openjdk.build-boot/lib/currency.data.temp \ < > ../../../src/share/classes/java/util/CurrencyData.properties Error: > time is more than 10 years from present: 1104530400000 > java.lang.RuntimeException: time is more than 10 years from > present: 1104530400000 > > See also this thread: > http://mail-index.netbsd.org/pkgsrc-users/2014/12/30/msg020843.html > > > > As a workaround I ran the script without problems on a virtual > machine where the clock was set 10 days back. > > The fix in the listed in the thread for the currency codes is ugly, as is your workaround. It was fixed months ago in the JDK 7 Updates Master: http://hg.openjdk.java.net/jdk7u/jdk7u/jdk/rev/74a70385c21d A better patch for openjdk-7u60 is here: https://github.com/NixOS/nixpkgs/commit/9b81769950b6d0221643c7b0758d894f7742a62a that extends the currency date check out to 20 years. Or better, there should be a openjdk-7u80, but pulling tags out of mercurial befuddles me. - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSt/CkACgkQXvwMaW61dLdIoQCeOVGxyN84AS9ygyuoI8i0b4XA wo0An00H3VuyunCwji19p7rSXPaomKSC =Jmhm -----END PGP SIGNATURE----- From h.gersen at gmail.com Thu Jan 8 10:54:47 2015 From: h.gersen at gmail.com (Henkjan) Date: Thu, 8 Jan 2015 10:54:47 +0000 (UTC) Subject: [Slackbuilds-users] unison slackbuild - triggers fatal error for windows binaries that are compiled using oclam3 Message-ID: <509334903.404.1420714488181.JavaMail.tomcat@ip-10-139-87-144> Last week I upgraded unison on slackware without paying attention and when I today tried to sync machines this triggered a scary fatal error when trying to sync a windows laptop running a precompiled 2.40.63. It turns out that the windows binaries are compiled using oclam3 while the slackbuild now uses oclam4. The problem I experienced and the suggested solution is in the following topic on the unison mailing list: https://groups.yahoo.com/neo/groups/unison-users/conversations/topics/10453 Upgrading the slackbuild to 3.4.102 indeed works again for me; no other changes needed to the slackbuild (it still needs the patch that is being applied). I didn't try a later version number; however seeing this problem it might be worth upgrading the version currently available on slackbuilds.org to 3.4.102 to prevent others having the same scary experience. ;) -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Jan 8 13:30:48 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 08 Jan 2015 20:30:48 +0700 Subject: [Slackbuilds-users] unison slackbuild - triggers fatal error for windows binaries that are compiled using oclam3 In-Reply-To: <509334903.404.1420714488181.JavaMail.tomcat@ip-10-139-87-144> References: <509334903.404.1420714488181.JavaMail.tomcat@ip-10-139-87-144> Message-ID: <54AE8688.9010203@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Last week I upgraded unison on slackware without paying attention > and when I today tried to sync machines this triggered a scary > fatal error when trying to sync a windows laptop running a > precompiled 2.40.63. It turns out that the windows binaries are > compiled using oclam3 while the slackbuild now uses oclam4. > > The problem I experienced and the suggested solution is in the > following topic on the unison mailing list: > > https://groups.yahoo.com/neo/groups/unison-users/conversations/topics/10453 > > Upgrading the slackbuild to 3.4.102 indeed works again for me; no > other changes needed to the slackbuild (it still needs the patch > that is being applied). I didn't try a later version number; > however seeing this problem it might be worth upgrading the version > currently available on slackbuilds.org to 3.4.102 to prevent others > having the same scary experience. ;) The current maintainer no longer update this package since 2011, so if you are using it intensively, i would suggest that you take maintainership of this package and submit an update - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSuhocACgkQiHuDdNczM4FlUgCgg/6Gg50Kn8nFWgVnJ1hSMu9c gPYAn3WzJ06tYWWITMHTgXZsWSVevF++ =uCly -----END PGP SIGNATURE----- From mjjzf at syntaktisk.dk Thu Jan 8 13:37:46 2015 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Thu, 8 Jan 2015 14:37:46 +0100 Subject: [Slackbuilds-users] Lxpanel build issue Message-ID: <20150108143746.2b534e5b@espero.syntaktisk.dk> Dear Slackbuilders, I am experiencing an issue with building Lxpanel. I have the deps, but I get: * * * make all-recursive make[1]: Entering directory `/tmp/SBo/lxpanel-0.8.0' Making all in src make[2]: Entering directory `/tmp/SBo/lxpanel-0.8.0/src' /bin/sh ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DPACKAGE_LIB_DIR=\""/usr/lib"\" -DPACKAGE_DATA_DIR=\""/usr/share/lxpanel"\" -DPACKAGE_UI_DIR=\""/usr/share/lxpanel/ui"\" -DPACKAGE_BIN_DIR=\""/usr/bin"\" -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/libdrm -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/menu-cache -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/libdrm -I/usr/include/harfbuzz -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -O2 -march=i486 -mtune=i686 -MT liblxpanel_la-misc.lo -MD -MP -MF .deps/liblxpanel_la-misc.Tpo -c -o liblxpanel_la-misc.lo `test -f 'misc.c' || echo './'`misc.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -DPACKAGE_LIB_DIR=\"/usr/lib\" -DPACKAGE_DATA_DIR=\"/usr/share/lxpanel\" -DPACKAGE_UI_DIR=\"/usr/share/lxpanel/ui\" -DPACKAGE_BIN_DIR=\"/usr/bin\" -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/libdrm -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0 -I/usr/include/menu-cache -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng14 -I/usr/include/libdrm -I/usr/include/harfbuzz -DG_DISABLE_ASSERT -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -O2 -march=i486 -mtune=i686 -MT liblxpanel_la-misc.lo -MD -MP -MF .deps/liblxpanel_la-misc.Tpo -c misc.c -fPIC -DPIC -o .libs/liblxpanel_la-misc.o In file included from /usr/include/libfm/fm-gtk.h:25:0, from misc.c:30: /usr/include/libfm/fm.h:26:24: fatal error: fm-version.h: No such file or directory #include "fm-version.h" ^ compilation terminated. make[2]: *** [liblxpanel_la-misc.lo] Error 1 make[2]: Leaving directory `/tmp/SBo/lxpanel-0.8.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/lxpanel-0.8.0' make: *** [all] Error 2 * * * I completely fail to see what the issue might be. Any pointers? All the best, have a good new year and thank you for the builds, Morten __ Morten Juhl-Johansen Z?lde-Fej?r syntaktisk.dk * mjjzf at syntaktisk.dk From willysr at slackbuilds.org Thu Jan 8 13:39:30 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 08 Jan 2015 20:39:30 +0700 Subject: [Slackbuilds-users] Lxpanel build issue In-Reply-To: <20150108143746.2b534e5b@espero.syntaktisk.dk> References: <20150108143746.2b534e5b@espero.syntaktisk.dk> Message-ID: <54AE8892.2000402@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/08/2015 08:37 PM, Morten Juhl-Johansen Z?lde-Fej?r wrote: > Dear Slackbuilders, > > I am experiencing an issue with building Lxpanel. I have the deps, > but I get: > > * * * make all-recursive make[1]: Entering directory > `/tmp/SBo/lxpanel-0.8.0' Making all in src make[2]: Entering > directory `/tmp/SBo/lxpanel-0.8.0/src' /bin/sh ../libtool --tag=CC > --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. > -DPACKAGE_LIB_DIR=\""/usr/lib"\" > -DPACKAGE_DATA_DIR=\""/usr/share/lxpanel"\" > -DPACKAGE_UI_DIR=\""/usr/share/lxpanel/ui"\" > -DPACKAGE_BIN_DIR=\""/usr/bin"\" > -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread > -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include > -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/freetype2 > -I/usr/include/libpng14 -I/usr/include/libdrm > -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ > -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0 > -I/usr/include/menu-cache -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 > -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/freetype2 -I/usr/include/libpng14 > -I/usr/include/libdrm -I/usr/include/harfbuzz -DG_DISABLE_ASSERT > -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -O2 -march=i486 > -mtune=i686 -MT liblxpanel_la-misc.lo -MD -MP -MF > .deps/liblxpanel_la-misc.Tpo -c -o liblxpanel_la-misc.lo `test -f > 'misc.c' || echo './'`misc.c libtool: compile: gcc -DHAVE_CONFIG_H > -I. -I.. -I.. -DPACKAGE_LIB_DIR=\"/usr/lib\" > -DPACKAGE_DATA_DIR=\"/usr/share/lxpanel\" > -DPACKAGE_UI_DIR=\"/usr/share/lxpanel/ui\" > -DPACKAGE_BIN_DIR=\"/usr/bin\" > -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread > -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include > -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/freetype2 > -I/usr/include/libpng14 -I/usr/include/libdrm > -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ > -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0 > -I/usr/include/menu-cache -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 > -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 > -I/usr/include/freetype2 -I/usr/include/libpng14 > -I/usr/include/libdrm -I/usr/include/harfbuzz -DG_DISABLE_ASSERT > -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -O2 -march=i486 > -mtune=i686 -MT liblxpanel_la-misc.lo -MD -MP -MF > .deps/liblxpanel_la-misc.Tpo -c misc.c -fPIC -DPIC -o > .libs/liblxpanel_la-misc.o In file included from > /usr/include/libfm/fm-gtk.h:25:0, from misc.c:30: > /usr/include/libfm/fm.h:26:24: fatal error: fm-version.h: No such > file or directory #include "fm-version.h" ^ compilation terminated. > make[2]: *** [liblxpanel_la-misc.lo] Error 1 make[2]: Leaving > directory `/tmp/SBo/lxpanel-0.8.0/src' make[1]: *** [all-recursive] > Error 1 make[1]: Leaving directory `/tmp/SBo/lxpanel-0.8.0' make: > *** [all] Error 2 > > * * * > > I completely fail to see what the issue might be. Any pointers? It seems you do not have libfm - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSuiJIACgkQiHuDdNczM4ECxwCfUpcS0vvTycaOIuZn7sDZfqOo mEcAniMuN9XtWIXbVNPbZPO9u5S5LUdv =SVzj -----END PGP SIGNATURE----- From mjjzf at syntaktisk.dk Thu Jan 8 13:42:19 2015 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Thu, 8 Jan 2015 14:42:19 +0100 Subject: [Slackbuilds-users] Lxpanel build issue In-Reply-To: <54AE8892.2000402@slackbuilds.org> References: <20150108143746.2b534e5b@espero.syntaktisk.dk> <54AE8892.2000402@slackbuilds.org> Message-ID: <20150108144219.337c1b86@espero.syntaktisk.dk> No, this happens as part of an upgrade: ~ $ ls /var/log/packages/ | grep libfm libfm-1.2.3-i486-2_SBo But thank you! -M On Thu, 08 Jan 2015 20:39:30 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01/08/2015 08:37 PM, Morten Juhl-Johansen Z?lde-Fej?r wrote: > > Dear Slackbuilders, > > > > I am experiencing an issue with building Lxpanel. I have the deps, > > but I get: > > > > * * * make all-recursive make[1]: Entering directory > > `/tmp/SBo/lxpanel-0.8.0' Making all in src make[2]: Entering > > directory `/tmp/SBo/lxpanel-0.8.0/src' /bin/sh ../libtool --tag=CC > > --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I.. > > -DPACKAGE_LIB_DIR=\""/usr/lib"\" > > -DPACKAGE_DATA_DIR=\""/usr/share/lxpanel"\" > > -DPACKAGE_UI_DIR=\""/usr/share/lxpanel/ui"\" > > -DPACKAGE_BIN_DIR=\""/usr/bin"\" > > -DPACKAGE_LOCALE_DIR=\""/usr/share/locale"\" -pthread > > -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include > > -I/usr/include/atk-1.0 -I/usr/include/cairo > > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 > > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > > -I/usr/include/pixman-1 -I/usr/include/freetype2 > > -I/usr/include/libpng14 -I/usr/include/libdrm > > -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ > > -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0 > > -I/usr/include/menu-cache -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 > > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 > > -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 > > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 > > -I/usr/include/freetype2 -I/usr/include/libpng14 > > -I/usr/include/libdrm -I/usr/include/harfbuzz -DG_DISABLE_ASSERT > > -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -O2 -march=i486 > > -mtune=i686 -MT liblxpanel_la-misc.lo -MD -MP -MF > > .deps/liblxpanel_la-misc.Tpo -c -o liblxpanel_la-misc.lo `test -f > > 'misc.c' || echo './'`misc.c libtool: compile: gcc -DHAVE_CONFIG_H > > -I. -I.. -I.. -DPACKAGE_LIB_DIR=\"/usr/lib\" > > -DPACKAGE_DATA_DIR=\"/usr/share/lxpanel\" > > -DPACKAGE_UI_DIR=\"/usr/share/lxpanel/ui\" > > -DPACKAGE_BIN_DIR=\"/usr/bin\" > > -DPACKAGE_LOCALE_DIR=\"/usr/share/locale\" -pthread > > -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include > > -I/usr/include/atk-1.0 -I/usr/include/cairo > > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 > > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > > -I/usr/include/pixman-1 -I/usr/include/freetype2 > > -I/usr/include/libpng14 -I/usr/include/libdrm > > -I/usr/include/harfbuzz -I/usr/include/gio-unix-2.0/ > > -I/usr/include/libwnck-1.0 -I/usr/include/startup-notification-1.0 > > -I/usr/include/menu-cache -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -pthread -I/usr/include/gtk-2.0 > > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 > > -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 > > -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 > > -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 > > -I/usr/include/freetype2 -I/usr/include/libpng14 > > -I/usr/include/libdrm -I/usr/include/harfbuzz -DG_DISABLE_ASSERT > > -DG_DISABLE_CHECKS -DG_DISABLE_CAST_CHECKS -O2 -march=i486 > > -mtune=i686 -MT liblxpanel_la-misc.lo -MD -MP -MF > > .deps/liblxpanel_la-misc.Tpo -c misc.c -fPIC -DPIC -o > > .libs/liblxpanel_la-misc.o In file included from > > /usr/include/libfm/fm-gtk.h:25:0, from misc.c:30: > > /usr/include/libfm/fm.h:26:24: fatal error: fm-version.h: No such > > file or directory #include "fm-version.h" ^ compilation terminated. > > make[2]: *** [liblxpanel_la-misc.lo] Error 1 make[2]: Leaving > > directory `/tmp/SBo/lxpanel-0.8.0/src' make[1]: *** [all-recursive] > > Error 1 make[1]: Leaving directory `/tmp/SBo/lxpanel-0.8.0' make: > > *** [all] Error 2 > > > > * * * > > > > I completely fail to see what the issue might be. Any pointers? > > It seems you do not have libfm > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSuiJIACgkQiHuDdNczM4ECxwCfUpcS0vvTycaOIuZn7sDZfqOo > mEcAniMuN9XtWIXbVNPbZPO9u5S5LUdv > =SVzj > -----END PGP SIGNATURE----- > _______________________________________________ > 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/ > __ Morten Juhl-Johansen Z?lde-Fej?r syntaktisk.dk * mjjzf at syntaktisk.dk From willysr at slackbuilds.org Thu Jan 8 13:49:11 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 08 Jan 2015 20:49:11 +0700 Subject: [Slackbuilds-users] Lxpanel build issue In-Reply-To: <20150108144219.337c1b86@espero.syntaktisk.dk> References: <20150108143746.2b534e5b@espero.syntaktisk.dk> <54AE8892.2000402@slackbuilds.org> <20150108144219.337c1b86@espero.syntaktisk.dk> Message-ID: <54AE8AD7.6020100@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > No, this happens as part of an upgrade: > > ~ $ ls /var/log/packages/ | grep libfm libfm-1.2.3-i486-2_SBo I just tested in slackware64-14.1 and here's the result libfm-extra: MD5SUM check for libfm-1.2.3.tar.xz ... OK Building package libfm-extra-1.2.3-x86_64-1_SBo.tgz ... OK Installing package libfm-extra-1.2.3-x86_64-1_SBo.tgz ... OK menu-cache: MD5SUM check for menu-cache-1.0.0.tar.xz ... OK Building package menu-cache-1.0.0-x86_64-1_SBo.tgz ... OK Installing package menu-cache-1.0.0-x86_64-1_SBo.tgz ... OK libfm: MD5SUM check for libfm-1.2.3.tar.xz ... OK Building package libfm-1.2.3-x86_64-2_SBo.tgz ... OK Installing package libfm-1.2.3-x86_64-2_SBo.tgz ... OK lxmenu-data: MD5SUM check for lxmenu-data-0.1.4.tar.xz ... OK Building package lxmenu-data-0.1.4-x86_64-1_SBo.tgz ... OK Installing package lxmenu-data-0.1.4-x86_64-1_SBo.tgz ... OK lxpanel: MD5SUM check for lxpanel-0.8.0.tar.xz ... OK Building package lxpanel-0.8.0-x86_64-1_SBo.tgz ... OK Installing package lxpanel-0.8.0-x86_64-1_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSuitcACgkQiHuDdNczM4EukQCghO/sfjBeS8ooXO9F5zIkIH7t juIAoKY+LMu79B2/FAHT+wjMcfjp8no3 =B6nO -----END PGP SIGNATURE----- From mjjzf at syntaktisk.dk Thu Jan 8 14:04:17 2015 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Thu, 8 Jan 2015 15:04:17 +0100 Subject: [Slackbuilds-users] Lxpanel build issue In-Reply-To: <54AE8AD7.6020100@slackbuilds.org> References: <20150108143746.2b534e5b@espero.syntaktisk.dk> <54AE8892.2000402@slackbuilds.org> <20150108144219.337c1b86@espero.syntaktisk.dk> <54AE8AD7.6020100@slackbuilds.org> Message-ID: <20150108150417.46d1ba71@espero.syntaktisk.dk> Aha! It worked when I installed libfm-extra - excellent! That is not noted as a dependency., it should be mentioned. Thank you for your help. All the best, Morten On Thu, 08 Jan 2015 20:49:11 +0700 Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > No, this happens as part of an upgrade: > > > > ~ $ ls /var/log/packages/ | grep libfm libfm-1.2.3-i486-2_SBo > > I just tested in slackware64-14.1 and here's the result > > libfm-extra: > MD5SUM check for libfm-1.2.3.tar.xz ... OK > Building package libfm-extra-1.2.3-x86_64-1_SBo.tgz ... OK > Installing package libfm-extra-1.2.3-x86_64-1_SBo.tgz ... OK > > menu-cache: > MD5SUM check for menu-cache-1.0.0.tar.xz ... OK > Building package menu-cache-1.0.0-x86_64-1_SBo.tgz ... OK > Installing package menu-cache-1.0.0-x86_64-1_SBo.tgz ... OK > > libfm: > MD5SUM check for libfm-1.2.3.tar.xz ... OK > Building package libfm-1.2.3-x86_64-2_SBo.tgz ... OK > Installing package libfm-1.2.3-x86_64-2_SBo.tgz ... OK > > lxmenu-data: > MD5SUM check for lxmenu-data-0.1.4.tar.xz ... OK > Building package lxmenu-data-0.1.4-x86_64-1_SBo.tgz ... OK > Installing package lxmenu-data-0.1.4-x86_64-1_SBo.tgz ... OK > > lxpanel: > MD5SUM check for lxpanel-0.8.0.tar.xz ... OK > Building package lxpanel-0.8.0-x86_64-1_SBo.tgz ... OK > Installing package lxpanel-0.8.0-x86_64-1_SBo.tgz ... OK > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSuitcACgkQiHuDdNczM4EukQCghO/sfjBeS8ooXO9F5zIkIH7t > juIAoKY+LMu79B2/FAHT+wjMcfjp8no3 > =B6nO > -----END PGP SIGNATURE----- > _______________________________________________ > 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/ > __ Morten Juhl-Johansen Z?lde-Fej?r syntaktisk.dk * mjjzf at syntaktisk.dk From matteo.bernardini at gmail.com Thu Jan 8 14:06:24 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 8 Jan 2015 15:06:24 +0100 Subject: [Slackbuilds-users] Lxpanel build issue In-Reply-To: <20150108150417.46d1ba71@espero.syntaktisk.dk> References: <20150108143746.2b534e5b@espero.syntaktisk.dk> <54AE8892.2000402@slackbuilds.org> <20150108144219.337c1b86@espero.syntaktisk.dk> <54AE8AD7.6020100@slackbuilds.org> <20150108150417.46d1ba71@espero.syntaktisk.dk> Message-ID: 2015-01-08 15:04 GMT+01:00 Morten Juhl-Johansen Z?lde-Fej?r : > Aha! > It worked when I installed libfm-extra - excellent! > That is not noted as a dependency., it should be mentioned. sorry, I just saw this: libfm-extra is a new dependency of menu-cache >= 1.0. Matteo From willysr at slackbuilds.org Thu Jan 8 15:09:09 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 8 Jan 2015 22:09:09 +0700 Subject: [Slackbuilds-users] Lxpanel build issue In-Reply-To: <20150108150417.46d1ba71@espero.syntaktisk.dk> References: <20150108143746.2b534e5b@espero.syntaktisk.dk> <54AE8892.2000402@slackbuilds.org> <20150108144219.337c1b86@espero.syntaktisk.dk> <54AE8AD7.6020100@slackbuilds.org> <20150108150417.46d1ba71@espero.syntaktisk.dk> Message-ID: > It worked when I installed libfm-extra - excellent! > That is not noted as a dependency., it should be mentioned. > Thank you for your help. REQUIRES only list first level of dependency, so you need to check whether a dependency requires another package or not I simply use sbopkg + sqg to generate all the queues files which list all the dep and build it using a correct order -- Willy Sudiarto Raharjo From hostmaster at slackonly.com Thu Jan 8 17:09:01 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Thu, 08 Jan 2015 19:09:01 +0200 Subject: [Slackbuilds-users] 7plus Message-ID: <54AEB9AD.8020009@slackonly.com> Hi, 7plus source seams to be down as the site http://sharon.esrac.ele.tue.nl/pub/linux/ I have uploaded here: https://slackonly.com/pub/sources/ham/7plus/7pl225sr.zip checksum matches... From rshepard at appl-ecosys.com Thu Jan 8 17:24:21 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Thu, 8 Jan 2015 09:24:21 -0800 (PST) Subject: [Slackbuilds-users] Postfix-2.11.3 test warning message Message-ID: Upgraded to postfix-2.11.3 with the SBo script. Now when I restart the tool I see many instances of this message on the v.t.: /usr/libexec/postfix/post-install: line 504: test: too many arguments Postfix runs, but since this warning has not appeared with previous versions I wonder if someone can look at it and see what needs to be fixed. Rich From mario at slackware.hr Thu Jan 8 21:04:48 2015 From: mario at slackware.hr (Mario Preksavec) Date: Thu, 08 Jan 2015 22:04:48 +0100 Subject: [Slackbuilds-users] Postfix-2.11.3 test warning message In-Reply-To: References: Message-ID: <54AEF0F0.20101@slackware.hr> On 01/08/2015 06:24 PM, Rich Shepard wrote: > Upgraded to postfix-2.11.3 with the SBo script. Now when I restart the > tool I see many instances of this message on the v.t.: > > /usr/libexec/postfix/post-install: line 504: test: too many arguments > > Postfix runs, but since this warning has not appeared with previous > versions I wonder if someone can look at it and see what needs to be > fixed. > > Rich What was the version that you upgraded from? None of my systems showed this error on minor updates and major version upgrades. Line 504 reads: test -r $path -a "$type" != "d" && obsolete="$obsolete $path" Best guess where it's coming from is that unquoted $path variable. Looking further up in the post-install file, this one gets parsed: /usr/libexec/postfix/postfix-files Although it's probably unlikely, check it for spaces and odd characters, this should probably do: grep '^$.* .*' /usr/libexec/postfix/postfix-files Preferably, check if any of these have such characters (in main.cf and such): $command_directory $config_directory $daemon_directory $data_directory $html_directory $mailq_path $manpage_directory $newaliases_path $queue_directory $readme_directory $sample_directory $sendmail_path -- Mario From ts at websafe.pl Thu Jan 8 21:42:15 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 08 Jan 2015 22:42:15 +0100 Subject: [Slackbuilds-users] virt-manager - hompage changed Message-ID: <54AEF9B7.9070007@websafe.pl> http://virt-manager.et.redhat.com is not valid anymore. The new homepage is located at http://virt-manager.org/ -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Thu Jan 8 23:42:26 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 09 Jan 2015 06:42:26 +0700 Subject: [Slackbuilds-users] virt-manager - hompage changed In-Reply-To: <54AEF9B7.9070007@websafe.pl> References: <54AEF9B7.9070007@websafe.pl> Message-ID: <54AF15E2.1010103@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > http://virt-manager.et.redhat.com is not valid anymore. > > The new homepage is located at http://virt-manager.org/ > > > fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSvFeEACgkQiHuDdNczM4HmLACgnIA7sP2tl+I+du7D7muo5hpD RoIAoJQ6a55tfvWq0GM1D7npRmNqFPjL =Pm/e -----END PGP SIGNATURE----- From willysr at slackbuilds.org Fri Jan 9 00:17:35 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 09 Jan 2015 07:17:35 +0700 Subject: [Slackbuilds-users] 7plus In-Reply-To: <54AEB9AD.8020009@slackonly.com> References: <54AEB9AD.8020009@slackonly.com> Message-ID: <54AF1E1F.7020807@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > 7plus source seams to be down as the site > http://sharon.esrac.ele.tue.nl/pub/linux/ I have uploaded here: > https://slackonly.com/pub/sources/ham/7plus/7pl225sr.zip checksum > matches... fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSvHh4ACgkQiHuDdNczM4F2dQCgsIPc9znyLqOs9otgRCb5uOCx wlwAn0OUsTMPGN4NDujofQY53dlJH+QA =SC0C -----END PGP SIGNATURE----- From mario at slackware.hr Fri Jan 9 02:33:27 2015 From: mario at slackware.hr (Mario Preksavec) Date: Fri, 09 Jan 2015 03:33:27 +0100 Subject: [Slackbuilds-users] Postfix-2.11.3 test warning message In-Reply-To: References: <54AEF0F0.20101@slackware.hr> Message-ID: <54AF3DF7.3030101@slackware.hr> On 01/09/2015 01:55 AM, Rich Shepard wrote: > On Thu, 8 Jan 2015, Mario Preksavec wrote: > >> What was the version that you upgraded from? None of my systems showed >> this error on minor updates and major version upgrades. > > Mario, > > Upgraded from 2.11.2. > >> Line 504 reads: >> >> test -r $path -a "$type" != "d" && obsolete="$obsolete >> $path" >> >> Best guess where it's coming from is that unquoted $path variable. > > Bingo! I quoted $path and restarted postfix and the warning went away. > > It's interesting that you have the same line in your version as I had in > mine, but did not see the warning when postfix started. > > Thanks very much, > > Rich You are very welcome, although it would probably make more sense to clean up paths in configuration files and avoid post-install file hackery... :-) -- Mario From kingbeowulf at gmail.com Fri Jan 9 05:40:49 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 08 Jan 2015 21:40:49 -0800 Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 Message-ID: <54AF69E1.1040104@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Perhaps the README was not sufficiently clear. To enable USB pass through on Slackware 14.1, you will download two (2) source packages: qemu-2.2.0.tar.bz2 libusb-1.0.19.tar.xz Then you will invoke: LIBUSB=yes ./qemu.SlackBuild Then you will upgradepkg --install-new qemu-2.2.0-$ARCH-1_SBo.tgz That still won't get you USB Passthrough, since /dev/bus/usb/XXX is owned root:root. But that's another story. Please DO NOT attempt to upgradepkg libusb-1.0.19.tar.xz If you do not need have USB pass through, run ./qemu.SlackBuild and ignore libusb-1.0.19.tar.xz Thanks, Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSvaeAACgkQXvwMaW61dLc/PACgn3RqxNXThm7JH7RpPjxlTxD/ 4NEAn0gaK0km/X9QA/jdStcLZqezVod4 =+r5R -----END PGP SIGNATURE----- From genghiskhan at gmx.ca Fri Jan 9 05:49:14 2015 From: genghiskhan at gmx.ca (Genghis Khan) Date: Fri, 9 Jan 2015 06:49:14 +0100 Subject: [Slackbuilds-users] Update PhotoQt URL Message-ID: Old URL http://photoqt.org/pkgs/photoqt-1.0.tar.gz New URL http://photoqt.org/oldRel/photoqt-1.0.tar.gz From genghiskhan at gmx.ca Fri Jan 9 06:05:29 2015 From: genghiskhan at gmx.ca (Genghis Khan) Date: Fri, 9 Jan 2015 07:05:29 +0100 Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 Message-ID: I have troubles to build VirtualBox, and the .run file from official website, for some reason, does not let me connect USB devices; thus I install an FTP server (e.g. FileZilla) in guest OS and transfer files using FTP client (e.g. gFTP) on host system. HTH > Sent: Friday, January 09, 2015 at 7:40 AM > From: "King Beowulf" > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Perhaps the README was not sufficiently clear. To enable USB pass > through on Slackware 14.1, you will download two (2) source packages: > > qemu-2.2.0.tar.bz2 > libusb-1.0.19.tar.xz > > Then you will invoke: > > LIBUSB=yes ./qemu.SlackBuild > > Then you will > > upgradepkg --install-new qemu-2.2.0-$ARCH-1_SBo.tgz > > That still won't get you USB Passthrough, since > > /dev/bus/usb/XXX > > is owned root:root. But that's another story. > > Please DO NOT attempt to > > upgradepkg libusb-1.0.19.tar.xz > > If you do not need have USB pass through, run > > ./qemu.SlackBuild > > and ignore libusb-1.0.19.tar.xz > > Thanks, > Ed > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSvaeAACgkQXvwMaW61dLc/PACgn3RqxNXThm7JH7RpPjxlTxD/ > 4NEAn0gaK0km/X9QA/jdStcLZqezVod4 > =+r5R > -----END PGP SIGNATURE----- > _______________________________________________ > 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 Jan 9 06:22:11 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 09 Jan 2015 13:22:11 +0700 Subject: [Slackbuilds-users] Update PhotoQt URL In-Reply-To: References: Message-ID: <54AF7393.5040209@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Old URL http://photoqt.org/pkgs/photoqt-1.0.tar.gz > > New URL http://photoqt.org/oldRel/photoqt-1.0.tar.gz Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSvc5MACgkQiHuDdNczM4EPUwCeNpNIU1tS6JKiCbS8eEqrZIDM 4GQAoII90oh64fJLOvxmkEBLXHohmNtO =pvpe -----END PGP SIGNATURE----- From info at microlinux.fr Fri Jan 9 06:35:40 2015 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 09 Jan 2015 07:35:40 +0100 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild Message-ID: <54AF76BC.6060802@microlinux.fr> Hi, I just noticed a strange line in python3.SlackBuild: PYVER=${VERSION::3} I only know this kind of notation: PYVER=${VERSION:-3} Is this an error or some special syntax I don't know? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Fri Jan 9 06:47:42 2015 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 09 Jan 2015 07:47:42 +0100 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> <54ABA0C9.4060109@microlinux.fr> Message-ID: <54AF798E.1030604@microlinux.fr> Le 06/01/2015 11:17, David Spencer a ?crit : > It looks like this: > http://bugs.python.org/issue17998 > which affects python-2.7.5. You could try SBo's python3? That would > probably be neater than building your own python-2.7.6+ to replace > Slackware's. I followed your suggestion and installed pycairo3, gnome-common and python3. I upgrade Catfish, and now I have: ImportError: No module named gi.repository I suggest removing Catfish from SBo, since this is clearly not working. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From chris.willing at iinet.net.au Fri Jan 9 07:09:55 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 09 Jan 2015 17:09:55 +1000 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild In-Reply-To: <54AF76BC.6060802@microlinux.fr> References: <54AF76BC.6060802@microlinux.fr> Message-ID: <54AF7EC3.3060505@iinet.net.au> On 01/09/2015 04:35 PM, Niki Kovacs wrote: > Hi, > > I just noticed a strange line in python3.SlackBuild: > > PYVER=${VERSION::3} > > I only know this kind of notation: > > PYVER=${VERSION:-3} > > Is this an error or some special syntax I don't know? From the Parameter Expansion section of the bash manpage: ${parameter:offset:length} Substring Expansion. Expands to up to length characters of the value of parameter starting at the character specified by off-set. Its not stated there but I presume a blank offset defaults it to 0, therefore for a VERSION of 3.4.2, PYVER would be set to 3.4 chris From ryan.q at linux.com Fri Jan 9 07:26:16 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 8 Jan 2015 23:26:16 -0800 Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 In-Reply-To: <54AF69E1.1040104@gmail.com> References: <54AF69E1.1040104@gmail.com> Message-ID: thanks for the build! what should i do on current? On Jan 8, 2015 9:40 PM, "King Beowulf" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Perhaps the README was not sufficiently clear. To enable USB pass > through on Slackware 14.1, you will download two (2) source packages: > > qemu-2.2.0.tar.bz2 > libusb-1.0.19.tar.xz > > Then you will invoke: > > LIBUSB=yes ./qemu.SlackBuild > > Then you will > > upgradepkg --install-new qemu-2.2.0-$ARCH-1_SBo.tgz > > That still won't get you USB Passthrough, since > > /dev/bus/usb/XXX > > is owned root:root. But that's another story. > > Please DO NOT attempt to > > upgradepkg libusb-1.0.19.tar.xz > > If you do not need have USB pass through, run > > ./qemu.SlackBuild > > and ignore libusb-1.0.19.tar.xz > > Thanks, > Ed > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSvaeAACgkQXvwMaW61dLc/PACgn3RqxNXThm7JH7RpPjxlTxD/ > 4NEAn0gaK0km/X9QA/jdStcLZqezVod4 > =+r5R > -----END PGP SIGNATURE----- > _______________________________________________ > 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 kingbeowulf at gmail.com Fri Jan 9 07:41:48 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 08 Jan 2015 23:41:48 -0800 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54AF798E.1030604@microlinux.fr> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> <54ABA0C9.4060109@microlinux.fr> <54AF798E.1030604@microlinux.fr> Message-ID: <54AF863C.1020509@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/08/2015 10:47 PM, Niki Kovacs wrote: > Le 06/01/2015 11:17, David Spencer a ?crit : >> It looks like this: http://bugs.python.org/issue17998 which >> affects python-2.7.5. You could try SBo's python3? That would >> probably be neater than building your own python-2.7.6+ to >> replace Slackware's. > > I followed your suggestion and installed pycairo3, gnome-common > and python3. I upgrade Catfish, and now I have: > > ImportError: No module named gi.repository > > I suggest removing Catfish from SBo, since this is clearly not > working. > > Cheers, > > Niki > Compiling catfish-1.2.1 from SBo manually, no sbopkg etc. Clean Slackware64 14.1 qemu VM (updated) pexpect-3.2 pyxdg-0.25 pygobject3-3.10.1 Compiles fine. No issues or errors. Appears to run OK in XFCE inside the Slackware64 guest. I would think, based on my testing tonight, that catfish removal from SBo is premature. - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSvhjoACgkQXvwMaW61dLeWrwCdF1/2rh0enX6q+E0+UglInNmd +TsAoLF/GYl2QMUvZ/ME69MtzwYuZshN =n++1 -----END PGP SIGNATURE----- From dave at dawoodfall.net Fri Jan 9 09:47:22 2015 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 9 Jan 2015 09:47:22 +0000 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54AF798E.1030604@microlinux.fr> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> <54ABA0C9.4060109@microlinux.fr> <54AF798E.1030604@microlinux.fr> Message-ID: <20150109094722.GM8796@Blackswan> >Le 06/01/2015 11:17, David Spencer a ?crit : >>It looks like this: >>http://bugs.python.org/issue17998 >>which affects python-2.7.5. You could try SBo's python3? That would >>probably be neater than building your own python-2.7.6+ to replace >>Slackware's. > >I followed your suggestion and installed pycairo3, gnome-common and >python3. I upgrade Catfish, and now I have: > >ImportError: No module named gi.repository > >I suggest removing Catfish from SBo, since this is clearly not working. > >Cheers, > >Niki Hi. I'm the maintainer. Nobody else has come forward with any problems with it. I can compile it just fine on a stock 14.1 system, with only the deps that are currently on sbo for 14.1. Dave From mjjzf at syntaktisk.dk Fri Jan 9 09:57:32 2015 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Fri, 9 Jan 2015 10:57:32 +0100 Subject: [Slackbuilds-users] Lxpanel build issue In-Reply-To: References: <20150108143746.2b534e5b@espero.syntaktisk.dk> <54AE8892.2000402@slackbuilds.org> <20150108144219.337c1b86@espero.syntaktisk.dk> <54AE8AD7.6020100@slackbuilds.org> <20150108150417.46d1ba71@espero.syntaktisk.dk> Message-ID: <20150109105732.7619b440@scopes.ufora.dk> On Thu, 8 Jan 2015 22:09:09 +0700 Willy Sudiarto Raharjo wrote: > > > It worked when I installed libfm-extra - excellent! > > That is not noted as a dependency., it should be mentioned. > > Thank you for your help. > > REQUIRES only list first level of dependency, so you need to check > whether a dependency requires another package or not I simply use > sbopkg + sqg to generate all the queues files which list all the dep > and build it using a correct order > > Willy Sudiarto Raharjo Ah, I only checked Lxpanel because I did the Sbopkg thing - and menu-cache built without errors. Thank you! All the best, Morten From info at microlinux.fr Fri Jan 9 10:33:09 2015 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 09 Jan 2015 11:33:09 +0100 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54AF863C.1020509@gmail.com> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> <54ABA0C9.4060109@microlinux.fr> <54AF798E.1030604@microlinux.fr> <54AF863C.1020509@gmail.com> Message-ID: <54AFAE65.1020700@microlinux.fr> Le 09/01/2015 08:41, King Beowulf a ?crit : > Compiling catfish-1.2.1 from SBo manually, no sbopkg etc. > > Clean Slackware64 14.1 qemu VM (updated) > pexpect-3.2 > pyxdg-0.25 > pygobject3-3.10.1 > > Compiles fine. No issues or errors. Appears to run OK in XFCE inside > the Slackware64 guest. > > I would think, based on my testing tonight, that catfish removal from > SBo is premature. Hmmm. I'm puzzled. My base Slackware system contains everything except KDE. And here's a list of extra stuff that's installed on my system: http://www.microlinux.fr/slackware/desktop-14.1-64bit/ChangeLog.txt Any idea what's going on here? BTW, in the meantime, I've reverted to the GTK2-based 0.32 version of Catfish, which works fine. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Fri Jan 9 12:43:29 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 09 Jan 2015 19:43:29 +0700 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54AFAE65.1020700@microlinux.fr> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> <54ABA0C9.4060109@microlinux.fr> <54AF798E.1030604@microlinux.fr> <54AF863C.1020509@gmail.com> <54AFAE65.1020700@microlinux.fr> Message-ID: <54AFCCF1.8080209@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > My base Slackware system contains everything except KDE. > > And here's a list of extra stuff that's installed on my system: > > http://www.microlinux.fr/slackware/desktop-14.1-64bit/ChangeLog.txt > > Any idea what's going on here? Most of us tested the packages in a clean environment with full installation a "pollutted" environment can make debugging harder since more packages means more combination to test - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSvzPEACgkQiHuDdNczM4F1RgCfeIMELUnJ049Qgfj14U2Mt74Y RfcAn2TSj+bW0AI/MPK1F23uO7Wj9Fg1 =Q2m9 -----END PGP SIGNATURE----- From rshepard at appl-ecosys.com Fri Jan 9 13:39:01 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 9 Jan 2015 05:39:01 -0800 (PST) Subject: [Slackbuilds-users] Postfix-2.11.3 test warning message In-Reply-To: <54AF3DF7.3030101@slackware.hr> References: <54AEF0F0.20101@slackware.hr> <54AF3DF7.3030101@slackware.hr> Message-ID: On Fri, 9 Jan 2015, Mario Preksavec wrote: > You are very welcome, although it would probably make more sense to clean > up paths in configuration files and avoid post-install file hackery... :-) Mario, That does make sense, but there were no path changes unless as a result of the postfix upgrade from 2.11.2 to 2.11.3. And, in that case, either postfix or the SBo build script should have accommodated it. When the next upgrade is installed we'll see if the issue re-appears. If it does, then further digging to find what's different in my system would be warranted. Rich From Jim.Diamond at acadiau.ca Fri Jan 9 17:34:03 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Fri, 9 Jan 2015 13:34:03 -0400 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild In-Reply-To: <54AF7EC3.3060505@iinet.net.au> References: <54AF76BC.6060802@microlinux.fr> <54AF7EC3.3060505@iinet.net.au> Message-ID: <20150109173403.GC26219@tux.acadiau.ca> On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote: > On 01/09/2015 04:35 PM, Niki Kovacs wrote: >>Hi, >>I just noticed a strange line in python3.SlackBuild: >>PYVER=${VERSION::3} >>I only know this kind of notation: >>PYVER=${VERSION:-3} >>Is this an error or some special syntax I don't know? > From the Parameter Expansion section of the bash manpage: > ${parameter:offset:length} > Substring Expansion. Expands to up to length characters of the > value of parameter starting at the character specified by off-set. > Its not stated there but I presume a blank offset defaults it to 0, > therefore for a VERSION of 3.4.2, PYVER would be set to 3.4 That is fragile code. If VERSION got as high as 3.10.x, Bad Things would happen. Cheers. Jim From kingbeowulf at gmail.com Fri Jan 9 18:43:50 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 09 Jan 2015 10:43:50 -0800 Subject: [Slackbuilds-users] Catfish not working In-Reply-To: <54AFCCF1.8080209@slackbuilds.org> References: <54A9032C.4010204@microlinux.fr> <54A99204.4040903@gmail.com> <54ABA0C9.4060109@microlinux.fr> <54AF798E.1030604@microlinux.fr> <54AF863C.1020509@gmail.com> <54AFAE65.1020700@microlinux.fr> <54AFCCF1.8080209@slackbuilds.org> Message-ID: <54B02166.7090809@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/09/2015 04:43 AM, Willy Sudiarto Raharjo wrote: >> My base Slackware system contains everything except KDE. > >> And here's a list of extra stuff that's installed on my system: > >> http://www.microlinux.fr/slackware/desktop-14.1-64bit/ChangeLog.txt > >> Any idea what's going on here? > > Most of us tested the packages in a clean environment with full > installation a "pollutted" environment can make debugging harder > since more packages means more combination to test > > Niki Just tested on my "polluted" box: Slackware64 14.1 multilib (full install, updated last week). Most add-ins from SBo (some customized or newer versions), some "rolled my own" (eq WINE), some from AlienBOB (with or without my bastardizations). Just too numerous, as well as pointless to list. I also have both wxPython-2.8.12.1-x86_64-1_SBo wxGTK3-3.0.1-x86_64-1_SBo installed (with wxPython-2.8 installed after wxGTK3 se README). So I would say, there either is a hidden dependency on KDE, or your installation is screwed up somewhere. I have many of your same gnome/* installed, but that is where I'd start. As per the discussion here in the past, IRC, and linuxquestions, ALWAYS test on a clean default install. Good Luck! Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSwIWQACgkQXvwMaW61dLfllgCdHN4NvHQ8mwwWkCdUa1YjcAhp ExUAnj0zibzMkfJa+ji3kAm4q0py+KZt =1lmf -----END PGP SIGNATURE----- From audrius at neutrino.lt Fri Jan 9 18:45:30 2015 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Fri, 9 Jan 2015 20:45:30 +0200 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild In-Reply-To: <20150109173403.GC26219@tux.acadiau.ca> References: <54AF76BC.6060802@microlinux.fr> <54AF7EC3.3060505@iinet.net.au> <20150109173403.GC26219@tux.acadiau.ca> Message-ID: <20150109184530.GA1324@varna> On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote: > On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote: > > > On 01/09/2015 04:35 PM, Niki Kovacs wrote: > >>Hi, > > >>I just noticed a strange line in python3.SlackBuild: > > >>PYVER=${VERSION::3} > > >>I only know this kind of notation: > > >>PYVER=${VERSION:-3} > > >>Is this an error or some special syntax I don't know? > > > From the Parameter Expansion section of the bash manpage: > > > ${parameter:offset:length} > > Substring Expansion. Expands to up to length characters of the > > value of parameter starting at the character specified by off-set. > > > Its not stated there but I presume a blank offset defaults it to 0, > > therefore for a VERSION of 3.4.2, PYVER would be set to 3.4 > > That is fragile code. If VERSION got as high as 3.10.x, Bad Things > would happen. Agreed, although very unlikely, according to one of Python developers[*]: My current expectation is that Python 4.0 will merely be "the release that comes after Python 3.9". <...> At the current rate of language feature releases (roughly every 18 months), that means we would likely see Python 4.0 some time in 2023, rather than seeing Python 3.10. But I'm still going to future-proof the code by changing the offending line to PYVER=$(cut -d. -f1,2 <<< "$VERSION") unless someone has a better suggestion. [*] http://opensource.com/life/14/9/why-python-4-wont-be-python-3 -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From kingbeowulf at gmail.com Fri Jan 9 23:48:57 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 09 Jan 2015 15:48:57 -0800 Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 In-Reply-To: References: <54AF69E1.1040104@gmail.com> Message-ID: <54B068E9.7090105@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 01/08/2015 11:26 PM, Ryan P.C. McQuen wrote: > thanks for the build! > > what should i do on current? > > > > Just run (as root), ./qemu.Slackbuild - -current already has the new(er) libusb so there is no need to build a static version. The build system should pickup the system libusb. Don't forget to read the README! Don't forget usbredir. Then read: http://qemu.weilnetz.de/qemu-doc.html#pcsys_005fusb Note that whenever you plug in a USB device, dev nodes are still root:root for example: $ lsusb ... Bus 001 Device 013: ID 08ec:0008 M-Systems Flash Disk Pioneers TravelDrive 2C ... ls -l /dev/bus/usb/001 total 0 crw-rw-r-- 1 root root 189, 0 Jan 4 18:33 001 crw-rw-r-- 1 root root 189, 5 Jan 4 18:33 006 crw-rw-r-- 1 root lp 189, 6 Jan 4 18:33 007 crw-rw-r-- 1 root root 189, 12 Jan 7 19:03 013 # chown :users /dev/bus/usb/001/013 NOW, you can $ qemu ... -usb -usbdevice host:08ec:0008 or use from within the qemu monitor (cli or gui depending on your preference): (qemu) usb_add host:08ec:0008 - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSwaOcACgkQXvwMaW61dLe2MQCfcBAf5dOdBhBASBahEm857Bih wcIAoJdARLyObNQn67YMXlpAkf8D9zng =UqRM -----END PGP SIGNATURE----- From ryan.q at linux.com Sat Jan 10 00:11:05 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 9 Jan 2015 16:11:05 -0800 Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 In-Reply-To: <54B068E9.7090105@gmail.com> References: <54AF69E1.1040104@gmail.com> <54B068E9.7090105@gmail.com> Message-ID: thank you! On Jan 9, 2015 3:48 PM, "King Beowulf" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 01/08/2015 11:26 PM, Ryan P.C. McQuen wrote: > > thanks for the build! > > > > what should i do on current? > > > > > > > > > Just run (as root), > > ./qemu.Slackbuild > > - -current already has the new(er) libusb so there is no need to build a > static version. The build system should pickup the system libusb. > Don't forget to read the README! Don't forget usbredir. > > Then read: > http://qemu.weilnetz.de/qemu-doc.html#pcsys_005fusb > > Note that whenever you plug in a USB device, dev nodes are still > root:root for example: > > $ lsusb > ... > Bus 001 Device 013: ID 08ec:0008 M-Systems Flash Disk Pioneers > TravelDrive 2C > ... > > ls -l /dev/bus/usb/001 > total 0 > crw-rw-r-- 1 root root 189, 0 Jan 4 18:33 001 > crw-rw-r-- 1 root root 189, 5 Jan 4 18:33 006 > crw-rw-r-- 1 root lp 189, 6 Jan 4 18:33 007 > crw-rw-r-- 1 root root 189, 12 Jan 7 19:03 013 > > # chown :users /dev/bus/usb/001/013 > > NOW, you can > > $ qemu ... -usb -usbdevice host:08ec:0008 > > or use from within the qemu monitor (cli or gui depending on your > preference): > > (qemu) usb_add host:08ec:0008 > > > > > > - -Ed > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlSwaOcACgkQXvwMaW61dLe2MQCfcBAf5dOdBhBASBahEm857Bih > wcIAoJdARLyObNQn67YMXlpAkf8D9zng > =UqRM > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Jan 10 00:59:01 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 10 Jan 2015 07:59:01 +0700 Subject: [Slackbuilds-users] Updates - 20150110.1 Message-ID: <54B07955.7020000@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Jan 10 00:49:56 UTC 2015 academic/units: Updated for version 2.11. audio/acousticbrainz-client: Added (Acoustic Music Scanner). audio/acousticbrainz-gui: Added (Acoustic Music Scanner). audio/acousticbrainz-music-extractor: Added (Music Extractor). audio/apulse: Allow library path option. audio/jack_capture: Updated for version 0.9.71 + new maintainer. business/ledger: Update HOMEPAGE. business/ledger: Updated for version 3.1 + new maintainer. desktop/catfish: Updated for version 1.2.2. desktop/insync-thunar: Added (Insync thunar integration). desktop/ssr: Updated for version 0.3.2. development/google-webdesigner: Fix permission on .desktop file. development/mono: Updated for version 3.10.0. development/p4v: Updated for version 2014.1.978848. games/minetest: Updated for version 0.4.11. games/minetest_game: Updated for version 0.4.11. games/openmw: Updated for version 0.34.0. games/unknown-horizons: Updated for version 2014.1. gis/Shapely: Updated for version 1.5.2. graphics/blender: Updated for version 2.73. graphics/graphviz: Fix for multilib. graphics/jpegoptim: Remove needless configure option. graphics/nomacs: Updated for version 2.2.0. graphics/photoqt: Update DOWNLOAD url. graphics/phototonic: Updated for version 1.5. graphics/qcad: Added (Open Source CAD). graphics/xdot: Updated for version 0.6 + new maintainer. ham/7plus: Update DOWNLOAD url. ham/svxlink-sounds-en_US-heather-16k: Updated for version 14.08. ham/svxlink: Updated for version 14.08. libraries/MyGUI: Fix VERSION. libraries/libwebp: Added optional python 3 support. libraries/live555: Updated for version 2015.01.04. libraries/ogre: Fix commit ID and MD5SUM. misc/par2cmdline-tbb: Updated for version 0.4_20141125. misc/protobuf: Update DEP. multimedia/cuetools: Updated for version 1.4.0. multimedia/get_iplayer: Updated for version 2.91. multimedia/picard-plugins: Added (MusicBrainz Picard Plugins). multimedia/picard: Updated for version 1.3.2. multimedia/xbmc: Fix DOWNLOAD url. network/copy: Updated for version 1.48.0451. network/courier-authlib: Updated for version 0.66.1. network/courier-imap: Updated for version 4.16.0. network/courier-unicode: Added (Courier Unicode library). network/dnscrypt-proxy: Updated for version 1.4.3. network/dnscrypt-wrapper: Updated for version 0.1.15. network/dropbox: Updated for version 3.0.5. network/etherpoke: Added (scriptable network session monitor). network/insync: Added (Google Drive Client). network/node: Updated for version 0.10.35. network/openntpd: Added (Network Time Protocol client/server). network/pastebincl: Added (submit pastes on Pastebin). network/skylable-sx: Updated for version 1.0. office/xmind: Updated for version 3.5.1 + new maintainer. perl/perl-AnyEvent-HTTP: Added (non-blocking HTTP/HTTPS client). perl/perl-common-sense: Fix DOWNLOAD url. python/python-gflags: Added (Python argument parsing library). python/python3: Report correct extension suffix. python/thunarx-python: Added (Thunar Python Bindings). system/brasero: Updated for version 3.12.0. system/firejail: Added (security sandbox). system/mlterm: Updated for version 3.4.2. system/postgresql: Updated for version 9.4.0. system/profile-sync-daemon: Updated for version 5.60.1. system/redis: Updated for version 2.10.3. system/simpleburn: Added (CD / DVD burning and extraction tool). system/slpkg: Updated for version 2.2.0. system/trmaid: Updated for version 0.3.3. system/unison: Updated for version 2.40.128. system/vagrant: Updated for version 1.7.2. system/virt-manager: Update HOMEPAGE. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSweVUACgkQiHuDdNczM4GnrQCgj3sWIYHiA+z0LnzCz6cPWsIU uk4AnRm3rqL/WEpLpGHLv5bxd6YqsUNB =bErm -----END PGP SIGNATURE----- From chris.willing at iinet.net.au Sat Jan 10 04:18:20 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 10 Jan 2015 14:18:20 +1000 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild In-Reply-To: <20150109184530.GA1324@varna> References: <54AF76BC.6060802@microlinux.fr> <54AF7EC3.3060505@iinet.net.au> <20150109173403.GC26219@tux.acadiau.ca> <20150109184530.GA1324@varna> Message-ID: <54B0A80C.4020305@iinet.net.au> On 01/10/2015 04:45 AM, Audrius Ka?ukauskas wrote: > On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote: >> On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote: >> >>> On 01/09/2015 04:35 PM, Niki Kovacs wrote: >>>> Hi, >> >>>> I just noticed a strange line in python3.SlackBuild: >> >>>> PYVER=${VERSION::3} >> >>>> I only know this kind of notation: >> >>>> PYVER=${VERSION:-3} >> >>>> Is this an error or some special syntax I don't know? >> >>> From the Parameter Expansion section of the bash manpage: >> >>> ${parameter:offset:length} >>> Substring Expansion. Expands to up to length characters of the >>> value of parameter starting at the character specified by off-set. >> >>> Its not stated there but I presume a blank offset defaults it to 0, >>> therefore for a VERSION of 3.4.2, PYVER would be set to 3.4 >> >> That is fragile code. If VERSION got as high as 3.10.x, Bad Things >> would happen. > > Agreed, although very unlikely, according to one of Python > developers[*]: > > My current expectation is that Python 4.0 will merely be "the release > that comes after Python 3.9". <...> > > At the current rate of language feature releases (roughly every 18 > months), that means we would likely see Python 4.0 some time in 2023, > rather than seeing Python 3.10. > > But I'm still going to future-proof the code by changing the offending > line to > > PYVER=$(cut -d. -f1,2 <<< "$VERSION") > > unless someone has a better suggestion. That would work but, just for fun, also: PYVER=${VERSION%.*} chris From ts at websafe.pl Sat Jan 10 04:21:54 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 10 Jan 2015 05:21:54 +0100 Subject: [Slackbuilds-users] Missing requirement: spice-gtk requires usbredir Message-ID: <54B0A8E2.50207@websafe.pl> spice-gtk http://slackbuilds.org/repository/14.1/network/spice-gtk/ requires usbredir http://slackbuilds.org/repository/14.1/system/usbredir/ otherwise: configure: error: usbredir support explicitly requested, but some required packages are not available when building spice-gtk. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sat Jan 10 04:31:10 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 10 Jan 2015 05:31:10 +0100 Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 In-Reply-To: <54B068E9.7090105@gmail.com> References: <54AF69E1.1040104@gmail.com> <54B068E9.7090105@gmail.com> Message-ID: <54B0AB0E.902@websafe.pl> On 01/10/2015 12:48 AM, King Beowulf wrote: > -current already has the new(er) libusb so there is no need to build a > static version. The build system should pickup the system libusb. > Don't forget to read the README! Don't forget usbredir. Please check my http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-January/013448.html spice-gtk (dependency of virt-manager) already requires usbredir so maybe usbredir should become a default for qemu? -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sat Jan 10 04:51:51 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 10 Jan 2015 05:51:51 +0100 Subject: [Slackbuilds-users] gnome-python2-gconf.SlackBuild breaks Message-ID: <54B0AFE7.8090708@websafe.pl> First I thought it's a missing dependency: gnome-python2-gconf http://slackbuilds.org/repository/14.1/libraries/gnome-python2-gconf/ probably requires pyorbit http://slackbuilds.org/repository/14.1/python/pyorbit/ otherwise build fails with: > Note: PyORBit 2.0.1 or later is required by bonobo > and gnomeui bindings. > Download it from: http://ftp.gnome.org/pub/GNOME/sources/pyorbit/2.0/ but then I've noticed, gnome-python2-gconf.SlackBuild fails on this: > find $PKG | xargs file | egrep "ELF.*shared object" | cut -f 1 -d : \ > | xargs strip --strip-unneeded 2> /dev/null After commenting these two lines the package is created without problems. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sat Jan 10 05:05:58 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 10 Jan 2015 06:05:58 +0100 Subject: [Slackbuilds-users] Missing requirement: spice-gtk requires usbredir In-Reply-To: <54B0A8E2.50207@websafe.pl> References: <54B0A8E2.50207@websafe.pl> Message-ID: <54B0B336.3040804@websafe.pl> On 01/10/2015 05:21 AM, Thomas Szteliga wrote:> spice-gtk http://slackbuilds.org/repository/14.1/network/spice-gtk/ > requires usbredir http://slackbuilds.org/repository/14.1/system/usbredir/ > otherwise: > configure: error: usbredir support explicitly requested, but some > required packages are not available > when building spice-gtk. Now I see there is: ~~~~ # enable support for usbredir and libcacard, if available if pkg-config --exists libusbredirhost; then usbredir="en"; else usbredir="dis"; fi if pkg-config --exists libcacard; then cacard="en"; else cacard="dis"; fi if [ "$GTK" = "2" ]; then gtkver="2"; else gtkver="3"; fi ~~~~ in spice-gtk.SlackBuild (I was building with slpkg). The slackbuild enabled in my case usbredir automatically, but the build failed, so I assumed usbredir is missing in REQUIRED... -- Thomas Szteliga From willysr at slackbuilds.org Sat Jan 10 06:07:15 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 10 Jan 2015 13:07:15 +0700 Subject: [Slackbuilds-users] Missing requirement: spice-gtk requires usbredir In-Reply-To: <54B0B336.3040804@websafe.pl> References: <54B0A8E2.50207@websafe.pl> <54B0B336.3040804@websafe.pl> Message-ID: <54B0C193.2000306@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > http://slackbuilds.org/repository/14.1/network/spice-gtk/ >> requires usbredir >> http://slackbuilds.org/repository/14.1/system/usbredir/ >> otherwise: configure: error: usbredir support explicitly >> requested, but some required packages are not available when >> building spice-gtk. > > > Now I see there is: > > ~~~~ # enable support for usbredir and libcacard, if available if > pkg-config --exists libusbredirhost; then usbredir="en"; else > usbredir="dis"; fi if pkg-config --exists libcacard; then > cacard="en"; else cacard="dis"; fi if [ "$GTK" = "2" ]; then > gtkver="2"; else gtkver="3"; fi ~~~~ > > in spice-gtk.SlackBuild (I was building with slpkg). The slackbuild > enabled in my case usbredir automatically, but the build failed, so > I assumed usbredir is missing in REQUIRED... it built fine here using sbopkg on a clean VM vala: MD5SUM check for vala-0.26.0.tar.xz ... OK Building package vala-0.26.0-x86_64-1_SBo.tgz ... OK Installing package vala-0.26.0-x86_64-1_SBo.tgz ... OK spice-protocol: MD5SUM check for spice-protocol-0.12.7.tar.bz2 ... OK Building package spice-protocol-0.12.7-noarch-1_SBo.tgz ... OK Installing package spice-protocol-0.12.7-noarch-1_SBo.tgz ... OK pyparsing: MD5SUM check for pyparsing-2.0.1.tar.gz ... OK Building package pyparsing-2.0.1-x86_64-1_SBo.tgz ... OK Installing package pyparsing-2.0.1-x86_64-1_SBo.tgz ... OK celt051: MD5SUM check for celt-0.5.1.3.tar.gz ... OK Building package celt051-0.5.1.3-x86_64-1_SBo.tgz ... OK Installing package celt051-0.5.1.3-x86_64-1_SBo.tgz ... OK spice: MD5SUM check for spice-0.12.5.tar.bz2 ... OK Building package spice-0.12.5-x86_64-1_SBo.tgz ... OK Installing package spice-0.12.5-x86_64-1_SBo.tgz ... OK spice-gtk: MD5SUM check for spice-gtk-0.25.tar.bz2 ... OK Building package spice-gtk-0.25-x86_64-1_SBo.tgz ... OK Installing package spice-gtk-0.25-x86_64-1_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSwwZMACgkQiHuDdNczM4GySgCgqCYmNOUeOEhUdJEMDjc54rmv evwAoJn4tjzosa/tOOUvXH1PondPm/8r =CCVp -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Jan 10 06:09:52 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 10 Jan 2015 13:09:52 +0700 Subject: [Slackbuilds-users] gnome-python2-gconf.SlackBuild breaks In-Reply-To: <54B0AFE7.8090708@websafe.pl> References: <54B0AFE7.8090708@websafe.pl> Message-ID: <54B0C230.1030306@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > First I thought it's a missing dependency: > > gnome-python2-gconf > http://slackbuilds.org/repository/14.1/libraries/gnome-python2-gconf/ > > probably requires > > pyorbit http://slackbuilds.org/repository/14.1/python/pyorbit/ > > otherwise build fails with: > >> Note: PyORBit 2.0.1 or later is required by bonobo and gnomeui >> bindings. Download it from: >> http://ftp.gnome.org/pub/GNOME/sources/pyorbit/2.0/ > > > but then I've noticed, gnome-python2-gconf.SlackBuild fails on > this: > >> find $PKG | xargs file | egrep "ELF.*shared object" | cut -f 1 -d >> : \ | xargs strip --strip-unneeded 2> /dev/null > > > After commenting these two lines the package is created without > problems. this works without any changes from what we have in our repo, but i notice this lines during build process The following modules will be built: gconf The following modules will NOT be built: gnome gnome.ui gnomecanvas gnomevfs gnomevfs.bonobo gnome-vfs python module support bonobo bonobo.activation bonobo.ui Note: PyORBit 2.0.1 or later is required by bonobo and gnomeui bindings. so PyORBit is basically an optional dependency and not mandatory here's the build result gnome-python2-gconf: MD5SUM check for gnome-python-2.28.1.tar.bz2 ... OK Building package gnome-python2-gconf-2.28.1-x86_64-1_SBo.tgz ... OK Installing package gnome-python2-gconf-2.28.1-x86_64-1_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlSwwjAACgkQiHuDdNczM4EA/wCaA8ZTTPb64/+0Ei0SGKIhih/M dHkAn2Znq3fPTck9rTBT0H9nT+MQrSOk =6G7n -----END PGP SIGNATURE----- From leva at ecentrum.hu Sat Jan 10 08:10:18 2015 From: leva at ecentrum.hu (=?iso-8859-1?Q?L=C9VAI_D=E1niel?=) Date: Sat, 10 Jan 2015 09:10:18 +0100 Subject: [Slackbuilds-users] rxvt-unicode up for grabs In-Reply-To: References: <20150102144641.GG1533@serenity.local> Message-ID: <20150110081018.GH24693@serenity.local> On p, jan 02, 2015 at 15:31:24 +0000, Glenn Becker wrote: > > >I'm not using it anymore. Anyone willing to take over? > > I'll adopt if no one else has beaten me ... :) > It's been two public update since. Is there anything else we supposed to do to transfer maintainership? Maybe a new update by the new maintainer? There is a new version -- just saying.. :-) Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From kingbeowulf at gmail.com Sat Jan 10 08:31:20 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 10 Jan 2015 00:31:20 -0800 Subject: [Slackbuilds-users] ANNOUNCEMENT: qemu-2.2.0 In-Reply-To: <54B0AB0E.902@websafe.pl> References: <54AF69E1.1040104@gmail.com> <54B068E9.7090105@gmail.com> <54B0AB0E.902@websafe.pl> Message-ID: On Friday, January 9, 2015, Thomas Szteliga wrote: > On 01/10/2015 12:48 AM, King Beowulf wrote: > > -current already has the new(er) libusb so there is no need to build a > > static version. The build system should pickup the system libusb. > > Don't forget to read the README! Don't forget usbredir. > > Please check my > > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-January/013448.html > > spice-gtk (dependency of virt-manager) already requires usbredir > so maybe usbredir should become a default for qemu? > > -- > Thomas Szteliga > > Once -current goes stable, and we can dispense with the static lib stuff, so we can revisit usbredir. -- 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 Jim.Diamond at acadiau.ca Sat Jan 10 15:14:09 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 10 Jan 2015 11:14:09 -0400 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild In-Reply-To: <20150109184530.GA1324@varna> References: <54AF76BC.6060802@microlinux.fr> <54AF7EC3.3060505@iinet.net.au> <20150109173403.GC26219@tux.acadiau.ca> <20150109184530.GA1324@varna> Message-ID: <20150110151408.GD23467@jdiamond-nb> On Fri, Jan 9, 2015 at 20:45 (+0200), Audrius Ka??ukauskas wrote: > On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote: >> On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote: >>> Its not stated there but I presume a blank offset defaults it to 0, >>> therefore for a VERSION of 3.4.2, PYVER would be set to 3.4 >> That is fragile code. If VERSION got as high as 3.10.x, Bad Things >> would happen. > Agreed, although very unlikely, according to one of Python > developers[*]: Also agreed. Another problem with having fragile code is that it might propagate itself into other Slackbuilds, which could (who knows?) end up with that actually being a bug. Cheers. Jim From chris.willing at iinet.net.au Sun Jan 11 01:37:56 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 11 Jan 2015 11:37:56 +1000 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild In-Reply-To: <20150110151408.GD23467@jdiamond-nb> References: <54AF76BC.6060802@microlinux.fr> <54AF7EC3.3060505@iinet.net.au> <20150109173403.GC26219@tux.acadiau.ca> <20150109184530.GA1324@varna> <20150110151408.GD23467@jdiamond-nb> Message-ID: <54B1D3F4.2060005@iinet.net.au> On 01/11/2015 01:14 AM, Jim Diamond wrote: > On Fri, Jan 9, 2015 at 20:45 (+0200), Audrius Ka??ukauskas wrote: > >> On Fri, 2015-01-09 at 13:34:03 -0400, Jim Diamond wrote: >>> On Fri, Jan 9, 2015 at 17:09 (+1000), Christoph Willing wrote: > >>>> Its not stated there but I presume a blank offset defaults it to 0, >>>> therefore for a VERSION of 3.4.2, PYVER would be set to 3.4 > >>> That is fragile code. If VERSION got as high as 3.10.x, Bad Things >>> would happen. > >> Agreed, although very unlikely, according to one of Python >> developers[*]: > > Also agreed. > > Another problem with having fragile code is that it might propagate > itself into other Slackbuilds, which could (who knows?) end up with > that actually being a bug. If we're looking for something more robust, yet generic, then my previously proposed solution: PYVER=${VERSION%.*} is not so great if a version string has extra fields i.e. VERSION=3.4.2.5 would become 3.4.2 (rather than the desired 3.4). To make up for that shortcoming, I offer: PYVER=$(sed 's/\.[^\.]*//2g' <<< "$VERSION") Maybe not as easy to read as Audrius' solution using cut though ... chris From vmj at linuxbox.fi Sun Jan 11 20:36:41 2015 From: vmj at linuxbox.fi (Mikko Varri) Date: Sun, 11 Jan 2015 22:36:41 +0200 Subject: [Slackbuilds-users] libncurses / libtinfo In-Reply-To: References: <20150105213201.GB21171@linuxbox.fi> <20150105155953.30abae4a@home.rlworkman.net> Message-ID: <20150111203641.GC21171@linuxbox.fi> On Mon, Jan 05, 2015 at 07:33:53PM -0500, B Watson wrote: > On 1/5/15, Robby Workman wrote: > > > However, the second best solution IMHO, and the one that will be needed > > for 14.1, is to create a separate "package" at SlackBuilds.org that > > is basically just a symlink and a README into the docs directory that > > explains why it's there. Feel free to submit a "libtinfo" package. :-) > > This seems like it might be a bad idea. I can imagine some configure > script detecting that libtinfo.so is found, and getting confused... > Good point. I already built the ghc package with REQUIRES="libtinfo", but I haven't submitted either. Also, I'm afraid some of the sbo build tools might reject the empty DOWNLOAD in libtinfo.info. My own script did :) > Maybe for the binary build of ghc, a better solution would be to stick > the libtinfo.so symlink in a private lib dir > Maybe it's worth bootstrapping it. Both of your suggestions seem better, so I'll try them. You're right about the reason for using bindist. -vmj From yalhcru at gmail.com Sun Jan 11 22:23:31 2015 From: yalhcru at gmail.com (B Watson) Date: Sun, 11 Jan 2015 17:23:31 -0500 Subject: [Slackbuilds-users] libncurses / libtinfo In-Reply-To: <20150111203641.GC21171@linuxbox.fi> References: <20150105213201.GB21171@linuxbox.fi> <20150105155953.30abae4a@home.rlworkman.net> <20150111203641.GC21171@linuxbox.fi> Message-ID: On 1/11/15, Mikko Varri wrote: >> Maybe it's worth bootstrapping it. > > Both of your suggestions seem better, so I'll try them. You're right > about the reason for using bindist. The other thing you might do: make your own bindist. Bootstrap it on your own system (not as part of the submitted SlackBuild), then host your Slackware-built binary package somewhere, and the SBo build can just download & make a pkg out of that. It would simplify the SlackBuild, and save your users some time... but it would also be a single point of failure: the script would depend on private state that exists only on your system. From thomas at beingboiled.info Mon Jan 12 03:56:49 2015 From: thomas at beingboiled.info (Thomas Morper) Date: Mon, 12 Jan 2015 04:56:49 +0100 (CET) Subject: [Slackbuilds-users] bitcoin incompatible w/ openssl-1.0.1k Message-ID: Users of the "bitcoin" SlackBuild, listen up: The recent upgrade to openssl-1.0.1k is incompatible with the Bitcoin system and could lead to consensus forks. You must either withhold the openssl upgrade or rebuild the bitcoin package including a hotfix. For a more detailed explanation and links to patches see http://thread.gmane.org/gmane.comp.bitcoin.devel/6702 and http://thread.gmane.org/gmane.comp.bitcoin.devel/6702/focus=6704 -- From marco.maggi-ipsu at poste.it Mon Jan 12 15:11:08 2015 From: marco.maggi-ipsu at poste.it (Marco Maggi) Date: Mon, 12 Jan 2015 16:11:08 +0100 Subject: [Slackbuilds-users] icoutils can be updated to latest release? Message-ID: <87wq4snier.fsf@governatore.luna> Ciao, the page of the "icoutils" package still references release 0.26.0; the latest release[2] is 0.31.0 available since May 2013. I was able to build the latest revision on my Slackware 14.1 64-bit with the following changes to the build script: 28c28 < VERSION=0.26.0 --- > VERSION=${VERSION:-0.26.0} 65c65 < tar xvf $CWD/$PRGNAM-$VERSION.tar.gz --- > tar xvf $CWD/$PRGNAM-$VERSION.tar.bz2 92c92 < ( cd $PKG/usr/man --- > ( cd $PKG/usr/share/man HTH P.S. Is it fine for me to post this kind of message on this mailing list? [1] [2] -- "Now feel the funk blast!" Rage Against the Machine - "Calm like a bomb" From marco.maggi-ipsu at poste.it Mon Jan 12 15:32:36 2015 From: marco.maggi-ipsu at poste.it (Marco Maggi) Date: Mon, 12 Jan 2015 16:32:36 +0100 Subject: [Slackbuilds-users] changing referenced web page of q4wine? Message-ID: <87r3v0nhez.fsf@governatore.luna> Ciao, the web page[1] of the package "q4wine" references an upstream home page[2] that is down for serious troubles. Is it the case to change it to the source code distribution page[3]? TIA P.S. I do not know what is other people's experience, but these days I cannot do a thing with SourceForge if I am not logged in. When I am logged in: everything works. Is it the case to add a note about this on the SlackBuilds package pages when they involve a link to this site? [1] [2] [3] -- Marco Maggi From rshepard at appl-ecosys.com Mon Jan 12 17:09:37 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 12 Jan 2015 09:09:37 -0800 (PST) Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available Message-ID: wxPython-3.0.2.0 (classic) was released at the end of last November. It builds here with a version change from the script I used to build -3.0.1.1. The version on SBo is in the 2.8.x.x series. Rich From matteo.bernardini at gmail.com Mon Jan 12 17:46:01 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 12 Jan 2015 18:46:01 +0100 Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available In-Reply-To: References: Message-ID: is it compatible with all the stuff on SBo that needs wxPython? Matteo From rshepard at appl-ecosys.com Mon Jan 12 18:28:52 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 12 Jan 2015 10:28:52 -0800 (PST) Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available In-Reply-To: References: Message-ID: On Mon, 12 Jan 2015, Matteo Bernardini wrote: > is it compatible with all the stuff on SBo that needs wxPython? Matteo, I don't know. I upgrade to the latest wxPython when I start a new project and it works for the applications I write. Heinz is the SBo package maintainer, and I let him know the new version's out. Rich From matteo.bernardini at gmail.com Mon Jan 12 18:57:55 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 12 Jan 2015 19:57:55 +0100 Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available In-Reply-To: References: Message-ID: 2015-01-12 19:28 GMT+01:00 Rich Shepard : > On Mon, 12 Jan 2015, Matteo Bernardini wrote: > >> is it compatible with all the stuff on SBo that needs wxPython? > > > Matteo, > > I don't know. I upgrade to the latest wxPython when I start a new project > and it works for the applications I write. Heinz is the SBo package > maintainer, and I let him know the new version's out. sorry Rich, I didn't meant to be rude, but IMHO (don't mean to step on Heinz toes) switching to wxPython-3.x for all the stuff we have in out repository isn't gonna be that easy. ATM, wxPython is needed by this stuff on our repository academic/bibus academic/extrema academic/gspiceui academic/treeview academic/wxMaxima academic/wxmacmolplt audio/audacity audio/miniAudicle audio/sooperlooper desktop/maitreya desktop/obapps development/Editra development/PythonToolkit development/codeblocks development/kicad development/mysql-workbench development/rapidsvn development/wxHexEditor development/xmlcopyeditor games/Pyfa games/Scorched3D games/doomsday games/golly games/megaglest games/openmsx-catapult games/openyahtzee games/pcsx2 games/playonlinux gis/grass graphics/discwrapper graphics/hugin graphics/phatch graphics/whyteboard graphics/xpe ham/ebook2cwgui ham/tqsl libraries/mathgl libraries/wxsvg multimedia/DivFix++ multimedia/mediainfo-gui multimedia/mkvtoolnix multimedia/tovid multimedia/wxcam network/Free-Cinema network/aMule network/emesene network/filezilla network/tribler office/TaskCoach office/etm office/myrulib office/nts office/pyspread office/trelby office/wammu python/winpdb system/fs-uae-arcade system/fs-uae-launcher system/pgadmin3 system/truecrypt system/xchm most of it isn't compatible as is with the new version: for example, audacity, that I maintain, needs an huge patch (and I still have to test it) https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749659#153 debian has a dedicated (and useful) page for the migration in their wiki that should detail more the PITA https://wiki.debian.org/Teams/WxWidgets/Transition2.8to3.0 Matteo From ryan.q at linux.com Mon Jan 12 19:02:54 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 12 Jan 2015 11:02:54 -0800 Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available In-Reply-To: References: Message-ID: maybe the packages should be separated? On Jan 12, 2015 10:58 AM, "Matteo Bernardini" wrote: > 2015-01-12 19:28 GMT+01:00 Rich Shepard : > > On Mon, 12 Jan 2015, Matteo Bernardini wrote: > > > >> is it compatible with all the stuff on SBo that needs wxPython? > > > > > > Matteo, > > > > I don't know. I upgrade to the latest wxPython when I start a new > project > > and it works for the applications I write. Heinz is the SBo package > > maintainer, and I let him know the new version's out. > > sorry Rich, I didn't meant to be rude, but IMHO (don't mean to step on > Heinz toes) switching to wxPython-3.x for all the stuff we have in out > repository isn't gonna be that easy. > ATM, wxPython is needed by this stuff on our repository > > academic/bibus > academic/extrema > academic/gspiceui > academic/treeview > academic/wxMaxima > academic/wxmacmolplt > audio/audacity > audio/miniAudicle > audio/sooperlooper > desktop/maitreya > desktop/obapps > development/Editra > development/PythonToolkit > development/codeblocks > development/kicad > development/mysql-workbench > development/rapidsvn > development/wxHexEditor > development/xmlcopyeditor > games/Pyfa > games/Scorched3D > games/doomsday > games/golly > games/megaglest > games/openmsx-catapult > games/openyahtzee > games/pcsx2 > games/playonlinux > gis/grass > graphics/discwrapper > graphics/hugin > graphics/phatch > graphics/whyteboard > graphics/xpe > ham/ebook2cwgui > ham/tqsl > libraries/mathgl > libraries/wxsvg > multimedia/DivFix++ > multimedia/mediainfo-gui > multimedia/mkvtoolnix > multimedia/tovid > multimedia/wxcam > network/Free-Cinema > network/aMule > network/emesene > network/filezilla > network/tribler > office/TaskCoach > office/etm > office/myrulib > office/nts > office/pyspread > office/trelby > office/wammu > python/winpdb > system/fs-uae-arcade > system/fs-uae-launcher > system/pgadmin3 > system/truecrypt > system/xchm > > most of it isn't compatible as is with the new version: for example, > audacity, that I maintain, needs an huge patch (and I still have to > test it) > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749659#153 > > debian has a dedicated (and useful) page for the migration in their > wiki that should detail more the PITA > > https://wiki.debian.org/Teams/WxWidgets/Transition2.8to3.0 > > 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 pprkut at slackbuilds.org Mon Jan 12 19:29:41 2015 From: pprkut at slackbuilds.org (Heinz Wiesinger) Date: Mon, 12 Jan 2015 20:29:41 +0100 Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available In-Reply-To: References: Message-ID: <32327982.HuEjnvDquD@titania> On Monday 12 January 2015 11:02:54 Ryan P.C. McQuen wrote: > On Jan 12, 2015 10:58 AM, "Matteo Bernardini" > > sorry Rich, I didn't meant to be rude, but IMHO (don't mean to step on > > Heinz toes) switching to wxPython-3.x for all the stuff we have in out > > repository isn't gonna be that easy. > > maybe the packages should be separated? That suggestion has come up in the past, and conceptually there's nothing wrong with it. Yet, it doesn't really solve the problem as the fact remains that some builds need the wx 2.8 api and some need the 3.0 api. Historically, the reason I started maintaining wxPython was for exactly this fact. We had wxGTK 2.6 in the repo, and a ton of builds depended on it. 2.8 came out, but lots of things were just not ready. So instead of waiting for everything to get ready for wxGTK 2.8, I submitted wxPython 2.8, made it conflict with wxGTK and gave apps the choice to either use the old wxGTK or the new wxPython, until everything was ready and one became pretty much drop-in for the other. Today, the situation is slightly more complicated. We have wxGTK and wxGTK3 in the repo, and quite an amount of builds that actually depend on the python bindings shipped in wxPython. To top it off, wxGTK3 not only switched the wx api, but also upgraded from GTK+2 to GTK+3. So there's a glorious amount of variables to consider for this migration, and that doesn't make it any easier. Even if I would update wxPython to version 3 now, I'd probably still use GTK+2 for a while, which in turn wouldn't make it drop-in with wxGTK3 and we'd end up with 3 wxGTK implementations that behave slightly differently and more or less conflict with each other. To be honest, I don't really know what's best to do at this point. In lack of a reasonable migration path I decided to play the waiting game and see what happens. Now one year has passed since wxPython 3.0 and nothing really changed. As far as I'm concerned, I don't mind waiting a while longer. If someone wants to jump ahead of the curve and submit a wxPython3 script, I don't mind, but it doesn't really strike me as a solution worth pursuing to add another variable to an already complicated equation. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: This is a digitally signed message part. URL: From rshepard at appl-ecosys.com Mon Jan 12 20:43:31 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 12 Jan 2015 12:43:31 -0800 (PST) Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available In-Reply-To: References: Message-ID: On Mon, 12 Jan 2015, Matteo Bernardini wrote: > sorry Rich, I didn't meant to be rude, but IMHO (don't mean to step on > Heinz toes) switching to wxPython-3.x for all the stuff we have in out > repository isn't gonna be that easy. ATM, wxPython is needed by this stuff > on our repository Matteo, The 'classic' wxPython works with Python-2.x. I haven't switched to Python-3.x because I've not had sufficient reason to do so. If you want wxPython for Python-3.x use the 'Phoenix' versions. It's not yet as complete as the 'classic' branch, but for those writing Python-3.x code it's the way to go. Rich From rshepard at appl-ecosys.com Mon Jan 12 20:49:28 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 12 Jan 2015 12:49:28 -0800 (PST) Subject: [Slackbuilds-users] wxPython-3.0.2.0 Available In-Reply-To: <32327982.HuEjnvDquD@titania> References: <32327982.HuEjnvDquD@titania> Message-ID: On Mon, 12 Jan 2015, Heinz Wiesinger wrote: > Now one year has passed since wxPython 3.0 and nothing really changed. As > far as I'm concerned, I don't mind waiting a while longer. FWIW, I've used wxPython-3.0.1.1 with Python-2.7.5 just fine. I expect that wxPython-3.0.2.0 will continue working just fine with Python-2.x. Robin and crew separated 'classic' wxPython into the new 'phoenix' branch. I think that 'phoenix' works with both Python-2 and Python-3, but since it does not yet have all the 'classic' widgets implemented I've not tried it. And I agree with you, Heinz, that wxGTK and wxPython have become very confusing. Rich From mario at slackware.hr Tue Jan 13 06:53:09 2015 From: mario at slackware.hr (Mario Preksavec) Date: Tue, 13 Jan 2015 07:53:09 +0100 Subject: [Slackbuilds-users] Postfix-2.11.3 test warning message In-Reply-To: References: <54AEF0F0.20101@slackware.hr> <54AF3DF7.3030101@slackware.hr> Message-ID: <54B4C0D5.9050400@slackware.hr> On 01/09/2015 02:39 PM, Rich Shepard wrote: > On Fri, 9 Jan 2015, Mario Preksavec wrote: > >> You are very welcome, although it would probably make more sense to >> clean >> up paths in configuration files and avoid post-install file >> hackery... :-) > > Mario, > > That does make sense, but there were no path changes unless as a > result of > the postfix upgrade from 2.11.2 to 2.11.3. And, in that case, either > postfix > or the SBo build script should have accommodated it. When the next > upgrade > is installed we'll see if the issue re-appears. If it does, then further > digging to find what's different in my system would be warranted. > > Rich Sorry for late reply, but it would help figuring it out if you resolved variables pasted in one of the previous emails... -- Mario From rshepard at appl-ecosys.com Tue Jan 13 16:52:22 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 13 Jan 2015 08:52:22 -0800 (PST) Subject: [Slackbuilds-users] Postfix-2.11.3 test warning message In-Reply-To: <54B4C0D5.9050400@slackware.hr> References: <54AEF0F0.20101@slackware.hr> <54AF3DF7.3030101@slackware.hr> <54B4C0D5.9050400@slackware.hr> Message-ID: On Tue, 13 Jan 2015, Mario Preksavec wrote: > Sorry for late reply, but it would help figuring it out if you resolved > variables pasted in one of the previous emails... Mario, Will do so if issue re-appears after next postfix upgrade. Rich From bgrundy at gmail.com Wed Jan 14 03:34:26 2015 From: bgrundy at gmail.com (Barry Grundy) Date: Tue, 13 Jan 2015 22:34:26 -0500 Subject: [Slackbuilds-users] Pyparsing Update? Message-ID: I'd like to eventually submit a SlackBuild for the Plaso project (forensic super-timeline). One of the (many) deps for Plaso is pyparsing. Plaso requires the current version - pyparsing v2.0.3. The version on SBo is 2.0.1. I've contacted the maintainer a couple of times over the past month (via email) offering to provide the updated build (a simple version bump) or to take over maintenance. I've not received any response as of yet. Given the time of year (holidays, etc.) I wanted to give a couple of weeks before reaching out to the this list, but I'm at the point where I'm not sure what to do. I have and upcoming class, and having Plaso on SBo would be most helpful. The SlackBuild update is available here: https://github.com/bgrundy/bgrundy_slackbuilds/tree/master/pyparsing ...and I would be happy to take over maintenance if the current maintainer has fallen off the grid. Packages that depend on pyparsing include: audio/puddletag network/spice libraries/matplotlib All build fine with the new version. Thanks, -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Jan 14 04:09:58 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 14 Jan 2015 11:09:58 +0700 Subject: [Slackbuilds-users] Pyparsing Update? In-Reply-To: References: Message-ID: <54B5EC16.1060900@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I'd like to eventually submit a SlackBuild for the Plaso project > (forensic super-timeline). One of the (many) deps for Plaso is > pyparsing. > > Plaso requires the current version - pyparsing v2.0.3. The version > on SBo is 2.0.1. I've contacted the maintainer a couple of times > over the past month (via email) offering to provide the updated > build (a simple version bump) or to take over maintenance. I've not > received any response as of yet. > > Given the time of year (holidays, etc.) I wanted to give a couple > of weeks before reaching out to the this list, but I'm at the point > where I'm not sure what to do. I have and upcoming class, and > having Plaso on SBo would be most helpful. > > The SlackBuild update is available here: > https://github.com/bgrundy/bgrundy_slackbuilds/tree/master/pyparsing > > > > ...and I would be happy to take over maintenance if the current > maintainer has fallen off the grid. Looking at the git log, it seems that the maintainer hasn't updated this package since 2 years ago. You can submit an update to this package and take over this package if you wish - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS17BYACgkQiHuDdNczM4EKyQCeIqDcU974XFWTE32vH3m80yBf KeIAn3lGAtDyaEF5troKuUSYiX5tW28M =Wv98 -----END PGP SIGNATURE----- From hostmaster at slackonly.com Thu Jan 15 12:10:55 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Thu, 15 Jan 2015 14:10:55 +0200 Subject: [Slackbuilds-users] adobe-source-code-pro-font Message-ID: <54B7AE4F.6030105@slackonly.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, adobe-source-code-pro-font download link not working because project is not hosted any more to sourceforge... New download link: http://pkgs.fedoraproject.org/repo/pkgs/adobe-source-code-pro-fonts/SourceCodePro_FontsOnly-1.017.zip/e59ce4be04d44c22e380865142bad0e3/SourceCodePro_FontsOnly-1.017.zip (md5sum match) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBAgAGBQJUt65PAAoJEHEA/7TwEbKGEwkP/2+hD5HNoXOJJKYumk77EAfp pzM4zHDIkPaV8+Ek4ZiMEjbGniQ54DZdLZcc5Q5nNkybFcM7PYD8yKceZyIY3gQY yRJPZpPxE72Hz0fJb34cEedLsdpDgToS0CfepPCTrjmw8S+9owdJGc496FTKV2d3 VuIH9pqK1fmzqqaXGpu63mRXGfYAP/Oe/KL/N0pVzbyBvwqxdDW72Qpsn1h0YjQ3 /7EqaTVEsosuBzIcGwJbyYJDH7oAwrHNdorHjt4pBpACqXscwnU5CnsRAJzU9HEc LiDSYnJV/vofe1htW+r3rHmddIYtFpowNlvVzWxjN8x960OHaGREteYiIOb7HX2t imfLIkF4vVjxPV85308NkiGAgM6nHLHLAO2TvlvCZvX4rLfuj6nUSv2KNDbi2Rzf Q3Sf0B2AxcSwBoSZK8hNnPKtJUDFoYLCZ2JIGB563SB+CTABkmnP6l5HHO27WAv2 gkWeUQZ7Hv/tqaVm9uHxIMdlPr6BQvcUaCdTJyq8uv59381DIueHaCXuvJnM4W/J 4MJpEXCt1Epkz/947FJUmyrB0ud/Lzmv9jQa1N9enab84sR52t7f+3L9lzlLUEcc JqoXZB8dPkM4+5WcOSoVhG2cGarwpjXWU0FcA05QZQ891JmjEyZKAJpkCNLLb8uV 2twZ18p2+yKbZzWk2yPY =Zawj -----END PGP SIGNATURE----- From marc at mos6581.de Thu Jan 15 13:15:31 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Thu, 15 Jan 2015 14:15:31 +0100 Subject: [Slackbuilds-users] mlbrot build fails Message-ID: <54B7BD73.7030502@mos6581.de> The configure script is searching for lablgtk in the wrong path. The defined gtkdir on line 72 should be gtkdir="+site-lib/lablgtk2" While this is present in the newer version 1.01 on line 72, it immediately gets overwritten on line 73. -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Jan 15 17:01:01 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 16 Jan 2015 00:01:01 +0700 Subject: [Slackbuilds-users] mlbrot build fails In-Reply-To: <54B7BD73.7030502@mos6581.de> References: <54B7BD73.7030502@mos6581.de> Message-ID: <54B7F24D.20303@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The configure script is searching for lablgtk in the wrong path. > The defined gtkdir on line 72 should be > > gtkdir="+site-lib/lablgtk2" > > While this is present in the newer version 1.01 on line 72, it > immediately gets overwritten on line 73. Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS38k0ACgkQiHuDdNczM4GNTACgnHkk7ewo60zhJokumj81Wci0 SbUAnAlwwWh6//u90AJRJN1aYUR/3qre =J2Y2 -----END PGP SIGNATURE----- From willysr at slackbuilds.org Thu Jan 15 17:07:12 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 16 Jan 2015 00:07:12 +0700 Subject: [Slackbuilds-users] adobe-source-code-pro-font In-Reply-To: <54B7AE4F.6030105@slackonly.com> References: <54B7AE4F.6030105@slackonly.com> Message-ID: <54B7F3C0.90808@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > adobe-source-code-pro-font download link not working because > project is not hosted any more to sourceforge... > > New download link: > http://pkgs.fedoraproject.org/repo/pkgs/adobe-source-code-pro-fonts/SourceCodePro_FontsOnly-1.017.zip/e59ce4be04d44c22e380865142bad0e3/SourceCodePro_FontsOnly-1.017.zip > > (md5sum match) fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS388AACgkQiHuDdNczM4EY+ACgpi4JOn44iuxQKV7VLm2qrNJt xkQAn0I7xy+7x7pvltHqR586vKpzdoUK =sInE -----END PGP SIGNATURE----- From audrius at neutrino.lt Thu Jan 15 20:32:56 2015 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Thu, 15 Jan 2015 22:32:56 +0200 Subject: [Slackbuilds-users] Possible typo in python3.SlackBuild In-Reply-To: <54B1D3F4.2060005@iinet.net.au> References: <54AF76BC.6060802@microlinux.fr> <54AF7EC3.3060505@iinet.net.au> <20150109173403.GC26219@tux.acadiau.ca> <20150109184530.GA1324@varna> <20150110151408.GD23467@jdiamond-nb> <54B1D3F4.2060005@iinet.net.au> Message-ID: <20150115203256.GA17317@varna> On Sun, 2015-01-11 at 11:37:56 +1000, Christoph Willing wrote: > If we're looking for something more robust, yet generic, then my previously > proposed solution: > PYVER=${VERSION%.*} > is not so great if a version string has extra fields i.e. VERSION=3.4.2.5 > would become 3.4.2 (rather than the desired 3.4). > > To make up for that shortcoming, I offer: > PYVER=$(sed 's/\.[^\.]*//2g' <<< "$VERSION") > > Maybe not as easy to read as Audrius' solution using cut though ... I decided to use my solution. Thanks for suggestions guys, and making me aware of the issue in the first place. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From rshepard at appl-ecosys.com Fri Jan 16 18:01:53 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 16 Jan 2015 10:01:53 -0800 (PST) Subject: [Slackbuilds-users] SQLite-ODBC Driver? Message-ID: I'd like to use SQLite3 as a single-user, embedded rdbms in a LibreOffice Base application. I don't see a driver in the SBo repository; perhaps I'm using incorrect search terms. Is there a SBo package for an ODBC driver for this database? Rich From ts at websafe.pl Sat Jan 17 02:05:42 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 17 Jan 2015 03:05:42 +0100 Subject: [Slackbuilds-users] Kivy - is this OK? Message-ID: <54B9C376.70401@websafe.pl> I've built Kivy on multiple machines with slpkg, but now there's a problem with the same slackbuild: ~~~~ +============================================================================== | MD5SUM check for 1.8.0.tar.gz [ PASSED ] +============================================================================== tar: /tmp/slpkg/build/Kivy/kivy-1.8.0.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now ./Kivy.SlackBuild: line 64: xvf: command not found Total build time for package Kivy : 0.14 Sec ~~~~ The problematic line is: ~~~~ tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || xvf $CWD/$VERSION.tar.gz ~~~~ Is that OK: "|| xvf $CWD/$VERSION.tar.gz"? IMVHO it should be " || tar xvf $CWD/$VERSION.tar.gz" or am I wrong? ^^^ On other machines I had "--content-disposition" in wget flags, on this machine I forgot about setting this, that's why the part after "||" is being called. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ryan.q at linux.com Sat Jan 17 02:17:17 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 17 Jan 2015 02:17:17 +0000 Subject: [Slackbuilds-users] Kivy - is this OK? References: <54B9C376.70401@websafe.pl> Message-ID: >~~~~ >tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || >xvf $CWD/$VERSION.tar.gz >~~~~ Just a typo, needs 'tar' in front of the second command. But may I suggest changing it to: if [ -e $CWD/$VERSION.tar.gz ]; then tar xvf $CWD/$VERSION.tar.gz else tar xvf $CWD/$SRCNAM-$VERSION.tar.gz fi That way you won't get an error message if the file isn't there in one form. ;-) On Fri, Jan 16, 2015, 6:05 PM Thomas Szteliga wrote: I've built Kivy on multiple machines with slpkg, but now there's a problem with the same slackbuild: ~~~~ +============================================================================== | MD5SUM check for 1.8.0.tar.gz [ PASSED ] +============================================================================== tar: /tmp/slpkg/build/Kivy/kivy-1.8.0.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now ./Kivy.SlackBuild: line 64: xvf: command not found Total build time for package Kivy : 0.14 Sec ~~~~ The problematic line is: ~~~~ tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || xvf $CWD/$VERSION.tar.gz ~~~~ Is that OK: "|| xvf $CWD/$VERSION.tar.gz"? IMVHO it should be " || tar xvf $CWD/$VERSION.tar.gz" or am I wrong? ^^^ On other machines I had "--content-disposition" in wget flags, on this machine I forgot about setting this, that's why the part after "||" is being called. -- Thomas Szteliga _______________________________________________ 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 lacielacie at rocketmail.com Sat Jan 17 02:22:48 2015 From: lacielacie at rocketmail.com (KaMii) Date: Fri, 16 Jan 2015 18:22:48 -0800 Subject: [Slackbuilds-users] Transmission fails to install transmission-qt.desktop file. Message-ID: <20150116182248.6a336074@Andromdeda.andromeda.gal> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have noticed that transmission builds with qt, but it fails to install the transmission-qt.desktop files. These commands will install the the proper files. mkdir -p $PKG/usr/share/applications mkdir -p $PKG/usr/share/pixmaps install -m644 $TMP/$PRGNAM-$VERSION/qt/transmission-qt.desktop $PKG/usr/share/applications/transmission-qt.desktop install -m644 $TMP/$PRGNAM-$VERSION/qt/icons/transmission.png $PKG/usr/share/pixmaps/transmission-qt.png - -KaMii -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlS5x3gACgkQkO84ARmAdEANkAQA3o6ir6kedchPYdZHNB6N1Dna 0bErJ4E3fWezbUZKBmAfZHFy83a+lSWrFrFjeMtnIYP2AnRudB7/hlauRMht3LYL zFRvFZYpLD8qRoq9wSNriJMwgTnAt8HHASkawP4tF/die103RuN6L32Yf9pc6T02 VFhm2iWrjjqkeIyQpUg= =FTVQ -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Jan 17 02:29:40 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Jan 2015 09:29:40 +0700 Subject: [Slackbuilds-users] Kivy - is this OK? In-Reply-To: <54B9C376.70401@websafe.pl> References: <54B9C376.70401@websafe.pl> Message-ID: <54B9C914.5090804@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I've built Kivy on multiple machines with slpkg, but now there's a > problem with the same slackbuild: > > ~~~~ > +============================================================================== > > | MD5SUM check for 1.8.0.tar.gz [ PASSED ] > +============================================================================== > > tar: /tmp/slpkg/build/Kivy/kivy-1.8.0.tar.gz: Cannot open: No such > file or directory tar: Error is not recoverable: exiting now > ./Kivy.SlackBuild: line 64: xvf: command not found Total build time > for package Kivy : 0.14 Sec ~~~~ > > > > The problematic line is: > > ~~~~ tar xvf $CWD/$SRCNAM-$VERSION.tar.gz || xvf > $CWD/$VERSION.tar.gz ~~~~ > > > Is that OK: "|| xvf $CWD/$VERSION.tar.gz"? > > > IMVHO it should be " || tar xvf $CWD/$VERSION.tar.gz" or am I > wrong? ^^^ > > On other machines I had "--content-disposition" in wget flags, on > this machine I forgot about setting this, that's why the part after > "||" is being called. fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS5yRQACgkQiHuDdNczM4EY8gCfc2aCTJCfmxV8BrMYCFc1xWiN yNcAoImZufwf+n7CMElyJRtgJTXJ6fqP =eZfW -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Jan 17 02:45:36 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Jan 2015 09:45:36 +0700 Subject: [Slackbuilds-users] Transmission fails to install transmission-qt.desktop file. In-Reply-To: <20150116182248.6a336074@Andromdeda.andromeda.gal> References: <20150116182248.6a336074@Andromdeda.andromeda.gal> Message-ID: <54B9CCD0.2070500@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I have noticed that transmission builds with qt, but it fails to > install the transmission-qt.desktop files. These commands will > install the the proper files. > > mkdir -p $PKG/usr/share/applications mkdir -p > $PKG/usr/share/pixmaps install -m644 > $TMP/$PRGNAM-$VERSION/qt/transmission-qt.desktop > $PKG/usr/share/applications/transmission-qt.desktop install -m644 > $TMP/$PRGNAM-$VERSION/qt/icons/transmission.png > $PKG/usr/share/pixmaps/transmission-qt.png Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS5zNAACgkQiHuDdNczM4FQlwCfVCUmS4hBZRP3z+y9nQbomsrt bWgAoJfRG0aVH7zTX1XT89EIF0hqWCXg =bdwD -----END PGP SIGNATURE----- From ts at websafe.pl Sat Jan 17 18:52:00 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 17 Jan 2015 19:52:00 +0100 Subject: [Slackbuilds-users] SDL2_mixer compilation fails Message-ID: <54BAAF50.6010407@websafe.pl> SDL2_mixer compilation fails with: ~~~~ libtool: compile: gcc -O2 -fPIC -D_GNU_SOURCE=1 -D_REENTRANT -I/usr/include/SDL2 -DHAVE_SIGNAL_H -DHAVE_SETBUF -fvisibility=hidden -DHAVE_FORK -DCMD_MUSIC -DWAV_MUSIC -DMODPLUG_MUSIC -DMODPLUG_DYNAMIC=\"libmodplug.so.1\" -DMID_MUSIC -DUSE_TIMIDITY_MIDI -I./timidity -DOGG_MUSIC -DOGG_DYNAMIC=\"libvorbisfile.so.3\" -DFLAC_MUSIC -DFLAC_DYNAMIC=\"libFLAC.so.8\" -MMD -MT build/mixer.lo -c mixer.c -fPIC -DPIC -o build/.libs/mixer.o In file included from mixer.c:38:0: dynamic_modplug.h:24:21: fatal error: modplug.h: No such file or directory #include "modplug.h" ^ compilation terminated. make: *** [build/mixer.lo] Error 1 Total build time for package SDL2_mixer : 6.16 Sec ~~~~ I found this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725564 Adding "-I/usr/include/libmodplug" to the compiler flags solved the problem. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sat Jan 17 19:15:45 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 17 Jan 2015 20:15:45 +0100 Subject: [Slackbuilds-users] SDL2_mixer compilation fails In-Reply-To: <54BAAF50.6010407@websafe.pl> References: <54BAAF50.6010407@websafe.pl> Message-ID: <54BAB4E1.3070209@websafe.pl> On 01/17/2015 07:52 PM, Thomas Szteliga wrote: > SDL2_mixer > > compilation fails with: SDL2_mixer compilation fails only on machines where `libmodplug` is installed (which is an optional dep for SDL2_mixer). Without libmodplug installed everything is fine. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From klaatu at straightedgelinux.com Sat Jan 17 23:46:02 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Sun, 18 Jan 2015 12:46:02 +1300 Subject: [Slackbuilds-users] SDL2_mixer compilation fails In-Reply-To: <54BAB4E1.3070209@websafe.pl> References: <54BAAF50.6010407@websafe.pl> <54BAB4E1.3070209@websafe.pl> Message-ID: <54BAF43A.2070302@straightedgelinux.com> On 01/18/2015 08:15 AM, Thomas Szteliga wrote: > On 01/17/2015 07:52 PM, Thomas Szteliga wrote: >> SDL2_mixer >> >> compilation fails with: > > > SDL2_mixer compilation fails only on machines where `libmodplug` > > is installed (which is an optional dep for SDL2_mixer). Without > libmodplug installed everything is fine. > > > > _______________________________________________ > 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/ > Coincidentally, I compiled this last night and happen to have libmodplug installed, and the compile and install worked as expected with this wee little patch: sed -i 's_modplug.h_/usr/include/libmodplug/modplug.h_' dynamic_modplug.h || exit 1 sed -i 's_modplug.h_/usr/include/libmodplug/modplug.h_' music_modplug.h || exit 1 -klaatu --- klaatu http://slackermedia.info From ryan.q at linux.com Sun Jan 18 01:34:16 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 17 Jan 2015 17:34:16 -0800 Subject: [Slackbuilds-users] higan md5sum mismatch Message-ID: It seems the upstream DOWNLOAD url has changed. Grabbing the tarball from: http://files.byuu.org/download/higan_v094-source.tar.xz Yields the same md5sum as the .info script. a0e8730f64f0ba666b4282b8145b8c31 higan_v094-source.tar.xz But grabbing from the link on SBo: http://byuu.net/files/higan_v094-source.tar.xz Yields: 5f04623c10da5d243ef13cb63f2f990a I recommend updating .info with this url: http://files.byuu.org/download/higan_v094-source.tar.xz Cheers, Ryan -- --- From willysr at slackbuilds.org Sun Jan 18 01:38:16 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 18 Jan 2015 08:38:16 +0700 Subject: [Slackbuilds-users] higan md5sum mismatch In-Reply-To: References: Message-ID: <54BB0E88.8060201@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > It seems the upstream DOWNLOAD url has changed. Grabbing the > tarball from: > > http://files.byuu.org/download/higan_v094-source.tar.xz > > Yields the same md5sum as the .info script. > > a0e8730f64f0ba666b4282b8145b8c31 higan_v094-source.tar.xz > > But grabbing from the link on SBo: > > http://byuu.net/files/higan_v094-source.tar.xz > > Yields: > > 5f04623c10da5d243ef13cb63f2f990a > > > I recommend updating .info with this url: > > http://files.byuu.org/download/higan_v094-source.tar.xz Fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS7DogACgkQiHuDdNczM4F4jwCglZQrUyTXUo6332d3CPJqMd6O uFcAnApmzAIDwJYioQVJsYE/rZquhOnD =hJ8J -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sun Jan 18 02:23:52 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 18 Jan 2015 09:23:52 +0700 Subject: [Slackbuilds-users] Updates - 20150118.1 Message-ID: <54BB1938.7060704@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sun Jan 18 02:10:14 UTC 2015 accessibility/pastebinit: Fix script. audio/discord: Update script. audio/mp3splt-gtk: Updated for version 0.9.2. audio/mp3splt: Updated for version 2.6.2. audio/qastools: Updated for version 0.18.1. audio/sidplayfp: Added (SID Player). desktop/q4wine: Update HOMEPAGE. desktop/rofi: Fix VERSION. desktop/ssr: Updated for version 0.3.3. desktop/trayer-srg: Updated for version 20141126. development/SDL2_mixer: Disable modplug support. development/gnuradio: Updated for version 3.7.5.1 + new maintainer. development/gr-osmosdr: Added (toolkit for building SDRs). development/hackrf: Added (radio platform). development/icoutils: Updated for version 0.31.0. development/osmo-sdr: Added (toolkit for building SDRs). development/poedit: Updated for version 1.7.3. development/vstudio: Updated for version 5.7. games/d1x-rebirth: Update EMAIL. games/d2x-rebirth: Update EMAIL. games/hedgewars: Updated for version 0.9.21.1. games/higan: Update DOWNLOAD url. games/instead: Update CMake Parameters. games/steam: Fix script. graphics/fontforge: Updated for version 20141126. graphics/mlbrot: Fix build. ham/rtl-sdr: Added (Realtek RTL2832 Driver). libraries/Kivy: Fix script. libraries/http-parser: Added (HTTP request/response parser). libraries/jsoncpp: Updated for version 1.1.0. libraries/libaacs: Fix DOWNLOAD url. libraries/libbde: Updated for version 20150106. libraries/libbluray: Update DOWNLOAD url. libraries/libfdk-aac: Added (Fraunhofer FDK AAC). libraries/libjpeg-turbo: Updated for version 1.4.0. libraries/libmp3splt: Updated for version 0.9.2. libraries/libosmo-dsp: Added (library with SDR primitives). libraries/libvdpau: Updated for version 0.9. libraries/libvhdi: Updated for version 20150110. libraries/mysql-connector-c++: Update DOWNLOAD url. libraries/qt5: Added optional documentation and example options. libraries/webkitgtk3: Updated for version 2.4.8. libraries/webkitgtk: Updated for version 2.4.8. libraries/wxsvg: Updated for version 1.5. libraries/zend-opcache: Updated for version 7.0.4. misc/gr-iqbal: Added (IQBalance Block). multimedia/dvdstyler: Updated for version 2.8.1. multimedia/fdkaac: Added (frontend for libfdk-aac). multimedia/flashplayer-plugin: Updated for version 11.2.202.429. multimedia/l-smash: Added (OpenSource mp4 handler). multimedia/lives: Updated for version 2.2.6. multimedia/picard-plugins: Updated for version 20150112. network/Pafy: Updated for version 0.3.68. network/bitcoin: Updated for version 0.9.4. network/ettercap: Updated for version 0.8.1, changed homepage. network/exim: Updated for version 4.85. network/flexget: Updated for version 1.2.263. network/pentadactyl: Updated to work with Firefox 35.0. network/tor-browser: Updated for version 4.0.3. network/transmission: Add transmission-qt. network/weechat: Updated for version 1.1. office/MasterPDFEditor: Updated for version 2.2.06. office/Ted: Update HOMEPAGE url. office/tasksh: Added (command-line todo list manager). perl/perl-DateTime: Fixed requires. python/astroid: Updated for version 1.3.3. python/boto3: Added (Python API for AWS). python/colorama: Updated for version 0.3.3. python/dfvfs: Updated for version 20150108. python/dulwich: Updated for version 0.9.8. python/psutil: Updated for version 2.2.0. python/pyparsing: Updated for version 2.0.3 + new maintainer. python/python-dateutil: Updated for version 2.4.0. python/python3: More robust major version detection. system/TLP: Update README.Slackware. system/adobe-source-code-pro-font: Update DOWNLOAD url. system/colord: Added (Color Profile System Service) system/fcron: Fix README and doinstall.sh. system/hh: Updated for version 1.15. system/hwloc: Added (Portable Hardware Locality). system/libfm: Added the needed dependency lxmenu-data. system/lxsession: Added the needed dependency libunique. system/numactl: Updated for version 2.0.9. system/nvidia-driver: Updated for version 340.65. system/nvidia-kernel: Updated for version 340.65. system/pcmanfm: Re-include the empty modules folder, JIC. system/profile-sync-daemon: Updated for version 5.61. system/redis: Updated for version 2.8.19. system/winusb: Added (USB Stick Windows Installer Creator). +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS7GTgACgkQiHuDdNczM4Ej7gCdHSvDlHeujHjHy/r//5yWtaus 8oEAn20cVge4mJpEvg31ek8eNR5gOyqf =R9Fn -----END PGP SIGNATURE----- From ryan.q at linux.com Sun Jan 18 03:06:57 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sun, 18 Jan 2015 03:06:57 +0000 Subject: [Slackbuilds-users] higan md5sum mismatch References: <54BB0E88.8060201@slackbuilds.org> Message-ID: On Sat, Jan 17, 2015, 5:38 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > It seems the upstream DOWNLOAD url has changed. Grabbing the > tarball from: > > http:// files.byuu.org /download/ higan _ v094-source.tar.xz > > Yields the same md5sum as the .info script. > > a0e8730f64f0ba666b4282b8145b8c31 higan_v094-source.tar.xz > > But grabbing from the link on SBo: > > http:// byuu.net /files/ higan _ v094-source.tar.xz > > Yields: > > 5f04623c10da5d243ef13cb63f2f990a > > > I recommend updating .info with this url: > > http:// files.byuu.org /download/ higan _ v094-source.tar.xz Fixed in my branch thanks. :-) - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS7DogACgkQiHuDdNczM4F4jwCglZQrUyTXUo6332d3CPJqMd6O uFcAnApmzAIDwJYioQVJsYE/rZquhOnD =hJ8J -----END PGP SIGNATURE----- _______________________________________________ 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 hba.nihilismus at gmail.com Tue Jan 20 00:50:10 2015 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Mon, 19 Jan 2015 18:50:10 -0600 Subject: [Slackbuilds-users] Some issues with Apache Tomcat Message-ID: Hi, i'm trying to understand how it is integrated Apache Tomcat into Slackware using the available SlackBuild at SBo. First some facts: * $CATALINA_HOME and $CATALINA_BASE are **global** environment variables. * $CATALINA_HOME is set to /usr/share/tomcat * $CATALINA_BASE is set to /var/lib/tomcat * Inside $CATALINA_HOME: * bin/ * lib/ * Inside $CATALINA_BASE: * bin -> /usr/share/tomcat/bin/ * conf -> /etc/tomcat/ * logs -> /var/log/tomcat/ * temp -> /var/tmp/tomcat/ * webapps/ * work -> /var/run/tomcat/ * /etc/rc.d/rc.tomcat has hardcoded values for $PIDFILE, $LOGFILE and $USER, and expects the environment variable $CATALINA_BASE has been already defined (which it is since it is a **global** environment variable). Now the questions/issues: * Trying to integrate $CATALINA_BASE into Eclipse does not work, i get the message: "Unknown version of Tomcat was specified." And from Netbeans i get: "The specified Server Location (Catalina Home) folder is not valid." This is because there is not a lib directory inside $CATALINA_BASE so to fix it one must execute (as root): # ln -s $CATALINA_HOME/lib $CATALINA_BASE/ Trying to integrate $CATALINA_HOME neither, i get the error message from Eclipse: "Could not load the Tomcat server configuration at /Servers/Tomcat v7.0 Server at localhost-config. The configuration may be corrupt or incomplete." And from Netbeans: "The /conf/server.xml can't be read." To fix it one must execute (as root): # ln -s /etc/tomcat/ $CATALINA_HOME/conf * Once i try to execute Apache Tomcat with Netbeans i get the error: "Starting of Tomcat failed, check whether the /usr/share/tomcat/bin/catalina.sh and related scripts are executable" To fix it execute (as root): # chmod +x $CATALINA_HOME/bin/*.sh So finally some questions: * Why the distinction between $CATALINA_HOME and $CATALINA_BASE?. As i understand this is just when you want to have multiple instances of Apache Tomcat, each one sharing some directories from $CATALINA_HOME while keeping their own configuration/libraries [1] [2] [3] [4] separated. Actually, this is what Eclipse/Netbean does, it ask you for $CATALINA_HOME and create a $CATALINA_BASE directory to manage it execution ("Create a local server"). IMHO there should not be $CATALINA_BASE **globally**, but **locally** (/etc/rc.d/rc.tomcat maybe). But remember that /etc/rc.d/rc.tomcat has hardcoded values for $PIDFILE, $LOGFILE and $USER to work with $CATALINA_BASE so i am not sure this is the case for multiple instances. Anyway these environment variable would be uniques to each instance of tomcat (if this is the case) so a better place to define them would be $CATALINA_BASE/conf/tomcat-java.conf, which brings the next question. * Why the configuration files are keep in /etc/tomcat?. Is this some kind of "HIER or die!"? ;-) * And finally, why the $CATALINA_HOME/bin/*.sh files are keep with 0744 as permission? It is for some kind of security?. I hope to make clear my questions and not generate more ;-) - Cheers [1] http://tomcat.apache.org/tomcat-7.0-doc/RUNNING.txt [2] http://java.dzone.com/articles/running-multiple-tomcat [3] http://www.ramkitech.com/2011/07/running-multiple-tomcat-instances-on.html [4] http://blogs.vmware.com/vfabric/2012/10/5-scenarios-and-best-practices-for-running-multiple-instances-of-tomcat-or-tc-server.html -- Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas at beingboiled.info Tue Jan 20 10:35:15 2015 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 20 Jan 2015 11:35:15 +0100 (CET) Subject: [Slackbuilds-users] PostgreSQL & /usr/share/postgresql Message-ID: Hello there, I noticed a minor problem with the PostgreSQL SlackBuild. The script installs all libs and binaries into a path containing the version number, e.g. /usr/lib64/postgresql/9.4. This allows a parallel install of two versions which is required for the pg_upgrade utility. As I now noticed the files in /usr/share/postgresql are version dependent, too. Installing 9.4 overwrote the 'Default' time zone set, but 9.3 couldn't parse the enhanced syntax and pg_upgrade failed. I'd suggest adding "--datadir=/usr/share/$PRGNAM/$PG_VERSION" to the SlackBuild's configure call. This will keep extensions, time zone sets and auxilliary files for text search separate between versions. -- From adis at linux.org.ba Tue Jan 20 18:33:06 2015 From: adis at linux.org.ba (Adis Nezirovic) Date: Tue, 20 Jan 2015 19:33:06 +0100 Subject: [Slackbuilds-users] PostgreSQL & /usr/share/postgresql In-Reply-To: References: Message-ID: Thomas, Thanks for the report, you are correct that 9.4 changed slightly format of "timezone_abbreviations" files. The proposed solution solves the issue completely (old db cluster can't start cleanly), and I'll submit new Slackbuild shortly. Best regards, Adis From ivanp84 at gmail.com Wed Jan 21 00:26:21 2015 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Wed, 21 Jan 2015 01:26:21 +0100 Subject: [Slackbuilds-users] povray compiling problem Message-ID: Hi guys. I'm running S64 current (Dec 2014), and I have a problem with povray. SB script breaks before compiling begins. Ends with a following lines: Makefiles --------- checking that generated files are newer than configure... done configure: creating ./config.status config.status: error: cannot find input file: `Makefile.in' Anyone faced a similar problem? Actually, I did not take a look to the script, but the error sounds bizarre after the fact that someone actually tested the script and probably dozens compiled povray without errors. Greets, Ivan -- If you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Jan 21 11:10:33 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 21 Jan 2015 18:10:33 +0700 Subject: [Slackbuilds-users] povray compiling problem In-Reply-To: References: Message-ID: <54BF8929.2030100@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Hi guys. I'm running S64 current (Dec 2014), and I have a problem > with povray. SB script breaks before compiling begins. Ends with a > following lines: > > Makefiles --------- checking that generated files are newer than > configure... done configure: creating ./config.status > config.status: error: cannot find input file: `Makefile.in' > > Anyone faced a similar problem? Actually, I did not take a look to > the script, but the error sounds bizarre after the fact that > someone actually tested the script and probably dozens compiled > povray without errors. it worked here on Slackware64-14.1 VM without any modification Done building package for povray. Built package: povray-3.7.0.0-x86_64-1_SBo.tgz +++++++++++++++++++++++++++++++++++++++++++ SUMMARY LOG Using the SBo repository for Slackware 14.1 Queue Process: Download and build povray: MD5SUM check for v3.7.0.0.tar.gz ... OK Building package povray-3.7.0.0-x86_64-1_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS/iSgACgkQiHuDdNczM4F3IACfVTqrmd5la0GQPu6ODcNfa0Oh IRQAn28CN8XLT2axqCajcl65RmE2WK3/ =4mP5 -----END PGP SIGNATURE----- From ivanp84 at gmail.com Wed Jan 21 12:12:30 2015 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Wed, 21 Jan 2015 13:12:30 +0100 Subject: [Slackbuilds-users] povray compiling problem In-Reply-To: <54BF8929.2030100@slackbuilds.org> References: <54BF8929.2030100@slackbuilds.org> Message-ID: Same problem, again and again... even when I tried built process by hand, again Makefile.in missed... Tonight I'll try to figure out what is going on. On Wed, Jan 21, 2015 at 12:10 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Hi guys. I'm running S64 current (Dec 2014), and I have a problem > > with povray. SB script breaks before compiling begins. Ends with a > > following lines: > > > > Makefiles --------- checking that generated files are newer than > > configure... done configure: creating ./config.status > > config.status: error: cannot find input file: `Makefile.in' > > > > Anyone faced a similar problem? Actually, I did not take a look to > > the script, but the error sounds bizarre after the fact that > > someone actually tested the script and probably dozens compiled > > povray without errors. > > it worked here on Slackware64-14.1 VM without any modification > > Done building package for povray. > Built package: povray-3.7.0.0-x86_64-1_SBo.tgz > > +++++++++++++++++++++++++++++++++++++++++++ > SUMMARY LOG > Using the SBo repository for Slackware 14.1 > Queue Process: Download and build > > povray: > MD5SUM check for v3.7.0.0.tar.gz ... OK > Building package povray-3.7.0.0-x86_64-1_SBo.tgz ... OK > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlS/iSgACgkQiHuDdNczM4F3IACfVTqrmd5la0GQPu6ODcNfa0Oh > IRQAn28CN8XLT2axqCajcl65RmE2WK3/ > =4mP5 > -----END PGP SIGNATURE----- > _______________________________________________ > 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/ > > -- If you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Jan 21 12:59:14 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 21 Jan 2015 19:59:14 +0700 Subject: [Slackbuilds-users] povray compiling problem In-Reply-To: References: <54BF8929.2030100@slackbuilds.org> Message-ID: <54BFA2A2.80105@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Same problem, again and again... even when I tried built process by > hand, again Makefile.in missed... Tonight I'll try to figure out > what is going on. add this before running ./prebuild.sh sed 's/automake --w/automake --add-missing --w/g' -i prebuild.sh - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlS/oqIACgkQiHuDdNczM4E+aQCgpjanD5JKIuMryMZ5k8Yme062 06EAn3QFgi0VND17HjfPVmEJXN3D0R2g =U0q7 -----END PGP SIGNATURE----- From ivanp84 at gmail.com Wed Jan 21 16:51:47 2015 From: ivanp84 at gmail.com (Ivan Pavicevic) Date: Wed, 21 Jan 2015 17:51:47 +0100 Subject: [Slackbuilds-users] povray compiling problem In-Reply-To: <54BFA2A2.80105@slackbuilds.org> References: <54BF8929.2030100@slackbuilds.org> <54BFA2A2.80105@slackbuilds.org> Message-ID: Thank you Willy! You really saved my day! I have built with SB script after editing with yours suggestion, changed line 84 this way: ( cd unix; sed 's/automake --w/automake --add-missing --w/g' -i prebuild.sh; sh ./prebuild.sh ) The changed script worked in classical manner. Cheers, Ivan On Wed, Jan 21, 2015 at 1:59 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Same problem, again and again... even when I tried built process by > > hand, again Makefile.in missed... Tonight I'll try to figure out > > what is going on. > > add this before running ./prebuild.sh > > sed 's/automake --w/automake --add-missing --w/g' -i prebuild.sh > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlS/oqIACgkQiHuDdNczM4E+aQCgpjanD5JKIuMryMZ5k8Yme062 > 06EAn3QFgi0VND17HjfPVmEJXN3D0R2g > =U0q7 > -----END PGP SIGNATURE----- > _______________________________________________ > 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/ > > -- If you don't care where you are, then you ain't lost -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrew.david.strong at gmail.com Wed Jan 21 22:50:52 2015 From: andrew.david.strong at gmail.com (andrew) Date: Thu, 22 Jan 2015 09:50:52 +1100 Subject: [Slackbuilds-users] eyeD3 requires... Message-ID: <20150121225052.GA16838@ilium.andrews-corner.org> Thanks for the fast review of the new eyeD3 script which now sits in the accepted queue. A small question though: a requirement has been added for python-magic which is an extra that would be installed with pip but is not required and can be omitted. Certainly it has never been required on my own system. Details here: http://eyed3.nicfit.net/installation.html#dependencies And thanks again for processing this so swiftly :) Andrew -- You think that's air you're breathing now? From willysr at slackbuilds.org Wed Jan 21 22:51:01 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 22 Jan 2015 05:51:01 +0700 Subject: [Slackbuilds-users] eyeD3 requires... In-Reply-To: <20150121225052.GA16838@ilium.andrews-corner.org> References: <20150121225052.GA16838@ilium.andrews-corner.org> Message-ID: <54C02D55.6070708@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Thanks for the fast review of the new eyeD3 script which now sits > in the accepted queue. A small question though: a requirement has > been added for python-magic which is an extra that would be > installed with pip but is not required and can be omitted. > Certainly it has never been required on my own system. > > Details here: > > http://eyed3.nicfit.net/installation.html#dependencies > > And thanks again for processing this so swiftly :) the script will DOWNLOAD python-magic if it's not installed during build this is something we tried to avoid since users might not be aware all downloadable source must be present in the DOWNLOAD or REQUIRES - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTALVUACgkQiHuDdNczM4HaKQCeMemWNxT2JnGNvWWLQMgLf4aK hzkAnjjrgRllWYMpJ/wzYbi5ZpIFWgFd =iG7n -----END PGP SIGNATURE----- From andrew.david.strong at gmail.com Wed Jan 21 23:15:50 2015 From: andrew.david.strong at gmail.com (andrew) Date: Thu, 22 Jan 2015 10:15:50 +1100 Subject: [Slackbuilds-users] eyeD3 requires... In-Reply-To: <54C02D55.6070708@slackbuilds.org> References: <20150121225052.GA16838@ilium.andrews-corner.org> <54C02D55.6070708@slackbuilds.org> Message-ID: <20150121231550.GA19537@ilium.andrews-corner.org> On Thu, Jan 22, 2015 at 05:51:01AM +0700, Willy Sudiarto Raharjo wrote: > the script will DOWNLOAD python-magic if it's not installed during build > this is something we tried to avoid since users might not be aware > all downloadable source must be present in the DOWNLOAD or REQUIRES But I believe this is only if eyeD3 is installed using pip directly? The slackbuild I have submitted does not use pip and does not install or use python-magic. Thanks again, Andrew -- You think that's air you're breathing now? From willysr at slackbuilds.org Wed Jan 21 23:36:28 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 22 Jan 2015 06:36:28 +0700 Subject: [Slackbuilds-users] eyeD3 requires... In-Reply-To: <20150121231550.GA19537@ilium.andrews-corner.org> References: <20150121225052.GA16838@ilium.andrews-corner.org> <54C02D55.6070708@slackbuilds.org> <20150121231550.GA19537@ilium.andrews-corner.org> Message-ID: <54C037FC.70504@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> the script will DOWNLOAD python-magic if it's not installed >> during build this is something we tried to avoid since users >> might not be aware all downloadable source must be present in the >> DOWNLOAD or REQUIRES > > But I believe this is only if eyeD3 is installed using pip > directly? The slackbuild I have submitted does not use pip and does > not install or use python-magic. run the slackbuild and see the build output it will download them and install them (python-magic) - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTAN/wACgkQiHuDdNczM4E+PwCfdrZD2oKPPrH2TymL/jpVQPcR g9sAoJYE+PiYz3og+/ekyf+sTpVOtf9k =oLqx -----END PGP SIGNATURE----- From andrew.david.strong at gmail.com Thu Jan 22 01:13:45 2015 From: andrew.david.strong at gmail.com (andrew) Date: Thu, 22 Jan 2015 12:13:45 +1100 Subject: [Slackbuilds-users] eyeD3 requires... In-Reply-To: <54C037FC.70504@slackbuilds.org> References: <20150121225052.GA16838@ilium.andrews-corner.org> <54C02D55.6070708@slackbuilds.org> <20150121231550.GA19537@ilium.andrews-corner.org> <54C037FC.70504@slackbuilds.org> Message-ID: <20150122011345.GA23872@ilium.andrews-corner.org> On Thu, Jan 22, 2015 at 06:36:28AM +0700, Willy Sudiarto Raharjo wrote: > >> the script will DOWNLOAD python-magic if it's not installed > >> during build this is something we tried to avoid since users > >> might not be aware all downloadable source must be present in the > >> DOWNLOAD or REQUIRES > > > > But I believe this is only if eyeD3 is installed using pip > > directly? The slackbuild I have submitted does not use pip and does > > not install or use python-magic. > > run the slackbuild and see the build output > it will download them and install them (python-magic) My deep apologies Willy! Of course when I looked at the output properly I saw: -------------------- eyeD3-0.7.5/src/eyed3/info.py Searching for python-magic Reading https://pypi.python.org/simple/python-magic/ Best match: python-magic 0.4.6 Downloading https://pypi.python.org/packages/2.7/p/python-magic/python_magic-0.4.6-py2.7.egg#md5=b016ddfa7d1e3d888eb64f3e8e44d933 Processing python_magic-0.4.6-py2.7.egg Moving python_magic-0.4.6-py2.7.egg to /tmp/SBo/eyeD3-0.7.5/.eggs ------------------ Thank you for catching this error in my script and thank you for all of your work :). Andrew -- You think that's air you're breathing now? From larryhaja at gmail.com Thu Jan 22 21:57:45 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Thu, 22 Jan 2015 13:57:45 -0800 Subject: [Slackbuilds-users] eyeD3 requires... In-Reply-To: <20150122011345.GA23872@ilium.andrews-corner.org> References: <20150121225052.GA16838@ilium.andrews-corner.org> <54C02D55.6070708@slackbuilds.org> <20150121231550.GA19537@ilium.andrews-corner.org> <54C037FC.70504@slackbuilds.org> <20150122011345.GA23872@ilium.andrews-corner.org> Message-ID: The gentoo folks seem to apply this to their eyed3.ebuild so that optional dependency python-magic is not automatically downloaded and installed. sed -i -e '/scripts/d' -e '/install_requires/d' pavement.py Ref: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-python/eyeD3/eyeD3-0.7.5.ebuild?revision=1.2&view=markup --Larry On Wed, Jan 21, 2015 at 5:13 PM, andrew wrote: > On Thu, Jan 22, 2015 at 06:36:28AM +0700, Willy Sudiarto Raharjo wrote: > > >> the script will DOWNLOAD python-magic if it's not installed > > >> during build this is something we tried to avoid since users > > >> might not be aware all downloadable source must be present in the > > >> DOWNLOAD or REQUIRES > > > > > > But I believe this is only if eyeD3 is installed using pip > > > directly? The slackbuild I have submitted does not use pip and does > > > not install or use python-magic. > > > > run the slackbuild and see the build output > > it will download them and install them (python-magic) > > My deep apologies Willy! Of course when I looked at the output > properly I saw: > > -------------------- > eyeD3-0.7.5/src/eyed3/info.py > Searching for python-magic > Reading https://pypi.python.org/simple/python-magic/ > Best match: python-magic 0.4.6 > Downloading > https://pypi.python.org/packages/2.7/p/python-magic/python_magic-0.4.6-py2.7.egg#md5=b016ddfa7d1e3d888eb64f3e8e44d933 > Processing python_magic-0.4.6-py2.7.egg > Moving python_magic-0.4.6-py2.7.egg to /tmp/SBo/eyeD3-0.7.5/.eggs > ------------------ > > Thank you for catching this error in my script and thank you for all > of your work :). > > Andrew > -- > You think that's air you're breathing now? > _______________________________________________ > 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 sbolokanov at abv.bg Fri Jan 23 17:18:26 2015 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Fri, 23 Jan 2015 19:18:26 +0200 (EET) Subject: [Slackbuilds-users] Xonotic update Message-ID: <1283320703.974465.1422033506642.JavaMail.apache@nm51.abv.bg> Here is a version bump for Xonotic 0.8.0 https://github.com/sbolokanov/slackbuilds.git -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From mfilpot at gmail.com Fri Jan 23 18:04:38 2015 From: mfilpot at gmail.com (Matthew Fillpot) Date: Fri, 23 Jan 2015 18:04:38 +0000 Subject: [Slackbuilds-users] Xonotic update References: <1283320703.974465.1422033506642.JavaMail.apache@nm51.abv.bg> Message-ID: Thank you for the update, I will have my son knock out the changes and submit the update this weekend. Thank you, Matthew Fillpot On Fri, Jan 23, 2015, 10:18 AM ????? ????????? wrote: > Here is a version bump for Xonotic 0.8.0 > > https://github.com/sbolokanov/slackbuilds.git > > -- ????? ????????? > _______________________________________________ > 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 andrew.david.strong at gmail.com Fri Jan 23 21:55:46 2015 From: andrew.david.strong at gmail.com (andrew) Date: Sat, 24 Jan 2015 08:55:46 +1100 Subject: [Slackbuilds-users] eyeD3 requires... In-Reply-To: References: <20150121225052.GA16838@ilium.andrews-corner.org> <54C02D55.6070708@slackbuilds.org> <20150121231550.GA19537@ilium.andrews-corner.org> <54C037FC.70504@slackbuilds.org> <20150122011345.GA23872@ilium.andrews-corner.org> Message-ID: <20150123215546.GA1076@ilium.andrews-corner.org> On Thu, Jan 22, 2015 at 01:57:45PM -0800, Larry Hajali wrote: > The gentoo folks seem to apply this to their eyed3.ebuild so that > optional dependency python-magic is not automatically downloaded and > installed. > > sed -i -e '/scripts/d' -e '/install_requires/d' pavement.py > > Ref: > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/dev-python/eyeD3/ > eyeD3-0.7.5.ebuild?revision=1.2&view=markup > > --Larry Thanks for this Larry. My own thought is that the script at the moment is most useful as Willy has set it. A future update may indeed remove the dependency with python-magic, I have contacted Travis (the developer of eyeD3) about the actual usage that eyeD3 makes of python-magic and the full implications of its removal. Thanks for looking at this, Andrew -- You think that's air you're breathing now? From willysr at slackbuilds.org Sat Jan 24 01:45:49 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 24 Jan 2015 08:45:49 +0700 Subject: [Slackbuilds-users] Updates - 20150124.1 Message-ID: <54C2F94D.60300@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Jan 24 01:28:32 UTC 2015 academic/stellarium: Updated for version 0.13.2. audio/discord: Update script. audio/eyeD3: Updated for version 0.7.5 + new maintainer. audio/sbagen: Added (Binaural Beat Generator). desktop/gtk-kde4: Updated for version 0.9.5b + new maintainer. desktop/gtkhash: Update script. development/Sphinx: Updated for version 1.2.3. development/bats: Added (Bash Automated Testing System). development/bfg: Added (git repo cleaner). development/bmake: Added (port of BSD make). development/ebe: New maintainer. development/erlang-otp: Updated for version 17.4. development/fossil: Updated for version 1.30. development/git-cola: Updated for version 2.1.0. development/jdk: Updated for version 8u31. development/leiningen: Updated for version 2.5.1. development/nose: Updated for version 1.3.4. development/openjdk: Updated for version 7u71b14. development/polyml: Updated for version 5.5.2 + new maintainer. development/regina-rexx: Add documentation. development/sbt: Updated for version 0.13.7. development/setuptools-git: Updated for version 1.1. development/u-boot-tools: Added (Das U-Boot bootloader Companion). development/zope.interface: Updated for version 4.1.2. development/zope.testing: Updated for version 4.1.3. games/garden: Updated for version 1.0.9. games/ioquake3: Updated for version r20140120. games/openmsx-catapult: Updated for version 0.11.0 + new maintainer. games/openmsx: Updated for version 0.11.0 + new maintainer. gis/SFCGAL: Updated for version 1.1.0. gis/Shapely: Updated for version 1.5.5. gis/geoserver-control-flow: Updated for version 2.6.2. gis/geoserver-css: Updated for version 2.6.2. gis/geoserver-oracle: Updated for version 2.6.2. gis/geoserver-pyramid: Updated for version 2.6.2. gis/geoserver-wps: Updated for version 2.6.2. gis/geoserver: Updated for version 2.6.2. gis/grass: Fix build for new freetype. graphics/povray: Fix build on -current. ham/gqrx: Added (software defined radio receiver). ham/rtl-sdr: Fix rtl-sdr.rules installation. libraries/CherryPy: Updated for version 3.6.0. libraries/GitPython: Updated for version 0.3.6. libraries/Jinja2: Updated for version 2.7.3. libraries/SQLObject: Updated for version 2.1.0. libraries/ZConfig: Updated for version 3.0.4. libraries/ZODB3: Updated for version 3.11.0. libraries/botocore: Updated for version 0.84.0. libraries/enca: Updated for version 1.16. libraries/gevent: Updated for version 1.0.1. libraries/gitdb: Updated for version 0.6.4. libraries/greenlet: Updated for version 0.4.5 libraries/http-parser: Updated for version 2.4.1. libraries/libevt: Updated for version 20150105. libraries/libevtx: Updated for version 20150105. libraries/libfwsi: Updated for version 20150105. libraries/liblnk: Updated for version 20150105. libraries/libmsiecf: Updated for version 20150106. libraries/libolecf: Updated for version 20150106. libraries/libqcow: Updated for version 20150105. libraries/libregf: Updated for version 20150105. libraries/libsigscan: Added (libYAL binary signature scanning). libraries/libsmdev: Updated for version 20150105. libraries/libsmraw: Updated for version 20150105. libraries/libsodium: Updated for version 1.0.2. libraries/libvmdk: Updated for version 20150105. libraries/libvorbisidec: Added (Ogg Vorbis 'Tremor' playback codec). libraries/libvshadow: Updated for version 20150106. libraries/libwebsocketpp: Updated for version 0.5.0. libraries/live555: Updated for version 2015.01.19. libraries/smmap: Updated for version 0.9.0. libraries/zdaemon: Updated for version 4.0.1. libraries/zope.component: Updated for version 4.2.1. libraries/zope.configuration: Updated for version 4.0.3. libraries/zope.event: Updated for version 4.0.3. libraries/zope.hookable: Updated for version 4.0.4. libraries/zope.i18nmessageid: Updated for version 4.0.3. libraries/zope.location: Updated for version 4.0.3. libraries/zope.proxy: Updated for version 4.1.4. libraries/zope.schema: Updated for version 4.4.2. libraries/zope.security: Updated for version 4.0.1. misc/drg2sbg: Added (convert I-Doser files to SBaGen scripts). misc/par2cmdline: Updated for version 0.6.11. multimedia/flashplayer-plugin: Updated for version 11.2.202.438. multimedia/gmtp: New maintainer. multimedia/makemkv: Update CFLAGS. network/awscli: Updated for version 1.7.3. network/btsync: Updated for version 1.4.106. network/deis: Updated for version 1.2.2. network/econnman: Added (E17 ConnMan UI). network/flexget: Updated for version 1.2.266. network/iojs: Added (Evented I/O for V8 JavaScript). network/mod_wsgi-metrics: Added (Metrics package for Apache). network/mod_wsgi: Updated for version 4.4.6. network/openntpd: Updated for version 5.7p2. network/snmptt: Added (SNMP Trap Translator). network/sshfp: Added (DNS SSHFP and TLSA/HASTLS records generator). network/yturl: Updated for version 1.17.0. perl/perl-AppConfig: Updated for version 1.67. perl/perl-Cstools: Added (Tools for dealing with Czech texts). perl/perl-IPC-Run3: Updated for version 0.048. perl/perl-Log-Log4perl: Updated for version 1.46. perl/perl-Proc-ProcessTable: Updated for version 0.51. perl/perl-Unicode-Map8: Added (Mapping table). perl/perl-Unicode-Map: Added (Convert String). python/Mako: Updated for version 1.0.0. python/astroid: Updated for version 1.3.4. python/dfvfs: Updated for version 20150117. python/jmespath: Updated for version 0.5.0. python/kaptan: Updated for version 0.5.8. python/path.py: Updated for version 7.1. python/pilkit: Updated for version 1.1.12. python/piprot: Updated for version 0.8.2. python/purl: Updated for version 1.0.3. python/py: Updated for version 1.4.26. python/python-chardet: Updated for version 2.3.0. python/python-ipcalc: Added (IP subnet calculation). python/pytsk: Updated for version 20150111. python/pyzmq: Updated for version 14.5.0. python/regex: Updated for version 2014.12.24. python/requests-futures: Added (Asynchronous Python HTTP). python/requirements-detector: Updated for version 0.3. python/stevedore: Updated for version 1.2.0. system/autoarchive: Updated for version 1.2.0. system/cdw: Updated for version 0.8.0 + new maintainer. system/dar: Updated for version 2.4.16. system/docker: Updated for version 1.4.1. system/inxi: Updated for version 2.2.17. system/mpich: Added (High-Performance Portable MPI). system/postgresql: Fix for pg_upgrade (timezone_abbreviations). system/profile-sync-daemon: Updated for version 5.64. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTC+U0ACgkQiHuDdNczM4GoLQCfbTT7kg1D/Mw2X6TKkkcZOsFm e4AAoKFw3y4AFNustL4AigbulCFrK3dP =p4hD -----END PGP SIGNATURE----- From richard at aaazen.com Sun Jan 25 20:04:19 2015 From: richard at aaazen.com (Richard) Date: Sun, 25 Jan 2015 12:04:19 -0800 (PST) Subject: [Slackbuilds-users] regina-rexx upload fails Message-ID: My attached SlackBuild upload fails with a message saying to post the package here at this forum. http://slackbuilds.org/submit/ Is there a size limit on SlackBuild packages? Some other error? Richard richard at aaazen.com -------------- next part -------------- A non-text attachment was scrubbed... Name: regina-rexx.tar.gz Type: application/octet-stream Size: 1579886 bytes Desc: regina-rexx slackbuild URL: From erik at slackbuilds.org Mon Jan 26 00:16:02 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 25 Jan 2015 18:16:02 -0600 Subject: [Slackbuilds-users] regina-rexx upload fails In-Reply-To: References: Message-ID: <20150125181602.643f95b0@shaggy.doo> On Sun, 25 Jan 2015 12:04:19 -0800 (PST) Richard wrote: > My attached SlackBuild upload fails with a message saying to post the > package here at this forum. > > http://slackbuilds.org/submit/ > > Is there a size limit on SlackBuild packages? > > Some other error? There is a size limit, I'm guessing that was the error. Can you find (or host) direct links for those giant pdf files? -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Jan 26 00:19:52 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 26 Jan 2015 07:19:52 +0700 Subject: [Slackbuilds-users] regina-rexx upload fails In-Reply-To: References: Message-ID: <54C58828.6030602@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > My attached SlackBuild upload fails with a message saying to post > the package here at this forum. > > http://slackbuilds.org/submit/ > > Is there a size limit on SlackBuild packages? > > Some other error? You should not place the sources in the submitted script it will be downloaded manually by the admins/users when testing/using your script - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTFiCgACgkQiHuDdNczM4GRcwCgkqQXDPyZ85jmJINyyc8BcXTj mO4An11Vt+qg63FmWR6rlEH2CfP/WBa/ =CJ00 -----END PGP SIGNATURE----- From richard at aaazen.com Mon Jan 26 01:06:50 2015 From: richard at aaazen.com (Richard) Date: Sun, 25 Jan 2015 17:06:50 -0800 (PST) Subject: [Slackbuilds-users] regina-rexx upload fails In-Reply-To: <20150125181602.643f95b0@shaggy.doo> References: <20150125181602.643f95b0@shaggy.doo> Message-ID: On Sun, 25 Jan 2015, Erik Hanson wrote: > Richard wrote: > > > My attached SlackBuild upload fails with a message saying to post the > > package here at this forum. > > > > http://slackbuilds.org/submit/ > > > > Is there a size limit on SlackBuild packages? > > > > Some other error? > > There is a size limit, I'm guessing that was the error. Can you find (or > host) direct links for those giant pdf files? > Okay, I will leave the current regina-rexx package alone for now as it already has the direct links for the giant pdf files. Please disregard the attached upload file Richard richard at aaazen.com --------------------------------------------------------------------- Baker's First Law of Federal Geometry: A block grant is a solid mass of money surrounded on all sides by governors. From marc at mos6581.de Mon Jan 26 11:30:25 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Mon, 26 Jan 2015 12:30:25 +0100 Subject: [Slackbuilds-users] parallel in pending Message-ID: <54C62551.9060909@mos6581.de> Seems I had a typo when I've searched for parallel on SBo. If Erik won't mind if it gets updated anyway? The version on SBo is quite outdated. -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From richard at aaazen.com Mon Jan 26 18:45:14 2015 From: richard at aaazen.com (Richard) Date: Mon, 26 Jan 2015 10:45:14 -0800 (PST) Subject: [Slackbuilds-users] zarfy SlackBuild installs data into /usr/share not /tmp/SBo/... Message-ID: It was pointed out in a LinuxQuestion forum that the zarfy build ignores the DESTDIR= for the man file and for the image files. http://www.linuxquestions.org/questions/slackware-14/the-myth-of-once-you-go-slack-you-never-go-back-4175531864/page5.html It appears that there are bugs in the Makefile.in and src/Makefile.bin that should be patched in the zarfy.SlackBuild These patches should work: --------------------------------------------------------------- $cat patch-makefile-in --- Makefile.in.orig 2008-09-13 06:05:07.000000000 -0700 +++ Makefile.in 2015-01-26 08:13:00.780325974 -0800 @@ -612,24 +612,24 @@ install-data-local: @$(NORMAL_INSTALL) - $(mkinstalldirs) $(pkgdatadir); \ + $(mkinstalldirs) $(DESTDIR)$(pkgdatadir); \ for fname in data/*; do \ if test -f $$fname; then \ - $(INSTALL_DATA) $$fname $(pkgdatadir); \ + $(INSTALL_DATA) $$fname $(DESTDIR)$(pkgdatadir); \ fi \ done; - $(mkinstalldirs) $(mandir)/man1; \ - $(INSTALL_DATA) man/zarfy.1.gz $(mandir)/man1 + $(mkinstalldirs) $(DESTDIR)$(mandir)/man1; \ + $(INSTALL_DATA) man/zarfy.1.gz $(DESTDIR)$(mandir)/man1 uninstall-local: @$(NORMAL_UNINSTALL) - for fname in $(pkgdatadir)/*; do \ + for fname in $(DESTDIR)$(pkgdatadir)/*; do \ if test -f $$fname; then \ rm $$fname; \ fi \ done; \ - rmdir $(pkgdatadir); \ - rm $(mandir)/man1/zarfy.* + rmdir $(DESTDIR)$(pkgdatadir); \ + rm $(DESTDIR)$(mandir)/man1/zarfy.* # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: ----------------------------------------------------------------------- $cat patch-src-makefile-in --- src/Makefile.in.orig 2008-09-13 06:05:07.000000000 -0700 +++ src/Makefile.in 2015-01-26 08:28:52.276310733 -0800 @@ -200,7 +200,7 @@ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh install-binPROGRAMS: $(bin_PROGRAMS) @$(NORMAL_INSTALL) - test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" + test -z "$(DESTDIR)$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" @list='$(bin_PROGRAMS)'; for p in $$list; do \ p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \ if test -f $$p \ ------------------------------------------------------------------------ Richard Narron richard at aaazen.com P.S. The README still has the word "positioning" misspelled From willysr at slackbuilds.org Mon Jan 26 23:54:38 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 27 Jan 2015 06:54:38 +0700 Subject: [Slackbuilds-users] zarfy SlackBuild installs data into /usr/share not /tmp/SBo/... In-Reply-To: References: Message-ID: <54C6D3BE.8070004@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > It was pointed out in a LinuxQuestion forum that the zarfy build > ignores the DESTDIR= for the man file and for the image files. > > http://www.linuxquestions.org/questions/slackware-14/the-myth-of-once-you-go-slack-you-never-go-back-4175531864/page5.html > > It appears that there are bugs in the Makefile.in and > src/Makefile.bin that should be patched in the zarfy.SlackBuild > > These patches should work: Richard, can you send the patch in form of a file instead of inline? Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTG074ACgkQiHuDdNczM4F/vQCdFPjK+08AKTPUH468m9TrVFBN W+UAnRJWmfI+maFacAR1hue9Mbg+FGyY =V3yT -----END PGP SIGNATURE----- From richard at aaazen.com Tue Jan 27 02:51:30 2015 From: richard at aaazen.com (Richard) Date: Mon, 26 Jan 2015 18:51:30 -0800 (PST) Subject: [Slackbuilds-users] zarfy SlackBuild installs data into /usr/share not /tmp/SBo/... In-Reply-To: <54C6D3BE.8070004@slackbuilds.org> References: <54C6D3BE.8070004@slackbuilds.org> Message-ID: On Tue, 27 Jan 2015, Willy Sudiarto Raharjo wrote: > can you send the patch in form of a file instead of inline? Sure. Richard Narron richard at aaazen.com --------------------------------------------------------------------- Birth, n.: The first and direst of all disasters. -- Ambrose Bierce, "The Devil's Dictionary" -------------- next part -------------- #!/bin/sh # Slackware build script for zarfy # Copyright 2006-2011 Robby Workman, Northport, Alabama, USA # All rights reserved. # # Redistribution and use of this script, with or without modification, is # permitted provided that the following conditions are met: # # 1. Redistributions of this script must retain the above copyright # notice, this list of conditions and the following disclaimer. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. # Maintained by Marc Dix PRGNAM=zarfy VERSION=${VERSION:-0.1.0} BUILD=${BUILD:-3} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) ARCH=i486 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac fi CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" else SLKCFLAGS="-O2" LIBDIRSUFFIX="" fi set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$VERSION.tar.bz2 cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 511 \) \ -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; patch -p0 < $CWD/patch-makefile-in patch -p0 < $CWD/patch-src-makefile-in CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ LDFLAGS="-lm -lX11" \ ./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --libexec=/usr/lib \ --enable-shared=yes \ --enable-static=no \ --enable-debug=no \ --build=$ARCH-slackware-linux make make install DESTDIR=$PKG find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared object" | \ grep ELF | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a \ AUTHORS COPYING ChangeLog INSTALL NEWS README \ $PKG/usr/doc/$PRGNAM-$VERSION cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cd $PKG /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} -------------- next part -------------- --- Makefile.in.orig 2008-09-13 06:05:07.000000000 -0700 +++ Makefile.in 2015-01-26 08:13:00.780325974 -0800 @@ -612,24 +612,24 @@ install-data-local: @$(NORMAL_INSTALL) - $(mkinstalldirs) $(pkgdatadir); \ + $(mkinstalldirs) $(DESTDIR)$(pkgdatadir); \ for fname in data/*; do \ if test -f $$fname; then \ - $(INSTALL_DATA) $$fname $(pkgdatadir); \ + $(INSTALL_DATA) $$fname $(DESTDIR)$(pkgdatadir); \ fi \ done; - $(mkinstalldirs) $(mandir)/man1; \ - $(INSTALL_DATA) man/zarfy.1.gz $(mandir)/man1 + $(mkinstalldirs) $(DESTDIR)$(mandir)/man1; \ + $(INSTALL_DATA) man/zarfy.1.gz $(DESTDIR)$(mandir)/man1 uninstall-local: @$(NORMAL_UNINSTALL) - for fname in $(pkgdatadir)/*; do \ + for fname in $(DESTDIR)$(pkgdatadir)/*; do \ if test -f $$fname; then \ rm $$fname; \ fi \ done; \ - rmdir $(pkgdatadir); \ - rm $(mandir)/man1/zarfy.* + rmdir $(DESTDIR)$(pkgdatadir); \ + rm $(DESTDIR)$(mandir)/man1/zarfy.* # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: -------------- next part -------------- --- src/Makefile.in.orig 2008-09-13 06:05:07.000000000 -0700 +++ src/Makefile.in 2015-01-26 08:28:52.276310733 -0800 @@ -200,7 +200,7 @@ cd $(top_builddir) && $(MAKE) $(AM_MAKEFLAGS) am--refresh install-binPROGRAMS: $(bin_PROGRAMS) @$(NORMAL_INSTALL) - test -z "$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" + test -z "$(DESTDIR)$(bindir)" || $(MKDIR_P) "$(DESTDIR)$(bindir)" @list='$(bin_PROGRAMS)'; for p in $$list; do \ p1=`echo $$p|sed 's/$(EXEEXT)$$//'`; \ if test -f $$p \ -------------- next part -------------- zarfy is a gui to libxrandr. It presents the user with a visual representaion of active displays on an interactive map of the screen memory. It features free positioning, configuration saving, scripting for R&R, and an alternate gui for switching monitors. From miguel at thedeanda.com Tue Jan 27 08:24:30 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 27 Jan 2015 00:24:30 -0800 Subject: [Slackbuilds-users] Some issues with Apache Tomcat In-Reply-To: References: Message-ID: I remember running into similar issues with jboss/wildfly about a year ago where the maintainer moved folders around and created a neat little web of symlinks. The problems is that while its generally good practice to put configuration in /etc, pids in /var/run, logs in /var/log, etc. it can sometimes be problematic for for software not written this way. Java applications like jetty, tomcat, wildfly, jboss, solr, etc. are much easier to maintain and run when they are just left as is. I've resolved to not using slackbuilds for any java programs and install I manually extract and run as my user account. (The only exception is apache-ant, that works well) It might be worth playing around with /etc/profile.d/ and adding a tomcat.* set for those variables. It might help with eclipse issues. -m On Mon, Jan 19, 2015 at 4:50 PM, Antonio Hern?ndez Blas < hba.nihilismus at gmail.com> wrote: > Hi, i'm trying to understand how it is integrated Apache Tomcat into > Slackware using the available SlackBuild at SBo. > > First some facts: > > * $CATALINA_HOME and $CATALINA_BASE are **global** environment variables. > * $CATALINA_HOME is set to /usr/share/tomcat > * $CATALINA_BASE is set to /var/lib/tomcat > * Inside $CATALINA_HOME: > * bin/ > * lib/ > * Inside $CATALINA_BASE: > * bin -> /usr/share/tomcat/bin/ > * conf -> /etc/tomcat/ > * logs -> /var/log/tomcat/ > * temp -> /var/tmp/tomcat/ > * webapps/ > * work -> /var/run/tomcat/ > * /etc/rc.d/rc.tomcat has hardcoded values for $PIDFILE, $LOGFILE and > $USER, and expects the environment variable $CATALINA_BASE has been already > defined (which it is since it is a **global** environment variable). > > Now the questions/issues: > > * Trying to integrate $CATALINA_BASE into Eclipse does not work, i get > the message: > > "Unknown version of Tomcat was specified." > > And from Netbeans i get: > > "The specified Server Location (Catalina Home) folder is not valid." > > This is because there is not a lib directory inside $CATALINA_BASE so > to fix it one must execute (as root): > > # ln -s $CATALINA_HOME/lib $CATALINA_BASE/ > > Trying to integrate $CATALINA_HOME neither, i get the error message > from Eclipse: > > "Could not load the Tomcat server configuration at /Servers/Tomcat v7.0 > Server at localhost-config. The configuration may be corrupt or incomplete." > > And from Netbeans: > > "The /conf/server.xml can't be read." > > To fix it one must execute (as root): > > # ln -s /etc/tomcat/ $CATALINA_HOME/conf > > * Once i try to execute Apache Tomcat with Netbeans i get the error: > > "Starting of Tomcat failed, check whether the > /usr/share/tomcat/bin/catalina.sh and related scripts are executable" > > To fix it execute (as root): > > # chmod +x $CATALINA_HOME/bin/*.sh > > So finally some questions: > > * Why the distinction between $CATALINA_HOME and $CATALINA_BASE?. As i > understand this is just when you want to have multiple instances of Apache > Tomcat, each one sharing some directories from $CATALINA_HOME while keeping > their own configuration/libraries [1] [2] [3] [4] separated. Actually, this > is what Eclipse/Netbean does, it ask you for $CATALINA_HOME and create a > $CATALINA_BASE directory to manage it execution ("Create a local server"). > > IMHO there should not be $CATALINA_BASE **globally**, but **locally** > (/etc/rc.d/rc.tomcat maybe). > > But remember that /etc/rc.d/rc.tomcat has hardcoded values for > $PIDFILE, $LOGFILE and $USER to work with $CATALINA_BASE so i am not sure > this is the case for multiple instances. Anyway these environment variable > would be uniques to each instance of tomcat (if this is the case) so a > better place to define them would be $CATALINA_BASE/conf/tomcat-java.conf, > which brings the next question. > > * Why the configuration files are keep in /etc/tomcat?. Is this some kind > of "HIER or die!"? ;-) > > * And finally, why the $CATALINA_HOME/bin/*.sh files are keep with 0744 > as permission? It is for some kind of security?. > > I hope to make clear my questions and not generate more ;-) > > - Cheers > > [1] http://tomcat.apache.org/tomcat-7.0-doc/RUNNING.txt > [2] http://java.dzone.com/articles/running-multiple-tomcat > [3] > http://www.ramkitech.com/2011/07/running-multiple-tomcat-instances-on.html > [4] > http://blogs.vmware.com/vfabric/2012/10/5-scenarios-and-best-practices-for-running-multiple-instances-of-tomcat-or-tc-server.html > > -- > Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. > https://github.com/nihilismus | https://bitbucket.org/nihilismus | > https://twitter.com/nihilipster > > _______________________________________________ > 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 erik at slackbuilds.org Tue Jan 27 15:28:50 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 27 Jan 2015 09:28:50 -0600 Subject: [Slackbuilds-users] parallel in pending In-Reply-To: <54C62551.9060909@mos6581.de> References: <54C62551.9060909@mos6581.de> Message-ID: <20150127092850.095e44bd@shaggy.doo> On Mon, 26 Jan 2015 12:30:25 +0100 Marcel Saegebarth wrote: > Seems I had a typo when I've searched for parallel on SBo. > If Erik won't mind if it gets updated anyway? The version on SBo > is quite outdated. You can take over maintenance if you like, I haven't used it in a long time. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From marc at mos6581.de Tue Jan 27 15:47:23 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Tue, 27 Jan 2015 16:47:23 +0100 Subject: [Slackbuilds-users] parallel in pending In-Reply-To: <20150127092850.095e44bd@shaggy.doo> References: <54C62551.9060909@mos6581.de> <20150127092850.095e44bd@shaggy.doo> Message-ID: <54C7B30B.1070008@mos6581.de> Thanks Erik. I'll take it. -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D On 01/27/2015 04:28 PM, Erik Hanson wrote: > On Mon, 26 Jan 2015 12:30:25 +0100 > Marcel Saegebarth wrote: > >> Seems I had a typo when I've searched for parallel on SBo. >> If Erik won't mind if it gets updated anyway? The version on SBo >> is quite outdated. > > You can take over maintenance if you like, I haven't used it in a long time. > > > > > _______________________________________________ > 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From marc at mos6581.de Thu Jan 29 14:30:49 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Thu, 29 Jan 2015 15:30:49 +0100 Subject: [Slackbuilds-users] git-cola Message-ID: <54CA4419.6030008@mos6581.de> git-cola should try to extract the archive also by tar xvf $CWD/v$VERSION.tar.gz Actually it just tries to extract an archive with full name and fails. -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Jan 29 17:22:15 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 30 Jan 2015 00:22:15 +0700 Subject: [Slackbuilds-users] git-cola In-Reply-To: <54CA4419.6030008@mos6581.de> References: <54CA4419.6030008@mos6581.de> Message-ID: <54CA6C47.2050606@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > git-cola should try to extract the archive also by > > tar xvf $CWD/v$VERSION.tar.gz > > Actually it just tries to extract an archive with full name and > fails. Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTKbEcACgkQiHuDdNczM4HpCwCfTqdr4+kJdanMtUJV9NXBAbWR 03MAoKRlOlxMPonbyR48PPlAhKbZGj0/ =Y2UP -----END PGP SIGNATURE----- From hba.nihilismus at gmail.com Fri Jan 30 05:28:01 2015 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Thu, 29 Jan 2015 23:28:01 -0600 Subject: [Slackbuilds-users] warsow's URL is returning 404 Message-ID: Working URLs: http://update.warsow.net/mirror/warsow_1.51_unified.tar.gz http://downloads.sourceforge.net/warsow.mirror/Warsow%201.51/warsow_1.51_unified.tar.gz - Cheers -- Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Jan 30 10:56:43 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 30 Jan 2015 17:56:43 +0700 Subject: [Slackbuilds-users] warsow's URL is returning 404 In-Reply-To: References: Message-ID: <54CB636B.4000202@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Working URLs: > > http://update.warsow.net/mirror/warsow_1.51_unified.tar.gz > > http://downloads.sourceforge.net/warsow.mirror/Warsow%201.51/warsow_1.51_unified.tar.gz Fixed > in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTLY2sACgkQiHuDdNczM4EJSgCfUDk9+pv8RDGmwx6fn3koyN3i IyUAoKeIIDB43+GNMm3Td0gC0Nike/7t =PWle -----END PGP SIGNATURE----- From jbernts at broadpark.no Fri Jan 30 16:36:01 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Fri, 30 Jan 2015 17:36:01 +0100 Subject: [Slackbuilds-users] Ledger update? In-Reply-To: <54242304.8070303@slackbuilds.org> References: <20140925135158.GE1677@jostein> <54242304.8070303@slackbuilds.org> Message-ID: <20150130163601.GA2086@jostein> On 25.09.14,21:13, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > The very useful ledger application is in a pretty old version on > > Slackbuild.org. The Slackbuild version of ledger is at 2.6.3 while > > the most recent version is at v.3.0.3 with many new features and > > bug fixes. Should this get an update? > > > > Ledger 3.0.3-20140608, the command-line accounting tool > > i think the maintainer never maintain this package anymore > he added this on 2011 and never update since > > if you are interested, try to contact the maintainer and if he's no > longer maintaining or reply, just submit a new version and take over > the maintenance > > > - -- > Willy Sudiarto Raharjo I have agreed with the maintainer L.Young previously that I could take over this. I have now uploaded a new ledger v.3.1 SlackBuild to the pending queue. (Have also uploaded the most recent versions of task and notmuch). Jostein From willysr at slackbuilds.org Fri Jan 30 16:49:20 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 30 Jan 2015 23:49:20 +0700 Subject: [Slackbuilds-users] Ledger update? In-Reply-To: <20150130163601.GA2086@jostein> References: <20140925135158.GE1677@jostein> <54242304.8070303@slackbuilds.org> <20150130163601.GA2086@jostein> Message-ID: <54CBB610.60709@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I have agreed with the maintainer L.Young previously that I could > take over this. I have now uploaded a new ledger v.3.1 SlackBuild > to the pending queue. (Have also uploaded the most recent versions > of task and notmuch). The one in our repo is already at 3.1 and it was updated by simotrone earlier this month and he is the current maintainer. You will need to ask his permission - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTLthAACgkQiHuDdNczM4FLgACdEvYGhEgDA8FxTK6MvfXanTy9 5DkAnjEPsMqV08Wf+xhJxe+1agznj2BD =xnoo -----END PGP SIGNATURE----- From jbernts at broadpark.no Fri Jan 30 17:00:12 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Fri, 30 Jan 2015 18:00:12 +0100 Subject: [Slackbuilds-users] Ledger update? In-Reply-To: <54CBB610.60709@slackbuilds.org> References: <20140925135158.GE1677@jostein> <54242304.8070303@slackbuilds.org> <20150130163601.GA2086@jostein> <54CBB610.60709@slackbuilds.org> Message-ID: <20150130170011.GB2086@jostein> On 30.01.15,23:49, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I have agreed with the maintainer L.Young previously that I could > > take over this. I have now uploaded a new ledger v.3.1 SlackBuild > > to the pending queue. (Have also uploaded the most recent versions > > of task and notmuch). > > The one in our repo is already at 3.1 and it was updated by simotrone > earlier this month and he is the current maintainer. > > You will need to ask his permission > OK, this escaped me. Will cancel my upload then. :) Jostein From zhu.qunying at gmail.com Fri Jan 30 18:40:27 2015 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 30 Jan 2015 10:40:27 -0800 Subject: [Slackbuilds-users] screenfetch could not build Message-ID: The latest screenfetch could not build. Found screenFetch-3.6.5.tar.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for screenFetch-3.6.5.tar.gz ... OK Building package for screenfetch... tar: /var/lib/sbopkg/SBo/14.1/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now tar: /var/lib/sbopkg/SBo/14.1/desktop/screenfetch/v3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now The reason is that the archive file name is screenFetch-3.6.5.tar.gz, but script is looking for screenfetch-3.6.5.tar.gz and failed. -- Qun-Ying From bocke at mycity.rs Fri Jan 30 19:09:13 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Fri, 30 Jan 2015 20:09:13 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: Message-ID: <20150130200913.6c4019b6@artwo.universe.uni> Hi. Did you change the script by hand? The archive name is different from the one in the current SBo script: > Found screenFetch-3.6.5.tar.gz in /var/cache/sbopkg. This also looks suspicious: > The reason is that the archive file name is screenFetch-3.6.5.tar.gz, > but script is looking for screenfetch-3.6.5.tar.gz and failed. If you did, 3.6.5 is already available on SBo. Just update your local SBo repo (sbopkg -r). Anyway, I did a quick build test. Better sure than sorry. Everything is ok on my end. Bojan (the maintainer). From zhu.qunying at gmail.com Fri Jan 30 20:56:25 2015 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 30 Jan 2015 12:56:25 -0800 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150130200913.6c4019b6@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> Message-ID: OK, I found the reason. I set wget to have "--content-disposition" on by default, which causing downloaded file to be named as screenFetch-3.6.5.tar.gz with the download link in the info file. On Fri, Jan 30, 2015 at 11:09 AM, Bojan Popovic wrote: > Hi. > > Did you change the script by hand? The archive name is different from > the one in the current SBo script: > >> Found screenFetch-3.6.5.tar.gz in /var/cache/sbopkg. > > This also looks suspicious: >> The reason is that the archive file name is screenFetch-3.6.5.tar.gz, >> but script is looking for screenfetch-3.6.5.tar.gz and failed. > > If you did, 3.6.5 is already available on SBo. Just update your local > SBo repo (sbopkg -r). > > Anyway, I did a quick build test. Better sure than sorry. Everything is > ok on my end. > > Bojan (the maintainer). > > > > > > _______________________________________________ > 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/ > -- Qun-Ying From bocke at mycity.rs Fri Jan 30 22:31:06 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Fri, 30 Jan 2015 23:31:06 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> Message-ID: <20150130233106.3d600783@artwo.universe.uni> Interesting. I will look at that the next upload. I have never used that option before. I will need to RTFM on it. Thanx for reporting. Bojan. On Fri, 30 Jan 2015 12:56:25 -0800 Qun-Ying wrote: > OK, I found the reason. I set wget to have "--content-disposition" on > by default, which causing downloaded file to be named as > screenFetch-3.6.5.tar.gz with the download link in the info file. > From willysr at slackbuilds.org Sat Jan 31 00:12:01 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 31 Jan 2015 07:12:01 +0700 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> Message-ID: <54CC1DD1.5000802@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > OK, I found the reason. I set wget to have "--content-disposition" > on by default, which causing downloaded file to be named as > screenFetch-3.6.5.tar.gz with the download link in the info file. I tried to recreate your situation with --content-disposition and it still works willysr at SBo64:~/slackbuilds/desktop/screenfetch$ wget - --content-disposition $DOWNLOAD - --2015-01-31 07:09:37-- https://github.com/KittyKatt/screenFetch/archive/v3.6.5.tar.gz Resolving github.com (github.com)... 192.30.252.129 Connecting to github.com (github.com)|192.30.252.129|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 [following] - --2015-01-31 07:09:38-- https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 Resolving codeload.github.com (codeload.github.com)... 192.30.252.145 Connecting to codeload.github.com (codeload.github.com)|192.30.252.145|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 54153 (53K) [application/x-gzip] Saving to: ?screenFetch-3.6.5.tar.gz? 100%[===================================================================================================================>] 54,153 84.8KB/s in 0.6s 2015-01-31 07:09:40 (84.8 KB/s) - ?screenFetch-3.6.5.tar.gz? saved [54153/54153] willysr at SBo64:~/slackbuilds/desktop/screenfetch$ su Password: root at SBo64:/home/willysr/slackbuilds/desktop/screenfetch$ sh screenfetch.SlackBuild tar: /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now screenFetch-3.6.5/ screenFetch-3.6.5/CHANGELOG screenFetch-3.6.5/COPYING screenFetch-3.6.5/README.mkdn screenFetch-3.6.5/TODO screenFetch-3.6.5/screenfetch-dev screenFetch-3.6.5/screenfetch.1 Slackware package maker, version 3.14159. Searching for symbolic links: No symbolic links were found, so we won't make an installation script. You can make your own later in ./install/doinst.sh and rebuild the package if you like. This next step is optional - you can set the directories in your package to some sane permissions. If any of the directories in your package have special permissions, then DO NOT reset them here! Would you like to reset all directory permissions to 755 (drwxr-xr-x) and directory ownerships to root.root ([y]es, [n]o)? n Creating Slackware package: /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz ./ install/ install/slack-desc usr/ usr/bin/ usr/bin/screenfetch usr/doc/ usr/doc/screenfetch-3.6.5/ usr/doc/screenfetch-3.6.5/TODO usr/doc/screenfetch-3.6.5/CHANGELOG usr/doc/screenfetch-3.6.5/README.mkdn usr/doc/screenfetch-3.6.5/COPYING Slackware package /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz created. - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTMHdEACgkQiHuDdNczM4EGewCfURlcFqXRB5Bwf2wcoBj523d1 c/IAoJW1HHyohQZ5fWq7GjOuNkYTqEnN =BT3z -----END PGP SIGNATURE----- From zhu.qunying at gmail.com Sat Jan 31 00:45:30 2015 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 30 Jan 2015 16:45:30 -0800 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <54CC1DD1.5000802@slackbuilds.org> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> Message-ID: It is a mysteryy why it works on your box, as you also got the error: root at SBo64:/home/willysr/ slackbuilds/desktop/screenfetch$ sh screenfetch.SlackBuild tar: /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: Cannot open: No such file or directory tar: Error is not recoverable: exiting now On Fri, Jan 30, 2015 at 4:12 PM, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> OK, I found the reason. I set wget to have "--content-disposition" >> on by default, which causing downloaded file to be named as >> screenFetch-3.6.5.tar.gz with the download link in the info file. > > I tried to recreate your situation with --content-disposition and it > still works > > willysr at SBo64:~/slackbuilds/desktop/screenfetch$ wget > - --content-disposition $DOWNLOAD > - --2015-01-31 07:09:37-- > https://github.com/KittyKatt/screenFetch/archive/v3.6.5.tar.gz > Resolving github.com (github.com)... 192.30.252.129 > Connecting to github.com (github.com)|192.30.252.129|:443... connected. > HTTP request sent, awaiting response... 302 Found > Location: > https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 > [following] > - --2015-01-31 07:09:38-- > https://codeload.github.com/KittyKatt/screenFetch/tar.gz/v3.6.5 > Resolving codeload.github.com (codeload.github.com)... 192.30.252.145 > Connecting to codeload.github.com > (codeload.github.com)|192.30.252.145|:443... connected. > HTTP request sent, awaiting response... 200 OK > Length: 54153 (53K) [application/x-gzip] > Saving to: ?screenFetch-3.6.5.tar.gz? > > 100%[===================================================================================================================>] > 54,153 84.8KB/s in 0.6s > > 2015-01-31 07:09:40 (84.8 KB/s) - ?screenFetch-3.6.5.tar.gz? saved > [54153/54153] > > willysr at SBo64:~/slackbuilds/desktop/screenfetch$ su > Password: > root at SBo64:/home/willysr/slackbuilds/desktop/screenfetch$ sh > screenfetch.SlackBuild > tar: > /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: > Cannot > open: No such file or directory > tar: Error is not recoverable: exiting now > screenFetch-3.6.5/ > screenFetch-3.6.5/CHANGELOG > screenFetch-3.6.5/COPYING > screenFetch-3.6.5/README.mkdn > screenFetch-3.6.5/TODO > screenFetch-3.6.5/screenfetch-dev > screenFetch-3.6.5/screenfetch.1 > > Slackware package maker, version 3.14159. > > Searching for symbolic links: > > No symbolic links were found, so we won't make an installation script. > You can make your own later in ./install/doinst.sh and rebuild the > package if you like. > > This next step is optional - you can set the directories in your package > to some sane permissions. If any of the directories in your package have > special permissions, then DO NOT reset them here! > > Would you like to reset all directory permissions to 755 (drwxr-xr-x) and > directory ownerships to root.root ([y]es, [n]o)? n > > Creating Slackware package: /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz > > ./ > install/ > install/slack-desc > usr/ > usr/bin/ > usr/bin/screenfetch > usr/doc/ > usr/doc/screenfetch-3.6.5/ > usr/doc/screenfetch-3.6.5/TODO > usr/doc/screenfetch-3.6.5/CHANGELOG > usr/doc/screenfetch-3.6.5/README.mkdn > usr/doc/screenfetch-3.6.5/COPYING > > Slackware package /tmp/screenfetch-3.6.5-noarch-1_SBo.tgz created. > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlTMHdEACgkQiHuDdNczM4EGewCfURlcFqXRB5Bwf2wcoBj523d1 > c/IAoJW1HHyohQZ5fWq7GjOuNkYTqEnN > =BT3z > -----END PGP SIGNATURE----- > _______________________________________________ > 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/ > -- Qun-Ying From zhu.qunying at gmail.com Sat Jan 31 00:52:38 2015 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 30 Jan 2015 16:52:38 -0800 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> Message-ID: Please take a look at the script: http://slackbuilds.org/cgit/slackbuilds/tree/desktop/screenfetch/screenfetch.SlackBuild?h=willysr At line 53: tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/v$VERSION.tar.gz It will not match the download filename, and hence the script should exit. -- Qun-Ying From bocke at mycity.rs Sat Jan 31 00:44:11 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 01:44:11 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> Message-ID: <20150131014411.47910d7f@artwo.universe.uni> You can safely ignore that. The script containts something like: tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/v$VERSION.tar.gz This is to allow packaging from both classical tarballs (screenfetch-3.6.5.tar.gz) and github tarballs (v3.6.5.tar.gz). This can be redirected to /dev/null. There might be reason why I didn't but can't remember right now as that error message is harmless. Or maybe it was just an ommision. I will fix that in the next update. If Willy didn't have any problems, I guess the problem is on your end. Bojan. On Fri, 30 Jan 2015 16:45:30 -0800 Qun-Ying wrote: > It is a mysteryy why it works on your box, as you also got the error: > > root at SBo64:/home/willysr/ > slackbuilds/desktop/screenfetch$ sh > screenfetch.SlackBuild > tar: > /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: > Cannot > open: No such file or directory > tar: Error is not recoverable: exiting now > From bocke at mycity.rs Sat Jan 31 00:46:34 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 01:46:34 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> Message-ID: <20150131014634.5d4e2d7e@artwo.universe.uni> Well, it should match. Github tarballs have a form of the second one. The first one is the old source tarball name format. So, in any case, problem seem to be on your end. Bojan. On Fri, 30 Jan 2015 16:52:38 -0800 Qun-Ying wrote: > Please take a look at the script: > http://slackbuilds.org/cgit/slackbuilds/tree/desktop/screenfetch/screenfetch.SlackBuild?h=willysr > At line 53: > tar xvf $CWD/$PRGNAM-$VERSION.tar.gz || tar xvf $CWD/v$VERSION.tar.gz > > It will not match the download filename, and hence the script should > exit. > From baildon.research at googlemail.com Sat Jan 31 01:04:11 2015 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 31 Jan 2015 01:04:11 +0000 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131014634.5d4e2d7e@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <20150131014634.5d4e2d7e@artwo.universe.uni> Message-ID: Hey people, Look carefully. Qun-Ying is getting screenFetch-3.6.5.tar.gz with an upper case F ... not screenfetch with a lower case F. And so am I. So the PRGNAM 'screenfetch' is not matched. So Qun-Ying is getting an error. And so am I. I don't know why it worked for you, Willy. Maybe the name has recently changed at Github? Best regards -D. From zhu.qunying at gmail.com Sat Jan 31 01:04:43 2015 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 30 Jan 2015 17:04:43 -0800 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131014634.5d4e2d7e@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <20150131014634.5d4e2d7e@artwo.universe.uni> Message-ID: When using the "--content-disposition" with wget, it will be the same effect as you download the file from a browser. When you download it from a browser, it will save the file as "screenFetch-3.6.5.tar.gz", that is how GitHub setup its download link. Wget by default only use the last part of the url as save filename, it maynot be the intended file name by web server. On Fri, Jan 30, 2015 at 4:46 PM, Bojan Popovic wrote: > Well, it should match. Github tarballs have a form of the second one. > The first one is the old source tarball name format. So, in any case, > problem seem to be on your end. > > Bojan. > -- Qun-Ying From willysr at slackbuilds.org Sat Jan 31 01:05:59 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 31 Jan 2015 08:05:59 +0700 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> Message-ID: <54CC2A77.4080206@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > It is a mysteryy why it works on your box, as you also got the > error: > > root at SBo64:/home/willysr/ slackbuilds/desktop/screenfetch$ sh > screenfetch.SlackBuild tar: > /home/willysr/slackbuilds/desktop/screenfetch/screenfetch-3.6.5.tar.gz: > > Cannot > open: No such file or directory tar: Error is not recoverable: > exiting now ah you are right i already have the other source inside the slackbuilds directory i have pushed a fix for this in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTMKncACgkQiHuDdNczM4GOUgCgmL99aKs9c+fjHS1vN7qVPRSA gJAAn0SHd9Rywy/1rfj5TcHWy/tqH5oJ =2Awi -----END PGP SIGNATURE----- From bocke at mycity.rs Sat Jan 31 00:57:43 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 01:57:43 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> Message-ID: <20150131015743.5bce6cd4@artwo.universe.uni> Anyway if you don't solve the problem, there is an easy manual solution. Screenfetch is simply a shell script. Just download it, make it executable and put in your path. You can get the latest git version here: http://git.silverirc.com/cgit.cgi/screenfetch.git/plain/screenfetch-dev Cheers, Bojan. From bocke at mycity.rs Sat Jan 31 01:00:00 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 02:00:00 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131015743.5bce6cd4@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <20150131015743.5bce6cd4@artwo.universe.uni> Message-ID: <20150131020000.6f071f42@artwo.universe.uni> Sorry, that's an older version. The current one is on GitHub: https://raw.githubusercontent.com/KittyKatt/screenFetch/master/screenfetch-dev Bojan. On Sat, 31 Jan 2015 01:57:43 +0100 Bojan Popovic wrote: > Anyway if you don't solve the problem, there is an easy manual > solution. Screenfetch is simply a shell script. Just download it, make > it executable and put in your path. > > You can get the latest git version here: > http://git.silverirc.com/cgit.cgi/screenfetch.git/plain/screenfetch-dev > > Cheers, > > Bojan. From zhu.qunying at gmail.com Sat Jan 31 01:18:45 2015 From: zhu.qunying at gmail.com (Qun-Ying) Date: Fri, 30 Jan 2015 17:18:45 -0800 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131020000.6f071f42@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <20150131015743.5bce6cd4@artwo.universe.uni> <20150131020000.6f071f42@artwo.universe.uni> Message-ID: Thanks, I already have it built by modifying the build script. My point was to bring attention to you and get the script updated, so that other people have that wget option set will not encounter the same error as me. From willysr at slackbuilds.org Sat Jan 31 01:56:53 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 31 Jan 2015 08:56:53 +0700 Subject: [Slackbuilds-users] Updates - 20150131.1 Message-ID: <54CC3665.6060003@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Jan 31 01:33:43 UTC 2015 accessibility/wgetpaste: Change default pastebin. audio/darkice: Cleanup against SBo templates audio/icecast: Cleanup against SBo templates audio/jack2: Set copyright year until 2015 audio/qjackctl: Set copyright year until 2015 audio/sidplayfp: Cleanup against SBo templates audio/sunvox: Updated for version 1.8.1. audio/xwax: copyright year + cleanup desktop/alltray: copyright year + cleanup desktop/insync-thunar: Fix slack-desc. desktop/screenfetch: Add source alternative. desktop/spectrwm: Updated for version 2.6.2. development/THE: Added missing documents. development/astyle: Updated for version 2.05.1 + new maintainer. development/ebe: Updated for version 2.7.1. development/enki: Added (a text editor for programmers). development/git-cola: Add source alternative from github. development/mutagen: Updated for version 1.27. development/openjdk: Remove unneeded patch. development/pcc: Updated for version 1.1.0. development/sbt: Fix VERSION. development/textadept: Added (a minimalist text editor). development/thunderpad: Added (a simple, powerful text editor). development/vstudio: Updated for version 5.7.1. games/mednafen: Switched build from gcc to clang to fix test errors. games/megaglest: Updated for version 3.11.0. games/pokerth: copyright year + cleanup games/qtsixa: copyright year + cleanup games/voxelands: Updated for version 1501.00. games/warsow: Update DOWNLOAD url. games/wesnoth: Updated for version 1.12.1. graphics/converseen: Updated for version 0.8.6. libraries/libgit2: Updated for version 0.21.5. libraries/libgsasl: Fixed VERSION + copyright year + cleanup libraries/libpar2: copyright year + cleanup libraries/libsidplay2: copyright year + cleanup libraries/libsidplayfp: Updated for version 1.7.0. libraries/live555: Updated for version 2015.01.27. libraries/ltm: Update HOMEPAGE and DOWNLOAD. libraries/qutepart: Added (core editor component). misc/dvtm: copyright year + cleanup multimedia/exaile: Updated for version 3.4.3 + new maintainer. multimedia/flashplayer-plugin: Updated for version 11.2.202.440. multimedia/gmtp: Updated for version 1.3.9. multimedia/makemkv: Updated for version 1.9.1. multimedia/mpv: Updated for version 0.7.3. multimedia/plex-home-theater: copyright year + cleanup network/cgterm: copyright year + cleanup + added homepage network/copy: Updated for version 1.48.0456 & Qt fixes. network/dillo: Updated for version 3.0.4.1. network/fwknop: Updated for version 2.6.5. network/insync: Fix slack-desc. network/iojs: Updated for version 1.0.4. network/mod_fcgid: Fixed VERSION + copyright year + cleanup network/nzbget: copyright year + cleanup network/openntpd: Updated for version 5.7p3. network/proxychains: copyright year + cleanup network/pydio-sync: copyright year + cleanup network/sshuttle: copyright year + cleanup network/synergy: Set copyright year until 2015 network/teamviewer: Updated for version 10.0.37742. network/weechat: Updated for version 1.1.1. office/libreoffice-helppack: Updated for version 4.4.0. office/libreoffice-langpack: Updated for version 4.4.0. office/libreoffice: Updated for version 4.4.0. office/notmuch: Updated for version 0.19. office/task: Updated for version 2.4.0. perl/perl-CPANPLUS-Dist-Slackware: Updated for version 1.021. perl/perl-Proc-Daemon: Updated for version 0.17. perl/perl-Statistics-Descriptive: Updated for version 3.0608. perl/perl-config-general: Fix slack-desc. python/cryptography: Updated for version 0.7.2. python/python-ipcalc: Added python 3 support. python/s3cmd: Updated for version 1.5.0. system/asbt: Updated for version 1.2. system/cbmfs: Fixed VERSION, eMail. + copyright year + cleanup system/fs-uae-arcade: Updated for version 2.4.3. system/fs-uae-launcher: Updated for version 2.4.3. system/fs-uae: Updated for version 2.4.3. system/mongodb: Updated for version 2.6.7. system/monitorix: copyright year + cleanup system/parallel: Updated for version 20150122 + new maintainer. system/profile-cleaner: Added (SQLite vacuuming and re-indexing). system/profile-sync-daemon: Updated for version 5.65. system/wmconfig: Updated for version 1.4.9. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTMNmUACgkQiHuDdNczM4ELTgCgiBGaOOyLZbkb+mrEiuHKEEhW iMoAoIcUQgh4O6ghEXygOt//WQUx0cL3 =jcIF -----END PGP SIGNATURE----- From duncan_roe at acslink.net.au Sat Jan 31 08:45:36 2015 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Sat, 31 Jan 2015 19:45:36 +1100 Subject: [Slackbuilds-users] Unable to submit updates: mx4.partnerconsole.net rejects my email address Message-ID: <20150131084536.GA2690@dimstar.local.net> Hi, There are new versions of libnftnl and nft, but when I tried to submit the new Slackbuilds, I got the message: duncan_roe at acslink.net.au was rejected by mx4.partnerconsole.net. Go back and enter a valid E-Mail address. duncan_roe at acslink.net.au *is* my email address! Can someone fix mx4 please? Cheers ... Duncan. -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html From rob0 at slackbuilds.org Sat Jan 31 10:25:36 2015 From: rob0 at slackbuilds.org (Rob McGee) Date: Sat, 31 Jan 2015 04:25:36 -0600 Subject: [Slackbuilds-users] Unable to submit updates: mx4.partnerconsole.net rejects my email address In-Reply-To: <20150131084536.GA2690@dimstar.local.net> References: <20150131084536.GA2690@dimstar.local.net> Message-ID: <20150131102536.GY23739@harrier.slackbuilds.org> On Sat, Jan 31, 2015 at 07:45:36PM +1100, Duncan Roe wrote: > There are new versions of libnftnl and nft, but when I tried to > submit the new Slackbuilds, I got the message: > > duncan_roe at acslink.net.au was rejected by mx4.partnerconsole.net. > Go back and enter a valid E-Mail address. > > duncan_roe at acslink.net.au *is* my email address! Can someone fix > mx4 please? We can't. You will have to ask your email provider. The http://slackbuilds.org/submit/ form is telling you what it encountered while trying to verify your address. This problem is often caused by things like greylisting. In that case, you can usually succeed by trying again in 5 minutes or so. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From bocke at mycity.rs Sat Jan 31 11:09:32 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 12:09:32 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <54CC2A77.4080206@slackbuilds.org> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> Message-ID: <20150131120932.3d56a4c5@artwo.universe.uni> Ok, thanx. But I need to ask you a tiny favor. I try to keep a small changelog on the top of the script. Could you add the line about the change. And increase the version in the comments to 1.5. This is the current log: # ChangeLog # 1.0 23-DEC-2012 Added # 1.1 08-JUL-2013 Updated to a new upstream ver. 3.0.5. Fixes Slack64 # detection. # 1.2 06-DEC-2013 Updated to a new upstream ver. 3.2.2. # 1.3 24-JUL-2014 Updated to a new upstream ver. 3.5.0. # 1.4 07-DEC-2014 Updated to a new upstream ver. 3.6.5 Just add the following line: # 1.5 31-JAN-2015 Added a source alternative (willysr) Bojan. On Sat, 31 Jan 2015 08:05:59 +0700 Willy Sudiarto Raharjo wrote: > ah you are right > i already have the other source inside the slackbuilds directory > i have pushed a fix for this in my branch > > Thanks From bocke at mycity.rs Sat Jan 31 11:28:30 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 12:28:30 +0100 Subject: [Slackbuilds-users] rawstudio & lensfun In-Reply-To: References: Message-ID: <20150131122830.0de6a08e@artwo.universe.uni> Hi. Sorry to resurrect the thread. I recently successfully built rawstudio against the latest lensfun. The common solution is to delete all instances of LF_MODIFY_CCI which is depreciated in the newer versions. But, even with that, the current stable version is too old and has a very limited support for cameras lagging a few years. Lens correction won't work with a bunch of cameras anyway. Although there is a new version in the git repo which is regulary updated (and supports newer cameras). This version unfortunately depends on some Gnome stuff (a geo locating library with Gnome deps) so I wasn't able to try it. You can find it here: https://github.com/rawstudio/rawstudio if you wish to try building it. Please share your experiences with the mailing list if you do. :) For now, Darktable works very well for me. So I probably won't experiment with Rawstudio in a close future. But I would be interested in reading any further discussion on the matter. Cheers, Bojan. On Sun, 2 Nov 2014 12:00:39 -0500 B Watson wrote: > On 11/2/14, andy vaselaar wrote: > > > So the way I see it, either rawstudio needs to be updated (which > > hasn't happened in years), or we have to setup our slackbuild to > > require an older version of lensfun. > > One way to do it would be to have the rawstudio SlackBuild script > compile its own older (preferably statically linked) private copy of > lensfun, then link rawstudio with that. > > I had to do this with irssi_otr, when the libotr on SBo got > upgraded and irssi_otr needed the older version. If you look at > network/irssi_otr/irssi_otr.SlackBuild, you can see how it's done. > > Another, much simpler thing to try: look for distro patches for > rawstudio, e.g. from Debian, Gentoo, Fedora, perhaps one of them has > patched rawstudio so it can be built against the newer lensfun. > _______________________________________________ > 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 Sat Jan 31 12:33:24 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 31 Jan 2015 19:33:24 +0700 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131120932.3d56a4c5@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> Message-ID: <54CCCB94.1060004@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > But I need to ask you a tiny favor. I try to keep a small changelog > on the top of the script. Could you add the line about the change. > And increase the version in the comments to 1.5. > > This is the current log: # ChangeLog # 1.0 23-DEC-2012 Added # 1.1 > 08-JUL-2013 Updated to a new upstream ver. 3.0.5. Fixes Slack64 # > detection. # 1.2 06-DEC-2013 Updated to a new upstream ver. > 3.2.2. # 1.3 24-JUL-2014 Updated to a new upstream ver. 3.5.0. # > 1.4 07-DEC-2014 Updated to a new upstream ver. 3.6.5 > > Just add the following line: # 1.5 31-JAN-2015 Added a source > alternative (willysr) It's kinda too late for that as i have pushed public update this morning you might want to add that in your next update in the future - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTMy5QACgkQiHuDdNczM4Fn2gCfUNnt8DhaIGYOk7aPkcoM/q0Q bt4AnA1mmr6KifNEE+pqnjXb/uWPAULf =FCzL -----END PGP SIGNATURE----- From bocke at mycity.rs Sat Jan 31 12:35:58 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 13:35:58 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <54CCCB94.1060004@slackbuilds.org> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> <54CCCB94.1060004@slackbuilds.org> Message-ID: <20150131133558.73e9b9f9@artwo.universe.uni> I don't think it's really late. I can make the change too, but I'll have to go through the upload form on the site. As the end result is the same, might be better if you do it. :) If you're hesistant, never mind. I'll just make the change myself and upload it later today. Just seems like extra work both me and you (someone needs to check the contents of the uploaded tarball). Bojan. On Sat, 31 Jan 2015 19:33:24 +0700 Willy Sudiarto Raharjo wrote: > It's kinda too late for that as i have pushed public update this > morning you might want to add that in your next update in the future > From markus.ka.rinne at gmail.com Sat Jan 31 13:39:40 2015 From: markus.ka.rinne at gmail.com (Markus Rinne) Date: Sat, 31 Jan 2015 15:39:40 +0200 Subject: [Slackbuilds-users] [PATCH] network/openresolv: Fix resolv script permissions Message-ID: <20150131133940.GA10401@tursas.sidaroth.foo> The script /etc/openvpn/update-resolv-conf needs to have execute permissions. Otherwise it cannot be run. This kind of error message is printed in /var/log/messages: Jan 31 14:58:56 markusri_laptop openvpn[5647]: Options error: --up script fails with /etc/openvpn/update-resolv-conf: Permission denied --- network/openresolv/openresolv.SlackBuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/network/openresolv/openresolv.SlackBuild b/network/openresolv/openresolv.SlackBuild index d153f15..dfee84f 100644 --- a/network/openresolv/openresolv.SlackBuild +++ b/network/openresolv/openresolv.SlackBuild @@ -45,7 +45,7 @@ if [ "${OPENVPN:-no}" = "no" ]; then USE_OPENVPN="" else if [ -d /etc/openvpn ]; then - USE_OPENVPN="cp $CWD/update-resolv-conf $PKG/etc/openvpn/" + USE_OPENVPN="install -m 755 $CWD/update-resolv-conf $PKG/etc/openvpn/" else echo "You must to have openvpn installed" exit 1 -- 1.8.4 From duncan_roe at acslink.net.au Sat Jan 31 13:49:43 2015 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Sun, 1 Feb 2015 00:49:43 +1100 Subject: [Slackbuilds-users] Unable to submit updates: mx4.partnerconsole.net rejects my email address In-Reply-To: <20150131102536.GY23739@harrier.slackbuilds.org> References: <20150131084536.GA2690@dimstar.local.net> <20150131102536.GY23739@harrier.slackbuilds.org> Message-ID: <20150131134942.GA6244@dimstar.local.net> On Sat, Jan 31, 2015 at 04:25:36AM -0600, Rob McGee wrote: > On Sat, Jan 31, 2015 at 07:45:36PM +1100, Duncan Roe wrote: > > There are new versions of libnftnl and nft, but when I tried to > > submit the new Slackbuilds, I got the message: > > > > duncan_roe at acslink.net.au was rejected by mx4.partnerconsole.net. > > Go back and enter a valid E-Mail address. > > > > duncan_roe at acslink.net.au *is* my email address! Can someone fix > > mx4 please? > > We can't. You will have to ask your email provider. The > http://slackbuilds.org/submit/ form is telling you what it > encountered while trying to verify your address. > > This problem is often caused by things like greylisting. In that > case, you can usually succeed by trying again in 5 minutes or so. Thanks for the suggestion - they did indeed work when I tried again, Cheers ... Duncan. From mario at slackware.hr Sat Jan 31 13:51:28 2015 From: mario at slackware.hr (Mario Preksavec) Date: Sat, 31 Jan 2015 14:51:28 +0100 Subject: [Slackbuilds-users] cmake-template.SlackBuild Message-ID: <54CCDDE0.60704@slackware.hr> While working on the new SlackBuild, I've noticed files ending up in strange places, adding these fixed it: -DCMAKE_INSTALL_SYSCONFDIR=/etc \ -DCMAKE_INSTALL_LOCALSTATEDIR=/var \ -DCMAKE_INSTALL_MANDIR=/usr/man \ -DCMAKE_INSTALL_DOCDIR=/usr/doc/$PRGNAM-$VERSION \ Unless if there is an issue having such defaults, they should probably get added to match autotools-template... Regards, -- Mario From erik at slackbuilds.org Sat Jan 31 15:19:19 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 31 Jan 2015 09:19:19 -0600 Subject: [Slackbuilds-users] cmake-template.SlackBuild In-Reply-To: <54CCDDE0.60704@slackware.hr> References: <54CCDDE0.60704@slackware.hr> Message-ID: <20150131091919.67f877b4@shaggy.doo> On Sat, 31 Jan 2015 14:51:28 +0100 Mario Preksavec wrote: > Unless if there is an issue having such defaults, they should probably > get added to match autotools-template... There is seemingly no standard for cmake flags, so they are often different from project to project. This is already addressed by the comments in the cmake template. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From mario at slackware.hr Sat Jan 31 16:03:06 2015 From: mario at slackware.hr (Mario Preksavec) Date: Sat, 31 Jan 2015 17:03:06 +0100 Subject: [Slackbuilds-users] cmake-template.SlackBuild In-Reply-To: <20150131091919.67f877b4@shaggy.doo> References: <54CCDDE0.60704@slackware.hr> <20150131091919.67f877b4@shaggy.doo> Message-ID: <54CCFCBA.1000505@slackware.hr> On 01/31/2015 04:19 PM, Erik Hanson wrote: > There is seemingly no standard for cmake flags, so they are often > different from project to project. This is already addressed by the > comments in the cmake template. Sure, but how does this argument not apply to configure parameters in autotools-template then as well? -- Mario From willysr at slackbuilds.org Sat Jan 31 16:51:05 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 31 Jan 2015 23:51:05 +0700 Subject: [Slackbuilds-users] [PATCH] network/openresolv: Fix resolv script permissions In-Reply-To: <20150131133940.GA10401@tursas.sidaroth.foo> References: <20150131133940.GA10401@tursas.sidaroth.foo> Message-ID: <54CD07F9.4020109@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The script /etc/openvpn/update-resolv-conf needs to have execute > permissions. Otherwise it cannot be run. This kind of error > message is printed in /var/log/messages: > > Jan 31 14:58:56 markusri_laptop openvpn[5647]: Options error: --up > script fails with /etc/openvpn/update-resolv-conf: Permission > denied --- network/openresolv/openresolv.SlackBuild | 2 +- 1 file > changed, 1 insertion(+), 1 deletion(-) > > diff --git a/network/openresolv/openresolv.SlackBuild > b/network/openresolv/openresolv.SlackBuild index d153f15..dfee84f > 100644 --- a/network/openresolv/openresolv.SlackBuild +++ > b/network/openresolv/openresolv.SlackBuild @@ -45,7 +45,7 @@ if [ > "${OPENVPN:-no}" = "no" ]; then USE_OPENVPN="" else if [ -d > /etc/openvpn ]; then - USE_OPENVPN="cp $CWD/update-resolv-conf > $PKG/etc/openvpn/" + USE_OPENVPN="install -m 755 > $CWD/update-resolv-conf $PKG/etc/openvpn/" else echo "You must to > have openvpn installed" exit 1 > Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTNB/kACgkQiHuDdNczM4F8jQCgppZqc81fl9GcUF60daDAT48l E4oAnAyz7QtkBmqFrdw3dVnz/MRR3iib =+TJS -----END PGP SIGNATURE----- From erik at slackbuilds.org Sat Jan 31 17:22:44 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 31 Jan 2015 11:22:44 -0600 Subject: [Slackbuilds-users] cmake-template.SlackBuild In-Reply-To: <54CCFCBA.1000505@slackware.hr> References: <54CCDDE0.60704@slackware.hr> <20150131091919.67f877b4@shaggy.doo> <54CCFCBA.1000505@slackware.hr> Message-ID: <20150131112244.2f43cf33@shaggy.doo> On Sat, 31 Jan 2015 17:03:06 +0100 Mario Preksavec wrote: > On 01/31/2015 04:19 PM, Erik Hanson wrote: > > There is seemingly no standard for cmake flags, so they are often > > different from project to project. This is already addressed by the > > comments in the cmake template. > > Sure, but how does this argument not apply to configure parameters in > autotools-template then as well? I'm not sure what you mean, the autotools template has a similar comment. The example flags there are much more standard though. Different cmake flags come in all the time. ~2 weeks ago we could have changed the template to these: http://slackbuilds.org/cgit/slackbuilds/commit/?id=b448f592dc4668 There are plenty of examples in the repo of why no set of cmake flags will be definitive. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From miguel at thedeanda.com Sat Jan 31 17:31:00 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Sat, 31 Jan 2015 09:31:00 -0800 Subject: [Slackbuilds-users] atom build failure Message-ID: i'm building from current with multilib but it only claims node is needed. any ideas? virtualbox has been crashing my system lately so its hard to test from non-current and non-multilib. thanks. ../node_modules/nan/nan.h: In function 'void NanContextDisposedNotification()': ../node_modules/nan/nan.h:222:5: error: 'ContextDisposedNotification' is not a member of 'v8::V8' v8::V8::ContextDisposedNotification(); ^ make: *** [Release/obj.target/spellchecker/src/main.o] Error 1 gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/mnt/sdb1/sbopkg/tmp/atom-0.138.0/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23) gyp ERR! stack at ChildProcess.emit (events.js:98:17) gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:810:12) gyp ERR! System Linux 3.14.29 gyp ERR! command "node" "/mnt/sdb1/sbopkg/tmp/atom-0.138.0/apm/node_modules/atom-package-manager/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild" gyp ERR! cwd /mnt/sdb1/sbopkg/tmp/atom-0.138.0/node_modules/spell-check/node_modules/spellchecker gyp ERR! node -v v0.10.32 gyp ERR! node-gyp -v v0.12.2 gyp ERR! not ok npm ERR! spellchecker at 1.1.0 install: `node-gyp rebuild` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the spellchecker at 1.1.0 install script. npm ERR! This is most likely a problem with the spellchecker package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp rebuild npm ERR! You can get their info via: npm ERR! npm owner ls spellchecker npm ERR! There is likely additional logging output above. npm ERR! System Linux 3.14.29 npm ERR! command "/mnt/sdb1/sbopkg/tmp/atom-0.138.0/apm/node_modules/atom-package-manager/bin/node" "/mnt/sdb1/sbopkg/tmp/atom-0.138.0/apm/node_modules/atom-package-manager/node_modules/npm/bin/npm-cli.js" "--globalconfig" "/mnt/sdb1/sbopkg/tmp/atom-0.138.0/apm/node_modules/atom-package-manager/.apmrc" "--userconfig" "/root/.atom/.apmrc" "install" "/mnt/sdb1/tmp/d-115031-17975-11cvpze/package.tgz" "--target=0.18.0" "--arch=x64" "--quiet" npm ERR! cwd /mnt/sdb1/sbopkg/tmp/atom-0.138.0 npm ERR! node -v v0.10.32 npm ERR! npm -v 1.4.4 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /mnt/sdb1/sbopkg/tmp/atom-0.138.0/npm-debug.log npm ERR! not ok code 0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bocke at mycity.rs Sat Jan 31 17:23:29 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 18:23:29 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <54CCCB94.1060004@slackbuilds.org> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> <54CCCB94.1060004@slackbuilds.org> Message-ID: <20150131182329.07bf7927@artwo.universe.uni> Hi. Just uploaded the updated tarball. Small changes: updated changelog according to git history log and reduced verbosity of tarball extraction. Btw, please do document your changes in the future so I am aware of updates. This time I went through the full git history and documented all the changes. Bojan. On Sat, 31 Jan 2015 19:33:24 +0700 Willy Sudiarto Raharjo wrote: > > It's kinda too late for that as i have pushed public update this > morning you might want to add that in your next update in the future > From ryan.q at linux.com Sat Jan 31 18:35:14 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 31 Jan 2015 18:35:14 +0000 Subject: [Slackbuilds-users] screenfetch could not build References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> <54CCCB94.1060004@slackbuilds.org> <20150131182329.07bf7927@artwo.universe.uni> Message-ID: On Sat, Jan 31, 2015, 9:35 AM Bojan Popovic wrote: Hi. Just uploaded the updated tarball. Small changes: updated changelog according to git history log and reduced verbosity of tarball extraction. Btw, please do document your changes in the future so I am aware of updates. This time I went through the full git history and documented all the changes. Every maintainer is different, but we already have git commit messages for tracking changes to the build. To me an additional changelog seems like overkill. Bojan. On Sat, 31 Jan 2015 19:33:24 +0700 Willy Sudiarto Raharjo wrote: > > It's kinda too late for that as i have pushed public update this > morning you might want to add that in your next update in the future > _______________________________________________ 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 bocke at mycity.rs Sat Jan 31 19:38:41 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 20:38:41 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> <54CCCB94.1060004@slackbuilds.org> <20150131182329.07bf7927@artwo.universe.uni> Message-ID: <20150131203841.2f712ea8@artwo.universe.uni> I don't agree. When SBo admins make changes whithout informing the maintainer, it's often not really obvious that changes are made to the code. Even if you notice, you can't be sure of a kind of changes that were made without looking at the log. And why would you look at the log if you are sure that no changes are made by the information you currently have. It's much easier to state the changes somewhere obvious then searching through the logs after every SBo update. I ask for them to document it when they change things whithout my knowledge (or as it happened several times before whithout asking) so I am aware of that when making future changes to the scripts. That's not much. And it's polite thing to do. Bojan. From t3slider at gmail.com Sat Jan 31 20:05:27 2015 From: t3slider at gmail.com (T3slider) Date: Sat, 31 Jan 2015 15:05:27 -0500 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131203841.2f712ea8@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> <54CCCB94.1060004@slackbuilds.org> <20150131182329.07bf7927@artwo.universe.uni> <20150131203841.2f712ea8@artwo.universe.uni> Message-ID: <20150131200527.GA3172@MyPC.phub.net.cable.rogers.com> On Sat, Jan 31, 2015 at 08:38:41PM +0100, Bojan Popovic wrote: > It's much easier to state the changes somewhere obvious then searching > through the logs after every SBo update. > > I ask for them to document it when they change things whithout my > knowledge (or as it happened several times before whithout asking) so I > am aware of that when making future changes to the scripts. That's not > much. And it's polite thing to do. I think the burden on admins is high enough and Willy has been doing an amazing job at keeping the pending queue empty. Contacting a maintainer after modifying anything would take too much effort and documenting any changes in the script inflates it for no reason (the git log already does this quite well). I personally maintain a local git repo for any SlackBuilds I maintain, and before making any changes for future submission I just download the SlackBuild's tarball from SBo and diff the files to see upstream changes. This takes under a minute for the maintainer and lets the admins continue on as they have been without any additional effort. I really don't see a problem with things as they are... From bocke at mycity.rs Sat Jan 31 20:07:48 2015 From: bocke at mycity.rs (Bojan Popovic) Date: Sat, 31 Jan 2015 21:07:48 +0100 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131200527.GA3172@MyPC.phub.net.cable.rogers.com> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> <54CCCB94.1060004@slackbuilds.org> <20150131182329.07bf7927@artwo.universe.uni> <20150131203841.2f712ea8@artwo.universe.uni> <20150131200527.GA3172@MyPC.phub.net.cable.rogers.com> Message-ID: <20150131210748.3daef1ea@artwo.universe.uni> Hi. I've never implied anything like that. I'm just asking for admin to leave trace in tte changelog if it exists embedded in the SlackBuild itself. If someone can fix the version in the script I guess he can, at the same expense, write 4 or 5 words which state that he changed it. That takes several seconds. Bojan. On Sat, 31 Jan 2015 15:05:27 -0500 T3slider wrote: > > I think the burden on admins is high enough and Willy has been doing > an amazing job at keeping the pending queue empty. Contacting a > maintainer after modifying anything would take too much effort and > documenting any changes in the script inflates it for no reason (the > git log already does this quite well).