 Done, I think. (re @tsimonq2: RikMills, sgmoore, arraybolt3: Yo, could someone follow up to get Ubiquity off the Kubuntu ISO? We're currently shipping two installers. :P)
 I not lubuntu seeds some extra things in live for luks encryption etc? Do we need those?
 /me has not dug that deep into calamares
 Thanks! (re @RikMills: Done, I think.)
 I think it's about time we have a common Calamares seed... :P (re @RikMills: I not lubuntu seeds some extra things in live for luks encryption etc? Do we need those?)
 That sounds a good plan
[11:31] <santa_> good morning everybody
[11:31] <santa_> I will have to comment some things
[11:33] <santa_> sgmoore: look, these days I have been trying to do test rebuilds, like I usually do. what I have been finding is way more messed up than normal
[11:34] <santa_> yesterday, for example I have been trying to fix the mess of plasma-pa and konqueror git repositories
[11:35] <santa_> also, I found out that there's a number of plasma packages that have things in its archive branches that simply do not match what is in the archive
[11:35] <santa_> example:
[11:35] <santa_> kdecoration in the archive: https://launchpad.net/ubuntu/+source/kdecoration
[11:36] <santa_> kdecoration in git: https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kdecoration?h=kubuntu_noble_archive
[11:37] <santa_> we have an ubuntu2 version there (also with tag) that was never uploaded to the archive
[11:37] <santa_> why? what happenned there?
[11:38] <santa_> this also not an isolated case; wqe have the same thing with gamma5:
[11:39] <santa_> https://launchpad.net/ubuntu/+source/kgamma5
[11:39] <santa_> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kgamma5?h=kubuntu_noble_archive
[11:40] <santa_> same with kwallet-pam:
[11:41] <santa_> https://launchpad.net/ubuntu/+source/kwallet-pam
[11:41] <santa_> https://git.launchpad.net/~kubuntu-packagers/kubuntu-packaging/+git/kwallet-pam?h=kubuntu_noble_archive
[11:48] <sgmoore> dunno, too much work, not enough sleep? I know I had to trigger some rebuilds due to the autopackage test container failures, it looks like I missed some uploads.. clearly. I will sort out a better system to ensure that doesn't happen again. Apologies.
[11:50] <santa_> sgmoore: alright, I'm going to be syncing some git repos (no-change rebuilds by other people, that's normal), and I will leave the ones mentioned above for later
[11:51] <santa_> so we can discuss the best way to proceed
[11:53] <sgmoore> I am fixing them now.
[11:58] <santa_> fixing them how?
 Make a list, santa_, we'll walk through them and fix them one by one.
[12:01] <sgmoore> I am not an idiot. I know how to fix my commits to match archive. Thanks.
[12:04] <santa_> well I was going to suggest:
[12:04] <santa_> - delete the tag
[12:05] <santa_> - push a "sync with archive" commit (maybe better that revert in this case?)
[12:05] <sgmoore> yep I am doing that as well
[12:06] <sgmoore> I did a revert and a new entry for new release, but I suppose timestamps won't match, so taking your suggestion with sync with achive. thank you.
[12:35] <sgmoore> santa_: the three you mentioned have been fixed. Please let me know if you encounter any more. thanks.
[12:36] <sgmoore> santa_: could you please elaborate on "the mess of plasma-pa and konqourer repositories" thanks.
[12:45] <santa_> sgmoore: yes, regarding konqueror, the _archive branch wasn't merged into _staging; instead there was (and there is) a duplicate commit "Add apparmor profile to fix userns. Ref: LP:2046844"
[12:45] -ubottu:#kubuntu-devel- Launchpad bug 2046844 in qutebrowser (Ubuntu) "AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP" [High, Confirmed] https://launchpad.net/bugs/2046844
[12:46] <santa_> so they were some changes in the _archive branch that were not in the _staging branch, meaning if someone started something from the _staging branch, some of your other changes would be accidentaly dropped
[12:46] <santa_> so I merged _archive into _staging
[12:47] <santa_> I hope that's ok, if it's not, let me know
[12:48] <sgmoore> santa_: ok, that was one of my first changes. I was still learning the way of things. It is fine, thanks for catching and fixing.
[12:49] <sgmoore> So I see now my workflow is mising the merge into staging any fix I push to archive... noted and it will not be an issue further.
[12:50] <santa_> yeah, well also I was going to mention a couple of things regarding this:
[12:51] <santa_> - our documentation doesn't explain the _archive and _staging branches workflow which is something to be fixed
[12:52] <santa_> - I have been merging the _archive branches into _staging for frameworks in order to prevent a situation where someone starts a new release of fw on top of the wrong commit
[12:56] <santa_> regarding plasma-pa, I have the impression it's ok now, maybe I confused it with other package
[12:57] <santa_> on my front: I have included the latest no-change rebuilds made by other people for: discover, flatpak-kcm, kde-gtk-config, plasma-desktop, plasma-nm
[12:58] <sgmoore> ok, let me know if you come across any more issues. I am currently doing a do-all git pull. Is there an easy way to track these changes made by 'other people' ?
[12:58] <santa_> yes
[12:58] <santa_> do-all check-archive
[12:58] <santa_> BUT:
[12:59]  * sgmoore adds to notes
[12:59] <santa_> keep in mind this program checks if the version in the archive is HIGHER that what you have in the local git clone
[12:59] <sgmoore> and not lower. ok 
[13:00] <santa_> that is effective to detect situations like what I have been just syncing: discover, flatpak-kcm, kde-gtk-config, plasma-desktop, plasma-nm
[13:01] <santa_> but it's not effective to detect situations like kdecoration, where the thing in git is higher than archive
[13:01] <sgmoore> ok, how did you find the latter?
[13:02] <santa_> for this I'm considering to add an "--strict" parameter to check archive to check if the version is exactly the same, what do you think?
[13:03] <sgmoore> Sounds very useful. +1
[13:03] <santa_> "ok, how did you find the latter?" by visually inspecting the output of check-archive, it tells you the local and archive version and I found out by coincidence the weird thing
[13:04] <santa_> example:
[13:04] <santa_> santa@watertown:~/archive/plasma/kdecoration$ check-archive
[13:04] <santa_> Latest local released version: 4:5.27.10-1ubuntu2
[13:04] <santa_> Latest archive version:        4:5.27.10-1ubuntu1
[13:04] <santa_> Archive version is not higher than local version
[13:04] <santa_> y
[13:04] <sgmoore> ok, good to know. THough I intend on fixing the issue that causedit in the first place.
[13:07] <sgmoore> santa_: also, is there plans on 'implementing' cases where the version has a suffix eg: +ds , it causes gbp-* to trip up and fail and one must manually build.
[13:08] <santa_> sgmoore: yes, that's something I have on my radar, I know you have that problem with ghostwriter ;)
[13:08] <sgmoore> great :)
[13:09] <sgmoore> otherwise the tools are fantastic, thanks so much for all the work there.
[13:09] <santa_> some code is alredy done, but I need to allocate some time to do the most important part: retrieving the tarball
[13:10] <santa_> at this point it just throws an exception, that's because I had to do some changes to prepare for that (i.e. detecting the suffix and the files to be excluded among other things if I remember well)
[13:11] <santa_> also I have on my radar resurrecting the merge script, which I think it didn't work for you, right?
[13:12] <sgmoore> correct
[13:12] <sgmoore> I ended up doing it the MOM way.
[13:15] <santa_> asnother thing regarding packaging and git status: plasma-welcome
[13:16] <santa_> s/asnother/another/
[13:16] <santa_> at the moment we have in git this kubuntu_skip-online-accounts-page.patch in the _archive branch
[13:16] <santa_> this branch wasn't merged into _staging
[13:17] <santa_> sgmoore, RikMills this needs to be merged right? I mean we want this change also in plasma 5.27.11 when uploaded to the archive, right?
[13:18] <sgmoore> yes please
[13:18] <santa_> alright, I'm going to merge and rebuild in the staging ppa if nobody complains
[13:20] <sgmoore> Go ahead. hopefully arm builds aren't still grumpy. also kpipewire is stuck on some deps out of our control
[13:21] <sgmoore> or at least mine, I lack motu or core
[13:22] <santa_> ah that's another thing, having a KA check-and-fix program to check the package set
[13:23] <santa_> that was no longer that important when Rik got MOTU
[13:23] <sgmoore> I plan on it when things settle
[13:25] <santa_> that's great :)
[13:25] <santa_> on my side I already had plenty of work with my modest set of permissions
[13:28] <BluesKaj> Hi all
[13:29] <santa_> hi BluesKaj 
[13:29] <BluesKaj> hi santa_
 yes (re @sgmoore: I think I may have reproduce systray bug.. @myfenris @Eickmeyer y'all on Wayland by chance?)
 Wayland or X, it shows in both (re @sgmoore: I think I may have reproduce systray bug.. @myfenris @Eickmeyer y'all on Wayland by chance?)
 yeah .. its me ... (re @IrcsomeBot: <arraybolt3> myfenris: you don't happen to be fenris on the IRC side do you?)
 sorry i missed the meeting about the candidate .. (re @IrcsomeBot: <arraybolt3> If so, there's an Ubuntu Membership Board meeting that could use your help)
 the board members voting via email
 any specific help needed? (re @IrcsomeBot: <arraybolt3> If so, there's an Ubuntu Membership Board meeting that could use your help)