Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1186865 > unrolled thread

Bug#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs Michael Hudson-Doyle <michael.hudson@ubuntu.com> - 2024-02-21 01:10 +0100
    Bug#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs Steve Langasek <vorlon@debian.org> - 2024-03-06 19:50 +0100

#1186865 — Bug#1064377: tcl-expect: identified for time_t transition but no ABI in shlibs

Package: tcl-expect
Version: 5.45.4-2build1
Severity: serious
User: debian-arm@lists.debian.org
Usertags: time-t

Dear maintainers,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
tcl-expect 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, tcl-expect' shlibs file declares a dependency on a library
package name that contains no ABI information:

$ cat DEBIAN/shlibs
libexpect 5.45 tcl-expect
$

It is therefore not obvious that we should rename the package to
'tcp-expect-t64' as part of this transition.

Looking at the archive, there is a package built from a separate source
package, 'skycat', which 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 (upgrading tcl-expect without also upgrading
skycat) will result in ABI skew and may result in broken behavior.

Cheers,
mwh

[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/tcl-expect-dev/base/log.txt


-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-17-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

[toc] | [next] | [standalone]

#1189289

[Multipart message — attachments visible in raw view] — view raw

On Tue, Mar 05, 2024 at 01:34:19PM +0300, Sergei Golovan wrote:
> Hi Steve,

> On Mon, Feb 26, 2024 at 1:12 AM Steve Langasek <vorlon@debian.org> wrote:

> > Control: severity -1 normal

> > Note that there are no reverse-dependencies in the archive that link against
> > libexpect, so I think we can downgrade this bug (or close wontfix, at the
> > maintainer's discretion).

> Also, as far as I can see, libexpect does not expose time_t (it uses
> it only internally), so I'm
> closing this bug.

I leave this to your discretion.  This is a package whose headers failed to
analyze under abi-compliance-checker:

https://adrien.dcln.fr/misc/armhf-time_t/2024-02-26T12%3A07%3A00/logs/tcl-expect-dev/base/abi-compliance-checker.log

So we don't know that its ABI is affected, but we also don't know that it
isn't.

-- 
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/
slangasek@ubuntu.com                                     vorlon@debian.org

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web