From willysr at slackbuilds.org Sat Dec 1 00:44:15 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 Dec 2018 07:44:15 +0700 Subject: [Slackbuilds-users] Updates - 20181201.1 Message-ID: <968afef9-7c96-7f29-7376-5e65c79847af@slackbuilds.org> Sat Dec 1 00:28:43 UTC 2018 academic/calc: Update to 2.12.7.2 academic/isoelectric-point: Update homepage and download. academic/novocraft: Updated for version 3.09.01. academic/pspp: Updated for version 1.2.0. academic/pyCRAC: Updated for version 1.3.3. academic/pyfits: Update homepage. academic/pysam: Updated for version 0.15.1. audio/mpdscribble: Update homepage and download. dekstop/catfish: Update README desktop/LX-Colors-Revival: Update download URLs, change SlackBuild. desktop/LX-Colors-themes: Update download URLs, change SlackBuild. desktop/dwm: Use local config.h. desktop/jgmenu: Updated for version 1.5. desktop/jwm: Update homepage. desktop/nitrogen: Update homepage. desktop/py3status: Updated for version 3.14. development/alex: Fix SlackBuild. development/diffoscope: Updated for version 106. development/hopper: Updated for version 4.4.8. development/mozjs: Remove build.log development/radare2: Updated for version 3.1.0. development/rtags: Updated for version 2.21. development/trf: Update homepage. development/zulu-openjdk7: Updated for version 7u201. development/zulu-openjdk8: Updated for version 8u192. development/zulu-openjdk9: Updated for version 9u07. games/beetle-psx-libretro: Updated for version 2018.11.26_a081f34. games/lutris: Updated for version 0.4.23. games/mangband: Switch homepage and download to https. gis/Fiona: Updated for version 1.8.3. gis/geos: Updated for version 3.7.1. gis/pktools: Updated for version 2.6.7.6. graphics/GraphicsMagick: Fix perl module. libraries/OpenAL: Switch homepage and download to https. libraries/SFGUI: Update homepage. libraries/alure: Switch homepage and download to https. libraries/botocore: Updated for version 1.12.57. libraries/gazebo: Fix build with tinyxml2-7.0.1. libraries/libtorrent-rasterbar: Update to 1.1.11 libraries/libwebp: Updated for version 1.0.1. libraries/libxlsxwriter: Update 0.8.4 libraries/live555: Updated for version 2018.11.26 libraries/lua-MessagePack: Update homepage. libraries/mujs: Fixed download link. libraries/netcdf: Updated for version 4.6.2. libraries/ois: Fix tarball handling. libraries/opencv: Updated for version 3.4.4 libraries/php-redis: Updated for version 4.2.0. libraries/spread-sheet-widget: Added (GTK+ Library). libraries/tDOM: Update homepage. misc/portecle: Updated for version 1.11. multimedia/ccxstream: Switch homepage to archive.org. multimedia/plexmediaserver: Updated for v. 1.14.0.5470_9d51fdfaa. network/Pafy: Update homepage. network/aircrack-ng: Updated for version 1.4 + new maintainer. network/awscli: Updated for version 1.16.67. network/geomyidae: Update to v0.34 network/httpie: Updated for version 1.0.2. network/linphone: Fixed deps. network/memcached-init: Update homepage. network/mps-youtube: Update homepage. network/mps: Switch homepage to archive.org. network/opera-developer: Updated for version 59.0.3154.0. network/opera: Updated for version 57.0.3098.76. network/pidgin-privacy-please: Update homepage. network/qbittorrent-qt5: Update to 4.1.4 network/qutebrowser: Update to 1.5.2 network/rejik: Switch homepage and download to https. network/rspamd: Updated for version 1.8.2. network/signal-desktop: Updated for version 1.18.1. network/swaks: Updated for version 20181104.0. network/teamviewer: Fix download. network/twitter: Switch homepage to https. network/w3m: Update to 0.5.3_34 network/wireshark: Updated for version 2.6.5. network/wmget: Update homepage and download. network/youtube-dl: Updated for version 2018.11.23. office/smoffice2018: Updated for version 2018_942. office/texstudio: Updated for version 2.12.12 perl/perl-CPAN-Perl-Releases: Updated for version 3.84. perl/perl-Mojolicious: Updated for version 8.07. python/Flask-Compress: Update homepage. python/Flask-Mail: Update homepage, fix readme. python/colorama: Updated for version 0.3.9. python/euca2ools: Update homepage. python/git-fame: Updated for version 1.6.0. python/pycryptodome: Updated for version 3.7.2. python/python-autobahn: Updated for version 18.11.1. python/python-certifi: Updated for version 2018.11.29. python/python-keyring: Updated for version 17.0.0. python/python-libsass: Updated for version 0.16.1. python/python-requests: Updated for version 2.20.1. python/python3-Pygments: Updated for version 2.3.0. python/python3-astroid: Updated for version 2.1.0. python/python3-ipython: Updated for version 7.2.0. python/python3-pylint: Updated for version 2.2.0. python/ruffus: Updated for version 2.8.1. python/scikit-learn: Updated for version 0.20.1. ruby/ruby-faraday: Updated for version 0.15.4. ruby/rubygem-mustache: Updated for version 1.1.0. ruby/rubygem-ronn: Fix manpage installation. ruby/rubygem-trollop: Update homepage. system/alacritty: Include upstream patch for crates.io winpty-sys. system/ansible: Updated for version 2.7.4. system/dvdisaster: Update homepage. system/dynamips: Update homepage. system/epson-inkjet-printer-escpr2: Updated for version 1.0.27. system/fira-fonts: Updated for version 4.301. system/inxi: Updated for version 3.0.27. system/jq: Fix MD5SUM. system/kbfs: Updated for version 2.11.0_20181127185939. system/keybase: Updated for version 2.10.1. system/lbench: Updated for version 3.7. system/lomoco: Switch homepage to archive.org. system/luckybackup: Updated for version 0.5.0. system/maxcso: Added (Fast cso compressor). system/nano-syntax-highlighting: Updated for version 20180827. system/openrc-services: Updated for version 20181107 + SYSCONFDIR changed. system/openrc: Updated for version 0.39.2 + SYSCONFDIR changed. system/phoronix-test-suite: Updated for version 8.4.0. system/pstate-frequency: Updated for version 3.10.2. system/qtfm: Updated for version 6.1.4. system/sboui: Updated for version 2.0. system/targetcli-fb: Updated for version 2.1.fb49 + new maintainer. system/telegraf: Updated for version 1.9.0. system/usermin: Updated for version 1.750. system/vagrant: Updated for version 2.2.2. system/webmin: Updated for version 1.900. +--------------------------+ -- 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 slackalaxy at gmail.com Sun Dec 2 21:41:59 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Sun, 2 Dec 2018 23:41:59 +0200 Subject: [Slackbuilds-users] calibre does not start Message-ID: hi all, calibre does not start. It shows this in the terminal: Failed to run pipe worker with command: from calibre.utils.ipc.pool import run_main, worker_main; run_main(worker_main) Traceback (most recent call last): File "/usr/bin/calibre-parallel", line 20, in sys.exit(main()) File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 180, in main exec (sys.argv[-1]) File "", line 1, in File "/usr/lib64/calibre/calibre/utils/ipc/pool.py", line 392, in run_main with closing(Client(address, authkey=key)) as conn: File "/usr/lib64/python2.7/multiprocessing/connection.py", line 169, in Client c = SocketClient(address) File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, in SocketClient s.connect(address) File "/usr/lib64/python2.7/socket.py", line 228, in meth return getattr(self._sock,name)(*args) socket.error: [Errno 111] Connection refused regards, Petar From flinchx at protonmail.com Mon Dec 3 06:02:16 2018 From: flinchx at protonmail.com (flinchx) Date: Mon, 03 Dec 2018 06:02:16 +0000 Subject: [Slackbuilds-users] calibre does not start In-Reply-To: References: Message-ID: I recall seeing the same traceback right after the big qt5 update and privately emailing the calibre maintainer about it. The problem was with python2-sip. What fixed calibre for me was to rebuild python2-sip after a fix was pushed (I believe it was this one https://git.slackbuilds.org/slackbuilds/commit/python/python2-sip?h=14.2&id=fa749a3a4df86ad32c6314cd03fc3793e830d787), then rebuild PyQt5, and then rebuild calibre. ??????? Original Message ??????? On Sunday, December 2, 2018 9:40 PM, Petar Petrov wrote: > hi all, > > calibre does not start. It shows this in the terminal: > > Failed to run pipe worker with command: from calibre.utils.ipc.pool > import run_main, worker_main; run_main(worker_main) > Traceback (most recent call last): > File "/usr/bin/calibre-parallel", line 20, in > > sys.exit(main()) > > > File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 180, in main > exec (sys.argv[-1]) > File "", line 1, in > File "/usr/lib64/calibre/calibre/utils/ipc/pool.py", line 392, in run_main > with closing(Client(address, authkey=key)) as conn: > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 169, in Client > c = SocketClient(address) > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, > in SocketClient > s.connect(address) > File "/usr/lib64/python2.7/socket.py", line 228, in meth > return getattr(self._sock,name)(*args) > socket.error: [Errno 111] Connection refused > > regards, > > Petar From slackbuilds at jaxartes.net Tue Dec 4 01:09:43 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Mon, 3 Dec 2018 17:09:43 -0800 Subject: [Slackbuilds-users] possible matplotlib patch Message-ID: Hi Serban, I wonder if this small patch would make sense for libraries/matplotlib? I've been having an issue where the script fails silently shortly after setup.py is run. The following error is in SETUP.OUTPUT: Unable to access the X Display, is $DISPLAY set properly? After some trial and error, I've found that disabling wxagg in setup.cfg avoids the script needing access to X. I do have wxPython and wxGTK3 installed but this issue only crops up on one of my two Slackware laptops. The patch simply ensures that wxagg is disabled and I don't think there's any downside to doing this. Incidentally, I don't think SETUP.OUTPUT was meant to be added to the repo, although no harm from it being there. Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: wx.patch Type: text/x-patch Size: 548 bytes Desc: not available URL: From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Tue Dec 4 11:02:00 2018 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Tue, 4 Dec 2018 12:02:00 +0100 Subject: [Slackbuilds-users] possible matplotlib patch In-Reply-To: References: Message-ID: <287ddccf-b897-6329-f8d7-ec1c62575b78@skmail.ikp.physik.tu-darmstadt.de> On 12/4/18 2:09 AM, Benjamin Trigona-Harany wrote: > Hi Serban, > > I wonder if this small patch would make sense for libraries/matplotlib? I've been > having an issue where the script fails silently shortly after setup.py is run. > > The following error is in SETUP.OUTPUT: > Unable to access the X Display, is $DISPLAY set properly? > > After some trial and error, I've found that disabling wxagg in setup.cfg avoids > the script needing access to X. I do have wxPython and wxGTK3 installed but this > issue only crops up on one of my two Slackware laptops. The patch simply ensures > that wxagg is disabled and I don't think there's any downside to doing this. > > Incidentally, I don't think SETUP.OUTPUT was meant to be added to the repo, > although no harm from it being there. > Hi Benjamin, And thank you for investigating the issue, reporting it and preparing the patch. I'm not sure that disabling wxagg is always ok. I would put its disabling as an option for now and try to find out more about this issue. I'm puzzled! Why should there be any need for accessing X? Did you enable tests? Yes, SETUP.OUTPUT was intended just for me. I'll correct this. However, could you please send me a SETUP.OUTPUT containing the error. Best regards, Serban From slackalaxy at gmail.com Tue Dec 4 14:52:31 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Tue, 4 Dec 2018 16:52:31 +0200 Subject: [Slackbuilds-users] calibre does not start In-Reply-To: References: Message-ID: thanks, but recompiling these (to the latest version available, not that particular commit) did not make Calibre work. Any other ideas? What else should I recompile? -petar On Mon, 3 Dec 2018 at 08:02, flinchx via SlackBuilds-users wrote: > > I recall seeing the same traceback right after the big qt5 update and privately emailing the calibre maintainer about it. The problem was with python2-sip. What fixed calibre for me was to rebuild python2-sip after a fix was pushed (I believe it was this one https://git.slackbuilds.org/slackbuilds/commit/python/python2-sip?h=14.2&id=fa749a3a4df86ad32c6314cd03fc3793e830d787), then rebuild PyQt5, and then rebuild calibre. > > ??????? Original Message ??????? > On Sunday, December 2, 2018 9:40 PM, Petar Petrov wrote: > > > hi all, > > > > calibre does not start. It shows this in the terminal: > > > > Failed to run pipe worker with command: from calibre.utils.ipc.pool > > import run_main, worker_main; run_main(worker_main) > > Traceback (most recent call last): > > File "/usr/bin/calibre-parallel", line 20, in > > > > sys.exit(main()) > > > > > > File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 180, in main > > exec (sys.argv[-1]) > > File "", line 1, in > > File "/usr/lib64/calibre/calibre/utils/ipc/pool.py", line 392, in run_main > > with closing(Client(address, authkey=key)) as conn: > > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 169, in Client > > c = SocketClient(address) > > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, > > in SocketClient > > s.connect(address) > > File "/usr/lib64/python2.7/socket.py", line 228, in meth > > return getattr(self._sock,name)(*args) > > socket.error: [Errno 111] Connection refused > > > > regards, > > > > Petar > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From fellype at gmail.com Tue Dec 4 16:10:27 2018 From: fellype at gmail.com (Fellype) Date: Tue, 4 Dec 2018 14:10:27 -0200 Subject: [Slackbuilds-users] possible matplotlib patch In-Reply-To: References: Message-ID: Hi Benjamin, Are you using a 32-bit system? This silent fail occurred only on the machine I run Slackware 32-bits, and only for the 2.x matplotlib (1.x build fine). But I haven't had time to investigate the reason(s) of the fail. Fellype Em seg, 3 de dez de 2018 ?s 23:09, Benjamin Trigona-Harany < slackbuilds at jaxartes.net> escreveu: > Hi Serban, > > I wonder if this small patch would make sense for libraries/matplotlib? > I've been having an issue where the script fails silently shortly after > setup.py is run. > > The following error is in SETUP.OUTPUT: > Unable to access the X Display, is $DISPLAY set properly? > > After some trial and error, I've found that disabling wxagg in setup.cfg > avoids the script needing access to X. I do have wxPython and wxGTK3 > installed but this issue only crops up on one of my two Slackware > laptops. The patch simply ensures that wxagg is disabled and I don't > think there's any downside to doing this. > > Incidentally, I don't think SETUP.OUTPUT was meant to be added to the > repo, although no harm from it being there. > > Thanks! > _______________________________________________ > 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/ > > -- Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackbuilds at jaxartes.net Tue Dec 4 16:52:49 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 4 Dec 2018 08:52:49 -0800 Subject: [Slackbuilds-users] possible matplotlib patch In-Reply-To: <287ddccf-b897-6329-f8d7-ec1c62575b78@skmail.ikp.physik.tu-darmstadt.de> References: <287ddccf-b897-6329-f8d7-ec1c62575b78@skmail.ikp.physik.tu-darmstadt.de> Message-ID: <20b076ce-dc6f-24a9-33a2-a01e7fc95f2b@jaxartes.net> On 2018-12-04 3:02 a.m., Serban Udrea wrote: > > And thank you for investigating the issue, reporting it and preparing > the patch. I'm not sure that disabling wxagg is always ok. I would put > its disabling as an option for now and try to find out more about this > issue. Yeah I'm not sure if there are any drawbacks! After removing wxagg, matplotlib *seemed* to work just fine. > I'm puzzled! Why should there be any need for accessing X? Did you > enable tests? I didn't make any other changes. I assume it has something to do with other packages that I have installed. But wxPython and wxGTK3 are on both my Slackware current installs and only one shows this issue. I just realised that in my initial email, I forgot to say that this happened on *current* not 14.2, so feel free to ignore this request on that basis! > Yes, SETUP.OUTPUT was intended just for me. I'll correct this. However, > could you please send me a SETUP.OUTPUT containing the error. Attached. Thanks for looking at this! Ben -------------- next part -------------- ============================================================================ Edit setup.cfg to change the build options BUILDING MATPLOTLIB matplotlib: yes [2.2.3] python: yes [2.7.15 (default, Jun 17 2018, 22:57:51) [GCC 7.3.0]] platform: yes [linux2] REQUIRED DEPENDENCIES AND EXTENSIONS numpy: yes [version 1.14.3] install_requires: yes [all third-party python packages are present] libagg: yes [pkg-config information for 'libagg' could not be found. Using local copy.] freetype: yes [version 2.9.1] png: yes [version 1.6.35] qhull: yes [pkg-config information for 'libqhull' could not be found. Using local copy.] OPTIONAL SUBPACKAGES sample_data: yes [installing] toolkits: yes [installing] tests: no [skipping due to configuration] toolkits_tests: no [skipping due to configuration] OPTIONAL BACKEND EXTENSIONS macosx: no [Mac OS-X only] qt5agg: yes [installing, Qt: 5.11.0, PyQt: 5.10.1; PySide2 not found] qt4agg: yes [installing, Qt: 4.8.7, PyQt: 4.12.1; PySide not found] No protocol specified No protocol specified gtk3agg: yes [installing, version 3.1.24] No protocol specified No protocol specified No protocol specified /usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py:57: GtkWarning: could not open display warnings.warn(str(e), _gtk.Warning) No protocol specified gtk3cairo: yes [installing, version 3.1.24] gtkagg: yes [installing, Gtk: 2.24.32 pygtk: 2.24.0] tkagg: yes [installing; run-time loading from Python Tcl / Tk] Unable to access the X Display, is $DISPLAY set properly? From slackbuilds at jaxartes.net Tue Dec 4 16:55:18 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Tue, 4 Dec 2018 08:55:18 -0800 Subject: [Slackbuilds-users] possible matplotlib patch In-Reply-To: References: Message-ID: <341bd7fa-fc47-b374-b568-1d820acd41f8@jaxartes.net> On 2018-12-04 8:10 a.m., Fellype wrote: > Hi Benjamin, > > Are you using a 32-bit system? This silent fail occurred only on the > machine I run Slackware 32-bits, and only for the 2.x matplotlib (1.x > build fine). But I haven't had time to investigate the reason(s) of the > fail. Hi Fellype, all my Slackware installs are 64-bit. The matplotlib SlackBuild worked and one didn't, so it must be something else that is behind the problem I glad that I am not totally alone in running into the problem though! From kingbeowulf at gmail.com Thu Dec 6 01:10:06 2018 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 5 Dec 2018 17:10:06 -0800 Subject: [Slackbuilds-users] calibre does not start In-Reply-To: References: Message-ID: <3e729a5f-58cd-0e07-77b9-fcf95b9b65fb@gmail.com> On 12/2/18 1:41 PM, Petar Petrov wrote: > hi all, > > calibre does not start. It shows this in the terminal: > > Failed to run pipe worker with command: from calibre.utils.ipc.pool > import run_main, worker_main; run_main(worker_main) > Traceback (most recent call last): > File "/usr/bin/calibre-parallel", line 20, in > sys.exit(main()) > File "/usr/lib64/calibre/calibre/utils/ipc/worker.py", line 180, in main > exec (sys.argv[-1]) > File "", line 1, in > File "/usr/lib64/calibre/calibre/utils/ipc/pool.py", line 392, in run_main > with closing(Client(address, authkey=key)) as conn: > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 169, in Client > c = SocketClient(address) > File "/usr/lib64/python2.7/multiprocessing/connection.py", line 308, > in SocketClient > s.connect(address) > File "/usr/lib64/python2.7/socket.py", line 228, in meth > return getattr(self._sock,name)(*args) > socket.error: [Errno 111] Connection refused > > I recall vaguely an issue with a change in calibre's built in content server with the 3.30 series. I now use Alienbobs calibre package. I don't use PyQt5. Rather, qt5-5.9.6 and qt5-webkit-5.9.0 to get it to work. Make sure have qt5 and qt5-webkit built in the correct order, and libwep might be required now as well. Or do what I did a few months ago and throw my hands up and just use Alienbob's calibre package. The dep chain was enough to shorten my lifespan.... -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: From andrew.david.strong at gmail.com Thu Dec 6 01:21:48 2018 From: andrew.david.strong at gmail.com (andrew) Date: Thu, 6 Dec 2018 12:21:48 +1100 Subject: [Slackbuilds-users] calibre does not start In-Reply-To: References: Message-ID: <20181206012148.GA3635@ilium.andrews-corner.org> On Tue, Dec 04, 2018 at 04:52:31PM +0200, Petar Petrov wrote: > thanks, but recompiling these (to the latest version available, not > that particular commit) did not make Calibre work. Any other ideas? > What else should I recompile? > > -petar This binary repackaging script will at least get you the latest version of Calibre: https://raw.githubusercontent.com/duganchen/my_slackbuilds/master/calibre.SlackBuild Does not solve your compiling issue though... Andrew -- You think that's air you're breathing now? From lists at osh.id.au Thu Dec 6 01:42:27 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 05 Dec 2018 17:42:27 -0800 Subject: [Slackbuilds-users] borgbackup msgpack-python problem Message-ID: <1544060547.168982.1600403136.0A616524@webmail.messagingengine.com> I'm having trouble with borgbackup on 14.2_64. Here's the error message upon running borg init . > Traceback (most recent call last): > File "/usr/bin/borg", line 6, in > from pkg_resources import load_entry_point > File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", > line 3088, in > @_call_aside > File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", > line 3072, in _call_aside> f(*args, **kwargs) > File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", > line 3101, in _initialize_master_working_set> working_set = WorkingSet._build_master() > File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", > line 574, in _build_master> ws.require(__requires__) > File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", > line 892, in require> needed = self.resolve(parse_requirements(requirements)) > File "/usr/lib64/python3.6/site-packages/pkg_resources/__init__.py", > line 778, in resolve> raise DistributionNotFound(req, requirers) > pkg_resources.DistributionNotFound: The 'msgpack- > python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6' > distribution was not found and is required by borgbackup> I've tried uninstalling and reinstalling borgbackup and all dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so that should be ok? -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From serban.udrea at skmail.ikp.physik.tu-darmstadt.de Thu Dec 6 08:49:39 2018 From: serban.udrea at skmail.ikp.physik.tu-darmstadt.de (Serban Udrea) Date: Thu, 6 Dec 2018 09:49:39 +0100 Subject: [Slackbuilds-users] possible matplotlib patch In-Reply-To: References: Message-ID: On 12/4/18 5:10 PM, Fellype wrote: > Hi Benjamin, > > Are you using a 32-bit system? This silent fail occurred only on the machine I run > Slackware 32-bits, and only for the 2.x matplotlib (1.x build fine). But I haven't > had time to investigate the reason(s) of the fail. > ... Hi Fellype, I compiled the 2.x matplotlib without issues on my Slackware 32-bits system, thus I don't think that it really has to do with the word width. I need some more time to properly look into this. Best regards Serban From audrius at neutrino.lt Thu Dec 6 17:53:39 2018 From: audrius at neutrino.lt (Audrius =?utf-8?Q?Ka=C5=BEukauskas?=) Date: Thu, 6 Dec 2018 19:53:39 +0200 Subject: [Slackbuilds-users] borgbackup msgpack-python problem In-Reply-To: <1544060547.168982.1600403136.0A616524@webmail.messagingengine.com> References: <1544060547.168982.1600403136.0A616524@webmail.messagingengine.com> Message-ID: <20181206175339.GA2367@varna> On Wed, 2018-12-05 at 17:42:27 -0800, David O'Shaughnessy wrote: > I'm having trouble with borgbackup on 14.2_64. Here's the error message > upon running borg init . <...> > > pkg_resources.DistributionNotFound: The 'msgpack- > > python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6' > > distribution was not found and is required by borgbackup> > > I've tried uninstalling and reinstalling borgbackup and all > dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so > that should be ok? I was hit by this as well a week or two ago, but was too tired and annoyed to investigate the root of this issue, so what I've done was a stupid, yet effective workaround -- I commented out msgpack-python line in /usr/lib64/python3.6/site-packages/borgbackup-1.1.7-py3.6.egg-info/requires.txt file and things were functional again. But now I got curious and looked around a bit. Here's what I dug up: the problem here is that borgbackup requires msgpack-python while upstream of the latter switched its name to msgpack (without -python suffix). borgbackup devs are aware of this change and will fix it eventually (if they haven't already), but what we can do right now is add the following to borgbackup.SlackBuild somewhere before the line that calls 'python3 setup.py install': sed -i 's/msgpack-python/msgpack/' setup.py -- Audrius Ka?ukauskas From atelszewski at gmail.com Thu Dec 6 18:06:41 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Thu, 6 Dec 2018 19:06:41 +0100 Subject: [Slackbuilds-users] borgbackup msgpack-python problem In-Reply-To: <20181206175339.GA2367@varna> References: <1544060547.168982.1600403136.0A616524@webmail.messagingengine.com> <20181206175339.GA2367@varna> Message-ID: On 06/12/2018 18:53, Audrius Ka?ukauskas wrote: > On Wed, 2018-12-05 at 17:42:27 -0800, David O'Shaughnessy wrote: >> I'm having trouble with borgbackup on 14.2_64. Here's the error message >> upon running borg init . > <...> >>> pkg_resources.DistributionNotFound: The 'msgpack- >>> python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6' >>> distribution was not found and is required by borgbackup> >> >> I've tried uninstalling and reinstalling borgbackup and all >> dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so >> that should be ok? > > I was hit by this as well a week or two ago, but was too tired and > annoyed to investigate the root of this issue, so what I've done was a > stupid, yet effective workaround -- I commented out msgpack-python line > in /usr/lib64/python3.6/site-packages/borgbackup-1.1.7-py3.6.egg-info/requires.txt > file and things were functional again. > > But now I got curious and looked around a bit. Here's what I dug up: > the problem here is that borgbackup requires msgpack-python while > upstream of the latter switched its name to msgpack (without -python > suffix). borgbackup devs are aware of this change and will fix it > eventually (if they haven't already), but what we can do right now is > add the following to borgbackup.SlackBuild somewhere before the line > that calls 'python3 setup.py install': > > sed -i 's/msgpack-python/msgpack/' setup.py > I'll try to look into it ASAP. (I need to finally switch to borg from attic, that would have caught my attention much faster). -- Best regards / Pozdrawiam, Andrzej Telszewski From mlton837 at scotdoyle.com Sat Dec 8 14:07:21 2018 From: mlton837 at scotdoyle.com (Scot) Date: Sat, 8 Dec 2018 14:07:21 +0000 (UTC) Subject: [Slackbuilds-users] mlton available Message-ID: Hi all, Would anyone like to take over mlton? The last two releases have been July 2013 and February 2018. Scot From slackalaxy at gmail.com Sat Dec 8 16:42:44 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Sat, 8 Dec 2018 18:42:44 +0200 Subject: [Slackbuilds-users] giving maintenance of Zotero to Andrew Message-ID: Hi all, I am giving maintenance of Zotero to Andrew Payne. For the rest of my SlackBuilds, I hope to submit updates to the end of the year. BTW, if someone is eager to maintain something from here: https://slackalaxy.com/slackbuilds/ let me know. best Petar From willysr at slackbuilds.org Sun Dec 9 06:28:34 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 9 Dec 2018 13:28:34 +0700 Subject: [Slackbuilds-users] Updates - 20181209.1 Message-ID: Hi, Sorry for the delay, but last minute submission requires big deps (Qt5, webkitgtk, and opencv), so compiling them take some time along with our busy schedule in our daily life. Here's the latest batch of update for this week: Sun Dec 9 06:18:08 UTC 2018 academic/libqalculate: Updated for version 2.8.2 academic/qalculate-gtk: Updated for version 2.8.2 accessibility/unclutter-xfixes: Updated for version 1.4. audio/alsa-tools: Updated for version 1.1.7. audio/snd: Updated for version 18.9. desktop/Zafiro-icons: Updated for version 0.7.4. desktop/flatpak: Updated for version 1.1.0. desktop/xfce4-windowck-plugin: Updated for version 0.4.5. development/adoptopenjdk: Updated for version 11.0.1+13. development/blassic: Fix homepage and download. development/cargo-vendor: Updated for version 0.1.22. development/kotlin: Updated for version 1.3.11. development/p4: Updated for version 2018.2.1724420. development/p4d: Updated for version 2018.2.1724420. development/psycopg2: Updated for version 2.7.6.1. development/pycharm: Updated for version 2018.3.1. development/rustup: Updated for version 1.15.0. development/sbcl: Updated for version 1.4.14. games/RetroArch: Fix KMS mode bug. games/astromenace: Updated for version 1.4.0. games/hedgewars: Updated for version 0.9.25. games/javacpc: Updated for version 2.9.7. games/mame: Updated for version 0.204. games/open-adventure: Updated for version 1.6. games/pysolfc: Add missing dep. games/snes9x: Updated for version 1.57. games/tome: Updated for version 1.5.10. games/xroar: Updated for version 0.35.2. gis/geopy: Updated for version 1.18.0. gis/gpxsee: Updated for version 7.0. gis/mapnik: Updated for version 3.0.21. gis/osm2pgrouting: Updated for version 2.3.6. gis/pgrouting: Updated for version 2.6.2. gis/pktools: Fix install directory and add docs. gis/rasterio: Updated for version 1.0.11. graphics/GraphicsMagick: Updated for version 1.3.31, fix perl mod. graphics/gmic: Updated for version 2.4.2. graphics/vsxu: Updated for version 0.6.3.0 haskell/haskell-ShellCheck: Updated for version 0.6.0. libraries/dcmtk: Updated for version 3.6.4 libraries/efivar: Updated for version 35. libraries/libaom: Updated for version 1.0.0.r994.g67aec0fc6. libraries/libfdk-aac: Updated for version 2.0.0 libraries/libfilezilla: Updated for version 0.15.1. libraries/libvirt: Unhardcoded verbose logging in rc.libvirt libraries/libwebp: Remove unknown parameter. libraries/luasec: Updated for version 0.7. libraries/nltk: Updated for version 3.4. libraries/ois: Updated for version 1.5.0 libraries/qt5-pbfimageplugin: Added (PBF image plugin for Qt5). misc/ghostpcl: Added (PCL interpreter). multimedia/MediathekView: Updated for version 13.2.1. multimedia/flashplayer-plugin: Updated for version 32.0.0.101. multimedia/get_iplayer: Updated for version 3.17. multimedia/obs-studio: Patch for latest libfdk-aac api multimedia/pepperflash-plugin: Updated for version 32.0.0.101. network/bozohttpd: Updated for version 20181125. network/dropbox: Updated for version 62.4.103. network/filezilla: Updated for version 3.39.0. network/liferea: Updated for version 1.12.6b. network/opera-developer: Updated for version 59.0.3160.0. network/opera: Updated for version 57.0.3098.91. network/palemoon-bin: Updated for version 28.2.2. network/palemoon: Updated for version 28.2.2. network/prosody-mod-csi: Updated for version hg3396. network/prosody-mod-http-upload: Updated for version hg3380. network/prosody: Updated for version 0.11.1. network/rspamd: Updated for version 1.8.3. network/shadowsocks-libev: Updated for version 3.2.3. network/shorewall-core: Updated for version 5.2.1.2. network/shorewall6: Updated for version 5.2.1.2. network/shorewall: Updated for version 5.2.1.2. network/stride: Removed (Discontinued by upstream). network/unbound: Updated for version 1.8.2. network/vivaldi: Fix MD5SUM. network/xdman: Updated for version 2018.7.2.8. network/you-get: Updated for version 0.4.1181. network/youtube-dl: Updated for version 2018.12.03. office/CherryTree: Updated for version 0.38.6. office/MasterPDFEditor: Updated for version 5.2.11. office/latex2rtf: Added (LaTeX converter). office/texstudio: Updated for version 2.12.14 office/wordgrinder: Added (A word processor for processing words). office/xtrkcad: Updated for version 5.1.2a. perl/perl-DBD-SQLite: Updated for version 1.60. perl/perl-Date-Manip: Updated for version 6.74. perl/perl-Mojolicious: Updated for version 8.09. python/decorator: Updated for version 4.3.1. python/python-fonttools: Updated for version 3.33.0. python/python-prometheus_client: Updated for version 0.5.0. python/python3-decorator: Updated for version 4.3.1. python/python3-django: Updated for version 2.1.4. ruby/ruby-build: Updated for version 20181207. ruby/rubygem-rubocop: Updated for version 0.61.1. system/ZoneMinder: Updated for version 1.32.2. system/aha: Updated for version 0.5. system/clamav: Updated for version 0.101.0. system/dosbox-dev: Updated for version 0.74.r4176. system/fd: Updated for version 7.1.0. system/fwupd: Updated for version 1.1.4. system/letsencrypt: Updated for version 0.29.1. system/openrc-services: Updated for version 20181203. system/pdfgrep: Updated for version 2.1.2. system/powerline-status: Updated for version 2.7. system/ranger: Add optimisation to build command. system/rmw: Updated for version 0.7.01. system/sandbox: Updated for version 2.14. system/sboui: Updated for version 2.0.1. system/stress-ng: Added (Stress Testing Tool). system/thermald: Fix build. system/unison: Updated for version 2.51.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 atelszewski at gmail.com Sun Dec 9 09:01:34 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 9 Dec 2018 10:01:34 +0100 Subject: [Slackbuilds-users] borgbackup msgpack-python problem In-Reply-To: <20181206175339.GA2367@varna> References: <1544060547.168982.1600403136.0A616524@webmail.messagingengine.com> <20181206175339.GA2367@varna> Message-ID: <7e2cfedc-f2e1-f245-88ed-b1d272a0969c@gmail.com> On 06/12/2018 18:53, Audrius Ka?ukauskas wrote: > On Wed, 2018-12-05 at 17:42:27 -0800, David O'Shaughnessy wrote: >> I'm having trouble with borgbackup on 14.2_64. Here's the error message >> upon running borg init . > <...> >>> pkg_resources.DistributionNotFound: The 'msgpack- >>> python!=0.5.0,!=0.5.1,!=0.5.2,!=0.5.3,!=0.5.4,!=0.5.5,<=0.5.6,>=0.4.6' >>> distribution was not found and is required by borgbackup> >> >> I've tried uninstalling and reinstalling borgbackup and all >> dependencies, but no luck yet. The msgpack-python installed is 0.5.6, so >> that should be ok? > > I was hit by this as well a week or two ago, but was too tired and > annoyed to investigate the root of this issue, so what I've done was a > stupid, yet effective workaround -- I commented out msgpack-python line > in /usr/lib64/python3.6/site-packages/borgbackup-1.1.7-py3.6.egg-info/requires.txt > file and things were functional again. > > But now I got curious and looked around a bit. Here's what I dug up: > the problem here is that borgbackup requires msgpack-python while > upstream of the latter switched its name to msgpack (without -python > suffix). borgbackup devs are aware of this change and will fix it > eventually (if they haven't already), but what we can do right now is > add the following to borgbackup.SlackBuild somewhere before the line > that calls 'python3 setup.py install': > > sed -i 's/msgpack-python/msgpack/' setup.py > I've just pushed an updated version. Unfortunately, upstream have not yet fixed the problem. All this being said, I included a patch to fix the msgpack rename problem. In my limited testing, borg works as expected again. Thanks Audrius for the hint. -- Best regards / Pozdrawiam, Andrzej Telszewski From gen-bch at useyouresp.org.uk Sun Dec 9 10:01:39 2018 From: gen-bch at useyouresp.org.uk (Habs) Date: Sun, 9 Dec 2018 10:01:39 +0000 (GMT) Subject: [Slackbuilds-users] Updates - 20181209.1 In-Reply-To: References: Message-ID: On Sun, 9 Dec 2018, Willy Sudiarto Raharjo wrote: > Hi, > > Sorry for the delay, but last minute submission requires big deps (Qt5, > webkitgtk, and opencv), so compiling them take some time along with our > busy schedule in our daily life. > Thank you. As far as I am concerned, there is no need to ever feel a need to apologise on matters like this. It is appreciated very much what effort goes in to making all this available to everyone. --- Sent using Alpine/Pine, a text based MUA --- Tox-id: 96945E2B98A02A58E86B08D104B9B9DBDC9C9CBAC04D8E96274AAC62CC50747FCB281137C07A From yth at ythogtha.org Sun Dec 9 14:08:31 2018 From: yth at ythogtha.org (Arnaud) Date: Sun, 9 Dec 2018 15:08:31 +0100 Subject: [Slackbuilds-users] Updates - 20181209.1 In-Reply-To: References: Message-ID: <20181209150831.a4675c4b8819e3800ab86966@ythogtha.org> > Hi, > > Sorry for the delay, but last minute submission requires big deps (Qt5, > webkitgtk, and opencv), so compiling them take some time along with our > busy schedule in our daily life. Damn, you have a life ? Why is that ? ^^ > libraries/libfdk-aac: Updated for version 2.0.0 It seems that ffmpeg does not build with this version of libfdk-aac. Though it is an optional dependency that needs to be manually activated with FDK_AAC=yes, so it won't matter for most people (including me, I just try to have the most bloated ffmpeg available on SBo ^^), I thought I should say it there. Here is the build error message : ibavcodec/libfdk-aacenc.c: Dans la fonction ?aac_encode_init?: libavcodec/libfdk-aacenc.c:289:34: erreur?: ?AACENC_InfoStruct {alias struct }? has no member named ?encoderDelay? avctx->initial_padding = info.encoderDelay; ^ ffbuild/common.mak:60?: la recette pour la cible ??libavcodec/libfdk-aacenc.o?? a ?chou?e make: *** [libavcodec/libfdk-aacenc.o] Erreur 1 -- Arnaud From sombragris at sombragris.org Sun Dec 9 20:19:17 2018 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sun, 9 Dec 2018 17:19:17 -0300 Subject: [Slackbuilds-users] Dropbox fails MD5 check Message-ID: I just want to report that drobpox fails the MD5 checksum. Thanks, Eduardo -- Eduardo S?nchez Gauto, Abog., Th.M. Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol Oficina: https://goo.gl/maps/mccgBNM7Zw32 Web: http://sombragris.org - Blog: http://shadow.sombragris.org TW: @thegreyshadow - FB: /thegreyshadow - Tel?fono: (0991) 755-355 - Asunci?n, Paraguay ================================================================== -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From d.zlatanidis at gmail.com Sun Dec 9 20:27:34 2018 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Sun, 9 Dec 2018 21:27:34 +0100 Subject: [Slackbuilds-users] Dropbox fails MD5 check In-Reply-To: References: Message-ID: Yes, Willy he has already fixed. https://git.slackbuilds.org/slackbuilds/commit/?id=216ed2be6 On Sun, Dec 9, 2018, 21:19 Eduardo Sanchez I just want to report that drobpox fails the MD5 checksum. > > Thanks, > > Eduardo > > -- > Eduardo S?nchez Gauto, Abog., Th.M. > Abogado - Traductor P?blico Matriculado Ingl?s - Espa?ol > Oficina: https://goo.gl/maps/mccgBNM7Zw32 > Web: http://sombragris.org - Blog: http://shadow.sombragris.org > TW: @thegreyshadow - FB: /thegreyshadow - > Tel?fono: (0991) 755-355 - Asunci?n, Paraguay > ================================================================== > _______________________________________________ > 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 chris.willing at linux.com Sun Dec 9 22:20:11 2018 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 10 Dec 2018 08:20:11 +1000 Subject: [Slackbuilds-users] Updates - 20181209.1 In-Reply-To: <20181209150831.a4675c4b8819e3800ab86966@ythogtha.org> References: <20181209150831.a4675c4b8819e3800ab86966@ythogtha.org> Message-ID: On 10/12/18 12:08 am, Arnaud wrote: [snip] > >> libraries/libfdk-aac: Updated for version 2.0.0 > > It seems that ffmpeg does not build with this version of libfdk-aac. > Though it is an optional dependency that needs to be manually activated with > FDK_AAC=yes, so it won't matter for most people (including me, I just try to > have the most bloated ffmpeg available on SBo ^^), I thought I should say it > there. > > Here is the build error message : > ibavcodec/libfdk-aacenc.c: Dans la fonction ?aac_encode_init?: > libavcodec/libfdk-aacenc.c:289:34: erreur?: ?AACENC_InfoStruct {alias struct }? has no member named ?encoderDelay? > avctx->initial_padding = info.encoderDelay; > ^ > ffbuild/common.mak:60?: la recette pour la cible ??libavcodec/libfdk-aacenc.o?? a ?chou?e > make: *** [libavcodec/libfdk-aacenc.o] Erreur 1 > Attached is simple minded patch which fixes the ffmpeg build problem with the new libfdk-aac-2.0.0. chris -------------- next part -------------- A non-text attachment was scrubbed... Name: ffmpeg-3.2.4-libfdk_aac-2.0.0.patch Type: text/x-patch Size: 399 bytes Desc: not available URL: From willysr at slackbuilds.org Mon Dec 10 01:03:05 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 10 Dec 2018 08:03:05 +0700 Subject: [Slackbuilds-users] Updates - 20181209.1 In-Reply-To: References: <20181209150831.a4675c4b8819e3800ab86966@ythogtha.org> Message-ID: <2202cd2c-66dd-99a6-09d6-d37c1a9231e0@slackbuilds.org> > Attached is simple minded patch which fixes the ffmpeg build problem > with the new libfdk-aac-2.0.0. Applied thanks Chris -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Tue Dec 11 08:22:22 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 11 Dec 2018 03:22:22 -0500 Subject: [Slackbuilds-users] higan is in terrible shape Message-ID: Who's maintaining this build? The .info file says Gabriel Magno, but the last version update was done by Johannes Schoepfer. The reason I ask is, higan seems totally broken. Trying to load a ROM from its GUI, or giving a ROM filename on the command line, gives a dialog box saying: Error: missing required file: /home/urchlay/.local/share/higan/Super Famicom.sys/manifest.bml This file (and the other support files) are installed to /usr/share/higan, but strace shows higan never looks there, only in $HOME/.local/share/higan. Emulation never starts... and when I try to exit the emulator, it segfaults. At least one other user (on IRC) is having the same issues... I'm not blaming any SBo maintainer for any of this, I just want to know who last tested this application and whether or not it worked for them. From slackbuilds at schoepfer.info Tue Dec 11 08:31:12 2018 From: slackbuilds at schoepfer.info (Franzen) Date: Tue, 11 Dec 2018 09:31:12 +0100 Subject: [Slackbuilds-users] higan is in terrible shape In-Reply-To: References: Message-ID: Hi, > Who's maintaining this build? The .info file says Gabriel Magno, but > the last version update was done by Johannes Schoepfer. I gues nobody is maintaining it. It was broken and somebody asked long ago, of here somebody would bring it in a better shape to prevent it's removal from SBo. I did that, and i think it did work somehow, but can't remember and don't use higan, sorry. Johannes From matteo.bernardini at gmail.com Tue Dec 11 08:31:34 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 11 Dec 2018 09:31:34 +0100 Subject: [Slackbuilds-users] higan is in terrible shape In-Reply-To: References: Message-ID: Il giorno mar 11 dic 2018 alle ore 09:22 B Watson ha scritto: > > Who's maintaining this build? The .info file says Gabriel Magno, but > the last version update was done by Johannes Schoepfer. > > The reason I ask is, higan seems totally broken. Trying to load a ROM > from its GUI, or giving a ROM filename on the command line, gives a > dialog box saying: > > Error: missing required file: /home/urchlay/.local/share/higan/Super > Famicom.sys/manifest.bml > > This file (and the other support files) are installed to > /usr/share/higan, but strace shows higan never looks there, only in > $HOME/.local/share/higan. > > Emulation never starts... and when I try to exit the emulator, it > segfaults. > > At least one other user (on IRC) is having the same issues... > > I'm not blaming any SBo maintainer for any of this, I just want to know > who last tested this application and whether or not it worked for them. I'll forward this also to the maintainer, as I'm not sure he follows the list... From yalhcru at gmail.com Tue Dec 11 21:46:22 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 11 Dec 2018 16:46:22 -0500 Subject: [Slackbuilds-users] higan is in terrible shape In-Reply-To: References: Message-ID: On 12/11/18, Matteo Bernardini wrote: > > I'll forward this also to the maintainer, as I'm not sure he follows the > list... He was CC'ed on the original email, but thanks anyway. I'll probably try to get higan working myself. If I manage it, I'll take over as maintainer. More likely I'll tear my hair out trying... From yalhcru at gmail.com Wed Dec 12 08:58:52 2018 From: yalhcru at gmail.com (B Watson) Date: Wed, 12 Dec 2018 03:58:52 -0500 Subject: [Slackbuilds-users] higan is in terrible shape In-Reply-To: References: Message-ID: On 12/11/18, B Watson wrote: > On 12/11/18, Matteo Bernardini wrote: >> >> I'll forward this also to the maintainer, as I'm not sure he follows the >> list... > > He was CC'ed on the original email, but thanks anyway. > > I'll probably try to get higan working myself. If I manage it, I'll take > over as maintainer. More likely I'll tear my hair out trying... > OK, I've got a *much* improved SlackBuild for higan, ready to submit. Updated to the latest stable release, got rid of the segfaults, and added some nice features. The original maintainer, Gabriel Magno, hasn't been active on SBo since October 2014 (4+ years ago) according to the git log. I emailed him already, 24+ hours ago, and haven't got a response yet... Does anyone insist I wait a week before taking over this build? From willysr at slackbuilds.org Wed Dec 12 09:36:46 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 12 Dec 2018 16:36:46 +0700 Subject: [Slackbuilds-users] higan is in terrible shape In-Reply-To: References: Message-ID: <4af41ee0-d297-8cc6-1b46-09b4467f9a35@slackbuilds.org> > OK, I've got a *much* improved SlackBuild for higan, ready to > submit. Updated to the latest stable release, got rid of the segfaults, > and added some nice features. > > The original maintainer, Gabriel Magno, hasn't been active on SBo since > October 2014 (4+ years ago) according to the git log. I emailed him > already, 24+ hours ago, and haven't got a response yet... Does anyone > insist I wait a week before taking over this build? Go for it -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Wed Dec 12 09:47:55 2018 From: yalhcru at gmail.com (B Watson) Date: Wed, 12 Dec 2018 04:47:55 -0500 Subject: [Slackbuilds-users] higan is in terrible shape In-Reply-To: <4af41ee0-d297-8cc6-1b46-09b4467f9a35@slackbuilds.org> References: <4af41ee0-d297-8cc6-1b46-09b4467f9a35@slackbuilds.org> Message-ID: On 12/12/18, Willy Sudiarto Raharjo wrote: > > Go for it OK, thanks, pushed to my git branch. From slackalaxy at gmail.com Wed Dec 12 10:11:44 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Wed, 12 Dec 2018 12:11:44 +0200 Subject: [Slackbuilds-users] calibre still does not start Message-ID: just a quick question -- is calibre broken just for me or others cannot start it, as well? I ended up installing the binary from their website. -petar From dchmelik at gmail.com Wed Dec 12 10:48:01 2018 From: dchmelik at gmail.com (David Melik) Date: Wed, 12 Dec 2018 02:48:01 -0800 Subject: [Slackbuilds-users] calibre still does not start In-Reply-To: References: Message-ID: On 12/12/18 2:11 AM, Petar Petrov wrote: > just a quick question -- is calibre broken just for me or others > cannot start it, as well? > > I ended up installing the binary from their website. > > -petar Most versions have broken for me for years.? Sometimes they work when recompiled (not always.) From matteo.bernardini at gmail.com Wed Dec 12 11:00:08 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 12 Dec 2018 12:00:08 +0100 Subject: [Slackbuilds-users] calibre still does not start In-Reply-To: References: Message-ID: Il giorno mer 12 dic 2018 alle ore 11:48 David Melik ha scritto: > > On 12/12/18 2:11 AM, Petar Petrov wrote: > > just a quick question -- is calibre broken just for me or others > > cannot start it, as well? > > > > I ended up installing the binary from their website. > > > > -petar > > Most versions have broken for me for years. Sometimes they work when > recompiled (not always.) it seems to work perfectly fine here. From alik at ejik.org Wed Dec 12 12:43:34 2018 From: alik at ejik.org (Alexander Verbovetsky) Date: Wed, 12 Dec 2018 15:43:34 +0300 Subject: [Slackbuilds-users] calibre still does not start In-Reply-To: References: Message-ID: <1544618614.1416879.1606977960.3CA72A0D@webmail.messagingengine.com> Hello, On Wed, 12 Dec 2018, at 13:11, Petar Petrov wrote: > just a quick question -- is calibre broken just for me or others > cannot start it, as well? I also cannot start it after a recent upgrade. I attached the error screenshot. Best regards, Alexander -------------- next part -------------- A non-text attachment was scrubbed... Name: calibre-error.png Type: image/png Size: 64243 bytes Desc: not available URL: From matteo.bernardini at gmail.com Wed Dec 12 13:27:48 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 12 Dec 2018 14:27:48 +0100 Subject: [Slackbuilds-users] calibre still does not start In-Reply-To: <1544618614.1416879.1606977960.3CA72A0D@webmail.messagingengine.com> References: <1544618614.1416879.1606977960.3CA72A0D@webmail.messagingengine.com> Message-ID: Il giorno mer 12 dic 2018 alle ore 13:43 Alexander Verbovetsky ha scritto: > > Hello, > > On Wed, 12 Dec 2018, at 13:11, Petar Petrov wrote: > > just a quick question -- is calibre broken just for me or others > > cannot start it, as well? > > I also cannot start it after a recent upgrade. I attached the error > screenshot. your error seems related to sip so I would check if you have python2-sip installed or if you have it already, just rebuild it. in any case, I would also try to rebuild calibre together with all of its dependencies, also if they are quite a lot: unrar unrardll dukpy python3 python-webencodings six html5lib BeautifulSoup4 lxml html5-parser regex msgpack-python Pygments enum34 python2-sip pyudev python-evdev graphviz ninja meson libwacom libinput libxkbcommon qt5 qt5-webkit PyQt5 optipng apsw cssselect psutil netifaces setuptools-scm python-dateutil podofo mechanize dnspython cssutils calibre Matteo From dave at tty1.uk Wed Dec 12 14:45:42 2018 From: dave at tty1.uk (Dave Woodfall) Date: Wed, 12 Dec 2018 14:45:42 +0000 Subject: [Slackbuilds-users] calibre still does not start In-Reply-To: <1544618614.1416879.1606977960.3CA72A0D@webmail.messagingengine.com> References: <1544618614.1416879.1606977960.3CA72A0D@webmail.messagingengine.com> Message-ID: <20181212144542.GA26349@blackswan.r0t.uk> I just built this to see if it was a python2-sip problem, but it failed on something completely different. The first time I ran it, it complained of not finding QtCore. The next few times it was socket related, so no idea what is going on there. DBus is running. If it is sip related, try rebuilding python2-sip and other PyQt5 dependencies followed by PyQt5 itself again, then calibre once again. Just a long shot but it may work. Dave On Wednesday 12 December 2018 15:43, Alexander Verbovetsky put forth the proposition: > Hello, > > On Wed, 12 Dec 2018, at 13:11, Petar Petrov wrote: > > just a quick question -- is calibre broken just for me or others > > cannot start it, as well? > > I also cannot start it after a recent upgrade. I attached the error > screenshot. > > Best regards, > Alexander > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -- Democracy is also a form of worship. It is the worship of Jackals by Jackasses. -- H. L. Mencken -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From porting at use.startmail.com Thu Dec 13 12:45:37 2018 From: porting at use.startmail.com (=?iso-8859-1?Q?Rub=E9n?= Llorente) Date: Thu, 13 Dec 2018 13:45:37 +0100 Subject: [Slackbuilds-users] Hedgewars - md5missmatch Message-ID: <20181213124537.GA35152@miniserver.corrin.dyn> Hello, I have noticed that the Hedgewars slackbuild has a wrong MD5 assigned to it. Correct one would be e1e3d162b2e08b9eadd133775f44ff77. -- OpenPGP Key Fingerprint: BB5A C2A2 2CAD ACB7 D50D C081 1DB9 6FC4 5AB7 92FA From edkchem at comcast.net Thu Dec 13 08:30:16 2018 From: edkchem at comcast.net (edkchem) Date: Thu, 13 Dec 2018 00:30:16 -0800 Subject: [Slackbuilds-users] Gemrb sourceforge SSL cert error and md5sum mismatch with github archive Message-ID: 1. Attempting to d/l gemrb source via Firefox as https from the SBo page yields a certificate error, but works as http 2. The sourceforge and github archives do not match # md5sum *.tar.gz 9be089783d869100cddd8a2d5e0bc454 gemrb-0.8.5.tar.gz ee81ef46367202dbe0569c7a9a29e2b1 sf-gemrb-0.8.5.tar.gz (I haven't look all that hard at the file list...) 3. http://www.gemrb.org states that the main source is at github, so perhaps SBo should pint there and not SF. From willysr at slackbuilds.org Thu Dec 13 20:29:45 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 14 Dec 2018 03:29:45 +0700 Subject: [Slackbuilds-users] Gemrb sourceforge SSL cert error and md5sum mismatch with github archive In-Reply-To: References: Message-ID: <0deb9b77-0453-6149-5b44-5f1986764cfa@slackbuilds.org> > 1. > Attempting to d/l gemrb source via Firefox as https from the SBo page > yields a certificate error, but works as http > > 2. > The sourceforge and github archives do not match > # md5sum *.tar.gz > 9be089783d869100cddd8a2d5e0bc454 gemrb-0.8.5.tar.gz > ee81ef46367202dbe0569c7a9a29e2b1 sf-gemrb-0.8.5.tar.gz > > (I haven't look all that hard at the file list...) > > 3. http://www.gemrb.org states that the main source is at github, so > perhaps SBo should pint there and not SF. They have an expired certificate ERROR: cannot verify tenet.dl.sourceforge.net's certificate, issued by ?CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US?: Issued certificate has expired. -- 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 z.coldplayer at gmail.com Fri Dec 14 15:13:15 2018 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Fri, 14 Dec 2018 19:13:15 +0400 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: <59146946-91f7-a5b8-0f4d-52b93c948da1@gmail.com> References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> <59146946-91f7-a5b8-0f4d-52b93c948da1@gmail.com> Message-ID: On Tue, 15 May 2018 at 17:25, Andrzej Telszewski wrote: > On 11/05/18 02:27, B Watson wrote: > > On 5/10/18, Andrzej Telszewski wrote: > >> > >> Because it builds fine on my side, I run out of ideas what might be > >> wrong on his side. > > > > You and your user both using the same version of Slackware, the same arch > > (32-bit or 64-bit)? With or without multilib, if you're both on 64-bit? > > He confirms that our setups are mostly the same. > Anyway, I asked him to post to the ML. > > Thanks. > > -- > Best regards / Pozdrawiam, > Andrzej Telszewski > _______________________________________________ > 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/ Hi, I am also having some issues but I need to confirm if this is the case to continue in this thread since I am not using qt-creator-llvm. I could not compile qt-creator-llvm initially, I will try again and post in the future. *cd clangbackend/ && ( test -e Makefile || /usr/bin/qmake-qt5 -o Makefile /tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools/clangbackend/clangbackend.pro 'QMAKE_CXXFLAGS=-O2 -fPIC' QTC_PREFIX=/usr IDE_LIBRARY_BASENAME=lib64 LLVM_INSTALL_DIR= QBS_INSTALL_DIR=/usr DEFINES+=QBS_ENABLE_PROJECT_FILE_UPDATES ) && make -f Makefile Project WARNING: Clang LibTooling is disabled because only version 5.0 is supported.make[3]: Entering directory '/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools/clangbackend'g++ -c -O2 -fPIC -Wno-noexcept-type -O2 -O2 -fPIC -std=gnu++1y -Wall -W -D_REENTRANT -fPIC -DQBS_ENABLE_PROJECT_FILE_UPDATES -D'RELATIVE_PLUGIN_PATH="../lib64/qtcreator/plugins"' -D'RELATIVE_LIBEXEC_PATH="../libexec/qtcreator"' -D'RELATIVE_DATA_PATH="../share/qtcreator"' -D'RELATIVE_DOC_PATH="../doc/qt-creator-4.6.2"' -DIDE_LIBRARY_BASENAME=\"lib64\" -DQT_CREATOR -DQT_NO_CAST_TO_ASCII -DQT_RESTRICTED_CAST_FROM_ASCII -DQT_DISABLE_DEPRECATED_BEFORE=0x050600 -DQT_USE_FAST_OPERATOR_PLUS -DQT_USE_FAST_CONCATENATION -DQT_NO_DEBUG -DQT_CONCURRENT_LIB -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -I../../../src -I../../../src -I../../libs -I/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/tools -I../../plugins -I../../libs -I../../libs/sqlite -I../../libs/clangsupport -Isource -isystem /usr/include -isystem /usr/include/qt5 -isystem /usr/include/qt5/QtConcurrent -isystem /usr/include/qt5/QtWidgets -isystem /usr/include/qt5/QtGui -isystem /usr/include/qt5/QtNetwork -isystem /usr/include/qt5/QtCore -I.moc/release-shared -isystem /usr/include/libdrm -I/usr/lib64/qt5/mkspecs/linux-g++ -o .obj/release-shared/clangcodecompleteresults.o source/clangcodecompleteresults.cppIn file included from /usr/include/c++/8.2.0/bits/stl_algo.h:59, from /usr/include/c++/8.2.0/algorithm:62, from /usr/include/qt5/QtCore/qglobal.h:142, from /usr/include/qt5/QtCore/QtGlobal:1, from ../../libs/sqlite/sqliteglobal.h:30, from ../../libs/sqlite/utf8string.h:28, from source/clangcodecompleteresults.h:30, from source/clangcodecompleteresults.cpp:26:/usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next ^~~~~~~~~~compilation terminated.make[3]: *** [Makefile:785: .obj/release-shared/clangcodecompleteresults.o] Error 1make[3]: Leaving directory '/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools/clangbackend'make[2]: *** [Makefile:229: sub-clangbackend-make_first] Error 2make[2]: Leaving directory '/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src/tools'make[1]: *** [Makefile:179: sub-tools-make_first-ordered] Error 2make[1]: Leaving directory '/tmp/sbopkg.yH3Sdt/qt-creator-4.6.2/src'make: *** [Makefile:46: sub-src-make_first-ordered] Error 2* Especially :: /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory I have been reading some forums and it seems this issue started when there was a change in gcc version bump as from 6.0. Could you please confirm or I will make a new thread. I am using Slackware-current and sbopkg. Three times I compiled and got the same error. Cheers Pritvi -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Fri Dec 14 19:23:09 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 14 Dec 2018 20:23:09 +0100 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> <59146946-91f7-a5b8-0f4d-52b93c948da1@gmail.com> Message-ID: Il giorno ven 14 dic 2018 alle ore 16:13 Jheengut Pritvi ha scritto: > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such file or directory > > I have been reading some forums and it seems this issue started when there was a change in > gcc version bump as from 6.0. Could you please confirm or I will make a new thread. > > I am using Slackware-current and sbopkg. Three times I compiled and got the same error. hi Pritvi, just version-bump qbs to 1.12.2 and qt-creator to 4.8.0 using the existing SlackBuilds and they will build fine also on current. Matteo From willysr at slackbuilds.org Sat Dec 15 01:12:16 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Dec 2018 08:12:16 +0700 Subject: [Slackbuilds-users] Hedgewars - md5missmatch In-Reply-To: <20181213124537.GA35152@miniserver.corrin.dyn> References: <20181213124537.GA35152@miniserver.corrin.dyn> Message-ID: > I have noticed that the Hedgewars slackbuild has a wrong MD5 assigned to > it. Correct one would be e1e3d162b2e08b9eadd133775f44ff77. It's fixed on my branch and surprisingly, i got another value md5sum hedgewars-src-0.9.25.tar.bz2 a1509a455c37e99f9ac56bc939248322 hedgewars-src-0.9.25.tar.bz2 -- 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 1.41421 at gmail.com Fri Dec 14 21:09:14 2018 From: 1.41421 at gmail.com (JCA) Date: Fri, 14 Dec 2018 14:09:14 -0700 Subject: [Slackbuilds-users] Chromium in Slackbuilds Message-ID: The version of the Chromium from Slackbuilds is 53, whereas the latest is 71. I.e. 53 is well over two years old. Why is it being kept that old, especially bearing in mind that Slackware packages for the latest Chromium may be downloaded from http://www.slackware.com/~alien/slackbuilds/chromium. I mean, what is the point of keeping such an old version in Slackbuilds? -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Dec 15 13:56:58 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Dec 2018 20:56:58 +0700 Subject: [Slackbuilds-users] Updates - 20181215.1 Message-ID: <5ea1b8ab-4f5b-42b2-88e3-9e4d9dae623e@slackbuilds.org> Hi everyone here are the latest work from the last 6 days since last public update Sat Dec 15 13:45:21 UTC 2018 academic/Gridcoin-Research: Updated for version 4.0.1.0. academic/zotero: Updated for version 5.0.58 + new maintainer. audio/helm: Added (software synthesiser). audio/lmms: Updated for version 1.1.90. audio/whipper: Updated for version 0.7.3. desktop/ComixCursors: Updated for version 0.9.1. desktop/Surfn: Added (Icon theme). desktop/i3-gaps: Updated for version 4.16. desktop/materia-theme: Added (A Material Design theme). development/CImg: Updated for version 2.4.2. development/apache-maven: Updated for version 3.6.0. development/bsdiff: New maintainer, tweaks. development/d-tools: Updated for version 2.083.1 development/dmd: Updated for version 2.083.1 development/git-lfs: Updated for version 2.6.1. development/google-go-lang: Updated for version 1.11.3. development/hopper: Updated for version 4.5.0. development/hub: Updated for version 2.6.1. development/jupyter_client: Updated for version 5.2.4. development/neovim-qt: Updated for version 0.2.11. development/pyvim: Updated for version 2.0.23. development/robotframework: Updated for version 3.1. development/rstudio-desktop: Updated for version 1.1.463. development/universal-ctags: Updated for version 1b9d344 development/zulu-openjdk-lts: Added (Open Implementation of JDK). games/astromenace: Update deps. games/flare-game: Updated for version 1.09.01. games/flare: Updated for version 1.09.01. games/golly: Updated for version 3.2, new maintainer. games/hedgewars: Fix MD5SUM. games/higan: Updated for version 106, new maintainer. games/libretro-reicast: Updated for version 2018.12.11_7221180. games/pcsx2: Updated for version 2018.12.11_0e43803. gis/Fiona: Updated for version 1.8.4. gis/OTB: Updated for version 6.6.1. gis/ossim: Updated for version 2.6.1. gis/rasterio: Updated for version 1.0.13. graphics/XnViewMP: Updated for version 0.92. graphics/nomacs: Patch for the newer opencv. graphics/opencollada: Fix MD5SUM ham/tlf: Updated for version 1.3.2 ham/wsjtx: Updated for version 2.0.0 libraries/glfw3: Updated for version 3.2.1. libraries/hoel: Updated for version 1.4.7. libraries/jansson: Updated for version 2.12 libraries/libjwt: Updated for version 1.10.0. libraries/libxnvctrl: Updated for version 410.73. libraries/live555: Updated for version 2018.12.14 libraries/npth: Updated for version 1.6. libraries/nv-codec-headers: Updated for version 8.2.15.7. libraries/opencv: Updated for version 4.0.0 libraries/orcania: Updated for version 1.2.9. libraries/qt5: Add CCACHE and WEBENGINE options. Add notes. libraries/ulfius: Updated for version 2.5.0. misc/mosquitto: Updated for version 1.5.5 misc/po4a: Updated for version 0.55. multimedia/ffmpeg: Fix build with new libfdk-aac API. multimedia/vivaldi-codecs-ffmpeg-extra: Updated for version 71.0.3578.80. network/aMule: Updated for version r11003. network/asterisk: Updated for version 16.1.0. network/dropbox: Fix MD5SUM. network/hylafax+: Updated for version 5.6.1. network/lighttpd: Updated for version 1.4.52. network/milter-greylist: Add rc init script. Move .conf to .example. network/netqmail: Fix for current. network/prosody-mod-mam-muc: Removed (incompatible w/ prosody 0.11) network/riot-web: Updated for version 0.17.7. network/signal-desktop: Updated for version 1.19.0. network/telegram: Updated for version 1.5.1. network/tor-browser: Updated for version 8.0.4. network/vivaldi: Updated for version 2.2.1388.34. network/vnstat: Updated for version 2.1. office/openoffice-langpack: Updated for version 4.1.6. office/pdfstudio2018: Updated for version 18.2.2. perl/MoarVM: Updated for version 2018.11. perl/nqp: Updated for version 2018.11. perl/perl-Date-Manip: Updated for version 6.75. perl/rakudo: Updated for version 2018.11. perl/zef: Updated for version 0.5.4. python/prompt_toolkit: Updated for version 2.0.7. python/python-fonttools: Updated for version 3.34.0. python/python-jsonrpclib: Updated for version 0.3.2. python/python3-jupyter_client: Updated for version 5.2.4. python/python3-six: Updated for version 1.12.0. python/six: Updated for version 1.12.0 system/ansible: Updated for version 2.7.5. system/atop: Add man page. system/borgbackup: Updated for version 1.1.8. system/gtk-vnc: Updated for version 0.9.0. system/keybase: Updated for version 2.11.0. system/kitchen-sync: Updated for version 1.7. system/phoronix-test-suite: Updated for version 8.4.1. system/qemu: Updated for version 3.1.0. system/qtfm: Updated for version 6.1.5. system/radeontop: Added (Radeon cards monitoring utility). system/ranger: Change homepage system/slack-scripts: Change homepage system/wine-staging: Updated for version 3.21. +--------------------------+ -- 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 chris.willing at linux.com Sat Dec 15 21:16:27 2018 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 16 Dec 2018 07:16:27 +1000 Subject: [Slackbuilds-users] Updates - 20181215.1 (opencv) In-Reply-To: <5ea1b8ab-4f5b-42b2-88e3-9e4d9dae623e@slackbuilds.org> References: <5ea1b8ab-4f5b-42b2-88e3-9e4d9dae623e@slackbuilds.org> Message-ID: <47b719e2-618d-a8aa-aaea-edb173113fec@linux.com> On 15/12/18 11:56 pm, Willy Sudiarto Raharjo wrote: > libraries/opencv: Updated for version 4.0.0 > I'm sorry but there's a mistake in this update to opencv-4.0.0. I've pushed a correction but in the meantime it can be fixed by changing the line: if [ -d /usr/etc/qt5 ]; then to if [ -d /usr/include/qt5 ]; then chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: From z.coldplayer at gmail.com Sun Dec 16 05:52:18 2018 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sun, 16 Dec 2018 09:52:18 +0400 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> <59146946-91f7-a5b8-0f4d-52b93c948da1@gmail.com> Message-ID: On Fri, 14 Dec 2018, 23:23 Matteo Bernardini Il giorno ven 14 dic 2018 alle ore 16:13 Jheengut Pritvi > ha scritto: > > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No such > file or directory > > > > I have been reading some forums and it seems this issue started when > there was a change in > > gcc version bump as from 6.0. Could you please confirm or I will make > a new thread. > > > > I am using Slackware-current and sbopkg. Three times I compiled and got > the same error. > > hi Pritvi, > > just version-bump qbs to 1.12.2 and qt-creator to 4.8.0 using the > existing SlackBuilds and they will build fine also on current. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ Thanks for your reply, This is what I am now doing ??. This evening I will check if everything has built well. > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From atelszewski at gmail.com Sun Dec 16 07:50:43 2018 From: atelszewski at gmail.com (Andrzej Telszewski) Date: Sun, 16 Dec 2018 08:50:43 +0100 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> <59146946-91f7-a5b8-0f4d-52b93c948da1@gmail.com> Message-ID: On 16/12/2018 06:52, Jheengut Pritvi wrote: > > > On Fri, 14 Dec 2018, 23:23 Matteo Bernardini > wrote: > > Il giorno ven 14 dic 2018 alle ore 16:13 Jheengut Pritvi > > ha scritto: > > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No > such file or directory > > > > I have been reading some forums and it seems this issue started > when there was a change in > > gcc version bump as from 6.0.? Could you please confirm or? I > will make a new thread. > > > > I am using Slackware-current and sbopkg. Three times I compiled > and got the same error. > > hi Pritvi, > > just version-bump qbs to 1.12.2 and qt-creator to 4.8.0 using the > existing SlackBuilds and they will build fine also on current. > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > Thanks for your reply, > This is what I am now doing ??. > > This evening I will check if everything has built well. > Hi, I'm in the process of updating the SlackBuilds. So far, I successfully compiled Qbs (1.12.2) and Qt Creator (4.8). I was also able to compile the LLVM/Clang (7.0) from https://code.qt.io/clang/llvm This is the recommended version of Clang to be used with QtC 4.8+. BUT, I haven't yet tested building QtC against this Clang version. If all goes well, the updated SlackBuilds should land in SBo in a couple of days. I'm building on 14.2. -- Best regards, Andrzej Telszewski From z.coldplayer at gmail.com Sun Dec 16 14:25:40 2018 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sun, 16 Dec 2018 18:25:40 +0400 Subject: [Slackbuilds-users] qt-creator fails (?) to build with qt-creator-llvm In-Reply-To: References: <7279679f-9562-e3a8-13e4-22bc8c773ae1@gmail.com> <59146946-91f7-a5b8-0f4d-52b93c948da1@gmail.com> Message-ID: On Sun, 16 Dec 2018 at 11:50, Andrzej Telszewski wrote: > On 16/12/2018 06:52, Jheengut Pritvi wrote: > > > > > > On Fri, 14 Dec 2018, 23:23 Matteo Bernardini > > wrote: > > > > Il giorno ven 14 dic 2018 alle ore 16:13 Jheengut Pritvi > > > ha scritto: > > > /usr/include/c++/8.2.0/cstdlib:75:15: fatal error: stdlib.h: No > > such file or directory > > > > > > I have been reading some forums and it seems this issue started > > when there was a change in > > > gcc version bump as from 6.0. Could you please confirm or I > > will make a new thread. > > > > > > I am using Slackware-current and sbopkg. Three times I compiled > > and got the same error. > > > > hi Pritvi, > > > > just version-bump qbs to 1.12.2 and qt-creator to 4.8.0 using the > > existing SlackBuilds and they will build fine also on current. > > > > Matteo > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - > https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > > Thanks for your reply, > > This is what I am now doing ??. > > > > This evening I will check if everything has built well. > > > > Hi, > > I'm in the process of updating the SlackBuilds. > > So far, I successfully compiled Qbs (1.12.2) and Qt Creator (4.8). > > I was also able to compile the LLVM/Clang (7.0) from > https://code.qt.io/clang/llvm > This is the recommended version of Clang to be used with QtC 4.8+. > > BUT, I haven't yet tested building QtC against this Clang version. > > If all goes well, the updated SlackBuilds should land in SBo in a couple > of days. > > I'm building on 14.2. > > -- > Best regards, > Andrzej Telszewski > Awesome, thanks for the update! I have successfully build qtcreator 4.8 with qbs 1.12.1 using alien bob's qt5 5.11.2, not slackbuilds qt5. Best Regards Pritvi Jheengut -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikelangdon at roadrunner.com Sun Dec 16 16:36:33 2018 From: mikelangdon at roadrunner.com (Michael Langdon) Date: Sun, 16 Dec 2018 10:36:33 -0600 Subject: [Slackbuilds-users] Pokerth and its queue Message-ID: The info file for pokerth lists 4 dependencies: libgsasl libircclient tinyxml protobuf If I load its queue, that queue adds six more items: google-apputils python-gflags six setuptools-scm python-dateutil pytz My question is, why doesn't the queue match the info file? I can build pokerth going by the requires from the info file, but it fails when going by the queue. libircclient fails because it can't find openssl. libircclient builds fine outside the queue. From falsetti at clansco.org Sun Dec 16 16:51:23 2018 From: falsetti at clansco.org (=?ISO-8859-1?Q?Fr=E9d=E9ric?= Falsetti) Date: Sun, 16 Dec 2018 17:51:23 +0100 Subject: [Slackbuilds-users] Updates - 20181215.1 (opencv) In-Reply-To: <47b719e2-618d-a8aa-aaea-edb173113fec@linux.com> References: <5ea1b8ab-4f5b-42b2-88e3-9e4d9dae623e@slackbuilds.org> <47b719e2-618d-a8aa-aaea-edb173113fec@linux.com> Message-ID: <20181216175123.edbb2655e702bf6c11ad7ad7@clansco.org> On Sun, 16 Dec 2018 07:16:27 +1000 Christoph Willing wrote: > On 15/12/18 11:56 pm, Willy Sudiarto Raharjo wrote: > > > libraries/opencv: Updated for version 4.0.0 > > > > I'm sorry but there's a mistake in this update to opencv-4.0.0. I've > pushed a correction but in the meantime it can be fixed by changing the > line: > if [ -d /usr/etc/qt5 ]; then > to > if [ -d /usr/include/qt5 ]; then > > chris > Hi, ffmpeg does not compile with opencv 4.0.0 ffmpeg -pattern_type glob -r 3 -i "*.JPG" -vf "crop=256:170:0:0" -c:v libx264 -pix_fmt yuv420p mf2aou14th.mp4 ffmpeg: error while loading shared libraries: libopencv_imgproc.so.3.4: cannot open shared object file: No such file or directory trying to rebuild ffmpeg I get: ... ffmpeg-3.2.4/CONTRIBUTING.md patching file configure patching file libavcodec/libopenjpegdec.c patching file libavcodec/libopenjpegenc.c ERROR: opencv not found using pkg-config ln -s libopencv_imgproc.so.4.0.0 libopencv_imgproc.so.3.4 ln -s libopencv_core.so.4.0.0 libopencv_core.so.3.4 and voila From matteo.bernardini at gmail.com Sun Dec 16 17:32:36 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 16 Dec 2018 18:32:36 +0100 Subject: [Slackbuilds-users] Pokerth and its queue In-Reply-To: References: Message-ID: Il giorno dom 16 dic 2018 alle ore 17:36 Michael Langdon ha scritto: > > The info file for pokerth lists 4 dependencies: > > libgsasl > > libircclient > > tinyxml > > protobuf > > If I load its queue, that queue adds six more items: > > google-apputils > > python-gflags > > six > > setuptools-scm > > python-dateutil > > pytz > > My question is, why doesn't the queue match the info file? Because the pokerth.info file lists only direct dependencies, while the queue you cite most probably includes also dependencies of dependencies, and so on, recursively. > I can build > pokerth going by the requires from the info file, but it fails when > going by the queue. libircclient fails because it can't find openssl. > libircclient builds fine outside the queue. libircclient should build fine on slackware 14.2, it's on current that needs help to find the version of openssl that current ships http://cgit.ponce.cc/slackbuilds/commit/?h=libircclient Matteo From mikelangdon at roadrunner.com Sun Dec 16 17:58:37 2018 From: mikelangdon at roadrunner.com (Michael Langdon) Date: Sun, 16 Dec 2018 11:58:37 -0600 Subject: [Slackbuilds-users] Pokerth and its queue In-Reply-To: References: Message-ID: <70ede2d9-a585-28e7-ff41-987df2f8f654@roadrunner.com> I should have said I was running current. It built fine using only the info requires. I think I will stick with the info files and forget the queue. On 12/16/18 11:32 AM, Matteo Bernardini wrote: > Il giorno dom 16 dic 2018 alle ore 17:36 Michael Langdon > ha scritto: >> The info file for pokerth lists 4 dependencies: >> >> libgsasl >> >> libircclient >> >> tinyxml >> >> protobuf >> >> If I load its queue, that queue adds six more items: >> >> google-apputils >> >> python-gflags >> >> six >> >> setuptools-scm >> >> python-dateutil >> >> pytz >> >> My question is, why doesn't the queue match the info file? > Because the pokerth.info file lists only direct dependencies, while > the queue you cite most probably includes also dependencies of > dependencies, and so on, recursively. > >> I can build >> pokerth going by the requires from the info file, but it fails when >> going by the queue. libircclient fails because it can't find openssl. >> libircclient builds fine outside the queue. > libircclient should build fine on slackware 14.2, it's on current that > needs help to find the version of openssl that current ships > > http://cgit.ponce.cc/slackbuilds/commit/?h=libircclient > > Matteo > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From d.zlatanidis at gmail.com Sun Dec 16 19:54:10 2018 From: d.zlatanidis at gmail.com (Dimitris Zlatanidis) Date: Sun, 16 Dec 2018 20:54:10 +0100 Subject: [Slackbuilds-users] Pokerth and its queue In-Reply-To: <70ede2d9-a585-28e7-ff41-987df2f8f654@roadrunner.com> References: <70ede2d9-a585-28e7-ff41-987df2f8f654@roadrunner.com> Message-ID: Are you have try slpkg? # slpkg -s sbo pokerth On Sun, Dec 16, 2018, 19:01 Michael Langdon I should have said I was running current. It built fine using only the > info requires. I think I will stick with the info files and forget the > queue. > On 12/16/18 11:32 AM, Matteo Bernardini wrote: > > Il giorno dom 16 dic 2018 alle ore 17:36 Michael Langdon ha scritto: > > > The info file for pokerth lists 4 dependencies: > > libgsasl > > libircclient > > tinyxml > > protobuf > > If I load its queue, that queue adds six more items: > > google-apputils > > python-gflags > > six > > setuptools-scm > > python-dateutil > > pytz > > My question is, why doesn't the queue match the info file? > > > Because the pokerth.info file lists only direct dependencies, while > the queue you cite most probably includes also dependencies of > dependencies, and so on, recursively. > > > I can build > pokerth going by the requires from the info file, but it fails when > going by the queue. libircclient fails because it can't find openssl. > libircclient builds fine outside the queue. > > > libircclient should build fine on slackware 14.2, it's on current that > needs help to find the version of openssl that current ships > http://cgit.ponce.cc/slackbuilds/commit/?h=libircclient > > Matteo > _______________________________________________ > SlackBuilds-users mailing listSlackBuilds-users at slackbuilds.orghttps://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From chris.willing at linux.com Sun Dec 16 22:00:24 2018 From: chris.willing at linux.com (Christoph Willing) Date: Mon, 17 Dec 2018 08:00:24 +1000 Subject: [Slackbuilds-users] Updates - 20181215.1 (opencv) In-Reply-To: <20181216175123.edbb2655e702bf6c11ad7ad7@clansco.org> References: <5ea1b8ab-4f5b-42b2-88e3-9e4d9dae623e@slackbuilds.org> <47b719e2-618d-a8aa-aaea-edb173113fec@linux.com> <20181216175123.edbb2655e702bf6c11ad7ad7@clansco.org> Message-ID: On 17/12/18 2:51 am, Fr?d?ric Falsetti wrote: > On Sun, 16 Dec 2018 07:16:27 +1000 > Christoph Willing wrote: > >> On 15/12/18 11:56 pm, Willy Sudiarto Raharjo wrote: >> >>> libraries/opencv: Updated for version 4.0.0 >>> >> >> I'm sorry but there's a mistake in this update to opencv-4.0.0. I've >> pushed a correction but in the meantime it can be fixed by changing the >> line: >> if [ -d /usr/etc/qt5 ]; then >> to >> if [ -d /usr/include/qt5 ]; then >> >> chris >> > Hi, > ffmpeg does not compile with opencv 4.0.0 > > ffmpeg -pattern_type glob -r 3 -i "*.JPG" -vf "crop=256:170:0:0" -c:v libx264 -pix_fmt yuv420p mf2aou14th.mp4 > ffmpeg: error while loading shared libraries: libopencv_imgproc.so.3.4: cannot open shared object file: No such file or directory > > trying to rebuild ffmpeg I get: > ... > ffmpeg-3.2.4/CONTRIBUTING.md > patching file configure > patching file libavcodec/libopenjpegdec.c > patching file libavcodec/libopenjpegenc.c > ERROR: opencv not found using pkg-config > > ln -s libopencv_imgproc.so.4.0.0 libopencv_imgproc.so.3.4 > ln -s libopencv_core.so.4.0.0 libopencv_core.so.3.4 > and voila > Due to circular (optional) dependency between opencv & ffmpeg, I choose to use only the "opencv depends on ffmpeg" case. Therefore I didn't test the "ffmpeg depends on opencv" case when upgrading opencv to version 4.0.0. I guess ffmpeg devs will sort out that problem eventually. However in the meantime you could build ffmpeg with opencv-legacy instead to avoid opencv-4.0.0. chris From jebrhansen+SBo at gmail.com Mon Dec 17 00:50:10 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 16 Dec 2018 17:50:10 -0700 Subject: [Slackbuilds-users] Pokerth and its queue In-Reply-To: <70ede2d9-a585-28e7-ff41-987df2f8f654@roadrunner.com> References: <70ede2d9-a585-28e7-ff41-987df2f8f654@roadrunner.com> Message-ID: On Sun, Dec 16, 2018, 11:01 AM Michael Langdon wrote: > I should have said I was running current. It built fine using only the > info requires. I think I will stick with the info files and forget the > queue. > If you do that, things are *very* likely to break. The info file is only supposed to list dependencies that are specific to that package. If one of those dependencies have its own dependencies, they won't be listed in the parent info to minimize duplication. In this case, protobuf is a dependency if pokerth and it has several of its own dependencies: python-dateutil, google-apputils, python-gflags, and pytz. python-dateutil has two additional dependencies: six and setuptools-scm. If you don't build six and setuptools-scm, python-dateutil either won't build or could be broken. If you don't build python-dateutil along with google-apputils, python-gflags, and pytz, then protobuf may not build or be broken. That could cause pokerth to either not build, be broken, or could be missing functionality. Since you're running -current, if you weren't already aware, SBo doesn't reach -current at all and many things are broken on it. Matteo has an unofficial repo for -current where he tries to fix anything that's broken on -current, many times with help from others. Eventually, this work will end up becoming the official version on SBo for Slackware 15.0. If you haven't already, you really should check out his toys on the LQ forum as it discusses how to use his repo. https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ Good luck! Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikelangdon at roadrunner.com Mon Dec 17 04:40:36 2018 From: mikelangdon at roadrunner.com (Michael Langdon) Date: Sun, 16 Dec 2018 22:40:36 -0600 Subject: [Slackbuilds-users] Pokerth and its queue In-Reply-To: References: <70ede2d9-a585-28e7-ff41-987df2f8f654@roadrunner.com> Message-ID: <55c4ba6b-a055-2c5f-b11e-63bcffddeb72@roadrunner.com> Still, I have came up short in the explanation. The queue file came from 14.2. The requires file came from Ponce's repo. I used the repo files and used each and every build for those requires, then the pokerth build lastly from Ponce's repo. So I guess the next logical question would be if there is a way to call a queue from the repo, or create one. That's why I said I would use the requires from now on. If a build fails from a secondary dependency, it will be in the log. On 12/16/18 6:50 PM, Jeremy Hansen wrote: > > > On Sun, Dec 16, 2018, 11:01 AM Michael Langdon > > wrote: > > I should have said I was running current. It built fine using only > the info requires. I think I will stick with the info files and > forget the queue. > > If you do that, things are *very* likely to break. The info file is > only supposed to list dependencies that are specific to that package. > If one of those dependencies have its own dependencies, they won't be > listed in the parent info to minimize duplication. > > In this case, protobuf is a dependency if pokerth and it has several > of its own dependencies:?python-dateutil, google-apputils, > python-gflags, and pytz.?python-dateutil has two additional > dependencies:?six and setuptools-scm. > > If you don't build?six and setuptools-scm,?python-dateutil either > won't build or could be broken. If you don't build?python-dateutil > along with?google-apputils, python-gflags, and pytz, then protobuf may > not build or be broken. That could cause pokerth to either not build, > be broken, or could be missing functionality. > > Since you're running -current, if you weren't already aware, SBo > doesn't reach -current at all and many things are broken on it. Matteo > has an unofficial repo for -current where he tries to fix anything > that's broken on -current, many times with help from others. > Eventually, this work will end up becoming the official version on SBo > for Slackware 15.0. > > If you haven't already, you really should check out his toys on the LQ > forum as it discusses how to use his repo. > > https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ > > Good luck! > Jeremy > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From sababa.sababa at gmail.com Sat Dec 15 21:09:08 2018 From: sababa.sababa at gmail.com (Rick Hultgren) Date: Sat, 15 Dec 2018 22:09:08 +0100 Subject: [Slackbuilds-users] FOSS game Thrive Message-ID: Hello, Has anyone managed to install the open source game Thrive? Here is a wiki for the game: http://thrivegame.wikidot.com/ Thanks in advance for advices and tips! /Rickard -------------- next part -------------- An HTML attachment was scrubbed... URL: From psychi2009 at gmail.com Wed Dec 19 01:40:00 2018 From: psychi2009 at gmail.com (psychi) Date: Wed, 19 Dec 2018 09:40:00 +0800 Subject: [Slackbuilds-users] [Pull Request] network/Riot-web Message-ID: Hi repo admins, Here is the update of Riot-web's slackbuild I maintained , sent as pull request to the SBo repo on Gitlab.com . https://gitlab.com/SlackBuilds.org/slackbuilds/merge_requests/14 Commits: 1. fa73cbb0280da44ee3fa7f7aac6cd398e419d896 2. a60a90d5f292d6f6b77e6da806caac3eb8e1a488 See if this works. (They are PGP verified) Many thanks Psychi (mdrights) -- -- *[PGP key]* 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 - If I did not reply to you, please find another email address of mine. Cheers. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From psychi2009 at gmail.com Wed Dec 19 01:45:27 2018 From: psychi2009 at gmail.com (psychi) Date: Wed, 19 Dec 2018 09:45:27 +0800 Subject: [Slackbuilds-users] [Pull Request] network/Riot-web In-Reply-To: References: Message-ID: Oh sorry for this message. I didn't see Willy's response earlier. Will re-PR. Thanks. On Wed, 19 Dec 2018 at 09:40, psychi wrote: > Hi repo admins, > > Here is the update of Riot-web's slackbuild I maintained , sent as pull > request to the SBo repo on Gitlab.com . > > https://gitlab.com/SlackBuilds.org/slackbuilds/merge_requests/14 > > Commits: > 1. fa73cbb0280da44ee3fa7f7aac6cd398e419d896 > 2. a60a90d5f292d6f6b77e6da806caac3eb8e1a488 > > See if this works. (They are PGP verified) > Many thanks > > Psychi (mdrights) > > -- > -- > *[PGP key]* > 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 > > - If I did not reply to you, please find another email address of mine. > > Cheers. > -- > > > -- -- *[PGP key]* 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 - If I did not reply to you, please find another email address of mine. Cheers. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Wed Dec 19 01:47:35 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 19 Dec 2018 08:47:35 +0700 Subject: [Slackbuilds-users] [Pull Request] network/Riot-web In-Reply-To: References: Message-ID: > Here is the update of? Riot-web's slackbuild I maintained , sent as pull > request to the SBo repo on Gitlab.com . > > https://gitlab.com/SlackBuilds.org/slackbuilds/merge_requests/14 > > Commits: > 1. fa73cbb0280da44ee3fa7f7aac6cd398e419d896 > 2. a60a90d5f292d6f6b77e6da806caac3eb8e1a488 > > See if this works. (They are PGP verified) > Many thanks Hi Psychi I made a comment last night of this pull request please check my comment and work through it before i can merge it. 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 slackalaxy at gmail.com Wed Dec 19 10:53:28 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Wed, 19 Dec 2018 12:53:28 +0200 Subject: [Slackbuilds-users] fastqc and future changes Message-ID: hi all, i am giving maintenance of fastqc to Rob (sborg63). Also, we have been discussing some rearrangements in the last week. The idea is that he submits updated versions of bowtie2, samtools and co, while I make mine into *-legacy SlackBuilds, to be used only with Ugene. Ugene still requires the older versions, and this is the reason I kept these to the old versions for so long. I hope to be ready in the next few days (well probably a bit longer)... -petar From kd5zex at gmail.com Wed Dec 19 12:06:27 2018 From: kd5zex at gmail.com (Alan Dingeldein) Date: Wed, 19 Dec 2018 06:06:27 -0600 Subject: [Slackbuilds-users] FOSS game Thrive In-Reply-To: References: Message-ID: >> managed to install the open source game Thrive? Looks like it needs 32 bit libraries. --Alan On Tue, Dec 18, 2018 at 12:21 PM Rick Hultgren wrote: > Hello, > > Has anyone managed to install the open source game Thrive? Here is a wiki > for the game: > > http://thrivegame.wikidot.com/ > > Thanks in advance for advices and tips! > > /Rickard > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Wed Dec 19 16:05:20 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 19 Dec 2018 08:05:20 -0800 (PST) Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 Message-ID: I tried viewing a graphviz .dot file and was told the application was not found. It is installed: $ ls /var/log/packages/ | grep graphviz graphviz-2.40.1-i586-1_SBo So, I rebuilt and re-installed it but it's still not found. Here's what are found: # find / -name graphviz /etc/file/magic/graphviz /etc/asciidoc/filters/graphviz /var/lib/sbopkg/SBo/14.2/graphics/graphviz /var/cache/packages/SLACKPKGPLUS_slacky/graphic/graphviz /opt/slackbuilds/Graphics/graphviz /usr/include/graphviz /usr/lib/graphviz /usr/lib/graphviz/java/org/graphviz /usr/lib/tcl8.6/graphviz /usr/share/graphviz /usr/share/texmf-dist/tex/latex/graphviz Why might there be no executable in /usr/bin/? How do I find the source of this issue? TIA, Rich From matteo.bernardini at gmail.com Wed Dec 19 16:13:11 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 19 Dec 2018 17:13:11 +0100 Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: References: Message-ID: Il giorno mer 19 dic 2018 alle ore 17:05 Rich Shepard ha scritto: > > I tried viewing a graphviz .dot file and was told the application was not > found. It is installed: > > $ ls /var/log/packages/ | grep graphviz > graphviz-2.40.1-i586-1_SBo > > So, I rebuilt and re-installed it but it's still not found. Here's what > are found: > > # find / -name graphviz > /etc/file/magic/graphviz > /etc/asciidoc/filters/graphviz > /var/lib/sbopkg/SBo/14.2/graphics/graphviz > /var/cache/packages/SLACKPKGPLUS_slacky/graphic/graphviz > /opt/slackbuilds/Graphics/graphviz > /usr/include/graphviz > /usr/lib/graphviz > /usr/lib/graphviz/java/org/graphviz > /usr/lib/tcl8.6/graphviz > /usr/share/graphviz > /usr/share/texmf-dist/tex/latex/graphviz > > Why might there be no executable in /usr/bin/? How do I find the source of > this issue? there's no graphviz executable in the graphviz package... what does the following command outputs on your system? grep ^usr\/bin\/ /var/log/packages/graphviz* Matteo From slackbuilds at jaxartes.net Wed Dec 19 16:20:31 2018 From: slackbuilds at jaxartes.net (Benjamin Trigona-Harany) Date: Wed, 19 Dec 2018 08:20:31 -0800 Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: References: Message-ID: <2955617.NsAoFCPf2o@wintermute.sprawl.net> On Wednesday, 19 December 2018 08:05:20 PST Rich Shepard wrote: > I tried viewing a graphviz .dot file and was told the application was not > found. It is installed: > > $ ls /var/log/packages/ | grep graphviz > graphviz-2.40.1-i586-1_SBo > > So, I rebuilt and re-installed it but it's still not found. Here's what > are found: > > # find / -name graphviz > /etc/file/magic/graphviz > /etc/asciidoc/filters/graphviz > /var/lib/sbopkg/SBo/14.2/graphics/graphviz > /var/cache/packages/SLACKPKGPLUS_slacky/graphic/graphviz > /opt/slackbuilds/Graphics/graphviz > /usr/include/graphviz > /usr/lib/graphviz > /usr/lib/graphviz/java/org/graphviz > /usr/lib/tcl8.6/graphviz > /usr/share/graphviz > /usr/share/texmf-dist/tex/latex/graphviz > > Why might there be no executable in /usr/bin/? How do I find the source > of this issue? The better way of finding executables is grep bin /var/log/packages/graphviz- *. You'll see that graphviz ships with many executables - but that none of them are named "graphviz". Ben From matteo.bernardini at gmail.com Wed Dec 19 16:17:26 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 19 Dec 2018 17:17:26 +0100 Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: References: Message-ID: Il giorno mer 19 dic 2018 alle ore 17:13 Matteo Bernardini ha scritto: > > Il giorno mer 19 dic 2018 alle ore 17:05 Rich Shepard > ha scritto: > > > > I tried viewing a graphviz .dot file and was told the application was not > > found. It is installed: > > > > $ ls /var/log/packages/ | grep graphviz > > graphviz-2.40.1-i586-1_SBo > > > > So, I rebuilt and re-installed it but it's still not found. Here's what > > are found: > > > > # find / -name graphviz > > /etc/file/magic/graphviz > > /etc/asciidoc/filters/graphviz > > /var/lib/sbopkg/SBo/14.2/graphics/graphviz > > /var/cache/packages/SLACKPKGPLUS_slacky/graphic/graphviz > > /opt/slackbuilds/Graphics/graphviz > > /usr/include/graphviz > > /usr/lib/graphviz > > /usr/lib/graphviz/java/org/graphviz > > /usr/lib/tcl8.6/graphviz > > /usr/share/graphviz > > /usr/share/texmf-dist/tex/latex/graphviz > > > > Why might there be no executable in /usr/bin/? How do I find the source of > > this issue? > > there's no graphviz executable in the graphviz package... > what does the following command outputs on your system? > > grep ^usr\/bin\/ /var/log/packages/graphviz* also, the first result of googling "view a graphviz dot file" is this https://github.com/rakhimov/cppdep/wiki/How-to-view-or-work-with-Graphviz-Dot-files https://slackbuilds.org/repository/14.2/graphics/xdot/ Matteo From rshepard at appl-ecosys.com Wed Dec 19 16:24:53 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 19 Dec 2018 08:24:53 -0800 (PST) Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: References: Message-ID: On Wed, 19 Dec 2018, Matteo Bernardini wrote: > there's no graphviz executable in the graphviz package... what does the > following command outputs on your system? > grep ^usr\/bin\/ /var/log/packages/graphviz* Matteo, It's been a while since I last used graphviz so I checked the docs. That suggested there is an executable. But, not here: # grep ^usr\/bin\/ /var/log/packages/graphviz* usr/bin/ usr/bin/acyclic usr/bin/bcomps usr/bin/ccomps usr/bin/cluster usr/bin/diffimg usr/bin/dijkstra usr/bin/dot usr/bin/dot_builtins usr/bin/dotty usr/bin/edgepaint usr/bin/gc usr/bin/gml2gv usr/bin/graphml2gv usr/bin/gv2gml usr/bin/gvcolor usr/bin/gvedit usr/bin/gvgen usr/bin/gvmap usr/bin/gvmap.sh usr/bin/gvpack usr/bin/gvpr usr/bin/gxl2gv usr/bin/lefty usr/bin/lneato usr/bin/mm2gv usr/bin/nop usr/bin/prune usr/bin/sccmap usr/bin/tred usr/bin/unflatten usr/bin/vimdot Regards, Rich From rshepard at appl-ecosys.com Wed Dec 19 16:27:44 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 19 Dec 2018 08:27:44 -0800 (PST) Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: <2955617.NsAoFCPf2o@wintermute.sprawl.net> References: <2955617.NsAoFCPf2o@wintermute.sprawl.net> Message-ID: On Wed, 19 Dec 2018, Benjamin Trigona-Harany wrote: > The better way of finding executables is grep bin /var/log/packages/graphviz- > *. Ben, So I have just learned. > You'll see that graphviz ships with many executables - but that none of > them are named "graphviz". Back to re-reading the docs. Thanks, Rich From didier at slint.fr Wed Dec 19 16:35:03 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 19 Dec 2018 17:35:03 +0100 Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: References: Message-ID: <3a2d9065-9ae7-3e1f-679d-ac63938d1501@slint.fr> On 19/12/2018 17:24, Rich Shepard wrote: > ? It's been a while since I last used graphviz so I checked the docs. That > suggested there is an executable. There of course many executable, but bone named graphviz, period. To know more, read: https://graphviz.gitlab.io/documentation/ Didier From didier at slint.fr Wed Dec 19 17:05:33 2018 From: didier at slint.fr (Didier Spaier) Date: Wed, 19 Dec 2018 18:05:33 +0100 Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: <3a2d9065-9ae7-3e1f-679d-ac63938d1501@slint.fr> References: <3a2d9065-9ae7-3e1f-679d-ac63938d1501@slint.fr> Message-ID: On 19/12/2018 17:35, Didier Spaier wrote: > To know more, read: > https://graphviz.gitlab.io/documentation/ There is also an excellent documentation is the package: firefox /usr/doc/graphviz-2.40.1/html/index.html Didier From rshepard at appl-ecosys.com Wed Dec 19 17:21:12 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 19 Dec 2018 09:21:12 -0800 (PST) Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: References: <3a2d9065-9ae7-3e1f-679d-ac63938d1501@slint.fr> Message-ID: On Wed, 19 Dec 2018, Didier Spaier wrote: > There is also an excellent documentation is the package: > firefox /usr/doc/graphviz-2.40.1/html/index.html Didier, Thanks. Rich From rshepard at appl-ecosys.com Wed Dec 19 17:22:37 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 19 Dec 2018 09:22:37 -0800 (PST) Subject: [Slackbuilds-users] Strange issue with graphviz-2.40.1 In-Reply-To: References: Message-ID: On Wed, 19 Dec 2018, Matteo Bernardini wrote: > also, the first result of googling "view a graphviz dot file" is this > https://github.com/rakhimov/cppdep/wiki/How-to-view-or-work-with-Graphviz-Dot-files > https://slackbuilds.org/repository/14.2/graphics/xdot/ Matteo, Thank you. As I wrote, it's been a long time since I last used graphviz and I forgot that it's a package of tools, the same as ImageMagick is. Regards, Rich From lists at osh.id.au Wed Dec 19 18:37:38 2018 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 19 Dec 2018 13:37:38 -0500 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: References: Message-ID: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> On Fri, 14 Dec 2018, at 5:44 PM, JCA wrote: > The version of the Chromium from Slackbuilds is 53, whereas the latest is 71. I.e. 53 is well over two years old. Why is it being kept that old, especially bearing in mind that Slackware packages for the latest Chromium may be downloaded from http://www.slackware.com/~alien/slackbuilds/chromium. I mean, what is the point of keeping such an old version in Slackbuilds? Hard to say, I also think that it should be dropped. For many packages it seems quite alright to be behind the latest version, but I don't think a web browser is one of those packages (security comes to mind). -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Wed Dec 19 18:52:33 2018 From: 1.41421 at gmail.com (JCA) Date: Wed, 19 Dec 2018 11:52:33 -0700 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> Message-ID: Why not simply officially adopt the AlienBob version? On Wed, Dec 19, 2018 at 11:38 AM David O'Shaughnessy wrote: > On Fri, 14 Dec 2018, at 5:44 PM, JCA wrote: > > The version of the Chromium from Slackbuilds is 53, whereas the latest is > 71. I.e. 53 is well over two years old. Why is it being kept that old, > especially bearing in mind that Slackware packages for the latest Chromium > may be downloaded from > http://www.slackware.com/~alien/slackbuilds/chromium. I mean, what is the > point of keeping such an old version in Slackbuilds? > > > Hard to say, I also think that it should be dropped. For many packages it > seems quite alright to be behind the latest version, but I don't think a > web browser is one of those packages (security comes to mind). > > -- > Dave > _______________________________________________ > 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 slackalaxy at gmail.com Wed Dec 19 20:55:36 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Wed, 19 Dec 2018 22:55:36 +0200 Subject: [Slackbuilds-users] muParser and future of QtiPlot Message-ID: Hi to all, i prepared an update of my muParser.SlackBuild for version 2.2.6.1. It builds fine, however QtiPlot which depends on muParser breaks when building against the new version. Now, I have these options: 1) I can build the old version muParser into QtiPlot. In this case, I will not have any reason to maintain the separate muparser, so I will give it to someone else. 2) I can try to find a solution for QtiPlot to build against newest muParser. This will take time. 3) I can just leave things as they are. A few notes. Most of the distros, stick with the older version of the library, so maybe we should too for now? Also, QtiPlot is very old and the publicly available source code is no longer maintained. The developer changed the license some time ago, so the version we have at SBo is the last with available source code. Even now, it requires a lot of patches and at a certain point in the future it will be no longer possible to build. I guess we should just drop it then. We have SciDAVis, which is a fork of QtiPlot and it seems quite good. What would you advise me to do? -petar From jebrhansen+SBo at gmail.com Wed Dec 19 23:00:32 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 19 Dec 2018 16:00:32 -0700 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> Message-ID: On Wed, Dec 19, 2018, 1:55 PM JCA <1.41421 at gmail.com> wrote: > Why not simply officially adopt the AlienBob version? > His SlackBuilds typically go against SBo requirements, namely downloading things within the SlackBuild script. There's nothing wrong with doing that, it's just not allowed by SBo. On Wed, Dec 19, 2018 at 11:38 AM David O'Shaughnessy > wrote: > >> On Fri, 14 Dec 2018, at 5:44 PM, JCA wrote: >> >> The version of the Chromium from Slackbuilds is 53, whereas the latest is >> 71. I.e. 53 is well over two years old. Why is it being kept that old, >> especially bearing in mind that Slackware packages for the latest Chromium >> may be downloaded from >> http://www.slackware.com/~alien/slackbuilds/chromium. I mean, what is >> the point of keeping such an old version in Slackbuilds? >> >> >> Hard to say, I also think that it should be dropped. For many packages it >> seems quite alright to be behind the latest version, but I don't think a >> web browser is one of those packages (security comes to mind). >> > It should be dropped if that maintainer isn't willing to keep it up and no one else is willing to pick it up. It hasn't been updated in over 2 years! We shouldn't keep something on here that is chalked full of security issues just to keep chromium on SBo. If it isn't going to be updated, it should just be removed. -------- Another option is to simply do a repackaging of Eric's chromium package, but if someone is willing to pick that up, they'd probably want to verify with Eric that he's ok with his package being repackaged and find out what server it should be hosted on. They'd also want to make sure they keep up with his releases, since he removes older versions when he releases new ones (or host the build somewhere else so it can survive until they can update to match his version). Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From psychi2009 at gmail.com Wed Dec 19 23:54:09 2018 From: psychi2009 at gmail.com (psychi) Date: Thu, 20 Dec 2018 07:54:09 +0800 Subject: [Slackbuilds-users] [Pull Request] network/Riot-web In-Reply-To: References: Message-ID: Hi Willy, I had re-requsted. Please take a look. (!15) Many thanks Psychi On Wed, 19 Dec 2018 at 09:47, Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Here is the update of Riot-web's slackbuild I maintained , sent as pull > > request to the SBo repo on Gitlab.com . > > > > https://gitlab.com/SlackBuilds.org/slackbuilds/merge_requests/14 > > > > Commits: > > 1. fa73cbb0280da44ee3fa7f7aac6cd398e419d896 > > 2. a60a90d5f292d6f6b77e6da806caac3eb8e1a488 > > > > See if this works. (They are PGP verified) > > Many thanks > > Hi Psychi > > I made a comment last night of this pull request > please check my comment and work through it before i can merge it. > > Thanks > > > -- > 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/ > > -- -- *[PGP key]* 04FD A83E F2D3 1DAE 43AC CCC4 F04F AA0B 9F11 6EF5 - If I did not reply to you, please find another email address of mine. Cheers. -- -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim.diamond at acadiau.ca Thu Dec 20 00:06:11 2018 From: jim.diamond at acadiau.ca (James Diamond) Date: Thu, 20 Dec 2018 00:06:11 +0000 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> Message-ID: <20181220000609.GB9189@jdiamond-mb.acadiau.ca> On Wed, Dec 19, 2018 at 16:00 (-0700), Jeremy Hansen wrote: > On Wed, Dec 19, 2018, 1:55 PM JCA <1.41421 at gmail.com> wrote: >> Why not simply officially adopt the AlienBob version? > His SlackBuilds typically go against SBo requirements, namely downloading > things within the SlackBuild script. There's nothing wrong with doing that, > it's just not allowed by SBo. Just out of curiosity, why is that not allowed? I can see a certain virtue in consistency of action, but at the same time, there are things to be said for reducing tedious activities. (Thus, I suppose, the reason for tools that download the SBo information, figure out what needs to be downloaded, downloading it if it is not already downloaded, and then doing the build.) Cheers Jim From fellype at gmail.com Thu Dec 20 00:21:05 2018 From: fellype at gmail.com (Fellype) Date: Wed, 19 Dec 2018 22:21:05 -0200 Subject: [Slackbuilds-users] muParser and future of QtiPlot In-Reply-To: References: Message-ID: Hi Petar, Em qua, 19 de dez de 2018 ?s 18:55, Petar Petrov escreveu: > Hi to all, > > i prepared an update of my muParser.SlackBuild for version 2.2.6.1. It > builds fine, however QtiPlot which depends on muParser breaks when > building against the new version. Now, I have these options: > > 1) I can build the old version muParser into QtiPlot. In this case, I > will not have any reason to maintain the separate muparser, so I will > give it to someone else. > 2) I can try to find a solution for QtiPlot to build against newest > muParser. This will take time. > 3) I can just leave things as they are. > > A few notes. Most of the distros, stick with the older version of the > library, so maybe we should too for now? Also, QtiPlot is very old and > the publicly available source code is no longer maintained. The > developer changed the license some time ago, so the version we have at > SBo is the last with available source code. Even now, it requires a > lot of patches and at a certain point in the future it will be no > longer possible to build. I guess we should just drop it then. We have > SciDAVis, which is a fork of QtiPlot and it seems quite good. > > What would you advise me to do? > > Unfortunately QtiPlot did a bad move when it adopted a non-free license (IMHO). As the maintainer of SciDAVis at SBo, my suggestion is that you choose option 3 - just leave things as they are, at least until the next Slackware release. Then, if you find it not worth the effort to adopt none of the options 1 or 2, drop QtiPlot and update muParser (or give it for another maintainer). Knowing the qtiplot build script, I call you hero for keeping it running for so long :-) The other software at SBo I could find that depends on MuParser are: OTB librecad meshlab It would be interesting to have feedback from maintainers of those in relation to the muParser version. It would be helpful if statistics were available on the use of QtiPlot (and any other software, of course) at SBo. Best regards, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Thu Dec 20 00:40:58 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 19 Dec 2018 17:40:58 -0700 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: <20181220000609.GB9189@jdiamond-mb.acadiau.ca> References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> <20181220000609.GB9189@jdiamond-mb.acadiau.ca> Message-ID: On Wed, Dec 19, 2018, 5:06 PM James Diamond via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > On Wed, Dec 19, 2018 at 16:00 (-0700), Jeremy Hansen wrote: > > > On Wed, Dec 19, 2018, 1:55 PM JCA <1.41421 at gmail.com> wrote: > > >> Why not simply officially adopt the AlienBob version? > > > His SlackBuilds typically go against SBo requirements, namely downloading > > things within the SlackBuild script. There's nothing wrong with doing > that, > > it's just not allowed by SBo. > > Just out of curiosity, why is that not allowed? I can see a certain > virtue in consistency of action, but at the same time, there are > things to be said for reducing tedious activities. (Thus, I suppose, > the reason for tools that download the SBo information, figure out > what needs to be downloaded, downloading it if it is not already > downloaded, and then doing the build.) > Between downloading the SlackBuilds tarball from the site and downloading the files in the .info, everything should be able to be done offline. They do not want the scripts to be downloading things while they run... everything that needs to be downloaded needs to be listed in the .info. With a quick run through the site, I didn't see any official documentation that spells this out specifically, but I have seen it mentioned many times in this mailing list as something to be corrected when it slips by (many times with python packages). > -------------- next part -------------- An HTML attachment was scrubbed... URL: From jim.diamond at acadiau.ca Thu Dec 20 00:57:37 2018 From: jim.diamond at acadiau.ca (James Diamond) Date: Thu, 20 Dec 2018 00:57:37 +0000 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> <20181220000609.GB9189@jdiamond-mb.acadiau.ca> Message-ID: <20181220005734.GA11815@jdiamond-mb.acadiau.ca> On Wed, Dec 19, 2018 at 17:40 (-0700), Jeremy Hansen wrote: > On Wed, Dec 19, 2018, 5:06 PM James Diamond via SlackBuilds-users < > slackbuilds-users at slackbuilds.org> wrote: >> On Wed, Dec 19, 2018 at 16:00 (-0700), Jeremy Hansen wrote: >>> On Wed, Dec 19, 2018, 1:55 PM JCA <1.41421 at gmail.com> wrote: >>>> Why not simply officially adopt the AlienBob version? >>> His SlackBuilds typically go against SBo requirements, namely downloading >>> things within the SlackBuild script. There's nothing wrong with doing >> that, >>> it's just not allowed by SBo. >> Just out of curiosity, why is that not allowed? I can see a certain >> virtue in consistency of action, but at the same time, there are >> things to be said for reducing tedious activities. (Thus, I suppose, >> the reason for tools that download the SBo information, figure out >> what needs to be downloaded, downloading it if it is not already >> downloaded, and then doing the build.) > Between downloading the SlackBuilds tarball from the site and > downloading the files in the .info, everything should be able to be > done offline. They do not want the scripts to be downloading things > while they run... everything that needs to be downloaded needs to > be listed in the .info. Sure, but that is more of a description of "what they say", as opposed to "why they say it". I'm really interested in the rationale, although as you say... > With a quick run through the site, I didn't see any official > documentation that spells this out specifically, but I have seen it > mentioned many times in this mailing list as something to be > corrected when it slips by (many times with python packages). Thanks for your thoughts. Jim From jebrhansen+SBo at gmail.com Thu Dec 20 01:06:28 2018 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 19 Dec 2018 18:06:28 -0700 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: <20181220005734.GA11815@jdiamond-mb.acadiau.ca> References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> <20181220000609.GB9189@jdiamond-mb.acadiau.ca> <20181220005734.GA11815@jdiamond-mb.acadiau.ca> Message-ID: On Wed, Dec 19, 2018, 5:57 PM James Diamond via SlackBuilds-users < slackbuilds-users at slackbuilds.org> wrote: > On Wed, Dec 19, 2018 at 17:40 (-0700), Jeremy Hansen wrote: > > > On Wed, Dec 19, 2018, 5:06 PM James Diamond via SlackBuilds-users < > > slackbuilds-users at slackbuilds.org> wrote: > > >> On Wed, Dec 19, 2018 at 16:00 (-0700), Jeremy Hansen wrote: > > >>> On Wed, Dec 19, 2018, 1:55 PM JCA <1.41421 at gmail.com> wrote: > > >>>> Why not simply officially adopt the AlienBob version? > > >>> His SlackBuilds typically go against SBo requirements, namely > downloading > >>> things within the SlackBuild script. There's nothing wrong with doing > >> that, > >>> it's just not allowed by SBo. > > >> Just out of curiosity, why is that not allowed? I can see a certain > >> virtue in consistency of action, but at the same time, there are > >> things to be said for reducing tedious activities. (Thus, I suppose, > >> the reason for tools that download the SBo information, figure out > >> what needs to be downloaded, downloading it if it is not already > >> downloaded, and then doing the build.) > > > Between downloading the SlackBuilds tarball from the site and > > downloading the files in the .info, everything should be able to be > > done offline. They do not want the scripts to be downloading things > > while they run... everything that needs to be downloaded needs to > > be listed in the .info. > > Sure, but that is more of a description of "what they say", as opposed > to "why they say it". I'm really interested in the rationale, > although as you say... > > > With a quick run through the site, I didn't see any official > > documentation that spells this out specifically, but I have seen it > > mentioned many times in this mailing list as something to be > > corrected when it slips by (many times with python packages). > > Thanks for your thoughts. > Just a thought, but any file in the .info is required to have an MD5SUM. This ensures the file has remained untouched from when the maintainer tested it. If files are downloaded within the script, you can't verify that those files are unmodified. This could mean simply that the files have been updated and have not been verified to work properly, but it can also mean that the files have been tampered with and may pose a threat to the system. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From slackalaxy at gmail.com Thu Dec 20 06:24:16 2018 From: slackalaxy at gmail.com (Petar Petrov) Date: Thu, 20 Dec 2018 08:24:16 +0200 Subject: [Slackbuilds-users] muParser and future of QtiPlot In-Reply-To: References: Message-ID: Hi Fellype, > Knowing the qtiplot build script, I call you hero for keeping > it running for so long :-) I did put some effort into QtiPlot.SlackBuild, but it was the SBo core team that took care of fixes between Slackware releases. Just wanted to be fair :) ok, I will leave muParser as it is for now. -petar On 20/12/2018, Fellype wrote: > Hi Petar, > > Em qua, 19 de dez de 2018 ?s 18:55, Petar Petrov > escreveu: > >> Hi to all, >> >> i prepared an update of my muParser.SlackBuild for version 2.2.6.1. It >> builds fine, however QtiPlot which depends on muParser breaks when >> building against the new version. Now, I have these options: >> >> 1) I can build the old version muParser into QtiPlot. In this case, I >> will not have any reason to maintain the separate muparser, so I will >> give it to someone else. >> 2) I can try to find a solution for QtiPlot to build against newest >> muParser. This will take time. >> 3) I can just leave things as they are. >> >> A few notes. Most of the distros, stick with the older version of the >> library, so maybe we should too for now? Also, QtiPlot is very old and >> the publicly available source code is no longer maintained. The >> developer changed the license some time ago, so the version we have at >> SBo is the last with available source code. Even now, it requires a >> lot of patches and at a certain point in the future it will be no >> longer possible to build. I guess we should just drop it then. We have >> SciDAVis, which is a fork of QtiPlot and it seems quite good. >> >> What would you advise me to do? >> >> Unfortunately QtiPlot did a bad move when it adopted a non-free license > (IMHO). > As the maintainer of SciDAVis at SBo, my suggestion is that you choose > option 3 - just leave things as they are, at least until the next Slackware > release. Then, if you find it not worth the effort to adopt none of the > options 1 or 2, drop QtiPlot and update muParser (or give it for another > maintainer). Knowing the qtiplot build script, I call you hero for keeping > it running for so long :-) > The other software at SBo I could find that depends on MuParser are: > OTB > librecad > meshlab > > It would be interesting to have feedback from maintainers of those in > relation to the muParser version. > It would be helpful if statistics were available on the use of QtiPlot (and > any other software, of course) at SBo. > > Best regards, > > Fellype > From didier at slint.fr Thu Dec 20 07:14:04 2018 From: didier at slint.fr (Didier Spaier) Date: Thu, 20 Dec 2018 08:14:04 +0100 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> <20181220000609.GB9189@jdiamond-mb.acadiau.ca> <20181220005734.GA11815@jdiamond-mb.acadiau.ca> Message-ID: Hello, On 20/12/2018 02:06, Jeremy Hansen wrote: >>> With a quick run through the site, I didn't see any official >>> documentation that spells this out specifically, but I have seen it >>> mentioned many times in this mailing list as something to be >>> corrected when it slips by (many times with python packages). Well, if you mean using pip, I am also against that, at least if not with virtualenv ;) As an aside, I try to avoid getting sources from "anonymous" places. Yesterday I packaged mps-youtube and its dependency Pafy. Both .info mention a source archive downloaded from Pypi. Even though the author suggests using pip for installation I preferred to get the source archives from GitHub. Is it only me? > Just a thought, but any file in the .info is required to have an MD5SUM. > This ensures the file has remained untouched from when the maintainer > tested it. If files are downloaded within the script, you can't verify that > those files are unmodified. > > This could mean simply that the files have been updated and have not been > verified to work properly, but it can also mean that the files have been > tampered with and may pose a threat to the system. Yes, but exceptio probat regulam. As an example, the author of emacs-w3m does not make releases anymore since a long time. As a result, emacs-w3m.info mentions a very old source archive. To package it, I did this instead (as suggested by the author): cvs -d :pserver:anonymous at cvs.namazu.org:/storage/cvsroot co emacs-w3m And also: VERSION=$(stat -c %y $PRGNAM/ChangeLog|sed "s/ .*//;s/-//g") I can understand that this be not acceptable @ SBo, but maybe in such a case the README could just mention this as an alternate way to get the source. Best, Didier From didier at slint.fr Thu Dec 20 08:05:14 2018 From: didier at slint.fr (Didier Spaier) Date: Thu, 20 Dec 2018 09:05:14 +0100 Subject: [Slackbuilds-users] Chromium in Slackbuilds In-Reply-To: References: <025d1ba9-776e-4fad-a51f-39d62a98cf36@sloti2d1t19> <20181220000609.GB9189@jdiamond-mb.acadiau.ca> <20181220005734.GA11815@jdiamond-mb.acadiau.ca> Message-ID: <76192424-3390-6033-2f5c-0c467845aad1@slint.fr> On 20/12/2018 08:14, Didier Spaier wrote: > Even though the author suggests using pip for installation I preferred > to get the source archives from GitHub. Well, actually this is suggested for end users if I understand well. From willysr at slackbuilds.org Sat Dec 22 02:00:16 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Dec 2018 09:00:16 +0700 Subject: [Slackbuilds-users] Updates - 20181222.1 Message-ID: <280aebcb-d130-4067-fb9c-9d94fb863ef7@slackbuilds.org> Hi We have finally removed chromium from SBo repository after we failed to get any contact with the maintainer and the current version is way behind upstream latest stable releases. Anyone who wanted to submit a new version is welcome to do so, but please make sure it's updated along with upstream. Google Go 1.11.4 is a security update, so please make sure to upgrade them. LibreOffice is updated to latest 6.1.4 version for binary repackaging, while source-based compilation is following soon. Latest work on docker is also included in this update. have a nice weekend Sat Dec 22 17:45:12 UTC 2018 academic/boinc: Updated for version 7.14.2. academic/cryptominisat: Updated for version 5.6.6. academic/fastqc: Updated for version 0.11.8 + new maintainer. academic/pulseview: Updated for version 0.4.1. academic/sigrok-cli: Updated for version 0.7.1. audio/caps: Updated for version 0.9.26. audio/drumkv1: Updated for version 0.9.4. audio/mixxx: Updated for version 2.1.5. audio/padthv1: Added (polyphonic synthesizer). audio/qtractor: Updated for version 0.9.2. audio/samplv1: Updated for version 0.9.4. audio/sonic-visualiser: Updated for version 3.2. audio/synthv1: Updated for version 0.9.4. desktop/Zafiro-icons: Updated for version 0.7.7. desktop/gnome-menus: Updated for version 3.31.3. desktop/oranchelo-icon-theme: Updated for version 0.7.9. desktop/qt5ct: Updated for version 0.37. desktop/skippy-xd: Updated for version 2016.10.20. development/chicken: Updated for version 5.0.0. development/google-go-lang: Updated to version 1.11.4 development/hhvm: Updated for version 3.30.1 development/hugo: Updated for version 0.52. development/jupyter-nbdime: Updated for version 1.0.4. development/jupyter-notebook: Updated for version 5.7.4. development/npm2tgz: Updated for version 1.3.5. development/rustup: Updated for version 1.16.0. development/sphinx_rtd_theme: Updated for version 0.4.2. development/tea: Updated for version 47.0.1. development/universal-ctags: Updated for version 321eeac games/dhewm3: Updated for version 1.5.0. games/doomseeker: Updated for version 1.2. games/mednafen: Updated for version 1.21.3. games/mednaffe: Added (frontend for mednafen). games/minetest: Updated for version 0.4.17.1. games/minetest_game: Updated for version 0.4.17.1. games/pcsx2: Remove old patch. games/srb2: Added (Sonic Robo Blast 2 game). games/teeworlds: Updated for version 0.7.1. gis/geopy: Updated for version 1.18.1. gis/ossim: Remove test binaries. graphics/deskew: Updated for version 1.25. libraries/hoel: Updated for version 1.4.8. libraries/libuv: Updated for version 1.24.1. libraries/lua-cjson: Added (JSON support for Lua). libraries/opencv: Fix condition to apply patch libraries/ulfius: Updated for version 2.5.1. libraries/wxSQLite3: Updated for version 4.4.0. libraries/zeromq: Updated for version 4.3.0. multimedia/ffmpeg4: Update to allow building with libaom. multimedia/mkvtoolnix: Make use the examples and man pages. multimedia/pepperflash-plugin: Added a note to the README. multimedia/smtube: Updated for version 18.11.0. network/chromium: Removed. network/glewlwyd: Updated for version 1.4.9. network/krb5: Updated for version 1.16.2. network/netsurf: Updated for version 3.8. network/opera-developer: Updated for version 59.0.3173.0. network/opera: Updated for version 57.0.3098.106. network/prosody: Change makefile name in doinst.sh. network/riot-web: Updated for version 0.17.8. network/telegram: Updated for version 1.5.2. network/vivaldi: Updated for version 2.2.1388.37. network/waterfox: Updated for version 56.2.6. network/yadifa: Updated for version 2.3.8-7713. office/libreoffice-helppack: Updated for version 6.1.4. office/libreoffice-langpack: Updated for version 6.1.4. office/libreoffice: Updated for version 6.1.4. office/lyx: Updated for version 2.3.2. office/onlyoffice-desktopeditors: Updated for version 5.2.4. perl/perl-CPAN-Perl-Releases: Updated for version 3.86. perl/perl-Module-ScanDeps: Updated for version 1.26. perl/perlbrew: Updated for version 0.85. python/affine: Updated for version 2.2.2. python/mypy: Updated for version 0.650. python/python-fonttools: Updated for version 3.34.2. python/python3-Pygments: Updated for version 2.3.1. python/python3-jedi: Updated for version 0.13.2. python/python3-pylint: Updated for version 2.2.2. python/scikit-learn: Updated for version 0.20.2. system/chipsec: Updated for version 1.3.6. system/chronograf: Updated for version 1.7.5. system/containerd: Updated for version 1.1.2. system/docker-machine-kvm: Updated libraries. system/docker-machine: Updated for version 0.16.0. system/docker-proxy: Updated for version 20181015_6da50d1. system/docker: Updated for version 18.09.0. system/epson-inkjet-printer-escpr: Updated for version 1.6.33. system/fatrace: Added (file access trace). system/fish: Updated for version 3.0b1. system/forkstat: Updated for version 0.02.09. system/kapacitor: Updated for version 1.5.2. system/kitchen-sync: Updated for version 1.9. system/omnidb-app: Updated for version 2.13.0. system/runc: Updated for version 1.0.0_rc6. system/telegraf: Updated for version 1.9.1. system/tini: Updated for version 0.18.0. system/trash: Updated for version 1.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 didier at slint.fr Sat Dec 22 13:02:18 2018 From: didier at slint.fr (Didier Spaier) Date: Sat, 22 Dec 2018 14:02:18 +0100 Subject: [Slackbuilds-users] Which jack? Message-ID: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> Hello, Some SlackBuilds mention as a mandatory or optional requirement jack-audio-connection-kit (aka jack1), others jack2. As both are mutually incompatible, what can I do if I want to build a package which mentions jack-audio-connection-kit as dependency, and also another one which mentions jack2 instead? Best, Didier From didier at slint.fr Sat Dec 22 13:15:01 2018 From: didier at slint.fr (Didier Spaier) Date: Sat, 22 Dec 2018 14:15:01 +0100 Subject: [Slackbuilds-users] Which jack? In-Reply-To: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> Message-ID: <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> Hello again, On 22/12/2018 14:02, Didier Spaier wrote: > Hello, > > Some SlackBuilds mention as a mandatory or optional requirement > jack-audio-connection-kit (aka jack1), others jack2. > > As both are mutually incompatible, what can I do if I want to build a > package which mentions jack-audio-connection-kit as dependency, and > also another one which mentions jack2 instead? Addendum: I see in the FAQ: https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 Programs compiled against Jack 1 will work with Jack 2 without recompile (and vice versa). Do you folks confirm? If yes, let me rephrase my question: if jack1 or jacjk2 is mentioned as build dependenecy, can actually use the other? I ask, because as a package provider I'd rather ship jack2. Then I could install jack1 locally to just build the packages that need specifically this one, but I'd prefer to avoid that if I can. Best, Didier From yalhcru at gmail.com Sat Dec 22 19:54:59 2018 From: yalhcru at gmail.com (B Watson) Date: Sat, 22 Dec 2018 14:54:59 -0500 Subject: [Slackbuilds-users] Which jack? In-Reply-To: <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> Message-ID: On 12/22/18, Didier Spaier wrote: > I see in the FAQ: > https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 > Programs compiled against Jack 1 will work with Jack 2 without recompile > (and vice versa). > > Do you folks confirm? That's been my experience. I haven't used jack2 much, but when I tried it, the jack1-compiled stuff I tested all worked fine without a recompile. > If yes, let me rephrase my question: if jack1 or jacjk2 is mentioned as > build dependenecy, can actually use the other? > > I ask, because as a package provider I'd rather ship jack2. > Then I could install jack1 locally to just build the packages that need > specifically this one, but I'd prefer to avoid that if I can. There are only 2 builds that list jack2 as a requirement: MuseScore and lives. I just built & ran lives with jack1 and it at least compiles and runs (it's a video editor; I didn't actually try to edit any video with it). Actually, lives offers several choices for audio playback, including both jack and pulseaudio. Seems like jack should be optional, not a required dependency, but the maintainer might have a good reason for doing it the way it's done... MuseScore requires qt5-webkit, which I didn't already have installed, so it's going to take a while to build. I'll try it with jack1 also, and get back to you. From kingbeowulf at gmail.com Sat Dec 22 21:48:12 2018 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 22 Dec 2018 13:48:12 -0800 Subject: [Slackbuilds-users] Suggestion: Change download order on script pages Message-ID: <7c3e58f8-4a9d-bc5f-9e70-abd57ff4558a@gmail.com> Hello, Recently I've helped new Slackware users with SBo. I noticed that they have a hard time figuring out what to download in order to run the buildscript. Yes, there is a HOW-TO...don't go there... I suggest the following order on the script pages: --------------------- Download SlackBuild: Source Downloads: Homepage: --------------------- And perhaps move "See our HOWTO for instructions..." to somewhere to the top of page; maybe below the title "SlackBuilds Repository" Most monitors are now 19:6 and the 1/4 of the screen can end up hidden. This way, they immediately see the HOWTO link, and can, hopefully, see the order of operations from top to bottom. Thanks Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 163 bytes Desc: OpenPGP digital signature URL: From didier at slint.fr Sat Dec 22 22:51:31 2018 From: didier at slint.fr (Didier Spaier) Date: Sat, 22 Dec 2018 23:51:31 +0100 Subject: [Slackbuilds-users] Which jack? In-Reply-To: References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> Message-ID: <30ba299c-f93d-2dc4-6253-4bc641e7019f@slint.fr> Hello, On 22/12/2018 20:54, B Watson wrote: > On 12/22/18, Didier Spaier wrote: > >> I see in the FAQ: >> https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 >> Programs compiled against Jack 1 will work with Jack 2 without recompile >> (and vice versa). >> >> Do you folks confirm? > > That's been my experience. I haven't used jack2 much, but when I tried it, > the jack1-compiled stuff I tested all worked fine without a recompile. OK, thanks. >> If yes, let me rephrase my question: if jack1 or jacjk2 is mentioned as >> build dependency, can actually use the other? >> >> I ask, because as a package provider I'd rather ship jack2. >> Then I could install jack1 locally to just build the packages that need >> specifically this one, but I'd prefer to avoid that if I can. > > There are only 2 builds that list jack2 as a requirement: MuseScore > and lives. I just built & ran lives with jack1 and it at least compiles > and runs (it's a video editor; I didn't actually try to edit any video > with it). Actually, lives offers several choices for audio playback, > including both jack and pulseaudio. Seems like jack should be optional, > not a required dependency, but the maintainer might have a good reason > for doing it the way it's done... Thanks for the information. I want to package lives for Slint, but I also need jack as a dependency of ecasound,that I need as dependency of dae (Digital Audio Editor) that I have already packaged. For your information dae is accessible to the blind, unfortunately it has no public repository yet. I'd rather package jack2, because according to the docs it's hard to make jack1 coexist with pulseaudio unless the user has two sound cards, and easier with jack2 using jackdbus (basically telling pulse to use jack as default sink when jack2 starts if I understand correctly, then telling it to use dmix (the default in Slint) when it stops. I assume I need two functions: jack_start() { pactl load-module module-jack-sink pactl load-module module-jack-source pacmd "set-default-sink jack_out" pacmd "set-default-source jack_in" } jack_stop() { pactl unload-module module-jack-sink pactl unload-module module-jack-source pacmd "set-default-sink dmix" pacmd "set-default-source jdsnoop" } Would this work? Best, Didier From yalhcru at gmail.com Sat Dec 22 23:52:36 2018 From: yalhcru at gmail.com (B Watson) Date: Sat, 22 Dec 2018 18:52:36 -0500 Subject: [Slackbuilds-users] Which jack? In-Reply-To: <30ba299c-f93d-2dc4-6253-4bc641e7019f@slint.fr> References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> <30ba299c-f93d-2dc4-6253-4bc641e7019f@slint.fr> Message-ID: On 12/22/18, Didier Spaier wrote: > For your information dae is accessible to the blind, unfortunately > it has no public repository yet. Hm. An audio editor you can use without having to look at it, would be useful for me too (I can see OK, but sometimes my eyes need to be looking at lyrics or sheet music instead of a GUI). > I assume I need two functions: > ... > Would this work? Maybe someone on the list knows, I'm the wrong guy to ask about pulseaudio unless your question is "how do I disable pulseaudio permanently?" :) From klaatu at member.fsf.org Sat Dec 22 14:49:18 2018 From: klaatu at member.fsf.org (Klaatu) Date: Sun, 23 Dec 2018 03:49:18 +1300 Subject: [Slackbuilds-users] Which jack? In-Reply-To: <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> Message-ID: <5996293.iS15iBafFV@beast> On Saturday, December 22, 2018 02:15:01 PM Didier Spaier wrote: > Hello again, > > On 22/12/2018 14:02, Didier Spaier wrote: > > Hello, > > > > Some SlackBuilds mention as a mandatory or optional requirement > > jack-audio-connection-kit (aka jack1), others jack2. > > > > As both are mutually incompatible, what can I do if I want to build a > > package which mentions jack-audio-connection-kit as dependency, and > > also another one which mentions jack2 instead? > > Addendum: > > I see in the FAQ: > https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_ja > ck2 Programs compiled against Jack 1 will work with Jack 2 without recompile > (and vice versa). > > Do you folks confirm? > > If yes, let me rephrase my question: if jack1 or jacjk2 is mentioned as > build dependenecy, can actually use the other? > > I ask, because as a package provider I'd rather ship jack2. > Then I could install jack1 locally to just build the packages that need > specifically this one, but I'd prefer to avoid that if I can. > > 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/ I use ONLY Jack2 and while I do compile most of my software, I just downloaded jack-rack from slackonly.com and it works as expected. I don't believe it matters. I brought this issue up to the mailing list before (https://lists.slackbuilds.org/pipermail/slackbuilds-users/2015-May/014252.html). I think it would be clearer for README files and REQUIRE lines to list a generic JACK dependency, rather than specifying jack-audio-connection-kit (and jack2 is never, in practice, mentioned). In packages that I maintain, I list both in the README file (https://slackbuilds.org/repository/14.2/audio/luppp/). For the record, I still think it would be useful for SBo at large to define a generic JACK dependency which means either JACK or JACK2. From yalhcru at gmail.com Sun Dec 23 07:20:43 2018 From: yalhcru at gmail.com (B Watson) Date: Sun, 23 Dec 2018 02:20:43 -0500 Subject: [Slackbuilds-users] Which jack? In-Reply-To: <5996293.iS15iBafFV@beast> References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> <5996293.iS15iBafFV@beast> Message-ID: On 12/22/18, Klaatu wrote: > > For the record, I still think it would be useful for SBo at large to define > a > generic JACK dependency which means either JACK or JACK2. You mean something like what Debian calls a metapackage? The existing SBo infrastructure hasn't got the concept of it. For it to exist, a bunch of work would have to be done (decisions to be made, tools and procedures updated). For jack 1 vs. 2, it's pretty simple, but I can imagine e.g. package xyz needs either foo or bar, but if it uses bar, bar must be compiled with MAGIC=yes set. Or, foo must be compiled with the optional dependency quux. We'd need a syntax to be able to express that in the .info file, and a parser for that syntax (to be used in sbopkg/sbotools/etc). Historically this level of complexity is something the SBo admins have resisted (I don't speak for them, but I've read previous discussions on this list...) Also, if I maintain some build that I say depends on jack-audio-connection-kit, and it gets replaced with a meta-dependency on jack in general... I now have to spend twice as much time testing my build (to make sure it really does work with both jacks). If I instead have the option to keep the dependency on jack-audio-connection-kit, I will, just to save myself the work. Which would make the meta-dependency pointless (at least it will if not using it is the path of least resistance). We have other things like this... various something and something-legacy, and wxGTK vs. wxPython. Also wx(GTK|Python) version 2.x vs. wxGTK3, since some things can be built with either. I take the REQUIRES= to mean "this is what the maintainer tests with". If something else happens to work, great (and it should ideally be mentioned in the README, like you do in your builds). From didier at slint.fr Sun Dec 23 09:47:47 2018 From: didier at slint.fr (Didier Spaier) Date: Sun, 23 Dec 2018 10:47:47 +0100 Subject: [Slackbuilds-users] Which jack? In-Reply-To: References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> <30ba299c-f93d-2dc4-6253-4bc641e7019f@slint.fr> Message-ID: Hello, On 23/12/2018 00:52, B Watson wrote: > On 12/22/18, Didier Spaier wrote: > >> For your information dae is accessible to the blind, unfortunately >> it has no public repository yet. > > Hm. An audio editor you can use without having to look at it, would > be useful for me too (I can see OK, but sometimes my eyes need to be > looking at lyrics or sheet music instead of a GUI). Well, this is one of the packages queued for the next Slint update (added or upgraded) cf.: http://slackware.uk/slint/x86_64/slint-14.2.1/next/packages/ http://slackware.uk/slint/x86_64/slint-14.2.1/next/source/ I still have to carefully check the dependencies, after that I will post here the list of those not in SBo and that can interest Slackware users with a short description and the list of dependencies. Best, Didier From rworkman at slackbuilds.org Sun Dec 23 18:38:52 2018 From: rworkman at slackbuilds.org (Robby Workman) Date: Sun, 23 Dec 2018 12:38:52 -0600 Subject: [Slackbuilds-users] Which jack? In-Reply-To: References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <4944ce0f-da25-3cc9-e9bb-d36b942890ff@slint.fr> <5996293.iS15iBafFV@beast> Message-ID: <20181223123852.643153ef@home.rlworkman.net> On Sun, 23 Dec 2018 02:20:43 -0500 B Watson wrote: > On 12/22/18, Klaatu wrote: > > > > For the record, I still think it would be useful for SBo at large > > to define a > > generic JACK dependency which means either JACK or JACK2. > > You mean something like what Debian calls a metapackage? The existing > SBo infrastructure hasn't got the concept of it. For it to exist, a > bunch of work would have to be done (decisions to be made, tools and > procedures updated). > > For jack 1 vs. 2, it's pretty simple, but I can imagine e.g. package > xyz needs either foo or bar, but if it uses bar, bar must be compiled > with MAGIC=yes set. Or, foo must be compiled with the optional > dependency quux. We'd need a syntax to be able to express that in > the .info file, and a parser for that syntax (to be used in > sbopkg/sbotools/etc). Historically this level of complexity is > something the SBo admins have resisted (I don't speak for them, but > I've read previous discussions on this list...) > > Also, if I maintain some build that I say depends on > jack-audio-connection-kit, and it gets replaced with a > meta-dependency on jack in general... I now have to spend twice as > much time testing my build (to make sure it really does work with > both jacks). If I instead have the option to keep the dependency on > jack-audio-connection-kit, I will, just to save myself the work. > Which would make the meta-dependency pointless (at least it will if > not using it is the path of least resistance). > > We have other things like this... various something and > something-legacy, and wxGTK vs. wxPython. Also wx(GTK|Python) version > 2.x vs. wxGTK3, since some things can be built with either. > > I take the REQUIRES= to mean "this is what the maintainer tests > with". If something else happens to work, great (and it should > ideally be mentioned in the README, like you do in your builds). Yes, what he said. ^^ -RW -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From klaatu at member.fsf.org Sun Dec 23 13:02:07 2018 From: klaatu at member.fsf.org (Klaatu) Date: Mon, 24 Dec 2018 02:02:07 +1300 Subject: [Slackbuilds-users] Which jack? In-Reply-To: References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <5996293.iS15iBafFV@beast> Message-ID: <4831691.E3QuHkuhVX@beast> On Sunday, December 23, 2018 02:20:43 AM B Watson wrote: > On 12/22/18, Klaatu wrote: > > For the record, I still think it would be useful for SBo at large to > > define > > a > > generic JACK dependency which means either JACK or JACK2. > > You mean something like what Debian calls a metapackage? The existing > SBo infrastructure hasn't got the concept of it. For it to exist, a > bunch of work would have to be done (decisions to be made, tools and > procedures updated). > > For jack 1 vs. 2, it's pretty simple, but I can imagine e.g. package > xyz needs either foo or bar, but if it uses bar, bar must be compiled > with MAGIC=yes set. Or, foo must be compiled with the optional dependency > quux. We'd need a syntax to be able to express that in the .info file, and > a parser for that syntax (to be used in sbopkg/sbotools/etc). Historically > this level of complexity is something the SBo admins have resisted (I > don't speak for them, but I've read previous discussions on this list...) > > Also, if I maintain some build that I say depends on > jack-audio-connection-kit, and it gets replaced with a meta-dependency on > jack in general... I now have to spend twice as much time testing my build > (to make sure it really does work with both jacks). If I instead have the > option to keep the dependency on jack-audio-connection-kit, I will, just > to save myself the work. Which would make the meta-dependency pointless > (at least it will if not using it is the path of least resistance). > > We have other things like this... various something and something-legacy, > and wxGTK vs. wxPython. Also wx(GTK|Python) version 2.x vs. wxGTK3, > since some things can be built with either. > > I take the REQUIRES= to mean "this is what the maintainer tests with". If > something else happens to work, great (and it should ideally be mentioned > in the README, like you do in your builds). > _______________________________________________ > 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/ Not exactly. I meant some string to indicate that either JACK 1 or 2 may be used. For instance, list "JACK" as a dep, and rename 'jack-audio-connection-kit' to 'jack1', allowing 'JACK' to convey that either 'jack1' or 'jack2' are acceptable). I know this would probably 'break' auto-install scripts, but I imagine those scripts could add something on their end such that a variable 'JACK' resolves to whatever the user defines in a config file. The differences between Jack 1 and 2 are summarized here: https://github.com/jackaudio/jackaudio.github.com/wiki/Q_difference_jack1_jack2 and I think it's debatable whether jack1 really should be the default jack- audio-connection-kit package. From yalhcru at gmail.com Mon Dec 24 02:36:02 2018 From: yalhcru at gmail.com (B Watson) Date: Sun, 23 Dec 2018 21:36:02 -0500 Subject: [Slackbuilds-users] Which jack? In-Reply-To: <4831691.E3QuHkuhVX@beast> References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <5996293.iS15iBafFV@beast> <4831691.E3QuHkuhVX@beast> Message-ID: On 12/23/18, Klaatu wrote: > > Not exactly. I meant some string to indicate that either JACK 1 or 2 may be > used. > > For instance, list "JACK" as a dep, and rename 'jack-audio-connection-kit' > to 'jack1', allowing 'JACK' to convey that either 'jack1' or 'jack2' are > acceptable). AFAIK, that's exactly what a Debian metapackage is. Assuming they still exist, anyway (may have been replaced by the /etc/alternatives system?) RPM has something similar ('provides' and 'requires', IIRC). > I know this would probably 'break' auto-install scripts, but I > imagine those scripts could add something on their end such that a variable > 'JACK' resolves to whatever the user defines in a config file. Make it $JACK. The config file could just be a bunch of shell variable assignments, with helpful comments: # Choose jack1 or jack2: JACK=jack1 # Choose wxPython or wxGTK: WX2=wxPython etc etc. Whatever tool you're using would just source that file (if the tool's written in bash) or otherwise parse it. Instead of $JACK in the .info file, it could even be: ${JACK:-jack1} Which means "whatever the config script defined JACK as, or jack1 if it's not defined". That even leaves the old "this is what the maintainer tests with" documented (the above would mean "I test with jack1, but you're welcome to try jack2 if you like"). Not that I expect this to actually get accepted by the admins any time soon (they have a ton of work to do already, and they're unpaid volunteers, just like us maintainers).. > and I think it's debatable whether jack1 really should be the default jack- > audio-connection-kit package. It is, but it's not a debate I want to enter into. Not even sure which side of the debate I'd be on... From didier at slint.fr Mon Dec 24 09:41:47 2018 From: didier at slint.fr (Didier Spaier) Date: Mon, 24 Dec 2018 10:41:47 +0100 Subject: [Slackbuilds-users] Which jack? In-Reply-To: References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <5996293.iS15iBafFV@beast> <4831691.E3QuHkuhVX@beast> Message-ID: <94279d64-8e35-3dbe-1a41-e9bfc942ddb1@slint.fr> Why not write in .info: REQUIRES=" jack1|jack2 " A similar syntax is used since ages by slapt-get & friends, just using comma instead of space as token delimiter. I doesn't matter that the vertical line be surrounded by spaces or not, as sbopkg & friends could remove them with: sed '/REQUIRES/s@[[:space:]]*|[[:space:]]*@|@g' .info or something like that. Didier From klaatu at member.fsf.org Mon Dec 24 18:55:36 2018 From: klaatu at member.fsf.org (Klaatu) Date: Tue, 25 Dec 2018 07:55:36 +1300 Subject: [Slackbuilds-users] Which jack? In-Reply-To: <94279d64-8e35-3dbe-1a41-e9bfc942ddb1@slint.fr> References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <5996293.iS15iBafFV@beast> <4831691.E3QuHkuhVX@beast> <94279d64-8e35-3dbe-1a41-e9bfc942ddb1@slint.fr> Message-ID: I quite like this idea. On 24 December 2018 10:41:47 PM NZDT, Didier Spaier wrote: >Why not write in .info: > >REQUIRES=" jack1|jack2 " > >A similar syntax is used since ages by slapt-get & friends, just using >comma instead of space as token delimiter. > >I doesn't matter that the vertical line be surrounded by spaces or not, >as sbopkg & friends could remove them with: >sed '/REQUIRES/s@[[:space:]]*|[[:space:]]*@|@g' .info >or something like that. > >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/ -- Klaatu -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Mon Dec 24 20:18:29 2018 From: didier at slint.fr (Didier Spaier) Date: Mon, 24 Dec 2018 21:18:29 +0100 Subject: [Slackbuilds-users] Which jack? In-Reply-To: References: <697d74a4-203f-1693-aa19-2be33b8c79e6@slint.fr> <5996293.iS15iBafFV@beast> <4831691.E3QuHkuhVX@beast> <94279d64-8e35-3dbe-1a41-e9bfc942ddb1@slint.fr> Message-ID: PS: this would help also for case like portaudio or speech-dispatcher for instance, as they need the support of at least an audio backend, but can safely be built with several ones. So for espeak.info the REQUIRES line could include: alsa|jack1|jack2|oss And for speech-dispatcher.info: pulse|libao|alsa|oss|nas Maybe in these cases this is an overkill, as oss, alsa and pulse are included in a full Slackware installation (at least either alsa or pulse in Slackware-current) and thus maybe should not be mentioned in the REQUIRES line, but you get the idea. These examples also illustrate that the vertical line should mean "or", not "xor". Didier On 24/12/2018 19:55, Klaatu wrote: > I quite like this idea. > > On 24 December 2018 10:41:47 PM NZDT, Didier Spaier wrote: >> Why not write in .info: >> >> REQUIRES=" jack1|jack2 " >> >> A similar syntax is used since ages by slapt-get & friends, just using >> comma instead of space as token delimiter. >> >> I doesn't matter that the vertical line be surrounded by spaces or not, >> as sbopkg & friends could remove them with: >> sed '/REQUIRES/s@[[:space:]]*|[[:space:]]*@|@g' .info >> or something like that. >> >> 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/ > > > _______________________________________________ > 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 Tue Dec 25 00:21:32 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 25 Dec 2018 07:21:32 +0700 Subject: [Slackbuilds-users] Updates - 20181225.1 Message-ID: Merry Christmas everyone!! Tue Dec 25 00:00:59 UTC 2018 academic/FCSalyzer: Updated for version 0.9.16_alpha. academic/ImageJ: Removed (Use fiji). academic/RepeatMasker: Updated for version 4.0.8. academic/WEVOTE: Added (WEighted VOting Taxonomic idEntification). academic/aliview: Updated for version 1.25. academic/archaeopteryx: Updated for version 0.9928b. academic/bowtie2-legacy: Added (aligning sequencing reads). academic/bpp-core: Updated for version 2.4.1. academic/bpp-phyl-omics: Updated for version 2.4.1. academic/bpp-phyl: Updated for version 2.4.1. academic/bpp-popgen: Updated for version 2.4.1. academic/bpp-seq-omics: Updated for version 2.4.1. academic/bpp-seq: Updated for version 2.4.1. academic/bppsuite: Updated for version 2.4.1. academic/clark-ugene: Added (supervised sequence classification). academic/diamond: Added (A sequence aligner). academic/fiji: Added (ImageJ Distribution). academic/hyphy: Updated for version 2.3.14. academic/ij-plugins-LOCI: Removed (Use fiji). academic/ij-plugins-UCSD: Removed (Use fiji). academic/jellyfish_k-mer: Added (k-mers counting tools). academic/kraken: Added (Assigning Taxonomic Labels). academic/mafft: Updated for version 7.407. academic/megax: Updated for version 10.0.5_1. academic/ncbi-blast+: Added (BLAST+ Command Line Applications). academic/ncbi-blast-plus: Removed (Use ncbi-blast+). academic/ncbi-blast: Update script. academic/ncbi-rmblastn: Update DEP. academic/samtools-legacy: Added (Sequence Alignment/Map Tools). academic/spades: Updated for version 3.13.0. academic/stringtie: Added (Assembler of RNA-Seq alignments). academic/tabix-legacy: Added (Generic indexer). academic/trimmomatic: Added (Trimming Tool). academic/ugene: Updated for version 1.31.1. academic/vcftools: Updated for version 0.1.16. academic/wehi-weasel: Updated for version 3.5.0.17. development/blassic: Fix .info file. development/hugo: Updated for version 0.53. libraries/leptonica: Updated for version 1.77.0. multimedia/plexmediaserver: Updated for version 1.14.1.5488_cc260c476. network/WhatWeb: Added (Next generation web scanner). network/dmitry: Added (Deepmagic Information Gathering Tool). network/neomutt: Added (Text-based Mail Client). network/onyx: Added (Gopher protocol engine). network/quagga: Updated for version 1.2.4 + new maintainer. network/sabnzbd: Updated for version 2.3.6. network/scapy: Added (interactive packet manipulation tool). network/ssvnc: Update README. network/telegram: Updated for version 1.5.4. office/MasterPDFEditor: Updated for version 5.2.20. python/mypy: Change email address. python/mypy_extensions: Change email address. python/python3-docutils: Change email address. python/python3-pyserial: Change email address. python/typed_ast: Updated for version 1.1.1. python/websocket-client: Added missing dependency. system/nvidia-driver: Updated for version 410.78. system/nvidia-kernel: Updated for version 410.78. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From yalhcru at gmail.com Tue Dec 25 12:31:44 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 25 Dec 2018 07:31:44 -0500 Subject: [Slackbuilds-users] (no subject) Message-ID: >From the latest sbosrcarch run (happened after the public update): academic/cryptominisat: bad md5sum development/adoptopenjdk: bad md5sum (it's actually the sha256sum) development/p4: bad md5sum (for both 32 and 64 bit) development/p4d: bad md5sum (for both 32 and 64 bit) games/open-adventure: bad md5sum (already fixed in user/urchlay/updates branch) network/palemoon-bin: bad md5sum (32 bit only; 64 bit is OK) system/isdct: bad md5sum Please don't shoot the messenger... From didier at slint.fr Tue Dec 25 12:57:20 2018 From: didier at slint.fr (Didier Spaier) Date: Tue, 25 Dec 2018 13:57:20 +0100 Subject: [Slackbuilds-users] (no subject) In-Reply-To: References: Message-ID: On 25/12/2018 13:31, B Watson wrote: > Please don't shoot the messenger... Long ago William wrote in King Henry IV, Second Part Act I, scene 1: > NORTHUMBERLAND. > Yet, for all this, say not that Percy's dead. > I see a strange confession in thine eye; > Thou shakest thy head and hold'st it fear or sin > To speak a truth. If he be slain, say so; > The tongue offends not that reports his death: > And he doth sin that doth belie the dead, > Not he which says the dead is not alive > Yet the first bringer of unwelcome news > Hath but a losing office, and his tongue > Sounds ever after as a sullen bell, > Remember'd tolling a departing friend. cf. http://www.gutenberg.org/ebooks/1518 From yalhcru at gmail.com Tue Dec 25 18:57:19 2018 From: yalhcru at gmail.com (B Watson) Date: Tue, 25 Dec 2018 13:57:19 -0500 Subject: [Slackbuilds-users] (no subject) In-Reply-To: References: Message-ID: On 12/25/18, Didier Spaier wrote: >> To speak a truth. If he be slain, say so; >> The tongue offends not that reports his death: Henry IV must have been a nicer guy than Henry VIII. Come to think of it, most people are nicer than Henry VIII... From willysr at slackbuilds.org Tue Dec 25 19:50:51 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 26 Dec 2018 02:50:51 +0700 Subject: [Slackbuilds-users] (no subject) In-Reply-To: References: Message-ID: <1549e109-b1b4-390e-9a44-b0249ef8b728@slackbuilds.org> > academic/cryptominisat: bad md5sum > development/adoptopenjdk: bad md5sum (it's actually the sha256sum) > development/p4: bad md5sum (for both 32 and 64 bit) > development/p4d: bad md5sum (for both 32 and 64 bit) > network/palemoon-bin: bad md5sum (32 bit only; 64 bit is OK) > system/isdct: bad md5sum All fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From fellype at gmail.com Wed Dec 26 18:50:59 2018 From: fellype at gmail.com (Fellype) Date: Wed, 26 Dec 2018 16:50:59 -0200 Subject: [Slackbuilds-users] Updates - 20181222.1 In-Reply-To: <280aebcb-d130-4067-fb9c-9d94fb863ef7@slackbuilds.org> References: <280aebcb-d130-4067-fb9c-9d94fb863ef7@slackbuilds.org> Message-ID: Hi all, Em s?b, 22 de dez de 2018 ?s 00:00, Willy Sudiarto Raharjo < willysr at slackbuilds.org> escreveu: > > Google Go 1.11.4 is a security update, so please make sure to upgrade > them. There are things that depend on google-go-lang that are not building here: runc, containerd, docker-proxy and docker All them return the error: go: cannot find GOROOT directory: /usr/lib64/go1.11.3/go google-go-lang was upgraded to 1.11.4 by using 'sbocheck' and 'sboupgrade --all' Anyone have any idea about what's going on? Thanks in advance, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Dec 26 19:01:33 2018 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 26 Dec 2018 20:01:33 +0100 Subject: [Slackbuilds-users] Updates - 20181222.1 In-Reply-To: References: <280aebcb-d130-4067-fb9c-9d94fb863ef7@slackbuilds.org> Message-ID: Il giorno mer 26 dic 2018 alle ore 19:51 Fellype ha scritto: > > Hi all, > > Em s?b, 22 de dez de 2018 ?s 00:00, Willy Sudiarto Raharjo escreveu: >> >> >> Google Go 1.11.4 is a security update, so please make sure to upgrade >> them. > > There are things that depend on google-go-lang that are not building here: > runc, containerd, docker-proxy and docker > All them return the error: > go: cannot find GOROOT directory: /usr/lib64/go1.11.3/go > > google-go-lang was upgraded to 1.11.4 by using 'sbocheck' and 'sboupgrade --all' > > Anyone have any idea about what's going on? > > Thanks in advance, after the upgrade of google-go-lang you have to logout and login again so that /etc/profile.d/go.sh gets loaded. From ricardo at palmtx.com.ar Wed Dec 26 19:43:42 2018 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Wed, 26 Dec 2018 16:43:42 -0300 Subject: [Slackbuilds-users] Updates - 20181222.1 In-Reply-To: References: <280aebcb-d130-4067-fb9c-9d94fb863ef7@slackbuilds.org> Message-ID: <201812261643.42519.ricardo@palmtx.com.ar> El Mi?rcoles 26/12/2018 a las 16:01, Matteo Bernardini escribi?: > Il giorno mer 26 dic 2018 alle ore 19:51 Fellype ha scritto: > > Hi all, > > > > Em s?b, 22 de dez de 2018 ?s 00:00, Willy Sudiarto Raharjo escreveu: > >> Google Go 1.11.4 is a security update, so please make sure to upgrade > >> them. > > > > There are things that depend on google-go-lang that are not building > > here: runc, containerd, docker-proxy and docker > > All them return the error: > > go: cannot find GOROOT directory: /usr/lib64/go1.11.3/go > > > > google-go-lang was upgraded to 1.11.4 by using 'sbocheck' and 'sboupgrade > > --all' > > > > Anyone have any idea about what's going on? > > > > Thanks in advance, > > after the upgrade of google-go-lang you have to logout and login again > so that /etc/profile.d/go.sh gets loaded. Or at least source the file: . /etc/profile.d/go.sh (That's what I did) Cheers! -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From willysr at slackbuilds.org Thu Dec 27 01:12:53 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 27 Dec 2018 08:12:53 +0700 Subject: [Slackbuilds-users] Updates - 20181222.1 In-Reply-To: References: <280aebcb-d130-4067-fb9c-9d94fb863ef7@slackbuilds.org> Message-ID: > There are things that depend on google-go-lang that are not building here: > runc, containerd, docker-proxy and docker > All them return the error: > go: cannot find GOROOT directory: /usr/lib64/go1.11.3/go > > google-go-lang was upgraded to 1.11.4 by using 'sbocheck' and > 'sboupgrade --all' > > Anyone have any idea about what's going on? After upgrading to google-go-lang, you need to source the new profile or simply use "su -" to do it and then you can build all docker-related packages. -- 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 Fri Dec 28 23:40:06 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Dec 2018 06:40:06 +0700 Subject: [Slackbuilds-users] Feedback needed: nodejs changes Message-ID: Hi all, Nodejs6 has entered maintenance release since April 2018 and it will be EOL'ed in April 2019. Since nothing is depending on this package, i plan to remove this package in 2019 if no one objected. I will push the latest stable update in today's public update. Current nodejs will be upgraded to nodejs v10 as the latest LTS release and it will be considered an active release until April 2020 and EOL'ed in April 2021 A new nodejs8 will be submitted if needed just in case there are some packages that still incompatible with the latest nodejs v10. I will push it after today's public update and give some time for users to migrate and test their applications. Any suggestions? -- 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 Dec 29 00:27:11 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Dec 2018 07:27:11 +0700 Subject: [Slackbuilds-users] Updates - 20181229.1 Message-ID: <276f7156-d623-bd10-9da2-a52cddad157c@slackbuilds.org> Hi This will be the last update in 2018. It's been another great year this time. We have many new contributors and many new packages gets added and we are looking forward to see more packages gets included in the SBo repository next year. We are also happy that more people are pushing updates through PR/MR in Github/GitLab so workflow is getting better as well. We are expecting people to send more in the future :-) A small stats on the SBo repository can be seen here: https://willysr.github.io/slackbuilds-stats/index.html Wishing you all a great happy new year 2019 Have a great weekend Sat Dec 29 00:04:44 UTC 2018 academic/cryptominisat: Fix MD5SUM. development/Sphinx: Updated for version 1.8.3. development/adoptopenjdk: Fix MD5SUM. development/hub: Updated for version 2.7.0. development/nodejs6: Updated for version 6.16.0. development/nodejs: Updated for version 8.15.0. development/p4: Updated for version 2018.2.1740258. development/p4d: Updated for version 2018.2.1740258. development/pycharm: Updated for version 2018.3.2. development/zeal: Updated for version 0.6.1. games/freeorion: Updated for version 0.4.8. games/open-adventure: Fix md5sum. games/tbftss: Added (The Battle For The Solar System). gis/openorienteering-mapper: Updated for version 0.8.4. gis/qmapshack: Updated for version 1.12.1. graphics/feh: Updated for version 3.1.1. graphics/graphite2: Updated for version 1.3.13. multimedia/tragtor: Added (GUI for ffmpeg/avconv). network/chrony: Updated for version 3.4. network/palemoon-bin: Fix MD5SUM. network/republicanywhere: Added (texting app for the desktop). network/suricata: Updated for version 4.1.2. network/vivaldi: Updated for version 2.2.1388.37. network/yle-dl: Updated for version 20181221. office/onlyoffice-desktopeditors: Fix MD5SUM. office/re-typeset: Added (resize scanned text images). perl/MoarVM: Updated for version 2018.12. perl/nqp: Updated for version 2018.12. perl/rakudo: Updated for version 2018.12. perl/zef: Updated for version 0.6.0. python/stem: Updated for version 1.7.1. ruby/ruby-build: Updated for version 20181225. ruby/rubygem-lolcat: Updated for version 99.9.20. ruby/rubygem-manpages: Added (man pages support to ruby gems). ruby/rubygem-optimist: Added (Commandline option parser for Ruby). system/clamtk: Updated for version 5.26. system/isdct: Fix MD5SUM. system/kbfs: Updated for version 2.13.0_20181219142726. system/reprepro: Added (Debian package repository producer). system/xen: Updated for version 4.11.1. system/yash: Updated for version 2.48. +--------------------------+ -- 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 andrew.david.strong at gmail.com Sat Dec 29 01:19:59 2018 From: andrew.david.strong at gmail.com (andrew) Date: Sat, 29 Dec 2018 12:19:59 +1100 Subject: [Slackbuilds-users] Updates - 20181229.1 In-Reply-To: <276f7156-d623-bd10-9da2-a52cddad157c@slackbuilds.org> References: <276f7156-d623-bd10-9da2-a52cddad157c@slackbuilds.org> Message-ID: <20181229011959.GB14591@ilium.andrews-corner.org> On Sat, Dec 29, 2018 at 07:27:11AM +0700, Willy Sudiarto Raharjo wrote: > This will be the last update in 2018. Thanks for all of your work in 2018 and all the other people who make SBo great! Happy New Year! Andrew -- You think that's air you're breathing now? From rshepard at appl-ecosys.com Sat Dec 29 01:20:23 2018 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Fri, 28 Dec 2018 17:20:23 -0800 (PST) Subject: [Slackbuilds-users] Updates - 20181229.1 In-Reply-To: <20181229011959.GB14591@ilium.andrews-corner.org> References: <276f7156-d623-bd10-9da2-a52cddad157c@slackbuilds.org> <20181229011959.GB14591@ilium.andrews-corner.org> Message-ID: On Sat, 29 Dec 2018, andrew wrote: > Thanks for all of your work in 2018 and all the other people who make SBo > great! And the same from me. Regards, Rich From willysr at slackbuilds.org Sat Dec 29 02:47:30 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 29 Dec 2018 09:47:30 +0700 Subject: [Slackbuilds-users] Feedback needed: nodejs changes In-Reply-To: References: Message-ID: > Current nodejs will be upgraded to nodejs v10 as the latest LTS release > and it will be considered an active release until April 2020 and EOL'ed > in April 2021 It turns out node 10 removed Open SSL 1.0.2 support (https://github.com/nodejs/node/issues/22025), so node 10 will only be available for next Slackware release and not in current cycle. So in the meantime, we will stick with nodejs 8 as our latest release in SBo repository. -- 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 z.coldplayer at gmail.com Sat Dec 29 07:03:34 2018 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sat, 29 Dec 2018 11:03:34 +0400 Subject: [Slackbuilds-users] Updates - 20181229.1 In-Reply-To: References: <276f7156-d623-bd10-9da2-a52cddad157c@slackbuilds.org> <20181229011959.GB14591@ilium.andrews-corner.org> Message-ID: Happy new year to you all Cheers Pritvi On Sat, 29 Dec 2018, 05:20 Rich Shepard On Sat, 29 Dec 2018, andrew wrote: > > > Thanks for all of your work in 2018 and all the other people who make SBo > > great! > > And the same from me. > > Regards, > > Rich > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From z.coldplayer at gmail.com Sat Dec 29 07:07:27 2018 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sat, 29 Dec 2018 11:07:27 +0400 Subject: [Slackbuilds-users] Feedback needed: nodejs changes In-Reply-To: References: Message-ID: On Sat, 29 Dec 2018, 06:47 Willy Sudiarto Raharjo > Current nodejs will be upgraded to nodejs v10 as the latest LTS release > > and it will be considered an active release until April 2020 and EOL'ed > > in April 2021 > > It turns out node 10 removed Open SSL 1.0.2 support > (https://github.com/nodejs/node/issues/22025), so node 10 will only be > available for next Slackware release and not in current cycle. > > So in the meantime, we will stick with nodejs 8 as our latest release in > SBo repository. > > -- > 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/ Hi willy, By current cycle do you mean Slackware 14.2. If that is the case, then I would be testing node 10 under Slackware - current. I only need to check whether openssl greater than 1.0.2 is available Cheers Pritvi -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sun Dec 30 00:06:57 2018 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 30 Dec 2018 07:06:57 +0700 Subject: [Slackbuilds-users] Feedback needed: nodejs changes In-Reply-To: References: Message-ID: <3453d9a4-2e50-b01e-a1d1-326186bf759b@slackbuilds.org> > By current cycle do you mean Slackware 14.2. > If that is the case, then I would be testing node 10 under Slackware - > current.? > I only need to check whether openssl greater than 1.0.2 is available? Yes, current cycle is 14.2 nodejs 10 is only supporting openssl 1.1.1, so it's not possible to build it for 14.2 unless it's patched, but upstream is not willing to do it due to the reason they stated in the issue tracker i mentioned before. Hence, 14.2 will only see nodejs 8 unless OpenSSL 1.1.1 is introduced in 14.2, which is unlikely, since it's EOL'ed by the end of 2019 according to https://www.openssl.org/policies/releasestrat.html. Only by end of 2019 we might have a chance to see whether openssl 1.1.x will be brought back to 14.2 or not. -- 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 z.coldplayer at gmail.com Sun Dec 30 09:08:32 2018 From: z.coldplayer at gmail.com (Jheengut Pritvi) Date: Sun, 30 Dec 2018 13:08:32 +0400 Subject: [Slackbuilds-users] Feedback needed: nodejs changes In-Reply-To: References: Message-ID: Hi, I have only one project depending upon nodejs so I will help as much as is possible. Cheers Pritvi On Sat, 29 Dec 2018, 03:40 Willy Sudiarto Raharjo Hi all, > > Nodejs6 has entered maintenance release since April 2018 and it will be > EOL'ed in April 2019. Since nothing is depending on this package, i plan > to remove this package in 2019 if no one objected. I will push the > latest stable update in today's public update. > > Current nodejs will be upgraded to nodejs v10 as the latest LTS release > and it will be considered an active release until April 2020 and EOL'ed > in April 2021 > > A new nodejs8 will be submitted if needed just in case there are some > packages that still incompatible with the latest nodejs v10. I will push > it after today's public update and give some time for users to migrate > and test their applications. > > Any suggestions? > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: