From willysr at slackbuilds.org Sat Nov 2 06:37:32 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 2 Nov 2019 13:37:32 +0700 Subject: [Slackbuilds-users] Updates - 20191102.1 Message-ID: Sat Nov 2 06:30:22 UTC 2019 academic/ngspice: Updated for version 31. academic/veusz: Updated for version 3.1. audio/accuraterip-checksum: Removed (use whipper). audio/apulse: Added (PulseAudio emulation for ALSA). audio/whipper: Updated for version 0.8.0. development/bpython: Updated INFO & README file. development/gambas3: Updated for version 3.14.1. development/lazarus: Updated for version 2.0.6. development/regina-rexx: Update script. games/ags: updated for version 3.5.0.19 games/pinball: Add more patch. games/pioneer: Updated for version 20191009. gis/gpxsee: Updated for version 7.16. gis/opencpn-plugin-oesenc: Updated for version 3.3.8. gis/python-pygeos: Added (Python wrapper for geos). graphics/OpenSubdiv: Script improvement. graphics/gmic: Add missing patch. graphics/libplacebo: Updated for version 1.21.0. graphics/white_dune: Updated for version 1.536. libraries/libxmlb: Updated for version 0.1.13. libraries/live555: Updated for version 2019.10.20 libraries/python-ruamel.yaml: Added (YAML 1.2 parser and emitter). misc/dmg2img: Added man page. misc/pmw: Added (Philip's Music Writer). misc/protobuf3: Updated for version 3.10.1. multimedia/ccextractor: Added (captions extractor for MPEG files). multimedia/devedeng: Updated for version 4.16.0. multimedia/vivaldi-codecs-ffmpeg-extra: Removed (merged to vivaldi). network/anydesk: Updated for version 5.4.0. network/asterisk: Updated for version 16.6.1. network/dropbox: Updated for version 84.4.170. network/hostapd: Updated for version 2.0.6. network/imapfilter: Updated for version 2.6.14. network/palemoon-bin: Updated for version 28.7.2. network/palemoon: Updated for version 28.7.2. network/qutebrowser-tox: Added (keyboard-driven vim-like browser). network/teamviewer: Updated for version 14.7.1965. network/tor-browser: Updated for version 9.0. network/tor: Updated for version 0.4.1.6. network/vivaldi: Updated for version 2.9.1705.31. network/wireshark: Update README. network/zoom-linux: Updated for version 3.0.306796.1020. office/jstock: Updated for version 1.0.7.40. office/smoffice2018: Updated for version 2018_972. perl/perl-Moo: Updated for version 2.003006. perl/perl-Role-Tiny: Updated for version 2.001004. python/python3-lazy-object-proxy: Updated for version 1.4.3. python/subuser: Added (Docker tool). ruby/ruby-build: Updated for version 20191031. sbo/README: Added github link. system/isdct: Update script. system/kbfs: Updated for version 4.7.2_20191028173732. system/keybase: Updated for version 4.7.2. system/loksh: Updated for version 6.6. system/runit-services: Updated for version 20191026. system/sleuthkit: Updated for version 4.7.0. system/telegraf: Updated for version 1.12.4. system/zstd: Fix MD5SUM. +--------------------------+ -- 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 fernando.lopezjr at gmail.com Sat Nov 2 22:24:07 2019 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 2 Nov 2019 16:24:07 -0600 Subject: [Slackbuilds-users] ngspice sbo download fails... Message-ID: ngspice: ngspice not found in /var/cache/sbopkg. --2019-11-02 16:20:52-- https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31.tar.gz/ Resolving sourceforge.net (sourceforge.net)... 216.105.38.13 Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31.tar.gz/download [following] --2019-11-02 16:20:54-- https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31.tar.gz/download Connecting to sourceforge.net (sourceforge.net)|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://downloads.sourceforge.net/project/ngspice/ng-spice-rework/31/ngspice-31.tar.gz?r=&ts=1572733254&use_mirror=iweb [following] --2019-11-02 16:20:54-- https://downloads.sourceforge.net/project/ngspice/ng-spice-rework/31/ngspice-31.tar.gz?r=&ts=1572733254&use_mirror=iweb Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.105.38.13 Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.105.38.13|:443... connected. HTTP request sent, awaiting response... 302 Found Location: https://iweb.dl.sourceforge.net/project/ngspice/ng-spice-rework/31/ngspice-31.tar.gz [following] --2019-11-02 16:20:55-- https://iweb.dl.sourceforge.net/project/ngspice/ng-spice-rework/31/ngspice-31.tar.gz Resolving iweb.dl.sourceforge.net (iweb.dl.sourceforge.net)... 192.175.120.182, 2607:f748:10:12::5f:2 Connecting to iweb.dl.sourceforge.net (iweb.dl.sourceforge.net)|192.175.120.182|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 7250057 (6.9M) [application/x-gzip] Saving to: ?index.html? index.html 100%[===================>] 6.91M 3.49MB/s in 2.0s 2019-11-02 16:20:59 (3.49 MB/s) - ?index.html? saved [7250057/7250057] ngspice not found in /var/cache/sbopkg. ngspice: 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. (Y)es to continue, (N)o to abort, (R)etry the build?: -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Nov 2 23:34:02 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 3 Nov 2019 06:34:02 +0700 Subject: [Slackbuilds-users] ngspice sbo download fails... In-Reply-To: References: Message-ID: <2da15238-e46c-c539-1c2d-73aff5f7d2d6@slackbuilds.org> > HTTP request sent, awaiting response... 200 OK > Length: 7250057 (6.9M) [application/x-gzip] > Saving to: ?index.html? > > index.html 100%[===================>] 6.91M 3.49MB/s in 2.0s > > > 2019-11-02 16:20:59 (3.49 MB/s) - ?index.html? saved [7250057/7250057] > > ngspice not found in /var/cache/sbopkg. > > ngspice: > 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. > > (Y)es to continue, (N)o to abort, (R)etry the build?: Fixed now 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 poprocks at gmail.com Mon Nov 4 02:42:41 2019 From: poprocks at gmail.com (Logan Rathbone) Date: Sun, 3 Nov 2019 21:42:41 -0500 Subject: [Slackbuilds-users] Tesseract - ping LukenShiro Message-ID: <20191104024241.GA9148@darkstar.example.net> Hello, A few weeks ago I was looking to contact LukenShiro, maintain of tesseract (inter alia) since I was hoping to request an update to version 4.x of tesseract. Certain programs such as ocrmypdf from pip are starting to require 4.x of tesseract and up. The email address provided for them, lukenshiro at ngi.it, bounced back. I'd be happy to volunteer to take over as maintainer of tesseract if LukenShiro is no longer interested. Thanks, Logan From willysr at slackbuilds.org Tue Nov 5 02:49:25 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 5 Nov 2019 09:49:25 +0700 Subject: [Slackbuilds-users] Tesseract - ping LukenShiro In-Reply-To: <20191104024241.GA9148@darkstar.example.net> References: <20191104024241.GA9148@darkstar.example.net> Message-ID: > I'd be happy to volunteer to take over as maintainer of > tesseract if LukenShiro is no longer interested. Please do -- Willy Sudiarto Raharjo From dickson.tim at googlemail.com Tue Nov 5 12:12:51 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Tue, 5 Nov 2019 12:12:51 +0000 Subject: [Slackbuilds-users] MuseScore slackbuild Message-ID: There are a couple of typos in MuseScore slackbuild. in the MuseScore.info file MuseScore_General-License.md should be MuseScore_General_License.md the cp line in MuseScore.SlackBuild also needs fixing. cp $CWD/MuseScore_General-License.md share/sound should be cp $CWD/MuseScore_General_License.md share/sound (FWIW version updating to 3.3 works fine with the usual updates to the .info and .SlackBuild ,including the fix mentioned above) Regards, Tim From slackbuilds at schoepfer.info Tue Nov 5 15:22:10 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 5 Nov 2019 16:22:10 +0100 Subject: [Slackbuilds-users] seq24 and amSynth Message-ID: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> Hi, i'd like to take over and update seq24 and amSynth. I mailed to the maintainers a few days ago(see blow), but as these both did not contribute for aabout 8 years, is it ok to just grab the scripts and do the work? -------- Weitergeleitete Nachricht -------- Betreff: amSynth on SBo Datum: Sun, 03 Nov 2019 08:57:19 +0100 Von: Franzen An: nyrednek at gmx.com Hi Christopher, as you are listed as maintainer for https://slackbuilds.org/repository/14.2/audio/amSynth/ , but haven't contributed for about 8 years, may i take over? Johannes -------- Weitergeleitete Nachricht -------- Betreff: seq24 on SBo Datum: Sun, 03 Nov 2019 08:53:52 +0100 Von: Franzen An: ad423520 at hotmail.com Hi Arik, as you are listed as maintainer for https://slackbuilds.org/repository/14.2/audio/seq24/ , but haven't contributed for about 8 years, may i take over? Johannes From matteo.bernardini at gmail.com Tue Nov 5 19:29:19 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 5 Nov 2019 20:29:19 +0100 Subject: [Slackbuilds-users] LukenShiro's SlackBuilds Message-ID: I just heard from LunkenShiro and he told me to forward this communication (his mail is not working anymore and he has connection problems with his pc): --- Ok, unfortunately I cannot maintain anymore my slackbuilds on SBo. I hope to return ASAP... farewell, great guys!!! Take care. --- the stuff he was maintaining follows: development/re2c graphics/tesseract graphics/unpaper libraries/c++-gtk-utils libraries/fltk libraries/hdf5 libraries/reportlab libraries/xforms network/efax-gtk network/pyzor network/sniffjoke network/spamassassin office/flowkeeper office/htmldoc perl/libwww-perl perl/perl-digest-hmac perl/perl-digest-sha1 perl/perl-encode-locale perl/perl-file-listing perl/perl-html-parser perl/perl-html-tagset perl/perl-http-cookies perl/perl-http-daemon perl/perl-http-date perl/perl-http-message perl/perl-http-negotiate perl/perl-lwp-mediatypes perl/perl-net-dns perl/perl-net-http perl/perl-net-ip perl/perl-www-robotrules python/easygui python/html2text python/numexpr python/pychecker python/pydblite python/pyflakes python/pyfltk python/pytables python/python-pmw system/ccid system/ecofont-ttf system/fdupes system/irqbalance system/openct system/opensc system/pcsc-lite system/pcsc-perl system/pcsc-tools everything is up for grabs! Matteo P.S. I shamelessly use my advantage reporting this to option fltk, hdf5, htmldoc, pcsc-lite, perl-digest-hmac, perl-digest-sha1 and re2c, if noone else want them badly... From slackbuilds at jaxartes.net Tue Nov 5 19:39:05 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 05 Nov 2019 11:39:05 -0800 Subject: [Slackbuilds-users] LukenShiro's SlackBuilds In-Reply-To: References: Message-ID: <2220197.3N8DHnmoXT@wintermute.sprawl.net> On Tuesday, 5 November 2019 11:29:19 PST Matteo Bernardini wrote: > python/numexpr I'll take this one. From gerardo.zamudio at linux.com Tue Nov 5 20:54:30 2019 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Tue, 05 Nov 2019 14:54:30 -0600 Subject: [Slackbuilds-users] LukenShiro's SlackBuilds In-Reply-To: References: Message-ID: <16915608.IxQ6tPvYuW@hades.slack.lan> On Tuesday, November 5, 2019 1:29:19 PM CST Matteo Bernardini wrote: > I just heard from LunkenShiro and he told me to forward this > communication (his mail is not working anymore and he has connection > problems with his pc): > > --- > > Ok, unfortunately I cannot maintain anymore my slackbuilds on SBo. > I hope to return ASAP... > farewell, great guys!!! Take care. > > --- > > the stuff he was maintaining follows: > > development/re2c > graphics/tesseract > graphics/unpaper > libraries/c++-gtk-utils > libraries/fltk > libraries/hdf5 > libraries/reportlab > libraries/xforms > network/efax-gtk > network/pyzor > network/sniffjoke > network/spamassassin > office/flowkeeper > office/htmldoc > perl/libwww-perl > perl/perl-digest-hmac > perl/perl-digest-sha1 > perl/perl-encode-locale > perl/perl-file-listing > perl/perl-html-parser > perl/perl-html-tagset > perl/perl-http-cookies > perl/perl-http-daemon > perl/perl-http-date > perl/perl-http-message > perl/perl-http-negotiate > perl/perl-lwp-mediatypes > perl/perl-net-dns > perl/perl-net-http > perl/perl-net-ip > perl/perl-www-robotrules > python/easygui > python/html2text > python/numexpr > python/pychecker > python/pydblite > python/pyflakes > python/pyfltk > python/pytables > python/python-pmw > system/ccid > system/ecofont-ttf > system/fdupes > system/irqbalance > system/openct > system/opensc > system/pcsc-lite > system/pcsc-perl > system/pcsc-tools > > everything is up for grabs! > > Matteo I'll take network/spamassassin network/pyzor > P.S. I shamelessly use my advantage reporting this to option fltk, > hdf5, htmldoc, pcsc-lite, perl-digest-hmac, perl-digest-sha1 and re2c, > if noone else want them badly... Makes sense to maintain pcsc-lite since you maintain libcacard. I think you should take the other pcsc- packages too. It's a good idea to have the same maintainer for related packages, IMHO. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From chris.willing at linux.com Tue Nov 5 23:00:27 2019 From: chris.willing at linux.com (Christoph Willing) Date: Wed, 6 Nov 2019 09:00:27 +1000 Subject: [Slackbuilds-users] LukenShiro's SlackBuilds In-Reply-To: References: Message-ID: On 6/11/19 5:29 am, Matteo Bernardini wrote: > libraries/xforms I'm not actually using it at the moment so I'm happy to defer to an active user but, having used it on IRIX in the 90's, I'd like to look after this one - just for old times sake. chris From jgraham at compukix.net Wed Nov 6 03:36:09 2019 From: jgraham at compukix.net (Jason Graham) Date: Tue, 5 Nov 2019 22:36:09 -0500 Subject: [Slackbuilds-users] pcsc-lite download url broken Message-ID: Hi, The download url for pcsc-lite is broken. The correct upstream location for the current SBo version is: ? https://pcsclite.apdu.fr/files/pcsc-lite-1.8.22.tar.bz2 The md5sum matches what is in the SBo info file. FWIW, version 1.8.25 is available. Kind regards, Jason From jgraham at compukix.net Wed Nov 6 04:03:09 2019 From: jgraham at compukix.net (Jason Graham) Date: Tue, 5 Nov 2019 23:03:09 -0500 Subject: [Slackbuilds-users] pcsc-lite download url broken In-Reply-To: References: Message-ID: All, forget my last message... I forgot that I updated pcsc-lite in my repo sometime back. The url for the version posted on SBo 1.8.14 works correctly. My apologies for the confusion. Best, Jason On 11/5/19 10:36 PM, Jason Graham wrote: > Hi, > > The download url for pcsc-lite is broken. The correct upstream > location for the current SBo version is: > > ? https://pcsclite.apdu.fr/files/pcsc-lite-1.8.22.tar.bz2 > > The md5sum matches what is in the SBo info file. > > FWIW, version 1.8.25 is available. > > Kind regards, > Jason From jdashiel at panix.com Wed Nov 6 06:27:15 2019 From: jdashiel at panix.com (Jude DaShiell) Date: Wed, 6 Nov 2019 01:27:15 -0500 Subject: [Slackbuilds-users] game scribble slackbuild Message-ID: I will check, but suspect the scribble game was not ported over from debian correctly. Reason for this suspicion is when computer plays the first word it has a rack of letters. The rack of letters is not decreased as a result of playing that first word. Worse though is when it's time for the human to play the human doesn't get a rack of letters that show up on the screen anywhere. The debug command as near as I can tell does nothing too. If the game is this defective on debian then the slackbuild builder could not do any better with what was ported from debian otherwise we have a defective build on debian similar to the concept of that amish interactive fiction game with only one possible outcome hard wired into the game. For any that haven't played that zcode game it will be quite short. -- From didier at slint.fr Wed Nov 6 13:51:09 2019 From: didier at slint.fr (Didier Spaier) Date: Wed, 6 Nov 2019 14:51:09 +0100 Subject: [Slackbuilds-users] game scribble slackbuild In-Reply-To: References: Message-ID: <41ea1f67-a988-91d4-842c-fdd274e854ee@slint.fr> Hi Jude and all, Le 06/11/2019 ? 07:27, Jude DaShiell a ?crit : > I will check, but suspect the scribble game was not ported over from > debian correctly. Reason for this suspicion is when computer plays the > first word it has a rack of letters. The rack of letters is not decreased > as a result of playing that first word. Worse though is when it's time > for the human to play the human doesn't get a rack of letters that show up > on the screen anywhere. The debug command as near as I can tell does > nothing too. If the game is this defective on debian then the slackbuild > builder could not do any better with what was ported from debian otherwise > we have a defective build on debian similar to the concept of that amish > interactive fiction game with only one possible outcome hard wired into > the game. For any that haven't played that zcode game it will be quite > short. > Well, this package is not really a port, just the source tarball comes from Debian. Anyway the game works well for me (discarding the warning about termcap, that seems harmless): ---Beginning of screen display--- didier[~]$ scribble Cannot find termcap: failed termcap lookup on xterm-256color at /usr/share/perl5/Term/ReadLine.pm line 373. Use: /usr/games/scribble (where level is 1 to 9) Level #1 (easiest) assumed... Reading words... (168075 found, 2039 w/ definitions) 86 letters remain 0 1 2 3 4 5 6 7 8 9 A B C D E - - - - - - - - - - - - - - - My Words 0| @ - @ - @ |0 1| * + + * |1 2| * - - * |2 3| - * - * - |3 4| * * |4 5| + + + + |5 6| - - - - |6 7| @ - * - @ |7 8| - - - - |8 Your Words: 9| + + + + |9 A| * * |A B| - * - * - |B C| * - - * |C D| * + + * |D E| @ - @ - @ |E - - - - - - - - - - - - - - - 0 1 2 3 4 5 6 7 8 9 A B C D E me:0 E A E N A F A you:0 I go first... Looking............... Thinking. I placed at 67d: 4 UN - one for a total of 4 points. 84 letters remain 0 1 2 3 4 5 6 7 8 9 A B C D E - - - - - - - - - - - - - - - My Words 0| @ - @ - @ |0 un(4) 1| * + + * |1 2| * - - * |2 3| - * - * - |3 4| * * |4 5| + + + + |5 6| - - U - - |6 7| @ - N - @ |7 8| - - - - |8 Your Words: 9| + + + + |9 A| * * |A B| - * - * - |B C| * - - * |C D| * + + * |D E| @ - @ - @ |E - - - - - - - - - - - - - - - 0 1 2 3 4 5 6 7 8 9 A B C D E me:4 E A E N A F A you:0 Enter word as "YXd " (Y=row, X=col, D=a/d) or "help" for other commands. ---end of scree display--- So the computer played first, the rack of letters was decreased from 86 to 84 and I got the rack of letters E A E N A F A. Maye an issue with a screen review function of the screen reader? Which one do you use? At least her espeakup works OK. Or do you use a Braille device? Best, Didier From jdashiel at panix.com Wed Nov 6 16:17:45 2019 From: jdashiel at panix.com (Jude DaShiell) Date: Wed, 6 Nov 2019 11:17:45 -0500 Subject: [Slackbuilds-users] game scribble slackbuild In-Reply-To: <41ea1f67-a988-91d4-842c-fdd274e854ee@slint.fr> References: <41ea1f67-a988-91d4-842c-fdd274e854ee@slint.fr> Message-ID: I use espeakup without xterm outside of x. It could be only one rack exists and each player takes from that rack to play the game. With so little documentation it can be hard to figure out sometimes. On Wed, 6 Nov 2019, Didier Spaier wrote: > Date: Wed, 6 Nov 2019 08:51:09 > From: Didier Spaier > Reply-To: SlackBuilds.org Users List > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] game scribble slackbuild > > Hi Jude and all, > > Le 06/11/2019 ? 07:27, Jude DaShiell a ?crit : > > I will check, but suspect the scribble game was not ported over from > > debian correctly. Reason for this suspicion is when computer plays the > > first word it has a rack of letters. The rack of letters is not decreased > > as a result of playing that first word. Worse though is when it's time > > for the human to play the human doesn't get a rack of letters that show up > > on the screen anywhere. The debug command as near as I can tell does > > nothing too. If the game is this defective on debian then the slackbuild > > builder could not do any better with what was ported from debian otherwise > > we have a defective build on debian similar to the concept of that amish > > interactive fiction game with only one possible outcome hard wired into > > the game. For any that haven't played that zcode game it will be quite > > short. > > > > Well, this package is not really a port, just the source tarball comes > from Debian. Anyway the game works well for me (discarding the warning > about termcap, that seems harmless): > > ---Beginning of screen display--- > didier[~]$ scribble > Cannot find termcap: failed termcap lookup on xterm-256color at > /usr/share/perl5/Term/ReadLine.pm line 373. > > Use: /usr/games/scribble (where level is 1 to 9) > Level #1 (easiest) assumed... > Reading words... (168075 found, 2039 w/ definitions) > > 86 letters remain > 0 1 2 3 4 5 6 7 8 9 A B C D E > - - - - - - - - - - - - - - - My Words > 0| @ - @ - @ |0 > 1| * + + * |1 > 2| * - - * |2 > 3| - * - * - |3 > 4| * * |4 > 5| + + + + |5 > 6| - - - - |6 > 7| @ - * - @ |7 > 8| - - - - |8 Your Words: > 9| + + + + |9 > A| * * |A > B| - * - * - |B > C| * - - * |C > D| * + + * |D > E| @ - @ - @ |E > - - - - - - - - - - - - - - - > 0 1 2 3 4 5 6 7 8 9 A B C D E > > me:0 E A E N A F A you:0 > > I go first... > Looking............... > Thinking. > > I placed at 67d: > 4 UN - one > for a total of 4 points. > > 84 letters remain > 0 1 2 3 4 5 6 7 8 9 A B C D E > - - - - - - - - - - - - - - - My Words > 0| @ - @ - @ |0 un(4) > 1| * + + * |1 > 2| * - - * |2 > 3| - * - * - |3 > 4| * * |4 > 5| + + + + |5 > 6| - - U - - |6 > 7| @ - N - @ |7 > 8| - - - - |8 Your Words: > 9| + + + + |9 > A| * * |A > B| - * - * - |B > C| * - - * |C > D| * + + * |D > E| @ - @ - @ |E > - - - - - - - - - - - - - - - > 0 1 2 3 4 5 6 7 8 9 A B C D E > > me:4 E A E N A F A you:0 > > Enter word as "YXd " (Y=row, X=col, D=a/d) or "help" for other commands. > ---end of scree display--- > > > So the computer played first, the rack of letters was decreased from 86 to > 84 and I got the rack of letters E A E N A F A. > > Maye an issue with a screen review function of the screen reader? > Which one do you use? At least her espeakup works OK. > Or do you use a Braille device? > > Best, > > Didier > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- From poprocks at gmail.com Thu Nov 7 03:29:02 2019 From: poprocks at gmail.com (Logan Rathbone) Date: Wed, 6 Nov 2019 22:29:02 -0500 Subject: [Slackbuilds-users] LukenShiro's SlackBuilds In-Reply-To: References: Message-ID: <20191107032902.GA26913@darkstar.example.net> On Tue, Nov 05, 2019 at 08:29:19PM +0100, Matteo Bernardini wrote: > I just heard from LunkenShiro and he told me to forward this > communication (his mail is not working anymore and he has connection > problems with his pc): > > --- > > Ok, unfortunately I cannot maintain anymore my slackbuilds on SBo. > I hope to return ASAP... > farewell, great guys!!! Take care. > > --- > > the stuff he was maintaining follows: I've already claimed tesseract in my 'ping LukenShiro' thread ;-) I'll take: graphics/unpaper system/irqbalance From dave at slackbuilds.org Thu Nov 7 11:21:06 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 7 Nov 2019 11:21:06 +0000 Subject: [Slackbuilds-users] Anyone use rednotebook and would like to maintain it? Message-ID: <20191107112106.GA12394@blackswan> Does anyone use rednotebook and would like to maintain it? I don't use it now, but there has been some recent activity with it. https://github.com/jendrikseipp/rednotebook -daw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From lramos.prof at yahoo.com.br Sat Nov 9 00:19:16 2019 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Fri, 8 Nov 2019 22:19:16 -0200 Subject: [Slackbuilds-users] Small typo in ngspice README file References: <20191109001915.GA20668.ref@giustizia.org> Message-ID: <20191109001915.GA20668@giustizia.org> Hello, Today I tried to build ngspice version 4.7.0, and the scripts I use to do it behaved abnormally. Tracing what happened, I found a trailing slash in the first source file listed in the DOWNLOAD field of the "info" file. This slash fooled wget and it downloaded an index file instead of the compressed source code. Below I attach a git patch which hopefully solves this small typo. Many thanks, Luiz Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br Subject: [PATCH] academic/ngspice: fixed download URL in info file The DOWNLOAD field of the info file quoted two file URLs, but the first one had a trailing slash that fooled wget, making it act as it was a directory and eventually downloading an index.html file. -- Luiz Ramos, 08/Nov/2019 --- academic/ngspice/ngspice.info | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/academic/ngspice/ngspice.info b/academic/ngspice/ngspice.info index d6e488aa34..cc47ace1ae 100644 --- a/academic/ngspice/ngspice.info +++ b/academic/ngspice/ngspice.info @@ -1,7 +1,7 @@ PRGNAM="ngspice" VERSION="31" HOMEPAGE="http://ngspice.sourceforge.net/" -DOWNLOAD="https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31.tar.gz/ \ +DOWNLOAD="https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31.tar.gz \ https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31-manual.pdf" MD5SUM="f50b4d8c6ecbf01acf121cd9edc3baab \ cd746e20a1a23889acab51d918cc1f77" -- 2.14.5 From lramos.prof at yahoo.com.br Sat Nov 9 00:19:16 2019 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Fri, 8 Nov 2019 22:19:16 -0200 Subject: [Slackbuilds-users] Small typo in ngspice README file References: <20191109001915.GA20668.ref@giustizia.org> Message-ID: <20191109001915.GA20668@giustizia.org> Hello, Today I tried to build ngspice version 4.7.0, and the scripts I use to do it behaved abnormally. Tracing what happened, I found a trailing slash in the first source file listed in the DOWNLOAD field of the "info" file. This slash fooled wget and it downloaded an index file instead of the compressed source code. Below I attach a git patch which hopefully solves this small typo. Many thanks, Luiz Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br Subject: [PATCH] academic/ngspice: fixed download URL in info file The DOWNLOAD field of the info file quoted two file URLs, but the first one had a trailing slash that fooled wget, making it act as it was a directory and eventually downloading an index.html file. -- Luiz Ramos, 08/Nov/2019 --- academic/ngspice/ngspice.info | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/academic/ngspice/ngspice.info b/academic/ngspice/ngspice.info index d6e488aa34..cc47ace1ae 100644 --- a/academic/ngspice/ngspice.info +++ b/academic/ngspice/ngspice.info @@ -1,7 +1,7 @@ PRGNAM="ngspice" VERSION="31" HOMEPAGE="http://ngspice.sourceforge.net/" -DOWNLOAD="https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31.tar.gz/ \ +DOWNLOAD="https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31.tar.gz \ https://sourceforge.net/projects/ngspice/files/ng-spice-rework/31/ngspice-31-manual.pdf" MD5SUM="f50b4d8c6ecbf01acf121cd9edc3baab \ cd746e20a1a23889acab51d918cc1f77" -- 2.14.5 From willysr at slackbuilds.org Sat Nov 9 00:26:45 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Nov 2019 07:26:45 +0700 Subject: [Slackbuilds-users] Small typo in ngspice README file In-Reply-To: <20191109001915.GA20668@giustizia.org> References: <20191109001915.GA20668.ref@giustizia.org> <20191109001915.GA20668@giustizia.org> Message-ID: <7c17f7f3-2b86-3958-db5e-fae8238045d0@slackbuilds.org> > Today I tried to build ngspice version 4.7.0, and the scripts I use to > do it behaved abnormally. Tracing what happened, I found a trailing > slash in the first source file listed in the DOWNLOAD field of the > "info" file. This slash fooled wget and it downloaded an index file > instead of the compressed source code. > > Below I attach a git patch which hopefully solves this small typo. It has been fixed in my branch few days ago -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Nov 9 00:56:34 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Nov 2019 07:56:34 +0700 Subject: [Slackbuilds-users] seq24 and amSynth In-Reply-To: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> References: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> Message-ID: <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> > i'd like to take over and update seq24 and amSynth. I mailed to the > maintainers a few days ago(see blow), but as these both did not > contribute for aabout 8 years, is it ok to just grab the scripts and do > the work? Yes -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Nov 9 06:55:58 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Nov 2019 13:55:58 +0700 Subject: [Slackbuilds-users] Updates - 20191109.1 Message-ID: <206f96fd-52dd-d59c-9ec1-3e8e6fc0b3a4@slackbuilds.org> Sat Nov 9 05:52:41 UTC 2019 academic/ngspice: Fix Download. desktop/jgmenu: Updated for version 3.5. desktop/simplenote: Added missing files. desktop/simplenote: Updated for version 1.10.0. desktop/weston: Added (Reference implementation of a Wayland). desktop/weston: Update DEP. development/Sphinx: Updated for version 2.2.1. development/amazon-corretto: Added (JDK Distribution). development/byacc: Updated for version 20191103. development/composer: Updated for version 1.9.1 development/d-tools: Updated for version 2.089.0 development/dart: Updated for version 2.6.0. development/dmd: Updated for version 2.089.0 development/fossil: Updated for version 2.10. development/google-go-lang: Update to version 1.11.13 development/hhvm: Updated for version 4.8.6 development/hub: Updated for version 2.13.0. development/jupyter-notebook: Updated for version 6.0.2. development/neovim-qt: Updated for version 0.2.15. development/neovim: Updated for version 0.4.3. development/psycopg2: Updated for version 2.8.4. development/radare2: Updated for version 4.0.0. development/universal-ctags: Updated for version be621ae development/vscode-bin: Updated for version 1.40.0. games/gargoyle: updated for version 2019.1 games/hedgewars: Updated for version 1.0.0. gis/OTB: Updated for version 6.6.2. gis/qmapshack: Updated for version 1.14.0. gis/whitebox-tools: Added (geospatial data analysis platform). graphics/tesseract: Updated for version 4.1.0. graphics/unpaper: Updated for version 6.1. graphics/vuescan: Updated for version 9.7.06. graphics/white_dune: Updated for version 1.570. libraries/Botan: Updated for version 2.12.1. libraries/Jinja2: Updated for version 2.10.3. libraries/SOPE: Updated for version 4.1.1. libraries/cryptocpp: Updated for version 8.2.0. libraries/libinput: Updated for version 1.14.3. libraries/libpwquality: Updated for version 1.4.2. libraries/libsass: updated for version 3.6.3 libraries/libuv: Updated for version 1.33.1. libraries/libxkbcommon: Updated for version 0.9.1. libraries/live555: Updated for version 2019.11.06 libraries/wxPython4: Updated for version 4.0.7.post1. libraries/xforms: New maintainer misc/pmw: Update README. multimedia/MuseScore: Fix script. multimedia/obs-studio: Updated for version 24.0.3 multimedia/opera-developer-ffmpeg-codecs: Updated for version 0.41. multimedia/opera-ffmpeg-codecs: Updated for version 0.41. multimedia/plexmediaserver: Updated for v 1.18.1.1973_0f4abfbcc. multimedia/x265: Updated for version 3.2.1. network/acme.sh: Update script. network/glewlwyd: updated for version 2.0.0 network/hostapd: Remove unneeded patches. network/insync: Updated for version 3.0.23.40579. network/ip2location-c: Updated for version 8.0.9. network/onioncat: Updated for version 2.4f. network/opera-developer: Updated for version 66.0.3489.0. network/opera: Updated for version 64.0.3417.83. network/packETH: Small fix and disable warnings-as-errors. network/shadowsocks-libev: Updated for version 3.3.3. network/signal-desktop: Updated for version 1.27.4. network/slimjet: Updated for version 24.0.5.0. network/tor-browser: Updated for version 9.0.1. network/vivaldi: Updated for version 2.9.1705.41. network/webhook: Added (WebHook tool). network/wildfly: Updated for version 18.0.0. office/SOGo: Updated for version 4.1.1. office/calibre-bin: Updated for version 4.3.0. office/keepassxc: Updated for version 2.5.0. office/libreoffice-helppack: Updated for version 6.2.8. office/libreoffice-langpack: Updated for version 6.2.8. office/libreoffice: Updated for version 6.2.8. perl/perl-Devel-PartialDump: Added (Partial dumping of data). perl/perl-MooseX-Types-Structured: Added (Structured Moose types). perl/perl-Parse-Method-Signatures: Added (Parse signatures). perl/perl-TryCatch: Added (Try - Catch operators for Perl 5). python/PyGreSQL: Fix MD5SUM. python/asttokens: Added (Python module). python/decorator: Updated for version 4.4.1. python/numexpr: Updated for version 2.7.0 and new maintainer. python/pelican: Updated for version 4.2.0. python/pycryptodome: Updated for version 3.9.1. python/python-PySnooper: Updated for version 0.2.8. python/python3-astroid: Updated for version 2.3.3. python/python3-gitdb2: Updated for version 2.0.6. python/python3-ipython: Updated for version 7.9.0. python/python3-jupyter-ipykernel: Updated for version 5.1.3. python/python3-packaging: Updated for version 19.2. python/thonny: Updated for version 3.2.2. python/traitlets: Updated for version 4.3.3. ruby/ruby-build: Updated for version 20191105. system/aespipe: Updated for version 2.4f. system/apparmor: Updated for version 2.13.3. system/bleachbit: Updated for version 3.0. system/epson-inkjet-printer-escpr: Updated for version 1.7.5. system/irqbalance: Updated for version 1.6.0. system/letsencrypt: Updated for version 0.40.1. system/pspg: Updated for version 2.5.3. system/samsung-mfp-drivers: Updated for version 1.00.39. system/targetcli-fb: Updated for version 2.1.51. system/vagrant: Updated for version 2.2.6. system/wine-staging: Updated for version 4.19. system/zstd: Updated for version 1.4.4. +--------------------------+ -- 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 alleytrotter at gmail.com Sat Nov 9 14:22:19 2019 From: alleytrotter at gmail.com (John Yost) Date: Sat, 9 Nov 2019 09:22:19 -0500 Subject: [Slackbuilds-users] Tesseract Message-ID: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> getting following error: libtool: link: ranlib .libs/libtesseract_api.a libtool: link: ( cd ".libs" && rm -f "libtesseract_api.la" && ln -s "../libtesseract_api.la" "libtesseract_api.la" ) /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -O2 -std=c++17 -llept -larchive -version-info 4:1 -o libtesseract.la -rpath /usr/lib64 libtesseract_api.la ../ccmain/libtesseract_main.la ../textord/libtesseract_textord.la ../wordrec/libtesseract_wordrec.la ../classify/libtesseract_classify.la ../dict/libtesseract_dict.la ../arch/libtesseract_arch.la ../arch/libtesseract_native.la ../lstm/libtesseract_lstm.la ../ccstruct/libtesseract_ccstruct.la ../cutil/libtesseract_cutil.la ../viewer/libtesseract_viewer.la ../ccutil/libtesseract_ccutil.la ../opencl/libtesseract_opencl.la ../arch/libtesseract_avx.la ../arch/libtesseract_avx2.la ../arch/libtesseract_sse.la -lpthread /usr/bin/grep: /usr/lib64/liblzma.la: No such file or directory /usr/bin/sed: can't read /usr/lib64/liblzma.la: No such file or directory libtool: error: '/usr/lib64/liblzma.la' is not a valid libtool archive Makefile:536: recipe for target 'libtesseract.la' failed make[2]: *** [libtesseract.la] Error 1 make[2]: Leaving directory '/tmp/SBo/tesseract-4.1.0/src/api' Makefile:498: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/tesseract-4.1.0' Makefile:407: recipe for target 'all' failed make: *** [all] Error 2 any help is appreciated -- John David Yost AlleyTrotter pub 2048D/F3BDEB55 2014-05-23 [expires: Never] -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x2C7AF6BEF3BDEB55.asc Type: application/pgp-keys Size: 2294 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Nov 9 14:23:12 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 9 Nov 2019 21:23:12 +0700 Subject: [Slackbuilds-users] Tesseract In-Reply-To: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> References: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> Message-ID: <382871d1-27d2-b1e5-1528-6bc51dd06cf2@slackbuilds.org> > libtool: link: ranlib .libs/libtesseract_api.a > libtool: link: ( cd ".libs" && rm -f "libtesseract_api.la" && ln -s > "../libtesseract_api.la" "libtesseract_api.la" ) > /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -O2 -std=c++17 > -llept -larchive -version-info 4:1 -o libtesseract.la -rpath > /usr/lib64 libtesseract_api.la ../ccmain/libtesseract_main.la > ../textord/libtesseract_textord.la ../wordrec/libtesseract_wordrec.la > ../classify/libtesseract_classify.la ../dict/libtesseract_dict.la > ../arch/libtesseract_arch.la ../arch/libtesseract_native.la > ../lstm/libtesseract_lstm.la ../ccstruct/libtesseract_ccstruct.la > ../cutil/libtesseract_cutil.la ../viewer/libtesseract_viewer.la > ../ccutil/libtesseract_ccutil.la ../opencl/libtesseract_opencl.la > ../arch/libtesseract_avx.la ../arch/libtesseract_avx2.la > ../arch/libtesseract_sse.la -lpthread > /usr/bin/grep: /usr/lib64/liblzma.la: No such file or directory > /usr/bin/sed: can't read /usr/lib64/liblzma.la: No such file or directory > libtool: error: '/usr/lib64/liblzma.la' is not a valid libtool archive > Makefile:536: recipe for target 'libtesseract.la' failed > make[2]: *** [libtesseract.la] Error 1 > make[2]: Leaving directory '/tmp/SBo/tesseract-4.1.0/src/api' > Makefile:498: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/tesseract-4.1.0' > Makefile:407: recipe for target 'all' failed > make: *** [all] Error 2 Did you try to build on -current or in -stable? -- 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 poprocks at gmail.com Sat Nov 9 18:57:48 2019 From: poprocks at gmail.com (Logan Rathbone) Date: Sat, 9 Nov 2019 13:57:48 -0500 Subject: [Slackbuilds-users] Tesseract In-Reply-To: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> References: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> Message-ID: <20191109185748.GA15078@darkstar.example.net> On Sat, Nov 09, 2019 at 09:22:19AM -0500, John Yost wrote: > getting following error: > libtool: link: ranlib .libs/libtesseract_api.a > libtool: link: ( cd ".libs" && rm -f "libtesseract_api.la" && ln -s > "../libtesseract_api.la" "libtesseract_api.la" ) > /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -O2 -std=c++17 > -llept -larchive -version-info 4:1 -o libtesseract.la -rpath > /usr/lib64 libtesseract_api.la ../ccmain/libtesseract_main.la > ../textord/libtesseract_textord.la ../wordrec/libtesseract_wordrec.la > ../classify/libtesseract_classify.la ../dict/libtesseract_dict.la > ../arch/libtesseract_arch.la ../arch/libtesseract_native.la > ../lstm/libtesseract_lstm.la ../ccstruct/libtesseract_ccstruct.la > ../cutil/libtesseract_cutil.la ../viewer/libtesseract_viewer.la > ../ccutil/libtesseract_ccutil.la ../opencl/libtesseract_opencl.la > ../arch/libtesseract_avx.la ../arch/libtesseract_avx2.la > ../arch/libtesseract_sse.la -lpthread > /usr/bin/grep: /usr/lib64/liblzma.la: No such file or directory > /usr/bin/sed: can't read /usr/lib64/liblzma.la: No such file or directory > libtool: error: '/usr/lib64/liblzma.la' is not a valid libtool archive > Makefile:536: recipe for target 'libtesseract.la' failed > make[2]: *** [libtesseract.la] Error 1 > make[2]: Leaving directory '/tmp/SBo/tesseract-4.1.0/src/api' > Makefile:498: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/tesseract-4.1.0' > Makefile:407: recipe for target 'all' failed > make: *** [all] Error 2 > > > any help is appreciated Works for me under -current and 14.2 (clean buildroot). If liblzma.la is not present on your system (it should be there on a clean 14.2 system) I'm assuming you're on -current. Sounds like you may have a broken chain of libtool archives (.la files). See the Slackware Current ChangeLog entry from April 19, 2018. From peter at peter-dambier.de Sat Nov 9 22:52:16 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Sat, 9 Nov 2019 23:52:16 +0100 Subject: [Slackbuilds-users] libc++-3.8.6 on slackware current xlocale.h not found. Message-ID: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> Hi, I am Peter and I am new to this list. Building libc++ aborted with an "xlocale.h" not found error. Digging into the subject I found this xlocale.h actually is a subset of locale.h and should never have escaped into the wild - so now is the time to remove it. As it is not needed, it might actually be empty, why not touch /usr/include/xlocale.h Package libc++-3.8.6-i586-1_SBo.tgz build without any more trouble. Of course this is not the right way to do it. But it may save somebodys day and you can always delete that xlocale.h immediately after building. Beware locate finds lots of xlocale.h: /usr/include/c++/v1/support/fuchsia/xlocale.h /usr/include/c++/v1/support/ibm/xlocale.h /usr/include/c++/v1/support/musl/xlocale.h /usr/include/c++/v1/support/newlib/xlocale.h /usr/include/c++/v1/support/solaris/xlocale.h /usr/include/wx-3.0/wx/xlocale.h but this one used to belong to glibc and lived in /usr/include. Kind regards Peter -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From dave at slackbuilds.org Sun Nov 10 00:23:36 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 10 Nov 2019 00:23:36 +0000 Subject: [Slackbuilds-users] libc++-3.8.6 on slackware current xlocale.h not found. In-Reply-To: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> References: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> Message-ID: <20191110002336.GA25579@blackswan> On Sat 9 Nov 2019 23:52, Peter Dambier put forth the proposition: > Hi, I am Peter and I am new to this list. > > Building libc++ aborted with an "xlocale.h" not found error. > > Digging into the subject I found this xlocale.h actually is > a subset of locale.h and should never have escaped > into the wild - so now is the time to remove it. > > As it is not needed, it might actually be empty, why not > > touch /usr/include/xlocale.h > > Package libc++-3.8.6-i586-1_SBo.tgz build without any > more trouble. > > Of course this is not the right way to do it. But it may > save somebodys day and you can always delete > that xlocale.h immediately after building. > > Beware locate finds lots of xlocale.h: > > /usr/include/c++/v1/support/fuchsia/xlocale.h > /usr/include/c++/v1/support/ibm/xlocale.h > /usr/include/c++/v1/support/musl/xlocale.h > /usr/include/c++/v1/support/newlib/xlocale.h > /usr/include/c++/v1/support/solaris/xlocale.h > /usr/include/wx-3.0/wx/xlocale.h > > but this one used to belong to glibc and lived in > /usr/include. Hi Peter, I have xlocale.h in glibc-2.23 on 14.2. grep xlocale.h /var/log/packages/* /var/log/packages/glibc-2.23-x86_64-4_slack14.2:usr/include/xlocale.h Do you not have this? -Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sun Nov 10 00:40:32 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Sun, 10 Nov 2019 00:40:32 +0000 Subject: [Slackbuilds-users] libc++-3.8.6 on slackware current xlocale.h not found. In-Reply-To: <20191110002336.GA25579@blackswan> References: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> <20191110002336.GA25579@blackswan> Message-ID: <20191110004032.GA307@blackswan> On Sun 10 Nov 2019 00:23, Dave Woodfall put forth the proposition: > On Sat 9 Nov 2019 23:52, > Peter Dambier put forth the proposition: > > Hi, I am Peter and I am new to this list. > > > > Building libc++ aborted with an "xlocale.h" not found error. > > > > Digging into the subject I found this xlocale.h actually is > > a subset of locale.h and should never have escaped > > into the wild - so now is the time to remove it. > > > > As it is not needed, it might actually be empty, why not > > > > touch /usr/include/xlocale.h > > > > Package libc++-3.8.6-i586-1_SBo.tgz build without any > > more trouble. > > > > Of course this is not the right way to do it. But it may > > save somebodys day and you can always delete > > that xlocale.h immediately after building. > > > > Beware locate finds lots of xlocale.h: > > > > /usr/include/c++/v1/support/fuchsia/xlocale.h > > /usr/include/c++/v1/support/ibm/xlocale.h > > /usr/include/c++/v1/support/musl/xlocale.h > > /usr/include/c++/v1/support/newlib/xlocale.h > > /usr/include/c++/v1/support/solaris/xlocale.h > > /usr/include/wx-3.0/wx/xlocale.h > > > > but this one used to belong to glibc and lived in > > /usr/include. > > Hi Peter, > > I have xlocale.h in glibc-2.23 on 14.2. > > grep xlocale.h /var/log/packages/* > /var/log/packages/glibc-2.23-x86_64-4_slack14.2:usr/include/xlocale.h > > Do you not have this? > > -Dave I should add that libc++ built fine for me. -Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From alleytrotter at gmail.com Sun Nov 10 03:49:06 2019 From: alleytrotter at gmail.com (John Yost) Date: Sat, 9 Nov 2019 22:49:06 -0500 Subject: [Slackbuilds-users] Tesseract In-Reply-To: <382871d1-27d2-b1e5-1528-6bc51dd06cf2@slackbuilds.org> References: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> <382871d1-27d2-b1e5-1528-6bc51dd06cf2@slackbuilds.org> Message-ID: <7b009e34-66c1-f82a-c985-a2cee2c2bbed@gmail.com> On 11/9/19 9:23 AM, Willy Sudiarto Raharjo wrote: >> libtool: link: ranlib .libs/libtesseract_api.a >> libtool: link: ( cd ".libs" && rm -f "libtesseract_api.la" && ln -s >> "../libtesseract_api.la" "libtesseract_api.la" ) >> /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -O2 -std=c++17 >> -llept -larchive -version-info 4:1 -o libtesseract.la -rpath >> /usr/lib64 libtesseract_api.la ../ccmain/libtesseract_main.la >> ../textord/libtesseract_textord.la ../wordrec/libtesseract_wordrec.la >> ../classify/libtesseract_classify.la ../dict/libtesseract_dict.la >> ../arch/libtesseract_arch.la ../arch/libtesseract_native.la >> ../lstm/libtesseract_lstm.la ../ccstruct/libtesseract_ccstruct.la >> ../cutil/libtesseract_cutil.la ../viewer/libtesseract_viewer.la >> ../ccutil/libtesseract_ccutil.la ../opencl/libtesseract_opencl.la >> ../arch/libtesseract_avx.la ../arch/libtesseract_avx2.la >> ../arch/libtesseract_sse.la -lpthread >> /usr/bin/grep: /usr/lib64/liblzma.la: No such file or directory >> /usr/bin/sed: can't read /usr/lib64/liblzma.la: No such file or directory >> libtool: error: '/usr/lib64/liblzma.la' is not a valid libtool archive >> Makefile:536: recipe for target 'libtesseract.la' failed >> make[2]: *** [libtesseract.la] Error 1 >> make[2]: Leaving directory '/tmp/SBo/tesseract-4.1.0/src/api' >> Makefile:498: recipe for target 'all-recursive' failed >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory '/tmp/SBo/tesseract-4.1.0' >> Makefile:407: recipe for target 'all' failed >> make: *** [all] Error 2 Thanks Willy & Logan Problem resolved by reinstalling the xz package cheers John -------------- next part -------------- A non-text attachment was scrubbed... Name: 0x2C7AF6BEF3BDEB55.asc Type: application/pgp-keys Size: 2294 bytes Desc: not available URL: From matteo.bernardini at gmail.com Sun Nov 10 06:36:55 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 10 Nov 2019 07:36:55 +0100 Subject: [Slackbuilds-users] libc++-3.8.6 on slackware current xlocale.h not found. In-Reply-To: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> References: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> Message-ID: Il giorno sab 9 nov 2019 alle ore 23:52 Peter Dambier ha scritto: > > Hi, I am Peter and I am new to this list. > > Building libc++ aborted with an "xlocale.h" not found error. > > Digging into the subject I found this xlocale.h actually is > a subset of locale.h and should never have escaped > into the wild - so now is the time to remove it. > > As it is not needed, it might actually be empty, why not > > touch /usr/include/xlocale.h > > Package libc++-3.8.6-i586-1_SBo.tgz build without any > more trouble. > > Of course this is not the right way to do it. But it may > save somebodys day and you can always delete > that xlocale.h immediately after building. > > Beware locate finds lots of xlocale.h: > > /usr/include/c++/v1/support/fuchsia/xlocale.h > /usr/include/c++/v1/support/ibm/xlocale.h > /usr/include/c++/v1/support/musl/xlocale.h > /usr/include/c++/v1/support/newlib/xlocale.h > /usr/include/c++/v1/support/solaris/xlocale.h > /usr/include/wx-3.0/wx/xlocale.h > > but this one used to belong to glibc and lived in > /usr/include. > > Kind regards > Peter this happens to you because xlocale.h has been removed from glibc since version 2.26 so it's not available anymore in the version shipped by current. there are a few ways to workaround this but you shouldn't actually need any: you don't install a separate libc++ in current because is now provided as part of the llvm package. Matteo From peter at peter-dambier.de Sun Nov 10 14:11:21 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Sun, 10 Nov 2019 15:11:21 +0100 Subject: [Slackbuilds-users] libc++-3.8.6 on slackware current xlocale.h not found. In-Reply-To: <20191110002336.GA25579@blackswan> References: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> <20191110002336.GA25579@blackswan> Message-ID: Tankyou Dave, thanyou Matteo. @Dave I am trying to get https://github.com/codilime/veles running on my system. It needs so much stuff, I decided it might be easieer from slackware current. Dont worry about my personal trouble with libc++. 14.2 is working fine. @Matteo I probably built more stuff than I need but veles asks for a lot. qt-creator-llvm and Python/Sphings I am not sure if I really need them. That is how I got into libc++. If I really get veles running, I'll try to make a propper slackbuild. Update veles successfully built. It is more complicated than I thought but it looks beautiful. Cheers Peter On Sun, 10 Nov 2019 00:23:36 +0000 Dave Woodfall wrote: > On Sat 9 Nov 2019 23:52, > Peter Dambier put forth the proposition: > > Hi, I am Peter and I am new to this list. > > > > Building libc++ aborted with an "xlocale.h" not found error. > > > > Digging into the subject I found this xlocale.h actually is > > a subset of locale.h and should never have escaped > > into the wild - so now is the time to remove it. > > > > As it is not needed, it might actually be empty, why not > > > > touch /usr/include/xlocale.h > > > > Package libc++-3.8.6-i586-1_SBo.tgz build without any > > more trouble. > > > > Of course this is not the right way to do it. But it may > > save somebodys day and you can always delete > > that xlocale.h immediately after building. > > > > Beware locate finds lots of xlocale.h: > > > > /usr/include/c++/v1/support/fuchsia/xlocale.h > > /usr/include/c++/v1/support/ibm/xlocale.h > > /usr/include/c++/v1/support/musl/xlocale.h > > /usr/include/c++/v1/support/newlib/xlocale.h > > /usr/include/c++/v1/support/solaris/xlocale.h > > /usr/include/wx-3.0/wx/xlocale.h > > > > but this one used to belong to glibc and lived in > > /usr/include. > > Hi Peter, > > I have xlocale.h in glibc-2.23 on 14.2. > > grep xlocale.h /var/log/packages/* > /var/log/packages/glibc-2.23-x86_64-4_slack14.2:usr/include/xlocale.h > > Do you not have this? > > -Dave -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From milgram at cgpp.com Sun Nov 10 20:38:00 2019 From: milgram at cgpp.com (Judah Milgram) Date: Sun, 10 Nov 2019 15:38:00 -0500 Subject: [Slackbuilds-users] pytesseract In-Reply-To: <20191109185748.GA15078@darkstar.example.net> References: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> <20191109185748.GA15078@darkstar.example.net> Message-ID: <7b7ea286-cf9f-7417-27c4-b4f9b4f422a2@cgpp.com> Thanks for upgrading the slackbuild to tesseract 4! Related thought: sure would be nice to have pytesseract. Is it already part of an existing slackbuild? If not, I'd be happy to take a stab at it. On 11/9/19 1:57 PM, Logan Rathbone wrote: > On Sat, Nov 09, 2019 at 09:22:19AM -0500, John Yost wrote: >> getting following error: >> libtool: link: ranlib .libs/libtesseract_api.a >> libtool: link: ( cd ".libs" && rm -f "libtesseract_api.la" && ln -s >> "../libtesseract_api.la" "libtesseract_api.la" ) >> /bin/sh ../../libtool --tag=CXX --mode=link g++ -g -O2 -std=c++17 >> -llept -larchive -version-info 4:1 -o libtesseract.la -rpath >> /usr/lib64 libtesseract_api.la ../ccmain/libtesseract_main.la >> ../textord/libtesseract_textord.la ../wordrec/libtesseract_wordrec.la >> ../classify/libtesseract_classify.la ../dict/libtesseract_dict.la >> ../arch/libtesseract_arch.la ../arch/libtesseract_native.la >> ../lstm/libtesseract_lstm.la ../ccstruct/libtesseract_ccstruct.la >> ../cutil/libtesseract_cutil.la ../viewer/libtesseract_viewer.la >> ../ccutil/libtesseract_ccutil.la ../opencl/libtesseract_opencl.la >> ../arch/libtesseract_avx.la ../arch/libtesseract_avx2.la >> ../arch/libtesseract_sse.la -lpthread >> /usr/bin/grep: /usr/lib64/liblzma.la: No such file or directory >> /usr/bin/sed: can't read /usr/lib64/liblzma.la: No such file or directory >> libtool: error: '/usr/lib64/liblzma.la' is not a valid libtool archive >> Makefile:536: recipe for target 'libtesseract.la' failed >> make[2]: *** [libtesseract.la] Error 1 >> make[2]: Leaving directory '/tmp/SBo/tesseract-4.1.0/src/api' >> Makefile:498: recipe for target 'all-recursive' failed >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory '/tmp/SBo/tesseract-4.1.0' >> Makefile:407: recipe for target 'all' failed >> make: *** [all] Error 2 >> >> >> any help is appreciated > > Works for me under -current and 14.2 (clean buildroot). > > If liblzma.la is not present on your system (it should be there on a > clean 14.2 system) I'm assuming you're on -current. Sounds like you may > have a broken chain of libtool archives (.la files). See the Slackware > Current ChangeLog entry from April 19, 2018. > _______________________________________________ > 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/ > -- Judah Milgram milgram at cgpp.com 301-257-7069 From poprocks at gmail.com Sun Nov 10 22:54:29 2019 From: poprocks at gmail.com (Logan Rathbone) Date: Sun, 10 Nov 2019 17:54:29 -0500 Subject: [Slackbuilds-users] pytesseract In-Reply-To: <7b7ea286-cf9f-7417-27c4-b4f9b4f422a2@cgpp.com> References: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> <20191109185748.GA15078@darkstar.example.net> <7b7ea286-cf9f-7417-27c4-b4f9b4f422a2@cgpp.com> Message-ID: <20191110225429.GA10369@darkstar.example.net> On Sun, Nov 10, 2019 at 03:38:00PM -0500, Judah Milgram wrote: > > > Thanks for upgrading the slackbuild to tesseract 4! > > Related thought: sure would be nice to have pytesseract. Is it already part > of an existing slackbuild? > > If not, I'd be happy to take a stab at it. It doesn't look like pytesseract is part of an existing slackbuild. So I'm sure you could feel free to submit to slackbuilds.org. However, it should be noted that pytesseract is also installable from pip. I'm not sure what (if anything) the SBo policy is on this, but it would seem to me that unless a perl or python package is needed as a dependency for something else, users might be best off installing those packages from CPAN or pip, so as to avoid duplication of effort. From milgram at cgpp.com Mon Nov 11 21:09:49 2019 From: milgram at cgpp.com (Judah Milgram) Date: Mon, 11 Nov 2019 16:09:49 -0500 Subject: [Slackbuilds-users] pytesseract In-Reply-To: <20191110225429.GA10369@darkstar.example.net> References: <612722c5-75bf-13c0-111a-795304a2c97a@gmail.com> <20191109185748.GA15078@darkstar.example.net> <7b7ea286-cf9f-7417-27c4-b4f9b4f422a2@cgpp.com> <20191110225429.GA10369@darkstar.example.net> Message-ID: I like that solution and it works just fine. And a good point - it seems to me there are many slackbuilds that could just be pip installations. I wonder how that fits into the Scheme of Things. On 11/10/19 5:54 PM, Logan Rathbone wrote: > On Sun, Nov 10, 2019 at 03:38:00PM -0500, Judah Milgram wrote: >> >> >> Thanks for upgrading the slackbuild to tesseract 4! >> >> Related thought: sure would be nice to have pytesseract. Is it already part >> of an existing slackbuild? >> >> If not, I'd be happy to take a stab at it. > > It doesn't look like pytesseract is part of an existing slackbuild. So > I'm sure you could feel free to submit to slackbuilds.org. > > However, it should be noted that pytesseract is also installable from > pip. I'm not sure what (if anything) the SBo policy is on this, but it > would seem to me that unless a perl or python package is needed as a > dependency for something else, users might be best off installing those > packages from CPAN or pip, so as to avoid duplication of effort. > _______________________________________________ > 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/ > -- Judah Milgram milgram at cgpp.com 301-257-7069 From slackbuilds at jaxartes.net Mon Nov 11 22:31:58 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Mon, 11 Nov 2019 14:31:58 -0800 Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj Message-ID: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> In 2018, the main opensource geospatial libraries - GDAL, proj, libgeotiff, libspatialite - started an effort to make core changes that could only be done simultaneously (https://gdalbarn.com/). Slowly the software that uses these libraries has been adopting that new tool chain. Slackware, however, is currently still on the old set of libraries, but I've finally sat down and worked through what will happen if SlackBuilds goes through the migration and I'd like to get feedback from maintainers and users on whether we should. Here are the core upgrades for 14.2 that need to be coordinated: gis/gdal 3.0.2 gis/proj 6.2.1 gis/geos 3.8.0 gis/libgeotiff 1.5.1 gis/libspatialite 4.3.0 Here are applications or other scripts that we get to upgrade. With a few exceptions we are no longer able to upgrade applications in this list without doing the above core library upgrades first: gis/qgis 3.10.0 gis/postgis 3.0.0 gis/Fiona 1.8.9 gis/rasterio 1.1.0 gis/grass 7.8.0 gis/ossim 2.10.0 gis/OTB 7.0.0 gis/pdal 2.0.1 gis/pyproj 2.4.1 academic/Shark 4.0.0 There are a few regressions or scripts which will need to be removed (or possibly patched from dev branches): gis/OTB will lose Python support gis/qlandkartegt no longer builds (but it's deprecated in favour of qmapshack anyhow) gis/osgEarth no longer builds but upcoming version 3.0 will work from what I can tell gis/libLAS no longer builds but isn't required by any projects and looks to be deprecated in favour of PDAL gis/merkaartor no longer builds but I think there might be commits in master that should make it work gis/pyspatialite no longer works but it is not needed by newer versions of QGIS anymore misc/zyGrib not building because of new proj I've also tested the other scripts that depend directly on the core library upgrades, all of which are working. Are the regressions that I have noted enough to hold back on going ahead with the upgrades? What about any indirect or optional dependencies? Feel free to use this branch if you want to do any testing: https:// git.slackbuilds.org/slackbuilds/log/?h=user/bosth/gdalbarn. Ben From matteo.bernardini at gmail.com Tue Nov 12 11:51:19 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 12 Nov 2019 12:51:19 +0100 Subject: [Slackbuilds-users] Fwd: [Slackbuilds-devel] postgresql In-Reply-To: <3d92dcaa-2ccc-a26d-31d9-5369ee30b06c@haproxy.com> References: <859c0c22-046e-440c-bc49-10cea32f385c@slackbuilds.org> <3d92dcaa-2ccc-a26d-31d9-5369ee30b06c@haproxy.com> Message-ID: ---------- Forwarded message --------- Da: Adis Nezirovic Date: mar 12 nov 2019 alle ore 10:09 Subject: Re: [Slackbuilds-devel] postgresql To: Matteo Bernardini Cc: SBo Admin List On 11/11/19 5:16 PM, Matteo Bernardini wrote: > Hi Adis, > > > it seems your email address registered at SBo is not working anymore and > people are asking about postgresql: are you still interested in > maintaining it? > > > Matteo > Hey Matteo, Thanks for reaching out, the issue with email/domain is solved now. As for PostgreSQL, I did really lousy job lately, real life interferes :-( I guess you can announce on the mailing list that the package is up for grabs, someone would probably volunteer. Best regards, -- Adis Nezirovic From mab974 at gmail.com Tue Nov 12 17:41:00 2019 From: mab974 at gmail.com (mab974) Date: Tue, 12 Nov 2019 21:41:00 +0400 Subject: [Slackbuilds-users] Fwd: [Slackbuilds-devel] postgresql In-Reply-To: References: <859c0c22-046e-440c-bc49-10cea32f385c@slackbuilds.org> <3d92dcaa-2ccc-a26d-31d9-5369ee30b06c@haproxy.com> Message-ID: <20191112214100.c113d1f7be3ee2feceb08b60@gmail.com> Selon Matteo Bernardini : > ---------- Forwarded message --------- > Da: Adis Nezirovic > Date: mar 12 nov 2019 alle ore 10:09 > Subject: Re: [Slackbuilds-devel] postgresql > To: Matteo Bernardini > Cc: SBo Admin List > > On 11/11/19 5:16 PM, Matteo Bernardini wrote: > > Hi Adis, > > > > > > it seems your email address registered at SBo is not working anymore and > > people are asking about postgresql: are you still interested in > > maintaining it? > > > > > > Matteo > > > > Hey Matteo, > > Thanks for reaching out, the issue with email/domain is solved now. > > As for PostgreSQL, I did really lousy job lately, real life interferes :-( > > I guess you can announce on the mailing list that the package is up for > grabs, someone would probably volunteer. > > Best regards, > -- > Adis Nezirovic > _______________________________________________ > 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/ > I?ve done some work on it, and I'd like to take it over if nobody absolutely wants it. Maybe temporarily if Adis wants to pick it up later when real life will allow it again. For upgrading, it might be desirable to differentiate between the major supported versions: 10, 11, ... and propose postgresql10, postgresql11, ....as in other distributions. What do you think of that ? Regards, Michel -*- mab974 From yakizarns1 at gmail.com Tue Nov 12 22:14:43 2019 From: yakizarns1 at gmail.com (Dionysis Ntreou) Date: Tue, 12 Nov 2019 22:14:43 +0000 Subject: [Slackbuilds-users] Fwd: [Slackbuilds-devel] postgresql In-Reply-To: <20191112214100.c113d1f7be3ee2feceb08b60@gmail.com> References: <859c0c22-046e-440c-bc49-10cea32f385c@slackbuilds.org> <3d92dcaa-2ccc-a26d-31d9-5369ee30b06c@haproxy.com> <20191112214100.c113d1f7be3ee2feceb08b60@gmail.com> Message-ID: I would really love it Michael As i am using it quite frequently, but It is fair you take it since you called it in first i suppose Kind Regards Dionysis On Tue, Nov 12, 2019 at 5:41 PM mab974 wrote: > Selon Matteo Bernardini : > > ---------- Forwarded message --------- > > Da: Adis Nezirovic > > Date: mar 12 nov 2019 alle ore 10:09 > > Subject: Re: [Slackbuilds-devel] postgresql > > To: Matteo Bernardini > > Cc: SBo Admin List > > > > On 11/11/19 5:16 PM, Matteo Bernardini wrote: > > > Hi Adis, > > > > > > > > > it seems your email address registered at SBo is not working anymore > and > > > people are asking about postgresql: are you still interested in > > > maintaining it? > > > > > > > > > Matteo > > > > > > > Hey Matteo, > > > > Thanks for reaching out, the issue with email/domain is solved now. > > > > As for PostgreSQL, I did really lousy job lately, real life interferes > :-( > > > > I guess you can announce on the mailing list that the package is up for > > grabs, someone would probably volunteer. > > > > Best regards, > > -- > > Adis Nezirovic > > _______________________________________________ > > 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/ > > > > I?ve done some work on it, and I'd like to take it over if nobody > absolutely wants it. > Maybe temporarily if Adis wants to pick it up later when real life will > allow it again. > > For upgrading, it might be desirable to > differentiate between the major supported versions: 10, 11, ... and > propose postgresql10, postgresql11, ....as in other distributions. > What do you think of that ? > > Regards, > Michel > > -*- > mab974 > _______________________________________________ > 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 peter.dambier at piraten-fraktion-bergstrasse.de Tue Nov 12 16:50:18 2019 From: peter.dambier at piraten-fraktion-bergstrasse.de (Peter Dambier) Date: Tue, 12 Nov 2019 17:50:18 +0100 Subject: [Slackbuilds-users] libc++-3.8.6 on slackware current xlocale.h not found. In-Reply-To: References: <4d1664f7-4792-a5ae-b994-858122a6f25d@peter-dambier.de> Message-ID: <20191112175018.2860fcf2.peter.dambier@piraten-fraktion-bergstrasse.de> On Sun, 10 Nov 2019 07:36:55 +0100 Matteo Bernardini wrote: > Il giorno sab 9 nov 2019 alle ore 23:52 Peter Dambier > ha scritto: > > > > Hi, I am Peter and I am new to this list. > > > > Building libc++ aborted with an "xlocale.h" not found error. > > > > Digging into the subject I found this xlocale.h actually is > > a subset of locale.h and should never have escaped > > into the wild - so now is the time to remove it. > > > > As it is not needed, it might actually be empty, why not > > > > touch /usr/include/xlocale.h > > > > Package libc++-3.8.6-i586-1_SBo.tgz build without any > > more trouble. > > > > Of course this is not the right way to do it. But it may > > save somebodys day and you can always delete > > that xlocale.h immediately after building. > > > > Beware locate finds lots of xlocale.h: > > > > /usr/include/c++/v1/support/fuchsia/xlocale.h > > /usr/include/c++/v1/support/ibm/xlocale.h > > /usr/include/c++/v1/support/musl/xlocale.h > > /usr/include/c++/v1/support/newlib/xlocale.h > > /usr/include/c++/v1/support/solaris/xlocale.h > > /usr/include/wx-3.0/wx/xlocale.h > > > > but this one used to belong to glibc and lived in > > /usr/include. > > > > Kind regards > > Peter > > this happens to you because xlocale.h has been removed from glibc > since version 2.26 so it's not available anymore in the version > shipped by current. > there are a few ways to workaround this but you shouldn't actually > need any: you don't install a separate libc++ in current because is > now provided as part of the llvm package. > > Matteo Thanks a lot, Matteo. I had to install llvm, so no separate libc++. And I have discovered there is a veles package with less headachses. Cheers Peter From slackbuilds at schoepfer.info Wed Nov 13 04:13:33 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Wed, 13 Nov 2019 05:13:33 +0100 Subject: [Slackbuilds-users] Fwd: Re: klavaro on SBo In-Reply-To: References: Message-ID: <9ef0a302ebe0612b6d427905824ad9ac@schoepfer.info> Hi, i'm taking over klavaro. Johannes -------- Original Message -------- Subject: Re: klavaro on SBo Date: 2019-11-11 10:40 From: Thibaut Notteboom To: Franzen Hi Johannes, I actually forget to update klavaro since I did not use it anymore. You can take it over. Thibaut Le dim. 10 nov. 2019 ? 15:16, Franzen a ?crit : > Hi Thibaut > > as you are listed as maintainer for > https://slackbuilds.org/repository/14.2/academic/klavaro/ , > but haven't contributed for about 4 years, may i take over? > > Johannes From mab974 at gmail.com Wed Nov 13 05:39:36 2019 From: mab974 at gmail.com (mab974) Date: Wed, 13 Nov 2019 09:39:36 +0400 Subject: [Slackbuilds-users] Fwd: [Slackbuilds-devel] postgresql In-Reply-To: References: <859c0c22-046e-440c-bc49-10cea32f385c@slackbuilds.org> <3d92dcaa-2ccc-a26d-31d9-5369ee30b06c@haproxy.com> <20191112214100.c113d1f7be3ee2feceb08b60@gmail.com> Message-ID: <20191113093936.eebf09cc6efe602813971349@gmail.com> Okay, Dionysis, you can take it. As long as it moves. Regards, Michel Selon Dionysis Ntreou : > I would really love it Michael > As i am using it quite frequently, but It is fair you take it since you > called it in first i suppose > > Kind Regards > Dionysis > > On Tue, Nov 12, 2019 at 5:41 PM mab974 wrote: > > > Selon Matteo Bernardini : > > > ---------- Forwarded message --------- > > > Da: Adis Nezirovic > > > Date: mar 12 nov 2019 alle ore 10:09 > > > Subject: Re: [Slackbuilds-devel] postgresql > > > To: Matteo Bernardini > > > Cc: SBo Admin List > > > > > > On 11/11/19 5:16 PM, Matteo Bernardini wrote: > > > > Hi Adis, > > > > > > > > > > > > it seems your email address registered at SBo is not working anymore > > and > > > > people are asking about postgresql: are you still interested in > > > > maintaining it? > > > > > > > > > > > > Matteo > > > > > > > > > > Hey Matteo, > > > > > > Thanks for reaching out, the issue with email/domain is solved now. > > > > > > As for PostgreSQL, I did really lousy job lately, real life interferes > > :-( > > > > > > I guess you can announce on the mailing list that the package is up for > > > grabs, someone would probably volunteer. > > > > > > Best regards, > > > -- > > > Adis Nezirovic > > > _______________________________________________ > > > 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/ > > > > > > > I?ve done some work on it, and I'd like to take it over if nobody > > absolutely wants it. > > Maybe temporarily if Adis wants to pick it up later when real life will > > allow it again. > > > > For upgrading, it might be desirable to > > differentiate between the major supported versions: 10, 11, ... and > > propose postgresql10, postgresql11, ....as in other distributions. > > What do you think of that ? > > > > Regards, > > Michel > > > > -*- > > mab974 > > _______________________________________________ > > 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/ > > > > -*- mab974 From willysr at slackbuilds.org Thu Nov 14 00:19:58 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 14 Nov 2019 07:19:58 +0700 Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> Message-ID: <6516b38f-e5c5-858f-6333-f54c8783e31a@slackbuilds.org> On 11/12/19 5:31 AM, Benjamin Trigona-Harany wrote: > In 2018, the main opensource geospatial libraries - GDAL, proj, libgeotiff, > libspatialite - started an effort to make core changes that could only be done > simultaneously (https://gdalbarn.com/). Slowly the software that uses these > libraries has been adopting that new tool chain. Slackware, however, is > currently still on the old set of libraries, but I've finally sat down and > worked through what will happen if SlackBuilds goes through the migration and > I'd like to get feedback from maintainers and users on whether we should. > > Here are the core upgrades for 14.2 that need to be coordinated: > gis/gdal 3.0.2 > gis/proj 6.2.1 > gis/geos 3.8.0 > gis/libgeotiff 1.5.1 > gis/libspatialite 4.3.0 > > Here are applications or other scripts that we get to upgrade. With a few > exceptions we are no longer able to upgrade applications in this list without > doing the above core library upgrades first: > gis/qgis 3.10.0 > gis/postgis 3.0.0 > gis/Fiona 1.8.9 > gis/rasterio 1.1.0 > gis/grass 7.8.0 > gis/ossim 2.10.0 > gis/OTB 7.0.0 > gis/pdal 2.0.1 > gis/pyproj 2.4.1 > academic/Shark 4.0.0 > > There are a few regressions or scripts which will need to be removed (or > possibly patched from dev branches): > gis/OTB will lose Python support > gis/qlandkartegt no longer builds (but it's deprecated in favour of qmapshack > anyhow) > gis/osgEarth no longer builds but upcoming version 3.0 will work from what I > can tell > gis/libLAS no longer builds but isn't required by any projects and looks to be > deprecated in favour of PDAL > gis/merkaartor no longer builds but I think there might be commits in master > that should make it work > gis/pyspatialite no longer works but it is not needed by newer versions of > QGIS anymore > misc/zyGrib not building because of new proj > > I've also tested the other scripts that depend directly on the core library > upgrades, all of which are working. > > Are the regressions that I have noted enough to hold back on going ahead with > the upgrades? What about any indirect or optional dependencies? > > Feel free to use this branch if you want to do any testing: https:// > git.slackbuilds.org/slackbuilds/log/?h=user/bosth/gdalbarn. Hi Ben David has been doing some work on GDAL in the past which is placed on a separate branch: gdal-review Can you have a look on it as well? See if it can be cherry-picked? -- 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 Thu Nov 14 01:18:47 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Wed, 13 Nov 2019 17:18:47 -0800 Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: <6516b38f-e5c5-858f-6333-f54c8783e31a@slackbuilds.org> References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> <6516b38f-e5c5-858f-6333-f54c8783e31a@slackbuilds.org> Message-ID: On 2019-11-13 4:19 p.m., Willy Sudiarto Raharjo wrote: > On 11/12/19 5:31 AM, Benjamin Trigona-Harany wrote: > > Hi Ben > > David has been doing some work on GDAL in the past which is placed on a > separate branch: gdal-review > > Can you have a look on it as well? See if it can be cherry-picked? I actually started with David's branch but ended up redoing it from scratch since he was using an older proj (5.x) and GDAL (2.3), and the main changes occurred with those two version bumps. Best, Ben From willysr at slackbuilds.org Thu Nov 14 02:54:35 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 14 Nov 2019 09:54:35 +0700 Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> <6516b38f-e5c5-858f-6333-f54c8783e31a@slackbuilds.org> Message-ID: <86ab5736-d9ea-cbe8-9ddc-31ba355b797e@slackbuilds.org> > I actually started with David's branch but ended up redoing it from > scratch since he was using an older proj (5.x) and GDAL (2.3), and the > main changes occurred with those two version bumps. Oh if your branch has newer version, i will probably delete the older branch of David. What do you think? -- 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 Thu Nov 14 03:01:55 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Wed, 13 Nov 2019 19:01:55 -0800 Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: <86ab5736-d9ea-cbe8-9ddc-31ba355b797e@slackbuilds.org> References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> <86ab5736-d9ea-cbe8-9ddc-31ba355b797e@slackbuilds.org> Message-ID: <2131055.Z3JN27x4G4@wintermute.sprawl.net> On Wednesday, 13 November 2019 18:54:35 PST Willy Sudiarto Raharjo wrote: > > I actually started with David's branch but ended up redoing it from > > scratch since he was using an older proj (5.x) and GDAL (2.3), and the > > main changes occurred with those two version bumps. > > Oh if your branch has newer version, i will probably delete the older > branch of David. What do you think? Let's keep it around until all the upgrades are done ... just in case :) From slackbuilds at schoepfer.info Thu Nov 14 09:11:27 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 14 Nov 2019 10:11:27 +0100 Subject: [Slackbuilds-users] seq24 and amSynth In-Reply-To: <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> References: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> Message-ID: Am 09.11.19 um 01:56 schrieb Willy Sudiarto Raharjo: >> i'd like to take over and update seq24 and amSynth. I mailed to the >> maintainers a few days ago(see blow), but as these both did not >> contribute for aabout 8 years, is it ok to just grab the scripts and do >> the work? > > Yes Then I'd also take a2jmidid, no sign from the maintainer since 8years. https://git.slackbuilds.org/slackbuilds/log/multimedia/a2jmidid Johannes From matteo.bernardini at gmail.com Thu Nov 14 09:39:44 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 14 Nov 2019 09:39:44 +0000 Subject: [Slackbuilds-users] seq24 and amSynth In-Reply-To: References: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> Message-ID: Maybe just give a ping to korgie as I think he is still active... Il gio 14 nov 2019, 09:11 Franzen ha scritto: > Am 09.11.19 um 01:56 schrieb Willy Sudiarto Raharjo: > >> i'd like to take over and update seq24 and amSynth. I mailed to the > >> maintainers a few days ago(see blow), but as these both did not > >> contribute for aabout 8 years, is it ok to just grab the scripts and do > >> the work? > > > > Yes > > Then I'd also take a2jmidid, no sign from the maintainer since 8years. > https://git.slackbuilds.org/slackbuilds/log/multimedia/a2jmidid > > Johannes > _______________________________________________ > 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 slackbuilds at schoepfer.info Thu Nov 14 09:48:42 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 14 Nov 2019 10:48:42 +0100 Subject: [Slackbuilds-users] seq24 and amSynth In-Reply-To: References: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> Message-ID: Hi Michales, i'd like to take over a2jmidid as it seems it doesn't get updates since years, and doesn't support jack2 in the current state. Is that ok for you? Johannes Am 14.11.19 um 10:39 schrieb Matteo Bernardini: > Maybe just give a ping to korgie as I think he is still active... > > Il gio 14 nov 2019, 09:11 Franzen > ha scritto: > > Am 09.11.19 um 01:56 schrieb Willy Sudiarto Raharjo: > >> i'd like to take over and update seq24 and amSynth. I mailed to the > >> maintainers a few days ago(see blow), but as these both did not > >> contribute for aabout 8 years, is it ok to just grab the scripts > and do > >> the work? > > > > Yes > > Then I'd also take a2jmidid, no sign from the maintainer since 8years. > https://git.slackbuilds.org/slackbuilds/log/multimedia/a2jmidid > > Johannes > _______________________________________________ > 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 korgie at gmail.com Thu Nov 14 20:55:15 2019 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Thu, 14 Nov 2019 22:55:15 +0200 Subject: [Slackbuilds-users] seq24 and amSynth In-Reply-To: References: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> Message-ID: 14 ??? 2019, 11:48 ??, ? ??????? ?Franzen ? ??????: > Hi Michales, > > i'd like to take over a2jmidid as it seems it doesn't get updates since years, and doesn't support jack2 in the current state. > Is that ok for you? It?s yours. I don?t use jack2 but jack1 (in fact many times I prefer alsa) Those last years I am too busy. I am happy that someone likes a2j. > Johannes > >> Am 14.11.19 um 10:39 schrieb Matteo Bernardini: >> Maybe just give a ping to korgie as I think he is still active... >> Il gio 14 nov 2019, 09:11 Franzen > ha scritto: >> Am 09.11.19 um 01:56 schrieb Willy Sudiarto Raharjo: >> >> i'd like to take over and update seq24 and amSynth. I mailed to the >> >> maintainers a few days ago(see blow), but as these both did not >> >> contribute for aabout 8 years, is it ok to just grab the scripts >> and do >> >> the work? >> > >> > Yes >> Then I'd also take a2jmidid, no sign from the maintainer since 8years. >> https://git.slackbuilds.org/slackbuilds/log/multimedia/a2jmidid >> Johannes >> _______________________________________________ >> 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 dickson.tim at googlemail.com Thu Nov 14 23:48:46 2019 From: dickson.tim at googlemail.com (Tim Dickson) Date: Thu, 14 Nov 2019 23:48:46 +0000 Subject: [Slackbuilds-users] what is the view on slackbuilds for none-free stuff Message-ID: <5d4a287b-a0c8-3f4a-7b8c-d0b173bb2da7@googlemail.com> I have a slackbuild for a game of which the sourc ecode is gpl and is on github, but the game data has to be purchased. As such the game homepage has a link to itch.io to buy the game which provides a personalised link fora gz of the source including the extra game data, as well as a pre-compiled binary.? I can include an md5sum for this source file, but obviously can't provide a direct download link. all you have to do is buy it (?1 minimum) and put the source tar.gz which includes the game data in the same folder as the build script as usual. Is that eligible for slackbuilds.org ? obviously to respect the author's data, resulting package would have to be for personal use. regards, Tim From fernando.lopezjr at gmail.com Fri Nov 15 00:51:11 2019 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 14 Nov 2019 17:51:11 -0700 Subject: [Slackbuilds-users] what is the view on slackbuilds for none-free stuff In-Reply-To: <5d4a287b-a0c8-3f4a-7b8c-d0b173bb2da7@googlemail.com> References: <5d4a287b-a0c8-3f4a-7b8c-d0b173bb2da7@googlemail.com> Message-ID: I say just create the program executables/libraries/etc... leave a comment on the slackbuild that you need the actual game data to play it. On Thu, Nov 14, 2019 at 4:49 PM Tim Dickson via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > I have a slackbuild for a game of which the sourc ecode is gpl and is on > github, but the game data has to be purchased. As such the game homepage > has a link to itch.io to buy the game which provides a personalised link > fora gz of the source including the extra game data, as well as a > pre-compiled binary. I can include an md5sum for this source file, but > obviously can't provide a direct download link. > all you have to do is buy it (?1 minimum) and put the source tar.gz > which includes the game data in the same folder as the build script as > usual. > Is that eligible for slackbuilds.org ? obviously to respect the author's > data, resulting package would have to be for personal use. > regards, Tim > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Fri Nov 15 03:29:53 2019 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Thu, 14 Nov 2019 20:29:53 -0700 Subject: [Slackbuilds-users] what is the view on slackbuilds for none-free stuff In-Reply-To: <5d4a287b-a0c8-3f4a-7b8c-d0b173bb2da7@googlemail.com> References: <5d4a287b-a0c8-3f4a-7b8c-d0b173bb2da7@googlemail.com> Message-ID: On Thu, Nov 14, 2019, 4:49 PM Tim Dickson via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > I have a slackbuild for a game of which the sourc ecode is gpl and is on > github, but the game data has to be purchased. As such the game homepage > has a link to itch.io to buy the game which provides a personalised link > fora gz of the source including the extra game data, as well as a > pre-compiled binary. I can include an md5sum for this source file, but > obviously can't provide a direct download link. > all you have to do is buy it (?1 minimum) and put the source tar.gz > which includes the game data in the same folder as the build script as > usual. > Is that eligible for slackbuilds.org ? obviously to respect the author's > data, resulting package would have to be for personal use. > regards, Tim > It shouldn't be an issue since most (if not all) of the Doom games on SBo require the Doom wad file(s). Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at schoepfer.info Fri Nov 15 16:04:18 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 15 Nov 2019 17:04:18 +0100 Subject: [Slackbuilds-users] seq24 and amSynth In-Reply-To: References: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> Message-ID: >> Hi Michales, >> >> i'd like to take over a2jmidid as it seems it doesn't get updates >> since years, and doesn't support jack2 in the current state. >> Is that ok for you? > > It?s yours. > > I don?t use jack2 but jack1 (in fact many times I prefer alsa) > > Those last years I am too busy. I am happy that someone likes a2j. Thanks :-) While we are on it, may i take also linuxsampler and libgig? From korgie at gmail.com Fri Nov 15 18:09:34 2019 From: korgie at gmail.com (=?utf-8?B?zpzOuc+HzqzOu863z4IgzpzOuc+HzrHOu86/z43OtM63z4I=?=) Date: Fri, 15 Nov 2019 20:09:34 +0200 Subject: [Slackbuilds-users] seq24 and amSynth In-Reply-To: References: <1ec28427-01b8-91f6-32d1-05d4f8a30364@schoepfer.info> <21187ac8-7d2b-2798-564c-b46528587083@slackbuilds.org> Message-ID: <7A6E9536-A2F0-4C31-A331-A691A336AF54@gmail.com> 15 ??? 2019, 6:04 ??, ? ??????? ?Franzen ? ??????: > > > While we are on it, may i take also linuxsampler and libgig? Yes. Twice the pleasure :-) From alik at ejik.org Sat Nov 16 01:27:29 2019 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 16 Nov 2019 04:27:29 +0300 Subject: [Slackbuilds-users] Vivaldi Message-ID: <36e2ba92-c884-4fa1-96a7-726c60361f11@www.fastmail.com> Hello, as I switched from Vivaldi (to qutebrowser) since some time, I'd like to invite someone to take it. Best regards, Alexander From leoc at gmx.com Sat Nov 16 15:35:23 2019 From: leoc at gmx.com (Leonardo Citrolo) Date: Sat, 16 Nov 2019 16:35:23 +0100 Subject: [Slackbuilds-users] Duplicated script removal request Message-ID: <20191116163523.2ada80b7ec1167c442f1bc50@gmx.com> Hi, someone noticed and reported to me that my development/python-docopt script is actually a duplication of an older one, namely python/docopt; I suppose that when I wrote and submitted mine I didn't check the SBo database properly first. Please remove mine and fix the .info file of pyqt-distutils (another script of mine, which currently depends on python-docopt) accordingly. Thanks Leo From willysr at slackbuilds.org Sat Nov 16 17:56:58 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Nov 2019 00:56:58 +0700 Subject: [Slackbuilds-users] Duplicated script removal request In-Reply-To: <20191116163523.2ada80b7ec1167c442f1bc50@gmx.com> References: <20191116163523.2ada80b7ec1167c442f1bc50@gmx.com> Message-ID: > someone noticed and reported to me that my development/python-docopt > script is actually a duplication of an older one, namely python/docopt; > I suppose that when I wrote and submitted mine I didn't check the SBo > database properly first. > Please remove mine and fix the .info file of pyqt-distutils (another > script of mine, which currently depends on python-docopt) accordingly. Done -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Nov 16 18:34:48 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Nov 2019 01:34:48 +0700 Subject: [Slackbuilds-users] Updates - 20191116.1 Message-ID: Sat Nov 16 18:23:50 UTC 2019 academic/gwyddion: Updated for version 2.55. academic/klavaro: Updated for version 3.03. audio/a2jmidid: Updated for version 1.3a, moved from multimedia. audio/amSynth: Updated for version 1.9.0. audio/linuxsampler: Updated for v 2.1.1, moved from multimedia. audio/seq24: Updated for version 0.9.3. development/STM32CubeIDE: Added (C/C++ development platform). development/check: Updated for version 0.13.0. development/dkms: Updated for version 2.8.1 development/hopper: Updated for version 4.5.18. development/jdk: Updated for version 8u231. development/jupyter_client: Updated for version 5.3.4. development/lepton-eda: Added (Lepton Electronic Design Automation). development/pycharm: Updated for version 2019.2.4. development/pyqt-distutils: Update DEP. development/python-docopt: Removed (duplicate). development/tiled: updated for version 1.3.0 development/vscode-bin: Updated for version 1.40.1. games/stockfish: Update EMAIL address. games/waterCloset: Added (An SDL2 based puzzle platform game). gis/GMT: Updated for version 6.0.0. gis/gpxsee: Updated for version 7.17. gis/openorienteering-mapper: Updated for version 0.9.0. gis/whitebox-tools: Updated for version 1.0.2. graphics/converseen: Updated for version 0.9.8.0. graphics/vuescan: Updated for version 9.7.08. graphics/white_dune: Updated for version 1.576. libraries/QScintilla-qt5: Added (Qt5 port of Scintilla C++ editor). libraries/dcmtk: Update for version 3.6.5 libraries/libcoap: Updated for version 4.2.1. libraries/libgig: Updated for version 4.2.0. libraries/live555: Updated for version 2019.11.11 libraries/qwt-qt5: Added (Qt5 widgets for technical applications). libraries/xforms: Fix typo multimedia/plexmediaserver: Updated for v 1.18.1.2019_c186313fe. network/3proxy: Updated for version 0.8.13. network/anydesk: Updated for version 5.4.1. network/dmitry: Updated for version 1.3a. network/dropbox: Updated for version 85.4.155. network/onedrive: Updated for version 2.3.11. network/prosody-mod-http-upload: Updated for version hg3713. network/remmina: Update script. network/zoom-linux: Updated for version 3.0.317369.1110. office/LibreOffice: Updated for version 6.2.8.2 office/gnucash-docs: Updated for version 3.6. office/gnucash: Updated for version 3.6. office/keepassxc: Updated for version 2.5.1. office/pdfstudio: Updated for version 2019.2.0. office/pdfstudioviewer: Updated for version 2019.2.0. office/xournalpp: Updated for version 1.0.16. python/Pyro4: Updated for version 4.77. python/hupper: updated for version 1.9.1 python/pycryptodome: Updated for version 3.9.2. python/python-requests: Update HOMEPAGE. python/python-serpent: Updated for version 1.28. python/python3-pylint: Updated for version 2.4.4. python/regex: Updated for version 2019.08.19. python/thonny: Updated for version 3.2.3. ruby/rubygem-ruumba: Updated for version 0.1.14. system/Iosevka: Updated for version 2.3.3. system/atop: Updated for version 2.5.0. system/capstone: Updated for version 4.0.1. system/collectd: Updated for version 5.10.0. system/epson-inkjet-printer-escpr: Updated for version 1.7.6. system/isdct: Updated for version 3.0.22. system/kbfs: Updated for version 5.0.0_20191114203213. system/keybase: Updated for version 5.0.0. system/mpich: Updated for version 3.3.2 system/postgresql: Updated for version 10.10. system/system76-io-dkms: Added (DKMS module). system/system76-power: Added (utility for managing graphics/power) system/telegraf: Updated for version 1.12.5. system/tpe-kmod: Updated for version 2.0.4. +--------------------------+ -- 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 lramos.prof at yahoo.com.br Sun Nov 17 01:21:44 2019 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sat, 16 Nov 2019 22:21:44 -0300 Subject: [Slackbuilds-users] Updates - 20191116.1 In-Reply-To: References: Message-ID: <20191117012143.GB20668@giustizia.org> Hi, please take a look at the download URL from capstone in the info file. The version in the file name is correct (4.0.1), but not in the rest of the path (3.0.5). Unfortunately, that wrong URL resolves to the old source file and the broken may pass undetected. Many thanks, Luiz Carlos Ramos Sao Paulo - Brazil lramos dot prof at yahoo dot com dot br On Sun, Nov 17, 2019 at 01:34:48AM +0700, Willy Sudiarto Raharjo wrote: > Sat Nov 16 18:23:50 UTC 2019 > academic/gwyddion: Updated for version 2.55. > academic/klavaro: Updated for version 3.03. > audio/a2jmidid: Updated for version 1.3a, moved from multimedia. > audio/amSynth: Updated for version 1.9.0. > audio/linuxsampler: Updated for v 2.1.1, moved from multimedia. > audio/seq24: Updated for version 0.9.3. > development/STM32CubeIDE: Added (C/C++ development platform). > development/check: Updated for version 0.13.0. > development/dkms: Updated for version 2.8.1 > development/hopper: Updated for version 4.5.18. > development/jdk: Updated for version 8u231. > development/jupyter_client: Updated for version 5.3.4. > development/lepton-eda: Added (Lepton Electronic Design Automation). > development/pycharm: Updated for version 2019.2.4. > development/pyqt-distutils: Update DEP. > development/python-docopt: Removed (duplicate). > development/tiled: updated for version 1.3.0 > development/vscode-bin: Updated for version 1.40.1. > games/stockfish: Update EMAIL address. > games/waterCloset: Added (An SDL2 based puzzle platform game). > gis/GMT: Updated for version 6.0.0. > gis/gpxsee: Updated for version 7.17. > gis/openorienteering-mapper: Updated for version 0.9.0. > gis/whitebox-tools: Updated for version 1.0.2. > graphics/converseen: Updated for version 0.9.8.0. > graphics/vuescan: Updated for version 9.7.08. > graphics/white_dune: Updated for version 1.576. > libraries/QScintilla-qt5: Added (Qt5 port of Scintilla C++ editor). > libraries/dcmtk: Update for version 3.6.5 > libraries/libcoap: Updated for version 4.2.1. > libraries/libgig: Updated for version 4.2.0. > libraries/live555: Updated for version 2019.11.11 > libraries/qwt-qt5: Added (Qt5 widgets for technical applications). > libraries/xforms: Fix typo > multimedia/plexmediaserver: Updated for v 1.18.1.2019_c186313fe. > network/3proxy: Updated for version 0.8.13. > network/anydesk: Updated for version 5.4.1. > network/dmitry: Updated for version 1.3a. > network/dropbox: Updated for version 85.4.155. > network/onedrive: Updated for version 2.3.11. > network/prosody-mod-http-upload: Updated for version hg3713. > network/remmina: Update script. > network/zoom-linux: Updated for version 3.0.317369.1110. > office/LibreOffice: Updated for version 6.2.8.2 > office/gnucash-docs: Updated for version 3.6. > office/gnucash: Updated for version 3.6. > office/keepassxc: Updated for version 2.5.1. > office/pdfstudio: Updated for version 2019.2.0. > office/pdfstudioviewer: Updated for version 2019.2.0. > office/xournalpp: Updated for version 1.0.16. > python/Pyro4: Updated for version 4.77. > python/hupper: updated for version 1.9.1 > python/pycryptodome: Updated for version 3.9.2. > python/python-requests: Update HOMEPAGE. > python/python-serpent: Updated for version 1.28. > python/python3-pylint: Updated for version 2.4.4. > python/regex: Updated for version 2019.08.19. > python/thonny: Updated for version 3.2.3. > ruby/rubygem-ruumba: Updated for version 0.1.14. > system/Iosevka: Updated for version 2.3.3. > system/atop: Updated for version 2.5.0. > system/capstone: Updated for version 4.0.1. > system/collectd: Updated for version 5.10.0. > system/epson-inkjet-printer-escpr: Updated for version 1.7.6. > system/isdct: Updated for version 3.0.22. > system/kbfs: Updated for version 5.0.0_20191114203213. > system/keybase: Updated for version 5.0.0. > system/mpich: Updated for version 3.3.2 > system/postgresql: Updated for version 10.10. > system/system76-io-dkms: Added (DKMS module). > system/system76-power: Added (utility for managing graphics/power) > system/telegraf: Updated for version 1.12.5. > system/tpe-kmod: Updated for version 2.0.4. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From fernando.lopezjr at gmail.com Sun Nov 17 01:26:52 2019 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sat, 16 Nov 2019 18:26:52 -0700 Subject: [Slackbuilds-users] Updates - 20191116.1 In-Reply-To: <20191117012143.GB20668@giustizia.org> References: <20191117012143.GB20668@giustizia.org> Message-ID: thank you so much for your report. willy can you fix it? On Sat, Nov 16, 2019 at 6:20 PM Luiz Carlos Ramos via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > Hi, > > please take a look at the download URL from capstone in the info file. > The version in the file name is correct (4.0.1), but not in the rest of > the path (3.0.5). > > Unfortunately, that wrong URL resolves to the old source file and the > broken may pass undetected. > > Many thanks, > > Luiz Carlos Ramos > Sao Paulo - Brazil > lramos dot prof at yahoo dot com dot br > > > On Sun, Nov 17, 2019 at 01:34:48AM +0700, Willy Sudiarto Raharjo wrote: > > Sat Nov 16 18:23:50 UTC 2019 > > academic/gwyddion: Updated for version 2.55. > > academic/klavaro: Updated for version 3.03. > > audio/a2jmidid: Updated for version 1.3a, moved from multimedia. > > audio/amSynth: Updated for version 1.9.0. > > audio/linuxsampler: Updated for v 2.1.1, moved from multimedia. > > audio/seq24: Updated for version 0.9.3. > > development/STM32CubeIDE: Added (C/C++ development platform). > > development/check: Updated for version 0.13.0. > > development/dkms: Updated for version 2.8.1 > > development/hopper: Updated for version 4.5.18. > > development/jdk: Updated for version 8u231. > > development/jupyter_client: Updated for version 5.3.4. > > development/lepton-eda: Added (Lepton Electronic Design Automation). > > development/pycharm: Updated for version 2019.2.4. > > development/pyqt-distutils: Update DEP. > > development/python-docopt: Removed (duplicate). > > development/tiled: updated for version 1.3.0 > > development/vscode-bin: Updated for version 1.40.1. > > games/stockfish: Update EMAIL address. > > games/waterCloset: Added (An SDL2 based puzzle platform game). > > gis/GMT: Updated for version 6.0.0. > > gis/gpxsee: Updated for version 7.17. > > gis/openorienteering-mapper: Updated for version 0.9.0. > > gis/whitebox-tools: Updated for version 1.0.2. > > graphics/converseen: Updated for version 0.9.8.0. > > graphics/vuescan: Updated for version 9.7.08. > > graphics/white_dune: Updated for version 1.576. > > libraries/QScintilla-qt5: Added (Qt5 port of Scintilla C++ editor). > > libraries/dcmtk: Update for version 3.6.5 > > libraries/libcoap: Updated for version 4.2.1. > > libraries/libgig: Updated for version 4.2.0. > > libraries/live555: Updated for version 2019.11.11 > > libraries/qwt-qt5: Added (Qt5 widgets for technical applications). > > libraries/xforms: Fix typo > > multimedia/plexmediaserver: Updated for v 1.18.1.2019_c186313fe. > > network/3proxy: Updated for version 0.8.13. > > network/anydesk: Updated for version 5.4.1. > > network/dmitry: Updated for version 1.3a. > > network/dropbox: Updated for version 85.4.155. > > network/onedrive: Updated for version 2.3.11. > > network/prosody-mod-http-upload: Updated for version hg3713. > > network/remmina: Update script. > > network/zoom-linux: Updated for version 3.0.317369.1110. > > office/LibreOffice: Updated for version 6.2.8.2 > > office/gnucash-docs: Updated for version 3.6. > > office/gnucash: Updated for version 3.6. > > office/keepassxc: Updated for version 2.5.1. > > office/pdfstudio: Updated for version 2019.2.0. > > office/pdfstudioviewer: Updated for version 2019.2.0. > > office/xournalpp: Updated for version 1.0.16. > > python/Pyro4: Updated for version 4.77. > > python/hupper: updated for version 1.9.1 > > python/pycryptodome: Updated for version 3.9.2. > > python/python-requests: Update HOMEPAGE. > > python/python-serpent: Updated for version 1.28. > > python/python3-pylint: Updated for version 2.4.4. > > python/regex: Updated for version 2019.08.19. > > python/thonny: Updated for version 3.2.3. > > ruby/rubygem-ruumba: Updated for version 0.1.14. > > system/Iosevka: Updated for version 2.3.3. > > system/atop: Updated for version 2.5.0. > > system/capstone: Updated for version 4.0.1. > > system/collectd: Updated for version 5.10.0. > > system/epson-inkjet-printer-escpr: Updated for version 1.7.6. > > system/isdct: Updated for version 3.0.22. > > system/kbfs: Updated for version 5.0.0_20191114203213. > > system/keybase: Updated for version 5.0.0. > > system/mpich: Updated for version 3.3.2 > > system/postgresql: Updated for version 10.10. > > system/system76-io-dkms: Added (DKMS module). > > system/system76-power: Added (utility for managing graphics/power) > > system/telegraf: Updated for version 1.12.5. > > system/tpe-kmod: Updated for version 2.0.4. > > +--------------------------+ > > > > > > -- > > Willy Sudiarto Raharjo > > > > > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Nov 17 01:29:55 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Nov 2019 08:29:55 +0700 Subject: [Slackbuilds-users] Updates - 20191116.1 In-Reply-To: <20191117012143.GB20668@giustizia.org> References: <20191117012143.GB20668@giustizia.org> Message-ID: <6161dc28-5725-deee-252b-9deeb03b8a02@slackbuilds.org> > please take a look at the download URL from capstone in the info file. > The version in the file name is correct (4.0.1), but not in the rest of > the path (3.0.5). > > Unfortunately, that wrong URL resolves to the old source file and the > broken may pass undetected. Done, fixed in git and also in the server. 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 andreas at andreasvoegele.com Sun Nov 17 06:24:20 2019 From: andreas at andreasvoegele.com (=?UTF-8?Q?Andreas_V=c3=b6gele?=) Date: Sun, 17 Nov 2019 07:24:20 +0100 Subject: [Slackbuilds-users] PostgreSQL versioning scheme Message-ID: PostgreSQL changed its versioning scheme with version 10. See https://www.postgresql.org/about/news/1786/ and https://en.wikipedia.org/wiki/PostgreSQL#Release_history Shouldn't PG_VERSION in system/postgresql.SlackBuild be just "10" in order to simplify updates? According to https://www.postgresql.org/docs/10/upgrading.html cluster upgrades are not required for minor releases. "Minor releases never change the internal storage format and are always compatible with earlier and later minor releases of the same major version number. For example, version 10.1 is compatible with version 10.0 and version 10.6. [...] To update between compatible versions, you simply replace the executables while the server is down and restart the server. The data directory remains unchanged ? minor upgrades are that simple." From belka at caraus.de Sun Nov 17 06:56:47 2019 From: belka at caraus.de (Eugen Wissner) Date: Sun, 17 Nov 2019 07:56:47 +0100 Subject: [Slackbuilds-users] PostgreSQL versioning scheme In-Reply-To: References: Message-ID: <1573973807.16154.1.camel@caraus.de> Yes, would be a good thing. Now I have to pass PG_VERSION=10 to the SlackBuild explicitly and if I forget it, the installation is broken. Am Sonntag, den 17.11.2019, 07:24 +0100 schrieb Andreas V?gele via SlackBuilds-users: > PostgreSQL changed its versioning scheme with version 10. See? > https://www.postgresql.org/about/news/1786/ and? > https://en.wikipedia.org/wiki/PostgreSQL#Release_history > > Shouldn't PG_VERSION in system/postgresql.SlackBuild be just "10" in? > order to simplify updates? > > According to https://www.postgresql.org/docs/10/upgrading.html > cluster? > upgrades are not required for minor releases. > > "Minor releases never change the internal storage format and are > always? > compatible with earlier and later minor releases of the same major? > version number. For example, version 10.1 is compatible with version? > 10.0 and version 10.6. [...] To update between compatible versions, > you? > simply replace the executables while the server is down and restart > the? > server. The data directory remains unchanged ? minor upgrades are > that? > simple." > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sun Nov 17 10:26:29 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 17 Nov 2019 17:26:29 +0700 Subject: [Slackbuilds-users] PostgreSQL versioning scheme In-Reply-To: References: Message-ID: <95df4836-1871-bf41-7ce6-bd2ed9e7c843@slackbuilds.org> > PostgreSQL changed its versioning scheme with version 10. See > https://www.postgresql.org/about/news/1786/ and > https://en.wikipedia.org/wiki/PostgreSQL#Release_history > > Shouldn't PG_VERSION in system/postgresql.SlackBuild be just "10" in > order to simplify updates? > > According to https://www.postgresql.org/docs/10/upgrading.html cluster > upgrades are not required for minor releases. > > "Minor releases never change the internal storage format and are always > compatible with earlier and later minor releases of the same major > version number. For example, version 10.1 is compatible with version > 10.0 and version 10.6. [...] To update between compatible versions, you > simply replace the executables while the server is down and restart the > server. The data directory remains unchanged ? minor upgrades are that > simple." I CC the maintainer just in case he didn't follow the list yet -- 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 yakizarns1 at gmail.com Sun Nov 17 12:35:35 2019 From: yakizarns1 at gmail.com (Dionysis Ntreou) Date: Sun, 17 Nov 2019 12:35:35 +0000 Subject: [Slackbuilds-users] PostgreSQL versioning scheme In-Reply-To: References: Message-ID: Totally missed this Thanks for letting me know having a read through that at this moment. I have done the change and works perfectly Will push soon On Sun, Nov 17, 2019 at 6:24 AM Andreas V?gele via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > PostgreSQL changed its versioning scheme with version 10. See > https://www.postgresql.org/about/news/1786/ and > https://en.wikipedia.org/wiki/PostgreSQL#Release_history > > Shouldn't PG_VERSION in system/postgresql.SlackBuild be just "10" in > order to simplify updates? > > According to https://www.postgresql.org/docs/10/upgrading.html cluster > upgrades are not required for minor releases. > > "Minor releases never change the internal storage format and are always > compatible with earlier and later minor releases of the same major > version number. For example, version 10.1 is compatible with version > 10.0 and version 10.6. [...] To update between compatible versions, you > simply replace the executables while the server is down and restart the > server. The data directory remains unchanged ? minor upgrades are that > simple." > _______________________________________________ > 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 slackbuilds at jaxartes.net Sun Nov 17 17:32:15 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 17 Nov 2019 09:32:15 -0800 Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> Message-ID: <9502219.zhghdeTENi@wintermute.sprawl.net> On Monday, 11 November 2019 14:31:58 PST Benjamin Trigona-Harany wrote: > There are a few regressions or scripts which will need to be removed (or > possibly patched from dev branches): > gis/OTB will lose Python support > gis/qlandkartegt no longer builds (but it's deprecated in favour of > qmapshack anyhow) > gis/osgEarth no longer builds but upcoming version 3.0 will work from what I > can tell > gis/libLAS no longer builds but isn't required by any projects and looks to > be deprecated in favour of PDAL > gis/merkaartor no longer builds but I think there might be commits in master > that should make it work > gis/pyspatialite no longer works but it is not needed by newer versions of > QGIS anymore > misc/zyGrib not building because of new proj Update on the list of packages that would be affected by upgrades to GDAL/ geos/proj. Now fixed: gis/merkaartor: project updated and supports all the new libraries gis/osgEarth: I patched the source so that it builds and runs Two scripts will have minor changes: gis/libLAS: loses GDAL support gis/OTB: loses Python support SlackBuilds have been or should be removed since they are deprecated: gis/qlandkartegt: obsoleted by qmapshack gis/pyspatialite: removed as it is no longer needed by QGIS misc/zyGrib: made obsolete by new project xyGrib With that, I think we are good to upgrade unless anyone has uncovered anything else during testing. Ben From rshepard at appl-ecosys.com Sun Nov 17 17:35:20 2019 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 17 Nov 2019 09:35:20 -0800 (PST) Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: <9502219.zhghdeTENi@wintermute.sprawl.net> References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> <9502219.zhghdeTENi@wintermute.sprawl.net> Message-ID: On Sun, 17 Nov 2019, Benjamin Trigona-Harany wrote: > Two scripts will have minor changes: > gis/libLAS: loses GDAL support Ben, I read that libLAS has been deprecated and replaced by PDAL. Does that affect anything? Regards, Rich From slackbuilds at jaxartes.net Sun Nov 17 17:41:53 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 17 Nov 2019 09:41:53 -0800 Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> <9502219.zhghdeTENi@wintermute.sprawl.net> Message-ID: <32142924.ragG3UtmJ8@wintermute.sprawl.net> On Sunday, 17 November 2019 09:35:20 PST Rich Shepard wrote: > On Sun, 17 Nov 2019, Benjamin Trigona-Harany wrote: > > Two scripts will have minor changes: > > gis/libLAS: loses GDAL support > > Ben, > > I read that libLAS has been deprecated and replaced by PDAL. Does that > affect anything? > > Regards, > > Rich The change to libLAS will be fairly minor - not being built against GDAL. As far as I know, the only functional change is: "libLAS 1.6+ allows you to assign color information to a .las file if GDAL is linked in at compile-time." libLAS is an optional dependency for a small number of SlackBuilds and I don't think the change above will cause any issues, but happy to hear any feedback if I'm mistaken. Ben From hedgehog87 at hotmail.it Sun Nov 17 17:49:59 2019 From: hedgehog87 at hotmail.it (Cristiano Urban) Date: Sun, 17 Nov 2019 17:49:59 +0000 Subject: [Slackbuilds-users] R: Updates - 20191116.1 In-Reply-To: References: <20191117012143.GB20668@giustizia.org>, <6161dc28-5725-deee-252b-9deeb03b8a02@slackbuilds.org>, Message-ID: I'm sorry, I previously sent the e-mail only to Willy instead of answering to all of you (my mistake). gdal fails when I try to build it having previously installed cryptopp. Here I attach some output. ___________________________________________ Site/blog @ https://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) ________________________________ Da: Cristiano Urban Inviato: domenica 17 novembre 2019 17:04 A: Willy Sudiarto Raharjo Oggetto: R: [Slackbuilds-users] Updates - 20191116.1 Hi, gdal fails when I try to build it having previously installed cryptopp. You can see the attachment for more details. ___________________________________________ Site/blog @ https://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) ________________________________ Da: SlackBuilds-users per conto di Willy Sudiarto Raharjo Inviato: domenica 17 novembre 2019 02:29 A: Luiz Carlos Ramos ; SlackBuilds.org Users List Oggetto: Re: [Slackbuilds-users] Updates - 20191116.1 > please take a look at the download URL from capstone in the info file. > The version in the file name is correct (4.0.1), but not in the rest of > the path (3.0.5). > > Unfortunately, that wrong URL resolves to the old source file and the > broken may pass undetected. Done, fixed in git and also in the server. Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: gdal_error.txt URL: From slackbuilds at jaxartes.net Sun Nov 17 17:52:38 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Sun, 17 Nov 2019 09:52:38 -0800 Subject: [Slackbuilds-users] R: Updates - 20191116.1 In-Reply-To: References: Message-ID: <2056459.lsrmMcxFfZ@wintermute.sprawl.net> On Sunday, 17 November 2019 09:49:59 PST Cristiano Urban wrote: > I'm sorry, I previously sent the e-mail only to Willy instead of answering > to all of you (my mistake). > > gdal fails when I try to build it having previously installed cryptopp. > Here I attach some output. Hi Cristiano, Willy and I were just chatting about it on IRC and I confirmed that this won't be a problem when the GDAL 3.0.0 SlackBuild goes out in next week's updates. Best, Ben > ___________________________________________ > Site/blog @ https://crish4cks.net/ > Registered user #488179 @ http://linuxcounter.net > Slackware, because it works! =) > ________________________________ > Da: Cristiano Urban > Inviato: domenica 17 novembre 2019 17:04 > A: Willy Sudiarto Raharjo > Oggetto: R: [Slackbuilds-users] Updates - 20191116.1 > > Hi, > gdal fails when I try to build it having previously installed cryptopp. > You can see the attachment for more details. > > ___________________________________________ > Site/blog @ https://crish4cks.net/ > Registered user #488179 @ http://linuxcounter.net > Slackware, because it works! =) > ________________________________ > Da: SlackBuilds-users per conto > di Willy Sudiarto Raharjo Inviato: domenica 17 > novembre 2019 02:29 > A: Luiz Carlos Ramos ; SlackBuilds.org Users List > Oggetto: Re: [Slackbuilds-users] > Updates - 20191116.1 > > > please take a look at the download URL from capstone in the info file. > > The version in the file name is correct (4.0.1), but not in the rest of > > the path (3.0.5). > > > > Unfortunately, that wrong URL resolves to the old source file and the > > broken may pass undetected. > > Done, fixed in git and also in the server. > > Thanks > > -- > Willy Sudiarto Raharjo From hedgehog87 at hotmail.it Sun Nov 17 17:54:41 2019 From: hedgehog87 at hotmail.it (Cristiano Urban) Date: Sun, 17 Nov 2019 17:54:41 +0000 Subject: [Slackbuilds-users] R: R: Updates - 20191116.1 In-Reply-To: <2056459.lsrmMcxFfZ@wintermute.sprawl.net> References: , <2056459.lsrmMcxFfZ@wintermute.sprawl.net> Message-ID: Ok! Thank you very much Benjamin! ___________________________________________ Site/blog @ https://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) ________________________________ Da: Benjamin Trigona-Harany Inviato: domenica 17 novembre 2019 18:52 A: slackbuilds-users at slackbuilds.org Cc: Cristiano Urban Oggetto: Re: [Slackbuilds-users] R: Updates - 20191116.1 On Sunday, 17 November 2019 09:49:59 PST Cristiano Urban wrote: > I'm sorry, I previously sent the e-mail only to Willy instead of answering > to all of you (my mistake). > > gdal fails when I try to build it having previously installed cryptopp. > Here I attach some output. Hi Cristiano, Willy and I were just chatting about it on IRC and I confirmed that this won't be a problem when the GDAL 3.0.0 SlackBuild goes out in next week's updates. Best, Ben > ___________________________________________ > Site/blog @ https://crish4cks.net/ > Registered user #488179 @ http://linuxcounter.net > Slackware, because it works! =) > ________________________________ > Da: Cristiano Urban > Inviato: domenica 17 novembre 2019 17:04 > A: Willy Sudiarto Raharjo > Oggetto: R: [Slackbuilds-users] Updates - 20191116.1 > > Hi, > gdal fails when I try to build it having previously installed cryptopp. > You can see the attachment for more details. > > ___________________________________________ > Site/blog @ https://crish4cks.net/ > Registered user #488179 @ http://linuxcounter.net > Slackware, because it works! =) > ________________________________ > Da: SlackBuilds-users per conto > di Willy Sudiarto Raharjo Inviato: domenica 17 > novembre 2019 02:29 > A: Luiz Carlos Ramos ; SlackBuilds.org Users List > Oggetto: Re: [Slackbuilds-users] > Updates - 20191116.1 > > > please take a look at the download URL from capstone in the info file. > > The version in the file name is correct (4.0.1), but not in the rest of > > the path (3.0.5). > > > > Unfortunately, that wrong URL resolves to the old source file and the > > broken may pass undetected. > > Done, fixed in git and also in the server. > > Thanks > > -- > Willy Sudiarto Raharjo -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Sun Nov 17 17:55:34 2019 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 17 Nov 2019 09:55:34 -0800 (PST) Subject: [Slackbuilds-users] Feedback on upgrading GDAL/geos/proj In-Reply-To: <32142924.ragG3UtmJ8@wintermute.sprawl.net> References: <2415170.nPLCpBH4Gp@wintermute.sprawl.net> <9502219.zhghdeTENi@wintermute.sprawl.net> <32142924.ragG3UtmJ8@wintermute.sprawl.net> Message-ID: On Sun, 17 Nov 2019, Benjamin Trigona-Harany wrote: > The change to libLAS will be fairly minor - not being built against GDAL. > As far as I know, the only functional change is: "libLAS 1.6+ allows you > to assign color information to a .las file if GDAL is linked in at > compile-time." Ben, Here, libLAS-1.8.1 would not build so I removed it as a GRASS dependency (for now). > libLAS is an optional dependency for a small number of SlackBuilds and I > don't think the change above will cause any issues, but happy to hear any > feedback if I'm mistaken. I don't recall where I read that it has been deprecated. For some reason I've yet to find qgis-3.10.0 still won't build here. I don't need it immediately so I'll keep futzing with it. Thanks for all your work on the spatial libraries. Best regards, Rich From lenardrspencer at gmail.com Mon Nov 18 00:45:00 2019 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Sun, 17 Nov 2019 19:45:00 -0500 Subject: [Slackbuilds-users] Gnucash Message-ID: I have reverted gnucash to 3.6 for now in SBo master/14.2 until version 3.8 comes out. The REQUIRES has also been updated in the .info file to show pygobject3-python3. BUT, for those of you running -current (including myself), 3.7 builds and runs just fine there and the extra dep is not needed since pygobject3 is already built with python3 support. Hope this helps. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Mon Nov 18 01:53:36 2019 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Sun, 17 Nov 2019 17:53:36 -0800 (PST) Subject: [Slackbuilds-users] Gnucash In-Reply-To: References: Message-ID: On Sun, 17 Nov 2019, Lenard Spencer wrote: > I have reverted gnucash to 3.6 for now in SBo master/14.2 until version > 3.8 comes out. The REQUIRES has also been updated in the .info file to > show pygobject3-python3. BUT, for those of you running -current (including > myself), 3.7 builds and runs just fine there and the extra dep is not > needed since pygobject3 is already built with python3 support. Lenard, FWIW, I'm running gnucash-3.7 on 14.2/x86_64 with python3-3.7.4 installed. I change the version in the build script and it keeps on working. Regards, Rich From jbernts at broadpark.no Mon Nov 18 12:47:03 2019 From: jbernts at broadpark.no (Jostein Berntsen) Date: Mon, 18 Nov 2019 13:47:03 +0100 Subject: [Slackbuilds-users] RSSOwl error Message-ID: <20191118124703.GA2483@jostein> RSSOwl errors out after started and selecting a rss post with: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f0334020f00, pid=14610, # tid=0x00007f035050b700 # # JRE version: OpenJDK Runtime Environment (8.0_222-b10) (build # 1.8.0_222-b10) # Java VM: OpenJDK 64-Bit Server VM (25.222-b10 mixed mode linux-amd64 # compressed oops) # Derivative: IcedTea 3.13.0 # Distribution: Custom build (Fri Jul 19 07:34:56 CEST 2019) # Problematic frame: # C [libpangoft2-1.0.so.0+0xbf00] pango_fc_font_key_get_variations+0x0 # # Failed to write core dump. Core dumps have been disabled. To enable # core dumping, try "ulimit -c unlimited" before starting Java again Jostein From gerardo.zamudio at linux.com Mon Nov 18 14:24:03 2019 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 18 Nov 2019 08:24:03 -0600 Subject: [Slackbuilds-users] network/deluge up for grabs Message-ID: <4771734.mRo3NQLzRG@hades.slack.lan> Hi all, Since I switched to KDE Plasma a few years ago I have not used Deluge (I use KTorrent now). Deluge 2.0 was released back in June. The new version uses Python 3 and GTK3. I have not taken the time to review what will be required to build the new version. If it requires a newer GTK3, it may not build in stock 14.2. The package is up for grabs by anyone who wants it. Regards, Gerardo Zamudio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From gerardo.zamudio at linux.com Mon Nov 18 17:24:33 2019 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 18 Nov 2019 11:24:33 -0600 Subject: [Slackbuilds-users] ldns build failure Message-ID: <2927606.gmIQLcA86q@hades.slack.lan> Hello, I am trying to build ldns-1.7.1 but it fails with an error saying "No targets specified and no makefile found". The full build log is here[1] I am using stock Slackware 14.2 with all updates applied. I have tried: * building Perl dependencies manually, CPAN, and sbopkg * using more recent (latest) versions of the Perl dependencies and sub dependencies listed in the INFO file * building ldns-1.7.0 * building on stock 14.2 with NO updates applied * applying this patch[2] which I found in this issue[3] * applying this patch[4] which I found in this FreeBSD bug report[5] [1] https://pastebin.com/d1K8u1jE [2] https://github.com/NLnetLabs/ldns/pull/41 [3] https://github.com/NLnetLabs/ldns/issues/40 [4] https://svnweb.freebsd.org/ports/head/dns/ldns/files/patch-packaging_ldns-config.in?view=log [5] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240297 >From what I can see in the log, the build fails at the DNS-LDNS Perl module compilation. There is a message that states "Can't link/include C library 'ldns', 'ldns', aborting." so I suspect some path is wrong somewhere. Does anyone have any ideas for fixing this? Have any of you been able to compile ldns-1.7.1 on stock Slackware 14.2? Thanks, Gerardo Zamudio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From willysr at slackbuilds.org Mon Nov 18 17:41:12 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 19 Nov 2019 00:41:12 +0700 Subject: [Slackbuilds-users] ldns build failure In-Reply-To: <2927606.gmIQLcA86q@hades.slack.lan> References: <2927606.gmIQLcA86q@hades.slack.lan> Message-ID: <3062c80b-a17e-bc1c-a2f6-95210f9b34bd@slackbuilds.org> > I am trying to build ldns-1.7.1 but it fails with an error saying "No targets > specified and no makefile found". The full build log is here[1] > > I am using stock Slackware 14.2 with all updates applied. I have tried: > > * building Perl dependencies manually, CPAN, and sbopkg > * using more recent (latest) versions of the Perl dependencies and sub > dependencies listed in the INFO file > * building ldns-1.7.0 > * building on stock 14.2 with NO updates applied > * applying this patch[2] which I found in this issue[3] > * applying this patch[4] which I found in this FreeBSD bug report[5] > > [1] https://pastebin.com/d1K8u1jE > [2] https://github.com/NLnetLabs/ldns/pull/41 > [3] https://github.com/NLnetLabs/ldns/issues/40 > [4] https://svnweb.freebsd.org/ports/head/dns/ldns/files/patch-packaging_ldns-config.in?view=log > [5] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240297 > > From what I can see in the log, the build fails at the DNS-LDNS Perl module > compilation. There is a message that states "Can't link/include C library > 'ldns', 'ldns', aborting." so I suspect some path is wrong somewhere. > > Does anyone have any ideas for fixing this? Have any of you been able to > compile ldns-1.7.1 on stock Slackware 14.2? Works just fine here perl-IO-CaptureOutput: MD5SUM check for IO-CaptureOutput-1.1104.tar.gz ... OK Building package perl-IO-CaptureOutput-1.1104-x86_64-1_SBo.tgz ... OK Installing package perl-IO-CaptureOutput-1.1104-x86_64-1_SBo.tgz ... OK perl-Devel-CheckLib: MD5SUM check for Devel-CheckLib-1.07.tar.gz ... OK Building package perl-Devel-CheckLib-1.07-x86_64-1_SBo.tgz ... OK Installing package perl-Devel-CheckLib-1.07-x86_64-1_SBo.tgz ... OK perl-Sub-Uplevel: MD5SUM check for Sub-Uplevel-0.25.tar.gz ... OK Building package perl-Sub-Uplevel-0.25-x86_64-1_SBo.tgz ... OK Installing package perl-Sub-Uplevel-0.25-x86_64-1_SBo.tgz ... OK perl-Test-Exception: MD5SUM check for Test-Exception-0.43.tar.gz ... OK Building package perl-Test-Exception-0.43-x86_64-1_SBo.tgz ... OK Installing package perl-Test-Exception-0.43-x86_64-1_SBo.tgz ... OK ldns: MD5SUM check for ldns-1.7.1.tar.gz ... OK MD5SUM check for root-anchors.xml ... OK Building package ldns-1.7.1-x86_64-1_SBo.tgz ... OK Installing package ldns-1.7.1-x86_64-1_SBo.tgz ... OK -- 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 appl-cidr2 at protonmail.com Mon Nov 18 17:55:09 2019 From: appl-cidr2 at protonmail.com (appl-cidr2) Date: Mon, 18 Nov 2019 17:55:09 +0000 Subject: [Slackbuilds-users] ldns build failure In-Reply-To: <2927606.gmIQLcA86q@hades.slack.lan> References: <2927606.gmIQLcA86q@hades.slack.lan> Message-ID: Hi Gerardo, I use your slackbuilds for ldns and unbound. For feedback I can tell you both (and ldns-1.7.1 specifically) build w/ no problems on -current - using the same versions of perl deps listed in Willy's post. Regards, appl-cidr2 Sent with ProtonMail Secure Email. ??????? Original Message ??????? On Monday, November 18, 2019 5:24 PM, Gerardo Zamudio wrote: > Hello, > > I am trying to build ldns-1.7.1 but it fails with an error saying "No targets > specified and no makefile found". The full build log is here[1] > > I am using stock Slackware 14.2 with all updates applied. I have tried: > > - building Perl dependencies manually, CPAN, and sbopkg > - using more recent (latest) versions of the Perl dependencies and sub > dependencies listed in the INFO file > > - building ldns-1.7.0 > - building on stock 14.2 with NO updates applied > - applying this patch[2] which I found in this issue[3] > - applying this patch[4] which I found in this FreeBSD bug report[5] > > [1] https://pastebin.com/d1K8u1jE > [2] https://github.com/NLnetLabs/ldns/pull/41 > [3] https://github.com/NLnetLabs/ldns/issues/40 > [4] https://svnweb.freebsd.org/ports/head/dns/ldns/files/patch-packaging_ldns-config.in?view=log > [5] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240297 > > From what I can see in the log, the build fails at the DNS-LDNS Perl module > compilation. There is a message that states "Can't link/include C library > 'ldns', 'ldns', aborting." so I suspect some path is wrong somewhere. > > Does anyone have any ideas for fixing this? Have any of you been able to > compile ldns-1.7.1 on stock Slackware 14.2? > > Thanks, > Gerardo Zamudio_______________________________________________ > 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 poprocks at gmail.com Mon Nov 18 18:54:27 2019 From: poprocks at gmail.com (Logan Rathbone) Date: Mon, 18 Nov 2019 13:54:27 -0500 Subject: [Slackbuilds-users] network/deluge up for grabs In-Reply-To: <4771734.mRo3NQLzRG@hades.slack.lan> References: <4771734.mRo3NQLzRG@hades.slack.lan> Message-ID: <20191118185427.GA30034@darkstar.example.net> On Mon, Nov 18, 2019 at 08:24:03AM -0600, Gerardo Zamudio wrote: > Hi all, > > Since I switched to KDE Plasma a few years ago I have not used Deluge (I use > KTorrent now). > > Deluge 2.0 was released back in June. The new version uses Python 3 and GTK3. > I have not taken the time to review what will be required to build the new > version. If it requires a newer GTK3, it may not build in stock 14.2. > > The package is up for grabs by anyone who wants it. I'll take this. Regards, Logan "Poprocks" From gerardo.zamudio at linux.com Mon Nov 18 19:35:16 2019 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 18 Nov 2019 13:35:16 -0600 Subject: [Slackbuilds-users] ldns build failure In-Reply-To: References: <2927606.gmIQLcA86q@hades.slack.lan> Message-ID: <23851860.EEO0rsWToi@hades.slack.lan> On Monday, November 18, 2019 11:55:09 AM CST appl-cidr2 via SlackBuilds-users wrote: > Hi Gerardo, > > I use your slackbuilds for ldns and unbound. For feedback I can tell > you both (and ldns-1.7.1 specifically) build w/ no problems on -current - > using the same versions of perl deps listed in Willy's post. > > Regards, > appl-cidr2 Hi appl-cidr2 and Willy, Thanks for the confirmation. I don't maintain ldns but I am trying to submit an update to unbound and want to make sure it works with 1.7.1 I looked at my "clean" Slackware VM and it turns out I have it set up with this in /etc/profile: export MAKEFLAGS=${MAKEFLAGS:-"-j$(nproc)"} It's one of the very few minimal changes I make to the VM image when building it (along with setting a slackpkg mirror, color prompt, aliases). I guess ldns is one of those packages that just doesn't build with more jobs. Thank you both for your quick response, Gerardo Zamudio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From gerardo.zamudio at linux.com Mon Nov 18 20:16:52 2019 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 18 Nov 2019 14:16:52 -0600 Subject: [Slackbuilds-users] network/deluge up for grabs In-Reply-To: <20191118185427.GA30034@darkstar.example.net> References: <4771734.mRo3NQLzRG@hades.slack.lan> <20191118185427.GA30034@darkstar.example.net> Message-ID: <5705064.eLJHHC60PG@hades.slack.lan> On Monday, November 18, 2019 12:54:27 PM CST Logan Rathbone wrote: > On Mon, Nov 18, 2019 at 08:24:03AM -0600, Gerardo Zamudio wrote: > > > > The package is up for grabs by anyone who wants it. > > I'll take this. > > Regards, > Logan "Poprocks" Take it. Feel free to submit an update to the new version with your name and email as the new maintainer. Regards, Gerardo Zamudio -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part. URL: From peter at peter-dambier.de Wed Nov 20 09:25:14 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Wed, 20 Nov 2019 10:25:14 +0100 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator Message-ID: I am missing apg. is it this one? Automated Password Generator (APG) PublishedOctober 5, 1993 Charles Dinkel Withdrawn on October 19, 2015 Here is a document including the source https://www.nist.gov/publications/automated-password-generator-apg There are many sources all the same md5sum in the internet. e.g. from Fossies the fresh open source software archive. https://fossies.org/linux/privat/old/apg-2.2.3.tar.gz The old (14.1) apg.SlackBuild works on my 32 bit Slackware Current. Can we trust NIST? I remember was an issue with tuned random number generators. But you can always add a SheBang to the suggested password. I know me own internal password generator depends on blood pressure and sugar and is far less trustworthy. If the maintainer has gone away I am willing to toke it. Cheers Peter -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From jdashiel at panix.com Wed Nov 20 13:33:28 2019 From: jdashiel at panix.com (Jude DaShiell) Date: Wed, 20 Nov 2019 08:33:28 -0500 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: One improvement that could be done to all of these password generators is to make sure every password starts with a letter and ends with a letter. That makes passwords more difficult by a little to crack. The reason for that is mathematics. Numbers and special symbols have a set size of 42 32 special symbols and 10 digits. Letters have a set size of 52 all lower-case and upper-case and the underscore. Why the underscore is understood as a letter by some people I don't know I would have thought that would have been a special symbol. On Wed, 20 Nov 2019, Peter Dambier wrote: > Date: Wed, 20 Nov 2019 04:25:14 > From: Peter Dambier > To: slackbuilds-users at slackbuilds.org > Subject: [Slackbuilds-users] apg-2.2.3 automated password generator > > I am missing apg. > > is it this one? > > Automated Password Generator (APG) > > PublishedOctober 5, 1993 > Charles Dinkel > Withdrawn on October 19, 2015 > > Here is a document including the source > > https://www.nist.gov/publications/automated-password-generator-apg > > There are many sources all the same md5sum in the internet. > > e.g. from Fossies the fresh open source software archive. > > https://fossies.org/linux/privat/old/apg-2.2.3.tar.gz > > The old (14.1) apg.SlackBuild works on my 32 bit Slackware Current. > > > Can we trust NIST? I remember was an issue with tuned random number > generators. But you can always add a SheBang to the suggested password. > I know me own internal password generator depends on blood pressure and > sugar and is far less trustworthy. > > If the maintainer has gone away I am willing to toke it. > > Cheers > Peter > > -- > Peter and Karin Dambier > Adalbert-Stifter-Strasse 17 > D-69509 Moerlenbach > +49(6209)280-3030 (VoIP: GGEW) > +49(6252)750-308 (VoIP: sipgate.de) > mail: peter at peter-dambier.de > _______________________________________________ > 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 erich.public at protonmail.com Wed Nov 20 14:43:11 2019 From: erich.public at protonmail.com (Erich Ritz) Date: Wed, 20 Nov 2019 14:43:11 +0000 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: ??????? Original Message ??????? On Wednesday, November 20, 2019 6:33 AM, Jude DaShiell wrote: > One improvement that could be done to all of these password generators > is to make sure every password starts with a letter and ends with a > letter. That makes passwords more difficult by a little to crack. The > reason for that is mathematics. Numbers and special symbols have a set > size of 42 32 special symbols and 10 digits. Letters have a set size of > 52 all lower-case and upper-case and the underscore. Why the underscore > is understood as a letter by some people I don't know I would have > thought that would have been a special symbol. > Your response if completely off-topic, but I feel I have to respond: Please don't roll your own crypto. https://crypto.stackexchange.com/questions/70445/what-is-the-origin-of-the-phrase-dont-roll-your-own-crypto https://www.schneier.com/blog/archives/2011/04/schneiers_law.html http://web.archive.org/web/20030629085904/http://www-106.ibm.com/developerworks/library/s-everything.html Your assertion is wrong. Assume a 3-character password and 3 different algorithms: 1) Each character is randomly chosen from your numbers/special/letters set (94 total characters) 2) 1st and last password character must be letters. 3) 1st and last password characters CANNOT be letters (only numbers and special symbols. Algorithm (1) has 94^3=830,584 possible passwords. Of those, some will begin and end with letters; some will start with a letter and end with a number/special, some will start with a number/special and end with a letter, and some will both start and end with a number/special. Algorithm (2) has 52*94*52=254,176 possible passwords. Algorithm (3) has 42*94*42=165,816 possible passwords. Your rationale compares algorithms (2) and (3) and concludes algorithm (2) is the best. But, you have completely discounted algorithm (1), which is by far the best algorithm. In general, adding any restrictions to the password generation decreases entropy. KeePass (or KeePassXC, can't remember which one) even warns of this when using their built-in password generator. From peter at peter-dambier.de Wed Nov 20 15:20:56 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Wed, 20 Nov 2019 16:20:56 +0100 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: Thankyou Erich, the only case worse than that would be to restrict to lowercase letters with even parity :) I tried a few runs. Slackware kernel 4.19.79-smp runs out of random numbers and then takes drastically longer. I have built my own kernel with crypto and random in mind and this one returns without delaying. I have compared it to a "native" Gentoo apg. They look the same. I am sure they are. Dont make your live depend on it but dont trust your smart builtin random generator either. Cheers Peter On 11/20/2019 03:43 PM, Erich Ritz via SlackBuilds-users wrote: > ??????? Original Message ??????? > On Wednesday, November 20, 2019 6:33 AM, Jude DaShiell wrote: > >> One improvement that could be done to all of these password generators >> is to make sure every password starts with a letter and ends with a >> letter. That makes passwords more difficult by a little to crack. The >> reason for that is mathematics. Numbers and special symbols have a set >> size of 42 32 special symbols and 10 digits. Letters have a set size of >> 52 all lower-case and upper-case and the underscore. Why the underscore >> is understood as a letter by some people I don't know I would have >> thought that would have been a special symbol. >> > > Your response if completely off-topic, but I feel I have to respond: > > Please don't roll your own crypto. > > https://crypto.stackexchange.com/questions/70445/what-is-the-origin-of-the-phrase-dont-roll-your-own-crypto > https://www.schneier.com/blog/archives/2011/04/schneiers_law.html > http://web.archive.org/web/20030629085904/http://www-106.ibm.com/developerworks/library/s-everything.html > > Your assertion is wrong. > > Assume a 3-character password and 3 different algorithms: > 1) Each character is randomly chosen from your numbers/special/letters set (94 total characters) > 2) 1st and last password character must be letters. > 3) 1st and last password characters CANNOT be letters (only numbers and special symbols. > > Algorithm (1) has 94^3=830,584 possible passwords. Of those, some will begin and end with letters; some will start with a letter and end with a number/special, some will start with a number/special and end with a letter, and some will both start and end with a number/special. > Algorithm (2) has 52*94*52=254,176 possible passwords. > Algorithm (3) has 42*94*42=165,816 possible passwords. > > Your rationale compares algorithms (2) and (3) and concludes algorithm (2) is the best. But, you have completely discounted algorithm (1), which is by far the best algorithm. > > In general, adding any restrictions to the password generation decreases entropy. KeePass (or KeePassXC, can't remember which one) even warns of this when using their built-in password generator. > _______________________________________________ > 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/ > -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From jdashiel at panix.com Wed Nov 20 15:34:31 2019 From: jdashiel at panix.com (Jude DaShiell) Date: Wed, 20 Nov 2019 10:34:31 -0500 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: Your example is insecure. On Wed, 20 Nov 2019, Erich Ritz via SlackBuilds-users wrote: > Date: Wed, 20 Nov 2019 09:43:11 > From: Erich Ritz via SlackBuilds-users > Reply-To: Erich Ritz , > SlackBuilds.org Users List > To: SlackBuilds.org Users List > Cc: Erich Ritz , > "peter at peter-dambier.de" > Subject: Re: [Slackbuilds-users] apg-2.2.3 automated password generator > > ??????? Original Message ??????? > On Wednesday, November 20, 2019 6:33 AM, Jude DaShiell wrote: > > > One improvement that could be done to all of these password generators > > is to make sure every password starts with a letter and ends with a > > letter. That makes passwords more difficult by a little to crack. The > > reason for that is mathematics. Numbers and special symbols have a set > > size of 42 32 special symbols and 10 digits. Letters have a set size of > > 52 all lower-case and upper-case and the underscore. Why the underscore > > is understood as a letter by some people I don't know I would have > > thought that would have been a special symbol. > > > > Your response if completely off-topic, but I feel I have to respond: > > Please don't roll your own crypto. > > https://crypto.stackexchange.com/questions/70445/what-is-the-origin-of-the-phrase-dont-roll-your-own-crypto > https://www.schneier.com/blog/archives/2011/04/schneiers_law.html > http://web.archive.org/web/20030629085904/http://www-106.ibm.com/developerworks/library/s-everything.html > > Your assertion is wrong. > > Assume a 3-character password and 3 different algorithms: > 1) Each character is randomly chosen from your numbers/special/letters set (94 total characters) > 2) 1st and last password character must be letters. > 3) 1st and last password characters CANNOT be letters (only numbers and special symbols. > > Algorithm (1) has 94^3=830,584 possible passwords. Of those, some will begin and end with letters; some will start with a letter and end with a number/special, some will start with a number/special and end with a letter, and some will both start and end with a number/special. > Algorithm (2) has 52*94*52=254,176 possible passwords. > Algorithm (3) has 42*94*42=165,816 possible passwords. > > Your rationale compares algorithms (2) and (3) and concludes algorithm (2) is the best. But, you have completely discounted algorithm (1), which is by far the best algorithm. > > In general, adding any restrictions to the password generation decreases entropy. KeePass (or KeePassXC, can't remember which one) even warns of this when using their built-in password generator. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -- From matteo.bernardini at gmail.com Wed Nov 20 15:55:22 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 20 Nov 2019 16:55:22 +0100 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: Il giorno mer 20 nov 2019 alle ore 14:33 Jude DaShiell ha scritto: > > One improvement that could be done to all of these password generators > is to make sure every password starts with a letter and ends with a > letter. That makes passwords more difficult by a little to crack. The > reason for that is mathematics. Numbers and special symbols have a set > size of 42 32 special symbols and 10 digits. Letters have a set size of > 52 all lower-case and upper-case and the underscore. Why the underscore > is understood as a letter by some people I don't know I would have > thought that would have been a special symbol. https://xkcd.com/936/ From didier at slint.fr Wed Nov 20 16:09:19 2019 From: didier at slint.fr (Didier Spaier) Date: Wed, 20 Nov 2019 17:09:19 +0100 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: Hi Matteo, this cartoon is funny, but hardly accessible by Jude who is blind (he is a Slint user, among other distributions). Cheers, Didier Le 11/20/19 ? 4:55 PM, Matteo Bernardini a ?crit?: > Il giorno mer 20 nov 2019 alle ore 14:33 Jude DaShiell > ha scritto: >> >> One improvement that could be done to all of these password generators >> is to make sure every password starts with a letter and ends with a >> letter. That makes passwords more difficult by a little to crack. The >> reason for that is mathematics. Numbers and special symbols have a set >> size of 42 32 special symbols and 10 digits. Letters have a set size of >> 52 all lower-case and upper-case and the underscore. Why the underscore >> is understood as a letter by some people I don't know I would have >> thought that would have been a special symbol. > > https://xkcd.com/936/ From matteo.bernardini at gmail.com Wed Nov 20 16:49:24 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 20 Nov 2019 17:49:24 +0100 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: Il giorno mer 20 nov 2019 alle ore 17:09 Didier Spaier ha scritto: > > Hi Matteo, > > this cartoon is funny, but hardly accessible by Jude who is blind > (he is a Slint user, among other distributions). sorry, I didn't know it. BTW, in the html of that page there's a
entry that I paste below: --- ((The comic illustrates the relative strength of passwords assuming basic knowledge of the system used to generate them. A set of boxes is used to indicate how many bits of entropy a section of the password provides. The comic is laid out with 6 panels arranged in a 3x2 grid. On each row, the first panel explains the breakdown of a password, the second panel shows how long it would take for a computer to guess, and the third panel provides an example scene showing someone trying to remember the password.)) [[The password "Tr0ub4dor&3" is shown in the centre of the panel. A line from each annotation indicates the word section the comment applies to.]] Uncommon (non-gibberish) base word [[Highlighting the base word - 16 bits of entropy.]] Caps? [[Highlighting the first letter - 1 bit of entropy.]] Common Substitutions [[Highlighting the letters 'a' (substituted by '4') and both 'o' (the first of which is substituted by '0') - 3 bits of entropy.]] Punctuation [[Highlighting the symbol appended to the word - 4 bits of entropy.]] Numeral [[Highlighting the number appended to the word - 3 bits of entropy.]] Order unknown [[Highlighting the appended characters - 1 bit of entropy.]] (You can add a few more bits to account for the fact that this is only one of a few common formats.) ~28 bits of entropy 2^28 = 3 days at 1000 guesses sec (Plausible attack on a weak remote web service. Yes, cracking a stolen hash is faster, but it's not what the average user should worry about.) Difficulty to guess: Easy. [[A person stands scratching their head trying to remember the password.]] Person: Was it trombone? No, Troubador. And one of the Os was a zero? Person: And there was some symbol... Difficulty to remember: Hard. [[The passphrase "correct horse battery staple" is shown in the centre of the panel.]] Four random common words {{Each word has 11 bits of entropy.}} ~44 bits of entropy. 2^44 = 550 years at 1000 guesses sec Difficulty to guess: Hard. [[A person is thinking, in their thought bubble a horse is standing to one side talking to an off-screen observer. An arrow points to a staple attached to the side of a battery.]] Horse: That's a battery staple. Observer: Correct! Difficulty to remember: You've already memorized it ((The caption below the comic reads: Through 20 years of effort, we've successfully trained everyone to use passwords that are hard for humans to remember, but easy for computers to guess.)) {{Title text: To anyone who understands information theory and security and is in an infuriating argument with someone who does not (possibly involving mixed case), I sincerely apologize.}} --- From peter at peter-dambier.de Wed Nov 20 18:03:14 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Wed, 20 Nov 2019 19:03:14 +0100 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: Long story short and without any more flames apg was originally developed by the nist to give pronounceable passwords that can easyly remembered. Most of them begin with a letter and end with a letter. From what I have seen apg uses the kernel random and entropy. From what I have experienced, I get emails from everybody with my password and name in the subject. Inside they want a lot of money or ... The only good thing, I used that password only for a single mailinglist and I was warned of this to happen. Inventing good passwords for each and every mailinglist- not a good idea. Relying on passwords only for security is not a good idea either. Getting a hickup whenever you see your name and password in the subject - it is spam after all. That is why I think Slackware should have an apg, almost everybody else has. If the nist has rectracted it, it must be good. Cheers Peter On 11/20/2019 05:49 PM, Matteo Bernardini wrote: > Il giorno mer 20 nov 2019 alle ore 17:09 Didier Spaier > ha scritto: >> >> Hi Matteo, >> >> this cartoon is funny, but hardly accessible by Jude who is blind >> (he is a Slint user, among other distributions). > > sorry, I didn't know it. > > BTW, in the html of that page there's a
entry > that I paste below: > > --- > > ((The comic illustrates the relative strength of passwords assuming > basic knowledge of the system used to generate them. A set of boxes is > used to indicate how many bits of entropy a section of the password > provides. The comic is laid out with 6 panels arranged in a 3x2 grid. > On each row, the first panel explains the breakdown of a password, the > second panel shows how long it would take for a computer to guess, and > the third panel provides an example scene showing someone trying to > remember the password.)) > > [[The password "Tr0ub4dor&3" is shown in the centre of the panel. A > line from each annotation indicates the word section the comment > applies to.]] > Uncommon (non-gibberish) base word [[Highlighting the base word - 16 > bits of entropy.]] > Caps? [[Highlighting the first letter - 1 bit of entropy.]] > Common Substitutions [[Highlighting the letters 'a' (substituted by > '4') and both 'o' (the first of which is substituted by '0') - 3 bits > of entropy.]] > Punctuation [[Highlighting the symbol appended to the word - 4 bits of > entropy.]] > Numeral [[Highlighting the number appended to the word - 3 bits of entropy.]] > Order unknown [[Highlighting the appended characters - 1 bit of entropy.]] > (You can add a few more bits to account for the fact that this is only > one of a few common formats.) > > ~28 bits of entropy > 2^28 = 3 days at 1000 guesses > sec > (Plausible attack on a weak remote web service. Yes, cracking a stolen > hash is faster, but it's not what the average user should worry > about.) > Difficulty to guess: Easy. > > [[A person stands scratching their head trying to remember the password.]] > Person: Was it trombone? No, Troubador. And one of the Os was a zero? > Person: And there was some symbol... > Difficulty to remember: Hard. > > [[The passphrase "correct horse battery staple" is shown in the centre > of the panel.]] > Four random common words {{Each word has 11 bits of entropy.}} > > ~44 bits of entropy. > 2^44 = 550 years at 1000 guesses > sec > Difficulty to guess: Hard. > > [[A person is thinking, in their thought bubble a horse is standing to > one side talking to an off-screen observer. An arrow points to a > staple attached to the side of a battery.]] > Horse: That's a battery staple. > Observer: Correct! > Difficulty to remember: You've already memorized it > > ((The caption below the comic reads: Through 20 years of effort, > we've successfully trained everyone to use passwords that are hard > for humans to remember, but easy for computers to guess.)) > > {{Title text: To anyone who understands information theory and > security and is in an infuriating argument with someone who does not > (possibly involving mixed case), I sincerely apologize.}} > > --- > _______________________________________________ > 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/ > -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From jebrhansen+SBo at gmail.com Thu Nov 21 03:04:23 2019 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 20 Nov 2019 20:04:23 -0700 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: On Wed, Nov 20, 2019, 8:34 AM Jude DaShiell wrote: > Your example is insecure. > Why is their example insecure? It seems like forcing a letter at the beginning and end limits the possible passwords by a significant amount. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at osh.id.au Thu Nov 21 03:53:05 2019 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 20 Nov 2019 23:53:05 -0400 Subject: [Slackbuilds-users] apg-2.2.3 automated password generator In-Reply-To: References: Message-ID: <17401fb7-3c1e-44ab-acb4-1c07207ed40c@www.fastmail.com> On Wed, 20 Nov 2019, at 9:33 AM, Jude DaShiell wrote: > One improvement that could be done to all of these password generators > is to make sure every password starts with a letter and ends with a > letter. That makes passwords more difficult by a little to crack. The > reason for that is mathematics. Numbers and special symbols have a set > size of 42 32 special symbols and 10 digits. Letters have a set size of > 52 all lower-case and upper-case and the underscore. It's hard to understand the logic of that: a = 42 (numbers/symbols) b = 52 (letters) c = a + b = 94 a < b < c So, draw from c. -- Dave From erik at slackbuilds.org Thu Nov 21 14:43:22 2019 From: erik at slackbuilds.org (Erik Hanson) Date: Thu, 21 Nov 2019 08:43:22 -0600 Subject: [Slackbuilds-users] RSSOwl error In-Reply-To: <20191118124703.GA2483@jostein> References: <20191118124703.GA2483@jostein> Message-ID: <87c6ec83-c86f-81e9-2182-3afcb92e4c7e@slackbuilds.org> On 11/18/19 6:47 AM, Jostein Berntsen wrote: > RSSOwl errors out after started and selecting a rss post with: RSSOwl is discontinued and is not safe to use. I will remove it from the repository soon. If someone would like to takeover and migrate to the maintained fork, please speak up quickly. https://github.com/Xyrio/RSSOwlnix -- Erik -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From peter at peter-dambier.de Fri Nov 22 08:34:10 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Fri, 22 Nov 2019 09:34:10 +0100 Subject: [Slackbuilds-users] imake and sbotmp Message-ID: I am fooling around with blt like tcl-blt, xDaliclock and xFishtank. X and iMake fit together like pantsbottom and toiletseat. I have never seen one without the other. Is there any x.SlackBuild I could borrow or should I select automake and forge the outcome until it looks like useable. Cheers Peter -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From peter at peter-dambier.de Fri Nov 22 10:12:26 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Fri, 22 Nov 2019 11:12:26 +0100 Subject: [Slackbuilds-users] imake and sbotmp In-Reply-To: References: Message-ID: <5d91a868-18eb-a9b4-7a10-93364836a6b5@peter-dambier.de> Answering my own question, I found xbmbrowser and xbmbrowser.SlackBuild seems to do what I need. On 11/22/2019 09:34 AM, Peter Dambier wrote: > I am fooling around with blt like tcl-blt, xDaliclock and xFishtank. > > X and iMake fit together like pantsbottom and toiletseat. I have never > seen one without the other. > > Is there any x.SlackBuild I could borrow or should I select automake > and forge the outcome until it looks like useable. > > Cheers > Peter > > -- > Peter and Karin Dambier > Adalbert-Stifter-Strasse 17 > D-69509 Moerlenbach > +49(6209)280-3030 (VoIP: GGEW) > +49(6252)750-308 (VoIP: sipgate.de) > mail: peter at peter-dambier.de > _______________________________________________ > 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/ > -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From slackbuilds at schoepfer.info Fri Nov 22 16:03:58 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 22 Nov 2019 17:03:58 +0100 Subject: [Slackbuilds-users] azr3 In-Reply-To: References: Message-ID: <08bec5a21a1c8b2372c332c4cff2a96a@schoepfer.info> Hi, i'd like to revive azr3, which seems it was dropped from SBo with 14.2: https://www.slackbuilds.org/repository/14.1/audio/azr3/ I mailed an BWatson, but got no reply since two weeks. Does somebody know the reason it was dropped? As it is unmaintained, may i take over? Johannes -------- Original Message -------- Subject: azr3 Date: 2019-11-10 19:52 From: Franzen To: yalhcru at gmail.com Hi B. Watson, may i ask you whay you dropped azr3 from SBo? Or, what alternative organ do you use? May it be worth activating azr3 again? Regards, Johannes From willysr at slackbuilds.org Fri Nov 22 16:16:48 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 22 Nov 2019 23:16:48 +0700 Subject: [Slackbuilds-users] azr3 In-Reply-To: <08bec5a21a1c8b2372c332c4cff2a96a@schoepfer.info> References: <08bec5a21a1c8b2372c332c4cff2a96a@schoepfer.info> Message-ID: <8ba3c847-3ffc-127c-ae8f-d9d115834c92@slackbuilds.org> > i'd like to revive azr3, which seems it was dropped from SBo with 14.2: > https://www.slackbuilds.org/repository/14.1/audio/azr3/ > > I mailed an BWatson, but got no reply since two weeks. > Does somebody know the reason it was dropped? > As it is unmaintained, may i take over? It was not building in 14.2 https://git.slackbuilds.org/slackbuilds/commit/?id=baaab4d446213c91d0f4c9bc82325ab14a3ee14d Feel free to resubmit if you can make it built on 14.2 -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Nov 23 09:14:05 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 23 Nov 2019 16:14:05 +0700 Subject: [Slackbuilds-users] Updates - 20191123.1 Message-ID: This batch of updates will bump GDAL, GEOS, PROJ and many other related packages to sync with upstream work. Big thanks to Benjamin for doing the effort to make this upgrade very smooth. Please see detailed changes on his original email: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2019-November/023485.html Sat Nov 23 09:03:15 UTC 2019 academic/ITK: Update download link. academic/Shark: Updated for version 4.0.0. audio/a2jmidid: Updated for version 9. audio/azr3: Added (tonewheel organ simulator). audio/setBfree: Added (A DSP Tonewheel Organ emulator). desktop/simplenote: Updated for version 1.11.0. development/byacc: Updated for version 20191119. development/dart: Updated for version 2.6.1. development/gambas3: Updated for version 3.14.2. development/jupyter-qtconsole: Updated for version 4.6.0. development/jupyter_core: Update for version 4.6.1. development/kotlin: Update VERSION. development/kotlin: Updated for version 1.3.60. development/sbcl: Updated for version 1.5.8. development/sqlitebrowser: Updated for version 3.11.2. development/sublime_merge: Added (A git client for Sublime Text). development/sublime_text: Updated for version 3.2.11. development/tig: Updated for version 2.5.0. development/yarn: Updated for version 1.19.2. games/vkQuake: Updated for version 1.03.0. gis/Fiona: Updated for version 1.8.11. gis/Fiona: Use Python 3 by default for CLI. gis/OTB: Fix comment. gis/OTB: Updated for version 7.0.0. gis/cartopy: Add support for proj6. gis/gdal: Updated for version 3.0.2. gis/geos: Make sure geos compiles under current. gis/geos: Updated for version 3.8.0. gis/grass: Add a couple of missing comments. gis/grass: Updated for version 7.8.0. gis/libLAS: Remove GDAL support. gis/libgeotiff: Updated for version 1.5.1. gis/libspatialite: Updated for version 4.3.0. gis/mapnik: Support proj version 6. gis/merkaartor: Updated for version 0.18.4. gis/osgEarth: Add geos 3.8 patch, remove Qt support. gis/osgEarth: Remove unneeded line from patch. gis/osm2pgsql: Updated for version 1.2.0. gis/ossim: Updated for version 2.10.0. gis/pdal: Updated for version 2.0.1. gis/pgsql-ogr-fdw: Updated for version 1.0.9. gis/proj: Updated for version 6.2.1. gis/pyproj: Updated for version 2.4.1 and removed Python 2 support. gis/pyspatialite: Removed. gis/python-mapnik: Python 3 won't work on 14.2. gis/qgis: Clarify build order in README. gis/qgis: Fix issue with build directory. gis/qgis: Remove comment from REQUIRES line. gis/qgis: Updated for version 3.10.0. gis/qlandkartegt: Removed (use qmapshack instead). gis/qmapshack: Fix paths. gis/rasterio: Enable Python 3 by default. gis/rasterio: Updated for version 1.1.0. gis/saga-gis: Alter metadata install path. graphics/vuescan: Update md5sums. graphics/white_dune: Updated for version 1.624. graphics/xdaliclock: Added (melting digital clock). libraries/QScintilla-qt5: Updated for version 2.11.3. libraries/libseccomp: Updated for version 2.4.2. libraries/libwpe: Added (General-purpose library for WPE WebKit). libraries/libxls: Updated for version 1.5.2. libraries/qwt-qt5: Updated for version 6.1.4. misc/zyGrib: Removed (no longer builds). multimedia/flashplayer-plugin: Updated for version 32.0.0.293. multimedia/pepperflash-plugin: Updated for version 32.0.0.293. multimedia/plexmediaserver: Updated for v 1.18.2.2041_3d469cb32. network/AdGuardHome: Updated for version 0.99.3. network/deluge: Updated for version 2.0.3. network/pyzor: New maintainer network/qutebrowser-tox: Updated for version 1.8.2. network/qutebrowser: Updated for version 1.8.2. network/slack: Updated for version 4.1.2. network/slimjet: Updated for version 24.0.6.0. network/spamassassin: Updated for version 3.4.2, new maintainer. network/teamviewer: Updated for version 15.0.8397. network/unbound: Updated for version 1.9.4. office/calibre-bin: Updated for version 4.4.0. pis/postgis: Updated for version 3.0.0. python/cocos2d: Updated for Python 3. python/kaptan: Updated for version 0.5.12. python/lockfile: Updated for Python 3. python/munch: Updated for version 2.5.0. python/nxt-python: Update README and update dep. python/pycryptodome: Updated for version 3.9.3. python/python-importlib_metadata: Added (Python package metadata). python/python-joblib: Updated for version 0.14.0. python/python-neovim: Updated for version 0.4.0. python/python-zipp: Added (Python module). python/python3-dateutil: Updated for version 2.8.1. python/python3-jsonschema: Updated for version 3.1.1. python/python3-pyrsistent: Added (persistent collections). python/python3-six: Updated for version 1.13.0. python/rencode: Added (Python module). python/waitress: Updated for version 1.3.1. ruby/ruby-build: Updated for version 20191111. system/capstone: Fix URL. system/clamav: Updated for version 0.102.1. system/multitail: Updated for version 6.5.0. system/noto-emoji: Updated for version 20191119. system/pspg: Updated for version 2.5.4. system/sboui: Updated for version 2.1. system/stow: Updated for version 2.3.1. system/telegraf: Updated for version 1.12.6. system/tmuxp: Updated for version 1.5.4. system/xen: Updated for version 4.12.1. +--------------------------+ -- 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 klaatu at member.fsf.org Sun Nov 24 08:41:33 2019 From: klaatu at member.fsf.org (Klaatu) Date: Sun, 24 Nov 2019 21:41:33 +1300 Subject: [Slackbuilds-users] Abandoning audiere SlackBuild Message-ID: <3367046.olmV3P38gc@beast> I'm going to drop the audiere library. I don't use it and it hasn't been updated in over a decade. Development seems to have ceased; the latest bug report was filed in 2015 and never resolved. Only one SlackBuild (Cuberok) claims to use it (as an optional dependency only), so this is likely to affect no one. If anyone wants to take it over, feel free. Otherwise, I'll politely ask Willy to remove it (or mark it as unmaintained, or whatever the official process is). From slackbuilds at schoepfer.info Sun Nov 24 13:38:01 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Sun, 24 Nov 2019 14:38:01 +0100 Subject: [Slackbuilds-users] Jack policy Message-ID: Hi, as there is no 'or/||' possible in the REQUIRES tag, installing package "a" with REQUIRES=jack-audio-connection-kit and then installing package "b" with REQUIRES=jack2 will end with a broken jack, as jack-audio-connection-kit and jack2 are conflicting packages. Details at https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 Grepping throus SBo git shows slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + | grep jack-audio-connection-kit | wc -l 73 slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + | grep jack2 | wc -l 6 If i change my builds to jack-audio-connection-kit, then there will only be two builds left with dep on jack2, namely MuseScore and lives. If their maintainers have no problem with jack-audio-connection-kit, maybe jack-audio-connection-kit could be handled as default jack on SBo? Johannes From fernando.lopezjr at gmail.com Mon Nov 25 00:43:02 2019 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 24 Nov 2019 17:43:02 -0700 Subject: [Slackbuilds-users] SBo: libregf not found. 404. Message-ID: -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Mon Nov 25 06:01:54 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 25 Nov 2019 06:01:54 +0000 Subject: [Slackbuilds-users] Jack policy In-Reply-To: References: Message-ID: <20191125060154.GB15005@blackswan> On 2019-11-24 14:38, Franzen put forth the proposition: > Hi, > > as there is no 'or/||' possible in the REQUIRES tag, installing package "a" > with REQUIRES=jack-audio-connection-kit > and then installing package "b" with REQUIRES=jack2 will end with a broken > jack, as jack-audio-connection-kit and jack2 > are conflicting packages. Details at https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 > > Grepping throus SBo git shows > > slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + | > grep jack-audio-connection-kit | wc -l > 73 > slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + | > grep jack2 | wc -l > 6 > > If i change my builds to jack-audio-connection-kit, then there will only be > two builds left with dep on jack2, namely > MuseScore and lives. > If their maintainers have no problem with jack-audio-connection-kit, maybe > jack-audio-connection-kit could > be handled as default jack on SBo? Personally, I find changing things to jack-audio-connection-kit from jack2 is a regression, and I'd recommend going the other way. I don't know the reasons that people stick to the now very old version. I've been running jack2 for several years and had no problems with it, or had to downgrade to the older jack. It's also what all the apps on Studioware use, and there haven't been any problems reported about it. This is just my 2 pennies though, speaking as an everyday jack user. -daw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From pfeifer.felix at gmail.com Mon Nov 25 07:50:37 2019 From: pfeifer.felix at gmail.com (Felix Pfeifer) Date: Mon, 25 Nov 2019 08:50:37 +0100 Subject: [Slackbuilds-users] Jack policy In-Reply-To: <20191125060154.GB15005@blackswan> References: <20191125060154.GB15005@blackswan> Message-ID: > Personally, I find changing things to jack-audio-connection-kit from jack2 is > a regression, and I'd recommend going the other way. I don't know the reasons > that people stick to the now very old version. > > I've been running jack2 for several years and had no problems with it, or had > to downgrade to the older jack. It's also what all the apps on Studioware > use, and there haven't been any problems reported about it. > > This is just my 2 pennies though, speaking as an everyday jack user. > Is jack2 supporting ALSA-MIDI? For my builds it would be OK to switch to jack2 as long as it supports ALSA-MIDI which I use to connect to my hardware. Also pd comes with support for ALSA-MIDI. cheers, Felix From chris.willing at linux.com Mon Nov 25 08:27:59 2019 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 25 Nov 2019 18:27:59 +1000 Subject: [Slackbuilds-users] Jack policy In-Reply-To: References: <20191125060154.GB15005@blackswan> Message-ID: <8bcc752c-e914-183b-0706-db6d006787e6@linux.com> On 25/11/19 5:50 pm, Felix Pfeifer wrote: >> Personally, I find changing things to jack-audio-connection-kit from jack2 is >> a regression, and I'd recommend going the other way. I don't know the reasons >> that people stick to the now very old version. >> >> I've been running jack2 for several years and had no problems with it, or had >> to downgrade to the older jack. It's also what all the apps on Studioware >> use, and there haven't been any problems reported about it. >> >> This is just my 2 pennies though, speaking as an everyday jack user. >> > > > Is jack2 supporting ALSA-MIDI? > For my builds it would be OK to switch to jack2 > as long as it supports ALSA-MIDI which I use > to connect to my hardware. Also pd comes with > support for ALSA-MIDI. > For a detailed list of differences & pros/cons, see: https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 SMP capability in jack2 seems attractive but see info in that linked page about why that is not necessarily such a big deal. The detailed feature differences table mentions that jack1 has builtin support for multiple sound cards (not in jack2). Also jack2 doesn't support Linux MIDI, according to that table. In other comments on that page, it says: "... current plan is to implement all Jack1 features into Jack 2 ..." which suggests (to me) that jack2 is still missing some features from jack1. However, jack2 supports DBUS & PulseAudio - not necessarily a plus for some people - for which jack1 requires patching to enable. Maybe those differences have been resolved since then - version 0.121.3 for jack1 and 1.9.10 for jack2. We're now at 0.125.0 for jack1 and 1.9.12 for jack2. chris From dave at slackbuilds.org Mon Nov 25 09:52:11 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 25 Nov 2019 09:52:11 +0000 Subject: [Slackbuilds-users] Jack policy In-Reply-To: References: <20191125060154.GB15005@blackswan> Message-ID: <20191125095211.GC15005@blackswan> On 2019-11-25 08:50, Felix Pfeifer put forth the proposition: > > Personally, I find changing things to jack-audio-connection-kit from jack2 is > > a regression, and I'd recommend going the other way. I don't know the reasons > > that people stick to the now very old version. > > > > I've been running jack2 for several years and had no problems with it, or had > > to downgrade to the older jack. It's also what all the apps on Studioware > > use, and there haven't been any problems reported about it. > > > > This is just my 2 pennies though, speaking as an everyday jack user. > > > > > Is jack2 supporting ALSA-MIDI? > For my builds it would be OK to switch to jack2 > as long as it supports ALSA-MIDI which I use > to connect to my hardware. Also pd comes with > support for ALSA-MIDI. > > cheers, > Felix I don't use midi myself and I have a slightly older version installed than on SBo at the moment, but the jackd man page has under alsa backend options -X, --midi [seq|raw] "Specify which ALSA MIDI system to provide access to. Using raw will provide a set of JACK MIDI ports that correspond to each raw ALSA device on the machine. Using seq will provide a set of JACK MIDI ports that correspond to each ALSA "sequencer" client (which includes each hardware MIDI port on the machine). raw provides slightly better performance but does not permit JACK MIDI communication with software written to use the ALSA "sequencer" API." ZSH<31>% jackd -dalsa -Xseq -r48000 -i2 -o2 jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit float little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit float little-endian ALSA: use 2 periods for playback port created: Midi-Through:midi/playback_1 port created: Midi-Through:midi/capture_1 port created: PCR:midi/playback_1 port created: PCR:midi/capture_1 port created: PCR:midi/playback_2 port created: PCR:midi/capture_2 port created: PCR:midi/playback_3 ZSH<30>% jack_lsp system:capture_1 system:capture_2 system:playback_1 system:playback_2 system:midi_capture_1 system:midi_playback_1 system:midi_capture_2 system:midi_playback_2 system:midi_capture_3 system:midi_playback_3 system:midi_capture_4 ZSH<32>% jackd -dalsa -Xraw -r48000 -i2 -o2 jackdmp 1.9.10 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2014 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in realtime mode with priority 10 self-connect-mode is "Don't restrict self connect requests" audio_reservation_init Acquire audio card Audio0 creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon|swmeter|-|32bit configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods ALSA: final selected sample format for capture: 32bit float little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit float little-endian ALSA: use 2 periods for playback scan: added port hw:3,0,0 in-hw-3-0-0-PCR-MIDI scan: added port hw:3,0,1 in-hw-3-0-1-PCR-1 scan: added port hw:3,0,2 in-hw-3-0-2-PCR-2 scan: added port hw:3,0,0 out-hw-3-0-0-PCR-MIDI scan: added port hw:3,0,1 out-hw-3-0-1-PCR-1 scan: opened port hw:3,0,0 in-hw-3-0-0-PCR-MIDI scan: opened port hw:3,0,1 in-hw-3-0-1-PCR-1 scan: opened port hw:3,0,2 in-hw-3-0-2-PCR-2 scan: opened port hw:3,0,0 out-hw-3-0-0-PCR-MIDI scan: opened port hw:3,0,1 out-hw-3-0-1-PCR-1 ZSH<30>% jack_lsp system:capture_1 system:capture_2 system:playback_1 system:playback_2 system:midi_capture_1 system:midi_capture_2 system:midi_capture_3 system:midi_playback_1 system:midi_playback_2 I can't imagine why they would ever remove midi support, but I hope that helps. -daw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Mon Nov 25 10:37:45 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 25 Nov 2019 10:37:45 +0000 Subject: [Slackbuilds-users] Jack policy In-Reply-To: <8bcc752c-e914-183b-0706-db6d006787e6@linux.com> References: <20191125060154.GB15005@blackswan> <8bcc752c-e914-183b-0706-db6d006787e6@linux.com> Message-ID: <20191125103745.GD15005@blackswan> On 2019-11-25 18:27, Christoph Willing put forth the proposition: > Also jack2 doesn't support Linux MIDI, according to that table. What do they actually mean by "Linux MIDI" though? Alsa? I can't imagine they would drop MIDI support altogether. It's what most musicians use right? I'm only a guitarist though (or was), not a keyboard player, so I don't have any use for it other than testing that sequencer and synth software etc. works. -daw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From peter at peter-dambier.de Mon Nov 25 10:53:12 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Mon, 25 Nov 2019 11:53:12 +0100 Subject: [Slackbuilds-users] Jack policy In-Reply-To: <20191125095211.GC15005@blackswan> References: <20191125060154.GB15005@blackswan> <20191125095211.GC15005@blackswan> Message-ID: <676a9446-903a-05d2-2563-8748d60102e5@peter-dambier.de> pulseaudio alarm. Jack 1 is alsa and Linux Midi. Jach 2 is pulseaudio and Apple OSX Midi. They did not finish to port everything from Jack 1 to Jack 2 yet but they continued to develop Jack 1. I am seeing this through my Slackware without pulseaudio eyes and I do experience both on AMD and Intel Atom a better audio and faster system. The other problem might be Jack 1 C, Jack 2 C++ So sorry to mention Gentoo: There might be a virtual Package Jack, that is emty and needs either Jack 1 or Jack 2 ... nut that only moves the trouble onto somebody elses desk and is a pain for the user. Kind regards Peter On 11/25/2019 10:52 AM, Dave Woodfall wrote: > On 2019-11-25 08:50, > Felix Pfeifer put forth the proposition: >>> Personally, I find changing things to jack-audio-connection-kit from jack2 is >>> a regression, and I'd recommend going the other way. I don't know the reasons >>> that people stick to the now very old version. >>> >>> I've been running jack2 for several years and had no problems with it, or had >>> to downgrade to the older jack. It's also what all the apps on Studioware >>> use, and there haven't been any problems reported about it. >>> >>> This is just my 2 pennies though, speaking as an everyday jack user. >>> >> >> >> Is jack2 supporting ALSA-MIDI? >> For my builds it would be OK to switch to jack2 >> as long as it supports ALSA-MIDI which I use >> to connect to my hardware. Also pd comes with >> support for ALSA-MIDI. >> >> cheers, >> Felix > > I don't use midi myself and I have a slightly older version installed > than on SBo at the moment, but the jackd man page has under alsa backend > options -X, --midi [seq|raw] > > "Specify which ALSA MIDI system to provide access to. Using raw will > provide a set of JACK MIDI ports that correspond to each raw ALSA device > on the machine. Using seq will provide a set of JACK MIDI ports that > correspond to each ALSA "sequencer" client (which includes each hardware > MIDI port on the machine). raw provides slightly better performance but > does not permit JACK MIDI communication with software written to use the > ALSA "sequencer" API." > > ZSH<31>% jackd -dalsa -Xseq -r48000 -i2 -o2 > jackdmp 1.9.10 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2014 Grame. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > self-connect-mode is "Don't restrict self connect requests" > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon|swmeter|-|32bit > configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods > ALSA: final selected sample format for capture: 32bit float little-endian > ALSA: use 2 periods for capture > ALSA: final selected sample format for playback: 32bit float little-endian > ALSA: use 2 periods for playback > port created: Midi-Through:midi/playback_1 > port created: Midi-Through:midi/capture_1 > port created: PCR:midi/playback_1 > port created: PCR:midi/capture_1 > port created: PCR:midi/playback_2 > port created: PCR:midi/capture_2 > port created: PCR:midi/playback_3 > > ZSH<30>% jack_lsp > system:capture_1 > system:capture_2 > system:playback_1 > system:playback_2 > system:midi_capture_1 > system:midi_playback_1 > system:midi_capture_2 > system:midi_playback_2 > system:midi_capture_3 > system:midi_playback_3 > system:midi_capture_4 > > ZSH<32>% jackd -dalsa -Xraw -r48000 -i2 -o2 > jackdmp 1.9.10 > Copyright 2001-2005 Paul Davis and others. > Copyright 2004-2014 Grame. > jackdmp comes with ABSOLUTELY NO WARRANTY > This is free software, and you are welcome to redistribute it > under certain conditions; see the file COPYING for details > JACK server starting in realtime mode with priority 10 > self-connect-mode is "Don't restrict self connect requests" > audio_reservation_init > Acquire audio card Audio0 > creating alsa driver ... hw:0|hw:0|1024|2|48000|2|2|nomon|swmeter|-|32bit > configuring for 48000Hz, period = 1024 frames (21.3 ms), buffer = 2 periods > ALSA: final selected sample format for capture: 32bit float little-endian > ALSA: use 2 periods for capture > ALSA: final selected sample format for playback: 32bit float little-endian > ALSA: use 2 periods for playback > scan: added port hw:3,0,0 in-hw-3-0-0-PCR-MIDI > scan: added port hw:3,0,1 in-hw-3-0-1-PCR-1 > scan: added port hw:3,0,2 in-hw-3-0-2-PCR-2 > scan: added port hw:3,0,0 out-hw-3-0-0-PCR-MIDI > scan: added port hw:3,0,1 out-hw-3-0-1-PCR-1 > scan: opened port hw:3,0,0 in-hw-3-0-0-PCR-MIDI > scan: opened port hw:3,0,1 in-hw-3-0-1-PCR-1 > scan: opened port hw:3,0,2 in-hw-3-0-2-PCR-2 > scan: opened port hw:3,0,0 out-hw-3-0-0-PCR-MIDI > scan: opened port hw:3,0,1 out-hw-3-0-1-PCR-1 > > ZSH<30>% jack_lsp > system:capture_1 > system:capture_2 > system:playback_1 > system:playback_2 > system:midi_capture_1 > system:midi_capture_2 > system:midi_capture_3 > system:midi_playback_1 > system:midi_playback_2 > > I can't imagine why they would ever remove midi support, but I hope that > helps. > > -daw > > > > _______________________________________________ > 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/ > -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From slackbuilds at schoepfer.info Mon Nov 25 11:15:13 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 25 Nov 2019 12:15:13 +0100 Subject: [Slackbuilds-users] Jack policy In-Reply-To: <676a9446-903a-05d2-2563-8748d60102e5@peter-dambier.de> References: <20191125060154.GB15005@blackswan> <20191125095211.GC15005@blackswan> <676a9446-903a-05d2-2563-8748d60102e5@peter-dambier.de> Message-ID: Hi, > Jack 1 is alsa and Linux Midi. > Jach 2 is pulseaudio and Apple OSX Midi. My intention was not to push users in either jack direction, but workaround the missing logical "or" in REQUIRES for applications that depend on a jack implementation. This could prevent pointless issues if someone e.g. install MuseScore and qtractor per sboutils, which aren't conflicting in reality. So i think there's no need for a poll what jack is better, but use the same jack for all apps in REQUIRES, and everybody is free to change that to the other jack, if one likes. The path to jack-audio-connecion-kit looked shorter to me, as only two builds need to be adjusted, but i don't have a preference. Johannes From dave at slackbuilds.org Mon Nov 25 11:24:36 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 25 Nov 2019 11:24:36 +0000 Subject: [Slackbuilds-users] Jack policy In-Reply-To: <676a9446-903a-05d2-2563-8748d60102e5@peter-dambier.de> References: <20191125060154.GB15005@blackswan> <20191125095211.GC15005@blackswan> <676a9446-903a-05d2-2563-8748d60102e5@peter-dambier.de> Message-ID: <20191125112436.GF15005@blackswan> On 2019-11-25 11:53, Peter Dambier put forth the proposition: > pulseaudio alarm. > > Jack 1 is alsa and Linux Midi. > Jach 2 is pulseaudio and Apple OSX Midi. Jack 2 works fine with Alsa and without pulse. That's how I've been using it for years. The jack2 man page says "Alsa MIDI", as I posted earlier. To stop pulseaudio, kill the daemon if it's running and comment out the lines in /etc/asound.conf: #pcm.default pulse #ctl.default pulse Then chmod -x /etc/rc.d/rc.pulseaudio to make sure it doesn't start at boot. This is the non-purist way of not using pulseaudio, and has worked for me since the release of 14.2. Also, the man page mentions about dbus: Defining $JACK_NO_AUDIO_RESERVATION will bypass audio device reservation via session bus (DBus). This can be useful if JACK was compiled with DBus support but should run on a headless system. I can confirm that it stops all the errors about X11 not running. -daw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Mon Nov 25 11:29:06 2019 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 25 Nov 2019 11:29:06 +0000 Subject: [Slackbuilds-users] Jack policy In-Reply-To: References: <20191125060154.GB15005@blackswan> <20191125095211.GC15005@blackswan> <676a9446-903a-05d2-2563-8748d60102e5@peter-dambier.de> Message-ID: <20191125112906.GG15005@blackswan> On 2019-11-25 12:15, Franzen put forth the proposition: > So i think there's no need for a poll what jack is better Sorry, my fault really. -daw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From slackbuilds at schoepfer.info Mon Nov 25 11:33:57 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Mon, 25 Nov 2019 12:33:57 +0100 Subject: [Slackbuilds-users] Jack policy In-Reply-To: <20191125112906.GG15005@blackswan> References: <20191125060154.GB15005@blackswan> <20191125095211.GC15005@blackswan> <676a9446-903a-05d2-2563-8748d60102e5@peter-dambier.de> <20191125112906.GG15005@blackswan> Message-ID: Am 25.11.19 um 12:29 schrieb Dave Woodfall: > On 2019-11-25 12:15, > Franzen put forth the proposition: >> So i think there's no need for a poll what jack is better > > Sorry, my fault really. In any case much value, i learned a lot about jack since yesterday. > -daw Cool shortcut, you need to make music with computers ;-) From klaatu at member.fsf.org Mon Nov 25 16:48:12 2019 From: klaatu at member.fsf.org (Klaatu) Date: Tue, 26 Nov 2019 05:48:12 +1300 Subject: [Slackbuilds-users] Jack policy In-Reply-To: References: Message-ID: <2164080.GSHLQbKFr4@beast> On Sunday, November 24, 2019 02:38:01 PM Franzen wrote: > Hi, > > as there is no 'or/||' possible in the REQUIRES tag, installing package > "a" with REQUIRES=jack-audio-connection-kit > and then installing package "b" with REQUIRES=jack2 will end with a > broken jack, as jack-audio-connection-kit and jack2 > are conflicting packages. Details at > https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_ja > ck2 > > Grepping throus SBo git shows > > slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + > > | grep jack-audio-connection-kit | wc -l > > 73 > slackbuilds> find . -type f -iname '*info' -exec grep -H REQUIRES '{}' + > > | grep jack2 | wc -l > > 6 > > If i change my builds to jack-audio-connection-kit, then there will only > be two builds left with dep on jack2, namely > MuseScore and lives. > If their maintainers have no problem with jack-audio-connection-kit, > maybe jack-audio-connection-kit could > be handled as default jack on SBo? > > Johannes > _______________________________________________ > 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/ I've been struggling with this on SBo for years. Last time I asked this list, the consensus was to just make a note in the README that *either* jack-audio- blah or jack2 were required. My thought was to just specify that "jack" is required, and let the user decide whether to install 'jack-audio-connection-kit' or 'jack2', but I guess that's a little too much like a "meta package". I wouldn't mind using jack2 as the default for SBo, if we're voting on the subject. I've used Jack2 since 2014 at least, and I've not run into problems with ALSA, JACK, or MIDI. However, I only use software MIDI (input through USB controllers) so I can't speak for physical [actual] MIDI interfaces. Even so, it's nearly 2020, and I feel like "most" users could safely default to jack2. The people connection daisy chains of MIDI synths directly to the back of their computer can fallback on jack-audio-connection-kit. From peter at peter-dambier.de Mon Nov 25 19:36:06 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Mon, 25 Nov 2019 20:36:06 +0100 Subject: [Slackbuilds-users] Trouble downloading from sourceforge.net Message-ID: Hi, e.g. from pcmanfm Slackbuild I wanted to download "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz" After lots of lots of redirect wget gave up. Trying the homepage got me into an ants nest where stupid me signed up for a newsletter in the 50th floor below ground but I still could not get the source. Google finally found it at: "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz" Again lots of lots of redirect and finally I get it from "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz" The redirects for both URLs looked the same. That is why I dont think there is a need to change the download in the SlackBuild. Horses tend to drop their manure everywhere but I remember there were quite a lot of downloads that did not succeed. pcmanfm actually was the first one I finally made to download after all obstacles. md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. and it runs on Slackware Current 32 Bit. Sorry for the rant but I had to vent because if I had blown my top like SpaceX did with Starship MK 1, I would look really silly :) Cheers Peter -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From atelszewski at gmail.com Mon Nov 25 19:41:01 2019 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Mon, 25 Nov 2019 20:41:01 +0100 Subject: [Slackbuilds-users] Wrong MD5SUM for libreoffice-6.2.8.2-srcs.tar.xz at SourceForge? Message-ID: Hi, When downloading: http://sourceforge.net/projects/slackbuildsdirectlinks/files/LibreOffice/libreoffice-6.2.8.2-srcs.tar.xz I get the following md5sum: b5d5e57832056d8a5625b1d5dc3aa024 whereas .info states the following one: 1fcf52003e0d3c514caf8bfd40b6b88e Where lies the problem? Thanks in advance! P.S. Bcc'd maintainer. -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Mon Nov 25 19:49:43 2019 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 25 Nov 2019 20:49:43 +0100 Subject: [Slackbuilds-users] Trouble downloading from sourceforge.net In-Reply-To: References: Message-ID: Il giorno lun 25 nov 2019 alle ore 20:35 Peter Dambier ha scritto: > > Hi, > > e.g. from pcmanfm Slackbuild I wanted to download > > "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz" > > After lots of lots of redirect wget gave up. > > Trying the homepage got me into an ants nest where stupid me signed up > for a newsletter in the 50th floor below ground but I still could not > get the source. > > Google finally found it at: > > "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz" > > Again lots of lots of redirect and finally I get it from > > "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz" > > The redirects for both URLs looked the same. That is why I dont think > there is a need to change the download in the SlackBuild. > > Horses tend to drop their manure everywhere but I remember there > were quite a lot of downloads that did not succeed. pcmanfm actually was > the first one I finally made to download after all obstacles. > > md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. > > and it runs on Slackware Current 32 Bit. > > Sorry for the rant but I had to vent because if I had blown my top like > SpaceX did with Starship MK 1, I would look really silly :) maybe is a temporary problem at SourceForge, it happens sometimes. remember that there's a backup hosting for the tarballs linked here at SBo, sbosrcarch (courtesy of Urchlay and hosted by Tadgy) http://slackware.uk/sbosrcarch/ From peter at peter-dambier.de Mon Nov 25 19:54:35 2019 From: peter at peter-dambier.de (Peter Dambier) Date: Mon, 25 Nov 2019 20:54:35 +0100 Subject: [Slackbuilds-users] Trouble downloading from sourceforge.net In-Reply-To: References: Message-ID: On 11/25/2019 08:49 PM, Matteo Bernardini wrote: > Il giorno lun 25 nov 2019 alle ore 20:35 Peter Dambier > ha scritto: >> >> Hi, >> >> e.g. from pcmanfm Slackbuild I wanted to download >> >> "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz" >> >> After lots of lots of redirect wget gave up. >> >> Trying the homepage got me into an ants nest where stupid me signed up >> for a newsletter in the 50th floor below ground but I still could not >> get the source. >> >> Google finally found it at: >> >> "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz" >> >> Again lots of lots of redirect and finally I get it from >> >> "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz" >> >> The redirects for both URLs looked the same. That is why I dont think >> there is a need to change the download in the SlackBuild. >> >> Horses tend to drop their manure everywhere but I remember there >> were quite a lot of downloads that did not succeed. pcmanfm actually was >> the first one I finally made to download after all obstacles. >> >> md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. >> >> and it runs on Slackware Current 32 Bit. >> >> Sorry for the rant but I had to vent because if I had blown my top like >> SpaceX did with Starship MK 1, I would look really silly :) > > maybe is a temporary problem at SourceForge, it happens sometimes. > > remember that there's a backup hosting for the tarballs linked here at > SBo, sbosrcarch (courtesy of Urchlay and hosted by Tadgy) > > http://slackware.uk/sbosrcarch/ > _______________________________________________ > 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/ > Thankyou Matteo, That is good news. Cheers Peter -- Peter and Karin Dambier Adalbert-Stifter-Strasse 17 D-69509 Moerlenbach +49(6209)280-3030 (VoIP: GGEW) +49(6252)750-308 (VoIP: sipgate.de) mail: peter at peter-dambier.de From jdashiel at panix.com Mon Nov 25 20:51:30 2019 From: jdashiel at panix.com (Jude DaShiell) Date: Mon, 25 Nov 2019 15:51:30 -0500 Subject: [Slackbuilds-users] Trouble downloading from sourceforge.net In-Reply-To: References: Message-ID: On Mon, 25 Nov 2019, Matteo Bernardini wrote: > Date: Mon, 25 Nov 2019 14:49:43 > From: Matteo Bernardini > Reply-To: SlackBuilds.org Users List > To: SlackBuilds.org Users List > Subject: Re: [Slackbuilds-users] Trouble downloading from sourceforge.net > > Il giorno lun 25 nov 2019 alle ore 20:35 Peter Dambier > ha scritto: > > > > Hi, > > > > e.g. from pcmanfm Slackbuild I wanted to download > > > > "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz" > > > > After lots of lots of redirect wget gave up. > > > > Trying the homepage got me into an ants nest where stupid me signed up > > for a newsletter in the 50th floor below ground but I still could not > > get the source. > > > > Google finally found it at: > > > > "https://downloads.sourceforge.net/pcmanfm/pcmanfm-1.3.1.tar.xz" > > > > Again lots of lots of redirect and finally I get it from > > > > "https://netcologne.dl.sourceforge.net/project/pcmanfm/PCManFM%20%2B%20Libfm%20%28tarball%20release%29/PCManFM/pcmanfm-1.3.1.tar.xz" > > > > The redirects for both URLs looked the same. That is why I dont think > > there is a need to change the download in the SlackBuild. > > > > Horses tend to drop their manure everywhere but I remember there > > were quite a lot of downloads that did not succeed. pcmanfm actually was > > the first one I finally made to download after all obstacles. > > > > md5sum matched. pcmanfm-1.3.1-i586-1_SBo.tgz created. > > > > and it runs on Slackware Current 32 Bit. > > > > Sorry for the rant but I had to vent because if I had blown my top like > > SpaceX did with Starship MK 1, I would look really silly :) > > maybe is a temporary problem at SourceForge, it happens sometimes. > > remember that there's a backup hosting for the tarballs linked here at > SBo, sbosrcarch (courtesy of Urchlay and hosted by Tadgy) > > http://slackware.uk/sbosrcarch/ > _______________________________________________ > 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/ > The line I have in my sf.sh takes care of that: wget -bc $1 --max-redirect=10000 --trust-server-names Once that's started you check on it these ways. First wc -l wget-log if it's larger than 6 lines the download is probably working. Then every so often: grep -i saved wget-log Nothing back from grep the download is still in progress. When saved appears you get the file information including the correct name of the file on your system. That's what that --trust-server-names switch does for you. I hope this helps. > -- From poprocks at gmail.com Mon Nov 25 21:37:34 2019 From: poprocks at gmail.com (Logan Rathbone) Date: Mon, 25 Nov 2019 16:37:34 -0500 Subject: [Slackbuilds-users] Trouble downloading from sourceforge.net In-Reply-To: References: Message-ID: <20191125213734.GA22660@darkstar.example.net> On Mon, Nov 25, 2019 at 08:36:06PM +0100, Peter Dambier wrote: > Hi, > > e.g. from pcmanfm Slackbuild I wanted to download > > "https://downloads.sf.net/pcmanfm/pcmanfm-1.3.1.tar.xz" > > After lots of lots of redirect wget gave up. > [snip] Not sure - but incidentally I was having similar problems with github yesterday. 500 errors abound. Coincidence? From chris.willing at linux.com Mon Nov 25 21:58:09 2019 From: chris.willing at linux.com (Christoph Willing) Date: Tue, 26 Nov 2019 07:58:09 +1000 Subject: [Slackbuilds-users] Wrong MD5SUM for libreoffice-6.2.8.2-srcs.tar.xz at SourceForge? In-Reply-To: References: Message-ID: On 26/11/19 5:41 am, Andrzej Telszewski wrote: > Hi, > > When downloading: > http://sourceforge.net/projects/slackbuildsdirectlinks/files/LibreOffice/libreoffice-6.2.8.2-srcs.tar.xz > > > I get the following md5sum: > b5d5e57832056d8a5625b1d5dc3aa024 > > whereas .info states the following one: > 1fcf52003e0d3c514caf8bfd40b6b88e > > > Where lies the problem? > Maintainer error. It should be: b5d5e57832056d8a5625b1d5dc3aa024 and will be fixed soon. Thanks, chris From ts at websafe.pl Tue Nov 26 20:07:07 2019 From: ts at websafe.pl (Thomas Szteliga) Date: Tue, 26 Nov 2019 20:07:07 +0000 Subject: [Slackbuilds-users] nsca-ng - download mirror down? Message-ID: <96fe167c-b9c5-d227-70d6-a7641e997292@websafe.pl> Hello, there's a problem with http://www.nsca-ng.org/ Maybe https://github.com/weiss/nsca-ng will be a better source? -- Thomas Szteliga From slackbuilds at schoepfer.info Thu Nov 28 08:42:22 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Thu, 28 Nov 2019 09:42:22 +0100 Subject: [Slackbuilds-users] Jack policy In-Reply-To: <2164080.GSHLQbKFr4@beast> References: <2164080.GSHLQbKFr4@beast> Message-ID: > I've been struggling with this on SBo for years. Last time I asked this list, > the consensus was to just make a note in the README that *either* jack-audio- > blah or jack2 were required. That was my thought too, but willy rejected that on my last builds by putting jack2 in REQUIRES. > Even so, > it's nearly 2020, and I feel like "most" users could safely default to jack2. The previous posts showed that there is no better or discontinued jack, to make a dependeing build work both seem to do the job. For now, i'll change my builds to jack-audio-connection-kit, maybe the last two other builds from other maintainer follow. Johannes From mufti11 at web.de Thu Nov 28 12:27:00 2019 From: mufti11 at web.de (J. Scheurich) Date: Thu, 28 Nov 2019 13:27:00 +0100 Subject: [Slackbuilds-users] Unable to send a submission for white_dune Message-ID: <7be42d0c-3adc-73f5-3c2d-3c0dc50ea224@web.de> *Hi,* *Unfortunatly i lost my mail archive, so i can not cancel the last submission 8-(* *Now i get * *https://slackbuilds.org/process_submit/* ** *| Upload Results * *|** * *| File exists; a submission by the name 'white_dune' is already pending approval.* The submitted file is available at *https://wdune.ourproject.org/examples/white_dune.tar.gz * *so long* *MUFTI * -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Nov 28 16:44:47 2019 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 28 Nov 2019 23:44:47 +0700 Subject: [Slackbuilds-users] Unable to send a submission for white_dune In-Reply-To: <7be42d0c-3adc-73f5-3c2d-3c0dc50ea224@web.de> References: <7be42d0c-3adc-73f5-3c2d-3c0dc50ea224@web.de> Message-ID: <68a8c56e-89ad-c84e-ad84-3fda01e342e9@slackbuilds.org> > *Unfortunatly i lost my mail archive, so i can not cancel the last > submission 8-(* > > *Now i get > * > > *https://slackbuilds.org/process_submit/* > > ** > > *| Upload Results > * > > *|** > * > > *| File exists; a submission by the name 'white_dune' is already pending > approval.* > > The submitted file is available at > > *https://wdune.ourproject.org/examples/white_dune.tar.gz You already have submission on white_dune -- 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 mario at slackware.hr Thu Nov 28 23:01:31 2019 From: mario at slackware.hr (Mario) Date: Fri, 29 Nov 2019 00:01:31 +0100 Subject: [Slackbuilds-users] nsca-ng - download mirror down? In-Reply-To: <96fe167c-b9c5-d227-70d6-a7641e997292@websafe.pl> References: <96fe167c-b9c5-d227-70d6-a7641e997292@websafe.pl> Message-ID: On 11/26/19 9:07 PM, Thomas Szteliga wrote: > Hello, > > there's a problem with http://www.nsca-ng.org/ > Maybe https://github.com/weiss/nsca-ng will be a better source? > Fixed in my branch. -- Mario From didier at slint.fr Thu Nov 28 23:34:01 2019 From: didier at slint.fr (Didier Spaier) Date: Fri, 29 Nov 2019 00:34:01 +0100 Subject: [Slackbuilds-users] python3 version Message-ID: Hello, I have currently Python3 3.59 installed and around 45 packages depending on it. Any caveat upgrading to version 3.7.2 (or even 3.8.0, currently the latest)? Should I rebuild all dependent packages to play it safe? Or is there an easy to apply test to know which would need a rebuild? Or maybe a list of SlackBuilds available @ Sbo who would need a rebuild? Best regards and happy Thanksgiving to whoever in concern. Didier From didier at slint.fr Thu Nov 28 23:35:50 2019 From: didier at slint.fr (Didier Spaier) Date: Fri, 29 Nov 2019 00:35:50 +0100 Subject: [Slackbuilds-users] python3 version In-Reply-To: References: Message-ID: Le 29/11/19 ? 00:34, Didier Spaier a ?crit?: > I have currently Python3 3.59 installed and around 45 packages depending on it. Please read version 3.5.9, not 3.59 From slackbuilds at jaxartes.net Thu Nov 28 23:41:15 2019 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Thu, 28 Nov 2019 23:41:15 +0000 Subject: [Slackbuilds-users] python3 version In-Reply-To: References: Message-ID: <2EC6C657-D9BC-43D3-BB40-91A84E135E55@jaxartes.net> You'll need to rebuild all your Python packages after upgrading since they'll be installed in /usr/lib/python3.5/... that the newer version of Python won't be able to find. Otherwise I don't expect you'll have any issues. You can grep all your packages for "python3.5" as an easy test of what needs rebuilding after your upgrade. Best, Ben On November 28, 2019 11:34:01 PM UTC, Didier Spaier wrote: >Hello, > >I have currently Python3 3.59 installed and around 45 packages >depending on it. > >Any caveat upgrading to version 3.7.2 (or even 3.8.0, currently the >latest)? > >Should I rebuild all dependent packages to play it safe? > >Or is there an easy to apply test to know which would need a rebuild? > >Or maybe a list of SlackBuilds available @ Sbo who would need a >rebuild? > >Best regards and happy Thanksgiving to whoever in concern. > >Didier >_______________________________________________ >SlackBuilds-users mailing list >SlackBuilds-users at slackbuilds.org >https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >FAQ - https://slackbuilds.org/faq/ -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Fri Nov 29 00:00:24 2019 From: didier at slint.fr (Didier Spaier) Date: Fri, 29 Nov 2019 01:00:24 +0100 Subject: [Slackbuilds-users] python3 version In-Reply-To: <2EC6C657-D9BC-43D3-BB40-91A84E135E55@jaxartes.net> References: <2EC6C657-D9BC-43D3-BB40-91A84E135E55@jaxartes.net> Message-ID: <79750a76-3840-fb7d-c367-65cfe7eb3fa3@slint.fr> Thanks for your answer Ben. My old buddies grep and find will help me again. Best, Didier Le 29/11/19 ? 00:41, Benjamin Trigona-Harany a ?crit?: > You'll need to rebuild all your Python packages after upgrading since they'll be installed in /usr/lib/python3.5/... that the newer version of Python won't be able to find. Otherwise I don't expect you'll have any issues. > > You can grep all your packages for "python3.5" as an easy test of what needs rebuilding after your upgrade. > > Best, Ben > > On November 28, 2019 11:34:01 PM UTC, Didier Spaier wrote: > > Hello, > > I have currently Python3 3.59 installed and around 45 packages depending on it. > > Any caveat upgrading to version 3.7.2 (or even 3.8.0, currently the latest)? > > Should I rebuild all dependent packages to play it safe? > > Or is there an easy to apply test to know which would need a rebuild? > > Or maybe a list of SlackBuilds available @ Sbo who would need a rebuild? > > Best regards and happy Thanksgiving to whoever in concern. > > Didier From slackbuilds at schoepfer.info Fri Nov 29 03:01:21 2019 From: slackbuilds at schoepfer.info (Franzen) Date: Fri, 29 Nov 2019 04:01:21 +0100 Subject: [Slackbuilds-users] Unable to send a submission for white_dune In-Reply-To: <68a8c56e-89ad-c84e-ad84-3fda01e342e9@slackbuilds.org> References: <7be42d0c-3adc-73f5-3c2d-3c0dc50ea224@web.de> <68a8c56e-89ad-c84e-ad84-3fda01e342e9@slackbuilds.org> Message-ID: <40a7404fa34d7a417db8f6e6c01369fc@schoepfer.info> On 2019-11-28 17:44, Willy Sudiarto Raharjo wrote: >> *Unfortunatly i lost my mail archive, so i can not cancel the last >> submission 8-(* >> >> *Now i get >> * >> >> *https://slackbuilds.org/process_submit/* >> >> ** >> >> *| Upload Results >> * >> >> *|** >> * >> >> *| File exists; a submission by the name 'white_dune' is already >> pending >> approval.* >> >> The submitted file is available at >> >> *https://wdune.ourproject.org/examples/white_dune.tar.gz > > You already have submission on white_dune I think Mufti is aware of that, he wanted to cancel that, to make another submission on that build. From fernando.lopezjr at gmail.com Fri Nov 29 06:17:29 2019 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Thu, 28 Nov 2019 23:17:29 -0700 Subject: [Slackbuilds-users] help trying to compile FreeRouting. Message-ID: I am trying to compile this https://github.com/nikropht/FreeRouting you need this jar: https://sourceforge.net/projects/jnlp/files/netx/0.5/ you can download the whole thing here: https://www.dropbox.com/s/unusqyttngxap2h/FreeRouting-master_SBO.tar.xz?dl=0 any help is appreciated. thank you. bash-5.0$ javac -version javac 1.8.0_221 bash-5.0$ export CLASSPATH="/home/usertmp/FreeRouting/FreeRouting-master/netx-0.5.jar;/home/usertmp/FreeRouting/FreeRouting-master/rules/;/home/usertmp/FreeRouting/FreeRouting-master/library/;/home/usertmp/FreeRouting/FreeRouting-master/interactive/;/home/usertmp/FreeRouting/FreeRouting-master/gui/;/home/usertmp/FreeRouting/FreeRouting-master/geometry/;/home/usertmp/FreeRouting/FreeRouting-master/geometry/planar/;/home/usertmp/FreeRouting/FreeRouting-master/designformats/;/home/usertmp/FreeRouting/FreeRouting-master/datastructures/;/home/usertmp/FreeRouting/FreeRouting-master/boardgraphics/;/home/usertmp/FreeRouting/FreeRouting-master/autoroute/;/home/usertmp/FreeRouting/FreeRouting-master/board/;/home/usertmp/FreeRouting/FreeRouting-master/tests/;" cd gui/ bash-5.0$ javac MainApplication.java bash-5.0$ javac MainApplication.java MainApplication.java:23: error: package board does not exist import board.TestLevel; ^ MainApplication.java:319: error: cannot find symbol static private BoardFrame create_board_frame(DesignFile p_design_file, javax.swing.JTextField p_message_field, ^ symbol: class DesignFile location: class MainApplication MainApplication.java:320: error: package BoardFrame does not exist BoardFrame.Option p_option, boolean p_is_test_version, java.util.Locale p_locale) ^ MainApplication.java:319: error: cannot find symbol static private BoardFrame create_board_frame(DesignFile p_design_file, javax.swing.JTextField p_message_field, ^ symbol: class BoardFrame location: class MainApplication MainApplication.java:375: error: cannot find symbol private final WindowNetSamples window_net_demonstrations; ^ symbol: class WindowNetSamples location: class MainApplication MainApplication.java:379: error: cannot find symbol private final WindowNetSamples window_net_sample_designs; ^ symbol: class WindowNetSamples location: class MainApplication MainApplication.java:381: error: cannot find symbol private java.util.Collection board_frames = new java.util.LinkedList(); ^ symbol: class BoardFrame location: class MainApplication MainApplication.java:386: error: cannot find symbol private static final TestLevel DEBUG_LEVEL = TestLevel.CRITICAL_DEBUGGING_OUTPUT; ^ symbol: class TestLevel location: class MainApplication MainApplication.java:391: error: cannot find symbol public BoardFrameWindowListener(BoardFrame p_board_frame) ^ symbol: class BoardFrame location: class MainApplication.BoardFrameWindowListener MainApplication.java:406: error: cannot find symbol private BoardFrame board_frame; ^ symbol: class BoardFrame location: class MainApplication.BoardFrameWindowListener MainApplication.java:95: error: package BoardFrame does not exist BoardFrame.Option board_option; ^ MainApplication.java:98: error: package BoardFrame does not exist board_option = BoardFrame.Option.SESSION_FILE; ^ MainApplication.java:102: error: package BoardFrame does not exist board_option = BoardFrame.Option.SINGLE_FRAME; ^ MainApplication.java:104: error: cannot find symbol DesignFile design_file = DesignFile.get_instance(design_file_name, false); ^ symbol: class DesignFile location: class MainApplication MainApplication.java:104: error: cannot find symbol DesignFile design_file = DesignFile.get_instance(design_file_name, false); ^ symbol: variable DesignFile location: class MainApplication MainApplication.java:113: error: cannot find symbol WindowMessage welcome_window = WindowMessage.show(message); ^ symbol: class WindowMessage location: class MainApplication MainApplication.java:113: error: cannot find symbol WindowMessage welcome_window = WindowMessage.show(message); ^ symbol: variable WindowMessage location: class MainApplication MainApplication.java:114: error: cannot find symbol final BoardFrame new_frame = ^ symbol: class BoardFrame location: class MainApplication MainApplication.java:164: error: cannot find symbol this.window_net_demonstrations = new WindowNetDemonstrations(p_current_locale); ^ symbol: class WindowNetDemonstrations location: class MainApplication MainApplication.java:167: error: cannot find symbol this.window_net_sample_designs = new WindowNetSampleDesigns(p_current_locale); ^ symbol: class WindowNetSampleDesigns location: class MainApplication MainApplication.java:258: error: cannot find symbol DesignFile design_file = DesignFile.open_dialog(this.is_webstart, this.design_dir_name); ^ symbol: class DesignFile location: class MainApplication MainApplication.java:258: error: cannot find symbol DesignFile design_file = DesignFile.open_dialog(this.is_webstart, this.design_dir_name); ^ symbol: variable DesignFile location: class MainApplication MainApplication.java:266: error: package BoardFrame does not exist BoardFrame.Option option; ^ MainApplication.java:269: error: package BoardFrame does not exist option = BoardFrame.Option.WEBSTART; ^ MainApplication.java:273: error: package BoardFrame does not exist option = BoardFrame.Option.FROM_START_MENU; ^ MainApplication.java:277: error: cannot find symbol WindowMessage welcome_window = WindowMessage.show(message); ^ symbol: class WindowMessage location: class MainApplication MainApplication.java:277: error: cannot find symbol WindowMessage welcome_window = WindowMessage.show(message); ^ symbol: variable WindowMessage location: class MainApplication MainApplication.java:279: error: cannot find symbol BoardFrame new_frame = ^ symbol: class BoardFrame location: class MainApplication MainApplication.java:304: error: cannot find symbol boolean file_deleted = WebStart.delete_files(BoardFrame.GUI_DEFAULTS_FILE_NAME, resources.getString("confirm_delete")); ^ symbol: variable BoardFrame location: class MainApplication MainApplication.java:304: error: cannot find symbol boolean file_deleted = WebStart.delete_files(BoardFrame.GUI_DEFAULTS_FILE_NAME, resources.getString("confirm_delete")); ^ symbol: variable WebStart location: class MainApplication MainApplication.java:335: error: cannot find symbol TestLevel test_level; ^ symbol: class TestLevel location: class MainApplication MainApplication.java:386: error: cannot find symbol private static final TestLevel DEBUG_LEVEL = TestLevel.CRITICAL_DEBUGGING_OUTPUT; ^ symbol: variable TestLevel location: class MainApplication MainApplication.java:342: error: cannot find symbol test_level = TestLevel.RELEASE_VERSION; ^ symbol: variable TestLevel location: class MainApplication MainApplication.java:344: error: cannot find symbol BoardFrame new_frame = new BoardFrame(p_design_file, p_option, test_level, p_locale, !p_is_test_version); ^ symbol: class BoardFrame location: class MainApplication MainApplication.java:344: error: cannot find symbol BoardFrame new_frame = new BoardFrame(p_design_file, p_option, test_level, p_locale, !p_is_test_version); ^ symbol: class BoardFrame location: class MainApplication MainApplication.java:359: error: package BoardFrame does not exist new_frame.board_panel.board_handling, p_option == BoardFrame.Option.WEBSTART, ^ MainApplication.java:358: error: cannot find symbol DesignFile.read_rules_file(name_parts[0], p_design_file.get_parent(), ^ symbol: variable DesignFile location: class MainApplication MainApplication.java:381: error: cannot find symbol private java.util.Collection board_frames = new java.util.LinkedList(); ^ symbol: class BoardFrame location: class MainApplication 38 errors -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mufti11 at web.de Fri Nov 29 15:31:52 2019 From: mufti11 at web.de (J. Scheurich) Date: Fri, 29 Nov 2019 16:31:52 +0100 Subject: [Slackbuilds-users] Fwd: Unable to send a submission for white_dune In-Reply-To: <7be42d0c-3adc-73f5-3c2d-3c0dc50ea224@web.de> References: <7be42d0c-3adc-73f5-3c2d-3c0dc50ea224@web.de> Message-ID: <3c362977-1de3-91f5-7285-b76cfbba9af4@web.de> *Hi, | Unfortunatly i lost my mail archive, so i can not cancel the last submission 8-( | | Now i get | | https://slackbuilds.org/process_submit/ | || Upload Results | || || File exists; a submission by the name 'white_dune' is already pending approval. | | The submitted file is available at | |https://wdune.ourproject.org/examples/white_dune.tar.gz I found bugs in white_dune, so please ignore the submitted file. I will upload a new version after the bufix, if the the way is free. so long MUFTI* From kingbeowulf at gmail.com Fri Nov 29 20:13:03 2019 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 29 Nov 2019 12:13:03 -0800 Subject: [Slackbuilds-users] ANNOUNCE: new nvidia buildscripts Message-ID: Hello all, For those that use the SBo scripts for Nvidia, new buildscripts for 440.36 are now in pending. These scripts work on both 14.2 (stable) and 15.0 (current); for current you will need kernel-5.4.0 from /testing in order to successfully compile the kernel module interface. Hightlights: 1. libglvnd only. 2. nvidia-switch removed - no longer needed. 3. *.la removed 4.nouveau blacklist still required. Please note, use "CURRENT=yes ./nvidia-driver" when on 15.0. This is to keep Nvidia installer from stomping on the existing libglvnd package. As always, it works here (so far). On one of my boxes (GTX 1060 w/ 4K monitor, GTX660 w/ 2x 1080p monitors), I experienced occasional stutters running Borderlands 2 (native, Steam), but this could just be my weird setup. The current Ryzen box completed several phoronix test suite GPU benchmarks successfully (GTX 950, hoping for a AMD Navi card soon). Let me know if you catch any bugs. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: