From chris.willing at linux.com Sun Jul 1 08:25:41 2018 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 1 Jul 2018 18:25:41 +1000 Subject: [Slackbuilds-users] certificate expired Message-ID: git.slackbuilds.org uses an invalid security certificate. The certificate expired on 01/07/18 14:10. The current time is 01/07/18 18:24. Error code: SEC_ERROR_EXPIRED_CERTIFICATE From idlemoor at slackbuilds.org Sun Jul 1 19:58:05 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sun, 1 Jul 2018 20:58:05 +0100 Subject: [Slackbuilds-users] Giving up maintainership of my slackbuiilds In-Reply-To: <0MCtql-1fQaNX0NJj-009czG@mail.gmx.com> References: <0MCtql-1fQaNX0NJj-009czG@mail.gmx.com> Message-ID: <0c5a6080-5cb5-1384-dbe3-7a0a9c37cedd@slackbuilds.org> > Dear subscribers of slackbuilds-users@, > > I'm giving up maintainership of my slackbuilds. Please either > remove them from SlackBuilds.org or let someone else take them > over. There's one really important thing that we haven't said yet: *Thank you* Leonard for your contributions, I hope everybody takes good care of your stuff :) Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From slackalaxy at gmail.com Mon Jul 2 06:15:50 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 2 Jul 2018 09:15:50 +0300 Subject: [Slackbuilds-users] Repology: a way to track potential updates Message-ID: Hi guys, i recently came across the repology website: https://repology.org/ it compares packages between distributions and their versions. You can search by package maintainer (I found myself by my email) and get a list of potential updates. -petar From dickson.tim at googlemail.com Mon Jul 2 08:49:31 2018 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 2 Jul 2018 09:49:31 +0100 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: References: Message-ID: yes that was mentioned in the mailing list some months ago. It is quite useful as a second check to make sure versions your maintain are up to date. As it gives a percentage of packages up to date per package manager, it is? also useful to show that slackbuild maintainers are tops! (yay us) It also doesn't do any harm as a central reference for a C.V. :-) Regards, Tim On 02/07/2018 07:15, Petar Petrov wrote: > Hi guys, > > i recently came across the repology website: > > https://repology.org/ > > it compares packages between distributions and their versions. You can > search by package maintainer (I found myself by my email) and get a > list of potential updates. > > -petar > _______________________________________________ > 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 rvnues at disroot.org Mon Jul 2 09:17:24 2018 From: rvnues at disroot.org (rob van nues) Date: Mon, 2 Jul 2018 10:17:24 +0100 Subject: [Slackbuilds-users] prompt_toolkit version used no good for python-2.7 Message-ID: <20180702101724.4c2122df@knotsUL> Hi, Thanks for all the python builds. Recently, however, Sbo-upgrades killed my ipython/jupyter setup (in python-2.7). The problem lies with prompt_toolkit-2.0.3 in the slackbuild script for prompt_toolkit. This needs to be a version 1. prompt_toolkit-2.0.3 is incompatible with python-2.7 and maybe not ready for ipython3 https://github.com/ipython/ipython/pull/11177 https://github.com/jonathanslenders/python-prompt-toolkit/issues/647 At first it seemed a swap of versions in the two builds: The 2.0.3 version of prompt_toolkit in the python2 script could have been for python3-prompt_toolkit, which has version 1.0.15, the version that works with python 2; With 2.0.3, also ipython3 (without recompiling) does not work at my end; it gives the same error I noticed when compiling jupyter or starting ipython in the shell: "...from prompt_toolkit.shortcuts import create_prompt_application, create_eventloop, create_prompt_layout, create_output ....." HTH rob -- ------------------------------- Rob van Nues 13A Lamer Street Dunbar East Lothian EH42 1HJ UK From yalhcru at gmail.com Mon Jul 2 09:56:45 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 2 Jul 2018 05:56:45 -0400 Subject: [Slackbuilds-users] perl/txt2html missing dep Message-ID: Need REQUIRES="perl-YAML-Syck" in txt2html.info. From didier at slint.fr Mon Jul 2 10:08:32 2018 From: didier at slint.fr (Didier Spaier) Date: Mon, 2 Jul 2018 12:08:32 +0200 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: References: Message-ID: <65d4bdeb-ab94-de60-81dd-ab33916b0b9e@slint.fr> Hello, Le 02/07/2018 ? 10:49, Tim Dickson via SlackBuilds-users a ?crit : > As it gives a percentage of packages up to date per package manager, > it is also useful to show that slackbuild maintainers are tops! > (yay us) Should we say "Thank you!" to a SlackBuild maintainer who provides an upgrade to a shared library so that the 172 packages that rely on it are now broken? Yes repology is an useful tool, but blindly upgrade all and every SlackBuild wouldn't be a good thing IMO. Have a good day, Didier PS Yes I know, the user has no obligation to apply an update. But not all users are aware of the possible consequences of doing that. From matteo.bernardini at gmail.com Mon Jul 2 10:20:10 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 2 Jul 2018 12:20:10 +0200 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: <65d4bdeb-ab94-de60-81dd-ab33916b0b9e@slint.fr> References: <65d4bdeb-ab94-de60-81dd-ab33916b0b9e@slint.fr> Message-ID: 2018-07-02 12:08 GMT+02:00 Didier Spaier : > > Should we say "Thank you!" to a SlackBuild maintainer who provides an > upgrade to a shared library so that the 172 packages that rely on it are > now broken? > > > Yes repology is an useful tool, but blindly upgrade all and every > SlackBuild wouldn't be a good thing IMO. > > Have a good day, > > Didier > > PS Yes I know, the user has no obligation to apply an update. But not > all users are aware of the possible consequences of doing that. I totally agree. let me say also that the ones who browse repology and then write to maintainers "your SlackBuilds are outdated!" should take in account the above: there could be a lot of different reasons why some packages are not upgraded, not counting the false positives that repology often list as "upgrades". Matteo From slackalaxy at gmail.com Mon Jul 2 11:19:55 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 2 Jul 2018 14:19:55 +0300 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: References: <65d4bdeb-ab94-de60-81dd-ab33916b0b9e@slint.fr> Message-ID: Hi all, it was not my intention to provoke rants of any sort... also, i see now, that I should have read the SBo mailing list more carefully before posting about stuff you already know. Simply, *for me* Repology turned out to be useful, and decided to bring it up. For example, repology pointed out that Perlprimer and primer3 (as well as some more) have new versions, which not announced on their webpages. -petar On 2 July 2018 at 13:20, Matteo Bernardini wrote: > 2018-07-02 12:08 GMT+02:00 Didier Spaier : >> >> Should we say "Thank you!" to a SlackBuild maintainer who provides an >> upgrade to a shared library so that the 172 packages that rely on it are >> now broken? >> >> >> Yes repology is an useful tool, but blindly upgrade all and every >> SlackBuild wouldn't be a good thing IMO. >> >> Have a good day, >> >> Didier >> >> PS Yes I know, the user has no obligation to apply an update. But not >> all users are aware of the possible consequences of doing that. > > I totally agree. > > let me say also that the ones who browse repology and then write to > maintainers "your SlackBuilds are outdated!" should take in account > the above: there could be a lot of different reasons why some packages > are not upgraded, not counting the false positives that repology often > list as "upgrades". > > 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/ > From rvnues at disroot.org Mon Jul 2 12:04:36 2018 From: rvnues at disroot.org (rob van nues) Date: Mon, 2 Jul 2018 13:04:36 +0100 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 147, Issue 2 In-Reply-To: References: Message-ID: <20180702130436.1fe68c32@knotsUL> On Mon, 02 Jul 2018 11:19:59 +0000 slackbuilds-users-request at slackbuilds.org wrote: > Date: Mon, 2 Jul 2018 09:15:50 +0300 > From: Petar Petrov > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] Repology: a way to track potential > updates > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > > Hi guys, > > i recently came across the repology website: > > https://repology.org/ > > it compares packages between distributions and their versions. You can > search by package maintainer (I found myself by my email) and get a > list of potential updates. > > -petar Thanks, Petar; found out that I can update a package... What I find quite worrying is that the search by email works too well. Email addresses are somewhat scrambled in the info-files; so why does this site publish the unscrambled version that can lead to quite a bit of spam? This seems contrary to policies adhered to here. I will ask the maintainer amdmi3 at amdmi3.ru rob -- ------------------------------- Rob van Nues 13A Lamer Street Dunbar East Lothian EH42 1HJ UK From dickson.tim at googlemail.com Mon Jul 2 12:21:52 2018 From: dickson.tim at googlemail.com (Tim Dickson) Date: Mon, 2 Jul 2018 13:21:52 +0100 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: References: <65d4bdeb-ab94-de60-81dd-ab33916b0b9e@slint.fr> Message-ID: ... and this list well knows that some packages can't be "the latest" because of breakage with stock slackware packages, or other compatibility or stability reasons with other packages. Regarding the issue Didier raised, i'm sure he has raised it with the build provider, and this list ? It is always a good thing to raise? for testing when a library which is used by lots of other builds is due an update, to avoid those sort of issues.? I seem to remember ffmpeg update was done this way. Repeating Petar,? the intention was not to provoke. after all, we're used to projects who upgrade library dependencies which are more recent than what is available on sbo or slackware, leaving us to try and patch them, just to get the software working, because upstream don't want to keep older compatibility. These issues appear both ways. I still like having all builds presented together as repology.org does, even if sometimes you have to say? software X is "older" because of Y; and if there is an issue with version detection, they are generally good at updating it if you let them know. regards, Tim On 02/07/2018 12:19, Petar Petrov wrote: > Hi all, > > it was not my intention to provoke rants of any sort... also, i see > now, that I should have read the SBo mailing list more carefully > before posting about stuff you already know. Simply, *for me* Repology > turned out to be useful, and decided to bring it up. For example, > repology pointed out that Perlprimer and primer3 (as well as some > more) have new versions, which not announced on their webpages. > > -petar > > > > On 2 July 2018 at 13:20, Matteo Bernardini wrote: >> 2018-07-02 12:08 GMT+02:00 Didier Spaier : >>> >>> Should we say "Thank you!" to a SlackBuild maintainer who provides an >>> upgrade to a shared library so that the 172 packages that rely on it are >>> now broken? >>> >>> >>> Yes repology is an useful tool, but blindly upgrade all and every >>> SlackBuild wouldn't be a good thing IMO. >>> >>> Have a good day, >>> >>> Didier >>> >>> PS Yes I know, the user has no obligation to apply an update. But not >>> all users are aware of the possible consequences of doing that. >> I totally agree. >> >> let me say also that the ones who browse repology and then write to >> maintainers "your SlackBuilds are outdated!" should take in account >> the above: there could be a lot of different reasons why some packages >> are not upgraded, not counting the false positives that repology often >> list as "upgrades". >> >> 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/ >> > _______________________________________________ > 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 rvnues at disroot.org Mon Jul 2 13:02:43 2018 From: rvnues at disroot.org (rob van nues) Date: Mon, 2 Jul 2018 14:02:43 +0100 Subject: [Slackbuilds-users] Repology again Re: SlackBuilds-users Digest, Vol 147, Issue 2 In-Reply-To: <20180702130436.1fe68c32@knotsUL> References: <20180702130436.1fe68c32@knotsUL> Message-ID: <20180702140243.3c1be5db@knotsUL> Well, it has been raised as an issue but the author cannot see the problem https://github.com/repology/repology/issues/220 This is not what I expected when email addresses were published in info files. Can we take them out?? On Mon, 2 Jul 2018 13:04:36 +0100 rob van nues wrote: > On Mon, 02 Jul 2018 11:19:59 +0000 > slackbuilds-users-request at slackbuilds.org wrote: > > > Date: Mon, 2 Jul 2018 09:15:50 +0300 > > From: Petar Petrov > > To: "SlackBuilds.org Users List" > > Subject: [Slackbuilds-users] Repology: a way to track potential > > updates > > Message-ID: > > > > Content-Type: text/plain; charset="UTF-8" > > > > Hi guys, > > > > i recently came across the repology website: > > > > https://repology.org/ > > > > it compares packages between distributions and their versions. You > > can search by package maintainer (I found myself by my email) and > > get a list of potential updates. > > > > -petar > > Thanks, Petar; found out that I can update a package... > > What I find quite worrying is that the search by email works too > well. > > Email addresses are somewhat scrambled in the info-files; so why does > this site publish the unscrambled version that can lead to quite a bit > of spam? This seems contrary to policies adhered to here. > > I will ask the maintainer amdmi3 at amdmi3.ru > > rob > -- ------------------------------- Rob van Nues 13A Lamer Street Dunbar East Lothian EH42 1HJ UK From yth at ythogtha.org Mon Jul 2 13:03:37 2018 From: yth at ythogtha.org (Ythogtha) Date: Mon, 2 Jul 2018 15:03:37 +0200 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 147, Issue 2 In-Reply-To: <20180702130436.1fe68c32@knotsUL> References: <20180702130436.1fe68c32@knotsUL> Message-ID: <20180702150337.5d6814b551120cfced9b7702@ythogtha.org> > > Hi guys, > > i recently came across the repology website: > > https://repology.org/ > > Thanks, Petar; found out that I can update a package... > > What I find quite worrying is that the search by email works too > well. > > Email addresses are somewhat scrambled in the info-files; so why does > this site publish the unscrambled version that can lead to quite a bit > of spam? This seems contrary to policies adhered to here. > > I will ask the maintainer amdmi3 at amdmi3.ru > > rob Maintainers emails are pretty public in the SBo repository. A quick grep shows 761 different maintainers email, of which 96 are somehow scrambled (of which 4 are yours ^^), and 665 are plain. Besides, the kind of scrambling we're talking about (guy at domain dot tld, or john[dot]doe[at]domain[dot]tld) aren't really a difficulty for spammers. I could write a script in 15 minutes that'll scrape plain and scrambled emails off of any webpages, if they're scrambled like that. So, well, I don't think you should be more worried now than you were before. -- Arnaud From slackbuilds at jaxartes.net Mon Jul 2 13:52:06 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Mon, 02 Jul 2018 06:52:06 -0700 Subject: [Slackbuilds-users] prompt_toolkit version used no good for python-2.7 In-Reply-To: <20180702101724.4c2122df@knotsUL> References: <20180702101724.4c2122df@knotsUL> Message-ID: <2344713.IjMtIyWL1H@wintermute.sprawl.net> On Monday, 2 July 2018 02:17:24 PDT rob van nues wrote: > Hi, > > Thanks for all the python builds. > > Recently, however, Sbo-upgrades killed my ipython/jupyter setup (in > python-2.7). > The problem lies with prompt_toolkit-2.0.3 in the slackbuild script for > prompt_toolkit. This needs to be a version 1. I see this issue as well. I'm sure Dmitris will be happy to downgrade prompt_toolkit for Python 2. The dependency chain for IPython and Jupyter is quite complex so on occasion there are issues like this that come up! Best, Ben From lems at gmx.net Mon Jul 2 12:46:10 2018 From: lems at gmx.net (Leonard Schmidt) Date: Mon, 02 Jul 2018 14:46:10 +0200 Subject: [Slackbuilds-users] Giving up maintainership of my slackbuiilds In-Reply-To: <0c5a6080-5cb5-1384-dbe3-7a0a9c37cedd@slackbuilds.org> References: <0MCtql-1fQaNX0NJj-009czG@mail.gmx.com> <0c5a6080-5cb5-1384-dbe3-7a0a9c37cedd@slackbuilds.org> Message-ID: <0MN748-1fTLRe15Gi-006eaB@mail.gmx.com> David Spencer writes: >> Dear subscribers of slackbuilds-users@, >> >> I'm giving up maintainership of my slackbuilds. Please either >> remove them from SlackBuilds.org or let someone else take them >> over. > >There's one really important thing that we haven't said yet: > >*Thank you* Leonard for your contributions, I hope everybody takes good >care of your stuff :) Thank you for your kind words, David! I fear I wasn't that good a maintainer, my scripts often had to be adjusted (I keep a git repository of my scripts and diff against SBo git master). I hope someone more capable will take care of them. And thanks to those who have already done so, it is highly appreciated! I have now been using Slackware for full five years on the desktop. But enough is enough: Slackware is seriously, *seriously* stuck in the nineties. I mean, really! I'm just kidding, of course. It has been a lot of fun, and I also learnt quite a lot. I will keep a "bare metal" installation of Slackware64 around on my old Pentium IV system. Generally though, my priorities changed now that I've become a (born-again) Christian, so I'm cutting back a bit on computer usage. I wish Slackware and the SlackBuilds.org project all the best, it was and is certainly a pleasant community with friendly and helpful people. Cheers! Leonard From yth at ythogtha.org Mon Jul 2 16:57:36 2018 From: yth at ythogtha.org (Ythogtha) Date: Mon, 2 Jul 2018 18:57:36 +0200 Subject: [Slackbuilds-users] sqldiff and other SQLite tools Message-ID: <20180702185736.65a4fa4de71036902e947785@ythogtha.org> Hi everybody ! I was searching for the SQLite tool called sqldiff, and didn't find it anywhere on Slackware. The SQLite tools are part of the SQLite source code, but are different targets, and they don't seem to be included in Slackware64. Furthermore, I haven't found a SlackBuild making them available. Have I missed something, or may I start creating a new SlackBuild for them ? I'm not completely sure of their usefulness, but I have a practical use for sqldiff, so there's motivation enough for me. And I have no clue (yet) about what the other SQLite tools are about either ^^ -- Arnaud From yalhcru at gmail.com Mon Jul 2 18:36:41 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 2 Jul 2018 14:36:41 -0400 Subject: [Slackbuilds-users] sqldiff and other SQLite tools In-Reply-To: <20180702185736.65a4fa4de71036902e947785@ythogtha.org> References: <20180702185736.65a4fa4de71036902e947785@ythogtha.org> Message-ID: On 7/2/18, Ythogtha wrote: > The SQLite tools are part of the SQLite source code, but are different > targets, and they don't seem to be included in Slackware64. I had to do something like this, create a python-keybinder build. The python bindings are in the keybinder source, but the Slack keybinder package doesn't include them. Yours could be called "sqlite3-tools" or "sqlite3-utilities" or "sqlite3-extras"... Keep your version in sync with Slackware's sqlite3 version, and be extra careful not to overwrite anything in the sqlite3 package... From jebrhansen+SBo at gmail.com Mon Jul 2 18:56:17 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Mon, 2 Jul 2018 12:56:17 -0600 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: References: <65d4bdeb-ab94-de60-81dd-ab33916b0b9e@slint.fr> Message-ID: On Mon, Jul 2, 2018, 4:20 AM Matteo Bernardini wrote: > 2018-07-02 12:08 GMT+02:00 Didier Spaier : > > > > Should we say "Thank you!" to a SlackBuild maintainer who provides an > > upgrade to a shared library so that the 172 packages that rely on it are > > now broken? > > > > > > Yes repology is an useful tool, but blindly upgrade all and every > > SlackBuild wouldn't be a good thing IMO. > > > > Have a good day, > > > > Didier > > > > PS Yes I know, the user has no obligation to apply an update. But not > > all users are aware of the possible consequences of doing that. > > I totally agree. > > let me say also that the ones who browse repology and then write to > maintainers "your SlackBuilds are outdated!" should take in account > the above: there could be a lot of different reasons why some packages > are not upgraded, not counting the false positives that repology often > list as "upgrades". > > Matteo > I found I was losing track of what packages I was intending to keep at their current versions and for what reason, so I ended up creating a page on my github to allow me (and others) to easily see if I just wasn't aware of an update or if I specifically decided to not update that program and for what reason. https://github.com/bassmadrigal/slackbuilds/blob/master/version-check.md That being said, I do use repology all the time so I can be made aware of some updates, then I can look over those updates and see if there's a good enough reason to update them. It's a great additional tool in the toolbox. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rvnues at disroot.org Mon Jul 2 19:00:30 2018 From: rvnues at disroot.org (rob van nues) Date: Mon, 2 Jul 2018 20:00:30 +0100 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 In-Reply-To: References: Message-ID: <20180702200030.3ccdcd53@knotsUL> On Mon, 02 Jul 2018 16:58:06 +0000 slackbuilds-users-request at slackbuilds.org wrote: > Maintainers emails are pretty public in the SBo repository. Well, that is fairly specific environment compared to the big heap repology provides.. > A quick grep shows 761 different maintainers email, of which > 96 are somehow scrambled (of which 4 are yours ^^), and 665 are plain. > > Besides, the kind of scrambling we're talking about > (guy at domain dot tld, or john[dot]doe[at]domain[dot]tld) aren't > really a difficulty for spammers. > I could write a script in 15 minutes that'll scrape plain and > scrambled emails off of any webpages, if they're scrambled like that. Maybe we should consider another way of contacting providers. > > So, well, I don't think you should be more worried now than > you were before. That's not the issue; the fact that personal details get transferred from SBo to another site who actively advertises these details on the basis of a facebook-like argumentation is something that can no longer be accepted as normal. According to eu laws people should be informed about this and asked to opt out if they want to. I do not see the need why repology should be able to publish my details without such provisions. I have repology to remove these details. I do not need and I do not want this kind of PR. And I think Sbo should think much harder than to make these details so publicly available. If they do, it should be via a layer in between; that is, for example, via an SBo-email address that represents the maintainer so that email-requests can be moderated/filtered. I do not want that details that have been in good faith passed on to SBo, are brought onto a platform that, when big and popular enough, will be sold/mined by agencies we are not thinking of as yet. Rob From matteo.bernardini at gmail.com Mon Jul 2 19:06:41 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 2 Jul 2018 21:06:41 +0200 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 In-Reply-To: <20180702200030.3ccdcd53@knotsUL> References: <20180702200030.3ccdcd53@knotsUL> Message-ID: 2018-07-02 21:00 GMT+02:00 rob van nues : > On Mon, 02 Jul 2018 16:58:06 +0000 > slackbuilds-users-request at slackbuilds.org wrote: > >> Maintainers emails are pretty public in the SBo repository. > > Well, that is fairly specific environment compared to the big heap > repology provides.. > >> A quick grep shows 761 different maintainers email, of which >> 96 are somehow scrambled (of which 4 are yours ^^), and 665 are plain. >> >> Besides, the kind of scrambling we're talking about >> (guy at domain dot tld, or john[dot]doe[at]domain[dot]tld) aren't >> really a difficulty for spammers. >> I could write a script in 15 minutes that'll scrape plain and >> scrambled emails off of any webpages, if they're scrambled like that. > > Maybe we should consider another way of contacting providers. >> >> So, well, I don't think you should be more worried now than >> you were before. > > That's not the issue; the fact that personal details get transferred > from SBo to another site who actively advertises these details > on the basis of a facebook-like argumentation is > something that can no longer be accepted as normal. > > According to eu laws people should be informed about this and asked to > opt out if they want to. I do not see the need why repology should be > able to publish my details without such provisions. > > I have repology to remove these details. I do not need and I do not > want this kind of PR. > > And I think Sbo should think much harder than to make these > details so publicly available. If they do, it should be via a layer in > between; that is, for example, via an SBo-email address that represents > the maintainer so that email-requests can be moderated/filtered. I do > not want that details that have been in good faith passed on to SBo, are > brought onto a platform that, when big and popular enough, will be > sold/mined by agencies we are not thinking of as yet. Rob, those datas have to be made available so that people can contact you as maintainer for your SlackBuilds, and they should be able to do it without passing through some form on the site: we absolutely don't have the resources to moderate all the mail addressed to maintainers. as they need to be public, anyone can grab them and use them as they like. if you are concerned about spam, IMHO, you should create an email address ad-hoc to maintain SlackBuilds. Matteo From kjhambrick at gmail.com Mon Jul 2 19:10:46 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Mon, 2 Jul 2018 14:10:46 -0500 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: References: <65d4bdeb-ab94-de60-81dd-ab33916b0b9e@slint.fr> Message-ID: Nice touch Jeremy ! -- kjh On Mon, Jul 2, 2018 at 1:56 PM, Jeremy Hansen wrote: > On Mon, Jul 2, 2018, 4:20 AM Matteo Bernardini < > matteo.bernardini at gmail.com> wrote: > >> 2018-07-02 12:08 GMT+02:00 Didier Spaier : >> > >> > Should we say "Thank you!" to a SlackBuild maintainer who provides an >> > upgrade to a shared library so that the 172 packages that rely on it are >> > now broken? >> > >> > >> > Yes repology is an useful tool, but blindly upgrade all and every >> > SlackBuild wouldn't be a good thing IMO. >> > >> > Have a good day, >> > >> > Didier >> > >> > PS Yes I know, the user has no obligation to apply an update. But not >> > all users are aware of the possible consequences of doing that. >> >> I totally agree. >> >> let me say also that the ones who browse repology and then write to >> maintainers "your SlackBuilds are outdated!" should take in account >> the above: there could be a lot of different reasons why some packages >> are not upgraded, not counting the false positives that repology often >> list as "upgrades". >> >> Matteo >> > > I found I was losing track of what packages I was intending to keep at > their current versions and for what reason, so I ended up creating a page > on my github to allow me (and others) to easily see if I just wasn't aware > of an update or if I specifically decided to not update that program and > for what reason. > > https://github.com/bassmadrigal/slackbuilds/blob/master/version-check.md > > That being said, I do use repology all the time so I can be made aware of > some updates, then I can look over those updates and see if there's a good > enough reason to update them. It's a great additional tool in the toolbox. > > Jeremy > >> > _______________________________________________ > 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 idlemoor at slackbuilds.org Mon Jul 2 22:10:04 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Mon, 2 Jul 2018 23:10:04 +0100 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 In-Reply-To: <20180702200030.3ccdcd53@knotsUL> References: <20180702200030.3ccdcd53@knotsUL> Message-ID: > That's not the issue; the fact that personal details get transferred > from SBo to another site who actively advertises these details > on the basis of a facebook-like argumentation is > something that can no longer be accepted as normal. Let me make this absolutely clear: Repology has those 'unscrambled' email addresses not because SBo gave those addresses to Repology -- we simply don't have them in 'unscrambled' format -- but because (as Arnaud explained) it is trivially easy to make a script that removes the variants of [at] [NO] [SPAM] etc. And that's what Repology has done, not because they want to expose people to risk, but because of people who invent multiple 'scrambled' variations of their names and email addresses, which cannot be correlated without removing the "spam traps". > According to eu laws people should be informed about this and asked to > opt out if they want to. I do not see the need why repology should be > able to publish my details without such provisions. SBo is operated in the USA, and Repology is operated in the Russian Federation. Each jurisdiction comes with its own obligations. In the case of Github, there's the DMCA :( > And I think Sbo should think much harder than to make these > details so publicly available. If they do, it should be via a layer in > between; that is, for example, via an SBo-email address that represents > the maintainer so that email-requests can be moderated/filtered. I do > not want that details that have been in good faith passed on to SBo, are > brought onto a platform that, when big and popular enough, will be > sold/mined by agencies we are not thinking of as yet. You can organise your own layer in between. Unlike almost every other software project, SBo tolerates pseudonyms for maintainers. We want you to read and reply to email at that address, and we can give your packages to somebody else if you don't. But we don't check proactively and it could even be a mailinator address. (The email address you use in the submission form is checked, but it does not need to be the same as the address in the .info file.) I'm pretty sure that the amount of spam I've had from participating at SBo is very close to zero -- whereas I once had a death threat from opposing The SCO Group. So please have a sense of proportion. Frankly, "spam trapping" your email is mostly pointless. If you're worried about "agencies we are not thinking of as yet", or death threats, you need a pseudonym, not a spam trap. And please can I say, it has sometimes been a significant pain for me when people have multiple variants of 'scrambled' email, because it makes it difficult to query git to discover whether a maintainer silently stopped maintaining eight years ago... Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From skaendo at excite.com Mon Jul 2 22:32:11 2018 From: skaendo at excite.com (Ed Ender) Date: Mon, 02 Jul 2018 18:32:11 -0400 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 Message-ID: <20180702183211.19195@web005.roc2.bluetie.com> -----Original Message----- From: "David Spencer" [idlemoor at slackbuilds.org] Date: 07/02/2018 05:10 PM To: "SlackBuilds.org Users List" Subject: Re: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 I have often wondered about why our emails are so visible. Personally, I would rather see a contact page that sends a email to the maintainer, but..... > IMHO, you should create an email address ad-hoc to maintain SlackBuilds. This is what I'm going to do and It'll be a real email address but I doubt that I'll ever check it. Ed From idlemoor at slackbuilds.org Mon Jul 2 22:36:22 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Mon, 2 Jul 2018 23:36:22 +0100 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 In-Reply-To: <20180702183211.19195@web005.roc2.bluetie.com> References: <20180702183211.19195@web005.roc2.bluetie.com> Message-ID: <38f81088-9f49-152f-4380-1c0fbc1ea8cf@slackbuilds.org> > This is what I'm going to do and It'll be a real email address but I doubt that > I'll ever check it. "I sent email to the maintainer but there was no reply" ... ... we all know what happens next. Cheers -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From skaendo at excite.com Mon Jul 2 22:53:56 2018 From: skaendo at excite.com (Ed Ender) Date: Mon, 02 Jul 2018 18:53:56 -0400 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 Message-ID: <20180702185356.3138@web002.roc2.bluetie.com> -----Original Message----- From: "David Spencer" [idlemoor at slackbuilds.org] Date: 07/02/2018 05:36 PM To: slackbuilds-users at slackbuilds.org Subject: Re: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 >"I sent email to the maintainer but there was no reply" ... > >... we all know what happens next. > >Cheers >-D. Sure, but as long as the messages eventually come across the maillist, it will be a message received. And I'm not married to my SlackBuilds, if someone can do a better job and wants them they need but ask. From idlemoor at slackbuilds.org Mon Jul 2 23:21:20 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Tue, 3 Jul 2018 00:21:20 +0100 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 In-Reply-To: <20180702185356.3138@web002.roc2.bluetie.com> References: <20180702185356.3138@web002.roc2.bluetie.com> Message-ID: <53ab735a-e89b-b3fd-2d6f-a8154713a962@slackbuilds.org> > Sure, but as long as the messages eventually come across the maillist, it will > be a message received. Reallocations don't always go via the mailing list. Additionally, the admins have at least 2 use cases for that: "Ed, there's a problem with your submission", and "Ed, would you like to join the elite family of git committers?" Most important, end users need a point of contact. Even if they used a webform to initiate contact, it would just send an email. > And I'm not married to my SlackBuilds, if someone > can do a better job and wants them they need but ask. How, when you're not reading at your published address? Not reading email is way out of proportion from the stated problem of spam. We need a common channel of communication that works. It's not a big request. This is really the only prerequisite of being a maintainer. It's your right not to read email, and it's your right to exclude yourself by insisting on that, but SBo is better with you than without you :) -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From dave at dawoodfall.net Tue Jul 3 07:19:00 2018 From: dave at dawoodfall.net (David Woodfall) Date: Tue, 3 Jul 2018 08:19:00 +0100 Subject: [Slackbuilds-users] Repology again Re: SlackBuilds-users Digest, Vol 147, Issue 2 In-Reply-To: <20180702140243.3c1be5db@knotsUL> References: <20180702130436.1fe68c32@knotsUL> <20180702140243.3c1be5db@knotsUL> Message-ID: <20180703071900.GC14797@blackswan> On Monday 2 July 2018 14:02, rob van nues put forth the proposition: > Well, it has been raised as an issue but the author cannot see the > problem > > https://github.com/repology/repology/issues/220 > > This is not what I expected when email addresses were published in info > files. Can we take them out?? > > On Mon, 2 Jul 2018 13:04:36 +0100 > rob van nues wrote: > > > On Mon, 02 Jul 2018 11:19:59 +0000 > > slackbuilds-users-request at slackbuilds.org wrote: > > > > > Date: Mon, 2 Jul 2018 09:15:50 +0300 > > > From: Petar Petrov > > > To: "SlackBuilds.org Users List" > > > Subject: [Slackbuilds-users] Repology: a way to track potential > > > updates > > > Message-ID: > > > > > > Content-Type: text/plain; charset="UTF-8" > > > > > > Hi guys, > > > > > > i recently came across the repology website: > > > > > > https://repology.org/ > > > > > > it compares packages between distributions and their versions. You > > > can search by package maintainer (I found myself by my email) and > > > get a list of potential updates. > > > > > > -petar > > > > Thanks, Petar; found out that I can update a package... > > > > What I find quite worrying is that the search by email works too > > well. > > > > Email addresses are somewhat scrambled in the info-files; so why does > > this site publish the unscrambled version that can lead to quite a bit > > of spam? This seems contrary to policies adhered to here. > > > > I will ask the maintainer amdmi3 at amdmi3.ru > > > > rob > > I've had public email addresses since I put my first website up umpteen years go, so I'm quite used to dealing with spam. However, my thoughts on this are that if people obfuscate their email then the Repology guys ought to respect that and leave them as they are. Just my ?0.02 -Dave -- Vini, vidi, Linux! -- Unknown source .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From sborg63 at disroot.org Tue Jul 3 08:41:04 2018 From: sborg63 at disroot.org (sborg63) Date: Tue, 3 Jul 2018 09:41:04 +0100 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 In-Reply-To: References: <20180702200030.3ccdcd53@knotsUL> Message-ID: <20180703094104.0fd0de73@knotsUL> On Mon, 2 Jul 2018 23:10:04 +0100 David Spencer wrote: > You can organise your own layer in between. Yes, one is forced to do so... Repology is of course just an example. Still, it is a bit steep to expect for people who contribute a couple of packages to set up their own middle layer to prevent this kind of risk. > And please can I say, it has sometimes been a significant pain for me > when people have multiple variants of 'scrambled' email, because it > makes it difficult to query git to discover whether a maintainer > silently stopped maintaining eight years ago... Well, let's turn this around. Is the fact that people somehow try to obfuscate their email address not a clear sign that they do not want this address to be recognized other than by people who really want to contact them because of some problem? Encouragingly, Repology no longer aims to bypass this intention. (https://github.com/repology/repology/issues/651). When you want to get rid of obfuscated emails one could think of combining SBo-submission with a mailing list like this one that relies on unscrambled email addresses. Why I suggest combining the submission with this mailing list: There is password protection to get on or off this mailing list; so, you already have a somehow protected database with 'real email addresses'. Such a non-public database with email-addresses from submitters (maintainers) will makes them contactable for people who might need these (like you). Give submitters the possibility to link these 'real email' addresses to some maintainer-pietje1-100 at slackbuilds.org alias. Publish the email-aliases in the info files and set up automatic email forwarding (not much moderation/storage needed). Sites like Github uses aliases if people want to opt out of publishing their email address. As any organisation relying on voluntary input one has to make it safe for contributors to submit their details. In this respect, it is worrying that while this mailing list is non-public, the archives of the email-exchanges show contact details AND are publicly available. One is protecting the server and this list from spam but why not also the contributors? Wouldn't it be "trivially easy to make a script that removes" the email addresses (or at least the domains) from the archives before (or after) publishing? Or one could put the archives behind a login barrier. Cheers, rob From idlemoor at slackbuilds.org Tue Jul 3 09:03:41 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Tue, 3 Jul 2018 10:03:41 +0100 Subject: [Slackbuilds-users] Repology a public emailaddress repository; SlackBuilds-users Digest, Vol 147, Issue 3 In-Reply-To: <20180703094104.0fd0de73@knotsUL> References: <20180702200030.3ccdcd53@knotsUL> <20180703094104.0fd0de73@knotsUL> Message-ID: On 03/07/18 09:41, sborg63 wrote: > Yes, one is forced to do so... Repology is of course just an > example. Still, it is a bit steep to expect for people who contribute a > couple of packages to set up their own middle layer to prevent this > kind of risk. Oh, come off it. The "risk" is trivial, and so is the effort of thinking of a new name for yourself and having a secondary mailbox. > When you want to get rid of obfuscated emails one could think of > combining SBo-submission with a mailing list like this one that relies > on unscrambled email addresses. *NO*. Combining separate datasets to unmask individuals is, legally and ethically, *very* *very* *bad*. (My day job involves both open data and GDPR, so I'm familiar with this stuff) > In this respect, it is worrying that while this mailing list is > non-public It isn't, it's public. Maybe more later, but #dayjob... -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From orbea at fredslev.dk Tue Jul 3 13:50:42 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Tue, 3 Jul 2018 06:50:42 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180602040121.GA4471@blackswan> Message-ID: <20180703065042.0bfcabcf@Akita.witch.org> Is there any news on updating Qt5? The version 5.7.1 is EOL and has known security issues that will not be fixed. Slackware is also the only distro terrible enough to use 5.7.1 according to repology. https://repology.org/metapackage/qt5/versions To be blunt, software that will fail with a supported release of Qt5 should be outright removed and Qt5 should be updated before the next weekly update. Its outright insulting that SBo would leave this issue unattended for so long. In the event that SBo is not willing to fix this asap (And I'm not willing to maintain Qt5) then I will exclusively support only AlienBob's Qt5 package for my own scripts and there will be no expectations that the Qt5 package at SBo will work or even should be used. From slackalaxy at gmail.com Tue Jul 3 14:01:01 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 3 Jul 2018 17:01:01 +0300 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180703065042.0bfcabcf@Akita.witch.org> References: <20180602040121.GA4471@blackswan> <20180703065042.0bfcabcf@Akita.witch.org> Message-ID: isn't AlienBob's QT5 the same version? http://www.slackware.com/~alien/slackbuilds/qt5/pkg64/14.2/ -petar On 3 July 2018 at 16:50, orbea at fredslev.dk wrote: > Is there any news on updating Qt5? The version 5.7.1 is EOL and has > known security issues that will not be fixed. Slackware is also the > only distro terrible enough to use 5.7.1 according to repology. > > https://repology.org/metapackage/qt5/versions > > To be blunt, software that will fail with a supported release of Qt5 > should be outright removed and Qt5 should be updated before the next > weekly update. Its outright insulting that SBo would leave this issue > unattended for so long. > > In the event that SBo is not willing to fix this asap (And I'm not > willing to maintain Qt5) then I will exclusively support only > AlienBob's Qt5 package for my own scripts and there will be no > expectations that the Qt5 package at SBo will work or even should be > used. > _______________________________________________ > 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 orbea at fredslev.dk Tue Jul 3 14:20:38 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Tue, 3 Jul 2018 07:20:38 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: Message-ID: <20180703072038.66163eaf@Akita.witch.org> Yes, it occurred to me after I hit send that I should of been clearer. I meant the qt-5.9.* package for current AlienBob maintains. I'll build it on 14.2 and test that if needed... From orbea at fredslev.dk Tue Jul 3 14:31:02 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Tue, 3 Jul 2018 07:31:02 -0700 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: Message-ID: <20180703073102.40fe94a3@Akita.witch.org> I just want to point out that when I first started using repology I had many false positive when looking at my own packages. However most of these have been solved quickly by e-mailing the repology maintainer whose e-mail is listed on their site at the bottom of the front page. From slackbuilds at jaxartes.net Tue Jul 3 14:39:46 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 03 Jul 2018 14:39:46 +0000 Subject: [Slackbuilds-users] Repology: a way to track potential updates In-Reply-To: <20180703073102.40fe94a3@Akita.witch.org> References: <20180703073102.40fe94a3@Akita.witch.org> Message-ID: On July 3, 2018 2:31:02 PM UTC, "orbea at fredslev.dk" wrote: >I just want to point out that when I first started using repology I had >many false positive when looking at my own packages. However most of >these have been solved quickly by e-mailing the repology maintainer >whose e-mail is listed on their site at the bottom of the front page. On every metapackage's page, there is a link that allows you to report issues. From sam_web at yahoo.de Tue Jul 3 15:13:42 2018 From: sam_web at yahoo.de (Marek Srejma) Date: Tue, 3 Jul 2018 17:13:42 +0200 Subject: [Slackbuilds-users] Luakit version change from 2.1 to 2.0 Message-ID: Hi, the luakit SlackBuild I submitted and which is now on the pending list, needs to be changed to version 2.0, since there's no 2.1 source package anymore on github. Also the md5 checksum changed. I attached a patch file. Thanks. Marek -------------- next part -------------- A non-text attachment was scrubbed... Name: luakit_2.1_to_2.0.patch Type: text/x-patch Size: 955 bytes Desc: not available URL: From johannes at schoepfer.info Tue Jul 3 17:16:00 2018 From: johannes at schoepfer.info (=?ISO-8859-1?Q?Johannes_Sch=F6pfer?=) Date: Tue, 03 Jul 2018 19:16:00 +0200 Subject: [Slackbuilds-users] qt5 is sorely in need of an update Message-ID: Maybe you meant this by EOL also, the source mentioned in qt5.info has vanished. Sorry if this is already known by everybody, i didn't follow the qt discussion yet. http://download.qt.io/official_releases/qt/5.7/5.7.1/single/qt-everywhere-opensource-src-5.7.1.tar.xzAm 03.07.2018 3:50 nachm. schrieb orbea at fredslev.dk: > > Is there any news on updating Qt5? The version 5.7.1 is EOL and has > known security issues that will not be fixed. Slackware is also the > only distro terrible enough to use 5.7.1 according to repology. > > https://repology.org/metapackage/qt5/versions > > To be blunt, software that will fail with a supported release of Qt5 > should be outright removed and Qt5 should be updated before the next > weekly update. Its outright insulting that SBo would leave this issue > unattended for so long. > > In the event that SBo is not willing to fix this asap (And I'm not > willing to maintain Qt5) then I will exclusively support only > AlienBob's Qt5 package for my own scripts and there will be no > expectations that the Qt5 package at SBo will work or even should be > used. > _______________________________________________ > 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 orbea at fredslev.dk Tue Jul 3 17:40:40 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Tue, 3 Jul 2018 10:40:40 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: Message-ID: <20180703104040.25c89823@Akita.witch.org> > Maybe you meant this by EOL also, the source mentioned in qt5.info > has vanished. Sorry if this is already known by everybody, i didn't > follow the qt discussion yet. I didn't even notice that yet! I meant that Qt5 upstream released 5.7.1 in December 14 2016 and will not update it again. https://wiki.qt.io/Qt_5.7_Release When programs I use will soon no longer support releases older than 5.9 I can not complain to them that it will no longer build in Slackware because by all means we should of updated literally years ago... From yalhcru at gmail.com Tue Jul 3 18:03:43 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 3 Jul 2018 14:03:43 -0400 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180703104040.25c89823@Akita.witch.org> References: <20180703104040.25c89823@Akita.witch.org> Message-ID: On 7/3/18, orbea at fredslev.dk wrote: > > When programs I use will soon no longer support releases older than > 5.9 I can not complain to them that it will no longer build in > Slackware because by all means we should of updated literally years > ago... You (or whoever) could submit a qt59 or qt5-new or something like that, and the stuff that requires qt 5.9 or newer could list that as a dep. That, or if the old qt5 maintainer's OK with the change, rename the existing qt5 to qt5-legacy and someone can submit a new qt5 build and keep it up to date. Anything that won't build with the new qt5 has the dep changed to qt5-legacy (more work that the previous option). Is the problem just that the maintainer's gone missing, or is he answering emails and giving out a reason why he won't update the build? From larryhaja at gmail.com Tue Jul 3 19:14:37 2018 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 3 Jul 2018 12:14:37 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> Message-ID: On Tue, Jul 3, 2018 at 11:03 AM B Watson wrote: > On 7/3/18, orbea at fredslev.dk wrote: > > > > When programs I use will soon no longer support releases older than > > 5.9 I can not complain to them that it will no longer build in > > Slackware because by all means we should of updated literally years > > ago... > > You (or whoever) could submit a qt59 or qt5-new or something like that, > and the stuff that requires qt 5.9 or newer could list that as a dep. > > That, or if the old qt5 maintainer's OK with the change, rename the > existing qt5 to qt5-legacy and someone can submit a new qt5 build and > keep it up to date. Anything that won't build with the new qt5 has the > dep changed to qt5-legacy (more work that the previous option). > > Is the problem just that the maintainer's gone missing, or is he answering > emails and giving out a reason why he won't update the build? > I'm here and I did respond if you look at this email chain. Issue is that newer PyQt5 versions rely on a newer version of sip that comes with Slackware 14.2. Last I remember someone was going to look at packaging a newer sip pacakge that can either replace or run alongside the stock sip package in Slackware 14.2. I don't have time to investigate this. If the ultimate goal is to have a new version of qt5, than someone can create a package called qt59 or whatever to satisfy a dependency. If someone does take over qt5 and upgrade then it would be up to them to make sure the dependencies work after the update. Upgrading a package like qt5 is a big ask as it is a big package itself to compile and there are multiple dependencies to test. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Tue Jul 3 20:05:07 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Tue, 03 Jul 2018 23:05:07 +0300 Subject: [Slackbuilds-users] Wrong permissions for evdev-1.0.0-py2.7.egg-info files Message-ID: <1530648307.2810535.1429035104.7A2916AE@webmail.messagingengine.com> Hello, There is a problem with python-evdev package (which could have a general nature). Files in the directory /usr/lib64/python2.7/site-packages/evdev-1.0.0-py2.7.egg-info/ have permission 660 and, thus, unreadable by a non-root. This breaks programs that use python-evdev, for example, whipper stops with error: IOError: [Errno 13] Permission denied: '/usr/lib64/python2.7/site-packages/evdev-1.0.0-py2.7.egg-info/PKG-INFO' chmod 644 fixes the problem. python-evdev.SlackBuild doesn't change permissions, so the similar problem can occur for any python module. I think that python setup.py install doesn't set correct permissions, hence SlackBuilds must fix permissions after this. If I'm right, then the python template needs a correction. Best regards, Alexander From yalhcru at gmail.com Tue Jul 3 20:19:30 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 3 Jul 2018 16:19:30 -0400 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> Message-ID: On 7/3/18, Larry Hajali wrote: > I'm here and I did respond if you look at this email chain. Sorry, haven't been following this thread until now... > Issue is that newer PyQt5 versions rely on a newer version of sip that > comes with Slackware 14.2. Hm. So if someone did build a newer qt5, they'd end up being able to run stuff written in C++ that uses it, but not Python as there'd be no way to build PyQt5... I sympathize, my zathura build and its plugins are stuck on an older version because they need a newer gtk3 than Slack 14.2 provides. The qt5 situation is worse because so much software uses it (nobody's clamoring for zathura updates, it's an application, not a library that other stuff needs). > Last I remember someone was going to look at packaging a newer sip > pacakge that can either replace or run alongside the stock sip package > in Slackware 14.2. I don't have time to investigate this. I wouldn't mind taking a look at this myself. "Run alongside", not "replace", and maybe instead of a separate package, it could be built in /tmp and used by the PyQt5 build. Kinda like Pat does with libmikmod, in his SDL SlackBuild. > If the ultimate goal is to have a new version of qt5, than someone can > create a package called qt59 or whatever to satisfy a dependency. Yah, that seems like the best way, at least until 15.0 gets released (assuming it has a new enough sip package). I guess there'd have to also be a PyQt59 to go along with qt59. From orbea at fredslev.dk Tue Jul 3 20:35:58 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Tue, 3 Jul 2018 13:35:58 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: Message-ID: <20180703133558.3bcb23bd@Akita.witch.org> > Is the problem just that the maintainer's gone missing, or is he > answering emails and giving out a reason why he won't update the > build? My issue is that this is a years old known packaging bug and no one has bothered to do anything about it despite complaining on numerous occasions here and on irc... The end result is a subpar and buggy Qt5 package which is quickly become less and less viable. Given the number of things that depend on it this really needs to be resolved sooner rather than later. > I wouldn't mind taking a look at this myself. "Run alongside", not > "replace", and maybe instead of a separate package, it could be built > in /tmp and used by the PyQt5 build. Kinda like Pat does with > libmikmod, in his SDL SlackBuild. This seems like a workable idea, as far as I can tell PyQt5 nor Qt5 actually link against sip and I'd guess its a only a build dependency? Another idea is to convince Pat to just update sip in 14.2, given the real problems its posing its not unreasonable. From chris.willing at iinet.net.au Tue Jul 3 22:02:15 2018 From: chris.willing at iinet.net.au (Christoph Willing) Date: Wed, 4 Jul 2018 08:02:15 +1000 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> Message-ID: On 04/07/18 06:19, B Watson wrote: > On 7/3/18, Larry Hajali wrote: >> I'm here and I did respond if you look at this email chain. > > Sorry, haven't been following this thread until now... > >> Issue is that newer PyQt5 versions rely on a newer version of sip that >> comes with Slackware 14.2. > > Hm. So if someone did build a newer qt5, they'd end up being able to run > stuff written in C++ that uses it, but not Python as there'd be no way > to build PyQt5... > > I sympathize, my zathura build and its plugins are stuck on an older > version because they need a newer gtk3 than Slack 14.2 provides. The qt5 > situation is worse because so much software uses it (nobody's clamoring > for zathura updates, it's an application, not a library that other > stuff needs). > >> Last I remember someone was going to look at packaging a newer sip >> pacakge that can either replace or run alongside the stock sip package >> in Slackware 14.2. I don't have time to investigate this. > > I wouldn't mind taking a look at this myself. "Run alongside", not > "replace", and maybe instead of a separate package, it could be built > in /tmp and used by the PyQt5 build. Kinda like Pat does with libmikmod, > in his SDL SlackBuild. > >> If the ultimate goal is to have a new version of qt5, than someone can >> create a package called qt59 or whatever to satisfy a dependency. > > Yah, that seems like the best way, at least until 15.0 gets released > (assuming it has a new enough sip package). I guess there'd have to also > be a PyQt59 to go along with qt59. Have a look at: https://www.riverbankcomputing.com/pipermail/pyqt/2018-June/040421.html which talks about new releases of PyQt using a private copy of the sip module. I haven't thought deeply into the ramifications but perhaps that would ease the problem of old sip in 14.2. chris From larryhaja at gmail.com Tue Jul 3 22:41:53 2018 From: larryhaja at gmail.com (Larry Hajali) Date: Tue, 3 Jul 2018 15:41:53 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> Message-ID: > > Have a look at: > > https://www.riverbankcomputing.com/pipermail/pyqt/2018-June/040421.html > > which talks about new releases of PyQt using a private copy of the sip > module. I haven't thought deeply into the ramifications but perhaps that > would ease the problem of old sip in 14.2. > Interesting. That might be a solution. I can take a look at that. --Larry -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Tue Jul 3 23:10:08 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 4 Jul 2018 06:10:08 +0700 Subject: [Slackbuilds-users] perl/txt2html missing dep In-Reply-To: References: Message-ID: <662c8c35-2ea4-1a0b-9140-ee847ba7acbc@slackbuilds.org> > Need REQUIRES="perl-YAML-Syck" in txt2html.info. Thanks for catching it. Pushed to 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 Tue Jul 3 23:21:52 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 4 Jul 2018 06:21:52 +0700 Subject: [Slackbuilds-users] prompt_toolkit version used no good for python-2.7 In-Reply-To: <2344713.IjMtIyWL1H@wintermute.sprawl.net> References: <20180702101724.4c2122df@knotsUL> <2344713.IjMtIyWL1H@wintermute.sprawl.net> Message-ID: <1d5855c0-8535-614f-0ece-8d25c7591b67@slackbuilds.org> >> Thanks for all the python builds. >> >> Recently, however, Sbo-upgrades killed my ipython/jupyter setup (in >> python-2.7). >> The problem lies with prompt_toolkit-2.0.3 in the slackbuild script for >> prompt_toolkit. This needs to be a version 1. > > I see this issue as well. I'm sure Dmitris will be happy to downgrade > prompt_toolkit for Python 2. The dependency chain for IPython and Jupyter is > quite complex so on occasion there are issues like this that come up! Dimitris have sent a new script prompt_toolkit1 and it's now in my branch. Ben, can you update your jupiter dep to this new script? 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 willysr at slackbuilds.org Tue Jul 3 23:25:04 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 4 Jul 2018 06:25:04 +0700 Subject: [Slackbuilds-users] Wrong permissions for evdev-1.0.0-py2.7.egg-info files In-Reply-To: <1530648307.2810535.1429035104.7A2916AE@webmail.messagingengine.com> References: <1530648307.2810535.1429035104.7A2916AE@webmail.messagingengine.com> Message-ID: > There is a problem with python-evdev package (which could have a general > nature). > > Files in the directory > /usr/lib64/python2.7/site-packages/evdev-1.0.0-py2.7.egg-info/ have > permission 660 and, thus, unreadable by a non-root. > > This breaks programs that use python-evdev, for example, whipper stops > with error: > > IOError: [Errno 13] Permission denied: '/usr/lib64/python2.7/site-packages/evdev-1.0.0-py2.7.egg-info/PKG-INFO' > > chmod 644 fixes the problem. > > python-evdev.SlackBuild doesn't change permissions, so the similar > problem can occur for any python module. > > I think that > python setup.py install > doesn't set correct permissions, hence SlackBuilds must fix permissions > after this. If I'm right, then the python template needs a correction. Thanks for spoting it. It has been 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 skaendo at excite.com Tue Jul 3 23:45:08 2018 From: skaendo at excite.com (Ed Ender) Date: Tue, 03 Jul 2018 19:45:08 -0400 Subject: [Slackbuilds-users] Wrong permissions for evdev-1.0.0-py2.7.egg-info files Message-ID: <20180703194508.8511@web001.roc2.bluetie.com> I thought that David had already fixed that: https://git.slackbuilds.org/slackbuilds/commit/?id=57fb210c8 -----Original Message----- From: "Willy Sudiarto Raharjo" [willysr at slackbuilds.org] Date: 07/03/2018 06:29 PM To: slackbuilds-users at slackbuilds.org Subject: Re: [Slackbuilds-users] Wrong permissions for evdev-1.0.0-py2.7.egg-info files > There is a problem with python-evdev package (which could have a general > nature). > > Files in the directory > /usr/lib64/python2.7/site-packages/evdev-1.0.0-py2.7.egg-info/ have > permission 660 and, thus, unreadable by a non-root. > > This breaks programs that use python-evdev, for example, whipper stops > with error: > > IOError: [Errno 13] Permission denied: '/usr/lib64/python2.7/site-packages/evdev-1.0.0-py2.7.egg-info/PKG-INFO' > > chmod 644 fixes the problem. > > python-evdev.SlackBuild doesn't change permissions, so the similar > problem can occur for any python module. > > I think that > python setup.py install > doesn't set correct permissions, hence SlackBuilds must fix permissions > after this. If I'm right, then the python template needs a correction. Thanks for spoting it. It has been fixed in my branch -- Willy Sudiarto Raharjo From willysr at slackbuilds.org Tue Jul 3 23:44:30 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 4 Jul 2018 06:44:30 +0700 Subject: [Slackbuilds-users] Wrong permissions for evdev-1.0.0-py2.7.egg-info files In-Reply-To: <20180703194508.8511@web001.roc2.bluetie.com> References: <20180703194508.8511@web001.roc2.bluetie.com> Message-ID: > I thought that David had already fixed that: > https://git.slackbuilds.org/slackbuilds/commit/?id=57fb210c8 Uh oh... i didn't look at his branch earlier i will delete my changes now Thanks again -- 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 slackbuilds at jaxartes.net Wed Jul 4 02:29:40 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 03 Jul 2018 19:29:40 -0700 Subject: [Slackbuilds-users] prompt_toolkit version used no good for python-2.7 In-Reply-To: <1d5855c0-8535-614f-0ece-8d25c7591b67@slackbuilds.org> References: <20180702101724.4c2122df@knotsUL> <2344713.IjMtIyWL1H@wintermute.sprawl.net> <1d5855c0-8535-614f-0ece-8d25c7591b67@slackbuilds.org> Message-ID: <2028268.dab06TrLVG@wintermute.sprawl.net> On Tuesday, 3 July 2018 16:21:52 PDT Willy Sudiarto Raharjo wrote: > >> Thanks for all the python builds. > >> > >> Recently, however, Sbo-upgrades killed my ipython/jupyter setup (in > >> python-2.7). > >> The problem lies with prompt_toolkit-2.0.3 in the slackbuild script for > >> prompt_toolkit. This needs to be a version 1. > > > > I see this issue as well. I'm sure Dmitris will be happy to downgrade > > prompt_toolkit for Python 2. The dependency chain for IPython and Jupyter > > is quite complex so on occasion there are issues like this that come up! > Dimitris have sent a new script prompt_toolkit1 and it's now in my branch. > > Ben, can you update your jupiter dep to this new script? Awesome, thanks Dimitris. Switched the ipython dependency with c88311. From xavier at maillard.im Wed Jul 4 13:15:09 2018 From: xavier at maillard.im (Xavier Maillard) Date: Wed, 4 Jul 2018 15:15:09 +0200 Subject: [Slackbuilds-users] [OT] Screen grabber ? In-Reply-To: (message from Kees Theunissen on Tue, 26 Jun 2018 18:35:59 +0200 (CEST)) References: <201806261505.w5QF5A4v003410@localhost.localdomain> Message-ID: <201807041315.w64DF9E6006522@localhost.localdomain> > Date: Tue, 26 Jun 2018 18:35:59 +0200 (CEST) > From: Kees Theunissen > > I always use "xv" (included in slackware since a very long time). > > Start xv, right-click on the xv window and click the "Grab" > button from the "xv controls" pop up. Thank you but as said, I am into a linux console aka. the thing right after the linux kernel has started with the "login:" prompt. I have no X running here (not yet at least). -- Xavier Maillard e/j:xavier at maillard.im w:www.maillard.im m: 06 52 18 63 43 GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B From xavier at maillard.im Wed Jul 4 13:24:38 2018 From: xavier at maillard.im (Xavier Maillard) Date: Wed, 4 Jul 2018 15:24:38 +0200 Subject: [Slackbuilds-users] [OT] Screen grabber ? In-Reply-To: <33d9090d-73f4-10de-cb03-0af5bcae2ff6@osh.id.au> (message from David O'Shaughnessy on Wed, 27 Jun 2018 15:31:54 +1000) References: <201806261505.w5QF5A4v003410@localhost.localdomain> <33d9090d-73f4-10de-cb03-0af5bcae2ff6@osh.id.au> Message-ID: <201807041324.w64DOcf5006550@localhost.localdomain> Hello, > scrot is another option on SBo if you like command line stuff. It does not seem to work directly without an X env running, does it? -- Xavier Maillard e/j:xavier at maillard.im w:www.maillard.im m: 06 52 18 63 43 GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B From xavier at maillard.im Wed Jul 4 13:25:32 2018 From: xavier at maillard.im (Xavier Maillard) Date: Wed, 4 Jul 2018 15:25:32 +0200 Subject: [Slackbuilds-users] [OT] Screen grabber ? In-Reply-To: <20180626194349.GA21058@jbsupah> (message from Jostein Berntsen on Tue, 26 Jun 2018 21:43:49 +0200) References: <201806261505.w5QF5A4v003410@localhost.localdomain> <20180626194349.GA21058@jbsupah> Message-ID: <201807041325.w64DPWN8006556@localhost.localdomain> Hello, > The "screengrab" program also works quite well. Is it part of a bigger package/project on SBo ? Regards -- Xavier Maillard e/j:xavier at maillard.im w:www.maillard.im m: 06 52 18 63 43 GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B From gen-bch at useyouresp.org.uk Wed Jul 4 13:37:00 2018 From: gen-bch at useyouresp.org.uk (Habs) Date: Wed, 4 Jul 2018 14:37:00 +0100 (BST) Subject: [Slackbuilds-users] [OT] Screen grabber ? In-Reply-To: <201807041315.w64DF9E6006522@localhost.localdomain> References: <201806261505.w5QF5A4v003410@localhost.localdomain> <201807041315.w64DF9E6006522@localhost.localdomain> Message-ID: On Wed, 4 Jul 2018, Xavier Maillard wrote: >> Date: Tue, 26 Jun 2018 18:35:59 +0200 (CEST) >> From: Kees Theunissen >> >> I always use "xv" (included in slackware since a very long time). >> >> Start xv, right-click on the xv window and click the "Grab" >> button from the "xv controls" pop up. > > Thank you but as said, I am into a linux console aka. the thing right > after the linux kernel has started with the "login:" prompt. > > I have no X running here (not yet at least). > -- > Xavier Maillard > e/j:xavier at maillard.im w:www.maillard.im > m: 06 52 18 63 43 > > GPG: 9983 DCA1 1FAC 8DA7 653A > F9AA BA49 09B7 8F04 DE1B > _______________________________________________ > 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/ > > A quick search threw up this; is this any help: http://www.pc-freak.net/blog/how-to-make-screenshot-in-devtty-console-on-gnu-linux-taking-picture-jpeg-png-snapshot-of-text-console-in-systems-without-graphical-environment/ or 'fbcat' on slackbuilds maybe regards H. --- Sent using Alpine/Pine, a text based MUA --- Tox-id: 96945E2B98A02A58E86B08D104B9B9DBDC9C9CBAC04D8E96274AAC62CC50747FCB281137C07A From yth at ythogtha.org Wed Jul 4 13:53:24 2018 From: yth at ythogtha.org (Ythogtha) Date: Wed, 4 Jul 2018 15:53:24 +0200 Subject: [Slackbuilds-users] sqldiff and other SQLite tools In-Reply-To: References: <20180702185736.65a4fa4de71036902e947785@ythogtha.org> Message-ID: <20180704155324.ab6ee34aeeccfde3c61a9faa@ythogtha.org> > On 7/2/18, Ythogtha wrote: > > > The SQLite tools are part of the SQLite source code, but are > > different targets, and they don't seem to be included in Slackware64. > > I had to do something like this, create a python-keybinder build. The > python bindings are in the keybinder source, but the Slack keybinder > package doesn't include them. Yours could be called "sqlite3-tools" or > "sqlite3-utilities" or "sqlite3-extras"... > > Keep your version in sync with Slackware's sqlite3 version, and be extra > careful not to overwrite anything in the sqlite3 package... Ok, thanks for your answer ! As I wasn't able to properly distinguish what tools might or might not be useful inside the SQLite tool folder - about none seemed useful except maybe when you have a use for them - I decided to only create an sqldiff package. Besides the sqlite-tools zip provided by SQLite includes only sqlite3 which is included the slackware SQLite package, sqlite3_analyzer which is included in the slackware tcl package and sqldiff. It seems logical to only create an sqldiff SlackBuild. So I used the slackware sqlite source, the URL I used is actually from the official slackware mirror source directory. And I cut'n'pasted the configure options for SQLite, so it should be the most compatible with slackware's version of SQLite. Here goes to the submit page ! Have a nice day :) -- Arnaud From pilbender at gmail.com Wed Jul 4 18:28:01 2018 From: pilbender at gmail.com (Richard Scott Smith) Date: Wed, 4 Jul 2018 11:28:01 -0700 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 147, Issue 7 In-Reply-To: References: Message-ID: > Date: Tue, 3 Jul 2018 12:14:37 -0700 > From: Larry Hajali > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] qt5 is sorely in need of an update > Message-ID: > gmail.com> > Content-Type: text/plain; charset="utf-8" > > On Tue, Jul 3, 2018 at 11:03 AM B Watson wrote: > > > On 7/3/18, orbea at fredslev.dk wrote: > > > > > > When programs I use will soon no longer support releases older than > > > 5.9 I can not complain to them that it will no longer build in > > > Slackware because by all means we should of updated literally years > > > ago... > > > > You (or whoever) could submit a qt59 or qt5-new or something like that, > > and the stuff that requires qt 5.9 or newer could list that as a dep. > > > > That, or if the old qt5 maintainer's OK with the change, rename the > > existing qt5 to qt5-legacy and someone can submit a new qt5 build and > > keep it up to date. Anything that won't build with the new qt5 has the > > dep changed to qt5-legacy (more work that the previous option). > > > > Is the problem just that the maintainer's gone missing, or is he > answering > > emails and giving out a reason why he won't update the build? > > > I'm here and I did respond if you look at this email chain. > > Issue is that newer PyQt5 versions rely on a newer version of sip that > comes with Slackware 14.2. Last I remember someone was going to look at > packaging a newer sip pacakge that can either replace or run alongside the > stock sip package in Slackware 14.2. I don't have time to investigate > this. > > If the ultimate goal is to have a new version of qt5, than someone can > create a package called qt59 or whatever to satisfy a dependency. If > someone does take over qt5 and upgrade then it would be up to them to make > sure the dependencies work after the update. Upgrading a package like qt5 > is a big ask as it is a big package itself to compile and there are > multiple dependencies to test. > > --Larry > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: attachments/20180703/500f9ec5/attachment-0001.html> > First, thank you for your work on qt5. +1 on moving qt 5.7 to legacy and making 5.9.x the current 14.2 Slackbuild. I have been running into this issue for the last couple of years. Zoom is one of the biggest problems as I use it for work all the time and it complains about qt5 being too old. I live with it and people I work with hate me for using Slackware because I have "issues". I symlink, I update nvidia drivers, I monkey with it until I've been able to get it to work on one of my 4 Slackware systems. My Intel graphics based systems are a lost cause. I don't even know what sip is, so I'm inclined to say I don't care about it. I like Slackware so much that I'm willing to work around most any issues simply because Slackware so great. I've used a lot of distros and all of them piss me off more than Slackware. For me, I'm speculating that updating qt5 would be less effort and heartache than working around what's there now. Has anyone used Alien Bob's Slackware current qt 5.9 install on Slackware 14.2? If that works, and creates a few "issues" I don't care about, that might be a worthy option. scott -------------- next part -------------- An HTML attachment was scrubbed... URL: From k.venken at online.be Wed Jul 4 18:37:57 2018 From: k.venken at online.be (Karel Venken) Date: Wed, 04 Jul 2018 20:37:57 +0200 Subject: [Slackbuilds-users] [OT] Screen grabber ? In-Reply-To: <201806261505.w5QF5A4v003410@localhost.localdomain> References: <201806261505.w5QF5A4v003410@localhost.localdomain> Message-ID: <5B3D1405.3040709@online.be> Xavier Maillard wrote: > Hello buddies, > > I am using a GPD pocket device and I am pretty happy with it running > pretty exclusively in the linux console. > > I am debugging a tool which does not react correctly when trying to > interrupt it. The project owner would like me to give him 1) the way > to reproduce the problem and 2) a "screenshot". > > I tried to look for a tool from the SBo repository but as far as I > know, there is not such tool. > > What would you recommend ? (I would then give a slackbuild script). > > Thank you > I am using xwd (standard available in Slackware 14.1). xwd -root -display :0 -out screendump You can then view the result with xv or xwud. K. From dave at dawoodfall.net Wed Jul 4 19:26:44 2018 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 4 Jul 2018 20:26:44 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> Message-ID: <20180704192644.GB28893@blackswan> On Tuesday 3 July 2018 12:14, Larry Hajali put forth the proposition: > On Tue, Jul 3, 2018 at 11:03 AM B Watson wrote: > > > On 7/3/18, orbea at fredslev.dk wrote: > > > > > > When programs I use will soon no longer support releases older than > > > 5.9 I can not complain to them that it will no longer build in > > > Slackware because by all means we should of updated literally years > > > ago... > > > > You (or whoever) could submit a qt59 or qt5-new or something like that, > > and the stuff that requires qt 5.9 or newer could list that as a dep. > > > > That, or if the old qt5 maintainer's OK with the change, rename the > > existing qt5 to qt5-legacy and someone can submit a new qt5 build and > > keep it up to date. Anything that won't build with the new qt5 has the > > dep changed to qt5-legacy (more work that the previous option). > > > > Is the problem just that the maintainer's gone missing, or is he answering > > emails and giving out a reason why he won't update the build? > > > I'm here and I did respond if you look at this email chain. > > Issue is that newer PyQt5 versions rely on a newer version of sip that > comes with Slackware 14.2. Last I remember someone was going to look at > packaging a newer sip pacakge that can either replace or run alongside the > stock sip package in Slackware 14.2. I don't have time to investigate this. I did say that I would look into a newer sip. Sorry, I just haven't had time yet. One option could be to download sip and install it but with it, and all the references, renamed. I did this with the new pudb that installed a custom urwid that didn't interfere with the stock, but that was fairly simple because pudb is a small application compared to PyQt5. I will try to get on to it ASAP -Dave -- How should I know if it works? That's what beta testers are for. I only coded it. -- Attributed to Linus Torvalds, somewhere in a posting .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From yalhcru at gmail.com Thu Jul 5 00:17:13 2018 From: yalhcru at gmail.com (B Watson) Date: Wed, 4 Jul 2018 20:17:13 -0400 Subject: [Slackbuilds-users] mixxx bogus udev rules Message-ID: After building (but not actually *installing*) audio/mixxx, I notice this in dmesg output: [4463837.124783] udevd[598]: invalid key/value pair in file /etc/udev/rules.d/mixxx.usb.rules on line 7, starting at character 99 ('#') [4463837.124791] udevd[598]: hint: comments can only start at beginning of line [4463837.124801] udevd[598]: invalid key/value pair in file /etc/udev/rules.d/mixxx.usb.rules on line 8, starting at character 99 ('#') [4463837.124803] udevd[598]: hint: comments can only start at beginning of line There are 2 issues here: #1: The udev rules from upstream are invalid (causing this noise in dmesg). Easy to fix: sed -i 's,\(.*\) \(#.*\),\n\2\n\1,' res/linux/mixxx.usb.rules ...somewhere in mixxx.SlackBuild before the 'scons' commands. #2: scons is installing the udev rules directly to /etc, rather than $PKG/etc. >From the build log: ... Install file: "res/linux/mixxx.usb.rules" as "/etc/udev/rules.d/mixxx.usb.rules" scons: done building targets. ... Looks like this is the only file (the rest of the "Install file" lines are going to /tmp/SBo/package-mixxx/). It also looks like it can be fixed with a one-line sed in the SlackBuild: sed -i "s,/etc/udev/rules.d,$PKG&," src/SConscript ...somewhere before the 'scons' commands. From xavier at maillard.im Thu Jul 5 04:50:19 2018 From: xavier at maillard.im (Xavier Maillard) Date: Thu, 5 Jul 2018 06:50:19 +0200 Subject: [Slackbuilds-users] Giving up maintainership of my slackbuiilds In-Reply-To: (message from B Watson on Thu, 28 Jun 2018 15:06:01 -0400) References: <0MCtql-1fQaNX0NJj-009czG@mail.gmx.com> Message-ID: <201807050450.w654oJT1006885@localhost.localdomain> Heya, > If nobody else wants them, I'll take these: > > desktop/ctwm > desktop/cwm > misc/abduco > misc/paperkey > network/nmh > network/vimb I will take misc/paperkey network/nmh if it is still possible. -- Xavier Maillard e/j:xavier at maillard.im w:www.maillard.im m: 06 52 18 63 43 GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B From xavier at maillard.im Thu Jul 5 20:15:27 2018 From: xavier at maillard.im (Xavier Maillard) Date: Thu, 5 Jul 2018 22:15:27 +0200 Subject: [Slackbuilds-users] keybase: md5 mismatch Message-ID: <201807052015.w65KFRjk032321@localhost.localdomain> Hello, just a word to signal a MD5 missmatch for the keybase SBo script: Checking MD5SUM: MD5SUM check for client-2.0.0.tar.gz ... FAILED! Expected: c17ff9f3bcee8265a5cd6ee133318e6a Found: 4c8f77197184c5a5d9552272fc161e10 Regards -- Xavier Maillard e/j:xavier at maillard.im w:www.maillard.im m: 06 52 18 63 43 GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B From xavier at maillard.im Thu Jul 5 20:23:51 2018 From: xavier at maillard.im (Xavier Maillard) Date: Thu, 5 Jul 2018 22:23:51 +0200 Subject: [Slackbuilds-users] keybase: md5 mismatch In-Reply-To: <201807052015.w65KFRjk032321@localhost.localdomain> (message from Xavier Maillard on Thu, 5 Jul 2018 22:15:27 +0200) References: <201807052015.w65KFRjk032321@localhost.localdomain> Message-ID: <201807052023.w65KNpro008950@localhost.localdomain> Hello again, things are more complex than expected, keybase is just not building at all: client-2.0.0/shared/wallets/wallet/index.stories.js client-2.0.0/shared/yarn.lock This will take a while to build. Please be patient. keybase.SlackBuild.build: line 82: /usr/lib64/go1.9.2/go/bin/go: No such file or directory keybase: Would you like to continue processing the rest of the queue or would you like to abort? If this failed package is a dependency of another package in the queue then it may not make sense to continue. Precisely, go is installed from the SBo repo *but* it is 1.10.2 version :/ Who is to blame here ? (joking) -- Xavier Maillard e/j:xavier at maillard.im w:www.maillard.im m: 06 52 18 63 43 GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B From willysr at slackbuilds.org Thu Jul 5 20:39:31 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 6 Jul 2018 03:39:31 +0700 Subject: [Slackbuilds-users] keybase: md5 mismatch In-Reply-To: <201807052023.w65KNpro008950@localhost.localdomain> References: <201807052015.w65KFRjk032321@localhost.localdomain> <201807052023.w65KNpro008950@localhost.localdomain> Message-ID: > things are more complex than expected, keybase is just not building at all: > > client-2.0.0/shared/wallets/wallet/index.stories.js > client-2.0.0/shared/yarn.lock > This will take a while to build. Please be patient. > > keybase.SlackBuild.build: line 82: /usr/lib64/go1.9.2/go/bin/go: No such file or directory > > keybase: > Would you like to continue processing the rest of the > queue or would you like to abort? If this failed > package is a dependency of another package in the queue > then it may not make sense to continue. > > > Precisely, go is installed from the SBo repo *but* it is 1.10.2 > version :/ Have you used "su -" instead of just su to make sure you get the updated environment, especially GOROOT environment variable? PS: I have an updated keybase 2.1.1 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 dave at dawoodfall.net Fri Jul 6 02:41:27 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 6 Jul 2018 03:41:27 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> Message-ID: <20180706024127.GL2038@blackswan> On Tuesday 3 July 2018 12:14, Larry Hajali put forth the proposition: > On Tue, Jul 3, 2018 at 11:03 AM B Watson wrote: > > > On 7/3/18, orbea at fredslev.dk wrote: > > > > > > When programs I use will soon no longer support releases older than > > > 5.9 I can not complain to them that it will no longer build in > > > Slackware because by all means we should of updated literally years > > > ago... > > > > You (or whoever) could submit a qt59 or qt5-new or something like that, > > and the stuff that requires qt 5.9 or newer could list that as a dep. > > > > That, or if the old qt5 maintainer's OK with the change, rename the > > existing qt5 to qt5-legacy and someone can submit a new qt5 build and > > keep it up to date. Anything that won't build with the new qt5 has the > > dep changed to qt5-legacy (more work that the previous option). > > > > Is the problem just that the maintainer's gone missing, or is he answering > > emails and giving out a reason why he won't update the build? > > > I'm here and I did respond if you look at this email chain. > > Issue is that newer PyQt5 versions rely on a newer version of sip that > comes with Slackware 14.2. Last I remember someone was going to look at > packaging a newer sip pacakge that can either replace or run alongside the > stock sip package in Slackware 14.2. I don't have time to investigate this. > > If the ultimate goal is to have a new version of qt5, than someone can > create a package called qt59 or whatever to satisfy a dependency. If > someone does take over qt5 and upgrade then it would be up to them to make > sure the dependencies work after the update. Upgrading a package like qt5 > is a big ask as it is a big package itself to compile and there are > multiple dependencies to test. > > --Larry OK. I've got what looks like a working build for sip-4.19.6. I've named it python2-sip. PyQt5 built with it without complaining. I tested with Qt5-5.9.2 but I will try with 5.10.1 and 5.11 next. Larry, I've also uploaded your PyQt5 slackbuild with the modifications needed. The .info has the download URL for PyQt5-5.9.2. The only issue I had was finding a more up-to-date Qt5-webkit because there only seems to be some rc version for 5.9 at the location in the original .info, so I used my build of the fork by annulen. 5.7.1 wouldn't build. Unless you know of a link to an upstream release of 5.9.x? I haven't tested this with anything yet, so this is a call for testers please. Link: http://dawoodfall.net/testing/ -Dave -- We come to bury DOS, not to praise it. -- Paul Vojta, vojta at math.berkeley.edu .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From dave at dawoodfall.net Fri Jul 6 02:44:04 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 6 Jul 2018 03:44:04 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180706024127.GL2038@blackswan> References: <20180703104040.25c89823@Akita.witch.org> <20180706024127.GL2038@blackswan> Message-ID: <20180706024404.GM2038@blackswan> On Friday 6 July 2018 03:41, Dave Woodfall put forth the proposition: > On Tuesday 3 July 2018 12:14, > Larry Hajali put forth the proposition: > > On Tue, Jul 3, 2018 at 11:03 AM B Watson wrote: > > > > > On 7/3/18, orbea at fredslev.dk wrote: > > > > > > > > When programs I use will soon no longer support releases older than > > > > 5.9 I can not complain to them that it will no longer build in > > > > Slackware because by all means we should of updated literally years > > > > ago... > > > > > > You (or whoever) could submit a qt59 or qt5-new or something like that, > > > and the stuff that requires qt 5.9 or newer could list that as a dep. > > > > > > That, or if the old qt5 maintainer's OK with the change, rename the > > > existing qt5 to qt5-legacy and someone can submit a new qt5 build and > > > keep it up to date. Anything that won't build with the new qt5 has the > > > dep changed to qt5-legacy (more work that the previous option). > > > > > > Is the problem just that the maintainer's gone missing, or is he answering > > > emails and giving out a reason why he won't update the build? > > > > > I'm here and I did respond if you look at this email chain. > > > > Issue is that newer PyQt5 versions rely on a newer version of sip that > > comes with Slackware 14.2. Last I remember someone was going to look at > > packaging a newer sip pacakge that can either replace or run alongside the > > stock sip package in Slackware 14.2. I don't have time to investigate this. > > > > If the ultimate goal is to have a new version of qt5, than someone can > > create a package called qt59 or whatever to satisfy a dependency. If > > someone does take over qt5 and upgrade then it would be up to them to make > > sure the dependencies work after the update. Upgrading a package like qt5 > > is a big ask as it is a big package itself to compile and there are > > multiple dependencies to test. > > > > --Larry > > OK. I've got what looks like a working build for sip-4.19.6. I've > named it python2-sip. > > PyQt5 built with it without complaining. I tested with Qt5-5.9.2 but I > will try with 5.10.1 and 5.11 next. > > Larry, I've also uploaded your PyQt5 slackbuild with the > modifications needed. The .info has the download URL for PyQt5-5.9.2. > > The only issue I had was finding a more up-to-date Qt5-webkit because > there only seems to be some rc version for 5.9 at the location in > the original .info, so I used my build of the fork by annulen. 5.7.1 > wouldn't build. Unless you know of a link to an upstream release of > 5.9.x? > > I haven't tested this with anything yet, so this is a call for > testers please. > > Link: http://dawoodfall.net/testing/ > > -Dave Link to qt5-webkit-annulen: http://slackbuilds.org/repository/14.2/libraries/qt5-webkit-annulen/ -- We can use symlinks of course... syslogd would be a symlink to syslogp and ftpd and ircd would be linked to ftpp and ircp... and of course the point-to-point protocal paenguin. -- Kevin M. Bealer, commenting on the penguin Linux logo .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From larryhaja at gmail.com Fri Jul 6 02:50:04 2018 From: larryhaja at gmail.com (Larry Hajali) Date: Thu, 5 Jul 2018 19:50:04 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180706024127.GL2038@blackswan> References: <20180703104040.25c89823@Akita.witch.org> <20180706024127.GL2038@blackswan> Message-ID: > > The only issue I had was finding a more up-to-date Qt5-webkit because > there only seems to be some rc version for 5.9 at the location in > the original .info, so I used my build of the fork by annulen. 5.7.1 > wouldn't build. Unless you know of a link to an upstream release of > 5.9.x? > I used this one. https://download.qt.io/community_releases/5.9/5.9.0-final/qtwebkit-opensource-src-5.9.0.tar.xz -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at dawoodfall.net Fri Jul 6 03:02:27 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 6 Jul 2018 04:02:27 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> <20180706024127.GL2038@blackswan> Message-ID: <20180706030227.GN2038@blackswan> On Thursday 5 July 2018 19:50, Larry Hajali put forth the proposition: > > > > The only issue I had was finding a more up-to-date Qt5-webkit because > > there only seems to be some rc version for 5.9 at the location in > > the original .info, so I used my build of the fork by annulen. 5.7.1 > > wouldn't build. Unless you know of a link to an upstream release of > > 5.9.x? > > > I used this one. > > https://download.qt.io/community_releases/5.9/5.9.0-final/qtwebkit-opensource-src-5.9.0.tar.xz Thanks, I'll give that a test before playing with Qt5-5.10.1 etc. -- DOS: n., A small annoying boot virus that causes random spontaneous system crashes, usually just before saving a massive project. Easily cured by UNIX. See also MS-DOS, IBM-DOS, DR-DOS. -- David Vicker's .plan .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From xavier at maillard.im Fri Jul 6 04:20:57 2018 From: xavier at maillard.im (Xavier Maillard) Date: Fri, 6 Jul 2018 06:20:57 +0200 Subject: [Slackbuilds-users] keybase: md5 mismatch In-Reply-To: (message from Willy Sudiarto Raharjo on Fri, 6 Jul 2018 03:39:31 +0700) References: <201807052015.w65KFRjk032321@localhost.localdomain> <201807052023.w65KNpro008950@localhost.localdomain> Message-ID: <201807060420.w664KvrU026505@localhost.localdomain> > From: Willy Sudiarto Raharjo > Date: Fri, 6 Jul 2018 03:39:31 +0700 > > > Precisely, go is installed from the SBo repo *but* it is 1.10.2 > > version :/ > > Have you used "su -" instead of just su to make sure you get the updated > environment, especially GOROOT environment variable? In fact, I have a dedicated root env (tty1 in the linux console) so I am not going 'su' or 'sudo su' or whatever, I am just logining as 'root' at the console prompt. > PS: I have an updated keybase 2.1.1 on my branch Notice that keybase 2.1.0 from the SBo repository is also broken for the same reason (wrong GO version). I am trying to figure out what is setting GOROOT and where. -- Xavier Maillard e/j:xavier at maillard.im w:www.maillard.im m: 06 52 18 63 43 GPG: 9983 DCA1 1FAC 8DA7 653A F9AA BA49 09B7 8F04 DE1B From dave at dawoodfall.net Fri Jul 6 04:24:17 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 6 Jul 2018 05:24:17 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: References: <20180703104040.25c89823@Akita.witch.org> <20180706024127.GL2038@blackswan> Message-ID: <20180706042417.GO2038@blackswan> On Thursday 5 July 2018 19:50, Larry Hajali put forth the proposition: > > > > The only issue I had was finding a more up-to-date Qt5-webkit because > > there only seems to be some rc version for 5.9 at the location in > > the original .info, so I used my build of the fork by annulen. 5.7.1 > > wouldn't build. Unless you know of a link to an upstream release of > > 5.9.x? > > > I used this one. > > https://download.qt.io/community_releases/5.9/5.9.0-final/qtwebkit-opensource-src-5.9.0.tar.xz That builds too. All we need now are some people that use PyQt5 to test building their apps with it. I'll have a grep through the sbo repo to see if I can find any. -- The new Linux anthem will be "He's an idiot, but he's ok", as performed by Monthy Python. You'd better start practicing. -- Linus Torvalds, announcing another kernel patch .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From matteo.bernardini at gmail.com Fri Jul 6 05:32:59 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 6 Jul 2018 07:32:59 +0200 Subject: [Slackbuilds-users] keybase: md5 mismatch In-Reply-To: <201807060420.w664KvrU026505@localhost.localdomain> References: <201807052015.w65KFRjk032321@localhost.localdomain> <201807052023.w65KNpro008950@localhost.localdomain> <201807060420.w664KvrU026505@localhost.localdomain> Message-ID: 2018-07-06 6:20 GMT+02:00 Xavier Maillard : >> From: Willy Sudiarto Raharjo >> Date: Fri, 6 Jul 2018 03:39:31 +0700 >> >> > Precisely, go is installed from the SBo repo *but* it is 1.10.2 >> > version :/ >> >> Have you used "su -" instead of just su to make sure you get the updated >> environment, especially GOROOT environment variable? > > In fact, I have a dedicated root env (tty1 in the linux console) so I > am not going 'su' or 'sudo su' or whatever, I am just logining as > 'root' at the console prompt. > >> PS: I have an updated keybase 2.1.1 on my branch > > Notice that keybase 2.1.0 from the SBo repository is also broken for > the same reason (wrong GO version). > I am trying to figure out what is setting GOROOT and where. keybase built fine here too. I suppose your issue is originated by updating to a new google-go-lang version without logging out of your root session and logging in again: in this case your enviroment would still look for the google-go-lang stuff in the old path. Matteo From dave at dawoodfall.net Fri Jul 6 05:48:53 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 6 Jul 2018 06:48:53 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180706042417.GO2038@blackswan> References: <20180703104040.25c89823@Akita.witch.org> <20180706024127.GL2038@blackswan> <20180706042417.GO2038@blackswan> Message-ID: <20180706054853.GP2038@blackswan> On Friday 6 July 2018 05:24, Dave Woodfall put forth the proposition: > On Thursday 5 July 2018 19:50, > Larry Hajali put forth the proposition: > > > > > > The only issue I had was finding a more up-to-date Qt5-webkit because > > > there only seems to be some rc version for 5.9 at the location in > > > the original .info, so I used my build of the fork by annulen. 5.7.1 > > > wouldn't build. Unless you know of a link to an upstream release of > > > 5.9.x? > > > > > I used this one. > > > > https://download.qt.io/community_releases/5.9/5.9.0-final/qtwebkit-opensource-src-5.9.0.tar.xz > > That builds too. > > All we need now are some people that use PyQt5 to test building their > apps with it. > > I'll have a grep through the sbo repo to see if I can find any. A small update to them both. -- Besides, I think Slackware sounds better than 'Microsoft,' don't you? -- Patrick Volkerding .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From dave at dawoodfall.net Fri Jul 6 10:32:55 2018 From: dave at dawoodfall.net (David Woodfall) Date: Fri, 6 Jul 2018 11:32:55 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180706054853.GP2038@blackswan> References: <20180703104040.25c89823@Akita.witch.org> <20180706024127.GL2038@blackswan> <20180706042417.GO2038@blackswan> <20180706054853.GP2038@blackswan> Message-ID: <20180706103255.GS2038@blackswan> On Friday 6 July 2018 06:48, Dave Woodfall put forth the proposition: > On Friday 6 July 2018 05:24, > Dave Woodfall put forth the proposition: > > On Thursday 5 July 2018 19:50, > > Larry Hajali put forth the proposition: > > > > > > > > The only issue I had was finding a more up-to-date Qt5-webkit because > > > > there only seems to be some rc version for 5.9 at the location in > > > > the original .info, so I used my build of the fork by annulen. 5.7.1 > > > > wouldn't build. Unless you know of a link to an upstream release of > > > > 5.9.x? > > > > > > > I used this one. > > > > > > https://download.qt.io/community_releases/5.9/5.9.0-final/qtwebkit-opensource-src-5.9.0.tar.xz > > > > That builds too. > > > > All we need now are some people that use PyQt5 to test building their > > apps with it. > > > > I'll have a grep through the sbo repo to see if I can find any. > > A small update to them both. Sorry, I forgot to upload the qt5 5.9.2 SlackBuild and .info. Done. -- We all know Linux is great... it does infinite loops in 5 seconds. - Linus Torvalds about the superiority of Linux on the Amterdam Linux Symposium .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From willysr at slackbuilds.org Sat Jul 7 00:19:57 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 7 Jul 2018 07:19:57 +0700 Subject: [Slackbuilds-users] Updates - 20180707.1 Message-ID: <27586170-b6ca-1137-20b8-3469013858c4@slackbuilds.org> Welcome to July's update :) Some of the hightlight in this batch is - gnucash is now at 3.x while people prefer to keep using the old version can migrate to gnucash-legacy - prompt_toolkit1 is added for those who still need Python 2 version. - skylable-sx is removed due to DMCA takedown on upstream project Some people are working on updating Qt5 in SBo while keeping the original Qt5 version (5.7.1) in place. They are working with the current maintainer (Larry) to make sure it build and work properly. After that, we might need some time to test all scripts that depends on Qt5 against the new Qt5. In worst case, we just need to change the dependency into the qt5-legacy (or whatever the names might be). There's no timeline here, but it's a work-in-progress. Thanks to all who suggested the ideas and actually working on it. Have a nice weekend Sat Jul 7 00:01:49 UTC 2018 academic/STAR: Update Script. academic/flexbar: Updated for version 3.4.0. academic/pyCRAC: Updated for version 1.3.2. academic/pysam: Change EMAIL. academic/suitesparse: Updated for version 5.3.0 academic/units: Updated for version 2.17. audio/drumkv1: Updated for version 0.9.1, French man page. audio/fmmidi: Fix download URL. audio/jack-keyboard: Updated for version 2.7.2. audio/rubberband: Updated for version 1.8.2. audio/samplv1: Updated for version 0.9.1, French man page. audio/synthv1: Updated for version 0.9.1, French man page. desktop/9menu: New maintainer. desktop/compton-conf: Updated for version 0.4.0. desktop/enlightenment: Updated for version 0.22.3. desktop/faba-icon-theme: Updated for version 4.3. desktop/mcwm: New maintainer. desktop/oomox: Update for moved downloads. desktop/py3status: Updated for version 3.10. desktop/redshift: Updated for version 1.12. desktop/simplenote: Update SlackBuild & maintainer email. desktop/slack-wallpapers: Update DOWNLOAD and EMAIL. desktop/xmonad: Switch homepage to https. desktop/zenity: Updated for version 3.28.0. development/Coin: Update homepage. development/SQLAlchemy: Updated for version 1.2.9. development/SoQt: Update homepage. development/brotli: Updated for version 1.0.5. development/d-tools: Updated for version 2.081.0 development/diffoscope: Updated for version 98. development/dmd: Updated for version 2.081.0 development/eclim: Updated for version 2.8.0. development/eclipse-cpp: Updated for version 4.8.0. development/eclipse-java: Updated for version 4.8.0. development/eclipse-jee: Updated for version 4.8.0. development/fpc-source: Updated for version 3.0.4. development/gambas3: Update EMAIL. development/glm: Updated for version 0.9.9.0. development/ioncube-loader: Updated for version 10.2.2 development/luajit: Fix FLAGS. development/monkey-studio: Update homepage. development/mrustc: Updated for version gitc1d4b60. development/pycharm: Updated for version 2018.1.4. development/tanya: Updated for version 0.10.0 development/tea: Updated for version 45.0.2. development/universal-ctags: Updated for version 1e2c63f games/advancemame: Updated for version 3.8. games/atari800: Updated for version 4.0.0. games/freeciv: Updated for version 2.6.0_RC1. games/mame: Updated for version 0.199. games/vbam: Updated for version 2.1.0. gis/GMT: Updated for version 5.4.4. gis/OTB: Add blas dependency. gis/google-earth: Updated for version 7.3.2.5483. graphics/gource: Updated for version 0.49. graphics/graphviz: Update homepage. graphics/meh: New maintainer. graphics/meh: Use github URL. graphics/xli: New maintainer, various fixes. graphics/yacreader: Updated for version 9.5.0. libraries/cmark: Fix man directory, update maintainer email. libraries/cpp-netlib: Switch homepage to https. libraries/hdf: Updated for version 4.2.14. libraries/libinput: Fix libinput.pc. libraries/libopenshot-audio: Updated for version 0.1.6 libraries/libopenshot: Updated for version 0.2.0 libraries/libosinfo: Updated for version 1.2.0. libraries/live555: Updated for version 2018.07.01 libraries/nltk: Updated for version 3.3.0. libraries/opencv: Updated for version 3.4.2 libraries/pcre2: Updated for version 10.31 libraries/pexpect: Updated for version 4.6.0. libraries/qt5: Fix download link. libraries/re2: Added (Regular Expression Engine). multimedia/QMPlay2: Updated for version 18.07.03. multimedia/get_iplayer: Updated for version 3.16. multimedia/openshot: Updated for version 2.4.2 multimedia/opera-ffmpeg-codecs: Updated for version 0.31.2. multimedia/smplayer: Updated for version 18.6.0. network/atftp: New maintainer, expand README. network/bozohttpd: New maintainer, many tweaks. network/dante: Added (a free SOCKS client and server). network/darkhttpd: New maintainer. network/dropbox: Updated for version 52.4.60. network/glewlwyd: Updated for version 1.4.6. network/gui-ufw: Amend SlackBuild, new maintainer email. network/luakit: Updated for version 2.0 + new maintainer. network/nextcloud-server: Updated for version 13.0.4. network/opera-developer: Updated for version 55.0.2991.0. network/opera: Updated for version 54.0.2952.41. network/prosody-mod-smacks: Updated for version hg3150. network/qutebrowser: Updated for version 1.4.0. network/riot-web: Updated for version 0.15.6. network/signal-desktop: Updated for version 1.13.0. network/skylable-sx: Removed (DMCA Takedown). network/skype4pidgin: Added (SkypeWeb Chat for Pidgin). network/slimjet: Update EMAIL. network/telegram: Updated for version 1.3.9. network/tnftp: New maintainer, SOCKS5 support. network/tor-browser: Updated for version 7.5.6. network/twine: Updated for version 1.11.0. network/vivaldi: Updated for version 1.15.1147.52. network/yandex-browser-beta: Updated for version 18.6.0.2253. network/youtube-dl: Updated for version 2018.06.25. office/MasterPDFEditor: Updated for version 5.0.32. office/ProjectLibre: Updated for version 1.8.0. office/ganttproject: Updated for version 2.8.8. office/gnucash-docs: Added (Gnucash help and user guides). office/gnucash-legacy-docs: Added (Gnucash help and user guides). office/gnucash-legacy: Added (financial accounting application). office/gnucash3-docs: Removed (see gnucash-docs). office/gnucash3: Removed (see gnucash). office/gnucash: Added (financial accounting application). office/paps: New maintainer, expand README. office/pdfshuffler: Change EMAIL. perl/perl-Math-Complex_C-L: Updated for version 0.06. perl/txt2html: Update DEP. python/atomicwrites: Added (Python library for atomic file writes). python/colored: Updated for version 1.3.93. python/getdevinfo: Added (A device information gatherer). python/ipython: Change dependency to prompt_toolkit1. python/lxml: Switch homepage to https. python/parso: Updated for version 0.3.0. python/prompt_toolkit1: Added (interactive command lines). python/ptyprocess: Updated for version 0.6.0. python/pytest: Updated for version 3.6.2. python/python-evdev: Fix permissions. python/python-unicodedata2: Updated for version 11.0.0. python/python3-jedi: Updated for version 0.12.1. python/python3-parso: Updated for version 0.3.0. python/ruffus: Change EMAIL. python/s3cmd: Switch homepage to https. system/ack: Updated for version 2.24. system/alacritty: Updated for version git68b3d8a. system/ansible: Updated for version 2.5.6. system/apparmor: Added (Mandatory Access Control mechanism). system/argyllcms: Updated for version 2.0.0. system/ddrescue-gui: Updated for version 2.0.0. system/dosbox-dev: Updated for version 0.74.r4122. system/keybase: Updated for version 2.1.1. system/lsb-release: Added (LSB version query program). system/luckybackup: Switch to i586. system/lynis: Updated for version 2.6.6. system/osinfo-db-tools: Updated for version 1.2.0. system/osinfo-db: Updated for version 20180612. system/snapscreenshot: Added (screenshot program for text consoles). system/sqldiff: Added (display differences). system/terminology: Updated for version 0.22.3. system/unicode-character-database: Updated for version 11.0.0. system/vagrant: Fix .info. +--------------------------+ -- 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 orbea at fredslev.dk Sat Jul 7 05:04:41 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Fri, 6 Jul 2018 22:04:41 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180706103255.GS2038@blackswan> Message-ID: <20180706220441.1b3550ed@Akita.witch.org> > Sorry, I forgot to upload the qt5 5.9.2 SlackBuild and .info. Done. I went to test before you noticed this and found your Qt-5.10.1 script instead. After many cryptic build failures I was informed that gentoo never unmasked 5.10 and now considers 5.11 to be stable. So I tried your script to build 5.11 and it worked on the first try with just changing the version number. I next updated your python2-sip to 4.19.11 as required by PyQt5-5.11.2. I wasn't able to quickly figure out how to make PyQt5 happy with a private sip so I applied the attached debian patch to build with a public sip, but there might be a better way to do that for someone with more patience to figure it out. Lastly I found that they broke INSTALL_ROOT and again, I didn't dwell on it long and worked around it with this sed before make since it seemed to be not that important... sed -i '/mk_distinfo.py/d' Makefile Other than that, everything on my system that requires Qt5 builds and seems to work fine with the exception of solarus-quest-editor which suffers build errors with the newer Qt5. However their git master is fixed and I seem to have backported the fix successfully. I plan to apply it to the SlackBuild if further testing doesn't reveal more issues. The single program I have that uses PyQt5, m64py, the lackluster gui front end to the standalone version of mupen64plus also seems to work as well as it did before. However I build this with my own script based on the git master since the stable versions are hopelessly outdated. Lastly my rpcs3 (PS3 emulator) script which I also build from their git master hasn't worked for a long time since they started requiring at least Qt 5.10. With the newer version it now builds again. I tested this on current and will try again with 14.2 tomorrow, but personally I would prefer 5.11 over 5.9 and would suggest skipping 5.10. -------------- next part -------------- A non-text attachment was scrubbed... Name: public_sip.diff Type: text/x-patch Size: 1886 bytes Desc: not available URL: From dave at dawoodfall.net Sat Jul 7 07:15:07 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sat, 7 Jul 2018 08:15:07 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180706220441.1b3550ed@Akita.witch.org> References: <20180706103255.GS2038@blackswan> <20180706220441.1b3550ed@Akita.witch.org> Message-ID: <20180707071507.GB13829@blackswan> On Friday 6 July 2018 22:04, orbea at fredslev.dk put forth the proposition: > > Sorry, I forgot to upload the qt5 5.9.2 SlackBuild and .info. Done. > > I went to test before you noticed this and found your Qt-5.10.1 script > instead. After many cryptic build failures I was informed that gentoo > never unmasked 5.10 and now considers 5.11 to be stable. So I tried > your script to build 5.11 and it worked on the first try with just > changing the version number. I built 5.11 a while back and at that time the riverbank guy only had -dev versions of sip and PyQt5. I'll have to catch up with that and build a proper 5.11 version. > I next updated your python2-sip to 4.19.11 as required by PyQt5-5.11.2. > > I wasn't able to quickly figure out how to make PyQt5 happy with a > private sip so I applied the attached debian patch to build with a > public sip, but there might be a better way to do that for someone with > more patience to figure it out. Thanks for the patch. > Lastly I found that they broke INSTALL_ROOT and again, I didn't dwell > on it long and worked around it with this sed before make since it > seemed to be not that important... > > sed -i '/mk_distinfo.py/d' Makefile > > Other than that, everything on my system that requires Qt5 builds and > seems to work fine with the exception of solarus-quest-editor which > suffers build errors with the newer Qt5. However their git master is > fixed and I seem to have backported the fix successfully. I plan to > apply it to the SlackBuild if further testing doesn't reveal more > issues. > > The single program I have that uses PyQt5, m64py, the lackluster gui > front end to the standalone version of mupen64plus also seems to work as > well as it did before. However I build this with my own script based on > the git master since the stable versions are hopelessly outdated. > > Lastly my rpcs3 (PS3 emulator) script which I also build from their git > master hasn't worked for a long time since they started requiring at > least Qt 5.10. With the newer version it now builds again. > > I tested this on current and will try again with 14.2 tomorrow, but > personally I would prefer 5.11 over 5.9 and would suggest skipping 5.10. I already had a build script for 5.10.1 so it wasn't really going out of my way. I don't know if the gentoo guys have fixed this, but I had to disable gstreamer support to get anything 5.10+ to build, but I'm guessing gentoo has a newer version. Personally, I'll keep updating just to stay up-to-date with the latest qtwebengine code/fixes for qutebrowser to improve. The one thing that worries me the most is that sip may need to be included as a module in other python apps, and of course I've changed the name of it to not mess with the stock sip. Therefore anyone building anything based on that module will need to do some renaming. I really don't know of anything else using it though, and PyQt5 was happy with just the binary path/name and the include dir. -- Shoot me again. Just proving that the quickest way to solve the problem is to post a whine to the newsgroups: within moments the solution presents itself to me, and meanwhile my ass is hanging out on the Net... *sigh*... -- Dave Phillips, dlphilp at bright.net, about problem solving via news .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From chytraeu at sdf.org Sat Jul 7 17:43:06 2018 From: chytraeu at sdf.org (Donald Cooley) Date: Sat, 7 Jul 2018 12:43:06 -0500 Subject: [Slackbuilds-users] can't remove brave submission Message-ID: I was trying to submit an update to Brave web browser and I had a network interruption. So, I received a confirmation email that brave was submitted. However, it's not in the pending or ready queues. Here's the confirmation I received: New upload: brave.tar.gz Category: Network Submission md5: 2833c8639f36c298c5d0a33e57199a8c If you need to remove this submission before it is approved please visit: https://slackbuilds.org/remove/ All I want to do is to submit an updated SlackBuild of brave. From willysr at slackbuilds.org Sat Jul 7 17:49:48 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 8 Jul 2018 00:49:48 +0700 Subject: [Slackbuilds-users] can't remove brave submission In-Reply-To: References: Message-ID: <68829cee-4cc0-c8d4-934b-aab5266250e8@slackbuilds.org> > I was trying to submit an update to Brave web browser and I had a > network interruption. > > So, I received a confirmation email that brave was submitted. > > However, it's not in the pending or ready queues. > > Here's the confirmation I received: > > New upload: brave.tar.gz > Category: Network > Submission md5: 2833c8639f36c298c5d0a33e57199a8c > > If you need to remove this submission before it is approved > please visit: https://slackbuilds.org/remove/ > > All I want to do is to submit an updated SlackBuild of brave. You can resubmit 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 orbea at fredslev.dk Sun Jul 8 03:46:54 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Sat, 7 Jul 2018 20:46:54 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180707071507.GB13829@blackswan> Message-ID: <20180707204654.33c3c33c@Akita.witch.org> Well I hit a roadblock with Qt-5.11 on 14.2. With '-system-harfbuzz' it bails on configure because harfbuzz is too old, with '-qt-harfbuzz' it fails to build late in the ninja stage and with '-no-harfbuzz' it around the same place with errors indicating it misses harfbuzz. The obvious solution would be to update harfbuzz, but that is easier said than done for 14.2. Also I forgot to mention enum34 is a new dependency of PyQt5, fortunately the version at SBo is both up to date and adequate. From willysr at slackbuilds.org Sun Jul 8 03:46:21 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 8 Jul 2018 10:46:21 +0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180707204654.33c3c33c@Akita.witch.org> References: <20180707204654.33c3c33c@Akita.witch.org> Message-ID: > Well I hit a roadblock with Qt-5.11 on 14.2. > > With '-system-harfbuzz' it bails on configure because harfbuzz is too > old, with '-qt-harfbuzz' it fails to build late in the ninja stage and > with '-no-harfbuzz' it around the same place with errors indicating it > misses harfbuzz. The obvious solution would be to update harfbuzz, but > that is easier said than done for 14.2. No, we can't do that as it's core packages in Slackware probably best option at this moment is stick with LTS 5.9.x -- 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 dave at dawoodfall.net Sun Jul 8 05:58:20 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 8 Jul 2018 06:58:20 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180707204654.33c3c33c@Akita.witch.org> References: <20180707071507.GB13829@blackswan> <20180707204654.33c3c33c@Akita.witch.org> Message-ID: <20180708055820.GF13829@blackswan> On Saturday 7 July 2018 20:46, orbea at fredslev.dk put forth the proposition: > Well I hit a roadblock with Qt-5.11 on 14.2. > > With '-system-harfbuzz' it bails on configure because harfbuzz is too > old, with '-qt-harfbuzz' it fails to build late in the ninja stage and > with '-no-harfbuzz' it around the same place with errors indicating it > misses harfbuzz. The obvious solution would be to update harfbuzz, but > that is easier said than done for 14.2. > > Also I forgot to mention enum34 is a new dependency of PyQt5, > fortunately the version at SBo is both up to date and adequate. I have a fix for that: # fix webkit harfbuzz WBK="qtwebengine/src/3rdparty/chromium/third_party/WebKit/Source/platform/fonts/ shaping/" HBDIR="../../../../../../../../../../qtbase/src/3rdparty/harfbuzz-ng/src" find $WBK -regex ".*\.\(cpp\|h\)$" -exec \ sed -i "s%#include %#include \"$HBDIR/hb.h\"%" {} \; find $WBK -regex ".*\.\(cpp\|h\)$" -exec \ sed -i "s%#include %#include \"$HBDIR/hb-ot.h\"%" {} \; Note that this is still building for me though, so don't be surprised if it fails somewhere else: http://dawoodfall.net/testing/qt5-5.11/qt5.SlackBuild -- As usual, this being a 1.3.x release, I haven't even compiled this kernel yet. So if it works, you should be doubly impressed. -- Linus Torvalds, announcing kernel 1.3.3 .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From dave at dawoodfall.net Sun Jul 8 06:28:42 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 8 Jul 2018 07:28:42 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180708055820.GF13829@blackswan> References: <20180707071507.GB13829@blackswan> <20180707204654.33c3c33c@Akita.witch.org> <20180708055820.GF13829@blackswan> Message-ID: <20180708062842.GG13829@blackswan> On Sunday 8 July 2018 06:58, Dave Woodfall put forth the proposition: > On Saturday 7 July 2018 20:46, > orbea at fredslev.dk put forth the proposition: > > Well I hit a roadblock with Qt-5.11 on 14.2. > > > > With '-system-harfbuzz' it bails on configure because harfbuzz is too > > old, with '-qt-harfbuzz' it fails to build late in the ninja stage and > > with '-no-harfbuzz' it around the same place with errors indicating it > > misses harfbuzz. The obvious solution would be to update harfbuzz, but > > that is easier said than done for 14.2. > > > > Also I forgot to mention enum34 is a new dependency of PyQt5, > > fortunately the version at SBo is both up to date and adequate. > > I have a fix for that: > > # fix webkit harfbuzz > WBK="qtwebengine/src/3rdparty/chromium/third_party/WebKit/Source/platform/fonts/ shaping/" > HBDIR="../../../../../../../../../../qtbase/src/3rdparty/harfbuzz-ng/src" > > find $WBK -regex ".*\.\(cpp\|h\)$" -exec \ > sed -i "s%#include %#include \"$HBDIR/hb.h\"%" {} \; > > find $WBK -regex ".*\.\(cpp\|h\)$" -exec \ > sed -i "s%#include %#include \"$HBDIR/hb-ot.h\"%" {} \; > > Note that this is still building for me though, so don't be surprised > if it fails somewhere else: > > http://dawoodfall.net/testing/qt5-5.11/qt5.SlackBuild This worked in 5.11.0 though. I haven't seen yet whether it works in .1 -- If the future navigation system [for interactive networked services on the NII] looks like something from Microsoft, it will never work. -- Chairman of Walt Disney Television & Telecommunications .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From dave at dawoodfall.net Sun Jul 8 06:44:36 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 8 Jul 2018 07:44:36 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180707204654.33c3c33c@Akita.witch.org> References: <20180707071507.GB13829@blackswan> <20180707204654.33c3c33c@Akita.witch.org> Message-ID: <20180708064436.GH13829@blackswan> On Saturday 7 July 2018 20:46, orbea at fredslev.dk put forth the proposition: > Also I forgot to mention enum34 is a new dependency of PyQt5, > fortunately the version at SBo is both up to date and adequate. enum.py seems to be part of python-3.6.x: find /usr/lib64/python3.6 -name enum\* (viins) /usr/lib64/python3.6/__pycache__/enum.cpython-36.opt-1.pyc /usr/lib64/python3.6/__pycache__/enum.cpython-36.pyc /usr/lib64/python3.6/__pycache__/enum.cpython-36.opt-2.pyc /usr/lib64/python3.6/enum.py /usr/lib64/python3.6/site-packages/pip/_vendor/chardet/__pycache__/enums.cpython-36.pyc /usr/lib64/python3.6/site-packages/pip/_vendor/chardet/enums.pY Doesn't that work? I'm not quite that far in the build process. -- /* * Oops. The kernel tried to access some bad page. We'll have to * terminate things with extreme prejudice. */ die_if_kernel("Oops", regs, error_code); -- From linux/arch/i386/mm/fault.c .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From dave at dawoodfall.net Sun Jul 8 06:46:20 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 8 Jul 2018 07:46:20 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180708064436.GH13829@blackswan> References: <20180707071507.GB13829@blackswan> <20180707204654.33c3c33c@Akita.witch.org> <20180708064436.GH13829@blackswan> Message-ID: <20180708064620.GI13829@blackswan> On Sunday 8 July 2018 07:44, Dave Woodfall put forth the proposition: > On Saturday 7 July 2018 20:46, > orbea at fredslev.dk put forth the proposition: > > Also I forgot to mention enum34 is a new dependency of PyQt5, > > fortunately the version at SBo is both up to date and adequate. > > enum.py seems to be part of python-3.6.x: > > find /usr/lib64/python3.6 -name enum\* (viins) > /usr/lib64/python3.6/__pycache__/enum.cpython-36.opt-1.pyc > /usr/lib64/python3.6/__pycache__/enum.cpython-36.pyc > /usr/lib64/python3.6/__pycache__/enum.cpython-36.opt-2.pyc > /usr/lib64/python3.6/enum.py > /usr/lib64/python3.6/site-packages/pip/_vendor/chardet/__pycache__/enums.cpython-36.pyc > /usr/lib64/python3.6/site-packages/pip/_vendor/chardet/enums.pY > > Doesn't that work? > > I'm not quite that far in the build process. Ah python2 OK. -- >Ever heard of .cshrc? That's a city in Bosnia. Right? -- Discussion in comp.os.linux.misc on the intuitiveness of commands .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From kjhambrick at gmail.com Sun Jul 8 14:12:21 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 8 Jul 2018 09:12:21 -0500 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? Message-ID: Dimitris -- Going thru this weeks new releases from Willy and ... The DOWNLOAD= Link failed for youtube-dl Version 2018-06-25 Digging around on the youtube-dl HomePage Download Link, I 'found' the download at: DOWNLOAD=" https://github.com/rg3/youtube-dl/releases/download/2018.06.25/youtube-dl-2018.06.25.tar.gz " The md5sum was the same as in the youtube-dl.info file and youtube-dl worked on my standard test link: https://www.youtube.com/watch?v=2ZrWHtvSog4 ( 1-Minute_Audio_Test_for_Stereo_Speakers_Headphones-2ZrWHtvSog4.webm ) Thanks for youtube-dl and ALL the other SlackBuilds that you provide ! -- kjh -------------- next part -------------- An HTML attachment was scrubbed... URL: From orbea at fredslev.dk Sun Jul 8 15:24:10 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Sun, 8 Jul 2018 08:24:10 -0700 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? In-Reply-To: Message-ID: <20180708082410.6c7e4829@Akita.witch.org> When I suggested to use upstream's releases instead of the auto generated ones at github which were causing issues I neglected to notice that upstream removed old releases... Sorry about that... From kjhambrick at gmail.com Sun Jul 8 15:29:54 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sun, 8 Jul 2018 10:29:54 -0500 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? In-Reply-To: <20180708082410.6c7e4829@Akita.witch.org> References: <20180708082410.6c7e4829@Akita.witch.org> Message-ID: No problem at all orbea. And I apologize too ... I missed the significance of your earlier email ... otherwise I would have replied-to instead of starting a new one ... :) -- kjh Found your email from before: Date: Thu, 28 Jun 2018 07:18:21 -0700 From: "orbea at fredslev.dk" To: slackbuilds-users at slackbuilds.org Message-ID: <20180628071821.72909788 at Akita.witch.org> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; x86_64-slackware-linux-gnu) In-Reply-To: MIME-Version: 1.0 Subject: Re: [Slackbuilds-users] youtube-dl On Sun, Jul 8, 2018 at 10:24 AM, orbea at fredslev.dk wrote: > When I suggested to use upstream's releases instead of the > auto generated ones at github which were causing issues I neglected to > notice that upstream removed old releases... Sorry about that... > _______________________________________________ > 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 orbea at fredslev.dk Sun Jul 8 16:37:46 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Sun, 8 Jul 2018 09:37:46 -0700 Subject: [Slackbuilds-users] cryptography SlackBuild six dependency. Message-ID: <20180708093746.5f845e73@Akita.witch.org> Hi, I noticed that cryptography depends on six, but also depends on packaging which then depends on six. I think six can be removed from the REQUIRES in cryptography to avoid listing it twice in the dependency chain. From willysr at slackbuilds.org Sun Jul 8 16:57:44 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 8 Jul 2018 23:57:44 +0700 Subject: [Slackbuilds-users] cryptography SlackBuild six dependency. In-Reply-To: <20180708093746.5f845e73@Akita.witch.org> References: <20180708093746.5f845e73@Akita.witch.org> Message-ID: > I noticed that cryptography depends on six, but also depends on > packaging which then depends on six. I think six can be removed from > the REQUIRES in cryptography to avoid listing it twice in the > dependency chain. Thanks for noticing pushed to 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 orbea at fredslev.dk Sun Jul 8 18:43:02 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Sun, 8 Jul 2018 11:43:02 -0700 Subject: [Slackbuilds-users] Giving up maintainership of my slackbuiilds In-Reply-To: Message-ID: <20180708114302.2c93d4c4@Akita.witch.org> > >I suppose I replied to the wrong thread, but I mentioned I'd be willing > >to take over system/yash in the "[Slackbuilds-users] Slackbuild patch > >for luakit 2.1" thread. Though if you really want it I have no issues > >with you maintaining it instead as long its kept up to date. :) > > I really want it if you don't mind. So are you going to take this script over? If you don't plan to do anything with it then I'd much rather take it over myself so I know it will stay up to date. From acmesmackme at live.com Sun Jul 8 21:04:10 2018 From: acmesmackme at live.com (Oooooo NOoooo) Date: Sun, 8 Jul 2018 21:04:10 +0000 Subject: [Slackbuilds-users] youtube-dl 2018.06.25 Slackbuild fails to download source package Message-ID: I am using Slackware64 Current. I was told to submit this to the slackbuilds-users mailing list by ponce. Here is the error: Connecting to www.yt-dl.org (www.yt-dl.org)|95.143.172.170|:80... connected. HTTP request sent, awaiting response... 302 Found Location: https://github.com/rg3/youtube-dl/releases/download/2018.07.04/youtube-dl-2018.06.25.tar.gz [following] --2018-07-08 17:01:13-- https://github.com/rg3/youtube-dl/releases/download/2018.07.04/youtube-dl-2018.06.25.tar.gz Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112 Connecting to github.com (github.com)|192.30.253.113|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-07-08 17:01:13 ERROR 404: Not Found. Sent from Outlook -------------- next part -------------- An HTML attachment was scrubbed... URL: From alik at ejik.org Wed Jul 11 01:37:16 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Wed, 11 Jul 2018 04:37:16 +0300 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? In-Reply-To: <20180708082410.6c7e4829@Akita.witch.org> References: <20180708082410.6c7e4829@Akita.witch.org> Message-ID: <1531273036.2963222.1436700864.3653B238@webmail.messagingengine.com> Hello, > When I suggested to use upstream's releases instead of the auto > generated ones at github which were causing issues I neglected to > notice that upstream removed old releases... Sorry about that... But this url works: https://yt-dl.org/downloads/2018.06.25/youtube-dl-2018.06.25.tar.gz The broken one is: http://www.yt-dl.org/downloads/latest/youtube-dl-2018.06.25.tar.gz Best regards, Alexander From alik at ejik.org Wed Jul 11 02:29:12 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Wed, 11 Jul 2018 05:29:12 +0300 Subject: [Slackbuilds-users] opencv issue In-Reply-To: <20180316143056.26418ea79ed5247709fe59a7@ythogtha.org> References: <20180316143056.26418ea79ed5247709fe59a7@ythogtha.org> Message-ID: <1531276152.3803343.1436737648.0B384F21@webmail.messagingengine.com> Hello, On Fri, 16 Mar 2018, at 16:30, Ythogtha wrote: > > When compiling opencv on Slackware using the Slackbuilds script and > > I noticed that opencv is creating a folder /usr/lib6464. Has anyone > > else noticed this? > There's a patched version of the OpenCV SlackBuild pushed by Christoph > Willing. But was this fix applied to version 3.4.2? I got /usr/lib6464 and this doesn't allow compilation of gmic. Best regards, Alexander From dave at dawoodfall.net Wed Jul 11 02:34:53 2018 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 11 Jul 2018 03:34:53 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180703104040.25c89823@Akita.witch.org> References: <20180703104040.25c89823@Akita.witch.org> Message-ID: <20180711023453.GX13829@blackswan> On Tuesday 3 July 2018 10:40, orbea at fredslev.dk put forth the proposition: > > Maybe you meant this by EOL also, the source mentioned in qt5.info > > has vanished. Sorry if this is already known by everybody, i didn't > > follow the qt discussion yet. > > I didn't even notice that yet! > > I meant that Qt5 upstream released 5.7.1 in December 14 2016 and will > not update it again. > > https://wiki.qt.io/Qt_5.7_Release > > When programs I use will soon no longer support releases older than > 5.9 I can not complain to them that it will no longer build in > Slackware because by all means we should of updated literally years > ago... I submitted python2-sip earlier (4.19.6 which is in line with the python3 version on sbo at the moment). I've put some basic instructions in README on what options you might need to supply to applications to build against it, and how to use it as a module in python2 code. eg: --sip-incdir="/usr/include/python$PYTHONVER/python2-sip" \ --sip=/usr/bin/python2-sip and import python2_sip I didn't however test any code using it, just saw that importing in the python cli raised no exception. I tested building it against Qt5 5.7.1, 5.9.2, 5.10.0, and 5.11.1 and it built fine. So far, so good. -Dave -- [In 'Doctor' mode], I spent a good ten minutes telling Emacs what I thought of it. (The response was, 'Perhaps you could try to be less abusive.') -- Matt Welsh .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From skaendo at excite.com Wed Jul 11 02:42:19 2018 From: skaendo at excite.com (Ed Ender) Date: Tue, 10 Jul 2018 22:42:19 -0400 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? Message-ID: <20180710224219.14919@web003.roc2.bluetie.com> This one works too: https://github.com/rg3/youtube-dl/releases/download/2018.07.10/youtube-dl-2018.07.10.tar.gz I prefer not to use referral links myself. Just my 2 cents. Ed -----Original Message----- From: "Alexander Verbovetsky" [alik at ejik.org] Date: 07/10/2018 08:37 PM To: slackbuilds-users at slackbuilds.org Subject: Re: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? Hello, > When I suggested to use upstream's releases instead of the auto > generated ones at github which were causing issues I neglected to > notice that upstream removed old releases... Sorry about that... But this url works: https://yt-dl.org/downloads/2018.06.25/youtube-dl-2018.06.25.tar.gz The broken one is: http://www.yt-dl.org/downloads/latest/youtube-dl-2018.06.25.tar.gz Best regards, Alexander _______________________________________________ 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 Wed Jul 11 02:55:26 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 11 Jul 2018 09:55:26 +0700 Subject: [Slackbuilds-users] opencv issue In-Reply-To: <1531276152.3803343.1436737648.0B384F21@webmail.messagingengine.com> References: <20180316143056.26418ea79ed5247709fe59a7@ythogtha.org> <1531276152.3803343.1436737648.0B384F21@webmail.messagingengine.com> Message-ID: >> There's a patched version of the OpenCV SlackBuild pushed by Christoph >> Willing. > > But was this fix applied to version 3.4.2? I got /usr/lib6464 and this > doesn't allow compilation of gmic. I have it fixed on my branch, thanks to Mario -- 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 slackbuilds at schoepfer.info Wed Jul 11 03:22:15 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 11 Jul 2018 05:22:15 +0200 Subject: [Slackbuilds-users] texlive 2018 Message-ID: Hi, i just submitted texlive,texlive-extra and texlive-docs. texlive-fonts is now included in texlive-extra, so texlive-fonts should be removed from SBo. Johannes From lrcjefferson at gmail.com Wed Jul 11 18:36:54 2018 From: lrcjefferson at gmail.com (Jefferson Rocha) Date: Wed, 11 Jul 2018 15:36:54 -0300 Subject: [Slackbuilds-users] dokuwiki package, new maintainer Message-ID: Hello! Yesterday I uploaded an update to the dokuwi package which is outdated! I was not allowed, but today I received permission today from Giorgio Peron to keep the dokuwiki package. Attached is the screenshot. Thanks. -- HOMEPAGE http://www.slackjeff.com.br PODCAST http://podcast.slackjeff.com.br YOUTUBE https://www.youtube.com.br/slackjeff MY PROGRAMS https://notabug.org/jeffersonrocha Emmi Linux Project https://www.emmilinux.com.br -------------- next part -------------- A non-text attachment was scrubbed... Name: Captura de tela_2018-07-11_15-18-35.png Type: image/png Size: 36415 bytes Desc: not available URL: From dave at dawoodfall.net Wed Jul 11 19:11:42 2018 From: dave at dawoodfall.net (David Woodfall) Date: Wed, 11 Jul 2018 20:11:42 +0100 Subject: [Slackbuilds-users] Security Update: Qutebrowser Message-ID: <20180711191142.GB13829@blackswan> Qutebrowser has been updated to 1.4.1 to fix a security issue. Details: https://github.com/qutebrowser/qutebrowser/issues/4060 The present slackbuild will work with the source for 1.4.1: https://github.com/qutebrowser/qutebrowser/releases/download/v1.4.1/qutebrowser-1.4.1.tar.gz eg: VERSION=1.4.1 ./qutebrowser.SlackBuild -Dave -- Anyone who thinks UNIX is intuitive should be forced to write 5000 lines of code using nothing but vi or emacs. AAAAACK! -- Discussion on the intuitiveness of commands, especially Emacs .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From willysr at slackbuilds.org Sat Jul 14 00:24:20 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 14 Jul 2018 07:24:20 +0700 Subject: [Slackbuilds-users] Updates - 20180714.1 Message-ID: <9b4f5160-0393-2600-61e5-74f329cdde14@slackbuilds.org> Sat Jul 14 00:02:50 UTC 2018 academic/PhyML: Updated for version 3.3.20180621. academic/gchemutils: Updated for version 0.14.17. academic/genometools: Updated for version 1.5.10. academic/hyphy: Updated for version 2.3.13. academic/megacc: Removed (see megax). academic/megax: Added (Molecular Evolutionary Genetics Analysis). academic/pari: Added (a computer algebra system). academic/perlprimer: Updated for version 1.2.3_f7d3bd0. academic/primer3: Updated for version 2.4.0. academic/treeview: Removed (renamed to treeviewx). academic/treeviewx: Added (Program to display phylogenetic trees). academic/zotero: Updated for version 5.0.52. audio/calf: Updated for version 0.90.1. audio/pianobar: Updated for version 2018.06.22. audio/unsf: Added (convert .sf2 files to GUS-type patches). desktop/jgmenu: Updated for version 1.1. desktop/lemonbar-xft: Added (lightweight taskbar based on XCB). desktop/murrine-themes: Updated for version 2.98.11. desktop/sun: Updated for version 1.2.3. development/afl: Updated for version 2.52b. development/complexity: Updated for version 1.10. development/d-tools: Updated for version 2.081.1 development/diffoscope: Updated for version 99. development/dkms: Updated for version 2.6.1 + new maintainer development/dmd: Updated for version 2.081.1 development/hopper: Updated for version 4.3.25. development/slibtool: Updated for version 0.5.21. development/universal-ctags: Updated for version a794069 development/vis: Added (vi-like editor). games/commandergenius: Updated for version 2.2.2. games/fizmo: Updated for version 0.8.5. games/fuse-emulator: Updated for version 1.5.5. games/jfsw: Updated for version 20180424_8fc2d54. games/puNES: Added (NES emulator). gis/rasterio: Updated for version 1.0.0. gis/saga-gis: Updated for version 6.4.0. graphics/OpenCASCADE: Update homepage. graphics/jpeg2ps: Switch homepage to https. graphics/ristretto: Updated for version 0.8.3. graphics/screencloud: Switch homepage to http. libraries/Kivy: Updated for version 1.10.1. libraries/PyYAML: Switch homepage and download to https. libraries/botocore: Updated for version 1.10.52. libraries/glktermw: Added (library for text interactive fiction). libraries/librelp: Update homepage. libraries/libsixel: Added (SIXEL encoder/decoder implementation). libraries/libspectrum: Updated for version 1.4.4. libraries/libxnvctrl: Updated for version 390.59. libraries/live555: Updated for version 2018.07.07 libraries/npth: Updated for version 1.5. libraries/opencv: Fix library paths libraries/python3-PyYAML: Switch homepage and download to https. libraries/qca-qt5: Added (Qt Cryptographic Architecture for Qt5). libraries/remglk: Added (RPC implementation of the Glk IF API). multimedia/flashplayer-plugin: Updated for version 30.0.0.134. multimedia/openshot: Removed paragraph from the README. multimedia/opera-developer-ffmpeg-codecs: Updated for version 0.31. multimedia/opera-ffmpeg-codecs: Updated for version 0.31.4. multimedia/pepperflash-plugin: Updated for version 30.0.0.134. network/SoulseekQt: Use /opt. network/WireGuard: Updated for version 0.0.20180708. network/atheme: Updated for version v7.2.10_r2. network/awscli: Updated for version 1.15.53. network/brave: Updated for version 0.23.31. network/bro: Updated for version 2.5.4. network/cicb: Update homepage, rm obsolete .diff. network/dokuwiki: Updated for version 20180422a + new maintainer. network/mattermost-desktop: Added (open-source Slack alternative). network/opera-developer: Updated for version 56.0.3003.0. network/opera: Updated for version 54.0.2952.51. network/psi-plus: Added (development branch of Psi IM client). network/qutebrowser: Updated for version 1.4.1. network/riot-web: Updated for version 0.15.7. network/signal-desktop: Updated for version 1.14.0. network/slimjet: Updated for version 19.0.7.0. network/yle-dl: Updated for version 2.34. network/youtube-dl: Updated for version 2018.07.04. office/texlive-docs: Updated for version 2018.180630. office/texlive-extra: Updated for version 2018.180630. office/texlive-fonts: Removed (included in texlive-extra). office/texlive: Updated for version 2018.180630. perl/MoarVM: Added (virtual machine for Rakudo Perl 6 and NQP). perl/nqp: Updated f/v 2018.06, moved from development/ + new maint. perl/perl-Sidef: Updated for version 3.18. perl/perl6-Readline: Added (Perl 6 interface to GNU Readline). perl/rakudo: Updated f/v 2018.06, moved from development/, new maint perl/zef: Added (module management for Perl 6). python/cryptography: Update DEP. python/httplib2: Autodect python3, cleanups. python/python-setuptools-doc: Added (HTML docs for setuptools). python/python2-sip: Added (Tool to generate Python bindings). python/python3-django: Updated for version 2.0.7. ruby/rubygem-rubocop: Updated for version 0.58.1. system/autojump: Updated for version 22.5.1. system/clamav: Updated for version 0.100.1. system/fio: Updated for version 3.7. system/fuse-emulator-utils: Updated for version 1.4.3. system/haveged: Updated for version 1.9.2. system/hh: Updated for version 1.25. system/inxi: Updated for version 3.0.16. system/mailfromd: Added (A General-Purpose Mail Filter). system/nano-syntax-highlighting: Updated for version 20180705. system/onerng: Updated for version 3.6. system/openrc-services: Updated for version 20180617. system/upx: Updated for version 3.94 + new maintainer. system/wine-staging: Updated for version 3.12. system/xonsh: Updated for version 0.6.9. system/zstd: Updated for version 1.3.5. +--------------------------+ -- 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 kjhambrick at gmail.com Sat Jul 14 10:21:24 2018 From: kjhambrick at gmail.com (Konrad J Hambrick) Date: Sat, 14 Jul 2018 05:21:24 -0500 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? In-Reply-To: <20180710224219.14919@web003.roc2.bluetie.com> References: <20180710224219.14919@web003.roc2.bluetie.com> Message-ID: Dimitris -- The DOWNLOAD= URI in this week's youtube-dl.info was also incorrect. When I 'found' and downloaded the File, the MD5SUM= in the youtube-dl.info File was OK and I was able to build a working youtube-gl version 2018-07-04 Ed -- Yes, the URI for the youtube-dl file is predictable. The youtube-dl releases are here: https://github.com/rg3/youtube-dl/releases/ Each YYYY.MM.DD Version is in a ~/YYYY.MM.DD/ subdirectory ( I dropped the https so gmail does not auto-link the 'url' ): github.com/rg3/youtube-dl/releases/YYYY.MM.DD/ And each of the versioned tar.gz files is: github.com/rg3/youtube-dl/releases/YYYY.MM.DD/youtube-dl-YYYY.MM.DD.tar.gz So for example, the DOWNLOAD= setting for Version 2018.07.04 should have been: DOWNLOAD=" https://github.com/rg3/youtube-dl/releases/download/2018.07.04/youtube-dl-2018.07.04.tar.gz " At least the pattern works for now, until they reorganize github :) -- kjh This Q&d script will generate a working youtube-dl.info DOWNLOAD= URI for a DateStamped Version: It can also generate the URI for the corresponding MD5SUMS File for checking the downloaded file. # --- cut here --- #!/bin/sh URI="https://github.com/rg3/youtube-dl/releases/download" VER="<>/youtube-dl-<>.tar.gz" MD5="<>/MD5SUMS" DoMD5=0 [ "$1" = "-m" ] && DoMD5=1 && shift [ $# -lt 1 ] && echo "usage `basename $0` Version [ Version ... ]" >&2 && exit 1 for Str in $@ do Ver="$(echo "$Str" |sed -e 's/\-/./g')" # because I am old and forgetful ... if [ "$DoMD5" != "1" ] then echo "$URI/$VER" |sed -e "s#<>#$Ver#g" else echo "$URI/$MD5" |sed -e "s#<>#$Ver#g" fi done # --- cut there --- Example ... The next version of youtube-dl is 2018-07.10 $ ./.gen-uri.sh 2018.07.10 https://github.com/rg3/youtube-dl/releases/download/2018.07.10/youtube-dl-2018.07.10.tar.gz There is also an MD5SUMS file ... get it ... $ ./.gen-uri.sh -m 2018.07.10 https://github.com/rg3/youtube-dl/releases/download/2018.07.10/MD5SUMS On Tue, Jul 10, 2018 at 9:42 PM, Ed Ender wrote: > This one works too: > https://github.com/rg3/youtube-dl/releases/download/ > 2018.07.10/youtube-dl-2018.07.10.tar.gz > > I prefer not to use referral links myself. > Just my 2 cents. > > Ed > > > -----Original Message----- > From: "Alexander Verbovetsky" [alik at ejik.org] > Date: 07/10/2018 08:37 PM > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? > > Hello, > > > When I suggested to use upstream's releases instead of the auto > > generated ones at github which were causing issues I neglected to > > notice that upstream removed old releases... Sorry about that... > > But this url works: > https://yt-dl.org/downloads/2018.06.25/youtube-dl-2018.06.25.tar.gz > > The broken one is: > http://www.yt-dl.org/downloads/latest/youtube-dl-2018.06.25.tar.gz > > Best regards, > Alexander > _______________________________________________ > 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 alik at ejik.org Sat Jul 14 11:21:04 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 14 Jul 2018 14:21:04 +0300 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? In-Reply-To: <20180710224219.14919@web003.roc2.bluetie.com> References: <20180710224219.14919@web003.roc2.bluetie.com> Message-ID: <1531567264.3688323.1440557096.296B2D48@webmail.messagingengine.com> On Wed, 11 Jul 2018, at 05:42, Ed Ender wrote: > This one works too: > https://github.com/rg3/youtube-dl/releases/download/2018.07.10/youtube-dl-2018.07.10.tar.gz > > I prefer not to use referral links myself. What is a "referral link"? Is the link https://yt-dl.org/downloads/2018.07.10/youtube-dl-2018.07.10.tar.gz bad? These two links give the same file. Thus, I don't understand 1. Why the source from upstream is better then the github source (discussed above in this thread) if they are identical? 2. Why the SlackBuild uses the link http://www.yt-dl.org/downloads/latest/youtube-dl-2018.07.04.tar.gz which is obviously valid for the "latest" release only. 3. Why the SlackBuild suggests version 2018.07.04 instead of 2018.07.10? Best regards, Alexander From skaendo at excite.com Sat Jul 14 12:58:58 2018 From: skaendo at excite.com (Ed Ender) Date: Sat, 14 Jul 2018 08:58:58 -0400 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? Message-ID: <20180714085858.24539@web003.roc2.bluetie.com> >What is a "referral link"? Is the link >https://yt-dl.org/downloads/2018.07.10/youtube-dl-2018.07.10.tar.gz >bad? >1. Why the source from upstream is better then the github source >(discussed above in this thread) if they are identical? When you click the link: https://yt-dl.org/downloads/2018.07.10/youtube-dl-2018.07.10.tar.gz you are not actually downloading anything from "yt-dl.org", but instead it is referring you to download it from GitHub. That is why they are the same, because both links download the exact same file from the exact same place. >2. Why the SlackBuild uses the link >http://www.yt-dl.org/downloads/latest/youtube-dl-2018.07.04.tar.gz >which is obviously valid for the "latest" release only. It is just for aesthetics really I'm guessing. It's really just up to the SlackBuild maintainer what link they prefer to use. -Ed From alik at ejik.org Sat Jul 14 13:31:11 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 14 Jul 2018 16:31:11 +0300 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? In-Reply-To: <20180714085858.24539@web003.roc2.bluetie.com> References: <20180714085858.24539@web003.roc2.bluetie.com> Message-ID: <1531575071.513426.1440627824.4F5F2A28@webmail.messagingengine.com> On Sat, 14 Jul 2018, at 15:58, Ed Ender wrote: > >What is a "referral link"? Is the link > >https://yt-dl.org/downloads/2018.07.10/youtube-dl-2018.07.10.tar.gz > >bad? > > >1. Why the source from upstream is better then the github source > >(discussed above in this thread) if they are identical? > > When you click the link: > https://yt-dl.org/downloads/2018.07.10/youtube-dl-2018.07.10.tar.gz > you are not actually downloading anything from "yt-dl.org", but > instead it is referring you to download it from GitHub. That is why > they are the same, because both links download the exact same file > from the exact same place. Now I understand what do you mean, thank you. BTW, github in both cases is referring me to Amazon's S3 https://github-production-release-asset-2e65be.s3.amazonaws.com > >2. Why the SlackBuild uses the link > >http://www.yt-dl.org/downloads/latest/youtube-dl-2018.07.04.tar.gz > >which is obviously valid for the "latest" release only. > > It is just for aesthetics really I'm guessing. It's really just up to > the SlackBuild maintainer what link they prefer to use. I think it's not just aesthetics, because the ".../latest/..." link is broken. Best regards, Alexander From skaendo at excite.com Sat Jul 14 13:46:52 2018 From: skaendo at excite.com (Ed Ender) Date: Sat, 14 Jul 2018 09:46:52 -0400 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? Message-ID: <20180714094652.32245@web007.roc2.bluetie.com> >Now I understand what do you mean, thank you. BTW, github in both cases >is referring me to Amazon's S3 >https://github-production-release-asset-2e65be.s3.amazonaws.com LOL. So it's a referral that points to another referral. I guess that everybody want's to get that "hit". >I think it's not just aesthetics, because the ".../latest/..." link is >broken. That's my main issue with those links. It's really pointless to use referral links if you have to update them every time. The correct way to use those links is like how Slimjet does and has a file with a generic name. ie; "https://www.slimjetbrowser.com/release/slimjet_amd64.tar.xz" Then the link never changes and never needs to be updated. -Ed From alik at ejik.org Sat Jul 14 13:49:41 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 14 Jul 2018 16:49:41 +0300 Subject: [Slackbuilds-users] texlive: correct md5sum Message-ID: <1531576181.518575.1440638424.13D42895@webmail.messagingengine.com> Hello, the MD5SUM for http://mirrors.ctan.org/systems/texlive/Source/texlive-20180414-source.tar.xz in texlive.SlackBuild should be corrected to 41d1e8874d266935c656fe51b440a413 instead of d7d5fa10e6d16efa76e5111f7a8eb580. Best regards, Alexander From idlemoor at slackbuilds.org Sat Jul 14 20:15:52 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Sat, 14 Jul 2018 21:15:52 +0100 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? In-Reply-To: <20180714094652.32245@web007.roc2.bluetie.com> References: <20180714094652.32245@web007.roc2.bluetie.com> Message-ID: > links is like how Slimjet does and has a file with a generic name. ie; > "https://www.slimjetbrowser.com/release/slimjet_amd64.tar.xz" > Then the link never changes and never needs to be updated. Oh heck *no*. The single worst thing we have to put up with on downloads are unversioned URLs, where the checksum instantly breaks every damn time upstream pushes a new version. If there exists a stable, permanent, versioned URL, please use it. Thanks -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From skaendo at excite.com Sat Jul 14 21:32:41 2018 From: skaendo at excite.com (Ed Ender) Date: Sat, 14 Jul 2018 17:32:41 -0400 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD= moved ? Message-ID: <20180714173241.623@web002.roc2.bluetie.com> >Oh heck *no*. The single worst thing we have to put up with on downloads >are unversioned URLs, where the checksum instantly breaks every damn >time upstream pushes a new version. >If there exists a stable, permanent, versioned URL, please use it. >Thanks >-D. LOL, I totally agree with you. I have been trying to get into the Slimjet forums to see if they would do their repo a little different, but apparently it is impossible to register on their forums (at least it is for me for some reason). I mean I can register, but you need to confirm your email and the conformation email never comes. That and there is zero way to contact them outside of the forum. -Ed From brent at exitstatusone.com Sun Jul 15 02:33:04 2018 From: brent at exitstatusone.com (Brenton Earl) Date: Sat, 14 Jul 2018 20:33:04 -0600 Subject: [Slackbuilds-users] Numix themes - new maintainer In-Reply-To: References: Message-ID: <664c315b-1b5e-31e2-a17b-b89048cf2e88@exitstatusone.com> Hello, With Edinaldo's permission, I will be taking over maintenance of all of his Numix SlackBuilds: desktop/numix-blue-theme desktop/numix-folders desktop/numix-gtk-theme desktop/numix-icon-theme desktop/numix-icon-theme-circle desktop/numix-icon-theme-square desktop/numix-ocean-theme desktop/numix-pack desktop/numix-sx-theme Thanks, Brenton -------- Forwarded Message -------- Subject: Re: Assunto: numix icon theme "circle" on SBo - 404 error Date: Sat, 14 Jul 2018 17:00:26 -0300 From: Edinaldo To: Brenton Earl OK, you can keep them if you want, good luck! ---------- Em Sat, 14 Jul 2018 16:16:25 -0300, Brenton Earl escreveu: > On 07/14/2018 12:46 PM, edps.mundognu at gmail.com wrote: >> * do you have interest in keep these SBo? all related numix-*? >> Please let me know about this. I don't using Numix anymore. > > This is the first time in quite a while that I have installed any of the > Numix icons or themes. I usually use murrine themes. Are these all of > the numix slackbuilds you maintain? > > # grep -l "Edinaldo P. Silva" > /var/lib/sbopkg/SBo/14.2/desktop/numix*/*.info > > /var/lib/sbopkg/SBo/14.2/desktop/numix-blue-theme/numix-blue-theme.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-folders/numix-folders.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-gtk-theme/numix-gtk-theme.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-icon-theme-circle/numix-icon-theme-circle.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-icon-theme-square/numix-icon-theme-square.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-icon-theme/numix-icon-theme.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-ocean-theme/numix-ocean-theme.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-pack/numix-pack.info > /var/lib/sbopkg/SBo/14.2/desktop/numix-sx-theme/numix-sx-theme.info > > Let me know if there are any others related to numix you want to give > me. I can take over maintenance if you would like. > > Thanks, > Brenton From yalhcru at gmail.com Sun Jul 15 08:06:33 2018 From: yalhcru at gmail.com (B Watson) Date: Sun, 15 Jul 2018 04:06:33 -0400 Subject: [Slackbuilds-users] bad downloads, courtesy of sbosrcarch Message-ID: Failed md5sums: gis/rasterio network/vivaldi (32-bit download only, x86_64 is OK) office/texlive 404 Not Found: network/signal-desktop network/youtube-dl (file exists under "releases" but not "latest") The entire website for signal-desktop's download (https://updates.signal.org/) is messed up, and I can't find the file elsewhere. Actually... why is signal-desktop using a .deb? There's source here: https://github.com/signalapp/Signal-Desktop/releases Is it one of those that's a bear to build, like palemoon or qt5? From lists at osh.id.au Sun Jul 15 08:16:45 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Sun, 15 Jul 2018 18:16:45 +1000 Subject: [Slackbuilds-users] bad downloads, courtesy of sbosrcarch In-Reply-To: References: Message-ID: <531cd438-93fb-5a9a-dcec-740f785524eb@osh.id.au> On 07/15/2018 06:06 PM, B Watson wrote: > 404 Not Found: > > network/signal-desktop Ok thanks. They don't normally remove release files, but they must have pulled 1.14.0 for some reason. The current version is 1.14.1 and I've submitted an update for that. > The entire website for signal-desktop's download > (https://updates.signal.org/) is messed up, and I can't find the file > elsewhere. Actually... why is signal-desktop using a .deb? There's > source here: > > https://github.com/signalapp/Signal-Desktop/releases > > Is it one of those that's a bear to build, like palemoon or qt5? I sync the binary releases to my machine using apt-mirror (from SBo). As for building from source, last time I looked there weren't any clear instructions for it, but if anyone wants to have a go, feel free. -- Dave From dave at dawoodfall.net Sun Jul 15 09:07:18 2018 From: dave at dawoodfall.net (David Woodfall) Date: Sun, 15 Jul 2018 10:07:18 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180711023453.GX13829@blackswan> References: <20180703104040.25c89823@Akita.witch.org> <20180711023453.GX13829@blackswan> Message-ID: <20180715090718.GE29592@blackswan> On Wednesday 11 July 2018 03:34, Dave Woodfall put forth the proposition: > On Tuesday 3 July 2018 10:40, > orbea at fredslev.dk put forth the proposition: > > > Maybe you meant this by EOL also, the source mentioned in qt5.info > > > has vanished. Sorry if this is already known by everybody, i didn't > > > follow the qt discussion yet. > > > > I didn't even notice that yet! > > > > I meant that Qt5 upstream released 5.7.1 in December 14 2016 and will > > not update it again. > > > > https://wiki.qt.io/Qt_5.7_Release > > > > When programs I use will soon no longer support releases older than > > 5.9 I can not complain to them that it will no longer build in > > Slackware because by all means we should of updated literally years > > ago... > > I submitted python2-sip earlier (4.19.6 which is in line with the > python3 version on sbo at the moment). > > I've put some basic instructions in README on what options you might > need to supply to applications to build against it, and how to use it > as a module in python2 code. eg: > > --sip-incdir="/usr/include/python$PYTHONVER/python2-sip" \ > --sip=/usr/bin/python2-sip > > and > > import python2_sip python2-sip is now available. The ball is in Larry's court now ;) -- Whoa...I did a 'zcat /vmlinuz > /dev/audio' and I think I heard God... -- mikecd on #Linux .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From slackbuilds at schoepfer.info Sun Jul 15 09:32:44 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 15 Jul 2018 11:32:44 +0200 Subject: [Slackbuilds-users] texlive: correct md5sum In-Reply-To: <1531576181.518575.1440638424.13D42895@webmail.messagingengine.com> References: <1531576181.518575.1440638424.13D42895@webmail.messagingengine.com> Message-ID: <7186aba8bc55b07bde66e7ca60dc0559@schoepfer.info> > the MD5SUM for > http://mirrors.ctan.org/systems/texlive/Source/texlive-20180414-source.tar.xz > in texlive.SlackBuild should be corrected to > 41d1e8874d266935c656fe51b440a413 > instead of > d7d5fa10e6d16efa76e5111f7a8eb580. Yes, sorry, i think i did the md5sum wrongly on a stripped tar-ball like it is shipped in slackware -current. Johannes From brent at exitstatusone.com Mon Jul 16 07:09:34 2018 From: brent at exitstatusone.com (Brenton Earl) Date: Mon, 16 Jul 2018 01:09:34 -0600 Subject: [Slackbuilds-users] Zed editor Message-ID: Hello, Zed editor appears to have been abandoned by the developer after its chrome app version was removed from the chrome app web store. When I volunteered to take over maintenance I had hopes that development would continue in its standalone version for Linux. However there are 169 open issues on the GitHub tracker and there has been no updates within the GitHub repository since May 11, 2015. I am requesting that this package be deleted from SBo. Unless, of course, someone else wishes to become the new maintainer. Info: https://slackbuilds.org/repository/14.2/development/zed/ -Brenton From sbo-usxx.sender.grmblfjx at spamgourmet.com Mon Jul 16 12:56:24 2018 From: sbo-usxx.sender.grmblfjx at spamgourmet.com (sbo-usxx.sender.grmblfjx at spamgourmet.com) Date: Mon, 16 Jul 2018 14:56:24 +0200 Subject: [Slackbuilds-users] youtube-dl DOWNLOAD cont'd Message-ID: Hi, sorry I only have this list on digest so this won't come up in the right thread. Adding to the discussion about the youtube-dl URL, see below for some forwarding shenenigans. youtube-dl not found in /slackstuff/sbopkg/src. --2018-07-16 14:55:12-- http://www.yt-dl.org/downloads/latest/youtube-dl-2018.07.04.tar.gz Resolving www.yt-dl.org... 2001:1a50:11:0:5f:8f:acaa:177, 95.143.172.170 Connecting to www.yt-dl.org|2001:1a50:11:0:5f:8f:acaa:177|:80... connected. HTTP request sent, awaiting response... 302 Found Location: http://www.yt-dl.org/downloads/2018.07.10/youtube-dl-2018.07.04.tar.gz [following] --2018-07-16 14:55:12-- http://www.yt-dl.org/downloads/2018.07.10/youtube-dl-2018.07.04.tar.gz Connecting to www.yt-dl.org|2001:1a50:11:0:5f:8f:acaa:177|:80... connected. HTTP request sent, awaiting response... 302 Found Location: https://github.com/rg3/youtube-dl/releases/download/2018.07.10/youtube-dl-2018.07.04.tar.gz [following] --2018-07-16 14:55:12-- https://github.com/rg3/youtube-dl/releases/download/2018.07.10/youtube-dl-2018.07.04.tar.gz Resolving github.com... 192.30.253.113, 192.30.253.112 Connecting to github.com|192.30.253.113|:443... connected. HTTP request sent, awaiting response... 404 Not Found 2018-07-16 14:55:12 ERROR 404: Not Found. From willysr at slackbuilds.org Mon Jul 16 16:55:55 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 16 Jul 2018 23:55:55 +0700 Subject: [Slackbuilds-users] texlive: correct md5sum In-Reply-To: <1531576181.518575.1440638424.13D42895@webmail.messagingengine.com> References: <1531576181.518575.1440638424.13D42895@webmail.messagingengine.com> Message-ID: > the MD5SUM for > http://mirrors.ctan.org/systems/texlive/Source/texlive-20180414-source.tar.xz > in texlive.SlackBuild should be corrected to > 41d1e8874d266935c656fe51b440a413 > instead of > d7d5fa10e6d16efa76e5111f7a8eb580. Thanks pushed to 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 yalhcru at gmail.com Mon Jul 16 20:06:32 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 16 Jul 2018 16:06:32 -0400 Subject: [Slackbuilds-users] bad downloads, courtesy of sbosrcarch In-Reply-To: <531cd438-93fb-5a9a-dcec-740f785524eb@osh.id.au> References: <531cd438-93fb-5a9a-dcec-740f785524eb@osh.id.au> Message-ID: On 7/15/18, David O'Shaughnessy wrote: > > Ok thanks. They don't normally remove release files, but they must have > pulled 1.14.0 for some reason. The current version is 1.14.1 and I've > submitted an update for that. The 1.14.1 download works (I manually changed the .0 to a .1 in the URL). If they start pulling old releases regularly, before you have time to notice and update the build, maybe someone on this list could help you out by hosting the .deb file somewhere? You'd use their URL as the download link, and it would keep working even if upstream removed the release from their site. That would give you some breathing room at least. From ts at websafe.pl Mon Jul 16 21:06:47 2018 From: ts at websafe.pl (Thomas Szteliga) Date: Mon, 16 Jul 2018 23:06:47 +0200 Subject: [Slackbuilds-users] signal-desktop - download link not working Message-ID: <701075e7-db9f-d4f6-5774-9fb805154b84@websafe.pl> Hello, there's a problem with the download url for signal-desktop: https://slackbuilds.org/repository/14.2/network/signal-desktop/ https://updates.signal.org/desktop/apt/pool/main/s/signal-desktop/signal-desktop_1.14.0_amd64.deb returns 404 Not Found. -- Thomas Szteliga From idlemoor at slackbuilds.org Mon Jul 16 21:19:13 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Mon, 16 Jul 2018 22:19:13 +0100 Subject: [Slackbuilds-users] signal-desktop - download link not working In-Reply-To: <701075e7-db9f-d4f6-5774-9fb805154b84@websafe.pl> References: <701075e7-db9f-d4f6-5774-9fb805154b84@websafe.pl> Message-ID: On 16/07/18 22:06, Thomas Szteliga wrote: > Hello, > > there's a problem with the download url for signal-desktop: > https://slackbuilds.org/repository/14.2/network/signal-desktop/ > > https://updates.signal.org/desktop/apt/pool/main/s/signal-desktop/signal-desktop_1.14.0_amd64.deb > > returns 404 Not Found. Hi, thanks for the report, David already has an update in Willy's branch: https://git.slackbuilds.org/slackbuilds/commit/?id=7b5f4fedc Thanks -D. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Tue Jul 17 00:46:08 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 17 Jul 2018 07:46:08 +0700 Subject: [Slackbuilds-users] Updates - 20180717.1 Message-ID: Hello everyone This is a PLANNED public update as at this moment, 25 years ago, Slackware 1.0 was announced to public. See the official announcement: http://www.slackware.com/announce/1.0.php Since then, Slackware has released 13 releases up to Slackware 14.2 and we are on route to see Slackware 15.0. HAPPY BIRTHDAY SLACKWARE!!! Big Thanks for Patrick Volkerding who has dedicated his life to make sure his baby grown up steadily and maturing on every single releases. Tue Jul 17 00:21:22 UTC 2018 academic/OpenFOAM: Updated for version 6. academic/loggerpro: Update homepage. academic/tuxmath: Update homepage. academic/tuxtype2: Update homepage. audio/xmms-ctl: Update homepage. desktop/crystal: Update homepage. desktop/crystalcursors: Update homepage. desktop/cwp: Update homepage and download. desktop/dunst: bump to version 1.3.2 desktop/kde44-oxygen-molecule: Update homepage. desktop/kfaenza-icon-theme: Update homepage. desktop/neutral: Update homepage and download. desktop/nitrokey-app: Updated for version 1.3.1. desktop/numix-blue-theme: New maintainer. desktop/numix-folders: New maintainer. desktop/numix-gtk-theme: New maintainer. desktop/numix-icon-theme-circle: New maintainer. desktop/numix-icon-theme-square: New maintainer. desktop/numix-icon-theme: New maintainer. desktop/numix-ocean-theme: New maintainer. desktop/numix-pack: New maintainer. desktop/numix-sx-theme: New maintainer. desktop/plasma-adjustable-clock: Update homepage. desktop/plasma-eyasdp: Update homepage. desktop/plasma-geek-clock: Update homepage. desktop/quickaccess: Update homepage. desktop/rootactions_servicemenu: Update homepage. desktop/smaragd: Update homepage and download. desktop/vbox-runner: Update homepage and download. desktop/yawp: Update homepage. development/blassic: Support last alpha version. development/jupyter-notebook: Updated for version 5.6.0. development/kotlin: Updated for version 1.2.51. development/mrustc: Updated for version git5d4bf9e. development/sbcl: Updated for version 1.4.9. development/slibtool: Updated for version 0.5.24. development/smartgit: Switch homepage to https. development/z88dk: Added (C cross compiler targetting the Z80). development/zed: Removed (inactive project). games/jfsw: Enhance script and documentation. games/jfsw_demo_data: Modified to coexist with jfsw_registered_data. games/jfsw_registered_data: Added (Game data for Shadow Warrior). games/jfsw_wanton_destruction: Added (Shadow Warrior expack). games/nSide-libretro: Update SOURCE. games/worldofgoo: Update homepage. gis/geopy: Updated for version 1.15.0. gis/pgsql-ogr-fdw: Updated for version 1.0.6. gis/rasterio: Fix md5sum. libraries/frei0r: Patch for the newer opencv. libraries/libgme: Updated for version 0.6.2. libraries/libhid: Update homepage. libraries/libuv: Updated for version 1.22.0. libraries/t4k_common: Update homepage. misc/abgx360: Switch homepage and download to https. misc/abgx360gui: Switch homepage and download to https. misc/fcitx-qt5: Updated for version 1.2.3. misc/jmri: Updated for version 4.12. misc/pinfo: Update homepage. network/SoulseekQt: Fixed symlink. network/axel: Update homepage. network/dirb: Switch homepage to http. network/lxi-tools: Updated for version 1.21 network/mattermost-desktop: Fixed symlink. network/psi-plus: Updated for version 1.3.398. network/signal-desktop: Updated for version 1.14.1. network/sqlmap: Updated for version 1.2.7. network/telegram: Updated for version 1.3.10. network/tor: Updated for version 0.3.3.9. network/tornado: Updated for version 5.1.0. network/vivaldi: Fix MD5SUM. network/weechat: Updated for version 2.2. network/youtube-dl: Updated for version 2018.07.10. office/MasterPDFEditor: Updated for version 5.0.36. office/texlive: Update MD5SUM. perl/zef: Updated for version 0.4.5. python/parso: Updated for version 0.3.1. python/python-keyring: Updated for version 13.2.1. python/python-prometheus_client: Added (Prometheus instrumentation). python/python3-parso: Updated for version 0.3.1. python/python3-tornado: Updated for version 5.1.0. python/pyzmq: Updated for version 17.1.0. system/ccid: Update homepage. system/chrpath: Updated homepage. system/keybase: Updated for version 2.3.0. system/mdf2iso: Update SOURCE. system/overpass-desktop-fonts: Updated for version 3.0.3. system/overpass-webfonts: Updated for version 3.0.3. system/pcsc-lite: Update homepage. system/pmount: Update homepage. system/pytrash: Updated for version 1.1.3. system/salt: Updated for version 2018.3.2. system/sandbox: Fixed build on 32 bit. system/spman: Updated for version 2.0.0. system/yash: New maintainer. +--------------------------+ -- 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 Tue Jul 17 13:05:09 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 17 Jul 2018 06:05:09 -0700 (PDT) Subject: [Slackbuilds-users] Updates - 20180717.1 In-Reply-To: References: Message-ID: On Tue, 17 Jul 2018, Willy Sudiarto Raharjo wrote: > Big Thanks for Patrick Volkerding who has dedicated his life to make > sure his baby grown up steadily and maturing on every single releases. +1 > office/texlive: Update MD5SUM. Just to confirm: I need to remove all prior texlive packages before running sbopkg and letting it upgrade texlive. Correct? Rich From slackbuilds at schoepfer.info Tue Jul 17 14:08:46 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 17 Jul 2018 16:08:46 +0200 Subject: [Slackbuilds-users] Updates - 20180717.1 In-Reply-To: References: Message-ID: >> office/texlive: Update MD5SUM. > > ? Just to confirm: I need to remove all prior texlive packages before > running sbopkg and letting it upgrade texlive. Correct? remove texlive-fonts and upgrade the others should work. From rshepard at appl-ecosys.com Tue Jul 17 14:32:15 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 17 Jul 2018 07:32:15 -0700 (PDT) Subject: [Slackbuilds-users] Updates - 20180717.1 In-Reply-To: References: Message-ID: On Tue, 17 Jul 2018, Franzen wrote: >> ? Just to confirm: I need to remove all prior texlive packages before >> running sbopkg and letting it upgrade texlive. Correct? > > remove texlive-fonts and upgrade the others should work. Thanks, Franzen. That is a change from the past. Best regards, Rich From yalhcru at gmail.com Tue Jul 17 23:23:51 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 17 Jul 2018 19:23:51 -0400 Subject: [Slackbuilds-users] development/p4d bad md5sum Message-ID: The downloads for development/p4d both have bad md5sums. From david.sullins at gmail.com Wed Jul 18 02:50:12 2018 From: david.sullins at gmail.com (David Sullins) Date: Tue, 17 Jul 2018 21:50:12 -0500 Subject: [Slackbuilds-users] development/p4d bad md5sum In-Reply-To: References: Message-ID: Thanks for noticing, I've submitted an update. Perforce likes to update patch releases but keep the same URL, so every time they patch the software, the md5sum needs to be updated. On Tue, Jul 17, 2018 at 6:23 PM, B Watson wrote: > The downloads for development/p4d both have bad md5sums. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From edps.mundognu at gmail.com Wed Jul 18 21:35:20 2018 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 18 Jul 2018 18:35:20 -0300 Subject: [Slackbuilds-users] Updates - 20180717.1 Message-ID: desktop/smaragd missing quotation marks in download URL: DOWNLOAD=https://dl.opendesktop.org/api/files/downloadfile/id/1483453851/s/275ae1d5d11179944d5eade8383cc546/t/1531675391/u//125162-smaragd-0.0.7.tar.gz" After correct, i get wrong MD5SUM: MD5SUM check for 125162-smaragd-0.0.7.tar.gz ... FAILED! Expected: 2288a0a333b43d635eb476c256b1b01d Found: 6d08f8cfabc9d37ad5a27c8f13463a25 Here's hash MD5 does not match when download by wget too: c659a6cc3933f640121292c790865b48 84c594ec90366a43f3fbab2cdddc95c4 Edinaldo. From idlemoor at slackbuilds.org Wed Jul 18 23:26:04 2018 From: idlemoor at slackbuilds.org (David Spencer) Date: Thu, 19 Jul 2018 00:26:04 +0100 Subject: [Slackbuilds-users] Updates - 20180717.1 In-Reply-To: References: Message-ID: On 18/07/18 22:35, Edinaldo wrote: > desktop/smaragd > > missing quotation marks in download URL: > > DOWNLOAD=https://dl.opendesktop.org/api/files/downloadfile/id/1483453851/s/275ae1d5d11179944d5eade8383cc546/t/1531675391/u//125162-smaragd-0.0.7.tar.gz" > > > After correct, i get wrong MD5SUM: > > ? MD5SUM check for 125162-smaragd-0.0.7.tar.gz ... FAILED! > ??? Expected: 2288a0a333b43d635eb476c256b1b01d > ??? Found:??? 6d08f8cfabc9d37ad5a27c8f13463a25 > > Here's hash MD5 does not match when download by wget too: > > c659a6cc3933f640121292c790865b48 > 84c594ec90366a43f3fbab2cdddc95c4 Damn, the quotation mark is my fault, sorry :( Unfortunately it looks like some of the download URLs at opendesktop.org and its many aliases (store.kde.org etc) that I tried to fix contain a temporary session ID that is globally valid for a limited time. Also, it sends a HTML document instead of a redirect or an error page, which causes the md5sum failure. *All* the opendesktop.org downloads are currently broken. I'll upload the correct tarballs for smaragd and all the others to SBo Direct Links and push fixes to my branch for the next public update. Thanks Edinaldo for telling us :) -D. -------------- 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 Jul 18 23:28:41 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 19 Jul 2018 06:28:41 +0700 Subject: [Slackbuilds-users] Updates - 20180717.1 In-Reply-To: References: Message-ID: <128ada1b-5c9f-b7d9-efcb-9e92a2633dae@slackbuilds.org> >> desktop/smaragd >> >> missing quotation marks in download URL: >> >> DOWNLOAD=https://dl.opendesktop.org/api/files/downloadfile/id/1483453851/s/275ae1d5d11179944d5eade8383cc546/t/1531675391/u//125162-smaragd-0.0.7.tar.gz" >> >> >> After correct, i get wrong MD5SUM: >> >> ? MD5SUM check for 125162-smaragd-0.0.7.tar.gz ... FAILED! >> ??? Expected: 2288a0a333b43d635eb476c256b1b01d >> ??? Found:??? 6d08f8cfabc9d37ad5a27c8f13463a25 >> >> Here's hash MD5 does not match when download by wget too: >> >> c659a6cc3933f640121292c790865b48 >> 84c594ec90366a43f3fbab2cdddc95c4 > > Damn, the quotation mark is my fault, sorry :( > > Unfortunately it looks like some of the download URLs at opendesktop.org > and its many aliases (store.kde.org etc) that I tried to fix contain a > temporary session ID that is globally valid for a limited time. > > Also, it sends a HTML document instead of a redirect or an error page, > which causes the md5sum failure. *All* the opendesktop.org downloads are > currently broken. > > I'll upload the correct tarballs for smaragd and all the others to SBo > Direct Links and push fixes to my branch for the next public update. smaragd is fixed on my branch already -- 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 artourter at gmail.com Fri Jul 20 14:22:55 2018 From: artourter at gmail.com (Greg' Ar Tourter) Date: Fri, 20 Jul 2018 15:22:55 +0100 Subject: [Slackbuilds-users] apparently abandoned packages. Message-ID: Hi admins, I have been using the pdfpc package regularly and notice it was out of date a while back as development had moved to a new team. About a year and a half ago I emailed the slackbuild maintainer who responded that he would update the package but never did. I emailed it back a couple of weeks ago, but haven't got anything back from him. I also noticed that he has not been active on slackbuild for a while now. Can I consider it abandoned and take it over? I have been updating the package for my own use and kept it up-to-date locally so I can easily submit the latest version. For information his packages are: network/gns3 libraries/lablgtk libraries/ocaml-ounit libraries/ocaml-findlib development/ocaml development/racket development/ecl development/newlisp audio/id3tool office/pdfpc system/quotatool system/dynamips desktop/disper desktop/stalonetray Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Fri Jul 20 19:08:36 2018 From: yalhcru at gmail.com (B Watson) Date: Fri, 20 Jul 2018 15:08:36 -0400 Subject: [Slackbuilds-users] apparently abandoned packages. In-Reply-To: References: Message-ID: On 7/20/18, Greg' Ar Tourter wrote: > audio/id3tool If this one's actually available, I'll take it. From willysr at slackbuilds.org Sat Jul 21 00:09:32 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 21 Jul 2018 07:09:32 +0700 Subject: [Slackbuilds-users] Updates - 20180721.1 Message-ID: Sat Jul 21 00:00:19 UTC 2018 academic/R: Updated for version 3.5.1. audio/jack2: Updated for version 1.9.12, new maintainer. audio/snd: Updated for version 18.5. audio/transcribe: Updated for version 8.72. desktop/smaragd: Fix DOWNLOAD. development/ChezScheme: Updated for version 9.5.1_fb826e5. development/Sphinx: Updated for version 1.7.6. development/cgit: Updated for version 1.2. development/ioncube-loader: Updated for version 10.2.3 development/neovim: Updated for version 0.3.1. development/p4d: Updated for version 2018.1.1673397. development/pkgconf: Updated for version 1.5.2. development/rustup: Updated for version 1.13.0. development/tanya: Updated for version 0.11.0 development/universal-ctags: Updated for version 9323929 games/jfsw_demo_data: Modified to coexist with jfsw_registered_data. games/ultimatestunts: Added (remake of DOS racing game 'Stunts'). gis/Fiona: Updated for version 1.7.13. gis/google-earth: Updated for version 7.3.2.5487. graphics/feh: Updated for version 2.27.1. graphics/nomacs: Updated for version 3.10.0. graphics/opencollada: Updated for version 1.6.63 libraries/appstream-glib: Updated for version 0.7.10. libraries/cfitsio: Updated for version 3.45. libraries/log4shib: Updated for version 2.0.0. libraries/opensaml: Updated for version 3.0.0. libraries/xf86-input-libinput: Updated for version 0.28.0. libraries/xml-security-c: Updated for version 2.0.0. libraries/xmltooling: Updated for version 3.0.0. multimedia/plexmediaserver: Updated for v 1.13.4.5251_2e6e8f841. network/WireGuard: Updated for version 0.0.20180718. network/autossh: Updated for version 1.4f, changed maintainer. network/brave: Updated for version 0.23.39. network/nextcloud-client: Updated for version 2.3.3. network/prosody-mod-http-upload: Updated for version hg3176. network/rclone: Updated for version 1.42. network/shibboleth-sp: Updated for version 3.0.0. network/signal-desktop: Updated for version 1.14.3. network/slimjet: Updated for version 19.0.8.0. office/keepassx: Update maintainer email. office/pdf2djvu: Updated for version 0.9.9. python/git-fame: Updated for version 1.5.0. python/pygame: Updated for version 1.9.4. python/python3-pyzmq: Updated foe version 17.1.0 python/stevedore: Updated for version 1.29.0. ruby/rubygem-parser: Updated for version 2.5.1.2. system/bit-babbler: Updated for version 0.8. system/fwupdate: Updated for version 12. system/kitchen-sync: Updated for version 1.1. system/nvme-cli: Updated for version 1.6. system/pspg: Updated for version 1.2.1. system/tarsnap: Update maintainer email. +--------------------------+ -- 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 Sat Jul 21 06:54:55 2018 From: yalhcru at gmail.com (B Watson) Date: Sat, 21 Jul 2018 02:54:55 -0400 Subject: [Slackbuilds-users] autossh Message-ID: 2 problems with this: 1. The md5sum wasn't updated, it's still 26520eea934f296be0783dabe7fcfd28 (which was correct for autossh-1.4c.tgz, not autossh-1.4f.tgz). 2. The download server is saying 'connection refused', tested from multiple locations. Found other copies of autossh-1.4f.tgz here: http://download.openpkg.org/components/cache/autossh/autossh-1.4f.tgz ftp://ftp.osuosl.org/pub/gentoo/distfiles/autossh-1.4f.tgz Both of the above have the same md5sum: 432ed721a71b8af4b5763b5c484f80df ...but of course it doesn't match the .info file because of the 1st problem. From matteo.bernardini at gmail.com Sat Jul 21 10:53:01 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 21 Jul 2018 12:53:01 +0200 Subject: [Slackbuilds-users] autossh In-Reply-To: References: Message-ID: 2018-07-21 8:54 GMT+02:00 B Watson : > 2 problems with this: > > 1. The md5sum wasn't updated, it's still 26520eea934f296be0783dabe7fcfd28 (which > was correct for autossh-1.4c.tgz, not autossh-1.4f.tgz). > > 2. The download server is saying 'connection refused', tested from > multiple locations. > > Found other copies of autossh-1.4f.tgz here: > > http://download.openpkg.org/components/cache/autossh/autossh-1.4f.tgz > > ftp://ftp.osuosl.org/pub/gentoo/distfiles/autossh-1.4f.tgz > > Both of the above have the same md5sum: 432ed721a71b8af4b5763b5c484f80df > > ...but of course it doesn't match the .info file because of the 1st problem. oops, thanks for reporting, I have fixed it in my branch. the homepage was actually working until a few days ago: I'll leave it as it is for a while, maybe it's a temporary issue... Matteo From ewfalor at gmail.com Sat Jul 21 18:05:27 2018 From: ewfalor at gmail.com (Erik Falor) Date: Sat, 21 Jul 2018 12:05:27 -0600 Subject: [Slackbuilds-users] apparently abandoned packages. In-Reply-To: References: Message-ID: <20180721180527.jnve4zut54w4labu@viking2.falor> On Fri, Jul 20, 2018 at 03:22:55PM +0100, Greg' Ar Tourter wrote: > Hi admins, > > I have been using the pdfpc package regularly and notice it was out of date > a while back as development had moved to a new team. > > About a year and a half ago I emailed the slackbuild maintainer who > responded that he would update the package but never did. I emailed it back > a couple of weeks ago, but haven't got anything back from him. I had emailed him a patch for the latest Racket SlackBuild just this week, but haven't yet gotten a reply. If it is determined that these packages are orphaned, I am willing to take care of these: > development/racket > development/newlisp -- 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 cary at SDF.ORG Mon Jul 23 00:29:40 2018 From: cary at SDF.ORG (Cary) Date: Mon, 23 Jul 2018 00:29:40 +0000 Subject: [Slackbuilds-users] build of zathura stops on CURRENT Message-ID: <20180723002939.GA211@SDF.ORG> Hi, everybody. To build the zathura SBo package on Current I needed to add WITH_SYNCTEX=0 . There is a new texlive package in Slackware-current. The slackbuild of zathura halted for me with the following message ... >>> In file included from zathura/synctex.c:8: /usr/include/synctex/synctex_parser.h:53:10: fatal error: synctex_version.h: No such file or directory #include "synctex_version.h" ^~~~~~~~~~~~~~~~~~~ compilation terminated. make: *** [Makefile:96: build/release/zathura/synctex.o] Error 1 rm zathura/resources.c <<< AFAICT, one or mre header files not installed by Slackware are required when building zathura with support for this feature of TeX, and support is optional. Here is some additional info, https://github.com/jlaurens/synctex . -- cary at sdf.org SDF Public Access UNIX System - http://sdf.org From lists at osh.id.au Mon Jul 23 01:21:50 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Mon, 23 Jul 2018 11:21:50 +1000 Subject: [Slackbuilds-users] bad downloads, courtesy of sbosrcarch In-Reply-To: References: <531cd438-93fb-5a9a-dcec-740f785524eb@osh.id.au> Message-ID: <2d07fb99-b0e3-ac54-1a10-9129c543068d@osh.id.au> On 07/17/2018 06:06 AM, B Watson wrote: > If they start pulling old releases regularly, before you have time > to notice and update the build, maybe someone on this list could help > you out by hosting the .deb file somewhere? You'd use their URL as the > download link, and it would keep working even if upstream removed the > release from their site. That would give you some breathing room at least. Looks like they are pulling releases quite quickly now, my 1.14.3 update is gone already. How does sbosrcarch work? Can I submit archives to that? -- Dave From yalhcru at gmail.com Mon Jul 23 05:57:26 2018 From: yalhcru at gmail.com (B Watson) Date: Mon, 23 Jul 2018 01:57:26 -0400 Subject: [Slackbuilds-users] bad downloads, courtesy of sbosrcarch In-Reply-To: <2d07fb99-b0e3-ac54-1a10-9129c543068d@osh.id.au> References: <531cd438-93fb-5a9a-dcec-740f785524eb@osh.id.au> <2d07fb99-b0e3-ac54-1a10-9129c543068d@osh.id.au> Message-ID: On 7/22/18, David O'Shaughnessy wrote: > > Looks like they are pulling releases quite quickly now, my 1.14.3 update > is gone already. How does sbosrcarch work? Can I submit archives to that? sbosrcarch follows the master branch of SBo git... meaning if you notice the file is gone and submit an update, sbosrcarch won't pick up your update until after Willy or David does a public update (usually weekly on weekends). If the release gets pulled again between the time you submit the update and the time of the public update, sbosrcarch won't be able to download that release... The way sbosrcarch works, even if I knew ahead of time about your update, I can't add the file to the archive manually: it will check the md5sum and see that it doesn't match the .info file, and the add will fail. Only after the public update will it work (and in this case, by then, it's too late). However, you could get yourself a sourceforge account and get added to the slackbuildsdirectlinks project, upload files that way. Not sure who's in charge of that (it isn't me) but it's someone on this list who will likely be replying to this message soon :) Failing that, I could host it on naptime.net, but my storage is pretty limited, and it'd be a hassle for you to have to contact me every time the file needs to be updated. Better to use sourceforge so you have control of it yourself. From slackbuilds at schoepfer.info Mon Jul 23 07:15:02 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 23 Jul 2018 09:15:02 +0200 Subject: [Slackbuilds-users] build of zathura stops on CURRENT In-Reply-To: <20180723002939.GA211@SDF.ORG> References: <20180723002939.GA211@SDF.ORG> Message-ID: <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> Hi, > To build the zathura SBo package on Current I needed to add > > WITH_SYNCTEX=0 . > > There is a new texlive package in Slackware-current. This is almost 100% the same package as the one on SBo. Does zathura build on slackware 14.2? >>>> > > In file included from zathura/synctex.c:8: > /usr/include/synctex/synctex_parser.h:53:10: fatal error: > synctex_version.h: No > such file or directory > #include "synctex_version.h" > ^~~~~~~~~~~~~~~~~~~ > compilation terminated. > make: *** [Makefile:96: build/release/zathura/synctex.o] Error 1 > rm zathura/resources.c > > <<< synctex_version.h was never included in texlive, as far as i know. The synctex build from github also doesn't put this header in the system on installation. Does it work if you put https://raw.githubusercontent.com/jlaurens/synctex/2017/synctex_version.h manually in /usr/include/synctex/ ? If not, maybe applying https://git.archlinux.org/svntogit/community.git/plain/trunk/0001-meson.build-Don-t-do-broken-synctex-version-check.patch?h=packages/zathurato the build works. Johannes From matteo.bernardini at gmail.com Mon Jul 23 07:48:26 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 23 Jul 2018 09:48:26 +0200 Subject: [Slackbuilds-users] build of zathura stops on CURRENT In-Reply-To: <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> References: <20180723002939.GA211@SDF.ORG> <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> Message-ID: 2018-07-23 9:15 GMT+02:00 Franzen : > Hi, > >> To build the zathura SBo package on Current I needed to add >> >> WITH_SYNCTEX=0 . >> >> There is a new texlive package in Slackware-current. > > > This is almost 100% the same package as the one on SBo. > Does zathura build on slackware 14.2? > >>>>> >> >> In file included from zathura/synctex.c:8: >> /usr/include/synctex/synctex_parser.h:53:10: fatal error: >> synctex_version.h: No >> such file or directory >> #include "synctex_version.h" >> ^~~~~~~~~~~~~~~~~~~ >> compilation terminated. >> make: *** [Makefile:96: build/release/zathura/synctex.o] Error 1 >> rm zathura/resources.c >> >> <<< > > > synctex_version.h was never included in texlive, as far as i know. > The synctex build from github also doesn't put this header in the > system on installation. > > Does it work if you put > https://raw.githubusercontent.com/jlaurens/synctex/2017/synctex_version.h > manually in /usr/include/synctex/ ? > > If not, maybe applying > https://git.archlinux.org/svntogit/community.git/plain/trunk/0001-meson.build-Don-t-do-broken-synctex-version-check.patch?h=packages/zathurato > the build works. IMHO, the problem is right there in synctex: it's synctex_parser.h, installed with it (together with texlive), that looks for synctex_version.h. archlinux maintainers consider it broken https://bugs.archlinux.org/task/58410 this breaks also, for example, qpdfview https://pastebin.com/raw/pwic3afY Matteo From matteo.bernardini at gmail.com Mon Jul 23 09:22:38 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 23 Jul 2018 11:22:38 +0200 Subject: [Slackbuilds-users] build of zathura stops on CURRENT In-Reply-To: <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> References: <20180723002939.GA211@SDF.ORG> <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> Message-ID: 2018-07-23 9:15 GMT+02:00 Franzen : > Hi, > >> To build the zathura SBo package on Current I needed to add >> >> WITH_SYNCTEX=0 . >> >> There is a new texlive package in Slackware-current. > > > This is almost 100% the same package as the one on SBo. > Does zathura build on slackware 14.2? BTW, I just tested this: with tetex builds fine, with texlive zathura-0.3.8/zathura/version.h.in zathura-0.3.8/zathura/zathura.c zathura-0.3.8/zathura/zathura.h patching file zathura/zathura.c Hunk #1 succeeded at 3 with fuzz 1. Hunk #2 succeeded at 333 with fuzz 1 (offset 216 lines). zathura build options: CFLAGS = -std=c11 -O2 -fPIC -Wall -Wno-format-zero-length -Wextra -pthread -I/usr/include/json-c -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib64/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0/ -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/harfbuzz -I/usr/include/libdrm -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libpng16 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/synctex LIBS = -lmagic -lgthread-2.0 -pthread -lgmodule-2.0 -pthread -lgirara-gtk3 -lgtk-3 -lgdk-3 -lpangocairo-1.0 -lpango-1.0 -latk-1.0 -lcairo-gobject -lcairo -lgdk_pixbuf-2.0 -lgio-2.0 -lgobject-2.0 -lglib-2.0 -lsqlite3 -ldl -lsynctex -lpthread -lm DFLAGS = -g CC = cc [GEN] zathura/resources.h [CC] zathura/adjustment.c [CC] zathura/bookmarks.c [CC] zathura/callbacks.c [CC] zathura/checked-integer-arithmetic.c [CC] zathura/commands.c [CC] zathura/completion.c [CC] zathura/config.c [CC] zathura/content-type.c [CC] zathura/database-plain.c [CC] zathura/database-sqlite.c [CC] zathura/database.c [CC] zathura/dbus-interface.c [CC] zathura/document.c [CC] zathura/file-monitor-glib.c [CC] zathura/file-monitor-signal.c [CC] zathura/file-monitor.c [CC] zathura/jumplist.c [CC] zathura/links.c [CC] zathura/main.c [CC] zathura/marks.c [CC] zathura/page-widget.c [CC] zathura/page.c [CC] zathura/plugin.c [CC] zathura/print.c [CC] zathura/render.c [GEN] zathura/resources.c [CC] zathura/resources.c [CC] zathura/shortcuts.c [CC] zathura/synctex.c In file included from zathura/synctex.c:8:0: /usr/include/synctex/synctex_parser.h:53:29: fatal error: synctex_version.h: No such file or directory compilation terminated. Makefile:93: recipe for target 'build/release/zathura/synctex.o' failed make: *** [build/release/zathura/synctex.o] Error 1 rm zathura/resources.c Matteo From slackbuilds at schoepfer.info Mon Jul 23 10:29:34 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 23 Jul 2018 12:29:34 +0200 Subject: [Slackbuilds-users] build of zathura stops on CURRENT In-Reply-To: References: <20180723002939.GA211@SDF.ORG> <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> Message-ID: <49afc7a6fd84a4de2ada9e2f85e8719a@schoepfer.info> > In file included from zathura/synctex.c:8:0: > /usr/include/synctex/synctex_parser.h:53:29: fatal error: > synctex_version.h: No such file or directory > compilation terminated. Attached patch adds synctex_version.h to texlive, and may be applied to the buildscript by + # Add missing synctex header + patch -Np0 -i $CWD/patches/synctex-missing-header.patch || exit 1 Johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: synctex-missing-header.patch Type: text/x-diff Size: 751 bytes Desc: not available URL: From matteo.bernardini at gmail.com Mon Jul 23 11:12:06 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 23 Jul 2018 13:12:06 +0200 Subject: [Slackbuilds-users] build of zathura stops on CURRENT In-Reply-To: <49afc7a6fd84a4de2ada9e2f85e8719a@schoepfer.info> References: <20180723002939.GA211@SDF.ORG> <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> <49afc7a6fd84a4de2ada9e2f85e8719a@schoepfer.info> Message-ID: 2018-07-23 12:29 GMT+02:00 Franzen : >> In file included from zathura/synctex.c:8:0: >> /usr/include/synctex/synctex_parser.h:53:29: fatal error: >> synctex_version.h: No such file or directory >> compilation terminated. > > > Attached patch adds synctex_version.h to texlive, > and may be applied to the buildscript by > > + # Add missing synctex header > + patch -Np0 -i $CWD/patches/synctex-missing-header.patch || exit 1 Hi Johannes, I applied the patch to texlive and then tried again to rebuild zathura and qpdfview, but unfortunately it seems that synctex still doesn't work :( https://pastebin.com/yTvC4ErA https://pastebin.com/NxBrMAPC Matteo From alik at ejik.org Mon Jul 23 12:30:27 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Mon, 23 Jul 2018 15:30:27 +0300 Subject: [Slackbuilds-users] build of zathura stops on CURRENT In-Reply-To: <20180723002939.GA211@SDF.ORG> References: <20180723002939.GA211@SDF.ORG> Message-ID: <1532349027.3305547.1449795632.460AA192@webmail.messagingengine.com> Hello, > To build the zathura SBo package on Current I needed to add > > WITH_SYNCTEX=0 . Could it be related to the version of zathura? https://pwmt.org/projects/zathura/changelog/ reads: ----- 0.4.0 Port to newer libsynctex ----- Best regards, Alexander From porting at use.startmail.com Mon Jul 23 13:25:27 2018 From: porting at use.startmail.com (=?iso-8859-1?Q?Rub=E9n?= Llorente) Date: Mon, 23 Jul 2018 15:25:27 +0200 Subject: [Slackbuilds-users] TiMidity++ as daemon, failure to connect to pulseaudio Message-ID: <20180723132526.GA49527@miniserver.corrin.dyn> Hello. The instructions provided in TiMidity++'s Slackbuild page for running it as a daemon/alsa sequencer don't work. https://slackbuilds.org/repository/14.2/audio/TiMidity++/ rc.timidity will have the daemon started, but it will fail to generate any sound output. I suspect that, when I start a desktop session, a pulseaudio instance under the privileges of my user gets started. TiMidity++, running as a root daemon, is not authorized to inject sound into Pulseaudio because it is a different user than my desktop one. Could somebody else reproduce this problem and confirm it? A possible solution would be to run pulseaudio as a system wide daemon, but that is too problematic. Another possible solution would be to apply something like this: https://wiki.archlinux.org/index.php/PulseAudio/Examples#Allowing_multiple_users_to_use_PulseAudio_at_the_same_time My suggestion, if this issue is reproducible and shown to be caused for the above reasons, is to update the slackbuild in the following ways: 1- Recommend the creation of a timidity user for running as a daemon. Running the daemon as root is a bit dangerous. 2- Modify rc.timidity for starting the daemon under the privileges of said user. 3- Recommend the solution posted in the Arch wiki. I have yet to try it, and is also a bit dangerous because it allows system-wide access to the daemon run by the user to everybody in the system, unless you take additional messures (such as changing the permissions of the socket?) Trivial solution is to start timidity with the desktop session, running with the privileges of the user sitting in front of the machine. -- OpenPGP Key Fingerprint: BB5A C2A2 2CAD ACB7 D50D C081 1DB9 6FC4 5AB7 92FA From matteo.bernardini at gmail.com Mon Jul 23 13:25:38 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 23 Jul 2018 15:25:38 +0200 Subject: [Slackbuilds-users] build of zathura stops on CURRENT In-Reply-To: References: <20180723002939.GA211@SDF.ORG> <2f7fdb383120f7f85a486912faeeddb3@schoepfer.info> <49afc7a6fd84a4de2ada9e2f85e8719a@schoepfer.info> Message-ID: 2018-07-23 13:12 GMT+02:00 Matteo Bernardini : > 2018-07-23 12:29 GMT+02:00 Franzen : >>> In file included from zathura/synctex.c:8:0: >>> /usr/include/synctex/synctex_parser.h:53:29: fatal error: >>> synctex_version.h: No such file or directory >>> compilation terminated. >> >> >> Attached patch adds synctex_version.h to texlive, >> and may be applied to the buildscript by >> >> + # Add missing synctex header >> + patch -Np0 -i $CWD/patches/synctex-missing-header.patch || exit 1 > > Hi Johannes, > > I applied the patch to texlive and then tried again to rebuild zathura > and qpdfview, but unfortunately it seems that synctex still doesn't > work :( > > https://pastebin.com/yTvC4ErA > > https://pastebin.com/NxBrMAPC actually, if I upgrade qpdfview to the latest beta release it seems to build fine if I apply the above patch to texlive. but, as its README says, zathura cannot be upgraded in stable because the last version compatible with gtk+3 in stable is 0.3.8, so an eventual update that fixes the build with the newer synctex might be current-only. Matteo -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-office-qpdfview-Updated-for-version-0.4.17beta1.patch Type: text/x-patch Size: 6018 bytes Desc: not available URL: From rshepard at appl-ecosys.com Mon Jul 23 16:01:16 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Jul 2018 09:01:16 -0700 (PDT) Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? Message-ID: In a gawk script I'm writing I need to use the switch statment. This web page, , says, "This subsection describes an experimental feature added in gawk 3.1.3. It is not enabled by default. To enable it, use the --enable-switch option to configure when gawk is being configured and built." Looking at the 14.2 gawk-4.1.3 slackbuild script at switch is not enabled; no options are enabled. Should I rebuild gawk-4.1.3 enabling switch? This is the syntax errors I see when I run the script: $ gawk -f trim-fields.awk longform > trimmed gawk: trim-fields.awk:14: switch NR { gawk: trim-fields.awk:14: ^ syntax error gawk: trim-fields.awk:15: case 36: # No shifts present. gawk: trim-fields.awk:15: ^ syntax error gawk: trim-fields.awk:18: case 37: # 1 shift present. gawk: trim-fields.awk:18: ^ syntax error gawk: trim-fields.awk:21: case 38: # 2 shifts present. gawk: trim-fields.awk:21: ^ syntax error gawk: trim-fields.awk:24: case ?: gawk: trim-fields.awk:24: ^ syntax error And this is the script: # Get line length (number of fields) switch NR { case 36: # No shifts present. { print $1, $6, $7, $8, $9, $10, $11, $12, $13, $18, $19, $20, $21, $22, $23, $24, $25, $29, $30, $31, $32, $33, $34, $35, $36 } break case 37: # 1 shift present. { print $1, $6, $7, $8, $9, $10, $11, $12, $13, $19, $20, $21, $22, $23, $24, $25, $26, $30, $31, $32, $33, $34, $35, $36, $37 } break case 38: # 2 shifts present. { print $1, $7, $8, $9, $10, $11, $12, $13, $14, $20, $21, $22, $23, $24, $25, $26, $27, $31, $32, $33, $34, $35, $36, $37, $38 } break case ?: break } The syntax is based on "Effective awk Programming, 4th Ed." by Arnold Robbins, page 154. Rich From dave at dawoodfall.net Mon Jul 23 17:19:34 2018 From: dave at dawoodfall.net (David Woodfall) Date: Mon, 23 Jul 2018 18:19:34 +0100 Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: References: Message-ID: <20180723171934.GA28106@blackswan> On Monday 23 July 2018 09:01, Rich Shepard put forth the proposition: > In a gawk script I'm writing I need to use the switch statment. This web > page, > , > says, "This subsection describes an experimental feature added in gawk > 3.1.3. It is not enabled by default. To enable it, use the --enable-switch > option to configure when gawk is being configured and built." > > Looking at the 14.2 gawk-4.1.3 slackbuild script at > > switch is not enabled; no options are enabled. > > Should I rebuild gawk-4.1.3 enabling switch? Not really a slackbuilds.org question. Did you mean to send it to the slackware list? However, switch is enabled 4.1.3. > And this is the script: > > # Get line length (number of fields) > switch NR { Try switch (NR) { -Dave -- There are no threads in a.b.p.erotica, so there's no gain in using a threaded news reader. -- unknown source .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From rshepard at appl-ecosys.com Mon Jul 23 17:50:20 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Jul 2018 10:50:20 -0700 (PDT) Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: <20180723171934.GA28106@blackswan> References: <20180723171934.GA28106@blackswan> Message-ID: On Mon, 23 Jul 2018, David Woodfall wrote: > Not really a slackbuilds.org question. Did you mean to send it to the > slackware list? Dave, Thought I'd ask here first. > However, switch is enabled 4.1.3. I suspected it would be. > Try switch (NR) { This occurred to me and I did try it. Same syntax errors. Time to try the awk experts. Thanks. Best regards, Rich From dave at dawoodfall.net Mon Jul 23 18:59:48 2018 From: dave at dawoodfall.net (David Woodfall) Date: Mon, 23 Jul 2018 19:59:48 +0100 Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: References: <20180723171934.GA28106@blackswan> Message-ID: <20180723185948.GB28106@blackswan> On Monday 23 July 2018 10:50, Rich Shepard put forth the proposition: > On Mon, 23 Jul 2018, David Woodfall wrote: > > > Not really a slackbuilds.org question. Did you mean to send it to the > > slackware list? > > Dave, > > Thought I'd ask here first. > > > However, switch is enabled 4.1.3. > > I suspected it would be. > > > Try switch (NR) { > > This occurred to me and I did try it. Same syntax errors. You need to surround your code in extra braces {} { } -- The new Linux anthem will be "He's an idiot, but he's ok", as performed by Monthy Python. You'd better start practicing. -- Linus Torvalds, announcing another kernel patch .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From rshepard at appl-ecosys.com Mon Jul 23 20:08:23 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Jul 2018 13:08:23 -0700 (PDT) Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: <20180723185948.GB28106@blackswan> References: <20180723171934.GA28106@blackswan> <20180723185948.GB28106@blackswan> Message-ID: On Mon, 23 Jul 2018, David Woodfall wrote: >>> Try switch (NR) { Dave, That was a type; I meant 'switch (NF)' regardless, ... > You need to surround your code in extra braces {} > > { > > } Actually, the solution was to drop the switch statement and use the NF result as the pattern. This gave me three lines: NF == 36 { print $1, $6, $7, $8, $9, $10, $11, $12, $13, $18, $19, $20, $21, $22, $23, $24, $25, $29, $30, $31, $32, $33, $34, $35, $36 } NF == 37 { print $1, $6, $7, $8, $9, $10, $11, $12, $13, $19, $20, $21, $22, $23, $24, $25, $26, $30, $31, $32, $33, $34, $35, $36, $37 } NF == 38 { print $1, $7, $8, $9, $10, $11, $12, $13, $14, $20, $21, $22, $23, $24, $25, $26, $27, $31, $32, $33, $34, $35, $36, $37, $38 } and this works. Originally, I tested NF in a bash shell script and called separate awk scripts for each one. Realizing this was inefficient I combined the three scripts and tried to replace the bash if-elif-else conditional with the awk switch statement. Using the basic pattern { action } pair is the correct approach. Many thanks, Rich From dave at dawoodfall.net Mon Jul 23 20:14:45 2018 From: dave at dawoodfall.net (David Woodfall) Date: Mon, 23 Jul 2018 21:14:45 +0100 Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: References: <20180723171934.GA28106@blackswan> <20180723185948.GB28106@blackswan> Message-ID: <20180723201445.GC28106@blackswan> On Monday 23 July 2018 13:08, Rich Shepard put forth the proposition: > On Mon, 23 Jul 2018, David Woodfall wrote: > > > > > Try switch (NR) { > > Dave, > > That was a type; I meant 'switch (NF)' regardless, ... > > > You need to surround your code in extra braces {} > > > > { > > > > } > > Actually, the solution was to drop the switch statement and use the NF > result as the pattern. This gave me three lines: > > NF == 36 { print $1, $6, $7, $8, $9, $10, $11, $12, $13, $18, $19, $20, $21, $22, $23, $24, $25, $29, $30, $31, $32, $33, $34, $35, $36 } > NF == 37 { print $1, $6, $7, $8, $9, $10, $11, $12, $13, $19, $20, $21, $22, $23, $24, $25, $26, $30, $31, $32, $33, $34, $35, $36, $37 } > NF == 38 { print $1, $7, $8, $9, $10, $11, $12, $13, $14, $20, $21, $22, $23, $24, $25, $26, $27, $31, $32, $33, $34, $35, $36, $37, $38 } > > and this works. > > Originally, I tested NF in a bash shell script and called separate awk > scripts for each one. Realizing this was inefficient I combined the three > scripts and tried to replace the bash if-elif-else conditional with the awk > switch statement. Using the basic pattern { action } pair is the correct > approach. Switch will work with both NF and NR (and usually anything else that you're likely to throw at it). The reason for the extra braces if because that entire switch block is "action" code, and action code belongs in braces. What you have done now is replace the single switch action with multiple tests and actions. -Dave -- > What does ELF stand for (in respect to Linux?) ELF is the first rock group that Ronnie James Dio performed with back in the early 1970's. In constrast, a.out is a misspelling of the French word for the month of August. What the two have in common is beyond me, but Linux users seem to use the two words together. -- seen on c.o.l.misc .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From rshepard at appl-ecosys.com Mon Jul 23 20:35:45 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Jul 2018 13:35:45 -0700 (PDT) Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: <20180723201445.GC28106@blackswan> References: <20180723171934.GA28106@blackswan> <20180723185948.GB28106@blackswan> <20180723201445.GC28106@blackswan> Message-ID: On Mon, 23 Jul 2018, David Woodfall wrote: > The reason for the extra braces if because that entire switch block > is "action" code, and action code belongs in braces. Dave, I missed seeing this. > What you have done now is replace the single switch action with > multiple tests and actions. As with most things linux, there are multiple approaches. Thanks very much for showing me my error. Best regards, Rich From glenn.becker at gmail.com Mon Jul 23 20:37:21 2018 From: glenn.becker at gmail.com (Glenn Becker) Date: Mon, 23 Jul 2018 16:37:21 -0400 Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: References: <20180723171934.GA28106@blackswan> <20180723185948.GB28106@blackswan> <20180723201445.GC28106@blackswan> Message-ID: This mailing list kicks ass. Off topic, but heartfelt. I learn so much here from you smart folks. Glenn On Mon, Jul 23, 2018 at 4:35 PM, Rich Shepard wrote: > On Mon, 23 Jul 2018, David Woodfall wrote: > > The reason for the extra braces if because that entire switch block >> is "action" code, and action code belongs in braces. >> > > Dave, > > I missed seeing this. > > What you have done now is replace the single switch action with >> multiple tests and actions. >> > > As with most things linux, there are multiple approaches. > > Thanks very much for showing me my error. > > Best regards, > > 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 rshepard at appl-ecosys.com Mon Jul 23 22:22:22 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Jul 2018 15:22:22 -0700 (PDT) Subject: [Slackbuilds-users] Default Slackware 'gawk' build options affecting output? In-Reply-To: References: <20180723171934.GA28106@blackswan> <20180723185948.GB28106@blackswan> <20180723201445.GC28106@blackswan> Message-ID: On Mon, 23 Jul 2018, Glenn Becker wrote: > This mailing list kicks ass. Off topic, but heartfelt. I learn so much here > from you smart folks. Glenn, So do some of us less-smart (at least, non computer professional) folks learn a lot here. Rich From orbea at fredslev.dk Tue Jul 24 01:00:03 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Mon, 23 Jul 2018 18:00:03 -0700 Subject: [Slackbuilds-users] capnproto sandbox violations Message-ID: <20180723180003.22eec545@Akita.witch.org> Hi, I built capnproto with sandbox from SBo and found it resulted with a open_wr violation for /etc/ld.so.cache~. ldconfig < /dev/null > /dev/null 2>&1 || true * ACCESS DENIED: open_wr: /etc/ld.so.cache~ * --------------------------- ACCESS VIOLATION SUMMARY --------------------------- * LOG FILE: "/tmp/sandbox-12065.log" * VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: open_wr S: deny P: /etc/ld.so.cache~ A: /etc/ld.so.cache~ R: /etc/ld.so.cache~ C: ldconfig * -------------------------------------------------------------------------------- This can be easily worked around by adding this line before 'autoreconf'. cd c++ sed -i '/ldconfig References: <20180723132526.GA49527@miniserver.corrin.dyn> Message-ID: On 7/23/18, Rub?n Llorente wrote: > Hello. > > The instructions provided in TiMidity++'s Slackbuild page for running > it as a daemon/alsa sequencer don't work. > https://slackbuilds.org/repository/14.2/audio/TiMidity++/ > > rc.timidity will have the daemon started, but it will fail to generate > any sound output. > > I suspect that, when I start a desktop session, a pulseaudio instance > under the privileges of my user gets started. TiMidity++, running as a > root daemon, is not authorized to inject sound into Pulseaudio because > it is a different user than my desktop one. > > Could somebody else reproduce this problem and confirm it? > > A possible solution would be to run pulseaudio as a system wide daemon, > but that is too problematic. > > Another possible solution would be to apply something like this: > https://wiki.archlinux.org/index.php/PulseAudio/Examples#Allowing_multiple_users_to_use_PulseAudio_at_the_same_time > > My suggestion, if this issue is reproducible and shown to be caused for > the above reasons, is to update the slackbuild in the following ways: > > 1- Recommend the creation of a timidity user for running as a daemon. > Running the daemon as root is a bit dangerous. > 2- Modify rc.timidity for starting the daemon under the privileges of > said user. > 3- Recommend the solution posted in the Arch wiki. I have yet to try it, > and is also a bit dangerous because it allows system-wide access to the > daemon run by the user to everybody in the system, unless you take > additional messures (such as changing the permissions of the socket?) > > Trivial solution is to start timidity with the desktop session, running > with the privileges of the user sitting in front of the machine. I'm listed as maintainer, but I don't think I've ever had a need to use it in daemon mode, and all my systems are mostly PulseAudio-free. So I'm not in a great position to test this. If you find a good solution, would you like to take over maintenance and submit an update? It's been a while since I've needed to use this program and I'm sure the script could use some love. -Kyle From didier at slint.fr Tue Jul 24 06:55:54 2018 From: didier at slint.fr (Didier Spaier) Date: Tue, 24 Jul 2018 08:55:54 +0200 Subject: [Slackbuilds-users] TiMidity++ as daemon, failure to connect to pulseaudio In-Reply-To: References: <20180723132526.GA49527@miniserver.corrin.dyn> Message-ID: <2e507e53-fec5-cd77-3780-6ff98db18271@slint.fr> Hello, On 07/24/2018 07:24 AM, Kyle Guinn wrote: > On 7/23/18, Rub?n Llorente wrote: >> Hello. >> >> The instructions provided in TiMidity++'s Slackbuild page for running >> it as a daemon/alsa sequencer don't work. >> https://slackbuilds.org/repository/14.2/audio/TiMidity++/ >> >> rc.timidity will have the daemon started, but it will fail to generate >> any sound output. >> >> I suspect that, when I start a desktop session, a pulseaudio instance >> under the privileges of my user gets started. TiMidity++, running as a >> root daemon, is not authorized to inject sound into Pulseaudio because >> it is a different user than my desktop one. >> >> Could somebody else reproduce this problem and confirm it? >> >> A possible solution would be to run pulseaudio as a system wide daemon, >> but that is too problematic. >> >> Another possible solution would be to apply something like this: >> https://wiki.archlinux.org/index.php/PulseAudio/Examples#Allowing_multiple_users_to_use_PulseAudio_at_the_same_time >> >> My suggestion, if this issue is reproducible and shown to be caused for >> the above reasons, is to update the slackbuild in the following ways: >> >> 1- Recommend the creation of a timidity user for running as a daemon. >> Running the daemon as root is a bit dangerous. >> 2- Modify rc.timidity for starting the daemon under the privileges of >> said user. >> 3- Recommend the solution posted in the Arch wiki. I have yet to try it, >> and is also a bit dangerous because it allows system-wide access to the >> daemon run by the user to everybody in the system, unless you take >> additional messures (such as changing the permissions of the socket?) >> >> Trivial solution is to start timidity with the desktop session, running >> with the privileges of the user sitting in front of the machine. > > I'm listed as maintainer, but I don't think I've ever had a need to > use it in daemon mode, and all my systems are mostly PulseAudio-free. > So I'm not in a great position to test this. If you find a good > solution, would you like to take over maintenance and submit an > update? It's been a while since I've needed to use this program and > I'm sure the script could use some love. > > -Kyle I have had a similar issue issue with Slint, because we need to start the espeakup daemon early in the boot process so that users can have speech before logging in, thus this daemon has to be started as root. The solution we applied is to use portaudio as audio backend for espeakup. portaudio itself relies on alsa, so to avoid that in turn alsa redirect on pulse we remove from /etc/asound.conf these lines: pcm.default pulse ctl.default pulse Conversely we include in /etc/pulse/default.pa these lines: load-module module-alsa-sink device=dmix load-module module-alsa-source device=dsnoop This way a regular users can use applications relying on pulse, and both alsamixer and pavucontrol work. I never used TiMidity++, but I see in ./configure --help that "--with-default-output=" offers many options. among which alsa, alib, portadio and jack. Maybe try one of these, or maybe just change default.pa and asound.conf as above would suffice? It is easy the check if starting the TiMidity++ daemon spawns pulse, just issue after it starts this command: ps -ef|grep pulse HTH, Didier From lists at osh.id.au Tue Jul 24 07:47:31 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Tue, 24 Jul 2018 17:47:31 +1000 Subject: [Slackbuilds-users] bad downloads, courtesy of sbosrcarch In-Reply-To: References: <531cd438-93fb-5a9a-dcec-740f785524eb@osh.id.au> <2d07fb99-b0e3-ac54-1a10-9129c543068d@osh.id.au> Message-ID: <5fe7e3e6-4236-e1c2-e299-c9a5034469a2@osh.id.au> On 07/23/2018 03:57 PM, B Watson wrote: > However, you could get yourself a sourceforge account and get added > to the slackbuildsdirectlinks project, upload files that way. Not sure > who's in charge of that (it isn't me) but it's someone on this list who > will likely be replying to this message soon :) This would be very handy, I'll sign up for a SourceForge account if someone from SlackBuilds Direct Links could fill me in on what exactly I need to do with it. My riot-web SlackBuild could also benefit from some caching (new releases tend to come quite quickly, and disappear quickly too!). -- Dave From willysr at slackbuilds.org Tue Jul 24 11:16:39 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 24 Jul 2018 18:16:39 +0700 Subject: [Slackbuilds-users] bad downloads, courtesy of sbosrcarch In-Reply-To: <5fe7e3e6-4236-e1c2-e299-c9a5034469a2@osh.id.au> References: <531cd438-93fb-5a9a-dcec-740f785524eb@osh.id.au> <2d07fb99-b0e3-ac54-1a10-9129c543068d@osh.id.au> <5fe7e3e6-4236-e1c2-e299-c9a5034469a2@osh.id.au> Message-ID: <1542188e-9282-f6cf-135f-850e24c065fb@slackbuilds.org> > This would be very handy, I'll sign up for a SourceForge account if > someone from SlackBuilds Direct Links could fill me in on what exactly I > need to do with it. My riot-web SlackBuild could also benefit from some > caching (new releases tend to come quite quickly, and disappear quickly > too!). send me your username, and i will add you as developer so you can upload your own source to the correct folders. -- 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 orbea at fredslev.dk Wed Jul 25 15:57:21 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Wed, 25 Jul 2018 08:57:21 -0700 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180715090718.GE29592@blackswan> Message-ID: <20180725085721.01cbfd07@Akita.witch.org> Given that you are doing great with Qt5 and that Larry has not even bothered to reply to your python2-sip comment my suggestion is that you should maintain Qt5 from this point on. You clearly seem the most willing and capable. From harald.achitz at gmail.com Wed Jul 25 16:16:00 2018 From: harald.achitz at gmail.com (Harald Achitz) Date: Wed, 25 Jul 2018 18:16:00 +0200 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180725085721.01cbfd07@Akita.witch.org> References: <20180715090718.GE29592@blackswan> <20180725085721.01cbfd07@Akita.witch.org> Message-ID: this sounds like a good idea! Am Mi., 25. Juli 2018 um 17:57 Uhr schrieb orbea at fredslev.dk < orbea at fredslev.dk>: > Given that you are doing great with Qt5 and that Larry has not even > bothered to reply to your python2-sip comment my suggestion is that you > should maintain Qt5 from this point on. You clearly seem the most > willing and capable. > _______________________________________________ > 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 porting at use.startmail.com Thu Jul 26 01:05:19 2018 From: porting at use.startmail.com (=?iso-8859-1?Q?Rub=E9n?= Llorente) Date: Thu, 26 Jul 2018 03:05:19 +0200 Subject: [Slackbuilds-users] TiMidity++ as daemon, failure to connect to pulseaudio In-Reply-To: <20180723132526.GA49527@miniserver.corrin.dyn> References: <20180723132526.GA49527@miniserver.corrin.dyn> Message-ID: <20180726010518.GA78079@miniserver.corrin.dyn> Sorry for the delay in the reply and the upcoming thread mess. GMANE is being a bit funky with emails. Kyle Guinn wrote: > I'm listed as maintainer, but I don't think I've ever had a need to > use it in daemon mode, and all my systems are mostly PulseAudio-free. > So I'm not in a great position to test this. If you find a good > solution, would you like to take over maintenance and submit an > update? It's been a while since I've needed to use this program and > I'm sure the script could use some love.Kyle Guinn I don't have an actual need of running the software as a system wide daemon myself either :-) I was just pointing out that, as it is, the rc script included is not working for as expected. I'll just set a new Slackware system and test it all out there just in case, and come back with the results. Didier Spaier wrote: > I have had a similar issue issue with Slint, because we need to start > the espeakup daemon early in the boot process so that users can have > speech before logging in, thus this daemon has to be started as > root. The solution we applied is to use portaudio as audio backend for > espeakup. portaudio itself relies on alsa, so to avoid that in turn > alsa > redirect on pulse we remove from /etc/asound.conf these lines: > pcm.default pulse > ctl.default pulse > > Conversely we include in /etc/pulse/default.pa these lines: > load-module module-alsa-sink device=dmix > load-module module-alsa-source device=dsnoop I can imagine why that works, but adding it as a default recommendation may be too strong. I mean, I bet TiMidity++ is not an essential daemon for most users. I don't think most users are going to change the config of the default sound architecture of their distribution for running MIDI's from dosbox... It makes for awesome advice and a cool README though. -- OpenPGP Key Fingerprint: BB5A C2A2 2CAD ACB7 D50D C081 1DB9 6FC4 5AB7 92FA From dave at dawoodfall.net Thu Jul 26 11:55:06 2018 From: dave at dawoodfall.net (David Woodfall) Date: Thu, 26 Jul 2018 12:55:06 +0100 Subject: [Slackbuilds-users] compton-conf pulling from git Message-ID: <20180726115506.GW32736@blackswan> After the recent updates I rebuilt compton-conf and noticed the following: -- Setting git repository in the translations dir '/tmp/SBo/compton-conf-0.4.0/trans lations' ... Initialized empty Git repository in /tmp/SBo/compton-conf-0.4.0/translations/.git/ -- Pulling the translations... >From https://github.com/lxqt/lxqt-l10n * branch master -> FETCH_HEAD * [new branch] master -> origin/master -Dave -- "One thing they don't tell you about doing experimental physics is that sometimes you must work under adverse conditions ... like a state of sheer terror." -- W. K. Hartmann .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From matteo.bernardini at gmail.com Thu Jul 26 12:46:21 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 26 Jul 2018 14:46:21 +0200 Subject: [Slackbuilds-users] compton-conf pulling from git In-Reply-To: <20180726115506.GW32736@blackswan> References: <20180726115506.GW32736@blackswan> Message-ID: 2018-07-26 13:55 GMT+02:00 David Woodfall : > After the recent updates I rebuilt compton-conf and noticed the > following: > > -- Setting git repository in the translations dir > '/tmp/SBo/compton-conf-0.4.0/trans > lations' ... > Initialized empty Git repository in > /tmp/SBo/compton-conf-0.4.0/translations/.git/ > -- Pulling the translations... > From https://github.com/lxqt/lxqt-l10n > * branch master -> FETCH_HEAD > * [new branch] master -> origin/master adding -DPULL_TRANSLATIONS=No \ between the cmake flags should be enought to avoid that. Matteo From edps.mundognu at gmail.com Thu Jul 26 20:33:25 2018 From: edps.mundognu at gmail.com (Edinaldo) Date: Thu, 26 Jul 2018 17:33:25 -0300 Subject: [Slackbuilds-users] compton-conf pulling from git In-Reply-To: References: <20180726115506.GW32736@blackswan> Message-ID: Thanks @Matteo and @David for the repport, i will update very soon! My Best reggards, Edinaldo Em Thu, 26 Jul 2018 09:46:21 -0300, Matteo Bernardini escreveu: > 2018-07-26 13:55 GMT+02:00 David Woodfall : >> After the recent updates I rebuilt compton-conf and noticed the >> following: >> >> -- Setting git repository in the translations dir >> '/tmp/SBo/compton-conf-0.4.0/trans >> lations' ... >> Initialized empty Git repository in >> /tmp/SBo/compton-conf-0.4.0/translations/.git/ >> -- Pulling the translations... >> From https://github.com/lxqt/lxqt-l10n >> * branch master -> FETCH_HEAD >> * [new branch] master -> origin/master > > adding > > -DPULL_TRANSLATIONS=No \ > > between the cmake flags should be enought to avoid that. > > Matteo From dave at dawoodfall.net Thu Jul 26 20:47:40 2018 From: dave at dawoodfall.net (David Woodfall) Date: Thu, 26 Jul 2018 21:47:40 +0100 Subject: [Slackbuilds-users] compton-conf pulling from git In-Reply-To: References: <20180726115506.GW32736@blackswan> Message-ID: <20180726204740.GC28256@blackswan> On Thursday 26 July 2018 17:33, Edinaldo put forth the proposition: > Thanks @Matteo and @David for the repport, i will update very soon! > > My Best reggards, > > Edinaldo Edinaldo, I see there are a number of releases on the lxqt github page. Perhaps it will work with using the latest release as an extra download and untar it in the translations directory? https://github.com/lxqt/lxqt-l10n -Dave > Em Thu, 26 Jul 2018 09:46:21 -0300, Matteo Bernardini > escreveu: > > > 2018-07-26 13:55 GMT+02:00 David Woodfall : > > > After the recent updates I rebuilt compton-conf and noticed the > > > following: > > > > > > -- Setting git repository in the translations dir > > > '/tmp/SBo/compton-conf-0.4.0/trans > > > lations' ... > > > Initialized empty Git repository in > > > /tmp/SBo/compton-conf-0.4.0/translations/.git/ > > > -- Pulling the translations... > > > From https://github.com/lxqt/lxqt-l10n > > > * branch master -> FETCH_HEAD > > > * [new branch] master -> origin/master > > > > adding > > > > -DPULL_TRANSLATIONS=No \ > > > > between the cmake flags should be enought to avoid that. > > > > Matteo -- The only "intuitive" interface is the nipple. After that, it's all learned. -- Bruce Ediger, bediger at teal.csn.org, on X interfaces .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~' From willysr at slackbuilds.org Sat Jul 28 02:10:13 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Jul 2018 09:10:13 +0700 Subject: [Slackbuilds-users] Updates - 20180728.1 Message-ID: <123c4b50-6be8-ae8c-68b6-93c712fd6268@slackbuilds.org> Hi all This will be the last update in July As you may aware, SlackBuilds Project will not exists without Patrick's work in Slackware, thus we are very grateful that Patrick is doing his job maintaining this wonderful Linux distributions. For those who haven't heard, Patrick had some issues with Slackware Store, which was discussed in length in https://www.linuxquestions.org/questions/slackware-14/donating-to-slackware-4175634729/. Patrick has officially posted his official PayPal link (https://paypal.me/volkerdi) for those who wanted to support Slackware Linux Project directly. This will ensure the continuation of Slackware Linux Project in the future. Sat Jul 28 01:52:35 UTC 2018 academic/ess: Updated for version 17.11. audio/ardour: Really change maintainer. desktop/compton-conf: Update script; added lxqt_l10n sources. desktop/gmrun: Updated for version 0.9.4w. desktop/qtile: Updated for version 0.12.0. development/autogen: Updated for version 5.18.14. development/hhvm: Updated for version 3.24.8 development/hugo: Updated for version 0.45.1. development/mutagen: Updated for version 1.41.0. development/obnc: Updated for version 0.13.3. development/tig: Updated for version 2.4.1. development/tiled: Updated for version 1.1.6. development/universal-ctags: Updated for version 3522685 development/yarn: Updated for version 1.9.2. games/angband: Updated for version 4.1.3. games/freeciv: Updated for version 2.6.0. games/jfsw_demo_data: Add missing doinst.sh. gis/opencpn-plugin-oesenc: Added (oeSENC Charts Plugin). gis/ossim: Updated for version 2.4.2. gis/rasterio: Updated for version 1.0.2. graphics/gimp-plugin-export-layers: Added (Export Layers for GIMP). graphics/teighafileconverter: Updated for v19.5.0.0, new maintainer. graphics/teighaviewer: Updated for version 4.00.0. libraries/libfilezilla: Updated for version 0.13.0. libraries/libinput: Updated for version 1.11.2. libraries/libsixel: Updated for version 1.8.2. libraries/ntl: Updated for version 11.2.1. libraries/wxSQLite3: Updated for version 4.0.4. multimedia/opera-developer-ffmpeg-codecs: Updated for v 0.31.5. multimedia/opera-ffmpeg-codecs: Updated for version 0.31.5. multimedia/plexmediaserver: Updated for v 1.13.4.5271_200287a06. network/autossh: Fixed download link and md5sum. network/brave: Updated for version 0.23.72. network/etcd: Added (key value store for shared configuration). network/filezilla: Updated for version 3.35.1. network/gophernicus: Updated for version 2.5v101, new maintainer. network/megatools: Updated for version 1.10.1. network/nextcloud-server: Updated for version 13.0.5. network/opera-developer: Updated for version 56.0.3013.0. network/opera: Updated for version 54.0.2952.60. network/owncloud-client: Updated for version 2.4.2. network/palemoon-bin: Updated for version 27.9.4. network/palemoon: Updated for version 27.9.4. network/persepolis: Added (Download Manager for aria2). network/signal-desktop: Updated for version 1.14.4. network/waterfox: Updated for version 56.2.2. network/wireshark: Updated for version 2.6.2. network/yandex-browser-beta: Updated for version 18.6.0.2300. network/youtube-dl: Updated for version 2018.07.21. office/anorack: Updated for version 0.2.4. perl/perl-IO-Socket-SSL: Updated for version 2.058. perl/perl-Path-Tiny: Updated for version 0.106. perl/perl6-Readline: Updated for version 0.1.4. python/python-fonttools: Updated for version 3.29.0. python/python-requests: Updated for version 2.19.1. ruby/rubygem-rubocop: Updated for version 0.58.2. system/dosbox-dev: Updated for version 0.74.r4132. system/elo-mt-usb: Added (elo USB multitouch controller driver). system/forkstat: Updated for version 0.02.05. system/inxi: Updated for version 3.0.19. system/letsencrypt: Updated for version 0.26.1. system/nano-syntax-highlighting: Updated for version 20180715. system/noto-fonts: Updated for version 20180624. system/omnidb-app: Updated for version 2.10.0. system/pspg: Updated for version 1.2.2. system/ttf-crosscorefonts: Updated for version 20180624. system/wine-staging: Updated for version 3.13. +--------------------------+ -- 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 Sat Jul 28 07:59:13 2018 From: yalhcru at gmail.com (B Watson) Date: Sat, 28 Jul 2018 03:59:13 -0400 Subject: [Slackbuilds-users] sbosrcarch coverage at 100% Message-ID: We finally made it to 100% coverage (for now): http://slackware.uk/sbosrcarch/STATUS For those of you who aren't aware of the SBo source archive, more information here: http://slackware.uk/sbosrcarch/README And here: http://slackware.uk/sbosrcarch/FAQ Enjoy! From willysr at slackbuilds.org Sat Jul 28 12:01:15 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Jul 2018 19:01:15 +0700 Subject: [Slackbuilds-users] sbosrcarch coverage at 100% In-Reply-To: References: Message-ID: <52f84727-d31a-1689-6c7e-e5835de70dd8@slackbuilds.org> > We finally made it to 100% coverage (for now): > > http://slackware.uk/sbosrcarch/STATUS > > For those of you who aren't aware of the SBo source archive, more information > here: > > http://slackware.uk/sbosrcarch/README > > And here: > > http://slackware.uk/sbosrcarch/FAQ Hi What about sources that aren't supposed to be mirrored outside the original location? -- 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 Sat Jul 28 17:37:10 2018 From: yalhcru at gmail.com (B Watson) Date: Sat, 28 Jul 2018 13:37:10 -0400 Subject: [Slackbuilds-users] sbosrcarch coverage at 100% In-Reply-To: <52f84727-d31a-1689-6c7e-e5835de70dd8@slackbuilds.org> References: <52f84727-d31a-1689-6c7e-e5835de70dd8@slackbuilds.org> Message-ID: On 7/28/18, Willy Sudiarto Raharjo wrote: > What about sources that aren't supposed to be mirrored outside the > original location? Answered in the FAQ. There's a blacklist, the archiver won't try to download blacklisted sources and doesn't count them towards the completion percentage either. From edps.mundognu at gmail.com Sun Jul 29 01:04:11 2018 From: edps.mundognu at gmail.com (Edinaldo) Date: Sat, 28 Jul 2018 22:04:11 -0300 Subject: [Slackbuilds-users] Bleachbit Slackbuild Message-ID: Hi all, It looks like the bleachbit script maintainer has not been active since 2015, i tried to contact it for more than a month and there was no return. If possible i would like to keep this script. The following scripts are maintained by the same maintainer: academic/gresistor audio/soundconverter desktop/cairo-dock-plugins desktop/cairo-dock development/energia games/playonlinux graphics/shotwell libraries/gnome-media libraries/gnome-vfsmm libraries/gtkmm-utils libraries/libgnomemm libraries/libgnomeuimm libraries/libsuinput misc/gourmet python/gnome-python-desktop python/python-elib.intl system/bleachbit system/gnome-commander According to repology, 10 scripts are outdated: https://repology.org/metapackages/?maintainer=e.van.zanten.evz%40gmail.com&outdated=1 Cheers, Edinaldo From willysr at slackbuilds.org Sun Jul 29 01:19:47 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 29 Jul 2018 08:19:47 +0700 Subject: [Slackbuilds-users] Bleachbit Slackbuild In-Reply-To: References: Message-ID: > It looks like the bleachbit script maintainer has not been active since > 2015, i tried to contact it for more than a month and there was no > return. If possible i would like to keep this script. > > The following scripts are maintained by the same maintainer: > > academic/gresistor > audio/soundconverter > desktop/cairo-dock-plugins > desktop/cairo-dock > development/energia > games/playonlinux > graphics/shotwell > libraries/gnome-media > libraries/gnome-vfsmm > libraries/gtkmm-utils > libraries/libgnomemm > libraries/libgnomeuimm > libraries/libsuinput > misc/gourmet > python/gnome-python-desktop > python/python-elib.intl > system/bleachbit > system/gnome-commander > > According to repology, 10 scripts are outdated: > > https://repology.org/metapackages/?maintainer=e.van.zanten.evz%40gmail.com&outdated=1 Sure, no problem but keep in mind that some GNOME-related projects are limited to certain version as Slackware's GTK+3 version doesn't 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 jgraha8 at gmail.com Sun Jul 29 02:14:06 2018 From: jgraha8 at gmail.com (Jason Graham) Date: Sat, 28 Jul 2018 22:14:06 -0400 Subject: [Slackbuilds-users] connman up for grabs Message-ID: <7f8f1056-6396-616a-7443-18aeec19faf8@gmail.com> I'm putting connman up for grabs. I'm not using the package, and have limited time for testing upgrades, etc. Just let me know if anyone would like to take over as maintainer. Cheers, Jason From artourter at gmail.com Sun Jul 29 12:11:12 2018 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sun, 29 Jul 2018 13:11:12 +0100 Subject: [Slackbuilds-users] apparently abandoned packages. In-Reply-To: <20180721180527.jnve4zut54w4labu@viking2.falor> References: <20180721180527.jnve4zut54w4labu@viking2.falor> Message-ID: Just following up on this, Erik, did you get anything back from Markus? I haven't. Admins, can we consider these packages up for grabs? Cheers Greg On Sat, 21 Jul 2018 at 19:05, Erik Falor wrote: > On Fri, Jul 20, 2018 at 03:22:55PM +0100, Greg' Ar Tourter wrote: > > Hi admins, > > > > I have been using the pdfpc package regularly and notice it was out of > date > > a while back as development had moved to a new team. > > > > About a year and a half ago I emailed the slackbuild maintainer who > > responded that he would update the package but never did. I emailed it > back > > a couple of weeks ago, but haven't got anything back from him. > > I had emailed him a patch for the latest Racket SlackBuild just this > week, but haven't yet gotten a reply. > > If it is determined that these packages are orphaned, I am willing to > take care of these: > > > development/racket > > development/newlisp > > > -- > Erik Falor > Registered Linux User #445632 http://unnovative.net > _______________________________________________ > 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 rshepard at appl-ecosys.com Sun Jul 29 21:54:20 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 29 Jul 2018 14:54:20 -0700 (PDT) Subject: [Slackbuilds-users] Google-earth upgrade question Message-ID: When I ran sbopkg google-earth was offered as an upgrade from the installed --7.3.2.5483. Of course, the md5sums did not match so downloaded the 32-bit .deb from SBo (version -7.3.2.5487). However, when built I have the same 5483 build as the output. Is this something I did incorrectly or was the newest 32-bit version not available from the SBo package page? Regards, Rich From arkadiusz at drabczyk.org Mon Jul 30 14:34:57 2018 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Mon, 30 Jul 2018 14:34:57 +0000 Subject: [Slackbuilds-users] [template] find .. strip doesn't work with whitespaces and ' Message-ID: <20180730143457.GA5282@raspberrypi> Probably not the most important issue but it piqued my interest today. Example list of files: $ ls -1 'l'ibsuper.so 'libsuper.so lib super.so libsuper.so Using find ... strip line from the current template: $ find . -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs stat --format=%n || true xargs: unmatched single quote; by default quotes are special to xargs unless you use the -0 option ./libsuper.so ./libsuper.so I noticed that this issue was first attempted to be fixed in fdf8673: $ find . -print | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs stat --format=%n || true It didn't work of course because -print0 was not used and fix was provided in commit 9fb8a16 which is also what we use today. Current approach not only fails with filenames that contain ' but also with filenames that contain whitespaces: $ ls -1 lib super.so libsuper.so $ find . -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF \ | cut -f 1 -d : | xargs stat --format=%n || true ./libsuper.so stat: cannot stat './lib': No such file or directory stat: cannot stat 'super.so': No such file or directory As crazy as it seems for someone to include whitespace or ' in library name I checked that gcc and ld.so don't have problems with that and as fix was added to the repository I guess someone had to already encounter this problem. IMO the problem with the current approach is that list of files is not passed correctly to the second xargs after cut. A suggested fix would be: $ find . -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF | cut -d : -f1 | tr '\n' '\0' | xargs -0 stat --format=%n || true or: $ find . -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF | cut -d : -f1 | xargs -d '\n' stat --format=%n || true There are 2 problems with that - first, it looks strange and second, it doesn't work correctly with filenames that contain newlines. Arguably, newlines in filenames are even less common that whitespaces and single quotes. Alternative fix that also works with newlines: $ find . -print0 | while read -rd $'\0' x; do file "$x" | grep -e "executable" -e "shared" | grep ELF >/dev/null && stat --format=%n "$x"; done Its disadvantage is that it's much slower than the first fix: $ time find . -print0 | xargs -0 file | grep -e "executable" -e "shared object" | grep ELF | cut -d : -f1 | xargs -d '\n' stat --format=%n || true ./libsuper.so ./'libsuper.so ./lib super.so ./'l'ibsuper.so real 0m0.019s user 0m0.034s sys 0m0.011s $ time find . -print0 | while read -rd $'\0' x; do file "$x" | grep -e "executable" -e "shared" | grep ELF >/dev/null && stat --format=%n "$x"; done./libsuper.so ./libsuper.so ./'libsuper.so ./lib super.so ./'l'ibsuper.so real 0m0.073s user 0m0.094s sys 0m0.034s -- Arkadiusz Drabczyk From orbea at fredslev.dk Mon Jul 30 17:46:12 2018 From: orbea at fredslev.dk (orbea at fredslev.dk) Date: Mon, 30 Jul 2018 10:46:12 -0700 Subject: [Slackbuilds-users] snes9x libretro builds Message-ID: <20180730104612.677a9f14@Akita.witch.org> Hi, I've noticed that the libretro port for snes9x is working upstream and its possible to use that instead of the snes9x-libretro fork from the libretro github repo. Would you be willing to add the libretro build in your script so that snes9x-libretro can be removed and SBo can then benefit from stable releases. This will require only one new optional runtime dependency, RetroArch, which is the frontend to run libretro cores. Other libretro frontends would also potentially work, but I'm not sure any of them have been tested in Slackware before. This can be tested with: retroarch -L /usr/lib64/libretro/snes9x_libretro.so /path/to/game.sfc Or with 32-bit installs it will be /usr/lib/libretro/snes9x_libretro.so. Alternatively it can be loaded via the RetroArch gui too. If the user does not have RetroArch its perfectly safe to ignore the libretro core and just use the gtk+ standalone frontend. Some things to note is that the libretro core does not build for 14.2 and only does for current, but upstream fixed this very quickly when I reported it and the attached patch applies fine to the current stable release. Also I have added the info file from libretro-super to the sources which is required for correct operation with RetroArch which will be installed to: /usr/lib${LIBDIRSUFFIX}/libretro/info/snes9x_libretro.info Thanks, Hunter -------------- next part -------------- A non-text attachment was scrubbed... Name: libretro.patch Type: text/x-patch Size: 3564 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: snes9x.patch Type: text/x-patch Size: 2642 bytes Desc: not available URL: From willysr at slackbuilds.org Mon Jul 30 18:22:31 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 31 Jul 2018 01:22:31 +0700 Subject: [Slackbuilds-users] Google-earth upgrade question In-Reply-To: References: Message-ID: > ? When I ran sbopkg google-earth was offered as an upgrade from the > installed --7.3.2.5483. Of course, the md5sums did not match so downloaded > the 32-bit .deb from SBo (version -7.3.2.5487). > > ? However, when built I have the same 5483 build as the output. > > ? Is this something I did incorrectly or was the newest 32-bit version not > available from the SBo package page? Hi Rich the 32 bit version doesn't get updated anymore i think Google is updating the x86_64 only -- 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 Mon Jul 30 19:26:33 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 30 Jul 2018 12:26:33 -0700 (PDT) Subject: [Slackbuilds-users] Google-earth upgrade question In-Reply-To: References: Message-ID: On Tue, 31 Jul 2018, Willy Sudiarto Raharjo wrote: > the 32 bit version doesn't get updated anymore i think Google is updating > the x86_64 only Willy, That's interesting. There are computers using the Atom CPU which is 32-bit, and probably others. I've not run into any issues using google-earth so I don't know what any new releases provide that the one on this host lacks. Perhaps the 32-bit link can be removed from the SBo page and mention made that like Opera google-earth is now only 64-bit. And, the 32-bit Opera (and chromium) still work here when some web server fails to accommodate the latest firefox versions. Thanks, Rich From chytraeu at sdf.org Tue Jul 31 00:32:59 2018 From: chytraeu at sdf.org (Donald Cooley) Date: Mon, 30 Jul 2018 19:32:59 -0500 Subject: [Slackbuilds-users] youtube-dl PermissionError: [Errno 13] Permission denied: '/usr/lib64/python3.6/site-packages/evdev-1.0.0-py3.6.egg-info/PKG-INFO' Message-ID: I wondered if someone here could help with the error PermissionError: [Errno 13] Permission denied: '/usr/lib64/python3.6/site-packages/evdev-1.0.0-py3.6.egg-info/PKG-INFO'. I get the above error whenever I run youtube-dl. I'm not a heavy user of the application so I am not sure how long I have had this problem with my system. BTW, I get a similar error if I uninstall python-3 and rebuild youtube-dl. Here is output from the terminal: youtube-dl Traceback (most recent call last): File "/usr/bin/youtube-dl", line 6, in from pkg_resources import load_entry_point File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 3088, in @_call_aside File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 3072, in _call_aside f(*args, **kwargs) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 3101, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 565, in _build_master ws = cls() File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 558, in __init__ self.add_entry(entry) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 614, in add_entry for dist in find_distributions(entry, True): File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 1964, in find_on_path for dist in factory(fullpath): File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2034, in distributions_from_metadata root, entry, metadata, precedence=DEVELOP_DIST, File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2473, in from_location py_version=py_version, platform=platform, **kw File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2835, in _reload_version md_version = _version_from_file(self._get_metadata(self.PKG_INFO)) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2437, in _version_from_file line = next(iter(version_lines), '') File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 2627, in _get_metadata for line in self.get_metadata_lines(name): File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 1408, in get_metadata_lines return yield_lines(self.get_metadata(name)) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 1404, in get_metadata value = self._get(self._fn(self.egg_info, name)) File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", line 1516, in _get with open(path, 'rb') as stream: PermissionError: [Errno 13] Permission denied: '/usr/lib64/python3.6/site-packages/evdev-1.0.0-py3.6.egg-info/PKG-INFO' From ewfalor at gmail.com Tue Jul 31 03:05:30 2018 From: ewfalor at gmail.com (Erik Falor) Date: Mon, 30 Jul 2018 21:05:30 -0600 Subject: [Slackbuilds-users] apparently abandoned packages. In-Reply-To: References: <20180721180527.jnve4zut54w4labu@viking2.falor> Message-ID: <20180731030530.5mtf7h3zo2ka3wj4@viking2.falor> On Sun, Jul 29, 2018 at 01:11:12PM +0100, Greg' Ar Tourter wrote: > Just following up on this, Erik, did you get anything back from Markus? I > haven't. No, I have not gotten any word from Markus about development/racket. -- 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 slackbuilds at schoepfer.info Tue Jul 31 12:15:41 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 31 Jul 2018 14:15:41 +0200 Subject: [Slackbuilds-users] sbosrcarch coverage at 100% In-Reply-To: References: Message-ID: <6a8733de-07c8-67bf-0c6d-b2705b56bf00@schoepfer.info> On 28.07.2018 09:59, B Watson wrote: > We finally made it to 100% coverage (for now): > > http://slackware.uk/sbosrcarch/STATUS Removing paths of removed/renamed packaes, e.g. http://slackware.uk/sbosrcarch/by-name/office/texlive-fonts/ may be good. Johannes From dave at dawoodfall.net Tue Jul 31 21:57:21 2018 From: dave at dawoodfall.net (David Woodfall) Date: Tue, 31 Jul 2018 22:57:21 +0100 Subject: [Slackbuilds-users] qt5 is sorely in need of an update In-Reply-To: <20180725085721.01cbfd07@Akita.witch.org> References: <20180715090718.GE29592@blackswan> <20180725085721.01cbfd07@Akita.witch.org> Message-ID: <20180731215721.GB9697@blackswan> On Wednesday 25 July 2018 08:57, orbea at fredslev.dk put forth the proposition: > Given that you are doing great with Qt5 and that Larry has not even > bothered to reply to your python2-sip comment my suggestion is that you > should maintain Qt5 from this point on. You clearly seem the most > willing and capable. I have no problem with doing Qt5 and PyQt5 is Larry doesn't want to keep them updated. -- .--. oo (____)// ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~'