From pagure at pagure.io Tue Jul 4 21:17:27 2023 From: pagure at pagure.io (=?utf-8?q?Grizzly_User?=) Date: Tue, 4 Jul 2023 21:17:27 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2374=3A_libre/iceweasel=3A_11?= =?utf-8?q?5=2E0-1=2Eparabola1?= Message-ID: grizzlyuser opened a new pull-request against the project: `abslibre` that you are following: `` libre/iceweasel: 115.0-1.parabola1 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/74 From bill-auger at peers.community Thu Jul 6 16:24:25 2023 From: bill-auger at peers.community (bill-auger) Date: Thu, 6 Jul 2023 12:24:25 -0400 Subject: [Dev] [abslibre] PR #74: libre/iceweasel: 115.0-1.parabola1 In-Reply-To: References: Message-ID: <20230706122425.34705596@parabola.localdomain> thanks again - extra credit for the reproducible branding package From bill-auger at peers.community Sat Jul 8 05:06:43 2023 From: bill-auger at peers.community (bill-auger) Date: Sat, 8 Jul 2023 01:06:43 -0400 Subject: [Dev] new keyring procedure Message-ID: <20230708010643.6c9555a5@parabola.localdomain> i re-wrote the keyring build recipe this week - this (hopefully) is inconsequential for the most part; but i must explain the changes the keyrings have been a recurring source of pain for years - we have discussed several ways to make it more robust - we have applied some of them; and some of them have worked well however, this week i needed to update my key; but the keyserver is not accepting uploads - the admin told me to wait a few days and try again - that is unfortunately the one factor that is out of our control one of the past ideas was to store hackers keys as text in hackers.git; so i thought this would be am excellent time to try that - i did, and it seems to work well as i studied the keyring package, i realized how ridiculously simple it actually is; yet as those of us who have studied the keyring makefile will know, that makefile is ridiculously complicated and unwieldy - we should have tried this long ago another benefit of getting rid of that makefile, is that it made 'parabola-keyring' be the only package which requires networking at build time (against parabola policy, strictly speaking) - the build is done entirely in the PKGBUILD now, with networking disabled - barring any unforeseen problems, i would declare that previous makefile to be obsolete - i can not imagine it ever being useful again so what does this mean for parabola devs? it means that you do not need to push your key to a keyserver - of course, you can; but that should never be factor for parabola users again - simply renew the expiration when necessary, dump the key to ASCII, and commit it to hackers.git there is a new 'keys/' directory - each hacker has a file named .asc - it is quite simple to grok - the process is explained in the PKGBUILD To generate a new keyring: $ KEY_ID= # ('pgp_keyid' in your hackers.git YAML file) $ cd /path/to/hackers.git/ $ gpg --armor --no-emit-version --export $KEY_ID > keys/$KEY_ID.asc $ git commit -m 'update my key' keys/$KEY_ID.asc $ git push parabola master of course, feel free to review the code if you are so inclined https://git.parabola.nu/abslibre.git/tree/libre/parabola-keyring/PKGBUILD From bill-auger at peers.community Sat Jul 8 21:03:30 2023 From: bill-auger at peers.community (bill-auger) Date: Sat, 8 Jul 2023 17:03:30 -0400 Subject: [Dev] the case for terse 'pkgdesc' In-Reply-To: <20230627104832.4468fc27@primary_laptop> References: <308330f0fe99990df9fbd714d4ecc8f560eb0385.camel@waelk.tech> <20230607124446.5f1bc0e3@parabola.localdomain> <4bedbed69bad004e7f49081fddf48484ed35eb64.camel@waelk.tech> <20230608055922.324011f4@parabola.localdomain> <74668973450988e6e5b877ff140a9fa79cb35812.camel@waelk.tech> <20230613175152.49c78b78@primary_laptop> <20230613221013.3d7e7db5@parabola.localdomain> <20230614070455.3ee49b3a@primary_laptop> <20230614062111.086b5ee7@parabola.localdomain> <20230614063428.59b927a8@parabola.localdomain> <20230614091003.79ad576a@parabola.localdomain> <20230627104832.4468fc27@primary_laptop> Message-ID: <20230708170330.411e1c75@parabola.localdomain> ok so there is something different about them - the remaining thing to nit-pick is that arch policy suggests the pkgdesc should not self-refer to the name of the software, and should be as terse as possible - i will make only these changes: - Flashrom is a utility which can be used to detect, + Utility to detect, - read, erase, write, write-protect or write-unprotect BIOS chips (FHW, + read, write, or write-protect BIOS chips (FHW, that seems sufficient to me - 'write' implies the ability to 'erase', and both 'write' and 'write-protect' imply the ability to 'write-unprotect' (which is not a common term anyways) From bill-auger at peers.community Sat Jul 8 21:17:45 2023 From: bill-auger at peers.community (bill-auger) Date: Sat, 8 Jul 2023 17:17:45 -0400 Subject: [Dev] the case for terse 'pkgdesc' In-Reply-To: <20230627104832.4468fc27@primary_laptop> References: <308330f0fe99990df9fbd714d4ecc8f560eb0385.camel@waelk.tech> <20230607124446.5f1bc0e3@parabola.localdomain> <4bedbed69bad004e7f49081fddf48484ed35eb64.camel@waelk.tech> <20230608055922.324011f4@parabola.localdomain> <74668973450988e6e5b877ff140a9fa79cb35812.camel@waelk.tech> <20230613175152.49c78b78@primary_laptop> <20230613221013.3d7e7db5@parabola.localdomain> <20230614070455.3ee49b3a@primary_laptop> <20230614062111.086b5ee7@parabola.localdomain> <20230614063428.59b927a8@parabola.localdomain> <20230614091003.79ad576a@parabola.localdomain> <20230627104832.4468fc27@primary_laptop> Message-ID: <20230708171745.34ce4a5d@parabola.localdomain> actually i sent that to soon - there are two other things i would make issue of 'flashrom' is an arch package, so we can not modify the pkgdesc without adopting the package - i assumed that the pkgdesc of 'flashrom' in this thead was the one arch uses; but it is not so we can not use it for comparison the arch pkgdesc: > Utility for reading, writing, erasing and verifying flash ROM chips the problem is that both packages meet that description - though the proposed pkgdescs did not mention 'verifying'; so it is not clear if they both have that feature then upon reading them more closely, what is evident per the proposed descriptions, is that 'flashrom' has _all_ features of 'flashrom-stable' and _more_ - that implies to me that 'flashrom-stable' has no value to parabola, which is the reason i began making a fuss about it in the first place so again, per those descriptions, it appears that its only value to parabola is "its not as rusty" (though that is probalby not a good rationale, and the pkgdesc does not mention that anyways) so, i think this should be revised again, so that it somehow clarifies any rationale for 'flashrom-stable' ie: what is the tangible benefit of 'flashrom-stable', if it only removes features if it adds no new functionality, but only removes some? From bill-auger at peers.community Sat Jul 8 22:00:06 2023 From: bill-auger at peers.community (bill-auger) Date: Sat, 8 Jul 2023 18:00:06 -0400 Subject: [Dev] [PKGBUILD][PATCH][UPDATE] Prosody Modules 0.12.3 In-Reply-To: References: Message-ID: <20230708180006.35faa062@parabola.localdomain> that comment in the PKGBUILD is confusing: > # The prosody-modules repository doesn't have tags that correspond to > # the prosody releases. So we used the commit right before June 09 > # to correspond to the prosody release. if the upstream does not tag the VCS properly, then where does pkgver='0.12.3' come from? - the suggestion seems to be that the upstream releases versioned tarballs - in that case, we should always prefer the tarball release to VCS - or do they only release binaries? in ether case i would ask them to release tarball sources (ideally), or at least to tag the VCS properly From bill-auger at peers.community Sun Jul 9 01:42:45 2023 From: bill-auger at peers.community (bill-auger) Date: Sat, 8 Jul 2023 21:42:45 -0400 Subject: [Dev] [PKGBUILD][PATCH][UPDATE] Prosody Modules 0.12.3 In-Reply-To: References: Message-ID: <20230708214245.6e7113e7@parabola.localdomain> just wanted to point out a minor flaw in this PKGBUILD - looks like denis overlooked it originally the libre source-ball was defined without a file extension, and without requiring a signature - i made the change, just wanted to mention it - the file extension is inconsequential, but the signature is important - source=(https://repo.parabola.nu/other/${pkgname}-libre/${pkgname}-libre-${pkgver}) + source=(https://repo.parabola.nu/other/${pkgname}-libre/${pkgname}-libre-${pkgver}.tar.xz{,.sig}) + validpgpkeys+=('3954A7AB837D0EA9CFA9798925DB7D9B5A8D4B40') # bill-auger From bill-auger at peers.community Sun Jul 9 02:23:57 2023 From: bill-auger at peers.community (bill-auger) Date: Sat, 8 Jul 2023 22:23:57 -0400 Subject: [Dev] [PKGBUILD][PATCH][UPDATE] Prosody Modules 0.12.3 In-Reply-To: References: Message-ID: <20230708222357.2e393ad6@parabola.localdomain> i also set wael as the Maintainer instead of "parabola hackers" i think we should consider it a matter of policy not to accept anything into PCR without a dedicated maintainer - the reason is that most packages in PCR got there because a very small number of users requested them, perhaps only one user - it is likely that no parabola dev uses them; so they are very likely to become forgotten cruft over time, especially if their users stop complaining about breakage (eg: because it has no more users) From wael at waelk.tech Sun Jul 9 09:08:30 2023 From: wael at waelk.tech (Wael Karram) Date: Sun, 09 Jul 2023 12:08:30 +0300 Subject: [Dev] [PKGBUILD][PATCH][UPDATE] Prosody Modules 0.12.3 In-Reply-To: <20230708180006.35faa062@parabola.localdomain> References: <20230708180006.35faa062@parabola.localdomain> Message-ID: <877178b5b2660c7e1c469114b38bff36cebfc023.camel@waelk.tech> On Sat, 2023-07-08 at 18:00 -0400, bill-auger wrote: > that comment in the PKGBUILD is confusing: > > # The prosody-modules repository doesn't have tags that correspond to > > # the prosody releases. So we used the commit right before June 09 > > # to correspond to the prosody release. > > if the upstream does not tag the VCS properly, then where does pkgver='0.12.3' > come from? - the suggestion seems to be that the upstream releases > versioned tarballs - in that case, we should always prefer the tarball release > to VCS - or do they only release binaries? > > in ether case i would ask them to release tarball sources (ideally), or at > least to tag the VCS properly > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev The VCS is for community contributions, and while most of the software there has proper licensing unlike what usually happens to contrib repos, the model is essentially of a rolling release. Hence, the upstream doesn't have proper releases as such and tagging cannot be done. This is why I've resolved to versioning it according to the current prosody version that is available in the repos - as generally the modules target the latest stable version and that is what parabola tracks too. Otherwise this would technically require constantly updating the package which is unfeasable, and in practice most deployments require the admins to manually pull the latest VCS version whenever they've updated the prosody daemon. There are two main issues I can see with this approach, but I don't think they're quite serious: 1) If someone installs a newer version of the modules package than that of the core prosody daemon package, they might have compatibility issues - but that necessarily means that they've intentionally not updated prosody on their system (as this package aims to track the prosody package). 2) There are some modules that would get updates in the VCS repo, but the updates won't reach this package until the prosody package gets updated. For most cases this isn't a big issue though as in practice most sysadmins only update the modules when they update prosody. -- Kind Regards, Wael Karram. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From wael at waelk.tech Sun Jul 9 09:15:21 2023 From: wael at waelk.tech (Wael Karram) Date: Sun, 09 Jul 2023 12:15:21 +0300 Subject: [Dev] the case for terse 'pkgdesc' In-Reply-To: <20230708171745.34ce4a5d@parabola.localdomain> References: <308330f0fe99990df9fbd714d4ecc8f560eb0385.camel@waelk.tech> <20230607124446.5f1bc0e3@parabola.localdomain> <4bedbed69bad004e7f49081fddf48484ed35eb64.camel@waelk.tech> <20230608055922.324011f4@parabola.localdomain> <74668973450988e6e5b877ff140a9fa79cb35812.camel@waelk.tech> <20230613175152.49c78b78@primary_laptop> <20230613221013.3d7e7db5@parabola.localdomain> <20230614070455.3ee49b3a@primary_laptop> <20230614062111.086b5ee7@parabola.localdomain> <20230614063428.59b927a8@parabola.localdomain> <20230614091003.79ad576a@parabola.localdomain> <20230627104832.4468fc27@primary_laptop> <20230708171745.34ce4a5d@parabola.localdomain> Message-ID: <6109a04d2ccfc7cd5420a2a082110e0978dc2555.camel@waelk.tech> On Sat, 2023-07-08 at 17:17 -0400, bill-auger wrote: > actually i sent that to soon - there are two other things i would make issue > of > > 'flashrom' is an arch package, so we can not modify the pkgdesc without > adopting the package - i assumed that the pkgdesc of 'flashrom' in this thead > was the one arch uses; but it is not so we can not use it for comparison > > the arch pkgdesc: > > Utility for reading, writing, erasing and verifying flash ROM chips > > the problem is that both packages meet that description - though the proposed > pkgdescs did not mention 'verifying'; so it is not clear if they both have > that feature > > then upon reading them more closely, what is evident per the proposed > descriptions, is that 'flashrom' has _all_ features of 'flashrom-stable' and > _more_ - that implies to me that 'flashrom-stable' has no value to parabola, > which is the reason i began making a fuss about it in the first place > > so again, per those descriptions, it appears that its only value to parabola > is > "its not as rusty" (though that is probalby not a good rationale, and the > pkgdesc does not mention that anyways) > > so, i think this should be revised again, so that it somehow clarifies any > rationale for 'flashrom-stable' > > ie: what is the tangible benefit of 'flashrom-stable', if it only removes > features if it adds no new functionality, but only removes some? > _______________________________________________ > Dev mailing list > Dev at lists.parabola.nu > https://lists.parabola.nu/mailman/listinfo/dev There is a bigger issue at play here: flashrom has been taken over by a google employee - the use of rust is merely a symptom, they're steering it in a direction suitable mostly only for use with chromebooks and dropping off compatibility layers and code that it had for multiple platforms. Saying that they overlap is true, but it isn't a matter of flashrom being more capable than flashrom-stable. Flashrom-stable seems to have been currently evicted our of coreboot, it isn't clear if Nico Huber is interested in fighting a battle with them on it. Currently this whole thing exists in limbo - Leah Rowe of Libreboot has expressed interest in carrying the development on in case Nico doesn't do anything about it in a few months. If anything, parabola should keep offering both in my opinion, but also keeping an eye out on any changes in the situation, as flashrom might introduce non-free parts. -- Kind Regards, Wael Karram, TeapotChat NetOP. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From bill-auger at peers.community Sun Jul 9 22:44:59 2023 From: bill-auger at peers.community (bill-auger) Date: Sun, 9 Jul 2023 18:44:59 -0400 Subject: [Dev] the case for terse 'pkgdesc' In-Reply-To: <6109a04d2ccfc7cd5420a2a082110e0978dc2555.camel@waelk.tech> References: <308330f0fe99990df9fbd714d4ecc8f560eb0385.camel@waelk.tech> <20230607124446.5f1bc0e3@parabola.localdomain> <4bedbed69bad004e7f49081fddf48484ed35eb64.camel@waelk.tech> <20230608055922.324011f4@parabola.localdomain> <74668973450988e6e5b877ff140a9fa79cb35812.camel@waelk.tech> <20230613175152.49c78b78@primary_laptop> <20230613221013.3d7e7db5@parabola.localdomain> <20230614070455.3ee49b3a@primary_laptop> <20230614062111.086b5ee7@parabola.localdomain> <20230614063428.59b927a8@parabola.localdomain> <20230614091003.79ad576a@parabola.localdomain> <20230627104832.4468fc27@primary_laptop> <20230708171745.34ce4a5d@parabola.localdomain> <6109a04d2ccfc7cd5420a2a082110e0978dc2555.camel@waelk.tech> Message-ID: <20230709184459.2c51c381@parabola.localdomain> it appears that "keeping an eye out on any changes in the situation" is the most important part of that explanation - in my experience, that explanation suggests to me that flashrom-stable will be very short-lived - most new software projects lose momentum or are abandoned within six months; and that is even more likely for those which are forks made for purely ethical of political reasons: * avconv? (was hyped to replace ffmpeg - it did not) * avideo? (was hyped to replace youtube-dl - it did not) * tenacity? (was hyped to replace audacity - it did not) remember those? of course not; because they never gained traction, because there was nothing fundamentally wrong with the original upstream code in the first place i have to strong suspicion that we will need to revisit this issue within a year - at that time, i suspect that one or the other will need to go, or if it is very important software with no alternatives, one (probably the original) should be kept frozen at the last-known good version ok, so we still need a more informational pkgdesc, something which distinguishes it from flashrom - problem is, that last explanation does not help much - all that implies: pkgdesc="the lass-capable flashrom fork, but without rust and is not maintained by a google employee" when i read that, it tells me "this is a petty excuse for a fork" - maybe those reasons will become important in the future; but the future is not here yet if you want to watch both of them closely, go for it; but if it were me, i would wait until the original upstream is demonstrably unfit for parabola, and ideally, the new fork has proven itself to be a long-term solution (something like two or three years old, minimum) - then, the original pkgdesc would be fine, because there would again be only one flashrom package From bill-auger at peers.community Sun Jul 9 22:59:59 2023 From: bill-auger at peers.community (bill-auger) Date: Sun, 9 Jul 2023 18:59:59 -0400 Subject: [Dev] [PKGBUILD][PATCH][UPDATE] Prosody Modules 0.12.3 In-Reply-To: <877178b5b2660c7e1c469114b38bff36cebfc023.camel@waelk.tech> References: <20230708180006.35faa062@parabola.localdomain> <877178b5b2660c7e1c469114b38bff36cebfc023.camel@waelk.tech> Message-ID: <20230709185959.5db97196@parabola.localdomain> On Sun, 09 Jul 2023 12:08:30 +0300 Wael wrote: > Hence, the upstream doesn't have proper releases as such and tagging cannot be > done. tagging is always possible - it takes only seconds - i would ask the upstream to do it, and i would probably reject their software if they refused per that description, this is, and always will be, an un-versioned VCS-only source, which is against parabola policy, except for extraordinary circumstances (a temporary mix-up, an emergency patch release, or otherwise a super critical software - at the very least, it should be named 'prosody-modules-hg' On Sun, 09 Jul 2023 12:08:30 +0300 Wael wrote: > This is why I've resolved to versioning it according to the current prosody > version that is available in the repos though that seems sensible, it is mis-information; and does not have the desired effect as you expect - the compatibility problem can be accomplished by pinning it to a specific version of prosody - depends=('prosody') + depends=('prosody=0.12.3') From bill-auger at peers.community Sun Jul 9 23:09:33 2023 From: bill-auger at peers.community (bill-auger) Date: Sun, 9 Jul 2023 19:09:33 -0400 Subject: [Dev] [PKGBUILD][PATCH][UPDATE] Prosody Modules 0.12.3 In-Reply-To: <20230709185959.5db97196@parabola.localdomain> References: <20230708180006.35faa062@parabola.localdomain> <877178b5b2660c7e1c469114b38bff36cebfc023.camel@waelk.tech> <20230709185959.5db97196@parabola.localdomain> Message-ID: <20230709190933.1f948ee5@parabola.localdomain> this is what i am suggesting - note how much smaller the comment has shrunk - that is generally a good smell diff --git a/pcr/prosody-modules/PKGBUILD b/pcr/prosody-modules/PKGBUILD index e95ed62c1..29a3b983e 100644 --- a/pcr/prosody-modules/PKGBUILD +++ b/pcr/prosody-modules/PKGBUILD @@ -3,51 +3,19 @@ # Maintainer: Wael Karram -# NOTE: -# The prosody-modules repository doesn't have tags that correspond to -# the prosody releases. So we used the commit right before June 09 -# to correspond to the prosody release. -# -# In the prosody source code we have: -# $ hg tags | grep "^0.12.1" -# 0.12.1 12526:252ed01896dd -# $ hg log -# [...] -# changeset: 12543:cf29bdb74c15 -# branch: 0.12 -# parent: 12526:252ed01896dd -# user: Matthew Wild -# date: Thu Jun 09 12:42:57 2022 +0100 -# summary: Added tag 0.12.1 for changeset 252ed01896dd -# [...] -# changeset: 12526:252ed01896dd -# branch: 0.12 -# tag: 0.12.1 -# user: Kim Alvefur -# date: Fri May 27 14:45:35 2022 +0200 -# summary: mod_smacks: Bounce unhandled stanzas from local origin (fix #1759) -# So we used the revision 4959:0989dea9b356 -# and in prosody-modules we have: -# $ hg log -# changeset: 4960:59bedf167910 -# user: Kim Alvefur -# date: Mon Jun 13 14:25:39 2022 +0200 -# summary: mod_muc_ping: Remove since Prosody mod_muc 0.11+ covers this natively -# -# changeset: 4959:0989dea9b356 -# user: Kim Alvefur -# date: Sun Jun 05 21:59:17 2022 +0200 -# summary: mod_rest: Add various things to openapi spec - - -pkgname=prosody-modules -pkgver=0.12.3 +# NOTE: The prosody-modules repository does not version nor make releases; +# so we use a date, and pin it to 'prosody' releases for compatibility. + + +pkgname=prosody-modules-hg +pkgver=20230708 +_prosody_ver=0.12.3 pkgrel=1 pkgdesc="Prosody community modules, includes experimental ones." arch=('any') url="https://modules.prosody.im/" license=('MIT') -depends=('prosody') +depends=(prosody=${_prosody_ver}) makedepends=('mercurial') mksource=(${pkgname}-${pkgver}::hg+https://hg.prosody.im/prosody-modules/#revision=5579) source=(https://repo.parabola.nu/other/${pkgname}-libre/${pkgname}-libre-${pkgver}.tar.xz{,.sig}) From nobody at parabola.nu Thu Jul 13 01:52:31 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Thu, 13 Jul 2023 01:52:31 -0000 Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date Message-ID: <20230713015231.2851825.56720@winston.parabola.nu> eliotreyna at disroot.org wants to notify you that the following packages may be out-of-date: * iceweasel 1:115.0-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/iceweasel/ The user provided the following additional text: Firefox source code has been updated to the version 115.0.2. The following bugfixes are: -Caret displaying in text editor in some websites. -Audio rendering bug in some websites. -PatternTransform translate using the wrong units. -A critical security fix. For more information, please follow the links below: https://www.mozilla.org/en-US/security/advisories/mfsa2023-26/ https://www.mozilla.org/en-US/firefox/115.0.2/releasenotes/ Thanks. From wael at waelk.tech Thu Jul 13 08:02:33 2023 From: wael at waelk.tech (Wael Karram) Date: Thu, 13 Jul 2023 11:02:33 +0300 Subject: [Dev] [PATCH][PKGBUILD] Update PHC-Intel to Revision 45 Message-ID: <915ef0addee681a3a114cbc43dff1130da2e93bb.camel@waelk.tech> Hello, This patch updates the phc-intel package to revision 45. Tested on my machines (X200 and desktop Core2Quad system). -- Kind Regards, Wael Karram. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-PHC-Intel-to-revision-45.patch Type: text/x-patch Size: 1371 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From bill-auger at peers.community Sat Jul 15 06:09:28 2023 From: bill-auger at peers.community (bill-auger) Date: Sat, 15 Jul 2023 02:09:28 -0400 Subject: [Dev] Fw: [GNU-linux-libre] third-party package managers Message-ID: <20230715020928.753fc1e3@parabola.localdomain> just to note that i moved the tables of evaluations and proposals to the wiki, to make it easier reference and to maintain https://wiki.parabola.nu/TPPM_Liberation_Project From pagure at pagure.io Mon Jul 17 11:03:19 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Mon, 17 Jul 2023 11:03:19 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2375=3A_libre/ktorrent_withou?= =?utf-8?q?t_qt5-webengine?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` libre/ktorrent without qt5-webengine `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/75 From pagure at pagure.io Mon Jul 17 18:49:06 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Mon, 17 Jul 2023 18:49:06 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2375=3A_libre/ktorrent_withou?= =?utf-8?q?t_qt5-webengine?= In-Reply-To: Message-ID: solvefinder closed without merging a pull-request against the project: `abslibre` that you are following. Closed pull-request: `` libre/ktorrent without qt5-webengine `` https://pagure.io/abslibre/pull-request/75 From pagure at pagure.io Mon Jul 17 20:10:15 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Mon, 17 Jul 2023 20:10:15 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2376=3A_libre/ktorrent_withou?= =?utf-8?q?t_qt5-webengine?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` libre/ktorrent without qt5-webengine `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/76 From pagure at pagure.io Mon Jul 17 20:12:51 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Mon, 17 Jul 2023 20:12:51 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2377=3A_libre/ktorrent_withou?= =?utf-8?q?t_qt5-webengine?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` libre/ktorrent without qt5-webengine `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/77 From pagure at pagure.io Mon Jul 17 20:13:23 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Mon, 17 Jul 2023 20:13:23 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2377=3A_libre/ktorrent_withou?= =?utf-8?q?t_qt5-webengine?= In-Reply-To: Message-ID: solvefinder closed without merging a pull-request against the project: `abslibre` that you are following. Closed pull-request: `` libre/ktorrent without qt5-webengine `` https://pagure.io/abslibre/pull-request/77 From pagure at pagure.io Tue Jul 18 02:52:06 2023 From: pagure at pagure.io (=?utf-8?q?bill-auger?=) Date: Tue, 18 Jul 2023 02:52:06 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2376=3A_libre/ktorrent_withou?= =?utf-8?q?t_qt5-webengine?= In-Reply-To: Message-ID: billauger merged a pull-request against the project: `abslibre` that you are following. Merged pull-request: `` libre/ktorrent without qt5-webengine `` https://pagure.io/abslibre/pull-request/76 From pagure at pagure.io Tue Jul 18 06:53:37 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Tue, 18 Jul 2023 06:53:37 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2378=3A_libre/parabola-appstr?= =?utf-8?q?eam_data_without_info_about_nonfree_packages?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` libre/parabola-appstream data without info about nonfree packages `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/78 From pagure at pagure.io Tue Jul 18 08:38:11 2023 From: pagure at pagure.io (=?utf-8?q?bill-auger?=) Date: Tue, 18 Jul 2023 08:38:11 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2378=3A_libre/parabola-appstr?= =?utf-8?q?eam_data_without_info_about_nonfree_packages?= In-Reply-To: Message-ID: billauger commented on the pull-request: `libre/parabola-appstream data without info about nonfree packages` that you are following: `` this is related to multiple open tickets on the bug tracker and an ongoing discussion on the FSDG mailing list https://labs.parabola.nu/issues/813 https://labs.parabola.nu/issues/1413 ``` if pkg in blacklist: ``` its not clear if the solution your proposing would be effective, unless all software in the index is exclusively arch packages - anything else would not be filtered; and that would make the two programs which use it 'gnome-software' and KDE 'discover' to be considered as TPPMs, which we are actively trying to get rid of or patch if it is the former, we should discuss this on the bug tracker - if it is the latter, we should discuss this on the FSDG mailing list `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/78 From pagure at pagure.io Tue Jul 18 18:51:50 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Tue, 18 Jul 2023 18:51:50 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2379=3A_updpkg=3A_libre/ark_2?= =?utf-8?b?My4wNC4z?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` updpkg: libre/ark 23.04.3 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/79 From pagure at pagure.io Wed Jul 19 08:09:01 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Wed, 19 Jul 2023 08:09:01 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2380=3A_updpkg=3A_nonsystemd/?= =?utf-8?q?pipewire_1=3A0=2E3=2E74?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` updpkg: nonsystemd/pipewire 1:0.3.74 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/80 From pagure at pagure.io Thu Jul 20 08:58:22 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Thu, 20 Jul 2023 08:58:22 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2381=3A_updpkg=3A_libre/libks?= =?utf-8?q?ysguard_5=2E27=2E6?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` updpkg: libre/libksysguard 5.27.6 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/81 From pagure at pagure.io Thu Jul 20 10:06:28 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Thu, 20 Jul 2023 10:06:28 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2382=3A_libre/discover_withou?= =?utf-8?q?t_nonfree_webview_support_and_TPPM_functionality?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` libre/discover without nonfree webview support and TPPM functionality `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/82 From pagure at pagure.io Thu Jul 20 16:12:35 2023 From: pagure at pagure.io (=?utf-8?q?bill-auger?=) Date: Thu, 20 Jul 2023 16:12:35 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2382=3A_libre/discover_withou?= =?utf-8?q?t_nonfree_webview_support_and_TPPM_functionality?= In-Reply-To: Message-ID: billauger commented on the pull-request: `libre/discover without nonfree webview support and TPPM functionality` that you are following: `` depends on PR #78 like i noted on #78, it is not obvious if we can use them, or what is their value if all they can do is install the same packages that pacman can - we should discuss this on the bug tracker or mailing list https://labs.parabola.nu/issues/1413 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/82 From pagure at pagure.io Thu Jul 20 16:13:09 2023 From: pagure at pagure.io (=?utf-8?q?bill-auger?=) Date: Thu, 20 Jul 2023 16:13:09 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2378=3A_libre/parabola-appstr?= =?utf-8?q?eam_data_without_info_about_nonfree_packages?= In-Reply-To: Message-ID: billauger commented on the pull-request: `libre/parabola-appstream data without info about nonfree packages` that you are following: `` depends on PR #82 `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/78 From nobody at parabola.nu Fri Jul 21 15:01:03 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Fri, 21 Jul 2023 15:01:03 -0000 Subject: [Dev] Orphan Libre package [nextcloud-client] marked out-of-date Message-ID: <20230721150103.2851826.39162@winston.parabola.nu> me at ssene.ca wants to notify you that the following packages may be out-of-date: * nextcloud-client 2:3.7.4-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/nextcloud-client/ * nextcloud-client-cloudproviders 2:3.7.4-1.parabola1 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/nextcloud-client-cloudproviders/ The user provided the following additional text: arch pkg is at 2:3.9.0-2. client pops up with > New Nextcloud Client 3.9.0 is available. Please open https://nextlcoud.com/install to download the update whenever it's opened. From kwopleq at proton.me Fri Jul 21 20:39:19 2023 From: kwopleq at proton.me (kwopleq) Date: Fri, 21 Jul 2023 20:39:19 +0000 Subject: [Dev] Discussion about package "discover" Message-ID: <61_x8ardCSqcJ0vQXydxLtn177eqA1OsLajbcfTvBdYpUnwJt_tRCKge4QAemUgm2McgcTLpT3A34MjnIpKOWNjntnqIONqhJCYcy927vxo=@proton.me> I've recently made libre versions of "archlinux-appstream-data" and "discover". There were webview support and TPPM functionality in discover, but now, hopefully it's removed (https://pagure.io/abslibre/pull-request/82). There's still flatpak support in "discover" that might result in nonfree packages. It could be patched if necessary. I've also patched "archlinux-appstream-data" so it doesn't include nonfree arch packages (https://pagure.io/abslibre/pull-request/78). It seems like there's no nonfree functionality left in "discover" and I'd like to see it in Parabola repositories. As "Parabola is a complete, user-friendly operating system, suitable for general "everyday" use" I think that "discover" would be a nice pacman frontend, that provides categorization of software, auto updater and more user-friendly interface. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pagure at pagure.io Sat Jul 22 09:40:02 2023 From: pagure at pagure.io (=?utf-8?q?Solve_Finder?=) Date: Sat, 22 Jul 2023 09:40:02 +0000 (GMT) Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2383=3A_archlinux-wallpapers_?= =?utf-8?q?replacement?= Message-ID: solvefinder opened a new pull-request against the project: `abslibre` that you are following: `` archlinux-wallpapers replacement `` To reply, visit the link below or just reply to this email https://pagure.io/abslibre/pull-request/83 From GNUtoo at cyberdimension.org Wed Jul 26 16:35:54 2023 From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli) Date: Wed, 26 Jul 2023 18:35:54 +0200 Subject: [Dev] Fw: [GNU-linux-libre] third-party package managers In-Reply-To: <20230715020928.753fc1e3@parabola.localdomain> References: <20230715020928.753fc1e3@parabola.localdomain> Message-ID: <20230726183554.7b87d4b0@primary_laptop> Hi, On Sat, 15 Jul 2023 02:09:28 -0400 bill-auger wrote: > just to note that i moved the tables of evaluations and proposals to > the wiki, to make it easier reference and to maintain > > https://wiki.parabola.nu/TPPM_Liberation_Project Thanks a lot for that work. Would it be possible to also license that specific page under this license: > Content is available under GNU Free Documentation License 1.3. By > contributing to any page on this wiki, you agree to assign copyright > for your contribution to the Free Software Foundation (see > LibrePlanet:Copyrights for details). The Free Software Foundation > promises to always use either a verbatim copying license or a free > documentation license when publishing your contribution. We grant you > back all your rights under copyright, including the rights to copy, > modify, and redistribute your contributions. You are also promising > us that you wrote this yourself, or copied it from a public domain or > similar free resource. DO NOT SUBMIT COPYRIGHTED WORK WITHOUT > PERMISSION! This could be done with text like that: > Additionally, the content of this page is available under the > following license(s) [list the licenses like the one above]. This would allow combining that work with other similar work from the Libreplanet wiki. To make sure things can work be both ways, if you want me to add the following license (from the Parbaola wiki) on some related Libreplanet wiki pages that I wrote, I could add this one as well (assuming I'm the only author, else I'd have to contact the other authors first): > Content is available under Creative Commons Attribution-ShareAlike > 4.0 International License (or at your option, any later version) > unless otherwise noted Denis. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From bill-auger at peers.community Thu Jul 27 01:26:58 2023 From: bill-auger at peers.community (bill-auger) Date: Wed, 26 Jul 2023 21:26:58 -0400 Subject: [Dev] Fw: [GNU-linux-libre] third-party package managers In-Reply-To: <20230726183554.7b87d4b0@primary_laptop> References: <20230715020928.753fc1e3@parabola.localdomain> <20230726183554.7b87d4b0@primary_laptop> Message-ID: <20230726212659.4a64a91b@parabola.localdomain> if license compatibility is a concern, i would suggest CC-zero, just like we did for the PKGBUILDs - that article is not a work of creativity or a specification, but a dry collection of facts that anyone could collect in other words, like the PKGBUILDs, i dont think it meets the threshold of creativity for copyright From wael at waelk.tech Sun Jul 30 13:46:49 2023 From: wael at waelk.tech (Wael Karram) Date: Sun, 30 Jul 2023 16:46:49 +0300 Subject: [Dev] [PATCH][PKGBUILD] Update LaGrange Gemini Client to 1.16.5 Message-ID: Hello, I've attached the patch for the updated package build for 1.16.5. -- Kind Regards, Wael Karram. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Updated-lagrange-to-1.16.5.patch Type: text/x-patch Size: 960 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From wael at waelk.tech Sun Jul 30 14:08:03 2023 From: wael at waelk.tech (Wael Karram) Date: Sun, 30 Jul 2023 17:08:03 +0300 Subject: [Dev] [PATCH][PKGBUILD] Update Inspircd to 3.16.1 Message-ID: <5161da86e4ac9e530f080cdb23e0a39b10b2ec2e.camel@waelk.tech> Hello, I've attached the updated PKGBUILD. -- Kind Regards, Wael Karram. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-inspircd-to-3.16.1.patch Type: text/x-patch Size: 1761 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From wael at waelk.tech Mon Jul 31 04:41:46 2023 From: wael at waelk.tech (Wael Karram) Date: Mon, 31 Jul 2023 07:41:46 +0300 Subject: [Dev] [PATCH] Upgrade Inspircd to 3.16.1 Message-ID: Hello, I've attached the patch to update inspircd to 3.16.1 (latest available release). -- Kind Regards, Wael Karram. -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Update-inspircd-to-3.16.1.patch Type: text/x-patch Size: 1761 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: This is a digitally signed message part URL: From nobody at parabola.nu Mon Jul 31 06:04:15 2023 From: nobody at parabola.nu (Parabola Website Notification) Date: Mon, 31 Jul 2023 06:04:15 -0000 Subject: [Dev] Orphan Libre package [psutils] marked out-of-date Message-ID: <20230731060415.2851826.23827@winston.parabola.nu> wael at waelk.tech wants to notify you that the following packages may be out-of-date: * psutils 1.17-6.parabola2 [libre] (armv7h): https://parabolagnulinux.org/packages/libre/armv7h/psutils/ * psutils 1.17-6.parabola2 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/psutils/ * psutils 1.17-6.parabola2 [libre] (x86_64): https://parabolagnulinux.org/packages/libre/x86_64/psutils/ The user provided the following additional text: Package out of date compared to the one available from the upstreams, needs rebuilding. From bill-auger at peers.community Mon Jul 31 11:36:25 2023 From: bill-auger at peers.community (bill-auger) Date: Mon, 31 Jul 2023 07:36:25 -0400 Subject: [Dev] Discussion about package "discover" In-Reply-To: <61_x8ardCSqcJ0vQXydxLtn177eqA1OsLajbcfTvBdYpUnwJt_tRCKge4QAemUgm2McgcTLpT3A34MjnIpKOWNjntnqIONqhJCYcy927vxo=@proton.me> References: <61_x8ardCSqcJ0vQXydxLtn177eqA1OsLajbcfTvBdYpUnwJt_tRCKge4QAemUgm2McgcTLpT3A34MjnIpKOWNjntnqIONqhJCYcy927vxo=@proton.me> Message-ID: <20230731073625.3a454f36@parabola.localdomain> On Fri, 21 Jul 2023 20:39:19 +0000 kwopleq wrote: > There were webview support and TPPM functionality in discover, but now, hopefully it's removed (https://pagure.io/abslibre/pull-request/82). > There's still flatpak support in "discover" that might result in nonfree packages. It could be patched if necessary. if the flatpak feature is still functional, then 'discover' is still a TPPM, and would still need some patching On Fri, 21 Jul 2023 20:39:19 +0000 kwopleq wrote: > I've also patched "archlinux-appstream-data" so it doesn't include nonfree arch packages (https://pagure.io/abslibre/pull-request/78). does "archlinux-appstream-data" include only arch packages? On Fri, 21 Jul 2023 20:39:19 +0000 kwopleq wrote: > As "Parabola is a complete, user-friendly operating system, suitable for general "everyday" use" I think that "discover" would be a nice pacman frontend, that provides categorization of software, auto updater and more user-friendly interface. 'octopi' already meets that description and is DE-agnostic - 'gnome-software' and 'discover' are much heavier; because they depend on large portions of GNOME or KDE