Your message dated Tue, 8 Sep 2026 17:07:39 +0200
with message-id <[email protected]>
and subject line Re: Bug#1147160: unblock: pcre2/10.48-2
has caused the Debian Bug report #1147160,
regarding unblock: pcre2/10.48-2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1147160: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1147160
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:pcre2 src:glib2.0
User: [email protected]
Usertags: unblock
Control: block 1118572 by -1
pcre2 can't migrate until the recent binNMU of glib2.0 (#1146418) also
migrates, because the old glib2.0 fails its autopkgtest with the new
pcre2. When compiled with the old pcre2, the GRegex test suite is unable
to expect a new error code that was only introduced by the new pcre2.
I believe this results in a circular dependency, because the binNMU'd
glib2.0 fixes the autopkgtest regression but picks up a dependency on
the new pcre2, so the glib2.0 binNMU can't migrate until the new pcre2
does.
Please could the release team hint these two packages to be tested and
migrated together, or temporarily ignore the glib2.0 autopkgtest failure
so that they can both migrate?
Thanks,
smcv
--- End Message ---
--- Begin Message ---
On 2026-09-08 15:03:30 +0100, Simon McVittie wrote:
> Package: release.debian.org
> Severity: normal
> X-Debbugs-Cc: [email protected], [email protected]
> Control: affects -1 + src:pcre2 src:glib2.0
> User: [email protected]
> Usertags: unblock
> Control: block 1118572 by -1
>
> pcre2 can't migrate until the recent binNMU of glib2.0 (#1146418) also
> migrates, because the old glib2.0 fails its autopkgtest with the new
> pcre2. When compiled with the old pcre2, the GRegex test suite is unable
> to expect a new error code that was only introduced by the new pcre2.
>
> I believe this results in a circular dependency, because the binNMU'd
> glib2.0 fixes the autopkgtest regression but picks up a dependency on
> the new pcre2, so the glib2.0 binNMU can't migrate until the new pcre2
> does.
>
> Please could the release team hint these two packages to be tested and
> migrated together, or temporarily ignore the glib2.0 autopkgtest failure
> so that they can both migrate?
Hint added.
Cheers
--
Sebastian Ramacher
--- End Message ---
