Your message dated Sun, 18 Feb 2024 16:28:38 -0800
with message-id <[email protected]>
and subject line Re: lua-socket: identified for time_t transition but no ABI in
shlibs
has caused the Debian Bug report #1064187,
regarding lua-socket: identified for time_t transition but no ABI in shlibs
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.)
--
1064187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064187
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lua-luv
Version: 1.44.2-0-1
Severity: serious
User: [email protected]
Usertags: time-t
Dear maintainers,
Analysis of the archive for the 64-bit time_t transition[0][1] identifies
luasocket as an affected package, on the basis that the headers could not
be compiled and analyzed out of the box using abi-compliance-checker[2], so
we have to assume it's affected.
However, lua-socket's shlibs file declares a dependency on a library package
name that contains no ABI information:
$ cat DEBIAN/shlibs
liblua5.1-mime 2 lua-socket (>= 3.1.0)
liblua5.1-socket-serial 0 lua-socket (>= 3.1.0)
liblua5.1-socket-unix 2 lua-socket (>= 3.1.0)
liblua5.1-socket 2 lua-socket (>= 3.1.0)
liblua5.2-mime 2 lua-socket (>= 3.1.0)
liblua5.2-socket-serial 0 lua-socket (>= 3.1.0)
liblua5.2-socket-unix 2 lua-socket (>= 3.1.0)
liblua5.2-socket 2 lua-socket (>= 3.1.0)
liblua5.3-mime 2 lua-socket (>= 3.1.0)
liblua5.3-socket-serial 0 lua-socket (>= 3.1.0)
liblua5.3-socket-unix 2 lua-socket (>= 3.1.0)
liblua5.3-socket 2 lua-socket (>= 3.1.0)
liblua5.4-mime 2 lua-socket (>= 3.1.0)
liblua5.4-socket-serial 0 lua-socket (>= 3.1.0)
liblua5.4-socket-unix 2 lua-socket (>= 3.1.0)
liblua5.4-socket 2 lua-socket (>= 3.1.0)
$
It is therefore not obvious that we should rename the package to
'lua-sockett64' as part of this transition.
Looking at the archive, there is a package built from the separate lua-sec
source package that depends on this library.
Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs.
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures will result in ABI skew and may result in
broken behavior.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
[email protected] [email protected]
[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
[2]
https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/logs/lua-socket-dev/base/log.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
We were able to get a successful analysis which show that lua-socket's ABI
is not affected by time_t, so closing this bug. Thanks!
On Sun, Feb 18, 2024 at 12:07:13AM -0800, Steve Langasek wrote:
> Control: reassign -1 src:luasocket/20200726-1
>
> Sigh, cut'n'paste fail. Reassigning.
>
> On Sat, Feb 17, 2024 at 11:57:16PM -0800, Steve Langasek wrote:
> > Source: lua-luv
> > Version: 1.44.2-0-1
> > Severity: serious
> > User: [email protected]
> > Usertags: time-t
> >
> > Dear maintainers,
> >
> > Analysis of the archive for the 64-bit time_t transition[0][1] identifies
> > luasocket as an affected package, on the basis that the headers could not
> > be compiled and analyzed out of the box using abi-compliance-checker[2], so
> > we have to assume it's affected.
> >
> > However, lua-socket's shlibs file declares a dependency on a library package
> > name that contains no ABI information:
> >
> > $ cat DEBIAN/shlibs
> > liblua5.1-mime 2 lua-socket (>= 3.1.0)
> > liblua5.1-socket-serial 0 lua-socket (>= 3.1.0)
> > liblua5.1-socket-unix 2 lua-socket (>= 3.1.0)
> > liblua5.1-socket 2 lua-socket (>= 3.1.0)
> > liblua5.2-mime 2 lua-socket (>= 3.1.0)
> > liblua5.2-socket-serial 0 lua-socket (>= 3.1.0)
> > liblua5.2-socket-unix 2 lua-socket (>= 3.1.0)
> > liblua5.2-socket 2 lua-socket (>= 3.1.0)
> > liblua5.3-mime 2 lua-socket (>= 3.1.0)
> > liblua5.3-socket-serial 0 lua-socket (>= 3.1.0)
> > liblua5.3-socket-unix 2 lua-socket (>= 3.1.0)
> > liblua5.3-socket 2 lua-socket (>= 3.1.0)
> > liblua5.4-mime 2 lua-socket (>= 3.1.0)
> > liblua5.4-socket-serial 0 lua-socket (>= 3.1.0)
> > liblua5.4-socket-unix 2 lua-socket (>= 3.1.0)
> > liblua5.4-socket 2 lua-socket (>= 3.1.0)
> > $
> >
> > It is therefore not obvious that we should rename the package to
> > 'lua-sockett64' as part of this transition.
> >
> > Looking at the archive, there is a package built from the separate lua-sec
> > source package that depends on this library.
> >
> > Since there is no self-evident thing to do with the library package name
> > here, we will not be handling this package as part of the mass NMUs.
> > Instead I am filing a serious bug because partial upgrades from bookworm to
> > trixie on 32-bit architectures will result in ABI skew and may result in
> > broken behavior.
> >
> > Thanks,
> > --
> > Steve Langasek Give me a lever long enough and a Free OS
> > Debian Developer to set it on, and I can move the world.
> > Ubuntu Developer https://www.debian.org/
> > [email protected] [email protected]
> >
> > [0] https://wiki.debian.org/ReleaseGoals/64bit-time
> > [1] https://lists.debian.org/debian-devel/2024/01/msg00041.html
> > [2]
> > https://adrien.dcln.fr/misc/armhf-time_t/2024-02-16T21%3A19%3A00/logs/lua-socket-dev/base/log.txt
>
> --
> Steve Langasek Give me a lever long enough and a Free OS
> Debian Developer to set it on, and I can move the world.
> Ubuntu Developer https://www.debian.org/
> [email protected] [email protected]
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer https://www.debian.org/
[email protected] [email protected]
signature.asc
Description: PGP signature
--- End Message ---
