From alik at ejik.org Tue Dec 1 14:19:12 2015 From: alik at ejik.org (Alexander Verbovetsky) Date: Tue, 01 Dec 2015 17:19:12 +0300 Subject: [Slackbuilds-users] unison: failed md5sum Message-ID: <1448979552.1255622.454694369.30A660EE@webmail.messagingengine.com> Hello, the unison source has wrong md5: ERROR: system/unison: Failed md5sum: unison-2.40.128.tar.gz actual md5sum is 4194015003956a10a2d0a83e3e7733f7 On the other hand, the slackbuild works as is with the version changed to 2.48.3 (which is the current version). Best regards, Alexander Verbovetsky From alik at ejik.org Tue Dec 1 18:16:54 2015 From: alik at ejik.org (Alexander Verbovetsky) Date: Tue, 01 Dec 2015 21:16:54 +0300 Subject: [Slackbuilds-users] minidjvu source Message-ID: <1448993814.1326725.454949369.0D13D303@webmail.messagingengine.com> Hello, I'd like to make a slackbuild for minidjvu. Its latest source is: https://svn.code.sf.net/p/minidjvu/code/trunk/ (it is not changed after 2010). What is the best way to have a tarball suitable for submission? Best regards, Alexander Verbovetsky From brent at exitstatusone.com Tue Dec 1 18:42:31 2015 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 1 Dec 2015 11:42:31 -0700 Subject: [Slackbuilds-users] idna requires Message-ID: <565DEA17.7040602@exitstatusone.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello, While building idna I noticed that pysetuptools is missing as a dependency. I successfully built it after adding this to the REQUIRES. Thanks, - -- Brenton Earl -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWXeoXAAoJEMAWbOXyIOfzuLsH/2vGk8azx0ECMy/sBX1/k9LY 1Dg2G1Athk2SNmnRaVT07FiQ4lQv+cCrRmNXfmoF9H7EJp3mqePKBp5J+bTLr5lA 2cm9Akl8ZmBSznW3pT5SH3cLMR3F6kpNhmkXhv92j/YnKwcP0ANjyi61lrKXX6tJ zlT7E4R58q74981yRIkmJufjeQsu6Ff4FEqVU/qi46ICRXjqlQ+dLdHHrj1hz05X XdmavQCe6MWuDppconpqOnt5OcCbTwE5kuHskhcjQuCA6UUs6RGyhBzYvFzKGApM bxSLB5JQ/jpP+fX5qqq5Ph6XR+oZ8/VcgsiF0Fl0X0gBJf+GQfCBuXGNA3arXbE= =vBA4 -----END PGP SIGNATURE----- From didier at slint.fr Tue Dec 1 18:43:08 2015 From: didier at slint.fr (Didier Spaier) Date: Tue, 1 Dec 2015 19:43:08 +0100 Subject: [Slackbuilds-users] minidjvu source In-Reply-To: <1448993814.1326725.454949369.0D13D303@webmail.messagingengine.com> References: <1448993814.1326725.454949369.0D13D303@webmail.messagingengine.com> Message-ID: <565DEA3C.7070701@slint.fr> On 01/12/2015 19:16, Alexander Verbovetsky wrote: > Hello, > > I'd like to make a slackbuild for minidjvu. Its latest source is: > https://svn.code.sf.net/p/minidjvu/code/trunk/ > (it is not changed after 2010). > > What is the best way to have a tarball suitable for submission? > > Best regards, > Alexander Verbovetsky I would get it from Debian: https://packages.debian.org/source/jessie/minidjvu And check the patch they apply, maybe it's worthwhile. Cheers, Dider From alik at ejik.org Tue Dec 1 19:48:39 2015 From: alik at ejik.org (Alexander Verbovetsky) Date: Tue, 01 Dec 2015 22:48:39 +0300 Subject: [Slackbuilds-users] minidjvu source In-Reply-To: <565DEA3C.7070701@slint.fr> References: <1448993814.1326725.454949369.0D13D303@webmail.messagingengine.com> <565DEA3C.7070701@slint.fr> Message-ID: <1448999319.2074910.455022969.349BEB9C@webmail.messagingengine.com> > > I'd like to make a slackbuild for minidjvu. Its latest source is: > > https://svn.code.sf.net/p/minidjvu/code/trunk/ > > (it is not changed after 2010). > > > > What is the best way to have a tarball suitable for submission? On Tue, Dec 1, 2015, at 21:43, Didier Spaier wrote: > I would get it from Debian: > https://packages.debian.org/source/jessie/minidjvu Debian repacked the source, there is no corresponding changelog, for sure they got rid of waf. Wouldn't it better to use the original source? > And check the patch they apply, maybe it's worthwhile. The short summary of patch contains 2 non debian related changes: * remove unneeded AC_PROG_RANLIB from configure.ac * correct spelling by not using the non-word "splitted" of which the latter, I think, worth to implement :-) Best regards, Alexander From didier at slint.fr Tue Dec 1 20:20:54 2015 From: didier at slint.fr (Didier Spaier) Date: Tue, 1 Dec 2015 21:20:54 +0100 Subject: [Slackbuilds-users] minidjvu source In-Reply-To: <1448999319.2074910.455022969.349BEB9C@webmail.messagingengine.com> References: <1448993814.1326725.454949369.0D13D303@webmail.messagingengine.com> <565DEA3C.7070701@slint.fr> <1448999319.2074910.455022969.349BEB9C@webmail.messagingengine.com> Message-ID: <565E0126.6000104@slint.fr> On 01/12/2015 20:48, Alexander Verbovetsky wrote: >>> I'd like to make a slackbuild for minidjvu. Its latest source is: >>> https://svn.code.sf.net/p/minidjvu/code/trunk/ >>> (it is not changed after 2010). >>> >>> What is the best way to have a tarball suitable for submission? > > On Tue, Dec 1, 2015, at 21:43, Didier Spaier wrote: >> I would get it from Debian: >> https://packages.debian.org/source/jessie/minidjvu > > Debian repacked the source, there is no corresponding changelog, for > sure they got rid of waf. Wouldn't it better to use the original > source? You will be the maintainer, so that's _your_ decision ;) That being said, I would see if waf (I don"t know what it is) brings a real benefit to users: _ If no, I'd just take the Debian archive. Easier. _ If yes I would make an archive and store it somewhere. sbosrcarch would be a good new home for it, I think Cheers, Didier From alik at ejik.org Tue Dec 1 21:18:51 2015 From: alik at ejik.org (Alexander Verbovetsky) Date: Wed, 02 Dec 2015 00:18:51 +0300 Subject: [Slackbuilds-users] minidjvu source In-Reply-To: <565E0126.6000104@slint.fr> References: <1448993814.1326725.454949369.0D13D303@webmail.messagingengine.com> <565DEA3C.7070701@slint.fr> <1448999319.2074910.455022969.349BEB9C@webmail.messagingengine.com> <565E0126.6000104@slint.fr> Message-ID: <1449004731.2101403.455122249.60B096B4@webmail.messagingengine.com> > >>> I'd like to make a slackbuild for minidjvu. Its latest source is: > >>> https://svn.code.sf.net/p/minidjvu/code/trunk/ > >>> (it is not changed after 2010). > >>> > >>> What is the best way to have a tarball suitable for submission? On Tue, Dec 1, 2015, at 21:43, Didier Spaier wrote: > >> I would get it from Debian: > >> https://packages.debian.org/source/jessie/minidjvu > > > > Debian repacked the source, there is no corresponding changelog, for > > sure they got rid of waf. Wouldn't it better to use the original > > source? > > You will be the maintainer, so that's _your_ decision ;) > > That being said, I would see if waf (I don"t know what it is) > brings a real benefit to users: > _ If no, I'd just take the Debian archive. Easier. > _ If yes I would make an archive and store it somewhere. > sbosrcarch would be a good new home for it, I think It turned out that Ubuntu distributes both sources, the original one and the one modified by Debian. So, I'll use http://ftp.ubuntu.com/ubuntu/pool/universe/m/minidjvu/minidjvu_0.8.svn.2010.05.06.orig.tar.gz Thank you for all suggestions! Best regards, Alexander From willysr at slackbuilds.org Wed Dec 2 01:28:06 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 Dec 2015 08:28:06 +0700 Subject: [Slackbuilds-users] idna requires In-Reply-To: <565DEA17.7040602@exitstatusone.com> References: <565DEA17.7040602@exitstatusone.com> Message-ID: <565E4926.1060604@slackbuilds.org> > While building idna I noticed that pysetuptools is missing as a > dependency. I successfully built it after adding this to the REQUIRES. Fixed 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 willysr at slackbuilds.org Wed Dec 2 01:38:05 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 2 Dec 2015 08:38:05 +0700 Subject: [Slackbuilds-users] unison: failed md5sum In-Reply-To: <1448979552.1255622.454694369.30A660EE@webmail.messagingengine.com> References: <1448979552.1255622.454694369.30A660EE@webmail.messagingengine.com> Message-ID: <565E4B7D.5030301@slackbuilds.org> > the unison source has wrong md5: > > ERROR: system/unison: Failed md5sum: unison-2.40.128.tar.gz > actual md5sum is 4194015003956a10a2d0a83e3e7733f7 Fixed 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 info at microlinux.fr Wed Dec 2 17:21:24 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 2 Dec 2015 18:21:24 +0100 Subject: [Slackbuilds-users] Virtualization and package building Message-ID: <565F2894.7010807@microlinux.fr> Hi, I have to build packages for Slackware 14.0 and 14.1 as well as the upcoming 14.2, for both 32-bit and 64-bit architecture and different scenarios: server vs. desktop. Until april 2015 I built everything in a series of VirtualBox guests on my main workstation, which worked quite well most of the time. I vaguely remember having had trouble with one or two packages, but don't recall exactly which one. Since this date I've setup a dedicated package build host on a rather modest hardware (AMD dual core processor, meh), and with a quite bone-headed setup. No virtualization here, only a good old multiboot with a hard disk partitioned to death: 15 partitions with a shared swap and a maximum of 14 different systems, currently 8 in use. I reckon this is a rather unusual way of doing things, but 1) KISS 2) works perfectly. Last week I bought a thick book about Linux & Virtualization, and before diving head first into all this stuff, I have a general question out of curiosity. I guess most of you build your stuff in virtual guests (correct me if I'm wrong). What kind of virtualization do you use for this? KVM + qemu seems to be great for servers, but is it apt for setting up a desktop stuff and building graphical applications (Scribus, VLC, whatever)? I think I'll read the book differently if I already have a vague sense of where I'm heading. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From atelszewski at gmail.com Wed Dec 2 17:29:32 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Dec 2015 18:29:32 +0100 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <565F2894.7010807@microlinux.fr> References: <565F2894.7010807@microlinux.fr> Message-ID: <565F2A7C.3090205@gmail.com> On 02/12/15 18:21, Nicolas Kovacs wrote: > Hi, > > I have to build packages for Slackware 14.0 and 14.1 as well as the > upcoming 14.2, for both 32-bit and 64-bit architecture and different > scenarios: server vs. desktop. > > Until april 2015 I built everything in a series of VirtualBox guests on > my main workstation, which worked quite well most of the time. I vaguely > remember having had trouble with one or two packages, but don't recall > exactly which one. > > Since this date I've setup a dedicated package build host on a rather > modest hardware (AMD dual core processor, meh), and with a quite > bone-headed setup. No virtualization here, only a good old multiboot > with a hard disk partitioned to death: 15 partitions with a shared swap > and a maximum of 14 different systems, currently 8 in use. I reckon this > is a rather unusual way of doing things, but 1) KISS 2) works perfectly. > > Last week I bought a thick book about Linux & Virtualization, and before > diving head first into all this stuff, I have a general question out of > curiosity. I guess most of you build your stuff in virtual guests > (correct me if I'm wrong). I build natively on the machine that I'm running on. > What kind of virtualization do you use for > this? KVM + qemu seems to be great for servers, but is it apt for > setting up a desktop stuff and building graphical applications (Scribus, > VLC, whatever)? It doesn't matter, QEMU is equal for server and desktop. What matters is the software you have installed *within* the virtual machine. I you installed all the X & and friends, you can build for desktop (if by server we mean GUI-less and by desktop GUI-full). > > I think I'll read the book differently if I already have a vague sense > of where I'm heading. > > Cheers, > > Niki > -- Best regards, Andrzej Telszewski From brent at exitstatusone.com Wed Dec 2 18:33:15 2015 From: brent at exitstatusone.com (Brenton Earl) Date: Wed, 2 Dec 2015 11:33:15 -0700 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <565F2894.7010807@microlinux.fr> References: <565F2894.7010807@microlinux.fr> Message-ID: <565F396B.2040401@exitstatusone.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/02/2015 10:21 AM, Nicolas Kovacs wrote: > Last week I bought a thick book about Linux & Virtualization, and > before diving head first into all this stuff, I have a general > question out of curiosity. I guess most of you build your stuff in > virtual guests (correct me if I'm wrong). What kind of > virtualization do you use for this? KVM + qemu seems to be great > for servers, but is it apt for setting up a desktop stuff and > building graphical applications (Scribus, VLC, whatever)? > I use lxc containers. It comes with Slackware and works out of the box with the slackware template. All you need to do is set up a bridge on your primary NIC so you can download the sources, sbopkg, or any other development software you need. For x86 testing I still use virtualbox (headless) since my laptop is running x86_64. I don't usually build on multilib since it's not officially supported by SBo. This set up also works with wifi. - -- Brenton Earl -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWXzlrAAoJEMAWbOXyIOfzpMMH/1p93usL3k9rOANI8tvjI+22 o/PrOUwEQEzz0Q9j6agXIAkhMQn3LoGI9vs67PGAM9wY8zcZ1Om4rYZxu5AQFWCA mzisaOn86S82NQ1jHHCRWvDsH/2pYncjamHyv9FaDwZjEVA8RtXmPDv74firZ0di 0lIr3YukJKOcf/Do6T964NYmtlrifU73MoCZoqS72fjIfJ6Ql4+78g8CsuusIhz8 Zq4KbNkt/KFr9i1Xx9zSOdmo9RcYAh+9SwpZX3gIF4yxfi+ybDXZ8g0ssxgY4TdL kAuDqRjpgz4tFVAYTOaiSbQBtgCAC5A4vn8Gqs486HxANNw7nuPoN6Hg77XsvAI= =8aLZ -----END PGP SIGNATURE----- From slackalaxy at gmail.com Wed Dec 2 18:39:06 2015 From: slackalaxy at gmail.com (Petar Petrov) Date: Wed, 2 Dec 2015 20:39:06 +0200 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <565F2894.7010807@microlinux.fr> References: <565F2894.7010807@microlinux.fr> Message-ID: Hi Niki, i have virtual machines with clean installations of Slackware 14.1 x86 and x86_64. I have had trouble with building certain packages in the past, probably because I tweaked the VM settings without a good understanding of what I was doing. Therefore, I made this post in my humble blog, where I list my VM settings for (my own) future reference: https://slackalaxy.wordpress.com/2015/08/02/virtual-machine-settings/ bye Petar 2015-12-02 19:21 GMT+02:00 Nicolas Kovacs : > Hi, > > I have to build packages for Slackware 14.0 and 14.1 as well as the > upcoming 14.2, for both 32-bit and 64-bit architecture and different > scenarios: server vs. desktop. > > Until april 2015 I built everything in a series of VirtualBox guests on > my main workstation, which worked quite well most of the time. I vaguely > remember having had trouble with one or two packages, but don't recall > exactly which one. > > Since this date I've setup a dedicated package build host on a rather > modest hardware (AMD dual core processor, meh), and with a quite > bone-headed setup. No virtualization here, only a good old multiboot > with a hard disk partitioned to death: 15 partitions with a shared swap > and a maximum of 14 different systems, currently 8 in use. I reckon this > is a rather unusual way of doing things, but 1) KISS 2) works perfectly. > > Last week I bought a thick book about Linux & Virtualization, and before > diving head first into all this stuff, I have a general question out of > curiosity. I guess most of you build your stuff in virtual guests > (correct me if I'm wrong). What kind of virtualization do you use for > this? KVM + qemu seems to be great for servers, but is it apt for > setting up a desktop stuff and building graphical applications (Scribus, > VLC, whatever)? > > I think I'll read the book differently if I already have a vague sense > of where I'm heading. > > Cheers, > > Niki > -- > Microlinux - Solutions informatiques durables > 7, place de l'?glise - 30730 Montpezat > Web : http://www.microlinux.fr > Mail : info at microlinux.fr > T?l. : 04 66 63 10 32 > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at dawoodfall.net Wed Dec 2 18:57:14 2015 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 2 Dec 2015 18:57:14 +0000 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <565F2894.7010807@microlinux.fr> References: <565F2894.7010807@microlinux.fr> Message-ID: <20151202185713.GG4283@Blackswan> >Hi, > >I have to build packages for Slackware 14.0 and 14.1 as well as the >upcoming 14.2, for both 32-bit and 64-bit architecture and different >scenarios: server vs. desktop. > >Until april 2015 I built everything in a series of VirtualBox guests on >my main workstation, which worked quite well most of the time. I vaguely >remember having had trouble with one or two packages, but don't recall >exactly which one. > >Since this date I've setup a dedicated package build host on a rather >modest hardware (AMD dual core processor, meh), and with a quite >bone-headed setup. No virtualization here, only a good old multiboot >with a hard disk partitioned to death: 15 partitions with a shared swap >and a maximum of 14 different systems, currently 8 in use. I reckon this >is a rather unusual way of doing things, but 1) KISS 2) works perfectly. > >Last week I bought a thick book about Linux & Virtualization, and before >diving head first into all this stuff, I have a general question out of >curiosity. I guess most of you build your stuff in virtual guests >(correct me if I'm wrong). What kind of virtualization do you use for >this? KVM + qemu seems to be great for servers, but is it apt for >setting up a desktop stuff and building graphical applications (Scribus, >VLC, whatever)? > >I think I'll read the book differently if I already have a vague sense >of where I'm heading. > >Cheers, > >Niki I use chroots - a 64bit for pretty much everything, but I also have a 32bit chroot for building wine in. It's faster than booting a VM. Dave From atelszewski at gmail.com Wed Dec 2 19:02:35 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Dec 2015 20:02:35 +0100 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <20151202185713.GG4283@Blackswan> References: <565F2894.7010807@microlinux.fr> <20151202185713.GG4283@Blackswan> Message-ID: <565F404B.1020403@gmail.com> On 02/12/15 19:57, David Woodfall wrote: >> Hi, >> >> I have to build packages for Slackware 14.0 and 14.1 as well as the >> upcoming 14.2, for both 32-bit and 64-bit architecture and different >> scenarios: server vs. desktop. >> >> Until april 2015 I built everything in a series of VirtualBox guests on >> my main workstation, which worked quite well most of the time. I vaguely >> remember having had trouble with one or two packages, but don't recall >> exactly which one. >> >> Since this date I've setup a dedicated package build host on a rather >> modest hardware (AMD dual core processor, meh), and with a quite >> bone-headed setup. No virtualization here, only a good old multiboot >> with a hard disk partitioned to death: 15 partitions with a shared swap >> and a maximum of 14 different systems, currently 8 in use. I reckon this >> is a rather unusual way of doing things, but 1) KISS 2) works perfectly. >> >> Last week I bought a thick book about Linux & Virtualization, and before >> diving head first into all this stuff, I have a general question out of >> curiosity. I guess most of you build your stuff in virtual guests >> (correct me if I'm wrong). What kind of virtualization do you use for >> this? KVM + qemu seems to be great for servers, but is it apt for >> setting up a desktop stuff and building graphical applications (Scribus, >> VLC, whatever)? >> >> I think I'll read the book differently if I already have a vague sense >> of where I'm heading. >> >> Cheers, >> >> Niki > > I use chroots - a 64bit for pretty much everything, but I also have a > 32bit chroot for building wine in. It's faster than booting a VM. Can you write a bit more on how you do this? Or give an reference? > > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Pozdrawiam, Best regards, Andrzej Telszewski From dave at dawoodfall.net Wed Dec 2 20:04:02 2015 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 2 Dec 2015 20:04:02 +0000 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <565F404B.1020403@gmail.com> References: <565F2894.7010807@microlinux.fr> <20151202185713.GG4283@Blackswan> <565F404B.1020403@gmail.com> Message-ID: <20151202200402.GH4283@Blackswan> >On 02/12/15 19:57, David Woodfall wrote: >>>Hi, >>> >>>I have to build packages for Slackware 14.0 and 14.1 as well as the >>>upcoming 14.2, for both 32-bit and 64-bit architecture and different >>>scenarios: server vs. desktop. >>> >>>Until april 2015 I built everything in a series of VirtualBox guests on >>>my main workstation, which worked quite well most of the time. I vaguely >>>remember having had trouble with one or two packages, but don't recall >>>exactly which one. >>> >>>Since this date I've setup a dedicated package build host on a rather >>>modest hardware (AMD dual core processor, meh), and with a quite >>>bone-headed setup. No virtualization here, only a good old multiboot >>>with a hard disk partitioned to death: 15 partitions with a shared swap >>>and a maximum of 14 different systems, currently 8 in use. I reckon this >>>is a rather unusual way of doing things, but 1) KISS 2) works perfectly. >>> >>>Last week I bought a thick book about Linux & Virtualization, and before >>>diving head first into all this stuff, I have a general question out of >>>curiosity. I guess most of you build your stuff in virtual guests >>>(correct me if I'm wrong). What kind of virtualization do you use for >>>this? KVM + qemu seems to be great for servers, but is it apt for >>>setting up a desktop stuff and building graphical applications (Scribus, >>>VLC, whatever)? >>> >>>I think I'll read the book differently if I already have a vague sense >>>of where I'm heading. >>> >>>Cheers, >>> >>>Niki >> >>I use chroots - a 64bit for pretty much everything, but I also have a >>32bit chroot for building wine in. It's faster than booting a VM. > >Can you write a bit more on how you do this? >Or give an reference? I use this 'mkchroot' script, after mounting the Slackware DVD, to install into the chroot: ########################################## #!/bin/sh set -e SERIES="a ap d f k kde l n t tcl x xap y" CHPATH="/home/chroots/slackware64" CDPATH="/mnt/cdrom/slackware64" bgreen="^[[01;32m" normal="^[[0m" cd $CDPATH for i in $SERIES do echo "${bgreen}Installing series $i${normal}" upgradepkg --reinstall --install-new -root $CHPATH $i/*.t?z done mkdir -p $CHROOT/proc mkdir -p $CHROOT/dev mkdir -p $CHROOT/sys mkdir -p $CHROOT/tmp ########################################## I use this script 'cht' to use log in: ########################################## #!/bin/sh CHROOT=/home/chroots/slackware64 if [ ! -r "$CHROOT" ]; then exit 1 fi # These are now mounted in /etc/fstab #mount -o bind /proc $CHROOT/proc #mount -o bind /dev $CHROOT/dev #mount -o bind /sys $CHROOT/sys #mount -o bind /tmp $CHROOT/tmp cp /etc/resolv.conf $CHROOT/etc cp /home/david/.Xauthority $CHROOT/root chroot $CHROOT /bin/zsh ########################################## My /etc/fstab entries: /proc /home/chroots/slackware64/proc auto rw,bind,noatime 0 0 /dev /home/chroots/slackware64/dev auto rw,bind,noatime 0 0 /sys /home/chroots/slackware64/sys auto rw,bind,noatime 0 0 /tmp /home/chroots/slackware64/tmp auto rw,bind,noatime 0 0 /tmp is shared between guest and host so I can move files/packages in and out easier. Hope this help. David -------------- next part -------------- #!/bin/sh set -e SERIES="a ap d f k kde l n t tcl x xap y" CHPATH="/home/chroots/slackware64" CDPATH="/mnt/cdrom/slackware64" bgreen="" normal="" cd $CDPATH for i in $SERIES do echo "${bgreen}Installing series $i${normal}" upgradepkg --reinstall --install-new -root $CHPATH $i/*.t?z done -------------- next part -------------- #!/bin/sh CHROOT=/home/chroots/slackware64 if [ ! -r "$CHROOT" ]; then exit 1 fi # These are now mounted in /etc/fstab #mount -o bind /proc $CHROOT/proc #mount -o bind /dev $CHROOT/dev #mount -o bind /sys $CHROOT/sys #mount -o bind /tmp $CHROOT/tmp cp /etc/resolv.conf $CHROOT/etc cp /home/david/.Xauthority $CHROOT/root chroot $CHROOT /bin/zsh From fernando.lopezjr at gmail.com Wed Dec 2 20:10:05 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 2 Dec 2015 13:10:05 -0700 Subject: [Slackbuilds-users] KiCad 4 is out. Message-ID: Just to let you know that kicad 4 is out... =) kicad-pcb.org/post/release-4.0.0/ -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ryan.q at linux.com Wed Dec 2 20:19:55 2015 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 02 Dec 2015 20:19:55 +0000 Subject: [Slackbuilds-users] KiCad 4 is out. In-Reply-To: References: Message-ID: On Wed, Dec 2, 2015 at 12:10 PM Fernando Lopez wrote: > Just to let you know that kicad 4 is out... =) > > kicad-pcb.org/post/release-4.0.0/ > Probably a good idea to CC the maintainer on emails like this (not all of them are subscribed to this mailing list). In this case, Niels Horn gave up all his builds, so you could probably take this one if someone else hasn't already claimed it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Wed Dec 2 20:35:10 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Wed, 2 Dec 2015 13:35:10 -0700 Subject: [Slackbuilds-users] KiCad 4 is out. In-Reply-To: References: Message-ID: okay. i'll take it. On Wed, Dec 2, 2015 at 1:19 PM, Ryan P.C. McQuen wrote: > > > On Wed, Dec 2, 2015 at 12:10 PM Fernando Lopez > wrote: > >> Just to let you know that kicad 4 is out... =) >> >> kicad-pcb.org/post/release-4.0.0/ >> > > Probably a good idea to CC the maintainer on emails like this (not all of > them are subscribed to this mailing list). > > In this case, Niels Horn gave up all his builds, so you could probably > take this one if someone else hasn't already claimed it. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Wed Dec 2 21:11:10 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 2 Dec 2015 22:11:10 +0100 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <20151202200402.GH4283@Blackswan> References: <565F2894.7010807@microlinux.fr> <20151202185713.GG4283@Blackswan> <565F404B.1020403@gmail.com> <20151202200402.GH4283@Blackswan> Message-ID: <565F5E6E.7010705@gmail.com> On 02/12/15 21:04, David Woodfall wrote: >> On 02/12/15 19:57, David Woodfall wrote: >>>> Hi, >>>> >>>> I have to build packages for Slackware 14.0 and 14.1 as well as the >>>> upcoming 14.2, for both 32-bit and 64-bit architecture and different >>>> scenarios: server vs. desktop. >>>> >>>> Until april 2015 I built everything in a series of VirtualBox guests on >>>> my main workstation, which worked quite well most of the time. I >>>> vaguely >>>> remember having had trouble with one or two packages, but don't recall >>>> exactly which one. >>>> >>>> Since this date I've setup a dedicated package build host on a rather >>>> modest hardware (AMD dual core processor, meh), and with a quite >>>> bone-headed setup. No virtualization here, only a good old multiboot >>>> with a hard disk partitioned to death: 15 partitions with a shared swap >>>> and a maximum of 14 different systems, currently 8 in use. I reckon >>>> this >>>> is a rather unusual way of doing things, but 1) KISS 2) works >>>> perfectly. >>>> >>>> Last week I bought a thick book about Linux & Virtualization, and >>>> before >>>> diving head first into all this stuff, I have a general question out of >>>> curiosity. I guess most of you build your stuff in virtual guests >>>> (correct me if I'm wrong). What kind of virtualization do you use for >>>> this? KVM + qemu seems to be great for servers, but is it apt for >>>> setting up a desktop stuff and building graphical applications >>>> (Scribus, >>>> VLC, whatever)? >>>> >>>> I think I'll read the book differently if I already have a vague sense >>>> of where I'm heading. >>>> >>>> Cheers, >>>> >>>> Niki >>> >>> I use chroots - a 64bit for pretty much everything, but I also have a >>> 32bit chroot for building wine in. It's faster than booting a VM. >> >> Can you write a bit more on how you do this? >> Or give an reference? > > I use this 'mkchroot' script, after mounting the Slackware DVD, to > install into the chroot: > > ########################################## > #!/bin/sh > > set -e > > SERIES="a ap d f k kde l n t tcl x xap y" > CHPATH="/home/chroots/slackware64" > CDPATH="/mnt/cdrom/slackware64" > bgreen="^[[01;32m" > normal="^[[0m" > > cd $CDPATH > > for i in $SERIES > do > echo "${bgreen}Installing series $i${normal}" > upgradepkg --reinstall --install-new -root $CHPATH $i/*.t?z > done > > mkdir -p $CHROOT/proc > mkdir -p $CHROOT/dev > mkdir -p $CHROOT/sys > mkdir -p $CHROOT/tmp > ########################################## > > I use this script 'cht' to use log in: > > ########################################## > #!/bin/sh > > CHROOT=/home/chroots/slackware64 > > if [ ! -r "$CHROOT" ]; then > exit 1 > fi > > # These are now mounted in /etc/fstab > #mount -o bind /proc $CHROOT/proc > #mount -o bind /dev $CHROOT/dev > #mount -o bind /sys $CHROOT/sys > #mount -o bind /tmp $CHROOT/tmp > > cp /etc/resolv.conf $CHROOT/etc > cp /home/david/.Xauthority $CHROOT/root > > chroot $CHROOT /bin/zsh > ########################################## > > My /etc/fstab entries: > > /proc /home/chroots/slackware64/proc auto rw,bind,noatime 0 0 > /dev /home/chroots/slackware64/dev auto rw,bind,noatime 0 0 > /sys /home/chroots/slackware64/sys auto rw,bind,noatime 0 0 > /tmp /home/chroots/slackware64/tmp auto rw,bind,noatime 0 0 > > /tmp is shared between guest and host so I can move files/packages in > and out easier. > > Hope this help. Yes, it helps a lot:) Bonus questions: How do you do 32-bit chroot on 64-bit system? Is it the same as for 64-bit one? Are there any gotchas to be aware of? I hope I don't eat too much time of yours;) > > David > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > -- Pozdrawiam, Best regards, Andrzej Telszewski From dave at dawoodfall.net Wed Dec 2 21:58:57 2015 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 2 Dec 2015 21:58:57 +0000 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <565F5E6E.7010705@gmail.com> References: <565F2894.7010807@microlinux.fr> <20151202185713.GG4283@Blackswan> <565F404B.1020403@gmail.com> <20151202200402.GH4283@Blackswan> <565F5E6E.7010705@gmail.com> Message-ID: <20151202215857.GJ4283@Blackswan> >On 02/12/15 21:04, David Woodfall wrote: >>>On 02/12/15 19:57, David Woodfall wrote: >>>>>Hi, >>>>> >>>>>I have to build packages for Slackware 14.0 and 14.1 as well as the >>>>>upcoming 14.2, for both 32-bit and 64-bit architecture and different >>>>>scenarios: server vs. desktop. >>>>> >>>>>Until april 2015 I built everything in a series of VirtualBox guests on >>>>>my main workstation, which worked quite well most of the time. I >>>>>vaguely >>>>>remember having had trouble with one or two packages, but don't recall >>>>>exactly which one. >>>>> >>>>>Since this date I've setup a dedicated package build host on a rather >>>>>modest hardware (AMD dual core processor, meh), and with a quite >>>>>bone-headed setup. No virtualization here, only a good old multiboot >>>>>with a hard disk partitioned to death: 15 partitions with a shared swap >>>>>and a maximum of 14 different systems, currently 8 in use. I reckon >>>>>this >>>>>is a rather unusual way of doing things, but 1) KISS 2) works >>>>>perfectly. >>>>> >>>>>Last week I bought a thick book about Linux & Virtualization, and >>>>>before >>>>>diving head first into all this stuff, I have a general question out of >>>>>curiosity. I guess most of you build your stuff in virtual guests >>>>>(correct me if I'm wrong). What kind of virtualization do you use for >>>>>this? KVM + qemu seems to be great for servers, but is it apt for >>>>>setting up a desktop stuff and building graphical applications >>>>>(Scribus, >>>>>VLC, whatever)? >>>>> >>>>>I think I'll read the book differently if I already have a vague sense >>>>>of where I'm heading. >>>>> >>>>>Cheers, >>>>> >>>>>Niki >>>> >>>>I use chroots - a 64bit for pretty much everything, but I also have a >>>>32bit chroot for building wine in. It's faster than booting a VM. >>> >>>Can you write a bit more on how you do this? >>>Or give an reference? >> >>I use this 'mkchroot' script, after mounting the Slackware DVD, to >>install into the chroot: >> >>########################################## >>#!/bin/sh >> >>set -e >> >>SERIES="a ap d f k kde l n t tcl x xap y" >>CHPATH="/home/chroots/slackware64" >>CDPATH="/mnt/cdrom/slackware64" >>bgreen="^[[01;32m" >>normal="^[[0m" >> >>cd $CDPATH >> >>for i in $SERIES >>do >> echo "${bgreen}Installing series $i${normal}" >> upgradepkg --reinstall --install-new -root $CHPATH $i/*.t?z >>done >> >>mkdir -p $CHROOT/proc >>mkdir -p $CHROOT/dev >>mkdir -p $CHROOT/sys >>mkdir -p $CHROOT/tmp >>########################################## >> >>I use this script 'cht' to use log in: >> >>########################################## >>#!/bin/sh >> >>CHROOT=/home/chroots/slackware64 >> >>if [ ! -r "$CHROOT" ]; then >> exit 1 >>fi >> >># These are now mounted in /etc/fstab >>#mount -o bind /proc $CHROOT/proc >>#mount -o bind /dev $CHROOT/dev >>#mount -o bind /sys $CHROOT/sys >>#mount -o bind /tmp $CHROOT/tmp >> >>cp /etc/resolv.conf $CHROOT/etc >>cp /home/david/.Xauthority $CHROOT/root >> >>chroot $CHROOT /bin/zsh >>########################################## >> >>My /etc/fstab entries: >> >>/proc /home/chroots/slackware64/proc auto rw,bind,noatime 0 0 >>/dev /home/chroots/slackware64/dev auto rw,bind,noatime 0 0 >>/sys /home/chroots/slackware64/sys auto rw,bind,noatime 0 0 >>/tmp /home/chroots/slackware64/tmp auto rw,bind,noatime 0 0 >> >>/tmp is shared between guest and host so I can move files/packages in >>and out easier. >> >>Hope this help. > >Yes, it helps a lot:) > >Bonus questions: >How do you do 32-bit chroot on 64-bit system? >Is it the same as for 64-bit one? >Are there any gotchas to be aware of? > >I hope I don't eat too much time of yours;) There is no real difference between the 32 and 64bit version. No patches that I'm aware of or have ever needed. I find it useful for building 32bit packages on a multilib host too. From atelszewski at gmail.com Thu Dec 3 00:27:45 2015 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 3 Dec 2015 01:27:45 +0100 Subject: [Slackbuilds-users] Virtualization and package building In-Reply-To: <20151202215857.GJ4283@Blackswan> References: <565F2894.7010807@microlinux.fr> <20151202185713.GG4283@Blackswan> <565F404B.1020403@gmail.com> <20151202200402.GH4283@Blackswan> <565F5E6E.7010705@gmail.com> <20151202215857.GJ4283@Blackswan> Message-ID: <565F8C81.20409@gmail.com> On 02/12/15 22:58, David Woodfall wrote: >> On 02/12/15 21:04, David Woodfall wrote: >>>> On 02/12/15 19:57, David Woodfall wrote: >>>>>> Hi, >>>>>> >>>>>> I have to build packages for Slackware 14.0 and 14.1 as well as the >>>>>> upcoming 14.2, for both 32-bit and 64-bit architecture and different >>>>>> scenarios: server vs. desktop. >>>>>> >>>>>> Until april 2015 I built everything in a series of VirtualBox >>>>>> guests on >>>>>> my main workstation, which worked quite well most of the time. I >>>>>> vaguely >>>>>> remember having had trouble with one or two packages, but don't >>>>>> recall >>>>>> exactly which one. >>>>>> >>>>>> Since this date I've setup a dedicated package build host on a rather >>>>>> modest hardware (AMD dual core processor, meh), and with a quite >>>>>> bone-headed setup. No virtualization here, only a good old multiboot >>>>>> with a hard disk partitioned to death: 15 partitions with a shared >>>>>> swap >>>>>> and a maximum of 14 different systems, currently 8 in use. I reckon >>>>>> this >>>>>> is a rather unusual way of doing things, but 1) KISS 2) works >>>>>> perfectly. >>>>>> >>>>>> Last week I bought a thick book about Linux & Virtualization, and >>>>>> before >>>>>> diving head first into all this stuff, I have a general question >>>>>> out of >>>>>> curiosity. I guess most of you build your stuff in virtual guests >>>>>> (correct me if I'm wrong). What kind of virtualization do you use for >>>>>> this? KVM + qemu seems to be great for servers, but is it apt for >>>>>> setting up a desktop stuff and building graphical applications >>>>>> (Scribus, >>>>>> VLC, whatever)? >>>>>> >>>>>> I think I'll read the book differently if I already have a vague >>>>>> sense >>>>>> of where I'm heading. >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Niki >>>>> >>>>> I use chroots - a 64bit for pretty much everything, but I also have a >>>>> 32bit chroot for building wine in. It's faster than booting a VM. >>>> >>>> Can you write a bit more on how you do this? >>>> Or give an reference? >>> >>> I use this 'mkchroot' script, after mounting the Slackware DVD, to >>> install into the chroot: >>> >>> ########################################## >>> #!/bin/sh >>> >>> set -e >>> >>> SERIES="a ap d f k kde l n t tcl x xap y" >>> CHPATH="/home/chroots/slackware64" >>> CDPATH="/mnt/cdrom/slackware64" >>> bgreen="^[[01;32m" >>> normal="^[[0m" >>> >>> cd $CDPATH >>> >>> for i in $SERIES >>> do >>> echo "${bgreen}Installing series $i${normal}" >>> upgradepkg --reinstall --install-new -root $CHPATH $i/*.t?z >>> done >>> >>> mkdir -p $CHROOT/proc >>> mkdir -p $CHROOT/dev >>> mkdir -p $CHROOT/sys >>> mkdir -p $CHROOT/tmp >>> ########################################## >>> >>> I use this script 'cht' to use log in: >>> >>> ########################################## >>> #!/bin/sh >>> >>> CHROOT=/home/chroots/slackware64 >>> >>> if [ ! -r "$CHROOT" ]; then >>> exit 1 >>> fi >>> >>> # These are now mounted in /etc/fstab >>> #mount -o bind /proc $CHROOT/proc >>> #mount -o bind /dev $CHROOT/dev >>> #mount -o bind /sys $CHROOT/sys >>> #mount -o bind /tmp $CHROOT/tmp >>> >>> cp /etc/resolv.conf $CHROOT/etc >>> cp /home/david/.Xauthority $CHROOT/root >>> >>> chroot $CHROOT /bin/zsh >>> ########################################## >>> >>> My /etc/fstab entries: >>> >>> /proc /home/chroots/slackware64/proc auto rw,bind,noatime 0 0 >>> /dev /home/chroots/slackware64/dev auto rw,bind,noatime 0 0 >>> /sys /home/chroots/slackware64/sys auto rw,bind,noatime 0 0 >>> /tmp /home/chroots/slackware64/tmp auto rw,bind,noatime 0 0 >>> >>> /tmp is shared between guest and host so I can move files/packages in >>> and out easier. >>> >>> Hope this help. >> >> Yes, it helps a lot:) >> >> Bonus questions: >> How do you do 32-bit chroot on 64-bit system? >> Is it the same as for 64-bit one? >> Are there any gotchas to be aware of? >> >> I hope I don't eat too much time of yours;) > > There is no real difference between the 32 and 64bit version. No > patches that I'm aware of or have ever needed. I find it useful for > building 32bit packages on a multilib host too. Thank you for the info. That sounds interesting. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -- Pozdrawiam, Best regards, Andrzej Telszewski From z.coldplayer at gmail.com Thu Dec 3 09:36:23 2015 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Thu, 3 Dec 2015 13:36:23 +0400 Subject: [Slackbuilds-users] Fwd: bad url for spatialite-tools In-Reply-To: References: Message-ID: ---------- Forwarded message ---------- From: Jheengut Pritvi Date: 17 November 2015 at 10:19 Subject: bad url for spatialite-tools To: mailman at slackbuilds.org I was compiling spatialite-tools and found the download url to be www.gaia-gis.it/gaia-sins/spatialite-tools-sources/spatialite-tools-4.2.0.tar.gz instead of http://www.gaia-gis.it/gaia-sins/spatialite-tools-4.2.0.tar.gz -------------- next part -------------- An HTML attachment was scrubbed... URL: From hostmaster at slackonly.com Fri Dec 4 11:18:31 2015 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Fri, 4 Dec 2015 13:18:31 +0200 Subject: [Slackbuilds-users] bcdoc Message-ID: <56617687.8050706@slackonly.com> Hi! bcdoc needs python-setuptools to build: File "setup.py", line 5, in from setuptools import setup ImportError: No module named setuptools But this package is available only to slackware-current. Thanks! From chris.willing at iinet.net.au Fri Dec 4 12:09:08 2015 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 4 Dec 2015 22:09:08 +1000 Subject: [Slackbuilds-users] bcdoc In-Reply-To: <56617687.8050706@slackonly.com> References: <56617687.8050706@slackonly.com> Message-ID: <56618264.6030105@iinet.net.au> On 12/04/2015 09:18 PM, Panagiotis Nikolaou wrote: > Hi! > bcdoc needs python-setuptools to build: > > File "setup.py", line 5, in > from setuptools import setup > ImportError: No module named setuptools > > But this package is available only to slackware-current. SBo has pysetuptools for 14.1 - same software, different name and version (18.2). chris From willysr at slackbuilds.org Fri Dec 4 18:16:21 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Dec 2015 01:16:21 +0700 Subject: [Slackbuilds-users] bcdoc In-Reply-To: <56617687.8050706@slackonly.com> References: <56617687.8050706@slackonly.com> Message-ID: <5661D875.6090901@slackbuilds.org> > bcdoc needs python-setuptools to build: > > File "setup.py", line 5, in > from setuptools import setup > ImportError: No module named setuptools Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Dec 5 01:12:39 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 5 Dec 2015 08:12:39 +0700 Subject: [Slackbuilds-users] Updates - 20151205.1 Message-ID: <56623A07.6010402@slackbuilds.org> Sat Dec 5 01:00:40 UTC 2015 academic/gwyddion: Updated for version 2.43. academic/spatialite-tools: Update DOWNLOAD url. audio/opus: Updated for version 1.1.1. desktop/dmenu: Updated for version 4.6. desktop/menutray: Updated for version 0.44. desktop/openbox-menu: Updated for version 0.8.0. development/asm6809: Added (6809/6309 cross assmbler). development/eagle: Updated for version 7.5.0. development/hub: Updated for version 2.2.2. development/lwtools: Added (6809/6309 cross-development tools). development/nodejs: Updated for version 4.2.3. development/poedit: Updated for version 1.8.6. development/scons: Updated for version 2.4.1. games/Tempus-Irae: Added (game data). games/marathon-eternal-data: Added (game data). games/marathon-evil-data: Added (game data). games/marathon-red-data: Added (game data). games/marathon-rubicon-data: Added (game data). games/pioneer: Updated for version 20151130. games/warsow: Updated for version 2.0 + new maintainer. graphics/fritzing: Updated for version 0.9.2b. graphics/pngcrush: Updated for version 1.7.88. graphics/qelectrotech: Updated for version 0.5. libraries/activemq-cpp: Added (ActiveMQ CPP Library). libraries/bcdoc: Update DEP. libraries/enum34: Updated for version 1.1.1. libraries/libbonobo: Added new patch. libraries/libgit2: Updated for version 0.23.4. misc/dos2unix: Updated for version 7.3.2. misc/sigrok-firmware-fx2lafw: Updated for version 0.1.3. misc/wcd: Updated for version 5.3.1. multimedia/pitivi: Updated for version 0.95. network/ClusterSSH: Updated for version 4.05. network/Electrum: Updated for version 2.5.4. network/broadcom-sta: Updated for version 6.30.223.271. network/guacamole-client: Updated for version 0.9.8. network/guacamole-server: Updated for version 0.9.8. network/icecat: Updated for version 38.4.0. network/icinga2: Updated for version 2.4.0. network/icingaweb2: Updated for version 2.1.0. network/ii: Added (minimalist IRC client). network/palemoon: Updated for version 25.8.1. network/pentadactyl: Updated for version 20151201. network/teamviewer: Updated for version 11.0.52520. network/vivaldi: Updated for version 1.0.334.3_1. network/you-get: Updated for version 0.4.176. network/youtube-dl: Updated for version 2015.11.27.1. office/MasterPDFEditor: Updated for version 3.5.02. office/libreoffice-langpack: Update README. office/minidjvu: Added (bitonal DjVu encoder/decoder). office/qpdf: Updated for version 6.0.0. office/xtrkcad: Updated for version 4.2.2. perl/perl-AnyEvent-HTTP: Fix download url. perl/perl-Class-MethodMaker: Fix download url. perl/perl-File-Copy-Recursive: Added (perl extension). perl/perl-File-ShareDir-Install: Added (install shared files). perl/perl-IO-All: Added (IO modules). perl/perl-IO-Socket-IP: Fix download url. perl/perl-IO-Socket-SSL: Avoid waiting user input. perl/perl-Inline-C: Added (C language support for Inline). perl/perl-Inline: Update README. perl/perl-Lingua-EN-Numbers-Ordinate: Fix download url. perl/perl-NetPacket: Fix download url. perl/perl-Pegex: Added (Acmeist PEG Parser Framework). perl/perl-Test-MockObject: Fix download url. perl/perl-YAML-LibYAML: Added (Perl YAML Serialization). python/click: Updated for version 6.2. python/idna: Update DEP. python/netlib: Added (Network utilities). python/py: Updated for version 1.4.31. python/pyperclip: Added (Python copy and paste clipboard functions). python/python-certifi: Updated for version 2015.11.20.1 python/python-pillow: Added (Python Imaging Library). system/Iosevka: Updated for version 1.0.0. system/clamav: Updated for version 0.99. system/distorm3: Added (Disassembler Library). system/gpart: Add support to LVMS2 and btrfs. system/hack-font-ttf: Updated for version 2.018. system/lxdm: Updated for version 0.5.3. system/unison: Fix MD5SUM. system/virt-manager: Reverted to version 1.2.1. system/volatility: Added (memory extraction utility framework). system/winetricks: Updated for version 20151116. system/wmconfig: Updated for version 1.4.11. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From thedoogster at gmail.com Sun Dec 6 18:08:11 2015 From: thedoogster at gmail.com (Doogster) Date: Sun, 6 Dec 2015 10:08:11 -0800 Subject: [Slackbuilds-users] Anyone want to take ownership of "oss"? Message-ID: Would anyone like to take over ownership of the "oss" (OSS4 from OpenSound) SlackBuild? I'm really not the best person to be maintaining it, because I stopped using it years ago. And OSS4 isn't something that you can test without actually being a user of it. If no-one steps up within 7 days, I'm going to orphan it. From info at microlinux.fr Wed Dec 9 11:00:44 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 9 Dec 2015 12:00:44 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current Message-ID: <566809DC.9030807@microlinux.fr> Hi, The issue has already been raised on LQ, but I think this is a better place to discuss it. Here's the context. Just installed a stock Slackware64 -current on a box, full installation without KDE. Then I built libgnomecanvas and gdm from SlackBuilds.org. Switched to init4 to fire up GDM, logged in to Xfce, and here's what I get: $ ck-list-sessions Session1: unix-user = '0' realname = '(null)' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2015-12-09T10:48:45.985157Z' login-session-id = '4294967295' When I remove GDM and use XDM instead, I'm getting this, as expected: $ ck-list-sessions Session2: unix-user = '1000' realname = 'Niki Kovacs' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2015-12-09T10:54:56.858488Z' login-session-id = '4294967295' I've googled around a bit, but to no avail. If anyone has a remote idea of how to make GDM behave under Slackware -current, I'd be grateful. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Wed Dec 9 12:09:28 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 9 Dec 2015 19:09:28 +0700 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <566809DC.9030807@microlinux.fr> References: <566809DC.9030807@microlinux.fr> Message-ID: <566819F8.7030500@slackbuilds.org> > Just installed a stock Slackware64 -current on a box, full installation > without KDE. > > Then I built libgnomecanvas and gdm from SlackBuilds.org. Switched to > init4 to fire up GDM, logged in to Xfce, and here's what I get: > > $ ck-list-sessions > Session1: > unix-user = '0' > realname = '(null)' > seat = 'Seat1' > session-type = '' > active = TRUE > x11-display = ':0' > x11-display-device = '/dev/tty7' > display-device = '' > remote-host-name = '' > is-local = TRUE > on-since = '2015-12-09T10:48:45.985157Z' > login-session-id = '4294967295' > > When I remove GDM and use XDM instead, I'm getting this, as expected: > > $ ck-list-sessions > Session2: > unix-user = '1000' > realname = 'Niki Kovacs' > seat = 'Seat1' > session-type = '' > active = TRUE > x11-display = ':0' > x11-display-device = '/dev/tty7' > display-device = '' > remote-host-name = '' > is-local = TRUE > on-since = '2015-12-09T10:54:56.858488Z' > login-session-id = '4294967295' > > > I've googled around a bit, but to no avail. If anyone has a remote idea > of how to make GDM behave under Slackware -current, I'd be grateful. well, gdm in SBo itself is quite old (5 years ago) the latest 2.2x version was 2.32 released in 2011 (4 years ago) and the latest one now is 3.18 which was released in November with all the big changes in -current, you probably need to try to test the new gdm 3.x -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Wed Dec 9 12:12:45 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 9 Dec 2015 13:12:45 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <566819F8.7030500@slackbuilds.org> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> Message-ID: <56681ABD.6000906@microlinux.fr> Le 09/12/2015 13:09, Willy Sudiarto Raharjo a ?crit : > well, gdm in SBo itself is quite old (5 years ago) the latest 2.2x > version was 2.32 released in 2011 (4 years ago) and the latest one > now is 3.18 which was released in November > > with all the big changes in -current, you probably need to try to > test the new gdm 3.x I vaguely remember gdm 3.x has dropped ConsoleKit support somewhere along the way. It seems to go down the path of all things GNOME, with a hard dependency on systemd. Time to let it go sooner or later, I guess. I'm currently fiddling with LXDM, which looks quite promising, even though I can't seem to be get the login window to display in french. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Wed Dec 9 12:40:00 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 9 Dec 2015 13:40:00 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <566819F8.7030500@slackbuilds.org> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> Message-ID: <56682120.7080004@microlinux.fr> Le 09/12/2015 13:09, Willy Sudiarto Raharjo a ?crit : > with all the big changes in -current, you probably need to try to > test the new gdm 3.x I admit I'm a bit confused right now. I feel the sort of light nausea you have when you are confronted with about half a dozen possible solutions, and none of them work as expected. So, I'm looking for a nice (!) functional (!) display manager for Xfce, on a machine where more or less everything is installed except KDE. 1. XDM works, but it's quite ugly. Maybe I'll look into how to customize it, but later, after I tried all the others. 2. SLiM works, except there's no shutdown/reboot button, which is essential for my users. Plus, login texts are hardcoded, so you would have to hand-edit SLiM's configuration file to replace these. 3. LXDM also works, except its window stubbornly displays everything in english on a machine where LANG is set to fr_FR.utf8. It's either untranslated, or I didn't find the special secret configuration option in the special secret configuration file to make it work. 4. LightDM could be another option, except there's no package on SBo. I took a peek at Willy's and ivandi's stuff. As far as I know, it has one single dependency on Linux-PAM. Correct me if I'm wrong. 5. I vaguely though about installing KDE's sddm login manager. I don't know how much of KDE I would need, if this would work, and if so, how "heavy" would this be. 6. Maybe a more recent GDM from the 3.x series, but *before* they dropped ConsoleKit support, is the way to go? At this stage, any suggestion is welcome. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From matteo.bernardini at gmail.com Wed Dec 9 13:41:05 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 9 Dec 2015 14:41:05 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <56682120.7080004@microlinux.fr> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> Message-ID: 2015-12-09 13:40 GMT+01:00 Nicolas Kovacs : > 3. LXDM also works, except its window stubbornly displays everything > in english on a machine where LANG is set to fr_FR.utf8. It's either > untranslated, or I didn't find the special secret configuration option > in the special secret configuration file to make it work. /usr/sbin/lxdm is a shell script that uses by default some parameters fit for other distributions. I will substitute it with what is in the following block (this will go also in our repository): - - - - - - - #!/bin/sh . /etc/profile.d/lang.sh export LANG exec /usr/sbin/lxdm-binary $* - - - - - - - please check if this works for you. Matteo From info at microlinux.fr Wed Dec 9 14:12:56 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 9 Dec 2015 15:12:56 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> Message-ID: <566836E8.5040107@microlinux.fr> Le 09/12/2015 14:41, Matteo Bernardini a ?crit : > /usr/sbin/lxdm is a shell script that uses by default some parameters > fit for other distributions. > > I will substitute it with what is in the following block (this will go > also in our repository): > > - - - - - - - > #!/bin/sh > . /etc/profile.d/lang.sh > export LANG > exec /usr/sbin/lxdm-binary $* > - - - - - - - > > please check if this works for you. Matteo, you're a star! This works! And upon verification, it looks like the script was written either for Fedora, Red Hat or SUSE, what with the /etc/sysconfig stuff. There's a significant advantage to LXDM, a bug that's actually a feature. The annoying "Switch User" option is now greyed out in Xfce's logout dialog. This has always been a resource hog especially at our local school, with 80+ users leaving their session suspended. I have a couple of questions on fine-tuning LXDM's appearance. 1. Just right beneath the big white "Login" word, the "User" and "Password" prompts display in black. Is there a way to change the color, because the black on blue is not very nice. I plan on defining a different default background, so being able to change that prompt's color would be nice. 2. I switched off the language selector in the bottom panel, so the only options I have left are a) the desktop selector in the bottom left corner, with two options: Xfce vs. Default (Xfce), and b) the Shutdown/Reboot button. I don't really need the desktop selector, but the only way of getting rid of it seems to be to set bottom_pane=0 in /etc/lxdm/lxdm.conf. Unfortunately, this also wipes away the Shutdown/Reboot button. Any idea how this could eventually be fixed? Cheers & thanks very much for your help. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From matteo.bernardini at gmail.com Wed Dec 9 14:26:19 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 9 Dec 2015 15:26:19 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <566836E8.5040107@microlinux.fr> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> Message-ID: 2015-12-09 15:12 GMT+01:00 Nicolas Kovacs : > I have a couple of questions on fine-tuning LXDM's appearance. > > 1. Just right beneath the big white "Login" word, the "User" and > "Password" prompts display in black. Is there a way to change the color, > because the black on blue is not very nice. I plan on defining a > different default background, so being able to change that prompt's > color would be nice. > > 2. I switched off the language selector in the bottom panel, so the only > options I have left are a) the desktop selector in the bottom left > corner, with two options: Xfce vs. Default (Xfce), and b) the > Shutdown/Reboot button. I don't really need the desktop selector, but > the only way of getting rid of it seems to be to set bottom_pane=0 in > /etc/lxdm/lxdm.conf. Unfortunately, this also wipes away the > Shutdown/Reboot button. Any idea how this could eventually be fixed? I've never done it but I guess the best way is to define a custom theme: copy the folder /usr/share/lxdm/themes/Industrial to /usr/share/lxdm/themes/Microlinux, set is as the default theme in /etc/lxdm/lxdm.conf (where you can specify a different background image) and then edit /usr/share/lxdm/themes/Microlinux/gtkrc and /usr/share/lxdm/themes/Microlinux/greeter.ui as you prefer. I suppose (but I haven't tried that too) that cutting away the 40 lines of the section with id="sessions_box" from greeter.ui should hide it. Matteo From info at microlinux.fr Wed Dec 9 14:42:54 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 9 Dec 2015 15:42:54 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> Message-ID: <56683DEE.6020000@microlinux.fr> Le 09/12/2015 15:26, Matteo Bernardini a ?crit : > I've never done it but I guess the best way is to define a custom > theme: copy the folder /usr/share/lxdm/themes/Industrial to > /usr/share/lxdm/themes/Microlinux, set is as the default theme in > /etc/lxdm/lxdm.conf (where you can specify a different background > image) and then edit /usr/share/lxdm/themes/Microlinux/gtkrc and > /usr/share/lxdm/themes/Microlinux/greeter.ui as you prefer. OK, I found out how to switch colors. There's a gtk.css file that's only partly used, editing it doesn't yield the expected results. The relevant option is hidden in gtkrc, so replacing 000000 by ffffff at the 'prompt' text line did the trick. Well, we're very close to perfection now. Last thing would be to hide the desktop selector menu at the bottom panel. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Wed Dec 9 15:01:31 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Wed, 9 Dec 2015 16:01:31 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> Message-ID: <5668424B.3080106@microlinux.fr> Le 09/12/2015 15:26, Matteo Bernardini a ?crit : > I suppose (but I haven't tried that too) that cutting away the 40 > lines of the section with id="sessions_box" from greeter.ui > should hide it. I think I'll just leave the session selector as is, since it's not really an annoyance. One last detail that bothers me a little. Normally, after installing LXDM, the user would have to manually edit /etc/rc.d/rc.4 to add a corresponding stanza: if [ -x /usr/sbin/lxdm ]; then exec /usr/sbin/lxdm fi Since my LXDM package will be intended for MLED (where there's only one single desktop, Xfce, as well as one single login manager, LXDM), I guess a comfortable way to "integrate" the package would be to add a sed line to lxdm's doinst.sh, to replace this in rc.4: # Someone thought that gdm looked prettier in /usr/sbin, # so look there, too: if [ -x /usr/sbin/gdm ]; then exec /usr/sbin/gdm -nodaemon fi ... with the above stanza. Or do you have a better idea? -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From didier at slint.fr Wed Dec 9 15:17:44 2015 From: didier at slint.fr (Didier Spaier) Date: Wed, 9 Dec 2015 16:17:44 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <5668424B.3080106@microlinux.fr> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> <5668424B.3080106@microlinux.fr> Message-ID: <56684618.6030003@slint.fr> On 09/12/2015 16:01, Nicolas Kovacs wrote: > One last detail that bothers me a little. Normally, after installing > LXDM, the user would have to manually edit /etc/rc.d/rc.4 to add a > corresponding stanza: > > if [ -x /usr/sbin/lxdm ]; then > exec /usr/sbin/lxdm > fi > > Since my LXDM package will be intended for MLED (where there's only one > single desktop, Xfce, as well as one single login manager, LXDM), I > guess a comfortable way to "integrate" the package would be to add a sed > line to lxdm's doinst.sh, to replace this in rc.4: > > # Someone thought that gdm looked prettier in /usr/sbin, > # so look there, too: > if [ -x /usr/sbin/gdm ]; then > exec /usr/sbin/gdm -nodaemon > fi > > ... with the above stanza. > > Or do you have a better idea? Why remove anything? I would just put lxdm on top. From info at microlinux.fr Thu Dec 10 08:33:35 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 10 Dec 2015 09:33:35 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> Message-ID: <566938DF.60907@microlinux.fr> Le 09/12/2015 15:26, Matteo Bernardini a ?crit : > I've never done it but I guess the best way is to define a custom > theme: copy the folder /usr/share/lxdm/themes/Industrial to > /usr/share/lxdm/themes/Microlinux, set is as the default theme in > /etc/lxdm/lxdm.conf (where you can specify a different background > image) and then edit /usr/share/lxdm/themes/Microlinux/gtkrc and > /usr/share/lxdm/themes/Microlinux/greeter.ui as you prefer. Here's my lxdm.SlackBuild with some additional stuff, in case you want to use some of it. http://www.microlinux.fr/microlinux/desktop-14.2-source/lxdm/ Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Thu Dec 10 08:50:09 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 10 Dec 2015 09:50:09 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> Message-ID: <56693CC1.6070401@microlinux.fr> Le 09/12/2015 15:26, Matteo Bernardini a ?crit : > I suppose (but I haven't tried that too) that cutting away the 40 > lines of the section with id="sessions_box" from greeter.ui > should hide it. I played around with it, and here's a possible solution. The section you mentioned: True 6 This has to be edited simply by replacing "True" by "False": False 6 Now I have a technical question for this. The "cleanest" way to do this would be a sed one-liner replacing it. The problem is: there are many lines in the script looking like this: True So how would a sed command look like that did something like this: Replace the following line: True ... by this: False But only where the previous line is this: I'm reaching the modest limits of my scripting skills here. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Thu Dec 10 09:33:34 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 10 Dec 2015 10:33:34 +0100 Subject: [Slackbuilds-users] opencv vs. ffmpeg: not found Message-ID: <566946EE.9020403@microlinux.fr> Hi, On a machine with Slackware 14.1, I have ffmpeg 2.6.3 installed (from SBo). Now I want to rebuilt opencv (3.0.0 also from SBo) to use it, but here's what cmake spews out: -- Video I/O: -- DC1394 1.x: NO -- DC1394 2.x: YES (ver 2.2.2) -- FFMPEG: NO -- codec: NO -- format: NO -- util: NO -- swscale: NO -- resample: NO -- gentoo-style: NO Any idea what's wrong here? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From didier at slint.fr Thu Dec 10 09:36:22 2015 From: didier at slint.fr (Didier Spaier) Date: Thu, 10 Dec 2015 10:36:22 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <56693CC1.6070401@microlinux.fr> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> <56693CC1.6070401@microlinux.fr> Message-ID: <56694796.8090005@slint.fr> On 10/12/2015 09:50, Nicolas Kovacs wrote: > Le 09/12/2015 15:26, Matteo Bernardini a ?crit : >> I suppose (but I haven't tried that too) that cutting away the 40 >> lines of the section with id="sessions_box" from greeter.ui >> should hide it. > > I played around with it, and here's a possible solution. The section you > mentioned: > > > True > 6 > > > This has to be edited simply by replacing "True" by "False": > > > False > 6 > > > Now I have a technical question for this. The "cleanest" way to do this > would be a sed one-liner replacing it. The problem is: there are many > lines in the script looking like this: > > True > > So how would a sed command look like that did something like this: > > Replace the following line: > > True > > ... by this: > > False > > But only where the previous line is this: > > sed '//{N;s@True@False@}' your_file Or more readable: sed -f sed_script your_file ------------ /tmp$ cat sed_script //{ N s@True@False@ } /tmp$ ------------ From didier at slint.fr Thu Dec 10 09:40:45 2015 From: didier at slint.fr (Didier Spaier) Date: Thu, 10 Dec 2015 10:40:45 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <56694796.8090005@slint.fr> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> <56693CC1.6070401@microlinux.fr> <56694796.8090005@slint.fr> Message-ID: <5669489D.7020703@slint.fr> On 10/12/2015 10:36, Didier Spaier wrote: > sed '//{N;s@ name="visible">True@ name="visible">False@}' your_file This was a single line but Thunderbird cut it, sorry. From info at microlinux.fr Thu Dec 10 10:10:12 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 10 Dec 2015 11:10:12 +0100 Subject: [Slackbuilds-users] opencv vs. ffmpeg: not found In-Reply-To: <566946EE.9020403@microlinux.fr> References: <566946EE.9020403@microlinux.fr> Message-ID: <56694F84.9020508@microlinux.fr> Le 10/12/2015 10:33, Nicolas Kovacs a ?crit : > On a machine with Slackware 14.1, I have ffmpeg 2.6.3 installed (from > SBo). Now I want to rebuilt opencv (3.0.0 also from SBo) to use it, but > here's what cmake spews out: > > -- Video I/O: > -- DC1394 1.x: NO > -- DC1394 2.x: YES (ver 2.2.2) > -- FFMPEG: NO > -- codec: NO > -- format: NO > -- util: NO > -- swscale: NO > -- resample: NO > -- gentoo-style: NO > > Any idea what's wrong here? After pulling out my hair for half an hour, I just found out the culprit. Curiously enough, on this machine, I had built ffmpeg 2.6.3 successfully, but then uninstalled it for some reason. Duh! Problem solved. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From info at microlinux.fr Thu Dec 10 10:51:25 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Thu, 10 Dec 2015 11:51:25 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <5669489D.7020703@slint.fr> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> <56693CC1.6070401@microlinux.fr> <56694796.8090005@slint.fr> <5669489D.7020703@slint.fr> Message-ID: <5669592D.9020906@microlinux.fr> Le 10/12/2015 10:40, Didier Spaier a ?crit : > This was a single line but Thunderbird cut it, sorry. Thanks for the script, Didier! Is there a way to cut this line, like you would do with \ in a shell script ? Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From didier at slint.fr Thu Dec 10 11:09:24 2015 From: didier at slint.fr (Didier Spaier) Date: Thu, 10 Dec 2015 12:09:24 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <5669592D.9020906@microlinux.fr> References: <566809DC.9030807@microlinux.fr> <566819F8.7030500@slackbuilds.org> <56682120.7080004@microlinux.fr> <566836E8.5040107@microlinux.fr> <56693CC1.6070401@microlinux.fr> <56694796.8090005@slint.fr> <5669489D.7020703@slint.fr> <5669592D.9020906@microlinux.fr> Message-ID: <56695D64.4010905@slint.fr> On 10/12/2015 11:51, Nicolas Kovacs wrote: > Thanks for the script, Didier! Is there a way to cut this line, like you > would do with \ in a shell script ? No. In sed \ is only used after i (insert) or a (append) commands, cf: http://pubs.opengroup.org/onlinepubs/9699919799/utilities/sed.html to know more. One liners are nice but hard to read, that's why I prefer to to use the -f option and provide a sed script like the one attached. Additionally this way you do not need shell escaping. Here is bigger example (shell script with embedded sed scripts): http://slint.fr/misc/convtags/convtags I do not attach it because it weighs 66K Cheers, Didier -------------- next part -------------- //{ N s@True@False@ } From thedoogster at gmail.com Fri Dec 11 17:47:30 2015 From: thedoogster at gmail.com (Doogster) Date: Fri, 11 Dec 2015 09:47:30 -0800 Subject: [Slackbuilds-users] Orphaning oss and vbam Message-ID: Hi. I'd like to announce that I'm orphaning the oss and vbam SlackBuilds I don't use oss because I like to use USB sound cards (which oss does not support). I don't use vbam because there are better alternatives available (RetroArch with the mGBA core, or mGBA standalone). -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Fri Dec 11 19:58:14 2015 From: yalhcru at gmail.com (B Watson) Date: Fri, 11 Dec 2015 14:58:14 -0500 Subject: [Slackbuilds-users] Orphaning oss and vbam In-Reply-To: References: Message-ID: On 12/11/15, Doogster wrote: > Hi. I'd like to announce that I'm orphaning the oss and vbam SlackBuilds If nobody else wants these, I'll take them. From yalhcru at gmail.com Fri Dec 11 20:00:30 2015 From: yalhcru at gmail.com (B Watson) Date: Fri, 11 Dec 2015 15:00:30 -0500 Subject: [Slackbuilds-users] Fwd: flpsed on slackbuilds.org In-Reply-To: References: Message-ID: Sent this out 3 days ago, no response, forwarding to the list in case the maintainer is monitoring it. ---------- Forwarded message ---------- From: B Watson Date: Tue, 8 Dec 2015 15:57:04 -0500 Subject: flpsed on slackbuilds.org To: jack at auburn.edu There have been quite a few releases of flpsed since the build was last update... currently, latest version is 0.7.3. Any chance you can update your script? From fernando.lopezjr at gmail.com Fri Dec 11 21:53:29 2015 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Fri, 11 Dec 2015 14:53:29 -0700 Subject: [Slackbuilds-users] KiCad 4 is out. In-Reply-To: References: Message-ID: I have submitted a new package on kicad also, wxWidgets. On Wed, Dec 2, 2015 at 1:35 PM, Fernando Lopez wrote: > okay. i'll take it. > > On Wed, Dec 2, 2015 at 1:19 PM, Ryan P.C. McQuen wrote: > >> >> >> On Wed, Dec 2, 2015 at 12:10 PM Fernando Lopez < >> fernando.lopezjr at gmail.com> wrote: >> >>> Just to let you know that kicad 4 is out... =) >>> >>> kicad-pcb.org/post/release-4.0.0/ >>> >> >> Probably a good idea to CC the maintainer on emails like this (not all of >> them are subscribed to this mailing list). >> >> In this case, Niels Horn gave up all his builds, so you could probably >> take this one if someone else hasn't already claimed it. >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > > > -- > > ------------ > Regards, > Fernando Lopez Jr. > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 12 00:07:56 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Dec 2015 07:07:56 +0700 Subject: [Slackbuilds-users] KiCad 4 is out. In-Reply-To: References: Message-ID: <566B655C.9030501@slackbuilds.org> > I have submitted a new package on kicad also, wxWidgets. No, you didn't send it via submission form :) -- 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 Dec 12 00:35:19 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Dec 2015 07:35:19 +0700 Subject: [Slackbuilds-users] Updates - 20151212.1 Message-ID: <566B6BC7.40901@slackbuilds.org> Sat Dec 12 00:21:30 UTC 2015 academic/fet: Updated for version 5.28.3. academic/sundials: Updated for version 2.6.2. audio/kradio: Updated for version 4.0.8. desktop/jwm: Updated for version 2.3.4. desktop/tint2: Updated for version 0.12.3. desktop/wmxss: Added (XScreenSaver DockApp). development/android-studio: Updated for version 1.5.1_141_2456560. development/atom: Updated for version 1.3.0. development/guile-json: Added (JSON module for Guile). development/hhvm: Updated for version 3.11.0. development/kaaedit: Updated for version 0.47.0. development/monodevelop-database: Updated for version 5.10.1.1. development/monodevelop: Updated for version 5.10.1.1. development/neovim: Updated for version 0.1.1. development/p4: Updated for version 2015.2.1311674. development/sbcl: Updated for version 1.3.1. development/universal-ctags: Updated for version 8efa556. games/SLADE: Updated for version 3.1.0.5. games/atari++: Updated for version 1.80. games/chocolate_duke3D: Update script. games/crispy-doom: Added (Doom source port). games/jackhammer: Added (Jackhammer Level Editor). games/mednafen: Only set CLANGFLAGS on affected version of clang. games/ut2004: Added (Unreal Tournament 2004). games/warsow: Hardcoded x86 ARCH to i686 games/wmquake: Update script. games/zod-engine: Fix version in .info file. graphics/GraphicsMagick: Fix compile issue. graphics/Shellpic: Updated for version 1.6.2. graphics/advancecomp: Updated for version 1.20. graphics/findimagedupes: Add perl-Inline-C to REQUIRES. graphics/graphite2: Added (rendering engine). graphics/phototonic: Updated for version 1.7. libraries/CoinMP: Added (C-API library). libraries/botocore: Updated for version 1.3.11. libraries/dropbox-python: Updated for version 4.0. libraries/htmlcxx: Updated for version 0.86. libraries/hyphen: Added (hyphenation library). libraries/libabw: Added (AbiWord Import Library). libraries/libcdr: Added (CorelDRAW Import Library). libraries/libcmis: Added (C++ client library). libraries/libe-book: Added (reflowable e-book import library). libraries/libetonyek: Added (Apple Keynote Import Library). libraries/libexttextcat: Added (Text Categorization library). libraries/libfreehand: Added (Adobe FreeHand Import Library). libraries/libgltf: Added (rendering library for glTF models). libraries/libhtp: Updated for version 0.5.18. libraries/libixion: Added (formula parser & interpreter). libraries/librevenge: Added (REVerse ENGineered formats filters). libraries/mdds: Added (Multi-Dimensional Data Structure). libraries/yaml-cpp0.3: Update download URL and homepage. multimedia/beets: Updated for version 1.3.15. multimedia/flashplayer-plugin: Updated for version 11.2.202.554. multimedia/gpodder: Updated for version 3.8.5. multimedia/lives: Updated for version 2.4.5. multimedia/mpv: Fix .info. multimedia/obs-studio: Updated for version 0.12.3. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 47.0.x. network/CherryMusic: Updated for version 0.36.0. network/aldryn-client: Updated for version 2.0.4. network/awscli: Updated for version 1.9.11. network/broadcom-sta: Remove doinst.sh. network/telegram: Updated for version 0.9.15. network/tixati: Updated for version 2.28_1. network/vivaldi: Updated for version 1.0.340.7_1. network/you-get: Updated for version 0.4.192. network/youtube-dl: Updated for version 2015.12.06. office/CherryTree: Updated for version 0.36.1. office/LanguageTool: Updated for version 3.1. office/MasterPDFEditor: Updated for version 3.5.10. office/tellico: Updated for version 2.3.11. office/texlive: Fix .info. perl/perl-Sidef: Updated for version 2.12. perl/perl-file-desktopentry: Updated for version 0.22. python/PyGithub: Updated for version 1.26.0. python/pytest: Updated for version 2.8.4. python/python-pillow: Update README. python/python-swiftclient: Updated for version 2.7.0. python/stevedore: Updated for version 1.10.0. python/tox: Updated for version 2.3.0. system/Iosevka: Updated for version 1.2.0. system/forkstat: Updated for version 0.01.13. system/glances: Update README. system/guix: Update README and Fix UID/GID. system/innoextract: Updated for version 1.5. system/letsencrypt: Added (Manage X.509 certificates). system/lxdm: Fix localization detection. system/mongo-tools: Updated for version 3.2.0. system/mongodb: Updated for version 3.2.0. system/ofono: Use bluez4. system/patool: Updated for version 1.9. system/pcsc-tools: Updated for version 1.4.25. system/slpkg: Updated for version 3.0.3. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rworkman at slackbuilds.org Sat Dec 12 03:05:42 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 11 Dec 2015 21:05:42 -0600 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <566809DC.9030807@microlinux.fr> References: <566809DC.9030807@microlinux.fr> Message-ID: <20151211210542.214b35a2@home.rlworkman.net> On Wed, 9 Dec 2015 12:00:44 +0100 Nicolas Kovacs wrote: > Hi, > > The issue has already been raised on LQ, but I think this is a better > place to discuss it. Here's the context. > > Just installed a stock Slackware64 -current on a box, full > installation without KDE. > > Then I built libgnomecanvas and gdm from SlackBuilds.org. Switched to > init4 to fire up GDM, logged in to Xfce, and here's what I get: > > $ ck-list-sessions > Session1: > unix-user = '0' > realname = '(null)' > seat = 'Seat1' > session-type = '' > active = TRUE > x11-display = ':0' > x11-display-device = '/dev/tty7' > display-device = '' > remote-host-name = '' > is-local = TRUE > on-since = '2015-12-09T10:48:45.985157Z' > login-session-id = '4294967295' > > When I remove GDM and use XDM instead, I'm getting this, as expected: > > $ ck-list-sessions > Session2: > unix-user = '1000' > realname = 'Niki Kovacs' > seat = 'Seat1' > session-type = '' > active = TRUE > x11-display = ':0' > x11-display-device = '/dev/tty7' > display-device = '' > remote-host-name = '' > is-local = TRUE > on-since = '2015-12-09T10:54:56.858488Z' > login-session-id = '4294967295' > > > I've googled around a bit, but to no avail. If anyone has a remote > idea of how to make GDM behave under Slackware -current, I'd be > grateful. I looked around in the gdm code and don't see anything obvious that would make it not work with CK2, and like you, google turned up nothing useful. I did notice that PCLinuxOS is using gdm-2.20.11 as well, but aside from a special dbus config file (which I tried here with no change to behavior), I don't see anything special that they do. I'll note that they use PAM though, so maybe that makes a difference. These days, I don't even use gdm any more - I'm on xdm with alienBOB's config (slightly modified) from his livecd work. The only things that users might miss are a session chooser (change $HOME.xinitrc instead) and switching users (I don't like that anyway, and you indicated the same, so good riddance to that one, right? :)) If someone wants to poke around at it and fix it, great; otherwise, gdm will dropped for 14.2. -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 rworkman at slackbuilds.org Sat Dec 12 04:00:46 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 11 Dec 2015 22:00:46 -0600 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <20151211210542.214b35a2@home.rlworkman.net> References: <566809DC.9030807@microlinux.fr> <20151211210542.214b35a2@home.rlworkman.net> Message-ID: <20151211220046.4c4bcc5a@home.rlworkman.net> On Fri, 11 Dec 2015 21:05:42 -0600 Robby Workman wrote: > and like you, google turned up nothing useful. Er, NO. Not what I meant to say there. In my head, it was "like you said, google turned up nothing useful" but something got lost between my brain and my fingers. -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 Jim.Diamond at acadiau.ca Sat Dec 12 14:42:49 2015 From: Jim.Diamond at acadiau.ca (Jim Diamond) Date: Sat, 12 Dec 2015 10:42:49 -0400 Subject: [Slackbuilds-users] sbotools 1.9 vs shutter Message-ID: <20151212144249.GA30587@jdiamond-nb2> sbocheck told me there was a new sbotools, so I upgraded to 1.9. sboupgrade sbotools Then I was rewarded with this: sbocheck Updating SlackBuilds tree... Finished. Checking for updated SlackBuilds... A fatal script error has occurred: error when parsing shutter.info file. Line: perl-net-dbus perl-Proc-ProcessTable perl-www-mechanize perl-x11-protocol Exiting. Anyone else having similar issues? Jim From willysr at slackbuilds.org Sat Dec 12 16:15:24 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 12 Dec 2015 23:15:24 +0700 Subject: [Slackbuilds-users] sbotools 1.9 vs shutter In-Reply-To: <20151212144249.GA30587@jdiamond-nb2> References: <20151212144249.GA30587@jdiamond-nb2> Message-ID: <566C481C.40700@slackbuilds.org> > sbocheck told me there was a new sbotools, so I upgraded to 1.9. > sboupgrade sbotools > Then I was rewarded with this: > sbocheck > Updating SlackBuilds tree... > Finished. > Checking for updated SlackBuilds... > A fatal script error has occurred: > error when parsing shutter.info file. Line: perl-net-dbus perl-Proc-ProcessTable perl-www-mechanize perl-x11-protocol > Exiting. > > Anyone else having similar issues? Fixed 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 brent at exitstatusone.com Sat Dec 12 19:16:41 2015 From: brent at exitstatusone.com (Brenton Earl) Date: Sat, 12 Dec 2015 12:16:41 -0700 Subject: [Slackbuilds-users] Testing mitmproxy SlackBuild Message-ID: <566C7299.9010002@exitstatusone.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hello fellow Slackers, I am in the process of testing mitmproxy and a number of its dependencies. There are a lot of moving parts. If anyone would like to assist in testing, it would be much appreciated. Relevant information can be found here: http://goo.gl/yibSB2 Thanks for your time, - -- Brenton Earl -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWbHKZAAoJEMAWbOXyIOfzzfYIAKrVUzyvkMcFVz2Mlj33fatM lLfOrqOV/tDK3LPwhJ7I119twyOnnrZHGMpRKN8Zd1vZx1M3BedQ4l+cHgIrLSyJ L46j5QkKhurO3WgXWIQ0lfdWx925IWRIK6BQFRP4ObTmKNhgxEn7Tifnx+k1civP pte8Pr5EzlqaoFHYl6idITpvvamxKqbAU9RlhLkxkplI9VXo6qHjrFCP8F6nloRW nC7v91wSbquWsq1n+p7tGdV0m52Tt08wQgBUZjqsmxsBTP1m0GJ1oAjT2j9qYfQ/ +1nJ8uaJC2P4LDMrutgDd4ECCFLqurRptwE5mhHOvWX7u+beVaSoY+ME9L+PT8Y= =MLdI -----END PGP SIGNATURE----- From info at microlinux.fr Sun Dec 13 18:43:36 2015 From: info at microlinux.fr (Nicolas Kovacs) Date: Sun, 13 Dec 2015 19:43:36 +0100 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <20151211210542.214b35a2@home.rlworkman.net> References: <566809DC.9030807@microlinux.fr> <20151211210542.214b35a2@home.rlworkman.net> Message-ID: <566DBC58.7040001@microlinux.fr> Le 12/12/2015 04:05, Robby Workman a ?crit : > I looked around in the gdm code and don't see anything obvious > that would make it not work with CK2, and like you, google turned > up nothing useful. I did notice that PCLinuxOS is using gdm-2.20.11 > as well, but aside from a special dbus config file (which I tried > here with no change to behavior), I don't see anything special that > they do. I'll note that they use PAM though, so maybe that makes a > difference. > > These days, I don't even use gdm any more - I'm on xdm with > alienBOB's config (slightly modified) from his livecd work. The > only things that users might miss are a session chooser (change > $HOME.xinitrc instead) and switching users (I don't like that > anyway, and you indicated the same, so good riddance to that one, > right? :)) I spent a rainy afternoon fiddling around with LXDM. Now I'm a happy camper with it, it works perfectly, looks very nice and doesn't depend on any other third-party stuff. Here's my modified version that works great with Xfce or any other window manager (WindowMaker, Fluxbox, IceWM, etc.) http://www.microlinux.fr/microlinux/testing-14.1-source/lxdm/ Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From slackph at posteo.de Sun Dec 13 19:23:57 2015 From: slackph at posteo.de (Philip Lacroix) Date: Sun, 13 Dec 2015 20:23:57 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= Message-ID: <2639962ad9bc82e442ba553324bd3f67@posteo.de> Greetings I wonder if something like the following test could be added to python-pillow.SlackBuild, in order to automatically add support for Python3 if the latter is installed: > python setup.py install --root=$PKG > > + if $(python3 -c 'import sys' 2>/dev/null); then > + python3 setup.py install --root=$PKG > + fi I've been using this test in my script for glances, after borrowing it from Larry Hajali's script for psutil, and it seems to do its job nicely. The reason for my suggestion is that I'm preparing a new SlackBuild that will require both python3 and python-pillow. The software expects pillow to support Python 3, but it doesn't, unless the script is manually edited. I understand that Slackware-current, from which the python-pillow script was taken, doesn't include Python 3, however SBo does, so it would be nice to have it autodetected. :) Best regards Philip From larryhaja at gmail.com Sun Dec 13 19:54:26 2015 From: larryhaja at gmail.com (Larry Hajali) Date: Sun, 13 Dec 2015 11:54:26 -0800 Subject: [Slackbuilds-users] Support for Python 3 in python-pillow? In-Reply-To: <2639962ad9bc82e442ba553324bd3f67@posteo.de> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> Message-ID: I've been on the fence about adding that auto-detection in my python slackbuilds. Some people think that this should be an option set at build time to add python3 support by using a variable. Eg. if ["${PYTHON3SUPPORT:-no}" == "yes" ]; then python3 setup.py install --root=$PKG fi I'm not opposed to that, but I'm also not sure how to handle packages that put files in /usr/bin directory (like python-pillow) for python2 and python3 scripts. If python3 files are built after python2 files, then everything in /usr/bin/* will have a shebang with #!/usr/bin/python3. I'm not sure that is a desired outcome. It may be best to create a second python3 package for python-pillow and possibly other python slackbuilds that support python3 to avoid file conflicts. Thanks, --Larry On Sun, Dec 13, 2015 at 11:23 AM, Philip Lacroix wrote: > Greetings > > I wonder if something like the following test could be added to > python-pillow.SlackBuild, in order to automatically add support for Python3 > if the latter is installed: > > python setup.py install --root=$PKG >> >> + if $(python3 -c 'import sys' 2>/dev/null); then >> + python3 setup.py install --root=$PKG >> + fi >> > > I've been using this test in my script for glances, after borrowing it > from Larry Hajali's script for psutil, and it seems to do its job nicely. > > The reason for my suggestion is that I'm preparing a new SlackBuild that > will require both python3 and python-pillow. The software expects pillow to > support Python 3, but it doesn't, unless the script is manually edited. I > understand that Slackware-current, from which the python-pillow script was > taken, doesn't include Python 3, however SBo does, so it would be nice to > have it autodetected. :) > > Best regards > Philip > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackph at posteo.de Sun Dec 13 20:23:18 2015 From: slackph at posteo.de (Philip Lacroix) Date: Sun, 13 Dec 2015 21:23:18 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> Message-ID: Hi Larry > It may be best to create a second python3 package for python-pillow and > possibly other python slackbuilds that support python3 to avoid file > conflicts. This makes sense. If having separate packages is a safer option I may take care of that and submit python3-pillow, unless Brenton Earl prefers to do that (as he already maintains python-pillow). I'll wait a few days for his feedback. Thank you Philip Am 13.12.2015 20:54 schrieb Larry Hajali: > I've been on the fence about adding that auto-detection in my python > slackbuilds. Some people think that this should be an option set at > build > time to add python3 support by using a variable. > > Eg. > > if ["${PYTHON3SUPPORT:-no}" == "yes" ]; then > > python3 setup.py install --root=$PKG > > fi > > > I'm not opposed to that, but I'm also not sure how to handle packages > that > put files in /usr/bin directory (like python-pillow) for python2 and > python3 scripts. If python3 files are built after python2 files, then > everything in /usr/bin/* will have a shebang with #!/usr/bin/python3. > I'm > not sure that is a desired outcome. > > It may be best to create a second python3 package for python-pillow and > possibly other python slackbuilds that support python3 to avoid file > conflicts. > > Thanks, > --Larry > > On Sun, Dec 13, 2015 at 11:23 AM, Philip Lacroix > wrote: > >> Greetings >> >> I wonder if something like the following test could be added to >> python-pillow.SlackBuild, in order to automatically add support for >> Python3 >> if the latter is installed: >> >> python setup.py install --root=$PKG >>> >>> + if $(python3 -c 'import sys' 2>/dev/null); then >>> + python3 setup.py install --root=$PKG >>> + fi >>> >> >> I've been using this test in my script for glances, after borrowing it >> from Larry Hajali's script for psutil, and it seems to do its job >> nicely. >> >> The reason for my suggestion is that I'm preparing a new SlackBuild >> that >> will require both python3 and python-pillow. The software expects >> pillow to >> support Python 3, but it doesn't, unless the script is manually >> edited. I >> understand that Slackware-current, from which the python-pillow script >> was >> taken, doesn't include Python 3, however SBo does, so it would be nice >> to >> have it autodetected. :) >> >> Best regards >> Philip >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ From klaatu at straightedgelinux.com Mon Dec 14 06:40:03 2015 From: klaatu at straightedgelinux.com (Klaatu) Date: Mon, 14 Dec 2015 19:40:03 +1300 Subject: [Slackbuilds-users] GDM vs. ConsoleKit in -current In-Reply-To: <566DBC58.7040001@microlinux.fr> References: <566809DC.9030807@microlinux.fr> <20151211210542.214b35a2@home.rlworkman.net> <566DBC58.7040001@microlinux.fr> Message-ID: <566E6443.9090104@straightedgelinux.com> On 12/14/2015 07:43 AM, Nicolas Kovacs wrote: > Le 12/12/2015 04:05, Robby Workman a ?crit : >> I looked around in the gdm code and don't see anything obvious >> that would make it not work with CK2, and like you, google turned >> up nothing useful. I did notice that PCLinuxOS is using gdm-2.20.11 >> as well, but aside from a special dbus config file (which I tried >> here with no change to behavior), I don't see anything special that >> they do. I'll note that they use PAM though, so maybe that makes a >> difference. >> >> These days, I don't even use gdm any more - I'm on xdm with >> alienBOB's config (slightly modified) from his livecd work. The >> only things that users might miss are a session chooser (change >> $HOME.xinitrc instead) and switching users (I don't like that >> anyway, and you indicated the same, so good riddance to that one, >> right? :)) > > I spent a rainy afternoon fiddling around with LXDM. Now I'm a happy > camper with it, it works perfectly, looks very nice and doesn't depend > on any other third-party stuff. > > Here's my modified version that works great with Xfce or any other > window manager (WindowMaker, Fluxbox, IceWM, etc.) > > http://www.microlinux.fr/microlinux/testing-14.1-source/lxdm/ > > Cheers, > > Niki > Bravo! thanks Niki, this is really nice. Think I might borrow it for myself. -klaatu From slackph at posteo.de Mon Dec 14 09:56:14 2015 From: slackph at posteo.de (Philip Lacroix) Date: Mon, 14 Dec 2015 10:56:14 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> Message-ID: <7b14c8be7a396cdb2625134cf7861a00@posteo.de> Am 13.12.2015 20:54 schrieb Larry Hajali: > I've been on the fence about adding that auto-detection in my python > slackbuilds. Some people think that this should be an option set at > build > time to add python3 support by using a variable. > > Eg. > > if ["${PYTHON3SUPPORT:-no}" == "yes" ]; then > > python3 setup.py install --root=$PKG > > fi > > I'm not opposed to that, but I'm also not sure how to handle packages > that > put files in /usr/bin directory (like python-pillow) for python2 and > python3 scripts. If python3 files are built after python2 files, then > everything in /usr/bin/* will have a shebang with #!/usr/bin/python3. > I'm > not sure that is a desired outcome. > > It may be best to create a second python3 package for python-pillow and > possibly other python slackbuilds that support python3 to avoid file > conflicts. Perhaps we could also avoid duplicating packages where such conflicts are possible, by adding an "else" statement in order to build either with Python OR Python3 support. For example: if ["${PYTHON3SUPPORT:-no}" == "yes" ]; then python3 setup.py install --root=$PKG else python setup.py install --root=$PKG fi Philip > Thanks, > --Larry > > On Sun, Dec 13, 2015 at 11:23 AM, Philip Lacroix > wrote: > >> Greetings >> >> I wonder if something like the following test could be added to >> python-pillow.SlackBuild, in order to automatically add support for >> Python3 >> if the latter is installed: >> >> python setup.py install --root=$PKG >>> >>> + if $(python3 -c 'import sys' 2>/dev/null); then >>> + python3 setup.py install --root=$PKG >>> + fi >>> >> >> I've been using this test in my script for glances, after borrowing it >> from Larry Hajali's script for psutil, and it seems to do its job >> nicely. >> >> The reason for my suggestion is that I'm preparing a new SlackBuild >> that >> will require both python3 and python-pillow. The software expects >> pillow to >> support Python 3, but it doesn't, unless the script is manually >> edited. I >> understand that Slackware-current, from which the python-pillow script >> was >> taken, doesn't include Python 3, however SBo does, so it would be nice >> to >> have it autodetected. :) >> >> Best regards >> Philip From brent at exitstatusone.com Mon Dec 14 20:37:54 2015 From: brent at exitstatusone.com (Brent Earl) Date: Mon, 14 Dec 2015 13:37:54 -0700 Subject: [Slackbuilds-users] Support for Python 3 in python-pillow? In-Reply-To: <7b14c8be7a396cdb2625134cf7861a00@posteo.de> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> Message-ID: I think that package duplication is unnecessary. An if else statment in the SlackBuild would be the solution I think. Where I live there is a large snow storm that knocked out my internet connection. It may not be until tomorrow or the next day that I can test this. All I have for now is a 1GB data plan on 4G. On Dec 14, 2015 2:56 AM, "Philip Lacroix" wrote: > Am 13.12.2015 20:54 schrieb Larry Hajali: > >> I've been on the fence about adding that auto-detection in my python >> slackbuilds. Some people think that this should be an option set at build >> time to add python3 support by using a variable. >> >> Eg. >> >> if ["${PYTHON3SUPPORT:-no}" == "yes" ]; then >> >> python3 setup.py install --root=$PKG >> >> fi >> >> I'm not opposed to that, but I'm also not sure how to handle packages that >> put files in /usr/bin directory (like python-pillow) for python2 and >> python3 scripts. If python3 files are built after python2 files, then >> everything in /usr/bin/* will have a shebang with #!/usr/bin/python3. I'm >> not sure that is a desired outcome. >> >> It may be best to create a second python3 package for python-pillow and >> possibly other python slackbuilds that support python3 to avoid file >> conflicts. >> > > Perhaps we could also avoid duplicating packages where such conflicts are > possible, by adding an "else" statement in order to build either with > Python OR Python3 support. For example: > > if ["${PYTHON3SUPPORT:-no}" == "yes" ]; then > python3 setup.py install --root=$PKG > else > python setup.py install --root=$PKG > fi > > Philip > > > Thanks, >> --Larry >> >> On Sun, Dec 13, 2015 at 11:23 AM, Philip Lacroix >> wrote: >> >> Greetings >>> >>> I wonder if something like the following test could be added to >>> python-pillow.SlackBuild, in order to automatically add support for >>> Python3 >>> if the latter is installed: >>> >>> python setup.py install --root=$PKG >>> >>>> >>>> + if $(python3 -c 'import sys' 2>/dev/null); then >>>> + python3 setup.py install --root=$PKG >>>> + fi >>>> >>>> >>> I've been using this test in my script for glances, after borrowing it >>> from Larry Hajali's script for psutil, and it seems to do its job nicely. >>> >>> The reason for my suggestion is that I'm preparing a new SlackBuild that >>> will require both python3 and python-pillow. The software expects pillow >>> to >>> support Python 3, but it doesn't, unless the script is manually edited. I >>> understand that Slackware-current, from which the python-pillow script >>> was >>> taken, doesn't include Python 3, however SBo does, so it would be nice to >>> have it autodetected. :) >>> >>> Best regards >>> Philip >>> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackph at posteo.de Mon Dec 14 22:11:39 2015 From: slackph at posteo.de (Philip Lacroix) Date: Mon, 14 Dec 2015 23:11:39 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> Message-ID: <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> Am 14.12.2015 21:37 schrieb Brent Earl: > I think that package duplication is unnecessary. An if else statment > in > the SlackBuild would be the solution I think. Where I live there is a > large snow storm that knocked out my internet connection. It may not > be > until tomorrow or the next day that I can test this. All I have for > now is > a 1GB data plan on 4G. Thanks. I'll either edit my package's README according to your solution and add "%README%" to REQUIRES. Cheers Philip From yalhcru at gmail.com Mon Dec 14 22:19:46 2015 From: yalhcru at gmail.com (B Watson) Date: Mon, 14 Dec 2015 17:19:46 -0500 Subject: [Slackbuilds-users] Support for Python 3 in python-pillow? In-Reply-To: <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> Message-ID: On 12/14/15, Philip Lacroix wrote: > Am 14.12.2015 21:37 schrieb Brent Earl: >> I think that package duplication is unnecessary. An if else statment >> in the SlackBuild would be the solution I think. > Thanks. > > I'll either edit my package's README according to your solution and add > "%README%" to REQUIRES. What happens if someone needs both python 2 and 3 support? Does the python3 stuff actually conflict with the python2 stuff? If not, maybe it'd be good to allow building both instead of choosing only one or the other. From slackph at posteo.de Mon Dec 14 22:40:09 2015 From: slackph at posteo.de (Philip Lacroix) Date: Mon, 14 Dec 2015 23:40:09 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> Message-ID: <120b93e8001419f352bd65840f6a5adc@posteo.de> Am 14.12.2015 23:19 schrieb B Watson: > On 12/14/15, Philip Lacroix wrote: >> Am 14.12.2015 21:37 schrieb Brent Earl: > >>> I think that package duplication is unnecessary. An if else >>> statment >>> in the SlackBuild would be the solution I think. > >> Thanks. >> >> I'll either edit my package's README according to your solution and >> add >> "%README%" to REQUIRES. > > What happens if someone needs both python 2 and 3 support? > > Does the python3 stuff actually conflict with the python2 stuff? If > not, > maybe it'd be good to allow building both instead of choosing only one > or the other. This is what some of us have been doing, but as Larry suggested: > (...) I'm also not sure how to handle packages that > put files in /usr/bin directory (like python-pillow) for python2 and > python3 scripts. If python3 files are built after python2 files, then > everything in /usr/bin/* will have a shebang with #!/usr/bin/python3. > I'm > not sure that is a desired outcome. This is the case for example with python-pillow, which has 13 files in /usr/bin. From slackph at posteo.de Tue Dec 15 12:57:53 2015 From: slackph at posteo.de (Philip Lacroix) Date: Tue, 15 Dec 2015 13:57:53 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> Message-ID: <1f18047ee924344333c82a63c6c749d7@posteo.de> Am 14.12.2015 23:19 schrieb B Watson: > What happens if someone needs both python 2 and 3 support? > > Does the python3 stuff actually conflict with the python2 stuff? If > not, > maybe it'd be good to allow building both instead of choosing only one > or the other. Something like the following example would allow the user to choose: Python 2 only (default), Python 3 only, and if both, in which order. ##### B1="2"; B2="" if [ "${PYTHON3SUPPORT:-no}" == "yes" ]; then case "$BUILD_FIRST" in 2) B1="2"; B2="3" ;; 3) B1="3"; B2="2" ;; *) B1="3"; B2="" ;; esac fi python$B1 setup.py install --root=$PKG if [[ -n $B2 ]]; then python$B2 setup.py install --root=$PKG fi ##### Cheers Philip From slackph at posteo.de Tue Dec 15 13:12:40 2015 From: slackph at posteo.de (Philip Lacroix) Date: Tue, 15 Dec 2015 14:12:40 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> Message-ID: <825f4750e4d813a1e43976f1840a30e4@posteo.de> Am 14.12.2015 23:19 schrieb B Watson: > What happens if someone needs both python 2 and 3 support? > > Does the python3 stuff actually conflict with the python2 stuff? If > not, > maybe it'd be good to allow building both instead of choosing only one > or the other. Removed redundant assignments in the case construct: ##### B1="2"; B2="" if [ "${PYTHON3SUPPORT:-no}" == "yes" ]; then case "$BUILD_FIRST" in 2) B2="3" ;; 3) B1="3"; B2="2" ;; *) B1="3" ;; esac fi python$B1 setup.py install --root=$PKG if [[ -n $B2 ]]; then python$B2 setup.py install --root=$PKG fi ##### From baildon.research at googlemail.com Tue Dec 15 14:53:27 2015 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 15 Dec 2015 14:53:27 +0000 Subject: [Slackbuilds-users] Support for Python 3 in python-pillow? In-Reply-To: <825f4750e4d813a1e43976f1840a30e4@posteo.de> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> <825f4750e4d813a1e43976f1840a30e4@posteo.de> Message-ID: Hi, sorry to have been late catching up with this thread, I think a single SlackBuild that auto-detects python3 is a horrible idea for python-pillow. It would cause an instant regression the moment that someone with python3 upgrades python-pillow-SBo to the python2-only python-pillow in -current or 14.2. A separate python3-pillow would "just work" now, and would still "just work" after 14.2 is released, unless Patrick is suddenly going to move 14.2 to python3 and change his python-pillow. -D. On 15 December 2015 at 13:12, Philip Lacroix wrote: > Am 14.12.2015 23:19 schrieb B Watson: >> >> What happens if someone needs both python 2 and 3 support? >> >> Does the python3 stuff actually conflict with the python2 stuff? If not, >> maybe it'd be good to allow building both instead of choosing only one >> or the other. > > > Removed redundant assignments in the case construct: > > ##### > B1="2"; B2="" > > if [ "${PYTHON3SUPPORT:-no}" == "yes" ]; then > case "$BUILD_FIRST" in > 2) B2="3" ;; > 3) B1="3"; B2="2" ;; > *) B1="3" ;; > esac > fi > > python$B1 setup.py install --root=$PKG > if [[ -n $B2 ]]; then > python$B2 setup.py install --root=$PKG > fi > ##### > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From brent at exitstatusone.com Tue Dec 15 16:00:19 2015 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 15 Dec 2015 09:00:19 -0700 Subject: [Slackbuilds-users] Support for Python 3 in python-pillow? In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> <825f4750e4d813a1e43976f1840a30e4@posteo.de> Message-ID: <56703913.8040804@exitstatusone.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I did not intend on adding python 3 support to my python-pillow SlackBuild. This SlackBuild is a dependency of my mitmproxy SlackBuild. Another dependency that needs to be updated is urwid, which exists in Slackware. I am not able to submit mitmproxy due to urwid being too outdated in 14.1. I cannot test in -current either because I need version urwid 1.3.1 and only 1.3.0 is available. None of this requires python 3. I discussed with one of the SBo admins that prior to creating my python-pillow SlackBuild that it would be removed once 14.2 was released. I would not recommend relying on my python-pillow package for this reason. Anyway, it exists -current and will be apart of Slackware in the future. So track the version in -current rather than mine. If you really need python 3 support for Pillow, then you should create a separate python3-pillow SlackBuild. On 12/15/2015 07:53 AM, David Spencer wrote: > Hi, sorry to have been late catching up with this thread, > > I think a single SlackBuild that auto-detects python3 is a > horrible idea for python-pillow. It would cause an instant > regression the moment that someone with python3 upgrades > python-pillow-SBo to the python2-only python-pillow in -current or > 14.2. A separate python3-pillow would "just work" now, and would > still "just work" after 14.2 is released, unless Patrick is > suddenly going to move 14.2 to python3 and change his > python-pillow. > > -D. > > On 15 December 2015 at 13:12, Philip Lacroix > wrote: >> Am 14.12.2015 23:19 schrieb B Watson: >>> >>> What happens if someone needs both python 2 and 3 support? >>> >>> Does the python3 stuff actually conflict with the python2 >>> stuff? If not, maybe it'd be good to allow building both >>> instead of choosing only one or the other. >> >> >> Removed redundant assignments in the case construct: >> >> ##### B1="2"; B2="" >> >> if [ "${PYTHON3SUPPORT:-no}" == "yes" ]; then case "$BUILD_FIRST" >> in 2) B2="3" ;; 3) B1="3"; B2="2" ;; *) B1="3" ;; esac fi >> >> python$B1 setup.py install --root=$PKG if [[ -n $B2 ]]; then >> python$B2 setup.py install --root=$PKG fi ##### >> - -- Brenton Earl -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWcDkTAAoJEMAWbOXyIOfzUJ0IAIu1VCu4Fe1O5YycGM/dSDQA eR9/uIdyAxx74NvvXuIPnFY0dPfBFDGrxHRCfMvkgtEilZoUUEwv13wDh2gNNq0o 3jIkDzTeaTEdbafv8si7HUSNNxgFm+CAWeTcWMJmy5r6D01YQhAgPKsqmY6/UvKa YpILccEpSNUvVy+kthCOWlYAWguMdAhHCN+906w4Y41LyG8BtBx7xTezcTCCcZ7n +czpaxL305StUfMV9da4I83ROgUScBQRRCsB6glQBEiwNC6VpGkf/raq9zUD2aWQ gkHPGGWGZil9S045SJA96UwguQxS2gCKkyWueElnSqUg2OuuPUGMUakqMu6se20= =TzMz -----END PGP SIGNATURE----- From slackph at posteo.de Tue Dec 15 16:48:29 2015 From: slackph at posteo.de (Philip Lacroix) Date: Tue, 15 Dec 2015 17:48:29 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: <56703913.8040804@exitstatusone.com> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> <825f4750e4d813a1e43976f1840a30e4@posteo.de> <56703913.8040804@exitstatusone.com> Message-ID: <1fed96e5ed21e032565aa67b763c16ff@posteo.de> Hi all I've built a test python3-pillow with support for both Python versions, where Python 2 is built *after* Phyton 3. There is no difference in the resulting content of /usr/bin with respect to python-pillow (and the shabang in all files is the default #!/usr/bin/python). The only difference is the additional /usr/lib{$LIBDIRSUFFIX}/python3.x directory. This shouldn't cause anything to break if python-pillow is replaced with python3-pillow, and the software I'm packaging (which would have python3-pillow as a requirement) is happy with this. If you guys have nothing against it, I'll submit a new python3-pillow SlackBuild according to the above points. Philip Am 15.12.2015 17:00 schrieb Brenton Earl: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I did not intend on adding python 3 support to my python-pillow > SlackBuild. This SlackBuild is a dependency of my mitmproxy > SlackBuild. Another dependency that needs to be updated is urwid, > which exists in Slackware. I am not able to submit mitmproxy due to > urwid being too outdated in 14.1. I cannot test in -current either > because I need version urwid 1.3.1 and only 1.3.0 is available. None > of this requires python 3. > > I discussed with one of the SBo admins that prior to creating my > python-pillow SlackBuild that it would be removed once 14.2 was > released. I would not recommend relying on my python-pillow package > for this reason. Anyway, it exists -current and will be apart of > Slackware in the future. So track the version in -current rather than > mine. > > If you really need python 3 support for Pillow, then you should create > a separate python3-pillow SlackBuild. > > > On 12/15/2015 07:53 AM, David Spencer wrote: >> Hi, sorry to have been late catching up with this thread, >> >> I think a single SlackBuild that auto-detects python3 is a >> horrible idea for python-pillow. It would cause an instant >> regression the moment that someone with python3 upgrades >> python-pillow-SBo to the python2-only python-pillow in -current or >> 14.2. A separate python3-pillow would "just work" now, and would >> still "just work" after 14.2 is released, unless Patrick is >> suddenly going to move 14.2 to python3 and change his >> python-pillow. >> >> -D. >> >> On 15 December 2015 at 13:12, Philip Lacroix >> wrote: >>> Am 14.12.2015 23:19 schrieb B Watson: >>>> >>>> What happens if someone needs both python 2 and 3 support? >>>> >>>> Does the python3 stuff actually conflict with the python2 >>>> stuff? If not, maybe it'd be good to allow building both >>>> instead of choosing only one or the other. >>> >>> >>> Removed redundant assignments in the case construct: >>> >>> ##### B1="2"; B2="" >>> >>> if [ "${PYTHON3SUPPORT:-no}" == "yes" ]; then case "$BUILD_FIRST" >>> in 2) B2="3" ;; 3) B1="3"; B2="2" ;; *) B1="3" ;; esac fi >>> >>> python$B1 setup.py install --root=$PKG if [[ -n $B2 ]]; then >>> python$B2 setup.py install --root=$PKG fi ##### >>> > > - -- > Brenton Earl From brent at exitstatusone.com Tue Dec 15 17:29:52 2015 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 15 Dec 2015 10:29:52 -0700 Subject: [Slackbuilds-users] Support for Python 3 in python-pillow? In-Reply-To: <1fed96e5ed21e032565aa67b763c16ff@posteo.de> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> <825f4750e4d813a1e43976f1840a30e4@posteo.de> <56703913.8040804@exitstatusone.com> <1fed96e5ed21e032565aa67b763c16ff@posteo.de> Message-ID: <56704E10.2010801@exitstatusone.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 The only problem I see with adding support for both 2 and 3 is that your python3-pillow will conflict with the official Slackware package when 14.2 is released. I believe that Pat's python-pillow is a dependency of hplip, and maybe other packages. I haven't checked what else though. For this reason, my package is intended to be removed once 14.2 is out. It might be good to test your SlackBuild on - -current before submitting it. On 12/15/2015 09:48 AM, Philip Lacroix wrote: > Hi all > > I've built a test python3-pillow with support for both Python > versions, where Python 2 is built *after* Phyton 3. > > There is no difference in the resulting content of /usr/bin with > respect to python-pillow (and the shabang in all files is the > default #!/usr/bin/python). The only difference is the additional > /usr/lib{$LIBDIRSUFFIX}/python3.x directory. This shouldn't cause > anything to break if python-pillow is replaced with python3-pillow, > and the software I'm packaging (which would have python3-pillow as > a requirement) is happy with this. > > If you guys have nothing against it, I'll submit a new > python3-pillow SlackBuild according to the above points. > > Philip > > > Am 15.12.2015 17:00 schrieb Brenton Earl: >> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >> >> I did not intend on adding python 3 support to my python-pillow >> SlackBuild. This SlackBuild is a dependency of my mitmproxy >> SlackBuild. Another dependency that needs to be updated is >> urwid, which exists in Slackware. I am not able to submit >> mitmproxy due to urwid being too outdated in 14.1. I cannot test >> in -current either because I need version urwid 1.3.1 and only >> 1.3.0 is available. None of this requires python 3. >> >> I discussed with one of the SBo admins that prior to creating my >> python-pillow SlackBuild that it would be removed once 14.2 was >> released. I would not recommend relying on my python-pillow >> package for this reason. Anyway, it exists -current and will be >> apart of Slackware in the future. So track the version in >> -current rather than mine. >> >> If you really need python 3 support for Pillow, then you should >> create a separate python3-pillow SlackBuild. >> >> >> On 12/15/2015 07:53 AM, David Spencer wrote: >>> Hi, sorry to have been late catching up with this thread, >>> >>> I think a single SlackBuild that auto-detects python3 is a >>> horrible idea for python-pillow. It would cause an instant >>> regression the moment that someone with python3 upgrades >>> python-pillow-SBo to the python2-only python-pillow in -current >>> or 14.2. A separate python3-pillow would "just work" now, and >>> would still "just work" after 14.2 is released, unless Patrick >>> is suddenly going to move 14.2 to python3 and change his >>> python-pillow. >>> >>> -D. >>> >>> On 15 December 2015 at 13:12, Philip Lacroix >>> wrote: >>>> Am 14.12.2015 23:19 schrieb B Watson: >>>>> >>>>> What happens if someone needs both python 2 and 3 support? >>>>> >>>>> Does the python3 stuff actually conflict with the python2 >>>>> stuff? If not, maybe it'd be good to allow building both >>>>> instead of choosing only one or the other. >>>> >>>> >>>> Removed redundant assignments in the case construct: >>>> >>>> ##### B1="2"; B2="" >>>> >>>> if [ "${PYTHON3SUPPORT:-no}" == "yes" ]; then case >>>> "$BUILD_FIRST" in 2) B2="3" ;; 3) B1="3"; B2="2" ;; *) B1="3" >>>> ;; esac fi >>>> >>>> python$B1 setup.py install --root=$PKG if [[ -n $B2 ]]; then >>>> python$B2 setup.py install --root=$PKG fi ##### - -- Brenton Earl -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWcE4QAAoJEMAWbOXyIOfzosMH/2fm0f40/IiZZs6WTSqJx1J4 xiSRRV86hjdlXoLsElkOZr5CFQjfJL1bikNJm/JOGGufP89Pol7qH6HUjxFrSpZM oSH0uvljGFHrW9qcuP/hi2BmkWBNC45P+5kzYxaxXKFRC8WMI0NuoTm5MnLXjkPI ffTX5oXOpYbW0I4P+Hh9vur7RN3NJnJnQm0xEdlMnDi8g6kewBGm3RqLqaoQTxJi YZNSmCwIyw2JbFKprY8FRcgaQlbyFbnTSJ3G1FoPI4nZgdoIys1wohZmEoSNhD/8 SWddPCJZlJwrJ2bdsVh7gAVJ1FVrgwIAvKMIiCLVchSMOXekwjth7QncNASGfd8= =XOmI -----END PGP SIGNATURE----- From slackph at posteo.de Tue Dec 15 18:02:27 2015 From: slackph at posteo.de (Philip Lacroix) Date: Tue, 15 Dec 2015 19:02:27 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: <56704E10.2010801@exitstatusone.com> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> <825f4750e4d813a1e43976f1840a30e4@posteo.de> <56703913.8040804@exitstatusone.com> <1fed96e5ed21e032565aa67b763c16ff@posteo.de> <56704E10.2010801@exitstatusone.com> Message-ID: Am 15.12.2015 18:29 schrieb Brenton Earl: > The only problem I see with adding support for both 2 and 3 is that > your python3-pillow will conflict with the official Slackware package > when 14.2 is released. There will be a note in the README mentioning that the two packages cannot coexist. > I believe that Pat's python-pillow is a > dependency of hplip, and maybe other packages. I haven't checked what > else though. For this reason, my package is intended to be removed > once 14.2 is out. It might be good to test your SlackBuild on > - -current before submitting it. Thanks, I will test that, but since the exact content of python-pillow is included in python3-pillow, from the point of view of packages depending on Pat's python-pillow there shouldn't be any difference, unless I'm missing something (in which case I'll stand corrected). Here's the diff output: ----- $ diff -r /tmp/SBo/package-python-pillow/ /tmp/SBo/package-python3-pillow/ Only in /tmp/SBo/package-python-pillow/usr/doc: python-pillow-3.0.0 Only in /tmp/SBo/package-python3-pillow/usr/doc: python3-pillow-3.0.0 Only in /tmp/SBo/package-python3-pillow/usr/lib64: python3.4 ----- > On 12/15/2015 09:48 AM, Philip Lacroix wrote: >> Hi all >> >> I've built a test python3-pillow with support for both Python >> versions, where Python 2 is built *after* Phyton 3. >> >> There is no difference in the resulting content of /usr/bin with >> respect to python-pillow (and the shabang in all files is the >> default #!/usr/bin/python). The only difference is the additional >> /usr/lib{$LIBDIRSUFFIX}/python3.x directory. This shouldn't cause >> anything to break if python-pillow is replaced with python3-pillow, >> and the software I'm packaging (which would have python3-pillow as >> a requirement) is happy with this. >> >> If you guys have nothing against it, I'll submit a new >> python3-pillow SlackBuild according to the above points. From slackph at posteo.de Tue Dec 15 18:13:52 2015 From: slackph at posteo.de (Philip Lacroix) Date: Tue, 15 Dec 2015 19:13:52 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> <825f4750e4d813a1e43976f1840a30e4@posteo.de> <56703913.8040804@exitstatusone.com> <1fed96e5ed21e032565aa67b763c16ff@posteo.de> <56704E10.2010801@exitstatusone.com> Message-ID: <836d05e3649d3195c6ae4ce42fd8e2bc@posteo.de> > Am 15.12.2015 18:29 schrieb Brenton Earl: >> The only problem I see with adding support for both 2 and 3 is that >> your python3-pillow will conflict with the official Slackware package >> when 14.2 is released. It would conflict anyway, even if it included support for Python 3 only, because of files in /usr/bin/. From brent at exitstatusone.com Tue Dec 15 18:17:22 2015 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 15 Dec 2015 11:17:22 -0700 Subject: [Slackbuilds-users] pilkit md5 hash Message-ID: <56705932.8040707@exitstatusone.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 While installing another SlackBuild I found that the md5 hash for pilkit 1.1.13 should be: dc586362902dcc1110d487d7c8ffd5e4 Thanks, - -- Brenton Earl -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWcFkyAAoJEMAWbOXyIOfzea0IAIegPyMV438h7FD+RYjSepsG 0GeKkDznzAOfWKu4pTRe5AMaq5SPmWoQPqwyURCm23wM7x3losQbm/q6E3HsaF2p O4WeXZtz4vKlTdPPAyY9GBCQIeRwQSmCWdODH0g71tQf3bFJ7zyrxJLOQH43rRiW ad5hclpwKeGbjaW3pNxugumN+TKJ5C94qwqFN8aJGYeuYvrsj7le7ym2ieQp73O5 2EukFXY+FYJbOQ5Ig4jObt9g7ZRJqX4IVE41/aj2fmKIq5EQbM8pQC9W6NPQl4Tn G5WPLLcxLCBMecOQqbDb6d0PRyxedBoH4yPo8iPMToaS7GwwzAZh/PW4O5Xljwc= =+WqL -----END PGP SIGNATURE----- From willysr at slackbuilds.org Tue Dec 15 18:36:12 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 16 Dec 2015 01:36:12 +0700 Subject: [Slackbuilds-users] pilkit md5 hash In-Reply-To: <56705932.8040707@exitstatusone.com> References: <56705932.8040707@exitstatusone.com> Message-ID: <56705D9C.1020101@slackbuilds.org> > While installing another SlackBuild I found that the md5 hash for > pilkit 1.1.13 should be: > > dc586362902dcc1110d487d7c8ffd5e4 Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chuangtzu.forum at yahoo.com Thu Dec 17 19:20:27 2015 From: chuangtzu.forum at yahoo.com (ChuangTzu) Date: Thu, 17 Dec 2015 14:20:27 -0500 Subject: [Slackbuilds-users] keepassx 0.4.3 source is no longer available Message-ID: <56730AFB.9020200@yahoo.com> Hello, I emailed the Slackbuild maintainer and also wanted to notify the mailing list. Keepassx 0.4.3 is no longer available; If you follow the current source link http://sourceforge.net/projects/keepassx/files/ you will see the message "This project has no files". https://www.keepassx.org/news/2015/12/551 shows an update for 0.4 series. https://www.keepassx.org/releases/0.4.4/keepassx-0.4.4.tar.gz new source link. I was able to build and install by changing the Slackbuild manually, however, it would be beneficial to change to the new source 0.4.4 since it corrects a security flaw in 0.4.3, and some users might not take the time to locate the new updated/source file. Regards and thank you for maintaining all of these Slackbuilds! From willysr at slackbuilds.org Fri Dec 18 04:17:29 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 18 Dec 2015 11:17:29 +0700 Subject: [Slackbuilds-users] keepassx 0.4.3 source is no longer available In-Reply-To: <56730AFB.9020200@yahoo.com> References: <56730AFB.9020200@yahoo.com> Message-ID: <567388D9.90307@slackbuilds.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > Keepassx 0.4.3 is no longer available; If you follow the current > source link http://sourceforge.net/projects/keepassx/files/ you > will see the message "This project has no files". > > https://www.keepassx.org/news/2015/12/551 shows an update for 0.4 > series. > > https://www.keepassx.org/releases/0.4.4/keepassx-0.4.4.tar.gz new > source link. > > I was able to build and install by changing the Slackbuild > manually, however, it would be beneficial to change to the new > source 0.4.4 since it corrects a security flaw in 0.4.3, and some > users might not take the time to locate the new updated/source > file. Hi Thanks i have updated the SlackBuild in my branch and it will be part for the next batch of update - -- Willy Sudiarto Raharjo -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlZziNkACgkQiHuDdNczM4GqCgCgi6rjk78MvOapALtr6rJYEVYh BacAn1MZj9y86GiARi7tE3apqUwJuArp =sWuo -----END PGP SIGNATURE----- From willysr at slackbuilds.org Sat Dec 19 00:46:55 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 19 Dec 2015 07:46:55 +0700 Subject: [Slackbuilds-users] Updates - 20151219.1 Message-ID: <5674A8FF.3040106@slackbuilds.org> Sat Dec 19 00:27:04 UTC 2015 desktop/mimi: Added (xdg-open alternative). development/SQLAlchemy: Updated for version 1.0.10. development/hhvm-pgsql: Updated for version 3.11.0. development/kicad: Updated for version 4.0.0 + new maintainer. development/leiningen: Updated for version 2.5.3. development/lighttable: Updated for version 0.8.0. development/pycharm: Updated for version 5.0.2. development/rust: Updated for version 1.5.0. development/tyrutils-ericw: Added (Map Compiling Tools). development/ucpp: Added (C preprocessor compliant to ISO-C99). development/vispatch: Added (VIS Patching for Quake BSPs). games/mgba: Updated for version 0.3.2. games/pioneer: Updated for version 20151214. games/ut2004: Update launcher. games/yamagi-quake2: Updated for version 5.32. graphics/brlcad: Add note about qt5 conflict. graphics/shutter: Fix .info. libraries/CondConfigParser: Addec (Python library). libraries/activemq-cpp: Updated for version 3.9.1. libraries/agg: Fixed download url and homepage. libraries/botocore: Updated for version 1.3.13. libraries/cffi: Updated for version 1.4.1. libraries/libcmis: Update script. libraries/libcpuid: Updated for version 0.2.2. libraries/libeot: Added (Embedded OpenType Import Library). libraries/libgaminggear: Added (Libraries for gaming input devices). libraries/libkvkontakte: Patched to work with newer cmake. libraries/liblangtag: Added (access tags for identifying languages). libraries/libmspub: Added (Microsoft Publisher Import Library). libraries/libmwaw: Added (Import library). libraries/liborcus: Added (documents processing library). libraries/libpagemaker: Added (Adobe PageMaker Import Library). libraries/libsodium: Updated for version 1.0.7. libraries/libtermkey: Updated for version 0.18. libraries/libuv: Updated for version 1.8.0. libraries/libvisio: Added (Microsoft Visio Import Library). libraries/libwps: Added (Microsoft Works format import library). libraries/msgpack-c: Updated for version 1.3.0. libraries/python3-pillow: Added (Python3 support for python-pillow). libraries/trader: Added (Technical Analysis for traders). libraries/unibilium: Updated for version 1.2.0. misc/abduco: Added (session manager). misc/fcitx-configtool: Updated for version 0.4.8. misc/fcitx: Updated for version 4.2.8.6. misc/kcm-fcitx: Updated for version 0.4.3. multimedia/minidlna: Updated for version 1.1.5. multimedia/x265: Updated for version 1.8. network/aldryn-client: Updated for version 2.0.5. network/aria2: Updated for version 1.19.3. network/awscli: Updated for version 1.9.13. network/memcached: Updated for version 1.4.25. network/owncloud-client: Updated for version 2.1.0. network/pentadactyl: Updated for version 20151215. network/qTox: Updated for version 20151212. network/teamviewer: Updated for version 11.0.53191. network/tor-browser: Updated for version 5.0.6. network/toxcore: Updated for version 20151211. network/uTox: Added (The lightest and fluffiest Tox client). network/vivaldi: Updated for version 1.0.344.5_1. network/you-get: Updated for version 0.4.210. network/youtube-dl: Updated for version 2015.12.13. office/impressive: Updated for version 0.11.1. office/keepassx: Updated for version 0.4.4. office/libreoffice-helppack: Updated for version 5.0.4. office/libreoffice-langpack: Updated for version 5.0.4. office/libreoffice: Updated for version 5.0.4. office/mythes: Added (simple thesaurus). office/pdf2djvu: Updated for version 0.9.3. office/texstudio: Updated for version 2.10.4. python/colorama: Updated for version 0.3.5. python/pilkit: Update MD5SUM. python/pyperclip: Updated for version 1.5.25. python/pytest: Updated for version 2.8.5. python/python3: Updated for version 3.5.1. python/tox: Updated for version 2.3.1. ruby/heroku-client: Updated for version 3.42.25. system/fio: Updated for version 2.2.13. system/gencfs: Updated for version 1.2. system/gnome-disk-utility: Added (storage device manipulation tools) system/gparted: Updated for version 0.24.0. system/jenkins: Updated for version 1.641. system/mlterm: Updated for version 3.6.1. system/nvidia-driver: Updated for version 352.63. system/nvidia-kernel: Updated for version 352.63. system/nvidia-legacy304-driver: Updated for version 304.131. system/nvidia-legacy304-kernel: Updated for version 304.131. system/nvidia-legacy340-driver: Updated for version 340.96. system/nvidia-legacy340-kernel: Updated for version 340.96. system/patool: Updated for version 1.10. system/qemu: Updated for version 2.4.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slackph at posteo.de Sat Dec 19 16:39:26 2015 From: slackph at posteo.de (Philip Lacroix) Date: Sat, 19 Dec 2015 17:39:26 +0100 Subject: [Slackbuilds-users] =?utf-8?q?Support_for_Python_3_in_python-pill?= =?utf-8?b?b3c/?= In-Reply-To: <56704E10.2010801@exitstatusone.com> References: <2639962ad9bc82e442ba553324bd3f67@posteo.de> <7b14c8be7a396cdb2625134cf7861a00@posteo.de> <9b6e28cdbe5da989d732efe46b3dcf92@posteo.de> <825f4750e4d813a1e43976f1840a30e4@posteo.de> <56703913.8040804@exitstatusone.com> <1fed96e5ed21e032565aa67b763c16ff@posteo.de> <56704E10.2010801@exitstatusone.com> Message-ID: <6dcd18d618742da7940338a99a48b987@posteo.de> A short follow-up. A non-invasive python3-pillow Slackbuild is now available as a complement to python-pillow. Thanks to all who answered to my post for your valuable input. Philip From chuangtzu.forum at yahoo.com Sat Dec 19 21:04:56 2015 From: chuangtzu.forum at yahoo.com (ChuangTzu) Date: Sat, 19 Dec 2015 16:04:56 -0500 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 116, Issue 11 In-Reply-To: References: Message-ID: <5675C678.3060106@yahoo.com> Thank You Willy! slackbuilds-users-request at slackbuilds.org wrote: > Send SlackBuilds-users mailing list submissions to > slackbuilds-users at slackbuilds.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > or, via email, send a message with subject or body 'help' to > slackbuilds-users-request at slackbuilds.org > > You can reach the person managing the list at > slackbuilds-users-owner at slackbuilds.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SlackBuilds-users digest..." > > > Today's Topics: > > 1. Re: Support for Python 3 in python-pillow? (Philip Lacroix) > 2. Re: Support for Python 3 in python-pillow? (Philip Lacroix) > 3. pilkit md5 hash (Brenton Earl) > 4. Re: pilkit md5 hash (Willy Sudiarto Raharjo) > 5. keepassx 0.4.3 source is no longer available (ChuangTzu) > 6. Re: keepassx 0.4.3 source is no longer available > (Willy Sudiarto Raharjo) > 7. Updates - 20151219.1 (Willy Sudiarto Raharjo) > 8. Re: Support for Python 3 in python-pillow? (Philip Lacroix) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 15 Dec 2015 19:02:27 +0100 > From: Philip Lacroix > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Support for Python 3 in > python-pillow? > Message-ID: > Content-Type: text/plain; charset=US-ASCII; format=flowed > > Am 15.12.2015 18:29 schrieb Brenton Earl: >> The only problem I see with adding support for both 2 and 3 is that >> your python3-pillow will conflict with the official Slackware package >> when 14.2 is released. > There will be a note in the README mentioning that the two packages > cannot coexist. > >> I believe that Pat's python-pillow is a >> dependency of hplip, and maybe other packages. I haven't checked what >> else though. For this reason, my package is intended to be removed >> once 14.2 is out. It might be good to test your SlackBuild on >> - -current before submitting it. > Thanks, I will test that, but since the exact content of python-pillow > is included in python3-pillow, from the point of view of packages > depending on Pat's python-pillow there shouldn't be any difference, > unless I'm missing something (in which case I'll stand corrected). > > Here's the diff output: > ----- > $ diff -r /tmp/SBo/package-python-pillow/ > /tmp/SBo/package-python3-pillow/ > Only in /tmp/SBo/package-python-pillow/usr/doc: python-pillow-3.0.0 > Only in /tmp/SBo/package-python3-pillow/usr/doc: python3-pillow-3.0.0 > Only in /tmp/SBo/package-python3-pillow/usr/lib64: python3.4 > ----- > > >> On 12/15/2015 09:48 AM, Philip Lacroix wrote: >>> Hi all >>> >>> I've built a test python3-pillow with support for both Python >>> versions, where Python 2 is built *after* Phyton 3. >>> >>> There is no difference in the resulting content of /usr/bin with >>> respect to python-pillow (and the shabang in all files is the >>> default #!/usr/bin/python). The only difference is the additional >>> /usr/lib{$LIBDIRSUFFIX}/python3.x directory. This shouldn't cause >>> anything to break if python-pillow is replaced with python3-pillow, >>> and the software I'm packaging (which would have python3-pillow as >>> a requirement) is happy with this. >>> >>> If you guys have nothing against it, I'll submit a new >>> python3-pillow SlackBuild according to the above points. > > ------------------------------ > > Message: 2 > Date: Tue, 15 Dec 2015 19:13:52 +0100 > From: Philip Lacroix > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Support for Python 3 in > python-pillow? > Message-ID: <836d05e3649d3195c6ae4ce42fd8e2bc at posteo.de> > Content-Type: text/plain; charset=US-ASCII; format=flowed > >> Am 15.12.2015 18:29 schrieb Brenton Earl: >>> The only problem I see with adding support for both 2 and 3 is that >>> your python3-pillow will conflict with the official Slackware package >>> when 14.2 is released. > It would conflict anyway, even if it included support for Python 3 only, > because of files in /usr/bin/. > > > ------------------------------ > > Message: 3 > Date: Tue, 15 Dec 2015 11:17:22 -0700 > From: Brenton Earl > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] pilkit md5 hash > Message-ID: <56705932.8040707 at exitstatusone.com> > Content-Type: text/plain; charset=utf-8 > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > While installing another SlackBuild I found that the md5 hash for > pilkit 1.1.13 should be: > > dc586362902dcc1110d487d7c8ffd5e4 > > Thanks, > - -- > Brenton Earl > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJWcFkyAAoJEMAWbOXyIOfzea0IAIegPyMV438h7FD+RYjSepsG > 0GeKkDznzAOfWKu4pTRe5AMaq5SPmWoQPqwyURCm23wM7x3losQbm/q6E3HsaF2p > O4WeXZtz4vKlTdPPAyY9GBCQIeRwQSmCWdODH0g71tQf3bFJ7zyrxJLOQH43rRiW > ad5hclpwKeGbjaW3pNxugumN+TKJ5C94qwqFN8aJGYeuYvrsj7le7ym2ieQp73O5 > 2EukFXY+FYJbOQ5Ig4jObt9g7ZRJqX4IVE41/aj2fmKIq5EQbM8pQC9W6NPQl4Tn > G5WPLLcxLCBMecOQqbDb6d0PRyxedBoH4yPo8iPMToaS7GwwzAZh/PW4O5Xljwc= > =+WqL > -----END PGP SIGNATURE----- > > > ------------------------------ > > Message: 4 > Date: Wed, 16 Dec 2015 01:36:12 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] pilkit md5 hash > Message-ID: <56705D9C.1020101 at slackbuilds.org> > Content-Type: text/plain; charset="windows-1252" > >> While installing another SlackBuild I found that the md5 hash for >> pilkit 1.1.13 should be: >> >> dc586362902dcc1110d487d7c8ffd5e4 > Fixed in my branch > > Thanks > > From arkadiusz at drabczyk.org Sun Dec 20 14:04:03 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sun, 20 Dec 2015 14:04:03 +0000 (UTC) Subject: [Slackbuilds-users] development/global should be updated Message-ID: We have 6.2.5 and the newest stable version is 6.5.2. The main difference between these two versions is that in 6.5.2 a new GTAGSLABEL called `pygments' is added to gtags.conf and it's needed for Python support. -- Arkadiusz Drabczyk From lukenshiro at ngi.it Mon Dec 21 17:02:36 2015 From: lukenshiro at ngi.it (LukenShiro) Date: Mon, 21 Dec 2015 18:02:36 +0100 Subject: [Slackbuilds-users] fltk in -current In-Reply-To: References: Message-ID: <20151221180236.3ad80f83@hamalayi.mnt> On Fri, 27 Nov 2015 12:24:21 -0500 B Watson wrote: > Is the SBo fltk build going to stay in the repo, maybe renamed to > fltk11 or fltk-legacy? Or will it go away, and everything that uses > fltk get patched to work with 1.3 (if possible)? Sorry for the delay, my plans are really simple ;) I intend to drop fltk(1.3.x) as it is in current/extra now (so it doesn't make sense to keep it here in post-14.1). I believe I will continue SlackBuild maintainance for fltk(1.1.x) as there are many packages who depend on it, anyway this script needs some modifications (fltk11 renaming, configure options etc..), and I've no problems to do what it is needed :P fltk-1.1 and fltk-1.3 are completely incompatible but they could co-exist in some way (no patch and no porting, just some change of directory for include files and libs). Best regards. -- GNU/Linux * Slackware64 current * k4.3.3 LU #210970 SU #12583 LM #98222/#412913 From lksj at yandex.ru Tue Dec 22 17:20:14 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Tue, 22 Dec 2015 20:20:14 +0300 Subject: [Slackbuilds-users] Patch for dvdauthor Message-ID: <923071450804814@web2o.yandex.ru> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: dvdauthor.patch Type: text/x-diff Size: 11028 bytes Desc: not available URL: From hba.nihilismus at gmail.com Wed Dec 23 00:55:23 2015 From: hba.nihilismus at gmail.com (=?UTF-8?Q?Antonio_Hern=C3=A1ndez_Blas?=) Date: Tue, 22 Dec 2015 18:55:23 -0600 Subject: [Slackbuilds-users] Fwd: PGBouncer script In-Reply-To: References: Message-ID: ---------- Forwarded message ---------- From: Thiago Ferreira Date: Tue, Dec 22, 2015 at 4:31 PM Subject: PGBouncer script To: hba.nihilismus at gmail.com Mr. Blas, Good afternoon! Today I finally got a time to update the pgbouncer in my computers/clusters, but when I went in the SBo to do download of the newest version of the scripts/pgbouncer, I saw that you did not have updated them yet. So, I used the old script available in the site. I needed to do 2 changes in the script, changes that I described now: 1 - Change the Script version 2 - Remove 2 files that are not more available in the tar file. I am forwarding for you the script updated. Regards, -- Thiago Ferreira Linux User #487560 (counter.li.org) Hi Thiago, i stoped using Slackware since some months ago so feel free to take pgBouncer maintainership ;-) - 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: pgbouncer.SlackBuild Type: application/octet-stream Size: 4031 bytes Desc: not available URL: From willysr at slackbuilds.org Wed Dec 23 00:57:22 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 23 Dec 2015 07:57:22 +0700 Subject: [Slackbuilds-users] Fwd: PGBouncer script In-Reply-To: References: Message-ID: <5679F172.2050902@slackbuilds.org> > I am forwarding for you the script updated. please submit them via submission form http://slackbuilds.org/submit/ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Wed Dec 23 07:23:55 2015 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 22 Dec 2015 23:23:55 -0800 Subject: [Slackbuilds-users] Patch for dvdauthor In-Reply-To: <923071450804814@web2o.yandex.ru> References: <923071450804814@web2o.yandex.ru> Message-ID: <567A4C0B.8040507@gmail.com> On 12/22/2015 09:20 AM, ????????? ??????? wrote: > Hello. Let me introduce patch for dvdauthor. > over time the dvdunauthor has generated the wrong file dvdauthor.xml, > that?can not be used for build dvd. > Now you can unbuild dvd and build again. > ? > What is done: > 1. Remove generation items and attirbutes, that break build dvd process > ("titlemap" and "buttons" tags, "audio id","audio presents" and > "subpicture present" attributes). > 2. Fixed "jump" command for jump to menu item. > 3. Remove some "exit" calls aka "exit(1)", for print errors to screen > and not silent exit. > 4. Fixed bug in audio_format list. > 5. Add video attributes: video_format ("ntsc", "pal") and display aspect > ratio ("4:3", "16:9"). > 6. Fixed dvdauthor.xsd file for correct validation dvdauthor.xml. The > structure corresponds to the dvdauthor manual page. > ? > The patch is applied. > ? > -- > ? ?????????, ?.????????? > ? > I am the current maintainer of dvdauthor. Since I use various frontends for dvdauthor, and I have not observed any issues, this patch is a bit much for me to test and verify. Nothing you patched involved compiling and packaging on Slackware. They look like bug fixes and feature improvements. I suggest you send them to the upstream developers. Development is still on going, if a bit slow. http://dvdauthor.sourceforge.net/ https://github.com/ldo/dvdauthor Mailing Lists: https://lists.sourceforge.net/lists/listinfo/dvdauthor-users https://lists.sourceforge.net/lists/listinfo/dvdauthor-developer Thanks -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri Dec 25 02:44:58 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 25 Dec 2015 09:44:58 +0700 Subject: [Slackbuilds-users] Updates - 20151225.1 Message-ID: <567CADAA.4010200@slackbuilds.org> Merry Christmas everyone!! This will be the last update in 2015. Hope to see you guys again in 2016 :) happy holiday Fri Dec 25 02:35:35 UTC 2015 academic/sage: Updated for version 6.10. audio/apulse: Updated for version 20151219. audio/lmms: Updated for version 1.1.3. development/SQLAlchemy: Updated for version 1.0.11. development/flow: Added (A static type checker for JavaScript). development/gnats: Added (set of tools for tracking bugs). development/lighttable: Fix indentation. development/pycharm: Updated for version 5.0.3. development/watchman: Added (A file watching service). games/angband: Updated for version. games/atanks: Updated for version 6.4. games/jackhammer: Updated for version 11855. games/mednafen: Fix indentation. games/roccat-tools: Added (Roccat common files). games/supertuxkart: Updated for version 0.9.1. games/warsow: Updated for version 2.01. gis/cligj: Updated for version 0.4.0. gis/osm-gps-map: Added (gtk mapping widget). gis/rasterio: Updated for version 0.31.0. graphics/pngquant: Updated for version 2.5.2. graphics/potrace: Updated for version 1.13. libraries/OpenAL: Updated for version 1.17.1. libraries/batinfo: Removes python3 support. libraries/botocore: Updated for version 1.3.14. libraries/cffi: Updated for version 1.4.2. libraries/enum34: Updated for version 1.1.2. libraries/libewf: Patch for newer GCC. libraries/liblangtag: Fix VERSION. libraries/libmseed: Added (C library framework). libraries/libva: Updated for version 1.6.2. libraries/png++: Added (C++ wrapper for libpng). libraries/pymdstat: Removes python3 support. libraries/wxSQLite3: Updated for version 3.3.0. misc/fcitx-mozc: Added (Mozc engine for fcitx). multimedia/lives: Updated for version 2.4.6. network/awscli: Updated for version 1.9.14. network/bottle: Removes python3 support. network/claws-mail: Updated for version 3.13.1. network/clipgrab: Updated for version 3.5.6. network/dropbox: Updated for version 3.12.6. network/gtk-gnutella: Updated for version 1.1.8. network/hylafax+: Updated for version 5.5.6. network/icecat: Updated for version 38.5.0. network/mumble: Updated for version 1.2.11. network/murmur: Updated for version 1.2.11. network/pentadactyl: Updated for version 20151223. network/purple-facebook: Updated for version 078fbf8d1a4e. network/tixati: Updated for version 2.31_1. network/uTox: Updated for version 078fbf8d1a4e. network/vivaldi: Updated for version 1.0.352.3_1. network/you-get: Updated for version 0.4.217. network/youtube-dl: Updated for version 2015.12.18. perl/perl-CPAN-Meta-YAML: Updated for version 0.018. python/psutil: Updated for version 3.3.0. python/py3sensors: Removes python3 support. system/Iosevka: Updated for version 1.5.1. system/adobe-source-code-pro-font: Update DOWNLOAD url. system/colord-gtk: Added (GTK integration for libcolord). system/glances: Removes python3 support. system/hardinfo: Patched for newer GCC. system/letsencrypt: Updated for version 0.1.1. system/mksh: Updated for version R52. system/parallel: Updated for version 20151222. system/sqlcipher: Added (256 bit AES encryption SQLite extension). system/udiskie: Updated for version 1.4.1. system/vagrant: Updated for version 1.8.0. system/wine-staging: Added (Wine Is Not an Emulator Staging). system/z: Updated for version 1.9. +--------------------------+ -- 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 Dec 25 03:28:55 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 25 Dec 2015 10:28:55 +0700 Subject: [Slackbuilds-users] Updates - 20151225.2 Message-ID: <567CB7F7.5080803@slackbuilds.org> Sorry folks, i forgot to add single diff for uTox Fri Dec 25 03:24:58 UTC 2015 network/uTox: Added missing gtk2.diff. -- 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 chuangtzu.forum at yahoo.com Fri Dec 25 21:01:02 2015 From: chuangtzu.forum at yahoo.com (ChuangTzu) Date: Fri, 25 Dec 2015 16:01:02 -0500 Subject: [Slackbuilds-users] bad link for xulrunner source In-Reply-To: References: Message-ID: <567DAE8E.7090200@yahoo.com> Hello, The correct link should be: https://ftp.mozilla.org/pub/xulrunner/releases/15.0.1/source/xulrunner-15.0.1.source.tar.bz2 From willysr at slackbuilds.org Sat Dec 26 00:33:18 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 26 Dec 2015 07:33:18 +0700 Subject: [Slackbuilds-users] bad link for xulrunner source In-Reply-To: <567DAE8E.7090200@yahoo.com> References: <567DAE8E.7090200@yahoo.com> Message-ID: <567DE04E.6050908@slackbuilds.org> > The correct link should be: > https://ftp.mozilla.org/pub/xulrunner/releases/15.0.1/source/xulrunner-15.0.1.source.tar.bz2 Thanks Fixed in my branch already -- 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 chuangtzu.forum at yahoo.com Sun Dec 27 01:23:45 2015 From: chuangtzu.forum at yahoo.com (ChuangTzu) Date: Sat, 26 Dec 2015 20:23:45 -0500 Subject: [Slackbuilds-users] gnucash will not build without geoclue In-Reply-To: References: Message-ID: <567F3DA1.8040709@yahoo.com> Hello, geoclue is listed as an optional dependency for webkitgtk, however, gnucash will not build without it. Perhaps it can be listed as a dependency for gnucash? Regards. From willysr at slackbuilds.org Sun Dec 27 04:16:55 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 27 Dec 2015 11:16:55 +0700 Subject: [Slackbuilds-users] gnucash will not build without geoclue In-Reply-To: <567F3DA1.8040709@yahoo.com> References: <567F3DA1.8040709@yahoo.com> Message-ID: <567F6637.9080400@slackbuilds.org> > geoclue is listed as an optional dependency for webkitgtk, however, > gnucash will not build without it. Perhaps it can be listed as a > dependency for gnucash? I just tested on slackware64-14.1 and build it using sbopkg and it works fine without geoclue: libwebp: MD5SUM check for libwebp-0.4.3.tar.gz ... OK Building package libwebp-0.4.3-x86_64-1_SBo.tgz ... OK Installing package libwebp-0.4.3-x86_64-1_SBo.tgz ... OK orc: MD5SUM check for orc-0.4.23.tar.xz ... OK Building package orc-0.4.23-x86_64-1_SBo.tgz ... OK Installing package orc-0.4.23-x86_64-1_SBo.tgz ... OK gstreamer1: MD5SUM check for gstreamer-1.4.5.tar.xz ... OK Building package gstreamer1-1.4.5-x86_64-1_SBo.tgz ... OK Installing package gstreamer1-1.4.5-x86_64-1_SBo.tgz ... OK gst1-plugins-base: MD5SUM check for gst-plugins-base-1.4.5.tar.xz ... OK Building package gst1-plugins-base-1.4.5-x86_64-1_SBo.tgz ... OK Installing package gst1-plugins-base-1.4.5-x86_64-1_SBo.tgz ... OK webkitgtk: MD5SUM check for webkitgtk-2.4.9.tar.xz ... OK Building package webkitgtk-2.4.9-x86_64-1_SBo.tgz ... OK Installing package webkitgtk-2.4.9-x86_64-1_SBo.tgz ... OK goffice0.8: MD5SUM check for goffice-0.8.17.tar.xz ... OK Building package goffice0.8-0.8.17-x86_64-2_SBo.tgz ... OK Installing package goffice0.8-0.8.17-x86_64-2_SBo.tgz ... OK libgnomecanvas: MD5SUM check for libgnomecanvas-2.30.3.tar.bz2 ... OK Building package libgnomecanvas-2.30.3-x86_64-1_SBo.tgz ... OK Installing package libgnomecanvas-2.30.3-x86_64-1_SBo.tgz ... OK libofx: MD5SUM check for libofx-0.9.9.tar.gz ... OK Building package libofx-0.9.9-x86_64-1_SBo.tgz ... OK Installing package libofx-0.9.9-x86_64-1_SBo.tgz ... OK gnucash: MD5SUM check for gnucash-2.6.6.tar.bz2 ... OK Building package gnucash-2.6.6-x86_64-1_SBo.tgz ... OK Installing package gnucash-2.6.6-x86_64-1_SBo.tgz ... OK did you forgot to install one of the deps or did you try it on -current? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From slack.dhabyx at gmail.com Sun Dec 27 22:59:34 2015 From: slack.dhabyx at gmail.com (Dhaby Xiloj) Date: Sun, 27 Dec 2015 16:59:34 -0600 Subject: [Slackbuilds-users] sshfs-fuse has changed links Message-ID: <56806D56.1060109@gmail.com> Hello, sshfs-fuse project has moved on from sourceforge to github. New links are: HOMEPAGE: https://github.com/libfuse/sshfs DOWNLOAD: https://github.com/libfuse/sshfs/releases/download/sshfs_2_5/sshfs-fuse-2.5.tar.gz -- Dhaby Xiloj From willysr at slackbuilds.org Mon Dec 28 00:22:38 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 28 Dec 2015 07:22:38 +0700 Subject: [Slackbuilds-users] sshfs-fuse has changed links In-Reply-To: <56806D56.1060109@gmail.com> References: <56806D56.1060109@gmail.com> Message-ID: <568080CE.8060901@slackbuilds.org> > sshfs-fuse project has moved on from sourceforge to github. > > New links are: > HOMEPAGE: https://github.com/libfuse/sshfs > DOWNLOAD: > https://github.com/libfuse/sshfs/releases/download/sshfs_2_5/sshfs-fuse-2.5.tar.gz Fixed in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lksj at yandex.ru Mon Dec 28 09:34:30 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Mon, 28 Dec 2015 12:34:30 +0300 Subject: [Slackbuilds-users] fim updated in upstream Message-ID: <6359751451295270@web19j.yandex.ru> An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Dec 28 10:07:02 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 28 Dec 2015 17:07:02 +0700 Subject: [Slackbuilds-users] fim updated in upstream In-Reply-To: <6359751451295270@web19j.yandex.ru> References: <6359751451295270@web19j.yandex.ru> Message-ID: <568109C6.1070804@slackbuilds.org> > Hello. > I try install fim > http://slackbuilds.org/repository/14.1/graphics/fim/?search=fim > and md5sum don't match. > In upstream tarboll date is 27 Dec 2015 - yesterday. > Something has changed. 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 lksj at yandex.ru Mon Dec 28 10:22:05 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Mon, 28 Dec 2015 13:22:05 +0300 Subject: [Slackbuilds-users] fim updated in upstream In-Reply-To: <568109C6.1070804@slackbuilds.org> References: <6359751451295270@web19j.yandex.ru> <568109C6.1070804@slackbuilds.org> Message-ID: <3435911451298125@web1g.yandex.ru> Hm... Version number not changed but checksum and date changed. This is strange. This update tarball or compromised? I doubt. 28.12.2015, 13:07, "Willy Sudiarto Raharjo" : >> ?Hello. >> ?I try install fim >> ?http://slackbuilds.org/repository/14.1/graphics/fim/?search=fim >> ?and md5sum don't match. >> ?In upstream tarboll date is 27 Dec 2015 - yesterday. >> ?Something has changed. > > Fixed in my branch > > -- > Willy Sudiarto Raharjo > > , > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ -- ? ?????????, ?.????????? From matteo.bernardini at gmail.com Mon Dec 28 10:29:56 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 28 Dec 2015 11:29:56 +0100 Subject: [Slackbuilds-users] fim updated in upstream In-Reply-To: <3435911451298125@web1g.yandex.ru> References: <6359751451295270@web19j.yandex.ru> <568109C6.1070804@slackbuilds.org> <3435911451298125@web1g.yandex.ru> Message-ID: 2015-12-28 11:22 GMT+01:00 ????????? ??????? : > Hm... Version number not changed but checksum and date changed. > This is strange. > This update tarball or compromised? > I doubt. > > 28.12.2015, 13:07, "Willy Sudiarto Raharjo" : >>> Hello. >>> I try install fim >>> http://slackbuilds.org/repository/14.1/graphics/fim/?search=fim >>> and md5sum don't match. >>> In upstream tarboll date is 27 Dec 2015 - yesterday. >>> Something has changed. >> >> Fixed in my branch that, judging by the name, is most probably a snapshot from trunk: to avoid changing again maybe the best solution would be to self host it. Matteo From willysr at slackbuilds.org Mon Dec 28 10:46:27 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 28 Dec 2015 17:46:27 +0700 Subject: [Slackbuilds-users] fim updated in upstream In-Reply-To: References: <6359751451295270@web19j.yandex.ru> <568109C6.1070804@slackbuilds.org> <3435911451298125@web1g.yandex.ru> Message-ID: <56811303.8030400@slackbuilds.org> > that, judging by the name, is most probably a snapshot from trunk: to > avoid changing again maybe the best solution would be to self host it. Yes, self-host it on slackbuildsdirectlinks SF project -- 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 lksj at yandex.ru Mon Dec 28 12:04:12 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Mon, 28 Dec 2015 15:04:12 +0300 Subject: [Slackbuilds-users] fim updated in upstream In-Reply-To: References: <6359751451295270@web19j.yandex.ru> <568109C6.1070804@slackbuilds.org> <3435911451298125@web1g.yandex.ru> Message-ID: <1773051451304252@web2o.yandex.ru> >that, judging by the name, is most probably a snapshot from trunk: Is it unstable version? I not found links to the stable release. -- ? ?????????, ?.????????? From matteo.bernardini at gmail.com Mon Dec 28 12:08:10 2015 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 28 Dec 2015 13:08:10 +0100 Subject: [Slackbuilds-users] fim updated in upstream In-Reply-To: <1773051451304252@web2o.yandex.ru> References: <6359751451295270@web19j.yandex.ru> <568109C6.1070804@slackbuilds.org> <3435911451298125@web1g.yandex.ru> <1773051451304252@web2o.yandex.ru> Message-ID: 2015-12-28 13:04 GMT+01:00 ????????? ??????? : >>that, judging by the name, is most probably a snapshot from trunk: > Is it unstable version? > I not found links to the stable release. maybe you should ask the maintainer: I'll put him in cc. Matteo From lksj at yandex.ru Mon Dec 28 12:12:43 2015 From: lksj at yandex.ru (=?koi8-r?B?68HSwcLBzs/XIOHMxcvTxco=?=) Date: Mon, 28 Dec 2015 15:12:43 +0300 Subject: [Slackbuilds-users] fim updated in upstream In-Reply-To: References: <6359751451295270@web19j.yandex.ru> <568109C6.1070804@slackbuilds.org> <3435911451298125@web1g.yandex.ru> <1773051451304252@web2o.yandex.ru> Message-ID: <1821041451304763@web2o.yandex.ru> I hoped that he will read. 28.12.2015, 15:08, "Matteo Bernardini" : > 2015-12-28 13:04 GMT+01:00 ????????? ??????? : >>> that, judging by the name, is most probably a snapshot from trunk: >> ?Is it unstable version? >> ?I not found links to the stable release. > > maybe you should ask the maintainer: I'll put him in cc. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ -- ? ?????????, ?.????????? From stormtracknole at gmail.com Mon Dec 28 17:26:50 2015 From: stormtracknole at gmail.com (stormtracknole) Date: Mon, 28 Dec 2015 11:26:50 -0600 Subject: [Slackbuilds-users] New maintainer for mlt Message-ID: Greetings List! I am the current maintainer for mlt mainly because I wanted to build kdenlive at the time several years ago. However, I don't directly use mlt. I mainly needed it as a dependency. So, I really need to give this up to someone that can give it the proper attention. Anybody interested? -stn -------------- next part -------------- An HTML attachment was scrubbed... URL: From chuangtzu.forum at yahoo.com Mon Dec 28 20:36:04 2015 From: chuangtzu.forum at yahoo.com (ChuangTzu) Date: Mon, 28 Dec 2015 15:36:04 -0500 Subject: [Slackbuilds-users] gnucash will not build without geoclue In-Reply-To: References: Message-ID: <56819D34.7010700@yahoo.com> Hello Willy, That is interesting, when I tried to build it on two different boxes with Slackware64-14.1 and Slackware 14.1, it would fail at libgeoclue (if I remember correctly), all other depends were installed with sbopkg as well. I will try again without geoclue and see if it works. Strange that it would require geoclue. Regards. slackbuilds-users-request at slackbuilds.org wrote: > Message: 3 Date: Sun, 27 Dec 2015 11:16:55 +0700 From: Willy Sudiarto > Raharjo To: > slackbuilds-users at slackbuilds.org Subject: Re: [Slackbuilds-users] > gnucash will not build without geoclue Message-ID: > <567F6637.9080400 at slackbuilds.org> Content-Type: text/plain; > charset="windows-1252" >> >geoclue is listed as an optional dependency for webkitgtk, however, >> >gnucash will not build without it. Perhaps it can be listed as a >> >dependency for gnucash? > I just tested on slackware64-14.1 and build it using sbopkg and it works > fine without geoclue: > > libwebp: > MD5SUM check for libwebp-0.4.3.tar.gz ... OK > Building package libwebp-0.4.3-x86_64-1_SBo.tgz ... OK > Installing package libwebp-0.4.3-x86_64-1_SBo.tgz ... OK > > orc: > MD5SUM check for orc-0.4.23.tar.xz ... OK > Building package orc-0.4.23-x86_64-1_SBo.tgz ... OK > Installing package orc-0.4.23-x86_64-1_SBo.tgz ... OK > > gstreamer1: > MD5SUM check for gstreamer-1.4.5.tar.xz ... OK > Building package gstreamer1-1.4.5-x86_64-1_SBo.tgz ... OK > Installing package gstreamer1-1.4.5-x86_64-1_SBo.tgz ... OK > > gst1-plugins-base: > MD5SUM check for gst-plugins-base-1.4.5.tar.xz ... OK > Building package gst1-plugins-base-1.4.5-x86_64-1_SBo.tgz ... OK > Installing package gst1-plugins-base-1.4.5-x86_64-1_SBo.tgz ... OK > > webkitgtk: > MD5SUM check for webkitgtk-2.4.9.tar.xz ... OK > Building package webkitgtk-2.4.9-x86_64-1_SBo.tgz ... OK > Installing package webkitgtk-2.4.9-x86_64-1_SBo.tgz ... OK > > goffice0.8: > MD5SUM check for goffice-0.8.17.tar.xz ... OK > Building package goffice0.8-0.8.17-x86_64-2_SBo.tgz ... OK > Installing package goffice0.8-0.8.17-x86_64-2_SBo.tgz ... OK > > libgnomecanvas: > MD5SUM check for libgnomecanvas-2.30.3.tar.bz2 ... OK > Building package libgnomecanvas-2.30.3-x86_64-1_SBo.tgz ... OK > Installing package libgnomecanvas-2.30.3-x86_64-1_SBo.tgz ... OK > > libofx: > MD5SUM check for libofx-0.9.9.tar.gz ... OK > Building package libofx-0.9.9-x86_64-1_SBo.tgz ... OK > Installing package libofx-0.9.9-x86_64-1_SBo.tgz ... OK > > gnucash: > MD5SUM check for gnucash-2.6.6.tar.bz2 ... OK > Building package gnucash-2.6.6-x86_64-1_SBo.tgz ... OK > Installing package gnucash-2.6.6-x86_64-1_SBo.tgz ... OK > > did you forgot to install one of the deps or did you try it on -current? > From arkadiusz at drabczyk.org Mon Dec 28 20:42:08 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Mon, 28 Dec 2015 20:42:08 +0000 (UTC) Subject: [Slackbuilds-users] [PATCH] development/global: Updated for version 6.5.2 References: Message-ID: On 2015-12-20, Arkadiusz Drabczyk wrote: > We have 6.2.5 and the newest stable version is 6.5.2. The main > difference between these two versions is that in 6.5.2 a new > GTAGSLABEL called `pygments' is added to gtags.conf and it's needed > for Python support. > FWIW it's enough to change a download link and version string. I attach a patch. >8------------------------------------------------------8< --- development/global/global.SlackBuild | 2 +- development/global/global.info | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) mode change 100644 => 100755 development/global/global.SlackBuild diff --git a/development/global/global.SlackBuild b/development/global/global.SlackBuild old mode 100644 new mode 100755 index fa45f58..a3ca767 --- a/development/global/global.SlackBuild +++ b/development/global/global.SlackBuild @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=global -VERSION=${VERSION:-6.2.5} +VERSION=${VERSION:-6.5.2} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff --git a/development/global/global.info b/development/global/global.info index 9caf3d9..ff72fce 100644 --- a/development/global/global.info +++ b/development/global/global.info @@ -1,8 +1,8 @@ PRGNAM="global" -VERSION="6.2.5" +VERSION="6.5.2" HOMEPAGE="http://www.gnu.org/software/global/" -DOWNLOAD="http://tamacom.com/global/global-6.2.5.tar.gz" -MD5SUM="38728f942e048a1ba22043d482caf2f2" +DOWNLOAD="http://tamacom.com/global/global-6.5.2.tar.gz" +MD5SUM="c154bc9ba77e7630068e2916cb9531c5" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -- 2.3.5 -- Arkadiusz Drabczyk From willysr at slackbuilds.org Tue Dec 29 04:59:57 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 29 Dec 2015 11:59:57 +0700 Subject: [Slackbuilds-users] gnucash will not build without geoclue In-Reply-To: <56819D34.7010700@yahoo.com> References: <56819D34.7010700@yahoo.com> Message-ID: <5682134D.9040204@slackbuilds.org> > That is interesting, when I tried to build it on two different boxes > with Slackware64-14.1 and Slackware 14.1, it would fail at libgeoclue > (if I remember correctly), all other depends were installed with sbopkg > as well. > > I will try again without geoclue and see if it works. Strange that it > would require geoclue. I tested this on a clean VM probably your machine have other SBo packages that relies on geoclue? -- 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 rworkman at slackbuilds.org Tue Dec 29 05:18:41 2015 From: rworkman at slackbuilds.org (Robby Workman) Date: Mon, 28 Dec 2015 23:18:41 -0600 Subject: [Slackbuilds-users] gnucash will not build without geoclue In-Reply-To: <5682134D.9040204@slackbuilds.org> References: <56819D34.7010700@yahoo.com> <5682134D.9040204@slackbuilds.org> Message-ID: <20151228231841.40520800@home.rlworkman.net> On Tue, 29 Dec 2015 11:59:57 +0700 Willy Sudiarto Raharjo wrote: > > That is interesting, when I tried to build it on two different boxes > > with Slackware64-14.1 and Slackware 14.1, it would fail at > > libgeoclue (if I remember correctly), all other depends were > > installed with sbopkg as well. > > > > I will try again without geoclue and see if it works. Strange that > > it would require geoclue. > > I tested this on a clean VM > probably your machine have other SBo packages that relies on geoclue? Yep, check the other things that gnucash is trying to link, and you'll find that one of them is linked to geoclue. Something like this will help: for file in $(find /usr/lib64 -type f -name "*.so.*" -print) ; do \ objdump -p $file | grep -q -E NEEDED.*geoclue && \ printf "$file links geoclue\n" ; done -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Dec 30 01:47:32 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 30 Dec 2015 08:47:32 +0700 Subject: [Slackbuilds-users] development/global should be updated In-Reply-To: References: Message-ID: <568337B4.2010507@slackbuilds.org> > We have 6.2.5 and the newest stable version is 6.5.2. The main > difference between these two versions is that in 6.5.2 a new > GTAGSLABEL called `pygments' is added to gtags.conf and it's needed > for Python support. you might want to contact the maintainer and if he doesn't reply back within a reasonable timeframe (give it 1-2 weeks), then please step up as a new maintainer and submit it via submission form. -- 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 mjjzf at syntaktisk.dk Wed Dec 30 10:31:03 2015 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Wed, 30 Dec 2015 11:31:03 +0100 Subject: [Slackbuilds-users] Fw: FocusWriter SlackBuild update Message-ID: <20151230113103.366a5634@espero.syntaktisk.dk> I have tried to contact the maintainer on his registered email with this update without getting an answer. All the best, Morten Begin forwarded message: Date: Fri, 11 Dec 2015 19:17:14 +0100 From: Morten Juhl-Johansen Z?lde-Fej?r To: giuseppe at osgate.org Subject: FocusWriter SlackBuild update Dear Guiseppe Scalzi - Just a note - I modified your SlackBuild of FocusWriter: http://slackbuilds.org/repository/14.1/office/focuswriter/?search=focuswriter - to the latest version 1.5.5. It works flawlessly, and I merely changed version, download path and checksum. From my own use case, the changes are minor, but it may be of interest to you - I attach it, in case you want to submit the update. All the best, Morten -------------- next part -------------- A non-text attachment was scrubbed... Name: focuswriter.tar.gz Type: application/x-gzip Size: 2473 bytes Desc: not available URL: From willysr at slackbuilds.org Wed Dec 30 10:49:06 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 30 Dec 2015 17:49:06 +0700 Subject: [Slackbuilds-users] Fw: FocusWriter SlackBuild update In-Reply-To: <20151230113103.366a5634@espero.syntaktisk.dk> References: <20151230113103.366a5634@espero.syntaktisk.dk> Message-ID: <5683B6A2.1000104@slackbuilds.org> > I have tried to contact the maintainer on his registered email with this > update without getting an answer. Hi if you don't mind, please use the submission form to submit an update and take maintainership of this package if you are going to maintain it 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 mjjzf at syntaktisk.dk Wed Dec 30 12:02:17 2015 From: mjjzf at syntaktisk.dk (Morten Juhl-Johansen =?ISO-8859-1?Q?Z=F6lde-Fej=E9r?=) Date: Wed, 30 Dec 2015 13:02:17 +0100 Subject: [Slackbuilds-users] Fw: FocusWriter SlackBuild update In-Reply-To: <5683B6A2.1000104@slackbuilds.org> References: <20151230113103.366a5634@espero.syntaktisk.dk> <5683B6A2.1000104@slackbuilds.org> Message-ID: <20151230130217.47125273@espero.syntaktisk.dk> On Wed, 30 Dec 2015 17:49:06 +0700 Willy Sudiarto Raharjo wrote: > > I have tried to contact the maintainer on his registered email with > > this update without getting an answer. > > > Hi > > if you don't mind, please use the submission form to submit an update > and take maintainership of this package if you are going to maintain > it > > thanks Of course I will if necessary, but I just wanted to post it here, in case the maintainer has not received my initial emails. All the best, Morten From arkadiusz at drabczyk.org Wed Dec 30 12:06:51 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Wed, 30 Dec 2015 12:06:51 +0000 (UTC) Subject: [Slackbuilds-users] development/global should be updated References: <568337B4.2010507@slackbuilds.org> Message-ID: On 2015-12-30, Willy Sudiarto Raharjo wrote: >> We have 6.2.5 and the newest stable version is 6.5.2. The main >> difference between these two versions is that in 6.5.2 a new >> GTAGSLABEL called `pygments' is added to gtags.conf and it's needed >> for Python support. > > you might want to contact the maintainer and if he doesn't reply back > within a reasonable timeframe (give it 1-2 weeks), then please step up > as a new maintainer and submit it via submission form. ok, I just thought that a maintainer of this package reads this mailing list. Ok, I will contact him directly. -- Arkadiusz Drabczyk From zhu.qunying at gmail.com Wed Dec 30 17:03:11 2015 From: zhu.qunying at gmail.com (Qun-Ying) Date: Wed, 30 Dec 2015 09:03:11 -0800 Subject: [Slackbuilds-users] development/global should be updated In-Reply-To: References: <568337B4.2010507@slackbuilds.org> Message-ID: feel free to take over the package -------------- next part -------------- An HTML attachment was scrubbed... URL: From arkadiusz at drabczyk.org Wed Dec 30 19:24:03 2015 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Wed, 30 Dec 2015 19:24:03 +0000 (UTC) Subject: [Slackbuilds-users] development/global should be updated References: <568337B4.2010507@slackbuilds.org> Message-ID: On 2015-12-30, Qun-Ying wrote: > feel free to take over the package ok, so I am a maintainer of develop/global since today -- Arkadiusz Drabczyk From chuangtzu.forum at yahoo.com Wed Dec 30 23:56:02 2015 From: chuangtzu.forum at yahoo.com (ChuangTzu) Date: Wed, 30 Dec 2015 18:56:02 -0500 Subject: [Slackbuilds-users] ede desktop needs correct source link for edelib In-Reply-To: References: Message-ID: <56846F12.8040501@yahoo.com> correct link for edelib: http://sourceforge.net/projects/ede/files/edelib/2.1/edelib-2.1.tar.gz/download From willysr at slackbuilds.org Thu Dec 31 00:37:42 2015 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 31 Dec 2015 07:37:42 +0700 Subject: [Slackbuilds-users] ede desktop needs correct source link for edelib In-Reply-To: <56846F12.8040501@yahoo.com> References: <56846F12.8040501@yahoo.com> Message-ID: <568478D6.1090701@slackbuilds.org> > correct link for edelib: > http://sourceforge.net/projects/ede/files/edelib/2.1/edelib-2.1.tar.gz/download Fixed it on my branch, but with different source URL as sf is not properly redirecting -- 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 Thu Dec 31 08:59:12 2015 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 31 Dec 2015 08:59:12 +0000 Subject: [Slackbuilds-users] Syncthing init script on SBo runs as root - security risk? In-Reply-To: References: Message-ID: <5684EE60.5010102@open-t.co.uk> On 31/12/15 08:45, henkjan gersen wrote: Hi Henkjan, > The current version of Syncthing on SBo installs an init script that > runs the daemon as root, which seems a security risk to me and goes > against the advice on the Syncthing wiki: > http://docs.syncthing.net/users/autostart.html#run-independent-of-user-login > > There was a thread on the mailing-list in June with patches that run > Syncthing as an unprivileged user, see > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-June/014347.html It was I who submitted those suggestions and patches > > > Those patches seem sensible for a situation that where it runs as a > system daemon and hence appear to be a safer default. Only minor > mistake appears to be the mention of "Exim" in the suggested group add > command. Thanks for catching that > > Any progress on fixing this or is it intentional that it runs as root? I was told at the time that the maintainer should approve the changes. I tried contacting the maintainer, but never heard anything back I'm afraid. From h.gersen at gmail.com Thu Dec 31 08:45:30 2015 From: h.gersen at gmail.com (henkjan gersen) Date: Thu, 31 Dec 2015 08:45:30 +0000 Subject: [Slackbuilds-users] Syncthing init script on SBo runs as root - security risk? Message-ID: The current version of Syncthing on SBo installs an init script that runs the daemon as root, which seems a security risk to me and goes against the advice on the Syncthing wiki: http://docs.syncthing.net/users/autostart.html#run-independent-of-user-login There was a thread on the mailing-list in June with patches that run Syncthing as an unprivileged user, see http://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-June/014347.html Those patches seem sensible for a situation that where it runs as a system daemon and hence appear to be a safer default. Only minor mistake appears to be the mention of "Exim" in the suggested group add command. Any progress on fixing this or is it intentional that it runs as root? btw) the package is also relatively outdated with Syncthing at 0.12.10 vs 0.11.10 on SBo. Best wishes, Henkjan Gersen -------------- next part -------------- An HTML attachment was scrubbed... URL: