Bug#1105152: Fwd: unblock dhcpcd
Howdy!
What currently sits in unstable was uploaded there, backed by an early
unblock request, precisely because it's needed for Trixie. Everything
newer or not essential for Trixie went straight to experimental.
Martin-Éric
ma 26.5.2025 klo 12.53 Sebastian Ramacher (sramacher@debian.org) kirjoitti:
>
> Hi,
>
> backports is not release team territory. But not that during the freeze
> I think that the rules to only upload once packages reached testing is
> important. Not everything will migrate until trixie is released.
>
> Cheers
>
> On 2025-05-25 18:50:00 +0200, Micha Lenk wrote:
> > Hi Sebastian,
> >
> > seems I fucked-up your mail address when trying to add you in CC. See
> > below...
> >
> > Best regards,
> > Micha
> >
> > -------- Forwarded Message --------
> > Subject: Re: unblock dhcpcd
> > Date: Sun, 25 May 2025 18:47:55 +0200
> > From: Micha Lenk <micha@debian.org>
> > To: Martin-Éric Racine <martin-eric.racine@iki.fi>
> > CC: 1105152@bugs.debian.org, "Sebastian Ramacher
> > <sramacher"@respighi.debian.org
> >
> >
> >
> > Hi Martin-Éric,
> >
> > On Thu, 22 May 2025 11:13:22 +0200 Sebastian Ramacher <sramacher@debian.org>
> > wrote:
> > > On 2025-05-22 12:04:31 +0300, Martin-Éric Racine wrote:
> > > > On Tue, 13 May 2025 15:32:43 +0000 Sebastian Ramacher
> > > > <sramacher@respighi.debian.org> wrote:
> > > > > Unblocked.
> > > > > Please note that the unblock didn't work. Instead, the delay got
> > > > lenghtened from 10 to 20 days.
> > >
> > > It did:
> > >
> > > Migration status for dhcpcd (1:10.1.0-10 to 1:10.1.0-11): Waiting for
> > > test results or another package, or too young (no action required now -
> > > check later)
> > > Issues preventing migration:
> > > ∙ ∙ Too young, only 13 of 20 days old
> > > Additional info:
> > > ∙ ∙ Piuparts tested OK -
> > > https://piuparts.debian.org/sid/source/d/dhcpcd.html
> > > ∙ ∙ autopkgtest for dhcpcd/1:10.1.0-11: amd64: Pass, arm64: No tests,
> > > superficial or marked flaky ♻ (reference ♻), armel: No tests,
> > > superficial or marked flaky ♻ (reference ♻), armhf: No tests,
> > > superficial or marked flaky ♻ (reference ♻), i386: No tests, superficial
> > > or marked flaky ♻ (reference ♻), ppc64el: No tests, superficial or
> > > marked flaky ♻ (reference ♻), riscv64: No tests, superficial or marked
> > > flaky ♻ (reference ♻), s390x: No tests, superficial or marked flaky ♻
> > > (reference ♻)
> > > ∙ ∙ Reproducible on amd64 - info ♻
> > > ∙ ∙ Reproducible on arm64 - info ♻
> > > ∙ ∙ Waiting for reproducibility test results on armhf - info ♻
> > > ∙ ∙ Reproducible on i386 - info ♻
> > > ∙ ∙ Ignoring block request by freeze, due to unblock request by sramacher
> > >
> > > The change in the age requirement is due to the start of the hard
> > > freeze.
> > Please note, currently the dhcpcd package in bookworm-backports is newer
> > than the package in trixie. This means, if dhcpcd 1:10.1.0-11 doesn't
> > migrate before trixie is released, we will end up with a situation where
> > systems upgrading from bookworm + bookworm-backports to trixie and having
> > the dhcpcd from bookworm-backports installed will have their dhcpcd package
> > remain on version 1:10.1.0-11~bpo12+1 from bookworm-backports.
> >
> > @Sebastian, I don't know whether this needs to be tracked in some way by the
> > release team. Will you take care of that in case we need it?
> >
> > @Martin-Éric, please, in the future don't upload versions to
> > stable-backports which have not migrated to testing yet.
> >
> > Best regards,
> > Micha
>
> --
> Sebastian Ramacher
Reply to: