From willysr at slackbuilds.org Sun Feb 1 18:31:04 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 02 Feb 2015 01:31:04 +0700 Subject: [Slackbuilds-users] screenfetch could not build In-Reply-To: <20150131210748.3daef1ea@artwo.universe.uni> References: <20150130200913.6c4019b6@artwo.universe.uni> <54CC1DD1.5000802@slackbuilds.org> <54CC2A77.4080206@slackbuilds.org> <20150131120932.3d56a4c5@artwo.universe.uni> <54CCCB94.1060004@slackbuilds.org> <20150131182329.07bf7927@artwo.universe.uni> <20150131203841.2f712ea8@artwo.universe.uni> <20150131200527.GA3172@MyPC.phub.net.cable.rogers.com> <20150131210748.3daef1ea@artwo.universe.uni> Message-ID: <54CE70E8.3060509@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I've never implied anything like that. I'm just asking for admin > to leave trace in tte changelog if it exists embedded in the > SlackBuild itself. If someone can fix the version in the script I > guess he can, at the same expense, write 4 or 5 words which state > that he changed it. That takes several seconds. While i do agree that documentation is important, unfortunately in this case, i can't promise anything. One of the reason why we use GIT is because it can track all the changes of the code from initial submission to the latest version. Visit http://slackbuilds.org/cgit/slackbuilds and enter your package name and you can see the history. Writing 4-5 words might be a simple thing, but that only applies to one package, while we have to deal with like +/- 70-100 submissions / week. We do this work on our free time, so our main focus is to make sure the scripts work. If the maintainer wishes to make a self-documentation, that's fine. I have seen some other maintainer do the same thing and it's a nice thing to see, but that's just not our main priority. This is my personal opinion though. Other admins might have different opinion about this. - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTOcOgACgkQiHuDdNczM4F8VACbBBjJwnQujMPpnQP5LXEJlYdM uS0An0KaFg1VRrJVfes2dcOgXieyEDxz =oaW0 -----END PGP SIGNATURE----- From marc at mos6581.de Tue Feb 3 15:08:59 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Tue, 03 Feb 2015 16:08:59 +0100 Subject: [Slackbuilds-users] rename Message-ID: <54D0E48B.1000407@mos6581.de> This package overwrites `rename` from the official util-linux package. I think this should be mentioned in the README or maybe better renaming it to 'pyrename' as it is written python? If a package depend or will depend on it, the user is may not aware of it. -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Feb 3 15:39:00 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 03 Feb 2015 22:39:00 +0700 Subject: [Slackbuilds-users] rename In-Reply-To: <54D0E48B.1000407@mos6581.de> References: <54D0E48B.1000407@mos6581.de> Message-ID: <54D0EB94.1040408@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > This package overwrites `rename` from the official util-linux > package. I think this should be mentioned in the README or maybe > better renaming it to 'pyrename' as it is written python? If a > package depend or will depend on it, the user is may not aware of > it. Fixed in my branch and cc'ed to maintainer Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTQ65MACgkQiHuDdNczM4EnWQCggL/kuIwZgok2/xYniuiy80vR EPYAnAqugSMphWfM9IvPPAAK2oqshyvb =jKLx -----END PGP SIGNATURE----- From petar.petrov at student.oulu.fi Tue Feb 3 20:48:58 2015 From: petar.petrov at student.oulu.fi (Petar Petrov) Date: Tue, 3 Feb 2015 20:48:58 +0000 Subject: [Slackbuilds-users] SeaView does not build against FLTK13 1.3.3 In-Reply-To: <54D0EB94.1040408@slackbuilds.org> References: <54D0E48B.1000407@mos6581.de>,<54D0EB94.1040408@slackbuilds.org> Message-ID: hi to all, I am planning an update of SeaView. It builds fine against fltk13 1.3.2, but fails when i try to build against fltk13 1.3.3. here is the SlackBuild: http://www.student.oulu.fi/~ppetrov/slackbuilds/seaview/seaview.tar.gz the source: http://doua.prabi.fr/software/seaview_data/archive/seaview_4.5.3.3.tar.gz the log of my build: http://www.student.oulu.fi/~ppetrov/slackbuilds/seaview/seaview-1.log or all of the above: http://www.student.oulu.fi/~ppetrov/slackbuilds/seaview/ Any ideas of what to do? -petar From ryan.q at linux.com Tue Feb 3 23:39:24 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Tue, 3 Feb 2015 15:39:24 -0800 Subject: [Slackbuilds-users] SeaView does not build against FLTK13 1.3.3 In-Reply-To: References: <54D0E48B.1000407@mos6581.de> <54D0EB94.1040408@slackbuilds.org> Message-ID: On 2/3/15, Petar Petrov wrote: > hi to all, > > I am planning an update of SeaView. It builds fine against fltk13 1.3.2, but > fails when i try to build against fltk13 1.3.3. > Does it build against fltk? http://slackbuilds.org/repository/14.1/libraries/fltk/ > here is the SlackBuild: > http://www.student.oulu.fi/~ppetrov/slackbuilds/seaview/seaview.tar.gz > the source: > http://doua.prabi.fr/software/seaview_data/archive/seaview_4.5.3.3.tar.gz > the log of my build: > http://www.student.oulu.fi/~ppetrov/slackbuilds/seaview/seaview-1.log > > or all of the above: > http://www.student.oulu.fi/~ppetrov/slackbuilds/seaview/ > > Any ideas of what to do? > > -petar > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- --- From yalhcru at gmail.com Wed Feb 4 00:11:03 2015 From: yalhcru at gmail.com (B Watson) Date: Tue, 3 Feb 2015 19:11:03 -0500 Subject: [Slackbuilds-users] SeaView does not build against FLTK13 1.3.3 In-Reply-To: References: <54D0E48B.1000407@mos6581.de> <54D0EB94.1040408@slackbuilds.org> Message-ID: On 2/3/15, Petar Petrov wrote: > I am planning an update of SeaView. It builds fine against fltk13 1.3.2, but > fails when i try to build against fltk13 1.3.3. I noticed this, in seaview's Makefile: #uncomment and adapt to your local file system the next line to use your own, uninstalled FLTK library #FLTK = $(HOME)/fltk-1.3.2 You could adapt that to build seaview with its own static copy of fltk-1.3.2. You'd add the fltk-1.3.2 source to DOWNLOAD= and remove fltk13 from REQUIRES=, and patch or sed the Makefile to look in e.g. $TMP/fltk-1.3.2 (or wherever you extract fltk-1.3.2). From niels.horn at gmail.com Wed Feb 4 01:02:59 2015 From: niels.horn at gmail.com (Niels Horn) Date: Tue, 3 Feb 2015 23:02:59 -0200 Subject: [Slackbuilds-users] My packages Message-ID: Greetings to all, As some of you may have noticed, I've not been able to update my SlackBuild scripts for some time now. It's not that I've lost interest. My whole professional life has been motivated by changes and challenges and when some time ago the company I work for offered me a new challenge, I accepted it. At the time I had no real clue about the consequences, but the idea of branching away from a technical career to an executive position seduced me (money-wise as well, naturally). I've learned many new things, like negotiating with legal departments, collaboration with branches from all aver the world, motivating leaders, setting goals and encouraging people to work hard to reach them, etc. But, it came with a price... More responsibility and more work hours. And that means less time for fun projects like maintaining SlackBuilds, a blog, homepage, etc. I miss that, but it is a choice I made and I'm enjoying some of the results. The only non-professional activity I kept is carpentry. I enjoy building furniture, fixing anything made from wood and hope to continue doing so ever after I retire. I still use Slackware and will continue doing so as long as it exists. No Windows or Mac for me. Over the last several months I've received some e-mails requesting updates of scripts. Some people I managed to convince to take over maintainership of a certain package, others not (yet). Basically, all my scripts are "up for grabs". I've not even been able to keep track of which ones already have been taken over, so feel free to do a # find ./ -name "*.info" -exec grep -l "Niels Horn" {} \; in your local copy of the SlackBuilds repository. If you have any technical questions about a specific script, feel free to contact me. It might take a few days to get an answer, but eventually I will. For the rest, the very capable administrators of SlackBuilds.org will no doubt find a way to handle any questions. Have fun! -- Niels Horn -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Wed Feb 4 01:07:04 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 3 Feb 2015 17:07:04 -0800 Subject: [Slackbuilds-users] My packages In-Reply-To: References: Message-ID: sorry to hear that. if nobody's taken fritzing, i'll take that one. -m On Tue, Feb 3, 2015 at 5:02 PM, Niels Horn wrote: > Greetings to all, > > As some of you may have noticed, I've not been able to update my > SlackBuild scripts for some time now. > > It's not that I've lost interest. > My whole professional life has been motivated by changes and challenges > and when some time ago the company I work for offered me a new challenge, I > accepted it. At the time I had no real clue about the consequences, but the > idea of branching away from a technical career to an executive position > seduced me (money-wise as well, naturally). > I've learned many new things, like negotiating with legal departments, > collaboration with branches from all aver the world, motivating leaders, > setting goals and encouraging people to work hard to reach them, etc. > > But, it came with a price... More responsibility and more work hours. > And that means less time for fun projects like maintaining SlackBuilds, a > blog, homepage, etc. > I miss that, but it is a choice I made and I'm enjoying some of the > results. > The only non-professional activity I kept is carpentry. I enjoy building > furniture, fixing anything made from wood and hope to continue doing so > ever after I retire. > > I still use Slackware and will continue doing so as long as it exists. No > Windows or Mac for me. > > Over the last several months I've received some e-mails requesting updates > of scripts. > Some people I managed to convince to take over maintainership of a certain > package, others not (yet). > Basically, all my scripts are "up for grabs". I've not even been able to > keep track of which ones already have been taken over, so feel free to do a > > # find ./ -name "*.info" -exec grep -l "Niels Horn" {} \; > > in your local copy of the SlackBuilds repository. > If you have any technical questions about a specific script, feel free to > contact me. It might take a few days to get an answer, but eventually I > will. > > For the rest, the very capable administrators of SlackBuilds.org will no > doubt find a way to handle any questions. > > Have fun! > > -- > Niels Horn > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Wed Feb 4 03:21:10 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 04 Feb 2015 03:21:10 +0000 Subject: [Slackbuilds-users] My packages References: Message-ID: On Tue, Feb 3, 2015, 5:07 PM Miguel De Anda wrote: sorry to hear that. if nobody's taken fritzing, i'll take that one. -m On Tue, Feb 3, 2015 at 5:02 PM, Niels Horn wrote: Greetings to all, As some of you may have noticed, I've not been able to update my SlackBuild scripts for some time now. It's not that I've lost interest. My whole professional life has been motivated by changes and challenges and when some time ago the company I work for offered me a new challenge, I accepted it. At the time I had no real clue about the consequences, but the idea of branching away from a technical career to an executive position seduced me (money-wise as well, naturally). I've learned many new things, like negotiating with legal departments, collaboration with branches from all aver the world, motivating leaders, setting goals and encouraging people to work hard to reach them, etc. But, it came with a price... More responsibility and more work hours. And that means less time for fun projects like maintaining SlackBuilds, a blog, homepage, etc. I miss that, but it is a choice I made and I'm enjoying some of the results. The only non-professional activity I kept is carpentry. I enjoy building furniture, fixing anything made from wood and hope to continue doing so ever after I retire. I still use Slackware and will continue doing so as long as it exists. No Windows or Mac for me. Over the last several months I've received some e-mails requesting updates of scripts. Some people I managed to convince to take over maintainership of a certain package, others not (yet). Basically, all my scripts are "up for grabs". I've not even been able to keep track of which ones already have been taken over, so feel free to do a # find ./ -name "*.info" -exec grep -l "Niels Horn" {} \; I would be honored to take: qt3, wxgtk, gtkextra and brlcad. Thank you for all you have done Niels, you are a true pillar of the Slackware community. in your local copy of the SlackBuilds repository. If you have any technical questions about a specific script, feel free to contact me. It might take a few days to get an answer, but eventually I will. For the rest, the very capable administrators of SlackBuilds.org will no doubt find a way to handle any questions. Have fun! -- Niels Horn _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / FAQ - http:// slackbuilds.org / faq / _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / FAQ - http:// slackbuilds.org / faq / -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Wed Feb 4 03:57:12 2015 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 4 Feb 2015 03:57:12 +0000 Subject: [Slackbuilds-users] My packages In-Reply-To: References: Message-ID: A Ferengi Funeral for Neils? ;-( Well this is the good stuff for me: libraries/eigen3 libraries/libdaemon libraries/libsigsegv libraries/rrdtool network/GeoIP network/ntop network/snort network/transmission system/lbench system/nbench system/slim If there's some graphics/ or libraries/ stuff left over after other people have chosen, I'd be willing to take them rather than see them unmaintained. Best regards -D. From ryan.q at linux.com Wed Feb 4 04:39:07 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 04 Feb 2015 04:39:07 +0000 Subject: [Slackbuilds-users] My packages References: Message-ID: On Tue, Feb 3, 2015, 7:57 PM David Spencer wrote: system/slim I'm not sure what you are running find on, but I've been maintaining slim for a while. Might want to double check you are up to date. That being said, go ahead and take slim, I didn't end up using it much. :-) Best regards -D. _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users@ slackbuilds.org http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / FAQ - http:// slackbuilds.org / faq / -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Wed Feb 4 05:18:23 2015 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 4 Feb 2015 05:18:23 +0000 Subject: [Slackbuilds-users] My packages In-Reply-To: References: Message-ID: > system/slim > > I'm not sure what you are running find on, but I've been maintaining slim > for a while. Might want to double check you are up to date. oops. I grepped that list on my bedroom lappie... right here in bed :O So this particular git clone hasn't been updated in a while, sorry. Maybe I need more regular insomnia to keep it up to date! > That being said, go ahead and take slim, I didn't end up using it much. :-) Er well only if that's really ok with you, thanks and sorry again! All the best -D. From aaditya_gnulinux at zoho.com Wed Feb 4 05:19:48 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 10:49:48 +0530 Subject: [Slackbuilds-users] My packages (David Spencer) In-Reply-To: References: Message-ID: <54D1ABF4.4070808@zoho.com> Message: 3 Date: Wed, 4 Feb 2015 03:57:12 +0000 From: David Spencer To: "SlackBuilds.org Users List" Subject: Re: [Slackbuilds-users] My packages Message-ID: Content-Type: text/plain; charset=UTF-8 A Ferengi Funeral for Neils? ;-( Well this is the good stuff for me: libraries/eigen3 libraries/libdaemon libraries/libsigsegv libraries/rrdtool network/GeoIP network/ntop network/snort network/transmission system/lbench system/nbench system/slim If there's some graphics/ or libraries/ stuff left over after other people have chosen, I'd be willing to take them rather than see them unmaintained. Best regards -D. ------------------------------ I can also take up transmission if David does not mind, or maybe he could implement an option in the SlackBuild for allowing not to install the Qt part of the client on GTK systems (a QT=no flag). Thx, Aaditya From baildon.research at googlemail.com Wed Feb 4 05:24:36 2015 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 4 Feb 2015 05:24:36 +0000 Subject: [Slackbuilds-users] My packages (David Spencer) In-Reply-To: <54D1ABF4.4070808@zoho.com> References: <54D1ABF4.4070808@zoho.com> Message-ID: > I can also take up transmission if David does not mind But of course, you're very welcome to have it... sounds like you will do a better job than me, and I'll have more time to finish fixing the slackrepo install problems you found :) Goodnight folks -D. From yalhcru at gmail.com Wed Feb 4 05:38:45 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 4 Feb 2015 00:38:45 -0500 Subject: [Slackbuilds-users] My packages (David Spencer) In-Reply-To: <54D1ABF4.4070808@zoho.com> References: <54D1ABF4.4070808@zoho.com> Message-ID: On 2/4/15, Aaditya Bagga wrote: > I can also take up transmission if David does not mind, or maybe he could > implement an option in the SlackBuild for allowing not to install the Qt > part of the client on GTK systems (a QT=no flag). For that matter, how about a GTK=no flag? There are a couple of us only using the Qt client (for one thing, the GTK one misbehaves under windowmaker). From aaditya_gnulinux at zoho.com Wed Feb 4 05:40:12 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 11:10:12 +0530 Subject: [Slackbuilds-users] My packages (David Spencer) In-Reply-To: References: Message-ID: <54D1B0BC.7050406@zoho.com> > I can also take up transmission if David does not mind But of course, you're very welcome to have it... sounds like you will do a better job than me, and I'll have more time to finish fixing the slackrepo install problems you found :) -------------------------------------------------------------------------------------- Thx David. And if someone else is interested in maintaining in transmission as well, let us know. Regards, Aaditya From aaditya_gnulinux at zoho.com Wed Feb 4 05:44:18 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 11:14:18 +0530 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 106, Issue 2 In-Reply-To: References: Message-ID: <54D1B1B2.1050908@zoho.com> >/ I can also take up transmission if David does not mind, or maybe he could />/ implement an option in the SlackBuild for allowing not to install the Qt />/ part of the client on GTK systems (a QT=no flag). / For that matter, how about a GTK=no flag? There are a couple of us only using the Qt client (for one thing, the GTK one misbehaves under windowmaker). ---------------------------------------------------------------------- Sure, why not. B Watson, would you like to maintain transmission and add these flags. If so, you can go ahead :) Thx, Aaditya P.S. My messages may look strange as I am posting by copying from the Slackbuild-users web archive. -------------- next part -------------- An HTML attachment was scrubbed... URL: From aaditya_gnulinux at zoho.com Wed Feb 4 06:00:57 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 11:30:57 +0530 Subject: [Slackbuilds-users] My packages (Aaditya Bagga) In-Reply-To: References: Message-ID: <54D1B599.4080006@zoho.com> Sure, why not. B Watson, would you like to maintain transmission and add these flags. If so, you can go ahead :) Thx, Aaditya P.S. My messages may look strange as I am posting by copying from the Slackbuild-users web archive. ---------------------------- Sorry for the wrong header in the previous message, and I am working on adding the GTK=no and QT=no flags. From yalhcru at gmail.com Wed Feb 4 06:14:20 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 4 Feb 2015 01:14:20 -0500 Subject: [Slackbuilds-users] My packages (Aaditya Bagga) In-Reply-To: <54D1B599.4080006@zoho.com> References: <54D1B599.4080006@zoho.com> Message-ID: On 2/4/15, Aaditya Bagga wrote: > Sure, why not. > > B Watson, would you like to maintain transmission and add these flags. > > If so, you can go ahead :) Hm, right now I can't even download it: Connecting to download-origin.transmissionbt.com (download-origin.transmissionbt.com)|212.129.33.50|:80... failed: Connection refused. From yalhcru at gmail.com Wed Feb 4 06:22:22 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 4 Feb 2015 01:22:22 -0500 Subject: [Slackbuilds-users] My packages (Aaditya Bagga) In-Reply-To: References: <54D1B599.4080006@zoho.com> Message-ID: On 2/4/15, B Watson wrote: > Connecting to download-origin.transmissionbt.com > (download-origin.transmissionbt.com)|212.129.33.50|:80... failed: > Connection refused. Guess that's why we have maintainers. Upstream changed the URL. I'll take over transmission and submit a new script in the next day or so, but meanwhile, Willy or someone, could you change the download link to: https://transmission.cachefly.net/transmission-2.84.tar.xz From aaditya_gnulinux at zoho.com Wed Feb 4 06:25:32 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 11:55:32 +0530 Subject: [Slackbuilds-users] My packages (Aaditya Bagga) In-Reply-To: References: Message-ID: <54D1BB5C.70108@zoho.com> On 2/4/15, B Watson wrote: > Connecting to download-origin.transmissionbt.com > (download-origin.transmissionbt.com)|212.129.33.50|:80... failed: > Connection refused. Guess that's why we have maintainers. Upstream changed the URL. I'll take over transmission and submit a new script in the next day or so, but meanwhile, Willy or someone, could you change the download link to: https://transmission.cachefly.net/transmission-2.84.tar.xz -------------------------------------------------------------------- Yeah, I changed the link, here is what I have so far: http://sourceforge.net/projects/mefiles/files/Slackware/transmission.tar.gz (will be up shortly I think) I can build it without Qt (QT=no ./transmission.SlackBuild) But cant seem to disable the GTK client (--disable-gtk) or build the Qt part. Fails with: /usr/lib64/qt/include/QtGui/qwidget.h:556:10: note: no known conversion for argument 1 from ?? to ?QLayout*? mainwin.cc:1323:9: error: invalid use of member function (did you forget the ?()? ?) layout->addItem (spacer, layout->rowCount (), 0, 1, layout->columnCount ()); ^ mainwin.cc:1323:9: error: base operand of ?->? is not a pointer mainwin.cc:1323:34: error: invalid use of member function (did you forget the ?()? ?) layout->addItem (spacer, layout->rowCount (), 0, 1, layout->columnCount ()); ^ mainwin.cc:1323:34: error: base operand of ?->? is not a pointer mainwin.cc:1323:61: error: invalid use of member function (did you forget the ?()? ?) layout->addItem (spacer, layout->rowCount (), 0, 1, layout->columnCount ()); ^ mainwin.cc:1323:61: error: base operand of ?->? is not a pointer make: *** [mainwin.o] Error 1 make: *** Waiting for unfinished jobs.... From willysr at gmail.com Wed Feb 4 06:26:22 2015 From: willysr at gmail.com (Willy Sudiarto Raharjo) Date: Wed, 4 Feb 2015 13:26:22 +0700 Subject: [Slackbuilds-users] My packages (Aaditya Bagga) In-Reply-To: References: <54D1B599.4080006@zoho.com> Message-ID: > but meanwhile, Willy or someone, could you change > the download link to: > > https://transmission.cachefly.net/transmission-2.84.tar.xz done -- Willy Sudiarto Raharjo Personal Blog : http://willysr.blogspot.com Linux Blog: http://slackblogs.blogspot.com From yalhcru at gmail.com Wed Feb 4 07:01:24 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 4 Feb 2015 02:01:24 -0500 Subject: [Slackbuilds-users] My packages (Aaditya Bagga) In-Reply-To: <54D1BB5C.70108@zoho.com> References: <54D1BB5C.70108@zoho.com> Message-ID: On 2/4/15, Aaditya Bagga wrote: > I can build it without Qt (QT=no ./transmission.SlackBuild) > But cant seem to disable the GTK client (--disable-gtk) > or build the Qt part. Working on this myself. I'm stuck on a slow netbook so it'll take me a while to get the script right (even with ccache, the autoreconf and configure step takes a couple minutes). From aaditya_gnulinux at zoho.com Wed Feb 4 07:04:15 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 12:34:15 +0530 Subject: [Slackbuilds-users] transmission-2.84 In-Reply-To: References: Message-ID: <54D1C46F.3020605@zoho.com> On 2/4/15, Aaditya Bagga wrote: > I can build it without Qt (QT=no ./transmission.SlackBuild) > But cant seem to disable the GTK client (--disable-gtk) > or build the Qt part. Working on this myself. I'm stuck on a slow netbook so it'll take me a while to get the script right (even with ccache, the autoreconf and configure step takes a couple minutes). ---------------------------------------------------------------- Thx. The link I posted earlier is up: http://sourceforge.net/projects/mefiles/files/Slackware/transmission.tar.gz I am failing to build the QT version, I think QT5 may have become a dependency to build it? Also failed to disable building the GTK version. Also thing that works is to build the GTK version (QT=no ./transmission.SlackBuild) Regards, Aaditya From philip at vd-hoeven.nl Wed Feb 4 07:47:25 2015 From: philip at vd-hoeven.nl (Philip van der Hoeven) Date: Wed, 04 Feb 2015 08:47:25 +0100 Subject: [Slackbuilds-users] My packages In-Reply-To: References: Message-ID: Hi, I would be interested in these: games/sl graphics/LDView graphics/LDraw_data graphics/leocad graphics/leocad_pieces network/freerdp Regards, Philip On 04-02-2015 02:02, Niels Horn wrote: > Greetings to all, > > As some of you may have noticed, I've not been able to update my SlackBuild scripts for some time now. > > It's not that I've lost interest. > My whole professional life has been motivated by changes and challenges and when some time ago the company I work for offered me a new challenge, I accepted it. At the time I had no real clue about the consequences, but the idea of branching away from a technical career to an executive position seduced me (money-wise as well, naturally). I've learned many new things, like negotiating with legal departments, collaboration with branches from all aver the world, motivating leaders, setting goals and encouraging people to work hard to reach them, etc. > But, it came with a price... More responsibility and more work hours. And that means less time for fun projects like maintaining SlackBuilds, a blog, homepage, etc. I miss that, but it is a choice I made and I'm enjoying some of the results. The only non-professional activity I kept is carpentry. I enjoy building furniture, fixing anything made from wood and hope to continue doing so ever after I retire. > > I still use Slackware and will continue doing so as long as it exists. No Windows or Mac for me. > > Over the last several months I've received some e-mails requesting updates of scripts. Some people I managed to convince to take over maintainership of a certain package, others not (yet). Basically, all my scripts are "up for grabs". I've not even been able to keep track of which ones already have been taken over, so feel free to do a > > # find ./ -name "*.info" -exec grep -l "Niels Horn" {} ; > > in your local copy of the SlackBuilds repository. If you have any technical questions about a specific script, feel free to contact me. It might take a few days to get an answer, but eventually I will. > > For the rest, the very capable administrators of SlackBuilds.org will no doubt find a way to handle any questions. > > Have fun! > > -- > Niels Horn > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users [1] > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ [2] > FAQ - http://slackbuilds.org/faq/ [3] Links: ------ [1] http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users [2] http://lists.slackbuilds.org/pipermail/slackbuilds-users/ [3] http://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lacielacie at rocketmail.com Wed Feb 4 08:01:16 2015 From: lacielacie at rocketmail.com (KaMii) Date: Wed, 4 Feb 2015 00:01:16 -0800 Subject: [Slackbuilds-users] transmission-2.84 In-Reply-To: <54D1C46F.3020605@zoho.com> References: <54D1C46F.3020605@zoho.com> Message-ID: <20150204000116.1fca960b@Andromdeda.andromeda.gal> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have --disable-gtk in my script and it works just fine, but I am also using qt5. I have not tried to build this on qt4 as I am migrating. https://github.com/KaMiila/SlackBuilds/blob/master/transmission/transmission.SlackBuild On Wed, 04 Feb 2015 12:34:15 +0530 Aaditya Bagga wrote: > > On 2/4/15, Aaditya Bagga wrote: > > > I can build it without Qt (QT=no ./transmission.SlackBuild) > > But cant seem to disable the GTK client (--disable-gtk) > > or build the Qt part. > > Working on this myself. I'm stuck on a slow netbook so it'll take > me a while to get the script right (even with ccache, the autoreconf > and configure step takes a couple minutes). > > ---------------------------------------------------------------- > > Thx. > > The link I posted earlier is up: > > http://sourceforge.net/projects/mefiles/files/Slackware/transmission.tar.gz > > I am failing to build the QT version, I think QT5 may have become a > dependency to build it? > > Also failed to disable building the GTK version. > > Also thing that works is to build the GTK version > (QT=no ./transmission.SlackBuild) > > Regards, > Aaditya > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlTR0cwACgkQkO84ARmAdEArnAP9HB/RqH37AnW+1xwhYlg8MDTD jpOdrmadQCaRDEqhy2Oqr1VCCtSojlje4An4rHoTNbf04UDYgxNzhB8WxDKN3xLP CVSJESlDxtwACPhzh3XrptxTpPp+PSbfhBZ2fJNiRnMjA/kPbLvmaZgu334AZfeo PZKmACyklGf46A6+wMM= =QrWQ -----END PGP SIGNATURE----- From aaditya_gnulinux at zoho.com Wed Feb 4 08:12:10 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 13:42:10 +0530 Subject: [Slackbuilds-users] transmission-2.84 (KaMii) In-Reply-To: References: Message-ID: <54D1D45A.7010007@zoho.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have --disable-gtk in my script and it works just fine, but I am also using qt5. I have not tried to build this on qt4 as I am migrating. https://github.com/KaMiila/SlackBuilds/blob/master/transmission/transmission.SlackBuild --------------------------------------------------------------------------- I did some more testing, and was able to disable building of the GTK client. (the option was --without-gtk rather than --disable-gtk) Regarding Qt, someone may need to file a bug report to find out why it is not building with Qt4 (I was also able to build it with Qt5).. Regards, Aaditya From yalhcru at gmail.com Wed Feb 4 08:16:42 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 4 Feb 2015 03:16:42 -0500 Subject: [Slackbuilds-users] transmission-2.84 (KaMii) In-Reply-To: <54D1D45A.7010007@zoho.com> References: <54D1D45A.7010007@zoho.com> Message-ID: On 2/4/15, Aaditya Bagga wrote: > Regarding Qt, someone may need to file a bug report to find out why it is > not building with Qt4 (I was also able to build it with Qt5).. Builds fine with qt4 here. Slack 14.1, 32-bit. See if my about-to-be-submitted script works for you: http://urchlay.naptime.net/~urchlay/transmission.tar.gz From lacielacie at rocketmail.com Wed Feb 4 08:18:29 2015 From: lacielacie at rocketmail.com (KaMii) Date: Wed, 4 Feb 2015 00:18:29 -0800 Subject: [Slackbuilds-users] transmission-2.84 (KaMii) In-Reply-To: <54D1D45A.7010007@zoho.com> References: <54D1D45A.7010007@zoho.com> Message-ID: <20150204001829.5550dc1f@Andromdeda.andromeda.gal> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ah, i wrote that wrong, good catch. As for qt4. I can confirm it builds fine with qt4. uncomment line 125 on my script and change line 150 from qmake-qt5 to qmake. On Wed, 04 Feb 2015 13:42:10 +0530 Aaditya Bagga wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I have --disable-gtk in my script and it works just fine, but I am > also using qt5. I have not tried to build this on qt4 as I am > migrating. > > https://github.com/KaMiila/SlackBuilds/blob/master/transmission/transmission.SlackBuild > --------------------------------------------------------------------------- > > I did some more testing, and was able to disable building of the GTK > client. (the option was --without-gtk rather than --disable-gtk) > > Regarding Qt, someone may need to file a bug report to find out why > it is not building with Qt4 (I was also able to build it with Qt5).. > > Regards, > Aaditya > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlTR1dUACgkQkO84ARmAdED5cQQAplhdoW1wr/XS/DGzLAcu8esq ewYcR9HNtSgR6NvZ8PXjXDu1UH/z28zujxZ1mVeBOv53GxJDLpKNj9JLrpKxUa// IU/6fU1Zc4BYzyJQn7Rs1EbIG7XdkOicRT6duO8tRgN1j0duUIieTfrlx6BicxIT mJIa9QGhnceyuc2WjxY= =TJns -----END PGP SIGNATURE----- From aaditya_gnulinux at zoho.com Wed Feb 4 08:27:16 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Wed, 04 Feb 2015 13:57:16 +0530 Subject: [Slackbuilds-users] transmission-2.84 (B Watson) In-Reply-To: References: Message-ID: <54D1D7E4.1060405@zoho.com> > Builds fine with qt4 here. Slack 14.1, 32-bit. > > See if my about-to-be-submitted script works for you: > > http://urchlay.naptime.net/~urchlay/transmission.tar.gz Yup that works for me. I think it was my fault, I had somehome deleted the lines related to qt4 # Needed when using Qt4 # https://trac.transmissionbt.com/ticket/5700#comment:2 echo "QMAKE_CXXFLAGS += -std=c++11" >> qt/qtr.pro Thx, Aaditya -------------- next part -------------- An HTML attachment was scrubbed... URL: From mario at slackware.hr Wed Feb 4 12:00:49 2015 From: mario at slackware.hr (Mario Preksavec) Date: Wed, 04 Feb 2015 13:00:49 +0100 Subject: [Slackbuilds-users] My packages In-Reply-To: References: Message-ID: <54D209F1.50703@slackware.hr> On 02/04/2015 02:02 AM, Niels Horn wrote: > I still use Slackware and will continue doing so as long as it exists. > No Windows or Mac for me. Great! > Basically, all my scripts are "up for grabs". Okay, I would like to take: network/nagios libraries/rrdtool system/nagios-plugins I've been submitting updates to these already, and asked to take them, but my mails were unanswered :-) p.s. Niels thanks for your work, hope to see you around in the future! -- Mario From mario at slackware.hr Wed Feb 4 12:24:27 2015 From: mario at slackware.hr (Mario Preksavec) Date: Wed, 04 Feb 2015 13:24:27 +0100 Subject: [Slackbuilds-users] My packages In-Reply-To: <54D209F1.50703@slackware.hr> References: <54D209F1.50703@slackware.hr> Message-ID: <54D20F7B.8090606@slackware.hr> On 02/04/2015 01:00 PM, Mario Preksavec wrote: > libraries/rrdtool Doh! Didn't notice an already laid claim to rrdtool, sorry :) David, if you decide that you have one too many... -- Mario From baildon.research at googlemail.com Wed Feb 4 13:17:00 2015 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 4 Feb 2015 13:17:00 +0000 Subject: [Slackbuilds-users] My packages In-Reply-To: <54D20F7B.8090606@slackware.hr> References: <54D209F1.50703@slackware.hr> <54D20F7B.8090606@slackware.hr> Message-ID: Hey Mario! rrdtool is a logical fit with nagios so you are welcome to have it :D This is getting complicated! -D. From mario at slackware.hr Wed Feb 4 13:24:57 2015 From: mario at slackware.hr (Mario Preksavec) Date: Wed, 04 Feb 2015 14:24:57 +0100 Subject: [Slackbuilds-users] My packages In-Reply-To: References: <54D209F1.50703@slackware.hr> <54D20F7B.8090606@slackware.hr> Message-ID: <54D21DA9.80800@slackware.hr> On 02/04/2015 02:17 PM, David Spencer wrote: > Hey Mario! > rrdtool is a logical fit with nagios so you are welcome to have it :D > > This is getting complicated! > -D. Yes, exactly, thanks! Any input regarding SB's that I maintain is appreciated as well! And I wouldn't say "complicated", it's better to have two potential maintainers then none ;-) -- Mario From info at microlinux.fr Wed Feb 4 15:14:54 2015 From: info at microlinux.fr (Niki Kovacs) Date: Wed, 04 Feb 2015 16:14:54 +0100 Subject: [Slackbuilds-users] Uploading squidGuard: problem with .info file Message-ID: <54D2376E.8040405@microlinux.fr> Hi, I just tried to submit a SlackBuild for the URL redirector software squidGuard. The SlackBuilds.org submission interface tells me that "there's a problem with the .info file". I double-checked and triple-checked everything, but I can't possibly see what's wrong. Here's the .info file: PRGNAM="squidGuard" VERSION="1.4" HOMEPAGE="http://www.squidguard.org" DOWNLOAD="http://www.squidguard.org/Downloads/squidGuard-1.4.tar.gz" MD5SUM="de834150998c1386c30feae196f16b06" DOWNLOAD_x86_64="" MD5SUM_x64_64="" REQUIRES="" MAINTAINER="Niki Kovacs" EMAIL="info at microlinux.fr" The files are in my Github repository: $ git clone https://github.com/kikinovak/slackbuilds Take a peek in pending/squidGuard/ Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From erik at slackbuilds.org Wed Feb 4 15:42:08 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 4 Feb 2015 09:42:08 -0600 Subject: [Slackbuilds-users] Uploading squidGuard: problem with .info file In-Reply-To: <54D2376E.8040405@microlinux.fr> References: <54D2376E.8040405@microlinux.fr> Message-ID: <20150204094208.4e18c3ee@shaggy.doo> On Wed, 04 Feb 2015 16:14:54 +0100 Niki Kovacs wrote: > Hi, > > I just tried to submit a SlackBuild for the URL redirector software > squidGuard. The SlackBuilds.org submission interface tells me that > "there's a problem with the .info file". I double-checked and > triple-checked everything, but I can't possibly see what's wrong. Can you try removing all the blank lines at the end? If it still fails, attach the failing tarball to an email and I'll look closer. -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ryan.q at linux.com Wed Feb 4 15:43:17 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 04 Feb 2015 15:43:17 +0000 Subject: [Slackbuilds-users] Uploading squidGuard: problem with .info file References: <54D2376E.8040405@microlinux.fr> <20150204094208.4e18c3ee@shaggy.doo> Message-ID: >MD5SUM_x64_64 Needs to be x86 On Wed, Feb 4, 2015, 7:42 AM Erik Hanson wrote: > On Wed, 04 Feb 2015 16:14:54 +0100 > Niki Kovacs wrote: > > > Hi, > > > > I just tried to submit a SlackBuild for the URL redirector software > > squidGuard. The SlackBuilds.org submission interface tells me that > > "there's a problem with the .info file". I double-checked and > > triple-checked everything, but I can't possibly see what's wrong. > > Can you try removing all the blank lines at the end? If it still fails, > attach the failing tarball to an email and I'll look closer. > > > -- > Erik Hanson > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Wed Feb 4 16:04:00 2015 From: info at microlinux.fr (Niki Kovacs) Date: Wed, 04 Feb 2015 17:04:00 +0100 Subject: [Slackbuilds-users] Uploading squidGuard: problem with .info file In-Reply-To: References: <54D2376E.8040405@microlinux.fr> <20150204094208.4e18c3ee@shaggy.doo> Message-ID: <54D242F0.3080409@microlinux.fr> Le 04/02/2015 16:43, Ryan P.C. McQuen a ?crit : > >MD5SUM_x64_64 > Needs to be x86 Duh! Corrected. Upload worked OK. Thanks! Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From erik at slackbuilds.org Wed Feb 4 16:06:32 2015 From: erik at slackbuilds.org (Erik Hanson) Date: Wed, 4 Feb 2015 10:06:32 -0600 Subject: [Slackbuilds-users] Uploading squidGuard: problem with .info file In-Reply-To: References: <54D2376E.8040405@microlinux.fr> <20150204094208.4e18c3ee@shaggy.doo> Message-ID: <20150204100632.56433d4f@shaggy.doo> On Wed, 04 Feb 2015 15:43:17 +0000 "Ryan P.C. McQuen" wrote: > >MD5SUM_x64_64 > Needs to be x86 Ah, good catch! -- Erik Hanson -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ryan.q at linux.com Wed Feb 4 16:09:35 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 04 Feb 2015 16:09:35 +0000 Subject: [Slackbuilds-users] Uploading squidGuard: problem with .info file References: <54D2376E.8040405@microlinux.fr> <20150204094208.4e18c3ee@shaggy.doo> <20150204100632.56433d4f@shaggy.doo> Message-ID: On Wed, Feb 4, 2015, 8:06 AM Erik Hanson wrote: On Wed, 04 Feb 2015 15:43:17 +0000 "Ryan P.C. McQuen" wrote: > >MD5SUM_x64_64 > Needs to be x86 Ah, good catch! Thanks. :-) -- Erik Hanson _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / FAQ - http:// slackbuilds.org / faq / -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Wed Feb 4 17:15:17 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 04 Feb 2015 09:15:17 -0800 Subject: [Slackbuilds-users] My packages In-Reply-To: References: Message-ID: <54D253A5.9080304@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/03/2015 05:02 PM, Niels Horn wrote: > Greetings to all, > > As some of you may have noticed, I've not been able to update my > SlackBuild scripts for some time now. > > It's not that I've lost interest. My whole professional life has > been motivated by changes and challenges and when some time ago the > company I work for offered me a new challenge, I accepted it. .... > > I still use Slackware and will continue doing so as long as it > exists. No Windows or Mac for me. > > Over the last several months I've received some e-mails requesting > updates of scripts. Some people I managed to convince to take over > maintainership of a certain package, others not (yet). Basically, > all my scripts are "up for grabs". ... Ah, management....I've gone the other direction since it was slowly killing me. Its good to keep at least one hobby - All work and no play... Good luck and don't be a stranger here, on IRC or LQ. I know many of us will miss you. Hopefully you won't shut down your site and blog anytime soon. Its still nice resource. If no one has snagged these yet, I'll take them: multimedia/tovid/tovid.info multimedia/dvdauthor/dvdauthor.info multimedia/minidlna/minidlna.info - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTSU6QACgkQXvwMaW61dLdxagCeLk8RVMt/UqHHWzLcZOL2uvXd bJkAn0f4xP8/aX8WCDo5dLd9k/xEzt7S =flZV -----END PGP SIGNATURE----- From lacielacie at rocketmail.com Thu Feb 5 03:32:39 2015 From: lacielacie at rocketmail.com (KaMii) Date: Wed, 4 Feb 2015 19:32:39 -0800 Subject: [Slackbuilds-users] Qt 5.4.0, QTWebEngine and Pulseaudio Message-ID: <20150204193239.7adb3939@Andromdeda.andromeda.gal> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have been working on getting QTWebEngine to compile without pulseaudio and found a very helpful sed line which allows this. Yet I am having some later issues with the compile job. http://pastebin.com/gSLhPyek The sed lines I found here: http://www.linuxfromscratch.org/~krejzi/kblfs/x/qt5.html sed -e "$ a !contains(QT_CONFIG, pulseaudio): GYP_CONFIG += use_pulseaudio=0" \ -i qtwebengine/src/core/config/desktop_linux.pri The script I wrote and am using is here: https://github.com/KaMiila/SlackBuilds/blob/master/qtwebengine/qtwebengine.SlackBuild Ideally I would love to get a qt5 script that combines QTWebEngine without pulseaudio. I noticed the slackbuild for qt5 has the QTWebEngine disabled if you do not USEPULSE=yes prefix. I just wanted to pass on this sed line and perhaps it is useful for those that want QTWebEngine without pulseaudio? Furthermore, if you can get this to build without, what appears to be a compiler version issue, that I have yet to conquer, please let me know! - -KaMii -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlTS5FcACgkQkO84ARmAdEBdqQQAqw7d23WHJwUxQsBTSZkfXJ3O nBh5cC8YuOEzfbnpgbX91NDO2opX428NCSsAT3B2M8mj66gubay2fbFnvB5MtmDB 34eqWLhuM8sxxAeWM8Fo2hgTLD8CEd2ORlkhx5lJpGy9H4o9yhc9RE3KTAI2MIRv BAb+fgVqgjRSAaPzmws= =/icP -----END PGP SIGNATURE----- From petar.petrov at student.oulu.fi Wed Feb 4 18:21:17 2015 From: petar.petrov at student.oulu.fi (Petar Petrov) Date: Wed, 4 Feb 2015 18:21:17 +0000 Subject: [Slackbuilds-users] SeaView builds now In-Reply-To: References: <54D0E48B.1000407@mos6581.de>, <54D0EB94.1040408@slackbuilds.org>, Message-ID: hi again, SeaView builds now against FLTK 1.3.3. I contacted the developer, he found what the issue was and modified the code of his program so it can use this version of the library. Great! I just submitted an updated script. bye Petar From marc at mos6581.de Thu Feb 5 08:18:18 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Thu, 05 Feb 2015 09:18:18 +0100 Subject: [Slackbuilds-users] Request UID/GID for seafile Message-ID: <54D3274A.5050100@mos6581.de> I'd like to request an UID and GID for seafile - not yet ready for submitting. From the the uid_gid.txt 300 would be the next one. -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Thu Feb 5 08:33:06 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 5 Feb 2015 09:33:06 +0100 Subject: [Slackbuilds-users] Request UID/GID for seafile In-Reply-To: <54D3274A.5050100@mos6581.de> References: <54D3274A.5050100@mos6581.de> Message-ID: 2015-02-05 9:18 GMT+01:00 Marcel Saegebarth : > I'd like to request an UID and GID for seafile - not yet ready for > submitting. > > From the the uid_gid.txt 300 would be the next one. seafile ======= User: seafile UID: 300 GID: 300 Group: seafile GID: 300 done. Matteo From marc at mos6581.de Thu Feb 5 08:36:04 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Thu, 05 Feb 2015 09:36:04 +0100 Subject: [Slackbuilds-users] Request UID/GID for seafile In-Reply-To: References: <54D3274A.5050100@mos6581.de> Message-ID: <54D32B74.7050608@mos6581.de> On 02/05/2015 09:33 AM, Matteo Bernardini wrote: > done. Thanks Matteo. -marc -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Thu Feb 5 08:57:12 2015 From: info at microlinux.fr (Niki Kovacs) Date: Thu, 05 Feb 2015 09:57:12 +0100 Subject: [Slackbuilds-users] Wallpaper directories Message-ID: <54D33068.6080309@microlinux.fr> Hi, Now that my MLED desktop is running nicely, I've decided to share some of my original SlackBuild scripts with SlackBuilds.org. I have a few questions on packaging details. First things first. The Elementary OS distribution has a very nice set of wallpapers. I've packaged these specifically for my Xfce-based desktop (http://www.microlinux.fr/slackware/desktop-14.1-source/xfce/luna-wallpapers/). But I guess folks who build the package from an SBo package will be running all kinds of different desktop environments. Here's the various wallpaper locations I've identified so far: * /usr/share/xfce4/backdrops * /usr/share/backgrounds * /usr/share/wallpapers Each desktop environment (Xfce, KDE, MATE, ...) has his own "default" wallpaper place, meaning the collection of wallpapers display nicely in a preview window when installed there. I think (correct me if I'm wrong) that the best solution would be to 1. Install all wallpapers to, say, /usr/share/xfce4/backdrops. 2. Create symlinks to /usr/share/backgrounds and /usr/share/wallpapers. Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From petar.petrov at student.oulu.fi Thu Feb 5 09:12:56 2015 From: petar.petrov at student.oulu.fi (Petar Petrov) Date: Thu, 5 Feb 2015 09:12:56 +0000 Subject: [Slackbuilds-users] Wallpaper directories In-Reply-To: <54D33068.6080309@microlinux.fr> References: <54D33068.6080309@microlinux.fr> Message-ID: hi Niki, my slack-wallpapers.SlackBuild script places the images in /usr/share/wallpapers and then creates symlinks to /usr/share/backgrounds/xfce. I chose /usr/share/wallpapers, because both Xscreensaver and KDE find the pictures there by default. Later I realised it would be nice for XFCE users to have them displayed in the Desktop Settings previw window. So, the images are symlinked there. I was thinking to add an option to the script to create symlinks that can work similarly for MATE. bye Petar ________________________________________ From: SlackBuilds-users [slackbuilds-users-bounces at slackbuilds.org] on behalf of Niki Kovacs [info at microlinux.fr] Sent: 05 February 2015 10:57 To: slackbuilds-users at slackbuilds.org Subject: [Slackbuilds-users] Wallpaper directories Hi, Now that my MLED desktop is running nicely, I've decided to share some of my original SlackBuild scripts with SlackBuilds.org. I have a few questions on packaging details. First things first. The Elementary OS distribution has a very nice set of wallpapers. I've packaged these specifically for my Xfce-based desktop (http://www.microlinux.fr/slackware/desktop-14.1-source/xfce/luna-wallpapers/). But I guess folks who build the package from an SBo package will be running all kinds of different desktop environments. Here's the various wallpaper locations I've identified so far: * /usr/share/xfce4/backdrops * /usr/share/backgrounds * /usr/share/wallpapers Each desktop environment (Xfce, KDE, MATE, ...) has his own "default" wallpaper place, meaning the collection of wallpapers display nicely in a preview window when installed there. I think (correct me if I'm wrong) that the best solution would be to 1. Install all wallpapers to, say, /usr/share/xfce4/backdrops. 2. Create symlinks to /usr/share/backgrounds and /usr/share/wallpapers. Any suggestions? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - http://slackbuilds.org/faq/ From willysr at slackbuilds.org Thu Feb 5 09:14:31 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 05 Feb 2015 16:14:31 +0700 Subject: [Slackbuilds-users] Wallpaper directories In-Reply-To: References: <54D33068.6080309@microlinux.fr> Message-ID: <54D33477.9080201@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > my slack-wallpapers.SlackBuild script places the images in > /usr/share/wallpapers and then creates symlinks to > /usr/share/backgrounds/xfce. I chose /usr/share/wallpapers, because > both Xscreensaver and KDE find the pictures there by default. Later > I realised it would be nice for XFCE users to have them displayed > in the Desktop Settings previw window. So, the images are symlinked > there. > > I was thinking to add an option to the script to create symlinks > that can work similarly for MATE. mate is using /usr/share/backgrounds/mate/ so it should be easy to be added as well :) - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTTNHcACgkQiHuDdNczM4GgJACgnwm11kx2IHD+ZHtM1ty4O56Z 0+MAoKDxdUnpOVTb0VwrOE+82ipX2rO/ =u3Yn -----END PGP SIGNATURE----- From ryan.q at linux.com Thu Feb 5 14:52:28 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 5 Feb 2015 06:52:28 -0800 Subject: [Slackbuilds-users] Wallpaper directories In-Reply-To: <54D33477.9080201@slackbuilds.org> References: <54D33068.6080309@microlinux.fr> <54D33477.9080201@slackbuilds.org> Message-ID: > /usr/share/xfce4/backdrops On my system (Slackware64-current) it appears xfce is using: /usr/share/backgrounds/xfce On 2/5/15, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> my slack-wallpapers.SlackBuild script places the images in >> /usr/share/wallpapers and then creates symlinks to >> /usr/share/backgrounds/xfce. I chose /usr/share/wallpapers, because >> both Xscreensaver and KDE find the pictures there by default. Later >> I realised it would be nice for XFCE users to have them displayed >> in the Desktop Settings previw window. So, the images are symlinked >> there. >> >> I was thinking to add an option to the script to create symlinks >> that can work similarly for MATE. > > mate is using /usr/share/backgrounds/mate/ so it should be easy to be > added as well :) > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlTTNHcACgkQiHuDdNczM4GgJACgnwm11kx2IHD+ZHtM1ty4O56Z > 0+MAoKDxdUnpOVTb0VwrOE+82ipX2rO/ > =u3Yn > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- --- From info at microlinux.fr Thu Feb 5 17:16:17 2015 From: info at microlinux.fr (Niki Kovacs) Date: Thu, 05 Feb 2015 18:16:17 +0100 Subject: [Slackbuilds-users] Wallpaper directories In-Reply-To: <54D33477.9080201@slackbuilds.org> References: <54D33068.6080309@microlinux.fr> <54D33477.9080201@slackbuilds.org> Message-ID: <54D3A561.1060905@microlinux.fr> Le 05/02/2015 10:14, Willy Sudiarto Raharjo a ?crit : > mate is using/usr/share/backgrounds/mate/ so it should be easy to be > added as well OK, I just submitted the SlackBuild and included symlinks to standard directories for Xfce, MATE and KDE. Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Thu Feb 5 17:22:03 2015 From: info at microlinux.fr (Niki Kovacs) Date: Thu, 05 Feb 2015 18:22:03 +0100 Subject: [Slackbuilds-users] SlackBuild for elementary-xfce icon theme... minor details Message-ID: <54D3A6BB.5070809@microlinux.fr> Hi, The next SlackBuild on my list is for the Elementary-Xfce icon theme... which, in my humble opinion, is by far the best icon theme available for Xfce. Classy, sober, beautiful... and 100% complete (yes, nothing missing). Here's a screenshot: http://www.microlinux.fr/images/desktop/bureau_linux.png The project is hosted at Github: https://github.com/shimmerproject/elementary-xfce There's no "release" per se, no version really, only a "Download ZIP" link. For my own (MLED) needs, I just grabbed the whole repository using Git, made a tarball out of it, put a datestamp on it and then uploaded the thing in my server. What's SBo's policy for this kind of moving target? Extract a snapshot and host it on the SBo server? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From ryan.q at linux.com Thu Feb 5 17:26:14 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 05 Feb 2015 17:26:14 +0000 Subject: [Slackbuilds-users] SlackBuild for elementary-xfce icon theme... minor details References: <54D3A6BB.5070809@microlinux.fr> Message-ID: On Thu, Feb 5, 2015, 9:22 AM Niki Kovacs wrote: Hi, The next SlackBuild on my list is for the Elementary-Xfce icon theme... which, in my humble opinion, is by far the best icon theme available for Xfce. Classy, sober, beautiful... and 100% complete (yes, nothing missing). Here's a screenshot: http:// www.microlinux.fr /images/desktop/bureau_linux.png The project is hosted at Github: https://github.com/shimmerproject/elementary-xfce There's no "release" per se, no version really, only a "Download ZIP" link. I would grab the tarball of the latest commit: https://github.com/shimmerproject/elementary-xfce/archive/71cd0329194fc33a24b67a6952578cf4578d3a38.tar.gz For my own (MLED) needs, I just grabbed the whole repository using Git, made a tarball out of it, put a datestamp on it and then uploaded the thing in my server. What's SBo's policy for this kind of moving target? Extract a snapshot and host it on the SBo server? Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http:// www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / FAQ - http:// slackbuilds.org / faq / -------------- next part -------------- An HTML attachment was scrubbed... URL: From larryhaja at gmail.com Thu Feb 5 17:29:49 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Thu, 5 Feb 2015 09:29:49 -0800 Subject: [Slackbuilds-users] Qt 5.4.0, QTWebEngine and Pulseaudio In-Reply-To: <20150204193239.7adb3939@Andromdeda.andromeda.gal> References: <20150204193239.7adb3939@Andromdeda.andromeda.gal> Message-ID: Hmmm...interesting. I took a look at the BLFS page for qt5. Thanks for the link. I haven't tried compiling qtwebengine without pulseaudio, but the link you sent says that it needs version of nss >= 3.17.3. Slackware 14.1 and -current comes with mozilla-nss 3.16.5. qtwebengine is new in qt5 5.4.0, so I didn't put much effort in compiling it into the qt5.SlackBuild. Good luck, --Larry On Wed, Feb 4, 2015 at 7:32 PM, KaMii wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I have been working on getting QTWebEngine to compile without > pulseaudio and found a very helpful sed line which allows this. Yet I > am having some later issues with the compile job. > http://pastebin.com/gSLhPyek > > The sed lines I found here: > http://www.linuxfromscratch.org/~krejzi/kblfs/x/qt5.html > > sed -e "$ a !contains(QT_CONFIG, pulseaudio): GYP_CONFIG += > use_pulseaudio=0" \ > -i qtwebengine/src/core/config/desktop_linux.pri > > The script I wrote and am using is here: > > https://github.com/KaMiila/SlackBuilds/blob/master/qtwebengine/qtwebengine.SlackBuild > > Ideally I would love to get a qt5 script that combines QTWebEngine > without pulseaudio. I noticed the slackbuild for qt5 has the > QTWebEngine disabled if you do not USEPULSE=yes prefix. I just wanted > to pass on this sed line and perhaps it is useful for those that want > QTWebEngine without pulseaudio? Furthermore, if you can get this to > build without, what appears to be a compiler version issue, that I have > yet to conquer, please let me know! > > - -KaMii > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iJwEAQECAAYFAlTS5FcACgkQkO84ARmAdEBdqQQAqw7d23WHJwUxQsBTSZkfXJ3O > nBh5cC8YuOEzfbnpgbX91NDO2opX428NCSsAT3B2M8mj66gubay2fbFnvB5MtmDB > 34eqWLhuM8sxxAeWM8Fo2hgTLD8CEd2ORlkhx5lJpGy9H4o9yhc9RE3KTAI2MIRv > BAb+fgVqgjRSAaPzmws= > =/icP > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From info at microlinux.fr Thu Feb 5 17:35:51 2015 From: info at microlinux.fr (Niki Kovacs) Date: Thu, 05 Feb 2015 18:35:51 +0100 Subject: [Slackbuilds-users] SlackBuild for elementary-xfce icon theme... minor details In-Reply-To: References: <54D3A6BB.5070809@microlinux.fr> Message-ID: <54D3A9F7.50302@microlinux.fr> Le 05/02/2015 18:26, Ryan P.C. McQuen a ?crit : > I would grab the tarball of the latest commit: > > https://github.com/shimmerproject/elementary-xfce/archive/71cd0329194fc33a24b67a6952578cf4578d3a38.tar.gz > I just figured out that they actually do have releases. The link is almost invisible, but here it is: https://github.com/shimmerproject/elementary-xfce/archive/v0.5.tar.gz Guess I'll go with that one. -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From petar.petrov at student.oulu.fi Thu Feb 5 17:36:01 2015 From: petar.petrov at student.oulu.fi (Petar Petrov) Date: Thu, 5 Feb 2015 17:36:01 +0000 Subject: [Slackbuilds-users] SlackBuild for elementary-xfce icon theme... minor details In-Reply-To: <54D3A6BB.5070809@microlinux.fr> References: <54D3A6BB.5070809@microlinux.fr> Message-ID: Niki, why don't you just link to the tarball at your server? -petar From ryan.q at linux.com Thu Feb 5 17:54:12 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 05 Feb 2015 17:54:12 +0000 Subject: [Slackbuilds-users] My packages References: <54D253A5.9080304@gmail.com> Message-ID: i'm going to jump back in and grab xspacewarp On Wed, Feb 4, 2015, 9:15 AM King Beowulf wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 02/03/2015 05:02 PM, Niels Horn wrote: > > Greetings to all, > > > > As some of you may have noticed, I've not been able to update my > > SlackBuild scripts for some time now. > > > > It's not that I've lost interest. My whole professional life has > > been motivated by changes and challenges and when some time ago the > > company I work for offered me a new challenge, I accepted it. > .... > > > > I still use Slackware and will continue doing so as long as it > > exists. No Windows or Mac for me. > > > > Over the last several months I've received some e-mails requesting > > updates of scripts. Some people I managed to convince to take over > > maintainership of a certain package, others not (yet). Basically, > > all my scripts are "up for grabs". > ... > > Ah, management....I've gone the other direction since it was slowly > killing me. Its good to keep at least one hobby - All work and no play... > > Good luck and don't be a stranger here, on IRC or LQ. I know many of > us will miss you. Hopefully you won't shut down your site and blog > anytime soon. Its still nice resource. > > If no one has snagged these yet, I'll take them: > > multimedia/tovid/tovid.info > multimedia/dvdauthor/dvdauthor.info > multimedia/minidlna/minidlna.info > > - -Ed > > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlTSU6QACgkQXvwMaW61dLdxagCeLk8RVMt/UqHHWzLcZOL2uvXd > bJkAn0f4xP8/aX8WCDo5dLd9k/xEzt7S > =flZV > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From klaatu at straightedgelinux.com Fri Feb 6 04:15:12 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Fri, 06 Feb 2015 17:15:12 +1300 Subject: [Slackbuilds-users] My packages In-Reply-To: References: Message-ID: <54D43FD0.1060701@straightedgelinux.com> I'll take povray. It's up to date with the latest stable release, so I will not be pushing any update, but it's something that is relevant to my work, so I'll gladly keep an eye out for it. - klaatu On 02/04/2015 02:02 PM, Niels Horn wrote: > Greetings to all, > > As some of you may have noticed, I've not been able to update my SlackBuild > scripts for some time now. > > It's not that I've lost interest. > My whole professional life has been motivated by changes and challenges and > when some time ago the company I work for offered me a new challenge, I > accepted it. At the time I had no real clue about the consequences, but the > idea of branching away from a technical career to an executive position > seduced me (money-wise as well, naturally). > I've learned many new things, like negotiating with legal departments, > collaboration with branches from all aver the world, motivating leaders, > setting goals and encouraging people to work hard to reach them, etc. > > But, it came with a price... More responsibility and more work hours. > And that means less time for fun projects like maintaining SlackBuilds, a > blog, homepage, etc. > I miss that, but it is a choice I made and I'm enjoying some of the results. > The only non-professional activity I kept is carpentry. I enjoy building > furniture, fixing anything made from wood and hope to continue doing so > ever after I retire. > > I still use Slackware and will continue doing so as long as it exists. No > Windows or Mac for me. > > Over the last several months I've received some e-mails requesting updates > of scripts. > Some people I managed to convince to take over maintainership of a certain > package, others not (yet). > Basically, all my scripts are "up for grabs". I've not even been able to > keep track of which ones already have been taken over, so feel free to do a > > # find ./ -name "*.info" -exec grep -l "Niels Horn" {} \; > > in your local copy of the SlackBuilds repository. > If you have any technical questions about a specific script, feel free to > contact me. It might take a few days to get an answer, but eventually I > will. > > For the rest, the very capable administrators of SlackBuilds.org will no > doubt find a way to handle any questions. > > Have fun! > > -- > Niels Horn > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From miguel at thedeanda.com Fri Feb 6 06:29:56 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Thu, 5 Feb 2015 22:29:56 -0800 Subject: [Slackbuilds-users] building qt5 apps Message-ID: so i was trying to update the fritzing buildscript to the latest version and ran into problems. the script actually compiles the app (even though they offer a binary) but it requires qt5. i built qt on my machine but it turns out the source only works on qt5 when its < 5.2.1. ( https://github.com/fritzing/fritzing-app/wiki/1.-Building-Fritzing ). however the qt5 buildscript builds qt 5.4.0 so the builds fail. so, that kind of puts me in a tough spot. should i just use the binary and have it build a package from that or wait for fritzing to compile on 5.4+? any thoughts? m -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Fri Feb 6 06:36:56 2015 From: yalhcru at gmail.com (B Watson) Date: Fri, 6 Feb 2015 01:36:56 -0500 Subject: [Slackbuilds-users] building qt5 apps In-Reply-To: References: Message-ID: On 2/6/15, Miguel De Anda wrote: > so, that kind of puts me in a tough spot. should i just use the binary and > have it build a package from that or wait for fritzing to compile on 5.4+? > > any thoughts? Have you actually tried running the binary package? I bet it won't work, whatever's preventing it from compiling will likely prevent it from running too. From info at microlinux.fr Fri Feb 6 07:44:06 2015 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 06 Feb 2015 08:44:06 +0100 Subject: [Slackbuilds-users] dropbox.SlackBuilds: wrong ARCH tag on 32-bit systems Message-ID: <54D470C6.5090002@microlinux.fr> Hi, On 32-bit systems, the Dropbox package gets an "x86" architecture tag instead of "i486". Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From miguel at thedeanda.com Fri Feb 6 07:46:42 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Thu, 5 Feb 2015 23:46:42 -0800 Subject: [Slackbuilds-users] building qt5 apps In-Reply-To: References: Message-ID: I had done it months ago and it was fine. Tried it now assuming qt was statically linked but it actually works with qt 5.4.0. If I uninstall qt5 and run ldd I get: $ldd ./lib/Fritzing linux-vdso.so.1 (0x00007fff26d30000) libz.so.1 => /lib64/libz.so.1 (0x00007f0126a70000) libQt5PrintSupport.so.5 => not found libQt5Svg.so.5 => not found libQt5Widgets.so.5 => not found libQt5SerialPort.so.5 => not found libQt5Sql.so.5 => not found libQt5Network.so.5 => not found libQt5Xml.so.5 => not found libQt5Gui.so.5 => not found libQt5Core.so.5 => not found libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0126850000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f0126548000) libm.so.6 => /lib64/libm.so.6 (0x00007f0126240000) libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f0126028000) libc.so.6 => /lib64/libc.so.6 (0x00007f0125c68000) /lib64/ld-linux-x86-64.so.2 (0x00007f0126cd8000) However, installing qt5 package built yesterday from the sbo script it works! I'll keep retrying. Maybe I'm doing something silly. -m On Thu, Feb 5, 2015 at 10:36 PM, B Watson wrote: > On 2/6/15, Miguel De Anda wrote: > > > so, that kind of puts me in a tough spot. should i just use the binary > and > > have it build a package from that or wait for fritzing to compile on > 5.4+? > > > > any thoughts? > > Have you actually tried running the binary package? I bet it won't > work, whatever's preventing it from compiling will likely prevent it > from running too. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Fri Feb 6 07:53:29 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Thu, 5 Feb 2015 23:53:29 -0800 Subject: [Slackbuilds-users] building qt5 apps In-Reply-To: References: Message-ID: Hmm this is odd. After uninstalling and re-installing the qt5 package and retrying to compile from source but at my local user, the compilation works. I guess there's a good chance it'll work after all. -m On Thu, Feb 5, 2015 at 11:46 PM, Miguel De Anda wrote: > I had done it months ago and it was fine. Tried it now assuming qt was > statically linked but it actually works with qt 5.4.0. If I uninstall qt5 > and run ldd I get: > > $ldd ./lib/Fritzing > linux-vdso.so.1 (0x00007fff26d30000) > libz.so.1 => /lib64/libz.so.1 (0x00007f0126a70000) > libQt5PrintSupport.so.5 => not found > libQt5Svg.so.5 => not found > libQt5Widgets.so.5 => not found > libQt5SerialPort.so.5 => not found > libQt5Sql.so.5 => not found > libQt5Network.so.5 => not found > libQt5Xml.so.5 => not found > libQt5Gui.so.5 => not found > libQt5Core.so.5 => not found > libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f0126850000) > libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f0126548000) > libm.so.6 => /lib64/libm.so.6 (0x00007f0126240000) > libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f0126028000) > libc.so.6 => /lib64/libc.so.6 (0x00007f0125c68000) > /lib64/ld-linux-x86-64.so.2 (0x00007f0126cd8000) > > However, installing qt5 package built yesterday from the sbo script it > works! > > I'll keep retrying. Maybe I'm doing something silly. > > -m > > On Thu, Feb 5, 2015 at 10:36 PM, B Watson wrote: > >> On 2/6/15, Miguel De Anda wrote: >> >> > so, that kind of puts me in a tough spot. should i just use the binary >> and >> > have it build a package from that or wait for fritzing to compile on >> 5.4+? >> > >> > any thoughts? >> >> Have you actually tried running the binary package? I bet it won't >> work, whatever's preventing it from compiling will likely prevent it >> from running too. >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Feb 6 11:55:32 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 06 Feb 2015 18:55:32 +0700 Subject: [Slackbuilds-users] dropbox.SlackBuilds: wrong ARCH tag on 32-bit systems In-Reply-To: <54D470C6.5090002@microlinux.fr> References: <54D470C6.5090002@microlinux.fr> Message-ID: <54D4ABB4.9080400@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > On 32-bit systems, the Dropbox package gets an "x86" architecture > tag instead of "i486". Thanks fixed in my branch and cc to maintainer - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTUq7QACgkQiHuDdNczM4HFpwCdE5XLSpbNt92Y8zLy7E9iyw5d UjQAoJCdD9fU8Sd37y0XFZCV0VnCfoFj =d6Pv -----END PGP SIGNATURE----- From info at microlinux.fr Fri Feb 6 15:31:19 2015 From: info at microlinux.fr (Niki Kovacs) Date: Fri, 06 Feb 2015 16:31:19 +0100 Subject: [Slackbuilds-users] SlackBuild for elementary-xfce icon theme... minor details In-Reply-To: References: <54D3A6BB.5070809@microlinux.fr> Message-ID: <54D4DE47.5090406@microlinux.fr> Le 05/02/2015 18:36, Petar Petrov a ?crit : > Niki, > > why don't you just link to the tarball at your server? If the tarball is available on an official project server, I prefer linking to that. BTW, I just submitted the SlackBuild. Cheers, Niki -- Microlinux - Solutions informatiques 100% Linux et logiciels libres 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Sat Feb 7 08:56:24 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 07 Feb 2015 15:56:24 +0700 Subject: [Slackbuilds-users] Updates - 20150207.1 Message-ID: <54D5D338.1030102@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Feb 7 08:24:33 UTC 2015 academic/archeopteryx: Updated for version 0.9901_beta. academic/bedtools: Updated for version 2.22.1. academic/bwa: Updated for version 0.7.12. academic/fet: Updated for version 5.26.0. academic/gchemutils: Updated for version 0.14.10. academic/genometools: Updated for version 1.5.4. academic/ij-plugins-LOCI: Updated for version 5.0.6. academic/jalview: Updated for version 2.8.2. academic/mafft: Updated for version 7.215. academic/mrbayes: Updated for version 3.2.4. academic/ncbi-blast-plus: Updated for version 2.2.30. academic/omlibraries: Updated for version svn20150131. academic/openmodelica: Updated for version svn24350. academic/paml: Fixed MD5SUM. academic/seaview: Updated for version 4.5.3.4. academic/spidey: Added x86_64 source. academic/staden: Fix build against tklib 0.6. academic/tophat: Updated for version 2.0.13. academic/ugene: Updated for version 1.15.1. academic/vcftools: Updated for version 0.1.12b. academic/zotero: Updated for version 4.0.25.2. audio/TiMidity++: Script cleanup. audio/eawpats: Remove obsolete instructions. audio/fluid-soundfont: Update timidity.cfg path in README. audio/freepats: Remove obsolete instructions. audio/soundconverter: Updated for version 2.1.5. desktop/CurseTheWeather: Fix HOMEPAGE. desktop/cwm-openbsd: Updated for version 5.6.0. desktop/elementary-xfce: Added (icon theme). desktop/luna-wallpapers: Added (Elementary OS Luna wallpapers). desktop/murrine-themes: Updated for version 0.98.8. desktop/screenfetch: Update changelog. desktop/seafile-gui: Added (Seafile Desktop Client). development/arduino: Updated for version 1.0.6. development/bluefish: Updated for version 2.2.6. development/checkbashisms: Added (Check for bashisms). development/chicken: Updated for version 4.9.0.1. development/dbeaver: Updated for version 3.1.2. development/django: Removed (replaced with python-django). development/energia: Updated for version 0101E0014. development/mg-openbsd: Updated for version 5.6.0. development/omake: Maintainer info update + minor fixes development/uncrustify: Added (source code beautifier). games/instead: Updated for version 2.2.1. games/sl: Updated for version 5.02 + new maintainer. gis/Fiona: Updated for version 1.5.0. graphics/LDView: Updated for version 4.2beta1 + new maintainer. graphics/LDraw_data: Updated for version 201402 + new maintainer. graphics/darktable: Updated for version 1.6.2. graphics/digikam: Updated for version 4.7.0. graphics/jhead: Updated for version 3.00. graphics/kphotoalbum: Updated for version 4.6 + new maintainer. graphics/leocad: Updated for version 0.81 + new maintainer. graphics/leocad_pieces: Updated for version 8750 + new maintainer. graphics/librecad: Updated for version 2.0.7. graphics/mitsuba-blender: Added (Blender Mitsuba Addon). graphics/mitsuba: Added (computer graphics renderer). graphics/qcad: Updated for version 3.7.7.0. graphics/qelectrotech: Updated for version 0.4rc2. graphics/shotwell: Updated for version 0.20.2. libraries/batinfo: Added (Battery Information Library). libraries/gtkextra: Updated for version 3.1.2 + new maintainer. libraries/libaacs: Updated for version 0.8.0. libraries/libbde: Updated for version 20150124. libraries/libevhtp: Added (libevent HTTP API). libraries/libfwsi: Updated for version 20150124. libraries/liblogging: Updated for version 1.0.5. libraries/libsearpc: Added (C RPC Framework). libraries/libvirt-python: Updated for version 1.2.12. libraries/libvirt: Updated for version 1.2.12. libraries/libzdb: Added (Source Database Connection Pool Library). libraries/live555: Updated for version 2015.02.05. libraries/mysqltcl: Maintainer info update + minor fixes libraries/php-memcache: Maintainer info update + minor fixes libraries/php-ssh2: Maintainer info update + minor fixes libraries/qt3: New Maintainer. libraries/rrdtool: Updated for version 1.4.9 + maintainer and fixes libraries/xmlrpc-c: Maintainer info update + minor fixes multimedia/flashplayer-plugin: Updated for version 11.2.202.442. multimedia/kodi: Added (Multi-platform Media Center). multimedia/smplayer: Updated for version 14.9.0.6690. multimedia/smtube: Updated for version 15.1.0. multimedia/xbmc: Removed (replaced by kodi). network/ClusterSSH: Updated for version 4.03_06. network/asterisk: Maintainer info update + minor fixes network/btsync: Updated for version 1.4.110. network/ccnet: Added (C Network Framework). network/dropbox: Fix ARCH on x86. network/fping3: Added (Another fping package). network/fping6: Update HOMEPAGE. network/fping: Update HOMEPAGE. network/freerdp: Updated for version 1.2.0_beta1_android9. network/graphite-carbon: Added (Backend data caching). network/hipchat: Updated for version 2.2.1328. network/icecat: Updated for version 31.4.0. network/iojs: Updated for version 1.1.0. network/jitsi: Updated for version 2.6. network/libnftnl: Updated for version 1.0.3. network/mk-livestatus: Updated for version 1.2.4p5 + nagios4 network/mod_ruid2: Updated for version 0.9.8 + enhancements network/nagios: Maintainer change + minor fixes network/nagiosgraph: Updated for version 1.5.2. network/nft: Updated for version 0.4. network/nrpe: Updated for version 2.15 + maintainer change network/nsca: Updated for version 2.9.1 + maintainer change network/oidentd: Maintainer info update + minor fixes network/openresolv: Fix permission. network/privoxy: Updated for version 3.0.23. network/qupzilla: Updated for version 1.8.6. network/seafile-client: Added (Cloud Storage System). network/seafile-server: Added (Cloud Storage System). network/seahub: Added (Seafile Web Frontend). network/squidGuard: Added (URL redirector). network/suricata: Updated for version 2.0.6. network/telegram: Updated for version 0.7.6 + enhancements network/transmission: new maintainer. office/kchmviewer-qt: Updated for version 7.2.1. office/text2pdf: Maintainer info update + minor fixes perl/perl-HTTP-Proxy: Updated for version 0.302. perl/perl-Proc-Daemon: Updated for version 0.18. perl/perl-Term-ReadLine-Gnu: Updated for version 1.26. python/dfvfs: Updated for version 20150129. python/plaso: Added (Forensic Super-Timeline). python/py3sensors: Added (Python bindings to libsensors). python/python-discid: Added (libdiscid Python Bindings). python/python-django-tagging: Added (Generic tagging application). python/python-django: Added (Web framework). python/python-lhafile: Added (Python LHA archive extension). python/python-memcached: Added (Python client for memached). python/python-parse: Added (Python String Parser). python/python-whisper: Added (Fixed size database). system/barman: Updated for version 1.4.0. system/bleachbit: Updated for version 1.6. system/clamav: Updated for version 0.98.6. system/clamtk: Updated for version 5.13. system/freeswitch: Maintainer info update + minor fixes system/glances: Updated for version 2.3. system/mbootpack: Maintainer info update + minor fixes system/nagios-plugins: Maintainer change + minor fixes system/pgadmin3: Updated for version 1.20.0 and minor fixes system/rar2fs: Updated for version 1.19.0 + maintainer info system/rename: Rename executable to pyrename. system/tamsyn-font: Updated for version 1.11. system/the_silver_searcher: Updated for version 0.29.0. system/zarfy: Fix build outside /tmp/SBo. +--------------------------+ NOTE: There's one small mistake: flashplayer-plugins is missing MD5SUMS for the individual .info file (it was taken from GIT), but i managed to fix it on the tarball before pushing the update, so there might be some inconsistency. You can check the checksums in the website (http://slackbuilds.org/repository/14.1/multimedia/flashplayer-plugin/) It will be updated in my branch or if flashplayer happened to get an update before next public update, it will be updated by it's maintainer. Other than above minor issue, this is the biggest change i ever manage since last year: around 145 commits in a week with 2 package removal (xbmc dan django, replaced by kodi and python-django) happy weekend :) - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTV0zgACgkQiHuDdNczM4FYnwCfdrT/f2h1pH1VS8UeMLa+2tgi o9QAoJP8oqr8frqrd1SI+evl8cz+iNVz =5neJ -----END PGP SIGNATURE----- From hostmaster at slackonly.com Sat Feb 7 15:49:54 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sat, 07 Feb 2015 17:49:54 +0200 Subject: [Slackbuilds-users] perl-Net-Pcap Message-ID: <54D63422.5040306@slackonly.com> Hi!, perl-Net-Pcap.SlackBuild stop in: t/00-load.t ................ 1/1 # Testing Net::Pcap 0.17 (libpcap version 1.4.0) under Perl 5.018001 t/00-load.t ................ ok t/01-api.t ................. ok t/02-lookup.t .............. ok t/03-openlive.t ............ ok t/04-loop.t ................ 1/195 Thanks... From willysr at slackbuilds.org Sat Feb 7 19:03:21 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 08 Feb 2015 02:03:21 +0700 Subject: [Slackbuilds-users] perl-Net-Pcap In-Reply-To: <54D63422.5040306@slackonly.com> References: <54D63422.5040306@slackonly.com> Message-ID: <54D66179.90905@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/07/2015 10:49 PM, Panagiotis Nikolaou wrote: > Hi!, > > perl-Net-Pcap.SlackBuild stop in: > > t/00-load.t ................ 1/1 # Testing Net::Pcap 0.17 (libpcap > version 1.4.0) under Perl 5.018001 t/00-load.t ................ ok > t/01-api.t ................. ok t/02-lookup.t .............. ok > t/03-openlive.t ............ ok t/04-loop.t ................ > 1/195 It works here # Testing Net::Pcap 0.17 (libpcap version 1.4.0) under Perl 5.018001 t/00-load.t ................ ok t/01-api.t ................. ok t/02-lookup.t .............. ok t/03-openlive.t ............ ok t/04-loop.t ................ ok t/05-dump.t ................ ok t/06-offline.t ............. ok t/07-stats.t ............... ok t/08-filter.t .............. ok t/09-error.t ............... ok t/10-fileno.t .............. ok t/11-snapshot.t ............ ok t/12-next.t ................ skipped: pcap_next() behaves too strangely for being tested on random machines t/13-dispatch.t ............ ok t/14-datalink.t ............ ok # This platform has been detected as a little endian architecture t/15-is_swapped.t .......... ok t/16-setnonblock.t ......... ok # libpcap version 1.4.0 t/17-lib_version.t ......... ok t/18-open_dead.t ........... ok t/19-breakloop.t ........... ok t/20-constants.t ........... ok t/21-next_ex.t ............. skipped: slowness and random failures... testing pcap_next_ex() is a PITA t/22-open.t ................ skipped: pcap_open() is not available t/23-srcstr.t .............. skipped: pcap_createsrcstr() is not available t/50-poe-component-pcap.t .. skipped: POE is not available t/distchk.t ................ skipped: Test::Distribution required for checking distribution t/pod.t .................... skipped: Test::Pod 1.14 required for testing POD t/podcover.t ............... skipped: Currently not working for Net::Pcap t/podspell.t ............... skipped: Pod spelling: for maintainer only t/portfs.t ................. skipped: Only for the module maintainer All tests successful. Test Summary Report - ------------------- t/06-offline.t (Wstat: 0 Tests: 403 Failed: 0) TODO passed: 398 t/07-stats.t (Wstat: 0 Tests: 134 Failed: 0) TODO passed: 29, 42, 55, 81, 107, 120 t/10-fileno.t (Wstat: 0 Tests: 21 Failed: 0) TODO passed: 19 Files=30, Tests=1508, 393 wallclock secs ( 0.20 usr 0.08 sys + 1.05 cusr 0.25 csys = 1.58 CPU) Result: PASS Files found in blib/arch: installing files in blib/lib into architecture dependent library tree Installing /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/vendor_perl/auto/Net/Pcap/Pcap.bs Installing /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/vendor_perl/auto/Net/Pcap/Pcap.so Installing /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/vendor_perl/Net/Pcap.pm Installing /tmp/SBo/package-perl-Net-Pcap/usr/share/man/man1/pcapinfo.1 Installing /tmp/SBo/package-perl-Net-Pcap/usr/man/man3/Net::Pcap.3 Installing /tmp/SBo/package-perl-Net-Pcap/usr/bin/pcapinfo Appending installation info to /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/perllocal.pod Slackware package maker, version 3.14159. Searching for symbolic links: No symbolic links were found, so we won't make an installation script. You can make your own later in ./install/doinst.sh and rebuild the package if you like. This next step is optional - you can set the directories in your package to some sane permissions. If any of the directories in your package have special permissions, then DO NOT reset them here! Would you like to reset all directory permissions to 755 (drwxr-xr-x) and directory ownerships to root.root ([y]es, [n]o)? n Creating Slackware package: /tmp/sbopkg.Kr45xm/sbopkg-sbooutputdir/perl-Net-Pcap-0.17-x86_64-1_SBo.tgz ./ install/ install/slack-desc usr/ usr/bin/ usr/bin/pcapinfo usr/doc/ usr/doc/perl-Net-Pcap-0.17/ usr/doc/perl-Net-Pcap-0.17/README usr/doc/perl-Net-Pcap-0.17/perl-Net-Pcap.SlackBuild usr/lib64/ usr/lib64/perl5/ usr/lib64/perl5/vendor_perl/ usr/lib64/perl5/vendor_perl/Net/ usr/lib64/perl5/vendor_perl/Net/Pcap.pm usr/lib64/perl5/vendor_perl/auto/ usr/lib64/perl5/vendor_perl/auto/Net/ usr/lib64/perl5/vendor_perl/auto/Net/Pcap/ usr/lib64/perl5/vendor_perl/auto/Net/Pcap/Pcap.so usr/man/ usr/man/man1/ usr/man/man1/pcapinfo.1.gz usr/man/man3/ usr/man/man3/Net::Pcap.3.gz Slackware package /tmp/sbopkg.Kr45xm/sbopkg-sbooutputdir/perl-Net-Pcap-0.17-x86_64-1_SBo.tgz created. you can remove the make test to skip the test which is slow indeed and sometimes need an trigger so that it will continue (an ENTER should be sufficient) - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTWYXkACgkQiHuDdNczM4HK2QCfSAG2CIJTEOzUvX4ooZuVJaEJ 7aYAoJFbxtzaAi8Tv7U2VCF8PBzD443x =jDP1 -----END PGP SIGNATURE----- From hostmaster at slackonly.com Sat Feb 7 19:13:42 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sat, 07 Feb 2015 21:13:42 +0200 Subject: [Slackbuilds-users] perl-Net-Pcap In-Reply-To: <54D66179.90905@slackbuilds.org> References: <54D63422.5040306@slackonly.com> <54D66179.90905@slackbuilds.org> Message-ID: <54D663E6.7020605@slackonly.com> Removing the make test did the job! Thanks Willy! On 02/07/2015 09:03 PM, Willy Sudiarto Raharjo wrote: > On 02/07/2015 10:49 PM, Panagiotis Nikolaou wrote: > > Hi!, > > > perl-Net-Pcap.SlackBuild stop in: > > > t/00-load.t ................ 1/1 # Testing Net::Pcap 0.17 (libpcap > > version 1.4.0) under Perl 5.018001 t/00-load.t ................ ok > > t/01-api.t ................. ok t/02-lookup.t .............. ok > > t/03-openlive.t ............ ok t/04-loop.t ................ > > 1/195 > > It works here > > # Testing Net::Pcap 0.17 (libpcap version 1.4.0) under Perl 5.018001 > t/00-load.t ................ ok > t/01-api.t ................. ok > t/02-lookup.t .............. ok > t/03-openlive.t ............ ok > t/04-loop.t ................ ok > t/05-dump.t ................ ok > t/06-offline.t ............. ok > t/07-stats.t ............... ok > t/08-filter.t .............. ok > t/09-error.t ............... ok > t/10-fileno.t .............. ok > t/11-snapshot.t ............ ok > t/12-next.t ................ skipped: pcap_next() behaves too > strangely for being tested on random machines > t/13-dispatch.t ............ ok > t/14-datalink.t ............ ok > # This platform has been detected as a little endian architecture > t/15-is_swapped.t .......... ok > t/16-setnonblock.t ......... ok > # libpcap version 1.4.0 > t/17-lib_version.t ......... ok > t/18-open_dead.t ........... ok > t/19-breakloop.t ........... ok > t/20-constants.t ........... ok > t/21-next_ex.t ............. skipped: slowness and random failures... > testing pcap_next_ex() is a PITA > t/22-open.t ................ skipped: pcap_open() is not available > t/23-srcstr.t .............. skipped: pcap_createsrcstr() is not available > t/50-poe-component-pcap.t .. skipped: POE is not available > t/distchk.t ................ skipped: Test::Distribution required for > checking distribution > t/pod.t .................... skipped: Test::Pod 1.14 required for > testing POD > t/podcover.t ............... skipped: Currently not working for Net::Pcap > t/podspell.t ............... skipped: Pod spelling: for maintainer only > t/portfs.t ................. skipped: Only for the module maintainer > All tests successful. > > Test Summary Report > ------------------- > t/06-offline.t (Wstat: 0 Tests: 403 Failed: 0) > TODO passed: 398 > t/07-stats.t (Wstat: 0 Tests: 134 Failed: 0) > TODO passed: 29, 42, 55, 81, 107, 120 > t/10-fileno.t (Wstat: 0 Tests: 21 Failed: 0) > TODO passed: 19 > Files=30, Tests=1508, 393 wallclock secs ( 0.20 usr 0.08 sys + 1.05 > cusr 0.25 csys = 1.58 CPU) > Result: PASS > Files found in blib/arch: installing files in blib/lib into > architecture dependent library tree > Installing > /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/vendor_perl/auto/Net/Pcap/Pcap.bs > Installing > /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/vendor_perl/auto/Net/Pcap/Pcap.so > Installing > /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/vendor_perl/Net/Pcap.pm > Installing /tmp/SBo/package-perl-Net-Pcap/usr/share/man/man1/pcapinfo.1 > Installing /tmp/SBo/package-perl-Net-Pcap/usr/man/man3/Net::Pcap.3 > Installing /tmp/SBo/package-perl-Net-Pcap/usr/bin/pcapinfo > Appending installation info to > /tmp/SBo/package-perl-Net-Pcap/usr/lib64/perl5/perllocal.pod > > Slackware package maker, version 3.14159. > > Searching for symbolic links: > > No symbolic links were found, so we won't make an installation script. > You can make your own later in ./install/doinst.sh and rebuild the > package if you like. > > This next step is optional - you can set the directories in your package > to some sane permissions. If any of the directories in your package have > special permissions, then DO NOT reset them here! > > Would you like to reset all directory permissions to 755 (drwxr-xr-x) and > directory ownerships to root.root ([y]es, [n]o)? n > > Creating Slackware package: > /tmp/sbopkg.Kr45xm/sbopkg-sbooutputdir/perl-Net-Pcap-0.17-x86_64-1_SBo.tgz > > ./ > install/ > install/slack-desc > usr/ > usr/bin/ > usr/bin/pcapinfo > usr/doc/ > usr/doc/perl-Net-Pcap-0.17/ > usr/doc/perl-Net-Pcap-0.17/README > usr/doc/perl-Net-Pcap-0.17/perl-Net-Pcap.SlackBuild > usr/lib64/ > usr/lib64/perl5/ > usr/lib64/perl5/vendor_perl/ > usr/lib64/perl5/vendor_perl/Net/ > usr/lib64/perl5/vendor_perl/Net/Pcap.pm > usr/lib64/perl5/vendor_perl/auto/ > usr/lib64/perl5/vendor_perl/auto/Net/ > usr/lib64/perl5/vendor_perl/auto/Net/Pcap/ > usr/lib64/perl5/vendor_perl/auto/Net/Pcap/Pcap.so > usr/man/ > usr/man/man1/ > usr/man/man1/pcapinfo.1.gz > usr/man/man3/ > usr/man/man3/Net::Pcap.3.gz > > Slackware package > /tmp/sbopkg.Kr45xm/sbopkg-sbooutputdir/perl-Net-Pcap-0.17-x86_64-1_SBo.tgz > created. > > > you can remove the make test to skip the test which is slow indeed and > sometimes need an trigger so that it will continue (an ENTER should be > sufficient) > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From C.J.Theunissen at differ.nl Sat Feb 7 23:54:59 2015 From: C.J.Theunissen at differ.nl (Kees Theunissen) Date: Sun, 8 Feb 2015 00:54:59 +0100 (CET) Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): MD5 checksums missing in .info file. Message-ID: Hi, The MD5SUM and the MD5SUM_x86_64 fields in flashplayer-plugin.info (version 11.2.202.442) are both empty. Regards, Kees Theunissen. -- Kees Theunissen, System and network manager, Tel: +31 (0)30 6096724 Dutch Institute For Fundamental Energy Research (DIFFER) e-mail address: C.J.Theunissen at differ.nl postal address: PO Box 1207, 3430 BE Nieuwegein, NL visitors address: Edisonbaan 14, 3439 MN Nieuwegein, NL From willysr at slackbuilds.org Sun Feb 8 00:18:45 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 08 Feb 2015 07:18:45 +0700 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): MD5 checksums missing in .info file. In-Reply-To: References: Message-ID: <54D6AB65.9090309@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The MD5SUM and the MD5SUM_x86_64 fields in flashplayer-plugin.info > (version 11.2.202.442) are both empty. I have mention it when i published the public update notification Robby has fixed it on his branch as well yesterday http://slackbuilds.org/cgit/slackbuilds/commit/?h=rworkman&id=19f70f59ad5212b2d0e238ec4445045220b8f539 - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTWq2UACgkQiHuDdNczM4Gv/gCfdd/5Cn9LdTdCrbzpfEp7YaN5 O9YAoIWwQrR3RwG7V9X661eLwf7Ra+6C =c5D7 -----END PGP SIGNATURE----- From enigma77 at gmx.net Sun Feb 8 12:41:17 2015 From: enigma77 at gmx.net (enigma) Date: Sun, 08 Feb 2015 13:41:17 +0100 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild Message-ID: <4427917.Ro0h01d4eq@slackware> Hello, i got errors by sbopkg as i try to upgrade the flashplayer-plugin to version 11.2.202.442. Then I try to upgrade the Software manually and get this error-message: $ tar -xvzf flashplayer-plugin.tar.gz gzip: stdin: not in gzip format tar: Child returned status 1 tar: Error is not recoverable: exiting now And last, i extract the slackbuild with dolphins integrated unpackager and upgrade it successfully. Wether the error was made by sbopkg, tar or the slackbuild, i can not say. Maybe it is helpful for anyone to know this. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Feb 8 13:53:14 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 08 Feb 2015 20:53:14 +0700 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild In-Reply-To: <4427917.Ro0h01d4eq@slackware> References: <4427917.Ro0h01d4eq@slackware> Message-ID: <54D76A4A.1050107@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Hello, i got errors by sbopkg as i try to upgrade the > flashplayer-plugin to version 11.2.202.442. > > Then I try to upgrade the Software manually and get this > error-message: > > $ tar -xvzf flashplayer-plugin.tar.gz > > gzip: stdin: not in gzip format tar: Child returned status 1 tar: > Error is not recoverable: exiting now > > > And last, i extract the slackbuild with dolphins integrated > unpackager and upgrade it successfully. Wether the error was made > by sbopkg, tar or the slackbuild, i can not say. works here tar xvf flashplayer-plugin.tar.gz flashplayer-plugin/ flashplayer-plugin/flashplayer-plugin.SlackBuild flashplayer-plugin/slack-desc flashplayer-plugin/README flashplayer-plugin/doinst.sh flashplayer-plugin/flashplayer-plugin.info - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTXakoACgkQiHuDdNczM4HdpwCfWIDnPZctFSd7ZoKwPgjks7YS 3gcAoKqim/ijYQN1H05NPh7/dgcC8MSb =qV+J -----END PGP SIGNATURE----- From mdhalstead at att.net Sun Feb 8 14:11:56 2015 From: mdhalstead at att.net (Mark Halstead) Date: Sun, 08 Feb 2015 09:11:56 -0500 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild In-Reply-To: <54D76A4A.1050107@slackbuilds.org> References: <4427917.Ro0h01d4eq@slackware> <54D76A4A.1050107@slackbuilds.org> Message-ID: <54D76EAC.2040501@att.net> Willy Sudiarto Raharjo wrote: > tar -xvzf flashplayer-plugin.tar.gz Interesting! The command enigma used fails for me as well. -xvzf fails while -xvf succeeds. From Jim.Diamond at acadiau.ca Sun Feb 8 14:06:35 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sun, 8 Feb 2015 10:06:35 -0400 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild In-Reply-To: <54D76A4A.1050107@slackbuilds.org> References: <4427917.Ro0h01d4eq@slackware> <54D76A4A.1050107@slackbuilds.org> Message-ID: <20150208140635.GC16007@jdiamond-nb> On Sun, Feb 8, 2015 at 20:53 (+0700), Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >> Hello, i got errors by sbopkg as i try to upgrade the >> flashplayer-plugin to version 11.2.202.442. >> Then I try to upgrade the Software manually and get this >> error-message: >> $ tar -xvzf flashplayer-plugin.tar.gz >> gzip: stdin: not in gzip format tar: Child returned status 1 tar: >> Error is not recoverable: exiting now >> And last, i extract the slackbuild with dolphins integrated >> unpackager and upgrade it successfully. Wether the error was made >> by sbopkg, tar or the slackbuild, i can not say. > works here > tar xvf flashplayer-plugin.tar.gz > flashplayer-plugin/ > flashplayer-plugin/flashplayer-plugin.SlackBuild > flashplayer-plugin/slack-desc > flashplayer-plugin/README > flashplayer-plugin/doinst.sh > flashplayer-plugin/flashplayer-plugin.info On a related note, # sboupgrade flashplayer-plugin flashplayer-plugin (flash plugin for web browsers) Proceed with flashplayer-plugin? [y]: flashplayer-plugin added to upgrade queue. Upgrade queue: flashplayer-plugin Are you sure you wish to continue? [y]: Unable to download/verify source file(s) for flashplayer-plugin: Unable to get download info from /usr/sbo/multimedia/flashplayer-plugin/flashplayer-plugin.info Do you want to proceed? [n] Failures: flashplayer-plugin: Unable to get download info from /usr/sbo/multimedia/flashplayer-plugin/flashplayer-plugin.info I'm not sure what's up with that, but I'll note that when I used my own "download and install or upgrade" script, it worked fine. Jim From willysr at slackbuilds.org Sun Feb 8 14:46:06 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 08 Feb 2015 21:46:06 +0700 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild In-Reply-To: <54D76EAC.2040501@att.net> References: <4427917.Ro0h01d4eq@slackware> <54D76A4A.1050107@slackbuilds.org> <54D76EAC.2040501@att.net> Message-ID: <54D776AE.7060808@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Interesting! The command enigma used fails for me as well. -xvzf > fails while -xvf succeeds. that's probaby when i generate the tarball manually, i don't use -z i used tar cvf, not tar czvf it should be fixed in the next public update - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEUEARECAAYFAlTXdq4ACgkQiHuDdNczM4GNHgCdGxFzMUfqGdDUo7eFxLt5zW8n zLcAl35dCdk0w5Pl9q4jP874CxKo7Lw= =aWje -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sun Feb 8 14:56:08 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 08 Feb 2015 21:56:08 +0700 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild In-Reply-To: <20150208140635.GC16007@jdiamond-nb> References: <4427917.Ro0h01d4eq@slackware> <54D76A4A.1050107@slackbuilds.org> <20150208140635.GC16007@jdiamond-nb> Message-ID: <54D77908.8000909@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > # sboupgrade flashplayer-plugin > > flashplayer-plugin (flash plugin for web browsers) > > Proceed with flashplayer-plugin? [y]: flashplayer-plugin added to > upgrade queue. > > Upgrade queue: flashplayer-plugin > > Are you sure you wish to continue? [y]: Unable to download/verify > source file(s) for flashplayer-plugin: Unable to get download info > from > /usr/sbo/multimedia/flashplayer-plugin/flashplayer-plugin.info > > Do you want to proceed? [n] Failures: flashplayer-plugin: Unable to > get download info from > /usr/sbo/multimedia/flashplayer-plugin/flashplayer-plugin.info > > > > I'm not sure what's up with that, but I'll note that when I used > my own "download and install or upgrade" script, it worked fine. probaby due to missing MD5SUM values it has been fixed and it will be fine in the next update - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTXeQgACgkQiHuDdNczM4EHOwCgnU/TMOgNhummGriArlzHBEw7 MA0An1eSnpjLH2jc9WdYIYc7Pwp6SZWY =dD8k -----END PGP SIGNATURE----- From enigma77 at gmx.net Sun Feb 8 16:54:22 2015 From: enigma77 at gmx.net (enigma) Date: Sun, 08 Feb 2015 17:54:22 +0100 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild In-Reply-To: <54D76EAC.2040501@att.net> References: <4427917.Ro0h01d4eq@slackware> <54D76A4A.1050107@slackbuilds.org> <54D76EAC.2040501@att.net> Message-ID: <15670011.XaDU4y5NfF@slackware> Am Sonntag, 8. Februar 2015, 09:11:56 schrieb Mark Halstead: > Willy Sudiarto Raharjo wrote: > > tar -xvzf flashplayer-plugin.tar.gz > Interesting! The command enigma used fails for me as well. -xvzf fails > while -xvf succeeds. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > I have now tried it with tar -xvf flashplayer-plugin.tar.gz and it works for me too. Really strange! -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jim.Diamond at acadiau.ca Sun Feb 8 17:13:55 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sun, 8 Feb 2015 13:13:55 -0400 Subject: [Slackbuilds-users] flashplayer-plugin (11.2.202.442): Upgrade-Problems by unpacking the Slackbuild In-Reply-To: <15670011.XaDU4y5NfF@slackware> References: <4427917.Ro0h01d4eq@slackware> <54D76A4A.1050107@slackbuilds.org> <54D76EAC.2040501@att.net> <15670011.XaDU4y5NfF@slackware> Message-ID: <20150208171355.GA31273@jdiamond-nb> On Sun, Feb 8, 2015 at 17:54 (+0100), enigma wrote: > Am Sonntag, 8. Februar 2015, 09:11:56 schrieb Mark Halstead: >> Willy Sudiarto Raharjo wrote: >>> tar -xvzf flashplayer-plugin.tar.gz >> Interesting! The command enigma used fails for me as well. -xvzf fails >> while -xvf succeeds. >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ > I have now tried it with > tar -xvf flashplayer-plugin.tar.gz > and it works for me too. Really strange! I guess it depends whether you find it strange that a non-compressed tar file ends in .gz or whether tar complains about using 'z' with a non-compressed file. :-) Jim From willysr at slackbuilds.org Sun Feb 8 17:32:40 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 09 Feb 2015 00:32:40 +0700 Subject: [Slackbuilds-users] Updates - 20150208.1 Message-ID: <54D79DB8.5040501@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 NOTE: This update should fix a bug when user is updating using previous update of flashplayer-plugin since MD5SUM were missing or the tarball is not generated properly. Sun Feb 8 17:24:21 UTC 2015 academic/gwyddion: Updated for version 2.40. audio/audacious-aac: Added (AAC Decoder Plugin). audio/audacious-cue: Added (Cue Sheet Plugin). desktop/cwm: Updated for version 5.6. desktop/plasma-adjustable-clock: Added (Adjustable Clock). development/arduino: Fix source download urls libraries/LucenePlusPlus: Updated for version 3.0.7. libraries/barry: Maintainer + minor fixes libraries/libtorrent: Remove unneeded dependency. multimedia/flashplayer-plugin: Insert MD5SUM lines in .info file multimedia/gpodder: Updated for version 3.8.3. network/squidGuard: Add missing patches. network/tornado: Updated for version 4.1. network/trojita: Updated for version 0.4.1. network/verlihub: Maintainer + minor fixes perl/perl-AppConfig: Updated for version 1.68. perl/perl-Net-Pcap: Remove test. system/efitools: Added (Tools for manipulating UEFI secure boot). system/fish: Update HOMEPAGE url. system/sbsigntools: Added (Signing utility for UEFI Secure Boot). +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTXnbgACgkQiHuDdNczM4Ef6ACdGZE37OnuxoqgCkLKyqHiA6J2 LJcAn04xLX5sSm8BN7wkJ3OoHXQNwY4L =lRg/ -----END PGP SIGNATURE----- From slackbuilds at rochefort.de Sun Feb 8 17:46:34 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sun, 08 Feb 2015 18:46:34 +0100 Subject: [Slackbuilds-users] Arduino Slackbuild: Broken Link Message-ID: <54D7A0FA.8090405@rochefort.de> Hi just subscribed to report that the links to the sources in the Arduino Slackbuild for 14.1 seem broken: http://slackbuilds.org/repository/14.1/development/arduino/ The current links are: http://downloads-01.arduino.cc/arduino-1.0.6-linux32.tgz http://downloads-01.arduino.cc/arduino-1.0.6-linux64.tgz They both give me 404 Not Found Unless I am missing something the correct links should be: http://arduino.cc/download.php?f=/arduino-1.0.6-linux32.tgz http://arduino.cc/download.php?f=/arduino-1.0.6-linux64.tgz Regards Enguerrand From willysr at slackbuilds.org Sun Feb 8 17:51:23 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 09 Feb 2015 00:51:23 +0700 Subject: [Slackbuilds-users] Arduino Slackbuild: Broken Link In-Reply-To: <54D7A0FA.8090405@rochefort.de> References: <54D7A0FA.8090405@rochefort.de> Message-ID: <54D7A21B.3040105@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > just subscribed to report that the links to the sources in the > Arduino Slackbuild for 14.1 seem broken: > > http://slackbuilds.org/repository/14.1/development/arduino/ > > The current links are: > http://downloads-01.arduino.cc/arduino-1.0.6-linux32.tgz > http://downloads-01.arduino.cc/arduino-1.0.6-linux64.tgz > > They both give me 404 Not Found Unless I am missing something the > correct links should be: > > http://arduino.cc/download.php?f=/arduino-1.0.6-linux32.tgz > http://arduino.cc/download.php?f=/arduino-1.0.6-linux64.tgz This has been fixed with the last public update in the last 5-10 minutes please refresh the page and the download link should be OK :) - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTXohsACgkQiHuDdNczM4FjAACeJ0T2xnhK+EA1KC3VA7ZgaqPO 1kIAoIFO45gjIUMS5Vq6WjsJUrLko5Tv =NKiY -----END PGP SIGNATURE----- From slackbuilds at rochefort.de Sun Feb 8 18:01:13 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sun, 08 Feb 2015 19:01:13 +0100 Subject: [Slackbuilds-users] Arduino Slackbuild: Broken Link In-Reply-To: <54D7A21B.3040105@slackbuilds.org> References: <54D7A0FA.8090405@rochefort.de> <54D7A21B.3040105@slackbuilds.org> Message-ID: <54D7A469.7010808@rochefort.de> Ok, perfect, it works! On 08.02.2015 18:51, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> just subscribed to report that the links to the sources in the >> Arduino Slackbuild for 14.1 seem broken: >> >> http://slackbuilds.org/repository/14.1/development/arduino/ >> >> The current links are: >> http://downloads-01.arduino.cc/arduino-1.0.6-linux32.tgz >> http://downloads-01.arduino.cc/arduino-1.0.6-linux64.tgz >> >> They both give me 404 Not Found Unless I am missing something the >> correct links should be: >> >> http://arduino.cc/download.php?f=/arduino-1.0.6-linux32.tgz >> http://arduino.cc/download.php?f=/arduino-1.0.6-linux64.tgz > > This has been fixed with the last public update in the last 5-10 minutes > please refresh the page and the download link should be OK :) > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlTXohsACgkQiHuDdNczM4FjAACeJ0T2xnhK+EA1KC3VA7ZgaqPO > 1kIAoIFO45gjIUMS5Vq6WjsJUrLko5Tv > =NKiY > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From audrius at neutrino.lt Sun Feb 8 18:10:58 2015 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sun, 8 Feb 2015 20:10:58 +0200 Subject: [Slackbuilds-users] pysetuptools 8 implements PEP 440 In-Reply-To: <20141222202117.GA24591@pc21.mareichelt.com> References: <20141222202117.GA24591@pc21.mareichelt.com> Message-ID: <20150208181058.GA14367@varna> On Mon, 2014-12-22 at 21:21:17 +0100, Markus Reichelt wrote: > just a heads-up wrt pysetuptools 8+ > > #tahoe-lafs on freenode: > setuptools 8 implements PEP 440 > PEP 440 makes the meaning of , change from "a bunch of > arbitrary confusing crap that PJE invented in the past" to "AND" > > related: > https://gist.github.com/kylemanna/a22e7c37e5ff1f9286c2 > > tl;dr: if you can, keep pysetuptools <8 I pushed updates for pysetuptools, pip and virtualenv latest versions. I feel that we waited long enough for things to settle down, and most of the issues related to PEP 440 should be solved either by setuptools devs (if there were any bugs in their code) or by upstream of other projects depending on setuptools. Regarding allmydata-tahoe, developers fixed version specifiers in their Git repo, but there doesn't seem to be any versions released with those fixes, so I extracted them into a patch (attached). It works for me with setuptools 12.0.5, but I only installed allmydata-tahoe and tried to run "tahoe --version", so please test it and see if everything works correctly. For other maintainers of packages depending on setuptools: if your package won't build with latest setuptools, see if there's newer version released. If there isn't, read PEP 440 version specifier section[*] and try fixing it yourself, it's not very complicated. Although in most cases I expect that everything will work as before. [*] https://www.python.org/dev/peps/pep-0440/#version-specifiers -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From audrius at neutrino.lt Sun Feb 8 18:13:37 2015 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sun, 8 Feb 2015 20:13:37 +0200 Subject: [Slackbuilds-users] pysetuptools 8 implements PEP 440 In-Reply-To: <20150208181058.GA14367@varna> References: <20141222202117.GA24591@pc21.mareichelt.com> <20150208181058.GA14367@varna> Message-ID: <20150208181337.GB14367@varna> On Sun, 2015-02-08 at 20:10:58 +0200, Audrius Ka?ukauskas wrote: > Regarding allmydata-tahoe, developers fixed version specifiers in their > Git repo, but there doesn't seem to be any versions released with those > fixes, so I extracted them into a patch (attached). It works for me > with setuptools 12.0.5, but I only installed allmydata-tahoe and tried > to run "tahoe --version", so please test it and see if everything works > correctly. Oops, forgot to attach a patch. -- Audrius Ka?ukauskas http://neutrino.lt/ -------------- next part -------------- diff -uar allmydata-tahoe-1.10.0.orig/src/allmydata/_auto_deps.py allmydata-tahoe-1.10.0/src/allmydata/_auto_deps.py --- allmydata-tahoe-1.10.0.orig/src/allmydata/_auto_deps.py 2013-05-01 20:32:45.000000000 +0300 +++ allmydata-tahoe-1.10.0/src/allmydata/_auto_deps.py 2015-02-08 17:56:20.583096384 +0200 @@ -16,7 +16,7 @@ # zope.interface >= 3.6.0 is required for Twisted >= 12.1.0. # zope.interface 3.6.3 and 3.6.4 are incompatible with Nevow (#1435). - "zope.interface == 3.6.0, == 3.6.1, == 3.6.2, >= 3.6.5", + "zope.interface >= 3.6.0, != 3.6.3, != 3.6.4", # * On Windows we need at least Twisted 9.0 to avoid an indirect # dependency on pywin32. @@ -55,7 +55,7 @@ # Needed for SFTP. pyasn1 is needed by twisted.conch in Twisted >= 9.0. # pycrypto 2.2 doesn't work due to https://bugs.launchpad.net/pycrypto/+bug/620253 # pycrypto 2.4 doesn't work due to https://bugs.launchpad.net/pycrypto/+bug/881130 - "pycrypto == 2.1.0, == 2.3, >= 2.4.1", + "pycrypto >= 2.1.0, != 2.2, != 2.4", "pyasn1 >= 0.0.8a", # http://www.voidspace.org.uk/python/mock/ , 0.8.0 provides "call" -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From kingbeowulf at gmail.com Sun Feb 8 21:13:47 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 08 Feb 2015 13:13:47 -0800 Subject: [Slackbuilds-users] Update: Nvidia driver status Message-ID: <54D7D18B.7090408@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Some updates and changes to the proprietary nvidia drivers: *SUPPORTED* - ----------- nvidia-{driver | kernel} = 346.xx long lived branch nvidia-legacy340 = 340.xx legacy series nvidia-legacy304 = 304.xx legacy series *END OF LIFE* - ------------- nvidia-legacy173 2013.12.6 xorg-server<=1.15 nvidia-legacy96 2012.09.17 xorg-server<=1.12 I only have time to support 2 legacy branches, as well as no longer having any GPUs this old. Slackware-14.1 now uses xorg-server-1.14.3 - ------------- I will not submit a final update to nvidia-legacy173 (173.14.39) unless requested. The current slackbuilds (173.14.38) "should" work with just a version change edit. You should run at least nvidia-legacy304 for GPUs from the 6-series and newer. Please review the supported GPU list on www.nvidia.com. I will submit updates later today. Have fun, Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTX0YoACgkQXvwMaW61dLcpCQCeIYBkUhercFMpx9YY5leChBAH 31kAn0U6v3ZkFA3LsASuiV5SrdcgbD+k =pNEA -----END PGP SIGNATURE----- From karl.gustav.roksund at pearson.com Mon Feb 9 12:52:13 2015 From: karl.gustav.roksund at pearson.com (=?UTF-8?Q?R=C3=B8ksund=2C_Karl_Gustav?=) Date: Mon, 9 Feb 2015 13:52:13 +0100 Subject: [Slackbuilds-users] Bug in Slack <--> IRC link Message-ID: Hello! If you do @channel in slack you guys send a message to the users connected via IRC that look something like this: *`@channel*: some fancy channel message [cc: nickname]` but the problem is that ] is a valid nick character, so the IRC clients don't highlight the mention :-( The fix for this problem would of course just be to add a space between the nickname and the ] so the message would become: *`@channel*: some fancy channel message [cc: nickname ]` -- Karl Gustav R?ksund Programmer Fronter - fronter.com E: karl.gustav.roksund at pearson.com M: +47 47 64 52 00 Pearson - Always Learning -------------- next part -------------- An HTML attachment was scrubbed... URL: From agianson at gmail.com Tue Feb 10 01:30:18 2015 From: agianson at gmail.com (Alan Ianson) Date: Mon, 9 Feb 2015 17:30:18 -0800 Subject: [Slackbuilds-users] Slim Message-ID: <20150209173018.1bc40019@slackware.localhost> Hi! I am trying to build slim from slackbuilds.org and am getting an error.. /usr/include/X11/Xft/Xft.h:39:22: fatal error: ft2build.h: No such file or directory #include ^ compilation terminated. make[2]: *** [CMakeFiles/libslim.dir/panel.cpp.o] Error 1 make[2]: Leaving directory `/tmp/SBo/slim-1.3.6/build' make[1]: *** [CMakeFiles/libslim.dir/all] Error 2 make[1]: Leaving directory `/tmp/SBo/slim-1.3.6/build' make: *** [all] Error 2 Looks like it can't find ft2build.h. I did build slim a month or two ago successfully but when I run slim I get messages on the console something about init? respawning to fast so I was hoping to try it again. The last time I built slim I was running a stock install of slackware64 14.1. At the moment I have the patches installed with slackpkg. I wonder if that changed something?? Searching with google I see a few posts about the respawning but I didn't see any solution. Any help would be appreciated. From willysr at slackbuilds.org Tue Feb 10 01:38:08 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 10 Feb 2015 08:38:08 +0700 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150209173018.1bc40019@slackware.localhost> References: <20150209173018.1bc40019@slackware.localhost> Message-ID: <54D96100.4060506@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I am trying to build slim from slackbuilds.org and am getting an > error.. > > /usr/include/X11/Xft/Xft.h:39:22: fatal error: ft2build.h: No such > file or directory #include ^ compilation terminated. > make[2]: *** [CMakeFiles/libslim.dir/panel.cpp.o] Error 1 make[2]: > Leaving directory `/tmp/SBo/slim-1.3.6/build' make[1]: *** > [CMakeFiles/libslim.dir/all] Error 2 make[1]: Leaving directory > `/tmp/SBo/slim-1.3.6/build' make: *** [all] Error 2 > > Looks like it can't find ft2build.h. I did build slim a month or > two ago successfully but when I run slim I get messages on the > console something about init? respawning to fast so I was hoping to > try it again. > > The last time I built slim I was running a stock install of > slackware64 14.1. At the moment I have the patches installed with > slackpkg. I wonder if that changed something?? > > Searching with google I see a few posts about the respawning but I > didn't see any solution. Any help would be appreciated. did you installed the latest freetype-2.5.5 update? ft2build.h is part of freetype package - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTZYP8ACgkQiHuDdNczM4G6AQCfSUWpqlpSVVJ2FDadYYJM7GIG NOAAn1D4Sng+iy9k2cZv9iFrDfPk1plh =m7uH -----END PGP SIGNATURE----- From agianson at gmail.com Tue Feb 10 01:44:00 2015 From: agianson at gmail.com (Alan Ianson) Date: Mon, 9 Feb 2015 17:44:00 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: <54D96100.4060506@slackbuilds.org> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> Message-ID: <20150209174400.6e0a98d1@slackware.localhost> On Tue, 10 Feb 2015 08:38:08 +0700 Willy wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I am trying to build slim from slackbuilds.org and am getting an > > error.. > > > > /usr/include/X11/Xft/Xft.h:39:22: fatal error: ft2build.h: No such > > file or directory #include ^ compilation terminated. > > make[2]: *** [CMakeFiles/libslim.dir/panel.cpp.o] Error 1 make[2]: > > Leaving directory `/tmp/SBo/slim-1.3.6/build' make[1]: *** > > [CMakeFiles/libslim.dir/all] Error 2 make[1]: Leaving directory > > `/tmp/SBo/slim-1.3.6/build' make: *** [all] Error 2 > > > > Looks like it can't find ft2build.h. I did build slim a month or > > two ago successfully but when I run slim I get messages on the > > console something about init? respawning to fast so I was hoping to > > try it again. > > > > The last time I built slim I was running a stock install of > > slackware64 14.1. At the moment I have the patches installed with > > slackpkg. I wonder if that changed something?? > > > > Searching with google I see a few posts about the respawning but I > > didn't see any solution. Any help would be appreciated. > > did you installed the latest freetype-2.5.5 update? > ft2build.h is part of freetype package Yes, I just had a look in pkgtool and my version of freetype is 2.5.5. There is also a freetype-compat32 package from alien's multilib but I don't think that would cause a problem?. From willysr at slackbuilds.org Tue Feb 10 01:57:25 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 10 Feb 2015 08:57:25 +0700 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150209174400.6e0a98d1@slackware.localhost> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> Message-ID: <54D96585.4020909@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Yes, I just had a look in pkgtool and my version of freetype is > 2.5.5. > > There is also a freetype-compat32 package from alien's multilib but > I don't think that would cause a problem?. You are running multilib? have you updated the freetype-compat32 package as well? - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTZZYUACgkQiHuDdNczM4HD3QCdG9n+//LdifoAgx4oZTsm4w9x 2Z8AoJleby/jaE9T9j0WCEEPWKHKN12p =dekD -----END PGP SIGNATURE----- From agianson at gmail.com Tue Feb 10 02:09:21 2015 From: agianson at gmail.com (Alan Ianson) Date: Mon, 9 Feb 2015 18:09:21 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: <54D96585.4020909@slackbuilds.org> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> Message-ID: <20150209180921.1d766228@slackware.localhost> On Tue, 10 Feb 2015 08:57:25 +0700 Willy wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Yes, I just had a look in pkgtool and my version of freetype is > > 2.5.5. > > > > There is also a freetype-compat32 package from alien's multilib but > > I don't think that would cause a problem?. > > You are running multilib? Yes > have you updated the freetype-compat32 package as well? Yes, I just mirrored aliens site a couple days ago and installed it as he says on the multilib page. The compat32 version is also 2.5.5. From agianson at gmail.com Tue Feb 10 02:22:21 2015 From: agianson at gmail.com (Alan Ianson) Date: Mon, 9 Feb 2015 18:22:21 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: <54D96100.4060506@slackbuilds.org> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> Message-ID: <20150209182221.0f79cc1a@slackware.localhost> On Tue, 10 Feb 2015 08:38:08 +0700 Willy wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > I am trying to build slim from slackbuilds.org and am getting an > > error.. > > > > /usr/include/X11/Xft/Xft.h:39:22: fatal error: ft2build.h: No such > > file or directory #include ^ compilation terminated. > > make[2]: *** [CMakeFiles/libslim.dir/panel.cpp.o] Error 1 make[2]: > > Leaving directory `/tmp/SBo/slim-1.3.6/build' make[1]: *** > > [CMakeFiles/libslim.dir/all] Error 2 make[1]: Leaving directory > > `/tmp/SBo/slim-1.3.6/build' make: *** [all] Error 2 > > > > Looks like it can't find ft2build.h. I did build slim a month or > > two ago successfully but when I run slim I get messages on the > > console something about init? respawning to fast so I was hoping to > > try it again. > > > > The last time I built slim I was running a stock install of > > slackware64 14.1. At the moment I have the patches installed with > > slackpkg. I wonder if that changed something?? > > > > Searching with google I see a few posts about the respawning but I > > didn't see any solution. Any help would be appreciated. > > did you installed the latest freetype-2.5.5 update? > ft2build.h is part of freetype package I do have .. /usr/include/freetype2/ft2build.h and also a link in /usr/include/freetype that points to /usr/include/freetype2. From hba.nihilismus at gmail.com Tue Feb 10 02:23:27 2015 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Mon, 9 Feb 2015 20:23:27 -0600 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150209180921.1d766228@slackware.localhost> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> Message-ID: The last week i tried to build Slim and have to use a patch [1], maybe you could give a try. [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup - Cheers On Mon, Feb 9, 2015 at 8:09 PM, Alan Ianson wrote: > On Tue, 10 Feb 2015 08:57:25 +0700 > Willy wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > Yes, I just had a look in pkgtool and my version of freetype is > > > 2.5.5. > > > > > > There is also a freetype-compat32 package from alien's multilib but > > > I don't think that would cause a problem?. > > > > You are running multilib? > > Yes > > > have you updated the freetype-compat32 package as well? > > Yes, I just mirrored aliens site a couple days ago and installed it as > he says on the multilib page. The compat32 version is also 2.5.5. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- 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 agianson at gmail.com Tue Feb 10 02:31:40 2015 From: agianson at gmail.com (Alan Ianson) Date: Mon, 9 Feb 2015 18:31:40 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> Message-ID: <20150209183140.5a24b470@slackware.localhost> On Mon, 9 Feb 2015 20:23:27 -0600 Antonio wrote: > The last week i tried to build Slim and have to use a patch [1], > maybe you could give a try. > > [1] > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup Will do, thanks! From ryan.q at linux.com Tue Feb 10 02:40:56 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 9 Feb 2015 18:40:56 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150209183140.5a24b470@slackware.localhost> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> Message-ID: >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > Will do, thanks! If this works, let David Spencer know to incorporate it. He is taking over slim. Thanks for the help everyone! -- --- From agianson at gmail.com Tue Feb 10 02:44:09 2015 From: agianson at gmail.com (Alan Ianson) Date: Mon, 9 Feb 2015 18:44:09 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> Message-ID: <20150209184409.605b40c3@slackware.localhost> On Mon, 9 Feb 2015 18:40:56 -0800 Ryan wrote: > >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > > > Will do, thanks! > > If this works, let David Spencer > know to incorporate it. He is taking over slim. Thanks for the help > everyone! > That is good news. I've hoping that slim wouldn't slip away. Will do. From agianson at gmail.com Tue Feb 10 03:19:26 2015 From: agianson at gmail.com (Alan Ianson) Date: Mon, 9 Feb 2015 19:19:26 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> Message-ID: <20150209191926.10b7d51c@slackware.localhost> On Mon, 9 Feb 2015 18:40:56 -0800 Ryan wrote: > >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > > > Will do, thanks! > > If this works, let David Spencer > know to incorporate it. He is taking over slim. Thanks for the help > everyone! > I grabbed this patch and added it to the slim.SlackBuild and now it builds and packages fine. I am still getting this on my console though.. Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... INIT: Id "x1" respawning too fast: disabled for 5 minites This repeats every 5 minutes. From duncan_roe at acslink.net.au Tue Feb 10 20:45:11 2015 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Wed, 11 Feb 2015 07:45:11 +1100 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150209191926.10b7d51c@slackware.localhost> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> <20150209191926.10b7d51c@slackware.localhost> Message-ID: <20150210204511.GA2617@dimstar.local.net> On Mon, Feb 09, 2015 at 07:19:26PM -0800, Alan Ianson wrote: > On Mon, 9 Feb 2015 18:40:56 -0800 > Ryan wrote: > > > >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > > > > > Will do, thanks! > > > > If this works, let David Spencer > > know to incorporate it. He is taking over slim. Thanks for the help > > everyone! > > > > I grabbed this patch and added it to the slim.SlackBuild and now it > builds and packages fine. > > I am still getting this on my console though.. > > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > Starting up X11 session manager... > INIT: Id "x1" respawning too fast: disabled for 5 minites > > This repeats every 5 minutes. > _______________________________________________ > That's normal init behaviour if a process that it starts crashes immediately. Suggest you start it manually and debug, Cheers ... Duncan. From agianson at gmail.com Wed Feb 11 06:19:41 2015 From: agianson at gmail.com (Alan Ianson) Date: Tue, 10 Feb 2015 22:19:41 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150210204511.GA2617@dimstar.local.net> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> <20150209191926.10b7d51c@slackware.localhost> <20150210204511.GA2617@dimstar.local.net> Message-ID: <20150210221941.7fd4291e@slackware.localhost> On Wed, 11 Feb 2015 07:45:11 +1100 Duncan wrote: > On Mon, Feb 09, 2015 at 07:19:26PM -0800, Alan Ianson wrote: > > On Mon, 9 Feb 2015 18:40:56 -0800 > > Ryan wrote: > > > > > >> http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > > > > > > > Will do, thanks! > > > > > > If this works, let David Spencer > > > know to incorporate it. He is taking over slim. Thanks for the > > > help everyone! > > > > > > > I grabbed this patch and added it to the slim.SlackBuild and now it > > builds and packages fine. > > > > I am still getting this on my console though.. > > > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > Starting up X11 session manager... > > INIT: Id "x1" respawning too fast: disabled for 5 minites > > > > This repeats every 5 minutes. > > _______________________________________________ > > > That's normal init behaviour if a process that it starts crashes > immediately. Suggest you start it manually and debug, Slim is up and running normally but the init system doesn't seem to know that. I'll keep looking.. From philip at vd-hoeven.nl Wed Feb 11 08:11:31 2015 From: philip at vd-hoeven.nl (Philip van der Hoeven) Date: Wed, 11 Feb 2015 09:11:31 +0100 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150210221941.7fd4291e@slackware.localhost> References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> <20150209191926.10b7d51c@slackware.localhost> <20150210204511.GA2617@dimstar.local.net> <20150210221941.7fd4291e@slackware.localhost> Message-ID: On 11-02-2015 07:19, Alan Ianson wrote: > On Wed, 11 Feb 2015 07:45:11 +1100 > Duncan wrote: > On Mon, Feb 09, 2015 at 07:19:26PM -0800, Alan Ianson wrote: On Mon, 9 Feb 2015 18:40:56 -0800 Ryan wrote: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup [1] Will do, thanks! If this works, let David Spencer know to incorporate it. He is taking over slim. Thanks for the help everyone! I grabbed this patch and added it to the slim.SlackBuild and now it builds and packages fine. I am still getting this on my console though.. Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... Starting up X11 session manager... INIT: Id "x1" respawning too fast: disabled for 5 minites This repeats every 5 minutes. _______________________________________________ That's normal init behaviour if a process that it starts crashes immediately. Suggest you start it manually and debug, Slim is up and running normally but the init system doesn't seem to know that. I'll keep looking.. What is your slim start command ? Perhaps you forgot 'exec' (without the qoutes) in front of it ? Philip Links: ------ [1] http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup -------------- next part -------------- An HTML attachment was scrubbed... URL: From duncan_roe at acslink.net.au Wed Feb 11 20:50:44 2015 From: duncan_roe at acslink.net.au (Duncan Roe) Date: Thu, 12 Feb 2015 07:50:44 +1100 Subject: [Slackbuilds-users] Slim In-Reply-To: References: <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> <20150209191926.10b7d51c@slackware.localhost> <20150210204511.GA2617@dimstar.local.net> <20150210221941.7fd4291e@slackware.localhost> Message-ID: <20150211205044.GA2629@dimstar.local.net> On Wed, Feb 11, 2015 at 09:11:31AM +0100, Philip van der Hoeven wrote: > > > On 11-02-2015 07:19, Alan Ianson wrote: > > > On Wed, 11 Feb 2015 07:45:11 +1100 > > Duncan wrote: > > On Mon, Feb 09, 2015 at 07:19:26PM -0800, Alan Ianson wrote: On Mon, 9 Feb 2015 18:40:56 -0800 Ryan wrote: http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup [1] Will do, thanks! > If this works, let David Spencer know > to incorporate it. He is taking over slim. Thanks for the help everyone! > I grabbed this patch and added it to the slim.SlackBuild and now it > builds and packages fine. I am still getting this on my console though.. > Starting up X11 session manager... Starting up X11 session manager... > Starting up X11 session manager... Starting up X11 session manager... > Starting up X11 session manager... Starting up X11 session manager... > Starting up X11 session manager... Starting up X11 session manager... > Starting up X11 session manager... Starting up X11 session manager... > INIT: Id "x1" respawning too fast: disabled for 5 minites This repeats > every 5 minutes. _______________________________________________ That's > normal init behaviour if a process that it starts crashes immediately. > Suggest you start it manually and debug, > > Slim is up and running normally but the init system doesn't seem to > know that. I'll keep looking.. > > What is your slim start command ? Perhaps you forgot 'exec' (without the > qoutes) in front of it ? > > Philip > > Links: > ------ > [1] > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup OTOH, you would get this scenario if you had an ampersand on the end of the init line (and had respawn). The actual command that init starts terminates, so init attempts the respawn. Presumably, the second (backgrounded server) instance fails to start in this case. Leading on from that, might something other than init have started the server? Then init would not be able to start it. To check this: kill the server and see if init now settles down having restarted it. Cheers ... Duncan. From agianson at gmail.com Thu Feb 12 03:19:25 2015 From: agianson at gmail.com (Alan Ianson) Date: Wed, 11 Feb 2015 19:19:25 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: References: <20150209173018.1bc40019@slackware.localhost> <54D96100.4060506@slackbuilds.org> <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> <20150209191926.10b7d51c@slackware.localhost> <20150210204511.GA2617@dimstar.local.net> <20150210221941.7fd4291e@slackware.localhost> Message-ID: <20150211191925.0ad676def5305feedb710a8d@gmail.com> On Wed, 11 Feb 2015 09:11:31 +0100 Philip van der Hoeven wrote: > > > On 11-02-2015 07:19, Alan Ianson wrote: > > > On Wed, 11 Feb 2015 07:45:11 +1100 > > Duncan wrote: > > On Mon, Feb 09, 2015 at 07:19:26PM -0800, Alan Ianson wrote: On > > Mon, 9 Feb 2015 18:40:56 -0800 Ryan wrote: > > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > [1] Will do, thanks! > If this works, let David Spencer > know to incorporate it. He is taking over slim. Thanks for the help > everyone! I grabbed this patch and added it to the slim.SlackBuild > and now it builds and packages fine. I am still getting this on my > console though.. Starting up X11 session manager... Starting up X11 > session manager... Starting up X11 session manager... Starting up X11 > session manager... Starting up X11 session manager... Starting up X11 > session manager... Starting up X11 session manager... Starting up X11 > session manager... Starting up X11 session manager... Starting up X11 > session manager... INIT: Id "x1" respawning too fast: disabled for 5 > minites This repeats every 5 minutes. > _______________________________________________ That's normal init > behaviour if a process that it starts crashes immediately. Suggest > you start it manually and debug, > > Slim is up and running normally but the init system doesn't seem to > know that. I'll keep looking.. > > What is your slim start command ? Perhaps you forgot 'exec' (without > the qoutes) in front of it ? This is what I have in /etc/rc.d/rc.4. I commented out the echo line so at least I don't see that.. :) # Tell the viewers what's going to happen... # echo "Starting up X11 session manager..." # Try to use SLiM login manager. This comes first, because if SLiM is # installed, then the user probably wants to use it by default: if [ -x /usr/bin/slim ]; then exec /usr/bin/slim fi From agianson at gmail.com Thu Feb 12 03:36:15 2015 From: agianson at gmail.com (Alan Ianson) Date: Wed, 11 Feb 2015 19:36:15 -0800 Subject: [Slackbuilds-users] Slim In-Reply-To: <20150211205044.GA2629@dimstar.local.net> References: <20150209174400.6e0a98d1@slackware.localhost> <54D96585.4020909@slackbuilds.org> <20150209180921.1d766228@slackware.localhost> <20150209183140.5a24b470@slackware.localhost> <20150209191926.10b7d51c@slackware.localhost> <20150210204511.GA2617@dimstar.local.net> <20150210221941.7fd4291e@slackware.localhost> <20150211205044.GA2629@dimstar.local.net> Message-ID: <20150211193615.a4df0c72c82dfd69eb1646a2@gmail.com> On Thu, 12 Feb 2015 07:50:44 +1100 Duncan Roe wrote: > On Wed, Feb 11, 2015 at 09:11:31AM +0100, Philip van der Hoeven wrote: > > > > > > On 11-02-2015 07:19, Alan Ianson wrote: > > > > > On Wed, 11 Feb 2015 07:45:11 +1100 > > > Duncan wrote: > > > On Mon, Feb 09, 2015 at 07:19:26PM -0800, Alan Ianson wrote: On > > > Mon, 9 Feb 2015 18:40:56 -0800 Ryan wrote: > > > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > > [1] Will do, thanks! > > If this works, let David Spencer > > know to incorporate it. He is taking over slim. Thanks for the help > > everyone! I grabbed this patch and added it to the slim.SlackBuild > > and now it builds and packages fine. I am still getting this on my > > console though.. Starting up X11 session manager... Starting up X11 > > session manager... Starting up X11 session manager... Starting up > > X11 session manager... Starting up X11 session manager... Starting > > up X11 session manager... Starting up X11 session manager... > > Starting up X11 session manager... Starting up X11 session > > manager... Starting up X11 session manager... INIT: Id "x1" > > respawning too fast: disabled for 5 minites This repeats every 5 > > minutes. _______________________________________________ That's > > normal init behaviour if a process that it starts crashes > > immediately. Suggest you start it manually and debug, > > > > Slim is up and running normally but the init system doesn't seem to > > know that. I'll keep looking.. > > > > What is your slim start command ? Perhaps you forgot > > 'exec' (without the qoutes) in front of it ? > > > > Philip > > > > Links: > > ------ > > [1] > > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/x11-misc/slim/files/slim-1.3.6-freetype.patch?view=markup > > OTOH, you would get this scenario if you had an ampersand on the end > of the init line (and had respawn). The actual command that init > starts terminates, so init attempts the respawn. Presumably, the > second (backgrounded server) instance fails to start in this case. > > Leading on from that, might something other than init have started > the server? Then init would not be able to start it. To check this: > kill the server and see if init now settles down having restarted it. I don't think so. The only command that starts slim is in /etc/rc.d.rc.4. I just looked up slim in htop and terminated it and slim fired up again waiting for someone to log in. I'll keep an eye out if those respawn messages have gone away. Thanks.. :) From ryan.q at linux.com Thu Feb 12 21:34:53 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 12 Feb 2015 13:34:53 -0800 Subject: [Slackbuilds-users] openoffice.org build up for grabs Message-ID: Hey friends, I use LibreOffice most of the time these days, so if someone wants to take this over, I think they would do a better job of maintaining it. The build needs some work, and whoever wants to take it over I can send a patch to (it fixes some of the build issues, but still needs a little TLC). Thanks, Ryan -- --- From lacielacie at rocketmail.com Fri Feb 13 22:42:00 2015 From: lacielacie at rocketmail.com (KaMii) Date: Fri, 13 Feb 2015 14:42:00 -0800 Subject: [Slackbuilds-users] Qt 5.4.0, QTWebEngine and Pulseaudio In-Reply-To: References: <20150204193239.7adb3939@Andromdeda.andromeda.gal> Message-ID: <20150213144200.62b9847d@Andromdeda.andromeda.gal> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Larry, I finally got QTWebEngine to compile without pulseaudio. I am not sure if this will build on 14.1 or on stock -current. I have a later version of sqlite and PCRE, you can give this a shot and see if it will work. My bigest issue was getting around the ld.gold treating warnings as errors. Anyway you can find my script here: https://github.com/KaMiila/SlackBuilds/tree/master/qtwebengine On Thu, 5 Feb 2015 09:29:49 -0800 Larry Hajali wrote: > Hmmm...interesting. I took a look at the BLFS page for qt5. Thanks > for the link. > > I haven't tried compiling qtwebengine without pulseaudio, but the > link you sent says that it needs version of nss >= 3.17.3. Slackware > 14.1 and -current comes with mozilla-nss 3.16.5. qtwebengine is new > in qt5 5.4.0, so I didn't put much effort in compiling it into the > qt5.SlackBuild. > > Good luck, > --Larry > > On Wed, Feb 4, 2015 at 7:32 PM, KaMii > wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > I have been working on getting QTWebEngine to compile without > > pulseaudio and found a very helpful sed line which allows this. > > Yet I am having some later issues with the compile job. > > http://pastebin.com/gSLhPyek > > > > The sed lines I found here: > > http://www.linuxfromscratch.org/~krejzi/kblfs/x/qt5.html > > > > sed -e "$ a !contains(QT_CONFIG, pulseaudio): GYP_CONFIG += > > use_pulseaudio=0" \ > > -i qtwebengine/src/core/config/desktop_linux.pri > > > > The script I wrote and am using is here: > > > > https://github.com/KaMiila/SlackBuilds/blob/master/qtwebengine/qtwebengine.SlackBuild > > > > Ideally I would love to get a qt5 script that combines QTWebEngine > > without pulseaudio. I noticed the slackbuild for qt5 has the > > QTWebEngine disabled if you do not USEPULSE=yes prefix. I just > > wanted to pass on this sed line and perhaps it is useful for those > > that want QTWebEngine without pulseaudio? Furthermore, if you can > > get this to build without, what appears to be a compiler version > > issue, that I have yet to conquer, please let me know! > > > > - -KaMii > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1 > > > > iJwEAQECAAYFAlTS5FcACgkQkO84ARmAdEBdqQQAqw7d23WHJwUxQsBTSZkfXJ3O > > nBh5cC8YuOEzfbnpgbX91NDO2opX428NCSsAT3B2M8mj66gubay2fbFnvB5MtmDB > > 34eqWLhuM8sxxAeWM8Fo2hgTLD8CEd2ORlkhx5lJpGy9H4o9yhc9RE3KTAI2MIRv > > BAb+fgVqgjRSAaPzmws= > > =/icP > > -----END PGP SIGNATURE----- > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iJwEAQECAAYFAlTefbgACgkQkO84ARmAdEAZ3AP/bW+dYSYht4m9LypRv9vfBnBY Kg246USOtBoujIWU57zGFQKAlpnziCFv6cCciZjdGnfDXAYW/uqDyXuws1PmLHUM OdlsVwAc+7McNULjDwEYGB/XbnrlTPDJh8kwQ60wUYTZV0voir6EllcSjefa/5cZ A5QuI+u4tNgMvi9g5b8= =qSP/ -----END PGP SIGNATURE----- From mathieu.bouillaguet at gmail.com Sat Feb 14 12:28:25 2015 From: mathieu.bouillaguet at gmail.com (Mathieu Bouillaguet) Date: Sat, 14 Feb 2015 13:28:25 +0100 Subject: [Slackbuilds-users] docker build fail on x86_64 Message-ID: Hi, The current slackbuild fails on my slackare64-14.1 machine fully updated with : patching file daemon/graphdriver/btrfs/btrfs.go > Hunk #1 succeeded at 4 with fuzz 1. > # WARNING! I don't seem to be running in the Docker container. > # The result of this command might be an incorrect build, and will not be > # officially supported. > # > # Try this instead: make all > # > > ---> Making bundle: dynbinary (in bundles/1.4.1/dynbinary) > Created binary: > /tmp/SBo/docker-1.4.1/bundles/1.4.1/dynbinary/dockerinit-1.4.1 > # github.com/docker/docker/daemon/graphdriver/btrfs > ../package-docker/usr/share/gocode/src/ > github.com/docker/docker/daemon/graphdriver/btrfs/version.go:6:27: fatal > error: btrfs/version.h: No such file or directory > #include > ^ > compilation terminated. > It's not a full install but I don't think I am missing any dependency. On another 64 bits machine running current the slackbuild was also failing with the same error until the latest update of btrfs-progs which include the missing header file. See current changelog below : a/btrfs-progs-20141107-x86_64-1.txz: Upgraded. > Added the header files to the package. Thanks to Vincent Batts. > I am missing something or does the slackbuild requires this header ? Thanks for your help -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Feb 14 13:02:36 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 14 Feb 2015 20:02:36 +0700 Subject: [Slackbuilds-users] docker build fail on x86_64 In-Reply-To: References: Message-ID: <54DF476C.8000802@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The current slackbuild fails on my slackare64-14.1 machine fully > updated with : > > patching file daemon/graphdriver/btrfs/btrfs.go >> Hunk #1 succeeded at 4 with fuzz 1. # WARNING! I don't seem to be >> running in the Docker container. # The result of this command >> might be an incorrect build, and will not be # officially >> supported. # # Try this instead: make all # >> >> ---> Making bundle: dynbinary (in bundles/1.4.1/dynbinary) >> Created binary: >> /tmp/SBo/docker-1.4.1/bundles/1.4.1/dynbinary/dockerinit-1.4.1 # >> github.com/docker/docker/daemon/graphdriver/btrfs >> ../package-docker/usr/share/gocode/src/ >> github.com/docker/docker/daemon/graphdriver/btrfs/version.go:6:27: >> fatal error: btrfs/version.h: No such file or directory #include >> ^ compilation terminated. >> > > It's not a full install but I don't think I am missing any > dependency. > > On another 64 bits machine running current the slackbuild was also > failing with the same error until the latest update of btrfs-progs > which include the missing header file. See current changelog below > : > > a/btrfs-progs-20141107-x86_64-1.txz: Upgraded. >> Added the header files to the package. Thanks to Vincent Batts. >> > > I am missing something or does the slackbuild requires this header > ? Yes, i confirmed that it does indeed failed to build on -stable releases I have notified Pat and see if he agreed to add the missing header to - -stable release as well - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTfR2wACgkQiHuDdNczM4FocwCdFACVLrD1LhRWSCTgrt1Wud0h UQUAoJrDYs+PBMhyyBFMiwAU8vEKgt4i =6s5w -----END PGP SIGNATURE----- From hostmaster at slackonly.com Sat Feb 14 15:19:42 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sat, 14 Feb 2015 17:19:42 +0200 Subject: [Slackbuilds-users] atunes.SlackBuild Message-ID: <54DF678E.2090900@slackonly.com> Hi!, I notice atunes.SlackBuild and MusicMixer.SlackBuild package gets an "i486" architecture tag instead of "x86_64". comments on MusicMixer.SlackBuild: ARCH=i486 # hardcoded for 32bit Is this correct? Thanks. From matteo.bernardini at gmail.com Sat Feb 14 15:45:15 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 14 Feb 2015 16:45:15 +0100 Subject: [Slackbuilds-users] atunes.SlackBuild In-Reply-To: <54DF678E.2090900@slackonly.com> References: <54DF678E.2090900@slackonly.com> Message-ID: 2015-02-14 16:19 GMT+01:00 Panagiotis Nikolaou : > Hi!, > > I notice atunes.SlackBuild and MusicMixer.SlackBuild > package gets an "i486" architecture tag instead of "x86_64". > > comments on MusicMixer.SlackBuild: ARCH=i486 # hardcoded for 32bit > > Is this correct? MusicMixer is a 32bit only application: notice that the download link is broken, but you can find it here http://ponce.cc/slackware/sources/repo/MusicMixer_x86_1.8.tgz I will fix it in our git. atunes is a java application and should be architecture indipendent (ARCH=noarch): I'll fix that too. Thanks for reporting! Matteo From kingbeowulf at gmail.com Sat Feb 14 20:59:28 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 14 Feb 2015 12:59:28 -0800 Subject: [Slackbuilds-users] libreoffice help pack README Message-ID: <54DFB730.9040505@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 FYI, The README states that the default build is for the en-GB locale but the slackbuild script says LOLANG=${LOLANG:-en-US} which is also the locale or the download file. - -Ed -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTfty8ACgkQXvwMaW61dLc9DACgrVmL79O+HxU5UxZMF/L8MrOo Du8AnirlxiUYi4P1boTu+jn0IC6zHniG =e5WN -----END PGP SIGNATURE----- From slacker at slaphappygeeks.com Sat Feb 14 21:21:26 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sat, 14 Feb 2015 14:21:26 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case Message-ID: <54DFBC56.6080008@slaphappygeeks.com> I am writing a Slackdocs article for setting up a virtual mail server using Postfix, Dovecot and MySQL. In this use case we require a separate non-priv user/group for which the Dovecot documents suggest "vmail" ( http://wiki.dovecot.org/VirtualUsers ), and which I have used in my own implementation. This is purely a configuration option and is not required to build the Dovecot package. But it seems to me it is a common enough use case and that having an SBo assigned uid/gid for "vmail" would dovetail nicely with the dovecot docs and simplify virtual mail setup for those building with SBo scripts. It would also simplify my Slackdocs article. So, please consider this a request for either discussion or simply for an assigned uid/gid for a vmail user. Thanks! Robert From rshepard at appl-ecosys.com Sat Feb 14 23:21:46 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 14 Feb 2015 15:21:46 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type Message-ID: When I build postfix-2.11.3 (or the new -3.0.0) there is an error that prevents postfix from starting. In /usr/libexec/postfix/post-install, on line 504 the error message is '... test: too many arguments'. This did not happen in earlier versions and I've no idea how to fix it. Last Sunday I rebuilt and re-installed -2.11.3 from a fresh download of the postfix and SlackBuild files tarballs. The kludge that allowed me to get postfix working again was to comment out line 504 in /usr/libexec/postfix/post-install: # Flag obsolete objects. XXX Solaris 2..9 does not have "test -e". if [ -n "$obsolete_flag" ] then 504 -> #test -r $path -a "$type" != "d" && obsolete="$obsolete $path" continue; else keep_list="$keep_list $path" fi Both cyrus and dovecot are install here (latest versions from SBo). And this is another issue I'd like to resolve. When I build postfix with SASL=dovecot, trying to start postfix causes it to throttle and generate continuous error messages. Building postfix with SASL=cyrus produces a working set of tools. Installed here are dovecot-2.2.13-i486-1_SBo and qca-cyrus-sasl-2.0.0_beta3-i486-1. A week ago I wrote to the maintainer but have not received a reply. Resolving these two issues is important. Thanks in advance, Rich From yalhcru at gmail.com Sun Feb 15 00:05:29 2015 From: yalhcru at gmail.com (B Watson) Date: Sat, 14 Feb 2015 19:05:29 -0500 Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: Message-ID: On 2/14/15, Rich Shepard wrote: > 504 -> #test -r $path -a "$type" != "d" && obsolete="$obsolete $path" Probably it's better to put double-quotes around $path: test -r "$path" -a ...blahblah From rshepard at appl-ecosys.com Sun Feb 15 00:10:07 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 14 Feb 2015 16:10:07 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: Message-ID: On Sat, 14 Feb 2015, B Watson wrote: > On 2/14/15, Rich Shepard wrote: > >> 504 -> #test -r $path -a "$type" != "d" && obsolete="$obsolete $path" > > Probably it's better to put double-quotes around $path: > > test -r "$path" -a ...blahblah That does work. So, are the missing double quotes a postfix or slackbuilds error? Thanks for that lesson. Any thoughts on why specifying DASL=dovecot does not work here? Much appreciated, Rich From willysr at slackbuilds.org Sun Feb 15 00:34:24 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 15 Feb 2015 07:34:24 +0700 Subject: [Slackbuilds-users] libreoffice help pack README In-Reply-To: <54DFB730.9040505@gmail.com> References: <54DFB730.9040505@gmail.com> Message-ID: <54DFE990.3010909@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > FYI, The README states that the default build is for the en-GB > locale but the slackbuild script says > > LOLANG=${LOLANG:-en-US} > > which is also the locale or the download file. Thanks for spotting it It should be en-US for helppack and en-GB for langpack it will be fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTf6ZAACgkQiHuDdNczM4FynwCgiTUoJxZ8L8NDd0cEQjnZz4QX xd0AnijCGu53FAFgxy8PP6OR07iB5cge =6/PN -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sun Feb 15 00:42:23 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 15 Feb 2015 07:42:23 +0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54DFBC56.6080008@slaphappygeeks.com> References: <54DFBC56.6080008@slaphappygeeks.com> Message-ID: <54DFEB6F.4030906@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > So, please consider this a request for either discussion or simply > for an assigned uid/gid for a vmail user. please use 303 for vmail - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTf628ACgkQiHuDdNczM4EQLACfRzJaQM5YZlt5gHDmgRDtiGaf HM4An0oDoN4VoRhvfY153/+GNkkK+NyI =zxOh -----END PGP SIGNATURE----- From slacker at slaphappygeeks.com Sun Feb 15 00:47:09 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sat, 14 Feb 2015 17:47:09 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54DFEB6F.4030906@slackbuilds.org> References: <54DFBC56.6080008@slaphappygeeks.com> <54DFEB6F.4030906@slackbuilds.org> Message-ID: <54DFEC8D.2050807@slaphappygeeks.com> On 02/14/2015 05:42 PM, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> So, please consider this a request for either discussion or simply >> for an assigned uid/gid for a vmail user. > > please use 303 for vmail > Thanks! From willysr at slackbuilds.org Sun Feb 15 01:12:02 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 15 Feb 2015 08:12:02 +0700 Subject: [Slackbuilds-users] Updates - 20150215.1 Message-ID: <54DFF262.5030406@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sun Feb 15 00:58:28 UTC 2015 academic/GeoGebra: Updated for version 5.0.62.0. academic/Mnemosyne: Updated for version 2.3.1. academic/patsy: Added (statistical models). audio/MusicMixer: Fixed download link. audio/atunes: Set ARCH=noarch. desktop/insync-thunar: Updated for version 1.1.5.32051. desktop/plasma-eyasdp: Added (Enhanced yaSDP). desktop/seafile-gui: Updated for version 4.0.7. development/Bottleneck: Updated for version 1.0.0. development/SDL2_gfx: Updated for version 1.0.1. development/bpython: Updated for version 0.13.2. development/coccinelle: Updated for version 1.0.0-r24. development/codelite: Added (cross platform IDE). development/eagle: Updated for version 7.2.0 + new maintainer. development/kelbt: Fixed download link and homepage. development/mono2: Updated for version 2.10.9. development/mphidflash: Added (command-line tool). development/pandas: Updated for version 0.15.2. development/poedit: Updated for version 1.7.4. development/ragel: Updated for version 6.9. development/textadept: Updated for version 7.8 & fixed symlinks. development/tstoolbox: Updated for version 0.9.4. development/uemacs: Updated for version 20141208. games/galaxyv2: Updated for version 1.85. games/lutris: Add optional DEPS. games/mednafen: Updated for version 0.9.38.1. games/xspacewarp: New maintainer. gis/OWSLib: Updated for version 0.8.13. gis/geopy: Updated for version 1.9.0. graphics/brlcad: Updated for version 7.24.2 + new maintainer. graphics/fim: Updated for version 0.5. graphics/leocad: Fix shortcut. graphics/pngquant: Updated for version 2.3.4. graphics/pygraphviz: Updated for version 1.3rc2. graphics/qcad: Updated for version 3.8.1.0. libraries/gtkdatabox: Added (GTK+ widget). libraries/libmspack: Updated for version 0.5alpha. libraries/libtar: Updated for version 1.2.20 + new maintainer. libraries/libucil: Added (a functions library). libraries/libunicapgtk: Added (GTK Widget). libraries/live555: Updated for version 2015.02.10. libraries/pymdstat: Added (library to parse /proc/mdstat). libraries/stfl: Updated for version 0.24. libraries/tinyxml2: Updated for version 2.2.0. libraries/wxGTK: New maintainer. misc/vdpauinfo: Updated for version 0.9. multimedia/Mopidy: Updated for version 0.19.5. multimedia/beets: Updated for version 1.3.10. multimedia/picard-plugins: Updated for version 20150131. multimedia/plex-home-theater: Updated for version 1.3.6.441. multimedia/ucview: Added (video capture and display program). network/Pafy: Updated for version 0.3.72. network/bottle: Added (Python web framework). network/ccnet: Updated for version 4.0.6. network/dropbox: Updated for version 3.2.6. network/graphite-carbon: Copy README.SLACKWARE into doc dir. network/insync: Updated for version 1.1.5.32051. network/iojs: Updated for version 1.2.0. network/mps-youtube: Updated for version 0.2.2. network/owncloud-server: Updated for version 8.0.0. network/postfix: Updated for version 2.11.4. network/seafile-client: Updated for version 4.0.6. network/seahub: Updated for version 4.0.6. network/youtube-dl-server: Updated for version 0.1.2. office/MasterPDFEditor: Updated for version 2.2.15. office/TaskCoach: Updated for version 1.4.2. office/libreoffice-helppack: Fix README. office/lyx: Updated for version 2.1.3. office/taskjuggler: Added (Project Management). perl/perl-AppConfig: Updated for version 1.69. python/APScheduler: Updated for version 3.0.1. python/Paver: Updated for version 1.2.3. python/babelfish: Updated for version 0.5.4. python/clint: Updated for version 0.4.1. python/curtsies: Updated for version 0.1.18. python/flake8: Updated for version 2.3.0. python/guessit: Updated for version 0.10.1. python/hg-git: Updated for version 0.8.0. python/hgsubversion: Updated for version 1.8. python/invoke: Updated for version 0.9.0. python/jmespath: Updated for version 0.6.1. python/jsonschema: Updated for version 2.4.0. python/lxml: Updated for version 3.4.2. python/mando: Added (Create Python CLI apps). python/monty: Updated for version 0.6.3. python/msgpack-python: Updated for version 0.4.5. python/path.py: Updated for version 7.2. python/pep8: Updated for version 1.6.1. python/pip: Updated for version 6.0.8. python/psutil: Updated for version 2.2.1. python/pygrametl: Updated for version 2.3.2. python/pysetuptools: Updated for version 12.0.5. python/pytest-cov: Updated for version 1.8.1. python/pytest: Updated for version 2.6.4. python/python-certifi: Updated for version 14.05.14. python/python-oauthlib: Updated for version 0.7.2. python/python-twitter: Updated for version 2.2. python/selenium: Updated for version 2.44.0. python/sge-pygame: Updated for version 0.16. python/thunarx-python: Fixed VERSION. python/virtualenv: Updated for version 12.0.7. system/TLP: Updated for version 0.7. system/gitolite: Added (Hosting git repositories). system/glances: Update optional dependencies. system/inxi: Updated for version 2.2.18. system/iucode_tool: Added (Intel Processor Microcode Tool). system/mlterm: Updated for version 3.4.3. system/nvidia-driver: Updated for version 346.35. system/nvidia-kernel: Updated for version 346.35. system/nvidia-legacy304-driver: Updated for version 304.125. system/nvidia-legacy304-kernel: Updated for version 304.125. system/nvidia-legacy340-driver: Added (Binary Nvidia Video Driver). system/nvidia-legacy340-kernel: Added (Kernel Interface for nvidia). system/profile-cleaner: Updated for version 2.34. system/profile-sync-daemon: Updated for version 5.68. system/slim: Fix build for new freetype. system/slpkg: Updated for version 2.2.2. system/the_silver_searcher: Updated for version 0.29.1. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTf8mIACgkQiHuDdNczM4GE/gCfbZEkprum/pSg77eBe79K/iBh JJUAoJyvV3Z8KHsODopbtIrMAYKKLZiD =Wmrt -----END PGP SIGNATURE----- From rob0 at slackbuilds.org Sun Feb 15 02:36:39 2015 From: rob0 at slackbuilds.org (Rob McGee) Date: Sat, 14 Feb 2015 20:36:39 -0600 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54DFBC56.6080008@slaphappygeeks.com> References: <54DFBC56.6080008@slaphappygeeks.com> Message-ID: <20150215023639.GK23739@harrier.slackbuilds.org> On Sat, Feb 14, 2015 at 02:21:26PM -0700, Slacker wrote: > I am writing a Slackdocs article for setting up a virtual mail > server using Postfix, Dovecot and MySQL. > > In this use case we require a separate non-priv user/group > for which the Dovecot documents suggest "vmail" ( > http://wiki.dovecot.org/VirtualUsers ), and which I have used > in my own implementation. > > This is purely a configuration option and is not required to build > the Dovecot package. But it seems to me it is a common enough use > case and that having an SBo assigned uid/gid for "vmail" would > dovetail nicely with the dovecot docs and simplify virtual mail > setup for those building with SBo scripts. It would also simplify > my Slackdocs article. > > So, please consider this a request for either discussion or simply > for an assigned uid/gid for a vmail user. I never have understood why so many small-time users want to have "virtual mail accounts." What is the appeal? "Gee whiz, all I do when I add a domain is enter it in mysql." Well, uh, how often do you add domains? I can see it if you're a large scale hosting provider. Why is that so good if you're not? In the small-timer case, delivery to system accounts is far more powerful and flexible. You can keep all your mail in your $HOME; you're able to run commands on certain incoming mail; you have many more options for storing and sorting mail. Furthermore, it's considerably less secure to have all mail under a single UID/GID, as most of these virtual/mysql howtos seem to advocate. A compromise of that user means all mail is at risk. With system users, each recipient has her own UID, and compromises are limited. (Actually that can be done with virtual also; both Postfix and Dovecot support map lookups for the UID & GID. But few howtos -- if any? I don't think I have seen one -- show how this is done.) So my concern here is twofold: one, it promotes "virtual mail" to users who should not be using it; and two, it promotes the less secure means of doing it, under a single UID/GID. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From rob0 at slackbuilds.org Sun Feb 15 02:48:22 2015 From: rob0 at slackbuilds.org (Rob McGee) Date: Sat, 14 Feb 2015 20:48:22 -0600 Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: Message-ID: <20150215024822.GL23739@harrier.slackbuilds.org> On Sat, Feb 14, 2015 at 04:10:07PM -0800, Rich Shepard wrote: > Any thoughts on why specifying DASL=dovecot does not work here? While "DASL" is clearly a typo, no, it makes no sense that Postfix would have a compile-time problem with Dovecot SASL. In fact no linkage takes place. Postfix communicate with Dovecot SASL over a socket, and the SASL implementation is entirely internal on the Dovecot side. The compile-time setting merely enables the code in Postfix to communicate with that socket. One might ask, why do you need Cyrus SASL if you have Dovecot installed? Typically you do not; only in the less usual case of Postfix having to authenticate at an upstream relay, would Cyrus become necessary. All the details are here: http://www.postfix.org/SASL_README.html -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From mario at slackware.hr Sun Feb 15 03:19:40 2015 From: mario at slackware.hr (Mario Preksavec) Date: Sun, 15 Feb 2015 04:19:40 +0100 Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: Message-ID: <54E0104C.90609@slackware.hr> On 02/15/2015 12:21 AM, Rich Shepard wrote: > When I build postfix-2.11.3 (or the new -3.0.0) there is an error that > prevents postfix from starting. In /usr/libexec/postfix/post-install, on > line 504 the error message is '... test: too many arguments'. > > This did not happen in earlier versions and I've no idea how to fix it. This question was answered a month ago and it can be found on this list. To answer it once more, you are probably missing quotes in main.cf (path variables). To make sure, you should probably check this and any other files that postfix loads. > When I build postfix with > SASL=dovecot, trying to start postfix causes it to throttle and generate > continuous error messages. Care to share those errors? > A week ago I wrote to the maintainer but have not received a reply. > Resolving these two issues is important. Actually, I've been sending in updates to postfix/dovecot for past 4-5 years. I am not the official maintainer, so I tried to keep changes small, for better or worse. -- Mario From mario at slackware.hr Sun Feb 15 03:39:42 2015 From: mario at slackware.hr (Mario Preksavec) Date: Sun, 15 Feb 2015 04:39:42 +0100 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <20150215023639.GK23739@harrier.slackbuilds.org> References: <54DFBC56.6080008@slaphappygeeks.com> <20150215023639.GK23739@harrier.slackbuilds.org> Message-ID: <54E014FE.5040401@slackware.hr> On 02/15/2015 03:36 AM, Rob McGee wrote: > On Sat, Feb 14, 2015 at 02:21:26PM -0700, Slacker wrote: >> I am writing a Slackdocs article for setting up a virtual mail >> server using Postfix, Dovecot and MySQL. >> >> In this use case we require a separate non-priv user/group >> for which the Dovecot documents suggest "vmail" ( >> http://wiki.dovecot.org/VirtualUsers ), and which I have used >> in my own implementation. >> >> This is purely a configuration option and is not required to build >> the Dovecot package. But it seems to me it is a common enough use >> case and that having an SBo assigned uid/gid for "vmail" would >> dovetail nicely with the dovecot docs and simplify virtual mail >> setup for those building with SBo scripts. It would also simplify >> my Slackdocs article. >> >> So, please consider this a request for either discussion or simply >> for an assigned uid/gid for a vmail user. > I never have understood why so many small-time users want to have > "virtual mail accounts." What is the appeal? "Gee whiz, all I do > when I add a domain is enter it in mysql." Well, uh, how often do > you add domains? I can see it if you're a large scale hosting > provider. Why is that so good if you're not? > > In the small-timer case, delivery to system accounts is far more > powerful and flexible. You can keep all your mail in your $HOME; > you're able to run commands on certain incoming mail; you have many > more options for storing and sorting mail. > > Furthermore, it's considerably less secure to have all mail under a > single UID/GID, as most of these virtual/mysql howtos seem to > advocate. A compromise of that user means all mail is at risk. > With system users, each recipient has her own UID, and compromises > are limited. > > (Actually that can be done with virtual also; both Postfix and > Dovecot support map lookups for the UID & GID. But few howtos -- if > any? I don't think I have seen one -- show how this is done.) > > So my concern here is twofold: one, it promotes "virtual mail" to > users who should not be using it; and two, it promotes the less > secure means of doing it, under a single UID/GID. Very well said. I would like to think that vmail *example* group was intentionally left out from uid_gid.txt to let user take a chunk of uid/gid mappings and do it properly. I also think that Slackdocs shouldn't be another copy/paste with a few minor changes; in fact, if done right it could fill that gap Rob is talking about :-) -- Mario From ts at websafe.pl Sun Feb 15 03:49:58 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 15 Feb 2015 04:49:58 +0100 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54DFEB6F.4030906@slackbuilds.org> References: <54DFBC56.6080008@slaphappygeeks.com> <54DFEB6F.4030906@slackbuilds.org> Message-ID: <54E01766.8090303@websafe.pl> On 02/15/2015 01:42 AM, Willy Sudiarto Raharjo wrote: > please use 303 for vmail I'm not sure if this (303) is a good idea? Everywhere I look I see uid 5000. I'm running Dovecot + Postfix on multiple machines, and I'm always using vmail/5000. http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix https://workaround.org/book/export/html/60 https://workaround.org/ispmail/squeeze/setting-up-dovecot http://www.openchange.org/cookbook/backends/sogo/dovecot.html https://www.linode.com/docs/email/postfix/email-with-postfix-dovecot-and-mysql-on-centos-5 And as Slacker stated, this is not required for building packages, so I don't think this should be defined in http://slackbuilds.org/uid_gid.txt The vmail user/group is not required for packaging and fully optional during dovecot usage. Slackbuilds do not create users/groups so the vmail group should not be defined there. For example, on some machines I'm using separate vmail groups for separate customers, starting with vmail/5000, vmail2/5001, vmail3/5002... -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Feb 15 03:55:09 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 15 Feb 2015 04:55:09 +0100 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54DFBC56.6080008@slaphappygeeks.com> References: <54DFBC56.6080008@slaphappygeeks.com> Message-ID: <54E0189D.3030007@websafe.pl> On 02/14/2015 10:21 PM, Slacker wrote: > I am writing a Slackdocs article for setting up a virtual mail server > using Postfix, Dovecot and MySQL. > In this use case we require a separate non-priv user/group for which the > Dovecot documents suggest "vmail" ( http://wiki.dovecot.org/VirtualUsers > ), and which I have used in my own implementation. > This is purely a configuration option and is not required to build the > Dovecot package. But it seems to me it is a common enough use case and > that having an SBo assigned uid/gid for "vmail" would dovetail nicely > with the dovecot docs and simplify virtual mail setup for those building > with SBo scripts. It would also simplify my Slackdocs article. > So, please consider this a request for either discussion or simply for > an assigned uid/gid for a vmail user. Hello Slacker, please consider using the default uid 5000 http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix https://wiki.archlinux.org/index.php/Virtual_user_mail_system http://www.stefan-seelmann.de/wiki/mailserver-postfix-dovecot and please let us know when Your article is published :-) -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Feb 15 04:08:06 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 15 Feb 2015 05:08:06 +0100 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <20150215023639.GK23739@harrier.slackbuilds.org> References: <54DFBC56.6080008@slaphappygeeks.com> <20150215023639.GK23739@harrier.slackbuilds.org> Message-ID: <54E01BA6.7080907@websafe.pl> On 02/15/2015 03:36 AM, Rob McGee wrote: > I never have understood why so many small-time users want to have > "virtual mail accounts." What is the appeal? "Gee whiz, all I do > when I add a domain is enter it in mysql." Well, uh, how often do > you add domains? I can see it if you're a large scale hosting > provider. Why is that so good if you're not? > In the small-timer case, delivery to system accounts is far more > powerful and flexible. You can keep all your mail in your $HOME; > you're able to run commands on certain incoming mail; you have many > more options for storing and sorting mail. I was running multiple Dovecot/Postfix instances for years, and I had the biggest problems with upgrading/migration etc. with system accounts. With virtual vmail accounts moving configs with e-mail storage among servers is much easier, so now I'm using vmail everywhere. > Furthermore, it's considerably less secure to have all mail under a > single UID/GID, as most of these virtual/mysql howtos seem to > advocate. A compromise of that user means all mail is at risk. > With system users, each recipient has her own UID, and compromises > are limited. Yes, but You already said "small-time users", so probably one-two domains, one owner, a single company etc. You can use multiple vmail users/groups (vmail1, vmail2) to separate customers. And when we're already in the subject of security, I would not give users access to their home dirs on an MTA. I would run an MTA in a separated vmachine instead of running multiple services on the same machine. And that's what I'm doing :-) > (Actually that can be done with virtual also; both Postfix and > Dovecot support map lookups for the UID & GID. But few howtos -- if > any? I don't think I have seen one -- show how this is done.) > So my concern here is twofold: one, it promotes "virtual mail" to > users who should not be using it; and two, it promotes the less > secure means of doing it, under a single UID/GID. As I already stated in this thread, I don't think that defining a vmail user/group in http://slackbuilds.org/uid_gid.txt is a good idea. IMO it's a bad idea and an unnecessary step :-) And uid 303 is really bad, because almost all howtos suggest 5000. -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From thomas at beingboiled.info Sun Feb 15 06:35:05 2015 From: thomas at beingboiled.info (Thomas Morper) Date: Sun, 15 Feb 2015 07:35:05 +0100 (CET) Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54DFEB6F.4030906@slackbuilds.org> References: <54DFBC56.6080008@slaphappygeeks.com> <54DFEB6F.4030906@slackbuilds.org> Message-ID: On Sun, 15 Feb 2015, Willy Sudiarto Raharjo wrote: > > So, please consider this a request for either discussion or simply > > for an assigned uid/gid for a vmail user. > please use 303 for vmail 303 is a bad choice for the vmail uid because then you'll need further adjustments in the Dovecot config to work around a security feature to prevent users from ever logging in as daemons (i.e. with uids < 500). A vmail user is not required at build time and not necessarily at runtime. When it is, the choice depends on the environment and on what one is trying to achieve. A static entry in the list of recommended UIDs/GIDs doesn't look sensible to me. -- From rshepard at appl-ecosys.com Sun Feb 15 14:26:26 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 06:26:26 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <20150215024822.GL23739@harrier.slackbuilds.org> References: <20150215024822.GL23739@harrier.slackbuilds.org> Message-ID: On Sat, 14 Feb 2015, Rob McGee wrote: > One might ask, why do you need Cyrus SASL if you have Dovecot installed? Rob, That's two of us asking. I need Cyrus SASL because if I specify SASL=dovecot postfix will not start. > Typically you do not; only in the less usual case of Postfix having to > authenticate at an upstream relay, would Cyrus become necessary. My outbound mail must be relayed through my ISP, but not the inbound. I would prefer to not use Cyrus. > All the details are here: > http://www.postfix.org/SASL_README.html I've read that several times. Let me build -3.0.0 with SASL=dovecot and upgrade. Then when I run '/etc/rc.d/rc.postfix start' I'll capture what /var/log/maillog shows and post that here. Will that help? Thanks, Rich From rshepard at appl-ecosys.com Sun Feb 15 15:55:14 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 07:55:14 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <54E0104C.90609@slackware.hr> References: <54E0104C.90609@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Mario Preksavec wrote: > Care to share those errors? Mario/Rob0: 1. Installed and running: postfix-2.11.3. 2. Stopped postfix. 3. Built -3.0.0 with VERSION=${VERSION:-3.0.0} ... # Build with dovecot sasl by default, cyrus/dovecot are supported SASL=${SASL:-dovecot} #SASL=${SASL:-cyrus} case "$SASL" in dovecot) SASLARGS="-DDEF_SERVER_SASL_TYPE=\\\"dovecot\\\"" SASLLIBS="" ;; cyrus) SASLARGS="-I/usr/include/sasl -DUSE_CYRUS_SASL" SASLLIBS="-L/usr/lib${LIBDIRSUFFIX}/sasl2 -lsasl2" ;; *) SASLARGS="" SASLLIBS="" ;; esac 4. upgradepkg /tmp/postfix-3.0.0-i486-1_SBo.tgz 5. See this diplayed in v.t.: Executing install script for postfix-3.0.0-i486-1_SBo.tgz. postfix: Postfix is running with backwards-compatible default settings postfix: See http://www.postfix.org/COMPATIBILITY_README.html for details postfix: To disable backwards compatibility use "postconf compatibility_level=2" and "postfix reload" /usr/libexec/postfix/post-install: line 539: test: too many arguments chown: cannot access '/usr/doc/postfix-2.11.3/README_FILES': No such file or / directory Package postfix-3.0.0-i486-1_SBo.tgz installed. Package postfix-2.11.3-i486-1_SBo upgraded with new package /tmp/postfix-3.0.0-i486-1_SBo.tgz. 6. Added quotes to "$path" to /usr/libexec/postfix/post-install, line 539 7. /etc/rc.d/rc.postfix start: Feb 15 07:16:55 salmo postfix/postsuper[19107]: fatal: scan_dir_push: open directory defer: Permission denied Feb 15 07:16:56 salmo postfix/postfix-script[19110]: fatal: Postfix integrity check failed! 8. Edited postfix.SlackBuild changing SASL to cyrus. 9. Re-built -3.0.0; same errors as in #5 above; editied post-install; starting postfix resulted in same errors as in #7 above. 10. Changed version back to -2.11.3 using SASL=${SALS:-cyrus}; re-ran postfix.Slackbuild. (using SASL=${SASL:-dovecot) fails with same errors as above. 11. 'upgradepkg /tmp/postfix-2.11.3-i486-1_SBo.tgz' now shows the post-install error on line 504 rather than on line 539. Fixed that. 12. '/etc/rc.d/rc.postfix start' returns postfix to working condition. The issues: 1. Version 3.0.0 will not build and install here regardless of SASL version. 2. Version 2.11.3 will not run with SASL=dovecot, only with SASL=cyrus. Please let me know what other information I can provide as I want to resolve these issues and be running postfix-3.0.0 with Dovecot. Thanks, Rich From rshepard at appl-ecosys.com Sun Feb 15 16:02:21 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 08:02:21 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: <54E0104C.90609@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Rich Shepard wrote: Typos: > 9. Re-built -3.0.0; same errors as in #5 above; editied post-install; edited > 10. Changed version back to -2.11.3 using SASL=${SALS:-cyrus}; re-ran SASL Rich From mario at slackware.hr Sun Feb 15 16:41:44 2015 From: mario at slackware.hr (Mario Preksavec) Date: Sun, 15 Feb 2015 17:41:44 +0100 Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: <54E0104C.90609@slackware.hr> Message-ID: <54E0CC48.3060101@slackware.hr> On 02/15/2015 04:55 PM, Rich Shepard wrote: > 3. Built -3.0.0 with At the moment, only version 2.11.4 is fully supported here. This update was added recently, so please use that. The newest 3.x series must undergo some scrutiny before its added as default; stability is preferred over a few minor features. Additionally, upstream is still backporting patches to 2.11.x series and will be for a long time; there is no reason to rush things and break stuff that works. -- Mario From rshepard at appl-ecosys.com Sun Feb 15 16:57:23 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 08:57:23 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <54E0CC48.3060101@slackware.hr> References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Mario Preksavec wrote: > At the moment, only version 2.11.4 is fully supported here. This update > was added recently, so please use that. Mario, Will do. I'll try 2.11.4 with dovecot and report the results. I suspect it will be no different from 2.11.3 and will not work for reasons yet to be determined. Thanks, Rich From rshepard at appl-ecosys.com Sun Feb 15 17:22:41 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 09:22:41 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <54E0CC48.3060101@slackware.hr> References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Mario Preksavec wrote: > At the moment, only version 2.11.4 is fully supported here. This update was > added recently, so please use that. Mario, Something here no longer works. There were no problems upgrading postfix over the past 17 years until 2.11.3. And now I cannot successfuly upgrade to even 2.11.4. Downloaded the new SlackBuild script and the postfix-2.11.4 tarball. After the script completed: [root at salmo /opt/slackbuilds/Office/postfix]# upgradepkg --reinstall /tmp/postfix-2.11.4-i486-1_SBo.tgz +============================================================================== | Upgrading postfix-2.11.4-i486-1_SBo package using /tmp/postfix-2.11.4-i486-1_SBo.tgz +============================================================================== Pre-installing package postfix-2.11.4-i486-1_SBo... /usr/libexec/postfix/post-install: line 504: test: too many arguments chown: cannot access '/usr/doc/postfix-2.11.3/README_FILES': No such file or / directory Removing package /var/log/packages/postfix-2.11.4-i486-1_SBo-upgraded-2015-02-15,09:06:43... Verifying package postfix-2.11.4-i486-1_SBo.tgz. Installing package postfix-2.11.4-i486-1_SBo.tgz: PACKAGE DESCRIPTION: # postfix (alternative to the widely-used Sendmail program) # # Postfix attempts to be fast, easy to administer, and secure, while at # the same time being sendmail compatible enough to not upset existing # users. Thus, the outside has a sendmail-ish flavor, but the inside is # completely different. # # Packaging script written by Alan Hicks # and the SlackBuilds.org Team # Executing install script for postfix-2.11.4-i486-1_SBo.tgz. /usr/libexec/postfix/post-install: line 504: test: too many arguments chown: cannot access '/usr/doc/postfix-2.11.3/README_FILES': No such file or / directory Package postfix-2.11.4-i486-1_SBo.tgz installed. Package postfix-2.11.4-i486-1_SBo upgraded with new package /tmp/postfix-2.11.4-i486-1_SBo.tgz. Notice the two lines above: /usr/libexec/postfix/post-install: line 504: test: too many arguments chown: cannot access '/usr/doc/postfix-2.11.3/README_FILES': No such file or / directory Line 504 need quotes around $path; should the quotes be added by the source file or by the SBo script? Why is the upgrade looking for the 2.11.3 README_FILES? So, it's installed and I try starting it: [root at salmo /opt/slackbuilds/Office/postfix]# /etc/rc.d/rc.postfix start postsuper: fatal: scan_dir_push: open directory defer: Permission denied postfix/postfix-script: fatal: Postfix integrity check failed! Next, I changed the SlackBuild script to use cyrus. Same results as above. In other words, 2.11.4 won't run either. Finally, rebuilt 2.11.3 with cyrus. Added quotes to post-install. Postfix starts and runs. Please suggest other diagnostics I can run here to isolate why no version higher than 2.11.3 runs. Thanks again, Rich From rshepard at appl-ecosys.com Sun Feb 15 17:27:22 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 09:27:22 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Rich Shepard wrote: > [root at salmo /opt/slackbuilds/Office/postfix]# upgradepkg --reinstall > /tmp/postfix-2.11.4-i486-1_SBo.tgz Oops! That was for the cyrus version. Before that, with 2.11.4 and dovecot trying to start postfix resulted in these errors: [root at salmo /opt/slackbuilds/Office/postfix]# /etc/rc.d/rc.postfix start postsuper: fatal: scan_dir_push: open directory defer: Permission denied postfix/postfix-script: fatal: Postfix integrity check failed! Same errors resulted with 2.11.4 and cyrus. Rich From rob0 at slackbuilds.org Sun Feb 15 19:45:29 2015 From: rob0 at slackbuilds.org (Rob McGee) Date: Sun, 15 Feb 2015 13:45:29 -0600 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54DFEC8D.2050807@slaphappygeeks.com> References: <54DFBC56.6080008@slaphappygeeks.com> <54DFEB6F.4030906@slackbuilds.org> <54DFEC8D.2050807@slaphappygeeks.com> Message-ID: <20150215194529.GM23739@harrier.slackbuilds.org> On Sat, Feb 14, 2015 at 05:47:09PM -0700, Slacker wrote: > On 02/14/2015 05:42 PM, Willy Sudiarto Raharjo wrote: > >>So, please consider this a request for either discussion > >>or simply for an assigned uid/gid for a vmail user. > > > >please use 303 for vmail On further discussion Willy and I have decided to revert this change. Thanks for the suggestion, and to all posters for their comments. We're sorry for any inconvenience regarding your howto. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From thomas at beingboiled.info Sun Feb 15 19:50:06 2015 From: thomas at beingboiled.info (Thomas Morper) Date: Sun, 15 Feb 2015 20:50:06 +0100 (CET) Subject: [Slackbuilds-users] stfl-0.24 and Perl examples Message-ID: Hello there, The SlackBuild for stfl conveniently relocates "example.pl" to the better fitting doc directory, but as of stfl 0.24 there's also an "example2.pl" which gets left in vendor_perl :-) Trivial fix: sed -i 's/example\.pl/example*.pl/' stfl.SlackBuild -- From mario at slackware.hr Sun Feb 15 20:25:31 2015 From: mario at slackware.hr (Mario Preksavec) Date: Sun, 15 Feb 2015 21:25:31 +0100 Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> Message-ID: <54E100BB.1000105@slackware.hr> On 02/15/2015 06:27 PM, Rich Shepard wrote: > [root at salmo /opt/slackbuilds/Office/postfix]# /etc/rc.d/rc.postfix start > postsuper: fatal: scan_dir_push: open directory defer: Permission denied > postfix/postfix-script: fatal: Postfix integrity check failed! > Are you going to fix paths in your config files? -- Mario From rshepard at appl-ecosys.com Sun Feb 15 20:43:54 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 12:43:54 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <54E100BB.1000105@slackware.hr> References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Mario Preksavec wrote: > Are you going to fix paths in your config files? Sure, when I know which files need fixing. I see no postfix confit files with 'locate config | less'. Rich From rshepard at appl-ecosys.com Sun Feb 15 20:56:18 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 12:56:18 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <54E100BB.1000105@slackware.hr> References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Mario Preksavec wrote: > Are you going to fix paths in your config files? Running 'postfix check' returns me to the shell prompt so there are no directory or permission issues. Rich From slacker at slaphappygeeks.com Sun Feb 15 23:11:48 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sun, 15 Feb 2015 16:11:48 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <20150215023639.GK23739@harrier.slackbuilds.org> References: <54DFBC56.6080008@slaphappygeeks.com> <20150215023639.GK23739@harrier.slackbuilds.org> Message-ID: <54E127B4.4020104@slaphappygeeks.com> On 02/14/2015 07:36 PM, Rob McGee wrote: > On Sat, Feb 14, 2015 at 02:21:26PM -0700, Slacker wrote: >> I am writing a Slackdocs article for setting up a virtual mail >> server using Postfix, Dovecot and MySQL. >> >> In this use case we require a separate non-priv user/group >> for which the Dovecot documents suggest "vmail" ( >> http://wiki.dovecot.org/VirtualUsers ), and which I have used >> in my own implementation. >> >> This is purely a configuration option and is not required to build >> the Dovecot package. But it seems to me it is a common enough use >> case and that having an SBo assigned uid/gid for "vmail" would >> dovetail nicely with the dovecot docs and simplify virtual mail >> setup for those building with SBo scripts. It would also simplify >> my Slackdocs article. >> >> So, please consider this a request for either discussion or simply >> for an assigned uid/gid for a vmail user. > So discussion it shall be! > I never have understood why so many small-time users want to have > "virtual mail accounts." What is the appeal? "Gee whiz, all I do > when I add a domain is enter it in mysql." Well, uh, how often do > you add domains? I can see it if you're a large scale hosting > provider. Why is that so good if you're not? My own use case is that I am consolidating some services for a customer, from multiple scattered hosting platforms into a VPS environment that they can manage. One big part of that is that they have dozens of email addresses across multiple domains that need to continue working when those existing hosts are changed or dropped. These "users" are email only and have no other presence on the host. This is really my first time out with setting up a a mail server, but virtual mail seemed the way to go, and has worked out well so far. > > In the small-timer case, delivery to system accounts is far more > powerful and flexible. You can keep all your mail in your $HOME; > you're able to run commands on certain incoming mail; you have many > more options for storing and sorting mail. > > Furthermore, it's considerably less secure to have all mail under a > single UID/GID, as most of these virtual/mysql howtos seem to > advocate. A compromise of that user means all mail is at risk. > With system users, each recipient has her own UID, and compromises > are limited. > > (Actually that can be done with virtual also; both Postfix and > Dovecot support map lookups for the UID & GID. But few howtos -- if > any? I don't think I have seen one -- show how this is done.) > > So my concern here is twofold: one, it promotes "virtual mail" to > users who should not be using it; and two, it promotes the less > secure means of doing it, under a single UID/GID. These concerns had not really crossed my own radar, thanks for the thoughts! Robert From slacker at slaphappygeeks.com Sun Feb 15 23:20:48 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sun, 15 Feb 2015 16:20:48 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54E014FE.5040401@slackware.hr> References: <54DFBC56.6080008@slaphappygeeks.com> <20150215023639.GK23739@harrier.slackbuilds.org> <54E014FE.5040401@slackware.hr> Message-ID: <54E129D0.6040100@slaphappygeeks.com> On 02/14/2015 08:39 PM, Mario Preksavec wrote: > On 02/15/2015 03:36 AM, Rob McGee wrote: >> On Sat, Feb 14, 2015 at 02:21:26PM -0700, Slacker wrote: >>> I am writing a Slackdocs article for setting up a virtual mail >>> server using Postfix, Dovecot and MySQL. >>> >>> In this use case we require a separate non-priv user/group >>> for which the Dovecot documents suggest "vmail" ( >>> http://wiki.dovecot.org/VirtualUsers ), and which I have used >>> in my own implementation. >>> >>> This is purely a configuration option and is not required to build >>> the Dovecot package. But it seems to me it is a common enough use >>> case and that having an SBo assigned uid/gid for "vmail" would >>> dovetail nicely with the dovecot docs and simplify virtual mail >>> setup for those building with SBo scripts. It would also simplify >>> my Slackdocs article. >>> >>> So, please consider this a request for either discussion or simply >>> for an assigned uid/gid for a vmail user. >> I never have understood why so many small-time users want to have >> "virtual mail accounts." What is the appeal? "Gee whiz, all I do >> when I add a domain is enter it in mysql." Well, uh, how often do >> you add domains? I can see it if you're a large scale hosting >> provider. Why is that so good if you're not? >> >> In the small-timer case, delivery to system accounts is far more >> powerful and flexible. You can keep all your mail in your $HOME; >> you're able to run commands on certain incoming mail; you have many >> more options for storing and sorting mail. >> >> Furthermore, it's considerably less secure to have all mail under a >> single UID/GID, as most of these virtual/mysql howtos seem to >> advocate. A compromise of that user means all mail is at risk. >> With system users, each recipient has her own UID, and compromises >> are limited. >> >> (Actually that can be done with virtual also; both Postfix and >> Dovecot support map lookups for the UID & GID. But few howtos -- if >> any? I don't think I have seen one -- show how this is done.) >> >> So my concern here is twofold: one, it promotes "virtual mail" to >> users who should not be using it; and two, it promotes the less >> secure means of doing it, under a single UID/GID. > > Very well said. I would like to think that vmail *example* group was > intentionally left out from uid_gid.txt to let user take a chunk of > uid/gid mappings and do it properly. I also think that Slackdocs > shouldn't be another copy/paste with a few minor changes; in fact, if > done right it could fill that gap Rob is talking about :-) > Well, I can't speak for anyone else, but my own Slackdocs article (my first there too by the way) is certainly not copy/paste. I am trying to make it a genuine "how to" which will liberally include the "why to" - something I could not find anywhere when I started this exercise! But I will certainly want to consider some changes and additions based on comments in replies to my question here - thanks to all! Robert From slacker at slaphappygeeks.com Sun Feb 15 23:28:34 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sun, 15 Feb 2015 16:28:34 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54E01766.8090303@websafe.pl> References: <54DFBC56.6080008@slaphappygeeks.com> <54DFEB6F.4030906@slackbuilds.org> <54E01766.8090303@websafe.pl> Message-ID: <54E12BA2.5040609@slaphappygeeks.com> On 02/14/2015 08:49 PM, Thomas Szteliga wrote: > On 02/15/2015 01:42 AM, Willy Sudiarto Raharjo wrote: >> please use 303 for vmail > > I'm not sure if this (303) is a good idea? > Everywhere I look I see uid 5000. > > I'm running Dovecot + Postfix on multiple machines, > and I'm always using vmail/5000. > > http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix > https://workaround.org/book/export/html/60 > https://workaround.org/ispmail/squeeze/setting-up-dovecot > http://www.openchange.org/cookbook/backends/sogo/dovecot.html > https://www.linode.com/docs/email/postfix/email-with-postfix-dovecot-and-mysql-on-centos-5 > > And as Slacker stated, this is not required for building > packages, so I don't think this should be defined > in http://slackbuilds.org/uid_gid.txt > > The vmail user/group is not required for packaging > and fully optional during dovecot usage. Slackbuilds do > not create users/groups so the vmail group should not be > defined there. > > For example, on some machines I'm using separate vmail > groups for separate customers, starting with vmail/5000, > vmail2/5001, vmail3/5002... I did see a number of references to uid 5000 for vmail, but never had the sense that it was pseudo-standard. In fact, it was the common use of "vmail" as the user/group name (I think because dovecot docs use it) but no compelling reason for any uid/gid that led to my question here. Thanks for the links too - I had seen some but not others. In the end my own approach resulted mostly from re-reading the dovecot and postfix docs after getting a general direction from other sources. Robert > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From slacker at slaphappygeeks.com Sun Feb 15 23:29:34 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sun, 15 Feb 2015 16:29:34 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54E0189D.3030007@websafe.pl> References: <54DFBC56.6080008@slaphappygeeks.com> <54E0189D.3030007@websafe.pl> Message-ID: <54E12BDE.2000007@slaphappygeeks.com> On 02/14/2015 08:55 PM, Thomas Szteliga wrote: > On 02/14/2015 10:21 PM, Slacker wrote: >> I am writing a Slackdocs article for setting up a virtual mail server >> using Postfix, Dovecot and MySQL. >> In this use case we require a separate non-priv user/group for which the >> Dovecot documents suggest "vmail" ( http://wiki.dovecot.org/VirtualUsers >> ), and which I have used in my own implementation. >> This is purely a configuration option and is not required to build the >> Dovecot package. But it seems to me it is a common enough use case and >> that having an SBo assigned uid/gid for "vmail" would dovetail nicely >> with the dovecot docs and simplify virtual mail setup for those building >> with SBo scripts. It would also simplify my Slackdocs article. >> So, please consider this a request for either discussion or simply for >> an assigned uid/gid for a vmail user. > > > Hello Slacker, > > please consider using the default uid 5000 > > http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix > https://wiki.archlinux.org/index.php/Virtual_user_mail_system > http://www.stefan-seelmann.de/wiki/mailserver-postfix-dovecot > > and please let us know when Your article is published :-) I will, on both counts! It is a work in progress! Robert > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From slackbuilds at jaxartes.net Sun Feb 15 23:39:32 2015 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 15 Feb 2015 15:39:32 -0800 Subject: [Slackbuilds-users] stfl-0.24 and Perl examples In-Reply-To: References: Message-ID: <5657685.VqFEcFmvAs@jerseybastion> On February 15, 2015 08:50:06 PM Thomas Morper wrote: > Hello there, > > The SlackBuild for stfl conveniently relocates "example.pl" to the better > fitting doc directory, but as of stfl 0.24 there's also an "example2.pl" > which gets left in vendor_perl :-) > > Trivial fix: sed -i 's/example\.pl/example*.pl/' stfl.SlackBuild Thanks! Fixed for next update. From slacker at slaphappygeeks.com Sun Feb 15 23:42:46 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sun, 15 Feb 2015 16:42:46 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54E01BA6.7080907@websafe.pl> References: <54DFBC56.6080008@slaphappygeeks.com> <20150215023639.GK23739@harrier.slackbuilds.org> <54E01BA6.7080907@websafe.pl> Message-ID: <54E12EF6.2040406@slaphappygeeks.com> On 02/14/2015 09:08 PM, Thomas Szteliga wrote: > On 02/15/2015 03:36 AM, Rob McGee wrote: >> I never have understood why so many small-time users want to have >> "virtual mail accounts." What is the appeal? "Gee whiz, all I do >> when I add a domain is enter it in mysql." Well, uh, how often do >> you add domains? I can see it if you're a large scale hosting >> provider. Why is that so good if you're not? >> In the small-timer case, delivery to system accounts is far more >> powerful and flexible. You can keep all your mail in your $HOME; >> you're able to run commands on certain incoming mail; you have many >> more options for storing and sorting mail. > > > I was running multiple Dovecot/Postfix instances for years, and > I had the biggest problems with upgrading/migration etc. with > system accounts. With virtual vmail accounts moving configs with > e-mail storage among servers is much easier, so now I'm using > vmail everywhere. I have not run these myself before, but the migration and future management requirements were what led me to it. > > >> Furthermore, it's considerably less secure to have all mail under a >> single UID/GID, as most of these virtual/mysql howtos seem to >> advocate. A compromise of that user means all mail is at risk. >> With system users, each recipient has her own UID, and compromises >> are limited. > > > Yes, but You already said "small-time users", so probably one-two > domains, one owner, a single company etc. You can use multiple vmail > users/groups (vmail1, vmail2) to separate customers. > And when we're already in the subject of security, I would not > give users access to their home dirs on an MTA. > I would run an MTA in a separated vmachine instead of running > multiple services on the same machine. And that's what I'm doing :-) Yes, that is very close to my own case - access to the machine will be strictly limited. > > >> (Actually that can be done with virtual also; both Postfix and >> Dovecot support map lookups for the UID & GID. But few howtos -- if >> any? I don't think I have seen one -- show how this is done.) >> So my concern here is twofold: one, it promotes "virtual mail" to >> users who should not be using it; and two, it promotes the less >> secure means of doing it, under a single UID/GID. > > > As I already stated in this thread, I don't think that > defining a vmail user/group in http://slackbuilds.org/uid_gid.txt > is a good idea. IMO it's a bad idea and an unnecessary step :-) > And uid 303 is really bad, because almost all howtos suggest 5000. OK, I realize the lower uid/gids are generally reserved for daemon processes, and there are a limited number of them... but really, it is still just a number - there isn't actually anything "special" about numbers in that range is there? I am not arguing it, I want to understand it better - why is it such a really bad idea? Thanks > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From slacker at slaphappygeeks.com Sun Feb 15 23:47:30 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sun, 15 Feb 2015 16:47:30 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: References: <54DFBC56.6080008@slaphappygeeks.com> <54DFEB6F.4030906@slackbuilds.org> Message-ID: <54E13012.2040206@slaphappygeeks.com> On 02/14/2015 11:35 PM, Thomas Morper wrote: > On Sun, 15 Feb 2015, Willy Sudiarto Raharjo wrote: > >>> So, please consider this a request for either discussion or simply >>> for an assigned uid/gid for a vmail user. > >> please use 303 for vmail > > 303 is a bad choice for the vmail uid because then you'll need further > adjustments in the Dovecot config to work around a security feature to > prevent users from ever logging in as daemons (i.e. with uids < 500). AH! One answer to a question I just posted in another reply! So this is a good reason not to use the lower numbers at least! > > A vmail user is not required at build time and not necessarily at runtime. > When it is, the choice depends on the environment and on what one is > trying to achieve. A static entry in the list of recommended UIDs/GIDs > doesn't look sensible to me. Yes, and my thought was to provide a static choice when it is required, as it is not an "unusual" requirement. Thanks > From slacker at slaphappygeeks.com Sun Feb 15 23:49:50 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Sun, 15 Feb 2015 16:49:50 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <20150215194529.GM23739@harrier.slackbuilds.org> References: <54DFBC56.6080008@slaphappygeeks.com> <54DFEB6F.4030906@slackbuilds.org> <54DFEC8D.2050807@slaphappygeeks.com> <20150215194529.GM23739@harrier.slackbuilds.org> Message-ID: <54E1309E.5080907@slaphappygeeks.com> On 02/15/2015 12:45 PM, Rob McGee wrote: > On Sat, Feb 14, 2015 at 05:47:09PM -0700, Slacker wrote: >> On 02/14/2015 05:42 PM, Willy Sudiarto Raharjo wrote: >>>> So, please consider this a request for either discussion >>>> or simply for an assigned uid/gid for a vmail user. >>> >>> please use 303 for vmail > > On further discussion Willy and I have decided to revert this change. > Thanks for the suggestion, and to all posters for their comments. > We're sorry for any inconvenience regarding your howto. Not an inconvenience! Part of my continuing education! Thanks for all comments and replies! Robert > From rshepard at appl-ecosys.com Mon Feb 16 01:12:58 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 17:12:58 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <54E100BB.1000105@slackware.hr> References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Mario Preksavec wrote: >> postfix/postfix-script: fatal: Postfix integrity check failed! > Are you going to fix paths in your config files? The fatal message above is on lines 97-98 in postfix-script. According to a 2008 thread on linuxquestions.org, the source should be identified by running 'postfix check' and 'postsuper -sv'. 'postfix check' returns nothing, which means (if my readings are accurate) that there are no directory or permission errors. 'postsuper -sv' returns: postsuper: name_mask: ipv4 postsuper: inet_addr_local: configured 2 IPv4 addresses postsuper: queue: defer postsuper: queue: bounce postsuper: queue: maildrop postsuper: queue: incoming postsuper: queue: active postsuper: queue: deferred postsuper: queue: hold postsuper: queue: flush and I do not see an indication of what might be missing. The -s option performs structure checks and repairs; the -v option enables verbose logging. My Web searches do not find what paths in main.cf might need fixing in 2.11.4 but not in 2.11.3. Guess I need to install 2.11.4 and run 'postfix check' and 'postsuper -sv' since there's nothing found out of whack on 2.11.3. That'll need to wait for tomorrow evening. Rich From rshepard at appl-ecosys.com Mon Feb 16 03:34:10 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 15 Feb 2015 19:34:10 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> Message-ID: On Sun, 15 Feb 2015, Rich Shepard wrote: > Guess I need to install 2.11.4 and run 'postfix check' and 'postsuper -sv' > ... postfix-2.11.4: added double quotes to /usr/libexec/postfix/post-install line 504 "$path". postfix check postsuper: fatal: scan_dir_push: open directory defer: Permission denied postsuper -sv postsuper: name_mask: ipv4 postsuper: inet_addr_local: configured 2 IPv4 addresses postsuper: queue: defer postsuper: fatal: scan_dir_push: open directory defer: Permission denied Found a linuxquestions.org thread for the fatal error: However, changing owner of /var/spool/postfix to postfix and the perms to 644 did not resolve the problem. Changed back to owner root and perms 755. Rebuilt and reinstalled -2.11.3. postfix check finds no issues; postsuper -sv lists all queues and no issues. I'm stymied and need help to fix the quotes, the above error on 2.11.4, and getting dovecot working in lieu of cyrus. Rich From dnc at hipplanet.com Mon Feb 16 05:13:28 2015 From: dnc at hipplanet.com (David Melik) Date: Sun, 15 Feb 2015 21:13:28 -0800 Subject: [Slackbuilds-users] Mathics SlackBuild Message-ID: <20150215211328.39F3BDF5@m0048136.ppops.net> Recently I successfully made a SlackBuild of Mathics (a Free/Libre/Opensource Software version of part of Mathematica, arguably the main academic mathematics programming language and software system). However, it uses Python, which I do not know. I would like someone to take over this build and submit it to SlackBuilds.org (SBo). If you want to, please let me know, and download http://temple-of-mathematics.com/david/math/code/mathics+deps.tar.gz , which has my SlackBuild and notes on what I had to do, or what else might have to be done to make it ready to submit to SBo. My archive file may also contain the source, but you should get that from mathics.org. They show a zip on the first page, that I used, that is not perfect for making a GNU/Linux version, and they have a source area on github or something, that has a .tar.gz, but that also has the aforementioned zip inside it (duplicating almost everything)... so, the project needs some more work, and unfortunately, may not have a maintainer right now... but I thought it was a pretty important SlackBuild, compared to all the other math software that are not so academic standard... David http://www.cwu.edu/~melikd (homepage on most stable site) http://temple-of-mathematics.com/david (homepage--same--updated first) _____________________________________________________________ Find out what's HIP! Visit Hip Planet for news, shopping, forums, chatrooms, free personal and classified ads and much more! Get FREE E-MAIL! at HipPlanet now! It's all waiting for you, at http://www.hipplanet.com From netrixtardis at stealth3.com Mon Feb 16 07:26:15 2015 From: netrixtardis at stealth3.com (netrixtardis) Date: Mon, 16 Feb 2015 01:26:15 -0600 Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> Message-ID: <54E19B97.50406@stealth3.com> On 2/15/2015 9:34 PM, Rich Shepard wrote: > On Sun, 15 Feb 2015, Rich Shepard wrote: > >> Guess I need to install 2.11.4 and run 'postfix check' and >> 'postsuper -sv' >> ... > > postfix-2.11.4: added double quotes to > /usr/libexec/postfix/post-install > line 504 "$path". > > postfix check > postsuper: fatal: scan_dir_push: open directory defer: Permission denied > > postsuper -sv > postsuper: name_mask: ipv4 > postsuper: inet_addr_local: configured 2 IPv4 addresses > postsuper: queue: defer > postsuper: fatal: scan_dir_push: open directory defer: Permission denied > > Found a linuxquestions.org thread for the fatal error: > > > However, changing owner of /var/spool/postfix to postfix and the perms to > 644 did not resolve the problem. Changed back to owner root and perms > 755. > > Rebuilt and reinstalled -2.11.3. postfix check finds no issues; > postsuper > -sv lists all queues and no issues. > > I'm stymied and need help to fix the quotes, the above error on 2.11.4, > and getting dovecot working in lieu of cyrus. > > Rich I have come across your issue when I have the following 2 lines in main.cf: #html_directory = /usr/doc/postfix-2.11.0/html #readme_directory = /usr/doc/postfix-2.11.0/README_FILES I have them currently commented out, however what I have found is that during the post-install, the postfix-script tried to make sure you have a sane main.cf. With these 2 lines showing hard coded path, you will have an error against the version you are installing. I figured this out around the time of my upgrade to 2.11.0, which is why I haven't update them. The fix would be to not hard code the version, or to update the lines prior to your update. From lems at gmx.net Mon Feb 16 07:26:30 2015 From: lems at gmx.net (Leonard Schmidt) Date: Mon, 16 Feb 2015 08:26:30 +0100 Subject: [Slackbuilds-users] nvidia-legacy340-driver: wrong dependency in .info file? Message-ID: <0M6wWn-1XbbTH3Pld-00wnGv@mail.gmx.com> Hello, I noticed that nvidia-legacy340-driver simply has `nvidia-kernel' as REQUIRES, while the other legacy drivers don't (they link to specific versions). My tool makes use of that information and would pull in nvidia-kernel instead of nvidia-legacy340-kernel. Regards Leonard From slacker at slaphappygeeks.com Mon Feb 16 10:11:15 2015 From: slacker at slaphappygeeks.com (Slacker) Date: Mon, 16 Feb 2015 03:11:15 -0700 Subject: [Slackbuilds-users] UID/GID for another Dovecot case In-Reply-To: <54E12BDE.2000007@slaphappygeeks.com> References: <54DFBC56.6080008@slaphappygeeks.com> <54E0189D.3030007@websafe.pl> <54E12BDE.2000007@slaphappygeeks.com> Message-ID: <54E1C243.4060100@slaphappygeeks.com> On 02/15/2015 04:29 PM, Slacker wrote: > > > On 02/14/2015 08:55 PM, Thomas Szteliga wrote: >> >> and please let us know when Your article is published :-) > For better or worse, I am out of time for the next week, so here it is, warts and all: http://docs.slackware.com/howtos:network_services:postfix_dovecot_mysql I appreciate all previous comments and will continue to appreciate helpful comments, suggestions and corrections via the list or my own email as appropriate. It still has a few shortcomings I hope to correct as time permits - but I think this a pretty good first edition. Thanks, Robert From rshepard at appl-ecosys.com Mon Feb 16 14:22:42 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 16 Feb 2015 06:22:42 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type In-Reply-To: <54E19B97.50406@stealth3.com> References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> <54E19B97.50406@stealth3.com> Message-ID: On Mon, 16 Feb 2015, netrixtardis wrote: > I have come across your issue when I have the following 2 lines in main.cf: > > #html_directory = /usr/doc/postfix-2.11.0/html > #readme_directory = /usr/doc/postfix-2.11.0/README_FILES > > I have them currently commented out, however what I have found is that > during the post-install, the postfix-script tried to make sure you have > a sane main.cf. With these 2 lines showing hard coded path, you will > have an error against the version you are installing. I figured this > out around the time of my upgrade to 2.11.0, which is why I haven't > update them. The fix would be to not hard code the version, or to > update the lines prior to your update. WOW! Yes, commenting out those two lines at the bottom of main.cf permits the upgrade from 2.11.3 to 2.11.4. Amazing that the version numbers are hard-coded in main.cf. I suspect that hard-coding occurred in 2.11.0 or 2.11.1 because that's also when the unquoted variable, $path, showed up as an issue. So, now that I have successfully upgraded in the 2.11.x series the need remains to 1) have $path correctly quoted in post-install and 2) use dovecot SASL rather than Cyrus SASL. Perhaps the latter is affected by the broken directories in main.cf. I'll make time to test this Real Soon Now. Thanks very much! Rich From willysr at slackbuilds.org Mon Feb 16 21:01:51 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 17 Feb 2015 04:01:51 +0700 Subject: [Slackbuilds-users] docker build fail on x86_64 In-Reply-To: <54DF476C.8000802@slackbuilds.org> References: <54DF476C.8000802@slackbuilds.org> Message-ID: <54E25ABF.3020602@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Yes, i confirmed that it does indeed failed to build on -stable > releases I have notified Pat and see if he agreed to add the > missing header to -stable release as well Pat has updated btrfs-progs in -stable, so this should build properly now. - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEUEARECAAYFAlTiWr8ACgkQiHuDdNczM4HjQACdH+blAAUT7ohO1Ek3TEQkKVyS 5HYAl1MPK6BaqNQfKfbtBVTgDMmfXwI= =Q6YP -----END PGP SIGNATURE----- From willysr at slackbuilds.org Tue Feb 17 09:31:10 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 17 Feb 2015 16:31:10 +0700 Subject: [Slackbuilds-users] nvidia-legacy340-driver: wrong dependency in .info file? In-Reply-To: <0M6wWn-1XbbTH3Pld-00wnGv@mail.gmx.com> References: <0M6wWn-1XbbTH3Pld-00wnGv@mail.gmx.com> Message-ID: <54E30A5E.50508@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I noticed that nvidia-legacy340-driver simply has `nvidia-kernel' > as REQUIRES, while the other legacy drivers don't (they link to > specific versions). My tool makes use of that information and would > pull in nvidia-kernel instead of nvidia-legacy340-kernel. Thanks for reporting it has been fixed in my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTjCl4ACgkQiHuDdNczM4EEuACggvOept9tjprH3fWztAJycHYK 1bEAoKBP+aGfda85zo48MEVnFTI7ZkUy =QaiQ -----END PGP SIGNATURE----- From slackbuilds at rochefort.de Tue Feb 17 12:56:16 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Tue, 17 Feb 2015 13:56:16 +0100 Subject: [Slackbuilds-users] Md5sum of unison Message-ID: <54E33A70.2090608@rochefort.de> Hi all, I am getting a wrong md5sum on the unison sources. The sum I an getting when I run md5sum unison-2.40.128.tar.gz is this: 4194015003956a10a2d0a83e3e7733f7 unison-2.40.128.tar.gz The download page states I should get aa4d9d425b2ee2f9676ac5331a154bac http://slackbuilds.org/repository/14.1/system/unison/?search=unison Am I missing something? From matteo.bernardini at gmail.com Tue Feb 17 13:08:34 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 17 Feb 2015 14:08:34 +0100 Subject: [Slackbuilds-users] Md5sum of unison In-Reply-To: <54E33A70.2090608@rochefort.de> References: <54E33A70.2090608@rochefort.de> Message-ID: 2015-02-17 13:56 GMT+01:00 Enguerrand de Rochefort : > Hi all, > > I am getting a wrong md5sum on the unison sources. > > The sum I an getting when I run > > md5sum unison-2.40.128.tar.gz > > is this: > 4194015003956a10a2d0a83e3e7733f7 unison-2.40.128.tar.gz > > The download page states I should get > aa4d9d425b2ee2f9676ac5331a154bac > > http://slackbuilds.org/repository/14.1/system/unison/?search=unison > > Am I missing something? I checked the tarball as archived by fedora people here (that has the same md5sum as the one we have in our repository) http://pkgs.fedoraproject.org/repo/pkgs/unison240/unison-2.40.128.tar.gz/aa4d9d425b2ee2f9676ac5331a154bac/unison-2.40.128.tar.gz and run a diff on the extracted sources from that and the new one: no differences at all. I suppose unison devs have overwritten the old with the one is available now but, IMHO, there's nothing worry. Matteo From rshepard at appl-ecosys.com Mon Feb 16 15:29:32 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 16 Feb 2015 07:29:32 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type [FIXED] In-Reply-To: References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> <54E19B97.50406@stealth3.com> Message-ID: On Mon, 16 Feb 2015, Rich Shepard wrote: > So, now that I have successfully upgraded in the 2.11.x series the need > remains to 1) have $path correctly quoted in post-install and 2) use dovecot > SASL rather than Cyrus SASL. Perhaps the latter is affected by the broken > directories in main.cf. I'll make time to test this Real Soon Now. I became impatient. Rebuilding 2.11.4 with dovecot succeeded. Looking at postfix.SlackBuild I see no indication that the hard coding of version numbers in the html and doc directories in main.cf, nor indications that the unquoted "$path" in line 504 of /usr/libexec/postfix/post-install come from this script. I'll report this on the postfix mail list. Thank you Mario, Rob0, and netrixtardis! Rich From rshepard at appl-ecosys.com Tue Feb 17 14:22:10 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 17 Feb 2015 06:22:10 -0800 (PST) Subject: [Slackbuilds-users] Problems With Postfix: post-install line 504 and SASL type [FIXED] In-Reply-To: References: <54E0104C.90609@slackware.hr> <54E0CC48.3060101@slackware.hr> <54E100BB.1000105@slackware.hr> <54E19B97.50406@stealth3.com> Message-ID: On Mon, 16 Feb 2015, Rich Shepard wrote: > I became impatient. Rebuilding 2.11.4 with dovecot succeeded. While building and upgrading postfix-2.11.4 with dovecot succeeded, I have not been able to correctly and successfully configure dovecot and the postfix main.cf. I'll take this to the postfix mail list. Rich From jbernts at broadpark.no Tue Feb 17 17:35:49 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 17 Feb 2015 18:35:49 +0100 Subject: [Slackbuilds-users] Barry dependencies Message-ID: <20150217173549.GA1819@jostein> I have a blackberry and would like to install barry, but the requirements for this one is quite confusing. When installing it with sbopkg it errors out with: configure: error: Package requirements (gtkmm-2.4 libglademm-2.4 gthread-2.0) were not met: No package 'gtkmm-2.4' found No package 'libglademm-2.4' found The readme file says libglademm and libtar. If I then install libgtkmm it request for 2 more dependencies, one of this is not in slackbuild (giomm). Should this be done more convenient to install? Jostein From matteo.bernardini at gmail.com Tue Feb 17 17:57:17 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 17 Feb 2015 18:57:17 +0100 Subject: [Slackbuilds-users] Barry dependencies In-Reply-To: <20150217173549.GA1819@jostein> References: <20150217173549.GA1819@jostein> Message-ID: if I generate a queue file with sqg, this is the output (this is the stuff, ordered, that must be built) libtar mm-common libsigc++ glibmm cairomm pangomm atkmm gtkmm libglademm barry Matteo From jbernts at broadpark.no Tue Feb 17 19:00:38 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 17 Feb 2015 20:00:38 +0100 Subject: [Slackbuilds-users] Barry dependencies In-Reply-To: References: <20150217173549.GA1819@jostein> Message-ID: <20150217190038.GC1826@jostein> On 17.02.15,18:57, Matteo Bernardini wrote: > if I generate a queue file with sqg, this is the output (this is the > stuff, ordered, that must be built) > > libtar > mm-common > libsigc++ > glibmm > cairomm > pangomm > atkmm > gtkmm > libglademm > barry > > Matteo Hi, this worked great. Thanks. Jostein From slackbuilds at rochefort.de Tue Feb 17 19:20:36 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Tue, 17 Feb 2015 20:20:36 +0100 Subject: [Slackbuilds-users] Md5sum of unison In-Reply-To: References: <54E33A70.2090608@rochefort.de> Message-ID: <54E39484.8060702@rochefort.de> Hi Matteo thanks a lot for your efforts... installing it now. Regards Enguerrand On 17.02.2015 14:08, Matteo Bernardini wrote: > 2015-02-17 13:56 GMT+01:00 Enguerrand de Rochefort : >> Hi all, >> >> I am getting a wrong md5sum on the unison sources. >> >> The sum I an getting when I run >> >> md5sum unison-2.40.128.tar.gz >> >> is this: >> 4194015003956a10a2d0a83e3e7733f7 unison-2.40.128.tar.gz >> >> The download page states I should get >> aa4d9d425b2ee2f9676ac5331a154bac >> >> http://slackbuilds.org/repository/14.1/system/unison/?search=unison >> >> Am I missing something? > > I checked the tarball as archived by fedora people here (that has the > same md5sum as the one we have in our repository) > > http://pkgs.fedoraproject.org/repo/pkgs/unison240/unison-2.40.128.tar.gz/aa4d9d425b2ee2f9676ac5331a154bac/unison-2.40.128.tar.gz > > and run a diff on the extracted sources from that and the new one: no > differences at all. > > I suppose unison devs have overwritten the old with the one is > available now but, IMHO, there's nothing worry. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From ml at mareichelt.com Tue Feb 17 21:04:49 2015 From: ml at mareichelt.com (Markus Reichelt) Date: Tue, 17 Feb 2015 22:04:49 +0100 Subject: [Slackbuilds-users] pysetuptools 8 implements PEP 440 In-Reply-To: <20150208181058.GA14367@varna> References: <20141222202117.GA24591@pc21.mareichelt.com> <20150208181058.GA14367@varna> Message-ID: <20150217210449.GD3629@pc21.mareichelt.com> * Audrius Kazukauskas wrote: > I pushed updates for pysetuptools, pip and virtualenv latest > versions. I feel that we waited long enough for things to settle > down, and most of the issues related to PEP 440 should be solved > either by setuptools devs (if there were any bugs in their code) or > by upstream of other projects depending on setuptools. Thanks for being patient (and the patch). > Regarding allmydata-tahoe, developers fixed version specifiers in > their Git repo, but there doesn't seem to be any versions released > with those fixes, so I extracted them into a patch (attached). It > works for me with setuptools 12.0.5, but I only installed > allmydata-tahoe and tried to run "tahoe --version", so please test > it and see if everything works correctly. allmydata-tahoe 1.10.1 is scheduled to be released soon (couple of weeks at most). Compared to 1.10 this version will have more (direct or indirect) dependencies and the adaptation of that code to PEP 440 is best documented at https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2354 According to the Slackware64 buildbot it's all fine, wrt PEP 440: https://tahoe-lafs.org/buildbot-tahoe-lafs/builders/Markus%20slackware64%20stable/builds/43 I plan to check all deps for updates and run tests this weekend. -- Naughty little Tahoe-LAFS. From jbernts at broadpark.no Wed Feb 18 02:06:51 2015 From: jbernts at broadpark.no (Jostein Berntsen) Date: Wed, 18 Feb 2015 03:06:51 +0100 Subject: [Slackbuilds-users] libopensync failing Message-ID: <20150218020651.GD1826@jostein> When installing libopensync it errors out with download file not found. Seems like www.opensync.org is not operative. Replacing the download file in info with f.ex. http://pkgs.fedoraproject.org/repo/pkgs/libopensync/libopensync-0.22.tar.bz2/f563ce2543312937a9afb4f8445ef932/libopensync-0.22.tar.bz2 makes the script work. Jostein From willysr at slackbuilds.org Wed Feb 18 06:09:27 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 18 Feb 2015 13:09:27 +0700 Subject: [Slackbuilds-users] libopensync failing In-Reply-To: <20150218020651.GD1826@jostein> References: <20150218020651.GD1826@jostein> Message-ID: <54E42C97.1040700@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > When installing libopensync it errors out with download file not > found. Seems like www.opensync.org is not operative. Replacing the > download file in info with f.ex. > > http://pkgs.fedoraproject.org/repo/pkgs/libopensync/libopensync-0.22.tar.bz2/f563ce2543312937a9afb4f8445ef932/libopensync-0.22.tar.bz2 > > makes the script work. Thanks fixed it on my branch - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTkLJcACgkQiHuDdNczM4FsAACgqekd4CIkndjOrgYQjxKt6IHy fD0AniJRiu2dkPaxS+4GXRezi6yMgPlA =g83r -----END PGP SIGNATURE----- From mathieu.bouillaguet at gmail.com Wed Feb 18 08:04:55 2015 From: mathieu.bouillaguet at gmail.com (Mathieu Bouillaguet) Date: Wed, 18 Feb 2015 09:04:55 +0100 Subject: [Slackbuilds-users] docker build fail on x86_64 In-Reply-To: <54E25ABF.3020602@slackbuilds.org> References: <54DF476C.8000802@slackbuilds.org> <54E25ABF.3020602@slackbuilds.org> Message-ID: I confirm that with the lastest btrfs-progs from stable the SlackBuild now builds correctly. Thanks 2015-02-16 22:01 GMT+01:00 Willy Sudiarto Raharjo : > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Yes, i confirmed that it does indeed failed to build on -stable > > releases I have notified Pat and see if he agreed to add the > > missing header to -stable release as well > > Pat has updated btrfs-progs in -stable, so this should build properly now. > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEUEARECAAYFAlTiWr8ACgkQiHuDdNczM4HjQACdH+blAAUT7ohO1Ek3TEQkKVyS > 5HYAl1MPK6BaqNQfKfbtBVTgDMmfXwI= > =Q6YP > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ts at websafe.pl Wed Feb 18 10:57:09 2015 From: ts at websafe.pl (Thomas Szteliga) Date: Wed, 18 Feb 2015 11:57:09 +0100 Subject: [Slackbuilds-users] libreoffice-langpack - problems / questions Message-ID: <54E47005.5030803@websafe.pl> Hello, few words about what I've noticed when I tried to build libreoffice-langpack (other than en-GB) with md5sum checking enabled (using slpkg). The build fails, because each langpack has another md5sum, and contains the md5sum only for the en-GB pack. Question is, should we: 1. create a "cloned" slackbuild for each langpack with a valid DOWNLOAD and MD5SUM in .nfo or 2. modify the SlackBuild and .nfo to include all languages by default or 3. leave it as it is? Any ideas? -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3692 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Wed Feb 18 12:15:43 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 18 Feb 2015 19:15:43 +0700 Subject: [Slackbuilds-users] libreoffice-langpack - problems / questions In-Reply-To: <54E47005.5030803@websafe.pl> References: <54E47005.5030803@websafe.pl> Message-ID: <54E4826F.3010701@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > few words about what I've noticed when I tried to build > libreoffice-langpack (other than en-GB) with md5sum checking > enabled (using slpkg). > > The build fails, because each langpack has another md5sum, and > > > contains the md5sum only for the en-GB pack. > > Question is, should we: > > 1. create a "cloned" slackbuild for each langpack with a valid > DOWNLOAD and MD5SUM in .nfo > > or > > 2. modify the SlackBuild and .nfo to include all languages by > default > > or > > 3. leave it as it is? if you plan to build other lang pack, i suggest you use the tarball and run it with LO-LANG= sh ./libreoffice-langpack.SlackBuild as mentioned in the README if you use an automatic tool, it will fail because the CHECKSUM will only be applied to the en-GB source only - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTkgm8ACgkQiHuDdNczM4HWhQCeOuW4Beg/FEEpXRfPp0oMsNjJ IP8An26bgRfF3cQedU8mNvmL9nktLRRR =DAAr -----END PGP SIGNATURE----- From s.arcus at open-t.co.uk Wed Feb 18 15:05:56 2015 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 18 Feb 2015 15:05:56 +0000 Subject: [Slackbuilds-users] Upcoming version of Apcupsd breaks SBo script Message-ID: <54E4AA54.3070504@open-t.co.uk> This is actually a fix which has broken other things :-) On the Apcupsd mailing list, I've followed up the issue of the Slackware scripts having lock files in "/var/lock/subsys", which appears to be specific to Redhat. They've been very receptive and kindly patched the Slackware scripts. However, this seems to have broken the current SBo script when applied to the the new Apcupsd (3.14.13). Full thread regarding the above here: http://apcupsd-ups-control-software.10985.n7.nabble.com/Slackware-startup-script-td8898.html From mancha1 at hush.com Wed Feb 18 20:32:07 2015 From: mancha1 at hush.com (mancha) Date: Wed, 18 Feb 2015 20:32:07 +0000 Subject: [Slackbuilds-users] xrdp v0.6.1 multiple issues Message-ID: <20150218203207.4162AC03E6@smtp.hushmail.com> As Alex reports on LQ (https://tinyurl.com/o2wsgyf), xrdp has a bug when checking for disabled shadow accounts. I developed a fix which has been accepted by upstream. Fix: http://sf.net/projects/mancha/files/misc/xrdp-v0.6.1_disabled.diff In addition, xrdp 0.6.1 has a few more problems I developed patches for based on xrdp's development branch: 1. segfault on NULL return from glibc (as can happen on glibc 2.17 onwards) and inability to validate shadow passwords hashed with SHA256 or SHA512 (Slackware 14.0 onwards defaults to SHA256-hashed passwords). Fix: http://sf.net/projects/mancha/files/sec/xrdp-v0.6.1_crypt.diff 2. states aren't cleared between connections leading to unpredictable behavior when changing modules and/or module parameters in the xrdp login window. Fix: http://sf.net/projects/mancha/files/misc/xrdp-v0.6.1_cleanup-state.diff Feel free to use them in SBo's xrdp package. --mancha From willysr at slackbuilds.org Fri Feb 20 09:10:26 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 20 Feb 2015 16:10:26 +0700 Subject: [Slackbuilds-users] xrdp v0.6.1 multiple issues In-Reply-To: <20150218203207.4162AC03E6@smtp.hushmail.com> References: <20150218203207.4162AC03E6@smtp.hushmail.com> Message-ID: <54E6FA02.7050307@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > As Alex reports on LQ (https://tinyurl.com/o2wsgyf), xrdp has a bug > when checking for disabled shadow accounts. > > I developed a fix which has been accepted by upstream. > > Fix: > http://sf.net/projects/mancha/files/misc/xrdp-v0.6.1_disabled.diff > > In addition, xrdp 0.6.1 has a few more problems I developed patches > for based on xrdp's development branch: > > 1. segfault on NULL return from glibc (as can happen on glibc 2.17 > onwards) and inability to validate shadow passwords hashed with > SHA256 or SHA512 (Slackware 14.0 onwards defaults to SHA256-hashed > passwords). > > Fix: > http://sf.net/projects/mancha/files/sec/xrdp-v0.6.1_crypt.diff > > 2. states aren't cleared between connections leading to > unpredictable behavior when changing modules and/or module > parameters in the xrdp login window. > > Fix: > http://sf.net/projects/mancha/files/misc/xrdp-v0.6.1_cleanup-state.diff > > Feel free to use them in SBo's xrdp package. Pushed to my branch Thanks for the efforts Mancha! - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTm+gIACgkQiHuDdNczM4FkdwCdE/v9p5fLt+J/HI0pk1feioYu MjAAnAle2l5l66Z0WgTTwaXtbQ+/gc5g =EWh8 -----END PGP SIGNATURE----- From slackbuilds at rochefort.de Sat Feb 21 00:27:44 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sat, 21 Feb 2015 01:27:44 +0100 Subject: [Slackbuilds-users] Slackbuild helper script Message-ID: <54E7D100.9020606@rochefort.de> Hi all I'm using Slackbuilds for a month or so by now, and I am pretty impressed by how well they work. So I started to write a bash script to simplify / automate the build & install process a bit. By now it has evolved into something which allows me to query, install and upgrade slackbuilds, do basic direct-dependency checking and md5sum checking and even automated inclusion of self written patches. The usage syntax is similar to slackpkg. It's certainly far from being perfect and should be considered as a work in progress, but it works reasonably well at least on my system already. The only dependencies are bash, wget, curl and obviously the build tools required for the Slackbuilds themselves. I was wondering if this is something that would be of interest for the community or if everybody has their own solutions in place anyways. If there is interest please let me know and please also advise what would be the preferred way of sharing it, as it was not obvious to me from the Slackbuilds.org site FAQ how to contribute scripts that are not actual slackbuild scripts... Cheers Enguerrand From miguel at thedeanda.com Sat Feb 21 00:32:00 2015 From: miguel at thedeanda.com (Miguel De Anda) Date: Fri, 20 Feb 2015 16:32:00 -0800 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E7D100.9020606@rochefort.de> References: <54E7D100.9020606@rochefort.de> Message-ID: did you check out http://www.sbopkg.org/ ? it sounds kind of similar. maybe join forces to create a super sbopkg script! On Fri, Feb 20, 2015 at 4:27 PM, Enguerrand de Rochefort < slackbuilds at rochefort.de> wrote: > Hi all > > I'm using Slackbuilds for a month or so by now, and I am pretty impressed > by how well they work. So I started to write a bash script to simplify / > automate the build & install process a bit. > > By now it has evolved into something which allows me to query, install and > upgrade slackbuilds, do basic direct-dependency checking and md5sum > checking and even automated inclusion of self written patches. The usage > syntax is similar to slackpkg. > It's certainly far from being perfect and should be considered as a work > in progress, but it works reasonably well at least on my system already. > > The only dependencies are bash, wget, curl and obviously the build tools > required for the Slackbuilds themselves. > > I was wondering if this is something that would be of interest for the > community or if everybody has their own solutions in place anyways. If > there is interest please let me know and please also advise what would be > the preferred way of sharing it, as it was not obvious to me from the > Slackbuilds.org site FAQ how to contribute scripts that are not actual > slackbuild scripts... > > Cheers > Enguerrand > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Sat Feb 21 00:42:33 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 20 Feb 2015 16:42:33 -0800 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: References: <54E7D100.9020606@rochefort.de> Message-ID: On 2/20/15, Miguel De Anda wrote: > did you check out http://www.sbopkg.org/ ? it sounds kind of similar. maybe > join forces to create a super sbopkg script! There is also: sqg, sbotools, and slpkg And probably a few more I have forgotten. sbotools and slpkg are available on SBo itself (is this an Inception thing? ha). I'd say why not have your tool installable via a SlackBuild? > > On Fri, Feb 20, 2015 at 4:27 PM, Enguerrand de Rochefort < > slackbuilds at rochefort.de> wrote: > >> Hi all >> >> I'm using Slackbuilds for a month or so by now, and I am pretty impressed >> by how well they work. So I started to write a bash script to simplify / >> automate the build & install process a bit. >> >> By now it has evolved into something which allows me to query, install >> and >> upgrade slackbuilds, do basic direct-dependency checking and md5sum >> checking and even automated inclusion of self written patches. The usage >> syntax is similar to slackpkg. >> It's certainly far from being perfect and should be considered as a work >> in progress, but it works reasonably well at least on my system already. >> >> The only dependencies are bash, wget, curl and obviously the build tools >> required for the Slackbuilds themselves. >> >> I was wondering if this is something that would be of interest for the >> community or if everybody has their own solutions in place anyways. If >> there is interest please let me know and please also advise what would be >> the preferred way of sharing it, as it was not obvious to me from the >> Slackbuilds.org site FAQ how to contribute scripts that are not actual >> slackbuild scripts... >> >> Cheers >> Enguerrand >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > -- --- From slackbuilds at rochefort.de Sat Feb 21 01:20:23 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sat, 21 Feb 2015 02:20:23 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: References: <54E7D100.9020606@rochefort.de> Message-ID: <54E7DD57.4060407@rochefort.de> Hi Miguel, hi Ryan just had a look at sbopkg... that looks like a serious piece of work. My approach is a lot more "minimalistic" I guess... I gather there is probably no real benefit from yet another tool (although I personally will probably stick to it, just for the fun of developing it, plus it's always easier to "fiddle" with self-written code.) I will take a look at the ones you mentioned though, and compare. I like the idea of making it a slackbuild. If at some point it gets mature enough and provides added value compared to what's already available I'll certainly do that. If other tools are known that where not mentioned so far please continue throwing the names at me so I can get a complete picture... One thought I am getting while I am writing this is that such a list should actually be added to the FAQ. (Can't imagine this isn't a frequently asked question...) On 21.02.2015 01:42, Ryan P.C. McQuen wrote: > On 2/20/15, Miguel De Anda wrote: >> did you check out http://www.sbopkg.org/ ? it sounds kind of similar. maybe >> join forces to create a super sbopkg script! > > There is also: > > sqg, sbotools, and slpkg > > And probably a few more I have forgotten. > > sbotools and slpkg are available on SBo itself (is this an Inception thing? ha). > > I'd say why not have your tool installable via a SlackBuild? > > >> >> On Fri, Feb 20, 2015 at 4:27 PM, Enguerrand de Rochefort < >> slackbuilds at rochefort.de> wrote: >> >>> Hi all >>> >>> I'm using Slackbuilds for a month or so by now, and I am pretty impressed >>> by how well they work. So I started to write a bash script to simplify / >>> automate the build & install process a bit. >>> >>> By now it has evolved into something which allows me to query, install >>> and >>> upgrade slackbuilds, do basic direct-dependency checking and md5sum >>> checking and even automated inclusion of self written patches. The usage >>> syntax is similar to slackpkg. >>> It's certainly far from being perfect and should be considered as a work >>> in progress, but it works reasonably well at least on my system already. >>> >>> The only dependencies are bash, wget, curl and obviously the build tools >>> required for the Slackbuilds themselves. >>> >>> I was wondering if this is something that would be of interest for the >>> community or if everybody has their own solutions in place anyways. If >>> there is interest please let me know and please also advise what would be >>> the preferred way of sharing it, as it was not obvious to me from the >>> Slackbuilds.org site FAQ how to contribute scripts that are not actual >>> slackbuild scripts... >>> >>> Cheers >>> Enguerrand >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - http://slackbuilds.org/faq/ >>> >>> >> > > From klaatu at straightedgelinux.com Sat Feb 21 01:32:11 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Sat, 21 Feb 2015 14:32:11 +1300 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E7DD57.4060407@rochefort.de> References: <54E7D100.9020606@rochefort.de> <54E7DD57.4060407@rochefort.de> Message-ID: <54E7E01B.4040000@straightedgelinux.com> Only because you asked: gitorious.org/slackport It's a tool that I wrote for myself because sbopkg, at the time, did not have an easy way for me to view both the README and the .info file in one command, on the same screen. It's not very fancy, either. -klaatu On 02/21/2015 02:20 PM, Enguerrand de Rochefort wrote: > Hi Miguel, hi Ryan > > just had a look at sbopkg... that looks like a serious piece of work. My > approach is a lot more "minimalistic" I guess... > > I gather there is probably no real benefit from yet another tool > (although I personally will probably stick to it, just for the fun of > developing it, plus it's always easier to "fiddle" with self-written code.) > > I will take a look at the ones you mentioned though, and compare. I like > the idea of making it a slackbuild. If at some point it gets mature > enough and provides added value compared to what's already available > I'll certainly do that. > > If other tools are known that where not mentioned so far please continue > throwing the names at me so I can get a complete picture... > > One thought I am getting while I am writing this is that such a list > should actually be added to the FAQ. (Can't imagine this isn't a > frequently asked question...) > > > > > On 21.02.2015 01:42, Ryan P.C. McQuen wrote: >> On 2/20/15, Miguel De Anda wrote: >>> did you check out http://www.sbopkg.org/ ? it sounds kind of similar. >>> maybe >>> join forces to create a super sbopkg script! >> >> There is also: >> >> sqg, sbotools, and slpkg >> >> And probably a few more I have forgotten. >> >> sbotools and slpkg are available on SBo itself (is this an Inception >> thing? ha). >> >> I'd say why not have your tool installable via a SlackBuild? >> >> >>> >>> On Fri, Feb 20, 2015 at 4:27 PM, Enguerrand de Rochefort < >>> slackbuilds at rochefort.de> wrote: >>> >>>> Hi all >>>> >>>> I'm using Slackbuilds for a month or so by now, and I am pretty >>>> impressed >>>> by how well they work. So I started to write a bash script to >>>> simplify / >>>> automate the build & install process a bit. >>>> >>>> By now it has evolved into something which allows me to query, install >>>> and >>>> upgrade slackbuilds, do basic direct-dependency checking and md5sum >>>> checking and even automated inclusion of self written patches. The >>>> usage >>>> syntax is similar to slackpkg. >>>> It's certainly far from being perfect and should be considered as a >>>> work >>>> in progress, but it works reasonably well at least on my system >>>> already. >>>> >>>> The only dependencies are bash, wget, curl and obviously the build >>>> tools >>>> required for the Slackbuilds themselves. >>>> >>>> I was wondering if this is something that would be of interest for the >>>> community or if everybody has their own solutions in place anyways. If >>>> there is interest please let me know and please also advise what >>>> would be >>>> the preferred way of sharing it, as it was not obvious to me from the >>>> Slackbuilds.org site FAQ how to contribute scripts that are not actual >>>> slackbuild scripts... >>>> >>>> Cheers >>>> Enguerrand >>>> _______________________________________________ >>>> SlackBuilds-users mailing list >>>> SlackBuilds-users at slackbuilds.org >>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>>> FAQ - http://slackbuilds.org/faq/ >>>> >>>> >>> >> >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From willysr at slackbuilds.org Sat Feb 21 02:18:12 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 21 Feb 2015 09:18:12 +0700 Subject: [Slackbuilds-users] Updates - 20150221.1 Message-ID: <54E7EAE4.7050505@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Small Note: Christoph Willing sent an update to VLC since there's a change in freerdp, but apparently it was too late since i already finished merging all the changes and the public update process has been started. Nevertheless, it will be included in my branch soon, so if you need to grab the patch, take it from my branch Sat Feb 21 02:05:18 UTC 2015 academic/sage: Updated for version 6.5. academic/xoscope: Updated for version 2.1. audio/id3: Updated for version 0.79. audio/yoshimi: Updated for version 1.3.2. desktop/meliae-icon-theme: Added (Meliae SVG icons). desktop/plasma-geek-clock: Added (Geek Clock plasmoid). desktop/qlandkartegt: Updated for version 1.8.1. desktop/wmcube: Updated for version 1.0.1. desktop/wminfo: Updated for version 4.2.0. desktop/xfce4-whiskermenu-plugin: Updated for version 1.5.0. development/bluefish: Updated for version 2.2.7. development/bpython: Updated for version 0.14. development/cgit: Updated for version 0.11.0. development/dbeaver: Updated for version 3.1.4. development/ebe: Updated for version 2.7.3. games/adl: Added (compiler and runtime). games/angband: Updated for version v3.5.1. games/freeminer: Updated for version 0.4.12.6. games/instead: Updated for version 2.2.2. games/mednafen: Updated for version 0.9.38.2. games/minetest: Updated for version 0.4.12. games/minetest_game: Updated for version 0.4.12. games/nFlood: Fix homepage. games/openclonk: Updated for version 5.5.1. games/term2048: Updated for version 0.2.5. games/vcmi: Updated for version 0.97. games/vms-empire: Updated for version 1.13. gis/geopy: Updated for version 1.9.1. gis/polyline: Added (Encoded Polyline Algorithm). graphics/aewan: Added (animation editor). graphics/bdfedit: Added (Tcl/TK based editor for BDF fonts). graphics/blender: Updated for version 2.73a. graphics/fritzing: Updated for version 0.9.1b. graphics/gimagereader: Updated for version 3.0.1. ham/chirp: Updated for version 0.4.1. libraries/fuzzylite: Added (control library in C++). libraries/grx: Updated for version 249. libraries/libopensync: Update DOWNLOAD url. libraries/live555: Updated for version 2015.02.17. libraries/poco: Updated for version 1.6.0. libraries/rarfile: Fix homepage. libraries/stfl: Fix misplaced example file. misc/dos2unix: Updated for version 7.2. misc/dvtm: Upgraded for version 0.14. misc/qtspell: Added (Spell checking). network/Flootty: Updated for version 3.1.2. network/bitcoin: Updated for version 0.10.0. network/connman: Updated for version 1.28. network/etherpoke: Updated for version 2.1.2. network/flexget: Updated for version 1.2.280. network/iojs: Updated for version 1.3.0. network/livestreamer-curses: Updated for version 1.5.0. network/mps-youtube: Updated for version 0.2.3. network/newsbeuter: Updated for version 2.9. network/nzbget: Updated for version 14.2. network/remmina: Updated for version 1.2.0-rcgit.1 + new maintainer. network/seafile-server: Enabled client + fixed README. network/translate: Updated for version 1.0.7. network/zabbix_agentd: Updated for version 2.4.3. network/zabbix_proxy: Updated for version 2.4.3. network/zabbix_server: Updated for version 2.4.3. office/CherryTree: Updated for version 0.35.7. office/MasterPDFEditor: Fix SOURCEARCH. office/taskjuggler: Fix README. python/coverage: Updated for version 4.0a5. python/python-oauthlib: Fix MD5SUM. python/s3cmd: Updated for version 1.5.2. python/statsmodels: Fixed VERSION. ruby/heroku-client: Updated for version 3.26.1. system/asbt: Updated for version 1.3. system/multicorn: Updated for version 1.1.0. system/nvidia-legacy340-driver: Fix DEPS. system/profile-sync-daemon: Updated for version 5.69. system/slpkg: Updated for version 2.2.3. system/suhosin: Added (PHP Protection System) system/termenu: Updated for version 1.1.5. system/watch-fs: Updated for version 1.3.1. system/xrdp: Rebuilt with patches. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTn6uQACgkQiHuDdNczM4Ff0ACeJfps4A7YPoEQTYP1OJt/Vujt JgsAoIQ670yyhV8zxcZM4ZZ0G0m1jaoz =KtaW -----END PGP SIGNATURE----- From mancha1 at hush.com Sat Feb 21 03:56:08 2015 From: mancha1 at hush.com (mancha) Date: Sat, 21 Feb 2015 03:56:08 +0000 (UTC) Subject: [Slackbuilds-users] xrdp v0.6.1 multiple issues References: <20150218203207.4162AC03E6@smtp.hushmail.com> <54E6FA02.7050307@slackbuilds.org> Message-ID: Willy Sudiarto Raharjo writes: > Pushed to my branch > > Thanks for the efforts Mancha! Good times. --mancha From genghiskhan at gmx.ca Sat Feb 21 07:24:31 2015 From: genghiskhan at gmx.ca (Genghis Khan) Date: Sat, 21 Feb 2015 08:24:31 +0100 Subject: [Slackbuilds-users] DOWN http://www.hds619.net/Jeex.php Message-ID: # slapt-src -i jeex The following packages will be installed: jeex Do you want to continue? [y/N] y Fetching README...Done Fetching doinst.sh...Done Fetching jeex.SlackBuild...Done Fetching jeex.info...Done Fetching slack-desc...Done Fetching http://www.hds619.net/data/jeex/jeex-pkg/jeex-12.6.1.tar.bz2...Done MD5SUM mismatch for jeex-12.6.1.tar.bz2 -- Ekiga 5 ? Progress Report http://blog.ekiga.net/?p=201 Are you interested in helping? Ekiga needs you! From xavier at maillard.im Sat Feb 21 08:36:09 2015 From: xavier at maillard.im (Xavier Maillard) Date: Sat, 21 Feb 2015 09:36:09 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E7D100.9020606@rochefort.de> References: <54E7D100.9020606@rochefort.de> Message-ID: Hi, Enguerrand de Rochefort writes: > Hi all > > I'm using Slackbuilds for a month or so by now, and I am pretty > impressed by how well they work. So I started to write a bash > script to simplify / automate the build & install process a bit. There is already something like that. Check sbopkg [1]. Footnotes: [1] http://sbopkg.org -- Sent with my mu4e -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 1494 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Feb 21 11:54:37 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 21 Feb 2015 18:54:37 +0700 Subject: [Slackbuilds-users] DOWN http://www.hds619.net/Jeex.php In-Reply-To: References: Message-ID: <54E871FD.3010407@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > # slapt-src -i jeex The following packages will be installed: jeex > Do you want to continue? [y/N] y Fetching README...Done Fetching > doinst.sh...Done Fetching jeex.SlackBuild...Done Fetching > jeex.info...Done Fetching slack-desc...Done Fetching > http://www.hds619.net/data/jeex/jeex-pkg/jeex-12.6.1.tar.bz2...Done > > MD5SUM mismatch for jeex-12.6.1.tar.bz2 the domain is no longer active, so unless someone has the source and host it somewhere, the SlackBuild is not really useful. - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTocfwACgkQiHuDdNczM4Hr7gCgmLe5Lptu01mrbjy+/GyVLEbJ yXoAoJQBiTOO59Q0GgWOhhIdpdhXZkjL =vZga -----END PGP SIGNATURE----- From ryan.q at linux.com Sat Feb 21 12:32:32 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 21 Feb 2015 12:32:32 +0000 Subject: [Slackbuilds-users] Slackbuild helper script References: <54E7D100.9020606@rochefort.de> Message-ID: I wrote a small shell function I use for non-SBo stuff (I am a big fan of sbopkg), but there is no reason it could not be used for a local SBo clone. ;-) ## install packages from my unofficial github repo my_repo_install() { ## set to wherever yours is MY_REPO=~/ryanpc-slackbuilds/unofficial ## just do one initial pull cd ${MY_REPO}/ git pull ## begin the beguine for ITEM in "$@"; do MY_REPO_PKG=$ITEM ## check if it is already installed if [ -z "`find /var/log/packages/ -name ${MY_REPO_PKG}-*`" ]; then cd ${MY_REPO}/${MY_REPO_PKG}/ . ${MY_REPO}/${MY_REPO_PKG}/${MY_REPO_PKG}.info ## no use trying to download if these vars are empty if [ "$DOWNLOAD" ] || [ "$DOWNLOAD_x86_64" ]; then if [ "$(uname -m)" = "x86_64" ] && [ "$DOWNLOAD_x86_64" ] && [ "$DOWNLOAD_x86_64" != "UNSUPPORTED" ] && [ "$DOWNLOAD_x86_64" != "UNTESTED" ]; then wget -N $DOWNLOAD_x86_64 -P ${MY_REPO}/${MY_REPO_PKG}/ else wget -N $DOWNLOAD -P ${MY_REPO}/${MY_REPO_PKG}/ fi fi ## finally run the build sh ${MY_REPO}/${MY_REPO_PKG}/${MY_REPO_PKG}.SlackBuild ls -t --color=never /tmp/${MY_REPO_PKG}-*_SBo.tgz | head -1 | xargs -i upgradepkg --install-new {} cd fi done } On Sat, Feb 21, 2015, 12:36 AM Xavier Maillard wrote: > Hi, > > Enguerrand de Rochefort writes: > > > Hi all > > > > I'm using Slackbuilds for a month or so by now, and I am pretty > > impressed by how well they work. So I started to write a bash > > script to simplify / automate the build & install process a bit. > > There is already something like that. Check sbopkg [1]. > > Footnotes: > [1] http://sbopkg.org > > -- > Sent with my mu4e > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.venken at online.be Sat Feb 21 13:26:15 2015 From: k.venken at online.be (Karel Venken) Date: Sat, 21 Feb 2015 14:26:15 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E7D100.9020606@rochefort.de> References: <54E7D100.9020606@rochefort.de> Message-ID: <54E88777.7090704@online.be> Hi, You somewhat mentioned it,... A few years ago, when I started with Slackware, I followed the same path. I have written my own script, which I am still using. Same idea, make it with the minimum amount of requirements, as a simple bash script. I especially wanted this script to do all the work for me. Like this,... # getpkgs -gr vlc wait somewhat, have a coffee and that's it... You have everything (vlc in the example) running - dependencies added as well. As expected, my script often fails (read the slackbuilds.org FAQ carefully ;-) for why) but I never felt the need to fix these cases, so it has its problems. However if you - or anyone else - wants to give it a look, use it, copy it, let me know... (it's around 24k size) K. Enguerrand de Rochefort wrote: > Hi all > > I'm using Slackbuilds for a month or so by now, and I am pretty > impressed by how well they work. So I started to write a bash script > to simplify / automate the build & install process a bit. > > By now it has evolved into something which allows me to query, install > and upgrade slackbuilds, do basic direct-dependency checking and > md5sum checking and even automated inclusion of self written patches. > The usage syntax is similar to slackpkg. > It's certainly far from being perfect and should be considered as a > work in progress, but it works reasonably well at least on my system > already. > > The only dependencies are bash, wget, curl and obviously the build > tools required for the Slackbuilds themselves. > > I was wondering if this is something that would be of interest for the > community or if everybody has their own solutions in place anyways. If > there is interest please let me know and please also advise what would > be the preferred way of sharing it, as it was not obvious to me from > the Slackbuilds.org site FAQ how to contribute scripts that are not > actual slackbuild scripts... > > Cheers > Enguerrand > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From slackbuilds at rochefort.de Sat Feb 21 14:20:53 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sat, 21 Feb 2015 15:20:53 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E88777.7090704@online.be> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> Message-ID: <54E89445.4060601@rochefort.de> Hi Karel I guess that this is a very typical path for somebody new to slackware. If you decide to use Slackware, chances are you actually want to do things yourself. Part of me expected that I'd get the type of answers I got, it was no big surprise to learn that there are other solutions in place. At the same time it felt strange to benefit from the great things this community is producing and not letting people know that there is something I created and that I'd be willing to share. I'd definitely be interested to take a look at everything that's available - including your script - and possibly do some cherry-picking to incorporate stuff into my own solution. Cheers Enguerrand On 21.02.2015 14:26, Karel Venken wrote: > Hi, > > You somewhat mentioned it,... > > A few years ago, when I started with Slackware, I followed the same path. I have written my own script, which I am still using. Same idea, make it with the minimum amount of requirements, as a simple bash script. I especially wanted this script to do all the work for me. Like this,... > > # getpkgs -gr vlc > > wait somewhat, have a coffee and that's it... You have everything (vlc in the example) running - dependencies added as well. As expected, my script often fails (read the slackbuilds.org FAQ carefully ;-) for why) but I never felt the need to fix these cases, so it has its problems. > > However if you - or anyone else - wants to give it a look, use it, copy it, let me know... (it's around 24k size) > > K. > > > > Enguerrand de Rochefort wrote: >> Hi all >> >> I'm using Slackbuilds for a month or so by now, and I am pretty impressed by how well they work. So I started to write a bash script to simplify / automate the build & install process a bit. >> >> By now it has evolved into something which allows me to query, install and upgrade slackbuilds, do basic direct-dependency checking and md5sum checking and even automated inclusion of self written patches. The usage syntax is similar to slackpkg. >> It's certainly far from being perfect and should be considered as a work in progress, but it works reasonably well at least on my system already. >> >> The only dependencies are bash, wget, curl and obviously the build tools required for the Slackbuilds themselves. >> >> I was wondering if this is something that would be of interest for the community or if everybody has their own solutions in place anyways. If there is interest please let me know and please also advise what would be the preferred way of sharing it, as it was not obvious to me from the Slackbuilds.org site FAQ how to contribute scripts that are not actual slackbuild scripts... >> >> Cheers >> Enguerrand >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From ryan.q at linux.com Sat Feb 21 14:59:05 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 21 Feb 2015 06:59:05 -0800 Subject: [Slackbuilds-users] DOWN http://www.hds619.net/Jeex.php In-Reply-To: <54E871FD.3010407@slackbuilds.org> References: <54E871FD.3010407@slackbuilds.org> Message-ID: On 2/21/15, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> # slapt-src -i jeex The following packages will be installed: jeex >> Do you want to continue? [y/N] y Fetching README...Done Fetching >> doinst.sh...Done Fetching jeex.SlackBuild...Done Fetching >> jeex.info...Done Fetching slack-desc...Done Fetching >> http://www.hds619.net/data/jeex/jeex-pkg/jeex-12.6.1.tar.bz2...Done >> >> > MD5SUM mismatch for jeex-12.6.1.tar.bz2 > > the domain is no longer active, so unless someone has the source and > host it somewhere, the SlackBuild is not really useful. > > David Spencer saved the day! http://slackbuilds.org/cgit/slackbuilds/commit/?id=6f7c87cc9 > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlTocfwACgkQiHuDdNczM4Hr7gCgmLe5Lptu01mrbjy+/GyVLEbJ > yXoAoJQBiTOO59Q0GgWOhhIdpdhXZkjL > =vZga > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- --- From k.venken at online.be Sat Feb 21 18:26:40 2015 From: k.venken at online.be (Karel Venken) Date: Sat, 21 Feb 2015 19:26:40 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E89445.4060601@rochefort.de> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> Message-ID: <54E8CDE0.4080004@online.be> Enguerrand de Rochefort wrote: > Hi Karel > > I guess that this is a very typical path for somebody new to > slackware. If you decide to use Slackware, chances are you actually > want to do things yourself. Part of me expected that I'd get the type > of answers I got, it was no big surprise to learn that there are other > solutions in place. > > At the same time it felt strange to benefit from the great things this > community is producing and not letting people know that there is > something I created and that I'd be willing to share. I am happy you like it, it is a great community and I have always had a lot of help myself! > I'd definitely be interested to take a look at everything that's > available - including your script - and possibly do some > cherry-picking to incorporate stuff into my own solution. It is in my notes (consider this a temporary link) http://users.online.be/~cd003081/slackware/packman/getpkgs Chances are slim it is what you want - I wrote it for myself- , but don't hesitate to comment and use it any way you see fit. regards, K. > Cheers > Enguerrand > > > > On 21.02.2015 14:26, Karel Venken wrote: >> Hi, >> >> You somewhat mentioned it,... >> >> A few years ago, when I started with Slackware, I followed the same >> path. I have written my own script, which I am still using. Same >> idea, make it with the minimum amount of requirements, as a simple >> bash script. I especially wanted this script to do all the work for >> me. Like this,... >> >> # getpkgs -gr vlc >> >> wait somewhat, have a coffee and that's it... You have everything >> (vlc in the example) running - dependencies added as well. As >> expected, my script often fails (read the slackbuilds.org FAQ >> carefully ;-) for why) but I never felt the need to fix these cases, >> so it has its problems. >> >> However if you - or anyone else - wants to give it a look, use it, >> copy it, let me know... (it's around 24k size) >> >> K. >> >> >> >> Enguerrand de Rochefort wrote: >>> Hi all >>> >>> I'm using Slackbuilds for a month or so by now, and I am pretty >>> impressed by how well they work. So I started to write a bash script >>> to simplify / automate the build & install process a bit. >>> >>> By now it has evolved into something which allows me to query, >>> install and upgrade slackbuilds, do basic direct-dependency checking >>> and md5sum checking and even automated inclusion of self written >>> patches. The usage syntax is similar to slackpkg. >>> It's certainly far from being perfect and should be considered as a >>> work in progress, but it works reasonably well at least on my system >>> already. >>> >>> The only dependencies are bash, wget, curl and obviously the build >>> tools required for the Slackbuilds themselves. >>> >>> I was wondering if this is something that would be of interest for >>> the community or if everybody has their own solutions in place >>> anyways. If there is interest please let me know and please also >>> advise what would be the preferred way of sharing it, as it was not >>> obvious to me from the Slackbuilds.org site FAQ how to contribute >>> scripts that are not actual slackbuild scripts... >>> >>> Cheers >>> Enguerrand >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - http://slackbuilds.org/faq/ >>> >>> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From k.venken at online.be Sat Feb 21 18:33:50 2015 From: k.venken at online.be (Karel Venken) Date: Sat, 21 Feb 2015 19:33:50 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E8CDE0.4080004@online.be> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> <54E8CDE0.4080004@online.be> Message-ID: <54E8CF8E.5000806@online.be> Enguerrand, Just in case you may want to use it, you can find some description of its usage http://users.online.be/~cd003081/slackware/getting_packages.html If you do, let me know if something is broken K. From slackbuilds at rochefort.de Sat Feb 21 19:53:44 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sat, 21 Feb 2015 20:53:44 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E8CDE0.4080004@online.be> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> <54E8CDE0.4080004@online.be> Message-ID: <54E8E248.9050506@rochefort.de> Really interesting to see / compare how others tackled the same thing in different ways. My first takeaway was the "look at info and readme file in one go" mentioned earlier, which is so useful that I can't see how I missed that. On 21.02.2015 19:26, Karel Venken wrote: > Enguerrand de Rochefort wrote: >> Hi Karel >> >> I guess that this is a very typical path for somebody new to slackware. If you decide to use Slackware, chances are you actually want to do things yourself. Part of me expected that I'd get the type of answers I got, it was no big surprise to learn that there are other solutions in place. >> >> At the same time it felt strange to benefit from the great things this community is producing and not letting people know that there is something I created and that I'd be willing to share. > I am happy you like it, it is a great community and I have always had a lot of help myself! >> I'd definitely be interested to take a look at everything that's available - including your script - and possibly do some cherry-picking to incorporate stuff into my own solution. > It is in my notes (consider this a temporary link) > > http://users.online.be/~cd003081/slackware/packman/getpkgs > > Chances are slim it is what you want - I wrote it for myself- , but don't hesitate to comment and use it any way you see fit. > > regards, > > K. >> Cheers >> Enguerrand >> >> >> >> On 21.02.2015 14:26, Karel Venken wrote: >>> Hi, >>> >>> You somewhat mentioned it,... >>> >>> A few years ago, when I started with Slackware, I followed the same path. I have written my own script, which I am still using. Same idea, make it with the minimum amount of requirements, as a simple bash script. I especially wanted this script to do all the work for me. Like this,... >>> >>> # getpkgs -gr vlc >>> >>> wait somewhat, have a coffee and that's it... You have everything (vlc in the example) running - dependencies added as well. As expected, my script often fails (read the slackbuilds.org FAQ carefully ;-) for why) but I never felt the need to fix these cases, so it has its problems. >>> >>> However if you - or anyone else - wants to give it a look, use it, copy it, let me know... (it's around 24k size) >>> >>> K. >>> >>> >>> >>> Enguerrand de Rochefort wrote: >>>> Hi all >>>> >>>> I'm using Slackbuilds for a month or so by now, and I am pretty impressed by how well they work. So I started to write a bash script to simplify / automate the build & install process a bit. >>>> >>>> By now it has evolved into something which allows me to query, install and upgrade slackbuilds, do basic direct-dependency checking and md5sum checking and even automated inclusion of self written patches. The usage syntax is similar to slackpkg. >>>> It's certainly far from being perfect and should be considered as a work in progress, but it works reasonably well at least on my system already. >>>> >>>> The only dependencies are bash, wget, curl and obviously the build tools required for the Slackbuilds themselves. >>>> >>>> I was wondering if this is something that would be of interest for the community or if everybody has their own solutions in place anyways. If there is interest please let me know and please also advise what would be the preferred way of sharing it, as it was not obvious to me from the Slackbuilds.org site FAQ how to contribute scripts that are not actual slackbuild scripts... >>>> >>>> Cheers >>>> Enguerrand >>>> _______________________________________________ >>>> SlackBuilds-users mailing list >>>> SlackBuilds-users at slackbuilds.org >>>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>>> FAQ - http://slackbuilds.org/faq/ >>>> >>>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - http://slackbuilds.org/faq/ >>> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > From anddt at ukr.net Sat Feb 21 20:27:50 2015 From: anddt at ukr.net (=?UTF-8?B?0JDQvdC00YDRltC5?=) Date: Sat, 21 Feb 2015 22:27:50 +0200 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E7D100.9020606@rochefort.de> References: <54E7D100.9020606@rochefort.de> Message-ID: <54E8EA46.4040302@ukr.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Enguerrand de Rochefort wrote: > Hi all Hi! > > I was wondering if this is something that would be of interest for the community or if everybody has their own solutions in place anyways. If there is interest please let me know and please also advise what would be the preferred way of sharing it, as it was not obvious to me from the Slackbuilds.org site FAQ how to contribute scripts that are not actual slackbuild scripts... > I wrote some bash functions, here: export OPTS="LANG=C NUMJOBS=-j2 TAG=_anddt PKGTYPE=txz TMP=/tmp/AndDT OUTPUT=/srv/ftp/packages-testing" sbdl () { for i in "$@"; do wget $i -O - | tar zxvf - ; done } sbget () { cp -vi -vr $(find /home/anddt/git/SBo -maxdepth 2 -mindepth 2 -type d -name "${1}") . } sbinfo () { find /home/anddt/git/SBo -maxdepth 2 -mindepth 2 -type d -name "${1}" -exec cat {}/${1}.info \; } sbmake () { sbget $1 && cd $1 && sbsrc && sbmk $OPTS2 && cd .. } sbmk () { dtach -c compiling sudo $OPTS "$@" sh ./`pwd |rev |cut -d \/ -f 1 |rev`.SlackBuild } sbmk_log () { ( dtach -c compiling sudo $OPTS "$@" sh ./`pwd |rev |cut -d \/ -f 1 |rev`.SlackBuild ) 2>&1 | tee ./log.txt } sbopending () { curl -s http://slackbuilds.org/pending/ | awk 'NR > 9' | sed -e "s:\ \;:\t:g" -e "s:\/::g" -e "s:::g" -e "s:::g" -e "s:::g" -e "s:::g" -e "s:::g" -e "s:::g" -e "s:
::g" -e :a -e '$d;N;2,4ba' -e 'P;D' } sbreadme () { cat $(find /home/anddt/git/SBo -maxdepth 2 -mindepth 2 -type d -name "${1}")/README* } sbreq () { for i in $(cat $(basename `pwd`).info |grep REQUIRES |cut -d\" -f 2); do echo $i; done } sbsrc () { . $(pwd |rev |cut -d \/ -f 1 |rev).info && for i in $DOWNLOAD; do FILE=$(echo $i |rev |cut -d\/ -f1 |rev); if [ ! -f "./$FILE" ]; then wget $i; else echo "$FILE is already here"; fi; done } Hope it would be useful for you. - -- Andrew -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCgAGBQJU6OpFAAoJENt8ZrcV3IiYFtwP/i8C2op0Cokb1aBHOoW/pvny +6WLtUxXlJMXsrv8+EmU8l7b3i+fZLQjPBCnKaiPkJektqT3HQ3KHNo9STrhOOuf /0r3q/jfD5QyQp1U3nq7iSkBfUd+zM+sotK3bfGjG8eghrRx+RYrtC/smDobeyD5 MkUmt1yzZ7PnowH4uWCQZfHVq3bcR2dVJClrdCgmE4krmm2Yd64a2ZM4V7/fBX7C T6JTM8iKWQIXNsQYXBiKN2xs+rC+iwCPcX4prDGPcxEfuR0sS945kEs+PPBLngfC jrenqbqnF2STVY2txk/tXDsANRuOWPaZyt+gzU/U87tjKJMzCGd07vIEcGPx9/dz xl5AWQzQtP05qd//LK041V0aH1fen2Q3VlEZfYQAipfcBbh7PpNxtiBmp3HxqW3j hdYRfyRjZCwjvRIryWqgP7VykrjYAJbv7qgH4WVQ2oQFW17Gbjoy5+Y/H3oue7rW k7Blt1JzcWnjFPFLc10sPfGtB+dAyrIb7EoKcBqgGfD22OhnTPfgZONvrGm7NgLT HNG8ZXSSe0hpkexHlMGdbKP1mqqddK8Ja4y4M2OnruzDdP0aIp1Fm5oy+dCMtOgf 50CEFzmrXKEgBIwTMh9exk9ecvhN7M36omdWlbI8wY/7vJlXxUXIvrrTFlplcXj0 n1LpNER6ZxFXGRbnOfUB =D0lu -----END PGP SIGNATURE----- From slackbuilds at rochefort.de Sat Feb 21 20:59:57 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sat, 21 Feb 2015 21:59:57 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E8CDE0.4080004@online.be> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> <54E8CDE0.4080004@online.be> Message-ID: <54E8F1CD.4070505@rochefort.de> Hi Karel One comment I have after scanning through your code is that I like the option to download (even recursively) without actually compiling. I should probably include something similar... I take it you made this possible (among other reasons) to be able to apply patches before compiling. One thing I wanted to be able to do was to have patches / customization tweaks being applied automatically everytime I compile a package, (i.e. everytime I upgrade it). So I am putting patch scripts at a central location that are named after the package name. The install function looks for a patch script once the slackbuild tarball is unpacked and asks me if I want to apply it... I think I might look into your code again when I get started with recursive dependency resolution. I saw the postinstall function that looks for changes in the profile, that's definitely one thing I'd have missed in the first attempt, so thanks a lot for sharing. On 21.02.2015 19:26, Karel Venken wrote: > I wrote it for myself- , but don't hesitate to comment and use it any way you see fit. From slackbuilds at rochefort.de Sat Feb 21 21:24:50 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sat, 21 Feb 2015 22:24:50 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E8EA46.4040302@ukr.net> References: <54E7D100.9020606@rochefort.de> <54E8EA46.4040302@ukr.net> Message-ID: <54E8F7A2.3080603@rochefort.de> On 21.02.2015 21:27, ?????? wrote: > export OPTS="LANG=C NUMJOBS=-j2 TAG=_anddt PKGTYPE=txz TMP=/tmp/AndDT Curious about the NUMJOBS variable. Is that something your are setting "just in case" in the hope that the slackbuild scripts will actually use it (which seems to happen only some of times)? Or are you doing something that I'm missing to make sure it's actually being applied? On 21.02.2015 21:27, ?????? wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Enguerrand de Rochefort wrote: >> Hi all > Hi! >> >> I was wondering if this is something that would be of interest for the > community or if everybody has their own solutions in place anyways. If > there is interest please let me know and please also advise what would > be the preferred way of sharing it, as it was not obvious to me from the > Slackbuilds.org site FAQ how to contribute scripts that are not actual > slackbuild scripts... >> > I wrote some bash functions, here: > > export OPTS="LANG=C NUMJOBS=-j2 TAG=_anddt PKGTYPE=txz TMP=/tmp/AndDT > OUTPUT=/srv/ftp/packages-testing" > > sbdl () > { > for i in "$@"; > do > wget $i -O - | tar zxvf - ; > done > } > sbget () > { > cp -vi -vr $(find /home/anddt/git/SBo -maxdepth 2 -mindepth 2 -type > d -name "${1}") . > } > sbinfo () > { > find /home/anddt/git/SBo -maxdepth 2 -mindepth 2 -type d -name > "${1}" -exec cat {}/${1}.info \; > } > sbmake () > { > sbget $1 && cd $1 && sbsrc && sbmk $OPTS2 && cd .. > } > sbmk () > { > dtach -c compiling sudo $OPTS "$@" sh ./`pwd |rev |cut -d \/ -f 1 > |rev`.SlackBuild > } > sbmk_log () > { > ( dtach -c compiling sudo $OPTS "$@" sh ./`pwd |rev |cut -d \/ -f 1 > |rev`.SlackBuild ) 2>&1 | tee ./log.txt > } > sbopending () > { > curl -s http://slackbuilds.org/pending/ | awk 'NR > 9' | sed -e > "s:\ \;:\t:g" -e "s:\/::g" -e "s:::g" -e "s:
::g" -e > "s:::g" -e "s:::g" -e "s:::g" -e "s:::g" -e > "s:
::g" -e :a -e '$d;N;2,4ba' -e 'P;D' > } > sbreadme () > { > cat $(find /home/anddt/git/SBo -maxdepth 2 -mindepth 2 -type d -name > "${1}")/README* > } > sbreq () > { > for i in $(cat $(basename `pwd`).info |grep REQUIRES |cut -d\" -f 2); > do > echo $i; > done > } > sbsrc () > { > . $(pwd |rev |cut -d \/ -f 1 |rev).info && for i in $DOWNLOAD; > do > FILE=$(echo $i |rev |cut -d\/ -f1 |rev); > if [ ! -f "./$FILE" ]; then > wget $i; > else > echo "$FILE is already here"; > fi; > done > } > > Hope it would be useful for you. > > - -- > Andrew > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQIcBAEBCgAGBQJU6OpFAAoJENt8ZrcV3IiYFtwP/i8C2op0Cokb1aBHOoW/pvny > +6WLtUxXlJMXsrv8+EmU8l7b3i+fZLQjPBCnKaiPkJektqT3HQ3KHNo9STrhOOuf > /0r3q/jfD5QyQp1U3nq7iSkBfUd+zM+sotK3bfGjG8eghrRx+RYrtC/smDobeyD5 > MkUmt1yzZ7PnowH4uWCQZfHVq3bcR2dVJClrdCgmE4krmm2Yd64a2ZM4V7/fBX7C > T6JTM8iKWQIXNsQYXBiKN2xs+rC+iwCPcX4prDGPcxEfuR0sS945kEs+PPBLngfC > jrenqbqnF2STVY2txk/tXDsANRuOWPaZyt+gzU/U87tjKJMzCGd07vIEcGPx9/dz > xl5AWQzQtP05qd//LK041V0aH1fen2Q3VlEZfYQAipfcBbh7PpNxtiBmp3HxqW3j > hdYRfyRjZCwjvRIryWqgP7VykrjYAJbv7qgH4WVQ2oQFW17Gbjoy5+Y/H3oue7rW > k7Blt1JzcWnjFPFLc10sPfGtB+dAyrIb7EoKcBqgGfD22OhnTPfgZONvrGm7NgLT > HNG8ZXSSe0hpkexHlMGdbKP1mqqddK8Ja4y4M2OnruzDdP0aIp1Fm5oy+dCMtOgf > 50CEFzmrXKEgBIwTMh9exk9ecvhN7M36omdWlbI8wY/7vJlXxUXIvrrTFlplcXj0 > n1LpNER6ZxFXGRbnOfUB > =D0lu > -----END PGP SIGNATURE----- > From k.venken at online.be Sat Feb 21 21:34:37 2015 From: k.venken at online.be (Karel Venken) Date: Sat, 21 Feb 2015 22:34:37 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E8F1CD.4070505@rochefort.de> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> <54E8CDE0.4080004@online.be> <54E8F1CD.4070505@rochefort.de> Message-ID: <54E8F9ED.6030105@online.be> Enguerrand de Rochefort wrote: > Hi Karel > > One comment I have after scanning through your code is that I like the > option to download (even recursively) without actually compiling. I > should probably include something similar... > I take it you made this possible (among other reasons) to be able to > apply patches before compiling. Indeed, also because I could download it in a separate step and work on if off line if needed. The download step also does not need to be run as root. The same with separation of build and install, you may want to work on it, change options etc... > One thing I wanted to be able to do was to have patches / > customization tweaks being applied automatically everytime I compile a > package, (i.e. everytime I upgrade it). > So I am putting patch scripts at a central location that are named > after the package name. The install function looks for a patch script > once the slackbuild tarball is unpacked and asks me if I want to apply > it... This is definitely missing in my scripts... The only (tiny) changes you can do is specified in the HINTS.TXT file if it is available (basically limited to adding additional/optional packages as dependencies, change versions, show some comments)... > I think I might look into your code again when I get started with > recursive dependency resolution. I saw the postinstall function that > looks for changes in the profile, that's definitely one thing I'd have > missed in the first attempt, so thanks a lot for sharing. Feel free to do so, glad I could give some tips. For recursive dependency resolution, don't count on it to work well. For instance, what you mentioned, even if the script is handling some profile stuff -like setting paths for java-, ones you leave it, it is back to the original environment settings and you still have to source the .profile or logout and login again. One of my (most important) requirements (as I have a few systems to maintain) was to be able to take the script with me on my USB, copy it, and launch it. It should do **all the rest** by itself, even downloading the SLACKBUILDS.TXT if it is not available on the new system. This is a somewhat different goal and as a result, there are much less features, like no possibility of viewing info files - when you use my script, you are supposed to know what you want to install already, although there is a -q option which can give you the proper name and version of the package. No interactive menus etc... But as said, I am happy you can find some usefull tips,... K. From lems at gmx.net Sun Feb 22 09:34:54 2015 From: lems at gmx.net (Leonard Schmidt) Date: Sun, 22 Feb 2015 10:34:54 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E8CDE0.4080004@online.be> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> <54E8CDE0.4080004@online.be> Message-ID: <0MLNeQ-1YQ0tx0P6g-000aL6@mail.gmx.com> Hello, Karel Venken writes: >It is in my notes (consider this a temporary link) > >http://users.online.be/~cd003081/slackware/packman/getpkgs > >Chances are slim it is what you want - I wrote it for myself- , but >don't hesitate to comment and use it any way you see fit. I really like the dependency tree your program produces when using -Hr, very cool! My script is simpler in this regard, and it has problems with large SlackBuilds like thunar-sendto-clamtk (though this is fixed by using -D on such a monster). My tool also has support for so-called .deps and .env files. So my ~/.sboget/options/ffmpeg.deps looks like this: faac:FAAC=yes gsm:GSM=yes openjpeg:JP2=yes lame:LAME=yes OpenAL:OPENAL=yes schroedinger:SCHROEDINGER=yes speex:SPEEX=yes twolame:TWOLAME=yes x264:X264=yes xvidcore:XVID=yes My digikam.deps looks like this: eigen3 libpgf libdc1394 QtGStreamer This allows me to enable optional dependencies, in an .env file one can specify optional variables to pass to the SlackBuild. This is about it. I've been using it for quite some time now to update my systems. It has support for http, rsync or git (I use a NFS-exported directory instead, one only has to change the mirror to rsync or git for this, otherwise it complains). I only began work on this because I already had written a package manager for Slackware (with third-party repository support -- didn't know about slackpkg+ back then). This script is of course not as sophisticated as sbopkg or even slackrepo (by David Spencer), let alone as well-written. Both, sbopkg and slackrepo, are incredible tools, highly sophisticated. I should add that it's an ash script: to be honest I always wanted to dive into (m)ksh programming, but since it's just a hobby for me I never had the time to do it, ash on the other hand is quite simple and was easily understandable. I could probably achieve more if I learnt bash or ksh, but for now this suffices for me. I started uploading my scripts to github, so my SBo tool is available here: https://raw.githubusercontent.com/1ems/scripts/master/sboget (My package manager is called `slacker', in case anyone's interested.) I usually use # sboget -Ssim SlackBuild_I [SlackBuild_II [...]] -S skips a message that should most likely be part of its usage, maybe I'll change this. -s skips already built packages, -i means "build and install the resulting packages" and -m stands for "exact match". It can download SlackBuilds -- in case mirror is http -- and sources only by using -pm, and one can check dependencies without downloading sources by using -Np(m). It supports .info files with multiple sources in their DOWNLOAD variable (like suckless-tools). It has primitive support for using fakeroot as of late, so running as user to build and install packages is possible now. With -gm, one can download only the SlackBuild specified on the command-line (if SBO_MIRROR is http). By default, it saves packages in /usr/SBo/packages/subdir/program, distfiles in /usr/SBo/distfiles/subdir/program, and SlackBuilds in /usr/SBo/slackbuilds. One can also log the whole output into a file (-l), saved in /usr/SBo/log/subdir/program/prog-version-arch-$build$tag.log All of this can be configured via ~/.sboget/config. I'm not sure if instead I should use /etc and /var, but then running as user is not as easy anymore. I usually have different profiles for root and my user, for testing things out et cetera. Regards Leonard From sbolokanov at abv.bg Sun Feb 22 12:35:38 2015 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Sun, 22 Feb 2015 14:35:38 +0200 (EET) Subject: [Slackbuilds-users] FlightGear{,-data}, SimGear updates Message-ID: <2118016297.434221.1424608538328.JavaMail.apache@nm52.abv.bg> Here are a few updates for 3.4.0 release of: FlightGear FlightGear-data SimGear https://github.com/sbolokanov/sbo/commits/master -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Sun Feb 22 15:55:06 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 22 Feb 2015 08:55:06 -0700 Subject: [Slackbuilds-users] i would like to be a maintainer. Message-ID: i would like to be a maintainer of inkscape, kicad & gimp. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Feb 22 16:12:43 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 22 Feb 2015 23:12:43 +0700 Subject: [Slackbuilds-users] i would like to be a maintainer. In-Reply-To: References: Message-ID: <54E9FFFB.4050701@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > i would like to be a maintainer of inkscape, kicad & gimp. GIMP is included in Slackware, so it's not possible to include it in SBo inkscape is maintained by Robby Workman kicad is maintained by Niels Horn, but since he is quite busy, perhaps he isn't mind if someone took care of his packages - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTp//sACgkQiHuDdNczM4EMgwCgov8ksc9QMq8/kR669xdj2apZ TtIAn2fv1YRgRJ2/3V0IozRwwbQNdKSo =h/xT -----END PGP SIGNATURE----- From hostmaster at slackonly.com Sun Feb 22 17:04:34 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 22 Feb 2015 19:04:34 +0200 Subject: [Slackbuilds-users] luxrender Message-ID: <54EA0C22.3050205@slackonly.com> Hi!, luxrender sources missing (returns: Oops, you've found a dead link)... Thanks... From hostmaster at slackonly.com Sun Feb 22 17:37:54 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sun, 22 Feb 2015 19:37:54 +0200 Subject: [Slackbuilds-users] odt2txt Message-ID: <54EA13F2.9020904@slackonly.com> Hi!, odt2txt source is only available from wget... From browser redirects to: https://github.com/dstosberg/odt2txt/ Thanks... From willysr at slackbuilds.org Sun Feb 22 17:52:32 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 23 Feb 2015 00:52:32 +0700 Subject: [Slackbuilds-users] odt2txt In-Reply-To: <54EA13F2.9020904@slackonly.com> References: <54EA13F2.9020904@slackonly.com> Message-ID: <54EA1760.3060606@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > odt2txt source is only available from wget... From browser > redirects to: https://github.com/dstosberg/odt2txt/ Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTqF2AACgkQiHuDdNczM4FoRgCfZ9VkQ+XjWaTj30Yj1cWY4tSW MjkAn2H9iiyOiqcc7NkdUVQVxI2m3dnX =edUa -----END PGP SIGNATURE----- From aaditya_gnulinux at zoho.com Sun Feb 22 18:24:52 2015 From: aaditya_gnulinux at zoho.com (Aaditya Bagga) Date: Sun, 22 Feb 2015 23:54:52 +0530 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: References: Message-ID: <54EA1EF4.3050009@zoho.com> > ------------------------------ > > Message: 5 > Date: Sat, 21 Feb 2015 01:27:44 +0100 > From: Enguerrand de Rochefort > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Slackbuild helper script > Message-ID: <54E7D100.9020606 at rochefort.de> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi all > > I'm using Slackbuilds for a month or so by now, and I am pretty impressed by how well they work. So I started to write a bash script to simplify / automate the build & install process a bit. > > By now it has evolved into something which allows me to query, install and upgrade slackbuilds, do basic direct-dependency checking and md5sum checking and even automated inclusion of self written patches. The usage syntax is similar to slackpkg. > It's certainly far from being perfect and should be considered as a work in progress, but it works reasonably well at least on my system already. > > The only dependencies are bash, wget, curl and obviously the build tools required for the Slackbuilds themselves. > > I was wondering if this is something that would be of interest for the community or if everybody has their own solutions in place anyways. If there is interest please let me know and please also advise what would be the preferred way of sharing it, as it was not obvious to me from the Slackbuilds.org site FAQ how to contribute scripts that are not actual slackbuild scripts... > > Cheers > Enguerrand > > > ------------------------------ > Hi, Seems like lot of us have our tools for the same task :) Mine is: http://slackbuilds.org/repository/14.1/system/asbt/?search=asbt From slackbuilds at rochefort.de Sun Feb 22 21:17:56 2015 From: slackbuilds at rochefort.de (Enguerrand de Rochefort) Date: Sun, 22 Feb 2015 22:17:56 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54EA1EF4.3050009@zoho.com> References: <54EA1EF4.3050009@zoho.com> Message-ID: <54EA4784.5020607@rochefort.de> On 22.02.2015 19:24, Aaditya Bagga wrote: > > Hi, > > Seems like lot of us have our tools for the same task : > > Mine is: http://slackbuilds.org/repository/14.1/system/asbt/?search=asbt Good stuff also. I'll steal the trick to prepend MAKEFLAGS=-j2 to the slackbuild ;-) From k.venken at online.be Sun Feb 22 21:18:50 2015 From: k.venken at online.be (Karel Venken) Date: Sun, 22 Feb 2015 22:18:50 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <0MLNeQ-1YQ0tx0P6g-000aL6@mail.gmx.com> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> <54E8CDE0.4080004@online.be> <0MLNeQ-1YQ0tx0P6g-000aL6@mail.gmx.com> Message-ID: <54EA47BA.4060104@online.be> Leonard Schmidt wrote: > Hello, > > Karel Venken writes: >> It is in my notes (consider this a temporary link) >> >> http://users.online.be/~cd003081/slackware/packman/getpkgs >> >> Chances are slim it is what you want - I wrote it for myself- , but >> don't hesitate to comment and use it any way you see fit. > I really like the dependency tree your program produces when using -Hr, > very cool! Thanks, I needed it when things go wrong to be able to gruadually pinpoint where the problem is. The tree helps to figure this out. I can manually work my way up the tree to see what went wrong. Afterwards, it turned usefull also to have a quick estimate of how much work needs to be done, currently I almost always start with this option, so I have an idea of how many packages needs to be handled. As it already provides the needed slackbuild scripts, I can eventually check the info files if needed. > > My script is simpler in this regard, and it has problems with large > SlackBuilds like thunar-sendto-clamtk (though this is fixed by using -D > on such a monster). My tool also has support for so-called .deps and > .env files. So my ~/.sboget/options/ffmpeg.deps looks like this: > > faac:FAAC=yes > gsm:GSM=yes > openjpeg:JP2=yes > lame:LAME=yes > OpenAL:OPENAL=yes > schroedinger:SCHROEDINGER=yes > speex:SPEEX=yes > twolame:TWOLAME=yes > x264:X264=yes > xvidcore:XVID=yes > > My digikam.deps looks like this: > eigen3 libpgf libdc1394 QtGStreamer > > This allows me to enable optional dependencies, in an .env file one can > specify optional variables to pass to the SlackBuild. This is about it. > I've been using it for quite some time now to update my systems. It has > support for http, rsync or git (I use a NFS-exported directory instead, > one only has to change the mirror to rsync or git for this, otherwise > it complains). Indeed, a logical step, at some point you want to be able to add some dependencies manually. I only added this much later by means of a text file HINTS.TXT, which is parsed for some options, like additional dependencies. But it is all in one file rather then spread over different,... > > I only began work on this because I already had written a package > manager for Slackware (with third-party repository support -- didn't > know about slackpkg+ back then). This script is of course not as > sophisticated as sbopkg or even slackrepo (by David Spencer), let alone > as well-written. Both, sbopkg and slackrepo, are incredible tools, > highly sophisticated. > > I should add that it's an ash script: to be honest I always wanted to > dive into (m)ksh programming, but since it's just a hobby for me I never > had the time to do it, ash on the other hand is quite simple and was > easily understandable. I could probably achieve more if I learnt bash > or ksh, but for now this suffices for me. > > I started uploading my scripts to github, so my SBo tool is available here: > https://raw.githubusercontent.com/1ems/scripts/master/sboget Thanks for sharing this, I looked at your script and it is much more worked out and advanced. Hmmm, my scripting skills need to improve, ;-) ... but if there is still some parts in mine you like, feel free to take it. I have to admit, I started writing scripts just for the fun of it, and because it takes work out of my hands. I also use a few selfmade ones for mounting USB, connecting wireless etc... > > (My package manager is called `slacker', in case anyone's interested.) > > I usually use > # sboget -Ssim SlackBuild_I [SlackBuild_II [...]] > > -S skips a message that should most likely be part of its usage, maybe > I'll change this. -s skips already built packages, -i means "build and > install the resulting packages" and -m stands for "exact match". > > It can download SlackBuilds -- in case mirror is http -- and sources > only by using -pm, and one can check dependencies without downloading > sources by using -Np(m). It supports .info files with multiple sources > in their DOWNLOAD variable (like suckless-tools). It has primitive > support for using fakeroot as of late, so running as user to build and > install packages is possible now. With -gm, one can download only the > SlackBuild specified on the command-line (if SBO_MIRROR is http). > > By default, it saves packages in /usr/SBo/packages/subdir/program, > distfiles in /usr/SBo/distfiles/subdir/program, and SlackBuilds in > /usr/SBo/slackbuilds. One can also log the whole output into a > file (-l), saved in > /usr/SBo/log/subdir/program/prog-version-arch-$build$tag.log > > All of this can be configured via ~/.sboget/config. I'm not sure if > instead I should use /etc and /var, but then running as user is not as > easy anymore. I usually have different profiles for root and my user, > for testing things out et cetera. > > Regards > > Leonard > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From rworkman at slackbuilds.org Sun Feb 22 21:23:42 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 22 Feb 2015 15:23:42 -0600 Subject: [Slackbuilds-users] i would like to be a maintainer. In-Reply-To: <54E9FFFB.4050701@slackbuilds.org> References: <54E9FFFB.4050701@slackbuilds.org> Message-ID: <20150222152342.361e8e72@home.rlworkman.net> On Sun, 22 Feb 2015 23:12:43 +0700 Willy Sudiarto Raharjo wrote: > > i would like to be a maintainer of inkscape, kicad & gimp. > > > GIMP is included in Slackware, so it's not possible to include it in > SBo inkscape is maintained by Robby Workman > kicad is maintained by Niels Horn, but since he is quite busy, perhaps > he isn't mind if someone took care of his packages I don't care much about inkscape since I rarely use it, so sure, you can have it. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From xavier at maillard.im Sun Feb 22 21:37:45 2015 From: xavier at maillard.im (Xavier Maillard) Date: Sun, 22 Feb 2015 22:37:45 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E88777.7090704@online.be> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> Message-ID: Karel Venken writes: > However if you - or anyone else - wants to give it a look, use it, copy > it, let me know... (it's around 24k size) Oh man ! My SB installation workflow goes this way: eval `grep DOWNLOAD package.info` ; wget $DOWNLOAD ; # read package build script and info just in case ./package.SlackBuild That's it ;-) -- Xavier. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 1494 bytes Desc: not available URL: From xavier at maillard.im Sun Feb 22 21:41:32 2015 From: xavier at maillard.im (Xavier Maillard) Date: Sun, 22 Feb 2015 22:41:32 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <54E8CF8E.5000806@online.be> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <54E89445.4060601@rochefort.de> <54E8CDE0.4080004@online.be> <54E8CF8E.5000806@online.be> Message-ID: Karel, Karel Venken writes: > Just in case you may want to use it, you can find some description of > its usage > > http://users.online.be/~cd003081/slackware/getting_packages.html Great page. I probably won't use your tool but I really appreciate your documentation effort. Keep up the good work ! -- Xavier. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 1494 bytes Desc: not available URL: From rshepard at appl-ecosys.com Mon Feb 23 00:30:40 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 22 Feb 2015 16:30:40 -0800 (PST) Subject: [Slackbuilds-users] Running Skype on -14.1? Message-ID: My friend needs to use Skype for a course so I installed 4.3.0.37 from SBo (along with the multilib libraries, of course). It won't run. Eric's blog from last June notes that M$ dropped ALSA support from Skype in favor of their PulseAudio. Assuming that I install pulseaudio-5.0 from SBo (plus the two dependencies), could we expect Skype to work? Has anyone experience with Skype on 14.1 with Xfce, or advice to share with us? TIA, Rich From ryan.q at linux.com Mon Feb 23 00:58:08 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Mon, 23 Feb 2015 00:58:08 +0000 Subject: [Slackbuilds-users] Running Skype on -14.1? References: Message-ID: On Sun, Feb 22, 2015, 4:30 PM Rich Shepard wrote: My friend needs to use Skype for a course so I installed 4.3.0.37 from SBo (along with the multilib libraries, of course). It won't run. Eric's blog from last June notes that M$ dropped ALSA support from Skype in favor of their PulseAudio. Assuming that I install pulseaudio-5.0 from SBo (plus the two dependencies), could we expect Skype to work? You could also try apulse if you do not need all of the pulseaudio stuff? Its sole purpose is to enable skype to run without pusleaudio like so: $ apulse skype Although on multilib, this will actually be: $ apulse32 skype On the next release of apulse there will only be one binary, but for now 32 and 64 bit are separate. Good luck! Has anyone experience with Skype on 14.1 with Xfce, or advice to share with us? TIA, Rich _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / FAQ - http:// slackbuilds.org / faq / -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Mon Feb 23 01:10:40 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 23 Feb 2015 11:10:40 +1000 Subject: [Slackbuilds-users] Running Skype on -14.1? In-Reply-To: References: Message-ID: <54EA7E10.40103@iinet.net.au> On 02/23/2015 10:30 AM, Rich Shepard wrote: > My friend needs to use Skype for a course so I installed 4.3.0.37 > from SBo > (along with the multilib libraries, of course). It won't run. Eric's blog > from last June notes that M$ dropped ALSA support from Skype in favor of > their PulseAudio. > > Assuming that I install pulseaudio-5.0 from SBo (plus the two > dependencies), could we expect Skype to work? > > Has anyone experience with Skype on 14.1 with Xfce, or advice to share > with us? The 4.3 version has an audio configuration button which tries to launch pavucontrol so you really need that package too. Unfortunately that entails a fairly deep dependency tree - good to use sbopkg or similar to build all that. That said, the combination works very well here with Xfce. Multilib makes it more complicated, not less, so if you only installed it for Skype, I'd ditch it. If you need to keep multilib, I made exhaustive (exhausting?) notes about building skype and dependencies on multilib at: http://darlo.selfip.org/multilibskype/ Otherwise there's at least one thread at LQ about running Skype - including without pulseaudio at all e.g. http://www.linuxquestions.org/questions/slackware-14/skype-4-3-a-4175508618/ chris From fernando.lopezjr at gmail.com Mon Feb 23 01:15:04 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 22 Feb 2015 18:15:04 -0700 Subject: [Slackbuilds-users] i would like to be a maintainer. In-Reply-To: <20150222152342.361e8e72@home.rlworkman.net> References: <54E9FFFB.4050701@slackbuilds.org> <20150222152342.361e8e72@home.rlworkman.net> Message-ID: awesome!! thanks :) On Feb 22, 2015 2:23 PM, "Robby Workman" wrote: > On Sun, 22 Feb 2015 23:12:43 +0700 > Willy Sudiarto Raharjo wrote: > > > > i would like to be a maintainer of inkscape, kicad & gimp. > > > > > > GIMP is included in Slackware, so it's not possible to include it in > > SBo inkscape is maintained by Robby Workman > > kicad is maintained by Niels Horn, but since he is quite busy, perhaps > > he isn't mind if someone took care of his packages > > > I don't care much about inkscape since I rarely use it, so sure, you > can have it. > > -RW > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Feb 23 01:16:41 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 23 Feb 2015 08:16:41 +0700 Subject: [Slackbuilds-users] luxrender In-Reply-To: <54EA0C22.3050205@slackonly.com> References: <54EA0C22.3050205@slackonly.com> Message-ID: <54EA7F79.7000502@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > luxrender sources missing (returns: Oops, you've found a dead > link)... i can't find the sources here either the maintainer hasn't update this package since 2013 as well So, anyone who uses this package can step up to become the maintainer - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTqf3kACgkQiHuDdNczM4G3XgCfcmuT4nOmvy+nYmKbkLdR2lWW aFcAoKJLRjlrdtxGEkqr+/3WhaHPM2sd =ghE/ -----END PGP SIGNATURE----- From rshepard at appl-ecosys.com Mon Feb 23 01:16:59 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 22 Feb 2015 17:16:59 -0800 (PST) Subject: [Slackbuilds-users] Running Skype on -14.1? In-Reply-To: References: Message-ID: On Mon, 23 Feb 2015, Ryan P.C. McQuen wrote: > You could also try apulse if you do not need all of the pulseaudio stuff? > Its sole purpose is to enable skype to run without pusleaudio like so: > > $ apulse32 skype Thanks, Ryan. That looks like the way to go. Much appreciated, Rich From rshepard at appl-ecosys.com Mon Feb 23 01:19:11 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 22 Feb 2015 17:19:11 -0800 (PST) Subject: [Slackbuilds-users] Running Skype on -14.1? In-Reply-To: <54EA7E10.40103@iinet.net.au> References: <54EA7E10.40103@iinet.net.au> Message-ID: On Mon, 23 Feb 2015, Christoph Willing wrote: > The 4.3 version has an audio configuration button which tries to launch > pavucontrol so you really need that package too. Unfortunately that > entails a fairly deep dependency tree - good to use sbopkg or similar to > build all that. That said, the combination works very well here with Xfce. Sigh. Guess I need to install sbopkg, first. > Multilib makes it more complicated, not less, so if you only installed it for > Skype, I'd ditch it. Strictly for skype. I'll remove those packages, too. Thanks, Christoph, Rich From klaatu at straightedgelinux.com Mon Feb 23 04:40:21 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Mon, 23 Feb 2015 17:40:21 +1300 Subject: [Slackbuilds-users] luxrender In-Reply-To: <54EA7F79.7000502@slackbuilds.org> References: <54EA0C22.3050205@slackonly.com> <54EA7F79.7000502@slackbuilds.org> Message-ID: <54EAAF35.3040803@straightedgelinux.com> On 02/23/2015 02:16 PM, Willy Sudiarto Raharjo wrote: >> luxrender sources missing (returns: Oops, you've found a dead >> link)... > > i can't find the sources here either > the maintainer hasn't update this package since 2013 as well > So, anyone who uses this package can step up to become the maintainer > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > This is relevant to my work. I'll take over maintainership of this. -klaatu From niels.horn at gmail.com Mon Feb 23 09:43:18 2015 From: niels.horn at gmail.com (Niels Horn) Date: Mon, 23 Feb 2015 06:43:18 -0300 Subject: [Slackbuilds-users] i would like to be a maintainer. In-Reply-To: References: <54E9FFFB.4050701@slackbuilds.org> <20150222152342.361e8e72@home.rlworkman.net> Message-ID: And feel free to take over kicad! -- Niels Horn On Sun, Feb 22, 2015 at 10:15 PM, Fernando Lopez wrote: > awesome!! thanks :) > On Feb 22, 2015 2:23 PM, "Robby Workman" wrote: > >> On Sun, 22 Feb 2015 23:12:43 +0700 >> Willy Sudiarto Raharjo wrote: >> >> > > i would like to be a maintainer of inkscape, kicad & gimp. >> > >> > >> > GIMP is included in Slackware, so it's not possible to include it in >> > SBo inkscape is maintained by Robby Workman >> > kicad is maintained by Niels Horn, but since he is quite busy, perhaps >> > he isn't mind if someone took care of his packages >> >> >> I don't care much about inkscape since I rarely use it, so sure, you >> can have it. >> >> -RW >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lksj at yandex.ru Mon Feb 23 10:16:16 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Mon, 23 Feb 2015 13:16:16 +0300 Subject: [Slackbuilds-users] xmms2 build bug Message-ID: <4994171424686576@web10j.yandex.ru> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: build-xmms2.log.tar.gz Type: application/x-gzip Size: 15112 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xmms2-libmodplug.patch.tar.gz Type: application/x-gzip Size: 351 bytes Desc: not available URL: From lksj at yandex.ru Mon Feb 23 10:24:44 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Mon, 23 Feb 2015 13:24:44 +0300 Subject: [Slackbuilds-users] xmms2 build bug In-Reply-To: <4994171424686576@web10j.yandex.ru> References: <4994171424686576@web10j.yandex.ru> Message-ID: <4636971424687084@web7o.yandex.ru> Sorry, I forgot to give the link. The solution is found here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724487 23.02.2015, 13:16, "????????? ???????" : > Hello. > I found bug in building xmms2 > http://slackbuilds.org/repository/14.1/audio/xmms2/?search=xmms2 > > Error: file modplug.h not found > > For fixing requires libmodplug > http://slackbuilds.org/repository/14.1/libraries/libmodplug/ > > Build log and patch attachend > > -- > ? ?????????, ?.????????? > > , > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ -- ? ?????????, ?.????????? From willysr at slackbuilds.org Mon Feb 23 11:38:48 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 23 Feb 2015 18:38:48 +0700 Subject: [Slackbuilds-users] xmms2 build bug In-Reply-To: <4994171424686576@web10j.yandex.ru> References: <4994171424686576@web10j.yandex.ru> Message-ID: <54EB1148.7030204@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I found bug in building xmms2 > http://slackbuilds.org/repository/14.1/audio/xmms2/?search=xmms2 > Error: file modplug.h not found For fixing requires libmodplug > http://slackbuilds.org/repository/14.1/libraries/libmodplug/ Build > log and patch attachend Hi I just tested on slackware64-14.1 VM and it built properly xmms2: MD5SUM check for xmms2-0.8DrO_o.tar.bz2 ... OK Building package xmms2-0.8DrO_o-x86_64-3_SBo.tgz ... OK - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTrEUgACgkQiHuDdNczM4EXpgCfRLp689iRyhvJw31EVZLC6uB/ kNUAn2qBKObYXTQd53N3myRgjKsi6i70 =O2/9 -----END PGP SIGNATURE----- From xavier at maillard.im Mon Feb 23 12:42:10 2015 From: xavier at maillard.im (Xavier Maillard) Date: Mon, 23 Feb 2015 13:42:10 +0100 Subject: [Slackbuilds-users] [ERR] Can't build ledger Message-ID: Hello, I see ledger is now at 3.1 in SBo but when I try to build/install it, I got this error: -- Build files have been written to: /tmp/SBo/ledger-3.1 [ 1%] Generating ../system.hh.gch /tmp/SBo/ledger-3.1/system.hh:162:18: fatal error: utf8.h: No such file or directory compilation terminated. make[2]: *** [system.hh.gch] Error 1 make[1]: *** [src/CMakeFiles/libledger.dir/all] Error 2 make: *** [all] Error 2 acprep: ERROR: Execution failed: make ledger: 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. Does anybody know where the missing file is part of ? Regards -- Xavier. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 1529 bytes Desc: not available URL: From willysr at slackbuilds.org Mon Feb 23 15:22:03 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 23 Feb 2015 22:22:03 +0700 Subject: [Slackbuilds-users] [ERR] Can't build ledger In-Reply-To: References: Message-ID: <54EB459B.4050902@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I see ledger is now at 3.1 in SBo but when I try to build/install > it, I got this error: > > -- Build files have been written to: /tmp/SBo/ledger-3.1 [ 1%] > Generating ../system.hh.gch /tmp/SBo/ledger-3.1/system.hh:162:18: > fatal error: utf8.h: No such file or directory compilation > terminated. make[2]: *** [system.hh.gch] Error 1 make[1]: *** > [src/CMakeFiles/libledger.dir/all] Error 2 make: *** [all] Error 2 > acprep: ERROR: Execution failed: make > > ledger: 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. > > Does anybody know where the missing file is part of ? http://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=f66f0b1985d0c9c85024aa46242e40843bd8beb4 - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTrRZsACgkQiHuDdNczM4HPwQCgjKtNc6qR3OiHYJ2aTJsfJIs/ OoIAoKB8IVAv6KQWkOY/Z58kUE1dk8Uz =k1GI -----END PGP SIGNATURE----- From fritz.kent at gmail.com Mon Feb 23 16:54:17 2015 From: fritz.kent at gmail.com (Kent Fritz) Date: Mon, 23 Feb 2015 08:54:17 -0800 Subject: [Slackbuilds-users] Fwd: libmicrohttpd slackbuild In-Reply-To: References: Message-ID: No response from maintainer (or my email went into spam folder). Marco -- are you out there? I got a reply from Marcel, the maintainer of plex-home-theater, with a go-ahead. ---------- Forwarded message ---------- From: Kent Fritz Date: Sun, Feb 15, 2015 at 8:11 AM Subject: libmicrohttpd slackbuild To: Marco Bonetti Cc: marc at mos6581.de I've attached a trivial patch that updates to the latest 0.9.39. The only dependent slackbuild seems to be plex-home-theater, which I don't have any experience with. Reasons for this update: 1. There are 2 medium CVE's against the current slackbuild version. 2. I have a slackbuild in-progress that has a feature requiring 0.9.35 or greater. Any chance for an update? Thanks, Kent. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: libmicrohttpd.patch Type: text/x-patch Size: 1091 bytes Desc: not available URL: From larryhaja at gmail.com Mon Feb 23 17:17:23 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Mon, 23 Feb 2015 09:17:23 -0800 Subject: [Slackbuilds-users] My packages In-Reply-To: <54D43FD0.1060701@straightedgelinux.com> References: <54D43FD0.1060701@straightedgelinux.com> Message-ID: A little late on this, but I'll take back libraries/irrlicht. --Larry On Thu, Feb 5, 2015 at 8:15 PM, Klaatu wrote: > I'll take povray. > > It's up to date with the latest stable release, so I will not be pushing > any update, but it's something that is relevant to my work, so I'll > gladly keep an eye out for it. > > - klaatu > > > On 02/04/2015 02:02 PM, Niels Horn wrote: > > Greetings to all, > > > > As some of you may have noticed, I've not been able to update my > SlackBuild > > scripts for some time now. > > > > It's not that I've lost interest. > > My whole professional life has been motivated by changes and challenges > and > > when some time ago the company I work for offered me a new challenge, I > > accepted it. At the time I had no real clue about the consequences, but > the > > idea of branching away from a technical career to an executive position > > seduced me (money-wise as well, naturally). > > I've learned many new things, like negotiating with legal departments, > > collaboration with branches from all aver the world, motivating leaders, > > setting goals and encouraging people to work hard to reach them, etc. > > > > But, it came with a price... More responsibility and more work hours. > > And that means less time for fun projects like maintaining SlackBuilds, a > > blog, homepage, etc. > > I miss that, but it is a choice I made and I'm enjoying some of the > results. > > The only non-professional activity I kept is carpentry. I enjoy building > > furniture, fixing anything made from wood and hope to continue doing so > > ever after I retire. > > > > I still use Slackware and will continue doing so as long as it exists. No > > Windows or Mac for me. > > > > Over the last several months I've received some e-mails requesting > updates > > of scripts. > > Some people I managed to convince to take over maintainership of a > certain > > package, others not (yet). > > Basically, all my scripts are "up for grabs". I've not even been able to > > keep track of which ones already have been taken over, so feel free to > do a > > > > # find ./ -name "*.info" -exec grep -l "Niels Horn" {} \; > > > > in your local copy of the SlackBuilds repository. > > If you have any technical questions about a specific script, feel free to > > contact me. It might take a few days to get an answer, but eventually I > > will. > > > > For the rest, the very capable administrators of SlackBuilds.org will no > > doubt find a way to handle any questions. > > > > Have fun! > > > > -- > > Niels Horn > > > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - http://slackbuilds.org/faq/ > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mancha1 at hush.com Mon Feb 23 18:26:07 2015 From: mancha1 at hush.com (mancha) Date: Mon, 23 Feb 2015 18:26:07 +0000 (UTC) Subject: [Slackbuilds-users] [ERR] Can't build ledger References: <54EB459B.4050902@slackbuilds.org> Message-ID: Willy Sudiarto Raharjo writes: > Xavier Maillard writes: > > > I see ledger is now at 3.1 in SBo but when I try to build/install > > it, I got this error: > > > > -- Build files have been written to: /tmp/SBo/ledger-3.1 [ 1%] > > Generating ../system.hh.gch /tmp/SBo/ledger-3.1/system.hh:162:18: > > fatal error: utf8.h: No such file or directory compilation > > terminated. make[2]: *** [system.hh.gch] Error 1 make[1]: *** > > [src/CMakeFiles/libledger.dir/all] Error 2 make: *** [all] Error 2 > > acprep: ERROR: Execution failed: make > > > > ledger: 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. > > > > Does anybody know where the missing file is part of ? > > http://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=f66f0b1985d0c9c85024aa46242e40843bd8beb4 > Hi. Xavier's problem is he didn't install ledger's dependency: utfcpp (provided by SBo). --mancha From willysr at slackbuilds.org Mon Feb 23 23:08:05 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 24 Feb 2015 06:08:05 +0700 Subject: [Slackbuilds-users] [ERR] Can't build ledger In-Reply-To: References: <54EB459B.4050902@slackbuilds.org> Message-ID: <54EBB2D5.2030107@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Xavier's problem is he didn't install ledger's dependency: utfcpp > (provided by SBo). it turns out utfcpp wasn't needed it requires a local copy of utfcpp, so installing utfcpp is not necessary and i have removed it on my branch http://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=423ce1420769a5dbe9da7ea7001bcf8ae5b71ad5 - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTrstUACgkQiHuDdNczM4GyIACeOzhyYBJGg2nuRS7apO6CJysr 3OkAnjzhKeOYPYVMkm8fIdt9mUGMH876 =Y9Zh -----END PGP SIGNATURE----- From willysr at slackbuilds.org Mon Feb 23 23:11:05 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 24 Feb 2015 06:11:05 +0700 Subject: [Slackbuilds-users] Fwd: libmicrohttpd slackbuild In-Reply-To: References: Message-ID: <54EBB389.6060605@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > No response from maintainer (or my email went into spam folder). > Marco -- are you out there? > > I got a reply from Marcel, the maintainer of plex-home-theater, > with a go-ahead. As far as the git log goes, Marco's last commit was in 2013 If you use libmicrohttpd, it would be better if you can step up and take this package and maintain it - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTrs4kACgkQiHuDdNczM4HimgCcD4wQ97d5jKRwCZkDbkd8R6s9 f5UAn1PmaCfbCluVCNhvevN4kSwK2kKR =3Cfb -----END PGP SIGNATURE----- From fritz.kent at gmail.com Tue Feb 24 04:43:42 2015 From: fritz.kent at gmail.com (Kent Fritz) Date: Mon, 23 Feb 2015 20:43:42 -0800 Subject: [Slackbuilds-users] Fwd: libmicrohttpd slackbuild In-Reply-To: <54EBB389.6060605@slackbuilds.org> References: <54EBB389.6060605@slackbuilds.org> Message-ID: Thanks, Willy. Update submitted. On Mon, Feb 23, 2015 at 3:11 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > No response from maintainer (or my email went into spam folder). > > Marco -- are you out there? > > > > I got a reply from Marcel, the maintainer of plex-home-theater, > > with a go-ahead. > > As far as the git log goes, Marco's last commit was in 2013 > > If you use libmicrohttpd, it would be better if you can step up and > take this package and maintain it > > > > - -- > Willy Sudiarto Raharjo > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iEYEARECAAYFAlTrs4kACgkQiHuDdNczM4HimgCcD4wQ97d5jKRwCZkDbkd8R6s9 > f5UAn1PmaCfbCluVCNhvevN4kSwK2kKR > =3Cfb > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ruben at orgizm.net Tue Feb 24 20:39:40 2015 From: ruben at orgizm.net (Ruben Schuller) Date: Tue, 24 Feb 2015 21:39:40 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> Message-ID: <20150224213940.06175ace@pflaume.kuchen> I hope that I'm not late for the party: http://ruben.orgizm.net/mkslackbuild.html Alas, I've overengineered that one a bit, I guess. But it worked pretty well for me so far ;) 2015-02-22 22:37 Xavier Maillard : > eval `grep DOWNLOAD package.info` ; wget $DOWNLOAD ; > # read package build script and info just in case > ./package.SlackBuild And thats just nice! Very unixy :) Cheers, Ruben From yalhcru at gmail.com Wed Feb 25 15:56:39 2015 From: yalhcru at gmail.com (B Watson) Date: Wed, 25 Feb 2015 10:56:39 -0500 Subject: [Slackbuilds-users] perl-Test-Deep download link gone 404 Message-ID: Found a copy here: http://pkgs.fedoraproject.org/repo/pkgs/perl-Test-Deep/Test-Deep-0.110.tar.gz/a5daeaaffcd8cf94a12594ff76970045/Test-Deep-0.110.tar.gz (apologies if word-wrap broke up that URL, it's all one piece with no spaces). From nastavs at gmail.com Wed Feb 25 16:02:39 2015 From: nastavs at gmail.com (Shrivats) Date: Wed, 25 Feb 2015 21:32:39 +0530 Subject: [Slackbuilds-users] Keepass and libgdiplus Message-ID: Hi, I recently built keepass on my slackware-14.1 machine and found that the information present on the SBo is slightly wrong: * It requires libgdiplus as a dependency [No mention on SBo] * libgdiplus URL is wrong (Atleast, it didn't work for me when I tried this morning - it should redirect to mono-project.com, which it never did) Apart from the above, both of them require a version bump: Keepass - 2.28 libgdiplus - 3.12 Shrivats From chris at chrisn.me.uk Wed Feb 25 16:21:54 2015 From: chris at chrisn.me.uk (Chris Novakovic) Date: Wed, 25 Feb 2015 16:21:54 +0000 Subject: [Slackbuilds-users] perl-Test-Deep download link gone 404 In-Reply-To: References: Message-ID: <54EDF6A2.7070706@chrisn.me.uk> On 25/02/2015 15:56, B Watson wrote: > Found a copy here: > > http://pkgs.fedoraproject.org/repo/pkgs/perl-Test-Deep/Test-Deep-0.110.tar.gz/a5daeaaffcd8cf94a12594ff76970045/Test-Deep-0.110.tar.gz Indeed: Ricardo Signes, the current maintainer, deleted 0.110 from the CPAN mirrors (as PAUSE authors are encouraged to do for versions of their module distributions that they no longer support). 0.110 was released in 2012 and has been superseded by 0.115 [1], and it might be best to update the Slackbuild to build that version instead of a rather outdated and unsupported one whose tarball is hosted by a third party. [1] http://search.cpan.org/CPAN/authors/id/R/RJ/RJBS/Test-Deep-0.115.tar.gz From willysr at slackbuilds.org Wed Feb 25 19:05:49 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 26 Feb 2015 02:05:49 +0700 Subject: [Slackbuilds-users] perl-Test-Deep download link gone 404 In-Reply-To: <54EDF6A2.7070706@chrisn.me.uk> References: <54EDF6A2.7070706@chrisn.me.uk> Message-ID: <54EE1D0D.7060001@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Indeed: Ricardo Signes, the current maintainer, deleted 0.110 from > the CPAN mirrors (as PAUSE authors are encouraged to do for > versions of their module distributions that they no longer > support). 0.110 was released in 2012 and has been superseded by > 0.115 [1], and it might be best to update the Slackbuild to build > that version instead of a rather outdated and unsupported one whose > tarball is hosted by a third party. > > [1] > http://search.cpan.org/CPAN/authors/id/R/RJ/RJBS/Test-Deep-0.115.tar.gz Fixed > in my branch and cc'ed to maintainer Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTuHQ0ACgkQiHuDdNczM4Eg3wCfYoL7isbEeT5w32WNbAZFsflR rEwAmwXQFXZkRMj3ixWVzLNqJElxA70X =dCcY -----END PGP SIGNATURE----- From willysr at slackbuilds.org Wed Feb 25 19:44:05 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 26 Feb 2015 02:44:05 +0700 Subject: [Slackbuilds-users] Keepass and libgdiplus In-Reply-To: References: Message-ID: <54EE2605.8050800@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > I recently built keepass on my slackware-14.1 machine and found > that the information present on the SBo is slightly wrong: > > * It requires libgdiplus as a dependency [No mention on SBo] i just tested the one we have in our repository and it can be built without libgdiplus since Mono no longer needs libgdiplus > * libgdiplus URL is wrong (Atleast, it didn't work for me when I > tried this morning - it should redirect to mono-project.com, which > it never did) libgdiplus URL is correct and it does point to mono-project.com - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTuJgUACgkQiHuDdNczM4Gt1ACffoFSfkmwiw6PUXMPZf1WUWvJ f7sAnj46IUKRb6ovquZaqxeDpHN1JbOZ =fTJH -----END PGP SIGNATURE----- From eric.b.pratt at gmail.com Wed Feb 25 20:00:16 2015 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Wed, 25 Feb 2015 12:00:16 -0800 Subject: [Slackbuilds-users] Keepass and libgdiplus In-Reply-To: <54EE2605.8050800@slackbuilds.org> References: <54EE2605.8050800@slackbuilds.org> Message-ID: Actually, I don't use KeePass anymore so if anyone wants to take it over, please feel free. If no one does, I'll try to submit a version bump for it soon (possibly as soon as this weekend.) About version dependencies, are we supposed to list dependencies of dependencies? How many levels deep are we supposed to go? I have only been mentioning one level of dependencies in my slackbuilds assuming people will follow the dependency tree. If that's incorrect, I can definitely update my dependency lists. But given that mono no longer requires libgdiplus, it will be a moot point for this slackbuild. Eric From willysr at slackbuilds.org Wed Feb 25 20:02:52 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 26 Feb 2015 03:02:52 +0700 Subject: [Slackbuilds-users] Keepass and libgdiplus In-Reply-To: References: <54EE2605.8050800@slackbuilds.org> Message-ID: <54EE2A6C.3020307@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Actually, I don't use KeePass anymore so if anyone wants to take > it over, please feel free. If no one does, I'll try to submit a > version bump for it soon (possibly as soon as this weekend.) > > About version dependencies, are we supposed to list dependencies > of dependencies? How many levels deep are we supposed to go? I > have only been mentioning one level of dependencies in my > slackbuilds assuming people will follow the dependency tree. If > that's incorrect, I can definitely update my dependency lists. But > given that mono no longer requires libgdiplus, it will be a moot > point for this slackbuild. 1 level of dependency I just tested that KeePass can be built without libgdiplus, but i didn't test for it's functionality. If it does require libgdiplus to be present in order for it to be functional, then yes, we can add libgdiplus to REQUIRES. Otherwise, leave mono as it's sole dependency - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTuKmwACgkQiHuDdNczM4EqWACeJOjCwv5rjEpWgXaF/q9TUzs9 nU8An0G49mQqu9KpmCB1YdLRaX8Y633c =+/Fu -----END PGP SIGNATURE----- From nastavs at gmail.com Wed Feb 25 20:15:46 2015 From: nastavs at gmail.com (Shrivats) Date: Thu, 26 Feb 2015 01:45:46 +0530 Subject: [Slackbuilds-users] Keepass and libgdiplus In-Reply-To: <54EE2A6C.3020307@slackbuilds.org> References: <54EE2605.8050800@slackbuilds.org> <54EE2A6C.3020307@slackbuilds.org> Message-ID: Hi, On 26 February 2015 at 01:32, Willy Sudiarto Raharjo wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > >> Actually, I don't use KeePass anymore so if anyone wants to take >> it over, please feel free. If no one does, I'll try to submit a >> version bump for it soon (possibly as soon as this weekend.) >> >> About version dependencies, are we supposed to list dependencies >> of dependencies? How many levels deep are we supposed to go? I >> have only been mentioning one level of dependencies in my >> slackbuilds assuming people will follow the dependency tree. If >> that's incorrect, I can definitely update my dependency lists. But >> given that mono no longer requires libgdiplus, it will be a moot >> point for this slackbuild. > > > 1 level of dependency > I just tested that KeePass can be built without libgdiplus, but i > didn't test for it's functionality. If it does require libgdiplus to > be present in order for it to be functional, then yes, we can add > libgdiplus to REQUIRES. Otherwise, leave mono as it's sole dependency > Although it's correct that KeePass doesn't require libgdiplus for it to build successfully, it *does* require this library in order to run properly. If Eric doesn't object, I can take over maintenance of this package. Shrivats From nastavs at gmail.com Wed Feb 25 20:17:11 2015 From: nastavs at gmail.com (Shrivats) Date: Thu, 26 Feb 2015 01:47:11 +0530 Subject: [Slackbuilds-users] Keepass and libgdiplus In-Reply-To: References: <54EE2605.8050800@slackbuilds.org> Message-ID: Hi, On 26 February 2015 at 01:30, Eric Pratt wrote: > Actually, I don't use KeePass anymore so if anyone wants to take it > over, please feel free. If no one does, I'll try to submit a version > bump for it soon (possibly as soon as this weekend.) > > About version dependencies, are we supposed to list dependencies of > dependencies? How many levels deep are we supposed to go? I have > only been mentioning one level of dependencies in my slackbuilds > assuming people will follow the dependency tree. If that's incorrect, > I can definitely update my dependency lists. But given that mono no > longer requires libgdiplus, it will be a moot point for this > slackbuild. > Normally we just list one level of dependencies - in this case, it isn't a nested level but an additional dependency to make KeePass work. IOW, libgdiplus is a runtime dependency. If you don't have any issues, perhaps I can take over maintenance? Shrivats From eric.b.pratt at gmail.com Thu Feb 26 00:53:18 2015 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Wed, 25 Feb 2015 16:53:18 -0800 Subject: [Slackbuilds-users] Keepass and libgdiplus In-Reply-To: References: <54EE2605.8050800@slackbuilds.org> Message-ID: On Wed, Feb 25, 2015 at 12:17 PM, Shrivats wrote: > > If you don't have any issues, perhaps I can take over maintenance? > I have no issues with this. Please take it over. Thanks! From xavier at maillard.im Thu Feb 26 06:43:59 2015 From: xavier at maillard.im (Xavier Maillard) Date: Thu, 26 Feb 2015 07:43:59 +0100 Subject: [Slackbuilds-users] Slackbuild helper script In-Reply-To: <20150224213940.06175ace@pflaume.kuchen> References: <54E7D100.9020606@rochefort.de> <54E88777.7090704@online.be> <20150224213940.06175ace@pflaume.kuchen> Message-ID: Ruben Schuller writes: > 2015-02-22 22:37 Xavier Maillard : > >> eval `grep DOWNLOAD package.info` ; wget $DOWNLOAD ; >> # read package build script and info just in case >> ./package.SlackBuild > > And thats just nice! Very unixy :) Indeed. -- Xavier. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 1494 bytes Desc: not available URL: From xavier at maillard.im Thu Feb 26 06:57:44 2015 From: xavier at maillard.im (Xavier Maillard) Date: Thu, 26 Feb 2015 07:57:44 +0100 Subject: [Slackbuilds-users] [ERR] Can't build ledger In-Reply-To: <54EBB2D5.2030107@slackbuilds.org> References: <54EB459B.4050902@slackbuilds.org> <54EBB2D5.2030107@slackbuilds.org> Message-ID: Hi, Willy Sudiarto Raharjo writes: >> Xavier's problem is he didn't install ledger's dependency: utfcpp >> (provided by SBo). > > it turns out utfcpp wasn't needed > it requires a local copy of utfcpp, so installing utfcpp is not > necessary and i have removed it on my branch Thank you very much ! I chose to install utfcpp SBo package instead of modifying ledger SB file. It turns out it install correctly now. Thank you ! -- Xavier. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 1494 bytes Desc: not available URL: From ryan.q at linux.com Fri Feb 27 00:43:19 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 26 Feb 2015 16:43:19 -0800 Subject: [Slackbuilds-users] pitivi is broken (possibly beyond repair) Message-ID: Slackers, It seems that pitivi's age is really starting to show. It just won't launch anymore, it may have broken when some dependent package upgraded. I've had some users email me to see if I knew a fix, sadly I can't seem to find one. :-( If someone would like to take over pitivi and get it working again that would be awesome. I spent hours trying to get a newer version to build, only to realize that it had a LOT of dependencies that weren't on SBo. Eventually I gave up. I'm not using pitivi anymore, so if someone wants a good project, it is open! Otherwise, we should probably remove it from SBo. Thanks and happy slacking! Ryan -- --- From willysr at slackbuilds.org Fri Feb 27 01:07:42 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 27 Feb 2015 08:07:42 +0700 Subject: [Slackbuilds-users] pitivi is broken (possibly beyond repair) In-Reply-To: References: Message-ID: <54EFC35E.6070101@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > It seems that pitivi's age is really starting to show. It just > won't launch anymore, it may have broken when some dependent > package upgraded. I've had some users email me to see if I knew a > fix, sadly I can't seem to find one. :-( > > If someone would like to take over pitivi and get it working again > that would be awesome. I spent hours trying to get a newer version > to build, only to realize that it had a LOT of dependencies that > weren't on SBo. Eventually I gave up. I'm not using pitivi anymore, > so if someone wants a good project, it is open! Have you tried the latest bundle? They provide a universal bundles in which they are probably pre-compiled binaries http://pitivi.ecchi.ca/bundles/ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTvw14ACgkQiHuDdNczM4GJ8gCdFJAJMBagogtKh3OK+sE+9M2A O1YAoIijdcuRvLzgBMOe+HT9/BpsVPWc =UUdp -----END PGP SIGNATURE----- From klaatu at straightedgelinux.com Fri Feb 27 03:36:15 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Fri, 27 Feb 2015 16:36:15 +1300 Subject: [Slackbuilds-users] pitivi is broken (possibly beyond repair) In-Reply-To: <54EFC35E.6070101@slackbuilds.org> References: <54EFC35E.6070101@slackbuilds.org> Message-ID: <54EFE62F.102@straightedgelinux.com> I have run the precompiled bundle (0.94) on Slack 14.1 (multilib and 64) and I can confirm that it does work...at least as much as Pitivi ever does. it's a single file; maybe the SlackBuild for it could just be copying that file to /opt and generating a quick and dirty .desktop file, or similar. Or just drop it from SBo. Depends on how many people actually use it, I reckon. -klaatu On 02/27/2015 02:07 PM, Willy Sudiarto Raharjo wrote: >> It seems that pitivi's age is really starting to show. It just >> won't launch anymore, it may have broken when some dependent >> package upgraded. I've had some users email me to see if I knew a >> fix, sadly I can't seem to find one. :-( > >> If someone would like to take over pitivi and get it working again >> that would be awesome. I spent hours trying to get a newer version >> to build, only to realize that it had a LOT of dependencies that >> weren't on SBo. Eventually I gave up. I'm not using pitivi anymore, >> so if someone wants a good project, it is open! > > Have you tried the latest bundle? > They provide a universal bundles in which they are probably > pre-compiled binaries > > http://pitivi.ecchi.ca/bundles/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > From ryan.q at linux.com Fri Feb 27 04:50:47 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Fri, 27 Feb 2015 04:50:47 +0000 Subject: [Slackbuilds-users] pitivi is broken (possibly beyond repair) References: <54EFC35E.6070101@slackbuilds.org> <54EFE62F.102@straightedgelinux.com> Message-ID: On Thu, Feb 26, 2015, 7:36 PM Klaatu wrote: I have run the precompiled bundle (0.94) on Slack 14.1 (multilib and 64) and I can confirm that it does work...at least as much as Pitivi ever does. it's a single file; maybe the SlackBuild for it could just be copying that file to /opt and generating a quick and dirty .desktop file, or similar. Or just drop it from SBo. Depends on how many people actually use it, I reckon. If it works I certainly do not mind maintaining the build! Always a little sad to go from source to precompiled binaries ... BUT ... better than nothing. Thanks to Willy for pointing to that and Klaatu to verifying it actually works. :-) I should be able to update the build tomorrow morning. -klaatu On 02/27/2015 02:07 PM, Willy Sudiarto Raharjo wrote: >> It seems that pitivi's age is really starting to show. It just >> won't launch anymore, it may have broken when some dependent >> package upgraded. I've had some users email me to see if I knew a >> fix, sadly I can't seem to find one. :-( > >> If someone would like to take over pitivi and get it working again >> that would be awesome. I spent hours trying to get a newer version >> to build, only to realize that it had a LOT of dependencies that >> weren't on SBo. Eventually I gave up. I'm not using pitivi anymore, >> so if someone wants a good project, it is open! > > Have you tried the latest bundle? > They provide a universal bundles in which they are probably > pre-compiled binaries > > http:// pitivi.ecchi.ca /bundles/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users > Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / > FAQ - http:// slackbuilds.org / faq / > > > _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org http:// lists.slackbuilds.org /mailman/ listinfo / slackbuilds-users Archives - http:// lists.slackbuilds.org / pipermail / slackbuilds-users / FAQ - http:// slackbuilds.org / faq / -------------- next part -------------- An HTML attachment was scrubbed... URL: From nastavs at gmail.com Fri Feb 27 19:42:51 2015 From: nastavs at gmail.com (Shrivats) Date: Sat, 28 Feb 2015 01:12:51 +0530 Subject: [Slackbuilds-users] Keepass and libgdiplus In-Reply-To: References: <54EE2605.8050800@slackbuilds.org> Message-ID: Hi, On 26 February 2015 at 06:23, Eric Pratt wrote: > > I have no issues with this. Please take it over. Thanks! I have uploaded the package with newer version info and it's in pending queue now. If there's something wrong in the upload, please let me know. Thanks, Shrivats From willysr at slackbuilds.org Sat Feb 28 03:28:02 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Feb 2015 10:28:02 +0700 Subject: [Slackbuilds-users] Early Warning: Changes in colord UID/GID Message-ID: <54F135C2.3020702@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all for those who have used colord, please note that in the next public update, the UID/GID will be changed to 303. It happened because i forgot to add colord UID/GID (was supposed to be 297) into the uid_gid.txt file, so it was then used for icinga. Since icinga UID/GID is used in many packages, i prefer to move the colord UID/GID to 303 which is available. Sorry for the unconveniance - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTxNcIACgkQiHuDdNczM4EkdACgnkHo4CZq3pJV4axryrp/NKYw jvgAn2H2ogs4leBF5wa58u7wnBVgIV60 =AigM -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Feb 28 05:14:19 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Feb 2015 12:14:19 +0700 Subject: [Slackbuilds-users] Updates - 20150228.{12} Message-ID: <54F14EAB.7030905@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sat Feb 28 05:09:30 UTC 2015 network/rtl8188eu: Fix SlackBuild filename. +--------------------------+ Sat Feb 28 04:41:10 UTC 2015 academic/armadillo: Added (C++ linear algebra library). academic/gcompris: Updated for version 15.02. academic/omlibraries: Updated for version svn20150221. academic/openmodelica: Updated for version svn24695. audio/aj-snapshot: Added (minimalist JACK session manager). audio/alsamixergui: BUILD bump. audio/apulse: Updated for version 20150103. audio/ponymix: Added (PulseAudio CLI mixer). business/ledger: Fix Build. desktop/aweather: Added (AWeather). desktop/clearlooks-phenix-theme: Updated for version 6.0.3. desktop/grits: Added (Virtual Globe Library). desktop/i3pystatus: Updated for version 3.32. desktop/py3status: Updated for version 2.3. desktop/rsl: Added (Radar Software Library). desktop/xdgmenumaker: Updated for version 0.5 + new maintainer. desktop/xfce4-eyes-plugin: Updated for version 4.4.3. development/groovy: Updated for version 2.4.1. development/hub: Updated for version 2.2.0 (moved from ruby). development/jeex: Fix DOWNLOAD. development/mcu8051ide: Updated for version 1.4.10. development/sqlitebrowser: Updated for version 3.5.1. development/thunderpad: Updated for version 20150222. games/FlightGear-data: Updated for version 3.4.0. games/FlightGear: Update for version 3.4.0. games/gbrainy: Updated for version 2.2.4. games/javacpc: Updated for version 2.6b. games/mame: Updated for version 0.159. games/pcsxr: Fix DOWNLOAD url. games/qmc2: Updated for version 0.49. gis/gdal: Updated for version 1.11.2. gis/grass: Updated for version 7.0.0. gis/qgis: Updated for version 2.8.0. graphics/converseen: Updated for version 0.9.0. graphics/digikam: Updated for version 4.8.0. graphics/inkscape: Updated for version 0.91. graphics/scrot: Update DOWNLOAD. libraries/CGAL: Updated for version 4.5.2. libraries/SimGear: Update for version 3.4.0. libraries/bcdoc: Updated for version 0.13.0. libraries/eigen3: Updated for version 3.2.4. libraries/enum34: Updated for version 1.0.4. libraries/htmlcxx: Added (HTML parser library). libraries/ipaddress: Updated for version 1.0.7. libraries/isodate: Updated for version 0.5.1. libraries/libdaemon: New maintainer + template update. libraries/libevhtp: Updated for version 1.2.10. libraries/libmicrohttpd: Updated for version 0.9.39, new maintainer. libraries/libsigsegv: New maintainer + template update. libraries/live555: Updated for version 2015.02.26. libraries/manubulon-snmp-plugins: Added (Manubulon SNMP Plugins). libraries/netcdf: Updated for version 4.3.3. libraries/pies2overrides: Updated for version 2.6.3. libraries/pies: Updated for version 2.6.3. libraries/pyechonest: Updated for version 9.0.0. libraries/pylast: Updated for version 1.1.0. libraries/tbb: Updated for version 4.3u3. libraries/wxsvg: Updated for version 1.5.3. libraries/xmlrpc-c: Updated for version 1.33.16. misc/KeePass: Updated for version 2.28 + new maintainer. misc/kronometer: Added (A stopwatch application for KDE). misc/mosquitto: Updated for version 1.4. misc/wcd: Updated for version 5.2.6. misc/xca: Updated for version 1.1.0. multimedia/dvdstyler: Updated for version 2.9.2. multimedia/lives: Updated for version 2.2.8. multimedia/pitivi: Updated for version 0.94_beta. multimedia/vlc: Patched to address interface change in freerdp. multimedia/x265: Updated for version 1.5. network/aria2: Updated for version 1.18.10. network/bitlbee-steam: Added (Steam protocol plugin for bitlbee). network/ccnet: Fixed MD5SUM. network/greenbone-security-assistant: Added (UI for OpenVAS). network/grsync: Updated for version 1.2.5. network/icinga2: Added (Network resource monitoring system). network/mpop: Updated for version 1.2.2. network/nagios: Use monitoring-plugins by default. network/openvas-cli: Added (CLI for OpenVAS). network/openvas-libraries: Added (Libraries used in OpenVAS). network/openvas-manager: Added (Manager for OpenVAS). network/openvas-scanner: Added (Scanner for OpenVAS). network/qbittorrent: Updated for version 3.1.12. network/rtl8188eu: Added (rtl-8188eu driver). network/seafile-server: Added garbage collector and fix long option. network/snort: Updated for version 2.9.7.0. network/tor-browser: Updated for version 4.0.4. network/urlwatch: Updated for version 1.18. network/youtube-dl: Updated for version 2015.02.21 + new maintainer. office/freemind: Updated for version 1.0.1. office/ganttproject: Updated for version 2.7. office/libreoffice-helppack: Updated for version 4.4.1. office/libreoffice-langpack: Updated for version 4.4.1. office/libreoffice: Updated for version 4.4.1. office/odt2txt: Update DOWNLOAD and script. office/openoffice.org: Fix build. perl/perl-Net-SNMP: Added (Object oriented interface to SNMP). perl/perl-Test-Deep: Updated for version 0.115. python/autopep8: Updated for version 1.1.1. python/colored: Updated for version 1.1.5. python/curtsies: Updated for version 0.2.3. python/pep8: Updated for version 1.6.2. python/wcwidth: Added (Measures number of Terminal). system/TLP: Update slackbuild system/TermRecord: Updated for version 1.2.4. system/bcache-tools: Added (block layer cache userspace utilities). system/colord: Update UID/GID. system/drbd-utils: Fix for Xen physical device paths. system/flSynclient: Updated DOWNLOAD and HOMEPAGE url. system/graphite-web: Added (Enterprise Scalable Realtime Graphing). system/icinga-web: Added (Network resource monitoring Web UI). system/icingaweb2: Added (Network resource monitoring Web UI). system/inxi: Updated for version 2.2.19. system/john: Support for AVX instructions, remove MERGEWORDS. system/kexec-tools: Updated for version 2.0.9. system/lbench: Updated for version 2.6. system/monitoring-plugins: Added (a bundle of monitoring plugins). system/nagvis: Added (visualization addon for Nagios or Icinga). system/nbench: New maintainer + template update. system/netatop: Updated for version 0.5. system/nsca-ng: Added (drop-in replacement for NSCA). system/parallel: Updated for version 20150222. system/rar: Updated for version 5.2.1 and maintainer change. system/rhash: Added header. system/slpkg: Updated for version 2.2.6. system/tinyvm: Added (small virtual machine). system/unrar: Updated for version 5.2.6. system/winetricks: Updated for version 20141130. +--------------------------+ - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTxTqsACgkQiHuDdNczM4Hr0ACfQNKCY1ysN0cHONsNtOIo9Tgu TewAmQEViNP1NHPeRT3YKYKl3ih+H2ML =26Wp -----END PGP SIGNATURE----- From hostmaster at slackonly.com Sat Feb 28 08:56:18 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Sat, 28 Feb 2015 10:56:18 +0200 Subject: [Slackbuilds-users] GeoGebra Message-ID: <54F182B2.5080509@slackonly.com> Hi!, GeoGebra source is missing! (It seems that the oldest in GeoGebra repo is the 5.0.64.0) Thanks! From marc at mos6581.de Sat Feb 28 13:31:13 2015 From: marc at mos6581.de (Marcel Saegebarth) Date: Sat, 28 Feb 2015 14:31:13 +0100 Subject: [Slackbuilds-users] Pafy, HTTP 404 Message-ID: <54F1C321.5050908@mos6581.de> The link to the source tarball is wrong, due to the capitalized p's. It should be "/p/pafy" instead of "/P/Pafy". Link: https://pypi.python.org/packages/source/p/pafy/Pafy-0.3.72.tar.gz -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From ryan.q at linux.com Sat Feb 28 16:56:17 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Sat, 28 Feb 2015 08:56:17 -0800 Subject: [Slackbuilds-users] GeoGebra In-Reply-To: <54F182B2.5080509@slackonly.com> References: <54F182B2.5080509@slackonly.com> Message-ID: On 2/28/15, Panagiotis Nikolaou wrote: > Hi!, > > GeoGebra source is missing! > (It seems that the oldest in GeoGebra repo is the 5.0.64.0) > A similar situation to live555, I suppose. R.S. Ananda, let me know if you would like to be added to my sf repo to store the tarballs there. I went ahead and uploaded the latest release: 5.0.68.0 Feel free to use this download link in an update: http://sourceforge.net/projects/slackbuildsdirectlinks/files/GeoGebra/GeoGebra-Linux-Portable-5.0.68.0.tar.bz2 > Thanks! > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- --- From rshepard at appl-ecosys.com Sat Feb 28 17:28:17 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 28 Feb 2015 09:28:17 -0800 (PST) Subject: [Slackbuilds-users] Running Skype on -14.1? In-Reply-To: <54EA7E10.40103@iinet.net.au> References: <54EA7E10.40103@iinet.net.au> Message-ID: On Mon, 23 Feb 2015, Christoph Willing wrote: > Multilib makes it more complicated, not less, so if you only installed it > for Skype, I'd ditch it. Before I mess up the laptop, is there a better way to ditch multilib other than inserting the distribution dvd and running 'updatepkg --reinstall ' for all gcc, glibc, and other files? Rich From rshepard at appl-ecosys.com Sat Feb 28 17:56:14 2015 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 28 Feb 2015 09:56:14 -0800 (PST) Subject: [Slackbuilds-users] Running Skype on -14.1? [RESOLVED] In-Reply-To: References: <54EA7E10.40103@iinet.net.au> Message-ID: On Sat, 28 Feb 2015, Rich Shepard wrote: > Before I mess up the laptop, is there a better way to ditch multilib > other than inserting the distribution dvd and running 'updatepkg > --reinstall ' for all gcc, glibc, and other files? Nevermind. The version of apulse in the SBo repository automagically recognizes the presence of the multilib libraries and builds to accommodate them. I wrote a shell script attached to a panel icon so that skype is now invoked as "... apulse skype -U". Will soon learn if that solves the problem Thanks, Rich From willysr at slackbuilds.org Sat Feb 28 18:22:59 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 01 Mar 2015 01:22:59 +0700 Subject: [Slackbuilds-users] Pafy, HTTP 404 In-Reply-To: <54F1C321.5050908@mos6581.de> References: <54F1C321.5050908@mos6581.de> Message-ID: <54F20783.1000504@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The link to the source tarball is wrong, due to the capitalized > p's. It should be "/p/pafy" instead of "/P/Pafy". > > Link: > > https://pypi.python.org/packages/source/p/pafy/Pafy-0.3.72.tar.gz Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTyB4IACgkQiHuDdNczM4HRRgCfStpluwlTIeLcgVK3JJ2RU7+j EysAoK19vbu5jI9SgzPWy7174fzPJnn9 =QSL/ -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Feb 28 18:24:55 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 01 Mar 2015 01:24:55 +0700 Subject: [Slackbuilds-users] GeoGebra In-Reply-To: <54F182B2.5080509@slackonly.com> References: <54F182B2.5080509@slackonly.com> Message-ID: <54F207F7.10205@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > GeoGebra source is missing! (It seems that the oldest in GeoGebra > repo is the 5.0.64.0) Fixed in my branch Thanks - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTyB/cACgkQiHuDdNczM4Hx6QCfTg9oAqNWY6b/aF3jj58eJOAa 68MAoJKo+KuHdhmoD8Q9faY4W6FDbxl1 =UD7a -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Feb 28 18:36:14 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 01 Mar 2015 01:36:14 +0700 Subject: [Slackbuilds-users] GeoGebra In-Reply-To: <54F207F7.10205@slackbuilds.org> References: <54F182B2.5080509@slackonly.com> <54F207F7.10205@slackbuilds.org> Message-ID: <54F20A9E.7020203@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> GeoGebra source is missing! (It seems that the oldest in >> GeoGebra repo is the 5.0.64.0) > > Fixed in my branch Ups, seems that Ryan posted a higher version This one is not yet fixed as i can't find the source elsewhere - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlTyCp4ACgkQiHuDdNczM4Gd0ACfU/SMQJmCp4hUxj6rQulNhDG7 xfQAn3XvZLJYdemdvOzjYP6Xxu8hAQdU =zP0I -----END PGP SIGNATURE-----