From willysr at slackbuilds.org Sat Feb 1 03:29:15 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 Feb 2025 10:29:15 +0700 Subject: [Slackbuilds-users] Updates - 20250201.1 Message-ID: <0b9bbaec-05fb-4ac7-ba52-ff7d5f2dd8d7@slackbuilds.org> Sat Feb 1 03:18:31 UTC 2025 academic/getfem: Updated for version 5.4.3. academic/gplates: Fix build against gwt. academic/ngspice: Fix VERSION. academic/plus42: Updated for version 1.2b audio/mixxx: Updated for version 2.5.0. desktop/nwg-panel: updated for version 0.9.61. desktop/nwg-shell-config: updated for version 0.5.56. desktop/pekwm: Updated for version 0.3.2. desktop/ufetch: Fix WM detection. development/OpenJDK11: Updated for version 11.0.26. development/OpenJDK17: Updated for version 17.0.14. development/OpenJDK21: Updated for version 21.0.6. development/abseil-cpp: Version bump to 20240722.1 development/aws-cdk: Updated for version 2.177.0. development/bacon: Updated for version 5.0.1. development/codespell: Updated for version 2.4.0. development/cosmocc: Updated for version 4.0.2. development/cproto: Updated for version 4.7x. development/diffosocpe: updated for version 286 development/gambas3: Updated for version 3.20.1. development/jdk23: Updated URL/sources development/kotlin: Updated for version 2.1.10. development/lazarus: Updated for version 3.8 development/mongodb-compass: Updated for version 1.45.2. development/mysql-workbench: Updated for version 8.0.41. development/notepadqq: Updated for version 20241111_632be8b development/obsidian: Updated for version 1.8.3. development/pahole: Updated for version 1.29. development/postman: Updated for version 11.29.5 development/pulsar: Updated for version 1.125.0. development/qbs: Updated for version 2.5.0 development/sbcl: Updated for version 2.5.1 development/tig: Updated for version 2.5.11. development/xnedit: Updated for version 1.6.1 development/yabasic: Updated for version 2.91.1 games/bstone: Updated for version 1.2.13. games/chessx: Updated for version 1.6.2. games/etlegacy: Updated for version 2.83.2. games/gzdoom: Updated for version 4.14.0. games/wesnoth: Allow optional multicore CPU builds games/wesnoth: Fix option to skip building server graphics/paraview: Tidy script ham/SoapySDRPlay: Updated for version 0.5.2. ham/qt-dab: Fix build against gwt. ham/qt-dab: Fix permission. ham/sdrangel: Update script. libraries/SOPE: Updated for version 5.11.2. libraries/dav1d: Version bump to 1.5.1 libraries/gumbo-parser: Updated for version 0.13.0. libraries/jbig2enc: Updated for version 0.30. libraries/jsoncpp: Updated for version 1.9.6. libraries/libmp4v2: Updated for version 2.1.3. libraries/libqtpas: Remove nprocr changes for now. libraries/libqtpas: Updated for version 3.8. libraries/libsixel: Updated for version 1.10.5. libraries/libslirp: Updated for version 4.9.0. libraries/libtorrent-rasterbar: Update for version 1.2.20. libraries/mimalloc: Updated for version 2.1.9. misc/OSCAR: Updated for version 1.6.0. misc/open-simh: Updated for version 20250117_feb155f multimedia/guvcview: Fix menu entry in LXDE. multimedia/inputstream.adaptive: Fix MD5SUM. multimedia/jellyfin-bin: Updated to 10.10.5 multimedia/jellyfin-media-player: Updated for version 10.11.1. multimedia/lsdvd: Updated for version 0.19. network/aerc: update to version 0.20.0 network/dante: Updated for version 1.4.4. network/discord: Version bump to 0.0.82 network/haproxy: Updated for version 3.0.8. network/hylafax+: Updated for version 7.0.10. network/kismet: Updated for version 20250128. network/linssid: Fix build against qwt. network/nextcloud-server: Updated for version 29.0.11. network/rustdesk-opt: Updated for version 1.3.7. network/signal-desktop: Updated for version 7.40.0. network/telegram: Updated for version 5.10.7. network/vivaldi: Updated for version 7.1.3570.42. network/yle-dl: Updated for version 20250126. network/yt-dlp-bin: Updated for version 2025.01.15. network/zmap: UPdated for version 4.3.2. office/Joplin: Added (note-taking application). office/Joplin: Fix permission. office/lowdown: Revert to 1.3.2. office/wps-office-dicts: Updated for version 25.2.0.3 python/colored: Updated for version 2.2.5. python/instaloader: Updated for version 4.14.1. python/python3-aiohttp: updated for version 3.11.11. python/python3-deprecated: Version bump to 1.2.17 python/python3-evdev: Version bump to 1.8.0 python/python3-netaddr: Removed python/python3-pdm: Version bump to 2.22.3 python/python3-poetry-dynamic-versioning: Updated for version 1.7.1. python/python3-soundfile: Version bump to 0.13.1 ruby/ruby-build: Updated for version 20250130. system/B-em: Updated for version 20250119_4cf85ec system/Iosevka-slab: Updated for version 32.4.0. system/Iosevka: Updated for version 32.4.0. system/dget: Updated for version 2.25.1. system/distrobox: Updated for version 1.8.1.2. system/doublecmd-qt5: Updated for version 1.1.22 system/fatrace: Updated for version 0.18.0. system/fzf: Updated for version 0.58.0. system/locust: Updated for version 2.32.6. system/lynis: Updated for version 3.1.4. system/memtester: Updated for version 4.7.1. system/mount-zip: Updated for version 1.6. system/netdata: Updated for version 2.2.0. system/netdata: Updated for version 2.2.1. system/nix: Revert optional mdBook. system/sbotools2: Updated for version 2.8.0. system/sbotools: Updated for version 3.4.1. system/usbguard: Fix #9482. system/vagrant: Updated for version 2.4.3 system/wine-staging: Updated for version 10.0. system/wine: Updated for version 10.0. system/worker: Updated for version 5.2.1 +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Feb 1 15:57:34 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 1 Feb 2025 22:57:34 +0700 Subject: [Slackbuilds-users] Updates - 20250125.1 In-Reply-To: References: <19e36f83-c549-4d18-8068-2ceb3c8f90b9@slackbuilds.org> Message-ID: <43384564-b266-4be2-bed9-24f2b5c8af7a@slackbuilds.org> >> python/python3-setuptools-opt: Remove dep. > > Willy has reverted that commit for the next update. > > It shouldn't have made it through my testing, but I made a mistake. > > Sorry for the hassle. I thought i made the revert already, but somehow it didn't get pushed :( -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From erich.public at protonmail.com Mon Feb 3 17:09:27 2025 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 03 Feb 2025 17:09:27 +0000 Subject: [Slackbuilds-users] Using OpenBLAS with getfem Message-ID: <1jJKN6dCjadBsClhzetyXF_aZauavBSte7N3M5HzaMHmghmII9bsrbbbdYlOtCMUpKibYQrryeRfIItC40sLp34vJEfN9W0_9XnAHXJ6ZTc=@protonmail.com> Hello all, getfem recently added superlu as a dependency, which itself needs a blas library. I prefer to always use OpenBLAS (and superlue suggests it as well), but initially building getfem failed (it failed to find a blas library). I was able to get the build to succeed by adding: --with-blas=openblas \ to the configure line in getfem.SlackBuild. (I also verified in getfem's build log that it found and used both OpenBLAS and superlu.) What is the best way to support using OpenBLAS with getfem? I prefer not to carry my own patch. Erich From fellype at gmail.com Mon Feb 3 18:27:17 2025 From: fellype at gmail.com (Fellype) Date: Mon, 3 Feb 2025 15:27:17 -0300 Subject: [Slackbuilds-users] Using OpenBLAS with getfem In-Reply-To: <1jJKN6dCjadBsClhzetyXF_aZauavBSte7N3M5HzaMHmghmII9bsrbbbdYlOtCMUpKibYQrryeRfIItC40sLp34vJEfN9W0_9XnAHXJ6ZTc=@protonmail.com> References: <1jJKN6dCjadBsClhzetyXF_aZauavBSte7N3M5HzaMHmghmII9bsrbbbdYlOtCMUpKibYQrryeRfIItC40sLp34vJEfN9W0_9XnAHXJ6ZTc=@protonmail.com> Message-ID: Hi Erich, Enabling superlu (or/and mumps) is required to build getfem. I chose superlu because it is already in the SBo repo. I don't want to add OpenBLAS as a dependency to getfem. But I can add a variable to allow users to pass openblas as an argument to the build script, with blas as the default option. Probably something like this: BLAS=${BLAS:-blas} ... --with-blas=$BLAS \ ... Then you can just build getfem with: BLAS=openblas sh getfem.SlackBuild Does it work for you? If you or someone else have a better way to implement this, please let me know. Regards, Fellype On Mon, Feb 3, 2025 at 2:09?PM Erich Ritz wrote: > Hello all, > > getfem recently added superlu as a dependency, which itself needs a blas > library. I prefer to always use OpenBLAS (and superlue suggests it as > well), but initially building getfem failed (it failed to find a blas > library). > > I was able to get the build to succeed by adding: > > --with-blas=openblas \ > > to the configure line in getfem.SlackBuild. (I also verified in getfem's > build log that it found and used both OpenBLAS and superlu.) > > What is the best way to support using OpenBLAS with getfem? I prefer not > to carry my own patch. > > Erich > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erich.public at protonmail.com Mon Feb 3 19:55:36 2025 From: erich.public at protonmail.com (Erich Ritz) Date: Mon, 03 Feb 2025 19:55:36 +0000 Subject: [Slackbuilds-users] Using OpenBLAS with getfem In-Reply-To: References: <1jJKN6dCjadBsClhzetyXF_aZauavBSte7N3M5HzaMHmghmII9bsrbbbdYlOtCMUpKibYQrryeRfIItC40sLp34vJEfN9W0_9XnAHXJ6ZTc=@protonmail.com> Message-ID: On Monday, February 3rd, 2025 at 12:27 PM, Fellype wrote: > Hi Erich, > > Enabling superlu (or/and mumps) is required to build getfem. I chose superlu because it is already in the SBo repo. > I don't want to add OpenBLAS as a dependency to getfem. But I can add a variable to allow users to pass openblas as an argument to the build script, with blas as the default option. > Probably something like this: > BLAS=${BLAS:-blas} > ... > > --with-blas=$BLAS \ > ... > > Then you can just build getfem with: > BLAS=openblas sh getfem.SlackBuild > Does it work for you? > If you or someone else have a better way to implement this, please let me know. > Yes, this would work perfect for me. > Regards, > Fellype > Erich From willysr at slackbuilds.org Sat Feb 8 02:48:55 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 8 Feb 2025 09:48:55 +0700 Subject: [Slackbuilds-users] Updates - 20250208.1 Message-ID: <80dcb077-26b0-4ecb-b8e6-842730651bfb@slackbuilds.org> Sat Feb 8 02:33:49 UTC 2025 academic/gcompris-qt: Updated for version 25.0. academic/getfem: Updated for version 5.4.4. academic/nco: Updated for version 5.3.2. academic/plus42: Updated for version 1.2.2 audio/drumkv1: Updated for version 1.3.0. audio/ncspot: Updated for version 1.2.2. audio/padthv1: Updated for version 1.3.0. audio/samplv1: Updated for version 1.3.0. audio/synthv1: Updated for version 1.3.0. desktop/SiriKali: Updated for version 1.8.1. desktop/gfi: Updated for version 0.3.0. desktop/orage: Updated for version 4.20.0. desktop/paginator: Added (desktop pager dockapp). desktop/papirus-icon-theme: Updated for version 20250201. desktop/rss-guard: updated for version 4.8.1 desktop/wmctrl: Fix docs. desktop/xwallpaper: Updated for version 0.7.6. development/aws-cdk: Updated for version 2.178.0. development/c_count: Updated for version 7.24, rename binary. development/cloc: Version bump to 2.04 development/crosstool-ng: Updated for version 1.27.0 development/cunit: new maintainer development/diffoscope: updated for version 287 development/dkms: Updated for version 3.1.5 development/ghex: Updated for version 46.2. development/github-cli: Updated for version 2.66.1 development/hugo: update 0.143.0 development/obsidian: updated for version 1.8.4 development/pnpm: Updated for version 9.15.5. development/postman: Updated for version 11.30.4 development/qbs: Updated for version 2.5.1 development/rust-opt: Updated for version 1.84.1. development/sysprof: Update meson options. development/tea: updated for version 63.2.0 development/tflint: Updated for version 0.55.1. development/tig: Updated for version 2.5.12. development/tiled: updated for version 1.11.2 development/vscode-bin: Updated for version 1.97.0. development/zope.interface: updated for version 7.2 games/ags: updated for version 3.6.1.31 games/endless-sky: updated for version 0.10.11 games/freeciv: updated for version 3.1.4 games/homm3_shareware_data: new maintainer games/lgogdownloader: updated for version 3.16 games/mame: Updated for version 0.274. games/pioneer: Apply bugfix patches. games/pioneer: Updated for version 20250203. games/scid_vs_pc: Updated for version 4.26. games/warzone2100: updated for version 4.5.5 graphics/graphviz: updated for version 12.2.1 graphics/nsxiv: Updated for version 33 graphics/vuescan: Updated for version 9.8.44. ham/sdrangel: Updated for version 7.22.6. ham/sdrpp: Updated for version 20250203.e0f90532. libraries/VTK: Updated for version 9.4.1 libraries/allegro: updated for version 5.2.10.1 libraries/libjcat: Updated for version 0.2.3. libraries/libjwt: updated for version 2.1.1 libraries/libwbxml: Added (Parse, encode and handle WBXML documents). libraries/libwpe: Updated for version 1.16.2. libraries/libxnvctrl: Updated for version 565.77. libraries/lualdap: Added (LUA Binding for OpenLDAP). libraries/protobuf-c: Updated for version 1.5.1. libraries/webkit2gtk4.1: Updated for version 2.46.6. libraries/webkit2gtk: Updated for version 2.46.6. libraries/zope.configuration: updated for version 6.0 libraries/zope.hookable: updated for version 7.0 libraries/zope.i18nmessageid: updated for version 7.0 libraries/zope.location: updated for version 5.1 libraries/zope.proxy: updated for version 6.1 libraries/zope.security: updated for version 7.3 misc/bitwarden-desktop: updated for version 2025.1.4 misc/yubioath-desktop: Update script. multimedia/picard-plugins: Version bump to 277aa4d multimedia/picard: Version bump to 2.13.1 multimedia/pipe-viewer: Updated for version 0.5.4. network/aerc: Updated for version 0.20.1 network/asterisk: Updated for version 22.1.1. network/brave-browser: update 1.74.51 network/darkhttpd: added rc script, config file, and default page network/discord: Version bump to 0.0.84 network/dropbox: Updated for version 217.4.4417. network/lldpd: Updated for version 1.0.19. network/protonmail-bridge: Updated for version 3.16.0. network/rclone: update 1.69.0 network/signal-desktop: Updated for version 7.41.0. network/skypeforlinux: Updated for version 8.136.0.202. network/snac2: Added (minimalistic ActivityPub instance). network/snac2: Fix permission. network/syncthingtray-bin: Updated for version 1.7.2. network/tailscale: update 1.80.0 network/teamviewer: Updated for version 15.62.4. network/tixati: Fix the icon file type. network/tor-browser: Updated for version 14.0.5. network/uwsgi: updated for version 2.0.28 network/vivaldi: Updated for version 7.1.3570.47. network/yt-dlp-bin: Updated for version 2025.01.26. network/yt-dlp: Updated for version 2025.01.26. office/LibreOffice: Updated for version 25.2.0.3 office/libreoffice-helppack: Updated for version 25.2.0. office/libreoffice-langpack: Updated for version 25.2.0. office/libreoffice: Updated for version 25.2.0. office/onlyoffice-desktopeditors: Updated for version 8.3.0 office/pandoc-bin: update 3.6.2 perl/perl-Mail-DMARC: Updated for version 1.20250203. perl/perl-io-uncompress-brotli: Added (brotli support for perl). python/PyGreSQL: Updated for version 6.1.0 python/PyPy3: updated for version 7.3.18 python/PyPy: updated for version 7.3.18 python/esptool: New maintainer. Add dep on python3-intelHex. python/pypy3: updated for version 7.3.18 python/pypy: updated for version 7.3.18 python/python3-BTrees: updated for version 6.1 python/python3-ZConfig: updated for version 4.2 python/python3-amqp: updated for version 5.3.1 python/python3-automat: updated for version 24.8.1 python/python3-babel: updated for version 2.17.0 python/python3-bcrypt: updated for version 4.2.1 python/python3-billiard: updated for version 4.2.1 python/python3-bleach: updated for version 6.2.0 python/python3-bottle: updated for version 0.13.2 python/python3-cython-opt: Added (Superset of Python). python/python3-dnspython: updated for version 2.7.0 python/python3-dulwich: updated for version 0.22.7 python/python3-formencode: updated for version 2.1.1 python/python3-incremental: updated for version 24.7.2 python/python3-intelHex: Added (Python Library). python/python3-kombu: updated for version 5.4.2 python/python3-lazr.config: updated for version 3.1 python/python3-lazr.delegates: updated for version 2.1.1 python/python3-mailman: updated for version 3.3.10 python/python3-paginate: updated for version 0.5.7 python/python3-persistent: updated for version 6.1 python/python3-prompt_toolkit: updated for version 3.0.50 python/python3-psycopg2: updated for version 2.9.10 python/python3-pyasn1-modules: updated for version 0.4.1 python/python3-pyasn1: updated for version 0.6.1 python/python3-service-identity: updated for version 24.2.0 python/python3-setuptools-opt: Restore dep. python/python3-socks: Updated for version 2.7.1. python/python3-transaction: updated for version 5.0 python/python3-twisted: updated for version 24.11.0 python/python3-waitress: updated for version 3.0.2 python/python3-webob: updated for version 1.8.9 python/python3-zodbpickle: updated for version 4.1.1 ruby/ruby-build: Updated for version 20250205. system/Iosevka-aile: Updated for version 32.5.0. system/Iosevka-etoile: Updated for version 32.5.0. system/Iosevka: Updated for version 32.5.0 system/chkrootkit: Make the install routine $LANG-safe. system/dosbox-x: updated for version 2025.02.01 system/duperemove: Pass $VERSION to Makefile system/fzf: Fix version of the encoding module in the info file. system/fzf: Updated for version 0.59.0. system/jenkins: Updated for version 2.492.1. system/netdata: Updated for version 2.2.3. system/netdata: Updated for version 2.2.4. system/pgbadger: updated for version 13.0 system/psensor: Added (HW Temp Monitoring Tool). system/pv: updated for version 1.9.31 system/redict: updated for version 7.3.2 system/redis-py: updated for version 5.2.1 system/redis: updated for version 7.4.2 system/sarasa-gothic: Updated for version 1.0.28. system/sbokeeper: Updated for version 2.04. system/sbotools: Updated for version 3.4.2. system/unionfs-fuse: updated for version 3.6 system/valkey: updated for version 8.0.2 system/winetricks: updated for version 20250102 system/yash: Updated for version 2.58. system/yash: Updated for version 2.58.1. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From bobfunk11 at gmail.com Mon Feb 10 22:36:41 2025 From: bobfunk11 at gmail.com (Bob Funk) Date: Mon, 10 Feb 2025 16:36:41 -0600 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: Message-ID: The source URL for gnome-desktop has been 404'd for a number of weeks now. It is a dependency to a number of my slackbuilds: https://slackbuilds.org/advsearch.php?q=gnome-desktop&stype=revdep1 I sent an email to the maintainer two weeks ago, which is what I forwarded in the remainder of this email to show my previous message. I still haven't heard back. Do we know if Gustavo is still active? I could have missed the memo if he did drop out. Like I said in my other email, I will happily take over this slackbuild and update the source URL if needed. Thanks, Bob ---------- Forwarded message --------- From: Bob Funk Date: Mon, Jan 27, 2025 at 8:42?PM Subject: gnome-desktop SlackBuild source is 404'd To: Hi Gustavo, Your slackbuild for gnome-desktop-41.1 no longer has a valid source URL to download, causing build failure. Please update the .info file to a better source download, for example this one works fine: https://download.gnome.org/sources/gnome-desktop/41/gnome-desktop-41.1.tar.xz If you are no longer using this slackbuild or maintaining it, I would gladly take over and update it for you with your permission. Thanks, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From urchlay at slackware.uk Tue Feb 11 00:03:43 2025 From: urchlay at slackware.uk (B. Watson) Date: Mon, 10 Feb 2025 19:03:43 -0500 (EST) Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: Message-ID: On Mon, 10 Feb 2025, Bob Funk wrote: > The source URL for gnome-desktop has been 404'd for a number of weeks now.? > > It is a dependency to a number of my slackbuilds: > https://slackbuilds.org/advsearch.php?q=gnome-desktop&stype=revdep1 Wonder why he used the "fallback" URL. download-fallback.gnome.org doesn't resolve any more. This URL works: https://download.gnome.org/sources/gnome-desktop/41/gnome-desktop-41.1.tar.xz > I sent an email to the maintainer two weeks ago, which is what I forwarded in the remainder of this email to show my previous message. > > I still haven't heard back. Do we know if Gustavo is still active? I could have missed the memo if he did drop out. I don't know if he ever announced he was leaving, but his last activity was about a year ago: commit 459ee916938fd89ec6505e13087ddd5293714ec0 Author: Gustavo B. Schenkel Date: Thu Feb 22 21:37:02 2024 +0700 development/opentofu: Added (fork of terraform). ...and all but two of his builds have been taken over by other maintainers. > Like I said in my other email, I will happily take over this slackbuild and update the source URL if needed. Go ahead and take over. You said it's been two weeks... if Gustavo shows up and wants his build back, you guys can work it out between yourselves. Also: If anyone's interested in opentofu, feel free to take it over. Nothing in the repo depends on it. There have been quite a few upstream releases since it was last updated on SBo, so it needs attention if it's going to stay in the repo. From willysr at slackbuilds.org Tue Feb 11 01:51:35 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Tue, 11 Feb 2025 08:51:35 +0700 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: Message-ID: > The source URL for gnome-desktop has been 404'd for a number of weeks now. > > It is a dependency to a number of my slackbuilds: > https://slackbuilds.org/advsearch.php?q=gnome-desktop&stype=revdep1 > > > I sent an email to the maintainer two weeks ago, which is what I > forwarded in the remainder of this email to show my previous message. > > I still haven't heard back. Do we know if Gustavo is still active? I > could have missed the memo if he did drop out. > > Like I said in my other email, I will happily take over this slackbuild > and update the source URL if needed. Gustavo was active in IRC yesterday (gbschenkel) try to contact him via IRC -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From urchlay at slackware.uk Tue Feb 11 20:37:40 2025 From: urchlay at slackware.uk (B. Watson) Date: Tue, 11 Feb 2025 15:37:40 -0500 (EST) Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: Message-ID: On Tue, 11 Feb 2025, Gustavo Brondani Schenkel wrote: > Also as I sad on the weekend on #slackbuilds liberachat, if gitlab or github > was used and submit zone to the packages, we could use CODEOWNER to involve > all package maintainers, then Bob Funk could have updated the package for me > just give my thumbs up, or open an Issue, the email will not be disused > because GitLab will send it. You vanished from IRC before I could reply to that... Your scheme would require all SBo maintainers and admins to create github/gitlab accounts. We're not going to require that. Even if we did, it wouldn't help with new submissions (rather than updates to existing builds). Those *must* go through the web form to populate our database correctly. What's so hard about using email? All you had to do was answer Bob Funk's mail... he didn't see a reply for a couple of weeks so I mistakenly assumed that meant you weren't maintaining your build, and gave him permission to take it over. From gustavo.schenkel at gmail.com Tue Feb 11 11:39:31 2025 From: gustavo.schenkel at gmail.com (Gustavo Brondani Schenkel) Date: Tue, 11 Feb 2025 08:39:31 -0300 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: Message-ID: Hi, OpenTofu was updated this weekend on GitLab. Gnome-Desktop, I will update it, but I can relay the maintenance of it to someone else, I only created as Lutris dependency and I not using anything else gnome related. Also as I sad on the weekend on #slackbuilds liberachat, if gitlab or github was used and submit zone to the packages, we could use CODEOWNER to involve all package maintainers, then Bob Funk could have updated the package for me just give my thumbs up, or open an Issue, the email will not be disused because GitLab will send it. PS: The slackbuilds filter wasn't working, I have correct it now. On 2/10/25 9:03 PM, B. Watson wrote: > > > On Mon, 10 Feb 2025, Bob Funk wrote: > >> The source URL for gnome-desktop has been 404'd for a number of weeks >> now. >> >> It is a dependency to a number of my slackbuilds: >> https://slackbuilds.org/advsearch.php?q=gnome-desktop&stype=revdep1 > > Wonder why he used the "fallback" URL. download-fallback.gnome.org > doesn't resolve any more. > > This URL works: > > https://download.gnome.org/sources/gnome-desktop/41/gnome-desktop-41.1.tar.xz > > >> I sent an email to the maintainer two weeks ago, which is what I >> forwarded in the remainder of this email to show my previous message. >> >> I still haven't heard back. Do we know if Gustavo is still active? I >> could have missed the memo if he did drop out. > > I don't know if he ever announced he was leaving, but his last > activity was about a year ago: > > commit 459ee916938fd89ec6505e13087ddd5293714ec0 > Author: Gustavo B. Schenkel > Date:?? Thu Feb 22 21:37:02 2024 +0700 > > ??? development/opentofu: Added (fork of terraform). > > ...and all but two of his builds have been taken over by other > maintainers. > >> Like I said in my other email, I will happily take over this >> slackbuild and update the source URL if needed. > > Go ahead and take over. You said it's been two weeks... if Gustavo > shows up and wants his build back, you guys can work it out between > yourselves. > > Also: If anyone's interested in opentofu, feel free to take it > over. Nothing in the repo depends on it. There have been quite a > few upstream releases since it was last updated on SBo, so it needs > attention if it's going to stay in the repo. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x4EEB0BCD843194ED.asc Type: application/pgp-keys Size: 13799 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 4798 bytes Desc: OpenPGP digital signature URL: From gustavo.schenkel at gmail.com Tue Feb 11 22:40:02 2025 From: gustavo.schenkel at gmail.com (Gustavo Brondani Schenkel) Date: Tue, 11 Feb 2025 19:40:02 -0300 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: Message-ID: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> We could use pipelines to populate the database, but okay, the pipelines could also check if the package build on a pristine Slackware 15.0, and the project on GitLab is already doing a pipeline with a job, is only matter to improve it. As I mention, I didn't saw Bob's email, it went on junk by mistake, from a rule which was suppose to send to specific folder, like the messages from LQ and Google Groups. About a email, when I was waiting 4 months with the script for Packer and Terraform to submit, you guys sad to "wait is not ready yet", then I couldn't check the site for 3 days, and someone else has submitted a package and was accepted. I personally put all my Slackware work on gitlab.com/slackware-brazil/slackbuilds and in git.schenkel.eti.br where I am building a sbo-o-matic to auto compile all slackbuilds using a VM on Proxmox which each time it build and upload the package, it reboot and restore the latest snapshot to remain immutable. Still a WIP and I am building only packages which I use on my workstation. I still want to use Anitya(release monitoring project) together to create a Issue about a new version. We could have contributing directly, just editing the text directly from GitLab, but since you don't accept work from non-maintainer, this can't happen, which is funny because since I submitted the gnome-desktop I didn't received any message from any who altered the code until now. Where is the transparency when changing the code from other people? PS: I just submitted gnome-desktop on the same MR waiting on GitLab. On 2/11/25 5:37 PM, B. Watson wrote: > > > On Tue, 11 Feb 2025, Gustavo Brondani Schenkel wrote: > >> Also as I sad on the weekend on #slackbuilds liberachat, if gitlab or >> github was used and submit zone to the packages, we could use >> CODEOWNER to involve all package maintainers, then Bob Funk could >> have updated the package for me just give my thumbs up, or open an >> Issue, the email will not be disused because GitLab will send it. > > You vanished from IRC before I could reply to that... > > Your scheme would require all SBo maintainers and admins to create > github/gitlab accounts. We're not going to require that. > > Even if we did, it wouldn't help with new submissions (rather than > updates to existing builds). Those *must* go through the web form to > populate our database correctly. > > What's so hard about using email? All you had to do was answer > Bob Funk's mail... he didn't see a reply for a couple of weeks so I > mistakenly assumed that meant you weren't maintaining your build, and > gave him permission to take it over. -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x4EEB0BCD843194ED.asc Type: application/pgp-keys Size: 13799 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 4798 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Wed Feb 12 03:30:17 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Wed, 12 Feb 2025 10:30:17 +0700 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> References: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> Message-ID: > We could use pipelines to populate the database, but okay, the pipelines > could also check if the package build on a pristine Slackware 15.0, and > the project on GitLab is already doing a pipeline with a job, is only > matter to improve it. No, that's not how the infrastructure works it only works from submission form and we want the main git repository in our SBo server, not from github/gitlab. They are just used for CI automation only. > About a email, when I was waiting 4 months with the script for Packer > and Terraform to submit, you guys sad to "wait is not ready yet", then I > couldn't check the site for 3 days, and someone else has submitted a > package and was accepted. when was this? i don't recall about terraform submission besides Andrew Clemon's. > I personally put all my Slackware work on gitlab.com/slackware-brazil/ > slackbuilds and in git.schenkel.eti.br where I am building a sbo-o-matic > to auto compile all slackbuilds using a VM on Proxmox which each time it > build and upload the package, it reboot and restore the latest snapshot > to remain immutable. Still a WIP and I am building only packages which I > use on my workstation. I still want to use Anitya(release monitoring > project) together to create a Issue about a new version. > > We could have contributing directly, just editing the text directly from > GitLab, but since you don't accept work from non-maintainer, this can't > happen, which is funny because since I submitted the gnome-desktop I > didn't received any message from any who altered the code until now. You can always see who changes your code from git history. We (admins) normally avoid changing things unless it's necessary (broken, security vulnerabilities, etc). Sometimes we might miss if someone update other people's script, but we tried to avoid this as well. > Where is the transparency when changing the code from other people? We do have policy of giving maintainer time to adjust their scripts if they are unavailable (usually around 1-2 weeks). If no reply within that time frame, other people may ask in the mailing list if they could take over and we (admins) can take a look on the activity of the maintainer. > PS: I just submitted gnome-desktop on the same MR waiting on GitLab. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From bobfunk11 at gmail.com Wed Feb 12 03:48:12 2025 From: bobfunk11 at gmail.com (Bob Funk) Date: Tue, 11 Feb 2025 21:48:12 -0600 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> Message-ID: So on the topic of gnome-desktop: I haven't put in any pull requests for updates or maintainer changes yet, and it sounds like Gustavo has that taken care of now. I'll consider this issue solved then. Bob On Tue, Feb 11, 2025, 21:30 Willy Sudiarto Raharjo wrote: > > We could use pipelines to populate the database, but okay, the pipelines > > could also check if the package build on a pristine Slackware 15.0, and > > the project on GitLab is already doing a pipeline with a job, is only > > matter to improve it. > > No, that's not how the infrastructure works > it only works from submission form and we want the main git repository > in our SBo server, not from github/gitlab. They are just used for CI > automation only. > > > About a email, when I was waiting 4 months with the script for Packer > > and Terraform to submit, you guys sad to "wait is not ready yet", then I > > couldn't check the site for 3 days, and someone else has submitted a > > package and was accepted. > > when was this? i don't recall about terraform submission besides Andrew > Clemon's. > > > I personally put all my Slackware work on gitlab.com/slackware-brazil/ > > slackbuilds and in git.schenkel.eti.br where I am building a > sbo-o-matic > > to auto compile all slackbuilds using a VM on Proxmox which each time it > > build and upload the package, it reboot and restore the latest snapshot > > to remain immutable. Still a WIP and I am building only packages which I > > use on my workstation. I still want to use Anitya(release monitoring > > project) together to create a Issue about a new version. > > > > We could have contributing directly, just editing the text directly from > > GitLab, but since you don't accept work from non-maintainer, this can't > > happen, which is funny because since I submitted the gnome-desktop I > > didn't received any message from any who altered the code until now. > > You can always see who changes your code from git history. > We (admins) normally avoid changing things unless it's necessary > (broken, security vulnerabilities, etc). Sometimes we might miss if > someone update other people's script, but we tried to avoid this as well. > > > Where is the transparency when changing the code from other people? > > We do have policy of giving maintainer time to adjust their scripts if > they are unavailable (usually around 1-2 weeks). If no reply within that > time frame, other people may ask in the mailing list if they could take > over and we (admins) can take a look on the activity of the maintainer. > > > PS: I just submitted gnome-desktop on the same MR waiting on GitLab. > > > -- > 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 urchlay at slackware.uk Wed Feb 12 07:42:24 2025 From: urchlay at slackware.uk (B. Watson) Date: Wed, 12 Feb 2025 02:42:24 -0500 (EST) Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> References: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> Message-ID: <591970da-416a-4bdf-de17-39fca26fd1b1@slackware.uk> OK, this got a bit long and started turning into a FAQ. Bear with me, hopefully it helps explain. However, don't take this as "the party line", SBo deliberately doesn't have by-laws, parliamentary procedure, a "steering committe", or any of the formal stuff a large project might have. It makes us flexible, but it also makes us inconsistent: you might get a different answer depending on which admin you ask. What you see in this email is my take on the situation, and other admins might respond with their ideas. On Tue, 11 Feb 2025, Gustavo Brondani Schenkel wrote: > About a email, when I was waiting 4 months with the script for Packer and > Terraform to submit, you guys sad to "wait is not ready yet", then I couldn't > check the site for 3 days, and someone else has submitted a package and was > accepted. That, I wasn't involved in. Was this during the time right after 15.0 released, and the submission form on the site was closed? ...it looks like it might have been. Terraform was added on March 31, 2022, less than 2 months after Slackware 15.0 got released. So you had it ready to submit, but submissions were closed... and when submissions opened again, someone else submitted it. I'm not sure how to avoid that happening. It was just bad timing. You had let someone know that you had these ready to submit, but it got forgotten about for whatever reason. See the bottom of this email, the part about "development cycle", which might give you an idea what was going on during that time. > We could have contributing directly, just editing the text directly from > GitLab, but since you don't accept work from non-maintainer, this can't > happen, which is funny because since I submitted the gnome-desktop I didn't > received any message from any who altered the code until now. We don't accept changes from anyone but the maintainer, *or* from one of us (the SBo team), *or* from someone who got permission from the maintainer. All the changes are in the SBo git log. You can clone the repo and run "git log libraries/gnome-desktop" or view it with a web browser here: https://git.slackbuilds.org/slackbuilds/log/libraries/gnome-desktop Looking at the commits, two of them are yours... Willy and Heinz are SBo admins. Heinz's changes were applied repo-wide to all builds: everything has the "Support $PRINT_PACKAGE_NAME", "SlackBuilds run in the directory they are in", and "Change SlackBuild shebang to /bin/bash" in its history, and everything that uses ninja has the "Support alternatives for ninja" there. Willy's update was to remove libseccomp from REQUIRES, possibly because it's not actually required. When SBo admins make changes to the SBo git tree, no automatic emails are sent. This is because we use git (withiout any github/gitlab extensions) for the primary repo, and git doesn't send emails. Normally, we *do* email you before messing with your build. But sometimes trivial changes (changing the DOWNLOAD to a mirror site because the original went away) don't seem worth an email. The system-wide changes (which reflect changes in the template) affected thousands of builds. They are rare, and they are announced on the mailing list when they happen. You're expected to periodically rebase your git branch on master, notice the changes in the log, and if there's something that you don't like, you email whoever made the change. I *am* kind of curious about the commit by Igor Alexandrov. He did a version update, but didn't change the maintainer info to his own name/email. Was this done with your knowledge and permission? Someone on the SBo team must have approved it: normally if we get a submission or PR on a build from someone other than the maintainer, we contact the maintainer and ask if it's OK. Did anyone contact you about commit 90594b47526e025e7f17a60c1b504f752cfa8d02 back when it happened (June 13, 2021)? > Where is the transparency when changing the code from other people? The code changes and the people who did them are in the git log. What other transparency should there be? There is also another factor: there are two alternating "cycles" at SBo. Normally we're in "release cycle", which is the usual state. When a new Slackware release is made (or maybe a bit before, when a release candidate or beta is released), we close the submission form and go into "development cycle". It takes a lot of man-hours of work to update all the builds from e.g. 14.2 to work correctly with 15.0. For a given build, sometimes that just means a small change in the script, or adding a patch. Sometimes the cleanest way is to version-update the build instead of trying to patch the previous version. During the dev cycle, there's a lot of frantic scrambling by the SBo admins to get all the work done in a reasonable amount of time. As a consequence, we don't send mail to maintainers about proposed changes and wait for responses. If something needs fixing, one of us fixes it. This isn't documented anywhere because it's not something that was planned out ahead of time. It's how our practices have evolved over the years. Probably there *should* be a FAQ on the site that explains all this. From bobfunk11 at gmail.com Wed Feb 12 23:40:15 2025 From: bobfunk11 at gmail.com (Bob Funk) Date: Wed, 12 Feb 2025 17:40:15 -0600 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: <591970da-416a-4bdf-de17-39fca26fd1b1@slackware.uk> References: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> <591970da-416a-4bdf-de17-39fca26fd1b1@slackware.uk> Message-ID: B. Watson brought up this in that last email, which I have a question about: There is also another factor: there are two alternating "cycles" > at SBo. Normally we're in "release cycle", which is the usual > state. When a new Slackware release is made (or maybe a bit before, > when a release candidate or beta is released), we close the submission > form and go into "development cycle". It takes a lot of man-hours of > work to update all the builds from e.g. 14.2 to work correctly with > 15.0. For a given build, sometimes that just means a small change > in the script, or adding a patch. Sometimes the cleanest way is to > version-update the build instead of trying to patch the previous > version. > > During the dev cycle, there's a lot of frantic scrambling by the SBo > admins to get all the work done in a reasonable amount of time. As a > consequence, we don't send mail to maintainers about proposed changes > and wait for responses. If something needs fixing, one of us fixes it. > > This isn't documented anywhere because it's not something that was > planned out ahead of time. It's how our practices have evolved over > the years. Probably there *should* be a FAQ on the site that explains > all this. > Will I be able to perform pull requests and update packages during this transition period in the next release? I started maintaining slackbuilds shortly after Slackware 15.0 was released. I wasn't around as a maintainer for the transitional period of prior releases. Now I have a large number of gnome packages that I maintain. Many of these packages are fixed at 41.x release versions. This is because their underlying libraries provided in the Slackware 15.0 base install limits me to this version. Upgrading the full set would require upgrading 14 packages in the Slackware base system (last time I checked). There are also other maintainers on slackbuilds.org who maintain packages in the gnome suite of software, which are also stuck to versions for similar reasons. Some of my packages depend on those other maintainers' ones too. All these problems go away on Slackware-current, where everything is up to date. At the next release, I will have upgrades for up to 60-70 packages, all hinging on newer Slackware base packages in the next release. I can provide updated builds, and help coordinate upgrades with the maintainers I depend on. This is why I wonder if/when I can get to upgrading these packages in a transitional period. Your email sounds like admins are doing this task. Or is that just fixing what doesn't build and then maintainers make their changes after your closed "development cycle"? Some clarification would be appreciated here. Thanks in advance, Bob -------------- next part -------------- An HTML attachment was scrubbed... URL: From jebrhansen+SBo at gmail.com Wed Feb 12 23:59:30 2025 From: jebrhansen+SBo at gmail.com (Jeremy Hansen) Date: Wed, 12 Feb 2025 15:59:30 -0800 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> <591970da-416a-4bdf-de17-39fca26fd1b1@slackware.uk> Message-ID: On Wed, Feb 12, 2025, 3:40?PM Bob Funk wrote: > B. Watson brought up this in that last email, which I have a question > about: > > There is also another factor: there are two alternating "cycles" >> at SBo. Normally we're in "release cycle", which is the usual >> state. When a new Slackware release is made (or maybe a bit before, >> when a release candidate or beta is released), we close the submission >> form and go into "development cycle". It takes a lot of man-hours of >> work to update all the builds from e.g. 14.2 to work correctly with >> 15.0. For a given build, sometimes that just means a small change >> in the script, or adding a patch. Sometimes the cleanest way is to >> version-update the build instead of trying to patch the previous >> version. >> >> During the dev cycle, there's a lot of frantic scrambling by the SBo >> admins to get all the work done in a reasonable amount of time. As a >> consequence, we don't send mail to maintainers about proposed changes >> and wait for responses. If something needs fixing, one of us fixes it. >> >> This isn't documented anywhere because it's not something that was >> planned out ahead of time. It's how our practices have evolved over >> the years. Probably there *should* be a FAQ on the site that explains >> all this. >> > > Will I be able to perform pull requests and update packages during this > transition period in the next release? > > I started maintaining slackbuilds shortly after Slackware 15.0 was > released. I wasn't around as a maintainer for the transitional period of > prior releases. > > Now I have a large number of gnome packages that I maintain. Many of these > packages are fixed at 41.x release versions. This is because their > underlying libraries provided in the Slackware 15.0 base install limits me > to this version. Upgrading the full set would require upgrading 14 packages > in the Slackware base system (last time I checked). There are also other > maintainers on slackbuilds.org who maintain packages in the gnome suite > of software, which are also stuck to versions for similar reasons. Some of > my packages depend on those other maintainers' ones too. > > All these problems go away on Slackware-current, where everything is up to > date. At the next release, I will have upgrades for up to 60-70 packages, > all hinging on newer Slackware base packages in the next release. I can > provide updated builds, and help coordinate upgrades with the maintainers I > depend on. > > This is why I wonder if/when I can get to upgrading these packages in a > transitional period. Your email sounds like admins are doing this task. Or > is that just fixing what doesn't build and then maintainers make their > changes after your closed "development cycle"? > Things get a little looser during the transition period. They start by merging Matteo's (ponce) -current repo and then start testing the repo by building and testing. Programs that are broken will attempt to be fixed, sometimes by admins, sometimes by maintainers, sometimes by non-maintainers (although, it's preferable to have the blessing of the maintainer to push that fix). If they can't be fixed before the transition period ends, they'll be removed before the admins publish the repo for the new stable (taking it out of transition mode). Maintainers can still push version updates during this time, but they'll be expected to be tested against -current, the RC, or 15.1 stable release (or whatever new version number it is). I also have a number of packages waiting for newer stock packages that will be updated during this transition. As an FYI, t is frowned on to update packages that aren't yours just to update them. However, if it's broken without updating, try and get the permission of the maintainer (because they might be working on it) before you push an update to a package you don't maintain. Keep in mind that once this transition period starts, the 15.0 repo will be frozen and no further updates will be made, even before 15.1 is released. The transition period can be made easier by testing scripts against -current and fixing what you can for 15.0 SBo, but if there are conflicts that don't work with 15.0, ping Matteo to have him put the change in his -current repo. This is not required of maintainers, but can help expedite the transition to the new release. Jeremy > -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Feb 13 02:24:32 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 13 Feb 2025 09:24:32 +0700 Subject: [Slackbuilds-users] Fwd: gnome-desktop SlackBuild source is 404'd In-Reply-To: References: <57d7d1a0-4573-4e02-9e24-d59a57ccd1bf@gmail.com> <591970da-416a-4bdf-de17-39fca26fd1b1@slackware.uk> Message-ID: <671e854a-16bd-426c-a2ae-13384ed256f1@slackbuilds.org> > Things get a little looser during the transition period. They start by > merging Matteo's (ponce) -current repo and then start testing the repo > by building and testing. Programs that are broken will attempt to be > fixed, sometimes by admins, sometimes by maintainers, sometimes by non- > maintainers (although, it's preferable to have the blessing of the > maintainer to push that fix). If they can't be fixed before the > transition period ends, they'll be removed before the admins publish the > repo for the new stable (taking it out of transition mode). it's more like hell break loose during transition period :) many scripts are added, removed, changed just to make sure it built and works fine for next slackware release with the hope that we can release the new repo in the same day as next Slackware release date -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Sat Feb 15 09:59:04 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 15 Feb 2025 16:59:04 +0700 Subject: [Slackbuilds-users] Updates - 20250215.1 Message-ID: <91b38d31-662c-4ab5-9b64-000e56dc4efd@slackbuilds.org> Sat Feb 15 09:49:57 UTC 2025 academic/plus42: Updated for version 1.2.4 audio/flac-opt: Added (Audio Codec). audio/qmmp-qt5: Updated for version 1.7.3. business/exercism_repack: Added (Solving exercises). desktop/ClamAV-GUI: Updated for version 20250206_11ba095 desktop/Tela-icon-theme: Updated for version 2025_02_10. desktop/dbgl: updated for version 0.99 desktop/fvwm3: Updated for version 1.1.2. desktop/numix-icon-theme-square: Updated for version 25.01.31. desktop/numix-icon-theme: Updated for version 25.01.31. development/ChezScheme: Updated for version to 10.1 development/QtPy: Updated for version 2.4.3. development/atasm: Updated for version 1.26. development/aws-cdk: Updated for version 2.178.1. development/aws-cdk: Updated for version 2.178.2. development/dpkg: Updated for version 1.22.15. development/github-cli: Updated for version 2.67.0 development/golangci-lint: Updated for version 1.64.4. development/icon: Updated for version 9.5.24b development/ispc: Updated for version 1.26.0 development/lua-language-server: Updated for version 3.13.6. development/neovim: Updated for version 0.10.4. development/nodejs18: Updated for version 18.20.6. development/nodejs: Updated for version 20.18.3. development/notepadqq: script update development/opentofu: Updated for version 1.9.0 development/php84: Updated for version 8.4.4 development/postman: Updated for version 11.31.3 development/regina-rexx: Update script. development/robotframework: Updated for version 7.2.2. development/rr: Updated for version 5.9.0. development/textadept: updated for version 12.6 development/tracy: Added (Sampling Profiler). development/vscode-bin: Updated for version 1.97.1. development/vscode-bin: Updated for version 1.97.2. development/vstudio: Updated for version 15.0 development/xmake: Updated for version 2.9.8. development/zope.testing: Updated for version 5.1. games/armagetronad: Updated for version 0.2.9.2.3. games/mame: Add groovy patch for 0.274. games/puzzles: Updated for version 20250208.5edcabb. gis/gdal: Updated for version 3.10.2. git/ci: Update CI dependencies. graphics/drawio: Updated for version 26.0.9. graphics/lilypond: Updated for version 2.24.4 graphics/pdfsyntax: Added (Python Library). graphics/ueberzugpp: Update script. graphics/xdot: Updated for version 1.4 ham/hamlib4: Updated for version 4.6.2. ham/qlog: Updated for version 0.42.0. libraries/SDL2_sound: updated for version 2.0.4 libraries/fcitx5-rime: Updated for version 5.1.10. libraries/gnome-desktop: Updated for version 44.1 libraries/gtkada: Added (ADA Bindings for GTK). libraries/iir1: Added (C++ filter library). libraries/lib3ds: Added (Software Library). libraries/libopenshot-audio: Updated for version 0.4.0 libraries/libopenshot: Updated for version 0.4.0 libraries/ogre: Add featuresummary patch libraries/openvino: Build with tbb instead of oneTBB. libraries/openvino: Bump BUILD for dependency update. libraries/td_lib: Updated for version 20250117. libraries/tree-sitter: Updated for version 0.25.1 libraries/zita-alsa-pcmi: Ship binaries, cleanup. libraries/zlib-ng: Added (zlib data compression library). misc/autofirma: Added (Sign Digital Certificate). misc/fcitx5-chewing: Updated for version 5.1.7. misc/fcitx5-chinese-addons: Updated for version 5.1.8. misc/fcitx5-configtool: Updated for version 5.1.8. misc/fcitx5-mcbopomofo: Updated for version 2.9.0. misc/fcitx5-qt: Updated for version 5.1.9. misc/fcitx5-table-extra: Updated for version 5.1.7. misc/fcitx5-table-other: Updated for version 5.1.4. misc/fcitx5: Updated for version 5.1.12. misc/gramps: Updated for version 5.2.4. misc/libime: Updated for version 1.1.10. misc/open-simh: Updated for version 20250213_b036821 multimedia/HandBrake: Version bump to 1.9.1 multimedia/ffmpegfs: Updated for version 2.17. multimedia/openshot: Updated for version 0.3.3 multimedia/picard: Version bump to 2.13.2 multimedia/plexmediaserver: Updated for version 1.41.4.9463_630c9f557. multimedia/w_scan2: Updated for version 1.0.16. network/brave-browser: updated for version 1.75.175 network/cinny-desktop: Updated for version 4.3.1. network/deluge: Fix build. network/discord: Version bump to 0.0.85 network/dma: Updated for version 0.14. network/ethersrv-linux: Added (server for EtherDFS). network/jitsi-meet-desktop: Updated for version 2025.2.0 network/librewolf: Updated for version 135.0 network/mailspring: Updated for version 1.15.1. network/mullvadvpn-app: Updated for version 2025.4. network/nextcloud-server: Updated for version 29.0.12. network/nginx: Updated for version 1.26.3 network/onedrive: Updated to version 2.5.4 network/onkyo-eiscp: Added (Python Library for Onkyo). network/privoxy: Updated for version 4.0.0 network/protonmail-bridge: Updated for version 3.17.0. network/putty: Updated for version 0.83. network/roundcubemail: Updated for version 1.6.10. network/signal-desktop: Updated for version 7.42.0. network/snac2: Updated for version 2.72. network/sshuttle: updated for version 1.2.0 network/telegram: Updated for version 5.11.0. network/tor-browser: Updated for version 14.0.6. network/tor: updated version 0.4.8.13 network/vivaldi: Updated for version 7.1.3570.50. network/vnstat: Updated for version 2.13. network/zdns: Updated for version 2.0.0. office/ishmael: Added (Convert EBook). office/kraft: Updated for version 1.2.2. office/pdfsandwich: Added (Generate OCR PDF). office/texworks: Updated for version 0.6.10. perl/perl-CryptX: Updated for version 0.085. python/buildbot-badges: updated for version 4.2.0 python/buildbot-worker: updated for version 4.2.0 python/buildbot: updated for version 4.2.0 python/colored: Updated for version 2.3.0. python/cryptography: Updated for version 44.0.1. python/josepy: Updated for version 2.0.0. python/python2-pyasn1-modules: Removed, unneeded python/python3-alembic: updated for version 1.14.1 python/python3-atpublic: updated for version 5.1 python/python3-bcrypt: Fix build. python/python3-croniter: Added (Python Library). python/python3-deprecated: Version bump to 1.2.18 python/python3-dogpile.cache: Version bump to 1.3.4 python/python3-evdev: Version bump to 1.9.0 python/python3-falcon: updated for version 4.0.2 python/python3-gearbox: Updated for version 0.3.1. python/python3-identify: Updated for version 2.6.7 python/python3-incremental: README update python/python3-incremental: Updated for version 24.7.2. python/python3-klein: updated for version 24.8.0 python/python3-lxml: Version bump to 5.3.1 python/python3-mir_eval: Version bump to 0.8.0 python/python3-presets: Version bump to 1.0.0 python/python3-pyjwt: updated for version 2.10.1 python/python3-treq: Added (HTTP Client Library). python/python3-tubes: Fix build. python/python3-unidiff: Added (Python Library). python/python3-versioneer: Clean up build. python/python3-zodbpickle: Updated for version 4.2. system/B-em: Updated for version 20250214_c6ecdf8 system/cpuid2cpuflags: Updated for version 15. system/dar: Updated for version 2.7.16. system/ded: Updated for version 20250117. system/dosbox-dev: updated for version 0.75_pre4484 system/dosbox-staging: Added (DOS Emulator). system/intel-microcode: Updated for version 20250211 system/letsencrypt: Updated for version 3.2.0. system/limine: Updated for version 8.7.0 system/locust: Updated for version 2.32.5 system/osquery-bin: Updated for version 5.15.0. system/postgresql15: Updated for version 15.11. system/postgresql16: Updated for version 16.7. system/postgresql17: Updated for version 17.3. system/postgresql: Updated for version 14.16. system/psensor: Update script. system/slpkg: Updated for version 5.1.9. system/spkg: Updated for version 1.7. system/thermald: Updated for version 2.5.9. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From andrzej at telszewski.com Wed Feb 19 09:47:38 2025 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Wed, 19 Feb 2025 10:47:38 +0100 Subject: [Slackbuilds-users] How to rename a package over GitHub PR? Message-ID: <11cbde98-f0ce-483f-839f-f002d6467fd4@telszewski.com> Hello, I wanted to rename a certain package over GitHub PR. How do I go about it? Should I create 2 commits, one to remove the _old_ named package, and one to add the _new_ named package? Any additional steps required? Thank you for your assistance! :-) -- Best regards, Andrzej Telszewski From matteo.bernardini at gmail.com Wed Feb 19 09:58:04 2025 From: matteo.bernardini at gmail.com (Matteo Bernardini) Date: Wed, 19 Feb 2025 10:58:04 +0100 Subject: [Slackbuilds-users] How to rename a package over GitHub PR? In-Reply-To: <11cbde98-f0ce-483f-839f-f002d6467fd4@telszewski.com> References: <11cbde98-f0ce-483f-839f-f002d6467fd4@telszewski.com> Message-ID: hi Andrzej, unfortunately this has to be considered as a new submission as the new entry in the database is created only through the submission form. the best way to behave in these situations is to just do the submission with the new name, putting in the submission notes that the script with the old name has to be removed from the repository: then the admin that will take care to approve your submission will take care of handling the two git commits (the one that removes the old script and the one that adds the new). thanks to you for your contributions! Matteo Il giorno mer 19 feb 2025 alle ore 10:47 Andrzej Telszewski < andrzej at telszewski.com> ha scritto: > Hello, > > I wanted to rename a certain package over GitHub PR. > > How do I go about it? > > Should I create 2 commits, one to remove the _old_ named package, and > one to add the _new_ named package? > Any additional steps required? > > Thank you for your assistance! :-) > > -- > Best regards, > Andrzej Telszewski > > _______________________________________________ > SlackBuilds-users mailing list > SlackBuilds-users at slackbuilds.org > https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users > Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ > FAQ - https://slackbuilds.org/faq/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrzej at telszewski.com Wed Feb 19 10:05:14 2025 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Wed, 19 Feb 2025 11:05:14 +0100 Subject: [Slackbuilds-users] How to rename a package over GitHub PR? In-Reply-To: References: <11cbde98-f0ce-483f-839f-f002d6467fd4@telszewski.com> Message-ID: On 19/02/2025 10:58, Matteo Bernardini wrote: > hi Andrzej, > > unfortunately this has to be considered as a new submission as the new > entry in the database is created only through the submission form. > > the best way to behave in these situations is to just do the > submission with the new name, putting in the submission notes that the > script with the old name has to be removed from the repository: then > the admin that will take care to approve your submission will take > care of handling the two git commits (the one that removes the old > script and the one that adds the new). > > thanks to you for your contributions! > > Matteo > I see, thanks! From simon at simonhugh.xyz Wed Feb 19 16:46:59 2025 From: simon at simonhugh.xyz (Simon H Moore) Date: Wed, 19 Feb 2025 16:46:59 +0000 Subject: [Slackbuilds-users] How do I get a UID/GID assigned? Message-ID: <4KmI_c3im2E6UvNYPJ2ENFAdTbs3FnFuP0fy8tlZgUq5bAxVn8GvloxK0_u5Q_oHgkurwN2i4RsaQtr-8eEyieB3aZputNLtRkhlW0IdWDg=@simonhugh.xyz> Hi, I am writing a new package for gotify, and need a UID and GID for a "gotify" user. This is my first slackbuilds package, so I am unsure as to the procedure on how to get one assigned. Could someone help me? Thank you, Simon -- Simon H Moore simon at simonhugh.xyz -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Thu Feb 20 01:42:16 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 20 Feb 2025 08:42:16 +0700 Subject: [Slackbuilds-users] How to rename a package over GitHub PR? In-Reply-To: <11cbde98-f0ce-483f-839f-f002d6467fd4@telszewski.com> References: <11cbde98-f0ce-483f-839f-f002d6467fd4@telszewski.com> Message-ID: <4eb51b2a-cec9-4c51-93a2-9b19fba3c87b@slackbuilds.org> > I wanted to rename a certain package over GitHub PR. > > How do I go about it? > > Should I create 2 commits, one to remove the _old_ named package, and > one to add the _new_ named package? > Any additional steps required? is it really necessary to rename a scripts? if it's a yes, then you need to submit a new script over submission form and you can delete the old one in a PR otherwise, let's just keep the script name so users doesn't need to tackle with trivial renames. I kept my certbot script as letsencrypt since people have been using it for some time and it still works so i kept it. -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From willysr at slackbuilds.org Thu Feb 20 01:43:36 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Thu, 20 Feb 2025 08:43:36 +0700 Subject: [Slackbuilds-users] How do I get a UID/GID assigned? In-Reply-To: <4KmI_c3im2E6UvNYPJ2ENFAdTbs3FnFuP0fy8tlZgUq5bAxVn8GvloxK0_u5Q_oHgkurwN2i4RsaQtr-8eEyieB3aZputNLtRkhlW0IdWDg=@simonhugh.xyz> References: <4KmI_c3im2E6UvNYPJ2ENFAdTbs3FnFuP0fy8tlZgUq5bAxVn8GvloxK0_u5Q_oHgkurwN2i4RsaQtr-8eEyieB3aZputNLtRkhlW0IdWDg=@simonhugh.xyz> Message-ID: > I am writing a new package for gotify, and need a UID and GID for a > "gotify" user. > > This is my first slackbuilds package, so I am unsure as to the procedure > on how to get one assigned. You can use 388 as your UID/GID -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From andrzej at telszewski.com Thu Feb 20 09:28:26 2025 From: andrzej at telszewski.com (Andrzej Telszewski) Date: Thu, 20 Feb 2025 10:28:26 +0100 Subject: [Slackbuilds-users] How to rename a package over GitHub PR? In-Reply-To: <4eb51b2a-cec9-4c51-93a2-9b19fba3c87b@slackbuilds.org> References: <11cbde98-f0ce-483f-839f-f002d6467fd4@telszewski.com> <4eb51b2a-cec9-4c51-93a2-9b19fba3c87b@slackbuilds.org> Message-ID: <578ba510-64bc-4a50-808c-0b011f51a1c6@telszewski.com> On 20/02/2025 02:42, Willy Sudiarto Raharjo wrote: >> I wanted to rename a certain package over GitHub PR. >> >> How do I go about it? >> >> Should I create 2 commits, one to remove the _old_ named package, and >> one to add the _new_ named package? >> Any additional steps required? > > is it really necessary to rename a scripts? Ordinarily, I wouldn't do it - but this time I wanted to have a common pattern in the way the SlackBuilds are named, because I have more than one SlackBuild in the _series_. > if it's a yes, then you need to submit a new script over submission > form and you can delete the old one in a PR I've already done that, asking for removal of the previous SlackBuild in the submission's form comment. Thanks! From slackcoder at server.ky Fri Feb 21 00:49:16 2025 From: slackcoder at server.ky (Slack Coder) Date: Thu, 20 Feb 2025 19:49:16 -0500 Subject: [Slackbuilds-users] Checksum failing for missing packages Message-ID: <79dc87d2-6dfd-423c-bc1c-a79b24dfc25d@server.ky> Hi All, The checksums file for 15.0 looks like it needs updating.? The minetest packages are listed which no longer exist. ``` rsync -a rsync://slackbuilds.org/slackbuilds/15.0 .; cd 15.0; tail +13 CHECKSUMS.md5 | md5sum -c --quiet - # md5sum: ./games/minetest.tar.gz: No such file or directory # ./games/minetest.tar.gz: FAILED open or read # md5sum: ./games/minetest.tar.gz.asc: No such file or directory # ./games/minetest.tar.gz.asc: FAILED open or read # md5sum: ./games/minetest_game.tar.gz: No such file or directory # ./games/minetest_game.tar.gz: FAILED open or read # md5sum: ./games/minetest_game.tar.gz.asc: No such file or directory # ./games/minetest_game.tar.gz.asc: FAILED open or read # md5sum: WARNING: 4 listed files could not be read ``` Best Regards, Slack Coder From willysr at slackbuilds.org Fri Feb 21 02:12:45 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Fri, 21 Feb 2025 09:12:45 +0700 Subject: [Slackbuilds-users] Checksum failing for missing packages In-Reply-To: <79dc87d2-6dfd-423c-bc1c-a79b24dfc25d@server.ky> References: <79dc87d2-6dfd-423c-bc1c-a79b24dfc25d@server.ky> Message-ID: <9459e199-7548-4d37-817f-a3169c5b1d5d@slackbuilds.org> > The checksums file for 15.0 looks like it needs updating.? The minetest > packages are listed which no longer exist. > > ``` > > rsync -a rsync://slackbuilds.org/slackbuilds/15.0 .; cd 15.0; tail +13 > CHECKSUMS.md5 | md5sum -c --quiet - > > # md5sum: ./games/minetest.tar.gz: No such file or directory > # ./games/minetest.tar.gz: FAILED open or read > # md5sum: ./games/minetest.tar.gz.asc: No such file or directory > # ./games/minetest.tar.gz.asc: FAILED open or read > # md5sum: ./games/minetest_game.tar.gz: No such file or directory > # ./games/minetest_game.tar.gz: FAILED open or read > # md5sum: ./games/minetest_game.tar.gz.asc: No such file or directory > # ./games/minetest_game.tar.gz.asc: FAILED open or read > # md5sum: WARNING: 4 listed files could not be read those two scripts were deleted in the git branch and will be removed in this week's update, so i deleted them from website and database already You can ignore those two entries -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_0x3F617144D7238786.asc Type: application/pgp-keys Size: 8363 bytes Desc: OpenPGP public key URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From mm at dorfdsl.de Fri Feb 21 06:56:51 2025 From: mm at dorfdsl.de (Marco Moock) Date: Fri, 21 Feb 2025 07:56:51 +0100 Subject: [Slackbuilds-users] ftp server not accessible Message-ID: <20250221075651.47edeef9@zbook> Hello! m at zbook:~$ LANG=C ftp ftp.slackbuilds.org Trying 2604:5800:0:90::67... ftp: connect to address 2604:5800:0:90::67Connection refused Trying 66.85.79.67... ftp: connect: Network is unreachable ftp> quit m at zbook:~$ I can't connect to the FTP server currently. I get a TCP RST via IPv6. Is the daemon running? HTTP/HTTPS work fine. Do other experience the same? -- kind regards Marco From urchlay at slackware.uk Fri Feb 21 07:18:14 2025 From: urchlay at slackware.uk (B. Watson) Date: Fri, 21 Feb 2025 02:18:14 -0500 (EST) Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <20250221075651.47edeef9@zbook> References: <20250221075651.47edeef9@zbook> Message-ID: On Fri, 21 Feb 2025, Marco Moock wrote: > I can't connect to the FTP server currently. > I get a TCP RST via IPv6. Works fine for me, but with an IPv4 address. If I use the IPv6 address (2604:5800:0:90::67), I get the same 'network is unreachable' as you do. From mm at dorfdsl.de Fri Feb 21 07:36:30 2025 From: mm at dorfdsl.de (Marco Moock) Date: Fri, 21 Feb 2025 08:36:30 +0100 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: References: <20250221075651.47edeef9@zbook> Message-ID: <20250221083630.3652de5e@zbook> Am Fri, 21 Feb 2025 02:18:14 -0500 (EST) schrieb "B. Watson" : > If I use the IPv6 address (2604:5800:0:90::67), I get the same > 'network is unreachable' as you do. That means your machine doesn't have IPv6. This is a different issue (at your side). From urchlay at slackware.uk Fri Feb 21 08:15:31 2025 From: urchlay at slackware.uk (B. Watson) Date: Fri, 21 Feb 2025 03:15:31 -0500 (EST) Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <20250221083630.3652de5e@zbook> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> Message-ID: On Fri, 21 Feb 2025, Marco Moock wrote: >> If I use the IPv6 address (2604:5800:0:90::67), I get the same >> 'network is unreachable' as you do. > > That means your machine doesn't have IPv6. > This is a different issue (at your side). Derp. You're right. I dunno when that happened (I didn't do anything to disable it) but somehow I have lost IPv6 at my house... *shrug*, I never missed it until now. Likely an ISP issue. Trying it from another host elsewhere (that *does* have IPv6 working), I get 'connection refused' for the IPv6 address, and it works fine with the IPv4 one. Checking on the server... the ftp daemon just isn't listening on the IPv6 address. Consider this escalated. The two potential fixes are (a) fix the daemon so it listens on IPv6 also, or (b) get rid of the AAAA record in DNS, so clients quit trying to use v6. I know which I'd prefer, but it's not my call. From mm at dorfdsl.de Fri Feb 21 08:32:54 2025 From: mm at dorfdsl.de (Marco Moock) Date: Fri, 21 Feb 2025 09:32:54 +0100 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> Message-ID: <20250221093254.71d030e6@ryz.dorfdsl.de> Am 21.02.2025 um 03:15:31 Uhr schrieb B. Watson: > Checking on the server... the ftp daemon just isn't listening on the > IPv6 address. I dunno which daemon you use, but I assume letting it listen on IPv6 should be rather simple. -- kind regards Marco Send unsolicited bulk mail to 1740104131muell at cartoonies.org From urchlay at slackware.uk Fri Feb 21 08:48:27 2025 From: urchlay at slackware.uk (B. Watson) Date: Fri, 21 Feb 2025 03:48:27 -0500 (EST) Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <20250221093254.71d030e6@ryz.dorfdsl.de> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <20250221093254.71d030e6@ryz.dorfdsl.de> Message-ID: <634d95a4-5225-8e1d-f71b-158aa1fdbe62@slackware.uk> On Fri, 21 Feb 2025, Marco Moock wrote: > Am 21.02.2025 um 03:15:31 Uhr schrieb B. Watson: > >> Checking on the server... the ftp daemon just isn't listening on the >> IPv6 address. > > I dunno which daemon you use, but I assume letting it listen on IPv6 > should be rather simple. Yes. But I'm not the sysadmin, and this isn't an emergency, and it's the middle of the night in the US timezones. So please be patient. From noel.butler at ausics.net Fri Feb 21 09:38:50 2025 From: noel.butler at ausics.net (Noel Butler) Date: Fri, 21 Feb 2025 19:38:50 +1000 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> Message-ID: <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> On 21/02/2025 18:15, B. Watson wrote: > Trying it from another host elsewhere (that *does* have IPv6 working), > I get 'connection refused' for the IPv6 address, and it works fine > with the IPv4 one. confirmed, I don't know why Marco is not getting in on ipv4 as you said, it tests fine, does your isp assign it with dhcp.delegated_prefix? I've found some routers dont ask for it on renew all the time, NFI idea why it happens. But Marco can expect a separate offlist email re another matter that his systems dont play correctly, and thats OT for this list. -- Regards, Noel Butler -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at dorfdsl.de Fri Feb 21 09:40:39 2025 From: mm at dorfdsl.de (Marco Moock) Date: Fri, 21 Feb 2025 10:40:39 +0100 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> Message-ID: <20250221104039.1f6768c9@ryz.dorfdsl.de> Am 21.02.2025 um 19:38:50 Uhr schrieb Noel Butler via SlackBuilds-users: > I don't know why Marco is not getting in on ipv4 as you said, The machine I used is intentionally only connected to IPv6 (with NAT64/DNS64). -- Gru? Marco Send unsolicited bulk mail to 1740163130muell at cartoonies.org From noel.butler at ausics.net Sat Feb 22 01:44:41 2025 From: noel.butler at ausics.net (Noel Butler) Date: Sat, 22 Feb 2025 11:44:41 +1000 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <20250221104039.1f6768c9@ryz.dorfdsl.de> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> <20250221104039.1f6768c9@ryz.dorfdsl.de> Message-ID: <233df9178537933a78bdd2725d7dfb68@ausics.net> On 21/02/2025 19:40, Marco Moock wrote: > Am 21.02.2025 um 19:38:50 Uhr schrieb Noel Butler via > SlackBuilds-users: > >> I don't know why Marco is not getting in on ipv4 as you said, > > The machine I used is intentionally only connected to IPv6 (with > NAT64/DNS64). Ahhh OK, in doing so you know and accept the risks, unfortunately like the one you are experiencing now. Since http works I gather you got what you were after? Cheers -- Regards, Noel Butler -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex at dcclost.com Sat Feb 22 02:11:59 2025 From: alex at dcclost.com (Alexander Grotewohl) Date: Sat, 22 Feb 2025 02:11:59 +0000 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <233df9178537933a78bdd2725d7dfb68@ausics.net> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> <20250221104039.1f6768c9@ryz.dorfdsl.de> <233df9178537933a78bdd2725d7dfb68@ausics.net> Message-ID: I'm sure glad I got to read this thread ?? -- Alexander Grotewohl https://dcclost.com ________________________________ From: SlackBuilds-users on behalf of Noel Butler via SlackBuilds-users Sent: Friday, February 21, 2025 8:44 PM To: slackbuilds-users at slackbuilds.org Cc: Noel Butler Subject: Re: [Slackbuilds-users] ftp server not accessible On 21/02/2025 19:40, Marco Moock wrote: Am 21.02.2025 um 19:38:50 Uhr schrieb Noel Butler via SlackBuilds-users: I don't know why Marco is not getting in on ipv4 as you said, The machine I used is intentionally only connected to IPv6 (with NAT64/DNS64). Ahhh OK, in doing so you know and accept the risks, unfortunately like the one you are experiencing now. Since http works I gather you got what you were after? Cheers -- Regards, Noel Butler -------------- next part -------------- An HTML attachment was scrubbed... URL: From willysr at slackbuilds.org Sat Feb 22 03:16:53 2025 From: willysr at slackbuilds.org (Willy Sudiarto Raharjo) Date: Sat, 22 Feb 2025 10:16:53 +0700 Subject: [Slackbuilds-users] Updates - 20250222.1 Message-ID: Sat Feb 22 03:02:08 UTC 2025 academic/plus42: Updated for version 1.2.6 audio/flacon: Updated for version 12.0.0. audio/ncmpc/ncmpc: Updated for version 0.52. desktop/ClamAV-GUI: Updated for version 20250210_8762118 desktop/gopsuinfo: Updated for version 0.1.9. desktop/nwg-dock: Updated for version 0.4.3. desktop/nwg-look: Updated for version 1.0.2. desktop/nwg-menu: Updated for version 0.1.7. desktop/nwg-panel: Updated for version 0.9.62. desktop/nwg-readme-browser: Updated for version 0.1.6. desktop/nwg-shell-config: Updated for version 0.5.58. desktop/nwg-shell: Updated for version 0.5.45. desktop/xseticon: Added (set the X11 window icon). development/abseil-cpp: Version bump to 20250127.0 development/acme: Added (Family Cross Assembler). development/aflex: Added (ADA Lexical Analyzer). development/aws-cdk: Updated for version 2.1000.2. development/aws-cdk: Updated for version 2.179.0. development/ayacc: Added (ADA Parser Generator). development/buf: Added (Protocol Buffers Tool). development/castxml: Added (XML Output Tool). development/dart-sass: Updated for version 1.85.0. development/diffoscope: updated for version 288 development/ghidra: Updated for version 11.3 development/hexcurse: Updated for version 1.70.0, new upstream. development/ispc: Update README. development/mongodb-compass: Updated for version 1.45.3. development/mysql-workbench: Updated the bundled gdal to 3.10.2. development/obsidian: updated for version 1.8.7 development/postman: Updated for version 11.32.2 development/reuse-tool: Updated for version 5.0.2. development/stm32cubeide: Added (C/C++ development platform). development/stm32cubeprog: Added (multi-OS software). development/sublime_text: Updated for version 4.1.92. development/vstudio: Updated for version 15.0.1 development/xnedit: Updated for version 1.6.2 games/frotz: Updated for version 2.55. games/luanti: Added (voxel game). games/minetest: Removed (upstream no longer exists). games/minetest_game: Removed (upstream no longer exists). games/widelands: Updated for version 1.2.1 libraries/ahven: Added (Simple Unit Test). libraries/botocore: Updated for version 1.36.24. libraries/gamemode: Update md5sum libraries/gnome-desktop: Downgraded to version 41.8 libraries/libfabric: Updated for version 2.0.0. libraries/liburcu: Updated for version 0.15.1. libraries/php-ssh2: Updated for version 1.4.1. libraries/pymediainfo: Version bump to 7.0.1 libraries/qt-jpegxl-image-plugin: Updated for version 0.8.0. libraries/spawn: Added (Ada Process API). misc/duhdraw: Added (ASCII Art Editor). multimedia/openh264: Updated for version 2.6.0. multimedia/picard: Version bump to 2.13.3 multimedia/pocketsphinx: Updated for version 5.0.4. multimedia/youtube-music: Updated for version 3.7.4. network/awscli: Updated for version 1.37.24. network/brave-browser: updated for version 1.75.180 network/cinny-desktop: Updated for version 4.3.2. network/discord: Version bump to 0.0.86 network/dropbox: Updated for version 218.4.4348. network/kirc: Updated for version 0.3.3. network/mpop: Updated for version 1.4.21. network/signal-desktop: Updated for version 7.43.0. network/simplex-desktop: Added (Messenger Chat). network/telegram: Updated for version 5.11.1. network/vivaldi: Updated for version 7.1.3570.54. network/webex: Updated for version 45.2.0.31755 network/wireshark: Updated for version 4.4.4. network/zoom-linux: Updated for 6.3.10.7150 office/focuswriter-qt6: updated for version 1.8.10 office/ishmael: Updated for version 0.05. office/typobuster: Added (Simplified Text Editor). python/buildbot-badges: updated for version 4.2.1 python/buildbot-worker: updated for version 4.2.1 python/buildbot: updated for version 4.2.1 python/license-expression: Updated for version 30.4.1. python/python-debian: Updated for version 0.1.52. python/python2-cryptography: Fix build on current. python/python3-PyGithub: Version bump to 2.6.0 python/python3-PyGithub: Version bump to 2.6.1 python/python3-aiohappyeyeballs: Updated for version 2.4.6. python/python3-aiohttp: Updated for version 3.11.12. python/python3-argcomplete: Updated for version 3.5.3. python/python3-autobahn: updated for version 24.4.2 python/python3-cachetools: Version bump to 5.5.2 python/python3-fonttools: Updated for version 4.56.0. python/python3-gearbox: updated for version 0.3.2 python/python3-glyphslib: Updated for version 6.10.1. python/python3-icalendar: Updated for version 6.1.1 python/python3-incremental: Fix build. python/python3-openstep-plist: Updated for version 0.5.0. python/python3-pytz: Version bump to 2025.1 + New maintainer python/python3-qbittorrent-api: Version bump to 2025.2.0 python/python3-reportlab: Updated for version 4.3.1. python/python3-ufo2ft: Updated for version 3.4.2. python/python3-ufolib2: Updated for version 0.17.1. python/python3-uharfbuzz: Updated for version 0.45.0. python/python3-virtualenv: Version bump to 20.29.2 python/rst2pdf: Updated for version 0.103.1. python/s3transfer: Updated for version 0.11.2. system/FreeFileSync: Updated for version 14.2 system/dracut: updated for version 106. system/fsarchiver: Updated for version 0.8.8. system/hardinfo2: Updated for version 2.2.7. system/netdata: Updated for version 2.2.6. system/openrazer-daemon: Updated for version 3.10.0. system/openrazer-kernel: Updated for version 3.10.0. system/openzfs: added configure arguments system/postgresql15: Updated for version 15.12. system/postgresql16: Updated for version 16.8. system/postgresql17: Updated for version 17.4. system/postgresql: Updated for version 14.17. system/prometheus: Updated for version 3.2.0 system/rewise: Updated for version 0.3.1. system/sbotools2: Updated for version 2.9.0. system/sbpkg: Updated for version 1.1.2. system/supervisor: Updated for version 4.2.5, new maintainer system/ttf-babelstone-latin: Updated for version 1.1. system/usermin: Updated for version 2.201. system/webmin: Updated for version 2.301. +--------------------------+ -- Willy Sudiarto Raharjo -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature.asc Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: From urchlay at slackware.uk Sat Feb 22 08:32:23 2025 From: urchlay at slackware.uk (B. Watson) Date: Sat, 22 Feb 2025 03:32:23 -0500 (EST) Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <233df9178537933a78bdd2725d7dfb68@ausics.net> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> <20250221104039.1f6768c9@ryz.dorfdsl.de> <233df9178537933a78bdd2725d7dfb68@ausics.net> Message-ID: <3740a089-652f-a65c-4abb-e6ebb9a54d7b@slackware.uk> On Sat, 22 Feb 2025, Noel Butler via SlackBuilds-users wrote: > > On 21/02/2025 19:40, Marco Moock wrote: > > Am 21.02.2025 um 19:38:50 Uhr schrieb Noel Butler via SlackBuilds-users: > > I don't know why Marco is not getting in on ipv4 as you said, > > > The machine I used is intentionally only connected to IPv6 (with > NAT64/DNS64). > > > Ahhh OK, in doing so you know and accept the risks, unfortunately like the one you are experiencing now. Actually... if I understand how NAT64 and DNS64 work, he should be able to connect to the IPv4 address if there's no AAAA record at all. See https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS64 DNS64 gives a 'synthetic' IPv6 address for a real IPv4 one, and NAT64 allows an IPv6-only host to connect to it. AFAICT, the problem is caused by us having an AAAA record, but not really listening on the IPv6 address. His machine doesn't think it needs to use DNS64/NAT64 because it sees there's a real AAAA record, so it tries to connect to the real IPv6 address, which gives 'connection refused'. If we got rid of the AAAA record entirely, DNS64 and NAT64 would be used instead. At least that's what it looks like based on the 5-minute crash course I just gave myself on DNS64 and NAT64. Marco, is that correct? From mm at dorfdsl.de Sat Feb 22 09:28:58 2025 From: mm at dorfdsl.de (Marco Moock) Date: Sat, 22 Feb 2025 10:28:58 +0100 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <3740a089-652f-a65c-4abb-e6ebb9a54d7b@slackware.uk> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> <20250221104039.1f6768c9@ryz.dorfdsl.de> <233df9178537933a78bdd2725d7dfb68@ausics.net> <3740a089-652f-a65c-4abb-e6ebb9a54d7b@slackware.uk> Message-ID: <20250222102858.4e9086de@ryz.dorfdsl.de> Am 22.02.2025 um 03:32:23 Uhr schrieb B. Watson: > His machine doesn't think it needs to use DNS64/NAT64 because it > sees there's a real AAAA record, so it tries to connect to the real > IPv6 address, which gives 'connection refused'. If we got rid of the > AAAA record entirely, DNS64 and NAT64 would be used instead. The DNS resolver indeed decides that. If there is an AAAA record, the logical assumption is that the daemons are listening on this address and therefore no NAT64 address needs to be used. > At least that's what it looks like based on the 5-minute crash course > I just gave myself on DNS64 and NAT64. > > Marco, is that correct? Yes, it is. Although I see no reason against just letting the daemon listen on IPv6 like it does for HTTP, so the service is accessible with both protocols. -- Gru? Marco Send unsolicited bulk mail to 1740191543muell at cartoonies.org From noel.butler at ausics.net Sat Feb 22 10:58:30 2025 From: noel.butler at ausics.net (Noel Butler) Date: Sat, 22 Feb 2025 20:58:30 +1000 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <3740a089-652f-a65c-4abb-e6ebb9a54d7b@slackware.uk> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> <20250221104039.1f6768c9@ryz.dorfdsl.de> <233df9178537933a78bdd2725d7dfb68@ausics.net> <3740a089-652f-a65c-4abb-e6ebb9a54d7b@slackware.uk> Message-ID: <30984da52656146461249683ba577476@ausics.net> On 22/02/2025 18:32, B. Watson wrote: > Actually... if I understand how NAT64 and DNS64 work, he should be > able to connect to the IPv4 address if there's no AAAA record at all. Not so sure about ftp, I confess its been 20 years since I've even skimmed over anything nat64 so I'd be honest and say I'm working off an aged memory :) we never had a need for it, but I'm sure I recall there was a problem with certain protocols and ftp was one? They may have come up with a solution to that by now, maybe they have and that's why Marco is trying to use it. > See https://en.wikipedia.org/wiki/IPv6_transition_mechanism#DNS64 > > DNS64 gives a 'synthetic' IPv6 address for a real IPv4 one, and NAT64 > allows an IPv6-only host to connect to it. yes embedding 32b address inside it, and needs gateway set up correctly if any part of my memory is not muddying the waters. > AFAICT, the problem is caused by us having an AAAA record, but not > really listening on the IPv6 address. Oh, didn't realise that part, I just thought there was a failure of routing, bit strange giving it a 6 DNS address but not using it, not sure what daemon is used, we've used pure-ftpd since about 2000-ish and it just uses every interface, , maybe its just a firewall that needs altering? But sounds like the daemon requires it implicitly be set? > His machine doesn't think it needs to use DNS64/NAT64 because it > sees there's a real AAAA record, so it tries to connect to the real > IPv6 address, which gives 'connection refused'. If we got rid of the > AAAA record entirely, DNS64 and NAT64 would be used instead. Makes sense, but why not just make sure its accepted rather than remove the 6 DNS :) Does Robby run it still? I'd like to ask him to change mailman too, but I'm thinking the version is not current enough to understand the changes, it's late Saturday night and you can guess what that means so I'll look in the morning hehe and if it meets requirements I'll shoot him off an email. > -- Regards, Noel Butler -------------- next part -------------- An HTML attachment was scrubbed... URL: From mm at dorfdsl.de Sat Feb 22 11:27:53 2025 From: mm at dorfdsl.de (Marco Moock) Date: Sat, 22 Feb 2025 12:27:53 +0100 Subject: [Slackbuilds-users] ftp server not accessible In-Reply-To: <30984da52656146461249683ba577476@ausics.net> References: <20250221075651.47edeef9@zbook> <20250221083630.3652de5e@zbook> <5ad8ffcc6492bc8c4b80b441140b277e@ausics.net> <20250221104039.1f6768c9@ryz.dorfdsl.de> <233df9178537933a78bdd2725d7dfb68@ausics.net> <3740a089-652f-a65c-4abb-e6ebb9a54d7b@slackware.uk> <30984da52656146461249683ba577476@ausics.net> Message-ID: <20250222122753.04edff1f@ryz.dorfdsl.de> Am 22.02.2025 um 20:58:30 Uhr schrieb Noel Butler via SlackBuilds-users: > On 22/02/2025 18:32, B. Watson wrote: > > > Actually... if I understand how NAT64 and DNS64 work, he should be > > able to connect to the IPv4 address if there's no AAAA record at > > all. > > Not so sure about ftp, I confess its been 20 years since I've even > skimmed over anything nat64 so I'd be honest and say I'm working off > an aged memory :) we never had a need for it, but I'm sure I recall > there was a problem with certain protocols and ftp was one? They may > have come up with a solution to that by now, maybe they have and > that's why Marco is trying to use it. Passive FTP works very well with SPI firewall, NAT and NAT64. In this case the hostname has an AAAA record and NAT64 won't used at all - by design. -- Gru? Marco Send unsolicited bulk mail to 1740254310muell at cartoonies.org From zsd+slackbuilds at jdvb.ca Sat Feb 22 23:26:33 2025 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 22 Feb 2025 19:26:33 -0400 Subject: [Slackbuilds-users] fvwm3 1.1.2 problem Message-ID: I recently used the Slackbuild to upgrade my fvwm3 from 1.1.1 to 1.1.2. I have some lines in my config file like this (and some more pairs of lines for other hosts following it): DestroyMenu Other_Hosts AddToMenu Other_Hosts + "x360" Exec exec my-xterm -ut -sl 2000 -bg "#125050" \ -n x360 -e ssh x360 -Y Notice there is a \ at the end of the second-last line. When I pick the x360 line from that menu, the "my-term" program only gets the following arguments -ut -sl 2000 -bg #860030 \ rather than -ut -sl 2000 -bg #860030 -n x360 -e ssh x360 -Y This type of thing has worked for me for the past 150 years or so. Is there anyone reading this who used fvwm3 1.1.2 and has continuation lines in their config? Thanks. Jim From kvngncrlsn at gmail.com Sun Feb 23 01:27:15 2025 From: kvngncrlsn at gmail.com (K. Eugene Carlson) Date: Sun, 23 Feb 2025 10:27:15 +0900 Subject: [Slackbuilds-users] fvwm3 1.1.2 problem In-Reply-To: References: Message-ID: On Sun, Feb 23, 2025 at 8:26?AM Jim wrote: > Is there anyone reading this who used fvwm3 1.1.2 and has continuation > lines in their config? > Yes, and they're working fine here. Are there any stray spaces after the backslashes? Best regards, Gene -------------- next part -------------- An HTML attachment was scrubbed... URL: From zsd+slackbuilds at jdvb.ca Sun Feb 23 02:48:17 2025 From: zsd+slackbuilds at jdvb.ca (Jim) Date: Sat, 22 Feb 2025 22:48:17 -0400 Subject: [Slackbuilds-users] fvwm3 1.1.2 problem In-Reply-To: References: Message-ID: Hi Gene, On Sun, Feb 23, 2025 at 10:27 (+0900), K. Eugene Carlson wrote: > On Sun, Feb 23, 2025 at 8:26?AM Jim wrote: >> Is there anyone reading this who used fvwm3 1.1.2 and has continuation >> lines in their config? > Yes, and they're working fine here. Are there any stray spaces after the > backslashes? Thanks for getting back. (Unfortunately) No stray spaces. (The same unedited file was working under 1.1.1 and a number of other versions of fvwm3.) Cheers. Jim From kvngncrlsn at gmail.com Sun Feb 23 07:29:54 2025 From: kvngncrlsn at gmail.com (K. Eugene Carlson) Date: Sun, 23 Feb 2025 16:29:54 +0900 Subject: [Slackbuilds-users] fvwm3 1.1.2 problem In-Reply-To: References: Message-ID: Hi, Jim, Very strange. I saw your issue on the fvwm3 repo. For what it's worth, I doubt it has anything to do with the patches or meson since those changes were made for version 1.1.1. I'd be happy to look at the whole config file if you wanted to send it. Best regards, Gene On Sun, Feb 23, 2025 at 11:48?AM Jim wrote: > Hi Gene, > > On Sun, Feb 23, 2025 at 10:27 (+0900), K. Eugene Carlson wrote: > > > On Sun, Feb 23, 2025 at 8:26?AM Jim wrote: > > >> Is there anyone reading this who used fvwm3 1.1.2 and has continuation > >> lines in their config? > > > > Yes, and they're working fine here. Are there any stray spaces after the > > backslashes? > > Thanks for getting back. > > (Unfortunately) No stray spaces. (The same unedited file was working under > 1.1.1 and a number of other versions of fvwm3.) > > Cheers. > Jim > _______________________________________________ > 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: