Re: Status of the t64 transition

2024-04-24 Thread Sebastian Ramacher
Hi,

dpkg and gcc with t64 enabled migrated to trixie last night. The other
packages will slowly migrate as we fix the remaining blockers
(autopkgtest regressions, FTBFS bugs, etc). Be aware that temporary
removals from trixie may occur to get packages (especially key packages)
unstuck as we work through all the packages hat need to migrate.

Since the time_t bugs are now also RC in trixie, I will reraise the
severity of all time_t bugs to serious in 1 week.

If you wonder how you are able to help with the migration, here are
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.

Cheers

[1] Note that wecurrently ignore autopkgtest results on armel and armhf.
-- 
Sebastian Ramacher



Re: Status of the t64 transition

2024-04-21 Thread Sebastian Ramacher
Hi Andreas,

please stop reopening the time_t bugs where transitions are staged in
experimental. When we eventually start those transitions, they do not
need to change the package name again as they will enter unstable with a
new SONAME and built with the 64 bit time_t ABI.

Cheers
-- 
Sebastian Ramacher



Re: Status of the t64 transition

2024-04-19 Thread Sebastian Ramacher
Hi Andreas

On 2024-04-19 10:49:15 +0200, Andreas Tille wrote:
> I've spotted these Debian Med packages.
> 
> > gentle

gentle required a rebuild for wxwidgets3.2 on mips64el. Done

> > jellyfish

The t64 changes were reverted. crac needs to rebuilt for this change so
that libjellyfish-2.0-2t64 can be decrufted. I've scheduled binNMUs and
excluded from further checks.

> > quorum

With jellyfish reverted, this one is fine.

> > sbmltoolbox

Builds an arch: all package with a dependency on a pre-t64 library. This
will need an upload fixing this issue.

> > 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?

As said in my initial mail, I didn't exclude packages that are not part
of testing. Patches welcome.

Cheers
-- 
Sebastian Ramacher



Re: Status of the t64 transition

2024-04-19 Thread Étienne Mollier
Hi Sebastian,

Andreas Tille, on 2024-04-19:
> 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.

About these two packages, I'm not 100% sure, but I believe some
confusion may stem from jellyfish's support removal for 32-bit
architectures[1,2].  This made the transition unnecessary so the
package renaming has been undone in version 2.3.1-3, as far as I
can witness in the changelog.  This probably affected quorum
transitively; and also this possibly affected crac, the other
libjellyfish-2.0-2 reverse dependency, although I don't know why
it hasn't stood out on the list.

[1]: https://bugs.debian.org/1067166
[2]: https://github.com/gmarcais/Jellyfish/pull/202#issuecomment-2007544485

In hope this clarifies things,
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/2, please excuse my verbosity
   `-


signature.asc
Description: PGP signature


Re: Status of the t64 transition

2024-04-19 Thread Andreas Tille
Hi Sebastian,

thank you for your work on t64 transition.

Am Thu, Apr 18, 2024 at 09:22:02PM +0200 schrieb Sebastian Ramacher:

I've spotted these Debian Med packages.

> gentle
> jellyfish
> quorum
> sbmltoolbox

No idea how we can help here.  Please let us know if we can do
something.

> anfo

We like to fix gcc-12 issues (#1012893) in anfo but so far nobody
managed to do so since it seems to be quite complex.  If we are
blocking progress with this package its probably a sign that it
should be removed from Debian.

> blasr

We try to work on #1067374.

> freebayes

Upstream is working on bug #1067271.

> 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?

> If you maintain any of the packages above, please check their status and
> help get them fixed. Any help in filing bugs, fixing packages,
> requesting removals, etc. is appreciated so that we can look into
> unblocking the whole stack and migrate it to testing.

I fixed two packages of Debian Python Team and pinged about some
packages in Debian Science Team.

Kind regards
Andreas. 

-- 
https://fam-tille.de



Re: Status of the t64 transition

2024-04-19 Thread John Paul Adrian Glaubitz
Hello,

On Thu, 2024-04-18 at 21:22 +0200, Sebastian Ramacher wrote:
> Finally, packages that need rebuilds but currently have open FTBFS (RC +
> ftbfs tag) bugs:
> (...)
> virtualjaguar

I already have a tentative patch and will fix the package within the next
days. I am also preparing to fix two other bugs, one being missing SDL-2
support and the other the FTBFS after rebuild from the same source unpack.

Adrian

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer
`. `'   Physicist
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913



Re: Status of the t64 transition

2024-04-19 Thread Sebastian Ramacher
On 2024-04-19 06:02:03 +0200, Andreas Metzler wrote:
> On 2024-04-18 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).
> 
> > 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?

It required rebuilds for wxwidgets3.2 on mips64el:

INFO Rebuilding src:hugin/2023.0.0+dfsg-1 (hugin) for libwxbase3.2-1 on mips64el
INFO Rebuilding src:hugin/2023.0.0+dfsg-1 (hugin-tools) for libwxbase3.2-1 on 
mips64el

They were scheduled last night and now hugin is fine. Thanks for double 
checking.

> PS: fakeroot seems to be an important blocker not in the list.

The lists in my mail only contain those packages that require changes to
their dependencies due to the library package renames. So everything on
these lists depends on foo, but should depend on foot64 [1]. fakeroot
only depends on packages that are not involved in the t64 transition.

Cheers

[1] And some other variations including previous ABI transitions such as
v5, etc:
https://github.com/sebastinas/drt-tools/blob/main/src/nmu_t64.rs#L75

-- 
Sebastian Ramacher



Re: Status of the t64 transition

2024-04-18 Thread Andreas Metzler
On 2024-04-18 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).

> 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?

TIA, cu Andreas

PS: fakeroot seems to be an important blocker not in the list.



Status of the t64 transition

2024-04-18 Thread Sebastian Ramacher
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.

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).

3depict
arctica-greeter
cegui-mk2
condor
courier
deepin-movie-reborn
fastnetmon
fcitx-kkc
gentle
gnome-subtitles
gocryptfs
gozer
gtk-chtheme
gvmd
gxneur
haskell-gi-dbusmenugtk3
haskell-gi-gtk
haskell-gi-gtk-hs
haskell-gi-vte
haskell-gtk-strut
hkl
hugin
hxtools
ibus-kkc
ippsample
jellyfish
jskeus
lcmaps-plugins-basic
lcmaps-plugins-jobrep
lcmaps-plugins-verify-proxy
lcmaps-plugins-voms
libcanberra
libosmo-netif
lightdm
lightdm-gtk-greeter
light-locker
limesuite
llvm-toolchain-17
lmms
lyskom-server
massxpert2
nautilus-wipe
ncl
nfs-ganesha
obs-advanced-scene-switcher
openjdk-20
perdition
ppp
prads
prelude-lml
prelude-manager
purple-xmpp-carbons
purple-xmpp-http-upload
python-escript
qt5-ukui-platformtheme
quorum
renpy
roger-router
rtags
sdpa
seafile-client
slick-greeter
sonic-visualiser
spectrwm
spice-gtk
swtpm
tfortune
thunderbird
trantor
ui-gxmlcpp
ukui-greeter
urfkill
vdeplug-pcap
vdeplug-slirp
wine-development
worker
xbase64
xca

Next, packages that need an upload since they build Architecture: all
binaries depending on pre-t64 libraries:

alsa-ucm-conf
anki
clearlooks-phenix-theme
gtk-sharp3
jruby
mandos
python-pylibdmtx
pyzbar
rapid-photo-downloader
ruby-ethon
ruby-ffi-libarchive
sbmltoolbox
syncevolution

Finally, packages that need rebuilds but currently have open FTBFS (RC +
ftbfs tag) bugs:

3dchess
ace-of-penguins
acm
adns
adonthell
alsa-oss
amberol
anfo
arrayfire
audtty
barrier
blasr
boinc-app-eah-brp
broker
caml-crush
cctools
clanlib
clazy
clickhouse
code-saturne
coz-profiler
cp2k
cpdb-backend-cups
cpm
criu
curlftpfs
dapl
darcs
das-watchdog
deepin-log-viewer
dnstop
dolphin-emu
dradio
dub
dune-pdelab
dvbstreamer
dx
ecere-sdk
elektra
epic4
epic5
eterm
filament
freebayes
freebsd-buildutils
gabedit
gamazons
ganeti
gdis
ggcov
ghdl
ghemical
giblib
gigedit
glirc
gnat-gps
gnome-breakout
gnome-photos
gnunet-gtk
google-compute-engine-oslogin
grok
gsocket
gtk-sharp3
gtkterm
gwc
gyoto
hardinfo
hping3
hplip
httest
i2masschroq
ibus-anthy
info-beamer
intel-hdcp
irssi-plugin-robustirc
isoquery
kamailio
kbtin
kcov
kdrill
kexec-tools
keynav
klatexformula
kluppe
kpatch
kraptor
kwin-effect-xrdesktop
ldapvi
lftp
libaws
libengine-gost-openssl
libgovirt
libkkc
libnginx-mod-http-modsecurity
liboqs
librm
libvma
libzorpll
lief
linssid
lintian-brush
linuxtv-dvb-apps
literki
lives
llvm-toolchain-16
lmemory
lnav
loqui
lsh-utils
mahimahi
maildrop
matchbox-keyboard
matchbox-panel
mate-equake-applet
mathgl
mdbtools
mdk4
mit-scheme
mldemos
mlpcap
mod-gnutls
moonshot-ui
mozillavpn
mpqc3
ncrack
netdiag
newsboat
nitrokey-app
nng
ntopng
obs-ashmanix-countdown
obs-downstream-keyer
obs-ptz
obs-scene-notes-dock
obs-websocket
octave-mpi
openems
openexr-viewers
openjdk-19
openmx
opensta
openturns
openvas-scanner
ortools
performous-composer
pesign
pidgin-sipe
pixmap
pngphoon
porg
projecteur
purify
purple-lurch
pxe-kexec
pyferret
pygame-sdl2
pytorch-vision
qstopmotion
raku-readline
ramond
rdup
recutils
regina-normal
resvg
rmlint
ruby3.2
ruby-fcgi
ruby-ruby-magic-static
ruby-sigar
s390-tools
sagemath
samhain
scm
scrollz
sdaps
searchmonkey
siconos
siridb-server
sitecopy
slapi-nis
slrn
sniffit
snort
spek
spotlighter
squeak-plugins-scratch
stimfit
subvertpy
supertuxkart
swift-im
syrthes
tcptrack
telegram-purple
termrec
thin-provisioning-tools
threadscope
tightvnc
tlog
uhub
urweb
vart
vecgeom
veusz
vg
virtualjaguar
whitedune
wmweather+
xbill
xcolmix
xir
xneur
xpat2
xpra
xqilla
xrt
xshogi
xtide
yap
yrmcds
zabbix
zeek

Note that not all of the packages listed above have bugs filed. Also,
the list is produced based on the state in unstable. Packages that were
already removed from testing are also on these lists.

If you maintain any of the packages above, please check their status and
help get them fixed. Any help in filing bugs, fixing packages,
requesting removals, etc. is appreciated so that we can look into
unblocking the whole stack and migrate it to testing.

The dd-list of the packages above is attached.

Cheers
-- 
Sebastian Ramacher
A Mennucc1 
   dvbstreamer

Adam Borowski 
   kbtin
   termrec

Adrian Knoth 
   qstopmotion (U)

Agathe Porte