Bug#1062702: libomp-dev: Program which has run for ten years crashed after distribution upgrade

[Sylvestre Ledru]

Hello,

Le 02/02/2024 à 20:02, William Melgaard a écrit :

Package: libomp-dev
Version: 1:14.0-55.7~deb12u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: piob...@mindspring.com

Dear Maintainer,



we will need more information about it. which versions you had, which 
version of you have now, gcc, etc


Thanks,

Cheers

S

Bug#1062775: lintian: watchfile v3 + DEB_EXT in dversionmangle leads to debian-watch-not-mangling-version

[Fab Stz]

Package: lintian
Version: 2.116.3
Severity: normal
Tags: patch

Dear Maintainer,

Consider this watchfile:

version=3
# Search the version number on this page
https://download.qt.io/development_releases/qt/6.7/
# Then use downloadurlmangle to transform it to the URL to the archive.
#
# We don't use repacksuffix=+ds because in salsa-ci we want to have the +ds
suffix, even if we use --no-exclusion (ie even if we ignore Files-Excluded)
#
opts="uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/, 
\
 dversionmangle=s/@DEB_EXT@//, \
 oversionmangle=s/$/\+ds.1/, \
downloadurlmangle=s/\/([\d\.]*(-((RC|rc|pre|dev|beta|alpha)\d*))?)\/$/\/$1\/
single\/qt-
everywhere-src-$1\.tar\.xz/, \
 filenamemangle=s/.*\/([\d\.]*(-((RC|rc|pre|dev|beta|alpha)\d*))?)\/$/qt-
everywhere-src-$1\.tar\.xz/" \
 https://download.qt.io/development_releases/qt/6\.(?:[\d\.]*)/ ([\d\.]*-.*)/
debian bash debian/scripts/repack.sh



Lintian will output:

debian-watch-not-mangling-version
opts="uversionmangle=s/(\d)[_\.\-\+]?((RC|rc|pre|dev|beta|alpha)\d*)$/$1~$2/,
dversionmangle=s/@DEB_EXT@//, oversionmangle=s/$/\+ds.1/,
downloadurlmangle=s/\/([\d\.]*(-((RC|rc|pre|dev|beta|alpha)\d*))?)\/$/\/$1\/
single\/qt-
everywhere-src-$1\.tar\.xz/,
filenamemangle=s/.*\/([\d\.]*(-((RC|rc|pre|dev|beta|alpha)\d*))?)\/$/qt-
everywhere-src-$1\.tar\.xz/"
https://download.qt.io/development_releases/qt/6\.(?:[\d\.]*)/ ([\d\.]*-.*)/
debian bash debian/scripts/repack.sh [debian/watch:12]


I suspect this is because lintian considers that @DEB_EXT@ is only valid for a
watchfile version >= 4 (see $DMANGLES_AUTOMATICALLY variable), but according 
to
source code in uscan, it seems it requires version >= 2.


BTW, I noticed that:
- if I use version=4 with @DEB_EXT@, the lintian warning is gone
- if I use version=3 + dversionmangle=auto, the lintian warning is gone as
well.

But version=3 with @DEB_EXT@ triggers the warning.

I'm attaching a patch without being sure that it is the correct way to fix the 
issue, but when it is applied lintian doesn't report a warning.



-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (991, 'stable-updates'), (991, 'stable-security'), (991, 
'stable'), (990, 'proposed-updates'), (390, 'oldstable-security'), (390, 
'oldstable'), (389, 'oldstable-updates'), (380, 'oldoldstable'), (379, 
'oldoldstable-updates'), (370, 'oldoldstable'), (95, 'testing'), (94, 
'unstable'), (93, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-17-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), 
LANGUAGE=fr:en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages lintian depends on:
ii  binutils2.40-2
ii  bzip2   1.0.8-5+b1
ii  diffstat1.65-1
ii  dpkg1.21.22
ii  dpkg-dev1.21.22
ii  file1:5.44-3
ii  gettext 0.21-12
ii  gpg 2.2.40-1.1
ii  intltool-debian 0.35.0+20060710.6
ii  iso-codes   4.15.0-1
ii  libapt-pkg-perl 0.1.40+b2
ii  libarchive-zip-perl 1.68-1
ii  libberkeleydb-perl  0.64-2+b1
ii  libcapture-tiny-perl0.48-2
ii  libclass-xsaccessor-perl1.19-4+b1
ii  libclone-perl   0.46-1
ii  libconfig-tiny-perl 2.28-2
ii  libconst-fast-perl  0.014-2
ii  libcpanel-json-xs-perl  4.35-1
ii  libdata-dpath-perl  0.58-2
ii  libdata-validate-domain-perl0.10-1.1
ii  libdata-validate-uri-perl   0.07-2
ii  libdevel-size-perl  0.83-2+b1
pn  libdigest-sha-perl  
ii  libdpkg-perl1.21.22
ii  libemail-address-xs-perl1.05-1+b1
ii  libfile-basedir-perl0.09-2
ii  libfile-find-rule-perl  0.34-3
ii  libfont-ttf-perl1.06-2
ii  libhtml-html5-entities-perl 0.004-3
ii  libhtml-tokeparser-simple-perl  3.16-4
ii  libio-interactive-perl  1.023-2
ii  libipc-run3-perl0.048-3
ii  libjson-maybexs-perl1.004004-1
ii  liblist-compare-perl0.55-2
ii  liblist-someutils-perl  0.59-1
ii  liblist-utilsby-perl0.12-2
ii  libmldbm-perl   2.05-4
ii  libmoo-perl 2.005005-1
ii  libmoox-aliases-perl0.001006-2
ii  libnamespace-clean-perl 0.27-2
ii  libpath-tiny-perl   0.144-1
ii  libperlio-gzip-perl 0.20-1+b1
ii  libperlio-utf8-strict-perl  0.010-1
ii  libproc-processtable-perl   0.634-1+b2
ii  libregexp-wildcards-perl1.05-3
ii  libsereal-decoder-perl  5.003+ds-1
ii  libsereal-encoder-perl  

Bug#1061660: liblwp-protocol-https-perl: Fail to verify certificates

[Christian Marillat]

On 02 févr. 2024 18:37, gregor herrmann  wrote:

> On Tue, 30 Jan 2024 18:18:59 +0100, Christian Marillat wrote:
>
>> > @@ -96,9 +96,12 @@
>> >  if ( $Net::HTTPS::SSL_SOCKET_CLASS->can('start_SSL')) {
>> >  *_upgrade_sock = sub {
>> >my ($self,$sock,$url) = @_;
>> > +# SNI should be passed there only if it is not an IP address.
>> > +# Details: 
>> > https://github.com/libwww-perl/libwww-perl/issues/449#issuecomment-1896175509
>> 
>> I had  the idea to read this github issue.
>
> Thanks for your further investigations!
>  
>> In my case I've a proxy and IPv6 isn't configured so this explain this
>> Debian bug and reverting upstream changes in 6.12 is maybe a bad idea.
>
> Ok; so where does this leave us? Do I understand you correctly that
> we should not revert the above change, and that the issue is with
> your local setup? So should we just close the bug or is there
> anything left?

This bug should be fixed. If Ipv6 isn't available, Ipv4 should be used.
Before 6.12 this package was working perfectly.

Th best is to forward this bug to upstream author.

Christian

Bug#1062774: xdotool: "mousemove --sync" can take 15s

[Jakub Wilk]

Package: xdotool
Version: 1:3.20160805.1-5

"xdotool mousemove --sync" takes over 15 seconds if the mouse cursor is 
already in the right location:


   $ for i in 1 2; do time xdotool mousemove --sync 37 42; done

   real 0m0.007s
   user 0m0.003s
   sys  0m0.003s

   real 0m15.236s
   user 0m0.025s
   sys  0m0.030s


-- System Information:
Architecture: i386

Versions of packages xdotool depends on:
ii  libc6 2.36-9+deb12u4
ii  libx11-6  2:1.8.4-2+deb12u2
ii  libxdo3   1:3.20160805.1-5

--
Jakub Wilk

Bug#1062773: python-watchgod: autopkgtest needs update for new version of python-anyio

[Paul Gevers]

Source: python-watchgod
Version: 0.8.2-2
Severity: serious
X-Debbugs-CC: python-an...@packages.debian.org
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-anyio

Dear maintainer(s),

[I note that python-watchgod has been requested for removal, but it has 
a big chain of reverse dependencies, so this bug is mostly to warn them, 
as it will trigger autoremoval from testing of python-watchgod and these 
reverse dependencies.]


With a recent upload of python-anyio the autopkgtest of python-watchgod 
fails in testing when that autopkgtest is run with the binary packages 
of python-anyio from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
python-anyio   from testing4.2.0-1
python-watchgodfrom testing0.8.2-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of python-anyio to 
testing [1]. Of course, python-anyio shouldn't just break your 
autopkgtest (or even worse, your package), but it seems to me that the 
change in python-anyio was intended and your package needs to update to 
the new situation.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from python-anyio should 
really add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python-anyio

https://ci.debian.net/data/autopkgtest/testing/arm64/p/python-watchgod/42699299/log.gz

=== FAILURES 
===
 57s _ test_async_alive_terminates[asyncio+uvloop] 
__
 57s  57s pyfuncitem = test_async_alive_terminates[asyncio+uvloop]>

 57s  57s @pytest.hookimpl(tryfirst=True)
 57s def pytest_pyfunc_call(pyfuncitem: Any) -> bool | None:
 57s def run_with_hypothesis(**kwargs: Any) -> None:
 57s with get_runner(backend_name, backend_options) as runner:
 57s runner.run_test(original_func, kwargs)
 57s  57s backend = pyfuncitem.funcargs.get("anyio_backend")
 57s if backend:
 57s backend_name, backend_options = 
extract_backend_and_options(backend)

 57s  57s if hasattr(pyfuncitem.obj, "hypothesis"):
 57s # Wrap the inner test function unless it's already 
wrapped

 57s original_func = pyfuncitem.obj.hypothesis.inner_test
 57s if original_func.__qualname__ != 
run_with_hypothesis.__qualname__:

 57s if iscoroutinefunction(original_func):
 57s pyfuncitem.obj.hypothesis.inner_test = 
run_with_hypothesis

 57s  57s return None
 57s  57s if iscoroutinefunction(pyfuncitem.obj):
 57s funcargs = pyfuncitem.funcargs
 57s testargs = {arg: funcargs[arg] for arg in 
pyfuncitem._fixtureinfo.argnames}
 57s >   with get_runner(backend_name, backend_options) as 
runner:
 57s  57s /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:123: 
57s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _  57s /usr/lib/python3.11/contextlib.py:137: in __enter__

 57s return next(self.gen)
 57s /usr/lib/python3/dist-packages/anyio/pytest_plugin.py:45: in 
get_runner

 57s asynclib.create_test_runner(backend_options)
 57s /usr/lib/python3/dist-packages/anyio/_backends/_asyncio.py:2465: 
in create_test_runner

 57s return TestRunner(**options)
 57s _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
_ _ _ _ _ _ _  57s  57s self = object at 0x9513e590>

 57s  57s def __init__(
 57s self,
 57s *,
 57s debug: bool | None = None,
 57s use_uvloop: bool = False,
 57s loop_factory: Callable[[], AbstractEventLoop] | None = None,
 57s ) -> None:
 57s if use_uvloop and loop_factory is None:
 57s >   import uvloop
 57s E   ModuleNotFoundError: No module named 'uvloop'
 57s  57s 
/usr/lib/python3/dist-packages/anyio/_backends/_asyncio.py:1837: 
ModuleNotFoundError
 57s __ test_watch[asyncio+uvloop] 
__
 57s  57s mocker = 0x95199050>

 57s  57s def test_watch(mocker):
 57s class FakeWatcher:
 57s def __init__(self, path):
 57s self._results = iter(
 57s [
 57s {'r1'},
 57s   

Bug#1058571: gnupg2: please enable TPM2 support

[Andreas Metzler]

On 2024-02-03 YunQiang Su  wrote:
> On Wed, 13 Dec 2023 11:17:10 +0800 YunQiang Su  wrote:
>> Package: src:gnupg2
>> Version: 2.4.3-2

>> TPM2 support has been introduced into GnuPG since 2.3.
>> https://gnupg.org/blog/20210315-using-tpm-with-gnupg-2.3.html
>> 
>> While TPM2 support is not enabled for Debian's gnupg2 package
>> in experimental:
[...]
> Hi, Andreas
> I noticed that you have 2 uploads of gnupg 2.4 to experimental in recent days.
> Is there any reason that no enabling TPM2 support?
> Is TPM2 support buggy?

Hello,

I am doing noninvasive minimal changes only, keeping the packaging up to
date with upstream releases.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1062772: apt: apt.conf(5) should document all options

[Thorsten Glaser]

Package: apt
Version: 2.2.4
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de

With “apt-config dump”, one can see lots of options, but they
mostly are not documented, so for example APT::Cmd::Pattern-Only
(which only shows up in Binary::apt:: so even “apt-config dump”
hides some options unless they are used anywhere).

I would expect apt.conf(5) to document any and all configuration
items one can do to apt*, either directly or by other manpages
referenced from “SEE ALSO”.


-- Package-specific info:

-- (no /etc/apt/preferences present) --


-- (/etc/apt/preferences.d/dash-mksh.pref present, but not submitted) --


-- (/etc/apt/preferences.d/ncurses-term-considered-harmful present, but not 
submitted) --


-- (/etc/apt/preferences.d/prevent-apparmor present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-aptitude present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-consolekit present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-drexim present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-networkmanager present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-packagekit present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-policykit present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-pulseaudio present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-puppet present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-ruby present, but not submitted) --


-- (/etc/apt/preferences.d/prevent-systemd-completely present, but not 
submitted) --


-- (/etc/apt/preferences.d/prevent-systemd-installed present, but not 
submitted) --


-- (/etc/apt/preferences.d/prevent-systemd-running present, but not submitted) 
--


-- (/etc/apt/preferences.d/prevent-unattended-upgrades present, but not 
submitted) --


-- (/etc/apt/preferences.d/prevent-usrmove present, but not submitted) --


-- (/etc/apt/preferences.d/systemd present, but not submitted) --


-- (no /etc/apt/sources.list present) --


-- (/etc/apt/sources.list.d/bullseye.list present, but not submitted) --


-- (/etc/apt/sources.list.d/wtf.list present, but not submitted) --


-- System Information:
Debian Release: 11.8
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 
'oldstable-proposed-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-27-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), 
LANGUAGE not set
Shell: /bin/sh linked to /bin/lksh
Init: sysvinit (via /sbin/init)

Versions of packages apt depends on:
ii  adduser 3.118+deb11u1
ii  debian-archive-keyring  2021.1.1+deb11u1
ii  gpgv2.2.27-2+deb11u2
ii  libapt-pkg6.0   2.2.4
ii  libc6   2.31-13+deb11u7
ii  libgcc-s1   10.2.1-6
ii  libgnutls30 3.7.1-5+deb11u4
ii  libseccomp2 2.5.1-1+deb11u1
ii  libstdc++6  10.2.1-6
ii  libsystemd0 247.3-7+deb11u4

Versions of packages apt recommends:
ii  ca-bundle [ca-certificates]  20190604

Versions of packages apt suggests:
pn  apt-doc  
pn  aptitude | synaptic | wajig  
ii  dpkg-dev 1.20.13
ii  gnupg2.2.27-2+deb11u2
ii  gnupg1   1.4.23-1.1
pn  powermgmt-base   

-- Configuration Files:
/etc/cron.daily/apt-compat changed [not included]
/etc/logrotate.d/apt changed [not included]

-- no debconf information

Bug#1062771: rasqal: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: rasqal
Version: 0.9.33-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
rasqal 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 rasqal
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru rasqal-0.9.33/debian/changelog rasqal-0.9.33/debian/changelog
--- rasqal-0.9.33/debian/changelog  2023-02-22 16:42:12.0 +
+++ rasqal-0.9.33/debian/changelog  2024-02-03 04:26:57.0 +
@@ -1,3 +1,10 @@
+rasqal (0.9.33-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Sat, 03 Feb 2024 04:26:57 
+
+
 rasqal (0.9.33-2) unstable; urgency=medium
 
   * QA upload.
diff -Nru rasqal-0.9.33/debian/control rasqal-0.9.33/debian/control
--- rasqal-0.9.33/debian/control2023-02-22 16:41:55.0 +
+++ rasqal-0.9.33/debian/control2024-02-03 04:26:56.0 +
@@ -16,12 +16,15 @@
 Suggests: librasqal3-doc
 Section: libdevel
 Architecture: any
-Depends: librasqal3 (= ${binary:Version}), libraptor2-dev, libgmp-dev, 
${misc:Depends}
+Depends: librasqal3t64 (= ${binary:Version}), libraptor2-dev, libgmp-dev, 
${misc:Depends}
 Description: Rasqal RDF query library development libraries and headers
  Development libraries, header files and documentation needed by
  programs that want to compile with the Rasqal RDF query library.
 
-Package: librasqal3
+Package: librasqal3t64
+Provides: ${t64:Provides}
+Replaces: librasqal3
+Breaks: librasqal3 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
diff -Nru rasqal-0.9.33/debian/librasqal3.docs 
rasqal-0.9.33/debian/librasqal3.docs
--- rasqal-0.9.33/debian/librasqal3.docs2022-05-16 17:13:02.0 
+
+++ rasqal-0.9.33/debian/librasqal3.docs1970-01-01 00:00:00.0 
+
@@ -1,4 +0,0 @@
-README
-NEWS
-AUTHORS
-NOTICE
diff -Nru rasqal-0.9.33/debian/librasqal3.install 
rasqal-0.9.33/debian/librasqal3.install
--- rasqal-0.9.33/debian/librasqal3.install 2022-05-16 17:13:02.0 
+
+++ rasqal-0.9.33/debian/librasqal3.install 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-debian/tmp/usr/lib/*/librasqal.so.*
diff -Nru rasqal-0.9.33/debian/librasqal3.shlibs 
rasqal-0.9.33/debian/librasqal3.shlibs
--- rasqal-0.9.33/debian/librasqal3.shlibs  2022-05-16 17:13:02.0 
+
+++ rasqal-0.9.33/debian/librasqal3.shlibs  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-librasqal 3 librasqal3 (>= 0.9.31)
diff -Nru rasqal-0.9.33/debian/librasqal3t64.docs 
rasqal-0.9.33/debian/librasqal3t64.docs
--- rasqal-0.9.33/debian/librasqal3t64.docs 1970-01-01 00:00:00.0 
+
+++ rasqal-0.9.33/debian/librasqal3t64.docs 2022-05-16 17:13:02.0 
+
@@ -0,0 +1,4 @@
+README
+NEWS
+AUTHORS
+NOTICE
diff -Nru rasqal-0.9.33/debian/librasqal3t64.install 
rasqal-0.9.33/debian/librasqal3t64.install
--- rasqal-0.9.33/debian/librasqal3t64.install  1970-01-01 00:00:00.0 
+
+++ rasqal-0.9.33/debian/librasqal3t64.install  2022-05-16 

Bug#1062769: radare2: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: radare2
Version: 5.5.0+dfsg-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
radare2 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 radare2
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru radare2-5.5.0+dfsg/debian/changelog 
radare2-5.5.0+dfsg/debian/changelog
--- radare2-5.5.0+dfsg/debian/changelog 2021-12-01 11:02:42.0 +
+++ radare2-5.5.0+dfsg/debian/changelog 2024-02-03 04:25:00.0 +
@@ -1,3 +1,10 @@
+radare2 (5.5.0+dfsg-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Sat, 03 Feb 2024 04:25:00 
+
+
 radare2 (5.5.0+dfsg-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru radare2-5.5.0+dfsg/debian/control radare2-5.5.0+dfsg/debian/control
--- radare2-5.5.0+dfsg/debian/control   2021-12-01 11:02:42.0 +
+++ radare2-5.5.0+dfsg/debian/control   2024-02-03 04:25:00.0 +
@@ -42,7 +42,10 @@
  supporting PE, mach0, ELF, class, etc. named rabin, and a block-based
  hash utility called rahash.
 
-Package: libradare2-5.0.0
+Package: libradare2-5.0.0t64
+Provides: ${t64:Provides}
+Replaces: libradare2-5.0.0
+Breaks: libradare2-5.0.0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Pre-Depends: ${misc:Pre-Depends}
@@ -66,7 +69,7 @@
 Package: libradare2-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, libradare2-5.0.0 (= ${binary:Version}),
+Depends: ${misc:Depends}, libradare2-5.0.0t64 (= ${binary:Version}),
  libcapstone-dev, libmagic-dev, libuv1-dev, liblz4-dev,
  libzip-dev,
 Description: devel files from the radare2 suite
diff -Nru radare2-5.5.0+dfsg/debian/libradare2-5.0.0.install 
radare2-5.5.0+dfsg/debian/libradare2-5.0.0.install
--- radare2-5.5.0+dfsg/debian/libradare2-5.0.0.install  2021-12-01 
11:02:42.0 +
+++ radare2-5.5.0+dfsg/debian/libradare2-5.0.0.install  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/*.so.5.*
diff -Nru radare2-5.5.0+dfsg/debian/libradare2-5.0.0.lintian-overrides 
radare2-5.5.0+dfsg/debian/libradare2-5.0.0.lintian-overrides
--- radare2-5.5.0+dfsg/debian/libradare2-5.0.0.lintian-overrides
2021-12-01 11:02:42.0 +
+++ radare2-5.5.0+dfsg/debian/libradare2-5.0.0.lintian-overrides
1970-01-01 00:00:00.0 +
@@ -1,4 +0,0 @@
-# One package is enough for all those libs
-libradare2-5.0.0: package-name-doesnt-match-sonames
-# Every r2 release increases API, so no need to track symbols
-libradare2-5.0.0: no-symbols-control-file
diff -Nru radare2-5.5.0+dfsg/debian/libradare2-5.0.0t64.install 
radare2-5.5.0+dfsg/debian/libradare2-5.0.0t64.install
--- radare2-5.5.0+dfsg/debian/libradare2-5.0.0t64.install   1970-01-01 
00:00:00.0 +
+++ radare2-5.5.0+dfsg/debian/libradare2-5.0.0t64.install   2021-12-01 
11:02:42.0 +
@@ -0,0 +1 @@
+usr/lib/*/*.so.5.*
diff -Nru radare2-5.5.0+dfsg/debian/libradare2-5.0.0t64.lintian-overrides 

Bug#1062770: raft: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: raft
Version: 0.20.0-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
raft 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 raft
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru raft-0.20.0/debian/changelog raft-0.20.0/debian/changelog
--- raft-0.20.0/debian/changelog2024-01-27 14:08:31.0 +
+++ raft-0.20.0/debian/changelog2024-02-03 04:26:22.0 +
@@ -1,3 +1,10 @@
+raft (0.20.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Sat, 03 Feb 2024 04:26:22 
+
+
 raft (0.20.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru raft-0.20.0/debian/control raft-0.20.0/debian/control
--- raft-0.20.0/debian/control  2024-01-27 14:05:52.0 +
+++ raft-0.20.0/debian/control  2024-02-03 04:26:22.0 +
@@ -11,7 +11,10 @@
 Vcs-Git: https://salsa.debian.org/cowsql-team/raft.git
 Homepage: https://raft.readthedocs.io/en/latest/
 
-Package: libraft0
+Package: libraft0t64
+Provides: ${t64:Provides}
+Replaces: libraft0
+Breaks: libraft0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -32,7 +35,7 @@
 Package: libraft-dev
 Section: libdevel
 Architecture: any
-Depends: libraft0 (= ${binary:Version}), ${misc:Depends}
+Depends: libraft0t64 (= ${binary:Version}), ${misc:Depends}
 Multi-Arch: same
 Description: Raft Consensus protocol implementation - development files
  Fully asynchronous C implementation of the Raft consensus protocol.
diff -Nru raft-0.20.0/debian/libraft0.install 
raft-0.20.0/debian/libraft0.install
--- raft-0.20.0/debian/libraft0.install 2024-01-27 14:05:52.0 +
+++ raft-0.20.0/debian/libraft0.install 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libraft*.so.*
diff -Nru raft-0.20.0/debian/libraft0.symbols 
raft-0.20.0/debian/libraft0.symbols
--- raft-0.20.0/debian/libraft0.symbols 2024-01-27 14:05:52.0 +
+++ raft-0.20.0/debian/libraft0.symbols 1970-01-01 00:00:00.0 +
@@ -1,110 +0,0 @@
-libraft.so.0 libraft0 #MINVER#
-* Build-Depends-Package: libraft-dev
- raft_add@Base 0.17.7
- raft_aligned_alloc@Base 0.17.7
- raft_aligned_free@Base 0.17.7
- raft_apply@Base 0.17.7
- raft_assign@Base 0.17.7
- raft_barrier@Base 0.17.7
- raft_bootstrap@Base 0.17.7
- raft_calloc@Base 0.17.7
- raft_catch_up@Base 0.19.0-1
- raft_close@Base 0.17.7
- raft_commit_index@Base 0.19.0-1
- raft_configuration_add@Base 0.17.7
- raft_configuration_close@Base 0.17.7
- raft_configuration_encode@Base 0.17.7
- raft_configuration_init@Base 0.17.7
- raft_current_term@Base 0.19.0-1
- raft_digest@Base 0.17.7
- raft_errmsg@Base 0.17.7
- raft_fixture_add_entry@Base 0.17.7
- raft_fixture_alive@Base 0.17.7
- raft_fixture_bootstrap@Base 0.17.7
- raft_fixture_close@Base 0.17.7
- raft_fixture_configuration@Base 0.17.7
- raft_fixture_depose@Base 0.17.7
- raft_fixture_desaturate@Base 0.17.7
- raft_fixture_disconnect@Base 0.17.7
- raft_fixture_elect@Base 0.17.7

Bug#1062768: qxmpp: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qxmpp
Version: 1.5.5-0.3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qxmpp 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 qxmpp
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qxmpp-1.5.5/debian/changelog qxmpp-1.5.5/debian/changelog
--- qxmpp-1.5.5/debian/changelog2023-11-17 08:36:15.0 +
+++ qxmpp-1.5.5/debian/changelog2024-02-03 04:23:32.0 +
@@ -1,3 +1,10 @@
+qxmpp (1.5.5-0.4) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Sat, 03 Feb 2024 04:23:32 
+
+
 qxmpp (1.5.5-0.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru qxmpp-1.5.5/debian/control qxmpp-1.5.5/debian/control
--- qxmpp-1.5.5/debian/control  2023-11-12 08:08:22.0 +
+++ qxmpp-1.5.5/debian/control  2024-02-03 04:23:32.0 +
@@ -18,10 +18,11 @@
 Vcs-Git: https://salsa.debian.org/xmpp-team/qxmpp.git
 Vcs-Browser: https://salsa.debian.org/xmpp-team/qxmpp
 
-Package: libqxmppqt5-4
+Package: libqxmppqt5-4t64
+Provides: ${t64:Provides}
 Architecture: any
-Replaces: libqxmpp0, libqxmpp1, libqxmpp2
-Breaks: libqxmpp0, libqxmpp1, libqxmpp2
+Replaces: libqxmppqt5-4, libqxmpp0, libqxmpp1, libqxmpp2
+Breaks: libqxmppqt5-4 (<< ${source:Version}), libqxmpp0, libqxmpp1, libqxmpp2
 Depends: gstreamer1.0-plugins-base,
  gstreamer1.0-plugins-good,
  gstreamer1.0-plugins-ugly,
@@ -34,7 +35,10 @@
  .
  This package contains the shared library.
 
-Package: libqxmppomemoqt5-4
+Package: libqxmppomemoqt5-4t64
+Provides: ${t64:Provides}
+Replaces: libqxmppomemoqt5-4
+Breaks: libqxmppomemoqt5-4 (<< ${source:Version})
 Architecture: any
 Depends: ${misc:Depends},
  ${shlibs:Depends}
@@ -49,8 +53,8 @@
 Section: libdevel
 Architecture: any
 Depends: libgstreamer1.0-dev,
- libqxmppomemoqt5-4 (= ${binary:Version}),
- libqxmppqt5-4 (= ${binary:Version}),
+ libqxmppomemoqt5-4t64 (= ${binary:Version}),
+ libqxmppqt5-4t64 (= ${binary:Version}),
  qtbase5-dev,
  ${misc:Depends}
 Breaks: libqxmpp-dev (<< 1.5.5-0.1~exp1~),
diff -Nru qxmpp-1.5.5/debian/libqxmppomemoqt5-4.install 
qxmpp-1.5.5/debian/libqxmppomemoqt5-4.install
--- qxmpp-1.5.5/debian/libqxmppomemoqt5-4.install   2023-11-12 
07:35:41.0 +
+++ qxmpp-1.5.5/debian/libqxmppomemoqt5-4.install   1970-01-01 
00:00:00.0 +
@@ -1,2 +0,0 @@
-usr/lib/*/libQXmppOmemoQt5.so.1.*
-usr/lib/*/libQXmppOmemoQt5.so.4
diff -Nru qxmpp-1.5.5/debian/libqxmppomemoqt5-4t64.install 
qxmpp-1.5.5/debian/libqxmppomemoqt5-4t64.install
--- qxmpp-1.5.5/debian/libqxmppomemoqt5-4t64.install1970-01-01 
00:00:00.0 +
+++ qxmpp-1.5.5/debian/libqxmppomemoqt5-4t64.install2023-11-12 
07:35:41.0 +
@@ -0,0 +1,2 @@
+usr/lib/*/libQXmppOmemoQt5.so.1.*
+usr/lib/*/libQXmppOmemoQt5.so.4
diff -Nru qxmpp-1.5.5/debian/libqxmppomemoqt5-4t64.lintian-overrides 
qxmpp-1.5.5/debian/libqxmppomemoqt5-4t64.lintian-overrides
--- 

Bug#1062767: quickfix: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: quickfix
Version: 1.15.1+dfsg-4
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
quickfix 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 quickfix
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru quickfix-1.15.1+dfsg/debian/changelog 
quickfix-1.15.1+dfsg/debian/changelog
--- quickfix-1.15.1+dfsg/debian/changelog   2020-04-29 19:41:30.0 
+
+++ quickfix-1.15.1+dfsg/debian/changelog   2024-02-03 04:20:42.0 
+
@@ -1,3 +1,10 @@
+quickfix (1.15.1+dfsg-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Sat, 03 Feb 2024 04:20:42 
+
+
 quickfix (1.15.1+dfsg-4) unstable; urgency=medium
 
   * Use --with-openssl option when building (Closes: #959132)
diff -Nru quickfix-1.15.1+dfsg/debian/control 
quickfix-1.15.1+dfsg/debian/control
--- quickfix-1.15.1+dfsg/debian/control 2020-04-29 19:41:30.0 +
+++ quickfix-1.15.1+dfsg/debian/control 2024-02-03 04:20:42.0 +
@@ -23,7 +23,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libquickfix17 (= ${binary:Version}),
+Depends: libquickfix17t64 (= ${binary:Version}),
  libxml2-dev,
  libssl-dev,
  ${misc:Depends}
@@ -36,7 +36,10 @@
  .
  This package includes the quickfix development files.
 
-Package: libquickfix17
+Package: libquickfix17t64
+Provides: ${t64:Provides}
+Replaces: libquickfix17
+Breaks: libquickfix17 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends},
diff -Nru quickfix-1.15.1+dfsg/debian/libquickfix17.dirs 
quickfix-1.15.1+dfsg/debian/libquickfix17.dirs
--- quickfix-1.15.1+dfsg/debian/libquickfix17.dirs  2020-04-29 
19:41:30.0 +
+++ quickfix-1.15.1+dfsg/debian/libquickfix17.dirs  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib
diff -Nru quickfix-1.15.1+dfsg/debian/libquickfix17.docs 
quickfix-1.15.1+dfsg/debian/libquickfix17.docs
--- quickfix-1.15.1+dfsg/debian/libquickfix17.docs  2020-04-29 
19:41:30.0 +
+++ quickfix-1.15.1+dfsg/debian/libquickfix17.docs  1970-01-01 
00:00:00.0 +
@@ -1,2 +0,0 @@
-NEWS
-ChangeLog
diff -Nru quickfix-1.15.1+dfsg/debian/libquickfix17.install 
quickfix-1.15.1+dfsg/debian/libquickfix17.install
--- quickfix-1.15.1+dfsg/debian/libquickfix17.install   2020-04-29 
19:41:30.0 +
+++ quickfix-1.15.1+dfsg/debian/libquickfix17.install   1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libquickfix.so.*
diff -Nru quickfix-1.15.1+dfsg/debian/libquickfix17t64.dirs 
quickfix-1.15.1+dfsg/debian/libquickfix17t64.dirs
--- quickfix-1.15.1+dfsg/debian/libquickfix17t64.dirs   1970-01-01 
00:00:00.0 +
+++ quickfix-1.15.1+dfsg/debian/libquickfix17t64.dirs   2020-04-29 
19:41:30.0 +
@@ -0,0 +1 @@
+usr/lib
diff -Nru quickfix-1.15.1+dfsg/debian/libquickfix17t64.docs 
quickfix-1.15.1+dfsg/debian/libquickfix17t64.docs
--- quickfix-1.15.1+dfsg/debian/libquickfix17t64.docs   1970-01-01 
00:00:00.0 +
+++ 

Bug#1062765: ITP: mailctl -- IMAP/SMTP clients with the capabilities of renewal and authorization of OAuth2 credentials

[陳昌倬]

Package: wnpp
Severity: wishlist
Owner: ChangZhuo Chen (陳昌倬) 
X-Debbugs-Cc: debian-de...@lists.debian.org

* Package name: mailctl
  Version : 0.9.2
  Upstream Contact: Peter Dobsan
* URL : https://github.com/pdobsan/mailctl
* License : BSD-3-Clause
  Programming Lang: Haskell
  Description : IMAP/SMTP clients with the capabilities of renewal and 
authorization of OAuth2 credentials


 mailctl provides IMAP/SMTP clients with the capabilities of renewal and
 authorization of OAuth2 credentials.

 The Oauth2 credentials are kept in the Gnome keyring or in GNU PG
 encrypted files.

 Many IMAP/SMTP clients, like msmtp, fdm, isync, neomutt or mutt can use
 OAuth2 access tokens but lack the ability to renew and/or authorize
 OAuth2 credentials. The purpose of mailctl is to provide these missing
 capabilities by acting as a kind of smart password manager. In
 particular, access token renewal happens automatically in the
 background transparent to the user.


The package will be maintained under the umbrella of the Debian Haskell
team.


-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1062762: qtsystems-opensource-src: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qtsystems-opensource-src
Version: 5.0~git20190103.e3332ee+dfsg1-5
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qtsystems-opensource-src 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 
qtsystems-opensource-src
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru 
qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/changelog 
qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/changelog
--- qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/changelog 
2023-01-07 20:02:19.0 +
+++ qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/changelog 
2024-02-03 03:16:01.0 +
@@ -1,3 +1,10 @@
+qtsystems-opensource-src (5.0~git20190103.e3332ee+dfsg1-5.1) experimental; 
urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Sat, 03 Feb 2024 03:16:01 
+
+
 qtsystems-opensource-src (5.0~git20190103.e3332ee+dfsg1-5) unstable; 
urgency=medium
 
   * debian/control: 
diff -Nru qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/control 
qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/control
--- qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/control   
2023-01-07 20:02:19.0 +
+++ qtsystems-opensource-src-5.0~git20190103.e3332ee+dfsg1/debian/control   
2024-02-03 03:16:00.0 +
@@ -23,7 +23,10 @@
 Vcs-Git: https://salsa.debian.org/qt-kde-team/qt/qtsystems.git
 Vcs-Browser: https://salsa.debian.org/qt-kde-team/qt/qtsystems/
 
-Package: libqt5serviceframework5
+Package: libqt5serviceframework5t64
+Provides: ${t64:Provides}
+Replaces: libqt5serviceframework5
+Breaks: libqt5serviceframework5 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends},
@@ -55,7 +58,10 @@
  snapshot of an ongoing development. The package is very likely to
  change in a binary incompatible way, and no guarantees are given.
 
-Package: libqt5publishsubscribe5
+Package: libqt5publishsubscribe5t64
+Provides: ${t64:Provides}
+Replaces: libqt5publishsubscribe5
+Breaks: libqt5publishsubscribe5 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends},
@@ -87,7 +93,10 @@
  snapshot of an ongoing development. The package is very likely to
  change in a binary incompatible way, and no guarantees are given.
 
-Package: libqt5systeminfo5
+Package: libqt5systeminfo5t64
+Provides: ${t64:Provides}
+Replaces: libqt5systeminfo5
+Breaks: libqt5systeminfo5 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends},
@@ -122,9 +131,9 @@
 Package: qtsystems5-dev
 Section: libdevel
 Architecture: any
-Depends: libqt5publishsubscribe5 (= ${binary:Version}),
- libqt5serviceframework5 (= ${binary:Version}),
- libqt5systeminfo5 (= ${binary:Version}),
+Depends: libqt5publishsubscribe5t64 (= ${binary:Version}),
+ libqt5serviceframework5t64 (= ${binary:Version}),
+ libqt5systeminfo5t64 (= 

Bug#1058571: gnupg2: please enable TPM2 support

[YunQiang Su]

On Wed, 13 Dec 2023 11:17:10 +0800 YunQiang Su  wrote:
> Package: src:gnupg2
> Version: 2.4.3-2
> 
> TPM2 support has been introduced into GnuPG since 2.3.
> https://gnupg.org/blog/20210315-using-tpm-with-gnupg-2.3.html
> 
> While TPM2 support is not enabled for Debian's gnupg2 package
> in experimental:
> 
> https://buildd.debian.org/status/fetch.php?pkg=gnupg2=i386=2.4.3-2=1695644413=0
> 
> TPM:   no
> 
>

Hi, Andreas
I noticed that you have 2 uploads of gnupg 2.4 to experimental in recent days.
Is there any reason that no enabling TPM2 support?
Is TPM2 support buggy?

Bug#1062756: cryptsetup-initramfs: cryptkeyctl script fails to discover decrypt_keyctl even when present

[debian . 627of]

That does indeed seem to be the case. 

It appears that my distro activated a temporary directory override recently, 
and I already had /tmp mounted as NOEXEC.

Bug report for my distro for anyone that comes across this:
https://github.com/Kicksecure/security-misc/issues/198

Thank you



On Friday, February 2nd, 2024 at 7:39 PM, Guilhem Moulin - guilhem at 
debian.org  wrote:

> 
> 
> Control: tag -1 moreinfo
> 
> Hi,
> 
> On Fri, 02 Feb 2024 at 18:44:43 -0500, abrasamji wrote:
> 
> > update-initramfs log excerpt with set -x:
> > 
> > Calling hook cryptkeyctl
> > + PREREQ=cryptroot
> > + . /usr/share/initramfs-tools/hook-functions
> > + [ ! -x 
> > /tmp/user/0/mkinitramfs_LhQz6c/lib/cryptsetup/scripts/decrypt_keyctl ]
> > + exit 0
> > 
> > A check with ls -la while update-initramfs was running, prior to
> > cryptkeyctl being executed, in order to prove it's presence:
> > 
> > /tmp/user/0/mkinitramfs_LhQz6c/usr/lib/cryptsetup/scripts:
> > total 4
> > drwxr-xr-x 2 root root 60 Feb 2 17:44 .
> > drwxr-xr-x 3 root root 100 Feb 2 17:44 ..
> > -rwxr-xr-x 1 root root 2042 Apr 20 2023 decrypt_keyctl
> > 
> > I changed the '-x' flag in the if statement to a '-s' flag. This fixed
> > it and I don't know why, and I don't know if its a bug in initramfs,
> > dash, or cryptsetup or something else.
> 
> 
> Seems like your update-initramfs is running under TMPDIR=/tmp/user/0, is
> is perhaps mounted with the ‘noexec’ flag set?
> 
> That would cause `test -x` to fail on an existing path with the exec bit
> set, and per mkinitramfs(8) this not supported:
> 
> ENVIRONMENT
> 
> mkinitramfs honours the TMPDIR environment variable. If set, it
> uses subdirectories in the given directory to create its
> temporary working directories. Else it uses /var/tmp as default
> value for that purpose. The given directory should be on a
> filesystem which allows the execution of files stored there, i.e.
> should not be mounted with the noexec mount option.
> 
> --
> Guilhem.

Bug#1062761: transition: libfm-qt

[陳昌倬]

Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
X-Debbugs-Cc: libfm...@packages.debian.org
Control: affects -1 + src:libfm-qt

libfm-qt has bumped its soversion from 13 to 14, so we need a
transition.

All affected packages listed in 
https://release.debian.org/transitions/html/auto-libfm-qt.html
are good in experimental.


Ben file:

title = "libfm-qt";
is_affected = .depends ~ "libfm-qt13" | .depends ~ "libfm-qt14";
is_good = .depends ~ "libfm-qt14";
is_bad = .depends ~ "libfm-qt13";

-- 
ChangZhuo Chen (陳昌倬) czchen@{czchen,debian}.org
Key fingerprint = BA04 346D C2E1 FE63 C790  8793 CC65 B0CD EC27 5D5B


signature.asc
Description: PGP signature

Bug#1062756: cryptsetup-initramfs: cryptkeyctl script fails to discover decrypt_keyctl even when present

[Guilhem Moulin]

Control: tag -1 moreinfo

Hi,

On Fri, 02 Feb 2024 at 18:44:43 -0500, abrasamji wrote:
> update-initramfs log excerpt with set -x:
>
> Calling hook cryptkeyctl
> + PREREQ=cryptroot
> + . /usr/share/initramfs-tools/hook-functions
> + [ ! -x /tmp/user/0/mkinitramfs_LhQz6c/lib/cryptsetup/scripts/decrypt_keyctl 
> ]
> + exit 0
>
> A check with ls -la while update-initramfs was running, prior to
> cryptkeyctl being executed, in order to prove it's presence:
>
> /tmp/user/0/mkinitramfs_LhQz6c/usr/lib/cryptsetup/scripts:
> total 4
> drwxr-xr-x 2 root root   60 Feb  2 17:44 .
> drwxr-xr-x 3 root root  100 Feb  2 17:44 ..
> -rwxr-xr-x 1 root root 2042 Apr 20  2023 decrypt_keyctl
>
> I changed the '-x' flag in the if statement to a '-s' flag. This fixed
> it and I don't know why, and I don't know if its a bug in initramfs,
> dash, or cryptsetup or something else.

Seems like your update-initramfs is running under TMPDIR=/tmp/user/0, is
is perhaps mounted with the ‘noexec’ flag set?

That would cause `test -x` to fail on an existing path with the exec bit
set, and per mkinitramfs(8) this not supported:

  ENVIRONMENT

   mkinitramfs honours the TMPDIR environment variable. If set, it
   uses subdirectories in the given directory to create its
   temporary working directories.  Else it uses /var/tmp as default
   value for that purpose.  The given directory should be on a
   filesystem which allows the execution of files stored there, i.e.
   should not be mounted with the noexec mount option.

-- 
Guilhem.


signature.asc
Description: PGP signature

Bug#1062756: cryptsetup-initramfs: cryptkeyctl script fails to discover decrypt_keyctl even when present

[debian . 627of]

In case anyone else is having this issue, error appears to the end user as:

decrypt_keyctl: empty input from stdin
keyctl: command not found

Cryptsetup then gives an error about the password being incorrect.

Bug#1062760: qtquickcontrols2-opensource-src: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qtquickcontrols2-opensource-src
Version: 5.15.10+dfsg-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qtquickcontrols2-opensource-src 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 
qtquickcontrols2-opensource-src
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/changelog 
qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/changelog
--- qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/changelog   
2023-07-08 08:03:59.0 +
+++ qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/changelog   
2024-02-02 23:56:09.0 +
@@ -1,3 +1,10 @@
+qtquickcontrols2-opensource-src (5.15.10+dfsg-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 23:56:09 
+
+
 qtquickcontrols2-opensource-src (5.15.10+dfsg-2) unstable; urgency=medium
 
   * Upload to unstable.
diff -Nru qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/control 
qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/control
--- qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/control 2023-07-08 
08:03:59.0 +
+++ qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/control 2024-02-02 
23:56:09.0 +
@@ -31,7 +31,10 @@
 Vcs-Git: https://salsa.debian.org/qt-kde-team/qt/qtquickcontrols2.git
 Vcs-Browser: https://salsa.debian.org/qt-kde-team/qt/qtquickcontrols2
 
-Package: libqt5quickcontrols2-5
+Package: libqt5quickcontrols2-5t64
+Provides: ${t64:Provides}
+Replaces: libqt5quickcontrols2-5
+Breaks: libqt5quickcontrols2-5 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -41,7 +44,10 @@
  .
  This package contains the Qt 5 Quick Controls 2 library.
 
-Package: libqt5quicktemplates2-5
+Package: libqt5quicktemplates2-5t64
+Provides: ${t64:Provides}
+Replaces: libqt5quicktemplates2-5
+Breaks: libqt5quicktemplates2-5 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -98,8 +104,8 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libqt5quickcontrols2-5 (= ${binary:Version}),
- libqt5quicktemplates2-5 (= ${binary:Version}),
+Depends: libqt5quickcontrols2-5t64 (= ${binary:Version}),
+ libqt5quicktemplates2-5t64 (= ${binary:Version}),
  ${misc:Depends}
 Description: Qt 5 Quick Controls 2 development files
  Qt is a cross-platform C++ application framework. Qt's primary feature
diff -Nru 
qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/libqt5quickcontrols2-5.install
 
qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/libqt5quickcontrols2-5.install
--- 
qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/libqt5quickcontrols2-5.install
  2023-07-08 08:03:59.0 +
+++ 
qtquickcontrols2-opensource-src-5.15.10+dfsg/debian/libqt5quickcontrols2-5.install
  1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@

Bug#1062759: qt6-websockets: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qt6-websockets
Version: 6.4.2-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qt6-websockets 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 qt6-websockets
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qt6-websockets-6.4.2/debian/changelog 
qt6-websockets-6.4.2/debian/changelog
--- qt6-websockets-6.4.2/debian/changelog   2023-07-25 18:29:09.0 
+
+++ qt6-websockets-6.4.2/debian/changelog   2024-02-02 23:55:25.0 
+
@@ -1,3 +1,10 @@
+qt6-websockets (6.4.2-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 23:55:25 
+
+
 qt6-websockets (6.4.2-3) unstable; urgency=medium
 
   * Team upload to unstable.
diff -Nru qt6-websockets-6.4.2/debian/control 
qt6-websockets-6.4.2/debian/control
--- qt6-websockets-6.4.2/debian/control 2023-07-25 16:11:17.0 +
+++ qt6-websockets-6.4.2/debian/control 2024-02-02 23:55:25.0 +
@@ -26,8 +26,10 @@
 Vcs-Git: https://salsa.debian.org/qt-kde-team/qt6/qt6-websockets.git
 Rules-Requires-Root: no
 
-Package: libqt6websockets6
-Provides: qt6-websockets-abi (= 6.4.2),
+Package: libqt6websockets6t64
+Replaces: libqt6websockets6
+Breaks: libqt6websockets6 (<< ${source:Version})
+Provides: ${t64:Provides}, qt6-websockets-abi (= 6.4.2),
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends},
@@ -55,7 +57,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libqt6websockets6 (= ${binary:Version}), qt6-base-dev, 
${misc:Depends},
+Depends: libqt6websockets6t64 (= ${binary:Version}), qt6-base-dev, 
${misc:Depends},
 Breaks: libqt6websockets6-dev (<< 6.4.0-2~),
 Replaces: libqt6websockets6-dev (<< 6.4.0-2~),
 Description: Qt 6 WebSockets library - development files
diff -Nru qt6-websockets-6.4.2/debian/libqt6websockets6.install 
qt6-websockets-6.4.2/debian/libqt6websockets6.install
--- qt6-websockets-6.4.2/debian/libqt6websockets6.install   2022-09-06 
19:59:32.0 +
+++ qt6-websockets-6.4.2/debian/libqt6websockets6.install   1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/${DEB_HOST_MULTIARCH}/libQt6WebSockets.so.*
diff -Nru qt6-websockets-6.4.2/debian/libqt6websockets6.symbols 
qt6-websockets-6.4.2/debian/libqt6websockets6.symbols
--- qt6-websockets-6.4.2/debian/libqt6websockets6.symbols   2023-01-02 
12:39:15.0 +
+++ qt6-websockets-6.4.2/debian/libqt6websockets6.symbols   1970-01-01 
00:00:00.0 +
@@ -1,174 +0,0 @@
-# SymbolsHelper-Confirmed: 6.4.0 amd64
-libQt6WebSockets.so.6 libqt6websockets6 #MINVER#, qt6-websockets-abi (= 6.4.2)
-* Build-Depends-Package: libqt6websockets6-dev
- _ZN10QWebSocket11qt_metacallEN11QMetaObject4CallEiPPv@Base 6.2.1
- _ZN10QWebSocket11qt_metacastEPKc@Base 6.2.1
- _ZN10QWebSocket12aboutToCloseEv@Base 6.2.1
- _ZN10QWebSocket12bytesWrittenEx@Base 6.2.1
- _ZN10QWebSocket12disconnectedEv@Base 6.2.1
- _ZN10QWebSocket12setPauseModeE6QFlagsIN15QAbstractSocket9PauseModeEE@Base 

Bug#1062757: odil: NMU diff for 64-bit time_t transition

[Lucas Kanashiro]

Source: odil
Version: 0.12.2-4
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
odil 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 odil
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')
Architecture: amd64 (x86_64)

Kernel: Linux 6.2.0-39-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, 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)
diff -Nru odil-0.12.2/debian/changelog odil-0.12.2/debian/changelog
--- odil-0.12.2/debian/changelog2023-12-21 16:12:20.0 -0300
+++ odil-0.12.2/debian/changelog2024-02-02 16:41:40.0 -0300
@@ -1,3 +1,10 @@
+odil (0.12.2-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas   Fri, 02 Feb 2024 16:41:40 -0300
+
 odil (0.12.2-4) unstable; urgency=medium
 
   * Team upload.
diff -Nru odil-0.12.2/debian/control odil-0.12.2/debian/control
--- odil-0.12.2/debian/control  2023-12-21 16:12:20.0 -0300
+++ odil-0.12.2/debian/control  2024-02-02 16:41:40.0 -0300
@@ -5,7 +5,7 @@
 Testsuite: autopkgtest-pkg-python
 Priority: optional
 Build-Depends: debhelper-compat (= 13),
-   d-shlibs,
+   d-shlibs (>= 0.106),
dh-python,
cmake,
pkg-config,
@@ -34,15 +34,15 @@
 Homepage: https://github.com/lamyj/odil
 Rules-Requires-Root: no
 
-Package: libodil0
+Package: libodil0t64
 Architecture: amd64 arm64 armel armhf i386 loong64 mipsel ppc64el s390x alpha 
ia64 powerpc ppc64 riscv64 x32
 Multi-Arch: same
 Section: libs
 Depends: ${shlibs:Depends},
  ${misc:Depends}
-Conflicts: libdcmtkpp0
-Provides: libdcmtkpp0
-Replaces: libdcmtkpp0
+Conflicts: libodil0 (<< ${source:Version}), libdcmtkpp0 
+Provides: ${t64:Provides}, libdcmtkpp0
+Replaces: libodil0, libdcmtkpp0
 Description: C++11 library for the DICOM standard
  Odil leverages C++ constructs to provide a user-friendly API of the
  different parts of the DICOM standard. Included in Odil are exception-based
@@ -58,7 +58,7 @@
 Architecture: amd64 arm64 armel armhf i386 loong64 mipsel ppc64el s390x
 Multi-Arch: same
 Section: libdevel
-Depends: libodil0 (= ${binary:Version}),
+Depends: libodil0t64 (= ${binary:Version}),
  ${devlibs:Depends},
  ${misc:Depends}
 Conflicts: libdcmtkpp-dev
@@ -97,7 +97,7 @@
 Architecture: amd64 arm64 armel armhf i386 loong64 mipsel ppc64el s390x
 Multi-Arch: foreign
 Section: python
-Depends: libodil0 (= ${binary:Version}),
+Depends: libodil0t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${python3:Depends},
  ${misc:Depends}
diff -Nru odil-0.12.2/debian/libodil0t64.lintian-overrides 
odil-0.12.2/debian/libodil0t64.lintian-overrides
--- odil-0.12.2/debian/libodil0t64.lintian-overrides1969-12-31 
21:00:00.0 -0300
+++ odil-0.12.2/debian/libodil0t64.lintian-overrides2024-02-02 
16:41:40.0 -0300
@@ -0,0 +1 @@
+libodil0t64: package-name-doesnt-match-sonames libodil0
diff -Nru odil-0.12.2/debian/rules odil-0.12.2/debian/rules
--- odil-0.12.2/debian/rules2023-12-21 16:12:20.0 -0300
+++ odil-0.12.2/debian/rules2024-02-02 16:41:40.0 -0300
@@ -102,6 +102,7 @@
 

Bug#1062756: cryptsetup-initramfs: cryptkeyctl script fails to discover decrypt_keyctl even when present

[abrasamji]

Package: cryptsetup-initramfs
Version: 2:2.6.1-4~deb12u1
Severity: important
X-Debbugs-Cc: debian.62...@simplelogin.com

Dear Maintainer,


Not sure what is happening here, but the 
/usr/share/initramfs-tools/hooks/cryptkeyctl script is no longer properly 
finding decrypt_keyctl in the initramfs temp file during initramfs build.

This script is meant to be called for usage with decrypt_keyctl in 
/etc/crypttab, a script to automatically pass the password of one LUKS volume 
to another during bootup. This script is provided by cryptsetup.
The consequence of this error is a failure to unlock any disks at boot-time 
that uses the decrypt_keyctl keyscript, and a failure to boot if the device is 
a root device or otherwise needed to boot.

update-initramfs log excerpt with set -x:

Calling hook cryptkeyctl
+ PREREQ=cryptroot
+ . /usr/share/initramfs-tools/hook-functions
+ [ ! -x /tmp/user/0/mkinitramfs_LhQz6c/lib/cryptsetup/scripts/decrypt_keyctl ]
+ exit 0


A check with ls -la while update-initramfs was running, prior to cryptkeyctl 
being executed, in order to prove it's presence:

/tmp/user/0/mkinitramfs_LhQz6c/usr/lib/cryptsetup/scripts:
total 4
drwxr-xr-x 2 root root   60 Feb  2 17:44 .
drwxr-xr-x 3 root root  100 Feb  2 17:44 ..
-rwxr-xr-x 1 root root 2042 Apr 20  2023 decrypt_keyctl



I changed the '-x' flag in the if statement to a '-s' flag. This fixed it and I 
don't know why, and I don't know if its a bug in initramfs, dash, or cryptsetup 
or something else.


Functioning code with the -s in the cryptkeyctl hook:

if  [ ! -s "$DESTDIR/lib/cryptsetup/scripts/decrypt_keyctl" ]; then
exit 0
fi

Thank you for your time.

-- Package-specific info:

-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable'), (100, 'bookworm-fasttrack')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.5-hardened1-stripes-1-s-3.32 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND, TAINT_RANDSTRUCT
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cryptsetup-initramfs depends on:
ii  busybox 1:1.35.0-4+b3
ii  cryptsetup  2:2.6.1-4~deb12u1
ii  debconf [debconf-2.0]   1.5.82
ii  initramfs-tools [linux-initramfs-tool]  0.142

Versions of packages cryptsetup-initramfs recommends:
ii  console-setup  1.221
ii  kbd2.5.1-1+b1

Version of dash

ii  dash  0.5.12-2

cryptsetup-initramfs suggests no packages.

-- debconf information excluded

Bug#1062754: lirc: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: lirc
Version: 0.10.2-0.5
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
lirc 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 lirc
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)
diff -Nru lirc-0.10.2/debian/changelog lirc-0.10.2/debian/changelog
--- lirc-0.10.2/debian/changelog2024-01-17 13:21:20.0 +
+++ lirc-0.10.2/debian/changelog2024-02-02 23:17:23.0 +
@@ -1,3 +1,10 @@
+lirc (0.10.2-0.6) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 23:17:23 +
+
 lirc (0.10.2-0.5) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru lirc-0.10.2/debian/control lirc-0.10.2/debian/control
--- lirc-0.10.2/debian/control  2024-01-17 13:21:18.0 +
+++ lirc-0.10.2/debian/control  2024-02-02 23:17:23.0 +
@@ -39,7 +39,7 @@
 Package: lirc
 Architecture: any
 Depends:
- liblirc0 (= ${binary:Version}),
+ liblirc0t64 (= ${binary:Version}),
  python3,
  ${misc:Depends},
  ${python3:Depends},
@@ -75,7 +75,10 @@
  This package provides the documentation including manual, manpages and
  the public website.
 
-Package: liblirc0
+Package: liblirc0t64
+Provides: ${t64:Provides}
+Replaces: liblirc0
+Breaks: liblirc0 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -95,8 +98,8 @@
 Section: libdevel
 #Provides: liblircclient-dev
 Depends:
- liblirc0 (= ${binary:Version}),
- liblirc-client0 (= ${binary:Version}),
+ liblirc0t64 (= ${binary:Version}),
+ liblirc-client0t64 (= ${binary:Version}),
  ${misc:Depends}
 Description: Infra-red remote control support - development files
  LIRC stands for 'Linux Infra-red Remote Control'.
@@ -106,7 +109,10 @@
  software. See the User Space Driver API and  Lirc Client API sections
  in the lirc manual available in lirc-doc.
 
-Package: liblirc-client0
+Package: liblirc-client0t64
+Provides: ${t64:Provides}
+Replaces: liblirc-client0
+Breaks: liblirc-client0 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Section: libs
@@ -121,7 +127,7 @@
 Package: lirc-x
 Architecture: any
 Depends:
- liblirc0 (= ${binary:Version}),
+ liblirc0t64 (= ${binary:Version}),
  lirc (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends}
diff -Nru lirc-0.10.2/debian/liblirc-client0.install 
lirc-0.10.2/debian/liblirc-client0.install
--- lirc-0.10.2/debian/liblirc-client0.install  2024-01-02 17:18:12.0 
+
+++ lirc-0.10.2/debian/liblirc-client0.install  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-debian/tmp/usr/lib/*/liblirc_client.so.*
diff -Nru lirc-0.10.2/debian/liblirc-client0t64.install 
lirc-0.10.2/debian/liblirc-client0t64.install
--- lirc-0.10.2/debian/liblirc-client0t64.install   1970-01-01 
00:00:00.0 +
+++ lirc-0.10.2/debian/liblirc-client0t64.install   2024-01-02 
17:18:12.0 +
@@ -0,0 +1 @@
+debian/tmp/usr/lib/*/liblirc_client.so.*
diff -Nru 

Bug#1062753: linux-atm: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: linux-atm
Version: 1:2.5.1-5
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
linux-atm 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 linux-atm
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)
diff -Nru linux-atm-2.5.1/debian/changelog linux-atm-2.5.1/debian/changelog
--- linux-atm-2.5.1/debian/changelog2023-12-20 21:41:15.0 +
+++ linux-atm-2.5.1/debian/changelog2024-02-02 23:14:33.0 +
@@ -1,3 +1,10 @@
+linux-atm (1:2.5.1-5.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 23:14:33 +
+
 linux-atm (1:2.5.1-5) unstable; urgency=medium
 
   * QA upload.
diff -Nru linux-atm-2.5.1/debian/control linux-atm-2.5.1/debian/control
--- linux-atm-2.5.1/debian/control  2023-12-20 21:41:15.0 +
+++ linux-atm-2.5.1/debian/control  2024-02-02 23:14:33.0 +
@@ -46,7 +46,10 @@
  uses one of these protocols: RFC 1483 bridged (RFC 2684 bridged),
  RFC 1483 bridged (RFC 2684 routed), PPP over Ethernet (PPPoE).
 
-Package: libatm1
+Package: libatm1t64
+Provides: ${t64:Provides}
+Replaces: libatm1
+Breaks: libatm1 (<< ${source:Version})
 Section: libs
 Architecture: linux-any
 Multi-Arch: same
@@ -59,7 +62,7 @@
 Package: libatm1-dev
 Section: libdevel
 Architecture: linux-any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libatm1 (= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, libatm1t64 (= ${binary:Version})
 Provides: libatm-dev
 Description: Development files for compiling ATM programs
  Header files and development libraries for compiling ATM (Asynchronous 
diff -Nru linux-atm-2.5.1/debian/libatm1.install 
linux-atm-2.5.1/debian/libatm1.install
--- linux-atm-2.5.1/debian/libatm1.install  2019-07-19 09:14:25.0 
+
+++ linux-atm-2.5.1/debian/libatm1.install  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/libatm.so.*
diff -Nru linux-atm-2.5.1/debian/libatm1.symbols 
linux-atm-2.5.1/debian/libatm1.symbols
--- linux-atm-2.5.1/debian/libatm1.symbols  2019-07-19 09:14:25.0 
+
+++ linux-atm-2.5.1/debian/libatm1.symbols  1970-01-01 00:00:00.0 
+
@@ -1,43 +0,0 @@
-libatm.so.1 libatm1 #MINVER#
- __atmlib_fetch@Base 2.4.1-17~
- __t2q_get_rate@Base 2.4.1-17~
- alloc@Base 2.4.1-17~
- ans_byaddr@Base 2.4.1-17~
- ans_byname@Base 2.4.1-17~
- atm2text@Base 2.4.1-17~
- atm_equal@Base 2.4.1-17~
- atm_tcpip_port_mapping@Base 2.4.1-17~
- diag@Base 2.4.1-17~
- diag_dump@Base 2.4.1-17~
- diag_fatal_debug_hook@Base 2.4.1-17~
- expire_timers@Base 2.4.1-17~
- get_logfile@Base 2.4.1-17~
- get_verbosity@Base 2.4.1-17~
- kptr_eq@Base 2.4.1-17~
- kptr_print@Base 2.4.1-17~
- next_timer@Base 2.4.1-17~
- now@Base 2.4.1-17~
- pop_timer@Base 2.4.1-17~
- qos2text@Base 2.4.1-17~
- qos_equal@Base 2.4.1-17~
- read_netl@Base 2.4.1-17~
- sap2text@Base 2.4.1-17~
- sap_equal@Base 2.4.1-17~
- sdu2cell@Base 2.4.1-17~
- set_application@Base 2.4.1-17~
- set_logfile@Base 

Bug#1062752: linphone: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: linphone
Version: 5.2.0-4.1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
linphone 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 linphone
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)
diff -Nru linphone-5.2.0/debian/changelog linphone-5.2.0/debian/changelog
--- linphone-5.2.0/debian/changelog 2023-12-17 16:31:05.0 +
+++ linphone-5.2.0/debian/changelog 2024-02-02 20:31:04.0 +
@@ -1,3 +1,10 @@
+linphone (5.2.0-4.2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 20:31:04 +
+
 linphone (5.2.0-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru linphone-5.2.0/debian/control linphone-5.2.0/debian/control
--- linphone-5.2.0/debian/control   2023-12-17 16:28:42.0 +
+++ linphone-5.2.0/debian/control   2024-02-02 20:31:04.0 +
@@ -41,8 +41,8 @@
 
 Package: liblinphone-dev
 Section: libdevel
-Depends: liblinphone11 (= ${binary:Version}),
- liblinphone++11 (= ${binary:Version}),
+Depends: liblinphone11t64 (= ${binary:Version}),
+ liblinphone++11t64 (= ${binary:Version}),
  libbelcard-dev (>= 5.2.0~),
  libbellesip-dev (>= 5.2.0~),
  libbelr-dev (>= 5.2.0~),
@@ -61,7 +61,10 @@
  This package contains the files needed to use the linphone's library in your
  programs.
 
-Package: liblinphone11
+Package: liblinphone11t64
+Provides: ${t64:Provides}
+Replaces: liblinphone11
+Breaks: liblinphone11 (<< ${source:Version})
 Section: libs
 Pre-Depends: ${misc:Pre-Depends},
 Depends: ${misc:Depends},
@@ -75,7 +78,10 @@
  .
  This package contains the shared runtime libraries.
 
-Package: liblinphone++11
+Package: liblinphone++11t64
+Provides: ${t64:Provides}
+Replaces: liblinphone++11
+Breaks: liblinphone++11 (<< ${source:Version})
 Section: libs
 Pre-Depends: ${misc:Pre-Depends},
 Depends: ${misc:Depends},
@@ -102,7 +108,7 @@
 
 Package: linphone-cli
 Depends: host,
- liblinphone11 (= ${binary:Version}),
+ liblinphone11t64 (= ${binary:Version}),
  linphone-common (= ${source:Version}),
  ${misc:Depends},
  ${shlibs:Depends},
diff -Nru linphone-5.2.0/debian/liblinphone++11.install 
linphone-5.2.0/debian/liblinphone++11.install
--- linphone-5.2.0/debian/liblinphone++11.install   2023-12-17 
16:28:42.0 +
+++ linphone-5.2.0/debian/liblinphone++11.install   1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/liblinphone++.so.*
diff -Nru linphone-5.2.0/debian/liblinphone++11.shlibs 
linphone-5.2.0/debian/liblinphone++11.shlibs
--- linphone-5.2.0/debian/liblinphone++11.shlibs2023-12-17 
16:28:42.0 +
+++ linphone-5.2.0/debian/liblinphone++11.shlibs1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-liblinphone++ 11 liblinphone++11 (>= 5.2.0-1), liblinphone++11 (<< 5.3.0-1)
diff -Nru linphone-5.2.0/debian/liblinphone++11t64.install 

Bug#1062750: qt6-virtualkeyboard: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qt6-virtualkeyboard
Version: 6.4.2+dfsg-4
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qt6-virtualkeyboard 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 qt6-virtualkeyboard
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qt6-virtualkeyboard-6.4.2+dfsg/debian/changelog 
qt6-virtualkeyboard-6.4.2+dfsg/debian/changelog
--- qt6-virtualkeyboard-6.4.2+dfsg/debian/changelog 2023-07-26 
21:33:20.0 +
+++ qt6-virtualkeyboard-6.4.2+dfsg/debian/changelog 2024-02-02 
23:11:24.0 +
@@ -1,3 +1,10 @@
+qt6-virtualkeyboard (6.4.2+dfsg-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 23:11:24 
+
+
 qt6-virtualkeyboard (6.4.2+dfsg-4) unstable; urgency=medium
 
   * Team upload to unstable.
diff -Nru qt6-virtualkeyboard-6.4.2+dfsg/debian/control 
qt6-virtualkeyboard-6.4.2+dfsg/debian/control
--- qt6-virtualkeyboard-6.4.2+dfsg/debian/control   2023-07-26 
21:32:16.0 +
+++ qt6-virtualkeyboard-6.4.2+dfsg/debian/control   2024-02-02 
23:11:24.0 +
@@ -31,7 +31,10 @@
 Vcs-Git: https://salsa.debian.org/qt-kde-team/qt6/qt6-virtualkeyboard.git
 Rules-Requires-Root: no
 
-Package: libqt6virtualkeyboard6
+Package: libqt6virtualkeyboard6t64
+Provides: ${t64:Provides}
+Replaces: libqt6virtualkeyboard6
+Breaks: libqt6virtualkeyboard6 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends},
@@ -45,7 +48,10 @@
  .
  This package contains the Qt Virtual Keyboard library.
 
-Package: libqt6hunspellinputmethod6
+Package: libqt6hunspellinputmethod6t64
+Provides: ${t64:Provides}
+Replaces: libqt6hunspellinputmethod6
+Breaks: libqt6hunspellinputmethod6 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends},
@@ -94,7 +100,7 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libqt6virtualkeyboard6 (= ${binary:Version}),
+Depends: libqt6virtualkeyboard6t64 (= ${binary:Version}),
  qt6-base-dev,
  ${misc:Depends},
 Breaks: libqt6virtualkeyboard6-dev (<< 6.4.1+dfsg-2~),
diff -Nru 
qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.install 
qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.install
--- qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.install
2022-09-06 18:34:45.0 +
+++ qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.install
1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/${DEB_HOST_MULTIARCH}/libQt6HunspellInputMethod.so.*
diff -Nru 
qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.symbols 
qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.symbols
--- qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.symbols
2023-07-08 15:11:11.0 +
+++ qt6-virtualkeyboard-6.4.2+dfsg/debian/libqt6hunspellinputmethod6.symbols
1970-01-01 00:00:00.0 +

Bug#1062748: link-grammar: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: link-grammar
Version: 5.12.3~dfsg-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
link-grammar 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 link-grammar
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)
diff -Nru link-grammar-5.12.3~dfsg/debian/changelog 
link-grammar-5.12.3~dfsg/debian/changelog
--- link-grammar-5.12.3~dfsg/debian/changelog   2023-06-27 16:28:28.0 
+
+++ link-grammar-5.12.3~dfsg/debian/changelog   2024-02-02 22:30:51.0 
+
@@ -1,3 +1,11 @@
+link-grammar (5.12.3~dfsg-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+  * Bump build-dependency on d-shlibs for --t64 support.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 22:30:51 +
+
 link-grammar (5.12.3~dfsg-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru link-grammar-5.12.3~dfsg/debian/control 
link-grammar-5.12.3~dfsg/debian/control
--- link-grammar-5.12.3~dfsg/debian/control 2023-01-07 10:14:10.0 
+
+++ link-grammar-5.12.3~dfsg/debian/control 2024-02-02 22:30:51.0 
+
@@ -5,7 +5,7 @@
 Build-Depends:
  ant [!hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !m68k !sh4],
  autoconf-archive,
- d-shlibs (>= 0.98~),
+ d-shlibs (>= 0.106~),
  debhelper-compat (= 13),
  default-jdk [!hppa !hurd-i386 !kfreebsd-amd64 !kfreebsd-i386 !m68k !sh4],
  dh-sequence-python3,
@@ -48,7 +48,10 @@
  .
  This package contains the user-executable binary.
 
-Package: liblink-grammar5
+Package: liblink-grammar5t64
+Provides: ${t64:Provides}
+Replaces: liblink-grammar5
+Conflicts: liblink-grammar5 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -80,7 +83,7 @@
 Architecture: any
 Multi-Arch: same
 Depends:
- liblink-grammar5 (= ${binary:Version}),
+ liblink-grammar5t64 (= ${binary:Version}),
  ${devlibs:Depends},
  ${misc:Depends},
 Description: Carnegie Mellon University's link grammar parser (development 
headers)
@@ -103,7 +106,7 @@
 Section: java
 Architecture: alpha amd64 arm64 armel armhf i386 ia64 mips mips64 mips64el 
mipsel powerpc powerpcspe ppc64 ppc64el s390x sparc sparc64 x32
 Depends:
- liblink-grammar5,
+ liblink-grammar5t64,
  ${misc:Depends},
  ${shlibs:Depends},
 Description: Carnegie Mellon University's link grammar parser (JNI library)
@@ -127,7 +130,7 @@
 Architecture: any
 Section: python
 Depends:
- liblink-grammar5,
+ liblink-grammar5t64,
  ${misc:Depends},
  ${python3:Depends},
  ${shlibs:Depends},
diff -Nru link-grammar-5.12.3~dfsg/debian/liblink-grammar5t64.lintian-overrides 
link-grammar-5.12.3~dfsg/debian/liblink-grammar5t64.lintian-overrides
--- link-grammar-5.12.3~dfsg/debian/liblink-grammar5t64.lintian-overrides   
1970-01-01 00:00:00.0 +
+++ link-grammar-5.12.3~dfsg/debian/liblink-grammar5t64.lintian-overrides   
2024-02-02 22:30:50.0 +
@@ -0,0 +1 @@
+liblink-grammar5t64: package-name-doesnt-match-sonames liblink-grammar5
diff -Nru link-grammar-5.12.3~dfsg/debian/rules 

Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable

[Craig Holyoak]

FWIW I'm having the same problems. Granted, this NIC is in a
Thunderbolt dock, so one can't exclude this as a factor, but the
errors are identical. This is even the case running the 6.7.1-1~exp1
kernel from experimental.

Bug#1062746: linbox: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: linbox
Version: 1.7.0-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
linbox 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 linbox
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)

Bug#1062744: libzypp: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libzypp
Version: 17.31.29-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libzypp 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 libzypp
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)

Bug#1062745: liggghts: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: liggghts
Version: 3.8.0+repack1-9
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
liggghts 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 liggghts
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)

Bug#1062743: libzip: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libzip
Version: 1.7.3-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libzip 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 libzip
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)

Bug#1062742: libzia: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libzia
Version: 4.52-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libzia 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 libzia
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)

Bug#1062741: libzen: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libzen
Version: 0.4.41-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libzen 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 libzen
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)

Bug#1062740: libzdb: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libzdb
Version: 3.1-0.2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libzdb 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 libzdb
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)

Bug#1062739: libydpdict: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libydpdict
Version: 1.0.4-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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)

Bug#1062737: libxtrxll: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libxtrxll
Version: 0.0.1+git20201202.1b6eddf-1.1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libxtrxll 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 libxtrxll
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)

Bug#1062738: libyang2: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libyang2
Version: 2.1.30-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libyang2 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 libyang2
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)

Bug#1062736: libxt: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libxt
Version: 1:1.2.1-1.1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libxt 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 libxt
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)

Bug#1062735: libxmltok: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libxmltok
Version: 1.2-4
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libxmltok 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 libxmltok
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)

Bug#1062734: libxmlbird: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libxmlbird
Version: 1.2.15-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libxmlbird 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 libxmlbird
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)

Bug#1062733: libxlsxwriter: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libxlsxwriter
Version: 1.1.5-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libxlsxwriter 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 libxlsxwriter
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)

Bug#1062732: libxeddsa: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libxeddsa
Version: 2.0.0+20221109.06a02c8-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libxeddsa 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 libxeddsa
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)

Bug#1062731: libwfa2: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libwfa2
Version: 2.3.3-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libwfa2 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 libwfa2
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)

Bug#1062730: libwebsockets: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libwebsockets
Version: 4.3.3-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libwebsockets 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 libwebsockets
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)

Bug#1062729: libvslvm: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libvslvm
Version: 20181227-1.1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libvslvm 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 libvslvm
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)

Bug#1062728: libvmime: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libvmime
Version: 0.9.2-8.1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libvmime 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 libvmime
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)

Bug#1062727: libvshadow: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libvshadow
Version: 20190323-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libvshadow 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 libvshadow
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)

Bug#1062726: libident: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libident
Version: 0.32-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libident 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 libident
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)

Bug#1062671: lomiri-ui-toolkit: NMU diff for 64-bit time_t transition

[Mike Gabriel]

Hi Graham,

On  Fr 02 Feb 2024 16:43:30 CET, Graham Inggs wrote:


Source: lomiri-ui-toolkit
Version: 1.3.5010+dfsg-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

NOTICE: these changes must not be uploaded to unstable yet!


As it seems this transition is kind of interfering with our  
FOSDEM-hacking effort of getting Lomiri packages updated in Debian  
unstable (for Ubuntu LTS).


Last night I uploaded a new upstream release of lomiri-ui-toolkit to  
unstable. I can take your patch and upgrade the version in exp to  
latest upstream.


(I also did that for lomiri-download-manager just now and would love  
to do it for lomiri-indicator-transfer; OT here, though).


Mike
--

DAS-NETZWERKTEAM
c\o Technik- und Ökologiezentrum Eckernförde
Mike Gabriel, Marienthaler Str. 17, 24340 Eckernförde
mobile: +49 (1520) 1976 148
landline: +49 (4351) 850 8940

GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22  0782 9AF4 6B30 2577 1B31
mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de



pgpPehvDW5HcH.pgp
Description: Digitale PGP-Signatur

Bug#1062724: node-cbor: cbor2comment throws exception on decoding null

[brian m. carlson]

Package: node-cbor
Version: 8.1.0+dfsg+~cs5.2.1-3
Severity: normal
File: /usr/bin/cbor2comment

cbor2comment can throw an exception when a null is deserialized:

$ cat >data <<-EOF
AKViaWQAaHNlbGVjdG9yoWRwYXRoTi9tZW1vcnkvdmF1bHQvZ3JlY3Vyc2WhZ2Jvb2xlYW71ZGtp
bmRqY3JlZGVudGlhbGRib2R5rGh1c2VybmFtZaFnbGl0ZXJhbENmb29mc2VjcmV0oWNhbnn2aGF1
dGh0eXBloWNhbnn2ZGtpbmShZ2xpdGVyYWxjYXBpaHByb3RvY29soWdsaXRlcmFsZWh0dHBzZGhv
c3ShZ2xpdGVyYWxvZ2l0LmV4YW1wbGUuY29tZXRpdGxloWdsaXRlcmFseB1HaXQ6IGh0dHBzOi8v
Z2l0LmV4YW1wbGUuY29tL2tkZXNjcmlwdGlvbqFjYW559mRwYXRooWNhbnn2Z3NlcnZpY2WhZ2xp
dGVyYWxjZ2l0ZWV4dHJhoGJpZKFnbGl0ZXJhbFiAODhkMmQ3Njc4YzEyNzdmODFiMzhmZWJkOWQ5
M2Y0ZDc0ZGY4OGYyNzIwOTYwMzA4YTFjY2VjZmI1N2QzNjVmNTNiMTAyMjc2YmQ1YjQ0MjcwMjkz
ZDQzNDU4M2RkMmVmNmMxZGViODdmYzI5NTA4YTc2YjI3YjA3OTgyNmI3MDYK
EOF
$ base64 -d data | cbor2comment
[Some data...]
f6  -- {Val:0}, TypeError: Cannot read properties of null 
(reading 'Symbol(nodejs.util.inspect.custom)')
at Object.cborValueToString (/usr/share/nodejs/cbor/lib/utils.js:246:21)
at Commented._on_value (/usr/share/nodejs/cbor/lib/commented.js:336:23)
at Decoder.emit (node:events:517:28)
at Decoder._parse (/usr/share/nodejs/cbor/lib/decoder.js:555:12)
at _parse.next ()
at Decoder._transform 
(/usr/share/nodejs/cbor/vendor/binary-parse-stream/index.js:53:29)
at Transform._write (node:internal/streams/transform:175:8)
at writeOrBuffer (node:internal/streams/writable:392:12)
at _write (node:internal/streams/writable:333:10)
at Writable.write (node:internal/streams/writable:337:10)

I expected cbor2comment to print the data, including the null, without
throwing an exception or truncating the dump.

I should note that cbor2json works, but because my data structure uses
byte strings heavily, the dump is effectively unreadable.  I have not
found other non-null data that triggers an error.

In case it is useful to know, the data structure was serialized using
the Rust library serde_cbor.  It's test data and is not sensitive, so
feel free to share it, add it to the testsuite, etc.

I believe this may be fixed with PR #188 upstream (in v9.0.2), but I'm
unsure.  In any event, I expect it's easy to verify one way or the other
with the steps above.

-- System Information:
Debian Release: trixie/sid
  APT prefers oldstable-security
  APT policy: (500, 'oldstable-security'), (500, 'unstable'), (500, 'stable'), 
(1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.6.9-amd64 (SMP w/20 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER, TAINT_WARN
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_CA:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages node-cbor depends on:
ii  node-bignumber  9.1.1-1
ii  node-commander  9.4.1-1
ii  nodejs  18.19.0+dfsg-6

node-cbor recommends no packages.

node-cbor suggests no packages.

-- no debconf information

-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA


signature.asc
Description: PGP signature

Bug#1059649: NTP does not keep accurate time on bookworm

[Rob Janssen]

Craig,

I'm sorry but I know absolutely nothing about that "systemd socket" mechanism.  
I am an old hat
that grew up with init and hates systemd.
Maybe I have inadvertently broken something, I only know what I have written 
before and that it does
not work for me without forcing the service to run as root instead of 
Debian-snmp.
What exactly is going on now is unclear to me.

Rob

On 2024-02-02 06:13, Craig Small wrote:
> On Fri, 2 Feb 2024 at 08:54, Rob Janssen  wrote:
>
> I am using systemd.
>
> Where are you seeing this error? The systemd socket is the thing that opens 
> up the socket, so shouldn't matter what the snmptrapd process is running as.
>
> When I reboot, I get this:
> $ sudo ss -unlp | grep 162
> UNCONN 0      0             0.0.0.0:162         0.0.0.0:* 
>    users:(("systemd",pid=1,fd=83))        
> UNCONN 0      0                [::]:162           [::]:*    
> users:(("systemd",pid=1,fd=84))        
> $ pgrep snmptrapd
>
> So systemd is listening to the socket and snmptrapd is not even running.
> After I send a trap:
> $ sudo ss -unlp | grep 162
> UNCONN 0      0             0.0.0.0:162         0.0.0.0:* 
>    users:(("snmptrapd",pid=7296,fd=3),("systemd",pid=1,fd=83))
> UNCONN 0      0                [::]:162           [::]:*    
> users:(("snmptrapd",pid=7296,fd=4),("systemd",pid=1,fd=84))
> $ pgrep snmptrapd
> 7296
>
> Maybe the issue is that this system does not have IPv6 enabled?  In 
> sysctl.conf it has:
> net.ipv6.conf.all.disable_ipv6 = 1
>
> I added that and rebooted, it worked fine.
>  
>
>
> That has effect on the default snmpd service as well, but I work around 
> that by modifying the listen
> port in the config file.
> The snmptrapd.service file has "udp:162" and "udp6:162" args in the 
> ExecStart but maybe these aren't used at all
> in this config?  In bullseye I think it worked out of the box.
>
> In a way, they're used.
>
> In a proper systemd socket activation, the service doesn't need to know or 
> define the ports it's listening to, they just get a bunch of file descriptors 
> and use those.
>
> So we could have a command line in the service file with no ports and it 
> looks like it works; but that is only because snmptrapd is sort-of looking 
> for UDP port 162.
> If you change the socket definition to another port, say 164 you get this:
> Feb 02 15:57:37 elmo snmptrapd[9123]: couldn't open udp:162 -- errno 13 
> ("Permission denied")
> Feb 02 15:57:37 elmo snmptrapd[9123]: couldn't open udp:162 -- errno 13 
> ("Permission denied")
>
> system opens port 164, a trap to port 164 starts snmptrapd which not only 
> listens to the systemd FD, but opens its own ports too running as a non-priv 
> user.
>  OK, so change the service definiton to listen to some port above 1024, it 
> should be ok because it can open that port and use the systemd FD. For some 
> reason
> it doesn't (as in it starts but there are no messages).
>
> What that means is the ports that are defined in the socket file need to 
> match the ports in the service file. snmptrapd is shipped with that:
> $ grep 162 debian/snmptrapd.s*
> debian/snmptrapd.service:ExecStart=/usr/sbin/snmptrapd -LOw -f udp:162 
> udp6:162
> debian/snmptrapd.socket:ListenDatagram=0.0.0.0:162 
> debian/snmptrapd.socket:ListenDatagram=[::]:162
> debian/snmptrapd.socket:# ListenStream=0.0.0.0:162 
> debian/snmptrapd.socket:# ListenStream=[::]:162
>
> It would be more friendly when snmpd and snmptrapd degrade gracefully to 
> IPv4-only when there is no IPv6 on the system.
>
> I don't think its that. 
>
>  - Craig
>

Bug#1062722: qt-qml-models: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qt-qml-models
Version: 0~0.0-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qt-qml-models 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 qt-qml-models
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qt-qml-models-0~0.0/debian/changelog 
qt-qml-models-0~0.0/debian/changelog
--- qt-qml-models-0~0.0/debian/changelog2021-01-14 11:42:37.0 
+
+++ qt-qml-models-0~0.0/debian/changelog2024-02-02 22:34:21.0 
+
@@ -1,3 +1,10 @@
+qt-qml-models (0~0.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 22:34:21 
+
+
 qt-qml-models (0~0.0-1) unstable; urgency=medium
 
   * Initial release (Closes: #980131)
diff -Nru qt-qml-models-0~0.0/debian/control qt-qml-models-0~0.0/debian/control
--- qt-qml-models-0~0.0/debian/control  2021-01-14 11:42:37.0 +
+++ qt-qml-models-0~0.0/debian/control  2024-02-02 22:34:21.0 +
@@ -8,7 +8,10 @@
 Homepage: https://github.com/cavewhere/qt-qml-models
 Rules-Requires-Root: no
 
-Package: libqtqmlmodels0
+Package: libqtqmlmodels0t64
+Provides: ${t64:Provides}
+Replaces: libqtqmlmodels0
+Breaks: libqtqmlmodels0 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -30,7 +33,7 @@
 Package: libqtqmlmodels-dev 
 Architecture: any
 Multi-Arch: same
-Depends: libqtqmlmodels0 (= ${binary:Version}), ${misc:Depends}
+Depends: libqtqmlmodels0t64 (= ${binary:Version}), ${misc:Depends}
 Description: Additional list-type data models for QML apps
  This package adds 2 C++ data models to the qml back end, for use by 
  QML applications.
diff -Nru qt-qml-models-0~0.0/debian/libqtqmlmodels0.install 
qt-qml-models-0~0.0/debian/libqtqmlmodels0.install
--- qt-qml-models-0~0.0/debian/libqtqmlmodels0.install  2021-01-14 
11:42:37.0 +
+++ qt-qml-models-0~0.0/debian/libqtqmlmodels0.install  1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libQtQmlModels.so.*
\ No newline at end of file
diff -Nru qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.install 
qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.install
--- qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.install   1970-01-01 
00:00:00.0 +
+++ qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.install   2021-01-14 
11:42:37.0 +
@@ -0,0 +1 @@
+usr/lib/*/libQtQmlModels.so.*
\ No newline at end of file
diff -Nru qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.lintian-overrides 
qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.lintian-overrides
--- qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.lintian-overrides 
1970-01-01 00:00:00.0 +
+++ qt-qml-models-0~0.0/debian/libqtqmlmodels0t64.lintian-overrides 
2024-02-02 22:34:21.0 +
@@ -0,0 +1 @@
+libqtqmlmodels0t64: package-name-doesnt-match-sonames libqtqmlmodels0

Bug#1062721: qsopt-ex: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qsopt-ex
Version: 2.5.10.3-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qsopt-ex 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 qsopt-ex
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qsopt-ex-2.5.10.3/debian/changelog qsopt-ex-2.5.10.3/debian/changelog
--- qsopt-ex-2.5.10.3/debian/changelog  2018-10-30 08:25:41.0 +
+++ qsopt-ex-2.5.10.3/debian/changelog  2024-02-02 22:20:45.0 +
@@ -1,3 +1,10 @@
+qsopt-ex (2.5.10.3-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 22:20:45 
+
+
 qsopt-ex (2.5.10.3-2) unstable; urgency=medium
 
   * Team upload.
diff -Nru qsopt-ex-2.5.10.3/debian/control qsopt-ex-2.5.10.3/debian/control
--- qsopt-ex-2.5.10.3/debian/control2018-10-30 08:25:41.0 +
+++ qsopt-ex-2.5.10.3/debian/control2024-02-02 22:20:45.0 +
@@ -4,7 +4,7 @@
 Section: math
 Priority: optional
 Build-Depends: debhelper (>= 11~),
-   d-shlibs,
+   d-shlibs (>= 0.106),
libgmp-dev
 Standards-Version: 4.2.1
 Vcs-Browser: https://salsa.debian.org/med-team/qsopt-ex
@@ -15,7 +15,7 @@
 Architecture: any
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- libqsopt-ex2 (= ${binary:Version})
+ libqsopt-ex2t64 (= ${binary:Version})
 Description: Exact linear programming solver
  QSopt-ex is an implementation of a simplex-based algorithm that returns exact
  rational solutions, taking advantage of the speed of floating-point
@@ -29,7 +29,7 @@
 Section: libdevel
 Depends: ${shlibs:Depends},
  ${misc:Depends},
- libqsopt-ex2 (= ${binary:Version})
+ libqsopt-ex2t64 (= ${binary:Version})
 Description: Exact linear programming solver -- development files
  QSopt-ex is an implementation of a simplex-based algorithm that returns exact
  rational solutions, taking advantage of the speed of floating-point
@@ -38,7 +38,10 @@
  .
  This package contains the header files and static library.
 
-Package: libqsopt-ex2
+Package: libqsopt-ex2t64
+Provides: ${t64:Provides}
+Replaces: libqsopt-ex2
+Conflicts: libqsopt-ex2 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
diff -Nru qsopt-ex-2.5.10.3/debian/libqsopt-ex2t64.lintian-overrides 
qsopt-ex-2.5.10.3/debian/libqsopt-ex2t64.lintian-overrides
--- qsopt-ex-2.5.10.3/debian/libqsopt-ex2t64.lintian-overrides  1970-01-01 
00:00:00.0 +
+++ qsopt-ex-2.5.10.3/debian/libqsopt-ex2t64.lintian-overrides  2024-02-02 
22:20:45.0 +
@@ -0,0 +1 @@
+libqsopt-ex2t64: package-name-doesnt-match-sonames libqsopt-ex2
diff -Nru qsopt-ex-2.5.10.3/debian/rules qsopt-ex-2.5.10.3/debian/rules
--- qsopt-ex-2.5.10.3/debian/rules  2018-10-30 08:25:41.0 +
+++ qsopt-ex-2.5.10.3/debian/rules  2024-02-02 22:20:45.0 +
@@ -10,6 +10,7 @@
 override_dh_install:
dh_install
d-shlibmove --commit \
+   --t64 \
  

Bug#1062720: qpxtool: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qpxtool
Version: 0.8.1-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qpxtool 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 qpxtool
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qpxtool-0.8.1/debian/changelog qpxtool-0.8.1/debian/changelog
--- qpxtool-0.8.1/debian/changelog  2020-01-01 00:00:01.0 +
+++ qpxtool-0.8.1/debian/changelog  2024-02-02 22:18:24.0 +
@@ -1,3 +1,10 @@
+qpxtool (0.8.1-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 22:18:24 
+
+
 qpxtool (0.8.1-2) unstable; urgency=high
 
   [ Boris Pek ]
diff -Nru qpxtool-0.8.1/debian/control qpxtool-0.8.1/debian/control
--- qpxtool-0.8.1/debian/control2020-01-01 00:00:01.0 +
+++ qpxtool-0.8.1/debian/control2024-02-02 22:18:24.0 +
@@ -18,7 +18,7 @@
 
 Package: qpxtool
 Architecture: any
-Depends: libqpx0 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
+Depends: libqpx0t64 (= ${binary:Version}), ${misc:Depends}, ${shlibs:Depends}
 Suggests: pxfw
 Description: CD/DVD quality checker
  QPxTool gives you access to all available Quality Checks (Q-Checks) on written
@@ -32,7 +32,7 @@
 
 Package: pxfw
 Architecture: any
-Depends: libqpx0 (= ${binary:Version}),
+Depends: libqpx0t64 (= ${binary:Version}),
  qpxtool,
  ${misc:Depends},
  ${shlibs:Depends}
@@ -45,7 +45,10 @@
  This package contains pxfw, a firmware flash program for Plextor optical
  drives.
 
-Package: libqpx0
+Package: libqpx0t64
+Provides: ${t64:Provides}
+Replaces: libqpx0
+Breaks: libqpx0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -60,7 +63,7 @@
 Package: libqpx-dev
 Architecture: any
 Section: libdevel
-Depends: libqpx0 (= ${binary:Version}), ${misc:Depends}
+Depends: libqpx0t64 (= ${binary:Version}), ${misc:Depends}
 Description: CD/DVD quality checker (development files)
  QPxTool gives you access to all available Quality Checks (Q-Checks) on written
  and blank media, that are available for your drive. This will help you to find
diff -Nru qpxtool-0.8.1/debian/libqpx0.install 
qpxtool-0.8.1/debian/libqpx0.install
--- qpxtool-0.8.1/debian/libqpx0.install2020-01-01 00:00:01.0 
+
+++ qpxtool-0.8.1/debian/libqpx0.install1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*.so.*
diff -Nru qpxtool-0.8.1/debian/libqpx0.lintian-overrides 
qpxtool-0.8.1/debian/libqpx0.lintian-overrides
--- qpxtool-0.8.1/debian/libqpx0.lintian-overrides  2020-01-01 
00:00:01.0 +
+++ qpxtool-0.8.1/debian/libqpx0.lintian-overrides  1970-01-01 
00:00:00.0 +
@@ -1,3 +0,0 @@
-# These libraries are for internal usage.
-libqpx0: package-name-doesnt-match-sonames
-libqpx0: no-symbols-control-file
diff -Nru qpxtool-0.8.1/debian/libqpx0t64.install 
qpxtool-0.8.1/debian/libqpx0t64.install
--- qpxtool-0.8.1/debian/libqpx0t64.install 

Bug#1062719: qpdf: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qpdf
Version: 11.8.0-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qpdf 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 qpdf
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qpdf-11.8.0/debian/changelog qpdf-11.8.0/debian/changelog
--- qpdf-11.8.0/debian/changelog2024-01-08 17:48:05.0 +
+++ qpdf-11.8.0/debian/changelog2024-02-02 22:16:17.0 +
@@ -1,3 +1,10 @@
+qpdf (11.8.0-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 22:16:17 
+
+
 qpdf (11.8.0-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru qpdf-11.8.0/debian/control qpdf-11.8.0/debian/control
--- qpdf-11.8.0/debian/control  2024-01-08 17:48:05.0 +
+++ qpdf-11.8.0/debian/control  2024-02-02 22:16:17.0 +
@@ -11,7 +11,10 @@
 Standards-Version: 4.6.2
 Homepage: https://qpdf.sourceforge.io
 
-Package: libqpdf29
+Package: libqpdf29t64
+Provides: ${t64:Provides}
+Replaces: libqpdf29
+Breaks: libqpdf29 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
@@ -43,7 +46,7 @@
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
-Depends: ${misc:Depends}, libqpdf29 (= ${binary:Version}), libjpeg-dev, 
zlib1g-dev
+Depends: ${misc:Depends}, libqpdf29t64 (= ${binary:Version}), libjpeg-dev, 
zlib1g-dev
 Suggests: qpdf-doc
 Description: development files for PDF transformation/inspection library
  QPDF is a program that can be used to linearize (web-optimize),
diff -Nru qpdf-11.8.0/debian/libqpdf29.install 
qpdf-11.8.0/debian/libqpdf29.install
--- qpdf-11.8.0/debian/libqpdf29.install2024-01-08 17:48:05.0 
+
+++ qpdf-11.8.0/debian/libqpdf29.install1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-debian/tmp/usr/lib/*/libqpdf.so.*
diff -Nru qpdf-11.8.0/debian/libqpdf29.shlibs 
qpdf-11.8.0/debian/libqpdf29.shlibs
--- qpdf-11.8.0/debian/libqpdf29.shlibs 2024-01-08 17:48:05.0 +
+++ qpdf-11.8.0/debian/libqpdf29.shlibs 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-libqpdf 29 libqpdf29 (>> 11.8~)
diff -Nru qpdf-11.8.0/debian/libqpdf29t64.install 
qpdf-11.8.0/debian/libqpdf29t64.install
--- qpdf-11.8.0/debian/libqpdf29t64.install 1970-01-01 00:00:00.0 
+
+++ qpdf-11.8.0/debian/libqpdf29t64.install 2024-01-08 17:48:05.0 
+
@@ -0,0 +1 @@
+debian/tmp/usr/lib/*/libqpdf.so.*
diff -Nru qpdf-11.8.0/debian/libqpdf29t64.lintian-overrides 
qpdf-11.8.0/debian/libqpdf29t64.lintian-overrides
--- qpdf-11.8.0/debian/libqpdf29t64.lintian-overrides   1970-01-01 
00:00:00.0 +
+++ qpdf-11.8.0/debian/libqpdf29t64.lintian-overrides   2024-02-02 
22:16:17.0 +
@@ -0,0 +1 @@
+libqpdf29t64: package-name-doesnt-match-sonames libqpdf29
diff -Nru qpdf-11.8.0/debian/libqpdf29t64.shlibs 
qpdf-11.8.0/debian/libqpdf29t64.shlibs
--- qpdf-11.8.0/debian/libqpdf29t64.shlibs  1970-01-01 00:00:00.0 
+
+++ 

Bug#1062718: qm-dsp: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qm-dsp
Version: 1.7.1-7
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qm-dsp 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 qm-dsp
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qm-dsp-1.7.1/debian/changelog qm-dsp-1.7.1/debian/changelog
--- qm-dsp-1.7.1/debian/changelog   2024-01-22 08:01:00.0 +
+++ qm-dsp-1.7.1/debian/changelog   2024-02-02 22:15:56.0 +
@@ -1,3 +1,10 @@
+qm-dsp (1.7.1-7.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 22:15:56 
+
+
 qm-dsp (1.7.1-7) unstable; urgency=medium
 
   * B-D on liblapack-dev
diff -Nru qm-dsp-1.7.1/debian/control qm-dsp-1.7.1/debian/control
--- qm-dsp-1.7.1/debian/control 2024-01-22 08:01:00.0 +
+++ qm-dsp-1.7.1/debian/control 2024-02-02 22:15:56.0 +
@@ -16,7 +16,10 @@
 Vcs-Git: https://salsa.debian.org/multimedia-team/qm-dsp.git
 Vcs-Browser: https://salsa.debian.org/multimedia-team/qm-dsp
 
-Package: libqm-dsp0
+Package: libqm-dsp0t64
+Provides: ${t64:Provides}
+Replaces: libqm-dsp0
+Breaks: libqm-dsp0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends:
@@ -37,7 +40,7 @@
 Section: libdevel
 Architecture: any
 Depends:
- libqm-dsp0 (= ${binary:Version}),
+ libqm-dsp0t64 (= ${binary:Version}),
  ${misc:Depends},
 Multi-Arch: same
 Description: Development files (headers) for libqm-dsp library
diff -Nru qm-dsp-1.7.1/debian/libqm-dsp0.install 
qm-dsp-1.7.1/debian/libqm-dsp0.install
--- qm-dsp-1.7.1/debian/libqm-dsp0.install  2024-01-22 08:01:00.0 
+
+++ qm-dsp-1.7.1/debian/libqm-dsp0.install  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-lib*.so.*  /usr/lib/${DEB_HOST_MULTIARCH}
diff -Nru qm-dsp-1.7.1/debian/libqm-dsp0t64.install 
qm-dsp-1.7.1/debian/libqm-dsp0t64.install
--- qm-dsp-1.7.1/debian/libqm-dsp0t64.install   1970-01-01 00:00:00.0 
+
+++ qm-dsp-1.7.1/debian/libqm-dsp0t64.install   2024-01-22 08:01:00.0 
+
@@ -0,0 +1 @@
+lib*.so.*  /usr/lib/${DEB_HOST_MULTIARCH}
diff -Nru qm-dsp-1.7.1/debian/libqm-dsp0t64.lintian-overrides 
qm-dsp-1.7.1/debian/libqm-dsp0t64.lintian-overrides
--- qm-dsp-1.7.1/debian/libqm-dsp0t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ qm-dsp-1.7.1/debian/libqm-dsp0t64.lintian-overrides 2024-02-02 
22:15:56.0 +
@@ -0,0 +1 @@
+libqm-dsp0t64: package-name-doesnt-match-sonames libqm-dsp0

Bug#1062716:

[Miriam Espana Acebal]

Attaching patch.
-- 
Miriam España Acebal
Software Engineer II - Ubuntu PublicCloud/Server
Canonical Ltd.
From 938bd71e0e8af3d3c854e54a12f5fea7d1a5e63e Mon Sep 17 00:00:00 2001
From: Miriam Espana Acebal 
Date: Fri, 2 Feb 2024 14:19:36 +0100
Subject: [PATCH] * d/prerm, d/postinst: fix path according to /usr movement

---
 debian/postinst | 2 +-
 debian/prerm| 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/debian/postinst b/debian/postinst
index e92a53d..456e73a 100644
--- a/debian/postinst
+++ b/debian/postinst
@@ -3,7 +3,7 @@
 set -e
 
 if [ "$1" = configure ]; then
-update-alternatives --install /bin/mt mt /bin/mt-gnu 10 \
+update-alternatives --install /usr/bin/mt mt /usr/bin/mt-gnu 10 \
   --slave \
 	/usr/share/man/man1/mt.1.gz mt.1.gz /usr/share/man/man1/mt-gnu.1.gz
 fi
diff --git a/debian/prerm b/debian/prerm
index 89490ea..08f3b39 100644
--- a/debian/prerm
+++ b/debian/prerm
@@ -3,5 +3,5 @@
 set -e
 
 if [ "$1" = remove ]; then
-update-alternatives --remove mt /bin/mt-gnu
+update-alternatives --remove mt /usr/bin/mt-gnu
 fi
-- 
2.40.1

Bug#1062533: chromium: Chromium doesn't launch in ARM64!

[Sally A.haj]

There is something update:
I was enabling "chrome://flags/#enable-unsafe-webgpu" flag, and it was
working fine with all the previous versions, now I have tried disabled
it, and the chromium works now.
I don't understand why when it enabled prevents chromium from
running/launching.

Thank you 

On Fri, 2024-02-02 at 04:17 -0500, Andres Salomon wrote:
> Running 'grep chromium /var/log/dpkg.log' (or /var/log/dpkg.log.1 if
> it 
> was already rotated) should tell you what version it was upgraded
> from.
> 
> On 2/1/24 15:43, Sally A.haj wrote:
> > I don't remember exactly, but I believe it was the very recent
> > before
> > the latest, because I usually do update the system every week or
> > so.
> > 
> > Thank you.
> > On Thu, 2024-02-01 at 15:36 -0500, Andres Salomon wrote:
> > > 
> > > 
> > > On 2/1/24 15:23, Sally A.haj wrote:
> > > [...]
> > > > 
> > > >  * What outcome did you expect instead?
> > > >  Before the latest update, it was working just fine.
> > > > I am using Gnome/Wayland on Raspberry Pi 4 for a quite some
> > > > times,
> > > > and this the first time I face an issue with chromium.
> > > > 
> > > 
> > > Thanks for the report. What exactly was the previous version that
> > > worked
> > > for you?
> > 

Bug#1062716: update-alternatives: error: alternative path /bin/mt-gnu doesn't exist

[Miriam España Acebal]

Package: cpio
Version: 2.15+dfsg-1
Severity: important
Tags: patch
X-Debbugs-Cc: miriam.esp...@canonical.com

Dear Maintainer,

we found that latest version of cpio is breaking some tests 
(sbuild/unshare-qemuwrapper) for some packages in migration (i.e. openssh) for 
the next Ubuntu series, due to the following change:

  * Move files to /usr
Patch by Helmut Grohne 
Closes: #1059756

It seems the path should be refreshed accordingly to the movement to
/usr in the prerm and the postinst too.

I reported the bug 2052295 in Ubuntu [1]. I made a patch for it which was 
already applied in Ubuntu. I attach it here for your consideration in case if 
helps in Debian too.

Thanks in advance, 

Miriam (mirespace)
 
[1] https://bugs.launchpad.net/ubuntu/+source/cpio/+bug/2052295

-- no debconf information

Bug#1062533: chromium: Chromium doesn't launch in ARM64!

[Sally A.haj]

Yes Andres,
I run the command you mentioned, and this is the previous version:
121.0.6167.85-1~deb12u1.

Thank you.

On Fri, 2024-02-02 at 04:17 -0500, Andres Salomon wrote:
> Running 'grep chromium /var/log/dpkg.log' (or /var/log/dpkg.log.1 if
> it 
> was already rotated) should tell you what version it was upgraded
> from.
> 
> On 2/1/24 15:43, Sally A.haj wrote:
> > I don't remember exactly, but I believe it was the very recent
> > before
> > the latest, because I usually do update the system every week or
> > so.
> > 
> > Thank you.
> > On Thu, 2024-02-01 at 15:36 -0500, Andres Salomon wrote:
> > > 
> > > 
> > > On 2/1/24 15:23, Sally A.haj wrote:
> > > [...]
> > > > 
> > > >  * What outcome did you expect instead?
> > > >  Before the latest update, it was working just fine.
> > > > I am using Gnome/Wayland on Raspberry Pi 4 for a quite some
> > > > times,
> > > > and this the first time I face an issue with chromium.
> > > > 
> > > 
> > > Thanks for the report. What exactly was the previous version that
> > > worked
> > > for you?
> > 

Bug#1062714: qdbm: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qdbm
Version: 1.8.78-12
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qdbm 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 qdbm
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qdbm-1.8.78/debian/changelog qdbm-1.8.78/debian/changelog
--- qdbm-1.8.78/debian/changelog2022-11-02 21:02:48.0 +
+++ qdbm-1.8.78/debian/changelog2024-02-02 21:46:29.0 +
@@ -1,3 +1,10 @@
+qdbm (1.8.78-12.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 21:46:29 
+
+
 qdbm (1.8.78-12) unstable; urgency=medium
 
   * QA upload.
diff -Nru qdbm-1.8.78/debian/control qdbm-1.8.78/debian/control
--- qdbm-1.8.78/debian/control  2022-11-02 21:02:48.0 +
+++ qdbm-1.8.78/debian/control  2024-02-02 21:46:29.0 +
@@ -10,7 +10,10 @@
 XS-Ruby-Versions: all
 Section: libs
 
-Package: libqdbm14
+Package: libqdbm14t64
+Provides: ${t64:Provides}
+Replaces: libqdbm14
+Breaks: libqdbm14 (<< ${source:Version})
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: QDBM Database Libraries without GDBM wrapper[runtime]
@@ -32,7 +35,7 @@
 Package: libqdbm-dev
 Section: libdevel
 Architecture: any
-Depends: libqdbm14 (= ${binary:Version}), ${misc:Depends}
+Depends: libqdbm14t64 (= ${binary:Version}), ${misc:Depends}
 Recommends: pkg-config
 Suggests: qdbm-doc
 Description: QDBM Database Libraries [development]
@@ -57,11 +60,13 @@
 Description: QDBM Database CGI commands
  This is the QDBM Database command package to be used as CGI commands.
 
-Package: libxqdbm3c2
+Package: libxqdbm3t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libxqdbm3c2
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Replaces: libqdbm3++c2 (<< 1.8.77-1)
-Breaks: libqdbm3++c2 (<< 1.8.77-1)
+Replaces: libxqdbm3c2, libqdbm3++c2 (<< 1.8.77-1)
+Breaks: libxqdbm3c2 (<< ${source:Version}), libqdbm3++c2 (<< 1.8.77-1)
 Description: QDBM Database Libraries for C++ [runtime]
  QDBM is an embedded database library compatible with GDBM and NDBM.
  It features hash database and B+ tree database and is developed referring
@@ -73,7 +78,7 @@
 Package: libxqdbm-dev
 Architecture: any
 Section: libdevel
-Depends: libxqdbm3c2 (= ${binary:Version}), libqdbm-dev (= ${binary:Version}), 
${misc:Depends}
+Depends: libxqdbm3t64 (= ${binary:Version}), libqdbm-dev (= 
${binary:Version}), ${misc:Depends}
 Replaces: libqdbm-dev (<< 1.8.78-1)
 Suggests: qdbm-doc
 Description: QDBM Database Libraries for C++ [development]
@@ -84,7 +89,7 @@
 Package: libqdbm3++c2
 Architecture: any
 Section: oldlibs
-Depends: libxqdbm3c2 (>= ${binary:Version}), ${misc:Depends}
+Depends: libxqdbm3t64 (>= ${binary:Version}), ${misc:Depends}
 Multi-Arch: no
 Description: QDBM Database Libraries for C++ [runtime] (transitional package)
  This is a dummy package to ease transition to new package name.
diff -Nru qdbm-1.8.78/debian/libqdbm14.dirs qdbm-1.8.78/debian/libqdbm14.dirs
--- 

Bug#1062715: FTBFS against openturns 1.22-1 in experimental

[Pierre Gruet]

Source: persalys
Version: 15.0+ds-3
Severity: important
Tags: ftbfs

Hi,

persalys FTBFS against openturns/1.22-1 which is in experimental, waiting for a
transition. I am almost sure updating persalys to newest upstream version will
solve this. I will care for it soon.

-- 
Pierre

Bug#1062713: qd: NMU diff for 64-bit time_t transition

[Sergio Durigan Junior]

Source: qd
Version: 2.3.23+dfsg.1-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
qd 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 qd
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'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.5.0-5-amd64 (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
diff -Nru qd-2.3.23+dfsg.1/debian/changelog qd-2.3.23+dfsg.1/debian/changelog
--- qd-2.3.23+dfsg.1/debian/changelog   2022-02-20 12:58:54.0 +
+++ qd-2.3.23+dfsg.1/debian/changelog   2024-02-02 21:45:01.0 +
@@ -1,3 +1,10 @@
+qd (2.3.23+dfsg.1-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Sergio Durigan Junior   Fri, 02 Feb 2024 21:45:01 
+
+
 qd (2.3.23+dfsg.1-1) unstable; urgency=medium
 
   * New upstream release. Closes: #997255
diff -Nru qd-2.3.23+dfsg.1/debian/control qd-2.3.23+dfsg.1/debian/control
--- qd-2.3.23+dfsg.1/debian/control 2022-02-20 12:58:54.0 +
+++ qd-2.3.23+dfsg.1/debian/control 2024-02-02 21:45:01.0 +
@@ -18,7 +18,7 @@
 Package: libqd-dev
 Section: libdevel
 Architecture: any
-Depends: libqd0v5 (= ${binary:Version}), ${misc:Depends}
+Depends: libqd0t64 (= ${binary:Version}), ${misc:Depends}
 Recommmends: pkg-config
 Description: Double-double and quad double types in C++ and F90
  This package supports both a double-double datatype (approx. 32
@@ -28,11 +28,14 @@
  to convert an existing C++ or Fortran-90 program to use the library
  with only minor changes to the source code.
 
-Package: libqd0v5
+Package: libqd0t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libqd0v5
+Breaks: libqd0v5 (<< ${source:Version})
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Multi-Arch: same
-Replaces: libqd2c2a, libqd0
+Replaces: libqd0v5, libqd2c2a, libqd0
 Conflicts: libqd2c2a, libqd0
 Description: Double-double and quad double types in C++ and F90
  This package supports both a double-double datatype (approx. 32
diff -Nru qd-2.3.23+dfsg.1/debian/libqd0t64.install 
qd-2.3.23+dfsg.1/debian/libqd0t64.install
--- qd-2.3.23+dfsg.1/debian/libqd0t64.install   1970-01-01 00:00:00.0 
+
+++ qd-2.3.23+dfsg.1/debian/libqd0t64.install   2022-02-20 12:58:54.0 
+
@@ -0,0 +1,2 @@
+usr/lib/*/libqd*.so.* 
+
diff -Nru qd-2.3.23+dfsg.1/debian/libqd0t64.lintian-overrides 
qd-2.3.23+dfsg.1/debian/libqd0t64.lintian-overrides
--- qd-2.3.23+dfsg.1/debian/libqd0t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ qd-2.3.23+dfsg.1/debian/libqd0t64.lintian-overrides 2024-02-02 
21:45:01.0 +
@@ -0,0 +1 @@
+libqd0t64: package-name-doesnt-match-sonames libqd0v5
diff -Nru qd-2.3.23+dfsg.1/debian/libqd0v5.install 
qd-2.3.23+dfsg.1/debian/libqd0v5.install
--- qd-2.3.23+dfsg.1/debian/libqd0v5.install2022-02-20 12:58:54.0 
+
+++ qd-2.3.23+dfsg.1/debian/libqd0v5.install1970-01-01 00:00:00.0 
+
@@ -1,2 +0,0 @@
-usr/lib/*/libqd*.so.* 
-

Bug#1061603: openturns: FTBFS with Python 3.12 as default

[Pierre Gruet]

Control: tags -1 fixed-in-experimental
Control: fixed -1 1.22-1

Hi,

The issue is fixed in version 1.22-1 in experimental. It will have to 
wait there a little bit as there are a lot of transitions of 
dependencies going on due to the 64 bit time_t transition.


Best,

--
Pierre


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1062554: Acknowledgement (cups-browsed is not detecting any network printers)

[Jonathan Kamens]

*sigh* Ignore everything I said about my second laptop. The cups-browsed 
problem I originally reported persists, but I believe everything else 
was a PEBKAC issue. Sorry.

Bug#1062710: kanboard: CVE-2024-22720

[Salvatore Bonaccorso]

Source: kanboard
Version: 1.2.31+ds2-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/kanboard/kanboard/issues/5411
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for kanboard.

CVE-2024-22720[0]:
| Kanboard 1.2.34 is vulnerable to Html Injection in the group
| management feature.

I'm aware that the upstrema project is in maintenance mode only.

If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-22720
https://www.cve.org/CVERecord?id=CVE-2024-22720
[1] https://github.com/kanboard/kanboard/issues/5411

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1044073: python-altair: FTBFS with pandas 2.0

[Sandro Tosi]

> which is not packaged yet.  I had no luck to skip the according test which
> fails in build time test[2].

what did you try that failed to skip that test? this seems a
straightforward case where --ignore and/or -k "not " should be
enough.

please be more explicit when you ask for error and report what
attempts you made tht didnt work, so others will try other ways
without repeating previous unsuccessful ones

-- 
Sandro "morph" Tosi
My website: http://sandrotosi.me/
Me at Debian: http://wiki.debian.org/SandroTosi
Twitter: https://twitter.com/sandrotosi

Bug#1030668: dinstall could run more often (every hour?)

[Gioele Barabucci]

Control: tag -1 - moreinfo

On Mon, 06 Feb 2023 20:45:30 +0100 Ansgar  wrote:

> > Not sure what you mean.  Can you please explain the workflow you
> > are talking about?
> 
> The linked Michale Stapelberg's blog post explains it better than I

> can:
> 
> https://michael.stapelberg.ch/posts/2019-03-10-debian-winding-down/#old-infrastructure-package-uploads


That sounds like Michael didn't know about incoming.d.o which has been
publically accessible since 2014[1].

  [1]: https://lists.debian.org/debian-devel-announce/2014/08/msg8.html

Please explain what issues you have that are not solved by using incoming.d.o.


Not all services fetch their packages from incoming.d.o, for example 
britney.


So perhaps a way to alleviate this problem is to ask all official 
services to use incoming.d.o in addition to the regular unstable archive.


Regards,

--
Gioele Barabucci

Bug#1062709: python-aiohttp: CVE-2024-23334

[Salvatore Bonaccorso]

Source: python-aiohttp
Version: 3.9.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-aiohttp.

CVE-2024-23334[0]:
| aiohttp is an asynchronous HTTP client/server framework for asyncio
| and Python. When using aiohttp as a web server and configuring
| static routes, it is necessary to specify the root path for static
| files. Additionally, the option 'follow_symlinks' can be used to
| determine whether to follow symbolic links outside the static root
| directory. When 'follow_symlinks' is set to True, there is no
| validation to check if reading a file is within the root directory.
| This can lead to directory traversal vulnerabilities, resulting in
| unauthorized access to arbitrary files on the system, even when
| symlinks are not present.  Disabling follow_symlinks and using a
| reverse proxy are encouraged mitigations.  Version 3.9.2 fixes this
| issue.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-23334
https://www.cve.org/CVERecord?id=CVE-2024-23334
[1] https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5h86-8mv2-jq9f
[2] 
https://github.com/aio-libs/aiohttp/commit/9118a5831e8a65b8c839eb7e4ac983e040ff41df

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1062708: python-aiohttp: CVE-2024-23829

[Salvatore Bonaccorso]

Source: python-aiohttp
Version: 3.9.1-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for python-aiohttp.

CVE-2024-23829[0]:
| aiohttp is an asynchronous HTTP client/server framework for asyncio
| and Python. Security-sensitive parts of the Python HTTP parser
| retained minor differences in allowable character sets, that must
| trigger error handling to robustly match frame boundaries of proxies
| in order to protect against injection of additional requests.
| Additionally, validation could trigger exceptions that were not
| handled consistently with processing of other malformed input.
| Being more lenient than internet standards require could, depending
| on deployment environment, assist in request smuggling. The
| unhandled exception could cause excessive resource consumption on
| the application server and/or its logging facilities. This
| vulnerability exists due to an incomplete fix for CVE-2023-47627.
| Version 3.9.2 fixes this vulnerability.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2024-23829
https://www.cve.org/CVERecord?id=CVE-2024-23829
[1] https://github.com/aio-libs/aiohttp/security/advisories/GHSA-8qpw-xqxj-h4r2
[2] 
https://github.com/aio-libs/aiohttp/commit/d33bc21414e283c9e6fe7f6caf69e2ed60d66c82

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Bug#1043240: transition: pandas 1.5 -> 2.1 - please upload fixes

[Andreas Tille]

Hi Rebecca,

Am Tue, Jan 30, 2024 at 08:05:35AM + schrieb Rebecca N. Palmer:
> I intend to upload pandas 2.x to unstable soon.  These packages have a patch
> in their bug - please upload them (I'm a DM, I can't do that), or if you
> think this patch won't work or isn't a good idea, tell me why:
> dials

Was uploaded, all bugs closed.

> influxdb-python

I've answered to the bug[1] that the hints you gave seem to be incomplete.
Unfortunately I have no idea how to fix this.

> python-altair

I tried hard to get the latest version which implements what you suggested
independently in the bug report.  Unfortunately it needs a new dependency
as I wrote in my comment in the bug report[2] and I was not able to easily
exclude the test that fails due to the missing module.

> python-feather-format seaborn tqdm

I try to check later.
 
> In particular, I'd like the seaborn fix uploaded before pandas, so I can set
> Breaks for it.  (The pandas documentation build-depends on seaborn.)

I will check soon as long as noone will beat me in doing so.

Kind regards and thanks for all your work on pandas
   Andreas.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044076#43
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044073#23

-- 
http://fam-tille.de

Bug#1061444: pcscd: GDM user is NOT authorized for action: access_pcsc

[Ludovic Rousseau]

Hello,

Le 24/01/2024 à 22:07, Ludovic Rousseau a écrit :

Le 24/01/2024 à 19:43, Ludovic Rousseau a écrit :

Le 24/01/2024 à 18:09, Laurent Bigonville a écrit :

Package: pcscd
Version: 2.0.1-1
Severity: normal
X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org

Hello,

When looking at the logs of pcscd, I see the following messages:

jan 22 09:47:37 edoras pcscd[1663]:  auth.c:125:IsClientAuthorized() 
Error in authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: 
Process not found
jan 22 09:47:37 edoras pcscd[1663]: 0031 auth.c:143:IsClientAuthorized() 
Process 1565 (user: 115) is NOT authorized for action: access_pcsc

It seems that GDM is not allowed to talk to pcscd.

GDM has the functionality to detect whether there is a smartcard in the
reader and then use the gdm-smartcard PAM service instead of the
gdm-password one to perform login.

I guess that GDM should be whitelisted to allow it to use pcscd?


Exact.
Good point.

You can add polkit config file until I fix the issue.
https://blog.apdu.fr/posts/2023/11/pcsc-lite-and-polkit/


The fix is quite easy.
Create a new file /etc/polkit-1/rules.d/03-polkit-pcscd.rules containing:
polkit.addRule(function(action, subject) {
 if ((action.id == "org.debian.pcsc-lite.access_pcsc"
     || action.id == "org.debian.pcsc-lite.access_card")
     && subject.user == "Debian-gdm") {
     return polkit.Result.YES;
     }
});


What I don't know is if this new file should be provided by the pcscd package 
or by the gdm3 package.
I would say gdm3 but I am not sure.

I started a discussion on the pcsclite-muscle list at 
https://lists.infradead.org/pipermail/pcsclite-muscle/2024-January/001457.html


The problem is also present on Fedora 39.
It is surprising because Fedora has enabled polkit in pcsc-lite since a long 
time (2014?)

I opened a ticket at gdm upstream
https://gitlab.gnome.org/GNOME/gdm/-/issues/904

I think the fix should be provided by gdm itself.
So I reassign this ticket to the Debian gdm package.

Bye

--
Dr. Ludovic Rousseau

Bug#1044073: python-altair: FTBFS with pandas 2.0

[Andreas Tille]

Hi,

I tried to upgrade python-altair in Git to the latest upstream version
which should work with Pandas 2.0.  Unfortunately it has a new dependency[1]
which is not packaged yet.  I had no luck to skip the according test which
fails in build time test[2].

Kind regards
Andreas.

[1] https://pypi.org/project/anywidget/
[2] https://salsa.debian.org/python-team/packages/python-altair/-/jobs/5240584

-- 
http://fam-tille.de

Bug#1062665: [INTL:sv] Swedish strings for clamav debconf

[Anders Jonsson]

Hi Martin,
read through the translation and did some fixes, mostly typos. Changes 
can be seen in the diff, nothing controversial.



Regards,
Anders Jonsson# Translation of clamav to Swedish
# Copyright (C) 2024 Martin Bagge 
# This file is distributed under the same license as the clamav package.
#
# Martin Bagge , 2008-2011, 2024
msgid ""
msgstr ""
"Project-Id-Version: clamav_0.93~dfsg-1_sv\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-12-20 15:17+\n"
"PO-Revision-Date: 2024-02-02 16:08+0100\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Poedit-Language: Swedish\n"
"X-Poedit-Country: Sweden\n"

#. Type: select
#. Choices
#: ../clamav-freshclam.templates:2001
msgid "daemon"
msgstr "demon"

#. Type: select
#. Choices
#: ../clamav-freshclam.templates:2001
msgid "manual"
msgstr "manuell"

#. Type: select
#. Description
#: ../clamav-freshclam.templates:2002
msgid "Virus database update method:"
msgstr "Metod för uppdatering av virusdatabasen:"

#. Type: select
#. Description
#: ../clamav-freshclam.templates:2002
msgid "Please choose the method for virus database updates."
msgstr "Välj en metod för uppdatering av virusdatabasen."

#. Type: select
#. Description
#: ../clamav-freshclam.templates:2002
msgid ""
" daemon:  freshclam is running as a daemon all the time. You should choose\n"
"  this option if you have a permanent network connection;\n"
" ifup.d:  freshclam will be running as a daemon as long as your Internet\n"
"  connection is up. Choose this one if you use a dialup Internet\n"
"  connection and don't want freshclam to initiate new connections;\n"
" cron:freshclam is started from cron. Choose this if you want full "
"control\n"
"  of when the database is updated;\n"
" manual:  no automatic invocation of freshclam. This is not recommended,\n"
"  as ClamAV's database is constantly updated."
msgstr ""
" daemon :   freshclam körs som en daemon hela tiden. Du bör välja\n"
"denna om du har en permanent nätverksuppkoppling.\n"
" ifup.d :   freshclam kommer att köras som en daemon så längre som din\n"
"Internet förbindelse är igång. Välj denna om du har en uppringd\n"
"förbindelse och inte vill att freshclam ska skapa nya "
"uppkopplingar.\n"
" cron : freshclam startas från cron. Välj denna om du vill ha full "
"kontroll\n"
"när databasen ska uppdateras.\n"
" manuellt : Ingen automatiskt uppdatering av freshclam. Detta är inte\n"
"rekommenderat eftersom clamav's databas uppdateras ofta."

#. Type: select
#. Description
#: ../clamav-freshclam.templates:3001
msgid "Local database mirror site:"
msgstr "Lokal spegelsajt för databas:"

#. Type: select
#. Description
#: ../clamav-freshclam.templates:3001
msgid "Please select the closest local mirror site."
msgstr "Välj den närmaste lokala spegelsajten."

#. Type: select
#. Description
#: ../clamav-freshclam.templates:3001
msgid ""
"Freshclam updates its database from a world wide network of mirror sites. "
"Please select the closest mirror. If you leave the default setting, an "
"attempt will be made to guess a nearby mirror."
msgstr ""
"Freshclam uppdaterar sin databas från ett världsspännande nätverk av "
"spegelsajter.  Välj den spegel som är närmast dig.  Om du lämnar detta kvar "
"som standardvärdet kommer ett försök att göras att hitta en spegel närmast "
"dig men detta försök kanske inte alltid ger dig den närmaste spegelsajten."

#. Type: string
#. Description
#: ../clamav-freshclam.templates:4001
msgid "HTTP proxy information (leave blank for none):"
msgstr "HTTP-proxy information (lämna blank om du inte har en):"

#. Type: string
#. Description
#: ../clamav-freshclam.templates:4001
msgid ""
"If you need to use an HTTP proxy to access the outside world, enter the "
"proxy information here. Otherwise, leave this blank."
msgstr ""
"Om du behöver använda en HTTP-proxy för att få tillgång till världen "
"utanför, ange proxyinformationen här. Om inte, lämna denna blank."

#. Type: string
#. Description
#: ../clamav-freshclam.templates:4001
msgid "Please use URL syntax (\"http://host[:port]\;) here."
msgstr "Använd URL-syntax (\"http://värd[:port]\;) här."

#. Type: string
#. Description
#: ../clamav-freshclam.templates:5001
msgid "Proxy user information (leave blank for none):"
msgstr "Användarinformation för proxy (lämna blank om du inte har någon):"

#. Type: string
#. Description
#: ../clamav-freshclam.templates:5001
msgid ""
"If you need to supply a username and password to the proxy, enter it here. "
"Otherwise, leave this blank."
msgstr ""
"Om du behöver skicka med ett användarnamn och lösenord till proxyn, ange då "
"det här. Om inte, lämna fältet blankt."

#. Type: string
#. Description
#: ../clamav-freshclam.templates:5001
msgid "When entering user information, use the standard 

Bug#1062707: python3-django-hyperkitty: Cron errors with: allauth.account.middleware.AccountMiddleware must be added to settings.MIDDLEWARE

[Colin Turner]

Package: python3-django-hyperkitty
Version: 1.3.7-1
Severity: normal

Dear Maintainer,

Thanks for your work on these packages. After upgrade I am now getting these 
errors once a minute:

django.core.exceptions.ImproperlyConfigured: 
allauth.account.middleware.AccountMiddleware must be added to 
settings.MIDDLEWARE

This seems to relate to a mismatch between the MIDDLEWARE configuration, and 
the version of python3-django-allauth - which I don't seem to be able to easily 
downgrade.

The proposed workaround - to add these lines - presumably to 
/etc/mailman3/mailman3-web.py

x = list(MIDDLEWARE)
x.insert(0, 'allauth.account.middleware.AccountMiddleware')
MIDDLEWARE = x

does not work, unfortunately.

I'm not sure is this affects all upgraded users, but for now the package isn't 
functional (internal server error).

Kind regards and thanks,

CT.

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'unstable'), 
(500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.4.0-2-amd64 (SMP w/4 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages python3-django-hyperkitty depends on:
ii  fonts-font-awesome   5.0.10+really4.7.0~dfsg-4.1
ii  fonts-glyphicons-halflings   1.009~3.4.1+dfsg-3
ii  libjs-bootstrap4 4.6.1+dfsg1-4
ii  libjs-jquery 3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-ui  1.13.2+dfsg-1
ii  libjs-sphinxdoc  7.2.6-3
ii  python3  3.11.6-1
ii  python3-dateutil 2.8.2-3
ii  python3-django   3:3.2.21-1
ii  python3-django-compressor4.0-4
ii  python3-django-extensions3.2.3-1
ii  python3-django-gravatar2 1.4.4-4
ii  python3-django-haystack  3.2.1-1
ii  python3-django-mailman3  1.3.11-1
ii  python3-django-q 1.6.1-1
ii  python3-djangorestframework  3.14.0-2
ii  python3-elasticsearch7.17.6-1
ii  python3-flufl.lock   5.0.1-5
ii  python3-mailmanclient3.3.5-1
ii  python3-mistune  3.0.2-1
ii  python3-networkx 2.8.8-1
ii  python3-robot-detection  0.4.0-3
ii  python3-tz   2023.3.post1-2

Versions of packages python3-django-hyperkitty recommends:
ii  mailman3-web  0+20200530-2.1

python3-django-hyperkitty suggests no packages.

-- no debconf information

Bug#1055434: libwebp: diff for NMU version 1.3.2-0.4

[Boyuan Yang]

Control: tags 1055434 + patch
Control: tags 1055434 + pending

Dear maintainer,

I've prepared an NMU for libwebp (versioned as 1.3.2-0.4) and
uploaded it to DELAYED/14. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru libwebp-1.3.2/debian/changelog libwebp-1.3.2/debian/changelog
--- libwebp-1.3.2/debian/changelog  2023-09-22 03:41:18.0 -0400
+++ libwebp-1.3.2/debian/changelog  2024-02-02 15:27:04.0 -0500
@@ -1,3 +1,13 @@
+libwebp (1.3.2-0.4) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/control: Introduce pkg.libwebp.notiff build profile to
+break the build-dep loop between libwebp and tiff. Mark build-dep
+libtiff-dev with .
+(Closes: #1055434)
+
+ -- Boyuan Yang   Fri, 02 Feb 2024 15:27:04 -0500
+
 libwebp (1.3.2-0.3) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libwebp-1.3.2/debian/control libwebp-1.3.2/debian/control
--- libwebp-1.3.2/debian/control2023-09-22 03:41:18.0 -0400
+++ libwebp-1.3.2/debian/control2024-02-02 15:27:00.0 -0500
@@ -10,7 +10,7 @@
  libglut-dev,
  libjpeg-dev,
  libpng-dev,
- libtiff-dev,
+ libtiff-dev ,
  pkg-config,
 Standards-Version: 4.6.2
 Vcs-Browser: https://salsa.debian.org/debian/libwebp


signature.asc
Description: This is a digitally signed message part

Bug#1055434: libwebp <-> tiff build-dep loop

[Boyuan Yang]

X-Debbugs-CC: sthiba...@debian.org

On Thu, 11 Jan 2024 19:44:10 +0100 Samuel Thibault  wrote:
> Hello,
> 
> Boyuan Yang, le jeu. 11 janv. 2024 13:37:45 -0500, a ecrit:
> > On Mon, 6 Nov 2023 01:42:57 +0100 Samuel Thibault  
> > wrote:
> > > There is a direct build-depend loop between libwebp and tiff. Could you
> > > introduce a notiff build profile in order to break this loop? Otherwise
> > > one can't seamlessly bootstrap new Debian ports.
> > 
> > According to 
> > https://wiki.debian.org/BuildProfileSpec#Adding_new_profiles_to_this_registry
> >  ,
> > adding a new build profile may need some discussion to reach a consensus. 
> > Do you
> > think it is necessary to start a discussion on debian-devel for notiff 
> > profile?
> 
> AIUI that is for cross-packages profiles. Packages themselves can freely
> add their own profile names, see pkg.$sourcepackage.$anything in
> https://wiki.debian.org/BuildProfileSpec#Registered_profile_names
> 
> e.g. here pkg.libwebp.notiff.

Thanks for the explanation. I am preparing a new upload (as deferred NMU) for 
this targeted fix.

Regards,
Boyuan Yang


signature.asc
Description: This is a digitally signed message part

Bug#1062706: ITP: python-pyhanko-certvalidator -- Validates X.509 certificates and paths

[Bastian Germann]

Package: wnpp
Severity: wishlist
Owner: Bastian Germann 

* Package name: python-pyhanko-certvalidator
* URL : https://github.com/MatthiasValvekens/certvalidator
* License : Expat
  Programming Lang: Python
  Description : Validates X.509 certificates and paths

 A Python library that offers functionality for validating X.509 digital
 certificates, which are widely used in security systems such
 as TLS/SSL, email encryption, PDF signatures, and more.

 The pyhanko-certvalidator library performs the following main tasks:
  - Certificate Validation: The library checks the validity of X.509
digital certificates. This includes checking the certificate signature,
expiration date, issuing authority (CA), certificate revocation, and
other important properties.
  - Chain of Trust: It helps to build and validate the certificate chain,
that is, the sequence of certificates that links a specific certificate
to a trusted certification authority (root CA).
  - CRL (Certificate Revocation Lists) Check: The library checks whether a
certificate has been revoked by querying Certificate Revocation Lists
(CRLs) published by certification authorities.
  - Online Certificate Status Protocol (OCSP) Check: In addition to CRL
checking, certvalidator can check the status of a certificate through
the Online Certificate Status Protocol (OCSP) to determine whether the
certificate is still valid.
  - Custom Expiration Policy: You can configure and apply custom validity
policies to meet specific certificate validation requirements.
  - Extensibility: The library is designed to be extensible and customizable.

 This is a fork of the python-certvalidator package.
 I need it in order to package pyhanko.

Bug#1062532: Accepted runc 1.1.12+ds1-1 (source) into unstable

[Salvatore Bonaccorso]

Source: runc
Source-Version: 1.1.12+ds1-1
Control: fixed 1062532 1.0.0~rc93+ds1-5+deb11u3
Control: fixed 1062532 1.1.5+ds1-1+deb12u1

This fixes #1062532. Adding as well the fixed version for the pending
runc update via bullseye-security and bookworm-security.

- Forwarded message from Debian FTP Masters 
 -

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 02 Feb 2024 21:20:26 +0800
Source: runc
Architecture: source
Version: 1.1.12+ds1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Shengjing Zhu 
Changes:
 runc (1.1.12+ds1-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 1.1.12+ds1
 + CVE-2024-21626: several container breakouts due to internally leaked fds
Checksums-Sha1:
 5bef8274f96e27dcf68992efe30b8f372807e0ad 2772 runc_1.1.12+ds1-1.dsc
 937c3fe186bca9df98b96c4f1b1354a89092d66c 528632 runc_1.1.12+ds1.orig.tar.xz
 6520a024c7ba75259db6a396e7bd95c245281cdb 14768 runc_1.1.12+ds1-1.debian.tar.xz
 adc4f0be51d402e882acc7bfcab17b2404c26a39 8215 runc_1.1.12+ds1-1_amd64.buildinfo
Checksums-Sha256:
 848316908f87dc5d286cf381d4bee523c495327cab033b9aa59b154a1d37d2c6 2772 
runc_1.1.12+ds1-1.dsc
 ab7ab8842157c9607f450cf1f2cc7dc2a61cc134766c27111d0e113bdd41d6a8 528632 
runc_1.1.12+ds1.orig.tar.xz
 367dfbddbc0b6bb3b06ef60dd21d6a006b1b7fdedab882bd861e14889516b419 14768 
runc_1.1.12+ds1-1.debian.tar.xz
 ab4810f32b977a6f811a24c206cef248f1e98d21561cfb5e5eb012570a37b4d8 8215 
runc_1.1.12+ds1-1_amd64.buildinfo
Files:
 d2ecde618e10f3096c71dff70088339e 2772 admin optional runc_1.1.12+ds1-1.dsc
 2c788fe39dea435e8db8e5baceba60e0 528632 admin optional 
runc_1.1.12+ds1.orig.tar.xz
 6056fd3324edcb874b3d1b732cca1d08 14768 admin optional 
runc_1.1.12+ds1-1.debian.tar.xz
 b981612583fa02cb52aa8ebb427fd757 8215 admin optional 
runc_1.1.12+ds1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEc793ixFTU9Vien7Zh7Iv85yjO70FAmW87XUACgkQh7Iv85yj
O718SQf+J8O0B8ZD224eAg4Q3HpeG5hFFUaVWxRLpvBXfs5XQI1/Rl+SrnElLSRw
inX9kZaUK/cIcs5E8gxiYl+o2Hf+qDjdTqziBt/j8HkTk7Gp4z5oFVX5I7JrnaH6
Xw3AeQ8yzPC8d3DPR7p3VMGRJwXrxV/Ox8ZB7Vd7HGB/pC5nzGzGbMaq+LwAy/nH
lY1GmdJkjj1cusFhgSs01hbNtZTJCVoBupBF4YdMmA6n/O6t7Rr7ZASks29u4jxo
qd1JgFNJJciZ3SZjtY76AFwfg0sWV+OmY5oEVa7qgA1xeoIxPwWnhlYUeSueNmTJ
Gxn9fh8uPucRpuqxg7RTfU3Ml9Pr5A==
=mnTr
-END PGP SIGNATURE-


- End forwarded message -

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

[Diederik de Haas]

On Friday, 2 February 2024 20:10:53 CET Miguel Angel wrote:
> Package: firmware-realtek
> Version: 20230625-2
> Severity: important
> X-Debbugs-Cc: mianro...@gmail.com
> 
> At system boot, the following message is shown:
> "Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2".
> 
> It seesm that the firmware is not properly loaded by kernel at boot.

Can you provide the dmesg output which would show that?
Doesn't have to be the full dmesg output, but don't 'grep' for it either as 
that will likely filter out the surrounding lines which are often relevant.

https://packages.debian.org/sid/all/firmware-realtek/filelist does show 
``rtl_nic/rtl8125b-2.fw``, so I'm a bit surprised.

signature.asc
Description: This is a digitally signed message part.

Bug#1062705: sq: please provide manpages

[Daniel Kahn Gillmor]

Package: sq
Version: 0.33.0-2

sq upstream has some pretty good manpage coverage.  However, the sq
package no longer seems to ship any man pages.

It would be great to ensure that the upstream manpages are generated at
build time, and shipped with the sq package.

Thanks,

--dkg


signature.asc
Description: PGP signature

Bug#1062679: lxc: NMU diff for 64-bit time_t transition

[Mathias Gibbens]

  ACK -- I won't plan to make any uploads of src:lxc to unstable until
after the time_t transition is complete.

  For the team, I've applied the NMU to the debian/experimental branch
up in salsa.

Mathias


signature.asc
Description: This is a digitally signed message part

Bug#1062704: python-certvalidator: Please make it team-maintained

[Bastian Germann]

Source: python-certvalidator

python-certvalidator is located in the Python Team's salsa namespace
but it is not team-maintained via d/control's Maintainer or Uploaders fields.
Please fix that.

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

[Miguel Angel]

Package: firmware-realtek
Version: 20230625-2
Severity: important
X-Debbugs-Cc: mianro...@gmail.com

At system boot, the following message is shown: 
"Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2".

It seesm that the firmware is not properly loaded by kernel at boot. 


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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

firmware-realtek depends on no packages.

firmware-realtek recommends no packages.

Versions of packages firmware-realtek suggests:
ii  initramfs-tools  0.142

-- no debconf information

Bug#1062702: libomp-dev: Program which has run for ten years crashed after distribution upgrade

[William Melgaard]

Package: libomp-dev
Version: 1:14.0-55.7~deb12u1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: piob...@mindspring.com

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 12.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-13-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libomp-dev depends on:
ii  libomp-14-dev  1:14.0.6-12

libomp-dev recommends no packages.

libomp-dev suggests no packages.

-- no debconf information
Program containing omp pragma failed after dist upgrade

[CODE]
// oomptest.c
// compile as gcc oomptest.c -o oomp -lm -fopenmp

#include 
#include 
#include 

int omp_get_max_threads(void);
int omp_get_thread_num(void);

void subroutine(float *subject, float *object, int index){
  object[index] -= subject[0];
}


int main(int argc, char* argv[]){
int i, id;
float v0[2] = {13579, 24680}, v1[5]={1, 3, 5, 7, 9};

#pragma omp parallel num_threads(5) private (id)
{
id = omp_get_thread_num(); printf("line 22 id=%d\n", id);
subroutine([1], [id], id);
}
for(i=0; i<5; i++)printf("v1[%d] = %f\n", i, v1[i]);

}[/CODE]
output from test program
"

line 22 id=0
line 22 id=3
line 22 id=1
line 22 id=2
line 22 id=4
v1[0] = -24679.00
v1[1] = 3.00
v1[2] = -24675.00
v1[3] = 7.00
v1[4] = -24671.00
"
expected output from test program
>
line 22 id=0
line 22 id=3
line 22 id=1
line 22 id=2
line 22 id=4
v1[0] = -24679.00
v1[1] = -24677.00
v1[2] = -24675.00
v1[3] = -24673.00
v1[4] = -24671.00
"

Bug#1062701: benchmark: Please use /usr/bin/python3 instead of /usr/bin/env python3

[Thomas Uhle]

Source: benchmark
Version: 1.8.3-3
Severity: normal
Control: affects -1 libbenchmark-tools

Dear maintainers,

could you please add the following lines to debian/rules:

override_dh_python3:
dh_python3 --shebang=/usr/bin/python3 /usr/share/benchmark

Thank you in advance!

Best regards,

Thomas Uhle

Bug#1062699: lirc: regression due to changed build dependencies in version 0.10.2-0.5

[Thomas Uhle]

Source: lirc
Version: 0.10.2-0.5
Severity: serious
X-Debbugs-CC: 1060...@bugs.debian.org

Dear maintainers, dear Gianfranco,

unfortunately, you have not exchanged systemd by systemd-dev but 
libsystemd-dev by systemd-dev instead.  So libsystemd-dev is no longer 
a build dependency and so /usr/sbin/lircd is no longer build with 
libsystemd.so for instance.  Could you please fix that.


Thank you in advance!

Best regards,

Thomas Uhle

Bug#1062698: libtirpc: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libtirpc
Version: 1.3.4+ds-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libtirpc 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 libtirpc
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)
diff -Nru libtirpc-1.3.4+ds/debian/changelog libtirpc-1.3.4+ds/debian/changelog
--- libtirpc-1.3.4+ds/debian/changelog  2023-11-12 23:45:44.0 +
+++ libtirpc-1.3.4+ds/debian/changelog  2024-02-02 08:35:04.0 +
@@ -1,3 +1,18 @@
+libtirpc (1.3.4+ds-1.1~exp1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+  * Move library to /usr/; Closes: #1055959
+  * debian/libtirpc3t64.preinst: implement 'Protective diversions' (M8 
+from https://subdivi.de/~helmut/dep17.html) to avoid files accidentally
+being deleted on upgrade when moving between packages and also moving
+between /lib and /usr/lib.  Because this package is present in the
+bootstrap set in some configurations, these diversions must be kept
+around until forky rather than being immediately removed in the
+postinst.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 08:35:04 +
+
 libtirpc (1.3.4+ds-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru libtirpc-1.3.4+ds/debian/clean libtirpc-1.3.4+ds/debian/clean
--- libtirpc-1.3.4+ds/debian/clean  2023-11-12 23:45:44.0 +
+++ libtirpc-1.3.4+ds/debian/clean  2024-02-02 08:35:04.0 +
@@ -1 +1,2 @@
 src/config.h
+debian/libtirpc3t64.preinst
diff -Nru libtirpc-1.3.4+ds/debian/control libtirpc-1.3.4+ds/debian/control
--- libtirpc-1.3.4+ds/debian/control2023-11-12 23:45:44.0 +
+++ libtirpc-1.3.4+ds/debian/control2024-02-02 08:35:04.0 +
@@ -13,7 +13,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libtirpc3 (= ${binary:Version}), ${misc:Depends}
+Depends: libtirpc3t64 (= ${binary:Version}), ${misc:Depends}
 Description: transport-independent RPC library - development files
  This package contains a port of Sun's transport-independent RPC library to
  Linux. The library is intended as a replacement for the RPC code in the GNU C
@@ -21,12 +21,14 @@
  .
  This package contains the files needed for development against libtirpc.
 
-Package: libtirpc3
+Package: libtirpc3t64
+Provides: ${t64:Provides}
+Replaces: libtirpc3
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}, libtirpc-common (>= 
${source:Version})
-Breaks: nfs-common (<< 1:1.2.8-7), nfs-kernel-server (<< 1:1.2.8-7)
+Breaks: libtirpc3 (<< ${source:Version}), nfs-common (<< 1:1.2.8-7), 
nfs-kernel-server (<< 1:1.2.8-7)
 Description: transport-independent RPC library
  This package contains a port of Sun's transport-independent RPC library to
  Linux. The library is intended as a replacement for the RPC code in the GNU C
@@ -36,8 +38,8 @@
 Architecture: all
 Multi-Arch: foreign
 Depends: ${misc:Depends}
-Breaks: libtirpc1, libtirpc3 (<< 1.1.4-0.1~)
-Replaces: 

Bug#1062697: libvformat: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libvformat
Version: 1.13-12
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libvformat 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 libvformat
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)
diff -Nru libvformat-1.13/debian/changelog libvformat-1.13/debian/changelog
--- libvformat-1.13/debian/changelog2020-08-10 21:55:14.0 +
+++ libvformat-1.13/debian/changelog2024-02-02 18:18:56.0 +
@@ -1,3 +1,10 @@
+libvformat (1.13-12.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:18:56 +
+
 libvformat (1.13-12) unstable; urgency=medium
 
   [ Thomas Preud'homme ]
diff -Nru libvformat-1.13/debian/control libvformat-1.13/debian/control
--- libvformat-1.13/debian/control  2020-08-10 21:55:14.0 +
+++ libvformat-1.13/debian/control  2024-02-02 18:18:56.0 +
@@ -13,7 +13,7 @@
 Package: libvformat-dev
 Section: libdevel
 Architecture: any
-Depends: libvformat0 (= ${binary:Version}), ${misc:Depends}
+Depends: libvformat0t64 (= ${binary:Version}), ${misc:Depends}
 Description: library to read and write vcard files (development files)
  This library provides an interface to vcard files according
  to the definitions laid down in the rfc2426.
@@ -21,7 +21,10 @@
  This package contains the development headers for the library found in
  libvformat0.
 
-Package: libvformat0
+Package: libvformat0t64
+Provides: ${t64:Provides}
+Replaces: libvformat0
+Breaks: libvformat0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
diff -Nru libvformat-1.13/debian/libvformat0.install 
libvformat-1.13/debian/libvformat0.install
--- libvformat-1.13/debian/libvformat0.install  2020-08-10 21:55:14.0 
+
+++ libvformat-1.13/debian/libvformat0.install  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/libvformat*.so.*
diff -Nru libvformat-1.13/debian/libvformat0.shlibs 
libvformat-1.13/debian/libvformat0.shlibs
--- libvformat-1.13/debian/libvformat0.shlibs   2020-08-10 21:55:14.0 
+
+++ libvformat-1.13/debian/libvformat0.shlibs   1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-libvformat 0 libvformat0 (>= 1.13-6)
diff -Nru libvformat-1.13/debian/libvformat0.symbols 
libvformat-1.13/debian/libvformat0.symbols
--- libvformat-1.13/debian/libvformat0.symbols  2020-08-10 21:55:14.0 
+
+++ libvformat-1.13/debian/libvformat0.symbols  1970-01-01 00:00:00.0 
+
@@ -1,61 +0,0 @@
-libvformat.so.0 libvformat0 #MINVER#
-* Build-Depends-Package: libvformat-dev
- _vf_free@Base 1.13-6~
- _vf_malloc@Base 1.13-6~
- _vf_realloc@Base 1.13-6~
- _vf_stdlib_free@Base 1.13-6~
- _vf_stdlib_malloc@Base 1.13-6~
- _vf_stdlib_realloc@Base 1.13-6~
- add_string_to_array@Base 1.13-6~
- append_to_curr_string@Base 1.13-6~
- append_to_pointer@Base 1.13-6~
- delete_prop_contents@Base 1.13-6~
- free_string_array_contents@Base 1.13-6~
- mark_property_modified@Base 1.13-6~
- 

Bug#1062696: libverto: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libverto
Version: 0.3.1-1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libverto 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 libverto
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)
diff -Nru libverto-0.3.1/debian/changelog libverto-0.3.1/debian/changelog
--- libverto-0.3.1/debian/changelog 2020-06-08 13:37:48.0 +
+++ libverto-0.3.1/debian/changelog 2024-02-02 18:18:10.0 +
@@ -1,3 +1,10 @@
+libverto (0.3.1-1.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:18:10 +
+
 libverto (0.3.1-1) unstable; urgency=medium
 
   [ Debian Janitor ]
diff -Nru libverto-0.3.1/debian/control libverto-0.3.1/debian/control
--- libverto-0.3.1/debian/control   2020-06-08 13:34:34.0 +
+++ libverto-0.3.1/debian/control   2024-02-02 18:18:10.0 +
@@ -12,7 +12,7 @@
 Package: libverto-dev
 Section: libdevel
 Architecture: any
-Depends: ${misc:Depends}, libverto1 (= ${binary:Version}), libverto-glib1 (= 
${binary:Version}), libverto-libev1 (= ${binary:Version})
+Depends: ${misc:Depends}, libverto1t64 (= ${binary:Version}), 
libverto-glib1t64 (= ${binary:Version}), libverto-libev1t64 (= 
${binary:Version})
 Description: Event loop abstraction for Libraries - Development
  Libverto exists to isolate libraries from the particular event loop
  chosen by an application. Libverto provides an asynchronous
@@ -22,7 +22,10 @@
  .
  This package includes development libraries.
 
-Package: libverto1
+Package: libverto1t64
+Provides: ${t64:Provides}
+Replaces: libverto1
+Breaks: libverto1 (<< ${source:Version})
 Section: libs
 Architecture: any
 PRe-Depends: ${misc:Pre-Depends}
@@ -37,7 +40,10 @@
  .
  This package includes the main runtime library.
 
-Package: libverto-libev1
+Package: libverto-libev1t64
+Provides: ${t64:Provides}
+Replaces: libverto-libev1
+Breaks: libverto-libev1 (<< ${source:Version})
 Section: libs
 Architecture: any
 PRe-Depends: ${misc:Pre-Depends}
@@ -52,7 +58,10 @@
  .
  This package includes support for the libev event loop.
 
-Package: libverto-glib1
+Package: libverto-glib1t64
+Provides: ${t64:Provides}
+Replaces: libverto-glib1
+Breaks: libverto-glib1 (<< ${source:Version})
 Section: libs
 Architecture: any
 PRe-Depends: ${misc:Pre-Depends}
diff -Nru libverto-0.3.1/debian/libverto-glib1.install 
libverto-0.3.1/debian/libverto-glib1.install
--- libverto-0.3.1/debian/libverto-glib1.install2014-05-29 
00:36:01.0 +
+++ libverto-0.3.1/debian/libverto-glib1.install1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/libverto-glib.so.*
diff -Nru libverto-0.3.1/debian/libverto-glib1t64.install 
libverto-0.3.1/debian/libverto-glib1t64.install
--- libverto-0.3.1/debian/libverto-glib1t64.install 1970-01-01 
00:00:00.0 +
+++ libverto-0.3.1/debian/libverto-glib1t64.install 2014-05-29 
00:36:01.0 +
@@ -0,0 +1 @@

Bug#1062694: libuv1: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libuv1
Version: 1.46.0-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libuv1 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 libuv1
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)
diff -Nru libuv1-1.46.0/debian/changelog libuv1-1.46.0/debian/changelog
--- libuv1-1.46.0/debian/changelog  2023-12-30 17:32:28.0 +
+++ libuv1-1.46.0/debian/changelog  2024-02-02 18:16:37.0 +
@@ -1,3 +1,10 @@
+libuv1 (1.46.0-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:16:37 +
+
 libuv1 (1.46.0-3) unstable; urgency=medium
 
   * add patch to fix build on kernel < 5.10.186.
diff -Nru libuv1-1.46.0/debian/control libuv1-1.46.0/debian/control
--- libuv1-1.46.0/debian/control2023-12-30 17:32:28.0 +
+++ libuv1-1.46.0/debian/control2024-02-02 18:16:37.0 +
@@ -19,7 +19,7 @@
 Multi-Arch: same
 Section: libdevel
 Depends: ${misc:Depends},
- libuv1 (= ${binary:Version})
+ libuv1t64 (= ${binary:Version})
 Conflicts: libuv-dev
 Replaces: libuv-dev
 Description: asynchronous event notification library - development files
@@ -38,7 +38,10 @@
  Install this package if you wish to develop your own programs using the
  libuv engine.
 
-Package: libuv1
+Package: libuv1t64
+Provides: ${t64:Provides}
+Replaces: libuv1
+Breaks: libuv1 (<< ${source:Version})
 Architecture: linux-any hurd-any
 Multi-Arch: same
 Depends: ${misc:Depends},
diff -Nru libuv1-1.46.0/debian/libuv1.install 
libuv1-1.46.0/debian/libuv1.install
--- libuv1-1.46.0/debian/libuv1.install 2023-12-30 17:32:28.0 +
+++ libuv1-1.46.0/debian/libuv1.install 1970-01-01 00:00:00.0 +
@@ -1,2 +0,0 @@
-#!/usr/bin/dh-exec
-usr/lib/*/libuv.so.1* usr/lib/${DEB_HOST_MULTIARCH}/
diff -Nru libuv1-1.46.0/debian/libuv1.symbols 
libuv1-1.46.0/debian/libuv1.symbols
--- libuv1-1.46.0/debian/libuv1.symbols 2023-12-30 17:32:28.0 +
+++ libuv1-1.46.0/debian/libuv1.symbols 1970-01-01 00:00:00.0 +
@@ -1,413 +0,0 @@
-libuv.so.1 libuv1 #MINVER#
-* Build-Depends-Package: libuv1-dev
-#MISSING: 1.46.0-2# (regex|optional)"^uv__" 1.0
-#MISSING: 1.46.0-2# (arch=linux-any|optional)uv__accept4@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__accept@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__async_close@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__async_fork@Base 1.18.0
-#MISSING: 1.46.0-2# (optional)uv__async_stop@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__calloc@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__check_close@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__cloexec_fcntl@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__cloexec_ioctl@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__close@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__close_nocheckstdio@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__count_bufs@Base 1.11.0
-#MISSING: 1.46.0-2# (optional)uv__dup2_cloexec@Base 1.11.0
-#MISSING: 1.46.0-2# 

Bug#1062695: libvbz-hdf-plugin: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libvbz-hdf-plugin
Version: 1.0.2-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libvbz-hdf-plugin 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 libvbz-hdf-plugin
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)
diff -Nru libvbz-hdf-plugin-1.0.2/debian/changelog 
libvbz-hdf-plugin-1.0.2/debian/changelog
--- libvbz-hdf-plugin-1.0.2/debian/changelog2023-07-23 08:52:45.0 
+
+++ libvbz-hdf-plugin-1.0.2/debian/changelog2024-02-02 18:17:23.0 
+
@@ -1,3 +1,10 @@
+libvbz-hdf-plugin (1.0.2-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:17:23 +
+
 libvbz-hdf-plugin (1.0.2-3) unstable; urgency=medium
 
   * gcc-13.patch: new: fix build failures with gcc 13. (Closes: #1037746)
diff -Nru libvbz-hdf-plugin-1.0.2/debian/control 
libvbz-hdf-plugin-1.0.2/debian/control
--- libvbz-hdf-plugin-1.0.2/debian/control  2023-07-23 08:52:45.0 
+
+++ libvbz-hdf-plugin-1.0.2/debian/control  2024-02-02 18:17:23.0 
+
@@ -16,7 +16,10 @@
 Homepage: https://github.com/nanoporetech/vbz_compression/
 Rules-Requires-Root: no
 
-Package: libvbz-hdf-plugin0
+Package: libvbz-hdf-plugin0t64
+Provides: ${t64:Provides}
+Replaces: libvbz-hdf-plugin0
+Breaks: libvbz-hdf-plugin0 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends},
@@ -38,7 +41,7 @@
 Package: libvbz-hdf-plugin-dev
 Architecture: any
 Section: libdevel
-Depends: libvbz-hdf-plugin0 (= ${binary:Version}),
+Depends: libvbz-hdf-plugin0t64 (= ${binary:Version}),
  ${shlibs:Depends},
  ${misc:Depends}
 Multi-Arch: same
diff -Nru libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.install 
libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.install
--- libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.install   2023-07-23 
08:52:45.0 +
+++ libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.install   1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.lintian-overrides 
libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.lintian-overrides
--- libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.lintian-overrides 
2023-07-23 08:52:45.0 +
+++ libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0.lintian-overrides 
1970-01-01 00:00:00.0 +
@@ -1,2 +0,0 @@
-# See https://wiki.debian.org/UsingSymbolsFiles#C.2B-.2B-_libraries
-libvbz-hdf-plugin0: no-symbols-control-file
diff -Nru libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0t64.install 
libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0t64.install
--- libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0t64.install
1970-01-01 00:00:00.0 +
+++ libvbz-hdf-plugin-1.0.2/debian/libvbz-hdf-plugin0t64.install
2023-07-23 08:52:45.0 +
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru 

Bug#1062693: libusbgx: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libusbgx
Version: 0.2.0-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libusbgx 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 libusbgx
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)
diff -Nru libusbgx-0.2.0/debian/changelog libusbgx-0.2.0/debian/changelog
--- libusbgx-0.2.0/debian/changelog 2023-08-28 13:49:05.0 +
+++ libusbgx-0.2.0/debian/changelog 2024-02-02 18:15:56.0 +
@@ -1,3 +1,10 @@
+libusbgx (0.2.0-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:15:56 +
+
 libusbgx (0.2.0-3) unstable; urgency=medium
 
   * Fix clean target (Closes: #1049287)
diff -Nru libusbgx-0.2.0/debian/control libusbgx-0.2.0/debian/control
--- libusbgx-0.2.0/debian/control   2023-08-28 13:49:05.0 +
+++ libusbgx-0.2.0/debian/control   2024-02-02 18:15:55.0 +
@@ -18,7 +18,7 @@
 Architecture: any
 Multi-Arch: same
 Depends:
- libusbgx2 (= ${binary:Version}),
+ libusbgx2t64 (= ${binary:Version}),
  ${misc:Depends},
 Description: Development files for libusbgx
  It provides routines for creating and parsing USB gadget devices using
@@ -43,7 +43,10 @@
  This package contains the document files like examples files,
  and doxygen generated API documentation.
 
-Package: libusbgx2
+Package: libusbgx2t64
+Provides: ${t64:Provides}
+Replaces: libusbgx2
+Breaks: libusbgx2 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends:
diff -Nru libusbgx-0.2.0/debian/libusbgx2.install 
libusbgx-0.2.0/debian/libusbgx2.install
--- libusbgx-0.2.0/debian/libusbgx2.install 2023-08-28 13:49:05.0 
+
+++ libusbgx-0.2.0/debian/libusbgx2.install 1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/${DEB_HOST_MULTIARCH}/lib*.so.*
diff -Nru libusbgx-0.2.0/debian/libusbgx2.symbols 
libusbgx-0.2.0/debian/libusbgx2.symbols
--- libusbgx-0.2.0/debian/libusbgx2.symbols 2023-08-28 13:49:05.0 
+
+++ libusbgx-0.2.0/debian/libusbgx2.symbols 1970-01-01 00:00:00.0 
+
@@ -1,217 +0,0 @@
-libusbgx.so.2 libusbgx2 #MINVER#
-* Build-Depends-Package: libusbgx-dev
- function_types@Base 0.2.0
- gadget_attr_names@Base 0.2.0
- gadget_os_desc_names@Base 0.2.0
- gadget_str_names@Base 0.2.0
- hid_attr@Base 0.2.0
- init_luns@Base 0.2.0
- midi_attr@Base 0.2.0
- usbg_add_config_function@Base 0.2.0
- usbg_check_dir@Base 0.2.0
- usbg_cleanup@Base 0.2.0
- usbg_cleanup_function@Base 0.2.0
- usbg_cleanup_function_attrs@Base 0.2.0
- usbg_create_config@Base 0.2.0
- usbg_create_function@Base 0.2.0
- usbg_create_gadget@Base 0.2.0
- usbg_create_gadget_vid_pid@Base 0.2.0
- usbg_disable_gadget@Base 0.2.0
- usbg_enable_gadget@Base 0.2.0
- usbg_error_name@Base 0.2.0
- usbg_ether_ntoa_r@Base 0.2.0
- usbg_export_config@Base 0.2.0
- usbg_export_function@Base 0.2.0
- usbg_export_gadget@Base 0.2.0
- usbg_f_fs_get_dev_name@Base 0.2.0
- usbg_f_fs_get_dev_name_s@Base 0.2.0
- usbg_f_hid_get_attr_val@Base 0.2.0

Bug#1062691: liburcu: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: liburcu
Version: 0.14.0-3
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
liburcu 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 liburcu
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)
diff -Nru liburcu-0.14.0/debian/changelog liburcu-0.14.0/debian/changelog
--- liburcu-0.14.0/debian/changelog 2024-01-15 21:55:05.0 +
+++ liburcu-0.14.0/debian/changelog 2024-02-02 18:14:20.0 +
@@ -1,3 +1,10 @@
+liburcu (0.14.0-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:14:20 +
+
 liburcu (0.14.0-3) unstable; urgency=medium
 
   * [d3fc511] Enable loong64 architecture (Closes: #1052595)
diff -Nru liburcu-0.14.0/debian/control liburcu-0.14.0/debian/control
--- liburcu-0.14.0/debian/control   2023-10-17 20:59:07.0 +
+++ liburcu-0.14.0/debian/control   2024-02-02 18:14:20.0 +
@@ -14,7 +14,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: ${misc:Depends}, liburcu8 (= ${binary:Version})
+Depends: ${misc:Depends}, liburcu8t64 (= ${binary:Version})
 Description: userspace RCU (read-copy-update) library - development files
  This data synchronization library provides read-side access which scales
  linearly with the number of cores. It does so by allowing multiples copies of
@@ -25,7 +25,10 @@
  Install this package if you wish to develop your own programs using the
  userspace RCU library.
 
-Package: liburcu8
+Package: liburcu8t64
+Provides: ${t64:Provides}
+Replaces: liburcu8
+Breaks: liburcu8 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
diff -Nru liburcu-0.14.0/debian/liburcu8.install 
liburcu-0.14.0/debian/liburcu8.install
--- liburcu-0.14.0/debian/liburcu8.install  2023-10-17 20:59:07.0 
+
+++ liburcu-0.14.0/debian/liburcu8.install  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.8*
diff -Nru liburcu-0.14.0/debian/liburcu8.symbols 
liburcu-0.14.0/debian/liburcu8.symbols
--- liburcu-0.14.0/debian/liburcu8.symbols  2023-10-17 20:59:07.0 
+
+++ liburcu-0.14.0/debian/liburcu8.symbols  1970-01-01 00:00:00.0 
+
@@ -1,794 +0,0 @@
-liburcu-bp.so.8 liburcu8 #MINVER#
-* Build-Depends-Package: liburcu-dev
- (arch=m68k,riscv64)__tls_access_urcu_bp_reader@Base 0.13.0-1
- __urcu_compat_futex_cond@Base 0.13.0
- __urcu_compat_futex_lock@Base 0.13.0
- compat_futex_async@Base 0.13.0
- compat_futex_noasync@Base 0.13.0
- rcu_cmpxchg_pointer_sym@Base 0.13.0
- rcu_dereference_sym@Base 0.13.0
- rcu_set_pointer_sym@Base 0.13.0
- rcu_xchg_pointer_sym@Base 0.13.0
- urcu_bp_after_fork_child@Base 0.13.0
- urcu_bp_after_fork_parent@Base 0.13.0
- urcu_bp_barrier@Base 0.13.0
- urcu_bp_before_fork@Base 0.13.0
- urcu_bp_call_rcu@Base 0.13.0
- urcu_bp_call_rcu_after_fork_child@Base 0.13.0
- urcu_bp_call_rcu_after_fork_parent@Base 0.13.0
- urcu_bp_call_rcu_before_fork@Base 0.13.0
- 

Bug#1062692: libusb3380: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libusb3380
Version: 0.0.1+git20190125.c83d1e9-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libusb3380 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 libusb3380
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)
diff -Nru libusb3380-0.0.1+git20190125.c83d1e9/debian/changelog 
libusb3380-0.0.1+git20190125.c83d1e9/debian/changelog
--- libusb3380-0.0.1+git20190125.c83d1e9/debian/changelog   2020-04-09 
09:25:30.0 +
+++ libusb3380-0.0.1+git20190125.c83d1e9/debian/changelog   2024-02-02 
18:15:20.0 +
@@ -1,3 +1,10 @@
+libusb3380 (0.0.1+git20190125.c83d1e9-2.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:15:20 +
+
 libusb3380 (0.0.1+git20190125.c83d1e9-2) unstable; urgency=medium
 
   * Fixed debian/copyright: added forgotten copyright holder.
diff -Nru libusb3380-0.0.1+git20190125.c83d1e9/debian/control 
libusb3380-0.0.1+git20190125.c83d1e9/debian/control
--- libusb3380-0.0.1+git20190125.c83d1e9/debian/control 2020-04-09 
09:25:30.0 +
+++ libusb3380-0.0.1+git20190125.c83d1e9/debian/control 2024-02-02 
18:15:20.0 +
@@ -12,7 +12,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libusb3380-0 (= ${binary:Version}), libusb-1.0-0-dev, ${misc:Depends}
+Depends: libusb3380-0t64 (= ${binary:Version}), libusb-1.0-0-dev, 
${misc:Depends}
 Description: USB3380 abstraction layer for libusb: development
  The USB 3380 is a PCI Express Gen 2 to USB 3.0 SuperSpeed Peripheral
  Controller. It features one PCI Express Gen 2 x1 port and one USB 3.0
@@ -26,7 +26,10 @@
  .
  This package contains development files.
 
-Package: libusb3380-0
+Package: libusb3380-0t64
+Provides: ${t64:Provides}
+Replaces: libusb3380-0
+Breaks: libusb3380-0 (<< ${source:Version})
 Architecture: any
 Multi-Arch: same
 Depends: ${shlibs:Depends}, ${misc:Depends}
diff -Nru libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0.install 
libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0.install
--- libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0.install
2020-04-09 09:25:30.0 +
+++ libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0.install
1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0t64.install 
libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0t64.install
--- libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0t64.install 
1970-01-01 00:00:00.0 +
+++ libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0t64.install 
2020-04-09 09:25:30.0 +
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru 
libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0t64.lintian-overrides 
libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0t64.lintian-overrides
--- 
libusb3380-0.0.1+git20190125.c83d1e9/debian/libusb3380-0t64.lintian-overrides   
1970-01-01 

Bug#1062660: pypy3 7.3.11+dfsg-2+deb12u1 flagged for acceptance

[Adam D Barratt]

package release.debian.org
tags 1062660 = bookworm pending
thanks

Hi,

The upload referenced by this bug report has been flagged for acceptance into 
the proposed-updates queue for Debian bookworm.

Thanks for your contribution!

Upload details
==

Package: pypy3
Version: 7.3.11+dfsg-2+deb12u1

Explanation: avoid an rpython assertion error in the JIT if integer ranges 
don't overlap in a loop

Bug#1062690: libuev: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libuev
Version: 2.4.0-1.1
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libuev 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 libuev
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)
diff -Nru libuev-2.4.0/debian/changelog libuev-2.4.0/debian/changelog
--- libuev-2.4.0/debian/changelog   2022-01-24 20:05:09.0 +
+++ libuev-2.4.0/debian/changelog   2024-02-02 18:13:45.0 +
@@ -1,3 +1,10 @@
+libuev (2.4.0-1.2) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:13:45 +
+
 libuev (2.4.0-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libuev-2.4.0/debian/control libuev-2.4.0/debian/control
--- libuev-2.4.0/debian/control 2022-01-24 20:05:00.0 +
+++ libuev-2.4.0/debian/control 2024-02-02 18:13:45.0 +
@@ -13,7 +13,7 @@
 Section: libdevel
 Architecture: linux-any
 Multi-Arch: same
-Depends: ${misc:Depends}, libuev3 (= ${binary:Version})
+Depends: ${misc:Depends}, libuev3t64 (= ${binary:Version})
 Replaces: libuev2
 Description: static library, header files, and docs for libuev
  Static library, header files, and documentation for libuEv
@@ -26,7 +26,10 @@
  Experienced developers may appreciate libuEv is built on top of modern
  Linux APIs like epoll, eventfd, timerf, and signalfd.
 
-Package: libuev3
+Package: libuev3t64
+Provides: ${t64:Provides}
+Replaces: libuev3
+Breaks: libuev3 (<< ${source:Version})
 Architecture: linux-any
 Multi-Arch: same
 Depends: ${misc:Depends}, ${shlibs:Depends}
diff -Nru libuev-2.4.0/debian/libuev3.install 
libuev-2.4.0/debian/libuev3.install
--- libuev-2.4.0/debian/libuev3.install 2022-01-24 20:05:00.0 +
+++ libuev-2.4.0/debian/libuev3.install 1970-01-01 00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru libuev-2.4.0/debian/libuev3.symbols 
libuev-2.4.0/debian/libuev3.symbols
--- libuev-2.4.0/debian/libuev3.symbols 2022-01-24 20:05:00.0 +
+++ libuev-2.4.0/debian/libuev3.symbols 1970-01-01 00:00:00.0 +
@@ -1,30 +0,0 @@
-libuev.so.3 libuev3 #MINVER#
-* Build-Depends-Package: libuev-dev
- _uev_watcher_active@Base 2.4.0
- _uev_watcher_init@Base 2.4.0
- _uev_watcher_rearm@Base 2.4.0
- _uev_watcher_start@Base 2.4.0
- _uev_watcher_stop@Base 2.4.0
- uev_cron_init@Base 2.4.0
- uev_cron_set@Base 2.4.0
- uev_cron_start@Base 2.4.0
- uev_cron_stop@Base 2.4.0
- uev_event_init@Base 2.4.0
- uev_event_post@Base 2.4.0
- uev_event_stop@Base 2.4.0
- uev_exit@Base 2.4.0
- uev_init1@Base 2.4.0
- uev_init@Base 2.4.0
- uev_io_init@Base 2.4.0
- uev_io_set@Base 2.4.0
- uev_io_start@Base 2.4.0
- uev_io_stop@Base 2.4.0
- uev_run@Base 2.4.0
- uev_signal_init@Base 2.4.0
- uev_signal_set@Base 2.4.0
- uev_signal_start@Base 2.4.0
- uev_signal_stop@Base 2.4.0
- uev_timer_init@Base 2.4.0
- uev_timer_set@Base 2.4.0
- uev_timer_start@Base 2.4.0
- uev_timer_stop@Base 2.4.0
diff -Nru libuev-2.4.0/debian/libuev3t64.install 

Bug#1062689: libtwin: NMU diff for 64-bit time_t transition

[Steve Langasek]

Source: libtwin
Version: 13.05.03.15.06-g287d16c-2.2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@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
libtwin 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 libtwin
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)
diff -Nru libtwin-13.05.03.15.06-g287d16c/debian/changelog 
libtwin-13.05.03.15.06-g287d16c/debian/changelog
--- libtwin-13.05.03.15.06-g287d16c/debian/changelog2016-01-22 
11:56:48.0 +
+++ libtwin-13.05.03.15.06-g287d16c/debian/changelog2024-02-02 
18:12:58.0 +
@@ -1,3 +1,10 @@
+libtwin (13.05.03.15.06-g287d16c-2.3) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Fri, 02 Feb 2024 18:12:58 +
+
 libtwin (13.05.03.15.06-g287d16c-2.2) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libtwin-13.05.03.15.06-g287d16c/debian/control 
libtwin-13.05.03.15.06-g287d16c/debian/control
--- libtwin-13.05.03.15.06-g287d16c/debian/control  2015-12-23 
02:12:22.0 +
+++ libtwin-13.05.03.15.06-g287d16c/debian/control  2024-02-02 
18:12:58.0 +
@@ -13,7 +13,7 @@
 Architecture: any
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
-Depends: libtwin0 (= ${binary:Version}), ${misc:Depends}, libx11-dev, 
libpng-dev, libjpeg-dev, libz-dev
+Depends: libtwin0t64 (= ${binary:Version}), ${misc:Depends}, libx11-dev, 
libpng-dev, libjpeg-dev, libz-dev
 Description: tiny window system (development files)
  With embedded systems gaining high resolution displays and powerful CPUs, the
  desire for sophisticated graphical user interfaces can be realized in even the
@@ -26,7 +26,10 @@
  .
  This package contains the header files for development.
 
-Package: libtwin0
+Package: libtwin0t64
+Provides: ${t64:Provides}
+Replaces: libtwin0
+Breaks: libtwin0 (<< ${source:Version})
 Section: libs
 Architecture: any
 Multi-Arch: same
diff -Nru libtwin-13.05.03.15.06-g287d16c/debian/libtwin0.install 
libtwin-13.05.03.15.06-g287d16c/debian/libtwin0.install
--- libtwin-13.05.03.15.06-g287d16c/debian/libtwin0.install 2013-05-22 
02:34:47.0 +
+++ libtwin-13.05.03.15.06-g287d16c/debian/libtwin0.install 1970-01-01 
00:00:00.0 +
@@ -1 +0,0 @@
-usr/lib/*/lib*.so.*
diff -Nru libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.install 
libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.install
--- libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.install  1970-01-01 
00:00:00.0 +
+++ libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.install  2013-05-22 
02:34:47.0 +
@@ -0,0 +1 @@
+usr/lib/*/lib*.so.*
diff -Nru libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.lintian-overrides 
libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.lintian-overrides
--- libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.lintian-overrides
1970-01-01 00:00:00.0 +
+++ libtwin-13.05.03.15.06-g287d16c/debian/libtwin0t64.lintian-overrides
2024-02-02 18:12:58.0 +
@@ -0,0 +1