From duwath at gmail.com Tue Sep 3 10:26:51 2013 From: duwath at gmail.com (Matteo Paoluzzi) Date: Tue, 03 Sep 2013 12:26:51 +0200 Subject: [Slackbuilds-users] Suggestion for nvidia-driver page Message-ID: <5225B96B.9060701@gmail.com> Using sbopkg for nvidia-driver installation in my new Slackware64, I found out that it failed extracting some missing archives. Those archives are listed in nvidia-driver's slackbuild page, but only under x86 architecture, thus preventing sbopkg from downloading them. This is not only a sbopkg issue, because those archives are needed by the slackbuild also on the x86_64 architecture, not only on x86, and looking at the page as is at moment, it seems that those archives are not needed under X86_64, which is wrong. My suggestion is to list the .tar.bz2 archives ALSO under "Source Download (64bit)" section. From artourter at gmail.com Tue Sep 3 10:54:56 2013 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 3 Sep 2013 11:54:56 +0100 Subject: [Slackbuilds-users] Suggestion for nvidia-driver page In-Reply-To: <5225B96B.9060701@gmail.com> References: <5225B96B.9060701@gmail.com> Message-ID: This has already been discussed and is fixed in the ready tree. we are just waiting for the next release now. As a side note to this, the current version of the non legacy package does not work on current as the kernel is not supported. upgrading to 325.15 solves that problem. Cheers Greg . On 3 September 2013 11:26, Matteo Paoluzzi wrote: > Using sbopkg for nvidia-driver installation in my new Slackware64, I > found out that it failed extracting some missing archives. Those > archives are listed in nvidia-driver's slackbuild page, but only under > x86 architecture, thus preventing sbopkg from downloading them. > > This is not only a sbopkg issue, because those archives are needed by > the slackbuild also on the x86_64 architecture, not only on x86, and > looking at the page as is at moment, it seems that those archives are > not needed under X86_64, which is wrong. > > My suggestion is to list the .tar.bz2 archives ALSO under "Source > Download (64bit)" section. > _______________________________________________ > 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 nickblizzard1776 at gmail.com Tue Sep 3 12:22:55 2013 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Tue, 3 Sep 2013 08:22:55 -0400 Subject: [Slackbuilds-users] Suggestion for nvidia-driver page In-Reply-To: References: <5225B96B.9060701@gmail.com> Message-ID: as a note to the note, a newer driver was released that also supports the 3.10 kernel used in -current: ftp://download.nvidia.com/XFree86/Linux-x86/319.49/ (Yea, I know, 319 < 325... but it really is a newer driver and is working well with -current) On Tue, Sep 3, 2013 at 6:54 AM, Greg' Ar Tourter wrote: > This has already been discussed and is fixed in the ready tree. we are > just waiting for the next release now. > > As a side note to this, the current version of the non legacy package does > not work on current as the kernel is not supported. upgrading to 325.15 > solves that problem. > > Cheers > > Greg > . > > > On 3 September 2013 11:26, Matteo Paoluzzi wrote: > >> Using sbopkg for nvidia-driver installation in my new Slackware64, I >> found out that it failed extracting some missing archives. Those >> archives are listed in nvidia-driver's slackbuild page, but only under >> x86 architecture, thus preventing sbopkg from downloading them. >> >> This is not only a sbopkg issue, because those archives are needed by >> the slackbuild also on the x86_64 architecture, not only on x86, and >> looking at the page as is at moment, it seems that those archives are >> not needed under X86_64, which is wrong. >> >> My suggestion is to list the .tar.bz2 archives ALSO under "Source >> Download (64bit)" section. >> _______________________________________________ >> 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 adis at linux.org.ba Tue Sep 3 15:04:15 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Tue, 3 Sep 2013 17:04:15 +0200 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions Message-ID: Guys, I have a question for all PostgreSQL users and SBo admins. Would it be OK for the next PostgreSQL package (upcoming 9.3) to be version specific and parallel-installable with old PostgreSQL versions. (of course, we would continue that practice in the future). Since PostgreSQL installations are not upgradeable in place, one needs to do export/import data cycle or use pg_upgrade utility, and having old and new database instance would be very handy for that. The packages would be named postgresql93 (v9.3.x), postgresql94 (v9.4.x) (the current postgresql can be treated as postgresql92), and would use version specific data directories. Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Tue Sep 3 15:23:38 2013 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 3 Sep 2013 16:23:38 +0100 Subject: [Slackbuilds-users] Suggestion for nvidia-driver page In-Reply-To: References: <5225B96B.9060701@gmail.com> Message-ID: Indeed 3.19.49 is probably a better bet (it wasn't available when I started using current). The 325.xx series is more a development branch (aka "shortlived" in Nvidia's terms). I personally have had no issues with the 325.xx branch on either 14.0 and current but ultimately, it is up to the package maintainer to choose which one he'd rather use. On 3 September 2013 13:22, Nick Blizzard wrote: > as a note to the note, a newer driver was released that also supports the > 3.10 kernel used in -current: > > ftp://download.nvidia.com/XFree86/Linux-x86/319.49/ > > (Yea, I know, 319 < 325... but it really is a newer driver and is working > well with -current) > > > On Tue, Sep 3, 2013 at 6:54 AM, Greg' Ar Tourter wrote: > >> This has already been discussed and is fixed in the ready tree. we are >> just waiting for the next release now. >> >> As a side note to this, the current version of the non legacy package >> does not work on current as the kernel is not supported. upgrading to >> 325.15 solves that problem. >> >> Cheers >> >> Greg >> . >> >> >> On 3 September 2013 11:26, Matteo Paoluzzi wrote: >> >>> Using sbopkg for nvidia-driver installation in my new Slackware64, I >>> found out that it failed extracting some missing archives. Those >>> archives are listed in nvidia-driver's slackbuild page, but only under >>> x86 architecture, thus preventing sbopkg from downloading them. >>> >>> This is not only a sbopkg issue, because those archives are needed by >>> the slackbuild also on the x86_64 architecture, not only on x86, and >>> looking at the page as is at moment, it seems that those archives are >>> not needed under X86_64, which is wrong. >>> >>> My suggestion is to list the .tar.bz2 archives ALSO under "Source >>> Download (64bit)" section. >>> _______________________________________________ >>> 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 audrius at neutrino.lt Tue Sep 3 18:10:51 2013 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Tue, 3 Sep 2013 21:10:51 +0300 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: Message-ID: <20130903181051.GA2236@varna> On Tue, 2013-09-03 at 17:04:15 +0200, Adis Nezirovic wrote: > Guys, I have a question for all PostgreSQL users and SBo admins. > > Would it be OK for the next PostgreSQL package (upcoming 9.3) to be version > specific and parallel-installable with old PostgreSQL versions. > (of course, we would continue that practice in the future). > > Since PostgreSQL installations are not upgradeable in place, one needs to > do export/import data cycle or use pg_upgrade utility, and having old and > new database instance would be very handy for that. > > The packages would be named postgresql93 (v9.3.x), postgresql94 (v9.4.x) > (the current postgresql can be treated as postgresql92), and would use > version specific data directories. Sounds like a very nice improvement. It would also benefit those of us, who want to run different PostgreSQL versions in parallel. I say go for it. Just one question: in case of new major release, what would happen to SlackBuild for the old one? Would it be removed from SBo? PostgreSQL community maintains 4 to 5 versions at the same time, but I guess this would be too much for a single SBo maintainer. Not that I need this (I'm already grateful for the current PostgreSQL SlackBuild), just something to think about. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Tue Sep 3 21:44:18 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 03 Sep 2013 14:44:18 -0700 Subject: [Slackbuilds-users] Suggestion for nvidia-driver page In-Reply-To: References: <5225B96B.9060701@gmail.com> Message-ID: <52265832.5040501@gmail.com> On 09/03/2013 08:23 AM, Greg' Ar Tourter wrote: > Indeed 3.19.49 is probably a better bet (it wasn't available when I > started using current). The 325.xx series is more a development branch > (aka "shortlived" in Nvidia's terms). I personally have had no issues > with the 325.xx branch on either 14.0 and current but ultimately, it is > up to the package maintainer to choose which one he'd rather use. > > > > On 3 September 2013 13:22, Nick Blizzard > wrote: > > as a note to the note, a newer driver was released that also > supports the 3.10 kernel used in -current: > > ftp://download.nvidia.com/XFree86/Linux-x86/319.49/ > > (Yea, I know, 319 < 325... but it really is a newer driver and is > working well with -current) > > > On Tue, Sep 3, 2013 at 6:54 AM, Greg' Ar Tourter > > wrote: > > This has already been discussed and is fixed in the ready tree. > we are just waiting for the next release now. > > As a side note to this, the current version of the non legacy > package does not work on current as the kernel is not supported. > upgrading to 325.15 solves that problem. > > Cheers > > Greg Just an FYI. I will only maintain the "Long Lived Branch" since that's a bit less work given I also need to track several legacy versions. Also, being a bit busy these days, I haven't been tracking -current for 14.0 package compatibility. Thanks Ed From bosth at alumni.sfu.ca Wed Sep 4 03:03:00 2013 From: bosth at alumni.sfu.ca (Benjamin Trigona-Harany) Date: Tue, 03 Sep 2013 20:03 -0700 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: Message-ID: <9667337.cYin8o9fAa@jerseybastion> On September 3, 2013 17:04:15 Adis Nezirovic wrote: > Guys, I have a question for all PostgreSQL users and SBo admins. > > Would it be OK for the next PostgreSQL package (upcoming 9.3) to be version > specific and parallel-installable with old PostgreSQL versions. > (of course, we would continue that practice in the future). > > Since PostgreSQL installations are not upgradeable in place, one needs to > do export/import data cycle or use pg_upgrade utility, and having old and > new database instance would be very handy for that. > > The packages would be named postgresql93 (v9.3.x), postgresql94 (v9.4.x) > (the current postgresql can be treated as postgresql92), and would use > version specific data directories. This is timely because a similar issue just came up with the 2.2 release of PostGIS, which also expects both the current 2.2 and the previous 2.1 versions installed to do an in-place upgrade of existing databases. However, providing both postgis21 and postgis22 SlackBuilds would mean some headaches for packages depending on PostGIS since it wouldn't be evident which version of PostGIS it was built against without also versioning that build script. Likewise, splitting PostgreSQL into version-dependent scripts is going to affect dependencies. Other distros have ended up with packages such as postgres91-postgis21-2.1.0, but I don't see that being maintainable, especially when we consider the further SlackBuilds that will depend on that package. Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part. URL: From joshuakwood at gmail.com Wed Sep 4 03:12:39 2013 From: joshuakwood at gmail.com (JK Wood) Date: Tue, 3 Sep 2013 22:12:39 -0500 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: <9667337.cYin8o9fAa@jerseybastion> References: <9667337.cYin8o9fAa@jerseybastion> Message-ID: On Sep 3, 2013 10:03 PM, "Benjamin Trigona-Harany" wrote: > > On September 3, 2013 17:04:15 Adis Nezirovic wrote: > > Guys, I have a question for all PostgreSQL users and SBo admins. > > > > Would it be OK for the next PostgreSQL package (upcoming 9.3) to be version > > specific and parallel-installable with old PostgreSQL versions. > > (of course, we would continue that practice in the future). > > > > Since PostgreSQL installations are not upgradeable in place, one needs to > > do export/import data cycle or use pg_upgrade utility, and having old and > > new database instance would be very handy for that. > > > > The packages would be named postgresql93 (v9.3.x), postgresql94 (v9.4.x) > > (the current postgresql can be treated as postgresql92), and would use > > version specific data directories. > > This is timely because a similar issue just came up with the 2.2 release of > PostGIS, which also expects both the current 2.2 and the previous 2.1 versions > installed to do an in-place upgrade of existing databases. > > However, providing both postgis21 and postgis22 SlackBuilds would mean some > headaches for packages depending on PostGIS since it wouldn't be evident which > version of PostGIS it was built against without also versioning that build > script. > > Likewise, splitting PostgreSQL into version-dependent scripts is going to > affect dependencies. Other distros have ended up with packages such as > postgres91-postgis21-2.1.0, but I don't see that being maintainable, > especially when we consider the further SlackBuilds that will depend on that > package. > > Ben > _______________________________________________ > 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/ > > Speaking as someone who works with databases professionally, if you don't have a way of maintaining an upgrade path you have bigger problems. Speaking as someone who maintains a few packages, having two differing packages won't solve the problem, which is overwriting the tools when you install the new package. It really sounds to me like an upgrade script which takes care of the necessary steps for an upgrade would be infinitely preferable, and should be done in addition to the current SlackBuild. --JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From adis at linux.org.ba Wed Sep 4 07:35:00 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Wed, 4 Sep 2013 09:35:00 +0200 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <9667337.cYin8o9fAa@jerseybastion> Message-ID: Well, maybe we can install binaries (or everythng) for PostgreSQL package into version specific directory (/usr/lib/postgresql/9.3)? It even doesn't need to be separate package, my intention is just to enable people to install new Postgresql version, transfer data, and remove old version if they want to. For example: 1) I would prepare new PostgreSQL 9.2 build with binaries in version specific directories and symlinks in /usr/bin (so functionally we have the same situation as with current package) rc.postgresql script will be modified to honour environment variable PG_VERSION, so we can start "other" PostgreSQL versions 2) User installs this PostgreSQL 9.2 package 3) New PostgreSQL 9.3 package is released, we can install it over the old version, it only overwrites shared symlinks in bin directory. At this point old version can be (re)started using: PG_VERSION=9.2 /etc/rc.d/rc.postgresql 4) User configures PostgreSQL 9.3 data dir, TCP ports in configurations etc. 5) User has option to upgrade/transfer data and test new PostgreSQL version 6) User can remove old PostgreSQL 9.2 package and its data directory (or keep it) As for third party software, we can continue as before, just target the latest major PostgreSQL version. I'll try to email maintainers of all packages with postgres tag before new major PostgreSQL version, so we can have our cake and eat it too. Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: From bosth at alumni.sfu.ca Wed Sep 4 15:00:12 2013 From: bosth at alumni.sfu.ca (Benjamin Trigona-Harany) Date: Wed, 04 Sep 2013 08:00:12 -0700 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: Message-ID: <6322767.2jBnRc8byD@jerseybastion> On September 4, 2013 09:35:00 Adis Nezirovic wrote: > Well, maybe we can install binaries (or everythng) for PostgreSQL package > into version specific directory (/usr/lib/postgresql/9.3)? > > It even doesn't need to be separate package, my intention is just to enable > people to install new Postgresql version, transfer data, and remove old > version if they want to. > > For example: > > 1) I would prepare new PostgreSQL 9.2 build with binaries in version > specific directories and symlinks in /usr/bin > (so functionally we have the same situation as with current package) > rc.postgresql script will be modified to honour environment variable > PG_VERSION, so we can start "other" PostgreSQL versions > > 2) User installs this PostgreSQL 9.2 package > > 3) New PostgreSQL 9.3 package is released, we can install it over the old > version, it only overwrites shared symlinks in bin directory. At this point > old version can be (re)started using: PG_VERSION=9.2 > /etc/rc.d/rc.postgresql > > 4) User configures PostgreSQL 9.3 data dir, TCP ports in configurations etc. > > 5) User has option to upgrade/transfer data and test new PostgreSQL version > > 6) User can remove old PostgreSQL 9.2 package and its data directory (or > keep it) This is similar to the upgrade procedure I had worked out for a single-package PostGIS: 1) installpkg postgis-2.1-*.tgz 2) perform upgrade (ALTER EXTENSION postgis UPDATE TO "2.1.0") for all affected databases 3) removepkg postgis-2.0 This works because it is only /usr/lib/postgresql/postgis-2.0.so that Postgres needs from the old package, and this will not be overwritten by installing the new package. I much prefer this to version-specific scripts for extensions. > As for third party software, we can continue as before, just target the > latest major PostgreSQL version. I'll try to email maintainers of all > packages with postgres tag before new major PostgreSQL version, so we can > have our cake and eat it too. That would be welcome. Thanks, Ben -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: This is a digitally signed message part. URL: From leva at ecentrum.hu Mon Sep 9 10:22:22 2013 From: leva at ecentrum.hu (LEVAI Daniel) Date: Mon, 9 Sep 2013 12:22:22 +0200 Subject: [Slackbuilds-users] perl-* slackbuild updates Message-ID: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> Hi! I'm working on a slackbuild for the WWW-Google-Contacts perl module and the long line of its dependencies required some updates to other perl modules. I've made updated slackbuilds and mailed the diffs to the corresponding maintainers, but all of them timed out. It would be great to see these get updated, so what now? The modules in question: Crypt-SSLeay Net-SSLeay perl-Class-Load perl-Dist-CheckConflicts perl-IO-Socket-INET6 perl-IO-Socket-SSL perl-List-MoreUtils perl-Module-Runtime perl-Package-DeprecationManager perl-Package-Stash perl-Sub-Exporter And the people involved with them: David Somero manuel.reimer [at] gmx.de Marco Bonetti Also, if someone knows something about or can get in touch with them, please guide them to this issue. Thanks, Daniel -- L?VAI D?niel PGP key ID = 0x83B63A8F Key fingerprint = DBEC C66B A47A DFA2 792D 650C C69B BE4C 83B6 3A8F From Bradley at NorthTech.US Mon Sep 9 23:19:41 2013 From: Bradley at NorthTech.US (Bradley D. Thornton) Date: Mon, 09 Sep 2013 16:19:41 -0700 Subject: [Slackbuilds-users] perl-* slackbuild updates In-Reply-To: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> References: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> Message-ID: <522E578D.7090604@NorthTech.US> -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 On 09/09/2013 03:22 AM, LEVAI Daniel wrote: > Hi! > > I'm working on a slackbuild for the WWW-Google-Contacts perl module and > the long line of its dependencies required some updates to other perl > modules. I've made updated slackbuilds and mailed the diffs to the > corresponding maintainers, but all of them timed out. > It would be great to see these get updated, so what now? > > The modules in question: > Crypt-SSLeay > Net-SSLeay > perl-Class-Load > perl-Dist-CheckConflicts > perl-IO-Socket-INET6 I know this is a bit off-topic, but I've been wanting to ask this for a long time, and this list is probably the place where I'll get the best answers, from the people who have the perspectives that matter to me the most in this regard. I often have problems when meeting Perl dependencies using SlackBuilds, sometimes they bomb, but more often than not, the list of deps needed are simply incomplete, prompting me to just use the cpan shell to install and maintain those modules. What are the advantages of using SBo's over that of cpan, for the management and installation of Perl modules, and why might I choose one method over the other? Again, I'm asking this from the perspective of those who are Slackers, using SBos to manage almost all of their installed software bases in the first place. Thanks, and kindest regards, - -- Bradley D. Thornton Manager Network Services NorthTech Computer TEL: +1.310.388.9469 (US) TEL: +44.203.318.2755 (UK) TEL: +41.43.508.05.10 (CH) http://NorthTech.US -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Find this cert at x-hkp://pool.sks-keyservers.net iQEcBAEBAwAGBQJSLleNAAoJEE1wgkIhr9j3ogAH/AzcuayER6Ty4abfIPxHBu6M 51MCP1LV35EPQtvbhMgvvYylJrRA131CltnKSrNzwzm9TC0dIy4xKTozrdhNSG5U HiyKEHNOqLCcC/eYYcydDOromaH9OWzsDmzxNXrMF+VZIiJcLK5jDilouVmWhU7S mPfJGeLFMa8sYdudVp/TFaX4FSZ3r02Iz9GeOPeYoxSZw+3TPdCjUXrbE+bK7S20 NrelTz8APQlA4VuzFYK0l4Hif21zPqMgd1bKE3NRHtWqxXpJZQ2khE6fB854eLPX PKLSDu0dOMcLALcKVfUbUbKEtkPQy8xrhgUTVmSVDDuRkhaN1O9qEub5P5LVcR8= =okhx -----END PGP SIGNATURE----- From willysr at gmail.com Mon Sep 9 23:31:40 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Tue, 10 Sep 2013 06:31:40 +0700 Subject: [Slackbuilds-users] perl-* slackbuild updates In-Reply-To: <522E578D.7090604@NorthTech.US> References: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> <522E578D.7090604@NorthTech.US> Message-ID: > I know this is a bit off-topic, but I've been wanting to ask this for a > long time, and this list is probably the place where I'll get the best > answers, from the people who have the perspectives that matter to me the > most in this regard. > > I often have problems when meeting Perl dependencies using SlackBuilds, > sometimes they bomb, but more often than not, the list of deps needed > are simply incomplete, prompting me to just use the cpan shell to > install and maintain those modules. > > What are the advantages of using SBo's over that of cpan, for the > management and installation of Perl modules, and why might I choose one > method over the other? > > Again, I'm asking this from the perspective of those who are Slackers, > using SBos to manage almost all of their installed software bases in the > first place. the advantages of using SBo is that it will match the same Perl version as Slackware and it will not change that often. Believe me, sometimes, it's better to stick with the same version unless you really need them to maintain from CPAN. I tried to run upgrade on CPAN and it blew up the CPAN as Perl gets upgraded (in -Current) to 5.18 and some of the modules weren't compatible since it was compiled in CPAN, and not manageable through pkgtool. If you are planning to use -Stable release for a long time, *probably* it might not be that problematic, but if you need to upgrade your PERL version, just make sure that all the modules that are upgraded in CPAN would be compatible with the API version on the PERL version -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From pprkut at liwjatan.at Tue Sep 10 06:14:14 2013 From: pprkut at liwjatan.at (Heinz Wiesinger) Date: Tue, 10 Sep 2013 08:14:14 +0200 Subject: [Slackbuilds-users] perl-* slackbuild updates In-Reply-To: <522E578D.7090604@NorthTech.US> References: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> <522E578D.7090604@NorthTech.US> Message-ID: <8624728.PGc9jsE23y@callisto> On Monday 09 September 2013 16:19:41 Bradley D. Thornton wrote: > - gpg control packet > > On 09/09/2013 03:22 AM, LEVAI Daniel wrote: > > Hi! > > > > I'm working on a slackbuild for the WWW-Google-Contacts perl module and > > the long line of its dependencies required some updates to other perl > > modules. I've made updated slackbuilds and mailed the diffs to the > > corresponding maintainers, but all of them timed out. > > It would be great to see these get updated, so what now? > > > > The modules in question: > > Crypt-SSLeay > > Net-SSLeay > > perl-Class-Load > > perl-Dist-CheckConflicts > > perl-IO-Socket-INET6 > > I know this is a bit off-topic, but I've been wanting to ask this for a > long time, and this list is probably the place where I'll get the best > answers, from the people who have the perspectives that matter to me the > most in this regard. > > I often have problems when meeting Perl dependencies using SlackBuilds, > sometimes they bomb, but more often than not, the list of deps needed > are simply incomplete, prompting me to just use the cpan shell to > install and maintain those modules. > > What are the advantages of using SBo's over that of cpan, for the > management and installation of Perl modules, and why might I choose one > method over the other? > > Again, I'm asking this from the perspective of those who are Slackers, > using SBos to manage almost all of their installed software bases in the > first place. This is, actually, not perl specific. A lot of languages have native mechanisms for managing extensions: perl has CPAN python has easy_install php has pear/pecl ruby has gem ... using either one of them works just fine. After all they were developed to handle the job of maintaining extensions. Now, consider the case where for some reason you need extensions for all of them. You have the choice of using SlackBuilds to generate packages for them, and manage them all using pkgtool, or you can use the native mechanism for each of them, or you mix and match. Again, either option will work just fine, but it's a matter of what you consider easier to work with. Me, I prefer working with one toolset rather than n different tools for updating my software. Grs, Heinz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 230 bytes Desc: This is a digitally signed message part. URL: From thomas at beingboiled.info Tue Sep 10 20:33:45 2013 From: thomas at beingboiled.info (Thomas Morper) Date: Tue, 10 Sep 2013 22:33:45 +0200 (CEST) Subject: [Slackbuilds-users] perl-* slackbuild updates In-Reply-To: <522E578D.7090604@NorthTech.US> References: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> <522E578D.7090604@NorthTech.US> Message-ID: On Mon, 9 Sep 2013, Bradley D. Thornton wrote: > What are the advantages of using SBo's over that of cpan, for the > management and installation of Perl modules, and why might I choose one > method over the other? When I use Perl modules, I usually need the exact same module versions on more than one machine (which could be different Slackware versions or have the gcc suite missing due to space constraints). In that case having a .txz from a SlackBuild makes installing, upgrading and downgrading(!) much, much easier than running "perl -MCPAN -e shell" everywhere and trying to keep everything in sync somehow. However... The traditional SBo approach for packaging modules works fine as long as you don't need more than a dozen. Beyond that it gets interesting. There are good, yet complex modules like Catalyst or Dancer2 that have 50 or more dependencies. I can't imagine anyone writing a SlackBuild for each and everyone of it. cpan2tgz has been around for a quite a while, but I wanted something that allowed more control over the result, so I took the perl template from SBo, made it as generic as possible, added "pre" and "post" hooks to allow modifications, and put the list of dependencies into a Makefile. The maintainer still has to check search.cpan.org manually, read the ChangeLog, track the list of dependencies, and more. But after that it's a simple "make" to put everything together instead of writing / editing the same .SlackBuild / .info / README / slack-desc files over and over again. Have a look at what I call "autoperl" here: http://beingboiled.info/slackware/14.0/build/autoperl/ This has been working very well for me for more than two years but nonetheless is propably not "production ready" for everyone. Feedback on how to make this work for more users will be highly appreciated. Hmm... this post isn't really and answer to your question but more like an extended version of the "how can I make building Perl modules more comfortable?" question, isn't it? Sorry for that. -- From baildon.research at googlemail.com Tue Sep 10 22:11:01 2013 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 10 Sep 2013 23:11:01 +0100 Subject: [Slackbuilds-users] perl-* slackbuild updates In-Reply-To: References: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> <522E578D.7090604@NorthTech.US> Message-ID: Heinz wrote: > perl has CPAN > python has easy_install > php has pear/pecl > ruby has gem > ... ... Firefox, Chrome, Libreoffice, Gimp, qgis, dokuwiki ... every one a different plugin mechanism, every one a configuration management nightmare. And now, O Joy!! we have the Lennart Crapplet to look forward to. http://lwn.net/Articles/562138/ Using pkgtools for everything has simplicity, familiarity, scriptability, repeatability, testability, scalability and recoverability. But not futility or senility ;-) Thomas wrote: > The traditional SBo approach for packaging modules works fine as long as > you don't need more than a dozen. Beyond that it gets interesting. There > are good, yet complex modules like Catalyst or Dancer2 that have 50 or > more dependencies. I'd be happy if 'make test' was removed from the Perl template. It's a frequent cause of complex dependencies and bogus failures. It promises more QA than it delivers. Interestingly, TeX's CTAN, which has similar granularity to CPAN, went the other way and ended up with the 1.4Gb monolith that is Tex Live. (Thanks, Robby!) -D. From andreas at andreasvoegele.com Tue Sep 10 22:41:55 2013 From: andreas at andreasvoegele.com (=?ISO-8859-1?Q?Andreas_V=F6gele?=) Date: Wed, 11 Sep 2013 00:41:55 +0200 Subject: [Slackbuilds-users] perl-* slackbuild updates In-Reply-To: References: <20130909102222.GA11488@daniell-kurt.KURTHQ.local> <522E578D.7090604@NorthTech.US> Message-ID: On 09/10/2013 10:33 PM, Thomas Morper wrote: > [...] complex modules like Catalyst or Dancer2 that have 50 or more > dependencies. I can't imagine anyone writing a SlackBuild for each > and everyone of it. Some operating systems package half of CPAN. But as maintainers go away keeping these packages up-to-date and consistent is a nightmare. Once I wanted to get a single Perl module updated but as several maintainers had quit I ended up updating dozens of packages. > [...] cpan2tgz has been around for a quite a while, but I wanted > something that allowed more control over the result, so I took the > perl template from SBo, [...], added "pre" and "post" hooks to allow > modifications, [...] The maintainer still has to check > search.cpan.org manually, read the ChangeLog, track the list of > dependencies, and more. [...] Have a look at what I call "autoperl" > here: > > http://beingboiled.info/slackware/14.0/build/autoperl/ > > This has been working very well for me for more than two years but > nonetheless is propably not "production ready" for everyone. Feedback > on how to make this work for more users will be highly appreciated. I wrote a CPANPLUS plugin that creates Slackware compatible packages but lets CPANPLUS do the hard work. Hooks that allow customizations are available through a plugin interface. A SlackBuild script exists: http://slackbuilds.org/repository/14.0/perl/perl-CPANPLUS-Dist-Slackware/ Unfortunately, the Perl 5 porters decided to remove CPANPLUS from the Perl core but CPANPLUS will continue to be available through CPAN. SlackBuild scripts for CPANPLUS on Slackware-current are available here: https://github.com/voegelas/slackbuilds-mystuff Someday I might also write a Dist::Zilla::Plugin::Slackware module that will be similar to Dist::Zilla::Plugin::RPM. Regards, Andreas From adis at linux.org.ba Wed Sep 11 12:50:02 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Wed, 11 Sep 2013 14:50:02 +0200 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: <6322767.2jBnRc8byD@jerseybastion> References: <6322767.2jBnRc8byD@jerseybastion> Message-ID: Hello guys, I have test slackbuild (see attachment). The scenario for using package produced by this slackbuild would be the following: 1) You don't have PostgreSQL installed. Install package, business as usual 2) You have PostgreSQL installed, don't care for in-place upgrades: Create backups, remove/upgrade PostgreSQL, load the backups 3) You have PostgreSQL installed (let's say 9.x series, or at least 8.3) You want to do in-place testing (two running PostgreSQL instances) and upgrade using pg_upgrade 3.1) Make sure you have backups 3.2) Build new PostgreSQL 9.3 3.3) Install new PostgreSQL 9.3, while keeping the old package installed as well - Please note that new PostgreSQL will have binaries in /usr/lib64/postgresql/9.3/bin, and install script create symlinks in /usr/bin only if respective postgresql binaries are not found in /usr/bin (i.e. it will _not_ overwrite your PostgreSQL 9.x binaries!) - Libraries will be kept as well (new install location for libraries is /usr/lib64/postgresql/9.3/lib) - Shared data, documents, include files will be overwritten 3.4) Make sure new rc.postgresql script is active - You can manage old PostgreSQL versions (< 9.3) by using: PG_VERSION=9.2 /etc/rc.d/rc.postgresql start|stop|... - Use PG_VERSION=9.2 for v9.2.x and older PostgreSQL versions - You can even specify port (port number is used for sockets as well): PG_VERSION=9.2 PG_PORT=6432 /etc/rc.d/rc.postgresql 3.5) Initialize the new PostgreSQL cluster as suggested by README file 3.6) Stop old and new cluster 3.7) Use pg_upgrade to import your data, e.g. /usr/lib64/postgresql/9.3/bin/pg_upgrade -v -b /usr/bin -B /usr/lib64/postgresql/9.3/bin \ -d /var/lib/pgsql/data -D /var/lib/pgsql/9.3/data Please remember that at this point, binaries in /usr/bin are still the old v9.2 binaries. When you remove old PostgreSQL package, you should create symlinks to the programs in /usr/lib64/postgresql/9.3/bin directory. You could use doinst.sh script, which is copied to /var/log/script/postgresql-9.3.0* Future PostgreSQL releases (e.g. 9.4) won't have binaries, but symlinks in /usr/bin, so this won't be necessary. Any feedback on all of this and testing the SlackBuild would be warmly welcomed. Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: postgresql.tgz Type: application/x-gzip Size: 5997 bytes Desc: not available URL: From shop at open-t.co.uk Thu Sep 12 20:33:12 2013 From: shop at open-t.co.uk (Sebastian Arcus) Date: Thu, 12 Sep 2013 21:33:12 +0100 Subject: [Slackbuilds-users] Hostapd latest version 2.0 - SBo still on 0.6.10 Message-ID: <52322508.9070109@open-t.co.uk> Just thought I would point out that the latest version of Hostapd is 2.0 - while the SBo version is on 0.6.10 I've emailed the maintainer - but I thought I would post here as well, in case it helps. Sebastian From miguel at thedeanda.com Thu Sep 12 20:38:20 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Thu, 12 Sep 2013 13:38:20 -0700 Subject: [Slackbuilds-users] pending queue Message-ID: how often do scripts get updated on the site? i submitted this awhile ago for mongo 2.4.5 -- just updated a few numbers in the script and its _still_ pending... now i need to update again for 2.4.6....... 17-Jul-2013 14:14 mongodb.tar.gz is there a way to have a peer reviewed process? something like just checking diffs can really speed up the process of accepting scripts. i want to help but don't know how. -miguel -------------- next part -------------- An HTML attachment was scrubbed... URL: From shop at open-t.co.uk Thu Sep 12 20:43:53 2013 From: shop at open-t.co.uk (Sebastian Arcus) Date: Thu, 12 Sep 2013 21:43:53 +0100 Subject: [Slackbuilds-users] Hostapd latest version 2.0 - SBo still on 0.6.10 In-Reply-To: <52322508.9070109@open-t.co.uk> References: <52322508.9070109@open-t.co.uk> Message-ID: <52322789.9020109@open-t.co.uk> On 12/09/13 21:33, Sebastian Arcus wrote: > Just thought I would point out that the latest version of Hostapd is 2.0 > - while the SBo version is on 0.6.10 > > I've emailed the maintainer - but I thought I would post here as well, > in case it helps. > > Sebastian > Just a follow-up to the above. My email to the maintainer has just bounced back (see below). Should I just go ahead and submit an updated version myself - or does someone else want to do it? "This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. The following addresses failed: SMTP error from remote server after RCPT command: host gmail-smtp-in.l.google.com[173.194.70.26]: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 x42si886725eel.176 - gsmtp" From thomas at beingboiled.info Tue Sep 17 22:24:25 2013 From: thomas at beingboiled.info (Thomas Morper) Date: Wed, 18 Sep 2013 00:24:25 +0200 (CEST) Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> Message-ID: On Wed, 11 Sep 2013, Adis Nezirovic wrote: > 3) You have PostgreSQL installed (let's say 9.x series, or at least 8.3) > You want to do in-place testing (two running PostgreSQL instances) and > upgrade using pg_upgrade I've got a small 15 GB Postgres 9.2 DB on a modest Atom server. The traditional dump/restore cycle takes around 3 hours, so the new approach to an easier "pg_upgrade" is very much welcome. > 3.3) Install new PostgreSQL 9.3, while keeping the old package installed > as well. Please note that new PostgreSQL will have binaries in > /usr/lib64/postgresql/9.3/bin, and install script create symlinks in > /usr/bin only if respective postgresql binaries are not found in > /usr/bin (i.e. it will _not_ overwrite your PostgreSQL 9.x binaries!) Minor problem: doinst.sh generates broken symlinks to usr/lib... instead of /usr/lib... - was easily fixed. > 3.4) Make sure new rc.postgresql script is active Minor problem: "Could not find 'postgres' binary." because the PRGNAM variable is missing in rc.postgresql. Again, easily fixed. Hmm... does this actually need to be a variable? > Any feedback on all of this and testing the SlackBuild would be warmly > welcomed. Besides those two minor issues (see attached diff for my changes) your test release of the SlackBuild has been working fine for me. Adding the "--link" option to pg_upgrade allowed upgrading from 9.2 to 9.3 in about a minute with no need for a dump/restore-cycle. -- -------------- next part -------------- diff -u -r postgresql-an/doinst.sh postgresql-tm/doinst.sh --- postgresql-an/doinst.sh 2013-09-11 14:39:41.000000000 +0200 +++ postgresql-tm/doinst.sh 2013-09-17 20:44:40.822303331 +0200 @@ -30,10 +30,10 @@ if [ -e usr/bin/$pg_prog ]; then # make sure we overwrite only symlinks and not actual binaries if [ -L usr/bin/$pg_prog ]; then - ln -sf $pg_binary usr/bin/$pg_prog + ln -sf /$pg_binary usr/bin/$pg_prog fi else - ln -s $pg_binary usr/bin/$pg_prog + ln -s /$pg_binary usr/bin/$pg_prog fi done diff -u -r postgresql-an/rc.postgresql.new postgresql-tm/rc.postgresql.new --- postgresql-an/rc.postgresql.new 2013-09-11 14:39:41.000000000 +0200 +++ postgresql-tm/rc.postgresql.new 2013-09-17 22:14:27.446243178 +0200 @@ -23,6 +23,7 @@ PG_VERSION=${PG_VERSION:- at PG_VERSION@} PG_PORT=${PG_PORT:- at PG_PORT@} +PRGNAM=${PRGNAM:- at PRGNAM@} LIBDIRSUFFIX="@LIBDIRSUFFIX@" if [ "x$PG_VERSION" != "x9.2" ];then From adis at linux.org.ba Wed Sep 18 11:48:36 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Wed, 18 Sep 2013 13:48:36 +0200 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> Message-ID: On Wed, Sep 18, 2013 at 12:24 AM, Thomas Morper wrote: > Minor problem: doinst.sh generates broken symlinks to usr/lib... instead > of /usr/lib... - was easily fixed. > > > 3.4) Make sure new rc.postgresql script is active > > Minor problem: "Could not find 'postgres' binary." because the PRGNAM > variable is missing in rc.postgresql. Again, easily fixed. Hmm... does > this actually need to be a variable? > The problem with symlinks is we must not use absolute paths (installpkg can be called with --root parameter). Anyway, I've simplified logic for symlinks in doinst.sh, should be more robust now. I've also removed PRGNAM from all scripts except SlackBuild (it was a leftover from an earlier experiment with versioned package names). Thanks for testing, I'll submit the SlackBuild (attached) during the weekend. Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: postgresql.tgz Type: application/x-gzip Size: 5945 bytes Desc: not available URL: From thomas at beingboiled.info Wed Sep 18 21:53:48 2013 From: thomas at beingboiled.info (Thomas Morper) Date: Wed, 18 Sep 2013 23:53:48 +0200 (CEST) Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> Message-ID: On Wed, 18 Sep 2013, Adis Nezirovic wrote: > The problem with symlinks is we must not use absolute paths (installpkg > can be called with --root parameter). Anyway, I've simplified logic for > symlinks in doinst.sh, should be more robust now. > I've also removed PRGNAM from all scripts except SlackBuild (it was a > leftover from an earlier experiment with versioned package names). The new version works almost perfectly. One minor nitpick though: The previous version explicitly set permissions for the DATADIR: # permissions for DATADIR should be u=rwx (0700) chmod 700 $PKG/var/lib/pgsql/$PG_VERSION/data The new version doesn't. That's fine, because the mandatory "initdb" will set the correct permissions. However, if you "upgradepkg --reinstall" postgres the DATADIR's permissions will get reset to 0755 and the server won't start any more. -- From adis at linux.org.ba Thu Sep 19 10:58:54 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Thu, 19 Sep 2013 12:58:54 +0200 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> Message-ID: Great, I've restored the line for explicit permissions of DATADIR and added a few tips for upgrade in README.SBo See attached archive. Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: postgresql.tgz Type: application/x-gzip Size: 6224 bytes Desc: not available URL: From adis at linux.org.ba Thu Sep 19 14:29:45 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Thu, 19 Sep 2013 16:29:45 +0200 Subject: [Slackbuilds-users] subversion linked to libpq Message-ID: Hello, I know Pat reads this list, hope he sees this. It seems to me that official Slackware subversion binary is somehow linked to PostgreSQL (Slackware-Current, subversion-1.7.13, but also v1.7.10): ldd /usr/bin/svn| grep libpq libpq.so.5 => not found I've noticed this when I removed PostgreSQL 9.2 package, new package for 9.3 keeps libraries in /usr/lib64/postgresql/9.3/lib Can anoyone confirm this? Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Thu Sep 19 15:52:49 2013 From: artourter at gmail.com (Greg' Ar Tourter) Date: Thu, 19 Sep 2013 16:52:49 +0100 Subject: [Slackbuilds-users] subversion linked to libpq In-Reply-To: References: Message-ID: Hi, not on my systems (all up-to-date -current with no postgres installed) you must have recompiled subversion or you binary has been overwritten by something. Greg On 19 September 2013 15:29, Adis Nezirovic wrote: > Hello, > > I know Pat reads this list, hope he sees this. > > It seems to me that official Slackware subversion binary is somehow linked > to PostgreSQL > (Slackware-Current, subversion-1.7.13, but also v1.7.10): > > ldd /usr/bin/svn| grep libpq > libpq.so.5 => not found > > I've noticed this when I removed PostgreSQL 9.2 package, new package for > 9.3 keeps libraries in > /usr/lib64/postgresql/9.3/lib > > > Can anoyone confirm this? > > > Best regards, > Adis > > _______________________________________________ > 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 adis at linux.org.ba Thu Sep 19 18:55:52 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Thu, 19 Sep 2013 20:55:52 +0200 Subject: [Slackbuilds-users] subversion linked to libpq In-Reply-To: References: Message-ID: You are correct, svn is not directly linked to libpq, it was transitive issue with libapr (subversion -> libapr -> libpq), since I have private copy of libapr, compiled with Postgres support (for apache mod_authn_dbd). Thanks for your input, I was seeing ghosts. Sorry for the noise guys. Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: From Hullen at t-online.de Fri Sep 20 09:09:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 20 Sep 2013 11:09:00 +0200 Subject: [Slackbuilds-users] clamav 0.98 Message-ID: Hallo, slackbuilds-users, "clamav 0.98" has changed the names of the configuration files in "/etc" to "xyz.conf.sample". The "slackBuild" file and "doinst.sh" have to be changed therefore. Viele Gruesse! Helmut From matteo.bernardini at gmail.com Fri Sep 20 09:50:10 2013 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 20 Sep 2013 11:50:10 +0200 Subject: [Slackbuilds-users] clamav 0.98 In-Reply-To: References: Message-ID: thanks Helmut for the heads up, I just submitted the attached update to what we have in the repository. Matteo -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-system-clamav-Updated-for-version-0.98.patch Type: application/octet-stream Size: 3536 bytes Desc: not available URL: From Hullen at t-online.de Fri Sep 20 11:05:00 2013 From: Hullen at t-online.de (Helmut Hullen) Date: 20 Sep 2013 13:05:00 +0200 Subject: [Slackbuilds-users] clamav 0.98 In-Reply-To: Message-ID: Hallo, Matteo, Du meintest am 20.09.13: > thanks Helmut for the heads up, I just submitted the attached update > to what we have in the repository. Fine - thank you! Viele Gruesse! Helmut From nick at linicks.net Fri Sep 20 13:38:20 2013 From: nick at linicks.net (Nick Warne) Date: Fri, 20 Sep 2013 14:38:20 +0100 Subject: [Slackbuilds-users] autotools-template.SlackBuild - missing perm Message-ID: <20130920133820.GA15615@sauron> Hi all, Great site, thanks. I currently preparing a submission and noticed a small issue with the autotools-template.SlackBuild script. \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; ...could do with a '-perm 640 -o' in there. Regards, Nick -- http://linicks.net/ From rneri at libero.it Sat Sep 21 12:35:55 2013 From: rneri at libero.it (rneri at libero.it) Date: Sat, 21 Sep 2013 14:35:55 +0200 (CEST) Subject: [Slackbuilds-users] Orphaned/Obsolete SlackBuilds Message-ID: <814191412.4349851379766955842.JavaMail.actor@webmail6> Hi all, after some hardware replacements & successful upgrade to 14.1beta, there are a few SlackBuilds that I can't/don't need to maintain any longer, namely system/avermedia-a867 I haven't this device anymore; I understand in kernel 3.10.12 it's managed by module dvb_usb_af9035, so probably it should simply be removed from the 14.1 branch network/rt5370 my D-Link DWA-125 USB device now works perfectly with stock module rt2800usb, so I think also this SlackBuild can be removed from 14.1 network/b43-firmware network/b43-fwcutter network/b43legacy-firmware I have also replaced this device so I'm unable to test any new version, if anyone wishes to take these over they're welcome. Thanks Roberto From openpandora at free.fr Mon Sep 23 11:33:12 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Mon, 23 Sep 2013 13:33:12 +0200 (CEST) Subject: [Slackbuilds-users] Qmc2 has been updated. In-Reply-To: <2089587790.244952619.1379935986793.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: <1662081923.244952718.1379935992814.JavaMail.root@zimbra53-e8.priv.proxad.net> Hi ! http://qmc2.arcadehits.net/wordpress/ From openpandora at free.fr Tue Sep 24 00:16:20 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 24 Sep 2013 02:16:20 +0200 (CEST) Subject: [Slackbuilds-users] Is SDL 2 SlackBuild planned ? Message-ID: <2113237169.245841607.1379981780655.JavaMail.root@zimbra53-e8.priv.proxad.net> ...by someone ? Hi btw ^^ . From thedoogster at gmail.com Tue Sep 24 04:22:04 2013 From: thedoogster at gmail.com (Doogster) Date: Mon, 23 Sep 2013 21:22:04 -0700 Subject: [Slackbuilds-users] Is SDL 2 SlackBuild planned ? In-Reply-To: <2113237169.245841607.1379981780655.JavaMail.root@zimbra53-e8.priv.proxad.net> References: <2113237169.245841607.1379981780655.JavaMail.root@zimbra53-e8.priv.proxad.net> Message-ID: SDL2 is approved. SDL2_mixer, SDL2_net, SDL2_image and SDL2_ttf are in pending. All were submitted by me. On Mon, Sep 23, 2013 at 5:16 PM, wrote: > ...by someone ? > > Hi btw ^^ . > _______________________________________________ > 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 openpandora at free.fr Tue Sep 24 07:18:16 2013 From: openpandora at free.fr (openpandora at free.fr) Date: Tue, 24 Sep 2013 09:18:16 +0200 (CEST) Subject: [Slackbuilds-users] Is SDL 2 SlackBuild planned ? In-Reply-To: Message-ID: <1156058468.246162212.1380007096720.JavaMail.root@zimbra53-e8.priv.proxad.net> Neat ! Thanks. ----- Mail original ----- De: "Doogster" ?: "SlackBuilds.org Users List" Envoy?: Mardi 24 Septembre 2013 06:22:04 Objet: Re: [Slackbuilds-users] Is SDL 2 SlackBuild planned ? SDL2 is approved. SDL2_mixer, SDL2_net, SDL2_image and SDL2_ttf are in pending. All were submitted by me. On Mon, Sep 23, 2013 at 5:16 PM, < openpandora at free.fr > wrote: ...by someone ? Hi btw ^^ . _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ From gabrielmagno1 at gmail.com Tue Sep 24 17:51:13 2013 From: gabrielmagno1 at gmail.com (Gabriel Magno) Date: Tue, 24 Sep 2013 14:51:13 -0300 Subject: [Slackbuilds-users] pending queue In-Reply-To: References: Message-ID: The frequency of updates varies, but generally it happens once a week. I think the delay is related to Slackware 14.1 release approaching. -- Gabriel Magno 2013/9/12 Miguel De Anda > how often do scripts get updated on the site? i submitted this awhile ago > for mongo 2.4.5 -- just updated a few numbers in the script and its _still_ > pending... now i need to update again for 2.4.6....... > > 17-Jul-2013 14:14 mongodb.tar.gz > > is there a way to have a peer reviewed process? something like just > checking diffs can really speed up the process of accepting scripts. i want > to help but don't know how. > > -miguel > > _______________________________________________ > 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 miguel at thedeanda.com Tue Sep 24 17:52:57 2013 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 24 Sep 2013 10:52:57 -0700 Subject: [Slackbuilds-users] pending queue In-Reply-To: References: Message-ID: I see. I have updates to both build scripts I have in the queue (newer versions released) but I don't want to restart the process. On Sep 24, 2013 10:51 AM, "Gabriel Magno" wrote: > The frequency of updates varies, but generally it happens once a week. > I think the delay is related to Slackware 14.1 release approaching. > > -- > Gabriel Magno > > > 2013/9/12 Miguel De Anda > >> how often do scripts get updated on the site? i submitted this awhile ago >> for mongo 2.4.5 -- just updated a few numbers in the script and its _still_ >> pending... now i need to update again for 2.4.6....... >> >> 17-Jul-2013 14:14 mongodb.tar.gz >> >> is there a way to have a peer reviewed process? something like just >> checking diffs can really speed up the process of accepting scripts. i want >> to help but don't know how. >> >> -miguel >> >> _______________________________________________ >> 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 joshuakwood at gmail.com Tue Sep 24 18:02:19 2013 From: joshuakwood at gmail.com (JK Wood) Date: Tue, 24 Sep 2013 13:02:19 -0500 Subject: [Slackbuilds-users] pending queue In-Reply-To: References: Message-ID: On Sep 24, 2013 12:53 PM, "Miguel De Anda" wrote: > > I see. I have updates to both build scripts I have in the queue (newer versions released) but I don't want to restart the process. > > On Sep 24, 2013 10:51 AM, "Gabriel Magno" wrote: >> >> The frequency of updates varies, but generally it happens once a week. >> I think the delay is related to Slackware 14.1 release approaching. >> >> -- >> Gabriel Magno >> >> >> 2013/9/12 Miguel De Anda >>> >>> how often do scripts get updated on the site? i submitted this awhile ago for mongo 2.4.5 -- just updated a few numbers in the script and its _still_ pending... now i need to update again for 2.4.6....... >>> >>> 17-Jul-2013 14:14 mongodb.tar.gz >>> >>> is there a way to have a peer reviewed process? something like just checking diffs can really speed up the process of accepting scripts. i want to help but don't know how. >>> >>> -miguel >>> >>> _______________________________________________ >>> 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/ > > In that case, use the links you received when you submitted the packages to remove them from Pending. That's what they're for. Thanks, JK -------------- next part -------------- An HTML attachment was scrubbed... URL: From dragonwisard at gmail.com Wed Sep 25 20:26:00 2013 From: dragonwisard at gmail.com (Ben Mendis) Date: Wed, 25 Sep 2013 16:26:00 -0400 Subject: [Slackbuilds-users] tsocks is broken on Slackware64 Message-ID: Hello, I was teaching a coworker about SSH tunneling and wanted to demonstrate using a SOCKS proxy with command-line utilities that are not SOCKS-aware. I tried to demonstrate tsocks but it did not work properly out-of-the-box on Slackware64. After a little bit of troubleshooting I figured out that the problem was an incorrect library path being added to LD_PRELOAD. The 'tsocks' command is adding the path '/usr/lib/libtsocks.so' when the library is actually located at '/usr/lib64/libtsocks.so'. It works fine if you specify it manually, eg: $ LD_PRELOAD="/usr/lib64/libtsocks.so" ssh target_host proxychains works correctly out of the box. Also, it would be helpful if the tsocks.conf examples from the source directory (let alone the 'inspectsocks' and 'validateconf' utilities which are referenced in the tsocks man page) were included in the package. Thank you, Ben the Pyrate -------------- next part -------------- An HTML attachment was scrubbed... URL: From C.J.Theunissen at differ.nl Thu Sep 26 08:27:48 2013 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Thu, 26 Sep 2013 10:27:48 +0200 (CEST) Subject: [Slackbuilds-users] tsocks is broken on Slackware64 In-Reply-To: References: Message-ID: On Wed, 25 Sep 2013, Ben Mendis wrote: >Hello, > >I was teaching a coworker about SSH tunneling and wanted to demonstrate using a SOCKS proxy with command-line utilities that are not SOCKS-aware. I tried to demonstrate tsocks but it did not work properly out-of-the-box on Slackware64. > >After a little bit of troubleshooting I figured out that the problem was an incorrect library path being added to LD_PRELOAD. > >The 'tsocks' command is adding the path '/usr/lib/libtsocks.so' when the library is actually located at '/usr/lib64/libtsocks.so'. >It works fine if you specify it manually, eg: >$ LD_PRELOAD="/usr/lib64/libtsocks.so" ssh target_host > >proxychains works correctly out of the box. > >Also, it would be helpful if the tsocks.conf examples from the source directory (let alone the 'inspectsocks' and 'validateconf' utilities which are referenced in the tsocks man page) were included in the package. > >Thank you, >Ben the Pyrate > Two months ago I reported a similar issue to this list and was pointed to: http://www.slackbuilds.org/faq/#multilib . 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 jbernts at broadpark.no Thu Sep 26 18:27:30 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 26 Sep 2013 20:27:30 +0200 Subject: [Slackbuilds-users] Wireshark installation error Message-ID: <20130926182730.GA1786@jostein> The wireshark slackbuild errors out with this: wireshark.pod > wireshark.1 Wide character in printf at /usr/share/perl5/Pod/Simple.pm line 539. wireshark.pod around line 3525: Non-ASCII character seen before =encoding in 'KovE?'. Assuming UTF-8 POD document had syntax errors at /usr/bin/pod2man line 71. make[2]: *** [wireshark.1] Error 255 make[2]: Leaving directory `/tmp/SBo/wireshark-1.8.6/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/wireshark-1.8.6' make: *** [all] Error 2 Anyone solved this? A doc install bug? Jostein From nickblizzard1776 at gmail.com Thu Sep 26 18:33:28 2013 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Thu, 26 Sep 2013 14:33:28 -0400 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: <20130926182730.GA1786@jostein> References: <20130926182730.GA1786@jostein> Message-ID: Guessing you are on -current? There were some patches / updates that needed applied due to changes in slackware after 14. Pulling a latest worked for me if I am recalling correctly. On Thu, Sep 26, 2013 at 2:27 PM, Jostein Berntsen wrote: > The wireshark slackbuild errors out with this: > > wireshark.pod > wireshark.1 > Wide character in printf at /usr/share/perl5/Pod/Simple.pm line 539. > wireshark.pod around line 3525: Non-ASCII character seen before =encoding > in > 'KovE?'. Assuming UTF-8 > POD document had syntax errors at /usr/bin/pod2man line 71. > make[2]: *** [wireshark.1] Error 255 > make[2]: Leaving directory `/tmp/SBo/wireshark-1.8.6/doc' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/SBo/wireshark-1.8.6' > make: *** [all] Error 2 > > Anyone solved this? A doc install bug? > > Jostein > > > > _______________________________________________ > 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 jbernts at broadpark.no Thu Sep 26 18:37:05 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 26 Sep 2013 20:37:05 +0200 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: References: <20130926182730.GA1786@jostein> Message-ID: <20130926183705.GB1786@jostein> On 26.09.13,14:33, Nick Blizzard wrote: > Guessing you are on -current? > > There were some patches / updates that needed applied due to changes in > slackware after 14. > > Pulling a latest worked for me if I am recalling correctly. > > Thanks. That's right, I'm on current. Will check it out. Jostein From baildon.research at googlemail.com Thu Sep 26 18:42:32 2013 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 26 Sep 2013 19:42:32 +0100 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: <20130926182730.GA1786@jostein> References: <20130926182730.GA1786@jostein> Message-ID: It's a Perl 5.18 thing. To fix it, insert a line '=encoding utf8' at the front of doc/wireshark.pod.template. Stick this bit of code in the SlackBuild, eg. after extracting the tarball: patch -p1 << :::: --- a/doc/wireshark.pod.template +++ b/doc/wireshark.pod.template @@ -1,3 +1,4 @@ +=encoding utf8 =head1 NAME :::: On 26 September 2013 19:27, Jostein Berntsen wrote: > The wireshark slackbuild errors out with this: > > wireshark.pod > wireshark.1 > Wide character in printf at /usr/share/perl5/Pod/Simple.pm line 539. > wireshark.pod around line 3525: Non-ASCII character seen before =encoding in > 'KovE?'. Assuming UTF-8 > POD document had syntax errors at /usr/bin/pod2man line 71. > make[2]: *** [wireshark.1] Error 255 > make[2]: Leaving directory `/tmp/SBo/wireshark-1.8.6/doc' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/SBo/wireshark-1.8.6' > make: *** [all] Error 2 > > Anyone solved this? A doc install bug? > > Jostein > > > > _______________________________________________ > 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 nickblizzard1776 at gmail.com Thu Sep 26 18:47:50 2013 From: nickblizzard1776 at gmail.com (Nick Blizzard) Date: Thu, 26 Sep 2013 14:47:50 -0400 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: References: <20130926182730.GA1786@jostein> Message-ID: Just did a pull of wireshark 1.10.2, no issues anymore from pearl, pod, or anything else. On Thu, Sep 26, 2013 at 2:42 PM, David Spencer < baildon.research at googlemail.com> wrote: > It's a Perl 5.18 thing. To fix it, insert a line '=encoding utf8' at > the front of doc/wireshark.pod.template. Stick this bit of code in > the SlackBuild, eg. after extracting the tarball: > > patch -p1 << :::: > --- a/doc/wireshark.pod.template > +++ b/doc/wireshark.pod.template > @@ -1,3 +1,4 @@ > +=encoding utf8 > > =head1 NAME > > :::: > > > > On 26 September 2013 19:27, Jostein Berntsen wrote: > > The wireshark slackbuild errors out with this: > > > > wireshark.pod > wireshark.1 > > Wide character in printf at /usr/share/perl5/Pod/Simple.pm line 539. > > wireshark.pod around line 3525: Non-ASCII character seen before > =encoding in > > 'KovE?'. Assuming UTF-8 > > POD document had syntax errors at /usr/bin/pod2man line 71. > > make[2]: *** [wireshark.1] Error 255 > > make[2]: Leaving directory `/tmp/SBo/wireshark-1.8.6/doc' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory `/tmp/SBo/wireshark-1.8.6' > > make: *** [all] Error 2 > > > > Anyone solved this? A doc install bug? > > > > Jostein > > > > > > > > _______________________________________________ > > 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 mancha1 at hush.com Thu Sep 26 20:23:23 2013 From: mancha1 at hush.com (mancha) Date: Thu, 26 Sep 2013 20:23:23 +0000 Subject: [Slackbuilds-users] tsocks is broken on Slackware64 Message-ID: <20130926202323.AB6276013F@smtp.hushmail.com> On Wed, 25 Sep 2013 20:26:07 +0000 "Ben Mendis" wrote: >After a little bit of troubleshooting I figured out that >the problem was an incorrect library path being added to >LD_PRELOAD. You are right. The tsocks SBo package needs to be fixed for 64-bit systems. I agree adding the utilities: inspectsocks & validateconf as well as sample configurations would be an improvement. The attached patch (tsocks-1.8beta5-64bit.diff) can be placed in the build directory along with changes to the SlackBuild script below. --mancha ====== --- tsocks.SlackBuild.orig +++ tsocks.SlackBuild @@ -43,7 +43,7 @@ PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} -DOCS="COPYING ChangeLog FAQ" +DOCS="COPYING ChangeLog FAQ tsocks.conf.simple.example tsocks.conf.complex.example" if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" @@ -74,6 +74,10 @@ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 - o -perm 400 \) \ -exec chmod 644 {} \; +if [ "$ARCH" = "x86_64" ]; then + patch -p1 --verbose < $CWD/tsocks-1.8beta5-64bit.diff || exit 1 +fi + CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ @@ -86,6 +90,7 @@ make make install DESTDIR=$PKG +/usr/bin/install -m755 inspectsocks validateconf $PKG/usr/bin find $PKG | xargs file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs strip --strip-unneeded 2> /dev/null || true -------------- next part -------------- A non-text attachment was scrubbed... Name: tsocks-1.8beta5-64bit.diff Type: application/octet-stream Size: 1414 bytes Desc: not available URL: From jbernts at broadpark.no Fri Sep 27 15:48:28 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Fri, 27 Sep 2013 17:48:28 +0200 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: References: <20130926182730.GA1786@jostein> Message-ID: <20130927154828.GA1712@jostein> On 26.09.13,19:42, David Spencer wrote: > It's a Perl 5.18 thing. To fix it, insert a line '=encoding utf8' at > the front of doc/wireshark.pod.template. Stick this bit of code in > the SlackBuild, eg. after extracting the tarball: > > patch -p1 << :::: > --- a/doc/wireshark.pod.template > +++ b/doc/wireshark.pod.template > @@ -1,3 +1,4 @@ > +=encoding utf8 > > =head1 NAME > > :::: > Will try that, thanks! Jostein From evanton at tut.by Sun Sep 29 05:44:03 2013 From: evanton at tut.by (James Bond) Date: Sun, 29 Sep 2013 08:44:03 +0300 Subject: [Slackbuilds-users] suggestion: modify buildscript for chromium to build and bundle chromedriver too Message-ID: chromedriver is a standalone server that is needed to use chrome/chromium browser for automated tests with selenium (seleniumhq.org) testing framework cons: chromedriver isn't required for using chromium for regular web browsing, having it in the chromium package will bloat the package a bit pros: - chromedriver is available as precompiled binaries from http://code.google.com/p/chromedriver/downloads/list, yet there are misc issues like it not working on systems with a different glibc version (this is true for debian wheezy, not related to slackware, but provided for context), or incompatibility with chromium due to version mismatches (the latest chromedriver official linux binary doesn't work with chromium package from SBo because that version of chromium is too old, yet an older version official linux binary works). having a chromedriver binary compiled from the same source (since its source code is part of chromium) and bundled it in the slackware package will exclude all those problems - there will be no need to recompile a lot of sources (chromium is heavier than the average application) for building chromedriver as another package - changes needed to be made to the SBo buildscript for chromium aren't big (this worked for me in Slackware64-14.0) ---- snip ---- --- chromium.SlackBuild.old 2013-09-28 14:57:39.739962762 +0300 +++ chromium.SlackBuild 2013-09-28 21:15:47.397401614 +0300 @@ -112,7 +112,7 @@ -Drelease_extra_cflags="$CFLAGS" \ $DDSSE -make chrome chrome_sandbox BUILDTYPE=Release V=1 +make chrome chrome_sandbox chromedriver BUILDTYPE=Release V=1 # Creating the package cd out/Release/ @@ -120,6 +120,7 @@ mkdir -p $PKG/usr/bin install -m 0755 -D chrome $PKG/usr/lib${LIBDIRSUFFIX}/chromium install -m 4555 -o root -g root -D chrome_sandbox $PKG/usr/lib${LIBDIRSUFFIX}/chromium + install -m 0755 -D chromedriver $PKG/usr/lib${LIBDIRSUFFIX}/chromium install -m 0755 -D libffmpegsumo.so $PKG/usr/lib${LIBDIRSUFFIX}/chromium cp *.pak $PKG/usr/lib${LIBDIRSUFFIX}/chromium cp -a locales/ $PKG/usr/lib${LIBDIRSUFFIX}/chromium @@ -146,6 +147,7 @@ cd $PKG ln -s /usr/lib${LIBDIRSUFFIX}/chromium/chrome $PKG/usr/bin/chrome ln -s /usr/lib${LIBDIRSUFFIX}/chromium/chrome_sandbox $PKG/usr/bin/chrome_sandbox + ln -s /usr/lib${LIBDIRSUFFIX}/chromium/chromedriver $PKG/usr/bin/chromedriver cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild ---- snip ---- This is not a request of taking ownership over the chromium slackbuild (the email address of the current maintainer seems to be invalid, so there are chances the buildscript is abandoned). I am just providing feedback after struggling for a few days with getting chromedriver to work painlessly in Slackware, hoping it may be useful to others. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at gmail.com Sun Sep 29 12:33:49 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sun, 29 Sep 2013 19:33:49 +0700 Subject: [Slackbuilds-users] perl-xml-twig Message-ID: Hi, The source of perl-xml-twig has been removed by cpan site it's still available on the official website: http://xmltwig.org/xmltwig/XML-Twig-3.41.tar.gz -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From audrius at neutrino.lt Sun Sep 29 13:13:02 2013 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sun, 29 Sep 2013 16:13:02 +0300 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> Message-ID: <20130929131302.GA26285@varna> On Thu, 2013-09-19 at 12:58:54 +0200, Adis Nezirovic wrote: > Great, I've restored the line for explicit permissions of DATADIR and added > a few tips for upgrade in README.SBo > See attached archive. I have successfully upgraded from 9.2.4 to 9.3.0 and then encountered the problem: while psycopg2 (Python DB adapter for Postgres) builds fine, trying to use it results in the following error: ImportError: libpq.so.5: cannot open shared object file: No such file or directory Quick remedy was to add LD_LIBRARY_PATH=/usr/lib/postgresql/9.3/lib to the init script for my webapps, but is there a better solution for this? -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From jbernts at broadpark.no Sun Sep 29 13:57:36 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Sun, 29 Sep 2013 15:57:36 +0200 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: References: <20130926182730.GA1786@jostein> Message-ID: <20130929135736.GD1712@jostein> On 26.09.13,19:42, David Spencer wrote: > It's a Perl 5.18 thing. To fix it, insert a line '=encoding utf8' at > the front of doc/wireshark.pod.template. Stick this bit of code in > the SlackBuild, eg. after extracting the tarball: > > patch -p1 << :::: > --- a/doc/wireshark.pod.template > +++ b/doc/wireshark.pod.template > @@ -1,3 +1,4 @@ > +=encoding utf8 > > =head1 NAME > When I run it now I get this error instead: /usr/bin/pod2man \ --center="The Wireshark Network Analyzer" \ --release=1.8.6 \ wireshark.pod > wireshark.1 Wide character in printf at /usr/share/perl5/Pod/Simple.pm line 539. wireshark.pod around line 3526: Non-ASCII character seen before =encoding in 'KovE?'. Assuming UTF-8 POD document had syntax errors at /usr/bin/pod2man line 71. make[2]: *** [wireshark.1] Error 255 make[2]: Leaving directory `/tmp/SBo/wireshark-1.8.6/doc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/SBo/wireshark-1.8.6' make: *** [all] Error 2 Jostein From willysr at gmail.com Sun Sep 29 15:08:35 2013 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Sun, 29 Sep 2013 22:08:35 +0700 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: <20130929135736.GD1712@jostein> References: <20130926182730.GA1786@jostein> <20130929135736.GD1712@jostein> Message-ID: > When I run it now I get this error instead: > > /usr/bin/pod2man \ > --center="The Wireshark Network Analyzer" \ > --release=1.8.6 \ > wireshark.pod > wireshark.1 > Wide character in printf at /usr/share/perl5/Pod/Simple.pm line 539. > wireshark.pod around line 3526: Non-ASCII character seen before =encoding in > 'KovE?'. Assuming UTF-8 > POD document had syntax errors at /usr/bin/pod2man line 71. > make[2]: *** [wireshark.1] Error 255 > make[2]: Leaving directory `/tmp/SBo/wireshark-1.8.6/doc' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/tmp/SBo/wireshark-1.8.6' > make: *** [all] Error 2 It's all fixed in the latest version of wireshark, so no patches needed again :) -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From nick at linicks.net Sun Sep 29 15:32:01 2013 From: nick at linicks.net (Nick Warne) Date: Sun, 29 Sep 2013 16:32:01 +0100 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: <20130929131302.GA26285@varna> References: <6322767.2jBnRc8byD@jerseybastion> <20130929131302.GA26285@varna> Message-ID: <20130929153201.GA13032@sauron> On Sun, Sep 29, 2013 at 04:13:02PM +0300, Audrius Ka?ukauskas wrote: > On Thu, 2013-09-19 at 12:58:54 +0200, Adis Nezirovic wrote: > > Great, I've restored the line for explicit permissions of DATADIR and added > > a few tips for upgrade in README.SBo > > See attached archive. > > I have successfully upgraded from 9.2.4 to 9.3.0 and then encountered the > problem: while psycopg2 (Python DB adapter for Postgres) builds fine, > trying to use it results in the following error: > > ImportError: libpq.so.5: cannot open shared object file: No such file > or directory > > Quick remedy was to add LD_LIBRARY_PATH=/usr/lib/postgresql/9.3/lib to > the init script for my webapps, but is there a better solution for this? You can add paths that ldconfig uses in /etc/ld.so.conf Just add: /usr/lib/postgresql/9.3/lib to that file and then run as root: ldconfig Nick -- FSF Associate Member 5508 http://linicks.net/ From jbernts at broadpark.no Sun Sep 29 15:35:10 2013 From: jbernts at broadpark.no (Jostein Berntsen) Date: Sun, 29 Sep 2013 17:35:10 +0200 Subject: [Slackbuilds-users] Wireshark installation error In-Reply-To: References: <20130926182730.GA1786@jostein> <20130929135736.GD1712@jostein> Message-ID: <20130929153510.GE1712@jostein> On 29.09.13,22:08, Willy Sudiarto Raharjo wrote: > > When I run it now I get this error instead: > > > > /usr/bin/pod2man \ > > --center="The Wireshark Network Analyzer" \ > > --release=1.8.6 \ > > wireshark.pod > wireshark.1 > > Wide character in printf at /usr/share/perl5/Pod/Simple.pm line 539. > > wireshark.pod around line 3526: Non-ASCII character seen before =encoding in > > 'KovE?'. Assuming UTF-8 > > POD document had syntax errors at /usr/bin/pod2man line 71. > > make[2]: *** [wireshark.1] Error 255 > > make[2]: Leaving directory `/tmp/SBo/wireshark-1.8.6/doc' > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory `/tmp/SBo/wireshark-1.8.6' > > make: *** [all] Error 2 > > It's all fixed in the latest version of wireshark, so no patches needed again :) > > Thanks, I downloaded the latest version 1.10.2 and this installation worked. Had to change this line in the Slackbuild: From: sed -i "s|/lib)|/lib$LIBDIRSUFFIX)|g" configure.in To: sed -i "s|/lib)|/lib$LIBDIRSUFFIX)|g" config.h.in Jostein From thomas at beingboiled.info Sun Sep 29 23:58:02 2013 From: thomas at beingboiled.info (Thomas Morper) Date: Mon, 30 Sep 2013 01:58:02 +0200 (CEST) Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: <20130929131302.GA26285@varna> References: <6322767.2jBnRc8byD@jerseybastion> <20130929131302.GA26285@varna> Message-ID: On Sun, 29 Sep 2013, Audrius Ka?ukauskas wrote: > I have successfully upgraded from 9.2.4 to 9.3.0 and then encountered the > problem: while psycopg2 (Python DB adapter for Postgres) builds fine, > trying to use it results in the following error: > > ImportError: libpq.so.5: cannot open shared object file: No such file > or directory The setup.py for psycopg2 asks pg_config for config options, but ignores the required LDFLAGS. As a workaround, you could specify the flags while building the package, e.g.: env LDFLAGS="$(pg_config --ldflags)" sh psycopg2.SlackBuild It's easy to adapt the SlackBuild accordingly, but maybe it would be better to address this in psycopg2 itself. -- From adis at linux.org.ba Mon Sep 30 13:29:28 2013 From: adis at linux.org.ba (Adis Nezirovic) Date: Mon, 30 Sep 2013 15:29:28 +0200 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> <20130929131302.GA26285@varna> Message-ID: Yes, that's the pain of having libraries in non public directory. Either solution is fine, I would like to avoid editing the /etc/ld.so.conf What about adding --with-postgres-libraries to the psycopg2 configure line? Best regards, Adis -------------- next part -------------- An HTML attachment was scrubbed... URL: From rneri at libero.it Mon Sep 30 16:24:49 2013 From: rneri at libero.it (rneri at libero.it) Date: Mon, 30 Sep 2013 18:24:49 +0200 (CEST) Subject: [Slackbuilds-users] R: Orphaned/Obsolete SlackBuilds Message-ID: <329532975.1688101380558289584.JavaMail.defaultUser@defaultHost> Hi, having experienced some performance issues with my D-Link DWA-125 USB device and stock module rt2800usb, I thought that maybe it's better to keep the network/rt5370 SlackBuild in the 14.1 branch... I have prepared an update, I don't think it's urgent so I'll wait until submissions are reopened. Thanks Roberto From melikamp at melikamp.com Mon Sep 30 16:34:07 2013 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Mon, 30 Sep 2013 12:34:07 -0400 Subject: [Slackbuilds-users] R: Orphaned/Obsolete SlackBuilds In-Reply-To: <329532975.1688101380558289584.JavaMail.defaultUser@defaultHost> References: <329532975.1688101380558289584.JavaMail.defaultUser@defaultHost> Message-ID: <5249A7FF.3000104@melikamp.com> This has nothing to do with R (http://www.r-project.org/) slackbuild, right? No need to answer if it doesn't. On 09/30/2013 12:24 PM, rneri at libero.it wrote: > Hi, > having experienced some performance issues with my D-Link DWA-125 USB device > and stock module rt2800usb, I thought that maybe it's better to keep the > network/rt5370 SlackBuild in the 14.1 branch... > > I have prepared an update, I don't think it's urgent so I'll wait until > submissions are reopened. > > Thanks > Roberto -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 901 bytes Desc: OpenPGP digital signature URL: From audrius at neutrino.lt Mon Sep 30 18:06:02 2013 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Mon, 30 Sep 2013 21:06:02 +0300 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> <20130929131302.GA26285@varna> Message-ID: <20130930180602.GB16357@varna> On Mon, 2013-09-30 at 15:29:28 +0200, Adis Nezirovic wrote: > Yes, that's the pain of having libraries in non public directory. Either > solution is fine, I would like to avoid editing the /etc/ld.so.conf > > What about adding --with-postgres-libraries to the psycopg2 configure line? In my last email I forgot to tell that in my case psycopg2 is installed into virtualenv via pip together with other dependencies of my projects (that's how I prefer it). It seems to me that the correct fix is to query pg_config for LDFLAGS value in setup.py file of psycopg2, as suggested by Thomas. I decided to ask about this in psycopg2 mailing list, will see what the developers think. Thanks to all for your input. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From kingbeowulf at gmail.com Mon Sep 30 19:41:18 2013 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 30 Sep 2013 12:41:18 -0700 Subject: [Slackbuilds-users] nvidia-319.49 and nvidia-legacy304 updates Message-ID: <5249D3DE.8010209@gmail.com> FYI nvidia updates are ready and I'll submit whenever SBo submissions reopen. For the impatient, or if you are effected by any of the bugs in the nvidia changelogs, you can grab tar-balls from the archives on either "master" or "14.0" branch: https://gitorious.org/kingbeowulf-slackbuilds/kingbeowulf-slackbuilds/source/303d6bc5ae4c426077aae6a9e1855700a5c99467: https://git.gitorious.org/kingbeowulf-slackbuilds/kingbeowulf-slackbuilds.git Testing of legacy304 appreciated; 319.49 works for me under 14.0 multilib. -Ed From nick at linicks.net Mon Sep 30 21:19:20 2013 From: nick at linicks.net (Nick Warne) Date: Mon, 30 Sep 2013 22:19:20 +0100 Subject: [Slackbuilds-users] PostgreSQL - multiple installed versions In-Reply-To: References: <6322767.2jBnRc8byD@jerseybastion> <20130929131302.GA26285@varna> Message-ID: <20130930211920.GA2127@sauron> On Mon, Sep 30, 2013 at 03:29:28PM +0200, Adis Nezirovic wrote: > Yes, that's the pain of having libraries in non public directory. Either > solution is fine, I would like to avoid editing the /etc/ld.so.conf Why rather avoid that? That is what it is there for to save complex linking errors like this. I sometimes install stuff in /home/~user for testing and just add the libs PATH as needed. It is easy and fault proof without having to mess about with build stuff etc. Plus it is read in order, so you can run old/new versions (etc.) with a quick edit. Obviously, this is no good for a generic build - but again, it is there to solve the issue of having various versions of libs on one system. Nick -- FSF Associate Member 5508 http://linicks.net/ From rshepard at appl-ecosys.com Mon Sep 30 22:22:07 2013 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 30 Sep 2013 15:22:07 -0700 (PDT) Subject: [Slackbuilds-users] Error Building chromium (24.0.1312.52) Message-ID: The message I tried sending to Francisco was returned as undeliverable. Perhaps someone here can help me overcome this build error. The libevent library is installed; I was trying to build the latest version of chromium to upgrade the installation. After 1 hour build time the attempt failed with: ui/base/gtk/gtk_expanded_container.cc: In function 'GType gtk_expanded_container_get_type()': ui/base/gtk/gtk_expanded_container.cc:118:1: error: size of array '_GStaticAssertCompileTimeAssertion_0' is negative ui/base/gtk/gtk_expanded_container.cc:118:1: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] ui/base/gtk/gtk_expanded_container.cc:118:1: error: size of array '_GStaticAssertCompileTimeAssertion_1' is negative ui/base/gtk/gtk_expanded_container.cc:118:1: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] ui/base/gtk/gtk_expanded_container.cc:118:1: error: size of array '_GStaticAssertCompileTimeAssertion_2' is negative make: *** [out/Release/obj.target/ui/ui/base/gtk/gtk_expanded_container.o] Error 1 This on a Sony Vaio running Slackware-14.0/x86_64. Have you any thoughts or suggestions for me? Thanks, Rich -- Richard B. Shepard, Ph.D. | Have knowledge, will travel. Applied Ecosystem Services, Inc. | Voice: 503-667-4517 Fax: 503-667-8863