From arkadiusz at drabczyk.org Tue Nov 1 02:09:06 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Tue, 1 Nov 2016 03:09:06 +0100 Subject: [Slackbuilds-users] misc/po4a: is `su -' requirement only about kpsewhich? Message-ID: <20161101020906.GA2089@comp.a> In misc/po4a README it says: "WARNING: run po4a.SlackBuild as root (su -) not with only root privileges (su), otherwise test #24 will fail." I did some tests and it seems that it's enough to add /usr/share/texmf/bin/ directory to $PATH for test #24 to pass. The warning is here because in standard Slackware setup this directory which contains kpsewich is added to $PATH by /etc/profile.d/tetex.sh. I think that current warning is quite uninformative and it only hides the real reason why test #24 fails without `su -'. It could it be improved, for example: "WARNING: run po4a.SlackBuild as root (su -) not with only root privileges (su) to have /usr/share/texmf/bin/kpsewhich in $PATH, otherwise test #24 will fail." What do you think? -- Arkadiusz Drabczyk From willysr at slackbuilds.org Tue Nov 1 03:06:11 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 1 Nov 2016 10:06:11 +0700 Subject: [Slackbuilds-users] misc/po4a: is `su -' requirement only about kpsewhich? In-Reply-To: <20161101020906.GA2089@comp.a> References: <20161101020906.GA2089@comp.a> Message-ID: > In misc/po4a README it says: > > "WARNING: run po4a.SlackBuild as root (su -) not with only root > privileges (su), otherwise test #24 will fail." > > I did some tests and it seems that it's enough to add > /usr/share/texmf/bin/ directory to $PATH for test #24 to pass. The > warning is here because in standard Slackware setup this directory > which contains kpsewich is added to $PATH by /etc/profile.d/tetex.sh. > I think that current warning is quite uninformative and it only hides > the real reason why test #24 fails without `su -'. It could it be > improved, for example: > > "WARNING: run po4a.SlackBuild as root (su -) not with only root > privileges (su) to have /usr/share/texmf/bin/kpsewhich in $PATH, > otherwise test #24 will fail." It's already written in the HOWTO https://slackbuilds.org/howto/#su some scripts will fail if we use normal su instead of su - -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From arkadiusz at drabczyk.org Tue Nov 1 21:58:11 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Tue, 1 Nov 2016 22:58:11 +0100 Subject: [Slackbuilds-users] misc/po4a: is `su -' requirement only about kpsewhich? In-Reply-To: References: <20161101020906.GA2089@comp.a> Message-ID: <20161101215811.GA13295@comp.a> On Tue, Nov 01, 2016 at 10:06:11AM +0700, Willy Sudiarto Raharjo wrote: > > In misc/po4a README it says: > > > > "WARNING: run po4a.SlackBuild as root (su -) not with only root > > privileges (su), otherwise test #24 will fail." > > > > I did some tests and it seems that it's enough to add > > /usr/share/texmf/bin/ directory to $PATH for test #24 to pass. The > > warning is here because in standard Slackware setup this directory > > which contains kpsewich is added to $PATH by /etc/profile.d/tetex.sh. > > I think that current warning is quite uninformative and it only hides > > the real reason why test #24 fails without `su -'. It could it be > > improved, for example: > > > > "WARNING: run po4a.SlackBuild as root (su -) not with only root > > privileges (su) to have /usr/share/texmf/bin/kpsewhich in $PATH, > > otherwise test #24 will fail." > > It's already written in the HOWTO > > https://slackbuilds.org/howto/#su > some scripts will fail if we use normal su instead of su - Oh, I missed that. Thanks. -- Arkadiusz Drabczyk From atelszewski at gmail.com Tue Nov 1 23:45:38 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 00:45:38 +0100 Subject: [Slackbuilds-users] fakeroot, po4a Message-ID: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> Hi, Would it make much hassle if I updated fakeroot SlackBuild and made po4a optional? Then the user would actually have to pass MANPO=yes to include the additional docs. What I mean is to make the SlackBuild automated tools friendly, e.g. _slackrepo_ has no way to disable building of what is in REQUIRES. -- Best regards, Andrzej Telszewski From yalhcru at gmail.com Tue Nov 1 23:58:38 2016 From: yalhcru at gmail.com (B Watson) Date: Tue, 1 Nov 2016 19:58:38 -0400 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> Message-ID: On 11/1/16, Andrzej Telszewski wrote: > > Then the user would actually have to pass MANPO=yes to include the > additional docs. Without looking at the script (so this is just a general observation), you don't necessarily have to do it that way. Your script could autodetect whether po4a is installed, and set whatever options are needed for fakeroot's configure or whatever it uses. And, in case the autodetection is somehow broken someday, or getting in someone's way, you could add a MANPO=no setting to disable it and skip po4a entirely. Whatever po4a actually is, I mean :) From chris.willing at iinet.net.au Wed Nov 2 00:03:30 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 2 Nov 2016 10:03:30 +1000 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> Message-ID: On 02/11/16 09:45, Andrzej Telszewski wrote: > Hi, > > Would it make much hassle if I updated fakeroot SlackBuild and made po4a > optional? > > Then the user would actually have to pass MANPO=yes to include the > additional docs. > > What I mean is to make the SlackBuild automated tools friendly, e.g. > _slackrepo_ has no way to disable building of what is in REQUIRES. > I don't use it (fakeroot) so I have no skin in this particular change. However, in general, my preference is to include whatever documentation is available in the source code we're building from. Any individual user may never refer to the documentation but for those expecting a man page (or whatever), it should be available if provided by upstream. Having a option in the SlackBuild solves the dilemma of whether to include it or not but I think the option should default to yes (not no as the suggestion above implies). chris From atelszewski at gmail.com Wed Nov 2 11:32:00 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 12:32:00 +0100 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> Message-ID: On 02/11/16 01:03, Christoph Willing wrote: > > However, in general, my preference is to include whatever documentation > is available in the source code we're building from. Any individual user > may never refer to the documentation but for those expecting a man page > (or whatever), it should be available if provided by upstream. > This is true most of the time. But the holidays end, when you have to pull ridiculous amount of dependencies to build the docs. That's the (only) reason I gave the option not to build the translated docs in fakeroot. > Having a option in the SlackBuild solves the dilemma of whether to > include it or not but I think the option should default to yes (not no > as the suggestion above implies). I would put it onto maintainers liking. The end user can easily choose, what she wants. But if building the docs requires additional dependencies, I would prefer to have it set to =NO and mentioned the dependencies as optional, rather than as REQUIRES in .info. @Willy, I'm going to implement it the way B Watson suggested, i.e. if po4a is installed, the docs will get translated and passing MANPO=no will prevent translation even if po4a is installed. This should not affect the current users. Question: should I increase the BUILD number? -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Wed Nov 2 11:42:04 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 Nov 2016 18:42:04 +0700 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> Message-ID: <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> > @Willy, I'm going to implement it the way B Watson suggested, i.e. if > po4a is installed, the docs will get translated and passing MANPO=no > will prevent translation even if po4a is installed. This should not > affect the current users. > > Question: should I increase the BUILD number? if the changes is critical so that users who uses automatic tools will notice it and rebuilt, it's better to bump the BUILD number, otherwise leave it as it is. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Wed Nov 2 11:47:46 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 12:47:46 +0100 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> Message-ID: <4bfb031c-6c53-262c-7aa7-fd316c18669a@gmail.com> On 02/11/16 12:42, Willy Sudiarto Raharjo wrote: >> @Willy, I'm going to implement it the way B Watson suggested, i.e. if >> po4a is installed, the docs will get translated and passing MANPO=no >> will prevent translation even if po4a is installed. This should not >> affect the current users. >> >> Question: should I increase the BUILD number? > > if the changes is critical so that users who uses automatic tools will > notice it and rebuilt, it's better to bump the BUILD number, otherwise > leave it as it is. > In the worst case scenario, they would lose translated man pages. I don't see it as critical and so I'm gonna leave BUILD as is. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Wed Nov 2 13:30:46 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 Nov 2016 20:30:46 +0700 Subject: [Slackbuilds-users] Perl modules orphaned between 14.1 and 14.2 In-Reply-To: <0q93i.01120072d8.20161031145925.2593563d@loli.sombragris.org> References: <0q93i.01120072d8.20161031145925.2593563d@loli.sombragris.org> Message-ID: <68f4f968-5b93-f5cd-d70c-d1e679ca5ee3@slackbuilds.org> > While hunting an odd bug in texinfo I caught the following: > > I have some perl modules installed from the 14.1 era: > > perl-CPAN-Meta-2.150005-x86_64-1_SBo > perl-CPAN-Meta-YAML-0.018-x86_64-1_SBo > perl-Parse-CPAN-Meta-1.4417-x86_64-1_SBo > perl-TermReadKey-2.33-x86_64-0_SBo > > Now, these modules are *not* in the 14.2 repository, nor there is any > notice I can find of their removal. It's easy to search in cgit history perl-CPAN-Meta-2.150005-x86_64-1_SBo https://slackbuilds.org/cgit/slackbuilds/commit/?id=00d8965762da496550d9a881f5237bff1caabfc3 perl-CPAN-Meta-YAML https://slackbuilds.org/cgit/slackbuilds/commit/?id=3a593469418a753c49547288d5d4baf23c45f7e3 perl-Parse-CPAN-Meta https://slackbuilds.org/cgit/slackbuilds/commit/?id=d817f7651fe72b666f1fa9fcf32f371796a83a86 perl-TermReadKey https://slackbuilds.org/cgit/slackbuilds/commit/?id=e9d408fef6876e93641061d6dfac10509c377f19 All history of scripts in SBo are now tracked via GIT and cgit is provided for easy navigation via web-based interface. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Wed Nov 2 13:38:16 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 2 Nov 2016 13:38:16 +0000 Subject: [Slackbuilds-users] Easy-rsa package (from OpenVPN) on SBo Message-ID: OpenVPN used to include scripts to manage certificate authorities, keys and certificates. These were bundled under the easy-rsa scripts, in /usr/share/docs/openvpn/easy-rsa - if I remember correctly, in Slackware. At some point in time, the OpenVPN maintainers decided to spin them off separately (https://github.com/OpenVPN/easy-rsa) - and from that moment on, they disappeared from Slackware. As this is only (relatively) easy way I'm aware of generating a CA for Openvpn, together with corresponding server and client certificates and keys, I've asked several times on LQ if they could be included back in Slackware - without success. I'm thinking of making an easy-rsa package for SBo, to make it easy to add them back to Slackware. What do people think? Good idea, bad idea? Maybe they are redundant and there are other tools in place already doing this job? From atelszewski at gmail.com Wed Nov 2 13:42:08 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 14:42:08 +0100 Subject: [Slackbuilds-users] Easy-rsa package (from OpenVPN) on SBo In-Reply-To: References: Message-ID: <8f1cf464-4de5-b02a-d3cb-44d93eff1bcd@gmail.com> On 02/11/16 14:38, Sebastian Arcus wrote: > > I'm thinking of making an easy-rsa package for SBo, to make it easy to > add them back to Slackware. What do people think? Good idea, bad idea? > Maybe they are redundant and there are other tools in place already > doing this job? Most probably a good idea. Sometime ago I wanted to do exactly that, but in the end I used something from here: https://github.com/PhantomX/slackbuilds/blob/master/easy-rsa/easy-rsa.SlackBuild -- Best regards, Andrzej Telszewski From didier at slint.fr Wed Nov 2 15:43:30 2016 From: didier at slint.fr (Didier Spaier) Date: Wed, 2 Nov 2016 16:43:30 +0100 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: <4bfb031c-6c53-262c-7aa7-fd316c18669a@gmail.com> References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> <4bfb031c-6c53-262c-7aa7-fd316c18669a@gmail.com> Message-ID: <727c9d8f-ee62-14a2-86a3-66a8ee63ae8d@slint.fr> Le 02/11/2016 ? 12:47, Andrzej Telszewski a ?crit : > On 02/11/16 12:42, Willy Sudiarto Raharjo wrote: >>> @Willy, I'm going to implement it the way B Watson suggested, i.e. if >>> po4a is installed, the docs will get translated and passing MANPO=no >>> will prevent translation even if po4a is installed. This should not >>> affect the current users. >>> >>> Question: should I increase the BUILD number? >> >> if the changes is critical so that users who uses automatic tools will >> notice it and rebuilt, it's better to bump the BUILD number, otherwise >> leave it as it is. >> > > In the worst case scenario, they would lose translated man pages. > I don't see it as critical and so I'm gonna leave BUILD as is. Not an answer, but though I be a happy user of fakeroot I must remind that in some cases it's unusable, see e.g. the other thread about po4a that I maintain. Another example that comes to mind is blackbox: The SlackBuild installs stuff directly in the host system to allow building bbkeys just after blackbox. Better chroot to a build system or do that in a VM ;) Incidentally and as a reminder, calling makepkg with its full path in the SlackBuild is necessary for "fakeroot sh maypackage.SlackBuild." to succeed. Have a good day, Didier -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x60C03EEA.asc Type: application/pgp-keys Size: 1718 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Wed Nov 2 15:23:14 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 16:23:14 +0100 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: <727c9d8f-ee62-14a2-86a3-66a8ee63ae8d@slint.fr> References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> <4bfb031c-6c53-262c-7aa7-fd316c18669a@gmail.com> <727c9d8f-ee62-14a2-86a3-66a8ee63ae8d@slint.fr> Message-ID: On 02/11/16 16:43, Didier Spaier wrote: > Not an answer, but though I be a happy user of fakeroot I must remind > that in some cases it's unusable, see e.g. the other thread about po4a > that I maintain. Another example that comes to mind is blackbox: > The SlackBuild installs stuff directly in the host system to allow > building bbkeys just after blackbox. Better chroot to a build system or > do that in a VM ;) Continuing being OOT, I had a play with fakeroot, but in the end decided not to use it for building packages. slackrepo (it is yours, isn't it?) in VM is my way to go. And BTW, I noticed there are multiple packages that write outside of build directories, if I recall correctly, mostly Python related stuff. Well, slackrepo noticed that ;-) Very nice feature. -- Best regards, Andrzej Telszewski From rob0 at slackbuilds.org Wed Nov 2 15:47:07 2016 From: rob0 at slackbuilds.org (Rob McGee) Date: Wed, 2 Nov 2016 10:47:07 -0500 Subject: [Slackbuilds-users] Easy-rsa package (from OpenVPN) on SBo In-Reply-To: References: Message-ID: <20161102154707.GY6526@harrier.slackbuilds.org> On Wed, Nov 02, 2016 at 01:38:16PM +0000, Sebastian Arcus wrote: > OpenVPN used to include scripts to manage certificate authorities, > keys and certificates. These were bundled under the easy-rsa > scripts, in /usr/share/docs/openvpn/easy-rsa - if I remember > correctly, in Slackware. > > At some point in time, the OpenVPN maintainers decided to spin them > off separately (https://github.com/OpenVPN/easy-rsa) - and from > that moment on, they disappeared from Slackware. As this is only > (relatively) easy way I'm aware of generating a CA for Openvpn, > together with corresponding server and client certificates and > keys, ... The idea of generating a key anywhere other than on the client who would be using it was part of the "easy" in easy-rsa, but it is incorrect from a security perspective. Users should generate their own key and CSR (certificate signing request), and send the CA only the CSR. The key should be securely maintained and not sent via insecure means. > I've asked several times on LQ if they could be included back > in Slackware - without success. Did you try emailing Pat directly? He might not see some things posted on LQ. > I'm thinking of making an easy-rsa package for SBo, to make it easy > to add them back to Slackware. What do people think? Good idea, bad When you install such a thing to a location writable only by root, people get the bad idea to run it as root. Worse, they often run it on the OpenVPN server itself. Then some others get the harebrained idea to put easy-rsa on a VM ... uh, no! Cryptography requires entropy (random data), and a VM has no means of getting entropy. None of these caveats say that SBo should not have a build for easy-rsa; just perhaps that a good stern README should be added (maybe the upstream one covers all this?) I have run my CA in a dedicated user account on a physical machine which is not a VPN client nor server. (No, I am not suggesting we should add a UID/GID for easy-rsa, but rather that this is one of several ways to DTRT.) > idea? Maybe they are redundant and there are other tools in place > already doing this job? They are just scripts which wrap around openssl commands. It's possible (albeit not easy, BTDT) to read them and figure out what they're doing. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From willysr at slackbuilds.org Wed Nov 2 16:43:20 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 Nov 2016 23:43:20 +0700 Subject: [Slackbuilds-users] fzf fails to build In-Reply-To: <20161030184328.GA3910@jostein> References: <20161024201030.GA2354@jostein> <20161030184328.GA3910@jostein> Message-ID: <901d2132-d5fb-ae94-ac8f-122442a6f8fb@slackbuilds.org> > I rebooted and tried again, but still gets the same error. make sure to use su - instead of su i tested this using sbopkg ran using su - and it built fine fzf: MD5SUM check for 0.13.5.tar.gz ... OK MD5SUM check for 35d512af ... OK MD5SUM check for 63c378b8 ... OK Building package fzf-0.13.5-x86_64-1_SBo.tgz ... OK Installing package fzf-0.13.5-x86_64-1_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Wed Nov 2 17:47:05 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 18:47:05 +0100 Subject: [Slackbuilds-users] ffmpeg without _custom Message-ID: Hi, As of now, ffmpeg is built with _custom ARCH, so it's meant for the machine it was built on. But I noticed that Alien's ffmpeg [http://www.slackware.com/~alien/slackbuilds/ffmpeg/] can be built and installed on different machines. Could we have something like that in SBo? And possibly, if there are some switches/deps that make the package built-machine dependent, only then would we add _custom tag? -- Best regards, Andrzej Telszewski From ruben at rbn.im Wed Nov 2 18:07:58 2016 From: ruben at rbn.im (Ruben Schuller) Date: Wed, 2 Nov 2016 19:07:58 +0100 Subject: [Slackbuilds-users] ffmpeg without _custom In-Reply-To: References: Message-ID: <20161102190758.02a3f31b@kiwi.kuchen> 2016-11-02 18:47:05 Andrzej Telszewski > Hi, > > As of now, ffmpeg is built with _custom ARCH, so it's meant for the > machine it was built on. > > But I noticed that Alien's ffmpeg > [http://www.slackware.com/~alien/slackbuilds/ffmpeg/] can be built > and installed on different machines. > > Could we have something like that in SBo? > > And possibly, if there are some switches/deps that make the package > built-machine dependent, only then would we add _custom tag? > From ruben at rbn.im Wed Nov 2 18:13:29 2016 From: ruben at rbn.im (Ruben Schuller) Date: Wed, 2 Nov 2016 19:13:29 +0100 Subject: [Slackbuilds-users] ffmpeg without _custom In-Reply-To: <20161102190758.02a3f31b@kiwi.kuchen> References: <20161102190758.02a3f31b@kiwi.kuchen> Message-ID: <20161102191329.6f83cb84@kiwi.kuchen> Sorry, hit the send button by accident. I'm building ffmpeg from SBo with slackrepo and have no problems with running that on other machines. 2016-11-02 19:07:58 Ruben Schuller > 2016-11-02 18:47:05 Andrzej Telszewski > > > Hi, > > > > As of now, ffmpeg is built with _custom ARCH, so it's meant for the > > machine it was built on. > > > > But I noticed that Alien's ffmpeg > > [http://www.slackware.com/~alien/slackbuilds/ffmpeg/] can be built > > and installed on different machines. > > > > Could we have something like that in SBo? > > > > And possibly, if there are some switches/deps that make the package > > built-machine dependent, only then would we add _custom tag? > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From baildon.research at googlemail.com Wed Nov 2 18:16:03 2016 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 2 Nov 2016 18:16:03 +0000 Subject: [Slackbuilds-users] Easy-rsa package (from OpenVPN) on SBo In-Reply-To: <20161102154707.GY6526@harrier.slackbuilds.org> References: <20161102154707.GY6526@harrier.slackbuilds.org> Message-ID: >> idea? Maybe they are redundant and there are other tools in place >> already doing this job? > > They are just scripts which wrap around openssl commands. It's > possible (albeit not easy, BTDT) to read them and figure out what > they're doing. https://wiki.openwrt.org/doc/howto/openvpn-streamlined-server-setup But I'm happy with easy-rsa and rob0's advice :) -D. From atelszewski at gmail.com Wed Nov 2 20:22:58 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 21:22:58 +0100 Subject: [Slackbuilds-users] ffmpeg without _custom In-Reply-To: <20161102191329.6f83cb84@kiwi.kuchen> References: <20161102190758.02a3f31b@kiwi.kuchen> <20161102191329.6f83cb84@kiwi.kuchen> Message-ID: <9b6bd0ea-68f4-b547-6ff1-cbdf249d92df@gmail.com> On 02/11/16 19:13, Ruben Schuller wrote: > Sorry, hit the send button by accident. > > I'm building ffmpeg from SBo with slackrepo and have no problems with > running that on other machines. > > 2016-11-02 19:07:58 Ruben Schuller > >> 2016-11-02 18:47:05 Andrzej Telszewski >> >>> Hi, >>> >>> As of now, ffmpeg is built with _custom ARCH, so it's meant for the >>> machine it was built on. >>> >>> But I noticed that Alien's ffmpeg >>> [http://www.slackware.com/~alien/slackbuilds/ffmpeg/] can be built >>> and installed on different machines. >>> >>> Could we have something like that in SBo? >>> >>> And possibly, if there are some switches/deps that make the package >>> built-machine dependent, only then would we add _custom tag? >>> But as far as I know, this is not guaranteed to work. I'm not pushing it, I guess this not trivial work, and it is not me who is going to fight it. -- Best regards, Andrzej Telszewski From alik at ejik.org Wed Nov 2 21:03:54 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Thu, 03 Nov 2016 00:03:54 +0300 Subject: [Slackbuilds-users] ffmpeg without _custom In-Reply-To: References: Message-ID: <1478120634.2171863.775518617.771BEA8C@webmail.messagingengine.com> On Wed, Nov 2, 2016, at 20:47, Andrzej Telszewski wrote: > Hi, > > As of now, ffmpeg is built with _custom ARCH, so it's meant for the > machine it was built on. > > But I noticed that Alien's ffmpeg > [http://www.slackware.com/~alien/slackbuilds/ffmpeg/] can be built and > installed on different machines. > > Could we have something like that in SBo? > > And possibly, if there are some switches/deps that make the package > built-machine dependent, only then would we add _custom tag? This switch is the build option --disable-runtime-cpudetect, but it is not used in the SBo SlackBuild. The opposite option --enable-runtime-cpudetect is the default for more than 4 years, see https://git.videolan.org/?p=ffmpeg.git;a=commit;h=c75b611a3853acc4cd05c37d1f6f72e67fb7b8eb Thus, the SBo ffmpeg is _not_ built-machine dependent and the "_custom" is not needed. The "_custom" thing is very unfortunate because it is not recognized by slackpkg and slackpkg+. Best regards, Alexander From atelszewski at gmail.com Wed Nov 2 21:05:49 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Nov 2016 22:05:49 +0100 Subject: [Slackbuilds-users] ffmpeg without _custom In-Reply-To: <1478120634.2171863.775518617.771BEA8C@webmail.messagingengine.com> References: <1478120634.2171863.775518617.771BEA8C@webmail.messagingengine.com> Message-ID: <377e79c6-cec7-0c42-a886-e1133dfd3a30@gmail.com> On 02/11/16 22:03, Alexander Verbovetsky wrote: > On Wed, Nov 2, 2016, at 20:47, Andrzej Telszewski wrote: >> Hi, >> >> As of now, ffmpeg is built with _custom ARCH, so it's meant for the >> machine it was built on. >> >> But I noticed that Alien's ffmpeg >> [http://www.slackware.com/~alien/slackbuilds/ffmpeg/] can be built and >> installed on different machines. >> >> Could we have something like that in SBo? >> >> And possibly, if there are some switches/deps that make the package >> built-machine dependent, only then would we add _custom tag? > > This switch is the build option --disable-runtime-cpudetect, but it is > not used in the SBo SlackBuild. > > The opposite option --enable-runtime-cpudetect is the default for more > than 4 years, see > https://git.videolan.org/?p=ffmpeg.git;a=commit;h=c75b611a3853acc4cd05c37d1f6f72e67fb7b8eb > > Thus, the SBo ffmpeg is _not_ built-machine dependent and the "_custom" > is not needed. > > The "_custom" thing is very unfortunate because it is not recognized by > slackpkg and slackpkg+. > > Best regards, > Alexander Sounds promising. :-) -- Best regards, Andrzej Telszewski From hba.nihilismus at gmail.com Thu Nov 3 02:37:52 2016 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Wed, 2 Nov 2016 20:37:52 -0600 Subject: [Slackbuilds-users] libraries/libkate: You should recreate aclocal.m4 Message-ID: Trying to build libraries/libkate: make[1]: Entering directory '/tmp/SBo/libkate-0.4.1' /bin/sh ./libtool --tag=CC --silent --mode=compile gcc -DHAVE_CONFIG_H -I. -I./include -I ./src -I ./include -Wall -W -O2 -fPIC -MT src/lib_libkate_la-kate.lo -MD -MP -MF src/.deps/lib_libkate_la-kate.Tpo -c -o src/lib_libkate_la-kate.lo `test -f 'src/kate.c' || echo './'`src/kate.c libtool: Version mismatch error. This is libtool 2.4.6, but the libtool: definition of this LT_INIT comes from libtool 2.2.6. libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6 libtool: and run autoconf again. Makefile:750: recipe for target 'src/lib_libkate_la-kate.lo' failed make[1]: *** [src/lib_libkate_la-kate.lo] Error 63 make[1]: Leaving directory '/tmp/SBo/libkate-0.4.1' Makefile:949: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 The solution was to add the next line between *configure ...* and *make && make install*: find . -iname aclocal.m4 -exec rm {} \; This was in Slackware64 14.2. Related to: http://sushihangover.github.io/mono-libtool-version-mismatch-error-this-is-libtool-2-dot-4-6/ http://www.howtodoityourself.org/how-to-fix-libtool-version-mismatch-error.html - Cheers -- Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Thu Nov 3 08:48:00 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 3 Nov 2016 08:48:00 +0000 Subject: [Slackbuilds-users] Easy-rsa package (from OpenVPN) on SBo In-Reply-To: References: <20161102154707.GY6526@harrier.slackbuilds.org> Message-ID: <03454eb2-5441-1c99-e566-7f09fd0e9d5d@open-t.co.uk> On 02/11/16 18:16, David Spencer wrote: >>> idea? Maybe they are redundant and there are other tools in place >>> already doing this job? >> >> They are just scripts which wrap around openssl commands. It's >> possible (albeit not easy, BTDT) to read them and figure out what >> they're doing. > > https://wiki.openwrt.org/doc/howto/openvpn-streamlined-server-setup > > But I'm happy with easy-rsa and rob0's advice :) Funnily enough, I can't access the above link at the moment: "The owner of wiki.openwrt.org has configured their website improperly. To protect your information from being stolen, Firefox has not connected to this website. This site uses HTTP Strict Transport Security (HSTS) to specify that Firefox only connect to it securely. As a result, it is not possible to add an exception for this certificate. wiki.openwrt.org uses an invalid security certificate. The certificate expired on 02/11/16 20:55. The current time is 03/11/16 08:46. Error code: SEC_ERROR_EXPIRED_CERTIFICATE" From ts at websafe.pl Thu Nov 3 09:38:31 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Thu, 3 Nov 2016 10:38:31 +0100 Subject: [Slackbuilds-users] Easy-rsa package (from OpenVPN) on SBo In-Reply-To: <03454eb2-5441-1c99-e566-7f09fd0e9d5d@open-t.co.uk> References: <20161102154707.GY6526@harrier.slackbuilds.org> <03454eb2-5441-1c99-e566-7f09fd0e9d5d@open-t.co.uk> Message-ID: On 11/03/2016 09:48 AM, Sebastian Arcus wrote: > Funnily enough, I can't access the above link at the moment: > "The owner of wiki.openwrt.org has configured their website improperly. > To protect your information from being stolen, Firefox has not connected > to this website. > This site uses HTTP Strict Transport Security (HSTS) to specify that > Firefox only connect to it securely. As a result, it is not possible to > add an exception for this certificate. Just remove the s from https http://wiki.openwrt.org/doc/howto/openvpn-streamlined-server-setup -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Thu Nov 3 09:46:58 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 3 Nov 2016 16:46:58 +0700 Subject: [Slackbuilds-users] libraries/libkate: You should recreate aclocal.m4 In-Reply-To: References: Message-ID: <9d9f1395-0bbc-fa03-7cab-9c2724abd3c2@slackbuilds.org> > Trying to build libraries/libkate: > > make[1]: Entering directory '/tmp/SBo/libkate-0.4.1' > /bin/sh ./libtool --tag=CC --silent --mode=compile gcc -DHAVE_CONFIG_H > -I. -I./include -I ./src -I ./include -Wall -W -O2 -fPIC -MT > src/lib_libkate_la-kate.lo -MD -MP -MF src/.deps/lib_libkate_la-kate.Tpo -c > -o src/lib_libkate_la-kate.lo `test -f 'src/kate.c' || echo './'`src/kate.c > libtool: Version mismatch error. This is libtool 2.4.6, but the > libtool: definition of this LT_INIT comes from libtool 2.2.6. > libtool: You should recreate aclocal.m4 with macros from libtool 2.4.6 > libtool: and run autoconf again. > Makefile:750: recipe for target 'src/lib_libkate_la-kate.lo' failed > make[1]: *** [src/lib_libkate_la-kate.lo] Error 63 > make[1]: Leaving directory '/tmp/SBo/libkate-0.4.1' > Makefile:949: recipe for target 'all-recursive' failed > make: *** [all-recursive] Error 1 > > The solution was to add the next line between *configure ...* and *make && > make install*: > > find . -iname aclocal.m4 -exec rm {} \; > > This was in Slackware64 14.2. > > Related to: > http://sushihangover.github.io/mono-libtool-version-mismatch-error-this-is-libtool-2-dot-4-6/ > http://www.howtodoityourself.org/how-to-fix-libtool-version-mismatch-error.html It works fine here using sbopkg libkate: MD5SUM check for libkate-0.4.1.tar.gz ... OK Building package libkate-0.4.1-x86_64-1_SBo.tgz ... OK is this a clean slackware64-14.2 or upgrade from previous version? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Thu Nov 3 16:57:45 2016 From: didier at slint.fr (Didier Spaier) Date: Thu, 3 Nov 2016 17:57:45 +0100 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> <4bfb031c-6c53-262c-7aa7-fd316c18669a@gmail.com> <727c9d8f-ee62-14a2-86a3-66a8ee63ae8d@slint.fr> Message-ID: <3fde835f-e6b9-49d1-6aa2-a548dfb2cbad@slint.fr> Le 02/11/2016 ? 16:23, Andrzej Telszewski a ?crit : > On 02/11/16 16:43, Didier Spaier wrote: >> Not an answer, but though I be a happy user of fakeroot I must remind >> that in some cases it's unusable, see e.g. the other thread about po4a >> that I maintain. Another example that comes to mind is blackbox: >> The SlackBuild installs stuff directly in the host system to allow >> building bbkeys just after blackbox. Better chroot to a build system or >> do that in a VM ;) > > Continuing being OOT, I had a play with fakeroot, but in the end decided not to use it for building packages. > > slackrepo (it is yours, isn't it?) in VM is my way to go. "Il faut rendre ? C?sar ce qui est ? C?sar", the author of slackrepo is David Spencer. Of course David did a good job, thanks to him. Even more OOT: upcoming Slint-14.2 will include some packages from Salix' extra-14.2 repos, also built with scripts from SBo, see this blog post from George Vlahavas aka gapan: http://salixos.blogspot.fr/2016/08/our-new-extra-repository.html All that being said, fakeroot saves me a lot of time. Didier From atelszewski at gmail.com Thu Nov 3 16:37:12 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 3 Nov 2016 17:37:12 +0100 Subject: [Slackbuilds-users] fakeroot, po4a In-Reply-To: <3fde835f-e6b9-49d1-6aa2-a548dfb2cbad@slint.fr> References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> <4bfb031c-6c53-262c-7aa7-fd316c18669a@gmail.com> <727c9d8f-ee62-14a2-86a3-66a8ee63ae8d@slint.fr> <3fde835f-e6b9-49d1-6aa2-a548dfb2cbad@slint.fr> Message-ID: <16c88b97-12af-b120-f57c-9236b531bac0@gmail.com> On 03/11/16 17:57, Didier Spaier wrote: > "Il faut rendre ? C?sar ce qui est ? C?sar", the author of slackrepo is David Spencer. > > Of course David did a good job, thanks to him. Yeah, found it out later on ;-) Sorry for the mistake :-) -- Best regards, Andrzej Telszewski From kingbeowulf at gmail.com Thu Nov 3 17:13:44 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Thu, 3 Nov 2016 10:13:44 -0700 Subject: [Slackbuilds-users] ffmpeg without _custom In-Reply-To: References: Message-ID: <2871a248-7a7d-3e57-4da4-64a8f3647971@gmail.com> On 11/02/2016 10:47 AM, Andrzej Telszewski wrote: > Hi, > > As of now, ffmpeg is built with _custom ARCH, so it's meant for the > machine it was built on. > > But I noticed that Alien's ffmpeg > [http://www.slackware.com/~alien/slackbuilds/ffmpeg/] can be built and > installed on different machines. > > Could we have something like that in SBo? > > And possibly, if there are some switches/deps that make the package > built-machine dependent, only then would we add _custom tag? > IIRC, this was discussed on this list ages ago. It wasn't to prevent execution on another computer - since only "uname -m" is tested - but for the possibility of (runtime?) compile options not the default of upstream. Anyway, this was to fix a problem that maybe isn't a problem anymore? -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Thu Nov 3 17:32:08 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 3 Nov 2016 18:32:08 +0100 Subject: [Slackbuilds-users] cssutils and python2-chardet Message-ID: <98e1587a-7c42-96ee-9644-1e92af16e4c3@gmail.com> Hi, cssutils mentions python2-chardet as optional dependency. Shouldn't it actually be "python-chardet"? -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Thu Nov 3 17:54:47 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 3 Nov 2016 18:54:47 +0100 Subject: [Slackbuilds-users] cssutils and python2-chardet In-Reply-To: <98e1587a-7c42-96ee-9644-1e92af16e4c3@gmail.com> References: <98e1587a-7c42-96ee-9644-1e92af16e4c3@gmail.com> Message-ID: 2016-11-03 18:32 GMT+01:00 Andrzej Telszewski : > Hi, > > cssutils mentions python2-chardet as optional dependency. > Shouldn't it actually be "python-chardet"? yes, it has been renamed a while ago but this most probably slipped. thanks for spotting this, Andrzej: I have fixed it in my branch and it will go in the next update. Matteo From atelszewski at gmail.com Thu Nov 3 18:52:57 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 3 Nov 2016 19:52:57 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> Message-ID: <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Hi, I've spent some time building packages now and although I used an automated tool (slackrepo to the rescue, thank you David!), I'm from the camp that reads README, trying to leave as little as possible to the fate. I'm using web browser to find the SlackBuild in question, read on and decide what to do. If an optional dependency is mentioned, I search for it, read on, and so on ;-) Searching for optional dependency is the most frustrating point. Sometimes there are many search results and you need to scan the list to find the one you need. Sometimes, the search filed leaves the keyword you entered there, so you have to erase it, before proceeding, etc. So what's the use for OPTIONAL field you ask? 1) PHP could parse it to give us direct link to the optional SlackBuild in question, 2) PHP could parse it to let us know about possible circular dependency. When it comes to automated tools, I'd say we need something more than just the package name in the OPTIONAL field. Probably something like that (ffmpeg for example) would be needed: OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no" This would have to be thought through to make the best design decisions and the SlackBuilds would have to be standardized in one way or the other. But for the next iteration, having OPTIONAL field mentioning just the packages names and SBo website listing them next to REQUIRES, would be the step towards the better, faster and more secure world :-) -- Best regards, Andrzej Telszewski From jbernts at broadpark.no Thu Nov 3 22:59:38 2016 From: jbernts at broadpark.no (Jostein Berntsen) Date: Thu, 03 Nov 2016 23:59:38 +0100 Subject: [Slackbuilds-users] fzf fails to build In-Reply-To: <901d2132-d5fb-ae94-ac8f-122442a6f8fb@slackbuilds.org> References: <20161024201030.GA2354@jostein> <20161030184328.GA3910@jostein> <901d2132-d5fb-ae94-ac8f-122442a6f8fb@slackbuilds.org> Message-ID: <20161103225938.GE3910@jostein> On 02.11.16,23:43, Willy Sudiarto Raharjo wrote: >> I rebooted and tried again, but still gets the same error. > >make sure to use su - instead of su > >i tested this using sbopkg ran using su - and it built fine >fzf: > MD5SUM check for 0.13.5.tar.gz ... OK > MD5SUM check for 35d512af ... OK > MD5SUM check for 63c378b8 ... OK > Building package fzf-0.13.5-x86_64-1_SBo.tgz ... OK > Installing package fzf-0.13.5-x86_64-1_SBo.tgz ... OK > > This worked fine, thanks. Jostein From coltree at tpg.com.au Fri Nov 4 01:01:10 2016 From: coltree at tpg.com.au (Colin Tree) Date: Fri, 4 Nov 2016 11:01:10 +1000 Subject: [Slackbuilds-users] NetworkManager-openvpn In-Reply-To: <3fde835f-e6b9-49d1-6aa2-a548dfb2cbad@slint.fr> References: <0ec6292d-3aae-b592-20b6-3058967a8dcd@gmail.com> <00dfa68c-54eb-9f46-d7ee-115ad502f3a5@slackbuilds.org> <4bfb031c-6c53-262c-7aa7-fd316c18669a@gmail.com> <727c9d8f-ee62-14a2-86a3-66a8ee63ae8d@slint.fr> <3fde835f-e6b9-49d1-6aa2-a548dfb2cbad@slint.fr> Message-ID: <59a7b26d-f4b5-1347-4f9c-99a30f008c37@tpg.com.au> Hi, sorry I'm not a programmer, but found a small problem with NM-openvpn from https://openvpn.net/ got directed to PrivateTunnel to setup a VPN service trying to configure a VPN with a user profile from https://www.privatetunnel.com it gags on " Cannot import VPN connection The file 'San Jose.ovpn' could not be read or does not contain recognized VPN connection information Error: configuration error: unsupported blob/xml element (line 77). " ------BEGIN CERTIFICATE------ bla-bla-bla ................ ------END CERTIFICATE------ had to change to and to The VPN server drops after ~ 1 minute of inactivity For out of the box workability should it also have the default configuration include a 30 sec ping to keep the VPN alive ? Go well, Colin From andreas.guldstrand at gmail.com Fri Nov 4 07:01:45 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Fri, 4 Nov 2016 08:01:45 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: As the current maintainer of sbotools, I would approve of an OPTIONAL field like the one proposed by Andrzej, with the "libass:ASS=yes|no" bits. Seems very useful and feasible to implement support for. On 3 November 2016 at 19:52, Andrzej Telszewski wrote: > Hi, > > I've spent some time building packages now and although I used an automated > tool (slackrepo to the rescue, thank you David!), I'm from the camp that > reads README, trying to leave as little as possible to the fate. > > I'm using web browser to find the SlackBuild in question, read on and decide > what to do. If an optional dependency is mentioned, I search for it, read > on, and so on ;-) > > Searching for optional dependency is the most frustrating point. > Sometimes there are many search results and you need to scan the list to > find the one you need. > Sometimes, the search filed leaves the keyword you entered there, so you > have to erase it, before proceeding, etc. > > So what's the use for OPTIONAL field you ask? > > 1) PHP could parse it to give us direct link to the optional SlackBuild in > question, > 2) PHP could parse it to let us know about possible circular dependency. > > > When it comes to automated tools, I'd say we need something more than just > the package name in the OPTIONAL field. > Probably something like that (ffmpeg for example) would be needed: > > OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no" > > This would have to be thought through to make the best design decisions and > the SlackBuilds would have to be standardized in one way or the other. > > But for the next iteration, having OPTIONAL field mentioning just the > packages names and SBo website listing them next to REQUIRES, would be the > step towards the better, faster and more secure world :-) > > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From andreas.guldstrand at gmail.com Fri Nov 4 07:54:14 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Fri, 4 Nov 2016 08:54:14 +0100 Subject: [Slackbuilds-users] Shouldn't KeePass (mono apps in general) be ARCH=noarch? In-Reply-To: <06777a0a-3c6b-6203-7c5a-a8f5c2b8934b@websafe.pl> References: <899534ea-7526-65f9-a50c-92acc83030ec@websafe.pl> <06777a0a-3c6b-6203-7c5a-a8f5c2b8934b@websafe.pl> Message-ID: On 29 October 2016 at 21:11, Thomas Szteliga wrote: > On 10/29/2016 08:37 PM, B Watson wrote: >> Example: a lot of Perl packages install only perl code, nothing native, >> but the install path is different (lib vs. lib64) so they can't use >> noarch. Actually, a lot of perl packages don't actually use lib/lib64 at all, but are still not marked noarch in SBo. I found this out when I carefully checked a bunch of perl submissions of mine if they used an arch-dependent directory at all, and when they didn't I marked them as noarch ... and then that was changed after I submitted. From kjhambrick at gmail.com Fri Nov 4 08:31:32 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Fri, 4 Nov 2016 03:31:32 -0500 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error Message-ID: All -- While trying to build PaleMoon 26.5.0, I am suffering from an md5sum error on 26.5.0_Release.tar.gz The Slackbuild's md5sum is d7578845894fb58470b54d569615d32f but I see 5556f1a1d668a0d1d71387a6e66b53ca I've run my SBo wrapper script twice now. Is it me or does the md5sum fail for Y'All too ? Thank you ! -- kjh Also reported on LQ -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Nov 4 09:02:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 4 Nov 2016 16:02:02 +0700 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error In-Reply-To: References: Message-ID: > While trying to build PaleMoon 26.5.0, I am suffering from an md5sum error > on 26.5.0_Release.tar.gz > > The Slackbuild's md5sum is d7578845894fb58470b54d569615d32f but I see > 5556f1a1d668a0d1d71387a6e66b53ca > > I've run my SBo wrapper script twice now. > > Is it me or does the md5sum fail for Y'All too ? Yes, it's incorrect i have fixed it on my branch thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kjhambrick at gmail.com Fri Nov 4 09:05:33 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Fri, 4 Nov 2016 04:05:33 -0500 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error In-Reply-To: References: Message-ID: thanks willy ! -- kjh On Fri, Nov 4, 2016 at 4:02 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > While trying to build PaleMoon 26.5.0, I am suffering from an md5sum > error > > on 26.5.0_Release.tar.gz > > > > The Slackbuild's md5sum is d7578845894fb58470b54d569615d32f but I see > > 5556f1a1d668a0d1d71387a6e66b53ca > > > > I've run my SBo wrapper script twice now. > > > > Is it me or does the md5sum fail for Y'All too ? > > Yes, it's incorrect > i have fixed it on my branch > > thanks > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Fri Nov 4 10:47:23 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 4 Nov 2016 20:47:23 +1000 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error In-Reply-To: References: Message-ID: <3985d815-0156-995b-c1c5-f04c433a57fd@iinet.net.au> On 04/11/16 19:02, Willy Sudiarto Raharjo wrote: >> While trying to build PaleMoon 26.5.0, I am suffering from an md5sum error >> on 26.5.0_Release.tar.gz >> >> The Slackbuild's md5sum is d7578845894fb58470b54d569615d32f but I see >> 5556f1a1d668a0d1d71387a6e66b53ca >> >> I've run my SBo wrapper script twice now. >> >> Is it me or does the md5sum fail for Y'All too ? > > Yes, it's incorrect > i have fixed it on my branch > Interestingly, the original md5sum works for me for a version downloaded around 1st October. Downloading it again just now, the new version (although with same name/version) has a new md5sum - also slightly different size: chris at d6:/storage/distfiles$ ls -l 26.5.0_Release.tar.gz -rw-r--r-- 1 chris vislab 128600018 Oct 1 13:49 26.5.0_Release.tar.gz chris at d6:/storage/distfiles$ md5sum 26.5.0_Release.tar.gz d7578845894fb58470b54d569615d32f 26.5.0_Release.tar.gz and new version: chris at d6:/tmp$ ls -l 26.5.0_Release.tar.gz -rw-r--r-- 1 chris vislab 128600081 Nov 4 20:41 26.5.0_Release.tar.gz chris at d6:/tmp$ md5sum 26.5.0_Release.tar.gz 5556f1a1d668a0d1d71387a6e66b53ca 26.5.0_Release.tar.gz I hate it when they do that. chris From matteo.bernardini at gmail.com Fri Nov 4 10:55:59 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 4 Nov 2016 11:55:59 +0100 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error In-Reply-To: <3985d815-0156-995b-c1c5-f04c433a57fd@iinet.net.au> References: <3985d815-0156-995b-c1c5-f04c433a57fd@iinet.net.au> Message-ID: 2016-11-04 11:47 GMT+01:00 Christoph Willing : > On 04/11/16 19:02, Willy Sudiarto Raharjo wrote: >>> >>> While trying to build PaleMoon 26.5.0, I am suffering from an md5sum >>> error >>> on 26.5.0_Release.tar.gz >>> >>> The Slackbuild's md5sum is d7578845894fb58470b54d569615d32f but I see >>> 5556f1a1d668a0d1d71387a6e66b53ca >>> >>> I've run my SBo wrapper script twice now. >>> >>> Is it me or does the md5sum fail for Y'All too ? >> >> >> Yes, it's incorrect >> i have fixed it on my branch >> > > Interestingly, the original md5sum works for me for a version downloaded > around 1st October. Downloading it again just now, the new version (although > with same name/version) has a new md5sum - also slightly different size: > > chris at d6:/storage/distfiles$ ls -l 26.5.0_Release.tar.gz > -rw-r--r-- 1 chris vislab 128600018 Oct 1 13:49 26.5.0_Release.tar.gz > chris at d6:/storage/distfiles$ md5sum 26.5.0_Release.tar.gz > d7578845894fb58470b54d569615d32f 26.5.0_Release.tar.gz > > and new version: > > chris at d6:/tmp$ ls -l 26.5.0_Release.tar.gz > -rw-r--r-- 1 chris vislab 128600081 Nov 4 20:41 26.5.0_Release.tar.gz > chris at d6:/tmp$ md5sum 26.5.0_Release.tar.gz > 5556f1a1d668a0d1d71387a6e66b53ca 26.5.0_Release.tar.gz > > I hate it when they do that. > > chris me too: it decreases the level of trust that I put on those particular developers. Matteo From s.arcus at open-t.co.uk Fri Nov 4 11:02:17 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Fri, 4 Nov 2016 11:02:17 +0000 Subject: [Slackbuilds-users] Best place to install the EasyRSA scripts? Message-ID: I am making the SBo scripts for EasyRSA, and I need to decide where they will be installed. Before they were removed from Slackware - when they were part of Openvpn, I think they used to go under /usr/share/doc/openvpn. However, it seems a bit strange to install a package in the directory of another package. Maybe /usr/share/doc/easyrsa instead? However, they are sample scripts - not really documentation. According to Linux filesystem standards, would there be a better place? Maybe /usr/share directly, or /us/lib or something? From chris.willing at iinet.net.au Fri Nov 4 11:36:36 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 4 Nov 2016 21:36:36 +1000 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error In-Reply-To: References: <3985d815-0156-995b-c1c5-f04c433a57fd@iinet.net.au> Message-ID: <23c4ae93-3071-1cc4-4d74-d453b1e6baa4@iinet.net.au> On 04/11/16 20:55, Matteo Bernardini wrote: > 2016-11-04 11:47 GMT+01:00 Christoph Willing : >> On 04/11/16 19:02, Willy Sudiarto Raharjo wrote: >>>> >>>> While trying to build PaleMoon 26.5.0, I am suffering from an md5sum >>>> error >>>> on 26.5.0_Release.tar.gz >>>> >>>> The Slackbuild's md5sum is d7578845894fb58470b54d569615d32f but I see >>>> 5556f1a1d668a0d1d71387a6e66b53ca >>>> >>>> I've run my SBo wrapper script twice now. >>>> >>>> Is it me or does the md5sum fail for Y'All too ? >>> >>> >>> Yes, it's incorrect >>> i have fixed it on my branch >>> >> >> Interestingly, the original md5sum works for me for a version downloaded >> around 1st October. Downloading it again just now, the new version (although >> with same name/version) has a new md5sum - also slightly different size: >> >> chris at d6:/storage/distfiles$ ls -l 26.5.0_Release.tar.gz >> -rw-r--r-- 1 chris vislab 128600018 Oct 1 13:49 26.5.0_Release.tar.gz >> chris at d6:/storage/distfiles$ md5sum 26.5.0_Release.tar.gz >> d7578845894fb58470b54d569615d32f 26.5.0_Release.tar.gz >> >> and new version: >> >> chris at d6:/tmp$ ls -l 26.5.0_Release.tar.gz >> -rw-r--r-- 1 chris vislab 128600081 Nov 4 20:41 26.5.0_Release.tar.gz >> chris at d6:/tmp$ md5sum 26.5.0_Release.tar.gz >> 5556f1a1d668a0d1d71387a6e66b53ca 26.5.0_Release.tar.gz >> >> I hate it when they do that. >> >> chris > > me too: it decreases the level of trust that I put on those particular > developers. > That's important for a project that I thought was supposed to be "more open" with fewer binary blobs (unknown code in your system) i.e. more trustworthy. Anyway, I raised an issue about it at their website: https://github.com/MoonchildProductions/Pale-Moon/issues/651 chris From kjhambrick at gmail.com Fri Nov 4 11:38:18 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Fri, 4 Nov 2016 06:38:18 -0500 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error In-Reply-To: <23c4ae93-3071-1cc4-4d74-d453b1e6baa4@iinet.net.au> References: <3985d815-0156-995b-c1c5-f04c433a57fd@iinet.net.au> <23c4ae93-3071-1cc4-4d74-d453b1e6baa4@iinet.net.au> Message-ID: Thank you Christoph ! I think I'll kill the SlackBuild Session and stand by. -- kjh On Fri, Nov 4, 2016 at 6:36 AM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 04/11/16 20:55, Matteo Bernardini wrote: > >> 2016-11-04 11:47 GMT+01:00 Christoph Willing > >: >> >>> On 04/11/16 19:02, Willy Sudiarto Raharjo wrote: >>> >>>> >>>>> While trying to build PaleMoon 26.5.0, I am suffering from an md5sum >>>>> error >>>>> on 26.5.0_Release.tar.gz >>>>> >>>>> The Slackbuild's md5sum is d7578845894fb58470b54d569615d32f but I see >>>>> 5556f1a1d668a0d1d71387a6e66b53ca >>>>> >>>>> I've run my SBo wrapper script twice now. >>>>> >>>>> Is it me or does the md5sum fail for Y'All too ? >>>>> >>>> >>>> >>>> Yes, it's incorrect >>>> i have fixed it on my branch >>>> >>>> >>> Interestingly, the original md5sum works for me for a version downloaded >>> around 1st October. Downloading it again just now, the new version >>> (although >>> with same name/version) has a new md5sum - also slightly different size: >>> >>> chris at d6:/storage/distfiles$ ls -l 26.5.0_Release.tar.gz >>> -rw-r--r-- 1 chris vislab 128600018 Oct 1 13:49 26.5.0_Release.tar.gz >>> chris at d6:/storage/distfiles$ md5sum 26.5.0_Release.tar.gz >>> d7578845894fb58470b54d569615d32f 26.5.0_Release.tar.gz >>> >>> and new version: >>> >>> chris at d6:/tmp$ ls -l 26.5.0_Release.tar.gz >>> -rw-r--r-- 1 chris vislab 128600081 Nov 4 20:41 26.5.0_Release.tar.gz >>> chris at d6:/tmp$ md5sum 26.5.0_Release.tar.gz >>> 5556f1a1d668a0d1d71387a6e66b53ca 26.5.0_Release.tar.gz >>> >>> I hate it when they do that. >>> >>> chris >>> >> >> me too: it decreases the level of trust that I put on those particular >> developers. >> >> That's important for a project that I thought was supposed to be "more > open" with fewer binary blobs (unknown code in your system) i.e. more > trustworthy. > > Anyway, I raised an issue about it at their website: > https://github.com/MoonchildProductions/Pale-Moon/issues/651 > > chris > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Fri Nov 4 13:25:34 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 4 Nov 2016 15:25:34 +0200 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: I do not mind having an "OPTIONAL=" field, if this will make third party automation tools more efficient. -petar 2016-11-04 9:01 GMT+02:00 Andreas Guldstrand : > As the current maintainer of sbotools, I would approve of an OPTIONAL > field like the one proposed by Andrzej, with the "libass:ASS=yes|no" > bits. > > Seems very useful and feasible to implement support for. > > On 3 November 2016 at 19:52, Andrzej Telszewski wrote: >> Hi, >> >> I've spent some time building packages now and although I used an automated >> tool (slackrepo to the rescue, thank you David!), I'm from the camp that >> reads README, trying to leave as little as possible to the fate. >> >> I'm using web browser to find the SlackBuild in question, read on and decide >> what to do. If an optional dependency is mentioned, I search for it, read >> on, and so on ;-) >> >> Searching for optional dependency is the most frustrating point. >> Sometimes there are many search results and you need to scan the list to >> find the one you need. >> Sometimes, the search filed leaves the keyword you entered there, so you >> have to erase it, before proceeding, etc. >> >> So what's the use for OPTIONAL field you ask? >> >> 1) PHP could parse it to give us direct link to the optional SlackBuild in >> question, >> 2) PHP could parse it to let us know about possible circular dependency. >> >> >> When it comes to automated tools, I'd say we need something more than just >> the package name in the OPTIONAL field. >> Probably something like that (ffmpeg for example) would be needed: >> >> OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no" >> >> This would have to be thought through to make the best design decisions and >> the SlackBuilds would have to be standardized in one way or the other. >> >> But for the next iteration, having OPTIONAL field mentioning just the >> packages names and SBo website listing them next to REQUIRES, would be the >> step towards the better, faster and more secure world :-) >> >> >> -- >> Best regards, >> Andrzej Telszewski >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From kjhambrick at gmail.com Fri Nov 4 13:49:43 2016 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Fri, 4 Nov 2016 08:49:43 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: Yes, an OPTIONAL= Line might be nice to have But as Andrzej Telszewski said the syntax would be TBD ... In the meantime, I would love to see something like that :) -- kjh On Fri, Nov 4, 2016 at 8:25 AM, Petar Petrov wrote: > I do not mind having an "OPTIONAL=" field, if this will make third > party automation tools more efficient. > > -petar > > 2016-11-04 9:01 GMT+02:00 Andreas Guldstrand >: > > As the current maintainer of sbotools, I would approve of an OPTIONAL > > field like the one proposed by Andrzej, with the "libass:ASS=yes|no" > > bits. > > > > Seems very useful and feasible to implement support for. > > > > On 3 November 2016 at 19:52, Andrzej Telszewski > wrote: > >> Hi, > >> > >> I've spent some time building packages now and although I used an > automated > >> tool (slackrepo to the rescue, thank you David!), I'm from the camp that > >> reads README, trying to leave as little as possible to the fate. > >> > >> I'm using web browser to find the SlackBuild in question, read on and > decide > >> what to do. If an optional dependency is mentioned, I search for it, > read > >> on, and so on ;-) > >> > >> Searching for optional dependency is the most frustrating point. > >> Sometimes there are many search results and you need to scan the list to > >> find the one you need. > >> Sometimes, the search filed leaves the keyword you entered there, so you > >> have to erase it, before proceeding, etc. > >> > >> So what's the use for OPTIONAL field you ask? > >> > >> 1) PHP could parse it to give us direct link to the optional SlackBuild > in > >> question, > >> 2) PHP could parse it to let us know about possible circular dependency. > >> > >> > >> When it comes to automated tools, I'd say we need something more than > just > >> the package name in the OPTIONAL field. > >> Probably something like that (ffmpeg for example) would be needed: > >> > >> OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no" > >> > >> This would have to be thought through to make the best design decisions > and > >> the SlackBuilds would have to be standardized in one way or the other. > >> > >> But for the next iteration, having OPTIONAL field mentioning just the > >> packages names and SBo website listing them next to REQUIRES, would be > the > >> step towards the better, faster and more secure world :-) > >> > >> > >> -- > >> Best regards, > >> Andrzej Telszewski > >> _______________________________________________ > >> SlackBuilds-users mailing list > >> SlackBuilds-users at slackbuilds.org > >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > >> FAQ - https://slackbuilds.org/faq/ > >> > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Fri Nov 4 15:11:48 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 5 Nov 2016 01:11:48 +1000 Subject: [Slackbuilds-users] PaleMoon 26.5.0 md5sum error In-Reply-To: References: <3985d815-0156-995b-c1c5-f04c433a57fd@iinet.net.au> <23c4ae93-3071-1cc4-4d74-d453b1e6baa4@iinet.net.au> Message-ID: On 04/11/16 21:38, Konrad J Hambrick wrote: > Thank you Christoph ! > > I think I'll kill the SlackBuild Session and stand by. > > -- kjh > > On Fri, Nov 4, 2016 at 6:36 AM, Christoph Willing > > wrote: > > On 04/11/16 20:55, Matteo Bernardini wrote: > > 2016-11-04 11:47 GMT+01:00 Christoph Willing > >: > > On 04/11/16 19:02, Willy Sudiarto Raharjo wrote: > > > While trying to build PaleMoon 26.5.0, I am > suffering from an md5sum > error > on 26.5.0_Release.tar.gz > > The Slackbuild's md5sum is > d7578845894fb58470b54d569615d32f but I see > 5556f1a1d668a0d1d71387a6e66b53ca > > I've run my SBo wrapper script twice now. > > Is it me or does the md5sum fail for Y'All too ? > > > > Yes, it's incorrect > i have fixed it on my branch > > > Interestingly, the original md5sum works for me for a > version downloaded > around 1st October. Downloading it again just now, the new > version (although > with same name/version) has a new md5sum - also slightly > different size: > > chris at d6:/storage/distfiles$ ls -l 26.5.0_Release.tar.gz > -rw-r--r-- 1 chris vislab 128600018 Oct 1 13:49 > 26.5.0_Release.tar.gz > chris at d6:/storage/distfiles$ md5sum 26.5.0_Release.tar.gz > d7578845894fb58470b54d569615d32f 26.5.0_Release.tar.gz > > and new version: > > chris at d6:/tmp$ ls -l 26.5.0_Release.tar.gz > -rw-r--r-- 1 chris vislab 128600081 Nov 4 20:41 > 26.5.0_Release.tar.gz > chris at d6:/tmp$ md5sum 26.5.0_Release.tar.gz > 5556f1a1d668a0d1d71387a6e66b53ca 26.5.0_Release.tar.gz > > I hate it when they do that. > > chris > > > me too: it decreases the level of trust that I put on those > particular > developers. > > That's important for a project that I thought was supposed to be > "more open" with fewer binary blobs (unknown code in your system) > i.e. more trustworthy. > > Anyway, I raised an issue about it at their website: > https://github.com/MoonchildProductions/Pale-Moon/issues/651 > > I think its all OK: chris at d6:/tmp$ diff -r PM1 PM2 diff -r PM1/Pale-Moon-26.5.0_Release/addon-sdk/source/python-lib/cuddlefish/_version.py PM2/Pale-Moon-26.5.0_Release/addon-sdk/source/python-lib/cuddlefish/_version.py 12c12 < git_refnames = " (tag: 26.5.0_Release, v26_Dev)" --- > git_refnames = " (tag: 26.5.0_Release)" where PM1 was the original tarball, PM2 the currently downloadable tarball. BTW to the maintainer, a nicer download url to use would be: https://github.com/MoonchildProductions/Pale-Moon/archive/26.5.0_Release/Pale-Moon-26.5.0.tar.gz which would give you a properly named tarball i.e. PaleMoon-26.5.0.tar.gz instead of the ugly and confusing 26.5.0_Release.tar.gz using the current url. chris From atelszewski at gmail.com Fri Nov 4 15:47:39 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 4 Nov 2016 16:47:39 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: On 04/11/16 14:49, Konrad J Hambrick wrote: > Yes, an OPTIONAL= Line might be nice to have > > But as Andrzej Telszewski said the syntax would be TBD ... > > In the meantime, I would love to see something like that :) Yet another possibility would be to have special tags for README, something like: [opt]libass[/opt] Such tags would have to be nice for those who read READMEs as plain text. On the website, the README could be parsed to generate OPTIONAL field of the .info file. This would lessen the job of maintainers and lower the possibility of inconsistency between README and .info. Another thing I would love to see is some form of README formatting when displayed in the web browser. Having required, run-time and build-time dependencies all in separate, nicely laid out tables would be cool. Again, all of this would have to be easily readable for pure text guys. I'm not maintaining too many SlackBuilds, so my voice is what it is ;-) -- Best regards, Andrzej Telszewski From alik at ejik.org Fri Nov 4 17:08:02 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 04 Nov 2016 20:08:02 +0300 Subject: [Slackbuilds-users] problems with 'volti' Message-ID: <1478279282.2807427.777652577.120BEB66@webmail.messagingengine.com> Hello, there are problems with the volti SlackBuild: 1. the download link is wrong, the new one that I found is: https://github.com/gen2brain/volti/archive/0.2.3/volti-0.2.3.tar.gz 2. the file PKG-INFO went away and should be removed from volti.SlackBuild. 3. The maintainer's address doesn't work: : Host or domain name not found. Name service error for name=gnomeslackbuild.org type=A: Host not found Best regards, Alexander From willysr at slackbuilds.org Fri Nov 4 17:54:58 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Nov 2016 00:54:58 +0700 Subject: [Slackbuilds-users] problems with 'volti' In-Reply-To: <1478279282.2807427.777652577.120BEB66@webmail.messagingengine.com> References: <1478279282.2807427.777652577.120BEB66@webmail.messagingengine.com> Message-ID: > there are problems with the volti SlackBuild: > > 1. the download link is wrong, the new one that I found is: > > https://github.com/gen2brain/volti/archive/0.2.3/volti-0.2.3.tar.gz > > 2. the file PKG-INFO went away and should be removed from > volti.SlackBuild. > > 3. The maintainer's address doesn't work: > > : Host or domain name not found. Name service > error for name=gnomeslackbuild.org type=A: Host not found Thanks for reporting it has been fixed on my branch if you are willing to step up and take over this package, please submit an update after the public update -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Fri Nov 4 18:25:32 2016 From: baildon.research at googlemail.com (David Spencer) Date: Fri, 4 Nov 2016 18:25:32 +0000 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: Hi - let me say to start that this is only a personal opinion, and I've been too busy recently to pay careful attention to this discussion. But IIRC we've talked about this before. In my opinion, real life is much too complex for OPTIONAL= Look at this example (graphics/luminance-hdr) > The following are optional dependencies: > cfitsio and CCfits - for importing FITS images (both needed) > hugin - for aligning multiple LDR exposures And this example (gis/gdal): > The following optional requirements are detected automatically: > cfitsio, freexl, hdf, hdf5, libwebp, netcdf, postgresql, xerces-c > > To enable OpenCL GPU-accelerated performance, specify the option > OPENCL=yes (requires opencl-headers to build, and either nvidia-driver > or amd-app-sdk with suitable GPU hardware to run). Users need to know what useful features each dep provides, if that information is available upstream. Users need to know if some deps are needed together (like cfitsio and CCfits above), or if some deps are mutually exclusive (like nvidia-driver and amd-app-sdk above). Some users want to know if deps are build-time only, or run-time only. Users need to know whether deps are automatically detected, or whether there are environment variables that need to be set. (Not all SlackBuilds use environment variables in the same way, and some SlackBuilds would need to be rewritten if we standardised on (for example) OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no". Who's going to find them all? Who's going to fix them all? Who's going to change all the users' queue files and build scripts?) And some users (ok, me) don't like XML, and don't like YAML, and don't like new stuff such as "[opt]libass[/opt]" that I'd have to write a parser for from scratch when XML and YAML already exist, and don't like reading stuff that's complicated. I don't think anybody -- either maintainers or users -- would enjoy having half the README file or the .info file written in YAML, but that's the kind of thing that would be needed if you look at all the real examples in SBo. IMO it's best to read all ~5800 README files before thinking about a solution. I've done it. It's quite easy to spot the interesting ones if you step through them quickly. Cheers -D. From alik at ejik.org Fri Nov 4 18:33:09 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Fri, 04 Nov 2016 21:33:09 +0300 Subject: [Slackbuilds-users] problems with 'volti' In-Reply-To: References: <1478279282.2807427.777652577.120BEB66@webmail.messagingengine.com> Message-ID: <1478284389.2824558.777732553.0518BA47@webmail.messagingengine.com> > if you are willing to step up and take over this package, please > submit an update after the public update I actually just tested it and found that it's not for me. Best regards, Alexander On Fri, Nov 4, 2016, at 20:54, Willy Sudiarto Raharjo wrote: > > there are problems with the volti SlackBuild: > > > > 1. the download link is wrong, the new one that I found is: > > > > https://github.com/gen2brain/volti/archive/0.2.3/volti-0.2.3.tar.gz > > > > 2. the file PKG-INFO went away and should be removed from > > volti.SlackBuild. > > > > 3. The maintainer's address doesn't work: > > > > : Host or domain name not found. Name service > > error for name=gnomeslackbuild.org type=A: Host not found > > Thanks for reporting > it has been fixed on my branch > > if you are willing to step up and take over this package, please submit > an update after the public update > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > Email had 1 attachment: > + signature.asc > 1k (application/pgp-signature) From hba.nihilismus at gmail.com Fri Nov 4 19:07:16 2016 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Fri, 4 Nov 2016 13:07:16 -0600 Subject: [Slackbuilds-users] libraries/libkate: You should recreate aclocal.m4 In-Reply-To: <9d9f1395-0bbc-fa03-7cab-9c2724abd3c2@slackbuilds.org> References: <9d9f1395-0bbc-fa03-7cab-9c2724abd3c2@slackbuilds.org> Message-ID: On Thu, Nov 3, 2016 at 3:46 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > is this a clean slackware64-14.2 or upgrade from previous version? > Weird enough... slackware64-14.2 clean install and using sbopkg too. Not my system but *sbopkg -b libkate* was executed some minutes ago and it worked... false alarm ;-) - Cheers -- Antonio Hern?ndez Blas | Oaxaca, M?xico, Mx. https://github.com/nihilismus | https://bitbucket.org/nihilismus | https://twitter.com/nihilipster -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas.guldstrand at gmail.com Fri Nov 4 20:40:14 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Fri, 4 Nov 2016 21:40:14 +0100 Subject: [Slackbuilds-users] Best place to install the EasyRSA scripts? In-Reply-To: References: Message-ID: How about '/usr/libexec'? On 4 November 2016 at 12:02, Sebastian Arcus wrote: > I am making the SBo scripts for EasyRSA, and I need to decide where they > will be installed. Before they were removed from Slackware - when they were > part of Openvpn, I think they used to go under /usr/share/doc/openvpn. > However, it seems a bit strange to install a package in the directory of > another package. Maybe /usr/share/doc/easyrsa instead? However, they are > sample scripts - not really documentation. According to Linux filesystem > standards, would there be a better place? Maybe /usr/share directly, or > /us/lib or something? > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From ts at websafe.pl Fri Nov 4 22:23:06 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Fri, 4 Nov 2016 23:23:06 +0100 Subject: [Slackbuilds-users] Best place to install the EasyRSA scripts? In-Reply-To: References: Message-ID: <30cd6ea3-9c21-5ae9-6e98-0eb9a65ae25f@websafe.pl> On 11/04/2016 12:02 PM, Sebastian Arcus wrote: > I am making the SBo scripts for EasyRSA, and I need to decide where they > will be installed. Before they were removed from Slackware - when they > were part of Openvpn, I think they used to go under > /usr/share/doc/openvpn. However, it seems a bit strange to install a > package in the directory of another package. Maybe > /usr/share/doc/easyrsa instead? However, they are sample scripts - not > really documentation. According to Linux filesystem standards, would > there be a better place? Maybe /usr/share directly, or /us/lib or > something? It was very handy to have them in /etc/openvpn/... EasyRSA scripts will create keys in the `keys` subdir, so /usr/share and /usr/doc are probably not the best location without patching KEY_DIR in easyrsa/*/vars to point to a more reasonable location export KEY_DIR="$EASY_RSA/keys" But this still should not be an absolute path, because when you're running multiple openvpn servers you would normally have something like: /etc/openvpn/server/server1/easyrsa/*/keys /etc/openvpn/server/server2/easyrsa/*/keys /etc/openvpn/server/server3/easyrsa/*/keys and a patched KEY_DIR would place all keys by default in one directory. That's not what you want (with multiple servers). So after rethinking this my suggestion is: /usr/share/easyrsa without patching KEY_DIR (keys placed in subdir) and users will have to copy the contents of /usr/share/easyrsa to a writable location like /etc/openvpn/server/server1/easyrsa -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sat Nov 5 00:34:34 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Nov 2016 07:34:34 +0700 Subject: [Slackbuilds-users] Updates - 20161105.1 Message-ID: <0d833700-7614-95cd-954a-b74c0a8b5dc2@slackbuilds.org> Sat Nov 5 00:17:41 UTC 2016 academic/gwyddion: Add more patches. audio/sayonara-player: Updated for version 0.9.2-git11. audio/snd: Updated for version 16.9. audio/sunvox: Updated for version 1.9.2. audio/volti: Switch to github release. desktop/ComixCursors: Updated for version 0.9.0. desktop/lumina: Fix VERSION. desktop/neofetch: Updated for version 1.9. desktop/numix-gtk-theme: Updated for version 2.6.5.606.201610230531. desktop/numix-pack: Updated for version 0.4.1. desktop/py3status: Updated for version 3.2. desktop/wbar: Fix DOWNLOAD. desktop/xed: Updated for version 1.2.0. development/Bottleneck: Updated for version 1.2.0. development/atom: Update script. development/ccl: Added (Clozure Common Lisp). development/dmd: Updated for version 2.072.0. development/flow: Updated for version 0.34.0. development/gambas3: Updated for version 3.9.1. development/gtest: Updated for version 1.8.0. development/gtkdialog: Updated for version 0.8.3. development/maude: Added (high-performance reflective language). development/menhir: Updated for version 20160825. development/mutagen: Updated for version 1.35. development/neovim: Updated for version 0.1.6. development/p4v: Updated for version 2015.2.1458499. development/perf: Updated for version 4.4.29. development/poedit: Updated for version 1.8.11. development/sbcl: Updated for version 1.3.11. development/valgrind: Updated for version 3.12.0. games/atanks: Updated for version 6.5. games/domination: Use ARCH=noarch. games/doomretro: Updated for version 2.3.3. games/mame: Updated for version 0.179. games/opendune: Added (realtime strategy game). games/ppsspp: Update script. games/snes9x: Fix MD5SUM. games/stockfish: Added (UCI chess engine). gis/opencpn: Update DEP and README. gis/qgis: Updated for version 2.18.0. graphics/pngcrush: Updated for version 1.8.10. graphics/tintii: Updated for version 2.10.0. libraries/audioread: Updated for version 2.1.4. libraries/buddy: Added (Binary Decision Diagram library). libraries/daq: Force -j1. libraries/fuzzylite: Updated for version 5.1. libraries/libfilezilla: Updated for version 0.8.0. libraries/libfixposix: Added (Thin wrapper over POSIX syscalls). libraries/libtecla: Added (interactive command line editing). libraries/live555: Updated for version 2016.11.03 libraries/poco: Updated for version 1.7.6. libraries/pycparser: Updated for version 2.17. libraries/python-gnupg: Updated for version 0.3.9. libraries/toro: Updated for version 1.0.1. misc/KeePassHttp: Added (plugin for KeePass). multimedia/MP3Diags: Add missing doinst.sh. multimedia/gaupol: Updated an optional dependency in the README. multimedia/mkvtoolnix: Updated for version 9.5.0. multimedia/opera-ffmpeg-codecs: Added (Extra ffmpeg codec). multimedia/pepperflash-plugin: Updated for version 23.0.0.205. multimedia/spotify: Updated for version 1.0.42.145.g7a5a182e. network/Electrum-DASH: Added (dash client). network/PaleMoon: Update MD5SUM. network/SoulseekQt: Added (Soulseek P2P network client). network/bitcoin: Updated for version 0.13.1. network/boxcryptor: Updated for version 2.2.410.162. network/filezilla: Updated for version 3.22.2. network/lighttpd: Updated for version 1.4.43. network/mpop: Updated for version 1.2.5. network/ncrack: Added (network authentication cracking tool). network/nsd: Added (Name Server Daemon). network/opera-developer: Update README and script. network/opera: Added (Fast and secure web browser). network/otter: Updated for version 0.9.11. network/retroshare: Update script. network/suricata: Updated for version 3.1.3. network/tor: Updated for version 0.2.8.9. network/wire: Updated for version 2.11.2665. office/CherryTree: Updated for version 0.37.6. office/LanguageTool: Updated for version 3.5. office/LibreOffice: Updated for version 5.2.3.3 office/libreoffice-helppack: Updated for version 5.2.3. office/libreoffice-langpack: Updated for version 5.2.3. office/libreoffice: Updated for version 5.2.3. office/lyx: Updated for version 2.2.2. office/multivalent-tool-pdf: Added (PDF tools). office/rednotebook: Updated an optional dependency in the README. office/texlive-docs: Updated for version 2016.161031. office/texlive-extra: Updated for version 2016.161031. office/texlive-fonts: Updated for version 2016.161031. office/texlive: Updated for version 2016.161031. perl/perl-Math-GMPz: Updated for version 0.44. python/Flask: Updated for version 0.11.1. python/colored: Updated for version 1.3.2. python/cssutils: Updated an optional dependency in the README. python/mnemonic: Added (reference implementation of BIP-0039). python/ndg_httpsclient: Updated for version 0.4.2. python/pendulum: Updated for version 0.6.5. python/psutil: Updated for version 4.4.1 python/python-x11_hash: Added (Python Module). python/sge-pygame: Updated for version 1.3. python/simplejson: Updated for version 3.10.0 python/tqdm: Updated for version 4.9.0. python/trezor: Added (Bitcoin Hardware Wallet). ruby/heroku-client: Update MD5SUM. system/I-Nex: Updated for version 7.6.0. system/bit-babbler: Added (Hardware True Random Number generator). system/dar: Updated for version 2.5.7. system/fakeroot: Update script. system/fzf: Updated for version 0.15.5. system/krusader: Updated for version git_20150309_13fa966. system/ttygif: Updated for version 1.3.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rob0 at slackbuilds.org Sat Nov 5 00:56:32 2016 From: rob0 at slackbuilds.org (Rob McGee) Date: Fri, 4 Nov 2016 19:56:32 -0500 Subject: [Slackbuilds-users] Best place to install the EasyRSA scripts? In-Reply-To: <30cd6ea3-9c21-5ae9-6e98-0eb9a65ae25f@websafe.pl> References: <30cd6ea3-9c21-5ae9-6e98-0eb9a65ae25f@websafe.pl> Message-ID: <20161105005632.GZ6526@harrier.slackbuilds.org> On Fri, Nov 04, 2016 at 11:23:06PM +0100, Thomas Szteliga wrote: > On 11/04/2016 12:02 PM, Sebastian Arcus wrote: > > I am making the SBo scripts for EasyRSA, and I need to decide > > where they will be installed. Before they were removed from > > Slackware - when they were part of Openvpn, I think they used to > > go under /usr/share/doc/openvpn. However, it seems a bit strange > > to install a package in the directory of another package. Maybe > > /usr/share/doc/easyrsa instead? However, they are sample scripts > > - not really documentation. According to Linux filesystem > > standards, would there be a better place? Maybe /usr/share > > directly, or /us/lib or something? > > It was very handy to have them in /etc/openvpn/... Eeek! Why? At least 3 problems I see with that as it implies: 1. that you have your CA on an openvpn server or client; 2. that you will be running these scripts as root; 3. that your CA is limited to use for openvpn. #1 is the big one, because that promotes insecure user practices; Slackbuilds.org MUST NOT do that. > EasyRSA scripts will create keys in the `keys` subdir, > so /usr/share and /usr/doc are probably not the best location > without patching KEY_DIR in easyrsa/*/vars to point > to a more reasonable location > > export KEY_DIR="$EASY_RSA/keys" > > But this still should not be an absolute path, > because when you're running multiple openvpn servers > you would normally have something like: > > /etc/openvpn/server/server1/easyrsa/*/keys > /etc/openvpn/server/server2/easyrsa/*/keys > /etc/openvpn/server/server3/easyrsa/*/keys Ewww, really, why? First thing, see above. Also a server only needs ITS OWN KEY, it does not need (and should not have!) any other keys. Admittedly I have never been in the position of having to support multiple servers, but I'd still only maintain a single CA for all of them in any given organization. If you need to restrict access on any given server, use a --client-config-dir and --ccd-exclusive (touch a file in the CCD for any permitted client's commonName on that server instance.) > and a patched KEY_DIR would place all keys by default > in one directory. That's not what you want (with multiple servers). > > > So after rethinking this my suggestion is: > > > /usr/share/easyrsa without patching KEY_DIR (keys placed in subdir) Hehe, actually I don't have any strong feelings against this suggestion. It's as good as any. > and users will have to copy the contents of /usr/share/easyrsa > to a writable location like /etc/openvpn/server/server1/easyrsa Eeek! How about /home/ca/ ? -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From ts at websafe.pl Sat Nov 5 01:43:14 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 5 Nov 2016 02:43:14 +0100 Subject: [Slackbuilds-users] Best place to install the EasyRSA scripts? In-Reply-To: <20161105005632.GZ6526@harrier.slackbuilds.org> References: <30cd6ea3-9c21-5ae9-6e98-0eb9a65ae25f@websafe.pl> <20161105005632.GZ6526@harrier.slackbuilds.org> Message-ID: <4fc90ba1-756d-fab5-0d45-7e008150bf62@websafe.pl> On 11/05/2016 01:56 AM, Rob McGee wrote: > At least 3 problems I see with that as it implies: > 1. that you have your CA on an openvpn server or client; > 2. that you will be running these scripts as root; > 3. that your CA is limited to use for openvpn. > #1 is the big one, because that promotes insecure user practices; > Slackbuilds.org MUST NOT do that. I'm aware. I have a separated isolated VM just for generating CA's, keys and testing configs for multiple servers/clients. > Admittedly I have never been in the position of having to support > multiple servers, but I'd still only maintain a single CA for all of > them in any given organization. If you need to restrict access on > any given server, use a --client-config-dir and --ccd-exclusive > (touch a file in the CCD for any permitted client's commonName on > that server instance.) I have individual CA's for each server, even when in a single organization and of course if clients of a single server need individual settings ccd's are used. > Hehe, actually I don't have any strong feelings against this > suggestion. It's as good as any. I think /usr/doc/easy-rsa is way better than /usr/doc/easy-rsa- /usr/libexec somehow feels really wrong. CentOS: /usr/share/easy-rsa/ Archlinux: /etc/easy-rsa FreeBSD: /usr/local/share/easy-rsa >> and users will have to copy the contents of /usr/share/easyrsa >> to a writable location like /etc/openvpn/server/server1/easyrsa > Eeek! How about /home/ca/ ? Oh no, really, a user for each CA? ;-) And just another fun-fact ;-) ~~~~ If you are using Linux, BSD, or a unix-like OS, open a shell and cd to the easy-rsa subdirectory. If you installed OpenVPN from an RPM or DEB file, the easy-rsa directory can usually be found in /usr/share/doc/packages/openvpn or /usr/share/doc/openvpn (it's best to copy this directory to another location such as /etc/openvpn, before any edits, so that future OpenVPN package upgrades won't overwrite your modifications). If you installed from a .tar.gz file, the easy-rsa directory will be in the top level directory of the expanded source tree. ~~~~ Again: "it's best to copy this directory to another location such as /etc/openvpn" :-)))) It's from the official howto: https://openvpn.net/index.php/open-source/documentation/howto.html -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From dpross1100 at msn.com Sat Nov 5 02:23:13 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 Nov 2016 02:23:13 +0000 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: References: <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: Hi, I am installing ffmpeg on a clean 14.2 system (well, actually I am installing vlc in order to test something, and ffmpeg is a dependency, but that's not important). I have tetex installed instead of texlive, and I get the following error: Could not find texi2html! Please make sure to have tetex or texlive installed and that texi2html is in PATH. The message is clear enough: the problem is that texi2html is not in the PATH. I checked the install log for tetex and found that it is in /usr/share/texmf/bin, so I made a symlink for it in /usr/bin. Is this situation expected? IMO it is not a great solution, because ideally any given package on SBo *should* build properly on a clean system provided all the dependencies are present, without having to manually create symlinks or modify the PATH. Someone new to Linux and/or Slackware, for example, would probably be stuck. At the very least, the README for ffmpeg should make it clear how to get around the problem. Or am I missing something? Dan From dpross1100 at msn.com Sat Nov 5 02:32:29 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 Nov 2016 02:32:29 +0000 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: References: <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: I'm sorry, that was not supposed to be a reply to the OPTIONAL thread. I will re-send it as a new message. Dan On Sat, Nov 05, 2016 at 02:23:13AM +0000, Daniel Prosser wrote: > Hi, > > I am installing ffmpeg on a clean 14.2 system (well, actually I am > installing vlc in order to test something, and ffmpeg is a dependency, > but that's not important). I have tetex installed instead of texlive, > and I get the following error: > > Could not find texi2html! Please make sure to have tetex or texlive > installed and that texi2html is in PATH. > > The message is clear enough: the problem is that texi2html is not in the > PATH. I checked the install log for tetex and found that it is in > /usr/share/texmf/bin, so I made a symlink for it in /usr/bin. Is this > situation expected? IMO it is not a great solution, because ideally any > given package on SBo *should* build properly on a clean system provided > all the dependencies are present, without having to manually create > symlinks or modify the PATH. Someone new to Linux and/or Slackware, for > example, would probably be stuck. At the very least, the README for > ffmpeg should make it clear how to get around the problem. > > Or am I missing something? > > Dan > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From dpross1100 at msn.com Sat Nov 5 02:34:32 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 Nov 2016 02:34:32 +0000 Subject: [Slackbuilds-users] ffmpeg and tetex Message-ID: (This is a copy of the message I accidentally sent as a reply to a different thread. Please respond to this one.) Hi, I am installing ffmpeg on a clean 14.2 system (well, actually I am installing vlc in order to test something, and ffmpeg is a dependency, but that's not important). I have tetex installed instead of texlive, and I get the following error: Could not find texi2html! Please make sure to have tetex or texlive installed and that texi2html is in PATH. The message is clear enough: the problem is that texi2html is not in the PATH. I checked the install log for tetex and found that it is in /usr/share/texmf/bin, so I made a symlink for it in /usr/bin. Is this situation expected? IMO it is not a great solution, because ideally any given package on SBo *should* build properly on a clean system provided all the dependencies are present, without having to manually create symlinks or modify the PATH. Someone new to Linux and/or Slackware, for example, would probably be stuck. At the very least, the README for ffmpeg should make it clear how to get around the problem. Or am I missing something? Dan From elyk03 at gmail.com Sat Nov 5 03:51:37 2016 From: elyk03 at gmail.com (Kyle Guinn) Date: Fri, 4 Nov 2016 22:51:37 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: On 11/4/16, David Spencer wrote: > Hi - let me say to start that this is only a personal opinion, and > I've been too busy recently to pay careful attention to this > discussion. But IIRC we've talked about this before. In my opinion, > real life is much too complex for OPTIONAL= > > Look at this example (graphics/luminance-hdr) > >> The following are optional dependencies: >> cfitsio and CCfits - for importing FITS images (both needed) >> hugin - for aligning multiple LDR exposures > > And this example (gis/gdal): > >> The following optional requirements are detected automatically: >> cfitsio, freexl, hdf, hdf5, libwebp, netcdf, postgresql, xerces-c >> >> To enable OpenCL GPU-accelerated performance, specify the option >> OPENCL=yes (requires opencl-headers to build, and either nvidia-driver >> or amd-app-sdk with suitable GPU hardware to run). > > Users need to know what useful features each dep provides, if that > information is available upstream. > > Users need to know if some deps are needed together (like cfitsio and > CCfits above), or if some deps are mutually exclusive (like > nvidia-driver and amd-app-sdk above). > > Some users want to know if deps are build-time only, or run-time only. > > Users need to know whether deps are automatically detected, or whether > there are environment variables that need to be set. (Not all > SlackBuilds use environment variables in the same way, and some > SlackBuilds would need to be rewritten if we standardised on (for > example) OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no". Who's > going to find them all? Who's going to fix them all? Who's going to > change all the users' queue files and build scripts?) > > And some users (ok, me) don't like XML, and don't like YAML, and don't > like new stuff such as "[opt]libass[/opt]" that I'd have to write a > parser for from scratch when XML and YAML already exist, and don't > like reading stuff that's complicated. I don't think anybody -- either > maintainers or users -- would enjoy having half the README file or the > .info file written in YAML, but that's the kind of thing that would be > needed if you look at all the real examples in SBo. > > IMO it's best to read all ~5800 README files before thinking about a > solution. I've done it. It's quite easy to spot the interesting ones > if you step through them quickly. > > Cheers > -D. I like the idea of having an OPTIONAL field because it could allow us to have clickable links on the website, and you could use it to build a better dependency graph. So for example if I'm updating a library and want to know what packages might be using it, searching through both REQUIRES and OPTIONAL could turn up a lot more hits than REQUIRES alone. It'd also be much more accurate than searching through README. I'm not a fan of putting script parameters in OPTIONAL, I think that would turn into a mess in a hurry. Better to keep that info in the README, and just keep OPTIONAL as a list of packages just like REQUIRES. Basically if any optional package is mentioned in the README, also put it in OPTIONAL just to establish a link between the two. This is somewhat off-topic, but I remember discussions in the past that the file is called README because you need to read it. But I'm sure we're all guilty of not reading it at some point. I usually don't, thinking that it just contains the package description, and if I'm installing it I already have an idea of what it does and why I need it. Then I realize there may be installation information I'm missing, so I go back and read it. What do you think about splitting off the package description into its own file (named "ABOUT" or somesuch)? ABOUT would contain the description (maybe just a repeat of slack-desc, or something longer and more detailed). README would contain package conflicts, more info about optional dependencies and what they would provide, script variables, pre-build or post-build instructions, etc. The README file itself would be optional in case there are no extra instructions, but if it exists you should read it! Each package should contain at least one of the two files, the website would show both, and descriptions could slowly be migrated to the ABOUT file at the maintainer's leisure. Any opinions? -Kyle From slackbuilds at schoepfer.info Sat Nov 5 06:12:07 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 05 Nov 2016 07:12:07 +0100 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: References: Message-ID: <1274b122bb5567806db46167c1845afe@schoepfer.info> > Could not find texi2html! Please make sure to have tetex or texlive > installed and that texi2html is in PATH. In the terminal you build in: source /etc/profile.de/tetex.sh It seems you installed tetex, but didn't login again or reboot. That would have fixed your issue also. The ffmpeg-version from SBo is able to build the documentations with help of texinfo package(stock package), which in that case actually doesn't need tetex/texlive at all. The warning comes from the ffmpeg.SlackbBuild(not from ffmpeg ./configure) and may need to be fxied, that was discussed some time agao, Heinz said that's on his todo-queue. Johannes From slackbuilds at schoepfer.info Sat Nov 5 08:45:39 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 05 Nov 2016 09:45:39 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> > In my opinion, > real life is much too complex for OPTIONAL= I feel it's too much hassle without that field, at least for an enduser. The OPTION field -should NOT replace the README. -is not meant to be complex to force a debian-apt-like engine, which wants to cover every case and will therefore fail. -is meant to cover the OPTIONS which are already present in BuildScripts, and that bin a better way, not more. In my ideal world: -On https://slackbuilds.org render content of slack-desc(instead of README) + REQUIRED + OPTIONAL (like Kyle proposed, if understood him right) -Leave README as is(clickable as all package-content) -Mandatory OPTIONAL-field in the .info-file for new submussion > Look at this example (graphics/luminance-hdr) > >> The following are optional dependencies: >> cfitsio and CCfits - for importing FITS images (both needed) >> hugin - for aligning multiple LDR exposures REQUIRES="qt5-webkit" OPTIONAL="hugin,cfitsio & CCfits" > And this example (gis/gdal): > >> The following optional requirements are detected automatically: >> cfitsio, freexl, hdf, hdf5, libwebp, netcdf, postgresql, xerces-c >> >> To enable OpenCL GPU-accelerated performance, specify the option >> OPENCL=yes (requires opencl-headers to build, and either nvidia-driver >> or amd-app-sdk with suitable GPU hardware to run). REQUIRES="geos,proj" OPTIONAL="opencl-headers:(nvidia-driver|amd-app-sdk), cfitsio,freexl,hdf,hdf5,libwebp,netcdf,postgresql,xerces-c" Easy enough in my opinion, also easy&fast to understand if one is not a native english speaker. > Users need to know what useful features each dep provides, if that > information is available upstream. > Some users want to know if deps are build-time only, or run-time only. > Users need to know whether deps are automatically detected, or whether > there are environment variables that need to be set. This is also not completely covered in all READMEs the current state, and doesn't get worse if there would be an OPTION-field also. > (Not all > SlackBuilds use environment variables in the same way, and some > SlackBuilds would need to be rewritten if we standardised on (for > example) OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no". Who's > going to find them all? Who's going to fix them all? Who's going to > change all the users' queue files and build scripts?) I volonteer to help. If the OPTIONAL-field is added to all SlackBuilds nothing will break if it's empty at first. Every SBo-submission would also help in parallel. > And some users (ok, me) don't like XML, and don't like YAML, and don't > like new stuff such as "[opt]libass[/opt]" > parser for from scratch when XML and YAML already exist, and don't > like reading stuff that's complicated. I don't think anybody -- either > maintainers or users -- would enjoy having half the README file or the > .info file written in YAML, but that's the kind of thing that would be > needed if you look at all the real examples in SBo. No YAML or XML needed to be written, just a simple syntax as proposed. > IMO it's best to read all ~5800 README files before thinking about a > solution. Is that really your proposal for all slackware-maintainers, or for all SBo-users? I'll get divorced from my wife, if i do that ;-) Johannes From baildon.research at googlemail.com Sat Nov 5 10:56:56 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 5 Nov 2016 10:56:56 +0000 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> Message-ID: > No YAML or XML needed to be written, just a simple syntax as proposed. Simple? Here's an offer. If *you* write all the code needed for slackrepo to parse that "simple syntax", and all the code needed for the user to select which options they actually want, and for slackrepo to remember them, and to make them happen when building, and do all that in a way that's compatible with slackrepo's existing configuration -- because slackrepo *already* has a 'hintfile' mechanism for selecting and remembering optional dependencies, and I genuinely did look at all the SBo READMEs to see what would work in the real world and to see what optional deps the default hintfiles should enable for lots of important packages -- then I'll consider merging it. > Is that really your proposal for all slackware-maintainers, or for all SBo-users? As I clearly wrote, it's for anybody who thinks they can design a solution like "OPTIONAL=". If you haven't checked how well the solution works for all the problems it's supposed to solve, you haven't finished the solution. -D. From dpross1100 at msn.com Sat Nov 5 11:34:59 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 Nov 2016 11:34:59 +0000 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: <1274b122bb5567806db46167c1845afe@schoepfer.info> References: <1274b122bb5567806db46167c1845afe@schoepfer.info> Message-ID: On Sat, Nov 05, 2016 at 07:12:07AM +0100, Franzen wrote: > > In the terminal you build in: > source /etc/profile.de/tetex.sh > > It seems you installed tetex, but didn't login again or reboot. That would > have fixed your issue also. > Aha! That's what I was missing. The first time I tried installing vlc, I did not have any latex package installed. When I got that error, I simply installed tetex and tried again. So I guess it's not really an issue, but maybe it would be a good idea for the maintainer to put that info you just told me in the README or the error message. Thanks, Dan From willysr at slackbuilds.org Sat Nov 5 11:52:07 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Nov 2016 18:52:07 +0700 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: References: <1274b122bb5567806db46167c1845afe@schoepfer.info> Message-ID: >> In the terminal you build in: >> source /etc/profile.de/tetex.sh >> >> It seems you installed tetex, but didn't login again or reboot. That would >> have fixed your issue also. >> > > Aha! That's what I was missing. The first time I tried installing vlc, I > did not have any latex package installed. When I got that error, I > simply installed tetex and tried again. So I guess it's not really an > issue, but maybe it would be a good idea for the maintainer to put that > info you just told me in the README or the error message. You should run the script using "su -" instead of "su" That should solve the problem with tetex PATH -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Nov 5 12:00:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Nov 2016 19:00:39 +0700 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> Message-ID: > If *you* write all the code needed for slackrepo to parse that "simple > syntax", and all the code needed for the user to select which options > they actually want, and for slackrepo to remember them, and to make > them happen when building, and do all that in a way that's compatible > with slackrepo's existing configuration -- because slackrepo *already* > has a 'hintfile' mechanism for selecting and remembering optional > dependencies, and I genuinely did look at all the SBo READMEs to see > what would work in the real world and to see what optional deps the > default hintfiles should enable for lots of important packages -- then > I'll consider merging it. > >> Is that really your proposal for all slackware-maintainers, or for all SBo-users? > > As I clearly wrote, it's for anybody who thinks they can design a > solution like "OPTIONAL=". If you haven't checked how well the > solution works for all the problems it's supposed to solve, you > haven't finished the solution. I personally don't see real benefit of doing it since everything is working fine with current README/REQUIRES. You just have to READ the README (which is why it's called README). If you need to list optional deps, it's simpler to make a new document called README.Slackware (or anything you like) and describe everything you want to tell which can't be listed in the original README. Some packages have been using it. It requires no changes at all for approval process and people are free to write all the optional deps there. Second problem is about maintainer's willingness to check EVERY optional dependencies and make sure it stays to build fine under ALL possible combinations. Do they have to track every one of them? Sooner or later, it will become a burden to maintainers (and admins during freeze period before new branch is released). -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sat Nov 5 12:09:00 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 13:09:00 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> Message-ID: <270aaed6-3126-be40-0b1e-6a8088674429@gmail.com> On 05/11/16 11:56, David Spencer wrote: >> No YAML or XML needed to be written, just a simple syntax as proposed. > > Simple? > > Here's an offer. > > If *you* write all the code needed for slackrepo to parse that "simple > syntax", and all the code needed for the user to select which options > they actually want, and for slackrepo to remember them, and to make > them happen when building, and do all that in a way that's compatible > with slackrepo's existing configuration -- because slackrepo *already* > has a 'hintfile' mechanism for selecting and remembering optional > dependencies, and I genuinely did look at all the SBo READMEs to see > what would work in the real world and to see what optional deps the > default hintfiles should enable for lots of important packages -- then > I'll consider merging it. > You don't have to actually implement anything other than skipping new OPTIONAL field in .info. At some point, if you decided you have the time, you then would go about it. >> Is that really your proposal for all slackware-maintainers, or for all SBo-users? > > As I clearly wrote, it's for anybody who thinks they can design a > solution like "OPTIONAL=". If you haven't checked how well the > solution works for all the problems it's supposed to solve, you > haven't finished the solution. > That is of course valid point, as with every good software design. > -D. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- Best regards, Andrzej Telszewski From slackbuilds at schoepfer.info Sat Nov 5 12:17:12 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 05 Nov 2016 13:17:12 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> Message-ID: <4d606a848af7146ce20c9ea40da576e7@schoepfer.info> >> No YAML or XML needed to be written, just a simple syntax as proposed. > > Simple? > > Here's an offer. David, sorry if i was offending, that was not my intention. > If *you* write all the code needed for slackrepo to parse that "simple What i read about slackrepo, it' really great, but i will not write code for slackrepo, as i'm not using it. I wrote my thoughts about an OPTIONAL-field, maybe dumb thoughts, i don't know. That OPTIONAL-field would not break any third-party-tool as far i can see. There would just be more possibilities for those tools, and better user-experience on SBo, and thus in IMHO it would be a great improvement. >> Is that really your proposal for all slackware-maintainers, or for all >> SBo-users? > > As I clearly wrote, it's for anybody who thinks they can design a > solution like "OPTIONAL=". Yes, i didn't read carefully, sorry. Johannes From atelszewski at gmail.com Sat Nov 5 12:14:57 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 13:14:57 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> Message-ID: On 05/11/16 13:00, Willy Sudiarto Raharjo wrote: > I personally don't see real benefit of doing it since everything is > working fine with current README/REQUIRES. I mentioned the real benefit previously, that is easier and faster navigation through the website. > > Second problem is about maintainer's willingness to check EVERY optional > dependencies and make sure it stays to build fine under ALL possible > combinations. Do they have to track every one of them? > We are doing this already, for better or worse. What we mean is to make the data accessible and possible to parse by machines. There are going to be mistakes, as there are now. -- Best regards, Andrzej Telszewski From ts at websafe.pl Sat Nov 5 12:25:22 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sat, 5 Nov 2016 13:25:22 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <270aaed6-3126-be40-0b1e-6a8088674429@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> <270aaed6-3126-be40-0b1e-6a8088674429@gmail.com> Message-ID: On 11/05/2016 01:09 PM, Andrzej Telszewski wrote: > You don't have to actually implement anything other than skipping new > OPTIONAL field in .info. > At some point, if you decided you have the time, you then would go about > it. +1 -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sat Nov 5 12:32:17 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Nov 2016 19:32:17 +0700 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> Message-ID: <17d76108-ae8b-d06e-9c78-cac9af8afbea@slackbuilds.org> > I mentioned the real benefit previously, that is easier and faster > navigation through the website. I personally don't see a real benefit if it's just easier and faster navigation through website. suppose you are suggesting to work on a CI (continuous integration) for SBo, then i (and probably other admins) will be interested since it really helped us to test and make sure all scripts are working fine. > We are doing this already, for better or worse. Have you count active maintainers vs non-active maintainers out there? take a simple example, i486->i586 migration. Out of 5800+ scripts out there, 3800+ are still in i486 after few months since 14.2 branch is released and i tried to stick with weekly public update. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Sat Nov 5 12:35:36 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 Nov 2016 12:35:36 +0000 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: References: <1274b122bb5567806db46167c1845afe@schoepfer.info> Message-ID: Thanks for the reminder, Willy. I have 'su' aliased to 'su -' on my main machine, but not on the VM where I was testing this. So maybe that error message and/or README doesn't need to be changed. I'll leave it up to the maintainer to decide. Dan On Sat, Nov 05, 2016 at 06:52:07PM +0700, Willy Sudiarto Raharjo wrote: > >> In the terminal you build in: > >> source /etc/profile.de/tetex.sh > >> > >> It seems you installed tetex, but didn't login again or reboot. That would > >> have fixed your issue also. > >> > > > > Aha! That's what I was missing. The first time I tried installing vlc, I > > did not have any latex package installed. When I got that error, I > > simply installed tetex and tried again. So I guess it's not really an > > issue, but maybe it would be a good idea for the maintainer to put that > > info you just told me in the README or the error message. > > You should run the script using "su -" instead of "su" > That should solve the problem with tetex PATH > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sat Nov 5 12:37:05 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Nov 2016 19:37:05 +0700 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: References: <1274b122bb5567806db46167c1845afe@schoepfer.info> Message-ID: <3e98a718-e170-cca8-2fc6-18f7ab002d26@slackbuilds.org> > Thanks for the reminder, Willy. I have 'su' aliased to 'su -' on my main > machine, but not on the VM where I was testing this. So maybe that error > message and/or README doesn't need to be changed. I'll leave it up to > the maintainer to decide. It's already mentioned here https://slackbuilds.org/howto/ Note that for many builds, you will need to have a true login shell in order to have a correctly populated environment. Among other things, /usr/share/texmf/bin will not be in your PATH if you simply do "su" -- therefore, you will need to either use "su -l" when switching to root, or source the /etc/profile script after doing "su", or perhaps modifying /root/.bashrc to include necessary PATH elements. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sat Nov 5 12:45:33 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 13:45:33 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <17d76108-ae8b-d06e-9c78-cac9af8afbea@slackbuilds.org> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> <17d76108-ae8b-d06e-9c78-cac9af8afbea@slackbuilds.org> Message-ID: On 05/11/16 13:32, Willy Sudiarto Raharjo wrote: >> I mentioned the real benefit previously, that is easier and faster >> navigation through the website. > > I personally don't see a real benefit if it's just easier and faster > navigation through website. > > suppose you are suggesting to work on a CI (continuous integration) for > SBo, then i (and probably other admins) will be interested since it > really helped us to test and make sure all scripts are working fine. > I've been thinking about CI too. But hey, let's make the life better for both, the users and maintainers, at the same time. > >> We are doing this already, for better or worse. > > Have you count active maintainers vs non-active maintainers out there? > take a simple example, i486->i586 migration. Out of 5800+ scripts out > there, 3800+ are still in i486 after few months since 14.2 branch is > released and i tried to stick with weekly public update. > > This is hard to say, but yes, if time allows, I'm here to help ;-) I have small experience in writing PHP extension in C (on a plus side it is used in real world commercial application). I could also help with some script conversions, if that would help. You can tell what you need and I can tell what I can give. -- Best regards, Andrzej Telszewski From dpross1100 at msn.com Sat Nov 5 12:59:53 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 Nov 2016 12:59:53 +0000 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> <17d76108-ae8b-d06e-9c78-cac9af8afbea@slackbuilds.org> Message-ID: I like David's suggestion of making sure we know exactly what problem is going to be solved by this and how much work is going to be needed before deciding to go ahead and do it (i.e., looking through all the SlackBuilds and keeping track of all the different ways optional dependencies are handled, and then making a decision). If this is too complicated to be included in the automated tools without programming in handling for a ton of possible permutations and edge cases, which I think it might be, and there is not another significant benefit to it, then there's no point in doing in. If, on the other hand, it does make life better for the users and maintainers, then it might be worth it. But that needs to be determined first. Dan On Sat, Nov 05, 2016 at 01:45:33PM +0100, Andrzej Telszewski wrote: > On 05/11/16 13:32, Willy Sudiarto Raharjo wrote: > > > I mentioned the real benefit previously, that is easier and faster > > > navigation through the website. > > > > I personally don't see a real benefit if it's just easier and faster > > navigation through website. > > > > suppose you are suggesting to work on a CI (continuous integration) for > > SBo, then i (and probably other admins) will be interested since it > > really helped us to test and make sure all scripts are working fine. > > > > I've been thinking about CI too. > But hey, let's make the life better for both, the users and maintainers, at > the same time. > > > > > > We are doing this already, for better or worse. > > > > Have you count active maintainers vs non-active maintainers out there? > > take a simple example, i486->i586 migration. Out of 5800+ scripts out > > there, 3800+ are still in i486 after few months since 14.2 branch is > > released and i tried to stick with weekly public update. > > > > > > This is hard to say, but yes, if time allows, I'm here to help ;-) > I have small experience in writing PHP extension in C (on a plus side it is > used in real world commercial application). > > I could also help with some script conversions, if that would help. > You can tell what you need and I can tell what I can give. > > -- > Best regards, > Andrzej Telszewski > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From slackbuilds at schoepfer.info Sat Nov 5 13:14:19 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 05 Nov 2016 14:14:19 +0100 Subject: [Slackbuilds-users] ffmpeg and tetex In-Reply-To: <3e98a718-e170-cca8-2fc6-18f7ab002d26@slackbuilds.org> References: <1274b122bb5567806db46167c1845afe@schoepfer.info> <3e98a718-e170-cca8-2fc6-18f7ab002d26@slackbuilds.org> Message-ID: <39301cdec5b51e46429630da02c04a21@schoepfer.info> On 2016-11-05 13:37, Willy Sudiarto Raharjo wrote: >> Thanks for the reminder, Willy. I have 'su' aliased to 'su -' on my >> main >> machine, but not on the VM where I was testing this. So maybe that >> error >> message and/or README doesn't need to be changed. I'll leave it up to >> the maintainer to decide. > > It's already mentioned here > https://slackbuilds.org/howto/ > > Note that for many builds, you will need to have a true login shell in > order to have a correctly populated environment. Among other things, > /usr/share/texmf/bin will not be in your PATH if you simply do "su" -- > therefore, you will need to either use "su -l" when switching to root, > or source the /etc/profile script after doing "su", or perhaps > modifying > /root/.bashrc to include necessary PATH elements. True, and looking at the mail subject, do not forget that texlive/tetex is not required to build ffmpeg(it was required some versions earlier), documentation is still build without tex. You just need to remove the texi2html-check from the Buildscript, it's of no use by now. Johannes From atelszewski at gmail.com Sat Nov 5 14:24:30 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 15:24:30 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> <17d76108-ae8b-d06e-9c78-cac9af8afbea@slackbuilds.org> Message-ID: On 05/11/16 13:59, Daniel Prosser wrote: > I like David's suggestion of making sure we know exactly what problem is > going to be solved by this and how much work is going to be needed > before deciding to go ahead and do it (i.e., looking through all the > SlackBuilds and keeping track of all the different ways optional > dependencies are handled, and then making a decision). If this is too > complicated to be included in the automated tools without programming in > handling for a ton of possible permutations and edge cases, which I > think it might be, and there is not another significant benefit to it, > then there's no point in doing in. If, on the other hand, it does make > life better for the users and maintainers, then it might be worth it. > But that needs to be determined first. I do agree that it has to be investigated, that is a must. What problems are going to be solved, I already have mentioned. Willy does not agree with me, it is his rightful opinion, just different from mine. I really get frustrated when searching for optional packages. But when it comes to differences in handling optional parameters between different SlackBuilds, then why not force maintainers to do it in a standardized way? We had no problems on forcing using 'find' instead of 'chmod -R', why would this be different? Standardization is good, to the benefit of all. And remember, it does not have to all happen at once. I see no problem with it being an incremental process. The presence of OPTIONAL field in the .info wouldn't disturb the automated tools, but if so, they can be easily fixed. What could disturb them, is standardization of handling of optional parameters, if the change was incompatible. -- Best regards, Andrzej Telszewski From 414N at slacky.it Sat Nov 5 15:17:21 2016 From: 414N at slacky.it (414N) Date: Sat, 5 Nov 2016 16:17:21 +0100 Subject: [Slackbuilds-users] Error building atom package Message-ID: <1bf4d8b0-f737-a235-a8fa-5d76c3b4b952@slacky.it> Hi everyone, it?s from some time that I?m not able anymore to build and upgrade my atom installation to any of the newer versions (I?m currently running v1.9.8). What I get during every build is this: |********************************************************************* * The installation process will download a lot of modules for atom. * ********************************************************************* Node: v6.9.1 Npm: v3.10.8 Installing script dependencies Installing apm npm ERR! Linux 4.4.29 npm ERR! argv "/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/bin/node" "/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/node_modules/.bin/npm" "dedupe" npm ERR! node v4.4.5 npm ERR! npm v3.10.5 npm ERR! path /tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/node_modules/npm/node_modules npm ERR! code EACCES npm ERR! errno -13 npm ERR! syscall access npm ERR! Error: EACCES: permission denied, access '/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/node_modules/npm/node_modules' npm ERR! at Error (native) npm ERR! { [Error: EACCES: permission denied, access '/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/node_modules/npm/node_modules'] npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'access', npm ERR! path: '/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/node_modules/npm/node_modules' } npm ERR! npm ERR! Please try running this command again as root/Administrator. npm ERR! Please include the following file with any support request: npm ERR! /tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/npm-debug.log module.js:327 throw err; ^ Error: Cannot find module 'node-gyp/bin/node-gyp' at Function.Module._resolveFilename (module.js:325:15) at Function.require.resolve (internal/module.js:16:19) at new Install (/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/lib/install.js:53:38) at Object.module.exports.run (/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/lib/apm-cli.js:226:18) at Object. (/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/lib/cli.js:8:7) at Object. (/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/lib/cli.js:12:4) at Module._compile (module.js:409:26) at Object.Module._extensions..js (module.js:416:10) at Module.load (module.js:343:32) at Function.Module._load (module.js:300:12) child_process.js:506 throw err; ^ Error: Command failed: /tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/bin/apm --loglevel=error install at checkExecSyncError (child_process.js:483:13) at Object.execFileSync (child_process.js:503:13) at module.exports (/tmp/SBo/atom-1.11.2/script/lib/install-atom-dependencies.js:19:16) at Object. (/tmp/SBo/atom-1.11.2/script/bootstrap:28:1) at Module._compile (module.js:570:32) at Object.Module._extensions..js (module.js:579:10) at Module.load (module.js:487:32) at tryModuleLoad (module.js:446:12) at Function.Module._load (module.js:438:3) at Module.require (module.js:497:17) | A strange thing I found out is that files inside the |/tmp/SBo/atom-1.11.2/apm/node_modules/atom-package-manager/node_modules/npm/node_modules| directory are owned by my normal user and group, while I?m running the build script in a proper root shell? Anyone has the same issue? ? -- Alan Alberghini SBo clone: GitHub -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From alik at ejik.org Sat Nov 5 15:21:47 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 05 Nov 2016 18:21:47 +0300 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <046ed444ed20fba241b0e5a6483e8db4@schoepfer.info> <17d76108-ae8b-d06e-9c78-cac9af8afbea@slackbuilds.org> Message-ID: <1478359307.1279928.778352145.2538CC6E@webmail.messagingengine.com> > Standardization is good, to the benefit of all. David has shown (convincing to me) that the standard is going to be complicated. Even for human it could be more difficult to decipher than just plain English like now. IMO, since the standard is not obvious, we hardly further the discussion without having a real draft of such standard. Best regards, Alexander From atelszewski at gmail.com Sat Nov 5 17:40:39 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 18:40:39 +0100 Subject: [Slackbuilds-users] Help offer Message-ID: Hi, I can offer some man power. Please contact me by e-mail. I feel most comfortably with C/C++ packages. I can build test in QEMU/slackrepo clean environment. I can go about i486 -> i586 migration and test build, but I'm not limited to it. We can settle something over e-mail. I'm C/C++ programmer too, if that was of help. As I mentioned before, I did a bit of PHP extension writing. I'm also somehow familiar with libarchive, that could be handy to process and/or inspect the submission archive at the time of landing in pending queue. I have some ideas for automated builds of pending submissions, but that is for separate discussion (and I don't know how you admins are handling it now). We all don't have time, so I'm not gonna tell how little of it I have :-^ P.S. Don't feel offended but proposals to change something. Nobody is rude here and most importantly nobody can push you to implement the change. Proposals are what they are, proposals. We all have different needs and wishes, and proposals are about fulfilling those wishes. It probably does not happen here that somebody comes with completely stupid idea/request. I am aware of the fact that if I propose something, it is very likely that I will have to spent my personal time on it. And I am prepared for that. And again, it does not have to all happen at once. Cheers :-) -- Best regards, Andrzej Telszewski From rob0 at slackbuilds.org Sat Nov 5 18:24:10 2016 From: rob0 at slackbuilds.org (Rob McGee) Date: Sat, 5 Nov 2016 13:24:10 -0500 Subject: [Slackbuilds-users] Best place to install the EasyRSA scripts? In-Reply-To: <4fc90ba1-756d-fab5-0d45-7e008150bf62@websafe.pl> References: <30cd6ea3-9c21-5ae9-6e98-0eb9a65ae25f@websafe.pl> <20161105005632.GZ6526@harrier.slackbuilds.org> <4fc90ba1-756d-fab5-0d45-7e008150bf62@websafe.pl> Message-ID: <20161105182410.GA6526@harrier.slackbuilds.org> On Sat, Nov 05, 2016 at 02:43:14AM +0100, Thomas Szteliga wrote: > On 11/05/2016 01:56 AM, Rob McGee wrote: > > At least 3 problems I see with that as it implies: > > 1. that you have your CA on an openvpn server or client; > > 2. that you will be running these scripts as root; > > 3. that your CA is limited to use for openvpn. > > #1 is the big one, because that promotes insecure user practices; > > Slackbuilds.org MUST NOT do that. > > I'm aware. I have a separated isolated VM just for generating > CA's, keys and testing configs for multiple servers/clients. Did you miss my post about this a few days back, in the original thread about easy-rsa? This violates another principle of cryptographic software: that crypto requires a good source of random data (entropy), and a VM has no good source of entropy. If your random data is predictable, your cryptography could be weak and vulnerable to attack. Yes, yes, I know in the real world that such attacks aren't going to happen (a gov't would apply a $5 hammer to your head until you decide to turn over the keys.) But still, why not do it right? > > Admittedly I have never been in the position of having to support > > multiple servers, but I'd still only maintain a single CA for all > > of them in any given organization. If you need to restrict > > access on any given server, use a --client-config-dir and > > --ccd-exclusive (touch a file in the CCD for any permitted > > client's commonName on that server instance.) > > I have individual CA's for each server, even when in a single > organization and of course if clients of a single server > need individual settings ccd's are used. Okay, I still don't see the point in multiple CAs, but that's a choice you can make which isn't "wrong" in some way. [ /usr/share/easy-rsa ] > > Hehe, actually I don't have any strong feelings against this > > suggestion. It's as good as any. > > I think /usr/doc/easy-rsa is way better than > /usr/doc/easy-rsa- /usr/libexec somehow feels really > wrong. I don't think /usr/doc is an appropriate place to put the scripts, and yes, /usr/libexec is wrong also. > CentOS: /usr/share/easy-rsa/ Best idea so far. > Archlinux: /etc/easy-rsa Yuck, not in line with FHS. > FreeBSD: /usr/local/share/easy-rsa Not permitted by Slackbuilds.org policy nor FHS. Note also that FreeBSD != Linux, so they use different standards. > >> and users will have to copy the contents of /usr/share/easyrsa > >> to a writable location like /etc/openvpn/server/server1/easyrsa > > Eeek! How about /home/ca/ ? > > Oh no, really, a user for each CA? ;-) You were the one who brought up the idea of multiple CAs. I seriously doubt very many OpenVPN users have those; if so, it suggests to me that they misunderstood the basic ideas behind X.509 and certificate authorities. That said, for maximum security precautions with multiple CAs, yes, different non-root users make sense. Note that a compromise of a CA's user account means the compromise of that CA. > And just another fun-fact ;-) > > ~~~~ > If you are using Linux, BSD, or a unix-like OS, open a shell and cd > to the easy-rsa subdirectory. If you installed OpenVPN from an RPM > or DEB file, the easy-rsa directory can usually be found in > /usr/share/doc/packages/openvpn or /usr/share/doc/openvpn (it's This is no longer correct since the split of easy-rsa from openvpn. > best to copy this directory to another location such as > /etc/openvpn, before any edits, so that future OpenVPN package This was bad advice even then. The people in OpenVPN project probably know this (at least I think the ones I know do), but they haven't gotten around to fixing old documentation. They're not the only free software project with outdated documentation online. (Another example is Slackware.com.) > upgrades won't overwrite your modifications). If you installed from > a .tar.gz file, the easy-rsa directory will be in the top level > directory of the expanded source tree. > ~~~~ And that's clearly outdated as well. > Again: > > "it's best to copy this directory to another location such as > /etc/openvpn" :-)))) > > > It's from the official howto: > https://openvpn.net/index.php/open-source/documentation/howto.html Wrong when that was written, and all these years later it's still wrong. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From thedoogster at gmail.com Sat Nov 5 18:55:35 2016 From: thedoogster at gmail.com (Doogster) Date: Sat, 5 Nov 2016 11:55:35 -0700 Subject: [Slackbuilds-users] Open offer: love (love2d) SlackBuild maintainership Message-ID: I'm happy to keep maintaining the love (love2d) SlackBuild, but it seems like there are people who are more on top of updates for it than I am. If anyone's interested in taking over maintainership of it, just ask. Also, there's a recent, very excellent love2d games that I'd, uhm, love to recommend: http://bluerevolvergame.com/ I'm not affiliated. I'm just very impressed. From kingbeowulf at gmail.com Sat Nov 5 19:59:53 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 5 Nov 2016 12:59:53 -0700 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> Message-ID: <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com> On 10/24/2016 02:57 PM, Christoph Willing wrote: >>----- >> > Because ffmpeg has so many options, it is a good example of the problem > to decide which to include. Some people want a mean & lean ffmpeg with > minimal options, while others want the lot. Even with a new OPTIONAL > field, which options would be included in it that would please everyone? > Each builder will probably modify to suit themselves. > > Of course everyone already has that option - to modify the .info file > with any additional fields they want. For ffmpeg I add: > ENVOPTS="LAME=yes X264=yes CELT=yes ..." > My build tool finds ENVOPTS and exports each of the variables found, > triggering the desired options already supplied in the ffmpeg.SlackBuild > file. > > However the maintainer can't know what options I want. They could put > all the possible options in a new OPTIONAL field but perhaps I don't > want _all_ of them; just some of them. Then I, the builder, would still > have to make the changes to suit my own needs/desires, so what has been > gained? > > Anyway, whatever the mechanism is used, its up to the various build > tools to actually support it. Maybe one of the public build tools will > introduce something of their own just to see if it catches on. > > chris > Reading through this threads commentary, I find everyone is going in circles. The above is one of the smarter responses. Whether it's ffmpeg, qemu or whatever there are just too many optional choices. Debian et al., Redhat, Gentoo, etc all try to automate the software installation process with mixed results. [ Day1: Gentoo User: "Yo Ed, check out "emerge world"! How cool is that?" Day 2: Me: "Say, is your server still up?" Gentoo: "In a bit. I decided to reinstall from scratch." Me: "What happened?" Gentoo: "Oh, just decided to start over clean." Me: (Sigh). ] 20+ yrs ago I choose Slackware because WE DON"T DO THAT. SBo, has a difficult task: It's one thing to test for all REQUIRED deps so that a package compiles, it's quite another to sift though the various build systems (Documentation? Read the source, Luke.) to find various optional deps. I've run into 1. Autodetected at compile time 2. Autodetected at run time 3. Configured during compile time but not autodetected There can be SCORES of these in various combinations, even after adjusting for a full Slackware installation. Some even have x86_64 vs x86 choices. This is just nuts from an automation standpoint. As Chris states above, not everyone will want the same options. Thus there is no way to keep everyone happy. As a maintainer, I volunteer my time on SBo and LQ to "pay forward" for all those years a sucked for free off the Slackware teat. I also purchase the odd item at the Slackware Store. That is pretty much my total skill set available. I personally use most of the SBo scripts I maintain. I simply do not have the time, the skill, or the hardware to sift and test all OPTIONAL deps. Hell, I don't even work in the Computer software/hardware/MIS/IT industry. As far as I know, no one involved in SBo gets paid. So, I vote NO on additional bloat added to SBo. Additional functions should have a damn good reason to exist, simple to implement, easy to maintain, and transparent. For those who disagree I think I should devote my time to making their lives easier, I suggest you fork the repo and do whatever the hell you want. Just stop nagging me for weird-ass option most people don't use. I have yet to nag an SBo maintainer of a scrip I use to add optional support that may only be useful to me. Now that said, I will be adding BRIDGE_HELPER_SETUID to qemu, for example, because 1. I didn't now about it 2. it's useful to the entire user base I am not opposed to having the community emailing me with useful feature additions or true bug reports. I just thinks it is up to the individual user to add their own fringe-case options. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sat Nov 5 20:20:08 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 21:20:08 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com> Message-ID: On 05/11/16 20:59, King Beowulf wrote: > to sift and test all OPTIONAL > deps. No, no, no. You're confusing what OPTIONAL is about. It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE README* into the .info file, so *MACHINES* can understand it. You are not going to test it more than you do already. Let's finally understand that. -- Best regards, Andrzej Telszewski From erik at slackbuilds.org Sat Nov 5 20:44:58 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 5 Nov 2016 15:44:58 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> Message-ID: <20161105154458.7701f2fd@shaggy.doo> On Fri, 4 Nov 2016 18:25:32 +0000 David Spencer wrote: > example) OPTIONAL="libass:ASS=yes|no libbluray:BLURAY=yes|no". Who's > going to find them all? Who's going to fix them all? Who's going to > change all the users' queue files and build scripts?) What I also don't see much (any?) mention of is what the admins will have to refactor.. the website, php, database, internal tools we use for submission/approval process (there are many) .. things are more complicated behind the scenes than people realize. It's a messy and time-consuming job. Adding an OPTIONAL field to the info file isn't something that, if only someone would do it, magically "just works". Forgetting the above (clickable links on the website, etc.) it's still not as simple as duplicating some of the README into the info file. The README file also contains maintainer commentary on what those optional deps provide, why someone may or may not want them, etc. Sometimes, those deps don't even exist on SBo, require system changes outside package management, increase compile time providing no benefit, and so on. It's not a good idea to present users with a simple list of optional deps without context. People still need to read the README. I get that what people want is a feature request, and not a solution to a problem. The issue I have is that this feature boils down to "I'd like to skip reading the README files please", and that's not a request that should be entertained, in my opinion. I'm not necessarily against an OPTIONAL field, since I quite like the way AUR works, for example. It's just really difficult to implement here. Theory crafting a grand syntax, and other ideas, are certainly fun exercises, but are very far removed from the real problems this additional field presents if implemented. > IMO it's best to read all ~5800 README files before thinking about a > solution. I've done it. It's quite easy to spot the interesting ones > if you step through them quickly. What my own custom build tool does is display the README and prompt "Continue building Y/n?" - As a founder of SBo, I'm about as seasoned as it gets when it comes to using the repo, and I still find this to be an invaluable step. If only the 3rd party tools made available to the public did the same... -- Erik From Jim.Diamond at acadiau.ca Sat Nov 5 20:56:17 2016 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 5 Nov 2016 17:56:17 -0300 Subject: [Slackbuilds-users] opera 41.0.2353.46 Message-ID: <20161105205617.GA8577@jdiamond-nb.acadiau.ca> I just installed this package and got a /usr/bin/opera with contents #!/bin/bash # Allow users to override command-line options # Based on Gentoo's chromium package (and by extension, Debian's) if [[ -f /etc/opera/default ]]; then . /etc/opera/default fi # Prefer user defined CHROMIUM_USER_FLAGS (from env) over system # default CHROMIUM_FLAGS (from /etc/chromium/default) OPERA_FLAGS=${OPERA_USER_FLAGS:-$OPERA_FLAGS} if [ "$ARCH" = "x86_64" ]; then exec /usr/lib64/opera/opera $OPERA_FLAGS "$@" else exec /usr/lib/opera/opera $OPERA_FLAGS "$@" fi I am running Slackware64, but I don't have variable ARCH set, so it tries to run /usr/lib/opera/opera, which isn't there. Is this package correct in assuming I am supposed to have $ARCH ? (This would be news to me.) Or is there a bug in the package and/or its installation procedure for Slackware? Cheers. Jim From atelszewski at gmail.com Sat Nov 5 20:59:11 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 21:59:11 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105154458.7701f2fd@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> Message-ID: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> On 05/11/16 21:44, Erik Hanson wrote: > It's not a good idea to present users with a simple list of > optional deps without context. People still need to read the README. I for one would be pleased by the tool that presents the optional packages, allowing me to just select those I want. You kinda have point with the context of the deps, but we're not here to babysit people. One shall README, period. -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sat Nov 5 21:35:28 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 22:35:28 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105154458.7701f2fd@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> Message-ID: <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> On 05/11/16 21:44, Erik Hanson wrote: > What I also don't see much (any?) mention of is what the admins will > have to refactor.. the website, php, database, internal tools we use > for submission/approval process (there are many) .. things are more > complicated behind the scenes than people realize. It's a messy and > time-consuming job. Adding an OPTIONAL field to the info file isn't > something that, if only someone would do it, magically "just works". I don't know behind the scenes, for that reason I don't see SlackBuilds.org as complex software project. I *do not imply* that it is easy from the maintenance point of view. -- Best regards, Andrzej Telszewski From dpross1100 at msn.com Sat Nov 5 22:06:37 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 5 Nov 2016 22:06:37 +0000 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> Message-ID: Say, for example, that someone was installing ffmpeg, which was brought up as an example earlier. It needs the optional dependencies to be explicitly enabled when running the script. Let's say average user Joe is using an automated tool that says "Hey, these are optional dependencies. Which ones do you want to install?" He could go ahead and choose a bunch of them, but they wouldn't be enabled when ffmpeg was subsequently built. Confusion would ensue. Even if the installer said to look at the README first, he'd have to go and figure out what each optional dependency does, how to enable it, and manually run the ffmpeg SlackBuild script anyway. So what was the point of the automation? In my opinion, it would add a lot of work and confusion with little benefit. -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sat Nov 5 22:15:04 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 5 Nov 2016 23:15:04 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: Message-ID: On 05/11/16 23:06, Daniel Prosser wrote: > Say, for example, that someone was installing ffmpeg, which was brought > up as an example earlier. It needs the optional dependencies to be > explicitly enabled when running the script. Let's say average user Joe > is using an automated tool that says "Hey, these are optional > dependencies. Which ones do you want to install?" He could go ahead and > choose a bunch of them, but they wouldn't be enabled when ffmpeg was > subsequently built. Confusion would ensue. Even if the installer said to > look at the README first, he'd have to go and figure out what each > optional dependency does, how to enable it, and manually run the ffmpeg > SlackBuild script anyway. So what was the point of the automation? In my > opinion, it would add a lot of work and confusion with little benefit. You got the point. OPTIONAL field is going to be useless or confusing at best, if the maintainers won't be willing to change their SlackBuilds. -- Best regards, Andrzej Telszewski From chris.willing at iinet.net.au Sat Nov 5 22:56:36 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 6 Nov 2016 08:56:36 +1000 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: Message-ID: On 06/11/16 08:15, Andrzej Telszewski wrote: > On 05/11/16 23:06, Daniel Prosser wrote: >> Say, for example, that someone was installing ffmpeg, which was brought >> up as an example earlier. It needs the optional dependencies to be >> explicitly enabled when running the script. Let's say average user Joe >> is using an automated tool that says "Hey, these are optional >> dependencies. Which ones do you want to install?" He could go ahead and >> choose a bunch of them, but they wouldn't be enabled when ffmpeg was >> subsequently built. Confusion would ensue. Even if the installer said to >> look at the README first, he'd have to go and figure out what each >> optional dependency does, how to enable it, and manually run the ffmpeg >> SlackBuild script anyway. So what was the point of the automation? In my >> opinion, it would add a lot of work and confusion with little benefit. > > You got the point. > > OPTIONAL field is going to be useless or confusing at best, if the > maintainers won't be willing to change their SlackBuilds. > We could go on like this for a long time. I think now would be a good time to provide a full example of what changes would be required for a particular and related SlackBuilds. Could you find a SlackBuild that has a number of optional requirements, one of which should be ffmpeg (itself with some options to be enabled); then show how you envisage the respective .info & README* files should be modified. A full example like this would give a clearer indication of what changes would be needed by individual maintainers (although for now glossing over backend changes that would also be required). chris From atelszewski at gmail.com Sat Nov 5 23:18:54 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 00:18:54 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: Message-ID: <35fea088-c59c-90b1-450b-c4b3961d4c5d@gmail.com> On 05/11/16 23:56, Christoph Willing wrote: >> > We could go on like this for a long time. > > I think now would be a good time to provide a full example of what > changes would be required for a particular and related SlackBuilds. > Could you find a SlackBuild that has a number of optional requirements, > one of which should be ffmpeg (itself with some options to be enabled); > then show how you envisage the respective .info & README* files should > be modified. A full example like this would give a clearer indication of > what changes would be needed by individual maintainers (although for now > glossing over backend changes that would also be required). > > chris I think you are 99%* correct. This should mute the thread for quite some time ;-) *1% = I don't think it makes sense to talk about backend at this stage. Let's first define how it should look from the maintainers and users point of view. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sun Nov 6 00:07:52 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 6 Nov 2016 07:07:52 +0700 Subject: [Slackbuilds-users] opera 41.0.2353.46 In-Reply-To: <20161105205617.GA8577@jdiamond-nb.acadiau.ca> References: <20161105205617.GA8577@jdiamond-nb.acadiau.ca> Message-ID: > I just installed this package and got a /usr/bin/opera with contents > > #!/bin/bash > > # Allow users to override command-line options > # Based on Gentoo's chromium package (and by extension, Debian's) > > if [[ -f /etc/opera/default ]]; then > . /etc/opera/default > fi > > # Prefer user defined CHROMIUM_USER_FLAGS (from env) over system > # default CHROMIUM_FLAGS (from /etc/chromium/default) > > OPERA_FLAGS=${OPERA_USER_FLAGS:-$OPERA_FLAGS} > > if [ "$ARCH" = "x86_64" ]; then > exec /usr/lib64/opera/opera $OPERA_FLAGS "$@" > else > exec /usr/lib/opera/opera $OPERA_FLAGS "$@" > fi > > > I am running Slackware64, but I don't have variable ARCH set, so it > tries to run /usr/lib/opera/opera, which isn't there. > > > Is this package correct in assuming I am supposed to have $ARCH ? > (This would be news to me.) > > Or is there a bug in the package and/or its installation procedure for > Slackware? Hi Jim It seems the maintainer only test this on x86 machines, so he always gets to the "else" part since ARCH is not set. I have the fix pushed to my branch. Can you confirm to work by adding the changes to /usr/bin/opera ? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From edps.mundognu at gmail.com Sun Nov 6 01:43:30 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Sat, 05 Nov 2016 23:43:30 -0200 Subject: [Slackbuilds-users] opera Message-ID: Hi all, about errors on x86_64, the packaging may be made without the use of files (opera and default), only using the contents of .debs. Just discard the files (opera and default) and remove on the opera.SlackBuild the following lines: mkdir -p $PKG/etc/$PRGNAM/ install -Dm644 $CWD/default $PKG/etc/$PRGNAM/default rm $PKG/usr/bin/$PRGNAM install -Dm755 $CWD/$PRGNAM $PKG/usr/bin/$PRGNAM * This affects opera-developer too, see the last log: https://slackbuilds.org/cgit/slackbuilds/commit/?h=willysr&id=aaf5d009d8dbfe4b8edca7332088b1ffb4286204 So... i will send a new update for each of them. Thank's for your attention and sorry for inconvenience. Edinaldo. From erik at slackbuilds.org Sun Nov 6 02:33:12 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 5 Nov 2016 21:33:12 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> Message-ID: <20161105213312.2b972f7e@shaggy.doo> On Sat, 5 Nov 2016 21:59:11 +0100 Andrzej Telszewski wrote: > On 05/11/16 21:44, Erik Hanson wrote: > > It's not a good idea to present users with a simple list of > > optional deps without context. People still need to read the > > README. > > I for one would be pleased by the tool that presents the optional > packages, allowing me to just select those I want. I'm not sure if this statement is for or against what I said, such is the nature of text-based communication. All I can add is that I believe it would be very important for said tool to provide that context. Can we expect all 3rd party tools to adopt a policy to inform their users in some way? I don't think so. Why is that important? Well, the tools that don't inform the user open things up to people just hitting "Yes" on all the optional deps. I mean, why wouldn't you want the most functionality built in to your packages? I can only envision the bug reports we would get, the same way the vast majority of bug reports currently come in with sbopkg text at the end. We don't endorse or support sbopkg, yet there it is. Next up, bug reports of 'fails to compile' or 'package broken' or 'trashed my system', none of which we can really deal with. All the result of some tool saying 'tick the boxes of what you want' - all context stripped away. People still need to read the README. > You kinda have point with the context of the deps, but we're not here > to babysit people. One shall README, period. And there is the crux of the entire matter. Currently, we expect people to read the README. A machine-readable field of optional deps means people have even less reason to read the README. Nothing good comes of this. A few power users might be okay, but the other 99.9% of people: fucked. Our goal has always been a repo of scripts that reliably create valid packages. OPTIONAL provides too many ways for that to go wrong. Read the README and you're golden. -- Erik From erik at slackbuilds.org Sun Nov 6 02:51:00 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 5 Nov 2016 21:51:00 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> Message-ID: <20161105215100.1df69d2e@shaggy.doo> On Sat, 5 Nov 2016 22:06:37 +0000 Daniel Prosser wrote: > He could go ahead and choose a bunch of them, but they wouldn't be > enabled when ffmpeg was subsequently built. Confusion would ensue. They would be enabled. The argument being made is that the OPTIONAL field would provide yes/no answers, and the 3rd party tool would pass those on to the SlackBuild script. The goal is then that no one would ever have to look at the README file, they could just tick some boxes and be on their way. I see obvious issues with this and that's the point I'm trying to get across. -- Erik From atelszewski at gmail.com Sun Nov 6 02:49:51 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 03:49:51 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105213312.2b972f7e@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> <20161105213312.2b972f7e@shaggy.doo> Message-ID: <770bb5a5-8792-b6b5-dd01-c05c97094ec0@gmail.com> On 06/11/16 03:33, Erik Hanson wrote: >> You kinda have point with the context of the deps, but we're not here >> > to babysit people. One shall README, period. > And there is the crux of the entire matter. Currently, we expect people > to read the README. A machine-readable field of optional deps means > people have even less reason to read the README. Nothing good comes of > this. A few power users might be okay, but the other 99.9% of people: > fucked. Our goal has always been a repo of scripts that reliably create > valid packages. OPTIONAL provides too many ways for that to go wrong. > > Read the README and you're golden. Well, I don't know. This feels kinda bad. Like babysitting. It's Linux in the end, you are expected to know more less what you're doing. There are many more ways to screw up your system. On the other hand, the last thing I would like to see is mailing list polluted with problems caused by OPTIONAL. Is this a real threat? -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sun Nov 6 02:53:36 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 03:53:36 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105215100.1df69d2e@shaggy.doo> References: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> <20161105215100.1df69d2e@shaggy.doo> Message-ID: On 06/11/16 03:51, Erik Hanson wrote: > The goal is then that no one would > ever have to look at the README file, they could just tick some boxes > and be on their way. No, that's not the point. At least not mine. The point is to facilitate the process. And you can't argue that for _educated_ user it is going to be. But as you mentioned before, we might have problem with _education_ among the users. -- Best regards, Andrzej Telszewski From erik at slackbuilds.org Sun Nov 6 03:39:30 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 5 Nov 2016 22:39:30 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <770bb5a5-8792-b6b5-dd01-c05c97094ec0@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> <20161105213312.2b972f7e@shaggy.doo> <770bb5a5-8792-b6b5-dd01-c05c97094ec0@gmail.com> Message-ID: <20161105223930.42c628c7@shaggy.doo> On Sun, 6 Nov 2016 03:49:51 +0100 Andrzej Telszewski wrote: > On 06/11/16 03:33, Erik Hanson wrote: > >> You kinda have point with the context of the deps, but we're not > >> here > >> > to babysit people. One shall README, period. > > And there is the crux of the entire matter. Currently, we expect > > people to read the README. A machine-readable field of optional > > deps means people have even less reason to read the README. Nothing > > good comes of this. A few power users might be okay, but the other > > 99.9% of people: fucked. Our goal has always been a repo of scripts > > that reliably create valid packages. OPTIONAL provides too many > > ways for that to go wrong. > > > > Read the README and you're golden. > > Well, I don't know. This feels kinda bad. Like babysitting. > It's Linux in the end, you are expected to know more less what you're > doing. There are many more ways to screw up your system. We should just delete the HOWTO and FAQ pages, I guess. Wouldn't want to babysit. I'm not sure how you get from "please read the README files, they contain vital information" to "we need to hold your hand". The only argument that I'm making is that demonstrably important information can be contained in the README file, and that we shouldn't give anyone a reason to bypass that information. It's not babysitting, it's not hand-holding, it's literally saying there is information here, it's important, and we CANNOT convey it to you in an OPTIONAL="" field. Sorry, but you have to do some reading. Please, I beg of you, tell me how reading up on things and gaining some understanding of how they work is not the Slackware way. > On the other hand, the last thing I would like to see is mailing list > polluted with problems caused by OPTIONAL. > Is this a real threat? Yes. It is. As I said, a lot of "doesn't build" reports come in with sbopkg text at the bottom. It's just a fact. It might not be relevant that they are using sbopkg, but is indicative of what people are doing. They're using an automated tool and can't even discern the difference between the compiler output and the sbopkg output. Sometimes, we ONLY get the sbopkg output! That only gets worse when 3rd party tools present a list of optional deps to users, without any rhyme or reason, and they just pick "Yes" and things break. We're a smart lot, and can probably deal with it, I don't doubt that. But should we allow it? That problem doesn't exist if we continue to tell people: Hey, read the README. That's literally why it's there. -- Erik From erik at slackbuilds.org Sun Nov 6 04:26:08 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sat, 5 Nov 2016 23:26:08 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> Message-ID: <20161105232608.65e14371@shaggy.doo> On Sat, 5 Nov 2016 22:35:28 +0100 Andrzej Telszewski wrote: > On 05/11/16 21:44, Erik Hanson wrote: > > What I also don't see much (any?) mention of is what the admins will > > have to refactor.. the website, php, database, internal tools we use > > for submission/approval process (there are many) .. things are more > > complicated behind the scenes than people realize. It's a messy and > > time-consuming job. Adding an OPTIONAL field to the info file isn't > > something that, if only someone would do it, magically "just > > works". > > I don't know behind the scenes, for that reason I don't see > SlackBuilds.org as complex software project. It is a complex software project. Everything we do was built from scratch, accommodating a custom submission system, a database, eventually git integration, and so on. > I *do not imply* that it is easy from the maintenance point of view. Currently, the active admins go above and beyond anything I would have ever expected. I'm incredibly proud of the people we have brought on board over the years. My heart swells when I think about how this project continues to exist 10+ years later, and the level of quality we maintain. Another aspect of this, is that I expect they would feel obligated to check everything in the OPTIONAL field, along side all the extra work they already do. Even if I were to explicitly say "don't bother with the OPTIONAL field" I know they would check it. They're just really good people that way, focused on the quality of our repository. Regardless of what I say, they're going to feel burdened by it. None of us want junk in the repo, or broken OPTIONAL lines. This is just a reality, and I'm going to fight against more work for these volunteer workers that put so much passion into this project. They have families and lives and I care for them deeply. There are much more pressing issues, our current server is on it's last legs, there's an "amber light of death", dmesg is filled with garbage, and I don't expect it to survive a reboot. Up 962 days as of this writing. We'll be fine for the foreseeable future, but something has to be done. We're not going down, it's not doom and gloom, I'll be sure of that. This is all just for reference as to why I'm really opposed to big changes right now. Or rather, why I'm able to squint, give a keen eye, and say "we really don't need this". -- Erik From rworkman at slackbuilds.org Sun Nov 6 05:03:58 2016 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 6 Nov 2016 00:03:58 -0500 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105232608.65e14371@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> <20161105232608.65e14371@shaggy.doo> Message-ID: <20161106000358.2810e6d9@home.rlworkman.net> On Sat, 5 Nov 2016 23:26:08 -0500 Erik Hanson wrote: > It is a complex software project. Everything we do was built from > scratch, accommodating a custom submission system, a database, > eventually git integration, and so on. > > > I *do not imply* that it is easy from the maintenance point of > > view. > > Currently, the active admins go above and beyond anything I would have > ever expected. I'm incredibly proud of the people we have brought on > board over the years. My heart swells when I think about how this > project continues to exist 10+ years later, and the level of quality > we maintain. > > Another aspect of this, is that I expect they would feel obligated to > check everything in the OPTIONAL field, along side all the extra work > they already do. Even if I were to explicitly say "don't bother with > the OPTIONAL field" I know they would check it. They're just really > good people that way, focused on the quality of our repository. > Regardless of what I say, they're going to feel burdened by it. None > of us want junk in the repo, or broken OPTIONAL lines. > > This is just a reality, and I'm going to fight against more work for > these volunteer workers that put so much passion into this project. > They have families and lives and I care for them deeply. > > There are much more pressing issues, our current server is on it's > last legs, there's an "amber light of death", dmesg is filled with > garbage, and I don't expect it to survive a reboot. Up 962 days as of > this writing. We'll be fine for the foreseeable future, but something > has to be done. We're not going down, it's not doom and gloom, I'll > be sure of that. This is all just for reference as to why I'm really > opposed to big changes right now. Or rather, why I'm able to squint, > give a keen eye, and say "we really don't need this". Everything said above is echoed here. -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 slackbuilds at schoepfer.info Sun Nov 6 07:05:01 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 06 Nov 2016 08:05:01 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105232608.65e14371@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> <20161105232608.65e14371@shaggy.doo> Message-ID: <38e9bba28b6cf2f126f04ddf3c93c834@schoepfer.info> > Even if I were to explicitly say "don't bother with > the OPTIONAL field" I know they would check it. They're just really > good people that way, focused on the quality of our repository. > Regardless of what I say, they're going to feel burdened by it. None of > us want junk in the repo, or broken OPTIONAL lines. > This is just a reality, and I'm going to fight against more work for > these volunteer workers that put so much passion into this project. > They have families and lives and I care for them deeply. So, even if you would like to change something general like the OPTION-field on SBo, it will hardly happen because of the workload? This is not meant offending, really, i just want to get the point. If nothing gonna be changed now, it's fair to say that, to not make the OPTIONAL-discussion a fight against windmills. If it's all about manpower, something should be done about that. Maybe the community can get more ability to contribute in some ways, beside providing SlackBuilds. Johannes From atelszewski at gmail.com Sun Nov 6 10:47:59 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 11:47:59 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105223930.42c628c7@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com> <20161105213312.2b972f7e@shaggy.doo> <770bb5a5-8792-b6b5-dd01-c05c97094ec0@gmail.com> <20161105223930.42c628c7@shaggy.doo> Message-ID: <9750e619-0241-f902-18a3-4904b630d352@gmail.com> On 06/11/16 04:39, Erik Hanson wrote: >> On 06/11/16 03:33, Erik Hanson wrote: >>>> > >> You kinda have point with the context of the deps, but we're not >>>> > >> here >>>>> > >> > to babysit people. One shall README, period. >>> > > And there is the crux of the entire matter. Currently, we expect >>> > > people to read the README. A machine-readable field of optional >>> > > deps means people have even less reason to read the README. Nothing >>> > > good comes of this. A few power users might be okay, but the other >>> > > 99.9% of people: fucked. Our goal has always been a repo of scripts >>> > > that reliably create valid packages. OPTIONAL provides too many >>> > > ways for that to go wrong. >>> > > >>> > > Read the README and you're golden. >> > >> > Well, I don't know. This feels kinda bad. Like babysitting. >> > It's Linux in the end, you are expected to know more less what you're >> > doing. There are many more ways to screw up your system. > We should just delete the HOWTO and FAQ pages, I guess. Wouldn't want > to babysit. > > I'm not sure how you get from "please read the README files, they > contain vital information" to "we need to hold your hand". The only > argument that I'm making is that demonstrably important information > can be contained in the README file, and that we shouldn't give anyone > a reason to bypass that information. It's not babysitting, it's not > hand-holding, it's literally saying there is information here, it's > important, and we CANNOT convey it to you in an OPTIONAL="" field. > Sorry, but you have to do some reading. Please, I beg of you, tell me > how reading up on things and gaining some understanding of how they > work is not the Slackware way. > I'm sorry for not being explicit. If you look at my messages, you'll notice that I do encourage to read READMEs. What I meant by babysitting was that you tell people to read README, but they don't do it anyway. -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sun Nov 6 10:52:06 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 11:52:06 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105232608.65e14371@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> <20161105232608.65e14371@shaggy.doo> Message-ID: <16fe2719-de07-c19f-bd8f-63666327b065@gmail.com> On 06/11/16 05:26, Erik Hanson wrote: > On Sat, 5 Nov 2016 22:35:28 +0100 > Andrzej Telszewski wrote: > >> On 05/11/16 21:44, Erik Hanson wrote: >>> What I also don't see much (any?) mention of is what the admins will >>> have to refactor.. the website, php, database, internal tools we use >>> for submission/approval process (there are many) .. things are more >>> complicated behind the scenes than people realize. It's a messy and >>> time-consuming job. Adding an OPTIONAL field to the info file isn't >>> something that, if only someone would do it, magically "just >>> works". >> >> I don't know behind the scenes, for that reason I don't see >> SlackBuilds.org as complex software project. > > It is a complex software project. Everything we do was built from > scratch, accommodating a custom submission system, a database, > eventually git integration, and so on. > You haven't convinced me ;-) I still don't see it as complex code. -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sun Nov 6 11:01:02 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 12:01:02 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161105232608.65e14371@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> <20161105232608.65e14371@shaggy.doo> Message-ID: On 06/11/16 05:26, Erik Hanson wrote: > Currently, the active admins go above and beyond anything I would have > ever expected. I'm incredibly proud of the people we have brought on > board over the years. My heart swells when I think about how this > project continues to exist 10+ years later, and the level of quality we > maintain. > You can be sure that many of us appreciate the work. We all remember how it was before SlackBuilds.org. > Another aspect of this, is that I expect they would feel obligated to > check everything in the OPTIONAL field, along side all the extra work > they already do. Even if I were to explicitly say "don't bother with > the OPTIONAL field" I know they would check it. They're just really > good people that way, focused on the quality of our repository. > Regardless of what I say, they're going to feel burdened by it. None of > us want junk in the repo, or broken OPTIONAL lines. > I understand what you want to say. I too have to be very careful to limit the time I spend on the code. > There are much more pressing issues, our current server is on it's last > legs, there's an "amber light of death", dmesg is filled with garbage, > and I don't expect it to survive a reboot. Up 962 days as of this > writing. We'll be fine for the foreseeable future, but something has to > be done. We're not going down, it's not doom and gloom, I'll be sure of > that. This is all just for reference as to why I'm really opposed to > big changes right now. Or rather, why I'm able to squint, give a keen > eye, and say "we really don't need this". I've already offered my help, feel obliged to contact me. And ask the community to buy a new server, we all depend on the service. -- Best regards, Andrzej Telszewski From s.arcus at open-t.co.uk Sun Nov 6 11:41:31 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 6 Nov 2016 11:41:31 +0000 Subject: [Slackbuilds-users] Best place to install the EasyRSA scripts? In-Reply-To: <30cd6ea3-9c21-5ae9-6e98-0eb9a65ae25f@websafe.pl> References: <30cd6ea3-9c21-5ae9-6e98-0eb9a65ae25f@websafe.pl> Message-ID: On 04/11/16 22:23, Thomas Szteliga wrote: > On 11/04/2016 12:02 PM, Sebastian Arcus wrote: >> I am making the SBo scripts for EasyRSA, and I need to decide where they >> will be installed. Before they were removed from Slackware - when they >> were part of Openvpn, I think they used to go under >> /usr/share/doc/openvpn. However, it seems a bit strange to install a >> package in the directory of another package. Maybe >> /usr/share/doc/easyrsa instead? However, they are sample scripts - not >> really documentation. According to Linux filesystem standards, would >> there be a better place? Maybe /usr/share directly, or /us/lib or >> something? > > > It was very handy to have them in /etc/openvpn/... > > EasyRSA scripts will create keys in the `keys` subdir, > so /usr/share and /usr/doc are probably not the best location > without patching KEY_DIR in easyrsa/*/vars to point > to a more reasonable location > > export KEY_DIR="$EASY_RSA/keys" > > But this still should not be an absolute path, > because when you're running multiple openvpn servers > you would normally have something like: > > /etc/openvpn/server/server1/easyrsa/*/keys > /etc/openvpn/server/server2/easyrsa/*/keys > /etc/openvpn/server/server3/easyrsa/*/keys > > and a patched KEY_DIR would place all keys by default > in one directory. That's not what you want (with multiple servers). > > > So after rethinking this my suggestion is: > > > /usr/share/easyrsa without patching KEY_DIR (keys placed in subdir) Thanks everybody. /usr/share/easyrsa is actually the place I settled in my mind after my initial post - it seems the most reasonable path. I will include some comments in the README as to their location, and they can be copied somewhere else when they are going to be used - if needed. From baildon.research at googlemail.com Sun Nov 6 11:47:55 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 6 Nov 2016 11:47:55 +0000 Subject: [Slackbuilds-users] Help offer In-Reply-To: References: Message-ID: > I can offer some man power. > Please contact me by e-mail. > [...] > > I have some ideas for automated builds of pending submissions, but that is > for separate discussion (and I don't know how you admins are handling it > now). Awesome! I'm sending this to the list because it needs to be sanity checked by everybody else :) As far as I know several people have been thinking independently about automated testing, continuous integration, etc I haven't discussed this with anybody until now, but maybe buildbot could be useful to us. Unless I've made a mistake reading the buildbot docs, it would allow people to volunteer their own systems as build hosts. There are a couple of things we would need to worry about - clean build environment, authentication - but the idea would seem to fit a project like SlackBuilds.org that tries to exist with minimum infrastructure of our own. So the outline idea would be - a submission arrives - our bot checks if it's a simple update, and how many packages depend on it -- including optional deps ;) - if it's a simple update, and the total expected build time (including depending packages) is less than a threshold, throw all those builds and rebuilds at the automatic build queue (I already have a database of build times) - if possible, do builds with multiple build tools (sbopkg sbotools slackrepo) because diverse tests catch more problems - do some automated tests on the final package (e.g. Heinz's lintpkg) - if the automatic builds fail, the submitter (maintainer) can see what happened and resubmit - otherwise flag it for manual testing - final approval always a human decision I've got a draft SlackBuild for buildbot-0.9.1, but since 0.9 it's one of those packages that need to download huge quantities of npm stuff at build time :( Anyway I'd love to make some progress on this today, but I have a wedding to go to -- not mine :) Thanks! -D. From atelszewski at gmail.com Sun Nov 6 12:07:44 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 13:07:44 +0100 Subject: [Slackbuilds-users] Help offer In-Reply-To: References: Message-ID: <8b12bf2f-84a9-d0b9-d687-82179d485d99@gmail.com> On 06/11/16 12:47, David Spencer wrote: >> I have some ideas for automated builds of pending submissions, but that is >> > for separate discussion (and I don't know how you admins are handling it >> > now). > Awesome! > > I'm sending this to the list because it needs to be sanity checked by > everybody else :) > > As far as I know several people have been thinking independently about > automated testing, continuous integration, etc > > I haven't discussed this with anybody until now, but maybe buildbot > could be useful to us. Unless I've made a mistake reading the buildbot > docs, it would allow people to volunteer their own systems as build > hosts. There are a couple of things we would need to worry about - > clean build environment, authentication - but the idea would seem to > fit a project like SlackBuilds.org that tries to exist with minimum > infrastructure of our own. > > So the outline idea would be > - a submission arrives > - our bot checks if it's a simple update, and how many packages > depend on it -- including optional deps ;) > - if it's a simple update, and the total expected build time > (including depending packages) is less than a threshold, throw all > those builds and rebuilds at the automatic build queue (I already have > a database of build times) > - if possible, do builds with multiple build tools (sbopkg sbotools > slackrepo) because diverse tests catch more problems > - do some automated tests on the final package (e.g. Heinz's lintpkg) > - if the automatic builds fail, the submitter (maintainer) can see > what happened and resubmit > - otherwise flag it for manual testing > - final approval always a human decision > > I've got a draft SlackBuild for buildbot-0.9.1, but since 0.9 it's one > of those packages that need to download huge quantities of npm stuff > at build time :( > > Anyway I'd love to make some progress on this today, but I have a > wedding to go to -- not mine :) > > Thanks! > -D. You have outlined more than less what I've been thinking of ;-) But I wonder if there could be a case where the update is not checked by human at all. Assume it's a version bump. Then you only make sure that the only part changed in the download link is version string. The check for version can be very strict, e.g. it has to change from 0.1 to 0.2 so it won't change from 0.1 to 0.$(screw up the system). When it comes to automated build systems, there is also https://jenkins.io/ But I've been thinking about rolling our own too. -- Best regards, Andrzej Telszewski From erik at slackbuilds.org Sun Nov 6 12:31:13 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 6 Nov 2016 06:31:13 -0600 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <38e9bba28b6cf2f126f04ddf3c93c834@schoepfer.info> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> <20161105232608.65e14371@shaggy.doo> <38e9bba28b6cf2f126f04ddf3c93c834@schoepfer.info> Message-ID: <20161106063113.263d9bcf@shaggy.doo> On Sun, 06 Nov 2016 08:05:01 +0100 Franzen wrote: > > Even if I were to explicitly say "don't bother with > > the OPTIONAL field" I know they would check it. They're just really > > good people that way, focused on the quality of our repository. > > Regardless of what I say, they're going to feel burdened by it. > > None of us want junk in the repo, or broken OPTIONAL lines. > > This is just a reality, and I'm going to fight against more work for > > these volunteer workers that put so much passion into this project. > > They have families and lives and I care for them deeply. > > So, even if you would like to change something general like the > OPTION-field > on SBo, it will hardly happen because of the workload? > This is not meant offending, really, i just want to get the point. > > If nothing gonna be changed now, it's fair to say that, to not make > the OPTIONAL-discussion a fight against windmills. No. Discussions are fine, we've made changes based on public discourse in the past. What appears before us is a handful of people really want to write some tool that plows through optional deps automatically. They don't want to read the README files, or maybe they don't need to, but I feel it's a bad idea to let EVERYBODY off the hook when it comes to the READMEs. I'm just one admin who decided to chime in with my thoughts on the issue. I'm in no way the sole arbiter of all things SBo. If I see that any number of admins view this issue differently, I'm happy to take their considerations and concede. > If it's all about manpower, something should be done about that. > Maybe the community can get more ability to contribute in some ways, > beside providing SlackBuilds. This particular issue is very much not just about manpower. -- Erik From andreas.guldstrand at gmail.com Sun Nov 6 13:40:44 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Sun, 6 Nov 2016 14:40:44 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: <20161106063113.263d9bcf@shaggy.doo> References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> <20161105232608.65e14371@shaggy.doo> <38e9bba28b6cf2f126f04ddf3c93c834@schoepfer.info> <20161106063113.263d9bcf@shaggy.doo> Message-ID: On 6 November 2016 at 13:31, Erik Hanson wrote: > No. Discussions are fine, we've made changes based on public > discourse in the past. What appears before us is a handful of people > really want to write some tool that plows through optional deps > automatically. They don't want to read the README files, or maybe > they don't need to, but I feel it's a bad idea to let EVERYBODY off > the hook when it comes to the READMEs. I'm sorry, but there are only two tools where anyone has mentioned support for this field in this thread (unless I missed something), and those are sbotools and slackrepo, and for slackrepo it was explicitly stated that the author would in fact *not* add any kind of support for these fields, and I myself mentioned I could see adding support for it in sbotools. However, you seem to believe "adding support" would necessarily entail skipping READMEs, but as the current maintainer of sbotools I can tell you that that would be absolutely wrong. Currently, sbotools does allow you to skip reading README files, but then it turns off all dependency resolution for you. Adding support for an OPTIONAL field would not in any way change this. In fact, the way I envision adding support for this kind of thing goes like this: sboinstall => => => This slackbuild contains optional dependencies. => Please read the README before continuing. => Would you also like to include some of them? [y/N] ... From andreas.guldstrand at gmail.com Sun Nov 6 13:51:05 2016 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Sun, 6 Nov 2016 14:51:05 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <7b1e6a0e-c911-9c1a-d17a-158e351ab4f1@gmail.com> <743463ff-cfce-a897-d280-4ad8c4d4957f@iinet.net.au> <3927f883-9cf1-7b70-3edd-d84298315f51@gmail.com> <8ece8ce0-2d57-c763-a39f-44e50aec579b@gmail.com> <20161105154458.7701f2fd@shaggy.doo> <874aa6d3-96a7-fe47-5743-e51370a95aa2@gmail.com> <20161105232608.65e14371@shaggy.doo> <38e9bba28b6cf2f126f04ddf3c93c834@schoepfer.info> <20161106063113.263d9bcf@shaggy.doo> Message-ID: ... and then list them in order, showing their READMEs, asking the user to confirm each of them (just as he needs to for regular dependencies) On 6 November 2016 at 14:40, Andreas Guldstrand wrote: > On 6 November 2016 at 13:31, Erik Hanson wrote: >> No. Discussions are fine, we've made changes based on public >> discourse in the past. What appears before us is a handful of people >> really want to write some tool that plows through optional deps >> automatically. They don't want to read the README files, or maybe >> they don't need to, but I feel it's a bad idea to let EVERYBODY off >> the hook when it comes to the READMEs. > > I'm sorry, but there are only two tools where anyone has mentioned > support for this field in this thread (unless I missed something), and > those are sbotools and slackrepo, and for slackrepo it was explicitly > stated that the author would in fact *not* add any kind of support for > these fields, and I myself mentioned I could see adding support for it > in sbotools. However, you seem to believe "adding support" would > necessarily entail skipping READMEs, but as the current maintainer of > sbotools I can tell you that that would be absolutely wrong. > Currently, sbotools does allow you to skip reading README files, but > then it turns off all dependency resolution for you. > > Adding support for an OPTIONAL field would not in any way change this. > In fact, the way I envision adding support for this kind of thing goes > like this: > > sboinstall > => > => > => This slackbuild contains optional dependencies. > => Please read the README before continuing. > => Would you also like to include some of them? [y/N] > ... From ts at websafe.pl Sun Nov 6 16:31:37 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 6 Nov 2016 17:31:37 +0100 Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and usbredir] In-Reply-To: References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl> <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com> <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl> <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org> <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com> <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl> <580E2AC4.8050508@schoepfer.info> <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au> <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com> Message-ID: <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl> On 11/05/2016 09:20 PM, Andrzej Telszewski wrote: > On 05/11/16 20:59, King Beowulf wrote: >> to sift and test all OPTIONAL >> deps. > No, no, no. > You're confusing what OPTIONAL is about. > It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE README* > into the .info file, so *MACHINES* can understand it. > You are not going to test it more than you do already. > Let's finally understand that. Exactly. What really needs to be discussed is the acceptable format of the OPTIONAL field. Implementation by the backend of SlackBuilds.org and package building tools (sbopkg/sbotools/slpkg) is another subject which is not important now, because we should let the maintainers of these tools (and Slackbuilds.org) decide if they implement this field or not. In the worst case, if we agree how the format of OPTIONAL should look, we don't have to put this field in *.nfo, we can put it in the README or README.slackware or even create a dedicated SaaS returning the OPTIONAL value for each package via SOAP API call ;-) -- Thomas Szteliga From atelszewski at gmail.com Sun Nov 6 16:56:00 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 17:56:00 +0100 Subject: [Slackbuilds-users] SlackBuilds.org automated build system [was: Help offer] In-Reply-To: References: Message-ID: <8b521e98-fafd-57c3-2f0f-c500701a0d6f@gmail.com> On 06/11/16 12:47, David Spencer wrote: > I haven't discussed this with anybody until now, but maybe buildbot > could be useful to us. Unless I've made a mistake reading the buildbot > docs, it would allow people to volunteer their own systems as build > hosts. There are a couple of things we would need to worry about - > clean build environment, authentication - but the idea would seem to > fit a project like SlackBuilds.org that tries to exist with minimum > infrastructure of our own. > Although people volunteering their systems sound appealing, I wouldn't go that direction. You know how it goes, everything is fine until it's not. It is much better to have system that you have total control over. Then it's only you that is responsible for the system's security and also you don't have to worry about volunteer's system security. Capable machines are dirt cheap. For 20 euro/month you can have 8C/8T @ 2.4 GHz at https://www.online.net/ I can easily donate such machine. Or gather 10 people, we pay 4 euro/month and you have two capable machines. > I've got a draft SlackBuild for buildbot-0.9.1, but since 0.9 it's one > of those packages that need to download huge quantities of npm stuff > at build time :( > Brr. I know it is 2016 and I should love Java and JavaScript, but I don't. If you go this direction, I will try to do my best to help, but don't count on it too much. Orthodox would apply to me very well in that respect ;-) What I've been thinking of is brewing our own (because it's much cooler :-)) build system. Quick draft would be: - QEMU, for isolation from the host system, - overlayfs -> chroot -> build tool, for keeping the system clean (you understand it correctly, i.e. slackrepo would run in overlayed chroot, creating its overlays/chroots inside), - running everything from single QEMU instance would probably allow for easier memory management, - some way of sending the SlackBuild, either tarball or something that is run based on git push (I have just started studying git, so I don't know yet its capabilities), - some way of receiving/monitoring the build status. -- Best regards, Andrzej Telszewski From ts at websafe.pl Sun Nov 6 18:02:53 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 6 Nov 2016 19:02:53 +0100 Subject: [Slackbuilds-users] Help offer In-Reply-To: References: Message-ID: <89466fdb-029d-d84a-e8b5-f926f4b1dff0@websafe.pl> On 11/06/2016 12:47 PM, David Spencer wrote: > So the outline idea would be > - a submission arrives Will we be able to download submissions from the pending queue? That's a question to SlackBuilds.org maintainers :-) https://slackbuilds.org/pending/ > - our bot checks if it's a simple update, and how many packages > depend on it -- including optional deps ;) slpkg can do this (based on REQUIRES). Short example with virt-manager: # slpkg -t sbo virt-manager --check-deps Resolving dependencies... Done +==================================== | Package virt-manager dependencies : +==================================== \ +---[ Tree of dependencies ] | +--1: vala is dependency --> gtk-vnc, libosinfo, libvirt-glib, spice-gtk, virt-manager, virt-viewer, vte3 | +--2: celt051 is dependency --> spice, spice-gtk, virt-manager | +--3: pyparsing is dependency --> spice, spice-gtk, virt-manager | +--4: six is dependency --> spice, spice-gtk, virt-manager | +--5: spice-protocol is dependency --> spice, spice-gtk, virt-manager | +--6: spice is dependency --> spice-gtk, virt-manager | +--7: yajl is dependency --> libvirt, libvirt-glib, libvirt-python, virt-manager | +--8: urlgrabber is dependency --> libvirt, libvirt-glib, libvirt-python, virt-manager | +--9: libvirt is dependency --> libvirt-glib, libvirt-python, virt-manager | +--10: libosinfo is dependency --> virt-manager | +--11: libvirt-glib is dependency --> virt-manager | +--12: libvirt-python is dependency --> virt-manager | +--13: gnome-python2-gconf is dependency --> virt-manager | +--14: tunctl is dependency --> virt-manager | +--15: ipaddr-py is dependency --> virt-manager | +--16: python-urllib3 is dependency --> virt-manager | +--17: python-requests is dependency --> virt-manager | +--18: gtk-vnc is dependency --> virt-manager, virt-viewer | +--19: spice-gtk is dependency --> virt-manager | +--20: vte3 is dependency --> virt-manager > - if it's a simple update, and the total expected build time > (including depending packages) is less than a threshold, throw all > those builds and rebuilds at the automatic build queue (I already have > a database of build times) > - if possible, do builds with multiple build tools (sbopkg sbotools > slackrepo) because diverse tests catch more problems And don't forget about slpkg: https://github.com/dslackw/slpkg > - do some automated tests on the final package (e.g. Heinz's lintpkg) https://github.com/pprkut/lintpkg -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Nov 6 18:38:43 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 6 Nov 2016 19:38:43 +0100 Subject: [Slackbuilds-users] Error building atom package In-Reply-To: <1bf4d8b0-f737-a235-a8fa-5d76c3b4b952@slacky.it> References: <1bf4d8b0-f737-a235-a8fa-5d76c3b4b952@slacky.it> Message-ID: On 11/05/2016 04:17 PM, 414N wrote: > Hi everyone, > it?s from some time that I?m not able anymore to build and upgrade my > atom > installation to any of the newer versions (I?m currently running v1.9.8). > What I get during every build is this: ... > module.js:327 throw err; ^ Error: Cannot find module ... > Anyone has the same issue? I'm on 1.11.2 built few days ago (Oct 30). I had to build twice, because during the first build npm had problems downloading some required modules. I would suggest just try again because your issue looks similar. -- Thomas Szteliga From atelszewski at gmail.com Sun Nov 6 19:16:23 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 6 Nov 2016 20:16:23 +0100 Subject: [Slackbuilds-users] Suggestion: monospace font for README Message-ID: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com> Hi, I think it would make sense to have README enclosed within
 
tags, having monospace font.

Otherwise, when using GUI web browser, we lose all the text formatting 
the maintainers do.

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Sun Nov  6 19:28:10 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 6 Nov 2016 20:28:10 +0100
Subject: [Slackbuilds-users] SlackBuilds.org automated build system
 [was: Help offer]
In-Reply-To: <8b521e98-fafd-57c3-2f0f-c500701a0d6f@gmail.com>
References: 
 
 <8b521e98-fafd-57c3-2f0f-c500701a0d6f@gmail.com>
Message-ID: <24106417-6029-d57c-e511-62f64467ab7e@gmail.com>

On 06/11/16 17:56, Andrzej Telszewski wrote:
> On 06/11/16 12:47, David Spencer wrote:
>> I haven't discussed this with anybody until now, but maybe buildbot
>> could be useful to us. Unless I've made a mistake reading the buildbot
>> docs, it would allow people to volunteer their own systems as build
>> hosts. There are a couple of things we would need to worry about -
>> clean build environment, authentication - but the idea would seem to
>> fit a project like SlackBuilds.org that tries to exist with minimum
>> infrastructure of our own.
>>
>
> Although people volunteering their systems sound appealing, I wouldn't
> go that direction.
> You know how it goes, everything is fine until it's not.
> It is much better to have system that you have total control over.
> Then it's only you that is responsible for the system's security and
> also you don't have to worry about volunteer's system security.
>
> Capable machines are dirt cheap.
> For 20 euro/month you can have 8C/8T @ 2.4 GHz at https://www.online.net/
> I can easily donate such machine.
> Or gather 10 people, we pay 4 euro/month and you have two capable machines.
>
>> I've got a draft SlackBuild for buildbot-0.9.1, but since 0.9 it's one
>> of those packages that need to download huge quantities of npm stuff
>> at build time :(
>>
>
> Brr. I know it is 2016 and I should love Java and JavaScript, but I don't.
> If you go this direction, I will try to do my best to help, but don't
> count on it too much.
> Orthodox would apply to me very well in that respect ;-)
>
> What I've been thinking of is brewing our own (because it's much cooler
> :-)) build system.
>
> Quick draft would be:
> - QEMU, for isolation from the host system,
> - overlayfs -> chroot -> build tool, for keeping the system clean (you
> understand it correctly, i.e. slackrepo would run in overlayed chroot,
> creating its overlays/chroots inside),
> - running everything from single QEMU instance would probably allow for
> easier memory management,
> - some way of sending the SlackBuild, either tarball or something that
> is run based on git push (I have just started studying git, so I don't
> know yet its capabilities),
> - some way of receiving/monitoring the build status.
>

Alternative, or probably better approach than QEMU would be to use some 
of the available sandboxing technologies.

We install full Slackware into one directory.
Then this directory is overlayfs mounted on another directory.
Then this another directory is passed as rootfs to the container.
Then the build tool runs in the container.

I have no experience with containers, so I cannot tell how viable would 
it be.

-- 
Best regards,
Andrzej Telszewski

From erik at slackbuilds.org  Sun Nov  6 19:56:18 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Sun, 6 Nov 2016 13:56:18 -0600
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
Message-ID: <20161106135618.08f71022@shaggy.doo>

On Sun, 6 Nov 2016 20:16:23 +0100
Andrzej Telszewski  wrote:

> Hi,
> 
> I think it would make sense to have README enclosed within
> 
 tags, having monospace font.
> 
> Otherwise, when using GUI web browser, we lose all the text
> formatting the maintainers do.

I've made the change. Not sure what I think about it. Instantly I can
see some README files are not word wrapped properly:
https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
It's probably smart to keep it though:
https://slackbuilds.org/repository/14.2/multimedia/JSampler/


-- 
Erik

From atelszewski at gmail.com  Sun Nov  6 20:06:44 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 6 Nov 2016 21:06:44 +0100
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <20161106135618.08f71022@shaggy.doo>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
Message-ID: <03286bd7-463c-80be-b989-c15fc00a11a1@gmail.com>

On 06/11/16 20:56, Erik Hanson wrote:
> On Sun, 6 Nov 2016 20:16:23 +0100
> Andrzej Telszewski  wrote:
>
>> Hi,
>>
>> I think it would make sense to have README enclosed within
>> 
 tags, having monospace font.
>>
>> Otherwise, when using GUI web browser, we lose all the text
>> formatting the maintainers do.
>
> I've made the change. Not sure what I think about it. Instantly I can
> see some README files are not word wrapped properly:
> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
> It's probably smart to keep it though:
> https://slackbuilds.org/repository/14.2/multimedia/JSampler/
>
>

That was fast :-)
Let's give it a try, because at first sight it looks strange.


-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Sun Nov  6 20:15:26 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 6 Nov 2016 20:15:26 +0000
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl>
Message-ID: 

Folks, I'm going to reply to a lot of different people in this post.  Sorry!

>> It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE README*
>> into the .info file, so *MACHINES* can understand it.

Somebody would have to verify that it really is "*THE SAME INFORMATION
THAT YOU PUT IN THE README*", and really there is no way of automating
that, because the README is only readable by humans.

>> You are not going to test it more than you do already.
>> Let's finally understand that.

But we *would* have to *review* more than we already do.  It's one
more thing to go wrong, in a world where newbie maintainers can't even
get the slack-desc right.  It's one more way for reviewing admins to
make mistakes and approve something that's broken because README and
OPTIONAL say two different things.  That's not a total NO from me, but
it makes me worry a bit :(

We *want* SlackBuilds to have a really low barrier to entry. We want
them to be easy. We are proud that SlackBuilds.org is much easier for
new people to become maintainers than (for example) becoming a Debian
Developer. Making 'OPTIONAL=' more than a plain list is dooming newbie
maintainers to one more headache.  So I think that, if we do have
OPTIONAL, it should be a plain list.  And then I think we are going to
need to bring %README% back again, for cases where we need to say
"it's really complicated, you *must* read the README".

(But previously, people didn't understand %README%. Some maintainers
would always put it in, because it looked pretty.  So now, it really
means "This Package Clashes With Something In Slackware".)

> Implementation by the backend of SlackBuilds.org
> and package building tools (sbopkg/sbotools/slpkg) is another
> subject which is not important now, because we should let the
> maintainers of these tools (and Slackbuilds.org) decide if they
> implement this field or not.

But what's the point of a machine readable field that isn't being read
by the machine?  The tool maintainers would pretty much *have* to
implement it, otherwise you're all going to be very disappointed.

> In the worst case, if we agree how the format of OPTIONAL
> should look, we don't have to put this field in *.nfo,
> we can put it in the README or README.slackware or even create
> a dedicated SaaS returning the OPTIONAL value for each
> package via SOAP API call ;-)

Congratulations, you just reinvented slackrepo's hintfiles. You are
welcome to write a scraper to get the ADDREQUIRES fields from my
github. It would force me to update them properly :)  And there's lots
of other good stuff in there -- like what options are needed to enable
those deps, and which ones need -j1 to build.

Finally --

When I said we need to define the problems we currently have, I did
have two specific things in mind.

One: occasionally in the README files, there are mistakes in the
package names. Sometimes it's an upper/lower case error, or someone
has forgot (for example) "python-", or whatever.  I was going to audit
the whole lot before 14.2 came out, but didn't.  Sorry.  Anyway, this
still needs to be done.  If you see any mistakes, please do tell us.
Thanks in advance!

Two: the single biggest problem we have at the moment (IMO) is qt5.
Lots of packages don't build properly unless you remove qt5 before
building.  The only solution we have is to mention it in the README.

I'm generally a believer in "fix the technology, not the people".  But
I don't see how to avoid falling back to README when it's complicated.

Maybe we should give some thought to making README files nicer to use.
Maybe they should become more like manpages, with less random
description and with standardised headings and layout.  Markdown?

Maybe we should hide some prizes in README files, like someone once
did with a licence agreement. ;-)

Can I just say one more thing?
Thanks to everybody for caring so passionately about SlackBuilds.org :D
-D.

From atelszewski at gmail.com  Sun Nov  6 20:23:05 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sun, 6 Nov 2016 21:23:05 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl>
 
Message-ID: <0357123b-3739-fe8e-5eb5-caba1e7755d0@gmail.com>

On 06/11/16 21:15, David Spencer wrote:
> Maybe we should give some thought to making README files nicer to use.
> Maybe they should become more like manpages, with less random
> description and with standardised headings and layout.  Markdown?

I would love to see it.
But... wasn't it you that objected when I proposed tags in README?

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Sun Nov  6 20:34:44 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 6 Nov 2016 20:34:44 +0000
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <0357123b-3739-fe8e-5eb5-caba1e7755d0@gmail.com>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl>
 
 <0357123b-3739-fe8e-5eb5-caba1e7755d0@gmail.com>
Message-ID: 

> I would love to see it.
> But... wasn't it you that objected when I proposed tags in README?

There's a world of difference between semantic machine-readable xml or
bbcode style tags, which personally I don't like, and a light form of
markdown for headers, which improves readability for humans whether or
not the page is rendered.

And also I was sort-of trolling :)  Actually I would *hate* full-on
kramdown in README files.  It looks krap when it's not rendered.

But maybe it would be good to always say "OPTIONAL DEPENDENCIES" as a
header instead of "The following requirements can be enabled" or a
thousand variations.

Cheers
-D.

From ts at websafe.pl  Sun Nov  6 20:44:01 2016
From: ts at websafe.pl (Thomas Szteliga)
Date: Sun, 6 Nov 2016 21:44:01 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl>
 
Message-ID: <295c9d65-131b-d2d8-18d0-9512af8799ff@websafe.pl>

On 11/06/2016 09:15 PM, David Spencer wrote:
> Maybe we should give some thought to making README files nicer to use.
> Maybe they should become more like manpages, with less random
> description and with standardised headings and layout.  Markdown?


Markdown is a very good idea. It would also solve the
current problem which occurred after enabling the
monospaced font:

https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/

;-)

-- 
Thomas Szteliga


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3719 bytes
Desc: S/MIME Cryptographic Signature
URL: 

From ts at websafe.pl  Sun Nov  6 20:46:37 2016
From: ts at websafe.pl (Thomas Szteliga)
Date: Sun, 6 Nov 2016 21:46:37 +0100
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <20161106135618.08f71022@shaggy.doo>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
Message-ID: <2cc841a6-331f-f898-021f-f7fc0ba8785a@websafe.pl>

On 11/06/2016 08:56 PM, Erik Hanson wrote:
> I've made the change. Not sure what I think about it. Instantly I can
> see some README files are not word wrapped properly:
> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
> It's probably smart to keep it though:
> https://slackbuilds.org/repository/14.2/multimedia/JSampler/


I don't think ACII-art should be supported ;-)
But if that's really needed the maintainer of JSampler
will be able to achieve this using Markdown.

So Markdown +1.


-- 
Thomas Szteliga


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3719 bytes
Desc: S/MIME Cryptographic Signature
URL: 

From yalhcru at gmail.com  Sun Nov  6 20:47:56 2016
From: yalhcru at gmail.com (B Watson)
Date: Sun, 6 Nov 2016 15:47:56 -0500
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <20161106135618.08f71022@shaggy.doo>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
Message-ID: 

On 11/6/16, Erik Hanson  wrote:

> I've made the change. Not sure what I think about it. Instantly I can
> see some README files are not word wrapped properly:
> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/

Yuck.

I was about to comment that un-word-wrapped READMEs violate the
guidelines, but went & looked first... and there's nothing in there
about word-wrapping or max line length in the README.

Maybe there should be?

$ find . -name README | wc -l
6124
$ find . -name README | xargs egrep -l
'^.{81,}$'|wc -l
288

Affects 5% of the builds. Shouldn't be too much work to fix, I'm willing
to spend some time on it if you want. In theory, every maintainer should
fix his own READMEs, but this is a cosmetic-only change, might be OK to
just do it?

Some of them are formatted OK, except they have URLs that are too
long. Not much can be done about that.

From ts at websafe.pl  Sun Nov  6 20:53:59 2016
From: ts at websafe.pl (Thomas Szteliga)
Date: Sun, 6 Nov 2016 21:53:59 +0100
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
Message-ID: 

On 11/06/2016 09:47 PM, B Watson wrote:
> On 11/6/16, Erik Hanson  wrote:
>> I've made the change. Not sure what I think about it. Instantly I can
>> see some README files are not word wrapped properly:
>> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/
> Yuck.
> I was about to comment that un-word-wrapped READMEs violate the
> guidelines, but went & looked first... and there's nothing in there
> about word-wrapping or max line length in the README.
> Maybe there should be?


Definitely. Max line length should be mandatory.


> $ find . -name README | wc -l
> 6124
> $ find . -name README | xargs egrep -l
> '^.{81,}$'|wc -l
> 288
> Affects 5% of the builds. Shouldn't be too much work to fix, I'm willing
> to spend some time on it if you want. In theory, every maintainer should
> fix his own READMEs, but this is a cosmetic-only change, might be OK to
> just do it?
> Some of them are formatted OK, except they have URLs that are too
> long. Not much can be done about that.



That's IMHO why Markdown would be the best solution for README files.


-- 
Thomas Szteliga


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3719 bytes
Desc: S/MIME Cryptographic Signature
URL: 

From ryan.q at linux.com  Sun Nov  6 21:03:57 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 06 Nov 2016 21:03:57 +0000
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 
Message-ID: 

>
>
> That's IMHO why Markdown would be the best solution for README files.
>

I am a big fan of Markdown. How much support is needed? If we only want to
be able to have code snippets, I wrote a really lightweight JavaScript
library to parse text and syntax highlight blocks of code like this:

```sh
#!/bin/sh
slackpkg_update_only() {
  slackpkg update gpg
  slackpkg update
}
```

It ends up looking something like the attached image.[image: Screenshot at
2016-11-06 13:00:26.png]

https://github.com/ryanpcmcquen/codeFormatter

If we only need code snippet support, this may be easier to integrate than
a full fledged markdown parser (if people are even onboard with that).
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot at 2016-11-06 13:00:26.png
Type: image/png
Size: 3259 bytes
Desc: not available
URL: 

From erik at slackbuilds.org  Sun Nov  6 21:11:08 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Sun, 6 Nov 2016 15:11:08 -0600
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
Message-ID: <20161106151108.0e6b4f7f@shaggy.doo>

On Sun, 6 Nov 2016 15:47:56 -0500
B Watson  wrote:

> I was about to comment that un-word-wrapped READMEs violate the
> guidelines, but went & looked first... and there's nothing in there
> about word-wrapping or max line length in the README.
> 
> Maybe there should be?

I agree.

> Affects 5% of the builds. Shouldn't be too much work to fix, I'm
> willing to spend some time on it if you want. In theory, every
> maintainer should fix his own READMEs, but this is a cosmetic-only
> change, might be OK to just do it?

If you want to push a branch that's just cosmetic fixes, I think we
could merge it.


-- 
Erik

From yalhcru at gmail.com  Sun Nov  6 22:41:30 2016
From: yalhcru at gmail.com (B Watson)
Date: Sun, 6 Nov 2016 17:41:30 -0500
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <20161106151108.0e6b4f7f@shaggy.doo>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
Message-ID: 

On 11/6/16, Erik Hanson  wrote:

> If you want to push a branch that's just cosmetic fixes, I think we
> could merge it.

OK, working on it now, branch will be called user/urchlay/cosmetics.

From jebrhansen+SBo at gmail.com  Sun Nov  6 22:48:18 2016
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 06 Nov 2016 22:48:18 +0000
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
Message-ID: 

You could also just use some CSS and have browsers wrap the text. Seems
much easier than editing a ton of READMES...

pre {
white-space: pre-wrap;       /* css-3 */
white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
white-space: -pre-wrap;      /* Opera 4-6 */
white-space: -o-pre-wrap;    /* Opera 7 */
word-wrap: break-word;       /* Internet Explorer 5.5+ */
}

http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag

On Sun, Nov 6, 2016, 5:41 PM B Watson  wrote:

> On 11/6/16, Erik Hanson  wrote:
>
> > If you want to push a branch that's just cosmetic fixes, I think we
> > could merge it.
>
> OK, working on it now, branch will be called user/urchlay/cosmetics.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From ryan.q at linux.com  Sun Nov  6 23:14:21 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Sun, 06 Nov 2016 23:14:21 +0000
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
Message-ID: 

On Sun, Nov 6, 2016 at 2:48 PM Jeremy Hansen jebrhansen+SBo at gmail.com
 wrote:

You could also just use some CSS and have browsers wrap the text. Seems
> much easier than editing a ton of READMES...
>
> pre {
> white-space: pre-wrap;       /* css-3 */
> white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
> white-space: -pre-wrap;      /* Opera 4-6 */
> white-space: -o-pre-wrap;    /* Opera 7 */
> word-wrap: break-word;       /* Internet Explorer 5.5+ */
> }
>
> http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag
>
Any reasonably modern browser will not need a prefix, meaning you could
simplify the CSS to:

pre {
  white-space: pre-wrap;}

https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility
?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From jebrhansen+SBo at gmail.com  Sun Nov  6 23:33:06 2016
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Sun, 06 Nov 2016 23:33:06 +0000
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
Message-ID: 

Yeah, it just covers any browsers that might not (which probably wouldn't
be frequently used by Slackware users).

On Sun, Nov 6, 2016, 6:14 PM Ryan P.C. McQuen  wrote:

> On Sun, Nov 6, 2016 at 2:48 PM Jeremy Hansen jebrhansen+SBo at gmail.com
>  wrote:
>
> You could also just use some CSS and have browsers wrap the text. Seems
> much easier than editing a ton of READMES...
>
> pre {
> white-space: pre-wrap;       /* css-3 */
> white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
> white-space: -pre-wrap;      /* Opera 4-6 */
> white-space: -o-pre-wrap;    /* Opera 7 */
> word-wrap: break-word;       /* Internet Explorer 5.5+ */
> }
>
> http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag
>
> Any reasonably modern browser will not need a prefix, meaning you could
> simplify the CSS to:
>
> pre {
>   white-space: pre-wrap;}
>
>
> https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility
> ?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From willysr at slackbuilds.org  Mon Nov  7 00:35:13 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Nov 2016 07:35:13 +0700
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
Message-ID: 

>> You could also just use some CSS and have browsers wrap the text. Seems
>> much easier than editing a ton of READMES...
>>
>> pre {
>> white-space: pre-wrap;       /* css-3 */
>> white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
>> white-space: -pre-wrap;      /* Opera 4-6 */
>> white-space: -o-pre-wrap;    /* Opera 7 */
>> word-wrap: break-word;       /* Internet Explorer 5.5+ */
>> }
>>
>> http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag
>>
>> Any reasonably modern browser will not need a prefix, meaning you could
>> simplify the CSS to:
>>
>> pre {
>>   white-space: pre-wrap;}
>>
>>
>> https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility

I implemented this proposal (wrapping issue) just now
can anyone review the results in
https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/ ?

The content of the README will be using 
 and it looks different
from the rest of the page (deps, maintainer, etc).


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From atelszewski at gmail.com  Mon Nov  7 00:35:19 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 7 Nov 2016 01:35:19 +0100
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
Message-ID: <0f563634-fcc8-d5cf-f46c-7ef7eaae5407@gmail.com>

On 07/11/16 01:35, Willy Sudiarto Raharjo wrote:
>>> You could also just use some CSS and have browsers wrap the text. Seems
>>> much easier than editing a ton of READMES...
>>>
>>> pre {
>>> white-space: pre-wrap;       /* css-3 */
>>> white-space: -moz-pre-wrap;  /* Mozilla, since 1999 */
>>> white-space: -pre-wrap;      /* Opera 4-6 */
>>> white-space: -o-pre-wrap;    /* Opera 7 */
>>> word-wrap: break-word;       /* Internet Explorer 5.5+ */
>>> }
>>>
>>> http://stackoverflow.com/questions/248011/how-do-i-wrap-text-in-a-pre-tag
>>>
>>> Any reasonably modern browser will not need a prefix, meaning you could
>>> simplify the CSS to:
>>>
>>> pre {
>>>   white-space: pre-wrap;}
>>>
>>>
>>> https://developer.mozilla.org/en-US/docs/Web/CSS/white-space#Browser_compatibility
>
> I implemented this proposal (wrapping issue) just now
> can anyone review the results in
> https://slackbuilds.org/repository/14.2/multimedia/ExMplayer/ ?
>

Works for me (SeaMonkey 2.40).

> The content of the README will be using 
 and it looks different
> from the rest of the page (deps, maintainer, etc).
>
>
>
>
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Mon Nov  7 00:41:24 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Nov 2016 07:41:24 +0700
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
Message-ID: 

> I was about to comment that un-word-wrapped READMEs violate the
> guidelines, but went & looked first... and there's nothing in there
> about word-wrapping or max line length in the README.
>
> Maybe there should be?
>
> $ find . -name README | wc -l
> 6124
> $ find . -name README | xargs egrep -l
> '^.{81,}$'|wc -l
> 288
>
> Affects 5% of the builds. Shouldn't be too much work to fix, I'm willing
> to spend some time on it if you want. In theory, every maintainer should
> fix his own READMEs, but this is a cosmetic-only change, might be OK to
> just do it?

I have implemented a css code to fix the wrap issue, but feel free to
update the README

-- 
Willy Sudiarto Raharjo

From yalhcru at gmail.com  Mon Nov  7 02:54:26 2016
From: yalhcru at gmail.com (B Watson)
Date: Sun, 6 Nov 2016 21:54:26 -0500
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 
Message-ID: 

On 11/6/16, Willy Sudiarto Raharjo  wrote:

> I have implemented a css code to fix the wrap issue, but feel free to
> update the README

Still worth doing, the READMEs with long lines look like crap in text
editors or less (which to me is their native environment, not the web).

From fernando.lopezjr at gmail.com  Mon Nov  7 03:00:21 2016
From: fernando.lopezjr at gmail.com (Fernando Lopez)
Date: Sun, 6 Nov 2016 20:00:21 -0700
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 
 
Message-ID: 

can we have a smaller font? font size is too big at least for me...

On Sun, Nov 6, 2016 at 7:54 PM, B Watson  wrote:

> On 11/6/16, Willy Sudiarto Raharjo  wrote:
>
> > I have implemented a css code to fix the wrap issue, but feel free to
> > update the README
>
> Still worth doing, the READMEs with long lines look like crap in text
> editors or less (which to me is their native environment, not the web).
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>


-- 

------------
Regards,
    Fernando Lopez Jr.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From slackbuilds at schoepfer.info  Mon Nov  7 06:40:38 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 07 Nov 2016 07:40:38 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl>
 
Message-ID: 

>>> It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE 
>>> README*
>>> into the .info file, so *MACHINES* can understand it.
> 
> Somebody would have to verify that it really is "*THE SAME INFORMATION
> THAT YOU PUT IN THE README*", and really there is no way of automating
> that, because the README is only readable by humans.

Yes.
If it comes that far, i'm willling to help by editing several hundreds 
.info-files.

>>> You are not going to test it more than you do already.
>>> Let's finally understand that.
> 
> But we *would* have to *review* more than we already do.

About 15% of all packages are affected with optional deps.
Just a rough find/grep
$ find . -type f -name 'README*' -exec fgrep -i optional '{}' + | wc -l
866

For new submitted packages the admins would have more work, for updates 
very less, as usually dependencies are not changing all the time.

> We *want* SlackBuilds to have a really low barrier to entry. We want
> them to be easy. We are proud that SlackBuilds.org is much easier for
> new people to become maintainers than (for example) becoming a Debian
> Developer.
> Making 'OPTIONAL=' more than a plain list is dooming newbie
> maintainers to one more headache.  So I think that, if we do have
> OPTIONAL, it should be a plain list.

It's really important to keep it simple. In most cases(85%) a maintainer 
won't have to fill the option field at all.
In most cases of the affected 15%, it would be a simple list, like in 
the REQUIRED field.

For the rest(e.g.qemu/spice-gtk and usbredir), the OPTIONAL= field gets 
really interesting and most useful in my opinion, if an OPTION:
- requires the OPTION to build against another package
- makes sense only combined with another OPTION
- conflicts with another package

This rendered on SBo-website would prevent bugreports(two ccured in the 
last months about uncleraness of qemu/gtk-spice,usbredir), as it is more 
obvious that optional packages have to be checked for further optional 
packages, which then may have become a requirement.
Links are more userfriendly, in the current state it's errorprone on the 
SBo-website to copy-paste optional deps from optional deps from optional 
deps to the next browser-tab, where the website has to be opend before.
And that all *because* i want to read the READMEs, i want a better way 
to get the READMEs by OPTIONAL=.
The possibility for 3rd-party automation is a sideeffect, i don't use 
them.
If those tools don't want to fully support syntax like !,&&,(),
these still just could cycle through OPTIONAL= showing the READMEs.

> Two: the single biggest problem we have at the moment (IMO) is qt5.
> Lots of packages don't build properly unless you remove qt5 before
> building.  The only solution we have is to mention it in the README.

If this problem only occurs on compiletime, maybe it
would be solved by implementing something like
"REQUIRED=!qt5" ?


Johannes

From andreas.guldstrand at gmail.com  Mon Nov  7 08:36:09 2016
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Mon, 7 Nov 2016 09:36:09 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <52d16b1b-61a5-04ce-129e-487fc0670744@websafe.pl>
 
 
Message-ID: 

>> Two: the single biggest problem we have at the moment (IMO) is qt5.
>> Lots of packages don't build properly unless you remove qt5 before
>> building.  The only solution we have is to mention it in the README.

This has got absolutely nothing to do with an OPTIONAL field though.
And the README works absolutely fine for this kind of thing without
any machine-readable help in the form of a .info field. No reason to
even involve this in the discussion.

From kingbeowulf at gmail.com  Mon Nov  7 08:59:37 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Mon, 7 Nov 2016 00:59:37 -0800
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
Message-ID: <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>

On 11/05/2016 01:20 PM, Andrzej Telszewski wrote:
> On 05/11/16 20:59, King Beowulf wrote:
>> to sift and test all OPTIONAL
>> deps.
> 
> No, no, no.
> 
> You're confusing what OPTIONAL is about.
> It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE README*
> into the .info file, so *MACHINES* can understand it.
> 
> You are not going to test it more than you do already.
> Let's finally understand that.
> 

I disagree.  Most packages have too many potential compile options.
Once you place these into an OPTIONAL tag to allow for machine readable
parsing, you are asking for trouble if you do not test each use case.

If its just for human-readable, then just leave it in the README.

I haven't coded in decades, and I am not that daft to believe that this
automation can solve this issue.  It can't.  SBo isn't designed for this.

-Ed

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From arnaud.garcia-fernandez at laposte.net  Mon Nov  7 09:01:49 2016
From: arnaud.garcia-fernandez at laposte.net (Arnaud)
Date: Mon, 7 Nov 2016 10:01:49 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com>
 
 <20161105215100.1df69d2e@shaggy.doo>
 
Message-ID: <20161107100149.e463322ed23c19c3b24d49f4@laposte.net>

> On 06/11/16 03:51, Erik Hanson wrote:
> > The goal is then that no one would
> > ever have to look at the README file, they could just tick some boxes
> > and be on their way.
> 
> No, that's not the point. At least not mine.
> The point is to facilitate the process.
> And you can't argue that for _educated_ user it is going to be.
> 
> But as you mentioned before, we might have problem with _education_ 


	My own use-case for an OPTIONAL field would be to alert me when there is
an update available for an installed package, which happen to be an OPTIONAL
dependency for another package I have installed.
	Quite the same as the actual REQUIRE : when a REQUIRED package has an
update, I list the installed packages which depends on it.
	This allows me to decide if I want to rebuild the package for which the
dependency changed, even if it hasn't changed itself.

	It had happened to me on occasions that ffmpeg stopped working because I
updated an OPTIONAL dependency, I was actually thinking about GREPing on the
READMEs to find those OPTIONAL dependencies, because it sucks when ffmpeg is
broken like that, and there is no easy way to know in advance in the general case
(I could do something specific for ffmpeg, but that's not the point, and there
are other packages with OPTIONAL dependencies, though none with as many as
this one).
	It could even happen while we aren't even aware we had an OPTIONAL
dependency, because some packages detects them automatically, and we could have
an OPTIONAL package already installed, hence linked into a new one without being
really aware of that : no step about it was taken, and we might not even need the
OPTIONAL part, but it's there, therefore used.

	For my own use-case, a simple list of possible OPTIONAL dependencies is
clearly enough, because I will read the READMEs, and know what to do, but I have
no direct way of automatically knowing what will be impacted by a package update.

	I think this is something that could be useful to everybody. It doesn't
change much, basically a tool would add OPTIONAL dependencies to REQUIRE ones
when they are already installed, for the purpose of presenting to the user what
might need rebuilding after an update, or even what packages might depend on
another one if we want to remove it :
? Hey, this package isn't REQUIREd by any of your installed packages, but is
OPTIONAL for this one, are you sure you want to remove it ? ?
	Or in my case a script "is_this_package_required PKGNAME" reporting when
the package is REQUIRED and OPTIONAL.


	Those are thoughts about the usefulness of the OPTIONAL field completely
out of an automatic building process with checkboxes and automatic dependencies
checking and building.

	Arnaud.

From yth at ythogtha.org  Mon Nov  7 09:00:05 2016
From: yth at ythogtha.org (Ythogtha)
Date: Mon, 7 Nov 2016 10:00:05 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com>
 
 <20161105215100.1df69d2e@shaggy.doo>
 
Message-ID: <20161107100005.676dbbb7ce2b83e9d195b165@ythogtha.org>

> On 06/11/16 03:51, Erik Hanson wrote:
> > The goal is then that no one would
> > ever have to look at the README file, they could just tick some boxes
> > and be on their way.
> 
> No, that's not the point. At least not mine.
> The point is to facilitate the process.
> And you can't argue that for _educated_ user it is going to be.
> 
> But as you mentioned before, we might have problem with _education_ 


	My own use-case for an OPTIONAL field would be to alert me when there is
an update available for an installed package, which happen to be an OPTIONAL
dependency for another package I have installed.
	Quite the same as the actual REQUIRE : when a REQUIRED package has an
update, I list the installed packages which depends on it.
	This allows me to decide if I want to rebuild the package for which the
dependency changed, even if it hasn't changed itself.

	It had happened to me on occasions that ffmpeg stopped working because I
updated an OPTIONAL dependency, I was actually thinking about GREPing on the
READMEs to find those OPTIONAL dependencies, because it sucks when ffmpeg is
broken like that, and there is no easy way to know in advance in the general case
(I could do something specific for ffmpeg, but that's not the point, and there
are other packages with OPTIONAL dependencies, though none with as many as
this one).
	It could even happen while we aren't even aware we had an OPTIONAL
dependency, because some packages detects them automatically, and we could have
an OPTIONAL package already installed, hence linked into a new one without being
really aware of that : no step about it was taken, and we might not even need the
OPTIONAL part, but it's there, therefore used.

	For my own use-case, a simple list of possible OPTIONAL dependencies is
clearly enough, because I will read the READMEs, and know what to do, but I have
no direct way of automatically knowing what will be impacted by a package update.

	I think this is something that could be useful to everybody. It doesn't
change much, basically a tool would add OPTIONAL dependencies to REQUIRE ones
when they are already installed, for the purpose of presenting to the user what
might need rebuilding after an update, or even what packages might depend on
another one if we want to remove it :
? Hey, this package isn't REQUIREd by any of your installed packages, but is
OPTIONAL for this one, are you sure you want to remove it ? ?
	Or in my case a script "is_this_package_required PKGNAME" reporting when
the package is REQUIRED and OPTIONAL.


	Those are thoughts about the usefulness of the OPTIONAL field completely
out of an automatic building process with checkboxes and automatic dependencies
checking and building.

-- 
Arnaud 

From yth at ythogtha.org  Mon Nov  7 09:16:39 2016
From: yth at ythogtha.org (Ythogtha)
Date: Mon, 7 Nov 2016 10:16:39 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <20161107100005.676dbbb7ce2b83e9d195b165@ythogtha.org>
References: <41c0a0b0-0fb5-d5ad-aef4-8007e293a310@gmail.com>
 
 <20161105215100.1df69d2e@shaggy.doo>
 
 <20161107100005.676dbbb7ce2b83e9d195b165@ythogtha.org>
Message-ID: <20161107101639.bd4953114ab467d7e3c2e411@ythogtha.org>

Sorry for the double mail, I thought it still wasn't working with this email
address, but it seems I did something right...

	Arnaud.


> > On 06/11/16 03:51, Erik Hanson wrote:
> > > The goal is then that no one would
> > > ever have to look at the README file, they could just tick some boxes
> > > and be on their way.
> > 
> > No, that's not the point. At least not mine.
> > The point is to facilitate the process.
> > And you can't argue that for _educated_ user it is going to be.
> > 
> > But as you mentioned before, we might have problem with _education_ 
> 
> 
> 	My own use-case for an OPTIONAL field would be to alert me when there is
> an update available for an installed package, which happen to be an OPTIONAL
> dependency for another package I have installed.
> 	Quite the same as the actual REQUIRE : when a REQUIRED package has an
> update, I list the installed packages which depends on it.
> 	This allows me to decide if I want to rebuild the package for which the
> dependency changed, even if it hasn't changed itself.
> 
> 	It had happened to me on occasions that ffmpeg stopped working because I
> updated an OPTIONAL dependency, I was actually thinking about GREPing on the
> READMEs to find those OPTIONAL dependencies, because it sucks when ffmpeg is
> broken like that, and there is no easy way to know in advance in the general case
> (I could do something specific for ffmpeg, but that's not the point, and there
> are other packages with OPTIONAL dependencies, though none with as many as
> this one).
> 	It could even happen while we aren't even aware we had an OPTIONAL
> dependency, because some packages detects them automatically, and we could have
> an OPTIONAL package already installed, hence linked into a new one without being
> really aware of that : no step about it was taken, and we might not even need the
> OPTIONAL part, but it's there, therefore used.
> 
> 	For my own use-case, a simple list of possible OPTIONAL dependencies is
> clearly enough, because I will read the READMEs, and know what to do, but I have
> no direct way of automatically knowing what will be impacted by a package update.
> 
> 	I think this is something that could be useful to everybody. It doesn't
> change much, basically a tool would add OPTIONAL dependencies to REQUIRE ones
> when they are already installed, for the purpose of presenting to the user what
> might need rebuilding after an update, or even what packages might depend on
> another one if we want to remove it :
> ? Hey, this package isn't REQUIREd by any of your installed packages, but is
> OPTIONAL for this one, are you sure you want to remove it ? ?
> 	Or in my case a script "is_this_package_required PKGNAME" reporting when
> the package is REQUIRED and OPTIONAL.
> 
> 
> 	Those are thoughts about the usefulness of the OPTIONAL field completely
> out of an automatic building process with checkboxes and automatic dependencies
> checking and building.
> 
> -- 
> Arnaud 
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 


-- 
Arnaud 

From slackbuilds at schoepfer.info  Mon Nov  7 09:43:53 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Mon, 07 Nov 2016 10:43:53 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
Message-ID: <858969e68c0ea46610818462b00b05da@schoepfer.info>

On 2016-11-07 09:59, King Beowulf wrote:
> On 11/05/2016 01:20 PM, Andrzej Telszewski wrote:
>> On 05/11/16 20:59, King Beowulf wrote:
>>> to sift and test all OPTIONAL
>>> deps.
>> 
>> No, no, no.
>> 
>> You're confusing what OPTIONAL is about.
>> It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE 
>> README*
>> into the .info file, so *MACHINES* can understand it.
>> 
>> You are not going to test it more than you do already.
>> Let's finally understand that.
>> 
> 
> I disagree.  Most packages have too many potential compile options.

You are still getting it wrong.
Nobody proposed to put any available compile option in an option-field.
This would most likely be complete insane.

Johannes

From s.arcus at open-t.co.uk  Mon Nov  7 09:57:15 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Mon, 7 Nov 2016 09:57:15 +0000
Subject: [Slackbuilds-users] EasyRSA scripts for testing
Message-ID: <41632ac7-e052-0f18-474d-99b728db9c59@open-t.co.uk>

I attach here the easyrsa SBo scripts I've made - if some people 
wouldn't mind taking them for a test run and reporting any problems they 
might spot - please.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: easyrsa.tar.gz
Type: application/gzip
Size: 38392 bytes
Desc: not available
URL: 

From s.arcus at open-t.co.uk  Mon Nov  7 10:11:14 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Mon, 7 Nov 2016 10:11:14 +0000
Subject: [Slackbuilds-users] EasyRSA scripts for testing
In-Reply-To: <41632ac7-e052-0f18-474d-99b728db9c59@open-t.co.uk>
References: <41632ac7-e052-0f18-474d-99b728db9c59@open-t.co.uk>
Message-ID: <757f70ab-62a0-34eb-d19a-79c38295fe72@open-t.co.uk>


On 07/11/16 09:57, Sebastian Arcus wrote:
> I attach here the easyrsa SBo scripts I've made - if some people
> wouldn't mind taking them for a test run and reporting any problems they
> might spot - please.

Oops - the scripts include the source archive file for some reason. 
Ignore that - I will remove it in the final version I will submit to SBo.

From atelszewski at gmail.com  Mon Nov  7 10:10:46 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 7 Nov 2016 11:10:46 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <858969e68c0ea46610818462b00b05da@schoepfer.info>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
Message-ID: 

On 07/11/16 10:43, Franzen wrote:
> On 2016-11-07 09:59, King Beowulf wrote:
>> On 11/05/2016 01:20 PM, Andrzej Telszewski wrote:
>>> On 05/11/16 20:59, King Beowulf wrote:
>>>> to sift and test all OPTIONAL
>>>> deps.
>>>
>>> No, no, no.
>>>
>>> You're confusing what OPTIONAL is about.
>>> It's about replicating *THE SAME INFORMATION THAT YOU PUT IN THE README*
>>> into the .info file, so *MACHINES* can understand it.
>>>
>>> You are not going to test it more than you do already.
>>> Let's finally understand that.
>>>
>>
>> I disagree.  Most packages have too many potential compile options.
>
> You are still getting it wrong.
> Nobody proposed to put any available compile option in an option-field.
> This would most likely be complete insane.

Would it? :-)

Without having the compile options machine readable there is no much 
sens of putting OPTIONAL in .info.

At least not directly by maintainers.

If the OPTIONAL was about only listing optional packages, then it would 
be far less error prone to simply tag them in README and then having SBO 
parse the README and create the OPTIONAL field.

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Mon Nov  7 11:12:29 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 7 Nov 2016 11:12:29 +0000
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
Message-ID: 

>> Nobody proposed to put any available compile option in an option-field.
>> This would most likely be complete insane.
>
> Would it? :-)
>
> Without having the compile options machine readable there is no much sens of
> putting OPTIONAL in .info.

This is why we have such a long thread.
Everybody has a different idea of OPTIONAL in their own mind, that
solves different problems.

-D.

From atelszewski at gmail.com  Mon Nov  7 11:14:39 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 7 Nov 2016 12:14:39 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
Message-ID: <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>

Hi,

I haven't slept too long and came up with the following idea
(this assumes that we do *somehow* agree on some tags in README):


The following optional, not auto-detected packages enable additional 
features (you need to install the package and set environment variable):

[opt] libass, [env] ASS=yes|no [/opt], for ASS support,
[opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
[opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for 
IEC61883 support,


The magic behind:
we do not modify .info in any way, we just allow willing maintainers 
(you can choose if you want or not to support the idea) to structure the 
README in particular way, enclosing optional packages and environment 
variables in tags.

We do it only for simple cases, i.e. if there is dependency that 
requires choosing between two exclusive ones, of which one depends on 
another optional package, then we leave it to human for parsing 
(although it still would be very helpful to be able to click on the 
optional package to see what is it about).

SBo would parse the README to create clickable optional packages.
Build tools would do what they have to do to do what they want to do.

SBo would allow for README preview, so the maintainer could ensure it's 
the way he thinks it is.
SBo would immediately reject the submission if there was syntax error 
(yuk, syntax error in README :-^).

Subject for improvements :-)

-- 
Best regards,
Andrzej Telszewski

From andreas.guldstrand at gmail.com  Mon Nov  7 11:35:10 2016
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Mon, 7 Nov 2016 12:35:10 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
Message-ID: 

Another thread proposed allowing markdown-like sections in the READMEs
and standardising on how to format the README for each slackbuild
according to that, which would be fine IMO as it's still very readable
in a text editor; the markdown section tagging is very easy to read.

But adding semantics for individual env options and optional
dependencies in the README strikes me as a horrible idea. Not only
would it be absolute hell for any machine to parse and be extremely
prone to syntax errors from the author (it's a README! SYNTAX
ERRORS????), but it would also look like utter s**te in a text editor.

On 7 November 2016 at 12:14, Andrzej Telszewski  wrote:
> Hi,
>
> I haven't slept too long and came up with the following idea
> (this assumes that we do *somehow* agree on some tags in README):
>
>
> The following optional, not auto-detected packages enable additional
> features (you need to install the package and set environment variable):
>
> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for IEC61883
> support,
>
>
> The magic behind:
> we do not modify .info in any way, we just allow willing maintainers (you
> can choose if you want or not to support the idea) to structure the README
> in particular way, enclosing optional packages and environment variables in
> tags.
>
> We do it only for simple cases, i.e. if there is dependency that requires
> choosing between two exclusive ones, of which one depends on another
> optional package, then we leave it to human for parsing (although it still
> would be very helpful to be able to click on the optional package to see
> what is it about).
>
> SBo would parse the README to create clickable optional packages.
> Build tools would do what they have to do to do what they want to do.
>
> SBo would allow for README preview, so the maintainer could ensure it's the
> way he thinks it is.
> SBo would immediately reject the submission if there was syntax error (yuk,
> syntax error in README :-^).
>
> Subject for improvements :-)
>
>
> --
> Best regards,
> Andrzej Telszewski
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From baildon.research at googlemail.com  Mon Nov  7 11:38:38 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Mon, 7 Nov 2016 11:38:38 +0000
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
Message-ID: 

> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for IEC61883

* No parser exists for this language that you have just invented. Some
poor fool would have to write that. And it's one of the context
senstive languages (like HTML) that can't be parsed with regular
expressions -- see https://en.wikipedia.org/wiki/Chomsky_hierarchy

* It's too complicated for newbies.

* It's going to look ugly in the README, and that really does matter.

* It's incomplete: there are packages with option formats that this
language can't describe. Look at grass. Yet again, I repeat: don't
propose a solution until you have checked whether it works in the real
world. You're only ever looking at ffmpeg :(

-D.

From ts at websafe.pl  Mon Nov  7 11:50:48 2016
From: ts at websafe.pl (Thomas Szteliga)
Date: Mon, 7 Nov 2016 12:50:48 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
Message-ID: <2edbc6af-5abc-c610-9ab2-3763ef4b2415@websafe.pl>

On 11/07/2016 12:14 PM, Andrzej Telszewski wrote:
> I haven't slept too long and came up with the following idea
> (this assumes that we do *somehow* agree on some tags in README):
> The following optional, not auto-detected packages enable additional
> features (you need to install the package and set environment variable):
> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for
> IEC61883 support,


IMVHO that's way too complicated.


My suggestion:

OPTIONAL=libass,libbluray,libiec61883,libavc1394

Slackbuilds could simply enable/disable optional deps
by checking if the defined package is available in /var/log/packages.


-- 
Thomas Szteliga


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3719 bytes
Desc: S/MIME Cryptographic Signature
URL: 

From alik at ejik.org  Mon Nov  7 11:54:06 2016
From: alik at ejik.org (Alexander Verbovetsky)
Date: Mon, 07 Nov 2016 14:54:06 +0300
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
Message-ID: <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>

Hello,

I like the mono font for README, but I use a large font and for me lines
are wrapped after 58 symbols.

On the other hand, the text is a narrow strip on my screen (1920x1200).
Could it be possible to let the text use all available space in width?

If it's not feasible, maybe someone can suggest me what to put in my
firefox's chrome/userContent.css to archive the same result?

Thank you in advance!

Best regards,
Alexander

From atelszewski at gmail.com  Mon Nov  7 12:05:27 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 7 Nov 2016 13:05:27 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
 
Message-ID: <94d367fe-fd70-5808-ad54-77366c5139fc@gmail.com>

On 07/11/16 12:35, Andreas Guldstrand wrote:
> Another thread proposed allowing markdown-like sections in the READMEs
> and standardising on how to format the README for each slackbuild
> according to that, which would be fine IMO as it's still very readable
> in a text editor; the markdown section tagging is very easy to read.
>

I don't like anything else than pure text going into README, markdown is 
no different.
Yet I would agree on that and my eyes would have to get used to it :-)

> But adding semantics for individual env options and optional
> dependencies in the README strikes me as a horrible idea. Not only
> would it be absolute hell for any machine to parse and be extremely
> prone to syntax errors from the author (it's a README! SYNTAX
> ERRORS????), but it would also look like utter s**te in a text editor.
>

The syntax I proposed, was just proposal.
Maybe someone can come up with something much better and cleaner.
And the syntax would be checked at submission time.

> On 7 November 2016 at 12:14, Andrzej Telszewski  wrote:
>> Hi,
>>
>> I haven't slept too long and came up with the following idea
>> (this assumes that we do *somehow* agree on some tags in README):
>>
>>
>> The following optional, not auto-detected packages enable additional
>> features (you need to install the package and set environment variable):
>>
>> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
>> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
>> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for IEC61883
>> support,
>>
>>
>> The magic behind:
>> we do not modify .info in any way, we just allow willing maintainers (you
>> can choose if you want or not to support the idea) to structure the README
>> in particular way, enclosing optional packages and environment variables in
>> tags.
>>
>> We do it only for simple cases, i.e. if there is dependency that requires
>> choosing between two exclusive ones, of which one depends on another
>> optional package, then we leave it to human for parsing (although it still
>> would be very helpful to be able to click on the optional package to see
>> what is it about).
>>
>> SBo would parse the README to create clickable optional packages.
>> Build tools would do what they have to do to do what they want to do.
>>
>> SBo would allow for README preview, so the maintainer could ensure it's the
>> way he thinks it is.
>> SBo would immediately reject the submission if there was syntax error (yuk,
>> syntax error in README :-^).
>>
>> Subject for improvements :-)
>>

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Mon Nov  7 12:09:03 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 7 Nov 2016 13:09:03 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
 
Message-ID: <569825c1-e8dc-12d1-6283-781cd0e6f1f8@gmail.com>

On 07/11/16 12:38, David Spencer wrote:
>> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
>> > [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
>> > [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for IEC61883
> * No parser exists for this language that you have just invented. Some
> poor fool would have to write that. And it's one of the context
> senstive languages (like HTML) that can't be parsed with regular
> expressions -- see https://en.wikipedia.org/wiki/Chomsky_hierarchy
>

Subject for improvement.

> * It's too complicated for newbies.
>

They might, but don't have to use it, as I suggested.

> * It's going to look ugly in the README, and that really does matter.
>

Subject for improvement :-)

> * It's incomplete: there are packages with option formats that this
> language can't describe. Look at grass. Yet again, I repeat: don't
> propose a solution until you have checked whether it works in the real
> world. You're only ever looking at ffmpeg :(
>
> -D.

As above :-)
I also suggested that, if it gets to complicated, you don't use it.
Handling simple cases is already an improvement.

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Mon Nov  7 12:13:33 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 7 Nov 2016 13:13:33 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <2edbc6af-5abc-c610-9ab2-3763ef4b2415@websafe.pl>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
 <2edbc6af-5abc-c610-9ab2-3763ef4b2415@websafe.pl>
Message-ID: 

On 07/11/16 12:50, Thomas Szteliga wrote:
> On 11/07/2016 12:14 PM, Andrzej Telszewski wrote:
>> I haven't slept too long and came up with the following idea
>> (this assumes that we do *somehow* agree on some tags in README):
>> The following optional, not auto-detected packages enable additional
>> features (you need to install the package and set environment variable):
>> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
>> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
>> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for
>> IEC61883 support,
>
>
> IMVHO that's way too complicated.
>

Let's improve and simplify! :-)

>
> My suggestion:
>
> OPTIONAL=libass,libbluray,libiec61883,libavc1394
>

This might be error prone, i.e. it might differ from README.
And requires changes to .info, whereas what I suggested, does not.

Also, as it was mentioned before, it would mentally force admins to 
check it. We don't want to force admins to do anything :-)

> Slackbuilds could simply enable/disable optional deps
> by checking if the defined package is available in /var/log/packages.
>

I don't think it's gonna happen.

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Mon Nov  7 12:25:24 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Nov 2016 19:25:24 +0700
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
Message-ID: <0d2da3ff-71c1-78ea-8cf0-5df714392499@slackbuilds.org>

> I like the mono font for README, but I use a large font and for me lines
> are wrapped after 58 symbols.
> 
> On the other hand, the text is a narrow strip on my screen (1920x1200).
> Could it be possible to let the text use all available space in width?

We will use the assumption users use default settings as most people do.
It's nearly impossible to accomodate every user's setting for their
browser preferences :)

Also, since different people have different settings, i  think it would
be good to include a screenshot link so that others can see how it's
seen on other people's computer.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From alik at ejik.org  Mon Nov  7 12:54:53 2016
From: alik at ejik.org (Alexander Verbovetsky)
Date: Mon, 07 Nov 2016 15:54:53 +0300
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <0d2da3ff-71c1-78ea-8cf0-5df714392499@slackbuilds.org>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <0d2da3ff-71c1-78ea-8cf0-5df714392499@slackbuilds.org>
Message-ID: <1478523293.3444255.779796329.267CB269@webmail.messagingengine.com>

> Also, since different people have different settings, i  think it
> would be good to include a screenshot link so that others can see how
> it's seen on other people's computer.

This is mine: http://ejik.org/q/SBo-README-slalik-0.jpg

Best regards,
Alexander

From yth at ythogtha.org  Mon Nov  7 12:57:59 2016
From: yth at ythogtha.org (Ythogtha)
Date: Mon, 7 Nov 2016 13:57:59 +0100
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
Message-ID: <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>

> Hello,
> 
> I like the mono font for README, but I use a large font and for me lines
> are wrapped after 58 symbols.
> 
> On the other hand, the text is a narrow strip on my screen (1920x1200).
> Could it be possible to let the text use all available space in width?
> 
> If it's not feasible, maybe someone can suggest me what to put in my
> firefox's chrome/userContent.css to archive the same result?
> 
> Thank you in advance!

Put that style, it'll break a little the middle part, but not much, it'll be
larger :
#include div#wrap {
    background-color: #fff;
    margin-: 0 -100px;
    width: 910px;
}
If you want even larger, replace the -100px in the margin by a larger number,
double its value, add it to 710 and that's your new width, example :
#include div#wrap {
    background-color: #fff;
    margin-: 0 -200px;
    width: 1110px;
}

-- 
Arnaud 

From willysr at slackbuilds.org  Mon Nov  7 13:25:54 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 7 Nov 2016 20:25:54 +0700
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <1478523293.3444255.779796329.267CB269@webmail.messagingengine.com>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <0d2da3ff-71c1-78ea-8cf0-5df714392499@slackbuilds.org>
 <1478523293.3444255.779796329.267CB269@webmail.messagingengine.com>
Message-ID: <081a8172-3399-0513-0ecf-36fdc1cd5597@slackbuilds.org>

> This is mine: http://ejik.org/q/SBo-README-slalik-0.jpg

here's mine with same package
http://imgur.com/a/smIYx


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From alik at ejik.org  Mon Nov  7 14:36:14 2016
From: alik at ejik.org (Alexander Verbovetsky)
Date: Mon, 07 Nov 2016 17:36:14 +0300
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
Message-ID: <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>

On Mon, Nov 7, 2016, at 15:57, Ythogtha wrote:
> Put that style, it'll break a little the middle part, but not much, it'll
> be
> larger :
> #include div#wrap {
>     background-color: #fff;
>     margin-: 0 -100px;
>     width: 910px;
> }
> If you want even larger, replace the -100px in the margin by a larger
> number,
> double its value, add it to 710 and that's your new width, example :
> #include div#wrap {
>     background-color: #fff;
>     margin-: 0 -200px;
>     width: 1110px;
> }

Thank you very much for the idea!

I modified it to the following code that works perfectly in
chrome/userContent.css:

/* 
 * Force SBo to be wider
 */
@-moz-document domain(slackbuilds.org) {
  #parent, #include div#wrap {
    width: 950px  !important;
    background-color: #fff  !important; }
}

Best regards,
Alexander

From erik at slackbuilds.org  Mon Nov  7 16:01:02 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Mon, 7 Nov 2016 10:01:02 -0600
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
Message-ID: <20161107100102.76d7a668@shaggy.doo>

On Mon, 7 Nov 2016 12:14:39 +0100
Andrzej Telszewski  wrote:

> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for 
> IEC61883 support,

My eyes! The goggles do nothing!


-- 
Erik

From atelszewski at gmail.com  Mon Nov  7 16:40:32 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 7 Nov 2016 17:40:32 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: <20161107100102.76d7a668@shaggy.doo>
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 <1eb07557-bc8d-cc39-e52a-153286afab5c@gmail.com>
 <20161107100102.76d7a668@shaggy.doo>
Message-ID: <2f5096ae-a639-05a9-6429-b559c3afc486@gmail.com>

On 07/11/16 17:01, Erik Hanson wrote:
> On Mon, 7 Nov 2016 12:14:39 +0100
> Andrzej Telszewski  wrote:
>
>> [opt] libass, [env] ASS=yes|no [/opt], for ASS support,
>> [opt] libbluray, [env] BLURAY=yes|no [/opt], for BLURAY support,
>> [opt] libiec61883, libavc1394, [env] IEC61883=yes|no [/opt], for
>> IEC61883 support,
>
> My eyes! The goggles do nothing!
>
>

:-^

-- 
Best regards,
Andrzej Telszewski

From slackbuilds at schoepfer.info  Tue Nov  8 00:13:03 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Tue, 08 Nov 2016 01:13:03 +0100
Subject: [Slackbuilds-users] OPTIONAL field [was: qemu/spice-gtk and
 usbredir]
In-Reply-To: 
References: <8ecdcaa5-464e-8d9d-25bc-d0c2ee054bb4@websafe.pl>
 <925d920a-c9fb-8f8f-5c18-c6ad45531306@gmail.com>
 <7cc0c577-3771-fb4e-ead5-63d3c29b98c3@websafe.pl>
 <67adde0c-0121-4a98-4d8b-7c6a30f5cf9c@slackbuilds.org>
 <08f58b06-4930-914a-b669-2bfec7d0435b@gmail.com>
 <022eea47-6131-13e8-aed6-a9ee0104d42f@websafe.pl>
 
 
 
 
 <580E2AC4.8050508@schoepfer.info>
 <19564a07-68b5-01f6-c426-2e23ec870818@iinet.net.au>
 <94e37b37-8483-8df1-d2c2-16811746d70d@gmail.com>
 
 <00ec13f8-ac9f-3ec7-c183-fdbd9fa99a65@gmail.com>
 <858969e68c0ea46610818462b00b05da@schoepfer.info>
 
 
Message-ID: <7243a905b2eacc8bc6fd4905f82c8140@schoepfer.info>

> This is why we have such a long thread.
> Everybody has a different idea of OPTIONAL in their own mind, that
> solves different problems.

So here is something like a draft, to make clear what and what for  the 
OPTIONAL= field could be, from my point of view.


=== OPTIONAL= field for .info files on SBo ===

== Purpose ==

It's all about dependencies at compiletime.
After REQUIRED, optional buildtime deps are the next thing
to know if one want to build a package utilizing SBo.
Similar to the REQUIRED field, these optional dependencies should be
rendered as links on https://slackbuilds.org, to make navigation to
the optional dependencies/READMEs more joyful.
Side effect, 3rd-party-tools may parse this new field as easy as the
required-field to improve automation.

== How to implement ==

The README stays as it is, as one still need to know
if the optional deps have to be enabled, or
if these are autodetected.
OPTIONAL= may contain nothing, or one, or more packages that have to 
exist on SBo.
Currently, About 15% of all READMEs/packages contain infos about 
optional packages,
these infos need to be added(most likely by hand, as the READMEs are 
hardly parseabel)
to the corresponding .info-file.
No further optional dependencies have to be researched.
Package maintainers have to keep track, that the new field has correct 
content.
For new submissions, the new field is mandatory.

== example ==

# example for flowblade
OPTIONAL="swh-plugins calf jack-audio-connection-kit"
# website "Optional deps: swh-plugins, calf, jack-audio-connection-kit"


=== OPTIONAL= field for .info-files on SBo (Extended) ===

Like above, but with extended syntax, to give a better overview when 
packages get
a littler more complicated. Also invoking REQUIRED as it might benefit 
from the new syntax by forcing minimum features of the required dep:

== syntax ==

PACKAGE:PACKAGE
# package needs to be build against further optional package

PACKAGE,PACKAGE
# Optional package makes sense only in conjunction with another package

== example ==

# example spice-gtk # compiling against usbredir makes sense only when 
qemu enabled usbredir.
-> OPTIONAL="usbredir,qemu:usbredir libcacard phodav opus"
# website "Optional deps: usbredir and qemu built at least with 
usbredir, libcacard,  phodav, opus"

# example audacious-ffmpeg # have at least opus, celt and lame included 
in ffmpeg
-> REQUIRED="ffmpeg:opus,celt,lame"
# website "This requires: ffmpeg built at least with opus and celt and 
lame"



From atelszewski at gmail.com  Tue Nov  8 01:35:40 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Tue, 8 Nov 2016 02:35:40 +0100
Subject: [Slackbuilds-users] LibreOffice, LOLANGS and dictionaries
Message-ID: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>

Hi,

I would like to ask what LOLANGS is about in LibreOffice.SlackBuild?
Is it only about user interface language?
Or does it influence for example date/time format, currency, etc?

Per 
https://wiki.documentfoundation.org/Development/How_to_build/localized 
it's not clear to me what localized means.

About dictionaries:
I like the way Alien has all the available dictionaries in separate 
packages:
http://www.slackware.com/~alien/slackbuilds/libreoffice/pkg64/14.2/

Is the 
https://slackbuilds.org/repository/14.2/office/libreoffice-langpack/ the 
way to do it in the same manner?

I see that Willy is using different dictionaries tarball:
LibreOffice_5.2.3_Linux_x86_rpm_langpack_en-GB.tar.gz (Willy)
vs
libreoffice-dictionaries-5.2.1.2.tar.xz (Alien)

BTW, If you don't have the answer right now, I'll investigate it on my 
own. But maybe somebody already knows the answer.

Also, LibreOffice README says that I can use hunspell dictionaries.
Do you have any experience with that?
Are they better in any way?
Or are they the same thing as the dictionaries built by Alien?

LibreOffice README correction:
- "distionary" should be changed to "dictionary",
- "hunspell.pl" should be changed to "hunspell-pl",
- I would suggest that README contained "ALL" that can be passed to 
LOLANGS (LO wiki mentions it).

SlackBuild correction:
Not having pl in LOLANGS="de es fr id it ja nl vi zh-CN"
is programming error :-^

Thanks!

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Tue Nov  8 02:52:22 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 8 Nov 2016 09:52:22 +0700
Subject: [Slackbuilds-users] LibreOffice, LOLANGS and dictionaries
In-Reply-To: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>
References: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>
Message-ID: <448539ea-fb61-c20c-992d-fdc816f4d6ef@slackbuilds.org>

> I would like to ask what LOLANGS is about in LibreOffice.SlackBuild?
> Is it only about user interface language?
> Or does it influence for example date/time format, currency, etc?

I think it's already mentioned on the README

support additional languages by overriding the LOLANGS variable, whose
default setting is LOLANGS="de es fr id it ja nl vi zh-CN". Note that
en-US is always added to whatever LOLANGS is set. Thus building with,
for example,
LOLOANGS="de" sh LibreOffice

would build LibreOffice with support for german and US english languages.

There are 2 terms for this: localization and internationalization
Here's a good discussion in SO:
https://stackoverflow.com/questions/506743/localization-and-internationalization-whats-the-difference

> About dictionaries:
> I like the way Alien has all the available dictionaries in separate
> packages:
> http://www.slackware.com/~alien/slackbuilds/libreoffice/pkg64/14.2/
> 
> Is the
> https://slackbuilds.org/repository/14.2/office/libreoffice-langpack/ the
> way to do it in the same manner?
> 
> I see that Willy is using different dictionaries tarball:
> LibreOffice_5.2.3_Linux_x86_rpm_langpack_en-GB.tar.gz (Willy)
> vs
> libreoffice-dictionaries-5.2.1.2.tar.xz (Alien)

what i use is a pre-built packages per language, while alienBOB used the
source to build dictionaries for all languages.
In most cases, you only need a spesific language pack, so that's why the
libreoffice-langpack only build a spesific language.


> SlackBuild correction:
> Not having pl in LOLANGS="de es fr id it ja nl vi zh-CN"
> is programming error :-^

I believe that's one good thing about open source. It evolves from time
to time and adding more languages is one of them. However, maintainers
may not notice every possible development done by upstream. That's why
we love it when people report and make things better :)


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From chris.willing at iinet.net.au  Tue Nov  8 02:56:38 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Tue, 8 Nov 2016 12:56:38 +1000
Subject: [Slackbuilds-users] LibreOffice, LOLANGS and dictionaries
In-Reply-To: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>
References: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>
Message-ID: <0e64471f-486e-aa3d-7e17-655d83ec49de@iinet.net.au>

On 08/11/16 11:35, Andrzej Telszewski wrote:
> Hi,
>
> I would like to ask what LOLANGS is about in LibreOffice.SlackBuild?
> Is it only about user interface language?
> Or does it influence for example date/time format, currency, etc?
>
> Per
> https://wiki.documentfoundation.org/Development/How_to_build/localized
> it's not clear to me what localized means.
>
If you were to run LibreOffice itself, you would find (in 
Options->Language Settings) that you are able to independently set these 
items. The language settings available are, as you might expect, those 
specified in the LOLANGS variable at build time. Other settings in the 
same widget such as Locale, currency have a far greater range of options 
from which to choose. I assume that greater range derives from whatever 
is available on your system.


> About dictionaries:
> I like the way Alien has all the available dictionaries in separate
> packages:
> http://www.slackware.com/~alien/slackbuilds/libreoffice/pkg64/14.2/
>
> Is the
> https://slackbuilds.org/repository/14.2/office/libreoffice-langpack/ the
> way to do it in the same manner?
>
> I see that Willy is using different dictionaries tarball:
> LibreOffice_5.2.3_Linux_x86_rpm_langpack_en-GB.tar.gz (Willy)
> vs
> libreoffice-dictionaries-5.2.1.2.tar.xz (Alien)
>
> BTW, If you don't have the answer right now, I'll investigate it on my
> own. But maybe somebody already knows the answer.
>
In general, the builder knows what language(s) they speak and build 
accordingly by setting LOLANGS if the default value doesn't already 
contain their language.


> Also, LibreOffice README says that I can use hunspell dictionaries.
> Do you have any experience with that?
> Are they better in any way?
Better than what?

> Or are they the same thing as the dictionaries built by Alien?
>
I'm not familiar with how those dictionaries are built/used.

> LibreOffice README correction:
> - "distionary" should be changed to "dictionary",
> - "hunspell.pl" should be changed to "hunspell-pl",
Thanks for spotting those - TODO in next update.

> - I would suggest that README contained "ALL" that can be passed to
> LOLANGS (LO wiki mentions it).
>
Yes, good idea - also TODO in next update.


> SlackBuild correction:
> Not having pl in LOLANGS="de es fr id it ja nl vi zh-CN"
> is programming error :-^
>
Well, the SackBuild actually says:
     LOLANGS=${LOLANGS:-"de es fr id it ja nl vi zh-CN"}
precisely so that a builder can trivially include whatever language(s) 
they want.

chris


From atelszewski at gmail.com  Tue Nov  8 23:20:57 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Wed, 9 Nov 2016 00:20:57 +0100
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
 <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>
Message-ID: 

Hi,

Looks and reads good to me.
Thanks!

-- 
Best regards,
Andrzej Telszewski

From zhu.qunying at gmail.com  Wed Nov  9 01:57:07 2016
From: zhu.qunying at gmail.com (Qun-Ying)
Date: Tue, 8 Nov 2016 17:57:07 -0800
Subject: [Slackbuilds-users] (no subject)
Message-ID: 

-- 
Qun-Ying

From zhu.qunying at gmail.com  Wed Nov  9 02:00:45 2016
From: zhu.qunying at gmail.com (Qun-Ying)
Date: Tue, 8 Nov 2016 18:00:45 -0800
Subject: [Slackbuilds-users] lxdm tcp_listen=1 does not work
Message-ID: 

Hi,

Sorry for sending an empty email previously.

For the lxdm's option tcp_listen=1 no longer works, as X.org now
defaults not to listen on TCP connection, and needs explicitly option
to turn it on.  I attached the lxdm-tcp.diff to add the necessary
function to make it work with new current X.org server.

-- 
Qun-Ying
-------------- next part --------------
Binary files lxdm-0.5.3/src/.lxdm.c.un~ and lxdm-new/src/.lxdm.c.un~ differ
diff -urN lxdm-0.5.3/src/lxdm.c lxdm-new/src/lxdm.c
--- lxdm-0.5.3/src/lxdm.c	2015-11-23 03:15:52.000000000 -0800
+++ lxdm-new/src/lxdm.c	2016-09-30 17:59:09.206381282 -0700
@@ -488,6 +488,9 @@
 	{
 		arg[arc++] = g_strdup("-nolisten");
 		arg[arc++] = g_strdup("tcp");
+	} else {
+		arg[arc++] = g_strdup("-listen");
+		arg[arc++] = g_strdup("tcp");
 	}
 	if(!novtswitch)
 	{

From matteo.bernardini at gmail.com  Wed Nov  9 05:50:43 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Wed, 9 Nov 2016 06:50:43 +0100
Subject: [Slackbuilds-users] lxdm tcp_listen=1 does not work
In-Reply-To: 
References: 
Message-ID: 

2016-11-09 3:00 GMT+01:00 Qun-Ying :
> Hi,
>
> Sorry for sending an empty email previously.
>
> For the lxdm's option tcp_listen=1 no longer works, as X.org now
> defaults not to listen on TCP connection, and needs explicitly option
> to turn it on.  I attached the lxdm-tcp.diff to add the necessary
> function to make it work with new current X.org server.

Hi Qun-Ying,

thanks for the patch!

I think this may be useful also upstream: have you tried contacting
the main developer of lxdm, dgod?

https://git.lxde.org/gitweb/?p=lxde/lxdm.git;a=commit;h=855c090f1330aedc97b9a486dcd0d0b4c7ff4f4e

IMHO you should try pinging him by mail with the diff

Matteo

From zhu.qunying at gmail.com  Wed Nov  9 18:17:38 2016
From: zhu.qunying at gmail.com (Qun-Ying)
Date: Wed, 9 Nov 2016 10:17:38 -0800
Subject: [Slackbuilds-users] lxdm tcp_listen=1 does not work
In-Reply-To: 
References: 
 
Message-ID: 

HI Matteo,

I just sent him an email with the patch.

On Tue, Nov 8, 2016 at 9:50 PM, Matteo Bernardini
 wrote:
> 2016-11-09 3:00 GMT+01:00 Qun-Ying :
>> Hi,
>>
>> Sorry for sending an empty email previously.
>>
>> For the lxdm's option tcp_listen=1 no longer works, as X.org now
>> defaults not to listen on TCP connection, and needs explicitly option
>> to turn it on.  I attached the lxdm-tcp.diff to add the necessary
>> function to make it work with new current X.org server.
>
> Hi Qun-Ying,
>
> thanks for the patch!
>
> I think this may be useful also upstream: have you tried contacting
> the main developer of lxdm, dgod?
>
> https://git.lxde.org/gitweb/?p=lxde/lxdm.git;a=commit;h=855c090f1330aedc97b9a486dcd0d0b4c7ff4f4e
>
> IMHO you should try pinging him by mail with the diff
>
> Matteo
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>



-- 
Qun-Ying

From s.arcus at open-t.co.uk  Thu Nov 10 10:43:14 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Thu, 10 Nov 2016 10:43:14 +0000
Subject: [Slackbuilds-users] EasyRSA - re-submittion - bug fix
Message-ID: <5ed75702-665a-da8f-69da-5e5ff3df1df8@open-t.co.uk>

I need to resubmit the EasyRSA scripts - as I discovered a bug in 
easyrsa.SlackBuild

I tried to use the removal form, but it says easyrsa.tar.gz is not 
pending. I tried to resubmit it, but it says it is pending. I attach the 
corrected one to this post - would it be possible for one of the admins 
to replace the one I submitted earlier, please.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: easyrsa.tar.gz
Type: application/gzip
Size: 2202 bytes
Desc: not available
URL: 

From baildon.research at googlemail.com  Thu Nov 10 12:48:56 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Thu, 10 Nov 2016 12:48:56 +0000
Subject: [Slackbuilds-users] EasyRSA - re-submittion - bug fix
In-Reply-To: <5ed75702-665a-da8f-69da-5e5ff3df1df8@open-t.co.uk>
References: <5ed75702-665a-da8f-69da-5e5ff3df1df8@open-t.co.uk>
Message-ID: 

> I need to resubmit the EasyRSA scripts - as I discovered a bug in
> easyrsa.SlackBuild
>
> I tried to use the removal form, but it says easyrsa.tar.gz is not pending.
> I tried to resubmit it, but it says it is pending. I attach the corrected
> one to this post - would it be possible for one of the admins to replace the
> one I submitted earlier, please.

Hi!  The 'pending' page has a link at the bottom that takes you to
"List of submissions that have been approved and are ready for the
next update" https://slackbuilds.org/ready/ -- the link there next to
easyrsa will show you what I did with it. (In particular I put the
docs in the conventional /usr/doc directory, and I made it 'noarch'.)

Please let me know if there's anything in the approved version that
needs further work.

Cheers
-D.

From atelszewski at gmail.com  Thu Nov 10 19:21:00 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 10 Nov 2016 20:21:00 +0100
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
Message-ID: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>

Hi,

README for msgpack-python is missing information on python3 being 
optional dependency.

This makes some packages depending on msgpack-python not working.

-- 
Best regards,
Andrzej Telszewski

From yalhcru at gmail.com  Thu Nov 10 21:40:03 2016
From: yalhcru at gmail.com (B Watson)
Date: Thu, 10 Nov 2016 16:40:03 -0500
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
 <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>
 
Message-ID: 

Ugh. The new CSS stuff causes lines to break at about 66 characters
for me, so READMEs that use line breaks at 72-75 characters come out
like this:

Blood Crossmatching (formerly known as BloodTC) is a recreation of
Blood
(by Monolith Productions) for EDuke32 to bring all the fun and action
of
Blood to the EDuke32 port. This mod will be more powerful in the
future,
considering EDuke32 keeps getting better and better.

Which I could "fix" by using a smaller font for 
 in my browser, but
it's already as small as it can be and still be readable (to me anyway).

Maybe we were better off before.

From ryan.q at linux.com  Thu Nov 10 22:09:57 2016
From: ryan.q at linux.com (Ryan P.C. McQuen)
Date: Thu, 10 Nov 2016 14:09:57 -0800
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
 <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>
 
 
Message-ID: 

On Thursday, November 10, 2016, B Watson  wrote:

> Ugh. The new CSS stuff causes lines to break at about 66 characters
> for me, so READMEs that use line breaks at 72-75 characters come out
> like this:
>
> Which I could "fix" by using a smaller font for 
 in my browser, but
> it's already as small as it can be and still be readable (to me anyway).
>


Isn't there some room to make the middle column wide enough to work for up
to 72 characters?

It is currently at 710 pixels, and even old and small screens should have
at least 768 pixels of width.


-- 
-Ryan
[ryanpcmcquen.org]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From s.arcus at open-t.co.uk  Fri Nov 11 00:09:48 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Fri, 11 Nov 2016 00:09:48 +0000
Subject: [Slackbuilds-users] EasyRSA - re-submittion - bug fix
In-Reply-To: 
References: <5ed75702-665a-da8f-69da-5e5ff3df1df8@open-t.co.uk>
 
Message-ID: <8cb5ac39-251b-048f-d7cb-0b6bf476eae8@open-t.co.uk>

On 10/11/16 12:48, David Spencer wrote:
>> I need to resubmit the EasyRSA scripts - as I discovered a bug in
>> easyrsa.SlackBuild
>>
>> I tried to use the removal form, but it says easyrsa.tar.gz is not pending.
>> I tried to resubmit it, but it says it is pending. I attach the corrected
>> one to this post - would it be possible for one of the admins to replace the
>> one I submitted earlier, please.
>
> Hi!  The 'pending' page has a link at the bottom that takes you to
> "List of submissions that have been approved and are ready for the
> next update" https://slackbuilds.org/ready/ -- the link there next to
> easyrsa will show you what I did with it. (In particular I put the
> docs in the conventional /usr/doc directory, and I made it 'noarch'.)
>
> Please let me know if there's anything in the approved version that
> needs further work.

That's fine - one of your changes overwrote my mistake :-)

Is there any way of being notified when one of the admins makes changes 
to a package I maintain? I worry that not knowing about it, I might 
overwrite the changes the admin made by re-using my version of the 
script (the version I submitted and have on my computer) when I submit a 
version bump in the future.


From willysr at slackbuilds.org  Fri Nov 11 00:29:12 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 11 Nov 2016 07:29:12 +0700
Subject: [Slackbuilds-users] EasyRSA - re-submittion - bug fix
In-Reply-To: <8cb5ac39-251b-048f-d7cb-0b6bf476eae8@open-t.co.uk>
References: <5ed75702-665a-da8f-69da-5e5ff3df1df8@open-t.co.uk>
 
 <8cb5ac39-251b-048f-d7cb-0b6bf476eae8@open-t.co.uk>
Message-ID: 

> Is there any way of being notified when one of the admins makes changes
> to a package I maintain? I worry that not knowing about it, I might
> overwrite the changes the admin made by re-using my version of the
> script (the version I submitted and have on my computer) when I submit a
> version bump in the future.

You will have to look at the changes at cgit
also make sure to grab the latest tarball everytime you wanted to push
an update or grab it from latest git repository after public update.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From willysr at slackbuilds.org  Fri Nov 11 00:30:05 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 11 Nov 2016 07:30:05 +0700
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
Message-ID: 

> README for msgpack-python is missing information on python3 being
> optional dependency.
> 
> This makes some packages depending on msgpack-python not working.

I think Dimitris added the python3 support directly into the SlackBuild


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From atelszewski at gmail.com  Fri Nov 11 00:37:46 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 11 Nov 2016 01:37:46 +0100
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: 
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
Message-ID: <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>

On 11/11/16 01:30, Willy Sudiarto Raharjo wrote:
>> README for msgpack-python is missing information on python3 being
>> optional dependency.
>>
>> This makes some packages depending on msgpack-python not working.
>
> I think Dimitris added the python3 support directly into the SlackBuild
>

I don't know what you mean by support in SlackBuild?
If python3 is not installed, then version for python3 is not built.
And README does not say about it.

I ran into problems with Attic because of that.

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Fri Nov 11 00:44:21 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Fri, 11 Nov 2016 07:44:21 +0700
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
Message-ID: <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>

> I don't know what you mean by support in SlackBuild?
> If python3 is not installed, then version for python3 is not built.
> And README does not say about it.

The script checks whether python3 is available or not
if it does, it will add python3 build as well.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From erik at slackbuilds.org  Fri Nov 11 00:50:17 2016
From: erik at slackbuilds.org (Erik Hanson)
Date: Thu, 10 Nov 2016 18:50:17 -0600
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
 <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>
 
 
Message-ID: <20161110185017.6f1bb082@shaggy.doo>

On Thu, 10 Nov 2016 16:40:03 -0500
B Watson  wrote:

> Ugh. The new CSS stuff causes lines to break at about 66 characters
> for me, so READMEs that use line breaks at 72-75 characters come out
> like this:
> 
> Blood Crossmatching (formerly known as BloodTC) is a recreation of
> Blood
> (by Monolith Productions) for EDuke32 to bring all the fun and action
> of
> Blood to the EDuke32 port. This mod will be more powerful in the
> future,
> considering EDuke32 keeps getting better and better.
> 
> Which I could "fix" by using a smaller font for 
 in my browser,
> but it's already as small as it can be and still be readable (to me
> anyway).
> 
> Maybe we were better off before.

It's not wrapping for me, there's plenty of room to the right of
the README text for bloodcm. Maybe you have some custom css, custom
font sizes, or need to reset your zoom?


-- 
Erik

From atelszewski at gmail.com  Fri Nov 11 00:49:03 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Fri, 11 Nov 2016 01:49:03 +0100
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
Message-ID: 

On 11/11/16 01:44, Willy Sudiarto Raharjo wrote:
> The script checks whether python3 is available or not
> if it does, it will add python3 build as well.

Exactly, but it's not mentioned in README.

-- 
Best regards,
Andrzej Telszewski

From baildon.research at googlemail.com  Fri Nov 11 01:07:32 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Fri, 11 Nov 2016 01:07:32 +0000
Subject: [Slackbuilds-users] EasyRSA - re-submittion - bug fix
In-Reply-To: <8cb5ac39-251b-048f-d7cb-0b6bf476eae8@open-t.co.uk>
References: <5ed75702-665a-da8f-69da-5e5ff3df1df8@open-t.co.uk>
 
 <8cb5ac39-251b-048f-d7cb-0b6bf476eae8@open-t.co.uk>
Message-ID: 

> Is there any way of being notified when one of the admins makes changes to a
> package I maintain? I worry that not knowing about it, I might overwrite the
> changes the admin made by re-using my version of the script (the version I
> submitted and have on my computer) when I submit a version bump in the
> future.

I'd guess at least half of new submissions are changed in review, so
no, we don't notify, and to save everybody's embarrassment those
changes are not public. It's good if you can check the approved
version some time after it leaves 'pending', because reviewers make
mistakes, but that's not a Rule :)

We have always said that you should get the latest version from the
repo before updating. But many people fail to do that, and it is
difficult to surprise us by updating the wrong version. We use 'git
diff' to examine your changes.

-D.

From yalhcru at gmail.com  Fri Nov 11 03:21:08 2016
From: yalhcru at gmail.com (B Watson)
Date: Thu, 10 Nov 2016 22:21:08 -0500
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: <20161110185017.6f1bb082@shaggy.doo>
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
 <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>
 
 
 <20161110185017.6f1bb082@shaggy.doo>
Message-ID: 

On 11/10/16, Erik Hanson  wrote:

> It's not wrapping for me, there's plenty of room to the right of
> the README text for bloodcm. Maybe you have some custom css, custom
> font sizes, or need to reset your zoom?

Yes, I increased the minimum font size in firefox ages ago, to a size
that I can actually read without squinting.

710 pixels / 80 columns would be around 9px wide. Same as the IBM
Monochrome Adaptor from 1981. But modern monitors have a lot smaller
dot pitch than the ones from 1981...

An annoying thing about the web (not singling out SBo site here) is
columnar layouts. My monitor's 1920 pixels wide, but those READMEs
only take up 710 pixels, or less than half the horizontal resolution,
with 2 huge columns on either side wasting space. Lot of stuff like that
out there.

Not a web designer, so I don't have a fix for it. Just venting.

From slackbuilds at schoepfer.info  Fri Nov 11 08:35:59 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Fri, 11 Nov 2016 09:35:59 +0100
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: 
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
 
Message-ID: <582582EF.90705@schoepfer.info>

On 11.11.2016 01:49, Andrzej Telszewski wrote:
> On 11/11/16 01:44, Willy Sudiarto Raharjo wrote:
>> The script checks whether python3 is available or not
>> if it does, it will add python3 build as well.
>
> Exactly, but it's not mentioned in README.

The question is:
Should optional deps be mentioned in README, also if they
are autodetected?
I feel: yes

Sorry if it is already documented somewhere, and i failed to see it.

Johannes









From s.arcus at open-t.co.uk  Fri Nov 11 09:39:27 2016
From: s.arcus at open-t.co.uk (Sebastian Arcus)
Date: Fri, 11 Nov 2016 09:39:27 +0000
Subject: [Slackbuilds-users] EasyRSA - re-submittion - bug fix
In-Reply-To: 
References: <5ed75702-665a-da8f-69da-5e5ff3df1df8@open-t.co.uk>
 
 <8cb5ac39-251b-048f-d7cb-0b6bf476eae8@open-t.co.uk>
 
Message-ID: 


On 11/11/16 01:07, David Spencer wrote:
>> Is there any way of being notified when one of the admins makes changes to a
>> package I maintain? I worry that not knowing about it, I might overwrite the
>> changes the admin made by re-using my version of the script (the version I
>> submitted and have on my computer) when I submit a version bump in the
>> future.
>
> I'd guess at least half of new submissions are changed in review, so
> no, we don't notify, and to save everybody's embarrassment those
> changes are not public. It's good if you can check the approved
> version some time after it leaves 'pending', because reviewers make
> mistakes, but that's not a Rule :)
>
> We have always said that you should get the latest version from the
> repo before updating. But many people fail to do that, and it is
> difficult to surprise us by updating the wrong version. We use 'git
> diff' to examine your changes.

That's great - thank you. I wasn't aware of the above. I've made a 
mental note to always download the latest tarball from SBo before 
updating my scripts!

From thedoogster at gmail.com  Fri Nov 11 16:08:35 2016
From: thedoogster at gmail.com (Doogster)
Date: Fri, 11 Nov 2016 08:08:35 -0800
Subject: [Slackbuilds-users] Suggestion: monospace font for README
In-Reply-To: 
References: <2ea9bacf-3694-7ec5-077e-6f49217016fa@gmail.com>
 <20161106135618.08f71022@shaggy.doo>
 
 <20161106151108.0e6b4f7f@shaggy.doo>
 
 
 
 
 
 <1478519646.3429026.779733817.78990DC7@webmail.messagingengine.com>
 <20161107135759.d322f56fe0af583e0210f5fb@ythogtha.org>
 <1478529374.3470010.779905761.2F6764BB@webmail.messagingengine.com>
 
 
 <20161110185017.6f1bb082@shaggy.doo>
 
Message-ID: 

It's extremely common for software development projects to mandate maximum
line lengths as part of their coding standards. I suggest that SBo picks a
number that would look good without X, in a console with a "vga"
framebuffer, and then demands that contributors follow it.

On Thursday, 10 November 2016, B Watson  wrote:

> On 11/10/16, Erik Hanson > wrote:
>
> > It's not wrapping for me, there's plenty of room to the right of
> > the README text for bloodcm. Maybe you have some custom css, custom
> > font sizes, or need to reset your zoom?
>
> Yes, I increased the minimum font size in firefox ages ago, to a size
> that I can actually read without squinting.
>
> 710 pixels / 80 columns would be around 9px wide. Same as the IBM
> Monochrome Adaptor from 1981. But modern monitors have a lot smaller
> dot pitch than the ones from 1981...
>
> An annoying thing about the web (not singling out SBo site here) is
> columnar layouts. My monitor's 1920 pixels wide, but those READMEs
> only take up 710 pixels, or less than half the horizontal resolution,
> with 2 huge columns on either side wasting space. Lot of stuff like that
> out there.
>
> Not a web designer, so I don't have a fix for it. Just venting.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org 
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From kjhambrick at gmail.com  Fri Nov 11 20:12:22 2016
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Fri, 11 Nov 2016 14:12:22 -0600
Subject: [Slackbuilds-users] ARCH Patch for flashplayer-plugin.SlackBuild
Message-ID: 

Robbie / All --

Slight Mod to flashplayer-plugin.SlackBuild to allow ARCH=override on
multilib systems.

Tested on Slackware64 14.2 + Multilib.

Both ARCH=i386 and ARCH=x86_64 work fine ...

Not sure what would make sense but maybe a BLURB in the README would be
warranted as well ?

Thanks !

-- kjh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
-------------- next part --------------
--- flashplayer-plugin.SlackBuild.orig	2016-10-29 02:58:39.870661303 -0500
+++ flashplayer-plugin.SlackBuild	2016-11-11 09:22:31.475355587 -0600
@@ -27,11 +27,14 @@
 
 VERS_MAJ=$(printf $VERSION | cut -d. -f1)
 
-case "$( uname -m )" in
-  i?86) ARCH=i386 ;;
-  arm*) ARCH=arm ;;
-     *) ARCH=$( uname -m ) ;;
-esac
+if [ "$ARCH" = "" ]
+then
+  case "$( uname -m )" in
+    i?86) ARCH=i386 ;;
+    arm*) ARCH=arm ;;
+       *) ARCH=$( uname -m ) ;;
+  esac
+fi
 
 if [ "$ARCH" = "x86_64" ]; then
   LIBDIRSUFFIX="64"

From idlemoor at slackbuilds.org  Fri Nov 11 21:23:37 2016
From: idlemoor at slackbuilds.org (David Spencer)
Date: Fri, 11 Nov 2016 21:23:37 +0000
Subject: [Slackbuilds-users] Updates - 20161111.1
Message-ID: 

Thanks to all our contributors :)

Fri Nov 11 20:46:51 UTC 2016
academic/engauge: Fixed tarball handling.
academic/fet: Fixed download.
accessibility/xdotool: Update README.
audio/alsamodularsynth: Updated for version 2.1.2.
business/skrooge: updated for version 1.12.5.
desktop/i3: Updated for version 4.13.
desktop/numix-icon-theme-circle: Updated for version 2.0.3.10.
desktop/numix-pack: Updated for version 0.4.2.
desktop/py3status: Fixed md5sum.
desktop/python-specbar: Switch to i586.
development/Editra: Switch to i586.
development/android-tools: Updated for version 7.1.0_r4.
development/atom: Updated for version 1.12.0.
development/dpkg: Updated for version 1.18.12.
development/fossil: Updated for version 1.36.
development/gradle: Fix gradle.csh.
development/idlex: Switch to i586.
development/komodo-ide: Fixed md5sums.
development/love: Updated for version 0.10.2.
development/luarocks: Updated for version 2.4.1.
development/vile: Updated for version 9.8r.
development/xvile: Updated for version 9.8r.
games/0ad-data: Updated for version 0.0.21.
games/0ad: Updated for version 0.0.21.
games/ceferino: Update README.
games/eduke32_hires_pack: Use latest music pack.
games/fuse-emulator: Updated for version 1.3.1.
games/mgba: Fix library location.
games/openmsx-debugger: Added (gui for openMSX debugger).
games/pioneer: Updated for version 20161028.
games/taipan: Update README.
games/tome4: Fixed md5sum.
games/xcowsay: Update README.
games/zelda-roth-se: Fixed desktop file.
gis/gdal: Updated for version 2.1.2.
gis/grass: Updated for version 7.0.5.
gis/libgeotiff: Updated for version 1.4.2.
graphics/Blender: Pass command line args through wrapper
graphics/advancecomp: Switch to i586.
graphics/darktable: Updated for version 2.0.7.
graphics/phototonic: Switch to i586.
graphics/triangulizor: Switch to i586.
graphics/urbanlightscape: Switch to i586.
libraries/CGAL: Updated for version 4.9.
libraries/OpenCSG: Updated for version 1.4.2.
libraries/PDCurses: Switch to i586.
libraries/Pykka: Switch to i586.
libraries/botocore: Updated for version 1.4.70.
libraries/cal3d: Switch to i586.
libraries/dropbox-python: Updated for version 7.1.1.
libraries/gitdb: Switch to i586.
libraries/isodate: Switch to i586.
libraries/jbig2enc: Added (encoder for JBIG2).
libraries/libspectrum: Updated for version 1.3.1.
libraries/live555: Updated for version 2016.11.16
libraries/mercator: Switch to i586.
libraries/musicbrainzngs: Switch to i586.
libraries/pyacoustid: Switch to i586.
libraries/pyqode.widgets: Switch to i586.
libraries/python3-dvdvideo: Fixed tarball handling.
libraries/sparsehash: Fixed tarball handling.
libraries/wfmath: Switch to i586.
libraries/ws4py: Updated for version 0.3.5.
libraries/xcb-util-xrm: Added (XCB utility functions).
libraries/yajl: Switch to i586.
misc/deb2tgz: Fixed tarball handling.
multimedia/ExMplayer: README/slack-desc/script fixups and tweaks
multimedia/OpenLP: Switch to i586.
multimedia/flashplayer-plugin: Updated for version 11.2.202.644.
multimedia/pepperflash-plugin: Updated for version 23.0.0.207.
multimedia/spotify: Updated for version 1.0.42.151.g19de0aa6.
network/RYMTracks: Switch to i586.
network/awscli: Updated for version 1.11.13.
network/claws-mail: Updated for version 3.14.1.
network/easyrsa: Added (CLI utility for managing a PKI CA).
network/flexget: Updated for version 2.5.12.
network/iperf3: Fixed tarball handling.
network/opera-developer: Fix build.
network/opera: Fix build.
network/pubnub-curses: Switch to i586.
network/r8168: Fix doc location.
network/sabnzbd: Updated for version 1.1.1.
network/sslh: Fixed download.
network/ssllabs-scan: Updated for version 1.4.0.
network/tixati: Updated for version 2.48_1.
network/twitter: Switch to i586.
network/vacuum-im: Fixed tarball handling.
network/vivaldi: Updated for version 1.4.589.41.
network/weighmail: Switch to i586.
network/wire: Updated for version 2.11.2670.
network/you-get: Updated for version 0.4.575.
network/youtube-dl-server: Switch to i586.
network/youtube-dl: Updated for version 2016.11.04.
office/LibreOffice: Update README
office/calibre: Updated for version 2.71.0
perl/perl-AnyEvent-I3: Switch to i586.
perl/perl-AnyEvent: Updated for version 7.13.
perl/perl-CGI: Updated for version 4.35.
perl/perl-Math-BigInt: Updated for version 1.999727.
perl/perl-Math-Decimal64: Fixed md5sum.
perl/perl-Math-GMPq: Updated for version 0.42.
python/APScheduler: Updated for version 3.3.0.
python/Baker: Switch to i586.
python/Parsley: Added (Parsing and pattern matching in Python).
python/enzyme: Switch to i586.
python/itsdangerous: Switch to i586.
python/jellyfish: Switch to i586.
python/parsel: Switch to i586.
python/pkginfo: Updated for version 1.4.0.
python/prompt_toolkit: Updated for version 1.0.9.
python/pycodestyle: Updated for version 2.1.0.
python/pydot: Fixed docs.
python/python-distro: Updated for version 1.0.1.
python/python-lazy-object-proxy: Switch to i586.
python/python-x11_hash: Fixed download.
python/python2-pythondialog: Switch to i586.
python/sge-pygame: Updated for version 1.4.1.1.
python/terminaltables: Switch to i586.
python/tornado_systemd: Switch to i586.
python/txi2p: Added (I2P bindings for Twisted).
python/txsocksx: Added (Twisted client endpoints for SOCKS{4,4a,5}).
python/txtorcon: Added (Twisted-based Tor controller client).
system/alien: Switch to i586.
system/butterfly: Switch to i586.
system/fish: Updated for version 2.4.0.
system/forkstat: Updated for version 0.01.16.
system/franny: Added (Atari 8-bit disk image utility).
system/fuse-emulator-utils: Added (The Fuse emulator utilities).
system/fzf: Fixed tarball handling.
system/intel-microcode: Updated for version 20161104.
system/iucode_tool: Updated for version 2.1.
system/kitchen-sync: Added (unidirectional database synch).
system/lbench: Updated for version 3.1.
system/letsencrypt: Update renewal instructions.
system/localepurge: Updated for version 0.7.3.4.
system/lsyncd: Fixed tarball handling.
system/nbench: Fixed homepage and download.
system/ossec-agent: Fix exit status, add uid/gid info.
system/ossec-local: Fix exit status, add uid/gid info.
system/ossec-server: Fix exit status, add uid/gid info.
system/pce: Switch to i586.
system/trmaid: Switch to i586.
system/vinterm: Update README.
system/xarchiver: Fixed tarball handling.
system/xen: Updated for version 4.7.1.
system/zstd: Updated for version 1.1.1.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: 

From atelszewski at gmail.com  Fri Nov 11 23:10:38 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 12 Nov 2016 00:10:38 +0100
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: <582582EF.90705@schoepfer.info>
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
 
 <582582EF.90705@schoepfer.info>
Message-ID: 

On 11/11/16 09:35, Franzen wrote:
> The question is:
> Should optional deps be mentioned in README, also if they
> are autodetected?
> I feel: yes

Of course they should.
I read READMEs, but please don't make me read SlackBuilds to find out 
optional packages.

When I posted this message, I thought the action was obvious: update the 
README and that's it.

I'm having hard times understanding your points of view.
There is no evil intent here, I just don't understand ;-)

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Fri Nov 11 23:46:46 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 12 Nov 2016 00:46:46 +0100
Subject: [Slackbuilds-users] Updates - 20161111.1
In-Reply-To: 
References: 
Message-ID: <25e45609-4165-9e40-7fcf-5bb9ade8d06c@gmail.com>

On 11/11/16 22:23, David Spencer wrote:
> development/dpkg: Updated for version 1.18.12.

The source code for dpkg 1.18.12:
http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.12.tar.xz

seems to be missing on the server.
(it jumps from 1.18.10 -> 1.18.13)

-- 
Best regards,
Andrzej Telszewski

From klaatu at member.fsf.org  Fri Nov 11 23:53:02 2016
From: klaatu at member.fsf.org (Klaatu)
Date: Sat, 12 Nov 2016 12:53:02 +1300
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: 
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
 
 <582582EF.90705@schoepfer.info>
 
Message-ID: 

On 12/11/16 12:10, Andrzej Telszewski wrote:
> On 11/11/16 09:35, Franzen wrote:
>> The question is:
>> Should optional deps be mentioned in README, also if they
>> are autodetected?
>> I feel: yes
> 
> Of course they should.
> I read READMEs, but please don't make me read SlackBuilds to find out
> optional packages.
> 
> When I posted this message, I thought the action was obvious: update the
> README and that's it.
> 
> I'm having hard times understanding your points of view.
> There is no evil intent here, I just don't understand ;-)
> 

When auto-detection is possible, but an override might be desirable, I
try to mention the choice in the README, and provide an env var for
overrides.

For example, in my build script for luxrender:


By default, this SlackBuild:
1. Attempts to auto-detect where your Blender install is by grepping
/var/log/packages
2. Attempts to install the Blender plugin to that location

If you do not want it to attempt to do this, do:

$ BLENDER=no ./luxrender.SlackBuild

The Blender plugin will be copied to /usr/share/luxrender-VERSION

If you do have Blender, but in a different path than the SlackBuild.org
path,, or not
listed in /var/log/packages for some reason, then you can hardcode the path:

$ BLENDER=/path/to/blender/scripts ./luxrender.SlackBuild

IMPORTANT: Point to your Blender **scripts** directory.


This way the user knows what my logic was when writing the script, and
has the choice between 1) accepting my logic or 2) overriding the
default action per their custom set up.

This is also why I try to use more variable in my scripts than the
template provides (specifically for doc path, man path, and info path);
the default is sane and follows the standard, but overrides are easy for
non-standard setups.

-klaatu

From willysr at slackbuilds.org  Fri Nov 11 23:54:12 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 12 Nov 2016 06:54:12 +0700
Subject: [Slackbuilds-users] Updates - 20161111.1
In-Reply-To: <25e45609-4165-9e40-7fcf-5bb9ade8d06c@gmail.com>
References: 
 <25e45609-4165-9e40-7fcf-5bb9ade8d06c@gmail.com>
Message-ID: <58621935-08d6-ba79-0dc8-6b24f1f3705b@slackbuilds.org>

>> development/dpkg: Updated for version 1.18.12.
> 
> The source code for dpkg 1.18.12:
> http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.12.tar.xz
> 
> seems to be missing on the server.
> (it jumps from 1.18.10 -> 1.18.13)


I guess they update faster than our public update :)

anyway it's now fixed on my branch


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From atelszewski at gmail.com  Sat Nov 12 00:04:02 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 12 Nov 2016 01:04:02 +0100
Subject: [Slackbuilds-users] hunspell-pl source code missing
Message-ID: <4b806bf3-f4f9-fd52-8d73-79d60f93ad15@gmail.com>

Hi,

The source code for hunspell-pl 20160907 is missing upstream:
http://sjp.pl/slownik/ort/

It looks like they do not keep older versions.
It would be worth finding another mirror or hosting the source tarball.

(Bcc-d maintainer).

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Sat Nov 12 00:08:49 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 12 Nov 2016 01:08:49 +0100
Subject: [Slackbuilds-users] Updates - 20161111.1
In-Reply-To: <58621935-08d6-ba79-0dc8-6b24f1f3705b@slackbuilds.org>
References: 
 <25e45609-4165-9e40-7fcf-5bb9ade8d06c@gmail.com>
 <58621935-08d6-ba79-0dc8-6b24f1f3705b@slackbuilds.org>
Message-ID: <4aa9236c-17de-b477-78a0-40c150c62105@gmail.com>

On 12/11/16 00:54, Willy Sudiarto Raharjo wrote:
>>> development/dpkg: Updated for version 1.18.12.
>>
>> The source code for dpkg 1.18.12:
>> http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.12.tar.xz
>>
>> seems to be missing on the server.
>> (it jumps from 1.18.10 -> 1.18.13)
>
>
> I guess they update faster than our public update :)
>
> anyway it's now fixed on my branch
>

It's component of no significance, so they can play as much as they want :-^

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Sat Nov 12 00:20:34 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 12 Nov 2016 07:20:34 +0700
Subject: [Slackbuilds-users] Updates - 20161112.1
Message-ID: 

Thanks for B. Watson for his efforts updating most of the READMEs and
slack-desc'

For all maintainers, please make sure you grab the latest tarball or
SlackBuild script files from our website or repository before pushing an
update.

Sat Nov 12 00:00:09 UTC 2016
accessibility/Synkron: Update README, slack-desc.
desktop/Window_Manager_Scripts: Update README.
desktop/ambiance-radiance-flat-colors-gtk-theme: Update README.
desktop/arandr: Update README.
desktop/awoken-icon-theme: Update README, slack-desc.
desktop/bashish: Update README.
desktop/boje-themes: Update README.
desktop/bunsen-themes: Update README, slack-desc.
desktop/catfish: Update README.
desktop/cathexis-suite-themes: Update README, slack-desc.
desktop/conky-manager: Update README.
desktop/dmenu2: Update README, slack-desc.
desktop/dunst: Update README, slack-desc.
desktop/faba-icon-theme: Update README, slack-desc.
desktop/fbmenugen: Update README.
desktop/gnome-menus: Update README.
desktop/imgurbash: Update README.
desktop/moka-icon-theme: Update README.
desktop/moka-minimal: Update README.
desktop/obbrowser: Update README, slack-desc.
desktop/obshutdown: Update README.
desktop/plasma-geek-clock: Update README.
desktop/pspshrink: Update README, slack-desc.
desktop/pyful: Update README, slack-desc.
desktop/quickaccess: Update README.
desktop/s1kls: Update README, slack-desc.
desktop/sawfish: Update README.
desktop/siva-flat-themes: Update README.
desktop/skippy-xd: Update README.
desktop/xipper: Update README, slack-desc.
development/dpkg: Updated for version 1.18.13.
graphics/digikam: Update README.
graphics/freewrl: Update README, slack-desc.
graphics/gimp-plugin-bimp: Update README, slack-desc.
graphics/gmic: Update README.
graphics/luxrender: Update README.
graphics/mitsuba-blender: Update README.
graphics/mitsuba: Update README, slack-desc.
graphics/qcad: Update README.
haskell/haskell-memory: Update README, slack-desc.
libraries/MyGUI: Update README.
libraries/SFGUI: Update README.
libraries/alure: Update README.
libraries/bzrtp: Update README, slack-desc.
libraries/iksemel: Update README.
libraries/libcangjie: Update README.
libraries/libcpuid: Update README.
libraries/libmseed: Update README.
libraries/libpwquality: Update README.
libraries/librapi2: Update README.
libraries/librep: Update README.
libraries/librevisa: Update README.
libraries/libvorbisidec: Update README.
libraries/libxnvctrl: Update README.
libraries/log4cpp: Update README.
libraries/msx264: Update README, slack-desc.
libraries/npth: Update README.
libraries/ogre: Update README.
libraries/pyPEG2: Update README.
libraries/uptime: Update README, slack-desc.
libraries/urdfdom: Update README.
libraries/wxPython3: Update README.
multimedia/Yolo: Update README.
multimedia/cinelerra: Update README.
multimedia/ffmpeg: Update README, slack-desc.
multimedia/kdenlive: Update README, slack-desc.
multimedia/lwks: Update README, slack-desc.
multimedia/tomahawk: Update README.
network/CherryMusic: Update README, slack-desc.
network/NetworkManager-openvpn: Update README.
network/Pafy: Update README.
network/PaleMoon: Update README.
network/cmst: Update README.
network/connman: Update README, slack-desc.
network/dovecot: Update README, slack-desc.
network/filezilla: Updated for version 3.22.2.2.
network/freerapid: Update README.
network/ganglia: Update README, slack-desc.
network/google-cli: Update README.
network/gui-ufw: Update README.
network/hiawatha: Update README.
network/iojs: Update README.
network/ipscan: Update README.
network/jetty: Update README.
network/jitsi: Update README, slack-desc.
network/keybase-client: Update README.
network/linphone: Update README.
network/malheur: Update README.
network/miredo: Update README.
network/modsecurity-apache: Update README.
network/munge: Update README.
network/netdrive-connector: Update README.
network/nginx: Update README, slack-desc.
network/pastebincl: Update README.
network/pidgin-nudge: Update README.
network/pidgin-skypeweb: Update README, slack-desc.
network/purple-facebook: Update README, slack-desc.
network/python-onedrive: Update README.
network/r8168: Update README.
network/rejik: Update README, slack-desc.
network/shorewall-core: Update README, slack-desc.
network/shorewall6: Update README, slack-desc.
network/shorewall: Update README, slack-desc.
network/sks-keyserver: Update README, slack-desc.
network/slowhttptest: Update README.
network/slurm: Update README.
network/suricata: Update README, slack-desc.
network/tightvnc: Update README.
network/vcspull: Update README.
network/vnstat: Update README, slack-desc.
network/weechat: Update README, slack-desc.
network/wmnotify: Update README.
network/x2goserver: Update README.
network/xdman: Update README.
network/you-get: Update README.
network/zmap: Update README.
perl/perl-Config-Simple: Update README, slack-desc.
perl/perl-ExtUtils-Install: Update README.
perl/perl-ExtUtils-ModuleMaker: Update README.
perl/perl-File-Save-Home: Update README.
perl/perl-Module-Install: Update README.
perl/perl-Net-LibIDN: Update README.
perl/perl-PAR-Dist: Update README.
perl/perl-PAR: Update README.
perl/perl-String-PerlIdentifier: Update README.
perl/perl-Sub-Uplevel: Update README.
perl/perl-YAML-Tiny: Update README.
perl/perl-file-basedir: Update README.
perl/perl-file-desktopentry: Update README.
perl/perl-inc-latest: Update README.
perl/perl-linux-desktop-files: Update README, slack-desc.
perl/perl-xml-libxml: Update README, slack-desc.
python/click-plugins: Update README.
python/dbus-python3: Update README.
python/fasteners: Update README, slack-desc.
python/filechunkio: Update README.
python/mnemonic: Update README, slack-desc.
python/nxt-python: Update README, slack-desc.
python/pattern: Update README.
python/pbr: Update README, slack-desc.
python/pluggy: Update README.
python/pydf: Update README.
python/pygoocanvas: Update README, slack-desc.
python/python-MonthDelta: Update README.
python/python3-pyzmq: Update README, slack-desc.
python/requests-toolbelt: Update README.
python/setuptools-scm: Update README, slack-desc.
+--------------------------+
-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From yalhcru at gmail.com  Sat Nov 12 00:33:17 2016
From: yalhcru at gmail.com (B Watson)
Date: Fri, 11 Nov 2016 19:33:17 -0500
Subject: [Slackbuilds-users] Updates - 20161112.1
In-Reply-To: 
References: 
Message-ID: 

On 11/11/16, Willy Sudiarto Raharjo  wrote:

> Thanks for B. Watson for his efforts updating most of the READMEs and
> slack-desc'

Actually that's only about half of the ones that need README updates,
more to come Real Soon Now.

From slackbuilds at schoepfer.info  Sat Nov 12 08:12:52 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 12 Nov 2016 09:12:52 +0100
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: 
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
 
 <582582EF.90705@schoepfer.info>
 
Message-ID: 

On 2016-11-12 00:10, Andrzej Telszewski wrote:
> On 11/11/16 09:35, Franzen wrote:
>> The question is:
>> Should optional deps be mentioned in README, also if they
>> are autodetected?
>> I feel: yes
> 
> Of course they should.
> I read READMEs, but please don't make me read SlackBuilds to find out
> optional packages.
> 
> When I posted this message, I thought the action was obvious: update
> the README and that's it.

Pretty obvious also for me, i don't understand what Willy wanted to say.
To me it sounds like "it is correct this way", but at least it is still 
unclear.

It would be helpful to hear from some SBo-admin something like:
  "Optional dependencies are beyond any policy on SBo, maintainers decide 
what to do with their packages."

or

  "The README of msgpack-python should be updated, we'll put
info on the FAQ, to make clear that involved optional deps are to be 
mentioned in READMEs"

or

  "We'll discuss this internally, wait a bit".


Johannes






From willysr at slackbuilds.org  Sat Nov 12 08:58:20 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 12 Nov 2016 15:58:20 +0700
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: 
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
 
 <582582EF.90705@schoepfer.info>
 
 
Message-ID: <2fb4fc63-6555-e35e-75db-ad9a4962c495@slackbuilds.org>

>>> The question is:
>>> Should optional deps be mentioned in README, also if they
>>> are autodetected?
>>> I feel: yes
>>
>> Of course they should.
>> I read READMEs, but please don't make me read SlackBuilds to find out
>> optional packages.
>>
>> When I posted this message, I thought the action was obvious: update
>> the README and that's it.
> 
> Pretty obvious also for me, i don't understand what Willy wanted to say.
> To me it sounds like "it is correct this way", but at least it is still
> unclear.

Hi,

Yes, it should be updated in the README, but i was hoping that the
maintainer (Dimitris) will do it since he is very active and he is on
this list as well. He also had privileges to make changes directly to
the git as well.

cc'ing Dimitris

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From atelszewski at gmail.com  Sat Nov 12 12:57:25 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Sat, 12 Nov 2016 13:57:25 +0100
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: <2fb4fc63-6555-e35e-75db-ad9a4962c495@slackbuilds.org>
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
 
 <582582EF.90705@schoepfer.info>
 
 
 <2fb4fc63-6555-e35e-75db-ad9a4962c495@slackbuilds.org>
Message-ID: <1d0fdecb-449d-2a01-32bc-90fafeb2cec6@gmail.com>

On 12/11/16 09:58, Willy Sudiarto Raharjo wrote:
>>>> The question is:
>>>> Should optional deps be mentioned in README, also if they
>>>> are autodetected?
>>>> I feel: yes
>>>
>>> Of course they should.
>>> I read READMEs, but please don't make me read SlackBuilds to find out
>>> optional packages.
>>>
>>> When I posted this message, I thought the action was obvious: update
>>> the README and that's it.
>>
>> Pretty obvious also for me, i don't understand what Willy wanted to say.
>> To me it sounds like "it is correct this way", but at least it is still
>> unclear.
>
> Hi,
>
> Yes, it should be updated in the README, but i was hoping that the
> maintainer (Dimitris) will do it since he is very active and he is on
> this list as well. He also had privileges to make changes directly to
> the git as well.
>
> cc'ing Dimitris
>

Thank you :-)

-- 
Best regards,
Andrzej Telszewski

From slackbuilds at schoepfer.info  Sat Nov 12 13:32:13 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 12 Nov 2016 14:32:13 +0100
Subject: [Slackbuilds-users] prosody
Message-ID: 

Hi,

the buildscript of prosody has some glitches and was not updated for 
about 1 1/2 years, there were 2 security-related releases since version 
0.9.8.
I've mailed the current maintainer about that a few days ago,
but didn't get a reply yet.
So i'd like to take over maintenance of prosody, is this ok?

Johannes

From willysr at slackbuilds.org  Sat Nov 12 13:34:54 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 12 Nov 2016 20:34:54 +0700
Subject: [Slackbuilds-users] prosody
In-Reply-To: 
References: 
Message-ID: 

> the buildscript of prosody has some glitches and was not updated for
> about 1 1/2 years, there were 2 security-related releases since version
> 0.9.8.
> I've mailed the current maintainer about that a few days ago,
> but didn't get a reply yet.
> So i'd like to take over maintenance of prosody, is this ok?

Gerardo Zamudio is still active based on git log

perhaps wait a little bit and if it doesn't get updated before next
public update, ping us again on this list


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From d.zlatanidis at gmail.com  Sat Nov 12 14:52:27 2016
From: d.zlatanidis at gmail.com (Dimitris Zlatanidis)
Date: Sat, 12 Nov 2016 16:52:27 +0200
Subject: [Slackbuilds-users] msgpack-python, missing python3 optional dep
In-Reply-To: <1d0fdecb-449d-2a01-32bc-90fafeb2cec6@gmail.com>
References: <0550f28f-b8bf-e561-517a-ca817edaa433@gmail.com>
 
 <0ef29168-f998-cfe9-35cc-c827850700df@gmail.com>
 <118d756f-4cc0-24a3-9142-aea8ee3eca5c@slackbuilds.org>
 
 <582582EF.90705@schoepfer.info>
 
 
 <2fb4fc63-6555-e35e-75db-ad9a4962c495@slackbuilds.org>
 <1d0fdecb-449d-2a01-32bc-90fafeb2cec6@gmail.com>
Message-ID: <7e2eaccc-e416-1dc7-23bb-83b1a6478d05@gmail.com>

Hi,

On Monday I will make the changes in the README file for msgpack-python
and the similar packages


On 11/12/2016 02:57 PM, Andrzej Telszewski wrote:
> On 12/11/16 09:58, Willy Sudiarto Raharjo wrote:
>>>>> The question is:
>>>>> Should optional deps be mentioned in README, also if they
>>>>> are autodetected?
>>>>> I feel: yes
>>>>
>>>> Of course they should.
>>>> I read READMEs, but please don't make me read SlackBuilds to find out
>>>> optional packages.
>>>>
>>>> When I posted this message, I thought the action was obvious: update
>>>> the README and that's it.
>>>
>>> Pretty obvious also for me, i don't understand what Willy wanted to
>>> say.
>>> To me it sounds like "it is correct this way", but at least it is still
>>> unclear.
>>
>> Hi,
>>
>> Yes, it should be updated in the README, but i was hoping that the
>> maintainer (Dimitris) will do it since he is very active and he is on
>> this list as well. He also had privileges to make changes directly to
>> the git as well.
>>
>> cc'ing Dimitris
>>
>
> Thank you :-)
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From edps.mundognu at gmail.com  Sat Nov 12 22:30:48 2016
From: edps.mundognu at gmail.com (Edinaldo)
Date: Sat, 12 Nov 2016 20:30:48 -0200
Subject: [Slackbuilds-users] Updates - 20161111.1
Message-ID: 

About dpkg:

It seems that this week this package has been updated a few times,
today it is already in version 1.18.14:

http://repo.cure.edu.uy/debian/pool/main/d/dpkg/
http://debian.salud.gob.sv/debian/pool/main/d/dpkg/

* and version 1.18.12 was apparently deleted.

About version 1.18.14...

source: http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.14.tar.xz
md5sum: f8f86236d9c52785b26b0f831d09975e

Thanks,

Edinaldo.

From willysr at slackbuilds.org  Sun Nov 13 00:27:17 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 13 Nov 2016 07:27:17 +0700
Subject: [Slackbuilds-users] Updates - 20161111.1
In-Reply-To: 
References: 
Message-ID: <835a9b34-2233-de2d-e560-631e6a798742@slackbuilds.org>

> About dpkg:
> 
> It seems that this week this package has been updated a few times,
> today it is already in version 1.18.14:
> 
> http://repo.cure.edu.uy/debian/pool/main/d/dpkg/
> http://debian.salud.gob.sv/debian/pool/main/d/dpkg/
> 
> * and version 1.18.12 was apparently deleted.
> 
> About version 1.18.14...
> 
> source: http://http.debian.net/debian/pool/main/d/dpkg/dpkg_1.18.14.tar.xz
> md5sum: f8f86236d9c52785b26b0f831d09975e

Hm... so i think it's better to host it somewhere public so it will not
be a broken link after few days


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From willysr at slackbuilds.org  Mon Nov 14 09:45:01 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 14 Nov 2016 16:45:01 +0700
Subject: [Slackbuilds-users] hunspell-pl source code missing
In-Reply-To: <4b806bf3-f4f9-fd52-8d73-79d60f93ad15@gmail.com>
References: <4b806bf3-f4f9-fd52-8d73-79d60f93ad15@gmail.com>
Message-ID: <5975efd4-d7cf-f745-b773-d353da45b11d@slackbuilds.org>

> The source code for hunspell-pl 20160907 is missing upstream:
> http://sjp.pl/slownik/ort/
> 
> It looks like they do not keep older versions.
> It would be worth finding another mirror or hosting the source tarball.
> 
> (Bcc-d maintainer).


Fixed in my branch


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From willysr at slackbuilds.org  Mon Nov 14 12:20:39 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 14 Nov 2016 19:20:39 +0700
Subject: [Slackbuilds-users] Updates - 20161114.1
Message-ID: 

Hi

This is an unplanned but important public update as B. Watson (Urchlay)
is working to fix ALL slack-desc to comply our templates.

In the next few days, he will be pushing his work on READMEs. Let's hope
there won't be any conflict during merging.

Big thanks to him who voluntarily do this amazing job in just a couple
of days. There's more than 1800+ commits done by him for slack-desc and
more to come in the next few days.

Maintainers, please make sure to grab the latest tarball from our
repository or grab it from GIT repository (i know, i have said this many
times), but it's important to start from what we have in the server/GIT
repository instead of using your local copy which *may* be out of date
or out of sync with ours.

Mon Nov 14 10:00:56 UTC 2016
academic/GeoGebra: Fix slack-desc.
academic/Kst: Fix slack-desc.
academic/R: Fix slack-desc.
academic/Xyce: Fix slack-desc.
academic/abntex: Fix slack-desc.
academic/amd: Fix slack-desc.
academic/amplifx: Fix slack-desc.
academic/archeopteryx: Fix slack-desc.
academic/armadillo: Fix slack-desc.
academic/artha: Fix slack-desc.
academic/avogadro: Fix slack-desc.
academic/biblesync: Fix slack-desc.
academic/bibletime: Fix slack-desc.
academic/btf: Fix slack-desc.
academic/calcoo: Fix slack-desc.
academic/camd: Fix slack-desc.
academic/cblas: Fix slack-desc.
academic/ccolamd: Fix slack-desc.
academic/chemtool: Fix slack-desc.
academic/cholmod: Fix slack-desc.
academic/colamd: Fix slack-desc.
academic/convertall: Fix slack-desc.
academic/copasi: Fix slack-desc.
academic/csparse: Fix slack-desc.
academic/cxsparse: Fix slack-desc.
academic/engauge: Fix slack-desc.
academic/equalx: Fix slack-desc.
academic/evopedia_qt: Fix slack-desc.
academic/fann: Fix slack-desc.
academic/fet: Fix slack-desc.
academic/fet: Updated for version 5.30.5.
academic/flann: Fix slack-desc.
academic/flashqard: Fix slack-desc.
academic/free42: Fix slack-desc.
academic/freechartgeany: Fix slack-desc.
academic/gaw3: Fix slack-desc.
academic/gcompris: Fix slack-desc.
academic/geda-gaf: Fix slack-desc.
academic/genius: Fix slack-desc.
academic/geomview: Fix slack-desc.
academic/ggobi: Fix slack-desc.
academic/gnucap: Fix slack-desc.
academic/gretl: Fix slack-desc.
academic/grpn: Fix slack-desc.
academic/gtkwave: Fix slack-desc.
academic/gtypist: Fix slack-desc.
academic/iTest: Fix slack-desc.
academic/irsim: Fix slack-desc.
academic/itex2mml: Fix slack-desc.
academic/jugglinglab: Fix slack-desc.
academic/klu: Fix slack-desc.
academic/knime: Fix slack-desc.
academic/ktikz: Fix slack-desc.
academic/labplot2: Fix slack-desc.
academic/ladr: Fix slack-desc.
academic/ldl: Fix slack-desc.
academic/link-grammar: Fix slack-desc.
academic/loggerpro: Fix slack-desc.
academic/mafft: Fix slack-desc.
academic/mathomatic: Fix slack-desc.
academic/maxima: Fix slack-desc.
academic/mendeleydesktop: Fix slack-desc.
academic/metis: Fix slack-desc.
academic/mpmath: Fix slack-desc.
academic/ncbi-blast-plus: Fix slack-desc.
academic/ngspice: Fix slack-desc.
academic/octave: Fix slack-desc.
academic/paml: Fix slack-desc.
academic/parmetis: Fix slack-desc.
academic/patsy: Fix slack-desc.
academic/pcb: Fix slack-desc.
academic/pspp: Fix slack-desc.
academic/pyfits: Fix slack-desc.
academic/qhull: Fix slack-desc.
academic/qtoctave: Fix slack-desc.
academic/rbio: Fix slack-desc.
academic/root: Fix slack-desc.
academic/scipy: Fix slack-desc.
academic/spades: Fix slack-desc.
academic/spqr: Fix slack-desc.
academic/stellarium: Fix slack-desc.
academic/suitesparseconfig: Fix slack-desc.
academic/sword-data-kjv: Fix slack-desc.
academic/sympy: Fix slack-desc.
academic/tabix: Fix slack-desc.
academic/tuxtype2: Fix slack-desc.
academic/umfpack: Fix slack-desc.
academic/veusz: Fix slack-desc.
academic/wmcalc: Fix slack-desc.
academic/xcircuit: Fix slack-desc.
accessibility/Synkron: Fix slack-desc.
accessibility/jpilot: Fix slack-desc.
audio/TiMidity++: Fix slack-desc.
audio/aacplusenc: Fix slack-desc.
audio/aften: Fix slack-desc.
audio/aj-snapshot: Fix slack-desc.
audio/alsaequal: Fix slack-desc.
audio/alsamodularsynth: Fix slack-desc.
audio/ario: Fix slack-desc.
audio/asunder: Fix slack-desc.
audio/atunes: Fix slack-desc.
audio/audacity: Fix slack-desc.
audio/calf: Fix slack-desc.
audio/chuck: Fix slack-desc.
audio/clementine: Fix slack-desc.
audio/clthreads: Fix slack-desc.
audio/clyrics: Fix slack-desc.
audio/coverlovin: Fix slack-desc.
audio/crip: Fix slack-desc.
audio/deadbeef: Fix slack-desc.
audio/decibel-audio-player: Fix slack-desc.
audio/easymp3gain: Fix slack-desc.
audio/easytag: Fix slack-desc.
audio/faad2: Fix slack-desc.
audio/faust: Fix slack-desc.
audio/fst: Fix slack-desc.
audio/gimmix: Fix slack-desc.
audio/gmpc: Fix slack-desc.
audio/gnomad2: Fix slack-desc.
audio/gnump3d: Fix slack-desc.
audio/gvolwheel: Fix slack-desc.
audio/herrie: Fix slack-desc.
audio/hydrogen: Fix slack-desc.
audio/iripdb: Fix slack-desc.
audio/jack2: Fix slack-desc.
audio/jamin: Fix slack-desc.
audio/kid3: Fix slack-desc.
audio/ladspa_sdk: Fix slack-desc.
audio/lash: Fix slack-desc.
audio/libbs2b: Fix slack-desc.
audio/luppp: Fix slack-desc.
audio/lv2file: Fix slack-desc.
audio/milkytracker: Fix slack-desc.
audio/minimodem: Fix slack-desc.
audio/mixxx: Fix slack-desc.
audio/mp3splt-gtk: Fix slack-desc.
audio/mp4tools: Fix slack-desc.
audio/mppenc: Fix slack-desc.
audio/nas: Fix slack-desc.
audio/ncmpcpp: Fix slack-desc.
audio/nero-aac: Fix slack-desc.
audio/non: Fix slack-desc.
audio/ocp: Fix slack-desc.
audio/patchage: Fix slack-desc.
audio/phat: Fix slack-desc.
audio/playmp3list: Fix slack-desc.
audio/pogo: Fix slack-desc.
audio/ponymix: Fix slack-desc.
audio/pulseaudio-ctl: Fix slack-desc.
audio/pyalsaaudio: Fix slack-desc.
audio/qjackctl: Fix slack-desc.
audio/retrovol: Fix slack-desc.
audio/sayonara-player: Fix slack-desc.
audio/sbagen: Fix slack-desc.
audio/schismtracker: Fix slack-desc.
audio/seq24: Fix slack-desc.
audio/sonata: Fix slack-desc.
audio/soundconverter: Fix slack-desc.
audio/spandsp: Fix slack-desc.
audio/specimen: Fix slack-desc.
audio/speex: Fix slack-desc.
audio/streamripper: Fix slack-desc.
audio/swh-plugins: Fix slack-desc.
audio/tagtool: Fix slack-desc.
audio/tuxguitar: Fix slack-desc.
audio/vcf_plugins: Fix slack-desc.
audio/volume.app: Fix slack-desc.
audio/volwheel: Fix slack-desc.
audio/wavbreaker: Fix slack-desc.
audio/whysynth: Fix slack-desc.
audio/wmusic: Fix slack-desc.
audio/xcfa: Fix slack-desc.
audio/xforge: Fix slack-desc.
audio/xmms-scrobbler: Fix slack-desc.
audio/xmms-shn: Fix slack-desc.
audio/xmms2: Fix slack-desc.
business/AssociationSubscribersManager: Fix slack-desc.
business/stansoft: Fix slack-desc.
desktop/Alphacube-GTK: Fix slack-desc.
desktop/LX-Colors-themes: Fix slack-desc.
desktop/QtCurve-KDE4: Fix slack-desc.
desktop/Window_Manager_Scripts: Fix slack-desc.
desktop/afterstep: Fix slack-desc.
desktop/avant-window-navigator: Fix slack-desc.
desktop/awemenugen: Fix slack-desc.
desktop/awn-extras: Fix slack-desc.
desktop/bashish: Fix slack-desc.
desktop/bmpanel2: Fix slack-desc.
desktop/boje-themes: Fix slack-desc.
desktop/bunsen-themes: Fix slack-desc.
desktop/catfish: Fix slack-desc.
desktop/cathexis-suite-themes: Fix slack-desc.
desktop/ccsm: Fix slack-desc.
desktop/cellwriter: Fix slack-desc.
desktop/clipit: Fix slack-desc.
desktop/devilspie: Fix slack-desc.
desktop/dmenu: Fix slack-desc.
desktop/dwm: Fix slack-desc.
desktop/e16: Fix slack-desc.
desktop/elementary-xfce: Fix slack-desc.
desktop/enlightenment: Fix slack-desc.
desktop/evilwm: Fix slack-desc.
desktop/fbpanel: Fix slack-desc.
desktop/fbrowse-tray: Fix slack-desc.
desktop/ffmpegthumbnailer: Fix slack-desc.
desktop/fvwm95: Fix slack-desc.
desktop/glabels: Fix slack-desc.
desktop/grits: Fix slack-desc.
desktop/grun: Fix slack-desc.
desktop/gtk-nodoka-engine: Fix slack-desc.
desktop/gtkhash: Fix slack-desc.
desktop/herbstluftwm: Fix slack-desc.
desktop/i3lock: Fix slack-desc.
desktop/i3pystatus: Fix slack-desc.
desktop/imgurbash: Fix slack-desc.
desktop/kanyremote: Fix slack-desc.
desktop/kover: Fix slack-desc.
desktop/kpartsplugin: Fix slack-desc.
desktop/lumina: Fix slack-desc.
desktop/lxpanel: Fix slack-desc.
desktop/maitreya: Fix slack-desc.
desktop/mimi: Fix slack-desc.
desktop/mousepad: Fix slack-desc.
desktop/musca: Fix slack-desc.
desktop/neutral: Fix slack-desc.
desktop/nitrogen: Fix slack-desc.
desktop/numix-icon-theme-circle: Fix slack-desc.
desktop/numix-icon-theme: Fix slack-desc.
desktop/obapps: Fix slack-desc.
desktop/obconf: Fix slack-desc.
desktop/obkey: Switch to i586.
desktop/obmenu: Fix slack-desc.
desktop/obsession: Fix slack-desc.
desktop/openbox-menu: Fix slack-desc.
desktop/pdfsam: Fix slack-desc.
desktop/pekwm: Fix slack-desc.
desktop/pidgin-window_merge: Added (Window Merge for Pidgin).
desktop/plank: Fix slack-desc.
desktop/plasma-applet-daisy: Fix slack-desc.
desktop/plasma-eyasdp: Fix slack-desc.
desktop/plasma-runner-browsefirefoxbookmarks: Fix slack-desc.
desktop/plasma-widget-menubar: Fix slack-desc.
desktop/pytyle: Fix slack-desc.
desktop/q4wine: Fix slack-desc.
desktop/quadkonsole4: Fix slack-desc.
desktop/razorqt: Fix slack-desc.
desktop/recorditnow: Fix slack-desc.
desktop/rofi: Fix slack-desc.
desktop/rootactions_servicemenu: Fix slack-desc.
desktop/rsl: Fix slack-desc.
desktop/sawfish-session-dialog: Fix slack-desc.
desktop/screenfetch: Fix slack-desc.
desktop/screenkey: Fix slack-desc.
desktop/screensaver-icon: Fix slack-desc.
desktop/searchmonkey: Fix slack-desc.
desktop/siva-flat-themes: Fix slack-desc.
desktop/skippy-xd: Fix slack-desc.
desktop/skulpture: Fix slack-desc.
desktop/slack-wallpapers: Fix slack-desc.
desktop/ssr: Fix slack-desc.
desktop/sun: Fix slack-desc.
desktop/sync-engine: Fix slack-desc.
desktop/thunar-dropbox: Fix slack-desc.
desktop/thunar-thumbnailers: Fix slack-desc.
desktop/tint2: Fix slack-desc.
desktop/uwm: Fix slack-desc.
desktop/velox: Fix slack-desc.
desktop/vim-qt: Fix slack-desc.
desktop/vivacious-colors-gtk-icon-theme: Fix slack-desc.
desktop/vivacious-colors-gtk-theme: Fix slack-desc.
desktop/vwm: Fix slack-desc.
desktop/wbar: Fix slack-desc.
desktop/wmakerconf: Fix slack-desc.
desktop/wmbackground: Fix slack-desc.
desktop/wmblob: Fix slack-desc.
desktop/wmcliphist: Fix slack-desc.
desktop/wmclockmon: Fix slack-desc.
desktop/wmname: Fix slack-desc.
desktop/wmpinboard: Fix slack-desc.
desktop/wmtimer: Fix slack-desc.
desktop/wmweather+: Fix slack-desc.
desktop/wmwebcam: Fix slack-desc.
desktop/wmxss: Fix slack-desc.
desktop/x-tile: Fix slack-desc.
desktop/xed: Fix slack-desc.
desktop/xed: Updated for version 1.2.1.
desktop/xfce4-eyes-plugin: Fix slack-desc.
desktop/xfce4-mount-plugin: Updated for version 0.6.7.
desktop/xfce4-wavelan-plugin: Fix slack-desc.
desktop/xtrascreenhacks: Fix slack-desc.
desktop/xvkbd: Fix slack-desc.
desktop/yawp: Fix slack-desc.
development/CImg: Fix slack-desc.
development/LLgen: Fix slack-desc.
development/ParadisEO: Fix slack-desc.
development/SDL2_gfx: Fix slack-desc.
development/WebStorm: Fix slack-desc.
development/ahven: Fix slack-desc.
development/android-studio: Fix slack-desc.
development/android-tools: Fix slack-desc.
development/apache-ant: Fix slack-desc.
development/apache-jmeter: Fix slack-desc.
development/apache-maven: Fix slack-desc.
development/apitrace: Fix slack-desc.
development/argouml: Fix slack-desc.
development/asl: Fix slack-desc.
development/asm6809: Fix slack-desc.
development/astyle: Fix slack-desc.
development/atom: Fix slack-desc.
development/atom: Updated for version 1.12.2.
development/avra: Fix slack-desc.
development/avrdude: Fix slack-desc.
development/bacon: Fix slack-desc.
development/bashdb: Fix slack-desc.
development/bfg: Fix slack-desc.
development/bluefish: Fix slack-desc.
development/brackets: Fix slack-desc.
development/bvi: Fix slack-desc.
development/cc65: Fix slack-desc.
development/ccl: Fix slack-desc.
development/check: Fix slack-desc.
development/chibi-scheme: Fix slack-desc.
development/chicken: Fix slack-desc.
development/cim: Fix slack-desc.
development/composer: Fix slack-desc.
development/couchdb: Fix slack-desc.
development/cppcms: Fix slack-desc.
development/cppdb: Fix slack-desc.
development/cppunit: Fix slack-desc.
development/cryptoki: Fix slack-desc.
development/cudatoolkit: Fix slack-desc.
development/cunit: Fix slack-desc.
development/curlpp: Fix slack-desc.
development/dao: Fix slack-desc.
development/decklink-sdk: Fix slack-desc.
development/dejagnu: Fix slack-desc.
development/diakonos: Fix slack-desc.
development/dpkg: Updated for version 1.18.14.
development/eagle: Fix slack-desc.
development/eclipse-cpp: Fix slack-desc.
development/eclipse-java: Fix slack-desc.
development/energia: Fix slack-desc.
development/epydoc: Fix slack-desc.
development/eric: Fix slack-desc.
development/erlang-otp: Fix slack-desc.
development/freetds: Fix slack-desc.
development/fsharp: Fix slack-desc.
development/ftjam: Fix slack-desc.
development/fuel: Fix slack-desc.
development/gambit: Fix slack-desc.
development/geany-plugins: Fix slack-desc.
development/geany: Fix slack-desc.
development/gecode: Fix slack-desc.
development/gedit-plugins: Fix slack-desc.
development/generatorrunner: Fix slack-desc.
development/gisto: Fix slack-desc.
development/glade: Fix slack-desc.
development/global: Fix slack-desc.
development/gnats: Fix slack-desc.
development/gnuradio: Fix slack-desc.
development/gnustep-startup: Fix slack-desc.
development/gob2: Fix slack-desc.
development/gplcver: Fix slack-desc.
development/grails: Fix slack-desc.
development/gtest: Fix slack-desc.
development/guile1.8: Fix slack-desc.
development/highlight: Fix slack-desc.
development/hugs98: Fix slack-desc.
development/icemon: Fix slack-desc.
development/icon: Fix slack-desc.
development/idea: Fix slack-desc.
development/ioncube-loader: Fix slack-desc.
development/ipython-mathjax: Fix slack-desc.
development/ipython: Fix slack-desc.
development/jam: Fix slack-desc.
development/javacc: Fix slack-desc.
development/jdk: Fix slack-desc.
development/jeex: Fix slack-desc.
development/julius: Fix slack-desc.
development/kaaedit: Fix slack-desc.
development/kompozer: Fix slack-desc.
development/leo: Fix slack-desc.
development/libxbgi: Fix slack-desc.
development/lighttable: Fix slack-desc.
development/love-legacy080: Fix slack-desc.
development/lua52: Fix slack-desc.
development/lua: Fix slack-desc.
development/luarocks: Fix slack-desc.
development/lwtools: Fix slack-desc.
development/makedepf90: Fix slack-desc.
development/maude: Fix slack-desc.
development/mcu8051ide: Fix slack-desc.
development/medit: Fix slack-desc.
development/meld3: Fix slack-desc.
development/mono-addins: Fix slack-desc.
development/mono: Fix slack-desc.
development/mosml: Fix slack-desc.
development/mphidflash: Fix slack-desc.
development/mtasc: Fix slack-desc.
development/mutagen: Fix slack-desc.
development/mutagen: Updated for version 1.35.1.
development/mysql-workbench: Fix slack-desc.
development/nedit: Fix slack-desc.
development/netbeans: Fix slack-desc.
development/newtonsoft-json: Fix slack-desc.
development/nexus: Fix slack-desc.
development/nickle: Fix slack-desc.
development/npm2tgz: Fix slack-desc.
development/nqp: Fix slack-desc.
development/nsis: Fix slack-desc.
development/nuget: Fix slack-desc.
development/numpy-legacy3: Fix slack-desc.
development/numpy-legacy: Fix slack-desc.
development/numpy3: Fix slack-desc.
development/numpy: Fix slack-desc.
development/omake: Fix slack-desc.
development/omniORBpy: Fix slack-desc.
development/opencvs: Fix slack-desc.
development/parrot: Fix slack-desc.
development/pasdoc: Fix slack-desc.
development/pd-psql: Fix slack-desc.
development/pforth: Fix slack-desc.
development/poedit: Fix slack-desc.
development/portaudio: Fix slack-desc.
development/power-architect: Fix slack-desc.
development/pudb: Fix slack-desc.
development/pycscope: Fix slack-desc.
development/pyenchant: Fix slack-desc.
development/pyvim: Fix slack-desc.
development/qconf: Fix slack-desc.
development/quilt: Fix slack-desc.
development/rakudo: Fix slack-desc.
development/referenceassemblies-pcl: Fix slack-desc.
development/regina-rexx: Fix slack-desc.
development/rmlmmc: Fix slack-desc.
development/rstudio-desktop: Fix slack-desc.
development/ruff: Fix slack-desc.
development/scite: Fix slack-desc.
development/sdcc: Fix slack-desc.
development/shed: Fix slack-desc.
development/shiboken: Fix slack-desc.
development/sloccount: Fix slack-desc.
development/sonarqube: Fix slack-desc.
development/spl: Fix slack-desc.
development/splint: Fix slack-desc.
development/sqldeveloper: Fix slack-desc.
development/squeak-vm: Fix slack-desc.
development/squirrel-sql: Fix slack-desc.
development/src-vcs: Fix slack-desc.
development/staruml: Fix slack-desc.
development/swfmill: Fix slack-desc.
development/textadept: Fix slack-desc.
development/tkdnd: Fix slack-desc.
development/tora: Fix slack-desc.
development/trac: Fix slack-desc.
development/tyrutils-ericw: Fix slack-desc.
development/u-boot-tools: Fix slack-desc.
development/udis86: Fix slack-desc.
development/uncrustify: Fix slack-desc.
development/vala-12: Fix slack-desc.
development/vala: Fix slack-desc.
development/valgrind: Fix slack-desc.
development/vispatch: Fix slack-desc.
development/visual-studio-code: Fix slack-desc.
development/vstudio: Fix slack-desc.
development/xdebug: Fix slack-desc.
development/xsp: Fix slack-desc.
development/xxdiff: Fix slack-desc.
games/0ad-data: Fix slack-desc.
games/0ad: Fix slack-desc.
games/7kaa: Fix slack-desc.
games/KoboDeluxe: Fix slack-desc.
games/Pyfa: Fix slack-desc.
games/SpaceZero: Fix slack-desc.
games/abe: Fix slack-desc.
games/abuse: Fix slack-desc.
games/ace: Fix slack-desc.
games/adom: Fix slack-desc.
games/advancemame: Fix slack-desc.
games/ags: Fix slack-desc.
games/antimicro: Fix slack-desc.
games/ardentryst: Fix slack-desc.
games/arnold-cpc: Fix slack-desc.
games/assaultcube-reloaded: Fix slack-desc.
games/assaultcube: Fix slack-desc.
games/bluemoon: Fix slack-desc.
games/bomberclone: Fix slack-desc.
games/brutalchess: Fix slack-desc.
games/caph: Fix slack-desc.
games/cgames: Fix slack-desc.
games/cgmadness: Fix slack-desc.
games/cgoban: Fix slack-desc.
games/chessx: Fix slack-desc.
games/chocolate_duke3D: Fix slack-desc.
games/chromium-bsu: Fix slack-desc.
games/conquest: Fix slack-desc.
games/cowsay: Fix slack-desc.
games/curseofwar: Fix slack-desc.
games/cutemaze: Fix slack-desc.
games/doomretro: Updated for version 2.3.4.
games/dunelegacy: Fix slack-desc.
games/ecwolf: Fix slack-desc.
games/einstein: Fix slack-desc.
games/enigma: Fix slack-desc.
games/exult: Fix slack-desc.
games/fgo: Fix slack-desc.
games/fillets-ng-data: Fix slack-desc.
games/fillets-ng: Fix slack-desc.
games/flare: Fix slack-desc.
games/foobillardplus: Fix slack-desc.
games/fortune_doctor_who: Fix slack-desc.
games/freedoom: Fix slack-desc.
games/frogatto: Fix slack-desc.
games/frozen-bubble: Fix slack-desc.
games/fuse-emulator: Fix slack-desc.
games/galaxyv2: Fix slack-desc.
games/gemrb: Fix slack-desc.
games/gnubg: Fix slack-desc.
games/gnugo: Fix slack-desc.
games/gnuski: Fix slack-desc.
games/golly: Fix slack-desc.
games/gottet: Fix slack-desc.
games/hedgewars: Fix slack-desc.
games/hnefatafl: Fix slack-desc.
games/instead: Fix slack-desc.
games/jin: Fix slack-desc.
games/kildclient: Fix slack-desc.
games/lbreakout2: Fix slack-desc.
games/libretro-lutro: Fix slack-desc.
games/libretro-reicast: Fix slack-desc.
games/lincity-ng: Fix slack-desc.
games/ltris: Fix slack-desc.
games/lutris: Fix slack-desc.
games/marathon-evil-data: Fix slack-desc.
games/marathon-red-data: Fix slack-desc.
games/mog: Fix slack-desc.
games/mupen64plus: Fix slack-desc.
games/naev: Fix slack-desc.
games/neverball: Fix slack-desc.
games/nuvie: Fix slack-desc.
games/oolite: Fix slack-desc.
games/openarena: Fix slack-desc.
games/openmsx: Fix slack-desc.
games/openmw: Fix slack-desc.
games/openspades: Fix slack-desc.
games/openttd: Fix slack-desc.
games/pcsx2: Fix slack-desc.
games/pengupop: Fix slack-desc.
games/pingus: Fix slack-desc.
games/pokerth: Fix slack-desc.
games/qmc2: Fix slack-desc.
games/qstat: Fix slack-desc.
games/qtsixa: Fix slack-desc.
games/quakeforge: Fix slack-desc.
games/qxw: Fix slack-desc.
games/qzdl: Fix slack-desc.
games/redeclipse: Fix slack-desc.
games/rlvm: Fix slack-desc.
games/rocksndiamonds: Fix slack-desc.
games/rogue: Fix slack-desc.
games/sauerbraten: Fix slack-desc.
games/scid_vs_pc: Fix slack-desc.
games/scummvm: Fix slack-desc.
games/singularity: Fix slack-desc.
games/sokowiz: Fix slack-desc.
games/solarus-quest-editor: Fix slack-desc.
games/solarus: Fix slack-desc.
games/speed-dreams: Fix slack-desc.
games/spring: Fix slack-desc.
games/steam: Fix slack-desc.
games/stockfish: Fix slack-desc.
games/stone_soup: Fix slack-desc.
games/supertux: Fix slack-desc.
games/tintin: Fix slack-desc.
games/tmw: Fix slack-desc.
games/tmwmusic: Fix slack-desc.
games/tome4: Fix slack-desc.
games/tome: Fix slack-desc.
games/transfusion: Fix slack-desc.
games/tuxkart: Fix slack-desc.
games/tuxnes: Fix slack-desc.
games/ut2004: Fix slack-desc.
games/vectoroids: Fix slack-desc.
games/vms-empire: Fix slack-desc.
games/voxelands: Fix slack-desc.
games/warmux: Fix slack-desc.
games/wesnoth: Fix slack-desc.
games/wmquake: Fix slack-desc.
games/wordwarvi: Fix slack-desc.
games/xmahjongg: Fix slack-desc.
games/xonotic: Fix slack-desc.
games/xskat: Fix slack-desc.
games/yetris: Fix slack-desc.
games/zaz: Fix slack-desc.
games/zod-engine: Fix slack-desc.
games/zork: Fix slack-desc.
games/zsxd: Fix slack-desc.
gis/Geohash: Fix slack-desc.
gis/OWSLib: Fix slack-desc.
gis/cartopy: Fix slack-desc.
gis/cligj: Fix slack-desc.
gis/gdal: Fix slack-desc.
gis/geogig-py: Fix slack-desc.
gis/geojson: Fix slack-desc.
gis/geos: Fix slack-desc.
gis/google-earth: Fix slack-desc.
gis/josm: Fix slack-desc.
gis/laszip: Fix slack-desc.
gis/librasterlite: Fix slack-desc.
gis/libspatialite: Fix slack-desc.
gis/merkaartor: Fix slack-desc.
gis/mobac: Fix slack-desc.
gis/navit: Fix slack-desc.
gis/opencpn: Fix slack-desc.
gis/opengrads: Fix slack-desc.
gis/osm2pgrouting: Fix slack-desc.
gis/pdal: Fix slack-desc.
gis/pgsql-ogr-fdw: Fix slack-desc.
gis/pointcloud: Fix slack-desc.
gis/polyline: Fix slack-desc.
gis/postgis: Fix slack-desc.
gis/pyshp: Fix slack-desc.
gis/pyspatialite: Fix slack-desc.
gis/pytrainer: Fix slack-desc.
gis/qlandkartegt: Fix slack-desc.
gis/qmapshack: Fix slack-desc.
gis/saga-gis: Fix slack-desc.
gis/spatialite_gui: Fix slack-desc.
gis/tangogps: Fix slack-desc.
graphics/Alchemy: Fix slack-desc.
graphics/Blender: Updated for version 2.78a
graphics/HotShots: Fix slack-desc.
graphics/aewan: Fix slack-desc.
graphics/autotrace: Fix slack-desc.
graphics/blender: Fix slack-desc.
graphics/brlcad: Fix slack-desc.
graphics/dcraw: Fix slack-desc.
graphics/digikam: Fix slack-desc.
graphics/djview4: Fix slack-desc.
graphics/dvisvgm: Fix slack-desc.
graphics/enblend-enfuse: Fix slack-desc.
graphics/evolus-pencil: Fix slack-desc.
graphics/exif: Fix slack-desc.
graphics/fontforge: Fix slack-desc.
graphics/freewrl: Fix slack-desc.
graphics/gimagereader: Fix slack-desc.
graphics/gimp-feca_hdr-plugin: Fix slack-desc.
graphics/gimp-plugin-bimp: Fix slack-desc.
graphics/gliv: Fix slack-desc.
graphics/gmic: Fix slack-desc.
graphics/gnome-web-photo: Fix slack-desc.
graphics/gpicview: Fix slack-desc.
graphics/graph-easy: Fix slack-desc.
graphics/graphviz: Fix slack-desc.
graphics/gthumb: Fix slack-desc.
graphics/hugin: Fix slack-desc.
graphics/inkscape: Fix slack-desc.
graphics/kamerka: Fix slack-desc.
graphics/kuickshow: Fix slack-desc.
graphics/lcdtest: Fix slack-desc.
graphics/lilypond: Fix slack-desc.
graphics/luminance-hdr: Fix slack-desc.
graphics/makehuman: Fix slack-desc.
graphics/metapixel: Fix slack-desc.
graphics/mftrace: Fix slack-desc.
graphics/mirage: Fix slack-desc.
graphics/mitsuba: Fix slack-desc.
graphics/mtpaint: Fix slack-desc.
graphics/nvidia-cg-toolkit: Fix slack-desc.
graphics/openclipart: Fix slack-desc.
graphics/openimageio: Fix slack-desc.
graphics/optipng: Fix slack-desc.
graphics/pdf2png: Fix slack-desc.
graphics/pdf2svg: Fix slack-desc.
graphics/photivo: Fix slack-desc.
graphics/phototonic: Fix slack-desc.
graphics/pinta: Fix slack-desc.
graphics/potrace: Fix slack-desc.
graphics/qelectrotech: Fix slack-desc.
graphics/rawstudio: Fix slack-desc.
graphics/rawtherapee: Fix slack-desc.
graphics/resynthesizer: Fix slack-desc.
graphics/scantailor: Fix slack-desc.
graphics/screencloud: Fix slack-desc.
graphics/simple-scan: Fix slack-desc.
graphics/simple-scan: Updated for version 3.22.0.1.
graphics/teighafileconverter: Update DOWNLOAD url.
graphics/teighaviewers: Update DOWNLOAD url.
graphics/tesseract: Fix slack-desc.
graphics/textext: Fix slack-desc.
graphics/tkpng: Fix slack-desc.
graphics/ufraw: Fix slack-desc.
graphics/uniconvertor: Fix slack-desc.
graphics/viewnior: Fix slack-desc.
graphics/vips: Fix slack-desc.
graphics/vuescan: Fix slack-desc.
graphics/wavelet-denoise: Fix slack-desc.
graphics/whyteboard: Fix slack-desc.
graphics/xbmbrowser: Fix slack-desc.
graphics/xcalib: Fix slack-desc.
graphics/xmedcon: Fix slack-desc.
graphics/yafaray-blender: Fix slack-desc.
graphics/yafaray: Fix slack-desc.
ham/7plus: Fix slack-desc.
ham/aldo: Fix slack-desc.
ham/aprx: Fix slack-desc.
ham/baudline: Fix slack-desc.
ham/chirp: Fix slack-desc.
ham/cqrlog: Fix slack-desc.
ham/cwdaemon: Fix slack-desc.
ham/demorse: Fix slack-desc.
ham/direwolf: Fix slack-desc.
ham/dxcc: Fix slack-desc.
ham/ebook2cw: Fix slack-desc.
ham/ebook2cwgui: Fix slack-desc.
ham/gridloc: Fix slack-desc.
ham/grig: Fix slack-desc.
ham/psk31lx: Fix slack-desc.
ham/qradiopredict: Fix slack-desc.
ham/qrq: Fix slack-desc.
ham/svxlink-sounds-en_US-heather-16k: Fix slack-desc.
ham/svxlink: Fix slack-desc.
ham/tqsl: Fix slack-desc.
ham/twhamqth: Fix slack-desc.
ham/wxapt: Fix slack-desc.
ham/xanalyser: Fix slack-desc.
ham/xdemorse: Fix slack-desc.
ham/xfhell: Fix slack-desc.
ham/xpsk31: Fix slack-desc.
ham/xwxapt: Fix slack-desc.
haskell/haskell-Crypto: Fix slack-desc.
haskell/haskell-cryptonite: Fix slack-desc.
haskell/haskell-idna: Fix slack-desc.
haskell/haskell-shellish: Fix slack-desc.
libraries/ETL: Fix slack-desc.
libraries/GitPython: Fix slack-desc.
libraries/LucenePlusPlus: Fix slack-desc.
libraries/OpenBLAS: Fix slack-desc.
libraries/VitaMTP: Fix slack-desc.
libraries/activemq-cpp: Fix slack-desc.
libraries/agg: Fix slack-desc.
libraries/allegro: Fix slack-desc.
libraries/ant-contrib: Fix slack-desc.
libraries/appmenu-qt: Fix slack-desc.
libraries/aqbanking: Fix slack-desc.
libraries/atlas: Fix slack-desc.
libraries/backports-ssl-match-hostname: Fix slack-desc.
libraries/bamf: Fix slack-desc.
libraries/batinfo: Fix slack-desc.
libraries/blas: Fix slack-desc.
libraries/boolstuff: Fix slack-desc.
libraries/botocore: Fix slack-desc.
libraries/buddy: Fix slack-desc.
libraries/bullet: Fix slack-desc.
libraries/cal3d: Fix slack-desc.
libraries/ccrtp: Fix slack-desc.
libraries/clalsadrv: Fix slack-desc.
libraries/collada-dom: Fix slack-desc.
libraries/compface: Fix slack-desc.
libraries/compiz-plugins-experimental: Fix slack-desc.
libraries/confuse: Fix slack-desc.
libraries/console_bridge: Fix slack-desc.
libraries/ctemplate: Fix slack-desc.
libraries/db46: Fix slack-desc.
libraries/dbus-sharp-glib: Fix slack-desc.
libraries/dietlibc: Fix slack-desc.
libraries/discogs-client: Fix slack-desc.
libraries/dotconf: Fix slack-desc.
libraries/dropbox-python: Fix slack-desc.
libraries/e_dbus: Fix slack-desc.
libraries/ecore: Fix slack-desc.
libraries/edje: Fix slack-desc.
libraries/eet: Fix slack-desc.
libraries/efreet: Fix slack-desc.
libraries/eina: Fix slack-desc.
libraries/eio: Fix slack-desc.
libraries/embryo: Fix slack-desc.
libraries/enum34: Fix slack-desc.
libraries/evas: Fix slack-desc.
libraries/exempi: Fix slack-desc.
libraries/ffms2: Fix slack-desc.
libraries/fltk: Fix slack-desc.
libraries/fpconst: Fix slack-desc.
libraries/freealut: Fix slack-desc.
libraries/freexl: Fix slack-desc.
libraries/ftgl: Fix slack-desc.
libraries/fuzzylite: Fix slack-desc.
libraries/ganv: Fix slack-desc.
libraries/genshi: Fix slack-desc.
libraries/geshi: Fix slack-desc.
libraries/glfw3: Fix slack-desc.
libraries/glfw: Fix slack-desc.
libraries/gnet: Fix slack-desc.
libraries/goffice0.8: Fix slack-desc.
libraries/goffice: Fix slack-desc.
libraries/gsnmp: Fix slack-desc.
libraries/gtk-aurora-engine: Fix slack-desc.
libraries/gtkdatabox: Fix slack-desc.
libraries/gtkglarea: Fix slack-desc.
libraries/gtkglext: Fix slack-desc.
libraries/gtkhotkey: Fix slack-desc.
libraries/gtksourceview3: Fix slack-desc.
libraries/gts: Fix slack-desc.
libraries/gupnp: Fix slack-desc.
libraries/gwenhywfar: Fix slack-desc.
libraries/hdf: Fix slack-desc.
libraries/hurry-filesize: Fix slack-desc.
libraries/imlib2: Fix slack-desc.
libraries/itcl: Fix slack-desc.
libraries/jai-imageio: Fix slack-desc.
libraries/javacomm: Fix slack-desc.
libraries/jbigkit: Fix slack-desc.
libraries/json-glib: Fix slack-desc.
libraries/lablgtk: Fix slack-desc.
libraries/lame: Fix slack-desc.
libraries/lapack-atlas: Fix slack-desc.
libraries/lapack: Fix slack-desc.
libraries/leptonica: Fix slack-desc.
libraries/libAfterImage: Fix slack-desc.
libraries/libaaio: Fix slack-desc.
libraries/libasr: Fix slack-desc.
libraries/libass: Fix slack-desc.
libraries/libbonoboui: Fix slack-desc.
libraries/libchewing: Fix slack-desc.
libraries/libcitadel: Fix slack-desc.
libraries/libcmis: Fix slack-desc.
libraries/libcryptui: Fix slack-desc.
libraries/libcsv: Fix slack-desc.
libraries/libcuefile: Fix slack-desc.
libraries/libdbusmenu: Fix slack-desc.
libraries/libe-book: Fix slack-desc.
libraries/libearth: Fix slack-desc.
libraries/libeot: Fix slack-desc.
libraries/libesmtp: Fix slack-desc.
libraries/libetpan: Fix slack-desc.
libraries/libexif-gtk: Fix slack-desc.
libraries/libexttextcat: Fix slack-desc.
libraries/libfdk-aac: Fix slack-desc.
libraries/libfsntfs: Fix slack-desc.
libraries/libftdi1: Fix slack-desc.
libraries/libfvde: Fix slack-desc.
libraries/libfwnt: Fix slack-desc.
libraries/libfwsi: Fix slack-desc.
libraries/libg15: Fix slack-desc.
libraries/libg15render: Fix slack-desc.
libraries/libgaiagraphics: Fix slack-desc.
libraries/libgcrypt15: Fix slack-desc.
libraries/libglpng: Fix slack-desc.
libraries/libgltf: Fix slack-desc.
libraries/libgtop: Fix slack-desc.
libraries/libilbc: Fix slack-desc.
libraries/libinstpatch: Fix slack-desc.
libraries/libkqueue: Fix slack-desc.
libraries/libmatroska: Fix slack-desc.
libraries/libmemcached: Fix slack-desc.
libraries/libmirage: Fix slack-desc.
libraries/libmp3splt: Fix slack-desc.
libraries/libmusicbrainz: Fix slack-desc.
libraries/libnxml: Fix slack-desc.
libraries/libofa: Fix slack-desc.
libraries/libofx: Fix slack-desc.
libraries/liboglappth: Fix slack-desc.
libraries/liboop: Fix slack-desc.
libraries/libotr: Fix slack-desc.
libraries/libpff: Fix slack-desc.
libraries/libpseudo: Fix slack-desc.
libraries/libpwquality: Fix slack-desc.
libraries/libqcow: Fix slack-desc.
libraries/libquvi-scripts: Fix slack-desc.
libraries/libqxt: Fix slack-desc.
libraries/librapi2: Fix slack-desc.
libraries/librsync: Fix slack-desc.
libraries/librtfcomp: Fix slack-desc.
libraries/libscrypt: Fix slack-desc.
libraries/libsidplay2: Fix slack-desc.
libraries/libsigscan: Fix slack-desc.
libraries/libsmdev: Fix slack-desc.
libraries/libsmf: Fix slack-desc.
libraries/libsmi: Fix slack-desc.
libraries/libsuinput: Fix slack-desc.
libraries/libsunpinyin: Fix slack-desc.
libraries/libsynce: Fix slack-desc.
libraries/libtelnet: Fix slack-desc.
libraries/libtermkey: Fix slack-desc.
libraries/libu2f-host: Fix slack-desc.
libraries/libunibreak: Fix slack-desc.
libraries/libuv: Fix slack-desc.
libraries/libvhdi: Fix slack-desc.
libraries/libvidcap: Fix slack-desc.
libraries/libviper: Fix slack-desc.
libraries/libvmdk: Fix slack-desc.
libraries/libvorbisidec: Fix slack-desc.
libraries/libvshadow: Fix slack-desc.
libraries/libvslvm: Fix slack-desc.
libraries/libvterm: Fix slack-desc.
libraries/libwebsockets: Fix slack-desc.
libraries/libxfcegui4: Fix slack-desc.
libraries/libxnvctrl: Fix slack-desc.
libraries/libzrtpcpp: Fix slack-desc.
libraries/linphone-srtp: Fix slack-desc.
libraries/live555: Fix slack-desc.
libraries/lksctp-tools: Fix slack-desc.
libraries/lockdev: Fix slack-desc.
libraries/lua-MessagePack: Fix slack-desc.
libraries/lua-cmsgpack: Fix slack-desc.
libraries/lua-lpeg: Fix slack-desc.
libraries/lua-md5: Fix slack-desc.
libraries/luadbi: Fix slack-desc.
libraries/luaexpat: Fix slack-desc.
libraries/luasocket: Fix slack-desc.
libraries/manubulon-snmp-plugins: Fix slack-desc.
libraries/mathgl: Fix slack-desc.
libraries/mdds: Fix slack-desc.
libraries/meanwhile: Fix slack-desc.
libraries/mujs: Fix slack-desc.
libraries/mxml: Updated for version 2.10.
libraries/mysql-connector-python: Fix slack-desc.
libraries/netcdf: Fix slack-desc.
libraries/nextaw: Fix slack-desc.
libraries/npth: Fix slack-desc.
libraries/opal: Fix slack-desc.
libraries/opencv: Fix slack-desc.
libraries/pgtcl-ng: Fix slack-desc.
libraries/php-oci8: Fix slack-desc.
libraries/physfs: Fix slack-desc.
libraries/pies2overrides: Fix slack-desc.
libraries/plib: Fix slack-desc.
libraries/podofo: Fix slack-desc.
libraries/polyclipping: Added (polygon/line clipping & offsetting).
libraries/ptlib: Fix slack-desc.
libraries/ptypes: Fix slack-desc.
libraries/purple-plugin_pack: Fix slack-desc.
libraries/pyPEG2: Fix slack-desc.
libraries/pybloomfiltermmap: Fix slack-desc.
libraries/pymdstat: Fix slack-desc.
libraries/pysendfile: Fix slack-desc.
libraries/python3-PyQt5: Fix slack-desc.
libraries/qt3: Fix slack-desc.
libraries/quazip: Fix slack-desc.
libraries/quesoglc: Fix slack-desc.
libraries/qwt: Fix slack-desc.
libraries/rep-gtk: Fix slack-desc.
libraries/rxtx: Fix slack-desc.
libraries/secp256k1: Fix slack-desc.
libraries/slib: Fix slack-desc.
libraries/squish: Fix slack-desc.
libraries/stfl: Fix slack-desc.
libraries/stk: Fix slack-desc.
libraries/swfdec: Fix slack-desc.
libraries/tkimg: Fix slack-desc.
libraries/tls: Fix slack-desc.
libraries/tolua++: Fix slack-desc.
libraries/tre: Fix slack-desc.
libraries/trilinos: Fix slack-desc.
libraries/unibilium: Fix slack-desc.
libraries/urdfdom: Fix slack-desc.
libraries/urdfdom_headers: Fix slack-desc.
libraries/uuid: Fix slack-desc.
libraries/webkit2gtk: Updated for version 2.14.2.
libraries/webkitgtk3: Fix slack-desc.
libraries/webkitgtk: Fix slack-desc.
libraries/wjelement: Fix slack-desc.
libraries/wvstreams: Fix slack-desc.
libraries/wxSQLite3: Fix slack-desc.
libraries/wxsvg: Fix slack-desc.
libraries/xalan: Fix slack-desc.
libraries/xawplus: Fix slack-desc.
libraries/xcb-util-xrm: Fix slack-desc.
libraries/xerces: Fix slack-desc.
libraries/xforms: Fix slack-desc.
libraries/xlt: Fix slack-desc.
libraries/xmlgen: Fix slack-desc.
libraries/xmlsec: Fix slack-desc.
libraries/xview: Fix slack-desc.
libraries/yaz: Fix slack-desc.
libraries/zsi: Fix slack-desc.
misc/Colormake: Fix slack-desc.
misc/KeePassHttp: Fix slack-desc.
misc/QCMA: Fix slack-desc.
misc/abgx360gui: Fix slack-desc.
misc/bbrun: Fix slack-desc.
misc/bchunk: Fix slack-desc.
misc/boncuk: Fix slack-desc.
misc/boxes: Fix slack-desc.
misc/clawsker: Fix slack-desc.
misc/doclifter: Fix slack-desc.
misc/fcitx-mozc: Fix slack-desc.
misc/fcrackzip: Fix slack-desc.
misc/figlet: Fix slack-desc.
misc/g15composer: Fix slack-desc.
misc/g15daemon: Fix slack-desc.
misc/g15stats: Fix slack-desc.
misc/glogg: Fix slack-desc.
misc/gnome-mime-data: Fix slack-desc.
misc/gourmet: Fix slack-desc.
misc/gprename: Fix slack-desc.
misc/gramps: Fix slack-desc.
misc/grc: Fix slack-desc.
misc/gxmessage: Fix slack-desc.
misc/hoorex: Fix slack-desc.
misc/ibus-skk: Fix slack-desc.
misc/ibus: Fix slack-desc.
misc/iscan-proprietary-drivers: Fix slack-desc.
misc/kasumi: Fix slack-desc.
misc/kcm-fcitx: Fix slack-desc.
misc/keychain: Fix slack-desc.
misc/mdic: Fix slack-desc.
misc/megatunix: Fix slack-desc.
misc/nfoview: Fix slack-desc.
misc/owfs: Fix slack-desc.
misc/par2cmdline: Fix slack-desc.
misc/pinfo: Fix slack-desc.
misc/po4a: Fix slack-desc.
misc/portecle: Fix slack-desc.
misc/rarcrack: Fix slack-desc.
misc/samdump2: Fix slack-desc.
misc/scim-chewing: Fix slack-desc.
misc/sdcv: Fix slack-desc.
misc/spotlighter: Fix slack-desc.
misc/stardict-tools: Fix slack-desc.
misc/sutils: Fix slack-desc.
misc/toilet: Fix slack-desc.
misc/torrentinfo: Fix slack-desc.
misc/utimer: Fix slack-desc.
misc/wcd: Fix slack-desc.
misc/weather: Fix slack-desc.
misc/wmbday: Fix slack-desc.
misc/xca: Fix slack-desc.
misc/xcape: Fix slack-desc.
misc/xclip: Fix slack-desc.
misc/xwinwrap: Fix slack-desc.
misc/yapet: Fix slack-desc.
misc/yara: Fix slack-desc.
misc/ydpdict: Fix slack-desc.
misc/zinnia: Fix slack-desc.
multimedia/DivFix++: Fix slack-desc.
multimedia/ExMplayer: Fix slack-desc.
multimedia/TeamSpeak3: Fix slack-desc.
multimedia/Yolo: Fix slack-desc.
multimedia/aces-dev: Fix slack-desc.
multimedia/aces_container: Fix slack-desc.
multimedia/aegisub: Fix slack-desc.
multimedia/apetag: Fix slack-desc.
multimedia/audiopreview: Fix slack-desc.
multimedia/avidemux: Fix slack-desc.
multimedia/ccxstream: Fix slack-desc.
multimedia/cowbell: Fix slack-desc.
multimedia/cuetools: Fix slack-desc.
multimedia/devedeng: Fix slack-desc.
multimedia/dvd-slideshow: Fix slack-desc.
multimedia/dvdrip: Fix slack-desc.
multimedia/dvdstyler: Fix slack-desc.
multimedia/dvgrab: Fix slack-desc.
multimedia/emoc: Fix slack-desc.
multimedia/exaile: Fix slack-desc.
multimedia/farsight2: Fix slack-desc.
multimedia/farstream: Fix slack-desc.
multimedia/fdkaac: Fix slack-desc.
multimedia/ffmpegyag: Fix slack-desc.
multimedia/flashplayer-plugin: Fix slack-desc.
multimedia/gigedit: Fix slack-desc.
multimedia/glyr: Fix slack-desc.
multimedia/gnash: Fix slack-desc.
multimedia/google-talkplugin: Fix slack-desc.
multimedia/gpac: Fix slack-desc.
multimedia/gpodder: Fix slack-desc.
multimedia/gtick: Fix slack-desc.
multimedia/gtk-recordmydesktop: Fix slack-desc.
multimedia/hexter: Fix slack-desc.
multimedia/huludesktop: Fix slack-desc.
multimedia/iat: Fix slack-desc.
multimedia/kaffeine-mozilla: Fix slack-desc.
multimedia/kaffeine: Fix slack-desc.
multimedia/kdenlive: Fix slack-desc.
multimedia/kino: Fix slack-desc.
multimedia/l-smash: Fix slack-desc.
multimedia/lives: Fix slack-desc.
multimedia/lwks: Fix slack-desc.
multimedia/minitube: Fix slack-desc.
multimedia/mkvtoolnix: Fix slack-desc.
multimedia/mlt: Fix slack-desc.
multimedia/mpv: Fix slack-desc.
multimedia/mythplugins: Fix slack-desc.
multimedia/mythtv: Fix slack-desc.
multimedia/nightingale: Fix slack-desc.
multimedia/obs-studio: Fix slack-desc.
multimedia/oggconvert: Fix slack-desc.
multimedia/openshot: Fix slack-desc.
multimedia/pepperflash-plugin: Fix slack-desc.
multimedia/picard-plugins: Fix slack-desc.
multimedia/pitivi: Fix slack-desc.
multimedia/plex-home-theater: Fix slack-desc.
multimedia/popcorntime: Fix slack-desc.
multimedia/pyradio: Fix slack-desc.
multimedia/qsampler: Fix slack-desc.
multimedia/realplayer: Fix slack-desc.
multimedia/rosa-media-player: Fix slack-desc.
multimedia/schroedinger: Fix slack-desc.
multimedia/sinthgunt: Fix slack-desc.
multimedia/spek: Fix slack-desc.
multimedia/subtitleeditor: Fix slack-desc.
multimedia/tabu_audio_player: Fix slack-desc.
multimedia/telepathy-farstream: Fix slack-desc.
multimedia/telepathy-glib: Fix slack-desc.
multimedia/tivodecode: Fix slack-desc.
multimedia/tstools: Fix slack-desc.
multimedia/tvheadend: Fix slack-desc.
multimedia/umplayer: Fix slack-desc.
multimedia/vobcopy: Fix slack-desc.
multimedia/xjadeo: Fix slack-desc.
multimedia/xmltv: Fix slack-desc.
multimedia/xvid4conf: Fix slack-desc.
multimedia/xvidcore: Fix slack-desc.
network/DarTui: Fix slack-desc.
network/FireWorks: Fix slack-desc.
network/LOIC: Fix slack-desc.
network/PaleMoon: Fix slack-desc.
network/aggregate: Fix slack-desc.
network/aiccu: Fix slack-desc.
network/amap: Fix slack-desc.
network/aoetools: Fix slack-desc.
network/authbind: Fix slack-desc.
network/axel: Fix slack-desc.
network/bip: Fix slack-desc.
network/bottle: Fix slack-desc.
network/bsflite: Fix slack-desc.
network/cgterm: Fix slack-desc.
network/cherokee: Fix slack-desc.
network/choqok: Fix slack-desc.
network/ckermit: Fix slack-desc.
network/claws-mail: Fix slack-desc.
network/clive: Fix slack-desc.
network/comgt: Fix slack-desc.
network/corkscrew: Fix slack-desc.
network/darkstat: Fix slack-desc.
network/davmail: Fix slack-desc.
network/dclib: Fix slack-desc.
network/ddclient: Fix slack-desc.
network/deluge: Fix slack-desc.
network/dianara: Fix slack-desc.
network/dkimproxy: Fix slack-desc.
network/dnstop: Fix slack-desc.
network/dokuwiki: Fix slack-desc.
network/dovecot-pigeonhole: Fix slack-desc.
network/dropbox: Fix slack-desc.
network/easyrsa: Fix slack-desc.
network/eiskaltdcpp: Fix slack-desc.
network/ekiga: Fix slack-desc.
network/emesene: Fix slack-desc.
network/enet: Fix slack-desc.
network/etherape: Fix slack-desc.
network/etherpad-lite: Fix slack-desc.
network/ettercap-NG: Fix slack-desc.
network/exim: Fix slack-desc.
network/fail2ban: Fix slack-desc.
network/fcgiwrap: Fix slack-desc.
network/fping6: Fix slack-desc.
network/fping: Fix slack-desc.
network/freeradius-server: Fix slack-desc.
network/ftp-cloudfs: Fix slack-desc.
network/gajim: Fix slack-desc.
network/ganglia-web: Fix slack-desc.
network/geoipupdate: Fix slack-desc.
network/glusterfs: Fix slack-desc.
network/gns3: Fix slack-desc.
network/googlecl: Fix slack-desc.
network/gq: Fix slack-desc.
network/guacamole-client: Fix slack-desc.
network/guacamole-server: Fix slack-desc.
network/gui-ufw: Fix slack-desc.
network/hamachi: Fix slack-desc.
network/havp: Fix slack-desc.
network/hiawatha: Fix slack-desc.
network/hostsblock: Fix slack-desc.
network/hping3: Fix slack-desc.
network/httping: Fix slack-desc.
network/hydra: Fix slack-desc.
network/ifstatus: Fix slack-desc.
network/ii: Fix slack-desc.
network/imapfilter: Fix slack-desc.
network/iperf3: Fix slack-desc.
network/iperf: Fix slack-desc.
network/ipscan: Fix slack-desc.
network/ipvsadm: Fix slack-desc.
network/jboss-as: Fix slack-desc.
network/kcm_ufw: Fix slack-desc.
network/keybase-client: Fix slack-desc.
network/kfilebox: Fix slack-desc.
network/kismet: Fix slack-desc.
network/kmess: Fix slack-desc.
network/konversation: Fix slack-desc.
network/kvirc: Fix slack-desc.
network/kwakd: Fix slack-desc.
network/leafnode: Fix slack-desc.
network/leechcraft: Fix slack-desc.
network/libdnet: Fix slack-desc.
network/licq: Fix slack-desc.
network/livestreamer: Fix slack-desc.
network/mailman: Fix slack-desc.
network/malheur: Fix slack-desc.
network/megatools: Fix slack-desc.
network/metasploit: Fix slack-desc.
network/mew: Fix slack-desc.
network/milter-greylist: Fix slack-desc.
network/mitter: Fix slack-desc.
network/mldonkey: Fix slack-desc.
network/mod_auth_kerb: Fix slack-desc.
network/mod_chroot: Fix slack-desc.
network/mod_geoip2: Fix slack-desc.
network/modsecurity-apache: Fix slack-desc.
network/monkey: Fix slack-desc.
network/mrtg: Fix slack-desc.
network/msmtp: Fix slack-desc.
network/mumble: Fix slack-desc.
network/museek+: Fix slack-desc.
network/mysecureshell: Fix slack-desc.
network/nagios: Fix slack-desc.
network/nagiosgraph: Fix slack-desc.
network/netcat-openbsd: Fix slack-desc.
network/netcat: Fix slack-desc.
network/nethogs: Fix slack-desc.
network/netperf: Fix slack-desc.
network/netstat-nat: Fix slack-desc.
network/newsbeuter: Fix slack-desc.
network/nfdump: Fix slack-desc.
network/nicotine+: Fix slack-desc.
network/nikto: Fix slack-desc.
network/nmh: Fix slack-desc.
network/noip2: Fix slack-desc.
network/nss-mdns: Fix slack-desc.
network/ntpclient: Fix slack-desc.
network/openconnect: Fix slack-desc.
network/opendchub: Fix slack-desc.
network/opendkim: Fix slack-desc.
network/openl2tp: Fix slack-desc.
network/openntpd: Fix slack-desc.
network/openresolv: Fix slack-desc.
network/openvswitch-utils: Fix slack-desc.
network/opera-developer: Updated for version 43.0.2403.0.
network/opera-legacy: Fix slack-desc.
network/opera: Updated for version 41.0.2353.56.
network/packETH: Fix slack-desc.
network/packit: Fix slack-desc.
network/palemoon: Fix slack-desc.
network/pastebincl: Fix slack-desc.
network/pentadactyl: Fix slack-desc.
network/pflogsumm: Fix slack-desc.
network/pgbouncer: Fix slack-desc.
network/pgl: Fix slack-desc.
network/phodav: Fix slack-desc.
network/pidgin-musictracker: Fix slack-desc.
network/pidgin-otr: Fix slack-desc.
network/pidgin-skypeweb: Fix slack-desc.
network/pidgin-skypeweb: Updated for version 1.2.2.
network/pidgin-sound: Fix slack-desc.
network/pidgin-visnotes: Fix slack-desc.
network/policyd2: Fix slack-desc.
network/polipo: Fix slack-desc.
network/privoxy: Fix slack-desc.
network/proxytunnel: Fix slack-desc.
network/psi: Fix slack-desc.
network/ptokax: Fix slack-desc.
network/pure-ftpd: Fix slack-desc.
network/purple-facebook: Fix slack-desc.
network/pyNeighborhood: Fix slack-desc.
network/pydio-agent: Fix slack-desc.
network/pydio-sync: Fix slack-desc.
network/qbittorrent: Fix slack-desc.
network/quagga: Fix slack-desc.
network/radicale: Fix slack-desc.
network/radvd: Fix slack-desc.
network/retroshare: Fix slack-desc.
network/roger-router: Fix slack-desc.
network/rtl8188eu: Fix slack-desc.
network/scapy: Fix slack-desc.
network/sftp-cloudfs: Fix slack-desc.
network/silc-toolkit: Fix slack-desc.
network/sipp: Fix slack-desc.
network/skype: Fix slack-desc.
network/slack: Fix slack-desc.
network/smcroute: Fix slack-desc.
network/sniffjoke: Fix slack-desc.
network/snmptt: Fix slack-desc.
network/snort: Fix slack-desc.
network/squid: Fix slack-desc.
network/squidGuard: Fix slack-desc.
network/squidanalyzer: Fix slack-desc.
network/sshpass: Fix slack-desc.
network/sslscan: Fix slack-desc.
network/ssmtp: Fix slack-desc.
network/sstp-client: Fix slack-desc.
network/ssvnc: Fix slack-desc.
network/sylpheed: Fix slack-desc.
network/synergy: Fix slack-desc.
network/t38modem: Fix slack-desc.
network/tcpflow: Fix slack-desc.
network/tramp: Fix slack-desc.
network/translate: Fix slack-desc.
network/transmission-remote-gtk: Fix slack-desc.
network/tucan: Fix slack-desc.
network/tunctl: Fix slack-desc.
network/twitter: Fix slack-desc.
network/uTox: Fix slack-desc.
network/udpxy: Fix slack-desc.
network/ufw: Fix slack-desc.
network/unbound: Fix slack-desc.
network/users-agent: Fix slack-desc.
network/uudeview: Fix slack-desc.
network/vacuum-im: Fix slack-desc.
network/valknut: Fix slack-desc.
network/vblade: Fix slack-desc.
network/vde2: Fix slack-desc.
network/verlihub: Fix slack-desc.
network/viber: Fix slack-desc.
network/vidalia: Fix slack-desc.
network/vivaldi: Fix slack-desc.
network/vmware-horizon-client: Fix slack-desc.
network/vpnc: Fix slack-desc.
network/wakeonlan: Fix slack-desc.
network/wavemon: Fix slack-desc.
network/weathercli: Fix slack-desc.
network/webalizer: Fix slack-desc.
network/wildfly: Fix slack-desc.
network/wire: Fix slack-desc.
network/wmget: Fix slack-desc.
network/wmnd: Fix slack-desc.
network/wmnotify: Fix slack-desc.
network/xdman: Fix slack-desc.
network/xinetd: Fix slack-desc.
network/xnetload: Fix slack-desc.
network/yadifa: Fix slack-desc.
network/yoda: Fix slack-desc.
network/znc: Fix slack-desc.
office/abiword: Fix slack-desc.
office/adobe-reader-fontpacks: Fix slack-desc.
office/aigaion: Fix slack-desc.
office/aiksaurus: Fix slack-desc.
office/asymptote: Fix slack-desc.
office/beaver: Fix slack-desc.
office/bookbinder: Fix slack-desc.
office/briss: Fix slack-desc.
office/broffice.org: Fix slack-desc.
office/calcurse: Fix slack-desc.
office/calibre: Fix slack-desc.
office/devtodo: Fix slack-desc.
office/ding: Fix slack-desc.
office/docx2txt: Fix slack-desc.
office/elyxer: Fix slack-desc.
office/epdfview: Fix slack-desc.
office/etmtk: Fix slack-desc.
office/fbreader: Fix slack-desc.
office/flowkeeper: Fix slack-desc.
office/focuswriter: Fix slack-desc.
office/ganttproject: Fix slack-desc.
office/gcal: Fix slack-desc.
office/gnumeric: Fix slack-desc.
office/homebank: Fix slack-desc.
office/hunspell-de: Fix slack-desc.
office/hunspell-pl: Update DOWNLOAD url.
office/jstock: Fix slack-desc.
office/kate-latex-plugin: Fix slack-desc.
office/kbgoffice: Fix slack-desc.
office/kbibtex: Fix slack-desc.
office/kchmviewer-qt: Fix slack-desc.
office/kchmviewer: Fix slack-desc.
office/keepassx: Fix slack-desc.
office/libreoffice-helppack: Fix slack-desc.
office/libreoffice-langpack: Fix slack-desc.
office/libreoffice: Fix slack-desc.
office/lout: Fix slack-desc.
office/lyx: Fix slack-desc.
office/mdbtools: Fix slack-desc.
office/moneydance: Fix slack-desc.
office/notmuch: Fix slack-desc.
office/openoffice.org: Fix slack-desc.
office/org-mode: Fix slack-desc.
office/osmo: Fix slack-desc.
office/paps: Fix slack-desc.
office/pdf2djvu: Fix slack-desc.
office/pdfchain: Fix slack-desc.
office/pdfjam: Fix slack-desc.
office/ps2eps: Fix slack-desc.
office/pstotext: Fix slack-desc.
office/python-gcalcli: Fix slack-desc.
office/rednotebook: Fix slack-desc.
office/referencer: Fix slack-desc.
office/sc-im: Fix slack-desc.
office/scribus: Fix slack-desc.
office/taskd: Fix slack-desc.
office/tasksh: Fix slack-desc.
office/tellico: Fix slack-desc.
office/texlive: Fix slack-desc.
office/texmacs: Fix slack-desc.
office/texworks: Fix slack-desc.
office/timetrap: Fix slack-desc.
office/treesheets: Fix slack-desc.
office/unoconv: Fix slack-desc.
office/verbiste: Fix slack-desc.
office/xmind: Fix slack-desc.
office/xpad: Fix slack-desc.
office/xtrkcad: Fix slack-desc.
perl/mod_perl: Fix slack-desc.
perl/perl-Archive-Zip: Fix slack-desc.
perl/perl-Canary-Stability: Fix slack-desc.
perl/perl-Class-Gomor: Fix slack-desc.
perl/perl-Convert-UU: Fix slack-desc.
perl/perl-Convert-UUlib: Fix slack-desc.
perl/perl-Danga-Socket: Fix slack-desc.
perl/perl-Date-Calc: Fix slack-desc.
perl/perl-Encode-ISO2022: Fix slack-desc.
perl/perl-Encode-JISX0213: Fix slack-desc.
perl/perl-ExtUtils-Install: Fix slack-desc.
perl/perl-ExtUtils-ModuleMaker: Fix slack-desc.
perl/perl-ExtUtils-XSBuilder: Fix slack-desc.
perl/perl-FCGI: Fix slack-desc.
perl/perl-File-Finder: Fix slack-desc.
perl/perl-File-ReadBackwards: Fix slack-desc.
perl/perl-File-Save-Home: Fix slack-desc.
perl/perl-File-Tail: Fix slack-desc.
perl/perl-LWP-Protocol-https: Fix slack-desc.
perl/perl-Locale-Maketext-Lexicon: Fix slack-desc.
perl/perl-Mail-SPF-Query: Fix slack-desc.
perl/perl-MailTools: Fix slack-desc.
perl/perl-Math-Decimal64: Fix slack-desc.
perl/perl-Math-GMPf: Fix slack-desc.
perl/perl-Module-Build: Fix slack-desc.
perl/perl-Module-Install: Fix slack-desc.
perl/perl-Module-ScanDeps: Fix slack-desc.
perl/perl-Mozilla-CA: Fix slack-desc.
perl/perl-Net-DNS-Resolver-Programmable: Fix slack-desc.
perl/perl-Net-Daemon: Fix slack-desc.
perl/perl-Net-Libdnet: Fix slack-desc.
perl/perl-Net-Pcap: Fix slack-desc.
perl/perl-Net-Write: Fix slack-desc.
perl/perl-Number-Bites-Human: Fix slack-desc.
perl/perl-PAR-Dist: Fix slack-desc.
perl/perl-PAR: Fix slack-desc.
perl/perl-PHP-Serialization: Fix slack-desc.
perl/perl-Path-Class: Fix slack-desc.
perl/perl-Readonly: Fix slack-desc.
perl/perl-Sidef: Updated for version 2.33.
perl/perl-Slurp-Tiny: Fix slack-desc.
perl/perl-String-ShellQuote: Fix slack-desc.
perl/perl-Sub-Uplevel: Fix slack-desc.
perl/perl-Sys-Hostname-Long: Fix slack-desc.
perl/perl-Test-Exception: Fix slack-desc.
perl/perl-Test-SharedFork: Fix slack-desc.
perl/perl-Text-CharWidth: Fix slack-desc.
perl/perl-Text-Iconv: Fix slack-desc.
perl/perl-Text-WrapI18N: Fix slack-desc.
perl/perl-Time-Out: Fix slack-desc.
perl/perl-Tree-Simple: Fix slack-desc.
perl/perl-WWW-Curl: Fix slack-desc.
perl/perl-X11-Protocol-Other: Fix slack-desc.
perl/perl-XML-Filter-BufferText: Fix slack-desc.
perl/perl-YAML-Tiny: Fix slack-desc.
perl/perl-ZMQ-Constants: Fix slack-desc.
perl/perl-cairo: Fix slack-desc.
perl/perl-cgi-minimal: Fix slack-desc.
perl/perl-common-sense: Fix slack-desc.
perl/perl-config-general: Fix slack-desc.
perl/perl-data-page-pageset: Fix slack-desc.
perl/perl-extutils-depends: Fix slack-desc.
perl/perl-extutils-makemaker: Fix slack-desc.
perl/perl-extutils-pkgconfig: Fix slack-desc.
perl/perl-file-basedir: Fix slack-desc.
perl/perl-file-desktopentry: Fix slack-desc.
perl/perl-file-listing: Fix slack-desc.
perl/perl-file-mimeinfo: Fix slack-desc.
perl/perl-glib: Fix slack-desc.
perl/perl-gnome2-canvas: Fix slack-desc.
perl/perl-gnome2-gconf: Fix slack-desc.
perl/perl-gnome2-vfs: Fix slack-desc.
perl/perl-gnome2-wnck: Fix slack-desc.
perl/perl-gnome2: Fix slack-desc.
perl/perl-goo-canvas: Fix slack-desc.
perl/perl-gstreamer: Fix slack-desc.
perl/perl-gtk2-imageview: Fix slack-desc.
perl/perl-gtk2: Fix slack-desc.
perl/perl-html-form: Fix slack-desc.
perl/perl-http-cookies: Fix slack-desc.
perl/perl-http-daemon: Fix slack-desc.
perl/perl-http-message: Fix slack-desc.
perl/perl-http-negotiate: Fix slack-desc.
perl/perl-http-response-encoding: Fix slack-desc.
perl/perl-http-server-simple: Fix slack-desc.
perl/perl-linux-desktop-files: Fix slack-desc.
perl/perl-net-ip: Fix slack-desc.
perl/perl-pango: Fix slack-desc.
perl/perl-test-warn: Fix slack-desc.
perl/perl-tree-dagnode: Fix slack-desc.
perl/perl-www-mechanize: Fix slack-desc.
perl/perl-x11-protocol: Fix slack-desc.
python/Flask-Login: Fix slack-desc.
python/Logbook: Fix slack-desc.
python/Markdown: Fix slack-desc.
python/Paver: Fix slack-desc.
python/PyXB: Updated for version 1.2.5.
python/PythonQt: Fix slack-desc.
python/RBTools: Fix slack-desc.
python/affine: Fix slack-desc.
python/artifacts: Fix slack-desc.
python/babel: Fix slack-desc.
python/backports-abc: Fix slack-desc.
python/bencode: Fix slack-desc.
python/bitarray: Fix slack-desc.
python/cairocffi: Fix slack-desc.
python/click-plugins: Fix slack-desc.
python/construct: Fix slack-desc.
python/cssselect: Fix slack-desc.
python/distorm: Fix slack-desc.
python/fabric: Fix slack-desc.
python/fasteners: Fix slack-desc.
python/feedgenerator: Fix slack-desc.
python/flask-paginate: Fix slack-desc.
python/frosted: Fix slack-desc.
python/fudge: Fix slack-desc.
python/funcsigs: Fix slack-desc.
python/gnome-python: Fix slack-desc.
python/gunicorn: Fix slack-desc.
python/hachoir-core: Fix slack-desc.
python/hachoir-metadata: Fix slack-desc.
python/hachoir-parser: Fix slack-desc.
python/itsdangerous: Fix slack-desc.
python/jedi: Fix slack-desc.
python/minidb: Fix slack-desc.
python/monotonic: Fix slack-desc.
python/msgpack-python: Update README.
python/munch: Fix slack-desc.
python/ndg_httpsclient: Fix slack-desc.
python/p4python: Fix slack-desc.
python/pbr: Fix slack-desc.
python/pilkit: Fix slack-desc.
python/pillowfight: Fix slack-desc.
python/pipdeptree: Fix slack-desc.
python/pkginfo: Fix slack-desc.
python/pkginfo: Updated for version 1.4.1.
python/planes: Fix slack-desc.
python/poster: Fix slack-desc.
python/progressive: Fix slack-desc.
python/ptpython: Fix slack-desc.
python/py3cairo: Fix slack-desc.
python/py3sensors: Fix slack-desc.
python/py4j: Fix slack-desc.
python/pyasn1-modules: Fix slack-desc.
python/pychm: Fix slack-desc.
python/pydblite: Fix slack-desc.
python/pyglet: Fix slack-desc.
python/pygoocanvas: Fix slack-desc.
python/pyinotify: Fix slack-desc.
python/pylirc: Fix slack-desc.
python/pyorbit: Fix slack-desc.
python/pypy3: Fix slack-desc.
python/pypy: Fix slack-desc.
python/pyside: Fix slack-desc.
python/pysmssend: Fix slack-desc.
python/pysnmp: Fix slack-desc.
python/python-MonthDelta: Fix slack-desc.
python/python-authres: Fix slack-desc.
python/python-bigfloat: Fix slack-desc.
python/python-blake2: Fix slack-desc.
python/python-chardet: Fix slack-desc.
python/python-cheetah: Fix slack-desc.
python/python-demjson: Fix slack-desc.
python/python-distutils-extra: Fix slack-desc.
python/python-editor: Fix slack-desc.
python/python-elementtree: Fix slack-desc.
python/python-elib.intl: Fix slack-desc.
python/python-ldap: Fix slack-desc.
python/python-libsass: Fix slack-desc.
python/python-mccabe: Fix slack-desc.
python/python-morbid: Fix slack-desc.
python/python-mpd: Fix slack-desc.
python/python-musicbrainz2: Fix slack-desc.
python/python-netaddr: Fix slack-desc.
python/python-pmw: Fix slack-desc.
python/python-pydns: Fix slack-desc.
python/python-pypolicyd-spf: Fix slack-desc.
python/python-pyspf: Fix slack-desc.
python/python-requestbuilder: Fix slack-desc.
python/python-requests-kerberos: Fix slack-desc.
python/python-stomper: Fix slack-desc.
python/python-uuid: Fix slack-desc.
python/python-vatnumber: Fix slack-desc.
python/python-wordpress-xmlrpc: Fix slack-desc.
python/python-wrapt: Fix slack-desc.
python/python-yenc: Fix slack-desc.
python/python3-Cython: Fix slack-desc.
python/python3-pyparted: Fix slack-desc.
python/python3-sip: Fix slack-desc.
python/pyusb: Fix slack-desc.
python/pywebkitgtk: Fix slack-desc.
python/pyxdg: Fix slack-desc.
python/pyzmq: Fix slack-desc.
python/relatorio: Fix slack-desc.
python/requests-oauthlib: Fix slack-desc.
python/scikit-learn: Fix slack-desc.
python/setuptools-scm: Fix slack-desc.
python/snuggs: Fix slack-desc.
python/soundcloud: Fix slack-desc.
python/sqlalchemy-migrate: Fix slack-desc.
python/tagpy: Fix slack-desc.
python/tempita: Fix slack-desc.
python/termcolor: Fix slack-desc.
python/trollius: Fix slack-desc.
python/virtualenv: Fix slack-desc.
python/webassets: Fix slack-desc.
python/werkzeug: Fix slack-desc.
python/wsgiref: Fix slack-desc.
ruby/passenger: Fix slack-desc.
ruby/ruby-build: Fix slack-desc.
ruby/ruby-faraday: Updated for version 0.10.0.
ruby/ruby-sass: Fix slack-desc.
ruby/rubygem-coderay: Fix slack-desc.
ruby/rubygem-gosu: Fix slack-desc.
ruby/rubygem-sass: Fix slack-desc.
ruby/rubygem-slop3: Fix slack-desc.
ruby/sqlite3: Fix slack-desc.
system/Eterm: Fix slack-desc.
system/MySQL-Sandbox: Fix slack-desc.
system/TermRecord: Fix slack-desc.
system/USBdev: Fix slack-desc.
system/adobe-source-han-sans-fonts: Fix slack-desc.
system/adobe-source-sans-pro-font: Fix slack-desc.
system/advcopy: Fix slack-desc.
system/aha: Fix slack-desc.
system/ansible: Fix slack-desc.
system/apache-tomcat: Fix slack-desc.
system/apachetop: Fix slack-desc.
system/argyllcms: Fix slack-desc.
system/asbt: Fix slack-desc.
system/aterm: Fix slack-desc.
system/atop: Fix slack-desc.
system/augeas: Fix slack-desc.
system/bacula-client: Fix slack-desc.
system/bacula: Fix slack-desc.
system/bicon: Fix slack-desc.
system/biew: Fix slack-desc.
system/bootchart: Fix slack-desc.
system/brasero: Fix slack-desc.
system/byobu: Fix slack-desc.
system/cantarell-fonts: Fixed SlackBuild.
system/caprice32: Fix slack-desc.
system/cbmbasic: Fix slack-desc.
system/cdemu-daemon: Fix slack-desc.
system/cdrkit: Fix slack-desc.
system/cntlm: Fix slack-desc.
system/colord: Add auto detection for vala.
system/cpuinfo2cpuflags: Fix slack-desc.
system/cpulimit: Fix slack-desc.
system/crmsh: Fix slack-desc.
system/cronie: Fix slack-desc.
system/crunch: Fix slack-desc.
system/d-feet: Fix slack-desc.
system/daa2iso: Fix slack-desc.
system/dar: Fix slack-desc.
system/ddrescue-gui: Fix slack-desc.
system/detox: Fix slack-desc.
system/disk-manager: Fix slack-desc.
system/diskscan: Fix slack-desc.
system/docker: Fix slack-desc.
system/dosbox: Fix slack-desc.
system/driconf: Fix slack-desc.
system/dstat: Fix slack-desc.
system/dump: Fix slack-desc.
system/dvdisaster: Fix slack-desc.
system/dynamips: Fix slack-desc.
system/elasticsearch: Fix slack-desc.
system/eltclsh: Fix slack-desc.
system/emelfm2: Fix slack-desc.
system/eventlog: Fix slack-desc.
system/evilvte: Fix slack-desc.
system/extract-xiso: Fix slack-desc.
system/facter: Fix slack-desc.
system/fdupes: Fix slack-desc.
system/file-roller: Fix slack-desc.
system/findcmd: Fix slack-desc.
system/findpkg: Fix slack-desc.
system/fira-fonts: Fix slack-desc.
system/fpm2: Fix slack-desc.
system/freeswitch: Fix slack-desc.
system/fs-uae-arcade: Fix slack-desc.
system/fs-uae-launcher: Fix slack-desc.
system/fs-uae: Fix slack-desc.
system/fslint: Fix slack-desc.
system/fuseiso: Fix slack-desc.
system/gdmap: Fix slack-desc.
system/gencfs: Fix slack-desc.
system/gksu: Fix slack-desc.
system/glyptodon: Fix slack-desc.
system/gnome-commander: Fix slack-desc.
system/gnome-terminal: Fix slack-desc.
system/gnomint: Fix slack-desc.
system/gpart: Fix slack-desc.
system/gpsbabel: Fix slack-desc.
system/gradm: Fix slack-desc.
system/graveman: Fix slack-desc.
system/gsmartcontrol: Fix slack-desc.
system/gtk-vnc: Fix slack-desc.
system/guix: Fix slack-desc.
system/hal-flash: Fix slack-desc.
system/hercules: Fix slack-desc.
system/hime: Fix slack-desc.
system/hntool: Fix slack-desc.
system/ibam: Fix slack-desc.
system/idle3-tools: Fix slack-desc.
system/info2man: Fix slack-desc.
system/inxi: Updated for version 2.3.4.
system/ioping: Fix slack-desc.
system/ipmitool: Fix slack-desc.
system/irqbalance: Fix slack-desc.
system/isomaster: Fix slack-desc.
system/jdiskreport: Fix slack-desc.
system/jenkins: Fix slack-desc.
system/jmtpfs: Fix slack-desc.
system/john: Fix slack-desc.
system/jq: Fix slack-desc.
system/jsawk: Fix slack-desc.
system/kafka: Fix slack-desc.
system/keylaunch: Fix slack-desc.
system/lbrate: Fix slack-desc.
system/letsencrypt: Fix slack-desc.
system/linkchecker: Fix slack-desc.
system/lnav: Fix slack-desc.
system/lomoco: Fix slack-desc.
system/lxdm: Fix slack-desc.
system/lxsplit: Fix slack-desc.
system/macemu: Fix slack-desc.
system/makeself: Fix slack-desc.
system/md5deep: Fix slack-desc.
system/memtest86+: Fix slack-desc.
system/memtest86: Fix slack-desc.
system/memuse: Fix slack-desc.
system/microcode_ctl: Fix slack-desc.
system/microemulator: Fix slack-desc.
system/mongo-tools: Fix slack-desc.
system/monitorix: Fix slack-desc.
system/msitools: Fix slack-desc.
system/mucommander: Fix slack-desc.
system/multitail: Fix slack-desc.
system/munin-node: Fix slack-desc.
system/musl: Fix slack-desc.
system/nanum-coding-fonts-ttf: Fix slack-desc.
system/nanum-fonts-ttf: Fix slack-desc.
system/numlockx: Fix slack-desc.
system/nvidia-legacy340-driver: Fix slack-desc.
system/opam: Fix slack-desc.
system/openmpi: Fix slack-desc.
system/openrc: Updated for version 0.22.3.
system/opensc: Fix slack-desc.
system/oracle-instantclient-basic: Fix slack-desc.
system/oracle-instantclient-devel: Fix slack-desc.
system/oracle-xe: Fix slack-desc.
system/packagekit: Fix slack-desc.
system/packagekit: Updated for version 1.1.4.
system/parallel: Fix slack-desc.
system/partclone: Fix slack-desc.
system/passwdqc: Fix slack-desc.
system/password-store: Fix slack-desc.
system/passwordsafe: Fix slack-desc.
system/pbzip2: Fix slack-desc.
system/pdsh: Fix slack-desc.
system/pev: Fix slack-desc.
system/pgadmin3: Fix slack-desc.
system/pgsanity: Fix slack-desc.
system/plan9port: Fix slack-desc.
system/pmount: Fix slack-desc.
system/pommed-light: Fix slack-desc.
system/postgresql: Fix slack-desc.
system/procinfo-ng: Fix slack-desc.
system/pstate-frequency: Fix slack-desc.
system/pv: Fix slack-desc.
system/pwsafe: Fix slack-desc.
system/qdirstat: Fix slack-desc.
system/qstardict: Fix slack-desc.
system/qtgzmanager: Fix slack-desc.
system/quotatool: Fix slack-desc.
system/rabbitmq-server: Fix slack-desc.
system/ranger: Fix slack-desc.
system/recorder: Fix slack-desc.
system/redis: Fix slack-desc.
system/rename: Fix slack-desc.
system/rhash: Fix slack-desc.
system/rng-tools: Fix slack-desc.
system/roxterm: Fix slack-desc.
system/rsyslog: Fix slack-desc.
system/rxvt-unicode: Fix slack-desc.
system/samhain: Fix slack-desc.
system/samsung-mfp-drivers: Fix slack-desc.
system/samsung-mfp-drivers: Updated for version 1.00.36.
system/sbbdep: Fix slack-desc.
system/scanmem: Fix slack-desc.
system/schedtool: Fix slack-desc.
system/shake: Fix slack-desc.
system/simpleburn: Fix slack-desc.
system/slim: Fix slack-desc.
system/spl-solaris: Fix slack-desc.
system/splix: Fix slack-desc.
system/sqlite2: Fix slack-desc.
system/statifier: Fix slack-desc.
system/sudosh2: Fix slack-desc.
system/supervisor: Fix slack-desc.
system/tagainijisho: Fix slack-desc.
system/tamsyn-font: Fix slack-desc.
system/tc-play: Fix slack-desc.
system/testdisk: Fix slack-desc.
system/the_silver_searcher: Fix slack-desc.
system/thermal_daemon: Updated for version 1.5.4.
system/thinkfan: Fix slack-desc.
system/tiger: Fix slack-desc.
system/tinyterm: Fix slack-desc.
system/tinyvm: Fix slack-desc.
system/tokyocabinet: Fix slack-desc.
system/tokyotyrant: Fix slack-desc.
system/trachet: Fix slack-desc.
system/trash-cli: Fix slack-desc.
system/trrntzip: Fix slack-desc.
system/truecrypt: Fix slack-desc.
system/ttf-arphic-uming: Fix slack-desc.
system/ttf-open-sans: Fix slack-desc.
system/ttf-paratype-pt-fonts: Fix slack-desc.
system/ttf-zekton: Fix slack-desc.
system/tty2gif: Fix slack-desc.
system/twin: Fix slack-desc.
system/uif2iso: Fix slack-desc.
system/un-fonts-core: Fix slack-desc.
system/unetbootin: Fix slack-desc.
system/unhide: Fix slack-desc.
system/unison: Fix slack-desc.
system/untex: Fix slack-desc.
system/usbview: Fix slack-desc.
system/vagrant: Fix slack-desc.
system/veracrypt: Fix slack-desc.
system/vice: Fix slack-desc.
system/vifm: Fix slack-desc.
system/webcore-fonts: Fix slack-desc.
system/webcore-fonts: Updated for version 3.0.
system/whowatch: Fix slack-desc.
system/wiimms-iso-tools: Fix slack-desc.
system/wine: Fix slack-desc.
system/winetricks: Fix slack-desc.
system/winusb: Fix slack-desc.
system/wipe: Fix slack-desc.
system/wmfsm: Fix slack-desc.
system/worker: Fix slack-desc.
system/wterm: Fix slack-desc.
system/xarchiver: Fix slack-desc.
system/xbattmon: Fix slack-desc.
system/xbindkeys: Fix slack-desc.
system/xdiskusage: Fix slack-desc.
system/xfe: Fix slack-desc.
system/xfsudo: Fix slack-desc.
system/xrdp: Fix slack-desc.
system/xrestop: Fix slack-desc.
system/xwiimote: Fix slack-desc.
system/yelp-tools: Fix slack-desc.
system/z: Fix slack-desc.
system/zfs-on-linux: Fix slack-desc.
system/zookeeper: Fix slack-desc.
system/zopfli: Fix slack-desc.
system/zuluCrypt: Fix slack-desc.
+--------------------------+

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From reedych at reedych.pw  Mon Nov 14 12:52:50 2016
From: reedych at reedych.pw (Reedych)
Date: Mon, 14 Nov 2016 18:52:50 +0600
Subject: [Slackbuilds-users] Updates - 20161114.1
Message-ID: <20161114155253.qqSK6obD@smtp1o.mail.yandex.net>

Emm, but for what (why) do you do this?

14 ????. 2016 ?. 18:20 ???????????? Willy Sudiarto Raharjo  ???????:
>
> Hi 
>
> This is an unplanned but important public update as B. Watson (Urchlay) 
> is working to fix ALL slack-desc to comply our templates. 
>
> In the next few days, he will be pushing his work on READMEs. Let's hope 
> there won't be any conflict during merging. 
>
> Big thanks to him who voluntarily do this amazing job in just a couple 
> of days. There's more than 1800+ commits done by him for slack-desc and 
> more to come in the next few days. 
>
> Maintainers, please make sure to grab the latest tarball from our 
> repository or grab it from GIT repository (i know, i have said this many 
> times), but it's important to start from what we have in the server/GIT 
> repository instead of using your local copy which *may* be out of date 
> or out of sync with ours. 
>
> Mon Nov 14 10:00:56 UTC 2016 
> academic/GeoGebra: Fix slack-desc. 
> academic/Kst: Fix slack-desc. 
> academic/R: Fix slack-desc. 
> academic/Xyce: Fix slack-desc. 
> academic/abntex: Fix slack-desc. 
> academic/amd: Fix slack-desc. 
> academic/amplifx: Fix slack-desc. 
> academic/archeopteryx: Fix slack-desc. 
> academic/armadillo: Fix slack-desc. 
> academic/artha: Fix slack-desc. 
> academic/avogadro: Fix slack-desc. 
> academic/biblesync: Fix slack-desc. 
> academic/bibletime: Fix slack-desc. 
> academic/btf: Fix slack-desc. 
> academic/calcoo: Fix slack-desc. 
> academic/camd: Fix slack-desc. 
> academic/cblas: Fix slack-desc. 
> academic/ccolamd: Fix slack-desc. 
> academic/chemtool: Fix slack-desc. 
> academic/cholmod: Fix slack-desc. 
> academic/colamd: Fix slack-desc. 
> academic/convertall: Fix slack-desc. 
> academic/copasi: Fix slack-desc. 
> academic/csparse: Fix slack-desc. 
> academic/cxsparse: Fix slack-desc. 
> academic/engauge: Fix slack-desc. 
> academic/equalx: Fix slack-desc. 
> academic/evopedia_qt: Fix slack-desc. 
> academic/fann: Fix slack-desc. 
> academic/fet: Fix slack-desc. 
> academic/fet: Updated for version 5.30.5. 
> academic/flann: Fix slack-desc. 
> academic/flashqard: Fix slack-desc. 
> academic/free42: Fix slack-desc. 
> academic/freechartgeany: Fix slack-desc. 
> academic/gaw3: Fix slack-desc. 
> academic/gcompris: Fix slack-desc. 
> academic/geda-gaf: Fix slack-desc. 
> academic/genius: Fix slack-desc. 
> academic/geomview: Fix slack-desc. 
> academic/ggobi: Fix slack-desc. 
> academic/gnucap: Fix slack-desc. 
> academic/gretl: Fix slack-desc. 
> academic/grpn: Fix slack-desc. 
> academic/gtkwave: Fix slack-desc. 
> academic/gtypist: Fix slack-desc. 
> academic/iTest: Fix slack-desc. 
> academic/irsim: Fix slack-desc. 
> academic/itex2mml: Fix slack-desc. 
> academic/jugglinglab: Fix slack-desc. 
> academic/klu: Fix slack-desc. 
> academic/knime: Fix slack-desc. 
> academic/ktikz: Fix slack-desc. 
> academic/labplot2: Fix slack-desc. 
> academic/ladr: Fix slack-desc. 
> academic/ldl: Fix slack-desc. 
> academic/link-grammar: Fix slack-desc. 
> academic/loggerpro: Fix slack-desc. 
> academic/mafft: Fix slack-desc. 
> academic/mathomatic: Fix slack-desc. 
> academic/maxima: Fix slack-desc. 
> academic/mendeleydesktop: Fix slack-desc. 
> academic/metis: Fix slack-desc. 
> academic/mpmath: Fix slack-desc. 
> academic/ncbi-blast-plus: Fix slack-desc. 
> academic/ngspice: Fix slack-desc. 
> academic/octave: Fix slack-desc. 
> academic/paml: Fix slack-desc. 
> academic/parmetis: Fix slack-desc. 
> academic/patsy: Fix slack-desc. 
> academic/pcb: Fix slack-desc. 
> academic/pspp: Fix slack-desc. 
> academic/pyfits: Fix slack-desc. 
> academic/qhull: Fix slack-desc. 
> academic/qtoctave: Fix slack-desc. 
> academic/rbio: Fix slack-desc. 
> academic/root: Fix slack-desc. 
> academic/scipy: Fix slack-desc. 
> academic/spades: Fix slack-desc. 
> academic/spqr: Fix slack-desc. 
> academic/stellarium: Fix slack-desc. 
> academic/suitesparseconfig: Fix slack-desc. 
> academic/sword-data-kjv: Fix slack-desc. 
> academic/sympy: Fix slack-desc. 
> academic/tabix: Fix slack-desc. 
> academic/tuxtype2: Fix slack-desc. 
> academic/umfpack: Fix slack-desc. 
> academic/veusz: Fix slack-desc. 
> academic/wmcalc: Fix slack-desc. 
> academic/xcircuit: Fix slack-desc. 
> accessibility/Synkron: Fix slack-desc. 
> accessibility/jpilot: Fix slack-desc. 
> audio/TiMidity++: Fix slack-desc. 
> audio/aacplusenc: Fix slack-desc. 
> audio/aften: Fix slack-desc. 
> audio/aj-snapshot: Fix slack-desc. 
> audio/alsaequal: Fix slack-desc. 
> audio/alsamodularsynth: Fix slack-desc. 
> audio/ario: Fix slack-desc. 
> audio/asunder: Fix slack-desc. 
> audio/atunes: Fix slack-desc. 
> audio/audacity: Fix slack-desc. 
> audio/calf: Fix slack-desc. 
> audio/chuck: Fix slack-desc. 
> audio/clementine: Fix slack-desc. 
> audio/clthreads: Fix slack-desc. 
> audio/clyrics: Fix slack-desc. 
> audio/coverlovin: Fix slack-desc. 
> audio/crip: Fix slack-desc. 
> audio/deadbeef: Fix slack-desc. 
> audio/decibel-audio-player: Fix slack-desc. 
> audio/easymp3gain: Fix slack-desc. 
> audio/easytag: Fix slack-desc. 
> audio/faad2: Fix slack-desc. 
> audio/faust: Fix slack-desc. 
> audio/fst: Fix slack-desc. 
> audio/gimmix: Fix slack-desc. 
> audio/gmpc: Fix slack-desc. 
> audio/gnomad2: Fix slack-desc. 
> audio/gnump3d: Fix slack-desc. 
> audio/gvolwheel: Fix slack-desc. 
> audio/herrie: Fix slack-desc. 
> audio/hydrogen: Fix slack-desc. 
> audio/iripdb: Fix slack-desc. 
> audio/jack2: Fix slack-desc. 
> audio/jamin: Fix slack-desc. 
> audio/kid3: Fix slack-desc. 
> audio/ladspa_sdk: Fix slack-desc. 
> audio/lash: Fix slack-desc. 
> audio/libbs2b: Fix slack-desc. 
> audio/luppp: Fix slack-desc. 
> audio/lv2file: Fix slack-desc. 
> audio/milkytracker: Fix slack-desc. 
> audio/minimodem: Fix slack-desc. 
> audio/mixxx: Fix slack-desc. 
> audio/mp3splt-gtk: Fix slack-desc. 
> audio/mp4tools: Fix slack-desc. 
> audio/mppenc: Fix slack-desc. 
> audio/nas: Fix slack-desc. 
> audio/ncmpcpp: Fix slack-desc. 
> audio/nero-aac: Fix slack-desc. 
> audio/non: Fix slack-desc. 
> audio/ocp: Fix slack-desc. 
> audio/patchage: Fix slack-desc. 
> audio/phat: Fix slack-desc. 
> audio/playmp3list: Fix slack-desc. 
> audio/pogo: Fix slack-desc. 
> audio/ponymix: Fix slack-desc. 
> audio/pulseaudio-ctl: Fix slack-desc. 
> audio/pyalsaaudio: Fix slack-desc. 
> audio/qjackctl: Fix slack-desc. 
> audio/retrovol: Fix slack-desc. 
> audio/sayonara-player: Fix slack-desc. 
> audio/sbagen: Fix slack-desc. 
> audio/schismtracker: Fix slack-desc. 
> audio/seq24: Fix slack-desc. 
> audio/sonata: Fix slack-desc. 
> audio/soundconverter: Fix slack-desc. 
> audio/spandsp: Fix slack-desc. 
> audio/specimen: Fix slack-desc. 
> audio/speex: Fix slack-desc. 
> audio/streamripper: Fix slack-desc. 
> audio/swh-plugins: Fix slack-desc. 
> audio/tagtool: Fix slack-desc. 
> audio/tuxguitar: Fix slack-desc. 
> audio/vcf_plugins: Fix slack-desc. 
> audio/volume.app: Fix slack-desc. 
> audio/volwheel: Fix slack-desc. 
> audio/wavbreaker: Fix slack-desc. 
> audio/whysynth: Fix slack-desc. 
> audio/wmusic: Fix slack-desc. 
> audio/xcfa: Fix slack-desc. 
> audio/xforge: Fix slack-desc. 
> audio/xmms-scrobbler: Fix slack-desc. 
> audio/xmms-shn: Fix slack-desc. 
> audio/xmms2: Fix slack-desc. 
> business/AssociationSubscribersManager: Fix slack-desc. 
> business/stansoft: Fix slack-desc. 
> desktop/Alphacube-GTK: Fix slack-desc. 
> desktop/LX-Colors-themes: Fix slack-desc. 
> desktop/QtCurve-KDE4: Fix slack-desc. 
> desktop/Window_Manager_Scripts: Fix slack-desc. 
> desktop/afterstep: Fix slack-desc. 
> desktop/avant-window-navigator: Fix slack-desc. 
> desktop/awemenugen: Fix slack-desc. 
> desktop/awn-extras: Fix slack-desc. 
> desktop/bashish: Fix slack-desc. 
> desktop/bmpanel2: Fix slack-desc. 
> desktop/boje-themes: Fix slack-desc. 
> desktop/bunsen-themes: Fix slack-desc. 
> desktop/catfish: Fix slack-desc. 
> desktop/cathexis-suite-themes: Fix slack-desc. 
> desktop/ccsm: Fix slack-desc. 
> desktop/cellwriter: Fix slack-desc. 
> desktop/clipit: Fix slack-desc. 
> desktop/devilspie: Fix slack-desc. 
> desktop/dmenu: Fix slack-desc. 
> desktop/dwm: Fix slack-desc. 
> desktop/e16: Fix slack-desc. 
> desktop/elementary-xfce: Fix slack-desc. 
> desktop/enlightenment: Fix slack-desc. 
> desktop/evilwm: Fix slack-desc. 
> desktop/fbpanel: Fix slack-desc. 
> desktop/fbrowse-tray: Fix slack-desc. 
> desktop/ffmpegthumbnailer: Fix slack-desc. 
> desktop/fvwm95: Fix slack-desc. 
> desktop/glabels: Fix slack-desc. 
> desktop/grits: Fix slack-desc. 
> desktop/grun: Fix slack-desc. 
> desktop/gtk-nodoka-engine: Fix slack-desc. 
> desktop/gtkhash: Fix slack-desc. 
> desktop/herbstluftwm: Fix slack-desc. 
> desktop/i3lock: Fix slack-desc. 
> desktop/i3pystatus: Fix slack-desc. 
> desktop/imgurbash: Fix slack-desc. 
> desktop/kanyremote: Fix slack-desc. 
> desktop/kover: Fix slack-desc. 
> desktop/kpartsplugin: Fix slack-desc. 
> desktop/lumina: Fix slack-desc. 
> desktop/lxpanel: Fix slack-desc. 
> desktop/maitreya: Fix slack-desc. 
> desktop/mimi: Fix slack-desc. 
> desktop/mousepad: Fix slack-desc. 
> desktop/musca: Fix slack-desc. 
> desktop/neutral: Fix slack-desc. 
> desktop/nitrogen: Fix slack-desc. 
> desktop/numix-icon-theme-circle: Fix slack-desc. 
> desktop/numix-icon-theme: Fix slack-desc. 
> desktop/obapps: Fix slack-desc. 
> desktop/obconf: Fix slack-desc. 
> desktop/obkey: Switch to i586. 
> desktop/obmenu: Fix slack-desc. 
> desktop/obsession: Fix slack-desc. 
> desktop/openbox-menu: Fix slack-desc. 
> desktop/pdfsam: Fix slack-desc. 
> desktop/pekwm: Fix slack-desc. 
> desktop/pidgin-window_merge: Added (Window Merge for Pidgin). 
> desktop/plank: Fix slack-desc. 
> desktop/plasma-applet-daisy: Fix slack-desc. 
> desktop/plasma-eyasdp: Fix slack-desc. 
> desktop/plasma-runner-browsefirefoxbookmarks: Fix slack-desc. 
> desktop/plasma-widget-menubar: Fix slack-desc. 
> desktop/pytyle: Fix slack-desc. 
> desktop/q4wine: Fix slack-desc. 
> desktop/quadkonsole4: Fix slack-desc. 
> desktop/razorqt: Fix slack-desc. 
> desktop/recorditnow: Fix slack-desc. 
> desktop/rofi: Fix slack-desc. 
> desktop/rootactions_servicemenu: Fix slack-desc. 
> desktop/rsl: Fix slack-desc. 
> desktop/sawfish-session-dialog: Fix slack-desc. 
> desktop/screenfetch: Fix slack-desc. 
> desktop/screenkey: Fix slack-desc. 
> desktop/screensaver-icon: Fix slack-desc. 
> desktop/searchmonkey: Fix slack-desc. 
> desktop/siva-flat-themes: Fix slack-desc. 
> desktop/skippy-xd: Fix slack-desc. 
> desktop/skulpture: Fix slack-desc. 
> desktop/slack-wallpapers: Fix slack-desc. 
> desktop/ssr: Fix slack-desc. 
> desktop/sun: Fix slack-desc. 
> desktop/sync-engine: Fix slack-desc. 
> desktop/thunar-dropbox: Fix slack-desc. 
> desktop/thunar-thumbnailers: Fix slack-desc. 
> desktop/tint2: Fix slack-desc. 
> desktop/uwm: Fix slack-desc. 
> desktop/velox: Fix slack-desc. 
> desktop/vim-qt: Fix slack-desc. 
> desktop/vivacious-colors-gtk-icon-theme: Fix slack-desc. 
> desktop/vivacious-colors-gtk-theme: Fix slack-desc. 
> desktop/vwm: Fix slack-desc. 
> desktop/wbar: Fix slack-desc. 
> desktop/wmakerconf: Fix slack-desc. 
> desktop/wmbackground: Fix slack-desc. 
> desktop/wmblob: Fix slack-desc. 
> desktop/wmcliphist: Fix slack-desc. 
> desktop/wmclockmon: Fix slack-desc. 
> desktop/wmname: Fix slack-desc. 
> desktop/wmpinboard: Fix slack-desc. 
> desktop/wmtimer: Fix slack-desc. 
> desktop/wmweather+: Fix slack-desc. 
> desktop/wmwebcam: Fix slack-desc. 
> desktop/wmxss: Fix slack-desc. 
> desktop/x-tile: Fix slack-desc. 
> desktop/xed: Fix slack-desc. 
> desktop/xed: Updated for version 1.2.1. 
> desktop/xfce4-eyes-plugin: Fix slack-desc. 
> desktop/xfce4-mount-plugin: Updated for version 0.6.7. 
> desktop/xfce4-wavelan-plugin: Fix slack-desc. 
> desktop/xtrascreenhacks: Fix slack-desc. 
> desktop/xvkbd: Fix slack-desc. 
> desktop/yawp: Fix slack-desc. 
> development/CImg: Fix slack-desc. 
> development/LLgen: Fix slack-desc. 
> development/ParadisEO: Fix slack-desc. 
> development/SDL2_gfx: Fix slack-desc. 
> development/WebStorm: Fix slack-desc. 
> development/ahven: Fix slack-desc. 
> development/android-studio: Fix slack-desc. 
> development/android-tools: Fix slack-desc. 
> development/apache-ant: Fix slack-desc. 
> development/apache-jmeter: Fix slack-desc. 
> development/apache-maven: Fix slack-desc. 
> development/apitrace: Fix slack-desc. 
> development/argouml: Fix slack-desc. 
> development/asl: Fix slack-desc. 
> development/asm6809: Fix slack-desc. 
> development/astyle: Fix slack-desc. 
> development/atom: Fix slack-desc. 
> development/atom: Updated for version 1.12.2. 
> development/avra: Fix slack-desc. 
> development/avrdude: Fix slack-desc. 
> development/bacon: Fix slack-desc. 
> development/bashdb: Fix slack-desc. 
> development/bfg: Fix slack-desc. 
> development/bluefish: Fix slack-desc. 
> development/brackets: Fix slack-desc. 
> development/bvi: Fix slack-desc. 
> development/cc65: Fix slack-desc. 
> development/ccl: Fix slack-desc. 
> development/check: Fix slack-desc. 
> development/chibi-scheme: Fix slack-desc. 
> development/chicken: Fix slack-desc. 
> development/cim: Fix slack-desc. 
> development/composer: Fix slack-desc. 
> development/couchdb: Fix slack-desc. 
> development/cppcms: Fix slack-desc. 
> development/cppdb: Fix slack-desc. 
> development/cppunit: Fix slack-desc. 
> development/cryptoki: Fix slack-desc. 
> development/cudatoolkit: Fix slack-desc. 
> development/cunit: Fix slack-desc. 
> development/curlpp: Fix slack-desc. 
> development/dao: Fix slack-desc. 
> development/decklink-sdk: Fix slack-desc. 
> development/dejagnu: Fix slack-desc. 
> development/diakonos: Fix slack-desc. 
> development/dpkg: Updated for version 1.18.14. 
> development/eagle: Fix slack-desc. 
> development/eclipse-cpp: Fix slack-desc. 
> development/eclipse-java: Fix slack-desc. 
> development/energia: Fix slack-desc. 
> development/epydoc: Fix slack-desc. 
> development/eric: Fix slack-desc. 
> development/erlang-otp: Fix slack-desc. 
> development/freetds: Fix slack-desc. 
> development/fsharp: Fix slack-desc. 
> development/ftjam: Fix slack-desc. 
> development/fuel: Fix slack-desc. 
> development/gambit: Fix slack-desc. 
> development/geany-plugins: Fix slack-desc. 
> development/geany: Fix slack-desc. 
> development/gecode: Fix slack-desc. 
> development/gedit-plugins: Fix slack-desc. 
> development/generatorrunner: Fix slack-desc. 
> development/gisto: Fix slack-desc. 
> development/glade: Fix slack-desc. 
> development/global: Fix slack-desc. 
> development/gnats: Fix slack-desc. 
> development/gnuradio: Fix slack-desc. 
> development/gnustep-startup: Fix slack-desc. 
> development/gob2: Fix slack-desc. 
> development/gplcver: Fix slack-desc. 
> development/grails: Fix slack-desc. 
> development/gtest: Fix slack-desc. 
> development/guile1.8: Fix slack-desc. 
> development/highlight: Fix slack-desc. 
> development/hugs98: Fix slack-desc. 
> development/icemon: Fix slack-desc. 
> development/icon: Fix slack-desc. 
> development/idea: Fix slack-desc. 
> development/ioncube-loader: Fix slack-desc. 
> development/ipython-mathjax: Fix slack-desc. 
> development/ipython: Fix slack-desc. 
> development/jam: Fix slack-desc. 
> development/javacc: Fix slack-desc. 
> development/jdk: Fix slack-desc. 
> development/jeex: Fix slack-desc. 
> development/julius: Fix slack-desc. 
> development/kaaedit: Fix slack-desc. 
> development/kompozer: Fix slack-desc. 
> development/leo: Fix slack-desc. 
> development/libxbgi: Fix slack-desc. 
> development/lighttable: Fix slack-desc. 
> development/love-legacy080: Fix slack-desc. 
> development/lua52: Fix slack-desc. 
> development/lua: Fix slack-desc. 
> development/luarocks: Fix slack-desc. 
> development/lwtools: Fix slack-desc. 
> development/makedepf90: Fix slack-desc. 
> development/maude: Fix slack-desc. 
> development/mcu8051ide: Fix slack-desc. 
> development/medit: Fix slack-desc. 
> development/meld3: Fix slack-desc. 
> development/mono-addins: Fix slack-desc. 
> development/mono: Fix slack-desc. 
> development/mosml: Fix slack-desc. 
> development/mphidflash: Fix slack-desc. 
> development/mtasc: Fix slack-desc. 
> development/mutagen: Fix slack-desc. 
> development/mutagen: Updated for version 1.35.1. 
> development/mysql-workbench: Fix slack-desc. 
> development/nedit: Fix slack-desc. 
> development/netbeans: Fix slack-desc. 
> development/newtonsoft-json: Fix slack-desc. 
> development/nexus: Fix slack-desc. 
> development/nickle: Fix slack-desc. 
> development/npm2tgz: Fix slack-desc. 
> development/nqp: Fix slack-desc. 
> development/nsis: Fix slack-desc. 
> development/nuget: Fix slack-desc. 
> development/numpy-legacy3: Fix slack-desc. 
> development/numpy-legacy: Fix slack-desc. 
> development/numpy3: Fix slack-desc. 
> development/numpy: Fix slack-desc. 
> development/omake: Fix slack-desc. 
> development/omniORBpy: Fix slack-desc. 
> development/opencvs: Fix slack-desc. 
> development/parrot: Fix slack-desc. 
> development/pasdoc: Fix slack-desc. 
> development/pd-psql: Fix slack-desc. 
> development/pforth: Fix slack-desc. 
> development/poedit: Fix slack-desc. 
> development/portaudio: Fix slack-desc. 
> development/power-architect: Fix slack-desc. 
> development/pudb: Fix slack-desc. 
> development/pycscope: Fix slack-desc. 
> development/pyenchant: Fix slack-desc. 
> development/pyvim: Fix slack-desc. 
> development/qconf: Fix slack-desc. 
> development/quilt: Fix slack-desc. 
> development/rakudo: Fix slack-desc. 
> development/referenceassemblies-pcl: Fix slack-desc. 
> development/regina-rexx: Fix slack-desc. 
> development/rmlmmc: Fix slack-desc. 
> development/rstudio-desktop: Fix slack-desc. 
> development/ruff: Fix slack-desc. 
> development/scite: Fix slack-desc. 
> development/sdcc: Fix slack-desc. 
> development/shed: Fix slack-desc. 
> development/shiboken: Fix slack-desc. 
> development/sloccount: Fix slack-desc. 
> development/sonarqube: Fix slack-desc. 
> development/spl: Fix slack-desc. 
> development/splint: Fix slack-desc. 
> development/sqldeveloper: Fix slack-desc. 
> development/squeak-vm: Fix slack-desc. 
> development/squirrel-sql: Fix slack-desc. 
> development/src-vcs: Fix slack-desc. 
> development/staruml: Fix slack-desc. 
> development/swfmill: Fix slack-desc. 
> development/textadept: Fix slack-desc. 
> development/tkdnd: Fix slack-desc. 
> development/tora: Fix slack-desc. 
> development/trac: Fix slack-desc. 
> development/tyrutils-ericw: Fix slack-desc. 
> development/u-boot-tools: Fix slack-desc. 
> development/udis86: Fix slack-desc. 
> development/uncrustify: Fix slack-desc. 
> development/vala-12: Fix slack-desc. 
> development/vala: Fix slack-desc. 
> development/valgrind: Fix slack-desc. 
> development/vispatch: Fix slack-desc. 
> development/visual-studio-code: Fix slack-desc. 
> development/vstudio: Fix slack-desc. 
> development/xdebug: Fix slack-desc. 
> development/xsp: Fix slack-desc. 
> development/xxdiff: Fix slack-desc. 
> games/0ad-data: Fix slack-desc. 
> games/0ad: Fix slack-desc. 
> games/7kaa: Fix slack-desc. 
> games/KoboDeluxe: Fix slack-desc. 
> games/Pyfa: Fix slack-desc. 
> games/SpaceZero: Fix slack-desc. 
> games/abe: Fix slack-desc. 
> games/abuse: Fix slack-desc. 
> games/ace: Fix slack-desc. 
> games/adom: Fix slack-desc. 
> games/advancemame: Fix slack-desc. 
> games/ags: Fix slack-desc. 
> games/antimicro: Fix slack-desc. 
> games/ardentryst: Fix slack-desc. 
> games/arnold-cpc: Fix slack-desc. 
> games/assaultcube-reloaded: Fix slack-desc. 
> games/assaultcube: Fix slack-desc. 
> games/bluemoon: Fix slack-desc. 
> games/bomberclone: Fix slack-desc. 
> games/brutalchess: Fix slack-desc. 
> games/caph: Fix slack-desc. 
> games/cgames: Fix slack-desc. 
> games/cgmadness: Fix slack-desc. 
> games/cgoban: Fix slack-desc. 
> games/chessx: Fix slack-desc. 
> games/chocolate_duke3D: Fix slack-desc. 
> games/chromium-bsu: Fix slack-desc. 
> games/conquest: Fix slack-desc. 
> games/cowsay: Fix slack-desc. 
> games/curseofwar: Fix slack-desc. 
> games/cutemaze: Fix slack-desc. 
> games/doomretro: Updated for version 2.3.4. 
> games/dunelegacy: Fix slack-desc. 
> games/ecwolf: Fix slack-desc. 
> games/einstein: Fix slack-desc. 
> games/enigma: Fix slack-desc. 
> games/exult: Fix slack-desc. 
> games/fgo: Fix slack-desc. 
> games/fillets-ng-data: Fix slack-desc. 
> games/fillets-ng: Fix slack-desc. 
> games/flare: Fix slack-desc. 
> games/foobillardplus: Fix slack-desc. 
> games/fortune_doctor_who: Fix slack-desc. 
> games/freedoom: Fix slack-desc. 
> games/frogatto: Fix slack-desc. 
> games/frozen-bubble: Fix slack-desc. 
> games/fuse-emulator: Fix slack-desc. 
> games/galaxyv2: Fix slack-desc. 
> games/gemrb: Fix slack-desc. 
> games/gnubg: Fix slack-desc. 
> games/gnugo: Fix slack-desc. 
> games/gnuski: Fix slack-desc. 
> games/golly: Fix slack-desc. 
> games/gottet: Fix slack-desc. 
> games/hedgewars: Fix slack-desc. 
> games/hnefatafl: Fix slack-desc. 
> games/instead: Fix slack-desc. 
> games/jin: Fix slack-desc. 
> games/kildclient: Fix slack-desc. 
> games/lbreakout2: Fix slack-desc. 
> games/libretro-lutro: Fix slack-desc. 
> games/libretro-reicast: Fix slack-desc. 
> games/lincity-ng: Fix slack-desc. 
> games/ltris: Fix slack-desc. 
> games/lutris: Fix slack-desc. 
> games/marathon-evil-data: Fix slack-desc. 
> games/marathon-red-data: Fix slack-desc. 
> games/mog: Fix slack-desc. 
> games/mupen64plus: Fix slack-desc. 
> games/naev: Fix slack-desc. 
> games/neverball: Fix slack-desc. 
> games/nuvie: Fix slack-desc. 
> games/oolite: Fix slack-desc. 
> games/openarena: Fix slack-desc. 
> games/openmsx: Fix slack-desc. 
> games/openmw: Fix slack-desc. 
> games/openspades: Fix slack-desc. 
> games/openttd: Fix slack-desc. 
> games/pcsx2: Fix slack-desc. 
> games/pengupop: Fix slack-desc. 
> games/pingus: Fix slack-desc. 
> games/pokerth: Fix slack-desc. 
> games/qmc2: Fix slack-desc. 
> games/qstat: Fix slack-desc. 
> games/qtsixa: Fix slack-desc. 
> games/quakeforge: Fix slack-desc. 
> games/qxw: Fix slack-desc. 
> games/qzdl: Fix slack-desc. 
> games/redeclipse: Fix slack-desc. 
> games/rlvm: Fix slack-desc. 
> games/rocksndiamonds: Fix slack-desc. 
> games/rogue: Fix slack-desc. 
> games/sauerbraten: Fix slack-desc. 
> games/scid_vs_pc: Fix slack-desc. 
> games/scummvm: Fix slack-desc. 
> games/singularity: Fix slack-desc. 
> games/sokowiz: Fix slack-desc. 
> games/solarus-quest-editor: Fix slack-desc. 
> games/solarus: Fix slack-desc. 
> games/speed-dreams: Fix slack-desc. 
> games/spring: Fix slack-desc. 
> games/steam: Fix slack-desc. 
> games/stockfish: Fix slack-desc. 
> games/stone_soup: Fix slack-desc. 
> games/supertux: Fix slack-desc. 
> games/tintin: Fix slack-desc. 
> games/tmw: Fix slack-desc. 
> games/tmwmusic: Fix slack-desc. 
> games/tome4: Fix slack-desc. 
> games/tome: Fix slack-desc. 
> games/transfusion: Fix slack-desc. 
> games/tuxkart: Fix slack-desc. 
> games/tuxnes: Fix slack-desc. 
> games/ut2004: Fix slack-desc. 
> games/vectoroids: Fix slack-desc. 
> games/vms-empire: Fix slack-desc. 
> games/voxelands: Fix slack-desc. 
> games/warmux: Fix slack-desc. 
> games/wesnoth: Fix slack-desc. 
> games/wmquake: Fix slack-desc. 
> games/wordwarvi: Fix slack-desc. 
> games/xmahjongg: Fix slack-desc. 
> games/xonotic: Fix slack-desc. 
> games/xskat: Fix slack-desc. 
> games/yetris: Fix slack-desc. 
> games/zaz: Fix slack-desc. 
> games/zod-engine: Fix slack-desc. 
> games/zork: Fix slack-desc. 
> games/zsxd: Fix slack-desc. 
> gis/Geohash: Fix slack-desc. 
> gis/OWSLib: Fix slack-desc. 
> gis/cartopy: Fix slack-desc. 
> gis/cligj: Fix slack-desc. 
> gis/gdal: Fix slack-desc. 
> gis/geogig-py: Fix slack-desc. 
> gis/geojson: Fix slack-desc. 
> gis/geos: Fix slack-desc. 
> gis/google-earth: Fix slack-desc. 
> gis/josm: Fix slack-desc. 
> gis/laszip: Fix slack-desc. 
> gis/librasterlite: Fix slack-desc. 
> gis/libspatialite: Fix slack-desc. 
> gis/merkaartor: Fix slack-desc. 
> gis/mobac: Fix slack-desc. 
> gis/navit: Fix slack-desc. 
> gis/opencpn: Fix slack-desc. 
> gis/opengrads: Fix slack-desc. 
> gis/osm2pgrouting: Fix slack-desc. 
> gis/pdal: Fix slack-desc. 
> gis/pgsql-ogr-fdw: Fix slack-desc. 
> gis/pointcloud: Fix slack-desc. 
> gis/polyline: Fix slack-desc. 
> gis/postgis: Fix slack-desc. 
> gis/pyshp: Fix slack-desc. 
> gis/pyspatialite: Fix slack-desc. 
> gis/pytrainer: Fix slack-desc. 
> gis/qlandkartegt: Fix slack-desc. 
> gis/qmapshack: Fix slack-desc. 
> gis/saga-gis: Fix slack-desc. 
> gis/spatialite_gui: Fix slack-desc. 
> gis/tangogps: Fix slack-desc. 
> graphics/Alchemy: Fix slack-desc. 
> graphics/Blender: Updated for version 2.78a 
> graphics/HotShots: Fix slack-desc. 
> graphics/aewan: Fix slack-desc. 
> graphics/autotrace: Fix slack-desc. 
> graphics/blender: Fix slack-desc. 
> graphics/brlcad: Fix slack-desc. 
> graphics/dcraw: Fix slack-desc. 
> graphics/digikam: Fix slack-desc. 
> graphics/djview4: Fix slack-desc. 
> graphics/dvisvgm: Fix slack-desc. 
> graphics/enblend-enfuse: Fix slack-desc. 
> graphics/evolus-pencil: Fix slack-desc. 
> graphics/exif: Fix slack-desc. 
> graphics/fontforge: Fix slack-desc. 
> graphics/freewrl: Fix slack-desc. 
> graphics/gimagereader: Fix slack-desc. 
> graphics/gimp-feca_hdr-plugin: Fix slack-desc. 
> graphics/gimp-plugin-bimp: Fix slack-desc. 
> graphics/gliv: Fix slack-desc. 
> graphics/gmic: Fix slack-desc. 
> graphics/gnome-web-photo: Fix slack-desc. 
> graphics/gpicview: Fix slack-desc. 
> graphics/graph-easy: Fix slack-desc. 
> graphics/graphviz: Fix slack-desc. 
> graphics/gthumb: Fix slack-desc. 
> graphics/hugin: Fix slack-desc. 
> graphics/inkscape: Fix slack-desc. 
> graphics/kamerka: Fix slack-desc. 
> graphics/kuickshow: Fix slack-desc. 
> graphics/lcdtest: Fix slack-desc. 
> graphics/lilypond: Fix slack-desc. 
> graphics/luminance-hdr: Fix slack-desc. 
> graphics/makehuman: Fix slack-desc. 
> graphics/metapixel: Fix slack-desc. 
> graphics/mftrace: Fix slack-desc. 
> graphics/mirage: Fix slack-desc. 
> graphics/mitsuba: Fix slack-desc. 
> graphics/mtpaint: Fix slack-desc. 
> graphics/nvidia-cg-toolkit: Fix slack-desc. 
> graphics/openclipart: Fix slack-desc. 
> graphics/openimageio: Fix slack-desc. 
> graphics/optipng: Fix slack-desc. 
> graphics/pdf2png: Fix slack-desc. 
> graphics/pdf2svg: Fix slack-desc. 
> graphics/photivo: Fix slack-desc. 
> graphics/phototonic: Fix slack-desc. 
> graphics/pinta: Fix slack-desc. 
> graphics/potrace: Fix slack-desc. 
> graphics/qelectrotech: Fix slack-desc. 
> graphics/rawstudio: Fix slack-desc. 
> graphics/rawtherapee: Fix slack-desc. 
> graphics/resynthesizer: Fix slack-desc. 
> graphics/scantailor: Fix slack-desc. 
> graphics/screencloud: Fix slack-desc. 
> graphics/simple-scan: Fix slack-desc. 
> graphics/simple-scan: Updated for version 3.22.0.1. 
> graphics/teighafileconverter: Update DOWNLOAD url. 
> graphics/teighaviewers: Update DOWNLOAD url. 
> graphics/tesseract: Fix slack-desc. 
> graphics/textext: Fix slack-desc. 
> graphics/tkpng: Fix slack-desc. 
> graphics/ufraw: Fix slack-desc. 
> graphics/uniconvertor: Fix slack-desc. 
> graphics/viewnior: Fix slack-desc. 
> graphics/vips: Fix slack-desc. 
> graphics/vuescan: Fix slack-desc. 
> graphics/wavelet-denoise: Fix slack-desc. 
> graphics/whyteboard: Fix slack-desc. 
> graphics/xbmbrowser: Fix slack-desc. 
> graphics/xcalib: Fix slack-desc. 
> graphics/xmedcon: Fix slack-desc. 
> graphics/yafaray-blender: Fix slack-desc. 
> graphics/yafaray: Fix slack-desc. 
> ham/7plus: Fix slack-desc. 
> ham/aldo: Fix slack-desc. 
> ham/aprx: Fix slack-desc. 
> ham/baudline: Fix slack-desc. 
> ham/chirp: Fix slack-desc. 
> ham/cqrlog: Fix slack-desc. 
> ham/cwdaemon: Fix slack-desc. 
> ham/demorse: Fix slack-desc. 
> ham/direwolf: Fix slack-desc. 
> ham/dxcc: Fix slack-desc. 
> ham/ebook2cw: Fix slack-desc. 
> ham/ebook2cwgui: Fix slack-desc. 
> ham/gridloc: Fix slack-desc. 
> ham/grig: Fix slack-desc. 
> ham/psk31lx: Fix slack-desc. 
> ham/qradiopredict: Fix slack-desc. 
> ham/qrq: Fix slack-desc. 
> ham/svxlink-sounds-en_US-heather-16k: Fix slack-desc. 
> ham/svxlink: Fix slack-desc. 
> ham/tqsl: Fix slack-desc. 
> ham/twhamqth: Fix slack-desc. 
> ham/wxapt: Fix slack-desc. 
> ham/xanalyser: Fix slack-desc. 
> ham/xdemorse: Fix slack-desc. 
> ham/xfhell: Fix slack-desc. 
> ham/xpsk31: Fix slack-desc. 
> ham/xwxapt: Fix slack-desc. 
> haskell/haskell-Crypto: Fix slack-desc. 
> haskell/haskell-cryptonite: Fix slack-desc. 
> haskell/haskell-idna: Fix slack-desc. 
> haskell/haskell-shellish: Fix slack-desc. 
> libraries/ETL: Fix slack-desc. 
> libraries/GitPython: Fix slack-desc. 
> libraries/LucenePlusPlus: Fix slack-desc. 
> libraries/OpenBLAS: Fix slack-desc. 
> libraries/VitaMTP: Fix slack-desc. 
> libraries/activemq-cpp: Fix slack-desc. 
> libraries/agg: Fix slack-desc. 
> libraries/allegro: Fix slack-desc. 
> libraries/ant-contrib: Fix slack-desc. 
> libraries/appmenu-qt: Fix slack-desc. 
> libraries/aqbanking: Fix slack-desc. 
> libraries/atlas: Fix slack-desc. 
> libraries/backports-ssl-match-hostname: Fix slack-desc. 
> libraries/bamf: Fix slack-desc. 
> libraries/batinfo: Fix slack-desc. 
> libraries/blas: Fix slack-desc. 
> libraries/boolstuff: Fix slack-desc. 
> libraries/botocore: Fix slack-desc. 
> libraries/buddy: Fix slack-desc. 
> libraries/bullet: Fix slack-desc. 
> libraries/cal3d: Fix slack-desc. 
> libraries/ccrtp: Fix slack-desc. 
> libraries/clalsadrv: Fix slack-desc. 
> libraries/collada-dom: Fix slack-desc. 
> libraries/compface: Fix slack-desc. 
> libraries/compiz-plugins-experimental: Fix slack-desc. 
> libraries/confuse: Fix slack-desc. 
> libraries/console_bridge: Fix slack-desc. 
> libraries/ctemplate: Fix slack-desc. 
> libraries/db46: Fix slack-desc. 
> libraries/dbus-sharp-glib: Fix slack-desc. 
> libraries/dietlibc: Fix slack-desc. 
> libraries/discogs-client: Fix slack-desc. 
> libraries/dotconf: Fix slack-desc. 
> libraries/dropbox-python: Fix slack-desc. 
> libraries/e_dbus: Fix slack-desc. 
> libraries/ecore: Fix slack-desc. 
> libraries/edje: Fix slack-desc. 
> libraries/eet: Fix slack-desc. 
> libraries/efreet: Fix slack-desc. 
> libraries/eina: Fix slack-desc. 
> libraries/eio: Fix slack-desc. 
> libraries/embryo: Fix slack-desc. 
> libraries/enum34: Fix slack-desc. 
> libraries/evas: Fix slack-desc. 
> libraries/exempi: Fix slack-desc. 
> libraries/ffms2: Fix slack-desc. 
> libraries/fltk: Fix slack-desc. 
> libraries/fpconst: Fix slack-desc. 
> libraries/freealut: Fix slack-desc. 
> libraries/freexl: Fix slack-desc. 
> libraries/ftgl: Fix slack-desc. 
> libraries/fuzzylite: Fix slack-desc. 
> libraries/ganv: Fix slack-desc. 
> libraries/genshi: Fix slack-desc. 
> libraries/geshi: Fix slack-desc. 
> libraries/glfw3: Fix slack-desc. 
> libraries/glfw: Fix slack-desc. 
> libraries/gnet: Fix slack-desc. 
> libraries/goffice0.8: Fix slack-desc. 
> libraries/goffice: Fix slack-desc. 
> libraries/gsnmp: Fix slack-desc. 
> libraries/gtk-aurora-engine: Fix slack-desc. 
> libraries/gtkdatabox: Fix slack-desc. 
> libraries/gtkglarea: Fix slack-desc. 
> libraries/gtkglext: Fix slack-desc. 
> libraries/gtkhotkey: Fix slack-desc. 
> libraries/gtksourceview3: Fix slack-desc. 
> libraries/gts: Fix slack-desc. 
> libraries/gupnp: Fix slack-desc. 
> libraries/gwenhywfar: Fix slack-desc. 
> libraries/hdf: Fix slack-desc. 
> libraries/hurry-filesize: Fix slack-desc. 
> libraries/imlib2: Fix slack-desc. 
> libraries/itcl: Fix slack-desc. 
> libraries/jai-imageio: Fix slack-desc. 
> libraries/javacomm: Fix slack-desc. 
> libraries/jbigkit: Fix slack-desc. 
> libraries/json-glib: Fix slack-desc. 
> libraries/lablgtk: Fix slack-desc. 
> libraries/lame: Fix slack-desc. 
> libraries/lapack-atlas: Fix slack-desc. 
> libraries/lapack: Fix slack-desc. 
> libraries/leptonica: Fix slack-desc. 
> libraries/libAfterImage: Fix slack-desc. 
> libraries/libaaio: Fix slack-desc. 
> libraries/libasr: Fix slack-desc. 
> libraries/libass: Fix slack-desc. 
> libraries/libbonoboui: Fix slack-desc. 
> libraries/libchewing: Fix slack-desc. 
> libraries/libcitadel: Fix slack-desc. 
> libraries/libcmis: Fix slack-desc. 
> libraries/libcryptui: Fix slack-desc. 
> libraries/libcsv: Fix slack-desc. 
> libraries/libcuefile: Fix slack-desc. 
> libraries/libdbusmenu: Fix slack-desc. 
> libraries/libe-book: Fix slack-desc. 
> libraries/libearth: Fix slack-desc. 
> libraries/libeot: Fix slack-desc. 
> libraries/libesmtp: Fix slack-desc. 
> libraries/libetpan: Fix slack-desc. 
> libraries/libexif-gtk: Fix slack-desc. 
> libraries/libexttextcat: Fix slack-desc. 
> libraries/libfdk-aac: Fix slack-desc. 
> libraries/libfsntfs: Fix slack-desc. 
> libraries/libftdi1: Fix slack-desc. 
> libraries/libfvde: Fix slack-desc. 
> libraries/libfwnt: Fix slack-desc. 
> libraries/libfwsi: Fix slack-desc. 
> libraries/libg15: Fix slack-desc. 
> libraries/libg15render: Fix slack-desc. 
> libraries/libgaiagraphics: Fix slack-desc. 
> libraries/libgcrypt15: Fix slack-desc. 
> libraries/libglpng: Fix slack-desc. 
> libraries/libgltf: Fix slack-desc. 
> libraries/libgtop: Fix slack-desc. 
> libraries/libilbc: Fix slack-desc. 
> libraries/libinstpatch: Fix slack-desc. 
> libraries/libkqueue: Fix slack-desc. 
> libraries/libmatroska: Fix slack-desc. 
> libraries/libmemcached: Fix slack-desc. 
> libraries/libmirage: Fix slack-desc. 
> libraries/libmp3splt: Fix slack-desc. 
> libraries/libmusicbrainz: Fix slack-desc. 
> libraries/libnxml: Fix slack-desc. 
> libraries/libofa: Fix slack-desc. 
> libraries/libofx: Fix slack-desc. 
> libraries/liboglappth: Fix slack-desc. 
> libraries/liboop: Fix slack-desc. 
> libraries/libotr: Fix slack-desc. 
> libraries/libpff: Fix slack-desc. 
> libraries/libpseudo: Fix slack-desc. 
> libraries/libpwquality: Fix slack-desc. 
> libraries/libqcow: Fix slack-desc. 
> libraries/libquvi-scripts: Fix slack-desc. 
> libraries/libqxt: Fix slack-desc. 
> libraries/librapi2: Fix slack-desc. 
> libraries/librsync: Fix slack-desc. 
> libraries/librtfcomp: Fix slack-desc. 
> libraries/libscrypt: Fix slack-desc. 
> libraries/libsidplay2: Fix slack-desc. 
> libraries/libsigscan: Fix slack-desc. 
> libraries/libsmdev: Fix slack-desc. 
> libraries/libsmf: Fix slack-desc. 
> libraries/libsmi: Fix slack-desc. 
> libraries/libsuinput: Fix slack-desc. 
> libraries/libsunpinyin: Fix slack-desc. 
> libraries/libsynce: Fix slack-desc. 
> libraries/libtelnet: Fix slack-desc. 
> libraries/libtermkey: Fix slack-desc. 
> libraries/libu2f-host: Fix slack-desc. 
> libraries/libunibreak: Fix slack-desc. 
> libraries/libuv: Fix slack-desc. 
> libraries/libvhdi: Fix slack-desc. 
> libraries/libvidcap: Fix slack-desc. 
> libraries/libviper: Fix slack-desc. 
> libraries/libvmdk: Fix slack-desc. 
> libraries/libvorbisidec: Fix slack-desc. 
> libraries/libvshadow: Fix slack-desc. 
> libraries/libvslvm: Fix slack-desc. 
> libraries/libvterm: Fix slack-desc. 
> libraries/libwebsockets: Fix slack-desc. 
> libraries/libxfcegui4: Fix slack-desc. 
> libraries/libxnvctrl: Fix slack-desc. 
> libraries/libzrtpcpp: Fix slack-desc. 
> libraries/linphone-srtp: Fix slack-desc. 
> libraries/live555: Fix slack-desc. 
> libraries/lksctp-tools: Fix slack-desc. 
> libraries/lockdev: Fix slack-desc. 
> libraries/lua-MessagePack: Fix slack-desc. 
> libraries/lua-cmsgpack: Fix slack-desc. 
> libraries/lua-lpeg: Fix slack-desc. 
> libraries/lua-md5: Fix slack-desc. 
> libraries/luadbi: Fix slack-desc. 
> libraries/luaexpat: Fix slack-desc. 
> libraries/luasocket: Fix slack-desc. 
> libraries/manubulon-snmp-plugins: Fix slack-desc. 
> libraries/mathgl: Fix slack-desc. 
> libraries/mdds: Fix slack-desc. 
> libraries/meanwhile: Fix slack-desc. 
> libraries/mujs: Fix slack-desc. 
> libraries/mxml: Updated for version 2.10. 
> libraries/mysql-connector-python: Fix slack-desc. 
> libraries/netcdf: Fix slack-desc. 
> libraries/nextaw: Fix slack-desc. 
> libraries/npth: Fix slack-desc. 
> libraries/opal: Fix slack-desc. 
> libraries/opencv: Fix slack-desc. 
> libraries/pgtcl-ng: Fix slack-desc. 
> libraries/php-oci8: Fix slack-desc. 
> libraries/physfs: Fix slack-desc. 
> libraries/pies2overrides: Fix slack-desc. 
> libraries/plib: Fix slack-desc. 
> libraries/podofo: Fix slack-desc. 
> libraries/polyclipping: Added (polygon/line clipping & offsetting). 
> libraries/ptlib: Fix slack-desc. 
> libraries/ptypes: Fix slack-desc. 
> libraries/purple-plugin_pack: Fix slack-desc. 
> libraries/pyPEG2: Fix slack-desc. 
> libraries/pybloomfiltermmap: Fix slack-desc. 
> libraries/pymdstat: Fix slack-desc. 
> libraries/pysendfile: Fix slack-desc. 
> libraries/python3-PyQt5: Fix slack-desc. 
> libraries/qt3: Fix slack-desc. 
> libraries/quazip: Fix slack-desc. 
> libraries/quesoglc: Fix slack-desc. 
> libraries/qwt: Fix slack-desc. 
> libraries/rep-gtk: Fix slack-desc. 
> libraries/rxtx: Fix slack-desc. 
> libraries/secp256k1: Fix slack-desc. 
> libraries/slib: Fix slack-desc. 
> libraries/squish: Fix slack-desc. 
> libraries/stfl: Fix slack-desc. 
> libraries/stk: Fix slack-desc. 
> libraries/swfdec: Fix slack-desc. 
> libraries/tkimg: Fix slack-desc. 
> libraries/tls: Fix slack-desc. 
> libraries/tolua++: Fix slack-desc. 
> libraries/tre: Fix slack-desc. 
> libraries/trilinos: Fix slack-desc. 
> libraries/unibilium: Fix slack-desc. 
> libraries/urdfdom: Fix slack-desc. 
> libraries/urdfdom_headers: Fix slack-desc. 
> libraries/uuid: Fix slack-desc. 
> libraries/webkit2gtk: Updated for version 2.14.2. 
> libraries/webkitgtk3: Fix slack-desc. 
> libraries/webkitgtk: Fix slack-desc. 
> libraries/wjelement: Fix slack-desc. 
> libraries/wvstreams: Fix slack-desc. 
> libraries/wxSQLite3: Fix slack-desc. 
> libraries/wxsvg: Fix slack-desc. 
> libraries/xalan: Fix slack-desc. 
> libraries/xawplus: Fix slack-desc. 
> libraries/xcb-util-xrm: Fix slack-desc. 
> libraries/xerces: Fix slack-desc. 
> libraries/xforms: Fix slack-desc. 
> libraries/xlt: Fix slack-desc. 
> libraries/xmlgen: Fix slack-desc. 
> libraries/xmlsec: Fix slack-desc. 
> libraries/xview: Fix slack-desc. 
> libraries/yaz: Fix slack-desc. 
> libraries/zsi: Fix slack-desc. 
> misc/Colormake: Fix slack-desc. 
> misc/KeePassHttp: Fix slack-desc. 
> misc/QCMA: Fix slack-desc. 
> misc/abgx360gui: Fix slack-desc. 
> misc/bbrun: Fix slack-desc. 
> misc/bchunk: Fix slack-desc. 
> misc/boncuk: Fix slack-desc. 
> misc/boxes: Fix slack-desc. 
> misc/clawsker: Fix slack-desc. 
> misc/doclifter: Fix slack-desc. 
> misc/fcitx-mozc: Fix slack-desc. 
> misc/fcrackzip: Fix slack-desc. 
> misc/figlet: Fix slack-desc. 
> misc/g15composer: Fix slack-desc. 
> misc/g15daemon: Fix slack-desc. 
> misc/g15stats: Fix slack-desc. 
> misc/glogg: Fix slack-desc. 
> misc/gnome-mime-data: Fix slack-desc. 
> misc/gourmet: Fix slack-desc. 
> misc/gprename: Fix slack-desc. 
> misc/gramps: Fix slack-desc. 
> misc/grc: Fix slack-desc. 
> misc/gxmessage: Fix slack-desc. 
> misc/hoorex: Fix slack-desc. 
> misc/ibus-skk: Fix slack-desc. 
> misc/ibus: Fix slack-desc. 
> misc/iscan-proprietary-drivers: Fix slack-desc. 
> misc/kasumi: Fix slack-desc. 
> misc/kcm-fcitx: Fix slack-desc. 
> misc/keychain: Fix slack-desc. 
> misc/mdic: Fix slack-desc. 
> misc/megatunix: Fix slack-desc. 
> misc/nfoview: Fix slack-desc. 
> misc/owfs: Fix slack-desc. 
> misc/par2cmdline: Fix slack-desc. 
> misc/pinfo: Fix slack-desc. 
> misc/po4a: Fix slack-desc. 
> misc/portecle: Fix slack-desc. 
> misc/rarcrack: Fix slack-desc. 
> misc/samdump2: Fix slack-desc. 
> misc/scim-chewing: Fix slack-desc. 
> misc/sdcv: Fix slack-desc. 
> misc/spotlighter: Fix slack-desc. 
> misc/stardict-tools: Fix slack-desc. 
> misc/sutils: Fix slack-desc. 
> misc/toilet: Fix slack-desc. 
> misc/torrentinfo: Fix slack-desc. 
> misc/utimer: Fix slack-desc. 
> misc/wcd: Fix slack-desc. 
> misc/weather: Fix slack-desc. 
> misc/wmbday: Fix slack-desc. 
> misc/xca: Fix slack-desc. 
> misc/xcape: Fix slack-desc. 
> misc/xclip: Fix slack-desc. 
> misc/xwinwrap: Fix slack-desc. 
> misc/yapet: Fix slack-desc. 
> misc/yara: Fix slack-desc. 
> misc/ydpdict: Fix slack-desc. 
> misc/zinnia: Fix slack-desc. 
> multimedia/DivFix++: Fix slack-desc. 
> multimedia/ExMplayer: Fix slack-desc. 
> multimedia/TeamSpeak3: Fix slack-desc. 
> multimedia/Yolo: Fix slack-desc. 
> multimedia/aces-dev: Fix slack-desc. 
> multimedia/aces_container: Fix slack-desc. 
> multimedia/aegisub: Fix slack-desc. 
> multimedia/apetag: Fix slack-desc. 
> multimedia/audiopreview: Fix slack-desc. 
> multimedia/avidemux: Fix slack-desc. 
> multimedia/ccxstream: Fix slack-desc. 
> multimedia/cowbell: Fix slack-desc. 
> multimedia/cuetools: Fix slack-desc. 
> multimedia/devedeng: Fix slack-desc. 
> multimedia/dvd-slideshow: Fix slack-desc. 
> multimedia/dvdrip: Fix slack-desc. 
> multimedia/dvdstyler: Fix slack-desc. 
> multimedia/dvgrab: Fix slack-desc. 
> multimedia/emoc: Fix slack-desc. 
> multimedia/exaile: Fix slack-desc. 
> multimedia/farsight2: Fix slack-desc. 
> multimedia/farstream: Fix slack-desc. 
> multimedia/fdkaac: Fix slack-desc. 
> multimedia/ffmpegyag: Fix slack-desc. 
> multimedia/flashplayer-plugin: Fix slack-desc. 
> multimedia/gigedit: Fix slack-desc. 
> multimedia/glyr: Fix slack-desc. 
> multimedia/gnash: Fix slack-desc. 
> multimedia/google-talkplugin: Fix slack-desc. 
> multimedia/gpac: Fix slack-desc. 
> multimedia/gpodder: Fix slack-desc. 
> multimedia/gtick: Fix slack-desc. 
> multimedia/gtk-recordmydesktop: Fix slack-desc. 
> multimedia/hexter: Fix slack-desc. 
> multimedia/huludesktop: Fix slack-desc. 
> multimedia/iat: Fix slack-desc. 
> multimedia/kaffeine-mozilla: Fix slack-desc. 
> multimedia/kaffeine: Fix slack-desc. 
> multimedia/kdenlive: Fix slack-desc. 
> multimedia/kino: Fix slack-desc. 
> multimedia/l-smash: Fix slack-desc. 
> multimedia/lives: Fix slack-desc. 
> multimedia/lwks: Fix slack-desc. 
> multimedia/minitube: Fix slack-desc. 
> multimedia/mkvtoolnix: Fix slack-desc. 
> multimedia/mlt: Fix slack-desc. 
> multimedia/mpv: Fix slack-desc. 
> multimedia/mythplugins: Fix slack-desc. 
> multimedia/mythtv: Fix slack-desc. 
> multimedia/nightingale: Fix slack-desc. 
> multimedia/obs-studio: Fix slack-desc. 
> multimedia/oggconvert: Fix slack-desc. 
> multimedia/openshot: Fix slack-desc. 
> multimedia/pepperflash-plugin: Fix slack-desc. 
> multimedia/picard-plugins: Fix slack-desc. 
> multimedia/pitivi: Fix slack-desc. 
> multimedia/plex-home-theater: Fix slack-desc. 
> multimedia/popcorntime: Fix slack-desc. 
> multimedia/pyradio: Fix slack-desc. 
> multimedia/qsampler: Fix slack-desc. 
> multimedia/realplayer: Fix slack-desc. 
> multimedia/rosa-media-player: Fix slack-desc. 
> multimedia/schroedinger: Fix slack-desc. 
> multimedia/sinthgunt: Fix slack-desc. 
> multimedia/spek: Fix slack-desc. 
> multimedia/subtitleeditor: Fix slack-desc. 
> multimedia/tabu_audio_player: Fix slack-desc. 
> multimedia/telepathy-farstream: Fix slack-desc. 
> multimedia/telepathy-glib: Fix slack-desc. 
> multimedia/tivodecode: Fix slack-desc. 
> multimedia/tstools: Fix slack-desc. 
> multimedia/tvheadend: Fix slack-desc. 
> multimedia/umplayer: Fix slack-desc. 
> multimedia/vobcopy: Fix slack-desc. 
> multimedia/xjadeo: Fix slack-desc. 
> multimedia/xmltv: Fix slack-desc. 
> multimedia/xvid4conf: Fix slack-desc. 
> multimedia/xvidcore: Fix slack-desc. 
> network/DarTui: Fix slack-desc. 
> network/FireWorks: Fix slack-desc. 
> network/LOIC: Fix slack-desc. 
> network/PaleMoon: Fix slack-desc. 
> network/aggregate: Fix slack-desc. 
> network/aiccu: Fix slack-desc. 
> network/amap: Fix slack-desc. 
> network/aoetools: Fix slack-desc. 
> network/authbind: Fix slack-desc. 
> network/axel: Fix slack-desc. 
> network/bip: Fix slack-desc. 
> network/bottle: Fix slack-desc. 
> network/bsflite: Fix slack-desc. 
> network/cgterm: Fix slack-desc. 
> network/cherokee: Fix slack-desc. 
> network/choqok: Fix slack-desc. 
> network/ckermit: Fix slack-desc. 
> network/claws-mail: Fix slack-desc. 
> network/clive: Fix slack-desc. 
> network/comgt: Fix slack-desc. 
> network/corkscrew: Fix slack-desc. 
> network/darkstat: Fix slack-desc. 
> network/davmail: Fix slack-desc. 
> network/dclib: Fix slack-desc. 
> network/ddclient: Fix slack-desc. 
> network/deluge: Fix slack-desc. 
> network/dianara: Fix slack-desc. 
> network/dkimproxy: Fix slack-desc. 
> network/dnstop: Fix slack-desc. 
> network/dokuwiki: Fix slack-desc. 
> network/dovecot-pigeonhole: Fix slack-desc. 
> network/dropbox: Fix slack-desc. 
> network/easyrsa: Fix slack-desc. 
> network/eiskaltdcpp: Fix slack-desc. 
> network/ekiga: Fix slack-desc. 
> network/emesene: Fix slack-desc. 
> network/enet: Fix slack-desc. 
> network/etherape: Fix slack-desc. 
> network/etherpad-lite: Fix slack-desc. 
> network/ettercap-NG: Fix slack-desc. 
> network/exim: Fix slack-desc. 
> network/fail2ban: Fix slack-desc. 
> network/fcgiwrap: Fix slack-desc. 
> network/fping6: Fix slack-desc. 
> network/fping: Fix slack-desc. 
> network/freeradius-server: Fix slack-desc. 
> network/ftp-cloudfs: Fix slack-desc. 
> network/gajim: Fix slack-desc. 
> network/ganglia-web: Fix slack-desc. 
> network/geoipupdate: Fix slack-desc. 
> network/glusterfs: Fix slack-desc. 
> network/gns3: Fix slack-desc. 
> network/googlecl: Fix slack-desc. 
> network/gq: Fix slack-desc. 
> network/guacamole-client: Fix slack-desc. 
> network/guacamole-server: Fix slack-desc. 
> network/gui-ufw: Fix slack-desc. 
> network/hamachi: Fix slack-desc. 
> network/havp: Fix slack-desc. 
> network/hiawatha: Fix slack-desc. 
> network/hostsblock: Fix slack-desc. 
> network/hping3: Fix slack-desc. 
> network/httping: Fix slack-desc. 
> network/hydra: Fix slack-desc. 
> network/ifstatus: Fix slack-desc. 
> network/ii: Fix slack-desc. 
> network/imapfilter: Fix slack-desc. 
> network/iperf3: Fix slack-desc. 
> network/iperf: Fix slack-desc. 
> network/ipscan: Fix slack-desc. 
> network/ipvsadm: Fix slack-desc. 
> network/jboss-as: Fix slack-desc. 
> network/kcm_ufw: Fix slack-desc. 
> network/keybase-client: Fix slack-desc. 
> network/kfilebox: Fix slack-desc. 
> network/kismet: Fix slack-desc. 
> network/kmess: Fix slack-desc. 
> network/konversation: Fix slack-desc. 
> network/kvirc: Fix slack-desc. 
> network/kwakd: Fix slack-desc. 
> network/leafnode: Fix slack-desc. 
> network/leechcraft: Fix slack-desc. 
> network/libdnet: Fix slack-desc. 
> network/licq: Fix slack-desc. 
> network/livestreamer: Fix slack-desc. 
> network/mailman: Fix slack-desc. 
> network/malheur: Fix slack-desc. 
> network/megatools: Fix slack-desc. 
> network/metasploit: Fix slack-desc. 
> network/mew: Fix slack-desc. 
> network/milter-greylist: Fix slack-desc. 
> network/mitter: Fix slack-desc. 
> network/mldonkey: Fix slack-desc. 
> network/mod_auth_kerb: Fix slack-desc. 
> network/mod_chroot: Fix slack-desc. 
> network/mod_geoip2: Fix slack-desc. 
> network/modsecurity-apache: Fix slack-desc. 
> network/monkey: Fix slack-desc. 
> network/mrtg: Fix slack-desc. 
> network/msmtp: Fix slack-desc. 
> network/mumble: Fix slack-desc. 
> network/museek+: Fix slack-desc. 
> network/mysecureshell: Fix slack-desc. 
> network/nagios: Fix slack-desc. 
> network/nagiosgraph: Fix slack-desc. 
> network/netcat-openbsd: Fix slack-desc. 
> network/netcat: Fix slack-desc. 
> network/nethogs: Fix slack-desc. 
> network/netperf: Fix slack-desc. 
> network/netstat-nat: Fix slack-desc. 
> network/newsbeuter: Fix slack-desc. 
> network/nfdump: Fix slack-desc. 
> network/nicotine+: Fix slack-desc. 
> network/nikto: Fix slack-desc. 
> network/nmh: Fix slack-desc. 
> network/noip2: Fix slack-desc. 
> network/nss-mdns: Fix slack-desc. 
> network/ntpclient: Fix slack-desc. 
> network/openconnect: Fix slack-desc. 
> network/opendchub: Fix slack-desc. 
> network/opendkim: Fix slack-desc. 
> network/openl2tp: Fix slack-desc. 
> network/openntpd: Fix slack-desc. 
> network/openresolv: Fix slack-desc. 
> network/openvswitch-utils: Fix slack-desc. 
> network/opera-developer: Updated for version 43.0.2403.0. 
> network/opera-legacy: Fix slack-desc. 
> network/opera: Updated for version 41.0.2353.56. 
> network/packETH: Fix slack-desc. 
> network/packit: Fix slack-desc. 
> network/palemoon: Fix slack-desc. 
> network/pastebincl: Fix slack-desc. 
> network/pentadactyl: Fix slack-desc. 
> network/pflogsumm: Fix slack-desc. 
> network/pgbouncer: Fix slack-desc. 
> network/pgl: Fix slack-desc. 
> network/phodav: Fix slack-desc. 
> network/pidgin-musictracker: Fix slack-desc. 
> network/pidgin-otr: Fix slack-desc. 
> network/pidgin-skypeweb: Fix slack-desc. 
> network/pidgin-skypeweb: Updated for version 1.2.2. 
> network/pidgin-sound: Fix slack-desc. 
> network/pidgin-visnotes: Fix slack-desc. 
> network/policyd2: Fix slack-desc. 
> network/polipo: Fix slack-desc. 
> network/privoxy: Fix slack-desc. 
> network/proxytunnel: Fix slack-desc. 
> network/psi: Fix slack-desc. 
> network/ptokax: Fix slack-desc. 
> network/pure-ftpd: Fix slack-desc. 
> network/purple-facebook: Fix slack-desc. 
> network/pyNeighborhood: Fix slack-desc. 
> network/pydio-agent: Fix slack-desc. 
> network/pydio-sync: Fix slack-desc. 
> network/qbittorrent: Fix slack-desc. 
> network/quagga: Fix slack-desc. 
> network/radicale: Fix slack-desc. 
> network/radvd: Fix slack-desc. 
> network/retroshare: Fix slack-desc. 
> network/roger-router: Fix slack-desc. 
> network/rtl8188eu: Fix slack-desc. 
> network/scapy: Fix slack-desc. 
> network/sftp-cloudfs: Fix slack-desc. 
> network/silc-toolkit: Fix slack-desc. 
> network/sipp: Fix slack-desc. 
> network/skype: Fix slack-desc. 
> network/slack: Fix slack-desc. 
> network/smcroute: Fix slack-desc. 
> network/sniffjoke: Fix slack-desc. 
> network/snmptt: Fix slack-desc. 
> network/snort: Fix slack-desc. 
> network/squid: Fix slack-desc. 
> network/squidGuard: Fix slack-desc. 
> network/squidanalyzer: Fix slack-desc. 
> network/sshpass: Fix slack-desc. 
> network/sslscan: Fix slack-desc. 
> network/ssmtp: Fix slack-desc. 
> network/sstp-client: Fix slack-desc. 
> network/ssvnc: Fix slack-desc. 
> network/sylpheed: Fix slack-desc. 
> network/synergy: Fix slack-desc. 
> network/t38modem: Fix slack-desc. 
> network/tcpflow: Fix slack-desc. 
> network/tramp: Fix slack-desc. 
> network/translate: Fix slack-desc. 
> network/transmission-remote-gtk: Fix slack-desc. 
> network/tucan: Fix slack-desc. 
> network/tunctl: Fix slack-desc. 
> network/twitter: Fix slack-desc. 
> network/uTox: Fix slack-desc. 
> network/udpxy: Fix slack-desc. 
> network/ufw: Fix slack-desc. 
> network/unbound: Fix slack-desc. 
> network/users-agent: Fix slack-desc. 
> network/uudeview: Fix slack-desc. 
> network/vacuum-im: Fix slack-desc. 
> network/valknut: Fix slack-desc. 
> network/vblade: Fix slack-desc. 
> network/vde2: Fix slack-desc. 
> network/verlihub: Fix slack-desc. 
> network/viber: Fix slack-desc. 
> network/vidalia: Fix slack-desc. 
> network/vivaldi: Fix slack-desc. 
> network/vmware-horizon-client: Fix slack-desc. 
> network/vpnc: Fix slack-desc. 
> network/wakeonlan: Fix slack-desc. 
> network/wavemon: Fix slack-desc. 
> network/weathercli: Fix slack-desc. 
> network/webalizer: Fix slack-desc. 
> network/wildfly: Fix slack-desc. 
> network/wire: Fix slack-desc. 
> network/wmget: Fix slack-desc. 
> network/wmnd: Fix slack-desc. 
> network/wmnotify: Fix slack-desc. 
> network/xdman: Fix slack-desc. 
> network/xinetd: Fix slack-desc. 
> network/xnetload: Fix slack-desc. 
> network/yadifa: Fix slack-desc. 
> network/yoda: Fix slack-desc. 
> network/znc: Fix slack-desc. 
> office/abiword: Fix slack-desc. 
> office/adobe-reader-fontpacks: Fix slack-desc. 
> office/aigaion: Fix slack-desc. 
> office/aiksaurus: Fix slack-desc. 
> office/asymptote: Fix slack-desc. 
> office/beaver: Fix slack-desc. 
> office/bookbinder: Fix slack-desc. 
> office/briss: Fix slack-desc. 
> office/broffice.org: Fix slack-desc. 
> office/calcurse: Fix slack-desc. 
> office/calibre: Fix slack-desc. 
> office/devtodo: Fix slack-desc. 
> office/ding: Fix slack-desc. 
> office/docx2txt: Fix slack-desc. 
> office/elyxer: Fix slack-desc. 
> office/epdfview: Fix slack-desc. 
> office/etmtk: Fix slack-desc. 
> office/fbreader: Fix slack-desc. 
> office/flowkeeper: Fix slack-desc. 
> office/focuswriter: Fix slack-desc. 
> office/ganttproject: Fix slack-desc. 
> office/gcal: Fix slack-desc. 
> office/gnumeric: Fix slack-desc. 
> office/homebank: Fix slack-desc. 
> office/hunspell-de: Fix slack-desc. 
> office/hunspell-pl: Update DOWNLOAD url. 
> office/jstock: Fix slack-desc. 
> office/kate-latex-plugin: Fix slack-desc. 
> office/kbgoffice: Fix slack-desc. 
> office/kbibtex: Fix slack-desc. 
> office/kchmviewer-qt: Fix slack-desc. 
> office/kchmviewer: Fix slack-desc. 
> office/keepassx: Fix slack-desc. 
> office/libreoffice-helppack: Fix slack-desc. 
> office/libreoffice-langpack: Fix slack-desc. 
> office/libreoffice: Fix slack-desc. 
> office/lout: Fix slack-desc. 
> office/lyx: Fix slack-desc. 
> office/mdbtools: Fix slack-desc. 
> office/moneydance: Fix slack-desc. 
> office/notmuch: Fix slack-desc. 
> office/openoffice.org: Fix slack-desc. 
> office/org-mode: Fix slack-desc. 
> office/osmo: Fix slack-desc. 
> office/paps: Fix slack-desc. 
> office/pdf2djvu: Fix slack-desc. 
> office/pdfchain: Fix slack-desc. 
> office/pdfjam: Fix slack-desc. 
> office/ps2eps: Fix slack-desc. 
> office/pstotext: Fix slack-desc. 
> office/python-gcalcli: Fix slack-desc. 
> office/rednotebook: Fix slack-desc. 
> office/referencer: Fix slack-desc. 
> office/sc-im: Fix slack-desc. 
> office/scribus: Fix slack-desc. 
> office/taskd: Fix slack-desc. 
> office/tasksh: Fix slack-desc. 
> office/tellico: Fix slack-desc. 
> office/texlive: Fix slack-desc. 
> office/texmacs: Fix slack-desc. 
> office/texworks: Fix slack-desc. 
> office/timetrap: Fix slack-desc. 
> office/treesheets: Fix slack-desc. 
> office/unoconv: Fix slack-desc. 
> office/verbiste: Fix slack-desc. 
> office/xmind: Fix slack-desc. 
> office/xpad: Fix slack-desc. 
> office/xtrkcad: Fix slack-desc. 
> perl/mod_perl: Fix slack-desc. 
> perl/perl-Archive-Zip: Fix slack-desc. 
> perl/perl-Canary-Stability: Fix slack-desc. 
> perl/perl-Class-Gomor: Fix slack-desc. 
> perl/perl-Convert-UU: Fix slack-desc. 
> perl/perl-Convert-UUlib: Fix slack-desc. 
> perl/perl-Danga-Socket: Fix slack-desc. 
> perl/perl-Date-Calc: Fix slack-desc. 
> perl/perl-Encode-ISO2022: Fix slack-desc. 
> perl/perl-Encode-JISX0213: Fix slack-desc. 
> perl/perl-ExtUtils-Install: Fix slack-desc. 
> perl/perl-ExtUtils-ModuleMaker: Fix slack-desc. 
> perl/perl-ExtUtils-XSBuilder: Fix slack-desc. 
> perl/perl-FCGI: Fix slack-desc. 
> perl/perl-File-Finder: Fix slack-desc. 
> perl/perl-File-ReadBackwards: Fix slack-desc. 
> perl/perl-File-Save-Home: Fix slack-desc. 
> perl/perl-File-Tail: Fix slack-desc. 
> perl/perl-LWP-Protocol-https: Fix slack-desc. 
> perl/perl-Locale-Maketext-Lexicon: Fix slack-desc. 
> perl/perl-Mail-SPF-Query: Fix slack-desc. 
> perl/perl-MailTools: Fix slack-desc. 
> perl/perl-Math-Decimal64: Fix slack-desc. 
> perl/perl-Math-GMPf: Fix slack-desc. 
> perl/perl-Module-Build: Fix slack-desc. 
> perl/perl-Module-Install: Fix slack-desc. 
> perl/perl-Module-ScanDeps: Fix slack-desc. 
> perl/perl-Mozilla-CA: Fix slack-desc. 
> perl/perl-Net-DNS-Resolver-Programmable: Fix slack-desc. 
> perl/perl-Net-Daemon: Fix slack-desc. 
> perl/perl-Net-Libdnet: Fix slack-desc. 
> perl/perl-Net-Pcap: Fix slack-desc. 
> perl/perl-Net-Write: Fix slack-desc. 
> perl/perl-Number-Bites-Human: Fix slack-desc. 
> perl/perl-PAR-Dist: Fix slack-desc. 
> perl/perl-PAR: Fix slack-desc. 
> perl/perl-PHP-Serialization: Fix slack-desc. 
> perl/perl-Path-Class: Fix slack-desc. 
> perl/perl-Readonly: Fix slack-desc. 
> perl/perl-Sidef: Updated for version 2.33. 
> perl/perl-Slurp-Tiny: Fix slack-desc. 
> perl/perl-String-ShellQuote: Fix slack-desc. 
> perl/perl-Sub-Uplevel: Fix slack-desc. 
> perl/perl-Sys-Hostname-Long: Fix slack-desc. 
> perl/perl-Test-Exception: Fix slack-desc. 
> perl/perl-Test-SharedFork: Fix slack-desc. 
> perl/perl-Text-CharWidth: Fix slack-desc. 
> perl/perl-Text-Iconv: Fix slack-desc. 
> perl/perl-Text-WrapI18N: Fix slack-desc. 
> perl/perl-Time-Out: Fix slack-desc. 
> perl/perl-Tree-Simple: Fix slack-desc. 
> perl/perl-WWW-Curl: Fix slack-desc. 
> perl/perl-X11-Protocol-Other: Fix slack-desc. 
> perl/perl-XML-Filter-BufferText: Fix slack-desc. 
> perl/perl-YAML-Tiny: Fix slack-desc. 
> perl/perl-ZMQ-Constants: Fix slack-desc. 
> perl/perl-cairo: Fix slack-desc. 
> perl/perl-cgi-minimal: Fix slack-desc. 
> perl/perl-common-sense: Fix slack-desc. 
> perl/perl-config-general: Fix slack-desc. 
> perl/perl-data-page-pageset: Fix slack-desc. 
> perl/perl-extutils-depends: Fix slack-desc. 
> perl/perl-extutils-makemaker: Fix slack-desc. 
> perl/perl-extutils-pkgconfig: Fix slack-desc. 
> perl/perl-file-basedir: Fix slack-desc. 
> perl/perl-file-desktopentry: Fix slack-desc. 
> perl/perl-file-listing: Fix slack-desc. 
> perl/perl-file-mimeinfo: Fix slack-desc. 
> perl/perl-glib: Fix slack-desc. 
> perl/perl-gnome2-canvas: Fix slack-desc. 
> perl/perl-gnome2-gconf: Fix slack-desc. 
> perl/perl-gnome2-vfs: Fix slack-desc. 
> perl/perl-gnome2-wnck: Fix slack-desc. 
> perl/perl-gnome2: Fix slack-desc. 
> perl/perl-goo-canvas: Fix slack-desc. 
> perl/perl-gstreamer: Fix slack-desc. 
> perl/perl-gtk2-imageview: Fix slack-desc. 
> perl/perl-gtk2: Fix slack-desc. 
> perl/perl-html-form: Fix slack-desc. 
> perl/perl-http-cookies: Fix slack-desc. 
> perl/perl-http-daemon: Fix slack-desc. 
> perl/perl-http-message: Fix slack-desc. 
> perl/perl-http-negotiate: Fix slack-desc. 
> perl/perl-http-response-encoding: Fix slack-desc. 
> perl/perl-http-server-simple: Fix slack-desc. 
> perl/perl-linux-desktop-files: Fix slack-desc. 
> perl/perl-net-ip: Fix slack-desc. 
> perl/perl-pango: Fix slack-desc. 
> perl/perl-test-warn: Fix slack-desc. 
> perl/perl-tree-dagnode: Fix slack-desc. 
> perl/perl-www-mechanize: Fix slack-desc. 
> perl/perl-x11-protocol: Fix slack-desc. 
> python/Flask-Login: Fix slack-desc. 
> python/Logbook: Fix slack-desc. 
> python/Markdown: Fix slack-desc. 
> python/Paver: Fix slack-desc. 
> python/PyXB: Updated for version 1.2.5. 
> python/PythonQt: Fix slack-desc. 
> python/RBTools: Fix slack-desc. 
> python/affine: Fix slack-desc. 
> python/artifacts: Fix slack-desc. 
> python/babel: Fix slack-desc. 
> python/backports-abc: Fix slack-desc. 
> python/bencode: Fix slack-desc. 
> python/bitarray: Fix slack-desc. 
> python/cairocffi: Fix slack-desc. 
> python/click-plugins: Fix slack-desc. 
> python/construct: Fix slack-desc. 
> python/cssselect: Fix slack-desc. 
> python/distorm: Fix slack-desc. 
> python/fabric: Fix slack-desc. 
> python/fasteners: Fix slack-desc. 
> python/feedgenerator: Fix slack-desc. 
> python/flask-paginate: Fix slack-desc. 
> python/frosted: Fix slack-desc. 
> python/fudge: Fix slack-desc. 
> python/funcsigs: Fix slack-desc. 
> python/gnome-python: Fix slack-desc. 
> python/gunicorn: Fix slack-desc. 
> python/hachoir-core: Fix slack-desc. 
> python/hachoir-metadata: Fix slack-desc. 
> python/hachoir-parser: Fix slack-desc. 
> python/itsdangerous: Fix slack-desc. 
> python/jedi: Fix slack-desc. 
> python/minidb: Fix slack-desc. 
> python/monotonic: Fix slack-desc. 
> python/msgpack-python: Update README. 
> python/munch: Fix slack-desc. 
> python/ndg_httpsclient: Fix slack-desc. 
> python/p4python: Fix slack-desc. 
> python/pbr: Fix slack-desc. 
> python/pilkit: Fix slack-desc. 
> python/pillowfight: Fix slack-desc. 
> python/pipdeptree: Fix slack-desc. 
> python/pkginfo: Fix slack-desc. 
> python/pkginfo: Updated for version 1.4.1. 
> python/planes: Fix slack-desc. 
> python/poster: Fix slack-desc. 
> python/progressive: Fix slack-desc. 
> python/ptpython: Fix slack-desc. 
> python/py3cairo: Fix slack-desc. 
> python/py3sensors: Fix slack-desc. 
> python/py4j: Fix slack-desc. 
> python/pyasn1-modules: Fix slack-desc. 
> python/pychm: Fix slack-desc. 
> python/pydblite: Fix slack-desc. 
> python/pyglet: Fix slack-desc. 
> python/pygoocanvas: Fix slack-desc. 
> python/pyinotify: Fix slack-desc. 
> python/pylirc: Fix slack-desc. 
> python/pyorbit: Fix slack-desc. 
> python/pypy3: Fix slack-desc. 
> python/pypy: Fix slack-desc. 
> python/pyside: Fix slack-desc. 
> python/pysmssend: Fix slack-desc. 
> python/pysnmp: Fix slack-desc. 
> python/python-MonthDelta: Fix slack-desc. 
> python/python-authres: Fix slack-desc. 
> python/python-bigfloat: Fix slack-desc. 
> python/python-blake2: Fix slack-desc. 
> python/python-chardet: Fix slack-desc. 
> python/python-cheetah: Fix slack-desc. 
> python/python-demjson: Fix slack-desc. 
> python/python-distutils-extra: Fix slack-desc. 
> python/python-editor: Fix slack-desc. 
> python/python-elementtree: Fix slack-desc. 
> python/python-elib.intl: Fix slack-desc. 
> python/python-ldap: Fix slack-desc. 
> python/python-libsass: Fix slack-desc. 
> python/python-mccabe: Fix slack-desc. 
> python/python-morbid: Fix slack-desc. 
> python/python-mpd: Fix slack-desc. 
> python/python-musicbrainz2: Fix slack-desc. 
> python/python-netaddr: Fix slack-desc. 
> python/python-pmw: Fix slack-desc. 
> python/python-pydns: Fix slack-desc. 
> python/python-pypolicyd-spf: Fix slack-desc. 
> python/python-pyspf: Fix slack-desc. 
> python/python-requestbuilder: Fix slack-desc. 
> python/python-requests-kerberos: Fix slack-desc. 
> python/python-stomper: Fix slack-desc. 
> python/python-uuid: Fix slack-desc. 
> python/python-vatnumber: Fix slack-desc. 
> python/python-wordpress-xmlrpc: Fix slack-desc. 
> python/python-wrapt: Fix slack-desc. 
> python/python-yenc: Fix slack-desc. 
> python/python3-Cython: Fix slack-desc. 
> python/python3-pyparted: Fix slack-desc. 
> python/python3-sip: Fix slack-desc. 
> python/pyusb: Fix slack-desc. 
> python/pywebkitgtk: Fix slack-desc. 
> python/pyxdg: Fix slack-desc. 
> python/pyzmq: Fix slack-desc. 
> python/relatorio: Fix slack-desc. 
> python/requests-oauthlib: Fix slack-desc. 
> python/scikit-learn: Fix slack-desc. 
> python/setuptools-scm: Fix slack-desc. 
> python/snuggs: Fix slack-desc. 
> python/soundcloud: Fix slack-desc. 
> python/sqlalchemy-migrate: Fix slack-desc. 
> python/tagpy: Fix slack-desc. 
> python/tempita: Fix slack-desc. 
> python/termcolor: Fix slack-desc. 
> python/trollius: Fix slack-desc. 
> python/virtualenv: Fix slack-desc. 
> python/webassets: Fix slack-desc. 
> python/werkzeug: Fix slack-desc. 
> python/wsgiref: Fix slack-desc. 
> ruby/passenger: Fix slack-desc. 
> ruby/ruby-build: Fix slack-desc. 
> ruby/ruby-faraday: Updated for version 0.10.0. 
> ruby/ruby-sass: Fix slack-desc. 
> ruby/rubygem-coderay: Fix slack-desc. 
> ruby/rubygem-gosu: Fix slack-desc. 
> ruby/rubygem-sass: Fix slack-desc. 
> ruby/rubygem-slop3: Fix slack-desc. 
> ruby/sqlite3: Fix slack-desc. 
> system/Eterm: Fix slack-desc. 
> system/MySQL-Sandbox: Fix slack-desc. 
> system/TermRecord: Fix slack-desc. 
> system/USBdev: Fix slack-desc. 
> system/adobe-source-han-sans-fonts: Fix slack-desc. 
> system/adobe-source-sans-pro-font: Fix slack-desc. 
> system/advcopy: Fix slack-desc. 
> system/aha: Fix slack-desc. 
> system/ansible: Fix slack-desc. 
> system/apache-tomcat: Fix slack-desc. 
> system/apachetop: Fix slack-desc. 
> system/argyllcms: Fix slack-desc. 
> system/asbt: Fix slack-desc. 
> system/aterm: Fix slack-desc. 
> system/atop: Fix slack-desc. 
> system/augeas: Fix slack-desc. 
> system/bacula-client: Fix slack-desc. 
> system/bacula: Fix slack-desc. 
> system/bicon: Fix slack-desc. 
> system/biew: Fix slack-desc. 
> system/bootchart: Fix slack-desc. 
> system/brasero: Fix slack-desc. 
> system/byobu: Fix slack-desc. 
> system/cantarell-fonts: Fixed SlackBuild. 
> system/caprice32: Fix slack-desc. 
> system/cbmbasic: Fix slack-desc. 
> system/cdemu-daemon: Fix slack-desc. 
> system/cdrkit: Fix slack-desc. 
> system/cntlm: Fix slack-desc. 
> system/colord: Add auto detection for vala. 
> system/cpuinfo2cpuflags: Fix slack-desc. 
> system/cpulimit: Fix slack-desc. 
> system/crmsh: Fix slack-desc. 
> system/cronie: Fix slack-desc. 
> system/crunch: Fix slack-desc. 
> system/d-feet: Fix slack-desc. 
> system/daa2iso: Fix slack-desc. 
> system/dar: Fix slack-desc. 
> system/ddrescue-gui: Fix slack-desc. 
> system/detox: Fix slack-desc. 
> system/disk-manager: Fix slack-desc. 
> system/diskscan: Fix slack-desc. 
> system/docker: Fix slack-desc. 
> system/dosbox: Fix slack-desc. 
> system/driconf: Fix slack-desc. 
> system/dstat: Fix slack-desc. 
> system/dump: Fix slack-desc. 
> system/dvdisaster: Fix slack-desc. 
> system/dynamips: Fix slack-desc. 
> system/elasticsearch: Fix slack-desc. 
> system/eltclsh: Fix slack-desc. 
> system/emelfm2: Fix slack-desc. 
> system/eventlog: Fix slack-desc. 
> system/evilvte: Fix slack-desc. 
> system/extract-xiso: Fix slack-desc. 
> system/facter: Fix slack-desc. 
> system/fdupes: Fix slack-desc. 
> system/file-roller: Fix slack-desc. 
> system/findcmd: Fix slack-desc. 
> system/findpkg: Fix slack-desc. 
> system/fira-fonts: Fix slack-desc. 
> system/fpm2: Fix slack-desc. 
> system/freeswitch: Fix slack-desc. 
> system/fs-uae-arcade: Fix slack-desc. 
> system/fs-uae-launcher: Fix slack-desc. 
> system/fs-uae: Fix slack-desc. 
> system/fslint: Fix slack-desc. 
> system/fuseiso: Fix slack-desc. 
> system/gdmap: Fix slack-desc. 
> system/gencfs: Fix slack-desc. 
> system/gksu: Fix slack-desc. 
> system/glyptodon: Fix slack-desc. 
> system/gnome-commander: Fix slack-desc. 
> system/gnome-terminal: Fix slack-desc. 
> system/gnomint: Fix slack-desc. 
> system/gpart: Fix slack-desc. 
> system/gpsbabel: Fix slack-desc. 
> system/gradm: Fix slack-desc. 
> system/graveman: Fix slack-desc. 
> system/gsmartcontrol: Fix slack-desc. 
> system/gtk-vnc: Fix slack-desc. 
> system/guix: Fix slack-desc. 
> system/hal-flash: Fix slack-desc. 
> system/hercules: Fix slack-desc. 
> system/hime: Fix slack-desc. 
> system/hntool: Fix slack-desc. 
> system/ibam: Fix slack-desc. 
> system/idle3-tools: Fix slack-desc. 
> system/info2man: Fix slack-desc. 
> system/inxi: Updated for version 2.3.4. 
> system/ioping: Fix slack-desc. 
> system/ipmitool: Fix slack-desc. 
> system/irqbalance: Fix slack-desc. 
> system/isomaster: Fix slack-desc. 
> system/jdiskreport: Fix slack-desc. 
> system/jenkins: Fix slack-desc. 
> system/jmtpfs: Fix slack-desc. 
> system/john: Fix slack-desc. 
> system/jq: Fix slack-desc. 
> system/jsawk: Fix slack-desc. 
> system/kafka: Fix slack-desc. 
> system/keylaunch: Fix slack-desc. 
> system/lbrate: Fix slack-desc. 
> system/letsencrypt: Fix slack-desc. 
> system/linkchecker: Fix slack-desc. 
> system/lnav: Fix slack-desc. 
> system/lomoco: Fix slack-desc. 
> system/lxdm: Fix slack-desc. 
> system/lxsplit: Fix slack-desc. 
> system/macemu: Fix slack-desc. 
> system/makeself: Fix slack-desc. 
> system/md5deep: Fix slack-desc. 
> system/memtest86+: Fix slack-desc. 
> system/memtest86: Fix slack-desc. 
> system/memuse: Fix slack-desc. 
> system/microcode_ctl: Fix slack-desc. 
> system/microemulator: Fix slack-desc. 
> system/mongo-tools: Fix slack-desc. 
> system/monitorix: Fix slack-desc. 
> system/msitools: Fix slack-desc. 
> system/mucommander: Fix slack-desc. 
> system/multitail: Fix slack-desc. 
> system/munin-node: Fix slack-desc. 
> system/musl: Fix slack-desc. 
> system/nanum-coding-fonts-ttf: Fix slack-desc. 
> system/nanum-fonts-ttf: Fix slack-desc. 
> system/numlockx: Fix slack-desc. 
> system/nvidia-legacy340-driver: Fix slack-desc. 
> system/opam: Fix slack-desc. 
> system/openmpi: Fix slack-desc. 
> system/openrc: Updated for version 0.22.3. 
> system/opensc: Fix slack-desc. 
> system/oracle-instantclient-basic: Fix slack-desc. 
> system/oracle-instantclient-devel: Fix slack-desc. 
> system/oracle-xe: Fix slack-desc. 
> system/packagekit: Fix slack-desc. 
> system/packagekit: Updated for version 1.1.4. 
> system/parallel: Fix slack-desc. 
> system/partclone: Fix slack-desc. 
> system/passwdqc: Fix slack-desc. 
> system/password-store: Fix slack-desc. 
> system/passwordsafe: Fix slack-desc. 
> system/pbzip2: Fix slack-desc. 
> system/pdsh: Fix slack-desc. 
> system/pev: Fix slack-desc. 
> system/pgadmin3: Fix slack-desc. 
> system/pgsanity: Fix slack-desc. 
> system/plan9port: Fix slack-desc. 
> system/pmount: Fix slack-desc. 
> system/pommed-light: Fix slack-desc. 
> system/postgresql: Fix slack-desc. 
> system/procinfo-ng: Fix slack-desc. 
> system/pstate-frequency: Fix slack-desc. 
> system/pv: Fix slack-desc. 
> system/pwsafe: Fix slack-desc. 
> system/qdirstat: Fix slack-desc. 
> system/qstardict: Fix slack-desc. 
> system/qtgzmanager: Fix slack-desc. 
> system/quotatool: Fix slack-desc. 
> system/rabbitmq-server: Fix slack-desc. 
> system/ranger: Fix slack-desc. 
> system/recorder: Fix slack-desc. 
> system/redis: Fix slack-desc. 
> system/rename: Fix slack-desc. 
> system/rhash: Fix slack-desc. 
> system/rng-tools: Fix slack-desc. 
> system/roxterm: Fix slack-desc. 
> system/rsyslog: Fix slack-desc. 
> system/rxvt-unicode: Fix slack-desc. 
> system/samhain: Fix slack-desc. 
> system/samsung-mfp-drivers: Fix slack-desc. 
> system/samsung-mfp-drivers: Updated for version 1.00.36. 
> system/sbbdep: Fix slack-desc. 
> system/scanmem: Fix slack-desc. 
> system/schedtool: Fix slack-desc. 
> system/shake: Fix slack-desc. 
> system/simpleburn: Fix slack-desc. 
> system/slim: Fix slack-desc. 
> system/spl-solaris: Fix slack-desc. 
> system/splix: Fix slack-desc. 
> system/sqlite2: Fix slack-desc. 
> system/statifier: Fix slack-desc. 
> system/sudosh2: Fix slack-desc. 
> system/supervisor: Fix slack-desc. 
> system/tagainijisho: Fix slack-desc. 
> system/tamsyn-font: Fix slack-desc. 
> system/tc-play: Fix slack-desc. 
> system/testdisk: Fix slack-desc. 
> system/the_silver_searcher: Fix slack-desc. 
> system/thermal_daemon: Updated for version 1.5.4. 
> system/thinkfan: Fix slack-desc. 
> system/tiger: Fix slack-desc. 
> system/tinyterm: Fix slack-desc. 
> system/tinyvm: Fix slack-desc. 
> system/tokyocabinet: Fix slack-desc. 
> system/tokyotyrant: Fix slack-desc. 
> system/trachet: Fix slack-desc. 
> system/trash-cli: Fix slack-desc. 
> system/trrntzip: Fix slack-desc. 
> system/truecrypt: Fix slack-desc. 
> system/ttf-arphic-uming: Fix slack-desc. 
> system/ttf-open-sans: Fix slack-desc. 
> system/ttf-paratype-pt-fonts: Fix slack-desc. 
> system/ttf-zekton: Fix slack-desc. 
> system/tty2gif: Fix slack-desc. 
> system/twin: Fix slack-desc. 
> system/uif2iso: Fix slack-desc. 
> system/un-fonts-core: Fix slack-desc. 
> system/unetbootin: Fix slack-desc. 
> system/unhide: Fix slack-desc. 
> system/unison: Fix slack-desc. 
> system/untex: Fix slack-desc. 
> system/usbview: Fix slack-desc. 
> system/vagrant: Fix slack-desc. 
> system/veracrypt: Fix slack-desc. 
> system/vice: Fix slack-desc. 
> system/vifm: Fix slack-desc. 
> system/webcore-fonts: Fix slack-desc. 
> system/webcore-fonts: Updated for version 3.0. 
> system/whowatch: Fix slack-desc. 
> system/wiimms-iso-tools: Fix slack-desc. 
> system/wine: Fix slack-desc. 
> system/winetricks: Fix slack-desc. 
> system/winusb: Fix slack-desc. 
> system/wipe: Fix slack-desc. 
> system/wmfsm: Fix slack-desc. 
> system/worker: Fix slack-desc. 
> system/wterm: Fix slack-desc. 
> system/xarchiver: Fix slack-desc. 
> system/xbattmon: Fix slack-desc. 
> system/xbindkeys: Fix slack-desc. 
> system/xdiskusage: Fix slack-desc. 
> system/xfe: Fix slack-desc. 
> system/xfsudo: Fix slack-desc. 
> system/xrdp: Fix slack-desc. 
> system/xrestop: Fix slack-desc. 
> system/xwiimote: Fix slack-desc. 
> system/yelp-tools: Fix slack-desc. 
> system/z: Fix slack-desc. 
> system/zfs-on-linux: Fix slack-desc. 
> system/zookeeper: Fix slack-desc. 
> system/zopfli: Fix slack-desc. 
> system/zuluCrypt: Fix slack-desc. 
> +--------------------------+ 
>
> -- 
> Willy Sudiarto Raharjo 
>
> _______________________________________________ 
> SlackBuilds-users mailing list 
> SlackBuilds-users at slackbuilds.org 
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users 
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ 
> FAQ - https://slackbuilds.org/faq/ 
>

From willysr at slackbuilds.org  Mon Nov 14 12:55:56 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Mon, 14 Nov 2016 19:55:56 +0700
Subject: [Slackbuilds-users] Updates - 20161114.1
In-Reply-To: <20161114155253.qqSK6obD@smtp1o.mail.yandex.net>
References: <20161114155253.qqSK6obD@smtp1o.mail.yandex.net>
Message-ID: 

> Emm, but for what (why) do you do this?

There are a lot of problematic slack-descs (and READMEs) so B. Watson
did all the work to fix it. It's nothing major and it won't have any
effect at all to your package, except that it's now formatted perfectly,
lined correctly and according to the template that we have set in the
first place.


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From atelszewski at gmail.com  Mon Nov 14 21:49:37 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Mon, 14 Nov 2016 22:49:37 +0100
Subject: [Slackbuilds-users] ready queue PHP error
Message-ID: <4d216bb3-1b69-adad-f815-3c36d173ef6c@gmail.com>

From: https://slackbuilds.org/ready/

Notice: Undefined offset: 1 in /slackbuilds/.ready/index.php on line 17 
Notice: Undefined offset: 2 in /slackbuilds/.ready/index.php on line 20 
Notice: Undefined offset: 1 in /slackbuilds/.ready/index.php on line 17 
Notice: Undefined offset: 2 in /slackbuilds/.ready/index.php on line 20

From edps.mundognu at gmail.com  Mon Nov 14 23:03:20 2016
From: edps.mundognu at gmail.com (Edinaldo)
Date: Mon, 14 Nov 2016 21:03:20 -0200
Subject: [Slackbuilds-users] Updates - 20161114.1
Message-ID: 

Hi all,

about last update, inform that are two occurrences for the rubygem sass:

rubygem-sass
https://slackbuilds.org/cgit/slackbuilds/commit/?id=d3865e39938408872643968507420e8df4954f44

and

ruby-sass:
https://slackbuilds.org/cgit/slackbuilds/commit/?id=31ff0b4507d27ec8d0d30e920135d5c0b68d696e

The Slackbuild rubygem-sass is a bit older here, but the same version than  
my "ruby-sass"

So... i request the removal of "ruby-sass", and after that, please add the  
"rubygem-sass" as
a dependency of the SlackBuild "numix-gtk-theme".

Thanks!

Edinaldo.

From willysr at slackbuilds.org  Mon Nov 14 23:18:12 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 15 Nov 2016 06:18:12 +0700
Subject: [Slackbuilds-users] Updates - 20161114.1
In-Reply-To: 
References: 
Message-ID: <4a6f3d8f-01d1-35a6-aef7-536ce7765e74@slackbuilds.org>

> about last update, inform that are two occurrences for the rubygem sass:
> 
> rubygem-sass
> https://slackbuilds.org/cgit/slackbuilds/commit/?id=d3865e39938408872643968507420e8df4954f44
> 
> 
> and
> 
> ruby-sass:
> https://slackbuilds.org/cgit/slackbuilds/commit/?id=31ff0b4507d27ec8d0d30e920135d5c0b68d696e
> 
> 
> The Slackbuild rubygem-sass is a bit older here, but the same version
> than my "ruby-sass"
> 
> So... i request the removal of "ruby-sass", and after that, please add
> the "rubygem-sass" as
> a dependency of the SlackBuild "numix-gtk-theme".

Done


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From gerardo.zamudio at linux.com  Mon Nov 14 23:53:11 2016
From: gerardo.zamudio at linux.com (Gerardo Zamudio)
Date: Mon, 14 Nov 2016 17:53:11 -0600
Subject: [Slackbuilds-users] prosody
In-Reply-To: 
References: 
 
Message-ID: 

On 11/12/2016 07:34 AM, Willy Sudiarto Raharjo wrote:
>> the buildscript of prosody has some glitches and was not updated for
>> about 1 1/2 years, there were 2 security-related releases since version
>> 0.9.8.
>> I've mailed the current maintainer about that a few days ago,
>> but didn't get a reply yet.
>> So i'd like to take over maintenance of prosody, is this ok?
> 
> Gerardo Zamudio is still active based on git log
> 
> perhaps wait a little bit and if it doesn't get updated before next
> public update, ping us again on this list

Yes, I am still active and I received both your emails :)

I apologize being late on this. I was on vacation the last two weeks. I
have submitted an update already

Regards

-- 
Gerardo Zamudio

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: 

From willysr at slackbuilds.org  Tue Nov 15 15:01:39 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Tue, 15 Nov 2016 22:01:39 +0700
Subject: [Slackbuilds-users] Updates - 20161115.1
Message-ID: <666d5fd2-2516-9d30-fa12-133af14380e4@slackbuilds.org>

Here comes the second big fixes for READMEs done by B. Watson.
I also bumped vala to 0.34.2 as requested by Christoph Willing but added
a patch to support GTK+3-3.18.x used in Slackware 14.2. Let me know if
there's a side effect of this change.

After this, i should go back to my normal weekend update.

Tue Nov 15 14:43:15 UTC 2016
academic/Kst: Fix README.
academic/WordNet: Fix README.
academic/Xyce: Fix README.
academic/aline: Fix README.
academic/amplifx: Fix README.
academic/clustalo: Fix README.
academic/cutadapt: Fix README.
academic/genometools: Fix README.
academic/gnucap: Fix README.
academic/labplot2: Fix README.
academic/lalnview: Fix README.
academic/mafft: Fix README.
academic/mpmath: Fix README.
academic/suitesparse: Fix README.
accessibility/pastebinit: Fix README.
audio/aj-snapshot: Fix README.
audio/alsaequal: Fixed download.
audio/coverlovin: Fix README.
audio/deadbeef: Fix README.
audio/decibel-audio-player: Fix README.
audio/distrho-ports: Fix README.
audio/flacon: Fix README.
audio/herrie: Fix README.
audio/jack2: Fix README.
audio/mt-daapd: Fix README.
audio/ponymix: Fix README.
audio/sbagen: Fix README.
audio/spandsp: Fix README.
audio/ttaenc: Fix README.
audio/volume.app: Fix README.
audio/xmms-ctl: Fix README.
desktop/glabels: Fix README.
desktop/lumina: Fix README.
desktop/numix-gtk-theme: Change dep.
desktop/pidgin-window_merge: Fix slack-desc.
desktop/skippy-xd: Fix README.
desktop/spectrwm: Fix README.
desktop/tint2: Fix README.
desktop/xfce4-mailwatch-plugin: Fix README.
desktop/xmonad: Fix README.
development/GitEye: Fix README.
development/PythonToolkit: Fix README.
development/asm6809: Fix README.
development/bacon: Fix README.
development/brackets: Fix README.
development/codeblocks: Fix README.
development/edb-debugger: Fix README.
development/energia: Fix README.
development/enki: Fix README.
development/extra-cmake-modules: Fix README.
development/flow: Fix README.
development/fsharp: Fix README.
development/fuel: Fix README.
development/gnuradio: Fix README.
development/gradle: Fix README.
development/hhvm: Fix README.
development/julia: Fix README.
development/libbitcoin: Fix README.
development/lmdb: Fix README.
development/mcu8051ide: Fix README.
development/monkey-studio: Fix README.
development/mphidflash: Fix README.
development/netbeans: Fix README.
development/nexus: Fix README.
development/osmo-sdr: Fix README.
development/pycscope: Fix README.
development/qt-creator2: Fix README.
development/rust: Fix README.
development/smartgit: Fix README.
development/sonarqube: Fix README.
development/swfmill: Fix README.
development/tyrutils-ericw: Fix README.
development/vala: Updated for version 0.34.2.
development/vispatch: Fix README.
development/watchman: Fix README.
development/xdebug: Fix README.
development/zeal: Fix README.
development/zed: Fix README.
games/OpenXcom: Updated for version 20161023+a340c36 + new maint.
games/Pyfa: Fix README.
games/abe: Fix README.
games/bsnes-libretro: Fix README.
games/chocolate_duke3D: Fix README, update .info.
games/dgen: Fix README.
games/dhewm3: Fix README.
games/doomretro: Updated for version 2.3.5.
games/ecwolf: Fix README.
games/edgar: Fix README.
games/exult: Fix README.
games/ggmud: Fix README.
games/glxosd: Fix README.
games/gnonograms: Update DOWNLOAD url.
games/jackhammer: Fix README.
games/libretro-lutro: Fix README.
games/mupen64plus: Fix README.
games/nestopia: Fix README.
games/nuvie: Fix README.
games/openmw: Fix README.
games/pcsx-rearmed: Fix README.
games/pcsx2: Fix README.
games/ppsspp: Fix README.
games/qstat: Fix README.
games/quakeforge: Fix README.
games/qzdl: Fix README.
games/roccat-tools: Fix README.
games/scid: Fix README.
games/solarus: Fix README.
games/tanglet: Fix README.
games/ut2004: Fix README.
games/xcowsay: Fix README.
games/zsdx: Fix README.
gis/openorienteering-mapper: Added (Orienteering mapmaking program).
gis/pgrouting: Fix README.
gis/saga-gis: Fix MD5SUM.
graphics/entangle: Fix README.
graphics/opencollada: Fix README.
graphics/yesplz: Fix README.
ham/svxlink-sounds-en_US-heather-16k: Fix README.
libraries/DirectFB: Fix README.
libraries/cffi: Updated for version 1.9.1.
libraries/gevent: Fix README.
libraries/gflags: Fix README.
libraries/gtkhotkey: Fix README.
libraries/liboauth: Fix README.
libraries/libsigrok: Fix README.
libraries/libsigscan: Fix README.
libraries/libslack: Fix README.
libraries/libupnp: Fix README.
libraries/ptypes: Fix README.
libraries/pylast: Fix README.
libraries/toro: Fix README.
libraries/wjelement: Updated for version 1.2.
misc/abgx360: Fix README.
misc/boncuk: Fix README.
misc/drg2sbg: Fix README.
misc/esniper: Fix README.
misc/fcitx-mozc: Fix README.
misc/fcitx: Fix README.
misc/g15stats: Fix README.
misc/moedict-desktop.app: Fix README.
misc/opencc: Fix README.
misc/slop: Fix README.
misc/subsurface: Fix README.
multimedia/JSampler: Fix README.
multimedia/aces-dev: Fix README.
multimedia/gnash: Fix README.
network/aria2: Fix README.
network/bitlbee: Fix README.
network/ckermit: Fix README.
network/firehol: Fix README.
network/gns3: Fix README.
network/ipscan: Fix README.
network/lighttpd2: Fix README.
network/lighttpd: Fix README.
network/nagios: Fix README.
network/netsurf: Fix README.
network/ngrep: Fix README.
network/nsd: Fix README.
network/prosody: Updated for version 0.9.11.
network/radvd: Fix README.
network/skylable-sx: Fix README.
network/tnftp: Fix README.
network/vde2: Fix README.
network/wire: Fix README.
network/yadifa: Fix README.
network/znc: Fix README.
office/LibreOffice: Fix README.
office/ccal: Fix README.
office/gnokii: Fix README.
office/mined: Fix README.
office/pyspread: Fix README.
office/taskjuggler: Fix README.
python/Flask-Login: Fix README.
python/Logbook: Fix README.
python/funcsigs: Fix README.
python/pkginfo: Fix README.
python/pytest: Updated for version 3.0.4.
python/python-patch: Fix README.
python/python-scandir: Fix README.
python/python-scandir: Updated for version 1.4.
python/tqdm: Updated for version 4.10.0.
python/w3lib: Updated for version 1.16.0.
ruby/gem2tgz: Fix README.
ruby/heroku-client: Fix README.
ruby/ruby-sass: Removed (Duplicate).
system/adobe-source-han-sans-fonts: Fix README.
system/anything-sync-daemon: Fix README.
system/apache-activemq: Fix README.
system/bochs: Fix README.
system/bootchart: Fix README.
system/btrbk: Fix README.
system/courier-prime: Fix README.
system/cpulimit: Fix README.
system/cronie: Fix README.
system/docker: Fix README.
system/dump: Fix README.
system/dynamips: Fix README.
system/elasticsearch: Fix README.
system/extract-xiso: Fix README.
system/fira-fonts: Fix README.
system/guix: Fix README.
system/ioping: Fix README.
system/keylaunch: Fix README.
system/man-pages-ru: Fix README.
system/modules: Fix README.
system/mongo-tools: Fix README.
system/mongodb: Fix README.
system/munin-node: Fix README.
system/musl: Fix README.
system/nix: Fix README.
system/nvidia-driver: Fix README.
system/nvidia-legacy304-driver: Fix README.
system/nvidia-legacy340-driver: Fix README.
system/opam: Fix README.
system/pstate-frequency: Fix README.
system/pycp: Fix README.
system/qdirstat: Fix README.
system/qingy: Fix README.
system/quotatool: Fix README.
system/rabbitmq-server: Fix README.
system/recoverjpeg: Fix README.
system/rhash: Fix README.
system/run-one: Fix README.
system/slack-utils: Fix README.
system/supervisor: Fix README.
system/tiger: Fix README.
system/tpm: Fix README.
system/trashy: Fix README.
system/ttf-open-sans: Fix README.
system/ttf-zekton: Fix README.
system/uptimed: Fix README.
system/virtualbox-kernel-addons: Fix README.
system/virtualbox-kernel: Fix README.
system/vlock: Fix README.
system/webcore-fonts: Fix README.
system/webmin: Fix README.
system/wiimms-iso-tools: Fix README.
system/wine-staging: Fix README.
system/winusb: Fix README.
system/wipe: Fix README.
system/wmfsm: Fix README.
system/xnp2: Fix README.
system/xrdp: Fix README.
system/zookeeper: Fix README.
system/zuluCrypt: Fix README.
+--------------------------+


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From didier at slint.fr  Tue Nov 15 18:10:21 2016
From: didier at slint.fr (Didier Spaier)
Date: Tue, 15 Nov 2016 19:10:21 +0100
Subject: [Slackbuilds-users] Submission rejected.
Message-ID: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>

Got this as upload result:
---
didier~at~slint~dot~fr was rejected by slint.fr.
Go back and enter a valid E-Mail address.

If your mailserver uses Greylisting you may want to Whitelist slackbuilds-users at slackbuilds.org.

However, I own the domain slint.fr and just checked through the cpanel of my account that greylisting is disabled.
---
I got a similar answer with another email address (appartement~dot~cdm~at~free~dot~fr).

What should I do or check?

TIA,

Dider
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0x60C03EEA.asc
Type: application/pgp-keys
Size: 1718 bytes
Desc: not available
URL: 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: 

From didier at slint.fr  Tue Nov 15 18:43:49 2016
From: didier at slint.fr (Didier Spaier)
Date: Tue, 15 Nov 2016 19:43:49 +0100
Subject: [Slackbuilds-users] Submission rejected.
In-Reply-To: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>
References: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>
Message-ID: <9b6a515e-6b9d-b1e0-164b-270df5468f01@slint.fr>

Le 15/11/2016 ? 19:10, Didier Spaier a ?crit :
> Got this as upload result:
> ...

PS: in case someone wonder: of course no "~" in the submission form.

From joshuakwood at gmail.com  Tue Nov 15 20:27:39 2016
From: joshuakwood at gmail.com (JK Wood)
Date: Tue, 15 Nov 2016 14:27:39 -0600
Subject: [Slackbuilds-users] Submission rejected.
In-Reply-To: <9b6a515e-6b9d-b1e0-164b-270df5468f01@slint.fr>
References: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>
 <9b6a515e-6b9d-b1e0-164b-270df5468f01@slint.fr>
Message-ID: 

On Nov 15, 2016 12:45, "Didier Spaier"  wrote:
>
> Le 15/11/2016 ? 19:10, Didier Spaier a ?crit :
> > Got this as upload result:
> > ...
>
> PS: in case someone wonder: of course no "~" in the submission form.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

The email is used to send you a link that will allow you to withdraw the
upload in case you need to modify it for some reason. That's all they use
the address for - it doesn't go into a public list and they won't use it to
contact you.

Thanks,
JK
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From baildon.research at googlemail.com  Tue Nov 15 23:50:01 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Tue, 15 Nov 2016 23:50:01 +0000
Subject: [Slackbuilds-users] perl-template needs updating
In-Reply-To: 
References: 
 
 
 
 
Message-ID: 

On 30 August 2016 at 23:45, David Spencer
 wrote:
> Hey everybody,
>
> Here for your review is the draft revised perl template that we
> discussed last week.

So ... I finally did this :D

Obviously if there's any problem with it, please let us know.

Thanks
-D.

From slackbuilds at schoepfer.info  Wed Nov 16 08:25:57 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Wed, 16 Nov 2016 09:25:57 +0100
Subject: [Slackbuilds-users] prosody
In-Reply-To: 
References: 
 
 
Message-ID: <582C1815.6000308@schoepfer.info>

On 15.11.2016 00:53, Gerardo Zamudio wrote:
> On 11/12/2016 07:34 AM, Willy Sudiarto Raharjo wrote:
>>> the buildscript of prosody has some glitches and was not updated for
>>> about 1 1/2 years, there were 2 security-related releases since version
>>> 0.9.8.
>>> I've mailed the current maintainer about that a few days ago,
>>> but didn't get a reply yet.
>>> So i'd like to take over maintenance of prosody, is this ok?
>>
>> Gerardo Zamudio is still active based on git log
>>
>> perhaps wait a little bit and if it doesn't get updated before next
>> public update, ping us again on this list
>
> Yes, I am still active and I received both your emails :)
>
> I apologize being late on this. I was on vacation the last two weeks. I
> have submitted an update already

Thanks. I have some suggestions for the buildscript, i'll mail you 
off-list when i find some time.

Johannes

From slackbuilds at schoepfer.info  Wed Nov 16 08:44:13 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Wed, 16 Nov 2016 09:44:13 +0100
Subject: [Slackbuilds-users] Submission rejected.
In-Reply-To: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>
References: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>
Message-ID: <582C1C5D.4070405@schoepfer.info>

On 15.11.2016 19:10, Didier Spaier wrote:
> Got this as upload result:
> ---
> didier~at~slint~dot~fr was rejected by slint.fr.

The Exim mta at slint~dot~fr seems to delay incoming mail for over 
30seconds. This is no greylisting, but i assume SBo submission times out 
earlier.
Maybe a SBo-whitelist for trusted maintainers is an idea.

Johannes

From didier at slint.fr  Wed Nov 16 10:47:45 2016
From: didier at slint.fr (Didier Spaier)
Date: Wed, 16 Nov 2016 11:47:45 +0100
Subject: [Slackbuilds-users] Submission rejected.
In-Reply-To: <582C1C5D.4070405@schoepfer.info>
References: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>
 <582C1C5D.4070405@schoepfer.info>
Message-ID: <1203aae5-29f0-0bdb-2e1e-ce47838a3fee@slint.fr>

Le 16/11/2016 ? 09:44, Franzen a ?crit :
> On 15.11.2016 19:10, Didier Spaier wrote:
>> Got this as upload result:
>> ---
>> didier~at~slint~dot~fr was rejected by slint.fr.
> 
> The Exim mta at slint~dot~fr seems to delay incoming mail for over 30seconds. This is no greylisting, but i assume SBo submission times out earlier.
> Maybe a SBo-whitelist for trusted maintainers is an idea.

Thanks for taking the time to test, Johannes, much appreciated.

And yes, you are right about the submission time out, this has been confirmed by rob0 on IRC.

If I understand well, checking the email address found in the submission form is intended to make sure that the confirmation email will be received by the submitter.

Anyway, for now as a workaround I will use a tentative email address, maybe registered @ https://www.mailinator.com/ as suggested on IRC.

Have a good day,

Didier

From didier at slint.fr  Wed Nov 16 11:34:32 2016
From: didier at slint.fr (Didier Spaier)
Date: Wed, 16 Nov 2016 12:34:32 +0100
Subject: [Slackbuilds-users] Submission rejected.
In-Reply-To: <1203aae5-29f0-0bdb-2e1e-ce47838a3fee@slint.fr>
References: <32ef48d4-0d72-5a45-e9ec-7a19d5bd7f43@slint.fr>
 <582C1C5D.4070405@schoepfer.info>
 <1203aae5-29f0-0bdb-2e1e-ce47838a3fee@slint.fr>
Message-ID: <8ace4c55-ce5c-f66a-8b5b-8208bdb87039@slint.fr>



Le 16/11/2016 ? 11:47, Didier Spaier a ?crit :
> Le 16/11/2016 ? 09:44, Franzen a ?crit :
>> On 15.11.2016 19:10, Didier Spaier wrote:
>>> Got this as upload result:
>>> ---
>>> didier~at~slint~dot~fr was rejected by slint.fr.
>>
>> The Exim mta at slint~dot~fr seems to delay incoming mail for over 30seconds. This is no greylisting, but i assume SBo submission times out earlier.
>> Maybe a SBo-whitelist for trusted maintainers is an idea.
> 
> Thanks for taking the time to test, Johannes, much appreciated.
> 
> And yes, you are right about the submission time out, this has been confirmed by rob0 on IRC.
> 
> If I understand well, checking the email address found in the submission form is intended to make sure that the confirmation email will be received by the submitter.
> 
> Anyway, for now as a workaround I will use a tentative email address, maybe registered @ https://www.mailinator.com/ as suggested on IRC.

I confirm that using the email address YesIamDidierFromSlint at mailinator.com worked.

My submission is now is the pending queue.

And I could read the message from mailinator.com, just typing YesIamDidierFromSlint in the input field, then copy/paste in a file the confirmation message with the md5 hash and delete it.

Maybe this can help others in a similar situation.

idlemoor: thanks for the hint.

Didier

From atelszewski at gmail.com  Thu Nov 17 00:18:48 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 17 Nov 2016 01:18:48 +0100
Subject: [Slackbuilds-users] spice development release?
Message-ID: <262bdbed-1a44-2af6-ee01-5f4ddce87578@gmail.com>

Hi,

That's something I noticed by luck.
Per https://www.spice-space.org/download.html

- 0.12.8 is stable release
- 0.13.2 is development release

and we have 0.13.2 on SBo.

I don't know if there is much difference.

I have really irritating problem with virt-manager:
http://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/virt-manager-virtual-terminal-often-steals-focus-unless-minimized-4175587999/

and still looking for solution.

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Thu Nov 17 01:16:22 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 17 Nov 2016 02:16:22 +0100
Subject: [Slackbuilds-users] spice development release?
In-Reply-To: <262bdbed-1a44-2af6-ee01-5f4ddce87578@gmail.com>
References: <262bdbed-1a44-2af6-ee01-5f4ddce87578@gmail.com>
Message-ID: <31a14a91-ae54-0dee-6359-7f0bda89ff58@gmail.com>

On 17/11/16 01:18, Andrzej Telszewski wrote:
> Hi,
>
> That's something I noticed by luck.
> Per https://www.spice-space.org/download.html
>
> - 0.12.8 is stable release
> - 0.13.2 is development release
>
> and we have 0.13.2 on SBo.
>
> I don't know if there is much difference.
>
> I have really irritating problem with virt-manager:
> http://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/virt-manager-virtual-terminal-often-steals-focus-unless-minimized-4175587999/
>
>
> and still looking for solution.
>

It looks like bumping spice-gtk to version 0.33 solves the problem.
(I pinged Matteo about that).

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Thu Nov 17 06:13:43 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 17 Nov 2016 07:13:43 +0100
Subject: [Slackbuilds-users] spice development release?
In-Reply-To: <31a14a91-ae54-0dee-6359-7f0bda89ff58@gmail.com>
References: <262bdbed-1a44-2af6-ee01-5f4ddce87578@gmail.com>
 <31a14a91-ae54-0dee-6359-7f0bda89ff58@gmail.com>
Message-ID: 

2016-11-17 2:16 GMT+01:00 Andrzej Telszewski :
> On 17/11/16 01:18, Andrzej Telszewski wrote:
>>
>> Hi,
>>
>> That's something I noticed by luck.
>> Per https://www.spice-space.org/download.html
>>
>> - 0.12.8 is stable release
>> - 0.13.2 is development release
>>
>> and we have 0.13.2 on SBo.
>>
>> I don't know if there is much difference.
>>
>> I have really irritating problem with virt-manager:
>>
>> http://www.linuxquestions.org/questions/linux-virtualization-and-cloud-90/virt-manager-virtual-terminal-often-steals-focus-unless-minimized-4175587999/
>>
>>
>> and still looking for solution.
>>
>
> It looks like bumping spice-gtk to version 0.33 solves the problem.
> (I pinged Matteo about that).

I pushed the update in my branch, should go in the next update.

Matteo

From atelszewski at gmail.com  Thu Nov 17 08:57:49 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 17 Nov 2016 09:57:49 +0100
Subject: [Slackbuilds-users] spice development release?
In-Reply-To: 
References: <262bdbed-1a44-2af6-ee01-5f4ddce87578@gmail.com>
 <31a14a91-ae54-0dee-6359-7f0bda89ff58@gmail.com>
 
Message-ID: 

On 17/11/16 07:13, Matteo Bernardini wrote:
> 2016-11-17 2:16 GMT+01:00 Andrzej Telszewski :
>>
>> It looks like bumping spice-gtk to version 0.33 solves the problem.
>> (I pinged Matteo about that).
>
> I pushed the update in my branch, should go in the next update.
>
> Matteo

Thanks.

Anyways, I polluted the topic.
My real intent was to signal that we have development release of spice 
in repository, instead of the stable one.

I guess it slipped through, because of the versioning scheme and that 
they keep the tarballs in single directory. Development and stable 
tarballs are hard to distinguish unless you look at the website.

-- 
Best regards,
Andrzej Telszewski

From matteo.bernardini at gmail.com  Thu Nov 17 09:05:17 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Thu, 17 Nov 2016 10:05:17 +0100
Subject: [Slackbuilds-users] spice development release?
In-Reply-To: 
References: <262bdbed-1a44-2af6-ee01-5f4ddce87578@gmail.com>
 <31a14a91-ae54-0dee-6359-7f0bda89ff58@gmail.com>
 
 
Message-ID: 

2016-11-17 9:57 GMT+01:00 Andrzej Telszewski :
> My real intent was to signal that we have development release of spice in
> repository, instead of the stable one.
>
> I guess it slipped through, because of the versioning scheme and that they
> keep the tarballs in single directory. Development and stable tarballs are
> hard to distinguish unless you look at the website.

no, I upgraded to that on purpose as it should be supporting virgl

https://www.kraxel.org/blog/tag/virgl/
http://blog.wikichoon.com/2016/05/spice-openglvirgl-acceleration-on.html

Matteo

From atelszewski at gmail.com  Thu Nov 17 10:11:44 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 17 Nov 2016 11:11:44 +0100
Subject: [Slackbuilds-users] spice development release?
In-Reply-To: 
References: <262bdbed-1a44-2af6-ee01-5f4ddce87578@gmail.com>
 <31a14a91-ae54-0dee-6359-7f0bda89ff58@gmail.com>
 
 
 
Message-ID: 

On 17/11/16 10:05, Matteo Bernardini wrote:
> 2016-11-17 9:57 GMT+01:00 Andrzej Telszewski :
>> My real intent was to signal that we have development release of spice in
>> repository, instead of the stable one.
>>
>> I guess it slipped through, because of the versioning scheme and that they
>> keep the tarballs in single directory. Development and stable tarballs are
>> hard to distinguish unless you look at the website.
>
> no, I upgraded to that on purpose as it should be supporting virgl
>
> https://www.kraxel.org/blog/tag/virgl/
> http://blog.wikichoon.com/2016/05/spice-openglvirgl-acceleration-on.html
>
> Matteo

Thanks for clarification.

-- 
Best regards,
Andrzej Telszewski

From willysr at slackbuilds.org  Sat Nov 19 00:41:33 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 19 Nov 2016 07:41:33 +0700
Subject: [Slackbuilds-users] Updates - 20161119.1
Message-ID: <4314975b-0646-9c83-e1c0-cb11dcf3e4bc@slackbuilds.org>

Sat Nov 19 00:32:31 UTC 2016
academic/lpsolve: Updated for version 5.5.2.5.
academic/sundials: Updated for version 2.7.0.
audio/gnump3d: Update email.
audio/qjackctl: Updated for version 0.4.4.
desktop/insync-thunar: Updated for version 1.3.12.36116.
desktop/pekwm: Update DOWNLOAD.
development/SQLAlchemy: Updated for version 1.1.4.
development/atom: Updated for version 1.12.3.
games/cowsay: Restore slack-desc.
games/worldofgoo: Update email and download.
graphics/OpenCASCADE: Fixed for VTK-7.1.0.
graphics/paraview: Updated for version 5.2.0
libraries/VTK: Updated for version 7.1.0. New maintainer
libraries/libgaminggear: Updated for version 0.15.0.
libraries/libpseudo: Updated for version 1.2.0.
libraries/libvdpau-va-gl: Updated for version 0.4.2.
libraries/libviper: Updated for version 1.4.6.
libraries/live555: Updated for version 2016.11.17
libraries/rhino: Update DOWNLOAD url.
multimedia/lives: Updated for version 2.8.1.
multimedia/plexmediaserver: Updated for version 1.2.7.2987.
network/Electrum: Updated for version 2.7.12.
network/aria2: Updated for version 1.29.0.
network/deluge: Updated for version 1.3.13.
network/insync: Updated for version 1.3.12.36116.
network/nghttp2: Updated for version 1.16.1.
network/opera-developer: Updated for version 43.0.2412.0.
network/sftp-cloudfs: Updated for version 0.19.
network/sipp: Fix slack-desc.
network/spice-gtk: Updated for version 0.33.
network/tor-browser: Updated for version 6.0.6.
network/unbound: Updated for version 1.5.10.
network/wireshark: Updated for version 2.2.2.
office/org-mode: Update slack-desc.
perl/perl-DBD-SQLite: Updated for version 1.52.
python/flake8: Updated for version 3.2.0.
python/google-api-python-client: Updated for version 1.5.5.
python/pycodestyle: Updated for version 2.2.0.
python/pyresample: Updated for version 1.2.7.
python/python-oauth2client: Updated for version 4.0.0.
python/python-swiftclient: Updated for version 3.2.0.
ruby/ruby-build: Updated for version 20161115.
system/MySQL-Sandbox: Updated for version 3.2.03.
system/colord-gtk: Update SlackBuild for new options.
system/freedup: Update MAINTAINER, switch to i586.
system/fs-uae: Updated for version 2.8.1.
system/monitorix: Updated for version 3.9.0.
system/parallel: Updated for version 20161022.
system/qControlCenter: Added (Easy to customize Control Center).
system/recorder: Update email, homepage and download.
system/s3ql: Updated for version 2.21.
system/salt: Updated for version 2016.3.4.
system/trash-cli: Restore slack-desc.
+--------------------------+

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From lspencer31 at cfl.rr.com  Sat Nov 19 17:06:54 2016
From: lspencer31 at cfl.rr.com (Lenard Spencer)
Date: Sat, 19 Nov 2016 12:06:54 -0500
Subject: [Slackbuilds-users] Fix for games/pokerth
Message-ID: 

Since -current updated boost to 1.61, pokerth will no longer build as 
is.  After some searching, I found a patch to make it compile. Several 
weeks ago I sent an email of the .diff file to the maintainer in the 
.info file, but to date I have not received a response.

This patch is only needed for building with boost >=1.60, but as 14.2 
still uses boost 1.59, it is not necessary.

Since I don't know what else to do, here is the patch to run in the 
pokerth SBo folder.

----------------------------------- begin 
-------------------------------------------

diff -Naur pokerth/patch-README pokerth.new/patch-README
--- pokerth/patch-README    1969-12-31 19:00:00.000000000 -0500
+++ pokerth.new/patch-README    2016-10-29 17:23:34.000000000 -0400
@@ -0,0 +1,5 @@
+pokerth-1.1.1-fstream-ambiguity.patch
+
+Found at 
https://github.com/OpenMandrivaAssociation/pokerth/blob/master/pokerth-1.1.1-fstream-ambiguity.patch
+
+This patch fixes the build error when trying to build against boost 
1.60 and newer.
diff -Naur pokerth/pokerth-1.1.1-fstream-ambiguity.patch 
pokerth.new/pokerth-1.1.1-fstream-ambiguity.patch
--- pokerth/pokerth-1.1.1-fstream-ambiguity.patch    1969-12-31 
19:00:00.000000000 -0500
+++ pokerth.new/pokerth-1.1.1-fstream-ambiguity.patch    2016-10-29 
17:12:55.000000000 -0400
@@ -0,0 +1,150 @@
+From 69f820bb3d7c4dc8c838f115cb4c7ee5fd188721 Mon Sep 17 00:00:00 2001
+From: Jonathan Wakely 
+Date: Thu, 26 Nov 2015 16:27:52 +0000
+Subject: [PATCH] Qualify std::ifstream and std::ofstream
+
+Starting with Boost 1.60.0  includes
+, which declares ifstream and ofstream
+types that make the unqualified names ifstream and ofstream ambiguous.
+The names must be qualified to refer to the std versions.
+---
+ src/core/common/avatarmanager.cpp    | 4 ++--
+ src/core/common/loghelper_server.cpp | 6 +++---
+ src/net/common/clientstate.cpp       | 4 ++--
+ src/net/common/clientthread.cpp      | 4 ++--
+ src/net/common/downloaderthread.cpp  | 2 +-
+ src/pokerth_server.cpp               | 2 +-
+ src/zlib_compress.cpp                | 4 ++--
+ 7 files changed, 13 insertions(+), 13 deletions(-)
+
+diff --git a/src/core/common/avatarmanager.cpp 
b/src/core/common/avatarmanager.cpp
+index a8a52e4..0246b72 100644
+--- a/src/core/common/avatarmanager.cpp
++++ b/src/core/common/avatarmanager.cpp
+@@ -61,7 +61,7 @@ using namespace std;
+ using namespace boost::filesystem;
+
+ struct AvatarFileState {
+-    ifstream        inputStream;
++    std::ifstream        inputStream;
+ };
+
+ AvatarManager::AvatarManager(bool useExternalServer, const std::string 
&externalServerAddress,
+@@ -371,7 +371,7 @@ AvatarManager::StoreAvatarInCache(const MD5Buf 
&md5buf, AvatarFileType avatarFil
+                 path tmpPath(cacheDir);
+                 tmpPath /= (md5buf.ToString() + ext);
+                 string fileName(tmpPath.file_string());
+-                ofstream o(fileName.c_str(), ios_base::out | 
ios_base::binary | ios_base::trunc);
++                std::ofstream o(fileName.c_str(), ios_base::out | 
ios_base::binary | ios_base::trunc);
+                 if (!o.fail()) {
+                     o.write((const char *)data, size);
+                     o.close();
+diff --git a/src/core/common/loghelper_server.cpp 
b/src/core/common/loghelper_server.cpp
+index f79e4ca..a0d0350 100644
+--- a/src/core/common/loghelper_server.cpp
++++ b/src/core/common/loghelper_server.cpp
+@@ -67,7 +67,7 @@ void
+ internal_log_err(const string &msg)
+ {
+     if (!g_logFile.empty()) {
+-        ofstream o(g_logFile.c_str(), ios_base::out | ios_base::app);
++        std::ofstream o(g_logFile.c_str(), ios_base::out | ios_base::app);
+         if (!o.fail()) {
+             o << second_clock::local_time() << " ERR: " << msg;
+             o.flush();
+@@ -80,7 +80,7 @@ internal_log_msg(const std::string &msg)
+ {
+     if (g_logLevel) {
+         if (!g_logFile.empty()) {
+-            ofstream o(g_logFile.c_str(), ios_base::out | ios_base::app);
++            std::ofstream o(g_logFile.c_str(), ios_base::out | 
ios_base::app);
+             if (!o.fail())
+                 o << second_clock::local_time() << " MSG: " << msg;
+         }
+@@ -92,7 +92,7 @@ internal_log_level(const std::string &msg, int logLevel)
+ {
+     if (g_logLevel >= logLevel) {
+         if (!g_logFile.empty()) {
+-            ofstream o(g_logFile.c_str(), ios_base::out | ios_base::app);
++            std::ofstream o(g_logFile.c_str(), ios_base::out | 
ios_base::app);
+             if (!o.fail())
+                 o << second_clock::local_time() << " OUT: " << msg;
+         }
+diff --git a/src/net/common/clientstate.cpp 
b/src/net/common/clientstate.cpp
+index 143773b..080da2d 100644
+--- a/src/net/common/clientstate.cpp
++++ b/src/net/common/clientstate.cpp
+@@ -308,8 +308,8 @@ 
ClientStateReadingServerList::Enter(boost::shared_ptr client)
+
+         // Unzip the file using zlib.
+         try {
+-            ifstream 
inFile(zippedServerListPath.directory_string().c_str(), ios_base::in | 
ios_base::binary);
+-            ofstream 
outFile(xmlServerListPath.directory_string().c_str(), ios_base::out | 
ios_base::trunc);
++            std::ifstream 
inFile(zippedServerListPath.directory_string().c_str(), ios_base::in | 
ios_base::binary);
++            std::ofstream 
outFile(xmlServerListPath.directory_string().c_str(), ios_base::out | 
ios_base::trunc);
+ boost::iostreams::filtering_streambuf in;
+             in.push(boost::iostreams::zlib_decompressor());
+             in.push(inFile);
+diff --git a/src/net/common/clientthread.cpp 
b/src/net/common/clientthread.cpp
+index d60a535..1f3a619 100644
+--- a/src/net/common/clientthread.cpp
++++ b/src/net/common/clientthread.cpp
+@@ -1695,7 +1695,7 @@ void
+ ClientThread::ReadSessionGuidFromFile()
+ {
+     string guidFileName(GetContext().GetCacheDir() + TEMP_GUID_FILENAME);
+-    ifstream guidStream(guidFileName.c_str(), ios::in | ios::binary);
++    std::ifstream guidStream(guidFileName.c_str(), ios::in | ios::binary);
+     if (guidStream.good()) {
+         std::vector tmpGuid(CLIENT_GUID_SIZE);
+         guidStream.read(&tmpGuid[0], CLIENT_GUID_SIZE);
+@@ -1707,7 +1707,7 @@ void
+ ClientThread::WriteSessionGuidToFile() const
+ {
+     string guidFileName(GetContext().GetCacheDir() + TEMP_GUID_FILENAME);
+-    ofstream guidStream(guidFileName.c_str(), ios::out | ios::trunc | 
ios::binary);
++    std::ofstream guidStream(guidFileName.c_str(), ios::out | 
ios::trunc | ios::binary);
+     if (guidStream.good()) {
+         guidStream.write(GetContext().GetSessionGuid().c_str(), 
GetContext().GetSessionGuid().size());
+     }
+diff --git a/src/net/common/downloaderthread.cpp 
b/src/net/common/downloaderthread.cpp
+index e58e3f8..56a9526 100644
+--- a/src/net/common/downloaderthread.cpp
++++ b/src/net/common/downloaderthread.cpp
+@@ -96,7 +96,7 @@ DownloaderThread::Main()
+                 // Previous download was finished.
+                 if (m_curDownloadData) {
+                     path filepath(m_curDownloadData->filename);
+-                    ifstream instream(filepath.file_string().c_str(), 
ios_base::in | ios_base::binary);
++                    std::ifstream 
instream(filepath.file_string().c_str(), ios_base::in | ios_base::binary);
+                     // Find out file size.
+                     // Not fully portable, but works on win/linux/mac.
+                     instream.seekg(0, ios_base::beg);
+diff --git a/src/pokerth_server.cpp b/src/pokerth_server.cpp
+index 3b93d46..450a47e 100644
+--- a/src/pokerth_server.cpp
++++ b/src/pokerth_server.cpp
+@@ -161,7 +161,7 @@ main(int argc, char *argv[])
+         pidFile = tmpPidPath.directory_string();
+     }
+     {
+-        ofstream pidStream(pidFile.c_str(), ios_base::out | 
ios_base::trunc);
++        std::ofstream pidStream(pidFile.c_str(), ios_base::out | 
ios_base::trunc);
+         if (!pidStream.fail())
+             pidStream << getpid();
+         else
+diff --git a/src/zlib_compress.cpp b/src/zlib_compress.cpp
+index e3fd72d..4b04817 100644
+--- a/src/zlib_compress.cpp
++++ b/src/zlib_compress.cpp
+@@ -59,8 +59,8 @@ main(int argc, char *argv[])
+         return 2;
+     }
+     try {
+-        ifstream inFile(inputFilePath.directory_string().c_str(), 
ios_base::in);
+-        ofstream outFile(outputFilePath.directory_string().c_str(), 
ios_base::out | ios_base::binary);
++        std::ifstream inFile(inputFilePath.directory_string().c_str(), 
ios_base::in);
++        std::ofstream 
outFile(outputFilePath.directory_string().c_str(), ios_base::out | 
ios_base::binary);
+ boost::iostreams::filtering_streambuf out;
+         out.push(boost::iostreams::zlib_compressor());
+         out.push(outFile);
diff -Naur pokerth/pokerth.SlackBuild pokerth.new/pokerth.SlackBuild
--- pokerth/pokerth.SlackBuild    2016-05-25 20:29:40.000000000 -0400
+++ pokerth.new/pokerth.SlackBuild    2016-10-30 09:02:23.104096209 -0400
@@ -28,7 +28,7 @@
  PRGNAM=pokerth
  SRCNAM=PokerTH
  VERSION=${VERSION:-1.1.1}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
  TAG=${TAG:-_SBo}

  if [ -z "$ARCH" ]; then
@@ -73,6 +73,9 @@
   \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
    -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

+# patch to build against boost 1.60 and newer:
+patch -p1 < $CWD/pokerth-1.1.1-fstream-ambiguity.patch
+
  # The headers to which this file points have moved in the newer 
libircclient...
  # Thanks ponce.
  sed -i "s|libircclient/||" src/net/common/ircthread.cpp

------------------------------------ end 
--------------------------------------------


From matteo.bernardini at gmail.com  Sat Nov 19 17:15:29 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Sat, 19 Nov 2016 18:15:29 +0100
Subject: [Slackbuilds-users] Fix for games/pokerth
In-Reply-To: 
References: 
Message-ID: 

2016-11-19 18:06 GMT+01:00 Lenard Spencer :
> Since -current updated boost to 1.61, pokerth will no longer build as is.
> After some searching, I found a patch to make it compile. Several weeks ago
> I sent an email of the .diff file to the maintainer in the .info file, but
> to date I have not received a response.
>
> This patch is only needed for building with boost >=1.60, but as 14.2 still
> uses boost 1.59, it is not necessary.
>
> Since I don't know what else to do, here is the patch to run in the pokerth
> SBo folder.
>
> ----------------------------------- begin
> -------------------------------------------
> [...]
> ------------------------------------ end
> --------------------------------------------

hi Lenard,

I already applied that patch a while ago in the unofficial fork for current...

http://cgit.ponce.cc/slackbuilds/commit/?h=pokerth

Matteo

P.S. if you find other patches for current not already there, feel
free to post on the dedicated thread on LQ (
https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/
) as current is not officially supported.

From lspencer31 at cfl.rr.com  Sat Nov 19 17:18:01 2016
From: lspencer31 at cfl.rr.com (Lenard Spencer)
Date: Sat, 19 Nov 2016 12:18:01 -0500
Subject: [Slackbuilds-users] /misc/gourmet SBo fix
Message-ID: <5a1710dd-b27c-7c99-d3eb-f680370638e3@cfl.rr.com>

Here is a fix I found for Gourmet.  Because of changes to Python since 
Slack 14.1, the ability to enter and edit recipes was broken. Like with 
pokerth, I tried to email the maintainer in the .info file, but have 
never received a response.  So I am posting the diff here in the hope 
you can use it.  This is only needed with 14.2 and later.

----------------------------------- begin 
-------------------------------------------

diff -Naur gourmet/gourmet.SlackBuild gourmet-patched/gourmet.SlackBuild
--- gourmet/gourmet.SlackBuild    2016-05-25 20:29:41.000000000 -0400
+++ gourmet-patched/gourmet.SlackBuild    2016-11-13 10:19:16.595150351 
-0500
@@ -24,7 +24,7 @@

  PRGNAM=gourmet
  VERSION=${VERSION:-0.17.4}
-BUILD=${BUILD:-1}
+BUILD=${BUILD:-2}
  TAG=${TAG:-_SBo}

  if [ -z "$ARCH" ]; then
@@ -69,6 +69,9 @@
   \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \
   -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \;

+# Patch to replace removed tostring() with tobytes()
+patch -p1 < $CWD/tostring-to-tobytes.patch
+
  python setup.py install --root=$PKG

  find $PKG -print0 | xargs -0 file | grep -e "executable" -e "shared 
object" | grep ELF \
diff -Naur gourmet/gourmet.info gourmet-patched/gourmet.info
--- gourmet/gourmet.info    2016-05-25 20:29:41.000000000 -0400
+++ gourmet-patched/gourmet.info    2016-11-13 10:56:56.131303754 -0500
@@ -5,6 +5,6 @@
  MD5SUM="937334364abc3093709a604c1d473e9f"
  DOWNLOAD_x86_64=""
  MD5SUM_x86_64=""
-REQUIRES="SQLAlchemy python-distutils-extra reportlab pygtkspell 
gst0-python python-elib.intl"
+REQUIRES="SQLAlchemy lxml python-distutils-extra reportlab pygtkspell 
gst0-python python-elib.intl"
  MAINTAINER="Erwin van Zanten"
  EMAIL="e.van.zanten.evz at gmail.com"
diff -Naur gourmet/tostring-to-tobytes.patch 
gourmet-patched/tostring-to-tobytes.patch
--- gourmet/tostring-to-tobytes.patch    1969-12-31 19:00:00.000000000 -0500
+++ gourmet-patched/tostring-to-tobytes.patch    2016-11-13 
10:09:20.452109878 -0500
@@ -0,0 +1,26 @@
+diff --git a/gourmet/gtk_extras/ratingWidget.py 
b/gourmet/gtk_extras/ratingWidget.py
+index 0e01735..efa6463 100644
+--- a/gourmet/gtk_extras/ratingWidget.py
++++ b/gourmet/gtk_extras/ratingWidget.py
+@@ -135,7 +135,7 @@ class StarGenerator:
+         if is_rgba: rowstride = 4
+         else: rowstride = 3
+         pb=gtk.gdk.pixbuf_new_from_data(
+-            image.tostring(),
++            image.tobytes(),
+             gtk.gdk.COLORSPACE_RGB,
+             is_rgba,
+             8,
+diff --git a/gourmet/plugins/browse_recipes/icon_helpers.py 
b/gourmet/plugins/browse_recipes/icon_helpers.py
+index 61c772c..2e7b08b 100644
+--- a/gourmet/plugins/browse_recipes/icon_helpers.py
++++ b/gourmet/plugins/browse_recipes/icon_helpers.py
+@@ -38,7 +38,7 @@ def get_pixbuf_from_image (image):
+     if is_rgba: rowstride = 4
+     else: rowstride = 3
+     pb=gtk.gdk.pixbuf_new_from_data(
+-        image.tostring(),
++        image.tobytes(),
+         gtk.gdk.COLORSPACE_RGB,
+         is_rgba,
+         8,

------------------------------------ end 
--------------------------------------------


From marc at mos6581.de  Sat Nov 19 17:19:29 2016
From: marc at mos6581.de (Marcel Saegebarth)
Date: Sat, 19 Nov 2016 18:19:29 +0100
Subject: [Slackbuilds-users] Fix for games/pokerth
In-Reply-To: 
References: 
Message-ID: 

On 11/19/2016 06:06 PM, Lenard Spencer wrote:
> Several
> weeks ago I sent an email of the .diff file to the maintainer in the
> .info file, but to date I have not received a response.

Sorry, but I did not received an eMail from you.

-marc

From didier at slint.fr  Sat Nov 19 23:23:23 2016
From: didier at slint.fr (Didier Spaier)
Date: Sun, 20 Nov 2016 00:23:23 +0100
Subject: [Slackbuilds-users] Dependency omitted in qControlCenter submission
Message-ID: <431813f4-9647-473c-2599-86168716209b@slint.fr>

In the submission of qControlCenter I forgot to mention that it requires
pyxdg, sorry about that.

Should I make a new submission?

Didier

From willysr at slackbuilds.org  Sat Nov 19 23:34:24 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sun, 20 Nov 2016 06:34:24 +0700
Subject: [Slackbuilds-users] Dependency omitted in qControlCenter
 submission
In-Reply-To: <431813f4-9647-473c-2599-86168716209b@slint.fr>
References: <431813f4-9647-473c-2599-86168716209b@slint.fr>
Message-ID: 

> In the submission of qControlCenter I forgot to mention that it requires
> pyxdg, sorry about that.
> 
> Should I make a new submission?

Updated in my branch

Thanks


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From edps.mundognu at gmail.com  Sun Nov 20 19:39:04 2016
From: edps.mundognu at gmail.com (Edinaldo)
Date: Sun, 20 Nov 2016 17:39:04 -0200
Subject: [Slackbuilds-users] coverloving - removal request
Message-ID: 


Hello everyone,

apparently the SlackBuild coverloving no longer works, so i request your  
removal.

searching it seems that the unavailability of the Google Image Search API  
service
broke this package:

https://www.mail-archive.com/aur-requests at archlinux.org/msg12479.html
https://www.mail-archive.com/aur-requests at archlinux.org/msg12641.html

Thank's in advance,

Edinaldo.

From baildon.research at googlemail.com  Sun Nov 20 21:26:11 2016
From: baildon.research at googlemail.com (David Spencer)
Date: Sun, 20 Nov 2016 21:26:11 +0000
Subject: [Slackbuilds-users] coverloving - removal request
In-Reply-To: 
References: 
Message-ID: 

> apparently the SlackBuild coverloving no longer works, so i request your
> removal.
>
> searching it seems that the unavailability of the Google Image Search API
> service
> broke this package:

Removed in my branch
;-(

Thanks for your other updates today :)
-D.

From aclemons at runbox.no  Mon Nov 21 07:33:24 2016
From: aclemons at runbox.no (Andrew Clemons)
Date: Mon, 21 Nov 2016 20:33:24 +1300
Subject: [Slackbuilds-users] imapfilter maintainer
Message-ID: <20161121073323.GA13036@runbox.no>

I sent a message to the imapfilter maintainer, ?ime Ramov, about an
update and he responded that he is no longer maintaining any of his
slackbuilds. If no one else is keen, I can take of this one.

Looks like he is also the maintainer of these:
./audio/musepack-tools
./graphics/viewnior
./libraries/html5lib
./libraries/libcuefile
./libraries/libev
./libraries/libreplaygain
./network/maildrop
./perl/perl-Text-Autoformat
./perl/perl-Text-Reform
./python/pyquery

----- Forwarded message from Sime Ramov  -----

Date: Fri, 18 Nov 2016 12:39:23 +0100
From: Sime Ramov 
To: Andrew Clemons 
Subject: Re: imapfilter on slackbuilds.org
X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-unknown-linux-gnu)

Hi,

> Are you still maintaining imapfilter on slackbuilds.org?

I'm sorry, unfortunately no (along with any other SlackBuilds). Feel
free to take it over.


----- End forwarded message -----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: 

From matteo.bernardini at gmail.com  Mon Nov 21 07:47:39 2016
From: matteo.bernardini at gmail.com (Matteo Bernardini)
Date: Mon, 21 Nov 2016 08:47:39 +0100
Subject: [Slackbuilds-users] imapfilter maintainer
In-Reply-To: <20161121073323.GA13036@runbox.no>
References: <20161121073323.GA13036@runbox.no>
Message-ID: 

2016-11-21 8:33 GMT+01:00 Andrew Clemons :
> ./libraries/libev

I'll get this, as it's a dependency of some things I use.

Matteo

From larryhaja at gmail.com  Mon Nov 21 16:02:01 2016
From: larryhaja at gmail.com (Larry Hajali)
Date: Mon, 21 Nov 2016 08:02:01 -0800
Subject: [Slackbuilds-users] imapfilter maintainer
In-Reply-To: <20161121073323.GA13036@runbox.no>
References: <20161121073323.GA13036@runbox.no>
Message-ID: 

>
> ./libraries/html5lib
>
I can take this one.

--Larry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From andreas.guldstrand at gmail.com  Mon Nov 21 20:19:58 2016
From: andreas.guldstrand at gmail.com (Andreas Guldstrand)
Date: Mon, 21 Nov 2016 21:19:58 +0100
Subject: [Slackbuilds-users] imapfilter maintainer
In-Reply-To: 
References: <20161121073323.GA13036@runbox.no>
 
Message-ID: 

I'll happily take the perl ones:
> ./perl/perl-Text-Autoformat
> ./perl/perl-Text-Reform

/ Andreas

From edps.mundognu at gmail.com  Tue Nov 22 22:46:02 2016
From: edps.mundognu at gmail.com (Edinaldo)
Date: Tue, 22 Nov 2016 20:46:02 -0200
Subject: [Slackbuilds-users] imapfilter maintainer
Message-ID: 

I can take this:

./graphics/viewnior

Edinaldo.

From lspencer31 at cfl.rr.com  Thu Nov 24 00:03:46 2016
From: lspencer31 at cfl.rr.com (Lenard Spencer)
Date: Wed, 23 Nov 2016 19:03:46 -0500
Subject: [Slackbuilds-users] Fix for games/pokerth
Message-ID: <25a2891d-b340-b149-37ee-bd092c3bce1e@cfl.rr.com>

>hi Lenard,
>
>I already applied that patch a while ago in the unofficial fork for current...


Strange, it doesn't show up in the slackbuilds git master repo, which is what I am working from.

And next time I'll remember to use the LQ thread if I find anything else.  Thanks for the tip.

Lenard


From willysr at slackbuilds.org  Thu Nov 24 00:13:01 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 24 Nov 2016 07:13:01 +0700
Subject: [Slackbuilds-users] Fix for games/pokerth
In-Reply-To: <25a2891d-b340-b149-37ee-bd092c3bce1e@cfl.rr.com>
References: <25a2891d-b340-b149-37ee-bd092c3bce1e@cfl.rr.com>
Message-ID: <64e3bbe5-d150-6f78-3ec4-92a20ac92136@slackbuilds.org>

>> I already applied that patch a while ago in the unofficial fork for
>> current...
> 
> 
> Strange, it doesn't show up in the slackbuilds git master repo, which is
> what I am working from.

It's ponce's repository, not SBo's git repository since SBo track stable
instead of current tree
http://cgit.ponce.cc/slackbuilds/

There's a branch for that
http://cgit.ponce.cc/slackbuilds/log/?h=pokerth


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From lspencer31 at cfl.rr.com  Thu Nov 24 12:45:31 2016
From: lspencer31 at cfl.rr.com (lspencer31 at cfl.rr.com)
Date: Thu, 24 Nov 2016 7:45:31 -0500
Subject: [Slackbuilds-users] Fix for games/pokerth
In-Reply-To: <64e3bbe5-d150-6f78-3ec4-92a20ac92136@slackbuilds.org>
Message-ID: <20161124124531.HAHCH.25963.root@cdptpa-web19>

Thanks for the info.  I'll switch my rsync over to his repo.

---- Willy Sudiarto Raharjo  wrote: 
> >> I already applied that patch a while ago in the unofficial fork for
> >> current...
> > 
> > 
> > Strange, it doesn't show up in the slackbuilds git master repo, which is
> > what I am working from.
> 
> It's ponce's repository, not SBo's git repository since SBo track stable
> instead of current tree
> http://cgit.ponce.cc/slackbuilds/
> 
> There's a branch for that
> http://cgit.ponce.cc/slackbuilds/log/?h=pokerth
> 
> 
> -- 
> Willy Sudiarto Raharjo
> 


From atelszewski at gmail.com  Thu Nov 24 14:45:08 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 24 Nov 2016 15:45:08 +0100
Subject: [Slackbuilds-users] LibreOffice, LOLANGS and dictionaries
In-Reply-To: <448539ea-fb61-c20c-992d-fdc816f4d6ef@slackbuilds.org>
References: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>
 <448539ea-fb61-c20c-992d-fdc816f4d6ef@slackbuilds.org>
Message-ID: 

On 08/11/16 03:52, Willy Sudiarto Raharjo wrote:
>> I would like to ask what LOLANGS is about in LibreOffice.SlackBuild?
>> Is it only about user interface language?
>> Or does it influence for example date/time format, currency, etc?
>
> I think it's already mentioned on the README
>
> support additional languages by overriding the LOLANGS variable, whose
> default setting is LOLANGS="de es fr id it ja nl vi zh-CN". Note that
> en-US is always added to whatever LOLANGS is set. Thus building with,
> for example,
> LOLOANGS="de" sh LibreOffice
>
> would build LibreOffice with support for german and US english languages.
>

Yep, but it wasn't clear to me ;-)

Now I know that it is about user interface only.
I actually built with en-US and all the currency/etc. stuff works as 
expected with other languages, so that's what I wanted.

>> SlackBuild correction:
>> Not having pl in LOLANGS="de es fr id it ja nl vi zh-CN"
>> is programming error :-^
>
> I believe that's one good thing about open source. It evolves from time
> to time and adding more languages is one of them. However, maintainers
> may not notice every possible development done by upstream. That's why
> we love it when people report and make things better :)
>

That was meant to be a joke, me being pl native speaker ;-)
I phrased it "programming error" for the purpose of play ;-)

Thanks for clarification.

-- 
Best regards,
Andrzej Telszewski

From atelszewski at gmail.com  Thu Nov 24 14:52:01 2016
From: atelszewski at gmail.com (Andrzej Telszewski)
Date: Thu, 24 Nov 2016 15:52:01 +0100
Subject: [Slackbuilds-users] LibreOffice, LOLANGS and dictionaries
In-Reply-To: <0e64471f-486e-aa3d-7e17-655d83ec49de@iinet.net.au>
References: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>
 <0e64471f-486e-aa3d-7e17-655d83ec49de@iinet.net.au>
Message-ID: <2721cdcc-5217-04a1-d835-2675e26e98e3@gmail.com>

On 08/11/16 03:56, Christoph Willing wrote:
> On 08/11/16 11:35, Andrzej Telszewski wrote:
>> Hi,
>>
>> I would like to ask what LOLANGS is about in LibreOffice.SlackBuild?
>> Is it only about user interface language?
>> Or does it influence for example date/time format, currency, etc?
>>
>> Per
>> https://wiki.documentfoundation.org/Development/How_to_build/localized
>> it's not clear to me what localized means.
>>
> If you were to run LibreOffice itself, you would find (in
> Options->Language Settings) that you are able to independently set these
> items. The language settings available are, as you might expect, those
> specified in the LOLANGS variable at build time. Other settings in the
> same widget such as Locale, currency have a far greater range of options
> from which to choose. I assume that greater range derives from whatever
> is available on your system.
>

That is clear now, as I wrote in reply to Willy.
Thanks.

>> Also, LibreOffice README says that I can use hunspell dictionaries.
>> Do you have any experience with that?
>> Are they better in any way?
> Better than what?
>

You mention in README that I can download OXT or use hunspell-*.
Is there any preference to use one or the other?

I have installed hunspell and it seems to be just fine.
Why I would vote hunspell over OXT, is that, at least in the case of PL 
language, the dictionary comes from the national language authority.
But I don't know how actually OXT version is produced.

>> SlackBuild correction:
>> Not having pl in LOLANGS="de es fr id it ja nl vi zh-CN"
>> is programming error :-^
>>
> Well, the SackBuild actually says:
>     LOLANGS=${LOLANGS:-"de es fr id it ja nl vi zh-CN"}
> precisely so that a builder can trivially include whatever language(s)
> they want.
>

Meant to be joke, didn't work ;-)

Thanks!

-- 
Best regards,
Andrzej Telszewski

From chris.willing at iinet.net.au  Thu Nov 24 21:30:44 2016
From: chris.willing at iinet.net.au (Christoph Willing)
Date: Fri, 25 Nov 2016 07:30:44 +1000
Subject: [Slackbuilds-users] LibreOffice, LOLANGS and dictionaries
In-Reply-To: <2721cdcc-5217-04a1-d835-2675e26e98e3@gmail.com>
References: <2c533277-4057-0f95-60c3-b4ae20ee0429@gmail.com>
 <0e64471f-486e-aa3d-7e17-655d83ec49de@iinet.net.au>
 <2721cdcc-5217-04a1-d835-2675e26e98e3@gmail.com>
Message-ID: <678b01c4-a9e9-7f60-fa9b-cbfd5265853c@iinet.net.au>

On 25/11/16 00:52, Andrzej Telszewski wrote:
...
>>> Also, LibreOffice README says that I can use hunspell dictionaries.
>>> Do you have any experience with that?
>>> Are they better in any way?
>> Better than what?
>>
>
> You mention in README that I can download OXT or use hunspell-*.
> Is there any preference to use one or the other?
>
> I have installed hunspell and it seems to be just fine.
> Why I would vote hunspell over OXT, is that, at least in the case of PL
> language, the dictionary comes from the national language authority.
> But I don't know how actually OXT version is produced.
>
The main advantage of the .oxt's is the range which is available. SBo 
has hunspell language packages for only german, english, polish & spanish.

chris


From akio at akionux.net  Fri Nov 25 16:06:50 2016
From: akio at akionux.net (Akio Nishimura)
Date: Sat, 26 Nov 2016 01:06:50 +0900
Subject: [Slackbuilds-users] Fix for academic/ghemical
Message-ID: <44cab488-5958-e490-52c6-c4b740f81333@akionux.net>

Hi,

Here is a fix for academic/ghemical. For multilib environment, LDFLAGS
need to be set. --libdir option seems not working.

diff --git a/academic/ghemical/ghemical.SlackBuild
b/academic/ghemical/ghemical.SlackBuild
index b1ae6c5..6b4062b 100644
--- a/academic/ghemical/ghemical.SlackBuild
+++ b/academic/ghemical/ghemical.SlackBuild
@@ -53,6 +53,7 @@ find -L . \
 
 CFLAGS="$SLKCFLAGS" \
 CXXFLAGS="$SLKCFLAGS" \
+LDFLAGS="-L/usr/lib${LIBDIRSUFFIX}" \
 ./configure \
   --prefix=/usr \
   --libdir=/usr/lib${LIBDIRSUFFIX} \

-- 
Best regards,
Akio


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 213 bytes
Desc: OpenPGP digital signature
URL: 

From duncan_roe at acslink.net.au  Fri Nov 25 23:17:59 2016
From: duncan_roe at acslink.net.au (Duncan Roe)
Date: Sat, 26 Nov 2016 10:17:59 +1100
Subject: [Slackbuilds-users] Please help with failing upload
Message-ID: <20161125231759.GA24772@dimstar.local.net>

Hi,

When I try to upload a new version of pstack-expect-gdb, the response comes back
"File exists; a submission by the name 'pstack-expect-gdb' is already pending
approval".

But I can't see pstack-expect-gdb in the pending queue and I can't remove it
either.

Could someone whithdraw it for me please?

Cheers ... Duncan.

--
 Please avoid sending me Word or PowerPoint attachments.
 See http://www.gnu.org/philosophy/no-word-attachments.html

From willysr at slackbuilds.org  Fri Nov 25 23:46:06 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 26 Nov 2016 06:46:06 +0700
Subject: [Slackbuilds-users] Please help with failing upload
In-Reply-To: <20161125231759.GA24772@dimstar.local.net>
References: <20161125231759.GA24772@dimstar.local.net>
Message-ID: 

> When I try to upload a new version of pstack-expect-gdb, the response comes back
> "File exists; a submission by the name 'pstack-expect-gdb' is already pending
> approval".
> 
> But I can't see pstack-expect-gdb in the pending queue and I can't remove it
> either.
> 
> Could someone whithdraw it for me please?

It's already approved and waiting for next public update
https://slackbuilds.org/cgit/slackbuilds/commit/?id=12c7f0e69


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From willysr at slackbuilds.org  Sat Nov 26 04:58:57 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Sat, 26 Nov 2016 11:58:57 +0700
Subject: [Slackbuilds-users] Updates - 20161126.1
Message-ID: 

Sat Nov 26 04:48:25 UTC 2016
academic/copasi: Updated for version 4.17.135.
academic/gwyddion: Updated for version 2.47.
academic/perlprimer: Updated for version 1.1.21.
audio/coverlovin: Removed (no longer works).
desktop/Xfce-Theme-Manager: Update DOWNLOAD url.
desktop/gtk-theme-Greybird: Updated for version 3.22.0.
desktop/neofetch: Updated for version 1.9.1.
desktop/numix-gtk-theme: Updated for version 2.6.6.626.201611150117.
desktop/numix-icon-theme-circle: Updated for v2.0.3.12.201611180232.
desktop/numix-icon-theme-square: Added (Numix Square icon theme).
desktop/numix-icon-theme: Updated for version 0.3.872.201611140017.
desktop/oranchelo-icon-theme: Added (Flat Icons).
desktop/py3status: Updated for version 3.3.
development/atom: Updated for version 1.12.5.
development/cc-tool: Added (support for TI CC Debugger).
development/composer: Updated for version 1.2.2.
development/dart: Added (An application programming language).
development/dpkg: Updated for version 1.18.15.
development/hhvm: Updated for version 3.15.3.
development/pstack-expect-gdb: Added (print stack traces).
development/pycharm: Updated for version 2016.3.
games/OpenXcom: Updated for version 20161115_2133.
games/doomretro: Updated for version 2.3.6.
games/playonlinux: Updated for version 4.2.10.
graphics/gimagereader: Updated for version 3.2.0.
graphics/viewnior: Updated for version 1.6, new maintainer.
libraries/GtkD: Added (D binding for GTK+).
libraries/VTK: Add qt5 option
libraries/c-ares: Updated for version 1.12.0.
libraries/libcpuid: Updated for version 0.4.0.
libraries/libtorrent-rasterbar: Updated for version 1.0.10.
libraries/opencv: Add VTK support + new maintainer
misc/QCMA: Updated for version 0.4.1.
multimedia/devedeng: Updated for version 4.8.5.
multimedia/mkvalidator: Added (Verify Matroska and WebM files).
multimedia/obs-studio: Updated for version 0.16.6
multimedia/shotcut: Updated for version 16.11 + new maint.
network/clipgrab: Updated for version 3.6.2.
network/flexget: Updated for version 2.6.2.
network/imapfilter: Updated for version 2.6.7 + new maintainer.
network/opera-developer: Updated for version 43.0.2420.0.
network/opera: Updated for version 41.0.2353.69.
network/phpmyadmin: Updated for version 4.6.5.
network/qbittorrent: Updated for version 3.2.5.
network/speedtest-cli: Updated for version 1.0.0.
network/teamviewer: Update DEP and Documentation.
network/vivaldi: Updated for version 1.5.658.44.
network/you-get: Updated for version 0.4.595.
network/youtube-dl: Updated for version 2016.11.18.
office/calibre: Updated for version 2.72.0
perl/perl-CPAN-Perl-Releases: Updated for version 3.00.
perl/perl-Devel-PatchPerl: Updated for version 1.46.
perl/perl-File-pushd: Updated for version 1.014.
perl/perl-Math-BigInt-GMP: Updated for version 1.6000.
perl/perl-Math-BigInt: Updated for version 1.999800.
perl/perl-Math-MPFR: Updated for version 3.34.
perl/perl-Module-ScanDeps: Updated for version 1.23.
perl/perl-PAR: Updated for version 1.012.
perl/perl-String-PerlIdentifier: Updated for version 0.06.
perl/perl-Term-ReadLine-Gnu: Updated for version 1.35.
perl/perlbrew: Updated for version 0.78.
python/PyGreSQL: Updated for version 5.0.2
python/colored: Updated for version 1.3.3.
python/flake8: Updated for version 3.2.1.
python/parsel: Updated for version 1.1.0.
python/path.py: Updated for version 9.0.
python/pattern: Updated for version 2.6.
python/psutil: Updated for version 5.0.0
python/py3cairo: Fix build directory variable.
python/pycassa: Updated for version 1.11.1.
python/python-editor: Updated for version 1.0.2b.
python/python-keyutils: Updated for version 0.4.
python/python-requestbuilder: Updated for version 0.7.0
python/regex: Updated for version 2016.11.18.
python/tox: Updated for version 2.5.0.
ruby/ruby-build: Updated for version 20161121.
system/btrbk: Updated for version 0.24.0.
system/davfs2: Updated for version 1.5.4.
system/entr: Updated for version 3.6.
system/fzf: Updated for version 0.15.8.
system/hack-font-ttf: Updated for version 2.020.
system/keybase: Updated for version 1.0.18.
system/nix: Updated for version 1.11.4.
system/passwordsafe: Updated for version 1.00BETA.
system/qControlCenter: Update dep.
system/sysdig: Updated for version 0.12.1
system/terminix: Added (Tiling terminal emulator).
system/ttf-inconsolata: Added (Monospace Font).
system/unar: Added (tools to list and extract archive file contents)
system/wine-staging: Updated for version 1.9.23.
+--------------------------+

-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From didier at slint.fr  Sat Nov 26 11:47:49 2016
From: didier at slint.fr (Didier Spaier)
Date: Sat, 26 Nov 2016 12:47:49 +0100
Subject: [Slackbuilds-users] wink is 32-bit only
Message-ID: 

The wink binary packaged by the SlackBuild is 32-bit only.

Furthermore it dates back 20 June 2005, so I don't know if it still works.
I couldn't check yet as I don't have a 32-bit system at the moment.

Didier

PS I write directly to the list as the maintainer hasn't been active since
2005 according to the cgit search engine.

From didier at slint.fr  Sat Nov 26 11:52:33 2016
From: didier at slint.fr (Didier Spaier)
Date: Sat, 26 Nov 2016 12:52:33 +0100
Subject: [Slackbuilds-users] wink is 32-bit only
In-Reply-To: 
References: 
Message-ID: <4c32c9b7-d609-457d-689c-d94daa88f892@slint.fr>

Message re-transmitted, I made a typo in Ben Collver's email address, sorry.

Le 26/11/2016 ? 12:47, Didier Spaier a ?crit :
> The wink binary packaged by the SlackBuild is 32-bit only.
> 
> Furthermore it dates back 20 June 2005, so I don't know if it still works.
> I couldn't check yet as I don't have a 32-bit system at the moment.
> 
> Didier
> 
> PS I write directly to the list as the maintainer hasn't been active since
> 2005 according to the cgit search engine.

From dn2010 at gmail.com  Sat Nov 26 11:55:10 2016
From: dn2010 at gmail.com (Daniil Bratashov)
Date: Sat, 26 Nov 2016 14:55:10 +0300
Subject: [Slackbuilds-users] Fix for academic/ghemical
In-Reply-To: <44cab488-5958-e490-52c6-c4b740f81333@akionux.net>
References: <44cab488-5958-e490-52c6-c4b740f81333@akionux.net>
Message-ID: <20161126145510.37346692@darkstar.example.net>

On Sat, 26 Nov 2016 01:06:50 +0900
Akio Nishimura  wrote:

> Here is a fix for academic/ghemical. For multilib environment, LDFLAGS
> need to be set. --libdir option seems not working.

I've submitted the new version, with the patch applied. Thanks.

WBR, Daniil Bratashov.

From kingbeowulf at gmail.com  Sun Nov 27 02:12:39 2016
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 26 Nov 2016 18:12:39 -0800
Subject: [Slackbuilds-users] wink is 32-bit only
In-Reply-To: 
References: 
Message-ID: <72a9f88b-ddc3-198c-125d-83a7d667c4a9@gmail.com>

On 11/26/2016 03:47 AM, Didier Spaier wrote:
> The wink binary packaged by the SlackBuild is 32-bit only.
> 
> Furthermore it dates back 20 June 2005, so I don't know if it still works.
> I couldn't check yet as I don't have a 32-bit system at the moment.
> 
> Didier
> 
> PS I write directly to the list as the maintainer hasn't been active since
> 2005 according to the cgit search engine.

I just happened to be running my Slackware32 14.2 VM (Xfce) and having
nothing better to do...

Looks like wink-1.5 needs
1. the pangox-compat package on SBo
2. libexpat.so.0 symlink to linexpat.so.1.6.0



It runs, the console console spits out a bunch of GdkPixbuf-CRITICAL
failures, the GUI is a bit odd, but seems to work.  Rendered output is swf

-Ed







-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From slackbuilds at schoepfer.info  Sun Nov 27 13:00:39 2016
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 27 Nov 2016 14:00:39 +0100
Subject: [Slackbuilds-users] =?utf-8?b?RndkOiDlm57lpI3vvJog5Zue5aSN77ya?=
 =?utf-8?q?texworks_on_SBo?=
In-Reply-To: 
References: <295997c9-14e7-2d8b-c5d4-e37871d6807a@schoepfer.info>
 
 <62f443a2e943eab8fc2f1edde0ee08a9@schoepfer.info>
 
Message-ID: <627b10e3e96a2221327057b36ec476f3@schoepfer.info>

Hi,

i got permission to take over texworks, i'll submit an update soon.

-------- Original Message --------
Subject: ??? ???texworks on SBo
Date: 2016-11-27 12:28
 From: "digwtx" 
To: "Franzen" 

Sure. And, thanks, Johannes.

------------------ ???? ------------------

???: "Franzen";
????: 2016?11?27?(???) ??3:03
???: "digwtx";
??: Re: ???texworks on SBo

digwtx, i'd like to take over maintenance if you don't maintain it
anymore, ok?

Johannes

On 2016-11-27 02:07, digwtx wrote:
> Hi Johannes, thanks for asking, I'm not maintained texworks any more,
> but it really out of date, about 4 years.
> 
> ------------------ ???? ------------------
> 
> ???: "Franzen";
> ????: 2016?11?22?(???) ??7:08
> ???: "digwtx";
> ??: texworks on SBo
> 
> Hi digwtx,
> 
> are you still maintaining
> 
https://slackbuilds.org/slackbuilds/14.2/office/texworks/texworks.SlackBuild
> [1]
> ?
> It's a bit out of date.
> 
> Regards
> 
> Johannes
> 
> Links:
> ------
> [1]
> 
https://slackbuilds.org/slackbuilds/14.2/office/texworks/texworks.SlackBuild

From serban.udrea at skmail.ikp.physik.tu-darmstadt.de  Wed Nov 30 18:23:12 2016
From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea)
Date: Wed, 30 Nov 2016 19:23:12 +0100
Subject: [Slackbuilds-users] xdotool GPG failure
In-Reply-To: 
References: 
Message-ID: <154202a7f7d1e68a4e1c88e538d55c24.squirrel@skmail.ikp.physik.tu-darmstadt.de>

Hello,

I just tried to update xdotool using sbopkg and got an "GPG check FAILED!"
error message. Running "gpg --verify xdotool.tar.gz.asc" within the
repository resulted in:

gpg: assuming signed data in `xdotool.tar.gz'
gpg: Signature made Sat 15 Oct 2016 02:18:48 AM CEST using DSA key ID
9C7BA3B6
gpg: BAD signature from "SlackBuilds.org Development Team
"

No problems with other SlackBuilds I just installed/upgraded.

Best regards,

Serban Udrea


From willysr at slackbuilds.org  Wed Nov 30 18:49:07 2016
From: willysr at slackbuilds.org (Willy Sudiarto Raharjo)
Date: Thu, 1 Dec 2016 01:49:07 +0700
Subject: [Slackbuilds-users] xdotool GPG failure
In-Reply-To: <154202a7f7d1e68a4e1c88e538d55c24.squirrel@skmail.ikp.physik.tu-darmstadt.de>
References: 
 <154202a7f7d1e68a4e1c88e538d55c24.squirrel@skmail.ikp.physik.tu-darmstadt.de>
Message-ID: <33061f3e-02f8-d829-ca33-a3c825b20e91@slackbuilds.org>

> I just tried to update xdotool using sbopkg and got an "GPG check FAILED!"
> error message. Running "gpg --verify xdotool.tar.gz.asc" within the
> repository resulted in:
> 
> gpg: assuming signed data in `xdotool.tar.gz'
> gpg: Signature made Sat 15 Oct 2016 02:18:48 AM CEST using DSA key ID
> 9C7BA3B6
> gpg: BAD signature from "SlackBuilds.org Development Team
> "
> 
> No problems with other SlackBuilds I just installed/upgraded.

It's fixed now
make sure to run sbopkg -r again first


-- 
Willy Sudiarto Raharjo

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: 

From serban.udrea at skmail.ikp.physik.tu-darmstadt.de  Wed Nov 30 18:59:29 2016
From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea)
Date: Wed, 30 Nov 2016 19:59:29 +0100
Subject: [Slackbuilds-users] xdotool GPG failure
In-Reply-To: <33061f3e-02f8-d829-ca33-a3c825b20e91@slackbuilds.org>
References: 
 <154202a7f7d1e68a4e1c88e538d55c24.squirrel@skmail.ikp.physik.tu-darmstadt.de>
 <33061f3e-02f8-d829-ca33-a3c825b20e91@slackbuilds.org>
Message-ID: <3922e24b585b6fda84839e1cd16f7c85.squirrel@skmail.ikp.physik.tu-darmstadt.de>

>
> It's fixed now
> make sure to run sbopkg -r again first
> ...

Upgrade worked! Thank you very much for the very quick fix!

Best regards,

Serban


From bencollver at gmail.com  Wed Nov 30 22:44:19 2016
From: bencollver at gmail.com (Ben Collver)
Date: Wed, 30 Nov 2016 14:44:19 -0800
Subject: [Slackbuilds-users] wink is 32-bit only
In-Reply-To: <4c32c9b7-d609-457d-689c-d94daa88f892@slint.fr>
References: 
 <4c32c9b7-d609-457d-689c-d94daa88f892@slint.fr>
Message-ID: 

Hi Didier,

I don't have a 32-bit system at the moment and i no longer use wink.
Please feel free to retire the package.

Thank you,
-Ben

On Sat, Nov 26, 2016 at 3:52 AM, Didier Spaier  wrote:

> Message re-transmitted, I made a typo in Ben Collver's email address,
> sorry.
>
> Le 26/11/2016 ? 12:47, Didier Spaier a ?crit :
> > The wink binary packaged by the SlackBuild is 32-bit only.
> >
> > Furthermore it dates back 20 June 2005, so I don't know if it still
> works.
> > I couldn't check yet as I don't have a 32-bit system at the moment.
> >
> > Didier
> >
> > PS I write directly to the list as the maintainer hasn't been active
> since
> > 2005 according to the cgit search engine.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 

From greyhat701 at gmail.com  Wed Nov 30 20:22:33 2016
From: greyhat701 at gmail.com (Dazmed DZD)
Date: Wed, 30 Nov 2016 15:22:33 -0500
Subject: [Slackbuilds-users] Urgente
Message-ID: 

They may include curlew 0.2.2 in the repo to install with sbopkg O
With SLPK? besides quelea 2016.2?

https://sourceforge.net/projects/curlew/

https://sourceforge.net/projects/quelea/

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: