From atelszewski at gmail.com Sat Apr 2 12:09:42 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 2 Apr 2016 14:09:42 +0200 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56EFB34D.3010805@mos6581.de> References: <56EF18AE.8010209@gmail.com> <56EF40FC.2010309@slackbuilds.org> <56EFA68A.3060408@gmail.com> <56EFB34D.3010805@mos6581.de> Message-ID: <56FFB686.3000406@gmail.com> On 21/03/16 09:39, Marcel Saegebarth wrote: > On 03/21/2016 08:45 AM, Andrzej Telszewski wrote: >> Easy or not, as you can see from the snippet I sent you, 0.40 is the >> best version to use. Keep in mind that it is a backup software. > > But if it doesn't build on Slackware 14.2, it would be dropped > anyway and mounting the attic archives wouldn't work anymore also. > It builds, it just doesn't work ;) Marcel, you can take over llfuse maintenance. For the moment, I'm going to stick with version 0.40 and in the long run I'm gonna try to bundle llfuse together with attic (or rather borgbackup). -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Sat Apr 2 12:16:03 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 2 Apr 2016 14:16:03 +0200 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56EFB7D6.5030204@slackbuilds.org> References: <56EF18AE.8010209@gmail.com> <56EF40FC.2010309@slackbuilds.org> <56EFA68A.3060408@gmail.com> <56EFB7D6.5030204@slackbuilds.org> Message-ID: <56FFB803.1070201@gmail.com> On 21/03/16 09:59, Willy Sudiarto Raharjo wrote: > here's what in borg's source code > llfuse<2.0 I have looked at version 1.0.0 of borg (stable) and this is what it says: extras_require = { # llfuse 0.40 (tested, proven, ok), needs FUSE version >= 2.8.0 # llfuse 0.41 (tested shortly, looks ok), needs FUSE version >= 2.8.0 # llfuse 0.42 (tested shortly, looks ok), needs FUSE version >= 2.8.0 # llfuse 1.0 will break API 'fuse': ['llfuse<1.0', ], } so clearly the best llfuse version to be used is 0.40. -- Best regards, Andrzej Telszewski From sbolokanov at abv.bg Sun Apr 3 14:57:33 2016 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvSDQkdC+0LvQvtC60LDQvdC+0LI=?=) Date: Sun, 3 Apr 2016 17:57:33 +0300 (EEST) Subject: [Slackbuilds-users] Dunst update Message-ID: <2102898424.195890.1459695453205.JavaMail.apache@nm52.abv.bg> Added don't clobber config and info update: https://github.com/sbolokanov/sbo-clone/commit/646aa48705212f08855746b59b7ec928c8bd4490 -- ????? ????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at mos6581.de Sun Apr 3 20:03:51 2016 From: marc at mos6581.de (Marcel Saegebarth) Date: Sun, 3 Apr 2016 22:03:51 +0200 Subject: [Slackbuilds-users] llfuse and attic In-Reply-To: <56FFB686.3000406@gmail.com> References: <56EF18AE.8010209@gmail.com> <56EF40FC.2010309@slackbuilds.org> <56EFA68A.3060408@gmail.com> <56EFB34D.3010805@mos6581.de> <56FFB686.3000406@gmail.com> Message-ID: <57017727.6010408@mos6581.de> On 04/02/2016 02:09 PM, Andrzej Telszewski wrote: > Marcel, you can take over llfuse maintenance. Thanks Andrzej. I'll take it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From info at microlinux.fr Tue Apr 5 10:04:19 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 5 Apr 2016 12:04:19 +0200 Subject: [Slackbuilds-users] VLC: broken URL for Blackmagic_Decklink_SDK Message-ID: <57038DA3.4010806@microlinux.fr> Hi, The download link for Blackmagic_DeckLink_SDK_10.1.4.zip is broken in the VLC SlackBuild. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Web : http://www.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 From willysr at slackbuilds.org Tue Apr 5 09:37:30 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 5 Apr 2016 16:37:30 +0700 Subject: [Slackbuilds-users] package for grab: sage In-Reply-To: <3995c5075873c4afab6eb2386c37cd30@posteo.de> References: <56F660A6.1080303@slackbuilds.org> <56F94181.2060602@grindcore.ch> <56F9425B.4040702@slackbuilds.org> <3995c5075873c4afab6eb2386c37cd30@posteo.de> Message-ID: <5703875A.5030201@slackbuilds.org> > I had some problems building Sage 7.1 as well (because of pynac) but > eventually > I could build and package it successfully, after tracking down and > removing the > following patch: > > build/pkgs/python2/patches/sys_path_security.patch Thanks pushed to my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Apr 5 10:06:16 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 5 Apr 2016 17:06:16 +0700 Subject: [Slackbuilds-users] VLC: broken URL for Blackmagic_Decklink_SDK In-Reply-To: <57038DA3.4010806@microlinux.fr> References: <57038DA3.4010806@microlinux.fr> Message-ID: <57038E18.9050204@slackbuilds.org> > The download link for Blackmagic_DeckLink_SDK_10.1.4.zip is broken in > the VLC SlackBuild. it has been fixed by Matteo 5 days ago in master branch http://ponce.cc/slackware/sources/repo/Blackmagic_DeckLink_SDK_10.1.4.zip -- 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 Tue Apr 5 10:08:59 2016 From: info at microlinux.fr (Nicolas Kovacs) Date: Tue, 5 Apr 2016 12:08:59 +0200 Subject: [Slackbuilds-users] VLC: broken URL for Blackmagic_Decklink_SDK In-Reply-To: <57038E18.9050204@slackbuilds.org> References: <57038DA3.4010806@microlinux.fr> <57038E18.9050204@slackbuilds.org> Message-ID: <57038EBB.8050807@microlinux.fr> Le 05/04/2016 12:06, Willy Sudiarto Raharjo a ?crit : > it has been fixed by Matteo 5 days ago in master branch > http://ponce.cc/slackware/sources/repo/Blackmagic_DeckLink_SDK_10.1.4.zip Thanks, Willy! -- 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 bgs at bgs.hu Wed Apr 6 13:07:07 2016 From: bgs at bgs.hu (=?UTF-8?B?Wm9sdMOhbiBQw7NzZmFp?=) Date: Wed, 6 Apr 2016 15:07:07 +0200 Subject: [Slackbuilds-users] bz2/gz mix-up in strongswan Message-ID: <570509FB.1030407@bgs.hu> Hi, I just tried to build strongswan, but it complained about a bad hash. Checking it, the cause turned out to be a mix-up of the tar.gz and tar.bz2 tarballs. Info has URL for tar.bz2 but hash for the tar.gz. Slackbuild has tar.bz2. Current (wrong) hash in to info file: c2a99ae6b0a9c2c50b59a9c9d31a629f strongswan-5.3.4.tar.gz What it should be: 655a632a515c74a99f2e9cc337ab2f33 strongswan-5.3.4.tar.bz2 Regards, Zolt?n From willysr at slackbuilds.org Wed Apr 6 14:30:07 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 6 Apr 2016 21:30:07 +0700 Subject: [Slackbuilds-users] bz2/gz mix-up in strongswan In-Reply-To: <570509FB.1030407@bgs.hu> References: <570509FB.1030407@bgs.hu> Message-ID: <57051D6F.3070602@slackbuilds.org> > I just tried to build strongswan, but it complained about a bad hash. > Checking it, the cause turned out to be a mix-up of the tar.gz and > tar.bz2 tarballs. > > Info has URL for tar.bz2 but hash for the tar.gz. > Slackbuild has tar.bz2. > > Current (wrong) hash in to info file: > c2a99ae6b0a9c2c50b59a9c9d31a629f strongswan-5.3.4.tar.gz > > What it should be: > 655a632a515c74a99f2e9cc337ab2f33 strongswan-5.3.4.tar.bz2 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 yavor at atanasov.us Wed Apr 6 22:46:55 2016 From: yavor at atanasov.us (Yavor Atanasov) Date: Wed, 06 Apr 2016 18:46:55 -0400 Subject: [Slackbuilds-users] alsa tools Message-ID: <2241171459982815@web28g.yandex.ru> Hello guys, I using sbo tools and I found that alsa-tools ver.1.0.29 has invalid download link. Here's the log: ============== Connecting to alsa.cybermirror.org (alsa.cybermirror.org)|85.13.133.184|:80... connected. HTTP request sent, awaiting response... 404 Not Found 2016-04-06 18:34:29 ERROR 404: Not Found. Unable to download/verify source file(s) for alsa-tools: Unable to wget http://alsa.cybermirror.org/firmware/alsa-firmware-1.0.29.tar.bz2. =========== The links from slackbuilds are dead too: https://slackbuilds.org/repository/14.1/audio/alsa-tools/ Thanks From willysr at slackbuilds.org Wed Apr 6 23:27:08 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 7 Apr 2016 06:27:08 +0700 Subject: [Slackbuilds-users] alsa tools In-Reply-To: <2241171459982815@web28g.yandex.ru> References: <2241171459982815@web28g.yandex.ru> Message-ID: <57059B4C.8090307@slackbuilds.org> > I using sbo tools and I found that alsa-tools ver.1.0.29 has invalid download link. Here's the log: > ============== > Connecting to alsa.cybermirror.org (alsa.cybermirror.org)|85.13.133.184|:80... connected. > HTTP request sent, awaiting response... 404 Not Found > 2016-04-06 18:34:29 ERROR 404: Not Found. > Unable to download/verify source file(s) for alsa-tools: > Unable to wget http://alsa.cybermirror.org/firmware/alsa-firmware-1.0.29.tar.bz2. > =========== > The links from slackbuilds are dead too: > https://slackbuilds.org/repository/14.1/audio/alsa-tools/ in master branch, it has been updated to 1.1.0 https://slackbuilds.org/cgit/slackbuilds/commit/?id=688d492a8ecc0f4d8d56b25ea9c07408e4190aaa 14.1 branch will receive less update since we are preparing for 14.2 -- 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 jgraha8 at gmail.com Wed Apr 6 23:32:52 2016 From: jgraha8 at gmail.com (Jason Graham) Date: Wed, 6 Apr 2016 19:32:52 -0400 Subject: [Slackbuilds-users] alsa tools In-Reply-To: <2241171459982815@web28g.yandex.ru> References: <2241171459982815@web28g.yandex.ru> Message-ID: Thanks Yavor. The top page says "Our Alsa mirror is undergoing maintenance right now and will be back shortly." I'd guess it would be rectified in the near future so you may try again later. Or grab it from a different mirror: http://ftp.osuosl.org/pub/blfs/conglomeration/alsa-firmware/alsa-firmware-1.0.29.tar.bz2 Best, Jason On Wed, Apr 6, 2016 at 6:46 PM, Yavor Atanasov wrote: > Hello guys, > I using sbo tools and I found that alsa-tools ver.1.0.29 has invalid > download link. Here's the log: > ============== > Connecting to alsa.cybermirror.org (alsa.cybermirror.org)|85.13.133.184|:80... > connected. > HTTP request sent, awaiting response... 404 Not Found > 2016-04-06 18:34:29 ERROR 404: Not Found. > Unable to download/verify source file(s) for alsa-tools: > Unable to wget > http://alsa.cybermirror.org/firmware/alsa-firmware-1.0.29.tar.bz2. > =========== > The links from slackbuilds are dead too: > https://slackbuilds.org/repository/14.1/audio/alsa-tools/ > > Thanks > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Apr 6 23:36:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 7 Apr 2016 06:36:53 +0700 Subject: [Slackbuilds-users] alsa tools In-Reply-To: <57059B4C.8090307@slackbuilds.org> References: <2241171459982815@web28g.yandex.ru> <57059B4C.8090307@slackbuilds.org> Message-ID: <57059D95.5010500@slackbuilds.org> >> I using sbo tools and I found that alsa-tools ver.1.0.29 has invalid download link. Here's the log: >> ============== >> Connecting to alsa.cybermirror.org (alsa.cybermirror.org)|85.13.133.184|:80... connected. >> HTTP request sent, awaiting response... 404 Not Found >> 2016-04-06 18:34:29 ERROR 404: Not Found. >> Unable to download/verify source file(s) for alsa-tools: >> Unable to wget http://alsa.cybermirror.org/firmware/alsa-firmware-1.0.29.tar.bz2. >> =========== >> The links from slackbuilds are dead too: >> https://slackbuilds.org/repository/14.1/audio/alsa-tools/ you may find it here ftp://ftp.alsa-project.org/pub/tools/alsa-tools-1.0.29.tar.bz2 ftp://ftp.alsa-project.org/pub/firmware/alsa-firmware-1.0.29.tar.bz2 -- 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 yavor at atanasov.us Wed Apr 6 23:37:40 2016 From: yavor at atanasov.us (Yavor Atanasov) Date: Wed, 06 Apr 2016 19:37:40 -0400 Subject: [Slackbuilds-users] alsa tools In-Reply-To: References: <2241171459982815@web28g.yandex.ru> Message-ID: <2300431459985860@web19m.yandex.ru> An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Fri Apr 8 15:17:12 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 8 Apr 2016 22:17:12 +0700 Subject: [Slackbuilds-users] OpenCV 3.1 Message-ID: <5707CB78.2090506@slackbuilds.org> Soon, opencv will be upgraded to 3.1 (right now it's in a separate branch for review). i have tried to make sure all packages that depends on opencv directly (hard dep) is working fine with the new update (vlc is still being tested by Christoph). if you are using packages that optionally depends on vlc, it would be good to try it as well. you can see the opencv changes in my branch opencv-3.1-review 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 Fri Apr 8 15:19:00 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 8 Apr 2016 22:19:00 +0700 Subject: [Slackbuilds-users] OpenCV 3.1 In-Reply-To: <5707CB78.2090506@slackbuilds.org> References: <5707CB78.2090506@slackbuilds.org> Message-ID: <5707CBE4.5090306@slackbuilds.org> > if you are using packages that optionally depends on vlc, it would be > good to try it as well. I mean depends on opencv -- 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 daniel.alayo at mykolab.ch Fri Apr 8 20:43:09 2016 From: daniel.alayo at mykolab.ch (Daniel Alayo) Date: Fri, 8 Apr 2016 22:43:09 +0200 Subject: [Slackbuilds-users] Bug in nvidia-driver slackbuild? Message-ID: <570817DD.8020005@mykolab.ch> Hello: This could just be me, I'm not very good at reading scripts. I trashed my installation of the nvidia-driver, so I had to review what were the installation scripts doing, and copy, delete or link files myself. I've noticed that the function nvidia_remove() in script nvidia-switch tries to remove the symlinks: /usr/lib/libvdpau-nvidia.so.1 /usr/lib64/libvdpau-nvidia.so.1 But if I'm not wrong, they're not created by the doinst.sh script of the nvidia-driver SlackBuild. Also, the doinst.sh script links libvdpau_nvidia.so.$NV_VERSION (notice the underscore), but script nvidia-switcht tries to delete symlinks libvdpau-nvidia.so.1 (notice the hyphen). I've never reported a bud in a slackbuild. If I've understood the instructions on https://www.slackbuilds.org/bugs/ well, the maintainer of the slackbuild should be reading this and then correcting it. If else, please do not be too hard on me... Thanks, "PreguntoYo" From kingbeowulf at gmail.com Sat Apr 9 01:08:02 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 8 Apr 2016 18:08:02 -0700 Subject: [Slackbuilds-users] Bug in nvidia-driver slackbuild? In-Reply-To: <570817DD.8020005@mykolab.ch> References: <570817DD.8020005@mykolab.ch> Message-ID: <570855F2.4010601@gmail.com> On 04/08/2016 01:43 PM, Daniel Alayo wrote: > Hello: > > This could just be me, I'm not very good at reading scripts. > > I trashed my installation of the nvidia-driver, so I had to review what > were the installation scripts doing, and copy, delete or link files myself. > > I've noticed that the function nvidia_remove() in script nvidia-switch > tries to remove the symlinks: > > /usr/lib/libvdpau-nvidia.so.1 > /usr/lib64/libvdpau-nvidia.so.1 > > But if I'm not wrong, they're not created by the doinst.sh script of the > nvidia-driver SlackBuild. > > Also, the doinst.sh script links libvdpau_nvidia.so.$NV_VERSION (notice > the underscore), but script nvidia-switcht tries to delete symlinks > libvdpau-nvidia.so.1 (notice the hyphen). > > I've never reported a bud in a slackbuild. If I've understood the > instructions on https://www.slackbuilds.org/bugs/ well, the maintainer > of the slackbuild should be reading this and then correcting it. If > else, please do not be too hard on me... > > Thanks, > "PreguntoYo" Are you using 14.1 slackbuild (version 352.63) or the experimental 14.2 SBo master branch - which i don't think is updated to the new driver yet - or the experimental version 361.42 I posted to this list as a link to a download location? I'll be updating for 14.2 this weekend. Thanks for the bug report. I'll check on it. Nvidia tends to rename libs willy-nilly, and I definitely need to increase the font size on these monitors ;-) -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 daniel.alayo at mykolab.ch Sun Apr 10 18:10:49 2016 From: daniel.alayo at mykolab.ch (Alayo, Daniel) Date: Sun, 10 Apr 2016 20:10:49 +0200 Subject: [Slackbuilds-users] Bug in nvidia-driver slackbuild? In-Reply-To: <570855F2.4010601@gmail.com> References: <570817DD.8020005@mykolab.ch> <570855F2.4010601@gmail.com> Message-ID: <3ef95daa5eb14a8bda653479fdc8bdfc@mykolab.ch> El 2016-04-09 03:08, King Beowulf escribi?: > On 04/08/2016 01:43 PM, Daniel Alayo wrote: >> Hello: >> >> This could just be me, I'm not very good at reading scripts. >> >> I trashed my installation of the nvidia-driver, so I had to review >> what >> were the installation scripts doing, and copy, delete or link files >> myself. >> >> I've noticed that the function nvidia_remove() in script nvidia-switch >> tries to remove the symlinks: >> >> /usr/lib/libvdpau-nvidia.so.1 >> /usr/lib64/libvdpau-nvidia.so.1 >> >> But if I'm not wrong, they're not created by the doinst.sh script of >> the >> nvidia-driver SlackBuild. >> >> Also, the doinst.sh script links libvdpau_nvidia.so.$NV_VERSION >> (notice >> the underscore), but script nvidia-switcht tries to delete symlinks >> libvdpau-nvidia.so.1 (notice the hyphen). >> >> I've never reported a bud in a slackbuild. If I've understood the >> instructions on https://www.slackbuilds.org/bugs/ well, the maintainer >> of the slackbuild should be reading this and then correcting it. If >> else, please do not be too hard on me... >> >> Thanks, >> "PreguntoYo" > > Are you using 14.1 slackbuild (version 352.63) or the experimental 14.2 > SBo master branch - which i don't think is updated to the new driver > yet > - or the experimental version 361.42 I posted to this list as a link to > a download location? > > I'll be updating for 14.2 this weekend. Thanks for the bug report. I'll > check on it. Nvidia tends to rename libs willy-nilly, and I definitely > need to increase the font size on these monitors ;-) > > -Ed > > > _______________________________________________ > 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/ Hello Ed: Thanks for reading my "bug" report. I've found this in the slackbuild for 14.1 (nvidia-driver version 352.63), the currently stable version of Slackware (sorry, I forgot to say this). I don't know if it has been there for previous versions of the nvidia-driver, or if it affects SlackBuilds-current also (is there a SlackBuilds-current?). I wonder if it has raised any problem in the use of the driver, of if it could have gone unnoticed indefinitely... Thanks. -- PreguntoYo From z.coldplayer at gmail.com Mon Apr 11 07:33:50 2016 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Mon, 11 Apr 2016 11:33:50 +0400 Subject: [Slackbuilds-users] bad url for spatialite-tools In-Reply-To: <56CF2B1F.90101@slackbuilds.org> References: <56CF2B1F.90101@slackbuilds.org> Message-ID: Hi, the website of spatialite has undergone a revamp. The source url has changed again. diff --git a/libraries/librasterlite/librasterlite.info b/libraries/librasterlite/librasterlite.info$ index 12310e6..447a91d 100644$ --- a/libraries/librasterlite/librasterlite.info$ +++ b/libraries/librasterlite/librasterlite.info$ @@ -1,7 +1,7 @@$ PRGNAM="librasterlite"$ VERSION="1.1g"$ HOMEPAGE="https://www.gaia-gis.it/fossil/librasterlite/index"$ -DOWNLOAD=" http://www.gaia-gis.it/librasterlite-sources/gaia-sins/librasterlite-1.1g.tar.gz "$ +DOWNLOAD="http://www.gaia-gis.it/gaia-sins/librasterlite-1.1g.tar.gz"$ MD5SUM="6c6e8f83ac8a06c78f3fdcee63dc5e3e"$ DOWNLOAD_x86_64=""$ MD5SUM_x86_64=""$ diff --git a/libraries/libspatialite/libspatialite.info b/libraries/libspatialite/libspatialite.info$ index 1213d61..359559f 100644$ --- a/libraries/libspatialite/libspatialite.info$ +++ b/libraries/libspatialite/libspatialite.info$ @@ -1,7 +1,7 @@$ PRGNAM="libspatialite"$ VERSION="4.2.0"$ HOMEPAGE="https://www.gaia-gis.it/fossil/libspatialite/index"$ -DOWNLOAD=" http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-sources/libspatialite-4.2.0.tar.gz "$ +DOWNLOAD=" http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz "$ MD5SUM="83305ed694a77152120d1f74c5151779"$ DOWNLOAD_x86_64=""$ MD5SUM_x86_64=""$ diff --git a/libraries/readosm/readosm.info b/libraries/readosm/readosm.info $ index 5969d64..c67964a 100644$ --- a/libraries/readosm/readosm.info$ +++ b/libraries/readosm/readosm.info$ @@ -1,7 +1,7 @@$ PRGNAM="readosm"$ VERSION="1.0.0d"$ HOMEPAGE="https://www.gaia-gis.it/fossil/readosm/index"$ -DOWNLOAD=" http://www.gaia-gis.it/readosm-sources/gaia-sins/readosm-1.0.0d.tar.gz"$ +DOWNLOAD=" http://www.gaia-gis.it/gaia-sins/readosm-sources/readosm-1.0.0d.tar.gz"$ MD5SUM="ba74b5141f115de5d240cf4a40478336"$ DOWNLOAD_x86_64=""$ MD5SUM_x86_64=""$ On 25 February 2016 at 20:26, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Sorry to bug in again but there are other sources who need to have their > > url corrected in the the Gaia-SINS federated projects home-page. > > > > diff --git a/academic/spatialite_gui/spatialite_gui.info > > b/academic/spatialite_gui/spatialite_gui.info > > index 817f539..02b1dff 100644 > > --- a/academic/spatialite_gui/spatialite_gui.info > > +++ b/academic/spatialite_gui/spatialite_gui.info > > @@ -1,7 +1,7 @@ > > PRGNAM="spatialite_gui" > > VERSION="1.7.1" > > HOMEPAGE="https://www.gaia-gis.it/fossil/spatialite_gui/index" > > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/spatialite_gui-1.7.1.tar.gz" > > +DOWNLOAD=" > > > http://www.gaia-gis.it/gaia-sins/spatialite-gui-sources/spatialite_gui-1.7.1.tar.gz > > " > > MD5SUM="c917f40810607784528b4db58cd36efb" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > diff --git a/libraries/librasterlite/librasterlite.info > > b/libraries/librasterlite/librasterlite.info > > index 447a91d..12310e6 100644 > > --- a/libraries/librasterlite/librasterlite.info > > +++ b/libraries/librasterlite/librasterlite.info > > @@ -1,7 +1,7 @@ > > PRGNAM="librasterlite" > > VERSION="1.1g" > > HOMEPAGE="https://www.gaia-gis.it/fossil/librasterlite/index" > > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/librasterlite-1.1g.tar.gz" > > +DOWNLOAD=" > > > http://www.gaia-gis.it/librasterlite-sources/gaia-sins/librasterlite-1.1g.tar.gz > > " > > MD5SUM="6c6e8f83ac8a06c78f3fdcee63dc5e3e" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > diff --git a/libraries/libspatialite/libspatialite.info > > b/libraries/libspatialite/libspatialite.info > > index 359559f..1213d61 100644 > > --- a/libraries/libspatialite/libspatialite.info > > +++ b/libraries/libspatialite/libspatialite.info > > @@ -1,7 +1,7 @@ > > PRGNAM="libspatialite" > > VERSION="4.2.0" > > HOMEPAGE="https://www.gaia-gis.it/fossil/libspatialite/index" > > -DOWNLOAD=" > > > http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz > > " > > +DOWNLOAD=" > > > http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-sources/libspatialite-4.2.0.tar.gz > > " > > MD5SUM="83305ed694a77152120d1f74c5151779" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > diff --git a/libraries/readosm/readosm.info b/libraries/readosm/ > readosm.info > > index 434f953..5969d64 100644 > > --- a/libraries/readosm/readosm.info > > +++ b/libraries/readosm/readosm.info > > @@ -1,7 +1,7 @@ > > PRGNAM="readosm" > > VERSION="1.0.0d" > > HOMEPAGE="https://www.gaia-gis.it/fossil/readosm/index" > > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/readosm-1.0.0d.tar.gz" > > +DOWNLOAD=" > > http://www.gaia-gis.it/readosm-sources/gaia-sins/readosm-1.0.0d.tar.gz" > > MD5SUM="ba74b5141f115de5d240cf4a40478336" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > > > I am using SBo-master on slackware-current. > > all applied to my branch > > Thanks > > > -- > 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/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.coldplayer at gmail.com Mon Apr 11 07:37:54 2016 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Mon, 11 Apr 2016 11:37:54 +0400 Subject: [Slackbuilds-users] bad url for spatialite-tools In-Reply-To: <56CF2B1F.90101@slackbuilds.org> References: <56CF2B1F.90101@slackbuilds.org> Message-ID: I visited the Gaia-SINS http://www.gaia-gis.it/gaia-sins/index.html websit. There are two Obsolete / Discontinued software [no longer maintained] :: libgaiagraphics sources a library supporting common-utility raster handling methods librasterlite sources a library allowing to store huge raster coverages within a SpatiaLite DBMS Would it be safe to continue to use these software in 14.2? PS: librasterlite has a new version:: librasterlite2 sources an advanced library supporting raster handling method On 25 February 2016 at 20:26, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Sorry to bug in again but there are other sources who need to have their > > url corrected in the the Gaia-SINS federated projects home-page. > > > > diff --git a/academic/spatialite_gui/spatialite_gui.info > > b/academic/spatialite_gui/spatialite_gui.info > > index 817f539..02b1dff 100644 > > --- a/academic/spatialite_gui/spatialite_gui.info > > +++ b/academic/spatialite_gui/spatialite_gui.info > > @@ -1,7 +1,7 @@ > > PRGNAM="spatialite_gui" > > VERSION="1.7.1" > > HOMEPAGE="https://www.gaia-gis.it/fossil/spatialite_gui/index" > > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/spatialite_gui-1.7.1.tar.gz" > > +DOWNLOAD=" > > > http://www.gaia-gis.it/gaia-sins/spatialite-gui-sources/spatialite_gui-1.7.1.tar.gz > > " > > MD5SUM="c917f40810607784528b4db58cd36efb" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > diff --git a/libraries/librasterlite/librasterlite.info > > b/libraries/librasterlite/librasterlite.info > > index 447a91d..12310e6 100644 > > --- a/libraries/librasterlite/librasterlite.info > > +++ b/libraries/librasterlite/librasterlite.info > > @@ -1,7 +1,7 @@ > > PRGNAM="librasterlite" > > VERSION="1.1g" > > HOMEPAGE="https://www.gaia-gis.it/fossil/librasterlite/index" > > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/librasterlite-1.1g.tar.gz" > > +DOWNLOAD=" > > > http://www.gaia-gis.it/librasterlite-sources/gaia-sins/librasterlite-1.1g.tar.gz > > " > > MD5SUM="6c6e8f83ac8a06c78f3fdcee63dc5e3e" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > diff --git a/libraries/libspatialite/libspatialite.info > > b/libraries/libspatialite/libspatialite.info > > index 359559f..1213d61 100644 > > --- a/libraries/libspatialite/libspatialite.info > > +++ b/libraries/libspatialite/libspatialite.info > > @@ -1,7 +1,7 @@ > > PRGNAM="libspatialite" > > VERSION="4.2.0" > > HOMEPAGE="https://www.gaia-gis.it/fossil/libspatialite/index" > > -DOWNLOAD=" > > > http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-4.2.0.tar.gz > > " > > +DOWNLOAD=" > > > http://www.gaia-gis.it/gaia-sins/libspatialite-sources/libspatialite-sources/libspatialite-4.2.0.tar.gz > > " > > MD5SUM="83305ed694a77152120d1f74c5151779" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > diff --git a/libraries/readosm/readosm.info b/libraries/readosm/ > readosm.info > > index 434f953..5969d64 100644 > > --- a/libraries/readosm/readosm.info > > +++ b/libraries/readosm/readosm.info > > @@ -1,7 +1,7 @@ > > PRGNAM="readosm" > > VERSION="1.0.0d" > > HOMEPAGE="https://www.gaia-gis.it/fossil/readosm/index" > > -DOWNLOAD="http://www.gaia-gis.it/gaia-sins/readosm-1.0.0d.tar.gz" > > +DOWNLOAD=" > > http://www.gaia-gis.it/readosm-sources/gaia-sins/readosm-1.0.0d.tar.gz" > > MD5SUM="ba74b5141f115de5d240cf4a40478336" > > DOWNLOAD_x86_64="" > > MD5SUM_x86_64="" > > > > I am using SBo-master on slackware-current. > > all applied to my branch > > Thanks > > > -- > 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/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Mon Apr 11 17:11:57 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 11 Apr 2016 20:11:57 +0300 Subject: [Slackbuilds-users] Ugene 1.22.0 Message-ID: Hello, I am trying to update my ugene Slackbuild for version 1.22.0 It builds fine, however when I try to start it, it gives the following error: bash-4.3$ ugene -ui This application failed to start because it could not find or load the Qt platform plugin "xcb". Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, wayland, xcb. Reinstalling the application may fix this problem. /usr/lib64/ugene/ugene: line 69: 3678 Aborted "$dirname/$appname" "${params[@]}" I build against ALienBob's QT5 (qt5-5.5.1-x86_64-5alien.txz ). Here's the build script: https://sourceforge.net/projects/sboppetrov/files/ugene/testing/ Any suggestions? Do you think it's an issue with the program itself, so I contact the developers? They proved to be very helpful before. regards, Petar -------------- next part -------------- An HTML attachment was scrubbed... URL: From artourter at gmail.com Mon Apr 11 17:37:49 2016 From: artourter at gmail.com (Greg' Ar Tourter) Date: Mon, 11 Apr 2016 18:37:49 +0100 Subject: [Slackbuilds-users] Ugene 1.22.0 In-Reply-To: References: Message-ID: no it is not an issue with the program nor the package. However, Alien's QT5 package was compiled with libxkbcommon, if you get the that package from SBo it should work. Hope this helps Greg On 11 April 2016 at 18:11, Petar Petrov wrote: > Hello, > > I am trying to update my ugene Slackbuild for version 1.22.0 > > It builds fine, however when I try to start it, it gives the following > error: > > bash-4.3$ ugene -ui > This application failed to start because it could not find or load the > Qt platform plugin "xcb". > > Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, > offscreen, wayland, xcb. > > Reinstalling the application may fix this problem. > /usr/lib64/ugene/ugene: line 69: 3678 Aborted > "$dirname/$appname" "${params[@]}" > > I build against ALienBob's QT5 (qt5-5.5.1-x86_64-5alien.txz > ). > Here's the build script: > > https://sourceforge.net/projects/sboppetrov/files/ugene/testing/ > > Any suggestions? > > Do you think it's an issue with the program itself, so I contact the > developers? They proved to be very helpful before. > > regards, > > Petar > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Mon Apr 11 21:15:53 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 12 Apr 2016 00:15:53 +0300 Subject: [Slackbuilds-users] Ugene 1.22.0 In-Reply-To: References: Message-ID: thank you for the clarification! -petar 2016-04-11 20:37 GMT+03:00 Greg' Ar Tourter : > no it is not an issue with the program nor the package. However, Alien's > QT5 package was compiled with libxkbcommon, if you get the that package > from SBo it should work. > > Hope this helps > > Greg > > On 11 April 2016 at 18:11, Petar Petrov wrote: > >> Hello, >> >> I am trying to update my ugene Slackbuild for version 1.22.0 >> >> It builds fine, however when I try to start it, it gives the following >> error: >> >> bash-4.3$ ugene -ui >> This application failed to start because it could not find or load the >> Qt platform plugin "xcb". >> >> Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, >> offscreen, wayland, xcb. >> >> Reinstalling the application may fix this problem. >> /usr/lib64/ugene/ugene: line 69: 3678 Aborted >> "$dirname/$appname" "${params[@]}" >> >> I build against ALienBob's QT5 (qt5-5.5.1-x86_64-5alien.txz >> ). >> Here's the build script: >> >> https://sourceforge.net/projects/sboppetrov/files/ugene/testing/ >> >> Any suggestions? >> >> Do you think it's an issue with the program itself, so I contact the >> developers? They proved to be very helpful before. >> >> regards, >> >> Petar >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> >> >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Apr 13 05:42:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 13 Apr 2016 12:42:27 +0700 Subject: [Slackbuilds-users] qt5 5.5.1 fails to build with multiple jobs In-Reply-To: References: <56E52C20.7070101@gmail.com> <56E53C77.10504@gmail.com> <56E53D25.6000801@slackbuilds.org> <56E55A90.70104@gmail.com> <56E5E9F7.8010706@slackbuilds.org> <56E83643.9080001@gmail.com> <56E85645.4080604@slackbuilds.org> Message-ID: <570DDC43.1090301@slackbuilds.org> > A recent mscore/musescore 2.0.2 also requires qt5, mscore 1.3 from SBo > is outdated. https://musescore.org/ it's now updated to 2.0.2 in my branch Klaatu: please let me know if you have objection this update and i will remove it -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From belka at caraus.de Thu Apr 14 06:59:04 2016 From: belka at caraus.de (Eugen Wissner) Date: Thu, 14 Apr 2016 08:59:04 +0200 Subject: [Slackbuilds-users] Remove hhvm-pgsql Message-ID: <1460617144.540.0.camel@caraus.de> Hello, hhvm-pgsql doesn't build against the last hhvm. Please remove hhvm- pgsql from master. Regards Eugene From matteo.bernardini at gmail.com Thu Apr 14 07:09:57 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 14 Apr 2016 09:09:57 +0200 Subject: [Slackbuilds-users] Remove hhvm-pgsql In-Reply-To: <1460617144.540.0.camel@caraus.de> References: <1460617144.540.0.camel@caraus.de> Message-ID: 2016-04-14 8:59 GMT+02:00 Eugen Wissner : > Hello, > > hhvm-pgsql doesn't build against the last hhvm. Please remove hhvm- > pgsql from master. committed in my branch. Matteo From willysr at slackbuilds.org Thu Apr 14 07:27:06 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 14 Apr 2016 14:27:06 +0700 Subject: [Slackbuilds-users] Remove hhvm-pgsql In-Reply-To: References: <1460617144.540.0.camel@caraus.de> Message-ID: <570F464A.2060303@slackbuilds.org> >> hhvm-pgsql doesn't build against the last hhvm. Please remove hhvm- >> pgsql from master. > > committed in my branch. have you tried the latest 3.12.0? it was released last February while the one in master was 3.11.0 from December 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 belka at caraus.de Thu Apr 14 07:32:25 2016 From: belka at caraus.de (Eugen Wissner) Date: Thu, 14 Apr 2016 09:32:25 +0200 Subject: [Slackbuilds-users] Remove hhvm-pgsql In-Reply-To: <570F464A.2060303@slackbuilds.org> References: <1460617144.540.0.camel@caraus.de> <570F464A.2060303@slackbuilds.org> Message-ID: <1460619145.540.10.camel@caraus.de> Yes, there was hhvm 3.13.0 and 3.13.1 already. hhvm-pgsql 3.12.0 doesn't build against it on current. There are also several issues on github about build problems on another linux distributions (although with other errors than I had). And even if it would build.. this extension is pretty useless imho since it misses a lot of functions from php- pgsql; I couldn't use it with Joomla and it doesn't work with Drupal so far I know. Does anybody actually use hhvm (It was a test by me, I switched again from Facebook's Hack to another language after it)? Eugene Am Donnerstag, den 14.04.2016, 14:27 +0700 schrieb Willy Sudiarto Raharjo: > > > > > > > > hhvm-pgsql doesn't build against the last hhvm. Please remove > > > hhvm- > > > pgsql from master. > > committed in my branch. > have you tried the latest 3.12.0? > it was released last February while the one in master was 3.11.0 from > December 11. > > > _______________________________________________ > 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 Thu Apr 14 09:32:01 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 14 Apr 2016 11:32:01 +0200 Subject: [Slackbuilds-users] Bug in nvidia-driver slackbuild? In-Reply-To: <570855F2.4010601@gmail.com> References: <570817DD.8020005@mykolab.ch> <570855F2.4010601@gmail.com> Message-ID: 2016-04-09 3:08 GMT+02:00 King Beowulf : > Are you using 14.1 slackbuild (version 352.63) or the experimental 14.2 > SBo master branch - which i don't think is updated to the new driver yet > - or the experimental version 361.42 I posted to this list as a link to > a download location? on SBo's master branch are available the versions also present here http://www.koenigcomputers.com/sbo-testing/14.2/system/ https://slackbuilds.org/cgit/slackbuilds/commit/?id=630b42da82e1e27a78739faabcb2d7dcd6efc77b I'll grab the occasion to reporta that there seems to be an issue with libGL linking to the libnvidia-tls library and not finding it (because it has been moved in a subdirectory?): this seems to manifest whenever building anything linking to libGL in a host with these latest drivers installed. Matteo From unix_lists at f-m.fm Fri Apr 15 01:21:26 2016 From: unix_lists at f-m.fm (unix_lists at f-m.fm) Date: Thu, 14 Apr 2016 20:21:26 -0500 Subject: [Slackbuilds-users] fvwm-crystal package on slackbuilds complains of missing files Message-ID: <1460683286.1474697.579321841.1CCE1048@webmail.messagingengine.com> hi, I'm trying to use fvwm-crystal but am running into issues. Just so you know, I'm using startx to open fvwm-crystal. I've linked to a screenshot. http://imgur.com/ILgrPSm As seen in the screenshot I can only get a terminal to open after completing the configuration that comes up the first time I ran xwmconfig and selected fvwm-crystal. And since I have to use ctrl-backspace to get out of the desktop, I saw there were two errors. The first complained that there wasn't the file DefaultDesktopManager under ~/.fvwm-crystal/preferences/. The second error is the following: [fvwm][READ]: <> file '/var/tmp/SBo/sbopkg.tqTYlb/package-fvwm-crystal/usr/bin/../share/fvwm-crystal/fvwm/recipes/Default' not found Regards, Donald Cooley From slackware at lemintown.eu Fri Apr 15 12:28:25 2016 From: slackware at lemintown.eu (Brian Lemin) Date: Fri, 15 Apr 2016 14:28:25 +0200 Subject: [Slackbuilds-users] Fwd: QuiteRSS Slackbuild In-Reply-To: <56F975A2.4060007@lemintown.eu> References: <56F975A2.4060007@lemintown.eu> Message-ID: <5710DE69.1090301@lemintown.eu> Hello, QuiteRSS slackbuild has not been updated for almost 2 years so I'd be glad to maintain it since I use it daily Have a nice week end, Brian -------- Forwarded Message -------- Subject: QuiteRSS Slackbuild Date: Mon, 28 Mar 2016 20:19:14 +0200 From: Brian Lemin To: andrew.maraev60 at yandex.ru Hello, Are you up for updating the QuiteRSS Slackbuild to the latest version? It built fine on a clean slack-14.1 In case you do not use QuiteRSS anymore I'd be glad to maitain the slackbuild. Regards, Brian From kingbeowulf at gmail.com Fri Apr 15 14:59:59 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 15 Apr 2016 07:59:59 -0700 Subject: [Slackbuilds-users] Bug in nvidia-driver slackbuild? In-Reply-To: References: <570817DD.8020005@mykolab.ch> <570855F2.4010601@gmail.com> Message-ID: <571101EF.4000701@gmail.com> On 04/14/2016 02:32 AM, Matteo Bernardini wrote: > 2016-04-09 3:08 GMT+02:00 King Beowulf : >> Are you using 14.1 slackbuild (version 352.63) or the experimental 14.2 >> SBo master branch - which i don't think is updated to the new driver yet >> - or the experimental version 361.42 I posted to this list as a link to >> a download location? > > on SBo's master branch are available the versions also present here > > http://www.koenigcomputers.com/sbo-testing/14.2/system/ > > https://slackbuilds.org/cgit/slackbuilds/commit/?id=630b42da82e1e27a78739faabcb2d7dcd6efc77b > > I'll grab the occasion to reporta that there seems to be an issue with > libGL linking to the libnvidia-tls library and not finding it (because > it has been moved in a subdirectory?): this seems to manifest whenever > building anything linking to libGL in a host with these latest drivers > installed. > > Matteo There are 2 versions of libnvidia-tls included in the nvidia proprietary blob. In the past, tls/libnvidia-tls was the one to use with Slackware. However something changed. For some programs, compile will fail where libGL can't find libnvidia-tls. there are two "libnvidia-tls" threading models, one in root of package and another in tls/. Issue seems to be wth use of tls/libnvidia-tls not being correct. There is a tool "tls_test" but I don't know what the exit codes mean. As a temporary fix, I added the one in packages root to /usr/lib$LIBDIRSUFFIX and the one in tls/ to /usr/lib$LIBDIRSUFFIX/tls but I don't think that is correct, so I haven't posted it yet. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Fri Apr 15 15:46:52 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 15 Apr 2016 17:46:52 +0200 Subject: [Slackbuilds-users] Bug in nvidia-driver slackbuild? In-Reply-To: <571101EF.4000701@gmail.com> References: <570817DD.8020005@mykolab.ch> <570855F2.4010601@gmail.com> <571101EF.4000701@gmail.com> Message-ID: 2016-04-15 16:59 GMT+02:00 King Beowulf : > On 04/14/2016 02:32 AM, Matteo Bernardini wrote: >> 2016-04-09 3:08 GMT+02:00 King Beowulf : >>> Are you using 14.1 slackbuild (version 352.63) or the experimental 14.2 >>> SBo master branch - which i don't think is updated to the new driver yet >>> - or the experimental version 361.42 I posted to this list as a link to >>> a download location? >> >> on SBo's master branch are available the versions also present here >> >> http://www.koenigcomputers.com/sbo-testing/14.2/system/ >> >> https://slackbuilds.org/cgit/slackbuilds/commit/?id=630b42da82e1e27a78739faabcb2d7dcd6efc77b >> >> I'll grab the occasion to reporta that there seems to be an issue with >> libGL linking to the libnvidia-tls library and not finding it (because >> it has been moved in a subdirectory?): this seems to manifest whenever >> building anything linking to libGL in a host with these latest drivers >> installed. >> >> Matteo > > There are 2 versions of libnvidia-tls included in the nvidia proprietary > blob. In the past, tls/libnvidia-tls was the one to use with Slackware. > However something changed. For some programs, compile will fail where > libGL can't find libnvidia-tls. > > there are two "libnvidia-tls" threading models, one in root of package > and another in tls/. Issue seems to be wth use of tls/libnvidia-tls not > being correct. There is a tool "tls_test" but I don't know what the > exit codes mean. > > As a temporary fix, I added the one in packages root to > /usr/lib$LIBDIRSUFFIX and the one in tls/ to /usr/lib$LIBDIRSUFFIX/tls > > but I don't think that is correct, so I haven't posted it yet. if you think it's better waiting for another version we can also revert that commit (together with the nvidia-kernel one): I took the versions you got in your webspace mistekenly thinking they were ready for prime time. but IMHO there's no hurry, the previous version still works fine here. Matteo From s.arcus at open-t.co.uk Sun Apr 17 08:55:44 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 17 Apr 2016 09:55:44 +0100 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current Message-ID: <57134F90.3070401@open-t.co.uk> Just a heads up that PTLib doesn't seem to compile any more on Slackware-current. I've tried to make sense of the error message below and googled, and it would appear it might be related to the version of Bison not supporting certain options any more - but I can't really make sense of things. I also tried the slightly newer ptlib-2.10.11. Then again, PTLib seems to have been last updated in 2013, so maybe it just won't compile on a modern system any more. If anybody has any hints, they are most welcome. ptlib/common/getdate.y: In function ?PTime_yyparse?: ptlib/common/getdate.y:105:38: error: ?parseParam? undeclared (first use in this function) #define VARIABLE ((struct Variables*)parseParam) ^ ptlib/common/getdate.y:158:6: note: in expansion of macro ?VARIABLE? VARIABLE->yyHaveTime++; ^ ptlib/common/getdate.y:105:38: note: each undeclared identifier is reported only once for each function it appears in #define VARIABLE ((struct Variables*)parseParam) ^ ptlib/common/getdate.y:158:6: note: in expansion of macro ?VARIABLE? VARIABLE->yyHaveTime++; ^ ptlib/common/getdate.y: In function ?PTimeParse?: ptlib/common/getdate.y:112:18: error: too many arguments to function ?PTime_yyparse? #define yyparse PTime_yyparse ^ ptlib/common/getdate.y:981:5: note: in expansion of macro ?yyparse? yyparse(&var); ^ ptlib/common/getdate.y:112:18: note: declared here #define yyparse PTime_yyparse ^ ptlib/common/getdate.tab.c:1161:1: note: in expansion of macro ?yyparse? yyparse (void) ^ Makefile:463: recipe for target '/tmp/SBo/ptlib-2.10.10/lib_linux_x86_64/obj/getdate.tab.o' failed make[2]: *** [/tmp/SBo/ptlib-2.10.10/lib_linux_x86_64/obj/getdate.tab.o] Error 1 make[2]: Leaving directory '/tmp/SBo/ptlib-2.10.10/src' ../make/common.mak:292: recipe for target 'optshared' failed make[1]: *** [optshared] Error 2 make[1]: Leaving directory '/tmp/SBo/ptlib-2.10.10/src' Makefile:91: recipe for target 'optshared' failed make: *** [optshared] Error 2 From s.arcus at open-t.co.uk Sun Apr 17 09:20:44 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 17 Apr 2016 10:20:44 +0100 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <57134F90.3070401@open-t.co.uk> References: <57134F90.3070401@open-t.co.uk> Message-ID: <5713556C.7080202@open-t.co.uk> On 17/04/16 09:55, Sebastian Arcus wrote: > Just a heads up that PTLib doesn't seem to compile any more on > Slackware-current. I've tried to make sense of the error message below > and googled, and it would appear it might be related to the version of > Bison not supporting certain options any more - but I can't really > make sense of things. I also tried the slightly newer ptlib-2.10.11. > Then again, PTLib seems to have been last updated in 2013, so maybe it > just won't compile on a modern system any more. If anybody has any > hints, they are most welcome. [Update] - After downloading the latest version from svn (2.16) it compiles and installs fine with the current SBo script on Slack -current. Now Ekiga won't compile any more against the new PTLib ... From willysr at slackbuilds.org Sun Apr 17 09:35:03 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Apr 2016 16:35:03 +0700 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <57134F90.3070401@open-t.co.uk> References: <57134F90.3070401@open-t.co.uk> Message-ID: <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> > Just a heads up that PTLib doesn't seem to compile any more on > Slackware-current. I've tried to make sense of the error message below > and googled, and it would appear it might be related to the version of > Bison not supporting certain options any more - but I can't really make > sense of things. I also tried the slightly newer ptlib-2.10.11. Then > again, PTLib seems to have been last updated in 2013, so maybe it just > won't compile on a modern system any more. If anybody has any hints, > they are most welcome. i just tested on x86 and it worked fine (not yet tested in x86_64) ptlib: MD5SUM check for ptlib-2.10.10.tar.xz ... OK Building package ptlib-2.10.10-i486-1_SBo.tgz ... OK Installing package ptlib-2.10.10-i486-1_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Apr 17 10:08:17 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Apr 2016 17:08:17 +0700 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> Message-ID: > i just tested on x86 and it worked fine (not yet tested in x86_64) > > ptlib: > MD5SUM check for ptlib-2.10.10.tar.xz ... OK > Building package ptlib-2.10.10-i486-1_SBo.tgz ... OK > Installing package ptlib-2.10.10-i486-1_SBo.tgz ... OK now updated to 2.10.11 plud a patch to disable SSLv3 and tested against ekiga in master branch and they are all OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Sun Apr 17 10:34:25 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 17 Apr 2016 11:34:25 +0100 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> Message-ID: <571366B1.6000905@open-t.co.uk> On 17/04/16 11:08, Willy Sudiarto Raharjo wrote: >> i just tested on x86 and it worked fine (not yet tested in x86_64) >> >> ptlib: >> MD5SUM check for ptlib-2.10.10.tar.xz ... OK >> Building package ptlib-2.10.10-i486-1_SBo.tgz ... OK >> Installing package ptlib-2.10.10-i486-1_SBo.tgz ... OK I'm on x86_64 - could that make a difference? From willysr at slackbuilds.org Sun Apr 17 10:45:30 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Apr 2016 17:45:30 +0700 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <571366B1.6000905@open-t.co.uk> References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> <571366B1.6000905@open-t.co.uk> Message-ID: <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> >>> MD5SUM check for ptlib-2.10.10.tar.xz ... OK >>> Building package ptlib-2.10.10-i486-1_SBo.tgz ... OK >>> Installing package ptlib-2.10.10-i486-1_SBo.tgz ... OK > I'm on x86_64 - could that make a difference? probably i will check it later since it's building other packages -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Apr 17 10:51:17 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Apr 2016 17:51:17 +0700 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> <571366B1.6000905@open-t.co.uk> <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> Message-ID: <08432046-256e-71d2-7ff8-e289e3e5f93f@slackbuilds.org> > i will check it later since it's building other packages it works fine on x86_64 as well Slackware package /tmp/ptlib-2.10.11-x86_64-1_SBo.tgz created. -- 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 Sun Apr 17 11:46:34 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 17 Apr 2016 12:46:34 +0100 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <08432046-256e-71d2-7ff8-e289e3e5f93f@slackbuilds.org> References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> <571366B1.6000905@open-t.co.uk> <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> <08432046-256e-71d2-7ff8-e289e3e5f93f@slackbuilds.org> Message-ID: <5713779A.8080800@open-t.co.uk> On 17/04/16 11:51, Willy Sudiarto Raharjo wrote: >> i will check it later since it's building other packages > it works fine on x86_64 as well > > Slackware package /tmp/ptlib-2.10.11-x86_64-1_SBo.tgz created. Hmm - it sounds like I'm stuck then. I have what I think is a completely current system (I just ran updates this morning again). It's all a little strange. But thank you for trying on your machine! From baildon.research at googlemail.com Sun Apr 17 12:58:31 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 17 Apr 2016 13:58:31 +0100 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <5713779A.8080800@open-t.co.uk> References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> <571366B1.6000905@open-t.co.uk> <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> <08432046-256e-71d2-7ff8-e289e3e5f93f@slackbuilds.org> <5713779A.8080800@open-t.co.uk> Message-ID: > Hmm - it sounds like I'm stuck then. I have what I think is a completely > current system (I just ran updates this morning again). It's all a little > strange. But thank you for trying on your machine! It's almost as if you've been using the 14.1 SlackBuild instead of the SlackBuild from git master, which I patched for exactly this problem months ago. ;-) -D. From s.arcus at open-t.co.uk Sun Apr 17 13:20:45 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 17 Apr 2016 14:20:45 +0100 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> <571366B1.6000905@open-t.co.uk> <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> <08432046-256e-71d2-7ff8-e289e3e5f93f@slackbuilds.org> <5713779A.8080800@open-t.co.uk> Message-ID: <57138DAD.5080608@open-t.co.uk> On 17/04/16 13:58, David Spencer wrote: >> Hmm - it sounds like I'm stuck then. I have what I think is a completely >> current system (I just ran updates this morning again). It's all a little >> strange. But thank you for trying on your machine! > It's almost as if you've been using the 14.1 SlackBuild instead of the > SlackBuild from git master, which I patched for exactly this problem > months ago. > > ;-) Ha! Now it's starting to make sense and I'm kind of lost at the same time! I didn't realise we were supposes to use the scripts from git. Now I'll have to figure out where those are and how to download them. Thank you! PS - Thinking about it, it starts to make sense - the git must contain the scripts which work with -current. From lionelyoung at gmail.com Sun Apr 17 11:48:16 2016 From: lionelyoung at gmail.com (Lionel Young) Date: Sun, 17 Apr 2016 19:48:16 +0800 Subject: [Slackbuilds-users] Looking for New Maintainers Message-ID: Hi all, I have two packages that can use new maintainers: * haskell-platform * syncthing Would anybody like these? ~Lionel -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Apr 17 13:50:12 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Apr 2016 20:50:12 +0700 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <57138DAD.5080608@open-t.co.uk> References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> <571366B1.6000905@open-t.co.uk> <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> <08432046-256e-71d2-7ff8-e289e3e5f93f@slackbuilds.org> <5713779A.8080800@open-t.co.uk> <57138DAD.5080608@open-t.co.uk> Message-ID: <72ab22dc-66f3-4211-12d6-e8f6beaf350c@slackbuilds.org> > Ha! Now it's starting to make sense and I'm kind of lost at the same > time! I didn't realise we were supposes to use the scripts from git. Now > I'll have to figure out where those are and how to download them. Thank > you! > > PS - Thinking about it, it starts to make sense - the git must contain > the scripts which work with -current. yes, master branch is now tracking current our website is still using the old 14.1 branch once Slackware 14.2 gets released and our repo is ready, we will make a new branch 14.2 and the website will use that. -- 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 Sun Apr 17 20:29:36 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 17 Apr 2016 21:29:36 +0100 Subject: [Slackbuilds-users] PTLib doesn't compile any more on -current In-Reply-To: <72ab22dc-66f3-4211-12d6-e8f6beaf350c@slackbuilds.org> References: <57134F90.3070401@open-t.co.uk> <0e4708ec-8af1-f06d-2990-d21ad951998d@slackbuilds.org> <571366B1.6000905@open-t.co.uk> <8c19ff9c-2d0c-7c96-eb9e-13e53179ab76@slackbuilds.org> <08432046-256e-71d2-7ff8-e289e3e5f93f@slackbuilds.org> <5713779A.8080800@open-t.co.uk> <57138DAD.5080608@open-t.co.uk> <72ab22dc-66f3-4211-12d6-e8f6beaf350c@slackbuilds.org> Message-ID: <5713F230.7010602@open-t.co.uk> On 17/04/16 14:50, Willy Sudiarto Raharjo wrote: >> Ha! Now it's starting to make sense and I'm kind of lost at the same >> time! I didn't realise we were supposes to use the scripts from git. Now >> I'll have to figure out where those are and how to download them. Thank >> you! >> >> PS - Thinking about it, it starts to make sense - the git must contain >> the scripts which work with -current. > yes, master branch is now tracking current > our website is still using the old 14.1 branch > once Slackware 14.2 gets released and our repo is ready, we will make a > new branch 14.2 and the website will use that. Thank you again Willy and David. I tracked down the copies from git master and it all worked out perfectly! I also understand a bit more about how SBo works as well. From s.arcus at open-t.co.uk Sun Apr 17 20:37:52 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 17 Apr 2016 21:37:52 +0100 Subject: [Slackbuilds-users] Looking for New Maintainers In-Reply-To: References: Message-ID: <5713F420.1030502@open-t.co.uk> On 17/04/16 12:48, Lionel Young wrote: > Hi all, > > I have two packages that can use new maintainers: > > * haskell-platform > * syncthing > > Would anybody like these? > I would quite like to look after syncthing - but I'm guessing to do that would involve using git - which I've never delved into yet? Or am I mistaken on that point? From kingbeowulf at gmail.com Sun Apr 17 23:26:24 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 17 Apr 2016 16:26:24 -0700 Subject: [Slackbuilds-users] Looking for New Maintainers In-Reply-To: <5713F420.1030502@open-t.co.uk> References: <5713F420.1030502@open-t.co.uk> Message-ID: <57141BA0.4040208@gmail.com> On 04/17/2016 01:37 PM, Sebastian Arcus wrote: > On 17/04/16 12:48, Lionel Young wrote: >> Hi all, >> >> I have two packages that can use new maintainers: >> >> * haskell-platform >> * syncthing >> >> Would anybody like these? >> > I would quite like to look after syncthing - but I'm guessing to do that > would involve using git - which I've never delved into yet? Or am I > mistaken on that point? > > The project posts release tarballs here: https://github.com/syncthing/syncthing/releases (binaries and source) -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 s.arcus at open-t.co.uk Mon Apr 18 07:11:30 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Mon, 18 Apr 2016 08:11:30 +0100 Subject: [Slackbuilds-users] Looking for New Maintainers In-Reply-To: <57141BA0.4040208@gmail.com> References: <5713F420.1030502@open-t.co.uk> <57141BA0.4040208@gmail.com> Message-ID: <571488A2.6010809@open-t.co.uk> On 18/04/16 00:26, King Beowulf wrote: > On 04/17/2016 01:37 PM, Sebastian Arcus wrote: >> On 17/04/16 12:48, Lionel Young wrote: >>> Hi all, >>> >>> I have two packages that can use new maintainers: >>> >>> * haskell-platform >>> * syncthing >>> >>> Would anybody like these? >>> >> I would quite like to look after syncthing - but I'm guessing to do that >> would involve using git - which I've never delved into yet? Or am I >> mistaken on that point? >> >> > The project posts release tarballs here: > > https://github.com/syncthing/syncthing/releases > > (binaries and source) > > -Ed Thank you Ed. I was actually referring to SBo. I'm not sure what the process is - if I would have to run git to push my updates to SBo? P.S. - OK - sorry, I just bothered to RTFM. Apparently I don't need git. In that case, I'd like to look after syncthing, if that's OK Lionel. From lionelyoung at gmail.com Mon Apr 18 10:32:33 2016 From: lionelyoung at gmail.com (Lionel Young) Date: Mon, 18 Apr 2016 18:32:33 +0800 Subject: [Slackbuilds-users] Looking for New Maintainers Message-ID: Thanks Sebastian! syncthing is yours Hi all, haskell-platform still available ~Lionel On Mon, Apr 18, 2016 at 3:11 PM, 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: PTLib doesn't compile any more on -current (David Spencer) > 2. Re: PTLib doesn't compile any more on -current (Sebastian Arcus) > 3. Looking for New Maintainers (Lionel Young) > 4. Re: PTLib doesn't compile any more on -current > (Willy Sudiarto Raharjo) > 5. Re: PTLib doesn't compile any more on -current (Sebastian Arcus) > 6. Re: Looking for New Maintainers (Sebastian Arcus) > 7. Re: Looking for New Maintainers (King Beowulf) > 8. Re: Looking for New Maintainers (Sebastian Arcus) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 17 Apr 2016 13:58:31 +0100 > From: David Spencer > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on > -current > Message-ID: > < > CAMt7G9SaQbjwpG8Apap5MbwQk-AfsOCU8rPnFKdZ2C+VLZE39A at mail.gmail.com> > Content-Type: text/plain; charset=UTF-8 > > > Hmm - it sounds like I'm stuck then. I have what I think is a completely > > current system (I just ran updates this morning again). It's all a little > > strange. But thank you for trying on your machine! > > It's almost as if you've been using the 14.1 SlackBuild instead of the > SlackBuild from git master, which I patched for exactly this problem > months ago. > > ;-) > > -D. > > > ------------------------------ > > Message: 2 > Date: Sun, 17 Apr 2016 14:20:45 +0100 > From: Sebastian Arcus > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on > -current > Message-ID: <57138DAD.5080608 at open-t.co.uk> > Content-Type: text/plain; charset=windows-1252; format=flowed > > On 17/04/16 13:58, David Spencer wrote: > >> Hmm - it sounds like I'm stuck then. I have what I think is a completely > >> current system (I just ran updates this morning again). It's all a > little > >> strange. But thank you for trying on your machine! > > It's almost as if you've been using the 14.1 SlackBuild instead of the > > SlackBuild from git master, which I patched for exactly this problem > > months ago. > > > > ;-) > > Ha! Now it's starting to make sense and I'm kind of lost at the same > time! I didn't realise we were supposes to use the scripts from git. Now > I'll have to figure out where those are and how to download them. Thank > you! > > PS - Thinking about it, it starts to make sense - the git must contain > the scripts which work with -current. > > > ------------------------------ > > Message: 3 > Date: Sun, 17 Apr 2016 19:48:16 +0800 > From: Lionel Young > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] Looking for New Maintainers > Message-ID: > w73sq2-6a5n5yeyZ4t44Kj6Twnzk+W26q6y0XoYSQ at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > I have two packages that can use new maintainers: > > * haskell-platform > * syncthing > > Would anybody like these? > > ~Lionel > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160417/627c0598/attachment-0001.html > > > > ------------------------------ > > Message: 4 > Date: Sun, 17 Apr 2016 20:50:12 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on > -current > Message-ID: <72ab22dc-66f3-4211-12d6-e8f6beaf350c at slackbuilds.org> > Content-Type: text/plain; charset="windows-1252" > > > Ha! Now it's starting to make sense and I'm kind of lost at the same > > time! I didn't realise we were supposes to use the scripts from git. Now > > I'll have to figure out where those are and how to download them. Thank > > you! > > > > PS - Thinking about it, it starts to make sense - the git must contain > > the scripts which work with -current. > > yes, master branch is now tracking current > our website is still using the old 14.1 branch > once Slackware 14.2 gets released and our repo is ready, we will make a > new branch 14.2 and the website will use that. > > > -- > 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: < > http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160417/5c76be54/attachment-0001.asc > > > > ------------------------------ > > Message: 5 > Date: Sun, 17 Apr 2016 21:29:36 +0100 > From: Sebastian Arcus > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on > -current > Message-ID: <5713F230.7010602 at open-t.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 17/04/16 14:50, Willy Sudiarto Raharjo wrote: > >> Ha! Now it's starting to make sense and I'm kind of lost at the same > >> time! I didn't realise we were supposes to use the scripts from git. Now > >> I'll have to figure out where those are and how to download them. Thank > >> you! > >> > >> PS - Thinking about it, it starts to make sense - the git must contain > >> the scripts which work with -current. > > yes, master branch is now tracking current > > our website is still using the old 14.1 branch > > once Slackware 14.2 gets released and our repo is ready, we will make a > > new branch 14.2 and the website will use that. > Thank you again Willy and David. I tracked down the copies from git > master and it all worked out perfectly! I also understand a bit more > about how SBo works as well. > > > > ------------------------------ > > Message: 6 > Date: Sun, 17 Apr 2016 21:37:52 +0100 > From: Sebastian Arcus > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Looking for New Maintainers > Message-ID: <5713F420.1030502 at open-t.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 17/04/16 12:48, Lionel Young wrote: > > Hi all, > > > > I have two packages that can use new maintainers: > > > > * haskell-platform > > * syncthing > > > > Would anybody like these? > > > I would quite like to look after syncthing - but I'm guessing to do that > would involve using git - which I've never delved into yet? Or am I > mistaken on that point? > > > > > ------------------------------ > > Message: 7 > Date: Sun, 17 Apr 2016 16:26:24 -0700 > From: King Beowulf > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Looking for New Maintainers > Message-ID: <57141BA0.4040208 at gmail.com> > Content-Type: text/plain; charset="utf-8" > > On 04/17/2016 01:37 PM, Sebastian Arcus wrote: > > On 17/04/16 12:48, Lionel Young wrote: > >> Hi all, > >> > >> I have two packages that can use new maintainers: > >> > >> * haskell-platform > >> * syncthing > >> > >> Would anybody like these? > >> > > I would quite like to look after syncthing - but I'm guessing to do that > > would involve using git - which I've never delved into yet? Or am I > > mistaken on that point? > > > > > > The project posts release tarballs here: > > https://github.com/syncthing/syncthing/releases > > (binaries and source) > > -Ed > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 181 bytes > Desc: OpenPGP digital signature > URL: < > http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160417/e02f6b35/attachment-0001.asc > > > > ------------------------------ > > Message: 8 > Date: Mon, 18 Apr 2016 08:11:30 +0100 > From: Sebastian Arcus > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Looking for New Maintainers > Message-ID: <571488A2.6010809 at open-t.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > On 18/04/16 00:26, King Beowulf wrote: > > On 04/17/2016 01:37 PM, Sebastian Arcus wrote: > >> On 17/04/16 12:48, Lionel Young wrote: > >>> Hi all, > >>> > >>> I have two packages that can use new maintainers: > >>> > >>> * haskell-platform > >>> * syncthing > >>> > >>> Would anybody like these? > >>> > >> I would quite like to look after syncthing - but I'm guessing to do that > >> would involve using git - which I've never delved into yet? Or am I > >> mistaken on that point? > >> > >> > > The project posts release tarballs here: > > > > https://github.com/syncthing/syncthing/releases > > > > (binaries and source) > > > > -Ed > Thank you Ed. I was actually referring to SBo. I'm not sure what the > process is - if I would have to run git to push my updates to SBo? > > P.S. - OK - sorry, I just bothered to RTFM. Apparently I don't need git. > In that case, I'd like to look after syncthing, if that's OK Lionel. > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > ------------------------------ > > End of SlackBuilds-users Digest, Vol 120, Issue 7 > ************************************************* > -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Mon Apr 18 11:13:39 2016 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 18 Apr 2016 12:13:39 +0100 Subject: [Slackbuilds-users] Looking for New Maintainers In-Reply-To: References: Message-ID: > Hi all, haskell-platform still available btw, it's broken on -current / 14.2rc, so if someone can fix it and maintain it, everybody will be really happy and grateful and favourably impressed :) -D. From porting at use.startmail.com Mon Apr 18 11:40:00 2016 From: porting at use.startmail.com (=?iso-8859-1?Q?Rub=E9n?= Llorente) Date: Mon, 18 Apr 2016 13:40:00 +0200 Subject: [Slackbuilds-users] Identity modification. Message-ID: <20160418113959.GA2742@workstation> Hello. I am no longer going to use a pseudonym for software projects, so I am requesting that the slackbuilds assigned to Black Rider be assigned to Rub?n Llorente You are invited to ask for a confirmation at the first email address. -- OpenPGP Key Fingerprint: BB5A C2A2 2CAD ACB7 D50D C081 1DB9 6FC4 5AB7 92FA OpenPGP Key ID: 5AB792FA From matt at thegnuguru.org Mon Apr 18 13:56:39 2016 From: matt at thegnuguru.org (Matt Arnold) Date: Mon, 18 Apr 2016 09:56:39 -0400 Subject: [Slackbuilds-users] Looking for New Maintainers In-Reply-To: References: Message-ID: I'll take haskell-pltform but I won't be able to unbreak it on 14.2 until the weekend On Mon, Apr 18, 2016 at 7:13 AM, David Spencer < baildon.research at googlemail.com> wrote: > > Hi all, haskell-platform still available > > btw, it's broken on -current / 14.2rc, so if someone can fix it and > maintain it, everybody will be really happy and grateful and > favourably impressed :) > > -D. > _______________________________________________ > 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 glenn.becker at gmail.com Mon Apr 18 14:26:33 2016 From: glenn.becker at gmail.com (Glenn Becker) Date: Mon, 18 Apr 2016 10:26:33 -0400 Subject: [Slackbuilds-users] Looking for New Maintainers In-Reply-To: References: Message-ID: I would step up if I wasn't doing a strikingly just barely adequate job with the ones I have ... Glenn On Mon, Apr 18, 2016 at 6:32 AM, Lionel Young wrote: > Thanks Sebastian! syncthing is yours > > Hi all, haskell-platform still available > > ~Lionel > > On Mon, Apr 18, 2016 at 3:11 PM, < > slackbuilds-users-request at slackbuilds.org> wrote: > >> Send SlackBuilds-users mailing list submissions to >> slackbuilds-users at slackbuilds.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> or, via email, send a message with subject or body 'help' to >> slackbuilds-users-request at slackbuilds.org >> >> You can reach the person managing the list at >> slackbuilds-users-owner at slackbuilds.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of SlackBuilds-users digest..." >> >> >> Today's Topics: >> >> 1. Re: PTLib doesn't compile any more on -current (David Spencer) >> 2. Re: PTLib doesn't compile any more on -current (Sebastian Arcus) >> 3. Looking for New Maintainers (Lionel Young) >> 4. Re: PTLib doesn't compile any more on -current >> (Willy Sudiarto Raharjo) >> 5. Re: PTLib doesn't compile any more on -current (Sebastian Arcus) >> 6. Re: Looking for New Maintainers (Sebastian Arcus) >> 7. Re: Looking for New Maintainers (King Beowulf) >> 8. Re: Looking for New Maintainers (Sebastian Arcus) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Sun, 17 Apr 2016 13:58:31 +0100 >> From: David Spencer >> To: "SlackBuilds.org Users List" >> Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on >> -current >> Message-ID: >> < >> CAMt7G9SaQbjwpG8Apap5MbwQk-AfsOCU8rPnFKdZ2C+VLZE39A at mail.gmail.com> >> Content-Type: text/plain; charset=UTF-8 >> >> > Hmm - it sounds like I'm stuck then. I have what I think is a completely >> > current system (I just ran updates this morning again). It's all a >> little >> > strange. But thank you for trying on your machine! >> >> It's almost as if you've been using the 14.1 SlackBuild instead of the >> SlackBuild from git master, which I patched for exactly this problem >> months ago. >> >> ;-) >> >> -D. >> >> >> ------------------------------ >> >> Message: 2 >> Date: Sun, 17 Apr 2016 14:20:45 +0100 >> From: Sebastian Arcus >> To: slackbuilds-users at slackbuilds.org >> Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on >> -current >> Message-ID: <57138DAD.5080608 at open-t.co.uk> >> Content-Type: text/plain; charset=windows-1252; format=flowed >> >> On 17/04/16 13:58, David Spencer wrote: >> >> Hmm - it sounds like I'm stuck then. I have what I think is a >> completely >> >> current system (I just ran updates this morning again). It's all a >> little >> >> strange. But thank you for trying on your machine! >> > It's almost as if you've been using the 14.1 SlackBuild instead of the >> > SlackBuild from git master, which I patched for exactly this problem >> > months ago. >> > >> > ;-) >> >> Ha! Now it's starting to make sense and I'm kind of lost at the same >> time! I didn't realise we were supposes to use the scripts from git. Now >> I'll have to figure out where those are and how to download them. Thank >> you! >> >> PS - Thinking about it, it starts to make sense - the git must contain >> the scripts which work with -current. >> >> >> ------------------------------ >> >> Message: 3 >> Date: Sun, 17 Apr 2016 19:48:16 +0800 >> From: Lionel Young >> To: slackbuilds-users at slackbuilds.org >> Subject: [Slackbuilds-users] Looking for New Maintainers >> Message-ID: >> > w73sq2-6a5n5yeyZ4t44Kj6Twnzk+W26q6y0XoYSQ at mail.gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> Hi all, >> >> I have two packages that can use new maintainers: >> >> * haskell-platform >> * syncthing >> >> Would anybody like these? >> >> ~Lionel >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> URL: < >> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160417/627c0598/attachment-0001.html >> > >> >> ------------------------------ >> >> Message: 4 >> Date: Sun, 17 Apr 2016 20:50:12 +0700 >> From: Willy Sudiarto Raharjo >> To: slackbuilds-users at slackbuilds.org >> Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on >> -current >> Message-ID: <72ab22dc-66f3-4211-12d6-e8f6beaf350c at slackbuilds.org> >> Content-Type: text/plain; charset="windows-1252" >> >> > Ha! Now it's starting to make sense and I'm kind of lost at the same >> > time! I didn't realise we were supposes to use the scripts from git. Now >> > I'll have to figure out where those are and how to download them. Thank >> > you! >> > >> > PS - Thinking about it, it starts to make sense - the git must contain >> > the scripts which work with -current. >> >> yes, master branch is now tracking current >> our website is still using the old 14.1 branch >> once Slackware 14.2 gets released and our repo is ready, we will make a >> new branch 14.2 and the website will use that. >> >> >> -- >> 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: < >> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160417/5c76be54/attachment-0001.asc >> > >> >> ------------------------------ >> >> Message: 5 >> Date: Sun, 17 Apr 2016 21:29:36 +0100 >> From: Sebastian Arcus >> To: slackbuilds-users at slackbuilds.org >> Subject: Re: [Slackbuilds-users] PTLib doesn't compile any more on >> -current >> Message-ID: <5713F230.7010602 at open-t.co.uk> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> On 17/04/16 14:50, Willy Sudiarto Raharjo wrote: >> >> Ha! Now it's starting to make sense and I'm kind of lost at the same >> >> time! I didn't realise we were supposes to use the scripts from git. >> Now >> >> I'll have to figure out where those are and how to download them. Thank >> >> you! >> >> >> >> PS - Thinking about it, it starts to make sense - the git must contain >> >> the scripts which work with -current. >> > yes, master branch is now tracking current >> > our website is still using the old 14.1 branch >> > once Slackware 14.2 gets released and our repo is ready, we will make a >> > new branch 14.2 and the website will use that. >> Thank you again Willy and David. I tracked down the copies from git >> master and it all worked out perfectly! I also understand a bit more >> about how SBo works as well. >> >> >> >> ------------------------------ >> >> Message: 6 >> Date: Sun, 17 Apr 2016 21:37:52 +0100 >> From: Sebastian Arcus >> To: "SlackBuilds.org Users List" >> Subject: Re: [Slackbuilds-users] Looking for New Maintainers >> Message-ID: <5713F420.1030502 at open-t.co.uk> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> On 17/04/16 12:48, Lionel Young wrote: >> > Hi all, >> > >> > I have two packages that can use new maintainers: >> > >> > * haskell-platform >> > * syncthing >> > >> > Would anybody like these? >> > >> I would quite like to look after syncthing - but I'm guessing to do that >> would involve using git - which I've never delved into yet? Or am I >> mistaken on that point? >> >> >> >> >> ------------------------------ >> >> Message: 7 >> Date: Sun, 17 Apr 2016 16:26:24 -0700 >> From: King Beowulf >> To: slackbuilds-users at slackbuilds.org >> Subject: Re: [Slackbuilds-users] Looking for New Maintainers >> Message-ID: <57141BA0.4040208 at gmail.com> >> Content-Type: text/plain; charset="utf-8" >> >> On 04/17/2016 01:37 PM, Sebastian Arcus wrote: >> > On 17/04/16 12:48, Lionel Young wrote: >> >> Hi all, >> >> >> >> I have two packages that can use new maintainers: >> >> >> >> * haskell-platform >> >> * syncthing >> >> >> >> Would anybody like these? >> >> >> > I would quite like to look after syncthing - but I'm guessing to do that >> > would involve using git - which I've never delved into yet? Or am I >> > mistaken on that point? >> > >> > >> >> The project posts release tarballs here: >> >> https://github.com/syncthing/syncthing/releases >> >> (binaries and source) >> >> -Ed >> >> -------------- next part -------------- >> A non-text attachment was scrubbed... >> Name: signature.asc >> Type: application/pgp-signature >> Size: 181 bytes >> Desc: OpenPGP digital signature >> URL: < >> http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20160417/e02f6b35/attachment-0001.asc >> > >> >> ------------------------------ >> >> Message: 8 >> Date: Mon, 18 Apr 2016 08:11:30 +0100 >> From: Sebastian Arcus >> To: slackbuilds-users at slackbuilds.org >> Subject: Re: [Slackbuilds-users] Looking for New Maintainers >> Message-ID: <571488A2.6010809 at open-t.co.uk> >> Content-Type: text/plain; charset=utf-8; format=flowed >> >> On 18/04/16 00:26, King Beowulf wrote: >> > On 04/17/2016 01:37 PM, Sebastian Arcus wrote: >> >> On 17/04/16 12:48, Lionel Young wrote: >> >>> Hi all, >> >>> >> >>> I have two packages that can use new maintainers: >> >>> >> >>> * haskell-platform >> >>> * syncthing >> >>> >> >>> Would anybody like these? >> >>> >> >> I would quite like to look after syncthing - but I'm guessing to do >> that >> >> would involve using git - which I've never delved into yet? Or am I >> >> mistaken on that point? >> >> >> >> >> > The project posts release tarballs here: >> > >> > https://github.com/syncthing/syncthing/releases >> > >> > (binaries and source) >> > >> > -Ed >> Thank you Ed. I was actually referring to SBo. I'm not sure what the >> process is - if I would have to run git to push my updates to SBo? >> >> P.S. - OK - sorry, I just bothered to RTFM. Apparently I don't need git. >> In that case, I'd like to look after syncthing, if that's OK Lionel. >> >> >> ------------------------------ >> >> Subject: Digest Footer >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> >> >> ------------------------------ >> >> End of SlackBuilds-users Digest, Vol 120, Issue 7 >> ************************************************* >> > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From miguel at thedeanda.com Mon Apr 18 21:29:25 2016 From: miguel at thedeanda.com (Miguel De Anda) Date: Mon, 18 Apr 2016 14:29:25 -0700 Subject: [Slackbuilds-users] libreoffice binaries missing Message-ID: the binaries linked for 5.0.4 seem to be missing now. i tried updating the url for 5.1.2 locally and used VERSION=5.1.2 and the build seemed to work except for a warning about dangling pointers. the menu entries seem to work fine and i didn't have a chance investigate any further yet. From willysr at slackbuilds.org Mon Apr 18 23:47:53 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 19 Apr 2016 06:47:53 +0700 Subject: [Slackbuilds-users] libreoffice binaries missing In-Reply-To: References: Message-ID: <6f4aafa9-55e2-80f5-3c86-5e32cc48eaab@slackbuilds.org> > the binaries linked for 5.0.4 seem to be missing now. i tried updating > the url for 5.1.2 locally and used VERSION=5.1.2 and the build seemed > to work except for a warning about dangling pointers. the menu entries > seem to work fine and i didn't have a chance investigate any further > yet. the one in website still refer to 14.1 branch in master branch, it has been updated to 5.1.2 -- 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 Tue Apr 19 15:51:51 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 19 Apr 2016 22:51:51 +0700 Subject: [Slackbuilds-users] libreoffice binaries missing In-Reply-To: <6f4aafa9-55e2-80f5-3c86-5e32cc48eaab@slackbuilds.org> References: <6f4aafa9-55e2-80f5-3c86-5e32cc48eaab@slackbuilds.org> Message-ID: <409c3859-b255-6a31-bf79-0b19d8724e60@slackbuilds.org> >> the binaries linked for 5.0.4 seem to be missing now. i tried updating >> the url for 5.1.2 locally and used VERSION=5.1.2 and the build seemed >> to work except for a warning about dangling pointers. the menu entries >> seem to work fine and i didn't have a chance investigate any further >> yet. > > the one in website still refer to 14.1 branch > in master branch, it has been updated to 5.1.2 well, 5.1.2 is now included in 14.1 branch and should fix the broken link in SBo's website -- 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 miguel at thedeanda.com Tue Apr 19 16:01:32 2016 From: miguel at thedeanda.com (Miguel De Anda) Date: Tue, 19 Apr 2016 09:01:32 -0700 Subject: [Slackbuilds-users] libreoffice binaries missing In-Reply-To: <409c3859-b255-6a31-bf79-0b19d8724e60@slackbuilds.org> References: <6f4aafa9-55e2-80f5-3c86-5e32cc48eaab@slackbuilds.org> <409c3859-b255-6a31-bf79-0b19d8724e60@slackbuilds.org> Message-ID: thanks. I just wanted to report in case anyone else had trouble. On Apr 19, 2016 8:52 AM, "Willy Sudiarto Raharjo" wrote: > >> the binaries linked for 5.0.4 seem to be missing now. i tried updating > >> the url for 5.1.2 locally and used VERSION=5.1.2 and the build seemed > >> to work except for a warning about dangling pointers. the menu entries > >> seem to work fine and i didn't have a chance investigate any further > >> yet. > > > > the one in website still refer to 14.1 branch > > in master branch, it has been updated to 5.1.2 > > well, 5.1.2 is now included in 14.1 branch and should fix the broken > link in SBo's website > > > -- > 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/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brent at exitstatusone.com Tue Apr 19 22:04:37 2016 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 19 Apr 2016 16:04:37 -0600 Subject: [Slackbuilds-users] perl-test-warn,perl-Test-Warn Message-ID: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> I ran into duplicate packages in SBo master while building perl-www-mechanize. perl-Test-Warn and perl-test-warn are the duplicates. Additionally the "perl-Test-Warn" package is not building because tar cannot open the source archive. Can someone please confirm this? I've tested it on two separate x86_64 14.2 RC2 virtual machines and both have the same result. Thanks! -- Brenton Earl -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From chris at chrisn.me.uk Tue Apr 19 22:13:25 2016 From: chris at chrisn.me.uk (Chris Novakovic) Date: Tue, 19 Apr 2016 23:13:25 +0100 Subject: [Slackbuilds-users] perl-test-warn,perl-Test-Warn In-Reply-To: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> References: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> Message-ID: <5716AD85.3030908@chrisn.me.uk> On 19/04/2016 23:04, Brenton Earl wrote: > I ran into duplicate packages in SBo master while building > perl-www-mechanize. > > perl-Test-Warn and perl-test-warn are the duplicates. They are indeed: well spotted. > Additionally the "perl-Test-Warn" package is not building because tar > cannot open the source archive. > > Can someone please confirm this? I've tested it on two separate x86_64 > 14.2 RC2 virtual machines and both have the same result. What source are you using for the tarball? The one in the .info file is the same for both SlackBuilds: https://cpan.metacpan.org/authors/id/C/CH/CHORNY/Test-Warn-0.30.tar.gz which downloads and extracts fine for me. You could also try downloading it from the master CPAN site: http://www.cpan.org/CPAN/authors/id/C/CH/CHORNY/Test-Warn-0.30.tar.gz From glenn.becker at gmail.com Tue Apr 19 22:16:03 2016 From: glenn.becker at gmail.com (Glenn Becker) Date: Tue, 19 Apr 2016 18:16:03 -0400 Subject: [Slackbuilds-users] perl-test-warn,perl-Test-Warn In-Reply-To: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> References: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> Message-ID: Hi Brenton, I have the lowercase "perl-test-warn" in my list. Don't know about the other ... Glenn On Tue, Apr 19, 2016 at 6:04 PM, Brenton Earl wrote: > I ran into duplicate packages in SBo master while building > perl-www-mechanize. > > perl-Test-Warn and perl-test-warn are the duplicates. > > Additionally the "perl-Test-Warn" package is not building because tar > cannot open the source archive. > > Can someone please confirm this? I've tested it on two separate x86_64 > 14.2 RC2 virtual machines and both have the same result. > > Thanks! > -- > Brenton Earl > > > _______________________________________________ > 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 brent at exitstatusone.com Tue Apr 19 22:37:44 2016 From: brent at exitstatusone.com (Brenton Earl) Date: Tue, 19 Apr 2016 16:37:44 -0600 Subject: [Slackbuilds-users] perl-test-warn,perl-Test-Warn In-Reply-To: References: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> Message-ID: <58410374-dff1-dc24-6271-04b9bbffa8e5@exitstatusone.com> It looks like if I change the .info file checksum to be within the MD5SUM setting, rather than MD5SUM_x86_64, perl-Test-Warn builds just fine. I guess it is a matter of choosing which to keep and correcting the .info file so the checksum is in the right variable for sbopkg to find this. After the duplicate Test-Warn is removed, then perl-www-mechainze will build correctly with sbopkg. sbopkg gets confused and builds both packages. REQUIRES are pulled from both .info files too. My attached screenshot shows what I mean when executing "sbopkg -i perl-www-mechainze". -- Brenton Earl -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot_SBo-dev-Slackware-14.2-RC2-x86_64_2016-04-19_16:35:04.png Type: image/png Size: 21055 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Apr 20 01:35:49 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Apr 2016 08:35:49 +0700 Subject: [Slackbuilds-users] perl-test-warn,perl-Test-Warn In-Reply-To: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> References: <4a323346-ec49-57b1-3c9f-021bbe627fa0@exitstatusone.com> Message-ID: > I ran into duplicate packages in SBo master while building > perl-www-mechanize. > > perl-Test-Warn and perl-test-warn are the duplicates. > > Additionally the "perl-Test-Warn" package is not building because tar > cannot open the source archive. > > Can someone please confirm this? I've tested it on two separate x86_64 > 14.2 RC2 virtual machines and both have the same result. it's now removed in my branch along with perl-test-tester which is now included in Slackware's perl package as well. Thanks for reporting -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From lems at gmx.net Wed Apr 20 02:22:22 2016 From: lems at gmx.net (Leonard Schmidt) Date: Wed, 20 Apr 2016 04:22:22 +0200 Subject: [Slackbuilds-users] please update network/bozohttpd to 20160415 Message-ID: <0Lx83d-1bq9xe1NuL-016izp@mail.gmx.com> Hello, attached is a patch which will update network/bozohttpd from 20150320 to 20160415. Among other small fixes, this is from the ChangeLog: o fix a security issue in CGI suffix handler support which would allow remote code execution, from shm at netbsd.org Regards Leonard -------------- next part -------------- A non-text attachment was scrubbed... Name: bozohttpd-20150320-to-20160415.diff Type: text/x-diff Size: 1014 bytes Desc: bozohttpd-20150320-to-20160415.diff URL: From miguel at thedeanda.com Wed Apr 20 08:32:51 2016 From: miguel at thedeanda.com (Miguel De Anda) Date: Wed, 20 Apr 2016 01:32:51 -0700 Subject: [Slackbuilds-users] kphotoalbum 4.7.1 Message-ID: 4.6.1 wasn't building on my slackware-current and i tried updating to 4.7.1 and it works better. changelog mentions fixes related to distro/gcc configurations so its probably related. it also now has an optional dependency of libkface. (since 4.6 i believe) i basically used the following in the info file: PRGNAM="kphotoalbum" VERSION="4.7.1" HOMEPAGE="http://kphotoalbum.org" DOWNLOAD="http://download.kde.org/stable/kphotoalbum/4.7.1/src/kphotoalbum-4.7.1.tar.xz" MD5SUM="6994263a53780e1f5d40cc197db8f10b" ... then bumped up VERSION in the SlackBuild to match: VERSION=${VERSION:-4.7.1} https://github.com/mdeanda/slackbuilds/commit/2165b5d703d6e19bee8ed49bfb7b2d665c567195 From willysr at slackbuilds.org Wed Apr 20 09:11:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Apr 2016 16:11:02 +0700 Subject: [Slackbuilds-users] kphotoalbum 4.7.1 In-Reply-To: References: Message-ID: > 4.6.1 wasn't building on my slackware-current and i tried updating to > 4.7.1 and it works better. changelog mentions fixes related to > distro/gcc configurations so its probably related. > > it also now has an optional dependency of libkface. (since 4.6 i believe) > > i basically used the following in the info file: > > PRGNAM="kphotoalbum" > VERSION="4.7.1" > HOMEPAGE="http://kphotoalbum.org" > DOWNLOAD="http://download.kde.org/stable/kphotoalbum/4.7.1/src/kphotoalbum-4.7.1.tar.xz" > MD5SUM="6994263a53780e1f5d40cc197db8f10b" > ... > > then bumped up VERSION in the SlackBuild to match: > > VERSION=${VERSION:-4.7.1} > > https://github.com/mdeanda/slackbuilds/commit/2165b5d703d6e19bee8ed49bfb7b2d665c567195 Applied to my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Apr 20 09:13:26 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Apr 2016 16:13:26 +0700 Subject: [Slackbuilds-users] please update network/bozohttpd to 20160415 In-Reply-To: <0Lx83d-1bq9xe1NuL-016izp@mail.gmx.com> References: <0Lx83d-1bq9xe1NuL-016izp@mail.gmx.com> Message-ID: > attached is a patch which will update network/bozohttpd from 20150320 to > 20160415. Among other small fixes, this is from the ChangeLog: > > o fix a security issue in CGI suffix handler support which would > allow remote code execution, from shm at netbsd.org Applied to my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Apr 20 09:20:31 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Apr 2016 16:20:31 +0700 Subject: [Slackbuilds-users] Identity modification. In-Reply-To: <20160418113959.GA2742@workstation> References: <20160418113959.GA2742@workstation> Message-ID: <95883c0e-d13d-1c2b-5115-0b7911e6b899@slackbuilds.org> > I am no longer going to use a pseudonym for software projects, so I am > requesting that the slackbuilds assigned to Black Rider > be assigned to Rub?n Llorente > Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From brent at exitstatusone.com Wed Apr 20 16:41:54 2016 From: brent at exitstatusone.com (Brenton Earl) Date: Wed, 20 Apr 2016 10:41:54 -0600 Subject: [Slackbuilds-users] netlib fix Message-ID: <6ef0be7d-477f-ca57-5ba4-5b4ebc5bf74a@exitstatusone.com> The attached patch fixes the website, download link, and checksum for netlib.info. This is for the 14.1 and master branches. Thanks, -- Brenton Earl -------------- next part -------------- A non-text attachment was scrubbed... Name: netlib.info.patch Type: text/x-patch Size: 825 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From brent at exitstatusone.com Wed Apr 20 23:49:51 2016 From: brent at exitstatusone.com (Brenton Earl) Date: Wed, 20 Apr 2016 17:49:51 -0600 Subject: [Slackbuilds-users] driconf, bad link Message-ID: Hello, The driconf url is inactive. (http://source.dawoodfall.net/driconf-0.9.1.tar.gz) This is the maintainer's new site. http://unrealize.co.uk/source/driconf-0.9.1.tar.gz Thanks, -- Brenton Earl From willysr at slackbuilds.org Thu Apr 21 15:48:06 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 Apr 2016 22:48:06 +0700 Subject: [Slackbuilds-users] netlib fix In-Reply-To: <6ef0be7d-477f-ca57-5ba4-5b4ebc5bf74a@exitstatusone.com> References: <6ef0be7d-477f-ca57-5ba4-5b4ebc5bf74a@exitstatusone.com> Message-ID: <6b6982cd-f3d4-c645-4887-ef7762bfab62@slackbuilds.org> > The attached patch fixes the website, download link, and checksum for > netlib.info. This is for the 14.1 and master branches. Fixed in my branch for 14.2 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Apr 21 15:50:35 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 21 Apr 2016 22:50:35 +0700 Subject: [Slackbuilds-users] driconf, bad link In-Reply-To: References: Message-ID: <24d971bf-8bcf-8744-df69-255e54c4296e@slackbuilds.org> > The driconf url is inactive. > > (http://source.dawoodfall.net/driconf-0.9.1.tar.gz) > > This is the maintainer's new site. > > http://unrealize.co.uk/source/driconf-0.9.1.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 slackbuilds at schoepfer.info Fri Apr 22 02:54:07 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 22 Apr 2016 04:54:07 +0200 Subject: [Slackbuilds-users] texlive 2015 Message-ID: Hi, here is a diff to update texlive 2014 to texlive 2015 on current. Please also add the attached texmf_get.sh, as it is needed to create the texmf-tree from the texlive netarchives. The resulting texlive-package is under 70mb if created as txz. I'll also send updates for texlive-texmf-extra and texlive-texmf-docs, these all depend on texmf_get.sh, so symlinking to it in the git-tree might be good. Franzen -------------- next part -------------- A non-text attachment was scrubbed... Name: texlive.diff Type: text/x-diff Size: 12682 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: texmf_get.sh Type: text/x-shellscript Size: 17788 bytes Desc: not available URL: From slackbuilds at schoepfer.info Fri Apr 22 03:18:04 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 22 Apr 2016 05:18:04 +0200 Subject: [Slackbuilds-users] texlive-texmf-extra 2015 Message-ID: Hi, here is a diff to update texlive-texmf-extra 2014 to texlive-texmf-extra 2015 on current. By the way, texi2html maybe should be removed from SBo, as texinfo-6.1 shipped with current covers (almost)all its functionality. Franzen -------------- next part -------------- A non-text attachment was scrubbed... Name: texlive-texmf-extra.diff Type: text/x-diff Size: 4186 bytes Desc: not available URL: From slackbuilds at schoepfer.info Fri Apr 22 03:36:09 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 22 Apr 2016 05:36:09 +0200 Subject: [Slackbuilds-users] texlive-texmf-docs 2015 Message-ID: <454b631e9b9ca194c163345ebfcecb7d@schoepfer.info> Hi, here is a diff to update texlive-texmf-docs 2014 to texlive-texmf-docs 2015 on current. If someone is more interested on the texlive-packages, see www.linuxquestions.org/questions/slackware-14/call-for-testers-texlive-custom-4175574254/ Franzen -------------- next part -------------- A non-text attachment was scrubbed... Name: texlive-texmf-docs.diff Type: text/x-diff Size: 3678 bytes Desc: not available URL: From hostmaster at slackonly.com Fri Apr 22 10:49:44 2016 From: hostmaster at slackonly.com (Panagiotis Nikolaou) Date: Fri, 22 Apr 2016 03:49:44 -0700 Subject: [Slackbuilds-users] XDecorations Message-ID: <7abb7587-faee-fdc0-10b3-a3fd3e1c9f04@slackonly.com> Hi!, The doinst.sh of XDecorations is empty... Thanks! From willysr at slackbuilds.org Fri Apr 22 10:50:19 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 22 Apr 2016 17:50:19 +0700 Subject: [Slackbuilds-users] XDecorations In-Reply-To: <7abb7587-faee-fdc0-10b3-a3fd3e1c9f04@slackonly.com> References: <7abb7587-faee-fdc0-10b3-a3fd3e1c9f04@slackonly.com> Message-ID: > The doinst.sh of XDecorations is empty... 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 jebrhansen+SBo at gmail.com Sun Apr 24 03:47:57 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 23 Apr 2016 23:47:57 -0400 Subject: [Slackbuilds-users] sickrage.SlackBuild Testing Request (and uid/gid Request) Message-ID: I have compiled a SlackBuild for sickrage (a fork of SickBeard, which tracks TV shows). I did a lot of work to (hopefully) ensure that it complies with SlackBuild submissions, and I created an rc.sickrage from scratch to control it all. I know submissions are currently on hold until the 14.2 release, but I wanted to throw this out there if anyone is willing to test it out and give me any feedback/suggestions, as this will be my first submitted package that required this much work. Also, I wanted to request a sickrage user and group assignment. Currently, I temporarily have them assigned to 999 in the SlackBuild and README. Once assigned, I will update my build and likely find a way to host it on my github page (had an account for awhile, just never used it) until it can be submitted to SBo. Thanks for all your help. Jeremy I intended to attached the tar.gz, but gmail blocked it (not sure why, none of the extensions within the tar.gz were prohibited). Instead, here is a link you can download it from my computer. I will likely remove it within a few weeks to keep the directory clear. If there are any issues with the download, please let me know and I will find a different way to host it. http://bassmadrigal.duckdns.org/temp/sickrage.tar.gz -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Apr 24 03:52:51 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 Apr 2016 10:52:51 +0700 Subject: [Slackbuilds-users] sickrage.SlackBuild Testing Request (and uid/gid Request) In-Reply-To: References: Message-ID: > I have compiled a SlackBuild for sickrage (a fork of SickBeard, which > tracks TV shows). I did a lot of work to (hopefully) ensure that it > complies with SlackBuild submissions, and I created an rc.sickrage from > scratch to control it all. I know submissions are currently on hold until > the 14.2 release, but I wanted to throw this out there if anyone is willing > to test it out and give me any feedback/suggestions, as this will be my > first submitted package that required this much work. > > Also, I wanted to request a sickrage user and group assignment. Currently, > I temporarily have them assigned to 999 in the SlackBuild and README. Once > assigned, I will update my build and likely find a way to host it on my > github page (had an account for awhile, just never used it) until it can be > submitted to SBo. > > Thanks for all your help. > Jeremy > > I intended to attached the tar.gz, but gmail blocked it (not sure why, none > of the extensions within the tar.gz were prohibited). Instead, here is a > link you can download it from my computer. I will likely remove it within a > few weeks to keep the directory clear. If there are any issues with the > download, please let me know and I will find a different way to host it. > > http://bassmadrigal.duckdns.org/temp/sickrage.tar.gz Assigned 324 in uid_gid -- 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 jebrhansen+SBo at gmail.com Sun Apr 24 03:58:04 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 24 Apr 2016 03:58:04 +0000 Subject: [Slackbuilds-users] sickrage.SlackBuild Testing Request (and uid/gid Request) In-Reply-To: References: Message-ID: Thanks! I'll get things updated on the script tomorrow. On Sat, Apr 23, 2016, 11:53 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I have compiled a SlackBuild for sickrage (a fork of SickBeard, which > > tracks TV shows). I did a lot of work to (hopefully) ensure that it > > complies with SlackBuild submissions, and I created an rc.sickrage from > > scratch to control it all. I know submissions are currently on hold until > > the 14.2 release, but I wanted to throw this out there if anyone is > willing > > to test it out and give me any feedback/suggestions, as this will be my > > first submitted package that required this much work. > > > > Also, I wanted to request a sickrage user and group assignment. > Currently, > > I temporarily have them assigned to 999 in the SlackBuild and README. > Once > > assigned, I will update my build and likely find a way to host it on my > > github page (had an account for awhile, just never used it) until it can > be > > submitted to SBo. > > > > Thanks for all your help. > > Jeremy > > > > I intended to attached the tar.gz, but gmail blocked it (not sure why, > none > > of the extensions within the tar.gz were prohibited). Instead, here is a > > link you can download it from my computer. I will likely remove it > within a > > few weeks to keep the directory clear. If there are any issues with the > > download, please let me know and I will find a different way to host it. > > > > http://bassmadrigal.duckdns.org/temp/sickrage.tar.gz > > Assigned 324 in uid_gid > > > > -- > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sun Apr 24 14:29:42 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 24 Apr 2016 16:29:42 +0200 Subject: [Slackbuilds-users] find in SlackBuilds: again Message-ID: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> Hi, Are you sure that find in SlackBuilds should have the -L switched on? What if there's source tarball containing soft link to, say, /etc? I ran into this problem using the template SlackBuild. Fortunately, the tarball is mine, it only contained soft link to /tmp and I ran it as regular user. BTW, I had a look at a few SlackBuilds in -current and find does not have -L switched on. What are your thoughts? -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sun Apr 24 14:32:09 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 Apr 2016 21:32:09 +0700 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> Message-ID: > Are you sure that find in SlackBuilds should have the -L switched on? > What if there's source tarball containing soft link to, say, /etc? > > I ran into this problem using the template SlackBuild. Fortunately, the > tarball is mine, it only contained soft link to /tmp and I ran it as > regular user. > > BTW, I had a look at a few SlackBuilds in -current and find does not > have -L switched on. > > What are your thoughts? That must be the old scripts which never gets updated again new or up to date scripts mostly have -L applied 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 atelszewski at gmail.com Sun Apr 24 14:39:14 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 24 Apr 2016 16:39:14 +0200 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> Message-ID: <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> On 24/04/16 16:32, Willy Sudiarto Raharjo wrote: >> Are you sure that find in SlackBuilds should have the -L switched on? >> What if there's source tarball containing soft link to, say, /etc? >> >> I ran into this problem using the template SlackBuild. Fortunately, the >> tarball is mine, it only contained soft link to /tmp and I ran it as >> regular user. >> >> BTW, I had a look at a few SlackBuilds in -current and find does not >> have -L switched on. >> >> What are your thoughts? > > That must be the old scripts which never gets updated again > new or up to date scripts mostly have -L applied already > I don't understand what you mean;) When I wrote -current, I meant Slackware -current. Should the -L switch be there or not in SlackBuilds.org? :) Also, there is a difference between the permissions in SlackBuilds.org and Slackware's -current: SlackBuilds.org: find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ -o -perm 511 \) -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; Slackware's -current: find . \ \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; 750 and 640 are not present in Slackware's SlackBuilds. > > > > > _______________________________________________ > 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/ > -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sun Apr 24 14:41:03 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 Apr 2016 21:41:03 +0700 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> Message-ID: <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> > I don't understand what you mean;) > When I wrote -current, I meant Slackware -current. > Should the -L switch be there or not in SlackBuilds.org? :) > > Also, there is a difference between the permissions in SlackBuilds.org > and Slackware's -current: > > SlackBuilds.org: > find -L . \ > \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > -o -perm 511 \) -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > > Slackware's -current: > find . \ > \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ > -exec chmod 755 {} \; -o \ > \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o > -perm 400 \) \ > -exec chmod 644 {} \; > > > 750 and 640 are not present in Slackware's SlackBuilds. we expect that maintainers stick to the template, so we should use -L -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Apr 24 14:51:01 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 24 Apr 2016 16:51:01 +0200 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> Message-ID: <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> On 24/04/16 16:41, Willy Sudiarto Raharjo wrote: >> I don't understand what you mean;) >> When I wrote -current, I meant Slackware -current. >> Should the -L switch be there or not in SlackBuilds.org? :) >> >> Also, there is a difference between the permissions in SlackBuilds.org >> and Slackware's -current: >> >> SlackBuilds.org: >> find -L . \ >> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ >> -o -perm 511 \) -exec chmod 755 {} \; -o \ >> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ >> -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; >> >> Slackware's -current: >> find . \ >> \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ >> -exec chmod 755 {} \; -o \ >> \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o >> -perm 400 \) \ >> -exec chmod 644 {} \; >> >> >> 750 and 640 are not present in Slackware's SlackBuilds. > > we expect that maintainers stick to the template, so we should use -L > Maybe it is a good time to change it? It does not sound too secure. Somebody might place something bad in the source tarball. And it might be just by accident, like in my case. And bad things can follow. > > > > _______________________________________________ > 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/ > -- Best regards, Andrzej Telszewski From maticsavli6 at gmail.com Sun Apr 24 15:45:35 2016 From: maticsavli6 at gmail.com (matic) Date: Sun, 24 Apr 2016 17:45:35 +0200 Subject: [Slackbuilds-users] a bug+solution found on transcode Slackbuilds Message-ID: <571CEA1F.5000807@gmail.com> Hi, I would like to give some feedback on the https://slackbuilds.org/repository/14.1/multimedia/transcode/ First thanks for providing this package. Transcode build itself is perfectly fine but I found one bug using transcode and ffmpeg mpeg2video codec A command making me problems and the output log are attached below (transcode_failed_log.txt). There is this pointer issue that was already found on https://bitbucket.org/france/transcode-tcforge/issues/4/segfault-at-end-of-pass-1-ffmpeg-mpeg4. ffmpeg version used: ffmpeg version 2.1 Copyright (c) 2000-2013 the FFmpeg developers built on Apr 29 2014 18:30:44 with gcc 4.8.2 (GCC) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --docdir=/usr/doc/ffmpeg-2.1/html --mandir=/usr/man --disable-debug --enable-shared --disable-static --enable-pthreads --enable-libtheora --enable-libvorbis --enable-gpl --enable-version3 --enable-postproc --enable-swscale --enable-x11grab --enable-avfilter --enable-gnutls --enable-libcdio --enable-libssh --arch=x86_64 --enable-libmp3lame --enable-libx264 transcode version used: from https://slackbuilds.org/repository/14.1/multimedia/transcode/) transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team I add the correction (using https://bitbucket.org/france/transcode-tcforge/issues/4/segfault-at-end-of-pass-1-ffmpeg-mpeg4) for the command above to work in a patch (attached below). Along I modified the transcode.SlackBuild to use this patch (also attached below). It is important to first use this patch and then all others already provided in the package. This solved the problem. I hope you can modify the Slackbuild package using this solution or just to let you know... Thanks. Cheers, matic -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- $ transcode -J transform --mplayer_probe -i movie_in.MOV -y ffmpeg,null -F mpeg2video -o movie_out.MOV transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team [transcode] V: auto-probing | 11320001.MOV (OK) [transcode] V: import format | (null) in (module=mplayer) [transcode] A: auto-probing | 11320001.MOV (OK) [transcode] A: import format | PCM in (module=mplayer) [transcode] V: AV demux/sync | (1) sync AV at initial MPEG sequence [transcode] V: import frame | 1920x1080 1.78:1 encoded @ 16:9 [transcode] V: bits/pixel | 0.029 (low) [transcode] V: decoding fps,frc | 30.000,5 [transcode] V: video format | YUV420 (4:2:0) aka I420 [transcode] A: import format | 0x1 PCM [32000,16,1] 512 kbps [transcode] A: export | disabled [transcode] V: encoding fps,frc | 30.000,5 [transcode] A: bytes per frame | 2134 (2133.333333) [transcode] A: adjustment | -664 at 1000 [transcode] V: IA32/AMD64 accel | sse42 sse41 ssse3 sse3 sse2 sse mmx cmove asm [transcode] V: video buffer | 10 @ 1920x1080 [0x2] [transcode] A: audio buffer | 10 @ 32000x1x16 [import_mplayer.so] v0.1.2 (2007-11-01) (video) rendered by mplayer | (audio) rendered by mplayer [filter_transform.so] v0.98 (2014-01-04) transforms each frame according to transformations given in an input file (e.g. translation, rotate) see also filter stabilize [filter_transform.so] Image Transformation/Stabilization Settings: [filter_transform.so] input = 11320001.MOV.trf [filter_transform.so] smoothing = 15 [filter_transform.so] maxshift = -1 [filter_transform.so] maxangle = -1.000000 [filter_transform.so] crop = Keep [filter_transform.so] relative = True [filter_transform.so] invert = False [filter_transform.so] zoom = 0.000000 [filter_transform.so] optzoom = 1 [filter_transform.so] interpol = Bi-Linear (2) [filter_transform.so] sharpen = 0.800000 [filter_transform.so] Final zoom: 2.117940 [filter_unsharp.so] unsharp: 5x5:0.80 (sharpen luma) [filter_unsharp.so] unsharp: 5x5:0.40 (sharpen chroma) [filter_unsharp.so] v1.0.1 (2003-10-27) unsharp mask & gaussian blur [export_null.so] v0.1.2 (2001-08-17) (video) null | (audio) null [export_ffmpeg.so] v0.3.18 (2008-11-29) (video) Lavc55.39.100 | (audio) MPEG/AC3/PCM [import_mplayer.so] mplayer -slave -hardframedrop -vo null -ao pcm:nowaveheader:file="/tmp/mplayer2transcode-audio.jNAmHw" "11320001.MOV" > /dev/null 2>&1 [import_mplayer.so] tcextract -i /tmp/mplayer2transcode-audio.jNAmHw -x pcm -t raw [import_mplayer.so] mplayer -slave -benchmark -noframedrop -nosound -vo yuv4mpeg:file=/tmp/mplayer2transcode-video.8QVkWv "11320001.MOV" -osdlevel 0 > /dev/null 2>&1 [import_mplayer.so] tcextract -i /tmp/mplayer2transcode-video.8QVkWv -x yuv420p -t yuv4mpeg [export_ffmpeg.so] Using FFMPEG codec 'mpeg2video' (FourCC 'mpg2', MPEG2 compliant video). [export_ffmpeg.so] No profile selected [export_ffmpeg.so] warning: Error opening configuration file ./ffmpeg.cfg: No such file or directory [export_ffmpeg.so] Starting 1 thread(s) [export_ffmpeg.so] Set display aspect ratio to input [mpeg2video @ 0x4c62320] removing common factors from framerate *** Error in `transcode': free(): invalid pointer: 0x00007f14b0deb57d *** ======= Backtrace: ========= /lib64/libc.so.6(+0x7fd8a)[0x7f14c4f5dd8a] /usr/lib64/libavutil.so.52(av_freep+0xc)[0x7f14afc3eb6c] /usr/lib64/libavutil.so.52(av_opt_free+0x3c)[0x7f14afc3f6fc] /usr/lib64/libavcodec.so.55(avcodec_close+0x125)[0x7f14afee7da6] /usr/lib64/transcode/export_ffmpeg.so(tc_export+0x4d9)[0x7f14b0de8199] transcode(tcv_export+0x35)[0x413a95] transcode(tc_encoder_stop+0xa5)[0x414ed5] transcode(main+0x4745)[0x40cb15] /lib64/libc.so.6(__libc_start_main+0xf5)[0x7f14c4effd85] transcode[0x40d59d] ======= Memory map: ======== 00400000-00470000 r-xp 00000000 08:01 1235496 /usr/bin/transcode 00670000-00673000 rw-p 00070000 08:01 1235496 /usr/bin/transcode 00673000-0068b000 rw-p 00000000 00:00 0 014ee000-04f00000 rw-p 00000000 00:00 0 [heap] 7f149c000000-7f149c024000 rw-p 00000000 00:00 0 7f149c024000-7f14a0000000 ---p 00000000 00:00 0 7f14a4000000-7f14a4021000 rw-p 00000000 00:00 0 7f14a4021000-7f14a8000000 ---p 00000000 00:00 0 7f14a8d7a000-7f14a8d8f000 r-xp 00000000 08:01 1232656 /usr/lib64/libgcc_s.so.1 7f14a8d8f000-7f14a8f8f000 ---p 00015000 08:01 1232656 /usr/lib64/libgcc_s.so.1 7f14a8f8f000-7f14a8f90000 rw-p 00015000 08:01 1232656 /usr/lib64/libgcc_s.so.1 7f14ab5fc000-7f14abaf0000 rw-p 00000000 00:00 0 7f14ac0df000-7f14ac0e0000 ---p 00000000 00:00 0 7f14ac0e0000-7f14ac8e0000 rw-p 00000000 00:00 0 7f14ac8e0000-7f14ac8e1000 ---p 00000000 00:00 0 7f14ac8e1000-7f14ad0e1000 rw-p 00000000 00:00 0 [stack:14305] 7f14ad0e1000-7f14ad0e2000 ---p 00000000 00:00 0 7f14ad0e2000-7f14ad8e2000 rw-p 00000000 00:00 0 7f14ad8e2000-7f14ad8e3000 ---p 00000000 00:00 0 7f14ad8e3000-7f14ae0e3000 rw-p 00000000 00:00 0 7f14ae0e3000-7f14ae0e4000 ---p 00000000 00:00 0 7f14ae0e4000-7f14ae8e4000 rw-p 00000000 00:00 0 [stack:14298] 7f14ae8e4000-7f14ae8ea000 r-xp 00000000 08:01 1212182 /usr/lib64/libogg.so.0.8.0 7f14ae8ea000-7f14aeae9000 ---p 00006000 08:01 1212182 /usr/lib64/libogg.so.0.8.0 7f14aeae9000-7f14aeaea000 rw-p 00005000 08:01 1212182 /usr/lib64/libogg.so.0.8.0 7f14aeaea000-7f14aeb31000 r-xp 00000000 08:01 1234438 /usr/lib64/libmp3lame.so.0.0.0 7f14aeb31000-7f14aed30000 ---p 00047000 08:01 1234438 /usr/lib64/libmp3lame.so.0.0.0 7f14aed30000-7f14aed32000 rw-p 00046000 08:01 1234438 /usr/lib64/libmp3lame.so.0.0.0 7f14aed32000-7f14aed60000 rw-p 00000000 00:00 0 7f14aed60000-7f14aed79000 r-xp 00000000 08:01 1212544 /usr/lib64/libtheoradec.so.1.1.4 7f14aed79000-7f14aef78000 ---p 00019000 08:01 1212544 /usr/lib64/libtheoradec.so.1.1.4 7f14aef78000-7f14aef79000 rw-p 00018000 08:01 1212544 /usr/lib64/libtheoradec.so.1.1.4 7f14aef79000-7f14aefb7000 r-xp 00000000 08:01 1212545 /usr/lib64/libtheoraenc.so.1.1.2 7f14aefb7000-7f14af1b7000 ---p 0003e000 08:01 1212545 /usr/lib64/libtheoraenc.so.1.1.2 7f14af1b7000-7f14af1b8000 rw-p 0003e000 08:01 1212545 /usr/lib64/libtheoraenc.so.1.1.2 7f14af1b8000-7f14af1e4000 r-xp 00000000 08:01 1212700 /usr/lib64/libvorbis.so.0.4.6 7f14af1e4000-7f14af3e3000 ---p 0002c000 08:01 1212700 /usr/lib64/libvorbis.so.0.4.6 7f14af3e3000-7f14af3e4000 rw-p 0002b000 08:01 1212700 /usr/lib64/libvorbis.so.0.4.6 7f14af3e4000-7f14af697000 r-xp 00000000 08:01 1212701 /usr/lib64/libvorbisenc.so.2.0.9 7f14af697000-7f14af896000 ---p 002b3000 08:01 1212701 /usr/lib64/libvorbisenc.so.2.0.9 7f14af896000-7f14af8b2000 rw-p 002b2000 08:01 1212701 /usr/lib64/libvorbisenc.so.2.0.9 7f14af8b2000-7f14af9a8000 r-xp 00000000 08:01 1234433 /usr/lib64/libx264.so.138 7f14af9a8000-7f14afba8000 ---p 000f6000 08:01 1234433 /usr/lib64/libx264.so.138 7f14afba8000-7f14afbaa000 rw-p 000f6000 08:01 1234433 /usr/lib64/libx264.so.138 7f14afbaa000-7f14afc25000 rw-p 00000000 00:00 0 7f14afc25000-7f14afc60000 r-xp 00000000 08:01 1234449 /usr/lib64/libavutil.so.52.48.100 7f14afc60000-7f14afe60000 ---p 0003b000 08:01 1234449 /usr/lib64/libavutil.so.52.48.100 7f14afe60000-7f14afe65000 rw-p 0003b000 08:01 1234449 /usr/lib64/libavutil.so.52.48.100 7f14afe65000-7f14afe75000 rw-p 00000000 00:00 0 7f14afe75000-7f14b05c9000 r-xp 00000000 08:01 1234448 /usr/lib64/libavcodec.so.55.39.100 7f14b05c9000-7f14b07c8000 ---p 00754000 08:01 1234448 /usr/lib64/libavcodec.so.55.39.100 7f14b07c8000-7f14b0800000 rw-p 00753000 08:01 1234448 /usr/lib64/libavcodec.so.55.39.100 7f14b0800000-7f14b0ddf000 rw-p 00000000 00:00 0 7f14b0ddf000-7f14b0dec000 r-xp 00000000 08:01 416123 /usr/lib64/transcode/export_ffmpeg.so 7f14b0dec000-7f14b0feb000 ---p 0000d000 08:01 416123 /usr/lib64/transcode/export_ffmpeg.so 7f14b0feb000-7f14b0fee000 rw-p 0000c000 08:01 416123 /usr/lib64/transcode/export_ffmpeg.so 7f14b0fee000-7f14b0fef000 r-xp 00000000 08:01 416106 /usr/lib64/transcode/export_null.so 7f14b0fef000-7f14b11ee000 ---p 00001000 08:01 416106 /usr/lib64/transcode/export_null.so 7f14b11ee000-7f14b11ef000 rw-p 00000000 08:01 416106 /usr/lib64/transcode/export_null.so 7f14b11ef000-7f14b203e000 rw-p 00000000 00:00 0 7f14b203e000-7f14b2041000 r-xp 00000000 08:01 416065 /usr/lib64/transcode/filter_unsharp.so 7f14b2041000-7f14b2240000 ---p 00003000 08:01 416065 /usr/lib64/transcode/filter_unsharp.so 7f14b2240000-7f14b2241000 rw-p 00002000 08:01 416065 /usr/lib64/transcode/filter_unsharp.so 7f14b2241000-7f14b2251000 r-xp 00000000 08:01 416041 /usr/lib64/transcode/filter_transform.so 7f14b2251000-7f14b2450000 ---p 00010000 08:01 416041 /usr/lib64/transcode/filter_transform.so 7f14b2450000-7f14b2451000 r--p 0000f000 08:01 416041 /usr/lib64/transcode/filter_transform.so 7f14b2451000-7f14b2452000 rw-p 00010000 08:01 416041 /usr/lib64/transcode/filter_transform.so 7f14b2452000-7f14b2454000 r-xp 00000000 08:01 416069 /usr/lib64/transcode/import_mplayer.so 7f14b2454000-7f14b2653000 ---p 00002000 08:01 416069 /usr/lib64/transcode/import_mplayer.so 7f14b2653000-7f14b2654000 rw-p 00001000 08:01 416069 /usr/lib64/transcode/import_mplayer.so 7f14b2654000-7f14c4494000 rw-p 00000000 00:00 0 7f14c4494000-7f14c4499000 r-xp 00000000 08:01 1224541 /usr/lib64/libXdmcp.so.6.0.0 7f14c4499000-7f14c4698000 ---p 00005000 08:01 1224541 /usr/lib64/libXdmcp.so.6.0.0 7f14c4698000-7f14c4699000 rw-p 00004000 08:01 1224541 /usr/lib64/libXdmcp.so.6.0.0 7f14c4699000-7f14c469b000 r-xp 00000000 08:01 1224444 /usr/lib64/libXau.so.6.0.0 7f14c469b000-7f14c489b000 ---p 00002000 08:01 1224444 /usr/lib64/libXau.so.6.0.0 7f14c489b000-7f14c489c000 rw-p 00002000 08:01 1224444 /usr/lib64/libXau.so.6.0.0 7f14c489c000-7f14c48b9000 r-xp 00000000 08:01 1227357 /usr/lib64/libxcb.so.1.1.0 7f14c48b9000-7f14c4ab8000 ---p 0001d000 08:01 1227357 /usr/lib64/libxcb.so.1.1.0 7f14c4ab8000-7f14c4ab9000 rw-p 0001c000 08:01 1227357 /usr/lib64/libxcb.so.1.1.0 7f14c4ab9000-7f14c4abc000 r-xp 00000000 08:01 261956 /lib64/libuuid.so.1.3.0 7f14c4abc000-7f14c4cbb000 ---p 00003000 08:01 261956 /lib64/libuuid.so.1.3.0 7f14c4cbb000-7f14c4cbc000 rw-p 00002000 08:01 261956 /lib64/libuuid.so.1.3.0 7f14c4cbc000-7f14c4cdd000 r-xp 00000000 08:01 261652 /lib64/liblzma.so.5.0.5 7f14c4cdd000-7f14c4edd000 ---p 00021000 08:01 261652 /lib64/liblzma.so.5.0.5 7f14c4edd000-7f14c4ede000 rw-p 00021000 08:01 261652 /lib64/liblzma.so.5.0.5 7f14c4ede000-7f14c509d000 r-xp 00000000 08:01 289334 /lib64/libc-2.17.so 7f14c509d000-7f14c529c000 ---p 001bf000 08:01 289334 /lib64/libc-2.17.so 7f14c529c000-7f14c52a0000 r--p 001be000 08:01 289334 /lib64/libc-2.17.so 7f14c52a0000-7f14c52a2000 rw-p 001c2000 08:01 289334 /lib64/libc-2.17.so 7f14c52a2000-7f14c52a7000 rw-p 00000000 00:00 0 7f14c52a7000-7f14c52aa000 r-xp 00000000 08:01 289337 /lib64/libdl-2.17.so 7f14c52aa000-7f14c54a9000 ---p 00003000 08:01 289337 /lib64/libdl-2.17.so 7f14c54a9000-7f14c54aa000 r--p 00002000 08:01 289337 /lib64/libdl-2.17.so 7f14c54aa000-7f14c54ab000 rw-p 00003000 08:01 289337 /lib64/libdl-2.17.so 7f14c54ab000-7f14c54c0000 r-xp 00000000 08:01 261644 /lib64/libz.so.1.2.8 7f14c54c0000-7f14c56bf000 ---p 00015000 08:01 261644 /lib64/libz.so.1.2.8 7f14c56bf000-7f14c56c0000 rw-p 00014000 08:01 261644 /lib64/libz.so.1.2.8 7f14c56c0000-7f14c57c1000 r-xp 00000000 08:01 283242 /lib64/libm-2.17.so 7f14c57c1000-7f14c59c0000 ---p 00101000 08:01 283242 /lib64/libm-2.17.so 7f14c59c0000-7f14c59c1000 r--p 00100000 08:01 283242 /lib64/libm-2.17.so 7f14c59c1000-7f14c59c2000 rw-p 00101000 08:01 283242 /lib64/libm-2.17.so 7f14c59c2000-7f14c5af6000 r-xp 00000000 08:01 1224411 /usr/lib64/libX11.so.6.3.0 7f14c5af6000-7f14c5cf6000 ---p 00134000 08:01 1224411 /usr/lib64/libX11.so.6.3.0 7f14c5cf6000-7f14c5cfc000 rw-p 00134000 08:01 1224411 /usr/lib64/libX11.so.6.3.0 7f14c5cfc000-7f14c5d0d000 r-xp 00000000 08:01 1224620 /usr/lib64/libXext.so.6.4.0 7f14c5d0d000-7f14c5f0c000 ---p 00011000 08:01 1224620 /usr/lib64/libXext.so.6.4.0 7f14c5f0c000-7f14c5f0d000 rw-p 00010000 08:01 1224620 /usr/lib64/libXext.so.6.4.0 7f14c5f0d000-7f14c5f23000 r-xp 00000000 08:01 1223578 /usr/lib64/libICE.so.6.3.0 7f14c5f23000-7f14c6123000 ---p 00016000 08:01 1223578 /usr/lib64/libICE.so.6.3.0 7f14c6123000-7f14c6124000 rw-p 00016000 08:01 1223578 /usr/lib64/libICE.so.6.3.0 7f14c6124000-7f14c6128000 rw-p 00000000 00:00 0 7f14c6128000-7f14c612f000 r-xp 00000000 08:01 1223585 /usr/lib64/libSM.so.6.0.1 7f14c612f000-7f14c632e000 ---p 00007000 08:01 1223585 /usr/lib64/libSM.so.6.0.1 7f14c632e000-7f14c632f000 rw-p 00006000 08:01 1223585 /usr/lib64/libSM.so.6.0.1 7f14c632f000-7f14c6346000 r-xp 00000000 08:01 283261 /lib64/libpthread-2.17.so 7f14c6346000-7f14c6546000 ---p 00017000 08:01 283261 /lib64/libpthread-2.17.so 7f14c6546000-7f14c6547000 r--p 00017000 08:01 283261 /lib64/libpthread-2.17.so 7f14c6547000-7f14c6548000 rw-p 00018000 08:01 283261 /lib64/libpthread-2.17.so 7f14c6548000-7f14c654c000 rw-p 00000000 00:00 0 7f14c654c000-7f14c66a7000 r-xp 00000000 08:01 1212824 /usr/lib64/libxml2.so.2.9.1 7f14c66a7000-7f14c68a6000 ---p 0015b000 08:01 1212824 /usr/lib64/libxml2.so.2.9.1 7f14c68a6000-7f14c68b0000 rw-p 0015a000 08:01 1212824 /usr/lib64/libxml2.so.2.9.1 7f14c68b0000-7f14c68b1000 rw-p 00000000 00:00 0 7f14c68b1000-7f14c68d4000 r-xp 00000000 08:01 289360 /lib64/ld-2.17.so 7f14c68f1000-7f14c6a94000 rw-p 00000000 00:00 0 7f14c6ad2000-7f14c6ad4000 rw-p 00000000 00:00 0 7f14c6ad4000-7f14c6ad5000 r--p 00023000 08:01 289360 /lib64/ld-2.17.so 7f14c6ad5000-7f14c6ad7000 rw-p 00024000 08:01 289360 /lib64/ld-2.17.so 7fffb7cca000-7fffb7ceb000 rw-p 00000000 00:00 0 [stack] 7fffb7dbe000-7fffb7dbf000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall] -------------- next part -------------- #!/bin/sh # Slackware build script for transcode # Copyright 2008-2015 Heinz Wiesinger, Amsterdam, The Netherlands # All rights reserved. # # Redistribution and use of this script, with or without modification, is # permitted provided that the following conditions are met: # # 1. Redistributions of this script must retain the above copyright # notice, this list of conditions and the following disclaimer. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR ''AS IS'' AND ANY EXPRESS OR IMPLIED # WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF # MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO # EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, # SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, # PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; # OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, # WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=transcode VERSION=1.1.7 BUILD=${BUILD:-4} TAG=${TAG:-_SBo} if [ -z "$ARCH" ]; then case "$( uname -m )" in i?86) ARCH=i486 ;; arm*) ARCH=arm ;; *) ARCH=$( uname -m ) ;; esac fi CWD=$(pwd) TMP=${TMP:-/tmp/SBo} PKG=$TMP/package-$PRGNAM OUTPUT=${OUTPUT:-/tmp} if [ "$ARCH" = "i486" ]; then SLKCFLAGS="-O2 -march=i486 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "i686" ]; then SLKCFLAGS="-O2 -march=i686 -mtune=i686" LIBDIRSUFFIX="" elif [ "$ARCH" = "x86_64" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="64" else SLKCFLAGS="-O2" LIBDIRSUFFIX="" fi set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP rm -rf $PRGNAM-$VERSION tar xvf $CWD/$PRGNAM-$VERSION.tar.bz2 cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 -o -perm 511 \) \ -exec chmod 755 {} \; -o \ \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o -perm 400 \) \ -exec chmod 644 {} \; # Fix building with newer ffmpeg patch -p0 -i $CWD/transcode-1.1.7-export_ffmpeg.patch patch -p0 -i $CWD/transcode-1.1.7-ffmpeg.patch patch -p0 -i $CWD/transcode-1.1.7-ffmpeg-0.10.patch patch -p1 -i $CWD/transcode-1.1.7-ffmpeg-0.11.patch patch -p1 -i $CWD/transcode-1.1.7-preset-free.patch patch -p0 -i $CWD/transcode-1.1.7-libav-9.patch patch -p1 -i $CWD/transcode-1.1.7-preset-force.patch patch -p1 -i $CWD/transcode-1.1.7-ffmpeg2.patch patch -p1 -i $CWD/transcode-1.1.7-ffmpeg24.patch CFLAGS="$SLKCFLAGS" \ CXXFLAGS="$SLKCFLAGS" \ ./configure \ --prefix=/usr \ --libdir=/usr/lib${LIBDIRSUFFIX} \ --sysconfdir=/etc \ --localstatedir=/var \ --docdir=/usr/doc/$PRGNAM-$VERSION \ --mandir=/usr/man \ --enable-alsa \ --enable-v4l \ --enable-libv4l2=${LIBV4L:-yes} \ --enable-libv4lconvert=${LIBV4L:-yes} \ --enable-libmpeg2=${LIBMPEG2:-no} \ --enable-libmpeg2convert=${LIBMPEG2:-no} \ --enable-ogg \ --enable-vorbis \ --enable-theora \ --enable-x264=${X264:-no} \ --enable-xvid=${XVID:-no} \ --enable-faac=${FAAC:-no} \ --enable-freetype2 \ --enable-sdl \ --enable-libxml2 \ --enable-libdv=${LIBDV:-no} \ --enable-libquicktime=${QUICKTIME:-no} \ --enable-mjpegtools=${MJPEGTOOLS:-no} \ --enable-a52=${A52DEC:-no} \ --enable-lame=${LAME:-no} \ --enable-nuv \ --enable-lzo \ --enable-libpostproc \ --enable-imagemagick \ --build=$ARCH-slackware-linux make make install-strip DESTDIR=$PKG # Install headers mkdir -p $PKG/usr/include/transcode/{aclib,avilib,libtc,libtcaudio,libtcvideo} install -m 644 src/*.h $PKG/usr/include/transcode/ install -m 644 aclib/*.h $PKG/usr/include/transcode/aclib/ install -m 644 avilib/*.h $PKG/usr/include/transcode/avilib/ install -m 644 libtc/*.h $PKG/usr/include/transcode/libtc/ install -m 644 libtcaudio/*.h $PKG/usr/include/transcode/libtcaudio/ install -m 644 libtcvideo/*.h $PKG/usr/include/transcode/libtcvideo/ install -m 644 config.h $PKG/usr/include/transcode/ # remove filters shipped by other packages rm -f $PKG/usr/lib$LIBDIRSUFFIX/transcode/filter_{stabilize,transform}.* find $PKG/usr/man -type f -exec gzip -9 {} \; mkdir -p $PKG/usr/doc/$PRGNAM-$VERSION cp -a AUTHORS ChangeLog COPYING INSTALL README STYLE TODO \ $PKG/usr/doc/$PRGNAM-$VERSION # --docdir does not work mv $PKG/usr/share/doc/$PRGNAM/* $PKG/usr/doc/$PRGNAM-$VERSION/ rm -rf $PKG/usr/share cat $CWD/$PRGNAM.SlackBuild > $PKG/usr/doc/$PRGNAM-$VERSION/$PRGNAM.SlackBuild mkdir -p $PKG/install cat $CWD/slack-desc > $PKG/install/slack-desc cd $PKG /sbin/makepkg -l y -c n $OUTPUT/$PRGNAM-$VERSION-$ARCH-$BUILD$TAG.${PKGTYPE:-tgz} -------------- next part -------------- A non-text attachment was scrubbed... Name: transcode-1.1.7-export_ffmpeg.patch Type: text/x-patch Size: 824 bytes Desc: not available URL: From erik at slackbuilds.org Sun Apr 24 15:52:53 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 24 Apr 2016 10:52:53 -0500 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> Message-ID: <20160424105253.123809b4@shaggy.doo> On Sun, 24 Apr 2016 16:51:01 +0200 Andrzej Telszewski wrote: > On 24/04/16 16:41, Willy Sudiarto Raharjo wrote: > >> I don't understand what you mean;) > >> When I wrote -current, I meant Slackware -current. > >> Should the -L switch be there or not in SlackBuilds.org? :) > >> > >> Also, there is a difference between the permissions in > >> SlackBuilds.org and Slackware's -current: > >> > >> SlackBuilds.org: > >> find -L . \ > >> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ > >> -o -perm 511 \) -exec chmod 755 {} \; -o \ > >> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ > >> -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; > >> > >> Slackware's -current: > >> find . \ > >> \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 > >> \) \ -exec chmod 755 {} \; -o \ > >> \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 > >> -o -perm 400 \) \ > >> -exec chmod 644 {} \; > >> > >> > >> 750 and 640 are not present in Slackware's SlackBuilds. > > > > we expect that maintainers stick to the template, so we should use > > -L > > Maybe it is a good time to change it? It does not sound too secure. > Somebody might place something bad in the source tarball. And it > might be just by accident, like in my case. And bad things can follow. > > > This is where -L was added, with explanation: https://slackbuilds.org/cgit/templates/commit/?h=14.1&id=2ca255d617118e -- Erik From willysr at slackbuilds.org Sun Apr 24 16:03:22 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 Apr 2016 23:03:22 +0700 Subject: [Slackbuilds-users] a bug+solution found on transcode Slackbuilds In-Reply-To: <571CEA1F.5000807@gmail.com> References: <571CEA1F.5000807@gmail.com> Message-ID: > I would like to give some feedback on the > https://slackbuilds.org/repository/14.1/multimedia/transcode/ > First thanks for providing this package. > > Transcode build itself is perfectly fine but I found one bug using > transcode and ffmpeg mpeg2video codec > > A command making me problems and the output log are attached below > (transcode_failed_log.txt). There is this pointer issue that was already > found on > https://bitbucket.org/france/transcode-tcforge/issues/4/segfault-at-end-of-pass-1-ffmpeg-mpeg4. > > > ffmpeg version used: > ffmpeg version 2.1 Copyright (c) 2000-2013 the FFmpeg developers > built on Apr 29 2014 18:30:44 with gcc 4.8.2 (GCC) > configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 > --docdir=/usr/doc/ffmpeg-2.1/html --mandir=/usr/man --disable-debug > --enable-shared --disable-static --enable-pthreads --enable-libtheora > --enable-libvorbis --enable-gpl --enable-version3 --enable-postproc > --enable-swscale --enable-x11grab --enable-avfilter --enable-gnutls > --enable-libcdio --enable-libssh --arch=x86_64 --enable-libmp3lame > --enable-libx264 > > transcode version used: > from https://slackbuilds.org/repository/14.1/multimedia/transcode/) > transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode > Team > > I add the correction (using > https://bitbucket.org/france/transcode-tcforge/issues/4/segfault-at-end-of-pass-1-ffmpeg-mpeg4) > for the command above to work in a patch (attached below). Along I > modified the transcode.SlackBuild to use this patch (also attached > below). It is important to first use this patch and then all others > already provided in the package. > > This solved the problem. I hope you can modify the Slackbuild package > using this solution or just to let you know... Hi can you test using the latest ffmpeg and transcode in master branch? some changes have been merged in master branch and they are not backported to 14.1 branch anymore 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 baildon.research at googlemail.com Sun Apr 24 17:02:31 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 24 Apr 2016 18:02:31 +0100 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> Message-ID: > Maybe it is a good time to change it? It does not sound too secure. > Somebody might place something bad in the source tarball. And it might be > just by accident, like in my case. And bad things can follow. You're focussing on a small theoretical problem. I remember what actually happened with Bumblebee.... This is why we prefer not to package release candidates. This is why it's better to wait a short while after upstream releases a new version. This is why we have maintainers. This is why I test-build in a chroot. -D. From atelszewski at gmail.com Sun Apr 24 18:44:54 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 24 Apr 2016 20:44:54 +0200 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> Message-ID: On 24/04/16 19:02, David Spencer wrote: >> Maybe it is a good time to change it? It does not sound too secure. >> Somebody might place something bad in the source tarball. And it might be >> just by accident, like in my case. And bad things can follow. > > You're focussing on a small theoretical problem. I remember what > actually happened with Bumblebee.... > That's your judgment on the matter, let me have my opinion. For me it wasn't theoretical problem. > This is why we prefer not to package release candidates. This is why > it's better to wait a short while after upstream releases a new > version. This is why we have maintainers. This is why I test-build in > a chroot. > I was packaging my own source code, which contains example symlinks and it is not a beta. Not everybody is building in chroot. It looks like using "! -type l" proposed here: https://slackbuilds.org/cgit/templates/commit/?h=14.1&id=2ca255d617118e would be a better choice. makepkg should recreate the links anyway if they are about to land in the package. OK, unless there is somebody to support my claim and solve the problem in clean way, can I just use find without -L in the handful of build scripts I maintain? > _______________________________________________ > 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/ > > -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Sun Apr 24 18:52:51 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 24 Apr 2016 20:52:51 +0200 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> Message-ID: 2016-04-24 20:44 GMT+02:00 Andrzej Telszewski : > I was packaging my own source code, which contains example symlinks and it > is not a beta. [...] > OK, unless there is somebody to support my claim and solve the problem in > clean way, can I just use find without -L in the handful of build scripts I > maintain? no, please, stick to the templates: it happens sometimes that we have to do global maintenance to the scripts and we have to avoid as much as possible diverging scripts. also, if you are packaging your own source code, you could (and should) avoid yourself links outside the source directory. Matteo From atelszewski at gmail.com Sun Apr 24 19:03:26 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 24 Apr 2016 21:03:26 +0200 Subject: [Slackbuilds-users] find in SlackBuilds: again In-Reply-To: References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> <338625d0-3212-81c9-636e-54b5c670d1b9@gmail.com> Message-ID: <986ae775-3e21-f6eb-a611-347222f7516f@gmail.com> On 24/04/16 20:52, Matteo Bernardini wrote: > 2016-04-24 20:44 GMT+02:00 Andrzej Telszewski : >> I was packaging my own source code, which contains example symlinks and it >> is not a beta. > > [...] > >> OK, unless there is somebody to support my claim and solve the problem in >> clean way, can I just use find without -L in the handful of build scripts I >> maintain? > > no, please, stick to the templates: it happens sometimes that we have > to do global maintenance to the scripts and we have to avoid as much > as possible diverging scripts. > OK. > also, if you are packaging your own source code, you could (and > should) avoid yourself links outside the source directory. I can also rm the directory with the links, before doing the find. OK, after unpacking the tarball I have to prepare the extracted directory structure, so the SlackBuild does not break. Problem solved. > > 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/ > > -- Best regards, Andrzej Telszewski From maticsavli6 at gmail.com Sun Apr 24 20:10:31 2016 From: maticsavli6 at gmail.com (matic) Date: Sun, 24 Apr 2016 22:10:31 +0200 Subject: [Slackbuilds-users] a bug+solution found on transcode Slackbuilds In-Reply-To: References: <571CEA1F.5000807@gmail.com> Message-ID: <571D2837.2020109@gmail.com> On 04/24/2016 06:03 PM, Willy Sudiarto Raharjo wrote: >> I would like to give some feedback on the >> https://slackbuilds.org/repository/14.1/multimedia/transcode/ >> First thanks for providing this package. >> >> Transcode build itself is perfectly fine but I found one bug using >> transcode and ffmpeg mpeg2video codec >> >> A command making me problems and the output log are attached below >> (transcode_failed_log.txt). There is this pointer issue that was already >> found on >> https://bitbucket.org/france/transcode-tcforge/issues/4/segfault-at-end-of-pass-1-ffmpeg-mpeg4. >> >> >> ffmpeg version used: >> ffmpeg version 2.1 Copyright (c) 2000-2013 the FFmpeg developers >> built on Apr 29 2014 18:30:44 with gcc 4.8.2 (GCC) >> configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 >> --docdir=/usr/doc/ffmpeg-2.1/html --mandir=/usr/man --disable-debug >> --enable-shared --disable-static --enable-pthreads --enable-libtheora >> --enable-libvorbis --enable-gpl --enable-version3 --enable-postproc >> --enable-swscale --enable-x11grab --enable-avfilter --enable-gnutls >> --enable-libcdio --enable-libssh --arch=x86_64 --enable-libmp3lame >> --enable-libx264 >> >> transcode version used: >> from https://slackbuilds.org/repository/14.1/multimedia/transcode/) >> transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode >> Team >> >> I add the correction (using >> https://bitbucket.org/france/transcode-tcforge/issues/4/segfault-at-end-of-pass-1-ffmpeg-mpeg4) >> for the command above to work in a patch (attached below). Along I >> modified the transcode.SlackBuild to use this patch (also attached >> below). It is important to first use this patch and then all others >> already provided in the package. >> >> This solved the problem. I hope you can modify the Slackbuild package >> using this solution or just to let you know... > Hi > > can you test using the latest ffmpeg and transcode in master branch? > some changes have been merged in master branch and they are not > backported to 14.1 branch anymore Hi, Just tested your suggestion. I tried with the master branch ffmpeg and transcode. In ffmpeg I was forced to remove the following flags from the configure step to successfully compile: |--enable-libopenjpeg ||--enable-libpulse ||--enable-libvpx| For the transcode I was also forced to remove one flag: |--enable-a52| and I used the following to build (this is actually also applied in my previous email, but forget to mention): LDFLAGS='-L/usr/lib64 -L/lib64' MJPEGTOOLS=yes ./transcode.SlackBuild So at the end the ffmpeg version: ffmpeg version 2.8.6 Copyright (c) 2000-2016 the FFmpeg developers built with gcc 4.8.2 (GCC) configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 --docdir=/usr/doc/ffmpeg-2.8.6/html --mandir=/usr/man --disable-debug --enable-shared --disable-static --enable-pthreads --enable-libtheora --enable-libvorbis --enable-gpl --enable-version3 --enable-postproc --enable-swscale --enable-x11grab --enable-avfilter --enable-avresample --enable-gnutls --enable-libcdio --enable-libssh --enable-libcaca --enable-libsmbclient --enable-opengl --enable-libwavpack --enable-libfreetype --enable-libfribidi --enable-fontconfig --arch=x86_64 And transcode: transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team After all this the same command was tested but it failed the same way. I then used the patch I described in my previous email and the program finished successfully. I think that compile flags removed above shouldn't do much change here but I am not sure. What do you think? matic -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Apr 25 00:14:56 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 25 Apr 2016 07:14:56 +0700 Subject: [Slackbuilds-users] a bug+solution found on transcode Slackbuilds In-Reply-To: <571D2837.2020109@gmail.com> References: <571CEA1F.5000807@gmail.com> <571D2837.2020109@gmail.com> Message-ID: > Just tested your suggestion. I tried with the master branch ffmpeg and > transcode. In ffmpeg I was forced to remove the following flags from the > configure step to successfully compile: > > |--enable-libopenjpeg ||--enable-libpulse ||--enable-libvpx| > > > For the transcode I was also forced to remove one flag: > > |--enable-a52| > > > and I used the following to build (this is actually also applied in my > previous email, but forget to mention): > LDFLAGS='-L/usr/lib64 -L/lib64' MJPEGTOOLS=yes ./transcode.SlackBuild > > So at the end the ffmpeg version: > ffmpeg version 2.8.6 Copyright (c) 2000-2016 the FFmpeg developers > built with gcc 4.8.2 (GCC) > configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 > --docdir=/usr/doc/ffmpeg-2.8.6/html --mandir=/usr/man --disable-debug > --enable-shared --disable-static --enable-pthreads --enable-libtheora > --enable-libvorbis --enable-gpl --enable-version3 --enable-postproc > --enable-swscale --enable-x11grab --enable-avfilter --enable-avresample > --enable-gnutls --enable-libcdio --enable-libssh --enable-libcaca > --enable-libsmbclient --enable-opengl --enable-libwavpack > --enable-libfreetype --enable-libfribidi --enable-fontconfig --arch=x86_64 > > And transcode: > transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team > > After all this the same command was tested but it failed the same way. I > then used the patch I described in my previous email and the program > finished successfully. I think that compile flags removed above > shouldn't do much change here but I am not sure. What do you think? did you test this on 14.1 or Slackware Current (14.2 RC 2 at the moment) ? all scripts in master branch are prepared for next Slackware release (14.2) and those packages (openjpeg, pulseaudio, libvpx, a52) are now included in Slackware, so we enable those configure options. -- 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 Mon Apr 25 04:16:52 2016 From: thedoogster at gmail.com (Doogster) Date: Sun, 24 Apr 2016 21:16:52 -0700 Subject: [Slackbuilds-users] w3m source Message-ID: May I recommend using Debian's patched-and-updated version of W3M (https://github.com/tats/w3m) as the source for the w3m SlackBuild? It has bugfixes that aren't present in the main project on Sourceforge. e.g https://github.com/hut/ranger/issues/86#issuecomment-150709871 I did email the maintainer directly. The email bounced. That's why I'm making the recommendation here. Note that the SlackBuild, as it is, already applies no less than 5 patches from the people who maintain w3m packages for their distributions (in this case, Gentoo). So the "keep it pure" ship has already sailed. From maticsavli6 at gmail.com Mon Apr 25 05:48:24 2016 From: maticsavli6 at gmail.com (matic) Date: Mon, 25 Apr 2016 07:48:24 +0200 Subject: [Slackbuilds-users] a bug+solution found on transcode Slackbuilds In-Reply-To: References: <571CEA1F.5000807@gmail.com> <571D2837.2020109@gmail.com> Message-ID: <571DAFA8.5060007@gmail.com> On 04/25/2016 02:14 AM, Willy Sudiarto Raharjo wrote: >> Just tested your suggestion. I tried with the master branch ffmpeg and >> transcode. In ffmpeg I was forced to remove the following flags from the >> configure step to successfully compile: >> >> |--enable-libopenjpeg ||--enable-libpulse ||--enable-libvpx| >> >> >> For the transcode I was also forced to remove one flag: >> >> |--enable-a52| >> >> >> and I used the following to build (this is actually also applied in my >> previous email, but forget to mention): >> LDFLAGS='-L/usr/lib64 -L/lib64' MJPEGTOOLS=yes ./transcode.SlackBuild >> >> So at the end the ffmpeg version: >> ffmpeg version 2.8.6 Copyright (c) 2000-2016 the FFmpeg developers >> built with gcc 4.8.2 (GCC) >> configuration: --prefix=/usr --libdir=/usr/lib64 --shlibdir=/usr/lib64 >> --docdir=/usr/doc/ffmpeg-2.8.6/html --mandir=/usr/man --disable-debug >> --enable-shared --disable-static --enable-pthreads --enable-libtheora >> --enable-libvorbis --enable-gpl --enable-version3 --enable-postproc >> --enable-swscale --enable-x11grab --enable-avfilter --enable-avresample >> --enable-gnutls --enable-libcdio --enable-libssh --enable-libcaca >> --enable-libsmbclient --enable-opengl --enable-libwavpack >> --enable-libfreetype --enable-libfribidi --enable-fontconfig --arch=x86_64 >> >> And transcode: >> transcode v1.1.7 (C) 2001-2003 Thomas Oestreich, 2003-2010 Transcode Team >> >> After all this the same command was tested but it failed the same way. I >> then used the patch I described in my previous email and the program >> finished successfully. I think that compile flags removed above >> shouldn't do much change here but I am not sure. What do you think? > did you test this on 14.1 or Slackware Current (14.2 RC 2 at the moment) ? > > all scripts in master branch are prepared for next Slackware release > (14.2) and those packages (openjpeg, pulseaudio, libvpx, a52) are now > included in Slackware, so we enable those configure options. I tested this on 14.1. Unfortunately I dont have a chroot or other way to test this on current but yes I understand that stuff in master branch is for current. From nemo at chem.bg.ac.rs Mon Apr 25 22:58:33 2016 From: nemo at chem.bg.ac.rs (=?UTF-8?B?0JzQsNGA0LrQviDQktGD0ZjQutC+0LLQuNGb?=) Date: Tue, 26 Apr 2016 00:58:33 +0200 Subject: [Slackbuilds-users] find in SlackBuilds: type an perm In-Reply-To: <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> References: <453becb7-877c-abe9-849d-b87a8525b915@gmail.com> <30bb3cc6-29d6-59a3-253f-6b6d80069417@gmail.com> <4269f253-ce21-46a7-eeae-89e15c46992a@slackbuilds.org> Message-ID: On 04/24/2016 04:41 PM, Willy Sudiarto Raharjo wrote: >> I don't understand what you mean;) >> When I wrote -current, I meant Slackware -current. >> Should the -L switch be there or not in SlackBuilds.org? :) >> >> Also, there is a difference between the permissions in SlackBuilds.org >> and Slackware's -current: >> >> SlackBuilds.org: >> find -L . \ >> \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ >> -o -perm 511 \) -exec chmod 755 {} \; -o \ >> \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ >> -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; >> >> Slackware's -current: >> find . \ >> \( -perm 777 -o -perm 775 -o -perm 711 -o -perm 555 -o -perm 511 \) \ >> -exec chmod 755 {} \; -o \ >> \( -perm 666 -o -perm 664 -o -perm 600 -o -perm 444 -o -perm 440 -o >> -perm 400 \) \ >> -exec chmod 644 {} \; >> >> >> 750 and 640 are not present in Slackware's SlackBuilds. > we expect that maintainers stick to the template, so we should use -L why not using this find . \ -type d \ -exec chmod -c 755 {} \; -o \ \( -type f ! -perm /a+x \) \ -exec chmod -c 644 {} \; -o \ \( -type f -perm /a+x \) \ -exec chmod -c 755 {} \; Best regards, Marko Vujkovic -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3705 bytes Desc: S/MIME Cryptographic Signature URL: From ruben at rbn.im Thu Apr 28 17:55:28 2016 From: ruben at rbn.im (Ruben Schuller) Date: Thu, 28 Apr 2016 19:55:28 +0200 Subject: [Slackbuilds-users] xerces-c needs a version update Message-ID: <20160428195528.32bf5b5d@kiwi.kuchen> Hi! the sources for xerces-c 3.1.2 were replaced with those for version 3.1.3, which built fine here. so: --- xerces-c/xerces-c.SlackBuild 2015-07-16 20:18:09.000000000 +0200 +++ xerces-c/xerces-c.SlackBuild.new 2016-04-28 19:44:25.226830406 +0200 @@ -49,7 +49,7 @@ ################################################################ PRGNAM=xerces-c -VERSION=${VERSION:-3.1.2} +VERSION=${VERSION:-3.1.3} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} --- xerces-c/xerces-c.info 2015-07-16 20:18:09.000000000 +0200 +++ xerces-c/xerces-c.info.new 2016-04-28 19:44:53.555831079 +0200 @@ -1,8 +1,8 @@ PRGNAM="xerces-c" -VERSION="3.1.2" +VERSION="3.1.3" HOMEPAGE="http://xerces.apache.org/xerces-c/" -DOWNLOAD="http://apache.cs.utah.edu/xerces/c/3/sources/xerces-c-3.1.2.tar.gz" -MD5SUM="9eb1048939e88d6a7232c67569b23985" +DOWNLOAD="http://apache.cs.utah.edu/xerces/c/3/sources/xerces-c-3.1.3.tar.gz" +MD5SUM="70320ab0e3269e47d978a6ca0c0e1e2d" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" From slacker at slaphappygeeks.com Thu Apr 28 18:44:40 2016 From: slacker at slaphappygeeks.com (Slacker) Date: Thu, 28 Apr 2016 12:44:40 -0600 Subject: [Slackbuilds-users] xerces-c needs a version update In-Reply-To: <20160428195528.32bf5b5d@kiwi.kuchen> References: <20160428195528.32bf5b5d@kiwi.kuchen> Message-ID: <57225A18.8000108@slaphappygeeks.com> Thanks for the heads-up, I have all my SlackBuilds queued locally and waiting for final update when 14.2 is released! That will include xerces-c. Glad to hear it builds for you with a simple version bump! Thanks On 04/28/2016 11:55 AM, Ruben Schuller wrote: > Hi! > > the sources for xerces-c 3.1.2 were replaced with those for version > 3.1.3, which built fine here. so: > > --- xerces-c/xerces-c.SlackBuild 2015-07-16 20:18:09.000000000 > +0200 > +++ xerces-c/xerces-c.SlackBuild.new 2016-04-28 > 19:44:25.226830406 +0200 > @@ -49,7 +49,7 @@ > ################################################################ > > PRGNAM=xerces-c > -VERSION=${VERSION:-3.1.2} > +VERSION=${VERSION:-3.1.3} > BUILD=${BUILD:-1} > TAG=${TAG:-_SBo} > > --- xerces-c/xerces-c.info 2015-07-16 20:18:09.000000000 +0200 > +++ xerces-c/xerces-c.info.new 2016-04-28 19:44:53.555831079 > +0200 > @@ -1,8 +1,8 @@ > PRGNAM="xerces-c" > -VERSION="3.1.2" > +VERSION="3.1.3" > HOMEPAGE="http://xerces.apache.org/xerces-c/" > -DOWNLOAD="http://apache.cs.utah.edu/xerces/c/3/sources/xerces-c-3.1.2.tar.gz" > -MD5SUM="9eb1048939e88d6a7232c67569b23985" > +DOWNLOAD="http://apache.cs.utah.edu/xerces/c/3/sources/xerces-c-3.1.3.tar.gz" > +MD5SUM="70320ab0e3269e47d978a6ca0c0e1e2d" > DOWNLOAD_x86_64="" > MD5SUM_x86_64="" > REQUIRES="" > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From willysr at slackbuilds.org Fri Apr 29 11:13:38 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 29 Apr 2016 18:13:38 +0700 Subject: [Slackbuilds-users] xerces-c needs a version update In-Reply-To: <57225A18.8000108@slaphappygeeks.com> References: <20160428195528.32bf5b5d@kiwi.kuchen> <57225A18.8000108@slaphappygeeks.com> Message-ID: <9e7c1a01-4066-12f8-b94f-710fd6d6a2ce@slackbuilds.org> > Thanks for the heads-up, I have all my SlackBuilds queued locally and > waiting for final update when 14.2 is released! That will include xerces-c. > > Glad to hear it builds for you with a simple version bump! > > Thanks > > On 04/28/2016 11:55 AM, Ruben Schuller wrote: >> Hi! >> >> the sources for xerces-c 3.1.2 were replaced with those for version >> 3.1.3, which built fine here. so: >> >> --- xerces-c/xerces-c.SlackBuild 2015-07-16 20:18:09.000000000 >> +0200 >> +++ xerces-c/xerces-c.SlackBuild.new 2016-04-28 >> 19:44:25.226830406 +0200 >> @@ -49,7 +49,7 @@ >> ################################################################ >> >> PRGNAM=xerces-c >> -VERSION=${VERSION:-3.1.2} >> +VERSION=${VERSION:-3.1.3} >> BUILD=${BUILD:-1} >> TAG=${TAG:-_SBo} >> >> --- xerces-c/xerces-c.info 2015-07-16 20:18:09.000000000 +0200 >> +++ xerces-c/xerces-c.info.new 2016-04-28 19:44:53.555831079 >> +0200 >> @@ -1,8 +1,8 @@ >> PRGNAM="xerces-c" >> -VERSION="3.1.2" >> +VERSION="3.1.3" >> HOMEPAGE="http://xerces.apache.org/xerces-c/" >> -DOWNLOAD="http://apache.cs.utah.edu/xerces/c/3/sources/xerces-c-3.1.2.tar.gz" >> >> -MD5SUM="9eb1048939e88d6a7232c67569b23985" >> +DOWNLOAD="http://apache.cs.utah.edu/xerces/c/3/sources/xerces-c-3.1.3.tar.gz" >> >> +MD5SUM="70320ab0e3269e47d978a6ca0c0e1e2d" >> DOWNLOAD_x86_64="" >> MD5SUM_x86_64="" >> REQUIRES="" applied to my branch already 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 slackalaxy at gmail.com Fri Apr 29 15:35:55 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 29 Apr 2016 18:35:55 +0300 Subject: [Slackbuilds-users] source download from bitbucket Message-ID: hello! I want to submit a slackbuild for a program hosted at bitbucket. This is the download link: https://bitbucket.org/cistrome/cistrome-applications-harvard/get/7bcbf7953a8b.zip if it is downloaded with wget, the archive is named 7bcbf7953a8b.zip if it is clicked from a browser, the saved archive is named cistrome-cistrome-applications-harvard-7bcbf7953a8b.zip MD5SUMs are the same. Can someone tell me how to make my slackbuild accept both names? bye Petar -------------- next part -------------- An HTML attachment was scrubbed... URL: From markus.ka.rinne at gmail.com Fri Apr 29 15:45:11 2016 From: markus.ka.rinne at gmail.com (Markus Rinne) Date: Fri, 29 Apr 2016 18:45:11 +0300 Subject: [Slackbuilds-users] source download from bitbucket In-Reply-To: References: Message-ID: <20160429154511.GA1472@tursas> On Fri, Apr 29, 2016 at 06:35:55PM +0300, Petar Petrov wrote: > MD5SUMs are the same. Can someone tell me how to make my slackbuild accept > both names? if [ -e $CWD/$VERSION.tar.gz ]; then tar xvf $CWD/$VERSION.tar.gz else tar xvf $CWD/$PRGNAM-$VERSION.tar.gz fi This was suggested here: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-May/014228.html Markus From slackalaxy at gmail.com Fri Apr 29 16:00:04 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 29 Apr 2016 19:00:04 +0300 Subject: [Slackbuilds-users] source download from bitbucket In-Reply-To: <20160429154511.GA1472@tursas> References: <20160429154511.GA1472@tursas> Message-ID: thank you! does the job! -petar 2016-04-29 18:45 GMT+03:00 Markus Rinne : > On Fri, Apr 29, 2016 at 06:35:55PM +0300, Petar Petrov wrote: > > MD5SUMs are the same. Can someone tell me how to make my slackbuild > accept > > both names? > > if [ -e $CWD/$VERSION.tar.gz ]; then > tar xvf $CWD/$VERSION.tar.gz > else > tar xvf $CWD/$PRGNAM-$VERSION.tar.gz > fi > > This was suggested here: > > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-May/014228.html > > Markus > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nastavs at gmail.com Sat Apr 30 00:11:19 2016 From: nastavs at gmail.com (Shrivats) Date: Sat, 30 Apr 2016 05:41:19 +0530 Subject: [Slackbuilds-users] A couple notes on SBCL slackbuilds Message-ID: Hi, I managed to build SBCL on Slackware 14.1 and found a couple things that can be mentioned on that SBo page. * The slackbuild includes building pdf manuals. Building PDF requires any variant of TeX installed. I turned it off and opted just for building (emacs) info files. * The SBo build(1.3.1) is not on the latest(1.3.5). The latest at 1.3.5 was released a few days ago[1]. However, that version is not available from Sourceforge page, last I saw. So, I built 1.3.4 instead. Can these be mentioned on SBo? Shrivats [1]: http://www.sbcl.org/news.html?1.3.5#1.3.5 From nastavs at gmail.com Sat Apr 30 00:14:26 2016 From: nastavs at gmail.com (Shrivats) Date: Sat, 30 Apr 2016 05:44:26 +0530 Subject: [Slackbuilds-users] SlackBuild version bumps on 14.1? Message-ID: Hi, I understand that 14.2 is on RC stage and we are all anxiously waiting for it to be released. So, are we holding off on accepting new version updates to existing SlackBuilds on SBo? I have KeePass that requires a version update and I'm waiting to hear back from someone before I go uploading it on SBo. Shrivats From willysr at slackbuilds.org Sat Apr 30 12:07:46 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 30 Apr 2016 19:07:46 +0700 Subject: [Slackbuilds-users] A couple notes on SBCL slackbuilds In-Reply-To: References: Message-ID: > I managed to build SBCL on Slackware 14.1 and found a couple things that > can be mentioned on that SBo page. > > * The slackbuild includes building pdf manuals. Building PDF requires > any variant of TeX installed. I turned it off and opted just for > building (emacs) info files. SBo assumed that users are using full installation of Slackware and that includes tetex so it will build properly. > * The SBo build(1.3.1) is not on the latest(1.3.5). The latest at > 1.3.5 was released a few days ago[1]. However, that version is not > available from Sourceforge page, last I saw. So, I built 1.3.4 > instead. updated on my branch for master to 1.3.5 -- 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 Apr 30 12:15:44 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 30 Apr 2016 19:15:44 +0700 Subject: [Slackbuilds-users] SlackBuild version bumps on 14.1? In-Reply-To: References: Message-ID: > I understand that 14.2 is on RC stage and we are all anxiously waiting > for it to be released. So, are we holding off on accepting new version > updates to existing SlackBuilds on SBo? > > I have KeePass that requires a version update and I'm waiting to hear > back from someone before I go uploading it on SBo. if you have updates, please send the diffs/patches through this list and we can review it, but only for 14.2 14.1 will only receive updates whenever it's considered necessary -- 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: