[00:19] <mmikowski> RikMills: 5.27.10 is out. Do you want us to do a testing round for 22.04 LTS?
[12:54] <BluesKaj> Hi all
[13:56] <tsimonq2> RikMills cc santa_: Just as a warmup this morning, I'm going to demote k3b-l10n to Suggests and add it as a Recommends to the Kubuntu seed, as discussed.
[13:56] <tsimonq2> This affects all langpacks.
[13:56] <tsimonq2> Should be a no-op for Kubuntu, will test the next daily to double check.
[14:08] <tsimonq2> *k3b-i18n
[15:05] <tsimonq2> $ cat run | pastebinit
[15:05] <tsimonq2> https://dpaste.com/BJQ4CRESY
[15:05] <tsimonq2> That script is what did all the updating. ^^^
[15:05] <tsimonq2> I don't think I have a current SSH key on the KDE tarball site. Maybe we should fix that for bus factor.
[15:06] <tsimonq2> I didn't use the existing script because after reading it, well, we do a lot of the same things.
[15:06] <tsimonq2> We (Kubuntu) should probably do a translations update this cycle. I'll be happy to set aside some time in the next week or two to do some script rewriting and take care of that, unless someone else gets to it first.
[15:06] <tsimonq2> santa_: I'm just thinking it would be a nice addition to the existing KA stuff. :)
[15:07] <tsimonq2> Also, it all uses Bazaar. :P
[15:08] <tsimonq2> Eickmeyer: FYI in case you ship k3b, I'd check your ISO manifest after this lands to make sure you didn't have the i18n package before and no longer have it (if that makes sense).
[15:30] <Eickmeyer> tsimonq2: We do ship k3b, but not the i18n package explicitly. It's a recommends so it shouldn't cause a FTBFS, at worst I'll just run a meta update.
 Thanks!
[18:40] <santa_> good evening everyone
[18:43] <santa_> tsimonq2: thanks for the info about the translations, I also have the impression that maybe we could add something to KA to handle it, but I would need some time to read calmly and understand better how the lang packs work in Ubuntu, but I don't have much time right now :|
[18:44] <santa_> RikMills: FYI we are running short on space on https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/staging-kdeapplications/+packages so I'm going to ask about this in #launchpad (I hope that's the right place to ask)
[19:57] <tsimonq2> santa_: Conceptually it's pretty simple. You have one repository with the template for all the languages, and another repository with config. Then, it grabs all of the tarballs from [whatever the KDE SSH server is called these days], bumps the changelog, and builds the package.
[19:57] <tsimonq2> They're literally arch:all packages; not much could go wrong unless KDE drastically changes behavior upstream.
[19:58] <tsimonq2> In reality though, the implementation is sorely lacking. It's all still in Bazaar, you have to manually change some stuff, bleh... probably worked just wonderfully back in the day, but in 2023 with the power of Git it really should be streamlined better.
[19:58] <tsimonq2> For example, do we really need an extra repository for every single language if they're literally all the same?
[19:59] <tsimonq2> Additionally, given the small amount of depends we *actually* have, should we still split it out into kubuntu:Depends/Suggests?
[20:00] <tsimonq2> If I were the architect of KA with a magic wand, I'd probably start by getting the common package up to date with my changes from the archive, converting it all to Git, and going from there.
[20:13]  * dm2912 test