New Ubuntu Core Developer - Athos Ribeiro
Hello everyone! We are pleased to announce that at today's DMB meeting athos has been formally accepted into the Ubuntu Core Developer family! Welcome aboard and congratulations! Best regards, -- Łukasz 'sil2100' Zemczak Foundations Team Tools Squad Interim Engineering Manager lukasz.zemc...@canonical.com www.canonical.com -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Core Dev Application
As of the July 25th DMB meeting, this Core Developer application was approved, and we welcome Mattia into the ranks of the Ubuntu Core Developers. Congratulations, Mattia! Thomas Ubuntu DMB Member On 7/13/22 12:13, Mattia Rizzolo wrote: Hi DMB! I decided to finally send in my core-dev application. See https://wiki.ubuntu.com/MattiaRizzolo/CoreDevApplication I added myself to https://wiki.ubuntu.com/DeveloperMembershipBoard/Agenda for the next meeting (scheduled on 2022-07-25 16 CEST if I can read the pages right). -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
Re: Enablement of systemd-repart in Jammy LTS (post-release)
On Mon, Aug 08, 2022 at 11:38:35AM +0200, Lukas Märdian wrote: > I already suggested, that one option to get such an exception (by further > reducing the risk involved) could be to ship systemd-repart in a separate > binary package in universe, not installed by default. > And not as part of the primary "systemd" package in main, as currently > suggested. In general, adding new entirely new packages is considered OK from a regression risk perspective. But note that once it's in, you don't get a free pass on updating the package any more, since at that point regression risk exists again. I haven't looked into the proposal in detail, so I don't know whether I would prefer the integrated approach over not splitting it out. However, we generally don't just add new packages to a stable release updates pocket automatically. A justification is still needed, and then the SRU team will consider it on a case-by-case basis. You have provided that already, but I'm not completely clear on the justification here: > Unfortunately, they're currently blocked on this because 22.04 doesn't > ship systemd-repart. The upstream CI uses Github Actions which runs on > Ubuntu Jammy and will do so until the next Ubuntu LTS is released. Can Github Actions not install software from any other source? For example, what if you were to put systemd-repart as a new package into a PPA, or into jammy-backports? Would Github Actions really be incapable of using this? signature.asc Description: PGP signature -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
[ubuntu-studio-devel] Ubuntu Studio daily CD health check
This is a daily health check report on the Ubuntu Studio CD images. If you have any questions, contact Colin Watson . ubuntustudio/dvd: kinetic-dvd-amd64.iso oversized by 56514048 bytes (5056514048) -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Enablement of systemd-repart in Jammy LTS (post-release)
Hi all, I recently talked to bluca on IRC about the enablement of "systemd-repart" [2] in Jammy. It is already enabled in Kinetic. The rational being that they (upstream systemd) want to make use of it for their mkosi image builder running on GitHub Actions Jammy images. See [0] for a detailed explanation. I explained, that we cannot enable new features after feature freeze much less after final release, usually. But we agreed it should be brought up for discussion in this case. bluca already provided a full SRU bug [0] and merge proposal [1]. It seems to be a low-risk change bringing value to our users, as they could opt-in to using it. I already suggested, that one option to get such an exception (by further reducing the risk involved) could be to ship systemd-repart in a separate binary package in universe, not installed by default. And not as part of the primary "systemd" package in main, as currently suggested. We would like to get more opinions on that, especially from release/SRU team members. Cheers, Lukas [0] https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1897932 [1] https://code.launchpad.net/~bluca/ubuntu/+source/systemd/+git/systemd/+merge/427557 [2] https://www.freedesktop.org/software/systemd/man/systemd-repart.service.html -- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
