From duncan_roe at optusnet.com.au Fri Apr 2 00:36:03 2021 From: duncan_roe at optusnet.com.au (Duncan Roe) Date: Fri, 2 Apr 2021 11:36:03 +1100 Subject: [Slackbuilds-users] Test message - please ignore Message-ID: <20210402003603.GU5704@dimstar.local.net> Sent from dimstar - nothing special From willysr at slackbuilds.org Fri Apr 2 02:40:01 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 2 Apr 2021 09:40:01 +0700 Subject: [Slackbuilds-users] gtk-vnc failure after meson update In-Reply-To: <8668b0ac-4225-44f9-801d-3dbe963cebee@www.fastmail.com> References: <1e93754d-d87b-e274-3058-ff3371ec75a1@slackbuilds.org> <8668b0ac-4225-44f9-801d-3dbe963cebee@www.fastmail.com> Message-ID: >> development/meson: Version bump to 0.57.1 and update copyright year > > For me this version change results in failure of gtk-vnc building. > > Does anybody have such problem? Nope, works fine here with latest meson -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Apr 3 02:02:56 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Apr 2021 09:02:56 +0700 Subject: [Slackbuilds-users] Updates - 20210403.1 Message-ID: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Sat Apr 3 01:49:17 UTC 2021 academic/ds9: Updated for version 8.2.1. academic/rpy2: Updated for version 3.4.3. audio/tauonmb: Added (TauonMusicBox Player) desktop/kwalletcli: Updated for version 3.03. development/Sphinx: Updated for version 3.5.3. development/byacc: Updated for version 20210328. development/composer: Updated for version 2.0.11 development/d-tools: Updated for version 2.096.0 development/dmd: Updated for version 2.096.0 development/eclipse-platform: Updated for version 4.19. development/git-extras: Added (GIT Utilities). development/github-cli: Updated for version 1.8.0. development/hexnet: Added (network terminal). development/hopper: Updated for version 4.7.3. development/jdk16: Added (Java Platform SDK). development/jupyter-nbformat: Updated for version 5.1.2. development/jupyter_client: Updated for version 6.1.11. development/jupyter_core: Updated for version 4.7.1. development/komodo-edit: Updated for version 12.0.1. development/komodo-ide: Updated for version 12.0.1. development/kotlin: Updated for version 1.4.32. development/nodejs: Updated for version 12.20.1. development/pkgconf: Updated for version 1.7.4. development/postman: Updated for version 8.0.10. development/shc: Updated for version 4.0.3. development/sqlcl: Updated for version 20.4.2.35.2359. development/sqldeveloper: Updated for version 20.4.1.407.0006. development/universal-ctags: Updated for version af30512 development/vscode-bin: Updated for version 1.55.0. games/0ad: Update README. games/VASSAL: Updated for version 3.5.4. games/endgame-singularity: Added (Simulation) games/freeciv: updated for version 2.6.4 games/mgba: Updated for version 0.9.0 gis/OWSLib: Updated for version 0.23.0. gis/gdal: Updated for version 3.2.2. gis/geos: Updated for version 3.9.1. gis/gj2ascii: Update for Python 3. gis/osm2pgrouting: Updated for version 2.3.7. gis/pyproj: Updated for version 3.0.1. gis/python-pygeos: Updated for version 0.9. gis/qgis: Updated for version 3.18.1. gis/rasterio: Updated for version 1.2.1. graphics/Blender: Enable build with ffmpeg4 graphics/vuescan: Updated MD5SUMs. libraries/libfaketime: Updated for version 0.9.9. libraries/libgxps: Updated for version 0.3.2. libraries/libuv: Updated for version 1.41.0. misc/ghostpcl: Updated for version 9.54.0. network/bluejeans: Updated for version 2.21.3.2. network/brave-browser: Updated for version 1.22.70. network/davmail: Updated for version 5.5.1. network/ngrok: Added (Tunnel local servers). network/protonmail-bridge: Updated for version 1.6.9. network/protonmail-import-export-app: Updated for version 1.3.1. network/proxychains: Fix $DOWNLOAD, i486 -> i586. network/qutebrowser-tox: Updated for version 2.1.1. network/qutebrowser: Updated for version 2.1.1. network/rclone: 32 bit is unsupported now. network/syncthing: Updated for version 1.14.0. network/teams: Updated for version 1.4.00.7556 network/teamviewer: Updated for version 15.16.8. network/tightvnc: Fix script. network/tor-browser: Updated for version 10.0.15. network/vivaldi: Updated for version 3.7.2218.52. network/weechat: Updated for version 3.1. network/wire: Updated for version 3.24.2939. network/zoom-linux: Updated for version 5.6.13632.0328 office/etmtk: Updated for version 3.2.37. office/taskopen: Updated for version 1.1.5. office/zim: Updated for version 0.73.5. python/arrow: Updated for version 0.17.0. python/python3-astroid: Updated for version 2.5.2. python/python3-hsaudiotag3k: Added (hsaudiotag Python3 library) python/python3-ipython: Updated for version 7.22.0. python/python3-isounidecode: Added (ISOunidecode Python3 library) python/python3-plexapi: Added (PlexAPI Python3 library) python/python3-pulsectl: Added (Pulse-control Python3 library) python/python3-pylyrics: Added (PyLyrics Python3 library) python/python3-pypresence: Added (Pypresence Python3 library) python/python3-pysdl2: Added (PySDL2 Python3 library) python/python3-stagger: Added (Stagger Python3 library) python/python3-tekore: Added (Tekore Python3 library) python/tzlocal: Updated for version 2.1. system/Iosevka-slab: Updated for version 5.1.1. system/Iosevka: Updated for version 5.1.1. system/bat: Updated for version 0.18.0. system/dust: Updated for version 0.5.4. system/intel-microcode: Updated for version 20210216. system/kapacitor: Updated for version 1.5.9 system/netdata: Updated for version 1.30.0. system/prometheus: Updated for version 2.26.0. system/pspg: Updated for version 4.5.0. system/rar2fs: Updated for version 1.29.4 system/softhsm: Updated for version 2.6.1. system/vagrant: Updated for version 2.2.15. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sat Apr 3 02:16:26 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 2 Apr 2021 19:16:26 -0700 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: Whoops...just sent up mumble and murmur updates but I guess I was too slow! -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Apr 3 02:24:43 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 3 Apr 2021 09:24:43 +0700 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: > Whoops...just sent up mumble and murmur updates but I guess I was too slow! Hi Ed, can you rebase your branch against latest master branch? Thanks -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From 1.41421 at gmail.com Sat Apr 3 13:40:27 2021 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 3 Apr 2021 07:40:27 -0600 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: Several of the upgrades seem to be broken for me in 14.2-64: atop: cc -O2 -fPIC -c -o atop.o atop.c cc -O2 -fPIC -c -o version.o version.c cc -O2 -fPIC -c -o various.o various.c cc -O2 -fPIC -c -o deviate.o deviate.c cc -O2 -fPIC -c -o procdbase.o procdbase.c cc -O2 -fPIC -c -o acctproc.o acctproc.c cc -O2 -fPIC -c -o photoproc.o photoproc.c cc -O2 -fPIC -c -o photosyst.o photosyst.c cc -O2 -fPIC -c -o rawlog.o rawlog.c cc -O2 -fPIC -c -o ifprop.o ifprop.c ifprop.c: In function 'initifprop': ifprop.c:107:32: error: storage size of 'ethlink' isn't known struct ethtool_link_settings ethlink; // preferred! ^ ifprop.c:156:30: error: 'ETHTOOL_GLINKSETTINGS' undeclared (first use in this function) ethlink.cmd = ETHTOOL_GLINKSETTINGS; ^ ifprop.c:156:30: note: each undeclared identifier is reported only once for each function it appears in : recipe for target 'ifprop.o' failed make: *** [ifprop.o] Error 1 netdata: make[2]: Entering directory '/tmp/SBo/netdata-1.30.0/claim' if sed \ -e 's#[@]localstatedir_POST@#/var#g' \ -e 's#[@]sbindir_POST@#/usr/sbin#g' \ -e 's#[@]pluginsdir_POST@#/usr/libexec/netdata/plugins.d#g' \ -e 's#[@]configdir_POST@#/etc/netdata#g' \ -e 's#[@]libconfigdir_POST@#/usr/lib64/netdata/conf.d#g' \ -e 's#[@]pkglibexecdir_POST@#/usr/libexec/netdata#g' \ -e 's#[@]cachedir_POST@#/var/cache/netdata#g' \ -e 's#[@]registrydir_POST@#/var/lib/netdata/registry#g' \ -e 's#[@]varlibdir_POST@#/var/lib/netdata#g' \ -e 's#[@]webdir_POST@#/usr/share/netdata/web#g' \ -e 's#[@]enable_aclk_POST@#yes#g' \ -e 's#[@]enable_cloud_POST@#detect#g' \ netdata-claim.sh.in > netdata-claim.sh.tmp; then \ mv "netdata-claim.sh.tmp" "netdata-claim.sh"; \ else \ rm -f "netdata-claim.sh.tmp"; \ false; \ fi make[2]: Leaving directory '/tmp/SBo/netdata-1.30.0/claim' Making all in parser make[2]: Entering directory '/tmp/SBo/netdata-1.30.0/parser' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/tmp/SBo/netdata-1.30.0/parser' Making all in spawn make[2]: Entering directory '/tmp/SBo/netdata-1.30.0/spawn' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/tmp/SBo/netdata-1.30.0/spawn' Making all in mqtt_websockets make[2]: Entering directory '/tmp/SBo/netdata-1.30.0/mqtt_websockets' make[2]: *** No rule to make target 'all'. Stop. make[2]: Leaving directory '/tmp/SBo/netdata-1.30.0/mqtt_websockets' Makefile:5477: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/netdata-1.30.0' Makefile:2889: recipe for target 'all' failed make: *** [all] Error 2 teams: ./usr/share/teams/resources/tmp/teams_1.4.00.7556/usr/share/teams/resources/node_modules/azure-devops-node-api/ThirdPartyNotice.txt ./usr/share/teams/resources/tmp/teams_1.4.00.7556/usr/share/teams/resources/node_modules/typed-rest-client/ ./usr/share/teams/resources/tmp/teams_1.4.00.7556/usr/share/teams/resources/node_modules/typed-rest-client/ThirdPartyNotice.txt ./usr/share/teams/resources.pak ./usr/share/teams/snapshot_blob.bin ./usr/share/teams/swiftshader/ ./usr/share/teams/swiftshader/libEGL.so ./usr/share/teams/swiftshader/libGLESv2.so ./usr/share/teams/teams ./usr/share/teams/v8_context_snapshot.bin cat: /var/lib/sbopkg/SBo/14.2/network/teams/doinst.sh: No such file or directory Is it just me? On Fri, Apr 2, 2021 at 8:25 PM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > > Whoops...just sent up mumble and murmur updates but I guess I was too > slow! > > Hi Ed, > > can you rebase your branch against latest master branch? > > Thanks > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ml at mareichelt.com Sat Apr 3 14:03:13 2021 From: ml at mareichelt.com (Markus Reichelt) Date: Sat, 3 Apr 2021 16:03:13 +0200 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: <20210403140313.GA3566@pc21.mareichelt.com> * Luveh Keraph <1.41421 at gmail.com> wrote: > Several of the upgrades seem to be broken for me in 14.2-64: > > atop: I get the same error on 14.2-64, on -current the compile finishes. From artourter at gmail.com Sun Apr 4 00:28:52 2021 From: artourter at gmail.com (Greg' Ar Tourter) Date: Sun, 4 Apr 2021 01:28:52 +0100 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: <20210403140313.GA3566@pc21.mareichelt.com> References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> <20210403140313.GA3566@pc21.mareichelt.com> Message-ID: Hi, The latest Teams slackbuild fails due to the missing doinst.sh file. I am not sure it is supposed to be there but missing, or was removed on purpose but the slackbuild script is still expecting one. Cheers Greg -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Sun Apr 4 01:00:39 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 3 Apr 2021 18:00:39 -0700 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: On 4/2/21 7:24 PM, Willy Sudiarto Raharjo wrote: >> Whoops...just sent up mumble and murmur updates but I guess I was too slow! > > Hi Ed, > > can you rebase your branch against latest master branch? > > Thanks > I did last Saturday. I was a bit late pushing the updates Friday and so missed out getting the updates included in 20210403.1...unless there was and update not posted to the list after 20210327.1? -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From kingbeowulf at gmail.com Sun Apr 4 01:58:58 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 3 Apr 2021 18:58:58 -0700 Subject: [Slackbuilds-users] mumble and murmur 1.3.4 update notes Message-ID: Hello, Mumble and murmur 1.3.4 now requires protobuf3. This may cause an incompatibility for those who also need protobuf I was not able to test speech-dispatcher TTS integration. It "should" work, but I am unable to test in the qemu VM - no 14.2 running on hardware. I just upgraded my desktop soundcard (CL SB Z Core3D chip) which works great except pulseaudio gets confused. As a result, qemu VM may or may not have sound via the host. In preparation for current, there's a slightly different buildscript here: http://www.linuxgalaxy.org/files/sbo-testing/15.0/SBo-archives/ since speechdispatcher etc is now included included. Here too, TTS is not working in mumble, even through TTS works with others (spd-say, okular...); no idea why. It should work OOTB. I find TTS annoying but someone requested this years ago and it was working then. Buy default, I include the bundled celt. It doesn't hurt anything and allows for backward compatibility. It will be removed when upstream does so. Also for current: mumble uses SVG icons/pixmaps. These will not display due to a KDE Framework 5 bug in kiconthemes that you can fix here: https://www.linuxquestions.org/questions/slackware-14/mumble-1-3-4-missing-svg-icons-in-slackware64-current-15-0-a-4175692892/ -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sun Apr 4 08:18:45 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 4 Apr 2021 15:18:45 +0700 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: <760e5fe3-2f4b-e4b9-8e9b-6fd170a69b04@slackbuilds.org> > Several of the upgrades seem to be broken for me in 14.2-64: > > atop: > > cc -O2 -fPIC -c -o atop.o atop.c > cc -O2 -fPIC -c -o version.o version.c > cc -O2 -fPIC -c -o various.o various.c > cc -O2 -fPIC -c -o deviate.o deviate.c > cc -O2 -fPIC -c -o procdbase.o procdbase.c > cc -O2 -fPIC -c -o acctproc.o acctproc.c > cc -O2 -fPIC -c -o photoproc.o photoproc.c > cc -O2 -fPIC -c -o photosyst.o photosyst.c > cc -O2 -fPIC -c -o rawlog.o rawlog.c > cc -O2 -fPIC -c -o ifprop.o ifprop.c > ifprop.c: In function 'initifprop': > ifprop.c:107:32: error: storage size of 'ethlink' isn't known > struct ethtool_link_settings ethlink; // preferred! > ^ > ifprop.c:156:30: error: 'ETHTOOL_GLINKSETTINGS' undeclared (first use in > this function) > ethlink.cmd = ETHTOOL_GLINKSETTINGS; > ^ > ifprop.c:156:30: note: each undeclared identifier is reported only once for > each function it appears in > : recipe for target 'ifprop.o' failed > make: *** [ifprop.o] Error 1 Sorry, i tested on wrong VM The fix is now pushed to my branch https://git.slackbuilds.org/slackbuilds/commit/?id=b7147018a -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Sun Apr 4 15:51:17 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 4 Apr 2021 16:51:17 +0100 Subject: [Slackbuilds-users] chntpw doesn't compile on -current Message-ID: <142363e3-8f8a-42e8-5669-17c28eabc8cf@open-t.co.uk> Just a heads up that chntpw doesn't seem to compile any more against -current. I've updated today to -current and tried it using the 14.2 SBo scripts, and using the scripts from Ponce's GitHub repository. The error message is below. Looking at the age of the code, I wouldn't be surprised if it has become incompatible with current libraries somewhere - but this is only me guessing. cc -c -DUSEOPENSSL -g -I. -I/usr/include -Wall chntpw.c chntpw.c: In function ?str_to_key?: chntpw.c:145:22: error: ?des_cblock? undeclared (first use in this function); did you mean ?DES_cblock?? 145 | DES_set_odd_parity((des_cblock *)key); | ^~~~~~~~~~ | DES_cblock chntpw.c:145:22: note: each undeclared identifier is reported only once for each function it appears in chntpw.c:145:34: error: expected expression before ?)? token 145 | DES_set_odd_parity((des_cblock *)key); | ^ chntpw.c: In function ?E1?: chntpw.c:190:3: error: unknown type name ?des_key_schedule?; did you mean ?DES_key_schedule?? 190 | des_key_schedule ks; | ^~~~~~~~~~~~~~~~ | DES_key_schedule chntpw.c:191:3: error: unknown type name ?des_cblock?; did you mean ?DES_cblock?? 191 | des_cblock deskey; | ^~~~~~~~~~ | DES_cblock chntpw.c:193:16: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 193 | str_to_key(k,(uchar *)deskey); | ^ chntpw.c:197:3: warning: implicit declaration of function ?des_set_key?; did you mean ?DES_set_key?? [-Wimplicit-function-declaration] 197 | des_set_key((des_cblock *)deskey,ks); | ^~~~~~~~~~~ | DES_set_key chntpw.c:197:16: error: ?des_cblock? undeclared (first use in this function); did you mean ?DES_cblock?? 197 | des_set_key((des_cblock *)deskey,ks); | ^~~~~~~~~~ | DES_cblock chntpw.c:197:28: error: expected expression before ?)? token 197 | des_set_key((des_cblock *)deskey,ks); | ^ chntpw.c:199:3: warning: implicit declaration of function ?des_ecb_encrypt?; did you mean ?DES_ecb_encrypt?? [-Wimplicit-function-declaration] 199 | des_ecb_encrypt((des_cblock *)d,(des_cblock *)out, ks, DES_ENCRYPT); | ^~~~~~~~~~~~~~~ | DES_ecb_encrypt chntpw.c:199:32: error: expected expression before ?)? token 199 | des_ecb_encrypt((des_cblock *)d,(des_cblock *)out, ks, DES_ENCRYPT); | ^ chntpw.c:190:20: warning: unused variable ?ks? [-Wunused-variable] 190 | des_key_schedule ks; | ^~ chntpw.c: In function ?change_pw?: chntpw.c:507:4: error: unknown type name ?des_key_schedule?; did you mean ?DES_key_schedule?? 507 | des_key_schedule ks1, ks2; | ^~~~~~~~~~~~~~~~ | DES_key_schedule chntpw.c:508:4: error: unknown type name ?des_cblock?; did you mean ?DES_cblock?? 508 | des_cblock deskey1, deskey2; | ^~~~~~~~~~ | DES_cblock chntpw.c:625:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 625 | sid_to_key1(rid,(unsigned char *)deskey1); | ^ chntpw.c:626:17: error: ?des_cblock? undeclared (first use in this function); did you mean ?DES_cblock?? 626 | des_set_key((des_cblock *)deskey1,ks1); | ^~~~~~~~~~ | DES_cblock chntpw.c:626:29: error: expected expression before ?)? token 626 | des_set_key((des_cblock *)deskey1,ks1); | ^ chntpw.c:627:20: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast] 627 | sid_to_key2(rid,(unsigned char *)deskey2); | ^ chntpw.c:628:29: error: expected expression before ?)? token 628 | des_set_key((des_cblock *)deskey2,ks2); | ^ chntpw.c:631:33: error: expected expression before ?)? token 631 | des_ecb_encrypt((des_cblock *)(vp+ntpw_offs ), | ^ chntpw.c:632:19: error: expected expression before ?)? token 632 | (des_cblock *)md4, ks1, DES_DECRYPT); | ^ chntpw.c:633:33: error: expected expression before ?)? token 633 | des_ecb_encrypt((des_cblock *)(vp+ntpw_offs + 8), | ^ chntpw.c:634:19: error: expected expression before ?)? token 634 | (des_cblock *)&md4[8], ks2, DES_DECRYPT); | ^ chntpw.c:637:33: error: expected expression before ?)? token 637 | des_ecb_encrypt((des_cblock *)(vp+lmpw_offs), | ^ chntpw.c:638:19: error: expected expression before ?)? token 638 | (des_cblock *)lanman, ks1, DES_DECRYPT); | ^ chntpw.c:639:33: error: expected expression before ?)? token 639 | des_ecb_encrypt((des_cblock *)(vp+lmpw_offs + 8), | ^ chntpw.c:640:19: error: expected expression before ?)? token 640 | (des_cblock *)&lanman[8], ks2, DES_DECRYPT); | ^ chntpw.c:708:35: error: expected expression before ?)? token 708 | des_ecb_encrypt((des_cblock *)digest, | ^ chntpw.c:710:35: error: expected expression before ?)? token 710 | des_ecb_encrypt((des_cblock *)(digest+8), | ^ chntpw.c:711:21: error: expected expression before ?)? token 711 | (des_cblock *)&despw[8], ks2, DES_ENCRYPT); | ^ chntpw.c:713:35: error: expected expression before ?)? token 713 | des_ecb_encrypt((des_cblock *)lanman, | ^ chntpw.c:715:35: error: expected expression before ?)? token 715 | des_ecb_encrypt((des_cblock *)(lanman+8), | ^ chntpw.c:716:21: error: expected expression before ?)? token 716 | (des_cblock *)&newlandes[8], ks2, DES_ENCRYPT); | ^ chntpw.c:507:26: warning: unused variable ?ks2? [-Wunused-variable] 507 | des_key_schedule ks1, ks2; | ^~~ chntpw.c:507:21: warning: unused variable ?ks1? [-Wunused-variable] 507 | des_key_schedule ks1, ks2; | ^~~ make: *** [Makefile:51: chntpw.o] Error 1 Failures: chntpw: chntpw.SlackBuild return non-zero From s.arcus at open-t.co.uk Sun Apr 4 16:07:09 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 4 Apr 2021 17:07:09 +0100 Subject: [Slackbuilds-users] ptlib doesn't compile on -current any more Message-ID: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> Just upgraded today to -current and can't seem to get ptlib to compile any more. I've enclosed the error messages. I can't quite make sense of them - as it reads "no such file or directory" - and yet it doesn't mention any specific file or path - so not too sure what is going on. I checked the GibHub repo and there is no newer version of the scripts. I realise this is -current - and things will break - as expected - so I'm ok with that. But I thought I'd mention it here in case it is useful. This machine has been updated a number of times over the years, so it's not impossible it is my end causing it. If someone could confirm ptlib is still compiling on -current for them, that would be much appreciated. [AR] /tmp/SBo/ptlib-2.10.11/lib_linux_x86_64/libpt_s.a [LD] /tmp/SBo/ptlib-2.10.11/lib_linux_x86_64/libpt.so.#define g++: error: 2.#define: No such file or directory g++: error: 10-#define: No such file or directory g++: error: .#define: No such file or directory g++: error: 11: No such file or directory g++: error: 2.#define: No such file or directory g++: error: 10-#define: No such file or directory g++: error: .#define: No such file or directory g++: error: 11: No such file or directory make[2]: *** [/tmp/SBo/ptlib-2.10.11/make/lib.mak:111: /tmp/SBo/ptlib-2.10.11/lib_linux_x86_64/libpt.so.#define] Error 1 make[1]: *** [../make/common.mak:292: optshared] Error 2 make[2]: Leaving directory '/tmp/SBo/ptlib-2.10.11/src' make[1]: Leaving directory '/tmp/SBo/ptlib-2.10.11/src' make: *** [Makefile:91: optshared] Error 2 Failures: ptlib: ptlib.SlackBuild return non-zero From matteo.bernardini at gmail.com Sun Apr 4 17:43:08 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 4 Apr 2021 19:43:08 +0200 Subject: [Slackbuilds-users] ptlib doesn't compile on -current any more In-Reply-To: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> References: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> Message-ID: you need this additional patch https://build.opensuse.org/package/view_file/network:telephony/libpt2/libpt2-gnu-make-4.3.patch Matteo Il giorno dom 4 apr 2021 alle ore 18:07 Sebastian Arcus ha scritto: > > Just upgraded today to -current and can't seem to get ptlib to compile > any more. I've enclosed the error messages. I can't quite make sense of > them - as it reads "no such file or directory" - and yet it doesn't > mention any specific file or path - so not too sure what is going on. > > I checked the GibHub repo and there is no newer version of the scripts. > I realise this is -current - and things will break - as expected - so > I'm ok with that. But I thought I'd mention it here in case it is useful. > > This machine has been updated a number of times over the years, so it's > not impossible it is my end causing it. If someone could confirm ptlib > is still compiling on -current for them, that would be much appreciated. > > > > [AR] /tmp/SBo/ptlib-2.10.11/lib_linux_x86_64/libpt_s.a > [LD] /tmp/SBo/ptlib-2.10.11/lib_linux_x86_64/libpt.so.#define > g++: error: 2.#define: No such file or directory > g++: error: 10-#define: No such file or directory > g++: error: .#define: No such file or directory > g++: error: 11: No such file or directory > g++: error: 2.#define: No such file or directory > g++: error: 10-#define: No such file or directory > g++: error: .#define: No such file or directory > g++: error: 11: No such file or directory > make[2]: *** [/tmp/SBo/ptlib-2.10.11/make/lib.mak:111: > /tmp/SBo/ptlib-2.10.11/lib_linux_x86_64/libpt.so.#define] Error 1 > make[1]: *** [../make/common.mak:292: optshared] Error 2 > make[2]: Leaving directory '/tmp/SBo/ptlib-2.10.11/src' > make[1]: Leaving directory '/tmp/SBo/ptlib-2.10.11/src' > make: *** [Makefile:91: optshared] Error 2 > Failures: > ptlib: ptlib.SlackBuild return non-zero > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From s.arcus at open-t.co.uk Sun Apr 4 17:59:58 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 4 Apr 2021 18:59:58 +0100 Subject: [Slackbuilds-users] ptlib doesn't compile on -current any more In-Reply-To: References: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> Message-ID: <1d7710d5-cd34-c7e8-70d8-8415a905e5d9@open-t.co.uk> On 04/04/2021 18:43, Matteo Bernardini wrote: > you need this additional patch > > https://build.opensuse.org/package/view_file/network:telephony/libpt2/libpt2-gnu-make-4.3.patch > > Matteo > > Il giorno dom 4 apr 2021 alle ore 18:07 Sebastian Arcus Thank you for that. It now seems to fail with different errors (below). Does the order of the 3 patches in ptbli.SlackBuild matter? /usr/include/c++/10.2.0/bits/unique_ptr.h:57:28: note: declared here 57 | template class auto_ptr; | ^~~~~~~~ ptclib/pssl.cxx:143:35: error: ?BIO_s_file_internal? was not declared in this scope 143 | PSSL_BIO(BIO_METHOD *method = BIO_s_file_internal()) | ^~~~~~~~~~~~~~~~~~~ In file included from /usr/include/openssl/x509.h:18, from /usr/include/openssl/ssl.h:20, from ptclib/pssl.cxx:99: ptclib/pssl.cxx: In member function ?PBoolean PSSLPrivateKey::Create(unsigned int, void (*)(int, int, void*), void*)?: ptclib/pssl.cxx:255:83: warning: ?RSA* RSA_generate_key(int, long unsigned int, void (*)(int, int, void*), void*)? is deprecated [-Wdeprecated-declarations] 255 | if (EVP_PKEY_assign_RSA(key, RSA_generate_key(modulus, 0x10001, callback, cb_arg))) | ^ In file included from /usr/include/openssl/e_os2.h:13, from /usr/include/openssl/ssl.h:15, from ptclib/pssl.cxx:99: /usr/include/openssl/rsa.h:235:1: note: declared here 235 | DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned long e, void | ^~~~~~~~~~~~~~~~~~ ptclib/pssl.cxx: In constructor ?PSSLDiffieHellman::PSSLDiffieHellman(const BYTE*, PINDEX, const BYTE*, PINDEX)?: ptclib/pssl.cxx:630:5: error: invalid use of incomplete type ?struct dh_st? 630 | dh->p = BN_bin2bn(pData, pSize, NULL); From matteo.bernardini at gmail.com Sun Apr 4 18:21:49 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 4 Apr 2021 20:21:49 +0200 Subject: [Slackbuilds-users] ptlib doesn't compile on -current any more In-Reply-To: <1d7710d5-cd34-c7e8-70d8-8415a905e5d9@open-t.co.uk> References: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> <1d7710d5-cd34-c7e8-70d8-8415a905e5d9@open-t.co.uk> Message-ID: strange, builds fine here: I just add this last patch after the other ones already applied in the modified ptlib.SlackBuild of the unofficial repository for current. one of them is specific to port ptlib to openssl-1.1.x and from the output you posted could it be that is not applied? Matteo Il giorno dom 4 apr 2021 alle ore 20:00 Sebastian Arcus ha scritto: > > On 04/04/2021 18:43, Matteo Bernardini wrote: > > you need this additional patch > > > > > https://build.opensuse.org/package/view_file/network:telephony/libpt2/libpt2-gnu-make-4.3.patch > > > > Matteo > > > > Il giorno dom 4 apr 2021 alle ore 18:07 Sebastian Arcus > > > Thank you for that. It now seems to fail with different errors (below). > Does the order of the 3 patches in ptbli.SlackBuild matter? > > > > /usr/include/c++/10.2.0/bits/unique_ptr.h:57:28: note: declared here > 57 | template class auto_ptr; > | ^~~~~~~~ > ptclib/pssl.cxx:143:35: error: ?BIO_s_file_internal? was not declared in > this scope > 143 | PSSL_BIO(BIO_METHOD *method = BIO_s_file_internal()) > | ^~~~~~~~~~~~~~~~~~~ > In file included from /usr/include/openssl/x509.h:18, > from /usr/include/openssl/ssl.h:20, > from ptclib/pssl.cxx:99: > ptclib/pssl.cxx: In member function ?PBoolean > PSSLPrivateKey::Create(unsigned int, void (*)(int, int, void*), void*)?: > ptclib/pssl.cxx:255:83: warning: ?RSA* RSA_generate_key(int, long > unsigned int, void (*)(int, int, void*), void*)? is deprecated > [-Wdeprecated-declarations] > 255 | if (EVP_PKEY_assign_RSA(key, RSA_generate_key(modulus, > 0x10001, callback, cb_arg))) > | > ^ > In file included from /usr/include/openssl/e_os2.h:13, > from /usr/include/openssl/ssl.h:15, > from ptclib/pssl.cxx:99: > /usr/include/openssl/rsa.h:235:1: note: declared here > 235 | DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned > long e, void > | ^~~~~~~~~~~~~~~~~~ > ptclib/pssl.cxx: In constructor > ?PSSLDiffieHellman::PSSLDiffieHellman(const BYTE*, PINDEX, const BYTE*, > PINDEX)?: > ptclib/pssl.cxx:630:5: error: invalid use of incomplete type ?struct dh_st? > 630 | dh->p = BN_bin2bn(pData, pSize, NULL); > > > > > _______________________________________________ > 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 kingbeowulf at gmail.com Sun Apr 4 18:39:11 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 4 Apr 2021 11:39:11 -0700 Subject: [Slackbuilds-users] mumble and murmur 1.3.4 update notes In-Reply-To: References: Message-ID: On 4/3/21 6:58 PM, King Beowulf wrote: > In preparation for current, there's a slightly different buildscript > here: http://www.linuxgalaxy.org/files/sbo-testing/15.0/SBo-archives/ > since speechdispatcher etc is now included included. Here too, TTS is > not working in mumble, even through TTS works with others (spd-say, > okular...); no idea why. It should work OOTB. I find TTS annoying but > someone requested this years ago and it was working then. Well...never mind. It does work on current. D'OH! PEBKAC. Testing feedback on 14.2 would still be appreciated. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From s.arcus at open-t.co.uk Sun Apr 4 18:59:22 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 4 Apr 2021 19:59:22 +0100 Subject: [Slackbuilds-users] ptlib doesn't compile on -current any more In-Reply-To: References: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> <1d7710d5-cd34-c7e8-70d8-8415a905e5d9@open-t.co.uk> Message-ID: On 04/04/2021 19:21, Matteo Bernardini wrote: > strange, builds fine here: I just add this last patch after the other > ones already applied in the modified ptlib.SlackBuild of the > unofficial repository for current. > one of them is specific to port ptlib to openssl-1.1.x and from the > output you posted could it be that is not applied? Sorry - I was getting confused between willysr's and ponce's repos. I take it ponce's is the most up to date one? I re-downloaded the scripts from ponce's, added the patch you suggested and it all compiled fine now. Thank you again. > > Matteo > > Il giorno dom 4 apr 2021 alle ore 20:00 Sebastian Arcus > ha scritto: >> >> On 04/04/2021 18:43, Matteo Bernardini wrote: >> > you need this additional patch >> > >> > >> https://build.opensuse.org/package/view_file/network:telephony/libpt2/libpt2-gnu-make-4.3.patch >> > >> > Matteo >> > >> > Il giorno dom 4 apr 2021 alle ore 18:07 Sebastian Arcus >> >> >> Thank you for that. It now seems to fail with different errors (below). >> Does the order of the 3 patches in ptbli.SlackBuild matter? >> >> >> >> /usr/include/c++/10.2.0/bits/unique_ptr.h:57:28: note: declared here >> 57 | template class auto_ptr; >> | ^~~~~~~~ >> ptclib/pssl.cxx:143:35: error: ?BIO_s_file_internal? was not declared in >> this scope >> 143 | PSSL_BIO(BIO_METHOD *method = BIO_s_file_internal()) >> | ^~~~~~~~~~~~~~~~~~~ >> In file included from /usr/include/openssl/x509.h:18, >> from /usr/include/openssl/ssl.h:20, >> from ptclib/pssl.cxx:99: >> ptclib/pssl.cxx: In member function ?PBoolean >> PSSLPrivateKey::Create(unsigned int, void (*)(int, int, void*), void*)?: >> ptclib/pssl.cxx:255:83: warning: ?RSA* RSA_generate_key(int, long >> unsigned int, void (*)(int, int, void*), void*)? is deprecated >> [-Wdeprecated-declarations] >> 255 | if (EVP_PKEY_assign_RSA(key, RSA_generate_key(modulus, >> 0x10001, callback, cb_arg))) >> | >> ^ >> In file included from /usr/include/openssl/e_os2.h:13, >> from /usr/include/openssl/ssl.h:15, >> from ptclib/pssl.cxx:99: >> /usr/include/openssl/rsa.h:235:1: note: declared here >> 235 | DEPRECATEDIN_0_9_8(RSA *RSA_generate_key(int bits, unsigned >> long e, void >> | ^~~~~~~~~~~~~~~~~~ >> ptclib/pssl.cxx: In constructor >> ?PSSLDiffieHellman::PSSLDiffieHellman(const BYTE*, PINDEX, const BYTE*, >> PINDEX)?: >> ptclib/pssl.cxx:630:5: error: invalid use of incomplete type ?struct dh_st? >> 630 | dh->p = BN_bin2bn(pData, pSize, NULL); >> >> >> >> >> _______________________________________________ >> 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 jebrhansen+SBo at gmail.com Sun Apr 4 20:34:17 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 4 Apr 2021 14:34:17 -0600 Subject: [Slackbuilds-users] ptlib doesn't compile on -current any more In-Reply-To: References: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> <1d7710d5-cd34-c7e8-70d8-8415a905e5d9@open-t.co.uk> Message-ID: On Sun, Apr 4, 2021, 12:59 PM Sebastian Arcus wrote: > On 04/04/2021 19:21, Matteo Bernardini wrote: > > strange, builds fine here: I just add this last patch after the other > > ones already applied in the modified ptlib.SlackBuild of the > > unofficial repository for current. > > one of them is specific to port ptlib to openssl-1.1.x and from the > > output you posted could it be that is not applied? > > Sorry - I was getting confused between willysr's and ponce's repos. I > take it ponce's is the most up to date one? I re-downloaded the scripts > from ponce's, added the patch you suggested and it all compiled fine > now. Thank you again. > The repo from ponce is an unofficial repo just for -current, where Willy's is for 14.2. Both are up-to-date, but designed for different versions of Slackware. SBo does not imply any support for -current, although, many scripts happen to work without modification. The unofficial repo from ponce keeps any modifications needed to ensure the scripts build properly and the resulting packages run properly on -current. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Sun Apr 4 20:55:47 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Sun, 4 Apr 2021 21:55:47 +0100 Subject: [Slackbuilds-users] ptlib doesn't compile on -current any more In-Reply-To: References: <739ca281-a28b-17c1-b910-14d4657c60de@open-t.co.uk> <1d7710d5-cd34-c7e8-70d8-8415a905e5d9@open-t.co.uk> Message-ID: <2b09b999-e1d2-8eeb-6890-7edb381fd8f7@open-t.co.uk> On 04/04/2021 21:34, Jeremy Hansen wrote: > On Sun, Apr 4, 2021, 12:59 PM Sebastian Arcus > wrote: > > On 04/04/2021 19:21, Matteo Bernardini wrote: > > strange, builds fine here: I just add this last patch after the other > > ones already applied in the modified ptlib.SlackBuild of the > > unofficial repository for current. > > one of them is specific to port ptlib to openssl-1.1.x and from the > > output you posted could it be that is not applied? > > Sorry - I was getting confused between willysr's and ponce's repos. I > take it ponce's is the most up to date one? I re-downloaded the scripts > from ponce's, added the patch you suggested and it all compiled fine > now. Thank you again. > > > The repo from ponce is an unofficial repo just for -current, where > Willy's is for 14.2. Both are up-to-date, but designed for different > versions of Slackware. > > SBo does not imply any support for -current, although, many scripts > happen to work without modification. The unofficial repo from ponce > keeps any modifications needed to ensure the scripts build properly and > the resulting packages run properly on -current. Thank you for the explanation. I realise there are good reasons for the SBo website only tracking the latest stable - but with 14.2 approaching 5 years old now, there are more and more pressing reasons to try and install something more recent than that. It is good that ponce has a repo which will work with -current. I wonder if there would be anyway this fact could be made more prominent in the docs or on the SBo website somewhere - it feels a bit like having to join the "underground" movement to find out about it :-) From kingbeowulf at gmail.com Sun Apr 4 22:26:41 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sun, 4 Apr 2021 15:26:41 -0700 Subject: [Slackbuilds-users] Gridcoin-Research EOL on Slackware-14.2 Message-ID: <52058db2-bedb-5d15-b297-e27b641bef5b@gmail.com> Hello, For 14.2 Gridcoin-Research-5.3.0.0 is the end unless openssl is upgraded. The next update 5.3.1.0 requires openssl-1.1.1j and 14.2 is currently at openssl-1.0.2u I'll post this on LQ as well for wider distribution. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From fellype at gmail.com Mon Apr 5 18:29:37 2021 From: fellype at gmail.com (Fellype) Date: Mon, 5 Apr 2021 15:29:37 -0300 Subject: [Slackbuilds-users] TauonMusicBox needs more deps Message-ID: Hi all, It looks like tauonmb also requires BeautifulSoup4 (runtime dep), which in turn require python3-soupsieve since tauonmb is built under some python3 stuff. With those deps tauonmb runs fine. Without them, the following errors are returned in command line: fellype at plasma:~$ tauonmb Tauon Music Box v6.5.4 Copyright 2015-2020 Taiko2k captain.gxj at gmail.com Running from installed location User files location: /home/fellype/.local/share/TauonMusicBox Found XDG-Downloads: /home/fellype/Downloads Found XDG-Music: /home/fellype/ Install directory: /opt/tauon-music-box Traceback (most recent call last): File "/usr/lib64/python3.9/site-packages/PyLyrics/classes.py", line 3, in from .functions import * File "/usr/lib64/python3.9/site-packages/PyLyrics/functions.py", line 2, in from bs4 import BeautifulSoup, Comment, NavigableString ModuleNotFoundError: No module named 'bs4' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib64/python3.9/site-packages/PyLyrics/__init__.py", line 6, in from .classes import * File "/usr/lib64/python3.9/site-packages/PyLyrics/classes.py", line 5, in from functions import * ModuleNotFoundError: No module named 'functions' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/opt/tauon-music-box/tauon.py", line 747, in from t_modules.t_lyrics import * File "/opt/tauon-music-box/t_modules/t_lyrics.py", line 22, in from PyLyrics import PyLyrics File "/usr/lib64/python3.9/site-packages/PyLyrics/__init__.py", line 11, in from functions import * ModuleNotFoundError: No module named 'functions' Note: tested in -current. But I guess it also applies to 14.2. Regards, Fellype -------------- next part -------------- An HTML attachment was scrubbed... URL: From ricardo at palmtx.com.ar Mon Apr 5 20:14:47 2021 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Mon, 5 Apr 2021 17:14:47 -0300 Subject: [Slackbuilds-users] chntpw doesn't compile on -current In-Reply-To: <142363e3-8f8a-42e8-5669-17c28eabc8cf@open-t.co.uk> References: <142363e3-8f8a-42e8-5669-17c28eabc8cf@open-t.co.uk> Message-ID: <202104051714.47863.ricardo@palmtx.com.ar> El Domingo 04/04/2021 a las 12:51, Sebastian Arcus escribi?: > Just a heads up that chntpw doesn't seem to compile any more against > -current. I've updated today to -current and tried it using the 14.2 SBo > scripts, and using the scripts from Ponce's GitHub repository. The error > message is below. Looking at the age of the code, I wouldn't be > surprised if it has become incompatible with current libraries somewhere > - but this is only me guessing. FWIW, version 140201 compiles fine on -current so maybe a bump will be needed. Also, I see that 7 utilities get compiled: chntpw, chntpw.static, cpnt, reged, reged.static, samusrgrp and sampasswd but only the first 5 get packaged by the slackbuild. CCing the maintainer in case they want to send an update. Cheers, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From dave at slackbuilds.org Mon Apr 5 21:14:12 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Mon, 5 Apr 2021 22:14:12 +0100 Subject: [Slackbuilds-users] TauonMusicBox needs more deps In-Reply-To: References: Message-ID: <20210405211412.GC5008@localhost> On 05/04/21 15:29, Fellype put forth the proposition: > Hi all, > It looks like tauonmb also requires BeautifulSoup4 (runtime dep), which in > turn require python3-soupsieve since tauonmb is built under some python3 > Regards, > Fellype Thanks, I'll add those for next weeks updates. -- Dave From mario at slackware.hr Tue Apr 6 10:11:53 2021 From: mario at slackware.hr (Mario) Date: Tue, 6 Apr 2021 12:11:53 +0200 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> <20210403140313.GA3566@pc21.mareichelt.com> Message-ID: <58ec1300-6d62-a8f0-547b-78c8f74995d9@slackware.hr> On 4/4/21 2:28 AM, Greg' Ar Tourter wrote: > Hi, > > The latest Teams slackbuild fails due to the missing doinst.sh file. I > am not sure it is supposed to be there but missing, or was removed on > purpose but the slackbuild script is still expecting one. > > Cheers > > Greg > Hey all, Yeah, this has been fixed in my branch for a couple of days now. It will probably get released on the weekend. Sorry about that :) Regards, -- Mario -------------- next part -------------- An HTML attachment was scrubbed... URL: From s.arcus at open-t.co.uk Tue Apr 6 12:07:04 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 6 Apr 2021 13:07:04 +0100 Subject: [Slackbuilds-users] chntpw doesn't compile on -current In-Reply-To: <202104051714.47863.ricardo@palmtx.com.ar> References: <142363e3-8f8a-42e8-5669-17c28eabc8cf@open-t.co.uk> <202104051714.47863.ricardo@palmtx.com.ar> Message-ID: <8e244331-beb9-0512-6cdf-73382d57bfd4@open-t.co.uk> On 05/04/2021 21:14, Ricardo J. Barberis wrote: > El Domingo 04/04/2021 a las 12:51, Sebastian Arcus escribi?: >> Just a heads up that chntpw doesn't seem to compile any more against >> -current. I've updated today to -current and tried it using the 14.2 SBo >> scripts, and using the scripts from Ponce's GitHub repository. The error >> message is below. Looking at the age of the code, I wouldn't be >> surprised if it has become incompatible with current libraries somewhere >> - but this is only me guessing. > > FWIW, version 140201 compiles fine on -current so maybe a bump will be needed. > > Also, I see that 7 utilities get compiled: chntpw, chntpw.static, cpnt, reged, > reged.static, samusrgrp and sampasswd but only the first 5 get packaged by > the slackbuild. > > CCing the maintainer in case they want to send an update. Brilliant - thank you very much for that. I think it's been already updated in the -current repo, as I just retried to install it with sbotools and it installed 140201 without problems. From s.arcus at open-t.co.uk Tue Apr 6 13:52:33 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 6 Apr 2021 14:52:33 +0100 Subject: [Slackbuilds-users] Ekiga 4.0.1 not compiling on current Message-ID: <7fce8a26-cf98-9833-3653-67a46a86e427@open-t.co.uk> Just a note that Ekiga 4.0.1 doesn't compile any more on current. I've enclosed below the error message. Looking at Ekiga's website, this version is from 2013 and there haven't been any updates since. Could it have developed some incompatibility with a current library in Slackware? ../lib/engine/framework/services.cpp:159:13: error: ?endl? is not a member of ?std? 159 | << std::endl | ^~~~ ../lib/engine/framework/services.cpp:47:1: note: ?std::endl? is defined in header ??; did you forget to ?#include ?? 46 | #include "services.h" +++ |+#include 47 | ../lib/engine/framework/services.cpp:161:13: error: ?endl? is not a member of ?std? 161 | << std::endl; | ^~~~ ../lib/engine/framework/services.cpp:161:13: note: ?std::endl? is defined in header ??; did you forget to ?#include ?? make[3]: *** [Makefile:2052: services.lo] Error 1 make[3]: Leaving directory '/tmp/SBo/ekiga-4.0.1/lib' make[2]: *** [Makefile:1436: all] Error 2 make[2]: Leaving directory '/tmp/SBo/ekiga-4.0.1/lib' make[1]: *** [Makefile:645: all-recursive] Error 1 make[1]: Leaving directory '/tmp/SBo/ekiga-4.0.1' make: *** [Makefile:529: all] Error 2 Failures: ekiga: ekiga.SlackBuild return non-zero From matteo.bernardini at gmail.com Tue Apr 6 14:26:26 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 6 Apr 2021 16:26:26 +0200 Subject: [Slackbuilds-users] Ekiga 4.0.1 not compiling on current In-Reply-To: <7fce8a26-cf98-9833-3653-67a46a86e427@open-t.co.uk> References: <7fce8a26-cf98-9833-3653-67a46a86e427@open-t.co.uk> Message-ID: it needs an additional header included to build with gcc 10.x: I included an additional patch http://cgit.ponce.cc/slackbuilds/commit/?h=ekiga Matteo Il giorno mar 6 apr 2021 alle ore 15:52 Sebastian Arcus ha scritto: > > Just a note that Ekiga 4.0.1 doesn't compile any more on current. I've > enclosed below the error message. Looking at Ekiga's website, this > version is from 2013 and there haven't been any updates since. Could it > have developed some incompatibility with a current library in Slackware? > > > > ../lib/engine/framework/services.cpp:159:13: error: ?endl? is not a > member of ?std? > 159 | << std::endl > | ^~~~ > ../lib/engine/framework/services.cpp:47:1: note: ?std::endl? is defined > in header ??; did you forget to ?#include ?? > 46 | #include "services.h" > +++ |+#include > 47 | > ../lib/engine/framework/services.cpp:161:13: error: ?endl? is not a > member of ?std? > 161 | << std::endl; > | ^~~~ > ../lib/engine/framework/services.cpp:161:13: note: ?std::endl? is > defined in header ??; did you forget to ?#include ?? > make[3]: *** [Makefile:2052: services.lo] Error 1 > make[3]: Leaving directory '/tmp/SBo/ekiga-4.0.1/lib' > make[2]: *** [Makefile:1436: all] Error 2 > make[2]: Leaving directory '/tmp/SBo/ekiga-4.0.1/lib' > make[1]: *** [Makefile:645: all-recursive] Error 1 > make[1]: Leaving directory '/tmp/SBo/ekiga-4.0.1' > make: *** [Makefile:529: all] Error 2 > Failures: > ekiga: ekiga.SlackBuild return non-zero > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From s.arcus at open-t.co.uk Tue Apr 6 15:55:55 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 6 Apr 2021 16:55:55 +0100 Subject: [Slackbuilds-users] Ekiga 4.0.1 not compiling on current In-Reply-To: References: <7fce8a26-cf98-9833-3653-67a46a86e427@open-t.co.uk> Message-ID: <8dc3d28c-eb07-98dc-e98b-7ee9691116bb@open-t.co.uk> On 06/04/2021 15:26, Matteo Bernardini wrote: > it needs an additional header included to build with gcc 10.x: I > included an additional patch > > http://cgit.ponce.cc/slackbuilds/commit/?h=ekiga Thank you very much for that - I can confirm that with the new patches I was able to compile and install Ekiga here. On the downside, it keeps on freezing and won't register to the SIP server (with "remote party is offline" error) - although before Slackware upgrade it was working fine with the same settings. But that might be beyond the scope of this conversation. I'll keep on persisting with it to see if I get anywhere. Thank you again > > Matteo > > Il giorno mar 6 apr 2021 alle ore 15:52 Sebastian Arcus > ha scritto: >> >> Just a note that Ekiga 4.0.1 doesn't compile any more on current. I've >> enclosed below the error message. Looking at Ekiga's website, this >> version is from 2013 and there haven't been any updates since. Could it >> have developed some incompatibility with a current library in Slackware? >> >> >> >> ../lib/engine/framework/services.cpp:159:13: error: ?endl? is not a >> member of ?std? >> 159 | << std::endl >> | ^~~~ >> ../lib/engine/framework/services.cpp:47:1: note: ?std::endl? is defined >> in header ??; did you forget to ?#include ?? >> 46 | #include "services.h" >> +++ |+#include >> 47 | >> ../lib/engine/framework/services.cpp:161:13: error: ?endl? is not a >> member of ?std? >> 161 | << std::endl; >> | ^~~~ >> ../lib/engine/framework/services.cpp:161:13: note: ?std::endl? is >> defined in header ??; did you forget to ?#include ?? >> make[3]: *** [Makefile:2052: services.lo] Error 1 >> make[3]: Leaving directory '/tmp/SBo/ekiga-4.0.1/lib' >> make[2]: *** [Makefile:1436: all] Error 2 >> make[2]: Leaving directory '/tmp/SBo/ekiga-4.0.1/lib' >> make[1]: *** [Makefile:645: all-recursive] Error 1 >> make[1]: Leaving directory '/tmp/SBo/ekiga-4.0.1' >> make: *** [Makefile:529: all] Error 2 >> Failures: >> ekiga: ekiga.SlackBuild return non-zero >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From s.arcus at open-t.co.uk Tue Apr 6 16:47:58 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 6 Apr 2021 17:47:58 +0100 Subject: [Slackbuilds-users] HandBrake not compiling on current Message-ID: <9a12dc1d-1868-960b-28f0-81e3c1f0f7c7@open-t.co.uk> Sorry - I'm afraid I have another one. HandBrake refuses to compile on -current with the following error message. I tried the latest version (1.3.3) as well - and I get a different error message (see further down below). I checked that there are no newer SBo scripts at ponce's GitHub. Trying to compile HandBrake 1.0.7: < /snip> /usr/include/pango-1.0/pango/pango-font.h:555:48: error: unknown type name ?hb_feature_t?; did you mean ?hb_value_t?? 555 | hb_feature_t *features, | ^~~~~~~~~~~~ | hb_value_t /usr/include/pango-1.0/pango/pango-font.h:558:3: error: expected ?;? before ?hb_font_t? 558 | hb_font_t * (*create_hb_font) (PangoFont *font); | ^~~~~~~~~ /usr/include/pango-1.0/pango/pango-font.h:598:53: error: unknown type name ?hb_feature_t?; did you mean ?hb_value_t?? 598 | hb_feature_t *features, | ^~~~~~~~~~~~ | hb_value_t /usr/include/pango-1.0/pango/pango-font.h:602:1: error: unknown type name ?hb_font_t? 602 | hb_font_t * pango_font_get_hb_font (PangoFont *font); | ^~~~~~~~~ make[3]: *** [Makefile:598: callbacks.o] Error 1 make[3]: Leaving directory '/tmp/SBo/HandBrake-1.0.7/build/gtk/src' make[2]: *** [Makefile:448: all-recursive] Error 1 make[1]: *** [Makefile:380: all] Error 2 make: *** [../gtk/module.rules:27: gtk.build] Error 2 make[2]: Leaving directory '/tmp/SBo/HandBrake-1.0.7/build/gtk' make[1]: Leaving directory '/tmp/SBo/HandBrake-1.0.7/build/gtk' Failures: HandBrake: HandBrake.SlackBuild return non-zero Trying to compile HandBrake 1.3.3: probe: numa...(fail) code 1 : b'Package numa was not found in the pkg-config search path.' : b"Perhaps you should add the directory containing `numa.pc'" : b'to the PKG_CONFIG_PATH environment variable' : b"No package 'numa' found" : [b'conftest.c:2:10: fatal error: numa.h: No such file or directory', b' 2 | #include ', b' | ^~~~~~~~', b'compilation terminated.'] ERROR: unable to continue; configure stop. From matteo.bernardini at gmail.com Tue Apr 6 16:59:19 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Tue, 6 Apr 2021 18:59:19 +0200 Subject: [Slackbuilds-users] HandBrake not compiling on current In-Reply-To: <9a12dc1d-1868-960b-28f0-81e3c1f0f7c7@open-t.co.uk> References: <9a12dc1d-1868-960b-28f0-81e3c1f0f7c7@open-t.co.uk> Message-ID: personally I use Alien Bob's prebuilt package on current. Matteo Il giorno mar 6 apr 2021 alle ore 18:48 Sebastian Arcus ha scritto: > > Sorry - I'm afraid I have another one. HandBrake refuses to compile on > -current with the following error message. I tried the latest version > (1.3.3) as well - and I get a different error message (see further down > below). I checked that there are no newer SBo scripts at ponce's GitHub. > > > Trying to compile HandBrake 1.0.7: > > < /snip> > > /usr/include/pango-1.0/pango/pango-font.h:555:48: error: unknown type > name ?hb_feature_t?; did you mean ?hb_value_t?? > 555 | hb_feature_t > *features, > | ^~~~~~~~~~~~ > | hb_value_t > /usr/include/pango-1.0/pango/pango-font.h:558:3: error: expected ?;? > before ?hb_font_t? > 558 | hb_font_t * (*create_hb_font) (PangoFont > *font); > | ^~~~~~~~~ > /usr/include/pango-1.0/pango/pango-font.h:598:53: error: unknown type > name ?hb_feature_t?; did you mean ?hb_value_t?? > 598 | > hb_feature_t *features, > | ^~~~~~~~~~~~ > | hb_value_t > /usr/include/pango-1.0/pango/pango-font.h:602:1: error: unknown type > name ?hb_font_t? > 602 | hb_font_t * pango_font_get_hb_font (PangoFont > *font); > | ^~~~~~~~~ > make[3]: *** [Makefile:598: callbacks.o] Error 1 > make[3]: Leaving directory '/tmp/SBo/HandBrake-1.0.7/build/gtk/src' > make[2]: *** [Makefile:448: all-recursive] Error 1 > make[1]: *** [Makefile:380: all] Error 2 > make: *** [../gtk/module.rules:27: gtk.build] Error 2 > make[2]: Leaving directory '/tmp/SBo/HandBrake-1.0.7/build/gtk' > make[1]: Leaving directory '/tmp/SBo/HandBrake-1.0.7/build/gtk' > Failures: > HandBrake: HandBrake.SlackBuild return non-zero > > > Trying to compile HandBrake 1.3.3: > > > > probe: numa...(fail) code 1 > : b'Package numa was not found in the pkg-config search path.' > : b"Perhaps you should add the directory containing `numa.pc'" > : b'to the PKG_CONFIG_PATH environment variable' > : b"No package 'numa' found" > : [b'conftest.c:2:10: fatal error: numa.h: No such file or > directory', b' 2 | #include ', b' | ^~~~~~~~', > b'compilation terminated.'] > ERROR: unable to continue; configure stop. > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From yalhcru at gmail.com Tue Apr 6 17:02:28 2021 From: yalhcru at gmail.com (B Watson) Date: Tue, 6 Apr 2021 13:02:28 -0400 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: On 4/2/21, Willy Sudiarto Raharjo wrote: > network/protonmail-bridge: Updated for version 1.6.9. Download link is 404. Fixed in my branch. > games/freeciv: updated for version 2.6.4 md5sum mismatch. Maintainer updated DOWNLOAD in the .info file but not MD5SUM. Fixed in my branch. From erich.public at protonmail.com Tue Apr 6 17:12:13 2021 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 06 Apr 2021 17:12:13 +0000 Subject: [Slackbuilds-users] Updates - 20210403.1 In-Reply-To: References: <14ee50da-d3b7-7d24-7f71-583aa804004c@slackbuilds.org> Message-ID: On Tuesday, April 6, 2021 10:02 AM, B Watson wrote: > On 4/2/21, Willy Sudiarto Raharjo willysr at slackbuilds.org wrote: > > > network/protonmail-bridge: Updated for version 1.6.9. > > Download link is 404. Fixed in my branch. Thank you! That's what I get for not clearing the download cache before running my final sbopkg check before submission. Erich From jvbernts at online.no Tue Apr 6 20:05:47 2021 From: jvbernts at online.no (Jostein Berntsen) Date: Tue, 6 Apr 2021 22:05:47 +0200 Subject: [Slackbuilds-users] sc-im not found Message-ID: Hi, I am maintaining the sc-im package which can be found at the web site search: https://slackbuilds.org/repository/14.2/office/sc-im/?search=sc-im Cli search with "sbopkg -g sc-im" or search in sbopkg curses do not work though. Is there an update needed for search here? Jostein From s.arcus at open-t.co.uk Tue Apr 6 20:18:50 2021 From: s.arcus at open-t.co.uk (Sebastian Arcus) Date: Tue, 6 Apr 2021 21:18:50 +0100 Subject: [Slackbuilds-users] HandBrake not compiling on current In-Reply-To: References: <9a12dc1d-1868-960b-28f0-81e3c1f0f7c7@open-t.co.uk> Message-ID: <997cdeca-5d0d-3caa-f83d-aaf675da1f72@open-t.co.uk> On 06/04/2021 17:59, Matteo Bernardini wrote: > personally I use Alien Bob's prebuilt package on current. Thank you for that - I didn't know that existed. I've installed it and it starts fine. Thanks From ricardo at palmtx.com.ar Tue Apr 6 23:49:22 2021 From: ricardo at palmtx.com.ar (Ricardo J. Barberis) Date: Tue, 6 Apr 2021 20:49:22 -0300 Subject: [Slackbuilds-users] sc-im not found In-Reply-To: References: Message-ID: <202104062049.22964.ricardo@palmtx.com.ar> El Martes 06/04/2021 a las 17:05, Jostein Berntsen escribi?: > Hi, > > I am maintaining the sc-im package which can be found at the web site > search: > > https://slackbuilds.org/repository/14.2/office/sc-im/?search=sc-im > > Cli search with "sbopkg -g sc-im" or search in sbopkg curses do not work > though. Is there an update needed for search here? > > > Jostein I see it: $ sudo sbopkg -g sc-im Searching for sc-im Found the following matches for sc-im: office/sc-im Maybe you forgot to run 'sudo sbopkg -r' to update your local copy of SBo? Cheers, -- Ricardo J. Barberis Usuario Linux N? 250625: http://counter.li.org/ Usuario LFS N? 5121: http://www.linuxfromscratch.org/ Senior SysAdmin / IT Architect - www.DonWeb.com From willysr at slackbuilds.org Sat Apr 10 10:28:46 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 10 Apr 2021 17:28:46 +0700 Subject: [Slackbuilds-users] Updates - 20210410.1 Message-ID: <382f2adf-0c7f-d16c-d124-34e20dac0551@slackbuilds.org> Sat Apr 10 10:06:04 UTC 2021 academic/Gridcoin-Research: Updated for version 5.3.1.0 academic/boinc: Updated for version 7.16.16 academic/sword-data-kjv: Updated for version 1.8.1_1. academic/wxMaxima: Updated for version 21.01.0. audio/ardour: Updated for version 6.6. audio/ncmpcpp: Update maintainer email. audio/vimpc: Update maintainer email. development/QtPy: Added (Qt abstraction layer for Python) development/apache-maven: Updated for version 3.8.1. development/dotnet-runtime: Updated for version 3.1.13. development/dotnet-sdk: Updated for version 3.1.407. development/ghi: Update maintainer email. development/github-cli: Updated for version 1.8.1 development/jupyter-ipykernel: Updated for version 5.3.4. development/jupyter-ipywidgets: Updated for version 7.6.3. development/jupyter-nbclient: Added (execution contexts). development/jupyter-nbconvert: Updated for version 6.0.7. development/jupyter-nbformat: Updated for version 5.1.3. development/jupyter-notebook: Updated for version 6.3.0. development/jupyter-qtconsole: Update dependencies. development/jupyter-qtconsole: Updated for version 5.0.1. development/jupyter_client: Remove Python 2 support. development/jupyter_client: Updated for version 6.1.13. development/jupyter_console: Change dependencies. development/jupyter_console: Updated for version 6.4.0. development/jupyter_core: Remove Python 2 support. development/jupyterlab_pygments: Added (theme for Pygments). development/mongodb-compass: Updated for version 1.26.1. development/neovim: Update homepage. development/nim: Updated for version 1.4.4. development/nodejs-bin: Updated for version 14.16.1. development/nodejs: Updated for version 12.22.1. development/racer: Updated for version 2.1.45. development/robotframework: Updated for version 4.0.1. development/sbcl: Updated for version 2.1.3. development/sdcc: Updated for version 4.1.0. development/slibtool: Updated for version 0.5.33. development/xkeys-sdk: Added (SDK for X-Keys) games/VASSAL: Updated for version 3.5.5. games/crispy-doom: Updated for version 5.10.1. games/freeciv: wrong md5sum games/steam: Updated for version 1.0.0.69 gis/Fiona: Updated for version 1.8.19. gis/geopandas: Updated for version 0.9.0. gis/osm2pgsql: Updated for version 1.4.1. gis/pgsql-ogr-fdw: Updated for version 1.1.0. gis/qgis: Support PROJ 8. gis/spatialite_gui: Add a fix for the newer proj. graphics/mtpaint: Updated for version 3.50. graphics/vuescan: Updated for version 9.7.52. ibraries/lua-luv: Updated for version 1.36.0_0. libraries/Jinja2: Updated for version 2.11.3. libraries/aspnetcore-runtime: Updated for version 3.1.13. libraries/libcpuid: Updated for version 0.5.1. libraries/libfastjson: Updated for version 0.99.9. libraries/libprelude: Added (Prelude SIEM/sensor library) libraries/librelp: Updated for version 1.10.0. libraries/libvterm: Updated for version 0.1.4. libraries/libxkbcommon: Updated for version 1.2.0. libraries/libxnvctrl: Updated for version 460.67. libraries/luasec: Updated for version 1.0. libraries/opencv: Updated for version 4.5.2 libraries/tox-extension-messages: Added (extension library for tox). libraries/toxext: Added (extension library for tox). libraries/unibilium: Updated for version 2.1.1. misc/mosquitto: Updated for version 2.0.10 multimedia/LBRY: Updated for version 0.50.2. multimedia/droidcam: Added (Chat Program). multimedia/plexmediaserver: Updated for v 1.22.1.4275_48e10484b. multimedia/pyradio: Update maintainer email. multimedia/srt-to-vtt-cl: Added (convert srt files to webtvv) network/Electrum: Updated for version 4.1.1. network/anydesk: Updated for version 6.1.0. network/brave-browser: Updated for version 1.22.71. network/emailrelay: Updated for version 2.2. network/libteam: Added (Library for controlling networking). network/mumble: Updated for version 1.3.4 network/murmur: Updated for version 1.3.4 network/newsboat: Updated for version 2.23. network/openfortivpn: Updated for version 1.16.0. network/privoxy: Updated for version 3.0.32. network/prosody: Updated for version 0.11.8. network/protonmail-bridge: Fix download URL. network/qutebrowser-tox: Update pdfjs. network/signal-desktop: Updated for version 1.40.1. network/spamassassin: Updated for version 3.4.5. network/speedtest-cli: Updated for version 2.1.3. network/sslscan: Updated for version 2.0.9. network/teams: Added missing doinst.sh file. network/verm: Updated for version 1.5.2. network/wendzelnntpd: Added (Easy-to-use NNTP Server). office/MasterPDFEditor: Updated for version 5.7.53. office/ghostwriter: Fix for -current. office/mairix: Update maintainer email. office/mu: Update maintainer email. office/notmuch: Update maintainer email. office/nts: Update maintainer email. office/sc-im: Update maintainer email. office/taskjuggler: Update maintainer email. office/teapot: Update maintainer email. office/tnote: Update maintainer email. office/tpp: Update maintainer email. office/tudu: Update maintainer email. office/watson: Update maintainer email. python/Pygments: Updated for version 2.8.1. python/apprise: Added (Multiplatform Push Notifications) python/async_generator: Added (async iterators). python/backcall: Updated for version 0.2.0. python/bleach: Updated for version 3.3.0. python/decorator: Updated for version 5.0.5. python/nest_asyncio: Added (nested async event loops). python/parso: Updated for version 0.8.2. python/python-PySnooper: Updated for version 0.4.3. python/python-emoji: Updated for version 1.2.0. python/python-neovim: Update homepage. python/python-prometheus_client: Updated for version 0.10.0. python/python3-aiorpcX-legacy: Added (async RPC implementation) python/python3-jupyter-ipykernel: Removed (use jupyter-ipykernel). python/python3-packaging: Updated for version 20.9. python/python3-prompt_toolkit: Updated for version 3.0.18. python/python3-pylint: Updated for version 2.7.4. python/python3-stagger: Fix URL. python/sphinxcontrib-applehelp: Updated for version 1.0.2. python/sphinxcontrib-htmlhelp: Updated for version 1.0.3. ruby/chronic: Update maintainer email. ruby/ncurses-ruby: Update maintainer email. ruby/ruby-build: Updated for version 20210405. ruby/rubygem-mail: Update maintainer email. ruby/rubygem-mime-types-data: Update maintainer email. ruby/rubygem-mime-types: Update maintainer email. ruby/rubygem-mini_mime: Update maintainer email. ruby/rubygem-multi_json: Update maintainer email. ruby/rubygem-pygments: Update maintainer email. ruby/rubygem-sync: Update maintainer email. ruby/rubygem-term-ansicolor: Update maintainer email. ruby/rubygem-tins: Update maintainer email. ruby/sequel4: Update maintainer email. ruby/sqlite3: Update maintainer email. system/CPU-X: Updated for version 4.2.0. system/atop: Fix build. system/avfs: Updated for version 1.1.4. system/clamav: Updated for version 0.103.2. system/exa: Updated for version 0.10.0. system/fzf: Updated for version 0.27.0. system/intelmas: Updated for version 1.7. system/jenkins: Updated for version 2.277.2. system/letsencrypt: Updated for version 1.14.0. system/porg: Update maintainer email. system/powershell: Updated for version 7.1.3. system/rsyslog: Updated for version 8.2102.0. system/skim: Updated for version 0.9.4. system/worker: Updated for version 4.8.0. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From belka at caraus.de Sat Apr 10 11:56:27 2021 From: belka at caraus.de (Eugen Wissner) Date: Sat, 10 Apr 2021 13:56:27 +0200 Subject: [Slackbuilds-users] nodejs tar.gz -> tar.xz Message-ID: nodejs download url seems to be https://nodejs.org/dist/v12.22.1/node-v12.22.1.tar.xz but the SlackBuild expects only .tar.gz. Regards Eugen From willysr at slackbuilds.org Sat Apr 10 12:45:38 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 10 Apr 2021 19:45:38 +0700 Subject: [Slackbuilds-users] nodejs tar.gz -> tar.xz In-Reply-To: References: Message-ID: > nodejs download url seems to be > https://nodejs.org/dist/v12.22.1/node-v12.22.1.tar.xz but the > SlackBuild expects only .tar.gz. Fixed in my branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From crts at gmx.net Sat Apr 10 15:20:11 2021 From: crts at gmx.net (CRTS) Date: Sat, 10 Apr 2021 17:20:11 +0200 Subject: [Slackbuilds-users] Broken link for squidguard Message-ID: <20210410152011.GA17166@rhea.titan.net> The SlackBuild for squidGuard contains a broken download link for version 1.4. According to the homepage the current release is version 1.3: http://www.squidguard.org/Downloads/squidGuard-1.3.tar.gz The homepage further contains a link to a patch for version 1.3 but that link is broken, too. From 1.41421 at gmail.com Sat Apr 10 15:25:37 2021 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 10 Apr 2021 09:25:37 -0600 Subject: [Slackbuilds-users] wxMaxima not building in 14.2-64 Message-ID: wxmaxima-Version-21.01.0/test/b.png wxmaxima-Version-21.01.0/test/c.png wxmaxima-Version-21.01.0/test/catch2/ wxmaxima-Version-21.01.0/test/catch2/catch.hpp wxmaxima-Version-21.01.0/test/d.png wxmaxima-Version-21.01.0/test/quit.mac wxmaxima-Version-21.01.0/test/testbench_simple.wxmx wxmaxima-Version-21.01.0/test/unit_tests/ wxmaxima-Version-21.01.0/test/unit_tests/.gitignore wxmaxima-Version-21.01.0/test/unit_tests/CMakeLists.txt wxmaxima-Version-21.01.0/test/unit_tests/TestStubs.cpp wxmaxima-Version-21.01.0/test/unit_tests/Version.h wxmaxima-Version-21.01.0/test/unit_tests/test_AFontSize.cpp wxmaxima-Version-21.01.0/test/unit_tests/test_CellPtr.cpp wxmaxima-Version-21.01.0/test/unit_tests/test_ImgCell.cpp wxmaxima-Version-21.01.0/test/unit_tests/test_ImgCell.h wxmaxima-Version-21.01.0/test/unit_tests/test_SqrtCell.cpp wxmaxima-Version-21.01.0/test/zzuf.sh wxmaxima-Version-21.01.0/wxmaxima.spec.in CMake Error: The source directory "/tmp/SBo/wxmaxima-Version-21.01.0/build" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sat Apr 10 15:33:13 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 10 Apr 2021 17:33:13 +0200 Subject: [Slackbuilds-users] Broken link for squidguard In-Reply-To: <20210410152011.GA17166@rhea.titan.net> References: <20210410152011.GA17166@rhea.titan.net> Message-ID: strange, the source is mirrored on sbosrcarch (and to be hosted there it means it was available in the download location at least until end 2015): extracting and having a look at it seems legit http://slackware.uk/sbosrcarch/by-name/network/squidGuard/ I suppose I can mirror it on my server if it's ok for the maintainer (yes, it's still you, Niki! :-) ). Matteo Il giorno sab 10 apr 2021 alle ore 17:21 CRTS ha scritto: > > The SlackBuild for squidGuard contains a broken download link > for version 1.4. > According to the homepage the current release is version 1.3: > > http://www.squidguard.org/Downloads/squidGuard-1.3.tar.gz > > The homepage further contains a link to a patch for version 1.3 but > that link is broken, too. > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > From matteo.bernardini at gmail.com Sat Apr 10 16:07:02 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 10 Apr 2021 18:07:02 +0200 Subject: [Slackbuilds-users] Broken link for squidguard In-Reply-To: References: <20210410152011.GA17166@rhea.titan.net> Message-ID: well, Niki actually dropped maintainership a while ago, so if you feel like stepping in as a maintainer, CRTS, the script is yours. Matteo Il giorno sab 10 apr 2021 alle ore 17:33 Matteo Bernardini ha scritto: > > strange, the source is mirrored on sbosrcarch (and to be hosted there > it means it was available in the download location at least until end > 2015): extracting and having a look at it seems legit > > http://slackware.uk/sbosrcarch/by-name/network/squidGuard/ > > I suppose I can mirror it on my server if it's ok for the maintainer > (yes, it's still you, Niki! :-) ). > > Matteo > > Il giorno sab 10 apr 2021 alle ore 17:21 CRTS ha scritto: > > > > The SlackBuild for squidGuard contains a broken download link > > for version 1.4. > > According to the homepage the current release is version 1.3: > > > > http://www.squidguard.org/Downloads/squidGuard-1.3.tar.gz > > > > The homepage further contains a link to a patch for version 1.3 but > > that link is broken, too. From dave at slackbuilds.org Sat Apr 10 16:39:05 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 10 Apr 2021 17:39:05 +0100 Subject: [Slackbuilds-users] wxMaxima not building in 14.2-64 In-Reply-To: References: Message-ID: <20210410163905.GK5008@localhost> Luveh Keraph <1.41421 at gmail.com> put forth the proposition: > CMake Error: The source directory "/tmp/SBo/wxmaxima-Version-21.01.0/build" > does not appear to contain CMakeLists.txt. > Specify --help for usage, or press the help button on the CMake GUI. Do you have cmake-202x (3.19.6) and ninja (1.10.2) installed? -- Dave From 1.41421 at gmail.com Sat Apr 10 17:27:20 2021 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 10 Apr 2021 11:27:20 -0600 Subject: [Slackbuilds-users] wxMaxima not building in 14.2-64 In-Reply-To: <20210410163905.GK5008@localhost> References: <20210410163905.GK5008@localhost> Message-ID: Thanks. I did not know that cmake-202x was a dependency for wxMaxima. After installing it (I already had ninja 1.10.2) wxMaxima builds without any problems. On Sat, Apr 10, 2021 at 10:39 AM Dave Woodfall wrote: > Luveh Keraph <1.41421 at gmail.com> put forth the proposition: > > CMake Error: The source directory > "/tmp/SBo/wxmaxima-Version-21.01.0/build" > > does not appear to contain CMakeLists.txt. > > Specify --help for usage, or press the help button on the CMake GUI. > > Do you have cmake-202x (3.19.6) and ninja (1.10.2) installed? > > -- > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From crts at gmx.net Sat Apr 10 18:54:04 2021 From: crts at gmx.net (CRTS) Date: Sat, 10 Apr 2021 20:54:04 +0200 Subject: [Slackbuilds-users] Broken link for squidguard In-Reply-To: References: <20210410152011.GA17166@rhea.titan.net> Message-ID: <20210410185404.GA1967@rhea.titan.net> Ok, I am taking over. Just need to figure out why there is no official version 1.3 anymore. I will contact the authors at "squidguard.org". By the way, is "squid" itself still maintained? Stable version is 4.14 and version on SBo is 4.13. On Sat, Apr 10, 2021 at 06:07:02PM +0200, Matteo Bernardini wrote: > well, Niki actually dropped maintainership a while ago, so if you feel > like stepping in as a maintainer, CRTS, the script is yours. > > Matteo > > Il giorno sab 10 apr 2021 alle ore 17:33 Matteo Bernardini > ha scritto: > > > > strange, the source is mirrored on sbosrcarch (and to be hosted there > > it means it was available in the download location at least until end > > 2015): extracting and having a look at it seems legit > > > > http://slackware.uk/sbosrcarch/by-name/network/squidGuard/ > > > > I suppose I can mirror it on my server if it's ok for the maintainer > > (yes, it's still you, Niki! :-) ). > > > > Matteo > > > > Il giorno sab 10 apr 2021 alle ore 17:21 CRTS ha scritto: > > > > > > The SlackBuild for squidGuard contains a broken download link > > > for version 1.4. > > > According to the homepage the current release is version 1.3: > > > > > > http://www.squidguard.org/Downloads/squidGuard-1.3.tar.gz > > > > > > The homepage further contains a link to a patch for version 1.3 but > > > that link is broken, too. > _______________________________________________ > 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 arnaud.garcia-fernandez at laposte.net Sat Apr 10 18:59:20 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sat, 10 Apr 2021 20:59:20 +0200 Subject: [Slackbuilds-users] Warzone 2100 4.0.0 will have to wait. Message-ID: <20210410205920.bf79b818e32e0fb3f9d911da@laposte.net> Hi everybody, unfortunately 14.2 oldness striked again. This time it's SQLite that is too old for the brand new 4.0.0 version of Warzone 2100. For people using -current at home, a simple version bump is enough to build the package. Others will have to either upgrade their sqlite at their own risk, or wait for 15.0... Arnaud From 1.41421 at gmail.com Sat Apr 10 19:58:22 2021 From: 1.41421 at gmail.com (Luveh Keraph) Date: Sat, 10 Apr 2021 13:58:22 -0600 Subject: [Slackbuilds-users] netdata still not building in 14.2-64 Message-ID: ./netdata.SlackBuild: line 91: /home/xyz/Downloads/netdata/9644483b6069bb474942df5afc1156968a99d7b2.patch: No such file or directory That patch file does not seem to be present anywhere. Commenting out the offending line in the slackbuilds file results in the same build error reported last week. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sat Apr 10 20:15:02 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 10 Apr 2021 21:15:02 +0100 Subject: [Slackbuilds-users] Warzone 2100 4.0.0 will have to wait. In-Reply-To: <20210410205920.bf79b818e32e0fb3f9d911da@laposte.net> References: <20210410205920.bf79b818e32e0fb3f9d911da@laposte.net> Message-ID: <20210410201502.GL5008@localhost> Slackbuilds Users put forth the proposition: > Hi everybody, > unfortunately 14.2 oldness striked again. > This time it's SQLite that is too old for the brand new 4.0.0 version of Warzone > 2100. Have you looked at the possibility of using a bundled version of sqlite? A few slackbuilds download and use internal versions of libs etc. when the stock ones are too old. -- Dave From kingbeowulf at gmail.com Sat Apr 10 20:35:31 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Sat, 10 Apr 2021 13:35:31 -0700 Subject: [Slackbuilds-users] Warzone 2100 4.0.0 will have to wait. In-Reply-To: <20210410201502.GL5008@localhost> References: <20210410205920.bf79b818e32e0fb3f9d911da@laposte.net> <20210410201502.GL5008@localhost> Message-ID: <49b6e329-f1d6-f0c5-86c9-8999393d5423@gmail.com> On 4/10/21 1:15 PM, Dave Woodfall wrote: > Slackbuilds Users put forth the proposition: >> Hi everybody, >> unfortunately 14.2 oldness striked again. >> This time it's SQLite that is too old for the brand new 4.0.0 version of Warzone >> 2100. > > Have you looked at the possibility of using a bundled version of > sqlite? A few slackbuilds download and use internal versions of libs > etc. when the stock ones are too old. > I considered this as well for some of mine but rejected it. Since Current is "real soon now" it didn't seem worth the effort or risk. -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From arnaud.garcia-fernandez at laposte.net Sat Apr 10 21:10:21 2021 From: arnaud.garcia-fernandez at laposte.net (Arnaud) Date: Sat, 10 Apr 2021 23:10:21 +0200 Subject: [Slackbuilds-users] Warzone 2100 4.0.0 will have to wait. In-Reply-To: <49b6e329-f1d6-f0c5-86c9-8999393d5423@gmail.com> References: <20210410205920.bf79b818e32e0fb3f9d911da@laposte.net> <20210410201502.GL5008@localhost> <49b6e329-f1d6-f0c5-86c9-8999393d5423@gmail.com> Message-ID: <20210410231021.fbf18566ed08bfedd8c92fc0@laposte.net> > On 4/10/21 1:15 PM, Dave Woodfall wrote: > > Slackbuilds Users put forth the > > proposition: > >> Hi everybody, > >> unfortunately 14.2 oldness striked again. > >> This time it's SQLite that is too old for the brand new 4.0.0 version of > >> Warzone > >> 2100. > > > > Have you looked at the possibility of using a bundled version of > > sqlite? A few slackbuilds download and use internal versions of libs > > etc. when the stock ones are too old. > > > > I considered this as well for some of mine but rejected it. Since > Current is "real soon now" it didn't seem worth the effort or risk. > > -Ed I'm there too : doesn't feel its worth the hassle since 15.0 is coming. And also, I feel that people really wanting to have an up-to-date warzone2100 might already be on -current, at least since 15.0-beta is out. And others may feel ok to wait a few months (hoping it won't be longer). But that's also why I sent the original message :if there are people really wanting it for 14.2, then it might be worth the effort. If nobody really asks for this specifically, I won't do it. -- Arnaud From willysr at slackbuilds.org Sun Apr 11 02:06:31 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 11 Apr 2021 09:06:31 +0700 Subject: [Slackbuilds-users] netdata still not building in 14.2-64 In-Reply-To: References: Message-ID: > ./netdata.SlackBuild: line 91: > /home/xyz/Downloads/netdata/9644483b6069bb474942df5afc1156968a99d7b2.patch: > No such file or directory > > That patch file does not seem to be present anywhere. Commenting out the > offending line in the slackbuilds file results in the same build error > reported last week. Yeah, my mistake. That commit should be on a different testing branch, but somehow i accidentally merge it into my own branch. The patch is used for upstream to create the correct tarball, so it will still fail to build until we have a new release. I think i will revert it to previous working version first. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From milgram at cgpp.com Sun Apr 11 02:25:35 2021 From: milgram at cgpp.com (Judah Milgram) Date: Sat, 10 Apr 2021 22:25:35 -0400 Subject: [Slackbuilds-users] wxMaxima not building in 14.2-64 In-Reply-To: References: <20210410163905.GK5008@localhost> Message-ID: Right, it didn't used to require cmake - this is the first wxMaxima SBo that does. I didn't notice that it required ninja! On 4/10/21 1:27 PM, Luveh Keraph wrote: > Thanks. I did not know that cmake-202x was a dependency for wxMaxima. > After installing it (I already had ninja 1.10.2) wxMaxima builds without > any problems. > > On Sat, Apr 10, 2021 at 10:39 AM Dave Woodfall > wrote: > > Luveh Keraph <1.41421 at gmail.com > put > forth the proposition: > > CMake Error: The source directory > "/tmp/SBo/wxmaxima-Version-21.01.0/build" > > does not appear to contain CMakeLists.txt. > > Specify --help for usage, or press the help button on the CMake GUI. > > Do you have cmake-202x (3.19.6) and ninja (1.10.2) installed? > > -- > Dave > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -- Judah Milgram milgram at cgpp.com 301-257-7069 From yalhcru at gmail.com Sun Apr 11 06:45:36 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 11 Apr 2021 02:45:36 -0400 Subject: [Slackbuilds-users] mosquitto download Message-ID: Currently getting "connection refused" from mosquitto.org. There's another copy of the file here: http://ftp.osuosl.org/pub/gentoo/distfiles/mosquitto-2.0.10.tar.gz ...same md5sum. Might be worth updating the .info file? From yalhcru at gmail.com Sun Apr 11 06:49:13 2021 From: yalhcru at gmail.com (B Watson) Date: Sun, 11 Apr 2021 02:49:13 -0400 Subject: [Slackbuilds-users] jupyter-ipykernel md5sum fail Message-ID: The version and download URL in the .info file got updated, but the md5sum didn't (it's still for the old version). Fixed on my branch. From belka at caraus.de Sun Apr 11 06:49:19 2021 From: belka at caraus.de (Eugen Wissner) Date: Sun, 11 Apr 2021 08:49:19 +0200 Subject: [Slackbuilds-users] adoptopenjdk-openj9 profile Message-ID: adoptopenjdk-openj9 installs 2 files into /etc/profile.d: adoptopenjdk-openj9.sh and adoptopenjdk-openj9.csh. JAVA_HOME is set there to /usr/local/lib/jdk- at VERSION@, but the java files are extracted into /usr/lib/jdk- at VERSION@ (where "lib" is "lib" or "lib64"). Further, the resulting package contains an empty /usr/bin directory. From sbolokanov at abv.bg Sun Apr 11 08:27:05 2021 From: sbolokanov at abv.bg (=?utf-8?B?0KHQuNC80L7QvdGKINCR0L7Qu9C+0LrQsNC90L7QstGK?=) Date: Sun, 11 Apr 2021 11:27:05 +0300 (EEST) Subject: [Slackbuilds-users] dmenu2 remove request Message-ID: <85196616.314548.1618129625935@nm52.abv.bg> Original maintainer of this fork is no longer active. dmenu has been forked like a hundred times by now. I guess it's better to remove it. -- ?. ?. ?????????? -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Sun Apr 11 08:37:56 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sun, 11 Apr 2021 10:37:56 +0200 Subject: [Slackbuilds-users] dmenu2 remove request In-Reply-To: <85196616.314548.1618129625935@nm52.abv.bg> References: <85196616.314548.1618129625935@nm52.abv.bg> Message-ID: done in my branch. Matteo Il giorno dom 11 apr 2021 alle ore 10:27 ?????? ?????????? ha scritto: > > Original maintainer of this fork is no longer active. dmenu has been forked like a hundred times by now. > I guess it's better to remove 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 belka at caraus.de Sun Apr 11 09:31:39 2021 From: belka at caraus.de (Eugen Wissner) Date: Sun, 11 Apr 2021 11:31:39 +0200 Subject: [Slackbuilds-users] adoptopenjdk-openj9 profile In-Reply-To: Message-ID: And I've just got "mailbox unavailable" from the maintainer's mail provider. On Sun Apr 11, 2021 at 8:49 AM CEST, Eugen Wissner wrote: > adoptopenjdk-openj9 installs 2 files into /etc/profile.d: > adoptopenjdk-openj9.sh and adoptopenjdk-openj9.csh. JAVA_HOME is set > there to /usr/local/lib/jdk- at VERSION@, but the java files are extracted > into /usr/lib/jdk- at VERSION@ (where "lib" is "lib" or "lib64"). Further, > the resulting package contains an empty /usr/bin directory. > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ From willysr at slackbuilds.org Sun Apr 11 11:54:05 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 11 Apr 2021 18:54:05 +0700 Subject: [Slackbuilds-users] teamviewer no GUI Message-ID: Hi all I have been trying to find solution for a major issue for teamviewer which is GUI no longer starting. I have tried many solutions posted but so far, none are really working well. Anyone have a working solution for this issue? -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From chris.willing at linux.com Sun Apr 11 12:32:56 2021 From: chris.willing at linux.com (Christoph Willing) Date: Sun, 11 Apr 2021 22:32:56 +1000 Subject: [Slackbuilds-users] mosquitto download In-Reply-To: References: Message-ID: <62c648be-185d-257d-4c85-e29166dead33@linux.com> On 11/4/21 4:45 pm, B Watson wrote: > Currently getting "connection refused" from mosquitto.org. There's > another copy of the file here: > > http://ftp.osuosl.org/pub/gentoo/distfiles/mosquitto-2.0.10.tar.gz > > ...same md5sum. Might be worth updating the .info file? I did reply to this earlier (saying I'd have an update ready to go if the site didn't come back up in a few days) but I sent email from wrong (unsubscribed) account, so didn't make it here. Since then, the site is back up and DOWNLOAD link works fine again. chris From jvbernts at online.no Sun Apr 11 15:33:55 2021 From: jvbernts at online.no (Jostein Berntsen) Date: Sun, 11 Apr 2021 17:33:55 +0200 Subject: [Slackbuilds-users] teamviewer no GUI In-Reply-To: References: Message-ID: On 11.04.21,18:54, Willy Sudiarto Raharjo wrote: > Hi all > > I have been trying to find solution for a major issue for teamviewer > which is GUI no longer starting. I have tried many solutions posted but > so far, none are really working well. > > Anyone have a working solution for this issue? > > Have you checked the most recent version 15.16.8 and if this fixes the issue? https://download.teamviewer.com/download/linux/teamviewer-host_amd64.tar.xz Jostein From willysr at slackbuilds.org Sun Apr 11 15:57:15 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sun, 11 Apr 2021 22:57:15 +0700 Subject: [Slackbuilds-users] teamviewer no GUI In-Reply-To: References: Message-ID: <527deb05-8468-3b54-8e48-7acdc1fd33e9@slackbuilds.org> > Have you checked the most recent version 15.16.8 and if this fixes the > issue? > > https://download.teamviewer.com/download/linux/teamviewer-host_amd64.tar.xz Yeah, i tried that version, but still no luck :( -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From slackalaxy at gmail.com Mon Apr 12 06:44:28 2021 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 12 Apr 2021 09:44:28 +0300 Subject: [Slackbuilds-users] teamviewer no GUI In-Reply-To: <527deb05-8468-3b54-8e48-7acdc1fd33e9@slackbuilds.org> References: <527deb05-8468-3b54-8e48-7acdc1fd33e9@slackbuilds.org> Message-ID: Are you starting in init 3? Using startx? You may check this: https://community.teamviewer.com/English/discussion/comment/32597#Comment_32597 I had this issue: Init... CheckCPU: SSE2 support: yes Checking setup... Launching TeamViewer ... Launching TeamViewer GUI ... https://slackalaxy.com/2021/03/19/teamviewer-wont-start/ -petar On 11/04/2021, Willy Sudiarto Raharjo wrote: >> Have you checked the most recent version 15.16.8 and if this fixes the >> issue? >> >> https://download.teamviewer.com/download/linux/teamviewer-host_amd64.tar.xz > > Yeah, i tried that version, but still no luck :( > > > -- > Willy Sudiarto Raharjo > > From slackalaxy at gmail.com Mon Apr 12 06:47:06 2021 From: slackalaxy at gmail.com (Petar Petrov) Date: Mon, 12 Apr 2021 09:47:06 +0300 Subject: [Slackbuilds-users] teamviewer no GUI In-Reply-To: References: Message-ID: sorry, I did not write the actual solution in my previous email. Try starting X from runlevel 4 using a log in manager, such as LXDM -petar From willysr at slackbuilds.org Mon Apr 12 06:47:46 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 12 Apr 2021 13:47:46 +0700 Subject: [Slackbuilds-users] teamviewer no GUI In-Reply-To: References: <527deb05-8468-3b54-8e48-7acdc1fd33e9@slackbuilds.org> Message-ID: <6cd5a1c9-eb4d-7bcb-6ca7-04449d219b74@slackbuilds.org> > Are you starting in init 3? Using startx? You may check this: > > https://community.teamviewer.com/English/discussion/comment/32597#Comment_32597 > > I had this issue: > Init... > CheckCPU: SSE2 support: yes > Checking setup... > Launching TeamViewer ... > Launching TeamViewer GUI ... > > https://slackalaxy.com/2021/03/19/teamviewer-wont-start/ I tried with lightdm but still no available -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From sborg63 at disroot.org Mon Apr 12 12:21:38 2021 From: sborg63 at disroot.org (sborg63) Date: Mon, 12 Apr 2021 13:21:38 +0100 Subject: [Slackbuilds-users] Broken link for squidguard Message-ID: <20210412132138.6c265913@knotsUL> Maybe best to look for the latest version of Squidguard in debian repositories as based on below search results from last summer (when I was trying to set it up at my end on -current); then it was 1.6.0 at indicated sites. HTH, Rob > https://centosfaq.org/centos/squidguard-update-in-epel/: > Stephen John says: > > > October 1, 2019 at 7:29 am > > Here is the googling I found > > > > https://salsa.debian.org/joowie-guest/maintain_squidguard > > https://www.joonet.de/sources/squidguard/ > > Liam O'Toole says: > October 1, 2019 at 2:06 am > > [?] > > > > FWIW, the current release has squidguard 1.6 > > https://packages.debian.org/source/stable/squidguard > > Tru Huynh says: > October 1, 2019 at 2:00 am > > > https://tracker.debian.org/pkg/squidguard > > 1.6.0 as of today :D > > just my 2 cents === > Message: 4 > Date: Sat, 10 Apr 2021 20:54:04 +0200 > From: CRTS > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Broken link for squidguard > Message-ID: <20210410185404.GA1967 at rhea.titan.net> > Content-Type: text/plain; charset=us-ascii > > Ok, I am taking over. Just need to figure out why there is no official > version 1.3 anymore. I will contact the authors at "squidguard.org". > By the way, is "squid" itself still maintained? Stable version is 4.14 > and version on SBo is 4.13. From gerardo.zamudio at linux.com Tue Apr 13 04:19:15 2021 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Mon, 12 Apr 2021 23:19:15 -0500 Subject: [Slackbuilds-users] Abandoning worldofgoo Message-ID: <569209cbbb789d83f4f8b21839cc4f29@linux.com> Hi all I no longer play this game or have an interest in maintaining the SlackBuild. There is a new version out but I'm not sure if it's a demo. The current SlackBuild demo version is hosted by us. Anyone is free to take it. If no one is interested please remove it from the repository or remove my name from the MAINTAINER field. Regards Gerardo Zamudio From josiahb at gmail.com Wed Apr 14 02:24:04 2021 From: josiahb at gmail.com (Josiah Boothby) Date: Tue, 13 Apr 2021 19:24:04 -0700 Subject: [Slackbuilds-users] Slackbuilds up for adoption (e16, fmit, wavbreaker, skulpture, robotfindskitten) Message-ID: My slackbuilds are available to new homes for anyone who wants to tend to them. They are: desktop/e16 (no longer suits my needs) audio/fmit (this hasn't played nicely with my hardware for years and I'm tired of fighting it) audio/wavbreaker (I haven't used this in years, can be considered abandoned if nobody wants it) desktop/skulpture (this is for kde4, probably can be safely abandoned) games/robotfindskitten (I don't mind continuing to maintain this but I also don't mind releasing it if someone would like to adopt) I think that's all of them. ?Josiah -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvbernts at online.no Wed Apr 14 07:42:36 2021 From: jvbernts at online.no (Jostein Berntsen) Date: Wed, 14 Apr 2021 09:42:36 +0200 Subject: [Slackbuilds-users] teamviewer no GUI In-Reply-To: <527deb05-8468-3b54-8e48-7acdc1fd33e9@slackbuilds.org> References: <527deb05-8468-3b54-8e48-7acdc1fd33e9@slackbuilds.org> Message-ID: On 11.04.21,22:57, Willy Sudiarto Raharjo wrote: > > Have you checked the most recent version 15.16.8 and if this fixes the > > issue? > > > > https://download.teamviewer.com/download/linux/teamviewer-host_amd64.tar.xz > > Yeah, i tried that version, but still no luck :( > > > -- > Willy Sudiarto Raharjo > Have you tried reverting back to v.12? Seems like some other distros have problem with recent versions as well. https://community.teamviewer.com/English/discussion/57795/teamviewer-14-not-working-on-ubuntu-14-04-64 Jostein > _______________________________________________ > 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 andrew.david.strong at gmail.com Wed Apr 14 08:01:26 2021 From: andrew.david.strong at gmail.com (andrew) Date: Wed, 14 Apr 2021 18:01:26 +1000 Subject: [Slackbuilds-users] Slackbuilds up for adoption (e16, fmit, wavbreaker, skulpture, robotfindskitten) In-Reply-To: References: Message-ID: Hi Josiah, I would be more than happy to take up wavbreaker, I love working with media files and I see wavbreaker has a newer version from 2019. To be perfectly honest an update would wait for 15.0... Andrew Strong On Tue, Apr 13, 2021 at 07:24:04PM -0700, Josiah Boothby wrote: > My slackbuilds are available to new homes for anyone who wants to tend to them. > They are: > > desktop/e16 (no longer suits my needs) > > audio/fmit (this hasn't played nicely with my hardware for years and I'm tired > of fighting it) > > audio/wavbreaker (I haven't used this in years, can be considered abandoned if > nobody wants it) > > desktop/skulpture (this is for kde4, probably can be safely abandoned) > > games/robotfindskitten (I don't mind continuing to maintain this but I also > don't mind releasing it if someone would like to adopt) > > I think that's all of them. > > ?Josiah > _______________________________________________ > 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/ > -- You think that's air you're breathing now? From 1.41421 at gmail.com Thu Apr 15 12:52:23 2021 From: 1.41421 at gmail.com (Luveh Keraph) Date: Thu, 15 Apr 2021 06:52:23 -0600 Subject: [Slackbuilds-users] Pari version obsolete Message-ID: The version of Pari (2.11.2) that the Slackbuilds script attempts to download is not found in the Pari repository any more - versions 2.13 and 2.13.1 alone seem to be present there. -------------- next part -------------- An HTML attachment was scrubbed... URL: From matteo.bernardini at gmail.com Thu Apr 15 13:16:40 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Thu, 15 Apr 2021 15:16:40 +0200 Subject: [Slackbuilds-users] Pari version obsolete In-Reply-To: References: Message-ID: https://pari.math.u-bordeaux.fr/pub/pari/OLD/2.11/pari-2.11.2.tar.gz I'll update the download link. Matteo Il giorno gio 15 apr 2021 alle ore 14:52 Luveh Keraph <1.41421 at gmail.com> ha scritto: > > The version of Pari (2.11.2) that the Slackbuilds script attempts to download is not found in the Pari repository any more - versions 2.13 and 2.13.1 alone seem to be present there. > _______________________________________________ > 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 dave at slackbuilds.org Thu Apr 15 13:23:34 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Thu, 15 Apr 2021 14:23:34 +0100 Subject: [Slackbuilds-users] Pari version obsolete In-Reply-To: References: Message-ID: <20210415132334.GP5008@localhost> I've just tested 2.13.1 and it builds OK, but the man pages are in /usr/man instead of /usr/man/man1. Matteo Bernardini put forth the proposition: > https://pari.math.u-bordeaux.fr/pub/pari/OLD/2.11/pari-2.11.2.tar.gz > I'll update the download link. > Matteo > Il giorno gio 15 apr 2021 alle ore 14:52 Luveh Keraph > <1.41421 at gmail.com> ha scritto: > > > > The version of Pari (2.11.2) that the Slackbuilds script attempts to download is not found in the Pari repository any more - versions 2.13 and 2.13.1 alone seem to be present there. > > -- Dave From bocke at slackware-srbija.org Thu Apr 15 20:09:10 2021 From: bocke at slackware-srbija.org (Bojan Popovic) Date: Thu, 15 Apr 2021 22:09:10 +0200 Subject: [Slackbuilds-users] Several packages up for adoption Message-ID: <81e9145c-db53-4015-3d3e-52ce2ef1320f@slackware-srbija.org> Hi. I'm dropping the following packages: bochs, py3cairo, compface and gvolwheel. Rationale: bochs - I haven't used it in a few years. Nowadays I mostly use Qemu and Virtualbox. py3cairo - I tought I already dropped this a year or two ago, but I see now I am still the maintainer. I'm not interested in maintaining it anymore. compface - This was an optional dependency for Claws Mail, but I have since gone back to Thunderbird. gvolwheel - Pulseaudio plugin in Xfce works good enough nowadays. Haven't used it in couple of years. Cheers, Bojan. From lenardrspencer at gmail.com Thu Apr 15 21:08:22 2021 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Thu, 15 Apr 2021 17:08:22 -0400 Subject: [Slackbuilds-users] Several packages up for adoption In-Reply-To: <81e9145c-db53-4015-3d3e-52ce2ef1320f@slackware-srbija.org> References: <81e9145c-db53-4015-3d3e-52ce2ef1320f@slackware-srbija.org> Message-ID: I'll take py3cairo if nobody else wants it. On Thu, Apr 15, 2021, 16:10 Bojan Popovic wrote: > Hi. > > I'm dropping the following packages: bochs, py3cairo, compface and > gvolwheel. > > Rationale: > > bochs - I haven't used it in a few years. Nowadays I mostly use Qemu and > Virtualbox. > > py3cairo - I tought I already dropped this a year or two ago, but I see > now I am still the maintainer. I'm not interested in maintaining it > anymore. > > compface - This was an optional dependency for Claws Mail, but I have > since gone back to Thunderbird. > > gvolwheel - Pulseaudio plugin in Xfce works good enough nowadays. > Haven't used it in couple of years. > > > Cheers, > > Bojan. > > _______________________________________________ > 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 Fri Apr 16 02:33:41 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 16 Apr 2021 09:33:41 +0700 Subject: [Slackbuilds-users] teamviewer no GUI In-Reply-To: References: <527deb05-8468-3b54-8e48-7acdc1fd33e9@slackbuilds.org> Message-ID: <63f79eb5-3a45-f027-6046-073497ecc83b@slackbuilds.org> > Have you tried reverting back to v.12? Seems like some other distros > have problem with recent versions as well. > > https://community.teamviewer.com/English/discussion/57795/teamviewer-14-not-working-on-ubuntu-14-04-64 As far as i know, older version like Teamviewer 12 will not be able to connect to other machines that uses newer version -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Fri Apr 16 10:27:07 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 16 Apr 2021 17:27:07 +0700 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository Message-ID: Hi everyone As you may have heard that Patrick has declared -current into Beta status, which means it's time for us to start working on our repository which will lead to 15.0 repository in the future. It might take some time until all scripts are checked to work with -current because of the big changes happening during the development cycle between 14.2 and -current. So here is what we will do after this weekend public update: 1. We will close submission form for 14.2. 2. Merge Ponce's current repository to master 3. Checking all scripts and making sure it's working with -current Due to the nature of the -current which is a moving target, we will focus on the big and high-impacting scripts first, especially the Qt5 and Python2/3 transition. For maintainers who have write access to SBo server or usually push updates through pull/merge requests via github/gitlab, please make sure to test your update against -current environment rather than 14.2 after this weekend's public update. As always, we always welcome any bug reports either on this list or in LQ thread (https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/) If the development cycle is smooth as planned, we should have 15.0 ready by the time Slackware 15.0 is released by Patrick. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From lenardrspencer at gmail.com Fri Apr 16 13:02:08 2021 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Fri, 16 Apr 2021 09:02:08 -0400 Subject: [Slackbuilds-users] Several packages up for adoption In-Reply-To: References: <81e9145c-db53-4015-3d3e-52ce2ef1320f@slackware-srbija.org> Message-ID: I guess I spoke a little too soon. 14.2 submissions are closed after this weekend and the pycairo in -current/15.0 already supports python3, so it is now a moot point. On Thu, Apr 15, 2021 at 5:08 PM Lenard Spencer wrote: > I'll take py3cairo if nobody else wants it. > > > On Thu, Apr 15, 2021, 16:10 Bojan Popovic > wrote: > >> Hi. >> >> I'm dropping the following packages: bochs, py3cairo, compface and >> gvolwheel. >> >> Rationale: >> >> bochs - I haven't used it in a few years. Nowadays I mostly use Qemu and >> Virtualbox. >> >> py3cairo - I tought I already dropped this a year or two ago, but I see >> now I am still the maintainer. I'm not interested in maintaining it >> anymore. >> >> compface - This was an optional dependency for Claws Mail, but I have >> since gone back to Thunderbird. >> >> gvolwheel - Pulseaudio plugin in Xfce works good enough nowadays. >> Haven't used it in couple of years. >> >> >> Cheers, >> >> Bojan. >> >> _______________________________________________ >> SlackBuilds-users mailing list >> SlackBuilds-users at slackbuilds.org >> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users >> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ >> FAQ - https://slackbuilds.org/faq/ >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernando.lopezjr at gmail.com Fri Apr 16 17:20:37 2021 From: fernando.lopezjr at gmail.com (Fernando Lopez) Date: Fri, 16 Apr 2021 11:20:37 -0600 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository In-Reply-To: References: Message-ID: finally. thanks! On Fri, Apr 16, 2021 at 4:27 AM Willy Sudiarto Raharjo < willysr at slackbuilds.org> wrote: > Hi everyone > > As you may have heard that Patrick has declared -current into Beta > status, which means it's time for us to start working on our repository > which will lead to 15.0 repository in the future. It might take some > time until all scripts are checked to work with -current because of the > big changes happening during the development cycle between 14.2 and > -current. > > So here is what we will do after this weekend public update: > 1. We will close submission form for 14.2. > 2. Merge Ponce's current repository to master > 3. Checking all scripts and making sure it's working with -current > > Due to the nature of the -current which is a moving target, we will > focus on the big and high-impacting scripts first, especially the Qt5 > and Python2/3 transition. > > For maintainers who have write access to SBo server or usually push > updates through pull/merge requests via github/gitlab, please make sure > to test your update against -current environment rather than 14.2 after > this weekend's public update. > > As always, we always welcome any bug reports either on this list or in > LQ thread > ( > https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ > ) > > If the development cycle is smooth as planned, we should have 15.0 ready > by the time Slackware 15.0 is released by Patrick. > > -- > 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/ > > -- ------------ Regards, Fernando Lopez Jr. -------------- next part -------------- An HTML attachment was scrubbed... URL: From kingbeowulf at gmail.com Fri Apr 16 18:52:14 2021 From: kingbeowulf at gmail.com (King Beowulf) Date: Fri, 16 Apr 2021 11:52:14 -0700 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository In-Reply-To: References: Message-ID: On 4/16/21 3:27 AM, Willy Sudiarto Raharjo wrote: > Hi everyone > > As you may have heard that Patrick has declared -current into Beta > status, which means it's time for us to start working on our repository > which will lead to 15.0 repository in the future. It might take some > time until all scripts are checked to work with -current because of the > big changes happening during the development cycle between 14.2 and > -current. > > So here is what we will do after this weekend public update: > 1. We will close submission form for 14.2. > 2. Merge Ponce's current repository to master > 3. Checking all scripts and making sure it's working with -current > > Nice. I've been running a local branch here for Current for a while. I look forward to cleaning that up to push. Many of my SBo submissions are now stuck at old versions (as previously reported) due to 14.2 age. Fun as well that a number of them are now in Slackware! -Ed -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 203 bytes Desc: OpenPGP digital signature URL: From sborg63 at disroot.org Fri Apr 16 19:27:23 2021 From: sborg63 at disroot.org (sborg63) Date: Fri, 16 Apr 2021 20:27:23 +0100 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository SlackBuilds-users Digest, Vol 180, Issue 12 In-Reply-To: References: Message-ID: <20210416202723.5279b7ac@knotsUL> Hi Willy, When would it be possible to submit scripts for packages that only run on current and that should replace outdated, no-longer maintained (e.g python2-only) packages that are in the repository for 14.2 atm? For example I maintain PDF-shuffler which should be dropped. This I would like to replace in the 15.0 repository with PDFarranger plus Pike PDF, which work fine for me on current (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). PikePDF relies on a version of qpdf not available in stock 14.2. Good luck with the work ahead... Rob > > Message: 2 > Date: Fri, 16 Apr 2021 17:27:07 +0700 > From: Willy Sudiarto Raharjo > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository > Message-ID: > Content-Type: text/plain; charset="utf-8" From dave at slackbuilds.org Fri Apr 16 19:32:00 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Fri, 16 Apr 2021 20:32:00 +0100 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository SlackBuilds-users Digest, Vol 180, Issue 12 In-Reply-To: <20210416202723.5279b7ac@knotsUL> References: <20210416202723.5279b7ac@knotsUL> Message-ID: <20210416193200.GS5008@localhost> Hi Rob, When submissions open again, and we will be in 15.0, which would be the correct time. Dave Slackbuilds Users put forth the proposition: > Hi Willy, > When would it be possible to submit scripts for packages that only run > on current and that should replace outdated, no-longer maintained > (e.g python2-only) packages that are in the repository for 14.2 atm? > For example I maintain PDF-shuffler which should be dropped. This I > would like to replace in the 15.0 repository with PDFarranger plus Pike > PDF, which work fine for me on current > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > PikePDF relies on a version of qpdf not available in stock 14.2. > Good luck with the work ahead... > Rob > > > > Message: 2 > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > From: Willy Sudiarto Raharjo > > To: "SlackBuilds.org Users List" > > Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository > > Message-ID: > > Content-Type: text/plain; charset="utf-8" -- Dave From willysr at slackbuilds.org Sat Apr 17 00:34:35 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Apr 2021 07:34:35 +0700 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository SlackBuilds-users Digest, Vol 180, Issue 12 In-Reply-To: <20210416193200.GS5008@localhost> References: <20210416202723.5279b7ac@knotsUL> <20210416193200.GS5008@localhost> Message-ID: > When submissions open again, and we will be in 15.0, which would be > the correct time. > > Dave > >> Hi Willy, >> When would it be possible to submit scripts for packages that only run >> on current and that should replace outdated, no-longer maintained >> (e.g python2-only) packages that are in the repository for 14.2 atm? >> For example I maintain PDF-shuffler which should be dropped. This I >> would like to replace in the 15.0 repository with PDFarranger plus Pike >> PDF, which work fine for me on current >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). >> PikePDF relies on a version of qpdf not available in stock 14.2. >> Good luck with the work ahead... Hi Rob Yes, i agree with Dave once 15.0 repo is ready, you can submit new scripts for now, we will focus on getting 15.0 ready first as base for future new scripts -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From lenardrspencer at gmail.com Sat Apr 17 02:26:58 2021 From: lenardrspencer at gmail.com (Lenard Spencer) Date: Fri, 16 Apr 2021 22:26:58 -0400 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository SlackBuilds-users Digest, Vol 180, Issue 12 In-Reply-To: References: <20210416202723.5279b7ac@knotsUL> <20210416193200.GS5008@localhost> Message-ID: I have several scripts that had to be updated for 15.0. Should I just go ahead anc zip up a tarball and send it directly to Matteo? Thanks. On Fri, Apr 16, 2021, 20:34 Willy Sudiarto Raharjo wrote: > > When submissions open again, and we will be in 15.0, which would be > > the correct time. > > > > Dave > > > >> Hi Willy, > >> When would it be possible to submit scripts for packages that only run > >> on current and that should replace outdated, no-longer maintained > >> (e.g python2-only) packages that are in the repository for 14.2 atm? > >> For example I maintain PDF-shuffler which should be dropped. This I > >> would like to replace in the 15.0 repository with PDFarranger plus Pike > >> PDF, which work fine for me on current > >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > >> PikePDF relies on a version of qpdf not available in stock 14.2. > >> Good luck with the work ahead... > > Hi Rob > > Yes, i agree with Dave > once 15.0 repo is ready, you can submit new scripts > for now, we will focus on getting 15.0 ready first as base for future > new scripts > > > -- > Willy Sudiarto Raharjo > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Apr 17 02:28:09 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Apr 2021 09:28:09 +0700 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository SlackBuilds-users Digest, Vol 180, Issue 12 In-Reply-To: References: <20210416202723.5279b7ac@knotsUL> <20210416193200.GS5008@localhost> Message-ID: <61e3dbb1-373f-96ef-27ed-4b016c4dd6dc@slackbuilds.org> > I have several scripts that had to be updated for 15.0. Should I just go > ahead anc zip up a tarball and send it directly to Matteo? Thanks. Please wait until i pushed public update this weekend and you can push it to your normal branch -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Apr 17 05:13:05 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 17 Apr 2021 12:13:05 +0700 Subject: [Slackbuilds-users] Updates - 20210417.1 Message-ID: <58c48067-a298-b3a8-365c-82e2a9d64606@slackbuilds.org> Hi all as previously mentioned, this will be the last update from normal submission for 14.2 and from now onwards, we will be focusing on testing scripts against -current environment. Sat Apr 17 04:48:35 UTC 2021 academic/cblas: Updated for version 3.9.1. academic/lapacke: Updated for version 3.9.1. academic/octave: Updated for version 6.2.0. academic/pari: Updated for version 2.13.1. academic/sundials: Fix download link. audio/mixxx: Use protobuf3 as a dependency. audio/nas: Force single make job. desktop/dmenu2: Removed (unmaintained upstream). desktop/lxpanel: Updated for version 0.10.1. desktop/screenkey: Updated for version 1.4. desktop/xss-lock: Added (using external locker as X screensaver) development/Sphinx: Updated for version 3.5.4. development/eovim: Updated for version 0.2.0. development/google-go-lang: Updated for version 1.16.3. development/jupyter-ipykernel: Updated for version 5.5.3. development/lepton-eda: Updated for version 1.9.14. development/nim: Updated for version 1.4.6. development/nodejs: Fix tarball extension. development/postman: Updated for version 8.2.1 development/tea: updated for version 60.0.3 games/armagetronad: Updated for version 0.2.9.1.0. gis/osm2pgsql: Updated for version 1.4.2. gis/rasterio: Updated for version 1.2.2. graphics/lilypond: Updated for version 2.22.0. graphics/vuescan: Updated MD5SUMs. libraries/blas: Updated for version 3.9.1. libraries/iddawc: Compress man pages. libraries/iddawc: updated for version 0.9.9 libraries/lapack: Updated for version 3.9.1. libraries/libfm-extra: Updated for version 1.3.2. libraries/libfm: Updated for version 1.3.2. libraries/libxkbcommon: Updated for version 1.2.1. libraries/libxlsxwriter: Updated for version 1.0.2. libraries/rhonabwy: updated for version 0.9.999 libraries/skalibs: Updated for version 2.10.0.3. libraries/xblas: Use a versioned tarball. multimedia/gnash: Updated for version 0.8.11dev_20190130. multimedia/plexmediaserver: Updated for v 1.22.2.4282_a97b03fad. network/basilisk-bin: Updated for version 2021.03.17. network/brave-browser: Updated for version 1.23.71. network/hostapd: Patched for P2P/wpa_supplicant vulnerabilities. network/keepalived: Updated for version 2.2.2. network/nweb: Added (tiny web server in C). network/palemoon-bin: Updated for version 29.1.1. network/palemoon: Updated for version 29.1.1. network/qutebrowser-tox: Updated for version 2.2.0. network/qutebrowser: Updated for version 2.2.0. network/signal-desktop: Updated for version 5.0.0. network/spamassassin: Updated for version 3.4.6. network/unbound: Updated for version 1.13.1. office/calcurse: Updated for version 4.7.1. office/calibre-bin: Updated for version 5.15.0. perl/perl-Math-GMPz: Updated for version 0.50. perl/perl-Sidef: Updated for version 3.98. python/decorator: Updated for version 5.0.6. python/decorator: Updated for version 5.0.7. python/internetarchive: Updated for version 2.0.1. python/python-neovim: Updated for version 0.4.3. python/python-prometheus_client: Updated for version 0.10.1. python/python3-aiohttp: Updated for version 3.7.4.post0. python/python3-astroid: Updated for version 2.5.3. python/python3-ptyprocess: Updated for version 0.7.0. python/python3-seaborn: Updated for version 0.11.1. python/scikit-learn: Updated for version 0.24.1. python/typed_ast: Updated for version 1.4.3. system/android-file-transfer: Updated for version 4.2. system/ansible: Updated for version 2.9.20. system/clamav: Fix permissions to allow users to run clamscan. system/execline: Updated for version 2.8.0.1. system/lxtask: Updated for version 0.1.10. system/lxterminal: Updated for version 0.4.0. system/netdata: Updated for version 1.29.3. system/newLd: Update script. system/pax: Updated for version 20201030 (switch to MirBSD pax). system/pcmanfm: Updated for version 1.3.2. system/qdirstat: Updated for version 1.7.1. system/s6-linux-init: Updated for version 1.0.6.2. system/s6-rc: Updated for version 0.5.2.2. system/s6: Updated for version 2.10.0.3. system/telegraf: Updated for version 1.18.1. system/wine-staging: Updated for version 6.5. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From belka at caraus.de Sat Apr 17 06:18:37 2021 From: belka at caraus.de (Eugen Wissner) Date: Sat, 17 Apr 2021 08:18:37 +0200 Subject: [Slackbuilds-users] My -current scripts Message-ID: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> Hi, I would like to ask to remove the following SlackBuilds: - gcc-d: Part of Slackware current - gkrellm-volume: The home page and download link are dead, I'm not sure if this software still exists - oniguruma: In Slackware current - opendbx: It builds on current, but opendbx doesn't seem to be active, the last release was in 2012 and nothing depends on it. - tanya: It is my own development; I wasn't working on it a lot in the last time and I'm not sure I will. Anyway it is not the best way to build D dependencies. I don't use the following SlackBuilds anymore. I will maintain them if someone needs them, but it would be great if they can be removed or find a new maintainer who can update them on a regular basis: - ioncube-loader: It probably builds on current, but it won't work since it should be updated for PHP 7. - psi - universal-ctags: Language servers replaced this one in the most cases The following scripts work on current: - composer - d-tools - dmd I'll try to update php-apcu and hhvm next week. On my production server with Slackware current I have modified versions of the following scripts: - colm - dovecot-pigeonhole - hyperscan - php-pgsql - ragel The reason I have them is that I couldn't build them at some point. Maybe I'm just ignorant and some problems where already fixed. Just for the case some of the maintainers struggle with an update, clone git://caraus.tech/pub/slackbuilder.git and look into private/ directory. Here is the web view: https://www.caraus.tech/projects/pub-slackbuilds/repository/26/revisions/master/show/private I have dovecot-pgsql and postfix-pgsql there if someone uses dovecot and postfix with PostgreSQL since the SBo's scripts support PostgreSQL, but the slackware's ones don't. Eugen From dave at slackbuilds.org Sat Apr 17 06:23:14 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 17 Apr 2021 07:23:14 +0100 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> Message-ID: <20210417062314.GV5008@localhost> Hi I can take psi if nobody else wants it. I maintain psi-plus, so I could do both. Dave Eugen Wissner put forth the proposition: > Hi, > I would like to ask to remove the following SlackBuilds: > - gcc-d: Part of Slackware current > - gkrellm-volume: The home page and download link are dead, I'm not sure > if this software still exists > - oniguruma: In Slackware current > - opendbx: It builds on current, but opendbx doesn't seem to be active, > the last release was in 2012 and nothing depends on it. > - tanya: It is my own development; I wasn't working on it a lot in the > last time and I'm not sure I will. Anyway it is not the best way to > build D dependencies. > I don't use the following SlackBuilds anymore. I will maintain them if > someone needs them, but it would be great if they can be removed or find > a new maintainer who can update them on a regular basis: > - ioncube-loader: It probably builds on current, but it won't work > since it should be updated for PHP 7. > - psi > - universal-ctags: Language servers replaced this one in the most cases > The following scripts work on current: > - composer > - d-tools > - dmd > I'll try to update php-apcu and hhvm next week. > On my production server with Slackware current I have modified versions > of the following scripts: > - colm > - dovecot-pigeonhole > - hyperscan > - php-pgsql > - ragel > The reason I have them is that I couldn't build them at some point. > Maybe I'm just ignorant and some problems where already fixed. Just for > the case some of the maintainers struggle with an update, clone > git://caraus.tech/pub/slackbuilder.git and look into private/ directory. > Here is the web view: > https://www.caraus.tech/projects/pub-slackbuilds/repository/26/revisions/master/show/private > I have dovecot-pgsql and postfix-pgsql there if someone uses dovecot and > postfix with PostgreSQL since the SBo's scripts support PostgreSQL, but > the slackware's ones don't. > Eugen -- Dave From matteo.bernardini at gmail.com Sat Apr 17 08:12:11 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 17 Apr 2021 10:12:11 +0200 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> Message-ID: Il giorno sab 17 apr 2021 alle ore 08:18 Eugen Wissner ha scritto: > > Hi, > > I would like to ask to remove the following SlackBuilds: > > - gcc-d: Part of Slackware current > - gkrellm-volume: The home page and download link are dead, I'm not sure > if this software still exists > - oniguruma: In Slackware current > - opendbx: It builds on current, but opendbx doesn't seem to be active, > the last release was in 2012 and nothing depends on it. > - tanya: It is my own development; I wasn't working on it a lot in the > last time and I'm not sure I will. Anyway it is not the best way to > build D dependencies. I've pushed these in my branch. Matteo From sb at rbn.im Sat Apr 17 11:04:13 2021 From: sb at rbn.im (Ruben Schuller) Date: Sat, 17 Apr 2021 13:04:13 +0200 Subject: [Slackbuilds-users] dillo with SSL on current Message-ID: <20210417130413.45ecac8c@kirsche.kuchen> hi, as we are approaching 15.0 and are fixing the slackbuilds now: i have recently fiddled with installing dillo with SSL on current. i've had to apply a patch [1] from gentoo, run "autoreconf -if" and compile with "-fcommon". see the attached patch for the slackbuild. the gentoo patch is assumed to be located in $CWD. cheers ruben [1] https://gitweb.gentoo.org/repo/gentoo.git/plain/www-client/dillo/files/dillo-3.0.5-openssl-1.1.patch?id=8e07d499b9d5acf45597936fef4370c0172d3247 -------------- next part -------------- A non-text attachment was scrubbed... Name: dillo-ssl.patch Type: text/x-patch Size: 621 bytes Desc: not available URL: From alik at ejik.org Sat Apr 17 12:02:04 2021 From: alik at ejik.org (Alexander Verbovetsky) Date: Sat, 17 Apr 2021 15:02:04 +0300 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository In-Reply-To: References: Message-ID: Hello, I'd like to ask to remove r2e. We have rss2email, which is the modern version of this program. Best regards, Alexander From dave at slackbuilds.org Sat Apr 17 12:54:05 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 17 Apr 2021 13:54:05 +0100 Subject: [Slackbuilds-users] Regarding Fixes and Patches for 15.0 Message-ID: <20210417125405.GA18892@localhost> Hello all, May I request that people hold on to their 15.0 patches and fixes for now, rather than posting them to the list? They really need to go through the usual submission system once we reopen it, so that they get added to the database properly, or via git if you use that method. Thanks! -- Dave From matteo.bernardini at gmail.com Sat Apr 17 13:51:33 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 17 Apr 2021 15:51:33 +0200 Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository In-Reply-To: References: Message-ID: pushed in my branch. Il giorno sab 17 apr 2021 alle ore 14:02 Alexander Verbovetsky ha scritto: > > Hello, > > I'd like to ask to remove r2e. > > We have rss2email, which is the modern version of this program. From jeffersoncarneiro at slackjeff.com.br Sat Apr 17 14:00:27 2021 From: jeffersoncarneiro at slackjeff.com.br (Jefferson Carneiro) Date: Sat, 17 Apr 2021 11:00:27 -0300 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 180, Issue 13 In-Reply-To: References: Message-ID: hmmm, repo 15 ;) I am happy to read this, it means that 15 comming \o On Sat, Apr 17, 2021 at 05:13:20AM +0000, 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: Development Cycle Towards 15.0 Repository > SlackBuilds-users Digest, Vol 180, Issue 12 (sborg63) > 2. Re: Development Cycle Towards 15.0 Repository > SlackBuilds-users Digest, Vol 180, Issue 12 (Dave Woodfall) > 3. Re: Development Cycle Towards 15.0 Repository > SlackBuilds-users Digest, Vol 180, Issue 12 (Willy Sudiarto Raharjo) > 4. Re: Development Cycle Towards 15.0 Repository > SlackBuilds-users Digest, Vol 180, Issue 12 (Lenard Spencer) > 5. Re: Development Cycle Towards 15.0 Repository > SlackBuilds-users Digest, Vol 180, Issue 12 (Willy Sudiarto Raharjo) > 6. Updates - 20210417.1 (Willy Sudiarto Raharjo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 16 Apr 2021 20:27:23 +0100 > From: sborg63 > To: "SlackBuilds.org Users List" , > > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <20210416202723.5279b7ac at knotsUL> > Content-Type: text/plain; charset=US-ASCII > > Hi Willy, > > When would it be possible to submit scripts for packages that only run > on current and that should replace outdated, no-longer maintained > (e.g python2-only) packages that are in the repository for 14.2 atm? > > For example I maintain PDF-shuffler which should be dropped. This I > would like to replace in the 15.0 repository with PDFarranger plus Pike > PDF, which work fine for me on current > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > PikePDF relies on a version of qpdf not available in stock 14.2. > > Good luck with the work ahead... > > Rob > > > > Message: 2 > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > From: Willy Sudiarto Raharjo > > To: "SlackBuilds.org Users List" > > Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository > > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > > ------------------------------ > > Message: 2 > Date: Fri, 16 Apr 2021 20:32:00 +0100 > From: Dave Woodfall > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <20210416193200.GS5008 at localhost> > Content-Type: text/plain; charset=utf-8 > > Hi Rob, > > When submissions open again, and we will be in 15.0, which would be > the correct time. > > Dave > > Slackbuilds Users put forth the proposition: > > Hi Willy, > > When would it be possible to submit scripts for packages that only run > > on current and that should replace outdated, no-longer maintained > > (e.g python2-only) packages that are in the repository for 14.2 atm? > > For example I maintain PDF-shuffler which should be dropped. This I > > would like to replace in the 15.0 repository with PDFarranger plus Pike > > PDF, which work fine for me on current > > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > > PikePDF relies on a version of qpdf not available in stock 14.2. > > Good luck with the work ahead... > > Rob > > > > > > Message: 2 > > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > > From: Willy Sudiarto Raharjo > > > To: "SlackBuilds.org Users List" > > > Subject: [Slackbuilds-users] Development Cycle Towards 15.0 Repository > > > Message-ID: > > > Content-Type: text/plain; charset="utf-8" > > -- > Dave > > > ------------------------------ > > Message: 3 > Date: Sat, 17 Apr 2021 07:34:35 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: > Content-Type: text/plain; charset="utf-8" > > > When submissions open again, and we will be in 15.0, which would be > > the correct time. > > > > Dave > > > >> Hi Willy, > >> When would it be possible to submit scripts for packages that only run > >> on current and that should replace outdated, no-longer maintained > >> (e.g python2-only) packages that are in the repository for 14.2 atm? > >> For example I maintain PDF-shuffler which should be dropped. This I > >> would like to replace in the 15.0 repository with PDFarranger plus Pike > >> PDF, which work fine for me on current > >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > >> PikePDF relies on a version of qpdf not available in stock 14.2. > >> Good luck with the work ahead... > > Hi Rob > > Yes, i agree with Dave > once 15.0 repo is ready, you can submit new scripts > for now, we will focus on getting 15.0 ready first as base for future > new scripts > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 840 bytes > Desc: OpenPGP digital signature > URL: > > ------------------------------ > > Message: 4 > Date: Fri, 16 Apr 2021 22:26:58 -0400 > From: Lenard Spencer > To: "SlackBuilds.org Users List" > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: > > Content-Type: text/plain; charset="utf-8" > > I have several scripts that had to be updated for 15.0. Should I just go > ahead anc zip up a tarball and send it directly to Matteo? Thanks. > > > On Fri, Apr 16, 2021, 20:34 Willy Sudiarto Raharjo > wrote: > > > > When submissions open again, and we will be in 15.0, which would be > > > the correct time. > > > > > > Dave > > > > > >> Hi Willy, > > >> When would it be possible to submit scripts for packages that only run > > >> on current and that should replace outdated, no-longer maintained > > >> (e.g python2-only) packages that are in the repository for 14.2 atm? > > >> For example I maintain PDF-shuffler which should be dropped. This I > > >> would like to replace in the 15.0 repository with PDFarranger plus Pike > > >> PDF, which work fine for me on current > > >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > > >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > > >> PikePDF relies on a version of qpdf not available in stock 14.2. > > >> Good luck with the work ahead... > > > > Hi Rob > > > > Yes, i agree with Dave > > once 15.0 repo is ready, you can submit new scripts > > for now, we will focus on getting 15.0 ready first as base for future > > new scripts > > > > > > -- > > Willy Sudiarto Raharjo > > > > _______________________________________________ > > SlackBuilds-users mailing list > > SlackBuilds-users at slackbuilds.org > > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > > FAQ - https://slackbuilds.org/faq/ > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: > > ------------------------------ > > Message: 5 > Date: Sat, 17 Apr 2021 09:28:09 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <61e3dbb1-373f-96ef-27ed-4b016c4dd6dc at slackbuilds.org> > Content-Type: text/plain; charset="utf-8" > > > I have several scripts that had to be updated for 15.0. Should I just go > > ahead anc zip up a tarball and send it directly to Matteo? Thanks. > > Please wait until i pushed public update this weekend and you can push > it to your normal branch > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 840 bytes > Desc: OpenPGP digital signature > URL: > > ------------------------------ > > Message: 6 > Date: Sat, 17 Apr 2021 12:13:05 +0700 > From: Willy Sudiarto Raharjo > To: "SlackBuilds.org Users List" > Subject: [Slackbuilds-users] Updates - 20210417.1 > Message-ID: <58c48067-a298-b3a8-365c-82e2a9d64606 at slackbuilds.org> > Content-Type: text/plain; charset="utf-8" > > Hi all > > as previously mentioned, this will be the last update from normal > submission for 14.2 and from now onwards, we will be focusing on testing > scripts against -current environment. > > > Sat Apr 17 04:48:35 UTC 2021 > academic/cblas: Updated for version 3.9.1. > academic/lapacke: Updated for version 3.9.1. > academic/octave: Updated for version 6.2.0. > academic/pari: Updated for version 2.13.1. > academic/sundials: Fix download link. > audio/mixxx: Use protobuf3 as a dependency. > audio/nas: Force single make job. > desktop/dmenu2: Removed (unmaintained upstream). > desktop/lxpanel: Updated for version 0.10.1. > desktop/screenkey: Updated for version 1.4. > desktop/xss-lock: Added (using external locker as X screensaver) > development/Sphinx: Updated for version 3.5.4. > development/eovim: Updated for version 0.2.0. > development/google-go-lang: Updated for version 1.16.3. > development/jupyter-ipykernel: Updated for version 5.5.3. > development/lepton-eda: Updated for version 1.9.14. > development/nim: Updated for version 1.4.6. > development/nodejs: Fix tarball extension. > development/postman: Updated for version 8.2.1 > development/tea: updated for version 60.0.3 > games/armagetronad: Updated for version 0.2.9.1.0. > gis/osm2pgsql: Updated for version 1.4.2. > gis/rasterio: Updated for version 1.2.2. > graphics/lilypond: Updated for version 2.22.0. > graphics/vuescan: Updated MD5SUMs. > libraries/blas: Updated for version 3.9.1. > libraries/iddawc: Compress man pages. > libraries/iddawc: updated for version 0.9.9 > libraries/lapack: Updated for version 3.9.1. > libraries/libfm-extra: Updated for version 1.3.2. > libraries/libfm: Updated for version 1.3.2. > libraries/libxkbcommon: Updated for version 1.2.1. > libraries/libxlsxwriter: Updated for version 1.0.2. > libraries/rhonabwy: updated for version 0.9.999 > libraries/skalibs: Updated for version 2.10.0.3. > libraries/xblas: Use a versioned tarball. > multimedia/gnash: Updated for version 0.8.11dev_20190130. > multimedia/plexmediaserver: Updated for v 1.22.2.4282_a97b03fad. > network/basilisk-bin: Updated for version 2021.03.17. > network/brave-browser: Updated for version 1.23.71. > network/hostapd: Patched for P2P/wpa_supplicant vulnerabilities. > network/keepalived: Updated for version 2.2.2. > network/nweb: Added (tiny web server in C). > network/palemoon-bin: Updated for version 29.1.1. > network/palemoon: Updated for version 29.1.1. > network/qutebrowser-tox: Updated for version 2.2.0. > network/qutebrowser: Updated for version 2.2.0. > network/signal-desktop: Updated for version 5.0.0. > network/spamassassin: Updated for version 3.4.6. > network/unbound: Updated for version 1.13.1. > office/calcurse: Updated for version 4.7.1. > office/calibre-bin: Updated for version 5.15.0. > perl/perl-Math-GMPz: Updated for version 0.50. > perl/perl-Sidef: Updated for version 3.98. > python/decorator: Updated for version 5.0.6. > python/decorator: Updated for version 5.0.7. > python/internetarchive: Updated for version 2.0.1. > python/python-neovim: Updated for version 0.4.3. > python/python-prometheus_client: Updated for version 0.10.1. > python/python3-aiohttp: Updated for version 3.7.4.post0. > python/python3-astroid: Updated for version 2.5.3. > python/python3-ptyprocess: Updated for version 0.7.0. > python/python3-seaborn: Updated for version 0.11.1. > python/scikit-learn: Updated for version 0.24.1. > python/typed_ast: Updated for version 1.4.3. > system/android-file-transfer: Updated for version 4.2. > system/ansible: Updated for version 2.9.20. > system/clamav: Fix permissions to allow users to run clamscan. > system/execline: Updated for version 2.8.0.1. > system/lxtask: Updated for version 0.1.10. > system/lxterminal: Updated for version 0.4.0. > system/netdata: Updated for version 1.29.3. > system/newLd: Update script. > system/pax: Updated for version 20201030 (switch to MirBSD pax). > system/pcmanfm: Updated for version 1.3.2. > system/qdirstat: Updated for version 1.7.1. > system/s6-linux-init: Updated for version 1.0.6.2. > system/s6-rc: Updated for version 0.5.2.2. > system/s6: Updated for version 2.10.0.3. > system/telegraf: Updated for version 1.18.1. > system/wine-staging: Updated for version 6.5. > +--------------------------+ > > > -- > Willy Sudiarto Raharjo > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: OpenPGP_signature > Type: application/pgp-signature > Size: 840 bytes > Desc: OpenPGP digital signature > URL: > > ------------------------------ > > 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 180, Issue 13 > ************************************************** From matteo.bernardini at gmail.com Sat Apr 17 14:05:42 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Sat, 17 Apr 2021 16:05:42 +0200 Subject: [Slackbuilds-users] dillo with SSL on current In-Reply-To: <20210417130413.45ecac8c@kirsche.kuchen> References: <20210417130413.45ecac8c@kirsche.kuchen> Message-ID: pushed in my branch. Il giorno sab 17 apr 2021 alle ore 13:04 Ruben Schuller ha scritto: > > hi, > > as we are approaching 15.0 and are fixing the slackbuilds now: > i have recently fiddled with installing dillo with SSL on current. > i've had to apply a patch [1] from gentoo, run > "autoreconf -if" and compile with "-fcommon". see the attached patch > for the slackbuild. the gentoo patch is assumed to be located in > $CWD. > > cheers > ruben > > [1] > https://gitweb.gentoo.org/repo/gentoo.git/plain/www-client/dillo/files/dillo-3.0.5-openssl-1.1.patch?id=8e07d499b9d5acf45597936fef4370c0172d3247 > _______________________________________________ > 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 jgraham at compukix.net Sat Apr 17 14:22:04 2021 From: jgraham at compukix.net (Jason Graham) Date: Sat, 17 Apr 2021 10:22:04 -0400 Subject: [Slackbuilds-users] Several packages up for adoption In-Reply-To: <81e9145c-db53-4015-3d3e-52ce2ef1320f@slackware-srbija.org> References: <81e9145c-db53-4015-3d3e-52ce2ef1320f@slackware-srbija.org> Message-ID: <0a246879-1d48-5a8a-a1bf-d1a342bb8d01@compukix.net> On 4/15/21 4:09 PM, Bojan Popovic wrote: > > bochs - I haven't used it in a few years. Nowadays I mostly use Qemu > and Virtualbox. Hi Bojan, I'm happy to take over bochs. I find it handy for tinkering with OS devel. Kind regards, Jason From gerardo.zamudio at linux.com Sat Apr 17 18:50:22 2021 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sat, 17 Apr 2021 13:50:22 -0500 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> Message-ID: On 2021-04-17 1:18 am, Eugen Wissner wrote: > Hi, > > I would like to ask to remove the following SlackBuilds: > > - opendbx: It builds on current, but opendbx doesn't seem to be active, > the last release was in 2012 and nothing depends on it. > > > Eugen I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if MySQL support is going to be compiled in (see README). Regards Gerardo Zamudio From belka at caraus.de Sat Apr 17 20:05:12 2021 From: belka at caraus.de (Eugen Wissner) Date: Sat, 17 Apr 2021 22:05:12 +0200 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> Message-ID: <20210417200512.qeiwzg2nifjuipdd@slave.caraus.de> On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: > On 2021-04-17 1:18 am, Eugen Wissner wrote: > > Hi, > > > > I would like to ask to remove the following SlackBuilds: > > > > - opendbx: It builds on current, but opendbx doesn't seem to be active, > > the last release was in 2012 and nothing depends on it. > > > > > > Eugen > > I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if MySQL > support is going to be compiled in (see README). > > Regards > Gerardo Zamudio Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years ago I switched to rspamd and forgot about OpenDBX. Sorry, my fault. From sborg63 at disroot.org Sat Apr 17 20:41:26 2021 From: sborg63 at disroot.org (sborg63) Date: Sat, 17 Apr 2021 21:41:26 +0100 Subject: [Slackbuilds-users] SlackBuilds-users Digest, Vol 180, Issue 13 In-Reply-To: References: Message-ID: <20210417214126.33f4a5b1@knotsUL> Ok, thanks for the update. But please do not carry over PDFshuffler from 14.2 to the 15.0 repo Cheers, Rob On Sat, 17 Apr 2021 05:13:20 +0000 slackbuilds-users-request at slackbuilds.org wrote: > Message: 1 > Date: Fri, 16 Apr 2021 20:27:23 +0100 > From: sborg63 > To: "SlackBuilds.org Users List" , > > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <20210416202723.5279b7ac at knotsUL> > Content-Type: text/plain; charset=US-ASCII > > Hi Willy, > > When would it be possible to submit scripts for packages that only run > on current and that should replace outdated, no-longer maintained > (e.g python2-only) packages that are in the repository for 14.2 atm? > > For example I maintain PDF-shuffler which should be dropped. This I > would like to replace in the 15.0 repository with PDFarranger plus > Pike PDF, which work fine for me on current > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > PikePDF relies on a version of qpdf not available in stock 14.2. > > Good luck with the work ahead... > > Rob > > > > Message: 2 > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > From: Willy Sudiarto Raharjo > > To: "SlackBuilds.org Users List" > > Subject: [Slackbuilds-users] Development Cycle Towards 15.0 > > Repository Message-ID: > > > > Content-Type: text/plain; charset="utf-8" > > > ------------------------------ > > Message: 2 > Date: Fri, 16 Apr 2021 20:32:00 +0100 > From: Dave Woodfall > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: <20210416193200.GS5008 at localhost> > Content-Type: text/plain; charset=utf-8 > > Hi Rob, > > When submissions open again, and we will be in 15.0, which would be > the correct time. > > Dave > > Slackbuilds Users put forth the > proposition: > > Hi Willy, > > When would it be possible to submit scripts for packages that only > > run on current and that should replace outdated, no-longer > > maintained (e.g python2-only) packages that are in the repository > > for 14.2 atm? For example I maintain PDF-shuffler which should be > > dropped. This I would like to replace in the 15.0 repository with > > PDFarranger plus Pike PDF, which work fine for me on current > > (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > > https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > > PikePDF relies on a version of qpdf not available in stock 14.2. > > Good luck with the work ahead... > > Rob > > > > > > Message: 2 > > > Date: Fri, 16 Apr 2021 17:27:07 +0700 > > > From: Willy Sudiarto Raharjo > > > To: "SlackBuilds.org Users List" > > > Subject: [Slackbuilds-users] > > > Development Cycle Towards 15.0 Repository Message-ID: > > > > > > Content-Type: text/plain; charset="utf-8" > > -- > Dave > > > ------------------------------ > > Message: 3 > Date: Sat, 17 Apr 2021 07:34:35 +0700 > From: Willy Sudiarto Raharjo > To: slackbuilds-users at slackbuilds.org > Subject: Re: [Slackbuilds-users] Development Cycle Towards 15.0 > Repository SlackBuilds-users Digest, Vol 180, Issue 12 > Message-ID: > Content-Type: text/plain; charset="utf-8" > > > When submissions open again, and we will be in 15.0, which would be > > the correct time. > > > > Dave > > > >> Hi Willy, > >> When would it be possible to submit scripts for packages that only > >> run on current and that should replace outdated, no-longer > >> maintained (e.g python2-only) packages that are in the repository > >> for 14.2 atm? For example I maintain PDF-shuffler which should be > >> dropped. This I would like to replace in the 15.0 repository with > >> PDFarranger plus Pike PDF, which work fine for me on current > >> (https://github.com/brobr/SLACKBUILDtrees/tree/master/pdfarranger > >> https://github.com/brobr/SLACKBUILDtrees/tree/master/pikepdf). > >> PikePDF relies on a version of qpdf not available in stock 14.2. > >> Good luck with the work ahead... > > Hi Rob > > Yes, i agree with Dave > once 15.0 repo is ready, you can submit new scripts > for now, we will focus on getting 15.0 ready first as base for future > new scripts > > From gerardo.zamudio at linux.com Sat Apr 17 20:51:45 2021 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sat, 17 Apr 2021 15:51:45 -0500 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <20210417200512.qeiwzg2nifjuipdd@slave.caraus.de> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> <20210417200512.qeiwzg2nifjuipdd@slave.caraus.de> Message-ID: <081577dadda018daa984f5bfa7b7aee9@linux.com> On 2021-04-17 3:05 pm, Eugen Wissner wrote: > On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: >> On 2021-04-17 1:18 am, Eugen Wissner wrote: >> > Hi, >> > >> > I would like to ask to remove the following SlackBuilds: >> > >> > - opendbx: It builds on current, but opendbx doesn't seem to be active, >> > the last release was in 2012 and nothing depends on it. >> > >> > >> > Eugen >> >> I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if >> MySQL >> support is going to be compiled in (see README). >> >> Regards >> Gerardo Zamudio > > Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years > ago > I switched to rspamd and forgot about OpenDBX. Sorry, my fault. Are you keeping it then? From belka at caraus.de Sat Apr 17 21:03:21 2021 From: belka at caraus.de (Eugen Wissner) Date: Sat, 17 Apr 2021 23:03:21 +0200 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <081577dadda018daa984f5bfa7b7aee9@linux.com> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> <20210417200512.qeiwzg2nifjuipdd@slave.caraus.de> <081577dadda018daa984f5bfa7b7aee9@linux.com> Message-ID: <20210417210321.zqa4qt6dhpxcatst@slave.caraus.de> On Sat, Apr 17, 2021 at 03:51:45PM -0500, Gerardo Zamudio wrote: > On 2021-04-17 3:05 pm, Eugen Wissner wrote: > > On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: > > > On 2021-04-17 1:18 am, Eugen Wissner wrote: > > > > Hi, > > > > > > > > I would like to ask to remove the following SlackBuilds: > > > > > > > > - opendbx: It builds on current, but opendbx doesn't seem to be active, > > > > the last release was in 2012 and nothing depends on it. > > > > > > > > > > > > Eugen > > > > > > I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if > > > MySQL > > > support is going to be compiled in (see README). > > > > > > Regards > > > Gerardo Zamudio > > > > Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years ago > > I switched to rspamd and forgot about OpenDBX. Sorry, my fault. > > Are you keeping it then? If you actually use it, it is surely in better hands with you. From gerardo.zamudio at linux.com Sat Apr 17 21:07:58 2021 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Sat, 17 Apr 2021 16:07:58 -0500 Subject: [Slackbuilds-users] My -current scripts In-Reply-To: <20210417210321.zqa4qt6dhpxcatst@slave.caraus.de> References: <20210417061837.cbyqqnc4vmbrpzm4@slave.caraus.de> <20210417200512.qeiwzg2nifjuipdd@slave.caraus.de> <081577dadda018daa984f5bfa7b7aee9@linux.com> <20210417210321.zqa4qt6dhpxcatst@slave.caraus.de> Message-ID: <0b0307ebcb66d0784d1f0cb8ad25da6d@linux.com> On 2021-04-17 4:03 pm, Eugen Wissner wrote: > On Sat, Apr 17, 2021 at 03:51:45PM -0500, Gerardo Zamudio wrote: >> On 2021-04-17 3:05 pm, Eugen Wissner wrote: >> > On Sat, Apr 17, 2021 at 01:50:22PM -0500, Gerardo Zamudio wrote: >> > > On 2021-04-17 1:18 am, Eugen Wissner wrote: >> > > > Hi, >> > > > >> > > > I would like to ask to remove the following SlackBuilds: >> > > > >> > > > - opendbx: It builds on current, but opendbx doesn't seem to be active, >> > > > the last release was in 2012 and nothing depends on it. >> > > > >> > > > >> > > > Eugen >> > > >> > > I can take OpenDBX. I maintain OpenDKIM and OpenDBX is required if >> > > MySQL >> > > support is going to be compiled in (see README). >> > > >> > > Regards >> > > Gerardo Zamudio >> > >> > Ah, OpenDKIM was probably the reason I maintained OpenDBX. Two years ago >> > I switched to rspamd and forgot about OpenDBX. Sorry, my fault. >> >> Are you keeping it then? > > If you actually use it, it is surely in better hands with you. OK, thank you. From dave at slackbuilds.org Tue Apr 20 01:10:04 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Tue, 20 Apr 2021 02:10:04 +0100 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: References: <20201102192126.GH32281@blackswan.r0t.uk> Message-ID: <20210420011004.GA24213@localhost> On 03/11/20 20:48, Andrzej Telszewski put forth the proposition: > On 03/11/2020 06:29, Jeremy Hansen wrote: > > I haven't used it before, but I was a big fan of the old amarok. If > > someone already uses it and wants to take over, I'm totally fine with > > that, but if no one else claims it by the end of the week, I'll take it > > over. > > > > Jeremy > > > > > I'm actually using *Clementine* as my main music player. > I'll happily take it over. > I'm bold enough to say that I'm better fir than Jeremy, because I actually > use it. :-> > On the other hand, I use it to play local collection exclusively, I don't > use services like Spotify. > And for that reason, I will not be able to reassure correct operation for > networked services. > If you find me a good fit for the job, I'm ready to take it. :-) > Cheers! > -- > Andrzej Andrzej, what did you decide? -- Dave From erich.public at protonmail.com Tue Apr 20 03:23:33 2021 From: erich.public at protonmail.com (Erich Ritz) Date: Tue, 20 Apr 2021 03:23:33 +0000 Subject: [Slackbuilds-users] Abandoning worldofgoo In-Reply-To: <569209cbbb789d83f4f8b21839cc4f29@linux.com> References: <569209cbbb789d83f4f8b21839cc4f29@linux.com> Message-ID: <26NJ6hkl8JmC4gfCV8VffnAzgCak_fJYxlqez9ZHEUPHpHiqzraSqfH_TviYmGRoD9wpkQDa4RUucxzBH3xU9LXQQURr1QKi08B1OB0X6dA=@protonmail.com> Hi Gerardo, ??????? Original Message ??????? On Monday, April 12, 2021 9:19 PM, Gerardo Zamudio wrote: > Hi all > > I no longer play this game or have an interest in maintaining the > SlackBuild. There is a new version out but I'm not sure if it's a demo. > The current SlackBuild demo version is hosted by us. > > Anyone is free to take it. If no one is interested please remove it from > the repository or remove my name from the MAINTAINER field. > > Regards > Gerardo Zamudio > I'll take over worldofgoo. I have the full version of the game. I'll send an update when submissions reopen after 15.0 is released to support both the demo (default) and full version of the game. Erich From andrzej at telszewski.com Tue Apr 20 19:54:15 2021 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Tue, 20 Apr 2021 21:54:15 +0200 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: <20210420011004.GA24213@localhost> References: <20201102192126.GH32281@blackswan.r0t.uk> <20210420011004.GA24213@localhost> Message-ID: <2ea07fa1-3ca0-4b77-51f6-5575c9487f0b@telszewski.com> On 4/20/21 3:10 AM, Dave Woodfall wrote: > On 03/11/20 20:48, > Andrzej Telszewski put forth the proposition: >> If you find me a good fit for the job, I'm ready to take it. :-) >> Cheers! >> -- >> Andrzej > Andrzej, what did you decide? I'll investigate over the coming weekend and come back to you. Thank you for heads up. I'm already on -current, so I'll test against it. From bgrundy at gmail.com Tue Apr 20 21:00:14 2021 From: bgrundy at gmail.com (Barry J. Grundy) Date: Tue, 20 Apr 2021 17:00:14 -0400 Subject: [Slackbuilds-users] Python (Again!) Message-ID: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> I know this has come up before and perhaps been answered and I've also read through the related threads on LQ, but I still have not seen a definitive answer (if there is one): Since python2 is EOL and -current/15 ships with python3, is it good practice now to build python packages with python3 by default?? If so, then what's the best way to handle the multiple versions?? This discussion was had on the list back in Feb of '19, but I don't see anything definitive. For example, I maintain dpkt.? The version in the -current (ponce's) repo works, but I have an update ready to go when submissions open again.? Right now dpkt builds for python2. Here's my question: My "ready to go" update switches to python3 by default and uses a "PYTHON2=yes" option to build python2 modules if the user wants. Would it be better to create python3-dpkt and leave the dpkt script at python2?? I see it both ways in the 14.2 repo. Another probably better example is distorm, which is a requirement for volatility (which is python2 only).? volatility3 is a separate re-write for python3 with different prerequisites (and I already have a slackbuild to submit for that when things open again).? So for volatility it makes sense to leave distorm as is.? I can submit a separate python3-distorm script when I submit volatility3. Perhaps with the submissions freeze it would be a good time to either separate the scripts or at least decide on a "best practice".? My apologies if I'm simply kicking a dead horse here. Thanks, Barry From slackbuilds at ninefamily.com Tue Apr 20 20:57:34 2021 From: slackbuilds at ninefamily.com (Eugene) Date: Tue, 20 Apr 2021 16:57:34 -0400 Subject: [Slackbuilds-users] Slackbuild Support for ARM In-Reply-To: <2ea07fa1-3ca0-4b77-51f6-5575c9487f0b@telszewski.com> References: <20201102192126.GH32281@blackswan.r0t.uk> <20210420011004.GA24213@localhost> <2ea07fa1-3ca0-4b77-51f6-5575c9487f0b@telszewski.com> Message-ID: <0309435e-de03-c087-ecb5-d0309762e388@ninefamily.com> Hello all. It was suggested I reach out to the Slackbuilds mailing list with my question as to Slackbuild support of the arm architecture. With the official support of some arm SBC's from Slackware, the SarPi support for Raspberry Pi and upcoming AArch64 there are many of us who may utilize existing Slackbuilds script to build software for our arm SBC's. I'm wondering then, is there any soft of official support for arm from the Slackbuild community, i.e. should we assume Slackbuilds to be usable and report any issues or are they not supported for arm at all? If arm is supported is there any effort to consolidate testing and patches similar to 15/-current? https://www.linuxquestions.org/questions/slackware-14/sbo-scripts-not-building-on-current-read-1st-post-pls-4175561999/ I've found that most will build without issue and a few simply need minor edits such as specifying the SLKCFLAGS and LIBDIRSUFFIX. elif [ "$ARCH" = "arm" ]; then SLKCFLAGS="-O2 -fPIC" LIBDIRSUFFIX="" Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerardo.zamudio at linux.com Tue Apr 20 21:48:43 2021 From: gerardo.zamudio at linux.com (Gerardo Zamudio) Date: Tue, 20 Apr 2021 16:48:43 -0500 Subject: [Slackbuilds-users] Python (Again!) In-Reply-To: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> References: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> Message-ID: <3189f6cbe21723de5cdb3b3dc2d5bafe@linux.com> On 2021-04-20 4:00 pm, Barry J. Grundy wrote: > I know this has come up before and perhaps been answered and I've also > read through the related threads on LQ, but I still have not seen a > definitive answer (if there is one): > > Since python2 is EOL and -current/15 ships with python3, is it good > practice now to build python packages with python3 by default?? Wait until submissions for 15 are open. For now, build with python2 by default and make a separate python3 package or add a python3 switch. But, submissions are closed, so new packages are no longer an option :) > For example, I maintain dpkt.? The version in the -current (ponce's) > repo works, but I have an update ready to go when submissions open > again.? Right now dpkt builds for python2. Here's my question: > > My "ready to go" update switches to python3 by default and uses a > "PYTHON2=yes" option to build python2 modules if the user wants. Would > it be better to create python3-dpkt and leave the dpkt script at > python2?? I see it both ways in the 14.2 repo. SlackBuilds target a default full install of Slackware. Your script should always use whatever is the default. If python3 is the default python version in a full install of Slackware, then your script should use that. This means for the upcoming Slackware 15 repo in SlackBuilds, your dpkt script should use python3 by default and if you want to add python2 support it could be a separate switch or you could create a separate python2-dpkt script. Regards Gerardo Zamudio From jebrhansen+SBo at gmail.com Tue Apr 20 21:52:59 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Tue, 20 Apr 2021 15:52:59 -0600 Subject: [Slackbuilds-users] Python (Again!) In-Reply-To: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> References: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> Message-ID: On Tue, Apr 20, 2021, 2:59 PM Barry J. Grundy wrote: > I know this has come up before and perhaps been answered and I've also > read through the related threads on LQ, but I still have not seen a > definitive answer (if there is one): > > Since python2 is EOL and -current/15 ships with python3, is it good > practice now to build python packages with python3 by default? If so, > then what's the best way to handle the multiple versions? This > discussion was had on the list back in Feb of '19, but I don't see > anything definitive. > > For example, I maintain dpkt. The version in the -current (ponce's) > repo works, but I have an update ready to go when submissions open > again. Right now dpkt builds for python2. Here's my question: > > My "ready to go" update switches to python3 by default and uses a > "PYTHON2=yes" option to build python2 modules if the user wants. Would > it be better to create python3-dpkt and leave the dpkt script at > python2? I see it both ways in the 14.2 repo. > > Another probably better example is distorm, which is a requirement for > volatility (which is python2 only). volatility3 is a separate re-write > for python3 with different prerequisites (and I already have a > slackbuild to submit for that when things open again). So for > volatility it makes sense to leave distorm as is. I can submit a > separate python3-distorm script when I submit volatility3. > > Perhaps with the submissions freeze it would be a good time to either > separate the scripts or at least decide on a "best practice". My > apologies if I'm simply kicking a dead horse here. > > Thanks, > > Barry > In my opinion, I think SBo for 15.0 should default to python3 for any packages and python2 should be something that can be optional (for those packages that support both). If there's a need to have separate python2 and python3 packages, the python3 package should not need an identifier in front of it, where the python2 package should ($PRGNAM for python3 and python2-$PRGNAM for python2). Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From rshepard at appl-ecosys.com Tue Apr 20 22:03:01 2021 From: rshepard at appl-ecosys.com (Rich Shepard) Date: Tue, 20 Apr 2021 15:03:01 -0700 (PDT) Subject: [Slackbuilds-users] Python (Again!) In-Reply-To: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> References: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> Message-ID: On Tue, 20 Apr 2021, Barry J. Grundy wrote: > Since python2 is EOL and -current/15 ships with python3, is it good > practice now to build python packages with python3 by default? Barry, Yes. > If so, then what's the best way to handle the multiple versions?? This > discussion was had on the list back in Feb of '19, but I don't see > anything definitive. I'm not an SBo package maintainer, but you'd be safe to stop any python2 upgrades. If there's python2 code that needs to be used with python3 run it through 2to3. That's what I did to my code and hadn't to do any hand tweaking. Rich From rworkman at slackbuilds.org Tue Apr 20 23:05:28 2021 From: rworkman at slackbuilds.org (Robby Workman) Date: Tue, 20 Apr 2021 18:05:28 -0500 Subject: [Slackbuilds-users] Python (Again!) In-Reply-To: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> References: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> Message-ID: <20210420180528.51262c3b@home.rlworkman.net> We are still in the "we don't know yet" phase of this. We will update everyone with a definitive answer once arrive at one :-) -RW On Tue, 20 Apr 2021 17:00:14 -0400 "Barry J. Grundy" wrote: > I know this has come up before and perhaps been answered and I've > also read through the related threads on LQ, but I still have not > seen a definitive answer (if there is one): > > Since python2 is EOL and -current/15 ships with python3, is it good > practice now to build python packages with python3 by default?? If > so, then what's the best way to handle the multiple versions?? This > discussion was had on the list back in Feb of '19, but I don't see > anything definitive. > > For example, I maintain dpkt.? The version in the -current (ponce's) > repo works, but I have an update ready to go when submissions open > again.? Right now dpkt builds for python2. Here's my question: > > My "ready to go" update switches to python3 by default and uses a > "PYTHON2=yes" option to build python2 modules if the user wants. > Would it be better to create python3-dpkt and leave the dpkt script > at python2?? I see it both ways in the 14.2 repo. > > Another probably better example is distorm, which is a requirement > for volatility (which is python2 only).? volatility3 is a separate > re-write for python3 with different prerequisites (and I already have > a slackbuild to submit for that when things open again).? So for > volatility it makes sense to leave distorm as is.? I can submit a > separate python3-distorm script when I submit volatility3. > > Perhaps with the submissions freeze it would be a good time to either > separate the scripts or at least decide on a "best practice".? My > apologies if I'm simply kicking a dead horse here. > > Thanks, > > Barry > > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From bgrundy at gmail.com Wed Apr 21 00:20:35 2021 From: bgrundy at gmail.com (Barry J. Grundy) Date: Tue, 20 Apr 2021 20:20:35 -0400 Subject: [Slackbuilds-users] Python (Again!) In-Reply-To: References: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> Message-ID: On 4/20/21 5:52 PM, Jeremy Hansen wrote: > On Tue, Apr 20, 2021, 2:59 PM Barry J. Grundy > wrote: > > I know this has come up before and perhaps been answered and I've > also > read through the related threads on LQ, but I still have not seen a > definitive answer (if there is one): > > Since python2 is EOL and -current/15 ships with python3, is it good > practice now to build python packages with python3 by default?? If > so, > then what's the best way to handle the multiple versions? This > discussion was had on the list back in Feb of '19, but I don't see > anything definitive. > > For example, I maintain dpkt.? The version in the -current (ponce's) > repo works, but I have an update ready to go when submissions open > again.? Right now dpkt builds for python2. Here's my question: > > My "ready to go" update switches to python3 by default and uses a > "PYTHON2=yes" option to build python2 modules if the user wants. > Would > it be better to create python3-dpkt and leave the dpkt script at > python2?? I see it both ways in the 14.2 repo. > > Another probably better example is distorm, which is a requirement > for > volatility (which is python2 only).? volatility3 is a separate > re-write > for python3 with different prerequisites (and I already have a > slackbuild to submit for that when things open again).? So for > volatility it makes sense to leave distorm as is.? I can submit a > separate python3-distorm script when I submit volatility3. > > Perhaps with the submissions freeze it would be a good time to either > separate the scripts or at least decide on a "best practice".? My > apologies if I'm simply kicking a dead horse here. > > Thanks, > > Barry > > > In my opinion, I think SBo for 15.0 should default to python3 for any > packages and python2 should be something that can be optional (for > those packages that support both). > > If there's a need to have separate python2 and python3 packages, the > python3 package should not need an identifier in front of it, where > the python2 package should ($PRGNAM for python3 and python2-$PRGNAM > for python2). I agree with defaulting to python3 for 15.0.? But right now we'd have $PRGNAM changing to python2-$PRGNAM and python3-$PRGNAM changing to $PRGNAM.? Then when python4 comes out it would be a repeat of the same issue (maybe).? Perhaps "python$VER-$PRGNAM" would be appropriate for everything. And perhaps I'm just over thinking it.? But thanks for the responses. Barry -------------- next part -------------- An HTML attachment was scrubbed... URL: From bgrundy at gmail.com Wed Apr 21 00:22:40 2021 From: bgrundy at gmail.com (Barry J. Grundy) Date: Tue, 20 Apr 2021 20:22:40 -0400 Subject: [Slackbuilds-users] Python (Again!) In-Reply-To: <20210420180528.51262c3b@home.rlworkman.net> References: <378dbe98-3b70-27a8-6ace-285b8151bf6f@gmail.com> <20210420180528.51262c3b@home.rlworkman.net> Message-ID: <91769de0-07ff-2fed-1f7d-0d11d58be676@gmail.com> On 4/20/21 7:05 PM, Robby Workman wrote: > We are still in the "we don't know yet" phase of this. > We will update everyone with a definitive answer once > arrive at one :-) > > -RW Thanks Robby.? I'll stop thinking about it now.?? :-) From slackbuilds at ninefamily.com Wed Apr 21 02:06:05 2021 From: slackbuilds at ninefamily.com (slackbuilds at ninefamily.com) Date: Tue, 20 Apr 2021 22:06:05 -0400 Subject: [Slackbuilds-users] files to users /home In-Reply-To: <0309435e-de03-c087-ecb5-d0309762e388@ninefamily.com> References: <20201102192126.GH32281@blackswan.r0t.uk> <20210420011004.GA24213@localhost> <2ea07fa1-3ca0-4b77-51f6-5575c9487f0b@telszewski.com> <0309435e-de03-c087-ecb5-d0309762e388@ninefamily.com> Message-ID: If an application needs to use a file in the user's /home what is the correct way to do so in a Slackbuild?? Do I put it in a central place and link to it or just instruct the user to manually put the file or a script for it? Thanks From dickson.tim at googlemail.com Wed Apr 21 07:51:40 2021 From: dickson.tim at googlemail.com (Tim Dickson) Date: Wed, 21 Apr 2021 08:51:40 +0100 Subject: [Slackbuilds-users] files to users /home In-Reply-To: References: <20201102192126.GH32281@blackswan.r0t.uk> <20210420011004.GA24213@localhost> <2ea07fa1-3ca0-4b77-51f6-5575c9487f0b@telszewski.com> <0309435e-de03-c087-ecb5-d0309762e388@ninefamily.com> Message-ID: if the file is program data which is only read, newver written, then linking to a common location e. /usr/share/appname/datafile is the most efficient, especially for large datafiles (think warzone2100 for example). ?I haven't seen any good way of handling this in a slackbuild, because you may have many existing users, and what about users added later?. editing the default user template to add link creation and going through existing users to add links is not ideal. if you remove the package, the links will remain. It is better if possible to get upstream to fix their code so that common user data is stored in a common place. local user data should be created as required by the software. regards, Tim On 21/04/2021 03:06, slackbuilds at ninefamily.com wrote: > If an application needs to use a file in the user's /home what is the > correct way to do so in a Slackbuild?? Do I put it in a central place > and link to it or just instruct the user to manually put the file or a > script for it? > > 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/ > -- This email has been checked for viruses by AVG. https://www.avg.com From sb at rbn.im Wed Apr 21 14:20:51 2021 From: sb at rbn.im (Ruben Schuller) Date: Wed, 21 Apr 2021 16:20:51 +0200 Subject: [Slackbuilds-users] etlegacy and etlegacy-from-source have the same PRGNAM Message-ID: <20210421162051.374fd011@kirsche.kuchen> Hi, i'm fumbling around with my own repository-building script, which notified me about that there are two slackbuilds with PRGNAM "etlegacy" (in master), namely "etlegacy" [1] and "etlegacy-from-source" [2]. is this allowed? i kind of assumed that PRGNAM is unique :) Cheers Ruben [1] https://git.slackbuilds.org/slackbuilds/tree/games/etlegacy/etlegacy.info [2] https://git.slackbuilds.org/slackbuilds/tree/games/etlegacy-from-source/etlegacy-from-source.info From matteo.bernardini at gmail.com Wed Apr 21 14:29:59 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 21 Apr 2021 16:29:59 +0200 Subject: [Slackbuilds-users] etlegacy and etlegacy-from-source have the same PRGNAM In-Reply-To: <20210421162051.374fd011@kirsche.kuchen> References: <20210421162051.374fd011@kirsche.kuchen> Message-ID: hi Ruben, no, it's not allowed, it's an oversight! thanks for the report! :-) Matteo Il giorno mer 21 apr 2021 alle ore 16:21 Ruben Schuller ha scritto: > > Hi, > > i'm fumbling around with my own repository-building script, which > notified me about that there are two slackbuilds with PRGNAM "etlegacy" > (in master), namely "etlegacy" [1] and "etlegacy-from-source" [2]. > is this allowed? i kind of assumed that PRGNAM is unique :) > > Cheers > Ruben > > [1] > https://git.slackbuilds.org/slackbuilds/tree/games/etlegacy/etlegacy.info > > [2] > https://git.slackbuilds.org/slackbuilds/tree/games/etlegacy-from-source/etlegacy-from-source.info > _______________________________________________ > 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 andrzej at telszewski.com Sat Apr 24 13:01:20 2021 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Sat, 24 Apr 2021 15:01:20 +0200 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: <2ea07fa1-3ca0-4b77-51f6-5575c9487f0b@telszewski.com> References: <20201102192126.GH32281@blackswan.r0t.uk> <20210420011004.GA24213@localhost> <2ea07fa1-3ca0-4b77-51f6-5575c9487f0b@telszewski.com> Message-ID: <940b39dd-238a-0d08-37bf-b29e39caf562@telszewski.com> On 4/20/21 9:54 PM, Andrzej Telszewski wrote: > On 4/20/21 3:10 AM, Dave Woodfall wrote: >> On 03/11/20 20:48, >> Andrzej Telszewski put forth the proposition: >>> If you find me a good fit for the job, I'm ready to take it. :-) >>> Cheers! >>> -- >>> Andrzej >> Andrzej, what did you decide? > I'll investigate over the coming weekend and come back to you. > Thank you for heads up. > I'm already on -current, so I'll test against it. > Hi Dave, I've just given _Strawberry_ (0.9.3) a try and I'm switching to it. I'm not going to be using _Clementine_ in the near future. Please find _Clementine_ a more suitable maintainer, as I will not take it finally. Thank you! When it comes to _Strawberry_, the main selling points are: - the code is being actively versioned and released, - there is less code than in _Clementine_ and I'm not missing any features. Should _Strawberry_ maintainer be not actively maintaining it anymore, I'll happily take it. Cheers! -- Best regards, Andrzej Telszewski From dave at slackbuilds.org Sat Apr 24 13:24:28 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 24 Apr 2021 14:24:28 +0100 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: References: <20201102192126.GH32281@blackswan.r0t.uk> Message-ID: <20210424132428.GC24213@localhost> On 02/11/20 22:29, Jeremy Hansen put forth the proposition: > I haven't used it before, but I was a big fan of the old amarok. If someone > already uses it and wants to take over, I'm totally fine with that, but if > no one else claims it by the end of the week, I'll take it over. > Jeremy Would you like to take it on still? -- Dave From jebrhansen+SBo at gmail.com Sat Apr 24 19:45:52 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 24 Apr 2021 13:45:52 -0600 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: <20210424132428.GC24213@localhost> References: <20201102192126.GH32281@blackswan.r0t.uk> <20210424132428.GC24213@localhost> Message-ID: On Sat, Apr 24, 2021, 7:24 AM Dave Woodfall wrote: > On 02/11/20 22:29, > Jeremy Hansen put forth the proposition: > > I haven't used it before, but I was a big fan of the old amarok. If > someone > > already uses it and wants to take over, I'm totally fine with that, but > if > > no one else claims it by the end of the week, I'll take it over. > > Jeremy > > Would you like to take it on still? > I'd be happy to take it, but since Spycrowsoft stated they're actually using it and are willing to maintain it, I'll give them the opportunity to take it on if they want. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From dave at slackbuilds.org Sat Apr 24 19:58:00 2021 From: dave at slackbuilds.org (Dave Woodfall) Date: Sat, 24 Apr 2021 20:58:00 +0100 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: References: <20201102192126.GH32281@blackswan.r0t.uk> <20210424132428.GC24213@localhost> Message-ID: <20210424195800.GD24213@localhost> On 24/04/21 13:45, Jeremy Hansen put forth the proposition: > On Sat, Apr 24, 2021, 7:24 AM Dave Woodfall wrote: > > On 02/11/20 22:29, > > Jeremy Hansen put forth the proposition: > > > I haven't used it before, but I was a big fan of the old amarok. If > > someone > > > already uses it and wants to take over, I'm totally fine with that, but > > if > > > no one else claims it by the end of the week, I'll take it over. > > > Jeremy > > > > Would you like to take it on still? > > > I'd be happy to take it, but since Spycrowsoft stated they're actually > using it and are willing to maintain it, I'll give them the opportunity to > take it on if they want. > Jeremy I can't find a message from him about it, but OK. -- Dave From jebrhansen+SBo at gmail.com Sat Apr 24 22:02:54 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sat, 24 Apr 2021 16:02:54 -0600 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: <20210424195800.GD24213@localhost> References: <20201102192126.GH32281@blackswan.r0t.uk> <20210424132428.GC24213@localhost> <20210424195800.GD24213@localhost> Message-ID: On Sat, Apr 24, 2021, 1:58 PM Dave Woodfall wrote: > On 24/04/21 13:45, > Jeremy Hansen put forth the proposition: > > On Sat, Apr 24, 2021, 7:24 AM Dave Woodfall > wrote: > > > On 02/11/20 22:29, > > > Jeremy Hansen put forth the proposition: > > > > I haven't used it before, but I was a big fan of the old amarok. If > > > someone > > > > already uses it and wants to take over, I'm totally fine with that, > but > > > if > > > > no one else claims it by the end of the week, I'll take it over. > > > > Jeremy > > > > > > Would you like to take it on still? > > > > > I'd be happy to take it, but since Spycrowsoft stated they're actually > > using it and are willing to maintain it, I'll give them the opportunity > to > > take it on if they want. > > Jeremy > > I can't find a message from him about it, but OK. > Looks like they sent that message directly to me. I am actively using it. > > >> I want to give others the option of taking over this slackbuild first, >> but if no one else takes over, I will do so. > > >> Spycrowsoft > > I'm adding them directly to the email. @Spycrowsoft, feel free to take over maintenance if you're still interested. Otherwise let me know and I'll take over. Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From spycrowsoft at gmail.com Sun Apr 25 09:24:44 2021 From: spycrowsoft at gmail.com (Spycrowsoft) Date: Sun, 25 Apr 2021 11:24:44 +0200 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: References: <20201102192126.GH32281@blackswan.r0t.uk> <20210424132428.GC24213@localhost> <20210424195800.GD24213@localhost> Message-ID: <398ceaa4-2d50-b442-1fc7-9a58a6489f82@gmail.com> You can take it as I am not actively looking for more slackbuilds to maintain. But if you are not willing to do so, I will take up the work. Op 25-04-2021 om 00:02 schreef Jeremy Hansen: > On Sat, Apr 24, 2021, 1:58 PM Dave Woodfall > wrote: > > On 24/04/21 13:45, > Jeremy Hansen > put forth the proposition: > > On Sat, Apr 24, 2021, 7:24 AM Dave Woodfall > > wrote: > > > On 02/11/20 22:29, > > > Jeremy Hansen > put forth the proposition: > > > > I haven't used it before, but I was a big fan of the old > amarok. If > > > someone > > > > already uses it and wants to take over, I'm totally fine > with that, but > > > if > > > > no one else claims it by the end of the week, I'll take it over. > > > > Jeremy > > > > > > Would you like to take it on still? > > > > > I'd be happy to take it, but since Spycrowsoft stated they're > actually > > using it and are willing to maintain it, I'll give them the > opportunity to > > take it on if they want. > > Jeremy > > I can't find a message from him about it, but OK. > > > Looks like they sent that message directly to me. > > I am actively using it. > > > I want to give others the option of taking over this > slackbuild first, but if no one else takes over, I will do so. > > > Spycrowsoft > > > I'm adding them directly to the email. > > @Spycrowsoft, feel free to take over maintenance if you're still > interested. Otherwise let me know and I'll take over. > > Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Mon Apr 26 04:31:04 2021 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Sun, 25 Apr 2021 22:31:04 -0600 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: <398ceaa4-2d50-b442-1fc7-9a58a6489f82@gmail.com> References: <20201102192126.GH32281@blackswan.r0t.uk> <20210424132428.GC24213@localhost> <20210424195800.GD24213@localhost> <398ceaa4-2d50-b442-1fc7-9a58a6489f82@gmail.com> Message-ID: On Sun, Apr 25, 2021, 3:24 AM Spycrowsoft wrote: > You can take it as I am not actively looking for more slackbuilds to > maintain. > > But if you are not willing to do so, I will take up the work. > Op 25-04-2021 om 00:02 schreef Jeremy Hansen: > > On Sat, Apr 24, 2021, 1:58 PM Dave Woodfall wrote: > >> On 24/04/21 13:45, >> Jeremy Hansen put forth the proposition: >> > On Sat, Apr 24, 2021, 7:24 AM Dave Woodfall >> wrote: >> > > On 02/11/20 22:29, >> > > Jeremy Hansen put forth the proposition: >> > > > I haven't used it before, but I was a big fan of the old amarok. If >> > > someone >> > > > already uses it and wants to take over, I'm totally fine with that, >> but >> > > if >> > > > no one else claims it by the end of the week, I'll take it over. >> > > > Jeremy >> > > >> > > Would you like to take it on still? >> > > >> > I'd be happy to take it, but since Spycrowsoft stated they're actually >> > using it and are willing to maintain it, I'll give them the opportunity >> to >> > take it on if they want. >> > Jeremy >> >> I can't find a message from him about it, but OK. >> > > Looks like they sent that message directly to me. > > I am actively using it. >> >> >>> I want to give others the option of taking over this slackbuild first, >>> but if no one else takes over, I will do so. >> >> >>> Spycrowsoft >> >> > I'm adding them directly to the email. > > @Spycrowsoft, feel free to take over maintenance if you're still > interested. Otherwise let me know and I'll take over. > > Jeremy > > Dave, Since Spycrowsoft is not interested in maintaining it, I'll take clementine and will submit the change once submissions reopen. If you want to just change it to my info on your branch, that's fine too. Name: Jeremy Hansen Email: jebrhansen+SBo at gmail.com Jeremy -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Mon Apr 26 05:21:15 2021 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Mon, 26 Apr 2021 12:21:15 +0700 Subject: [Slackbuilds-users] Clementine up for grabs In-Reply-To: References: <20201102192126.GH32281@blackswan.r0t.uk> <20210424132428.GC24213@localhost> <20210424195800.GD24213@localhost> <398ceaa4-2d50-b442-1fc7-9a58a6489f82@gmail.com> Message-ID: <415bacec-5a8e-6d29-3d1b-388241565340@slackbuilds.org> > Name: Jeremy Hansen > Email: jebrhansen+SBo at gmail.com It's now yours Jeremy -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From slackcoder at server.ky Wed Apr 28 13:37:50 2021 From: slackcoder at server.ky (Slack Coder) Date: Wed, 28 Apr 2021 08:37:50 -0500 Subject: [Slackbuilds-users] Jansson SlackBuild uses unofficial mirror Message-ID: Hi, It appears the Jansson SlackBuild uses an unofficial mirror for its download.? Is this ok or discouraged for SlackBuild.org's scripts? https://raw.githubusercontent.com/asterisk/third-party/master/jansson/2.12/jansson-2.12.tar.bz2 instead of https://digip.org/jansson/releases/jansson-2.12.tar.bz2 Thanks, Slack Coder From matteo.bernardini at gmail.com Wed Apr 28 13:49:00 2021 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 28 Apr 2021 15:49:00 +0200 Subject: [Slackbuilds-users] Jansson SlackBuild uses unofficial mirror In-Reply-To: References: Message-ID: it might happen that the official mirror is unreachable (for various reasons) so, in these cases, the download link is updated with some mirror locations: this is most probably what is happened with jansson (that was submitted with the official download link on SBo). in any case that's actually not a problem as long as the md5sum of the file is the same (and in this case it is). Matteo Il giorno mer 28 apr 2021 alle ore 15:37 Slack Coder ha scritto: > > Hi, > > It appears the Jansson SlackBuild uses an unofficial mirror for its > download. Is this ok or discouraged for SlackBuild.org's scripts? > > https://raw.githubusercontent.com/asterisk/third-party/master/jansson/2.12/jansson-2.12.tar.bz2 > > instead of > > https://digip.org/jansson/releases/jansson-2.12.tar.bz2 > > Thanks, > > Slack Coder > > _______________________________________________ > 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 gen-bch at useyouresp.org.uk Fri Apr 30 09:16:38 2021 From: gen-bch at useyouresp.org.uk (Habs) Date: Fri, 30 Apr 2021 10:16:38 +0100 (BST) Subject: [Slackbuilds-users] linphone 404 not found Message-ID: Hello euan@ >From a month ago or so that I first mentioned to the list and yourself, there are still [a few] '404 not found' being returned for source packages re:linphone e.g. from slackbuilds page: https://www.linphone.org/releases/sources/linphone/linphone-3.12.0.tar.gz Is it still being maintained, or is it in hand ? Regards, best wishes Habs --- Sent using Alpine/Pine, probably the best MUA --- My Tox Messaging Id: 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925 https://tox.chat/ From info at microlinux.fr Sat Apr 10 16:14:42 2021 From: info at microlinux.fr (Nicolas Kovacs) Date: Sat, 10 Apr 2021 16:14:42 -0000 Subject: [Slackbuilds-users] Broken link for squidguard In-Reply-To: References: <20210410152011.GA17166@rhea.titan.net> Message-ID: Le 10/04/2021 ? 18:07, Matteo Bernardini a ?crit?: > well, Niki actually dropped maintainership a while ago, so if you feel > like stepping in as a maintainer, CRTS, the script is yours. > > Matteo The only problem here is, I haven't used Slackware anymore since 2017. I moved my servers to a mix of CentOS and Oracle Linux, and my workstations are all running OpenSUSE Leap. Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info at microlinux.fr T?l. : 04 66 63 10 32 Mob. : 06 51 80 12 12