Your message dated Fri, 13 Feb 2026 09:23:19 +0000
with message-id <[email protected]>
and subject line Re: Bug#1127656: debci: testing packages for migration takes
proposed package from unstable but -dbgsym from testing
has caused the Debian Bug report #1127656,
regarding debci: testing packages for migration takes proposed package from
unstable but -dbgsym from testing
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.)
--
1127656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1127656
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: debci
Severity: normal
X-Debbugs-Cc: [email protected], [email protected],
[email protected]
Control: affects -1 + src:glib2.0 src:gdpc
glib2.0/2.87.x is currently trying to migrate to testing, but is blocked
by the autopkgtest for src:gdpc regressing:
51s E: Unable to satisfy dependencies. Reached two conflicting assignments:
51s 1. libglib2.0-0t64-dbgsym:amd64 is selected for install because:
51s 1. satisfy:command-line:amd64=1 is selected for install
51s 2. satisfy:command-line:amd64 Depends libglib2.0-0t64-dbgsym
51s 2. libglib2.0-0t64-dbgsym:amd64 Depends libglib2.0-0t64 (= 2.86.3-5)
51s but none of the choices are installable:
51s - libglib2.0-0t64:amd64=2.86.3-5 is not selected for install
This appears to be because src:gdpc has a test dependency on
libglib2.0-0t64-dbgsym (it's unusual for a test to pull in detached
debug symbols like this), and debci ran autopkgtest with:
> --pin-packages=unstable=src:glib2.0 \
> --add-apt-source='deb-src http://deb.debian.org/debian unstable main contrib
> non-free non-free-firmware\
> deb http://deb.debian.org/debian unstable main contrib
> non-free non-free-firmware'
gdpc's test-dependencies will only be satisfiable if debci adds an apt
source for unstable detached debug symbols, too:
deb http://deb.debian.org/debian-debug unstable-debug main contrib non-free
non-free-firmware
so that apt can find the libglib2.0-0t64-dbgsym that corresponds to the
proposed libglib2.0-0t64 package.
Similarly when autopkgtests run on unstable, with selected packages from
experimental, debci should probably add an apt source for
experimental-debug.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
On Wed, 11 Feb 2026 at 20:35:17 +0100, Paul Gevers wrote:
I think
it's the responsibility of the job submitter to add all additional
archives as they need, and debci shouldn't infer from some additional
archive that more are needed. For britney2 there's already bug #917528
to do that.
Thanks, I'm never sure how much of this is a debci responsibility and
how much is coming from the testing migration infrastructure. Yes,
#917528 looks like the root cause.
I notice #917528 was also reported against debci and reassigned to
release.debian.org, so I'm not the only one getting this wrong. I've
added an "affects" so it shows on debci's BTS summary for the next
person to encounter this.
On Fri, 13 Feb 2026 at 06:55:20 +0100, Andreas Tille wrote:
I think this was solved in gdpc (2.2.5-19) upload.
This specific instance of the problem (the one that was stopping glib2.0
migrating), yes; and the problem more generally is already tracked as
#917528, so I'll close this report.
smcv
--- End Message ---
