From GNUtoo at cyberdimension.org  Sat Aug  6 10:25:26 2022
From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli)
Date: Sat, 6 Aug 2022 12:25:26 +0200
Subject: [Dev] [PATCH] blacklist.txt: fix syntax
In-Reply-To: <20220715084753.25612-1-casiniandrea26@gmail.com>
References: <20220715084753.25612-1-casiniandrea26@gmail.com>
Message-ID: <20220806122526.4c2e8179@primary_laptop>

Hi,

On Fri, 15 Jul 2022 10:47:53 +0200
ditadipolvere08 <casiniandrea26 at gmail.com> wrote:

> ---
>  blacklist.txt | 132
> +++++++++++++++++++++++++------------------------- 1 file changed, 66
> insertions(+), 66 deletions(-)
> 
> diff --git a/blacklist.txt b/blacklist.txt
> index 0cdca8d..875fa26 100644
> --- a/blacklist.txt
> +++ b/blacklist.txt
[...]

Thanks a lot for the patches.

I've reviewed and they are fine.

For this one I've modified a bit the commit.

I'm currently offline so I'll try to push the commit as soon as I'm
online again, though this mail might arrive first.

Denis.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220806/81c4a1a4/attachment.sig>

From wael at waelk.tech  Thu Aug 11 07:26:40 2022
From: wael at waelk.tech (Wael Karram)
Date: Thu, 11 Aug 2022 10:26:40 +0300
Subject: [Dev] [prosody-community-modules] proposed package for prosody's
 modules
Message-ID: <20220811102640.071f8fba.wael@waelk.tech>

Hello,
Currently anyone using prosody on Parabola will most likely have to download
packages from the source repository to get full functionality in prosody
(reliant on their community modules).
I propose this package as a solution to that which allows packaging the same
modules through the distro's repositories instead.

I've attached the PKGBUILD I came up with and started to vet the source's
licensing.
On the latter issue it seems that almost everything is licensed under the MIT
license, but I want to check all modules to make sure such is the case (I've
asked on the prosody support channel and the recommended I double-check just in
case).

-- 
Kind Regards,
Wael Karram.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PKGBUILD
Type: application/octet-stream
Size: 454 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220811/4b56890d/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220811/4b56890d/attachment-0001.sig>

From lukeshu at lukeshu.com  Sat Aug 13 23:45:35 2022
From: lukeshu at lukeshu.com (lukeshu at lukeshu.com)
Date: Sat, 13 Aug 2022 17:45:35 -0600
Subject: [Dev] Parabola credentials
In-Reply-To: <87bksnd899.wl-lukeshu@lukeshu.com>
References: <87sh301fv8.wl-lukeshu@lukeshu.com>
 <45799fdb2a339ee007033c43aaa084e9@riseup.net>
 <107baedfb1fba4e8a336914ae0633ef5@riseup.net>
 <87bksnd899.wl-lukeshu@lukeshu.com>
Message-ID: <878rnrd7xc.wl-lukeshu@lukeshu.com>

I've removed your Django account from the support-staff group, which
should remove you from the web page.

-- 
Happy hacking,
~ Luke Shumaker

On Sat, 13 Aug 2022 17:38:26 -0600,
<lukeshu at lukeshu.com> wrote:
> 
> Kathryn,
> 
> Sorry I missed your initial reply.
> 
> Will do.
> 
> -- 
> Happy hacking,
> ~ Luke Shumaker
> 
> On Thu, 11 Aug 2022 09:50:18 -0600,
> ingegnue at riseup.net wrote:
> > 
> > Hi Luke, could you remove me (Kathryn Bukovi) from the Parabola website?
> > I appreciate your honorable mention and that it is there still, but I no
> > longer use Parabola and haven't for some years now. I have no time
> > anymore...and it doesn't feel comfortable to still be on there, I don't
> > deserve any credit. I apologize for not turning out to volunteer as much
> > as I had wanted, but life got in the way.
> > 
> > https://www.parabola.nu/people/support-staff/
> > 
> > On 2018-09-24 20:41, ingegnue at riseup.net wrote:
> > > Hi Luke, 
> > > 
> > > If you can can remove me, that would be good. I will come back some time
> > > in the future, when I am better at programming and git. Probably under a
> > > different username, so that's why I suggest removing me.
> > > 
> > > Thanks!
> > > 
> > > ingeGNUe
> > > 
> > > On 2018-08-27 06:30, Luke Shumaker wrote:
> > >> Hi Kathryn,
> > >>
> > >> It seems you have no packages in the current pacman repos, and haven't
> > >> committed to any of the repos at git.parabola.nu in over a year.  So,
> > >> I'm disabling your access to Parabola infrastructure, and moving you
> > >> from "hackers" to "fellows".  That isn't to say that we don't want you
> > >> around, or that you aren't welcome!  If you'd like to start
> > >> contributing again, just let us know.
> > >>
> > >> Your ingegnue at parabola.nu email forwarding address will continue to
> > >> function.  If you would like to update where it forwards to, or would
> > >> like it disabled, let me know.

From GNUtoo at cyberdimension.org  Mon Aug 15 17:26:25 2022
From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli)
Date: Mon, 15 Aug 2022 19:26:25 +0200
Subject: [Dev] [prosody-community-modules] proposed package for
 prosody's modules
In-Reply-To: <20220811102640.071f8fba.wael@waelk.tech>
References: <20220811102640.071f8fba.wael@waelk.tech>
Message-ID: <20220815192625.1cb2f228@primary_laptop>

On Thu, 11 Aug 2022 10:26:40 +0300
Wael Karram <wael at waelk.tech> wrote:

> Hello,
Hi,

> Currently anyone using prosody on Parabola will most likely have to
> download packages from the source repository to get full
> functionality in prosody (reliant on their community modules).
> I propose this package as a solution to that which allows packaging
> the same modules through the distro's repositories instead.
> 
> I've attached the PKGBUILD I came up with and started to vet the
> source's licensing.
> On the latter issue it seems that almost everything is licensed under
> the MIT license, but I want to check all modules to make sure such is
> the case (I've asked on the prosody support channel and the
> recommended I double-check just in case).
A way to deal with that would be to use mksource() to only include the
source code that you audited for licensing. This way we could include
the work right now without waiting for it to be completed.

You could then send subsequent patches to add more modules.

> # Maintainer: Wael Karram <wael at waelk.tech>

If you did the PKGBUILD yourself, and that you want to maintain it,
using something like is better since it helps clarifying the license:
> # Copyright (C) 2022 Wael Karram <wael at waelk.tech>
> # SPDX-License-Identifier: CC0-1.0
> # Maintainer: Wael Karram <wael at waelk.tech>

If you want everybody (you included) to maintain it, the following can
be used instead:
> # Copyright (C) 2022 Wael Karram <wael at waelk.tech>
> # SPDX-License-Identifier: CC0-1.0
> # Maintainers: Parabola hackers <dev at lists.parabola.nu>

> pkgname=prosody-community-modules
> pkgver=0.12.1
> pkgrel=1
> pkgdesc="Prosody community modules."

The README has the following:
> Community repository for non-core, unofficial and/or experimental
> plugins for [Prosody][]. [...]
> 
> There are lots of fun and exciting modules to be found here, we know
> you'll like it.  However please note that each module is in a
> different state of development.  Some are proof-of-concept, others
> are quite stable and ready for production use.  Be sure to read the
> wiki page of any module before installing it on your server.
I think it is important to indicate that some of the modules are
experimental or even worse (work in progress / proof of concept) in the
pkgdesc, otherwise users might have different expectations of the
modules quality.

> arch=('any')
> url="https://modules.prosody.im/"
> license=('MIT')
> depends=('prosody')
> makedepends=('mercurial')
> source=("hg+https://hg.prosody.im/prosody-modules/")
Here we download some source, but we somehow need to tell mercurial to
fetch a specific version (the one that corresponds to 0.12.1).

> sha1sums=('SKIP')
> 
> package() {
> 	mkdir -p "${pkgdir}/usr/lib/prosody/modules/"
> 	cp -r "${srcdir}/prosody-modules/" \
>             "${pkgdir}/usr/lib/prosody/modules/" 
> }
There is some issues with that approach. We end up with a
/usr/lib/prosody/modules/prosody-modules/.hg directory.

A way to deal with that would be to at least delete that directory
after the copy.

I'm also not sure if just copying the directories is the best way to do
proper packages, but given that some of the modules are experimental
or a proof of concept, if the way it is packaged works, that is probably
good enough.

PS: Note that it is also possible to send patches for review. This way
    we can reuse your commit message, so if you have interesting things
    to add there they get included in the commit.

Denis.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220815/8b4fea6a/attachment.sig>

From wael at waelk.tech  Tue Aug 16 10:39:03 2022
From: wael at waelk.tech (Wael Karram)
Date: Tue, 16 Aug 2022 13:39:03 +0300
Subject: [Dev] [prosody-community-modules] proposed package for prosody's
 modules
In-Reply-To: <20220815192625.1cb2f228@primary_laptop>
References: <20220811102640.071f8fba.wael@waelk.tech>
 <20220815192625.1cb2f228@primary_laptop>
Message-ID: <20220816133903.4b32d99b.wael@waelk.tech>

On Mon, 15 Aug 2022 19:26:25 +0200
Denis 'GNUtoo' Carikli <GNUtoo at cyberdimension.org> wrote:

> On Thu, 11 Aug 2022 10:26:40 +0300
> Wael Karram <wael at waelk.tech> wrote:
> 
> > Hello,  
> Hi,
> 
> > Currently anyone using prosody on Parabola will most likely have to
> > download packages from the source repository to get full
> > functionality in prosody (reliant on their community modules).
> > I propose this package as a solution to that which allows packaging
> > the same modules through the distro's repositories instead.
> > 
> > I've attached the PKGBUILD I came up with and started to vet the
> > source's licensing.
> > On the latter issue it seems that almost everything is licensed under
> > the MIT license, but I want to check all modules to make sure such is
> > the case (I've asked on the prosody support channel and the
> > recommended I double-check just in case).  
> A way to deal with that would be to use mksource() to only include the
> source code that you audited for licensing. This way we could include
> the work right now without waiting for it to be completed.
> 
> You could then send subsequent patches to add more modules.
> 
> > # Maintainer: Wael Karram <wael at waelk.tech>  
> 
> If you did the PKGBUILD yourself, and that you want to maintain it,
> using something like is better since it helps clarifying the license:
> > # Copyright (C) 2022 Wael Karram <wael at waelk.tech>
> > # SPDX-License-Identifier: CC0-1.0
> > # Maintainer: Wael Karram <wael at waelk.tech>  
> 
> If you want everybody (you included) to maintain it, the following can
> be used instead:
> > # Copyright (C) 2022 Wael Karram <wael at waelk.tech>
> > # SPDX-License-Identifier: CC0-1.0
> > # Maintainers: Parabola hackers <dev at lists.parabola.nu>  
> 
> > pkgname=prosody-community-modules
> > pkgver=0.12.1
> > pkgrel=1
> > pkgdesc="Prosody community modules."  
I have fixed the copyright and identifier, I've also dealt with the .hg
directory.
As for the modules and their licensing status, it seems so far that everything
is MIT-licensed.
I'll sit in the evening again and double check, but if that is the case then no
need for mksource hackery I think.

> 
> The README has the following:
> > Community repository for non-core, unofficial and/or experimental
> > plugins for [Prosody][]. [...]
> > 
> > There are lots of fun and exciting modules to be found here, we know
> > you'll like it.  However please note that each module is in a
> > different state of development.  Some are proof-of-concept, others
> > are quite stable and ready for production use.  Be sure to read the
> > wiki page of any module before installing it on your server.  
> I think it is important to indicate that some of the modules are
> experimental or even worse (work in progress / proof of concept) in the
> pkgdesc, otherwise users might have different expectations of the
> modules quality.
> 
> > arch=('any')
> > url="https://modules.prosody.im/"
> > license=('MIT')
> > depends=('prosody')
> > makedepends=('mercurial')
> > source=("hg+https://hg.prosody.im/prosody-modules/")  
> Here we download some source, but we somehow need to tell mercurial to
> fetch a specific version (the one that corresponds to 0.12.1).
> 
There is no point in doing that, I've checked the official docs, it seems as
though packages should be updated in tandem with the core server software - yet
most of them still retain backwards compatibility (the issue is with
forwards-compatibility sometimes).
I propose that this package gets updated and versioned in tandem with the core
prosody software to avoid any issues.
> > sha1sums=('SKIP')
> > 
> > package() {
> > 	mkdir -p "${pkgdir}/usr/lib/prosody/modules/"
> > 	cp -r "${srcdir}/prosody-modules/" \
> >             "${pkgdir}/usr/lib/prosody/modules/" 
> > }  
> There is some issues with that approach. We end up with a
> /usr/lib/prosody/modules/prosody-modules/.hg directory.
> 
> A way to deal with that would be to at least delete that directory
> after the copy.
> 
Seeing as this is the simplest way, this is what I opted to do.
> I'm also not sure if just copying the directories is the best way to do
> proper packages, but given that some of the modules are experimental
> or a proof of concept, if the way it is packaged works, that is probably
> good enough.
The modules are all Lua interpreter files, so copying suffices and upstream
doesn't have a better way for organizing or even versioning them.
It's all one big rolling release, and most modules are very small and simple.

> PS: Note that it is also possible to send patches for review. This way
>     we can reuse your commit message, so if you have interesting things
>     to add there they get included in the commit.
> 
> Denis.

While reviewing things again though, I have come up on an issue which I didn't
consider before: it seems to all be free software, but some of the modules
might cause issues when it comes to privacy.
For example, there is a captcha module that offers the option to use google or
cloudflare captchas (while also providing an option of a local fallback captcha
for those who opt out of using such services).
Does this mean we'll potentially have to patch some modules and maybe even
delete others altogether?

-- 
Kind Regards,
Wael Karram.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-updated-pkgbuild-for-prosody-community-modules.patch
Type: text/x-patch
Size: 1178 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220816/60ea4cf9/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220816/60ea4cf9/attachment.sig>

From wael at waelk.tech  Wed Aug 17 07:09:58 2022
From: wael at waelk.tech (Wael Karram)
Date: Wed, 17 Aug 2022 10:09:58 +0300
Subject: [Dev] [prosody-community-modules] proposed package for prosody's
 modules
In-Reply-To: <20220815192625.1cb2f228@primary_laptop>
References: <20220811102640.071f8fba.wael@waelk.tech>
 <20220815192625.1cb2f228@primary_laptop>
Message-ID: <20220817100958.44340725.wael@waelk.tech>

Hello,
I finally managed to clean it up, these two patches should form the base
package (cleans up nonfree and unmaintained modules).
I will send another patch in for cleaning up any modules that would conflict
with your-privacy/make it impossible to include this package in nonprism.

-- 
Kind Regards,
Wael Karram.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0002-Updated-PKGBUILD-to-exclude-unlicensed-files.patch
Type: text/x-patch
Size: 2878 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/4f6e8aa3/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Updated-PKGBUILD-to-exclude-unlicensed-files.patch
Type: text/x-patch
Size: 3038 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/4f6e8aa3/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/4f6e8aa3/attachment-0001.sig>

From wael at waelk.tech  Wed Aug 17 07:20:48 2022
From: wael at waelk.tech (Wael Karram)
Date: Wed, 17 Aug 2022 10:20:48 +0300
Subject: [Dev] [prosody-community-modules] proposed package for
 prosody's modules
In-Reply-To: <20220817100958.44340725.wael@waelk.tech>
References: <20220811102640.071f8fba.wael@waelk.tech>
 <20220815192625.1cb2f228@primary_laptop>
 <20220817100958.44340725.wael@waelk.tech>
Message-ID: <20220817102048.55efddb9.wael@waelk.tech>

On Wed, 17 Aug 2022 10:09:58 +0300
Wael Karram <wael at waelk.tech> wrote:

> Hello,
> I finally managed to clean it up, these two patches should form the base
> package (cleans up nonfree and unmaintained modules).
> I will send another patch in for cleaning up any modules that would conflict
> with your-privacy/make it impossible to include this package in nonprism.
> 

Hello,
Here is the PKGBUILD for the package that'd go in nonprism.
I've also attached the whole list of modules that I've excluded.

-- 
Kind Regards,
Wael Karram.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Removed-modules-relying-on-nonfree-network-services.patch
Type: text/x-patch
Size: 2020 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/ff8a4e41/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: modules_requiring_special_treatment
Type: application/octet-stream
Size: 1163 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/ff8a4e41/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/ff8a4e41/attachment.sig>

From GNUtoo at cyberdimension.org  Wed Aug 17 13:41:43 2022
From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli)
Date: Wed, 17 Aug 2022 15:41:43 +0200
Subject: [Dev] [prosody-community-modules] proposed package for
 prosody's modules
In-Reply-To: <20220817102048.55efddb9.wael@waelk.tech>
References: <20220811102640.071f8fba.wael@waelk.tech>
 <20220815192625.1cb2f228@primary_laptop>
 <20220817100958.44340725.wael@waelk.tech>
 <20220817102048.55efddb9.wael@waelk.tech>
Message-ID: <20220817154143.219d4ac3@primary_laptop>

On Mon, 15 Aug 2022 19:26:25 +0200
Denis 'GNUtoo' Carikli <GNUtoo at cyberdimension.org> wrote:
> PS: Note that it is also possible to send patches for review. This
> way we can reuse your commit message, so if you have interesting
> things to add there they get included in the commit.
By patches I meant something like sending a single patch to add the
prosody-community-modules PKGBUILD in abslibre. 

If the patch is not pushed (yet) in abslibre and needs modifications,
it's usually easier for maintainers to review a new version of that
patch/PKGBUILD instead of having to review patches on top of the first
PKGBUILD being sent.

On Wed, 17 Aug 2022 10:20:48 +0300
Wael Karram <wael at waelk.tech> wrote:
> Here is the PKGBUILD for the package that'd go in nonprism.
> I've also attached the whole list of modules that I've excluded.
Did you manage to make the PKGBUILD clone a specific mercurial
revision, or did I miss that? 

This is important because otherwise users and people building this
PKGBUILD will expect a specific revision (0.12.1) of the
prosody-community-modules and will instead get the last revision at the
time the package was built.

If the idea is to have the latest revision, this brings several issues.

Aur has packages that use the latest (usually git) revisions, so when
users automatically builds them, they get the latest revision at the
time they build it. 

Parabola doesn't have something like that so we end up having to use a
fixed revision at least for the packages we ship. And some Parabola
contributor(s) really want PKGBUILDS to use known releases.

If your goal is to always have the latest revision, we can try to find
solutions for that, like publishing the PKGBUILD in a separate
repository in abslibre but letting users build it with makepkg.

In that case the PKGBUILD would also need to be modified to communicate
that to users. In pcr/omap-u-boot-utils-git/PKGBUILD, there is an
example that shows how to set pkgver and pkgname for git.

As for the information in modules_requiring_special_treatment, it is
very useful, so it would be sad to loose it. To avoid that it could be
added as-is in the PKGBUILD inside comments.

It also has comments like that inside
> mod_pubsub_feeds: seems to include unlicensed code.

Here if we don't use mksource(), Parabola would end up shipping
binary packages without mod_pubsub_feeds (as you removed it if I recall
well), but it would also ship the mod_pubsub_feeds source code.

So it's probably easier to use mksource() to make sure that Parabola
doesn't accidentally redistribute code that could make Parabola liable.

There are also other options for that but they are more complicated.

Denis.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/a3a225d5/attachment.sig>

From wael at waelk.tech  Wed Aug 17 15:44:13 2022
From: wael at waelk.tech (Wael Karram)
Date: Wed, 17 Aug 2022 18:44:13 +0300
Subject: [Dev] [prosody-community-modules] proposed package for
 prosody's modules
In-Reply-To: <20220817154143.219d4ac3@primary_laptop>
References: <20220811102640.071f8fba.wael@waelk.tech>
 <20220815192625.1cb2f228@primary_laptop>
 <20220817100958.44340725.wael@waelk.tech>
 <20220817102048.55efddb9.wael@waelk.tech>
 <20220817154143.219d4ac3@primary_laptop>
Message-ID: <20220817184413.10ffda7f.wael@waelk.tech>

On Wed, 17 Aug 2022 15:41:43 +0200
Denis 'GNUtoo' Carikli <GNUtoo at cyberdimension.org> wrote:

> On Mon, 15 Aug 2022 19:26:25 +0200
> Denis 'GNUtoo' Carikli <GNUtoo at cyberdimension.org> wrote:
> > PS: Note that it is also possible to send patches for review. This
> > way we can reuse your commit message, so if you have interesting
> > things to add there they get included in the commit.  
> By patches I meant something like sending a single patch to add the
> prosody-community-modules PKGBUILD in abslibre. 
> 
> If the patch is not pushed (yet) in abslibre and needs modifications,
> it's usually easier for maintainers to review a new version of that
> patch/PKGBUILD instead of having to review patches on top of the first
> PKGBUILD being sent.

I see, then I'll just send in the two different PKGBUILDs for now, once I fix
the issues in both.
> On Wed, 17 Aug 2022 10:20:48 +0300
> Wael Karram <wael at waelk.tech> wrote:
> > Here is the PKGBUILD for the package that'd go in nonprism.
> > I've also attached the whole list of modules that I've excluded.  
> Did you manage to make the PKGBUILD clone a specific mercurial
> revision, or did I miss that? 
> 
> This is important because otherwise users and people building this
> PKGBUILD will expect a specific revision (0.12.1) of the
> prosody-community-modules and will instead get the last revision at the
> time the package was built.
> 
> If the idea is to have the latest revision, this brings several issues.
> 
> Aur has packages that use the latest (usually git) revisions, so when
> users automatically builds them, they get the latest revision at the
> time they build it. 
> 
> Parabola doesn't have something like that so we end up having to use a
> fixed revision at least for the packages we ship. And some Parabola
> contributor(s) really want PKGBUILDS to use known releases.
> 
> If your goal is to always have the latest revision, we can try to find
> solutions for that, like publishing the PKGBUILD in a separate
> repository in abslibre but letting users build it with makepkg.
> 
> In that case the PKGBUILD would also need to be modified to communicate
> that to users. In pcr/omap-u-boot-utils-git/PKGBUILD, there is an
> example that shows how to set pkgver and pkgname for git.
I guess I'll have to figure out the equivalent for mercurial, I think Arch Wiki
had something about it.
> As for the information in modules_requiring_special_treatment, it is
> very useful, so it would be sad to loose it. To avoid that it could be
> added as-is in the PKGBUILD inside comments.
> 
> It also has comments like that inside
> > mod_pubsub_feeds: seems to include unlicensed code.  
> 
> Here if we don't use mksource(), Parabola would end up shipping
> binary packages without mod_pubsub_feeds (as you removed it if I recall
> well), but it would also ship the mod_pubsub_feeds source code.
> 
> So it's probably easier to use mksource() to make sure that Parabola
> doesn't accidentally redistribute code that could make Parabola liable.
> 
> There are also other options for that but they are more complicated.
> 
I've tried the mksource approach now, we'll see if it is enough.
I've attached the PKGBUILD to the email, this is the stricter version that
removes all modules interacting with non-free code of any form (mostly "cloud"
stuff).
> Denis.



-- 
Kind Regards,
Wael Karram.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PKGBUILD
Type: application/octet-stream
Size: 1727 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/0de42e7c/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220817/0de42e7c/attachment.sig>

From GNUtoo at cyberdimension.org  Fri Aug 19 11:54:56 2022
From: GNUtoo at cyberdimension.org (Denis 'GNUtoo' Carikli)
Date: Fri, 19 Aug 2022 13:54:56 +0200
Subject: [Dev] [prosody-community-modules] proposed package for
 prosody's modules
In-Reply-To: <20220817184413.10ffda7f.wael@waelk.tech>
References: <20220811102640.071f8fba.wael@waelk.tech>
 <20220815192625.1cb2f228@primary_laptop>
 <20220817100958.44340725.wael@waelk.tech>
 <20220817102048.55efddb9.wael@waelk.tech>
 <20220817154143.219d4ac3@primary_laptop>
 <20220817184413.10ffda7f.wael@waelk.tech>
Message-ID: <20220819135456.3724cee4@primary_laptop>

On Wed, 17 Aug 2022 18:44:13 +0300
Wael Karram <wael at waelk.tech> wrote:
> I guess I'll have to figure out the equivalent for mercurial, I think
> Arch Wiki had something about it.

I've found an example in the Parabola wiki in the
Package_maintainer_guide page:
> source=("https://repo.parabola.nu/other/~lukeshu/wmii/wmii-hg-${pkgver}.tar.gz")
> md5sums=('1ab85d01467e5e53c9b16ca19cca9824')
> 
> mkdepends=("mercurial")
> mksource=("wmii-hg${pkgver}::hg+https://code.google.com/p/wmii/#revision=${pkgver}")
> mkmd5sums=('SKIP')
> mksource() {
> 	# don't include this precompiled binary (probably included by
>       # accident) 
>       rm "${srcdir}/wmii-hg${pkgver}/lib/libutf/libutf.a"
> }

I've not tested it though and I'm currently offline (I downloaded the
wiki with git and Mediawiki remote).

Denis.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220819/09017978/attachment.sig>

From wael at waelk.tech  Sat Aug 20 18:19:15 2022
From: wael at waelk.tech (Wael Karram)
Date: Sat, 20 Aug 2022 21:19:15 +0300
Subject: [Dev] [prosody-community-modules] proposed package for
 prosody's modules
In-Reply-To: <20220819135456.3724cee4@primary_laptop>
References: <20220811102640.071f8fba.wael@waelk.tech>
 <20220815192625.1cb2f228@primary_laptop>
 <20220817100958.44340725.wael@waelk.tech>
 <20220817102048.55efddb9.wael@waelk.tech>
 <20220817154143.219d4ac3@primary_laptop>
 <20220817184413.10ffda7f.wael@waelk.tech>
 <20220819135456.3724cee4@primary_laptop>
Message-ID: <20220820205032.4e4f2483.wael@waelk.tech>

On Fri, 19 Aug 2022 13:54:56 +0200
Denis 'GNUtoo' Carikli <GNUtoo at cyberdimension.org> wrote:

> On Wed, 17 Aug 2022 18:44:13 +0300
> Wael Karram <wael at waelk.tech> wrote:
> > I guess I'll have to figure out the equivalent for mercurial, I
> > think Arch Wiki had something about it.  
> 
> I've found an example in the Parabola wiki in the
> Package_maintainer_guide page:
> > source=("https://repo.parabola.nu/other/~lukeshu/wmii/wmii-hg-${pkgver}.tar.gz")
> > md5sums=('1ab85d01467e5e53c9b16ca19cca9824')
> > 
> > mkdepends=("mercurial")
> > mksource=("wmii-hg${pkgver}::hg+https://code.google.com/p/wmii/#revision=${pkgver}")
> > mkmd5sums=('SKIP')
> > mksource() {
> > 	# don't include this precompiled binary (probably included
> > by # accident) 
> >       rm "${srcdir}/wmii-hg${pkgver}/lib/libutf/libutf.a"
> > }  
> 
> I've not tested it though and I'm currently offline (I downloaded the
> wiki with git and Mediawiki remote).
> 
> Denis.

Thanks a lot for the help! I think have finally managed to get it right.
I've attached the final PKGBUILD to this email.
Note that I couldn't properly test it, as for some reason running
libremakepkg with all mksource packages fails here on downloading the
libre source.

-- 
Kind Regards,
Wael Karram.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PKGBUILD
Type: application/octet-stream
Size: 1796 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220820/82e5dacc/attachment-0001.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220820/82e5dacc/attachment-0001.sig>

From avalos at disroot.org  Sun Aug 21 03:18:07 2022
From: avalos at disroot.org (=?UTF-8?B?SXbDoW4gw4F2YWxvcw==?=)
Date: Sat, 20 Aug 2022 22:18:07 -0500
Subject: [Dev] Request: update pcr/gtg to version 0.6
Message-ID: <20220820221807.52a483ac@thinkpad.localdomain>

Getting Things GNOME is on the PCR, but it is version 0.3, which is
very old and still depends on python2. The latest version is 0.6. I
found a PKGBUILD in the AUR for that version, which I'm attaching to
this e-mail.

-- 
Iv?n ?valos
XMPP: ivan at avalos.me
Website: https://avalos.me/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PKGBUILD
Type: application/octet-stream
Size: 1191 bytes
Desc: not available
URL: <https://lists.parabola.nu/pipermail/dev/attachments/20220820/4670f8fc/attachment.obj>

From nobody at parabola.nu  Thu Aug 25 00:47:06 2022
From: nobody at parabola.nu (Parabola Website Notification)
Date: Thu, 25 Aug 2022 00:47:06 -0000
Subject: [Dev] Orphan Libre package [iceweasel] marked out-of-date
Message-ID: <20220825004706.3710384.80453@winston.parabola.nu>

eliotreyna at disroot.org wants to notify you that the following packages may be out-of-date:


* iceweasel 1:103.0-1.parabola1 [libre] (i686): https://parabolagnulinux.org/packages/libre/i686/iceweasel/
* iceweasel 1:103.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 104.

The following changes are:

-Optimization for battery-operated computers like laptops and tablet PC's via UI Throttling.
-Support of "scroll-snap-stop" and "re-snapping" properties.

For more detailed information, please follow the link below:

https://www.mozilla.org/en-US/firefox/104.0/releasenotes/

Thanks.


From pagure at pagure.io  Thu Aug 25 19:56:49 2022
From: pagure at pagure.io (=?utf-8?q?bill-auger?=)
Date: Thu, 25 Aug 2022 19:56:49 +0000 (GMT)
Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2362=3A_libre/iceweasel=3A_10?=
 =?utf-8?q?3=2E0-1=2Eparabola1?=
In-Reply-To: <abslibre-pull-request-98457f68856141af93eb87d34698e5ef@pagure.io>
Message-ID: <abslibre-pull-request-98457f68856141af93eb87d34698e5ef/close/1661457409.0@pagure.io>


billauger closed without merging a pull-request against the project: `abslibre` that you
are following.

Closed pull-request:

``
libre/iceweasel: 103.0-1.parabola1
``

https://pagure.io/abslibre/pull-request/62

From pagure at pagure.io  Thu Aug 25 19:56:41 2022
From: pagure at pagure.io (=?utf-8?q?bill-auger?=)
Date: Thu, 25 Aug 2022 19:56:41 +0000 (GMT)
Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2362=3A_libre/iceweasel=3A_10?=
 =?utf-8?q?3=2E0-1=2Eparabola1?=
In-Reply-To: <abslibre-pull-request-98457f68856141af93eb87d34698e5ef@pagure.io>
Message-ID: <abslibre-pull-request-98457f68856141af93eb87d34698e5ef-176368@pagure.io>


billauger commented on the pull-request: `libre/iceweasel: 103.0-1.parabola1` that you are following:
``
merged
``

To reply, visit the link below or just reply to this email
https://pagure.io/abslibre/pull-request/62

From pagure at pagure.io  Sun Aug 28 20:01:04 2022
From: pagure at pagure.io (=?utf-8?q?Grizzly_User?=)
Date: Sun, 28 Aug 2022 20:01:04 +0000 (GMT)
Subject: [Dev] =?utf-8?q?=5Babslibre=5D_PR_=2363=3A_libre/iceweasel=3A_10?=
 =?utf-8?q?4=2E0-1=2Eparabola1?=
Message-ID: <abslibre-pull-request-38b1bdb2419a424fb4430b96637a089e@pagure.io>


grizzlyuser opened a new pull-request against the project: `abslibre` that you are following:
``
libre/iceweasel: 104.0-1.parabola1
``

To reply, visit the link below or just reply to this email
https://pagure.io/abslibre/pull-request/63

From bill-auger at peers.community  Mon Aug 29 20:29:57 2022
From: bill-auger at peers.community (bill-auger)
Date: Mon, 29 Aug 2022 16:29:57 -0400
Subject: [Dev] [abslibre] PR #63: libre/iceweasel: 104.0-1.parabola1
In-Reply-To: <abslibre-pull-request-38b1bdb2419a424fb4430b96637a089e@pagure.io>
References: <abslibre-pull-request-38b1bdb2419a424fb4430b96637a089e@pagure.io>
Message-ID: <20220829162957.485945ed@parabola.localdomain>

looks like the profiling build is requiring network access again

i let it run for an entire day and it never completed
trying again with skip_pgo now

 |  Running "pip check" to verify compatibility between the system Python and the "mach" site.
 |  created virtual environment CPython3.10.6.final.0-64 in 28ms
 |    creator CPython3Posix(dest=/build/iceweasel/src/firefox-104.0/obj/_virtualenvs/common, clear=False, no_vcs_ignore=False, global=False)
 |    activators BashActivator,CShellActivator,FishActivator,PowerShellActivator,PythonActivator
 |  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=1.00744) [GFX1-]: glxtest: libpci missing
 |  ATTENTION: default value of option mesa_glthread overridden by environment.
 |  console.warn: SearchSettings: "get: No settings file exists, new profile?" (new NotFoundError("Could not open the file at /tmp/tmp53x05rfz/search.json.mozlz4", (void 0)))
 |  Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
 |  Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
 |  console.error: "Error during quit-application-granted: [Exception... \"File error: Not found\"  nsresult: \"0x80520012 (NS_ERROR_FILE_NOT_FOUND)\"  location: \"JS frame :: resource:///modules/BrowserGlue.jsm :: _onQuitApplicationGranted/tasks< :: line 2013\"  data: no]"
 |  Waiting in WillDestroyCurrentMessageLoop for pid 4065159
 |  Waiting in WillDestroyCurrentMessageLoop for pid 4065175
 |  Waiting in WillDestroyCurrentMessageLoop for pid 4065245
 |  Waiting in WillDestroyCurrentMessageLoop for pid 4065247
 |  Waiting in WillDestroyCurrentMessageLoop for pid 4065263
 |  Waiting in WillDestroyCurrentMessageLoop for pid 4065102
 |  Crash Annotation GraphicsCriticalError: |[0][GFX1-]: glxtest: libpci missing (t=0.477505) [GFX1-]: glxtest: libpci missing
 |  ATTENTION: default value of option mesa_glthread overridden by environment.
 |  console.error: SessionStore: "The session file is invalid: TypeError: state is null"
 |  Missing chrome or resource URL: resource://gre/modules/UpdateListener.sys.mjs
 |  JavaScript error: resource://gre/modules/XULStore.jsm, line 62: Error: Can't find profile directory.
 |  1661725932563       addons.xpi      ERROR   System addon update list error Error: Failed downloading XML, status: 0, reason: error

From dev at lists.parabola.nu  Tue Aug 30 21:22:40 2022
From: dev at lists.parabola.nu (Parabola GNU/Linux-libre: Recent news updates: bill auger)
Date: Tue, 30 Aug 2022 21:22:40 -0000
Subject: [Dev] [dev] Grub bootloader upgrade and configuration
 incompatibilities
Message-ID: <20220830212240.3710385.48486@winston.parabola.nu>

2022-08-30 - Christian Hesse

Recent changes in grub added a new command option to fwsetup and changed the way the command is invoked in the generated boot configuration. Depending on your system hardware and setup this could cause an unbootable system due to incompatibilities between the installed bootloader and configuration. After a grub package update it is advised to run both, installation and regeneration of configuration:

    grub-install ...
    grub-mkconfig -o /boot/grub/grub.cfg


URL: /news/grub-bootloader-upgrade-and-configuration-incompatibilities/