time_t progress report

2024-02-19 Thread Steve Langasek
Hi folks,

Not as quickly as hoped for, but we are getting close to having all the
library transitions staged in experimental[0] with NMU patches in the BTS.

Thanks to improved analysis coverage of various packages, the total count of
libraries transitioned has come down to something south of 1108+49=1157[1]. 
The count of reverse-dependencies to be binNMUed is now down to
5298+178=5476[2].  We have 1025 'pending' bugs filed with patches that will
be mass-NMUed to unstable, plus an additional 46 packages[4] for which
patches are available but which will not be included in the mass NMUs either
because the packages FTBFS in unstable or because the maintainers have asked
to handle these uploads directly; and 17 packages which have been identified
as needing a transition but don't have soname-qualified library package
names that accomodate inclusion in the mass-renaming.

There is one outstanding bug for a package among the experimental uploads
which needs usrmerge mitigation[6], and a small number of packages for which
the NMU patches need to be fixed because the resulting binary packages are
missing the actual libraries[7].

There are also a handful of packages still in flight for upload.

I have coordinated with the gcc maintainer so that we can have the default
flags in gcc-13 changed this week.

We are therefore targeting Friday for the mass NMUs to unstable though there
is a possibility this won't start until as late as Monday depending on
capacity.

I am including below for your review an annotated (unsorted) list of
packages that were identified as packages to be NMUed but which have not
been for one reason or another.

# already in experimental
abseil: failed
# already in experimental
ace: failed
# already in experimental
actor-framework: failed
# ftbfs in unstable
anfo: failed
# ftbfs in unstable
arrayfire: failed
# already in experimental
belle-sip: failed
# already in experimental
ceph: failed
# already in experimental
clamav: failed
# can't rename libbinutils; just punt it
binutils: failed
# ftbfs in unstable
libaws: failed
# already in experimental
libcdk5: failed
# already in experimental
libchipcard: failed
# ada, who the hell knows
libflorist: failed
# already in experimental
lib2geom: failed
# ftbfs in unstable
libcxx-serial: failed
# already in experimental
libhinawa: failed
# already in experimental
libkiwix: failed
# ftbfs since 2021
libneo4j-client: failed
# ftbfs in unstable, https://bugs.debian.org/1061493
consolekit2: failed
# just mark so we don't try to upload; maintainer will handle
libreoffice: failed
# no sane ABI info; https://bugs.debian.org/1064308
libricohcamerasdk: failed
# unsatisfiable build deps https://bugs.debian.org/1022008
librm: failed
# ftbfs since 2018 https://bugs.debian.org/893023
librsl: failed
# ftbfs in unstable https://bugs.debian.org/1050161
libtins: failed
# ftbfs in unstable (unreported)
libvirt-glib: failed
# ftbfs in unstable https://bugs.debian.org/1006506
libzorpll: failed
# ftbfs in unstable https://bugs.debian.org/1037752
lief: failed
# already in experimental
linphone: failed
# ftbfs in unstable https://bugs.debian.org/1013421
lives: failed
# no sane ABI info, no revdeps
linpac: failed
# ftbfs in unstable, https://bugs.debian.org/997441
squirrel3: failed
# no sane ABI info, no revdeps
swish-e: failed
# ftbfs in unstable
syndication: failed
# no sane ABI info, no revdeps; https://bugs.debian.org/1063077
syslog-ng: failed
# ftbfs in unstable https://bugs.debian.org/1060972
telepathy-farstream: failed
# already in experimental
unixcw: failed
# FTBFS in unstable https://bugs.debian.org/1060107
urweb: failed
# no sane ABI info, no revdeps
uptimed: failed
# ftbfs in unstable, previously unreported https://bugs.debian.org/1063044
vecgeom: failed
# ftbfs in unstable https://bugs.debian.org/1061655; likely false positive 
anyway?
wine: failed
# no sane ABI info, no revdeps
lldpad: failed
# no sane ABI info, no revdeps
linuxcnc: failed
# no sane ABI info, no revdeps
alsa-oss: failed
# already in experimental
bctoolbox: failed
# no sane ABI info; https://bugs.debian.org/1063254
lua-luv: failed
# no sane ABI info, no revdeps
tcplay: failed
# no sane ABI info; https://bugs.debian.org/1063275
r-bioc-rhtslib: failed
# already in experimental
vtk9: failed
# closed invalid by maintainer
xdp-tools: failed
# ftbfs in unstable; https://bugs.debian.org/1060164
xeus-python: failed
# no sane ABI info, no revdeps
xine-lib-1.2: failed
# already in experimental
xmlsec1: failed
# no sane ABI info, no revdeps; https://bugs.debian.org/1063316
xmorph: failed
# FTBFS in unstable, https://bugs.debian.org/1062427
ghmm: failed
# already in experimental
gimp: failed
# already in experimental
gmerlin: failed
# already in experimental; probably false positive, see 
https://bugs.debian.org/1062184
gnucap: failed
# see https://salsa.debian.org/vorlon/armhf-time_t/-/merge_requests/128
gcc-10: failed
# see https://salsa.debian.org/vorlon/armhf-time_t/-/merge_requests/128
gcc-11: failed
# s

Re: 64-bit time_t transition in progressL

2024-02-19 Thread Alastair McKinstry



On 18/02/2024 17:52, Alastair McKinstry wrote:

Hi Steve

On 16/02/2024 08:11, Steve Langasek wrote:

Hi Alastair,

There are in fact three related MPI transitions, as mpich-4.2.0 is 
essentially a mini-transition ;


openmpi 4 -> 5 drops 32-bit support, and has a Fortran API change too 
in close inspection: it moves MPI_Integer type from 4 to 8 bytes.


Apologies , I need to correct this; default MPI_Integer does not change 
from 4 bytes on openmpi5.


I have yet to upload an mpich transition bug to request transition.


I'm not sure how to do this; the API has changed, but not the ABI? the 
SO interface hasn't changed, so how do I write the appropriate BEN code?




Regards

Alastair


--
Alastair McKinstry,
GPG: 82383CE9165B347C787081A2CBE6BB4E5D9AD3A5
ph: +353 87 6847928 e: alast...@mckinstry.ie, im: @alastair:mckinstry.ie



Bug#1064279: ITP: jnr-a64asm

2024-02-19 Thread Jérôme Charaoui

Package: wnpp
Severity: wishlist
Owner: Jérôme Charaoui 
X-Debbugs-Cc: debian-devel@lists.debian.org

   Package name : jnr-a64asm
   Version  : 1.0.0
   Upstream author  : Ossdev07
   URL  : https://github.com/jnr/jnr-a64asm
   License  : Apache-2.0
   Programming Lang : Java
   Description  : Pure-java aarch64 assembler

jnr-a64asm is a pure-java port of AsmJit, a lightweight library for 
machine code generation written in C++ language.


This is a dependency of the jnr-ffi library (related parts are currently 
patched out).


Thanks,

-- Jerome