October 2021 - PureOS-project - Purism Mailing Lists

Re: [PureOS] Updating localechooser in landing/byzantium
by Jonas Smedegaard 16 Oct '21

16 Oct '21

Quoting Guido Günther (2021-10-09 17:11:27) > Hi, > On Sat, Oct 09, 2021 at 10:25:20AM +0200, Carsten Schoenert wrote: > [..snip..] > > > https://source.puri.sm/pureos/packages/lollypop contains no local > > > feature commits (i.e. no feature changes, only boilerplate changes > > > to packaging metadata) so does not illustrate well how to best > > > tackle package upgrades. What it does illustrate is that it > > > didn't preserve earlier PureOS work - i.e. the work tracked at > > > https://source.puri.sm/librem5-apps/lollypop > > > > That is unfortunately correct. :( > > I wasn't aware that there was already a lollypop tree until now. > > Then we need to think about how get that split fixed. > > I wasn't aware of > > https://source.puri.sm/librem5-apps/lollypop > > when importing, sorry. > > We can preserve that history in the pureos/packages/lollypop repo need > be or just leave it as is and use that fork in unlikely case we need > updates for amber-phone. Both works for me. That particular work of mine is not important for me that we preserve. If topic of this conversation is _simplest_ practice then let's just throw away historic git repos. I pointed to that historic git repo because a) it was unclear to me what Carsten wanted to say (he also referenced missing posts by Guido still unavailable to me¹), and b) I mistakenly focused on finding _best_ practice. - Jonas ¹ Seems many posts from Guido has reached only cc'ed participants in discussions, not this list. As a concrete example, this email is a response to an email from Guido with Message-ID <YWGxH0nt5AnmfYO9(a)qwark.sigxcpu.org> which I received but does not appear at https://lists.puri.sm/pipermail/pureos-project/2021-October/thread.html -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private

2 3

Dropping derived cron package?
by Carsten Schoenert 16 Oct '21

16 Oct '21

Hi, back in 2018 Matthias did a small modification within the cron package that resulted in forked tree and small different binary package for cron. Basically the only difference is this patch: > $ git show c2766e7259b86b32bcecd2d61607eb022fd31310 > commit c2766e7259b86b32bcecd2d61607eb022fd31310 > Author: Matthias Klumpp <matthias(a)tenstral.net> > Date: Sun Aug 19 20:50:32 2018 +0200 > > Only suggest, not recommend, an MTA > > diff --git a/debian/control b/debian/control > index 1bd9c3e..e6a6766 100644 > --- a/debian/control > +++ b/debian/control > @@ -25,12 +25,11 @@ Depends: > adduser, > lsb-base (>= 3.0-10), > libpam-runtime (>= 1.0.1-11) > -Recommends: > - exim4 | postfix | mail-transport-agent > Suggests: > anacron (>=2.0-1), > logrotate, > - checksecurity > + checksecurity, > + exim4 | postfix | mail-transport-agent > Breaks: > dpkg (<< 1.15.4) > Provides: cron-daemon In between times the packaging in Debian has been changed on this part. > $ git show f27b9ccdb2046fe3fbb1eef6d7801d4b3d6900c7 > commit f27b9ccdb2046fe3fbb1eef6d7801d4b3d6900c7 > Author: Christian Kastner <ckk(a)debian.org> > Date: Tue Feb 19 21:46:16 2019 +0100 > > Switch cron MTA Recommends to default-mta | mail-transport-agent > > Recommend these virtual packages rather than specific MTAs. > > diff --git a/debian/control b/debian/control > index fc59f49..609e84f 100644 > --- a/debian/control > +++ b/debian/control > @@ -25,7 +25,7 @@ Depends: > lsb-base (>= 3.0-10), > libpam-runtime (>= 1.0.1-11) > Recommends: > - exim4 | postfix | mail-transport-agent > + default-mta | mail-transport-agent > Suggests: > anacron (>= 2.0-1), > logrotate, Is this change worth to update the current cron package in byzantium or could the derived package instead get dropped? (It's not completely clear to me why the mta part was moved to Suggests.) -- Regards Carsten Schoenert

3 4

Re: [PureOS] Updating localechooser in landing/byzantium
by Jonas Smedegaard 11 Oct '21

11 Oct '21

Quoting Guido Günther (2021-10-09 18:06:35) > On Sat, Oct 09, 2021 at 05:50:00PM +0200, Jonas Smedegaard wrote: > [..snip..] > > ¹ Seems many posts from Guido has reached only cc'ed participants in > > discussions, not this list. As a concrete example, this email is a > > response to an email from Guido with Message-ID > > <YWGxH0nt5AnmfYO9(a)qwark.sigxcpu.org> which I received but does not > > appear at > > https://lists.puri.sm/pipermail/pureos-project/2021-October/thread.html > > Thanks for making me aware: > > I checked all the mails had the right "From:" so I can't tell why > those gone missing. The mail servers I have access to show no signs of > error an logged those mails as being accepted by > lists.puri.sm[138.201.228.37]:25 Thanks for those details. Now the list has them as well :-/ - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private

2 2

Re: [PureOS] Updating localechooser in landing/byzantium
by Guido Günther 09 Oct '21

09 Oct '21

Hi, On Sat, Oct 09, 2021 at 06:06:36PM +0200, Guido Günther wrote: > On Sat, Oct 09, 2021 at 05:50:00PM +0200, Jonas Smedegaard wrote: > [..snip..] > > ¹ Seems many posts from Guido has reached only cc'ed participants in > > discussions, not this list. As a concrete example, this email is a > > response to an email from Guido with Message-ID > > <YWGxH0nt5AnmfYO9(a)qwark.sigxcpu.org> which I received but does not > > appear at > > https://lists.puri.sm/pipermail/pureos-project/2021-October/thread.html > > Thanks for making me aware: > > I checked all the mails had the right "From:" so I can't tell why > those gone missing. The mail servers I have access to show no signs of > error an logged those mails as being accepted by > lists.puri.sm[138.201.228.37]:25 ahh...wait. Does this one reach you? I think I mixed tings up again because I'm subscribed with another mail address. I'll fix that. Cheers, -- Guido > > Cheers, > -- Guido > > > > > -- > > * Jonas Smedegaard - idealist & Internet-arkitekt > > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > > > [x] quote me freely [ ] ask before reusing [ ] keep private > > > > > _______________________________________________ > > PureOS-project mailing list > > PureOS-project(a)lists.puri.sm > > https://lists.puri.sm/listinfo/pureos-project >

2 1

Updating localechooser in landing/byzantium
by Carsten Schoenert 09 Oct '21

09 Oct '21

Hi, I've looked at localechooser as it's mentioned currently in the synchronization issues for landing. https://master.pureos.net/sync/landing Last time the package was touched was in 2018 by Matthias and shortly later by Chris [1]. As Matthias choose to start with a standalone branch back in 2018 I now merged the Debian tag 2.93 from the upstream repository on Salsa into a derived branch pureos/latest based on the standalone branch named master within the Purism tree. That's how I see future work will be manageable, merging the required Debian tag into the derived PureOS tree as done in other forked repos. I managed to get the merge conflicts solved so far. I also added a configuration for gbp and also a CI controlling file. So why I'm posting here? Simply because there is no target branch on the destination tree I can create a MR for and also because I'm currently not know much about the background for this forked package. So please have a look at the current state I prepared [2] for further discussion. The CI pipeline succeeded so far. But as for python-apt, other things might be needed to check before pushing my work to the main repo. [1] https://source.puri.sm/pureos/core/localechooser [2] https://source.puri.sm/carsten.schoenert/localechooser/-/commits/pureos/lat… -- Regards Carsten Schoenert

2 5

Re: [PureOS] Updating localechooser in landing/byzantium
by Jeremiah C. Foster 08 Oct '21

08 Oct '21

On 10/8/21 3:11 AM, Guido Günther wrote: > Hi, > On Thu, Oct 07, 2021 at 02:58:54PM -0400, Jeremiah C. Foster wrote: >>> We can forward all of gitlab traffic to from the PureOS space to this >>> (or another) list or better explain how to subscribe to all changes there. >> >> So you'd rather de-commission or deprecate this list? Isn't following even >> just the PureOS space via a RSS type feed a _lot_ of mail? I'll import it >> into my inbox to see how much myself. I can see a benefit of having fewer >> communication streams. > > Not at all. I'd keep the list for sure as a discussion point. My point > was just that you can also have email for gitlab discussions forwarded > to a list. The /pureos space currently doesn't generate much mail but > I'd rather keep `-project` as low volume and have all changes forwarded > to another list. Okay, sounds good. Do we then leave the status quo and ask those who wish to follow everything packaging related to PureOS via the Gitlab feed[0] (which is down at the moment) or should we redirect the PureOS activity to the pureos-changes[1] mailing list? I'd prefer just keeping the status quo. Cheers, Jeremiah 0. https://source.puri.sm/pureos.atom?feed_token=FyqHac77BYBaZh9ZAXtM 1. https://lists.puri.sm/listinfo/pureos-changes

1 0

Re: [PureOS] Updating localechooser in landing/byzantium
by Carsten Schoenert 08 Oct '21

08 Oct '21

Guido, Am 06.10.21 um 16:38 schrieb Guido Günther: >> I've currently decided against this option because to keep the existing old >> history within the same tree as base for the current new added branch. > > …but that wouldn't change since the current history is on `master` and > you'd merge that plus your changes / the update into `pureos/latest`, > right? no, my current way of doing nor your point would break or drop history, how you are seeing it, or your pov of doing is just another way to get the same goal. The merge of the old master branch is just into another direction than I've done it currently. > Am i missing something? Your merge of the old 'master' wouldn't > get broken as long as the merge of the MR to `pureos/latest` is > fast-forward. Sure, to get things merge-able by a MR the repo on core-packages would need an existing branch pureos/latest. That isn't existing right now. I've tried the readjust the way you would make update for the fork. 1. Create new branch pureos/latest based on Debian tag 2.93 2. Merge in the (old pureos) master branch 3. Add additional stuff as gbp.conf and CI yaml file The outcome and the required work is the same to my current kind of doing, most of the work is to solve the merge conflicts as this is exact same todo on both ways. But maybe I'm the one that is missing something. ;) > Again I have no strong opinion here but rather try to understand why one > would use a different workflow as with other packages (which > e.g. results in the discussion being split between mailing list and > giltab). Well, the thing is still, there is no branch I can start a MR against (at least I think). There is not even yet a tag 2.93 on soure.p.s., there is currently only the old master branch which isn't connected anyhow to the "mother" tree on Salsa. If it would exist at all this mail traffic wouldn't needed and I've started directly any discussion within a MR. If the outcome is there is no problem to create a starting branch pureos/latest by preparing the tree on source.p.s then I'm of course fine with this. I'm unsure if I would can do that, given to the permissions for Developers I should. > My take for using merge requests for about everything is that it keeps > the discussion close to the code (and searchable). I fully understand this. But I'm quite conservative about possible direct action on "hot" repositories as I'm still new and like to prevent any damages. -- Regards Carsten Schoenert

3 7

Re: [PureOS] Updating localechooser in landing/byzantium
by Jeremiah C. Foster 07 Oct '21

07 Oct '21

Hello again! On 10/7/21 3:51 AM, Guido Günther wrote: > Hi Jeremiah, > On Wed, Oct 06, 2021 at 04:22:55PM -0400, Jeremiah C. Foster wrote: >> Hello, >> >> On 10/6/21 12:29 PM, Carsten Schoenert wrote: >>> Guido, >>> >>> Am 06.10.21 um 16:38 schrieb Guido Günther: >> <snip> >>>> Again I have no strong opinion here but rather try to understand why one >>>> would use a different workflow as with other packages (which >>>> e.g. results in the discussion being split between mailing list and >>>> giltab). >>> Well, the thing is still, there is no branch I can start a MR against >>> (at least I think). There is not even yet a tag 2.93 on soure.p.s., >>> there is currently only the old master branch which isn't connected >>> anyhow to the "mother" tree on Salsa. >> This is an issue with all packages on source.puri.sm - both pureos/core and >> pureos/packages are not connected to Salsa or to Laniakea. > By far not all. /Librem5/debs space uses full sources mirrored from > salsa so do many projects I've encountered in the PureOS /core and > /packages spaces. Just one exmple from each: > > https://source.puri.sm/pureos/core/dpkg/-/commits/pureos/master > https://source.puri.sm/pureos/packages/gnome-control-center > > There's many more and new ones also use this pattern to my > knowledge. That is fantastic! In my experience that was not the case but looking at the package lists of core and packages now I can see that there are many updated as you say. Other's say "fork from Debian" and some are years old or month old but they may have newer branches, etc. If we could use those two package repos going forward, we might be able to determine a minimum set of PureOS forked or modified packages that we can evaluate for support over the longer term if we chose to support Amber longer than it's current security service going forward. We have more "PureOS only" stuff in Byzantium I assume so the sooner we can define that minimum set of things we need to support (and for how long) the better we can allocate resources that work. >> These repo groupings (core and packages) likely no longer serve the same >> purpose as originally - namely to be "complete and corresponding" source >> code for all the packages in PureOS. We likely ought to have a plan or >> create one for how we can have a one-to-one correspondence between source >> code in a git repo and the binaries in the archives to make support easier. >> >>> If it would exist at all this mail traffic wouldn't needed and I've >>> started directly any discussion within a MR. >>> >>> If the outcome is there is no problem to create a starting branch >>> pureos/latest by preparing the tree on source.p.s then I'm of course >>> fine with this. >>> I'm unsure if I would can do that, given to the permissions for >>> Developers I should. >>> >>>> My take for using merge requests for about everything is that it keeps >>>> the discussion close to the code (and searchable). >> This makes sense but this list can be a very valuable resource for those new >> to PureOS, for making policy, and for other co-ordination. So I for one >> welcome Carsten's mail to the list. > We can forward all of gitlab traffic to from the PureOS space to this > (or another) list or better explain how to subscribe to all changes there. So you'd rather de-commission or deprecate this list? Isn't following even just the PureOS space via a RSS type feed a _lot_ of mail? I'll import it into my inbox to see how much myself. I can see a benefit of having fewer communication streams. Regards, Jeremiah

1 0

Re: [PureOS] Updating localechooser in landing/byzantium
by Carsten Schoenert 06 Oct '21

06 Oct '21

Hello Guido, Am 06.10.21 um 14:44 schrieb Guido Günther: >> So why I'm posting here? >> Simply because there is no target branch on the destination tree I can > > Wouldn't a branch `pureos/latest` at the same commit as Debian's 2.93 be > the target branch to create an MR against? Similar to what happened for > seahorse and lollypop? Why wouldn't that work? of course that would work too. > It's a small diff and i don't want to complicate things, just trying to > figure out where default workflows break. I've currently decided against this option because to keep the existing old history within the same tree as base for the current new added branch. I think currently it makes no difference if we would stay on the current created pureos/latest branch. If you all think it would make more sense to branch away pureos/latest starting from the relevant tag 2.93 I'll can rework the trees. That's why I've posted here, to get a common opinion on how to proceed. -- Regards Carsten Schoenert

2 1

Byzantium plasma builds
by Jeremiah C. Foster 05 Oct '21

05 Oct '21

Hiya, Do we plan to support KDE Plasma builds for Byzantium? I don't see it here; https://downloads.puri.sm/byzantium/ I don't know how much usage they get or how much work it is to support them so I'm open to dropping if it makes sense. Regards, Jeremiah

2 2

2024

2023

2022

2021

2020

2019

2018

PureOS-project October 2021