[07:59] tjaalton: thank you for the libdrm fix and sync :) [07:59] RikMills: np, forgot to sync it earlier [10:18] sil2100: juliank: Laney: Can I somehow make the autopkgtest that we trigger from systemd github to be somehow more of a github action? and like download/unpack/show the results summary too? cause at the moment it's just a status thing and is kind of odd. [10:23] xnox: It depends what you mean by somehow [10:24] If you mean do work to make it happen, then yes. If you mean can be done with what we have currently, then no [10:24] I think it should be more like "@autopkgtest run-tests" kind of thing [10:27] Laney: i like the "@autopkgtest run-tests" aka similar to how snapcore build-action is. [10:27] Laney: at the moment looking at even simple https://github.com/marketplace/actions/http-request-action and then followed by poll/collect results. [10:29] what's wrong with using statuses? [10:29] they're the right way to represent the results of CI runs I think [11:26] Laney: hm. Somehow i thought statues thingies are legacy, and that it should all be github actions in the brave new world. [11:27] aka kind of like snapd spread tests that do fork off to google cloud, but then collect all the results in place. [11:31] xnox: AFAIK statuses are the API to make those cross / tick / running lists, don't think that's a legacy thing, it's integrated with PR landing for example [11:31] as for how they are requested to be run, I think that's up to the project [11:32] we just have a stupid 'post a run in progress for any PR opening / push' for autopkgtest [11:32] but it could be like post as response to a comment or action or something smarter [11:33] fair enough. [11:33] I'll try to move systemd from bionic to focal [11:33] it's overdue. [11:36] aye [11:36] xnox: https://github.com/ostreedev/ostree/pull/2350 [11:36] see the CI stuff on that, that's what would be nice for usu to have [11:36] us* [12:34] xnox yes the move from b->f was held up by lp: #1895132 but that's released now, however there are still some failures running the tests with focal [12:34] Launchpad bug 1895132 in linux (Ubuntu Bionic) "s390x broken with unknown syscall number on kernels < 5.8" [Medium,Fix committed] https://launchpad.net/bugs/1895132 [13:25] ddstreet: i see =( === cpaelzer_ is now known as cpaelzer [14:22] Hi [14:23] any plan about a rolling release for server ? [14:27] rolling release for server is an extraordinary idea ngl [14:28] eoli3n_, https://ubuntu.com/core is a rolling release server [14:29] "Ubuntu Core is Ubuntu for IoT and embedded environments" [14:29] (can even roll in both directions) [14:29] blaze is that sarcasm ? :) [14:30] i think it is a good idea, yes [14:30] well, it exists already ... [14:38] eoli3n_: well, you can use "devel" in your sources.list and yes, that is rolling.... =) [14:39] heh [14:39] against the wall ... [14:40] (not really something to use in production) [14:46] Is there a quick way to ask "which of the binaries provided by source package X is installed"? [14:46] I can do grep-dctrl magic. [14:47] But it seems to be a common thing I want, so wondering if there's an easier way already. [14:47] I want this for upgrade/downgrade purposes for tracking down a regression. [14:48] dpkg --get-selections ? [14:48] hmm, that wont show versions ... perhaps not then [14:49] I don't need versions really [14:49] Just the list of binary packages complementary to the one I want to upgrade/downgrade [14:49] ten it might work .. try it 🙂 [14:50] "grep-status -SnsPackage systemd" maybe [14:52] Need an -X in there too [14:58] Alternatively if you have the .debs downloaded then you could use debi -u [19:44] tjaalton, RikMills: plasma-desktop started to build again today, thank you both for the great work :)