I just wanted to make sure this was not closed by mistake, since the
subject of your message mentions libydpdict, while the body
mentions cuneiform.
Marcin
śr., 14 lut 2024 o 22:18 Debian Bug Tracking System <
owner@bugs.debian.org> napisał(a):
Your message dated Wed, 14 Feb 2024 13:15:04 -0800
with message-id <Zc0tWHGHt+PnKiUZ@homer.dodds.net>
and subject line Re: libydpdict: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1062739,
regarding libydpdict: NMU diff for 64-bit time_t transition
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 owner@bugs.debian.org immediately.)
--
1062739: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062739
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
---------- Forwarded message ----------
From: Steve Langasek <vorlon@debian.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Cc:
Bcc:
Date: Fri, 02 Feb 2024 23:00:51 +0000
Subject: libydpdict: NMU diff for 64-bit time_t transition
Source: libydpdict
Version: 1.0.4-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-arm@lists.debian.org
Usertags: time-t
NOTICE: these changes must not be uploaded to unstable yet!
Dear maintainer,
As part of the 64-bit time_t transition required to support 32-bit architectures in 2038 and beyond (https://wiki.debian.org/ReleaseGoals/64bit-time), we have identified libydpdict as a source package shipping runtime libraries whose ABI
either is affected by the change in size of time_t, or could not be
analyzed via abi-compliance-checker (and therefore to be on the safe
side we assume is affected).
To ensure that inconsistent combinations of libraries with their reverse-dependencies are never installed together, it is necessary to
have a library transition, which is most easily done by renaming the
runtime library package.
Since turning on 64-bit time_t is being handled centrally through a change
to the default dpkg-buildflags (https://bugs.debian.org/1037136), it is important that libraries affected by this ABI change all be uploaded close together in time. Therefore I have prepared a 0-day NMU for libydpdict
which will initially be uploaded to experimental if possible, then to unstable after packages have cleared binary NEW.
Please find the patch for this NMU attached.
If you have any concerns about this patch, please reach out ASAP. Although this package will be uploaded to experimental immediately, there will be a period of several days before we begin uploads to unstable; so if
information
becomes available that your package should not be included in the
transition,
there is time for us to amend the planned uploads.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
---------- Forwarded message ----------
From: Steve Langasek <vorlon@debian.org>
To: 1062739-done@bugs.debian.org
Cc:
Bcc:
Date: Wed, 14 Feb 2024 13:15:04 -0800
Subject: Re: libydpdict: NMU diff for 64-bit time_t transition
Happily, we can report that an improved analysis shows cuneiform does not have an ABI affected by this transition. We will not be uploading to unstable, and the NMU in experimental can be ignored/superseded/requested
to
be removed.
--
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
<div dir="ltr">I just wanted to make sure this was not closed by mistake, since the subject of your message mentions libydpdict, while the body mentions cuneiform.<div><br></div><div>Marcin</div></div><br><div class="gmail_quote"><div dir="ltr" class="
gmail_attr">śr., 14 lut 2024 o 22:18 Debian Bug Tracking System <<a href="mailto:
owner@bugs.debian.org">
owner@bugs.debian.org</a>> napisał(a):<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,
204,204);padding-left:1ex">Your message dated Wed, 14 Feb 2024 13:15:04 -0800<br>
with message-id <<a href="mailto:Zc0tWHGHt%
2BPnKiUZ@homer.dodds.net" target="_blank">
Zc0tWHGHt+PnKiUZ@homer.dodds.net</a>><br>
and subject line Re: libydpdict: NMU diff for 64-bit time_t transition<br>
has caused the Debian Bug report #1062739,<br>
regarding libydpdict: NMU diff for 64-bit time_t transition<br>
to be marked as done.<br>
This means that you claim that the problem has been dealt with.<br>
If this is not the case it is now your responsibility to reopen the<br>
Bug report if necessary, and/or fix the problem forthwith.<br>
(NB: If you are a system administrator and have no idea what this<br>
message is talking about, this may indicate a serious mail system<br> misconfiguration somewhere. Please contact <a href="mailto:
owner@bugs.debian.org" target="_blank">
owner@bugs.debian.org</a><br>
immediately.)<br>
-- <br>
1062739: <a href="
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062739" rel="noreferrer" target="_blank">
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062739</a><br>
Debian Bug Tracking System<br>
Contact <a href="mailto:
owner@bugs.debian.org" target="_blank">
owner@bugs.debian.org</a> with problems<br>
<br><br><br>---------- Forwarded message ----------<br>From: Steve Langasek <<a href="mailto:
vorlon@debian.org" target="_blank">
vorlon@debian.org</a>><br>To: Debian Bug Tracking System <<a href="mailto:
submit@bugs.debian.org" target="_blank">
submit@bugs.debian.org</a>><br>Cc: <br>Bcc: <br>Date: Fri, 02 Feb 2024 23:00:51 +0000<br>Subject: libydpdict: NMU diff for 64-bit time_t transition<br>Source: libydpdict<br>
Version: 1.0.4-3<br>
Severity: serious<br>
Tags: patch pending sid trixie<br>
Justification: library ABI skew on upgrade<br>
User: <a href="mailto:
debian-arm@lists.debian.org" target="_blank">
debian-arm@lists.debian.org</a><br>
Usertags: time-t<br>
NOTICE: these changes must not be uploaded to unstable yet!<br>
Dear maintainer,<br>
As part of the 64-bit time_t transition required to support 32-bit<br> architectures in 2038 and beyond<br>
(<a href="
https://wiki.debian.org/ReleaseGoals/64bit-time" rel="noreferrer" target="_blank">
https://wiki.debian.org/ReleaseGoals/64bit-time</a>), we have identified<br>
libydpdict as a source package shipping runtime libraries whose ABI<br>
either is affected by the change in size of time_t, or could not be<br> analyzed via abi-compliance-checker (and therefore to be on the safe<br>
side we assume is affected).<br>
To ensure that inconsistent combinations of libraries with their<br> reverse-dependencies are never installed together, it is necessary to<br>
have a library transition, which is most easily done by renaming the<br> runtime library package.<br>
Since turning on 64-bit time_t is being handled centrally through a change<br> to the default dpkg-buildflags (<a href="
https://bugs.debian.org/1037136" rel="noreferrer" target="_blank">
https://bugs.debian.org/1037136</a>), it is<br>
important that libraries affected by this ABI change all be uploaded close<br> together in time. Therefore I have prepared a 0-day NMU for libydpdict<br> which will initially be uploaded to experimental if possible, then to<br> unstable after packages have cleared binary NEW.<br>
Please find the patch for this NMU attached.<br>
If you have any concerns about this patch, please reach out ASAP. Although<br>
this package will be uploaded to experimental immediately, there will be a<br> period of several days before we begin uploads to unstable; so if information<br>
becomes available that your package should not be included in the transition,<br>
there is time for us to amend the planned uploads.<br>
-- System Information:<br>
Debian Release: trixie/sid<br>
APT prefers unstable<br>
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')<br>
Architecture: amd64 (x86_64)<br>
Kernel: Linux 6.5.0-14-generic (SMP w/12 CPU threads; PREEMPT)<br>
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE<br>
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set<br>
Shell: /bin/sh linked to /usr/bin/dash<br>
Init: systemd (via /run/systemd/system)<br>
<br><br><br>---------- Forwarded message ----------<br>From: Steve Langasek <<a href="mailto:
vorlon@debian.org" target="_blank">
vorlon@debian.org</a>><br>To: <a href="mailto:
1062739-done@bugs.debian.org" target="_blank">
1062739-done@bugs.debian.
org</a><br>Cc: <br>Bcc: <br>Date: Wed, 14 Feb 2024 13:15:04 -0800<br>Subject: Re: libydpdict: NMU diff for 64-bit time_t transition<br>Happily, we can report that an improved analysis shows cuneiform does not<br>
have an ABI affected by this transition. We will not be uploading to<br> unstable, and the NMU in experimental can be ignored/superseded/requested to<br>
be removed.<br>
-- <br>
Steve Langasek Give me a lever long enough and a Free OS<br>
Debian Developer to set it on, and I can move the world.<br>
Ubuntu Developer <a href="
https://www.debian.org/" rel="noreferrer" target="_blank">
https://www.debian.org/</a><br>
<a href="mailto:
slangasek@ubuntu.com" target="_blank">
slangasek@ubuntu.com</a> <a href="mailto:
vorlon@debian.org" target="_blank">
vorlon@debian.org</a><br>
</blockquote></div>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)