From lukeshu at lukeshu.com Wed Apr 3 18:51:49 2024 From: lukeshu at lukeshu.com (Luke T. Shumaker) Date: Wed, 03 Apr 2024 12:51:49 -0600 Subject: [Dev] libretools 20240221.1 release announcement In-Reply-To: <20240324023114.3b65ce66@parabola.localdomain> References: <87ttm1w726.wl-lukeshu@lukeshu.com> <20240324023114.3b65ce66@parabola.localdomain> Message-ID: <87r0fmnut6.wl-lukeshu@lukeshu.com> On Sun, 24 Mar 2024 00:31:14 -0600, bill-auger wrote: > i am making a new release of libretools (v20240324), mainly for two reasons: > > 1) one of the changes in the previous release broke mksource > https://git.parabola.nu/packages/libretools.git/commit/?id=a623a620f68ba19750fc4feba34d1d2db8cd08dc > that reverted a previous change, which was made specifically to fix mksource > https://git.parabola.nu/packages/libretools.git/commit/?id=3d488f32b4d9c84fcf461dedf56911792b217b57 ? > we should figure out whats > the deal with 1) - when i fixed mksource originally, i could not determine what > difference that change made, other than allowing mksource to work again - but > lukeshu left a comment this time suggesting that the LOC in question was > important - if it really is important, we need to find out another way to > un-break mksource Yes, I did un-break it in the linked commit, by adding the `-not -name ext.sh` bit in `librefetchdir/Makefile`. Setting PKGEXT is important so that the correct compression method is used. For example: if the user's makepkg.conf says PKGEXT=pkg.tar.zst, and we're generating `whatever.gz`, then it will be zstd-compressed, not gzip-compressed; which will in-turn cause makepkg to fail to extract it. A testcase for this was added in https://git.parabola.nu/packages/libretools.git/commit/?id=7b9538d383841c7deb286dd0b8f31a5c40cb5d0f At the time of the v20240221.1 release, all tests were passing, including the ones that check that librefetch works. > 2) it needs a rebuild because it was pinned to pacman <6.1 > > i will push it to libre-testing for now, until we sort out (1) - but i already > moved the upgraded pacman to libre because other packages depended on it > https://labs.parabola.nu/issues/3606 > so there will be a conflict for people who have libretools installed now > https://labs.parabola.nu/issues/3610 So that librefetch is broken now is because it needs updated for pacman 6.1--hence it pinning 6.0. I've got a fix coming soon. > also, the pbot announcements still were not quite right - so i backported a few > changes my WIP branches, mainly documentation and updated translations (because > it is not very obvious how to build libretools and generate a source-ball); but > also one relatively minor, but possibly breaking change to the config - > breaking, only if /etc/libretools.conf was modified and the changes go into a > .pacnew instead - no biggie, just merge the .pacnew - librerelease will suggest > to do so for anyone who does not read this Acknowledged. I'm now reviewing the changes you've pushed. -- Happy hacking, ~ Luke T. Shumaker From lukeshu at lukeshu.com Thu Apr 4 05:54:15 2024 From: lukeshu at lukeshu.com (Luke T. Shumaker) Date: Wed, 03 Apr 2024 23:54:15 -0600 Subject: [Dev] libretools 20240403 release announcement Message-ID: <87o7apoepk.wl-lukeshu@lukeshu.com> I've just released libretools 20240403 to [libre] and pushed the source tarball to . I've not yet reviewed all of the changes that Bill included in the v20240327 release. Changes from v20240327 to v20240403: User-facing: - librefetch: Now works with makepkg 6.1. - librerelease: Minor changes to the output that shows in your terminal. - librechroot, libremakepkg: A minor mistake in the spanish translationof the help text has been fixed. Developer-facing: - .po files no longer include file locations. This may make it harder to figure out what the context of a string is, but it should cut down on commit noise. - The way to limit which tests run has changed; `TESTENVFLAGS='--no-network --no-sudo'` becomes `BATS_FLAGS='--filter-tags !network,~sudo`. - A number of improvements to the HACKING documentation. -- Happy hacking, ~ Luke T. Shumaker From nobody at parabola.nu Mon Apr 8 07:23:03 2024 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 08 Apr 2024 07:23:03 -0000 Subject: [Dev] Orphan Libre package [filesystem] marked out-of-date Message-ID: <20240408072303.1197.57518@winston.parabola.nu> dario86 at tutamail.com wants to notify you that the following packages may be out-of-date: * filesystem 2023.09.18-1.parabola1 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/filesystem/ * filesystem 2023.09.18-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/filesystem/ * filesystem 2023.09.18-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/filesystem/ The user provided the following additional text: Version 2024.04.07-1 is out with an important improvement for gaming. From nobody at parabola.nu Sun Apr 14 23:25:14 2024 From: nobody at parabola.nu (Parabola Website Notification) Date: Sun, 14 Apr 2024 23:25:14 -0000 Subject: [Dev] Orphan Libre package [tp_smapi] marked out-of-date Message-ID: <20240414232514.1200.80524@winston.parabola.nu> contact at blob42.xyz wants to notify you that the following packages may be out-of-date: * tp_smapi 0.44-15.parabola1.basekernel6.5.8 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/tp_smapi/ * tp_smapi 0.44-15.parabola1.basekernel6.5.8 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/tp_smapi/ The user provided the following additional text: Hi, The tp_smapi module is important for battery monitoring and maintenance on modern kernels and thinkpads. Can this be upgraded ? Best Regards, blob42 From bill-auger at peers.community Sun Apr 14 23:46:55 2024 From: bill-auger at peers.community (bill-auger) Date: Sun, 14 Apr 2024 19:46:55 -0400 Subject: [Dev] Fw: [PKG Submission] Submit fsearch Message-ID: <20240414194655.03f8aaaf@parabola.localdomain> you sent this to me only; so the mailing list did not get it - when replying to mailing lists, mind that you need to press "reply-all" or "reply-list", depending on your client Begin forwarded message: Date: Sat, 30 Mar 2024 15:18:52 -0700 From: Integral To: bill-auger Subject: Re: [Dev] [PKG Submission] Submit fsearch Of course, I am willing to maintain the PKGBUILD of fsearch, including new versions testing & submission and bugs handling. From bill-auger at peers.community Sun Apr 14 23:49:50 2024 From: bill-auger at peers.community (bill-auger) Date: Sun, 14 Apr 2024 19:49:50 -0400 Subject: [Dev] [PKG Submission] Submit fsearch In-Reply-To: <20240329000436.50c69541@IntegralPC> References: <20240329000436.50c69541@IntegralPC> Message-ID: <20240414194950.499d9a0b@parabola.localdomain> ok, i took a look at that PKGBUILD - there are several issues to address - i have made all of these changes; but as the maintainer you should be aware of them * PKGBUILDs need a `Maintainer:` line, as someone who is associated with parabola - PKGBUILDs forked from anther source (eg: the AUR) should have the `Maintainer:` line changed to `Maintainer (aur):` - i added 'Integral '; but maybe you want to change it (eg: your real name, a different email address, etc) * i added `arch+=('armv7h')` in order to support ARM computers * `license=('GPL-2.0-or-later')` will not work; because we have not migrated to SPDX yet - however, in this case, the AUR PKGBUILD `license=('GPL2')` was wrong - 'GPL2' indicates GPLv2-only - it should be `license=('GPL')`, which indicates "any version" * i added `makedepends+=('intltool' 'itstool')` because the upstream documentation suggests so - it is not obvious if it is used; but presumably, documentation or translations would not be built properly without them * i added back `--buildtype release -Dchannel=other` (and adjusted a few other lines), just to minimize the diff against the AUR PKGBUILD - the only lines i did not sync are `_gitname=fsearch` and `conflicts=('fsearch-git')` because they are irrelevant to parabola * the 'License' file does not need to be installed - any licenses under /usr/share/licenses/common/ should not be installed with the package From bill-auger at peers.community Mon Apr 15 00:19:31 2024 From: bill-auger at peers.community (bill-auger) Date: Sun, 14 Apr 2024 20:19:31 -0400 Subject: [Dev] Orphan Libre package [tp_smapi] marked out-of-date In-Reply-To: <20240414232514.1200.80524@winston.parabola.nu> References: <20240414232514.1200.80524@winston.parabola.nu> Message-ID: <20240414201931.57d85bf4@parabola.localdomain> 'tp_smapi' is at the latest version 0.44, released Jul 31, 2023 is it not working? From bill-auger at peers.community Mon Apr 15 01:07:48 2024 From: bill-auger at peers.community (bill-auger) Date: Sun, 14 Apr 2024 21:07:48 -0400 Subject: [Dev] [PKG Submission] Submit fsearch In-Reply-To: <20240414194950.499d9a0b@parabola.localdomain> References: <20240329000436.50c69541@IntegralPC> <20240414194950.499d9a0b@parabola.localdomain> Message-ID: <20240414210748.61204a76@parabola.localdomain> there are built packages in pcr-testing now - plz test at least the x86_64 package to ensure that it behaves correctly - then they can be moved to pcr # pacman -U https://repo.parabola.nu/pool/parabola/fsearch-0.2.3-1-x86_64.pkg.tar.zst From integral at murena.io Mon Apr 15 04:17:23 2024 From: integral at murena.io (Integral) Date: Sun, 14 Apr 2024 21:17:23 -0700 Subject: [Dev] [PKG Submission] Submit fsearch In-Reply-To: <20240414210748.61204a76@parabola.localdomain> Message-ID: <20240414211723.65b63a34@IntegralPC> I have tested it on x86_64. It works.