[08:10] <RikMills> tjaalton: is a libdrm merge/sync due to happen for kinetic?
[08:11] <RikMills> next KDE plasma version may need 2.4.112
[08:11] <tjaalton> RikMills: already done
[08:11] <tjaalton> last week
[08:12] <tjaalton> huh, didn't upload it
[08:12] <RikMills> yeah, kinetic is at 2.4.110
[08:12] <Unit193> tjaalton: Sorry to ping you twice, but did you happen to see my other ping on the other network?
[08:12] <tjaalton> Unit193: yes, but it was late saturday or such
[08:13] <Unit193> Sure, not time sensitive, just hoped you didn't miss it or something. :)
[08:13] <tjaalton> RikMills: oh now I remember, lp didn't accept uploads at the time
[08:13] <RikMills> aha
[08:15] <RikMills> as long as it is on the way, that is grand :)
[08:15] <tjaalton> uploaded now
[08:15] <RikMills> ty :D
[08:16] <tjaalton> Unit193: so, as they were available before and no-one complained about patents, I guess they can be enabled...
[08:17] <Unit193> tjaalton: Thanks!
[08:18] <Unit193> I was hoping for such an outcome, wasn't really sure how it was going to turn out though.
[11:32] <luis220413> What architectures are supported by each Ubuntu desktop flavor?
[11:37] <tarzeau> luis220413: 22.04: amd64 arm64 armhf ppc64el s390x
[11:37] <tarzeau> same for kinetic, 21.10, 20.04, 18.04
[11:39] <luis220413> tarzeau: Thanks!
[11:43] <ogra> ... and soon riscv ... 🙂
[11:53] <jbicha> tarzeau: only amd64 & arm64 are supported for desktop. There aren't installers for the other architectures. Packages are generally built for other architectures but people are on their own then
[11:54] <jbicha> The ubuntu-desktop metapackage is currently built for "amd64 arm64 armhf ppc64el" in part because test and build issues were common on s390x for gjs and gnome-shell
[12:00] <tarzeau> jbicha: oh thanks for correcting me, didn't know (don't have anything else than amd64 and arm64)
[12:01] <tarzeau> ogra: do you have any riscv hardware? which one & cost of it?
[12:03] <ogra> tarzeau, i have a visionfive board ... cost was around 130€ ...
[12:03] <ogra> https://shop.allnetchina.cn/products/starfive-visionfive-ai-single-board-computer
[12:04] <ogra> seems the price rised ? weird ...
[12:04] <tarzeau> ogra: could you run https://github.com/alexmyczko/autoexec.bat/blob/master/benchmark and post output?
[12:04] <tarzeau> how many cores/memory?
[12:04] <ogra> note that it does not have a GPU, so not useful for desktop stuff
[12:04] <tarzeau> i don't mind no GPU. as long as it has video output, and keyboard/mouse input
[12:05] <tarzeau> and fast i/o + memory. no active cooling needed?
[12:05] <ogra> it is dualcore 1GHz, 8GB RAM
[12:05] <ogra> it comes with a fan, have not tried runing it without yet
[12:06] <tarzeau> nice, raspberry pies have more cpu power and similar ram, but sd card goes brrr everytime i want to use it, and it's so slow, it's pointless (ok if you don't need to read/write data)
[12:06] <ogra> I/O and memory are fine, CPU speed is noticeable slow (like with all current RISC boards i think)
[12:07] <tarzeau> what's also a pity is, 1 gbit only :( 2.5, 5, 10gbit would be such a killer these days
[12:08] <ogra> well, i actually use wifi only with it ....
[12:08] <tarzeau> ogra: if you get a chance to run my benchmark, i'm only interested in the memory+cpu outputs
[12:08] <tarzeau> what do you use yours for? (sorry this is getting offtopic)
[12:09] <ogra> i'll try ... though my board currently runs Ubuntu Core exclusively ... (would need a snap of yor benchmark first, r i can run it in lxd but then there is potentially some overhead from the container)
[12:09] <tarzeau> i don't mind, run it as you wish, might want to read it first, and comment out the parts about network+disk
[12:41] <luis220413> How can I force the expiry of a bug?
[12:41] <luis220413> How can I force the expiry of an incomplete bug?
[12:42] <ogra> incomlete auto-expires after 60 days
[12:42] <ogra> +p
[12:42] <ogra> there is nothign you need to do
[12:42] <luis220413> ogra: But there is a bug task for a project without bug tracking configured that is apparently blocking the expiration.
[12:43] <luis220413> This bug has not expired in 7 years.
[12:43] <ogra> close it as invalid ?
[12:43] <ogra> (that particular task)
[12:43] <luis220413> ogra: Done
[12:53] <rbasak> Different projects in LP have different bug expiration settings. It's a boolean - a project may choose not to expire inactive Incomplete bug tasks.
[13:25] <Eickmeyer[m]> luis220413: #launchpad is for asking for help with launchpad itself. Don't go in there asking for changes to individual bugs please.
[13:38] <luis220413> Eickmeyer[m]: Yes, but this is an operational issue with Launchpad (a bug watch is not updating).
[13:38] <Eickmeyer> luis220413: That takes time.
[13:38] <luis220413> Eickmeyer: But the change was done almost 2 years ago.
[13:40] <Eickmeyer> luis220413: But going in there and telling someone to do something is not the way. Maybe you should ask them why it's not doing the thing it's supposed to do so they can investigate a possible bug?
[13:41] <luis220413> Eickmeyer: OK
[13:41] <Eickmeyer> luis220413: People don't like to take orders, and you tend to try to give orders around here a lot, and we're not taking kindly to that.
[13:42] <luis220413> Eickmeyer: I will stop giving orders now.
[13:42] <Eickmeyer> luis220413: Thank you.
[13:53] <schopin> The package pktanon is stuck in -proposed because it doesn't have an armhf binary, but the -proposed version explicitly removed that arch. What'd be the correct way to solve this?
[13:55] <dbungert> schopin: as I hear it, you should request a_rchive remove the existing armhf binary.
[13:57] <schopin> dbungert: makes sense, thanks
[15:12] <bdmurray> Bug expiry is a little more complicated than just being Incomplete - https://help.launchpad.net/BugExpiry
[18:33] <arraybolt3[m]> This might be a silly question, but Ubuntu Kylin is still considered to be an official Ubuntu flavor, right? It's not listed on https://ubuntu.com/desktop/flavours.
[18:59] <icey[m]> hey coreycb - by chance, do you know how CMAKE_INSTALL_LIBDIR gets set in package builds (specifically: Ceph)?
[19:05] <krytarik> arraybolt3[m]: https://github.com/canonical/ubuntu.com/pull/11852 - I'm seeing this, but unfortunately the referenced issue (along with the whole "commercial-squad" project it is on) is set to private, so we can't tell from that what really the rationale is.. :3
[19:07] <sarnold> wow, when yo'ure accustomed to the launchpad big bright red banner that takes half a second extra to render into place, it's *super* easy to overlook the very small unobtrusive "private" marker
[19:12] <coreycb> icey[m]: it looks to be expansion of _libdir by cmake which it may get from ceph.spec.
[19:20] <icey[m]> ah, good spot, thanks :)
[19:20] <arraybolt3[m]> krytarik: Weird. We still treat it like an official flavor AFAIK, I wonder why they did that.
[19:21] <arraybolt3[m]> I asked because of a comment I noticed on Ask Ubuntu stating that Kylin used to be an official flavor, and I was like, "Used to be? Still is, right?"
[19:23] <arraybolt3[m]> And this was only 30 days ago.
[19:23] <krytarik> Yeah, if it wasn't anymore, that'd be totally new to me too - only their website is slightly inaccesible recently..
[19:25] <arraybolt3[m]> krytarik: The release team probably knows - do you think it's worth asking them or would that just be needless noise?
[19:26] <icey[m]> coreycb: any idea where _libdir is created?
[19:26] <icey[m]> the only reference I see creating it is buried in the jerasure part of the source
[19:27] <coreycb> icey[m]: I think cmake may be generating that
[19:27] <coreycb> well, expanding it
[19:27] <krytarik> arraybolt3[m]: Well, I definitely think this needs clarification, because I slightly feel like the community is being left out here.
[19:33] <arraybolt3[m]> krytarik: OK, I'll ask.
[20:31] <ItzSwirlz> hai, is feature freeze (the 25th) the last day we sync from debian unstable or is the actual last sync a earlier? Cinnamon packages have had patches and fixes that have been pushed to unstable and less requestsyncs would be nice :)
[20:39] <Fallen> Quick note on the above, community team is investigating the Kylin issue. We hope to get this resolved quickly, it was a surprise for some folks internally as well but I'm in touch with the right people now and will find out what happened.
[20:49] <jbicha> ItzSwirlz: yes, the autosync is turned off then, at "Debian Import Freeze" on the schedule
[20:50] <jbicha> last year, Debian Import Freeze was on an earlier day than Feature Freeze but that was a unique situation
[20:50] <ItzSwirlz> Thanks
[21:44] <Fallen> Hey folks, I've been able to get to the bottom of the situation. First off, there has been no decision to remove Kylin as a flavor.  We had been waiting for updated assets for that page and did not receive any from Kylin so far, which had inadvertently caused the removal. We're going to go ahead and revert the change and continue efforts to get up to date information from the Kylin folks. Thank you so much for flagging this!
[21:48] <Unit193> arraybolt3[m], krytarik: ↑ "Assests not updated, removed instead.  Oops" but is still official.
[22:16] <Eickmeyer[m]> Bear in mind, from a governance standpoint, it's up to the Technical Board to remove a flavor. It doesn't just happen overnight.
[22:28] <arraybolt3[m]> Fa
[22:28] <arraybolt3[m]> Fallen: Thanks for the update!