Let's start with the first category. Those are packages that could be binNMUed, but there are issues that make those rebuilds not have the[...]
desired effect. This list include packages that
* are BD-Uninstallabe,
* FTBFS but with out ftbfs-tagged RC bug,
* have hard-coded dependencies on pre-t64 libraries,
* have $oldlib | $newlib dependencies (those are at least wrong on
armel/armhf and violate policy 2.2.1 once the pre-t64 libraries are
decrufted),
* have been rebuilt before all dependencies were built,
* have broken symbols/shlibs files producing incorrect dependencies,
* or might just be missing the binNMU (but those should be few).
hugin
On 2024-04-18 Sebastian Ramacher <sramacher@debian.org> wrote:
[...]
Let's start with the first category. Those are packages that could be binNMUed, but there are issues that make those rebuilds not have the desired effect. This list include packages that
* are BD-Uninstallabe,
* FTBFS but with out ftbfs-tagged RC bug,
* have hard-coded dependencies on pre-t64 libraries,
* have $oldlib | $newlib dependencies (those are at least wrong on
armel/armhf and violate policy 2.2.1 once the pre-t64 libraries are
decrufted),
* have been rebuilt before all dependencies were built,
* have broken symbols/shlibs files producing incorrect dependencies,
* or might just be missing the binNMU (but those should be few).
hugin[...]
Good morning,
thanks for the update.
Looking at hugin, I think it is fine on all release-architectures, none
of the problems noted above apply here. Am I missing something?
PS: fakeroot seems to be an important blocker not in the list.
Hi,
as the progress on the t64 transition is slowing down, I want to give an overview of some of the remaining blockers that we need to tackle to get
it unstuck. I tried to identify some clusters of issues, but there might
be other classes of issues.
Finally, packages that need rebuilds but currently have open FTBFS (RC + ftbfs tag) bugs:
(...)
virtualjaguar
I've spotted these Debian Med packages.[…]
Am Thu, Apr 18, 2024 at 09:22:02PM +0200 schrieb Sebastian Ramacher:[…]
[…]jellyfish
quorum
No idea how we can help here. Please let us know if we can do
something.
Let's start with the first category. Those are packages that could be binNMUed, but there are issues that make those rebuilds not have theBD-Uninstallable (mathgl FTBFS)
desired effect. This list include packages that
* are BD-Uninstallabe,
* FTBFS but with out ftbfs-tagged RC bug,
* have hard-coded dependencies on pre-t64 libraries,
* have $oldlib | $newlib dependencies (those are at least wrong on
armel/armhf and violate policy 2.2.1 once the pre-t64 libraries are
decrufted),
* have been rebuilt before all dependencies were built,
* have broken symbols/shlibs files producing incorrect dependencies,
* or might just be missing the binNMU (but those should be few).
3depict
arctica-greeterfixed recently
cegui-mk2not sure?
condornot sure?
courierFTBFS without a bug, filed
deepin-movie-rebornnot sure?
fastnetmonnot sure?
fcitx-kkcBD-Uninstallable (libkkc FTBFS)
gentlenot sure?
gnome-subtitlesFTBFS without a bug, filed
gocryptfsFTBFS without a bug, filed
gozerBD-Uninstallable (giblib FTBFS)
gtk-chthemefixed recently
gvmdnot sure?
gxneurBD-Uninstallable (xneur FTBFS)
haskell-gi-dbusmenugtk3BD-Uninstallable (haskell-gi-gtk FTBFS)
haskell-gi-gtkFTBFS without a bug, filed
haskell-gi-gtk-hsBD-Uninstallable (haskell-gi-gtk FTBFS)
haskell-gi-vteBD-Uninstallable (haskell-gi-gtk FTBFS)
haskell-gtk-strutBD-Uninstallable (haskell-gi-gtk FTBFS)
hklBD-Uninstallable (datatype99 FTBFS)
huginnot sure?
hxtoolsDep-Wait on libhx
ibus-kkcBD-Uninstallable (libkkc FTBFS)
ippsamplenot sure?
jellyfishnot sure?
jskeusFTBFS without a bug, filed
lcmaps-plugins-basicfixed recently
lcmaps-plugins-jobrepfixed recently
lcmaps-plugins-verify-proxyfixed recently
lcmaps-plugins-vomsfixed recently
libcanberranot sure?
libosmo-netifnot sure?
lightdmfixed recently
lightdm-gtk-greeterfixed recently
light-lockerfixed recently
limesuitenot sure?
llvm-toolchain-17not sure?
lmmsFTBFS, bug in wine
lyskom-serverBD-Uninstallable (adns FTBFS)
massxpert2BD-Uninstallable (libpappsomspp FTBFS)
nautilus-wipenot sure?
nclnot sure?
nfs-ganeshaBD-Uninstallable (ceph dropped 32bit)
obs-advanced-scene-switchernot sure?
openjdk-20BD-Uninstallable (wrong BD without a bug, filed)
perditionnot sure?
pppFTBFS
pradsnot sure?
prelude-lmlBD-Uninstallable (libprelude FTBFS)
prelude-managerBD-Uninstallable (libprelude FTBFS)
purple-xmpp-carbonsnot sure?
purple-xmpp-http-uploadnot sure?
python-escriptFTBFS (pmix dropped 32bit?)
qt5-ukui-platformthemenot sure?
quorumnot sure?
renpyBD-Uninstallable (pygame-sdl2 FTBFS)
roger-routerBD-Uninstallable (librm bug)
rtagsFTBFS without a tag, tagged
sdpaDep-Wait (mumps FTBFS because pmix dropped 32bit?)
seafile-clientnot sure?
slick-greeterfixed recently
sonic-visualiserFTBFS without a bug, filed
spectrwmnot sure?
spice-gtknot sure?
swtpmnot sure?
tfortunenot sure?
thunderbirdnot sure?
trantorfixed recently
ui-gxmlcppnot sure?
ukui-greeterfixed recently
urfkillnot sure?
vdeplug-pcapnot sure?
vdeplug-slirpnot sure?
wine-developmentFTBFS without a bug, filed
workerDep-Wait (avfs FTBFS)
xbase64not sure?
xcaFTBFS without a tag, tagged
I've spotted these Debian Med packages.
gentle
jellyfish
quorum
sbmltoolbox
vg
This package is in a bad state in any case and we are aware of this.
However, could you explain in how far is this affecting t64 transition
since 32bit architectures are excluded?
Sebastian Ramacher <sramacher@debian.org> writes:
Hi,
as the progress on the t64 transition is slowing down, I want to give an overview of some of the remaining blockers that we need to tackle to get
it unstuck. I tried to identify some clusters of issues, but there might
be other classes of issues.
Thanks for update. I haven't seen any response to my analysis of why 'shishi' shouldn't have t64-migrating, and lacking any response I
eventually made an upload to revert the renaming. I've raised an Ubuntu
bug too since they haven't synced the updated package. The Debian bug
is now closed, so it wasn't included in your list, and maybe everything
that can be hoped for is already achieved, but I wanted to mention as it ought to be on the t64 radar.
On Thu, Apr 18, 2024 at 09:22:02PM +0200, Sebastian Ramacher wrote:
Let's start with the first category. Those are packages that could be binNMUed, but there are issues that make those rebuilds not have the desired effect. This list include packages that
* are BD-Uninstallabe,
* FTBFS but with out ftbfs-tagged RC bug,
* have hard-coded dependencies on pre-t64 libraries,
* have $oldlib | $newlib dependencies (those are at least wrong on
armel/armhf and violate policy 2.2.1 once the pre-t64 libraries are
decrufted),
* have been rebuilt before all dependencies were built,
* have broken symbols/shlibs files producing incorrect dependencies,
* or might just be missing the binNMU (but those should be few).
cegui-mk2not sure?
condornot sure?
deepin-movie-rebornnot sure?
fastnetmonnot sure?
gentlenot sure?
huginnot sure?
limesuitenot sure?
gvmdnot sure?
ippsamplenot sure?
jellyfishnot sure?
nclnot sure?
libcanberranot sure?
libosmo-netifnot sure?
llvm-toolchain-17not sure?
nautilus-wipenot sure?
obs-advanced-scene-switchernot sure?
perditionnot sure?
pradsnot sure?
purple-xmpp-carbonsnot sure?
purple-xmpp-http-uploadnot sure?
qt5-ukui-platformthemenot sure?
quorumnot sure?
seafile-clientnot sure?
spectrwmnot sure?
spice-gtknot sure?
swtpmnot sure?
tfortunenot sure?
thunderbirdnot sure?
ui-gxmlcppnot sure?
urfkillnot sure?
vdeplug-pcapnot sure?
vdeplug-slirpnot sure?
xbase64not sure?
Let's start with the first category. Those are packages that could be binNMUed, but there are issues that make those rebuilds not have the
desired effect. This list include packages that
* are BD-Uninstallabe,
* FTBFS but with out ftbfs-tagged RC bug,
* have hard-coded dependencies on pre-t64 libraries,
* have $oldlib | $newlib dependencies (those are at least wrong on
armel/armhf and violate policy 2.2.1 once the pre-t64 libraries are
decrufted),
* have been rebuilt before all dependencies were built,
* have broken symbols/shlibs files producing incorrect dependencies,
* or might just be missing the binNMU (but those should be few).
Next, packages that need an upload since they build Architecture: all binaries depending on pre-t64 libraries:(9 packages out of 13)
Finally, packages that need rebuilds but currently have open FTBFS (RC + ftbfs tag) bugs:(57 packages out of 221)
If you wonder how you are able to help with the migration, here areWhat to do with autopkgtests that fail in testing because of problems with packages in testing that are fixed in unstable, e.g. the autopkgtest for speech-dispatcher/0.11.5-2 on https://qa.debian.org/excuses.php?package=glib2.0?
some things to do:
* Fix FTBFS bugs
* Check the status of autopkgtests [1] and report or fix any issues
related to failing tests.
* Check if source-only uploads for Arch: all packages are missing.
Hi,
On 24-04-2024 7:35 p.m., Andrey Rakhmatullin wrote:
What to do with autopkgtests that fail in testing because of problemswith
packages in testing that are fixed in unstable, e.g. the autopkgtest for speech-dispatcher/0.11.5-2 on
Inform the Release Team and we can either schedule the combination
manually, add a hint or both.
Hi,Can you please look at libproxy<->glib-networking? libproxy excuses show glib-networking tests failing, but they are working in sid.
On 24-04-2024 7:35 p.m., Andrey Rakhmatullin wrote:
What to do with autopkgtests that fail in testing because of problems with packages in testing that are fixed in unstable, e.g. the autopkgtest for speech-dispatcher/0.11.5-2 on
Inform the Release Team and we can either schedule the combination manually, add a hint or both.
I'm not a maintainer of either of them and I couldn't understand from theCan you please look at libproxy<->glib-networking? libproxy excuses show glib-networking tests failing, but they are working in sid.
And that's not missing a versioned Depends and/or Breaks? I.e. this is a
test only failure?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 360 |
Nodes: | 16 (2 / 14) |
Uptime: | 129:24:58 |
Calls: | 7,686 |
Files: | 12,828 |
Messages: | 5,711,157 |