From zhu.qunying at gmail.com Wed Jun 1 00:08:42 2016 From: zhu.qunying at gmail.com (Qun-Ying) Date: Tue, 31 May 2016 17:08:42 -0700 Subject: [Slackbuilds-users] update refind to 0.10.3 Message-ID: Attached is the build script update to refind to 0.10.3 for current. -- Qun-Ying -------------- next part -------------- A non-text attachment was scrubbed... Name: refind.patch Type: text/x-patch Size: 1953 bytes Desc: not available URL: From willysr at slackbuilds.org Wed Jun 1 00:14:58 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Jun 2016 07:14:58 +0700 Subject: [Slackbuilds-users] update refind to 0.10.3 In-Reply-To: References: Message-ID: <142dfc48-dd9a-d3af-71ed-16243c14c265@slackbuilds.org> > Attached is the build script update to refind to 0.10.3 for current. Applied to my branch with some minor modification - keep the 486 and tgz format - move man pages to correct location -- 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 Jun 1 00:43:43 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Jun 2016 07:43:43 +0700 Subject: [Slackbuilds-users] p7zip vulnerabilities In-Reply-To: References: Message-ID: > p7zip 9.20.1 has two security issues : > > CVE-2015-1038: > p7zip 9.20.1 allows remote attackers to write to arbitrary files via a > symlink attack in an archive. > > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-1038 > https://sourceforge.net/p/p7zip/bugs/147/#2f9c > > CVE-2016-2335: > 7zip UDF CInArchive::ReadFileItem Code Execution Vulnerability > > http://www.talosintel.com/reports/TALOS-2016-0094/ > https://sourceforge.net/p/p7zip/discussion/383043/thread/9d0fb86b/#1dba > > The latest p7zip, ie. 15.14.1, is not affected by CVE-2015-1038, but > affected by CVE-2016-2335 and also by CVE-2016-2334. > > In attachment, the patches for these issues, and for the slackbuild. > > Notes: > > p7zip.SlackBuild.patch > Applies the patches to fix vulnerabilities in p7zip 9.20.1 Applied 9.20.1 patches in my branch 15.14.1 still break jalview here 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 thomas at beingboiled.info Wed Jun 1 01:29:39 2016 From: thomas at beingboiled.info (Thomas Morper) Date: Wed, 1 Jun 2016 03:29:39 +0200 (CEST) Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 In-Reply-To: References: Message-ID: On Mon, 30 May 2016, David Spencer wrote: > 1. academic/Xyce > > http://pastebin.com/nsMwxhgR > > It looks like an underlinking error, but I can't see anything wrong > with the link. There is a new version 6.4 upstream, I have tried it, > but the same linking problem happens. Maybe its dep > libraries/trilinos is involved This one is a bit tricky... the problem indeed is trilinos which can't be built with neither "atlas" (as stated in the info file) nor "blas" and "lapack" as currently present on SBo. atlas is a very fragile library and highly dependent on certain compiler versions and CPU timings! The build is very old and the README is unclear on how to merge the atlas and lapack libraries to get the lapack functions that atlas doesn't cover. On the other hand, blas and lapack 3.6.0 are too new for trilinos. 3.6.0 replaced some deprecated functions, but the wrapper in trilinos still uses the old function names, resulting in a libepetra.so with unresolved symbols that will make Xyce fail. So, this gets us the following options: 1) Ditch atlas and build trilinos with blas and lapack downgraded to version 3.5.0. Easy, unless this breaks other packages. 2) Ditch atlas and patch trilinos to work with blas and lapack in version 3.6.0. There's no readymade patch available and I don't know how to do this as this involves FORTRAN code. 3) Bring atlas up to date and merge it with lapack for a fully functional high-performance library. Ideally done by a maintainer who understands how atlas works, aka "not me". Any other options? -- From citizen.anon.x at gmail.com Wed Jun 1 03:11:11 2016 From: citizen.anon.x at gmail.com (Citizen X) Date: Tue, 31 May 2016 23:11:11 -0400 Subject: [Slackbuilds-users] Nvidia Message-ID: FYI, Nvidia driver builds are out of date. Nvidia is now up to 361.45 as of May 24th. Kernel and driver builds are still at 352.63. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Jun 1 05:13:59 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Jun 2016 12:13:59 +0700 Subject: [Slackbuilds-users] Nvidia In-Reply-To: References: Message-ID: <494e1f03-36be-341d-fb93-fef43c82a03e@slackbuilds.org> > FYI, Nvidia driver builds are out of date. Nvidia is now up to 361.45 as of > May 24th. Kernel and driver builds are still at 352.63. in master, it has been updated for 361.42 -- 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 Jun 1 05:29:45 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Jun 2016 12:29:45 +0700 Subject: [Slackbuilds-users] Aigaion errors In-Reply-To: <72C4E4C7-614D-4EDC-B80A-10834EC8C4F8@gmail.com> References: <72C4E4C7-614D-4EDC-B80A-10834EC8C4F8@gmail.com> Message-ID: <149e1a0b-0794-97df-7145-7dc119e4d20f@slackbuilds.org> > I?ve installed Aigaion 2.2.b on OS X 10.11.3 with MAMP 3.0.7.3/MySQL 5.5.38/PHP > 5.6.2. > > URL is http://localhost:8888/index.php > > Installation proceeded OK. (Modded index.php to include non-standard HTTP port.) > > I?ve attached a screen grab of the error message. > > Is this a directory permissions issue? I'm not sure this is the right place to ask since this is SlackBuild-related mailing list and definitely for Linux, not Mac :) -- 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 jensi at 192.168.1.28 Wed Jun 1 09:49:10 2016 From: jensi at 192.168.1.28 (jens) Date: Wed, 1 Jun 2016 11:49:10 +0200 Subject: [Slackbuilds-users] Aigaion errors In-Reply-To: <72C4E4C7-614D-4EDC-B80A-10834EC8C4F8@gmail.com> References: <72C4E4C7-614D-4EDC-B80A-10834EC8C4F8@gmail.com> Message-ID: <979d2be2-f377-7468-158c-981d640dc5eb@tuxane.com> Hello, > > Installation proceeded OK. (Modded index.php to include non-standard > HTTP port.) Looks like the index.php could be the problem. Normally this error means that something is in the file which shouldn't be there like a UTF-8 BOM or even line breakes before the session starts I would try the original file and see if it is working then > > > _______________________________________________ > 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 s.arcus at open-t.co.uk Wed Jun 1 12:29:24 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 1 Jun 2016 13:29:24 +0100 Subject: [Slackbuilds-users] Navit GPS In-Reply-To: <8cb3e7b9-bdfe-dbf3-d366-eb67d5f3685c@open-t.co.uk> References: <8cb3e7b9-bdfe-dbf3-d366-eb67d5f3685c@open-t.co.uk> Message-ID: <96702008-ebb4-5ac6-84c2-b79c47c6be25@open-t.co.uk> On 01/06/16 00:19, Sebastian Arcus wrote: > I note that SBo doesn't have Navit in the repositories > (www.navit-project.org). I've been using it for years, mainly as it > appears to be the only gps navigation software capable of downloading > and using offline the map of an entire country from OpenStreetMap in > vector format (thus available at all zoom levels). > > Do I remember correctly that Navit used to be available on SBo, and > then got removed as it needed some dependencies which couldn't be > satisfied at the time? I have just compiled and installed it on a > Slack64 -current box, and it seems to have worked out just fine with > no extra dependencies needed - using cmake. As nobody has replied, I will guess there is no particular reason against having Navit in SBo repositories - so I'd like to try and build the scripts for it. As Navit now uses cmake, and I've been scratching my head against the cmake docs for a while, is there any project already in the SBo repositories which uses cmake - to draw some inspiration as to how to include cmake in the .SlackBuilds file and run it in non-interractive mode? From ryan.q at linux.com Wed Jun 1 13:00:38 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 1 Jun 2016 06:00:38 -0700 Subject: [Slackbuilds-users] Navit GPS In-Reply-To: <96702008-ebb4-5ac6-84c2-b79c47c6be25@open-t.co.uk> References: <8cb3e7b9-bdfe-dbf3-d366-eb67d5f3685c@open-t.co.uk> <96702008-ebb4-5ac6-84c2-b79c47c6be25@open-t.co.uk> Message-ID: > As nobody has replied, I will guess there is no particular reason against having Navit in SBo repositories - so I'd like to try and build the scripts for it. As Navit now uses cmake, and I've been scratching my head against the cmake docs for a while, is there any project already in the SBo repositories which uses cmake - to draw some inspiration as to how to include cmake in the .SlackBuilds file and run it in non-interractive mode? This would be a good start: https://slackbuilds.org/templates/cmake-template.SlackBuild -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Wed Jun 1 14:35:29 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 1 Jun 2016 15:35:29 +0100 Subject: [Slackbuilds-users] Navit GPS In-Reply-To: References: <8cb3e7b9-bdfe-dbf3-d366-eb67d5f3685c@open-t.co.uk> <96702008-ebb4-5ac6-84c2-b79c47c6be25@open-t.co.uk> Message-ID: On 01/06/16 14:00, Ryan P.C. McQuen wrote: > > > > As nobody has replied, I will guess there is no particular reason > against having Navit in SBo repositories - so I'd like to try and > build the scripts for it. As Navit now uses cmake, and I've been > scratching my head against the cmake docs for a while, is there any > project already in the SBo repositories which uses cmake - to draw > some inspiration as to how to include cmake in the .SlackBuilds file > and run it in non-interractive mode? > > This would be a good start: > > https://slackbuilds.org/templates/cmake-template.SlackBuild > Brilliant - thank you! I had no idea there is a separate template for cmake. From willysr at slackbuilds.org Wed Jun 1 14:48:03 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 1 Jun 2016 21:48:03 +0700 Subject: [Slackbuilds-users] Navit GPS In-Reply-To: References: <8cb3e7b9-bdfe-dbf3-d366-eb67d5f3685c@open-t.co.uk> <96702008-ebb4-5ac6-84c2-b79c47c6be25@open-t.co.uk> Message-ID: <8c7781d2-9c2e-c680-357e-3db6a592258b@slackbuilds.org> > Brilliant - thank you! I had no idea there is a separate template for > cmake. We have templates for almost all kind of possible development platform/tools https://slackbuilds.org/templates/ -- 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 andrew at omniarch.is Thu Jun 2 03:14:24 2016 From: andrew at omniarch.is (Andrew) Date: Thu, 2 Jun 2016 15:14:24 +1200 Subject: [Slackbuilds-users] Update tarsnap to version 1.0.37 and new maintainer. Message-ID: <081badc2-5166-2635-de11-a40b1fafd163@omniarch.is> T?n? koutou katoa, Having discussed the updated version of tarsnap with it's prior maintainer, he has decided to pass the flame to me. I'm uncertain of the proper procedure, but below is the diff of the old and new files. diff -u -r -N tarsnap/README tarsnap-old/README --- tarsnap/README 2016-06-02 14:39:59.401457815 +1200 +++ tarsnap-old/README 2016-06-02 14:23:11.480531869 +1200 @@ -1,8 +1,7 @@ -Tarsnap: Online backups for the truly paranoid +Encrypted Snapshotted Remote Backup Service -Colin Pecival's program 'tarsnap' to be used as a part of Tarsnap. Tarsnap -is an online snapshotted backup service featuring client-side encryption -and deduplication. +Colin Percival's program 'tarsnap' to be used as a part of Tarsnap. Tarsnap +is an online encrypted snapshotted backup service. -Please note that this is only the client. In order to use Tarsnap you must -subscribe to the service. Please visit https://tarsnap.com for further details. +Please note that this is only the client. In order to use tarsnap, one must +subscribe to the Tarsnap service - see their website for details. diff -u -r -N tarsnap/slack-desc tarsnap-old/slack-desc --- tarsnap/slack-desc 2016-06-02 14:45:40.076432784 +1200 +++ tarsnap-old/slack-desc 2016-06-02 14:23:11.480531869 +1200 @@ -6,14 +6,14 @@ # customary to leave one space after the ':' except on otherwise blank lines. |-----handy-ruler------------------------------------------------------| -tarsnap: tarsnap (Client-Side Encrpyted Snapshotted Remote Backup Service) +tarsnap: tarsnap (Encrypted Snapshotted Remote Backup Service) tarsnap: tarsnap: Colin Percival's program 'tarsnap' to be used as a part of Tarsnap. -tarsnap: Tarsnap is an online snapshotted backup service featuring client-side -tarsnap: encryption and deduplication. +tarsnap: Tarsnap is an online encrypted snapshotted backup service. +tarsnap: +tarsnap: http://www.tarsnap.com tarsnap: tarsnap: -tarsnap: Homepage: http://www.tarsnap.com tarsnap: tarsnap: tarsnap: diff -u -r -N tarsnap/tarsnap.SlackBuild tarsnap-old/tarsnap.SlackBuild --- tarsnap/tarsnap.SlackBuild 2016-06-02 14:53:56.122396338 +1200 +++ tarsnap-old/tarsnap.SlackBuild 2016-06-02 14:23:11.480531869 +1200 @@ -22,7 +22,7 @@ PRGNAM=tarsnap -VERSION=${VERSION:-1.0.37} +VERSION=${VERSION:-1.0.35} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff -u -r -N tarsnap/tarsnap.info tarsnap-old/tarsnap.info --- tarsnap/tarsnap.info 2016-06-02 14:52:35.939402230 +1200 +++ tarsnap-old/tarsnap.info 2016-06-02 14:23:11.480531869 +1200 @@ -1,10 +1,10 @@ PRGNAM="tarsnap" -VERSION="1.0.37" +VERSION="1.0.35" HOMEPAGE="http://www.tarsnap.com" -DOWNLOAD="https://www.tarsnap.com/download/tarsnap-autoconf-1.0.37.tgz" -MD5SUM="755492b15a2ab53286182c3ba5f05c94" +DOWNLOAD="https://www.tarsnap.com/download/tarsnap-autoconf-1.0.35.tgz" +MD5SUM="74daeff5479ec6f101a903f4047b526f" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -MAINTAINER="Andrew Stevens" -EMAIL="andrew at omniarch.is" +MAINTAINER="Ryan P.C. McQuen" +EMAIL="ryan.q at linux.com" Regards, Andrew Stevens From mats.bertil.tegner at gmail.com Thu Jun 2 07:11:10 2016 From: mats.bertil.tegner at gmail.com (Mats Bertil Tegner) Date: Thu, 2 Jun 2016 09:11:10 +0200 Subject: [Slackbuilds-users] Vivaldi In-Reply-To: References: Message-ID: On 2016-05-03 10:08, Matteo Bernardini wrote: > It has been reported on LQ that the download link for vivaldi is broken > > https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page4.html#post5538863 > > I had a look at the directory where the vivaldi people publish their > releases and concluded that they often remove old ones, breaking the > scripts in our repository. > > so I had prepared a patch in my branch to: > - self host their tarballs avoiding breakage; > - move from snapshots to the stable release (seems it's more up2date > than the snapshots ;) ). > > https://slackbuilds.org/cgit/slackbuilds/commit/?h=ponce-for-14.2&id=13031fffc0af538e73e9a6919a4d44aca5e89525 > > Matteo Vivaldi-stable have just been updated to 1.2: https://vivaldi.net/en-US/teamblog/120-vivaldi-1-2-with-mouse-gestures https://update.vivaldi.com/update/1.0/relnotes/1.2.490.35.html Mats From alik at ejik.org Thu Jun 2 17:35:36 2016 From: alik at ejik.org (Alexander Verbovetsky) Date: Thu, 02 Jun 2016 20:35:36 +0300 Subject: [Slackbuilds-users] DOWNLOAD advice for github In-Reply-To: References: Message-ID: <1464888936.323564.626150921.5F0C4645@webmail.messagingengine.com> Hello, On Sat, May 14, 2016, at 19:35, David Spencer wrote: > Hi everybody, > > For maintainers, here's some advice about what to put in DOWNLOAD in > the .info file for github URLs. > > NOTE: you don't need to change any of your existing files, this is > just some general advice that we hope you will find helpful and > interesting and useful. Also, this is not related to 14.2, it is > actually some new advice about github that Heinz worked out yesterday > :) > > Hopefully, most of you know already that github is "clever" with > download URLs. It uses an HTTP "content disposition" header to tell > browsers the name of the archive that githib has dynamically created. > But by default wget and curl do not use the "content disposition" > header and use the last component of the URL as a filename. Therefore > (until now) our SlackBuilds have needed to try both possible names for > the download, e.g. > > tar xvf $CWD/v$VERSION.tar.gz || tar xvf $CWD/$PRGNAM-$VERSION.tar.gz > > So, here's the new advice: Heinz has worked out that if we use (for > example) > > DOWNLOAD="https://github.com/trizen/clyrics/archive/0.04/clyrics-0.04.tar.gz" > > then the archive will *always* be named clyrics-0.04.tar.gz, even if > we use wget or curl, and so we can just do the usual tar command in > the SlackBuild: > > tar xvf $CWD/$PRGNAM-$VERSION.tar.gz > > Apparently this will even work nicely for projects that include the > project name in the git tag, e.g. > > DOWNLOAD="https://github.com/christophgysin/pasystray/archive/0.5.2/pasystray-0.5.2.tar.gz" > > so we can now stop using confusing and ugly commands like these: > > rm -rf $PRGNAM-$PRGNAM-$VERSION > tar xvf $CWD/$PRGNAM-$PRGNAM-$VERSION.tar.gz > cd $PRGNAM-$PRGNAM-$VERSION > > I hope this is helpful to you. Thanks to Heinz for finally working > out the right way of handling this! > > Best regards to everybody > -D. > > ps. If I've made any mistakes above, corrections will be gratefully > received :D Apparently, there are some minor variations here, e.g., wget https://github.com/Microsoft/cpprestsdk/archive/2.8.0/cpprestsdk-2.8.0.tar.gz doesn't work (with ERROR 404: Not Found), but with additional letter "v" before the version number, it works: wget https://github.com/Microsoft/cpprestsdk/archive/v2.8.0/cpprestsdk-2.8.0.tar.gz Best regards, Alexander From bryanlharris at gmail.com Thu Jun 2 17:50:03 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Thu, 2 Jun 2016 13:50:03 -0400 Subject: [Slackbuilds-users] Question re: slackbuild script Message-ID: Hello all, I realize there is a freeze, but I want to ask for my own reference. And then once 14.2 comes out I would try to submit this unless someone has already done so. I have not done one of these in years, and I am running into the github download problem. In the info file I have it like this: DOWNLOAD="https://github.com/koct9i/ioping/archive/v0.9.tar.gz" And then in the SBo script I have it like this: tar xvf $CWD/v0.9.tar.gz I tried the advice from a previous email and here is how it looks. wget https://github.com/koct9i/ioping/archive/0.9/ioping-0.9.tar.gz --2016-06-02 13:45:25-- https://github.com/koct9i/ioping/archive/0.9/ioping-0.9.tar.gz Resolving github.com (github.com)... 192.30.252.123 Connecting to github.com (github.com)|192.30.252.123|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://codeload.github.com/koct9i/ioping/tar.gz/0.9/ioping-0.9 [following] --2016-06-02 13:45:25-- https://codeload.github.com/koct9i/ioping/tar.gz/0.9/ioping-0.9 Resolving codeload.github.com (codeload.github.com)... 192.30.252.160 Connecting to codeload.github.com (codeload.github.com)|192.30.252.160|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2016-06-02 13:45:26 ERROR 404: Not Found. Was my workaround an acceptable way to handle the situation? Any help/advice is appreciated. V/r, Bryan From lynx at panix.com Thu Jun 2 17:53:09 2016 From: lynx at panix.com (Arthur W. Green) Date: Thu, 2 Jun 2016 11:53:09 -0600 Subject: [Slackbuilds-users] DOWNLOAD advice for github In-Reply-To: References: Message-ID: <1b74ee80-af87-4617-b831-30565e19b4a2@panix.com> On 14/05/16 10:35, David Spencer wrote: > For maintainers, here's some advice about what to put in DOWNLOAD in > the .info file for github URLs. Thanks to both of you for working this out! How should an .info's MD5SUM field be treated for sources that may readily change (e.g., github URLs)? My recollection is that sbopkg wasn't happy with blank ("") MD5SUM fields, although not being an sbopkg user myself, I don't know if this is still the case. Excuse me if I missed the message where this was addressed. \\ Arthur From baildon.research at googlemail.com Thu Jun 2 18:58:47 2016 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 2 Jun 2016 19:58:47 +0100 Subject: [Slackbuilds-users] Question re: slackbuild script In-Reply-To: References: Message-ID: > I tried the advice from a previous email and here is how it looks. > > wget https://github.com/koct9i/ioping/archive/0.9/ioping-0.9.tar.gz > --2016-06-02 13:45:25-- > https://github.com/koct9i/ioping/archive/0.9/ioping-0.9.tar.gz > Resolving github.com (github.com)... 192.30.252.123 > Connecting to github.com (github.com)|192.30.252.123|:443... connected. > HTTP request sent, awaiting response... 302 Found > Location: https://codeload.github.com/koct9i/ioping/tar.gz/0.9/ioping-0.9 > [following] > --2016-06-02 13:45:25-- > https://codeload.github.com/koct9i/ioping/tar.gz/0.9/ioping-0.9 > Resolving codeload.github.com (codeload.github.com)... 192.30.252.160 > Connecting to codeload.github.com > (codeload.github.com)|192.30.252.160|:443... connected. > HTTP request sent, awaiting response... 404 Not Found > 2016-06-02 13:45:26 ERROR 404: Not Found. Hi Bryan, since I wrote the previous advice we have found some more details and special cases, and this is one of those special cases, and it needs quite a long explanation. Sorry! The general form for a github download is https://github.com/koct9i//archive//-.tar.gz is the repository name (in your case 'ioping'), ideally the same as the SlackBuild PRGNAM can be one of two things: ideally a "git tag", or if necessary a "git commit" (short commit id is ok) The git tag can be got by looking at the 'releases' page https://github.com/koct9i/ioping/releases or the 'tags' page https://github.com/koct9i/ioping/tags to see what tags they have created. In your case the tag is 'v0.9' (note the 'v', you can't omit the 'v') can be one of two things: a version number derived from the git tag, or a full length git commit. This is where the new details become important. Lots of projects like to prefix the 'git tag' (what we would call the version number) with v, and apparently ioping is one of those projects. But because the 'v' looks silly in a version number, Github's download handler apparently has some code to remove 'v' from the start of the version number, if present. Otherwise if the tag is *not* a number that starts with a v, then Github just uses the git tag. [please see footnote!] So the VERSION and DOWNLOAD that you want are VERSION="0.9" DOWNLOAD="https://github.com/koct9i/ioping/archive/v0.9/ioping-0.9.tar.gz" If you look inside ioping-0.9.tar.gz you will see that the top level directory is named ioping-0.9 (this is good, because it looks just like a traditional tar.gz source archive). Therefore the commands you want inside the SlackBuild are rm -rf $PRGNAM-$VERSION tar xvf $PRGNAM-$VERSION.tar.gz cd $PRGNAM-$VERSION Note that "$PRGNAM-$VERSION" must (almost always) be exactly the same in all three commands! Hope this is clear -- I'm going to have to cover the "git-commit" case in a reply to the other email from Arthur. Best regards -D. [FOOTNOTE] In my previous email I wrote that stupid-stupid-projects that prefix their tags with the project name don't need special code. This is *wrong*. I accidentally chose a project that creates two sets of tags... anyway, I'll have to write another email about that, too. From baildon.research at googlemail.com Thu Jun 2 19:03:42 2016 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 2 Jun 2016 20:03:42 +0100 Subject: [Slackbuilds-users] Question re: slackbuild script In-Reply-To: References: Message-ID: Damn! Sorry! That should be rm -rf $PRGNAM-$VERSION tar xvf $CWD/PRGNAM-$VERSION.tar.gz cd $PRGNAM-$VERSION Note the $CWD/ exactly like in the templates. Sorry again -D. From baildon.research at googlemail.com Thu Jun 2 19:12:43 2016 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 2 Jun 2016 20:12:43 +0100 Subject: [Slackbuilds-users] DOWNLOAD advice for github In-Reply-To: <1464888936.323564.626150921.5F0C4645@webmail.messagingengine.com> References: <1464888936.323564.626150921.5F0C4645@webmail.messagingengine.com> Message-ID: Hi Alexander, Yes you are exactly right. > wget https://github.com/Microsoft/cpprestsdk/archive/v2.8.0/cpprestsdk-2.8.0.tar.gz The first one "v2.8.0" is a git tag from the Github repository (see the 'tags' or 'releases' page), but the second one "-2.8.0.tar.gz" should not have "v". Apparently the Github download code removes "v" from the tag when it creates the archive. This isn't documented anywhere.... so thanks for working it out on your own :) Best regards -D. From baildon.research at googlemail.com Thu Jun 2 19:40:52 2016 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 2 Jun 2016 20:40:52 +0100 Subject: [Slackbuilds-users] DOWNLOAD advice for github In-Reply-To: <1b74ee80-af87-4617-b831-30565e19b4a2@panix.com> References: <1b74ee80-af87-4617-b831-30565e19b4a2@panix.com> Message-ID: Hi Arthur, > How should an .info's MD5SUM field be treated for sources that may > readily change (e.g., github URLs)? My recollection is that sbopkg > wasn't happy with blank ("") MD5SUM fields, although not being an sbopkg > user myself, I don't know if this is still the case. With Git (including Github, Bitbucket, mercurial, svn, etc), if there isn't a tagged version then you would choose a specific commit, which will download with the same MD5SUM every time. e.g. https://slackbuilds.org/slackbuilds/14.1/libraries/luasocket/luasocket.info But for everything else -- If the copyright terms allow redistribution, you can grab a copy with a known MD5SUM and make it available on your own website if you have one, or some maintainers even use their own Dropbox, or there's Ryan's SBo Direct Links on Sourceforge (just email me or Willy or Ryan if you need to use that). e.g. https://slackbuilds.org/cgit/slackbuilds/tree/network/GeoIP/GeoIP.info But if you're not allowed to redistribute it -- The only solution we have is to put a warning in the README :-( e.g. https://slackbuilds.org/repository/14.1/multimedia/google-talkplugin/ Hope this is helpful (well, almost helpful) Best regards -D. From ryan.q at linux.com Thu Jun 2 19:54:35 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Thu, 2 Jun 2016 12:54:35 -0700 Subject: [Slackbuilds-users] Question re: slackbuild script In-Reply-To: References: Message-ID: > > > rm -rf $PRGNAM-$VERSION > tar xvf $CWD/PRGNAM-$VERSION.tar.gz > cd $PRGNAM-$VERSION > > Note the $CWD/ exactly like in the templates. > I think you have a typo there: sed 's/PRGNAM/\$PRGNAM/' foo -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Thu Jun 2 20:06:30 2016 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 2 Jun 2016 21:06:30 +0100 Subject: [Slackbuilds-users] Question re: slackbuild script In-Reply-To: References: Message-ID: > I think you have a typo there: > > sed 's/PRGNAM/\$PRGNAM/' foo Thanks Ryan, you are right of course, thanks for proofreading :) -D. From baildon.research at googlemail.com Thu Jun 2 20:14:07 2016 From: baildon.research at googlemail.com (David Spencer) Date: Thu, 2 Jun 2016 21:14:07 +0100 Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 In-Reply-To: References: Message-ID: >> 1. academic/Xyce > So, this gets us the following options: > > 1) Ditch atlas and build trilinos with blas and lapack downgraded to > version 3.5.0. Easy, unless this breaks other packages. > > 2) Ditch atlas and patch trilinos to work with blas and lapack in version > 3.6.0. There's no readymade patch available and I don't know how to do > this as this involves FORTRAN code. > > 3) Bring atlas up to date and merge it with lapack for a fully functional > high-performance library. Ideally done by a maintainer who understands > how atlas works, aka "not me". Well you're better than me :) I'm too tired to try these options tonight, but -- *Thank you*! That's a great explanation. I'll try soon and report back here :D Best regards -D. From bryanlharris at gmail.com Fri Jun 3 00:00:11 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Thu, 2 Jun 2016 20:00:11 -0400 Subject: [Slackbuilds-users] Question re: slackbuild script In-Reply-To: References: Message-ID: Oh I think I see. It looks like I need the tag as another folder name. Thanks for your help. V/r, Bryan On Thu, Jun 2, 2016 at 4:06 PM, David Spencer wrote: >> I think you have a typo there: >> >> sed 's/PRGNAM/\$PRGNAM/' foo > > Thanks Ryan, you are right of course, thanks for proofreading :) > -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/ > From mats.bertil.tegner at gmail.com Fri Jun 3 00:03:46 2016 From: mats.bertil.tegner at gmail.com (Mats Bertil Tegner) Date: Fri, 3 Jun 2016 02:03:46 +0200 Subject: [Slackbuilds-users] Vivaldi In-Reply-To: References: Message-ID: <60410ecb-dc5b-e311-d82f-6b2eba5a36ca@gmail.com> On 2016-05-03 10:08, Matteo Bernardini wrote: > It has been reported on LQ that the download link for vivaldi is broken > > https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/page4.html#post5538863 > > I had a look at the directory where the vivaldi people publish their > releases and concluded that they often remove old ones, breaking the > scripts in our repository. > > so I had prepared a patch in my branch to: > - self host their tarballs avoiding breakage; > - move from snapshots to the stable release (seems it's more up2date > than the snapshots ;) ). > > https://slackbuilds.org/cgit/slackbuilds/commit/?h=ponce-for-14.2&id=13031fffc0af538e73e9a6919a4d44aca5e89525 > > Matteo Vivaldi-stable have just been updated to 1.2: https://vivaldi.net/en-US/teamblog/120-vivaldi-1-2-with-mouse-gestures https://update.vivaldi.com/update/1.0/relnotes/1.2.490.39.html Mats From kingbeowulf at gmail.com Fri Jun 3 16:29:27 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 3 Jun 2016 09:29:27 -0700 Subject: [Slackbuilds-users] release 14.2 almost here! Please test the following Message-ID: Hello Slackers! If you have time, please test a few of my build scripts in SBo master on your hardware. I want to make sure these are ready for go-live. You can email me off-list (see .info). I'll be traveling for work all next week and will try to get fixes in place this weekend. Thanks! These depend on either kernel or system lib versions, etc. The remainder are just simple libs or apps and have been fairly stable over most of the -current cycle. I am particularly interested in nvidia bug reports: I don't have any legacy cards to test, ATM, just one GTX 660. Also ping me off-list if you run "unsupported" multilib on nvidia and are having issues. multimedia/wxcam network/mumble network/murmur system/nvidia-driver system/nvidia-kernel system/nvidia-legacy304-driver system/nvidia-legacy304-kernel system/nvidia-legacy340-driver system/nvidia-legacy340-kernel system/qemu Please note that I will hold off on any version updates unless needed for a bug fix. Thanks! Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Fri Jun 3 17:30:05 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Fri, 3 Jun 2016 19:30:05 +0200 Subject: [Slackbuilds-users] release 14.2 almost here! Please test the following In-Reply-To: References: Message-ID: On 03/06/16 18:29, King Beowulf wrote: > Hello Slackers! > > If you have time, please test a few of my build scripts in SBo master on > your hardware. I want to make sure these are ready for go-live. You > can email me off-list (see .info). I'll be traveling for work all next > week and will try to get fixes in place this weekend. Thanks! > > These depend on either kernel or system lib versions, etc. The remainder > are just simple libs or apps and have been fairly stable over most of > the -current cycle. > > I am particularly interested in nvidia bug reports: I don't have any > legacy cards to test, ATM, just one GTX 660. Also ping me off-list if > you run "unsupported" multilib on nvidia and are having issues. > > system/qemu I've built version 2.6.0 more less at the time the SlackBuild was updated. I haven't noticed any problems building and running. When it comes to running, I'm emulating Win7 with remote-viewer. -- Best regards, Andrzej Telszewski From mats.bertil.tegner at gmail.com Fri Jun 3 17:41:58 2016 From: mats.bertil.tegner at gmail.com (Mats Bertil Tegner) Date: Fri, 3 Jun 2016 19:41:58 +0200 Subject: [Slackbuilds-users] release 14.2 almost here! Please test the following In-Reply-To: References: Message-ID: On 2016-06-03 18:29, King Beowulf wrote: > Hello Slackers! > > If you have time, please test a few of my build scripts in SBo master on > your hardware. I want to make sure these are ready for go-live. You > can email me off-list (see .info). I'll be traveling for work all next > week and will try to get fixes in place this weekend. Thanks! > > These depend on either kernel or system lib versions, etc. The remainder > are just simple libs or apps and have been fairly stable over most of > the -current cycle. > > I am particularly interested in nvidia bug reports: I don't have any > legacy cards to test, ATM, just one GTX 660. Also ping me off-list if > you run "unsupported" multilib on nvidia and are having issues. > system/nvidia-legacy340-driver > system/nvidia-legacy340-kernel > Thanks! > Ed Hello Ed, The nvidia-legacy driver and kernel packages 340.96 seems to build fine under -current64 using kernel 4.4.12. Mats -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 884 bytes Desc: OpenPGP digital signature URL: From laitcg at gmail.com Fri Jun 3 17:47:11 2016 From: laitcg at gmail.com (Jack S. Lai) Date: Fri, 3 Jun 2016 12:47:11 -0500 Subject: [Slackbuilds-users] release 14.2 almost here! Please test the following In-Reply-To: References: Message-ID: On Fri, Jun 3, 2016 at 11:29 AM, King Beowulf wrote: > Hello Slackers! > > If you have time, please test a few of my build scripts in SBo master on > your hardware. I want to make sure these are ready for go-live. You > > system/nvidia-driver > Missing README and .info file needs updated specs for v361.42 > system/nvidia-kernel > No issues Compiled on current, kernel 4.4.12 -- When you want a computer system that works, just choose Linux. When you want a computer system that works, just, choose Microsoft. -------------- next part -------------- An HTML attachment was scrubbed... URL: From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Sat Jun 4 10:15:24 2016 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Sat, 04 Jun 2016 12:15:24 +0200 Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 In-Reply-To: References: Message-ID: <5752AA3C.8010004@skmail.ikp.physik.tu-darmstadt.de> On 06/01/2016 03:29 AM, Thomas Morper wrote: > On Mon, 30 May 2016, David Spencer wrote: > >> 1. academic/Xyce >> >> http://pastebin.com/nsMwxhgR >> >> It looks like an underlinking error, but I can't see anything wrong >> with the link. There is a new version 6.4 upstream, I have tried it, >> but the same linking problem happens. Maybe its dep >> libraries/trilinos is involved > > This one is a bit tricky... the problem indeed is trilinos which can't be > built with neither "atlas" (as stated in the info file) nor "blas" and > "lapack" as currently present on SBo. > >... > > 3) Bring atlas up to date and merge it with lapack for a fully functional > high-performance library. Ideally done by a maintainer who understands > how atlas works, aka "not me". > > Any other options? > Hello! Last time I tried to upgrade ATLAS I failed. I'll try again, since I do have some more spare time next week. Nevertheless, ATLAS does not provide much more than a BLAS implementation. Thus, if trillions has problems with the newest LAPACK version, the LAPACK+ATLAS combination should stick to version 3.5.0 of LAPACK. There is also OpenBLAS on Slackbuilds. To my knowledge, in spite of its name, it can provide also LAPACK functionality. But the maintainer of OpenBLAS may need to give more details on this. Best regards, Serban Udrea From arkadiusz at drabczyk.org Sat Jun 4 19:25:48 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sat, 4 Jun 2016 21:25:48 +0200 Subject: [Slackbuilds-users] [PATCH 2/3] Bump development/global to 6.5.4 In-Reply-To: <1465068349-26362-1-git-send-email-arkadiusz@drabczyk.org> References: <1465068349-26362-1-git-send-email-arkadiusz@drabczyk.org> Message-ID: <1465068349-26362-2-git-send-email-arkadiusz@drabczyk.org> --- development/global/global.SlackBuild | 2 +- development/global/global.info | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/development/global/global.SlackBuild b/development/global/global.SlackBuild index a3ca767..af9ed7a 100644 --- a/development/global/global.SlackBuild +++ b/development/global/global.SlackBuild @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=global -VERSION=${VERSION:-6.5.2} +VERSION=${VERSION:-6.5.4} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff --git a/development/global/global.info b/development/global/global.info index 015c545..0059bab 100644 --- a/development/global/global.info +++ b/development/global/global.info @@ -1,8 +1,8 @@ PRGNAM="global" -VERSION="6.5.2" +VERSION="6.5.4" HOMEPAGE="http://www.gnu.org/software/global/" -DOWNLOAD="http://tamacom.com/global/global-6.5.2.tar.gz" -MD5SUM="c154bc9ba77e7630068e2916cb9531c5" +DOWNLOAD="http://tamacom.com/global/global-6.5.4.tar.gz" +MD5SUM="a6693598b4cd0890c648aa2cbfa92fe7" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -- 2.7.4 From arkadiusz at drabczyk.org Sat Jun 4 19:25:49 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sat, 4 Jun 2016 21:25:49 +0200 Subject: [Slackbuilds-users] [PATCH 3/3] Add a requirement for misc/moreutils In-Reply-To: <1465068349-26362-1-git-send-email-arkadiusz@drabczyk.org> References: <1465068349-26362-1-git-send-email-arkadiusz@drabczyk.org> Message-ID: <1465068349-26362-3-git-send-email-arkadiusz@drabczyk.org> --- misc/moreutils/moreutils.info | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/misc/moreutils/moreutils.info b/misc/moreutils/moreutils.info index 99cdf6f..0ae901c 100644 --- a/misc/moreutils/moreutils.info +++ b/misc/moreutils/moreutils.info @@ -5,6 +5,6 @@ DOWNLOAD="http://drabczyk.org/moreutils-0.59.tar.gz" MD5SUM="718900463335f8a9405493c5db5cf4bb" DOWNLOAD_x86_64="" MD5SUM_x86_64="" -REQUIRES="" +REQUIRES="perl-IPC-Run" MAINTAINER="Arkadiusz Drabczyk" EMAIL="arkadiusz at drabczyk.org" -- 2.7.4 From arkadiusz at drabczyk.org Sat Jun 4 19:25:47 2016 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Sat, 4 Jun 2016 21:25:47 +0200 Subject: [Slackbuilds-users] [PATCH 1/3] Bump misc/moreutils to 0.59 Message-ID: <1465068349-26362-1-git-send-email-arkadiusz@drabczyk.org> --- misc/moreutils/moreutils.SlackBuild | 2 +- misc/moreutils/moreutils.info | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/misc/moreutils/moreutils.SlackBuild b/misc/moreutils/moreutils.SlackBuild index e0c2fa9..757529a 100644 --- a/misc/moreutils/moreutils.SlackBuild +++ b/misc/moreutils/moreutils.SlackBuild @@ -23,7 +23,7 @@ # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. PRGNAM=moreutils -VERSION=${VERSION:-0.57} +VERSION=${VERSION:-0.59} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} diff --git a/misc/moreutils/moreutils.info b/misc/moreutils/moreutils.info index 738bceb..99cdf6f 100644 --- a/misc/moreutils/moreutils.info +++ b/misc/moreutils/moreutils.info @@ -1,8 +1,8 @@ PRGNAM="moreutils" -VERSION="0.57" +VERSION="0.59" HOMEPAGE="https://joeyh.name/code/moreutils" -DOWNLOAD="http://drabczyk.org/moreutils-0.57.tar.gz" -MD5SUM="7268b9061281bcd550408218c7ec8ae9" +DOWNLOAD="http://drabczyk.org/moreutils-0.59.tar.gz" +MD5SUM="718900463335f8a9405493c5db5cf4bb" DOWNLOAD_x86_64="" MD5SUM_x86_64="" REQUIRES="" -- 2.7.4 From ts at websafe.pl Sun Jun 5 02:12:07 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 5 Jun 2016 04:12:07 +0200 Subject: [Slackbuilds-users] Problem building truecrypt Message-ID: <2358692b-61a1-965e-16ff-1eeb040b28b1@websafe.pl> Hello, building https://slackbuilds.org/repository/14.1/system/truecrypt/ ends up with: Compiling Aeskey.c In file included from ../Crypto/Aeskey.c:28:0: ../Crypto/Aeskey.c: In function ?aes_decrypt_key256?: ../Crypto/Aeskey.c:524:34: warning: operation on ?ss[4]? may be undefined [-Wsequence-point] cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:524:25: note: in expansion of macro ?ff? cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); ^ ../Crypto/Aeskey.c:524:34: warning: operation on ?ss[4]? may be undefined [-Wsequence-point] cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:524:25: note: in expansion of macro ?ff? cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); ^ ../Crypto/Aeskey.c:524:34: warning: operation on ?ss[4]? may be undefined [-Wsequence-point] cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:524:25: note: in expansion of macro ?ff? cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); ^ ../Crypto/Aeskey.c:525:34: warning: operation on ?ss[5]? may be undefined [-Wsequence-point] cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:525:25: note: in expansion of macro ?ff? cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); ^ ../Crypto/Aeskey.c:525:34: warning: operation on ?ss[5]? may be undefined [-Wsequence-point] cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:525:25: note: in expansion of macro ?ff? cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); ^ ../Crypto/Aeskey.c:525:34: warning: operation on ?ss[5]? may be undefined [-Wsequence-point] cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:525:25: note: in expansion of macro ?ff? cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); ^ ../Crypto/Aeskey.c:526:34: warning: operation on ?ss[6]? may be undefined [-Wsequence-point] cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:526:25: note: in expansion of macro ?ff? cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); ^ ../Crypto/Aeskey.c:526:34: warning: operation on ?ss[6]? may be undefined [-Wsequence-point] cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:526:25: note: in expansion of macro ?ff? cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); ^ ../Crypto/Aeskey.c:526:34: warning: operation on ?ss[6]? may be undefined [-Wsequence-point] cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:526:25: note: in expansion of macro ?ff? cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); ^ ../Crypto/Aeskey.c:527:34: warning: operation on ?ss[7]? may be undefined [-Wsequence-point] cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:527:25: note: in expansion of macro ?ff? cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); ^ ../Crypto/Aeskey.c:527:34: warning: operation on ?ss[7]? may be undefined [-Wsequence-point] cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:527:25: note: in expansion of macro ?ff? cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); ^ ../Crypto/Aeskey.c:527:34: warning: operation on ?ss[7]? may be undefined [-Wsequence-point] cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); ^ ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) ^ ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ ^ ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) ^ ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? #define ff(x) inv_mcol(x) ^ ../Crypto/Aeskey.c:527:25: note: in expansion of macro ?ff? cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); ^ Compiling Aestab.c Compiling Blowfish.c Compiling Cast.c Compiling Des.c Compiling Rmd160.c Compiling Serpent.c Compiling Sha1.c Compiling Sha2.c Compiling Twofish.c Compiling Whirlpool.c Compiling Crc.c Compiling Endian.c Compiling GfMul.c Compiling Pkcs5.c Compiling SecurityToken.cpp Updating library Volume.a Compiling FuseService.cpp Updating library Driver.a Compiling CoreBase.cpp Compiling CoreException.cpp Compiling FatFormatter.cpp Compiling HostDevice.cpp Compiling MountOptions.cpp Compiling RandomNumberGenerator.cpp Compiling VolumeCreator.cpp Compiling CoreService.cpp Compiling CoreServiceRequest.cpp Compiling CoreServiceResponse.cpp Compiling CoreUnix.cpp Compiling CoreLinux.cpp Updating library Core.a Precompiling SystemPrecompiled.h Compiling Application.cpp In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0: /usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function ?static TrueCrypt::FilePath TrueCrypt::Application::GetConfigFilePath(const wxString&, bool)?: /usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error: ?wxStandardPaths::wxStandardPaths()? is protected wxStandardPaths() { } ^ TextUserInterface.h:99:19: error: within this context In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0: /usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function ?static TrueCrypt::DirectoryPath TrueCrypt::Application::GetExecutableDirectory()?: /usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error: ?wxStandardPaths::wxStandardPaths()? is protected wxStandardPaths() { } ^ TextUserInterface.h:124:47: error: within this context In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0: /usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function ?static TrueCrypt::FilePath TrueCrypt::Application::GetExecutablePath()?: /usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error: ?wxStandardPaths::wxStandardPaths()? is protected wxStandardPaths() { } ^ TextUserInterface.h:129:35: error: within this context make[1]: *** [Application.o] Error 1 make: *** [all] Error 2 Is it just me? -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sun Jun 5 03:11:23 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Jun 2016 10:11:23 +0700 Subject: [Slackbuilds-users] Problem building truecrypt In-Reply-To: <2358692b-61a1-965e-16ff-1eeb040b28b1@websafe.pl> References: <2358692b-61a1-965e-16ff-1eeb040b28b1@websafe.pl> Message-ID: <17fc6626-e3cb-bddc-815d-d919d9e7b2e4@slackbuilds.org> > building https://slackbuilds.org/repository/14.1/system/truecrypt/ > ends up with: > > > Compiling Aeskey.c > In file included from ../Crypto/Aeskey.c:28:0: > ../Crypto/Aeskey.c: In function ?aes_decrypt_key256?: > ../Crypto/Aeskey.c:524:34: warning: operation on ?ss[4]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:524:25: note: in expansion of macro ?ff? > cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); > ^ > ../Crypto/Aeskey.c:524:34: warning: operation on ?ss[4]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:524:25: note: in expansion of macro ?ff? > cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); > ^ > ../Crypto/Aeskey.c:524:34: warning: operation on ?ss[4]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:524:25: note: in expansion of macro ?ff? > cx->ks[v(56,(4))] = ff(ss[4] = word_in(key, 4)); > ^ > ../Crypto/Aeskey.c:525:34: warning: operation on ?ss[5]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:525:25: note: in expansion of macro ?ff? > cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); > ^ > ../Crypto/Aeskey.c:525:34: warning: operation on ?ss[5]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:525:25: note: in expansion of macro ?ff? > cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); > ^ > ../Crypto/Aeskey.c:525:34: warning: operation on ?ss[5]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:525:25: note: in expansion of macro ?ff? > cx->ks[v(56,(5))] = ff(ss[5] = word_in(key, 5)); > ^ > ../Crypto/Aeskey.c:526:34: warning: operation on ?ss[6]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:526:25: note: in expansion of macro ?ff? > cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); > ^ > ../Crypto/Aeskey.c:526:34: warning: operation on ?ss[6]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:526:25: note: in expansion of macro ?ff? > cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); > ^ > ../Crypto/Aeskey.c:526:34: warning: operation on ?ss[6]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:526:25: note: in expansion of macro ?ff? > cx->ks[v(56,(6))] = ff(ss[6] = word_in(key, 6)); > ^ > ../Crypto/Aeskey.c:527:34: warning: operation on ?ss[7]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:527:25: note: in expansion of macro ?ff? > cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); > ^ > ../Crypto/Aeskey.c:527:34: warning: operation on ?ss[7]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:527:25: note: in expansion of macro ?ff? > cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); > ^ > ../Crypto/Aeskey.c:527:34: warning: operation on ?ss[7]? may be > undefined [-Wsequence-point] > cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); > ^ > ../Crypto/Aesopt.h:541:37: note: in definition of macro ?bval? > #define bval(x,n) ((uint_8t)((x) >> (8 * (n)))) > ^ > ../Crypto/Aesopt.h:689:17: note: in expansion of macro ?vf1? > ^ tab[2][bval(vf(x,2,c),rf(2,c))] \ > ^ > ../Crypto/Aesopt.h:709:27: note: in expansion of macro ?four_tables? > #define inv_mcol(x) four_tables(x,t_use(i,m),vf1,rf1,0) > ^ > ../Crypto/Aeskey.c:249:17: note: in expansion of macro ?inv_mcol? > #define ff(x) inv_mcol(x) > ^ > ../Crypto/Aeskey.c:527:25: note: in expansion of macro ?ff? > cx->ks[v(56,(7))] = ff(ss[7] = word_in(key, 7)); > ^ > Compiling Aestab.c > Compiling Blowfish.c > Compiling Cast.c > Compiling Des.c > Compiling Rmd160.c > Compiling Serpent.c > Compiling Sha1.c > Compiling Sha2.c > Compiling Twofish.c > Compiling Whirlpool.c > Compiling Crc.c > Compiling Endian.c > Compiling GfMul.c > Compiling Pkcs5.c > Compiling SecurityToken.cpp > Updating library Volume.a > Compiling FuseService.cpp > Updating library Driver.a > Compiling CoreBase.cpp > Compiling CoreException.cpp > Compiling FatFormatter.cpp > Compiling HostDevice.cpp > Compiling MountOptions.cpp > Compiling RandomNumberGenerator.cpp > Compiling VolumeCreator.cpp > Compiling CoreService.cpp > Compiling CoreServiceRequest.cpp > Compiling CoreServiceResponse.cpp > Compiling CoreUnix.cpp > Compiling CoreLinux.cpp > Updating library Core.a > Precompiling SystemPrecompiled.h > Compiling Application.cpp > In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0: > /usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function > ?static TrueCrypt::FilePath > TrueCrypt::Application::GetConfigFilePath(const wxString&, bool)?: > /usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error: > ?wxStandardPaths::wxStandardPaths()? is protected > wxStandardPaths() { } > ^ > TextUserInterface.h:99:19: error: within this context > In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0: > /usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function > ?static TrueCrypt::DirectoryPath > TrueCrypt::Application::GetExecutableDirectory()?: > /usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error: > ?wxStandardPaths::wxStandardPaths()? is protected > wxStandardPaths() { } > ^ > TextUserInterface.h:124:47: error: within this context > In file included from /usr/include/wx-3.0/wx/stdpaths.h:185:0: > /usr/include/wx-3.0/wx/unix/stdpaths.h: In static member function > ?static TrueCrypt::FilePath TrueCrypt::Application::GetExecutablePath()?: > /usr/include/wx-3.0/wx/unix/stdpaths.h:56:5: error: > ?wxStandardPaths::wxStandardPaths()? is protected > wxStandardPaths() { } > ^ > TextUserInterface.h:129:35: error: within this context > make[1]: *** [Application.o] Error 1 > make: *** [all] Error 2 > > > > Is it just me? Tested on lates current and it worked fine truecrypt: MD5SUM check for truecrypt-7.1a.tar.gz ... OK Building package truecrypt-7.1a-x86_64-1_SBo.tgz ... OK Installing package truecrypt-7.1a-x86_64-1_SBo.tgz ... OK From your error message, it seems that you have wxGTK3 instead of wxPython as requested -- 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 skaendo at excite.com Sun Jun 5 03:50:39 2016 From: skaendo at excite.com (Ed Ender) Date: Sat, 04 Jun 2016 23:50:39 -0400 Subject: [Slackbuilds-users] TrueCrypt Message-ID: <20160604235039.21949@web006.roc2.bluetie.com> TrueCrypt is actually outdated, vulnerable and unmaintained. You might be better off using VeraCrypt, it will also handle the old TrueCrypt containers. Eric has it prebuilt in his repo. From ts at websafe.pl Sun Jun 5 04:25:21 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 5 Jun 2016 06:25:21 +0200 Subject: [Slackbuilds-users] Problem building truecrypt In-Reply-To: <17fc6626-e3cb-bddc-815d-d919d9e7b2e4@slackbuilds.org> References: <2358692b-61a1-965e-16ff-1eeb040b28b1@websafe.pl> <17fc6626-e3cb-bddc-815d-d919d9e7b2e4@slackbuilds.org> Message-ID: <41a4f506-dd97-1401-3326-2917cd2737de@websafe.pl> On 06/05/2016 05:11 AM, Willy Sudiarto Raharjo wrote: > Tested on lates current and it worked fine > truecrypt: > MD5SUM check for truecrypt-7.1a.tar.gz ... OK > Building package truecrypt-7.1a-x86_64-1_SBo.tgz ... OK > Installing package truecrypt-7.1a-x86_64-1_SBo.tgz ... OK > From your error message, it seems that you have wxGTK3 instead of > wxPython as requested I'm on 14.1 and: ~~~~ # ls -1 /var/log/packages/wx* /var/log/packages/wxGTK3-3.0.2-x86_64-2_SBo /var/log/packages/wxPython-2.8.12.1-x86_64-2_SBo ~~~~ I'll removepkg wxGTK3 and try again... OK, after removing of wxGTK3-3.0.2 I'm getting another error: ~~~~ ... Compiling CoreUnix.cpp Compiling CoreLinux.cpp Updating library Core.a make[1]: wx-config: Command not found make[1]: wx-config: Command not found Precompiling SystemPrecompiled.h SystemPrecompiled.h:9:19: fatal error: wx/wx.h: No such file or directory #include ^ compilation terminated. make[1]: *** [SystemPrecompiled.h.gch] Error 1 make: *** [all] Error 2 ~~~~ And finally I solved this problem by doing: ~~~~ slpkg -s sbo wxGTK ~~~~ after that I had: ~~~~ # ls -1 /var/log/packages/wx* /var/log/packages/wxGTK-2.8.12-x86_64-3_SBo /var/log/packages/wxPython-2.8.12.1-x86_64-2_SBo ~~~~ and I was able to build truecrypt :-) I'm not sure why I had wxGTK3 but I'll probably see it in a few days ;-) -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From ts at websafe.pl Sun Jun 5 04:45:13 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 5 Jun 2016 06:45:13 +0200 Subject: [Slackbuilds-users] TrueCrypt In-Reply-To: <20160604235039.21949@web006.roc2.bluetie.com> References: <20160604235039.21949@web006.roc2.bluetie.com> Message-ID: <837a7a9c-49a4-233a-4c54-bba6ace6eb0f@websafe.pl> On 06/05/2016 05:50 AM, Ed Ender wrote: > TrueCrypt is actually outdated, vulnerable and unmaintained. > You might be better off using VeraCrypt, it will also handle the old TrueCrypt containers. Eric has it prebuilt in his repo. I'm aware, on Windows I'm using Veracrypt, but I can't find Veracrypt on slackbuilds.org... I see zulucrypt? https://slackbuilds.org/repository/14.1/system/zuluCrypt/?search=veracrypt I need this only for encrypted volumes on pendrives (containing my password-protected private keys) used on both linux and Windows machines. -- Z powa?aniem / Best regards / Mit freundlichen Gr??en, Thomas Szteliga websafe.pl Complete IT Solutions for Enterprises ul. Mazowiecka 8 PL 45-308 Opole https://websafe.pl/ NIP: 754-209-69-74 REGON: 531327129 BANK: PL 31 1050 1504 1000 0090 6254 7428 -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sun Jun 5 04:50:10 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Jun 2016 11:50:10 +0700 Subject: [Slackbuilds-users] Problem building truecrypt In-Reply-To: <41a4f506-dd97-1401-3326-2917cd2737de@websafe.pl> References: <2358692b-61a1-965e-16ff-1eeb040b28b1@websafe.pl> <17fc6626-e3cb-bddc-815d-d919d9e7b2e4@slackbuilds.org> <41a4f506-dd97-1401-3326-2917cd2737de@websafe.pl> Message-ID: > I'm on 14.1 and: > > ~~~~ > # ls -1 /var/log/packages/wx* > /var/log/packages/wxGTK3-3.0.2-x86_64-2_SBo > /var/log/packages/wxPython-2.8.12.1-x86_64-2_SBo > ~~~~ > > > I'll removepkg wxGTK3 and try again... > > OK, after removing of wxGTK3-3.0.2 I'm getting another error: > > ~~~~ > ... > Compiling CoreUnix.cpp > Compiling CoreLinux.cpp > Updating library Core.a > make[1]: wx-config: Command not found > make[1]: wx-config: Command not found > Precompiling SystemPrecompiled.h > SystemPrecompiled.h:9:19: fatal error: wx/wx.h: No such file or directory > #include > ^ > compilation terminated. > make[1]: *** [SystemPrecompiled.h.gch] Error 1 > make: *** [all] Error 2 > ~~~~ > > > And finally I solved this problem by doing: > > ~~~~ > slpkg -s sbo wxGTK > ~~~~ > > > after that I had: > > ~~~~ > # ls -1 /var/log/packages/wx* > /var/log/packages/wxGTK-2.8.12-x86_64-3_SBo > /var/log/packages/wxPython-2.8.12.1-x86_64-2_SBo > ~~~~ > > > and I was able to build truecrypt :-) > > > I'm not sure why I had wxGTK3 but I'll probably see it > in a few days ;-) wxPython = wxGTK + Python Bindings so you basically can use wxGTK or wxPython to build truecrypt the problem is that you probably install wxGTK3 later and this package overwrite wx-config that is used by other applications that depends on wxGTK/wxPython to check it's existence. You can solve it by reinstalling wxGTK or wxPython as mentioned in the README. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Jun 5 07:05:31 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Jun 2016 14:05:31 +0700 Subject: [Slackbuilds-users] [PATCH 1/3] Bump misc/moreutils to 0.59 In-Reply-To: <1465068349-26362-1-git-send-email-arkadiusz@drabczyk.org> References: <1465068349-26362-1-git-send-email-arkadiusz@drabczyk.org> Message-ID: > misc/moreutils/moreutils.SlackBuild | 2 +- > misc/moreutils/moreutils.info | 6 +++--- > 2 files changed, 4 insertions(+), 4 deletions(-) Applied in my branch with minor update to prevent it overwriting a man page from Slackware's openssl package -- 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 Sun Jun 5 08:41:16 2016 From: belka at caraus.de (Eugen Wissner) Date: Sun, 05 Jun 2016 10:41:16 +0200 Subject: [Slackbuilds-users] hhvm 3.13.2 Message-ID: <1465116076.1626.3.camel@caraus.de> And again hhvm update. git patch against master. Please add BUILDING.txt aswell. Since I'm not using the original git source, it could be useful for people to know how they can build hhvm (maybe an update or the master) Regards Eugene -------------- next part -------------- A non-text attachment was scrubbed... Name: hhvm.diff Type: text/x-patch Size: 1414 bytes Desc: not available URL: From willysr at slackbuilds.org Sun Jun 5 13:27:16 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Jun 2016 20:27:16 +0700 Subject: [Slackbuilds-users] hhvm 3.13.2 In-Reply-To: <1465116076.1626.3.camel@caraus.de> References: <1465116076.1626.3.camel@caraus.de> Message-ID: <0e943452-e26f-a32f-d83b-828f336f6505@slackbuilds.org> > And again hhvm update. > > git patch against master. > > Please add BUILDING.txt aswell. Since I'm not using the original git > source, it could be useful for people to know how they can build hhvm > (maybe an update or the master) Applied to my branch with minor update i added docs from hhvm but i can't find any BUILDING.txt in the source -- 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 ts at websafe.pl Sun Jun 5 14:17:46 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 5 Jun 2016 16:17:46 +0200 Subject: [Slackbuilds-users] Problem building truecrypt In-Reply-To: References: <2358692b-61a1-965e-16ff-1eeb040b28b1@websafe.pl> <17fc6626-e3cb-bddc-815d-d919d9e7b2e4@slackbuilds.org> <41a4f506-dd97-1401-3326-2917cd2737de@websafe.pl> Message-ID: <1e9a3ebe-f592-6ed0-9744-c346212c5426@websafe.pl> On 05.06.2016 06:50, Willy Sudiarto Raharjo wrote: > wxPython = wxGTK + Python Bindings > so you basically can use wxGTK or wxPython to build truecrypt > the problem is that you probably install wxGTK3 later and this package > overwrite wx-config that is used by other applications that depends on > wxGTK/wxPython to check it's existence. You can solve it by reinstalling > wxGTK or wxPython as mentioned in the README. Thank you for this explanation :-) -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From belka at caraus.de Sun Jun 5 14:27:25 2016 From: belka at caraus.de (Eugen Wissner) Date: Sun, 05 Jun 2016 16:27:25 +0200 Subject: [Slackbuilds-users] hhvm 3.13.2 In-Reply-To: <0e943452-e26f-a32f-d83b-828f336f6505@slackbuilds.org> References: <1465116076.1626.3.camel@caraus.de> <0e943452-e26f-a32f-d83b-828f336f6505@slackbuilds.org> Message-ID: <1465136845.26069.1.camel@caraus.de> Thanks. Oh, "git diff" doesn't add new files, it is my fault. BUILDING.txt is now attached. Eugene Am Sonntag, den 05.06.2016, 20:27 +0700 schrieb Willy Sudiarto Raharjo: > > > > And again hhvm update. > > > > git patch against master. > > > > Please add BUILDING.txt aswell. Since I'm not using the original > > git > > source, it could be useful for people to know how they can build > > hhvm > > (maybe an update or the master) > Applied to my branch with minor update > i added docs from hhvm but i can't find any BUILDING.txt in the > source > > > _______________________________________________ > 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 -------------- Clone the repository: git clone --depth=1 git://github.com/facebook/hhvm.git HHVM-3.13.2 Check out the last branch/tag. Download third-party modules: git submodule update --init --recursive Third-party modules can be removed: - libsqlite3 Remove GIT related files: find . -name "\.git*" -print0 | xargs -0 rm -rf Build: cmake make -j5 make install From willysr at slackbuilds.org Sun Jun 5 15:34:40 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 5 Jun 2016 22:34:40 +0700 Subject: [Slackbuilds-users] hhvm 3.13.2 In-Reply-To: <1465136845.26069.1.camel@caraus.de> References: <1465116076.1626.3.camel@caraus.de> <0e943452-e26f-a32f-d83b-828f336f6505@slackbuilds.org> <1465136845.26069.1.camel@caraus.de> Message-ID: <1833b0fc-1bcd-3980-170e-7db3f1441911@slackbuilds.org> > Oh, "git diff" doesn't add new files, it is my fault. BUILDING.txt is > now attached. I don't think that kind of instructions is suitable to be included in SBo -- 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 Sun Jun 5 16:17:50 2016 From: belka at caraus.de (Eugen Wissner) Date: Sun, 05 Jun 2016 18:17:50 +0200 Subject: [Slackbuilds-users] hhvm 3.13.2 In-Reply-To: <1833b0fc-1bcd-3980-170e-7db3f1441911@slackbuilds.org> References: <1465116076.1626.3.camel@caraus.de> <0e943452-e26f-a32f-d83b-828f336f6505@slackbuilds.org> <1465136845.26069.1.camel@caraus.de> <1833b0fc-1bcd-3980-170e-7db3f1441911@slackbuilds.org> Message-ID: <1465143470.26069.2.camel@caraus.de> Ok, I'll keep it locally then. Eugene Am Sonntag, den 05.06.2016, 22:34 +0700 schrieb Willy Sudiarto Raharjo: > > > > Oh, "git diff" doesn't add new files, it is my fault. BUILDING.txt > > is > > now attached. > I don't think that kind of instructions is suitable to be included in > SBo > > > _______________________________________________ > 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 ts at websafe.pl Sun Jun 5 16:47:40 2016 From: ts at websafe.pl (Thomas Szteliga) Date: Sun, 5 Jun 2016 18:47:40 +0200 Subject: [Slackbuilds-users] makeself - missing symlink Message-ID: <153f35ef-5665-ba48-24f6-982e763f06c8@websafe.pl> Hello, I'm trying to build veracrypt, and veracrypt requires makeself but even after installing makeself the build script of veracrypt fails, because it's referring to it as makeself, not `makeself.sh`, so maybe updating the makeself.SlackBuild with something like (cd /usr/bin && ln -s makeself.sh makeself) would be a good idea? Other distributions have `makeself` available: https://pkgs.org/centos-7/epel-x86_64/makeself-2.2.0-3.el7.noarch.rpm.html https://packages.debian.org/jessie/all/makeself/filelist http://manpages.ubuntu.com/manpages/trusty/man1/makeself.1.html -- Thomas Szteliga -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3719 bytes Desc: S/MIME Cryptographic Signature URL: From willysr at slackbuilds.org Sun Jun 5 17:46:29 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 6 Jun 2016 00:46:29 +0700 Subject: [Slackbuilds-users] makeself - missing symlink In-Reply-To: <153f35ef-5665-ba48-24f6-982e763f06c8@websafe.pl> References: <153f35ef-5665-ba48-24f6-982e763f06c8@websafe.pl> Message-ID: > I'm trying to build veracrypt, and veracrypt requires > makeself > but even after installing makeself the build script of veracrypt > fails, because it's referring to it as makeself, not `makeself.sh`, > so maybe updating the makeself.SlackBuild with something like > > (cd /usr/bin && ln -s makeself.sh makeself) Applied 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 baildon.research at googlemail.com Sun Jun 5 18:01:32 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 5 Jun 2016 19:01:32 +0100 Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 In-Reply-To: References: Message-ID: On 1 June 2016 at 02:29, Thomas Morper wrote: > > 2) Ditch atlas and patch trilinos to work with blas and lapack in version > 3.6.0. There's no readymade patch available and I don't know how to do > this as this involves FORTRAN code. It worked! Thanks Thomas! Double winner of the challenge! https://slackbuilds.org/cgit/slackbuilds/commit/?h=idlemoor-for-14.2&id=ad0bb3a0be2288bb7c536b116f1f2c36e917e781 https://slackbuilds.org/cgit/slackbuilds/commit/?h=idlemoor-for-14.2&id=ffb4fc658693a4b3e2c61111bdc8e4073cded80a Ok, more challenges tomorrow :) Thanks again -D. From baildon.research at googlemail.com Mon Jun 6 14:00:17 2016 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 6 Jun 2016 15:00:17 +0100 Subject: [Slackbuilds-users] Update tarsnap to version 1.0.37 and new maintainer. In-Reply-To: <081badc2-5166-2635-de11-a40b1fafd163@omniarch.is> References: <081badc2-5166-2635-de11-a40b1fafd163@omniarch.is> Message-ID: > Having discussed the updated version of tarsnap with it's prior maintainer, > he has decided to pass the flame to me. > > I'm uncertain of the proper procedure, but below is the diff of the old and > new files. Done in my branch. (btw. the diff's whitespace got mangled in the email body, an attached tar.gz like the submission form is safer) Thanks! -D. From didier at slint.fr Mon Jun 6 15:53:27 2016 From: didier at slint.fr (Didier Spaier) Date: Mon, 6 Jun 2016 17:53:27 +0200 Subject: [Slackbuilds-users] Update tarsnap to version 1.0.37 and new maintainer. In-Reply-To: References: <081badc2-5166-2635-de11-a40b1fafd163@omniarch.is> Message-ID: On 06/06/2016 16:00, David Spencer wrote: > (btw. the diff's whitespace got mangled in the email body, an attached > tar.gz like the submission form is safer) Also, this document is helpful, I think: /usr/src/linux/Documentation/email-clients.txt It's intended to folks sending patches to the Linux kernel, but: "qui peut le plus, peut le moins". HTH, Didier From baildon.research at googlemail.com Mon Jun 6 22:20:37 2016 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 6 Jun 2016 23:20:37 +0100 Subject: [Slackbuilds-users] Moving stuff to gis/ ? Message-ID: Hi everybody, There's quite a lot of packages that could be moved to the gis/ category. Here's some suggestions: academic/TauDEM academic/opengrads/ academic/spatialite-tools/ academic/spatialite-gui/ desktop/josm/ desktop/qlandkartegt/ desktop/qmapshack graphics/CreateCloudMap graphics/osgEarth/ libraries/basemap libraries/librasterlite/ libraries/libspatialindex/ libraries/libspatialite/ libraries/readosm/ misc/merkaartor/ misc/tangogps/ multimedia/google-earth/ network/gmapcatcher/ If you have any additions, removals, or philosophical objections, I'd be interested to know -- I don't want to do something stupid or unpopular :-) Best regards -D. From jebrhansen+SBo at gmail.com Mon Jun 6 23:16:46 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 06 Jun 2016 23:16:46 +0000 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: Is there a list somewhere that explains all the categories and what type of software does into each? I searched for something and came up empty. The reason I ask is twofold... 1. I don't know what gis stands for (maybe geographical information system, as that is what Google says, so is that all graphics manipulation software?). 2. I have packages (that I will be submitting) that cover multiple categories, so I wonder if one takes precedence over the other all the time or if it is dependent on the application. On Mon, Jun 6, 2016, 6:20 PM David Spencer wrote: > Hi everybody, > > There's quite a lot of packages that could be moved to the gis/ > category. Here's some suggestions: > > academic/TauDEM > academic/opengrads/ > academic/spatialite-tools/ > academic/spatialite-gui/ > desktop/josm/ > desktop/qlandkartegt/ > desktop/qmapshack > graphics/CreateCloudMap > graphics/osgEarth/ > libraries/basemap > libraries/librasterlite/ > libraries/libspatialindex/ > libraries/libspatialite/ > libraries/readosm/ > misc/merkaartor/ > misc/tangogps/ > multimedia/google-earth/ > network/gmapcatcher/ > > If you have any additions, removals, or philosophical objections, I'd > be interested to know -- I don't want to do something stupid or > unpopular :-) > > Best regards > -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 kingbeowulf at gmail.com Tue Jun 7 07:11:06 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 7 Jun 2016 00:11:06 -0700 Subject: [Slackbuilds-users] release 14.2 almost here! Please test the following In-Reply-To: References: Message-ID: On 06/03/2016 10:47 AM, Jack S. Lai wrote: > On Fri, Jun 3, 2016 at 11:29 AM, King Beowulf > wrote: > > Hello Slackers! > > If you have time, please test a few of my build scripts in SBo master on > your hardware. I want to make sure these are ready for go-live. You > > > > system/nvidia-driver > > Missing README and .info file needs updated specs for v361.42 Looks like I befuddled my local files using rsync. SBo master looks fine and now all seems properly synchronized. Thanks Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Tue Jun 7 10:19:25 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 7 Jun 2016 12:19:25 +0200 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: 2016-06-07 1:16 GMT+02:00 Jeremy Hansen : > Is there a list somewhere that explains all the categories and what type of > software does into each? I searched for something and came up empty. no, but they should be pretty self-explanatory https://slackbuilds.org/repository/14.1/ > The reason I ask is twofold... 1. I don't know what gis stands for (maybe > geographical information system, as that is what Google says, so is that all > graphics manipulation software?). 2. I have packages (that I will be yes, it's "geographical information system" and, citing from wikipedia, "the term describes any information system that integrates, stores, edits, analyzes, shares, and displays geographic information". maybe your best option is to have a look to what's provided in the category for a general idea of what goes in it. > submitting) that cover multiple categories, so I wonder if one takes > precedence over the other all the time or if it is dependent on the > application. it's dependent on the application. can you provide a list of examples of what you are about to submit, so maybe we can help you identify to what category they belong... in some cases (that too on a case-by-case basis) categories can also be not that strict and the collocation of one script under one of them instead of another can depend on whatever the maintainer decides. Matteo From jebrhansen+SBo at gmail.com Tue Jun 7 10:50:16 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 07 Jun 2016 10:50:16 +0000 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: Thanks Matteo. I had already looked at the categories provided and after some thought, decided on a category for the package I initially wasn't sure about (it was sickrage, which I felt covered multiple categories, but I felt it fit in the network category the best). I was just wondering if there was an official page that went into more detail, but no worries that there isn't. And thanks for the more in-depth info on gis. Sorry for the noise, David! On Tue, Jun 7, 2016, 6:19 AM Matteo Bernardini wrote: > 2016-06-07 1:16 GMT+02:00 Jeremy Hansen : > > Is there a list somewhere that explains all the categories and what type > of > > software does into each? I searched for something and came up empty. > > no, but they should be pretty self-explanatory > > https://slackbuilds.org/repository/14.1/ > > > The reason I ask is twofold... 1. I don't know what gis stands for (maybe > > geographical information system, as that is what Google says, so is that > all > > graphics manipulation software?). 2. I have packages (that I will be > > yes, it's "geographical information system" and, citing from > wikipedia, "the term describes any information system that integrates, > stores, edits, analyzes, shares, and displays geographic information". > maybe your best option is to have a look to what's provided in the > category for a general idea of what goes in it. > > > submitting) that cover multiple categories, so I wonder if one takes > > precedence over the other all the time or if it is dependent on the > > application. > > it's dependent on the application. > can you provide a list of examples of what you are about to submit, so > maybe we can help you identify to what category they belong... > in some cases (that too on a case-by-case basis) categories can also > be not that strict and the collocation of one script under one of them > instead of another can depend on whatever the maintainer decides. > > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue Jun 7 11:05:29 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 7 Jun 2016 13:05:29 +0200 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: 2016-06-07 12:50 GMT+02:00 Jeremy Hansen : > Thanks Matteo. I had already looked at the categories provided and after > some thought, decided on a category for the package I initially wasn't sure > about (it was sickrage, which I felt covered multiple categories, but I felt > it fit in the network category the best). I was just wondering if there was if sickrage is this https://github.com/SiCKRAGETV/SiCKRAGE candidates categories would be "multimedia" (for what it does), but better, IMHO, "python", as it's a python library. Matteo From baildon.research at googlemail.com Tue Jun 7 11:34:36 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 7 Jun 2016 12:34:36 +0100 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: > Sorry for the noise, David! No problem, it's not noise (thanks Matteo!) To be honest we are quite relaxed about the categories, the only reason for moving stuff to gis/ now is that we didn't finish the job when gis/ was created two years ago. If people have related questions to discuss, it's a useful signal that the original question is not controversial. Please continue ;-) Thanks folks -D. From jebrhansen+SBo at gmail.com Tue Jun 7 12:06:33 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 07 Jun 2016 12:06:33 +0000 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: That's kinda it, but a newer, forked version ( https://github.com/SickRage/SickRage -- apparently there was a bunch of drama so most the developers decided to fork it and leave the main project). Hmm... obviously I didn't go with either of those, but they were both under consideration. I ended up under network, since it hosts a page and downloads stuff from the internet. I thought that python might relate to just libraries used by other programs (stuff that generally installs as a python module), and it doesn't actually do anything multimedia related other than grabbing files that can be deemed multimedia and tracking those files. But I'm totally open to moving it, because, as I said, I wasn't sure what category would best fit the package. Now that you brought up the python aspect, I'm curious about another package I'll be submitting, acd_cli (https://github.com/yadayada/acd_cli). It is a python script to allow you CLI access to an Amazon Cloud Drive, which can be useful for backups. It is python based, but I figured it seemed to best fit under network since it provides access to remote storage. Should I consider moving this to the python category too? On Tue, Jun 7, 2016, 7:05 AM Matteo Bernardini wrote: > 2016-06-07 12:50 GMT+02:00 Jeremy Hansen : > > Thanks Matteo. I had already looked at the categories provided and after > > some thought, decided on a category for the package I initially wasn't > sure > > about (it was sickrage, which I felt covered multiple categories, but I > felt > > it fit in the network category the best). I was just wondering if there > was > > if sickrage is this > > https://github.com/SiCKRAGETV/SiCKRAGE > > candidates categories would be "multimedia" (for what it does), but > better, IMHO, "python", as it's a python library. > > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue Jun 7 12:12:58 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 7 Jun 2016 14:12:58 +0200 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: 2016-06-07 14:06 GMT+02:00 Jeremy Hansen : > That's kinda it, but a newer, forked version > (https://github.com/SickRage/SickRage -- apparently there was a bunch of > drama so most the developers decided to fork it and leave the main project). > > Hmm... obviously I didn't go with either of those, but they were both under > consideration. I ended up under network, since it hosts a page and downloads > stuff from the internet. I thought that python might relate to just > libraries used by other programs (stuff that generally installs as a python > module), and it doesn't actually do anything multimedia related other than > grabbing files that can be deemed multimedia and tracking those files. > > But I'm totally open to moving it, because, as I said, I wasn't sure what > category would best fit the package. whatever you prefer (as long as it makes sense ;) ), you are the maintainer :) > Now that you brought up the python aspect, I'm curious about another package > I'll be submitting, acd_cli (https://github.com/yadayada/acd_cli). It is a > python script to allow you CLI access to an Amazon Cloud Drive, which can be > useful for backups. It is python based, but I figured it seemed to best fit > under network since it provides access to remote storage. Should I consider > moving this to the python category too? still IMHO, as it's an application and not a library, I think it should be ok under network (as you say, for what it does). Matteo From willysr at slackbuilds.org Tue Jun 7 12:17:10 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Jun 2016 19:17:10 +0700 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: > Now that you brought up the python aspect, I'm curious about another > package I'll be submitting, acd_cli (https://github.com/yadayada/acd_cli). > It is a python script to allow you CLI access to an Amazon Cloud Drive, > which can be useful for backups. It is python based, but I figured it > seemed to best fit under network since it provides access to remote > storage. Should I consider moving this to the python category too? We already have a similar package: awscli https://slackbuilds.org/repository/14.1/network/awscli/ -- 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 Tue Jun 7 13:33:44 2016 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 07 Jun 2016 13:33:44 +0000 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: Willy, Were you providing that as an already existing example to confirm my category selection (if so, thanks) or to possibly imply that I may not need to submit acd_cli? If it's the latter, I don't believe awscli supports Amazon Cloud Drive... at least, I couldn't find any references of it. On Tue, Jun 7, 2016, 8:17 AM Willy Sudiarto Raharjo wrote: > > Now that you brought up the python aspect, I'm curious about another > > package I'll be submitting, acd_cli (https://github.com/yadayada/acd_cli > ). > > It is a python script to allow you CLI access to an Amazon Cloud Drive, > > which can be useful for backups. It is python based, but I figured it > > seemed to best fit under network since it provides access to remote > > storage. Should I consider moving this to the python category too? > > We already have a similar package: awscli > https://slackbuilds.org/repository/14.1/network/awscli/ > > > -- > 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 willysr at slackbuilds.org Tue Jun 7 14:12:54 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 7 Jun 2016 21:12:54 +0700 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: > Were you providing that as an already existing example to confirm my > category selection (if so, thanks) or to possibly imply that I may not need > to submit acd_cli? If it's the latter, I don't believe awscli supports > Amazon Cloud Drive... at least, I couldn't find any references of it. i was just pointing a probably similar application/library so you can take it as an example. It uses python, but it's still located in network -- 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 Tue Jun 7 22:31:55 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 7 Jun 2016 23:31:55 +0100 Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 In-Reply-To: References: Message-ID: > 3. games/ember Our new Challenge Winner Dimitris Zlatanidis fixed this today -- he's made it look easy, but I'm sure it wasn't! I have no idea how you figured that out! Genius! https://slackbuilds.org/cgit/slackbuilds/commit/?h=user/dslackw/for-14.2&id=86cbde4a1e658f89d7142cd13d0d92900c870ab1 A Big Thank You to Dimitris! So all four challenges are now Solved -- thanks to all our winners, and also thanks to everybody else who looked and got stuck like me ;) -D. From bryanlharris at gmail.com Wed Jun 8 14:20:32 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Wed, 8 Jun 2016 10:20:32 -0400 Subject: [Slackbuilds-users] 14.2 release date Message-ID: Hi all, Does anybody have any indication or even a guess as to when the 14.2 release will be finished? I've glanced at the home page and don't see anything. Just curious as to how long it will be until it's done. Thanks in advance. V/r, Bryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From d.zlatanidis at gmail.com Wed Jun 8 14:26:24 2016 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Wed, 8 Jun 2016 17:26:24 +0300 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: References: Message-ID: Hi Bryan, Found your answer in Q5 http://www.slackware.com/faq/do_faq.php?faq=general#5 On 06/08/2016 05:20 PM, Bryan Harris wrote: > Hi all, > > Does anybody have any indication or even a guess as to when the 14.2 > release will be finished? I've glanced at the home page and don't see > anything. Just curious as to how long it will be until it's done. > > Thanks in advance. > > V/r, > Bryan > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From miguel at thedeanda.com Wed Jun 8 14:27:58 2016 From: miguel at thedeanda.com (Miguel De Anda) Date: Wed, 8 Jun 2016 07:27:58 -0700 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: References: Message-ID: Ive been reloading the homepage for a few months now myself.... my guess is any second.... (reloads page a few more times) On Jun 8, 2016 7:20 AM, "Bryan Harris" wrote: > Hi all, > > Does anybody have any indication or even a guess as to when the 14.2 > release will be finished? I've glanced at the home page and don't see > anything. Just curious as to how long it will be until it's done. > > Thanks in advance. > > V/r, > Bryan > > _______________________________________________ > 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 anderson.siqueira.cruz at gmail.com Wed Jun 8 14:30:22 2016 From: anderson.siqueira.cruz at gmail.com (Anderson Cruz) Date: Wed, 8 Jun 2016 11:30:22 -0300 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: References: Message-ID: Normally will be done when it's done :P Regards Anderson Cruz On Wed, Jun 8, 2016 at 11:20 AM, Bryan Harris wrote: > Hi all, > > Does anybody have any indication or even a guess as to when the 14.2 > release will be finished? I've glanced at the home page and don't see > anything. Just curious as to how long it will be until it's done. > > Thanks in advance. > > V/r, > Bryan > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Wed Jun 8 14:51:09 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 8 Jun 2016 07:51:09 -0700 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: References: Message-ID: On Wednesday, June 8, 2016, Bryan Harris wrote: > Hi all, > > Does anybody have any indication or even a guess as to when the 14.2 > release will be finished? I've glanced at the home page and don't see > anything. Just curious as to how long it will be until it's done. > > Thanks in advance. > > V/r, > Bryan > Keep an eye on the Changelogs. lots still happening! -- You! What PLANET is this! -- McCoy, "The City on the Edge of Forever", stardate 3134.0 -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryanlharris at gmail.com Wed Jun 8 15:47:43 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Wed, 8 Jun 2016 11:47:43 -0400 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: References: Message-ID: <0F9D7DE5-E313-44C9-A608-CB7DAF9FB3CE@gmail.com> Where can I go to see those? That sounds like what might keep me engaged for a while anyway. V/r, Bryan Sent from my iPhone > On Jun 8, 2016, at 10:51 AM, King Beowulf wrote: > >> On Wednesday, June 8, 2016, Bryan Harris wrote: >> Hi all, >> >> Does anybody have any indication or even a guess as to when the 14.2 release will be finished? I've glanced at the home page and don't see anything. Just curious as to how long it will be until it's done. >> >> Thanks in advance. >> >> V/r, >> Bryan > > Keep an eye on the Changelogs. lots still happening! > > > > -- > You! What PLANET is this! > -- McCoy, "The City on the Edge of Forever", stardate 3134.0 > > _______________________________________________ > 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 gerardo.zamudio at linux.com Wed Jun 8 15:54:42 2016 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 8 Jun 2016 10:54:42 -0500 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: <0F9D7DE5-E313-44C9-A608-CB7DAF9FB3CE@gmail.com> References: <0F9D7DE5-E313-44C9-A608-CB7DAF9FB3CE@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 06/08/2016 10:47 AM, Bryan Harris wrote: > Where can I go to see those? That sounds like what might keep me > engaged for a while anyway. > > V/r, Bryan > >> >> Keep an eye on the Changelogs. lots still happening! > You can click on the "ChangeLogs" link on the left side menu in http://www.slackware.com/ . It will take you here: http://www.slackware.com/changelog/ . I don't think the S/390 ChangeLog is working at the moment, though. The slack390 directory is missing from the mirror. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJXWD+7AAoJEPbPpamee1lXn/AP/RV6ipaog8zCavokN8/sxO2p e8J5Xb+MyLNx2331kRghgluCx4nolh4H2R59ZkY3d8J0ndl7fvWjXiR7dQbBl40S L6wjAX7T/9/GQFfsftKSw74Ykbx4cFIItaSPF1wJtykSbq+tD77MdshvrB73hnUf E+4YNOzHVaxHbJl00zF1sNyKxlwWjBjj4/RMg8v2r5ghScEES8etq0iX4vhuE7F9 6HqFGoYtDMeI6UQgf9/Kvui0ThKa3E6CHAbENPKf28wCbQ00rPtXpUDvZlDy6qL+ VXjcwJPaKwhWc5RqWKFh7hkV/vWCQxcYkZCw39b1UaNXrSk8eAjZ5as8J+e/OZpD 1Vqg+mgz6pfUTQOVkqoB4A5JOpRhYlI8+lqiTSeiGZkEmL1NiOwF9p0b5NZWFMmu KnMFUY15DAO3qAw2oSROC0JC1OYomCosbCIdo0NiCNNHle36c7DkuLWw9h0K2VDt 4EHu7C0Dbrh4LD/RTfoPlnOcQ5QftCnxTy7Cp7r1nGgSrE/ExDNiHDugR1+GWGz8 ggHAZ+m4w4N3SLL9FH7btCpfFdZIptzAD3Suisx66DAewBLuQXaagXOr6HfmJyNs Xv8dFalhViO6e/ghfcqHbzomozsE3/+F5fT02z6t6fUmmCJ6bh2MaKKJDA/uw/Ir Wu8YXSv3LoWjyk+TXS3d =HyCw -----END PGP SIGNATURE----- From bryanlharris at gmail.com Wed Jun 8 16:17:15 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Wed, 8 Jun 2016 12:17:15 -0400 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: References: <0F9D7DE5-E313-44C9-A608-CB7DAF9FB3CE@gmail.com> Message-ID: Aha thank you. V/r, Bryan On Wed, Jun 8, 2016 at 11:54 AM, Gerardo Zamudio wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 06/08/2016 10:47 AM, Bryan Harris wrote: > > Where can I go to see those? That sounds like what might keep me > > engaged for a while anyway. > > > > V/r, Bryan > > > >> > >> Keep an eye on the Changelogs. lots still happening! > > > > You can click on the "ChangeLogs" link on the left side menu in > http://www.slackware.com/ . > > It will take you here: http://www.slackware.com/changelog/ . > > I don't think the S/390 ChangeLog is working at the moment, though. > The slack390 directory is missing from the mirror. > > > > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBCgAGBQJXWD+7AAoJEPbPpamee1lXn/AP/RV6ipaog8zCavokN8/sxO2p > e8J5Xb+MyLNx2331kRghgluCx4nolh4H2R59ZkY3d8J0ndl7fvWjXiR7dQbBl40S > L6wjAX7T/9/GQFfsftKSw74Ykbx4cFIItaSPF1wJtykSbq+tD77MdshvrB73hnUf > E+4YNOzHVaxHbJl00zF1sNyKxlwWjBjj4/RMg8v2r5ghScEES8etq0iX4vhuE7F9 > 6HqFGoYtDMeI6UQgf9/Kvui0ThKa3E6CHAbENPKf28wCbQ00rPtXpUDvZlDy6qL+ > VXjcwJPaKwhWc5RqWKFh7hkV/vWCQxcYkZCw39b1UaNXrSk8eAjZ5as8J+e/OZpD > 1Vqg+mgz6pfUTQOVkqoB4A5JOpRhYlI8+lqiTSeiGZkEmL1NiOwF9p0b5NZWFMmu > KnMFUY15DAO3qAw2oSROC0JC1OYomCosbCIdo0NiCNNHle36c7DkuLWw9h0K2VDt > 4EHu7C0Dbrh4LD/RTfoPlnOcQ5QftCnxTy7Cp7r1nGgSrE/ExDNiHDugR1+GWGz8 > ggHAZ+m4w4N3SLL9FH7btCpfFdZIptzAD3Suisx66DAewBLuQXaagXOr6HfmJyNs > Xv8dFalhViO6e/ghfcqHbzomozsE3/+F5fT02z6t6fUmmCJ6bh2MaKKJDA/uw/Ir > Wu8YXSv3LoWjyk+TXS3d > =HyCw > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Wed Jun 8 16:33:50 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 8 Jun 2016 18:33:50 +0200 Subject: [Slackbuilds-users] 14.2 release date In-Reply-To: References: <0F9D7DE5-E313-44C9-A608-CB7DAF9FB3CE@gmail.com> Message-ID: <6e513fcc-0f58-c305-1bce-88b1bf71396a@gmail.com> On 08/06/16 18:17, Bryan Harris wrote: > Aha thank you. > > V/r, > Bryan > 1. https://slackbuilds.org/mirror/rss/ 2. https://slackbuilds.org/apps/slackchlog/ > On Wed, Jun 8, 2016 at 11:54 AM, Gerardo Zamudio > > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 06/08/2016 10:47 AM, Bryan Harris wrote: > > Where can I go to see those? That sounds like what might keep me > > engaged for a while anyway. > > > > V/r, Bryan > > > >> > >> Keep an eye on the Changelogs. lots still happening! > > > > You can click on the "ChangeLogs" link on the left side menu in > http://www.slackware.com/ . > > It will take you here: http://www.slackware.com/changelog/ . > > I don't think the S/390 ChangeLog is working at the moment, though. > The slack390 directory is missing from the mirror. > > > > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBCgAGBQJXWD+7AAoJEPbPpamee1lXn/AP/RV6ipaog8zCavokN8/sxO2p > e8J5Xb+MyLNx2331kRghgluCx4nolh4H2R59ZkY3d8J0ndl7fvWjXiR7dQbBl40S > L6wjAX7T/9/GQFfsftKSw74Ykbx4cFIItaSPF1wJtykSbq+tD77MdshvrB73hnUf > E+4YNOzHVaxHbJl00zF1sNyKxlwWjBjj4/RMg8v2r5ghScEES8etq0iX4vhuE7F9 > 6HqFGoYtDMeI6UQgf9/Kvui0ThKa3E6CHAbENPKf28wCbQ00rPtXpUDvZlDy6qL+ > VXjcwJPaKwhWc5RqWKFh7hkV/vWCQxcYkZCw39b1UaNXrSk8eAjZ5as8J+e/OZpD > 1Vqg+mgz6pfUTQOVkqoB4A5JOpRhYlI8+lqiTSeiGZkEmL1NiOwF9p0b5NZWFMmu > KnMFUY15DAO3qAw2oSROC0JC1OYomCosbCIdo0NiCNNHle36c7DkuLWw9h0K2VDt > 4EHu7C0Dbrh4LD/RTfoPlnOcQ5QftCnxTy7Cp7r1nGgSrE/ExDNiHDugR1+GWGz8 > ggHAZ+m4w4N3SLL9FH7btCpfFdZIptzAD3Suisx66DAewBLuQXaagXOr6HfmJyNs > Xv8dFalhViO6e/ghfcqHbzomozsE3/+F5fT02z6t6fUmmCJ6bh2MaKKJDA/uw/Ir > Wu8YXSv3LoWjyk+TXS3d > =HyCw > -----END PGP SIGNATURE----- > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > > > > _______________________________________________ > 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 z.coldplayer at gmail.com Thu Jun 9 04:17:47 2016 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Thu, 9 Jun 2016 08:17:47 +0400 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: I support to move packages into categories whose names are more intuitive and makes more sense rather than a general category such as haskell which does not help at all considering the large number of packages hosted there. The next time I dwelve into slackbuilds/sbopkg to create a queue to create new packages, I won't have to search through many categories to find one slackbuild. Move the packages to gis as soon as possible so that we can test whether it does not break any automized scripts. On 7 Jun 2016 6:13 pm, "Willy Sudiarto Raharjo" wrote: > > Were you providing that as an already existing example to confirm my > > category selection (if so, thanks) or to possibly imply that I may not > need > > to submit acd_cli? If it's the latter, I don't believe awscli supports > > Amazon Cloud Drive... at least, I couldn't find any references of it. > > i was just pointing a probably similar application/library so you can > take it as an example. It uses python, but it's still located in network > > -- > 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 ryan.q at linux.com Thu Jun 9 04:30:20 2016 From: ryan.q at linux.com (Ryan P.C. McQuen) Date: Wed, 8 Jun 2016 21:30:20 -0700 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: > > There's quite a lot of packages that could be moved to the gis/ >> category. > > +1 -- -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Thu Jun 9 14:46:41 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Jun 2016 16:46:41 +0200 Subject: [Slackbuilds-users] qbs maintainer Message-ID: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> Hi, Some time ago I tried to approach qbs maintainer for possible qbs update, but had no answer. Nikos, are you here? :) -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Thu Jun 9 15:59:38 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Jun 2016 17:59:38 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> Message-ID: On 09/06/16 16:46, Andrzej Telszewski wrote: > Hi, > > Some time ago I tried to approach qbs maintainer for possible qbs > update, but had no answer. > > Nikos, are you here? :) > Just in case, if Nikos is not interested in maintaining the qbs, I would like to take over. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Thu Jun 9 16:07:54 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 9 Jun 2016 23:07:54 +0700 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> Message-ID: <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> >> Some time ago I tried to approach qbs maintainer for possible qbs >> update, but had no answer. >> >> Nikos, are you here? :) >> > > Just in case, if Nikos is not interested in maintaining the qbs, I would > like to take over. I'm testing the new version 1.5.1 at this moment Nikos submitted this package 2 years ago and since then no more updates coming in. -- 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 Thu Jun 9 16:33:01 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Jun 2016 18:33:01 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> Message-ID: On 09/06/16 18:07, Willy Sudiarto Raharjo wrote: >>> Some time ago I tried to approach qbs maintainer for possible qbs >>> update, but had no answer. >>> >>> Nikos, are you here? :) >>> >> >> Just in case, if Nikos is not interested in maintaining the qbs, I would >> like to take over. > > I'm testing the new version 1.5.1 at this moment > Nikos submitted this package 2 years ago and since then no more updates > coming in. > Willy, I've spent quite some time on the subject. Attached please find my results. We're working together with Andre (qt-creator maintainter), because qt-creator and qbs are coupled in a way. With Andre we agreed on making qbs hard dependency for qt-creator, but in that case it has to be updated to newer version (latest is 1.5.1 as you mentioned). Let me know if you want me to proceed and take the things over. -- Best regards, Andrzej Telszewski -------------- next part -------------- A non-text attachment was scrubbed... Name: qbs.tar.gz Type: application/gzip Size: 2935 bytes Desc: not available URL: From willysr at slackbuilds.org Thu Jun 9 16:37:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 9 Jun 2016 23:37:02 +0700 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> Message-ID: <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> > Willy, I've spent quite some time on the subject. > Attached please find my results. > > We're working together with Andre (qt-creator maintainter), because > qt-creator and qbs are coupled in a way. > > With Andre we agreed on making qbs hard dependency for qt-creator, but > in that case it has to be updated to newer version (latest is 1.5.1 as > you mentioned). > > Let me know if you want me to proceed and take the things over. Already 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 atelszewski at gmail.com Thu Jun 9 16:42:45 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Jun 2016 18:42:45 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> Message-ID: On 09/06/16 18:37, Willy Sudiarto Raharjo wrote: >> Willy, I've spent quite some time on the subject. >> Attached please find my results. >> >> We're working together with Andre (qt-creator maintainter), because >> qt-creator and qbs are coupled in a way. >> >> With Andre we agreed on making qbs hard dependency for qt-creator, but >> in that case it has to be updated to newer version (latest is 1.5.1 as >> you mentioned). >> >> Let me know if you want me to proceed and take the things over. > > Already pushed to my branch :) > I understand you took my version? If so, the README has to be slightly updated. Andre sent me qt-creator SlackBuild for a review. I should have the things tested and sorted out tomorrow. Then I'll send the README update. -- Best regards, Andrzej Telszewski From atelszewski at gmail.com Thu Jun 9 16:45:24 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Jun 2016 18:45:24 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> Message-ID: <9d31e2ba-f5d1-17de-57a2-6daff39c8c3b@gmail.com> On 09/06/16 18:42, Andrzej Telszewski wrote: > On 09/06/16 18:37, Willy Sudiarto Raharjo wrote: >>> Willy, I've spent quite some time on the subject. >>> Attached please find my results. >>> >>> We're working together with Andre (qt-creator maintainter), because >>> qt-creator and qbs are coupled in a way. >>> >>> With Andre we agreed on making qbs hard dependency for qt-creator, but >>> in that case it has to be updated to newer version (latest is 1.5.1 as >>> you mentioned). >>> >>> Let me know if you want me to proceed and take the things over. >> >> Already pushed to my branch :) >> > > I understand you took my version? > > If so, the README has to be slightly updated. > > Andre sent me qt-creator SlackBuild for a review. > I should have the things tested and sorted out tomorrow. > Then I'll send the README update. > OK, I checked your branch;) -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Thu Jun 9 16:45:51 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 9 Jun 2016 23:45:51 +0700 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> Message-ID: <55434e7b-e22d-d4a4-0864-e60d62e21226@slackbuilds.org> > I understand you took my version? > > If so, the README has to be slightly updated. > > Andre sent me qt-creator SlackBuild for a review. > I should have the things tested and sorted out tomorrow. > Then I'll send the README update. At the first time, i didn't look at your version as i have been working on that before your email got to my inbox, but now i have updated the README from your update. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Thu Jun 9 16:49:59 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Jun 2016 18:49:59 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <55434e7b-e22d-d4a4-0864-e60d62e21226@slackbuilds.org> References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> <55434e7b-e22d-d4a4-0864-e60d62e21226@slackbuilds.org> Message-ID: <7218522d-08a4-1884-efa6-8a652e2168b0@gmail.com> On 09/06/16 18:45, Willy Sudiarto Raharjo wrote: >> I understand you took my version? >> >> If so, the README has to be slightly updated. >> >> Andre sent me qt-creator SlackBuild for a review. >> I should have the things tested and sorted out tomorrow. >> Then I'll send the README update. > > At the first time, i didn't look at your version as i have been working > on that before your email got to my inbox, but now i have updated the > README from your update. > Please take a look at the whole SlackBuild. There are more things needed for qbs to be useful for qt-creator. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Thu Jun 9 16:55:29 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 9 Jun 2016 23:55:29 +0700 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <7218522d-08a4-1884-efa6-8a652e2168b0@gmail.com> References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> <55434e7b-e22d-d4a4-0864-e60d62e21226@slackbuilds.org> <7218522d-08a4-1884-efa6-8a652e2168b0@gmail.com> Message-ID: <35785e0a-b199-fcc2-b99f-19f89910b9cf@slackbuilds.org> > Please take a look at the whole SlackBuild. > There are more things needed for qbs to be useful for qt-creator. Thanks pushed-force with changes from your SlackBuild update -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Thu Jun 9 17:02:01 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 9 Jun 2016 19:02:01 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <35785e0a-b199-fcc2-b99f-19f89910b9cf@slackbuilds.org> References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> <55434e7b-e22d-d4a4-0864-e60d62e21226@slackbuilds.org> <7218522d-08a4-1884-efa6-8a652e2168b0@gmail.com> <35785e0a-b199-fcc2-b99f-19f89910b9cf@slackbuilds.org> Message-ID: <108ef48d-0874-8a47-3235-1d67a3292265@gmail.com> On 09/06/16 18:55, Willy Sudiarto Raharjo wrote: >> Please take a look at the whole SlackBuild. >> There are more things needed for qbs to be useful for qt-creator. > > Thanks > pushed-force with changes from your SlackBuild update > OK. I'll send you the updated README soon enough. Thanks! -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Fri Jun 10 01:04:25 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 10 Jun 2016 08:04:25 +0700 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: <369e51d5-703f-b2a7-f584-93a1797a6371@slackbuilds.org> > There's quite a lot of packages that could be moved to the gis/ > category. Here's some suggestions: > > academic/TauDEM > academic/opengrads/ > academic/spatialite-tools/ > academic/spatialite-gui/ > desktop/josm/ > desktop/qlandkartegt/ > desktop/qmapshack > graphics/CreateCloudMap > graphics/osgEarth/ > libraries/basemap > libraries/librasterlite/ > libraries/libspatialindex/ > libraries/libspatialite/ > libraries/readosm/ > misc/merkaartor/ > misc/tangogps/ > multimedia/google-earth/ > network/gmapcatcher/ > > If you have any additions, removals, or philosophical objections, I'd > be interested to know -- I don't want to do something stupid or > unpopular :-) It's all merged to master just now Big thanks to David for his work on moving this scripts to a better category -- 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 Jun 10 14:13:58 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Fri, 10 Jun 2016 17:13:58 +0300 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: <369e51d5-703f-b2a7-f584-93a1797a6371@slackbuilds.org> References: <369e51d5-703f-b2a7-f584-93a1797a6371@slackbuilds.org> Message-ID: hey, concerning all this GIS stuff... have you considered renaming 'gis' to something more self-explanatory? -petar 2016-06-10 4:04 GMT+03:00 Willy Sudiarto Raharjo : > > There's quite a lot of packages that could be moved to the gis/ > > category. Here's some suggestions: > > > > academic/TauDEM > > academic/opengrads/ > > academic/spatialite-tools/ > > academic/spatialite-gui/ > > desktop/josm/ > > desktop/qlandkartegt/ > > desktop/qmapshack > > graphics/CreateCloudMap > > graphics/osgEarth/ > > libraries/basemap > > libraries/librasterlite/ > > libraries/libspatialindex/ > > libraries/libspatialite/ > > libraries/readosm/ > > misc/merkaartor/ > > misc/tangogps/ > > multimedia/google-earth/ > > network/gmapcatcher/ > > > > If you have any additions, removals, or philosophical objections, I'd > > be interested to know -- I don't want to do something stupid or > > unpopular :-) > > It's all merged to master just now > > Big thanks to David for his work on moving this scripts to a better > category > > -- > 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 willysr at slackbuilds.org Fri Jun 10 14:39:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 10 Jun 2016 21:39:27 +0700 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: <369e51d5-703f-b2a7-f584-93a1797a6371@slackbuilds.org> Message-ID: > concerning all this GIS stuff... have you considered renaming 'gis' to > something more self-explanatory? Actually GIS is self-explanatory if you put GIS in search engine, you will get it in the first entry -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sat Jun 11 03:27:18 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sat, 11 Jun 2016 05:27:18 +0200 Subject: [Slackbuilds-users] qbs maintainer In-Reply-To: <108ef48d-0874-8a47-3235-1d67a3292265@gmail.com> References: <61513355-6ccb-1c2b-7cd7-833311871fb6@gmail.com> <9401f426-047e-a61a-6862-d49abf261836@slackbuilds.org> <9fe46da5-a073-25ae-d80a-5596905dd4e0@slackbuilds.org> <55434e7b-e22d-d4a4-0864-e60d62e21226@slackbuilds.org> <7218522d-08a4-1884-efa6-8a652e2168b0@gmail.com> <35785e0a-b199-fcc2-b99f-19f89910b9cf@slackbuilds.org> <108ef48d-0874-8a47-3235-1d67a3292265@gmail.com> Message-ID: On 09/06/16 19:02, Andrzej Telszewski wrote: > On 09/06/16 18:55, Willy Sudiarto Raharjo wrote: >>> Please take a look at the whole SlackBuild. >>> There are more things needed for qbs to be useful for qt-creator. >> >> Thanks >> pushed-force with changes from your SlackBuild update >> > > OK. I'll send you the updated README soon enough. > > Thanks! > Attached please find the updated README for qbs. ;) -- Best regards, Andrzej Telszewski -------------- next part -------------- A non-text attachment was scrubbed... Name: README.tar.gz Type: application/gzip Size: 383 bytes Desc: not available URL: From slackbuilds at schoepfer.info Sat Jun 11 12:19:09 2016 From: slackbuilds at schoepfer.info (Franzen) Date: Sat, 11 Jun 2016 14:19:09 +0200 Subject: [Slackbuilds-users] mhwaveedit Message-ID: <027578533d5152fe5070e5e3cc2b2d01@schoepfer.info> Hi, to update/make mhwaveedit 1.4.23 compile on Current, i had to create the attached diff. The Slackbuild-diff was made against the master-branch. The package-maintainer is in cc. Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: intbox.diff Type: text/x-diff Size: 278 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: mhwaveedit.diff Type: text/x-diff Size: 1271 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Jun 11 14:05:58 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 11 Jun 2016 21:05:58 +0700 Subject: [Slackbuilds-users] mhwaveedit In-Reply-To: <027578533d5152fe5070e5e3cc2b2d01@schoepfer.info> References: <027578533d5152fe5070e5e3cc2b2d01@schoepfer.info> Message-ID: <82fec069-36bf-56b6-37cd-aebe4502c09c@slackbuilds.org> > to update/make mhwaveedit 1.4.23 compile on Current, i had to create the > attached diff. The Slackbuild-diff was made against the master-branch. > The package-maintainer is in cc. Thanks applied 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 kingbeowulf at gmail.com Sun Jun 12 05:28:28 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 11 Jun 2016 22:28:28 -0700 Subject: [Slackbuilds-users] nvidia-361.45.11 update Message-ID: <655b740f-d2f7-c873-3db7-87d3b1e7f691@gmail.com> Quick update for the new kernel since I had to recompile anyway and a friendly slacker informed me it works ok. nvidia-361.45.11 has few upstream fixes. See attached diff against SBo git master. Thanks Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-361.45.11-update.diff Type: text/x-patch Size: 5260 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From philip at vanderhoeven.org Tue Jun 14 15:21:29 2016 From: philip at vanderhoeven.org (=?utf-8?Q?Philip_van_der_Hoeven?=) Date: Tue, 14 Jun 2016 17:21:29 +0200 Subject: [Slackbuilds-users] sabnzbd Message-ID: Hi, Hereby a patch against master to update sabnzbd to 1.0.3 Regards, Philip -------------- next part -------------- A non-text attachment was scrubbed... Name: sabnzbd.patch.gz Type: application/gzip Size: 671 bytes Desc: not available URL: From willysr at slackbuilds.org Tue Jun 14 15:31:32 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 14 Jun 2016 22:31:32 +0700 Subject: [Slackbuilds-users] sabnzbd In-Reply-To: References: Message-ID: <02c3ab4d-9913-db64-f696-b9b5ed9d3c4a@slackbuilds.org> > Hereby a patch against master to update sabnzbd to 1.0.3 Applied 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 d.zlatanidis at gmail.com Wed Jun 15 14:30:26 2016 From: d.zlatanidis at gmail.com (d.zlatanidis) Date: Wed, 15 Jun 2016 17:30:26 +0300 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo Message-ID: Can anyone help me to fix build system/gentoo package for -current 14.2? New version 0.20.17 are available. Thank you Dimitris Zlatanidis From matteo.bernardini at gmail.com Wed Jun 15 14:53:31 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 15 Jun 2016 16:53:31 +0200 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: References: Message-ID: 2016-06-15 16:30 GMT+02:00 d.zlatanidis : > > Can anyone help me to fix build system/gentoo package for -current 14.2? New version 0.20.17 are available. hi Dimitris, which issue are you having? I've tried to version-bump it here to 0.20.7 and it built and run fine (beside a "development version" warning at start). Matteo From d.zlatanidis at gmail.com Thu Jun 16 00:35:01 2016 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Thu, 16 Jun 2016 03:35:01 +0300 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: References: Message-ID: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking whether gcc understands -c and -o together... yes checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking dependency style of gcc... (cached) gcc3 checking how to run the C preprocessor... gcc -E checking for ranlib... ranlib checking for pkg-config... /usr/bin/pkg-config checking for GTK+ - version >= 3.12.0... no *** Could not run GTK+ test program, checking why... *** The test program failed to compile or link. See the file config.log for the *** exact error that occured. This usually means GTK+ is incorrectly installed. configure: error: Bad GTK+ version it seems cannot be found GTK+ library On 06/15/2016 05:53 PM, Matteo Bernardini wrote: > 2016-06-15 16:30 GMT+02:00 d.zlatanidis : >> >> Can anyone help me to fix build system/gentoo package for -current 14.2? New version 0.20.17 are available. > > > hi Dimitris, > > which issue are you having? I've tried to version-bump it here to > 0.20.7 and it built and run fine (beside a "development version" > warning at start). > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From matteo.bernardini at gmail.com Thu Jun 16 06:07:31 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 16 Jun 2016 08:07:31 +0200 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> References: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> Message-ID: 2016-06-16 2:35 GMT+02:00 Dimitris Zlatanidis : > *** Could not run GTK+ test program, checking why... > *** The test program failed to compile or link. See the file config.log > for the > *** exact error that occured. This usually means GTK+ is incorrectly > installed. > configure: error: Bad GTK+ version please post the full generated config.log file on http://pastebin.com and paste back here the link to it as it may cointain hints to what went wrong... Matteo From lynx at panix.com Thu Jun 16 08:14:03 2016 From: lynx at panix.com (Arthur W. Green) Date: Thu, 16 Jun 2016 02:14:03 -0600 Subject: [Slackbuilds-users] audio/snd: Update to version 16.6. Message-ID: <89cdf642-f17d-eee6-3953-8f61c07c38fc@panix.com> Hi, Attached is a version bump for audio/snd in branch willysr-for-14.2. Thank you! \\ Arthur -------------- next part -------------- A non-text attachment was scrubbed... Name: snd-16.6.patch Type: text/x-patch Size: 877 bytes Desc: not available URL: From willysr at slackbuilds.org Thu Jun 16 10:19:34 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 16 Jun 2016 17:19:34 +0700 Subject: [Slackbuilds-users] audio/snd: Update to version 16.6. In-Reply-To: <89cdf642-f17d-eee6-3953-8f61c07c38fc@panix.com> References: <89cdf642-f17d-eee6-3953-8f61c07c38fc@panix.com> Message-ID: > Attached is a version bump for audio/snd in branch willysr-for-14.2. applied 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 d.zlatanidis at gmail.com Thu Jun 16 11:02:31 2016 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Thu, 16 Jun 2016 14:02:31 +0300 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: References: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> Message-ID: <4a746b7a-33a2-5ddc-8003-3f628e162ae0@gmail.com> here it is: http://pastebin.com/5v6wd3sA On 06/16/2016 09:07 AM, Matteo Bernardini wrote: > 2016-06-16 2:35 GMT+02:00 Dimitris Zlatanidis : >> *** Could not run GTK+ test program, checking why... >> *** The test program failed to compile or link. See the file config.log >> for the >> *** exact error that occured. This usually means GTK+ is incorrectly >> installed. >> configure: error: Bad GTK+ version > > please post the full generated config.log file on http://pastebin.com > and paste back here the link to it as it may cointain hints to what > went wrong... > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From matteo.bernardini at gmail.com Thu Jun 16 11:04:53 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 16 Jun 2016 13:04:53 +0200 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: <4a746b7a-33a2-5ddc-8003-3f628e162ae0@gmail.com> References: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> <4a746b7a-33a2-5ddc-8003-3f628e162ae0@gmail.com> Message-ID: 2016-06-16 13:02 GMT+02:00 Dimitris Zlatanidis : > > here it is: > http://pastebin.com/5v6wd3sA maybe there's a misunderstanding: the config.log is a specific file named that way into the sources folder, generated at the moment in which ./configure is run. you should be able to find it in the /tmp/SBo/gentoo-0.20.7 directory. Matteo From slackalaxy at gmail.com Thu Jun 16 14:30:39 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Thu, 16 Jun 2016 17:30:39 +0300 Subject: [Slackbuilds-users] SBo packages conflicts? Message-ID: Hi to all. What is your opinion and is SlackBuilds.org going to do something in regards to this: http://www.linuxquestions.org/questions/slackware-14/slackpkg-add-on-for-sbo-4175581768/page2.html#post5558622 bye Petar -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Thu Jun 16 16:16:16 2016 From: didier at slint.fr (Didier Spaier) Date: Thu, 16 Jun 2016 18:16:16 +0200 Subject: [Slackbuilds-users] SBo packages conflicts? In-Reply-To: References: Message-ID: <5f2984d4-2d2a-c25a-2a79-3d205b7af2c0@slint.fr> Hi to all and Petar, On 16/06/2016 16:30, Petar Petrov wrote: > Hi to all. > > What is your opinion and is SlackBuilds.org going to do something in > regards to this: > > http://www.linuxquestions.org/questions/slackware-14/slackpkg-add-on-for-sbo-4175581768/page2.html#post5558622 > > bye > > Petar Please see the message forwarded below. I sent it Tuesday but for some reason it didn't go through @Admins: what happens? I asked to Rob yesterday, no answer so far. Maybe my IP is banned by slackbuilds.org, but why? @Petar: if you don't see this message on the list abut 10 minutes after having received it, would you be kind enough to forward it to the list for me? TIA. Regards, Didier -------- Forwarded Message -------- Subject: Suggested method to better document the conflicts between packages. Date: Tue, 14 Jun 2016 23:16:21 +0200 From: Didier Spaier To: SlackBuilds.org Users List This is a proposal intended as a request for comments. The goal is to avoid that installing a package built from a SlackBuild overrides files installed by another one. Why? Because unless replaced and replacing files be identical, this can prevent the already installed software and those that depend on it to work properly. Manually spot such conflicts is a daunting task, as that needs to check each package against thousands of other ones. But David has written scripts that automatize finding the collisions and summarizing them per tuple of packages, see the post #21 in: http://www.linuxquestions.org/questions/slackware-14/slackpkg-add-on-for-sbo-4175581768/ I found the results very interesting, so I suggest to build on that to spot and document the conflicts: _ at least in the README files of the conflicting packages, _ and also in a new "CONFLICTS:" field of .info. The latter would then allow package tools to parse this information, either from the .info file or through the PACKAGES.TXT file. Some package tools can already make use of the CONFLICTS info in PACKAGES.TXT and it won't be difficult to copy from the former to the latter. So here is my proposal (after adaptation if need be of the scripts written by David as a proof of concept). The list of collisions and tuples (packages included in Slackware and SlackBuilds hosted @ slackbuilds.org) would be updated after the 14.2 release. Then these list would be made available to all SlackBuild maintainers (maybe after sort of the tuples per maintainer), who could: _ check which of their packages are among the tuples if not yet sorted, _ grep collisions to see which files would be overwritten, _ assess the collisions: some are harmless others not, _ in case of harmful collisions, insert a warning in the README and/or feed .info with the name(s) of the conflicting packages, _ possibly consult with the maintainers of the conflicting SlackBuilds, about how to avoid collisions if possible, else inform the users in a consistent way. I didn't give much thought about how to deal with updates of Slackware packages and SlackBuilds after the release but this should be addressed. Thanks for having read this long post and in advance for your thoughts. Cheers, Didier From marc at mos6581.de Thu Jun 16 16:16:52 2016 From: marc at mos6581.de (Marcel Saegebarth) Date: Thu, 16 Jun 2016 18:16:52 +0200 Subject: [Slackbuilds-users] SBo packages conflicts? In-Reply-To: References: Message-ID: <52138ea2-7582-e550-f11c-b4d1cadcc126@mos6581.de> On 06/16/2016 04:30 PM, Petar Petrov wrote: > Hi to all. > > What is your opinion and is SlackBuilds.org going to do something in > regards to this: > > http://www.linuxquestions.org/questions/slackware-14/slackpkg-add-on-for-sbo-4175581768/page2.html#post5558622 There are some false-positives as some SlackBuilds explicit state that they will conflict so you should just install just one of them. For instance: jack2 and jack-audio-connection-kit wxGTK3 is even more different. -marc -------------------------------------------------------------------------------- PGP 32 bit Key ID: 0x69EC498D PGP 64 bit Key ID: 0x8EE93B2D69EC498D PGP Key fingerprint: D320 76CB 4053 D544 52BD D461 8EE9 3B2D 69EC 498D -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From erik at slackbuilds.org Thu Jun 16 17:58:39 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 16 Jun 2016 12:58:39 -0500 Subject: [Slackbuilds-users] SBo packages conflicts? In-Reply-To: <5f2984d4-2d2a-c25a-2a79-3d205b7af2c0@slint.fr> References: <5f2984d4-2d2a-c25a-2a79-3d205b7af2c0@slint.fr> Message-ID: <20160616125839.37ec441d@shaggy.doo> On Thu, 16 Jun 2016 18:16:16 +0200 Didier Spaier wrote: Since this is intended as RFC, these are my comments and not meant to be me setting anything in stone. > But David has written scripts that automatize finding the collisions > and summarizing them per tuple of packages, see the post #21 in: > http://www.linuxquestions.org/questions/slackware-14/slackpkg-add-on-for-sbo-4175581768/ I noticed a significant number of lines that are stock packages conflicting with stock packages. These are not the concern of SBo, but suggest to me, at least, that most conflicts are probably not very important. As such, my initial concern is minimal. Important conflicts, like incompatible .h files being replaced, need to be dealt with. > I found the results very interesting, so I suggest to build on that > to spot and document the conflicts: > _ at least in the README files of the conflicting packages, This is how it's supposed to already happen. If it's not true for some scripts, their README files need to be updated. If anyone on the list is willing to do the work and provide a patch set, that would be appreciated. I'm guessing no admins really have the time for this. I don't want to further burden the few that are working hard on getting us ready for 14.2. The idea of doing it after 14.2 is a bit moot, this can be done at any time, and should be done sooner rather than later. > _ and also in a new "CONFLICTS:" field of .info. This will probably not happen. Conflicts such as wxPython and wxGTK should have that info in the README already. As for individual files conflicting, like docs or headers, that should be dealt with in some way such as removing or renaming the files before generating the package. If that's not possible (it breaks the package), then a mention in the README is necessary. By and large, there aren't many scripts that generate conflicting packages. Not nearly enough to justify adding a CONFLICTS line to the .info files. (n.b. this is in reference to packages and not files within packages.) > The latter would then allow package tools to parse this information, > either from the .info file or through the PACKAGES.TXT file. > Some package tools can already make use of the CONFLICTS info in > PACKAGES.TXT and it won't be difficult to copy from the former to the > latter. We don't provide any PACKAGES.TXT file, since, you know, we don't provide packages. :) If you meant SLACKBUILDS.TXT, there are no CONFLICTS lines in said file. > So here is my proposal (after adaptation if need be of the scripts > written by David as a proof of concept). > > The list of collisions and tuples (packages included in Slackware and > SlackBuilds hosted @ slackbuilds.org) would be updated after the 14.2 > release. Then these list would be made available to all SlackBuild > maintainers (maybe after sort of the tuples per maintainer), who > could: _ check which of their packages are among the tuples if not > yet sorted, _ grep collisions to see which files would be overwritten, > _ assess the collisions: some are harmless others not, > _ in case of harmful collisions, insert a warning in the README and/or > feed .info with the name(s) of the conflicting packages, > _ possibly consult with the maintainers of the conflicting Internally, we have a post-check script that checks for conflicts with files that already exist in a full install. I'm not sure if every admin is using it, or if it's broken, or this is the result of using git more than we did in the past. Especially right now, while we're focusing on 14.2, "updates" aren't running the way they usually would for the stable branch. The usual way being to run the post-check during approval. Ultimately though, maintainers should be making sure this doesn't happen. > SlackBuilds, about how to avoid collisions if possible, else inform > the users in a consistent way. > > I didn't give much thought about how to deal with updates of Slackware > packages and SlackBuilds after the release but this should be > addressed. > > Thanks for having read this long post and in advance for your > thoughts. Cheers, Didier Thanks for looking into it initially. Again, if anyone is willing to step up and provide patches, that would probably be best. Some maintainers are inactive (or busy, or uninterested) and simply creating a list of them, and/or contacting them, may not prove entirely fruitful. -- Erik From bryanlharris at gmail.com Fri Jun 17 00:02:44 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Thu, 16 Jun 2016 20:02:44 -0400 Subject: [Slackbuilds-users] Building libvirt Message-ID: Hello all, I tried building libvirt on Slackware 14.1. The following optional dependencies went fine: - avahi - libcap-ng - libdaemon - libssh2 I decided to skip the xen optional dependency since I didn't understand what it provides, plus it looks more complicated to install. When I went to run the SBo script for libvirt, I got the following message. configure: error: You must install the libyajl library & headers to compile libvirt After installing the yajl package libvirt builds fine. Should the yajl package have a mention within the README file in the dependencies list? V/r, Bryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Fri Jun 17 00:19:09 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Fri, 17 Jun 2016 10:19:09 +1000 Subject: [Slackbuilds-users] Building libvirt In-Reply-To: References: Message-ID: On 17/06/16 10:02, Bryan Harris wrote: > Hello all, > > I tried building libvirt on Slackware 14.1. The following optional > dependencies went fine: > > - avahi > - libcap-ng > - libdaemon > - libssh2 > > I decided to skip the xen optional dependency since I didn't understand > what it provides, plus it looks more complicated to install. > > When I went to run the SBo script for libvirt, I got the following message. > > configure: error: You must install the libyajl library & headers to > compile libvirt > > After installing the yajl package libvirt builds fine. Should the yajl > package have a mention within the README file in the dependencies list? > yajl is required for xen (which you skipped). From bryanlharris at gmail.com Fri Jun 17 00:35:09 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Thu, 16 Jun 2016 20:35:09 -0400 Subject: [Slackbuilds-users] Building libvirt In-Reply-To: References: Message-ID: Any reason why libvirt didn't build without yajl? Perhaps it is a check in the ./configure step? V/r, Bryan On Thu, Jun 16, 2016 at 8:19 PM, Christoph Willing < chris.willing at iinet.net.au> wrote: > On 17/06/16 10:02, Bryan Harris wrote: > >> Hello all, >> >> I tried building libvirt on Slackware 14.1. The following optional >> dependencies went fine: >> >> - avahi >> - libcap-ng >> - libdaemon >> - libssh2 >> >> I decided to skip the xen optional dependency since I didn't understand >> what it provides, plus it looks more complicated to install. >> >> When I went to run the SBo script for libvirt, I got the following >> message. >> >> configure: error: You must install the libyajl library & headers to >> compile libvirt >> >> After installing the yajl package libvirt builds fine. Should the yajl >> package have a mention within the README file in the dependencies list? >> >> yajl is required for xen (which you skipped). > > _______________________________________________ > 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 matteo.bernardini at gmail.com Fri Jun 17 06:05:37 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 17 Jun 2016 08:05:37 +0200 Subject: [Slackbuilds-users] Building libvirt In-Reply-To: References: Message-ID: 2016-06-17 2:35 GMT+02:00 Bryan Harris : > Any reason why libvirt didn't build without yajl? Perhaps it is a check in > the ./configure step? hi Bryan, yajl is a mandatory dependency of libvirt, not an optional one: as such, is listed in in the libvirt.info file in the variable REQUIRES and on the SBo's libvirt page https://slackbuilds.org/repository/14.1/libraries/libvirt/ Matteo From bryanlharris at gmail.com Fri Jun 17 08:04:08 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Fri, 17 Jun 2016 04:04:08 -0400 Subject: [Slackbuilds-users] Building libvirt In-Reply-To: References: Message-ID: Oh I see, I only read the README. I'll read the info file from now on. V/r, Bryan On Fri, Jun 17, 2016 at 2:05 AM, Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > 2016-06-17 2:35 GMT+02:00 Bryan Harris : > > Any reason why libvirt didn't build without yajl? Perhaps it is a check > in > > the ./configure step? > > hi Bryan, > > yajl is a mandatory dependency of libvirt, not an optional one: as > such, is listed in in the libvirt.info file in the variable REQUIRES > and on the SBo's libvirt page > > https://slackbuilds.org/repository/14.1/libraries/libvirt/ > > 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/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Fri Jun 17 10:20:11 2016 From: didier at slint.fr (Didier Spaier) Date: Fri, 17 Jun 2016 12:20:11 +0200 Subject: [Slackbuilds-users] SBo packages conflicts? In-Reply-To: <20160616125839.37ec441d@shaggy.doo> References: <5f2984d4-2d2a-c25a-2a79-3d205b7af2c0@slint.fr> <20160616125839.37ec441d@shaggy.doo> Message-ID: <049e9941-031d-8155-18e7-8944bc93e425@slint.fr> Thanks Erik for your comments that show me the need of precision. On 16/06/2016 19:58, Erik Hanson wrote: >> On Thu, 16 Jun 2016 18:16:16 +0200 Didier Spaier wrote: > > Since this is intended as RFC, these are my comments and not meant to > be me setting anything in stone. > >> But David has written scripts that automatize finding the collisions >> and summarizing them per tuple of packages, see the post #21 in: >> http://www.linuxquestions.org/questions/slackware-14/slackpkg-add-on-for-sbo-4175581768/ > > I noticed a significant number of lines that are stock packages > conflicting with stock packages. These are not the concern of SBo, but > suggest to me, at least, that most conflicts are probably not very > important. As such, my initial concern is minimal. Important conflicts, > like incompatible .h files being replaced, need to be dealt with. Most of the conflicts of stock packages with stock packages are due to aaa_elflibs shipping shared objects provided in other packages to allow getting a working "minimal" system without installing the whole L series and also ease installation. That is no (more) an issue as now Pat ships the same versions in aaa_elflibs and the other packages anyway. Of course there have been files shipped in several glibc-* packages but that was never an issue as they were identical. But that Pat takes care of avoiding harmful conflicts doesn't mean that every SlackBuild maintainer (including myself for a very few ones) does. The difficulty is to spot the conflicts between thousands of packages that can be built from SlackBuilds provided by SBo and then take care of the "true positives", even if in the end there are not many (that I don't know). Of course it is the duty of the maintainers and it is obvious that no third-party package should replace a stock .h or a .so, or if it does at least with a rationale clearly stated in the README. It is maybe less obvious to maintainers that conflicts between two packages both built from stuff from @ SBo should (or at least could) be taken care as well. This proposal's goal is to help them doing that, not doing it for them. >> I found the results very interesting, so I suggest to build on that >> to spot and document the conflicts: >> _ at least in the README files of the conflicting packages, > > This is how it's supposed to already happen. If it's not true for some > scripts, their README files need to be updated. If anyone on the list > is willing to do the work and provide a patch set, that would be > appreciated. I'm guessing no admins really have the time for this. I > don't want to further burden the few that are working hard on getting > us ready for 14.2. Indeed: spotting the conflicts and documenting them in the README is the duty of the maintainers, not the admins. And if I detect some I promise to inform the maintainer and if need be to a provide patch set myself. > The idea of doing it after 14.2 is a bit moot, this can be done at any > time, and should be done sooner rather than later. That's right, I stand corrected. >> _ and also in a new "CONFLICTS:" field of .info. > > This will probably not happen. Conflicts such as wxPython and wxGTK > should have that info in the README already. As for individual files > conflicting, like docs or headers, that should be dealt with in some > way such as removing or renaming the files before generating the > package. If that's not possible (it breaks the package), then a mention > in the README is necessary. But in the few cases where there are real conflicts that can't be avoided modifying the scripts, would a .info that includes a CONFLICTS: line be accepted? Of course mentioning the conflicts in the README would stay mandatory. > By and large, there aren't many scripts that generate conflicting > packages. Not nearly enough to justify adding a CONFLICTS line to > the .info files. (n.b. this is in reference to packages and not files > within packages.) I would really know for sure how many scripts generate conflicting packages (real conflicts, not false positive) ;) >> The latter would then allow package tools to parse this information, >> either from the .info file or through the PACKAGES.TXT file. >> Some package tools can already make use of the CONFLICTS info in >> PACKAGES.TXT and it won't be difficult to copy from the former to the >> latter. > > We don't provide any PACKAGES.TXT file, since, you know, we don't > provide packages. :) If you meant SLACKBUILDS.TXT, there are no > CONFLICTS lines in said file. Yes I know that you don't provide packages ;) By the way the blog post http://alien.slackbook.org/blog/ten-years-of-slackbuilds-org/ is an interesting reading But feeding PACKAGES.TXT (in a third party repository neither maintained nor endorsed by SBo) from the .info files would be done by a volunteer, possibly the repo maintainer, not by a SBo admin. >> So here is my proposal (after adaptation if need be of the scripts >> written by David as a proof of concept). >> >> The list of collisions and tuples (packages included in Slackware and >> SlackBuilds hosted @ slackbuilds.org) would be updated after the 14.2 >> release. Then these list would be made available to all SlackBuild >> maintainers (maybe after sort of the tuples per maintainer), who >> could: _ check which of their packages are among the tuples if not >> yet sorted, _ grep collisions to see which files would be overwritten, >> _ assess the collisions: some are harmless others not, >> _ in case of harmful collisions, insert a warning in the README and/or >> feed .info with the name(s) of the conflicting packages, >> _ possibly consult with the maintainers of the conflicting > > Internally, we have a post-check script that checks for conflicts with > files that already exist in a full install. I'm not sure if every admin > is using it, or if it's broken, or this is the result of using git more > than we did in the past. Especially right now, while we're focusing on > 14.2, "updates" aren't running the way they usually would for the stable > branch. The usual way being to run the post-check during approval. > > Ultimately though, maintainers should be making sure this doesn't > happen. Yes. I already stated, I just suggest that they could (even if it is optional) take care of also of conflicts with files coming from packages built from SBo scripts. > Thanks for looking into it initially. Again, if anyone is willing to > step up and provide patches, that would probably be best. Some > maintainers are inactive (or busy, or uninterested) and simply creating > a list of them, and/or contacting them, may not prove entirely fruitful. Yes. Just making publicly available the files that document possible conflicts could be enough, then anyone willing to help could use that. Best regards, Didier From d.zlatanidis at gmail.com Fri Jun 17 11:44:03 2016 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Fri, 17 Jun 2016 14:44:03 +0300 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: References: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> <4a746b7a-33a2-5ddc-8003-3f628e162ae0@gmail.com> Message-ID: <085b794a-5bef-dbad-6892-85a83c8628e8@gmail.com> Ok... this is: http://pastebin.com/QujxPVNt On 06/16/2016 02:04 PM, Matteo Bernardini wrote: > 2016-06-16 13:02 GMT+02:00 Dimitris Zlatanidis : >> >> here it is: >> http://pastebin.com/5v6wd3sA > > maybe there's a misunderstanding: the config.log is a specific file > named that way into the sources folder, generated at the moment in > which ./configure is run. > you should be able to find it in the /tmp/SBo/gentoo-0.20.7 directory. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From willysr at slackbuilds.org Fri Jun 17 11:49:14 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 17 Jun 2016 18:49:14 +0700 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: <085b794a-5bef-dbad-6892-85a83c8628e8@gmail.com> References: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> <4a746b7a-33a2-5ddc-8003-3f628e162ae0@gmail.com> <085b794a-5bef-dbad-6892-85a83c8628e8@gmail.com> Message-ID: <37a179f4-88c2-a942-5aa7-2d631a75813a@slackbuilds.org> > Ok... this is: > > http://pastebin.com/QujxPVNt Here on my desktop (current x86) GTK_CFLAGS='-pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/$ GTK_LIBS='-lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0' on your log GTK_CFLAGS='' GTK_LIBS='' tested with plain ./configure here -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Fri Jun 17 12:41:23 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 17 Jun 2016 14:41:23 +0200 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: <085b794a-5bef-dbad-6892-85a83c8628e8@gmail.com> References: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> <4a746b7a-33a2-5ddc-8003-3f628e162ae0@gmail.com> <085b794a-5bef-dbad-6892-85a83c8628e8@gmail.com> Message-ID: 2016-06-17 13:44 GMT+02:00 Dimitris Zlatanidis : > Ok... this is: > > http://pastebin.com/QujxPVNt looking at this /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../../i586-slackware-linux/bin/ld: warning: libEGL.so.1, needed by /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libgtk-3.so, not found (try using -rpath or -rpath-link) /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglMakeCurrent' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglDestroySurface' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglChooseConfig' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglGetProcAddress' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglQueryContext' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglCreatePbufferSurface' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglQueryString' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglGetCurrentContext' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglSwapBuffers' /usr/lib/gcc/i586-slackware-linux/5.3.0/../../../libcairo.so: undefined reference to `eglGetCurrentSurface' are you using some proprietary drivers? to let the build go on maybe you should try removing them and reinstalling mesa: looks like some functions cairo links to and that should be available as part of the libEGL library, part of the mesa package, are not there anymore. Matteo From d.zlatanidis at gmail.com Fri Jun 17 12:47:30 2016 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Fri, 17 Jun 2016 15:47:30 +0300 Subject: [Slackbuilds-users] [slackbuilds-users] gentoo In-Reply-To: References: <5073a359-b242-5a07-9b2a-d76d8787be8e@gmail.com> <4a746b7a-33a2-5ddc-8003-3f628e162ae0@gmail.com> <085b794a-5bef-dbad-6892-85a83c8628e8@gmail.com> Message-ID: <461717b7-3d1b-0be3-3bc9-b45e3f4d4b17@gmail.com> Done!!! SOLVED, thank you Matteo! On 06/17/2016 03:41 PM, Matteo Bernardini wrote: > to let the build go on maybe you should try removing them and > reinstalling mesa: looks like some functions cairo links to and that > should be available as part of the libEGL library, part of the mesa > package, are not there anymore. From erik at slackbuilds.org Fri Jun 17 16:05:23 2016 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 17 Jun 2016 11:05:23 -0500 Subject: [Slackbuilds-users] SBo packages conflicts? In-Reply-To: <049e9941-031d-8155-18e7-8944bc93e425@slint.fr> References: <5f2984d4-2d2a-c25a-2a79-3d205b7af2c0@slint.fr> <20160616125839.37ec441d@shaggy.doo> <049e9941-031d-8155-18e7-8944bc93e425@slint.fr> Message-ID: <20160617110523.7ab36f2b@shaggy.doo> On Fri, 17 Jun 2016 12:20:11 +0200 Didier Spaier wrote: > The difficulty is to spot the conflicts between thousands of packages > that can be built from SlackBuilds provided by SBo and then take care > of the "true positives", even if in the end there are not many (that > I don't know). Something I hadn't considered when writing my original reply, and I think significantly changes my view on things, is that it's not practical at all for anyone to have all SBo-derived packages installed in order to check against them. A solution would be a FILES.TXT, but I consider this difficult to the point of impracticality. Some scripts have build-time options that could change the contents of the output package. The same is true for optional dependencies. Someone could build every possible combination of every SlackBuild in the repo, to generate a list of files, but I fear for that persons sanity. :) Consider how many permutations of ffmpeg there are. The 14.1 script has 33 options, and 36 optional dependencies. Some of those may have options/optional deps as well. Note that I'm not saying ffmpeg dumps out a different set of files in all those cases, for all I know it's the same every time. It serves as a good example though, showing that we can't predict what every package looks like on every persons system. > It is maybe less obvious to maintainers that conflicts between two > packages both built from stuff from @ SBo should (or at least could) > be taken care as well. Indeed, it wasn't even obvious to me until now. I had written from the perspective of checking against stock packages, in which case everything I said is still true. > But in the few cases where there are real conflicts that can't be > avoided modifying the scripts, would a .info that includes a > CONFLICTS: line be accepted? Of course mentioning the conflicts in > the README would stay mandatory. This information has to come from somewhere, it doesn't currently exist. As I expressed above, I don't have confidence in the ability to generate it. > > By and large, there aren't many scripts that generate conflicting > > packages. Not nearly enough to justify adding a CONFLICTS line to > > the .info files. (n.b. this is in reference to packages and not > > files within packages.) > > I would really know for sure how many scripts generate conflicting > packages (real conflicts, not false positive) ;) I imagine grep'ing the READMEs for 'conflicts' give a close approximation. > Yes. I already stated, I just suggest that they could (even if it is > optional) take care of also of conflicts with files coming from > packages built from SBo scripts. The best we can hope for, I think, is when someone notices conflicts they report it to the respective maintainers or this list. -- Erik From bryanlharris at gmail.com Fri Jun 17 21:47:16 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Fri, 17 Jun 2016 17:47:16 -0400 Subject: [Slackbuilds-users] Building libvirt In-Reply-To: References: Message-ID: Oh I see. The website builds URL links on the package page showing me the dependencies. I missed it before when I was looking at libvirt. But when I look at something like virt-manager it stands out at me. V/r, Bryan On Fri, Jun 17, 2016 at 4:04 AM, Bryan Harris wrote: > Oh I see, I only read the README. I'll read the info file from now on. > > V/r, > Bryan > > On Fri, Jun 17, 2016 at 2:05 AM, Matteo Bernardini < > matteo.bernardini at gmail.com> wrote: > >> 2016-06-17 2:35 GMT+02:00 Bryan Harris : >> > Any reason why libvirt didn't build without yajl? Perhaps it is a >> check in >> > the ./configure step? >> >> hi Bryan, >> >> yajl is a mandatory dependency of libvirt, not an optional one: as >> such, is listed in in the libvirt.info file in the variable REQUIRES >> and on the SBo's libvirt page >> >> https://slackbuilds.org/repository/14.1/libraries/libvirt/ >> >> 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/ >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From bryanlharris at gmail.com Sat Jun 18 00:32:27 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Fri, 17 Jun 2016 20:32:27 -0400 Subject: [Slackbuilds-users] cairo version Message-ID: Hello folks, I believe I've got myself into another confusing spot. While looking to install virt-manager, I arrive at the page for gtk-vnc, which explains that I need cairo 1.12.16 to work properly. The cairo that comes with Slackware 14.1 is 1.12.14, so I looked on SBo for a newer version. However, I don't see it on SBo. I recalled seeing that in the /slackware64-current folder I could see updated things for 14.2 (I think). So I decided to look in there. But I see only cairo 1.12.6 (what seems even older strangely). http://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/l/cairo/ Can anybody tell me where I can get the SBo script or package for cairo 1.12.14? Or what I'm doing wrong in this case? Thanks in advance. V/r, Bryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris at chrisn.me.uk Sat Jun 18 00:34:59 2016 From: chris at chrisn.me.uk (Chris Novakovic) Date: Sat, 18 Jun 2016 01:34:59 +0100 Subject: [Slackbuilds-users] cairo version In-Reply-To: References: Message-ID: On 18/06/2016 01:32, Bryan Harris wrote: > The cairo that comes with Slackware 14.1 is 1.12.14, so I looked on SBo > for a newer version. However, I don't see it on SBo. Per https://slackbuilds.org/guidelines/, SBo in general doesn't accept submissions for software that is included as part of Slackware. > I recalled seeing that in the /slackware64-current folder I could see > updated things for 14.2 (I think). So I decided to look in there. But > I see only cairo 1.12.6 (what seems even older strangely). > > http://slackware.mirrors.tds.net/pub/slackware/slackware64-current/source/l/cairo/ That's 1.14.16, not 1.12.6. :) From chris at chrisn.me.uk Sat Jun 18 00:36:47 2016 From: chris at chrisn.me.uk (Chris Novakovic) Date: Sat, 18 Jun 2016 01:36:47 +0100 Subject: [Slackbuilds-users] cairo version In-Reply-To: References: Message-ID: <14edfeb6-6a59-bcc4-d78e-af1db954e6e3@chrisn.me.uk> On 18/06/2016 01:34, Chris Novakovic wrote: > That's 1.14.16 D'oh --- 1.14.6, not 1.14.16. Newer than the 1.12 series, in any case. From bryanlharris at gmail.com Sat Jun 18 00:48:47 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Fri, 17 Jun 2016 20:48:47 -0400 Subject: [Slackbuilds-users] cairo version In-Reply-To: <14edfeb6-6a59-bcc4-d78e-af1db954e6e3@chrisn.me.uk> References: <14edfeb6-6a59-bcc4-d78e-af1db954e6e3@chrisn.me.uk> Message-ID: Aha! Yes, I got confused after arriving to the website with the 14.2 stuff. I wonder if it's possible to obtain dyslexia later in life... Thanks. I will try that one out. V/r, Bryan On Fri, Jun 17, 2016 at 8:36 PM, Chris Novakovic wrote: > On 18/06/2016 01:34, Chris Novakovic wrote: > > That's 1.14.16 > > D'oh --- 1.14.6, not 1.14.16. Newer than the 1.12 series, in any case. > > _______________________________________________ > 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 edps.mundognu at gmail.com Sat Jun 18 19:19:48 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Sat, 18 Jun 2016 16:19:48 -0300 Subject: [Slackbuilds-users] Mutagen and Quodlibet SlackBuilds Message-ID: The SlackBuild "quodlibet" is a long time without updating, this is fact, actually in a 2.4.1 version on SlackBuilds. In new versions, e.g., 3.6.2, some things are necessary for the correct compilation of program. Among them, this requires the version 1.32 of SlackBuild "mutagen" whose link and MD5 hash are: DOWNLOAD = "https://bitbucket.org/lazka/mutagen/downloads/mutagen-1.32.tar.gz" MD5SUM = "349b987d26dbf15f64919f80c060eb14" Regarding SlackBuild "quodlibet" you must modify the file quodlibet.info in REQUIRES line to the following: REQUIRES = "gst-plugins-bad gst-python gst-plugins-ugly mutagen" And add the following in the README file: Optional dependencies: feedparser, musicbrainzngs. Given the above, i would become the maintainer of SlackBuild "quodlibet" if possible (and if no objections). Follow the SlackBuild attached which was tested on a clean install of Slackware -current with branch "master" instead of 14.1. -------------- next part -------------- A non-text attachment was scrubbed... Name: quodlibet.tar.gz Type: application/x-gzip Size: 10240 bytes Desc: not available URL: From acohen36 at linuxquestions.net Sat Jun 18 22:55:50 2016 From: acohen36 at linuxquestions.net (Aaron Cohen) Date: Sat, 18 Jun 2016 15:55:50 -0700 Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 Message-ID: <20160618155550.5F324286@m0087792.ppops.net> What's the current status on having Slackbuilds available and working for the impending Slackware 14.2 release and even for current pre-14.2 builds? Read through the latest Current (pre-release) ChangeLog for x86 (32-bit) at http://www.slackware.com/changelog/current.php?cpu=i386 and already downloaded and installed one of the latest pre-14.2 builds from http://bear.alienbase.nl/mirrors/slackware/slackware-current-iso/ The SlackBuild Usage HOWTO at https://slackbuilds.org/howto/ still declares "All of our scripts are written for usage on the latest stable release of Slackware" And there doesn't seem to be an easy way to get to updated Slackbuild repositories other than from https://slackbuilds.org/repository/14.1/ https://slackbuilds.org/slackbuilds/14.1/ ftp://slackbuilds.org/ Last definitive post on this thread here was https://lists.slackbuilds.org/pipermail/slackbuilds-users/2016-May/016195.html dated over half-a-month ago as follows: David Spencer baildon.research at googlemail.com wrote on Sun May 29 23:23:14 UTC 2016: > Hey folks! > > So here we all are, waiting for the release of Slackware 14.2. It's > looking good, but nobody knows when it will be good enough for Patrick > :) > > Meanwhile, work is continuing to get SlackBuilds.org ready for the new > release. According to Willy there have been 2373 commits in the SBo > git repo since submissions were closed. That's about one commit every > 1hour 20min. You can see Willy's list here: > > http://pastebin.com/S63pPStU > > At this time there are only a few packages that fail to build, and all > the git commiters are getting a bit tired, so we would like to > challenge the community to help fix the last few problems. Your > reward will be a nice Thank You in the git repo :D > > Here are the first four ... if you can fix them, there will be some more later! -- Are there any guarantees that Slackbuilds in the abovelisted 14.1 repos will or even will NOT function properly using one of the latest pre-14.2 builds?? TY for any pointers here :-) -A --- When you must stand up for something important in the face of those who would readily cut you down, then you must continually remind yourself of the words of the great Mahatma Gandhi, "First they ignore you, then they laugh at you, then they fight you, then you win." -- _____________________________________________________________ Thank you for choosing LinuxQuestions. http://www.linuxquestions.org From edps.mundognu at gmail.com Sat Jun 18 19:43:56 2016 From: edps.mundognu at gmail.com (Edinaldo) Date: Sat, 18 Jun 2016 16:43:56 -0300 Subject: [Slackbuilds-users] How can submit new updates of my SlackBuilds? Message-ID: At this stage, when we are prepared to receive the new version of Slackware 14.2, i'm ask: how to submit new versions of my SlackBuilds? Or ... if I should wait for the release of this new version? Currently, i have the following SlackBuilds to be send: cantarell-fonts ddrescue-gui faba-icon-theme fbrowse-tray fish flacon gmusicbrowser-art google-cli libdbusmenu librep libuchardet menutray moka-icon-theme obbrowser obmenu-generator perl-File-Remove perl-Module-Build perl-Module-ScanDeps perl-Number-Bites-Human perl-extutils-makemaker perl-linux-desktop-files plank pycp rep-gtk ruby-faraday sawfish vivaldi vivaldi-codecs-ffmpeg-extra zuluCrypt And one to be solved: the SlackBuild "openbox-simple-theme" whose download is only available through my folder on DropBox (because the owner of theme) remove the same in https://www.gnome-look.org/ and https : //www.box-look.org/ Thanks. From baildon.research at googlemail.com Sat Jun 18 23:33:08 2016 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 19 Jun 2016 00:33:08 +0100 Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 In-Reply-To: <20160618155550.5F324286@m0087792.ppops.net> References: <20160618155550.5F324286@m0087792.ppops.net> Message-ID: > What's the current status on having Slackbuilds available and working for > the impending Slackware 14.2 release and even for current pre-14.2 builds? > What's the current status on having Slackbuilds available and working for > the impending Slackware 14.2 release and even for current pre-14.2 builds? Updated SlackBuilds for almost-14.2 are being developed in and are available from the master branch in the SBo git repository. I thought everybody knew that by now. Sorry if you missed it. https://slackbuilds.org/cgit/slackbuilds/ If you use (for example) sbopkg you can configure it to use the git master branch. (I'm not sure I remember how, so I'll leave that to someone else if you're stuck.) If you prefer manual builds, it might be easiest just to clone the whole repository. git clone git://slackbuilds.org/slackbuilds.git The good news is that everything in git master has been fixed for almost-14.2. *All* of them are working at this time. [*] Thanks to everybody that played a part in making this happen. Looking forward, what's likely to happen is that there will be a proper stable released SBo 14.2 branch and a nice announcement very soon after we get a proper stable Slackware 14.2 release and a nice announcement. That's what happened the last few times, anyway :D -D. [*] except that you might still encounter some source downloads that are broken. You can almost always find an alternative download in sbosrcarch: http://slackware.uk/sbosrcarch/ From clansco at clansco.org Thu Jun 9 11:30:08 2016 From: clansco at clansco.org (clansco) Date: Thu, 9 Jun 2016 13:30:08 +0200 Subject: [Slackbuilds-users] Moving stuff to gis/ ? In-Reply-To: References: Message-ID: <20160609133008.799bc5aa1efc375aac8bdce8@clansco.org> On Wed, 8 Jun 2016 21:30:20 -0700 "Ryan P.C. McQuen" wrote: > > > > There's quite a lot of packages that could be moved to the gis/ > >> category. > > > > > +1 > > > -- > -Ryan > [ryanpcmcquen.org] +1 fal7i From willysr at slackbuilds.org Sun Jun 19 00:37:48 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Jun 2016 07:37:48 +0700 Subject: [Slackbuilds-users] How can submit new updates of my SlackBuilds? In-Reply-To: References: Message-ID: > At this stage, when we are prepared to receive the new version of > Slackware 14.2, i'm ask: > > how to submit new versions of my SlackBuilds? > > Or ... if I should wait for the release of this new version? > > Currently, i have the following SlackBuilds to be send: > > > cantarell-fonts > ddrescue-gui > faba-icon-theme > fbrowse-tray > fish > flacon > gmusicbrowser-art > google-cli > libdbusmenu > librep > libuchardet > menutray > moka-icon-theme > obbrowser > obmenu-generator > perl-File-Remove > perl-Module-Build > perl-Module-ScanDeps > perl-Number-Bites-Human > perl-extutils-makemaker > perl-linux-desktop-files > plank > pycp > rep-gtk > ruby-faraday > sawfish > vivaldi > vivaldi-codecs-ffmpeg-extra > zuluCrypt Hi Edinaldo There are several options 1. If you use GIT, you can push your changes in your repository and we can pull it into our branch. Make sure you follow our commit message standard (see https://slackbuilds.org/cgit/slackbuilds/) 2. If you don't use git, you can send the diff/patch for each of your packages to the list. Please make sure you already grab the latest version from master branch (again, see the latest update in https://slackbuilds.org/cgit/slackbuilds/) please note that some of your packages *may* have been updated by us (admins) during development cycle. -- 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 Jun 19 00:40:26 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Jun 2016 07:40:26 +0700 Subject: [Slackbuilds-users] Community Challenge! Help fix the last few SlackBuilds for 14.2 In-Reply-To: References: <20160618155550.5F324286@m0087792.ppops.net> Message-ID: <7da713d4-453e-ead6-9b1f-54d56a95dea1@slackbuilds.org> > If you use (for example) sbopkg you can configure it to use the git > master branch. (I'm not sure I remember how, so I'll leave that to > someone else if you're stuck.) https://slackblogs.blogspot.com/2016/01/help-testing-sbo-scripts-for-upcoming.html -- 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 Jun 19 00:46:39 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Jun 2016 07:46:39 +0700 Subject: [Slackbuilds-users] qt5 update in master Message-ID: Hi guys, just now all changes in the last few days have been merged back to master branch, including a Qt5 update to 5.6.1. This version brings a lot of new features as well as bug fixes according to https://wiki.qt.io/New_Features_in_Qt_5.6 BUT they removed 2 modules in this release: Qt WebKit Qt Declarative (Qt Quick 1) and they are deprecating another 2 modules in this release and they may be removed in future releases of Qt Qt Script Qt Enginio If you have packages that depends on Qt5, please help us test those packages against Qt 5.6.1. So far, here are the list that have qt5 in REQUIRES: academic/stellarium academic/ugene audio/acousticbrainz-gui audio/qjackctl desktop/lumina desktop/rss-guard development/fuel development/qbs development/qt-creator development/qt-creator3 development/zeal games/dustrac games/peg-e games/solarus-quest-editor games/vcmi gis/qmapshack graphics/fritzing graphics/librecad graphics/luminance-hdr graphics/nomacs graphics/photoqt graphics/phototonic graphics/qelectrotech graphics/scantailor libraries/poppler-qt5 libraries/python3-PyQt5 libraries/qmltermwidget multimedia/mscore multimedia/obs-studio multimedia/xvst network/cmst network/otter network/qTox network/wireshark office/sigil system/zuluCrypt 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 fernando.lopezjr at gmail.com Sun Jun 19 00:52:17 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 18 Jun 2016 18:52:17 -0600 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: there is Qt 5.7.0 out already. =| On Sat, Jun 18, 2016 at 6:46 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi guys, > > just now all changes in the last few days have been merged back to > master branch, including a Qt5 update to 5.6.1. > This version brings a lot of new features as well as bug fixes according > to https://wiki.qt.io/New_Features_in_Qt_5.6 > > BUT they removed 2 modules in this release: > Qt WebKit > Qt Declarative (Qt Quick 1) > > and they are deprecating another 2 modules in this release and they may > be removed in future releases of Qt > Qt Script > Qt Enginio > > If you have packages that depends on Qt5, please help us test those > packages against Qt 5.6.1. > > So far, here are the list that have qt5 in REQUIRES: > academic/stellarium > academic/ugene > audio/acousticbrainz-gui > audio/qjackctl > desktop/lumina > desktop/rss-guard > development/fuel > development/qbs > development/qt-creator > development/qt-creator3 > development/zeal > games/dustrac > games/peg-e > games/solarus-quest-editor > games/vcmi > gis/qmapshack > graphics/fritzing > graphics/librecad > graphics/luminance-hdr > graphics/nomacs > graphics/photoqt > graphics/phototonic > graphics/qelectrotech > graphics/scantailor > libraries/poppler-qt5 > libraries/python3-PyQt5 > libraries/qmltermwidget > multimedia/mscore > multimedia/obs-studio > multimedia/xvst > network/cmst > network/otter > network/qTox > network/wireshark > office/sigil > system/zuluCrypt > > 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Jun 19 00:54:05 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Jun 2016 07:54:05 +0700 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: <4f796bb7-ad69-fab9-1e60-9e68a6b7470e@slackbuilds.org> > there is Qt 5.7.0 out already. =| Yes, we are aware of that, but we prefer to wait until first point release (5.7.1) gets released to make sure it's stable enough -- 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 fernando.lopezjr at gmail.com Sun Jun 19 00:54:58 2016 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 18 Jun 2016 18:54:58 -0600 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: <4f796bb7-ad69-fab9-1e60-9e68a6b7470e@slackbuilds.org> References: <4f796bb7-ad69-fab9-1e60-9e68a6b7470e@slackbuilds.org> Message-ID: cool. On Sat, Jun 18, 2016 at 6:54 PM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > there is Qt 5.7.0 out already. =| > > Yes, we are aware of that, but we prefer to wait until first point > release (5.7.1) gets released to make sure it's stable enough > > > -- > 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/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Jun 19 01:07:11 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 19 Jun 2016 08:07:11 +0700 Subject: [Slackbuilds-users] Mutagen and Quodlibet SlackBuilds In-Reply-To: References: Message-ID: <51b7fa71-3f8c-c9e1-e92b-7216924ae1cd@slackbuilds.org> > Given the above, i would become the maintainer of SlackBuild "quodlibet" > if possible (and if no objections). You can ask the current maintainer, but it seems he is inactive for a long time. If you don't get any response for several days, you can step up and take the maintainership of this package -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Jun 19 06:41:20 2016 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 18 Jun 2016 23:41:20 -0700 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: <7b12d7dd-35cc-063e-b9b6-5e4e00b45c66@gmail.com> On 06/18/2016 05:46 PM, Willy Sudiarto Raharjo wrote: > Hi guys, > > just now all changes in the last few days have been merged back to > master branch, including a Qt5 update to 5.6.1. > This version brings a lot of new features as well as bug fixes according > to https://wiki.qt.io/New_Features_in_Qt_5.6 Successfully compiled and run libraries/qt5 academic/stellarium In a clean, updated qemu VM slackware64-current updated Jun 18 2016 18:26 PDT USA. packages installed and running under slackware64-current multilib. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Sun Jun 19 11:12:32 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 19 Jun 2016 13:12:32 +0200 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: <6c20652b-96dc-e948-edb8-a894302cdcb6@gmail.com> On 19/06/16 02:52, Fernando Lopez wrote: > there is Qt 5.7.0 out already. =| 5.6 has LTS, so I wouldn't mind sticking with it. -- Best regards, Andrzej Telszewski From dpross1100 at msn.com Sun Jun 19 13:41:46 2016 From: dpross1100 at msn.com (Daniel Prosser) Date: Sun, 19 Jun 2016 09:41:46 -0400 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: Hi, network/otter requires Qt Webkit, so it no longer works with Qt 5.6.1. However, the latest otter version 0.9.10 has Qt WebEngine support, and it does work with Qt 5.6.1. Patches for the version bump are attached. As a caveat, the release notes for otter refer to the Qt WebEngine support as "experimental." Dan (aka montagdude on LQ) On Sunday, June 19, 2016 07:46:39 AM Willy Sudiarto Raharjo wrote: > Hi guys, > > just now all changes in the last few days have been merged back to > master branch, including a Qt5 update to 5.6.1. > This version brings a lot of new features as well as bug fixes according > to https://wiki.qt.io/New_Features_in_Qt_5.6 > > BUT they removed 2 modules in this release: > Qt WebKit > Qt Declarative (Qt Quick 1) > > and they are deprecating another 2 modules in this release and they may > be removed in future releases of Qt > Qt Script > Qt Enginio > > If you have packages that depends on Qt5, please help us test those > packages against Qt 5.6.1. > > So far, here are the list that have qt5 in REQUIRES: > academic/stellarium > academic/ugene > audio/acousticbrainz-gui > audio/qjackctl > desktop/lumina > desktop/rss-guard > development/fuel > development/qbs > development/qt-creator > development/qt-creator3 > development/zeal > games/dustrac > games/peg-e > games/solarus-quest-editor > games/vcmi > gis/qmapshack > graphics/fritzing > graphics/librecad > graphics/luminance-hdr > graphics/nomacs > graphics/photoqt > graphics/phototonic > graphics/qelectrotech > graphics/scantailor > libraries/poppler-qt5 > libraries/python3-PyQt5 > libraries/qmltermwidget > multimedia/mscore > multimedia/obs-studio > multimedia/xvst > network/cmst > network/otter > network/qTox > network/wireshark > office/sigil > system/zuluCrypt > > Thanks -------------- next part -------------- A non-text attachment was scrubbed... Name: otter.SlackBuild.patch Type: text/x-patch Size: 291 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: otter.info.patch Type: text/x-patch Size: 514 bytes Desc: not available URL: From willysr at slackbuilds.org Sun Jun 19 18:32:03 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Jun 2016 01:32:03 +0700 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: > network/otter requires Qt Webkit, so it no longer works with Qt 5.6.1. > However, the latest otter version 0.9.10 has Qt WebEngine support, and it does > work with Qt 5.6.1. Patches for the version bump are attached. As a caveat, > the release notes for otter refer to the Qt WebEngine support as > "experimental." Thanks, applied 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 bdiego at gmail.com Sun Jun 19 19:45:08 2016 From: bdiego at gmail.com (Diego Borghetti) Date: Sun, 19 Jun 2016 20:45:08 +0100 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: Hi, I try to update cmst to a new version and so far, no luck to make it work again. The qt5 version is not the problem, that is fine. It's the dbus and connman interface and to be honest, I'm tire of fight with dbus/connman. I already remove the package from my system and I'm using my old method to handle the networking. I would say keep the package for 14.1 if you want (which is working without problem) or remove it from slackbuilds. On Sun, Jun 19, 2016 at 1:46 AM, Willy Sudiarto Raharjo wrote: > Hi guys, > > just now all changes in the last few days have been merged back to > master branch, including a Qt5 update to 5.6.1. > This version brings a lot of new features as well as bug fixes according > to https://wiki.qt.io/New_Features_in_Qt_5.6 > > BUT they removed 2 modules in this release: > Qt WebKit > Qt Declarative (Qt Quick 1) > > and they are deprecating another 2 modules in this release and they may > be removed in future releases of Qt > Qt Script > Qt Enginio > > If you have packages that depends on Qt5, please help us test those > packages against Qt 5.6.1. > > So far, here are the list that have qt5 in REQUIRES: > academic/stellarium > academic/ugene > audio/acousticbrainz-gui > audio/qjackctl > desktop/lumina > desktop/rss-guard > development/fuel > development/qbs > development/qt-creator > development/qt-creator3 > development/zeal > games/dustrac > games/peg-e > games/solarus-quest-editor > games/vcmi > gis/qmapshack > graphics/fritzing > graphics/librecad > graphics/luminance-hdr > graphics/nomacs > graphics/photoqt > graphics/phototonic > graphics/qelectrotech > graphics/scantailor > libraries/poppler-qt5 > libraries/python3-PyQt5 > libraries/qmltermwidget > multimedia/mscore > multimedia/obs-studio > multimedia/xvst > network/cmst > network/otter > network/qTox > network/wireshark > office/sigil > system/zuluCrypt > > 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/ > > -- -- Diego From slackalaxy at gmail.com Sun Jun 19 20:21:06 2016 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 19 Jun 2016 23:21:06 +0300 Subject: [Slackbuilds-users] Mutagen and Quodlibet SlackBuilds Message-ID: Hi, concerning QuodLibet's dependencies: the player can use XINE as its backend: https://quodlibet.readthedocs.io/en/latest/guide/playback/backends.html May be it should be mentioned in the README if users do not want to install gst-plugins-whatever? I wrote a post about it in my humble blog if someone want's to take a look: https://slackalaxy.wordpress.com/2015/05/23/quod-libet-an-audio-player-with-a-xine-backend/ bye Petar From thedoogster at gmail.com Sun Jun 19 20:34:05 2016 From: thedoogster at gmail.com (Doogster) Date: Sun, 19 Jun 2016 13:34:05 -0700 Subject: [Slackbuilds-users] Mutagen and Quodlibet SlackBuilds In-Reply-To: References: Message-ID: I completely missed what this discussion is about, but if someone's asking if they could take over ownership of mutagen, the answer is yes. On Sun, Jun 19, 2016 at 1:21 PM, Petar Petrov wrote: > Hi, > > concerning QuodLibet's dependencies: the player can use XINE as its backend: > https://quodlibet.readthedocs.io/en/latest/guide/playback/backends.html > > May be it should be mentioned in the README if users do not want to > install gst-plugins-whatever? I wrote a post about it in my humble > blog if someone want's to take a look: > > https://slackalaxy.wordpress.com/2015/05/23/quod-libet-an-audio-player-with-a-xine-backend/ > > bye > > Petar > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > From atelszewski at gmail.com Sun Jun 19 23:11:58 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 20 Jun 2016 01:11:58 +0200 Subject: [Slackbuilds-users] qt-creator3.SlackBuild removal Message-ID: Hi, Willy, please remove qt-creator3.SlackBuild from master. It is now provided by qt-creator.SlackBuild, actually version 4, but it is line continuation. And for legacy purposes, Qt Creator 2 is now provided by qt-creator2 SlackBuild, which was previously named qt-creator.SlackBuild. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Sun Jun 19 23:47:10 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Jun 2016 06:47:10 +0700 Subject: [Slackbuilds-users] qt-creator3.SlackBuild removal In-Reply-To: References: Message-ID: > Willy, please remove qt-creator3.SlackBuild from master. > It is now provided by qt-creator.SlackBuild, actually version 4, but it > is line continuation. > > And for legacy purposes, Qt Creator 2 is now provided by qt-creator2 > SlackBuild, which was previously named qt-creator.SlackBuild. Done 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 atelszewski at gmail.com Sun Jun 19 23:51:04 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 20 Jun 2016 01:51:04 +0200 Subject: [Slackbuilds-users] qt-creator3.SlackBuild removal In-Reply-To: References: Message-ID: On 20/06/16 01:47, Willy Sudiarto Raharjo wrote: >> Willy, please remove qt-creator3.SlackBuild from master. >> It is now provided by qt-creator.SlackBuild, actually version 4, but it >> is line continuation. >> >> And for legacy purposes, Qt Creator 2 is now provided by qt-creator2 >> SlackBuild, which was previously named qt-creator.SlackBuild. > > Done in my branch > Thanks -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Mon Jun 20 00:00:29 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Jun 2016 07:00:29 +0700 Subject: [Slackbuilds-users] Mutagen and Quodlibet SlackBuilds In-Reply-To: References: Message-ID: <09ef9af1-0c1a-2018-1e34-ac33178c3fb4@slackbuilds.org> > concerning QuodLibet's dependencies: the player can use XINE as its backend: > https://quodlibet.readthedocs.io/en/latest/guide/playback/backends.html > > May be it should be mentioned in the README if users do not want to > install gst-plugins-whatever? I wrote a post about it in my humble > blog if someone want's to take a look: > > https://slackalaxy.wordpress.com/2015/05/23/quod-libet-an-audio-player-with-a-xine-backend/ Updated in my branch Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Mon Jun 20 00:55:14 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Jun 2016 07:55:14 +0700 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: > I try to update cmst to a new version and so far, no luck to make it work again. > The qt5 version is not the problem, that is fine. It's the dbus and > connman interface and to be honest, I'm tire of fight with > dbus/connman. > I already remove the package from my system and I'm using my old > method to handle the networking. I would say keep the package for 14.1 > if you want (which is working without problem) or remove it from > slackbuilds. I tried to build latest 2016.04.03 and it worked here, but i need to use root user instead of normal user when running it. maybe i need to start investigating the policy files -- 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 bdiego at gmail.com Mon Jun 20 09:11:54 2016 From: bdiego at gmail.com (Diego Borghetti) Date: Mon, 20 Jun 2016 10:11:54 +0100 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: I just try that here and also work (as root). I'm going to give a check to the policy files too, see if I can spot the problem. On Mon, Jun 20, 2016 at 1:55 AM, Willy Sudiarto Raharjo wrote: >> I try to update cmst to a new version and so far, no luck to make it work again. >> The qt5 version is not the problem, that is fine. It's the dbus and >> connman interface and to be honest, I'm tire of fight with >> dbus/connman. >> I already remove the package from my system and I'm using my old >> method to handle the networking. I would say keep the package for 14.1 >> if you want (which is working without problem) or remove it from >> slackbuilds. > > I tried to build latest 2016.04.03 and it worked here, but i need to use > root user instead of normal user when running it. > > maybe i need to start investigating the policy files > > -- > 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/ > > -- -- Diego From atelszewski at gmail.com Mon Jun 20 09:14:39 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 20 Jun 2016 11:14:39 +0200 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: <9789bcc5-f8cd-21e1-45bb-add08871ab86@gmail.com> On 19/06/16 02:46, Willy Sudiarto Raharjo wrote: > development/qbs > development/qt-creator Both qbs and qt-creator compile fine and seem to be running fine. Qt Creator version tested was 4.0.2. You might consider bumping the version in master. Diffs attached. Thanks! -- Best regards, Andrzej Telszewski -------------- next part -------------- A non-text attachment was scrubbed... Name: qt-creator.SlackBuild.diff Type: text/x-patch Size: 729 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: qt-creator.info.diff Type: text/x-patch Size: 597 bytes Desc: not available URL: From bdiego at gmail.com Mon Jun 20 10:39:24 2016 From: bdiego at gmail.com (Diego Borghetti) Date: Mon, 20 Jun 2016 11:39:24 +0100 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: Well, after digging a little around it I found out that the problem is not cmst. If you try to run connmanctl as normal user, you get something similar (Error getting services: Rejected send message). After some search, I found this: https://forum.voidlinux.eu/t/connman-needs-root/231/6 The problem is in the connman-nmcompat.conf file. I don't have NetworkManager on my machine so the 'deny' rule in that file is causing the problem (not really sure if the bug is in dbus or connman). I changed the rule from 'deny' to 'allow' and not only connmandctl is working again, also cmst (as normal user). Later today I will send a patch to upgrade cmst to the new release, but I'm not sure what to do about the dbus thing. I can try to submit a bug in connman and see what they say but my knowledge of dbus is not great. Can anyone see anything else here ? On Mon, Jun 20, 2016 at 10:11 AM, Diego Borghetti wrote: > I just try that here and also work (as root). I'm going to give a > check to the policy files too, see if I can spot the problem. > > On Mon, Jun 20, 2016 at 1:55 AM, Willy Sudiarto Raharjo > wrote: >>> I try to update cmst to a new version and so far, no luck to make it work again. >>> The qt5 version is not the problem, that is fine. It's the dbus and >>> connman interface and to be honest, I'm tire of fight with >>> dbus/connman. >>> I already remove the package from my system and I'm using my old >>> method to handle the networking. I would say keep the package for 14.1 >>> if you want (which is working without problem) or remove it from >>> slackbuilds. >> >> I tried to build latest 2016.04.03 and it worked here, but i need to use >> root user instead of normal user when running it. >> >> maybe i need to start investigating the policy files >> >> -- >> 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/ >> >> > > > > -- > -- > > Diego -- -- Diego From willysr at slackbuilds.org Mon Jun 20 13:51:27 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 20 Jun 2016 20:51:27 +0700 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: <9f5f47c3-4e80-2e1c-4a6d-630dba85850d@slackbuilds.org> > Well, after digging a little around it I found out that the problem is > not cmst. If you try to run connmanctl as normal user, you get > something similar (Error getting services: Rejected send message). > After some search, I found this: > > https://forum.voidlinux.eu/t/connman-needs-root/231/6 > > The problem is in the connman-nmcompat.conf file. I don't have > NetworkManager on my machine so the 'deny' rule in that file is > causing the problem (not really sure if the bug is in dbus or > connman). > I changed the rule from 'deny' to 'allow' and not only connmandctl is > working again, also cmst (as normal user). > > Later today I will send a patch to upgrade cmst to the new release, > but I'm not sure what to do about the dbus thing. > I can try to submit a bug in connman and see what they say but my > knowledge of dbus is not great. > > Can anyone see anything else here ? Yup, that fixed the problem here as well -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Mon Jun 20 18:48:27 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 20 Jun 2016 20:48:27 +0200 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: 2016-06-19 2:46 GMT+02:00 Willy Sudiarto Raharjo : > desktop/rss-guard ... > graphics/nomacs > graphics/photoqt ... > libraries/qmltermwidget ... > network/wireshark these are ok with the newer qt. Matteo From dave at dawoodfall.net Tue Jun 21 00:48:16 2016 From: dave at dawoodfall.net (David Woodfall) Date: Tue, 21 Jun 2016 01:48:16 +0100 Subject: [Slackbuilds-users] Driconf source location Message-ID: <20160621004816.GB16912@Blackswan> The source location for driconf is wrong and should be pointed at: http://pkgs.fedoraproject.org/repo/pkgs/driconf/driconf-0.9.1.tar.gz/76d610bcd56aa5e8a489debb5081178a/driconf-0.9.1.tar.gz If someone could correct that, I'd be grateful. -Dave From willysr at slackbuilds.org Tue Jun 21 06:09:26 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 21 Jun 2016 13:09:26 +0700 Subject: [Slackbuilds-users] Driconf source location In-Reply-To: <20160621004816.GB16912@Blackswan> References: <20160621004816.GB16912@Blackswan> Message-ID: <0e5300d6-9d58-d74b-80ba-a862c6084762@slackbuilds.org> > The source location for driconf is wrong and should be pointed at: > > http://pkgs.fedoraproject.org/repo/pkgs/driconf/driconf-0.9.1.tar.gz/76d610bcd56aa5e8a489debb5081178a/driconf-0.9.1.tar.gz both are valid sources, so no changes is needed -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From chris.willing at iinet.net.au Tue Jun 21 11:58:25 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 21 Jun 2016 21:58:25 +1000 Subject: [Slackbuilds-users] Which "go" to use? Message-ID: I see we have a development/google-go-lang SlackBuild. However we already have /usr/bin/go from the stock gcc-go package. Does anyone have insights as to which is the preferred one to use? chris From mail at rbn.im Tue Jun 21 12:20:51 2016 From: mail at rbn.im (Ruben Schuller) Date: Tue, 21 Jun 2016 14:20:51 +0200 Subject: [Slackbuilds-users] Which "go" to use? In-Reply-To: References: Message-ID: Hi! On 2016-06-21 13:58, Christoph Willing wrote: > I see we have a development/google-go-lang SlackBuild. However we > already have /usr/bin/go from the stock gcc-go package. > > Does anyone have insights as to which is the preferred one to use? They are different implementations of the Go language. I'd say the golang.org (google) version is more widely used than the gcc version (which I've never used). My two cents: From my own experience I'd recommend to just install the golang.org version to somewhere in your $HOME and setting PATH accordingly. Either use a precompiled version (https://golang.org/doc/install) or install from source (https://golang.org/doc/install/source), both options are easy :) Ruben From vbatts at gmail.com Tue Jun 21 15:13:33 2016 From: vbatts at gmail.com (Vincent Batts) Date: Tue, 21 Jun 2016 11:13:33 -0400 Subject: [Slackbuilds-users] Which "go" to use? In-Reply-To: References: Message-ID: the gcc-go implementation, while largely OK, is known to have more edge-cases that are not supported. The nice thing is that the gcc-go that is provided by gcc v5+ is useful for _compiling_ the golang.org compiler (as the compiler itself is now written in golang). If you're running -current (soon to be 14.2), then check out https://github.com/willysr/slackbuilds/tree/master/development/google-go-lang which is updated for latest upstream stable. On Tue, Jun 21, 2016 at 8:20 AM, Ruben Schuller wrote: > Hi! > > On 2016-06-21 13:58, Christoph Willing wrote: >> >> I see we have a development/google-go-lang SlackBuild. However we >> already have /usr/bin/go from the stock gcc-go package. >> >> Does anyone have insights as to which is the preferred one to use? > > > They are different implementations of the Go language. I'd say the > golang.org (google) version is more widely used than the gcc version (which > I've never used). > > My two cents: > From my own experience I'd recommend to just install the golang.org version > to somewhere in your $HOME and setting PATH accordingly. Either use a > precompiled version (https://golang.org/doc/install) or install from source > (https://golang.org/doc/install/source), both options are easy :) > > Ruben > > _______________________________________________ > 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 s.arcus at open-t.co.uk Tue Jun 21 17:07:49 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 21 Jun 2016 18:07:49 +0100 Subject: [Slackbuilds-users] New submission - Navit version R6771 Message-ID: <4a4060ff-8013-1408-fdb9-d38ed3dba36e@open-t.co.uk> I would like to submit scripts for the Navit gps navigation system (www.navit-project.org). It seems to compile fine and it has no compulsory dependencies on Slack. Gpsd is an optional dependency if wanting to use a usb gps receiver. I wonder if somebody can take a look at the doinst.sh file. I've removed what was obvious, but I don't use KDE or Gnome and couldn't quite figure out what code in there would apply to Navit (and what wouldn't). -------------- next part -------------- A non-text attachment was scrubbed... Name: navit.tar.gz Type: application/gzip Size: 3943 bytes Desc: not available URL: From bryanlharris at gmail.com Tue Jun 21 22:22:58 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Tue, 21 Jun 2016 18:22:58 -0400 Subject: [Slackbuilds-users] ptop home page & htop question Message-ID: Hello all, It appears the ptop home page has changed (from .me to .in). This one works for me but not the old one. http://black-perl.in/ptop/ Does anyone know what happened with htop? I used to install it but now I can't find it on SBo (only if I put "all"). V/r, Bryan -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Tue Jun 21 22:29:55 2016 From: baildon.research at googlemail.com (David Spencer) Date: Tue, 21 Jun 2016 23:29:55 +0100 Subject: [Slackbuilds-users] ptop home page & htop question In-Reply-To: References: Message-ID: > Does anyone know what happened with htop? It's been part of Slackware since 14.0 and consequently was removed from SBo's repo when 14.0 was released. If you have a full install of Slackware, you already have htop. -D. From bdiego at gmail.com Tue Jun 21 22:30:53 2016 From: bdiego at gmail.com (Diego Borghetti) Date: Tue, 21 Jun 2016 23:30:53 +0100 Subject: [Slackbuilds-users] ptop home page & htop question In-Reply-To: References: Message-ID: htop is part of slackware. On Tue, Jun 21, 2016 at 11:22 PM, Bryan Harris wrote: > Hello all, > > It appears the ptop home page has changed (from .me to .in). This one works > for me but not the old one. > > http://black-perl.in/ptop/ > > Does anyone know what happened with htop? I used to install it but now I > can't find it on SBo (only if I put "all"). > > V/r, > Bryan > > _______________________________________________ > 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/ > > -- -- Diego From bryanlharris at gmail.com Tue Jun 21 22:34:39 2016 From: bryanlharris at gmail.com (Bryan Harris) Date: Tue, 21 Jun 2016 18:34:39 -0400 Subject: [Slackbuilds-users] ptop home page & htop question In-Reply-To: References: Message-ID: Thanks for the info re: htop. V/r, Bryan On Tue, Jun 21, 2016 at 6:30 PM, Diego Borghetti wrote: > htop is part of slackware. > > On Tue, Jun 21, 2016 at 11:22 PM, Bryan Harris > wrote: > > Hello all, > > > > It appears the ptop home page has changed (from .me to .in). This one > works > > for me but not the old one. > > > > http://black-perl.in/ptop/ > > > > Does anyone know what happened with htop? I used to install it but now I > > can't find it on SBo (only if I put "all"). > > > > V/r, > > Bryan > > > > _______________________________________________ > > 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/ > > > > > > > > -- > -- > > Diego > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at iinet.net.au Wed Jun 22 02:53:30 2016 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 22 Jun 2016 12:53:30 +1000 Subject: [Slackbuilds-users] Which "go" to use? In-Reply-To: References: Message-ID: Thanks all, I built version from SBo master and since the resulting files didn't seem to clash with /usr/bin/go from gcc-go, I installed the package normally (into /). It all went well - I can now compile the go based project I was having problems with. chris On 22/06/16 01:13, Vincent Batts wrote: > the gcc-go implementation, while largely OK, is known to have more > edge-cases that are not supported. The nice thing is that the gcc-go > that is provided by gcc v5+ is useful for _compiling_ the golang.org > compiler (as the compiler itself is now written in golang). > If you're running -current (soon to be 14.2), then check out > https://github.com/willysr/slackbuilds/tree/master/development/google-go-lang > which is updated for latest upstream stable. > > > On Tue, Jun 21, 2016 at 8:20 AM, Ruben Schuller wrote: >> Hi! >> >> On 2016-06-21 13:58, Christoph Willing wrote: >>> >>> I see we have a development/google-go-lang SlackBuild. However we >>> already have /usr/bin/go from the stock gcc-go package. >>> >>> Does anyone have insights as to which is the preferred one to use? >> >> >> They are different implementations of the Go language. I'd say the >> golang.org (google) version is more widely used than the gcc version (which >> I've never used). >> >> My two cents: >> From my own experience I'd recommend to just install the golang.org version >> to somewhere in your $HOME and setting PATH accordingly. Either use a >> precompiled version (https://golang.org/doc/install) or install from source >> (https://golang.org/doc/install/source), both options are easy :) >> >> Ruben >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - http://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - http://slackbuilds.org/faq/ > > From atelszewski at gmail.com Wed Jun 22 12:45:57 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 22 Jun 2016 14:45:57 +0200 Subject: [Slackbuilds-users] Qt 5.6.1-1 Released To Fix A Critical Problem Message-ID: <99f47c7d-0e13-3a90-177a-a370b792795e@gmail.com> Hi, "Slipping into Qt 5.6.1 was a regression that prevented certain types of Qt Quick applications from working correctly. This issue with Qt 5.6.1 would cause Qt Quick applications to crash but did not affect the newer Qt 5.7.0 release." http://www.phoronix.com/scan.php?page=news_item&px=Qt-5.6.1-1-Released -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Wed Jun 22 13:00:39 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 22 Jun 2016 15:00:39 +0200 Subject: [Slackbuilds-users] Qt 5.6.1-1 Released To Fix A Critical Problem In-Reply-To: <99f47c7d-0e13-3a90-177a-a370b792795e@gmail.com> References: <99f47c7d-0e13-3a90-177a-a370b792795e@gmail.com> Message-ID: 2016-06-22 14:45 GMT+02:00 Andrzej Telszewski : > Hi, > > "Slipping into Qt 5.6.1 was a regression that prevented certain types of Qt > Quick applications from working correctly. This issue with Qt 5.6.1 would > cause Qt Quick applications to crash but did not affect the newer Qt 5.7.0 > release." > > http://www.phoronix.com/scan.php?page=news_item&px=Qt-5.6.1-1-Released Just pushed in my branch, thanks. Matteo From willysr at slackbuilds.org Sat Jun 25 02:03:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 25 Jun 2016 09:03:02 +0700 Subject: [Slackbuilds-users] qt5 update in master In-Reply-To: References: Message-ID: <87a1b991-cbe7-8be7-55ac-326b36651b5a@slackbuilds.org> > If you have packages that depends on Qt5, please help us test those > packages against Qt 5.6.1. I have merged all changes back to master branch and we have added 2 new packages: - qt5-webkit (it was previously included in Qt 5.5, but dropped in 5.6 and released as a separate source) - PyQt5 (python2 Qt5 binding) if there are still some packages that won't build with qt5, please try to add qt5-webkit and see if it works. Also please report it to us as well so we can fix it in the repository. Big thanks for the help in reviewing packages in our repo -- 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 414N at slacky.it Sat Jun 25 08:50:47 2016 From: 414N at slacky.it (414N) Date: Sat, 25 Jun 2016 10:50:47 +0200 Subject: [Slackbuilds-users] Terminator 0.98 "I'll be back" package update Message-ID: Hi everyone, I've gone mostly missing for some time but here I am with an update to the terminator package I maintain :-) May I ask what is the preferred way now to submit these updates? I cloned SBo git repo and applied my changes inside a branch (so a diff is easy to obtain), but I can also provide an "old-style" tarball file. -- Alan Alberghini -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Sat Jun 25 11:28:06 2016 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 25 Jun 2016 13:28:06 +0200 Subject: [Slackbuilds-users] Terminator 0.98 "I'll be back" package update In-Reply-To: References: Message-ID: 2016-06-25 10:50 GMT+02:00 414N <414N at slacky.it>: > Hi everyone, > > I've gone mostly missing for some time but here I am with an update to the > terminator package I maintain :-) > > May I ask what is the preferred way now to submit these updates? I cloned > SBo git repo and applied my changes inside a branch (so a diff is easy to > obtain), but I can also provide an "old-style" tarball file. Hi Alan, in this transitioning phase it's ok like this: I added your remote and got the commit, just edited the commit message, you can find it in my branch. https://slackbuilds.org/cgit/slackbuilds/log/?h=ponce-for-14.2 Matteo From 414N at slacky.it Sat Jun 25 13:42:42 2016 From: 414N at slacky.it (414N) Date: Sat, 25 Jun 2016 15:42:42 +0200 Subject: [Slackbuilds-users] Terminator 0.98 "I'll be back" package update In-Reply-To: References: Message-ID: Perfect, thank you! Alan Alberghini On 25/06/2016 13:28, Matteo Bernardini wrote: > 2016-06-25 10:50 GMT+02:00 414N <414N at slacky.it>: >> Hi everyone, >> >> I've gone mostly missing for some time but here I am with an update to the >> terminator package I maintain :-) >> >> May I ask what is the preferred way now to submit these updates? I cloned >> SBo git repo and applied my changes inside a branch (so a diff is easy to >> obtain), but I can also provide an "old-style" tarball file. > Hi Alan, > > in this transitioning phase it's ok like this: I added your remote and > got the commit, just edited the commit message, you can find it in my > branch. > > https://slackbuilds.org/cgit/slackbuilds/log/?h=ponce-for-14.2 > > 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/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Mon Jun 27 01:45:51 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 27 Jun 2016 03:45:51 +0200 Subject: [Slackbuilds-users] Bunch of possible version bumps Message-ID: <139749cf-04b2-6cea-89c7-c879c50a589a@gmail.com> Hi, Attached please find diffs for a bunch of possible version updates. I'm running these versions and haven't observed any problems. When it comes to virt-viewer, I could only test remote-viewer, since I don't use the whole virt-manager stack (so virt-viewer is not being built). In kicad.SlackBuild I updated the way the version string is passed to cmake. Please note that I'm not the maintainer of any of the SlackBuilds, so I cannot ensure that there isn't anything missing. I think that at least minor version bumps are safe to apply. -- Best regards, Andrzej Telszewski -------------- next part -------------- A non-text attachment was scrubbed... Name: eagle.diff Type: text/x-patch Size: 1083 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: elementary-xfce.diff Type: text/x-patch Size: 903 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: gammu.diff Type: text/x-patch Size: 787 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: kicad.diff Type: text/x-patch Size: 1069 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: liferea.diff Type: text/x-patch Size: 896 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smplayer.diff Type: text/x-patch Size: 1313 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smtube.diff Type: text/x-patch Size: 812 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: virt-viewer.diff Type: text/x-patch Size: 844 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xfce4-xkb-plugin.diff Type: text/x-patch Size: 960 bytes Desc: not available URL: From s.arcus at open-t.co.uk Mon Jun 27 12:09:02 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Mon, 27 Jun 2016 13:09:02 +0100 Subject: [Slackbuilds-users] New submission - Navit version R6771 In-Reply-To: References: <4a4060ff-8013-1408-fdb9-d38ed3dba36e@open-t.co.uk> Message-ID: On 21/06/16 20:38, David Spencer wrote: > Hi Sebastian, > > Have you been building navit on 14.1? It fails to build for me on -current: > http://dpaste.com/0B4BPDT Hi David - and thank you very much for your help. I have originally tested my scripts against a current(ish) Slack64 - about 5 weeks out of date. I have brought it up to date today using slackpkg - and my original script is still working ok - so I'm not entirely sure why it was failing in your case. Maybe there are some other differences between the systems we are testing on? From s.arcus at open-t.co.uk Mon Jun 27 12:31:21 2016 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Mon, 27 Jun 2016 13:31:21 +0100 Subject: [Slackbuilds-users] New submission - Navit version R6771 In-Reply-To: References: <4a4060ff-8013-1408-fdb9-d38ed3dba36e@open-t.co.uk> Message-ID: <1771642c-d8d3-b05d-7961-8e2a6ae20525@open-t.co.uk> On 21/06/16 21:17, David Spencer wrote: > Hi, me again, sorry, > > (1) Adding -fpermissive to the CMAKE_CXX_FLAGS flags fixes the build > failure :) Note that despite the warnings we apparently also need to > set it on CMAKE_C_FLAGS otherwise the build still fails (I wonder if > this is an upstream error that they're using the C flags when they're > compiling C++). > > (2) Don't use /usr/share/man. The Slackware location is /usr/man. If a > cmake project ignores MAN_INSTALL_DIR (sadly most of them do, and > sadly this is yet another one) then we have to move the manpages to > the right place in the SlackBuild. makepkg tried to warn you they were > in the wrong place ;) > > (3) The package is shipping these files: > > usr/share/icons/ > usr/share/icons/hicolor/ > usr/share/icons/hicolor/22x22/ > usr/share/icons/hicolor/22x22/apps/ > usr/share/icons/hicolor/22x22/apps/navit.png > usr/share/icons/hicolor/128x128/ > usr/share/icons/hicolor/128x128/apps/ > usr/share/icons/hicolor/128x128/apps/navit.png > usr/share/applications/ > usr/share/applications/navit.desktop > > ... so doinst.sh needs the bit that runs update-desktop-database and > the bit that runs gtk-update-icon-cache. > > There's nothing in /etc so you don't need the config stuff, there's > nothing in usr/share/mime, the other really unusual stuff doesn't > apply, so you just need those two bits. Thank you for all the pointers in this email and the email before - and for kindly doing the amendments for me! I did notice the comment about the location of man pages, but couldn't figure out at which point in the process and in which script I was supposed to move them. I can see what is supposed to happen now and where, based on your changes. > > I think we're done now. Please make sure you submit it to the gis/ > category when submissions reopen. I haven't been following closely enough the SBo mailing list I'm afraid. Are we in some sort of freeze at the moment until 14.2 is released - even when it comes to submitting new packages to the git repository? From willysr at slackbuilds.org Mon Jun 27 12:36:02 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 27 Jun 2016 19:36:02 +0700 Subject: [Slackbuilds-users] New submission - Navit version R6771 In-Reply-To: <1771642c-d8d3-b05d-7961-8e2a6ae20525@open-t.co.uk> References: <4a4060ff-8013-1408-fdb9-d38ed3dba36e@open-t.co.uk> <1771642c-d8d3-b05d-7961-8e2a6ae20525@open-t.co.uk> Message-ID: <66f9ff74-206f-9d56-dae5-245966370a55@slackbuilds.org> > On 21/06/16 21:17, David Spencer wrote: >> Hi, me again, sorry, >> >> (1) Adding -fpermissive to the CMAKE_CXX_FLAGS flags fixes the build >> failure :) Note that despite the warnings we apparently also need to >> set it on CMAKE_C_FLAGS otherwise the build still fails (I wonder if >> this is an upstream error that they're using the C flags when they're >> compiling C++). >> >> (2) Don't use /usr/share/man. The Slackware location is /usr/man. If a >> cmake project ignores MAN_INSTALL_DIR (sadly most of them do, and >> sadly this is yet another one) then we have to move the manpages to >> the right place in the SlackBuild. makepkg tried to warn you they were >> in the wrong place ;) >> >> (3) The package is shipping these files: >> >> usr/share/icons/ >> usr/share/icons/hicolor/ >> usr/share/icons/hicolor/22x22/ >> usr/share/icons/hicolor/22x22/apps/ >> usr/share/icons/hicolor/22x22/apps/navit.png >> usr/share/icons/hicolor/128x128/ >> usr/share/icons/hicolor/128x128/apps/ >> usr/share/icons/hicolor/128x128/apps/navit.png >> usr/share/applications/ >> usr/share/applications/navit.desktop >> >> ... so doinst.sh needs the bit that runs update-desktop-database and >> the bit that runs gtk-update-icon-cache. >> >> There's nothing in /etc so you don't need the config stuff, there's >> nothing in usr/share/mime, the other really unusual stuff doesn't >> apply, so you just need those two bits. > > Thank you for all the pointers in this email and the email before - and > for kindly doing the amendments for me! I did notice the comment about > the location of man pages, but couldn't figure out at which point in the > process and in which script I was supposed to move them. I can see what > is supposed to happen now and where, based on your changes. > >> >> I think we're done now. Please make sure you submit it to the gis/ >> category when submissions reopen. One more thing WARNING: zero length file usr/doc/navit-R6671/NEWS since it's empty, perhaps it is better NOT be include it in the final package -- 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 414N at slacky.it Mon Jun 27 20:00:46 2016 From: 414N at slacky.it (414N) Date: Mon, 27 Jun 2016 22:00:46 +0200 Subject: [Slackbuilds-users] New submission: glabels Message-ID: <1241eece-5a59-bc49-feb9-1e1bb4ef46e8@slacky.it> Hello everyone, I recently needed to design some CD labels and stumbled upon the glabels project and decided to package it, seeing that it goes easy on the dependencies list. I tested the latest version (3.4.0 as of writing) first on Slackware current and it seems to work fine, however, seeing that it doesn't compile on Slackware 14.1 because the GTK+3 version is too old, I decided to revert to version 3.2.1 that seems to work fine in both Slackware versions. Comments and critics are welcome -- Alan Alberghini -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: glabels.tar.gz Type: application/gzip Size: 10240 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Tue Jun 28 09:33:46 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 28 Jun 2016 11:33:46 +0200 Subject: [Slackbuilds-users] python3.SlackBuild error Message-ID: <76522cd4-ef5e-e662-66e5-1999033feedf@gmail.com> Hi, Trying to update to Python 3.5.2 I got the following error: [...] Python-3.5.2/Include/tupleobject.h patching file Modules/readline.c patching file Makefile.pre.in Hunk #1 succeeded at 567 (offset 3 lines). Hunk #2 succeeded at 606 (offset 7 lines). Hunk #3 succeeded at 695 (offset 7 lines). Hunk #4 succeeded at 1386 (offset 26 lines). patching file Lib/distutils/command/install.py patching file Lib/distutils/sysconfig.py patching file Lib/site.py patching file Lib/sysconfig.py patching file Makefile.pre.in patching file Modules/getpath.c Hunk #1 FAILED at 118. Hunk #2 succeeded at 494 (offset -17 lines). Hunk #3 succeeded at 683 (offset -17 lines). Hunk #4 succeeded at 695 (offset -17 lines). 1 out of 4 hunks FAILED -- saving rejects to file Modules/getpath.c.rej patching file configure Hunk #1 succeeded at 14662 (offset 198 lines). patching file setup.py Hunk #1 succeeded at 492 (offset 23 lines). Hunk #2 succeeded at 780 (offset 30 lines). Hunk #3 succeeded at 821 (offset 30 lines). python3: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Tue Jun 28 12:28:40 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 28 Jun 2016 19:28:40 +0700 Subject: [Slackbuilds-users] python3.SlackBuild error In-Reply-To: <76522cd4-ef5e-e662-66e5-1999033feedf@gmail.com> References: <76522cd4-ef5e-e662-66e5-1999033feedf@gmail.com> Message-ID: <93319216-ec9c-b721-5800-a2ece364d1ae@slackbuilds.org> > Trying to update to Python 3.5.2 I got the following error: > > [...] > Python-3.5.2/Include/tupleobject.h > patching file Modules/readline.c > patching file Makefile.pre.in > Hunk #1 succeeded at 567 (offset 3 lines). > Hunk #2 succeeded at 606 (offset 7 lines). > Hunk #3 succeeded at 695 (offset 7 lines). > Hunk #4 succeeded at 1386 (offset 26 lines). > patching file Lib/distutils/command/install.py > patching file Lib/distutils/sysconfig.py > patching file Lib/site.py > patching file Lib/sysconfig.py > patching file Makefile.pre.in > patching file Modules/getpath.c > Hunk #1 FAILED at 118. > Hunk #2 succeeded at 494 (offset -17 lines). > Hunk #3 succeeded at 683 (offset -17 lines). > Hunk #4 succeeded at 695 (offset -17 lines). > 1 out of 4 hunks FAILED -- saving rejects to file Modules/getpath.c.rej > patching file configure > Hunk #1 succeeded at 14662 (offset 198 lines). > patching file setup.py > Hunk #1 succeeded at 492 (offset 23 lines). > Hunk #2 succeeded at 780 (offset 30 lines). > Hunk #3 succeeded at 821 (offset 30 lines). this should be fixed now in master branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From atelszewski at gmail.com Tue Jun 28 14:54:24 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 28 Jun 2016 16:54:24 +0200 Subject: [Slackbuilds-users] python3.SlackBuild error In-Reply-To: <93319216-ec9c-b721-5800-a2ece364d1ae@slackbuilds.org> References: <76522cd4-ef5e-e662-66e5-1999033feedf@gmail.com> <93319216-ec9c-b721-5800-a2ece364d1ae@slackbuilds.org> Message-ID: <8d4f755a-f80e-1090-4d17-3d7118e94241@gmail.com> On 28/06/16 14:28, Willy Sudiarto Raharjo wrote: >> Trying to update to Python 3.5.2 I got the following error: >> >> [...] >> Python-3.5.2/Include/tupleobject.h >> patching file Modules/readline.c >> patching file Makefile.pre.in >> Hunk #1 succeeded at 567 (offset 3 lines). >> Hunk #2 succeeded at 606 (offset 7 lines). >> Hunk #3 succeeded at 695 (offset 7 lines). >> Hunk #4 succeeded at 1386 (offset 26 lines). >> patching file Lib/distutils/command/install.py >> patching file Lib/distutils/sysconfig.py >> patching file Lib/site.py >> patching file Lib/sysconfig.py >> patching file Makefile.pre.in >> patching file Modules/getpath.c >> Hunk #1 FAILED at 118. >> Hunk #2 succeeded at 494 (offset -17 lines). >> Hunk #3 succeeded at 683 (offset -17 lines). >> Hunk #4 succeeded at 695 (offset -17 lines). >> 1 out of 4 hunks FAILED -- saving rejects to file Modules/getpath.c.rej >> patching file configure >> Hunk #1 succeeded at 14662 (offset 198 lines). >> patching file setup.py >> Hunk #1 succeeded at 492 (offset 23 lines). >> Hunk #2 succeeded at 780 (offset 30 lines). >> Hunk #3 succeeded at 821 (offset 30 lines). > > this should be fixed now in master branch > Built successfully, thanks! -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Tue Jun 28 15:11:10 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 28 Jun 2016 22:11:10 +0700 Subject: [Slackbuilds-users] New submission: glabels In-Reply-To: <1241eece-5a59-bc49-feb9-1e1bb4ef46e8@slacky.it> References: <1241eece-5a59-bc49-feb9-1e1bb4ef46e8@slacky.it> Message-ID: <7625075e-219d-2a35-908f-bfd3ec1e3b14@slackbuilds.org> > I recently needed to design some CD labels and stumbled upon the glabels > project and decided to package it, seeing that it > goes easy on the dependencies list. > > I tested the latest version (3.4.0 as of writing) first on Slackware > current and it seems to work fine, however, seeing that it doesn't > compile on Slackware 14.1 because the GTK+3 version is too old, I > decided to revert to version 3.2.1 that seems to work fine in both > Slackware versions. > > Comments and critics are welcome hi Alan it's better to target for 14.2 as this will be the supported version in SBo soon once Slackware 14.2 is released -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Jun 30 16:56:20 2016 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 30 Jun 2016 23:56:20 +0700 Subject: [Slackbuilds-users] Bunch of possible version bumps In-Reply-To: <139749cf-04b2-6cea-89c7-c879c50a589a@gmail.com> References: <139749cf-04b2-6cea-89c7-c879c50a589a@gmail.com> Message-ID: <7032c0ad-12a7-0a0e-ab18-e24cb01a7b08@slackbuilds.org> > Attached please find diffs for a bunch of possible version updates. > I'm running these versions and haven't observed any problems. all pushed to master 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 atelszewski at gmail.com Thu Jun 30 20:04:15 2016 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 30 Jun 2016 22:04:15 +0200 Subject: [Slackbuilds-users] virt-viewer.SlackBuild: a small touch Message-ID: Hi, Attached is a patch to slightly change the virt-viewer.SlackBuild's line where the GTK is detected. Up to your taste. Other than that, I built remote-viewer and it seems to be working fine. -- Best regards, Andrzej Telszewski -------------- next part -------------- A non-text attachment was scrubbed... Name: virt-viewer.SlackBuild.diff Type: text/x-patch Size: 357 bytes Desc: not available URL: