From yth at ythogtha.org Fri Sep 1 13:57:22 2017 From: yth at ythogtha.org (Ythogtha) Date: Fri, 1 Sep 2017 15:57:22 +0200 Subject: [Slackbuilds-users] Can I submit a slackbuild that requires multilib? In-Reply-To: References: Message-ID: <20170901155722.db1bff4d6760d5cb2d361663@ythogtha.org> > On Mon, Aug 28, 2017 at 9:31 AM, David Spencer < > baildon.research at googlemail.com> wrote: > > > > > Hmm, can I change my mind on that? > > > > I'm wrong, and as you initially said Eric, this would be the only > > thing on SBo that absolutely requires x86_64 + multilib. Everything > > else will work on either normal i?86, or normal x86_64. The other > > admins are nervous about this -- and testing it would be difficult for > > us. So I don't think we can accept unity-editor, sorry :( > > > > However, thanks for asking, for me it raises another question. Can / > > should we help to find a way of making interesting SlackBuilds outside > > of SBo more discoverable? > > > > Thanks > > -D. > > > > ?Needless to say, that's disappointing. I understand the large storage > requirement is a concern.? But I'd like to hope that not officially > supporting multilib wouldn't translate into a ban. Considering that there > is a real need for multilibed systems and software and that Slackware 64 > was setup to make it easy to multilib, it's always struck me as odd that > SBo's multilib stance has been one of non-support. > > I'd like to see something different happen with multilib here. Even if the > lack of official support remains, I'd like to see a more permissive > policy. For instance, add a multilib flag to the .info files that would > mark a package as requiring multilib that could be checked during testing. > If multilib is required, the test box could skip over it and the web page > for that slackbuild would be marked as unsupported and requiring multilib. > Then you could allow people on the mailing list to give a best-effort > support if they wish. > > If you want more of a dissociation between slackbuilds.org packages and > multilib packages like this one, all you need is an extra IP, a vhost, and > extra repo. Just stand up a multilib.slackbuilds.org site on the same host > that has the same architecture as slackbuilds.org but only hosts packages > requiring multilib. It would always be small but would make it easy to > host multilib-only packages for Slackware users. Tools that add more > automation to slackbuilds, like sbopkg, could be updated to support > multiple repos, like slackpkplus does. There is at least another slackbuild which'll work on a multilib environment only. It exists because it also works on a pure x86 environment, x86_64 is marked as UNSUPPORTED. It's wine, and it can be built on a multilib x86_64 machine, by activating multilib shell environment, and removing UNSUPPORTED from the DOWNLOAD_64 on wine.info. Although it is still not supported by SBo. Does your package works on a 32-bit environment ? If so, you could still submit and maintain it, with a README.x86_64 that explains how to build it on an x86_64 multilib environment. It'll be up to everybody to read it and do it properly, while problems still won't be supported by SBo. Yth. From rshepard at appl-ecosys.com Fri Sep 1 17:52:00 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Sep 2017 10:52:00 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded Message-ID: I think the problem with not building gnucash-2.6.17 on my 32-bit 14.2 system is related to outdated SBo libraries, specifically libwebp and webkitgtk. libwebp is now at version 0.6.0; it built and upgraded on my desktop. webkitgtk is now at version 2.16.6; it apparently switched from configure; make; make install to CMake. When I try the SBo script (with the correct version number) it fails: "./webkitgtk.SlackBuild: line 75: ./configure: No such file or directory" One critical library missing from the gnucash build is provided by webkitgtk (/usr/lib/libicule.so.56), but the SBo version provides 51 instead. How do I modify the build script to use CMake so I can upgrade webkitgtk and see if that allows gnucash-2.6.17 to build on this system? Rich From slacker6896 at gmail.com Fri Sep 1 18:08:39 2017 From: slacker6896 at gmail.com (Sebastien BALLET) Date: Fri, 1 Sep 2017 20:08:39 +0200 Subject: [Slackbuilds-users] slackware-xdg-menu: missing directory Message-ID: Hello, the package *slackware-xdg-menu *does not create the required directory /var/cache/xdg-menu which prevents tool update-menus to work properly (*fails without any message*). The attached patch fixes this issue. -- SeB -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: slackware-xdg-menu-missing-dir.patch Type: text/x-patch Size: 519 bytes Desc: not available URL: From didier at slint.fr Fri Sep 1 18:14:00 2017 From: didier at slint.fr (Didier Spaier) Date: Fri, 1 Sep 2017 20:14:00 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: Message-ID: <93da88d2-7666-8ce5-0c24-6bd386c06683@slint.fr> Hello, Le 01/09/2017 ? 19:52, Rich Shepard a ?crit?: > ? I think the problem with not building gnucash-2.6.17 on my 32-bit 14.2 > system is related to outdated SBo libraries, specifically libwebp and > webkitgtk. > > ? libwebp is now at version 0.6.0; it built and upgraded on my desktop. > > ? webkitgtk is now at version 2.16.6; it apparently switched from configure; > make; make install to CMake. When I try the SBo script (with the correct > version number) it fails: > > "./webkitgtk.SlackBuild: line 75: ./configure: No such file or directory" > > ? One critical library missing from the gnucash build is provided by webkitgtk > (/usr/lib/libicule.so.56), but the SBo version provides 51 instead. > > ? How do I modify the build script to use CMake so I can upgrade webkitgtk > and see if that allows gnucash-2.6.17 to build on this system? If you don't build the packages at the versions for which the SlackBuilds have been tested you are on your own, Rich. Have a good day, Didier From rshepard at appl-ecosys.com Fri Sep 1 18:20:54 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Sep 2017 11:20:54 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <93da88d2-7666-8ce5-0c24-6bd386c06683@slint.fr> References: <93da88d2-7666-8ce5-0c24-6bd386c06683@slint.fr> Message-ID: On Fri, 1 Sep 2017, Didier Spaier wrote: > If you don't build the packages at the versions for which the SlackBuilds > have been tested you are on your own, Rich. Didier, The 2.4.11 version is well out of date and does not provide a current library version so gnucash-2.6.17 won't build on 32-bit systems. I'll need to build the new webkitgtk outside the SBo since there's no support for it. Rich From didier at slint.fr Fri Sep 1 18:32:24 2017 From: didier at slint.fr (Didier Spaier) Date: Fri, 1 Sep 2017 20:32:24 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <93da88d2-7666-8ce5-0c24-6bd386c06683@slint.fr> Message-ID: <69f93bea-64c1-5617-d606-fe9d1754c219@slint.fr> Le 01/09/2017 ? 20:20, Rich Shepard a ?crit?: > On Fri, 1 Sep 2017, Didier Spaier wrote: > >> If you don't build the packages at the versions for which the SlackBuilds >> have been tested you are on your own, Rich. > > Didier, > > ? The 2.4.11 version is well out of date and does not provide a current > library version so gnucash-2.6.17 won't build on 32-bit systems. And that maybe one of the reason why @ SBo gnucsh is still @ 2.6.17... > ? I'll need to build the new webkitgtk outside the SBo since there's no > support for it. It is on SBo but under a different name: http://slackbuilds.org/repository/14.2/libraries/webkit2gtk/ However if using it as a dependency of gnucash-2.6.17 fails, you are still on your own, as far as I am in concern at least. TIP: the benefit of using the most recent version of a given package are not always worth the efforts needed to build it ;) From dn2010 at gmail.com Fri Sep 1 18:32:52 2017 From: dn2010 at gmail.com (Daniil Bratashov) Date: Fri, 1 Sep 2017 22:32:52 +0400 Subject: [Slackbuilds-users] python3-matplotlib requires pyhon3-dateutil Message-ID: not a python-dateutil, it is now build without python3 support. WBR, Daniil Bratashov. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Fri Sep 1 18:59:52 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Sep 2017 11:59:52 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <69f93bea-64c1-5617-d606-fe9d1754c219@slint.fr> References: <93da88d2-7666-8ce5-0c24-6bd386c06683@slint.fr> <69f93bea-64c1-5617-d606-fe9d1754c219@slint.fr> Message-ID: On Fri, 1 Sep 2017, Didier Spaier wrote: > And that maybe one of the reason why @ SBo gnucsh is still @ 2.6.17... Didier, When I look at SBo I see gnucash-2.6.13 ... > It is on SBo but under a different name: > http://slackbuilds.org/repository/14.2/libraries/webkit2gtk/ ... and following the dependency link on that page (webkitgtk) I'm sent to 14.2 > Libraries > webkitgtk (2.4.11). I'll try webkit2gtk now. Thanks. Regards, Rich From didier at slint.fr Fri Sep 1 19:25:27 2017 From: didier at slint.fr (Didier Spaier) Date: Fri, 1 Sep 2017 21:25:27 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <93da88d2-7666-8ce5-0c24-6bd386c06683@slint.fr> <69f93bea-64c1-5617-d606-fe9d1754c219@slint.fr> Message-ID: <09fa21b0-2efd-142a-5cc3-47dd75ca54aa@slint.fr> Le 01/09/2017 ? 20:59, Rich Shepard a ?crit?: > On Fri, 1 Sep 2017, Didier Spaier wrote: > >> And that maybe one of the reason why @ SBo gnucsh is still? @ 2.6.17... > > Didier, > > ? When I look at SBo I see gnucash-2.6.13 ... Yes. I failed to re-read before posting, sorry >> It is on SBo but under a different name: >> http://slackbuilds.org/repository/14.2/libraries/webkit2gtk/ > > ? ... and following the dependency link on that page (webkitgtk) I'm sent to > 14.2 > Libraries > webkitgtk (2.4.11). I'll try webkit2gtk now. Thanks. The deps of a given software can vary upon versions. Here is the end of README.deps in the source archive of gncash-2.6.17: --- ?cut here --- Libraries/Deps -------------- required Version -------- _______ glib2 2.28.0 gtk+2 2.24.0 guile 1.8.5 or 2.0.0 libgnomecanvas 2.0 [lib]goffice 0.7.0 libxml2 2.5.10 libxslt swig 2.0.10 Only required to build from git or SVN. webkit 1.0 optional -------- aqbanking 4.0.0 online banking; also requires gwehywfar and ktoblzcheck libdbi 0.8.3 SQL backend; also requires at least one of libdbd-sqlite3, libdbd-mysql, or libdbd-pgsql libofx 0.9.0 OFX/QFX import python 2.4.0 python bindings; headers required, not just binaries. at runtime, required --------------------- a gsettings backend to store the gnucash global preferences in This backend is platform dependent. - linux: dconf - windows: registry - osx/quarz: plists Note that the osx and windows backends are built-in in gio for their respective platforms. On linux and similar systems, the dconf package should be installed. at runtime, suggested --------------------- isocodes: translation of currency names --- cut here --- As you can see, the webkit version requested is, not 2. But webkitg2gtk is webkit 2, not 1! From dario at darioniedermann.it Fri Sep 1 20:35:38 2017 From: dario at darioniedermann.it (Dario Niedermann) Date: Fri, 1 Sep 2017 22:35:38 +0200 Subject: [Slackbuilds-users] pure-ftpd: why --without-inetd ? Message-ID: <20170901203538.GA3754@darioniedermann.it> Hello. May I enquire why the SlackBuild for pure-ftpd-1.0.46 (for Slackware 14.2) configures the build without inetd (by including the '--without-inetd' configure option) ? TIA, DN -- Dario Niedermann. Also on the Internet at: gopher://darioniedermann.it/ <> https://www.darioniedermann.it/ From fernando.lopezjr at gmail.com Fri Sep 1 20:39:19 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Fri, 1 Sep 2017 14:39:19 -0600 Subject: [Slackbuilds-users] pure-ftpd: why --without-inetd ? In-Reply-To: <20170901203538.GA3754@darioniedermann.it> References: <20170901203538.GA3754@darioniedermann.it> Message-ID: i have no idea but there are two ftp packages included in slackware. proftpd vsftpd On Fri, Sep 1, 2017 at 2:35 PM, Dario Niedermann wrote: > Hello. May I enquire why the SlackBuild for pure-ftpd-1.0.46 (for > Slackware 14.2) configures the build without inetd (by including > the '--without-inetd' configure option) ? > > TIA, > DN > > > -- > Dario Niedermann. Also on the Internet at: > > gopher://darioniedermann.it/ <> https://www.darioniedermann.it/ > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Fri Sep 1 20:56:27 2017 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 01 Sep 2017 20:56:27 +0000 Subject: [Slackbuilds-users] pure-ftpd: why --without-inetd ? In-Reply-To: <20170901203538.GA3754@darioniedermann.it> References: <20170901203538.GA3754@darioniedermann.it> Message-ID: On Fri, Sep 1, 2017, 4:35 PM Dario Niedermann wrote: > Hello. May I enquire why the SlackBuild for pure-ftpd-1.0.46 (for > Slackware 14.2) configures the build without inetd (by including > the '--without-inetd' configure option) ? > > TIA, > DN > > > -- > Dario Niedermann. Also on the Internet at: > > gopher://darioniedermann.it/ <> > You should email the maintainer that question. They're the one who created the SlackBuild (or at least maintains it now) and they should be the one to answer the question. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Fri Sep 1 23:50:45 2017 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 1 Sep 2017 18:50:45 -0500 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: Message-ID: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> On 09/01/2017 12:52 PM, Rich Shepard wrote: > ? I think the problem with not building gnucash-2.6.17 on my 32-bit 14.2 > system is related to outdated SBo libraries, specifically libwebp and > webkitgtk. > > ? libwebp is now at version 0.6.0; it built and upgraded on my desktop. > > ? webkitgtk is now at version 2.16.6; it apparently switched from > configure; > make; make install to CMake. When I try the SBo script (with the correct > version number) it fails: > > "./webkitgtk.SlackBuild: line 75: ./configure: No such file or directory" > > ? One critical library missing from the gnucash build is provided by > webkitgtk > (/usr/lib/libicule.so.56), but the SBo version provides 51 instead. > > ? How do I modify the build script to use CMake so I can upgrade webkitgtk > and see if that allows gnucash-2.6.17 to build on this system? On a clean, 32-bit, full install of Slackware 14.2, using the scripts as they currently exist in the SBo repo, gnucash and it's dependencies built and installed without issue. libwebp-0.5.2-i586-1_SBo libofx-0.9.11-i486-1_SBo libgnomecanvas-2.30.3-i486-1_SBo goffice0.8-0.8.17-i486-2_SBo webkitgtk-2.4.11-i586-1_SBo gnucash-2.6.13-i586-1_SBo Also, as Matteo noted in your "CMake issues" thread, even gnucash 2.6.17 will build against what is in the repo. So, yet again Rich, the issue is not reproducible and appears to be on your end. -- Erik -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sat Sep 2 00:10:30 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Sep 2017 17:10:30 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> Message-ID: On Fri, 1 Sep 2017, Erik Hanson wrote: > So, yet again Rich, the issue is not reproducible and appears to be on > your end. Which is why I'm trying to learn where the conflict is so that it can be removed. Rich From rworkman at slackbuilds.org Sat Sep 2 01:06:37 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Fri, 1 Sep 2017 20:06:37 -0500 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> Message-ID: <20170901200637.0eb6b191@home.rlworkman.net> On Fri, 1 Sep 2017 17:10:30 -0700 (PDT) Rich Shepard wrote: > On Fri, 1 Sep 2017, Erik Hanson wrote: > > > So, yet again Rich, the issue is not reproducible and appears to be > > on your end. > > Which is why I'm trying to learn where the conflict is so that it > can be removed. You mentioned specific versions of some of those libraries (rather than versions of the *package* containing those libraries), e.g. libsomething.so.56. I'd almost bet dollars to donuts that gnucash is trying to link to a library that is linked to that libsomething.so.56, but since the libsomething.so.56 is not present any more, the link is failing. Given that the libsomething.so.56 or whatever it was is newer than what is in the SBo repo, it's probably an artifact from when you were trying newer versions of stuff, then building other stuff, and some of the other stuff got linked by yet other stuff, then you removed the what-was-"newer"-stuff above, built some yet-other-other stuff that didn't link the now-removed "newer" stuff, thus you figured everything was fine, and now here you are. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sat Sep 2 01:52:02 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 1 Sep 2017 18:52:02 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <20170901200637.0eb6b191@home.rlworkman.net> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> Message-ID: On Fri, 1 Sep 2017, Robby Workman wrote: > I'd almost bet dollars to donuts that gnucash is trying to link to a > library that is linked to that libsomething.so.56, but since the > libsomething.so.56 is not present any more, the link is failing. Robby, It's the opposite. Gnucash wants libicuil18n.so.51 (which was used in the prior gnucash) while libicuil18n.so.56 is in the current webkitgtk package. > Given that the libsomething.so.56 or whatever it was is newer than > what is in the SBo repo, it's probably an artifact from when you > were trying newer versions of stuff, It's not in the SBo repo under webkitgtk, but is there in webkit2gtk. That's what I learned from Didier this afternoon. The only 'newer' version I need to get running is gnucash-2.6.17 because the 14.2 upgrade did not load 2.6.16 (library version difference). If there is something subtle here that needs cleaning, as there seems to be, I want to find it and clean it out. There are no duplicates in of /usr in /usr/local so it must be elsewhere. Rich From erik at slackbuilds.org Sat Sep 2 02:48:52 2017 From: erik at slackbuilds.org (Erik Hanson) Date: Fri, 1 Sep 2017 21:48:52 -0500 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> Message-ID: <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> On 09/01/2017 08:52 PM, Rich Shepard wrote: > On Fri, 1 Sep 2017, Robby Workman wrote: > >> I'd almost bet dollars to donuts that gnucash is trying to link to a >> library that is linked to that libsomething.so.56, but since the >> libsomething.so.56 is not present any more, the link is failing. > > Robby, > > ? It's the opposite. Gnucash wants libicuil18n.so.51 (which was used in the > prior gnucash) while libicuil18n.so.56 is in the current webkitgtk package. This sounds like you're trying to run an already built gnucash binary and getting an error. You're not going to fix this by only rebuilding some related deps. >> Given that the libsomething.so.56 or whatever it was is newer than >> what is in the SBo repo, it's probably an artifact from when you >> were trying newer versions of stuff, > > ? It's not in the SBo repo under webkitgtk, but is there in webkit2gtk. > That's what I learned from Didier this afternoon. The only 'newer' version > I need to get running is gnucash-2.6.17 because the 14.2 upgrade did not > load 2.6.16 (library version difference). > > ? If there is something subtle here that needs cleaning, as there seems to > be, I want to find it and clean it out. There are no duplicates in of /usr > in /usr/local so it must be elsewhere. Remove gnucash and ALL related dependencies, along with anything else you've installed to try and solve this, and start over. Use what's in the SBo repo, /exactly/ as listed (no webkit2gtk instead of webkitgtk, etc., don't version bump anything) and you have a shot at getting a working gnucash package. -- Erik -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Sat Sep 2 07:26:32 2017 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Sat, 2 Sep 2017 09:26:32 +0200 Subject: [Slackbuilds-users] python3-matplotlib requires pyhon3-dateutil In-Reply-To: References: Message-ID: <260c39f4-1e20-6ad6-4fd7-888235327ef2@skmail.ikp.physik.tu-darmstadt.de> On 09/01/2017 08:32 PM, Daniil Bratashov wrote: > not a python-dateutil, it is now build without python3 support. > > WBR, Daniil Bratashov. > ... Hi! I just took a look at the git log and mentioned that the SlackBuilds changed since I submitted the python3-matplotlib one. At that time I wrote in the README (2nd Note) that "The python-dateutil and pytz dependencies must be compiled with Python 3 support.". This is still true for pytz but in April a python3-dateutil package got added and python-dateutil eventually dropped support for python3 (most probably with the last update in July). Sorry, but I wasn't aware of this change until now. Thus the list of required packages for python3-matplotlib has to be corrected accordingly. I'll do this with the next update. Actually there seem to be three approaches to python3: 1) SlackBuilds which automatically build a python3 version if one is detected 2) SlackBuilds which need an environment variable to be set for python3 support (I didn't fully check if the python2 version gets anyway installed or not, but for some it does) 3) SlackBuilds which have separate versions for python 2 and 3 Moreover, there is at least one pair of SlackBuilds (six and python3-six) which mix approaches 2 and 3. As much as I remember there was once a decision in favour of the last approach but maybe I'm wrong or its implementation is ongoing. Best regards, Serban Udrea From idlemoor at slackbuilds.org Sat Sep 2 10:02:23 2017 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 2 Sep 2017 11:02:23 +0100 Subject: [Slackbuilds-users] Updates - 20170902.1 Message-ID: Hi folks! Only 99 commits this week. Sat Sep 2 09:29:23 UTC 2017 academic/gspiceui: Updated for version 1.1.00. academic/libqalculate: Updated for version 2.0.0 academic/pulseview: Switch to https. academic/qalculate-gtk: Updated for version 2.0.0 academic/sigrok-cli: Switch to https. audio/guitarix: Updated for version 0.35.6. audio/kid3: Updated for version 3.5.0. desktop/fbmenugen: Updated for version 0.80. desktop/menutray: Updated for version 0.50. desktop/obbrowser: Updated for version 0.07. desktop/obmenu-generator: Updated for version 0.80. desktop/sawfish: Updated for version 1.12.90. desktop/slackware-xdg-menu: Fixed update-menus problem. development/asm6809: Fix bad commit d8d8d2be3. development/cppcms: Updated for version 1.1.1. development/dmd: Fixed download. development/jupyter-nbconvert: Updated for version 5.3.0. development/meson: Updated for version 0.42.0. development/rust: Updated for version 1.20.0. development/sassc: Added (C/C++ port of the Sass CSS precompiler). games/Pyfa: Updated for version 1.31.0. games/angband: Updated for version 4.1.0. games/commandergenius: Updated for version 1.9.9.5beta. games/doomretro: Updated for version 2.5.4. games/edgar: Updated for version 1.27. games/freeciv: Updated for version 2.5.9. games/instead: Updated for version 3.1.2. games/quake_shareware_data: Switch to https. games/solarus-quest-editor: Patched to fix guessing the assets dir. gis/Shapely: Updated for version 1.6.1. gis/geojson: Updated for version 2.1.0. graphics/barcode: Added (GNU Barcode). graphics/dxftoqet: Added (Element DXF Converter). graphics/opencollada: Updated for version 1.6.59 graphics/openimageio: Updated for version 1.7.17 libraries/VTK: Updated for version 8.0.1 libraries/appstream-glib: Updated for version 0.7.2. libraries/libiio: Added (Linux Industrial I/O library). libraries/libmediainfo: Updated for version 0.7.98. libraries/libnodave: Added (Siemens S7 300/400 PLC library). libraries/librep: Updated for version 0.92.7. libraries/libsass: Added (Sass compiler written in C++). libraries/libserialport: Switch to https. libraries/libsigrok: Switch to https. libraries/libsigrokdecode: Switch to https. libraries/libwacom: Updated for version 0.26. libraries/libzen: Updated for version 0.4.36. libraries/ogre: Updated to latest 1.9 commits. libraries/stfl: Switch to i586. libraries/unibilium: Updated for version 1.2.1. misc/gprename: Patched to use DESTDIR. misc/sigrok-firmware-fx2lafw: Switch to https. multimedia/mediainfo: Updated for version 0.7.98. network/2ping: Added (bi-directional ping utility). network/mrtg: Switch to https. network/newsbeuter: Apply Podbeuter segfault fix. network/phpmyadmin: Updated for version 4.7.4. network/plowshare-modules: Updated for version 952eceb. network/plowshare: Updated for version 2.1.7. network/sickrage: Updated for version 2017.06.05_1. network/slimjet: Updated for version 15.1.1.0. network/tor: Updated for version 0.3.0.10. network/tornado: Updated for version 4.5.2. network/uget: Updated for version 2.0.10. network/wireshark: Updated for version 2.4.1. network/yandex-browser-beta: Updated for version 17.7.1.802. network/yle-dl: Added (Download videos from Yle servers). office/LibreOffice: Updated for version 5.4.1.2 office/calibre: Updated for version 3.7.0 office/extractpdfmark: Added (extract page mode etc from PDF). office/libreoffice-helppack: Updated for version 5.4.1. office/libreoffice-langpack: Updated for version 5.4.1. office/libreoffice: Updated for version 5.4.1. office/pdfchain: Updated for version 0.4.4.2. perl/perl-Math-GMPf: Updated for version 0.43. perl/perl-Sidef: Updated for version 3.03. python/dulwich: Updated for version 0.18.2. python/egenix-mx-base: Switch to https. python/hg-git: Updated for version 0.8.9. python/python-gattlib: Fixed odd permissions on some files. python/python-keyutils: Fix dep. python/python-progress: Added (easy to use progress bars). python/python-whisper: Fix SlackBuild. python/python3-tornado: Updated for version 4.5.2. system/ffproxy: Added (filtering HTTP/HTTPS proxy server). system/fileschanged: Added (File Alteration Monitor client). system/fpm2: Switch to https. system/fwupd: Updated for version 0.9.7. system/fzf: Updated for version 0.17.0. system/hfsprogs: Added (hfs+ user space utils). system/hungrycat: Updated for version 0.4. system/iucode_tool: Updated for version 2.2. system/mariadb-plugin-saslauthd: Updated for version 1.2. system/nagvis: Fixed build. system/noto-emoji: Updated for version gita4ddd5b. system/pv: New maintainer. system/ripgrep: Added (line oriented search tool). system/secure-delete: Fixed download. system/wine-staging: Updated for version 2.15. +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From am.marconi at gmx.com Sat Sep 2 14:33:26 2017 From: am.marconi at gmx.com (Andrea Maria Marconi) Date: Sat, 2 Sep 2017 16:33:26 +0200 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio Message-ID: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> Hi all, I'm experiencing problems upgrading 4 programs both using sbotools and building packages in the "standard" way. The oldest package I'm not able to upgrade is opencolorio. I attach here the last lines of the output. These are coming out from the command sboupgrade -r opencolorio If you have any indication it would be much appreciated. Thanks. Andrea --------begin included text ----- [ 65%] Building CXX object src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/main.cpp.o [ 66%] Linking CXX executable ocioconvert /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: warning: libavcodec.so.56, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: warning: libavformat.so.56, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: warning: libavutil.so.54, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: warning: libswscale.so.3, needed by /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, not found (try using -rpath or -rpath-link) /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: warning: libavresample.so.2, needed by /usr/lib64/libopencv_videoio.so.3.1, not found (try using -rpath or -rpath-link) /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_codec_get_id at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_malloc at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avcodec_find_encoder at LIBAVCODEC_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_freep at LIBAVUTIL_54" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "sws_getContext at LIBSWSCALE_3" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avcodec_close at LIBAVCODEC_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avformat_free_context at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_guess_codec at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avformat_write_header at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_sub_q at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_opt_set at LIBAVUTIL_54" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_free at LIBAVUTIL_54" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_seek_frame at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avcodec_flush_buffers at LIBAVCODEC_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avpicture_get_size at LIBAVCODEC_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avcodec_get_context_defaults3 at LIBAVCODEC_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_codec_get_tag at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_frame_free at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_guess_format at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_write_frame at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_free_packet at LIBAVCODEC_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avformat_alloc_context at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avpicture_fill at LIBAVCODEC_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_dict_free at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_write_trailer at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avcodec_open2 at LIBAVCODEC_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avformat_open_input at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_dict_get at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avformat_network_init at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avformat_find_stream_info at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avio_open at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avcodec_decode_video2 at LIBAVCODEC_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_register_all at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "sws_getCachedContext at LIBSWSCALE_3" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avformat_new_stream at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avcodec_encode_video2 at LIBAVCODEC_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_rescale_q at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avformat_get_mov_video_tags at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_lockmgr_register at LIBAVCODEC_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_init_packet at LIBAVCODEC_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_log_set_level at LIBAVUTIL_54" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_read_frame at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avcodec_find_decoder at LIBAVCODEC_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "sws_freeContext at LIBSWSCALE_3" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "sws_scale at LIBSWSCALE_3" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "avformat_close_input at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_dict_set at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avio_close at LIBAVFORMAT_56" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "avformat_get_riff_video_tags at LIBAVFORMAT_56" /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: riferimento non definito a "av_frame_alloc at LIBAVUTIL_54" /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a "av_reduce at LIBAVUTIL_54" collect2: error: ld returned 1 exit status src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/build.make:176: set di istruzioni per l'obiettivo "src/apps/ocioconvert/ocioconvert" non riuscito make[2]: *** [src/apps/ocioconvert/ocioconvert] Errore 1 make[1]: *** [src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all] Errore 2 CMakeFiles/Makefile2:247: set di istruzioni per l'obiettivo "src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all" non riuscito make: *** [all] Errore 2 Makefile:160: set di istruzioni per l'obiettivo "all" non riuscito Failures: ? opencolorio: opencolorio.SlackBuild return non-zero From slackbuilds at jaxartes.net Sat Sep 2 15:02:46 2017 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sat, 02 Sep 2017 08:02:46 -0700 Subject: [Slackbuilds-users] Updates - 20170902.1 In-Reply-To: References: Message-ID: <34208394.W27sRB9cL4@wintermute> On Saturday, September 2, 2017 3:02:23 AM PDT David Spencer wrote: > Hi folks! > > Only 99 commits this week. > > Sat Sep 2 09:29:23 UTC 2017 > academic/gspiceui: Updated for version 1.1.00. > academic/libqalculate: Updated for version 2.0.0 > academic/pulseview: Switch to https. > academic/qalculate-gtk: Updated for version 2.0.0 > academic/sigrok-cli: Switch to https. > audio/guitarix: Updated for version 0.35.6. > audio/kid3: Updated for version 3.5.0. > desktop/fbmenugen: Updated for version 0.80. > desktop/menutray: Updated for version 0.50. > desktop/obbrowser: Updated for version 0.07. > desktop/obmenu-generator: Updated for version 0.80. > desktop/sawfish: Updated for version 1.12.90. > desktop/slackware-xdg-menu: Fixed update-menus problem. > development/asm6809: Fix bad commit d8d8d2be3. > development/cppcms: Updated for version 1.1.1. > development/dmd: Fixed download. > development/jupyter-nbconvert: Updated for version 5.3.0. > development/meson: Updated for version 0.42.0. > development/rust: Updated for version 1.20.0. > development/sassc: Added (C/C++ port of the Sass CSS precompiler). > games/Pyfa: Updated for version 1.31.0. > games/angband: Updated for version 4.1.0. > games/commandergenius: Updated for version 1.9.9.5beta. > games/doomretro: Updated for version 2.5.4. > games/edgar: Updated for version 1.27. > games/freeciv: Updated for version 2.5.9. > games/instead: Updated for version 3.1.2. > games/quake_shareware_data: Switch to https. > games/solarus-quest-editor: Patched to fix guessing the assets dir. > gis/Shapely: Updated for version 1.6.1. > gis/geojson: Updated for version 2.1.0. > graphics/barcode: Added (GNU Barcode). > graphics/dxftoqet: Added (Element DXF Converter). > graphics/opencollada: Updated for version 1.6.59 > graphics/openimageio: Updated for version 1.7.17 > libraries/VTK: Updated for version 8.0.1 > libraries/appstream-glib: Updated for version 0.7.2. > libraries/libiio: Added (Linux Industrial I/O library). > libraries/libmediainfo: Updated for version 0.7.98. > libraries/libnodave: Added (Siemens S7 300/400 PLC library). > libraries/librep: Updated for version 0.92.7. > libraries/libsass: Added (Sass compiler written in C++). > libraries/libserialport: Switch to https. > libraries/libsigrok: Switch to https. > libraries/libsigrokdecode: Switch to https. > libraries/libwacom: Updated for version 0.26. > libraries/libzen: Updated for version 0.4.36. > libraries/ogre: Updated to latest 1.9 commits. > libraries/stfl: Switch to i586. > libraries/unibilium: Updated for version 1.2.1. > misc/gprename: Patched to use DESTDIR. > misc/sigrok-firmware-fx2lafw: Switch to https. > multimedia/mediainfo: Updated for version 0.7.98. > network/2ping: Added (bi-directional ping utility). > network/mrtg: Switch to https. > network/newsbeuter: Apply Podbeuter segfault fix. > network/phpmyadmin: Updated for version 4.7.4. > network/plowshare-modules: Updated for version 952eceb. > network/plowshare: Updated for version 2.1.7. > network/sickrage: Updated for version 2017.06.05_1. > network/slimjet: Updated for version 15.1.1.0. > network/tor: Updated for version 0.3.0.10. > network/tornado: Updated for version 4.5.2. > network/uget: Updated for version 2.0.10. > network/wireshark: Updated for version 2.4.1. > network/yandex-browser-beta: Updated for version 17.7.1.802. > network/yle-dl: Added (Download videos from Yle servers). > office/LibreOffice: Updated for version 5.4.1.2 > office/calibre: Updated for version 3.7.0 > office/extractpdfmark: Added (extract page mode etc from PDF). > office/libreoffice-helppack: Updated for version 5.4.1. > office/libreoffice-langpack: Updated for version 5.4.1. > office/libreoffice: Updated for version 5.4.1. > office/pdfchain: Updated for version 0.4.4.2. > perl/perl-Math-GMPf: Updated for version 0.43. > perl/perl-Sidef: Updated for version 3.03. > python/dulwich: Updated for version 0.18.2. > python/egenix-mx-base: Switch to https. > python/hg-git: Updated for version 0.8.9. > python/python-gattlib: Fixed odd permissions on some files. > python/python-keyutils: Fix dep. > python/python-progress: Added (easy to use progress bars). > python/python-whisper: Fix SlackBuild. > python/python3-tornado: Updated for version 4.5.2. > system/ffproxy: Added (filtering HTTP/HTTPS proxy server). > system/fileschanged: Added (File Alteration Monitor client). > system/fpm2: Switch to https. > system/fwupd: Updated for version 0.9.7. > system/fzf: Updated for version 0.17.0. > system/hfsprogs: Added (hfs+ user space utils). > system/hungrycat: Updated for version 0.4. > system/iucode_tool: Updated for version 2.2. > system/mariadb-plugin-saslauthd: Updated for version 1.2. > system/nagvis: Fixed build. > system/noto-emoji: Updated for version gita4ddd5b. > system/pv: New maintainer. > system/ripgrep: Added (line oriented search tool). > system/secure-delete: Fixed download. > system/wine-staging: Updated for version 2.15. > +--------------------------+ From rshepard at appl-ecosys.com Sat Sep 2 20:40:34 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 2 Sep 2017 13:40:34 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> Message-ID: On Fri, 1 Sep 2017, Erik Hanson wrote: > This sounds like you're trying to run an already built gnucash binary and > getting an error. You're not going to fix this by only rebuilding some > related deps. Erik, No installed gnucash package when trying to build one. > Remove gnucash and ALL related dependencies, along with anything else > you've installed to try and solve this, and start over. Use what's in the > SBo repo, /exactly/ as listed (no webkit2gtk instead of webkitgtk, etc., > don't version bump anything) and you have a shot at getting a working > gnucash package. Did this. The build fails after 6 minutes because: ice-9/boot-9.scm:106:20: In procedure dynamic-link: file: "libgnc-gnome", message: "file not found" Makefile:1162: recipe for target 'qif-import.go' failed Full build log (gzipped) attached. Same failure with gnucash-2.6.17 (all dependencies as in repo). Rich -------------- next part -------------- A non-text attachment was scrubbed... Name: salmo-build.log.gz Type: application/x-gzip Size: 65735 bytes Desc: URL: From dickson.tim at googlemail.com Sat Sep 2 21:45:47 2017 From: dickson.tim at googlemail.com (Tim Dickson) Date: Sat, 2 Sep 2017 22:45:47 +0100 Subject: [Slackbuilds-users] kde_cdemu Message-ID: Hi Ronny (and list), The source location for your kde_cdemu slackbuild is giving a 403 error (forbidden). Do you know of another location for the source for this build? (I can can find source for more recent 0.7.2 version, but it needs kde5, so 0.5.0 version should be fine. Alternatively, if someone on the list has a copy of the 0.5.0 source, maybe it could be put on the sourceforge slackbuilds source repository) thanks, Tim -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Sat Sep 2 21:49:25 2017 From: didier at slint.fr (Didier Spaier) Date: Sat, 2 Sep 2017 23:49:25 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> Message-ID: <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> Rich, Le 02/09/2017 ? 22:40, Rich Shepard a ?crit?: > ? Same failure with gnucash-2.6.17 (all dependencies as in repo). Again, the SlackBuild has not been tested for this version. At least try to build gnucash-2.6.13. As long as you don't have a Slint 14.2 freshly installed from scratch, you are on your own anyway, as already said several times. Best, Didier From rshepard at appl-ecosys.com Sat Sep 2 21:57:12 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 2 Sep 2017 14:57:12 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> Message-ID: On Sat, 2 Sep 2017, Didier Spaier wrote: > At least try to build gnucash-2.6.13. Will do. > As long as you don't have a Slint 14.2 freshly installed from scratch, you > are on your own anyway, as already said several times. Why is there such resistance to resolving issues after upgrades? Rich From didier at slint.fr Sat Sep 2 21:59:52 2017 From: didier at slint.fr (Didier Spaier) Date: Sat, 2 Sep 2017 23:59:52 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> Message-ID: <23a12675-a54a-5c9e-37f9-da31a09ac01a@slint.fr> Le 02/09/2017 ? 23:49, Didier Spaier a ?crit?: > At least try to build gnucash-2.6.13. Well actually you did But you still do not have clean Slackware 14.2, and we can't scan your system to find all the stale files that can get in the way. From rshepard at appl-ecosys.com Sat Sep 2 22:11:05 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 2 Sep 2017 15:11:05 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> Message-ID: On Sat, 2 Sep 2017, Rich Shepard wrote: >> At least try to build gnucash-2.6.13. > > Will do. Actually, that's what I reported in the previous e-mail and for which I attached the gzipped build log. That was the 2.6.13 version from the SBo repository. Rich From didier at slint.fr Sat Sep 2 22:12:44 2017 From: didier at slint.fr (Didier Spaier) Date: Sun, 3 Sep 2017 00:12:44 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> Message-ID: <4775ed06-8b7b-07c7-5bbf-8fd84dfc7860@slint.fr> Le 02/09/2017 ? 23:57, Rich Shepard a ?crit?: > ? Why is there such resistance to resolving issues after upgrades? Because finding the stale file that is causing the issue is like trying to find a needle in a haystack. Because we are eager to send time to help you, but not to waste it. I will return your question: Why is there such resistance to install anew? All in all it would cost you way less time than trying to solve all the issues caused by your upgrade. And we could spend our time more constructively than just repeating the same advice endlessly. From didier at slint.fr Sat Sep 2 22:16:01 2017 From: didier at slint.fr (Didier Spaier) Date: Sun, 3 Sep 2017 00:16:01 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <4775ed06-8b7b-07c7-5bbf-8fd84dfc7860@slint.fr> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> <4775ed06-8b7b-07c7-5bbf-8fd84dfc7860@slint.fr> Message-ID: <0b01c163-4560-a73e-5a79-6b1a0cb7a4c5@slint.fr> Le 03/09/2017 ? 00:12, Didier Spaier a ?crit?: > Because we are eager to send time to help you, but not to waste it. Please read "spend" instead of "send". From rshepard at appl-ecosys.com Sat Sep 2 22:19:19 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 2 Sep 2017 15:19:19 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <23a12675-a54a-5c9e-37f9-da31a09ac01a@slint.fr> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> <23a12675-a54a-5c9e-37f9-da31a09ac01a@slint.fr> Message-ID: On Sat, 2 Sep 2017, Didier Spaier wrote: > But you still do not have clean Slackware 14.2, and we can't scan your > system to find all the stale files that can get in the way. Didier, But I can scan it if I learn what tools to use. There are no libraries in /usr/local/lib/ that duplicate libraries in /usr/lib/ and, as far as I've seen so far, nothing in /usr/local/bin/ that duplicates /usr/bin/. If I copy the results of 'ls /usr/bin/' to a text file and the results of 'ls /usr/local/bin' to another file I can run them through 'diff -y'. There's also another command whose name I keep forgetting that allows comparison of two files and permits presenting lines only in file 1, or only in file 2, or present in both. I wish I could remember its name because it's a very handy tool. If there are other approaches to check for conflicts please educate me so I can remove them all. Thanks, Rich From chris.willing at iinet.net.au Sat Sep 2 22:20:48 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 3 Sep 2017 08:20:48 +1000 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> Message-ID: On 03/09/17 00:33, Andrea Maria Marconi wrote: > Hi all, > > I'm experiencing problems upgrading 4 programs both using sbotools and > building packages in the "standard" way. > > The oldest package I'm not able to upgrade is opencolorio. > > I attach here the last lines of the output. These are coming out from > the command > > sboupgrade -r opencolorio > > If you have any indication it would be much appreciated. > I think this is because you have openimageio already installed in your system. This is an optional package for opencolorio which isn't supported in the SlackBuild because it results in a circular dependency (since openimageio already depends on opencolorio). That's why we don't list openimageio as a dependency. However since openimageio has been detected in your system, the opencolorio build now also needs some or all of whatever packages openimageio depends on. That will include (according to what I've just built in a clean VM) opencv, ffmpeg and libwebp. chris > --------begin included text ----- > > [ 65%] Building CXX object > src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/main.cpp.o > [ 66%] Linking CXX executable ocioconvert > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libavcodec.so.56, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libavformat.so.56, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libavutil.so.54, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libswscale.so.3, needed by > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, > not found (try using -rpath or -rpath-link) > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: > warning: libavresample.so.2, needed by > /usr/lib64/libopencv_videoio.so.3.1, not found (try using -rpath or > -rpath-link) > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_codec_get_id at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_malloc at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avcodec_find_encoder at LIBAVCODEC_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_freep at LIBAVUTIL_54" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "sws_getContext at LIBSWSCALE_3" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avcodec_close at LIBAVCODEC_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avformat_free_context at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_guess_codec at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avformat_write_header at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_sub_q at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_opt_set at LIBAVUTIL_54" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_free at LIBAVUTIL_54" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_seek_frame at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avcodec_flush_buffers at LIBAVCODEC_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avpicture_get_size at LIBAVCODEC_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avcodec_get_context_defaults3 at LIBAVCODEC_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_codec_get_tag at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_frame_free at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_guess_format at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_write_frame at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_free_packet at LIBAVCODEC_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avformat_alloc_context at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avpicture_fill at LIBAVCODEC_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_dict_free at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_write_trailer at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avcodec_open2 at LIBAVCODEC_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avformat_open_input at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_dict_get at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avformat_network_init at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avformat_find_stream_info at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avio_open at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avcodec_decode_video2 at LIBAVCODEC_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_register_all at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "sws_getCachedContext at LIBSWSCALE_3" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avformat_new_stream at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avcodec_encode_video2 at LIBAVCODEC_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_rescale_q at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avformat_get_mov_video_tags at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_lockmgr_register at LIBAVCODEC_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_init_packet at LIBAVCODEC_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_log_set_level at LIBAVUTIL_54" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_read_frame at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avcodec_find_decoder at LIBAVCODEC_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "sws_freeContext at LIBSWSCALE_3" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "sws_scale at LIBSWSCALE_3" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "avformat_close_input at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_dict_set at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avio_close at LIBAVFORMAT_56" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "avformat_get_riff_video_tags at LIBAVFORMAT_56" > /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: > riferimento non definito a "av_frame_alloc at LIBAVUTIL_54" > /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a > "av_reduce at LIBAVUTIL_54" > collect2: error: ld returned 1 exit status > src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/build.make:176: set di > istruzioni per l'obiettivo "src/apps/ocioconvert/ocioconvert" non riuscito > make[2]: *** [src/apps/ocioconvert/ocioconvert] Errore 1 > make[1]: *** [src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all] Errore 2 > CMakeFiles/Makefile2:247: set di istruzioni per l'obiettivo > "src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all" non riuscito > make: *** [all] Errore 2 > Makefile:160: set di istruzioni per l'obiettivo "all" non riuscito > Failures: > ? opencolorio: opencolorio.SlackBuild return non-zero > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From didier at slint.fr Sat Sep 2 22:34:44 2017 From: didier at slint.fr (Didier Spaier) Date: Sun, 3 Sep 2017 00:34:44 +0200 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> <23a12675-a54a-5c9e-37f9-da31a09ac01a@slint.fr> Message-ID: <4f007734-4a1f-48c5-e0e2-c690da82c4bc@slint.fr> Rich, I won't answer any question until you make a fresh installation. Bests regards, Didier From rworkman at slackbuilds.org Sat Sep 2 22:38:58 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Sat, 2 Sep 2017 17:38:58 -0500 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> <23a12675-a54a-5c9e-37f9-da31a09ac01a@slint.fr> Message-ID: <20170902173858.66a0afd4@home.rlworkman.net> On Sat, 2 Sep 2017 15:19:19 -0700 (PDT) Rich Shepard wrote: > On Sat, 2 Sep 2017, Didier Spaier wrote: > > > But you still do not have clean Slackware 14.2, and we can't scan > > your system to find all the stale files that can get in the way. > > Didier, > > But I can scan it if I learn what tools to use. There are no > libraries in /usr/local/lib/ that duplicate libraries in /usr/lib/ > and, as far as I've seen so far, nothing in /usr/local/bin/ that > duplicates /usr/bin/. > > If I copy the results of 'ls /usr/bin/' to a text file and the > results of 'ls /usr/local/bin' to another file I can run them through > 'diff -y'. There's also another command whose name I keep forgetting > that allows comparison of two files and permits presenting lines only > in file 1, or only in file 2, or present in both. I wish I could > remember its name because it's a very handy tool. That's diff(1). > If there are other approaches to check for conflicts please > educate me so I can remove them all. Given the history here, I think the best option is for you to do similar to what (probably) many others here do: Create a virtual machine of each Slackware version you run. Create a snapshot of it using the virtualization platform. Build packages on that virtual machine, put them somewhere else, install them on the other hosts from that location. Revert the virtual machine state to that prior snapshot. As /patches are issued, update the virtual machine, take a new snapshot, repeat process as needed. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Sat Sep 2 22:57:06 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 2 Sep 2017 23:57:06 +0100 Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> Message-ID: > Full build log (gzipped) attached. > > Same failure with gnucash-2.6.17 (all dependencies as in repo). This is a long shot, but have you tried doing 'export MAKEFLAGS=-j1' immediately before the build? Cheers -D. From baildon.research at googlemail.com Sat Sep 2 23:18:57 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 3 Sep 2017 00:18:57 +0100 Subject: [Slackbuilds-users] kde_cdemu In-Reply-To: References: Message-ID: > The source location for your kde_cdemu slackbuild is giving a 403 error > (forbidden). > Do you know of another location for the source for this build? It's at sbosrcarch http://slackware.uk/sbosrcarch/by-name/misc/kde_cdemu/99752-kde_cdemu-0.5.0.tar.bz2 Almost everything is at sbosrcarch -- see http://slackware.uk/sbosrcarch/README Cheers -D. From duncan_roe at optusnet.com.au Sun Sep 3 01:32:39 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 3 Sep 2017 11:32:39 +1000 Subject: [Slackbuilds-users] Updates - 20170902.1 In-Reply-To: References: Message-ID: <20170903013239.GA17437@dimstar.local.net> Hi Willy, libreoffice 5.4.1 is making the dangling symlink /usr/bin/spadmin -> ../../opt/libreoffice5.4/ Looks like spadmin has gone at 5.4, Cheers ... Duncan. On Sat, Sep 02, 2017 at 11:02:23AM +0100, David Spencer wrote: > Hi folks! > > Only 99 commits this week. > > Sat Sep 2 09:29:23 UTC 2017 > academic/gspiceui: Updated for version 1.1.00. > academic/libqalculate: Updated for version 2.0.0 > academic/pulseview: Switch to https. > academic/qalculate-gtk: Updated for version 2.0.0 > academic/sigrok-cli: Switch to https. > audio/guitarix: Updated for version 0.35.6. > audio/kid3: Updated for version 3.5.0. > desktop/fbmenugen: Updated for version 0.80. > desktop/menutray: Updated for version 0.50. > desktop/obbrowser: Updated for version 0.07. > desktop/obmenu-generator: Updated for version 0.80. > desktop/sawfish: Updated for version 1.12.90. > desktop/slackware-xdg-menu: Fixed update-menus problem. > development/asm6809: Fix bad commit d8d8d2be3. > development/cppcms: Updated for version 1.1.1. > development/dmd: Fixed download. > development/jupyter-nbconvert: Updated for version 5.3.0. > development/meson: Updated for version 0.42.0. > development/rust: Updated for version 1.20.0. > development/sassc: Added (C/C++ port of the Sass CSS precompiler). > games/Pyfa: Updated for version 1.31.0. > games/angband: Updated for version 4.1.0. > games/commandergenius: Updated for version 1.9.9.5beta. > games/doomretro: Updated for version 2.5.4. > games/edgar: Updated for version 1.27. > games/freeciv: Updated for version 2.5.9. > games/instead: Updated for version 3.1.2. > games/quake_shareware_data: Switch to https. > games/solarus-quest-editor: Patched to fix guessing the assets dir. > gis/Shapely: Updated for version 1.6.1. > gis/geojson: Updated for version 2.1.0. > graphics/barcode: Added (GNU Barcode). > graphics/dxftoqet: Added (Element DXF Converter). > graphics/opencollada: Updated for version 1.6.59 > graphics/openimageio: Updated for version 1.7.17 > libraries/VTK: Updated for version 8.0.1 > libraries/appstream-glib: Updated for version 0.7.2. > libraries/libiio: Added (Linux Industrial I/O library). > libraries/libmediainfo: Updated for version 0.7.98. > libraries/libnodave: Added (Siemens S7 300/400 PLC library). > libraries/librep: Updated for version 0.92.7. > libraries/libsass: Added (Sass compiler written in C++). > libraries/libserialport: Switch to https. > libraries/libsigrok: Switch to https. > libraries/libsigrokdecode: Switch to https. > libraries/libwacom: Updated for version 0.26. > libraries/libzen: Updated for version 0.4.36. > libraries/ogre: Updated to latest 1.9 commits. > libraries/stfl: Switch to i586. > libraries/unibilium: Updated for version 1.2.1. > misc/gprename: Patched to use DESTDIR. > misc/sigrok-firmware-fx2lafw: Switch to https. > multimedia/mediainfo: Updated for version 0.7.98. > network/2ping: Added (bi-directional ping utility). > network/mrtg: Switch to https. > network/newsbeuter: Apply Podbeuter segfault fix. > network/phpmyadmin: Updated for version 4.7.4. > network/plowshare-modules: Updated for version 952eceb. > network/plowshare: Updated for version 2.1.7. > network/sickrage: Updated for version 2017.06.05_1. > network/slimjet: Updated for version 15.1.1.0. > network/tor: Updated for version 0.3.0.10. > network/tornado: Updated for version 4.5.2. > network/uget: Updated for version 2.0.10. > network/wireshark: Updated for version 2.4.1. > network/yandex-browser-beta: Updated for version 17.7.1.802. > network/yle-dl: Added (Download videos from Yle servers). > office/LibreOffice: Updated for version 5.4.1.2 > office/calibre: Updated for version 3.7.0 > office/extractpdfmark: Added (extract page mode etc from PDF). > office/libreoffice-helppack: Updated for version 5.4.1. > office/libreoffice-langpack: Updated for version 5.4.1. > office/libreoffice: Updated for version 5.4.1. > office/pdfchain: Updated for version 0.4.4.2. > perl/perl-Math-GMPf: Updated for version 0.43. > perl/perl-Sidef: Updated for version 3.03. > python/dulwich: Updated for version 0.18.2. > python/egenix-mx-base: Switch to https. > python/hg-git: Updated for version 0.8.9. > python/python-gattlib: Fixed odd permissions on some files. > python/python-keyutils: Fix dep. > python/python-progress: Added (easy to use progress bars). > python/python-whisper: Fix SlackBuild. > python/python3-tornado: Updated for version 4.5.2. > system/ffproxy: Added (filtering HTTP/HTTPS proxy server). > system/fileschanged: Added (File Alteration Monitor client). > system/fpm2: Switch to https. > system/fwupd: Updated for version 0.9.7. > system/fzf: Updated for version 0.17.0. > system/hfsprogs: Added (hfs+ user space utils). > system/hungrycat: Updated for version 0.4. > system/iucode_tool: Updated for version 2.2. > system/mariadb-plugin-saslauthd: Updated for version 1.2. > system/nagvis: Fixed build. > system/noto-emoji: Updated for version gita4ddd5b. > system/pv: New maintainer. > system/ripgrep: Added (line oriented search tool). > system/secure-delete: Fixed download. > system/wine-staging: Updated for version 2.15. > +--------------------------+ > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html From rshepard at appl-ecosys.com Sun Sep 3 01:38:57 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sat, 2 Sep 2017 18:38:57 -0700 (PDT) Subject: [Slackbuilds-users] Library versions need to be upgraded In-Reply-To: <20170902173858.66a0afd4@home.rlworkman.net> References: <619a9729-bdbb-e9b0-5da8-8e60121dfbdd@slackbuilds.org> <20170901200637.0eb6b191@home.rlworkman.net> <99fdc76e-525a-279c-4ddb-bf81e231c013@slackbuilds.org> <9f59f3ca-3c34-7916-20d0-aa17e75e77d8@slint.fr> <23a12675-a54a-5c9e-37f9-da31a09ac01a@slint.fr> <20170902173858.66a0afd4@home.rlworkman.net> Message-ID: On Sat, 2 Sep 2017, Robby Workman wrote: > That's diff(1). Robby, Yes, diff -y does a good job. I've just gone file-by-file through /usr/local/bin/, /usr/local/include/, /usr/local/lib/, and /usr/local/share/ and removed those also present in the equivalent /usr/ subdirectory. I did find some I missed before (including a 7-year-old libgnomecanvas). There is now only one copy (the latest from 14.2) of files and directories in /usr/. Thanks, Rich From willysr at slackbuilds.org Sun Sep 3 02:30:48 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 Sep 2017 09:30:48 +0700 Subject: [Slackbuilds-users] Updates - 20170902.1 In-Reply-To: <20170903013239.GA17437@dimstar.local.net> References: <20170903013239.GA17437@dimstar.local.net> Message-ID: > libreoffice 5.4.1 is making the dangling symlink /usr/bin/spadmin -> > ../../opt/libreoffice5.4/ > > Looks like spadmin has gone at 5.4, Hi Duncan thanks for noticing that it's now fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From eric.b.pratt at gmail.com Sun Sep 3 02:50:46 2017 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Sat, 2 Sep 2017 19:50:46 -0700 Subject: [Slackbuilds-users] Maintaining perl-Text-CSV_XS Message-ID: The "?perl-Text-CSV_XS" package is about 4 years outdated. I need a couple of features added in later versions. I emailed the maintainer but his address is no longer valid: ?> ** Address not found ** > > Your message wasn't delivered to falu0_0 at fastmail.fm because the address couldn't be found. Check for typos or unnecessary spaces and try again. > > The response from the remote server was: > 550 5.1.1 : Recipient address rejected: User unknown in virtual mailbox table ?? Does he still actively maintain slackbuilds under another address? If not, ?I can take over as maintainer of this package unless someone else wants it.? Eric -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Sep 3 03:13:48 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 Sep 2017 10:13:48 +0700 Subject: [Slackbuilds-users] Maintaining perl-Text-CSV_XS In-Reply-To: References: Message-ID: > The "?perl-Text-CSV_XS" package is about 4 years outdated. I need a couple > of features added in later versions. I emailed the maintainer but his > address is no longer valid: > > ?> ** Address not found ** >> >> Your message wasn't delivered to falu0_0 at fastmail.fm because the address > couldn't be found. Check for typos or unnecessary spaces and try again. >> >> The response from the remote server was: >> 550 5.1.1 : Recipient address rejected: User unknown > in virtual mailbox table > ?? > Does he still actively maintain slackbuilds under another address? If not, > ?I can take over as maintainer of this package unless someone else wants > it.? if the email is no longer valid, feel free to take over -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From am.marconi at gmx.com Sun Sep 3 07:06:59 2017 From: am.marconi at gmx.com (Andrea Maria Marconi) Date: Sun, 3 Sep 2017 09:06:59 +0200 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> Message-ID: <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> Hi Chris and thanks for your feedback. Actually the situation is as you described. I installed opencolorio as it's required by openimageio together with ffmpeg, opencv and libwebp. In turn I needed openimageio for Blender. So all the four packages that you have mentioned are present in my system. Actually opencolorio and openimageio are both stopping during the upgrade process either I use sboupgrade or I try to build packages alone. If there's no way to upgrade I'll leave them as they are. Thanks again. Andrea On 03/09/2017 00:20, Christoph Willing wrote: > On 03/09/17 00:33, Andrea Maria Marconi wrote: >> Hi all, >> >> I'm experiencing problems upgrading 4 programs both using sbotools and >> building packages in the "standard" way. >> >> The oldest package I'm not able to upgrade is opencolorio. >> >> I attach here the last lines of the output. These are coming out from >> the command >> >> sboupgrade -r opencolorio >> >> If you have any indication it would be much appreciated. >> > I think this is because you have openimageio already installed in your > system. This is an optional package for opencolorio which isn't > supported in the SlackBuild because it results in a circular dependency > (since openimageio already depends on opencolorio). That's why we don't > list openimageio as a dependency. However since openimageio has been > detected in your system, the opencolorio build now also needs some or > all of whatever packages openimageio depends on. That will include > (according to what I've just built in a clean VM) opencv, ffmpeg and > libwebp. > > chris > >> --------begin included text ----- >> >> [ 65%] Building CXX object >> src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/main.cpp.o >> [ 66%] Linking CXX executable ocioconvert >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >> warning: libavcodec.so.56, needed by >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >> not found (try using -rpath or -rpath-link) >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >> warning: libavformat.so.56, needed by >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >> not found (try using -rpath or -rpath-link) >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >> warning: libavutil.so.54, needed by >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >> not found (try using -rpath or -rpath-link) >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >> warning: libswscale.so.3, needed by >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >> not found (try using -rpath or -rpath-link) >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >> warning: libavresample.so.2, needed by >> /usr/lib64/libopencv_videoio.so.3.1, not found (try using -rpath or >> -rpath-link) >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_codec_get_id at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_malloc at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avcodec_find_encoder at LIBAVCODEC_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_freep at LIBAVUTIL_54" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "sws_getContext at LIBSWSCALE_3" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avcodec_close at LIBAVCODEC_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avformat_free_context at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_guess_codec at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avformat_write_header at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_sub_q at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_opt_set at LIBAVUTIL_54" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_free at LIBAVUTIL_54" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_seek_frame at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avcodec_flush_buffers at LIBAVCODEC_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avpicture_get_size at LIBAVCODEC_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avcodec_get_context_defaults3 at LIBAVCODEC_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_codec_get_tag at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_frame_free at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_guess_format at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_write_frame at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_free_packet at LIBAVCODEC_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avformat_alloc_context at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avpicture_fill at LIBAVCODEC_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_dict_free at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_write_trailer at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avcodec_open2 at LIBAVCODEC_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avformat_open_input at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_dict_get at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avformat_network_init at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avformat_find_stream_info at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avio_open at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avcodec_decode_video2 at LIBAVCODEC_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_register_all at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "sws_getCachedContext at LIBSWSCALE_3" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avformat_new_stream at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avcodec_encode_video2 at LIBAVCODEC_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_rescale_q at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avformat_get_mov_video_tags at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_lockmgr_register at LIBAVCODEC_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_init_packet at LIBAVCODEC_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_log_set_level at LIBAVUTIL_54" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_read_frame at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avcodec_find_decoder at LIBAVCODEC_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "sws_freeContext at LIBSWSCALE_3" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "sws_scale at LIBSWSCALE_3" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "avformat_close_input at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_dict_set at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avio_close at LIBAVFORMAT_56" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "avformat_get_riff_video_tags at LIBAVFORMAT_56" >> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >> riferimento non definito a "av_frame_alloc at LIBAVUTIL_54" >> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >> "av_reduce at LIBAVUTIL_54" >> collect2: error: ld returned 1 exit status >> src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/build.make:176: set di >> istruzioni per l'obiettivo "src/apps/ocioconvert/ocioconvert" non riuscito >> make[2]: *** [src/apps/ocioconvert/ocioconvert] Errore 1 >> make[1]: *** [src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all] Errore 2 >> CMakeFiles/Makefile2:247: set di istruzioni per l'obiettivo >> "src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all" non riuscito >> make: *** [all] Errore 2 >> Makefile:160: set di istruzioni per l'obiettivo "all" non riuscito >> Failures: >> ? opencolorio: opencolorio.SlackBuild return non-zero >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From duncan_roe at optusnet.com.au Sun Sep 3 07:57:04 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 3 Sep 2017 17:57:04 +1000 Subject: [Slackbuilds-users] pyPdf SlackBuild or can't upgrade sofastats In-Reply-To: References: <20170820032938.GB3396@dimstar.local.net> Message-ID: <20170903075704.GB17437@dimstar.local.net> On Sun, Aug 27, 2017 at 10:01:01AM +0200, 414N wrote: > Hello Duncan, > thanks for your reply and sorry for the HTML-only message, I???ll make > sure to send plaintext versions too. ;-) > While the suggestion of mentioning the usage of |pip2tgz| to obtain > pyPdf in the README of sofastats can indeed work as a quite good > workaround to the issue at hand, I think there are some drawbacks to it: > > * people who use automated tools to install packages (i.e. |sbopkg|) > will build a package that won???t work at runtime, even if all the > other hard-dependencies specified in the |REQUIRES| line are installed > * dependencies specified in the README should only be optional or > recommended ones, not mandatory ones (at least, this is what I > grasped here on SBo) > > I guess the second one clashes with the guidelines here on SBo, but I > don???t know for sure. > If someone knows better, please correct me if I???m wrong > > Cheers > > ??? > > Alan Alberghini > > SBo clone: GitHub > Hi Alan, Sorry for the delay in replying - have had network problems this last week. If pyPdf is only a *runtime* dependency, I believe you don't absolutely *have* to have it as a requirement. But really, the existing package should be renamed. This is not entirely trivial: as well as renaming the directory the maintainer would also have to rename a couple of files therein and edit the SlackBuild, info and slack-desc. The required patches are below. I've cc'd the maintainer (Hi Brent!) in the hope he can submit the new SB and withdraw the old one, Cheers ... Duncan. > On 20/08/2017 05:29, Duncan Roe wrote: > > On Sat, Aug 19, 2017 at 06:06:47PM +0200, 414N wrote: > > > >> I'm working on an updated sofastats SlackBuild but I stumbled upon a > >> dependency issue... > >> It seems like the sofastats package depends since some time on the `pyPdf` > >> python library for managing PDF exports (see the official documentation at > >> http://www.sofastatistics.com/wiki/doku.php?id=help:linux_installation#packages_required_dependencies, > >> although they only report distro-specific package names...). Problem is, > >> that the pyPdf package on SBo is not the original library required for the > >> build, but instead is a ~2011 fork based on that library that has since gone > >> separate ways and was renamed `PyPDF2`. This is also reflected on the module > >> name, as it is installed as PyPDF2 inside > >> /usr/lib64/python2.7/site-packages/PyPDF2/. > >> The full story of the forking is available on the official site of PyPDF2 at > >> https://mstamy2.github.io/PyPDF2/, while the original library is still > >> available at http://pybrary.net/pyPdf/. > >> What I'd like to propose is: > >> > >> - to rename the current pyPdf package to the more proper `PyPDF2` name > >> > >> - to submit (I've already created a SlackBuild) the original unmaintained > >> library as `pyPdf`, so the dependency can be set inside the updated > >> sofastats.info > >> -- > >> Alan Alberghini > > Hi Alan, > > > > Please try to avoid sending HTML-only messages to the list in future. > > > > pyPdf is indexed by PyPI - the Python Package Index > > (https://pypi.python.org/pypi), so pip2tgz will build it. The package ends up > > as pyPdf-1.13-x86_64-1_pip2_SBo.tgz. (PyPDF2 is also listed on PyPI BTW). > > > > Unfortunately you can't put a pip2tgz-built package as a dependency in > > sofastats.info. You would have to mention it in the README as being required. > > That would enable you to get the main SB out the door. > > > > I certainly agree that the existing pyPdf SB should be renamed, > > > > Cheers ... Duncan. --------------------------------- 17:46:36$ diffdir -u /usr/src/slackbuilds/python/pyPdf . Only in .: PyPDF2.SlackBuild Only in .: PyPDF2.info Only in /usr/src/slackbuilds/python/pyPdf: pyPdf.SlackBuild Only in /usr/src/slackbuilds/python/pyPdf: pyPdf.info diff -u /usr/src/slackbuilds/python/pyPdf/slack-desc ./slack-desc --- /usr/src/slackbuilds/python/pyPdf/slack-desc 2017-04-08 09:57:55.000000000 +1000 +++ ./slack-desc 2017-09-03 17:42:07.000000000 +1000 @@ -5,15 +5,15 @@ # You must make exactly 11 lines for the formatting to be correct. It's also # customary to leave one space after the ':' except on otherwise blank lines. - |-----handy-ruler------------------------------------------------------| -pyPdf: pyPdf (Python PDF toolkit) -pyPdf: -pyPdf: A Pure-Python library built as a PDF toolkit. -pyPdf: -pyPdf: -pyPdf: -pyPdf: -pyPdf: -pyPdf: -pyPdf: -pyPdf: + |-----handy-ruler------------------------------------------------------| +PyPDF2: PyPDF2 (Python PDF toolkit) +PyPDF2: +PyPDF2: A Pure-Python library built as a PDF toolkit. +PyPDF2: +PyPDF2: This is a fork of pyPdf, available separately +PyPDF2: +PyPDF2: +PyPDF2: +PyPDF2: +PyPDF2: +PyPDF2: 17:46:38$ diff -u /usr/src/slackbuilds/python/pyPdf/pyPdf.SlackBuild PyPDF2.SlackBuild --- /usr/src/slackbuilds/python/pyPdf/pyPdf.SlackBuild 2017-04-08 09:57:55.000000000 +1000 +++ PyPDF2.SlackBuild 2017-09-03 17:35:11.000000000 +1000 @@ -1,6 +1,6 @@ #!/bin/sh -# Slackware build script for pyPdf. +# Slackware build script for PyPDF2. # Copyright 2009-2011 Marco Bonetti # Copyright 2015-2017 Brenton Earl @@ -23,8 +23,7 @@ # OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF # ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. -PRGNAM=pyPdf -SRCNAM=PyPDF2 +PRGNAM=PyPDF2 VERSION=${VERSION:-1.26.0} BUILD=${BUILD:-1} TAG=${TAG:-_SBo} @@ -64,9 +63,9 @@ rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT cd $TMP -rm -rf $SRCNAM-$VERSION -tar xvf $CWD/$SRCNAM-$VERSION.tar.gz -cd $SRCNAM-$VERSION +rm -rf $PRGNAM-$VERSION +tar xvf $CWD/$PRGNAM-$VERSION.tar.gz +cd $PRGNAM-$VERSION chown -R root:root . find -L . \ \( -perm 777 -o -perm 775 -o -perm 750 -o -perm 711 -o -perm 555 \ 17:50:36$ diff -u /usr/src/slackbuilds/python/pyPdf/pyPdf.info PyPDF2.info --- /usr/src/slackbuilds/python/pyPdf/pyPdf.info 2017-04-08 09:57:55.000000000 +1000 +++ PyPDF2.info 2017-09-03 17:32:36.000000000 +1000 @@ -1,4 +1,4 @@ -PRGNAM="pyPdf" +PRGNAM="PyPDF2" VERSION="1.26.0" HOMEPAGE="https://mstamy2.github.io/PyPDF2/" DOWNLOAD="https://github.com/mstamy2/PyPDF2/archive/1.26.0/PyPDF2-1.26.0.tar.gz" From chris.willing at iinet.net.au Sun Sep 3 08:56:13 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sun, 3 Sep 2017 18:56:13 +1000 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> Message-ID: <238b1a67-f1bf-f13f-424f-3937ab7f3c57@iinet.net.au> On 03/09/17 17:06, Andrea Maria Marconi wrote: > Hi Chris and thanks for your feedback. > > Actually the situation is as you described. I installed opencolorio as > it's required by openimageio together with ffmpeg, opencv and libwebp. > In turn I needed openimageio for Blender. > > So all the four packages that you have mentioned are present in my > system. Actually opencolorio and openimageio are both stopping during > the upgrade process either I use sboupgrade or I try to build packages > alone. > With all those packages installed, opencolorio will build OK (I tried it again this morning). More linking problems like: >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_free_context at LIBAVFORMAT_56" suggest to me that you have upgraded your ffmpeg sometime after you first built opencv. You probably need to rebuild opencv to match your existing ffmpeg. chris > On 03/09/2017 00:20, Christoph Willing wrote: >> On 03/09/17 00:33, Andrea Maria Marconi wrote: >>> Hi all, >>> >>> I'm experiencing problems upgrading 4 programs both using sbotools and >>> building packages in the "standard" way. >>> >>> The oldest package I'm not able to upgrade is opencolorio. >>> >>> I attach here the last lines of the output. These are coming out from >>> the command >>> >>> sboupgrade -r opencolorio >>> >>> If you have any indication it would be much appreciated. >>> >> I think this is because you have openimageio already installed in your >> system. This is an optional package for opencolorio which isn't >> supported in the SlackBuild because it results in a circular dependency >> (since openimageio already depends on opencolorio). That's why we don't >> list openimageio as a dependency. However since openimageio has been >> detected in your system, the opencolorio build now also needs some or >> all of whatever packages openimageio depends on. That will include >> (according to what I've just built in a clean VM) opencv, ffmpeg and >> libwebp. >> >> chris >> >>> --------begin included text ----- >>> >>> [ 65%] Building CXX object >>> src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/main.cpp.o >>> [ 66%] Linking CXX executable ocioconvert >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>> warning: libavcodec.so.56, needed by >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>> not found (try using -rpath or -rpath-link) >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>> warning: libavformat.so.56, needed by >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>> not found (try using -rpath or -rpath-link) >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>> warning: libavutil.so.54, needed by >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>> not found (try using -rpath or -rpath-link) >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>> warning: libswscale.so.3, needed by >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>> not found (try using -rpath or -rpath-link) >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>> warning: libavresample.so.2, needed by >>> /usr/lib64/libopencv_videoio.so.3.1, not found (try using -rpath or >>> -rpath-link) >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_codec_get_id at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_malloc at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avcodec_find_encoder at LIBAVCODEC_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_freep at LIBAVUTIL_54" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "sws_getContext at LIBSWSCALE_3" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avcodec_close at LIBAVCODEC_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_free_context at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_guess_codec at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_write_header at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_sub_q at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_opt_set at LIBAVUTIL_54" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_free at LIBAVUTIL_54" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_seek_frame at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avcodec_flush_buffers at LIBAVCODEC_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avpicture_get_size at LIBAVCODEC_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avcodec_get_context_defaults3 at LIBAVCODEC_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_codec_get_tag at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_frame_free at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_guess_format at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_write_frame at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_free_packet at LIBAVCODEC_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_alloc_context at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avpicture_fill at LIBAVCODEC_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_dict_free at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_write_trailer at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avcodec_open2 at LIBAVCODEC_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avformat_open_input at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_dict_get at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_network_init at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avformat_find_stream_info at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avio_open at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avcodec_decode_video2 at LIBAVCODEC_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_register_all at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "sws_getCachedContext at LIBSWSCALE_3" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_new_stream at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avcodec_encode_video2 at LIBAVCODEC_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_rescale_q at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_get_mov_video_tags at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_lockmgr_register at LIBAVCODEC_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_init_packet at LIBAVCODEC_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_log_set_level at LIBAVUTIL_54" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_read_frame at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avcodec_find_decoder at LIBAVCODEC_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "sws_freeContext at LIBSWSCALE_3" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "sws_scale at LIBSWSCALE_3" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "avformat_close_input at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_dict_set at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avio_close at LIBAVFORMAT_56" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "avformat_get_riff_video_tags at LIBAVFORMAT_56" >>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>> riferimento non definito a "av_frame_alloc at LIBAVUTIL_54" >>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>> "av_reduce at LIBAVUTIL_54" >>> collect2: error: ld returned 1 exit status >>> src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/build.make:176: set di >>> istruzioni per l'obiettivo "src/apps/ocioconvert/ocioconvert" non riuscito >>> make[2]: *** [src/apps/ocioconvert/ocioconvert] Errore 1 >>> make[1]: *** [src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all] Errore 2 >>> CMakeFiles/Makefile2:247: set di istruzioni per l'obiettivo >>> "src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all" non riuscito >>> make: *** [all] Errore 2 >>> Makefile:160: set di istruzioni per l'obiettivo "all" non riuscito >>> Failures: >>> ? opencolorio: opencolorio.SlackBuild return non-zero >>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From andreas.guldstrand at gmail.com Sun Sep 3 12:22:05 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Sun, 3 Sep 2017 14:22:05 +0200 Subject: [Slackbuilds-users] Maintaining perl-Text-CSV_XS In-Reply-To: References: Message-ID: As I'm the maintainer of perl-Text-CSV, I'd like to take maintenance of perl-Text-CSV_XS as well if Eric wouldn't mind. On 3 September 2017 at 05:13, Willy Sudiarto Raharjo wrote: >> The "perl-Text-CSV_XS" package is about 4 years outdated. I need a couple >> of features added in later versions. I emailed the maintainer but his >> address is no longer valid: >> >> > ** Address not found ** >>> >>> Your message wasn't delivered to falu0_0 at fastmail.fm because the address >> couldn't be found. Check for typos or unnecessary spaces and try again. >>> >>> The response from the remote server was: >>> 550 5.1.1 : Recipient address rejected: User unknown >> in virtual mailbox table >> >> Does he still actively maintain slackbuilds under another address? If not, >> I can take over as maintainer of this package unless someone else wants >> it. > > if the email is no longer valid, feel free to take over > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From am.marconi at gmx.com Sun Sep 3 15:40:21 2017 From: am.marconi at gmx.com (Andrea Maria Marconi) Date: Sun, 3 Sep 2017 17:40:21 +0200 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: <238b1a67-f1bf-f13f-424f-3937ab7f3c57@iinet.net.au> References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> <238b1a67-f1bf-f13f-424f-3937ab7f3c57@iinet.net.au> Message-ID: <1bfdc59d-3957-d6b5-179b-5a102dc3a261@gmx.com> Hi Chris, thanks for the help but it doesn't work. I've erased the opencv package with sboremove and reinstalled with sboinstall then I tried to upgrade opencolorio with the ususal sboupgrade -r but it stops again at the same place. It's not of crucial importance for me since I do not use much Blender nowadays it's just irritating that it doesn't update... Thanks anyway Andrea On 03/09/2017 10:56, Christoph Willing wrote: > On 03/09/17 17:06, Andrea Maria Marconi wrote: >> Hi Chris and thanks for your feedback. >> >> Actually the situation is as you described. I installed opencolorio as >> it's required by openimageio together with ffmpeg, opencv and libwebp. >> In turn I needed openimageio for Blender. >> >> So all the four packages that you have mentioned are present in my >> system. Actually opencolorio and openimageio are both stopping during >> the upgrade process either I use sboupgrade or I try to build packages >> alone. >> > With all those packages installed, opencolorio will build OK (I tried it > again this morning). > > More linking problems like: > >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_free_context at LIBAVFORMAT_56" > suggest to me that you have upgraded your ffmpeg sometime after you > first built opencv. You probably need to rebuild opencv to match your > existing ffmpeg. > > chris > > >> On 03/09/2017 00:20, Christoph Willing wrote: >>> On 03/09/17 00:33, Andrea Maria Marconi wrote: >>>> Hi all, >>>> >>>> I'm experiencing problems upgrading 4 programs both using sbotools and >>>> building packages in the "standard" way. >>>> >>>> The oldest package I'm not able to upgrade is opencolorio. >>>> >>>> I attach here the last lines of the output. These are coming out from >>>> the command >>>> >>>> sboupgrade -r opencolorio >>>> >>>> If you have any indication it would be much appreciated. >>>> >>> I think this is because you have openimageio already installed in your >>> system. This is an optional package for opencolorio which isn't >>> supported in the SlackBuild because it results in a circular dependency >>> (since openimageio already depends on opencolorio). That's why we don't >>> list openimageio as a dependency. However since openimageio has been >>> detected in your system, the opencolorio build now also needs some or >>> all of whatever packages openimageio depends on. That will include >>> (according to what I've just built in a clean VM) opencv, ffmpeg and >>> libwebp. >>> >>> chris >>> >>>> --------begin included text ----- >>>> >>>> [ 65%] Building CXX object >>>> src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/main.cpp.o >>>> [ 66%] Linking CXX executable ocioconvert >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>>> warning: libavcodec.so.56, needed by >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>>> not found (try using -rpath or -rpath-link) >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>>> warning: libavformat.so.56, needed by >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>>> not found (try using -rpath or -rpath-link) >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>>> warning: libavutil.so.54, needed by >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>>> not found (try using -rpath or -rpath-link) >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>>> warning: libswscale.so.3, needed by >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so, >>>> not found (try using -rpath or -rpath-link) >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../x86_64-slackware-linux/bin/ld: >>>> warning: libavresample.so.2, needed by >>>> /usr/lib64/libopencv_videoio.so.3.1, not found (try using -rpath or >>>> -rpath-link) >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_codec_get_id at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_malloc at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avcodec_find_encoder at LIBAVCODEC_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_freep at LIBAVUTIL_54" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "sws_getContext at LIBSWSCALE_3" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avcodec_close at LIBAVCODEC_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_free_context at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_guess_codec at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_write_header at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_sub_q at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_opt_set at LIBAVUTIL_54" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_free at LIBAVUTIL_54" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_seek_frame at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avcodec_flush_buffers at LIBAVCODEC_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avpicture_get_size at LIBAVCODEC_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avcodec_get_context_defaults3 at LIBAVCODEC_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_codec_get_tag at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_frame_free at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_guess_format at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_write_frame at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_free_packet at LIBAVCODEC_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_alloc_context at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avpicture_fill at LIBAVCODEC_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_dict_free at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_write_trailer at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avcodec_open2 at LIBAVCODEC_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avformat_open_input at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_dict_get at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_network_init at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avformat_find_stream_info at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avio_open at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avcodec_decode_video2 at LIBAVCODEC_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_register_all at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "sws_getCachedContext at LIBSWSCALE_3" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_new_stream at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avcodec_encode_video2 at LIBAVCODEC_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_rescale_q at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_get_mov_video_tags at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_lockmgr_register at LIBAVCODEC_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_init_packet at LIBAVCODEC_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_log_set_level at LIBAVUTIL_54" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_read_frame at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avcodec_find_decoder at LIBAVCODEC_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "sws_freeContext at LIBSWSCALE_3" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "sws_scale at LIBSWSCALE_3" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "avformat_close_input at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_dict_set at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avio_close at LIBAVFORMAT_56" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "avformat_get_riff_video_tags at LIBAVFORMAT_56" >>>> /usr/lib64/gcc/x86_64-slackware-linux/5.3.0/../../../../lib64/libOpenImageIO.so: >>>> riferimento non definito a "av_frame_alloc at LIBAVUTIL_54" >>>> /usr/lib64/libopencv_videoio.so.3.1: riferimento non definito a >>>> "av_reduce at LIBAVUTIL_54" >>>> collect2: error: ld returned 1 exit status >>>> src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/build.make:176: set di >>>> istruzioni per l'obiettivo "src/apps/ocioconvert/ocioconvert" non riuscito >>>> make[2]: *** [src/apps/ocioconvert/ocioconvert] Errore 1 >>>> make[1]: *** [src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all] Errore 2 >>>> CMakeFiles/Makefile2:247: set di istruzioni per l'obiettivo >>>> "src/apps/ocioconvert/CMakeFiles/ocioconvert.dir/all" non riuscito >>>> make: *** [all] Errore 2 >>>> Makefile:160: set di istruzioni per l'obiettivo "all" non riuscito >>>> Failures: >>>> ? opencolorio: opencolorio.SlackBuild return non-zero >>>> >>>> >>>> _______________________________________________ >>>> SlackBuilds-users mailing list >>>> SlackBuilds-users at slackbuilds.org >>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>>> FAQ - https://slackbuilds.org/faq/ >>>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sun Sep 3 16:12:09 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 Sep 2017 23:12:09 +0700 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: <1bfdc59d-3957-d6b5-179b-5a102dc3a261@gmx.com> References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> <238b1a67-f1bf-f13f-424f-3937ab7f3c57@iinet.net.au> <1bfdc59d-3957-d6b5-179b-5a102dc3a261@gmx.com> Message-ID: <91e29928-624d-3770-bb35-e6d0cbe30de1@slackbuilds.org> > thanks for the help but it doesn't work. > > I've erased the opencv package with sboremove and reinstalled with > sboinstall then I tried to upgrade opencolorio with the ususal > sboupgrade -r but it stops again at the same place. > > It's not of crucial importance for me since I do not use much Blender > nowadays it's just irritating that it doesn't update... please note that opencv and ffmpeg has a circular dependency you might want to try to build them again after both of them are installed on your system. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sun Sep 3 17:23:30 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 3 Sep 2017 10:23:30 -0700 (PDT) Subject: [Slackbuilds-users] Building gnucash-2.6.17 fails: no libpng14.la [FIXED] In-Reply-To: References: Message-ID: On Fri, 1 Sep 2017, Trayan Denev wrote: Trayan, Found and fixed the problem!! Ran ldd on the not-found library (libgnc-gnome) and saw two missing dependent libraries: libicuuc.so.51 => not found libicudata.so.51 => not found These are missing because Slackware-14.2 provides both in version 56. Made soft links from the gnucash-required version to the installed version and the build script completed. Installed it and it's loaded and waiting for me to enter a couple of week's worth of transactions. Thanks very much for all your patient help, Rich -- Richard Shepard, Ph.D. Have Knowledge - Will Travel Applied Ecosystem Services, LLC Troutdale, OR 97060 USA www[dot]appl-ecosys[dot]com Voice: 503-667-4517 Fax: 503-667-8863 From yalhcru at gmail.com Sun Sep 3 17:28:15 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 3 Sep 2017 13:28:15 -0400 Subject: [Slackbuilds-users] PyXML Message-ID: So I was tracking down a build failure in mame, related to a python script... it turned out that the script would fail if PyXML was installed, and worked fine without it. So did a little further digging and discovered that PyXML has been a dead & abandoned project since 2004. As far as mame goes, I found an easy workaround that allows it to build whether PyXML is installed or not... but I'm thinking PyXML should probably go away anyway. Python itself ships with XML support that was originally based on PyXML, but the API has changed some over the years. Some stuff that was written for one will work OK with the other, and some won't... The PyXML sourceforge page is gone, and you can't find PyXML by searching on pypi.python.org (though its homepage is there, if you follow the link from the .info file). Search on google for "PyXML deprecated" and you'll find lots of distros dropping it from their repos... Debian doesn't ship it, for instance. On SBo we have 4 builds that list PyXML as a requirement: audio/soundconverter business/openerp-server network/tribler python/SOAPpy tribler is one of mine, I can confirm it build & runs without PyXML (as well as it ever runs, anyway). soundconverter seems to behave the same way with or without PyXML installed: I can't get it to actually open & convert audio files, and it gives no error message in the UI nor console. Does anyone use this software? There's a SOAPpy (python-soappy) package in Debian, that doesn't depend on PyXML. So it should be possible to get rid of the PyXML dep... openerp-server, I know nothing about, but found a set of install instructions for it that doesn't mention PyXML: https://doc.odoo.com/install/linux/server/ If it turns out that PyXML is really & truly necessary for one of these builds, and we have to keep it... install it to a nonstandard directory, and patch the stuff that uses it to look there. Adding it to sys.path at the top of the python script(s) would be enough. From fernando.lopezjr at gmail.com Sun Sep 3 17:32:59 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 3 Sep 2017 11:32:59 -0600 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: I dont see the need to remove packages. the more packages there are in sbopkg the better even if outdated. I hate when admins remove packages just because "it is not needed by any package" or "outdated" or "it breaks this" or that... just add a note explaining the issue and have the user decide if they will use the package or not but dont erase it for the rest of us. my two cents. On Sun, Sep 3, 2017 at 11:28 AM, B Watson wrote: > So I was tracking down a build failure in mame, related to a python > script... it turned out that the script would fail if PyXML was installed, > and worked fine without it. So did a little further digging and discovered > that PyXML has been a dead & abandoned project since 2004. > > As far as mame goes, I found an easy workaround that allows it to build > whether PyXML is installed or not... but I'm thinking PyXML should > probably go away anyway. > > Python itself ships with XML support that was originally based on PyXML, > but the API has changed some over the years. Some stuff that was written > for one will work OK with the other, and some won't... > > The PyXML sourceforge page is gone, and you can't find PyXML by searching > on pypi.python.org (though its homepage is there, if you follow the link > from the .info file). Search on google for "PyXML deprecated" and you'll > find lots of distros dropping it from their repos... Debian doesn't ship > it, for instance. > > On SBo we have 4 builds that list PyXML as a requirement: > > audio/soundconverter > business/openerp-server > network/tribler > python/SOAPpy > > tribler is one of mine, I can confirm it build & runs without PyXML > (as well as it ever runs, anyway). > > soundconverter seems to behave the same way with or without PyXML > installed: I can't get it to actually open & convert audio files, > and it gives no error message in the UI nor console. Does anyone use > this software? > > There's a SOAPpy (python-soappy) package in Debian, that doesn't depend > on PyXML. So it should be possible to get rid of the PyXML dep... > > openerp-server, I know nothing about, but found a set of install > instructions > for it that doesn't mention PyXML: https://doc.odoo.com/install/ > linux/server/ > > If it turns out that PyXML is really & truly necessary for one of these > builds, and we have to keep it... install it to a nonstandard directory, > and patch the stuff that uses it to look there. Adding it to sys.path > at the top of the python script(s) would be enough. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rworkman at slackbuilds.org Sun Sep 3 17:36:08 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 3 Sep 2017 12:36:08 -0500 Subject: [Slackbuilds-users] Building gnucash-2.6.17 fails: no libpng14.la [FIXED] In-Reply-To: References: Message-ID: <20170903123608.145d7296@home.rlworkman.net> On Sun, 3 Sep 2017 10:23:30 -0700 (PDT) Rich Shepard wrote: > On Fri, 1 Sep 2017, Trayan Denev wrote: > > Trayan, > > Found and fixed the problem!! > > Ran ldd on the not-found library (libgnc-gnome) and saw two missing > dependent libraries: > > libicuuc.so.51 => not found > libicudata.so.51 => not found > > These are missing because Slackware-14.2 provides both in version > 56. Made soft links from the gnucash-required version to the > installed version and the build script completed. You didn't *fix* anything. You papered over it. You're just compounding the real problem here. The fact that libgnc-gnome is still linked to libicuuc.so.51 is the problem. You shouldn't paper over the problem with symlinks. Fix the problem. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sun Sep 3 17:42:07 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 3 Sep 2017 10:42:07 -0700 (PDT) Subject: [Slackbuilds-users] Building gnucash-2.6.17 fails: no libpng14.la [FIXED] In-Reply-To: <20170903123608.145d7296@home.rlworkman.net> References: <20170903123608.145d7296@home.rlworkman.net> Message-ID: On Sun, 3 Sep 2017, Robby Workman wrote: > You didn't *fix* anything. You papered over it. You're just compounding > the real problem here. > > The fact that libgnc-gnome is still linked to libicuuc.so.51 is the > problem. You shouldn't paper over the problem with symlinks. Fix the > problem. Robby, That package is provided by the gnucash source code; all libgnc* libraries are. I've no control over that. Perhaps other distributions still install version 51 of those libraries so it's not an issue for them. Papering works since that's the only thing over which I have control. Discuss the issue with the gnucash devs (developer-to-developer) and perhaps they'll fix that in the next version. Rich From yalhcru at gmail.com Sun Sep 3 17:48:55 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 3 Sep 2017 13:48:55 -0400 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: On 9/3/17, Fernando Lopez wrote: > I dont see the need to remove packages. the more packages there are in > sbopkg the better even if outdated. I hate when admins remove packages just > because "it is not needed by any package" or "outdated" or "it breaks this" > or that... just add a note explaining the issue and have the user decide > if they will use the package or not but dont erase it for the rest of us. > > my two cents. I normally would agree with you. However, PyXML causes actual harm: if it's installed, it causes random Python scripts to break, if they're trying to use the XML library that ships with Python itself. It will create extra *and pointless* work for maintainers. And the functionality of PyXML became part of core Python itself years ago. In other words, it conflicts with a package that's in core Slackware, which is against SBo guidelines. It's installing a 13-year-old outdated version of a library that's already present in Slackware's python package. I'm more familiar with Perl than Python, but this happens all the time: SBo has a Perl module, and in the next release of Slackware, the core perl package starts including that module. Keeping the old one around can cause problems with perl scripts. From fernando.lopezjr at gmail.com Sun Sep 3 17:57:19 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 3 Sep 2017 11:57:19 -0600 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: why does it have inkscape as keyword? On Sun, Sep 3, 2017 at 11:48 AM, B Watson wrote: > On 9/3/17, Fernando Lopez wrote: > > I dont see the need to remove packages. the more packages there are in > > sbopkg the better even if outdated. I hate when admins remove packages > just > > because "it is not needed by any package" or "outdated" or "it breaks > this" > > or that... just add a note explaining the issue and have the user decide > > if they will use the package or not but dont erase it for the rest of us. > > > > my two cents. > > I normally would agree with you. However, PyXML causes actual harm: if > it's installed, it causes random Python scripts to break, if they're > trying to use the XML library that ships with Python itself. It will > create extra *and pointless* work for maintainers. And the functionality > of PyXML became part of core Python itself years ago. > > In other words, it conflicts with a package that's in core Slackware, > which is against SBo guidelines. It's installing a 13-year-old outdated > version of a library that's already present in Slackware's python package. > > I'm more familiar with Perl than Python, but this happens all the time: > SBo has a Perl module, and in the next release of Slackware, the core > perl package starts including that module. Keeping the old one around > can cause problems with perl scripts. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From erik at slackbuilds.org Sun Sep 3 18:15:05 2017 From: erik at slackbuilds.org (Erik Hanson) Date: Sun, 3 Sep 2017 13:15:05 -0500 Subject: [Slackbuilds-users] Building gnucash-2.6.17 fails: no libpng14.la [FIXED] In-Reply-To: References: <20170903123608.145d7296@home.rlworkman.net> Message-ID: On 09/03/2017 12:42 PM, Rich Shepard wrote: > On Sun, 3 Sep 2017, Robby Workman wrote: > >> You didn't *fix* anything. You papered over it. You're just compounding >> the real problem here. >> >> The fact that libgnc-gnome is still linked to libicuuc.so.51 is the >> problem. You shouldn't paper over the problem with symlinks. Fix the >> problem. > > Robby, > > ? That package is provided by the gnucash source code; all libgnc* > libraries > are. I've no control over that. Perhaps other distributions still install > version 51 of those libraries so it's not an issue for them. > > ? Papering works since that's the only thing over which I have control. > Discuss the issue with the gnucash devs (developer-to-developer) and > perhaps > they'll fix that in the next version. On a clean install of 32-bit Slackware 14.2, gnucash builds and correctly links libgnc-gnome.so against libicuuc.so.56 and libicudata.so.56, etc. So the problem is on your end, please do not contact upstream gnucash devs about this. -- Erik -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sun Sep 3 18:22:39 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 3 Sep 2017 11:22:39 -0700 (PDT) Subject: [Slackbuilds-users] Building gnucash-2.6.17 fails: no libpng14.la [FIXED] In-Reply-To: References: <20170903123608.145d7296@home.rlworkman.net> Message-ID: On Sun, 3 Sep 2017, Erik Hanson wrote: > On a clean install of 32-bit Slackware 14.2, gnucash builds and correctly > links libgnc-gnome.so against libicuuc.so.56 and libicudata.so.56, etc. So > the problem is on your end, please do not contact upstream gnucash devs > about this. Erik, OK. Some if the *icu* libraries installed here off the 14.2 distribution disk are version 56, but those two were not. Why this was the case I've no idea. Rich From matteo.bernardini at gmail.com Sun Sep 3 18:35:43 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 3 Sep 2017 20:35:43 +0200 Subject: [Slackbuilds-users] Building gnucash-2.6.17 fails: no libpng14.la [FIXED] In-Reply-To: References: <20170903123608.145d7296@home.rlworkman.net> Message-ID: 2017-09-03 20:22 GMT+02:00 Rich Shepard : > OK. Some if the *icu* libraries installed here off the 14.2 distribution > disk are version 56, but those two were not. Why this was the case I've no > idea. you still have old stuff installed to which gnucash tries to link that links to the old icu, and I haven't the slightest of what it could be. you can install Harald's sbbdep ( https://slackbuilds.org/repository/14.2/system/sbbdep/ ), run it once without arguments (so that it builds its own database) and then run it again like sbbdep --who-needs /usr/lib/libicuuc.so.51 and it should tell what package you have installed that needs the old version of libicu* I have no idea if it supports also stuff installed in /usr/local/ but it's your duty to check this stuff. Matteo From klaatu at member.fsf.org Sun Sep 3 18:42:54 2017 From: klaatu at member.fsf.org (Klaatu) Date: Mon, 04 Sep 2017 06:42:54 +1200 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: <316926F3-41A0-47E1-8A13-68CD4BB4BDC2@member.fsf.org> I don't know, but I can verify that Inkscape works quite well without this package. I use Inkscape every day and have never installed this PyXML package. On 4 September 2017 5:57:19 AM NZST, Fernando Lopez wrote: >why does it have inkscape as keyword? > >On Sun, Sep 3, 2017 at 11:48 AM, B Watson wrote: > >> On 9/3/17, Fernando Lopez wrote: >> > I dont see the need to remove packages. the more packages there are >in >> > sbopkg the better even if outdated. I hate when admins remove >packages >> just >> > because "it is not needed by any package" or "outdated" or "it >breaks >> this" >> > or that... just add a note explaining the issue and have the user >decide >> > if they will use the package or not but dont erase it for the rest >of us. >> > >> > my two cents. >> >> I normally would agree with you. However, PyXML causes actual harm: >if >> it's installed, it causes random Python scripts to break, if they're >> trying to use the XML library that ships with Python itself. It will >> create extra *and pointless* work for maintainers. And the >functionality >> of PyXML became part of core Python itself years ago. >> >> In other words, it conflicts with a package that's in core Slackware, >> which is against SBo guidelines. It's installing a 13-year-old >outdated >> version of a library that's already present in Slackware's python >package. >> >> I'm more familiar with Perl than Python, but this happens all the >time: >> SBo has a Perl module, and in the next release of Slackware, the core >> perl package starts including that module. Keeping the old one around >> can cause problems with perl scripts. >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > > >-- > >------------ >Regards, > Fernando Lopez Jr. -- Klaatu -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Sun Sep 3 18:59:39 2017 From: didier at slint.fr (Didier Spaier) Date: Sun, 3 Sep 2017 20:59:39 +0200 Subject: [Slackbuilds-users] PyXML In-Reply-To: <316926F3-41A0-47E1-8A13-68CD4BB4BDC2@member.fsf.org> References: <316926F3-41A0-47E1-8A13-68CD4BB4BDC2@member.fsf.org> Message-ID: <9bc70c2b-9542-8e29-caf3-27c790d3b8f4@slint.fr> Le 03/09/2017 ? 20:42, Klaatu a ?crit?: > I don't know, but I can verify that Inkscape works quite well without this package. I use Inkscape every day and have never installed this PyXML package. IIRC this is needed only for features accessed from the Help menu entry. At least that's why I needed it. FWIW I have built a full featured inkscape-0.92 (with all optional deps). I attach the configuration summary with the dependencies list. -------------- next part -------------- ------------------------------------------------------------------------ Configuration Summary ------------------------------------------------------------------------ PROJECT_NAME: inkscape INKSCAPE_VERSION: 0.92.2 INKSCAPE_DIST_PREFIX: inkscape-0.92.2 CMAKE_BINARY_DIR: /old/home/didier/Slint/repo/x86_64/slint-testing/source/inkscape/src/inkscape-0.92.2/build CMAKE_INSTALL_PREFIX: /usr PACKAGE_LOCALE_DIR /usr/share/locale CMAKE_SYSTEM_NAME: Linux CMAKE_SYSTEM_VERSION: 4.4.75 CMAKE_SYSTEM_PROCESSOR: x86_64 CMAKE_C_COMPILER: /usr/bin/cc CMAKE_CXX_COMPILER: /usr/bin/c++ CMAKE_BUILD_TYPE: Release ENABLE_LCMS: ON ENABLE_POPPLER: ON ENABLE_POPPLER_CAIRO: ON GMOCK_PRESENT: ON WITH_DBUS: OFF WITH_GNOME_VFS: OFF WITH_GTK3_EXPERIMENTAL: OFF WITH_GTKSPELL: 1 WITH_IMAGE_MAGICK: ON WITH_LIBCDR: ON WITH_LIBVISIO: ON WITH_LIBWPG: ON WITH_NLS: ON WITH_OPENMP: ON WITH_PROFILING: OFF ------------------------------------------------------------------------ didier[/old/home/didier/Slint/repo/x86_64/slint-testing/source/inkscape]$ depfinder -p -f -j4 *txz WARNING: python module elementtree not found. WARNING: python module msvcrt not found. WARNING: python module png not found. WARNING: python module scipy not found. WARNING: python module scour not found. WARNING: python module serial not found. WARNING: python module timing not found. Output: aaa_elflibs|bzip2,aaa_elflibs|gcc,aaa_elflibs|gcc-g++,aaa_elflibs|glib2,aaa_elflibs|libjpeg-turbo, aaa_elflibs|popt,aaa_elflibs|xz,aaa_elflibs|zlib,aspell,atk,atkmm,cairo,cairomm,djvulibre,enchant, expat,fftw,fontconfig,freetype,gc,gcc,gdk-pixbuf2,glib2,glibmm,gsl,gtk+2,gtkmm2,gtkspell,harfbuzz, icu4c,ilmbase,imagemagick,lcms2,libICE,libSM,libX11,libXau,libXcomposite,libXcursor,libXdamage, libXdmcp,libXext,libXfixes,libXi,libXinerama,libXrandr,libXrender,libXt,libXxf86vm,libcdr, libcroco,libdrm,libffi,libpng,librevenge,librsvg,libsigc++,libtiff,libvisio,libwmf,libwpd,libwpg, libxcb,libxml2,libxshmfence,libxslt,mesa,mozilla-nss,numpy,openexr,openjpeg,pango,pangomm,pixman, poppler,potrace,python,python-lxml,python-six,sqlite,util-linux From yalhcru at gmail.com Sun Sep 3 19:10:49 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 3 Sep 2017 15:10:49 -0400 Subject: [Slackbuilds-users] PyXML In-Reply-To: <9bc70c2b-9542-8e29-caf3-27c790d3b8f4@slint.fr> References: <316926F3-41A0-47E1-8A13-68CD4BB4BDC2@member.fsf.org> <9bc70c2b-9542-8e29-caf3-27c790d3b8f4@slint.fr> Message-ID: On 9/3/17, Didier Spaier wrote: > IIRC this is needed only for features accessed from the Help menu entry. > > At least that's why I needed it. > > FWIW I have built a full featured inkscape-0.92 (with all optional deps). > > I attach the configuration summary with the dependencies list. ...from the attached log: aaa_elflibs|bzip2,aaa_elflibs|gcc,aaa_elflibs|gcc-g++,aaa_elflibs|glib2,aaa_elflibs|libjpeg-turbo, aaa_elflibs|popt,aaa_elflibs|xz,aaa_elflibs|zlib,aspell,atk,atkmm,cairo,cairomm,djvulibre,enchant, expat,fftw,fontconfig,freetype,gc,gcc,gdk-pixbuf2,glib2,glibmm,gsl,gtk+2,gtkmm2,gtkspell,harfbuzz, icu4c,ilmbase,imagemagick,lcms2,libICE,libSM,libX11,libXau,libXcomposite,libXcursor,libXdamage, libXdmcp,libXext,libXfixes,libXi,libXinerama,libXrandr,libXrender,libXt,libXxf86vm,libcdr, libcroco,libdrm,libffi,libpng,librevenge,librsvg,libsigc++,libtiff,libvisio,libwmf,libwpd,libwpg, libxcb,libxml2,libxshmfence,libxslt,mesa,mozilla-nss,numpy,openexr,openjpeg,pango,pangomm,pixman, poppler,potrace,python,python-lxml,python-six,sqlite,util-linux ...it mentions libxml2 (Slackware package) and python-lxml (SBo package), but nothing about PyXML. From am.marconi at gmx.com Sun Sep 3 19:14:21 2017 From: am.marconi at gmx.com (Andrea Maria Marconi) Date: Sun, 3 Sep 2017 21:14:21 +0200 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: <91e29928-624d-3770-bb35-e6d0cbe30de1@slackbuilds.org> References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> <238b1a67-f1bf-f13f-424f-3937ab7f3c57@iinet.net.au> <1bfdc59d-3957-d6b5-179b-5a102dc3a261@gmx.com> <91e29928-624d-3770-bb35-e6d0cbe30de1@slackbuilds.org> Message-ID: <7f974104-89cd-e552-2888-70d07ebc9444@gmx.com> Willy, thanks for your suggestion but please understand that I'm? not so experienced. Would you suggest to erase both the packages and install them again in which order? In other words shoudl I try to install first ffmpeg and then opencv and finally opencolorio or should I install again first opencv then ffmpeg and then opencolorio? Thanks again for helping me. Andrea On 03/09/2017 18:12, Willy Sudiarto Raharjo wrote: >> thanks for the help but it doesn't work. >> >> I've erased the opencv package with sboremove and reinstalled with >> sboinstall then I tried to upgrade opencolorio with the ususal >> sboupgrade -r but it stops again at the same place. >> >> It's not of crucial importance for me since I do not use much Blender >> nowadays it's just irritating that it doesn't update... > please note that opencv and ffmpeg has a circular dependency > you might want to try to build them again after both of them are > installed on your system. > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From brent at exitstatusone.com Sun Sep 3 19:18:19 2017 From: brent at exitstatusone.com (Brenton Earl) Date: Sun, 3 Sep 2017 13:18:19 -0600 Subject: [Slackbuilds-users] pyPdf SlackBuild or can't upgrade sofastats In-Reply-To: <20170903075704.GB17437@dimstar.local.net> References: <20170820032938.GB3396@dimstar.local.net> <20170903075704.GB17437@dimstar.local.net> Message-ID: <20170903191819.GA9589@gmail.com> Hello, I've resubmitted pyPdf with all relevant files renamed to PyPDF2. You can see my changes here: https://github.com/BrentonEarl/slackbuilds-14.2/commit/d734040db2b21fdbde2b552c750aa4172730eb7b Let me know if more is required. Sorry for the confusion and the late reply. I've been very busy and have a lot less time to dedicate to SBo maintenance. Regards, Brent On Sun, Sep 03, 2017 at 05:57:04PM +1000, Duncan Roe wrote: > On Sun, Aug 27, 2017 at 10:01:01AM +0200, 414N wrote: > > Hello Duncan, > > thanks for your reply and sorry for the HTML-only message, I???ll make > > sure to send plaintext versions too. ;-) > > While the suggestion of mentioning the usage of |pip2tgz| to obtain > > pyPdf in the README of sofastats can indeed work as a quite good > > workaround to the issue at hand, I think there are some drawbacks to it: > > > > * people who use automated tools to install packages (i.e. |sbopkg|) > > will build a package that won???t work at runtime, even if all the > > other hard-dependencies specified in the |REQUIRES| line are installed > > * dependencies specified in the README should only be optional or > > recommended ones, not mandatory ones (at least, this is what I > > grasped here on SBo) > > > > I guess the second one clashes with the guidelines here on SBo, but I > > don???t know for sure. > > If someone knows better, please correct me if I???m wrong > > > > Cheers > > > > ??? > > > > Alan Alberghini > > > > SBo clone: GitHub > > > Hi Alan, > > Sorry for the delay in replying - have had network problems this last week. > > If pyPdf is only a *runtime* dependency, I believe you don't absolutely *have* > to have it as a requirement. > > But really, the existing package should be renamed. This is not entirely > trivial: as well as renaming the directory the maintainer would also have to > rename a couple of files therein and edit the SlackBuild, info and slack-desc. > > The required patches are below. I've cc'd the maintainer (Hi Brent!) in the > hope he can submit the new SB and withdraw the old one, > > Cheers ... Duncan. > > > On 20/08/2017 05:29, Duncan Roe wrote: > > > On Sat, Aug 19, 2017 at 06:06:47PM +0200, 414N wrote: > > > > > >> I'm working on an updated sofastats SlackBuild but I stumbled upon a > > >> dependency issue... > > >> It seems like the sofastats package depends since some time on the `pyPdf` > > >> python library for managing PDF exports (see the official documentation at > > >> http://www.sofastatistics.com/wiki/doku.php?id=help:linux_installation#packages_required_dependencies, > > >> although they only report distro-specific package names...). Problem is, > > >> that the pyPdf package on SBo is not the original library required for the > > >> build, but instead is a ~2011 fork based on that library that has since gone > > >> separate ways and was renamed `PyPDF2`. This is also reflected on the module > > >> name, as it is installed as PyPDF2 inside > > >> /usr/lib64/python2.7/site-packages/PyPDF2/. > > >> The full story of the forking is available on the official site of PyPDF2 at > > >> https://mstamy2.github.io/PyPDF2/, while the original library is still > > >> available at http://pybrary.net/pyPdf/. > > >> What I'd like to propose is: > > >> > > >> - to rename the current pyPdf package to the more proper `PyPDF2` name > > >> > > >> - to submit (I've already created a SlackBuild) the original unmaintained > > >> library as `pyPdf`, so the dependency can be set inside the updated > > >> sofastats.info > > >> -- > > >> Alan Alberghini > > > Hi Alan, > > > > > > Please try to avoid sending HTML-only messages to the list in future. > > > > > > pyPdf is indexed by PyPI - the Python Package Index > > > (https://pypi.python.org/pypi), so pip2tgz will build it. The package ends up > > > as pyPdf-1.13-x86_64-1_pip2_SBo.tgz. (PyPDF2 is also listed on PyPI BTW). > > > > > > Unfortunately you can't put a pip2tgz-built package as a dependency in > > > sofastats.info. You would have to mention it in the README as being required. > > > That would enable you to get the main SB out the door. > > > > > > I certainly agree that the existing pyPdf SB should be renamed, > > > > > > Cheers ... Duncan. > From didier at slint.fr Sun Sep 3 19:28:26 2017 From: didier at slint.fr (Didier Spaier) Date: Sun, 3 Sep 2017 21:28:26 +0200 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: <316926F3-41A0-47E1-8A13-68CD4BB4BDC2@member.fsf.org> <9bc70c2b-9542-8e29-caf3-27c790d3b8f4@slint.fr> Message-ID: Le 03/09/2017 ? 21:10, B Watson a ?crit?: > On 9/3/17, Didier Spaier wrote: > >> IIRC this is needed only for features accessed from the Help menu entry. >> >> At least that's why I needed it. >> >> FWIW I have built a full featured inkscape-0.92 (with all optional deps). >> >> I attach the configuration summary with the dependencies list. > > ...from the attached log: > > aaa_elflibs|bzip2,aaa_elflibs|gcc,aaa_elflibs|gcc-g++,aaa_elflibs|glib2,aaa_elflibs|libjpeg-turbo, > aaa_elflibs|popt,aaa_elflibs|xz,aaa_elflibs|zlib,aspell,atk,atkmm,cairo,cairomm,djvulibre,enchant, > expat,fftw,fontconfig,freetype,gc,gcc,gdk-pixbuf2,glib2,glibmm,gsl,gtk+2,gtkmm2,gtkspell,harfbuzz, > icu4c,ilmbase,imagemagick,lcms2,libICE,libSM,libX11,libXau,libXcomposite,libXcursor,libXdamage, > libXdmcp,libXext,libXfixes,libXi,libXinerama,libXrandr,libXrender,libXt,libXxf86vm,libcdr, > libcroco,libdrm,libffi,libpng,librevenge,librsvg,libsigc++,libtiff,libvisio,libwmf,libwpd,libwpg, > libxcb,libxml2,libxshmfence,libxslt,mesa,mozilla-nss,numpy,openexr,openjpeg,pango,pangomm,pixman, > poppler,potrace,python,python-lxml,python-six,sqlite,util-linux > > > ...it mentions libxml2 (Slackware package) and python-lxml (SBo package), > but nothing about PyXML. That's right, sorry for the confusion. From rshepard at appl-ecosys.com Sun Sep 3 19:50:01 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 3 Sep 2017 12:50:01 -0700 (PDT) Subject: [Slackbuilds-users] Building gnucash-2.6.17 fails: no libpng14.la [FIXED] In-Reply-To: References: <20170903123608.145d7296@home.rlworkman.net> Message-ID: On Sun, 3 Sep 2017, Matteo Bernardini wrote: > you still have old stuff installed to which gnucash tries to link that > links to the old icu, and I haven't the slightest of what it could be. Matteo, These two libraries are provided by webkitgtk. That was not installed when I tried webkit2gtk. Removed the latter and rebuilt/re-installed webkitgtk-2.4.11 from the SBo repository. Why two of those libraries were version 51 I don't know. It was a clean installation of webkitgtk. > you can install Harald's sbbdep ( > https://slackbuilds.org/repository/14.2/system/sbbdep/ ), run it once > without arguments (so that it builds its own database) and then run it > again like > > sbbdep --who-needs /usr/lib/libicuuc.so.51 > > and it should tell what package you have installed that needs the old > version of libicu* OK. I'll see if there's time tomorrow after finishing my new 64-bit server/workstation with 14.2 on it. > I have no idea if it supports also stuff installed in /usr/local/ but > it's your duty to check this stuff. The only applications on /usr/local/ are not supplied by SBo, such as jpilot, treeline, and grass. Rich From eric.b.pratt at gmail.com Sun Sep 3 19:51:32 2017 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Sun, 3 Sep 2017 12:51:32 -0700 Subject: [Slackbuilds-users] Maintaining perl-Text-CSV_XS In-Reply-To: References: Message-ID: On Sun, Sep 3, 2017 at 5:22 AM, Andreas Guldstrand < andreas.guldstrand at gmail.com> wrote: > As I'm the maintainer of perl-Text-CSV, I'd like to take maintenance > of perl-Text-CSV_XS as well if Eric wouldn't mind. > ?She's all yours. Thanks!? ?Eric? -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Sun Sep 3 20:38:44 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 3 Sep 2017 16:38:44 -0400 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: On 9/3/17, Fernando Lopez wrote: > why does it have inkscape as keyword? PyXML used to be mentioned in inkscape's README as an optional dependency: $ git diff 908e7bce57..e007950e02 graphics/inkscape/README diff --git a/graphics/inkscape/README b/graphics/inkscape/README index 5c22ca6097..a173dbfb25 100644 --- a/graphics/inkscape/README +++ b/graphics/inkscape/README @@ -7,7 +7,9 @@ layers, complex path operations, bitmap tracing, text-on-path, flowed text, direct XML editing, and more. It imports formats such as JPEG, PNG, TIFF, and others and exports PNG as well as multiple vector-based formats. -Inkscape requires libsigc++, glibmm, gtkmm (which requires cairomm), and gc, -all of which are available at SlackBuilds.org. It can also optionally use -PyXML, which will allow you to save projects as .xcf (open with Gimp) to -maintain image layering. +This build script includes a patch that might be needed if you're building +inkscape against a newer version of poppler than what Slackware 12.1 has; +if you need it, uncomment it in the build script. + +Inkscape requires boost, libsigc++, glibmm, gtkmm (which requires cairomm), +and gc, all of which are available at SlackBuilds.org. That commit is from 2011. Would someone (Klaatu?) like to test a modern build of inkscape and confirm that it can save as .xcf? From matteo.bernardini at gmail.com Sun Sep 3 20:48:20 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 3 Sep 2017 22:48:20 +0200 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: 2017-09-03 22:38 GMT+02:00 B Watson : > That commit is from 2011. Would someone (Klaatu?) like to test a modern > build of inkscape and confirm that it can save as .xcf? I can confirm that "save as" has the option to save the files as xcf and that it keeps layer informations. From yalhcru at gmail.com Sun Sep 3 20:57:20 2017 From: yalhcru at gmail.com (B Watson) Date: Sun, 3 Sep 2017 16:57:20 -0400 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: On 9/3/17, Matteo Bernardini wrote: > 2017-09-03 22:38 GMT+02:00 B Watson : >> That commit is from 2011. Would someone (Klaatu?) like to test a modern >> build of inkscape and confirm that it can save as .xcf? > > I can confirm that "save as" has the option to save the files as xcf > and that it keeps layer informations. And that's on a system that doesn't have PyXML installed, correct? From didier at slint.fr Sun Sep 3 22:03:29 2017 From: didier at slint.fr (Didier Spaier) Date: Mon, 4 Sep 2017 00:03:29 +0200 Subject: [Slackbuilds-users] PyXML In-Reply-To: References: Message-ID: <28f67edb-758a-2768-4cb4-b3c73ecd2ec6@slint.fr> Le 03/09/2017 ? 22:57, B Watson a ?crit?: > On 9/3/17, Matteo Bernardini wrote: >> 2017-09-03 22:38 GMT+02:00 B Watson : >>> That commit is from 2011. Would someone (Klaatu?) like to test a modern >>> build of inkscape and confirm that it can save as .xcf? >> >> I can confirm that "save as" has the option to save the files as xcf >> and that it keeps layer informations. > > And that's on a system that doesn't have PyXML installed, correct? True here. I am proposed GIMP XCF avec conservation des calques (*.xcf) I cab then open it in GIMP and indeed I have not PyXML installed ;) This is Inkscape 0.92.2 (5c3e80d, 2017-08-06) Source dir: http://slackware.uk/slint/x86_64/slint-testing/source/inkscape/ From chytraeu at sdf.org Sun Sep 3 23:09:07 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Sun, 3 Sep 2017 18:09:07 -0500 Subject: [Slackbuilds-users] package auditing tool at slackbuilds.org Message-ID: Hello, is there a tool that lists installed packages that are vulnerable against a database of some kind? I thought there was one I had used before, but I am unable to recall the name of it. I'm thinking of something similar to pkg audit of FreeBSD. -- Regards, Donald Cooley From baildon.research at googlemail.com Mon Sep 4 12:59:58 2017 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 4 Sep 2017 13:59:58 +0100 Subject: [Slackbuilds-users] pyPdf SlackBuild or can't upgrade sofastats In-Reply-To: <20170903191819.GA9589@gmail.com> References: <20170820032938.GB3396@dimstar.local.net> <20170903075704.GB17437@dimstar.local.net> <20170903191819.GA9589@gmail.com> Message-ID: > I've resubmitted pyPdf with all relevant files renamed to PyPDF2. You > can see my changes here: Thanks Brent for taking the time to do this for us, PyPDF2 is now added in my branch as a new submission (also I changed office/pdfshuffler to require PyPDF2) >> > >> - to submit (I've already created a SlackBuild) the original unmaintained >> > >> library as `pyPdf`, so the dependency can be set inside the updated >> > >> sofastats.info Ok, this is now ready for you Alan, please submit your pyPdf as if it's an update with a new maintainer Thanks everybody :D -D. From baildon.research at googlemail.com Mon Sep 4 13:25:21 2017 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 4 Sep 2017 14:25:21 +0100 Subject: [Slackbuilds-users] package auditing tool at slackbuilds.org In-Reply-To: References: Message-ID: On 4 September 2017 at 00:09, Donald Cooley wrote: > Hello, > is there a tool that lists installed packages that are vulnerable > against a database of some kind? I thought there was one I had used > before, but I am unable to recall the name of it. I'm thinking of > something similar to pkg audit of FreeBSD. Hi Donald There's cve-check-tool https://slackbuilds.org/repository/14.2/system/cve-check-tool/ of course there are multiple issues to think about -- variations in package naming and version parsing, whether one database is sufficient, whether the vulnerabilities are realistic, whether our builds are actually vulnerable... The database for cve-check-tool is 550 Mb, but the FreeBSD database is 5Mb and the NetBSD database is less than 1.3 Mb. Hmmm. Cheers -D. From chytraeu at sdf.org Mon Sep 4 14:25:06 2017 From: chytraeu at sdf.org (Donald Cooley) Date: Mon, 04 Sep 2017 09:25:06 -0500 Subject: [Slackbuilds-users] package auditing tool at slackbuilds.org In-Reply-To: References: Message-ID: On September 4, 2017 8:25:21 AM CDT, David Spencer wrote: >On 4 September 2017 at 00:09, Donald Cooley wrote: >> Hello, >> is there a tool that lists installed packages that are vulnerable >> against a database of some kind? I thought there was one I had used >> before, but I am unable to recall the name of it. I'm thinking of >> something similar to pkg audit of FreeBSD. > >Hi Donald > >There's cve-check-tool >https://slackbuilds.org/repository/14.2/system/cve-check-tool/ > >of course there are multiple issues to think about -- variations in >package naming and version parsing, whether one database is >sufficient, whether the vulnerabilities are realistic, whether our >builds are actually vulnerable... > >The database for cve-check-tool is 550 Mb, but the FreeBSD database is >5Mb and the NetBSD database is less than 1.3 Mb. Hmmm. > >Cheers >-D. >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ Thanks David. That's what I was thinking of -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From ricardo at palmtx.com.ar Mon Sep 4 19:05:05 2017 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Mon, 4 Sep 2017 16:05:05 -0300 Subject: [Slackbuilds-users] Zeal 0.4.0 slackbuild Message-ID: <201709041605.05907.ricardo@palmtx.com.ar> Hi list, Yesterday I submitted an update for my zeal slackbuild but I forgot to mention that one of the new "featuers" is displaying a small ad in zeal's home page. It's pretty inobtrusive and can be disabled from Edit -> Preferencens -> Content -> Disable advertisement on the welcome page. I don't know if there's a policy aginst that on SBo, if so you may remove this update. If the package can stay, I can mention in the README how to disable the ad. Thanks, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From baildon.research at googlemail.com Mon Sep 4 22:14:03 2017 From: baildon.research at googlemail.com (David Spencer) Date: Mon, 4 Sep 2017 23:14:03 +0100 Subject: [Slackbuilds-users] Zeal 0.4.0 slackbuild In-Reply-To: <201709041605.05907.ricardo@palmtx.com.ar> References: <201709041605.05907.ricardo@palmtx.com.ar> Message-ID: > Hi list, Hi Ricardo, > Yesterday I submitted an update for my zeal slackbuild but I forgot to mention > that one of the new "featuers" is displaying a small ad in zeal's home page. > > It's pretty inobtrusive and can be disabled from Edit -> Preferencens -> > Content -> Disable advertisement on the welcome page. > > I don't know if there's a policy aginst that on SBo, if so you may remove this > update. If the package can stay, I can mention in the README how to disable > the ad. Well, I don't know what other people think -- but our usual question is simply whether the package builds and works ok. And if you think that a tip for the user in README is a good idea, I'm happy to help, so I just updated my branch to include your tip. I hope that's ok with everybody? Cheers -D. From chris.willing at iinet.net.au Mon Sep 4 22:17:31 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Tue, 5 Sep 2017 08:17:31 +1000 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: <7f974104-89cd-e552-2888-70d07ebc9444@gmx.com> References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> <238b1a67-f1bf-f13f-424f-3937ab7f3c57@iinet.net.au> <1bfdc59d-3957-d6b5-179b-5a102dc3a261@gmx.com> <91e29928-624d-3770-bb35-e6d0cbe30de1@slackbuilds.org> <7f974104-89cd-e552-2888-70d07ebc9444@gmx.com> Message-ID: <7f2aad3f-4e08-2a48-5c9f-d3f891f5a5c3@iinet.net.au> The order for the packages mentioned so far would be opencv, libwebp, ffmpeg, opencolorio, openimageio, Blender. Remember that it's the order of building which is important, not just installation. Also there are other packages involved due to various dependencies and options enabled. My basic build/install order for Blender on a full clean system is: python/python-chardet libraries/SDL2 python/python3 python/python-certifi libraries/opencv graphics/opencollada libraries/libwebp python/idna multimedia/ffmpeg development/valgrind python/python-urllib3 graphics/opencolorio development/numpy3 graphics/openimageio python/python-requests libraries/OpenAL audio/jack-audio-connection-kit libraries/freealut graphics/Blender chris On 04/09/17 05:14, Andrea Maria Marconi wrote: > Willy, > > thanks for your suggestion but please understand that I'm? not so > experienced. Would you suggest to erase both the packages and install > them again in which order? > > In other words shoudl I try to install first ffmpeg and then opencv and > finally opencolorio or should I install again first opencv then ffmpeg > and then opencolorio? > > Thanks again for helping me. > > Andrea > > > On 03/09/2017 18:12, Willy Sudiarto Raharjo wrote: >>> thanks for the help but it doesn't work. >>> >>> I've erased the opencv package with sboremove and reinstalled with >>> sboinstall then I tried to upgrade opencolorio with the ususal >>> sboupgrade -r but it stops again at the same place. >>> >>> It's not of crucial importance for me since I do not use much Blender >>> nowadays it's just irritating that it doesn't update... >> please note that opencv and ffmpeg has a circular dependency >> you might want to try to build them again after both of them are >> installed on your system. >> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From ricardo at palmtx.com.ar Mon Sep 4 23:16:26 2017 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Mon, 4 Sep 2017 20:16:26 -0300 Subject: [Slackbuilds-users] Zeal 0.4.0 slackbuild In-Reply-To: References: <201709041605.05907.ricardo@palmtx.com.ar> Message-ID: <201709042016.26671.ricardo@palmtx.com.ar> El Lunes 04/09/2017 a las 19:14, David Spencer escribi?: > > Hi list, > > Hi Ricardo, Hi :) > > Yesterday I submitted an update for my zeal slackbuild but I forgot to > > mention that one of the new "featuers" is displaying a small ad in zeal's > > home page. > > > > It's pretty inobtrusive and can be disabled from Edit -> Preferencens -> > > Content -> Disable advertisement on the welcome page. > > > > I don't know if there's a policy aginst that on SBo, if so you may remove > > this update. If the package can stay, I can mention in the README how to > > disable the ad. > > Well, I don't know what other people think -- but our usual question > is simply whether the package builds and works ok. And if you think > that a tip for the user in README is a good idea, I'm happy to help, Yes, I'm OK with the ad, but I think it'd be nice for people to know upfront that you can disable it. > so I just updated my branch to include your tip. Thank you! > I hope that's ok with everybody? > > Cheers > -D. -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From 1.41421 at gmail.com Tue Sep 5 16:44:42 2017 From: 1.41421 at gmail.com (JCA) Date: Tue, 5 Sep 2017 10:44:42 -0600 Subject: [Slackbuilds-users] Runc failing to build on 14.2 Message-ID: I have just tried to build runc (required for docker) on Slackware64 14.2, using the latest version of go (1.8.3) and libseccomp (2.3.2) available at slackbuilds.org, without success: runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/tty.go runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/update.go runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/utils.go runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/utils_linux.go ln -sfn /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/src/ github.com/opencontainers/runc go build -i -ldflags "-X main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe -X main.version=1.0.0-rc2" -tags "seccomp" -o runc . go build: when using gccgo toolchain, please pass linker flags using -gccgoflags, not -ldflags # _/tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/pkg/gccgo_linux_amd64/ github.com/seccomp/liblibseccomp-golang.a(seccomp.cgo2.o): In function `_cgo_68447050d42b_Cfunc_seccomp_arch_add': /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/src/ github.com/seccomp/libseccomp-golang/seccomp.go:59: undefined reference to `seccomp_arch_add' Changing the Makefile in the runc source code package, as suggested in the diagnostic above, makes things, if anything, worse: /runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/main_unsupported.go ./runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/create.go ./runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/VERSION ln -sfn /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/src/ github.com/opencontainers/runc go build -i -gccgoflags "-X main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe -X main.version=1.0.0-rc2" -tags "seccomp" -o runc . # github.com/Sirupsen/logrus gccgo: error: main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe: No such file or directory gccgo: error: main.version=1.0.0-rc2: No such file or directory gccgo: error: unrecognized command line option '-X' gccgo: error: unrecognized command line option '-X' # github.com/coreos/go-systemd/activation gccgo: error: main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe: No such file or directory gccgo: error: main.version=1.0.0-rc2: No such file or directory gccgo: error: unrecognized command line option '-X' gccgo: error: unrecognized command line option '-X' # github.com/docker/docker/pkg/symlink Any idea as to what is going on, and how to fix this? -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Tue Sep 5 16:53:56 2017 From: 1.41421 at gmail.com (JCA) Date: Tue, 5 Sep 2017 10:53:56 -0600 Subject: [Slackbuilds-users] Runc failing to build on 14.2 In-Reply-To: References: Message-ID: As it happens suspiciously often, I found the problem minutes after I posted my question. The problem is that my PATH variable did not have an entry for the go binary in the google-golang package, and the build system was picking up the one under /usr/bin/, which is the gccgo binary. On Tue, Sep 5, 2017 at 10:44 AM, JCA <1.41421 at gmail.com> wrote: > I have just tried to build runc (required for docker) on Slackware64 14.2, > using the latest version of go (1.8.3) and libseccomp (2.3.2) available at > slackbuilds.org, without success: > > runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/tty.go > runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/update.go > runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/utils.go > runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/utils_linux.go > ln -sfn /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe > /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/ > src/github.com/opencontainers/runc > go build -i -ldflags "-X main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe > -X main.version=1.0.0-rc2" -tags "seccomp" -o runc . > go build: when using gccgo toolchain, please pass linker flags using > -gccgoflags, not -ldflags > # _/tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe > /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/ > pkg/gccgo_linux_amd64/github.com/seccomp/liblibseccomp- > golang.a(seccomp.cgo2.o): In function `_cgo_68447050d42b_Cfunc_ > seccomp_arch_add': > /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/ > src/github.com/seccomp/libseccomp-golang/seccomp.go:59: undefined > reference to `seccomp_arch_add' > > Changing the Makefile in the runc source code package, as suggested in the > diagnostic above, makes things, if anything, worse: > > /runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/main_unsupported.go > ./runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/create.go > ./runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/VERSION > ln -sfn /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe > /tmp/SBo/runc-54296cf40ad8143b62dbcaa1d90e520a2136ddfe/Godeps/_workspace/ > src/github.com/opencontainers/runc > go build -i -gccgoflags "-X main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe > -X main.version=1.0.0-rc2" -tags "seccomp" -o runc . > # github.com/Sirupsen/logrus > gccgo: error: main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe: No > such file or directory > gccgo: error: main.version=1.0.0-rc2: No such file or directory > gccgo: error: unrecognized command line option '-X' > gccgo: error: unrecognized command line option '-X' > # github.com/coreos/go-systemd/activation > gccgo: error: main.gitCommit=54296cf40ad8143b62dbcaa1d90e520a2136ddfe: No > such file or directory > gccgo: error: main.version=1.0.0-rc2: No such file or directory > gccgo: error: unrecognized command line option '-X' > gccgo: error: unrecognized command line option '-X' > # github.com/docker/docker/pkg/symlink > > Any idea as to what is going on, and how to fix this? > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Tue Sep 5 16:58:29 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 5 Sep 2017 18:58:29 +0200 Subject: [Slackbuilds-users] Runc failing to build on 14.2 In-Reply-To: References: Message-ID: 2017-09-05 18:53 GMT+02:00 JCA <1.41421 at gmail.com>: > As it happens suspiciously often, I found the problem minutes after I posted > my question. The problem is that my PATH variable did not have an entry for > the go binary in the google-golang package, and the build system was picking > up the one under /usr/bin/, which is the gccgo binary. after installing google-go-lang you sould logout and relogin to let /etc/profile source also /etc/profile.d/go.sh (or source it manually). From 414N at slacky.it Tue Sep 5 21:17:17 2017 From: 414N at slacky.it (414N) Date: Tue, 5 Sep 2017 23:17:17 +0200 Subject: [Slackbuilds-users] pyPdf SlackBuild or can't upgrade sofastats In-Reply-To: References: <20170820032938.GB3396@dimstar.local.net> <20170903075704.GB17437@dimstar.local.net> <20170903191819.GA9589@gmail.com> Message-ID: <1e99aa29-00eb-7844-bd0e-b0e532e1849c@slacky.it> Done, I just uploaded the tarball archive. Thanks everyone! Alan Alberghini SBo clone: GitHub On 04/09/2017 14:59, David Spencer wrote: >> I've resubmitted pyPdf with all relevant files renamed to PyPDF2. You >> can see my changes here: > Thanks Brent for taking the time to do this for us, > PyPDF2 is now added in my branch as a new submission > (also I changed office/pdfshuffler to require PyPDF2) > >>>>>> - to submit (I've already created a SlackBuild) the original unmaintained >>>>>> library as `pyPdf`, so the dependency can be set inside the updated >>>>>> sofastats.info > Ok, this is now ready for you Alan, please submit your pyPdf as if > it's an update with a new maintainer > > Thanks everybody :D > -D. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://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 davidnchmelik at gmail.com Thu Sep 7 03:46:39 2017 From: davidnchmelik at gmail.com (David Melik) Date: Wed, 6 Sep 2017 20:46:39 -0700 Subject: [Slackbuilds-users] pysetuptools? In-Reply-To: <4bffcb32-e022-da2d-6901-5846c1fd845b@gmail.com> References: <72f95a2a-edc4-c76e-7cae-b4b6a378065a@slacky.it> <4bffcb32-e022-da2d-6901-5846c1fd845b@gmail.com> Message-ID: <31896b10-22f9-e183-ecb7-f726e3f955ab@gmail.com> > On 08/06/2017 10:24 PM, Willy Sudiarto Raharjo wrote: >>> html5lib requires setuptools version 18.5 or above; please upgrade >>> before >>> installing (you have 0.6rc11) >> >> do you have a custom installation of pysetuptools in /usr/local perhaps? > > I don't think so; I have no reason to (I don't even make anything in > Python.)? I searched there, didn't find anything. After saying the above, okay, I found I had some similar/fork package of pysetuptools, that name started with 'd,' and supposedly was going to become better than setuptools, but lately was removed from SBo. I wish the people working on these newer languages would make up their mind. I removed the similar/fork package, then was able to compile everything that hadn't compiled in SBo. From willysr at slackbuilds.org Fri Sep 8 00:29:32 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 8 Sep 2017 07:29:32 +0700 Subject: [Slackbuilds-users] kde_cdemu In-Reply-To: References: Message-ID: <0cdaf19b-06f7-8dea-3404-c717310b8045@slackbuilds.org> > Hi Ronny (and list), > The source location for your kde_cdemu slackbuild is giving a 403 error > (forbidden). > Do you know of another location for the source for this build? > (I can can find source for more recent 0.7.2 version, but it needs kde5, so > 0.5.0 version should be fine. Alternatively, if someone on the list has a > copy of the 0.5.0 source, maybe it could be put on the sourceforge > slackbuilds source repository) > thanks, Tim This should be fixed in my branch now -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From andreas.guldstrand at gmail.com Fri Sep 8 20:29:13 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Fri, 8 Sep 2017 22:29:13 +0200 Subject: [Slackbuilds-users] Maintaining perl-Text-CSV_XS In-Reply-To: References: Message-ID: I've now updated perl-Text-CSV_XS to the latest version, should be included in the next update. https://git.slackbuilds.org/slackbuilds/commit/?id=f95e65c77 / Andreas From eric.b.pratt at gmail.com Fri Sep 8 21:47:06 2017 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Fri, 8 Sep 2017 14:47:06 -0700 Subject: [Slackbuilds-users] Maintaining perl-Text-CSV_XS In-Reply-To: References: Message-ID: Thank you very much! On Fri, Sep 8, 2017 at 1:29 PM, Andreas Guldstrand < andreas.guldstrand at gmail.com> wrote: > I've now updated perl-Text-CSV_XS to the latest version, should be > included in the next update. > > https://git.slackbuilds.org/slackbuilds/commit/?id=f95e65c77 > > / Andreas > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Sep 9 00:16:08 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Sep 2017 07:16:08 +0700 Subject: [Slackbuilds-users] Updates - 20170909.1 Message-ID: <2bcf929c-90ab-ee79-2e3c-5807e933b196@slackbuilds.org> Hi, Patrick has just released an update for mozila-nss which is required by some scripts in our repository, mostly for browsers. Please make sure to upgrade those packages first. Sat Sep 9 00:00:03 UTC 2017 academic/veusz: Updated for version 1.27. accessibility/svkbd: Switch to https. desktop/awesome-extra: Updated for version 2017090101. desktop/dwm: Switch to https. desktop/i3: Updated for version 4.14. desktop/sawfish-extras: Added (Extras for Sawfish WM). desktop/sawfish-session-dialog: Updated for version 20150813. desktop/tint2: Updated for version 15.0. desktop/wmname: Switch to https. development/atom-amd64: Updated for version 1.19.7. development/cppcms: Updated for version 1.1.0. development/dis6502: Added (flow-tracing disassembler for 6502). development/dis: Added (statically tracing 6502 disassembler). development/dmd: Updated for version 2.076.0 development/jupyter-nbconvert: Updated for version 5.3.1. development/mads: Added (cross assembler). development/p4: Updated for version 2017.1.1559660. development/p4d: Updated for version 2017.1.1559660. development/rmac: Added (cross assembler for 6502 and 68000). development/rust: Allow building/bootstrapping for i586. development/sbcl: Updated for version 1.3.21. development/simavr: Updated for version git20170904. development/universal-ctags: Updated for version c310a7c development/xasm: Added (cross assembler targetting the 6502). development/zeal: Updated for version 0.4.0. games/atari800: New homepage. games/dustrac: Updated for version 1.13.0 games/fortune_firefly: Switch to https. games/mame: Updated for version 0.189. games/mednafen: Updated for version 0.9.47. graphics/Shellpic: Fixed tarball handling. graphics/inkscape: Updated for version 0.92.2. graphics/pngcrush: Updated for version 1.8.13. libraries/CoinMP: Fix path. libraries/libinput: Updated for version 1.8.2. libraries/libopenshot: Updated for version 0.1.8 libraries/libtommath: Updated for version 1.0.1. libraries/libu2f-host: Updated for version 1.1.4. libraries/libuv: Updated for version 1.14.1. libraries/pcre2: Updated for version 10.30 libraries/wxSQLite3: Updated for version 3.5.7. misc/kde_cdemu: Update DOWNLOAD. multimedia/openshot: Updated for version 2.4.0 multimedia/opera-ffmpeg-codecs: Updated for version 60.0.3112.90. multimedia/smplayer: Updated for version 17.9.0. network/haproxy: Updated for version 1.7.9. network/ii: Switch to https. network/opera: Updated for version 47.0.2631.80. network/radicale: Updated for version 1.1.6. network/surf: Switch to https. network/syncthing: Updated for version 0.14.37. network/telegram: Updated for version 1.1.23. network/tor-browser: Updated for version 7.0.5. office/MasterPDFEditor: Updated for version 4.3.10. office/aspell6-es: Added (Spanish language files for aspell). office/libreoffice: Remove spadmin symlink. office/pdfshuffler: Updated dep (pyPdf is renamed PyPDF2). perl/perl-AnyEvent: Updated for version 7.14. perl/perl-Date-Manip: Updated for version 6.60. perl/perl-File-Which: Updated for version 1.22. perl/perl-Mojolicious: Updated for version 7.45. perl/perl-Text-CSV_XS: Updated for version 1.31 + new maintainer. python/PyPDF2: Added (Python PDF toolkit). python/psutil: Updated for version 5.3.0 python/pyPdf: Updated for version 1.13 + new maintainer. python/python-requests: Updated for version 2.18.4. system/GentiumPlus: Switch to https. system/Iosevka: Updated for version 1.13.3. system/dateutils: Updated for version 0.4.2. system/exa: Added (replacement for 'ls' written in Rust). system/exomizer: Added (compression for low-resource systems). system/google-fonts: Added (complete collection from Google Fonts). system/kbfs: Updated for version 1.0.29_20170901160109. system/keybase: Updated for version 1.0.29. system/letsencrypt: Updated for version 0.18.0. system/lynis: Updated for version 2.5.5. system/pgbadger: Updated for version 9.2. system/pucrunch: Added (Hybrid Compressor). system/redis: Updated for version 4.0.1. system/rndaddentropy: Added (Small wrapper around RNDADDENTROPY). system/sandy: Switch to https. system/st: Switch to https. system/suckless-tools: Switch to https. system/tabbed: Switch to https. system/vagrant: Updated for version 2.0.0. system/yash: Move binary to /bin. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From am.marconi at gmx.com Mon Sep 11 16:41:17 2017 From: am.marconi at gmx.com (Andrea Maria Marconi) Date: Mon, 11 Sep 2017 18:41:17 +0200 Subject: [Slackbuilds-users] Problems with upgrades: opencolorio In-Reply-To: <7f2aad3f-4e08-2a48-5c9f-d3f891f5a5c3@iinet.net.au> References: <5ea58b48-dbee-7807-3865-27ea110b1c2e@gmx.com> <27ece274-57f4-479f-83ba-3d571b80880b@gmx.com> <238b1a67-f1bf-f13f-424f-3937ab7f3c57@iinet.net.au> <1bfdc59d-3957-d6b5-179b-5a102dc3a261@gmx.com> <91e29928-624d-3770-bb35-e6d0cbe30de1@slackbuilds.org> <7f974104-89cd-e552-2888-70d07ebc9444@gmx.com> <7f2aad3f-4e08-2a48-5c9f-d3f891f5a5c3@iinet.net.au> Message-ID: Thanks Chirs. Finally worked in this way. I'm happy with all updated. Andrea On 05/09/2017 00:17, Christoph Willing wrote: > The order for the packages mentioned so far would be > opencv, libwebp, ffmpeg, opencolorio, openimageio, Blender. > > Remember that it's the order of building which is important, not just > installation. Also there are other packages involved due to various > dependencies and options enabled. My basic build/install order for > Blender on a full clean system is: > > python/python-chardet > libraries/SDL2 > python/python3 > python/python-certifi > libraries/opencv > graphics/opencollada > libraries/libwebp > python/idna > multimedia/ffmpeg > development/valgrind > python/python-urllib3 > graphics/opencolorio > development/numpy3 > graphics/openimageio > python/python-requests > libraries/OpenAL > audio/jack-audio-connection-kit > libraries/freealut > graphics/Blender > > > chris > > > On 04/09/17 05:14, Andrea Maria Marconi wrote: >> Willy, >> >> thanks for your suggestion but please understand that I'm? not so >> experienced. Would you suggest to erase both the packages and install >> them again in which order? >> >> In other words shoudl I try to install first ffmpeg and then opencv and >> finally opencolorio or should I install again first opencv then ffmpeg >> and then opencolorio? >> >> Thanks again for helping me. >> >> Andrea >> >> >> On 03/09/2017 18:12, Willy Sudiarto Raharjo wrote: >>>> thanks for the help but it doesn't work. >>>> >>>> I've erased the opencv package with sboremove and reinstalled with >>>> sboinstall then I tried to upgrade opencolorio with the ususal >>>> sboupgrade -r but it stops again at the same place. >>>> >>>> It's not of crucial importance for me since I do not use much Blender >>>> nowadays it's just irritating that it doesn't update... >>> please note that opencv and ffmpeg has a circular dependency >>> you might want to try to build them again after both of them are >>> installed on your system. >>> >>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ewfalor at gmail.com Tue Sep 12 06:14:47 2017 From: ewfalor at gmail.com (Erik Falor) Date: Tue, 12 Sep 2017 00:14:47 -0600 Subject: [Slackbuilds-users] slackbuilds.org site down? Message-ID: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> To whom it may concern: I'm trying to connect to the slackbuilds.org website but my connection times out. http://www.isitdownrightnow.com/slackbuilds.org.html agrees with me that the site is down. Thanks, -- Erik Falor Registered Linux User #445632 http://unnovative.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: not available URL: From rworkman at slackbuilds.org Tue Sep 12 06:31:44 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 12 Sep 2017 01:31:44 -0500 Subject: [Slackbuilds-users] slackbuilds.org site down? In-Reply-To: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> References: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> Message-ID: <20170912013144.2d0705b7@home.rlworkman.net> On Tue, 12 Sep 2017 00:14:47 -0600 Erik Falor wrote: > To whom it may concern: > > I'm trying to connect to the slackbuilds.org website but my connection > times out. > > http://www.isitdownrightnow.com/slackbuilds.org.html agrees with me > that the site is down. Yes, it is down. The Onyxlight datacenter is in Orlando, Florida (USA), which was affected by Hurricane Irma. None of the staff there are currently reachable, but last we heard, they and the DC are okay and have emergency power available. Most likely their uplinks to the net are down. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Tue Sep 12 17:31:25 2017 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 12 Sep 2017 10:31:25 -0700 Subject: [Slackbuilds-users] slackbuilds.org site down? In-Reply-To: <20170912013144.2d0705b7@home.rlworkman.net> References: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> <20170912013144.2d0705b7@home.rlworkman.net> Message-ID: <2df2b553-780d-7df9-668b-fe7fa9c817a3@gmail.com> On 09/11/2017 11:31 PM, Robby Workman wrote: > On Tue, 12 Sep 2017 00:14:47 -0600 > Erik Falor wrote: > >> To whom it may concern: >> >> I'm trying to connect to the slackbuilds.org website but my connection >> times out. >> >> http://www.isitdownrightnow.com/slackbuilds.org.html agrees with me >> that the site is down. > > > Yes, it is down. > > The Onyxlight datacenter is in Orlando, Florida (USA), which was > affected by Hurricane Irma. None of the staff there are currently > reachable, but last we heard, they and the DC are okay and have > emergency power available. Most likely their uplinks to the net > are down. > > -RW > > Good to hear they are ok. I've been through a few hurricanes back in Sc and FL, including Andrew (that's one reason I moved to the western states) and know the grief, both physical and emotional, they can cause. We can FL etc a bit of time to dig out from under Nature's wrath. Let's hope Jose keeps wandering around aimlessly in the Atlantic.... -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 fernando.lopezjr at gmail.com Wed Sep 13 00:26:52 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Tue, 12 Sep 2017 18:26:52 -0600 Subject: [Slackbuilds-users] slackbuilds.org site down? In-Reply-To: <2df2b553-780d-7df9-668b-fe7fa9c817a3@gmail.com> References: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> <20170912013144.2d0705b7@home.rlworkman.net> <2df2b553-780d-7df9-668b-fe7fa9c817a3@gmail.com> Message-ID: so, now what? :'( On Sep 12, 2017 11:31 AM, "King Beowulf" wrote: > On 09/11/2017 11:31 PM, Robby Workman wrote: > > On Tue, 12 Sep 2017 00:14:47 -0600 > > Erik Falor wrote: > > > >> To whom it may concern: > >> > >> I'm trying to connect to the slackbuilds.org website but my connection > >> times out. > >> > >> http://www.isitdownrightnow.com/slackbuilds.org.html agrees with me > >> that the site is down. > > > > > > Yes, it is down. > > > > The Onyxlight datacenter is in Orlando, Florida (USA), which was > > affected by Hurricane Irma. None of the staff there are currently > > reachable, but last we heard, they and the DC are okay and have > > emergency power available. Most likely their uplinks to the net > > are down. > > > > -RW > > > > > > Good to hear they are ok. I've been through a few hurricanes back in Sc > and FL, including Andrew (that's one reason I moved to the western > states) and know the grief, both physical and emotional, they can cause. > We can FL etc a bit of time to dig out from under Nature's wrath. > > Let's hope Jose keeps wandering around aimlessly in the Atlantic.... > > -Ed > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Sep 13 01:06:02 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 13 Sep 2017 08:06:02 +0700 Subject: [Slackbuilds-users] slackbuilds.org site down? In-Reply-To: References: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> <20170912013144.2d0705b7@home.rlworkman.net> <2df2b553-780d-7df9-668b-fe7fa9c817a3@gmail.com> Message-ID: <99c9aa75-5717-3ecd-dc81-9a1c9c00ea65@slackbuilds.org> > so, now what? :'( We wait until the situation is back to normal This can be considered as a force majeur -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kd5zex at gmail.com Wed Sep 13 02:18:43 2017 From: kd5zex at gmail.com (Alan Dingeldein) Date: Wed, 13 Sep 2017 02:18:43 +0000 Subject: [Slackbuilds-users] slackbuilds.org site down? In-Reply-To: <99c9aa75-5717-3ecd-dc81-9a1c9c00ea65@slackbuilds.org> References: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> <20170912013144.2d0705b7@home.rlworkman.net> <2df2b553-780d-7df9-668b-fe7fa9c817a3@gmail.com> <99c9aa75-5717-3ecd-dc81-9a1c9c00ea65@slackbuilds.org> Message-ID: > We wait until the situation is back to normal It seems to be up and running for me. --Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Sep 13 02:43:54 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 13 Sep 2017 09:43:54 +0700 Subject: [Slackbuilds-users] slackbuilds.org site down? In-Reply-To: References: <20170912061447.tzseqoj5n6zsqctq@viking2.falor> <20170912013144.2d0705b7@home.rlworkman.net> <2df2b553-780d-7df9-668b-fe7fa9c817a3@gmail.com> <99c9aa75-5717-3ecd-dc81-9a1c9c00ea65@slackbuilds.org> Message-ID: >> We wait until the situation is back to normal > > It seems to be up and running for me. Yes, it appears so i have just pushed an update to my branch as well -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Wed Sep 13 10:40:05 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 13 Sep 2017 11:40:05 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency Message-ID: I know SBo and Slackware doesn't have a system in place to track dependencies - and most of the time that suits me just fine. However, on occasion, I stumble over a piece of SBo software installed on my machine - such as a library, and I would like to know why is it there - which package needs it. I was thinking that, if when using the search field on SBo website, it would also search through the .info and README files of packages, I could easily get a list of packages which depend on or use the library - and spot if one of them is something that I use or have installed. It would be crude, but I think it would work. From yth at ythogtha.org Wed Sep 13 11:56:56 2017 From: yth at ythogtha.org (Ythogtha) Date: Wed, 13 Sep 2017 13:56:56 +0200 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: Message-ID: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> If you have a git clone of the SBo repository, you could go there and use this kind of command line : -> Get all SBo packages requiredby a specified package, here is wxGTK3 : grep -E "REQUIRE.*wxGTK3" */*/*.info | cut -d. -f1 | rev | cut -d / -f1 | rev -> Get all the ones installed on your system : for pkg in $(grep -E "REQUIRE.*wxGTK3" */*/*.info | cut -d. -f1 | rev | \ cut -d / -f1 | rev); \ do ls /var/log/packages/$pkg-*SBo; done 2>/dev/null /var/log/packages/audacity-2.1.3-x86_64-2SBo /var/log/packages/codelite-8.1-x86_64-1SBo /var/log/packages/filezilla-3.27.1-x86_64-1SBo -> Get only the names by adding at the end of the previous one : | rev | cut -d- -f4 | cut -d/ -f1 | rev It'll show : audacity codelite filezilla Put that in a script, and there you are :) Yth. > I know SBo and Slackware doesn't have a system in place to track > dependencies - and most of the time that suits me just fine. However, on > occasion, I stumble over a piece of SBo software installed on my machine > - such as a library, and I would like to know why is it there - which > package needs it. I was thinking that, if when using the search field on > SBo website, it would also search through the .info and README files of > packages, I could easily get a list of packages which depend on or use > the library - and spot if one of them is something that I use or have > installed. It would be crude, but I think it would work. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -- Arnaud From gerardo.zamudio at linux.com Wed Sep 13 12:26:09 2017 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 13 Sep 2017 07:26:09 -0500 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: Message-ID: On 09/13/2017 05:40 AM, Sebastian Arcus wrote: > I know SBo and Slackware doesn't have a system in place to track > dependencies - and most of the time that suits me just fine. However, on > occasion, I stumble over a piece of SBo software installed on my machine > - such as a library, and I would like to know why is it there - which > package needs it. I was thinking that, if when using the search field on > SBo website, it would also search through the .info and README files of > packages, I could easily get a list of packages which depend on or use > the library - and spot if one of them is something that I use or have > installed. It would be crude, but I think it would work. In addition, I think we should add a PROVIDES file or something that has the output of /var/log/packages/$PKG. That way if you get an error with a program that 'libjli.so' is not found and you search SBo, you'll find the 'jdk' package provides this. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Sep 13 12:35:16 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 13 Sep 2017 19:35:16 +0700 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: Message-ID: <5e1034ea-4c64-4628-92b0-9069f8cc32a0@slackbuilds.org> > In addition, I think we should add a PROVIDES file or something that has > the output of /var/log/packages/$PKG. That way if you get an error with > a program that 'libjli.so' is not found and you search SBo, you'll find > the 'jdk' package provides this. Please note that we don't provides binary packages like ARCH Linux. We only provide scripts to build a source into a package. Another thing to consider is that the resulting files may be different from one to another due to optional dependencies installed on each machines. It would be a nightmare for maintainer to track all files for each combination of optional dependencies -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Wed Sep 13 12:51:58 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 13 Sep 2017 13:51:58 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> Message-ID: On 13/09/17 12:56, Ythogtha wrote: > If you have a git clone of the SBo repository, you could go there and use this > kind of command line : Thank you for the suggestion. At the moment I don't have a git clone of SBo - and I was hoping there is an easier way to search for a package than setting up a git repository :-) From gerardo.zamudio at linux.com Wed Sep 13 12:52:36 2017 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Wed, 13 Sep 2017 07:52:36 -0500 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <5e1034ea-4c64-4628-92b0-9069f8cc32a0@slackbuilds.org> References: <5e1034ea-4c64-4628-92b0-9069f8cc32a0@slackbuilds.org> Message-ID: On 09/13/2017 07:35 AM, Willy Sudiarto Raharjo wrote: > > Please note that we don't provides binary packages like ARCH Linux. We > only provide scripts to build a source into a package. What's wrong with a file that lists the binaries the script will generate? > Another thing to consider is that the resulting files may be different > from one to another due to optional dependencies installed on each > machines. It would be a nightmare for maintainer to track all files for > each combination of optional dependencies > Why should the file include *optional* dependencies and build parameters? The SBo scripts are supposed to be tested in a clean, full install of Slackware. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Wed Sep 13 12:58:24 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Wed, 13 Sep 2017 12:58:24 +0000 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: Message-ID: If you use the sboui frontend for sbopkg and sbotools, it has a function to show "inverse dependencies" -- every SBo package installed on your system that depends on another one that you choose. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Wed Sep 13 13:31:25 2017 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 13 Sep 2017 13:31:25 +0000 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <5e1034ea-4c64-4628-92b0-9069f8cc32a0@slackbuilds.org> Message-ID: On Wed, Sep 13, 2017, 8:53 AM Gerardo Zamudio wrote: > > > On 09/13/2017 07:35 AM, Willy Sudiarto Raharjo wrote: > > > > Please note that we don't provides binary packages like ARCH Linux. We > > only provide scripts to build a source into a package. > > What's wrong with a file that lists the binaries the script will generate? > > > Another thing to consider is that the resulting files may be different > > from one to another due to optional dependencies installed on each > > machines. It would be a nightmare for maintainer to track all files for > > each combination of optional dependencies > > > > Why should the file include *optional* dependencies and build > parameters? The SBo scripts are supposed to be tested in a clean, full > install of Slackware. > Why should SBo, which doesn't provide binary packages, provide a listing of what is in a binary package? > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Wed Sep 13 13:41:39 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 13 Sep 2017 23:41:39 +1000 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> Message-ID: <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> On 09/13/2017 10:51 PM, Sebastian Arcus wrote: > Thank you for the suggestion. At the moment I don't have a git clone of > SBo - and I was hoping there is an easier way to search for a package > than setting up a git repository :-) If you use sbotools or sbopkg wouldn't you already have that though? Not sure where sbopkg puts it, but sbotools has it in /usr/sbo/repo -- Dave From willysr at slackbuilds.org Wed Sep 13 13:59:02 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 13 Sep 2017 20:59:02 +0700 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <5e1034ea-4c64-4628-92b0-9069f8cc32a0@slackbuilds.org> Message-ID: > What's wrong with a file that lists the binaries the script will generate? you can have them by looking at /var/log/packages/ >> Another thing to consider is that the resulting files may be different >> from one to another due to optional dependencies installed on each >> machines. It would be a nightmare for maintainer to track all files for >> each combination of optional dependencies >> > > Why should the file include *optional* dependencies and build > parameters? The SBo scripts are supposed to be tested in a clean, full > install of Slackware. Because some package can have different output based on the optional packages available on a system. Take an example of ffmpeg -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Wed Sep 13 14:29:47 2017 From: didier at slint.fr (Didier Spaier) Date: Wed, 13 Sep 2017 16:29:47 +0200 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: Message-ID: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> Le 13/09/2017 ? 12:40, Sebastian Arcus a ?crit : > I know SBo and Slackware doesn't have a system in place to track > dependencies - and most of the time that suits me just fine. However, > on occasion, I stumble over a piece of SBo software installed on my > machine - such as a library, and I would like to know why is it there > - which package needs it. I was thinking that, if when using the > search field on SBo website, it would also search through the .info > and README files of packages, I could easily get a list of packages > which depend on or use the library - and spot if one of them is > something that I use or have installed. It would be crude, but I think > it would work. Why bother? Just leave this package alone, or if you are really curious, remove it and see what happens. Also, if you upgrade a package, it is possible that it doesn't need a dependency any more. Furthermore, as others have said, you would need to check the optional dependencies. In my opinion the gain in disk space removing a package is not often worth the time you will spend to find out if you can safely remove it, unless you always keep notes of why you installed a package, but even then, you could install another package that needs it later, without paying attention. This doesn't apply to leaf packages, of course. From didier at slint.fr Wed Sep 13 14:42:52 2017 From: didier at slint.fr (Didier Spaier) Date: Wed, 13 Sep 2017 16:42:52 +0200 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> References: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> Message-ID: Le 13/09/2017 ? 16:29, Didier Spaier a ?crit : > Le 13/09/2017 ? 12:40, Sebastian Arcus a ?crit : >> I know SBo and Slackware doesn't have a system in place to track >> dependencies - and most of the time that suits me just fine. However, >> on occasion, I stumble over a piece of SBo software installed on my >> machine - such as a library, and I would like to know why is it there >> - which package needs it. I was thinking that, if when using the >> search field on SBo website, it would also search through the .info >> and README files of packages, I could easily get a list of packages >> which depend on or use the library - and spot if one of them is >> something that I use or have installed. It would be crude, but I think >> it would work. > > Why bother? Just leave this package alone, or if you are really curious, > remove it and see what happens. > > Also, if you upgrade a package, it is possible that it doesn't need a > dependency any more. > > Furthermore, as others have said, you would need to check the optional > dependencies. > > In my opinion the gain in disk space removing a package is not often > worth the time you will spend to find out if you can safely remove it, > unless you always keep notes of why you installed a package, but even > then, you could install another package that needs it later, without > paying attention. > > This doesn't apply to leaf packages, of course. I forgot: but if you remove a package you can easily spot some deps with 'ls -ltr /var/log/packages' as they were installed just before. Then, you can probably safely remove the deps *if* recently installed. From baildon.research at googlemail.com Wed Sep 13 15:06:54 2017 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 13 Sep 2017 16:06:54 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> Message-ID: Chris Willing's tool hoorex will find "inverse dependencies" of packages. https://github.com/cwilling/hoorex One other idea for finding why you installed a library -- you can list the files in /var/log/packages sorted by time (ls -lt) which will show you the other packages that were installed immediately afterwards. Twenty years ago I wrote this kind of thing in a little book. Ten years ago I used dokuwiki. Now I just never uninstall them. There is no official test build system that would have a full listing of files. Unofficially, I build almost every package from time to time. A list of files (depending on random options) in almost every package is 325 Mb. I'm not sure I would want to put them unofficially on a website somewhere if each query will grep 325Mb of data. (And also I hate elasticsearch.) Cheers -D. From s.arcus at open-t.co.uk Wed Sep 13 16:06:45 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 13 Sep 2017 17:06:45 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> Message-ID: <607e8c49-c06f-8645-37fb-41f1f3b3d249@open-t.co.uk> On 13/09/17 14:41, David O'Shaughnessy wrote: > On 09/13/2017 10:51 PM, Sebastian Arcus wrote: >> Thank you for the suggestion. At the moment I don't have a git clone of >> SBo - and I was hoping there is an easier way to search for a package >> than setting up a git repository :-) > > If you use sbotools or sbopkg wouldn't you already have that though? Not > sure where sbopkg puts it, but sbotools has it in /usr/sbo/repo Good call - I didn't think of that. I use sbotools. I suppose I could grep through /usr/sbo/repo for references to the package I am interested in. From s.arcus at open-t.co.uk Wed Sep 13 16:12:36 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 13 Sep 2017 17:12:36 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> References: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> Message-ID: <74078fd2-fd1d-3be1-7549-3dbdfc2f9e05@open-t.co.uk> On 13/09/17 15:29, Didier Spaier wrote: > Le 13/09/2017 ? 12:40, Sebastian Arcus a ?crit : >> I know SBo and Slackware doesn't have a system in place to track >> dependencies - and most of the time that suits me just fine. However, >> on occasion, I stumble over a piece of SBo software installed on my >> machine - such as a library, and I would like to know why is it there >> - which package needs it. I was thinking that, if when using the >> search field on SBo website, it would also search through the .info >> and README files of packages, I could easily get a list of packages >> which depend on or use the library - and spot if one of them is >> something that I use or have installed. It would be crude, but I think >> it would work. > > Why bother? Just leave this package alone, or if you are really curious, > remove it and see what happens. Hmm - I'm not sure that is a very useful piece of advice in practice. You would have to test all the functionality of every single piece of software installed, to find out what is affected. From lists at osh.id.au Wed Sep 13 16:34:39 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Thu, 14 Sep 2017 02:34:39 +1000 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <607e8c49-c06f-8645-37fb-41f1f3b3d249@open-t.co.uk> References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> <607e8c49-c06f-8645-37fb-41f1f3b3d249@open-t.co.uk> Message-ID: <55304510-88f8-1337-3e16-4ad6790fe244@osh.id.au> On 09/14/2017 02:06 AM, Sebastian Arcus wrote: > Good call - I didn't think of that. I use sbotools. I suppose I could > grep through /usr/sbo/repo for references to the package I am interested > in. I just tried out "Hoorex" (that someone else suggested), and it works well: # hoorex vlc # vlc vlsub sopcast-player kaffeine # hoorex -i vlc # vlc By default it shows all the packages in SBo that depend on it, with the -i flag it restricts the search to installed packages. -- Dave From didier at slint.fr Wed Sep 13 17:24:04 2017 From: didier at slint.fr (Didier Spaier) Date: Wed, 13 Sep 2017 19:24:04 +0200 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <74078fd2-fd1d-3be1-7549-3dbdfc2f9e05@open-t.co.uk> References: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> <74078fd2-fd1d-3be1-7549-3dbdfc2f9e05@open-t.co.uk> Message-ID: Le 13/09/2017 ? 18:12, Sebastian Arcus a ?crit?: > On 13/09/17 15:29, Didier Spaier wrote: >> Le 13/09/2017 ? 12:40, Sebastian Arcus a ?crit : >>> I know SBo and Slackware doesn't have a system in place to track >>> dependencies - and most of the time that suits me just fine. However, >>> on occasion, I stumble over a piece of SBo software installed on my >>> machine - such as a library, and I would like to know why is it there >>> - which package needs it. I was thinking that, if when using the >>> search field on SBo website, it would also search through the .info >>> and README files of packages, I could easily get a list of packages >>> which depend on or use the library - and spot if one of them is >>> something that I use or have installed. It would be crude, but I think >>> ? it would work. >> >> Why bother? Just leave this package alone, or if you are really curious, >> remove it and see what happens. > > Hmm - I'm not sure that is a very useful piece of advice in practice.> You would have to test all the functionality of every single piece of > software installed, to find out what is affected. That's why if you are not sure why and when it was installed, me actual advice is to just keep it. From s.arcus at open-t.co.uk Wed Sep 13 18:11:06 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Wed, 13 Sep 2017 19:11:06 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> Message-ID: On 13/09/17 14:41, David O'Shaughnessy wrote: > On 09/13/2017 10:51 PM, Sebastian Arcus wrote: >> Thank you for the suggestion. At the moment I don't have a git clone of >> SBo - and I was hoping there is an easier way to search for a package >> than setting up a git repository :-) > > If you use sbotools or sbopkg wouldn't you already have that though? Not > sure where sbopkg puts it, but sbotools has it in /usr/sbo/repo Actually, slightly OT, but why is sbotools storing its stuff under /usr/sbo? I was under the impression that stuff shouldn't go directly under /usr, but under /usr/share/ or /usr/lib or /usr/src and so on? Thinking about it, it would have made more sense to store it somewhere like /var/lib/sbo I think. "/usr/sbo" just looks messy. From rworkman at slackbuilds.org Thu Sep 14 04:00:54 2017 From: rworkman at slackbuilds.org (Robby Workman) Date: Wed, 13 Sep 2017 23:00:54 -0500 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> Message-ID: <20170913230054.2c5a9a81@home.rlworkman.net> On Wed, 13 Sep 2017 19:11:06 +0100 Sebastian Arcus wrote: > On 13/09/17 14:41, David O'Shaughnessy wrote: > > On 09/13/2017 10:51 PM, Sebastian Arcus wrote: > >> Thank you for the suggestion. At the moment I don't have a git > >> clone of SBo - and I was hoping there is an easier way to search > >> for a package than setting up a git repository :-) > > > > If you use sbotools or sbopkg wouldn't you already have that > > though? Not sure where sbopkg puts it, but sbotools has it > > in /usr/sbo/repo > > Actually, slightly OT, but why is sbotools storing its stuff under > /usr/sbo? I was under the impression that stuff shouldn't go directly > under /usr, but under /usr/share/ or /usr/lib or /usr/src and so on? > Thinking about it, it would have made more sense to store it > somewhere like /var/lib/sbo I think. "/usr/sbo" just looks messy. Agreed, for what that's worth. -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yth at ythogtha.org Thu Sep 14 08:08:32 2017 From: yth at ythogtha.org (Ythogtha) Date: Thu, 14 Sep 2017 10:08:32 +0200 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> Message-ID: <20170914100832.a3c40979d1d390b18f565bb6@ythogtha.org> > If you have a git clone of the SBo repository, you could go there and use this > kind of command line : > > -> Get all SBo packages requiredby a specified package, here is wxGTK3 : > grep -E "REQUIRE.*wxGTK3" */*/*.info | cut -d. -f1 | rev | cut -d / -f1 | rev > > -> Get all the ones installed on your system : > for pkg in $(grep -E "REQUIRE.*wxGTK3" */*/*.info | cut -d. -f1 | rev | \ > cut -d / -f1 | rev); \ > do ls /var/log/packages/$pkg-*SBo; done 2>/dev/null > > /var/log/packages/audacity-2.1.3-x86_64-2SBo > /var/log/packages/codelite-8.1-x86_64-1SBo > /var/log/packages/filezilla-3.27.1-x86_64-1SBo > > -> Get only the names by adding at the end of the previous one : > | rev | cut -d- -f4 | cut -d/ -f1 | rev I wrote a bug here, it should be "-f4-" and not "-f4": | rev | cut -d- -f4- | cut -d/ -f1 | rev Or else a package like "MySQL-python" would only show "python", which wouldn't be good... -- Yth From andreas.guldstrand at gmail.com Thu Sep 14 08:57:08 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Thu, 14 Sep 2017 10:57:08 +0200 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: <20170913230054.2c5a9a81@home.rlworkman.net> References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> <20170913230054.2c5a9a81@home.rlworkman.net> Message-ID: On 14 September 2017 at 06:00, Robby Workman wrote: > On Wed, 13 Sep 2017 19:11:06 +0100 > Sebastian Arcus wrote: >> Actually, slightly OT, but why is sbotools storing its stuff under >> /usr/sbo? I was under the impression that stuff shouldn't go directly >> under /usr, but under /usr/share/ or /usr/lib or /usr/src and so on? >> Thinking about it, it would have made more sense to store it >> somewhere like /var/lib/sbo I think. "/usr/sbo" just looks messy. > > > Agreed, for what that's worth. As the maintainer of sbotools, I also agree, /var/lib/sbo would be a better place. It would have been moved there already, except for the need to maintain backwards compatibility. Once I manage to put together a new major version it'll likely change. / Andreas From gen-bch at useyouresp.org.uk Thu Sep 14 09:16:27 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Thu, 14 Sep 2017 10:16:27 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <3e5211b8-d437-46f0-b2df-2d2913a46975@slint.fr> Message-ID: <20170914101627.0b366686@dv6920ea.localdomain> On Wed, 13 Sep 2017 16:06:54 +0100 David Spencer wrote: > Chris Willing's tool hoorex will find "inverse dependencies" of > packages. https://github.com/cwilling/hoorex > > One other idea for finding why you installed a library -- you can list > the files in /var/log/packages sorted by time (ls -lt) which will show > you the other packages that were installed immediately afterwards. > > Twenty years ago I wrote this kind of thing in a little book. Ten > years ago I used dokuwiki. Now I just never uninstall them. > > There is no official test build system that would have a full listing > of files. Unofficially, I build almost every package from time to > time. A list of files (depending on random options) in almost every > package is 325 Mb. I'm not sure I would want to put them unofficially > on a website somewhere if each query will grep 325Mb of data. (And > also I hate elasticsearch.) > Im likely comparatively poor at sysadmin, but my approach re:slackware taken from my old school a long time is to create (and try to maintain haha) a register of any software added afterwards...inc documenting the dependencies etc. Its only a simple xml affair that records whats listed on SBo as required and optional (if ive intalled the optional stuff) etc, but i can cross check stuff easily enough. My biggest problem is laziness in keeping up to it :-) Of course this is all no good, if its not done right from the get go. As mentioned above though, I find the var/log/packages thing can get me some way. I like Slackware and SBo - I think the community is great and thanks to everyone involved keeping it ie. Slackware and SBo, as it is. If it went full-on like the other distros, it would be a shame. Have a lovely day folks. Peace best wishes Habs From lists at osh.id.au Thu Sep 14 09:45:44 2017 From: lists at osh.id.au (David O'Shaughnessy) Date: Thu, 14 Sep 2017 19:45:44 +1000 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> <20170913230054.2c5a9a81@home.rlworkman.net> Message-ID: On 09/14/2017 06:57 PM, Andreas Guldstrand wrote: > As the maintainer of sbotools, I also agree, /var/lib/sbo would be a > better place. It would have been moved there already, except for the > need to maintain backwards compatibility. Once I manage to put > together a new major version it'll likely change. I'd prefer that also, /usr/sbo always struck me as somewhat odd. -- Dave From yalhcru at gmail.com Thu Sep 14 12:15:03 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 14 Sep 2017 08:15:03 -0400 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> <20170913230054.2c5a9a81@home.rlworkman.net> Message-ID: On 9/14/17, David O'Shaughnessy wrote: > I'd prefer that also, /usr/sbo always struck me as somewhat odd. I don't actually know, but I bet it's because sbotools was modelled on FreeBSD ports, which uses /usr/ports. From s.arcus at open-t.co.uk Thu Sep 14 18:29:16 2017 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Thu, 14 Sep 2017 19:29:16 +0100 Subject: [Slackbuilds-users] Very simple way of finding dependency In-Reply-To: References: <20170913135656.13a8b293321e6b83afebd747@ythogtha.org> <0d10bb0c-2eb6-c4f4-6d79-19302b08c6b6@osh.id.au> <20170913230054.2c5a9a81@home.rlworkman.net> Message-ID: <45d3c28e-efa6-ed7a-8145-e967c0ef571b@open-t.co.uk> On 14/09/17 09:57, Andreas Guldstrand wrote: > On 14 September 2017 at 06:00, Robby Workman wrote: >> On Wed, 13 Sep 2017 19:11:06 +0100 >> Sebastian Arcus wrote: >>> Actually, slightly OT, but why is sbotools storing its stuff under >>> /usr/sbo? I was under the impression that stuff shouldn't go directly >>> under /usr, but under /usr/share/ or /usr/lib or /usr/src and so on? >>> Thinking about it, it would have made more sense to store it >>> somewhere like /var/lib/sbo I think. "/usr/sbo" just looks messy. >> >> >> Agreed, for what that's worth. > > As the maintainer of sbotools, I also agree, /var/lib/sbo would be a > better place. It would have been moved there already, except for the > need to maintain backwards compatibility. Once I manage to put > together a new major version it'll likely change. That's good news From willysr at slackbuilds.org Sat Sep 16 00:50:44 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 Sep 2017 07:50:44 +0700 Subject: [Slackbuilds-users] Updates - 20170916.1 Message-ID: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> Hi, We got plenty of updates this weekend and also some security updates for flashplayer-plugins and peppperflash-plugins. As some of those updates were a requirement for other packages, if you found some issues after upgrading those packages, you might want to try to rebuild the other packages. Also, a reminder that Pat has just issued a security advisory for kernel updates in -stable (and -current) regarding to BlueBorne attack Have fun :) Sat Sep 16 00:16:29 UTC 2017 academic/flexbar: Added (barcode and adapter removal). academic/novocraft: Added (map short reads onto reference genome). academic/pysam: Added (read/write genomic data sets). audio/pianobar: Updated for version 2017.08.30. business/reckon: Switch to https. desktop/dwm: New maintainer. desktop/elementary-xfce: Updated for version 0.9. desktop/fbrowse-tray: Updated for version 0.08. desktop/gtk-theme-Greybird: Updated for version 3.22.5. desktop/neofetch: Updated for version 3.3.0. desktop/sawfish: SlackBuild script updated. desktop/tint2: Updated for version 15.1. development/astyle: Updated for version 3.0.1 development/jupyter-notebook: Updated for version 5.1.0. development/komodo-edit: Updated for version 10.2.3. development/komodo-ide: Updated for version 10.2.3. development/meld3: Updated for version 3.18.0. development/ninja: Updated for version 1.8.2. development/perf: Updated for version 4.4.88. development/simavr: Fixed download. games/RetroArch: Added udev input driver patch. games/doomretro: Updated for version 2.5.5. games/freedroidrpg: Updated for version 0.16.1. games/lutris: Updated for version 0.4.13. games/megaglest: Switch to https. games/naev: Updated for version 0.7.0. gis/OWSLib: Updated for version 0.15.0. gis/navit: Updated for version R7651. gis/pgrouting: Updated for version 2.5.0. gis/proj: Add datumgrid to build. gis/qgis: Updated for version 2.18.13. graphics/Blender: Updated for version 2.79 graphics/feh: Updated for version 2.20. ham/aprx: Updated for version 2.9.0. ham/dxcc: Updated for newer CTY.DAT file. ham/fldigi: Updated for version 4.0.9. ham/grig: Updated for version 0.8.1. ham/psk31lx: Updated for version 2.1. ham/tqsl: Updated for version 2.3.1. ham/wxapt: Updated for version 1.6. ham/xnec2c: Updated for version 3.5.1. libraries/libversion: Updated for version 2.0.0. libraries/live555: Updated for version 2017.09.12 libraries/openjfx: Added (Open Source JavaFX binary distribution). libraries/vte3: Updated for version 0.50.0. libraries/webkit2gtk: Updated for version 2.18.0. libraries/xerces-c: Updated for version 3.2.0. misc/par2cmdline: Updated for version 0.7.4. multimedia/MediathekView: Updated for version 13.0.2. multimedia/QMPlay2: Updated for version 17.09.13. multimedia/flashplayer-plugin: Updated for version 27.0.0.130. multimedia/mpv: Updated for version 0.27.0 + update README. multimedia/munt: Updated for version 2.2.0. multimedia/pepperflash-plugin: Updated for version 27.0.0.130. multimedia/winff: Updated for version 20170714_220b212. network/davmail: Updated for version 4.8.0. network/munge: Updated for version 0.5.12. network/nbd: Updated for version 3.16.2 network/ntpclient: Updated for version 2015_365. network/owncloud-client: Updated for version 2.3.3. network/slurm: Updated for version 17.02.7. network/sqlmap: Updated for version 1.1.9. network/tinc: Updated for version 1.0.32. office/aspell6-es: Fix VERSION in .info. office/htmldoc: Fixed download. office/pdf2djvu: Updated for version 0.9.7. office/pdfstudio12: Updated for version 12.0.3. office/zim: Updated for version 0.67. perl/perl-CPAN-Perl-Releases: Updated for version 3.34. perl/perl-Date-Manip: Disable make test. perl/perl-IO-Socket-SSL: Updated for version 2.051. perl/perl-Mojolicious: Updated for version 7.46. perl/perl-Time-Piece: Updated for version 1.3202. python/dulwich: Updated for version 0.18.3. python/python-docker: Updated for version 2.5.1. python/python-texttable: Updated for version 0.9.1. python/python-unicodedata2: Updated for version 10.0.0. python/ruffus: Added (Computation Pipeline library). ruby/ruby-build: Updated for version 20170914. system/containerd: Updated for version 0.2.9_6e23458. system/displaylink: Added (driver for DisplayLink devices). system/docker-compose: Updated for version 1.16.1. system/docker-machine: Updated for version 0.12.2. system/docker-proxy: Updated for version 20170120_7b2b1fe. system/docker: Updated for version 17.06.2. system/evdi-kernel: Added (Extensible Virtual Display Interface). system/evdi: Added (Extensible Virtual Display Interface). system/fio: Updated for version 3.0. system/firejail: Updated for version 0.9.50. system/haveged: SlackBuild updated (thanks to Nikos Giotis). system/influxdb: Updated for version 1.3.5. system/inxi: Updated for version 2.3.38. system/letsencrypt: Updated for version 0.18.1. system/noto-emoji: Updated for version git7159f45. system/openmpi: Updated for version 2.1.1. system/openrc: Updated for version 0.30. system/posh: Added (Policy-compliant Ordinary SHell). system/rndaddentropy: Fix SlackBuild and .info. system/runc: Updated for version 1.0.0_rc3_810190c. system/sleuthkit: Updated for version 4.4.2. system/wine-staging: Updated for version 2.16. system/xpad: Fixed slack-desc. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Sep 16 01:18:33 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 Sep 2017 08:18:33 +0700 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> Message-ID: > system/containerd: Updated for version 0.2.9_6e23458. > system/docker-machine: Updated for version 0.12.2. > system/docker-proxy: Updated for version 20170120_7b2b1fe. > system/docker: Updated for version 17.06.2. > system/runc: Updated for version 1.0.0_rc3_810190c. It seems some of the docker updates have invalid MD5SUM values. i have pushed the fixes on my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Sep 16 05:35:25 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 Sep 2017 12:35:25 +0700 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> Message-ID: > libraries/webkit2gtk: Updated for version 2.18.0. Just FYI, if you are using -current (this is not supported by SBo officially), you need to add gst-plugins-bad in order to build webkit2gtk 2.18.0 as they enabled GstreamerGL when building against gstreamer >= 1.10.0. As 14.2 still uses 1.6.x, it's disabled by default, so it works without gst-plugins-bad. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From audrius at neutrino.lt Sat Sep 16 08:57:01 2017 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sat, 16 Sep 2017 11:57:01 +0300 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> Message-ID: <20170916085701.GA2485@varna> On Sat, 2017-09-16 at 08:18:33 +0700, Willy Sudiarto Raharjo wrote: > > system/containerd: Updated for version 0.2.9_6e23458. > > system/docker-machine: Updated for version 0.12.2. > > system/docker-proxy: Updated for version 20170120_7b2b1fe. > > system/docker: Updated for version 17.06.2. > > system/runc: Updated for version 1.0.0_rc3_810190c. > > It seems some of the docker updates have invalid MD5SUM values. > i have pushed the fixes on my branch Well, this is strange. I still have all the tarballs downloaded when I was updating docker-related build scripts (it was last Sunday). I checked all of them and their MD5 checksums match the ones in .info files. But when I downloaded runc tarball now, its checksum is different, although there are no apparent changes. Both times I used wget to download the tarballs. Has anyone got a clue what happened here? -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Sep 16 10:00:52 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 16 Sep 2017 17:00:52 +0700 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: <20170916085701.GA2485@varna> References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> <20170916085701.GA2485@varna> Message-ID: > Well, this is strange. I still have all the tarballs downloaded when I > was updating docker-related build scripts (it was last Sunday). I > checked all of them and their MD5 checksums match the ones in .info > files. But when I downloaded runc tarball now, its checksum is > different, although there are no apparent changes. Both times I used > wget to download the tarballs. > > Has anyone got a clue what happened here? There's a chance that upstream re-upload the tar.gz source again with a minor change? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From audrius at neutrino.lt Sat Sep 16 10:44:10 2017 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sat, 16 Sep 2017 13:44:10 +0300 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> <20170916085701.GA2485@varna> Message-ID: <20170916104410.GA14914@varna> On Sat, 2017-09-16 at 17:00:52 +0700, Willy Sudiarto Raharjo wrote: > There's a chance that upstream re-upload the tar.gz source again with a > minor change? These archives are generated by GitHub from git commits or tags, so they're not really uploaded. Extracted content is identical according to diff, file timestamps look the same as well. Maybe something changed at GitHub itself after I downloaded them? -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From ryanpcmcquen at member.fsf.org Sat Sep 16 17:34:20 2017 From: ryanpcmcquen at member.fsf.org (Ryan P.C. McQuen) Date: Sat, 16 Sep 2017 10:34:20 -0700 Subject: [Slackbuilds-users] Leiningen build for sale Message-ID: <15e8bc164eb.fa74c6a4379242.3242709454828709831@member.fsf.org> Somehow I missed this one when giving up all my builds. Whoever wants it can have for $0.00. -Ryan [ryanpcmcquen.org] -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Sat Sep 16 20:31:24 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 16 Sep 2017 14:31:24 -0600 Subject: [Slackbuilds-users] Leiningen build for sale In-Reply-To: <15e8bc164eb.fa74c6a4379242.3242709454828709831@member.fsf.org> References: <15e8bc164eb.fa74c6a4379242.3242709454828709831@member.fsf.org> Message-ID: ill wait till it is cheaper... thanks... On Sep 16, 2017 11:35 AM, "Ryan P.C. McQuen" wrote: > Somehow I missed this one when giving up all my builds. Whoever wants it > can have for $0.00. > > > -Ryan > [ryanpcmcquen.org] > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From aclemons at runbox.no Sat Sep 16 22:23:51 2017 From: aclemons at runbox.no (Andrew Clemons) Date: Sun, 17 Sep 2017 10:23:51 +1200 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: <20170916104410.GA14914@varna> References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> <20170916085701.GA2485@varna> <20170916104410.GA14914@varna> Message-ID: <20170916222350.GA24726@runbox.no> On 2017-09-16 13:44:10 +0300, audrius at neutrino.lt wrote: > Maybe something changed at GitHub itself after I downloaded them? ^ this https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From audrius at neutrino.lt Sun Sep 17 10:21:23 2017 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Sun, 17 Sep 2017 13:21:23 +0300 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: <20170916222350.GA24726@runbox.no> References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> <20170916085701.GA2485@varna> <20170916104410.GA14914@varna> <20170916222350.GA24726@runbox.no> Message-ID: <20170917102123.GA2453@varna> On Sun, 2017-09-17 at 10:23:51 +1200, Andrew Clemons wrote: > On 2017-09-16 13:44:10 +0300, audrius at neutrino.lt wrote: > > Maybe something changed at GitHub itself after I downloaded them? > > ^ this > > https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745 Thanks for the link, that explains it. I guess there's nothing we can do about it, only update the checksums when we find they have changed. Also forgot to thank Willy for updating all the checksums for my scripts, I appreciate it. -- Audrius Ka?ukauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: not available URL: From willysr at slackbuilds.org Sun Sep 17 11:33:35 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Sep 2017 18:33:35 +0700 Subject: [Slackbuilds-users] Updates - 20170916.1 In-Reply-To: <20170917102123.GA2453@varna> References: <864ef3cd-d6bc-0b96-96ef-51388ca5ef93@slackbuilds.org> <20170916085701.GA2485@varna> <20170916104410.GA14914@varna> <20170916222350.GA24726@runbox.no> <20170917102123.GA2453@varna> Message-ID: <07c66d7b-2701-004a-f9d7-d6ad166e17a4@slackbuilds.org> >> https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745 > > Thanks for the link, that explains it. I guess there's nothing we can > do about it, only update the checksums when we find they have changed. > > Also forgot to thank Willy for updating all the checksums for my > scripts, I appreciate it. A new public update will be pushed soon :) -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Sep 17 13:41:17 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Sep 2017 20:41:17 +0700 Subject: [Slackbuilds-users] Updates - 20170917.1 Message-ID: <08c88eb4-31b1-69f4-b283-ad621867af1d@slackbuilds.org> Hi, here's another public update to fix some incorrect MD5SUMs for some scripts and more updates since the last public update, including a security update for newsbeuter to fix remote code execution. Regarding the incorrect MD5SUM on previous public update, it is believed due to changes in GitHub due to their recent OS upgrade on it's fileserver. See more detail here [1]. Let's hope they fix this issue already. Sun Sep 17 13:31:07 UTC 2017 desktop/awf: Added (A Widget Factory). development/anjuta: Updated for version 3.26.0. development/atom-amd64: Updated for version 1.20.0. development/diffoscope: Updated for version 86. development/git-lfs: Updated for version 2.3.0. gis/gpsd: Updated for version 3.17. libraries/WebOb: Updated for version 1.7.3. libraries/gdl: Updated for version 3.26.0. libraries/hyphen: Switch to https. libraries/nx-libs: Update script. libraries/xmlsec: Updated for version 1.2.25. misc/dos2unix: Updated for version 7.3.5. network/GeoIP: Updated for version 1.6.11. network/WireGuard: Updated for version 0.0.20170907. network/newsbeuter: Patch remote code execution vulnerability. network/youtube-dl: Updated for version 2017.09.15. office/leafpad: New maintainer. python/ipython: Upgraded for version 5.5.0. python/pytest-runner: Updated for version 2.12.1. python/python-autobahn: Updated for version 17.9.2. python/python-m2r: Updated for version 0.1.12. python/python-txaio: Updated for version 2.8.2. python/python3-ipython: Updated for version 6.2.0. system/containerd: Update MD5SUM. system/docker-machine: Update MD5SUM. system/docker-proxy: Update MD5SUM. system/docker: Update MD5SUM. system/runc: Update MD5SUM. system/salt: Updated for version 2017.7.1. +--------------------------+ [1]: https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Sun Sep 17 17:59:25 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 17 Sep 2017 10:59:25 -0700 (PDT) Subject: [Slackbuilds-users] zim-0.67 fails to build Message-ID: Just downloaded zim-0.67 to upgrade from -0.65, but it won't build: # ./zim.SlackBuild tar: This does not look like a tar archive tar: Skipping to next header tar: Exiting with failure status due to previous errors The md5sum of the tarball does not match that on the web page: web page: e87975727f1166c723912c949bea51f2 here: $ md5sum zim/zim-0.67.tar.gz 99a564aecfe0a0116639bbf812bca055 zim/zim-0.67.tar.gz Advice, please, Rich From didier at slint.fr Sun Sep 17 18:16:11 2017 From: didier at slint.fr (Didier Spaier) Date: Sun, 17 Sep 2017 20:16:11 +0200 Subject: [Slackbuilds-users] zim-0.67 fails to build In-Reply-To: References: Message-ID: <4a2be752-f90e-05d9-a49b-1700c590673d@slint.fr> Le 17/09/2017 ? 19:59, Rich Shepard a ?crit?: > ? Just downloaded zim-0.67 to upgrade from -0.65, but it won't build: > > # ./zim.SlackBuild tar: This does not look like a tar archive > tar: Skipping to next header > tar: Exiting with failure status due to previous errors > > ? The md5sum of the tarball does not match that on the web page: > web page: e87975727f1166c723912c949bea51f2 > here: $ md5sum zim/zim-0.67.tar.gz 99a564aecfe0a0116639bbf812bca055 zim/zim-0.67.tar.gz No issue here. The md5sum matches and the package is built. Download it again, preferably using wget as firefox can do nasty things when downloading a compressed archive depending of settings. Didier From rshepard at appl-ecosys.com Sun Sep 17 18:30:23 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 17 Sep 2017 11:30:23 -0700 (PDT) Subject: [Slackbuilds-users] zim-0.67 fails to build [RESOLVED] In-Reply-To: <4a2be752-f90e-05d9-a49b-1700c590673d@slint.fr> References: <4a2be752-f90e-05d9-a49b-1700c590673d@slint.fr> Message-ID: On Sun, 17 Sep 2017, Didier Spaier wrote: > No issue here. The md5sum matches and the package is built. Didier, Good to know. > Download it again, preferably using wget as firefox can do nasty things > when downloading a compressed archive depending of settings. Haven't had this issue with firefox before. Using wget did the job once I removed the first download. I'll save your advice if this situation happens again. Thanks, Rich From gen-bch at useyouresp.org.uk Sun Sep 17 18:59:01 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Sun, 17 Sep 2017 19:59:01 +0100 Subject: [Slackbuilds-users] webkit2gtk build problems Message-ID: <20170917195901.6152f465@dv6920ea.localdomain> Hello All I'm afraid, I need some help please to sort out what's going on with the build for webkit2gtk (2.18.0) downloaded via SBo today onto slackware 14.2 64bit full standard install. I have run the build on two different machines (AMD and Intel) and both coming back with same error at same place. Previous version build fine. Do I need to rebuild the listed dependencies (actually on the Intel all were built), or is it something else that you can spot for me please ? Not sure, but I wonder if I've missed previous posts about this..perhaps not ... my mind is a sieve. (build error attached below). Thank you for any ideas/help etc. Habs [ 76%] Building CXX object Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o In file included from /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp:21:0: /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h:23:40: fatal error: WebCore/HysteresisActivity.h: No such file or directory compilation terminated. Source/WebCore/CMakeFiles/WebCore.dir/build.make:51125: recipe for target 'Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o' failed make[2]: *** [Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o] Error 1 CMakeFiles/Makefile2:1065: recipe for target 'Source/WebCore/CMakeFiles/WebCore.dir/all' failed make[1]: *** [Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2 Makefile:149: recipe for target 'all' failed make: *** [all] Error 2 r From jgraha8 at gmail.com Sun Sep 17 23:10:22 2017 From: jgraha8 at gmail.com (Jason Graham) Date: Sun, 17 Sep 2017 19:10:22 -0400 Subject: [Slackbuilds-users] makedepf90: dropped Message-ID: Hi, Looks like makedepf90 has been whacked from 14.2. It's a package that I maintain. There probably isn't an enormous number of folks using it (other than me), but since it's included with most other distros I figured it's a good idea to include. I'd like to reinstated it; can provide a new upload if it's helpful. Actually, looks like the original homepage has disappeared which may be why it was considered dead (?). debian and fedora have copies of the source. I can host it as an alternative, though, not sure what to put as the homepage at this point since it seems dead. Suggestions welcomed. Kind regards, J -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Mon Sep 18 08:42:40 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 18 Sep 2017 10:42:40 +0200 Subject: [Slackbuilds-users] libquvi and libquvi-scripts SlackBuild Message-ID: <40099eab-266b-b6d4-63dd-6492d7a2c598@gmail.com> Hi, FYI, since mpv no longer requires libquvi, nothing else seems to depend on it. I'm not telling to remove it from repository without good reason. I'm not sure if it's still maintained upstream. (Bcc-d maintainer). -- Best regards, Andrzej Telszewski From willysr at slackbuilds.org Mon Sep 18 08:51:02 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 18 Sep 2017 15:51:02 +0700 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170917195901.6152f465@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> Message-ID: <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> On 09/18/2017 01:59 AM, Habs wrote: > Hello All > > I'm afraid, I need some help please to sort out what's going on with > the build for webkit2gtk (2.18.0) downloaded via SBo today onto > slackware 14.2 64bit full standard install. > > I have run the build on two different machines (AMD and Intel) and both > coming back with same error at same place. Previous version build fine. > > > > > Do I need to rebuild the listed dependencies (actually on the Intel all > were built), or is it something else that you can spot for me please ? > > Not sure, but I wonder if I've missed previous posts about > this..perhaps not ... my mind is a sieve. > > (build error attached below). > > Thank you for any ideas/help etc. > > Habs > > [ 76%] Building CXX object > Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o > In file included > from /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp:21:0: /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h:23:40: > fatal error: WebCore/HysteresisActivity.h: No such file or directory > compilation terminated. > Source/WebCore/CMakeFiles/WebCore.dir/build.make:51125: recipe for > target > 'Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o' > failed make[2]: *** > [Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o] > Error 1 CMakeFiles/Makefile2:1065: recipe for target > 'Source/WebCore/CMakeFiles/WebCore.dir/all' failed make[1]: *** > [Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2 Makefile:149: > recipe for target 'all' failed make: *** [all] Error 2 r Hi I think i made a mistake when testing this build. I *may have* ran it on a current VM rather than a stable VM, so i'm reverting it to 2.16.0 in my branch for now while i'm investigating it further. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From sam_web at yahoo.de Mon Sep 18 09:33:21 2017 From: sam_web at yahoo.de (Marek Srejma) Date: Mon, 18 Sep 2017 11:33:21 +0200 Subject: [Slackbuilds-users] libquvi and libquvi-scripts SlackBuild In-Reply-To: <40099eab-266b-b6d4-63dd-6492d7a2c598@gmail.com> References: <40099eab-266b-b6d4-63dd-6492d7a2c598@gmail.com> Message-ID: <876cdcf0-5bbd-33bd-994f-01a2b81d1f6e@yahoo.de> Hi Andrzej, cclive requires quvi, which requires libquvi. Although cclive can still be useful, it's not developed anymore and is not as good as youtube-dl. The current realease 0.9.3 is from 2013. I'm maintaining the SlackBuilds for cclive, quvi, libquvi and libqvi-scripts, however I'm not sure if of in which case libqvi-scripts are useful. :) Marek Andrzej Telszewski schrieb: > Hi, > > FYI, since mpv no longer requires libquvi, nothing else seems to > depend on it. > I'm not telling to remove it from repository without good reason. > I'm not sure if it's still maintained upstream. > > (Bcc-d maintainer). > . From sam_web at yahoo.de Mon Sep 18 09:54:37 2017 From: sam_web at yahoo.de (Marek Srejma) Date: Mon, 18 Sep 2017 11:54:37 +0200 Subject: [Slackbuilds-users] libquvi and libquvi-scripts SlackBuild In-Reply-To: <876cdcf0-5bbd-33bd-994f-01a2b81d1f6e@yahoo.de> References: <40099eab-266b-b6d4-63dd-6492d7a2c598@gmail.com> <876cdcf0-5bbd-33bd-994f-01a2b81d1f6e@yahoo.de> Message-ID: <0d2646ea-6e52-68d0-f806-7a1c3bb85b57@yahoo.de> > however I'm not sure if of in which case libqvi-scripts are useful. :) sorry, libquvi requires libqvi-scripts. :) Marek Srejma schrieb: > Hi Andrzej, > > cclive requires quvi, which requires libquvi. > > Although cclive can still be useful, it's not developed anymore and is > not as good as youtube-dl. The current realease 0.9.3 is from 2013. > I'm maintaining the SlackBuilds for cclive, quvi, libquvi and > libqvi-scripts, however I'm not sure if of in which case > libqvi-scripts are useful. :) > > > Marek > > Andrzej Telszewski schrieb: >> Hi, >> >> FYI, since mpv no longer requires libquvi, nothing else seems to >> depend on it. >> I'm not telling to remove it from repository without good reason. >> I'm not sure if it's still maintained upstream. >> >> (Bcc-d maintainer). >> > . From yth at ythogtha.org Mon Sep 18 09:59:02 2017 From: yth at ythogtha.org (Ythogtha) Date: Mon, 18 Sep 2017 11:59:02 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> Message-ID: <20170918115902.fc2971e1435249504378c61b@ythogtha.org> > On 09/18/2017 01:59 AM, Habs wrote: > > Hello All > > > > I'm afraid, I need some help please to sort out what's going on with > > the build for webkit2gtk (2.18.0) downloaded via SBo today onto > > slackware 14.2 64bit full standard install. > > > > I have run the build on two different machines (AMD and Intel) and both > > coming back with same error at same place. Previous version build fine. > > > > > > > > > > Do I need to rebuild the listed dependencies (actually on the Intel all > > were built), or is it something else that you can spot for me please ? > > > > Not sure, but I wonder if I've missed previous posts about > > this..perhaps not ... my mind is a sieve. > > > > (build error attached below). > > > > Thank you for any ideas/help etc. > > > > Habs > > > > [ 76%] Building CXX object > > Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o > > In file included > > from /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp:21:0: /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h:23:40: > > fatal error: WebCore/HysteresisActivity.h: No such file or directory > > compilation terminated. > > Source/WebCore/CMakeFiles/WebCore.dir/build.make:51125: recipe for > > target > > 'Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o' > > failed make[2]: *** > > [Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o] > > Error 1 CMakeFiles/Makefile2:1065: recipe for target > > 'Source/WebCore/CMakeFiles/WebCore.dir/all' failed make[1]: *** > > [Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2 Makefile:149: > > recipe for target 'all' failed make: *** [all] Error 2 r > > Hi > > I think i made a mistake when testing this build. I *may have* ran it on > a current VM rather than a stable VM, so i'm reverting it to 2.16.0 in > my branch for now while i'm investigating it further. > > > -- > Willy Sudiarto Raharjo > I've just compiled it fine on a slackware64 14.2 fully patched, but with a lot of other packages in it, so not a clean install, but still not on a current branch. I didn't rebuild any dependency since my last 2.16 build, compilation was already ongoing when you sent your message, and I just let it go to see what would happen. Are you sure you didn't ran out of disk space ? It's taking a lot of it during compilation.... -- Arnaud From atelszewski at gmail.com Mon Sep 18 10:10:27 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 18 Sep 2017 12:10:27 +0200 Subject: [Slackbuilds-users] libquvi and libquvi-scripts SlackBuild In-Reply-To: <876cdcf0-5bbd-33bd-994f-01a2b81d1f6e@yahoo.de> References: <40099eab-266b-b6d4-63dd-6492d7a2c598@gmail.com> <876cdcf0-5bbd-33bd-994f-01a2b81d1f6e@yahoo.de> Message-ID: <56c3b50b-57f3-6f60-25e2-fb03fc16b3cc@gmail.com> On 18/09/17 11:33, Marek Srejma wrote: > Hi Andrzej, > > cclive requires quvi, which requires libquvi. > > Although cclive can still be useful, it's not developed anymore and is > not as good as youtube-dl. The current realease 0.9.3 is from 2013. > I'm maintaining the SlackBuilds for cclive, quvi, libquvi and > libqvi-scripts, however I'm not sure if of in which case libqvi-scripts > are useful. :) > > > Marek > > Andrzej Telszewski schrieb: >> Hi, >> >> FYI, since mpv no longer requires libquvi, nothing else seems to >> depend on it. >> I'm not telling to remove it from repository without good reason. >> I'm not sure if it's still maintained upstream. >> >> (Bcc-d maintainer). >> OK, grepping didn't reveal cclive to me. My bad ;-) -- Best regards, Andrzej Telszewski From gen-bch at useyouresp.org.uk Mon Sep 18 10:19:26 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Mon, 18 Sep 2017 11:19:26 +0100 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170918115902.fc2971e1435249504378c61b@ythogtha.org> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> Message-ID: <20170918111926.4aacb666@dv6920ea.localdomain> On Mon, 18 Sep 2017 11:59:02 +0200 Ythogtha wrote: > > Hi > > > > I think i made a mistake when testing this build. I *may have* ran > > it on a current VM rather than a stable VM, so i'm reverting it to > > 2.16.0 in my branch for now while i'm investigating it further. > > > > > > -- > > Willy Sudiarto Raharjo > > > > I've just compiled it fine on a slackware64 14.2 fully > patched, but with a lot of other packages in it, so not a clean > install, but still not on a current branch. I didn't rebuild any > dependency since my last 2.16 build, compilation was already ongoing > when you sent your message, and I just let it go to see what would > happen. > > Are you sure you didn't ran out of disk space ? It's taking a > lot of it during compilation.... > Hard disk space, no I dont think it is a partition space issue on the machine.... how much would it require with this release compared to previous ? The error message I attached, could that be caused by space issues? Thank you Habs From chris.willing at iinet.net.au Mon Sep 18 11:10:36 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Mon, 18 Sep 2017 21:10:36 +1000 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> Message-ID: <64eb618d-6564-86a3-8a7b-5d3adcb9a889@iinet.net.au> On 18/09/17 18:51, Willy Sudiarto Raharjo wrote: > On 09/18/2017 01:59 AM, Habs wrote: >> Hello All >> >> I'm afraid, I need some help please to sort out what's going on with >> the build for webkit2gtk (2.18.0) downloaded via SBo today onto >> slackware 14.2 64bit full standard install. >> >> I have run the build on two different machines (AMD and Intel) and both >> coming back with same error at same place. Previous version build fine. >> >> >> >> >> Do I need to rebuild the listed dependencies (actually on the Intel all >> were built), or is it something else that you can spot for me please ? >> >> Not sure, but I wonder if I've missed previous posts about >> this..perhaps not ... my mind is a sieve. >> >> (build error attached below). >> >> Thank you for any ideas/help etc. >> >> Habs >> >> [ 76%] Building CXX object >> Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o >> In file included >> from /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp:21:0: /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h:23:40: >> fatal error: WebCore/HysteresisActivity.h: No such file or directory >> compilation terminated. >> Source/WebCore/CMakeFiles/WebCore.dir/build.make:51125: recipe for >> target >> 'Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o' >> failed make[2]: *** >> [Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o] >> Error 1 CMakeFiles/Makefile2:1065: recipe for target >> 'Source/WebCore/CMakeFiles/WebCore.dir/all' failed make[1]: *** >> [Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2 Makefile:149: >> recipe for target 'all' failed make: *** [all] Error 2 r > > Hi > > I think i made a mistake when testing this build. I *may have* ran it on > a current VM rather than a stable VM, so i'm reverting it to 2.16.0 in > my branch for now while i'm investigating it further. > 2.18.0 builds fine here on stock 14.2. An interesting aspect of the error above is the complaint about not finding the file /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h, whereas it is actually located (and found during compilation) at /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/BackingStoreBackendCairoImpl.h in my build log. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From yth at ythogtha.org Mon Sep 18 11:11:51 2017 From: yth at ythogtha.org (Arnaud) Date: Mon, 18 Sep 2017 13:11:51 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170918111926.4aacb666@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> Message-ID: <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> Le 18 septembre 2017 12:19:26 GMT+02:00, Habs a ?crit : >On Mon, 18 Sep 2017 11:59:02 +0200 >Ythogtha wrote: > > >> > Hi >> > >> > I think i made a mistake when testing this build. I *may have* ran >> > it on a current VM rather than a stable VM, so i'm reverting it to >> > 2.16.0 in my branch for now while i'm investigating it further. >> > >> > >> > -- >> > Willy Sudiarto Raharjo >> > >> >> I've just compiled it fine on a slackware64 14.2 fully >> patched, but with a lot of other packages in it, so not a clean >> install, but still not on a current branch. I didn't rebuild any >> dependency since my last 2.16 build, compilation was already ongoing >> when you sent your message, and I just let it go to see what would >> happen. >> >> Are you sure you didn't ran out of disk space ? It's taking a >> lot of it during compilation.... >> > >Hard disk space, no I dont think it is a partition space issue on the >machine.... how much would it require with this release compared to >previous ? > >The error message I attached, could that be caused by space issues? > >Thank you >Habs >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ Well, it complains about a missing file, could be because it couldn't be created in the first place. Hence the disk space. Could also be for any number of other reasons... -- Yth. -------------- next part -------------- An HTML attachment was scrubbed... URL: From glenn.becker at gmail.com Mon Sep 18 11:48:42 2017 From: glenn.becker at gmail.com (Glenn Becker) Date: Mon, 18 Sep 2017 07:48:42 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> Message-ID: I got the same error as Habs on a stable install. Glenn On Mon, Sep 18, 2017 at 7:11 AM, Arnaud wrote: > Le 18 septembre 2017 12:19:26 GMT+02:00, Habs > a ?crit : >> >> On Mon, 18 Sep 2017 11:59:02 +0200 >> Ythogtha wrote: >> >> >> Hi >>>> >>>> I think i made a mistake when testing this build. I *may have* ran >>>> it on a current VM rather than a stable VM, so i'm reverting it to >>>> 2.16.0 in my branch for now while i'm investigating it further. >>>> >>>> >>>> -- >>>> Willy Sudiarto Raharjo >>>> >>>> >>> I've just compiled it fine on a slackware64 14.2 fully >>> patched, but with a lot of other packages in it, so not a clean >>> install, but still not on a current branch. I didn't rebuild any >>> dependency since my last 2.16 build, compilation was already ongoing >>> when you sent your message, and I just let it go to see what would >>> happen. >>> >>> Are you sure you didn't ran out of disk space ? It's taking a >>> lot of it during compilation.... >>> >>> >> Hard disk space, no I dont think it is a partition space issue on the >> machine.... how much would it require with this release compared to >> previous ? >> >> The error message I attached, could that be caused by space issues? >> >> Thank you >> Habs >> ------------------------------ >> >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > Well, it complains about a missing file, could be because it couldn't be > created in the first place. Hence the disk space. > Could also be for any number of other reasons... > -- > Yth. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Sep 18 14:18:19 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 18 Sep 2017 21:18:19 +0700 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> Message-ID: > I got the same error as Habs on a stable install. I was convinced by Matteo and David that webkit2gtk build fine on stable and current for both arch, BUT it requires a LOT of resources, so i cancelled my revert and update README instead to make additional SWAP space if you have small amount of memory installed. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From glenn.becker at gmail.com Mon Sep 18 14:49:29 2017 From: glenn.becker at gmail.com (Glenn Becker) Date: Mon, 18 Sep 2017 10:49:29 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> Message-ID: OK. I will try again. For what it is worth, the machine I tried building it on has 16 gig o RAM. Granted it's an older core i5 processor. :/ Still, curious. On Mon, Sep 18, 2017 at 10:18 AM, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > I got the same error as Habs on a stable install. > > I was convinced by Matteo and David that webkit2gtk build fine on stable > and current for both arch, BUT it requires a LOT of resources, so i > cancelled my revert and update README instead to make additional SWAP > space if you have small amount of memory installed. > > > > -- > Willy Sudiarto Raharjo > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yth at ythogtha.org Mon Sep 18 14:56:01 2017 From: yth at ythogtha.org (Ythogtha) Date: Mon, 18 Sep 2017 16:56:01 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> Message-ID: <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> > > I got the same error as Habs on a stable install. > > I was convinced by Matteo and David that webkit2gtk build fine on stable > and current for both arch, BUT it requires a LOT of resources, so i > cancelled my revert and update README instead to make additional SWAP > space if you have small amount of memory installed. After the package is created, the temporary build directory takes 1.1Gb. It's not that big, but it is also true that the build takes up a lot of resources during compilation. My computer only has 8Gb of RAM. Maybe using multiple jobs may be a problem, I use -j2, and my computer is on its knees (or chips, or circuits, don't know... ^^) when building, but it builds fine. -- Arnaud From glenn.becker at gmail.com Mon Sep 18 14:59:49 2017 From: glenn.becker at gmail.com (Glenn Becker) Date: Mon, 18 Sep 2017 10:59:49 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> Message-ID: I would be okay with doing other stuff while compiling but this thing [infamously? I've Googled and found lots of complaints] tales a loong time. I ain't rich, so the referenced box is my 'new' laptop, and it gives me a little chill when I check in on the cmake % done notifications and have to stifle yells of "ONLY X PERCENT??" :( On Mon, Sep 18, 2017 at 10:56 AM, Ythogtha wrote: > > > I got the same error as Habs on a stable install. > > > > I was convinced by Matteo and David that webkit2gtk build fine on stable > > and current for both arch, BUT it requires a LOT of resources, so i > > cancelled my revert and update README instead to make additional SWAP > > space if you have small amount of memory installed. > > After the package is created, the temporary build directory takes > 1.1Gb. > It's not that big, but it is also true that the build takes up a lot of > resources during compilation. > My computer only has 8Gb of RAM. Maybe using multiple jobs may be a > problem, I use -j2, and my computer is on its knees (or chips, or circuits, > don't know... ^^) when building, but it builds fine. > > -- > Arnaud > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jgraha8 at gmail.com Mon Sep 18 15:02:48 2017 From: jgraha8 at gmail.com (Jason Graham) Date: Mon, 18 Sep 2017 11:02:48 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> Message-ID: On Mon, Sep 18, 2017 at 10:56 AM, Ythogtha wrote: > > > I got the same error as Habs on a stable install. > > > > I was convinced by Matteo and David that webkit2gtk build fine on stable > > and current for both arch, BUT it requires a LOT of resources, so i > > cancelled my revert and update README instead to make additional SWAP > > space if you have small amount of memory installed. > > After the package is created, the temporary build directory takes > 1.1Gb. > It's not that big, but it is also true that the build takes up a lot of > resources during compilation. > My computer only has 8Gb of RAM. Maybe using multiple jobs may be a > problem, I use -j2, and my computer is on its knees (or chips, or circuits, > don't know... ^^) when building, but it builds fine. > > > I had a similar experience. I first tried with -j8 on a VM and the compilation finished (or at least the cmake progress showed 100%) but it didn't proceed from there. There were 4Gb of ram allocated to this VM so I suppose it was resource constrained based on other folks' findings. It stalled for quite some time (~30min) before I killed the job. So I tried again with -j1 and it failed in the same location has Habs. Best, Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From gen-bch at useyouresp.org.uk Mon Sep 18 16:20:21 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Mon, 18 Sep 2017 17:20:21 +0100 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> Message-ID: <20170918172021.021fbd76@dv6920ea.localdomain> On Mon, 18 Sep 2017 11:02:48 -0400 Jason Graham wrote: > On Mon, Sep 18, 2017 at 10:56 AM, Ythogtha wrote: > > > > > I got the same error as Habs on a stable install. > > > > > > I was convinced by Matteo and David that webkit2gtk build fine on > > > stable and current for both arch, BUT it requires a LOT of > > > resources, so i cancelled my revert and update README instead to > > > make additional SWAP space if you have small amount of memory > > > installed. > > > > After the package is created, the temporary build directory > > takes 1.1Gb. > > It's not that big, but it is also true that the build takes up a > > lot of resources during compilation. > > My computer only has 8Gb of RAM. Maybe using multiple jobs > > may be a problem, I use -j2, and my computer is on its knees (or > > chips, or circuits, don't know... ^^) when building, but it builds > > fine. > > > > > > > > I had a similar experience. I first tried with -j8 on a VM and the > compilation finished (or at least the cmake progress showed 100%) but > it didn't proceed from there. There were 4Gb of ram allocated to this > VM so I suppose it was resource constrained based on other folks' > findings. It stalled for quite some time (~30min) before I killed the > job. > > So I tried again with -j1 and it failed in the same location has Habs. > > Best, > Jason Ive started the build off again after clearing it out. As I said, I'm simple minded ;-) so please forgive me, but it puzzles me that the error message is related to space - is that disk resource and,or ram resources ...and more over, why would the previous version build fine on the exact same machine _without issue_ but not this updated version...what is it doing different I wonder (all said rhetorically speaking). I will see what happens in the early hours :-) Thanks again everyone Habs From kenneth.t.chan at gmail.com Mon Sep 18 19:33:29 2017 From: kenneth.t.chan at gmail.com (Kenneth Chan) Date: Mon, 18 Sep 2017 19:33:29 +0000 Subject: [Slackbuilds-users] Leiningen build for sale In-Reply-To: References: <15e8bc164eb.fa74c6a4379242.3242709454828709831@member.fsf.org> Message-ID: Yumm... I'd love to take it please. On Sun, 17 Sep 2017 at 04:31 Fernando Lopez wrote: > ill wait till it is cheaper... thanks... > > On Sep 16, 2017 11:35 AM, "Ryan P.C. McQuen" > wrote: > >> Somehow I missed this one when giving up all my builds. Whoever wants it >> can have for $0.00. >> >> >> -Ryan >> [ryanpcmcquen.org] >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> >> _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gen-bch at useyouresp.org.uk Mon Sep 18 19:52:07 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Mon, 18 Sep 2017 20:52:07 +0100 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170918172021.021fbd76@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> Message-ID: <20170918205207.68073915@dv6920ea.localdomain> On Mon, 18 Sep 2017 17:20:21 +0100 Habs wrote: > On Mon, 18 Sep 2017 11:02:48 -0400 > Jason Graham wrote: > > > On Mon, Sep 18, 2017 at 10:56 AM, Ythogtha wrote: > > > > > > > I got the same error as Habs on a stable install. > > > > > > > > I was convinced by Matteo and David that webkit2gtk build fine > > > > on stable and current for both arch, BUT it requires a LOT of > > > > resources, so i cancelled my revert and update README instead to > > > > make additional SWAP space if you have small amount of memory > > > > installed. > > > > > > After the package is created, the temporary build > > > directory takes 1.1Gb. > > > It's not that big, but it is also true that the build takes up a > > > lot of resources during compilation. > > > My computer only has 8Gb of RAM. Maybe using multiple jobs > > > may be a problem, I use -j2, and my computer is on its knees (or > > > chips, or circuits, don't know... ^^) when building, but it builds > > > fine. > > > > > > > > > > > > > I had a similar experience. I first tried with -j8 on a VM and the > > compilation finished (or at least the cmake progress showed 100%) > > but it didn't proceed from there. There were 4Gb of ram allocated > > to this VM so I suppose it was resource constrained based on other > > folks' findings. It stalled for quite some time (~30min) before I > > killed the job. > > > > So I tried again with -j1 and it failed in the same location has > > Habs. > > > > Best, > > Jason > > Ive started the build off again after clearing it out. > As I said, I'm simple minded ;-) so please forgive me, but it puzzles > me that the error message is related to space - is that disk resource > and,or ram resources ...and more over, why would the previous version > build fine on the exact same machine _without issue_ but not this > updated version...what is it doing different I wonder (all said > rhetorically speaking). > > I will see what happens in the early hours :-) > > Thanks again everyone > Habs Well, it failed again - both machines (one Intel one AMD tower) - as detailed previously. They were doing nothing else other than building this. The machines are by no means gutsy, but still...4Gb RAM, 500Gb disk space etc. Swap wasnt overly affected from what I could see, which just leaves memory etc ...why would that cause it to conk I dunno. If it is a resources issue for building, producing the error at the same place each time, then it seems like its getting to the point of needing a Cray computer to do this. Ridiculous. :-) From reading other posts, I will have a go with the -j switch and see what gives, but it seems remote. Not sure what else to do, or I can do. The previous version builds fine, so I can use that and not upgrade any more, until I understand what's going on (hmmm). Thank you, good night (as it is for me) to all. Habs --- [ 76%] Building CXX object Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o In file included from /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp:21:0: /tmp/SBo/webkitgtk-2.18.0/Source/WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h:23:40: fatal error: WebCore/HysteresisActivity.h: No such file or directory compilation terminated. Source/WebCore/CMakeFiles/WebCore.dir/build.make:51125: recipe for target 'Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o' failed make[2]: *** [Source/WebCore/CMakeFiles/WebCore.dir/platform/graphics/cairo/BackingStoreBackendCairoImpl.cpp.o] Error 1 CMakeFiles/Makefile2:1065: recipe for target 'Source/WebCore/CMakeFiles/WebCore.dir/all' failed make[1]: *** [Source/WebCore/CMakeFiles/WebCore.dir/all] Error 2 Makefile:149: recipe for target 'all' failed make: *** [all] Error 2 --- From jgraha8 at gmail.com Mon Sep 18 21:49:53 2017 From: jgraha8 at gmail.com (Jason Graham) Date: Mon, 18 Sep 2017 17:49:53 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170918172021.021fbd76@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> Message-ID: On Mon, Sep 18, 2017 at 12:20 PM, Habs wrote: > > Ive started the build off again after clearing it out. > As I said, I'm simple minded ;-) so please forgive me, but it puzzles > me that the error message is related to space - is that disk resource > and,or ram resources ...and more over, why would the previous version > build fine on the exact same machine _without issue_ but not this > updated version...what is it doing different I wonder (all said > rhetorically speaking). > > The missing header file issue between the two -j values is indeed a bit baffling (if it were happening with anything other than -j1 that would seem to make more sense). With regard to the resource requirements for the build, passing -DCMAKE_VERBOSE_MAKEFILE=1 will show how involved building this package is. There are at least 100 different include directories used during compilation of each file so header files are scattered all throughout the source tree. I'd say a similar number of object files for each library it creates during linking which seem to be the most demanding with regard to memory. Best, Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Sep 19 03:44:02 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 19 Sep 2017 10:44:02 +0700 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> Message-ID: On 09/19/2017 04:49 AM, Jason Graham wrote: > On Mon, Sep 18, 2017 at 12:20 PM, Habs wrote: > >> >> Ive started the build off again after clearing it out. >> As I said, I'm simple minded ;-) so please forgive me, but it puzzles >> me that the error message is related to space - is that disk resource >> and,or ram resources ...and more over, why would the previous version >> build fine on the exact same machine _without issue_ but not this >> updated version...what is it doing different I wonder (all said >> rhetorically speaking). >> >> > The missing header file issue between the two -j values is indeed a bit > baffling (if it were happening with anything other than -j1 that would seem > to make more sense). > > With regard to the resource requirements for the build, passing > -DCMAKE_VERBOSE_MAKEFILE=1 will show how involved building this package is. > There are at least 100 different include directories used during > compilation of each file so header files are scattered all throughout the > source tree. I'd say a similar number of object files for each library it > creates during linking which seem to be the most demanding with regard to > memory. Just a short FYI that i'm able to build webkit2gtk on my Slackware64-14.2 VM with 1 vCPU and 2 GB of RAM with 10 additional swap space (total of 12 GB) using commands that Ponce stated in LQ thread fallocate -l 10G /temp-swap chmod 0600 /temp-swap mkswap /temp-swap swapon /temp-swap webkit2gtk: MD5SUM check for webkitgtk-2.18.0.tar.xz ... OK Building package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK Installing package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK free -h total used free shared buff/cache available Mem: 1.9G 22M 123M 4K 1.8G 1.6G Swap: 12G 22M 12G -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From matteo.bernardini at gmail.com Tue Sep 19 08:56:16 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 19 Sep 2017 10:56:16 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170918205207.68073915@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170918205207.68073915@dv6920ea.localdomain> Message-ID: 2017-09-18 21:52 GMT+02:00 Habs : > From reading other posts, I will have a go with the -j switch and see > what gives, but it seems remote. Not sure what else to do, or I can > do. The previous version builds fine, so I can use that and not > upgrade any more, until I understand what's going on (hmmm). I was able to reproduce your error when building webkit2gtk with a single make job (the default), while it went fine if two jobs or more were used. you can try adding a line like this to the SlackBuild (so that it defaults to use at least two jobs) --- webkit2gtk.SlackBuild.orig 2017-09-16 02:20:30.000000000 +0200 +++ webkit2gtk.SlackBuild 2017-09-19 10:54:00.493180645 +0200 @@ -55,6 +55,8 @@ LIBDIRSUFFIX="" fi +MAKEFLAGS=${MAKEFLAGS:--j2} + set -eu rm -rf $PKG or you can try also passing a MAKEFLAGS=-j${n} (with n >= 2) to the SlackBuild to use multiple make jobs. Matteo From gen-bch at useyouresp.org.uk Tue Sep 19 08:59:11 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Tue, 19 Sep 2017 09:59:11 +0100 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> Message-ID: <20170919095911.5386372d@dv6920ea.localdomain> On Tue, 19 Sep 2017 10:44:02 +0700 Willy Sudiarto Raharjo wrote: > On 09/19/2017 04:49 AM, Jason Graham wrote: > > On Mon, Sep 18, 2017 at 12:20 PM, Habs > > wrote: > >> > >> Ive started the build off again after clearing it out. > >> As I said, I'm simple minded ;-) so please forgive me, but it > >> puzzles me that the error message is related to space - is that > >> disk resource and,or ram resources ...and more over, why would > >> the previous version build fine on the exact same machine _without > >> issue_ but not this updated version...what is it doing different I > >> wonder (all said rhetorically speaking). > >> > >> > > The missing header file issue between the two -j values is indeed a > > bit baffling (if it were happening with anything other than -j1 > > that would seem to make more sense). > > > > With regard to the resource requirements for the build, passing > > -DCMAKE_VERBOSE_MAKEFILE=1 will show how involved building this > > package is. There are at least 100 different include directories > > used during compilation of each file so header files are scattered > > all throughout the source tree. I'd say a similar number of object > > files for each library it creates during linking which seem to be > > the most demanding with regard to memory. > > Just a short FYI that i'm able to build webkit2gtk on my > Slackware64-14.2 VM with 1 vCPU and 2 GB of RAM with 10 additional > swap space (total of 12 GB) using commands that Ponce stated in LQ > thread > > fallocate -l 10G /temp-swap > chmod 0600 /temp-swap > mkswap /temp-swap > swapon /temp-swap > > webkit2gtk: > MD5SUM check for webkitgtk-2.18.0.tar.xz ... OK > Building package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK > Installing package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK > > free -h > total used free shared buff/cache available > Mem: 1.9G 22M 123M 4K 1.8G 1.6G > Swap: 12G 22M 12G > > Can I just have clarified please re: > fallocate -l 10G /temp-swap > chmod 0600 /temp-swap > mkswap /temp-swap > swapon /temp-swap ... that be done without messing up the swap already setup (in fstab) i.e. it is a temporary allocation for the build process that can then be deallocated etc (hopefully you get what I mean) ? The machine I'm using already has 8b swap (I believe) and 4Gb RAM. I will track down the thread on LQ and try it out...but it is getting a bit silly when a 4GB quad-core machine that is doing nothing else, struggles or conks out due to resource issues etc :-) Thank you again all for the input...maybe I am learning something too! Habs From gen-bch at useyouresp.org.uk Tue Sep 19 09:01:02 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Tue, 19 Sep 2017 10:01:02 +0100 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170918205207.68073915@dv6920ea.localdomain> Message-ID: <20170919100102.7431d4d4@dv6920ea.localdomain> On Tue, 19 Sep 2017 10:56:16 +0200 Matteo Bernardini wrote: > 2017-09-18 21:52 GMT+02:00 Habs : > > From reading other posts, I will have a go with the -j switch and > > see what gives, but it seems remote. Not sure what else to do, or > > I can do. The previous version builds fine, so I can use that and > > not upgrade any more, until I understand what's going on (hmmm). > > I was able to reproduce your error when building webkit2gtk with a > single make job (the default), while it went fine if two jobs or more > were used. > > you can try adding a line like this to the SlackBuild (so that it > defaults to use at least two jobs) > > --- webkit2gtk.SlackBuild.orig 2017-09-16 02:20:30.000000000 +0200 > +++ webkit2gtk.SlackBuild 2017-09-19 10:54:00.493180645 +0200 > @@ -55,6 +55,8 @@ > LIBDIRSUFFIX="" > fi > > +MAKEFLAGS=${MAKEFLAGS:--j2} > + > set -eu > > rm -rf $PKG > > or you can try also passing a MAKEFLAGS=-j${n} (with n >= 2) to the > SlackBuild to use multiple make jobs. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > Thank you will give a few things a try until it builds or I give up due to lack of brain capacity (and frustration) :-) From ekinakoglu at gmail.com Tue Sep 19 09:03:24 2017 From: ekinakoglu at gmail.com (Ekin Akoglu) Date: Tue, 19 Sep 2017 12:03:24 +0300 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170919095911.5386372d@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> Message-ID: Hi, I don't think this is a resource issue. My system is with 16 GB RAM and 8 GB swap space, however, the build fails at 76% with a similar error (sorry but I didn't record the exact error so that I could post here). Best, Ekin On 19/09/17 11:59, Habs wrote: > On Tue, 19 Sep 2017 10:44:02 +0700 > Willy Sudiarto Raharjo wrote: > >> On 09/19/2017 04:49 AM, Jason Graham wrote: >>> On Mon, Sep 18, 2017 at 12:20 PM, Habs >>> wrote: >>>> Ive started the build off again after clearing it out. >>>> As I said, I'm simple minded ;-) so please forgive me, but it >>>> puzzles me that the error message is related to space - is that >>>> disk resource and,or ram resources ...and more over, why would >>>> the previous version build fine on the exact same machine _without >>>> issue_ but not this updated version...what is it doing different I >>>> wonder (all said rhetorically speaking). >>>> >>>> >>> The missing header file issue between the two -j values is indeed a >>> bit baffling (if it were happening with anything other than -j1 >>> that would seem to make more sense). >>> >>> With regard to the resource requirements for the build, passing >>> -DCMAKE_VERBOSE_MAKEFILE=1 will show how involved building this >>> package is. There are at least 100 different include directories >>> used during compilation of each file so header files are scattered >>> all throughout the source tree. I'd say a similar number of object >>> files for each library it creates during linking which seem to be >>> the most demanding with regard to memory. >> Just a short FYI that i'm able to build webkit2gtk on my >> Slackware64-14.2 VM with 1 vCPU and 2 GB of RAM with 10 additional >> swap space (total of 12 GB) using commands that Ponce stated in LQ >> thread >> >> fallocate -l 10G /temp-swap >> chmod 0600 /temp-swap >> mkswap /temp-swap >> swapon /temp-swap >> >> webkit2gtk: >> MD5SUM check for webkitgtk-2.18.0.tar.xz ... OK >> Building package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK >> Installing package webkit2gtk-2.18.0-x86_64-1_SBo.tgz ... OK >> >> free -h >> total used free shared buff/cache available >> Mem: 1.9G 22M 123M 4K 1.8G 1.6G >> Swap: 12G 22M 12G >> >> > Can I just have clarified please re: > >> fallocate -l 10G /temp-swap >> chmod 0600 /temp-swap >> mkswap /temp-swap >> swapon /temp-swap > ... that be done without messing up the swap already setup (in fstab) > i.e. it is a temporary allocation for the build process that can then > be deallocated etc (hopefully you get what I mean) ? > > The machine I'm using already has 8b swap (I believe) and 4Gb RAM. > I will track down the thread on LQ and try it out...but it is getting a > bit silly when a 4GB quad-core machine that is doing nothing else, > struggles or conks out due to resource issues etc :-) > > > Thank you again all for the input...maybe I am learning something too! > > Habs > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From matteo.bernardini at gmail.com Tue Sep 19 09:11:35 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 19 Sep 2017 11:11:35 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170919095911.5386372d@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> Message-ID: 2017-09-19 10:59 GMT+02:00 Habs : > Can I just have clarified please re: > >> fallocate -l 10G /temp-swap >> chmod 0600 /temp-swap >> mkswap /temp-swap >> swapon /temp-swap > > ... that be done without messing up the swap already setup (in fstab) > i.e. it is a temporary allocation for the build process that can then > be deallocated etc (hopefully you get what I mean) ? yes: you can disable it and delete the additional swap file after you don't need it anymore with swapoff /temp-swap rm /temp-swap Matteo From atelszewski at gmail.com Tue Sep 19 11:17:30 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Tue, 19 Sep 2017 13:17:30 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> Message-ID: <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> Hi, I've just built for testing (I don't need the package) with slackrepo: env MAKEFLAGS=' -j4 ' nice -n 5 bash ./webkit2gtk.SlackBuild Build time 187 min, peak load 6.69, peak memory 3674M, peak tmp 1222M Built ok: webkit2gtk-2.18.0-x86_64-1_sbo.txz -- Best regards, Andrzej Telszewski From jgraha8 at gmail.com Tue Sep 19 12:23:06 2017 From: jgraha8 at gmail.com (Jason Graham) Date: Tue, 19 Sep 2017 08:23:06 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> Message-ID: On Tue, Sep 19, 2017 at 7:17 AM, Andrzej Telszewski wrote: > Hi, > > I've just built for testing (I don't need the package) with slackrepo: > > env MAKEFLAGS=' -j4 ' nice -n 5 bash ./webkit2gtk.SlackBuild > Build time 187 min, peak load 6.69, peak memory 3674M, peak tmp 1222M > Built ok: webkit2gtk-2.18.0-x86_64-1_sbo.txz > > Thanks Andrzej for testing and capturing resource info. This confirms my suspicions with regard to resource requirements for the build; they aren't insignificant. Best, J -------------- next part -------------- An HTML attachment was scrubbed... URL: From gen-bch at useyouresp.org.uk Tue Sep 19 13:48:49 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Tue, 19 Sep 2017 14:48:49 +0100 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> Message-ID: <20170919144849.19b2eae9@dv6920ea.localdomain> On Tue, 19 Sep 2017 13:17:30 +0200 Andrzej Telszewski wrote: > Hi, > > I've just built for testing (I don't need the package) with slackrepo: > > env MAKEFLAGS=' -j4 ' nice -n 5 bash ./webkit2gtk.SlackBuild > Build time 187 min, peak load 6.69, peak memory 3674M, peak tmp 1222M > Built ok: webkit2gtk-2.18.0-x86_64-1_sbo.txz > That did the trick. \m/ Before messing with swap, I tried this first and the machine romped through it with no [resource] issues that I could see. Thank you for this ... and to all for the other contributions. I've realised I know very little comparatively :-) Regards Habs From markus.ka.rinne at gmail.com Tue Sep 19 17:18:52 2017 From: markus.ka.rinne at gmail.com (Markus Rinne) Date: Tue, 19 Sep 2017 20:18:52 +0300 Subject: [Slackbuilds-users] [PATCH] *.SlackBuild: Remove trailing whitespace Message-ID: <20170919171852.GA1978@tursas.sidaroth.foo> --- haskell-template.SlackBuild | 2 +- python-template.SlackBuild | 2 +- rubygem-template.SlackBuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/haskell-template.SlackBuild b/haskell-template.SlackBuild index 929e79b..75527a0 100644 --- a/haskell-template.SlackBuild +++ b/haskell-template.SlackBuild @@ -86,7 +86,7 @@ else LIBDIRSUFFIX="" fi -set -e +set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT diff --git a/python-template.SlackBuild b/python-template.SlackBuild index 409a36f..0472cd6 100644 --- a/python-template.SlackBuild +++ b/python-template.SlackBuild @@ -82,7 +82,7 @@ else LIBDIRSUFFIX="" fi -set -e +set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT diff --git a/rubygem-template.SlackBuild b/rubygem-template.SlackBuild index 154ff2b..1c5543f 100644 --- a/rubygem-template.SlackBuild +++ b/rubygem-template.SlackBuild @@ -84,7 +84,7 @@ else LIBDIRSUFFIX="" fi -set -e +set -e rm -rf $PKG mkdir -p $TMP $PKG $OUTPUT -- 2.14.1 From willysr at slackbuilds.org Tue Sep 19 21:01:54 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Sep 2017 04:01:54 +0700 Subject: [Slackbuilds-users] [PATCH] *.SlackBuild: Remove trailing whitespace In-Reply-To: <20170919171852.GA1978@tursas.sidaroth.foo> References: <20170919171852.GA1978@tursas.sidaroth.foo> Message-ID: <053a6ebd-c69e-9e5e-5ee4-9b44d4f0e693@slackbuilds.org> > --- > haskell-template.SlackBuild | 2 +- > python-template.SlackBuild | 2 +- > rubygem-template.SlackBuild | 2 +- > 3 files changed, 3 insertions(+), 3 deletions(-) commit 1097046640ababf67aa65fd4f3f1adcce1b776b5 (HEAD -> master, origin/master, origin/HEAD) Author: Markus Rinne Date: Wed Sep 20 03:59:38 2017 +0700 *.SlackBuild: Remove Whitespaces. Signed-off-by: Willy Sudiarto Raharjo Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jbernts at broadpark.no Tue Sep 19 21:12:27 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 19 Sep 2017 23:12:27 +0200 Subject: [Slackbuilds-users] hub package Message-ID: <20170919211227.GC1903@jbsupah> The google-go-lang dependency installs fine, but the hub package errors out with: hub: MD5SUM check for v2.2.9.tar.gz ... FAILED! Expected: 0469114903f572fe5290d46a0911288e Found: 44b74ff789df3f0d197401b25ddb165d Searching source repository. MD5SUM check for v2.2.9.tar.gz ... OK Error occurred with build. Please check the log. Anything to check here? Jostein From jbernts at broadpark.no Tue Sep 19 21:31:48 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 19 Sep 2017 23:31:48 +0200 Subject: [Slackbuilds-users] hub package In-Reply-To: <20170919211227.GC1903@jbsupah> References: <20170919211227.GC1903@jbsupah> Message-ID: <20170919213148.GD1903@jbsupah> On 19.09.17,23:12, Jostein Berntsen wrote: > The google-go-lang dependency installs fine, but the hub package errors > out with: > > hub: > MD5SUM check for v2.2.9.tar.gz ... FAILED! > Expected: 0469114903f572fe5290d46a0911288e > Found: 44b74ff789df3f0d197401b25ddb165d > Searching source repository. > MD5SUM check for v2.2.9.tar.gz ... OK > Error occurred with build. Please check the log. > > Anything to check here? > > There are also errors like these: hub-2.2.9/version/version.go /tmp/go/src/github.com/github/hub/github/config_decoder.go:7:2: cannot find package "github.com/BurntSushi/toml" in any of: /usr/src/github.com/BurntSushi/toml (from $GOROOT) /tmp/go/src/github.com/BurntSushi/toml (from $GOPATH) /tmp/go/src/github.com/github/hub/commands/updater.go:21:2: cannot find package "github.com/inconshreveable/go-update" in any of: /usr/src/github.com/inconshreveable/go-update (from $GOROOT) /tmp/go/src/github.com/inconshreveable/go-update (from $GOPATH) Jostein From jbernts at broadpark.no Tue Sep 19 21:34:48 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 19 Sep 2017 23:34:48 +0200 Subject: [Slackbuilds-users] sbopkg in screen Message-ID: <20170919213448.GE1903@jbsupah> sbopkg behaves a bit strangely in screen with black background, fields and some strange characters. I have tested it in konsole and yakuake. It works like expected outside screen. Anyone seen this? Jostein From willysr at slackbuilds.org Tue Sep 19 21:42:12 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Sep 2017 04:42:12 +0700 Subject: [Slackbuilds-users] hub package In-Reply-To: <20170919213148.GD1903@jbsupah> References: <20170919211227.GC1903@jbsupah> <20170919213148.GD1903@jbsupah> Message-ID: <97db1d18-44a8-d0d1-a01a-8678fae172af@slackbuilds.org> >> The google-go-lang dependency installs fine, but the hub package errors >> out with: >> >> hub: >> MD5SUM check for v2.2.9.tar.gz ... FAILED! >> Expected: 0469114903f572fe5290d46a0911288e >> Found: 44b74ff789df3f0d197401b25ddb165d >> Searching source repository. >> MD5SUM check for v2.2.9.tar.gz ... OK >> Error occurred with build. Please check the log. >> >> Anything to check here? Thanks for spotting it has been fixed in my branch most likely it's due to GIT changes over their OS. > There are also errors like these: > > hub-2.2.9/version/version.go > /tmp/go/src/github.com/github/hub/github/config_decoder.go:7:2: cannot find package "github.com/BurntSushi/toml" in any of: > /usr/src/github.com/BurntSushi/toml (from $GOROOT) > /tmp/go/src/github.com/BurntSushi/toml (from $GOPATH) > /tmp/go/src/github.com/github/hub/commands/updater.go:21:2: cannot find package "github.com/inconshreveable/go-update" in any of: > /usr/src/github.com/inconshreveable/go-update (from $GOROOT) > /tmp/go/src/github.com/inconshreveable/go-update (from $GOPATH) Use "su -" instead of just "su" also, if you have just installed google-go-lang, you need to logout first and re-login -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Sep 19 21:44:06 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 20 Sep 2017 04:44:06 +0700 Subject: [Slackbuilds-users] sbopkg in screen In-Reply-To: <20170919213448.GE1903@jbsupah> References: <20170919213448.GE1903@jbsupah> Message-ID: <6a7d2281-fdcb-20fd-a132-8090544aef7e@slackbuilds.org> > sbopkg behaves a bit strangely in screen with black background, fields > and some strange characters. I have tested it in konsole and yakuake. It > works like expected outside screen. Anyone seen this? please post sbopkg's bug in sbopkg's mailing list or in sbopkg's issue tracker in github (https://github.com/sbopkg/sbopkg/issues). Use screenshot if possible to describe what you get in your system. This is SlackBuilds' mailing list Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jbernts at broadpark.no Tue Sep 19 21:54:42 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 19 Sep 2017 23:54:42 +0200 Subject: [Slackbuilds-users] sbopkg in screen In-Reply-To: <6a7d2281-fdcb-20fd-a132-8090544aef7e@slackbuilds.org> References: <20170919213448.GE1903@jbsupah> <6a7d2281-fdcb-20fd-a132-8090544aef7e@slackbuilds.org> Message-ID: <20170919215442.GF1903@jbsupah> On 20.09.17,04:44, Willy Sudiarto Raharjo wrote: > > sbopkg behaves a bit strangely in screen with black background, fields > > and some strange characters. I have tested it in konsole and yakuake. It > > works like expected outside screen. Anyone seen this? > > please post sbopkg's bug in sbopkg's mailing list or in sbopkg's issue > tracker in github (https://github.com/sbopkg/sbopkg/issues). Use > screenshot if possible to describe what you get in your system. > > This is SlackBuilds' mailing list > > Thanks > Seems like I sent it twice to this list. Please delete. I have sent it to the sbopkg-users list now. Jostein From jbernts at broadpark.no Tue Sep 19 21:53:20 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Tue, 19 Sep 2017 23:53:20 +0200 Subject: [Slackbuilds-users] sbopkg in screen Message-ID: <20170919215320.GA1897@jbsupah> sbopkg behaves a bit strangely in screen with black background, fields and some strange characters. I have tested it in konsole and yakuake. It works like expected outside screen. Anyone seen this? I have attached a couple of screenshot. Jostein -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-yakuake.png Type: image/png Size: 103526 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: sbopkg-konsole.png Type: image/png Size: 98832 bytes Desc: not available URL: From lspencer31 at cfl.rr.com Tue Sep 19 22:15:07 2017 From: lspencer31 at cfl.rr.com (Lenard Spencer) Date: Tue, 19 Sep 2017 18:15:07 -0400 Subject: [Slackbuilds-users] sbopkg in screen Message-ID: <0l8dqvitkacqea03psh3tj5t.1505859089712@email.lge.com> I think it had something to do with Slackware from LANG=C to LANG=en_US a while back. ?Try 'LANG=C sbopkg' and see what that does (worked for me). ------ Original message------From: Jostein BerntsenDate: Tue, Sep 19, 2017 17:54To: slackbuilds-users at slackbuilds.org;Cc: Subject:[Slackbuilds-users] sbopkg in screen sbopkg behaves a bit strangely in screen with black background, fields and some strange characters. I have tested it in konsole and yakuake. It works like expected outside screen. Anyone seen this? I have attached a couple of screenshot. Jostein -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Wed Sep 20 12:02:15 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 20 Sep 2017 14:02:15 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170919144849.19b2eae9@dv6920ea.localdomain> References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> Message-ID: Hi, I think webkit2gtk README should not be updated with the adding more swap space tip. -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Wed Sep 20 13:26:33 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 20 Sep 2017 15:26:33 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> Message-ID: 2017-09-20 14:02 GMT+02:00 Andrzej Telszewski : > I think webkit2gtk README should not be updated with the adding more swap > space tip. it has been just a suggestion and in Willy's case it has been useful, but I agree that it's something that maybe would fit better between the FAQs (as it applies to multiple SlackBuilds). Matteo From yalhcru at gmail.com Wed Sep 20 14:08:53 2017 From: yalhcru at gmail.com (B Watson) Date: Wed, 20 Sep 2017 10:08:53 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <1c01ecf7-5889-e74d-98fa-0b6a43cd7ccc@slackbuilds.org> <20170918115902.fc2971e1435249504378c61b@ythogtha.org> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> Message-ID: On 9/20/17, Matteo Bernardini wrote: > 2017-09-20 14:02 GMT+02:00 Andrzej Telszewski : >> I think webkit2gtk README should not be updated with the adding more swap >> space tip. > > it has been just a suggestion and in Willy's case it has been useful, > but I agree that it's something that maybe would fit better between > the FAQs (as it applies to multiple SlackBuilds). Why can't it be mentioned in both places, the README as specific advice for someone about to build webkit2gtk, and the FAQ as general advice for multiple builds? The issue here seems to be that it takes several hours for the build to fail, and it took all the people on this thread several days to 100% diagnose the problem. That represents enough computer cycles and human labour that it's worth passing on to the next guy who might need to know it. An extra sentence in a README costs nothing, and might save someone some time and headache. From atelszewski at gmail.com Wed Sep 20 14:24:30 2017 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Wed, 20 Sep 2017 16:24:30 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: References: <20170917195901.6152f465@dv6920ea.localdomain> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> Message-ID: <229158ac-8963-b7b5-ab72-908a6bc4809e@gmail.com> On 20/09/17 16:08, B Watson wrote: > On 9/20/17, Matteo Bernardini wrote: >> 2017-09-20 14:02 GMT+02:00 Andrzej Telszewski: >>> I think webkit2gtk README should not be updated with the adding more swap >>> space tip. >> it has been just a suggestion and in Willy's case it has been useful, >> but I agree that it's something that maybe would fit better between >> the FAQs (as it applies to multiple SlackBuilds). > Why can't it be mentioned in both places, the README as specific advice > for someone about to build webkit2gtk, and the FAQ as general advice > for multiple builds? > > The issue here seems to be that it takes several hours for the build > to fail, and it took all the people on this thread several days to 100% > diagnose the problem. That represents enough computer cycles and human > labour that it's worth passing on to the next guy who might need to know > it. An extra sentence in a README costs nothing, and might save someone > some time and headache. But was that an actual solution? That is, I might not have noticed that, but was increasing the swap space the solution? I built it fine in 5GB VM, using 4 make jobs. And we have many more scripts that might be hungry, like qt5 or LibreOffice. I'm not sure if they all should be updated this way. -- Best regards, Andrzej Telszewski From yth at ythogtha.org Wed Sep 20 14:42:08 2017 From: yth at ythogtha.org (Ythogtha) Date: Wed, 20 Sep 2017 16:42:08 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <229158ac-8963-b7b5-ab72-908a6bc4809e@gmail.com> References: <20170917195901.6152f465@dv6920ea.localdomain> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> <229158ac-8963-b7b5-ab72-908a6bc4809e@gmail.com> Message-ID: <20170920164208.5c936818376513a4918cd0de@ythogtha.org> > > An extra sentence in a README costs nothing, and might save someone > > some time and headache. > > But was that an actual solution? > > That is, I might not have noticed that, but was increasing the swap > space the solution? > > I built it fine in 5GB VM, using 4 make jobs. > > And we have many more scripts that might be hungry, like qt5 or LibreOffice. > > I'm not sure if they all should be updated this way. That's the question... Wasn't the solution to use multiple jobs ? -j2 or higher does the trick, but if -j1 it fails ? It seems to me that was the real solution wasn't it ? And couldn't this be handled in the SlackBuild directly ? Checking for NUMJOBS and setting 2 jobs if there are only one asked for, regardless of user preferences. -- Yth From johannes at schoepfer.info Wed Sep 20 14:47:07 2017 From: johannes at schoepfer.info (=?UTF-8?Q?Johannes_Sch=c3=b6pfer?=) Date: Wed, 20 Sep 2017 16:47:07 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <20170920164208.5c936818376513a4918cd0de@ythogtha.org> References: <20170917195901.6152f465@dv6920ea.localdomain> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> <229158ac-8963-b7b5-ab72-908a6bc4809e@gmail.com> <20170920164208.5c936818376513a4918cd0de@ythogtha.org> Message-ID: <5acf44b7-a99e-7cfc-0b95-7c89f5749dcf@schoepfer.info> On 20.09.2017 16:42, Ythogtha wrote: >>> An extra sentence in a README costs nothing, and might save someone >>> some time and headache. >> >> But was that an actual solution? >> >> That is, I might not have noticed that, but was increasing the swap >> space the solution? >> >> I built it fine in 5GB VM, using 4 make jobs. >> >> And we have many more scripts that might be hungry, like qt5 or LibreOffice. >> >> I'm not sure if they all should be updated this way. > > That's the question... > Wasn't the solution to use multiple jobs ? > -j2 or higher does the trick, but if -j1 it fails ? > > It seems to me that was the real solution wasn't it ? > > And couldn't this be handled in the SlackBuild directly ? Isn't that already done? https://git.slackbuilds.org/slackbuilds/commit/?id=e9952e154 Johannes From yalhcru at gmail.com Wed Sep 20 14:57:14 2017 From: yalhcru at gmail.com (B Watson) Date: Wed, 20 Sep 2017 10:57:14 -0400 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <229158ac-8963-b7b5-ab72-908a6bc4809e@gmail.com> References: <20170917195901.6152f465@dv6920ea.localdomain> <20170918111926.4aacb666@dv6920ea.localdomain> <4BCD2EEA-3CCD-458C-A3B5-CA5C01CEEDE9@ythogtha.org> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> <229158ac-8963-b7b5-ab72-908a6bc4809e@gmail.com> Message-ID: On 9/20/17, Andrzej Telszewski wrote: > And we have many more scripts that might be hungry, like qt5 or > LibreOffice. > > I'm not sure if they all should be updated this way. Up to the individual maintainers. If it were up for voting, I'd vote yes. What possible reason is there for not wanting to do this? (I honestly can't see one. Even laziness shouldn't apply, we're talking about adding one line to a file that already exists) Anything that takes many hours to complete, and stands a chance of failing because of missing information on the builder's part (like "this needs 2GB of RAM"), information that the maintainer *has* but hasn't bothered to share with the builder... that leads to wasted time and resources, and annoys the builder (who is your audience... the person you're ultimately doing this for in the first place). Me, I put this in mame's README: "This build requires around 2GB of storage in /tmp (or whatever you set TMP to in the environment)." ...to be fully honest, I put it there because I myself will forget that fact, and try to build it on my laptop where /tmp is a tmpfs that never grows past 1GB. After shooting myself in the foot several times, I've put a warning label on the gun (which will also benefit others). I also went to some trouble with the mame build to reduce the build time and amount of memory used, by using the ld.gold linker. qt5 I think already does this (autodetects it). LibreOffice might not benefit much from it since it's got so much Java code... haven't looked at webkit2gtk, maybe it could benefit from this too? (possibly as simple as adding LDFLAGS="-fuse-ld=gold" to the make command) From yth at ythogtha.org Wed Sep 20 14:59:22 2017 From: yth at ythogtha.org (Ythogtha) Date: Wed, 20 Sep 2017 16:59:22 +0200 Subject: [Slackbuilds-users] webkit2gtk build problems In-Reply-To: <5acf44b7-a99e-7cfc-0b95-7c89f5749dcf@schoepfer.info> References: <20170917195901.6152f465@dv6920ea.localdomain> <20170918165601.201aecf6aab52c69a2293d2c@ythogtha.org> <20170918172021.021fbd76@dv6920ea.localdomain> <20170919095911.5386372d@dv6920ea.localdomain> <162879cc-04ad-ffc6-79e9-d5f76af5ddfe@gmail.com> <20170919144849.19b2eae9@dv6920ea.localdomain> <229158ac-8963-b7b5-ab72-908a6bc4809e@gmail.com> <20170920164208.5c936818376513a4918cd0de@ythogtha.org> <5acf44b7-a99e-7cfc-0b95-7c89f5749dcf@schoepfer.info> Message-ID: <20170920165922.b94230e04b0c6bdb041e7b3d@ythogtha.org> > On 20.09.2017 16:42, Ythogtha wrote: > >>> An extra sentence in a README costs nothing, and might save someone > >>> some time and headache. > >> > >> But was that an actual solution? > >> > >> That is, I might not have noticed that, but was increasing the swap > >> space the solution? > >> > >> I built it fine in 5GB VM, using 4 make jobs. > >> > >> And we have many more scripts that might be hungry, like qt5 or LibreOffice. > >> > >> I'm not sure if they all should be updated this way. > > > > That's the question... > > Wasn't the solution to use multiple jobs ? > > -j2 or higher does the trick, but if -j1 it fails ? > > > > It seems to me that was the real solution wasn't it ? > > > > And couldn't this be handled in the SlackBuild directly ? > > Isn't that already done? > https://git.slackbuilds.org/slackbuilds/commit/?id=e9952e154 > > Johannes Short answer : yes. So is there any other build problem there ? Doesn't setting -j2 solve every build problem ? -- Arnaud From chris.willing at iinet.net.au Thu Sep 21 00:43:18 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Thu, 21 Sep 2017 10:43:18 +1000 Subject: [Slackbuilds-users] Use ld.gold? Message-ID: Following B Watson's remark in another thread: > I also went to some trouble with the mame build to reduce the build > time and amount of memory used, by using the ld.gold linker. qt5 I think > already does this (autodetects it). LibreOffice might not benefit much > from it since it's got so much Java code... haven't looked at webkit2gtk, > maybe it could benefit from this too? (possibly as simple as adding > LDFLAGS="-fuse-ld=gold" to the make command) I just tried building LibreOffice with LDFLAGS="-fuse-ld=gold". The build log notes: checking for explicit LDFLAGS... -fuse-ld=gold but apart from that, there's no indication that ld.gold was used and the build time was not spectacularly different compared with an otherwise identical build done on Sep 2 - it's actually somewhat slower with ld.gold. Sep 2 build: real 90m51.395s user 493m40.305s sys 29m55.917s Sep 21 build (with ld.gold) real 92m57.284s user 498m55.163s sys 34m4.537s That's not a great result, high amount of java code notwithstanding. I'll use the newly built version for a while to look for any runtime problems and, if there aren't any, I'll add an option to use ld.gold to the SlackBuild at the next update - it would be interesting to hear of other results. chris From didier at slint.fr Thu Sep 21 09:37:03 2017 From: didier at slint.fr (Didier Spaier) Date: Thu, 21 Sep 2017 11:37:03 +0200 Subject: [Slackbuilds-users] Heads-up for py3cairo Message-ID: <47114506-cfb7-c2d3-ed06-e215744135b7@slint.fr> Hello, A need of py3cairo version >= 11 as dep leaded me to the new website: https://github.com/pygobject/pycairo The releases are at: https://github.com/pygobject/pycairo/releases This is an information, not an upgrade request. I just can say that I had no issue so far with version 15.2, and that patches are no more needed to build it. BCC-ing the maintainer (Hello Bojan!) Have a good day, Didier From bocke at slackware-srbija.org Thu Sep 21 09:52:14 2017 From: bocke at slackware-srbija.org (Bojan =?UTF-8?B?UG9wb3ZpxIc=?=) Date: Thu, 21 Sep 2017 11:52:14 +0200 Subject: [Slackbuilds-users] Heads-up for py3cairo In-Reply-To: <47114506-cfb7-c2d3-ed06-e215744135b7@slint.fr> References: <47114506-cfb7-c2d3-ed06-e215744135b7@slint.fr> Message-ID: <20170921115214.0c683bea@malac.universe.local> Hi, Thanx for letting me know. To be honest I currently don't use anything that requires Python 3 (and hence py3cairo) so I'll gladly put it up for adoption. If there is no interest, I'll correct it when I get around. Or you can send me your corrections and I will apply them after testing out in a VM. But wait a bit in case somebody is interested in adopting it. Thanx, Bojan. On Thu, 21 Sep 2017 11:37:03 +0200 Didier Spaier wrote: > Hello, > > A need of py3cairo version >= 11 as dep leaded me to the new website: > https://github.com/pygobject/pycairo > The releases are at: > https://github.com/pygobject/pycairo/releases > > This is an information, not an upgrade request. > I just can say that I had no issue so far with version 15.2, and that > patches are no more needed to build it. > > BCC-ing the maintainer (Hello Bojan!) > > Have a good day, > > Didier > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From yalhcru at gmail.com Thu Sep 21 14:48:35 2017 From: yalhcru at gmail.com (B Watson) Date: Thu, 21 Sep 2017 10:48:35 -0400 Subject: [Slackbuilds-users] Use ld.gold? In-Reply-To: References: Message-ID: On 9/20/17, Christoph Willing wrote: > > I just tried building LibreOffice with LDFLAGS="-fuse-ld=gold". The > build log notes: > checking for explicit LDFLAGS... -fuse-ld=gold > but apart from that, there's no indication that ld.gold was used and the > build time was not spectacularly different compared with an otherwise > identical build done on Sep 2 - it's actually somewhat slower with ld.gold. It's possible that LibreOffice's build process already checks for ld.gold and uses it if found. qt5 does that. You can find out by running the build like this: strace -f -ostrace.out ./LibreOffice.SlackBuild ...which will take maybe twice as long to run as usual (strace overhead). Then "grep gold strace.out". Try this with & without LDFLAGS="-fuse-ld=gold" set in the environment. Other than speeding up the build, there's no real reason to offer a ld.gold option. It's only faster at link time, the LibreOffice binary won't run any faster (or any differently at all) from one built without ld.gold. What I've found is that ld.gold speeds up those builds where there's a *huge* link process (usually at the end), where the build process looks like it's stalled (but it's eating 100% of one CPU core) and the currently running command has *many* object files: gcc -o whatever this.o that.o theother.o <100 or more .o files and/or .a files> The command might be g++ or ld instead of gcc, of course. With mame, that one command would take over 2 hours to complete with the regular ld linker... and finishes in seconds with ld.gold. From dpross1100 at msn.com Sat Sep 23 03:09:14 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 23 Sep 2017 03:09:14 +0000 Subject: [Slackbuilds-users] opencv md5sum error Message-ID: Hi, Trying to install opencv, I'm getting an md5sum mismatch for opencv-3.1.0.tar.gz. The .info file says the md5sum should be: 70e1dd07f0aa06606f1bc0e3fa15abd3 but I'm getting: a0669e22172dfc3225835b180744c9f0 I'm afraid to ignore the md5sum error and continue with the build without knowing the reason for it. Did github change something behind the scenes like seems to happen sometimes? Maybe just a packaging oversight? Thanks, Dan From chris.willing at iinet.net.au Sat Sep 23 04:24:24 2017 From: chris.willing at iinet.net.au (Christoph Willing) Date: Sat, 23 Sep 2017 14:24:24 +1000 Subject: [Slackbuilds-users] opencv md5sum error In-Reply-To: References: Message-ID: <0074c5d5-7a27-04de-2155-d7f10e2c81f5@iinet.net.au> On 23/09/17 13:09, Daniel Prosser wrote: > Hi, > > Trying to install opencv, I'm getting an md5sum mismatch for > opencv-3.1.0.tar.gz. The .info file says the md5sum should be: > > 70e1dd07f0aa06606f1bc0e3fa15abd3 > That is the correct one for my locally cached copy. > but I'm getting: > > a0669e22172dfc3225835b180744c9f0 Yes, looks like it has changed. > > I'm afraid to ignore the md5sum error and continue with the build > without knowing the reason for it. Did github change something behind > the scenes like seems to happen sometimes? Yes, well .... It turns out that our expectation that Github tarballs never change is not well founded. There is some discussion about it here: https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745 chris From bocke at mycity.rs Sat Sep 23 14:40:17 2017 From: bocke at mycity.rs (Bojan =?UTF-8?B?UG9wb3ZpxIc=?=) Date: Sat, 23 Sep 2017 16:40:17 +0200 Subject: [Slackbuilds-users] Heads-up for py3cairo In-Reply-To: <47114506-cfb7-c2d3-ed06-e215744135b7@slint.fr> References: <47114506-cfb7-c2d3-ed06-e215744135b7@slint.fr> Message-ID: <20170923164017.2d28333e@malac.universe.local> Hi! Good news: Py3 just hit Slack Current. I'll update py3cairo soon, but the next update will have to wait until we see what Python 3 packages will be part of the next Slackware release. Bojan. On Thu, 21 Sep 2017 11:37:03 +0200 Didier Spaier wrote: > Hello, > > A need of py3cairo version >= 11 as dep leaded me to the new website: > https://github.com/pygobject/pycairo > The releases are at: > https://github.com/pygobject/pycairo/releases > > This is an information, not an upgrade request. > I just can say that I had no issue so far with version 15.2, and that > patches are no more needed to build it. > > BCC-ing the maintainer (Hello Bojan!) > > Have a good day, > > Didier > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From idlemoor at slackbuilds.org Sat Sep 23 16:06:17 2017 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 23 Sep 2017 17:06:17 +0100 Subject: [Slackbuilds-users] Updates - 20170923.1 Message-ID: <8ba0cfb6-b91d-33e3-ab8f-23a70f16d3d5@slackbuilds.org> Hello everybody, This week's public update is a bit later than usual, because of our personal schedules :) Please note that because of changes at Github, some md5sums may be out of date. Don't worry if you find one, but please let us know via the mailing list, so that we can fix them. For anybody who has been using tiled-qt, this has now been renamed to 'tiled' (still in the development/ category). Thanks to everybody who contributed! -D. Sat Sep 23 15:38:17 UTC 2017 academic/OpenFOAM: Added (computational fluid dynamics). academic/dakota: Added (optimization toolkit). audio/pulseaudio-ctl: Updated for version 1.66. desktop/anki: Updated for version 2.0.47. desktop/areao43-icon-theme: Fixed SlackBuild. desktop/lxappearance-obconf: Use gtk+3 by default. desktop/lxappearance: Use GTK+3. desktop/oomox: Added (gtk theme designer). development/gcc-d: Added (D support for GCC). development/hexedit: New maintainer + switch to i586. development/hub: Update MD5SUM. development/jupyter-ipywidgets: Updated for version 7.0.1. development/npm2tgz: Updated for version 1.3.4. development/obnc: Added (Oberon-07 Compiler). development/pkgconf: Updated for version 1.3.9. development/rtags: Added (indexer with Emacs integration). development/tiled-qt: Removed (renamed to tiled). development/tiled: Added (Tiled map editor), renamed from tiled-qt. development/zulu-openjdk9: Added (Open Implementation of JDK). games/0ad-data: Updated for version 0.0.22. games/0ad: Updated for version 0.0.22. games/SLADE: Updated for version 3.1.1.5. games/bstone: Updated for version 1.1.9. games/crispy-doom: Updated for version 4.2. games/freeciv: Updated for version 2.6.0_beta1. games/pioneer: Updated for version 20170827. gis/geojson: Updated for version 2.3.0. gis/opencpn: Updated for version 4.8.0. gis/osm2pgsql: Updated for version 0.94.0_RC1. graphics/fbida: Updated for version 2.14, add fbipdf manpage. libraries/SDL2: Updated for version 2.0.6. libraries/efivar: Updated for version 32. libraries/libconfig: Updated for version 1.6. libraries/libvirt-python: Updated for version 3.7.0. libraries/libvirt: Updated for version 3.7.0. libraries/obnc-libstd: Added (Standard Library for OBNC). libraries/opencv: Updated md5sum and DOWNLOAD url libraries/protobuf-c: Updated for version 1.3.0. libraries/webkit2gtk: Fix build issue on single job. multimedia/MuseScore: Updated for version 2.1.0. multimedia/QMPlay2: Updated for version 17.09.16. multimedia/lightspark: Updated for version 2017.09.17_823fdba. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 61.0. multimedia/youtube-viewer: Updated for version 3.2.9. network/Icecat: Added (GNU version of the Firefox browser). network/msmtp: Updated for version 1.6.6. network/newsboat: Added (RSS console feed reader). network/owncloud-client: Changed deps, please see README. network/vivaldi: Updated for version 1.12.955.36. office/MasterPDFEditor: Updated for version 4.3.50. office/notmuch: Updated for version 0.25.1. office/pdfstudio12: Update md5sums. office/taskjuggler: Changed deps. office/timetrap: Updated for version 1.15.1. perl/perl-linux-desktop-files: Updated for version 0.20. python/parso: Added (Python parser). python/path.py: Updated for version 10.4. python/psutil: Updated for version 5.3.1 python/pymongo: Updated for version 3.5.1. python/python3-jedi: Updated for version 0.11.0. python/python3-parso: Added (Python parser). python/python3-six: Updated for version 1.11.0. python/six: Updated for version 1.11.0 ruby/rubygem-mail: Added (Ruby Mail handler). ruby/rubygem-mime-types-data: Added (MIME media type registry). ruby/rubygem-mime-types: Updated for version 3.1. ruby/rubygem-term-ansicolor: Added (ANSI escape sequence library). ruby/rubygem-tins: Added (tools library in Ruby). ruby/sequel4: Added (Database toolkit for Ruby, legacy version). ruby/sequel: Updated for version 5.0.0. system/agedu: Updated for version 20170831.fc6b2b5. system/brasero: Updated for version 3.12.2. system/evhz: Added (show mouse refresh rate). system/fzf: Updated for version 0.17.0_2. system/inxi: Updated for version 2.3.39. system/isdct: Updated for version 3.0.7. system/kbfs: Updated for version 1.0.31_20170917003451. system/keybase: Updated for version 1.0.30. system/kitchen-sync: Updated for version 0.56. system/netdata: Updated for version 1.8.0. system/nvme-cli: Updated for version 1.4. system/openrc-services: Updated for version 20170917. system/openrc: Updated for version 0.31.2. system/phoronix-test-suite: Updated for version 7.4.0. system/pspg: Added (psql pager). system/thin-provisioning-tools: Added (manage LVM2 targets). system/xen: XSA 231-235 update. +--------------------------+ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From dpross1100 at msn.com Sat Sep 23 17:29:28 2017 From: dpross1100 at msn.com (Daniel Prosser) Date: Sat, 23 Sep 2017 17:29:28 +0000 Subject: [Slackbuilds-users] opencv md5sum error In-Reply-To: <0074c5d5-7a27-04de-2155-d7f10e2c81f5@iinet.net.au> References: <0074c5d5-7a27-04de-2155-d7f10e2c81f5@iinet.net.au> Message-ID: Alright, thanks for the explanation. I went ahead and built it anyway, and it seems to be fine. Dan On Sat, Sep 23, 2017 at 02:24:24PM +1000, Christoph Willing wrote: > On 23/09/17 13:09, Daniel Prosser wrote: > > Hi, > > > > Trying to install opencv, I'm getting an md5sum mismatch for > > opencv-3.1.0.tar.gz. The .info file says the md5sum should be: > > > > 70e1dd07f0aa06606f1bc0e3fa15abd3 > > > That is the correct one for my locally cached copy. > > > > but I'm getting: > > > > a0669e22172dfc3225835b180744c9f0 > Yes, looks like it has changed. > > > > > I'm afraid to ignore the md5sum error and continue with the build > > without knowing the reason for it. Did github change something behind > > the scenes like seems to happen sometimes? > > Yes, well .... > > It turns out that our expectation that Github tarballs never change is > not well founded. There is some discussion about it here: > https://github.com/libgit2/libgit2/issues/4343#issuecomment-328631745 > > > chris > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From duncan_roe at optusnet.com.au Sun Sep 24 09:18:33 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 24 Sep 2017 19:18:33 +1000 Subject: [Slackbuilds-users] Mail archives seem to be unavailable Message-ID: <20170924091833.GA26969@dimstar.local.net> Hi Admins, I tried to access the mail archives via the URL in the FAQ but Firefox couldn't connect. On testing I found: - lists.slackbuilds.org answers pings - telnet to lists.slackbuilds.org port https gets connection refused - telnet to lists.slackbuilds.org port http gets connection refused HTH, Cheers ... Duncan. -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html From duncan_roe at optusnet.com.au Sun Sep 24 09:29:01 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Sun, 24 Sep 2017 19:29:01 +1000 Subject: [Slackbuilds-users] Updates - 20170923.1 In-Reply-To: <8ba0cfb6-b91d-33e3-ab8f-23a70f16d3d5@slackbuilds.org> References: <8ba0cfb6-b91d-33e3-ab8f-23a70f16d3d5@slackbuilds.org> Message-ID: <20170924092901.GB26969@dimstar.local.net> Hi Dave, On Sat, Sep 23, 2017 at 05:06:17PM +0100, David Spencer wrote: > Hello everybody, > > This week's public update is a bit later than usual, because of our > personal schedules :) > ... > libraries/webkit2gtk: Fix build issue on single job. ... It seems you need this: diff --git a/libraries/webkit2gtk/webkit2gtk.SlackBuild b/libraries/webkit2gtk/webkit2gtk.SlackBuild index 57e4f2e..2f7c42e 100644 --- a/libraries/webkit2gtk/webkit2gtk.SlackBuild +++ b/libraries/webkit2gtk/webkit2gtk.SlackBuild @@ -57,7 +57,7 @@ fi # This is needed to fix build issue on single make job # Thanks to ponce for investigating this issue. -MAKEFLAGS=${MAKEFLAGS:--j2} +export MAKEFLAGS=${MAKEFLAGS:--j2} set -eu ------------------ My build just failed after 18 hrs. It only ever ran 1 cc1plus. With the patch, it's running 2 of them, Cheers ... Duncan. From sbolokanov at abv.bg Sun Sep 24 09:53:21 2017 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGKINCR0L7Qu9C+0LrQsNC90L7QstGK?=) Date: Sun, 24 Sep 2017 12:53:21 +0300 (EEST) Subject: [Slackbuilds-users] libtorrent-rasterbar build error on last Slackware-current? Message-ID: <662763807.578614.1506246801103.JavaMail.apache@nm53.abv.bg> Anybody else having issues building libtorrent-rasterbar after last Slackware64-current update? It seems issue is with boost. Any hints? [CODE] In file included from ../include/libtorrent/version.hpp:36:0, from version.cpp:33: ../include/libtorrent/export.hpp:37:12: fatal error: boost/config/select_compiler_config.hpp: No such file or directory # include ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make[1]: *** [Makefile:890: version.lo] Error 1 make[1]: Leaving directory '/tmp/SBo/libtorrent-rasterbar-1.0.11/src' make: *** [Makefile:622: all-recursive] Error 1 [/CODE] -- ?????? ?. ?????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Sep 24 10:01:00 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 24 Sep 2017 17:01:00 +0700 Subject: [Slackbuilds-users] libtorrent-rasterbar build error on last Slackware-current? In-Reply-To: <662763807.578614.1506246801103.JavaMail.apache@nm53.abv.bg> References: <662763807.578614.1506246801103.JavaMail.apache@nm53.abv.bg> Message-ID: > Anybody else having issues building libtorrent-rasterbar after last Slackware64-current update? Hi SBo doesn't officially support -current Use this thread in LQ instead https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From sbolokanov at abv.bg Sun Sep 24 10:16:23 2017 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGKINCR0L7Qu9C+0LrQsNC90L7QstGK?=) Date: Sun, 24 Sep 2017 13:16:23 +0300 (EEST) Subject: [Slackbuilds-users] libtorrent-rasterbar build error on last Slackware-current? In-Reply-To: References: <662763807.578614.1506246801103.JavaMail.apache@nm53.abv.bg> Message-ID: <1908931574.579334.1506248183673.JavaMail.apache@nm53.abv.bg> Aha! Looks like file has been moved root at sevar:~# locate select_compiler_config.hpp /usr/include/CLucene/ext/boost/config/select_compiler_config.hpp /usr/include/boost/config/detail/select_compiler_config.hpp Made link for this and it build fine: root at sevar:~# ln -s /usr/include/boost/config/detail/select_compiler_config.hpp /usr/include/boost/config/select_compiler_config.hpp ln -s /usr/include/boost/config/detail/select_platform_config.hpp /usr/include/boost/config/select_platform_config.hpp -- ?????? ?. ?????????? >-------- ?????????? ????? -------- >??: Willy Sudiarto Raharjo willysr at slackbuilds.org >???????: Re: [Slackbuilds-users] libtorrent-rasterbar build error on last Slackware-current? >??: slackbuilds-users at slackbuilds.org >????????? ??: 24.09.2017 13:01 > Anybody else having issues building libtorrent-rasterbar after last Slackware64-current update? Hi SBo doesn't officially support -current Use this thread in LQ instead https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ -- Willy Sudiarto Raharjo -------------- next part -------------- An HTML attachment was scrubbed... URL: From rob0 at slackbuilds.org Sun Sep 24 12:32:54 2017 From: rob0 at slackbuilds.org (Rob McGee) Date: Sun, 24 Sep 2017 07:32:54 -0500 Subject: [Slackbuilds-users] Mail archives seem to be unavailable In-Reply-To: <20170924091833.GA26969@dimstar.local.net> References: <20170924091833.GA26969@dimstar.local.net> Message-ID: <20170924123253.GX2027@harrier.slackbuilds.org> On Sun, Sep 24, 2017 at 07:18:33PM +1000, Duncan Roe wrote: > I tried to access the mail archives via the URL in the FAQ but > Firefox couldn't connect. On testing I found: > > - lists.slackbuilds.org answers pings > - telnet to lists.slackbuilds.org port https gets connection refused > - telnet to lists.slackbuilds.org port http gets connection refused Yep, thanks for the notice. For some reason yet unknown, httpd wasn't running. It's started now, and IWFM. -- Rob McGee - /dev/rob0 - rob0 at slackbuilds.org From gen-bch at useyouresp.org.uk Sun Sep 24 13:11:36 2017 From: gen-bch at useyouresp.org.uk (Habs) Date: Sun, 24 Sep 2017 14:11:36 +0100 Subject: [Slackbuilds-users] Mail archives seem to be unavailable In-Reply-To: <20170924123253.GX2027@harrier.slackbuilds.org> References: <20170924091833.GA26969@dimstar.local.net> <20170924123253.GX2027@harrier.slackbuilds.org> Message-ID: <20170924141136.205fed8a@dv6920ea.localdomain> On Sun, 24 Sep 2017 07:32:54 -0500 Rob McGee wrote: > > Yep, thanks for the notice. For some reason yet unknown, httpd > wasn't running. It's started now, and IWFM. i know im not young anymore...but what is IWFM. i had to look it up! im going for 'it works for me' ? ;-) From jbernts at broadpark.no Sun Sep 24 15:11:44 2017 From: jbernts at broadpark.no (Jostein Berntsen) Date: Sun, 24 Sep 2017 17:11:44 +0200 Subject: [Slackbuilds-users] hub package In-Reply-To: <97db1d18-44a8-d0d1-a01a-8678fae172af@slackbuilds.org> References: <20170919211227.GC1903@jbsupah> <20170919213148.GD1903@jbsupah> <97db1d18-44a8-d0d1-a01a-8678fae172af@slackbuilds.org> Message-ID: <20170924151144.GB32439@jbsupah> On 20.09.17,04:42, Willy Sudiarto Raharjo wrote: > >> The google-go-lang dependency installs fine, but the hub package errors > >> out with: > >> > >> hub: > >> MD5SUM check for v2.2.9.tar.gz ... FAILED! > >> Expected: 0469114903f572fe5290d46a0911288e > >> Found: 44b74ff789df3f0d197401b25ddb165d > >> Searching source repository. > >> MD5SUM check for v2.2.9.tar.gz ... OK > >> Error occurred with build. Please check the log. > >> > >> Anything to check here? > > Thanks for spotting > it has been fixed in my branch > most likely it's due to GIT changes over their OS. > > > > There are also errors like these: > > > > hub-2.2.9/version/version.go > > /tmp/go/src/github.com/github/hub/github/config_decoder.go:7:2: cannot find package "github.com/BurntSushi/toml" in any of: > > /usr/src/github.com/BurntSushi/toml (from $GOROOT) > > /tmp/go/src/github.com/BurntSushi/toml (from $GOPATH) > > /tmp/go/src/github.com/github/hub/commands/updater.go:21:2: cannot find package "github.com/inconshreveable/go-update" in any of: > > /usr/src/github.com/inconshreveable/go-update (from $GOROOT) > > /tmp/go/src/github.com/inconshreveable/go-update (from $GOPATH) > > Use "su -" instead of just "su" > also, if you have just installed google-go-lang, you need to logout > first and re-login > This worked fine now, thanks. Jostein From lspencer31 at cfl.rr.com Sun Sep 24 17:05:16 2017 From: lspencer31 at cfl.rr.com (Lenard Spencer) Date: Sun, 24 Sep 2017 13:05:16 -0400 Subject: [Slackbuilds-users] PokerTH revisited in 14.2 and -current Message-ID: With all the new goodies added and upgraded in -current, I had to go back and rebuild a few things.? Things were going good until I got to PokerTH, when it bombed out on an ambiguous 'advance()' call into the boost library, much like the earlier 'ifstream()' and 'ofstream()' calls did.? The advance() call is only made once, so here is a simple patch to fix that: diff -Naur PokerTH-1.1.1-src/src/gui/qt/gametable/gametableimpl.cpp PokerTH-1.1.1-src.new/src/gui/qt/gametable/gametableimpl.cpp --- PokerTH-1.1.1-src.orig/src/gui/qt/gametable/gametableimpl.cpp 2014-01-10 16:18:20.788643125 -0500 +++ PokerTH-1.1.1-src/src/gui/qt/gametable/gametableimpl.cpp 2017-09-24 12:20:07.042925701 -0400 @@ -3859,7 +3859,7 @@ ???? int playerCount = static_cast(seatList->size()); ???? if (id < playerCount) { ???? ??? PlayerListIterator pos = seatList->begin(); -??? ??? advance(pos, id); +??? ??? std::advance(pos, id); myStartWindow->getSession()->startVoteKickPlayer((*pos)->getMyUniqueID()); ???? } ?} I have tested it for quite a while, and so far I have found no problems with it.? Even invoking pokerth from a terminal window doesn't produce any squawks. As for 14.2 stable, the 'std-ifstream-and-std-ofstream.patch is necessary because of the change in the python imaging library (from the old PIL in 14.1 to pillow in 14.2).? So that patch should probably incorporated into 14.2 and master. I have cc'ed the maintainer, and if it is OK with him I would like to take over maintainership of it. From matteo.bernardini at gmail.com Sun Sep 24 17:40:49 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 24 Sep 2017 19:40:49 +0200 Subject: [Slackbuilds-users] PokerTH revisited in 14.2 and -current In-Reply-To: References: Message-ID: 2017-09-24 19:05 GMT+02:00 Lenard Spencer : > With all the new goodies added and upgraded in -current, I had to go back > and rebuild a few things. Things were going good until I got to PokerTH, > when it bombed out on an ambiguous 'advance()' call into the boost library, > much like the earlier 'ifstream()' and 'ofstream()' calls did. The > advance() call is only made once, so here is a simple patch to fix that: > > diff -Naur PokerTH-1.1.1-src/src/gui/qt/gametable/gametableimpl.cpp > PokerTH-1.1.1-src.new/src/gui/qt/gametable/gametableimpl.cpp > --- PokerTH-1.1.1-src.orig/src/gui/qt/gametable/gametableimpl.cpp 2014-01-10 > 16:18:20.788643125 -0500 > +++ PokerTH-1.1.1-src/src/gui/qt/gametable/gametableimpl.cpp 2017-09-24 > 12:20:07.042925701 -0400 > @@ -3859,7 +3859,7 @@ > int playerCount = static_cast(seatList->size()); > if (id < playerCount) { > PlayerListIterator pos = seatList->begin(); > - advance(pos, id); > + std::advance(pos, id); > myStartWindow->getSession()->startVoteKickPlayer((*pos)->getMyUniqueID()); > } > } > > I have tested it for quite a while, and so far I have found no problems with > it. Even invoking pokerth from a terminal window doesn't produce any > squawks. hi Lenard, I was about to submit the exact same fix on the unofficial repository for current: I took the patch from Gentoo and tested it too. Matteo From lspencer31 at cfl.rr.com Sun Sep 24 18:33:54 2017 From: lspencer31 at cfl.rr.com (Lenard Spencer) Date: Sun, 24 Sep 2017 14:33:54 -0400 Subject: [Slackbuilds-users] PokerTH revisited in 14.2 and -current Message-ID: Sounds good. ?I searched for it but didn't find anything. ------ Original message------From: Matteo BernardiniDate: Sun, Sep 24, 2017 13:40To: SlackBuilds.org Users List;Cc: Subject:Re: [Slackbuilds-users] PokerTH revisited in 14.2 and -current 2017-09-24 19:05 GMT+02:00 Lenard Spencer : > With all the new goodies added and upgraded in -current, I had to go back > and rebuild a few things. Things were going good until I got to PokerTH, > when it bombed out on an ambiguous 'advance()' call into the boost library, > much like the earlier 'ifstream()' and 'ofstream()' calls did. The > advance() call is only made once, so here is a simple patch to fix that: > > diff -Naur PokerTH-1.1.1-src/src/gui/qt/gametable/gametableimpl.cpp > PokerTH-1.1.1-src.new/src/gui/qt/gametable/gametableimpl.cpp > --- PokerTH-1.1.1-src.orig/src/gui/qt/gametable/gametableimpl.cpp 2014-01-10 > 16:18:20.788643125 -0500 > +++ PokerTH-1.1.1-src/src/gui/qt/gametable/gametableimpl.cpp 2017-09-24 > 12:20:07.042925701 -0400 > @@ -3859,7 +3859,7 @@ > int playerCount = static_cast(seatList->size()); > if (id < playerCount) { > PlayerListIterator pos = seatList->begin(); > - advance(pos, id); > + std::advance(pos, id); > myStartWindow->getSession()->startVoteKickPlayer((*pos)->getMyUniqueID()); > } > } > > I have tested it for quite a while, and so far I have found no problems with > it. Even invoking pokerth from a terminal window doesn't produce any > squawks. hi Lenard, I was about to submit the exact same fix on the unofficial repository for current: I took the patch from Gentoo and tested it too. Matteo _______________________________________________ SlackBuilds-users mailing list SlackBuilds-users at slackbuilds.org https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sun Sep 24 19:05:38 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 24 Sep 2017 21:05:38 +0200 Subject: [Slackbuilds-users] PokerTH revisited in 14.2 and -current In-Reply-To: References: Message-ID: 2017-09-24 20:33 GMT+02:00 Lenard Spencer : > Sounds good. I searched for it but didn't find anything. https://gitweb.gentoo.org/repo/gentoo.git/commit/games-board/pokerth?id=1f6eeb3ae3f00b88fa38398613a63d08422e320f From matteo.bernardini at gmail.com Sun Sep 24 19:11:19 2017 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 24 Sep 2017 21:11:19 +0200 Subject: [Slackbuilds-users] PokerTH revisited in 14.2 and -current In-Reply-To: References: Message-ID: 2017-09-24 21:05 GMT+02:00 Matteo Bernardini : > 2017-09-24 20:33 GMT+02:00 Lenard Spencer : >> Sounds good. I searched for it but didn't find anything. > > https://gitweb.gentoo.org/repo/gentoo.git/commit/games-board/pokerth?id=1f6eeb3ae3f00b88fa38398613a63d08422e320f BTW, it needs some other patches to build on current http://cgit.ponce.cc/slackbuilds/commit/?h=pokerth From sombragris at sombragris.org Sun Sep 24 19:50:32 2017 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sun, 24 Sep 2017 15:50:32 -0400 Subject: [Slackbuilds-users] GeoIP: MD5 problem Message-ID: Hi there. I use -current but I think this applies to any Slackbuilds user. After the latest updates, GeoIP shows a mistmatched MD5 sum: =================== HTTP request sent, awaiting response... 200 OK Length: 658262 (643K) [application/x-gzip] Saving to: ?GeoIP.dat.gz? GeoIP.dat.gz 100%[===================>] 642.83K 92.2KB/s in 6.9s 2017-09-24 15:43:56 (93.5 KB/s) - ?GeoIP.dat.gz? saved [658262/658262] Found GeoIP.dat.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for GeoIP.dat.gz ... OK Found GeoIPv6.dat.gz in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for GeoIPv6.dat.gz ... FAILED! Expected: 8335c482e83fe6a45312418c69a3d28d Found: 7bb92ae5ebb8b61c3aeac247657c6c8f Do you want to use the downloaded GeoIP source: GeoIPv6.dat.gz in /var/cache/sbopkg? =================== Thanks, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From baildon.research at googlemail.com Sun Sep 24 20:17:02 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 24 Sep 2017 21:17:02 +0100 Subject: [Slackbuilds-users] GeoIP: MD5 problem In-Reply-To: References: Message-ID: > After the latest updates, GeoIP shows a mistmatched MD5 sum: Hi, I added this to the README because this has been causing problems for people: "If you are using sbopkg and you have md5sum errors, you need to delete your old data files from the cache and try again." Thanks -D. From baildon.research at googlemail.com Sun Sep 24 21:43:23 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sun, 24 Sep 2017 22:43:23 +0100 Subject: [Slackbuilds-users] Github md5sums Message-ID: As Daniel and Christoph discussed last week, some md5sums have changed on downloads from Github (even though the contents of the downloads are exactly the same). The ones we know about at the moment are listed below, they are all corrected in my branch and will go into the next public update. Until then, don't worry, nobody is trying to hack you. Well, maybe they are, but not with bad github downloads :) If you find any more, you can help us by replying here. Thanks -D. academic/bppsuite desktop/awoken-icon-theme development/atom development/extra-cmake-modules development/fsharp development/lighttable development/mono-addins development/qbs development/referenceassemblies-pcl development/rstudio-desktop games/OpenXcom games/commandergenius games/doomretro games/hlsdk games/mame games/openclonk games/openlierox graphics/meshlab graphics/povray graphics/qcad libraries/cpprestsdk libraries/kashmir libraries/libgit2 libraries/libopenshot-audio libraries/yaml-cpp misc/protobuf3 multimedia/OpenPHT multimedia/kodi multimedia/miro multimedia/plex-home-theater network/luakit office/texworks system/afdko From duncan_roe at optusnet.com.au Mon Sep 25 01:55:51 2017 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Mon, 25 Sep 2017 11:55:51 +1000 Subject: [Slackbuilds-users] Updates - 20170923.1 In-Reply-To: <20170924092901.GB26969@dimstar.local.net> References: <8ba0cfb6-b91d-33e3-ab8f-23a70f16d3d5@slackbuilds.org> <20170924092901.GB26969@dimstar.local.net> Message-ID: <20170925015551.GA3333@dimstar.local.net> Hi Willy, I just noticed you're the maintainer ;) On Sun, Sep 24, 2017 at 07:29:01PM +1000, Duncan Roe wrote: > Hi Dave, > > On Sat, Sep 23, 2017 at 05:06:17PM +0100, David Spencer wrote: > > Hello everybody, > > > > This week's public update is a bit later than usual, because of our > > personal schedules :) > > > ... > > libraries/webkit2gtk: Fix build issue on single job. > ... > > It seems you need this: > > diff --git a/libraries/webkit2gtk/webkit2gtk.SlackBuild b/libraries/webkit2gtk/webkit2gtk.SlackBuild > index 57e4f2e..2f7c42e 100644 > --- a/libraries/webkit2gtk/webkit2gtk.SlackBuild > +++ b/libraries/webkit2gtk/webkit2gtk.SlackBuild > @@ -57,7 +57,7 @@ fi > > # This is needed to fix build issue on single make job > # Thanks to ponce for investigating this issue. > -MAKEFLAGS=${MAKEFLAGS:--j2} > +export MAKEFLAGS=${MAKEFLAGS:--j2} > > set -eu > > > ------------------ > > My build just failed after 18 hrs. It only ever ran 1 cc1plus. > > With the patch, it's running 2 of them, > > Cheers ... Duncan. My re-build ran to completion with the above patch. However, I do wonder whether "make -j2" is simply masking a bug in the make process. Perhaps you might like to report the failure to upstream. Here's what I found: As Chris Willing noted in https://lists.slackbuilds.org/pipermail/slackbuilds-users/2017-September/019991.html, sources from the tarball #include WebCore/BackingStoreBackendCairoImpl.h whereas the file exists at webkitgtk-2.18.0/Source/WebCore/platform/HysteresisActivity.h. The successful build generates webkitgtk-2.18.0/build/DerivedSources/ForwardingHeaders/WebCore/BackingStoreBackendCairoImpl.h which has the line #include "WebCore/platform/graphics/cairo/BackingStoreBackendCairoImpl.h" (i.e. where the file really is). The single-job make doesn't even get to create the directory webkitgtk-2.18.0/build/DerivedSources/ForwardingHeaders/WebCore/ before failing. Could this indicate an error in the build sequence? Cheers ... Duncan. From fernando.lopezjr at gmail.com Mon Sep 25 02:43:51 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 24 Sep 2017 20:43:51 -0600 Subject: [Slackbuilds-users] what should be the values for this two variables? Message-ID: https://github.com/zeromq/libzmq/blob/master/src/libzmq.pc.in what should be the values for this two variables? prefix=@prefix@ exec_prefix=@exec_prefix@ prefix=/usr exec_prefix=??????? -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From elyk03 at gmail.com Mon Sep 25 03:10:54 2017 From: elyk03 at gmail.com (Kyle Guinn) Date: Sun, 24 Sep 2017 22:10:54 -0500 Subject: [Slackbuilds-users] what should be the values for this two variables? In-Reply-To: References: Message-ID: On 9/24/17, Fernando Lopez wrote: > https://github.com/zeromq/libzmq/blob/master/src/libzmq.pc.in > > what should be the values for this two variables? > > prefix=@prefix@ > exec_prefix=@exec_prefix@ > > prefix=/usr > exec_prefix=??????? The configure script usually sets it to: exec_prefix=${prefix} unless you specify --exec-prefix when running ./configure. -Kyle From vasilysora at posteo.net Mon Sep 25 18:09:02 2017 From: vasilysora at posteo.net (Vasily Sora) Date: Mon, 25 Sep 2017 10:09:02 -0800 Subject: [Slackbuilds-users] Taking a trip to Romania will be afk for a while. In-Reply-To: References: Message-ID: <20170925100902.2969fd4c@darkstar.localhost> Hi everyone, I just wanted to let everyone know I'm going to be afk for a while, but, I'm not abandoning the SlackBuilds I maintain. For the record, I maintain the PaleMoon.SlackBuild, eltclsh and a few others. I'm just wanting to let people know about this in case I seem unreachable. I'll be checking in when I can; but there will certainly be gaps since I will be, like I said, basically afk for a while. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Mon Sep 25 21:51:21 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 25 Sep 2017 14:51:21 -0700 (PDT) Subject: [Slackbuilds-users] fontforge-20170731 has library issue Message-ID: On a fully patched 14.2 system trying to build fontforge-20170731 throws this error: .libs/libgutils_la-gimagereadxpm.o: In function `findnextkey': gimagereadxpm.c:(.text+0x9b): undefined reference to `ff_unicode_utype' .libs/libgutils_la-gimagereadxpm.o: In function `GImageReadXpm': gimagereadxpm.c:(.text+0x4ec): undefined reference to `ff_unicode_utype' .libs/libgutils_la-giohosts.o: In function `_GIO_LookupHost': giohosts.c:(.text+0x4fe): undefined reference to `ff_unicode_utype' collect2: error: ld returned 1 exit status libtool: error: error: relink 'libgutils.la' with the above command before installing it Makefile:1313: recipe for target 'install-libLTLIBRARIES' failed make[3]: *** [install-libLTLIBRARIES] Error 1 make[3]: Leaving directory '/tmp/SBo/fontforge-20170731/gutils' Makefile:1749: recipe for target 'install-am' failed make[2]: *** [install-am] Error 2 make[2]: Leaving directory '/tmp/SBo/fontforge-20170731/gutils' Makefile:1580: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/fontforge-20170731' Makefile:1877: recipe for target 'install' failed make: *** [install] Error 2 Please advise how to fix it. Regards, Rich From rshepard at appl-ecosys.com Mon Sep 25 22:04:14 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 25 Sep 2017 15:04:14 -0700 (PDT) Subject: [Slackbuilds-users] fontforge-20170731 has library issue [RESOLVED] In-Reply-To: References: Message-ID: On Mon, 25 Sep 2017, Rich Shepard wrote: > On a fully patched 14.2 system trying to build fontforge-20170731 throws > this error: Mea culpa! I totally forgot to remove the prior version before building the new one. After removing the old version the new one successfully built. Rich From reedych at ya.ru Tue Sep 26 14:07:59 2017 From: reedych at ya.ru (reedych) Date: Tue, 26 Sep 2017 20:07:59 +0600 Subject: [Slackbuilds-users] Roll back the 0ad script Message-ID: <20170926200759.0871a9840afb8478b40240fd@ya.ru> Hello all. I received a report that package doesn't work (i got segfault also, but i thinked-though that it only my problem). I try to fix it, but now i have not a lot of time. Please, rollback 0ad slackbuild to 0.0.21 version. From bocke at slackware-srbija.org Tue Sep 26 19:27:49 2017 From: bocke at slackware-srbija.org (Bojan =?UTF-8?B?UG9wb3ZpxIc=?=) Date: Tue, 26 Sep 2017 21:27:49 +0200 Subject: [Slackbuilds-users] Heads-up for py3cairo In-Reply-To: <20170923164017.2d28333e@malac.universe.local> References: <47114506-cfb7-c2d3-ed06-e215744135b7@slint.fr> <20170923164017.2d28333e@malac.universe.local> Message-ID: <20170926212707.78afc02a@malac.universe.local> Hi! On Sat, 23 Sep 2017 16:40:17 +0200 Bojan Popovi? wrote: > Good news: Py3 just hit Slack Current. I'll update py3cairo soon, but > the next update will have to wait until we see what Python 3 packages > will be part of the next Slackware release. I just checked it out and Pycairo in current already includes Python 3 version. So the next update might be one of the last if not the last. Cheers, Bojan. From yalhcru at gmail.com Tue Sep 26 20:42:38 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 26 Sep 2017 16:42:38 -0400 Subject: [Slackbuilds-users] Fwd: asl.SlackBuild In-Reply-To: References: Message-ID: Forwarding this to the list, in case the maintainer's monitoring it: ---------- Forwarded message ---------- From: B Watson Date: Thu, 21 Sep 2017 11:19:18 -0400 Subject: asl.SlackBuild To: oleg.chukaev at mail.ru Any chance you'll update this for a later snapshot? The latest is asl-current-142-bld119.tar.bz2, from August 21, 2017. It's about a month old, or 2+ years newer than the version on SBo. Also, the README states: Note: The source downloaded is a snapshot from 20090810. ...but it's actually from 20150525. From willysr at slackbuilds.org Tue Sep 26 20:46:03 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 27 Sep 2017 03:46:03 +0700 Subject: [Slackbuilds-users] Fwd: asl.SlackBuild In-Reply-To: References: Message-ID: > Forwarding this to the list, in case the maintainer's monitoring it: > > ---------- Forwarded message ---------- > From: B Watson > Date: Thu, 21 Sep 2017 11:19:18 -0400 > Subject: asl.SlackBuild > To: oleg.chukaev at mail.ru > > Any chance you'll update this for a later snapshot? The latest is > asl-current-142-bld119.tar.bz2, from August 21, 2017. It's about a month > old, or 2+ years newer than the version on SBo. > > Also, the README states: > > Note: The source downloaded is a snapshot from 20090810. > > ...but it's actually from 20150525. Just FYI, The maintainer hasn't updated this script since 2010 https://git.slackbuilds.org/slackbuilds/log/?qt=grep&q=development%2Fasl If you are interested, please take over -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Wed Sep 27 00:14:19 2017 From: yalhcru at gmail.com (B Watson) Date: Tue, 26 Sep 2017 20:14:19 -0400 Subject: [Slackbuilds-users] Fwd: asl.SlackBuild In-Reply-To: References: Message-ID: On 9/26/17, Willy Sudiarto Raharjo wrote: > > If you are interested, please take over Done. Thanks. From slackbuilds at schoepfer.info Wed Sep 27 06:54:51 2017 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 27 Sep 2017 08:54:51 +0200 Subject: [Slackbuilds-users] i3 Message-ID: Hi, i've submitted an new version of i3. perl-AnyEvent-I3 is now included in the upstream i3-tarball, so please remove https://slackbuilds.org/repository/14.2/perl/perl-AnyEvent-I3/ from SBo, as it's not needed by any other software. Johannes From willysr at slackbuilds.org Wed Sep 27 08:51:51 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 27 Sep 2017 15:51:51 +0700 Subject: [Slackbuilds-users] i3 In-Reply-To: References: Message-ID: > i've submitted an new version of i3. > perl-AnyEvent-I3 is now included in the upstream i3-tarball, so please > remove https://slackbuilds.org/repository/14.2/perl/perl-AnyEvent-I3/ > from SBo, as it's not needed by any other software. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From d.zlatanidis at gmail.com Wed Sep 27 16:15:53 2017 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Wed, 27 Sep 2017 18:15:53 +0200 Subject: [Slackbuilds-users] libwacom checksum error Message-ID: <51f5df62-387a-ba1f-7f48-1eb0097e6a31@gmail.com> Hi, +============================================================================== | MD5SUM check for libwacom-0.26.tar.bz2 [ FAILED ] +============================================================================== | Expected: 00d7f50bc7feda6a01f2b2546f787bc9 | Found: cb530d737c8f2d1023797cf0587b4e05 +============================================================================== -- Dimitris Zlatanidis From baildon.research at googlemail.com Wed Sep 27 20:58:36 2017 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 27 Sep 2017 21:58:36 +0100 Subject: [Slackbuilds-users] libwacom checksum error In-Reply-To: <51f5df62-387a-ba1f-7f48-1eb0097e6a31@gmail.com> References: <51f5df62-387a-ba1f-7f48-1eb0097e6a31@gmail.com> Message-ID: > +============================================================================== > | MD5SUM check for libwacom-0.26.tar.bz2 [ FAILED ] > +============================================================================== > | Expected: 00d7f50bc7feda6a01f2b2546f787bc9 > | Found: cb530d737c8f2d1023797cf0587b4e05 > +============================================================================== Oh, this is a *good* *one* :D It's actually downloading an HTML document (with that md5sum) that says: lololololol -D. From baildon.research at googlemail.com Wed Sep 27 21:00:32 2017 From: baildon.research at googlemail.com (David Spencer) Date: Wed, 27 Sep 2017 22:00:32 +0100 Subject: [Slackbuilds-users] Roll back the 0ad script In-Reply-To: <20170926200759.0871a9840afb8478b40240fd@ya.ru> References: <20170926200759.0871a9840afb8478b40240fd@ya.ru> Message-ID: > Hello all. I received a report that package doesn't work (i got segfault also, but i thinked-though that it only my problem). I try to fix it, but now i have not a lot of time. Please, rollback 0ad slackbuild to 0.0.21 version. Sorry for the late reply, we did this last night (also 0ad-data) Thanks -D. From alan.aversa at cox.net Wed Sep 27 18:34:06 2017 From: alan.aversa at cox.net (Alan Aversa) Date: Wed, 27 Sep 2017 11:34:06 -0700 Subject: [Slackbuilds-users] MuseScore build error on slack-current (w/ Qt 5.9.1) Message-ID: I'm getting the following errors when trying to build MuseScore 2.1.0 with the latest SlackBuild on Slackware64-current (Qt 5.9.1): if test ! -d build.release; then mkdir build.release; fi; \ cd build.release; \ export PATH=/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/go/bin:/home/alan/Documents/go//bin; \ cmake -DCMAKE_BUILD_TYPE=RELEASE \ -DCMAKE_TOOLCHAIN_FILE="" \ -DCMAKE_INSTALL_PREFIX="/usr" \ -DMSCORE_INSTALL_SUFFIX="""" \ -DMUSESCORE_LABEL="""" \ -DBUILD_LAME=""ON" " \ -DBUILD_PULSEAUDIO=""ON" " \ -DBUILD_JACK=""ON" " \ -DBUILD_PORTAUDIO=""ON" " \ -DBUILD_WEBKIT=""ON" " \ -DCMAKE_SKIP_RPATH=""FALSE"" ..; \ make lrelease; \ make -j 4; \ -- The C compiler identification is GNU 7.2.0 -- The CXX compiler identification is GNU 7.2.0 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Detecting C compile features -- Detecting C compile features - done -- Check for working CXX compiler: /usr/bin/c++ -- Check for working CXX compiler: /usr/bin/c++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Deprecation Warning at CMakeLists.txt:42 (cmake_policy): The OLD behavior for policy CMP0020 will be removed from a future version of CMake. The cmake-policies(7) manual explains that the OLD behaviors of all policies are deprecated and that a policy should be set to OLD only under specific short-term circumstances. Projects should be ported to the NEW behavior and not rely on setting a policy to OLD. CMake Error at /usr/lib64/cmake/Qt5Designer/Qt5DesignerConfig.cmake:27 (message): The imported target "Qt5::Designer" references the file "/usr/lib64/qt5/plugins/designer/libqdeclarativeview.so" but this file does not exist. Possible reasons include: * The file was deleted, renamed, or moved to another location. * An install or uninstall procedure did not complete successfully. * The installation package was faulty and contained "/usr/lib64/cmake/Qt5Designer/Qt5Designer_QDeclarativeViewPlugin.cmake" but not all the files it references. Call Stack (most recent call first): /usr/lib64/cmake/Qt5Designer/Qt5DesignerConfig.cmake:171 (_qt5_Designer_check_file_exists) /usr/lib64/cmake/Qt5Designer/Qt5Designer_QDeclarativeViewPlugin.cmake:4 (_populate_Designer_plugin_properties) /usr/lib64/cmake/Qt5Designer/Qt5DesignerConfig.cmake:179 (include) build/FindQt5Transitional.cmake:30 (find_package) CMakeLists.txt:56 (include) -- Configuring incomplete, errors occurred! See also "/tmp/SBo/MuseScore-2.1.0/build.release/CMakeFiles/CMakeOutput.log". make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/tmp/SBo/MuseScore-2.1.0/build.release' make[1]: *** No rule to make target 'lrelease'. Stop. make[1]: Leaving directory '/tmp/SBo/MuseScore-2.1.0/build.release' make[1]: warning: -jN forced in submake: disabling jobserver mode. make[1]: Entering directory '/tmp/SBo/MuseScore-2.1.0/build.release' make[1]: *** No targets specified and no makefile found. Stop. make[1]: Leaving directory '/tmp/SBo/MuseScore-2.1.0/build.release' make: *** [Makefile:48: release] Error 2 Has anyone else encountered this issue? If so, how did you fix it? thanks, Alan -- ? -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 256 bytes Desc: OpenPGP digital signature URL: From klaatu at member.fsf.org Thu Sep 28 01:56:55 2017 From: klaatu at member.fsf.org (Klaatu) Date: Thu, 28 Sep 2017 14:56:55 +1300 Subject: [Slackbuilds-users] MuseScore build error on slack-current (w/ Qt 5.9.1) In-Reply-To: References: Message-ID: <6B90C7DC-AE2A-47C9-B681-A062FC148DC9@member.fsf.org> I'd be interested in this, as well. I maintain it and cannot replicate the error. On 28 September 2017 7:34:06 AM NZDT, Alan Aversa wrote: >I'm getting the following errors when trying to build MuseScore 2.1.0 >with the latest SlackBuild on Slackware64-current (Qt 5.9.1): > > if test ! -d build.release; then mkdir build.release; fi; \ > cd build.release; \ >export >PATH=/usr/local/sbin:/usr/local/bin:/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/go/bin:/home/alan/Documents/go//bin; > \ > cmake -DCMAKE_BUILD_TYPE=RELEASE \ > -DCMAKE_TOOLCHAIN_FILE="" \ > -DCMAKE_INSTALL_PREFIX="/usr" \ > -DMSCORE_INSTALL_SUFFIX="""" \ > -DMUSESCORE_LABEL="""" \ > -DBUILD_LAME=""ON" " \ > -DBUILD_PULSEAUDIO=""ON" " \ > -DBUILD_JACK=""ON" " \ > -DBUILD_PORTAUDIO=""ON" " \ > -DBUILD_WEBKIT=""ON" " \ > -DCMAKE_SKIP_RPATH=""FALSE"" ..; \ > make lrelease; \ > make -j 4; \ > > -- The C compiler identification is GNU 7.2.0 > -- The CXX compiler identification is GNU 7.2.0 > -- Check for working C compiler: /usr/bin/cc > -- Check for working C compiler: /usr/bin/cc -- works > -- Detecting C compiler ABI info > -- Detecting C compiler ABI info - done > -- Detecting C compile features > -- Detecting C compile features - done > -- Check for working CXX compiler: /usr/bin/c++ > -- Check for working CXX compiler: /usr/bin/c++ -- works > -- Detecting CXX compiler ABI info > -- Detecting CXX compiler ABI info - done > -- Detecting CXX compile features > -- Detecting CXX compile features - done > CMake Deprecation Warning at CMakeLists.txt:42 (cmake_policy): >The OLD behavior for policy CMP0020 will be removed from a future >version > of CMake. > > The cmake-policies(7) manual explains that the OLD behaviors of all >policies are deprecated and that a policy should be set to OLD only >under >specific short-term circumstances. Projects should be ported to the >NEW > behavior and not rely on setting a policy to OLD. > > >CMake Error at /usr/lib64/cmake/Qt5Designer/Qt5DesignerConfig.cmake:27 >(message): > The imported target "Qt5::Designer" references the file > > "/usr/lib64/qt5/plugins/designer/libqdeclarativeview.so" > > but this file does not exist. Possible reasons include: > > * The file was deleted, renamed, or moved to another location. > > * An install or uninstall procedure did not complete successfully. > > * The installation package was faulty and contained > >"/usr/lib64/cmake/Qt5Designer/Qt5Designer_QDeclarativeViewPlugin.cmake" > > but not all the files it references. > > Call Stack (most recent call first): >/usr/lib64/cmake/Qt5Designer/Qt5DesignerConfig.cmake:171 >(_qt5_Designer_check_file_exists) >/usr/lib64/cmake/Qt5Designer/Qt5Designer_QDeclarativeViewPlugin.cmake:4 >(_populate_Designer_plugin_properties) > /usr/lib64/cmake/Qt5Designer/Qt5DesignerConfig.cmake:179 (include) > build/FindQt5Transitional.cmake:30 (find_package) > CMakeLists.txt:56 (include) > > > -- Configuring incomplete, errors occurred! >See also >"/tmp/SBo/MuseScore-2.1.0/build.release/CMakeFiles/CMakeOutput.log". >make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent >make rule. > make[1]: Entering directory '/tmp/SBo/MuseScore-2.1.0/build.release' > make[1]: *** No rule to make target 'lrelease'. Stop. > make[1]: Leaving directory '/tmp/SBo/MuseScore-2.1.0/build.release' > make[1]: warning: -jN forced in submake: disabling jobserver mode. > make[1]: Entering directory '/tmp/SBo/MuseScore-2.1.0/build.release' > make[1]: *** No targets specified and no makefile found. Stop. > make[1]: Leaving directory '/tmp/SBo/MuseScore-2.1.0/build.release' > make: *** [Makefile:48: release] Error 2 > >Has anyone else encountered this issue? If so, how did you fix it? > >thanks, >Alan >-- >? -- Klaatu -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Thu Sep 28 23:16:02 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 28 Sep 2017 17:16:02 -0600 Subject: [Slackbuilds-users] help. trying to create package for radare2-bindings. Message-ID: I can't get it to compile.... maybe missing something? I did try version, 1.4.x and 1.6.x and latest commit. I believe it is just broken... *./configure* ==> Using valabind 1.4 ==> Using swig 3.0.12 Checking valabind languages support... - python: yes - perl: yes - ruby: yes - lua: yes - go: no - java: yes - guile: yes - php5: no - node-ffi: no - ctypes: yes - ocaml: no - cxx: yes (g++) - valac: yes Supported langs: - ctypes - cxx - duktape - guile - java - lua - perl - python - ruby - valac checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu checking for working directories... current using prefix '/usr/local' checking for c compiler... gcc checking for c++ compiler... g++ checking for valabind... /usr/bin/valabind checking for swig... /usr/bin/swig checking for g-ir-compiler... /usr/bin/g-ir-compiler Using PKGCONFIG: pkg-config checking pkg-config flags for r_core... yes creating ./config.mk cleaning temporally files... done Final report: - PREFIX = /usr/local - HAVE_SWIG = 1 - HAVE_VALABIND = 1 - HAVE_GIRCOMPILER = 1 *make > error.txt 2>&1* (pkg-config:6055): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:6055): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed make -C libr/lang/p make[1]: Entering directory '/home/ferdna/Downloads/slackbuilds/radare2-bindings/radare2-bindings/radare2-bindings-1.6.0/libr/lang/p' (pkg-config:6064): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:6064): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:6078): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:6078): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed cc -I/usr/include/libr -I/usr/include/texlua52 -c -o lua.o lua.c lua.c: In function ???init???: lua.c:10:16: error: ???PREFIX??? undeclared (first use in this function); did you mean ???PRIX8???? #define LIBDIR PREFIX"/lib" ^ lua.c:97:20: note: in expansion of macro ???LIBDIR??? r_lua_file (NULL, LIBDIR"/radare2/"R2_VERSION"/radare.lua"); ^~~~~~ lua.c:10:16: note: each undeclared identifier is reported only once for each function it appears in #define LIBDIR PREFIX"/lib" ^ lua.c:97:20: note: in expansion of macro ???LIBDIR??? r_lua_file (NULL, LIBDIR"/radare2/"R2_VERSION"/radare.lua"); ^~~~~~ lua.c:10:22: error: expected ???)??? before string constant #define LIBDIR PREFIX"/lib" ^ lua.c:97:20: note: in expansion of macro ???LIBDIR??? r_lua_file (NULL, LIBDIR"/radare2/"R2_VERSION"/radare.lua"); ^~~~~~ make[1]: *** [: lua.o] Error 1 make[1]: Leaving directory '/home/ferdna/Downloads/slackbuilds/radare2-bindings/radare2-bindings/radare2-bindings-1.6.0/libr/lang/p' make: *** [Makefile:46: all] Error 2 *THIS IS FOR LATEST COMMIT(1846502d79f8abe309769829d7f6c72e9e9fb708):* *bash-4.4$ make* (pkg-config:7653): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7653): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed make -C libr/lang/p make[1]: Entering directory '/home/ferdna/Downloads/slackbuilds/radare2-bindings/radare2-bindings/radare2-bindings-1846502d79f8abe309769829d7f6c72e9e9fb708/libr/lang/p' (pkg-config:7662): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7662): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7682): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7682): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed cc -I/usr/include/libr -DPREFIX=\"/usr/local\" -I/usr/include/texlua52 -c -o lua.o lua.c (pkg-config:7690): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7690): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7695): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7695): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed cc -I/usr/include/libr -DPREFIX=\"/usr/local\" -I/usr/include/texlua52 -fPIC -lr_core -lr_io -lr_util -shared -o lang_lua.so lua.c -ltexlua52 (pkg-config:7705): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7705): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed cc -I/usr/include/libr -DPREFIX=\"/usr/local\" -I/usr/include/texlua52 -I/usr/lib64/perl5/CORE/ \ -fPIC -lr_core -lr_io -lr_util -shared -o lang_perl.so perl.c \ `perl -MExtUtils::Embed -e ccopts | sed -e 's/-arch [^\s]* //g'` \ `perl -MExtUtils::Embed -e ldopts | sed -e 's/-arch [^\s]* //g'` In file included from /usr/include/ctype.h:25:0, from /usr/include/libr/r_types_base.h:4, from /usr/include/libr/r_types.h:160, from /usr/include/libr/r_lib.h:7, from perl.c:4: /usr/include/features.h:373:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp] # warning _FORTIFY_SOURCE requires compiling with optimization (-O) ^~~~~~~ perl.c: In function ?setup?: perl.c:75:2: warning: #warning TODO: implement setup in lang/perl [-Wcpp] #warning TODO: implement setup in lang/perl ^~~~~~~ (pkg-config:7725): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed (pkg-config:7725): GLib-CRITICAL **: g_string_insert_len: assertion 'len == 0 || val != NULL' failed cc python.c -I/usr/include/libr -DPREFIX=\"/usr/local\" -I/usr/include/texlua52 -I/usr/include/python2.7 -I/usr/include/python2.7 -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -DPYVER=2 -lpython2.7 -lpthread -ldl -lutil -lm -L/usr/lib -lr_core -lr_io -lr_util -shared \ -lr_core -lr_io -lr_util -shared -fPIC -o lang_python2.so In file included from python.c:76:0: python/io.c: In function ?Radare_plugin_io?: python/io.c:178:4: error: ?RLibStruct {aka struct r_lib_struct_t}? has no member named ?free? lp.free = (void (*)(void *data))Radare_plugin_io_free; ^ python/io.c:180:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] Py_RETURN_TRUE; ^~~~~~~~~~~~~~ In file included from python.c:77:0: python/asm.c: In function ?Radare_plugin_asm?: python/asm.c:89:4: error: ?RLibStruct {aka struct r_lib_struct_t}? has no member named ?free? lp.free = (void (*)(void *data))Radare_plugin_asm_free; ^ python/asm.c:91:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] Py_RETURN_TRUE; ^~~~~~~~~~~~~~ In file included from python.c:78:0: python/anal.c: In function ?Radare_plugin_anal?: python/anal.c:234:4: error: ?RLibStruct {aka struct r_lib_struct_t}? has no member named ?free? lp.free = (void (*)(void *data))Radare_plugin_anal_free; ^ python/anal.c:236:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] Py_RETURN_TRUE; ^~~~~~~~~~~~~~ In file included from python.c:79:0: python/bin.c: In function ?Radare_plugin_bin?: python/bin.c:787:4: error: ?RLibStruct {aka struct r_lib_struct_t}? has no member named ?free? lp.free = (void (*)(void *data))Radare_plugin_bin_free; ^ python/bin.c:789:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] Py_RETURN_TRUE; ^~~~~~~~~~~~~~ In file included from python.c:80:0: python/core.c: In function ?Radare_plugin_core?: python/core.c:51:4: error: ?RLibStruct {aka struct r_lib_struct_t}? has no member named ?free? lp.free = (void (*)(void *data))Radare_plugin_core_free; ^ python/core.c:53:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] Py_RETURN_TRUE; ^~~~~~~~~~~~~~ python.c: In function ?init_radare_module?: python.c:265:2: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] Py_INCREF(&RadareType); ^~~~~~~~~ make[1]: *** [Makefile:72: lang_python.so] Error 1 make[1]: Leaving directory '/home/ferdna/Downloads/slackbuilds/radare2-bindings/radare2-bindings/radare2-bindings-1846502d79f8abe309769829d7f6c72e9e9fb708/libr/lang/p' make: *** [Makefile:46: all] Error 2 bash-4.4$ -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Fri Sep 29 17:28:43 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 29 Sep 2017 10:28:43 -0700 (PDT) Subject: [Slackbuilds-users] Web site question Message-ID: I have many typefaces/fonts on this desktop that I don't need. Many look very similar to others in their class (at least to non-typographer me) and I want to remove these extraneous fonts, including those for non-Roman alphabets. After removing a bunch of typefaces I discovered that the one used to display the category and name of the SBo package was among those removed. Looking at a package's web page source I did not see a font name. Is there a way to identify the fonts used so I can keep them available? Rich From markus.ka.rinne at gmail.com Fri Sep 29 18:29:21 2017 From: markus.ka.rinne at gmail.com (Markus Rinne) Date: Fri, 29 Sep 2017 21:29:21 +0300 Subject: [Slackbuilds-users] help. trying to create package for radare2-bindings. In-Reply-To: References: Message-ID: <20170929182921.GA1327@tursas.sidaroth.foo> Hello, On Thu, Sep 28, 2017 at 05:16:02PM -0600, Fernando Lopez wrote: > I can't get it to compile.... maybe missing something? I did try version, > 1.4.x and 1.6.x and latest commit. I believe it is just broken... The error you got with 1.6.0 has been fixed after version 1.6.0 in git: https://github.com/radare/radare2-bindings/commit/508658d5d194e495ecc9b79e9816780a1579d708 Newest git version doesn't compile because since commit https://github.com/radare/radare2-bindings/commit/075d1e88a8468d5de4eefc8716d3d457d86e620b it needs things that were added to radare2 after version radare2-1.6.0. Seems that member 'free' was added in this commit: https://github.com/radare/radare2/commit/e61f5ef0a032ea2487ac08124adfee0a19230da7 I would use radare2-bindings version 1.6.0 and apply changes of commit 508658d5d194e495ecc9b79e9816780a1579d708 as a patch. Markus From fellype at gmail.com Fri Sep 29 18:45:50 2017 From: fellype at gmail.com (Fellype do Nascimento) Date: Fri, 29 Sep 2017 15:45:50 -0300 Subject: [Slackbuilds-users] Can't submit academic/veusz SlackBuild because it still in pending In-Reply-To: <12d2944a-921b-e916-4ec6-dc7e47751ac3@gmail.com> References: <12d2944a-921b-e916-4ec6-dc7e47751ac3@gmail.com> Message-ID: <1e1ebd8b-0add-757e-35a5-4355721e2a5c@gmail.com> Dear SBo admins, I'm trying to submit a new version of academic/veusz SlackBuild but I can't do it because is appears to still in pending (after a previous submission that failed to build - analyzed and reported by David Spencer). Please, remove the previous veusz submission (md5sum: a466ac04d55ed2fbf83fb098a8be8a77) so I can do a new one. If you prefer, you can update it in SBo for me (the veusz.tar.gz file is attached). It was updated for version 2.0.1. The 2.x version moved from Qt4/PyQt4 to Qt5/PyQt5, then PyQt5 was added to "REQUIRES". It requires CFLAGS=-std=c++11 in order to build properly with Qt 5.7 (see line 72 of the .SlackBuild) - thanks to Jeremy Sanders. The README file was also updated. Best regards -------- Forwarded Message -------- Subject: veusz.tar.gz still in pending Date: Thu, 28 Sep 2017 14:53:45 -0300 From: Fellype do Nascimento To: David Spencer On 09/23/2017 07:10 AM, David Spencer wrote: > Hi Fellype, > > Unfortunately this fails to build for me, there are a huge number of > errors, please see https://pastebin.com/PXKfgCyy > > I wonder if you tested this on -current, or with a different version of > qt5? These are the SBo dependencies I used: > > numpy-1.11.1 > libwacom-0.26 > libinput-1.8.2 > libxkbcommon-0.7.1 > qt5-5.7.1 > qt5-webkit-5.7.1 > PyQt5-5.7 > > Thanks > -D. > Hi David, Can you please remove veusz.tar.gz from pending? I can't submit a new one nor remove it by myself. Or, if you prefer, please update it in SBo for me (the veusz.tar.gz file is attached). It was updated for version 2.0.1. The 2.x version moved from Qt4/PyQt4 to Qt5/PyQt5, then PyQt5 was added to "REQUIRES". It requires CFLAGS=-std=c++11 in order to build properly with Qt 5.7 (see line 72 of the .SlackBuild) - thanks to Jeremy Sanders. The README file was also updated. Best regards -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: veusz.tar.gz Type: application/gzip Size: 3080 bytes Desc: not available URL: From rshepard at appl-ecosys.com Fri Sep 29 19:18:31 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 29 Sep 2017 12:18:31 -0700 (PDT) Subject: [Slackbuilds-users] Web site question In-Reply-To: <29fa9895-4238-9478-f9ea-b072dfebd588@dcclost.com> References: <29fa9895-4238-9478-f9ea-b072dfebd588@dcclost.com> Message-ID: On Fri, 29 Sep 2017, Alexander Grotewohl wrote: > Just a quick look in Firefox listed variants of Liberation sans, DejaVu > Sans and Nimbus Sans This isn't a good answer though, because those fonts > were subbed in (on my machine at least!) for what we find in the CSS: Alexander, I agree that font substitution is very common. I must have missed the fonts on the page I viewed and most web sites don't let outsiders look at their css files so I didn't try to find one. > Fonts don't really take up a lot of space. I'd say unless there are fonts > you added yourself that you no longer use, I wouldn't mess with them to > avoid problems like this :) Yes, I added many over the years (fontmatrix counts 813 on the system). I suspect many are duplicates. I think I can safely remove the non-Roman alphabets because I cannot read them, but I'll leave the various serif and sanserif fonts because, as you write, they don't take a lot of room. Thanks for your useful response, Rich From andreas.guldstrand at gmail.com Fri Sep 29 19:42:44 2017 From: andreas.guldstrand at gmail.com (Andreas Guldstrand) Date: Fri, 29 Sep 2017 21:42:44 +0200 Subject: [Slackbuilds-users] Web site question In-Reply-To: References: <29fa9895-4238-9478-f9ea-b072dfebd588@dcclost.com> Message-ID: On 29 September 2017 at 21:18, Rich Shepard wrote: > [...] and most web sites don't let outsiders look at > their css files so I didn't try to find one. What do you mean? All CSS files need to be readable in order for the browser to be able to load it in the first place. There's neither a way nor a reason to have a usable CSS file that isn't available to look at. From rshepard at appl-ecosys.com Fri Sep 29 19:52:03 2017 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 29 Sep 2017 12:52:03 -0700 (PDT) Subject: [Slackbuilds-users] Web site question In-Reply-To: References: <29fa9895-4238-9478-f9ea-b072dfebd588@dcclost.com> Message-ID: On Fri, 29 Sep 2017, Andreas Guldstrand wrote: > What do you mean? All CSS files need to be readable in order for the > browser to be able to load it in the first place. There's neither a way > nor a reason to have a usable CSS file that isn't available to look at. The browser can find it but the few times I've looked I've not found a link. Rich From eric.b.pratt at gmail.com Fri Sep 29 20:36:11 2017 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Fri, 29 Sep 2017 13:36:11 -0700 Subject: [Slackbuilds-users] Web site question In-Reply-To: References: <29fa9895-4238-9478-f9ea-b072dfebd588@dcclost.com> Message-ID: On any given package's page on the slackbuilds site, I only see one .css file mentioned in the html: It's a relative link that refers to http://slackbuilds.org/css/style.css but you won't find an actual like you can see on the rendered web page. Just hit CTRL + U to view source and search it or use wget or curl to download and grep it. On Fri, Sep 29, 2017 at 12:52 PM, Rich Shepard wrote: > On Fri, 29 Sep 2017, Andreas Guldstrand wrote: > > What do you mean? All CSS files need to be readable in order for the >> browser to be able to load it in the first place. There's neither a way >> nor a reason to have a usable CSS file that isn't available to look at. >> > > The browser can find it but the few times I've looked I've not found a > link. > > Rich > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Fri Sep 29 20:36:31 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Fri, 29 Sep 2017 14:36:31 -0600 Subject: [Slackbuilds-users] help. trying to create package for radare2-bindings. In-Reply-To: <20170929182921.GA1327@tursas.sidaroth.foo> References: <20170929182921.GA1327@tursas.sidaroth.foo> Message-ID: awesome!!! thanks!!! =D On Fri, Sep 29, 2017 at 12:29 PM, Markus Rinne wrote: > Hello, > > On Thu, Sep 28, 2017 at 05:16:02PM -0600, Fernando Lopez wrote: > > I can't get it to compile.... maybe missing something? I did try version, > > 1.4.x and 1.6.x and latest commit. I believe it is just broken... > > The error you got with 1.6.0 has been fixed after version 1.6.0 in git: > > https://github.com/radare/radare2-bindings/commit/ > 508658d5d194e495ecc9b79e9816780a1579d708 > > Newest git version doesn't compile because since commit > > https://github.com/radare/radare2-bindings/commit/ > 075d1e88a8468d5de4eefc8716d3d457d86e620b > > it needs things that were added to radare2 after version radare2-1.6.0. > Seems > that member 'free' was added in this commit: > > https://github.com/radare/radare2/commit/e61f5ef0a032ea2487ac08124adfee > 0a19230da7 > > I would use radare2-bindings version 1.6.0 and apply changes of commit > 508658d5d194e495ecc9b79e9816780a1579d708 as a patch. > > Markus > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Fri Sep 29 20:46:28 2017 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Fri, 29 Sep 2017 14:46:28 -0600 Subject: [Slackbuilds-users] Web site question In-Reply-To: References: <29fa9895-4238-9478-f9ea-b072dfebd588@dcclost.com> Message-ID: aren't fonts pulled from the web? that is almost everywhere because not all systems(win,lin,and) have the required fonts... thats why they are pulled from the web... On Fri, Sep 29, 2017 at 2:36 PM, Eric Pratt wrote: > On any given package's page on the slackbuilds site, I only see one .css > file mentioned in the html: > > > > It's a relative link that refers to http://slackbuilds.org/css/style.css > but you won't find an actual like you can see on the rendered web page. > Just hit CTRL + U to view source and search it or use wget or curl to > download and grep it. > > > On Fri, Sep 29, 2017 at 12:52 PM, Rich Shepard > wrote: > >> On Fri, 29 Sep 2017, Andreas Guldstrand wrote: >> >> What do you mean? All CSS files need to be readable in order for the >>> browser to be able to load it in the first place. There's neither a way >>> nor a reason to have a usable CSS file that isn't available to look at. >>> >> >> The browser can find it but the few times I've looked I've not found a >> link. >> >> Rich >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From eric.b.pratt at gmail.com Fri Sep 29 21:11:45 2017 From: eric.b.pratt at gmail.com (Eric Pratt) Date: Fri, 29 Sep 2017 14:11:45 -0700 Subject: [Slackbuilds-users] Web site question In-Reply-To: References: <29fa9895-4238-9478-f9ea-b072dfebd588@dcclost.com> Message-ID: On Fri, Sep 29, 2017 at 1:46 PM, Fernando Lopez wrote: > aren't fonts pulled from the web? that is almost everywhere because not > all systems(win,lin,and) have the required fonts... thats why they are > pulled from the web... > ?Not really. Unless you name a specific font in your CSS and provide src links to the font files in a @font-face block in your CSS, they're almost always pulled from the local system.? Most of the time, a generic font-family is specified in CSS instead of an embedded font. If you don't have the required font-family, your browser simply substitutes what it has configured as default fonts for various styles. Actually, I suspect the majority of the time, fonts are actually specified at all and your browser just uses its configured defaults for everything. This is one of the reasons why the Microsoft web core fonts got so popular with so many Linux users. But these days, the fonts issue is generally a non-issue. -------------- next part -------------- An HTML attachment was scrubbed... URL: From baildon.research at googlemail.com Fri Sep 29 23:12:42 2017 From: baildon.research at googlemail.com (David Spencer) Date: Sat, 30 Sep 2017 00:12:42 +0100 Subject: [Slackbuilds-users] Can't submit academic/veusz SlackBuild because it still in pending In-Reply-To: <1e1ebd8b-0add-757e-35a5-4355721e2a5c@gmail.com> References: <12d2944a-921b-e916-4ec6-dc7e47751ac3@gmail.com> <1e1ebd8b-0add-757e-35a5-4355721e2a5c@gmail.com> Message-ID: > I'm trying to submit a new version of academic/veusz SlackBuild but I can't do it because is appears to still in pending (after a previous submission that failed to build - analyzed and reported by David Spencer). > Please, remove the previous veusz submission (md5sum: a466ac04d55ed2fbf83fb098a8be8a77) so I can do a new one. > If you prefer, you can update it in SBo for me (the veusz.tar.gz file is attached). Hi Fellype, Thanks for the new version! Sorry I didn't clear it from pending last week, and sorry I didn't do this yesterday -- but your new version is now ready :D Cheers -D. From willysr at slackbuilds.org Sat Sep 30 00:37:29 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 30 Sep 2017 07:37:29 +0700 Subject: [Slackbuilds-users] Updates - 20170930.1 Message-ID: <624a7158-d88e-01d6-7a0a-093e4fa64b8e@slackbuilds.org> This is the last update in September! David has managed to fix the github md5sum issue last week. Hopefully that's all, but whenever you find a mismatch md5sum, let us know. 0ad and 0ad-data are reverted to previous version due to segfault reported to the maintainer, while FlightGear is now updated to the latest 2017.3.1 release. This week, we have over 140+ commits. Big thanks to all maintainers and contributors. Keep up the good work maintaining those scripts and we will see you in October :) Keep Slacking! Sat Sep 30 00:20:04 UTC 2017 academic/Mnemosyne: Updated for version 2.5. academic/OpenFOAM: Fix build. academic/bppsuite: Fix new github md5sum. academic/fet: Updated for version 5.33.1. academic/veusz: Updated for version 2.0.1. audio/clementine: Updated README for optional dependency. audio/snd: Updated for version 17.7. desktop/awoken-icon-theme: Fix new github md5sum. desktop/i3: Updated for version 4.14.1. desktop/mh5000: Added (Sets and Changes Background Image). desktop/oomox: Updated for version 1.4.0. desktop/xdo: Updated for version 0.5.7. desktop/zuki-themes: Updated for version 20170805. development/Catch: Updated for version 1.10.0 development/SQLAlchemy: Updated for version 1.1.14. development/Sphinx: Updated for version 1.6.4. development/asl: Updated for version 142_bld119, new maintainer. development/atom: Fix new github md5sum. development/cmocka: Updated for version 1.1.1. development/diffoscope: Updated for version 87. development/extra-cmake-modules: Fix new github md5sum. development/fsharp: Fix new github md5sum. development/hhvm: Updated for version 3.21.3 development/kotlin: Updated for version 1.1.50. development/lighttable: Fix new github md5sum. development/meson: Updated for version 0.42.1. development/mono-addins: Fix new github md5sum. development/ninja: Updated to match slackware current. development/pycharm: Updated for version 2017.2.3. development/qbs: Fix new github md5sum. development/referenceassemblies-pcl: Fix new github md5sum. development/rstudio-desktop: Fix new github md5sum. development/universal-ctags: Updated for version e1bc2a3 development/valabind: Added (vapi bindings for nodejs, python etc). development/vscode: Updated for version 1.16.1 development/wheel: Updated for version 0.30.0. games/0ad-data: Reverted to version 0.0.21. games/0ad: Reverted to version 0.0.21. games/FlightGear-data: Updated for version 2017.3.1. games/FlightGear: Updated for version 2017.3.1. games/OpenXcom: Fix new github md5sum. games/commandergenius: Fix new github md5sum. games/doomretro: Fix new github md5sum. games/empire: Updated for version 4.4.0. games/hlsdk: Fix new github md5sum. games/libretro-ppsspp: Updated for version 2017.09.29_25d3bab. games/mame: Updated for version 0.190. games/openclonk: Fix new github md5sum. games/openlierox: Fix new github md5sum. games/yamagi-quake2: Updated for version 7.02. gis/gdal: Updated for version 2.2.2. gis/grass: Updated for version 7.2.2. gis/qmapshack: Updated for version 1.9.1. graphics/XnViewMP: Switch to https. graphics/meh: Switch to https. graphics/meshlab: Fix new github md5sum. graphics/povray: Fix new github md5sum. graphics/qcad: Fix new github md5sum. graphics/vulkansdk: Updated for version 1.0.61.1. ham/gqrx-sdr: Updated for version 2.8. libraries/SimGear: Updated for version 2017.3.1. libraries/cffi: Updated for version 1.11.0. libraries/cpprestsdk: Fix new github md5sum. libraries/dlib: Updated for version 19.7 libraries/double-conversion: Updated for version 3.0.0 libraries/folly: Updated for version 2017.09.25.00 libraries/fuzzylite: Switch to https. libraries/google-fruit: Updated for version 3.0.0 libraries/kashmir: Fix new github md5sum. libraries/libfilezilla: Updated for version 0.11.0. libraries/libgit2: Fix new github md5sum. libraries/libidn2: Updated for version 2.0.4. libraries/libmediainfo: Updated for version 0.7.99. libraries/libopenshot-audio: Fix new github md5sum. libraries/libversion: Updated for version 2.1.0. libraries/libzen: Updated for version 0.4.37. libraries/pjsip: Updated for version 2.7. libraries/proxygen: Updated for version 2017.09.25.00 libraries/qt5-styleplugins: Added (additional Qt5 style plugins). libraries/rocksdb: Updated for version 5.7.3 libraries/sqlpp11-connector-sqlite3: Updated for version 0.25 libraries/sqlpp11: Updated for version 0.51 libraries/wangle: Updated for version 2017.09.25.00 libraries/webkit2gtk: Fix missing export. libraries/yaml-cpp: Fix new github md5sum. misc/protobuf3: Fix new github md5sum. multimedia/OpenPHT: Fix new github md5sum. multimedia/kodi: Fix new github md5sum. multimedia/mediainfo: Updated for version 0.7.99. multimedia/miro: Fix new github md5sum. multimedia/opera-developer-ffmpeg-codecs: Updated for version 62.0. multimedia/plex-home-theater: Fix new github md5sum. network/PaleMoon: Updated for version 27.5.0. network/WireGuard: Updated for version 0.0.20170918. network/dnstracer: Update DOWNLOAD. network/dovecot-pigeonhole: Updated for version 0.4.20. network/dovecot: Updated for version 2.2.32. network/fail2ban: Updated for version 0.10.0. network/filezilla: Updated for version 3.28.0. network/hylafax+: Updated for version 5.5.9. network/krb5: Updated for version 1.15.2. network/luakit: Fix new github md5sum. network/nagios: Updated for version 4.3.4. network/opera-developer: Updated for version 50.0.2729.0. network/palemoon: Updated for version 27.5.0. network/postfix: Updated for version 3.2.3. network/r8168: Updated for version 8.045.08. network/skypeforlinux: Updated for version 5.5.0.1. network/slimjet: Updated for version 15.1.4.0. network/teamviewer: Updated for version 12.0.85001. network/vivaldi: Updated for version 1.12.955.38. network/weechat: Updated for version 1.9.1. network/yle-dl: Updated for version 2.24. office/pdfjam: Switch to https. office/texworks: Fix new github md5sum. perl/perl-AnyEvent-I3: Removed (Included in I3). perl/perl-linux-desktop-files: Updated for version 0.21. python/Flask-SQLAlchemy: Updated for version 2.3.0. python/aniso8601: Updated for version 1.3.0. python/bleach: Updated for version 2.1. python/jedi: Updated for version 0.11.0. python/ndg_httpsclient: Updated for version 0.4.3. python/pendulum: Updated for version 1.3.0. python/python-autobahn: Updated for version 17.9.3. python/selenium: Updated for version 3.6.0. python/sqlparse: Updated for version 0.2.4. ruby/rubygem-method_source: Updated for version 0.9.0. ruby/rubygem-pry: Updated for version 0.11.1. system/afdko: Fix new github md5sum. system/barman: Updated for version 2.3. system/bit-babbler: Updated for version 0.7. system/drbd-utils: Updated for version 9.1.0. system/kbfs: Updated for version 1.0.31_20170922160113. system/keybase: Updated for version 1.0.31. system/letsencrypt: Updated for version 0.18.2. system/mlterm: Updated for version 3.8.3. system/noto-fonts: Updated for version 20170920. system/pspg: Updated for version 0.2. system/rar: Updated for version 5.5.0. system/slpkg: Updated for version 3.2.9. system/sysdig: Updated for version 0.18.0 system/unrar: Updated for version 5.5.8. system/wine-staging: Updated for version 2.17. system/worker: Updated for version 3.12.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From sombragris at sombragris.org Sat Sep 30 22:16:51 2017 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 30 Sep 2017 18:16:51 -0400 Subject: [Slackbuilds-users] Problem: MD5 fail in GeoIP Message-ID: Hi there: Posting here because I suspect the problem applies even to the official slackbuilds despite the fact that I use current. Upon downloading GeoIP sbopkg complains that there is a MD5 sum mismatch. Can you look into the matter please? Thanks in advance Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Sep 30 22:21:31 2017 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 1 Oct 2017 05:21:31 +0700 Subject: [Slackbuilds-users] Problem: MD5 fail in GeoIP In-Reply-To: References: Message-ID: <05a209bb-1353-c350-bc76-596474edd42d@slackbuilds.org> > Posting here because I suspect the problem applies even to the official > slackbuilds despite the fact that I use current. > > Upon downloading GeoIP sbopkg complains that there is a MD5 sum > mismatch. > > Can you look into the matter please? It has been written on the README If you are using sbopkg and you have md5sum errors, you need to delete your old data files from the cache and try again. basically GeoIP uses the same source filenames, so it will have invalid MD5 checksum when they are updated unless you remove the old sources first -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: