From lists at osh.id.au Wed Feb 1 00:12:55 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 1 Feb 2017 10:12:55 +1000 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: References: Message-ID: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> On 02/01/2017 06:34 AM, JCA wrote: > I have tried building Chromium for 14.1, using the relevant Slackbuilds > scripts. The chromium version on SBo (31.0.1650.57) was released in late 2013! (see https://chromereleases.googleblog.com/2013/11/stable-channel-update_14.html). I wouldn't touch it; it's a massive security risk (which is why I think unmaintained browser slackbuilds should be dropped from the repo entirely). -- Dave From willysr at slackbuilds.org Wed Feb 1 00:11:59 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Feb 2017 07:11:59 +0700 Subject: [Slackbuilds-users] Stellarium-0.15.x, qt-5.7.x and libinput In-Reply-To: References: <8fb2fce7-0942-286d-89ed-855e2384dcb5@slackbuilds.org> Message-ID: > From your explanation I agree that adding libinput as a required dependency > for qt5 makes sense. I only see these applications that need to be tested > with libinput as a required dep., which also have qt5 as a required dep. > > desktop/compton-conf > network/qbittorrent-qt5 > system/zuluCrypt Done all in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed Feb 1 00:14:36 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 31 Jan 2017 16:14:36 -0800 (PST) Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> Message-ID: On Wed, 1 Feb 2017, David O'Shaughnessy wrote: > The chromium version on SBo (31.0.1650.57) was released in late 2013! I'm using Alien BOB's package, chromium-51.0.2704.84-i486-1alien, on 14.1. He might have an upgrade available, but since firefox is my main browser I don't frequently upgrade chromium. Rich From 1.41421 at gmail.com Wed Feb 1 00:19:40 2017 From: 1.41421 at gmail.com (JCA) Date: Tue, 31 Jan 2017 17:19:40 -0700 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> Message-ID: On Tue, Jan 31, 2017 at 5:12 PM, David O'Shaughnessy wrote: > On 02/01/2017 06:34 AM, JCA wrote: > > I have tried building Chromium for 14.1, using the relevant Slackbuilds > > scripts. > > The chromium version on SBo (31.0.1650.57) was released in late 2013! > (see > https://chromereleases.googleblog.com/2013/11/stable- > channel-update_14.html). > I wouldn't touch it; it's a massive security risk (which is why I think > unmaintained browser slackbuilds should be dropped from the repo entirely). > > -- > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > Well, that's what is available in Slackbuilds for 14.1. I guess that it is not really maintained anymore :-( -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Feb 1 00:21:05 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Feb 2017 07:21:05 +0700 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> Message-ID: <3860c7b6-676b-7dac-0452-24eafc98a60c@slackbuilds.org> > Well, that's what is available in Slackbuilds for 14.1. I guess that it is > not really maintained anymore :-( Unfortunately no. We simply don't have resources to maintain 2 repositories at the same time. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Wed Feb 1 00:23:05 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 1 Feb 2017 10:23:05 +1000 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> Message-ID: On 02/01/2017 10:19 AM, JCA wrote: > Well, that's what is available in Slackbuilds for 14.1. I guess that it > is not really maintained anymore :-( It's not maintained for any Slackware version. Vivaldi (based on chromium) is probably a better SBo option at this point. -- Dave From lists at osh.id.au Wed Feb 1 00:26:03 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 1 Feb 2017 10:26:03 +1000 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> Message-ID: <3c38f9e6-6c38-fba2-7288-2216d1912f11@osh.id.au> On 02/01/2017 10:23 AM, David O'Shaughnessy wrote: > On 02/01/2017 10:19 AM, JCA wrote: >> Well, that's what is available in Slackbuilds for 14.1. I guess that it >> is not really maintained anymore :-( > > It's not maintained for any Slackware version. Vivaldi (based on > chromium) is probably a better SBo option at this point. > > -- > Dave Sorry, I just realised (after Willy's comment) that the entire 14.1 branch is unmaintained, so my suggestion to use Vivaldi only applies to 14.2. -- Dave From lists at osh.id.au Wed Feb 1 00:26:53 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 1 Feb 2017 10:26:53 +1000 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> Message-ID: <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> On 02/01/2017 10:14 AM, Rich Shepard wrote: > On Wed, 1 Feb 2017, David O'Shaughnessy wrote: > >> The chromium version on SBo (31.0.1650.57) was released in late 2013! > > I'm using Alien BOB's package, chromium-51.0.2704.84-i486-1alien, on > 14.1. > He might have an upgrade available, but since firefox is my main browser I > don't frequently upgrade chromium. > > Rich Is there any reason why SBo doesn't just use the slackbuild that alienbob maintains for chromium anyway? -- Dave From willysr at slackbuilds.org Wed Feb 1 00:27:16 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Feb 2017 07:27:16 +0700 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> Message-ID: <08da7def-8f54-5ec3-026a-20a6c8c075e2@slackbuilds.org> > Is there any reason why SBo doesn't just use the slackbuild that > alienbob maintains for chromium anyway? That's up to the maintainer -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Wed Feb 1 00:29:41 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Tue, 31 Jan 2017 16:29:41 -0800 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> Message-ID: > Is there any reason why SBo doesn't just use the slackbuild that >> >> alienbob maintains for chromium anyway? I think this is a good reason: # This package is built with Alien's Google API keys for Chromium. # The keys are contained in the file "chromium_apikeys". # If you want to rebuild this package, you can use my API keys, however: # you are not allowed to re-distribute these keys!! # You can also obtain your own, see: # http://www.chromium.org/developers/how-tos/api-keys # Or else you can simply compile without API keys. This will disable stuff like # browser sync and other functionality which accesses Google APIs. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Wed Feb 1 00:37:35 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 1 Feb 2017 10:37:35 +1000 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: <08da7def-8f54-5ec3-026a-20a6c8c075e2@slackbuilds.org> References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> <08da7def-8f54-5ec3-026a-20a6c8c075e2@slackbuilds.org> Message-ID: <3e37060e-10f8-61bd-67c8-75fb7c8527e5@osh.id.au> On 02/01/2017 10:27 AM, Willy Sudiarto Raharjo wrote: >> Is there any reason why SBo doesn't just use the slackbuild that >> alienbob maintains for chromium anyway? > > That's up to the maintainer Considering we've not seen an update in 3 years, at this point I think we can safely say that the SBo Chromium is a zombie ship ;) Seriously though, it's not good to leave stagnant builds for high profile networking software (that must be riddled with security holes). There simply is no one maintaining it. -- Dave From willysr at slackbuilds.org Wed Feb 1 00:38:24 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Feb 2017 07:38:24 +0700 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: <3e37060e-10f8-61bd-67c8-75fb7c8527e5@osh.id.au> References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> <08da7def-8f54-5ec3-026a-20a6c8c075e2@slackbuilds.org> <3e37060e-10f8-61bd-67c8-75fb7c8527e5@osh.id.au> Message-ID: <7d4b466c-ecf3-7880-8e31-40f3d2f88b35@slackbuilds.org> > Considering we've not seen an update in 3 years, at this point I think > we can safely say that the SBo Chromium is a zombie ship ;) > > Seriously though, it's not good to leave stagnant builds for high > profile networking software (that must be riddled with security holes). > There simply is no one maintaining it. The last update was in 2016-10 https://slackbuilds.org/cgit/slackbuilds/commit/?id=9514306f3d8dd25b6f0a41428c0652d06bf80477 but yes, it's out-dated -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Wed Feb 1 01:07:08 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 1 Feb 2017 11:07:08 +1000 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: <7d4b466c-ecf3-7880-8e31-40f3d2f88b35@slackbuilds.org> References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> <934bdbb5-2812-6e0a-d1dd-b879d34ad947@osh.id.au> <08da7def-8f54-5ec3-026a-20a6c8c075e2@slackbuilds.org> <3e37060e-10f8-61bd-67c8-75fb7c8527e5@osh.id.au> <7d4b466c-ecf3-7880-8e31-40f3d2f88b35@slackbuilds.org> Message-ID: <68768f1b-d22f-7b12-b8c8-cfcb740be0dd@osh.id.au> On 02/01/2017 10:38 AM, Willy Sudiarto Raharjo wrote: >> Considering we've not seen an update in 3 years, at this point I think >> we can safely say that the SBo Chromium is a zombie ship ;) >> >> Seriously though, it's not good to leave stagnant builds for high >> profile networking software (that must be riddled with security holes). >> There simply is no one maintaining it. > > The last update was in 2016-10 > https://slackbuilds.org/cgit/slackbuilds/commit/?id=9514306f3d8dd25b6f0a41428c0652d06bf80477 > > but yes, it's out-dated Apologies, I must have been looking at the 14.1 build by mistake! Still, these fast moving browsers are a lot of work, and I don't begrudge anyone for not keeping up with them, but they're a hazard when they lag behind. -- Dave From atelszewski at gmail.com Wed Feb 1 13:15:59 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 1 Feb 2017 14:15:59 +0100 Subject: [Slackbuilds-users] qt5 and libinput Message-ID: <6b81022f-5ff1-eb97-9c47-f038b058facf@gmail.com> Hi, Why libinput has become hard dependency for qt5? Please ignore this message if you don't have the time to answer, it's only my curiosity. (Bcc-d maintainer). -- Best regards, Andrzej Telszewski From korgie at gmail.com Wed Feb 1 13:21:43 2017 From: korgie at gmail.com (korgman) Date: Wed, 1 Feb 2017 15:21:43 +0200 Subject: [Slackbuilds-users] Chromium build broken in 14.1 In-Reply-To: References: <5265b243-316d-a644-01fd-d803267aa814@osh.id.au> Message-ID: <26c85c7e-62b9-db20-7f4a-f83737fb1d34@gmail.com> On 01/02/2017 02:19 ??, JCA wrote: > Well, that's what is available in Slackbuilds for 14.1. I guess that it is not really maintained anymore :-( I that case, I just use 14.2 repository. My main system is still in 14.1 but I am using the SBo repository of 14.2. Ohhhh... the freedom of no-dependency-checking :p I found only mysql-workbench form 14.2 repo that does not work with 14.1 I suppose some other programs have problems with my hybrid - stupid - approach. So far so good though. I think the compile time is huge, so I also use alien build as mentioned. From andreas.guldstrand at gmail.com Wed Feb 1 13:23:34 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Wed, 1 Feb 2017 14:23:34 +0100 Subject: [Slackbuilds-users] qt5 and libinput In-Reply-To: <6b81022f-5ff1-eb97-9c47-f038b058facf@gmail.com> References: <6b81022f-5ff1-eb97-9c47-f038b058facf@gmail.com> Message-ID: Take a look at https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-January/018118.html On 1 February 2017 at 14:15, Andrzej Telszewski wrote: > Hi, > > Why libinput has become hard dependency for qt5? > Please ignore this message if you don't have the time to answer, it's only > my curiosity. > > (Bcc-d maintainer). > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From atelszewski at gmail.com Wed Feb 1 13:39:20 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 1 Feb 2017 14:39:20 +0100 Subject: [Slackbuilds-users] qt5 and libinput In-Reply-To: References: <6b81022f-5ff1-eb97-9c47-f038b058facf@gmail.com> Message-ID: On 01/02/17 14:23, Andreas Guldstrand wrote: > Take a look at https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-January/018118.html All clear now, thanks ;-) -- Best regards, Andrzej Telszewski From ekinakoglu at gmail.com Wed Feb 1 20:30:24 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Wed, 1 Feb 2017 23:30:24 +0300 Subject: [Slackbuilds-users] Updated tuxguitar.SlackBuild for tuxguitar version 1.4 Message-ID: <2627a4d5-d10a-d624-cfd8-ebc800b095d2@gmail.com> Dear all, Usually it is simply a version update in the SlackBuild script in order to create a Slackware package of the latest version of the related software. However, with TuxGuitar version 1.4, the process was a little bit cumbersome due to some large changes. However, I have managed to update the tuxguitar.SlackBuild script for TuxGuitar version 1.4. and I am sending you attached to this e-mail for your convenience. Erik, being the maintainer of TuxGuitar, could you please review my patch and check if you can provide the update for the SlackBuilds repository? Thank you for your concerns. Kind regards, Ekin P.S. The patch required for fixing the start-up script for version 1.2 is no longer necessary for version 1.4 of TuxGuitar. -------------- next part -------------- A non-text attachment was scrubbed... Name: tuxguitar.SlackBuild.patch Type: text/x-patch Size: 5478 bytes Desc: not available URL: From kingbeowulf at gmail.com Wed Feb 1 22:46:49 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 1 Feb 2017 14:46:49 -0800 Subject: [Slackbuilds-users] Updated tuxguitar.SlackBuild for tuxguitar version 1.4 In-Reply-To: <2627a4d5-d10a-d624-cfd8-ebc800b095d2@gmail.com> References: <2627a4d5-d10a-d624-cfd8-ebc800b095d2@gmail.com> Message-ID: <6aef572d-6050-154e-c528-76ab4b152b24@gmail.com> On 02/01/2017 12:30 PM, Ekin Akoglu wrote: ---snip--- > > Erik, being the maintainer of TuxGuitar, could you please review my > patch and check if you can provide the update for the SlackBuilds > repository? Thank you for your concerns. > --snip--- Also, looks like the web link needs to be updated to: http://www.tuxguitar.pw/ Since the existing one redirects to random spam -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From erik at slackbuilds.org Wed Feb 1 23:35:12 2017 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 1 Feb 2017 17:35:12 -0600 Subject: [Slackbuilds-users] Updated tuxguitar.SlackBuild for tuxguitar version 1.4 In-Reply-To: <2627a4d5-d10a-d624-cfd8-ebc800b095d2@gmail.com> References: <2627a4d5-d10a-d624-cfd8-ebc800b095d2@gmail.com> Message-ID: <20170201173512.68c5b0d4@shaggy.doo> On Wed, 1 Feb 2017 23:30:24 +0300 Ekin Akoglu wrote: > Erik, being the maintainer of TuxGuitar, could you please review my > patch and check if you can provide the update for the SlackBuilds > repository? Thank you for your concerns. If you are interested, please take over maintenance of TuxGuitar and submit an updated script. I don't use it and don't have time to review any patches for it. -- Erik From ekinakoglu at gmail.com Thu Feb 2 12:54:26 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Thu, 2 Feb 2017 15:54:26 +0300 Subject: [Slackbuilds-users] Updated tuxguitar.SlackBuild for tuxguitar version 1.4 In-Reply-To: <20170201173512.68c5b0d4@shaggy.doo> References: <2627a4d5-d10a-d624-cfd8-ebc800b095d2@gmail.com> <20170201173512.68c5b0d4@shaggy.doo> Message-ID: Dear Erik, I would gladly like to take over the maintenance of TuxGuitar because I use it frequently. However, it is my first time in maintaining a package. Could you please inform me about the steps to be taken for this transition? Best, Ekin On 02/02/2017 02:35 AM, Erik Hanson wrote: > On Wed, 1 Feb 2017 23:30:24 +0300 > Ekin Akoglu wrote: > >> Erik, being the maintainer of TuxGuitar, could you please review my >> patch and check if you can provide the update for the SlackBuilds >> repository? Thank you for your concerns. > If you are interested, please take over maintenance of TuxGuitar and > submit an updated script. I don't use it and don't have time to review > any patches for it. > > From atelszewski at gmail.com Thu Feb 2 12:56:12 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 2 Feb 2017 13:56:12 +0100 Subject: [Slackbuilds-users] Updated tuxguitar.SlackBuild for tuxguitar version 1.4 In-Reply-To: References: <2627a4d5-d10a-d624-cfd8-ebc800b095d2@gmail.com> <20170201173512.68c5b0d4@shaggy.doo> Message-ID: On 02/02/17 13:54, Ekin Akoglu wrote: > > I would gladly like to take over the maintenance of TuxGuitar because I > use it frequently. However, it is my first time in maintaining a > package. Could you please inform me about the steps to be taken for this > transition? Read the submission guidelines: https://slackbuilds.org/guidelines/ Then just send the updated version, mentioning in the comment that you got the permission to take over the SlackBuild from the previous maintainer. -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Thu Feb 2 19:54:46 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 2 Feb 2017 20:54:46 +0100 Subject: [Slackbuilds-users] hunspell-pl 20170128 update In-Reply-To: <9667b423-15d0-0bef-cdfa-fd887ef69c9a@gmail.com> References: <9667b423-15d0-0bef-cdfa-fd887ef69c9a@gmail.com> Message-ID: <8461fab9-715f-1211-4e7b-a3f18afa3c38@gmail.com> On 28/01/17 20:55, Andrzej Telszewski wrote: > Hi, > > The update to hunspell-pl > [https://slackbuilds.org/cgit/slackbuilds/commit/?id=11bc3f81e] uses the > upstream download URL. > > But the upstream delete the source as soon as they release newer version. > > Just to let you know ;-) > > (Bcc'd maintainer). > The download link has already expired ;-) -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Thu Feb 2 21:57:01 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 2 Feb 2017 16:57:01 -0500 Subject: [Slackbuilds-users] hunspell-pl 20170128 update In-Reply-To: <8461fab9-715f-1211-4e7b-a3f18afa3c38@gmail.com> References: <9667b423-15d0-0bef-cdfa-fd887ef69c9a@gmail.com> <8461fab9-715f-1211-4e7b-a3f18afa3c38@gmail.com> Message-ID: On 2/2/17, Andrzej Telszewski wrote: > The download link has already expired ;-) Has anyone contacted upstream and asked whether they could leave the old versions up for at least a little while? From chris.willing at iinet.net.au Thu Feb 2 22:26:16 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 3 Feb 2017 08:26:16 +1000 Subject: [Slackbuilds-users] hunspell-pl 20170128 update In-Reply-To: References: <9667b423-15d0-0bef-cdfa-fd887ef69c9a@gmail.com> <8461fab9-715f-1211-4e7b-a3f18afa3c38@gmail.com> Message-ID: <59bd171e-972d-7c26-1ba6-82de466b291c@iinet.net.au> On 03/02/17 07:57, B Watson wrote: > On 2/2/17, Andrzej Telszewski wrote: > >> The download link has already expired ;-) > > Has anyone contacted upstream and asked whether they could leave the > old versions up for at least a little while? > I have a similar problem with disappearing releases for live555. These days, most new releases are bug fixes and upstream doesn't want to support old, buggy releases. My solution has been to keep a copy on slackbuildsdirectlinks and use that as the DOWNLOAD url. chris From willysr at slackbuilds.org Sat Feb 4 00:26:16 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Feb 2017 07:26:16 +0700 Subject: [Slackbuilds-users] Updates - 20170204.1 Message-ID: Hi Folks first update on February brings several interesting changes: - Qt5 will have new dep: libinput for xcb plugin - Wine 2.0 is now available for both stable and staging - libreoffice 5.3.0 for binary repackaging and 5.2.5 for source compilation - letsencrypt warning should now be gone, after pyOpenSSL bump thanks to Kikinovak's investigation. - READMEs are now updated with user/group creation instructions thanks to Miguel De Anda and Andreas Guldstrand - ltm is now renamed to libtommath - tons of updates and new package additions i have decided to postpone bullet update since glPortal upstream is still working to make it compatible with latest bullet 2.86. make sure to grab the latest tarball from our repository after every public update for future submission. have fun Sat Feb 4 00:00:59 UTC 2017 academic/bibletime: Updated for version 2.11.0. academic/stellarium: Updated for version 0.15.1. accessibility/speech-dispatcher: Updated for version 0.8.6. audio/alsa-tools: Updated for version 1.1.3. audio/jack-tools: Updated for version 20170117. audio/mpd: Updated for version 0.20.4. audio/snd: Updated for version 17.1. audio/tuxguitar: Updated for version 1.4 + new maintainer. desktop/Alphacube-GTK: Fixed download, updated homepage. desktop/compton-conf: Update DEP. desktop/dunst: Update HOMEPAGE. desktop/lumina: Minor SlackBuild changes. desktop/moka-themes: Fixed download. desktop/neofetch: Updated for version 3.0.1. desktop/numix-icon-theme: Updated for version 0.3.875.201701252032. desktop/numix-sx-theme: Updated for version 20170128. desktop/obshutdown: Fixed download. desktop/screenkey: Updated for version 0.9. development/Catch: Updated for version 1.7.0. development/boost-di: Added (C++14 Dependency Injection Library). development/byacc: Updated for version 20170201. development/cc65: Updated for version 2.15_20170126. development/dpkg: Updated for version 1.18.20. development/facile: Updated for version 1.1.3. development/glm: Updated for version 0.9.8.4. development/google-webdesigner: Updated for version 1.7.0.1114. development/hhvm: Updated for version 3.15.5. development/jupyter-ipyleaflet: Fixed md5sum. development/neovim: Remove unused build parameter. development/p4: Updated for version 2016.2.1468155. development/p4d: Updated for version 2016.2.1468155. development/pkgconf: Updated for version 1.2.1. development/sauce: Added (C++ Dependency Injection Framework). development/sbcl: Updated for version 1.3.14. development/universal-ctags: Updated for version e2a1691. games/blobby2: Updated for version 1.0. games/bloodcm: Updated for version 12.2016. games/ds-models: Fix HOMEPAGE. games/dunelegacy: Updated for version 0.96.4. games/eduke32: Updated for version 20170123_6052. games/eduke32_shareware_data: Fix HOMEPAGE. games/extremetuxracer: Updated for version 0.7.4. games/frozen-bubble: Fix stripping of binaries. games/glPortal: Fix Build. games/mame: Updated for version 0.182. games/mednafen: Updated for version 0.9.41. games/openspades: Updated for version 0.1.0. games/vbam: Updated for version 2.0.0beta3. games/widelands: Updated for version build19. gis/cartopy: Updated for version 0.15.0. gis/gdal: Updated for version 2.1.3. gis/google-earth: Updated for version 7.1.8.3036. gis/postgis: Updated for version 2.3.2. gis/saga-gis: Updated for version 3.0.0. graphics/SweetHome3D: Updated for version 5.3. graphics/converseen: Updated for version 0.9.6.1. graphics/darktable: Updated for version 2.2.3. graphics/exact-image: Updated for version 0.9.2. graphics/gource: Added the new dependency SDL2_image. graphics/qcad: Updated for version 3.16.4.4 graphics/resynthesizer: Updated for version 2.0.1. haskell/haskell-cmark: Updated for version 0.5.4. haskell/haskell-cryptonite: Updated for version 0.21. haskell/haskell-graphviz: Updated for version 2999.18.1.2. haskell/haskell-memory: Updated for version 0.14.1. haskell/haskell-setlocale: Updated for version 1.0.0.4. haskell/haskell-stringsearch: Added (search for substrings). haskell/haskell-tagged: Updated for version 0.8.5. libraries/google-fruit: Added (dependency injection for C++). libraries/libcoap: Added (C-Implementation of CoAP). libraries/libdivecomputer: Updated for version 0.5.0 libraries/libechonest: Updated for version 2.3.1. libraries/libgit2-glib: Updated for version 0.24.4. libraries/libgit2: Updated for version 0.24.6. libraries/libtomcrypt: Added (portable cryptographic toolkit). libraries/libtommath: Added (LibTomMath library). libraries/libvirt-glib: Updated for version 1.0.0. libraries/libvirt-python: Updated for version 3.0.0. libraries/libvirt: Updated for version 3.0.0. libraries/live555: Updated for version 2017.01.26 libraries/ltm: Removed (renamed to libtommath). libraries/lua-lpeg: Updated for version 1.0.1. libraries/podofo: fix building against cppunit on x86 libraries/qt5: Update DEP and README. libraries/sqlpp11: Updated for version 0.45. libraries/vte3: Updated for version 0.44.3. misc/grc: Updated for version 1.10. multimedia/dvdauthor: Updated for version 0.7.2. multimedia/mlt: Updated for version 6.4.1. multimedia/opera-developer-ffmpeg-codecs: Updated for v 57.0.2970.0. multimedia/spotify: Updated for version 1.0.48. multimedia/winff: Fixed download links. network/PaleMoon: Updated for version 27.0.3. network/dovecot: Put group/user info in README. network/etherpad-lite: README changes, including user/group info. network/flexget: Updated for version 2.9.11. network/kismet: Updated for version 2016_07_R1. network/lighttpd2: Revise group/user info in README. network/lighttpd: Revise group/user info in README. network/mumble: Updated for version 1.2.19. network/murmur: Updated for version 1.2.19. network/nginx: Updated for version 1.10.3 network/openfire: Put group/user info in README. network/opera-developer: Updated for version 44.0.2487.0. network/opera: Updated for version 42.0.2393.517. network/psad: Added (Intrusion Detection and Log Analysis). network/qbittorrent-qt5: Update DEP. network/roger-router: README changes, including user/group info. network/sks-keyserver: Put group/user info in README. network/snort: Support non-ethernet decoders. network/telegram: Updated for version 1.0.5. network/tor-browser: Updated for version 6.5. network/youtube-dl: Updated for version 2017.01.28. office/LibreOffice: Updated for version 5.2.5.1 office/MasterPDFEditor: Updated for version 4.0.30. office/calibre: Updated for version 2.78.0 office/convertlit: Update REQUIRES. office/grisbi: Updated for version 1.0.1 office/htmldoc: Updated for version 1.8.29. office/hunspell-pl: Updated for version 20170131. office/libreoffice-helppack: Updated for version 5.3.0. office/libreoffice-langpack: Updated for version 5.3.0. office/libreoffice: Updated for version 5.3.0. office/multivalent-tool-pdf: Updated for version 0.8.5.20060102. office/tellico: Updated for version 2.3.12. perl/perl-Alien-SDL: Updated for version 1.446. perl/perl-Compress-Bzip2: Updated for version 2.25. perl/perl-EV: Added (perl interface to libev). perl/perl-ExtUtils-ModuleMaker: Updated for version 0.56. perl/perl-File-ShareDir: Updated for version 1.102. perl/perl-IO-Socket-SSL: Updated for version 2.044. perl/perl-IO-Socket-Socks: Added (perl module). perl/perl-Math-MPFR: Updated for version 3.35. perl/perl-Mojolicious: Updated for version 7.23 + Fix README. perl/perl-Net-DNS-Native: Added (non-blocking system DNS resolver). perl/perl-Sidef: Updated for version 2.35. perl/perl-Test-Most: Updated for version 0.34. perl/perl-Text-CSV: Updated for version 1.91. perl/perl-Tie-Simple: Updated for version 1.04. perl/perl-xml-twig: Updated for version 3.52. perl/perl-yaml: Updated for version 1.21. python/dulwich: Updated for version 0.16.3. python/psutil: Updated for version 5.1.0 python/pyOpenSSL: Updated for version 16.2.0. python/python-autobahn: Added (Websocket and WAMP for Python). python/python-klein: Added (micro-framework for web services). python/python-neovim: Added (Python client for Neovim). python/python-parsedatetime: Updated for version 2.2. python/python-txaio: Added (compatibility for Twisted/Trollius). python/sqlparse: Updated for version 0.2.2. python/tqdm: Updated for version 4.11.2. python/trezor: Updated for version 0.7.9.post1. python/zxcvbn-python: Added (password strength estimator). ruby/ruby-build: Updated for version 20170201. ruby/ruby-faraday: Minor SlackBuild changes. ruby/ruby-gist: Minor SlackBuild changes. ruby/ruby-haste: Updated for version 0.2.2. ruby/ruby-json: Minor SlackBuild changes. ruby/ruby-multipart-post: Minor SlackBuild changes. ruby/rubygem-bundler: Updated for version 1.14.3. ruby/rubygem-hpricot: Added (HTML parser). ruby/rubygem-mustache: Added (logic-free views). ruby/rubygem-rdiscount: Added (Markdown for Ruby). ruby/rubygem-ronn: Added (manual authoring tool). system/Iosevka: Updated for version 1.11.0. system/apache-activemq: Put group/user info in README. system/clamav: Put group/user info in README. system/etckeeper: Updated for version 1.18.6. system/fzf: Updated for version 0.16.3. system/jenkins: Put group/user info in README. system/kafka: Put group/user info in README. system/lbench: Updated for version 3.2. system/letsencrypt: Updated for version 0.10.2. system/man-db: Updated for version 2.7.6. system/man-pages-ja: Updated for version 20170115. system/mysql-utilities: Updated for version 1.6.5. system/nilfs-utils: Updated for version 2.2.6. system/nvme-cli: Added (NVMe management command line interface). system/pgbadger: Updated for version 9.1. system/posixovl: Added (POSIX Overlay Filesystem). system/qemu: Added qemu-bridge-helper setuid. system/salt: Updated for version 2016.11.2. system/tomb: Updated for version 2.3. system/wine-staging: Updated for version 2.0. system/wine: Updated for version 2.0. system/xf86-video-qxl: Updated for version 0.1.5, cleanups. system/zuluCrypt: Update DEP. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Feb 4 00:55:08 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Feb 2017 07:55:08 +0700 Subject: [Slackbuilds-users] letsencrypt users Message-ID: Hi, For letsencrypt users, you may want to install python-future since it's now required for python-parsedatetime and letsencrypt will complaint without it. I missed this dep in this public update, but it has been merged in my branch and will be merged to master in next public update. Sorry for this inconvenience -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From cary at SDF.ORG Sat Feb 4 02:41:39 2017 From: cary at SDF.ORG (Cary) Date: Sat, 4 Feb 2017 02:41:39 +0000 Subject: [Slackbuilds-users] heroku-client source fails checksum test Message-ID: <20170204024138.GA16532@SDF.ORG> Hi, all. The checksum for heroku-client does not match . Package built without any errors. ... heroku-client: heroku-client not found in /var/cache/sbopkg. --2017-02-03 18:34:13-- https://s3.amazonaws.com/assets.heroku.com/heroku-client/heroku-client.tgz Resolving s3.amazonaws.com (s3.amazonaws.com)... 52.216.81.43 Connecting to s3.amazonaws.com (s3.amazonaws.com)|52.216.81.43|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 1834517 (1.7M) [application/x-gtar] Saving to: ???heroku-client.tgz??? heroku-client.tgz 100%[===================>] 1.75M 406KB/s in 5.4s 2017-02-03 18:34:20 (330 KB/s) - ???heroku-client.tgz??? saved [1834517/1834517] Found heroku-client.tgz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for heroku-client.tgz ... FAILED! Expected: ed1595e7bf1005e333515251e8b75408 Found: 1c2843e228a04ca91639afc321a56169 -- cary at sdf.org SDF Public Access UNIX System - http://sdf.org From willysr at slackbuilds.org Sat Feb 4 04:27:01 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Feb 2017 11:27:01 +0700 Subject: [Slackbuilds-users] heroku-client source fails checksum test In-Reply-To: <20170204024138.GA16532@SDF.ORG> References: <20170204024138.GA16532@SDF.ORG> Message-ID: <94266c04-4382-568e-91d9-2e6cfc6476ca@slackbuilds.org> > The checksum for heroku-client does not match . > Package built without any errors. > ... > > heroku-client: > heroku-client not found in /var/cache/sbopkg. > --2017-02-03 18:34:13-- https://s3.amazonaws.com/assets.heroku.com/heroku-client/heroku-client.tgz > Resolving s3.amazonaws.com (s3.amazonaws.com)... 52.216.81.43 > Connecting to s3.amazonaws.com (s3.amazonaws.com)|52.216.81.43|:443... connected. > HTTP request sent, awaiting response... 200 OK > Length: 1834517 (1.7M) [application/x-gtar] > Saving to: ?heroku-client.tgz? > > heroku-client.tgz 100%[===================>] 1.75M 406KB/s in 5.4s > > 2017-02-03 18:34:20 (330 KB/s) - ?heroku-client.tgz? saved [1834517/1834517] > > Found heroku-client.tgz in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for heroku-client.tgz ... FAILED! > Expected: ed1595e7bf1005e333515251e8b75408 > Found: 1c2843e228a04ca91639afc321a56169 Thanks it's now fixed and hosted on sbodirectlinks to avoid checksum missmatch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Sat Feb 4 07:06:30 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 4 Feb 2017 08:06:30 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: Message-ID: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> Le 04/02/2017 ? 01:26, Willy Sudiarto Raharjo a ?crit : > - libreoffice 5.3.0 for binary repackaging and 5.2.5 for source compilation > - letsencrypt warning should now be gone, after pyOpenSSL bump thanks to > Kikinovak's investigation. Kiki Novak has another suggestion to add for LibreOffice. In my experience, users of LibreOffice want a *stable* application, not the latest and greatest riddled with bugs. I'd do the opposite: provide 5.3.0 for the adventurous folks who compile it, and stick with the hassle-free repackaged 5.2.5 for mere users. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Sat Feb 4 07:45:17 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Feb 2017 14:45:17 +0700 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> Message-ID: <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> > Kiki Novak has another suggestion to add for LibreOffice. In my > experience, users of LibreOffice want a *stable* application, not the > latest and greatest riddled with bugs. > > I'd do the opposite: provide 5.3.0 for the adventurous folks who compile > it, and stick with the hassle-free repackaged 5.2.5 for mere users. There's always pro and cons i'm using LO 5.3.0 since Beta release and i didn't see any major problem except for the missing icons on the new UI mode (which is disabled by default). On the other hand, some documents that wasn't properly opened in 5.2.x gets better in 5.3, so in this area, new version brings improvements needed by other people (mostly for those who are working in non-ODP formats). compiling LO takes time and sometimes can be very tricky, so most of the time, it will be a little bit behind the binary repackaging. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lists at osh.id.au Sat Feb 4 08:07:06 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 4 Feb 2017 18:07:06 +1000 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> Message-ID: <26baf66d-43ce-56b1-316e-51a45c88be4c@osh.id.au> On 02/04/2017 05:45 PM, Willy Sudiarto Raharjo wrote: >> Kiki Novak has another suggestion to add for LibreOffice. In my >> experience, users of LibreOffice want a *stable* application, not the >> latest and greatest riddled with bugs. >> >> I'd do the opposite: provide 5.3.0 for the adventurous folks who compile >> it, and stick with the hassle-free repackaged 5.2.5 for mere users. > > There's always pro and cons > i'm using LO 5.3.0 since Beta release and i didn't see any major problem > except for the missing icons on the new UI mode (which is disabled by > default). I've never come across any major bugs in the current (aka "fresh") release of LibreOffice myself, so I'm OK with whatever version the maintainer is willing to support. -- Dave From pessoal at profcavalheiro.com Sat Feb 4 10:51:37 2017 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Sat, 4 Feb 2017 08:51:37 -0200 Subject: [Slackbuilds-users] About VLC Message-ID: Guys, I've noticed a little something while trying to compile VLC: it will hit an error if you have qt5 installed. I only compiled it after uninstalling qt5. Please add this info on VLC REAMDE. -- Cordialmente, Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Sat Feb 4 11:46:56 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Sat, 4 Feb 2017 21:46:56 +1000 Subject: [Slackbuilds-users] About VLC In-Reply-To: References: Message-ID: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> On 02/04/2017 08:51 PM, Luis Cavalheiro wrote: > Guys, I've noticed a little something while trying to compile VLC: it > will hit an error if you have qt5 installed. I only compiled it after > uninstalling qt5. Please add this info on VLC REAMDE. Fails for me too with qt5 installed. I wonder if there's a way to force VLC to compile against qt4 in the SlackBuild? (Maintainer cc'd in). -- Dave From alik at ejik.org Sat Feb 4 13:26:45 2017 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 04 Feb 2017 16:26:45 +0300 Subject: [Slackbuilds-users] dpkg source is unavailable In-Reply-To: References: Message-ID: <1486214805.1428137.870173680.717E4BD8@webmail.messagingengine.com> Hello, > development/dpkg: Updated for version 1.18.20. dpkg is already 1.18.22 and 1.18.20 source is removed. Best regards, Alexander From willysr at slackbuilds.org Sat Feb 4 13:32:31 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Feb 2017 20:32:31 +0700 Subject: [Slackbuilds-users] dpkg source is unavailable In-Reply-To: <1486214805.1428137.870173680.717E4BD8@webmail.messagingengine.com> References: <1486214805.1428137.870173680.717E4BD8@webmail.messagingengine.com> Message-ID: >> development/dpkg: Updated for version 1.18.20. > > dpkg is already 1.18.22 and 1.18.20 source is removed. Edinaldo, perhaps it's better to host it at sbodirectlinks ? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From pessoal at profcavalheiro.com Sat Feb 4 13:55:22 2017 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Sat, 4 Feb 2017 11:55:22 -0200 Subject: [Slackbuilds-users] About VLC In-Reply-To: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> Message-ID: I found easier uninstall QT5 before compiling VLC and reinstall it after. But it would be interesting if exists a way to automatically force VLC to compile against QT4. Em 4 de fev de 2017 9:45 AM, "David O'Shaughnessy" escreveu: > On 02/04/2017 08:51 PM, Luis Cavalheiro wrote: > > Guys, I've noticed a little something while trying to compile VLC: it > > will hit an error if you have qt5 installed. I only compiled it after > > uninstalling qt5. Please add this info on VLC REAMDE. > > Fails for me too with qt5 installed. I wonder if there's a way to force > VLC to compile against qt4 in the SlackBuild? (Maintainer cc'd in). > > -- > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Sat Feb 4 14:14:03 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 5 Feb 2017 00:14:03 +1000 Subject: [Slackbuilds-users] About VLC In-Reply-To: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> Message-ID: On 04/02/17 21:46, David O'Shaughnessy wrote: > On 02/04/2017 08:51 PM, Luis Cavalheiro wrote: >> Guys, I've noticed a little something while trying to compile VLC: it >> will hit an error if you have qt5 installed. I only compiled it after >> uninstalling qt5. Please add this info on VLC REAMDE. > > Fails for me too with qt5 installed. I wonder if there's a way to force > VLC to compile against qt4 in the SlackBuild? (Maintainer cc'd in). > Yes, it seems there is such a way - a quick & dirty test on a regular machine has worked. Tomorrow I'll test it more fully in a clean (+qt5) build system before submitting. chris From willysr at slackbuilds.org Sat Feb 4 14:23:37 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Feb 2017 21:23:37 +0700 Subject: [Slackbuilds-users] About VLC In-Reply-To: References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> Message-ID: <3a1dea6f-eb1d-9e5c-89aa-1c572845508e@slackbuilds.org> >>> Guys, I've noticed a little something while trying to compile VLC: it >>> will hit an error if you have qt5 installed. I only compiled it after >>> uninstalling qt5. Please add this info on VLC REAMDE. >> >> Fails for me too with qt5 installed. I wonder if there's a way to force >> VLC to compile against qt4 in the SlackBuild? (Maintainer cc'd in). >> > Yes, it seems there is such a way - a quick & dirty test on a regular > machine has worked. Tomorrow I'll test it more fully in a clean (+qt5) > build system before submitting. I already build all deps on my VM here mind sharing the "dirty way" so i can test them here as well? Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ryanpcmcquen at member.fsf.org Sat Feb 4 14:47:56 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Sat, 4 Feb 2017 06:47:56 -0800 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <26baf66d-43ce-56b1-316e-51a45c88be4c@osh.id.au> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <26baf66d-43ce-56b1-316e-51a45c88be4c@osh.id.au> Message-ID: > I'd do the opposite: provide 5.3.0 for the adventurous folks who compile > it, and stick with the hassle-free repackaged 5.2.5 for mere users. I prefer the later version as well (5.3.0) and I am glad Willy keeps it up-to-date. -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sat Feb 4 14:47:33 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 4 Feb 2017 15:47:33 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> Message-ID: <36bbcfe3-06bb-50c1-0807-71f22ed791f1@gmail.com> On 04/02/17 08:06, Nicolas Kovacs wrote: > I'd do the opposite: provide 5.3.0 for the adventurous folks who compile > it, and stick with the hassle-free repackaged 5.2.5 for mere users. Those who compile, don't necessarily do it to have the latest/greatest. I just prefer to have the packages compiled on my own. -- Best regards, Andrzej Telszewski From info at microlinux.fr Sat Feb 4 15:48:08 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 4 Feb 2017 16:48:08 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> Message-ID: <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> Le 04/02/2017 ? 08:45, Willy Sudiarto Raharjo a ?crit : > There's always pro and cons > i'm using LO 5.3.0 since Beta release and i didn't see any major problem > except for the missing icons on the new UI mode (which is disabled by > default). Then I have a more general suggestion to make. Why not create two branches libreoffice-still and libreoffice-fresh, as other distributions (like Arch) do? Which should suit both conservative users (looking for stability) and those who feel more adventurous. And by doing so, we'd also be following upstream's policy. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Sat Feb 4 16:01:58 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 4 Feb 2017 23:01:58 +0700 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> Message-ID: <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> > Why not create two branches libreoffice-still and libreoffice-fresh, as > other distributions (like Arch) do? Which should suit both conservative > users (looking for stability) and those who feel more adventurous. And > by doing so, we'd also be following upstream's policy. Upstream offer choices and it's up to downstream/users to pick following your suggestions means we need 6 new packages -libreoffice-still -libreoffice-still-langpack -libreoffice-still-helppack -libreoffice-fresh -libreoffice-fresh-langpack -libreoffice-fresh-helppack plus we have LibreOffice for source compilation, so that makes it 7 packages in SBo. that's a big NO from me, but if you want to maintain libreoffice-still, feel free to submit :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From alik at ejik.org Sat Feb 4 16:24:35 2017 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 04 Feb 2017 19:24:35 +0300 Subject: [Slackbuilds-users] dpkg source is unavailable In-Reply-To: References: <1486214805.1428137.870173680.717E4BD8@webmail.messagingengine.com> Message-ID: <1486225475.1470871.870272456.463E8335@webmail.messagingengine.com> On Sat, Feb 4, 2017, at 16:32, Willy Sudiarto Raharjo wrote: > >> development/dpkg: Updated for version 1.18.20. > > > > dpkg is already 1.18.22 and 1.18.20 source is removed. > > Edinaldo, perhaps it's better to host it at sbodirectlinks ? Another option could be using something like this: http://snapshot.debian.org/archive/debian/20170128T211018Z/pool/main/d/dpkg/dpkg-dev_1.18.20_all.deb Alexander From edps.mundognu at gmail.com Sat Feb 4 18:28:45 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Sat, 04 Feb 2017 16:28:45 -0200 Subject: [Slackbuilds-users] dpkg source is unavailable Message-ID: Using Debian Snapshots Archives is a excellent alternative too! for any package... Thanks @Alexander! So... the last day of DPKG 1.18.20 in Debian Snapshots was in February 3 2017: http://snapshot.debian.org/archive/debian/20170201T032403Z/pool/main/d/dpkg/dpkg_1.18.20.tar.xz MD5SUM is the same. * Today, the most recent version of DPKG is 1.18.22: http://snapshot.debian.org/archive/debian/20170204T153245Z/pool/main/d/dpkg/dpkg_1.18.22.tar.xz MD5SUM: 1f32e3e272310df3def050eae6d6cd9f ** tested and installed in my system. I will submit this new update. Thanks to all! Edinaldo. From info at microlinux.fr Sat Feb 4 18:54:59 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 4 Feb 2017 19:54:59 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> Message-ID: <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> Le 04/02/2017 ? 17:01, Willy Sudiarto Raharjo a ?crit : > Upstream offer choices and it's up to downstream/users to pick > following your suggestions means we need 6 new packages > -libreoffice-still > -libreoffice-still-langpack > -libreoffice-still-helppack > -libreoffice-fresh > -libreoffice-fresh-langpack > -libreoffice-fresh-helppack These wouldn't exactly be new. More like almost identical copies. Let's say we're at version 5.2.4 (like we were a week ago). Now 5.2.5 comes out at the same time as 5.3.0. So all the package maintainer has to do is to copy the existing 5.2.4 package into 5.2.5-stable. It's almost the same package, the only thing that changes here is $PRGNAM, everything else stays the same. In the past, I've been bitten by bugs in OO and LO .0 releases. In production use, this means a client phoning you on a sunday morning and asking why the hell a closing bracket in LibreOffice gets rejected to a newline start, or similar quirks. Here's the description from LibreOffice.org: "Download LibreOffice... ... 5.3.0: The latest "fresh" version of LibreOffice, recommended for technology enthusiasts. ... 5.2.5: The mature "still" version of LibreOffice, recommended for enterprises." I don't know about you, but I'm all for "mature" in production use. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From ryanpcmcquen at member.fsf.org Sat Feb 4 19:00:05 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Sat, 4 Feb 2017 11:00:05 -0800 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> Message-ID: On Feb 4, 2017 10:56 AM, "Nicolas Kovacs" wrote: Le 04/02/2017 ? 17:01, Willy Sudiarto Raharjo a ?crit : > Upstream offer choices and it's up to downstream/users to pick > following your suggestions means we need 6 new packages > -libreoffice-still > -libreoffice-still-langpack > -libreoffice-still-helppack > -libreoffice-fresh > -libreoffice-fresh-langpack > -libreoffice-fresh-helppack These wouldn't exactly be new. More like almost identical copies. Let's say we're at version 5.2.4 (like we were a week ago). Now 5.2.5 comes out at the same time as 5.3.0. So all the package maintainer has to do is to copy the existing 5.2.4 package into 5.2.5-stable. It's almost the same package, the only thing that changes here is $PRGNAM, everything else stays the same. In the past, I've been bitten by bugs in OO and LO .0 releases. In production use, this means a client phoning you on a sunday morning and asking why the hell a closing bracket in LibreOffice gets rejected to a newline start, or similar quirks. SBo is not for your 'clients'. If you want to profit off of this, roll up your sleeves and make your own build. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sat Feb 4 19:26:59 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 4 Feb 2017 20:26:59 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> Message-ID: IMHO, versions of the SlackBuilds are decided by the maintainers. you can try persuade them, do any surveys you want but they have the last words. Matteo From baildon.research at googlemail.com Sat Feb 4 19:39:52 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 4 Feb 2017 19:39:52 +0000 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> Message-ID: > Let's say we're at version 5.2.4 (like we were a week ago). > > Now 5.2.5 comes out at the same time as 5.3.0. This is exactly what git is for. The 5.2.4 SlackBuild is still there ... and if you look at the history, so is 5.2.5. And even if 5.2.6 comes out next week, you can checkout the 5.2.5 SlackBuild and use VERSION= Cheers -D. From kingbeowulf at gmail.com Sat Feb 4 19:59:49 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 4 Feb 2017 11:59:49 -0800 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> Message-ID: <69375fcb-e636-7ce8-0b87-cb351989f55e@gmail.com> On 02/03/2017 11:06 PM, Nicolas Kovacs wrote: > Le 04/02/2017 ? 01:26, Willy Sudiarto Raharjo a ?crit : >> - libreoffice 5.3.0 for binary repackaging and 5.2.5 for source compilation >> - letsencrypt warning should now be gone, after pyOpenSSL bump thanks to >> Kikinovak's investigation. > > Kiki Novak has another suggestion to add for LibreOffice. In my > experience, users of LibreOffice want a *stable* application, not the > latest and greatest riddled with bugs. > > I'd do the opposite: provide 5.3.0 for the adventurous folks who compile > it, and stick with the hassle-free repackaged 5.2.5 for mere users. > 'Kiki' and others raise a few good points. Here are my 2 cents: Given Slackware's goal for, and, yes, reputation as, a stable, solid Linux distribution, then SBo should have that goal as well. There will always be those who dabble in -current and so treat Slackware as a "rolling release." That's fine. However, I think most of us rather prefer stability over wiz-bang newness. My preference, as a maintainer, is that SBo does not succumb to "version creep" and sticks with STABLE packages that are as bug free as possible given the nature of F/OSS. Since I use most of the packages I maintain, I do not need the hassle of constantly upgrading and troubleshooting some weird lib breakage. Bluntly: I've got shit to do. (This list had a discussion previously about how some maintainers are a bit "slow" to update so we do not need to re-hash that here.) My preference is to only upgrade to fix bugs or add vital functionality. In the case of LO, it may be a good idea to read AleinBOB's recent blog entry A solution to "newness" may be to have a branch of SBo-current that tracks Slackware-current. That way SBo-stable can be kept free of multiple versions of newer packages until we can work out the bugs and patches. Ok, I've ranted enough. Too much time one my hands lately.. -Ed. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Sat Feb 4 20:08:47 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 4 Feb 2017 21:08:47 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> Message-ID: Le 04/02/2017 ? 20:26, Matteo Bernardini a ?crit : > IMHO, versions of the SlackBuilds are decided by the maintainers. > > you can try persuade them, do any surveys you want but they have the last words. I know, Matteo. And this is the reason why I have my own package repo: http://www.microlinux.fr/microlinux/ It only seemed more coherent to me that someone running a stable version of Slackware (as SBo users are supposed to do) should also prefer software versions explicitly advertised as stable and mature. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From kingbeowulf at gmail.com Sat Feb 4 20:11:37 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 4 Feb 2017 12:11:37 -0800 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> Message-ID: On 02/04/2017 11:39 AM, David Spencer wrote: --- > This is exactly what git is for. The 5.2.4 SlackBuild is still there > ... and if you look at the history, so is 5.2.5. And even if 5.2.6 > comes out next week, you can checkout the 5.2.5 SlackBuild and use > VERSION= > > Cheers > -D. git may be a bit much for some novices who typically get the package script from the web site. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Sat Feb 4 20:16:55 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 4 Feb 2017 21:16:55 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> Message-ID: <395bab67-6398-2cbd-4c10-9c2feb9b2955@microlinux.fr> Le 04/02/2017 ? 20:00, Ryan P.C. McQuen a ?crit : > SBo is not for your 'clients'. If you want to profit off of this, roll > up your sleeves and make your own build. http://www.microlinux.fr/microlinux/desktop-14.2-source/xap/libreoffice/ What motivated my initial suggestion was something like: if my clients enjoy the stability of an application, then so will the casual user of SBo scripts. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From ryanpcmcquen at member.fsf.org Sat Feb 4 20:32:39 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Sat, 4 Feb 2017 12:32:39 -0800 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <395bab67-6398-2cbd-4c10-9c2feb9b2955@microlinux.fr> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> <395bab67-6398-2cbd-4c10-9c2feb9b2955@microlinux.fr> Message-ID: On Feb 4, 2017 12:17 PM, "Nicolas Kovacs" wrote: Le 04/02/2017 ? 20:00, Ryan P.C. McQuen a ?crit : > SBo is not for your 'clients'. If you want to profit off of this, roll > up your sleeves and make your own build. http://www.microlinux.fr/microlinux/desktop-14.2-source/xap/libreoffice/ What motivated my initial suggestion was something like: if my clients enjoy the stability of an application, then so will the casual user of SBo scripts. Slackware is not geared toward the casual user. Plenty of other distros are, though. -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Sat Feb 4 20:38:41 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 4 Feb 2017 21:38:41 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <281d2368-e34e-114d-1c52-a69cd3aec485@slackbuilds.org> <413f9f97-0095-fd57-49d0-72ab896efa82@microlinux.fr> <99adb97a-326b-438d-e7a6-6eccb0b53f29@slackbuilds.org> <718c4a91-6a6e-b0e1-059b-a882284b12ae@microlinux.fr> <395bab67-6398-2cbd-4c10-9c2feb9b2955@microlinux.fr> Message-ID: <420fe17d-7500-a6dc-d824-528010246178@microlinux.fr> Le 04/02/2017 ? 21:32, Ryan P.C. McQuen a ?crit : > > Slackware is not geared toward the casual user. Plenty of other distros > are, though. Silly me :o) -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From nuncestbibendum at excite.com Sat Feb 4 20:51:30 2017 From: nuncestbibendum at excite.com (Full Name) Date: Sat, 04 Feb 2017 15:51:30 -0500 Subject: [Slackbuilds-users] Updates - 20170204.1 Message-ID: <20170204155130.24511@web008.roc2.bluetie.com> > From: "King Beowulf" [kingbeowulf at gmail.com] > Date: 02/04/2017 03:00 PM > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Updates - 20170204.1 > > My preference, as a maintainer, is that SBo does not succumb to "version > creep" and sticks with STABLE packages that are as bug free as possible > given the nature of F/OSS. Another factor to bear in mind is the relative obsolescence of packages. I.e. a given Slackbuilds package's version might be such that another package that depends on it won't build. One could sensibly argue that, as long as that this latter package is not one in Slackbuilds, the problem is not Slackbuilds'. However, this would limit Slackbuilds' (and Slackware's) usefulness. There may be a middle, pragmatic way, between wanting to have the latest and greatest and strict conservatism. Such an approach would probably be more onerous on maintainers though. From chris.willing at iinet.net.au Sat Feb 4 23:37:17 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 5 Feb 2017 09:37:17 +1000 Subject: [Slackbuilds-users] About VLC In-Reply-To: <3a1dea6f-eb1d-9e5c-89aa-1c572845508e@slackbuilds.org> References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> <3a1dea6f-eb1d-9e5c-89aa-1c572845508e@slackbuilds.org> Message-ID: <109724ce-538c-0139-ea97-90b7b4a572d2@iinet.net.au> On 05/02/17 00:23, Willy Sudiarto Raharjo wrote: >>>> Guys, I've noticed a little something while trying to compile VLC: it >>>> will hit an error if you have qt5 installed. I only compiled it after >>>> uninstalling qt5. Please add this info on VLC REAMDE. >>> >>> Fails for me too with qt5 installed. I wonder if there's a way to force >>> VLC to compile against qt4 in the SlackBuild? (Maintainer cc'd in). >>> >> Yes, it seems there is such a way - a quick & dirty test on a regular >> machine has worked. Tomorrow I'll test it more fully in a clean (+qt5) >> build system before submitting. > > I already build all deps on my VM here > mind sharing the "dirty way" so i can test them here as well? > Sorry for the delay Willy, I just saw your email now. The quick & dirty method is to apply the attached patch, then add: --enable-qt=4 \ to the configure options. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: qt4-select.patch Type: text/x-patch Size: 2171 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Feb 5 00:05:05 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Feb 2017 07:05:05 +0700 Subject: [Slackbuilds-users] About VLC In-Reply-To: <109724ce-538c-0139-ea97-90b7b4a572d2@iinet.net.au> References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> <3a1dea6f-eb1d-9e5c-89aa-1c572845508e@slackbuilds.org> <109724ce-538c-0139-ea97-90b7b4a572d2@iinet.net.au> Message-ID: <734225b4-f7d0-684b-2cb8-52bef95f09bf@slackbuilds.org> > The quick & dirty method is to apply the attached patch, then add: > --enable-qt=4 \ > to the configure options. That did the trick :) it built nicely here -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From erik at slackbuilds.org Sun Feb 5 00:05:36 2017 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 4 Feb 2017 18:05:36 -0600 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <69375fcb-e636-7ce8-0b87-cb351989f55e@gmail.com> References: <15a9e475-fc5d-183f-71fe-5abe64be4156@microlinux.fr> <69375fcb-e636-7ce8-0b87-cb351989f55e@gmail.com> Message-ID: <20170204180536.5c56cfec@shaggy.doo> On Sat, 4 Feb 2017 11:59:49 -0800 King Beowulf wrote: > Given Slackware's goal for, and, yes, reputation as, a stable, solid > Linux distribution, then SBo should have that goal as well. There > will always be those who dabble in -current and so treat Slackware as > a "rolling release." That's fine. However, I think most of us rather > prefer stability over wiz-bang newness. The only goal has been to provide a large collection of quality-tested scripts. SBo is maintainer driven, it doesn't cater to what any portion of the audience wants. > My preference, as a maintainer, is that SBo does not succumb to > "version creep" and sticks with STABLE packages that are as bug free > as possible given the nature of F/OSS. Since I use most of the > packages I maintain, I do not need the hassle of constantly upgrading > and troubleshooting some weird lib breakage. No one is forcing you to update your scripts, you maintain them, you're free to do what you like. You're also free to not use other peoples' scripts if they don't meet your needs. Maybe it's easy to forget, but SBo isn't a small group of maintainers who write and care for all the scripts in the repository. There's something like 900+ maintainers. It isn't reasonable to enforce a rule of "only stable versions" on everyone, for a variety of reasons. Some software never releases as "stable", some stable releases are outdated, unusable, buggier, etc. than a beta or git branch. Individual maintainers get to decide what's stable, and the onus of support is on them. It's also not feasible for the admins to make sure everything being submitted falls under some measure of stability. For that reason alone the decision of what a maintainer wants to maintain needs to remain with them, and our involvement stops after making sure the scripts meet with quality guidelines. > A solution to "newness" may be to have a branch of SBo-current that > tracks Slackware-current. That way SBo-stable can be kept free of > multiple versions of newer packages until we can work out the bugs and > patches. This is not going to happen. Also, please stop referring to scripts as "packages", SBo does not provide packages. -- Erik From kingbeowulf at gmail.com Sun Feb 5 02:11:31 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 4 Feb 2017 18:11:31 -0800 Subject: [Slackbuilds-users] SweetHome3D-5.3 Message-ID: <9da88833-e2d5-0c5a-bc61-746f16672f90@gmail.com> I screwed up this one and it would be best to revert to the previous working version 5.2. I am currently testing 5.4 and it works except for the Nvidia proprietary drivers. The Nvidia java3d error is here: http://www.sweethome3d.com/support/forum/viewthread_thread,7269 The new script is here if anyone wished to help debug: http://www.linuxgalaxy.org/files/sbo-testing/14.2/SBo-archives/SweetHome3D.tar.gz Thanks -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Sun Feb 5 02:13:17 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 5 Feb 2017 12:13:17 +1000 Subject: [Slackbuilds-users] About VLC In-Reply-To: <734225b4-f7d0-684b-2cb8-52bef95f09bf@slackbuilds.org> References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> <3a1dea6f-eb1d-9e5c-89aa-1c572845508e@slackbuilds.org> <109724ce-538c-0139-ea97-90b7b4a572d2@iinet.net.au> <734225b4-f7d0-684b-2cb8-52bef95f09bf@slackbuilds.org> Message-ID: <302a7123-ca8f-e55f-8e8d-56615b752136@iinet.net.au> On 05/02/17 10:05, Willy Sudiarto Raharjo wrote: >> The quick & dirty method is to apply the attached patch, then add: >> --enable-qt=4 \ >> to the configure options. > > That did the trick :) > it built nicely here > Thanks for the confirmation Willy. Before I submit, I'm investigating whether the SlackBuild could optionally set --enable-qt=5. It works for the configuration step (appears to find correct version Qt libraries) but I had a problem during compilation. Before trying again I'm rebuilding my qt5 packages, then look at it a bit more deeply. In the meantime, anyone seeing the original problem (vlc not building in presence of qt5) could patch & configure just as you have done. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From awg at posteo.us Sun Feb 5 02:54:49 2017 From: awg at posteo.us (Arthur W. Green) Date: Sat, 4 Feb 2017 19:54:49 -0700 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: Message-ID: On 04/02/17 12:00, "Ryan P.C. McQuen" SBo is not for your 'clients'. If you want to profit off of this, roll > up your sleeves and make your own build. I believe he already does this, and I believe his only motivation for taking this to The List is because he believed his suggestion a useful one--I don't agree with implication that he has a conflict of interest. As a "casual user" who has gotten stung a few times by dot zero LO releases, I've perhaps a more rudimentary approach: I let the maintainer (in this case, Willy) upgrade as often as he wishes, and I simply avoid dot zero releases and others that seem too "fresh" for their own good. Yes, I prefer stability, but I believe it's ultimately my responsibility to read the release notes and make the determination to upgrade or not. Having more updates is therefore better than too few, imho. \\ Arthur From kingbeowulf at gmail.com Sun Feb 5 03:17:44 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 4 Feb 2017 19:17:44 -0800 Subject: [Slackbuilds-users] SweetHome3D-5.3 update and java3d fix (Nvidia) In-Reply-To: <9da88833-e2d5-0c5a-bc61-746f16672f90@gmail.com> References: <9da88833-e2d5-0c5a-bc61-746f16672f90@gmail.com> Message-ID: <73d8fcc6-c1fc-ce9b-518f-c2ce2cbaf788@gmail.com> On 02/04/2017 06:11 PM, King Beowulf wrote: > I screwed up this one and it would be best to revert to the previous > working version 5.2. I am currently testing 5.4 and it works except for > the Nvidia proprietary drivers. The Nvidia java3d error is here: > http://www.sweethome3d.com/support/forum/viewthread_thread,7269 > > The new script is here if anyone wished to help debug: > http://www.linuxgalaxy.org/files/sbo-testing/14.2/SBo-archives/SweetHome3D.tar.gz > Submitted new 5.4 version to fix script errors and add upstream's Nvidia Java3D "fix" to downgrade to Java3d-1.5.2 for Linux based distros. Sorry for the confusion. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From falsetti at clansco.org Sun Feb 5 04:41:10 2017 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Sun, 5 Feb 2017 05:41:10 +0100 Subject: [Slackbuilds-users] last grass and qgis Message-ID: <20170205054110.9dda3001a0655da338397a67@clansco.org> Hi, to be able to compile grass with libLAS you must have libproj.so.9 ln -s libproj.so.12.0.0 libproj.so.9 ENABLE="sqlite, gmath, unixODBC, libLAS" ./grass.SlackBuild and for qgis ln -s libgeos-3.6.1.so libgeos-3.6.0.so slpkg -s sbo qgis This compile but not sure it works fine I will test asap From slackbuilds at jaxartes.net Sun Feb 5 05:08:00 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 04 Feb 2017 21:08:00 -0800 Subject: [Slackbuilds-users] last grass and qgis In-Reply-To: <20170205054110.9dda3001a0655da338397a67@clansco.org> References: <20170205054110.9dda3001a0655da338397a67@clansco.org> Message-ID: <3978870.V63quLYFcl@wintermute> On Sunday, February 5, 2017 5:41:10 AM PST Fr?d?ric Falsetti wrote: > and for qgis > ln -s libgeos-3.6.1.so libgeos-3.6.0.so > slpkg -s sbo qgis This should not be necessary if you recompile everything that depends on geos (for example, gdal and libspatialite) before you try to build qgis. From akio at akionux.net Sun Feb 5 05:56:07 2017 From: akio at akionux.net (Akio Nishimura) Date: Sun, 5 Feb 2017 14:56:07 +0900 Subject: [Slackbuilds-users] graphics/pdf2svg: DOWNLOAD is no longer available Message-ID: <24e4d6d8-22fb-4e85-7a07-f92b17cc4dbd@akionux.net> Hi, DOWNLOAD of graphics/pdf2svg is no longer available. It should be DOWNLOAD="https://github.com/dawbarton/pdf2svg/archive/v0.2.2.tar.gz" -- Best regards, Akio From info at microlinux.fr Sun Feb 5 06:38:26 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sun, 5 Feb 2017 07:38:26 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: Message-ID: <5d7ba655-090b-7f54-18ca-58291b87cb14@microlinux.fr> Le 05/02/2017 ? 03:54, Arthur W. Green a ?crit : > I believe he already does this, and I believe his only motivation for > taking this to The List is because he believed his suggestion a useful > one--I don't agree with implication that he has a conflict of interest. Exactly. Though I have to confess that the idea of sleeping late every morning, selling a handful of SlackBuild scripts on the black market and then spending the rest of the day counting my money in the basement sounds appealing. :o) > > As a "casual user" who has gotten stung a few times by dot zero LO > releases, I've perhaps a more rudimentary approach: I let the maintainer > (in this case, Willy) upgrade as often as he wishes, and I simply avoid > dot zero releases and others that seem too "fresh" for their own good. > Yes, I prefer stability, but I believe it's ultimately my responsibility > to read the release notes and make the determination to upgrade or not. > Having more updates is therefore better than too few, imho. +1 Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From yalhcru at gmail.com Sun Feb 5 08:00:30 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 5 Feb 2017 03:00:30 -0500 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <5d7ba655-090b-7f54-18ca-58291b87cb14@microlinux.fr> References: <5d7ba655-090b-7f54-18ca-58291b87cb14@microlinux.fr> Message-ID: On 2/5/17, Nicolas Kovacs wrote: > Exactly. Though I have to confess that the idea of sleeping late every > morning, selling a handful of SlackBuild scripts on the black market and > then spending the rest of the day counting my money in the basement > sounds appealing. :o) Your ideas are intriguing to me, and I wish to subscribe to your newsletter! :) From willysr at slackbuilds.org Sun Feb 5 08:10:34 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Feb 2017 15:10:34 +0700 Subject: [Slackbuilds-users] graphics/pdf2svg: DOWNLOAD is no longer available In-Reply-To: <24e4d6d8-22fb-4e85-7a07-f92b17cc4dbd@akionux.net> References: <24e4d6d8-22fb-4e85-7a07-f92b17cc4dbd@akionux.net> Message-ID: > DOWNLOAD of graphics/pdf2svg is no longer available. > It should be > DOWNLOAD="https://github.com/dawbarton/pdf2svg/archive/v0.2.2.tar.gz" Thanks, fixed on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Sun Feb 5 08:35:06 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Sun, 5 Feb 2017 09:35:06 +0100 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: <5d7ba655-090b-7f54-18ca-58291b87cb14@microlinux.fr> Message-ID: Le 05/02/2017 ? 09:00, B Watson a ?crit : > Your ideas are intriguing to me, and I wish to subscribe to your > newsletter! Here you go: http://blog.microlinux.fr/slackware/ Though I guess I have to rethink my strategy, which is more in the line of "How to earn very little money while spending thousands of hours reading and writing documentation". :o) -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From ekinakoglu at gmail.com Sun Feb 5 11:38:54 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Sun, 5 Feb 2017 14:38:54 +0300 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: References: Message-ID: <596688c3-b3fc-e54a-5e6f-7112b4ef5e24@gmail.com> Hi, tuxguitar.patch is no longer needed for tuxguitar 1.4. Further, I did not submit it in my SlackBuild before the Feburary update, however, it appears on the SlackBuild page of tuxguitar as well as in the tarball of the SlackBuild. Could you please provide information about why it is still there? Maybe has it been overlooked? Thank you. Best, Ekin On 02/04/2017 03:26 AM, Willy Sudiarto Raharjo wrote: > Hi Folks > > first update on February brings several interesting changes: > - Qt5 will have new dep: libinput for xcb plugin > - Wine 2.0 is now available for both stable and staging > - libreoffice 5.3.0 for binary repackaging and 5.2.5 for source compilation > - letsencrypt warning should now be gone, after pyOpenSSL bump thanks to > Kikinovak's investigation. > - READMEs are now updated with user/group creation instructions thanks > to Miguel De Anda and Andreas Guldstrand > - ltm is now renamed to libtommath > - tons of updates and new package additions > > i have decided to postpone bullet update since glPortal upstream is > still working to make it compatible with latest bullet 2.86. > > make sure to grab the latest tarball from our repository after every > public update for future submission. > > > have fun > > > Sat Feb 4 00:00:59 UTC 2017 > academic/bibletime: Updated for version 2.11.0. > academic/stellarium: Updated for version 0.15.1. > accessibility/speech-dispatcher: Updated for version 0.8.6. > audio/alsa-tools: Updated for version 1.1.3. > audio/jack-tools: Updated for version 20170117. > audio/mpd: Updated for version 0.20.4. > audio/snd: Updated for version 17.1. > audio/tuxguitar: Updated for version 1.4 + new maintainer. > desktop/Alphacube-GTK: Fixed download, updated homepage. > desktop/compton-conf: Update DEP. > desktop/dunst: Update HOMEPAGE. > desktop/lumina: Minor SlackBuild changes. > desktop/moka-themes: Fixed download. > desktop/neofetch: Updated for version 3.0.1. > desktop/numix-icon-theme: Updated for version 0.3.875.201701252032. > desktop/numix-sx-theme: Updated for version 20170128. > desktop/obshutdown: Fixed download. > desktop/screenkey: Updated for version 0.9. > development/Catch: Updated for version 1.7.0. > development/boost-di: Added (C++14 Dependency Injection Library). > development/byacc: Updated for version 20170201. > development/cc65: Updated for version 2.15_20170126. > development/dpkg: Updated for version 1.18.20. > development/facile: Updated for version 1.1.3. > development/glm: Updated for version 0.9.8.4. > development/google-webdesigner: Updated for version 1.7.0.1114. > development/hhvm: Updated for version 3.15.5. > development/jupyter-ipyleaflet: Fixed md5sum. > development/neovim: Remove unused build parameter. > development/p4: Updated for version 2016.2.1468155. > development/p4d: Updated for version 2016.2.1468155. > development/pkgconf: Updated for version 1.2.1. > development/sauce: Added (C++ Dependency Injection Framework). > development/sbcl: Updated for version 1.3.14. > development/universal-ctags: Updated for version e2a1691. > games/blobby2: Updated for version 1.0. > games/bloodcm: Updated for version 12.2016. > games/ds-models: Fix HOMEPAGE. > games/dunelegacy: Updated for version 0.96.4. > games/eduke32: Updated for version 20170123_6052. > games/eduke32_shareware_data: Fix HOMEPAGE. > games/extremetuxracer: Updated for version 0.7.4. > games/frozen-bubble: Fix stripping of binaries. > games/glPortal: Fix Build. > games/mame: Updated for version 0.182. > games/mednafen: Updated for version 0.9.41. > games/openspades: Updated for version 0.1.0. > games/vbam: Updated for version 2.0.0beta3. > games/widelands: Updated for version build19. > gis/cartopy: Updated for version 0.15.0. > gis/gdal: Updated for version 2.1.3. > gis/google-earth: Updated for version 7.1.8.3036. > gis/postgis: Updated for version 2.3.2. > gis/saga-gis: Updated for version 3.0.0. > graphics/SweetHome3D: Updated for version 5.3. > graphics/converseen: Updated for version 0.9.6.1. > graphics/darktable: Updated for version 2.2.3. > graphics/exact-image: Updated for version 0.9.2. > graphics/gource: Added the new dependency SDL2_image. > graphics/qcad: Updated for version 3.16.4.4 > graphics/resynthesizer: Updated for version 2.0.1. > haskell/haskell-cmark: Updated for version 0.5.4. > haskell/haskell-cryptonite: Updated for version 0.21. > haskell/haskell-graphviz: Updated for version 2999.18.1.2. > haskell/haskell-memory: Updated for version 0.14.1. > haskell/haskell-setlocale: Updated for version 1.0.0.4. > haskell/haskell-stringsearch: Added (search for substrings). > haskell/haskell-tagged: Updated for version 0.8.5. > libraries/google-fruit: Added (dependency injection for C++). > libraries/libcoap: Added (C-Implementation of CoAP). > libraries/libdivecomputer: Updated for version 0.5.0 > libraries/libechonest: Updated for version 2.3.1. > libraries/libgit2-glib: Updated for version 0.24.4. > libraries/libgit2: Updated for version 0.24.6. > libraries/libtomcrypt: Added (portable cryptographic toolkit). > libraries/libtommath: Added (LibTomMath library). > libraries/libvirt-glib: Updated for version 1.0.0. > libraries/libvirt-python: Updated for version 3.0.0. > libraries/libvirt: Updated for version 3.0.0. > libraries/live555: Updated for version 2017.01.26 > libraries/ltm: Removed (renamed to libtommath). > libraries/lua-lpeg: Updated for version 1.0.1. > libraries/podofo: fix building against cppunit on x86 > libraries/qt5: Update DEP and README. > libraries/sqlpp11: Updated for version 0.45. > libraries/vte3: Updated for version 0.44.3. > misc/grc: Updated for version 1.10. > multimedia/dvdauthor: Updated for version 0.7.2. > multimedia/mlt: Updated for version 6.4.1. > multimedia/opera-developer-ffmpeg-codecs: Updated for v 57.0.2970.0. > multimedia/spotify: Updated for version 1.0.48. > multimedia/winff: Fixed download links. > network/PaleMoon: Updated for version 27.0.3. > network/dovecot: Put group/user info in README. > network/etherpad-lite: README changes, including user/group info. > network/flexget: Updated for version 2.9.11. > network/kismet: Updated for version 2016_07_R1. > network/lighttpd2: Revise group/user info in README. > network/lighttpd: Revise group/user info in README. > network/mumble: Updated for version 1.2.19. > network/murmur: Updated for version 1.2.19. > network/nginx: Updated for version 1.10.3 > network/openfire: Put group/user info in README. > network/opera-developer: Updated for version 44.0.2487.0. > network/opera: Updated for version 42.0.2393.517. > network/psad: Added (Intrusion Detection and Log Analysis). > network/qbittorrent-qt5: Update DEP. > network/roger-router: README changes, including user/group info. > network/sks-keyserver: Put group/user info in README. > network/snort: Support non-ethernet decoders. > network/telegram: Updated for version 1.0.5. > network/tor-browser: Updated for version 6.5. > network/youtube-dl: Updated for version 2017.01.28. > office/LibreOffice: Updated for version 5.2.5.1 > office/MasterPDFEditor: Updated for version 4.0.30. > office/calibre: Updated for version 2.78.0 > office/convertlit: Update REQUIRES. > office/grisbi: Updated for version 1.0.1 > office/htmldoc: Updated for version 1.8.29. > office/hunspell-pl: Updated for version 20170131. > office/libreoffice-helppack: Updated for version 5.3.0. > office/libreoffice-langpack: Updated for version 5.3.0. > office/libreoffice: Updated for version 5.3.0. > office/multivalent-tool-pdf: Updated for version 0.8.5.20060102. > office/tellico: Updated for version 2.3.12. > perl/perl-Alien-SDL: Updated for version 1.446. > perl/perl-Compress-Bzip2: Updated for version 2.25. > perl/perl-EV: Added (perl interface to libev). > perl/perl-ExtUtils-ModuleMaker: Updated for version 0.56. > perl/perl-File-ShareDir: Updated for version 1.102. > perl/perl-IO-Socket-SSL: Updated for version 2.044. > perl/perl-IO-Socket-Socks: Added (perl module). > perl/perl-Math-MPFR: Updated for version 3.35. > perl/perl-Mojolicious: Updated for version 7.23 + Fix README. > perl/perl-Net-DNS-Native: Added (non-blocking system DNS resolver). > perl/perl-Sidef: Updated for version 2.35. > perl/perl-Test-Most: Updated for version 0.34. > perl/perl-Text-CSV: Updated for version 1.91. > perl/perl-Tie-Simple: Updated for version 1.04. > perl/perl-xml-twig: Updated for version 3.52. > perl/perl-yaml: Updated for version 1.21. > python/dulwich: Updated for version 0.16.3. > python/psutil: Updated for version 5.1.0 > python/pyOpenSSL: Updated for version 16.2.0. > python/python-autobahn: Added (Websocket and WAMP for Python). > python/python-klein: Added (micro-framework for web services). > python/python-neovim: Added (Python client for Neovim). > python/python-parsedatetime: Updated for version 2.2. > python/python-txaio: Added (compatibility for Twisted/Trollius). > python/sqlparse: Updated for version 0.2.2. > python/tqdm: Updated for version 4.11.2. > python/trezor: Updated for version 0.7.9.post1. > python/zxcvbn-python: Added (password strength estimator). > ruby/ruby-build: Updated for version 20170201. > ruby/ruby-faraday: Minor SlackBuild changes. > ruby/ruby-gist: Minor SlackBuild changes. > ruby/ruby-haste: Updated for version 0.2.2. > ruby/ruby-json: Minor SlackBuild changes. > ruby/ruby-multipart-post: Minor SlackBuild changes. > ruby/rubygem-bundler: Updated for version 1.14.3. > ruby/rubygem-hpricot: Added (HTML parser). > ruby/rubygem-mustache: Added (logic-free views). > ruby/rubygem-rdiscount: Added (Markdown for Ruby). > ruby/rubygem-ronn: Added (manual authoring tool). > system/Iosevka: Updated for version 1.11.0. > system/apache-activemq: Put group/user info in README. > system/clamav: Put group/user info in README. > system/etckeeper: Updated for version 1.18.6. > system/fzf: Updated for version 0.16.3. > system/jenkins: Put group/user info in README. > system/kafka: Put group/user info in README. > system/lbench: Updated for version 3.2. > system/letsencrypt: Updated for version 0.10.2. > system/man-db: Updated for version 2.7.6. > system/man-pages-ja: Updated for version 20170115. > system/mysql-utilities: Updated for version 1.6.5. > system/nilfs-utils: Updated for version 2.2.6. > system/nvme-cli: Added (NVMe management command line interface). > system/pgbadger: Updated for version 9.1. > system/posixovl: Added (POSIX Overlay Filesystem). > system/qemu: Added qemu-bridge-helper setuid. > system/salt: Updated for version 2016.11.2. > system/tomb: Updated for version 2.3. > system/wine-staging: Updated for version 2.0. > system/wine: Updated for version 2.0. > system/xf86-video-qxl: Updated for version 0.1.5, cleanups. > system/zuluCrypt: Update DEP. > +--------------------------+ > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Sun Feb 5 13:48:27 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 5 Feb 2017 13:48:27 +0000 Subject: [Slackbuilds-users] Updates - 20170204.1 In-Reply-To: <596688c3-b3fc-e54a-5e6f-7112b4ef5e24@gmail.com> References: <596688c3-b3fc-e54a-5e6f-7112b4ef5e24@gmail.com> Message-ID: > tuxguitar.patch is no longer needed for tuxguitar 1.4. Further, I did not > submit it in my SlackBuild before the Feburary update, however, it appears > on the SlackBuild page of tuxguitar as well as in the tarball of the > SlackBuild. Could you please provide information about why it is still > there? Maybe has it been overlooked? Thank you. That was my mistake with a new version of the script I use for processing submissions, it's now fixed in my branch. Thanks for noticing it -D. From slackph at posteo.de Sun Feb 5 19:28:19 2017 From: slackph at posteo.de (Philip Lacroix) Date: Sun, 05 Feb 2017 20:28:19 +0100 Subject: [Slackbuilds-users] Glances 2.8 In-Reply-To: References: Message-ID: <849185dbe99f52024fb6e4ddd72935a1@posteo.de> Am 21.01.2017 19:09 schrieb Nicolas Kovacs: > Hi everybody, > > In the wake of the discussion about package updates, I thought I might > give you a little heads-up. > > SBo is currently providing Glances 2.5.1. Version 2.8 has just been > released by Nicolas Hennion. I gave it a spin, and it builds fine > against the same dependencies. A simple version bump does the trick > > It's worth the update, since it provides some nifty extra > functionality. Hi Niki, thanks for the heads-up. I'm the maintainer of the slackbuild for Glances, and I received Nicolas Hennion's update for 2.8 (I'm on his mailing list). I've been busy lately, and haven't updated my scripts for a few months, but I'm planning to catch up with upstream very soon. Cheers Philip From edps.mundognu at gmail.com Sun Feb 5 19:31:14 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Sun, 05 Feb 2017 17:31:14 -0200 Subject: [Slackbuilds-users] youtube-viewer (new dependency) Message-ID: Hi guys! here youtube-viewer not open without installation of perl-JSON (not listed as requirement): ~ ? gtk-youtube-viewer [Sun Feb 5 17:13:46 2017]: Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: /usr/local/lib/perl5 /usr/local/share/perl5 /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5 /usr/share/perl5 .) at /usr/share/perl5/vendor_perl/WWW/YoutubeViewer/ParseJSON.pm line 33. Can't locate JSON.pm in @INC (you may need to install the JSON module) (@INC contains: /usr/local/lib/perl5 /usr/local/share/perl5 /usr/lib/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib/perl5 /usr/share/perl5 .) at /usr/share/perl5/vendor_perl/WWW/YoutubeViewer/ParseJSON.pm line 33. After install perl-JSON works! in GUI or CLI mode :) https://i.imgur.com/QuZCVho.jpg Cheers! Edinaldo. From yalhcru at gmail.com Sun Feb 5 19:45:19 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 5 Feb 2017 14:45:19 -0500 Subject: [Slackbuilds-users] youtube-viewer (new dependency) In-Reply-To: References: Message-ID: On 2/5/17, Edinaldo wrote: > here youtube-viewer not open without installation of perl-JSON (not listed > as requirement): This is because of the perl-JSON-XS update from January 21. The older version of perl-JSON-XS had perl-JSON as a required dep, meaning perl-JSON didn't need to be listed in youtube-viewer's .info file because perl-JSON-XS was already there. I'll update youtube-viewer to work with the newer perl-JSON-XS, thanks for the report. From kingbeowulf at gmail.com Sun Feb 5 20:07:33 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 5 Feb 2017 12:07:33 -0800 Subject: [Slackbuilds-users] dvdauthor (0.7.2) unnecessary patch file Message-ID: <4b247e5c-998a-1fa3-591f-75b0de4aafdc@gmail.com> Admins I left an unnecessary config.patch in the dvdauthor submission. This patch is not required, or used, and can be removed. Thanks -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Sun Feb 5 21:57:29 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 6 Feb 2017 07:57:29 +1000 Subject: [Slackbuilds-users] About VLC In-Reply-To: <302a7123-ca8f-e55f-8e8d-56615b752136@iinet.net.au> References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> <3a1dea6f-eb1d-9e5c-89aa-1c572845508e@slackbuilds.org> <109724ce-538c-0139-ea97-90b7b4a572d2@iinet.net.au> <734225b4-f7d0-684b-2cb8-52bef95f09bf@slackbuilds.org> <302a7123-ca8f-e55f-8e8d-56615b752136@iinet.net.au> Message-ID: <728d56cb-0377-7221-1c98-fdec17b63534@iinet.net.au> On 05/02/17 12:13, Christoph Willing wrote: > On 05/02/17 10:05, Willy Sudiarto Raharjo wrote: >>> The quick & dirty method is to apply the attached patch, then add: >>> --enable-qt=4 \ >>> to the configure options. >> >> That did the trick :) >> it built nicely here >> > Thanks for the confirmation Willy. > > Before I submit, I'm investigating whether the SlackBuild could > optionally set --enable-qt=5. It works for the configuration step > (appears to find correct version Qt libraries) but I had a problem > during compilation. Before trying again I'm rebuilding my qt5 packages, > then look at it a bit more deeply. > > In the meantime, anyone seeing the original problem (vlc not building in > presence of qt5) could patch & configure just as you have done. > The change to force use of Qt4 has been pushed and should appear in the next round of updates. Thanks for raising the build problem when Qt5 is already installed. Use of Qt5 instead of Qt4 doesn't seem possible with the currently released code. It works with the newer vlc-3 but that isn't officially released yet and requires a more recent version of ffmpeg to be useful. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From pessoal at profcavalheiro.com Sun Feb 5 22:07:16 2017 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Sun, 5 Feb 2017 20:07:16 -0200 Subject: [Slackbuilds-users] About VLC In-Reply-To: <728d56cb-0377-7221-1c98-fdec17b63534@iinet.net.au> References: <56b98fe3-d193-cdfd-7e33-53a4ddb33c45@osh.id.au> <3a1dea6f-eb1d-9e5c-89aa-1c572845508e@slackbuilds.org> <109724ce-538c-0139-ea97-90b7b4a572d2@iinet.net.au> <734225b4-f7d0-684b-2cb8-52bef95f09bf@slackbuilds.org> <302a7123-ca8f-e55f-8e8d-56615b752136@iinet.net.au> <728d56cb-0377-7221-1c98-fdec17b63534@iinet.net.au> Message-ID: You're welcome, man Em 5 de fev de 2017 7:57 PM, "Christoph Willing" escreveu: > On 05/02/17 12:13, Christoph Willing wrote: > > On 05/02/17 10:05, Willy Sudiarto Raharjo wrote: > >>> The quick & dirty method is to apply the attached patch, then add: > >>> --enable-qt=4 \ > >>> to the configure options. > >> > >> That did the trick :) > >> it built nicely here > >> > > Thanks for the confirmation Willy. > > > > Before I submit, I'm investigating whether the SlackBuild could > > optionally set --enable-qt=5. It works for the configuration step > > (appears to find correct version Qt libraries) but I had a problem > > during compilation. Before trying again I'm rebuilding my qt5 packages, > > then look at it a bit more deeply. > > > > In the meantime, anyone seeing the original problem (vlc not building in > > presence of qt5) could patch & configure just as you have done. > > > The change to force use of Qt4 has been pushed and should appear in the > next round of updates. Thanks for raising the build problem when Qt5 is > already installed. > > Use of Qt5 instead of Qt4 doesn't seem possible with the currently > released code. It works with the newer vlc-3 but that isn't officially > released yet and requires a more recent version of ffmpeg to be useful. > > chris > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Feb 6 00:34:06 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 6 Feb 2017 07:34:06 +0700 Subject: [Slackbuilds-users] dvdauthor (0.7.2) unnecessary patch file In-Reply-To: <4b247e5c-998a-1fa3-591f-75b0de4aafdc@gmail.com> References: <4b247e5c-998a-1fa3-591f-75b0de4aafdc@gmail.com> Message-ID: <75a3a362-fcbc-ebd2-b420-a4014bd10c64@slackbuilds.org> > I left an unnecessary config.patch in the dvdauthor submission. This > patch is not required, or used, and can be removed. Done in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From andreas.guldstrand at gmail.com Mon Feb 6 01:29:29 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Mon, 6 Feb 2017 02:29:29 +0100 Subject: [Slackbuilds-users] Groups and users in README, was Re: kafka In-Reply-To: References: Message-ID: After going through the uid_gid.txt file, I found some more discrepancies: postfix amavisd-new ntop avahi VirtualBox openntpd nut znc exim policyd2 zabbix-server, zabbix-proxy, zabbix-agentd apache-tomcat cvsd DKIMproxy mediatomb quagga bitlbee pcsc-lite rplay bacula freeradius-server jabberd2 icecream spyke taskd dnscrypt-proxy icinga2 graphite-carbon seafile-server gitolite unbound dhcpy6d bareos oracle-xe ossec-agent, ossec-local, ossec-server spyke is especially fun, because in its README.SLACKWARE file, instead of suggesting to use its assigned uid/gid of 284/284, it suggests using 666/666 From kristofru at gmail.com Mon Feb 6 10:21:42 2017 From: kristofru at gmail.com (Chris Abela) Date: Mon, 6 Feb 2017 11:21:42 +0100 Subject: [Slackbuilds-users] letsencrypt users In-Reply-To: References: Message-ID: <0d1c4eec-3914-b83b-647e-bc3b9124f5dd@gmail.com> On 04/02/17 01:55, Willy Sudiarto Raharjo wrote: > Hi, > > For letsencrypt users, you may want to install python-future since it's > now required for python-parsedatetime and letsencrypt will complaint > without it. > > I missed this dep in this public update, but it has been merged in my > branch and will be merged to master in next public update. > > Sorry for this inconvenience > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > LibreOffice does not build if python-parsedatetime is installed. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From kristofru at gmail.com Mon Feb 6 10:25:46 2017 From: kristofru at gmail.com (Chris Abela) Date: Mon, 6 Feb 2017 11:25:46 +0100 Subject: [Slackbuilds-users] letsencrypt users In-Reply-To: <0d1c4eec-3914-b83b-647e-bc3b9124f5dd@gmail.com> References: <0d1c4eec-3914-b83b-647e-bc3b9124f5dd@gmail.com> Message-ID: On 06/02/17 11:21, Chris Abela wrote: > > > > On 04/02/17 01:55, Willy Sudiarto Raharjo wrote: >> Hi, >> >> For letsencrypt users, you may want to install python-future since it's >> now required for python-parsedatetime and letsencrypt will complaint >> without it. >> >> I missed this dep in this public update, but it has been merged in my >> branch and will be merged to master in next public update. >> >> Sorry for this inconvenience >> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ -https://slackbuilds.org/faq/ >> > LibreOffice does not build if python-parsedatetime is installed. > > Chris Correction: LibreOffice does not build if _python-future_ is installed. Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Mon Feb 6 11:55:09 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Mon, 6 Feb 2017 12:55:09 +0100 Subject: [Slackbuilds-users] letsencrypt users In-Reply-To: References: Message-ID: <05811d84-ea34-350e-af5f-240f2e9dbaa1@microlinux.fr> Le 04/02/2017 ? 01:55, Willy Sudiarto Raharjo a ?crit : > For letsencrypt users, you may want to install python-future since it's > now required for python-parsedatetime and letsencrypt will complaint > without it. > > I missed this dep in this public update, but it has been merged in my > branch and will be merged to master in next public update. Has this new dependency been introduced with python-parsedatetime 2.2? I have 2.1 installed on my main server without python-future, and letsencrypt works perfectly. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From chris.willing at iinet.net.au Mon Feb 6 12:47:11 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 6 Feb 2017 22:47:11 +1000 Subject: [Slackbuilds-users] letsencrypt users In-Reply-To: References: <0d1c4eec-3914-b83b-647e-bc3b9124f5dd@gmail.com> Message-ID: <98808b4d-8c4d-7d6e-73f1-8375be041ac7@iinet.net.au> On 06/02/17 20:25, Chris Abela wrote: > > > On 06/02/17 11:21, Chris Abela wrote: >> >> >> >> On 04/02/17 01:55, Willy Sudiarto Raharjo wrote: >>> Hi, >>> >>> For letsencrypt users, you may want to install python-future since it's >>> now required for python-parsedatetime and letsencrypt will complaint >>> without it. >>> >>> I missed this dep in this public update, but it has been merged in my >>> branch and will be merged to master in next public update. >>> >>> Sorry for this inconvenience >>> >>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> LibreOffice does not build if python-parsedatetime is installed. >> >> Chris > > Correction: > > LibreOffice does not build if _python-future_ is installed. > Is there anything else special about your setup? I just built the latest LibreOffice without problems in a clean VM with both python-parsedatetime and python-future installed. I used the SlackBuild in the ready queue (https://slackbuilds.org/cgit/slackbuilds/commit/?id=dc30b2fe6) which is mostly just a version update. chris From willysr at slackbuilds.org Mon Feb 6 13:04:42 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 6 Feb 2017 20:04:42 +0700 Subject: [Slackbuilds-users] letsencrypt users In-Reply-To: <05811d84-ea34-350e-af5f-240f2e9dbaa1@microlinux.fr> References: <05811d84-ea34-350e-af5f-240f2e9dbaa1@microlinux.fr> Message-ID: <96adb3e6-d814-d013-c823-b4460011c64b@slackbuilds.org> >> I missed this dep in this public update, but it has been merged in my >> branch and will be merged to master in next public update. > > Has this new dependency been introduced with python-parsedatetime 2.2? I > have 2.1 installed on my main server without python-future, and > letsencrypt works perfectly. it appears it's part of python-parsedatetime 2.2 and i missed them since it's a run-time dep. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Mon Feb 6 19:04:15 2017 From: yalhcru at gmail.com (B Watson) Date: Mon, 6 Feb 2017 14:04:15 -0500 Subject: [Slackbuilds-users] Fwd: zdoom SlackBuild In-Reply-To: References: Message-ID: Sent this to the zdoom maintainer a few days ago, received no response. Sending it to the list in case he's monitoring it. ---------- Forwarded message ---------- From: B Watson Date: Thu, 2 Feb 2017 17:15:46 -0500 Subject: zdoom SlackBuild To: pablosantamaria at gmail.com Looks like zdoom development has ended, https://zdoom.org/News says: "I am hereby eschewing further ZDoom development. There will be no future releases." So, could you update your build to the last version, 2.8.1? It's been 4.5 years since you last updated it (in July of 2012). After updating to 2.8.1 it should never need another version update... From yalhcru at gmail.com Mon Feb 6 19:06:05 2017 From: yalhcru at gmail.com (B Watson) Date: Mon, 6 Feb 2017 14:06:05 -0500 Subject: [Slackbuilds-users] Fwd: reiser4progs and libaal getting long in the tooth In-Reply-To: References: Message-ID: Sent this out last week, got no response. Sending to the list in case the maintainer's monitoring it. ---------- Forwarded message ---------- From: B Watson Date: Tue, 31 Jan 2017 14:19:03 -0500 Subject: reiser4progs and libaal getting long in the tooth To: kerickson at lavabit.com These 2 packages on SBo have you listed as maintainer. libaal is now up to version 1.0.6 (updated in 2014), and reiser4progs is at 1.10 (updated in late 2015). Any chance you'll update your builds? I ask because I'm trying to build partclone with support for reiser 4, and it needs a newer reiser4progs (or a patch for the old one). Also HOMEPAGE in both .info files should be updated to https://reiser4.wiki.kernel.org/index.php/Reiser4progs or maybe https://reiser4.wiki.kernel.org/index.php/Main_Page From ryanpcmcquen at member.fsf.org Mon Feb 6 19:19:25 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Mon, 6 Feb 2017 11:19:25 -0800 Subject: [Slackbuilds-users] Fwd: zdoom SlackBuild In-Reply-To: References: Message-ID: > So, could you update your build to the last version, 2.8.1? It's been > 4.5 years since you last updated it (in July of 2012). After updating > to 2.8.1 it should never need another version update... Added this to SBo direct links, in case the site goes down: https://sourceforge.net/projects/slackbuildsdirectlinks/files/zdoom/zdoom-2.8.1-src.7z -- - Ryan [ryanpcmcquen.org] From duncan_roe at acslink.net.au Mon Feb 6 23:05:31 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Tue, 7 Feb 2017 10:05:31 +1100 Subject: [Slackbuilds-users] Need some gids and uids please Message-ID: <20170206230531.GA11226@dimstar.local.net> Hi admins, Having used it for years, I'm putting together a SlackBuild for qmail. Qmail needs 2 groups and 7 users: can you allocate them from the pool please? Groups are qmail & nofiles Users are alias & qmail{d,l,p,q,r,s} (i.e. qmailq, qmaill (ell) &c.) I have noted the recent correspondence regarding uids, gids & README; but I was planning to have doinst.sh create them if they didn't exist. Cheers ... Duncan. From willysr at slackbuilds.org Tue Feb 7 00:39:13 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Feb 2017 07:39:13 +0700 Subject: [Slackbuilds-users] Need some gids and uids please In-Reply-To: <20170206230531.GA11226@dimstar.local.net> References: <20170206230531.GA11226@dimstar.local.net> Message-ID: > Having used it for years, I'm putting together a SlackBuild for qmail. > > Qmail needs 2 groups and 7 users: can you allocate them from the pool please? > > Groups are qmail & nofiles > > Users are alias & qmail{d,l,p,q,r,s} (i.e. qmailq, qmaill (ell) &c.) > > I have noted the recent correspondence regarding uids, gids & README; but I > was planning to have doinst.sh create them if they didn't exist. please review the last entry in the uid_gid.txt -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Tue Feb 7 03:40:55 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 7 Feb 2017 03:40:55 +0000 Subject: [Slackbuilds-users] PyQt5 requirements Message-ID: Hi, I asked the maintainer of PyQt5 this question a couple weeks ago but didn't get a response, so I thought I would ask the group. PyQt5 lists qt5-webkit as a required dependency, but it builds and runs (at least for my use case) fine without it. Is there a reason why it is listed as a requirement? I was under the impression that requirements should be needed either to build or run the software. In the case of qt5-webkit, it also takes a long time to compile, so for most people it would be preferred not to install it if not needed. Regards, Dan From duncan_roe at acslink.net.au Tue Feb 7 04:00:41 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Tue, 7 Feb 2017 15:00:41 +1100 Subject: [Slackbuilds-users] Need some gids and uids please (re-send) Message-ID: <20170207040040.GA24708@dimstar.local.net> Hi admins, Having used it for years, I'm putting together a SlackBuild for qmail. Qmail needs 2 groups and 7 users: can you allocate them from the pool please? Groups are qmail & nofiles Users are alias & qmail{d,l,p,q,r,s} (i.e. qmailq, qmaill (ell) &c.) I have noted the recent correspondence regarding uids, gids & README; but I was planning to have doinst.sh create them if they didn't exist. Cheers ... Duncan. PS thought I sent this already but never saw it in the list - D From yalhcru at gmail.com Tue Feb 7 04:25:47 2017 From: yalhcru at gmail.com (B Watson) Date: Mon, 6 Feb 2017 23:25:47 -0500 Subject: [Slackbuilds-users] Need some gids and uids please (re-send) In-Reply-To: <20170207040040.GA24708@dimstar.local.net> References: <20170207040040.GA24708@dimstar.local.net> Message-ID: On 2/6/17, Duncan Roe wrote: > > PS thought I sent this already but never saw it in the list - D You did. By default this mailing list doesn't send a copy of the message back to the sender. Think it's possible to change that via web interface, you should have gotten the URL when you subscribed to the list. From duncan_roe at acslink.net.au Tue Feb 7 06:15:57 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Tue, 7 Feb 2017 17:15:57 +1100 Subject: [Slackbuilds-users] Need some gids and uids please In-Reply-To: References: <20170206230531.GA11226@dimstar.local.net> Message-ID: <20170207061557.GC24708@dimstar.local.net> On Tue, Feb 07, 2017 at 07:39:13AM +0700, Willy Sudiarto Raharjo wrote: > > Having used it for years, I'm putting together a SlackBuild for qmail. > > > > Qmail needs 2 groups and 7 users: can you allocate them from the pool please? > > > > Groups are qmail & nofiles > > > > Users are alias & qmail{d,l,p,q,r,s} (i.e. qmailq, qmaill (ell) &c.) > > > > I have noted the recent correspondence regarding uids, gids & README; but I > > was planning to have doinst.sh create them if they didn't exist. > > please review the last entry in the uid_gid.txt > > > -- > Willy Sudiarto Raharjo > Thanks Willy. All the users are either in group qmail or nofiles, so gids 339 - 345 are unused. The list could look like: User: alias UID: 339 GID: 340 qmaild UID: 340 GID: 340 qmaill UID: 341 GID: 340 qmailp UID: 342 GID: 340 qmailq UID: 343 GID: 339 qmailr UID: 344 GID: 339 qmails UID: 345 GID: 339 Group: qmail GID: 339 nofiles GID: 340 Cheers ... Duncan. From willysr at slackbuilds.org Tue Feb 7 08:14:12 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Feb 2017 15:14:12 +0700 Subject: [Slackbuilds-users] Need some gids and uids please In-Reply-To: <20170207061557.GC24708@dimstar.local.net> References: <20170206230531.GA11226@dimstar.local.net> <20170207061557.GC24708@dimstar.local.net> Message-ID: <7640dc85-4089-b927-923e-6a8898742527@slackbuilds.org> > All the users are either in group qmail or nofiles, so gids 339 - 345 are > unused. The list could look like: > > User: alias UID: 339 GID: 340 > qmaild UID: 340 GID: 340 > qmaill UID: 341 GID: 340 > qmailp UID: 342 GID: 340 > qmailq UID: 343 GID: 339 > qmailr UID: 344 GID: 339 > qmails UID: 345 GID: 339 > Group: qmail GID: 339 > nofiles GID: 340 Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Tue Feb 7 08:18:44 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 7 Feb 2017 18:18:44 +1000 Subject: [Slackbuilds-users] PyQt5 requirements In-Reply-To: References: Message-ID: On 07/02/17 13:40, Daniel Prosser wrote: > Hi, > > I asked the maintainer of PyQt5 this question a couple weeks ago but > didn't get a response, so I thought I would ask the group. PyQt5 lists > qt5-webkit as a required dependency, but it builds and runs (at least > for my use case) fine without it. Is there a reason why it is listed as > a requirement? I was under the impression that requirements should be > needed either to build or run the software. I think that statement should be something more like: "requirements should be needed to build or run the software so that it has some level of usefulness" SBo SlackBuilds and packages generally (as far as I know) don't aim to be minimalist. They don't aim to provide the barest possible pieces of software with as few requirements as possible. The resulting software needs to provide some amount utility, not just exist as an example of how few requirements it needs. The level of usefulness is decided by the maintainer. In this case it appears the maintainer believes qt5-webkit is needed to make the built software useful - to them anyway. > In the case of qt5-webkit, > it also takes a long time to compile, so for most people it would be > preferred not to install it if not needed. > The fact that something is not useful (and time consuming, in this case) to you doesn't necessarily mean that "most people" feel the same way (or differently for that matter). If you don't need it, just leave it out. chris From matteo.bernardini at gmail.com Tue Feb 7 08:23:29 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 7 Feb 2017 09:23:29 +0100 Subject: [Slackbuilds-users] PyQt5 requirements In-Reply-To: References: Message-ID: 2017-02-07 9:18 GMT+01:00 Christoph Willing : > On 07/02/17 13:40, Daniel Prosser wrote: >> Hi, >> >> I asked the maintainer of PyQt5 this question a couple weeks ago but >> didn't get a response, so I thought I would ask the group. PyQt5 lists >> qt5-webkit as a required dependency, but it builds and runs (at least >> for my use case) fine without it. Is there a reason why it is listed as >> a requirement? I was under the impression that requirements should be >> needed either to build or run the software. > > I think that statement should be something more like: > "requirements should be needed to build or run the software > so that it has some level of usefulness" > > SBo SlackBuilds and packages generally (as far as I know) don't aim to > be minimalist. They don't aim to provide the barest possible pieces of > software with as few requirements as possible. The resulting software > needs to provide some amount utility, not just exist as an example of > how few requirements it needs. > > The level of usefulness is decided by the maintainer. In this case it > appears the maintainer believes qt5-webkit is needed to make the built > software useful - to them anyway. > >> In the case of qt5-webkit, >> it also takes a long time to compile, so for most people it would be >> preferred not to install it if not needed. >> > The fact that something is not useful (and time consuming, in this case) > to you doesn't necessarily mean that "most people" feel the same way (or > differently for that matter). If you don't need it, just leave it out. Hi Daniel, last time I tried if you didn't build PyQt5 against qt5-webkit calibre, that depends on PyQt5, didn't build at all. Matteo From sombragris at sombragris.org Tue Feb 7 10:38:00 2017 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Tue, 7 Feb 2017 07:38:00 -0300 Subject: [Slackbuilds-users] Problems building neofetch Message-ID: Using Slack64-current but this is something that could be seen in any Slack version. After last Saturday (Feb 04 2017) updates, neofetch cannot be built. This is because there is a mismatch between the version number of the software (3.0.1) and the tarball itself (3.0). I worked around this by editing the SlackBuild. My changes/additions are marked as (+++). I added a new variable $TARID: > PRGNAM=neofetch > VERSION=${VERSION:-3.0.1} > BUILD=${BUILD:-1} > TAG=${TAG:-_SBo} > +++ TARID=${TARID:-3.0} And then modifying the tarball extraction line: > rm -rf $PKG > mkdir -p $TMP $PKG $OUTPUT > cd $TMP > rm -rf $PRGNAM-$VERSION > +++ tar xvf $CWD/$PRGNAM-$TARID.tar.?z* > cd $PRGNAM-$VERSION > chmod 644 $DOCS And that's it. Please don't ask me to submit a patch. The patch commandline syntax is something I cannot master no matter how much I try. ;) Regards, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Tue Feb 7 11:05:47 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 7 Feb 2017 21:05:47 +1000 Subject: [Slackbuilds-users] Problems building neofetch In-Reply-To: References: Message-ID: <545c1a18-2965-653d-f14d-ab01a7121364@iinet.net.au> On 07/02/17 20:38, Eduardo Sanchez wrote: > Using Slack64-current but this is something that could be seen in any > Slack version. > > After last Saturday (Feb 04 2017) updates, neofetch cannot be built. > > This is because there is a mismatch between the version number of the > software (3.0.1) and the tarball itself (3.0). Looks like a typo in the DOWNLOAD url. It should be: https://github.com/dylanaraps/neofetch/archive/3.0.1/neofetch-3.0.1.tar.gz (not https://github.com/dylanaraps/neofetch/archive/3.0.1/neofetch-3.0.tar.gz) chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From sombragris at sombragris.org Tue Feb 7 11:45:46 2017 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Tue, 7 Feb 2017 08:45:46 -0300 Subject: [Slackbuilds-users] Problems building neofetch In-Reply-To: <20170207073800.06baaae6@loli.sombragris.org> References: <20170207073800.06baaae6@loli.sombragris.org> Message-ID: Well, it's a typo or some kind of mismatch, but it's upstream. The tarball is identified as 3.0 but upon uncompressing the directory carries the 3.0.1 version. Eduardo On 07/02/17 20:38, Eduardo Sanchez wrote: > > Using Slack64-current but this is something that could be seen in > > any Slack version. > > > > After last Saturday (Feb 04 2017) updates, neofetch cannot be built. > > > > This is because there is a mismatch between the version number of > > the software (3.0.1) and the tarball itself (3.0). > > Looks like a typo in the DOWNLOAD url. It should be: > > https://github.com/dylanaraps/neofetch/archive/3.0.1/neofetch-3.0.1.tar.gz > > (not > https://github.com/dylanaraps/neofetch/archive/3.0.1/neofetch-3.0.tar.gz) > > chris -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From andreas.guldstrand at gmail.com Tue Feb 7 12:01:36 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Tue, 7 Feb 2017 13:01:36 +0100 Subject: [Slackbuilds-users] Problems building neofetch In-Reply-To: References: <20170207073800.06baaae6@loli.sombragris.org> Message-ID: On 7 February 2017 at 12:45, Eduardo Sanchez wrote: > Well, it's a typo or some kind of mismatch, but it's upstream. The > tarball is identified as 3.0 but upon uncompressing the directory > carries the 3.0.1 version. No, it's just as Christoph said, it's the link that needs changing. Github links to tarballs like that are made up of 3 parts (at least). The first part is https://github.com/dylanaraps/neofetch/archive/3.0.1/ which identifies exactly _what_ is being downloaded, the second and third parts are, in this case neofetch-3.0.tar.gz which identifies the filename and the format the download will have. Thus, if you just change that part to neofetch-3.0.1.tar.gz none of the TARID stuff is necessary. From baildon.research at googlemail.com Tue Feb 7 12:01:47 2017 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 7 Feb 2017 12:01:47 +0000 Subject: [Slackbuilds-users] Problems building neofetch In-Reply-To: References: <20170207073800.06baaae6@loli.sombragris.org> Message-ID: Sorry I missed this problem -- thanks to both Eduardo and Chris for the report and the fix. I've pushed it to my branch and ivt will be in the next public update. > Well, it's a typo or some kind of mismatch, but it's upstream. The > tarball is identified as 3.0 but upon uncompressing the directory > carries the 3.0.1 version. Because of the way Github creates tarballs, you could download https://github.com/dylanaraps/neofetch/archive/3.0.1/thanks_eduardo_and_chris.tar.gz and it would still contain the same 3.0.1 version with the correct md5sum :) Thanks again -D. From dpross1100 at msn.com Tue Feb 7 12:33:53 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 7 Feb 2017 12:33:53 +0000 Subject: [Slackbuilds-users] PyQt5 requirements In-Reply-To: References: Message-ID: Chris and Matteo, Thanks for the replies. That makes sense. The question was more to clarify my own understanding of what constitutes a requirement, which I guess was mistaken or incomplete. Dan On Tue, Feb 07, 2017 at 09:23:29AM +0100, Matteo Bernardini wrote: > 2017-02-07 9:18 GMT+01:00 Christoph Willing : > > On 07/02/17 13:40, Daniel Prosser wrote: > >> Hi, > >> > >> I asked the maintainer of PyQt5 this question a couple weeks ago but > >> didn't get a response, so I thought I would ask the group. PyQt5 lists > >> qt5-webkit as a required dependency, but it builds and runs (at least > >> for my use case) fine without it. Is there a reason why it is listed as > >> a requirement? I was under the impression that requirements should be > >> needed either to build or run the software. > > > > I think that statement should be something more like: > > "requirements should be needed to build or run the software > > so that it has some level of usefulness" > > > > SBo SlackBuilds and packages generally (as far as I know) don't aim to > > be minimalist. They don't aim to provide the barest possible pieces of > > software with as few requirements as possible. The resulting software > > needs to provide some amount utility, not just exist as an example of > > how few requirements it needs. > > > > The level of usefulness is decided by the maintainer. In this case it > > appears the maintainer believes qt5-webkit is needed to make the built > > software useful - to them anyway. > > > >> In the case of qt5-webkit, > >> it also takes a long time to compile, so for most people it would be > >> preferred not to install it if not needed. > >> > > The fact that something is not useful (and time consuming, in this case) > > to you doesn't necessarily mean that "most people" feel the same way (or > > differently for that matter). If you don't need it, just leave it out. > > Hi Daniel, > > last time I tried if you didn't build PyQt5 against qt5-webkit > calibre, that depends on PyQt5, didn't build at all. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From dpross1100 at msn.com Tue Feb 7 12:40:25 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Tue, 7 Feb 2017 12:40:25 +0000 Subject: [Slackbuilds-users] Octave with qt5 Message-ID: Hi, Earlier there was some discussion about problems building VLC when Qt5 is installed. I had a similar problem with Octave. With Qt5 installed, the editor didn't work (it depends on QScintilla, which is built against Qt4 in Slackware), and the command window also used a really strange font in my case. I had to add the configure flag --with-qt=4 in order for it to work properly. Maybe someone can confirm? Regards, Dan From yalhcru at gmail.com Tue Feb 7 15:17:24 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 7 Feb 2017 10:17:24 -0500 Subject: [Slackbuilds-users] Taking over fmodapi and zdoom Message-ID: The maintainer of these 2 builds doesn't respond to emails and hasn't updated any of his builds in 3 years. Unless anyone objects, I'd like to take over fmodapi and zdoom (I already maintain gzdoom, which is based on zdoom). The only builds that depend on fmodapi are zdoom and doomsday, but doomsday doesn't actually get built with fmodapi support (it's listed in REQUIRES but isn't included in the build at all). Also, updating fmodapi will allow me to clean up the gzdoom build script, since it currently packages a private copy of a newer version of fmodapi than the SBo build. From thedoogster at gmail.com Tue Feb 7 16:08:17 2017 From: thedoogster at gmail.com (Doogster) Date: Tue, 7 Feb 2017 08:08:17 -0800 Subject: [Slackbuilds-users] Unable to contact Deadbeef SlackBuild maintainer. Message-ID: Heads up that I've been unable to contact the maintainer of the Deadbeef SlackBuild. I emailed him twice: once in November, and once two days ago. Never heard back. From willysr at slackbuilds.org Tue Feb 7 16:33:20 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Feb 2017 23:33:20 +0700 Subject: [Slackbuilds-users] Unable to contact Deadbeef SlackBuild maintainer. In-Reply-To: References: Message-ID: <9b1978d6-33d4-f8a4-2284-41bb07656df0@slackbuilds.org> > Heads up that I've been unable to contact the maintainer of the > Deadbeef SlackBuild. I emailed him twice: once in November, and once > two days ago. Never heard back. You can step up and take over the script -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From thedoogster at gmail.com Tue Feb 7 17:19:47 2017 From: thedoogster at gmail.com (Doogster) Date: Tue, 07 Feb 2017 17:19:47 +0000 Subject: [Slackbuilds-users] Unable to contact Deadbeef SlackBuild maintainer. In-Reply-To: <9b1978d6-33d4-f8a4-2284-41bb07656df0@slackbuilds.org> References: <9b1978d6-33d4-f8a4-2284-41bb07656df0@slackbuilds.org> Message-ID: Sure. On Tue, Feb 7, 2017 at 8:33 AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Heads up that I've been unable to contact the maintainer of the > > Deadbeef SlackBuild. I emailed him twice: once in November, and once > > two days ago. Never heard back. > > You can step up and take over the script > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedoogster at gmail.com Tue Feb 7 17:20:56 2017 From: thedoogster at gmail.com (Doogster) Date: Tue, 07 Feb 2017 17:20:56 +0000 Subject: [Slackbuilds-users] Taking over SpaceFM Message-ID: Heads up that I'm the new maintainer of SpaceFM. I've discussed this with the current maintainer. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Feb 7 17:49:44 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 7 Feb 2017 12:49:44 -0500 Subject: [Slackbuilds-users] Taking doomsday Message-ID: Forwarded message from maintainer: From: Dimitris Zlatanidis Date: Tue, 7 Feb 2017 18:28:57 +0200 Subject: Re: doomsday, part deux To: B Watson Ok, take it :) On 02/07/2017 06:26 PM, B Watson wrote: > I didn't really want to, but if you're not interested in maintaining it, > I could take it over. You might say I've got a thing for Doom. -- Dimitris Zlatanidis From ryanpcmcquen at member.fsf.org Tue Feb 7 18:56:42 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Tue, 7 Feb 2017 10:56:42 -0800 Subject: [Slackbuilds-users] wbar up for grabs Message-ID: Anyone interested in this? I never use it. There is a newer version available here: https://github.com/rodolf0/wbar -- - Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Tue Feb 7 19:14:03 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 7 Feb 2017 11:14:03 -0800 Subject: [Slackbuilds-users] Need some gids and uids please (re-send) In-Reply-To: References: <20170207040040.GA24708@dimstar.local.net> Message-ID: On 02/06/2017 08:25 PM, B Watson wrote: > On 2/6/17, Duncan Roe wrote: >> >> PS thought I sent this already but never saw it in the list - D > > You did. By default this mailing list doesn't send a copy of the message > back to the sender. Think it's possible to change that via web interface, > you should have gotten the URL when you subscribed to the list. I use the "sent" folder for that sort of thing, to avoid spamming myself. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Tue Feb 7 23:13:48 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 7 Feb 2017 16:13:48 -0700 Subject: [Slackbuilds-users] cant build osgEarth. Message-ID: i get errors when building it... also, 2.8 is out... maybe maintainer can update? [ 18%] Built target osgEarth Scanning dependencies of target osgEarthSymbology [ 18%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/AltitudeSymbol.cpp.o [ 18%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Color.cpp.o [ 18%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/CoverageSymbol.cpp.o [ 18%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/CssUtils.cpp.o [ 19%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Expression.cpp.o [ 19%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/ExtrusionSymbol.cpp.o [ 19%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Fill.cpp.o [ 19%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Geometry.cpp.o [ 19%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GeometryFactory.cpp.o [ 19%] Building CXX object src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o In file included from /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: /usr/include/geos/geom/GeometryFactory.h: In constructor ?osgEarth::Symbology::GEOSContext::GEOSContext()?: /usr/include/geos/geom/GeometryFactory.h:453:2: error: ?geos::geom::GeometryFactory::GeometryFactory(const geos::geom::PrecisionModel*)? is protected GeometryFactory(const PrecisionModel *pm); ^ /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:215:52: error: within this context _factory = new geos::geom::GeometryFactory( pm ); ^ In file included from /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: /usr/include/geos/geom/GeometryFactory.h: In destructor ?osgEarth::Symbology::GEOSContext::~GEOSContext()?: /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual geos::geom::GeometryFactory::~GeometryFactory()? is protected virtual ~GeometryFactory(); ^ /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:223:12: error: within this context delete _factory; ^ In file included from /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: /usr/include/geos/geom/GeometryFactory.h: In member function ?void osgEarth::Symbology::GEOSContext::disposeGeometry(geos::geom::Geometry*)?: /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual geos::geom::GeometryFactory::~GeometryFactory()? is protected virtual ~GeometryFactory(); ^ /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:333:20: error: within this context delete f; ^ src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/build.make:278: recipe for target 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o' failed make[2]: *** [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o] Error 1 CMakeFiles/Makefile2:385: recipe for target 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all' failed make[1]: *** [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all] Error 2 Makefile:149: recipe for target 'all' failed make: *** [all] Error 2 -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Wed Feb 8 00:03:10 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 7 Feb 2017 19:03:10 -0500 Subject: [Slackbuilds-users] Pablo Santamaria's builds Message-ID: So Pablo's disappeared, doesn't answer email, hasn't updated anything since 3 years ago (Feb 9 2014). It might be that we should divvy up his builds, so they won't stay unmaintained... I grabbed zdoom and fmodapi already. I'm willing to take these too: graphics/qiv desktop/wmdl desktop/wmsystemtray desktop/wmtime development/ftnchek system/makepasswd system/yeahconsole games/advancescan (unless the advancemame maintainer wants it, but advancemame hasn't been updated since May 2010! Anyone want to grab them both? I've already got one mame, I don't need another. Doogster?) Which leaves a good long list up for grabs: academic/arpack academic/g3data academic/lapack95 academic/qrupdate academic/slatec academic/suitesparse audio/cuberok desktop/macopix (this is hilarious, does anyone actually use it?) gis/gmapcatcher graphics/discwrapper graphics/tuxpaint graphics/tuxpaint-stamps libraries/audiere libraries/libaosd (should go to Ryan, it's a dep of licq) libraries/libgringotts libraries/libpaper (should go to whoever takes tuxpaint) multimedia/dvbsnoop multimedia/lircaile multimedia/subtitlecomposer multimedia/videocut office/hunspell-en office/hunspell-es perl/perl-class-accessor perl/perl-file-path-expand perl/perl-lirc-client perl/perl-tk python/pylirc From fernando.lopezjr at gmail.com Wed Feb 8 00:07:39 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 7 Feb 2017 17:07:39 -0700 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: i'll take this: graphics/tuxpaint graphics/tuxpaint-stamps On Tue, Feb 7, 2017 at 5:03 PM, B Watson wrote: > So Pablo's disappeared, doesn't answer email, hasn't updated anything > since 3 years ago (Feb 9 2014). It might be that we should divvy up his > builds, so they won't stay unmaintained... > > I grabbed zdoom and fmodapi already. I'm willing to take these too: > > graphics/qiv > desktop/wmdl > desktop/wmsystemtray > desktop/wmtime > development/ftnchek > system/makepasswd > system/yeahconsole > games/advancescan (unless the advancemame maintainer wants it, but > advancemame hasn't been updated since May 2010! Anyone > want to grab them both? I've already got one mame, I > don't need another. Doogster?) > > Which leaves a good long list up for grabs: > > academic/arpack > academic/g3data > academic/lapack95 > academic/qrupdate > academic/slatec > academic/suitesparse > audio/cuberok > desktop/macopix (this is hilarious, does anyone actually use it?) > gis/gmapcatcher > graphics/discwrapper > graphics/tuxpaint > graphics/tuxpaint-stamps > libraries/audiere > libraries/libaosd (should go to Ryan, it's a dep of licq) > libraries/libgringotts > libraries/libpaper (should go to whoever takes tuxpaint) > multimedia/dvbsnoop > multimedia/lircaile > multimedia/subtitlecomposer > multimedia/videocut > office/hunspell-en > office/hunspell-es > perl/perl-class-accessor > perl/perl-file-path-expand > perl/perl-lirc-client > perl/perl-tk > python/pylirc > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryanpcmcquen at member.fsf.org Wed Feb 8 00:07:44 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Tue, 7 Feb 2017 16:07:44 -0800 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: libraries/libaosd (should go to Ryan, it's a dep of licq) > I?m not using licq anymore, so if someone wants to take that and this one, it would probably be a lot better for licq. Otherwise, I will try to take this one, but I?m pretty busy as of late. ? -- - Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From klaatu at mixedsignals.ml Wed Feb 8 00:54:16 2017 From: klaatu at mixedsignals.ml (klaatu at mixedsignals.ml) Date: Wed, 08 Feb 2017 13:54:16 +1300 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: On 2017-02-08 13:03, B Watson wrote: > So Pablo's disappeared, doesn't answer email, hasn't updated anything > since 3 years ago (Feb 9 2014). It might be that we should divvy up his > builds, so they won't stay unmaintained... > > I grabbed zdoom and fmodapi already. I'm willing to take these too: > > graphics/qiv > desktop/wmdl > desktop/wmsystemtray > desktop/wmtime > development/ftnchek > system/makepasswd > system/yeahconsole > games/advancescan (unless the advancemame maintainer wants it, but > advancemame hasn't been updated since May 2010! > Anyone > want to grab them both? I've already got one mame, I > don't need another. Doogster?) > > Which leaves a good long list up for grabs: > > academic/arpack > academic/g3data > academic/lapack95 > academic/qrupdate > academic/slatec > academic/suitesparse > audio/cuberok > desktop/macopix (this is hilarious, does anyone actually use it?) > gis/gmapcatcher > graphics/discwrapper > graphics/tuxpaint > graphics/tuxpaint-stamps > libraries/audiere > libraries/libaosd (should go to Ryan, it's a dep of licq) > libraries/libgringotts > libraries/libpaper (should go to whoever takes tuxpaint) > multimedia/dvbsnoop > multimedia/lircaile > multimedia/subtitlecomposer > multimedia/videocut > office/hunspell-en > office/hunspell-es > perl/perl-class-accessor > perl/perl-file-path-expand > perl/perl-lirc-client > perl/perl-tk > python/pylirc > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ I'll take: multimedia/subtitlecomposer multimedia/dvbsnoop From willysr at slackbuilds.org Wed Feb 8 03:01:09 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 8 Feb 2017 10:01:09 +0700 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: References: Message-ID: > i get errors when building it... also, 2.8 is out... maybe maintainer can > update? > > [ 18%] Built target osgEarth > Scanning dependencies of target osgEarthSymbology > [ 18%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/AltitudeSymbol.cpp.o > [ 18%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Color.cpp.o > [ 18%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/CoverageSymbol.cpp.o > [ 18%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/CssUtils.cpp.o > [ 19%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Expression.cpp.o > [ 19%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/ExtrusionSymbol.cpp.o > [ 19%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Fill.cpp.o > [ 19%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Geometry.cpp.o > [ 19%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GeometryFactory.cpp.o > [ 19%] Building CXX object > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o > In file included from > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: > /usr/include/geos/geom/GeometryFactory.h: In constructor > ?osgEarth::Symbology::GEOSContext::GEOSContext()?: > /usr/include/geos/geom/GeometryFactory.h:453:2: error: > ?geos::geom::GeometryFactory::GeometryFactory(const > geos::geom::PrecisionModel*)? is protected > GeometryFactory(const PrecisionModel *pm); > ^ > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:215:52: > error: within this context > _factory = new geos::geom::GeometryFactory( pm ); > ^ > In file included from > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: > /usr/include/geos/geom/GeometryFactory.h: In destructor > ?osgEarth::Symbology::GEOSContext::~GEOSContext()?: > /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual > geos::geom::GeometryFactory::~GeometryFactory()? is protected > virtual ~GeometryFactory(); > ^ > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:223:12: > error: within this context > delete _factory; > ^ > In file included from > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: > /usr/include/geos/geom/GeometryFactory.h: In member function ?void > osgEarth::Symbology::GEOSContext::disposeGeometry(geos::geom::Geometry*)?: > /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual > geos::geom::GeometryFactory::~GeometryFactory()? is protected > virtual ~GeometryFactory(); > ^ > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:333:20: > error: within this context > delete f; > ^ > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/build.make:278: > recipe for target > 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o' failed > make[2]: *** > [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o] Error 1 > CMakeFiles/Makefile2:385: recipe for target > 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all' failed > make[1]: *** [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all] > Error 2 > Makefile:149: recipe for target 'all' failed > make: *** [all] Error 2 Even 2.8 still failed to build In file included from /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:25:0: /usr/include/geos/geom/GeometryFactory.h: In constructor ?osgEarth::Symbology::GEOSContext::GEOSContext()?: /usr/include/geos/geom/GeometryFactory.h:453:2: error: ?geos::geom::GeometryFactory::GeometryFactory(const geos::geom::PrecisionModel*)? is protected GeometryFactory(const PrecisionModel *pm); ^ /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:219:52: error: within this context _factory = new geos::geom::GeometryFactory( pm ); ^ In file included from /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:25:0: /usr/include/geos/geom/GeometryFactory.h: In destructor ?osgEarth::Symbology::GEOSContext::~GEOSContext()?: /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual geos::geom::GeometryFactory::~GeometryFactory()? is protected virtual ~GeometryFactory(); ^ /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:227:12: error: within this context delete _factory; ^ In file included from /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:25:0: /usr/include/geos/geom/GeometryFactory.h: In member function ?void osgEarth::Symbology::GEOSContext::disposeGeometry(geos::geom::Geometry*)?: /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual geos::geom::GeometryFactory::~GeometryFactory()? is protected virtual ~GeometryFactory(); ^ /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:337:20: error: within this context delete f; ^ src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/build.make:350: recipe for target 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o' failed make[2]: *** [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o] Error 1 CMakeFiles/Makefile2:333: recipe for target 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all' failed make[1]: *** [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all] Error 2 Makefile:149: recipe for target 'all' failed make: *** [all] Error 2 reported upstream: https://github.com/gwaldron/osgearth/issues/865 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ekinakoglu at gmail.com Wed Feb 8 07:40:53 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Wed, 8 Feb 2017 10:40:53 +0300 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: I would like to take arpack, g3data and lapack95. Best, Ekin On 02/08/2017 03:54 AM, klaatu at mixedsignals.ml wrote: > On 2017-02-08 13:03, B Watson wrote: >> So Pablo's disappeared, doesn't answer email, hasn't updated anything >> since 3 years ago (Feb 9 2014). It might be that we should divvy up his >> builds, so they won't stay unmaintained... >> >> I grabbed zdoom and fmodapi already. I'm willing to take these too: >> >> graphics/qiv >> desktop/wmdl >> desktop/wmsystemtray >> desktop/wmtime >> development/ftnchek >> system/makepasswd >> system/yeahconsole >> games/advancescan (unless the advancemame maintainer wants it, but >> advancemame hasn't been updated since May 2010! >> Anyone >> want to grab them both? I've already got one mame, I >> don't need another. Doogster?) >> >> Which leaves a good long list up for grabs: >> >> academic/arpack >> academic/g3data >> academic/lapack95 >> academic/qrupdate >> academic/slatec >> academic/suitesparse >> audio/cuberok >> desktop/macopix (this is hilarious, does anyone actually use it?) >> gis/gmapcatcher >> graphics/discwrapper >> graphics/tuxpaint >> graphics/tuxpaint-stamps >> libraries/audiere >> libraries/libaosd (should go to Ryan, it's a dep of licq) >> libraries/libgringotts >> libraries/libpaper (should go to whoever takes tuxpaint) >> multimedia/dvbsnoop >> multimedia/lircaile >> multimedia/subtitlecomposer >> multimedia/videocut >> office/hunspell-en >> office/hunspell-es >> perl/perl-class-accessor >> perl/perl-file-path-expand >> perl/perl-lirc-client >> perl/perl-tk >> python/pylirc >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ > > > I'll take: > > multimedia/subtitlecomposer > multimedia/dvbsnoop > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From chytraeu at sdf.org Wed Feb 8 08:23:30 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Wed, 8 Feb 2017 02:23:30 -0600 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: I'd like to take offfice/hunspell-en if no one else has On 02/08/2017 01:40 AM, Ekin Akoglu wrote: > I would like to take arpack, g3data and lapack95. > > Best, > > Ekin > > > On 02/08/2017 03:54 AM, klaatu at mixedsignals.ml wrote: >> On 2017-02-08 13:03, B Watson wrote: >>> So Pablo's disappeared, doesn't answer email, hasn't updated anything >>> since 3 years ago (Feb 9 2014). It might be that we should divvy up his >>> builds, so they won't stay unmaintained... >>> >>> I grabbed zdoom and fmodapi already. I'm willing to take these too: >>> >>> graphics/qiv >>> desktop/wmdl >>> desktop/wmsystemtray >>> desktop/wmtime >>> development/ftnchek >>> system/makepasswd >>> system/yeahconsole >>> games/advancescan (unless the advancemame maintainer wants it, but >>> advancemame hasn't been updated since May 2010! >>> Anyone >>> want to grab them both? I've already got one mame, I >>> don't need another. Doogster?) >>> >>> Which leaves a good long list up for grabs: >>> >>> academic/arpack >>> academic/g3data >>> academic/lapack95 >>> academic/qrupdate >>> academic/slatec >>> academic/suitesparse >>> audio/cuberok >>> desktop/macopix (this is hilarious, does anyone actually use it?) >>> gis/gmapcatcher >>> graphics/discwrapper >>> graphics/tuxpaint >>> graphics/tuxpaint-stamps >>> libraries/audiere >>> libraries/libaosd (should go to Ryan, it's a dep of licq) >>> libraries/libgringotts >>> libraries/libpaper (should go to whoever takes tuxpaint) >>> multimedia/dvbsnoop >>> multimedia/lircaile >>> multimedia/subtitlecomposer >>> multimedia/videocut >>> office/hunspell-en >>> office/hunspell-es >>> perl/perl-class-accessor >>> perl/perl-file-path-expand >>> perl/perl-lirc-client >>> perl/perl-tk >>> python/pylirc >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >> >> >> I'll take: >> >> multimedia/subtitlecomposer >> multimedia/dvbsnoop >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Wed Feb 8 09:02:57 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 8 Feb 2017 02:02:57 -0700 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: References: Message-ID: i was able to compile *osgEarth 2.8* with *GEOS 3.5.0* On Tue, Feb 7, 2017 at 8:01 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > i get errors when building it... also, 2.8 is out... maybe maintainer can > > update? > > > > [ 18%] Built target osgEarth > > Scanning dependencies of target osgEarthSymbology > > [ 18%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology. > dir/AltitudeSymbol.cpp.o > > [ 18%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Color.cpp.o > > [ 18%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology. > dir/CoverageSymbol.cpp.o > > [ 18%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/CssUtils.cpp.o > > [ 19%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Expression.cpp.o > > [ 19%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology. > dir/ExtrusionSymbol.cpp.o > > [ 19%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Fill.cpp.o > > [ 19%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/Geometry.cpp.o > > [ 19%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology. > dir/GeometryFactory.cpp.o > > [ 19%] Building CXX object > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o > > In file included from > > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: > > /usr/include/geos/geom/GeometryFactory.h: In constructor > > ?osgEarth::Symbology::GEOSContext::GEOSContext()?: > > /usr/include/geos/geom/GeometryFactory.h:453:2: error: > > ?geos::geom::GeometryFactory::GeometryFactory(const > > geos::geom::PrecisionModel*)? is protected > > GeometryFactory(const PrecisionModel *pm); > > ^ > > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:215:52: > > error: within this context > > _factory = new geos::geom::GeometryFactory( pm ); > > ^ > > In file included from > > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: > > /usr/include/geos/geom/GeometryFactory.h: In destructor > > ?osgEarth::Symbology::GEOSContext::~GEOSContext()?: > > /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual > > geos::geom::GeometryFactory::~GeometryFactory()? is protected > > virtual ~GeometryFactory(); > > ^ > > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:223:12: > > error: within this context > > delete _factory; > > ^ > > In file included from > > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:25:0: > > /usr/include/geos/geom/GeometryFactory.h: In member function ?void > > osgEarth::Symbology::GEOSContext::disposeGeometry( > geos::geom::Geometry*)?: > > /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual > > geos::geom::GeometryFactory::~GeometryFactory()? is protected > > virtual ~GeometryFactory(); > > ^ > > /tmp/SBo/osgearth-osgearth-2.7/src/osgEarthSymbology/GEOS.cpp:333:20: > > error: within this context > > delete f; > > ^ > > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/build.make:278: > > recipe for target > > 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o' > failed > > make[2]: *** > > [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o] > Error 1 > > CMakeFiles/Makefile2:385: recipe for target > > 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all' failed > > make[1]: *** [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology. > dir/all] > > Error 2 > > Makefile:149: recipe for target 'all' failed > > make: *** [all] Error 2 > > Even 2.8 still failed to build > > In file included from > /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:25:0: > /usr/include/geos/geom/GeometryFactory.h: In constructor > ?osgEarth::Symbology::GEOSContext::GEOSContext()?: > /usr/include/geos/geom/GeometryFactory.h:453:2: error: > ?geos::geom::GeometryFactory::GeometryFactory(const > geos::geom::PrecisionModel*)? is protected > GeometryFactory(const PrecisionModel *pm); > ^ > /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:219:52: error: > within this context > _factory = new geos::geom::GeometryFactory( pm ); > ^ > In file included from > /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:25:0: > /usr/include/geos/geom/GeometryFactory.h: In destructor > ?osgEarth::Symbology::GEOSContext::~GEOSContext()?: > /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual > geos::geom::GeometryFactory::~GeometryFactory()? is protected > virtual ~GeometryFactory(); > ^ > /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:227:12: error: > within this context > delete _factory; > ^ > In file included from > /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:25:0: > /usr/include/geos/geom/GeometryFactory.h: In member function ?void > osgEarth::Symbology::GEOSContext::disposeGeometry(geos::geom::Geometry*)?: > /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual > geos::geom::GeometryFactory::~GeometryFactory()? is protected > virtual ~GeometryFactory(); > ^ > /tmp/SBo/osgearth-2.8/src/osgEarthSymbology/GEOS.cpp:337:20: error: > within this context > delete f; > ^ > src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/build.make:350: > recipe for target > 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o' failed > make[2]: *** > [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/GEOS.cpp.o] Error > 1 > CMakeFiles/Makefile2:333: recipe for target > 'src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all' failed > make[1]: *** > [src/osgEarthSymbology/CMakeFiles/osgEarthSymbology.dir/all] Error 2 > Makefile:149: recipe for target 'all' failed > make: *** [all] Error 2 > > reported upstream: https://github.com/gwaldron/osgearth/issues/865 > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Wed Feb 8 09:53:46 2017 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 8 Feb 2017 09:53:46 +0000 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: References: Message-ID: osm2pgsql has the same problem. The latest version osm2pgsql-0.92.0 has the same problem too ... after converting it to cmake and adding lua as a new dep :( In file included from geometry-builder.cpp:37:0: /usr/include/geos/geom/GeometryFactory.h: In member function ?geometry_builder::maybe_wkt_t geometry_builder::get_wkt_simple(const nodelist_t&, int) const?: /usr/include/geos/geom/GeometryFactory.h:420:2: error: ?geos::geom::GeometryFactory::GeometryFactory()? is protected GeometryFactory(); ^ geometry-builder.cpp:93:21: error: within this context GeometryFactory gf; ^ In file included from geometry-builder.cpp:37:0: /usr/include/geos/geom/GeometryFactory.h:474:10: error: ?virtual geos::geom::GeometryFactory::~GeometryFactory()? is protected virtual ~GeometryFactory(); ^ geometry-builder.cpp:93:21: error: within this context GeometryFactory gf; ^ [etc] Sorry about the bad news -D. From willysr at slackbuilds.org Wed Feb 8 12:28:10 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 8 Feb 2017 19:28:10 +0700 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: References: Message-ID: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> > i was able to compile *osgEarth 2.8* with *GEOS 3.5.0* Benjamin, what's your suggestion about this? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From bosth at alumni.sfu.ca Wed Feb 8 15:10:27 2017 From: bosth at alumni.sfu.ca (Benjamin Trigona-Harany) Date: Wed, 08 Feb 2017 07:10:27 -0800 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> References: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> Message-ID: <1862751.1Pq5sUKZdH@wintermute> On Wednesday, February 8, 2017 7:28:10 PM PST Willy Sudiarto Raharjo wrote: > > i was able to compile *osgEarth 2.8* with *GEOS 3.5.0* > > Benjamin, what's your suggestion about this? I was aware of the issue affecting the latest osm2pgsql and have not upgraded that script accordingly. If the new geos is also affecting osgEarth then we can consider a downgrade back to 3.5.x. However, it might be worth keeping an eye on https://github.com/gwaldron/ osgearth/issues/867 to see if they get a quick patch for 3.6.x. From bosth at alumni.sfu.ca Wed Feb 8 15:14:44 2017 From: bosth at alumni.sfu.ca (Benjamin Trigona-Harany) Date: Wed, 08 Feb 2017 07:14:44 -0800 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> References: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> Message-ID: <4104402.ec2MpoAre0@wintermute> On Wednesday, February 8, 2017 7:28:10 PM PST Willy Sudiarto Raharjo wrote: > > i was able to compile *osgEarth 2.8* with *GEOS 3.5.0* > > Benjamin, what's your suggestion about this? I was aware of the issue affecting the latest osm2pgsql and have not upgraded that script accordingly. If the new geos is also affecting osgEarth then we can consider a downgrade back to 3.5.x. However, it might be worth keeping an eye on https://github.com/gwaldron/ osgearth/issues/867 to see if they get a quick patch for 3.6.x. From dpross1100 at msn.com Thu Feb 9 01:23:11 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Thu, 9 Feb 2017 01:23:11 +0000 Subject: [Slackbuilds-users] ncmpcpp requires mpd Message-ID: Hi, ncmpcpp lists only libmpdclient as a requirement, but not mpd. However, from what I can tell, mpd is required at runtime. If mpd is not running, when I start ncmpcpp I get the following error: ncmpcpp: Connection refused I did a search in the SBo repository and I found that the following MPD clients list libmpdclient as a requirement, but not mpd itself: ario mpc ncmpc ncmpcpp vimpc But there is one that lists both libmpdclient and mpd: mpdscribble Given that so many do not list mpd as a requirement, I'm inclined to think I'm missing something, and mpd must not actually be required for ncmpcpp. If so, I'd like to know what it is that I'm missing. If not, then I think mpd should be added as a requirement for ncmpcpp, and possibly the others listed above as well (though ncmpcpp is the only one I've used, so I don't know for sure). Dan From thedoogster at gmail.com Thu Feb 9 01:31:49 2017 From: thedoogster at gmail.com (Doogster) Date: Wed, 8 Feb 2017 17:31:49 -0800 Subject: [Slackbuilds-users] ncmpcpp requires mpd In-Reply-To: References: Message-ID: The reason is that ncmpcpp (and other mpd clients) can connect to an mpd instance on a different computer. They don't need mpd installed on the same box in order to work. On Wed, Feb 8, 2017 at 5:23 PM, Daniel Prosser wrote: > Hi, > > ncmpcpp lists only libmpdclient as a requirement, but not mpd. However, > from what I can tell, mpd is required at runtime. If mpd is not running, > when I start ncmpcpp I get the following error: > > ncmpcpp: Connection refused > > I did a search in the SBo repository and I found that the following > MPD clients list libmpdclient as a requirement, but not mpd itself: > > ario > mpc > ncmpc > ncmpcpp > vimpc > > But there is one that lists both libmpdclient and mpd: > > mpdscribble > > Given that so many do not list mpd as a requirement, I'm inclined to > think I'm missing something, and mpd must not actually be required for > ncmpcpp. If so, I'd like to know what it is that I'm missing. If not, > then I think mpd should be added as a requirement for ncmpcpp, and > possibly the others listed above as well (though ncmpcpp is the only > one I've used, so I don't know for sure). > > Dan > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From slackbuilds at jaxartes.net Thu Feb 9 01:40:20 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Wed, 08 Feb 2017 17:40:20 -0800 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: <4104402.ec2MpoAre0@wintermute> References: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> <4104402.ec2MpoAre0@wintermute> Message-ID: <3083159.nxI3lStsjp@wintermute> On Wednesday, February 8, 2017 7:14:44 AM PST Benjamin Trigona-Harany wrote: > On Wednesday, February 8, 2017 7:28:10 PM PST Willy Sudiarto Raharjo wrote: > > > i was able to compile *osgEarth 2.8* with *GEOS 3.5.0* > > > > Benjamin, what's your suggestion about this? > > I was aware of the issue affecting the latest osm2pgsql and have not > upgraded that script accordingly. If the new geos is also affecting > osgEarth then we can consider a downgrade back to 3.5.x. > > However, it might be worth keeping an eye on https://github.com/gwaldron/ > osgearth/issues/867 to see if they get a quick patch for 3.6.x. Here's a patch already: https://github.com/Alexpux/MINGW-packages/blob/master/ mingw-w64-osgearth/0002-geos-3_6_1-support.patch From willysr at slackbuilds.org Thu Feb 9 01:45:13 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 9 Feb 2017 08:45:13 +0700 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: <3083159.nxI3lStsjp@wintermute> References: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> <4104402.ec2MpoAre0@wintermute> <3083159.nxI3lStsjp@wintermute> Message-ID: <187dd41e-061f-5ffa-6565-c62e50a628ab@slackbuilds.org> >> However, it might be worth keeping an eye on https://github.com/gwaldron/ >> osgearth/issues/867 to see if they get a quick patch for 3.6.x. > > Here's a patch already: https://github.com/Alexpux/MINGW-packages/blob/master/ > mingw-w64-osgearth/0002-geos-3_6_1-support.patch Yes, he has requested a PR, but not yet merged to master https://github.com/gwaldron/osgearth/pull/848 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Thu Feb 9 01:51:08 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Thu, 9 Feb 2017 01:51:08 +0000 Subject: [Slackbuilds-users] ncmpcpp requires mpd In-Reply-To: References: Message-ID: Interesting. Ok, well in that case, I think that information should be mentioned in the README. The "Connection refused" error isn't really descriptive enough for the uninitiated to understand what the problem is. It had me scratching my head and googling for a solution the first time I encountered it. Also, then, for the sake of consistency with all the others, maybe mpdscribble shouldn't list mpd as a requirement either? (Again, I haven't used it, so that's just my assumption. Maybe mpdscribble actually does need to connect to a local mpd instance.) On Wed, Feb 08, 2017 at 05:31:49PM -0800, Doogster wrote: > The reason is that ncmpcpp (and other mpd clients) can connect to an > mpd instance on a different computer. They don't need mpd installed on > the same box in order to work. > > On Wed, Feb 8, 2017 at 5:23 PM, Daniel Prosser wrote: > > Hi, > > > > ncmpcpp lists only libmpdclient as a requirement, but not mpd. However, > > from what I can tell, mpd is required at runtime. If mpd is not running, > > when I start ncmpcpp I get the following error: > > > > ncmpcpp: Connection refused > > > > I did a search in the SBo repository and I found that the following > > MPD clients list libmpdclient as a requirement, but not mpd itself: > > > > ario > > mpc > > ncmpc > > ncmpcpp > > vimpc > > > > But there is one that lists both libmpdclient and mpd: > > > > mpdscribble > > > > Given that so many do not list mpd as a requirement, I'm inclined to > > think I'm missing something, and mpd must not actually be required for > > ncmpcpp. If so, I'd like to know what it is that I'm missing. If not, > > then I think mpd should be added as a requirement for ncmpcpp, and > > possibly the others listed above as well (though ncmpcpp is the only > > one I've used, so I don't know for sure). > > > > Dan > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From yalhcru at gmail.com Thu Feb 9 18:32:26 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 9 Feb 2017 13:32:26 -0500 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: So far we've got: Fernando Lopez: graphics/tuxpaint graphics/tuxpaint-stamps Fernando, can you take libraries/libpaper too, since it's a dependency of tuxpaint (and nothing else, only tuxpaint uses it)? Ryan P.C. McQuen (for now, until someone else takes licq): libraries/libaosd Ryan, libaosd hasn't been developed since 2010. All you really have to do is update the .info file with your name/email, and wait for bug reports (which probably will never come). Donald Cooley: office/hunspell-en Donald, would you mind taking hunspell-es also? Its homepage & download site seems to be gone, moved to github here: https://github.com/sbosio/rla-es klaatu: multimedia/dvbsnoop multimedia/subtitlecomposer Ekin Akoglu: academic/arpack academic/g3data academic/lapack95 From yalhcru at gmail.com Thu Feb 9 18:53:00 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 9 Feb 2017 13:53:00 -0500 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: So these remain unclaimed still: academic/qrupdate academic/slatec academic/suitesparse audio/cuberok desktop/macopix gis/gmapcatcher graphics/discwrapper libraries/audiere libraries/libgringotts multimedia/lircaile multimedia/videocut perl/perl-class-accessor perl/perl-file-path-expand perl/perl-lirc-client perl/perl-tk python/pylirc Everyone check your builds, see if any of these are dependencies of your stuff. From fernando.lopezjr at gmail.com Thu Feb 9 19:27:45 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 9 Feb 2017 12:27:45 -0700 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: sure. On Thu, Feb 9, 2017 at 11:53 AM, B Watson wrote: > So these remain unclaimed still: > > academic/qrupdate > academic/slatec > academic/suitesparse > audio/cuberok > desktop/macopix > gis/gmapcatcher > graphics/discwrapper > libraries/audiere > libraries/libgringotts > multimedia/lircaile > multimedia/videocut > perl/perl-class-accessor > perl/perl-file-path-expand > perl/perl-lirc-client > perl/perl-tk > python/pylirc > > Everyone check your builds, see if any of these are dependencies of > your stuff. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Thu Feb 9 21:24:09 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 10 Feb 2017 07:24:09 +1000 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: On 10/02/17 04:53, B Watson wrote: > So these remain unclaimed still: > > academic/qrupdate and > academic/suitesparse are both optional dependencies of octave - hint :) > > Everyone check your builds, see if any of these are dependencies of > your stuff. > From chytraeu at sdf.org Thu Feb 9 22:10:35 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Thu, 9 Feb 2017 16:10:35 -0600 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: <53a4265b-9139-8de7-65fc-cc563595efca@sdf.org> On 02/09/2017 12:32 PM, B Watson wrote: > snip>>>>>>>>>>>>>>>>>>>>> > > Donald Cooley: > office/hunspell-en > > Donald, would you mind taking hunspell-es also? Its homepage & > download site seems to be gone, moved to github here: > https://github.com/sbosio/rla-es > > snip>>>>> No, I don't speak Spanish. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From fernando.lopezjr at gmail.com Thu Feb 9 22:12:29 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 9 Feb 2017 15:12:29 -0700 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: <53a4265b-9139-8de7-65fc-cc563595efca@sdf.org> References: <53a4265b-9139-8de7-65fc-cc563595efca@sdf.org> Message-ID: you dont need to... all you need is the zip file/.git and that is it... everything is the same... although there is google translator. ;) On Thu, Feb 9, 2017 at 3:10 PM, Donald Cooley wrote: > > > On 02/09/2017 12:32 PM, B Watson wrote: > > snip>>>>>>>>>>>>>>>>>>>>> > > > > Donald Cooley: > > office/hunspell-en > > > > Donald, would you mind taking hunspell-es also? Its homepage & > > download site seems to be gone, moved to github here: > > https://github.com/sbosio/rla-es > > > > > snip>>>>> > > No, I don't speak Spanish. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From chytraeu at sdf.org Thu Feb 9 22:17:41 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Thu, 9 Feb 2017 16:17:41 -0600 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: <53a4265b-9139-8de7-65fc-cc563595efca@sdf.org> Message-ID: <150a543b-e356-2469-6823-8cf1dcdbb562@sdf.org> Alright. I don't mind, just thought it would be better if a Spanish speaker took it over. I'll take it. On 02/09/2017 04:12 PM, Fernando Lopez wrote: > you dont need to... all you need is the zip file/.git and that is > it... everything is the same... although there is google translator. ;) > > On Thu, Feb 9, 2017 at 3:10 PM, Donald Cooley > wrote: > > > > On 02/09/2017 12:32 PM, B Watson wrote: > > snip>>>>>>>>>>>>>>>>>>>>> > > > > Donald Cooley: > > office/hunspell-en > > > > Donald, would you mind taking hunspell-es also? Its homepage & > > download site seems to be gone, moved to github here: > > https://github.com/sbosio/rla-es > > > > > snip>>>>> > > No, I don't speak Spanish. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Thu Feb 9 23:49:25 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 9 Feb 2017 18:49:25 -0500 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: <150a543b-e356-2469-6823-8cf1dcdbb562@sdf.org> References: <53a4265b-9139-8de7-65fc-cc563595efca@sdf.org> <150a543b-e356-2469-6823-8cf1dcdbb562@sdf.org> Message-ID: On 2/9/17, Donald Cooley wrote: > Alright. I don't mind, just thought it would be better if a Spanish > speaker took it over. I'll take it. I don't speak Japanese, but I maintain man-pages-ja. Original idea was that one day I'd learn to read Japanese, but that hasn't actually happened so far... From slack.dhabyx at gmail.com Fri Feb 10 04:18:33 2017 From: slack.dhabyx at gmail.com (Dhaby Xiloj) Date: Thu, 9 Feb 2017 22:18:33 -0600 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: <47d0bbe1-cfc4-1f36-6d74-5dd6ca83212c@gmail.com> 07/02/17, 18:03, B Watson: > office/hunspell-es I will take this one -- Dhaby Xiloj From elyk03 at gmail.com Fri Feb 10 04:43:58 2017 From: elyk03 at gmail.com (Kyle Guinn) Date: Thu, 9 Feb 2017 22:43:58 -0600 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: On 2/9/17, Christoph Willing wrote: > On 10/02/17 04:53, B Watson wrote: >> So these remain unclaimed still: >> >> academic/qrupdate > and >> academic/suitesparse > > are both optional dependencies of octave - hint :) OK. I can take academic/qrupdate. academic/suitesparse can probably go away (unless something depends on that old version), I've got scripts for each of its individual components. Likewise, academic/arpack can probably also go away. Last I knew, upstream was dead, but it's continuing to be maintained as arpack-ng. I've got a script for that one. From northrup at yellowapple.us Fri Feb 10 08:33:29 2017 From: northrup at yellowapple.us (Ryan S. Northrup) Date: Fri, 10 Feb 2017 00:33:29 -0800 (PST) Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: On Thu, 9 Feb 2017, B Watson wrote: > So these remain unclaimed still: > > [...] > > perl/perl-class-accessor > perl/perl-file-path-expand > perl/perl-lirc-client > perl/perl-tk I'll take these if nobody else wants 'em. Thanks, -- Ryan S. Northrup northrup at yellowapple.us From baildon.research at googlemail.com Fri Feb 10 13:01:31 2017 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 10 Feb 2017 13:01:31 +0000 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: <47d0bbe1-cfc4-1f36-6d74-5dd6ca83212c@gmail.com> References: <47d0bbe1-cfc4-1f36-6d74-5dd6ca83212c@gmail.com> Message-ID: On 10 February 2017 at 04:18, Dhaby Xiloj wrote: > 07/02/17, 18:03, B Watson: >> office/hunspell-es > I will take this one Donald Cooley got hunspell-es earlier, but I think he didn't really want it ;-) Is that ok Donald? would you prefer if Dhaby has hunspell-es? Thanks everybody -D. From atelszewski at gmail.com Fri Feb 10 21:13:56 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 10 Feb 2017 22:13:56 +0100 Subject: [Slackbuilds-users] gtk-vnc 0.7.0 release including 2 security fixes Message-ID: <435b6097-4126-57bc-2eb2-4a95502ab662@gmail.com> Hi, gtk-vnc 0.7.0 is available. Have a look here: https://www.berrange.com/posts/2017/02/10/announce-gtk-vnc-0-7-0-release-including-2-security-fixes/ (Bcc-d maintainer). Cheers. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Fri Feb 10 23:41:54 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Feb 2017 06:41:54 +0700 Subject: [Slackbuilds-users] cant build osgEarth. In-Reply-To: <187dd41e-061f-5ffa-6565-c62e50a628ab@slackbuilds.org> References: <00162283-2e72-28fd-740d-03dac12f396d@slackbuilds.org> <4104402.ec2MpoAre0@wintermute> <3083159.nxI3lStsjp@wintermute> <187dd41e-061f-5ffa-6565-c62e50a628ab@slackbuilds.org> Message-ID: >>> However, it might be worth keeping an eye on https://github.com/gwaldron/ >>> osgearth/issues/867 to see if they get a quick patch for 3.6.x. >> >> Here's a patch already: https://github.com/Alexpux/MINGW-packages/blob/master/ >> mingw-w64-osgearth/0002-geos-3_6_1-support.patch > > Yes, he has requested a PR, but not yet merged to master > https://github.com/gwaldron/osgearth/pull/848 I tested this PR and it built fine and merge it along with 2.8 update. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chytraeu at sdf.org Fri Feb 10 23:55:43 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Fri, 10 Feb 2017 17:55:43 -0600 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: <47d0bbe1-cfc4-1f36-6d74-5dd6ca83212c@gmail.com> Message-ID: <0f866c18-8930-d4cd-3661-d6419550f6db@sdf.org> On 02/10/2017 07:01 AM, David Spencer wrote: > On 10 February 2017 at 04:18, Dhaby Xiloj wrote: >> 07/02/17, 18:03, B Watson: >>> office/hunspell-es >> I will take this one > Donald Cooley got hunspell-es earlier, but I think he didn't really want it ;-) > > Is that ok Donald? would you prefer if Dhaby has hunspell-es? > > Thanks everybody > -D. Dhaby can take it if he wants. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Feb 11 00:18:06 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Feb 2017 07:18:06 +0700 Subject: [Slackbuilds-users] Fwd: reiser4progs and libaal getting long in the tooth In-Reply-To: References: Message-ID: > Sent this out last week, got no response. Sending to the list in case > the maintainer's monitoring it. > > ---------- Forwarded message ---------- > From: B Watson > Date: Tue, 31 Jan 2017 14:19:03 -0500 > Subject: reiser4progs and libaal getting long in the tooth > To: kerickson at lavabit.com > > These 2 packages on SBo have you listed as maintainer. libaal is now up > to version 1.0.6 (updated in 2014), and reiser4progs is at 1.10 (updated > in late 2015). Any chance you'll update your builds? > > I ask because I'm trying to build partclone with support for reiser 4, > and it needs a newer reiser4progs (or a patch for the old one). > > Also HOMEPAGE in both .info files should be updated to > https://reiser4.wiki.kernel.org/index.php/Reiser4progs or > maybe https://reiser4.wiki.kernel.org/index.php/Main_Page bumped to 1.0.6 and 1.10 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slack.dhabyx at gmail.com Sat Feb 11 00:38:45 2017 From: slack.dhabyx at gmail.com (Dhaby Xiloj) Date: Fri, 10 Feb 2017 18:38:45 -0600 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: <0f866c18-8930-d4cd-3661-d6419550f6db@sdf.org> References: <47d0bbe1-cfc4-1f36-6d74-5dd6ca83212c@gmail.com> <0f866c18-8930-d4cd-3661-d6419550f6db@sdf.org> Message-ID: 10/02/17, 17:55, Donald Cooley : > Dhaby can take it if he wants. > Thanks, I uploaded the new hunspell-es to SBo, and for now is in pending queue. -- Dhaby Xiloj -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Feb 11 00:45:07 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Feb 2017 07:45:07 +0700 Subject: [Slackbuilds-users] Updates - 20170211.1 Message-ID: Hi Folks another great contributions for a week with almost 200 commits Lots of games updates from Hunter, LibreOffice 5.3.0.3 for source compilation, a couple of bug fix updates from user's report and the rest are just normal updates and new submission. gqrx is now renamed to gqrx-sdr so users using gqrx should take note on that change. As always, we welcome reports from users and also maintainers Sat Feb 11 00:25:34 UTC 2017 academic/CAPS_coevolution: Added (Coevolution Analysis). academic/mendeleydesktop: Updated for version 1.17.7. audio/drumkv1: Added (JACK/LV2 drum machine). audio/samplv1: Added (polyphonic sampler). audio/synthv1: Added (polyphonic synthesizer). audio/tuxguitar: Deleted unused patch. desktop/adwaita-qt: Added (KDE/QT Theme). desktop/mhsetroot: Added (sets background image ). desktop/neofetch: Fixed download. desktop/numix-folders: Updated for version 1.1.1.201702010031.197. desktop/qt5ct: Updated for version 0.30. desktop/screenkey: Fixed tarball handling. desktop/sgsearch: Added (search frontend). desktop/wmdl: New maintainer, add man page. desktop/wmsystemtray: Updated for version 1.4, new maintainer. desktop/wmtime: New maintainer, add multiple language support. development/Catch: Updated for version 1.7.1. development/antlr2: Added (parser generator). development/atom: Updated for version 1.14.1. development/camlp5: Updated for version 6.17. development/composer: Updated for version 1.3.2. development/dpkg: Updated for version 1.18.22. development/elixir: Updated for version 1.4.0. development/erlang-otp: Updated for version 19.2. development/ftnchek: New maintainer, minor fixes. development/gnuradio: Updated for version 3.7.10.1. development/google-go-lang: Updated for version 1.7.5. development/gr-osmosdr: Updated for version 2016.06.23. development/hackrf: Updated for version 2017.02.03. development/jupyter-notebook: Updated for version 4.3.2. development/mysql-workbench: Updated for version 6.3.9. development/nodejs: Updated for version 6.9.5. development/osmo-sdr: Updated for version 2015.12.11. development/pycharm: Updated for version 2016.3.2. development/sbcl: Fixed md5sum. development/scala: Updated for version 2.12.1. development/vscode: Updated for version 1.9.0. games/4do-libretro: Updated for version 2017.01.24_b8b029b. games/Craft-libretro: Updated for version 2017.01.20_4a11641. games/FlightGear-data: Updated for version 2016.4.4. games/FlightGear: Updated for version 2016.4.4. games/GLupeN64: Updated for version 2017.01.30_7b7cb25. games/QuickNES-Core: Updated for version 2017.01.24_f7238df. games/RetroArch: Updated for version 1.4.1. games/beetle-bsnes-libretro: Updated for version 2017.01.24_74d78da. games/beetle-gba-libretro: Updated for version 2017.01.24_1f948a6. games/beetle-lynx-libretro: Updated for version 2017.01.24_8ea8650. games/beetle-ngp-libretro: Updated for version 2017.01.24_66ef987. games/beetle-pcfx-libretro: Updated for version 2017.02.02_f53c58a. games/beetle-psx-libretro: Updated for version 2017.02.04_e3aae3d. games/beetle-saturn-libretro: Updated for v. 2017.01.24_bb5d0c1. games/beetle-supergrafx-libretro: Updated for v. 2017.01.24_1757cc3. games/beetle-vb-libretro: Updated for version 2017.01.24_1809ea7. games/beetle-wswan-libretro: Updated for version 2017.01.24_d106ea1. games/blastem-libretro: Updated for version 2017.01.24_7b6f4c5. games/blueMSX-libretro: Updated for version 2017.01.24_24144ba. games/bnes-libretro: Updated for version 2016.12.22_5197b6c. games/bsnes-libretro: Updated for version 2017.02.04_026fc306. games/bsnes-mercury: Updated for version 2017.02.04_4012862. games/doomsday: Fix REQUIRES, new maintainer. games/fbalpha: Updated for version 2017.01.25_c4c9fb5. games/fifengine: Updated for version 0.4.1. games/fmsx-libretro: Updated for version 2017.01.24_0386da0. games/fuse-emulator: Updated for version 1.3.3. games/gambatte-libretro: Updated for version 2017.02.03_b1af734. games/glPortal: Fixed tarball handling. games/gpsp-libretro: Updated for version 2017.01.24_c31b3e8. games/gw-libretro: Updated for version 2017.01.24_7e1c2a6. games/gzdoom: Use system fmodapi. games/libretro-2048: Added (2048 puzzle game libretro port). games/libretro-desmume: Updated for version 2017.01.24_62786c58. games/libretro-fceumm: Updated for version 2017.01.27_bdf5fa7. games/libretro-handy: Updated for version 2017.01.24_c55760b. games/libretro-lutro: Updated for version 2017.01.24_be1efa6. games/libretro-mgba: Updated for version 2017.02.01_998dc433. games/libretro-ppsspp: Updated for version 2016.12.14_5f7bcf7bf. games/libretro-prboom: Updated for version 2017.01.26_6384659. games/libretro-reicast: Updated for version 2017.01.26_148638c6. games/libretro-vecx: Updated for version 2017.01.24_30d39a0. games/libretro-yabause: Updated for version 2017.01.24_c8f4c573. games/mame2000-libretro: Updated for version 2017.01.27_1083de2. games/mame2010-libretro: Updated for version 2017.01.25_4776991. games/mame2014-libretro: Updated for version 2017.02.01_ee898d836c. games/mednafen: Updated for version 0.9.42. games/meteor-libretro: Updated for version 2017.01.24_b7f5c82. games/mgba: Updated for version 0.5.2. games/mupen64plus-libretro: Updated for version 2017.02.04_78f37eca. games/nestopia-libretro: Updated for version 2017.01.28_9d84c83. games/nxengine-libretro: Updated for version 2017.01.24_20f6aac. games/pcsx-rearmed: Updated for version 2017.01.29_731139f. games/pcsx2: Updated for version 2017.02.01_23d081ab2. games/picodrive-libretro: Updated for version 2016.12.10_d6be4fa. games/prosystem-libretro: Updated for version 2017.01.24_1cf5472. games/scummvm-libretro: Updated for version 2017.01.24_011f40ad0a. games/snes9x-libretro: Updated for version 2017.01.26_2d579c6. games/snes9x2002: Updated for version 2017.01.29_0c28605. games/snes9x2005: Updated for version 2017.01.29_b6006bc. games/snes9x2010: Updated for version 2017.02.04_9710b8f. games/stella-libretro: Updated for version 2017.01.24_cdbc9cc. games/tyrquake-libretro: Updated for version 2017.02.01_8cb9ceb. games/unknown-horizons: Updated for version 2017.2. games/vba-next: Updated for version 2017.01.23_e773475. games/vbam-libretro: Updated for version 2016.12.15_f3d150b. games/virtualjaguar-libretro: Updated for v. 2017.01.24_7697f9d. games/zdoom: Updated for version 2.8.1, new maintainer. gis/mapnik: Updated for version 3.0.13. gis/osgEarth: Updated for version 2.8. graphics/SweetHome3D: Updated for version 5.4. graphics/dia: Switch to i586. graphics/evolus-pencil: Fixed download + new maintainer. graphics/frescobaldi: Updated for version 2.19.0. graphics/gimagereader: Updated for version 3.2.1. graphics/pdf2svg: Fix DOWNLOAD url + switch to i586. graphics/qiv: Updated for v2.3.2pre20160530, new maintainer. graphics/rawtherapee: Updated for version 5.0.r1. ham/gqrx-sdr: Added (software defined radio receiver). ham/gqrx: Removed (renamed to gqrx-sdr). ham/rtl-sdr: Updated for version 2016.11.27. libraries/Hypodermic: Added (IoC container for C++). libraries/SimGear: Updated for version 2016.4.4. libraries/botocore: Updated for version 1.5.7. libraries/cpp-netlib: Added (The C++ Network Library Project). libraries/fifechan: Updated for version 0.1.4. libraries/fmodapi: Updated for version 4.44.61, new maintainer. libraries/ftplib: Updated for version 4.0.1. libraries/libaal: Updated for version 1.0.6. libraries/libhtp: Updated for version 0.5.23. libraries/libinput: Updated for version 1.6.1. libraries/libosmo-dsp: Updated for version 2016.12.30. libraries/libscca: Added (libYAL Windows Prefetch File parser). libraries/libuv: Updated for version 1.11.0. libraries/poco: Updated for version 1.7.7. libraries/podofo: Updated for version 0.9.5 libraries/rocksdb: Updated for version 5.1.2. libraries/webkit2gtk: Updated for version 2.14.4. misc/gr-iqbal: Updated for version 2015.11.20. misc/gramps: Updated for version 4.2.5. multimedia/coriander: Minor changes, added new optional dep. multimedia/dvdauthor: Remove unused patch. multimedia/opera-developer-ffmpeg-codecs: Fix build on x86. multimedia/opera-ffmpeg-codecs: Updated for version 56.0.2924.76. multimedia/vlc: Force use of Qt4 multimedia/youtube-viewer: Fix REQUIRES. network/Electrum: Updated for version 2.7.18. network/PaleMoon: Updated for version 27.1.0. network/awscli: Updated for version 1.11.44. network/c-toxcore: Updated for version 0.1.6. network/clipgrab: Updated for version 3.6.3. network/dropbox: Updated for version 19.4.13. network/nicotine+: Updated for version 1.4.0. network/opera-developer: Updated for version 44.0.2494.0. network/opera: Updated for version 43.0.2442.806. network/psad: Fixed slack-desc. network/pure-ftpd: Updated for version 1.0.45. network/tor: Update torrc sample file. office/LibreOffice: Updated for version 5.3.0.3 office/hunspell-es: Updated for version 2.2 + new maintainer. office/keepassxc: Updated for version 2.1.1. office/pdfstudio11: Updated for version 11.0.5. perl/perl-IO-Interface: Updated for version 1.09 + new maintainer. perl/perl-Math-BigInt-GMP: Updated for version 1.6004. perl/perl-Mojolicious: Updated for version 7.25. perl/perl-Net-Netmask: Updated for version 1.9022. perl/perl-extutils-makemaker: Updated for version 7.25.01. python/affine: Updated for version 2.0.0. python/construct: Downgraded for version 2.5.3. python/dotty: Added (Python query language). python/munch: Updated for version 2.1.0. python/python-distro: Updated for version 1.0.2. python/python-ly: Added (python parser for lilyPond files). python/python-parsedatetime: Update DEP. python/python-poppler-qt4: Updated for version 0.24.0. python/s3transfer: Updated for version 0.1.10. python/tox: Updated for version 2.6.0. ruby/heroku-client: Updated for version 3.43.16 system/dar: Updated for version 2.5.9. system/dehydrated: Updated for version 0.4.0. system/exfat-utils: Updated for version 1.2.6. system/fish: Updated for version 2.5.0. system/fuse-exfat: Updated for version 1.2.6. system/fzf: Updated for version 0.16.4. system/gtk-vnc: Updated for version 0.7.0. system/hh: Updated for version 1.22. system/kafka: Updated for version 0.10.1.1. system/letsencrypt: Updated for version 0.11.1. system/makepasswd: Updated for version 0.5.4, new maintainer. system/msr-tools: Added (access the processor MSRs and CPU ID). system/qdirstat: Updated for version 1.2. system/redis: Updated for version 3.2.7. system/reiser4progs: Updated for version 1.1.0. system/slpkg: Updated for version 3.2.3. system/spl-solaris: Updated for version 0.6.5.9. system/ttf-dark-courier: Added (HP font based on courier-new). system/yeahconsole: New maintainer, add man page, various fixes. system/zfs-on-linux: Updated for version 0.6.5.9. system/zookeeper: Updated for version 3.4.9. system/zstd: Updated for version 1.1.3. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Feb 11 00:45:50 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Feb 2017 07:45:50 +0700 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: <47d0bbe1-cfc4-1f36-6d74-5dd6ca83212c@gmail.com> <0f866c18-8930-d4cd-3661-d6419550f6db@sdf.org> Message-ID: <831af2cc-66d9-959b-990c-a52aa5d720ac@slackbuilds.org> > Thanks, I uploaded the new hunspell-es to SBo, and for now is in pending > queue. it's out now :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From reedych at reedych.pw Sat Feb 11 06:28:51 2017 From: reedych at reedych.pw (=?UTF-8?B?0KDQuNC00LjRhw==?=) Date: Sat, 11 Feb 2017 12:28:51 +0600 Subject: [Slackbuilds-users] Updates - 20170211.1 In-Reply-To: References: Message-ID: <04455b27-09f1-431e-899f-79e52b075ba7@reedych.pw> Hodiau are with small updates. On 11.02.2017 06:45, Willy Sudiarto Raharjo wrote: > Hi Folks > > another great contributions for a week with almost 200 commits > > Lots of games updates from Hunter, LibreOffice 5.3.0.3 for source > compilation, a couple of bug fix updates from user's report and the rest > are just normal updates and new submission. > > gqrx is now renamed to gqrx-sdr so users using gqrx should take note on > that change. > > As always, we welcome reports from users and also maintainers > > Sat Feb 11 00:25:34 UTC 2017 > academic/CAPS_coevolution: Added (Coevolution Analysis). > academic/mendeleydesktop: Updated for version 1.17.7. > audio/drumkv1: Added (JACK/LV2 drum machine). > audio/samplv1: Added (polyphonic sampler). > audio/synthv1: Added (polyphonic synthesizer). > audio/tuxguitar: Deleted unused patch. > desktop/adwaita-qt: Added (KDE/QT Theme). > desktop/mhsetroot: Added (sets background image ). > desktop/neofetch: Fixed download. > desktop/numix-folders: Updated for version 1.1.1.201702010031.197. > desktop/qt5ct: Updated for version 0.30. > desktop/screenkey: Fixed tarball handling. > desktop/sgsearch: Added (search frontend). > desktop/wmdl: New maintainer, add man page. > desktop/wmsystemtray: Updated for version 1.4, new maintainer. > desktop/wmtime: New maintainer, add multiple language support. > development/Catch: Updated for version 1.7.1. > development/antlr2: Added (parser generator). > development/atom: Updated for version 1.14.1. > development/camlp5: Updated for version 6.17. > development/composer: Updated for version 1.3.2. > development/dpkg: Updated for version 1.18.22. > development/elixir: Updated for version 1.4.0. > development/erlang-otp: Updated for version 19.2. > development/ftnchek: New maintainer, minor fixes. > development/gnuradio: Updated for version 3.7.10.1. > development/google-go-lang: Updated for version 1.7.5. > development/gr-osmosdr: Updated for version 2016.06.23. > development/hackrf: Updated for version 2017.02.03. > development/jupyter-notebook: Updated for version 4.3.2. > development/mysql-workbench: Updated for version 6.3.9. > development/nodejs: Updated for version 6.9.5. > development/osmo-sdr: Updated for version 2015.12.11. > development/pycharm: Updated for version 2016.3.2. > development/sbcl: Fixed md5sum. > development/scala: Updated for version 2.12.1. > development/vscode: Updated for version 1.9.0. > games/4do-libretro: Updated for version 2017.01.24_b8b029b. > games/Craft-libretro: Updated for version 2017.01.20_4a11641. > games/FlightGear-data: Updated for version 2016.4.4. > games/FlightGear: Updated for version 2016.4.4. > games/GLupeN64: Updated for version 2017.01.30_7b7cb25. > games/QuickNES-Core: Updated for version 2017.01.24_f7238df. > games/RetroArch: Updated for version 1.4.1. > games/beetle-bsnes-libretro: Updated for version 2017.01.24_74d78da. > games/beetle-gba-libretro: Updated for version 2017.01.24_1f948a6. > games/beetle-lynx-libretro: Updated for version 2017.01.24_8ea8650. > games/beetle-ngp-libretro: Updated for version 2017.01.24_66ef987. > games/beetle-pcfx-libretro: Updated for version 2017.02.02_f53c58a. > games/beetle-psx-libretro: Updated for version 2017.02.04_e3aae3d. > games/beetle-saturn-libretro: Updated for v. 2017.01.24_bb5d0c1. > games/beetle-supergrafx-libretro: Updated for v. 2017.01.24_1757cc3. > games/beetle-vb-libretro: Updated for version 2017.01.24_1809ea7. > games/beetle-wswan-libretro: Updated for version 2017.01.24_d106ea1. > games/blastem-libretro: Updated for version 2017.01.24_7b6f4c5. > games/blueMSX-libretro: Updated for version 2017.01.24_24144ba. > games/bnes-libretro: Updated for version 2016.12.22_5197b6c. > games/bsnes-libretro: Updated for version 2017.02.04_026fc306. > games/bsnes-mercury: Updated for version 2017.02.04_4012862. > games/doomsday: Fix REQUIRES, new maintainer. > games/fbalpha: Updated for version 2017.01.25_c4c9fb5. > games/fifengine: Updated for version 0.4.1. > games/fmsx-libretro: Updated for version 2017.01.24_0386da0. > games/fuse-emulator: Updated for version 1.3.3. > games/gambatte-libretro: Updated for version 2017.02.03_b1af734. > games/glPortal: Fixed tarball handling. > games/gpsp-libretro: Updated for version 2017.01.24_c31b3e8. > games/gw-libretro: Updated for version 2017.01.24_7e1c2a6. > games/gzdoom: Use system fmodapi. > games/libretro-2048: Added (2048 puzzle game libretro port). > games/libretro-desmume: Updated for version 2017.01.24_62786c58. > games/libretro-fceumm: Updated for version 2017.01.27_bdf5fa7. > games/libretro-handy: Updated for version 2017.01.24_c55760b. > games/libretro-lutro: Updated for version 2017.01.24_be1efa6. > games/libretro-mgba: Updated for version 2017.02.01_998dc433. > games/libretro-ppsspp: Updated for version 2016.12.14_5f7bcf7bf. > games/libretro-prboom: Updated for version 2017.01.26_6384659. > games/libretro-reicast: Updated for version 2017.01.26_148638c6. > games/libretro-vecx: Updated for version 2017.01.24_30d39a0. > games/libretro-yabause: Updated for version 2017.01.24_c8f4c573. > games/mame2000-libretro: Updated for version 2017.01.27_1083de2. > games/mame2010-libretro: Updated for version 2017.01.25_4776991. > games/mame2014-libretro: Updated for version 2017.02.01_ee898d836c. > games/mednafen: Updated for version 0.9.42. > games/meteor-libretro: Updated for version 2017.01.24_b7f5c82. > games/mgba: Updated for version 0.5.2. > games/mupen64plus-libretro: Updated for version 2017.02.04_78f37eca. > games/nestopia-libretro: Updated for version 2017.01.28_9d84c83. > games/nxengine-libretro: Updated for version 2017.01.24_20f6aac. > games/pcsx-rearmed: Updated for version 2017.01.29_731139f. > games/pcsx2: Updated for version 2017.02.01_23d081ab2. > games/picodrive-libretro: Updated for version 2016.12.10_d6be4fa. > games/prosystem-libretro: Updated for version 2017.01.24_1cf5472. > games/scummvm-libretro: Updated for version 2017.01.24_011f40ad0a. > games/snes9x-libretro: Updated for version 2017.01.26_2d579c6. > games/snes9x2002: Updated for version 2017.01.29_0c28605. > games/snes9x2005: Updated for version 2017.01.29_b6006bc. > games/snes9x2010: Updated for version 2017.02.04_9710b8f. > games/stella-libretro: Updated for version 2017.01.24_cdbc9cc. > games/tyrquake-libretro: Updated for version 2017.02.01_8cb9ceb. > games/unknown-horizons: Updated for version 2017.2. > games/vba-next: Updated for version 2017.01.23_e773475. > games/vbam-libretro: Updated for version 2016.12.15_f3d150b. > games/virtualjaguar-libretro: Updated for v. 2017.01.24_7697f9d. > games/zdoom: Updated for version 2.8.1, new maintainer. > gis/mapnik: Updated for version 3.0.13. > gis/osgEarth: Updated for version 2.8. > graphics/SweetHome3D: Updated for version 5.4. > graphics/dia: Switch to i586. > graphics/evolus-pencil: Fixed download + new maintainer. > graphics/frescobaldi: Updated for version 2.19.0. > graphics/gimagereader: Updated for version 3.2.1. > graphics/pdf2svg: Fix DOWNLOAD url + switch to i586. > graphics/qiv: Updated for v2.3.2pre20160530, new maintainer. > graphics/rawtherapee: Updated for version 5.0.r1. > ham/gqrx-sdr: Added (software defined radio receiver). > ham/gqrx: Removed (renamed to gqrx-sdr). > ham/rtl-sdr: Updated for version 2016.11.27. > libraries/Hypodermic: Added (IoC container for C++). > libraries/SimGear: Updated for version 2016.4.4. > libraries/botocore: Updated for version 1.5.7. > libraries/cpp-netlib: Added (The C++ Network Library Project). > libraries/fifechan: Updated for version 0.1.4. > libraries/fmodapi: Updated for version 4.44.61, new maintainer. > libraries/ftplib: Updated for version 4.0.1. > libraries/libaal: Updated for version 1.0.6. > libraries/libhtp: Updated for version 0.5.23. > libraries/libinput: Updated for version 1.6.1. > libraries/libosmo-dsp: Updated for version 2016.12.30. > libraries/libscca: Added (libYAL Windows Prefetch File parser). > libraries/libuv: Updated for version 1.11.0. > libraries/poco: Updated for version 1.7.7. > libraries/podofo: Updated for version 0.9.5 > libraries/rocksdb: Updated for version 5.1.2. > libraries/webkit2gtk: Updated for version 2.14.4. > misc/gr-iqbal: Updated for version 2015.11.20. > misc/gramps: Updated for version 4.2.5. > multimedia/coriander: Minor changes, added new optional dep. > multimedia/dvdauthor: Remove unused patch. > multimedia/opera-developer-ffmpeg-codecs: Fix build on x86. > multimedia/opera-ffmpeg-codecs: Updated for version 56.0.2924.76. > multimedia/vlc: Force use of Qt4 > multimedia/youtube-viewer: Fix REQUIRES. > network/Electrum: Updated for version 2.7.18. > network/PaleMoon: Updated for version 27.1.0. > network/awscli: Updated for version 1.11.44. > network/c-toxcore: Updated for version 0.1.6. > network/clipgrab: Updated for version 3.6.3. > network/dropbox: Updated for version 19.4.13. > network/nicotine+: Updated for version 1.4.0. > network/opera-developer: Updated for version 44.0.2494.0. > network/opera: Updated for version 43.0.2442.806. > network/psad: Fixed slack-desc. > network/pure-ftpd: Updated for version 1.0.45. > network/tor: Update torrc sample file. > office/LibreOffice: Updated for version 5.3.0.3 > office/hunspell-es: Updated for version 2.2 + new maintainer. > office/keepassxc: Updated for version 2.1.1. > office/pdfstudio11: Updated for version 11.0.5. > perl/perl-IO-Interface: Updated for version 1.09 + new maintainer. > perl/perl-Math-BigInt-GMP: Updated for version 1.6004. > perl/perl-Mojolicious: Updated for version 7.25. > perl/perl-Net-Netmask: Updated for version 1.9022. > perl/perl-extutils-makemaker: Updated for version 7.25.01. > python/affine: Updated for version 2.0.0. > python/construct: Downgraded for version 2.5.3. > python/dotty: Added (Python query language). > python/munch: Updated for version 2.1.0. > python/python-distro: Updated for version 1.0.2. > python/python-ly: Added (python parser for lilyPond files). > python/python-parsedatetime: Update DEP. > python/python-poppler-qt4: Updated for version 0.24.0. > python/s3transfer: Updated for version 0.1.10. > python/tox: Updated for version 2.6.0. > ruby/heroku-client: Updated for version 3.43.16 > system/dar: Updated for version 2.5.9. > system/dehydrated: Updated for version 0.4.0. > system/exfat-utils: Updated for version 1.2.6. > system/fish: Updated for version 2.5.0. > system/fuse-exfat: Updated for version 1.2.6. > system/fzf: Updated for version 0.16.4. > system/gtk-vnc: Updated for version 0.7.0. > system/hh: Updated for version 1.22. > system/kafka: Updated for version 0.10.1.1. > system/letsencrypt: Updated for version 0.11.1. > system/makepasswd: Updated for version 0.5.4, new maintainer. > system/msr-tools: Added (access the processor MSRs and CPU ID). > system/qdirstat: Updated for version 1.2. > system/redis: Updated for version 3.2.7. > system/reiser4progs: Updated for version 1.1.0. > system/slpkg: Updated for version 3.2.3. > system/spl-solaris: Updated for version 0.6.5.9. > system/ttf-dark-courier: Added (HP font based on courier-new). > system/yeahconsole: New maintainer, add man page, various fixes. > system/zfs-on-linux: Updated for version 0.6.5.9. > system/zookeeper: Updated for version 3.4.9. > system/zstd: Updated for version 1.1.3. > +--------------------------+ > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Sat Feb 11 09:52:59 2017 From: yalhcru at gmail.com (B Watson) Date: Sat, 11 Feb 2017 04:52:59 -0500 Subject: [Slackbuilds-users] Fwd: reiser4progs and libaal getting long in the tooth In-Reply-To: References: Message-ID: On 2/10/17, Willy Sudiarto Raharjo wrote: > bumped to 1.0.6 and 1.10 Hm. Mind if I send you a patch for reiser4progs? It's needed for anything that wants to link with -lreiser4 (specifically, partclone, which would then be able to back up reiser 4 partitions). I don't want to take maintenance of reiser4progs, that should go to someone who actually uses reiser4. From willysr at slackbuilds.org Sat Feb 11 10:01:32 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Feb 2017 17:01:32 +0700 Subject: [Slackbuilds-users] Fwd: reiser4progs and libaal getting long in the tooth In-Reply-To: References: Message-ID: <73695006-f985-e05b-4df3-44bf8f668995@slackbuilds.org> > Hm. Mind if I send you a patch for reiser4progs? It's needed for anything > that wants to link with -lreiser4 (specifically, partclone, which would > then be able to back up reiser 4 partitions). > > I don't want to take maintenance of reiser4progs, that should go to > someone who actually uses reiser4. Sure, push it to a different branch with a -review at the back and i will merge it to my branch after reviewing it. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From Jim.Diamond at acadiau.ca Sat Feb 11 16:10:46 2017 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 11 Feb 2017 12:10:46 -0400 Subject: [Slackbuilds-users] compiling dvdauthor 0.7.1 crashes and burns Message-ID: <20170211161046.GA6967@jdiamond-nb.acadiau.ca> Hi, on a Slackware64 14.2 system (no multi-lib), sboupgrade, after a while it gets to libtool: link: gcc -Wall -O2 -fPIC -o dvdauthor dvdauthor.o dvdcompile.o dvdvml.o dvdvmy.o dvdifo.o dvdvob.o dvdpgc.o dvdcli.o readxml.o conffile.o compat.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -lm -ldl -pthread mv -f .deps/mpeg2desc.Tpo .deps/mpeg2desc.Po /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -O2 -fPIC -o mpeg2desc mpeg2desc.o compat.o libtool: link: gcc -Wall -O2 -fPIC -o mpeg2desc mpeg2desc.o compat.o mv -f .deps/spuunmux-spuunmux.Tpo .deps/spuunmux-spuunmux.Po /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/include/libpng16 -Wall -O2 -fPIC -o spuunmux spuunmux-spuunmux.o spuunmux-compat.o spuunmux-conffile.o -lpng16 mv -f .deps/dvdunauthor.Tpo .deps/dvdunauthor.Po mv -f .deps/subreader.Tpo .deps/subreader.Po /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -O2 -fPIC -o spumux subgen.o subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o compat.o subrender.o subreader.o subfont.o -lxml2 -lz -llzma -lm -ldl -lMagickCore-6.Q16 -lMagickCore-6.Q16 -lfreetype -lfribidi -lglib-2.0 -lfontconfig -lfreetype -lm libtool: link: gcc -I/usr/include/libpng16 -Wall -O2 -fPIC -o spuunmux spuunmux-spuunmux.o spuunmux-compat.o spuunmux-conffile.o /usr/lib64/libpng16.so mv -f .deps/dvduncompile.Tpo .deps/dvduncompile.Po /bin/sh ../libtool --tag=CC --mode=link gcc -Wall -O2 -fPIC -o dvdunauthor dvdunauthor.o dvduncompile.o compat.o -lxml2 -lz -llzma -lm -ldl -ldvdread libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -ldl -lMagickCore-6.Q16 /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `DestroyPixelWand' /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `PixelSetColor' /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `DrawSetStrokeWidth' /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `DrawRectangle' and after a bunch of undefined reference lines it says /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `AcquireDrawingWand' collect2: error: ld returned 1 exit status make[2]: *** [spumux] Error 1 Makefile:523: recipe for target 'spumux' failed make[2]: *** Waiting for unfinished jobs.... libtool: link: gcc -Wall -O2 -fPIC -o dvdunauthor dvdunauthor.o dvduncompile.o compat.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -lm -ldl /usr/lib64/libdvdread.so -pthread make[2]: Leaving directory '/tmp/SBo/dvdauthor/src' make[1]: *** [all] Error 2 Makefile:412: recipe for target 'all' failed make[1]: Leaving directory '/tmp/SBo/dvdauthor/src' make: *** [all-recursive] Error 1 Makefile:414: recipe for target 'all-recursive' failed Failures: dvdauthor: dvdauthor.SlackBuild return non-zero - sboupgrade dvdauthor 13.18s user 1.18s system 136% cpu 10.527 total I read a few articles with various opinions of the Right Thing To Do on other systems compiling other things. However... presumably this worked for at least the maintainer on a Slackware 14.2 system. Anyone solved this and care to share the solution? Thanks. Jim From baildon.research at googlemail.com Sat Feb 11 17:07:49 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 11 Feb 2017 17:07:49 +0000 Subject: [Slackbuilds-users] compiling dvdauthor 0.7.1 crashes and burns In-Reply-To: <20170211161046.GA6967@jdiamond-nb.acadiau.ca> References: <20170211161046.GA6967@jdiamond-nb.acadiau.ca> Message-ID: > libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -ldl -lMagickCore-6.Q16 /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `DestroyPixelWand' > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `PixelSetColor' For me, the link looks like this, with no reference to -lMagickCore-6.Q16 libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -ldl /usr/lib64/libpng16.so /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread I'd be interested to know what your configure output looks like round about this point: checking for getopt_long... yes checking for setmode... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for LIBPNG... yes checking for MagickCore-config... MagickCore-config checking for ExportImagePixels... no configure: ImageMagick does not support the function ExportImagePixels. Please upgrade to ImageMagick 5.5.7 or newer checking for MAGICK... no checking for FONTCONFIG... yes checking for FRIBIDI... yes checking for freetype-config... freetype-config checking ft2build.h usability... yes checking ft2build.h presence... yes checking for ft2build.h... yes ... and whether the version of imagemagick you have installed is imagemagick-6.9.4_9-x86_64-1 Interestingly, the message "Please upgrade to ImageMagick 5.5.7 or newer" is bogus, but this seems to be the reason why it Works For Me Hmmmm -D. From kingbeowulf at gmail.com Sat Feb 11 18:26:49 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 11 Feb 2017 10:26:49 -0800 Subject: [Slackbuilds-users] compiling dvdauthor 0.7.1 crashes and burns In-Reply-To: References: <20170211161046.GA6967@jdiamond-nb.acadiau.ca> Message-ID: On 02/11/2017 09:07 AM, David Spencer wrote: >> libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -ldl -lMagickCore-6.Q16 /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `DestroyPixelWand' >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `PixelSetColor' > > For me, the link looks like this, with no reference to -lMagickCore-6.Q16 > > libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o > subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o > compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz > /usr/lib64/liblzma.so -ldl /usr/lib64/libpng16.so > /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so > /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread > --snip-- Please upgrade to 14.2 > Multimedia > dvdauthor (0.7.2) since this should have been corrected upstream (missing header file defines). Then send me a bug report, if any. if on 14.1, upgrade anyway. Thanks Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Sat Feb 11 20:23:23 2017 From: yalhcru at gmail.com (B Watson) Date: Sat, 11 Feb 2017 15:23:23 -0500 Subject: [Slackbuilds-users] Pablo Santamaria's builds In-Reply-To: References: Message-ID: On 2/7/17, B Watson wrote: > games/advancescan (unless the advancemame maintainer wants it, but > advancemame hasn't been updated since May 2010! Anyone > want to grab them both? I've already got one mame, I > don't need another. Doogster?) OK, I played with advancemame a bit today, got a nice working script for it, so I will take it and advancescan after all. From alleytrotter at gmail.com Sun Feb 12 01:05:02 2017 From: alleytrotter at gmail.com (John Yost) Date: Sat, 11 Feb 2017 20:05:02 -0500 Subject: [Slackbuilds-users] (no subject) Message-ID: On Sat, Feb 11, 2017 at 03:00:23PM -0500, John wrote: > When using a slackbuild what is the proper base system > Is it a full install of 14.2? > Or is it a full install with all updates posted by Pat? This is not the proper address for such questions, but see the Slackbuilds HOWTO and FAQ links on the web site. If you still have questions, subscribe to the users' mailing list, http://lists.slackbuilds.org/ and ask there. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org Actually I could not find the answer in the FAQ or the HOWTO. Does not seem to address the issue of updates. Sorry I used the wrong email. -- John David Yost AlleyTrotter pub 2048D/F3BDEB55 2014-05-23 [expires: Never] -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xF3BDEB55.asc Type: application/pgp-keys Size: 2312 bytes Desc: not available URL: From willysr at slackbuilds.org Sun Feb 12 02:19:19 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 12 Feb 2017 09:19:19 +0700 Subject: [Slackbuilds-users] (no subject) In-Reply-To: References: Message-ID: <5492f4b5-06b3-8bb0-1605-08b628e5454e@slackbuilds.org> >> When using a slackbuild what is the proper base system >> Is it a full install of 14.2? >> Or is it a full install with all updates posted by Pat? > > This is not the proper address for such questions, but see the > Slackbuilds HOWTO and FAQ links on the web site. If you still have > questions, subscribe to the users' mailing list, > > http://lists.slackbuilds.org/ > > and ask there. It's listed here on the very top https://slackbuilds.org/howto/ and also on the very bottom here https://slackbuilds.org/faq/#full -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Sun Feb 12 02:28:51 2017 From: yalhcru at gmail.com (B Watson) Date: Sat, 11 Feb 2017 21:28:51 -0500 Subject: [Slackbuilds-users] (no subject) In-Reply-To: <5492f4b5-06b3-8bb0-1605-08b628e5454e@slackbuilds.org> References: <5492f4b5-06b3-8bb0-1605-08b628e5454e@slackbuilds.org> Message-ID: On 2/11/17, Willy Sudiarto Raharjo wrote: > It's listed here on the very top > https://slackbuilds.org/howto/ " All of our scripts are written and tested for usage on the latest stble release of Slackware with full installation" > and also on the very bottom here > https://slackbuilds.org/faq/#full " All scripts are tested against a full installation of Slackware (all default install groups)." Neither of those answered the question he was asking. Does "a full install" mean "an unpatched system, exactly as released, just after being installed from DVD", or does it mean "a full install, with the latest patches from Pat's patches/ dir"? I've always assumed the latter: scripts are expected to work on a fully patched system, and it's a bug if they don't. Doing it the other way, expecting everyone to keep an unpatched system, would be insane (who doesn't apply at least security patches to their OS?) In most cases, the difference is no difference (Pat's very good at keeping patches from breaking things). But in the rare case where it does matter, if a build maintainer has to make a choice (script has to be broken on one or the other), the system with the latest patches should be the primary targer. But, to the original poster: That's just my opinion, I don't speak for the SBo team. I'm wrong all the time, so don't take it as a definitive answer. From willysr at slackbuilds.org Sun Feb 12 02:31:21 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 12 Feb 2017 09:31:21 +0700 Subject: [Slackbuilds-users] (no subject) In-Reply-To: References: <5492f4b5-06b3-8bb0-1605-08b628e5454e@slackbuilds.org> Message-ID: <64472064-c36d-1379-49ee-7a1659d469f0@slackbuilds.org> > Neither of those answered the question he was asking. Does "a full > install" mean "an unpatched system, exactly as released, just after > being installed from DVD", or does it mean "a full install, with the > latest patches from Pat's patches/ dir"? > > I've always assumed the latter: scripts are expected to work on a fully > patched system, and it's a bug if they don't. Doing it the other way, > expecting everyone to keep an unpatched system, would be insane (who > doesn't apply at least security patches to their OS?) > > In most cases, the difference is no difference (Pat's very good at > keeping patches from breaking things). But in the rare case where it > does matter, if a build maintainer has to make a choice (script has > to be broken on one or the other), the system with the latest patches > should be the primary targer. > > But, to the original poster: That's just my opinion, I don't speak for the > SBo team. I'm wrong all the time, so don't take it as a definitive answer. fully patched, but yeah, Pat RARELY introduce a change on stable releases except when it's already few years old, so that's good thing. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From alleytrotter at gmail.com Sun Feb 12 03:53:20 2017 From: alleytrotter at gmail.com (John Yost) Date: Sat, 11 Feb 2017 22:53:20 -0500 Subject: [Slackbuilds-users] (no subject) In-Reply-To: <64472064-c36d-1379-49ee-7a1659d469f0@slackbuilds.org> References: <5492f4b5-06b3-8bb0-1605-08b628e5454e@slackbuilds.org> <64472064-c36d-1379-49ee-7a1659d469f0@slackbuilds.org> Message-ID: <829e14c7-5556-b930-3d3c-1f79be195eb1@gmail.com> On 02/11/2017 09:31 PM, Willy Sudiarto Raharjo wrote: >> Neither of those answered the question he was asking. Does "a full >> install" mean "an unpatched system, exactly as released, just after >> being installed from DVD", or does it mean "a full install, with the >> latest patches from Pat's patches/ dir"? >> >> I've always assumed the latter: scripts are expected to work on a fully >> patched system, and it's a bug if they don't. Doing it the other way, >> expecting everyone to keep an unpatched system, would be insane (who >> doesn't apply at least security patches to their OS?) >> >> In most cases, the difference is no difference (Pat's very good at >> keeping patches from breaking things). But in the rare case where it >> does matter, if a build maintainer has to make a choice (script has >> to be broken on one or the other), the system with the latest patches >> should be the primary targer. >> >> But, to the original poster: That's just my opinion, I don't speak for the >> SBo team. I'm wrong all the time, so don't take it as a definitive answer. > > fully patched, but yeah, Pat RARELY introduce a change on stable > releases except when it's already few years old, so that's good thing. > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Thanks very much Mr. Watson you did interpret my question as intended. I also run a full installation of Slackware with PV's patches I had a problem building the most recent Libreoffice.Slackbuild on my patched system, but it did build on a fresh installation on a qemu virtual machine without the patches. That is what brought the question to mind. However my system may not be perfect with regards to other software (ie non-SBo). I just wanted to establish the same starting point as the maintainer. Now I can try to track down the problem with my system or the slackbuild. Thanks again for your kind reply John From alleytrotter at gmail.com Sun Feb 12 04:14:54 2017 From: alleytrotter at gmail.com (John Yost) Date: Sat, 11 Feb 2017 23:14:54 -0500 Subject: [Slackbuilds-users] Fwd: Re: (no subject) In-Reply-To: <829e14c7-5556-b930-3d3c-1f79be195eb1@gmail.com> References: <829e14c7-5556-b930-3d3c-1f79be195eb1@gmail.com> Message-ID: <4992041d-adbe-793a-4c2a-813bcc2b392a@gmail.com> -------- Forwarded Message -------- Subject: Re: [Slackbuilds-users] (no subject) Date: Sat, 11 Feb 2017 22:53:20 -0500 From: John Yost To: slackbuilds-users at slackbuilds.org On 02/11/2017 09:31 PM, Willy Sudiarto Raharjo wrote: >> Neither of those answered the question he was asking. Does "a full >> install" mean "an unpatched system, exactly as released, just after >> being installed from DVD", or does it mean "a full install, with the >> latest patches from Pat's patches/ dir"? >> >> I've always assumed the latter: scripts are expected to work on a fully >> patched system, and it's a bug if they don't. Doing it the other way, >> expecting everyone to keep an unpatched system, would be insane (who >> doesn't apply at least security patches to their OS?) >> >> In most cases, the difference is no difference (Pat's very good at >> keeping patches from breaking things). But in the rare case where it >> does matter, if a build maintainer has to make a choice (script has >> to be broken on one or the other), the system with the latest patches >> should be the primary targer. >> >> But, to the original poster: That's just my opinion, I don't speak for the >> SBo team. I'm wrong all the time, so don't take it as a definitive answer. > > fully patched, but yeah, Pat RARELY introduce a change on stable > releases except when it's already few years old, so that's good thing. > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Thanks very much Mr. Watson you did interpret my question as intended. I also run a full installation of Slackware with PV's patches I had a problem building the most recent Libreoffice.Slackbuild on my patched system, but it did build on a fresh installation on a qemu virtual machine without the patches. That is what brought the question to mind. However my system may not be perfect with regards to other software (ie non-SBo). I just wanted to establish the same starting point as the maintainer. Now I can try to track down the problem with my system or the slackbuild. Thanks again for your kind reply John -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xF3BDEB55.asc Type: application/pgp-keys Size: 2312 bytes Desc: not available URL: From chris.willing at iinet.net.au Sun Feb 12 08:21:57 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 12 Feb 2017 18:21:57 +1000 Subject: [Slackbuilds-users] (no subject) In-Reply-To: <829e14c7-5556-b930-3d3c-1f79be195eb1@gmail.com> References: <5492f4b5-06b3-8bb0-1605-08b628e5454e@slackbuilds.org> <64472064-c36d-1379-49ee-7a1659d469f0@slackbuilds.org> <829e14c7-5556-b930-3d3c-1f79be195eb1@gmail.com> Message-ID: <9438af66-2be3-5eef-6aa1-791ad0a2d2d6@iinet.net.au> On 12/02/17 13:53, John Yost wrote: [snip] > > Thanks very much Mr. Watson you did interpret my question as intended. > I also run a full installation of Slackware with PV's patches > I had a problem building the most recent Libreoffice.Slackbuild on my > patched system, but it did build on a fresh installation on a qemu > virtual machine without the patches. That is what brought the question > to mind. Hi John, Feel free to contact me directly about your LibreOffice build issue at the contact address in the LibreOffice.info file. I'm aiming to make the build process as painless as possible and a build failure certainly doesn't fulfill that aim. chris From chris.willing at iinet.net.au Sun Feb 12 10:12:26 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 12 Feb 2017 20:12:26 +1000 Subject: [Slackbuilds-users] compiling dvdauthor 0.7.1 crashes and burns In-Reply-To: References: <20170211161046.GA6967@jdiamond-nb.acadiau.ca> Message-ID: <55b60c52-1eb4-da70-86d7-590c8b409f05@iinet.net.au> On 12/02/17 04:26, King Beowulf wrote: > On 02/11/2017 09:07 AM, David Spencer wrote: >>> libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -ldl -lMagickCore-6.Q16 /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `DestroyPixelWand' >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `PixelSetColor' >> >> For me, the link looks like this, with no reference to -lMagickCore-6.Q16 >> >> libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o >> subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o >> compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz >> /usr/lib64/liblzma.so -ldl /usr/lib64/libpng16.so >> /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so >> /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread >> > --snip-- > > Please upgrade to > > 14.2 > Multimedia > dvdauthor (0.7.2) > > since this should have been corrected upstream (missing header file > defines). Then send me a bug report, if any. if on 14.1, upgrade anyway. > I saw the same problem as Jim (for dvdauthor-0.7.2). In my case, it was due to the presence of GraphicsMagick in the build environment; when removed, the build succeeded. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From edps.mundognu at gmail.com Sun Feb 12 10:45:15 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Sun, 12 Feb 2017 08:45:15 -0200 Subject: [Slackbuilds-users] Opera Developer sources Message-ID: Hi people, the sources for opera-developer-ffmpeg-codecs was removed from http://repo.herecura.be, for now i'm request change URLs in opera-developer-ffmpeg-codecs.info for this: DOWNLOAD="http://slackware.uk/sbosrcarch/by-name/multimedia/opera-developer-ffmpeg-codecs/opera-developer-ffmpeg-codecs-57.0.2970.0-1-i686.pkg.tar.xz" DOWNLOAD_x86_64="http://slackware.uk/sbosrcarch/by-name/multimedia/opera-developer-ffmpeg-codecs/opera-developer-ffmpeg-codecs-57.0.2970.0-1-x86_64.pkg.tar.xz" or DOWNLOAD="http://slackware.uk/sbosrcarch/by-md5/7/5/750ffa5d9c72ba482446e47bac365962/opera-developer-ffmpeg-codecs-57.0.2970.0-1-i686.pkg.tar.xz" DOWNLOAD_x86_64="http://slackware.uk/sbosrcarch/by-md5/e/7/e7b6b3ead534b6e3df9734a0dc8abe3d/opera-developer-ffmpeg-codecs-57.0.2970.0-1-x86_64.pkg.tar.xz" In the next days i will send new update for version 57.0.2979.0: http://repo.herecura.be/herecura/i686/opera-developer-ffmpeg-codecs-57.0.2979.0-1-i686.pkg.tar.xz md5sum: ddbbf07bc54de57c202da84a810b5f87 http://repo.herecura.be/herecura/x86_64/opera-developer-ffmpeg-codecs-57.0.2979.0-1-x86_64.pkg.tar.xz md5sum: 0f0cf4a928bf95a1e917b9832f973080 Thanks! From johnyost at ptd.net Sun Feb 12 01:00:26 2017 From: johnyost at ptd.net (John) Date: Sat, 11 Feb 2017 20:00:26 -0500 Subject: [Slackbuilds-users] Fwd: Re: Slackbuild Usage In-Reply-To: <20170211231952.GR8339@harrier.slackbuilds.org> References: <20170211231952.GR8339@harrier.slackbuilds.org> Message-ID: <0f9fb4fe-a783-2ace-89f0-2f7c2ef7b980@ptd.net> -------- Forwarded Message -------- Subject: Re: Slackbuild Usage Date: Sat, 11 Feb 2017 17:19:52 -0600 From: Rob McGee Organization: slackbuilds.org To: John CC: postmaster at slackbuilds.org On Sat, Feb 11, 2017 at 03:00:23PM -0500, John wrote: > When using a slackbuild what is the proper base system > Is it a full install of 14.2? > Or is it a full install with all updates posted by Pat? This is not the proper address for such questions, but see the Slackbuilds HOWTO and FAQ links on the web site. If you still have questions, subscribe to the users' mailing list, http://lists.slackbuilds.org/ and ask there. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org proper proper please -- John David Yost AlleyTrotter pub 2048D/F3BDEB55 2014-05-23 [expires: Never] -------------- next part -------------- A non-text attachment was scrubbed... Name: 0xF3BDEB55.asc Type: application/pgp-keys Size: 2312 bytes Desc: not available URL: From Jim.Diamond at acadiau.ca Sun Feb 12 16:34:16 2017 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sun, 12 Feb 2017 12:34:16 -0400 Subject: [Slackbuilds-users] compiling dvdauthor 0.7.1 crashes and burns In-Reply-To: <55b60c52-1eb4-da70-86d7-590c8b409f05@iinet.net.au> References: <20170211161046.GA6967@jdiamond-nb.acadiau.ca> <55b60c52-1eb4-da70-86d7-590c8b409f05@iinet.net.au> Message-ID: <20170212163416.GA26091@jdiamond-nb.acadiau.ca> On Sun, Feb 12, 2017 at 20:12 (+1000), Christoph Willing wrote: > On 12/02/17 04:26, King Beowulf wrote: >> On 02/11/2017 09:07 AM, David Spencer wrote: >>>> libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz /usr/lib64/liblzma.so -ldl -lMagickCore-6.Q16 /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `DestroyPixelWand' >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libMagickCore-6.Q16.so: undefined reference to `PixelSetColor' >>> For me, the link looks like this, with no reference to -lMagickCore-6.Q16 >>> libtool: link: gcc -Wall -O2 -fPIC -o spumux subgen.o >>> subgen-parse-xml.o readxml.o subgen-encode.o subgen-image.o conffile.o >>> compat.o subrender.o subreader.o subfont.o /usr/lib64/libxml2.so -lz >>> /usr/lib64/liblzma.so -ldl /usr/lib64/libpng16.so >>> /usr/lib64/libfribidi.so /usr/lib64/libglib-2.0.so >>> /usr/lib64/libfontconfig.so /usr/lib64/libfreetype.so -lm -pthread >> --snip-- >> Please upgrade to >> 14.2 > Multimedia > dvdauthor (0.7.2) >> since this should have been corrected upstream (missing header file >> defines). Then send me a bug report, if any. if on 14.1, upgrade anyway. > I saw the same problem as Jim (for dvdauthor-0.7.2). In my case, it was > due to the presence of GraphicsMagick in the build environment; when > removed, the build succeeded. Thanks Chris, removing GraphicsMagick allowed dvdauthor to build without any problems. Jim From matteo.bernardini at gmail.com Sun Feb 12 16:41:15 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 12 Feb 2017 17:41:15 +0100 Subject: [Slackbuilds-users] Fwd: Re: Slackbuild Usage In-Reply-To: <0f9fb4fe-a783-2ace-89f0-2f7c2ef7b980@ptd.net> References: <20170211231952.GR8339@harrier.slackbuilds.org> <0f9fb4fe-a783-2ace-89f0-2f7c2ef7b980@ptd.net> Message-ID: 2017-02-12 2:00 GMT+01:00 John : > On Sat, Feb 11, 2017 at 03:00:23PM -0500, John wrote: >> When using a slackbuild what is the proper base system >> Is it a full install of 14.2? >> Or is it a full install with all updates posted by Pat? both should work fine the same. Matteo From jvogel4 at stny.rr.com Sun Feb 12 17:53:32 2017 From: jvogel4 at stny.rr.com (John Vogel) Date: Sun, 12 Feb 2017 12:53:32 -0500 Subject: [Slackbuilds-users] slackbuilds up for grabs Message-ID: <20170212125332.0d3b8589@stygian.lan> Dear list, I am relinquishing my Slackbuilds. I no longer use Slackware and don't have time to keep my build scripts updated anymore. According to my notes, I had been maintaining the following Slackbuilds: avidemux bar bmake bspwm dash dvdbackup mpv sutils sxhkd xtitle I will eventually be cleaning out my github repo in the near future, so if anyone has a use for my Slackware stuff there, the relevent links are: https://github.com/jvvv/slackbuilds https://github.com/jvvv/slacktags I apologize for any inconvience this may cause. Regards, John From fernando.lopezjr at gmail.com Sun Feb 12 17:55:04 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 12 Feb 2017 10:55:04 -0700 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: <20170212125332.0d3b8589@stygian.lan> References: <20170212125332.0d3b8589@stygian.lan> Message-ID: ill take avidemux On Feb 12, 2017 10:54 AM, "John Vogel" wrote: > Dear list, > > I am relinquishing my Slackbuilds. I no longer use Slackware and don't > have time to keep my build scripts updated anymore. According to my > notes, I had been maintaining the following Slackbuilds: > > avidemux > bar > bmake > bspwm > dash > dvdbackup > mpv > sutils > sxhkd > xtitle > > I will eventually be cleaning out my github repo in the near future, > so if anyone has a use for my Slackware stuff there, the relevent > links are: > https://github.com/jvvv/slackbuilds > https://github.com/jvvv/slacktags > > I apologize for any inconvience this may cause. > > Regards, > John > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.guldstrand at gmail.com Sun Feb 12 18:07:00 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Sun, 12 Feb 2017 19:07:00 +0100 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: References: <20170212125332.0d3b8589@stygian.lan> Message-ID: I'll take mpv, thanks for your efforts On 12 February 2017 at 18:55, Fernando Lopez wrote: > ill take avidemux > > On Feb 12, 2017 10:54 AM, "John Vogel" wrote: >> >> Dear list, >> >> I am relinquishing my Slackbuilds. I no longer use Slackware and don't >> have time to keep my build scripts updated anymore. According to my >> notes, I had been maintaining the following Slackbuilds: >> >> avidemux >> bar >> bmake >> bspwm >> dash >> dvdbackup >> mpv >> sutils >> sxhkd >> xtitle >> >> I will eventually be cleaning out my github repo in the near future, >> so if anyone has a use for my Slackware stuff there, the relevent >> links are: >> https://github.com/jvvv/slackbuilds >> https://github.com/jvvv/slacktags >> >> I apologize for any inconvience this may cause. >> >> Regards, >> John >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From hostmaster at slackonly.com Sun Feb 12 18:40:10 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 12 Feb 2017 10:40:10 -0800 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: <20170212125332.0d3b8589@stygian.lan> References: <20170212125332.0d3b8589@stygian.lan> Message-ID: <745d504e-415b-34f5-07df-55a6be19a770@slackonly.com> I'll take bspwm and sxhkd On 02/12/2017 09:53 AM, John Vogel wrote: > Dear list, > > I am relinquishing my Slackbuilds. I no longer use Slackware and don't > have time to keep my build scripts updated anymore. According to my > notes, I had been maintaining the following Slackbuilds: > > avidemux > bar > bmake > bspwm > dash > dvdbackup > mpv > sutils > sxhkd > xtitle > > I will eventually be cleaning out my github repo in the near future, > so if anyone has a use for my Slackware stuff there, the relevent > links are: > https://github.com/jvvv/slackbuilds > https://github.com/jvvv/slacktags > > I apologize for any inconvience this may cause. > > Regards, > John > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From hostmaster at slackonly.com Sun Feb 12 19:00:53 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 12 Feb 2017 11:00:53 -0800 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: <745d504e-415b-34f5-07df-55a6be19a770@slackonly.com> References: <20170212125332.0d3b8589@stygian.lan> <745d504e-415b-34f5-07df-55a6be19a770@slackonly.com> Message-ID: I'll take also bar, sutils, and xtitle On 02/12/2017 10:40 AM, Panagiotis Nikolaou wrote: > I'll take bspwm and sxhkd > > On 02/12/2017 09:53 AM, John Vogel wrote: >> Dear list, >> >> I am relinquishing my Slackbuilds. I no longer use Slackware and don't >> have time to keep my build scripts updated anymore. According to my >> notes, I had been maintaining the following Slackbuilds: >> >> avidemux >> bar >> bmake >> bspwm >> dash >> dvdbackup >> mpv >> sutils >> sxhkd >> xtitle >> >> I will eventually be cleaning out my github repo in the near future, >> so if anyone has a use for my Slackware stuff there, the relevent >> links are: >> https://github.com/jvvv/slackbuilds >> https://github.com/jvvv/slacktags >> >> I apologize for any inconvience this may cause. >> >> Regards, >> John >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From rshepard at appl-ecosys.com Sun Feb 12 19:58:52 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 12 Feb 2017 11:58:52 -0800 (PST) Subject: [Slackbuilds-users] Which LibreOffice version to use? Message-ID: I see there are two versions of LO on SBo: LibreOffice-5.3.0.3 and libreoffice-5.3.0. What is the basis for selecting one? Rich From dave at dawoodfall.net Sun Feb 12 20:14:31 2017 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 12 Feb 2017 20:14:31 +0000 Subject: [Slackbuilds-users] Which LibreOffice version to use? In-Reply-To: References: Message-ID: <20170212201431.GU5539@Blackswan> > I see there are two versions of LO on SBo: LibreOffice-5.3.0.3 and >libreoffice-5.3.0. > > What is the basis for selecting one? > >Rich LibreOffice-5.3.0.3 is built from source, while libreoffice-5.3.0 is a binary repackage. The relevant pages have info on usage. It mostly depends on whether you have time to build from source or not. -D From rshepard at appl-ecosys.com Sun Feb 12 21:07:15 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 12 Feb 2017 13:07:15 -0800 (PST) Subject: [Slackbuilds-users] Which LibreOffice version to use? In-Reply-To: <20170212201431.GU5539@Blackswan> References: <20170212201431.GU5539@Blackswan> Message-ID: On Sun, 12 Feb 2017, David Woodfall wrote: > LibreOffice-5.3.0.3 is built from source, while libreoffice-5.3.0 is a > binary repackage. > > The relevant pages have info on usage. It mostly depends on whether > you have time to build from source or not. David, Thanks for clarifying. Since the latter has fewer dependencies and I don't use LO that often, I'll install the lowercase version. Much appreciated, Rich From chytraeu at sdf.org Sun Feb 12 21:27:24 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Sun, 12 Feb 2017 15:27:24 -0600 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: <20170212125332.0d3b8589@stygian.lan> References: <20170212125332.0d3b8589@stygian.lan> Message-ID: <8f75168f-f342-e5f3-5535-6756b9d0ae31@sdf.org> I'll take dash On 02/12/2017 11:53 AM, John Vogel wrote: > Dear list, > > I am relinquishing my Slackbuilds. I no longer use Slackware and don't > have time to keep my build scripts updated anymore. According to my > notes, I had been maintaining the following Slackbuilds: > > avidemux > bar > bmake > bspwm > dash > dvdbackup > mpv > sutils > sxhkd > xtitle > > I will eventually be cleaning out my github repo in the near future, > so if anyone has a use for my Slackware stuff there, the relevent > links are: > https://github.com/jvvv/slackbuilds > https://github.com/jvvv/slacktags > > I apologize for any inconvience this may cause. > > Regards, > John > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Mon Feb 13 02:41:56 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 12 Feb 2017 21:41:56 -0500 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: <20170212125332.0d3b8589@stygian.lan> References: <20170212125332.0d3b8589@stygian.lan> Message-ID: On 2/12/17, John Vogel wrote: > bmake I'll take bmake. From pessoal at profcavalheiro.com Mon Feb 13 07:00:54 2017 From: pessoal at profcavalheiro.com (Luis Cavalheiro) Date: Mon, 13 Feb 2017 05:00:54 -0200 Subject: [Slackbuilds-users] Error when compiling Audacity Message-ID: Guys, when I run Audacity SlackBuild I got a lot of error like this one: DirManager.cpp:1570:20: error: cannot convert ?const wxString? to ?const wxChar* {aka const wchar_t*}? in initialization And then build stops because error. Does someone has a clue on it? -- Cordialmente, Lu?s Fernando Carvalho Cavalheiro -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Mon Feb 13 07:04:00 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 13 Feb 2017 08:04:00 +0100 Subject: [Slackbuilds-users] Error when compiling Audacity In-Reply-To: References: Message-ID: 2017-02-13 8:00 GMT+01:00 Luis Cavalheiro : > Guys, when I run Audacity SlackBuild I got a lot of error like this one: > > DirManager.cpp:1570:20: error: cannot convert ?const wxString? to ?const > wxChar* {aka const wchar_t*}? in initialization > > And then build stops because error. Does someone has a clue on it? Hi Luis, can you please post the full build log on someplace like pastebin.com? Matteo From fernando.lopezjr at gmail.com Mon Feb 13 07:05:49 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 13 Feb 2017 00:05:49 -0700 Subject: [Slackbuilds-users] Error when compiling Audacity In-Reply-To: References: Message-ID: do you have wxGTK3 installed? On Mon, Feb 13, 2017 at 12:00 AM, Luis Cavalheiro < pessoal at profcavalheiro.com> wrote: > Guys, when I run Audacity SlackBuild I got a lot of error like this one: > > DirManager.cpp:1570:20: error: cannot convert ?const wxString? to ?const > wxChar* {aka const wchar_t*}? in initialization > > And then build stops because error. Does someone has a clue on it? > > -- > Cordialmente, > Lu?s Fernando Carvalho Cavalheiro > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Mon Feb 13 07:36:14 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Mon, 13 Feb 2017 00:36:14 -0700 Subject: [Slackbuilds-users] Error when compiling Audacity In-Reply-To: References: Message-ID: I just re-compile it... and it compiled just fine... On Mon, Feb 13, 2017 at 12:05 AM, Fernando Lopez wrote: > do you have wxGTK3 installed? > > On Mon, Feb 13, 2017 at 12:00 AM, Luis Cavalheiro < > pessoal at profcavalheiro.com> wrote: > >> Guys, when I run Audacity SlackBuild I got a lot of error like this one: >> >> DirManager.cpp:1570:20: error: cannot convert ?const wxString? to ?const >> wxChar* {aka const wchar_t*}? in initialization >> >> And then build stops because error. Does someone has a clue on it? >> >> -- >> Cordialmente, >> Lu?s Fernando Carvalho Cavalheiro >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> >> > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lspencer31 at cfl.rr.com Mon Feb 13 16:03:01 2017 From: lspencer31 at cfl.rr.com (Lenard Spencer) Date: Mon, 13 Feb 2017 11:03:01 -0500 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: <20170212125332.0d3b8589@stygian.lan> References: <20170212125332.0d3b8589@stygian.lan> Message-ID: <36d6458e-f53b-f6ca-b6af-b9fd1b0644a2@cfl.rr.com> I'll be more than happy to take over dvdbackup. On 02/12/2017 12:53 PM, John Vogel wrote: > Dear list, > > I am relinquishing my Slackbuilds. I no longer use Slackware and don't > have time to keep my build scripts updated anymore. According to my > notes, I had been maintaining the following Slackbuilds: > > avidemux > bar > bmake > bspwm > dash > dvdbackup > mpv > sutils > sxhkd > xtitle > > I will eventually be cleaning out my github repo in the near future, > so if anyone has a use for my Slackware stuff there, the relevent > links are: > https://github.com/jvvv/slackbuilds > https://github.com/jvvv/slacktags > > I apologize for any inconvience this may cause. > > Regards, > John > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From jvogel4 at stny.rr.com Mon Feb 13 21:30:18 2017 From: jvogel4 at stny.rr.com (John Vogel) Date: Mon, 13 Feb 2017 16:30:18 -0500 Subject: [Slackbuilds-users] slackbuilds up for grabs In-Reply-To: References: <20170212125332.0d3b8589@stygian.lan> Message-ID: <20170213163018.7b085055@stygian.lan> On Sun, 12 Feb 2017 19:07:00 +0100 Andreas Guldstrand wrote: > I'll take mpv, thanks for your efforts > You're very welcome. Please accept my thanks. And thank you to everyone who has stepped up to pickup my slackbuilds. I'd like to say, in parting, that this is a great community and have enjoyed my interactions with people here. My leaving is somewhat sad, but I am more content running Crux for my desktop and Alpine for my server; they suit my needs in each. I wish you all well. From rshepard at appl-ecosys.com Tue Feb 14 16:13:17 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 08:13:17 -0800 (PST) Subject: [Slackbuilds-users] acroread for 64-bit machines? Message-ID: My use of Adobe's acrobat reader is infrequent, but good for presentations showing beamer-class slides. There was no problem that I recall using it with 14.1, but I'm having issues trying to get a version that works with 14.2. I have a presentation tomorrow and neither xpdf nor mupdf will display the LaTeX/beamer slides full screen. The windows are full screen, but not the PDF file. Do I need the 32-bit compatibility libraries to run acroread? What are other folks using? Rich From fellype at gmail.com Tue Feb 14 16:27:42 2017 From: fellype at gmail.com (Fellype do Nascimento) Date: Tue, 14 Feb 2017 14:27:42 -0200 Subject: [Slackbuilds-users] acroread for 64-bit machines? In-Reply-To: References: Message-ID: Not a solution for your problems with acroread... But have you tried to use Okular? It works well, in full screen mode, with pdf files created using LaTeX/beamer. Fellype On 02/14/2017 02:13 PM, Rich Shepard wrote: > My use of Adobe's acrobat reader is infrequent, but good for > presentations > showing beamer-class slides. There was no problem that I recall using it > with 14.1, but I'm having issues trying to get a version that works with > 14.2. > > I have a presentation tomorrow and neither xpdf nor mupdf will > display the > LaTeX/beamer slides full screen. The windows are full screen, but not the > PDF file. > > Do I need the 32-bit compatibility libraries to run acroread? What are > other folks using? > > Rich From dn2010 at gmail.com Tue Feb 14 16:34:13 2017 From: dn2010 at gmail.com (Daniil Bratashov) Date: Tue, 14 Feb 2017 20:34:13 +0400 Subject: [Slackbuilds-users] acroread for 64-bit machines? In-Reply-To: References: Message-ID: evince seems to work fine with beamer presentations. WBR, Daniil Bratashov. On Tue, Feb 14, 2017 at 8:27 PM, Fellype do Nascimento wrote: > Not a solution for your problems with acroread... > But have you tried to use Okular? It works well, in full screen mode, with > pdf files created using LaTeX/beamer. > > Fellype > > > On 02/14/2017 02:13 PM, Rich Shepard wrote: > >> My use of Adobe's acrobat reader is infrequent, but good for >> presentations >> showing beamer-class slides. There was no problem that I recall using it >> with 14.1, but I'm having issues trying to get a version that works with >> 14.2. >> >> I have a presentation tomorrow and neither xpdf nor mupdf will display >> the >> LaTeX/beamer slides full screen. The windows are full screen, but not the >> PDF file. >> >> Do I need the 32-bit compatibility libraries to run acroread? What are >> other folks using? >> >> Rich >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Tue Feb 14 16:36:42 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 08:36:42 -0800 (PST) Subject: [Slackbuilds-users] acroread for 64-bit machines? In-Reply-To: References: Message-ID: On Tue, 14 Feb 2017, Fellype do Nascimento wrote: > Not a solution for your problems with acroread... But have you tried to > use Okular? It works well, in full screen mode, with pdf files created > using LaTeX/beamer. Fellype, I just tried it. Like xpdf and mupdf at full-screen mode the entire window is displayed. With acroread, pressing ctrl-l put the contents in full-screen display with no window frame. A second ctrl-l returned it to the default size. This allows only the slides to be displayed. If you've seen Microsoft using folks use PowerPoint you have seen the difference between displays of the PowerPoint window with sidebars, frame, etc. and only the file they are are using. I need the equivalent of this which acroread provides. Thanks, Rich From rshepard at appl-ecosys.com Tue Feb 14 16:47:16 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 08:47:16 -0800 (PST) Subject: [Slackbuilds-users] acroread for 64-bit machines? In-Reply-To: References: Message-ID: On Tue, 14 Feb 2017, Daniil Bratashov wrote: > evince seems to work fine with beamer presentations. Daniil, This, too, displays the window frame and sidebar in full-screen mode. Thanks, Rich From info at microlinux.fr Tue Feb 14 16:52:38 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 14 Feb 2017 17:52:38 +0100 Subject: [Slackbuilds-users] flashplayer-plugin: broken URL Message-ID: Hi, As usual, the Adobe folks play hide & seek with their URLs. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From rshepard at appl-ecosys.com Tue Feb 14 16:55:35 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 08:55:35 -0800 (PST) Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: References: Message-ID: On Tue, 14 Feb 2017, Rich Shepard wrote: > Do I need the 32-bit compatibility libraries to run acroread? What are > other folks using? The short answer is, "no." There is an xpdf option, -fullscreen, that does exactly what acroread's ctrl-l does: presents the file contents across the full screen with no frame or other distractions. Super kewel! Today's linux lesson. Rich From ryanpcmcquen at member.fsf.org Tue Feb 14 16:56:15 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Tue, 14 Feb 2017 08:56:15 -0800 Subject: [Slackbuilds-users] acroread for 64-bit machines? In-Reply-To: References: Message-ID: On Tuesday, February 14, 2017, Rich Shepard wrote: > On Tue, 14 Feb 2017, Daniil Bratashov wrote: > > evince seems to work fine with beamer presentations. >> > > Daniil, > > This, too, displays the window frame and sidebar in full-screen mode. > How about Firefox? -- --- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From dn2010 at gmail.com Tue Feb 14 17:00:26 2017 From: dn2010 at gmail.com (Daniil Bratashov) Date: Tue, 14 Feb 2017 21:00:26 +0400 Subject: [Slackbuilds-users] acroread for 64-bit machines? In-Reply-To: References: Message-ID: No, just start it as presentation (in menu from mode button, near the size scale). WBR, Daniil Bratashov. On Tue, Feb 14, 2017 at 8:47 PM, Rich Shepard wrote: > On Tue, 14 Feb 2017, Daniil Bratashov wrote: > > evince seems to work fine with beamer presentations. >> > > Daniil, > > This, too, displays the window frame and sidebar in full-screen mode. > > Thanks, > > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryanpcmcquen at member.fsf.org Tue Feb 14 17:00:55 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Tue, 14 Feb 2017 09:00:55 -0800 Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: References: Message-ID: On Tuesday, February 14, 2017, Rich Shepard wrote: > On Tue, 14 Feb 2017, Rich Shepard wrote: > > Do I need the 32-bit compatibility libraries to run acroread? What are >> other folks using? >> > > The short answer is, "no." There is an xpdf option, -fullscreen, that > does > exactly what acroread's ctrl-l does: presents the file contents across the > full screen with no frame or other distractions. > > Super kewel! Today's linux lesson. > Firefox also does this. ;^) -- --- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Tue Feb 14 17:09:00 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 09:09:00 -0800 (PST) Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: References: Message-ID: On Tue, 14 Feb 2017, Ryan P.C. McQuen wrote: > Firefox also does this. ;^) Ryan, But that's a browser and I prefer to use them only for web pages. Thanks, Rich From willysr at slackbuilds.org Tue Feb 14 17:25:28 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 15 Feb 2017 00:25:28 +0700 Subject: [Slackbuilds-users] flashplayer-plugin: broken URL In-Reply-To: References: Message-ID: <0c6fa776-7c8a-850e-5529-137b32e64f5c@slackbuilds.org> > As usual, the Adobe folks play hide & seek with their URLs. Fixed in my branch Thanks for reporting -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ryanpcmcquen at member.fsf.org Tue Feb 14 17:30:39 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Tue, 14 Feb 2017 09:30:39 -0800 Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: References: Message-ID: On Feb 14, 2017 9:10 AM, "Rich Shepard" wrote: On Tue, 14 Feb 2017, Ryan P.C. McQuen wrote: Firefox also does this. ;^) > Ryan, But that's a browser and I prefer to use them only for web pages. If it works, who cares what its normal usage is? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ewfalor at gmail.com Tue Feb 14 17:37:11 2017 From: ewfalor at gmail.com (Erik Falor) Date: Tue, 14 Feb 2017 10:37:11 -0700 Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: References: Message-ID: <20170214173711.zs4nnajxs532dp3y@viking2.falor> On Tue, Feb 14, 2017 at 09:30:39AM -0800, Ryan P.C. McQuen wrote: > Ryan, > ? But that's a browser and I prefer to use them only for web pages. > > If it works, who cares what its normal usage is? Because a fullscreen PDF viewer doesn't use 100MB of RAM and won't phone home? Wait, are we still talking about the Adobe product or the open-source PDF viewer? -- Erik Falor Registered Linux User #445632 http://unnovative.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: not available URL: From ryanpcmcquen at member.fsf.org Tue Feb 14 17:50:47 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Tue, 14 Feb 2017 09:50:47 -0800 Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: <20170214173711.zs4nnajxs532dp3y@viking2.falor> References: <20170214173711.zs4nnajxs532dp3y@viking2.falor> Message-ID: On Tuesday, February 14, 2017, Erik Falor > wrote: > On Tue, Feb 14, 2017 at 09:30:39AM -0800, Ryan P.C. McQuen wrote: > > Ryan, > > ? But that's a browser and I prefer to use them only for web pages. > > > > If it works, who cares what its normal usage is? > > Because a fullscreen PDF viewer doesn't use 100MB of RAM and won't > phone home? > If resources or privacy were a concern, the OP wouldn't have been coming from a proprietary Adobe product. -- --- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Tue Feb 14 18:05:04 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 10:05:04 -0800 (PST) Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: References: <20170214173711.zs4nnajxs532dp3y@viking2.falor> Message-ID: On Tue, 14 Feb 2017, Ryan P.C. McQuen wrote: > If resources or privacy were a concern, the OP wouldn't have been coming > from a proprietary Adobe product. My default PDF viewer has always been xpdf. As the Slackware version does not support the most recent Adobe PDF versions I use mupdf for those. My only use of acroread has been slide presentations. Now that I've learned that xpdf provides a fullscreen mode I've removed the acroread packages from all my hosts. And privacy and resource use are concerns; acroread binaries are comparatively small and it does not track me over the Web. Rich From ryanpcmcquen at member.fsf.org Tue Feb 14 18:13:48 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Tue, 14 Feb 2017 10:13:48 -0800 Subject: [Slackbuilds-users] acroread for 64-bit machines? [RESOLVED] In-Reply-To: References: <20170214173711.zs4nnajxs532dp3y@viking2.falor> Message-ID: On Tuesday, February 14, 2017, Rich Shepard wrote: > On Tue, 14 Feb 2017, Ryan P.C. McQuen wrote: > > If resources or privacy were a concern, the OP wouldn't have been coming >> from a proprietary Adobe product. >> > > My default PDF viewer has always been xpdf. As the Slackware version does > not support the most recent Adobe PDF versions I use mupdf for those. My > only use of acroread has been slide presentations. > > Now that I've learned that xpdf provides a fullscreen mode I've removed > the acroread packages from all my hosts. > > And privacy and resource use are concerns; acroread binaries are > comparatively small and it does not track me over the Web. > Believe whatever you need to. -- --- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From ronayne.thomas at gmail.com Tue Feb 14 19:46:14 2017 From: ronayne.thomas at gmail.com (Thomas Ronayne) Date: Tue, 14 Feb 2017 14:46:14 -0500 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 130, Issue 27 In-Reply-To: References: Message-ID: The current Firefox will atuomagically open a PDF in an editor/viewer (I read Linux Journal like this). It will also, if you have LibreOffice (maybe OpenOffice too, don't know), open from the Firefox viewer in LibreOffice so you can edit, view, save or print. You really don't need Acrobat Reader to do so; that is, you can save, print, view in the viewer or open in LibreOffice for editing, viewing, saving, printing. It's dirt easy and not too much fiddling around -- haven't found anything that doesn't work in just the viewer. On 02/14/2017 01:05 PM, slackbuilds-users-request at slackbuilds.org wrote: > Send SlackBuilds-users mailing list submissions to > slackbuilds-users at slackbuilds.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > or, via email, send a message with subject or body 'help' to > slackbuilds-users-request at slackbuilds.org > > You can reach the person managing the list at > slackbuilds-users-owner at slackbuilds.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SlackBuilds-users digest..." > > > Today's Topics: > > 1. Re: acroread for 64-bit machines? (Daniil Bratashov) > 2. Re: acroread for 64-bit machines? [RESOLVED] (Ryan P.C. McQuen) > 3. Re: acroread for 64-bit machines? [RESOLVED] (Rich Shepard) > 4. Re: flashplayer-plugin: broken URL (Willy Sudiarto Raharjo) > 5. Re: acroread for 64-bit machines? [RESOLVED] (Ryan P.C. McQuen) > 6. Re: acroread for 64-bit machines? [RESOLVED] (Erik Falor) > 7. Re: acroread for 64-bit machines? [RESOLVED] (Ryan P.C. McQuen) > 8. Re: acroread for 64-bit machines? [RESOLVED] (Rich Shepard) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 14 Feb 2017 21:00:26 +0400 > From: Daniil Bratashov > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] acroread for 64-bit machines? > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > No, just start it as presentation (in menu from mode button, near the size > scale). > > WBR, Daniil Bratashov. > > On Tue, Feb 14, 2017 at 8:47 PM, Rich Shepard > wrote: > >> On Tue, 14 Feb 2017, Daniil Bratashov wrote: >> >> evince seems to work fine with beamer presentations. >> Daniil, >> >> This, too, displays the window frame and sidebar in full-screen mode. >> >> Thanks, >> >> >> Rich >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 2 > Date: Tue, 14 Feb 2017 09:00:55 -0800 > From: "Ryan P.C. McQuen" > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] acroread for 64-bit machines? > [RESOLVED] > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > On Tuesday, February 14, 2017, Rich Shepard > wrote: > >> On Tue, 14 Feb 2017, Rich Shepard wrote: >> >> Do I need the 32-bit compatibility libraries to run acroread? What are >>> other folks using? >>> >> The short answer is, "no." There is an xpdf option, -fullscreen, that >> does >> exactly what acroread's ctrl-l does: presents the file contents across the >> full screen with no frame or other distractions. >> >> Super kewel! Today's linux lesson. >> > Firefox also does this. ;^) > > From artourter at gmail.com Tue Feb 14 21:45:23 2017 From: artourter at gmail.com (Greg' Ar Tourter) Date: Tue, 14 Feb 2017 21:45:23 +0000 Subject: [Slackbuilds-users] acroread for 64-bit machines? In-Reply-To: References: Message-ID: As the maintainer of the adobe reader package, the answer to the question of whether you need the 32bit compatibility libs to run adobe reader on 64bit slackware is yes, and I may add "unfortunately". Now to the rest of the conversation, I always come back to adobe reader for viewing documents but it is true that the linux version is now very old and lacks the features its mac and windows version now have. Unfortunately, I very much doubt we will ever see an updated version from Adobe (although they have released a synchronised version of flash after saying they would never do so there is still hope, albeit a very very small glimmer of it). For presentations, I have started using pdfpc (also available on SBo, but an old version. I have emailed the maintainer of the package a patch to a newer one a while back and he assured me he would have a look... I probably should probe again). pdfpc offers notes, presenter console, highlighter, pointer.... Hope this helps Cheers Greg On 14 February 2017 at 16:13, Rich Shepard wrote: > My use of Adobe's acrobat reader is infrequent, but good for > presentations > showing beamer-class slides. There was no problem that I recall using it > with 14.1, but I'm having issues trying to get a version that works with > 14.2. > > I have a presentation tomorrow and neither xpdf nor mupdf will display > the > LaTeX/beamer slides full screen. The windows are full screen, but not the > PDF file. > > Do I need the 32-bit compatibility libraries to run acroread? What are > other folks using? > > Rich > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Feb 14 21:59:32 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 14 Feb 2017 16:59:32 -0500 Subject: [Slackbuilds-users] Fwd: reiser4progs and libaal getting long in the tooth In-Reply-To: <73695006-f985-e05b-4df3-44bf8f668995@slackbuilds.org> References: <73695006-f985-e05b-4df3-44bf8f668995@slackbuilds.org> Message-ID: On 2/11/17, Willy Sudiarto Raharjo wrote: > Sure, push it to a different branch with a -review at the back and i > will merge it to my branch after reviewing it. Thanks. Pushed to user/urchlay/reiser4progs-review From kingbeowulf at gmail.com Tue Feb 14 22:30:26 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 14 Feb 2017 14:30:26 -0800 Subject: [Slackbuilds-users] [OT] xpdf and okular (was: acroread for 64-bit machines?) In-Reply-To: References: Message-ID: On 02/14/2017 08:13 AM, Rich Shepard wrote: > My use of Adobe's acrobat reader is infrequent, but good for > presentations > showing beamer-class slides. There was no problem that I recall using it > with 14.1, but I'm having issues trying to get a version that works with > 14.2. > > I have a presentation tomorrow and neither xpdf nor mupdf will display > the > LaTeX/beamer slides full screen. The windows are full screen, but not the > PDF file. > You already marked as "resolved" but here is another tip. Besides the CLI -fullscreen options, in xpdf if you - on the open, displayed file, the pop-up menu has a "fullscreen" option. Also, I prefer okular these days. It integrates much better with modern WMs, has better font support, form entry, search/find. Summary: Various document formats, including: PDFs, EPUB ebooks, CBR and CBZ comic books, DjVu, images Annotate and mark up PDF files with comments, highlights, etc. Extract text from a PDF to a text file Set bookmarks for later viewing Trim white page borders etc Okular also does quite well with odd pdfs that I sometimes get from my employer. The only downside is some KDE baggage. Since a full stock Slackware install is only about 8GB or so, I'm not too worried about using too much space. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Wed Feb 15 00:54:37 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 16:54:37 -0800 (PST) Subject: [Slackbuilds-users] Need 14.1/32-bit tarball for LibreOffice-5.1.4 Message-ID: I goofed by upgrading my 14.1/32-bit workstation's libreoffice from 5.1.4 to 5.3.0. Apparently enough has changed between 14.1 and 14.2 that the new version no longer finds all my installed typefaces in the /usr/share/fonts/ subdirectories. Unfortunately, the only older version I have is 5.0.1, not the 5.1.4 that was installed. I can no longer download the 32-bit 5.1.4 from the LibreOffice web site link on SBo. If you have a copy of the 32-bit version of 5.1.4 please contact me and we'll make arrangements for transferring a copy to me. TIA, Rich From willysr at slackbuilds.org Wed Feb 15 01:20:11 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 15 Feb 2017 08:20:11 +0700 Subject: [Slackbuilds-users] Scripts For Grab Message-ID: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> Hi, If anyone is interested to take over some of my scripts below, feel free to reply to the list academic/sage academic/galculator development/google-webdesigner games/wesnoth gis/routino libraries/ocaml-bisect misc/nixnote multimedia/TeamSpeak3 multimedia/pngnq-s9 network/megasync system/autocutsel Most of them are up to date with the latest version (except for sage and megasync) NOTE: sage is fixed at 7.2 until next Slackware is released See commit message in https://slackbuilds.org/cgit/slackbuilds/commit/?id=2a406c5075d9310a32d63adffa6b784e4c348019 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Wed Feb 15 02:16:48 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 14 Feb 2017 18:16:48 -0800 Subject: [Slackbuilds-users] Need 14.1/32-bit tarball for LibreOffice-5.1.4 In-Reply-To: References: Message-ID: On 02/14/2017 04:54 PM, Rich Shepard wrote: --- > > Unfortunately, the only older version I have is 5.0.1, not the 5.1.4 that > was installed. I can no longer download the 32-bit 5.1.4 from the > LibreOffice web site link on SBo. > --- Try the Document Foundation archives: https://downloadarchive.documentfoundation.org/libreoffice/old/ -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Wed Feb 15 03:10:21 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Tue, 14 Feb 2017 19:10:21 -0800 Subject: [Slackbuilds-users] Scripts For Grab In-Reply-To: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> References: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> Message-ID: On 02/14/2017 05:20 PM, Willy Sudiarto Raharjo wrote: > academic/galculator I'll take galculator From rshepard at appl-ecosys.com Wed Feb 15 03:11:41 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 14 Feb 2017 19:11:41 -0800 (PST) Subject: [Slackbuilds-users] Need 14.1/32-bit tarball for LibreOffice-5.1.4 In-Reply-To: References: Message-ID: On Tue, 14 Feb 2017, King Beowulf wrote: > Try the Document Foundation archives: > https://downloadarchive.documentfoundation.org/libreoffice/old/ Ed, Will do. Thanks, Rich From yalhcru at gmail.com Wed Feb 15 03:33:57 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 14 Feb 2017 22:33:57 -0500 Subject: [Slackbuilds-users] Scripts For Grab In-Reply-To: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> References: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> Message-ID: On 2/14/17, Willy Sudiarto Raharjo wrote: > system/autocutsel I'll take autocutsel. From info at microlinux.fr Wed Feb 15 07:40:24 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 15 Feb 2017 08:40:24 +0100 Subject: [Slackbuilds-users] vsxu: strange symlinks Message-ID: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> Hi, I have installed vsxu, mostly as a dependency for VLC. I've noticed something strange. There are some strange symlinks in the users' home directories. User kikinovak has a vsxu symlink to /home/kikinovak/.local/share/vsxu/, and even root has a (broken) /root/vsxu symlink to a nonexistent /root/vsxu/local/share/vsxu. Anyone know what's going on here? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From kingbeowulf at gmail.com Wed Feb 15 07:43:12 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 14 Feb 2017 23:43:12 -0800 Subject: [Slackbuilds-users] Scripts For Grab In-Reply-To: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> References: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> Message-ID: <1b92743d-7c39-a8f4-303d-32f5f2bfb233@gmail.com> On 02/14/2017 05:20 PM, Willy Sudiarto Raharjo wrote: > academic/sage > games/wesnoth > multimedia/TeamSpeak3 I'll take these 3 if not already spoken for, 'cause I'm a glutton for extra work! -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Wed Feb 15 08:06:58 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 15 Feb 2017 18:06:58 +1000 Subject: [Slackbuilds-users] vsxu: strange symlinks In-Reply-To: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> References: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> Message-ID: <4821e85a-bafd-f84d-d6be-172c2383b4fa@iinet.net.au> On 15/02/17 17:40, Nicolas Kovacs wrote: > Hi, > > I have installed vsxu, mostly as a dependency for VLC. > > I've noticed something strange. There are some strange symlinks in the > users' home directories. User kikinovak has a vsxu symlink to > /home/kikinovak/.local/share/vsxu/, and even root has a (broken) > /root/vsxu symlink to a nonexistent /root/vsxu/local/share/vsxu. > > Anyone know what's going on here? > See items 5 & 6 in the first (General Features) box: http://www.vsxu.com/documentation/changelog Its not much of an explanation but something ... chris From kingbeowulf at gmail.com Wed Feb 15 08:09:25 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 15 Feb 2017 00:09:25 -0800 Subject: [Slackbuilds-users] vsxu: strange symlinks In-Reply-To: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> References: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> Message-ID: On 02/14/2017 11:40 PM, Nicolas Kovacs wrote: > Hi, > > I have installed vsxu, mostly as a dependency for VLC. > > I've noticed something strange. There are some strange symlinks in the > users' home directories. User kikinovak has a vsxu symlink to > /home/kikinovak/.local/share/vsxu/, and even root has a (broken) > /root/vsxu symlink to a nonexistent /root/vsxu/local/share/vsxu. > --- Sounds like a change in where they stick local configuration. Of course, this isn't mention in the github changelog, the dummies. http://www.vsxu.com/documentation/changelog Change Log 0.3.0.4 (April 2012) ------------------- + For GNU/Linux version, we now use ~/.local/share/vsxu INSTEAD of ~/.vsxu Since you might want to look this over (and your backup scripts!) we think you should do the migration yourself, thus we didn't add an automatic script to copy the old files into this new location. The reason for this move is to better comply with standards. + For GNU/Linux version, we now create a symbolic link in your home directory - "vsxu" which points to ~/.local/share/vsxu for your convenience -------------- Your google-fu is weak, young one. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From dickson.tim at googlemail.com Wed Feb 15 11:30:09 2017 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 15 Feb 2017 11:30:09 +0000 Subject: [Slackbuilds-users] gtkhtml In-Reply-To: References: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> Message-ID: Hi folks, I am the maintainer for this package, but the only package that required it (xiphos) moved to webkit a while ago. If no-one else uses it, perhaps it could get dumped. (it is a little out of date, but I don't have a program to test it works any more.) Tim From willysr at slackbuilds.org Wed Feb 15 12:13:26 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 15 Feb 2017 19:13:26 +0700 Subject: [Slackbuilds-users] gtkhtml In-Reply-To: References: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> Message-ID: <9476348b-8a5b-fc1b-8ed4-1eeb6f5e2b30@slackbuilds.org> > Hi folks, I am the maintainer for this package, but the only package > that required it (xiphos) moved to webkit a while ago. If no-one else > uses it, perhaps it could get dumped. (it is a little out of date, but I > don't have a program to test it works any more.) > Tim Unless it's no longer build against default packages in Slackware/SBo, i think it's safe to keep them in the repository. many scripts in the repository exists without being used by others and perhaps there's a chance that some project might use them someday. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slackph at posteo.de Wed Feb 15 13:24:10 2017 From: slackph at posteo.de (Philip Lacroix) Date: Wed, 15 Feb 2017 14:24:10 +0100 Subject: [Slackbuilds-users] Scripts For Grab In-Reply-To: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> References: <2c6fcf72-a7f9-9b22-117f-56016a1772ec@slackbuilds.org> Message-ID: Am 15.02.2017 02:20 schrieb Willy Sudiarto Raharjo: > gis/routino I'll take routino, if no one else wants it. Thanks Philip From info at microlinux.fr Wed Feb 15 14:02:57 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 15 Feb 2017 15:02:57 +0100 Subject: [Slackbuilds-users] vsxu: strange symlinks In-Reply-To: <4821e85a-bafd-f84d-d6be-172c2383b4fa@iinet.net.au> References: <77185d8e-c5ec-54c0-68c1-11d3a4e52f2e@microlinux.fr> <4821e85a-bafd-f84d-d6be-172c2383b4fa@iinet.net.au> Message-ID: <4175b6bb-7f16-580e-1e0c-e6cdf5651a91@microlinux.fr> Le 15/02/2017 ? 09:06, Christoph Willing a ?crit : > See items 5 & 6 in the first (General Features) box: > http://www.vsxu.com/documentation/changelog > > Its not much of an explanation but something ... OK, thanks! -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Wed Feb 15 20:43:29 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 15 Feb 2017 21:43:29 +0100 Subject: [Slackbuilds-users] Suggestion to patch skippy-xd Message-ID: <50f1fa9a-3588-c847-17f1-6fd0b26670bb@microlinux.fr> Hi, This morning I built skippy-xd and had a weird problem with it. The whole process is described here, along with the solution: http://www.linuxquestions.org/questions/slackware-14/skippy-xd-for-more-than-one-user-4175599797/ Here's a working version: http://www.microlinux.fr/microlinux/desktop-14.2-source/x/skippy-xd/ I suggest to upload the patched version to SBo, since this is a major bug: skippy-xd doesn't work correctly on systems with more than one user. And thanks again to Matteo and bassmadrigal for the help. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From edps.mundognu at gmail.com Wed Feb 15 21:24:55 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 15 Feb 2017 19:24:55 -0200 Subject: [Slackbuilds-users] Suggestion to patch skippy-xd Message-ID: I can submit a updated version with suggested sources, tested here on x86_64. Thanks! Edinaldo. From aclemons at runbox.no Thu Feb 16 19:34:02 2017 From: aclemons at runbox.no (Andrew Clemons) Date: Fri, 17 Feb 2017 08:34:02 +1300 Subject: [Slackbuilds-users] uid and gid for verm Message-ID: <20170216193401.GA9553@runbox.no> I'd like to submit a slackbuild for verm?. Could I get a user and group allocated with the same name? Thanks, ? https://github.com/willbryant/verm -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From chytraeu at sdf.org Thu Feb 16 23:55:05 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Thu, 16 Feb 2017 17:55:05 -0600 Subject: [Slackbuilds-users] host source for dash-0.5.9.1 Message-ID: Hi, Can someone upload the source for dash-0.5.9.1 to SlackBuilds direct links? I found the source at http://ftp.openbsd.org/pub/OpenBSD/distfiles//dash-0.5.9.1.tar.gz. I'm updating the package to the latest version. Also, the home page for dash at http://gondor.apana.org.au/~herbert/dash/ is offline. So I don't know what to do for that in the *.info file. Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From ryanpcmcquen at member.fsf.org Fri Feb 17 00:03:28 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Thu, 16 Feb 2017 16:03:28 -0800 Subject: [Slackbuilds-users] host source for dash-0.5.9.1 In-Reply-To: References: Message-ID: On Thursday, February 16, 2017, Donald Cooley wrote: > Hi, > > Can someone upload the source for dash-0.5.9.1 to SlackBuilds direct > links? I found the source at > http://ftp.openbsd.org/pub/OpenBSD/distfiles//dash-0.5.9.1.tar.gz. > > I'm updating the package to the latest version. > Hey Donald, I've added it. Let me know what you SF username is and I can add you to SBo direct links so you can add stuff in the future. :^) https://sourceforge.net/projects/slackbuildsdirectlinks/files/dash/dash-0.5.9.1.tar.gz -- --- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From chytraeu at sdf.org Fri Feb 17 01:19:25 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Thu, 16 Feb 2017 19:19:25 -0600 Subject: [Slackbuilds-users] host source for dash-0.5.9.1 In-Reply-To: References: Message-ID: <1cd1db73-e928-8b33-3992-9362243f127d@sdf.org> On 02/16/2017 06:03 PM, Ryan P.C. McQuen wrote: > > > On Thursday, February 16, 2017, Donald Cooley > wrote: > > Hi, > > Can someone upload the source for dash-0.5.9.1 to SlackBuilds direct > links? I found the source at > http://ftp.openbsd.org/pub/OpenBSD/distfiles//dash-0.5.9.1.tar.gz > . > > I'm updating the package to the latest version. > > > Hey Donald, > > I've added it. Let me know what you SF username is and I can add you > to SBo direct links so you can add stuff in the future. :^) > > https://sourceforge.net/projects/slackbuildsdirectlinks/files/dash/dash-0.5.9.1.tar.gz > > > -- > --- > -Ryan > [ryanpcmcquen.org ] > Thanks Ryan. My SF username is chytraeus -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From jebrhansen+SBo at gmail.com Fri Feb 17 16:09:11 2017 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 17 Feb 2017 11:09:11 -0500 Subject: [Slackbuilds-users] Fwd: Download link broken for redeclipse SlackBuild In-Reply-To: References: <20170217154131.xd3inizxbwnz4l5g@viking2.falor> Message-ID: SBo Admins, I have been given permission to take over maintenance of redeclipse by the current maintainer. I had created a patch to fix a broken download link and sent it to him, but he doesn't have the time to maintain it and asked if I'd like to take over. I am not currently at home to easily change the contact details in the .info, and I'd like to at least get it building before this weekend's update goes out, so attached you will find the patch to fix it. I'll work on getting an updated SlackBuild for v1.5.8 submitted this weekend (it's not a simple version bump since it now at least requires SDL2 -- not sure if there's other required dependencies, but I'll figure it out). Let me know if there's any questions. Jeremy ---------- Forwarded message ---------- From: Jeremy Hansen Date: Fri, Feb 17, 2017 at 10:48 AM Subject: Re: Download link broken for redeclipse SlackBuild To: Erik Falor Sure. I'll send the patch to Willy for 1.5.1, and I'll try to get an updated SlackBuild for 1.5.8 out this weekend. On Fri, Feb 17, 2017, 10:41 AM Erik Falor wrote: > On Thu, Feb 16, 2017 at 08:54:50PM -0500, Jeremy Hansen wrote: > > Erik, > > I tried installing redeclipse earlier today, but the download link is > > no longer valid. I found the source on github and updated the .info > and > > SlackBuild for it (the tarball name changed because the repo name is > > "base". There is a patch attached if you want to look at it. If you'd > > like, I could also send it to Willy... maybe it could make it into > this > > weekend's update. > > Also, just as an FYI, there are newer versions from the 1.5.1 that was > > released in Apr 2015. The latest is now 1.5.8 released last month, but > > it seems they've switched to SDL2, so there might be additional > > dependencies. I haven't tried it at all yet. > > [1]https://github.com/red-eclipse/base/releases > > Thanks for your work on this. > > Jeremy > > Hi Jeremy, > > I'm sorry that you've had difficulty with the Red Eclipse SlackBuild. > I have been meaning to update that script for a long time, but I just > haven't had much time to play games for the last year or more. > > Yours isn't the first request I've received to update this SlackBuild, > and I feel really bad about letting it languish. But I just don't see > myself getting more free time in the near future. Since you've already > fixed it this time, would you be willing to take on the maintenance of > this script? That would be a relief to me, and I know you'd be several > people's hero. > > -- > Erik Falor > Registered Linux User #445632 http://unnovative.net > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-download-link.patch Type: application/octet-stream Size: 1714 bytes Desc: not available URL: From ryanpcmcquen at member.fsf.org Fri Feb 17 16:14:00 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Fri, 17 Feb 2017 08:14:00 -0800 Subject: [Slackbuilds-users] host source for dash-0.5.9.1 In-Reply-To: <1cd1db73-e928-8b33-3992-9362243f127d@sdf.org> References: <1cd1db73-e928-8b33-3992-9362243f127d@sdf.org> Message-ID: Thanks Ryan. My SF username is chytraeus Thanks, you're in there! -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Feb 17 16:15:51 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 17 Feb 2017 23:15:51 +0700 Subject: [Slackbuilds-users] uid and gid for verm In-Reply-To: <20170216193401.GA9553@runbox.no> References: <20170216193401.GA9553@runbox.no> Message-ID: <2cec533f-f52c-9eb9-6837-f364a75e2b9f@slackbuilds.org> > I'd like to submit a slackbuild for verm?. Could I get a user and group > allocated with the same name? You can use 346 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From martijn at inlv.org Fri Feb 17 16:31:06 2017 From: martijn at inlv.org (Martijn Dekker) Date: Fri, 17 Feb 2017 17:31:06 +0100 Subject: [Slackbuilds-users] dash with libedit [was: host source for dash-0.5.9.1] In-Reply-To: References: Message-ID: Hi Donald, hi all, dash supports linking against libedit (which is also on slackbuilds.org) to provide basic editing capabilities on the interactive command line. This would involve adding '--with-libedit' to the 'configure' invocation and adding libedit as a dependency, perhaps as an option triggered by an environment variable. Please consider enabling this. Thanks, - M. From baildon.research at googlemail.com Fri Feb 17 22:18:28 2017 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 17 Feb 2017 22:18:28 +0000 Subject: [Slackbuilds-users] Fwd: Download link broken for redeclipse SlackBuild In-Reply-To: References: <20170217154131.xd3inizxbwnz4l5g@viking2.falor> Message-ID: All good and committed thanks :) -D. From chytraeu at sdf.org Sat Feb 18 00:44:52 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Fri, 17 Feb 2017 18:44:52 -0600 Subject: [Slackbuilds-users] host source for dash-0.5.9.1 In-Reply-To: References: <1cd1db73-e928-8b33-3992-9362243f127d@sdf.org> Message-ID: <48091893-b6ab-d6a9-c2b0-13eefd01d6b1@sdf.org> On 02/17/2017 10:14 AM, Ryan P.C. McQuen wrote: > >> Thanks Ryan. My SF username is chytraeus > > > > Thanks, you're in there! > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Ryan, I see that you added me. But I can't add any files or folders. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From ryanpcmcquen at member.fsf.org Sat Feb 18 00:59:06 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Fri, 17 Feb 2017 16:59:06 -0800 Subject: [Slackbuilds-users] host source for dash-0.5.9.1 In-Reply-To: <48091893-b6ab-d6a9-c2b0-13eefd01d6b1@sdf.org> References: <1cd1db73-e928-8b33-3992-9362243f127d@sdf.org> <48091893-b6ab-d6a9-c2b0-13eefd01d6b1@sdf.org> Message-ID: > > Ryan, I see that you added me. But I can't add any files or folders. > Weird, maybe email me directly and we can work it out so we don't pollute the mailing list. You should have the same permissions as everyone else. -- --- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Feb 18 01:13:24 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 18 Feb 2017 08:13:24 +0700 Subject: [Slackbuilds-users] Updates - 20170218.1 Message-ID: <570dd811-e936-0407-82cb-3e6c152d662a@slackbuilds.org> Hi folks we have some security updates on this batch of release: - flashplayer-plugins/pepperflash-plugins - webkit2gtk LibreOffice 5.3 from source is now rebuilt with a patch to fix firebase build race and also updated nvidia-{driver,kernel} for legacy drivers. Lastly, wine-staging is now updated to 2.1. Please note that wine-staging is a development release, but it adds more interesting features compared to stable releases. Thanks to all maintainers!!! Sat Feb 18 00:55:39 UTC 2017 academic/CAFS_divergence: Added (functional shift clustering). academic/FCSalyzer: Updated for version 0.9.13_alpha. academic/fityk: Added (nonlinear curve fitting). audio/jack-keyboard: Updated for version 2.7.1. audio/lv2-mda-metapiano: Fix HOMEPAGE. desktop/gtk-theme-Greybird: Updated for version 3.22.1. desktop/plasmaxplanet: Fix links. desktop/qtile: Updated for version 0.10.7. desktop/skippy-xd: Updated for version 0.5.1. desktop/wmtime: Add man page. development/Catch: Updated for version 1.7.2. development/SQLAlchemy: Updated for version 1.1.5. development/antlr2: Add compiler flags. development/bmake: Updated for version 20170201, new maintainer. development/camlp5: Fixed download. development/conan: Updated for version 0.19.2. development/diffoscope: Updated for version 77. development/dmd: Updated for version 2.073.1. development/electron: Added (cross-platform building library). development/hackrf: Fixed file ownership. development/hhvm: Updated for version 3.15.6. development/hopper: Added (disassembler). development/ioncube-loader: Updated for version 6.0.9. development/mono: Updated for version 4.6.2.16. development/universal-ctags: Updated for version d2efd07. development/vscode: Updated for version 1.9.1. games/advancemame: Updated for version 3.2, new maintainer. games/advancescan: Updated for version 1.18, new maintainer. games/edgar: Updated for version 1.26. games/ffgo: Added (graphical launcher for FlightGear). games/fgo: Fixed doinst.sh. games/mame: Support optional GroovyMAME patch. games/redeclipse: Fixed download. gis/Fiona: Updated for version 1.7.3. gis/josm: Updated for version 11526. gis/routino: New maintainer, switch to i586. graphics/pencil3: Added (Sketching and GUI prototyping tool). graphics/ristretto: Updated for version 0.8.2. haskell/haskell-base-compat: Added (backported functions). haskell/haskell-cmark: Updated for version 0.5.5. haskell/haskell-wl-pprint-text: Updated for version 1.1.1.0. libraries/CondConfigParser: Updated for version 1.0.3. libraries/Hypodermic: Fixed download. libraries/batinfo: Updated for version 0.4.2. libraries/flatbuffers: Updated for version 1.6.0. libraries/gdl: Updated for version 3.22.0. libraries/gtk-sharp: Updated for version 2.12.40. libraries/gtkhtml: Updated for version 4.10.0. libraries/libmseed: Update DOWNLOAD url. libraries/libnfs: Updated for version 1.11.0 libraries/libucil: Updated for version 20160609. libraries/libunicapgtk: Updated for version 20160609. libraries/msgpack-c: Updated for version 2.1.1. libraries/pymdstat: Switch to i586, tweak download. libraries/python3-pillow: Switch to i586. libraries/webkit2gtk: Updated for version 2.14.5. libraries/xylib: Added (x-y data from powder diffraction etc). misc/grc: Amended SlackBuild. misc/no-more-secrets: Updated for version 0.3.0. misc/subsurface: Updated for version 4.6.1 multimedia/QMPlay2: Added (video/audio player). multimedia/flashplayer-plugin: Updated for version 24.0.0.221. multimedia/gpodder: Updated for version 3.9.3. multimedia/guvcview: Updated for version 2.0.5. multimedia/mpv: Updated for version 0.22.0 + new maintainer. multimedia/opera-developer-ffmpeg-codecs: Updated for v 57.0.2979.0. multimedia/pepperflash-plugin: Updated for version 24.0.0.221. multimedia/ripit: Update DOWNLOAD url. multimedia/sinthgunt: Fixed download, applied patch. multimedia/spotify: Updated for version 1.0.49. multimedia/ucview: Switch to i586, tweak download. multimedia/vlsub: Updated for version 0.10.2. network/bottle: Updated for version 0.12.13. network/flexget: Updated for version 2.9.20. network/nicotine+: Fixed download. network/otter: Updated for version 0.9.12. network/pirate-get: Added (command line interface for TPB). network/vivaldi: Updated for version 1.7.735.46. network/you-get: Updated for version 0.4.652. network/youtube-dl: Updated for version 2017.02.11. office/LibreOffice: Upstream patch for firebird build race office/MasterPDFEditor: Updated for version 4.0.40. office/alot: Updated for version 0.5.1. office/calibre: Updated for version 2.79.1 office/hunspell-en: Updated for version 2017.01.22 + new maintainer. office/hunspell-es: Update README and slack-desc. office/jstock: Updated for version 1.0.7.20. office/keepassxc: Updated for version 2.1.2. perl/perl-Devel-PatchPerl: Updated for version 1.48. perl/perl-Devel-Symdump: Updated for version 2.18. perl/perl-File-Save-Home: Updated for version 0.10. perl/perl-IO-Interface: Fixed deps. perl/perl-Math-BigInt: Updated for version 1.999809. perl/perl-Math-GMPz: Updated for version 0.45. perl/perl-Mojolicious: Updated for version 7.26. perl/perl-class-accessor: New maintainer + new download. perl/perl-file-path-expand: New maintainer + new download. perl/perl-lirc-client: New maintainer + switch to i586. perl/perl-tk: New maintainer + switch to i586. python/bsddb3: Added (Python interface for Berkeley DB). python/cairocffi: Updated for version 0.8.0. python/hgsubversion: Updated for version 1.8.7. python/plaso: Updated for version 1.5.1. python/psutil: Updated for version 5.1.3 python/py-cpuinfo: Added (retrieve CPU information). python/py3sensors: Fix md5sum, switch to i586. python/python-axolotl-curve25519: Updated for version 0.1. python/python-dateutil: Updated for version 2.6.0 python/python-xcffib: Updated for version 0.5.1. python/terminado: Added (terminals served by tornado websockets). python/veryprettytable: Added (Python tabular library). ruby/rubygem-bundler: Updated for version 1.14.4. ruby/rubygem-lolcat: Added (Rainbows and unicorns). ruby/rubygem-paint: Added (Ruby gem for ANSI terminal colors). ruby/rubygem-trollop: Updated for version 2.1.2. ruby/sequel: Updated for version 4.43.0. system/autocutsel: Updated for version 0.10.0, new maintainer. system/dash: Updated for version 0.5.9.1. system/glances: Updated for version 2.8.2. system/isdct: Updated for version 3.0.3. system/man-db: Updated for version 2.7.6.1. system/nvidia-legacy304-driver: Updated for version 304.135. system/nvidia-legacy304-kernel: Updated for version 304.135. system/nvidia-legacy340-driver: Updated for version 340.102. system/nvidia-legacy340-kernel: Updated for version 340.102. system/onerng: Added (entropy generator). system/openrc-services: Updated for version 20170217. system/redis: Updated for version 3.2.8. system/reiser4progs: Fix 3rd party linking. system/wine-staging: Updated for version 2.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From Jim.Diamond at acadiau.ca Sat Feb 18 18:22:54 2017 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 18 Feb 2017 14:22:54 -0400 Subject: [Slackbuilds-users] Updates - 20170218.1 PEPPERFLASH md5sum In-Reply-To: <570dd811-e936-0407-82cb-3e6c152d662a@slackbuilds.org> References: <570dd811-e936-0407-82cb-3e6c152d662a@slackbuilds.org> Message-ID: <20170218182254.GA18777@jdiamond-nb.acadiau.ca> On Sat, Feb 18, 2017 at 08:13 (+0700), Willy Sudiarto Raharjo wrote: > Hi folks > we have some security updates on this batch of release: > - flashplayer-plugins/pepperflash-plugins > multimedia/pepperflash-plugin: Updated for version 24.0.0.221. It seems the md5sum for pepperflash is not quite right: - sboupgrade pepperflash-plugin This package contains Adobe's PPAPI Flash Plugin. You will have to accept the bundled license file if you want to use this closed-source plugin. Proceed with pepperflash-plugin? [y] pepperflash-plugin added to upgrade queue. Upgrade queue: pepperflash-plugin Are you sure you wish to continue? [y] --2017-02-18 14:18:41-- https://fpdownload.adobe.com/pub/flashplayer/pdc/24.0.0.221/flash_player_ppapi_linux.x86_64.tar.gz Resolving fpdownload.adobe.com (fpdownload.adobe.com)... 104.93.183.169 Connecting to fpdownload.adobe.com (fpdownload.adobe.com)|104.93.183.169|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 9479634 (9.0M) [application/x-gzip] Saving to: ?flash_player_ppapi_linux.x86_64.tar.gz? flash_player_ppapi_ 100%[===================>] 9.04M 10.6MB/s in 0.9s 2017-02-18 14:18:42 (10.6 MB/s) - ?flash_player_ppapi_linux.x86_64.tar.gz? saved [9479634/9479634] --2017-02-18 14:18:42-- ftp://slackware.uk/sbosrcarch/by-md5/1/e/1e687be20a421d6844140afa56006cfd/flash_player_ppapi_linux.x86_64.tar.gz => ?flash_player_ppapi_linux.x86_64.tar.gz? Resolving slackware.uk (slackware.uk)... 91.109.244.240 Connecting to slackware.uk (slackware.uk)|91.109.244.240|:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD (1) /sbosrcarch/by-md5/1/e/1e687be20a421d6844140afa56006cfd ... done. ==> SIZE flash_player_ppapi_linux.x86_64.tar.gz ... done. ==> PASV ... done. ==> RETR flash_player_ppapi_linux.x86_64.tar.gz ... No such file ?flash_player_ppapi_linux.x86_64.tar.gz?. Unable to download/verify source file(s) for pepperflash-plugin: md5sum failure for ..../distfiles/flash_player_ppapi_linux.x86_64.tar.gz. Do you want to proceed? [n] Failures: pepperflash-plugin: md5sum failure for /usr/local/poo/usr-sbo-142/distfiles/flash_player_ppapi_linux.x86_64.tar.gz. Cheers. Jim From baildon.research at googlemail.com Sat Feb 18 18:34:02 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 18 Feb 2017 18:34:02 +0000 Subject: [Slackbuilds-users] Updates - 20170218.1 PEPPERFLASH md5sum In-Reply-To: <20170218182254.GA18777@jdiamond-nb.acadiau.ca> References: <570dd811-e936-0407-82cb-3e6c152d662a@slackbuilds.org> <20170218182254.GA18777@jdiamond-nb.acadiau.ca> Message-ID: Thanks for the report, pepperflash-plugin and a couple more are fixed in my branch and they should be in the next public update Cheers -D. From matteo.bernardini at gmail.com Sat Feb 18 18:38:57 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 18 Feb 2017 19:38:57 +0100 Subject: [Slackbuilds-users] Updates - 20170218.1 PEPPERFLASH md5sum In-Reply-To: References: <570dd811-e936-0407-82cb-3e6c152d662a@slackbuilds.org> <20170218182254.GA18777@jdiamond-nb.acadiau.ca> Message-ID: 2017-02-18 19:34 GMT+01:00 David Spencer : > Thanks for the report, pepperflash-plugin and a couple more are fixed > in my branch and they should be in the next public update ups! sorry and thanks guys... Matteo From hostmaster at slackonly.com Sat Feb 18 20:37:30 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sat, 18 Feb 2017 12:37:30 -0800 Subject: [Slackbuilds-users] anki Message-ID: <5721edf3-d207-b00c-1791-78f5d80ec317@slackonly.com> Hi!, anki website has removed the source. New source: http://pkgs.fedoraproject.org/lookaside/pkgs/anki/anki-2.0.39-source.tgz/sha512/010f59ce6d44546587b50ccaded2742bc7735dca1cca5c296317ef1d4401c7f2bae5af7946b163a8ae4e5f99268b3cf40a9ac5b1f9bb24cee715c68d4e4ef2c5/anki-2.0.39-source.tgz (md5sum match). Also current version is 2.0.42. Thanks From edps.mundognu at gmail.com Sat Feb 18 22:31:29 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Sat, 18 Feb 2017 20:31:29 -0200 Subject: [Slackbuilds-users] beets not running Message-ID: Hi guys, here on Slack 14.2 i686 beets not running without installation of "six": Traceback (most recent call last): File "/usr/bin/beet", line 5, in from pkg_resources import load_entry_point File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2927, in @_call_aside File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2913, in _call_aside f(*args, **kwargs) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2940, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 635, in _build_master ws.require(__requires__) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 943, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 829, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'six>=1.9' distribution was not found and is required by beets and six is not listed as dependencie or in README. From willysr at slackbuilds.org Sun Feb 19 01:38:38 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Feb 2017 08:38:38 +0700 Subject: [Slackbuilds-users] anki In-Reply-To: <5721edf3-d207-b00c-1791-78f5d80ec317@slackonly.com> References: <5721edf3-d207-b00c-1791-78f5d80ec317@slackonly.com> Message-ID: > anki website has removed the source. > > New source: > http://pkgs.fedoraproject.org/lookaside/pkgs/anki/anki-2.0.39-source.tgz/sha512/010f59ce6d44546587b50ccaded2742bc7735dca1cca5c296317ef1d4401c7f2bae5af7946b163a8ae4e5f99268b3cf40a9ac5b1f9bb24cee715c68d4e4ef2c5/anki-2.0.39-source.tgz > (md5sum match). > > Also current version is 2.0.42. Thanks, download location fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Feb 19 02:04:12 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Feb 2017 09:04:12 +0700 Subject: [Slackbuilds-users] beets not running In-Reply-To: References: Message-ID: <373334f1-b28c-6afd-a41e-6661d51b8e2b@slackbuilds.org> > here on Slack 14.2 i686 beets not running without installation of "six": > > Traceback (most recent call last): > File "/usr/bin/beet", line 5, in > from pkg_resources import load_entry_point > File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", > line 2927, in > @_call_aside > File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", > line 2913, in _call_aside > f(*args, **kwargs) > File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", > line 2940, in _initialize_master_working_set > working_set = WorkingSet._build_master() > File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", > line 635, in _build_master > ws.require(__requires__) > File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", > line 943, in require > needed = self.resolve(parse_requirements(requirements)) > File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", > line 829, in resolve > raise DistributionNotFound(req, requirers) > pkg_resources.DistributionNotFound: The 'six>=1.9' distribution was not > found and is required by beets > > and six is not listed as dependencie or in README. Thanks fixed on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chytraeu at sdf.org Sun Feb 19 23:43:32 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Sun, 19 Feb 2017 17:43:32 -0600 Subject: [Slackbuilds-users] dash with libedit [was: host source for dash-0.5.9.1] In-Reply-To: References: Message-ID: <20e3a271-7d9c-10f5-f850-4323587d97fa@sdf.org> On 02/17/2017 10:31 AM, Martijn Dekker wrote: > Hi Donald, hi all, > > dash supports linking against libedit (which is also on > slackbuilds.org) to provide basic editing capabilities on the > interactive command line. This would involve adding '--with-libedit' > to the 'configure' invocation and adding libedit as a dependency, > perhaps as an option triggered by an environment variable. Please > consider enabling this. > > Thanks, > > - M. > I'll look into this soon. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From edps.mundognu at gmail.com Mon Feb 20 00:56:06 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Sun, 19 Feb 2017 21:56:06 -0300 Subject: [Slackbuilds-users] thunar-archive-plugin deps Message-ID: We recently saw a topic here: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-December/017685.html The fact is: xarchiver is not necessair for build thunar-archive-plugin, and him or file-roller works well with thunar-archive-plugin. So... why not remove xarchiver as dep and listed him or fille-roller (or both) in README as optional dep? * outside this, file-roller is much more faster than xarchiver for create packed files. In my *Box install .. from XFCE i have only the following packages installed: Thunar thunar-volman exo libxfce4ui libxfce4util libxfconf xfce4-screenshooter xfce4-notifyd tumbler and from SBo, this: https://gist.github.com/fccc1c02fa58f57f9af81ce9c3c070b9 Cheers, Edinaldo. From kingbeowulf at gmail.com Mon Feb 20 02:34:24 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 19 Feb 2017 18:34:24 -0800 Subject: [Slackbuilds-users] thunar-archive-plugin deps In-Reply-To: References: Message-ID: On 02/19/2017 04:56 PM, Edinaldo wrote: > We recently saw a topic here: > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-December/017685.html > > > The fact is: xarchiver is not necessair for build thunar-archive-plugin, > and him or > file-roller works well with thunar-archive-plugin. > > So... why not remove xarchiver as dep and listed him or fille-roller (or > both) in README > as optional dep? > Actually, that's a good point. The thunar-archive-plugin source provides thunar integration (.tap) files for ark and file-roller out-of-the-box and does not need an archiver present to compile. Thus, technically, no dependencies are needed. Ark and File-roller can be listed as an optional run-time dependencies. Xarchiver provides a .tap file for thunar/thunar-archive-plugin capatibility. Since Xarchiver is not part of a default Slackware installation, it should also be listed as on optional run-time dependency. To summarize: optional deps: Ark (part of Slackware), File-roller (on SBo), xarchiver (on SBo) -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Mon Feb 20 02:41:47 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 19 Feb 2017 18:41:47 -0800 Subject: [Slackbuilds-users] [Sackbuilds-users] nvidia-{driver, kernel} 375.39 Message-ID: <7dd37957-dced-aaf8-5d72-6af22fc83049@gmail.com> I just posted a workable script using the 'old method' and not nvidia-installer. Since there are a number of upstream security fixes, I recommend pushing 375.39 out as soon as possible. Sorry for the delay. We can kill the old stuff in the 'nvidia-pending' branch. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Feb 20 07:12:53 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Feb 2017 14:12:53 +0700 Subject: [Slackbuilds-users] [Sackbuilds-users] nvidia-{driver, kernel} 375.39 In-Reply-To: <7dd37957-dced-aaf8-5d72-6af22fc83049@gmail.com> References: <7dd37957-dced-aaf8-5d72-6af22fc83049@gmail.com> Message-ID: <393faabb-cde9-6c3d-773a-db0938e36346@slackbuilds.org> > I just posted a workable script using the 'old method' and not > nvidia-installer. Since there are a number of upstream security fixes, I > recommend pushing 375.39 out as soon as possible. Sorry for the delay. As soon as Ponce test the new update, i can issue an unscheduled public update > We can kill the old stuff in the 'nvidia-pending' branch. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From duncan_roe at acslink.net.au Mon Feb 20 21:27:40 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Tue, 21 Feb 2017 08:27:40 +1100 Subject: [Slackbuilds-users] Can a moderator please remove daemontools.tar.gz from pending Message-ID: <20170220212740.GA23963@dimstar.local.net> Silly me - I can't use https://slackbuilds.org/remove/ because I didn't keep the old file so don't know the checksum. Thanks ... Duncan. From ryanpcmcquen at member.fsf.org Mon Feb 20 22:31:40 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Mon, 20 Feb 2017 14:31:40 -0800 Subject: [Slackbuilds-users] Can a moderator please remove daemontools.tar.gz from pending In-Reply-To: <20170220212740.GA23963@dimstar.local.net> References: <20170220212740.GA23963@dimstar.local.net> Message-ID: On Feb 20, 2017 1:32 PM, "Duncan Roe" wrote: Silly me - I can't use https://slackbuilds.org/remove/ because I didn't keep the old file so don't know the checksum. You should have gotten an email: New SBo Upload: daemontools.tar.gz -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Feb 21 00:56:55 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 21 Feb 2017 07:56:55 +0700 Subject: [Slackbuilds-users] Can a moderator please remove daemontools.tar.gz from pending In-Reply-To: References: <20170220212740.GA23963@dimstar.local.net> Message-ID: <36f7ba1b-57d5-f3a7-56f9-7acc092dde5e@slackbuilds.org> > Silly me - I can't use https://slackbuilds.org/remove/ because I didn't > keep the > old file so don't know the checksum. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From duncan_roe at acslink.net.au Tue Feb 21 01:45:40 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Tue, 21 Feb 2017 12:45:40 +1100 Subject: [Slackbuilds-users] Can a moderator please remove daemontools.tar.gz from pending In-Reply-To: References: <20170220212740.GA23963@dimstar.local.net> Message-ID: <20170221014540.GA24854@dimstar.local.net> On Mon, Feb 20, 2017 at 02:31:40PM -0800, Ryan P.C. McQuen wrote: > On Feb 20, 2017 1:32 PM, "Duncan Roe" wrote: > > > Silly me - I can't use https://slackbuilds.org/remove/ because I didn't > > keep the > > old file so don't know the checksum. > > > > You should have gotten an email: > > New SBo Upload: daemontools.tar.gz Thanks Ryan, I didn't think of that. I could have used it to remove but Willy beat me to it: Thanks Willy Cheers ... Duncan From info at microlinux.fr Tue Feb 21 07:42:27 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 21 Feb 2017 08:42:27 +0100 Subject: [Slackbuilds-users] GNU Backgammon Message-ID: <46bbd1b9-998a-3e12-e542-e891da364cdd@microlinux.fr> Hi, I recently wanted to build gnubg, but the package doesn't build, since source aren't available anymore. Simply doing a version bump doesn't work because the new sources are packaged differently and stuff ends up in different places, so I just wrote a new SlackBuild from scratch myself, which builds fine on both Slackware 14.1 and 14.2. http://www.microlinux.fr/microlinux/extras-14.2-source/gnubg/ Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Tue Feb 21 09:58:20 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 21 Feb 2017 16:58:20 +0700 Subject: [Slackbuilds-users] Updates - 20170221.1 Message-ID: <4cf0700e-6c6f-1143-3c0a-76d6a3d64f2f@slackbuilds.org> Hi folks sorry for the unscheduled updates, but some of the updates are considered important and it also have a security update, thus this update is pushed. Tue Feb 21 09:45:46 UTC 2017 audio/jack-keyboard: Make lash optional again. desktop/anki: Update DOWNLOAD source. development/ChezScheme: Added (A scheme implementation). development/mutagen: Add python3 support. development/p4: Updated for version 2016.2.1487173. development/p4d: Updated for version 2016.2.1487173. development/spdlog: Updated for version 0.12.0. games/redeclipse: Updated for version 1.5.8. games/yamagi-quake2: Update README. gis/osgEarth: Fixed md5sum. graphics/inkscape: Updated for version 0.92.1. libraries/CherryPy: Updated for version 10.1.1. libraries/gtk-sharp: Minor change in SlackBuild. libraries/libc++: Added (LLVM C++ standard library implementation). libraries/virglrenderer: Updated for version 0.6.0. multimedia/QMPlay2: Updated for version 17.02.12. multimedia/beets: Update DEP. multimedia/pepperflash-plugin: Fixed md5sum. multimedia/podcastparser: Added (Python RSS feed parser). network/authbind: Updated for version 2.1.2. network/flexget: Updated for version 2.10.2. network/heimdal: Updated for version 7.1.0. network/nicotine+: Updated for version 1.4.1. network/pirate-get: Update README & .info file. network/telegram: Updated for version 1.0.12. network/you-get: Fixed md5sum. network/youtube-dl: Updated for version 2017.02.17. network/zsync: Added (client-side implementation of rsync). office/jstock: Fixed download. perl/perl-CPAN-Perl-Releases: Updated for version 3.10. perl/perl-CPANPLUS-Dist-Build: Updated for version 0.82. perl/perl-CPANPLUS: Updated for version 0.9164. python/cheroot: Added (pure-Python HTTP). python/portend: Added (TCP ports monitor). python/tempora: Added (tool for date and time). system/bit-babbler: Update README. system/fzf: Updated for version 0.16.5. system/nvidia-driver: Updated for version 375.39. system/nvidia-kernel: Updated for version 375.39. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slacker at slaphappygeeks.com Tue Feb 21 09:59:48 2017 From: slacker at slaphappygeeks.com (Slacker) Date: Tue, 21 Feb 2017 02:59:48 -0700 Subject: [Slackbuilds-users] GNU Backgammon In-Reply-To: <46bbd1b9-998a-3e12-e542-e891da364cdd@microlinux.fr> References: <46bbd1b9-998a-3e12-e542-e891da364cdd@microlinux.fr> Message-ID: <16698569-6710-0e07-ab82-ccc244894a88@slaphappygeeks.com> Thanks Niki! Builds and works fine on my 32 bit 14.1 laptop. Robert On 02/21/2017 12:42 AM, Nicolas Kovacs wrote: > Hi, > > I recently wanted to build gnubg, but the package doesn't build, since > source aren't available anymore. Simply doing a version bump doesn't > work because the new sources are packaged differently and stuff ends up > in different places, so I just wrote a new SlackBuild from scratch > myself, which builds fine on both Slackware 14.1 and 14.2. > > http://www.microlinux.fr/microlinux/extras-14.2-source/gnubg/ > > Cheers, > > Niki > From info at microlinux.fr Tue Feb 21 10:22:27 2017 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 21 Feb 2017 11:22:27 +0100 Subject: [Slackbuilds-users] GNU Backgammon In-Reply-To: <16698569-6710-0e07-ab82-ccc244894a88@slaphappygeeks.com> References: <46bbd1b9-998a-3e12-e542-e891da364cdd@microlinux.fr> <16698569-6710-0e07-ab82-ccc244894a88@slaphappygeeks.com> Message-ID: Le 21/02/2017 ? 10:59, Slacker a ?crit : > Thanks Niki! > > Builds and works fine on my 32 bit 14.1 laptop. > > Robert You might want to install pangox-common and gtkglext for 3D support (both available on SBo). -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From falsetti at clansco.org Tue Feb 21 15:18:14 2017 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Tue, 21 Feb 2017 16:18:14 +0100 Subject: [Slackbuilds-users] terminix fails to build Message-ID: <20170221161814.bb6a57bea785953946d34630@clansco.org> seems like dmd issue : make[1]: Entering directory '/tmp/SBo/terminix-1.3.5' dmd -O -inline -release -version=StdLoggerDisableTrace -I/usr/include/d/gtkd-3/ -L-lvted-3 -L-L/usr/lib/ -L-lgtkd-3 -L-ldl -c source/secret/SchemaAttribute.d source/secret/Collection.d source/secret/Prompt.d source/secret/Secret.d source/secret/Service.d source/secret/Item.d source/secret/Schema.d source/secret/Value.d source/gx/util/array.d source/gx/util/string.d source/gx/gtk/dialog.d source/gx/gtk/x11.d source/gx/gtk/clipboard.d source/gx/gtk/cairo.d source/gx/gtk/vte.d source/gx/gtk/actions.d source/gx/gtk/threads.d source/gx/gtk/resource.d source/gx/gtk/util.d source/gx/terminix/shortcuts.d source/gx/terminix/preferences.d source/gx/terminix/application.d source/gx/terminix/sidebar.d source/gx/terminix/common.d source/gx/terminix/constants.d source/gx/terminix/cmdparams.d source/gx/terminix/colorschemes.d source/gx/terminix/prefwindow.d source/gx/terminix/sessionswitcher.d source/gx/terminix/terminal/layout.d source/gx/terminix/terminal/advpaste.d source/gx/terminix/terminal/te rminal.d source/gx/terminix/terminal/exvte.d source/gx/terminix/terminal/password.d source/gx/terminix/terminal/search.d source/gx/terminix/terminal/actions.d source/gx/terminix/encoding.d source/gx/terminix/profilewindow.d source/gx/terminix/appwindow.d source/gx/terminix/session.d source/gx/i18n/l10n.d source/secretc/secrettypes.d source/secretc/secret.d source/app.d source/x11/X.d source/x11/Xlib.d -ofterminix.o Internal error: backend/cg87.c 299 Makefile:1033: recipe for target 'terminix.o' failed make[1]: *** [terminix.o] Error 1 make[1]: Leaving directory '/tmp/SBo/terminix-1.3.5' From clansco at clansco.org Tue Feb 21 15:14:30 2017 From: clansco at clansco.org (clansco) Date: Tue, 21 Feb 2017 16:14:30 +0100 Subject: [Slackbuilds-users] terminix fails to build Message-ID: <20170221161430.fb33fd8398700b4520e96641@clansco.org> seems like dmd issue : make[1]: Entering directory '/tmp/SBo/terminix-1.3.5' dmd -O -inline -release -version=StdLoggerDisableTrace -I/usr/include/d/gtkd-3/ -L-lvted-3 -L-L/usr/lib/ -L-lgtkd-3 -L-ldl -c source/secret/SchemaAttribute.d source/secret/Collection.d source/secret/Prompt.d source/secret/Secret.d source/secret/Service.d source/secret/Item.d source/secret/Schema.d source/secret/Value.d source/gx/util/array.d source/gx/util/string.d source/gx/gtk/dialog.d source/gx/gtk/x11.d source/gx/gtk/clipboard.d source/gx/gtk/cairo.d source/gx/gtk/vte.d source/gx/gtk/actions.d source/gx/gtk/threads.d source/gx/gtk/resource.d source/gx/gtk/util.d source/gx/terminix/shortcuts.d source/gx/terminix/preferences.d source/gx/terminix/application.d source/gx/terminix/sidebar.d source/gx/terminix/common.d source/gx/terminix/constants.d source/gx/terminix/cmdparams.d source/gx/terminix/colorschemes.d source/gx/terminix/prefwindow.d source/gx/terminix/sessionswitcher.d source/gx/terminix/terminal/layout.d source/gx/terminix/terminal/advpaste.d source/gx/terminix/terminal/te rminal.d source/gx/terminix/terminal/exvte.d source/gx/terminix/terminal/password.d source/gx/terminix/terminal/search.d source/gx/terminix/terminal/actions.d source/gx/terminix/encoding.d source/gx/terminix/profilewindow.d source/gx/terminix/appwindow.d source/gx/terminix/session.d source/gx/i18n/l10n.d source/secretc/secrettypes.d source/secretc/secret.d source/app.d source/x11/X.d source/x11/Xlib.d -ofterminix.o Internal error: backend/cg87.c 299 Makefile:1033: recipe for target 'terminix.o' failed make[1]: *** [terminix.o] Error 1 make[1]: Leaving directory '/tmp/SBo/terminix-1.3.5' From philip at vd-hoeven.nl Tue Feb 21 15:44:10 2017 From: philip at vd-hoeven.nl (Philip van der Hoeven) Date: Tue, 21 Feb 2017 16:44:10 +0100 Subject: [Slackbuilds-users] terminix fails to build In-Reply-To: <20170221161814.bb6a57bea785953946d34630@clansco.org> References: <20170221161814.bb6a57bea785953946d34630@clansco.org> Message-ID: <1487691850.1571.1.camel@vd-hoeven.nl> On Tue, 2017-02-21 at 16:18 +0100, Fr?d?ric Falsetti wrote: > seems like dmd issue : > > make[1]: Entering directory '/tmp/SBo/terminix-1.3.5' > dmd -O -inline -release -version=StdLoggerDisableTrace > -I/usr/include/d/gtkd-3/ -L-lvted-3 -L-L/usr/lib/ -L-lgtkd-3 -L-ldl > -c source/secret/SchemaAttribute.d source/secret/Collection.d > source/secret/Prompt.d source/secret/Secret.d source/secret/Service.d > source/secret/Item.d source/secret/Schema.d source/secret/Value.d > source/gx/util/array.d source/gx/util/string.d source/gx/gtk/dialog.d > source/gx/gtk/x11.d source/gx/gtk/clipboard.d source/gx/gtk/cairo.d > source/gx/gtk/vte.d source/gx/gtk/actions.d source/gx/gtk/threads.d > source/gx/gtk/resource.d source/gx/gtk/util.d > source/gx/terminix/shortcuts.d source/gx/terminix/preferences.d > source/gx/terminix/application.d source/gx/terminix/sidebar.d > source/gx/terminix/common.d source/gx/terminix/constants.d > source/gx/terminix/cmdparams.d source/gx/terminix/colorschemes.d > source/gx/terminix/prefwindow.d source/gx/terminix/sessionswitcher.d > source/gx/terminix/terminal/layout.d > source/gx/terminix/terminal/advpaste.d source/gx/terminix/terminal/te > ?rminal.d source/gx/terminix/terminal/exvte.d > source/gx/terminix/terminal/password.d > source/gx/terminix/terminal/search.d > source/gx/terminix/terminal/actions.d source/gx/terminix/encoding.d > source/gx/terminix/profilewindow.d source/gx/terminix/appwindow.d > source/gx/terminix/session.d source/gx/i18n/l10n.d > source/secretc/secrettypes.d source/secretc/secret.d source/app.d > source/x11/X.d source/x11/Xlib.d -ofterminix.o > Internal error: backend/cg87.c 299 > Makefile:1033: recipe for target 'terminix.o' failed > make[1]: *** [terminix.o] Error 1 > make[1]: Leaving directory '/tmp/SBo/terminix-1.3.5' > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > It seems to work fine here: Slackware package /tmp/slackrepo.6Dy3T9/packages_terminix/terminix- 1.3.5-x86_64-2_SBo.txz created. Built ok:??terminix-1.3.5-x86_64- 2_SBo.txz??????????????????????????????16:34:34 Unmounting chroot ... :-) system/terminix Rebuilt (-: Perhaps it's a multilib issue ? Philip From matteo.bernardini at gmail.com Tue Feb 21 15:52:47 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 21 Feb 2017 16:52:47 +0100 Subject: [Slackbuilds-users] terminix fails to build In-Reply-To: <1487691850.1571.1.camel@vd-hoeven.nl> References: <20170221161814.bb6a57bea785953946d34630@clansco.org> <1487691850.1571.1.camel@vd-hoeven.nl> Message-ID: 2017-02-21 16:44 GMT+01:00 Philip van der Hoeven : > On Tue, 2017-02-21 at 16:18 +0100, Fr?d?ric Falsetti wrote: >> seems like dmd issue : >> >> make[1]: Entering directory '/tmp/SBo/terminix-1.3.5' >> dmd -O -inline -release -version=StdLoggerDisableTrace >> -I/usr/include/d/gtkd-3/ -L-lvted-3 -L-L/usr/lib/ -L-lgtkd-3 -L-ldl >> -c source/secret/SchemaAttribute.d source/secret/Collection.d >> source/secret/Prompt.d source/secret/Secret.d source/secret/Service.d >> source/secret/Item.d source/secret/Schema.d source/secret/Value.d >> source/gx/util/array.d source/gx/util/string.d source/gx/gtk/dialog.d >> source/gx/gtk/x11.d source/gx/gtk/clipboard.d source/gx/gtk/cairo.d >> source/gx/gtk/vte.d source/gx/gtk/actions.d source/gx/gtk/threads.d >> source/gx/gtk/resource.d source/gx/gtk/util.d >> source/gx/terminix/shortcuts.d source/gx/terminix/preferences.d >> source/gx/terminix/application.d source/gx/terminix/sidebar.d >> source/gx/terminix/common.d source/gx/terminix/constants.d >> source/gx/terminix/cmdparams.d source/gx/terminix/colorschemes.d >> source/gx/terminix/prefwindow.d source/gx/terminix/sessionswitcher.d >> source/gx/terminix/terminal/layout.d >> source/gx/terminix/terminal/advpaste.d source/gx/terminix/terminal/te >> rminal.d source/gx/terminix/terminal/exvte.d >> source/gx/terminix/terminal/password.d >> source/gx/terminix/terminal/search.d >> source/gx/terminix/terminal/actions.d source/gx/terminix/encoding.d >> source/gx/terminix/profilewindow.d source/gx/terminix/appwindow.d >> source/gx/terminix/session.d source/gx/i18n/l10n.d >> source/secretc/secrettypes.d source/secretc/secret.d source/app.d >> source/x11/X.d source/x11/Xlib.d -ofterminix.o >> Internal error: backend/cg87.c 299 >> Makefile:1033: recipe for target 'terminix.o' failed >> make[1]: *** [terminix.o] Error 1 >> make[1]: Leaving directory '/tmp/SBo/terminix-1.3.5' >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > It seems to work fine here: > > Slackware package /tmp/slackrepo.6Dy3T9/packages_terminix/terminix- > 1.3.5-x86_64-2_SBo.txz created. > > Built ok: terminix-1.3.5-x86_64- > 2_SBo.txz 16:34:34 > Unmounting chroot ... > :-) system/terminix Rebuilt (-: I can confirm Frederic's error on 32-bit. Matteo From willysr at slackbuilds.org Tue Feb 21 15:53:43 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 21 Feb 2017 22:53:43 +0700 Subject: [Slackbuilds-users] terminix fails to build In-Reply-To: References: <20170221161814.bb6a57bea785953946d34630@clansco.org> <1487691850.1571.1.camel@vd-hoeven.nl> Message-ID: <1dc40ecf-2c96-18a1-763e-aba6568e8c30@slackbuilds.org> > I can confirm Frederic's error on 32-bit. It does built on x86_64, so it's architecture spesific -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lspencer31 at cfl.rr.com Tue Feb 21 17:08:26 2017 From: lspencer31 at cfl.rr.com (lspencer31 at cfl.rr.com) Date: Tue, 21 Feb 2017 12:08:26 -0500 Subject: [Slackbuilds-users] [Sackbuilds-users] nvidia-{driver, kernel} 375.39 In-Reply-To: <393faabb-cde9-6c3d-773a-db0938e36346@slackbuilds.org> Message-ID: <20170221170826.8YXYT.140873.root@cdptpa-web01> Just to help you guys out, I have it working on two boxes here without a hitch, with just a version bump using the old method. One with a GT730 card and the other with a GTX550ti. ---- Willy Sudiarto Raharjo wrote: > > I just posted a workable script using the 'old method' and not > > nvidia-installer. Since there are a number of upstream security fixes, I > > recommend pushing 375.39 out as soon as possible. Sorry for the delay. > > As soon as Ponce test the new update, i can issue an unscheduled public > update > > > We can kill the old stuff in the 'nvidia-pending' branch. > > Done > > > -- > Willy Sudiarto Raharjo > From kingbeowulf at gmail.com Tue Feb 21 17:45:35 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 21 Feb 2017 09:45:35 -0800 Subject: [Slackbuilds-users] [Sackbuilds-users] nvidia-{driver, kernel} 375.39 In-Reply-To: <20170221170826.8YXYT.140873.root@cdptpa-web01> References: <20170221170826.8YXYT.140873.root@cdptpa-web01> Message-ID: On 02/21/2017 09:08 AM, lspencer31 at cfl.rr.com wrote: > Just to help you guys out, I have it working on two boxes here without a hitch, with just a version bump using the old method. One with a GT730 card and the other with a GTX550ti. > Any and all help is appreciated, but just bumping the old script is not really that simple. Nvidia moves/renames some libs with every major update, so in your case you could be missing some functionality with just a version bump. This script now more closely matches that of nvidia-installer. Highlights ========== /usr/lib/vdpau/libnvidia_vdpau formerly in /usr/lib/ GLVND wrappers for libGL and LIBEGL some new/added libs symlink changes keep Xorg libwfb instead of using Nvidia's COMPAT32 improvements fix nvidia-switch -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Wed Feb 22 02:49:03 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 21 Feb 2017 18:49:03 -0800 Subject: [Slackbuilds-users] Academic > topdraw keyword spelling correction Message-ID: <80157f25-3f4a-8990-6311-c9d1ef12c618@gmail.com> Just poking around and noticed: scetch -> sketch So FYI! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Feb 22 07:19:09 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 22 Feb 2017 14:19:09 +0700 Subject: [Slackbuilds-users] Academic > topdraw keyword spelling correction In-Reply-To: <80157f25-3f4a-8990-6311-c9d1ef12c618@gmail.com> References: <80157f25-3f4a-8990-6311-c9d1ef12c618@gmail.com> Message-ID: <2dccd651-8e14-a729-9725-8da1e19bdb63@slackbuilds.org> > Just poking around and noticed: > > scetch -> sketch Fixed -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From philip at vd-hoeven.nl Wed Feb 22 17:21:53 2017 From: philip at vd-hoeven.nl (Philip van der Hoeven) Date: Wed, 22 Feb 2017 18:21:53 +0100 Subject: [Slackbuilds-users] terminix fails to build In-Reply-To: <1dc40ecf-2c96-18a1-763e-aba6568e8c30@slackbuilds.org> References: <20170221161814.bb6a57bea785953946d34630@clansco.org> <1487691850.1571.1.camel@vd-hoeven.nl> <1dc40ecf-2c96-18a1-763e-aba6568e8c30@slackbuilds.org> Message-ID: <1487784113.4145.5.camel@vd-hoeven.nl> On Tue, 2017-02-21 at 22:53 +0700, Willy Sudiarto Raharjo wrote: > > I can confirm Frederic's error on 32-bit. > > It does built on x86_64, so it's architecture spesific > So I've been playing with this a bit today. I upgraded terminix to 1.5.0 and GtkD to 3.5.1 it still would not build, same error. However, if I remove -inline?from the DCFLAGS it does build, but it segfaults when running. gdb says this: (gdb) bt #0??0x09d0f298 in??() #1??0x0830277f in gx.terminix.application.Terminix.installAppMenu() () #2??0x08303bea in gx.terminix.application.Terminix.onAppStartup(gio.Application.Applicati on) () #3??0xffffffff in gio.Application.Application.callBackStartup(gtkc.giotypes.GApplication* , gio.Application.Application.OnStartupDelegateWrapper) () at /usr/lib/libgtkd-3.so.0 #4??0xffffffff in g_cclosure_marshal_VOID__VOID () at /usr/lib/libgobject-2.0.so.0 #5??0xffffffff in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0 #6??0xffffffff in??() at /usr/lib/libgobject-2.0.so.0 #7??0xffffffff in g_signal_emit_valist () at /usr/lib/libgobject- 2.0.so.0 #8??0xffffffff in g_signal_emit () at /usr/lib/libgobject-2.0.so.0 #9??0xffffffff in g_application_register () at /usr/lib/libgio-2.0.so.0 #10 0xffffffff in??() at /usr/lib/libgio-2.0.so.0 #11 0xffffffff in??() at /usr/lib/libgtk-3.so.0 #12 0xffffffff in g_application_run () at /usr/lib/libgio-2.0.so.0 #13 0xffffffff in gio.Application.Application.run(immutable(char)[][]) () at /usr/lib/libgtkd-3.so.0 #14 0x082d376f in D main () Well, that does not ring a bell with me. But I'm a bit sick so the brains don't really work ;-) I found an .deb for ubuntu but after extracting the executable it also segfaults. Anybody has a clue ? Philip From lspencer31 at cfl.rr.com Wed Feb 22 17:29:45 2017 From: lspencer31 at cfl.rr.com (Lenard Spencer) Date: Wed, 22 Feb 2017 12:29:45 -0500 Subject: [Slackbuilds-users] [Sackbuilds-users] nvidia-{driver, kernel} 375.39 In-Reply-To: References: <20170221170826.8YXYT.140873.root@cdptpa-web01> Message-ID: <0eb9dd6b-be47-8411-355b-1bdf19e0a22d@cfl.rr.com> I know I have not had any problems, but in just looking at the diff of nvidia-switch between the older versions and current I can see what you mean. On 02/21/2017 12:45 PM, King Beowulf wrote: > On 02/21/2017 09:08 AM, lspencer31 at cfl.rr.com wrote: >> Just to help you guys out, I have it working on two boxes here without a hitch, with just a version bump using the old method. One with a GT730 card and the other with a GTX550ti. >> > Any and all help is appreciated, but just bumping the old script is not > really that simple. Nvidia moves/renames some libs with every major > update, so in your case you could be missing some functionality with > just a version bump. This script now more closely matches that of > nvidia-installer. > > Highlights > ========== > /usr/lib/vdpau/libnvidia_vdpau formerly in /usr/lib/ > GLVND wrappers for libGL and LIBEGL > some new/added libs > symlink changes > keep Xorg libwfb instead of using Nvidia's > COMPAT32 improvements > fix nvidia-switch > > -Ed > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Feb 22 17:32:04 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 23 Feb 2017 00:32:04 +0700 Subject: [Slackbuilds-users] terminix fails to build In-Reply-To: <1487784113.4145.5.camel@vd-hoeven.nl> References: <20170221161814.bb6a57bea785953946d34630@clansco.org> <1487691850.1571.1.camel@vd-hoeven.nl> <1dc40ecf-2c96-18a1-763e-aba6568e8c30@slackbuilds.org> <1487784113.4145.5.camel@vd-hoeven.nl> Message-ID: <92f06b71-7bc1-e162-5499-6de668acb7b5@slackbuilds.org> > So I've been playing with this a bit today. > I upgraded terminix to 1.5.0 and GtkD to 3.5.1 it still would not > build, same error. > However, if I remove -inline from the DCFLAGS it does build, but it > segfaults when running. > gdb says this: > (gdb) bt > #0 0x09d0f298 in () > #1 0x0830277f in gx.terminix.application.Terminix.installAppMenu() () > #2 0x08303bea in > gx.terminix.application.Terminix.onAppStartup(gio.Application.Applicati > on) () > #3 0xffffffff in > gio.Application.Application.callBackStartup(gtkc.giotypes.GApplication* > , gio.Application.Application.OnStartupDelegateWrapper) () at > /usr/lib/libgtkd-3.so.0 > #4 0xffffffff in g_cclosure_marshal_VOID__VOID () at > /usr/lib/libgobject-2.0.so.0 > #5 0xffffffff in g_closure_invoke () at /usr/lib/libgobject-2.0.so.0 > #6 0xffffffff in () at /usr/lib/libgobject-2.0.so.0 > #7 0xffffffff in g_signal_emit_valist () at /usr/lib/libgobject- > 2.0.so.0 > #8 0xffffffff in g_signal_emit () at /usr/lib/libgobject-2.0.so.0 > #9 0xffffffff in g_application_register () at /usr/lib/libgio-2.0.so.0 > #10 0xffffffff in () at /usr/lib/libgio-2.0.so.0 > #11 0xffffffff in () at /usr/lib/libgtk-3.so.0 > #12 0xffffffff in g_application_run () at /usr/lib/libgio-2.0.so.0 > #13 0xffffffff in gio.Application.Application.run(immutable(char)[][]) > () at /usr/lib/libgtkd-3.so.0 > #14 0x082d376f in D main () > > Well, that does not ring a bell with me. But I'm a bit sick so the > brains don't really work ;-) > > I found an .deb for ubuntu but after extracting the executable it also > segfaults. > > Anybody has a clue ? perhaps reverting to older GtkD fix it ? I'm pretty sure the only change lately was just GtkD and not terminix nor dmd -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Wed Feb 22 22:14:23 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Wed, 22 Feb 2017 14:14:23 -0800 Subject: [Slackbuilds-users] pdfsam Message-ID: Hi!, pdfsam needs also as a dependency jdk: Error: JAVA_HOME is not defined correctly. We cannot execute /usr/lib64/java/bin/java Thanks! From hostmaster at slackonly.com Wed Feb 22 22:15:36 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Wed, 22 Feb 2017 14:15:36 -0800 Subject: [Slackbuilds-users] sources Message-ID: Hi!, Some sources fixes: academic/edsim51di md5sum is c0b5d0a37ed468db17fdf909357581a6 instead of 3458e49bda689445737041c0e69c3a8c desktop/numix-sx-theme upstream has update the source to 20170209: https://dl.opendesktop.org/api/files/download/id/1486611037/Numix-SX.tar.xz desktop/wmcliphist missing source, new source: https://svwh.dl.sourceforge.net/project/slackbuildsdirectlinks/wmcliphist/wmcliphist-latest.tar.gz Thanks... From yalhcru at gmail.com Wed Feb 22 22:19:59 2017 From: yalhcru at gmail.com (B Watson) Date: Wed, 22 Feb 2017 17:19:59 -0500 Subject: [Slackbuilds-users] pdfsam In-Reply-To: References: Message-ID: On 2/22/17, Panagiotis Nikolaou wrote: > pdfsam needs also as a dependency jdk: > > Error: JAVA_HOME is not defined correctly. > We cannot execute /usr/lib64/java/bin/java That's a consequence of apache-ant recently losing its hard dependency on jdk. Stuff that depends on apache-ant used to not have to list jdk, because apache-ant depended on jdk... which was incorrect (apache-ant can work with slackware's gcc-java, or openjdk). Other builds which might (or might not) be affected by this: academic/link-grammar development/Arduino development/eclim development/rstudio-desktop libraries/ant-contrib libraries/xalan libraries/xerces multimedia/JSampler office/LibreOffice office/fop office/ganttproject system/bootchart system/commons-daemon Maintainers of these might want to have a look... From yalhcru at gmail.com Wed Feb 22 22:26:02 2017 From: yalhcru at gmail.com (B Watson) Date: Wed, 22 Feb 2017 17:26:02 -0500 Subject: [Slackbuilds-users] sources In-Reply-To: References: Message-ID: On 2/22/17, Panagiotis Nikolaou wrote: > academic/edsim51di > md5sum is c0b5d0a37ed468db17fdf909357581a6 instead of > 3458e49bda689445737041c0e69c3a8c There's a copy of the file with the correct md5sum here: http://slackware.uk/sbosrcarch//by-md5/3/4/3458e49bda689445737041c0e69c3a8c/edsim51di.zip > desktop/numix-sx-theme > upstream has update the source to 20170209: > https://dl.opendesktop.org/api/files/download/id/1486611037/Numix-SX.tar.xz The older version can be found here: http://slackware.uk/sbosrcarch//by-md5/0/d/0d6cfe58cd7fdb996f7a3240ac39fb96/Numix-SX.tar.xz > desktop/wmcliphist > missing source, new source: > https://svwh.dl.sourceforge.net/project/slackbuildsdirectlinks/wmcliphist/wmcliphist-latest.tar.gz Source with matching md5sum here: http://slackware.uk/sbosrcarch//by-md5/8/1/81c9627c2955949669d2afa547415a10/wmcliphist-latest.tar.gz ...which is not to say the builds shouldn't be updated for the new sources you listed, but using sbosrcarch to get the old sources lets you just go ahead and build the package now instead of waiting for an update. From hostmaster at slackonly.com Wed Feb 22 22:25:38 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Wed, 22 Feb 2017 14:25:38 -0800 Subject: [Slackbuilds-users] pdfsam In-Reply-To: References: Message-ID: On 02/22/2017 02:19 PM, B Watson wrote: > On 2/22/17, Panagiotis Nikolaou wrote: >> pdfsam needs also as a dependency jdk: >> >> Error: JAVA_HOME is not defined correctly. >> We cannot execute /usr/lib64/java/bin/java > That's a consequence of apache-ant recently losing its hard dependency > on jdk. Stuff that depends on apache-ant used to not have to list jdk, > because apache-ant depended on jdk... which was incorrect (apache-ant > can work with slackware's gcc-java, or openjdk). > > Other builds which might (or might not) be affected by this: > > academic/link-grammar > development/Arduino > development/eclim > development/rstudio-desktop > libraries/ant-contrib > libraries/xalan > libraries/xerces > multimedia/JSampler > office/LibreOffice > office/fop > office/ganttproject > system/bootchart > system/commons-daemon > > Maintainers of these might want to have a look... > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Yes you have right! More SlackBuilds are affected from that change. From edps.mundognu at gmail.com Thu Feb 23 00:39:04 2017 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 22 Feb 2017 21:39:04 -0300 Subject: [Slackbuilds-users] sources Message-ID: About desktop/numix-sx-theme ... now i submitted a new update with this sources. Thanks, Edinaldo. From willysr at slackbuilds.org Thu Feb 23 01:18:08 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 23 Feb 2017 08:18:08 +0700 Subject: [Slackbuilds-users] pdfsam In-Reply-To: References: Message-ID: <32dff886-ae72-7a45-6c1d-c31568571cb6@slackbuilds.org> > pdfsam needs also as a dependency jdk: > > Error: JAVA_HOME is not defined correctly. > We cannot execute /usr/lib64/java/bin/java Fixed on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Feb 23 01:22:55 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 23 Feb 2017 08:22:55 +0700 Subject: [Slackbuilds-users] sources In-Reply-To: References: Message-ID: <1bf48e7a-9e56-30f6-bd24-ad1a43a80c07@slackbuilds.org> > Some sources fixes: > > academic/edsim51di > md5sum is c0b5d0a37ed468db17fdf909357581a6 instead of > 3458e49bda689445737041c0e69c3a8c > > desktop/numix-sx-theme > upstream has update the source to 20170209: > https://dl.opendesktop.org/api/files/download/id/1486611037/Numix-SX.tar.xz > > desktop/wmcliphist > missing source, new source: > https://svwh.dl.sourceforge.net/project/slackbuildsdirectlinks/wmcliphist/wmcliphist-latest.tar.gz All fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Feb 23 02:16:43 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 23 Feb 2017 09:16:43 +0700 Subject: [Slackbuilds-users] pdfsam In-Reply-To: References: Message-ID: <5a52f38f-ec8d-723a-1cde-79ee4ce1ff51@slackbuilds.org> > Other builds which might (or might not) be affected by this: here's some update academic/link-grammar (not yet tested) development/Arduino (not yet tested) development/eclim (jdk is second level dep) development/rstudio-desktop (not yet tested) libraries/ant-contrib (not yet tested) libraries/xalan (updated) libraries/xerces (updated) multimedia/JSampler (jdk is second level dep) office/LibreOffice (not yet tested) office/fop (jdk is second level dep) office/ganttproject (updated) system/bootchart (updated) system/commons-daemon (jdk already listed) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From hba.nihilismus at gmail.com Thu Feb 23 02:53:15 2017 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Wed, 22 Feb 2017 20:53:15 -0600 Subject: [Slackbuilds-users] sources In-Reply-To: <1bf48e7a-9e56-30f6-bd24-ad1a43a80c07@slackbuilds.org> References: <1bf48e7a-9e56-30f6-bd24-ad1a43a80c07@slackbuilds.org> Message-ID: Related, current DOWNLOAD returns 404 for the next SlackBuilds: * desktop/faience-icon-theme: DOWNLOAD=" https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/faience-theme/faience-icon-theme_0.5.zip " * desktop/kfaenza-icon-theme: DOWNLOAD=" http://pkgs.fedoraproject.org/repo/pkgs/kfaenza-icon-theme/kfaenza-icon-theme-0.8.9.tar.gz/95e9f287da7a0fd76fb406d313eee77e/kfaenza-icon-theme-0.8.9.tar.gz " * desktop/polar-cursor-themes: DOWNLOAD=" https://dl.opendesktop.org/api/files/download/id/1460735356/27913-PolarCursorThemes.tar.bz2 " * desktop/ambiance-radiance-flat-colors-gtk-theme: DOWNLOAD=" https://drive.google.com/uc?export=download&id=0B7iDWdwgu9QATV96bTVUSktlXzQ" URL from AUR, but wget downloads "download&id=0B7iDWdwgu9QATV96bTVUSktlXzQ" as result. - Cheers On Wed, Feb 22, 2017 at 7:22 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Some sources fixes: > > > > academic/edsim51di > > md5sum is c0b5d0a37ed468db17fdf909357581a6 instead of > > 3458e49bda689445737041c0e69c3a8c > > > > desktop/numix-sx-theme > > upstream has update the source to 20170209: > > https://dl.opendesktop.org/api/files/download/id/ > 1486611037/Numix-SX.tar.xz > > > > desktop/wmcliphist > > missing source, new source: > > https://svwh.dl.sourceforge.net/project/slackbuildsdirectlinks/ > wmcliphist/wmcliphist-latest.tar.gz > > All fixed in my branch > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -- 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 Thu Feb 23 04:42:47 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 23 Feb 2017 11:42:47 +0700 Subject: [Slackbuilds-users] sources In-Reply-To: References: <1bf48e7a-9e56-30f6-bd24-ad1a43a80c07@slackbuilds.org> Message-ID: <62c520c7-5557-eaf3-8f0a-d405e21c29a6@slackbuilds.org> > Related, current DOWNLOAD returns 404 for the next SlackBuilds: > > * desktop/faience-icon-theme: > DOWNLOAD="https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/faience-theme/faience-icon-theme_0.5.zip" > > * desktop/kfaenza-icon-theme: > DOWNLOAD="http://pkgs.fedoraproject.org/repo/pkgs/kfaenza-icon-theme/kfaenza-icon-theme-0.8.9.tar.gz/95e9f287da7a0fd76fb406d313eee77e/kfaenza-icon-theme-0.8.9.tar.gz" > > * desktop/polar-cursor-themes: > DOWNLOAD="https://dl.opendesktop.org/api/files/download/id/1460735356/27913-PolarCursorThemes.tar.bz2" > > * desktop/ambiance-radiance-flat-colors-gtk-theme: > DOWNLOAD="https://drive.google.com/uc?export=download&id=0B7iDWdwgu9QATV96bTVUSktlXzQ" > URL from AUR, but wget downloads > "download&id=0B7iDWdwgu9QATV96bTVUSktlXzQ" as result. All fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Thu Feb 23 08:18:06 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 23 Feb 2017 03:18:06 -0500 Subject: [Slackbuilds-users] wmcliphist (was: sources) Message-ID: On 2/22/17, Panagiotis Nikolaou wrote: > desktop/wmcliphist Actually. This build hasn't been updated by its maintainer since 2010. Would anyone mind if I take it over & submit an update for the latest version? From jbernts at broadpark.no Thu Feb 23 13:52:16 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 23 Feb 2017 14:52:16 +0100 Subject: [Slackbuilds-users] Spamassassin Message-ID: <20170223135216.GA17468@jostein> Running install of spamassassin after processing queue gives this error: Checking optional features... inc_bundling_support....disabled requires: ! inc::latest is not installed ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the versions of the modules indicated above before proceeding with this installation Created MYMETA.yml and MYMETA.json Creating new 'Build' script for 'Module-Build' version '0.4220' Parser.c: loadable library and perl binaries are mismatched (got handshake key 0xdb00080, needed 0xdb80080) perl-Module-Build: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. (Y)es to continue, (N)o to abort, (R)etry the build?: Is this an error on my side? Jostein From jbernts at broadpark.no Thu Feb 23 14:37:09 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 23 Feb 2017 15:37:09 +0100 Subject: [Slackbuilds-users] Spamassassin In-Reply-To: <20170223135216.GA17468@jostein> References: <20170223135216.GA17468@jostein> Message-ID: <20170223143709.GB17468@jostein> On 23.02.17,14:52, Jostein Berntsen wrote: >Running install of spamassassin after processing queue gives this error: > >Checking optional features... >inc_bundling_support....disabled >requires: >! inc::latest is not installed > >ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the >versions >of the modules indicated above before proceeding with this >installation > >Created MYMETA.yml and MYMETA.json >Creating new 'Build' script for 'Module-Build' version '0.4220' >Parser.c: loadable library and perl binaries are mismatched (got >handshake key 0xdb00080, needed 0xdb80080) > >perl-Module-Build: >Would you like to continue processing the rest of the >queue or would you like to abort? If this failed >package is a dependency of another package in the queue >then it may not make sense to continue. > >(Y)es to continue, (N)o to abort, (R)etry the build?: > > >Is this an error on my side? > Came a bit further now, but now gets these errors: libwww-perl: GPG checks not supported for the SBo repository. Processing libwww-perl 6.13-1 Using original .info file Using original SlackBuild file No build options selected. spamassassin: GPG checks not supported for the SBo repository. Processing spamassassin 3.4.1-1 Using original .info file Using original SlackBuild file No build options selected. +++++++++++++++++++++++++++++++++++++++++++ Pre-check complete. Do you wish to proceed based on the search results above? Packages not found will be skipped during the process. Jostein From bch at shroggslodge.freeserve.co.uk Thu Feb 23 14:37:46 2017 From: bch at shroggslodge.freeserve.co.uk (bch at shroggslodge.freeserve.co.uk) Date: Thu, 23 Feb 2017 14:37:46 +0000 Subject: [Slackbuilds-users] raw-thumbnailer source Message-ID: Hello all http://raw-thumbnailer.googlecode.com/files/raw-thumbnailer-0.2.1.tar.gz - source link is showing response 404. A message on googlecode suggests it [googlecode] is being shutdown. In relation to this program, raw-thumbnailer, it is moved it GitHub https://github.com/erlendd/raw-thumbnailer I do not know what is the usual Git url to use to get the source. Just thought I'd pass this on; hopefully maintainer will notice (cc'd in). Thank you. Regards Habs -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Feb 23 20:06:27 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 24 Feb 2017 03:06:27 +0700 Subject: [Slackbuilds-users] raw-thumbnailer source In-Reply-To: References: Message-ID: > http://raw-thumbnailer.googlecode.com/files/raw-thumbnailer-0.2.1.tar.gz > - source link is showing response 404. > > A message on googlecode suggests it [googlecode] is being shutdown. In > relation to this program, raw-thumbnailer, it is moved it GitHub > > https://github.com/erlendd/raw-thumbnailer > > I do not know what is the usual Git url to use to get the source. > > Just thought I'd pass this on; hopefully maintainer will notice (cc'd in). Fixed Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Feb 23 20:07:54 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 24 Feb 2017 03:07:54 +0700 Subject: [Slackbuilds-users] Spamassassin In-Reply-To: <20170223135216.GA17468@jostein> References: <20170223135216.GA17468@jostein> Message-ID: <8ca3735d-ebb1-be4f-10ff-7c87697f0868@slackbuilds.org> > Running install of spamassassin after processing queue gives this error: > > Checking optional features... > inc_bundling_support....disabled > requires: > ! inc::latest is not installed > > ERRORS/WARNINGS FOUND IN PREREQUISITES. You may wish to install the > versions > of the modules indicated above before proceeding with this > installation > > Created MYMETA.yml and MYMETA.json > Creating new 'Build' script for 'Module-Build' version '0.4220' > Parser.c: loadable library and perl binaries are mismatched (got > handshake key 0xdb00080, needed 0xdb80080) > > perl-Module-Build: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > (Y)es to continue, (N)o to abort, (R)etry the build?: > > Is this an error on my side? Did you notice that SpamAssassin has LOTS of deps? this is what i got from sqg re2c pyzor perl-Net-Server perl-Net-Ident perl-PAR-Dist perl-Module-Build perl-net-ip perl-digest-sha1 perl-digest-hmac perl-net-dns perl-NetAddr-IP perl-Net-DNS-Resolver-Programmable perl-Mail-SPF perl-TimeDate perl-MailTools perl-Crypt-OpenSSL-Random perl-Crypt-OpenSSL-RSA perl-Mail-DKIM perl-Image-Info perl-Geography-Countries perl-IP-Country perl-Net-LibIDN Net-SSLeay perl-IO-Socket-SSL perl-Socket6 perl-IO-Socket-INET6 perl-Encode-Detect perl-Crypt-OpenSSL-Bignum perl-www-robotrules perl-net-http perl-IO-HTML perl-lwp-mediatypes perl-http-date perl-html-tagset perl-html-parser perl-encode-locale perl-http-message perl-http-negotiate perl-http-daemon perl-http-cookies perl-file-listing libwww-perl spamassassin -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Feb 23 20:20:39 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 24 Feb 2017 03:20:39 +0700 Subject: [Slackbuilds-users] wmcliphist (was: sources) In-Reply-To: References: Message-ID: <9fd7d58e-9f20-0c94-c976-192e50e5367c@slackbuilds.org> > On 2/22/17, Panagiotis Nikolaou wrote: >> desktop/wmcliphist > > Actually. This build hasn't been updated by its maintainer since > 2010. Would anyone mind if I take it over & submit an update for the > latest version? Sure let me know if you do, since i have made commit on it to change the download URL -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Thu Feb 23 20:46:21 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 23 Feb 2017 15:46:21 -0500 Subject: [Slackbuilds-users] wmcliphist (was: sources) In-Reply-To: <9fd7d58e-9f20-0c94-c976-192e50e5367c@slackbuilds.org> References: <9fd7d58e-9f20-0c94-c976-192e50e5367c@slackbuilds.org> Message-ID: On 2/23/17, Willy Sudiarto Raharjo wrote: > let me know if you do, since i have made commit on it to change the > download URL OK, pushed. The download URL is different for the new version, you probably just want to remove your commit entirely. From duncan_roe at acslink.net.au Fri Feb 24 11:32:41 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Fri, 24 Feb 2017 22:32:41 +1100 Subject: [Slackbuilds-users] spice is not picking up lz4 support Message-ID: <20170224113241.GA792@dimstar.local.net> Hi Matteo, This looks to be an upstream bug. I built and installed the latest lz4 (1.7.5), but spice does not build with LZ4 support. Looking at config.log, I think I can see the problem: $PKG_CONFIG --exists --print-errors "liblz4 >= 129" What has happened is: lz4 used to have plain numeric revs. The last of these was 131, released on Jun 29, 2015. After that, lz4 changed to x.y.z revision format, starting with 1.7.3 released on Nov 17, 2016. The proper fix is to spice-common/m4/spice-deps.m4:188, which should be expanded to accept either >= 129 or >= 1.7.3. But tomorrow I will try the effect of patching configure (it's getting late now). Cheers ... Duncan. From matteo.bernardini at gmail.com Fri Feb 24 13:19:25 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 24 Feb 2017 14:19:25 +0100 Subject: [Slackbuilds-users] spice is not picking up lz4 support In-Reply-To: <20170224113241.GA792@dimstar.local.net> References: <20170224113241.GA792@dimstar.local.net> Message-ID: 2017-02-24 12:32 GMT+01:00 Duncan Roe : > Hi Matteo, > > This looks to be an upstream bug. > > I built and installed the latest lz4 (1.7.5), but spice does not build with LZ4 > support. > > Looking at config.log, I think I can see the problem: > > $PKG_CONFIG --exists --print-errors "liblz4 >= 129" > > What has happened is: lz4 used to have plain numeric revs. The last of these was > 131, released on Jun 29, 2015. After that, lz4 changed to x.y.z revision format, > starting with 1.7.3 released on Nov 17, 2016. > > The proper fix is to spice-common/m4/spice-deps.m4:188, which should be expanded > to accept either >= 129 or >= 1.7.3. yes, it's definitely an upstream bug: a quick fix should be to modify the SlackBuild like this --- ./spice.SlackBuild.orig 2017-02-23 11:12:28.218760310 +0100 +++ ./spice.SlackBuild 2017-02-24 14:14:43.292547670 +0100 @@ -78,6 +78,9 @@ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; +sed -i "s|129|1.7.3|" spice-common/m4/spice-deps.m4 +autoreconf -fi + CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ Matteo From matteo.bernardini at gmail.com Fri Feb 24 13:22:26 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 24 Feb 2017 14:22:26 +0100 Subject: [Slackbuilds-users] spice is not picking up lz4 support In-Reply-To: References: <20170224113241.GA792@dimstar.local.net> Message-ID: 2017-02-24 14:19 GMT+01:00 Matteo Bernardini : > 2017-02-24 12:32 GMT+01:00 Duncan Roe : >> Hi Matteo, >> >> This looks to be an upstream bug. >> >> I built and installed the latest lz4 (1.7.5), but spice does not build with LZ4 >> support. >> >> Looking at config.log, I think I can see the problem: >> >> $PKG_CONFIG --exists --print-errors "liblz4 >= 129" >> >> What has happened is: lz4 used to have plain numeric revs. The last of these was >> 131, released on Jun 29, 2015. After that, lz4 changed to x.y.z revision format, >> starting with 1.7.3 released on Nov 17, 2016. >> >> The proper fix is to spice-common/m4/spice-deps.m4:188, which should be expanded >> to accept either >= 129 or >= 1.7.3. > > yes, it's definitely an upstream bug: a quick fix should be to modify > the SlackBuild like this > > --- ./spice.SlackBuild.orig 2017-02-23 11:12:28.218760310 +0100 > +++ ./spice.SlackBuild 2017-02-24 14:14:43.292547670 +0100 > @@ -78,6 +78,9 @@ > \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o > -perm 400 \) \ > -exec chmod 644 {} \; > > +sed -i "s|129|1.7.3|" spice-common/m4/spice-deps.m4 > +autoreconf -fi > + > CFLAGS="$SLKCFLAGS" \ > CXXFLAGS="$SLKCFLAGS" \ > ./configure \ but it seems it's already fixed in the newer spice-common (included in spice), so it will probably will go in the next spice release https://cgit.freedesktop.org/spice/spice-common/commit/?id=48da2c6654f37fcf02711aa86a08d6404dd6d215 Matteo From duncan_roe at acslink.net.au Fri Feb 24 23:02:07 2017 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Sat, 25 Feb 2017 10:02:07 +1100 Subject: [Slackbuilds-users] spice is not picking up lz4 support In-Reply-To: References: <20170224113241.GA792@dimstar.local.net> Message-ID: <20170224230207.GA3621@dimstar.local.net> On Fri, Feb 24, 2017 at 02:19:25PM +0100, Matteo Bernardini wrote: > 2017-02-24 12:32 GMT+01:00 Duncan Roe : > > Hi Matteo, > > > > This looks to be an upstream bug. > > > > I built and installed the latest lz4 (1.7.5), but spice does not build with LZ4 > > support. > > > > Looking at config.log, I think I can see the problem: > > > > $PKG_CONFIG --exists --print-errors "liblz4 >= 129" > > > > What has happened is: lz4 used to have plain numeric revs. The last of these was > > 131, released on Jun 29, 2015. After that, lz4 changed to x.y.z revision format, > > starting with 1.7.3 released on Nov 17, 2016. > > > > The proper fix is to spice-common/m4/spice-deps.m4:188, which should be expanded > > to accept either >= 129 or >= 1.7.3. > > yes, it's definitely an upstream bug: a quick fix should be to modify > the SlackBuild like this > > --- ./spice.SlackBuild.orig 2017-02-23 11:12:28.218760310 +0100 > +++ ./spice.SlackBuild 2017-02-24 14:14:43.292547670 +0100 > @@ -78,6 +78,9 @@ > \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o > -perm 400 \) \ > -exec chmod 644 {} \; > > +sed -i "s|129|1.7.3|" spice-common/m4/spice-deps.m4 > +autoreconf -fi > + > CFLAGS="$SLKCFLAGS" \ > CXXFLAGS="$SLKCFLAGS" \ > ./configure \ > > Matteo > _______________________________________________ Hi Matteo, That worked, thanks. But first I had to rejoin the split line starting " \( -perm 666 -o -perm ". Cheers ... Duncan. From willysr at slackbuilds.org Sat Feb 25 00:46:50 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 25 Feb 2017 07:46:50 +0700 Subject: [Slackbuilds-users] Updates - 20170225.1 Message-ID: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Back to our normal weekend updates There's a bunch of mono-related updates from Andre along with other updates. We also found that terminix is still failing to build on x86 architecture. Patches are welcome to fix this issue. Another (potential) issue is about the removal of jdk as apache-ant requirement. This (may) leaves some scripts failing to build as well. A feedback on this scripts whether they are working without jdk package are generously accepted: academic/link-grammar development/Arduino development/rstudio-desktop libraries/ant-contrib office/LibreOffice here's the update for the weekend: Sat Feb 25 00:31:42 UTC 2017 academic/edsim51di: Update MD5SUM. audio/snd: Updated for version 17.2. desktop/ambiance-radiance-flat-colors-gtk-themes: Update DOWNLOAD. desktop/faience-icon-theme: Update DOWNLOAD url. desktop/kfaenza-icon-theme: Update DOWNLOAD url. desktop/numix-sx-theme: Updated for version 20170209. desktop/obmenu-generator: Updated for version 0.69. desktop/pdfsam: Updated for version 2.2.4e, new deps. desktop/polar-cursor-themes: Update DOWNLOAD url. desktop/wmcliphist: Updated for version 2.1, new maintainer. desktop/wmmon: Fix doinst.sh. development/git-lfs: Updated for version 1.5.6. development/mono-addins: Updated for version 1.3. development/mono: Updated for version 4.8.0.495. development/monodevelop: Updated for version 6.2.0.1821. development/nodejs: Updated for version 6.10.0. development/nuget: Updated for version 3.5.0. development/poedit: Updated for version 1.8.12. development/scite: Updated for version 3.7.3. development/svn-all-fast-export: Added (SVN to git converter). games/mame: Updated for version 0.183. graphics/raw-thumbnailer: Update DOWNLOAD url. libraries/botocore: Updated for version 1.5.17. libraries/dlib: Updated for version 19.3. libraries/libfilezilla: Updated for version 0.9.1. libraries/libgraphqlparser: Added (A GraphQL query parser). libraries/libxnvctrl: Updated for version 375.39. libraries/poco: Updated for version 1.7.8. libraries/sqlpp11-connector-mysql: Updated for version 0.21. libraries/xalan: Update DEP. libraries/xerces: Update DEP. misc/mosquitto: Updated for version 1.4.11 misc/subsurface: Updated for version 4.6.2 multimedia/TeamSpeak3: Updated for version 3.1.1.1 + new maintainer. multimedia/gpodder: Update DEP. multimedia/opera-developer-ffmpeg-codecs: Updated for version 57.0. multimedia/opera-ffmpeg-codecs: Updated for version 56.0.2924.87. multimedia/x265: Updated for version 2.3. network/PaleMoon: Updated for version 27.1.1. network/awscli: Updated for version 1.11.54. network/bozohttpd: Updated for version 20170201. network/emailrelay: Added (SMTP proxy and store-and-forward MTA). network/filezilla: Updated for version 3.24.1. network/flexget: Updated for version 2.10.6. network/glusterfs: Updated for version 3.9.1. network/opera-developer: Updated for version 44.0.2505.0. network/opera: Updated for version 43.0.2442.991. network/putty: Updated for version 0.68. network/shorewall-core: Updated for version 5.0.15.3. network/shorewall6: Updated for version 5.0.15.3. network/shorewall: Updated for version 5.0.15.3. network/spice: Fix broken lz4 autodetection. network/suricata: Updated for version 3.2.1. network/telegram: Updated for version 1.0.14. network/tixati: Updated for version 2.53_1. network/uwsgi: Updated for version 2.0.14. network/verm: Added (An immutable, WORM filestore). network/youtube-dl: Updated for version 2017.02.24. office/ganttproject: Update DEP. office/sc-im: Updated for version 0.5.0. perl/perl-IO-Socket-SSL: Updated for version 2.047. python/Scrapy: Updated for version 1.3.2. ruby/rubygem-bundler: Updated for version 1.14.5. system/bootchart: Update DEP. system/kafka: Updated for version 0.10.2.0. system/lynix: Updated for version 2.4.2. system/slpkg: Updated for version 3.2.6. system/yash: Updated for version 2.44. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Sat Feb 25 01:22:24 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 25 Feb 2017 11:22:24 +1000 Subject: [Slackbuilds-users] Updates - 20170225.1 In-Reply-To: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: On 25/02/17 10:46, Willy Sudiarto Raharjo wrote: > Back to our normal weekend updates > > Another (potential) issue is about the removal of jdk as apache-ant > requirement. This (may) leaves some scripts failing to build as well. A > feedback on this scripts whether they are working without jdk package > are generously accepted: > office/LibreOffice > Over time, I've had many suggestions and reminders that LibreOffice will build successfully without the jdk package. I prefer a build with as full functionality as is made possible upstream, so I prefer that it remain as a requirement. Java haters are welcome to add --without-java or --with-java=no to their local versions - which reminds me I could add a JAVA=no option to the SlackBuild at the next version update. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From hostmaster at slackonly.com Sat Feb 25 03:30:45 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Fri, 24 Feb 2017 19:30:45 -0800 Subject: [Slackbuilds-users] Updates - 20170225.1 In-Reply-To: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: > Another (potential) issue is about the removal of jdk as apache-ant > requirement. This (may) leaves some scripts failing to build as well. A > feedback on this scripts whether they are working without jdk package > are generously accepted: > academic/link-grammar > development/Arduino > development/rstudio-desktop > libraries/ant-contrib academic/link-grammar development/Arduino development/rstudio-desktop All failed with: Error: JAVA_HOME is not defined correctly. We cannot execute java libraries/ant-contrib: working without jdk From rworkman at slackbuilds.org Sat Feb 25 03:55:16 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 24 Feb 2017 21:55:16 -0600 Subject: [Slackbuilds-users] spice is not picking up lz4 support In-Reply-To: References: <20170224113241.GA792@dimstar.local.net> Message-ID: <20170224215516.0075528b@home.rlworkman.net> On Fri, 24 Feb 2017 14:22:26 +0100 Matteo Bernardini wrote: > 2017-02-24 14:19 GMT+01:00 Matteo Bernardini > : > > 2017-02-24 12:32 GMT+01:00 Duncan Roe : > >> Hi Matteo, > >> > >> This looks to be an upstream bug. > >> > >> I built and installed the latest lz4 (1.7.5), but spice does not > >> build with LZ4 support. > >> > >> Looking at config.log, I think I can see the problem: > >> > >> $PKG_CONFIG --exists --print-errors "liblz4 >= 129" > >> > >> What has happened is: lz4 used to have plain numeric revs. The > >> last of these was 131, released on Jun 29, 2015. After that, lz4 > >> changed to x.y.z revision format, starting with 1.7.3 released on > >> Nov 17, 2016. > >> > >> The proper fix is to spice-common/m4/spice-deps.m4:188, which > >> should be expanded to accept either >= 129 or >= 1.7.3. > > > > yes, it's definitely an upstream bug: a quick fix should be to > > modify the SlackBuild like this > > > > --- ./spice.SlackBuild.orig 2017-02-23 11:12:28.218760310 +0100 > > +++ ./spice.SlackBuild 2017-02-24 14:14:43.292547670 +0100 > > @@ -78,6 +78,9 @@ > > \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 > > -o -perm 400 \) \ > > -exec chmod 644 {} \; > > > > +sed -i "s|129|1.7.3|" spice-common/m4/spice-deps.m4 > > +autoreconf -fi > > + > > CFLAGS="$SLKCFLAGS" \ > > CXXFLAGS="$SLKCFLAGS" \ > > ./configure \ > > but it seems it's already fixed in the newer spice-common (included in > spice), so it will probably will go in the next spice release > > https://cgit.freedesktop.org/spice/spice-common/commit/?id=48da2c6654f37fcf02711aa86a08d6404dd6d215 Here's the patch (slightly modified to fix the dir); apply with: patch -p1 < $CWD/fix-lz4-detection.diff See attached. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: fix-lz4-detection.diff Type: text/x-patch Size: 1951 bytes Desc: not available URL: -------------- 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 Feb 25 04:09:15 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 25 Feb 2017 11:09:15 +0700 Subject: [Slackbuilds-users] Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: <5b6d1cc0-50de-eadf-36aa-0532e2f55c9c@slackbuilds.org> > academic/link-grammar > development/Arduino > development/rstudio-desktop > > All failed with: > Error: JAVA_HOME is not defined correctly. > We cannot execute java > > libraries/ant-contrib: > working without jdk Applied to my branch thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Sat Feb 25 08:12:28 2017 From: yalhcru at gmail.com (B Watson) Date: Sat, 25 Feb 2017 03:12:28 -0500 Subject: [Slackbuilds-users] Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: On 2/24/17, Christoph Willing wrote: > Over time, I've had many suggestions and reminders that LibreOffice will > build successfully without the jdk package. I prefer a build with as > full functionality as is made possible upstream, so I prefer that it > remain as a requirement. Java haters are welcome to add --without-java > or --with-java=no to their local versions - which reminds me I could add > a JAVA=no option to the SlackBuild at the next version update. Will it work with openjdk rather than Oracle's jdk? That's probably a question that should be asked about any of the builds mentioned in this thread. If the answer is "it requires a JDK, and will work with either jdk or openjdk", what's the best way to handle that? List jdk in REQUIRES, and say "you can use openjdk instead of jdk" in the README? Or, list neither in REQUIRES, and in the README say "you need one of either jdk or openjdk"? Or, maybe openjdk should be listed in REQUIRES, as it's easier to deal with (doesn't require jumping through hoops to download like jdk does)? In which case the README would say "you can use jdk instead of openjdk"? From rshepard at appl-ecosys.com Sat Feb 25 15:31:57 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 25 Feb 2017 07:31:57 -0800 (PST) Subject: [Slackbuilds-users] atlas3.10.3 build fails due to throttling Message-ID: System is running Slackware-14.2/x86_64. After installing lapack-3.6.1 (a.k.a. lapack-atlas) I tried to build atlas-3.10.3 but it quit after 4 seconds because of throttling. I need guidance on resolving this issue so I can install NumPy and other applications to run a hydrologic model. Regards, Rich From dn2010 at gmail.com Sat Feb 25 17:13:24 2017 From: dn2010 at gmail.com (Daniil Bratashov) Date: Sat, 25 Feb 2017 21:13:24 +0400 Subject: [Slackbuilds-users] atlas3.10.3 build fails due to throttling In-Reply-To: References: Message-ID: citing slackbuild instructions: As with Slackware 14.2 you can run /etc/rc.d/rc.cpufreq as root with "performance" as command line argument. If you'll still have trottling issues (I had with Haswell), you can add --cripple-atlas-performance to ./configure arguments inside the slackbuild. On Sat, Feb 25, 2017 at 7:31 PM, Rich Shepard wrote: > System is running Slackware-14.2/x86_64. > > After installing lapack-3.6.1 (a.k.a. lapack-atlas) I tried to build > atlas-3.10.3 but it quit after 4 seconds because of throttling. > > I need guidance on resolving this issue so I can install NumPy and other > applications to run a hydrologic model. > > Regards, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Sat Feb 25 18:16:29 2017 From: yalhcru at gmail.com (B Watson) Date: Sat, 25 Feb 2017 13:16:29 -0500 Subject: [Slackbuilds-users] atlas3.10.3 build fails due to throttling In-Reply-To: References: Message-ID: On 2/25/17, Daniil Bratashov wrote: > citing slackbuild instructions: > As with Slackware 14.2 you can run /etc/rc.d/rc.cpufreq as root with > "performance" as command line > argument. > > If you'll still have trottling issues (I had with Haswell), you can > add --cripple-atlas-performance to ./configure arguments inside the > slackbuild. This is fresh in my mind, I just had to do this on my laptop yesterday. 'performance' still allows the CPU to be throttled, even though the comments in rc.cpufreq imply that it doesn't. I ended up using the cpufreq-set command in rc.local. It would really be nice if there were a simple option to cpufreq-set that means "disable throttling, run at max speed all the time", but there isn't one: you can do it, but you have to include the frequency on the command line. Also, the -r (all hardware-related CPUs) switch seems to be broken. So you have to repeat the command for each core. So my rc.local has: cpufreq-set -c 0 -r -f 1.60GHz cpufreq-set -c 1 -r -f 1.60GHz ...where the 1.60GHZ number came from running cpufreq-info and noting the maximum frequency. I've got 2 cores on the laptop, so there are 2 commands. If I had 4 cores, I'd add these: cpufreq-set -c 2 -r -f 1.60GHz cpufreq-set -c 3 -r -f 1.60GHz On my old laptop, this works fine and doesn't cause any problems. However I wouldn't trust this blindly, I'd watch the output of 'sensors' to make sure it's not causing overheating. The above relies on the userspace governor being available, it's built in (not a module) in both the huge and generic kernels. From rshepard at appl-ecosys.com Sat Feb 25 18:37:03 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 25 Feb 2017 10:37:03 -0800 (PST) Subject: [Slackbuilds-users] atlas3.10.3 build fails due to throttling In-Reply-To: References: Message-ID: On Sat, 25 Feb 2017, B Watson wrote: > This is fresh in my mind, I just had to do this on my laptop yesterday. Thanks to both of you for the answer. I missed seeing it on the SBo page. I don't recall having this issue when I installed/upgraded atlas on my 32-bit workstation. > 'performance' still allows the CPU to be throttled, even though the > comments in rc.cpufreq imply that it doesn't. I ended up using the > cpufreq-set command in rc.local. Huh. Perhaps I should try this on my Dell Latitude E5410 with 4 cores before moving to the next step. > It would really be nice if there were a simple option to cpufreq-set > that means "disable throttling, run at max speed all the time", but > there isn't one: you can do it, but you have to include the frequency > on the command line. > Also, the -r (all hardware-related CPUs) switch seems to be broken. So > you have to repeat the command for each core. So my rc.local has: > > cpufreq-set -c 0 -r -f 1.60GHz > cpufreq-set -c 1 -r -f 1.60GHz > The above relies on the userspace governor being available, it's built in > (not a module) in both the huge and generic kernels. Since I don't regularly use atlas (at least, not that I'm aware of using; I think GRASS is the only tool that wants in sometimes), can I block throttling to build and install atlas, then unblock it afterwards? Rich From rshepard at appl-ecosys.com Sat Feb 25 18:50:07 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 25 Feb 2017 10:50:07 -0800 (PST) Subject: [Slackbuilds-users] atlas3.10.3 build fails due to throttling [RESOLVED] In-Reply-To: References: Message-ID: Daniil/B.: Turns out that with OpenBLAS and LAPACK installed I don't need Atlas to build NumPy. This makes life easier for me. Thanks again, both of you, Rich From chris.willing at iinet.net.au Sat Feb 25 23:25:21 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 26 Feb 2017 09:25:21 +1000 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: On 25/02/17 18:12, B Watson wrote: > On 2/24/17, Christoph Willing wrote: >> Over time, I've had many suggestions and reminders that LibreOffice will >> build successfully without the jdk package. I prefer a build with as >> full functionality as is made possible upstream, so I prefer that it >> remain as a requirement. Java haters are welcome to add --without-java >> or --with-java=no to their local versions - which reminds me I could add >> a JAVA=no option to the SlackBuild at the next version update. > > Will it work with openjdk rather than Oracle's jdk? > > That's probably a question that should be asked about any of the builds > mentioned in this thread. > > If the answer is "it requires a JDK, and will work with either jdk or > openjdk", what's the best way to handle that? List jdk in REQUIRES, > and say "you can use openjdk instead of jdk" in the README? Or, list > neither in REQUIRES, and in the README say "you need one of either jdk > or openjdk"? > > Or, maybe openjdk should be listed in REQUIRES, as it's easier to deal > with (doesn't require jumping through hoops to download like jdk does)? > In which case the README would say "you can use jdk instead of openjdk"? I haven't tried openjdk for a long time - there were often problems running it with the java apps I was using at that time and the Oracle version always just worked. However that was some time ago and your comment about being 'easier to deal with' (in automated build systems, at least) is a good point. Therefore I tried building openjdk in a fresh 14.2 64bit VM and very soon had the following failure: compile: [javac] Compiling 2760 source files to /tmp/SBo/openjdk/icedtea-build/openjdk.build-boot/jaxws/build/classes [javac] Annotation processing got disabled, since it requires a 1.6 compliant JVM [javac] java.lang.NullPointerException [javac] at org.eclipse.jdt.internal.compiler.batch.CompilationUnit.getContents(CompilationUnit.java:77) [javac] at org.eclipse.jdt.internal.compiler.batch.Main$2.acceptResult(Main.java:2962) [javac] at org.eclipse.jdt.internal.compiler.Compiler.handleInternalException(Compiler.java:609) [javac] at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:527) [javac] at org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4099) [javac] at org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689) [javac] at org.eclipse.jdt.internal.compiler.batch.Main.main(Main.java:1400) [javac] BUILD FAILED /tmp/SBo/openjdk/icedtea-build/openjdk-boot/jaxws/build.xml:155: Compile failed; see the compiler error output for details. Total time: 1 second Makefile:150: recipe for target 'all' failed This morning I've just started a build in a 32bit VM which is not complete yet but seems to be progressing just fine. Is there a known problem with openjdk on 64bit? Does anyone recognize the failure above and/or know a possible solution? chris From atelszewski at gmail.com Sat Feb 25 23:45:44 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 26 Feb 2017 00:45:44 +0100 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: <85b8812e-e39b-3929-3225-7196ede12b87@gmail.com> On 26/02/17 00:25, Christoph Willing wrote: > Is there a known > problem with openjdk on 64bit? Does anyone recognize the failure above > and/or know a possible solution? I've been building openjdk (version 7) on 64 bits just fine. Please take a look at the README, as it has many pointers on what might go wrong. -- Best regards, Andrzej Telszewski From chris.willing at iinet.net.au Sat Feb 25 23:53:02 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 26 Feb 2017 09:53:02 +1000 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> On 26/02/17 09:25, Christoph Willing wrote: > On 25/02/17 18:12, B Watson wrote: >> On 2/24/17, Christoph Willing wrote: >>> Over time, I've had many suggestions and reminders that LibreOffice will >>> build successfully without the jdk package. I prefer a build with as >>> full functionality as is made possible upstream, so I prefer that it >>> remain as a requirement. Java haters are welcome to add --without-java >>> or --with-java=no to their local versions - which reminds me I could add >>> a JAVA=no option to the SlackBuild at the next version update. >> >> Will it work with openjdk rather than Oracle's jdk? >> >> That's probably a question that should be asked about any of the builds >> mentioned in this thread. >> >> If the answer is "it requires a JDK, and will work with either jdk or >> openjdk", what's the best way to handle that? List jdk in REQUIRES, >> and say "you can use openjdk instead of jdk" in the README? Or, list >> neither in REQUIRES, and in the README say "you need one of either jdk >> or openjdk"? >> >> Or, maybe openjdk should be listed in REQUIRES, as it's easier to deal >> with (doesn't require jumping through hoops to download like jdk does)? >> In which case the README would say "you can use jdk instead of openjdk"? > > I haven't tried openjdk for a long time - there were often problems > running it with the java apps I was using at that time and the Oracle > version always just worked. However that was some time ago and your > comment about being 'easier to deal with' (in automated build systems, > at least) is a good point. > > Therefore I tried building openjdk in a fresh 14.2 64bit VM and very > soon had the following failure: > > compile: > [javac] Compiling 2760 source files to > /tmp/SBo/openjdk/icedtea-build/openjdk.build-boot/jaxws/build/classes > [javac] Annotation processing got disabled, since it requires a 1.6 > compliant JVM > [javac] java.lang.NullPointerException > [javac] at > org.eclipse.jdt.internal.compiler.batch.CompilationUnit.getContents(CompilationUnit.java:77) > [javac] at > org.eclipse.jdt.internal.compiler.batch.Main$2.acceptResult(Main.java:2962) > [javac] at > org.eclipse.jdt.internal.compiler.Compiler.handleInternalException(Compiler.java:609) > [javac] at > org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:527) > [javac] at > org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4099) > [javac] at > org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689) > [javac] at > org.eclipse.jdt.internal.compiler.batch.Main.main(Main.java:1400) > [javac] > > BUILD FAILED > /tmp/SBo/openjdk/icedtea-build/openjdk-boot/jaxws/build.xml:155: Compile > failed; see the compiler error output for details. > > Total time: 1 second > Makefile:150: recipe for target 'all' failed > > > > This morning I've just started a build in a 32bit VM which is not > complete yet but seems to be progressing just fine. Is there a known > problem with openjdk on 64bit? Does anyone recognize the failure above > and/or know a possible solution? > Well the 32bit version finished building so I was encouraged to try the 64bit build again. This time it has passed the previous point of failure and seems also to be progressing just fine. In the meantime, I see that the 32bit build produced openjdk-7u111b01-i486-1_SBo.txz which seems pretty old. Looking around I found there was also a SlackBuild for openjdk8 (and even older openjdk6). Wanting to try the openjdk8, I found it has a requirement for openjdk (not just apache-ant, as is the case for openjdk & openjdk6). Is that just a typo (should require apache-ant, not openjdk)? chris From rshepard at appl-ecosys.com Sat Feb 25 23:57:51 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 25 Feb 2017 15:57:51 -0800 (PST) Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: <85b8812e-e39b-3929-3225-7196ede12b87@gmail.com> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <85b8812e-e39b-3929-3225-7196ede12b87@gmail.com> Message-ID: On Sun, 26 Feb 2017, Andrzej Telszewski wrote: > I've been building openjdk (version 7) on 64 bits just fine. Please take a > look at the README, as it has many pointers on what might go wrong. I built and use openjdk-8 on both 32- and 64-bit machines. JabRef (and Jgnash before I switched to GnuCash) work just fine with openjdk. Rich From chris.willing at iinet.net.au Sun Feb 26 04:20:27 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 26 Feb 2017 14:20:27 +1000 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> Message-ID: <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> On 26/02/17 09:53, Christoph Willing wrote: > On 26/02/17 09:25, Christoph Willing wrote: >> On 25/02/17 18:12, B Watson wrote: >>> On 2/24/17, Christoph Willing wrote: >>>> Over time, I've had many suggestions and reminders that LibreOffice will >>>> build successfully without the jdk package. I prefer a build with as >>>> full functionality as is made possible upstream, so I prefer that it >>>> remain as a requirement. Java haters are welcome to add --without-java >>>> or --with-java=no to their local versions - which reminds me I could add >>>> a JAVA=no option to the SlackBuild at the next version update. >>> >>> Will it work with openjdk rather than Oracle's jdk? >>> >>> That's probably a question that should be asked about any of the builds >>> mentioned in this thread. >>> >>> If the answer is "it requires a JDK, and will work with either jdk or >>> openjdk", what's the best way to handle that? List jdk in REQUIRES, >>> and say "you can use openjdk instead of jdk" in the README? Or, list >>> neither in REQUIRES, and in the README say "you need one of either jdk >>> or openjdk"? >>> >>> Or, maybe openjdk should be listed in REQUIRES, as it's easier to deal >>> with (doesn't require jumping through hoops to download like jdk does)? >>> In which case the README would say "you can use jdk instead of openjdk"? >> >> I haven't tried openjdk for a long time - there were often problems >> running it with the java apps I was using at that time and the Oracle >> version always just worked. However that was some time ago and your >> comment about being 'easier to deal with' (in automated build systems, >> at least) is a good point. >> >> Therefore I tried building openjdk in a fresh 14.2 64bit VM and very >> soon had the following failure: >> >> compile: >> [javac] Compiling 2760 source files to >> /tmp/SBo/openjdk/icedtea-build/openjdk.build-boot/jaxws/build/classes >> [javac] Annotation processing got disabled, since it requires a 1.6 >> compliant JVM >> [javac] java.lang.NullPointerException >> [javac] at >> org.eclipse.jdt.internal.compiler.batch.CompilationUnit.getContents(CompilationUnit.java:77) >> [javac] at >> org.eclipse.jdt.internal.compiler.batch.Main$2.acceptResult(Main.java:2962) >> [javac] at >> org.eclipse.jdt.internal.compiler.Compiler.handleInternalException(Compiler.java:609) >> [javac] at >> org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:527) >> [javac] at >> org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4099) >> [javac] at >> org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689) >> [javac] at >> org.eclipse.jdt.internal.compiler.batch.Main.main(Main.java:1400) >> [javac] >> >> BUILD FAILED >> /tmp/SBo/openjdk/icedtea-build/openjdk-boot/jaxws/build.xml:155: Compile >> failed; see the compiler error output for details. >> >> Total time: 1 second >> Makefile:150: recipe for target 'all' failed >> >> >> >> This morning I've just started a build in a 32bit VM which is not >> complete yet but seems to be progressing just fine. Is there a known >> problem with openjdk on 64bit? Does anyone recognize the failure above >> and/or know a possible solution? >> > Well the 32bit version finished building so I was encouraged to try the > 64bit build again. This time it has passed the previous point of failure > and seems also to be progressing just fine. > > In the meantime, I see that the 32bit build produced > openjdk-7u111b01-i486-1_SBo.txz which seems pretty old. Looking around I > found there was also a SlackBuild for openjdk8 (and even older > openjdk6). Wanting to try the openjdk8, I found it has a requirement for > openjdk (not just apache-ant, as is the case for openjdk & openjdk6). Is > that just a typo (should require apache-ant, not openjdk)? > Answering my own question; no it's not a typo. To test, I changed the openjdk8's REQUIRES field from openjdk to apache-ant but the build failed because JAVA_HOME hadn't been set up i.e. no jdk or openjdk installed. When I reverted the REQUIRES field to openjdk, the build of openjdk8 succeeded. Furthermore, openjdk's own README-builds.html states that before attempting to build: "Install a Bootstrap JDK. All OpenJDK builds require access to a previously released JDK called the bootstrap JDK or boot JDK. The general rule is that the bootstrap JDK must be an instance of the previous major release of the JDK." The question for me now is whether changing LibreOffice's jdk requirement to openjdk really makes building LibreOffice much more straightforward. While it may build with openjdk, I'd personally be uncomfortable with using an out of date version. However to use openjdk8 as the requirement means that a builder of LibreOffice needs to build openjdk first, then openjdk8. Apart from the complication of downloading the Oracle jdk, building it (repackaging it) seems simpler, not to mention much faster. Any other views on using openjdk* instead of jdk as requirement for LibreOffice? chris From firebird209 at gmail.com Sun Feb 26 07:47:17 2017 From: firebird209 at gmail.com (firebird209) Date: Sun, 26 Feb 2017 01:47:17 -0600 Subject: [Slackbuilds-users] Weechat maintainer wanted Message-ID: <3a8a1942-3c49-3941-ee73-f83705a4eaa4@gmail.com> Anyone out there who'd like to take over maintaining weechat? I maintained it for a while now, and actually let a couple versions slip past so it needs updating to current release. I've just no interest in maintaining it anymore so wanting to pass the torch to someone else. Thank you. From yalhcru at gmail.com Sun Feb 26 08:13:46 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 26 Feb 2017 03:13:46 -0500 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> Message-ID: On 2/25/17, Christoph Willing wrote: > Apart from the complication of downloading the Oracle jdk, building it > (repackaging it) seems simpler, not to mention much faster. > > Any other views on using openjdk* instead of jdk as requirement for > LibreOffice? I haven't really got a horse in this race (have never used LibreOffice), but I'm full of ideas. Which you can ignore, if you think they're bad ideas (I won't be offended). What's needed is a way to say "either-or" in REQUIRES. Which isn't likely to happen (nobody wants the added complexity, for good & valid reasons). So instead... You could leave both jdk and openjdk out of REQUIRES, and in the README say "For a full-featured LibreOffice build, you will require either jdk or openjdk8". For bonus points, have the script auto-detect which is installed and use that. If neither is installed, act as though JAVA=no was set. Is it even possible to install both jdk and openjdk8 without them stepping on each other? If so, the user should be able to set JAVA=jdk or JAVA=openjdk8, and if he doesn't, and both are installed, I guess give precedence to jdk. For more bonus points, make the slack-desc say: This package was built with %JAVA%. ...and instead of "cat $CWD/slack-desc > $PKG/install/slack-desc", do this: sed "s,%JAVA%,$JAVA," $CWD/slack-desc > $PKG/install/slack-desc Where JAVA is set to one of "jdk", "openjdk8", or "no Java support". I do this in quite a few of my own builds, if only to help myself keep track of what options a package was built with. Whether this is actually a good idea depends on exactly what functionality is missing from LibreOffice if it's built without Java. I have no idea, but not having one or the other in REQUIRES is going to lead to a lot of non-README-reading users building without it. Another facet: some people will prefer openjdk because of licensing. People who care about the "Libre" in the LibreOffice name might care about this. From slackbuilds at jaxartes.net Sun Feb 26 09:10:07 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 26 Feb 2017 01:10:07 -0800 Subject: [Slackbuilds-users] Weechat maintainer wanted In-Reply-To: <3a8a1942-3c49-3941-ee73-f83705a4eaa4@gmail.com> References: <3a8a1942-3c49-3941-ee73-f83705a4eaa4@gmail.com> Message-ID: <5787067.1AXnrqdngX@wintermute> On Saturday, February 25, 2017 11:47:17 PM PST firebird209 wrote: > Anyone out there who'd like to take over maintaining weechat? I > maintained it for a while now, and actually let a couple versions slip > past so it needs updating to current release. I've just no interest in > maintaining it anymore so wanting to pass the torch to someone else. > > Thank you. Sure, I can take it. From firebird209 at gmail.com Sun Feb 26 09:38:42 2017 From: firebird209 at gmail.com (firebird209) Date: Sun, 26 Feb 2017 03:38:42 -0600 Subject: [Slackbuilds-users] Weechat maintainer wanted In-Reply-To: <5787067.1AXnrqdngX@wintermute> References: <3a8a1942-3c49-3941-ee73-f83705a4eaa4@gmail.com> <5787067.1AXnrqdngX@wintermute> Message-ID: Great, if you want to take it, I shall pass the torch on to you then :) Thank you. On 2/26/2017 3:10 AM, Benjamin Trigona-Harany wrote: > On Saturday, February 25, 2017 11:47:17 PM PST firebird209 wrote: >> Anyone out there who'd like to take over maintaining weechat? I >> maintained it for a while now, and actually let a couple versions slip >> past so it needs updating to current release. I've just no interest in >> maintaining it anymore so wanting to pass the torch to someone else. >> >> Thank you. > Sure, I can take it. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From chris.willing at iinet.net.au Sun Feb 26 12:53:20 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 26 Feb 2017 22:53:20 +1000 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> Message-ID: On 26/02/17 18:13, B Watson wrote: > On 2/25/17, Christoph Willing wrote: > >> Apart from the complication of downloading the Oracle jdk, building it >> (repackaging it) seems simpler, not to mention much faster. >> >> Any other views on using openjdk* instead of jdk as requirement for >> LibreOffice? > > I haven't really got a horse in this race (have never used LibreOffice), > but I'm full of ideas. Which you can ignore, if you think they're bad > ideas (I won't be offended). > > What's needed is a way to say "either-or" in REQUIRES. Which isn't > likely to happen (nobody wants the added complexity, for good & valid > reasons). So instead... > > You could leave both jdk and openjdk out of REQUIRES, and in the README > say "For a full-featured LibreOffice build, you will require either jdk > or openjdk8". For bonus points, have the script auto-detect which is > installed and use that. If neither is installed, act as though JAVA=no > was set. > > Is it even possible to install both jdk and openjdk8 without them > stepping on each other? If so, the user should be able to set JAVA=jdk > or JAVA=openjdk8, and if he doesn't, and both are installed, I guess > give precedence to jdk. > > For more bonus points, make the slack-desc say: > > This package was built with %JAVA%. > > ...and instead of "cat $CWD/slack-desc > $PKG/install/slack-desc", do this: > > sed "s,%JAVA%,$JAVA," $CWD/slack-desc > $PKG/install/slack-desc > > Where JAVA is set to one of "jdk", "openjdk8", or "no Java support". I > do this in quite a few of my own builds, if only to help myself keep > track of what options a package was built with. > > Whether this is actually a good idea depends on exactly what functionality > is missing from LibreOffice if it's built without Java. I have no idea, > but not having one or the other in REQUIRES is going to lead to a lot > of non-README-reading users building without it. > > Another facet: some people will prefer openjdk because of > licensing. People who care about the "Libre" in the LibreOffice name > might care about this. > Thanks for the suggestions - I'll ponder on them ... chris From khronosschoty at utmail.net Sun Feb 26 13:11:27 2017 From: khronosschoty at utmail.net (Vasily Sora) Date: Sun, 26 Feb 2017 05:11:27 -0800 Subject: [Slackbuilds-users] LibreOffice without Java? In-Reply-To: References: Message-ID: I just wanted to point out this SlackBuild here: https://notabug.org/orbea/Slackbuilds/src/master/office/libreoffice. I have no actual experience working with LibreOffice without Java; but I hear its pretty close to fully functional; and that most users wont miss whats missing. On 02/26/2017 04:53 AM, slackbuilds-users-request at slackbuilds.org wrote: > Send SlackBuilds-users mailing list submissions to > slackbuilds-users at slackbuilds.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > or, via email, send a message with subject or body 'help' to > slackbuilds-users-request at slackbuilds.org > > You can reach the person managing the list at > slackbuilds-users-owner at slackbuilds.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SlackBuilds-users digest..." > > > Today's Topics: > > 1. Re: openjdk was: Re: Updates - 20170225.1 (Rich Shepard) > 2. Re: openjdk was: Re: Updates - 20170225.1 (Christoph Willing) > 3. Weechat maintainer wanted (firebird209) > 4. Re: openjdk was: Re: Updates - 20170225.1 (B Watson) > 5. Re: Weechat maintainer wanted (Benjamin Trigona-Harany) > 6. Re: Weechat maintainer wanted (firebird209) > 7. Re: openjdk was: Re: Updates - 20170225.1 (Christoph Willing) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 25 Feb 2017 15:57:51 -0800 (PST) > From: Rich Shepard > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 > Message-ID: > Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed > > On Sun, 26 Feb 2017, Andrzej Telszewski wrote: > >> I've been building openjdk (version 7) on 64 bits just fine. Please take a >> look at the README, as it has many pointers on what might go wrong. > I built and use openjdk-8 on both 32- and 64-bit machines. JabRef (and > Jgnash before I switched to GnuCash) work just fine with openjdk. > > Rich > > > ------------------------------ > > Message: 2 > Date: Sun, 26 Feb 2017 14:20:27 +1000 > From: Christoph Willing > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 > Message-ID: <39182867-607c-87e6-59a9-d52b98703467 at iinet.net.au> > Content-Type: text/plain; charset=utf-8 > > On 26/02/17 09:53, Christoph Willing wrote: >> On 26/02/17 09:25, Christoph Willing wrote: >>> On 25/02/17 18:12, B Watson wrote: >>>> On 2/24/17, Christoph Willing wrote: >>>>> Over time, I've had many suggestions and reminders that LibreOffice will >>>>> build successfully without the jdk package. I prefer a build with as >>>>> full functionality as is made possible upstream, so I prefer that it >>>>> remain as a requirement. Java haters are welcome to add --without-java >>>>> or --with-java=no to their local versions - which reminds me I could add >>>>> a JAVA=no option to the SlackBuild at the next version update. >>>> Will it work with openjdk rather than Oracle's jdk? >>>> >>>> That's probably a question that should be asked about any of the builds >>>> mentioned in this thread. >>>> >>>> If the answer is "it requires a JDK, and will work with either jdk or >>>> openjdk", what's the best way to handle that? List jdk in REQUIRES, >>>> and say "you can use openjdk instead of jdk" in the README? Or, list >>>> neither in REQUIRES, and in the README say "you need one of either jdk >>>> or openjdk"? >>>> >>>> Or, maybe openjdk should be listed in REQUIRES, as it's easier to deal >>>> with (doesn't require jumping through hoops to download like jdk does)? >>>> In which case the README would say "you can use jdk instead of openjdk"? >>> I haven't tried openjdk for a long time - there were often problems >>> running it with the java apps I was using at that time and the Oracle >>> version always just worked. However that was some time ago and your >>> comment about being 'easier to deal with' (in automated build systems, >>> at least) is a good point. >>> >>> Therefore I tried building openjdk in a fresh 14.2 64bit VM and very >>> soon had the following failure: >>> >>> compile: >>> [javac] Compiling 2760 source files to >>> /tmp/SBo/openjdk/icedtea-build/openjdk.build-boot/jaxws/build/classes >>> [javac] Annotation processing got disabled, since it requires a 1.6 >>> compliant JVM >>> [javac] java.lang.NullPointerException >>> [javac] at >>> org.eclipse.jdt.internal.compiler.batch.CompilationUnit.getContents(CompilationUnit.java:77) >>> [javac] at >>> org.eclipse.jdt.internal.compiler.batch.Main$2.acceptResult(Main.java:2962) >>> [javac] at >>> org.eclipse.jdt.internal.compiler.Compiler.handleInternalException(Compiler.java:609) >>> [javac] at >>> org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:527) >>> [javac] at >>> org.eclipse.jdt.internal.compiler.batch.Main.performCompilation(Main.java:4099) >>> [javac] at >>> org.eclipse.jdt.internal.compiler.batch.Main.compile(Main.java:1689) >>> [javac] at >>> org.eclipse.jdt.internal.compiler.batch.Main.main(Main.java:1400) >>> [javac] >>> >>> BUILD FAILED >>> /tmp/SBo/openjdk/icedtea-build/openjdk-boot/jaxws/build.xml:155: Compile >>> failed; see the compiler error output for details. >>> >>> Total time: 1 second >>> Makefile:150: recipe for target 'all' failed >>> >>> >>> >>> This morning I've just started a build in a 32bit VM which is not >>> complete yet but seems to be progressing just fine. Is there a known >>> problem with openjdk on 64bit? Does anyone recognize the failure above >>> and/or know a possible solution? >>> >> Well the 32bit version finished building so I was encouraged to try the >> 64bit build again. This time it has passed the previous point of failure >> and seems also to be progressing just fine. >> >> In the meantime, I see that the 32bit build produced >> openjdk-7u111b01-i486-1_SBo.txz which seems pretty old. Looking around I >> found there was also a SlackBuild for openjdk8 (and even older >> openjdk6). Wanting to try the openjdk8, I found it has a requirement for >> openjdk (not just apache-ant, as is the case for openjdk & openjdk6). Is >> that just a typo (should require apache-ant, not openjdk)? >> > Answering my own question; no it's not a typo. > > To test, I changed the openjdk8's REQUIRES field from openjdk to > apache-ant but the build failed because JAVA_HOME hadn't been set up > i.e. no jdk or openjdk installed. When I reverted the REQUIRES field to > openjdk, the build of openjdk8 succeeded. > > Furthermore, openjdk's own README-builds.html states that before > attempting to build: > "Install a Bootstrap JDK. All OpenJDK builds require access to a > previously released JDK called the bootstrap JDK or boot JDK. The > general rule is that the bootstrap JDK must be an instance of the > previous major release of the JDK." > > The question for me now is whether changing LibreOffice's jdk > requirement to openjdk really makes building LibreOffice much more > straightforward. While it may build with openjdk, I'd personally be > uncomfortable with using an out of date version. However to use openjdk8 > as the requirement means that a builder of LibreOffice needs to build > openjdk first, then openjdk8. > > Apart from the complication of downloading the Oracle jdk, building it > (repackaging it) seems simpler, not to mention much faster. > > Any other views on using openjdk* instead of jdk as requirement for > LibreOffice? > > chris > > > > ------------------------------ > > Message: 3 > Date: Sun, 26 Feb 2017 01:47:17 -0600 > From: firebird209 > To: SlackBuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Weechat maintainer wanted > Message-ID: <3a8a1942-3c49-3941-ee73-f83705a4eaa4 at gmail.com> > Content-Type: text/plain; charset=utf-8 > > Anyone out there who'd like to take over maintaining weechat? I > maintained it for a while now, and actually let a couple versions slip > past so it needs updating to current release. I've just no interest in > maintaining it anymore so wanting to pass the torch to someone else. > > Thank you. > > > > ------------------------------ > > Message: 4 > Date: Sun, 26 Feb 2017 03:13:46 -0500 > From: B Watson > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > On 2/25/17, Christoph Willing wrote: > >> Apart from the complication of downloading the Oracle jdk, building it >> (repackaging it) seems simpler, not to mention much faster. >> >> Any other views on using openjdk* instead of jdk as requirement for >> LibreOffice? > I haven't really got a horse in this race (have never used LibreOffice), > but I'm full of ideas. Which you can ignore, if you think they're bad > ideas (I won't be offended). > > What's needed is a way to say "either-or" in REQUIRES. Which isn't > likely to happen (nobody wants the added complexity, for good & valid > reasons). So instead... > > You could leave both jdk and openjdk out of REQUIRES, and in the README > say "For a full-featured LibreOffice build, you will require either jdk > or openjdk8". For bonus points, have the script auto-detect which is > installed and use that. If neither is installed, act as though JAVA=no > was set. > > Is it even possible to install both jdk and openjdk8 without them > stepping on each other? If so, the user should be able to set JAVA=jdk > or JAVA=openjdk8, and if he doesn't, and both are installed, I guess > give precedence to jdk. > > For more bonus points, make the slack-desc say: > > This package was built with %JAVA%. > > ...and instead of "cat $CWD/slack-desc > $PKG/install/slack-desc", do this: > > sed "s,%JAVA%,$JAVA," $CWD/slack-desc > $PKG/install/slack-desc > > Where JAVA is set to one of "jdk", "openjdk8", or "no Java support". I > do this in quite a few of my own builds, if only to help myself keep > track of what options a package was built with. > > Whether this is actually a good idea depends on exactly what functionality > is missing from LibreOffice if it's built without Java. I have no idea, > but not having one or the other in REQUIRES is going to lead to a lot > of non-README-reading users building without it. > > Another facet: some people will prefer openjdk because of > licensing. People who care about the "Libre" in the LibreOffice name > might care about this. > > > ------------------------------ > > Message: 5 > Date: Sun, 26 Feb 2017 01:10:07 -0800 > From: Benjamin Trigona-Harany > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Weechat maintainer wanted > Message-ID: <5787067.1AXnrqdngX at wintermute> > Content-Type: text/plain; charset="us-ascii" > > On Saturday, February 25, 2017 11:47:17 PM PST firebird209 wrote: >> Anyone out there who'd like to take over maintaining weechat? I >> maintained it for a while now, and actually let a couple versions slip >> past so it needs updating to current release. I've just no interest in >> maintaining it anymore so wanting to pass the torch to someone else. >> >> Thank you. > Sure, I can take it. > > > > > ------------------------------ > > Message: 6 > Date: Sun, 26 Feb 2017 03:38:42 -0600 > From: firebird209 > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Weechat maintainer wanted > Message-ID: > Content-Type: text/plain; charset=windows-1252 > > Great, if you want to take it, I shall pass the torch on to you then :) > > Thank you. > > On 2/26/2017 3:10 AM, Benjamin Trigona-Harany wrote: >> On Saturday, February 25, 2017 11:47:17 PM PST firebird209 wrote: >>> Anyone out there who'd like to take over maintaining weechat? I >>> maintained it for a while now, and actually let a couple versions slip >>> past so it needs updating to current release. I've just no interest in >>> maintaining it anymore so wanting to pass the torch to someone else. >>> >>> Thank you. >> Sure, I can take it. >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > > ------------------------------ > > Message: 7 > Date: Sun, 26 Feb 2017 22:53:20 +1000 > From: Christoph Willing > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 > Message-ID: > Content-Type: text/plain; charset=utf-8 > > On 26/02/17 18:13, B Watson wrote: >> On 2/25/17, Christoph Willing wrote: >> >>> Apart from the complication of downloading the Oracle jdk, building it >>> (repackaging it) seems simpler, not to mention much faster. >>> >>> Any other views on using openjdk* instead of jdk as requirement for >>> LibreOffice? >> I haven't really got a horse in this race (have never used LibreOffice), >> but I'm full of ideas. Which you can ignore, if you think they're bad >> ideas (I won't be offended). >> >> What's needed is a way to say "either-or" in REQUIRES. Which isn't >> likely to happen (nobody wants the added complexity, for good & valid >> reasons). So instead... >> >> You could leave both jdk and openjdk out of REQUIRES, and in the README >> say "For a full-featured LibreOffice build, you will require either jdk >> or openjdk8". For bonus points, have the script auto-detect which is >> installed and use that. If neither is installed, act as though JAVA=no >> was set. >> >> Is it even possible to install both jdk and openjdk8 without them >> stepping on each other? If so, the user should be able to set JAVA=jdk >> or JAVA=openjdk8, and if he doesn't, and both are installed, I guess >> give precedence to jdk. >> >> For more bonus points, make the slack-desc say: >> >> This package was built with %JAVA%. >> >> ...and instead of "cat $CWD/slack-desc > $PKG/install/slack-desc", do this: >> >> sed "s,%JAVA%,$JAVA," $CWD/slack-desc > $PKG/install/slack-desc >> >> Where JAVA is set to one of "jdk", "openjdk8", or "no Java support". I >> do this in quite a few of my own builds, if only to help myself keep >> track of what options a package was built with. >> >> Whether this is actually a good idea depends on exactly what functionality >> is missing from LibreOffice if it's built without Java. I have no idea, >> but not having one or the other in REQUIRES is going to lead to a lot >> of non-README-reading users building without it. >> >> Another facet: some people will prefer openjdk because of >> licensing. People who care about the "Libre" in the LibreOffice name >> might care about this. >> > Thanks for the suggestions - I'll ponder on them ... > > chris > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > ------------------------------ > > End of SlackBuilds-users Digest, Vol 130, Issue 41 > ************************************************** > From kingbeowulf at gmail.com Sun Feb 26 20:57:29 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Feb 2017 12:57:29 -0800 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> Message-ID: <61f67ed6-ff65-0108-836e-b1960c57e8ca@gmail.com> On 02/25/2017 03:25 PM, Christoph Willing wrote: ---snip--- > > I haven't tried openjdk for a long time - there were often problems > running it with the java apps I was using at that time and the Oracle > version always just worked. However that was some time ago and your > comment about being 'easier to deal with' (in automated build systems, > at least) is a good point. > ----snip--- In terms of scripts I maintain, openjdk games/jin works graphic/SweetHome3D does not work at least for SweetHome3D, I've never been able to figure out the glitch as of yet. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Sun Feb 26 21:06:56 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 26 Feb 2017 16:06:56 -0500 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: <61f67ed6-ff65-0108-836e-b1960c57e8ca@gmail.com> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <61f67ed6-ff65-0108-836e-b1960c57e8ca@gmail.com> Message-ID: On 2/26/17, King Beowulf wrote: > > In terms of scripts I maintain, openjdk > > games/jin works > graphic/SweetHome3D does not work The only one I maintain with jdk as a hard dep is games/domination. It will semi-work with openjdk: you can play local games, but networked multiplayer throws a bunch of crypto-related exceptions. There's a 3rd party open source crypto package called 'bouncycastle' that might fix it (and might help with your broken build, even). From kingbeowulf at gmail.com Sun Feb 26 21:13:06 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Feb 2017 13:13:06 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. Message-ID: Not sure if this is a global issue, but at least for xarchiver.info, this no longer works: wget https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7.tar.gz Anyone know WTF is going on? Thanks Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ryanpcmcquen at member.fsf.org Sun Feb 26 21:25:05 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Sun, 26 Feb 2017 13:25:05 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> Message-ID: <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> >wget https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7.tar.gz >Anyone know WTF is going on? This works: https://github.com/ib/xarchiver/archive/0.5.4.7.tar.gz -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From hostmaster at slackonly.com Sun Feb 26 21:29:08 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 26 Feb 2017 13:29:08 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: References: Message-ID: <2fe622a3-31df-7aca-6873-09bbc3f099ba@slackonly.com> On 02/26/2017 01:13 PM, King Beowulf wrote: > Not sure if this is a global issue, but at least for xarchiver.info, > this no longer works: > > wget https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7.tar.gz > > Anyone know WTF is going on? > > Thanks > Ed > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > https://github.com/ib/xarchiver/archive/0.5.4.7.tar.gz -------------- next part -------------- An HTML attachment was scrubbed... URL: From hostmaster at slackonly.com Sun Feb 26 21:30:13 2017 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 26 Feb 2017 13:30:13 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> Message-ID: <4009dcd8-2748-6a3c-309c-7e050e262901@slackonly.com> On 02/26/2017 01:25 PM, Ryan P.C. McQuen wrote: > > > > >wget > https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7.tar.gz > > >Anyone know WTF is going on? > > > > > > This works: > > https://github.com/ib/xarchiver/archive/0.5.4.7.tar.gz > > -Ryan > [ryanpcmcquen.org] > > > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Ryan you are fast! :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Sun Feb 26 21:36:52 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 27 Feb 2017 07:36:52 +1000 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: <2fe622a3-31df-7aca-6873-09bbc3f099ba@slackonly.com> References: <2fe622a3-31df-7aca-6873-09bbc3f099ba@slackonly.com> Message-ID: <30e67310-cacd-c2dc-674d-9998c386d279@iinet.net.au> On 27/02/17 07:29, Panagiotis Nikolaou wrote: > On 02/26/2017 01:13 PM, King Beowulf wrote: >> Not sure if this is a global issue, but at least for xarchiver.info, >> this no longer works: >> >> wget https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7.tar.gz >> >> Anyone know WTF is going on? >> >> Thanks >> Ed >> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > https://github.com/ib/xarchiver/archive/0.5.4.7.tar.gz > Could I suggest instead: https://github.com/ib/xarchiver/archive/0.5.4.7/xarchiver-0.5.4.7.tar.gz which gives you xarchiver-0.5.4.7.tar.gz as a result, rather than 0.5.4.7.tar.gz chris From kingbeowulf at gmail.com Sun Feb 26 21:48:58 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Feb 2017 13:48:58 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> Message-ID: <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> On 02/26/2017 01:25 PM, Ryan P.C. McQuen wrote: > > > >wget > https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7.tar.gz > > >Anyone know WTF is going on? > This works: > > https://github.com/ib/xarchiver/archive/0.5.4.7.tar.gz > > -Ryan > [ryanpcmcquen.org] > Dude, I'm not that stupid! damn kids... The downloaded filename is then "0.5.4.7.tar.gz" and not "xarchiver-0.5.4.7.tar.gz" as before. If I click on the link in Firefox, github does stupid script magic to save as "xarchiver-0.5.4.7.tar.gz" even though hovering over the link shows "0.5.4.7.tar.gz" which may also have implication with the d/l link of the SBo page. Thus, this breaks a bunch of SBo related scripts that depend on wget to grab the link from *.info in the correct format - unless you remember to append "-O -.tar.gz" or the scripts will have to use curl -L https://github.com/ib/xarchiver/archive/0.5.4.8.tar.gz > xarchiver-0.5.4.8.tar.gz -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Feb 26 21:50:55 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Feb 2017 13:50:55 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: <30e67310-cacd-c2dc-674d-9998c386d279@iinet.net.au> References: <2fe622a3-31df-7aca-6873-09bbc3f099ba@slackonly.com> <30e67310-cacd-c2dc-674d-9998c386d279@iinet.net.au> Message-ID: <839d02d8-9172-4c22-d452-f2bcc98f9cd9@gmail.com> On 02/26/2017 01:36 PM, Christoph Willing wrote: > On 27/02/17 07:29, Panagiotis Nikolaou wrote: >> On 02/26/2017 01:13 PM, King Beowulf wrote: >>> Not sure if this is a global issue, but at least for xarchiver.info, >>> this no longer works: >>> >>> wget https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7.tar.gz >>> >>> Anyone know WTF is going on? >>> >>> Thanks >>> Ed >>> >>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> https://github.com/ib/xarchiver/archive/0.5.4.7.tar.gz >> > Could I suggest instead: > https://github.com/ib/xarchiver/archive/0.5.4.7/xarchiver-0.5.4.7.tar.gz > > which gives you xarchiver-0.5.4.7.tar.gz as a result, rather than > 0.5.4.7.tar.gz > > chris Thanks, chris. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Feb 26 22:00:03 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Feb 2017 14:00:03 -0800 Subject: [Slackbuilds-users] system/xarchiver download link as changed Message-ID: <7f587b5b-e77a-bf8a-397d-5c4d8c530807@gmail.com> Admins: be advised d/l link for xarchiver has changed/needs correction. Diff against current master attached. https://github.com/ib/xarchiver/archive/0.5.4.7/xarchiver-0.5.4.7.tar.gz Thanks. -------------- next part -------------- A non-text attachment was scrubbed... Name: xarchiver-correct-download.diff Type: text/x-patch Size: 555 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From northrup at yellowapple.us Sun Feb 26 22:30:40 2017 From: northrup at yellowapple.us (Ryan S. Northrup) Date: Sun, 26 Feb 2017 14:30:40 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> Message-ID: <20170226143040.4a5cfb7c@Peridot.yellowapple.us> On Sun, 26 Feb 2017 13:48:58 -0800 King Beowulf wrote: > If I click on the link in Firefox, github does stupid script magic to > save as "xarchiver-0.5.4.7.tar.gz" even though hovering over the link > shows "0.5.4.7.tar.gz" which may also have implication with the d/l > link of the SBo page. > > Thus, this breaks a bunch of SBo related scripts that depend on wget > to grab the link from *.info in the correct format - unless you > remember to append "-O -.tar.gz" or the scripts will > have to use > > curl -L https://github.com/ib/xarchiver/archive/0.5.4.8.tar.gz > > xarchiver-0.5.4.8.tar.gz > > -Ed > > Or the *.info file (and SlackBuild) can use the GitHub-provided version-only name, which is what I personally do in, e.g., elixir.SlackBuild. The resulting folder after extracting the tarball ends up with a more "correct" name, so the only thing really affected is the name of the source archive, and the rest of the SlackBuild can proceed as if nothing was different. I've tested this to work at the very least with sbopkg. Not sure about other SBo-wrapping scripts. -- Ryan S. Northrup northrup at yellowapple.us From baildon.research at googlemail.com Sun Feb 26 22:40:56 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 26 Feb 2017 22:40:56 +0000 Subject: [Slackbuilds-users] system/xarchiver download link as changed In-Reply-To: <7f587b5b-e77a-bf8a-397d-5c4d8c530807@gmail.com> References: <7f587b5b-e77a-bf8a-397d-5c4d8c530807@gmail.com> Message-ID: > be advised d/l link for xarchiver has changed/needs correction. Diff > against current master attached. > > https://github.com/ib/xarchiver/archive/0.5.4.7/xarchiver-0.5.4.7.tar.gz Apparently, what happened is that someone told them they have been doing their git tags wrong: https://github.com/ib/xarchiver/issues/15 ... which is true, and I wish all the other upstreams that put the project name in their tags would stop doing that. But why the bloody hell did they delete lots of the old tags? They could have just added new tags :( It also affects the md5sum and the top level directory name, so that's all fixed now. (I see 0.5.4.8 is out btw) Thanks Ed, Ryan, Panagiotis and Chris! -D. From baildon.research at googlemail.com Sun Feb 26 22:52:35 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 26 Feb 2017 22:52:35 +0000 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: <20170226143040.4a5cfb7c@Peridot.yellowapple.us> References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> <20170226143040.4a5cfb7c@Peridot.yellowapple.us> Message-ID: > Or the *.info file (and SlackBuild) can use the GitHub-provided > version-only name, which is what I personally do in, e.g., > elixir.SlackBuild. The resulting folder after extracting the tarball > ends up with a more "correct" name, so the only thing really affected > is the name of the source archive, and the rest of the SlackBuild can > proceed as if nothing was different. > > I've tested this to work at the very least with sbopkg. Not sure about > other SBo-wrapping scripts. This *doesn't* work for people who download manually with a browser from the SlackBuilds.org webpages, or with anything else that honours content disposition, so whenever I see a SlackBuild doing that, I fix it :p Furthermore, if you use the long-format Github download, the SBo template Just Works. Cheers -D. From yalhcru at gmail.com Sun Feb 26 23:14:21 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 26 Feb 2017 18:14:21 -0500 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> <20170226143040.4a5cfb7c@Peridot.yellowapple.us> Message-ID: On 2/26/17, David Spencer wrote: > Furthermore, if you use the long-format Github download, the SBo > template Just Works. I need to fix some of my builds to do this. I have a few with e.g. tar xvf v$VERSION.tar.gz || tar xvf $PRGNAM-$VERSION.tar.gz From chytraeu at sdf.org Sun Feb 26 23:41:17 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Sun, 26 Feb 2017 17:41:17 -0600 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> <20170226143040.4a5cfb7c@Peridot.yellowapple.us> Message-ID: On 02/26/2017 05:14 PM, B Watson wrote: > On 2/26/17, David Spencer wrote: >> Furthermore, if you use the long-format Github download, the SBo >> template Just Works. > I need to fix some of my builds to do this. I have a few with e.g. > > tar xvf v$VERSION.tar.gz || tar xvf $PRGNAM-$VERSION.tar.gz > I do the same thing as Mr. Watson in some of my SlackBuilds. How do I get the long-format Github download that works with wget or if someone downloads it by clicking on the source at Github? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Sun Feb 26 23:54:25 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 26 Feb 2017 23:54:25 +0000 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> <20170226143040.4a5cfb7c@Peridot.yellowapple.us> Message-ID: > I need to fix some of my builds to do this. I have a few with e.g. > > tar xvf v$VERSION.tar.gz || tar xvf $PRGNAM-$VERSION.tar.gz I don't think maintainers should feel pressure to change this, or even to understand the whole Github download craziness. If you want to leave them until the next version update -- or forever -- that's ok. Cheers -D. From kingbeowulf at gmail.com Mon Feb 27 00:20:15 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Feb 2017 16:20:15 -0800 Subject: [Slackbuilds-users] nvidia-driver symlink glitch Message-ID: <0947eea7-4bef-6f94-a135-f6b650ec7cdf@gmail.com> On reboot, the symlinks for libGL* and libEGL* can end up being changed to the "-xorg" versions, for example, /usr/lib64/libGL.so -> libGL.so.1 /usr/lib64/libGL.so.1 -> libGL.so.1.2.0-xorg /usr/lib64/libGL.so.1.0.0 /usr/lib64/libGL.so.1.2.0-xorg This effects all the Mesa version that are replaced with Nvidia versions (and COMPAT32). I am doing (or not) something screwy with ldconfig and the work around is to simply, as root, nvidia-switch --remove nvidia-switch --install As I am by no means an expect in this area, anyone with a better fix or explanation? -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Mon Feb 27 00:56:31 2017 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 27 Feb 2017 00:56:31 +0000 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> <20170226143040.4a5cfb7c@Peridot.yellowapple.us> Message-ID: > I do the same thing as Mr. Watson in some of my SlackBuilds. How do I > get the long-format Github download that works with wget or if someone > downloads it by clicking on the source at Github? This is a bit complicated, so I'm happy if people don't worry about this or if they make mistakes. But if you really want to know, here it is. We start at the homepage on Github: https://github.com/ib/xarchiver The username here is 'ib' The project name here is 'xarchiver' We look at the 'releases' page from the link that says '32 releases' https://github.com/ib/xarchiver/releases This is actually a list of git tags. The one we want is '0.5.4.7' The long-format download URL is https://github.com///archive//-.tar.gz in this case: https://github.com/ib/xarchiver/archive/0.5.4.7/xarchiver-0.5.4.7.tar.gz Inside the tarball, the top level directory will always be -/ This is true even if the tag starts with the project name, for example previously xarchiver was like this: https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7/xarchiver-xarchiver-0.5.4.7.tar.gz **Exception** if the tag starts with 'v', the tarball name and top level directory does *not* start with 'v', for example https://github.com/kparal/sendKindle/archive/v2.1/sendKindle-2.1.tar.gz Summary: I am truly sorry for bringing this complicated stuff into your lives, and I really don't mind doing fixups when necessary :) Cheers -D. From kingbeowulf at gmail.com Mon Feb 27 01:36:41 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 26 Feb 2017 17:36:41 -0800 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> <20170226143040.4a5cfb7c@Peridot.yellowapple.us> Message-ID: <191a58ba-0f0e-fa0a-1948-a8fb81f8046b@gmail.com> On 02/26/2017 04:56 PM, David Spencer wrote: >> I do the same thing as Mr. Watson in some of my SlackBuilds. How do I >> get the long-format Github download that works with wget or if someone >> downloads it by clicking on the source at Github? > > This is a bit complicated, so I'm happy if people don't worry about > this or if they make mistakes. But if you really want to know, here it > is. > >---snip---- > > Summary: I am truly sorry for bringing this complicated stuff into > your lives, and I really don't mind doing fixups when necessary :) > Dude, I've printed your post an its taped to the wall. Old school, but works. I hate getting emails from user's of my scripts about broken links. Rather fix 'em quick, or at least know why, than constantly have admins scour the database for them! Thanks. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chytraeu at sdf.org Mon Feb 27 01:40:43 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Sun, 26 Feb 2017 19:40:43 -0600 Subject: [Slackbuilds-users] github wget source file ERROR 404: Not Found. In-Reply-To: References: <15a7c4ed3aa.c0e078e143790.4634582678874403258@mcquen.org> <15a7c500e07.11f5d27ce37173.1175136954030954255@member.fsf.org> <5a271e5d-cf74-cec0-aad3-a17088e336c2@gmail.com> <20170226143040.4a5cfb7c@Peridot.yellowapple.us> Message-ID: <8d28f7c9-9ebc-ca98-db73-31133d975e93@sdf.org> On 02/26/2017 06:56 PM, David Spencer wrote: >> I do the same thing as Mr. Watson in some of my SlackBuilds. How do I >> get the long-format Github download that works with wget or if someone >> downloads it by clicking on the source at Github? > This is a bit complicated, so I'm happy if people don't worry about > this or if they make mistakes. But if you really want to know, here it > is. > > We start at the homepage on Github: > https://github.com/ib/xarchiver > The username here is 'ib' > The project name here is 'xarchiver' > > We look at the 'releases' page from the link that says '32 releases' > https://github.com/ib/xarchiver/releases > This is actually a list of git tags. The one we want is '0.5.4.7' > > The long-format download URL is > https://github.com///archive//-.tar.gz > in this case: > https://github.com/ib/xarchiver/archive/0.5.4.7/xarchiver-0.5.4.7.tar.gz > > Inside the tarball, the top level directory will always be > -/ > > This is true even if the tag starts with the project name, for example > previously xarchiver was like this: > https://github.com/ib/xarchiver/archive/xarchiver-0.5.4.7/xarchiver-xarchiver-0.5.4.7.tar.gz > > **Exception** if the tag starts with 'v', the tarball name and top > level directory does *not* start with 'v', for example > https://github.com/kparal/sendKindle/archive/v2.1/sendKindle-2.1.tar.gz > > Summary: I am truly sorry for bringing this complicated stuff into > your lives, and I really don't mind doing fixups when necessary :) > > Cheers > -D. Thanks for the explanation. Looks very helpful. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From dickson.tim at googlemail.com Mon Feb 27 08:23:15 2017 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 27 Feb 2017 08:23:15 +0000 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> Message-ID: <130f67f8-f710-e98a-6f20-7529416c8933@googlemail.com> On 26/02/2017 08:13, B Watson wrote: > On 2/25/17, Christoph Willing wrote: > >> Apart from the complication of downloading the Oracle jdk, building it >> (repackaging it) seems simpler, not to mention much faster. >> >> Any other views on using openjdk* instead of jdk as requirement for >> LibreOffice? > I haven't really got a horse in this race (have never used LibreOffice), > but I'm full of ideas. Which you can ignore, if you think they're bad > ideas (I won't be offended). > > What's needed is a way to say "either-or" in REQUIRES. Which isn't > likely to happen (nobody wants the added complexity, for good & valid > reasons). So instead... > > You could leave both jdk and openjdk out of REQUIRES, and in the README > say "For a full-featured LibreOffice build, you will require either jdk > or openjdk8". For bonus points, have the script auto-detect which is > installed and use that. If neither is installed, act as though JAVA=no > was set. > > Is it even possible to install both jdk and openjdk8 without them > stepping on each other? If so, the user should be able to set JAVA=jdk > or JAVA=openjdk8, and if he doesn't, and both are installed, I guess > give precedence to jdk. > > For more bonus points, make the slack-desc say: > > This package was built with %JAVA%. > > ...and instead of "cat $CWD/slack-desc > $PKG/install/slack-desc", do this: > > sed "s,%JAVA%,$JAVA," $CWD/slack-desc > $PKG/install/slack-desc > > Where JAVA is set to one of "jdk", "openjdk8", or "no Java support". I > do this in quite a few of my own builds, if only to help myself keep > track of what options a package was built with. > > Whether this is actually a good idea depends on exactly what functionality > is missing from LibreOffice if it's built without Java. I have no idea, > but not having one or the other in REQUIRES is going to lead to a lot > of non-README-reading users building without it. without java support macro's (and accessibility functions) don't work, as macros are based on the java types exposed to libre basic/python etc. > Another facet: some people will prefer openjdk because of > licensing. People who care about the "Libre" in the LibreOffice name > might care about this. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From yalhcru at gmail.com Mon Feb 27 09:17:30 2017 From: yalhcru at gmail.com (B Watson) Date: Mon, 27 Feb 2017 04:17:30 -0500 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: <130f67f8-f710-e98a-6f20-7529416c8933@googlemail.com> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> <130f67f8-f710-e98a-6f20-7529416c8933@googlemail.com> Message-ID: On 2/27/17, Tim Dickson wrote: > without java support macro's (and accessibility functions) don't work, > as macros are based on the java types exposed to libre basic/python etc. Hm. In the Windows/Office world, what percentage of Office users actually write macros? Or would even be capable of learning to write them, if someone tried to teach them? Accessibility... if you need it, you need it. Again, I bet the vast majority of users could do without. Maybe it's not completely unreasonable to allow building without java (and make it easy for people to build with java, if they want/need it). From dickson.tim at googlemail.com Mon Feb 27 10:53:28 2017 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 27 Feb 2017 10:53:28 +0000 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> <130f67f8-f710-e98a-6f20-7529416c8933@googlemail.com> Message-ID: <5de3fbc8-b8fd-04d2-c34d-2bb4d46094f9@googlemail.com> On 27/02/2017 09:17, B Watson wrote: > On 2/27/17, Tim Dickson wrote: >> without java support macro's (and accessibility functions) don't work, >> as macros are based on the java types exposed to libre basic/python etc. > Hm. In the Windows/Office world, what percentage of Office users actually > write macros? Or would even be capable of learning to write them, if > someone tried to teach them? I must confess I have a vested interest, as I wrote a (cross platform) job control system in libreoffice calc, which depends on macros in order to work. > Accessibility... if you need it, you need it. Again, I bet the vast > majority of users could do without. > > Maybe it's not completely unreasonable to allow building without java > (and make it easy for people to build with java, if they want/need it). sounds like that would please all camps (apart from the automatic tools that don't know what is required) if the readme clearly states what is supported with the options. It may even improve starting speeds when compiled without the java support. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From atelszewski at gmail.com Mon Feb 27 11:05:57 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 27 Feb 2017 12:05:57 +0100 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: <5de3fbc8-b8fd-04d2-c34d-2bb4d46094f9@googlemail.com> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> <130f67f8-f710-e98a-6f20-7529416c8933@googlemail.com> <5de3fbc8-b8fd-04d2-c34d-2bb4d46094f9@googlemail.com> Message-ID: <58dd001e-2e63-134e-e57a-7dd25dc0b49f@gmail.com> On 27/02/17 11:53, Tim Dickson wrote: > without java support macro's (and accessibility functions) don't work, > as macros are based on the java types exposed to libre basic/python etc. I think Base is useless without Java. I can't confirm, because the last time I used database in office suite was in primary school. -- Best regards, Andrzej Telszewski From dickson.tim at googlemail.com Mon Feb 27 11:38:22 2017 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 27 Feb 2017 11:38:22 +0000 Subject: [Slackbuilds-users] openjdk was: Re: Updates - 20170225.1 In-Reply-To: <58dd001e-2e63-134e-e57a-7dd25dc0b49f@gmail.com> References: <6f713cb3-6546-c9ad-9612-32963f5f5a55@slackbuilds.org> <7153f517-b926-3a7e-ad8c-51fae47539da@iinet.net.au> <39182867-607c-87e6-59a9-d52b98703467@iinet.net.au> <130f67f8-f710-e98a-6f20-7529416c8933@googlemail.com> <5de3fbc8-b8fd-04d2-c34d-2bb4d46094f9@googlemail.com> <58dd001e-2e63-134e-e57a-7dd25dc0b49f@gmail.com> Message-ID: <291706d3-8f27-db7b-2d7f-f76a84825acc@googlemail.com> On 27/02/2017 11:05, Andrzej Telszewski wrote: > On 27/02/17 11:53, Tim Dickson wrote: >> without java support macro's (and accessibility functions) don't work, >> as macros are based on the java types exposed to libre basic/python etc. > > I think Base is useless without Java. > I can't confirm, because the last time I used database in office suite > was in primary school. > yes, I didn't mention that, but it is pretty hard to write a usable visual database interface without programming, and all programming in libreoffice base requires java support. From kingbeowulf at gmail.com Mon Feb 27 22:34:02 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 27 Feb 2017 14:34:02 -0800 Subject: [Slackbuilds-users] nvidia-driver config path typo Message-ID: <29630f01-86fd-7264-b115-639510fe6497@gmail.com> Just had a bug report that I had a typo in the path for the vulkan icd. The correct path is: $PKG/etc/vulcan/icd.d Diff against current master attached. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-driver-vulkan-icd-path-fix.diff Type: text/x-patch Size: 1098 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Feb 28 12:00:26 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 28 Feb 2017 19:00:26 +0700 Subject: [Slackbuilds-users] nvidia-driver config path typo In-Reply-To: <29630f01-86fd-7264-b115-639510fe6497@gmail.com> References: <29630f01-86fd-7264-b115-639510fe6497@gmail.com> Message-ID: <5702fb3b-edae-872a-e945-7159217e071a@slackbuilds.org> > Just had a bug report that I had a typo in the path for the vulkan icd. > The correct path is: > > $PKG/etc/vulcan/icd.d > > Diff against current master attached. Applied to my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Tue Feb 28 19:40:36 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 28 Feb 2017 19:40:36 +0000 Subject: [Slackbuilds-users] libva required by motion Message-ID: <40908cd3-b951-c46d-54d5-9f8499ba0a1b@open-t.co.uk> I am trying to test build the next version/generation of Motion (4.0.1 from here: https://github.com/Motion-Project/motion/releases) to upload at SBo. I'm going around in circles a bit as I can't work out the correct requirements. The previous version has libva down as optional dependency, but this version doesn't seem to want to compile without it. I can't even find libva on SBo anyway - searching for it leads to the vdpau-video page - which in turn requires "a version of the proprietary NVIDIA display driver". I've read the various descriptions of the above libraries - and I can't work out: 1. if libva is really a hard dependency for motion - or how can I compile without it? There doesn't seem to be a corresponding switch for ./configure 2. what is the connection between libva and vdpau-video? Is one a replacement for the other? 3. if vdpau-video is really required - does it literally mean I would have to install NVDIA drivers on a system which doesn't even have any NVDIA chip? Any clues about the above would be much appreciated. I enclose below the output from attempting to compile motion: Linking Motion... -------------------------------------------------------------------------------- gcc -o motion motion.o logger.o conf.o draw.o jpegutils.o vloopback_motion.o video.o video2.o video_common.o netcam.o netcam_ftp.o netcam_jpeg.o netcam_wget.o track.o alg.o event.o picture.o rotate.o webhttpd.o stream.o md5.o netcam_rtsp.o ffmpeg.o -lm -lpthread -ljpeg -lsqlite3 -lavutil -lavformat -lavcodec -lswscale /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: warning: libX11.so.6, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: warning: libvdpau.so.1, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: warning: libva.so.1, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: warning: libva-drm.so.1, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: warning: libva-x11.so.1, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaInitialize' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaQueryConfigProfiles' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaMaxNumImageFormats' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `XOpenDisplay' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vdp_device_create_x11' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaRenderPicture' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaDeriveImage' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaGetDisplay' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaMapBuffer' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaGetImage' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaPutImage' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaDestroySurfaces' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaMaxNumProfiles' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `XDefaultScreen' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaSyncSurface' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaTerminate' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaDestroyImage' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaGetConfigAttributes' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaCreateImage' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaMaxNumEntrypoints' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `XDisplayName' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaCreateSurfaces at VA_API_0.33.0' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaQueryVendorString' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaCreateBuffer' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaQueryConfigEntrypoints' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaDestroyBuffer' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaCreateConfig' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaQueryImageFormats' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaEndPicture' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaErrorStr' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaDestroyConfig' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaUnmapBuffer' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `XDisplayString' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaCreateContext' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaQuerySurfaceAttributes' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaDestroyContext' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: undefined reference to `vaBeginPicture' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `vaGetDisplayDRM' /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: undefined reference to `XCloseDisplay' collect2: error: ld returned 1 exit status make: *** [Makefile:85: motion] Error 1 From jebrhansen+SBo at gmail.com Tue Feb 28 20:10:30 2017 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 28 Feb 2017 20:10:30 +0000 Subject: [Slackbuilds-users] libva required by motion In-Reply-To: <40908cd3-b951-c46d-54d5-9f8499ba0a1b@open-t.co.uk> References: <40908cd3-b951-c46d-54d5-9f8499ba0a1b@open-t.co.uk> Message-ID: On Tue, Feb 28, 2017, 2:40 PM Sebastian Arcus wrote: > I am trying to test build the next version/generation of Motion (4.0.1 > from here: https://github.com/Motion-Project/motion/releases) to upload > at SBo. I'm going around in circles a bit as I can't work out the > correct requirements. The previous version has libva down as optional > dependency, but this version doesn't seem to want to compile without it. > I can't even find libva on SBo anyway - searching for it leads to the > vdpau-video page - which in turn requires "a version of the proprietary > NVIDIA display driver". I've read the various descriptions of the above > libraries - and I can't work out: > > 1. if libva is really a hard dependency for motion - or how can I > compile without it? There doesn't seem to be a corresponding switch for > ./configure > 2. what is the connection between libva and vdpau-video? Is one a > replacement for the other? > 3. if vdpau-video is really required - does it literally mean I would > have to install NVDIA drivers on a system which doesn't even have any > NVDIA chip? > > Any clues about the above would be much appreciated. I enclose below the > output from attempting to compile motion: > > > Linking Motion... > > -------------------------------------------------------------------------------- > gcc -o motion motion.o logger.o conf.o draw.o jpegutils.o > vloopback_motion.o video.o video2.o video_common.o netcam.o netcam_ftp.o > netcam_jpeg.o netcam_wget.o track.o alg.o event.o picture.o rotate.o > webhttpd.o stream.o md5.o netcam_rtsp.o ffmpeg.o -lm -lpthread -ljpeg > -lsqlite3 -lavutil -lavformat -lavcodec -lswscale > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libX11.so.6, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libvdpau.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva-drm.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva-x11.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaInitialize' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryConfigProfiles' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaMaxNumImageFormats' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XOpenDisplay' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vdp_device_create_x11' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaRenderPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDeriveImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetDisplay' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaMapBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaPutImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDestroySurfaces' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaMaxNumProfiles' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDefaultScreen' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaSyncSurface' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaTerminate' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDestroyImage' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaGetConfigAttributes' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaCreateImage' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaMaxNumEntrypoints' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDisplayName' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaCreateSurfaces at VA_API_0.33.0' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryVendorString' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateBuffer' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryConfigEntrypoints' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyBuffer' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateConfig' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaQueryImageFormats' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaEndPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaErrorStr' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyConfig' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaUnmapBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDisplayString' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateContext' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaQuerySurfaceAttributes' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyContext' > > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaBeginPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetDisplayDRM' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XCloseDisplay' > collect2: error: ld returned 1 exit status > make: *** [Makefile:85: motion] Error 1 To me, it looks like your ffmpeg was compiled against dependencies that are not on your system. There's a bunch of undefined references in a bunch of ffmpeg .so files. Did you compile ffmpeg for your system or did you grab a pre-compiled version from some repo? If it's the second, try compiling your own version or at least grab Eric'n pre-compiled version as that should have all dependencies statically linked. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.guldstrand at gmail.com Tue Feb 28 20:10:55 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Tue, 28 Feb 2017 21:10:55 +0100 Subject: [Slackbuilds-users] libva required by motion In-Reply-To: <40908cd3-b951-c46d-54d5-9f8499ba0a1b@open-t.co.uk> References: <40908cd3-b951-c46d-54d5-9f8499ba0a1b@open-t.co.uk> Message-ID: libva-1.6.2-x86_64-1 is a part of slackware already On 28 February 2017 at 20:40, Sebastian Arcus wrote: > I am trying to test build the next version/generation of Motion (4.0.1 from > here: https://github.com/Motion-Project/motion/releases) to upload at SBo. > I'm going around in circles a bit as I can't work out the correct > requirements. The previous version has libva down as optional dependency, > but this version doesn't seem to want to compile without it. I can't even > find libva on SBo anyway - searching for it leads to the vdpau-video page - > which in turn requires "a version of the proprietary NVIDIA display driver". > I've read the various descriptions of the above libraries - and I can't work > out: > > 1. if libva is really a hard dependency for motion - or how can I compile > without it? There doesn't seem to be a corresponding switch for ./configure > 2. what is the connection between libva and vdpau-video? Is one a > replacement for the other? > 3. if vdpau-video is really required - does it literally mean I would have > to install NVDIA drivers on a system which doesn't even have any NVDIA > chip? > > Any clues about the above would be much appreciated. I enclose below the > output from attempting to compile motion: > > > Linking Motion... > -------------------------------------------------------------------------------- > gcc -o motion motion.o logger.o conf.o draw.o jpegutils.o > vloopback_motion.o video.o video2.o video_common.o netcam.o netcam_ftp.o > netcam_jpeg.o netcam_wget.o track.o alg.o event.o picture.o rotate.o > webhttpd.o stream.o md5.o netcam_rtsp.o ffmpeg.o -lm -lpthread -ljpeg > -lsqlite3 -lavutil -lavformat -lavcodec -lswscale > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libX11.so.6, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libvdpau.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva-drm.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva-x11.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaInitialize' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryConfigProfiles' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaMaxNumImageFormats' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XOpenDisplay' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vdp_device_create_x11' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaRenderPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDeriveImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetDisplay' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaMapBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaPutImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDestroySurfaces' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaMaxNumProfiles' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDefaultScreen' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaSyncSurface' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaTerminate' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDestroyImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaGetConfigAttributes' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaCreateImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaMaxNumEntrypoints' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDisplayName' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaCreateSurfaces at VA_API_0.33.0' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryVendorString' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryConfigEntrypoints' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateConfig' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaQueryImageFormats' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaEndPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaErrorStr' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyConfig' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaUnmapBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDisplayString' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateContext' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaQuerySurfaceAttributes' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyContext' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaBeginPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetDisplayDRM' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XCloseDisplay' > collect2: error: ld returned 1 exit status > make: *** [Makefile:85: motion] Error 1 > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From s.arcus at open-t.co.uk Tue Feb 28 20:55:12 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 28 Feb 2017 20:55:12 +0000 Subject: [Slackbuilds-users] libva required by motion In-Reply-To: <40908cd3-b951-c46d-54d5-9f8499ba0a1b@open-t.co.uk> References: <40908cd3-b951-c46d-54d5-9f8499ba0a1b@open-t.co.uk> Message-ID: <7f0862ad-8982-ca80-6e50-ec404764ad80@open-t.co.uk> On 28/02/17 19:40, Sebastian Arcus wrote: > I am trying to test build the next version/generation of Motion (4.0.1 > from here: https://github.com/Motion-Project/motion/releases) to > upload at SBo. Must be the late hour - I just realised that libva is not on SBo any more because it is part of mainline Slackware. And it wasn't installed on the server I was working on, because the x series wasn't installed - it being a headless server. I will get libva and its dependencies installed and re-attempt the compilation. Sorry for the noise! > I'm going around in circles a bit as I can't work out the correct > requirements. The previous version has libva down as optional > dependency, but this version doesn't seem to want to compile without > it. I can't even find libva on SBo anyway - searching for it leads to > the vdpau-video page - which in turn requires "a version of the > proprietary NVIDIA display driver". I've read the various descriptions > of the above libraries - and I can't work out: > > 1. if libva is really a hard dependency for motion - or how can I > compile without it? There doesn't seem to be a corresponding switch > for ./configure > 2. what is the connection between libva and vdpau-video? Is one a > replacement for the other? > 3. if vdpau-video is really required - does it literally mean I would > have to install NVDIA drivers on a system which doesn't even have any > NVDIA chip? > > Any clues about the above would be much appreciated. I enclose below > the output from attempting to compile motion: > > > Linking Motion... > -------------------------------------------------------------------------------- > > gcc -o motion motion.o logger.o conf.o draw.o jpegutils.o > vloopback_motion.o video.o video2.o video_common.o netcam.o > netcam_ftp.o netcam_jpeg.o netcam_wget.o track.o alg.o event.o > picture.o rotate.o webhttpd.o stream.o md5.o netcam_rtsp.o ffmpeg.o > -lm -lpthread -ljpeg -lsqlite3 -lavutil -lavformat -lavcodec -lswscale > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libX11.so.6, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libvdpau.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva-drm.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libva-x11.so.1, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaInitialize' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryConfigProfiles' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaMaxNumImageFormats' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XOpenDisplay' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vdp_device_create_x11' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaRenderPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDeriveImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetDisplay' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaMapBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaPutImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDestroySurfaces' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaMaxNumProfiles' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDefaultScreen' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaSyncSurface' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaTerminate' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaDestroyImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaGetConfigAttributes' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaCreateImage' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaMaxNumEntrypoints' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDisplayName' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaCreateSurfaces at VA_API_0.33.0' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryVendorString' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaQueryConfigEntrypoints' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateConfig' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaQueryImageFormats' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaEndPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaErrorStr' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyConfig' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaUnmapBuffer' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XDisplayString' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaCreateContext' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaQuerySurfaceAttributes' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaDestroyContext' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavcodec.so: > undefined reference to `vaBeginPicture' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `vaGetDisplayDRM' > /usr/lib64/gcc/x86_64-slackware-linux/5.4.0/../../../../lib64/libavutil.so: > undefined reference to `XCloseDisplay' > collect2: error: ld returned 1 exit status > make: *** [Makefile:85: motion] Error 1 > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ >