Greetings, Thanks Simon for spotting and reporting this!
> 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' For the rationale about such configuration, there were issues that seemed hardware specific and were caught in various contexts of execution of autopkgtest affecting gdpc. This was discussed first on Debian Med list[1] starting on 2026-01-25. The idea was to obtain more interesting information in such situation than a crude "buffer overflow" or "segmentation fault". [1] : https://lists.debian.org/debian-med/2026/01/msg00025.html Also, there is no urgency, as Yavor Doganov and Jeremy Bicha uploaded gdpc 2.2.5-19, which won't block on missing dbgsym. Have a nice day, :) -- .''`. Étienne Mollier <[email protected]> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/0, please excuse my verbosity `- on air: The Flower Kings - Last Minute On Earth
signature.asc
Description: PGP signature
