On Thu, 5 Sept 2024 at 03:31, Rodrigo Figueiredo Zaiden <
rodrigo.zai...@canonical.com> wrote:
> Hi,
>
> The Ubuntu Security team has a proposed update for the AppArmor
> userspace utilities in focal and jammy ready to move forward that we
> would like the help of the SRU or archive admin teams.
>
On Sun, 1 Sept 2024 at 09:04, Erich Eickmeyer wrote:
> Hi Release Team!
>
> As alluded to earlier, we had some broken Ubuntu Studio builds which have
> since been rectified. However, now we have another problem which is simply
> beyond my ability to fix:
>
>- The new images do not appear on c
On Fri, 12 Apr 2024 at 06:48, Paride Legovini wrote:
> Hi ubuntu-release,
>
> A recent update has been done on autopkgtest.ubuntu.com, transitioning
> from autopkgtest 5.28 to 5.34.
Hooray! Thanks for maintaining and continuing to improve this critical
infrastructure!
Before this change, some
On Wed, 31 Jan 2024 at 13:33, Steve Langasek
wrote:
> On Wed, Jan 31, 2024 at 01:04:21PM +1300, Michael Hudson-Doyle wrote:
> > So do we think this reached any kind of consensus? Can I start deleting
> > code related to source ISOs?
>
> After basically a month with no genui
6+ isos with
> source content, which in my opinion nowadays wasn't very useful
> anyway.
>
> Cheers,
>
> On Thu, 4 Jan 2024 at 05:55, Steve Langasek
> wrote:
> >
> > On Thu, Jan 04, 2024 at 04:41:43PM +1300, Michael Hudson-Doyle wrote:
> > > Hello release te
Hello release team,
In the course of recent refactorings of ubuntu-cdimage / debian-cd we
somehow broke the building of source ISOs. I doubt this is anything very
deep and can surely be fixed but there is another option: stop building
source ISOs.
AFAIU the point of a source ISO is GPL-compliance
On Wed, 9 Aug 2023 at 02:18, Paride Legovini wrote:
> Hello everyone,
>
> We just finished building our first set of 22.04.3 release candidate
> images, which are now available for testing from the ISO tracker:
>
> https://iso.qa.ubuntu.com/qatracker/milestones/447/builds
>
> Please pick your fav
On Sat, 17 Jun 2023 at 00:30, Robie Basak wrote:
> In the case of an SRU using some kind of exception to bump to a newer
> upstream version (whether that's a microrelease, a feature changing
> major release or a backport of something) we can end up with:
>
> 1. Some kind of tracking bug that expl
On Thu, 1 Jun 2023 at 07:54, Steve Langasek
wrote:
> On Wed, May 31, 2023 at 01:14:27PM +1200, Michael Hudson-Doyle wrote:
> > On Sat, 27 May 2023 at 04:16, Steve Langasek
> > wrote:
>
> > > Thanks for raising this valid concern.
>
> > > On Thu, May 25, 2
On Sat, 27 May 2023 at 04:16, Steve Langasek
wrote:
> Thanks for raising this valid concern.
>
> On Thu, May 25, 2023 at 12:47:23PM +1200, Michael Hudson-Doyle wrote:
> > Debian bookworm is scheduled to be released on June 10. Debian Import
> > Freeze is currently schedule
Hi release team,
Debian bookworm is scheduled to be released on June 10. Debian Import
Freeze is currently scheduled for about six weeks later, on August 17. Do
we want to shut off debian imports early, basically as soon as bookworm
releases, to avoid having all our work overwhelmed by a bunch of
On Mon, 8 Aug 2022 at 15:12, Steve Langasek
wrote:
> Hi Michael,
>
> On Mon, Aug 08, 2022 at 11:55:08AM +1200, Michael Hudson-Doyle wrote:
> > Hi all,
>
> > Glibc 2.36 was released last week. I'd hoped to have an archive test
> > rebuild done with a recent snap
Hi all,
Glibc 2.36 was released last week. I'd hoped to have an archive test
rebuild done with a recent snapshot but with one thing and another this
didn't happen. So I'd like some thoughts about what to do wrt getting the
update in before feature freeze.
One option would be to start a test rebui
On Thu, 30 Jun 2022 at 13:21, Robie Basak wrote:
> Hi Michael,
>
Thanks for the reply!
> On Thu, Jun 30, 2022 at 12:43:20PM +1200, Michael Hudson-Doyle wrote:
> > I also want to get an SRU into jammy in time for the release of 20.04.1
> > which is due August 4, probably
Hi all,
In the next few weeks I intend to upload glibc to both jammy and kinetic.
I intend to upload the 2.36 release to kinetic as reasonably possible after
the upstream release, which is due August 1 (we should get a test rebuild
going soon I guess!).
I also want to get an SRU into jammy in ti
On Tue, 8 Mar 2022 at 17:01, Michael Hudson-Doyle <
michael.hud...@canonical.com> wrote:
> Hi all,
>
> Last week I uploaded glibc to jammy-proposed. This gummed up the
> autopkgtest queues a good deal as usual but once all is done there are two
> regressions (well three curr
Hi all,
Last week I uploaded glibc to jammy-proposed. This gummed up the
autopkgtest queues a good deal as usual but once all is done there are two
regressions (well three currently but I think one will go away on retry):
libassuan/2.5.5-1 and libgpg-error/1.43-3. These fail in the same way: they
On Fri, 21 May 2021, 02:28 Julian Andres Klode,
wrote:
> On Wed, May 19, 2021 at 03:59:06PM -0700, Brian Murray wrote:
> > The release team was recently discussing the possibility of point
> > release media containing updates which are not fully phased and how this
> > creates a difference betwee
Hi,
We've just added a new proposed migration report:
https://people.canonical.com/~ubuntu-archive/proposed-migration/eoan/rcbuggy-problem-packages.html
The idea here is to identify packages that are not in debian testing
because of release critical bugs that are preventing other packages from
On 21 October 2016 at 06:21, Steve Langasek
wrote:
> On Thu, Oct 20, 2016 at 09:58:45AM +, Adam Conrad wrote:
> > On Wed, Oct 19, 2016 at 06:02:35PM -0700, Steve Langasek wrote:
>
> > > The only complication I'm aware of is that we absolutely must have
> different
> > > apt preferences behavi
20 matches
Mail list logo
