From didier at slint.fr Wed Mar 4 18:15:08 2020 From: didier at slint.fr (Didier Spaier) Date: Wed, 4 Mar 2020 19:15:08 +0100 Subject: [Slackbuilds-users] viewnior SlackBuild In-Reply-To: References: Message-ID: <307ea7d7-6a4c-8f82-a093-98c741adce31@slint.fr> Hello Edinaldo and list, Le 01/03/2020 ? 23:43, Edinaldo a ?crit?: > Hi Didier, > > viewnior SlackBuild still linking to me as the maintainer: > > http://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-January/023802.html > > Please let me know if you don't have interest in keep him, in this case i will send as the "orphan" state. Thanks for the heads-up. On second thought I don't have interest to keep it. Best regards, Didier From yalhcru at gmail.com Wed Mar 4 18:42:04 2020 From: yalhcru at gmail.com (B Watson) Date: Wed, 4 Mar 2020 13:42:04 -0500 Subject: [Slackbuilds-users] viewnior SlackBuild In-Reply-To: <307ea7d7-6a4c-8f82-a093-98c741adce31@slint.fr> References: <307ea7d7-6a4c-8f82-a093-98c741adce31@slint.fr> Message-ID: On 3/4/20, Didier Spaier wrote: > > On second thought I don't have interest to keep it. Hm, I never looked at this before. It looks useful, if nobody else wants it I'll take it. From slackalaxy at gmail.com Thu Mar 5 08:16:21 2020 From: slackalaxy at gmail.com (Petar Petrov) Date: Thu, 5 Mar 2020 10:16:21 +0200 Subject: [Slackbuilds-users] viewnior SlackBuild In-Reply-To: References: <307ea7d7-6a4c-8f82-a093-98c741adce31@slint.fr> Message-ID: it is a great little program. I use it as my default image viewer. On 04/03/2020, B Watson wrote: > On 3/4/20, Didier Spaier wrote: >> >> On second thought I don't have interest to keep it. > > Hm, I never looked at this before. It looks useful, if nobody else wants > it I'll take it. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > From willysr at slackbuilds.org Sat Mar 7 07:17:29 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 7 Mar 2020 14:17:29 +0700 Subject: [Slackbuilds-users] Updates - 20200307.1 Message-ID: Welcome to first update in March Sat Mar 7 07:07:17 UTC 2020 academic/bowtie2: Updated for version 2.4.1. academic/nco: Added (netCDF Operators Software Stack). academic/pysam: Updated for version 0.15.4. academic/reduce-algebra: Updated for version 20200301svn5286. accessibility/sct: Updated for version 0.5 desktop/ceti-2-theme: Orphaned. desktop/faba-icon-theme: Update script. desktop/jgmenu: Updated for version 4.1.0. desktop/moka-icon-theme: Update script. development/Sphinx: Updated for version 2.4.3. development/cf-cli: Updated for version 6.50.0. development/chicken: Update README. development/hhvm: Updated for version 4.32.0 development/hub: Updated for version 2.14.2. development/julia: Updated for version 1.3.1. development/jupyter_core: Updated for version 4.6.3. development/kotlin: Updated for version 1.3.70. development/mawk: Updated for version 1.3.4_20200120. development/mg-troglobit: Updated for version 3.3. development/pycharm: Updated for version 2019.3.3. development/yarn: Fix MD5SUM. development/yarn: Updated for version 1.22.1. games/atari800: Updated for version 4.2.0. games/commandergenius: Updated for version 2.3.9. games/gzdoom: Updated for version 4.3.3. gis/gdal: Updated for version 3.0.4. gis/mapnik: Updated for version 3.0.23. gis/proj-data: Added (proj datum grids). gis/proj: Updated for 7.0.0 and removed datumgrids. graphics/fontforge: Update gnulib to 20200127~e313a53 graphics/viewnior: New maintainer, minor fix. graphics/vuescan: Updated for version 9.7.24. graphics/white_dune: Updated for version 1.822. ham/chirp: Updated for version 20200227. libraries/libinput: Updated for version 1.15.3. libraries/libopenshot-audio: Updated for version 0.2.0 libraries/libopenshot: Updated for version 0.2.5 libraries/libpwquality: New maintainer. libraries/libvterm: Updated for version 0.1.3. libraries/live555: Updated for version 2020.03.06 libraries/skalibs: Updated for version 2.9.2.0. libraries/unibilium: Updated for version 2.1.0. misc/mosquitto: Updated for version 1.6.9 misc/rarcrack: New maintainer, various fixes. multimedia/get_iplayer: Updated for version 3.25. multimedia/musixmatch: Added (Lyrics finder). multimedia/openshot: Updated for version 2.5.1 multimedia/straw-viewer: Added (search/stream videos from youtube). multimedia/youtube-viewer: Updated for version 3.7.4. network/Electrum: Update DEP. network/anydesk: Updated for version 5.5.4. network/axel: Updated for version 2.17.7. network/dropbox: Updated for version 92.4.382. network/nordvpn: Update README. network/opera-developer: Updated for version 68.0.3616.0. network/opera: Updated for version 67.0.3575.53. network/shorewall-core: Updated for version 5.2.3.6. network/shorewall6: Updated for version 5.2.3.6. network/shorewall: Updated for version 5.2.3.6. network/signal-desktop: Updated for version 1.32.0. network/vivaldi: Updated for version 2.11.1811.47. network/vnstat: Updated for version 2.6. network/youtube-dl: Updated for version 2020.03.06. office/calibre-bin: Updated for version 4.12.0. office/keepassx: New maintainer. perl/MoarVM: Updated for version 2020.02.1. perl/nqp: Updated for version 2020.02.1. perl/perl-Algorithm-Combinatorics: New Maintainer perl/perl-Algorithm-Loops: New Maintainer perl/perl-Clone-PP: Added (Recursive copy). perl/perl-Crypt-OpenSSL-AES: Added (Crypt::OpenSSL::AES). perl/perl-Data-Printer: Added (Pretty Data::Dumper). perl/perl-Data-Validate-IP: Added (IPv4/IPv6 validation methods). perl/perl-Date-Manip: Updated for version 6.81. perl/perl-ExtUtils-Install: New maintainer. perl/perl-ExtUtils-ModuleMaker: New maintainer. perl/perl-File-Remove: New maintainer. perl/perl-File-Safe-Home: New maintainer. perl/perl-List-UtilsBy: Updated for version 0.11. perl/perl-Math-GMPz: New Maintainer perl/perl-Math-Int128: Added (Manipulate 128 bits integers). perl/perl-Math-Int64: Added (Manipulate 64 bits integers). perl/perl-Math-MPC: New Maintainer perl/perl-Math-Prime-Util-GMP: New Maintainer perl/perl-Math-Prime-Util: Added (prime numbers utilities). perl/perl-Module-Install: New maintainer. perl/perl-Number-Bites-Human: New maintainer. perl/perl-Sidef: New Maintainer perl/perl-String-PerlIdentifier: New maintainer. perl/perl-YAML-Tiny: New maintainer. perl/rakudo: Updated for version 2020.02.1. python/decorator: Updated for version 4.4.2. python/josepy: Updated for version 1.3.0. python/parso: Updated for version 0.6.2. python/python-branca: Updated for version 0.4.0. python/python3-multidict: Fix MD5SUM. python/python3-patsy: Added (statistical models). python/python3-seaborn: Added (statistical data visualization). python/python3-statsmodels: Added (Statistical computations models). ruby/rubygem-mail: Updated for version 2.7.1. ruby/rubygem-mini_mime: Added (A lightweight mime type lookup toy). ruby/rubygem-sync: Added (ruby module). ruby/rubygem-tins: Updated for version 1.24.1. ruby/sequel: Updated for version 5.30.0. ruby/sqlite3: Updated for version 1.4.2. system/agedu: Updated for version 20200206.963bc9d. system/dust: Updated for version 0.5.1. system/epson-inkjet-printer-escpr2: Updated for version 1.1.9. system/execline: Updated for version 2.6.0.0. system/image-analyzer: Updated for version 3.2.4. system/letsencrypt: Updated for version 1.3.0. system/logtool: Orphaned. system/logwatch: Updated for version 7.5.3. system/netdata: Fix missing dep. system/openrc-services: Update README. system/phoronix-test-suite: Updated for version 9.4.1. system/powershell: Updated for version 7.0.0. system/rEFInd: Updated for version 0.11.5 system/refind: Updated for version 0.11.5. system/s6-linux-init: Updated for version 1.0.4.0. system/s6-rc: Updated for version 0.5.1.2. system/s6: Updated for version 2.9.1.0. system/secure-delete: Orphaned. system/slpkg: Updated for version 3.8.5. system/vagrant-public-key: Added (Vagrant Public Key). system/wipe: Orphaned. system/zsh-syntax-highlighting: Updated for version 0.7.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Mar 7 07:20:23 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 7 Mar 2020 14:20:23 +0700 Subject: [Slackbuilds-users] Updates - 20200215.1 In-Reply-To: References: <3ab37a7d-879d-534c-a5a4-a26550adc383@slackbuilds.org> <76edbbc1-d7f1-f3a2-351e-f83a4393f3cc@o2.pl> <7a179386-2beb-8d6f-a912-9fad7df87896@web.de> Message-ID: <0949e00d-522d-9f97-62fd-d8a17a90a4bc@slackbuilds.org> > Too late for that. The version on the ftp server is now 1.758, dated > yesterday. > > Looks like they update often enough that your build will spend more > time broken than it will working: we only update weekly on Saturday, > meaning if they update on Monday or Tuesday, and you notice right away > and send an update for your script... by the time your updated script > hits the SBo site (on Saturday), the white_dune devs may have already > removed the source for your update. > > What you need is a place to host the source file yourself. Several users > on this list have web space, and might be willing to help you out. Hey J, i always pushed your source for white_dune into our SF link to make sure it stays there even when upstream removed the source from their server. I'm hoping you would do it from now. If you need access to SF project, please send me your SF username and i will grant you a developer access so you can upload the white_dune source on your own. 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 lists at osh.id.au Wed Mar 11 18:49:44 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Wed, 11 Mar 2020 11:49:44 -0700 Subject: [Slackbuilds-users] JabRef-5.x In-Reply-To: References: Message-ID: <00bed03e-9adb-4ef3-96f0-116a2f459eb5@www.fastmail.com> On Mon, 24 Feb 2020, at 8:40 AM, Rich Shepard wrote: > Mario, et al.: > > SBo has version 2.9.2 of JabRef (the bibliographic reference database > management system) which is so far past its best-used-by date that it has > mold on it. :-) JabRef 5.0 has now been released. -- Dave From rshepard at appl-ecosys.com Wed Mar 11 19:46:05 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Wed, 11 Mar 2020 12:46:05 -0700 (PDT) Subject: [Slackbuilds-users] JabRef-5.x In-Reply-To: <00bed03e-9adb-4ef3-96f0-116a2f459eb5@www.fastmail.com> References: <00bed03e-9adb-4ef3-96f0-116a2f459eb5@www.fastmail.com> Message-ID: On Wed, 11 Mar 2020, David O'Shaughnessy wrote: > JabRef 5.0 has now been released. Dave, Yes. I'm running the 5.1.dev snapshots. The major improvement is the built-in jave-13 so there's no need to install a specific version of Oracle's JDK for this application. Regards, Rich From willysr at slackbuilds.org Sat Mar 14 01:57:45 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 14 Mar 2020 08:57:45 +0700 Subject: [Slackbuilds-users] Updates - 20200314.1 Message-ID: <99e3779a-77f2-6172-e84b-f0af1032565d@slackbuilds.org> Hi The correct MD5SUM for libseccomp is 3a2c3b7539c1b6a933c20cd1fdcb2252. I have fixed it on my branch, but too late for this public update :( Sat Mar 14 01:46:54 UTC 2020 academic/gmsh: Updated for version 4.5.4. academic/pysam: Fix permission. academic/veusz: Updated for version 3.2. audio/guitarix: Updated for version 0.39.0. audio/quodlibet: New maintainer. business/stansoft: Updated for version 7.16. desktop/simplenote: Updated for version 1.14.0. development/bmake: Updated for version 20200212. development/composer: Updated for version 1.10.0 development/d-tools: Updated for version 2.091.0 development/dmd: Updated for version 2.091.0 development/julia: Restore libexec support. development/netbeans: Updated for version 11.3. development/openjdk7: Updated for version 7u251. development/openjdk8: Updated for version 8u242. development/radare2: Updated for version 4.3.1. development/universal-ctags: Updated for version 30cd8e0 games/domination: Updated for version 1.2.1. gis/proj-data: Fix md5sum. graphics/Blender: Updated for version 2.82a graphics/vuescan: Updated for version 9.7.25 graphics/vulkan-sdk: Updated for version 1.2.131.2. libraries/libQuotient: Added (cross-platform library). libraries/libseccomp: Updated for version 2.4.3. libraries/nv-codec-headers: Updated for version 9.1.23.1. libraries/ode: Updated for version 0.16.1. multimedia/straw-viewer: Updated for version 0.0.2+20200307_9089523. network/Quaternion: Added (A Qt5-based IM client for Matrix). network/asterisk: Update configure parameter. network/bitcoin: Updated for version 0.19.1. network/hiawatha: Updated for version 10.10. network/netcat-openbsd: New maintainer. network/opera-developer: Updated for version 69.0.3623.0. network/opera: Updated for version 67.0.3575.79. network/slimjet: Updated for version 25.0.10.0. network/tor-browser: Updated for version 9.0.6. network/windscribe: Added (Browse the web privately). network/zoom-linux: Updated for version 3.5.361976.0301. office/wps-office: Updated for version 11.1.0.9126.XA. perl/perl-MooX-StrictConstructor: Added (Perl Module). perl/perl-gnome2-canvas: New maintainer. perl/perl-gnome2-vfs: New maintainer. perl/perl-gnome2-wnck: New maintainer. perl/perl-gnome2: New maintainer. perl/perl-gtk2-imageview: New maintainer. python/PyGreSQL: Updated for version 5.1.1 python/mypy: Updated for version 0.770. python/pyewmh: Remove python2 support. python/python-faulthandler: Updated for version 3.2. system/ipmitool: Fix build on -current. system/kbfs: Updated for version 5.3.0_20200310205642. system/keybase: Updated for version 5.3.0. system/mailutils: Updated for version 3.9. system/musl: Updated for version 1.2.0. system/ossec-agent: Updated for version 3.6.0. system/ossec-local: Updated for version 3.6.0. system/ossec-server: Updated for version 3.6.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From wedinm at gmail.com Sat Mar 14 05:49:46 2020 From: wedinm at gmail.com (M Wedin) Date: Sat, 14 Mar 2020 06:49:46 +0100 Subject: [Slackbuilds-users] Updates - 20200314.1 In-Reply-To: <99e3779a-77f2-6172-e84b-f0af1032565d@slackbuilds.org> References: <99e3779a-77f2-6172-e84b-f0af1032565d@slackbuilds.org> Message-ID: 2020-03-14 2:57 GMT+01:00, Willy Sudiarto Raharjo : > Hi > > The correct MD5SUM for libseccomp is 3a2c3b7539c1b6a933c20cd1fdcb2252. > I have fixed it on my branch, but too late for this public update :( > > Sat Mar 14 01:46:54 UTC 2020 > academic/gmsh: Updated for version 4.5.4. > academic/pysam: Fix permission. > academic/veusz: Updated for version 3.2. > audio/guitarix: Updated for version 0.39.0. > audio/quodlibet: New maintainer. > business/stansoft: Updated for version 7.16. > desktop/simplenote: Updated for version 1.14.0. > development/bmake: Updated for version 20200212. > development/composer: Updated for version 1.10.0 > development/d-tools: Updated for version 2.091.0 > development/dmd: Updated for version 2.091.0 > development/julia: Restore libexec support. > development/netbeans: Updated for version 11.3. > development/openjdk7: Updated for version 7u251. > development/openjdk8: Updated for version 8u242. > development/radare2: Updated for version 4.3.1. > development/universal-ctags: Updated for version 30cd8e0 > games/domination: Updated for version 1.2.1. > gis/proj-data: Fix md5sum. > graphics/Blender: Updated for version 2.82a > graphics/vuescan: Updated for version 9.7.25 > graphics/vulkan-sdk: Updated for version 1.2.131.2. > libraries/libQuotient: Added (cross-platform library). > libraries/libseccomp: Updated for version 2.4.3. > libraries/nv-codec-headers: Updated for version 9.1.23.1. > libraries/ode: Updated for version 0.16.1. > multimedia/straw-viewer: Updated for version 0.0.2+20200307_9089523. > network/Quaternion: Added (A Qt5-based IM client for Matrix). > network/asterisk: Update configure parameter. > network/bitcoin: Updated for version 0.19.1. > network/hiawatha: Updated for version 10.10. > network/netcat-openbsd: New maintainer. > network/opera-developer: Updated for version 69.0.3623.0. > network/opera: Updated for version 67.0.3575.79. > network/slimjet: Updated for version 25.0.10.0. > network/tor-browser: Updated for version 9.0.6. > network/windscribe: Added (Browse the web privately). > network/zoom-linux: Updated for version 3.5.361976.0301. > office/wps-office: Updated for version 11.1.0.9126.XA. > perl/perl-MooX-StrictConstructor: Added (Perl Module). > perl/perl-gnome2-canvas: New maintainer. > perl/perl-gnome2-vfs: New maintainer. > perl/perl-gnome2-wnck: New maintainer. > perl/perl-gnome2: New maintainer. > perl/perl-gtk2-imageview: New maintainer. > python/PyGreSQL: Updated for version 5.1.1 > python/mypy: Updated for version 0.770. > python/pyewmh: Remove python2 support. > python/python-faulthandler: Updated for version 3.2. > system/ipmitool: Fix build on -current. > system/kbfs: Updated for version 5.3.0_20200310205642. > system/keybase: Updated for version 5.3.0. > system/mailutils: Updated for version 3.9. > system/musl: Updated for version 1.2.0. > system/ossec-agent: Updated for version 3.6.0. > system/ossec-local: Updated for version 3.6.0. > system/ossec-server: Updated for version 3.6.0. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > > From sombragris at sombragris.org Sat Mar 14 18:08:29 2020 From: sombragris at sombragris.org (Eduardo Sanchez) Date: Sat, 14 Mar 2020 15:08:29 -0300 Subject: [Slackbuilds-users] libseccomp: MD5 sum error Message-ID: <19c38.7342ca4beb.20200314150829.50dd9340@tiki.sombragris.org> Hi there, Using -current but I think this applies also to 14.2 so I post this here. After the latest update, libseccomp does not match its supplied checksum: > libseccomp: > MD5SUM check for libseccomp-2.4.3.tar.gz ... FAILED! > Expected: d2e04306c5a690621d1cac5e2d7c4dc8 > Found: 3a2c3b7539c1b6a933c20cd1fdcb2252 > Downloading again. 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 jebrhansen+SBo at gmail.com Sat Mar 14 19:38:21 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 14 Mar 2020 13:38:21 -0600 Subject: [Slackbuilds-users] libseccomp: MD5 sum error In-Reply-To: <19c38.7342ca4beb.20200314150829.50dd9340@tiki.sombragris.org> References: <19c38.7342ca4beb.20200314150829.50dd9340@tiki.sombragris.org> Message-ID: On Sat, Mar 14, 2020, 12:09 PM Eduardo Sanchez wrote: > Hi there, > > Using -current but I think this applies also to 14.2 so I post this > here. > > After the latest update, libseccomp does not match its supplied > checksum: > > > libseccomp: > > MD5SUM check for libseccomp-2.4.3.tar.gz ... FAILED! > > Expected: d2e04306c5a690621d1cac5e2d7c4dc8 > > Found: 3a2c3b7539c1b6a933c20cd1fdcb2252 > > Downloading again. > > Thanks, > > Eduardo > Willy already noticed this and announced it in the updates email. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arkadiusz at drabczyk.org Mon Mar 16 20:20:53 2020 From: arkadiusz at drabczyk.org (Arkadiusz Drabczyk) Date: Mon, 16 Mar 2020 21:20:53 +0100 Subject: [Slackbuilds-users] desktop/xvkbd: incorrect download link Message-ID: <20200316202053.GA5354@comp.lan> 403 Forbidden. Backup tarball with the same md5sum can be found at http://ftp.vim.org/ftp/pub/ftp/os/Linux/distr/quirky/quirky6/sources/alphabetical/x/xvkbd-3.8.tar.gz -- Arkadiusz Drabczyk From dpross1100 at msn.com Tue Mar 17 03:06:48 2020 From: dpross1100 at msn.com (Daniel Prosser) Date: Mon, 16 Mar 2020 23:06:48 -0400 Subject: [Slackbuilds-users] Bug in matplotlib setupext.py Message-ID: Hi, Matplotlib has a custom setupext.py script designed to stop the build when a dependency is not installed. However, it seems to have a bug which makes it crash with this error: Traceback (most recent call last):? File "setup.py", line 172, in ??? result = package.check()? File "/tmp/SBo/matplotlib-2.2.3/setupext.py", line 1480, in check??? print_status(package.name, req_fail_msg)NameError: global name 'package' is not defined Is this the expected behavior? The following patch will avoid the error and still stop the build if there is a missing dependency, with an actual helpful list of dependencies that have not been installed: --- setupext.py 2020-03-16 10:02:52.376214282 -0400 +++ setupext.py.new 2020-03-16 10:03:34.462812966 -0400 @@ -1477,7 +1477,7 @@ req_fail_msg += (os.linesep.join(not_available) + os.linesep*(2*sp_mult)) * min(1, len(not_available)) req_fail_msg += (os.linesep*2).join(wrong_version) - print_status(package.name, req_fail_msg) + print_status(pack_name, req_fail_msg) raise CheckFailed("missing or faulty third-party python packages") return "all third-party python packages are present" Regards, Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: From melikamp at melikamp.com Tue Mar 17 05:09:52 2020 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Mon, 16 Mar 2020 22:09:52 -0700 Subject: [Slackbuilds-users] compton/picom SlackBuild In-Reply-To: <20200317001151.hs4qexhvsp6llus3@hyperion.home> References: <20200317001151.hs4qexhvsp6llus3@hyperion.home> Message-ID: <14808980.RTZtVpqhvW@ithil> I cannot replicate the slackbuild behavior you are describing on Slackware 14.2. It seems to build perfectly. Also, Picom seems to be a fork of compton, perhaps it can be packaged separately. On Monday, March 16, 2020 20:11:51 you wrote: > Hi, > > Wanted to reach out to you regarding the compton slackbuild > before posting to SlackBuilds-users. > > The source code has changed to "Picom" so the slackbuild fails on > both the md5sum and the change to the extracted directory. > > Thanks, > -- > > ************************ > # Barry J. Grundy > # bgrundy at gmail.com > # bgrundy at linuxleo.com > ************************ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: This is a digitally signed message part. URL: From erik at slackbuilds.org Tue Mar 17 14:11:44 2020 From: erik at slackbuilds.org (Erik Hanson) Date: Tue, 17 Mar 2020 09:11:44 -0500 Subject: [Slackbuilds-users] desktop/xvkbd: incorrect download link In-Reply-To: <20200316202053.GA5354@comp.lan> References: <20200316202053.GA5354@comp.lan> Message-ID: On 3/16/20 3:20 PM, Arkadiusz Drabczyk wrote: > 403 Forbidden. Backup tarball with the same md5sum can be found at > http://ftp.vim.org/ftp/pub/ftp/os/Linux/distr/quirky/quirky6/sources/alphabetical/x/xvkbd-3.8.tar.gz Thanks for letting me know, I've bumped it to 4.0. -- Erik -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From melikamp at melikamp.com Wed Mar 18 03:48:38 2020 From: melikamp at melikamp.com (Ivan Zaigralin) Date: Tue, 17 Mar 2020 20:48:38 -0700 Subject: [Slackbuilds-users] compton/picom SlackBuild In-Reply-To: <20200317143652.wna3xx27vcaszj2k@hyperion.home> References: <20200317001151.hs4qexhvsp6llus3@hyperion.home> <14808980.RTZtVpqhvW@ithil> <20200317143652.wna3xx27vcaszj2k@hyperion.home> Message-ID: <2192867.oeRbYsUele@ithil> I am not sure why you are downloading this file. The link in .info file is different. Though, I have to say, there may be a problem with md5sum. I cannot guarantee an instant fix, but I will definitely start looking into this. On Tuesday, March 17, 2020 10:36:52 you wrote: > That's interesting...This is what I see when downloading the > source (from the link in the .info): > > > +barry at hyperion ~ $ wget > https://github.com/yshui/compton/archive/v7.2/compton-7.2.tar.gz > --2020-03-17 10:33:41-- > https://github.com/yshui/compton/archive/v7.2/compton-7.2.tar.gz Resolving > github.com (github.com)... 140.82.114.3 > ... > Saving to: ?compton-7.2.tar.gz? > > compton-7.2.tar.gz [ <=> ] 212.38K > 524KB/s in 0.4s > > 2020-03-17 10:33:43 (524 KB/s) - ?compton-7.2.tar.gz? saved [217474] > > +barry at hyperion ~ $ tar tzvf compton-7.2.tar.gz | head -n 5 > drwxrwxr-x root/root 0 2019-08-09 18:41 picom-7.2/ > drwxrwxr-x root/root 0 2019-08-09 18:41 picom-7.2/.circleci/ > -rw-rw-r-- root/root 2873 2019-08-09 18:41 > picom-7.2/.circleci/config.yml -rw-rw-r-- root/root 1085 2019-08-09 > 18:41 picom-7.2/.clang-format -rw-rw-r-- root/root 78 2019-08-09 > 18:41 picom-7.2/.editorconfig > On Mon 16.Mar'20 at 22:09, Ivan Zaigralin wrote: > > I cannot replicate the slackbuild behavior you are describing on Slackware > > 14.2. It seems to build perfectly. > > > > Also, Picom seems to be a fork of compton, perhaps it can be packaged > > separately.> > > On Monday, March 16, 2020 20:11:51 you wrote: > > > Hi, > > > > > > Wanted to reach out to you regarding the compton slackbuild > > > before posting to SlackBuilds-users. > > > > > > The source code has changed to "Picom" so the slackbuild fails on > > > both the md5sum and the change to the extracted directory. > > > > > > Thanks, > > > -- > > > > > > ************************ > > > # Barry J. Grundy > > > # bgrundy at gmail.com > > > # bgrundy at linuxleo.com > > > ************************ > > -- > > ************************ > # Barry J. Grundy > # bgrundy at gmail.com > # bgrundy at linuxleo.com > ************************ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: This is a digitally signed message part. URL: From edps.mundognu at gmail.com Wed Mar 18 12:17:08 2020 From: edps.mundognu at gmail.com (Edinaldo) Date: Wed, 18 Mar 2020 09:17:08 -0300 Subject: [Slackbuilds-users] compton/picom SlackBuild Message-ID: Hi guys, Picom is a fork of Compton, some files have the same name in Compton SlackBuild: --> /usr/bin/compton (symlink) was found in another package. Skipping. --> /usr/bin/compton-trans (symlink) was found in another package. Skipping. --> /usr/bin/compton-convgen.py was found in another package. Skipping. --> /usr/share/applications/compton.desktop was found in another package. Skipping. --> /usr/share/icons/hicolor/48x48/apps/compton.png was found in another package. Skipping. --> /usr/share/icons/hicolor/scalable/apps/compton.svg was found in another package. Skipping. Recently i made a SlackBuild for this and only work in Slack Current, not in 14.2. If you have interest i can send the entire script for you, i don't have interest in maintain it. Full log (build, install, remove on -current): http://dpaste.com/06TEAWZ Cheers, Ed From bgrundy at gmail.com Wed Mar 18 15:33:27 2020 From: bgrundy at gmail.com (Barry Grundy) Date: Wed, 18 Mar 2020 11:33:27 -0400 Subject: [Slackbuilds-users] compton/picom SlackBuild In-Reply-To: <2192867.oeRbYsUele@ithil> References: <20200317001151.hs4qexhvsp6llus3@hyperion.home> <14808980.RTZtVpqhvW@ithil> <20200317143652.wna3xx27vcaszj2k@hyperion.home> <2192867.oeRbYsUele@ithil> Message-ID: Ah...the mistake is mine. I should have checked the build on SBo for 14.2 first. The issue is that I'm using ponce's repo for current and the SlackBuild is different in there. I've been using it for awhile now and forgot it's not the stock slackbuild. I should have realized being on -current caused the issue. My apologies. On Tue, Mar 17, 2020 at 11:48 PM Ivan Zaigralin wrote: > I am not sure why you are downloading this file. The link in .info file is > different. Though, I have to say, there may be a problem with md5sum. I > cannot guarantee an instant fix, but I will definitely start looking into > this. > > > > On Tuesday, March 17, 2020 10:36:52 you wrote: > > > That's interesting...This is what I see when downloading the > > > source (from the link in the .info): > > > > > > > > > +barry at hyperion ~ $ wget > > > https://github.com/yshui/compton/archive/v7.2/compton-7.2.tar.gz > > > --2020-03-17 10:33:41-- > > > https://github.com/yshui/compton/archive/v7.2/compton-7.2.tar.gz > Resolving > > > github.com (github.com)... 140.82.114.3 > > > ... > > > Saving to: ?compton-7.2.tar.gz? > > > > > > compton-7.2.tar.gz [ <=> ] 212.38K > > > 524KB/s in 0.4s > > > > > > 2020-03-17 10:33:43 (524 KB/s) - ?compton-7.2.tar.gz? saved [217474] > > > > > > +barry at hyperion ~ $ tar tzvf compton-7.2.tar.gz | head -n 5 > > > drwxrwxr-x root/root 0 2019-08-09 18:41 picom-7.2/ > > > drwxrwxr-x root/root 0 2019-08-09 18:41 picom-7.2/.circleci/ > > > -rw-rw-r-- root/root 2873 2019-08-09 18:41 > > > picom-7.2/.circleci/config.yml -rw-rw-r-- root/root 1085 2019-08-09 > > > 18:41 picom-7.2/.clang-format -rw-rw-r-- root/root 78 2019-08-09 > > > 18:41 picom-7.2/.editorconfig > > > On Mon 16.Mar'20 at 22:09, Ivan Zaigralin wrote: > > > > I cannot replicate the slackbuild behavior you are describing on > Slackware > > > > 14.2. It seems to build perfectly. > > > > > > > > Also, Picom seems to be a fork of compton, perhaps it can be packaged > > > > separately.> > > > > On Monday, March 16, 2020 20:11:51 you wrote: > > > > > Hi, > > > > > > > > > > Wanted to reach out to you regarding the compton slackbuild > > > > > before posting to SlackBuilds-users. > > > > > > > > > > The source code has changed to "Picom" so the slackbuild fails on > > > > > both the md5sum and the change to the extracted directory. > > > > > > > > > > Thanks, > > > > > -- > > > > > > > > > > ************************ > > > > > # Barry J. Grundy > > > > > # bgrundy at gmail.com > > > > > # bgrundy at linuxleo.com > > > > > ************************ > > > > > > -- > > > > > > ************************ > > > # Barry J. Grundy > > > # bgrundy at gmail.com > > > # bgrundy at linuxleo.com > > > ************************ > -- ---- Barry Grundy bgrundy at gmail.com bgrundy at linuxleo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Fri Mar 20 18:59:48 2020 From: didier at slint.fr (Didier Spaier) Date: Fri, 20 Mar 2020 19:59:48 +0100 Subject: [Slackbuilds-users] Packaging questions Message-ID: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> Hi, I intend to upgrade espeakup, dynamically linked to espeak-ng not espeak, as speech is then way better (tested by Slint users). Indeed I will provide a SlackBuild for espeak-ng but that leads to a few questions. For both espeakup and espeak-ng I do a "git archive ". 1. How should I name $VERSION? git, , git_commit? 2. If I indicate in the README the command to use to get the source archive, tools that automatize source downloads won't work. Is there a recommended place to store the source archive? 3. For espeak-ng I use tools like pandoc and ruby-ronn to build the documentation. As it seems unreasonable to require them, can I assume that including their output in the tarball is OK? Thanks, Didier From matteo.bernardini at gmail.com Fri Mar 20 19:15:53 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 20 Mar 2020 20:15:53 +0100 Subject: [Slackbuilds-users] Packaging questions In-Reply-To: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> References: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> Message-ID: Il giorno ven 20 mar 2020 alle ore 20:00 Didier Spaier ha scritto: > > Hi, > > I intend to upgrade espeakup, dynamically linked to espeak-ng not > espeak, as speech is then way better (tested by Slint users). > > Indeed I will provide a SlackBuild for espeak-ng but that leads to a few > questions. > > For both espeakup and espeak-ng I do a "git archive ". > > 1. How should I name $VERSION? git, , git_commit? I usually use the date and the commit as $VERSION (without any "git" prefix), resulting in a string like "20200320_4e2af03" so that I have also an indication of the date of the commit. but AFAIK there's no fixed standard. > 2. If I indicate in the README the command to use to get the source > archive, tools that automatize source downloads won't work. Is there a > recommended place to store the source archive? if you have a sourceforge.net account and ask Willy permissions, I think you could use slackbuildsdirectlinks https://sourceforge.net/projects/slackbuildsdirectlinks/ > 3. For espeak-ng I use tools like pandoc and ruby-ronn to build the > documentation. As it seems unreasonable to require them, can I assume > that including their output in the tarball is OK? it's just a suggestion but the best course IMHO would be to make the docs optional, activating the build of them with a variable (like DOCS=yes), and indicating in the README that they will need the optional dependencies pandoc and ruby-ronn to build. Matteo From yalhcru at gmail.com Fri Mar 20 20:25:04 2020 From: yalhcru at gmail.com (B Watson) Date: Fri, 20 Mar 2020 16:25:04 -0400 Subject: [Slackbuilds-users] Packaging questions In-Reply-To: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> References: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> Message-ID: On 3/20/20, Didier Spaier wrote: > Hi, > > I intend to upgrade espeakup, dynamically linked to espeak-ng not > espeak, as speech is then way better (tested by Slint users). > > Indeed I will provide a SlackBuild for espeak-ng but that leads to a few > questions. > > For both espeakup and espeak-ng I do a "git archive ". > > 1. How should I name $VERSION? git, , git_commit? epeak-ng version 1.50 was released 4 months ago, is the latest git really that much better than the release? If not, I'd stick with the release. If you decide you really have to upgrade to the latest git, I'd recommend using a version number like this: 1.50+yyyymmdd_ where yyyymmdd is the date of the commit, and is the 7-digit commit ID. In fact... I was gonna say, use the git2tarxz.sh script from multimedia/straw-viewer, but I had to modify it some to make it work with espeak-ng (due to them using tags in a way my script wasn't smart enough to handle). So try this: http://urchlay.naptime.net/~urchlay/src/git2tarxz.sh.espeak-ng The result is a tarball called espeak-ng-1.50+20200317_7a44961a.tar.xz, which you can use as your source and host somewhere. Since you're talking about including pregenerated docs (below), you'll want to add them to this tarball. If you use the git2tarxz script, please do include it in your SlackBuild tarball. > 2. If I indicate in the README the command to use to get the source > archive, tools that automatize source downloads won't work. Is there a > recommended place to store the source archive? Possibly here: https://sourceforge.net/projects/slackbuildsdirectlinks/ > 3. For espeak-ng I use tools like pandoc and ruby-ronn to build the > documentation. As it seems unreasonable to require them, can I assume > that including their output in the tarball is OK? Yes, I'd say including prebuilt docs is a good solution, *especially* since pandoc has 138 (!) dependencies. If some of the docs are strictly for developers (e.g. guide to hacking on its source, API documentation on how to use espeak-ng as a library), I'd even say don't include them at all, or add a DOCS=yes variable (defaulting to no). The vast majority of users aren't going to need developer docs, it's sorta silly to make them chase down a huge chain of dependencies to build documentation they aren't going to read. From didier at slint.fr Fri Mar 20 21:36:18 2020 From: didier at slint.fr (Didier Spaier) Date: Fri, 20 Mar 2020 22:36:18 +0100 Subject: [Slackbuilds-users] Packaging questions In-Reply-To: References: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> Message-ID: <107c25ed-de3e-d20e-a8a1-3d04cfc0ffdb@slint.fr> Le 20/03/2020 ? 21:25, B Watson a ?crit?: > On 3/20/20, Didier Spaier wrote: >> Hi, >> >> I intend to upgrade espeakup, dynamically linked to espeak-ng not >> espeak, as speech is then way better (tested by Slint users). >> >> Indeed I will provide a SlackBuild for espeak-ng but that leads to a few >> questions. >> >> For both espeakup and espeak-ng I do a "git archive ". >> >> 1. How should I name $VERSION? git, , git_commit? > > epeak-ng version 1.50 was released 4 months ago, is the latest git really > that much better than the release? If not, I'd stick with the release. Thare have been several fixes that worth an upgrade, I think. And the version I consider is already used in Slint since two weeks with no reported issue (I have explicitly requested a feedback), both in console mode through espeakup and in graphical environments through speech-dispatcher and Orca. > If you decide you really have to upgrade to the latest git, I'd recommend > using a version number like this: > > 1.50+yyyymmdd_ > > where yyyymmdd is the date of the commit, and is the 7-digit > commit ID. Will do. > In fact... I was gonna say, use the git2tarxz.sh script from > multimedia/straw-viewer, but I had to modify it some to make it work > with espeak-ng (due to them using tags in a way my script wasn't smart > enough to handle). > > So try this: http://urchlay.naptime.net/~urchlay/src/git2tarxz.sh.espeak-ng > > The result is a tarball called espeak-ng-1.50+20200317_7a44961a.tar.xz, > which you can use as your source and host somewhere. Since you're talking > about including pregenerated docs (below), you'll want to add them to > this tarball. > > If you use the git2tarxz script, please do include it in your SlackBuild > tarball. Will do, thanks for sharing. I have a similar script but targeting a locally cloned repository, so yours is indeed better to ship as the SlackBuild's user can then re-generate the archive if he or she wants to. >> 2. If I indicate in the README the command to use to get the source >> archive, tools that automatize source downloads won't work. Is there a >> recommended place to store the source archive? > > Possibly here: https://sourceforge.net/projects/slackbuildsdirectlinks/ This was also suggested by Matteo (thanks!). On second thought I could as well store these archive on my own server (Linode VPS) as they are not big. >> 3. For espeak-ng I use tools like pandoc and ruby-ronn to build the >> documentation. As it seems unreasonable to require them, can I assume >> that including their output in the tarball is OK? > > Yes, I'd say including prebuilt docs is a good solution, *especially* > since pandoc has 138 (!) dependencies. > > If some of the docs are strictly for developers (e.g. guide to hacking > on its source, API documentation on how to use espeak-ng as a library), > I'd even say don't include them at all, or add a DOCS=yes variable > (defaulting to no). The vast majority of users aren't going to need > developer docs, it's sorta silly to make them chase down a huge chain > of dependencies to build documentation they aren't going to read. I will check that and probably include prebuilt docs. Cheers, Didier From jebrhansen+SBo at gmail.com Sat Mar 21 00:00:06 2020 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Fri, 20 Mar 2020 18:00:06 -0600 Subject: [Slackbuilds-users] Packaging questions In-Reply-To: <107c25ed-de3e-d20e-a8a1-3d04cfc0ffdb@slint.fr> References: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> <107c25ed-de3e-d20e-a8a1-3d04cfc0ffdb@slint.fr> Message-ID: On Fri, Mar 20, 2020, 3:36 PM Didier Spaier wrote: > Le 20/03/2020 ? 21:25, B Watson a ?crit : > > On 3/20/20, Didier Spaier wrote: > >> Hi, > >> > >> I intend to upgrade espeakup, dynamically linked to espeak-ng not > >> espeak, as speech is then way better (tested by Slint users). > >> > >> Indeed I will provide a SlackBuild for espeak-ng but that leads to a few > >> questions. > >> > >> For both espeakup and espeak-ng I do a "git archive ". > >> > >> 1. How should I name $VERSION? git, , git_commit? > > > > epeak-ng version 1.50 was released 4 months ago, is the latest git really > > that much better than the release? If not, I'd stick with the release. > > Thare have been several fixes that worth an upgrade, I think. And the > version I consider is already used in Slint since two weeks with no > reported issue (I have explicitly requested a feedback), both in console > mode through espeakup and in graphical environments through > speech-dispatcher > and Orca. > > > If you decide you really have to upgrade to the latest git, I'd recommend > > using a version number like this: > > > > 1.50+yyyymmdd_ > > > > where yyyymmdd is the date of the commit, and is the 7-digit > > commit ID. > > Will do. > > > In fact... I was gonna say, use the git2tarxz.sh script from > > multimedia/straw-viewer, but I had to modify it some to make it work > > with espeak-ng (due to them using tags in a way my script wasn't smart > > enough to handle). > > > > So try this: > http://urchlay.naptime.net/~urchlay/src/git2tarxz.sh.espeak-ng > > > > The result is a tarball called espeak-ng-1.50+20200317_7a44961a.tar.xz, > > which you can use as your source and host somewhere. Since you're talking > > about including pregenerated docs (below), you'll want to add them to > > this tarball. > > > > If you use the git2tarxz script, please do include it in your SlackBuild > > tarball. > > Will do, thanks for sharing. I have a similar script but targeting a > locally cloned repository, so yours is indeed better to ship as the > SlackBuild's user can then re-generate the archive if he or she wants to. > > >> 2. If I indicate in the README the command to use to get the source > >> archive, tools that automatize source downloads won't work. Is there a > >> recommended place to store the source archive? > > > > Possibly here: https://sourceforge.net/projects/slackbuildsdirectlinks/ > > This was also suggested by Matteo (thanks!). On second thought I could > as well store these archive on my own server (Linode VPS) as they are > not big. > > >> 3. For espeak-ng I use tools like pandoc and ruby-ronn to build the > >> documentation. As it seems unreasonable to require them, can I assume > >> that including their output in the tarball is OK? > > > > Yes, I'd say including prebuilt docs is a good solution, *especially* > > since pandoc has 138 (!) dependencies. > > > > If some of the docs are strictly for developers (e.g. guide to hacking > > on its source, API documentation on how to use espeak-ng as a library), > > I'd even say don't include them at all, or add a DOCS=yes variable > > (defaulting to no). The vast majority of users aren't going to need > > developer docs, it's sorta silly to make them chase down a huge chain > > of dependencies to build documentation they aren't going to read. > > I will check that and probably include prebuilt docs. > > Cheers, > Didier > Is there a reason to host a tarball separately vs just grabbing the tarball directly from GitHub? You can download the source from a specific commit using the following URL (based on the latest commit, but you can just switch it to the commit you need - hopefully I did it right, since I'm doing this on my phone). You aren't limited to just downloading releases. https://github.com/espeak-ng/espeak-ng/archive/7a44961/espeak-ng-7a44961ac3abce0b390131c9832085e9eba0b92c.tar.gz If you want to see an example of how I do this in a SlackBuild, check out glportal on SBo. http://slackbuilds.org/repository/14.2/games/glportal/ Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Mar 21 02:12:45 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 21 Mar 2020 09:12:45 +0700 Subject: [Slackbuilds-users] Updates - 20200321.1 Message-ID: Sat Mar 21 02:01:07 UTC 2020 academic/boinc: update dependency list academic/verilator: Added (Verilog HDL Simulator). audio/fmmidi: Fix homepage. desktop/notion: Updated for version 4.0.0. desktop/simplenote: Updated for version 1.15.1. desktop/wmalauncher: Updated for version 2020.0124. desktop/xtrlock: Updated for version 2.13. desktop/xvkbd: Updated for version 4.0. development/beautysh: Updated for version 6.0.1. development/dotnet-sdk: Updated for version 3.1.200. development/eclipse-php: Add missing png file. development/eclipse-php: Updated for version 4.14. development/fossil: Update script. development/google-go-lang: updated for version 1.13.8. development/hexinator: Updated for version 1.10. development/minikube: Updated for version 1.8.2. development/vscode-bin: Updated for version 1.43.1. development/yarn: Updated for version 1.22.4. games/crispy-doom: Updated for version 5.7.2. games/ioquake3: Updated for version r20200211. gis/geos: Updated for version 3.8.1. ham/cqrlog: Updated for version 2.4.0. ham/qsstv: Updated for version 9.4.4. libraries/jbig2dec: Updated for version 0.18. libraries/jbigkit: Include libjbig85. libraries/libdwarf: Added (DWARF parser/generator library). libraries/libinput: Updated for version 1.15.4. libraries/libmaxminddb: Updated for version 1.4.2. libraries/libseccomp: Fix MD5SUM. libraries/libuv: Updated for version 1.35.0. libraries/tbb: Updated for version 2020u1. misc/font-unscii: Added (bitmapped Unicode font). misc/ghostpcl: Updated for version 9.51. misc/grc: Orphaned. misc/protobuf3: Updated for version 3.11.4. misc/vttest: Updated for version 2.7.20200303. misc/weather: Updated for version 2.3. multimedia/flashplayer-plugin: Updated for version 32.0.0.344. multimedia/pepperflash-plugin: Updated for version 32.0.0.344. multimedia/plexmediaserver: Updated for v 1.18.8.2527_740d4c206. multimedia/vobsub2srt: Added (convert VOBSUB subtitles to SRT). network/AdGuardHome: Updated for version 0.101.0. network/bluejeans: Updated for version 2.1.0. network/firewalld: Update script. network/neomutt: Updated for version 20200320. network/opera: Updated for version 67.0.3575.97. network/pCloudDrive: Added (pCloud client and drive mounter). network/qutebrowser-tox: Add missing README.SBo. network/qutebrowser-tox: Update OpenSSL. network/signal-desktop: Updated for version 1.32.1. network/slimjet: Updated for version 25.0.11.0. network/speedtest-cli: Switch to python3. network/telegram: Updated for version 1.9.21. network/tor: Updated for version 0.4.2.7. network/wireguard-linux-compat: Updated for version 0.0.20200318. network/wireguard-tools: Updated for version 1.0.20200319. network/youtube-dl: Updated for version 2020.03.08. office/smoffice2018: Updated for version 2018_976. office/taskjuggler: Updated for version 3.7.1. perl/perl-Math-GMPq: Orphaned. python/bleach: Updated for version 3.1.3. python/python-configargparse: Updated for version 1.1. ruby/rubygem-term-ansicolor: Updated for version 1.7.1. system/ansible: Updated for version 2.9.6. system/apparmor: Updated for version 2.13.4. system/consolation: Added (copy-paste for the Linux console). system/dosbox-x: Updated for version 0.83.0. system/epson-inkjet-printer-escpr2: Updated for version 1.1.10. system/man-db: Updated for version 2.9.1. system/unicode-character-database: Updated for version 13.0.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sat Mar 21 02:46:04 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 20 Mar 2020 19:46:04 -0700 Subject: [Slackbuilds-users] Packaging questions In-Reply-To: <107c25ed-de3e-d20e-a8a1-3d04cfc0ffdb@slint.fr> References: <74ce70c6-3298-3f37-d0f1-eb6d81d5330a@slint.fr> <107c25ed-de3e-d20e-a8a1-3d04cfc0ffdb@slint.fr> Message-ID: <49855072-44c8-78dc-7db7-a408bdf7c514@gmail.com> On 3/20/20 2:36 PM, Didier Spaier wrote: > Le 20/03/2020 ? 21:25, B Watson a ?crit?: >> On 3/20/20, Didier Spaier wrote: >>> Hi, >>> >>> I intend to upgrade espeakup, dynamically linked to espeak-ng not >>> espeak, as speech is then way better (tested by Slint users). >>> >>> Indeed I will provide a SlackBuild for espeak-ng but that leads to a few >>> questions. >>> >>> For both espeakup and espeak-ng I do a "git archive ". >>> >>> 1. How should I name $VERSION? git, , git_commit? >> >> epeak-ng version 1.50 was released 4 months ago, is the latest git really >> that much better than the release? If not, I'd stick with the release. > > Thare have been several fixes that worth an upgrade, I think. And the > version I consider is already used in Slint since two weeks with no > reported issue (I have explicitly requested a feedback), both in console > mode through espeakup and in graphical environments through speech-dispatcher > and Orca. > If the size of the fixes aren't too large, you can just include those patch(es) in the script tarball and have your script patch the source in the fly. Then you won't need to host the source code somewhere. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jim.diamond at acadiau.ca Sat Mar 21 17:22:27 2020 From: jim.diamond at acadiau.ca (James Diamond) Date: Sat, 21 Mar 2020 17:22:27 +0000 Subject: [Slackbuilds-users] Unstated requirement (apparently) to build octave Message-ID: <20200321172225.GA12950@jdiamond-mb.acadiau.ca> Hi, I often ssh in to a much faster machine to run sboupgrade to build new versions of various SB packages. It turns out that when I try this with octave, it fails repeatably. But if I VNC in and run it from a terminal open on that machine, it succeeds. It seems that while building it wants to use/access/look at/investigate/... the graphics, and that fails during an ssh -Y connection. Possibly if I reset DISPLAY it would be happy. Or didn't use -Y. Or something else... In any case, should someone add a comment to the README about this, to keep other people who might run into this from wasting too much of their time? Cheers. Jim From matteo.bernardini at gmail.com Sat Mar 21 18:52:54 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 21 Mar 2020 19:52:54 +0100 Subject: [Slackbuilds-users] Unstated requirement (apparently) to build octave In-Reply-To: <20200321172225.GA12950@jdiamond-mb.acadiau.ca> References: <20200321172225.GA12950@jdiamond-mb.acadiau.ca> Message-ID: Il giorno sab 21 mar 2020 alle ore 18:22 James Diamond via SlackBuilds-users ha scritto: > > Hi, > > I often ssh in to a much faster machine to run sboupgrade to build new > versions of various SB packages. It turns out that when I try this > with octave, it fails repeatably. But if I VNC in and run it from a > terminal open on that machine, it succeeds. > > It seems that while building it wants to use/access/look at/investigate/... > the graphics, and that fails during an ssh -Y connection. Possibly if I > reset DISPLAY it would be happy. Or didn't use -Y. Or something else... > > In any case, should someone add a comment to the README about this, to > keep other people who might run into this from wasting too much of > their time? > > Cheers. > > Jim Hi Jim, I don't know what's happening there but I just built octave successfully on my headless slackware64-14.2 virtual machine. Matteo From jim.diamond at acadiau.ca Sat Mar 21 19:29:32 2020 From: jim.diamond at acadiau.ca (James Diamond) Date: Sat, 21 Mar 2020 19:29:32 +0000 Subject: [Slackbuilds-users] Unstated requirement (apparently) to build octave In-Reply-To: References: <20200321172225.GA12950@jdiamond-mb.acadiau.ca> Message-ID: <20200321192930.GA20012@jdiamond-mb.acadiau.ca> On Sat, Mar 21, 2020 at 19:52 (+0100), Matteo Bernardini wrote: > Il giorno sab 21 mar 2020 alle ore 18:22 James Diamond via > SlackBuilds-users ha scritto: >> Hi, >> I often ssh in to a much faster machine to run sboupgrade to build new >> versions of various SB packages. It turns out that when I try this >> with octave, it fails repeatably. But if I VNC in and run it from a >> terminal open on that machine, it succeeds. >> It seems that while building it wants to use/access/look at/investigate/... >> the graphics, and that fails during an ssh -Y connection. Possibly if I >> reset DISPLAY it would be happy. Or didn't use -Y. Or something else... >> In any case, should someone add a comment to the README about this, to >> keep other people who might run into this from wasting too much of >> their time? >> Cheers. >> Jim > Hi Jim, > I don't know what's happening there but I just built octave > successfully on my headless slackware64-14.2 virtual machine. Hi Matteo, interesting. I wish I had saved the error messages (I will regenerate them if anyone is particularly interested, but they occur after a lot of compiling, when the tests are being done). Perhaps in your case the test suite recognizes that there is no graphics card and doesn't try various tests, or, at least, doesn't get fooled by the fact that the local graphics card and the $DISPLAY graphics card don't match. Cheers Jim From matteo.bernardini at gmail.com Sat Mar 21 19:46:12 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 21 Mar 2020 20:46:12 +0100 Subject: [Slackbuilds-users] Unstated requirement (apparently) to build octave In-Reply-To: <20200321192930.GA20012@jdiamond-mb.acadiau.ca> References: <20200321172225.GA12950@jdiamond-mb.acadiau.ca> <20200321192930.GA20012@jdiamond-mb.acadiau.ca> Message-ID: Il giorno sab 21 mar 2020 alle ore 20:29 James Diamond via SlackBuilds-users ha scritto: > > On Sat, Mar 21, 2020 at 19:52 (+0100), Matteo Bernardini wrote: > > > Il giorno sab 21 mar 2020 alle ore 18:22 James Diamond via > > SlackBuilds-users ha scritto: > > >> Hi, > > >> I often ssh in to a much faster machine to run sboupgrade to build new > >> versions of various SB packages. It turns out that when I try this > >> with octave, it fails repeatably. But if I VNC in and run it from a > >> terminal open on that machine, it succeeds. > > >> It seems that while building it wants to use/access/look at/investigate/... > >> the graphics, and that fails during an ssh -Y connection. Possibly if I > >> reset DISPLAY it would be happy. Or didn't use -Y. Or something else... > > >> In any case, should someone add a comment to the README about this, to > >> keep other people who might run into this from wasting too much of > >> their time? > > >> Cheers. > > >> Jim > > > Hi Jim, > > > I don't know what's happening there but I just built octave > > successfully on my headless slackware64-14.2 virtual machine. > > Hi Matteo, > > interesting. I wish I had saved the error messages (I will regenerate > them if anyone is particularly interested, but they occur after a lot > of compiling, when the tests are being done). > > Perhaps in your case the test suite recognizes that there is no > graphics card and doesn't try various tests, or, at least, doesn't get > fooled by the fact that the local graphics card and the $DISPLAY > graphics card don't match. > > Cheers > > Jim FWIW, # lspci | grep VGA 00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) # set | grep DISPLAY # IMHO code running on the host executing the SlackBuild has no way to know which hardware is on a remote DISPLAY. Matteo From kev4321 at fastmail.fm Sat Mar 21 22:29:36 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Sat, 21 Mar 2020 17:29:36 -0500 Subject: [Slackbuilds-users] zoom-linux crash Message-ID: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> My computer:? Thinkpad T440p? Slackware 14.2 with many packages from SBo. video: Nvidia GeForce GT 730M and Intel i5-4200M with GPU I mention the video because it may have something to do with the problem. zoom-linux gives a flash on the screen and crashes. $ zoom-linux & . . . Graphics Card Info:: Zoom package arch is 64bit, runing OS arch is x86_64 AppIconMgr::systemDesktopName log Desktop Name:? QGLXContext: Failed to create dummy context qt.scenegraph.general: QSG: basic render loop qt.scenegraph.general: Using sg animation driver qt.svg: link image0 hasn't been detected! qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0 Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile? QSurfaceFormat::OpenGLContextProfile(NoProfile)) ZoomLauncher: new dump generated from pid 20534, path: /home/XXXXX/.zoom/logs/1524b74b-f164-461a-8ad868b2-dbb81244.dmp $HOME = /home/XXXXX sh: line 1: 20534 Aborted???????????????? /opt/zoom-linux/zoom "" success to create child process,status is 34304. zoom exited normally. Something went wrong while running zoom,exit code is 134. ZoomLauncher exit. I can't find anything helpful on this. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From JimDiamond at ns.sympatico.ca Sun Mar 22 00:05:32 2020 From: JimDiamond at ns.sympatico.ca (Jim Diamond) Date: Sat, 21 Mar 2020 21:05:32 -0300 Subject: [Slackbuilds-users] Unstated requirement (apparently) to build octave In-Reply-To: References: <20200321172225.GA12950@jdiamond-mb.acadiau.ca> <20200321192930.GA20012@jdiamond-mb.acadiau.ca> Message-ID: <20200322000532.GA6478@jdiamond-mb.acadiau.ca> Hi again Matteo, On Sat, Mar 21, 2020 at 20:46 (+0100), Matteo Bernardini wrote: > Il giorno sab 21 mar 2020 alle ore 20:29 James Diamond via > SlackBuilds-users ha scritto: >> On Sat, Mar 21, 2020 at 19:52 (+0100), Matteo Bernardini wrote: >>> Il giorno sab 21 mar 2020 alle ore 18:22 James Diamond via >>> SlackBuilds-users ha scritto: >>>> Hi, >>>> I often ssh in to a much faster machine to run sboupgrade to build new >>>> versions of various SB packages. It turns out that when I try this >>>> with octave, it fails repeatably. But if I VNC in and run it from a >>>> terminal open on that machine, it succeeds. >>>> It seems that while building it wants to use/access/look at/investigate/... >>>> the graphics, and that fails during an ssh -Y connection. Possibly if I >>>> reset DISPLAY it would be happy. Or didn't use -Y. Or something else... >>>> In any case, should someone add a comment to the README about this, to >>>> keep other people who might run into this from wasting too much of >>>> their time? >>>> Cheers. >>>> Jim >>> Hi Jim, >>> I don't know what's happening there but I just built octave >>> successfully on my headless slackware64-14.2 virtual machine. >> Hi Matteo, >> interesting. I wish I had saved the error messages (I will regenerate >> them if anyone is particularly interested, but they occur after a lot >> of compiling, when the tests are being done). >> Perhaps in your case the test suite recognizes that there is no >> graphics card and doesn't try various tests, or, at least, doesn't get >> fooled by the fact that the local graphics card and the $DISPLAY >> graphics card don't match. >> Cheers >> Jim > FWIW, > # lspci | grep VGA > 00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual > graphic card (rev 04) > # set | grep DISPLAY > # > IMHO code running on the host executing the SlackBuild has no way to > know which hardware is on a remote DISPLAY. Well, that may be so. However, after 1525 seconds of compiling on a somewhat low-end Xeon, here is the end of the show: ... help/which.m ................................................... PASS 8/8 image/cmpermute.m .............................................. PASS 19/19 image/cmunique.m ............................................... PASS 19/19 image/colormap.m ............................................... PASS 9/9 image/contrast.m ............................................... PASS 1/1 image/frame2im.m ............................................... PASS 4/4 image/getframe.m ...............................................libGL error: failed to authenticate magic 2 libGL error: failed to load driver: i965 fatal: caught signal Illegal instruction -- stopping myself... /bin/sh: line 1: 14187 Illegal instruction (core dumped) /bin/sh ../run-octave --norc --silent --no-history -p /tmp/SBo/octave-5.2.0/test/mex /tmp/SBo/octave-5.2.0/test/fntests.m /tmp/SBo/octave-5.2.0/test Makefile:27887: recipe for target 'check-local' failed make[3]: *** [check-local] Error 132 make[3]: Leaving directory '/tmp/SBo/octave-5.2.0' Makefile:26265: recipe for target 'check-am' failed make[2]: *** [check-am] Error 2 make[2]: Leaving directory '/tmp/SBo/octave-5.2.0' Makefile:25976: recipe for target 'check-recursive' failed make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/octave-5.2.0' Makefile:26267: recipe for target 'check' failed make: *** [check] Error 2 I will point out that on the compiling Xeon, I am using the Nouveau driver, and the string "965" does not appear anywhere in /var/log/Xorg.0.log. However, on the laptop I am ssh'ed in from, Xorg.0.log has [ 8.295] (II) Module vesa: vendor="X.Org Foundation" [ 8.295] compiled for 1.18.0, module version = 2.3.4 [ 8.295] Module class: X.Org Video Driver [ 8.295] ABI class: X.Org Video Driver, version 20.0 [ 8.295] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 Also, running xrandr and/or xdpyinfo from the Xeon shows that a program running on the Xeon can find out my screen configuration and other information, so I can imagine some nosy X program finding out what is going on. In fact, running glinfo on the Xeon gives output starting with libGL error: failed to authenticate magic 2 libGL error: failed to load driver: i965 GL_VERSION: 3.0 Mesa 11.2.2 so again, programs running on the Xeon can know a lot about the laptop from which I ssh'ed into the Xeon. This may have nothing to do with anything, but the fact that the above error message whined about i965 and the only i965 driver in use that I know about is the one on my laptop made me put those together. However, I freely admit the reasoning is not rock-solid. Cheers. Jim From kev4321 at fastmail.fm Sun Mar 22 00:27:46 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Sat, 21 Mar 2020 19:27:46 -0500 Subject: [Slackbuilds-users] zoom-linux crash In-Reply-To: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> References: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> Message-ID: <96d1796e-b590-9d68-74d9-bf981d21b5d4@fastmail.fm> A little more investigation reveals that the recommended driver for Geforce GT 730M is 418.1130,? I have 440,59 installed now. On 3/21/20 5:29 PM, Kevin McCormick wrote: > My computer:? Thinkpad T440p? > Slackware 14.2 with many packages from SBo. > video: Nvidia GeForce GT 730M and Intel i5-4200M with GPU > I mention the video because it may have something to do with the problem. > > zoom-linux gives a flash on the screen and crashes. > > $ zoom-linux & > . . . > Graphics Card Info:: > Zoom package arch is 64bit, runing OS arch is x86_64 > AppIconMgr::systemDesktopName log Desktop Name:? > QGLXContext: Failed to create dummy context > qt.scenegraph.general: QSG: basic render loop > qt.scenegraph.general: Using sg animation driver > qt.svg: link image0 hasn't been detected! > qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0 > Failed to create OpenGL context for format QSurfaceFormat(version 2.0, > options QFlags(), depthBufferSize 24, > redBufferSize -1, greenBufferSize -1, blueBufferSize -1, > alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior > QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile? > QSurfaceFormat::OpenGLContextProfile(NoProfile)) > ZoomLauncher: new dump generated from pid 20534, path: > /home/XXXXX/.zoom/logs/1524b74b-f164-461a-8ad868b2-dbb81244.dmp > $HOME = /home/XXXXX > sh: line 1: 20534 Aborted???????????????? /opt/zoom-linux/zoom "" > success to create child process,status is 34304. > zoom exited normally. > Something went wrong while running zoom,exit code is 134. > ZoomLauncher exit. > > I can't find anything helpful on this. > > 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/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From kev4321 at fastmail.fm Sun Mar 22 12:58:10 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Sun, 22 Mar 2020 07:58:10 -0500 Subject: [Slackbuilds-users] zoom-linux crash In-Reply-To: <96d1796e-b590-9d68-74d9-bf981d21b5d4@fastmail.fm> References: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> <96d1796e-b590-9d68-74d9-bf981d21b5d4@fastmail.fm> Message-ID: <5c957f7a-03ef-be69-eb87-bbe6e359c7a5@fastmail.fm> I should also add that kde will not start.? The splash screen appears, but then crashes to a black screen with the cursor in the upper left and no keyboard or mouse response.? Computer must be powered off by pressing the power button for 4 sec.? I tried "export KDE_DEBUG=True" but cannot find a dump file.? Using fluxbox is fine. On 3/21/20 7:27 PM, Kevin McCormick wrote: > A little more investigation reveals that the recommended driver for > Geforce GT 730M is 418.1130,? I have 440,59 installed now. > > > On 3/21/20 5:29 PM, Kevin McCormick wrote: >> My computer:? Thinkpad T440p? >> Slackware 14.2 with many packages from SBo. >> video: Nvidia GeForce GT 730M and Intel i5-4200M with GPU >> I mention the video because it may have something to do with the problem. >> >> zoom-linux gives a flash on the screen and crashes. >> >> $ zoom-linux & >> . . . >> Graphics Card Info:: >> Zoom package arch is 64bit, runing OS arch is x86_64 >> AppIconMgr::systemDesktopName log Desktop Name:? >> QGLXContext: Failed to create dummy context >> qt.scenegraph.general: QSG: basic render loop >> qt.scenegraph.general: Using sg animation driver >> qt.svg: link image0 hasn't been detected! >> qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0 >> Failed to create OpenGL context for format QSurfaceFormat(version >> 2.0, options QFlags(), depthBufferSize >> 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, >> alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior >> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile? >> QSurfaceFormat::OpenGLContextProfile(NoProfile)) >> ZoomLauncher: new dump generated from pid 20534, path: >> /home/XXXXX/.zoom/logs/1524b74b-f164-461a-8ad868b2-dbb81244.dmp >> $HOME = /home/XXXXX >> sh: line 1: 20534 Aborted???????????????? /opt/zoom-linux/zoom "" >> success to create child process,status is 34304. >> zoom exited normally. >> Something went wrong while running zoom,exit code is 134. >> ZoomLauncher exit. >> >> I can't find anything helpful on this. >> >> 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/ >> > > > _______________________________________________ > 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 kev4321 at fastmail.fm Sun Mar 22 18:16:26 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Sun, 22 Mar 2020 13:16:26 -0500 Subject: [Slackbuilds-users] zoom-linux crash In-Reply-To: <5c957f7a-03ef-be69-eb87-bbe6e359c7a5@fastmail.fm> References: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> <96d1796e-b590-9d68-74d9-bf981d21b5d4@fastmail.fm> <5c957f7a-03ef-be69-eb87-bbe6e359c7a5@fastmail.fm> Message-ID: Further information: removed the nvidia-kernel and nvidia-driver packages(440.59) and xf86-video-nouveau-blacklist package.? Now zoom-linux and kde seem to run fine.? Problem is display quality is far lower than when nvidia was installed.? Apparently, xorg was unloading nvidia and loading nouveau regardless of blacklist, shown in Xorg.0.log, but the nvidia libraries are so much better.? When I used /etc/X11/xorg.conf.d/10-nvidia.conf there was a crash with X regardless of window manager, so the issue is plainly using the wrong nvidia driver.? When I tried to manually use the NVIDIA-Linux***.run program, it claimed there was a kernel module present, so I halted at that point.?? The nvidia README lists possible library conflicts, which is a problem for me.? How does one package the 418.1130 driver and is nvidia-switch necessary? On 3/22/20 7:58 AM, Kevin McCormick wrote: > I should also add that kde will not start.? The splash screen appears, > but then crashes to a black screen with the cursor in the upper left > and no keyboard or mouse response.? Computer must be powered off by > pressing the power button for 4 sec.? I tried "export KDE_DEBUG=True" > but cannot find a dump file.? Using fluxbox is fine. > > On 3/21/20 7:27 PM, Kevin McCormick wrote: >> A little more investigation reveals that the recommended driver for >> Geforce GT 730M is 418.1130,? I have 440,59 installed now. >> >> >> On 3/21/20 5:29 PM, Kevin McCormick wrote: >>> My computer:? Thinkpad T440p? >>> Slackware 14.2 with many packages from SBo. >>> video: Nvidia GeForce GT 730M and Intel i5-4200M with GPU >>> I mention the video because it may have something to do with the >>> problem. >>> >>> zoom-linux gives a flash on the screen and crashes. >>> >>> $ zoom-linux & >>> . . . >>> Graphics Card Info:: >>> Zoom package arch is 64bit, runing OS arch is x86_64 >>> AppIconMgr::systemDesktopName log Desktop Name:? >>> QGLXContext: Failed to create dummy context >>> qt.scenegraph.general: QSG: basic render loop >>> qt.scenegraph.general: Using sg animation driver >>> qt.svg: link image0 hasn't been detected! >>> qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0 >>> Failed to create OpenGL context for format QSurfaceFormat(version >>> 2.0, options QFlags(), depthBufferSize >>> 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, >>> alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior >>> QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile? >>> QSurfaceFormat::OpenGLContextProfile(NoProfile)) >>> ZoomLauncher: new dump generated from pid 20534, path: >>> /home/XXXXX/.zoom/logs/1524b74b-f164-461a-8ad868b2-dbb81244.dmp >>> $HOME = /home/XXXXX >>> sh: line 1: 20534 Aborted???????????????? /opt/zoom-linux/zoom "" >>> success to create child process,status is 34304. >>> zoom exited normally. >>> Something went wrong while running zoom,exit code is 134. >>> ZoomLauncher exit. >>> >>> I can't find anything helpful on this. >>> >>> 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/ >>> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Sun Mar 22 18:30:11 2020 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 22 Mar 2020 12:30:11 -0600 Subject: [Slackbuilds-users] composer md5sum error Message-ID: slackbuilds.org/repository/14.2/development/composer/ Processing composer composer: Found composer.phar in /var/cache/sbopkg. Checking MD5SUM: MD5SUM check for composer.phar ... FAILED! Expected: 01bd034c495417327127f093b90e24e2 Found: 3756c596b9359c9b1be51b0d4c07ab19 Do you want to use the downloaded composer source: composer.phar in /var/cache/sbopkg? You can choose among the following options: - (Y)es, keep the source and continue the build process; - (N)o, delete the source and abort the build process; - (R)etry download and continue the build process; or - (A)ttempt to download from third party source repository. -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From belka at caraus.de Sun Mar 22 18:37:54 2020 From: belka at caraus.de (Eugen Wissner) Date: Sun, 22 Mar 2020 19:37:54 +0100 Subject: [Slackbuilds-users] composer md5sum error In-Reply-To: References: Message-ID: <17103897bd0.27a8.a5fd6ead26a950985989b4ffaa6e5bbe@caraus.de> You seem to have an older version in the cache. The checksum is correct. (R) should work. Am 22. M?rz 2020 19:30:26 schrieb Fernando Lopez : > slackbuilds.org/repository/14.2/development/composer/ > > > Processing composer > > composer: > Found composer.phar in /var/cache/sbopkg. > Checking MD5SUM: > MD5SUM check for composer.phar ... FAILED! > Expected: 01bd034c495417327127f093b90e24e2 > Found: 3756c596b9359c9b1be51b0d4c07ab19 > > Do you want to use the downloaded composer source: > composer.phar in /var/cache/sbopkg? > > You can choose among the following options: > - (Y)es, keep the source and continue the build process; > - (N)o, delete the source and abort the build process; > - (R)etry download and continue the build process; or > - (A)ttempt to download from third party source repository. > > -- > > > ------------ > Regards, > Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Sun Mar 22 18:42:59 2020 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Sun, 22 Mar 2020 12:42:59 -0600 Subject: [Slackbuilds-users] composer md5sum error In-Reply-To: <17103897bd0.27a8.a5fd6ead26a950985989b4ffaa6e5bbe@caraus.de> References: <17103897bd0.27a8.a5fd6ead26a950985989b4ffaa6e5bbe@caraus.de> Message-ID: my bad. thanks :) On Sun, Mar 22, 2020 at 12:37 PM Eugen Wissner wrote: > You seem to have an older version in the cache. The checksum is correct. > (R) should work. > > Am 22. M?rz 2020 19:30:26 schrieb Fernando Lopez < > fernando.lopezjr at gmail.com>: > >> slackbuilds.org/repository/14.2/development/composer/ >> >> Processing composer >> >> composer: >> Found composer.phar in /var/cache/sbopkg. >> Checking MD5SUM: >> MD5SUM check for composer.phar ... FAILED! >> Expected: 01bd034c495417327127f093b90e24e2 >> Found: 3756c596b9359c9b1be51b0d4c07ab19 >> >> Do you want to use the downloaded composer source: >> composer.phar in /var/cache/sbopkg? >> >> You can choose among the following options: >> - (Y)es, keep the source and continue the build process; >> - (N)o, delete the source and abort the build process; >> - (R)etry download and continue the build process; or >> - (A)ttempt to download from third party source repository. >> -- >> >> ------------ >> Regards, >> Fernando Lopez Jr. >> > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From elyk03 at gmail.com Sun Mar 22 20:25:03 2020 From: elyk03 at gmail.com (Kyle Guinn) Date: Sun, 22 Mar 2020 15:25:03 -0500 Subject: [Slackbuilds-users] Unstated requirement (apparently) to build octave In-Reply-To: <20200322000532.GA6478@jdiamond-mb.acadiau.ca> References: <20200321172225.GA12950@jdiamond-mb.acadiau.ca> <20200321192930.GA20012@jdiamond-mb.acadiau.ca> <20200322000532.GA6478@jdiamond-mb.acadiau.ca> Message-ID: On 3/21/20, Jim Diamond wrote: > Well, that may be so. However, after 1525 seconds of compiling on a > somewhat low-end Xeon, here is the end of the show: > ... > help/which.m ................................................... PASS > 8/8 > image/cmpermute.m .............................................. PASS > 19/19 > image/cmunique.m ............................................... PASS > 19/19 > image/colormap.m ............................................... PASS > 9/9 > image/contrast.m ............................................... PASS > 1/1 > image/frame2im.m ............................................... PASS > 4/4 > image/getframe.m ...............................................libGL > error: failed to authenticate magic 2 > libGL error: failed to load driver: i965 > fatal: caught signal Illegal instruction -- stopping myself... > /bin/sh: line 1: 14187 Illegal instruction (core dumped) /bin/sh > ../run-octave --norc --silent --no-history -p /tmp/SBo/octave-5.2.0/test/mex > /tmp/SBo/octave-5.2.0/test/fntests.m /tmp/SBo/octave-5.2.0/test > Makefile:27887: recipe for target 'check-local' failed > make[3]: *** [check-local] Error 132 > make[3]: Leaving directory '/tmp/SBo/octave-5.2.0' > Makefile:26265: recipe for target 'check-am' failed > make[2]: *** [check-am] Error 2 > make[2]: Leaving directory '/tmp/SBo/octave-5.2.0' > Makefile:25976: recipe for target 'check-recursive' failed > make[1]: *** [check-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/octave-5.2.0' > Makefile:26267: recipe for target 'check' failed > make: *** [check] Error 2 > > > I will point out that on the compiling Xeon, I am using the > Nouveau driver, and the string "965" does not appear anywhere in > /var/log/Xorg.0.log. > > However, on the laptop I am ssh'ed in from, Xorg.0.log has > [ 8.295] (II) Module vesa: vendor="X.Org Foundation" > [ 8.295] compiled for 1.18.0, module version = 2.3.4 > [ 8.295] Module class: X.Org Video Driver > [ 8.295] ABI class: X.Org Video Driver, version 20.0 > [ 8.295] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets: > i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, > 915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, > Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, > Q33, > GM45, 4 Series, G45/G43, Q45/Q43, G41, B43 > > Also, running xrandr and/or xdpyinfo from the Xeon shows that a > program running on the Xeon can find out my screen configuration and > other information, so I can imagine some nosy X program finding out > what is going on. In fact, running glinfo on the Xeon gives output > starting with > libGL error: failed to authenticate magic 2 > libGL error: failed to load driver: i965 > GL_VERSION: 3.0 Mesa 11.2.2 > so again, programs running on the Xeon can know a lot about the laptop > from which I ssh'ed into the Xeon. > > This may have nothing to do with anything, but the fact that the above > error message whined about i965 and the only i965 driver in use that I > know about is the one on my laptop made me put those together. > However, I freely admit the reasoning is not rock-solid. I've got a similar setup where I've SSH'd into other machines to build octave. I've seen some similar errors with some of the graphics tests, but none of them were fatal and it continued to build the package. If all else fails, just comment out the `make check` line. -Kyle From kev4321 at fastmail.fm Mon Mar 23 18:13:26 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Mon, 23 Mar 2020 13:13:26 -0500 Subject: [Slackbuilds-users] zoom-linux crash In-Reply-To: References: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> <96d1796e-b590-9d68-74d9-bf981d21b5d4@fastmail.fm> <5c957f7a-03ef-be69-eb87-bbe6e359c7a5@fastmail.fm> Message-ID: <86309700-01b7-6942-a8d7-1cd672d5be67@fastmail.fm> For the curious, I have resolved the situation for now by removing the nvidia drivers and also blacklisting nouveau.? This leaves only the intel i915 driver using the integrated intel graphics (HD4600).? So the nvidia GT 730M is unused.? This notebook uses Optimus technology, meaning the nvidia card cannot be used independently of the intel integrated GPU.? I am hoping that using only the intel GPU will give acceptable screen quality.? For this Thinkpad T440p, the nvidia-driver should probably be? nvidia-legacy390, built with GLVND="no" and also use the "pass-through" xorg settings from? http://us.download.nvidia.com/XFree86/Linux-x86_64/390.132/README/randr14.html.? I think my issues were caused by the nvidia OpenGL replacement libraries not working with Qt5. On 3/22/20 1:16 PM, Kevin McCormick wrote: > Further information: removed the nvidia-kernel and nvidia-driver > packages(440.59) and xf86-video-nouveau-blacklist package.? Now > zoom-linux and kde seem to run fine.? Problem is display quality is > far lower than when nvidia was installed.? Apparently, xorg was > unloading nvidia and loading nouveau regardless of blacklist, shown in > Xorg.0.log, but the nvidia libraries are so much better.? When I used > /etc/X11/xorg.conf.d/10-nvidia.conf there was a crash with X > regardless of window manager, so the issue is plainly using the wrong > nvidia driver.? When I tried to manually use the NVIDIA-Linux***.run > program, it claimed there was a kernel module present, so I halted at > that point.?? The nvidia README lists possible library conflicts, > which is a problem for me.? How does one package the 418.1130 driver > and is nvidia-switch necessary? > > On 3/22/20 7:58 AM, Kevin McCormick wrote: >> I should also add that kde will not start.? The splash screen >> appears, but then crashes to a black screen with the cursor in the >> upper left and no keyboard or mouse response.? Computer must be >> powered off by pressing the power button for 4 sec.? I tried "export >> KDE_DEBUG=True" but cannot find a dump file.? Using fluxbox is fine. >> >> On 3/21/20 7:27 PM, Kevin McCormick wrote: >>> A little more investigation reveals that the recommended driver for >>> Geforce GT 730M is 418.1130,? I have 440,59 installed now. >>> >>> >>> On 3/21/20 5:29 PM, Kevin McCormick wrote: >>>> My computer:? Thinkpad T440p? >>>> Slackware 14.2 with many packages from SBo. >>>> video: Nvidia GeForce GT 730M and Intel i5-4200M with GPU >>>> I mention the video because it may have something to do with the >>>> problem. >>>> >>>> zoom-linux gives a flash on the screen and crashes. >>>> >>>> $ zoom-linux & >>>> . . . >>>> Graphics Card Info:: >>>> Zoom package arch is 64bit, runing OS arch is x86_64 >>>> AppIconMgr::systemDesktopName log Desktop Name:? >>>> QGLXContext: Failed to create dummy context >>>> qt.scenegraph.general: QSG: basic render loop >>>> qt.scenegraph.general: Using sg animation driver >>>> qt.svg: link image0 hasn't been detected! >>>> qt.svg: :/images/wechat.svg:10:6: Could not resolve property: pattern0 >>>> Failed to create OpenGL context for format QSurfaceFormat(version >>>> 2.0, options QFlags(), >>>> depthBufferSize 24, redBufferSize -1, greenBufferSize -1, >>>> blueBufferSize -1, alphaBufferSize 8, stencilBufferSize 8, samples >>>> -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), >>>> swapInterval 1, profile? >>>> QSurfaceFormat::OpenGLContextProfile(NoProfile)) >>>> ZoomLauncher: new dump generated from pid 20534, path: >>>> /home/XXXXX/.zoom/logs/1524b74b-f164-461a-8ad868b2-dbb81244.dmp >>>> $HOME = /home/XXXXX >>>> sh: line 1: 20534 Aborted???????????????? /opt/zoom-linux/zoom "" >>>> success to create child process,status is 34304. >>>> zoom exited normally. >>>> Something went wrong while running zoom,exit code is 134. >>>> ZoomLauncher exit. >>>> >>>> I can't find anything helpful on this. >>>> >>>> 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/ >>>> >>> >>> >>> _______________________________________________ >>> SlackBuilds-users mailing list >>> SlackBuilds-users at slackbuilds.org >>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >>> FAQ - https://slackbuilds.org/faq/ >>> >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Mar 23 18:30:06 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 24 Mar 2020 01:30:06 +0700 Subject: [Slackbuilds-users] zoom-linux crash In-Reply-To: <86309700-01b7-6942-a8d7-1cd672d5be67@fastmail.fm> References: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> <96d1796e-b590-9d68-74d9-bf981d21b5d4@fastmail.fm> <5c957f7a-03ef-be69-eb87-bbe6e359c7a5@fastmail.fm> <86309700-01b7-6942-a8d7-1cd672d5be67@fastmail.fm> Message-ID: > For the curious, I have resolved the situation for now by removing the > nvidia drivers and also blacklisting nouveau.? This leaves only the > intel i915 driver using the integrated intel graphics (HD4600).? So the > nvidia GT 730M is unused.? This notebook uses Optimus technology, > meaning the nvidia card cannot be used independently of the intel > integrated GPU.? I am hoping that using only the intel GPU will give > acceptable screen quality.? For this Thinkpad T440p, the nvidia-driver > should probably be? nvidia-legacy390, built with GLVND="no" and also use > the "pass-through" xorg settings from? > http://us.download.nvidia.com/XFree86/Linux-x86_64/390.132/README/randr14.html.? > I think my issues were caused by the nvidia OpenGL replacement libraries > not working with Qt5. Hi, i tried to run zoom on my desktop with NVidia Driver 390.132 (from NVidia directly, not from SBo) and it worked fine here. PS: I'm using -current, to clarify things. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From rshepard at appl-ecosys.com Mon Mar 23 19:18:02 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Mar 2020 12:18:02 -0700 (PDT) Subject: [Slackbuilds-users] Last Saturday's updates Message-ID: I did not save Willy's message with the list of new updates. When sbopkg processed the queue it choked on a library (lib...) and I did not write the name for later, separate update. Is last Saturday's list available somewhere? I'd like to identify the package that wouldn't build here and figure out why not. TIA, Rich From didier at slint.fr Mon Mar 23 19:28:22 2020 From: didier at slint.fr (Didier Spaier) Date: Mon, 23 Mar 2020 20:28:22 +0100 Subject: [Slackbuilds-users] Last Saturday's updates In-Reply-To: References: Message-ID: Le 23/03/2020 ? 20:18, Rich Shepard a ?crit : > Is last Saturday's list available somewhere? I'd like to identify the > package that wouldn't build here and figure out why not. http://slackbuilds.org/ChangeLog.txt Didier From matteo.bernardini at gmail.com Mon Mar 23 19:30:02 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Mon, 23 Mar 2020 20:30:02 +0100 Subject: [Slackbuilds-users] Last Saturday's updates In-Reply-To: References: Message-ID: Il giorno lun 23 mar 2020 alle ore 20:18 Rich Shepard ha scritto: > Is last Saturday's list available somewhere? I'd like to identify the > package that wouldn't build here and figure out why not. https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-March/024179.html From rshepard at appl-ecosys.com Mon Mar 23 19:32:14 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Mar 2020 12:32:14 -0700 (PDT) Subject: [Slackbuilds-users] Last Saturday's updates In-Reply-To: References: Message-ID: On Mon, 23 Mar 2020, Matteo Bernardini wrote: > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-March/024179.html Thanks, Matteo. I'll keep this available so I know where messages are archived. Regards, Rich From rshepard at appl-ecosys.com Mon Mar 23 19:34:32 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Mar 2020 12:34:32 -0700 (PDT) Subject: [Slackbuilds-users] Last Saturday's updates In-Reply-To: References: Message-ID: On Mon, 23 Mar 2020, Didier Spaier wrote: > http://slackbuilds.org/ChangeLog.txt Didier, Thanks very much. Regards, Rich From lists at osh.id.au Mon Mar 23 19:40:17 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Mon, 23 Mar 2020 12:40:17 -0700 Subject: [Slackbuilds-users] Last Saturday's updates In-Reply-To: References: Message-ID: <9675895f-d5e9-45de-ac82-203f2bcb25c5@www.fastmail.com> Another option is to follow the RSS feed: https://slackbuilds.org/rss/ChangeLog.rss -- Dave From kev4321 at fastmail.fm Mon Mar 23 20:29:27 2020 From: kev4321 at fastmail.fm (Kevin McCormick) Date: Mon, 23 Mar 2020 15:29:27 -0500 Subject: [Slackbuilds-users] zoom-linux crash In-Reply-To: References: <9357b8ff-b6a9-23ba-3ee8-9ccacde29453@fastmail.fm> <96d1796e-b590-9d68-74d9-bf981d21b5d4@fastmail.fm> <5c957f7a-03ef-be69-eb87-bbe6e359c7a5@fastmail.fm> <86309700-01b7-6942-a8d7-1cd672d5be67@fastmail.fm> Message-ID: <7b7f9445-0588-ff57-af03-6e4e9ce8422a@fastmail.fm> Yes, I use nvidia 440.59 on my desktop and zoom-linux works fine.? I think the problem is really a complicated issue with the dual graphics devices on the T440p laptop.? I found out there is a bumblebee project and other attempts at solving the problem, but since the intel graphics seems to be OK, I just gave up. On 3/23/20 1:30 PM, Willy Sudiarto Raharjo wrote: >> For the curious, I have resolved the situation for now by removing the >> nvidia drivers and also blacklisting nouveau.? This leaves only the >> intel i915 driver using the integrated intel graphics (HD4600).? So the >> nvidia GT 730M is unused.? This notebook uses Optimus technology, >> meaning the nvidia card cannot be used independently of the intel >> integrated GPU.? I am hoping that using only the intel GPU will give >> acceptable screen quality.? For this Thinkpad T440p, the nvidia-driver >> should probably be? nvidia-legacy390, built with GLVND="no" and also use >> the "pass-through" xorg settings from? >> http://us.download.nvidia.com/XFree86/Linux-x86_64/390.132/README/randr14.html.? >> I think my issues were caused by the nvidia OpenGL replacement libraries >> not working with Qt5. > Hi, > > i tried to run zoom on my desktop with NVidia Driver 390.132 (from > NVidia directly, not from SBo) and it worked fine here. > > PS: I'm using -current, to clarify things. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Mon Mar 23 21:09:14 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Mar 2020 14:09:14 -0700 (PDT) Subject: [Slackbuilds-users] libinput-1.15.4 build fails: no pkg_resources Message-ID: I'm running Slackware-14.2/x86_64 and Python3-3.8.2 with current versions of libinput requirements and libinput-1.15.3. When I try to build -1.15.4 the process fails here: Traceback (most recent call last): File "/usr/bin/meson", line 6, in from pkg_resources import load_entry_point ModuleNotFoundError: No module named 'pkg_resources' Sure enough, I cannot import pkg_resources in Python3. A StackOverflow thread taught me that pkg_resources is distributed with setuptools; I have three of 'em here: python-setuptools-22.0.5-x86_64-1[1], setuptools-git-1.1-x86_64-1_SBo, and setuptools-scm-3.3.3-x86_64-1_SBo. An answer to the SO question says that: "July 2018 Update "Most people should now use pip install setuptools (possibly with sudo). "Some may need to (re)install the python-setuptools package via their package manager (apt-get install, yum install, etc.). "This issue can be highly dependent on your OS and dev environment. See the legacy/other answers below if the above isn't working for you. "Explanation "This error message is caused by a missing/broken Python setuptools package. Per Matt M.'s comment and setuptools issue #581, the bootstrap script referred to below is no longer the recommended installation method. "The bootstrap script instructions will remain below, in case it's still helpful to anyone." Advice needed, Rich [1] SBo has python3-setuptools_autover, but not a separate python3-setuptools. From didier at slint.fr Mon Mar 23 21:44:14 2020 From: didier at slint.fr (Didier Spaier) Date: Mon, 23 Mar 2020 22:44:14 +0100 Subject: [Slackbuilds-users] libinput-1.15.4 build fails: no pkg_resources In-Reply-To: References: Message-ID: Le 23/03/2020 ? 22:09, Rich Shepard a ?crit?: > I'm running Slackware-14.2/x86_64 and Python3-3.8.2 with current versions of > libinput requirements and libinput-1.15.3. When I try to build -1.15.4 the > process fails here: > > Traceback (most recent call last): > ? File "/usr/bin/meson", line 6, in > ??? from pkg_resources import load_entry_point > ModuleNotFoundError: No module named 'pkg_resources' > > Sure enough, I cannot import pkg_resources in Python3. > > A StackOverflow thread taught me that pkg_resources is distributed with > setuptools; I have three of 'em here: python-setuptools-22.0.5-x86_64-1[1], > setuptools-git-1.1-x86_64-1_SBo, and setuptools-scm-3.3.3-x86_64-1_SBo. An > answer to the SO question says that: > > "July 2018 Update > > "Most people should now use pip install setuptools (possibly with sudo). > > "Some may need to (re)install the python-setuptools package via their > package manager (apt-get install, yum install, etc.). > > "This issue can be highly dependent on your OS and dev environment. See the > legacy/other answers below if the above isn't working for you. > > "Explanation > > "This error message is caused by a missing/broken Python setuptools package. > Per Matt M.'s comment and setuptools issue #581, the bootstrap script > referred to below is no longer the recommended installation method. > > "The bootstrap script instructions will remain below, in case it's still helpful to > anyone." > > Advice needed, > > Rich > > [1] SBo has python3-setuptools_autover, but not a separate > python3-setuptools. python-setup-tools is not needed to build libinput according to: sqg -p libinput. The queue file is: six pyudev python-evdev graphviz ninja python3 meson libwacom libinput Additionally python in SBo is @ version 3.7.2, not 3.8 and upgrading a needed package in a build chain is a hit or miss endeavor. As long as you use software shipped neither in Slacwkare 14.2 nor in SBo at the version provided, as far as I am in concern you are on your own. Have a good day, Didier From rshepard at appl-ecosys.com Mon Mar 23 22:40:45 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Mar 2020 15:40:45 -0700 (PDT) Subject: [Slackbuilds-users] libinput-1.15.4 build fails: no pkg_resources In-Reply-To: References: Message-ID: On Mon, 23 Mar 2020, Didier Spaier wrote: > python-setup-tools is not needed to build libinput according to: > sqg -p libinput. The queue file is: > > six > pyudev > python-evdev > graphviz > ninja > python3 > meson > libwacom These are all in place and at current versions. > Additionally python in SBo is @ version 3.7.2, not 3.8 and upgrading a > needed package in a build chain is a hit or miss endeavor. Yes, I know that 3.7.2 is what's currently supported. > As long as you use software shipped neither in Slacwkare 14.2 nor in > SBo at the version provided, as far as I am in concern you are on your > own. Okay. Perhaps I'll build the chain from the current source since python-3.8.x is supported there. For now I don't know that I need an upgraded libinput so I'll focus on getting work done. Thanks, Didier, Rich From chris.willing at linux.com Mon Mar 23 23:00:45 2020 From: chris.willing at linux.com (Christoph Willing) Date: Tue, 24 Mar 2020 09:00:45 +1000 Subject: [Slackbuilds-users] libinput-1.15.4 build fails: no pkg_resources In-Reply-To: References: Message-ID: On 24/3/20 8:40 am, Rich Shepard wrote: > On Mon, 23 Mar 2020, Didier Spaier wrote: > >> python-setup-tools is not needed to build libinput according to: >> sqg -p libinput. The queue file is: >> >> six >> pyudev >> python-evdev >> graphviz >> ninja >> python3 >> meson >> libwacom > > These are all in place and at current versions. > >> Additionally python in SBo is @ version 3.7.2, not 3.8 and upgrading a >> needed package in a build chain is a hit or miss endeavor. > > Yes, I know that 3.7.2 is what's currently supported. > >> As long as you use software shipped neither in Slacwkare 14.2 nor in >> SBo at the version provided, as far as I am in concern you are on your >> own. > > Okay. Perhaps I'll build the chain from the current source since > python-3.8.x is supported there. Your problem will likely persist, or worsen, while trying to mix packages from 14.2 with those of -current. At some point, the pkg_resources module was moved from python3 into python-setuptools. It exists in python3-3.7.2 (the SBo supported version for 14.2) and imports without issue. However it doesn't exist anymore in python3-3.8.2 (the version supported in -current) because it was moved into python-setuptools. In each case (14.2 and -current) importing the pkg_resource module normally works because either python3 or python-setuptools contains the pkg_resources module. In your case it doesn't work because you're mixing 14.2's python-setuptools (no pkg_resources module) with -current's python3 (also no pkg_resources module). If you must have -current's python3-3.8.2 then you'll also need to update to -current's python-setuptools (45.2.0) to access the pkg_resources module. Who knows what else that change will break ... chris From didier at slint.fr Mon Mar 23 23:04:54 2020 From: didier at slint.fr (Didier Spaier) Date: Tue, 24 Mar 2020 00:04:54 +0100 Subject: [Slackbuilds-users] libinput-1.15.4 build fails: no pkg_resources In-Reply-To: References: Message-ID: Le 23/03/2020 ? 23:40, Rich Shepard a ?crit?: > Okay. Perhaps I'll build the chain from the current source since > python-3.8.x is supported there. For now I don't know that I need an > upgraded libinput so I'll focus on getting work done. If you build the chain from the current sources: 1. That could fail. 2. Even if that succeeds that could break other packages needing some of the software of this chain. My advice is to just remove python 3.8 and re-install 3.7.2 so that you will have a consistent system, as I doubt that you need 3.8 on Slackware 14.2 now. It is possible to have both versions installed and use 3.8 only on demand though, finding how is left to the reader as an exercise. Best regards, Didier From rshepard at appl-ecosys.com Mon Mar 23 23:31:10 2020 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Mon, 23 Mar 2020 16:31:10 -0700 (PDT) Subject: [Slackbuilds-users] libinput-1.15.4 build fails: no pkg_resources In-Reply-To: References: Message-ID: On Tue, 24 Mar 2020, Christoph Willing wrote: > In each case (14.2 and -current) importing the pkg_resource module > normally works because either python3 or python-setuptools contains the > pkg_resources module. In your case it doesn't work because you're mixing > 14.2's python-setuptools (no pkg_resources module) with -current's python3 > (also no pkg_resources module). If you must have -current's python3-3.8.2 > then you'll also need to update to -current's python-setuptools (45.2.0) > to access the pkg_resources module. Who knows what else that change will > break ... chris, Thanks for the insights. I'm writing an application that needs to run under the current Python3 version, that's why I upgrade to the latest. Since I've not had any issues with applications using libinput-1.15.3 (which is installed here) I'll forego upgrading that library. Regards, Rich From flinchx at protonmail.com Tue Mar 24 00:20:29 2020 From: flinchx at protonmail.com (flinchx) Date: Tue, 24 Mar 2020 00:20:29 +0000 Subject: [Slackbuilds-users] libinput-1.15.4 build fails: no pkg_resources In-Reply-To: References: Message-ID: You may want to consider pyenv for this. ??????? Original Message ??????? On Tuesday, March 24, 2020 1:31 AM, Rich Shepard wrote: > I'm writing an application that needs to run under > the current Python3 version, that's why I upgrade to the latest. From kingbeowulf at gmail.com Tue Mar 24 02:55:58 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 23 Mar 2020 19:55:58 -0700 Subject: [Slackbuilds-users] qemu-4.1.0 is final SBo 14.2 version Message-ID: Hello all, qemu-4.2.0 requires glib >= 2.48. Thus, qemu-4.1.0 is the final SBo version for Slackware-14.2. Also, for qemu-14.2, if you use '-display gtk' and have a nonfunctional monitor window, use '-display sdl' and invoke the monitor window with CTRL-ALT-2 (see docs). I haven't been able to isolate the qemu gtk3 issue and probably won't until we move to 15.0. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From alessandro.baggi at gmail.com Tue Mar 24 09:02:17 2020 From: alessandro.baggi at gmail.com (Alessandro Baggi) Date: Tue, 24 Mar 2020 10:02:17 +0100 Subject: [Slackbuilds-users] qemu-4.1.0 is final SBo 14.2 version In-Reply-To: References: Message-ID: Il 24/03/20 03:55, King Beowulf ha scritto: > Hello all, > > qemu-4.2.0 requires glib >= 2.48. Thus, qemu-4.1.0 is the final SBo > version for Slackware-14.2. > > Also, for qemu-14.2, if you use '-display gtk' and have a nonfunctional > monitor window, use '-display sdl' and invoke the monitor window with > CTRL-ALT-2 (see docs). I haven't been able to isolate the qemu gtk3 > issue and probably won't until we move to 15.0. > Then I hope that 15.0 will be released soon. Thank you for info. From kingbeowulf at gmail.com Wed Mar 25 05:32:12 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Tue, 24 Mar 2020 22:32:12 -0700 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted Message-ID: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Hello, everyone. I hope everyone is surviving the Viral Apocalypse in good health and spirits. I just posted updates to the Long Lived Branch nvidia-440.64 driver, compatible, hopefully, with both 14.2 and current. This will be my last 14.2 release, except for bug fixes, until 15.0. I will then release a cleaned up buildscript for 15.0. That update will be my last nvidia script. Thus, this script is now up for grabs. I've since moved on to AMD NAVI GPU and the full open source X.org/Mesa/kernel 5.4.x stack works plenty good enough for my needs and gaming addiction. The nvidia driver my second script for SBo many moons ago. It's a bit melancholy to let it go after all this time. Here's to another 10 years. -Ed -------------- 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 Wed Mar 25 14:38:02 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Wed, 25 Mar 2020 08:38:02 -0600 Subject: [Slackbuilds-users] Libvirt no building Message-ID: I just downloaded the latest libvirt files from Slackbuilds, and the build process gets aborted as follows: make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' Making all in tools make[2]: Entering directory '/tmp/SBo/libvirt-4.5.0/tools' GEN libvirt-guests.sh make all-am make[3]: Entering directory '/tmp/SBo/libvirt-4.5.0/tools' CC nss/nss_libnss_libvirt_impl_la-libvirt_nss.lo CCLD nss/libnss_libvirt_impl.la CCLD nss/libnss_libvirt.la CC nss/nss_libnss_libvirt_guest_impl_la-libvirt_nss.lo CCLD nss/libnss_libvirt_guest_impl.la CCLD nss/libnss_libvirt_guest.la CC libvirt_shell_la-vsh.lo CCLD libvirt_shell.la GEN wireshark/src/libvirt/protocol.h CC wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo wireshark/src/packet-libvirt.c:26:30: fatal error: wireshark/config.h: No such file or directory compilation terminated. Makefile:2803: recipe for target 'wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo' failed make[3]: *** [wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo] Error 1 make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/tools' Makefile:2393: recipe for target 'all' failed make[2]: *** [all] Error 2 make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/tools' Makefile:2107: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/libvirt-4.5.0' Makefile:2000: recipe for target 'all' failed make: *** [all] Error 2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Wed Mar 25 16:01:37 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 25 Mar 2020 17:01:37 +0100 Subject: [Slackbuilds-users] Libvirt no building In-Reply-To: References: Message-ID: Il giorno mer 25 mar 2020 alle ore 16:32 Luveh Keraph <1.41421 at gmail.com> ha scritto: > > I just downloaded the latest libvirt files from Slackbuilds, and the build process gets aborted as follows: > > make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > Making all in tools > make[2]: Entering directory '/tmp/SBo/libvirt-4.5.0/tools' > GEN libvirt-guests.sh > make all-am > make[3]: Entering directory '/tmp/SBo/libvirt-4.5.0/tools' > CC nss/nss_libnss_libvirt_impl_la-libvirt_nss.lo > CCLD nss/libnss_libvirt_impl.la > CCLD nss/libnss_libvirt.la > CC nss/nss_libnss_libvirt_guest_impl_la-libvirt_nss.lo > CCLD nss/libnss_libvirt_guest_impl.la > CCLD nss/libnss_libvirt_guest.la > CC libvirt_shell_la-vsh.lo > CCLD libvirt_shell.la > GEN wireshark/src/libvirt/protocol.h > CC wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo > wireshark/src/packet-libvirt.c:26:30: fatal error: wireshark/config.h: No such file or directory > compilation terminated. > Makefile:2803: recipe for target 'wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo' failed > make[3]: *** [wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo] Error 1 > make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/tools' > Makefile:2393: recipe for target 'all' failed > make[2]: *** [all] Error 2 > make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/tools' > Makefile:2107: recipe for target 'all-recursive' failed > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/libvirt-4.5.0' > Makefile:2000: recipe for target 'all' failed > make: *** [all] Error 2 as a workaround I think you can remove temporarily wireshark and try again to build libvirt. From kd5zex at gmail.com Wed Mar 25 17:24:15 2020 From: kd5zex at gmail.com (Alan Dingeldein) Date: Wed, 25 Mar 2020 12:24:15 -0500 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: >> Here's to another 10 years. Thanks for all your efforts Ed! --Alan -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenardrspencer at gmail.com Wed Mar 25 17:32:53 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Wed, 25 Mar 2020 13:32:53 -0400 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: If nobody else wants it I'll take it. On Wed, Mar 25, 2020, 01:32 King Beowulf wrote: > Hello, everyone. > > I hope everyone is surviving the Viral Apocalypse in good health and > spirits. > > I just posted updates to the Long Lived Branch nvidia-440.64 driver, > compatible, hopefully, with both 14.2 and current. This will be my last > 14.2 release, except for bug fixes, until 15.0. I will then release a > cleaned up buildscript for 15.0. That update will be my last nvidia > script. Thus, this script is now up for grabs. > > I've since moved on to AMD NAVI GPU and the full open source > X.org/Mesa/kernel 5.4.x stack works plenty good enough for my needs and > gaming addiction. > > The nvidia driver my second script for SBo many moons ago. It's a bit > melancholy to let it go after all this time. > > Here's to another 10 years. > -Ed > > > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From christopher.duston at protonmail.com Wed Mar 25 19:01:27 2020 From: christopher.duston at protonmail.com (Christopher L Duston) Date: Wed, 25 Mar 2020 19:01:27 +0000 Subject: [Slackbuilds-users] insync compiled against updated glibc? Message-ID: <0esnKQ8ZbPzYRupZxWQjzbq6LtWk_yfiCJA-aqLCdt8EpMU6mQmYXJjcO0EXO8EZfuJ5IvOiuVE7P4gxnL4wKZSuQ-0kex5IuW7ZZG8B0fM=@protonmail.com> Hello! Is it possible that the insync script (https://slackbuilds.org/repository/14.2/network/insync/) is being built against a newer version of glibc? I get $ insync [6063] Error loading Python lib '/usr/lib64/insync/libpython3.7m.so.1.0': dlopen: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib64/insync/libpython3.7m.so.1.0) After an apparently fine install. Both my Slack 14.2 machines have 2.23: bash-4.3$ ldd --version ldd (GNU libc) 2.23 What dumb thing am I missing? Thanks, Chris Sent with [ProtonMail](https://protonmail.com) Secure Email. -------------- next part -------------- An HTML attachment was scrubbed... URL: From didier at slint.fr Wed Mar 25 19:46:44 2020 From: didier at slint.fr (Didier Spaier) Date: Wed, 25 Mar 2020 20:46:44 +0100 Subject: [Slackbuilds-users] insync compiled against updated glibc? In-Reply-To: <0esnKQ8ZbPzYRupZxWQjzbq6LtWk_yfiCJA-aqLCdt8EpMU6mQmYXJjcO0EXO8EZfuJ5IvOiuVE7P4gxnL4wKZSuQ-0kex5IuW7ZZG8B0fM=@protonmail.com> References: <0esnKQ8ZbPzYRupZxWQjzbq6LtWk_yfiCJA-aqLCdt8EpMU6mQmYXJjcO0EXO8EZfuJ5IvOiuVE7P4gxnL4wKZSuQ-0kex5IuW7ZZG8B0fM=@protonmail.com> Message-ID: Hello, Le 25/03/2020 ? 20:01, Christopher L Duston via SlackBuilds-users a ?crit?: > Is it possible that the insync script (https://slackbuilds.org/repository/14.2/network/insync/) is being built against a newer version of glibc? I get > > $ insync > [6063] Error loading Python lib '/usr/lib64/insync/libpython3.7m.so.1.0': dlopen: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib64/insync/libpython3.7m.so.1.0) > > After an apparently fine install. Both my Slack 14.2 machines have 2.23: > > bash-4.3$ ldd --version > ldd (GNU libc) 2.23 > > What dumb thing am I missing? > > Thanks, > Chri I don't think that's possible to build against another version of glibc because this is a repackaging of an upstream binary. I have already posted about this issue, cf.: https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-February/024124.html Best regards, Didier From kingbeowulf at gmail.com Thu Mar 26 01:48:00 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Wed, 25 Mar 2020 18:48:00 -0700 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: On 3/25/20 10:32 AM, Lenard Spencer wrote: > If nobody else wants it I'll take it. > > > On Wed, Mar 25, 2020, 01:32 King Beowulf > wrote: > > Hello, everyone. > > I hope everyone is surviving the Viral Apocalypse in good health and > spirits. > > I just posted updates to the Long Lived Branch nvidia-440.64 driver, > compatible, hopefully, with both 14.2 and current. This will be my last > 14.2 release, except for bug fixes, until 15.0.? I will then release a > cleaned up buildscript for 15.0.? That update will be my last nvidia > script. Thus, this script is now up for grabs. > Thanks! I'll clean is up and do a final update when 15.0 comes out, and then it's yours. -Ed -------------- 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 Wed Mar 25 16:57:01 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Wed, 25 Mar 2020 10:57:01 -0600 Subject: [Slackbuilds-users] Libvirt no building In-Reply-To: References: Message-ID: That results in a different error: emu_driver.c:(.text+0x2d1ba): undefined reference to `virStorageFileDeinit' qemu_driver.c:(.text+0x2d219): undefined reference to `virGetLastErrorCode' qemu_driver.c:(.text+0x2d5a5): undefined reference to `virStorageFileCreate' qemu_driver.c:(.text+0x2d8dc): undefined reference to `virGetLastErrorCode' qemu_driver.c:(.text+0x2ddf1): undefined reference to `virStorageFileUnlink' qemu_driver.c:(.text+0x2df09): undefined reference to `virGetLastErrorCode' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainManagedSave': qemu_driver.c:(.text+0x2e4ba): undefined reference to `virDomainObjCheckActive' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainSaveFlags': qemu_driver.c:(.text+0x2e77c): undefined reference to `virDomainObjCheckActive' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainCoreDumpWithFormat': qemu_driver.c:(.text+0x2ef81): undefined reference to `virDomainObjCheckActive' qemu_driver.c:(.text+0x2f1a7): undefined reference to `virGetLastErrorCode' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuProcessEventHandler': qemu_driver.c:(.text+0x2ff07): undefined reference to `virDomainObjCheckActive' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainStorageCloseStat': qemu_driver.c:(.text+0x27cf): undefined reference to `virStorageFileDeinit' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_security.o): In function `qemuSecurityStartTPMEmulator': qemu_security.c:(.text+0x808): undefined reference to `virSecurityManagerSetTPMLabels' qemu_security.c:(.text+0x890): undefined reference to `virSecurityManagerRestoreTPMLabels' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_security.o): In function `qemuSecurityCleanupTPMEmulator': qemu_security.c:(.text+0x8b8): undefined reference to `virSecurityManagerRestoreTPMLabels' ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_tpm.o): In function `qemuExtTPMStart': qemu_tpm.c:(.text+0xac6): undefined reference to `virFileChownFiles' collect2: error: ld returned 1 exit status libtool: error: error: relink 'libvirt_driver_qemu.la' with the above command before installing it Makefile:6541: recipe for target 'install-modLTLIBRARIES' failed make[4]: *** [install-modLTLIBRARIES] Error 1 make[4]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' Makefile:12432: recipe for target 'install-am' failed make[3]: *** [install-am] Error 2 make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' Makefile:12426: recipe for target 'install' failed make[2]: *** [install] Error 2 make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' Makefile:2107: recipe for target 'install-recursive' failed make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/libvirt-4.5.0' Makefile:2415: recipe for target 'install-strip' failed make: *** [install-strip] Error 2 I do have the latest qemu installed, but I don't want to have to remove it for the sake of libvirt. On Wed, Mar 25, 2020 at 10:00 AM Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > Il giorno mer 25 mar 2020 alle ore 16:32 Luveh Keraph > <1.41421 at gmail.com> ha scritto: > > > > I just downloaded the latest libvirt files from Slackbuilds, and the > build process gets aborted as follows: > > > > make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > > make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > > Making all in tools > > make[2]: Entering directory '/tmp/SBo/libvirt-4.5.0/tools' > > GEN libvirt-guests.sh > > make all-am > > make[3]: Entering directory '/tmp/SBo/libvirt-4.5.0/tools' > > CC nss/nss_libnss_libvirt_impl_la-libvirt_nss.lo > > CCLD nss/libnss_libvirt_impl.la > > CCLD nss/libnss_libvirt.la > > CC nss/nss_libnss_libvirt_guest_impl_la-libvirt_nss.lo > > CCLD nss/libnss_libvirt_guest_impl.la > > CCLD nss/libnss_libvirt_guest.la > > CC libvirt_shell_la-vsh.lo > > CCLD libvirt_shell.la > > GEN wireshark/src/libvirt/protocol.h > > CC wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo > > wireshark/src/packet-libvirt.c:26:30: fatal error: wireshark/config.h: > No such file or directory > > compilation terminated. > > Makefile:2803: recipe for target > 'wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo' failed > > make[3]: *** [wireshark/src/wireshark_src_libvirt_la-packet-libvirt.lo] > Error 1 > > make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/tools' > > Makefile:2393: recipe for target 'all' failed > > make[2]: *** [all] Error 2 > > make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/tools' > > Makefile:2107: recipe for target 'all-recursive' failed > > make[1]: *** [all-recursive] Error 1 > > make[1]: Leaving directory '/tmp/SBo/libvirt-4.5.0' > > Makefile:2000: recipe for target 'all' failed > > make: *** [all] Error 2 > > as a workaround I think you can remove temporarily wireshark and try > again to build libvirt. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Fri Mar 27 07:17:38 2020 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Fri, 27 Mar 2020 08:17:38 +0100 Subject: [Slackbuilds-users] Libvirt no building In-Reply-To: References: Message-ID: Il giorno ven 27 mar 2020 alle ore 03:06 Luveh Keraph <1.41421 at gmail.com> ha scritto: > > That results in a different error: > > emu_driver.c:(.text+0x2d1ba): undefined reference to `virStorageFileDeinit' > qemu_driver.c:(.text+0x2d219): undefined reference to `virGetLastErrorCode' > qemu_driver.c:(.text+0x2d5a5): undefined reference to `virStorageFileCreate' > qemu_driver.c:(.text+0x2d8dc): undefined reference to `virGetLastErrorCode' > qemu_driver.c:(.text+0x2ddf1): undefined reference to `virStorageFileUnlink' > qemu_driver.c:(.text+0x2df09): undefined reference to `virGetLastErrorCode' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainManagedSave': > qemu_driver.c:(.text+0x2e4ba): undefined reference to `virDomainObjCheckActive' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainSaveFlags': > qemu_driver.c:(.text+0x2e77c): undefined reference to `virDomainObjCheckActive' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainCoreDumpWithFormat': > qemu_driver.c:(.text+0x2ef81): undefined reference to `virDomainObjCheckActive' > qemu_driver.c:(.text+0x2f1a7): undefined reference to `virGetLastErrorCode' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuProcessEventHandler': > qemu_driver.c:(.text+0x2ff07): undefined reference to `virDomainObjCheckActive' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): In function `qemuDomainStorageCloseStat': > qemu_driver.c:(.text+0x27cf): undefined reference to `virStorageFileDeinit' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_security.o): In function `qemuSecurityStartTPMEmulator': > qemu_security.c:(.text+0x808): undefined reference to `virSecurityManagerSetTPMLabels' > qemu_security.c:(.text+0x890): undefined reference to `virSecurityManagerRestoreTPMLabels' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_security.o): In function `qemuSecurityCleanupTPMEmulator': > qemu_security.c:(.text+0x8b8): undefined reference to `virSecurityManagerRestoreTPMLabels' > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_tpm.o): In function `qemuExtTPMStart': > qemu_tpm.c:(.text+0xac6): undefined reference to `virFileChownFiles' > collect2: error: ld returned 1 exit status > libtool: error: error: relink 'libvirt_driver_qemu.la' with the above command before installing it > Makefile:6541: recipe for target 'install-modLTLIBRARIES' failed > make[4]: *** [install-modLTLIBRARIES] Error 1 > make[4]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > Makefile:12432: recipe for target 'install-am' failed > make[3]: *** [install-am] Error 2 > make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > Makefile:12426: recipe for target 'install' failed > make[2]: *** [install] Error 2 > make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > Makefile:2107: recipe for target 'install-recursive' failed > make[1]: *** [install-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/libvirt-4.5.0' > Makefile:2415: recipe for target 'install-strip' failed > make: *** [install-strip] Error 2 > > I do have the latest qemu installed, but I don't want to have to remove it for the sake of libvirt. do you have, by any chance, another version of libvirt installed? try removing that before building the new one. From 1.41421 at gmail.com Fri Mar 27 13:41:02 2020 From: 1.41421 at gmail.com (Luveh Keraph) Date: Fri, 27 Mar 2020 07:41:02 -0600 Subject: [Slackbuilds-users] Libvirt no building In-Reply-To: References: Message-ID: Removing both the already-installed versions of libvirt and wireshark did the trick. Thanks. On Fri, Mar 27, 2020 at 1:16 AM Matteo Bernardini < matteo.bernardini at gmail.com> wrote: > Il giorno ven 27 mar 2020 alle ore 03:06 Luveh Keraph > <1.41421 at gmail.com> ha scritto: > > > > That results in a different error: > > > > emu_driver.c:(.text+0x2d1ba): undefined reference to > `virStorageFileDeinit' > > qemu_driver.c:(.text+0x2d219): undefined reference to > `virGetLastErrorCode' > > qemu_driver.c:(.text+0x2d5a5): undefined reference to > `virStorageFileCreate' > > qemu_driver.c:(.text+0x2d8dc): undefined reference to > `virGetLastErrorCode' > > qemu_driver.c:(.text+0x2ddf1): undefined reference to > `virStorageFileUnlink' > > qemu_driver.c:(.text+0x2df09): undefined reference to > `virGetLastErrorCode' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): > In function `qemuDomainManagedSave': > > qemu_driver.c:(.text+0x2e4ba): undefined reference to > `virDomainObjCheckActive' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): > In function `qemuDomainSaveFlags': > > qemu_driver.c:(.text+0x2e77c): undefined reference to > `virDomainObjCheckActive' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): > In function `qemuDomainCoreDumpWithFormat': > > qemu_driver.c:(.text+0x2ef81): undefined reference to > `virDomainObjCheckActive' > > qemu_driver.c:(.text+0x2f1a7): undefined reference to > `virGetLastErrorCode' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): > In function `qemuProcessEventHandler': > > qemu_driver.c:(.text+0x2ff07): undefined reference to > `virDomainObjCheckActive' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_driver.o): > In function `qemuDomainStorageCloseStat': > > qemu_driver.c:(.text+0x27cf): undefined reference to > `virStorageFileDeinit' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_security.o): > In function `qemuSecurityStartTPMEmulator': > > qemu_security.c:(.text+0x808): undefined reference to > `virSecurityManagerSetTPMLabels' > > qemu_security.c:(.text+0x890): undefined reference to > `virSecurityManagerRestoreTPMLabels' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_security.o): > In function `qemuSecurityCleanupTPMEmulator': > > qemu_security.c:(.text+0x8b8): undefined reference to > `virSecurityManagerRestoreTPMLabels' > > > ./.libs/libvirt_driver_qemu_impl.a(libvirt_driver_qemu_impl_la-qemu_tpm.o): > In function `qemuExtTPMStart': > > qemu_tpm.c:(.text+0xac6): undefined reference to `virFileChownFiles' > > collect2: error: ld returned 1 exit status > > libtool: error: error: relink 'libvirt_driver_qemu.la' with the above > command before installing it > > Makefile:6541: recipe for target 'install-modLTLIBRARIES' failed > > make[4]: *** [install-modLTLIBRARIES] Error 1 > > make[4]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > > Makefile:12432: recipe for target 'install-am' failed > > make[3]: *** [install-am] Error 2 > > make[3]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > > Makefile:12426: recipe for target 'install' failed > > make[2]: *** [install] Error 2 > > make[2]: Leaving directory '/tmp/SBo/libvirt-4.5.0/src' > > Makefile:2107: recipe for target 'install-recursive' failed > > make[1]: *** [install-recursive] Error 1 > > make[1]: Leaving directory '/tmp/SBo/libvirt-4.5.0' > > Makefile:2415: recipe for target 'install-strip' failed > > make: *** [install-strip] Error 2 > > > > I do have the latest qemu installed, but I don't want to have to remove > it for the sake of libvirt. > > do you have, by any chance, another version of libvirt installed? try > removing that before building the new one. > _______________________________________________ > 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 christopher.duston at protonmail.com Fri Mar 27 20:54:17 2020 From: christopher.duston at protonmail.com (Christopher L Duston) Date: Fri, 27 Mar 2020 20:54:17 +0000 Subject: [Slackbuilds-users] insync compiled against updated glibc? In-Reply-To: References: <0esnKQ8ZbPzYRupZxWQjzbq6LtWk_yfiCJA-aqLCdt8EpMU6mQmYXJjcO0EXO8EZfuJ5IvOiuVE7P4gxnL4wKZSuQ-0kex5IuW7ZZG8B0fM=@protonmail.com> Message-ID: To follow up here, it works if you use the Mint 18.x (xenial) from the Insync website (https://www.insynchq.com/downloads) and change the version/debname. If you don't hear from the maintainer, I can provide that update. Or whatever the procedure here is. Sent with ProtonMail Secure Email. ??????? Original Message ??????? On Wednesday, March 25, 2020 3:46 PM, Didier Spaier wrote: > Hello, > > Le 25/03/2020 ? 20:01, Christopher L Duston via SlackBuilds-users a ?crit?: > > > Is it possible that the insync script (https://slackbuilds.org/repository/14.2/network/insync/) is being built against a newer version of glibc? I get > > $ insync > > [6063] Error loading Python lib '/usr/lib64/insync/libpython3.7m.so.1.0': dlopen: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib64/insync/libpython3.7m.so.1.0) > > After an apparently fine install. Both my Slack 14.2 machines have 2.23: > > bash-4.3$ ldd --version > > ldd (GNU libc) 2.23 > > What dumb thing am I missing? > > Thanks, > > Chri > > I don't think that's possible to build against another version of glibc > because this is a repackaging of an upstream binary. > > I have already posted about this issue, cf.: > https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-February/024124.html > > Best regards, > Didier > > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From didier at slint.fr Fri Mar 27 22:06:23 2020 From: didier at slint.fr (Didier Spaier) Date: Fri, 27 Mar 2020 23:06:23 +0100 Subject: [Slackbuilds-users] insync compiled against updated glibc? In-Reply-To: References: <0esnKQ8ZbPzYRupZxWQjzbq6LtWk_yfiCJA-aqLCdt8EpMU6mQmYXJjcO0EXO8EZfuJ5IvOiuVE7P4gxnL4wKZSuQ-0kex5IuW7ZZG8B0fM=@protonmail.com> Message-ID: <3fccb345-a571-3f61-682b-52412e8368f6@slint.fr> Confirmed here, the greeting screen is displayed, thanks Christopher. Have a good day, Didier Le 27/03/2020 ? 21:54, Christopher L Duston via SlackBuilds-users a ?crit?: > To follow up here, it works if you use the Mint 18.x (xenial) from the Insync website (https://www.insynchq.com/downloads) and change the version/debname. > > If you don't hear from the maintainer, I can provide that update. Or whatever the procedure here is. > > > Sent with ProtonMail Secure Email. > > ??????? Original Message ??????? > On Wednesday, March 25, 2020 3:46 PM, Didier Spaier wrote: > >> Hello, >> >> Le 25/03/2020 ? 20:01, Christopher L Duston via SlackBuilds-users a ?crit?: >> >>> Is it possible that the insync script (https://slackbuilds.org/repository/14.2/network/insync/) is being built against a newer version of glibc? I get >>> $ insync >>> [6063] Error loading Python lib '/usr/lib64/insync/libpython3.7m.so.1.0': dlopen: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /usr/lib64/insync/libpython3.7m.so.1.0) >>> After an apparently fine install. Both my Slack 14.2 machines have 2.23: >>> bash-4.3$ ldd --version >>> ldd (GNU libc) 2.23 >>> What dumb thing am I missing? >>> Thanks, >>> Chri >> >> I don't think that's possible to build against another version of glibc >> because this is a repackaging of an upstream binary. >> >> I have already posted about this issue, cf.: >> https://lists.slackbuilds.org/pipermail/slackbuilds-users/2020-February/024124.html >> >> Best regards, >> 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 Sat Mar 28 06:37:52 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Mar 2020 13:37:52 +0700 Subject: [Slackbuilds-users] Updates - 20200328.1 Message-ID: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> Hi Just a tip for those who wants to orphaned a script, please make sure to keep the MAINTAINER and EMAIL field filled (use a non existent email is fine) For maintainers, please make sure to have the properly git hooks that checks the permissions. All scripts must have 644 instead of 755. Stay safe everyone Sat Mar 28 06:21:53 UTC 2020 desktop/Qogir-icon-theme: Added (A colorful design icon theme). desktop/neofetch: Updated for version 7.0.0. desktop/numix-icon-theme-circle: Updated for version 19.12.27. desktop/numix-icon-theme: Updated for version 20.03.20. development/composer: Updated for version 1.10.1 development/dart: Updated for version 2.7.2. development/eclipse-cpp: Updated for version 4.15. development/eclipse-java: Updated for version 4.15. development/eclipse-jee: Updated for version 4.15. development/fly: Updated for version 6.0.0. development/gede: Updated for version 2.15.4. development/hexinator: Updated for version 1.12. development/kotlin: Updated for version 1.3.71. development/lepton-eda: Updated for version 1.9.10. development/snappy: Updated for version 1.1.8. development/tea: Updated for version 50.0.4. development/universal-ctags: Updated for version 09b7cc5 development/velero: Added (Backup and migrate Kubernetes resources). development/vscode-bin: Updated for version 1.43.2. games/steam: Add desktop file gis/qgis: Updated for version 3.12.1. graphics/vuescan: Updated for version 9.7.26. libraries/libwacom: Updated for version 1.3. libraries/stfl: Support builds on current. libraries/t38modem-opal: Added (Open Phone Abstraction Library). libraries/t38modem-ptlib: Added (Portable Tools Library). libraries/tbb: Cleanup temp file. misc/ghostpcl: Updated for version 9.52. misc/par2cmdline-tbb: Updated for version 0.4_20150503. multimedia/plexmediaserver: Updated for v 1.18.9.2571_e106a8a91. network/asterisk: Updated for version 16.9.0. network/emailrelay: Updated HOMEPAGE. network/insync: Updated for version 3.1.0.40756. network/onedrive: Updated for version 2.4.0. network/opera-developer: Updated for version 69.0.3638.0. network/opera: Updated for version 67.0.3575.115. network/palemoon-bin: Updated for version 28.8.4. network/palemoon: Updated for version 28.8.4. network/speedtest-cli: Updated script. network/teamviewer: Updated for version 15.4.4445. network/tor-browser: Updated for version 9.0.7. network/zoom-linux: Updated for version 3.5.374815.0324. office/calibre-bin: Updated for version 4.13.0. perl/perl-Sidef: Updated for version 3.95. perl/perl-xml-libxml: Updated for version 2.0134. python/DVR-Scan: Added (Motion Events Detector). python/python3-aiohttp-socks: Updated for version 0.3.6. system/bat: Updated for version 0.13.0. system/duplicity: Updated for version 0.7.19. system/fd: Updated for version 7.5.0. system/fzf: Updated for version 0.21.0. system/nvidia-driver: Fix permission. system/nvidia-driver: fix scripts; updated for version 440.64 system/nvidia-kernel: updated for version 440.64 system/nvidia-legacy340-driver: corrected maintainer system/nvidia-legacy390-driver: unmaintained system/nvidia-legacy390-kernel: unmaintained system/ranger: Updated for version 1.9.3. system/ripgrep: Updated for version 12.0.0. system/slpkg: Updated for version 3.8.6. system/splix: Updated for version 2.0.0_76268c4. system/unison: Updated HOMEPAGE. system/wine: Updated for version 4.0.3. +--------------------------+ -- 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 lyonels at gmail.com Sat Mar 28 09:50:18 2020 From: lyonels at gmail.com (Lyonel S) Date: Sat, 28 Mar 2020 10:50:18 +0100 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: Hello Thank you very much for you hard work. I just noted a glitch in the last SBo update for nvidia-driver.info : md5sum are those of 440.64 but the filenames are still 440.59 (beware of a "59" in one of the md5sum strings, I got bitten by a brute replace ;-) I dig a little in the nvidia-installer options and I found we can use a switch on Current not to install GLVND libraries in the first place, instead of removing them after. The only library still installed/replaced is /usr/lib64/libOpenCL.so.1.0.0 found in the ocl-icd package. I encountered no problem, so I didn't try to move it around with the nvidia-switch script. Here is a diff file to make use of this option. Hope it helps I have a last dump question : did anyone try adding libglvnd to SBo for 14.2 ? At first glance it seems easier to do than tracking libraries to remove in nvidia-driver. Cheers and stay safe Lyonel Le jeu. 26 mars 2020 ? 02:48, King Beowulf a ?crit : > On 3/25/20 10:32 AM, Lenard Spencer wrote: > > If nobody else wants it I'll take it. > > > > > > On Wed, Mar 25, 2020, 01:32 King Beowulf > > wrote: > > > > Hello, everyone. > > > > I hope everyone is surviving the Viral Apocalypse in good health and > > spirits. > > > > I just posted updates to the Long Lived Branch nvidia-440.64 driver, > > compatible, hopefully, with both 14.2 and current. This will be my > last > > 14.2 release, except for bug fixes, until 15.0. I will then release > a > > cleaned up buildscript for 15.0. That update will be my last nvidia > > script. Thus, this script is now up for grabs. > > > > Thanks! I'll clean is up and do a final update when 15.0 comes out, and > then it's yours. > > -Ed > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: nvidia-driver-SBo-current.diff Type: text/x-patch Size: 1956 bytes Desc: not available URL: From willysr at slackbuilds.org Sat Mar 28 12:15:00 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Mar 2020 19:15:00 +0700 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: > I just noted a glitch in the last SBo update for nvidia-driver.info : > md5sum are those of 440.64 but the filenames are still 440.59 (beware of a > "59" in one of the md5sum strings, I got bitten by a brute replace ;-) Thanks for reporting It's fixed in my branch and i will update the links in our server as well, but the actual update will be in next public update. -- 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 Hedgehog87 at hotmail.it Sat Mar 28 15:30:05 2020 From: Hedgehog87 at hotmail.it (Cristiano Urban) Date: Sat, 28 Mar 2020 15:30:05 +0000 Subject: [Slackbuilds-users] obspy: switch to python3 Message-ID: Hi, after having uploaded the latest version of the python3-obspy slackbuild, I would like to inform you that I decided to drop obspy and basemap which will be replaced by python3-obspy and python3-basemap. So, I think that obspy and basemap can be removed in order to leave space to the corresponding python3 versions. Let me know if this choice can entail some issues. Best regards, Cristiano Urban. ___________________________________________ Site/blog @ https://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) -------------- next part -------------- An HTML attachment was scrubbed... URL: From lramos.prof at yahoo.com.br Sat Mar 28 15:35:32 2020 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sat, 28 Mar 2020 12:35:32 -0300 Subject: [Slackbuilds-users] Updates - 20200328.1 In-Reply-To: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> References: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> Message-ID: <20200328153532.GA21728@giustizia.org> Hello, I just had an issue here with snappy. The build wasn't successful: it stopped with a lot of errors when linking a unitttest. I could find a solution googling a little and so I'm offering a patch which hopefully may prevent this issue happening in other environments. Many thanks, and stay safe! Luiz Ramos lramos dot prof at yahoo dot com dot br >From 67e14aeffa26a59caaeb08a918ada15a5c563031 Mon Sep 17 00:00:00 2001 From: Luiz Ramos Date: Sat, 28 Mar 2020 12:19:57 -0300 Subject: [PATCH] development/snappy: fix build For an unknown reason, the build of development/snappy gave errors when linking the unittest. Googling a little, a fix was found (adding the variable ${GTEST_LIBRARIES} to the build statement in CMakeLists.txt; check https://github.com/google/snappy/pull/40 for details). The concept was implemented in the SlackBuild and the change fixed the problem. --- development/snappy/01-add-flag-to-linker.patch | 12 ++++++++++++ development/snappy/snappy.SlackBuild | 3 +++ 2 files changed, 15 insertions(+) create mode 100644 development/snappy/01-add-flag-to-linker.patch diff --git a/development/snappy/01-add-flag-to-linker.patch b/development/snappy/01-add-flag-to-linker.patch new file mode 100644 index 0000000000000000000000000000000000000000..c275e7672859b80a0ea16cf2fa8755e20cafb11a --- /dev/null +++ b/development/snappy/01-add-flag-to-linker.patch @@ -0,0 +1,12 @@ +diff -urpN a/CMakeLists.txt b/CMakeLists.txt +--- a/CMakeLists.txt 2020-03-28 12:11:45.488255295 -0300 ++++ b/CMakeLists.txt 2020-03-28 12:10:53.359253439 -0300 +@@ -212,7 +212,7 @@ if(SNAPPY_BUILD_TESTS) + "snappy-test.cc" + ) + target_compile_definitions(snappy_unittest PRIVATE -DHAVE_CONFIG_H) +- target_link_libraries(snappy_unittest snappy ${GFLAGS_LIBRARIES}) ++ target_link_libraries(snappy_unittest snappy ${GFLAGS_LIBRARIES} ${GTEST_LIBRARIES}) + + if(HAVE_LIBZ) + target_link_libraries(snappy_unittest z) diff --git a/development/snappy/snappy.SlackBuild b/development/snappy/snappy.SlackBuild index fcaa12847c14925ab440fb2ffc32db706db42d94..5ce0b6dd1bc9b7eea67b2cf58def8c6dab16ac93 100644 --- a/development/snappy/snappy.SlackBuild +++ b/development/snappy/snappy.SlackBuild @@ -52,6 +52,9 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; +# check: https://github.com/google/snappy/pull/40 +patch -p1 -i $CWD/01-add-flag-to-linker.patch + mkdir -p build cd build cmake \ -- 2.14.5 On Sat, Mar 28, 2020 at 01:37:52PM +0700, Willy Sudiarto Raharjo wrote: > Hi > > Just a tip for those who wants to orphaned a script, please make sure to > keep the MAINTAINER and EMAIL field filled (use a non existent email is > fine) > > For maintainers, please make sure to have the properly git hooks that > checks the permissions. All scripts must have 644 instead of 755. > > Stay safe everyone > > > Sat Mar 28 06:21:53 UTC 2020 > desktop/Qogir-icon-theme: Added (A colorful design icon theme). > desktop/neofetch: Updated for version 7.0.0. > desktop/numix-icon-theme-circle: Updated for version 19.12.27. > desktop/numix-icon-theme: Updated for version 20.03.20. > development/composer: Updated for version 1.10.1 > development/dart: Updated for version 2.7.2. > development/eclipse-cpp: Updated for version 4.15. > development/eclipse-java: Updated for version 4.15. > development/eclipse-jee: Updated for version 4.15. > development/fly: Updated for version 6.0.0. > development/gede: Updated for version 2.15.4. > development/hexinator: Updated for version 1.12. > development/kotlin: Updated for version 1.3.71. > development/lepton-eda: Updated for version 1.9.10. > development/snappy: Updated for version 1.1.8. > development/tea: Updated for version 50.0.4. > development/universal-ctags: Updated for version 09b7cc5 > development/velero: Added (Backup and migrate Kubernetes resources). > development/vscode-bin: Updated for version 1.43.2. > games/steam: Add desktop file > gis/qgis: Updated for version 3.12.1. > graphics/vuescan: Updated for version 9.7.26. > libraries/libwacom: Updated for version 1.3. > libraries/stfl: Support builds on current. > libraries/t38modem-opal: Added (Open Phone Abstraction Library). > libraries/t38modem-ptlib: Added (Portable Tools Library). > libraries/tbb: Cleanup temp file. > misc/ghostpcl: Updated for version 9.52. > misc/par2cmdline-tbb: Updated for version 0.4_20150503. > multimedia/plexmediaserver: Updated for v 1.18.9.2571_e106a8a91. > network/asterisk: Updated for version 16.9.0. > network/emailrelay: Updated HOMEPAGE. > network/insync: Updated for version 3.1.0.40756. > network/onedrive: Updated for version 2.4.0. > network/opera-developer: Updated for version 69.0.3638.0. > network/opera: Updated for version 67.0.3575.115. > network/palemoon-bin: Updated for version 28.8.4. > network/palemoon: Updated for version 28.8.4. > network/speedtest-cli: Updated script. > network/teamviewer: Updated for version 15.4.4445. > network/tor-browser: Updated for version 9.0.7. > network/zoom-linux: Updated for version 3.5.374815.0324. > office/calibre-bin: Updated for version 4.13.0. > perl/perl-Sidef: Updated for version 3.95. > perl/perl-xml-libxml: Updated for version 2.0134. > python/DVR-Scan: Added (Motion Events Detector). > python/python3-aiohttp-socks: Updated for version 0.3.6. > system/bat: Updated for version 0.13.0. > system/duplicity: Updated for version 0.7.19. > system/fd: Updated for version 7.5.0. > system/fzf: Updated for version 0.21.0. > system/nvidia-driver: Fix permission. > system/nvidia-driver: fix scripts; updated for version 440.64 > system/nvidia-kernel: updated for version 440.64 > system/nvidia-legacy340-driver: corrected maintainer > system/nvidia-legacy390-driver: unmaintained > system/nvidia-legacy390-kernel: unmaintained > system/ranger: Updated for version 1.9.3. > system/ripgrep: Updated for version 12.0.0. > system/slpkg: Updated for version 3.8.6. > system/splix: Updated for version 2.0.0_76268c4. > system/unison: Updated HOMEPAGE. > system/wine: Updated for version 4.0.3. > +--------------------------+ > > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From lramos.prof at yahoo.com.br Sat Mar 28 15:35:32 2020 From: lramos.prof at yahoo.com.br (Luiz Carlos Ramos) Date: Sat, 28 Mar 2020 12:35:32 -0300 Subject: [Slackbuilds-users] Updates - 20200328.1 In-Reply-To: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> References: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> Message-ID: <20200328153532.GA21728@giustizia.org> Hello, I just had an issue here with snappy. The build wasn't successful: it stopped with a lot of errors when linking a unitttest. I could find a solution googling a little and so I'm offering a patch which hopefully may prevent this issue happening in other environments. Many thanks, and stay safe! Luiz Ramos lramos dot prof at yahoo dot com dot br >From 67e14aeffa26a59caaeb08a918ada15a5c563031 Mon Sep 17 00:00:00 2001 From: Luiz Ramos Date: Sat, 28 Mar 2020 12:19:57 -0300 Subject: [PATCH] development/snappy: fix build For an unknown reason, the build of development/snappy gave errors when linking the unittest. Googling a little, a fix was found (adding the variable ${GTEST_LIBRARIES} to the build statement in CMakeLists.txt; check https://github.com/google/snappy/pull/40 for details). The concept was implemented in the SlackBuild and the change fixed the problem. --- development/snappy/01-add-flag-to-linker.patch | 12 ++++++++++++ development/snappy/snappy.SlackBuild | 3 +++ 2 files changed, 15 insertions(+) create mode 100644 development/snappy/01-add-flag-to-linker.patch diff --git a/development/snappy/01-add-flag-to-linker.patch b/development/snappy/01-add-flag-to-linker.patch new file mode 100644 index 0000000000000000000000000000000000000000..c275e7672859b80a0ea16cf2fa8755e20cafb11a --- /dev/null +++ b/development/snappy/01-add-flag-to-linker.patch @@ -0,0 +1,12 @@ +diff -urpN a/CMakeLists.txt b/CMakeLists.txt +--- a/CMakeLists.txt 2020-03-28 12:11:45.488255295 -0300 ++++ b/CMakeLists.txt 2020-03-28 12:10:53.359253439 -0300 +@@ -212,7 +212,7 @@ if(SNAPPY_BUILD_TESTS) + "snappy-test.cc" + ) + target_compile_definitions(snappy_unittest PRIVATE -DHAVE_CONFIG_H) +- target_link_libraries(snappy_unittest snappy ${GFLAGS_LIBRARIES}) ++ target_link_libraries(snappy_unittest snappy ${GFLAGS_LIBRARIES} ${GTEST_LIBRARIES}) + + if(HAVE_LIBZ) + target_link_libraries(snappy_unittest z) diff --git a/development/snappy/snappy.SlackBuild b/development/snappy/snappy.SlackBuild index fcaa12847c14925ab440fb2ffc32db706db42d94..5ce0b6dd1bc9b7eea67b2cf58def8c6dab16ac93 100644 --- a/development/snappy/snappy.SlackBuild +++ b/development/snappy/snappy.SlackBuild @@ -52,6 +52,9 @@ find -L . \ \( -perm 666 -o -perm 664 -o -perm 640 -o -perm 600 -o -perm 444 \ -o -perm 440 -o -perm 400 \) -exec chmod 644 {} \; +# check: https://github.com/google/snappy/pull/40 +patch -p1 -i $CWD/01-add-flag-to-linker.patch + mkdir -p build cd build cmake \ -- 2.14.5 On Sat, Mar 28, 2020 at 01:37:52PM +0700, Willy Sudiarto Raharjo wrote: > Hi > > Just a tip for those who wants to orphaned a script, please make sure to > keep the MAINTAINER and EMAIL field filled (use a non existent email is > fine) > > For maintainers, please make sure to have the properly git hooks that > checks the permissions. All scripts must have 644 instead of 755. > > Stay safe everyone > > > Sat Mar 28 06:21:53 UTC 2020 > desktop/Qogir-icon-theme: Added (A colorful design icon theme). > desktop/neofetch: Updated for version 7.0.0. > desktop/numix-icon-theme-circle: Updated for version 19.12.27. > desktop/numix-icon-theme: Updated for version 20.03.20. > development/composer: Updated for version 1.10.1 > development/dart: Updated for version 2.7.2. > development/eclipse-cpp: Updated for version 4.15. > development/eclipse-java: Updated for version 4.15. > development/eclipse-jee: Updated for version 4.15. > development/fly: Updated for version 6.0.0. > development/gede: Updated for version 2.15.4. > development/hexinator: Updated for version 1.12. > development/kotlin: Updated for version 1.3.71. > development/lepton-eda: Updated for version 1.9.10. > development/snappy: Updated for version 1.1.8. > development/tea: Updated for version 50.0.4. > development/universal-ctags: Updated for version 09b7cc5 > development/velero: Added (Backup and migrate Kubernetes resources). > development/vscode-bin: Updated for version 1.43.2. > games/steam: Add desktop file > gis/qgis: Updated for version 3.12.1. > graphics/vuescan: Updated for version 9.7.26. > libraries/libwacom: Updated for version 1.3. > libraries/stfl: Support builds on current. > libraries/t38modem-opal: Added (Open Phone Abstraction Library). > libraries/t38modem-ptlib: Added (Portable Tools Library). > libraries/tbb: Cleanup temp file. > misc/ghostpcl: Updated for version 9.52. > misc/par2cmdline-tbb: Updated for version 0.4_20150503. > multimedia/plexmediaserver: Updated for v 1.18.9.2571_e106a8a91. > network/asterisk: Updated for version 16.9.0. > network/emailrelay: Updated HOMEPAGE. > network/insync: Updated for version 3.1.0.40756. > network/onedrive: Updated for version 2.4.0. > network/opera-developer: Updated for version 69.0.3638.0. > network/opera: Updated for version 67.0.3575.115. > network/palemoon-bin: Updated for version 28.8.4. > network/palemoon: Updated for version 28.8.4. > network/speedtest-cli: Updated script. > network/teamviewer: Updated for version 15.4.4445. > network/tor-browser: Updated for version 9.0.7. > network/zoom-linux: Updated for version 3.5.374815.0324. > office/calibre-bin: Updated for version 4.13.0. > perl/perl-Sidef: Updated for version 3.95. > perl/perl-xml-libxml: Updated for version 2.0134. > python/DVR-Scan: Added (Motion Events Detector). > python/python3-aiohttp-socks: Updated for version 0.3.6. > system/bat: Updated for version 0.13.0. > system/duplicity: Updated for version 0.7.19. > system/fd: Updated for version 7.5.0. > system/fzf: Updated for version 0.21.0. > system/nvidia-driver: Fix permission. > system/nvidia-driver: fix scripts; updated for version 440.64 > system/nvidia-kernel: updated for version 440.64 > system/nvidia-legacy340-driver: corrected maintainer > system/nvidia-legacy390-driver: unmaintained > system/nvidia-legacy390-kernel: unmaintained > system/ranger: Updated for version 1.9.3. > system/ripgrep: Updated for version 12.0.0. > system/slpkg: Updated for version 3.8.6. > system/splix: Updated for version 2.0.0_76268c4. > system/unison: Updated HOMEPAGE. > system/wine: Updated for version 4.0.3. > +--------------------------+ > > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From willysr at slackbuilds.org Sat Mar 28 16:46:18 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 28 Mar 2020 23:46:18 +0700 Subject: [Slackbuilds-users] Updates - 20200328.1 In-Reply-To: <20200328153532.GA21728@giustizia.org> References: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> <20200328153532.GA21728@giustizia.org> Message-ID: <863bb949-d985-eb37-ff24-b6966f35a5da@slackbuilds.org> > I just had an issue here with snappy. The build wasn't successful: it > stopped with a lot of errors when linking a unitttest. > > I could find a solution googling a little and so I'm offering a patch > which hopefully may prevent this issue happening in other environments. I had an issue as well when testing this under -current, but when being tested under -stable, it works just fine -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From dave at slackbuilds.org Sat Mar 28 18:08:21 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 28 Mar 2020 18:08:21 +0000 Subject: [Slackbuilds-users] obspy: switch to python3 In-Reply-To: References: Message-ID: <20200328180821.GA3186@blackswan.r0t.uk> On 2020-03-28 15:30, Cristiano Urban put forth the proposition: > Hi, > after having uploaded the latest version of the python3-obspy slackbuild, I would like to inform you that I decided to drop obspy and basemap which will be replaced by python3-obspy and python3-basemap. So, I think that obspy and basemap can be removed in order to leave space to the corresponding python3 versions. > > Let me know if this choice can entail some issues. > > Best regards, > Cristiano Urban. Hi Cristiano, I can't see anything else that will be affected by removing those, so I'll remove them once the python3 versions are added. Cheers, -- Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From dave at slackbuilds.org Sat Mar 28 18:14:45 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 28 Mar 2020 18:14:45 +0000 Subject: [Slackbuilds-users] obspy: switch to python3 In-Reply-To: <20200328180821.GA3186@blackswan.r0t.uk> References: <20200328180821.GA3186@blackswan.r0t.uk> Message-ID: <20200328181445.GB3186@blackswan.r0t.uk> On 2020-03-28 18:08, Dave Woodfall put forth the proposition: > On 2020-03-28 15:30, > Cristiano Urban put forth the proposition: > > Hi, > > after having uploaded the latest version of the python3-obspy slackbuild, I would like to inform you that I decided to drop obspy and basemap which will be replaced by python3-obspy and python3-basemap. So, I think that obspy and basemap can be removed in order to leave space to the corresponding python3 versions. > > > > Let me know if this choice can entail some issues. > > > > Best regards, > > Cristiano Urban. > > Hi Cristiano, > > I can't see anything else that will be affected by removing those, so > I'll remove them once the python3 versions are added. I see the python3 versions are already in the repo, so I'll remove the others now. -- Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From hedgehog87 at hotmail.it Sat Mar 28 19:15:40 2020 From: hedgehog87 at hotmail.it (Cristiano Urban) Date: Sat, 28 Mar 2020 19:15:40 +0000 Subject: [Slackbuilds-users] R: obspy: switch to python3 In-Reply-To: <20200328181445.GB3186@blackswan.r0t.uk> References: <20200328180821.GA3186@blackswan.r0t.uk>, <20200328181445.GB3186@blackswan.r0t.uk> Message-ID: Yes, python3 versions were already present. Today I've uploaded an update for python3-obspy which is in the pending queue. Thank you for your time Dave! ___________________________________________ Site/blog @ https://crish4cks.net/ Registered user #488179 @ http://linuxcounter.net Slackware, because it works! =) ________________________________ Da: SlackBuilds-users per conto di Dave Woodfall Inviato: sabato 28 marzo 2020 19:14 A: slackbuilds-users at slackbuilds.org Oggetto: Re: [Slackbuilds-users] obspy: switch to python3 On 2020-03-28 18:08, Dave Woodfall put forth the proposition: > On 2020-03-28 15:30, > Cristiano Urban put forth the proposition: > > Hi, > > after having uploaded the latest version of the python3-obspy slackbuild, I would like to inform you that I decided to drop obspy and basemap which will be replaced by python3-obspy and python3-basemap. So, I think that obspy and basemap can be removed in order to leave space to the corresponding python3 versions. > > > > Let me know if this choice can entail some issues. > > > > Best regards, > > Cristiano Urban. > > Hi Cristiano, > > I can't see anything else that will be affected by removing those, so > I'll remove them once the python3 versions are added. I see the python3 versions are already in the repo, so I'll remove the others now. -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Sun Mar 29 02:48:14 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 28 Mar 2020 19:48:14 -0700 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: On 3/28/20 2:50 AM, Lyonel S wrote: > Hello > > Thank you very much for you hard work. > > I just noted a glitch in the last SBo update for nvidia-driver.info > : md5sum are those of 440.64 but the > filenames are still 440.59 (beware of a "59" in one of the md5sum > strings, I got bitten by a brute replace ;-) > Thanks, and to willy for the quick fix. Silly me...After all this decades you'd think I could master global search & replace. > I dig a little in the nvidia-installer options and I found we can use a > switch on Current not to install GLVND libraries in the first place, > instead of removing them after. > The only library still installed/replaced is > /usr/lib64/libOpenCL.so.1.0.0 found in the ocl-icd package. I encountered > no problem, so I didn't try to move > it around with the nvidia-switch script. > > Here is a diff file to make use of this option. > Hope it helps Unfortunately, that won't work as expected. in 15.0 we MUST use the GLVND libs. --no-install-libglvnd will install the non-GLVND nvidia libs (these are NOT the same as the GLVND versions), but the Slackware-current libglvnd will still be present with potential issues and unintended consequences and thus will need to be removed. To be clear: 1. Nvidia driver components come in 2 flavors: a. non-GLVND libs (legacy) b. GLVND libs + libglvnd (new hotness) 2. You can install either one but NOT both. 3. Slackware-current requires the nvidia GLVND versions 4. Nvidia deprecated non-GLVND libs and will remove them "soon" Hence the weirdness in the build script. (I won't even go down the library overlap rabbit hole.) When 15.0 hits RC1, I'll make the final 14.2 ONLY specific version, and then the 15.0 specific version. > > I have a last dump question : did anyone try adding libglvnd to SBo for > 14.2 ? > At first glance it seems easier to do than tracking libraries to remove > in nvidia-driver. > I thought about that but since 15.0 is "real soon now" and I'm switching to amdgpu, so ?\_(?)_/? -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From jdiamond at acadiau.ca Sun Mar 29 15:39:12 2020 From: jdiamond at acadiau.ca (Jim Diamond) Date: Sun, 29 Mar 2020 12:39:12 -0300 Subject: [Slackbuilds-users] Qt5 ... newer versions available In-Reply-To: <20191012020329.GE19897@blackholeuniverse.ru> References: <20191011204532.GA30117@jdiamond-mb.acadiau.ca> <20191012020329.GE19897@blackholeuniverse.ru> Message-ID: <20200329153912.GA14718@jdiamond-mb.acadiau.ca> On Sat, Oct 12, 2019 at 03:03 (+0100), Dave Woodfall wrote: > On Fri 11 Oct 2019 20:45, > Slackbuilds Users put forth the proposition: >> Hi all, > Hi >> SBO has Qt5 5.9.8, but 5.13.1 is now (since Sept 5) a going concern. >> Are there any plans to update? > 5.9.8 is the most supported LTS version at the moment. > It could be possible to update to the latest LTS, which is 5.12, but > it may mean the various dependencies to also be updated, and perhaps > older versions kept available for older applications. It would > require some testing to make sure that everything works with it. > I do still a SlackBuild for 5.12, so I'll have a look at it. Dave, have you had a chance to look at that? Thanks. Jim From dave at slackbuilds.org Sun Mar 29 23:51:20 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 30 Mar 2020 00:51:20 +0100 Subject: [Slackbuilds-users] Qt5 ... newer versions available In-Reply-To: <20200329153912.GA14718@jdiamond-mb.acadiau.ca> References: <20191011204532.GA30117@jdiamond-mb.acadiau.ca> <20191012020329.GE19897@blackholeuniverse.ru> <20200329153912.GA14718@jdiamond-mb.acadiau.ca> Message-ID: <20200329235120.GA14920@blackswan.r0t.uk> On 2020-03-29 12:39, Slackbuilds Users put forth the proposition: > On Sat, Oct 12, 2019 at 03:03 (+0100), Dave Woodfall wrote: > > > On Fri 11 Oct 2019 20:45, > > Slackbuilds Users put forth the proposition: > >> Hi all, > > > Hi > > >> SBO has Qt5 5.9.8, but 5.13.1 is now (since Sept 5) a going concern. > > >> Are there any plans to update? > > > 5.9.8 is the most supported LTS version at the moment. > > > It could be possible to update to the latest LTS, which is 5.12, but > > it may mean the various dependencies to also be updated, and perhaps > > older versions kept available for older applications. It would > > require some testing to make sure that everything works with it. > > > I do still a SlackBuild for 5.12, so I'll have a look at it. > > Dave, > > have you had a chance to look at that? Thanks. > > Jim Hi Jim I did a lot of testing with LTS 5.12.6, and then 5.12.7 was announced a little while ago, so I had to recheck everything again from scratch. I should have some updates soon. Most things that didn't build initially have now been fixed, apart from a few that will remain on 5.9 as -legacy. -- Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From bifferos at gmail.com Mon Mar 30 13:02:17 2020 From: bifferos at gmail.com (Biff Eros) Date: Mon, 30 Mar 2020 13:02:17 +0000 Subject: [Slackbuilds-users] uids/gids Message-ID: Hi All, Before I parse the contents of this file https://slackbuilds.org/uid_gid.txt, Can anyone tell me if there's a machine-readable version of that somewhere, it looks as though it might have been generated from something. thanks, Biff. From willysr at slackbuilds.org Mon Mar 30 14:07:59 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 30 Mar 2020 21:07:59 +0700 Subject: [Slackbuilds-users] uids/gids In-Reply-To: References: Message-ID: <30b09ce6-e46c-1ce9-3ca5-4578d548dfcc@slackbuilds.org> > Before I parse the contents of this file > https://slackbuilds.org/uid_gid.txt, Can anyone tell me if there's a > machine-readable version of that somewhere, it looks as though it > might have been generated from something. it's human-generated file :) -- 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 jdiamond at acadiau.ca Mon Mar 30 14:31:02 2020 From: jdiamond at acadiau.ca (Jim Diamond) Date: Mon, 30 Mar 2020 11:31:02 -0300 Subject: [Slackbuilds-users] Qt5 ... newer versions available In-Reply-To: <20200329235120.GA14920@blackswan.r0t.uk> References: <20191011204532.GA30117@jdiamond-mb.acadiau.ca> <20191012020329.GE19897@blackholeuniverse.ru> <20200329153912.GA14718@jdiamond-mb.acadiau.ca> <20200329235120.GA14920@blackswan.r0t.uk> Message-ID: <20200330143102.GB5283@jdiamond-mb.acadiau.ca> On Mon, Mar 30, 2020 at 00:51 (+0100), Dave Woodfall wrote: > On 2020-03-29 12:39, > Slackbuilds Users put forth the proposition: >> Dave, >> have you had a chance to look at that? Thanks. > Hi Jim > I did a lot of testing with LTS 5.12.6, and then 5.12.7 was announced a > little while ago, so I had to recheck everything again from scratch. > I should have some updates soon. > Most things that didn't build initially have now been fixed, apart > from a few that will remain on 5.9 as -legacy. Hi Dave, I just tried building 5.12.7 with a minimally modified Slackbuild, and it crashed when it tried to edit Qt5WebEngineCore.pc, which doesn't exist. I could play around, but if you have a working Slackbuild (and related files/patches/...), would you mind sharing it with me for additional testing? Thanks. Jim From dave at slackbuilds.org Mon Mar 30 15:45:09 2020 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 30 Mar 2020 16:45:09 +0100 Subject: [Slackbuilds-users] Qt5 ... newer versions available In-Reply-To: <20200330143102.GB5283@jdiamond-mb.acadiau.ca> References: <20191011204532.GA30117@jdiamond-mb.acadiau.ca> <20191012020329.GE19897@blackholeuniverse.ru> <20200329153912.GA14718@jdiamond-mb.acadiau.ca> <20200329235120.GA14920@blackswan.r0t.uk> <20200330143102.GB5283@jdiamond-mb.acadiau.ca> Message-ID: <20200330154509.GB14920@blackswan.r0t.uk> On 2020-03-30 11:31, Slackbuilds Users put forth the proposition: > On Mon, Mar 30, 2020 at 00:51 (+0100), Dave Woodfall wrote: > > > On 2020-03-29 12:39, > > Slackbuilds Users put forth the proposition: > >> Dave, > > >> have you had a chance to look at that? Thanks. > > > Hi Jim > > > I did a lot of testing with LTS 5.12.6, and then 5.12.7 was announced a > > little while ago, so I had to recheck everything again from scratch. > > I should have some updates soon. > > > Most things that didn't build initially have now been fixed, apart > > from a few that will remain on 5.9 as -legacy. > > Hi Dave, > > I just tried building 5.12.7 with a minimally modified Slackbuild, and > it crashed when it tried to edit Qt5WebEngineCore.pc, which doesn't exist. > > I could play around, but if you have a working Slackbuild (and related > files/patches/...), would you mind sharing it with me for additional > testing? > > Thanks. I have it in my user/dive/qt5-5.12 branch: https://git.slackbuilds.org/slackbuilds/log/?h=user/dive/qt5-5.12 There are also updates for (python3-)PyQt5 and python(2,3)-sip. -- Dave -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: not available URL: From lists at osh.id.au Mon Mar 30 18:37:22 2020 From: lists at osh.id.au (David O'Shaughnessy) Date: Mon, 30 Mar 2020 11:37:22 -0700 Subject: [Slackbuilds-users] Updates - 20200328.1 In-Reply-To: <863bb949-d985-eb37-ff24-b6966f35a5da@slackbuilds.org> References: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> <20200328153532.GA21728@giustizia.org> <863bb949-d985-eb37-ff24-b6966f35a5da@slackbuilds.org> Message-ID: On Sat, 28 Mar 2020, at 9:46 AM, Willy Sudiarto Raharjo wrote: > > I just had an issue here with snappy. The build wasn't successful: it > > stopped with a lot of errors when linking a unitttest. > > > > I could find a solution googling a little and so I'm offering a patch > > which hopefully may prevent this issue happening in other environments. > > I had an issue as well when testing this under -current, but when being > tested under -stable, it works just fine > I can't get it to build on -current or 14.2, both fail at the unit test. -- Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From mrvladislavovich at gmail.com Mon Mar 30 18:45:24 2020 From: mrvladislavovich at gmail.com (MyRequiem) Date: Mon, 30 Mar 2020 22:45:24 +0400 Subject: [Slackbuilds-users] Updates - 20200328.1 In-Reply-To: References: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> <20200328153532.GA21728@giustizia.org> <863bb949-d985-eb37-ff24-b6966f35a5da@slackbuilds.org> Message-ID: <20200330184524.GA27685@lenovo.myrequiem.net> Re: David O'Shaughnessy 30.03.2020 >On Sat, 28 Mar 2020, at 9:46 AM, Willy Sudiarto Raharjo wrote: > > > I just had an issue here with snappy. The build wasn't successful: it > > stopped with a lot of errors when linking a unitttest. > > > > I could find a solution googling a little and so I'm offering a patch > > which hopefully may prevent this issue happening in other environments. > > I had an issue as well when testing this under -current, but when being > tested under -stable, it works just fine > > > >I can't get it to build on -current or 14.2, both fail at the unit test. > >-- >Dave Hi, Willy :) I added -DSNAPPY_BUILD_TESTS=0 option and 'snappy' compiled without problems snappy.SlackBuild ----------------- cmake \ -DCMAKE_C_FLAGS="$SLKCFLAGS" \ -DCMAKE_CXX_FLAGS="$SLKCFLAGS" \ -DCMAKE_BUILD_TYPE="Release" \ -DCMAKE_INSTALL_PREFIX=/usr \ -DBUILD_SHARED_LIBS=ON \ -DSNAPPY_BUILD_TESTS=0 \ .. >_______________________________________________ >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 bifferos at gmail.com Mon Mar 30 22:04:20 2020 From: bifferos at gmail.com (Biff Eros) Date: Mon, 30 Mar 2020 22:04:20 +0000 Subject: [Slackbuilds-users] uids/gids In-Reply-To: <30b09ce6-e46c-1ce9-3ca5-4578d548dfcc@slackbuilds.org> References: <30b09ce6-e46c-1ce9-3ca5-4578d548dfcc@slackbuilds.org> Message-ID: On Mon, Mar 30, 2020 at 2:08 PM Willy Sudiarto Raharjo wrote: > > > Before I parse the contents of this file > > https://slackbuilds.org/uid_gid.txt, Can anyone tell me if there's a > > machine-readable version of that somewhere, it looks as though it > > might have been generated from something. > > it's human-generated file :) Thanks Willy! I converted it to .ini file format in the end: https://github.com/bifferos/afterpkg/blob/master/uid_gid.txt From yalhcru at gmail.com Mon Mar 30 21:47:21 2020 From: yalhcru at gmail.com (B Watson) Date: Mon, 30 Mar 2020 17:47:21 -0400 Subject: [Slackbuilds-users] uids/gids In-Reply-To: References: <30b09ce6-e46c-1ce9-3ca5-4578d548dfcc@slackbuilds.org> Message-ID: On 3/30/20, Biff Eros wrote: > Thanks Willy! I converted it to .ini file format in the end: > https://github.com/bifferos/afterpkg/blob/master/uid_gid.txt Out of curiosity... why do you need to parse uid_gid.txt? From kingbeowulf at gmail.com Mon Mar 30 22:01:18 2020 From: kingbeowulf at gmail.com (King Beowulf) Date: Mon, 30 Mar 2020 15:01:18 -0700 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: On 3/25/20 10:32 AM, Lenard Spencer wrote: > If nobody else wants it I'll take it. > > Approved. A bit earlier than had I planned, but it is definitely better to have a maintainer that can run the nvidia-driver on actual hardware. All hail the newly anointed nvidia high priest! -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From bifferos at gmail.com Mon Mar 30 22:52:53 2020 From: bifferos at gmail.com (Biff Eros) Date: Mon, 30 Mar 2020 22:52:53 +0000 Subject: [Slackbuilds-users] uids/gids In-Reply-To: References: <30b09ce6-e46c-1ce9-3ca5-4578d548dfcc@slackbuilds.org> Message-ID: On Mon, Mar 30, 2020 at 9:47 PM B Watson wrote: > > On 3/30/20, Biff Eros wrote: > > Thanks Willy! I converted it to .ini file format in the end: > > https://github.com/bifferos/afterpkg/blob/master/uid_gid.txt > > Out of curiosity... why do you need to parse uid_gid.txt? I started off manually creating user/group creation scripts for Afterpkg, looking a bit like this: https://github.com/bifferos/afterpkg/blob/master/scripts/system/mongodb/before.sh But then I realised it's much better to just auto-generate them, using that file as a starting point. It's going to save a lot of boiler-plate code. cheers, Biff. From jdiamond at acadiau.ca Mon Mar 30 23:44:47 2020 From: jdiamond at acadiau.ca (Jim Diamond) Date: Mon, 30 Mar 2020 20:44:47 -0300 Subject: [Slackbuilds-users] Qt5 ... newer versions available In-Reply-To: <20200330154509.GB14920@blackswan.r0t.uk> References: <20191011204532.GA30117@jdiamond-mb.acadiau.ca> <20191012020329.GE19897@blackholeuniverse.ru> <20200329153912.GA14718@jdiamond-mb.acadiau.ca> <20200329235120.GA14920@blackswan.r0t.uk> <20200330143102.GB5283@jdiamond-mb.acadiau.ca> <20200330154509.GB14920@blackswan.r0t.uk> Message-ID: <20200330234447.GA2250@jdiamond-mb.acadiau.ca> On Mon, Mar 30, 2020 at 16:45 (+0100), Dave Woodfall wrote: > On 2020-03-30 11:31, > Slackbuilds Users put forth the proposition: >> On Mon, Mar 30, 2020 at 00:51 (+0100), Dave Woodfall wrote: >>> On 2020-03-29 12:39, >>> Slackbuilds Users put forth the proposition: >>>> Dave, >>>> have you had a chance to look at that? Thanks. >>> Hi Jim >>> I did a lot of testing with LTS 5.12.6, and then 5.12.7 was announced a >>> little while ago, so I had to recheck everything again from scratch. >>> I should have some updates soon. >>> Most things that didn't build initially have now been fixed, apart >>> from a few that will remain on 5.9 as -legacy. >> Hi Dave, >> I just tried building 5.12.7 with a minimally modified Slackbuild, and >> it crashed when it tried to edit Qt5WebEngineCore.pc, which doesn't exist. >> I could play around, but if you have a working Slackbuild (and related >> files/patches/...), would you mind sharing it with me for additional >> testing? >> Thanks. > I have it in my user/dive/qt5-5.12 branch: > https://git.slackbuilds.org/slackbuilds/log/?h=user/dive/qt5-5.12 Thanks Dave, with your Slackbuild and related files it successfully built. I'll let you know if I see any issues. Cheers. Jim From willysr at slackbuilds.org Tue Mar 31 01:11:16 2020 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 31 Mar 2020 08:11:16 +0700 Subject: [Slackbuilds-users] Updates - 20200328.1 In-Reply-To: <20200330184524.GA27685@lenovo.myrequiem.net> References: <1f13d81a-d680-8297-08f3-76962e1cd3b6@slackbuilds.org> <20200328153532.GA21728@giustizia.org> <863bb949-d985-eb37-ff24-b6966f35a5da@slackbuilds.org> <20200330184524.GA27685@lenovo.myrequiem.net> Message-ID: > Hi, Willy :) > I added -DSNAPPY_BUILD_TESTS=0 option and 'snappy' compiled without problems I test it here on my VM and it worked fine snappy: MD5SUM check for snappy-1.1.8.tar.gz ... OK Building package snappy-1.1.8-x86_64-1_SBo.tgz ... OK -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From lenardrspencer at gmail.com Tue Mar 31 01:13:44 2020 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Mon, 30 Mar 2020 21:13:44 -0400 Subject: [Slackbuilds-users] nvidia-driver-440.64 submitted In-Reply-To: References: <4f6acc99-e3ba-5bc1-1a1b-0807b798a240@gmail.com> Message-ID: Thanks much! On Mon, Mar 30, 2020, 18:01 King Beowulf wrote: > On 3/25/20 10:32 AM, Lenard Spencer wrote: > > If nobody else wants it I'll take it. > > > > > > Approved. A bit earlier than had I planned, but it is definitely better > to have a maintainer that can run the nvidia-driver on actual hardware. > > All hail the newly anointed nvidia high priest! > > -Ed > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yalhcru at gmail.com Tue Mar 31 02:59:34 2020 From: yalhcru at gmail.com (B Watson) Date: Mon, 30 Mar 2020 22:59:34 -0400 Subject: [Slackbuilds-users] uids/gids In-Reply-To: References: <30b09ce6-e46c-1ce9-3ca5-4578d548dfcc@slackbuilds.org> Message-ID: On 3/30/20, Biff Eros wrote: > I started off manually creating user/group creation scripts for > Afterpkg, looking a bit like this: > https://github.com/bifferos/afterpkg/blob/master/scripts/system/mongodb/before.sh Interesting project... not sure I'd want to mix-and-match pip-installed and SBo-installed stuff, but if someone does want to, your script looks like it should handle it well. The before.sh you linked does something horrible though. Nobody should ever grep /etc/passwd and/or group to see if a user exists (what if they're using LDAP authentication? NIS? In 15.0 we're going to have PAM, what if they're using something we never even heard of before?) Instead use getent. Like so: ---cut-here--- #!/bin/bash # Create the mongo group if getent group mongo >/dev/null ; then echo "mongo group exists, no need to add it" else echo "Creating mongo group" groupadd -r -g 285 mongo fi # Create the mongo user if getent passwd mongo >/dev/null ; then echo "mongo user exists, no need to add it" else echo "Creating mongo user" useradd -u 285 -d /var/lib/mongodb -s /bin/false -g mongo mongo fi ---cut-here--- Notice it's a pretty minor change: only the two "if grep" lines are different. getent is is part of glibc, so it's guaranteed to be present on any Slack box that's able to compile anything. If you're generating the uid/gid creation scripts, I guess you only have to change it in one place (the generator script). From bifferos at gmail.com Tue Mar 31 07:51:58 2020 From: bifferos at gmail.com (Biff Eros) Date: Tue, 31 Mar 2020 08:51:58 +0100 Subject: [Slackbuilds-users] uids/gids In-Reply-To: References: <30b09ce6-e46c-1ce9-3ca5-4578d548dfcc@slackbuilds.org> Message-ID: I think there was some reason I couldn't rely on getent being present when I wrote that code, initially I was using it in the context of a minimal install but you are right, I will make that change, thanks for letting me know. On Tue, Mar 31, 2020, 3:59 AM B Watson wrote: > On 3/30/20, Biff Eros wrote: > > > I started off manually creating user/group creation scripts for > > Afterpkg, looking a bit like this: > > > https://github.com/bifferos/afterpkg/blob/master/scripts/system/mongodb/before.sh > > Interesting project... not sure I'd want to mix-and-match pip-installed > and SBo-installed stuff, but if someone does want to, your script looks > like it should handle it well. > > The before.sh you linked does something horrible though. Nobody should > ever grep /etc/passwd and/or group to see if a user exists (what if > they're using LDAP authentication? NIS? In 15.0 we're going to have PAM, > what if they're using something we never even heard of before?) > > Instead use getent. Like so: > > ---cut-here--- > #!/bin/bash > > # Create the mongo group > if getent group mongo >/dev/null ; then > echo "mongo group exists, no need to add it" > else > echo "Creating mongo group" > groupadd -r -g 285 mongo > fi > > # Create the mongo user > if getent passwd mongo >/dev/null ; then > echo "mongo user exists, no need to add it" > else > echo "Creating mongo user" > useradd -u 285 -d /var/lib/mongodb -s /bin/false -g mongo mongo > fi > ---cut-here--- > > Notice it's a pretty minor change: only the two "if grep" lines are > different. getent is is part of glibc, so it's guaranteed to be present > on any Slack box that's able to compile anything. > > If you're generating the uid/gid creation scripts, I guess you only have > to change it in one place (the generator script). > _______________________________________________ > 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 dchmelik at gmail.com Tue Mar 31 14:45:25 2020 From: dchmelik at gmail.com (David Chmelik) Date: Tue, 31 Mar 2020 07:45:25 -0700 Subject: [Slackbuilds-users] updates needed for dependencies I wrote scripts for? (mathics but others' builds now?) Message-ID: <4588910d-6120-782c-e8f8-c7b9c45d0faf@gmail.com> ??? Some years ago I wrote mathics.SlackBuild and some dependencies (depends on colorama, mpmath, ply, python-dateutil, python-django-legacy, six, sympy, but at this point I forgot which few I did, though I have them) and am aware some people use one or more dependencies I wrote for something else.? However, Mathics hasn't had normally-numbered (sequential-numbered) stable releases in years rather than abnormally-numbered (hash-numbered) development releases.? I am not building any of those releases.? If someone soon needs a newer version of some dependency I wrote the script for, it'll have to be forked.? Let me know if/when that needs to be done, which I suggest whoever needs that dependency, will (after letting me submit a so-called 'legacy' version) take it over when you need to update your build, so fork my dependency, update it for newer versions (and I'll keep the so-called 'legacy' version for Mathics.) ??? If they're going to have to be converted to Python 3, I'm not sure about that.? Basically I'd have to wait for a new normally-numbered Mathics release and see if that uses Python 3, or if it can be otherwise changed, otherwise the current Mathics will have to use what it has, or be dropped, whatever will work... will have to see what the SlackBuilds administrators say... From arcadellama at posteo.net Tue Mar 31 14:46:53 2020 From: arcadellama at posteo.net (arcadellama at posteo.net) Date: Tue, 31 Mar 2020 09:46:53 -0500 Subject: [Slackbuilds-users] help In-Reply-To: References: Message-ID: <9217930D-7259-44E2-95F6-7A6AE4CAAF7D@posteo.net> > On Mar 31, 2020, at 9:45 AM, slackbuilds-users-request at slackbuilds.org wrote: > > Send SlackBuilds-users mailing list submissions to > slackbuilds-users at slackbuilds.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > or, via email, send a message with subject or body 'help' to > slackbuilds-users-request at slackbuilds.org > > You can reach the person managing the list at > slackbuilds-users-owner at slackbuilds.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of SlackBuilds-users digest..." > > > Today's Topics: > > 1. Re: Updates - 20200328.1 (Willy Sudiarto Raharjo) > 2. Re: nvidia-driver-440.64 submitted (Lenard Spencer) > 3. Re: uids/gids (B Watson) > 4. Re: uids/gids (Biff Eros) > 5. updates needed for dependencies I wrote scripts for? (mathics > but others' builds now?) (David Chmelik) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 31 Mar 2020 08:11:16 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Updates - 20200328.1 > Message-ID: > Content-Type: text/plain; charset="utf-8" > >> Hi, Willy :) >> I added -DSNAPPY_BUILD_TESTS=0 option and 'snappy' compiled without problems > > I test it here on my VM and it worked fine > snappy: > MD5SUM check for snappy-1.1.8.tar.gz ... OK > Building package snappy-1.1.8-x86_64-1_SBo.tgz ... OK > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 195 bytes > Desc: OpenPGP digital signature > URL: > > ------------------------------ > > Message: 2 > Date: Mon, 30 Mar 2020 21:13:44 -0400 > From: Lenard Spencer > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] nvidia-driver-440.64 submitted > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > Thanks much! > > On Mon, Mar 30, 2020, 18:01 King Beowulf wrote: > >> On 3/25/20 10:32 AM, Lenard Spencer wrote: >>> If nobody else wants it I'll take it. >>> >>> >> >> Approved. A bit earlier than had I planned, but it is definitely better >> to have a maintainer that can run the nvidia-driver on actual hardware. >> >> All hail the newly anointed nvidia high priest! >> >> -Ed >> >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 3 > Date: Mon, 30 Mar 2020 22:59:34 -0400 > From: B Watson > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] uids/gids > Message-ID: > > Content-Type: text/plain; charset="UTF-8" > > On 3/30/20, Biff Eros wrote: > >> I started off manually creating user/group creation scripts for >> Afterpkg, looking a bit like this: >> https://github.com/bifferos/afterpkg/blob/master/scripts/system/mongodb/before.sh > > Interesting project... not sure I'd want to mix-and-match pip-installed > and SBo-installed stuff, but if someone does want to, your script looks > like it should handle it well. > > The before.sh you linked does something horrible though. Nobody should > ever grep /etc/passwd and/or group to see if a user exists (what if > they're using LDAP authentication? NIS? In 15.0 we're going to have PAM, > what if they're using something we never even heard of before?) > > Instead use getent. Like so: > > ---cut-here--- > #!/bin/bash > > # Create the mongo group > if getent group mongo >/dev/null ; then > echo "mongo group exists, no need to add it" > else > echo "Creating mongo group" > groupadd -r -g 285 mongo > fi > > # Create the mongo user > if getent passwd mongo >/dev/null ; then > echo "mongo user exists, no need to add it" > else > echo "Creating mongo user" > useradd -u 285 -d /var/lib/mongodb -s /bin/false -g mongo mongo > fi > ---cut-here--- > > Notice it's a pretty minor change: only the two "if grep" lines are > different. getent is is part of glibc, so it's guaranteed to be present > on any Slack box that's able to compile anything. > > If you're generating the uid/gid creation scripts, I guess you only have > to change it in one place (the generator script). > > > ------------------------------ > > Message: 4 > Date: Tue, 31 Mar 2020 08:51:58 +0100 > From: Biff Eros > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] uids/gids > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > I think there was some reason I couldn't rely on getent being present when > I wrote that code, initially I was using it in the context of a minimal > install but you are right, I will make that change, thanks for letting me > know. > > On Tue, Mar 31, 2020, 3:59 AM B Watson wrote: > >> On 3/30/20, Biff Eros wrote: >> >>> I started off manually creating user/group creation scripts for >>> Afterpkg, looking a bit like this: >>> >> https://github.com/bifferos/afterpkg/blob/master/scripts/system/mongodb/before.sh >> >> Interesting project... not sure I'd want to mix-and-match pip-installed >> and SBo-installed stuff, but if someone does want to, your script looks >> like it should handle it well. >> >> The before.sh you linked does something horrible though. Nobody should >> ever grep /etc/passwd and/or group to see if a user exists (what if >> they're using LDAP authentication? NIS? In 15.0 we're going to have PAM, >> what if they're using something we never even heard of before?) >> >> Instead use getent. Like so: >> >> ---cut-here--- >> #!/bin/bash >> >> # Create the mongo group >> if getent group mongo >/dev/null ; then >> echo "mongo group exists, no need to add it" >> else >> echo "Creating mongo group" >> groupadd -r -g 285 mongo >> fi >> >> # Create the mongo user >> if getent passwd mongo >/dev/null ; then >> echo "mongo user exists, no need to add it" >> else >> echo "Creating mongo user" >> useradd -u 285 -d /var/lib/mongodb -s /bin/false -g mongo mongo >> fi >> ---cut-here--- >> >> Notice it's a pretty minor change: only the two "if grep" lines are >> different. getent is is part of glibc, so it's guaranteed to be present >> on any Slack box that's able to compile anything. >> >> If you're generating the uid/gid creation scripts, I guess you only have >> to change it in one place (the generator script). >> _______________________________________________ >> 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: > > ------------------------------ > > Message: 5 > Date: Tue, 31 Mar 2020 07:45:25 -0700 > From: David Chmelik > To: SlackBuilds-users > Subject: [Slackbuilds-users] updates needed for dependencies I wrote > scripts for? (mathics but others' builds now?) > Message-ID: <4588910d-6120-782c-e8f8-c7b9c45d0faf at gmail.com> > Content-Type: text/plain; charset=utf-8; format=flowed > > ??? Some years ago I wrote mathics.SlackBuild and some dependencies > (depends on colorama, mpmath, ply, python-dateutil, > python-django-legacy, six, sympy, but at this point I forgot which few I > did, though I have them) and am aware some people use one or more > dependencies I wrote for something else.? However, Mathics hasn't had > normally-numbered (sequential-numbered) stable releases in years rather > than abnormally-numbered (hash-numbered) development releases.? I am not > building any of those releases.? If someone soon needs a newer version > of some dependency I wrote the script for, it'll have to be forked.? Let > me know if/when that needs to be done, which I suggest whoever needs > that dependency, will (after letting me submit a so-called 'legacy' > version) take it over when you need to update your build, so fork my > dependency, update it for newer versions (and I'll keep the so-called > 'legacy' version for Mathics.) > ??? If they're going to have to be converted to Python 3, I'm not sure > about that.? Basically I'd have to wait for a new normally-numbered > Mathics release and see if that uses Python 3, or if it can be otherwise > changed, otherwise the current Mathics will have to use what it has, or > be dropped, whatever will work... will have to see what the SlackBuilds > administrators say... > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > > ------------------------------ > > End of SlackBuilds-users Digest, Vol 167, Issue 20 > **************************************************