Bug#1063251: Bug#1065121: xdelta: still depends on libxdelta2

[Steve Langasek]

Thanks, NMU uploaded.  Attached is a full NMU debdiff for the time_t
transition.

On Thu, Feb 29, 2024 at 11:26:42PM +0100, Sven Joachim wrote:
> Package: xdelta
> Version: 1.1.3-10.5
> Severity: serious
> X-Debbugs-Cc: Sven Joachim , Steve Langasek 
> 
> 
> The xdelta package still depends on libxdelta2, rather than on
> libxdelta2t64 as it should.
> 
> The build log on m68k[1] shows that on this architecture libxdelta2t64
> gained a dependency on libxdelta2 as well.  Builds for other 32-bit
> architectures are still missing, but I suspect the libxdelta2t64 package
> will not installable on architectures where it does not provide
> libxdelta2.
> 
> Removing the debian/shlibs.local file is most certainly going to fix
> this mess, but I have not tested it.
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (101, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> 
> 1. 
> https://buildd.debian.org/status/fetch.php?pkg=xdelta=m68k=1.1.3-10.5=1709209632=0
> 

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru xdelta-1.1.3/debian/changelog xdelta-1.1.3/debian/changelog
--- xdelta-1.1.3/debian/changelog   2021-12-31 16:50:22.0 +
+++ xdelta-1.1.3/debian/changelog   2024-03-03 07:46:54.0 +
@@ -1,3 +1,18 @@
+xdelta (1.1.3-10.6) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Remove obsolete debian/shlibs.local which breaks install on 32-bit 
+archs.  Thanks to Sven Joachim .  Closes: #1065121.   
+
+ -- Steve Langasek   Sun, 03 Mar 2024 07:46:54 +
+
+xdelta (1.1.3-10.5) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.  Closes: #1063251
+
+ -- Steve Langasek   Thu, 29 Feb 2024 06:20:41 +
+
 xdelta (1.1.3-10.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru xdelta-1.1.3/debian/control xdelta-1.1.3/debian/control
--- xdelta-1.1.3/debian/control 2021-12-31 16:50:22.0 +
+++ xdelta-1.1.3/debian/control 2024-02-29 06:20:41.0 +
@@ -2,7 +2,7 @@
 Section: utils
 Priority: optional
 Maintainer: LaMont Jones 
-Build-Depends: debhelper-compat (= 13), libglib2.0-dev, zlib1g-dev, pkgconf | 
pkg-config
+Build-Depends: dpkg-dev (>= 1.22.5), debhelper-compat (= 13), libglib2.0-dev, 
zlib1g-dev, pkgconf | pkg-config
 Standards-Version: 4.6.0
 Rules-Requires-Root: no
 Vcs-Browser: https://salsa.debian.org/debian/xdelta
@@ -20,7 +20,10 @@
  these deltas to a copy of the original file.  Xdelta uses a fast,
  linear algorithm and performs well on both binary and text files.
 
-Package: libxdelta2
+Package: libxdelta2t64
+Provides: ${t64:Provides}
+Replaces: libxdelta2
+Breaks: libxdelta2 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${misc:Depends}, ${shlibs:Depends}
@@ -39,7 +42,7 @@
 Package: libxdelta2-dev
 Architecture: any
 Section: libdevel
-Depends: ${misc:Depends}, libxdelta2 (= ${binary:Version})
+Depends: ${misc:Depends}, libxdelta2t64 (= ${binary:Version})
 Breaks: xdelta (<< 1.1.3-9.3~)
 Replaces: xdelta-dev, xdelta (<< 1.1.3-9.3~)
 Conflicts: libxdelta0-dev, libxdelta1-dev
diff -Nru xdelta-1.1.3/debian/libxdelta2.install 
xdelta-1.1.3/debian/libxdelta2.install
--- xdelta-1.1.3/debian/libxdelta2.install  2021-12-31 16:50:22.0 
+
+++ xdelta-1.1.3/debian/libxdelta2.install  1970-01-01 00:00:00.0 
+
@@ -1 +0,0 @@
-usr/lib/*/*.so.*
diff -Nru xdelta-1.1.3/debian/libxdelta2.shlibs 
xdelta-1.1.3/debian/libxdelta2.shlibs
--- xdelta-1.1.3/debian/libxdelta2.shlibs   2021-12-31 16:50:22.0 
+
+++ xdelta-1.1.3/debian/libxdelta2.shlibs   1970-01-01 00:00:00.0 
+
@@ -1,2 +0,0 @@
-libxdelta 2 libxdelta2 (>= 1.1.3)
-libedsio 0 libxdelta2 (>= 1.1.3)
diff -Nru xdelta-1.1.3/debian/libxdelta2t64.install 
xdelta-1.1.3/debian/libxdelta2t64.install
--- xdelta-1.1.3/debian/libxdelta2t64.install   1970-01-01 00:00:00.0 
+
+++ xdelta-1.1.3/debian/libxdelta2t64.install   2021-12-31 16:50:22.0 
+
@@ -0,0 +1 @@
+usr/lib/*/*.so.*
diff -Nru xdelta-1.1.3/debian/libxdelta2t64.lintian-overrides 
xdelta-1.1.3/debian/libxdelta2t64.lintian-overrides
--- xdelta-1.1.3/debian/libxdelta2t64.lintian-overrides 1970-01-01 
00:00:00.0 +
+++ xdelta-1.1.3/debian/libxdelta2t64.lintian-overrides 2024-02-29 
06:20:32.0 +
@@ -0,0 +1 @@
+libxdelta2t64: package-name-doesnt-match-sonames libxdelta2
diff -Nru xdelta-1.1.3/debian/libxdelta2t64.shlibs 
xdelta-1.1.3/debian/libxdelta2t64.shlibs
--- xdelta-1.1.3/debian/libxdelta2t64.shlibs1970-01-01 00:00:00.0 
+
+++ xdelta-1.1.3/debian/libxdelta2t64.shlibs2024-02-29 

Bug#1064558: [Pkg-javascript-devel] Bug#1064558: node-leveldown: FTBFS on mips64el: not ok 1397 Error: batch(array) element must be an object and not `null`

[Yadd]

On 2/24/24 13:10, Sebastian Ramacher wrote:

Source: node-leveldown
Version: 5.6.0+dfsg-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=node-leveldown=mips64el=5.6.0%2Bdfsg-4%2Bb1=1708632735=0

not ok 1397 Error: batch(array) element must be an object and not `null`
   ---
 operator: error
 stack: |-
   Error: batch(array) element must be an object and not `null`
   at AbstractLevelDOWN.batch 
(/usr/share/nodejs/abstract-leveldown/abstract-leveldown.js:163:33)
   at /<>/test/iterator-recursion-test.js:48:8
   at /usr/share/nodejs/abstract-leveldown/abstract-leveldown.js:41:5
   ...

Cheers


Hi Jérémy,

when trying to build on mips64el porterbox, i got this:

make[1]: Entering directory '/home/yadd/node-leveldown'
node-gyp clean
node: error while loading shared libraries: libnode.so.108: cannot open 
shared object file: No such file or directory

make[1]: *** [debian/rules:18: override_dh_auto_clean] Error 127
make[1]: Leaving directory '/home/yadd/node-leveldown'

Bug#1065341: src:openstructure: unsatisfied build dependency in testing: sip-dev

[Paul Gevers]

Source: openstructure
Version: 2.5.0-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Control: block -1 by 1060745

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Bug 1060745 was filed about this and apparently the issue is already 
fixed in experimental, because it's closed. However, sip4 has been 
removed from testing due to its RC bug, and I don't expect it to come back.


Can you please investigate the situation and figure out how to resolve
it?

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:openstructure: unsatisfied build dependency in testing: sip-dev

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1060745
Bug #1065341 [src:openstructure] src:openstructure: unsatisfied build 
dependency in testing: sip-dev
1065341 was not blocked by any bugs.
1065341 was not blocking any bugs.
Added blocking bug(s) of 1065341: 1060745

-- 
1065341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065341
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065340: src:guidata: unsatisfied build dependency in testing: python3-sip

[Paul Gevers]

Source: guidata
Version: 3.0.4+dfsg1-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable
Control: block -1 by 1060742

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing.

Bug #1060742 was filed earlier to warn you about the issue; python3-sip 
has now been removed from testing due to its RC bug.


Can you please investigate the situation and figure out how to resolve
it?

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:guidata: unsatisfied build dependency in testing: python3-sip

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1060742
Bug #1065340 [src:guidata] src:guidata: unsatisfied build dependency in 
testing: python3-sip
1065340 was not blocked by any bugs.
1065340 was not blocking any bugs.
Added blocking bug(s) of 1065340: 1060742

-- 
1065340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065340
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064282: poppler: NMU diff for 64-bit time_t transition

[Steve Langasek]

On Sun, Mar 03, 2024 at 07:25:22AM +0100, Andreas Metzler wrote:
> On 2024-03-01 Daniel Serpell  wrote:
> > Source: poppler
> > Followup-For: Bug #1064282
> > Control: reopen 1064282

> > As reported in bug 1065155, the provided patch was incorrect, the
> > X-Time64-Compat header is set incorrectly to libpoppler-cpp0v5 for all
> > the library packages.

> Good Morning,

> Also afaict (from browsing GIT history) the build-dependencies are
> insufficient, X-Time64-Compat was initially added in debhelper 13.12.

Note that the Provides: are effectively an optimization on 64-bit archs, to
provide binary backwards-compatibility with third-party binaries and with
binaries in stable series as part of an upgrade.  All packages in Debian
should be rebuilt against the new library names, on all archs, before
release.  So we have not added versioned build-depends on debhelper. 
(Particularly irrelevant for poppler, whose soname changes ~ monthly.)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Processed: src:r-cran-rstanarm: fails to migrate to testing for too long: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.32.1-1
Bug #1065339 [src:r-cran-rstanarm] src:r-cran-rstanarm: fails to migrate to 
testing for too long: FTBFS on mips64el
Marked as fixed in versions r-cran-rstanarm/2.32.1-1.
Bug #1065339 [src:r-cran-rstanarm] src:r-cran-rstanarm: fails to migrate to 
testing for too long: FTBFS on mips64el
Marked Bug as done

-- 
1065339: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065339
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065339: src:r-cran-rstanarm: fails to migrate to testing for too long: FTBFS on mips64el

[Paul Gevers]

Source: r-cran-rstanarm
Version: 2.26.1-2
Severity: serious
Control: close -1 2.32.1-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-rstanarm has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
failed to build on mips64el.


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-rstanarm



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.5.0-1
Bug #1065338 [src:r-cran-rpact] src:r-cran-rpact: fails to migrate to testing 
for too long: autopkgtest failures
Marked as fixed in versions r-cran-rpact/3.5.0-1.
Bug #1065338 [src:r-cran-rpact] src:r-cran-rpact: fails to migrate to testing 
for too long: autopkgtest failures
Marked Bug as done

-- 
1065338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: src:r-cran-igraph: fails to migrate to testing for too long: FTBFS on32 bits

[Debian Bug Tracking System]

Processing control commands:

> close -1 2.0.1.1-1
Bug #1065337 [src:r-cran-igraph] src:r-cran-igraph: fails to migrate to testing 
for too long: FTBFS on32 bits
Marked as fixed in versions r-cran-igraph/2.0.1.1-1.
Bug #1065337 [src:r-cran-igraph] src:r-cran-igraph: fails to migrate to testing 
for too long: FTBFS on32 bits
Marked Bug as done

-- 
1065337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065337
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065338: src:r-cran-rpact: fails to migrate to testing for too long: autopkgtest failures

[Paul Gevers]

Source: r-cran-rpact
Version: 3.4.0-1
Severity: serious
Control: close -1 3.5.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-rpact has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
fails its own autopkgtest on some architectures: arm64, ppc64el and 
s390x (and i386, but that's not a regression).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-rpact



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065337: src:r-cran-igraph: fails to migrate to testing for too long: FTBFS on32 bits

[Paul Gevers]

Source: r-cran-igraph
Version: 1.6.0-1
Severity: serious
Control: close -1 2.0.1.1-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:r-cran-igraph has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
failed to build on armel, armhf and i386 (our 32 bits architectures).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=r-cran-igraph



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065336: lxpanel: Depends: libfm-modules but is not installable

[Linus Lüssing]

Package: lxpanel
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: linus.luess...@c0d3.blue

Dear Maintainer,

On a Debian Sid system with "task-lxqt-desktop" and "task-lxde-desktop" 
installed
an "apt-get dist-upgrade" has removed these packages and by that a large
list of other packages and made a login into a graphical desktop /
window manager impossible.

Trying to reinstall "task-lxde-desktop" results in the following error:

```
The following packages have unmet dependencies:
 lxpanel : Depends: libfm-modules but ist is not installable
```

Or trying to reinstall "task-lxqt-desktop" results in:

```
The following packages have unmet dependencies:
 libfm-qt13 : Depends: libglib2.0-bin
 libqt5xdg3 : Depends: libglib2.0-bin
```

Manually running "apt-get install libfm-modules" ran through fine,
removed "libfm-extra4" automatically and by that fixed the "task-lxde-desktop" /
"lxpanel" installation for me. After that I could run "apt-get install
task-lxde-desktop" without any issues.

For "task-lxqt-desktop" I couldn't quite figure out a solution yet (but
is likely unrelated to lxpanel / libfm dependencies anyway, I guess).

Regards, Linus


*** 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: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, arm64

Kernel: Linux 6.6.11-amd64 (SMP w/16 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages lxpanel depends on:
ii  libasound2   1.2.10-3
ii  libc62.37-13
ii  libcairo21.18.0-1+b1
ii  libcurl3-gnutls  8.5.0-2
pn  libfm-gtk3-4 
pn  libfm-modules
pn  libfm4   
ii  libgdk-pixbuf-2.0-0  2.42.10+dfsg-3+b1
ii  libglib2.0-0 2.78.3-1
ii  libgtk-3-0   3.24.41-1
ii  libiw30  30~pre9-16+b1
pn  libkeybinder-3.0-0   
pn  libmenu-cache3   
ii  libpango-1.0-0   1.51.0+ds-4
ii  libwnck-3-0  43.0-3
ii  libx11-6 2:1.8.7-1
ii  libxml2  2.9.14+dfsg-1.3+b2
pn  lxmenu-data  
pn  lxpanel-data 

Versions of packages lxpanel recommends:
ii  awesome [notification-daemon]   4.3-7
ii  dunst [notification-daemon] 1.9.2-1
ii  gnome-shell [notification-daemon]   44.7-1
ii  gnome-terminal [x-terminal-emulator]3.50.1-1
ii  libnotify-bin   0.8.3-1
ii  lxterminal [x-terminal-emulator]0.4.0-2
ii  notification-daemon 3.20.0-4+b1
ii  pavucontrol 5.0-2
ii  plasma-workspace [notification-daemon]  4:5.27.10-2
ii  xkb-data2.38-2
ii  xterm [x-terminal-emulator] 389-1

Versions of packages lxpanel suggests:
ii  chromium [www-browser]  120.0.6099.199-1
ii  firefox [www-browser]   121.0-2
ii  lynx [www-browser]  2.9.0dev.12-1

Bug#1064282: poppler: NMU diff for 64-bit time_t transition

[Andreas Metzler]

On 2024-03-01 Daniel Serpell  wrote:
> Source: poppler
> Followup-For: Bug #1064282
> Control: reopen 1064282

> As reported in bug 1065155, the provided patch was incorrect, the
> X-Time64-Compat header is set incorrectly to libpoppler-cpp0v5 for all
> the library packages.

Good Morning,

Also afaict (from browsing GIT history) the build-dependencies are
insufficient, X-Time64-Compat was initially added in debhelper 13.12.

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#1065275: mariadb: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Otto Kekäläinen]

Since this is now the first time I noticed that new time_t should be
available for testing and I started testing, I noticed that MariaDB
has built-in check to prevent it from running on 2038 at all:

# date
Thu Mar  3 05:55:28 UTC 2039

# ./sql/mariadbd --version
2039-03-03  5:58:55 0 [ERROR] This server doesn't support dates later than 2038

Seems to stem from This is due to
https://github.com/MariaDB/server/blob/11.5/sql/mysqld.cc#L3903-L3908


I am looking into this now as well..


On Sat, 2 Mar 2024 at 16:41, Otto Kekäläinen  wrote:
>
> > > Could you Sebastian perhaps quickly skim through the commit that
> > > implemented this
> > > https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/8194544349982990fb2585c2a8c15c4db3904735
> > > and say if there might be something else missing as well?
> >
> > Did you mean
> > https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/d2a0784f1e01b6613fefda17199a4e9867a126c3?
> >
> > At least for now that looks good.
>
> No I meant the original one, but you have now seen the original and
> amendment and had no further comments, so seems good.
>
> I see Steven just uploaded curl 8.6.0-3.2 to fix the curl issues. I
> will continue to wait a bit for the basic dependencies to stabilize,
> for example this seems to affect many packages:
>
> libnsl2 depends on:
> - libtirpc3:armel (>= 1.0.2)
> libtirpc3t64 conflicts with:
> - libtirpc3:armel (< 1.3.4+ds-1.1)
>
> I will upload new MariaDB as soon as I can verify that it is buildable.

Bug#1065274: marked as done (ipset: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sun, 03 Mar 2024 04:35:18 +
with message-id 
and subject line Bug#1065274: fixed in ipset 7.21-3
has caused the Debian Bug report #1065274,
regarding ipset: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065274: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065274
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ipset
Version: 7.21-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: ipset
Source-Version: 7.21-3
Done: Neutron Soutmun 

We believe that the bug you reported is fixed in the latest version of
ipset, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Neutron Soutmun  (supplier of updated ipset package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 03 Mar 2024 10:24:42 +0700
Source: ipset
Architecture: source
Version: 7.21-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Netfilter Packaging Team 

Changed-By: Neutron Soutmun 
Closes: 1065274
Changes:
 ipset (7.21-3) unstable; urgency=medium
 .
   * [7f164e5] d/tests/control: Restrictions list separated by commas
   * [51adda5] d/control: build depends on dpkg-dev (>= 1.22.5)
 * Add build depends on dpkg-dev (>= 1.22.5) to ensure that the time64
   feature was enabled properly. Closes: #1065274
   Thanks to Sebastian Ramacher for suggestion.
Checksums-Sha1:
 3e194db0b078dff76549f55da8cf5773d07d9bab 2195 ipset_7.21-3.dsc
 2fceabcc2de17d53d7ed27dccd77fca94b965e45 687746 ipset_7.21.orig.tar.bz2
 53395e6a8f02e3efe1c5c4691ac37604165b837a 16888 ipset_7.21-3.debian.tar.xz
 db3d6def414282d0839301a70177908a1116673b 7069 ipset_7.21-3_amd64.buildinfo
Checksums-Sha256:
 87b49431add7de7d565496f8263589fdbab1646669851a43f9b8025e8ca33107 2195 
ipset_7.21-3.dsc
 e2c6ce4fcf3acb3893ca5d35c86935f80ad76fc5ccae601185842df760e0bc69 687746 
ipset_7.21.orig.tar.bz2
 3d096543b3a287b98df7c3df03200791ded8a7820a1ec3bdd6d3fad4cb32212a 16888 
ipset_7.21-3.debian.tar.xz
 e3d6b2f616fd3376b8b535978875f03559858d822534a9f44ff6bae44f86afa2 7069 
ipset_7.21-3_amd64.buildinfo
Files:
 72ffcab49426d6437a28d729df18c94f 2195 net optional ipset_7.21-3.dsc
 c1116de7c5dd01a0a83413b308ca1917 687746 net optional ipset_7.21.orig.tar.bz2
 18c89216950663b25482d545e1be21f4 16888 net optional ipset_7.21-3.debian.tar.xz
 80de54316762937642eb05965bd691c9 7069 net optional ipset_7.21-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE9TLaEOVj7oRECXehnQRwvabNxFcFAmXj9I4ACgkQnQRwvabN
xFc7Rw/+Isxrzrorm5ZEK9t9r8b4UnI5nZa1lQ5SEDEHiHC6THQxRjLRkzzKNJxD
Kg96H8wxsursSzdB7AB9i1EVeMgE3iURkN+I8yxqbeK+BwQsOO1oU/XCSqMb4gGN
r+jWAVPEDf7rScaiYypUtY5gTMuMu2Gu4uWPhtS5+1OVOzNPjQScXSU2PgqoUsXU
ztP2ke6CCwc0Rs5PVhiaf8R/oUwmaFqBiq+2kE5SEfp+t/u7yGYDROjdLdHv/Eny
XTq94/gi0LDUMzGCFKp/SWNjCHUDqo6NOLAi1Bu4Eka1tiPXp3HxorJj62kW2sLL
yQiKODuFb9sx+YMu7gJzFq9N/EnoJHqfPqgvPEs7t538vtsfM8SwujMEZwVXl7p2
t/lNvc/DmWxx6k3mG+Seouro0XaLMkNr1RS4F4HMLt8Qg3pZe1HN9yfatewWYrXE
RJUTjNta6iF78I6BITLxTOL+Kpa3tbpcat1UNFrjPzOOwV9uJCvRraT8xtHAqbGZ
QUrvyGi/sqBM+SpAB67vWHV6/zjYY5QKmPyuwtcLp09uAOxncXA9g1NJBEgPYkeE
2t3kaLSS+JAjXQylPaC2vKWUvnZuLT76y4Y/U4ahiI3tmBI1wupfm6dl4E9edatw
2qaQ22I5oEXze81JV8Q0CBFFPVxkIoobVtPyBivqTSnV4f3FoQg=
=zktm
-END PGP SIGNATURE-



pgpKzD8E1UV2K.pgp
Description: PGP signature
--- End Message ---

Bug#1063254: marked as done (lua-luv: identified for time_t transition but no ABI in shlibs)

[Debian Bug Tracking System]

Your message dated Sun, 03 Mar 2024 02:55:09 +
with message-id 
and subject line Bug#1063254: fixed in lua-luv 1.48.0-2-1
has caused the Debian Bug report #1063254,
regarding lua-luv: identified for time_t transition but no ABI in shlibs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1063254: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063254
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lua-luv
Version: 1.44.2-0-1
Severity: serious
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainers,

Analysis of the archive for the 64-bit time_t transition[0][1] identifies
lua-luv as an affected package, on the basis that it depends on some library
whose ABI is sensitive to time_t, which requires reverse-dependencies to be
built with LFS support enabled, and lua-luv's own ABI is sensitive to LFS
support.

However, lua-luv's shlibs file declares a dependency on a library package
name that contains no ABI information:

$ cat DEBIAN/shlibs
liblua5.1-luv 0 lua-luv (>= 1.44.2-0)
liblua5.2-luv 0 lua-luv (>= 1.44.2-0)
liblua5.3-luv 0 lua-luv (>= 1.44.2-0)
liblua5.4-luv 0 lua-luv (>= 1.44.2-0)
$

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

Looking at the archive, there are packages built from the separate lua-nvim
and neovim source packages that depend on this library.

Since there is no self-evident thing to do with the library package name
here, we will not be handling this package as part of the mass NMUs.
Instead I am filing a serious bug because partial upgrades from bookworm to
trixie on 32-bit architectures will result in ABI skew and may result in
broken behavior.

Thanks,
-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

[0] https://wiki.debian.org/ReleaseGoals/64bit-time
[1] https://lists.debian.org/debian-devel/2024/01/msg00041.html


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: lua-luv
Source-Version: 1.48.0-2-1
Done: James McCoy 

We believe that the bug you reported is fixed in the latest version of
lua-luv, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1063...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
James McCoy  (supplier of updated lua-luv package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 20:24:41 -0500
Source: lua-luv
Architecture: source
Version: 1.48.0-2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Lua Team 
Changed-By: James McCoy 
Closes: 1063254
Changes:
 lua-luv (1.48.0-2-1) unstable; urgency=medium
 .
   * New upstream release
   * Build-Depend against dpkg-dev >= 1.22.5 for the t64 transition
 (Closes: #1063254)
   * Disable loop tests since they fail with dh-lua's app-dynamic test cycle.
Checksums-Sha1:
 5deebc23ee20f62092cae09c0388014957405f95 2383 lua-luv_1.48.0-2-1.dsc
 d745cfa85e0894f07fe6c624d92bb7c0338c3acb 134821 lua-luv_1.48.0-2.orig.tar.gz
 40b1bea69955f445410745ff8f189cab20e0e691 5232 lua-luv_1.48.0-2-1.debian.tar.xz
Checksums-Sha256:
 1e6e2947f1bf9757b5c9e89d6fcfa2c476b8d664c41e6d31ac32a594d1ae 2383 
lua-luv_1.48.0-2-1.dsc
 e64cd8a0197449288b37df6ca058120e8d2308fc305f543162b5bf3e92273a05 134821 
lua-luv_1.48.0-2.orig.tar.gz
 8c403ca286db2771563b6c3520eacf888f3279bbc81a257f10b21df9c9d42863 5232 
lua-luv_1.48.0-2-1.debian.tar.xz
Files:
 b6be9750f58836c563ee55970c860e91 2383 interpreters optional 
lua-luv_1.48.0-2-1.dsc
 8efb4574249415a888a4197468529a9b 134821 interpreters optional 
lua-luv_1.48.0-2.orig.tar.gz
 c503c424e442c1814bdfd04ea72f4767 5232 interpreters optional 
lua-luv_1.48.0-2-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKoBAEBCgCSFiEEkb+/TWlWvV33ty0j3+aRrjMbo9sFAmXj1URfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDkx
QkZCRjRENjk1NkJENURGN0I3MkQyM0RGRTY5MUFFMzMxQkEzREIUHGphbWVzc2Fu

Bug#1065022: marked as done (libglib2.0-0t64: transition from libglib2.0-0 breaks GSettings, GIO modules)

[Debian Bug Tracking System]

Your message dated Sun, 03 Mar 2024 01:49:32 +
with message-id 
and subject line Bug#1065022: fixed in glib2.0 2.79.3-3
has caused the Debian Bug report #1065022,
regarding libglib2.0-0t64: transition from libglib2.0-0 breaks GSettings, GIO 
modules
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libglib2.0-0t64
Version: 2.78.4-2
Severity: critical
Justification: breaks unrelated software
X-Debbugs-Cc: debian-de...@lists.debian.org

Hey.


CCing d-d since there seems some further deeper problem with the t64
transition (namely lib files getting lost, when "downgrading" i.e.
reverting).


Earlier tonight I've upgraded this day’s packages which included
numerous that made the t64 transition (see the attached aptitude log
for the whole process, first the upgrade, and then "bi-secting" to
find the culprit).

Immediately afterwards, starting GUI programs from the still running
desktop environment caused failures like:
$ evince

(evince:17537): GLib-GIO-CRITICAL **: 04:18:22.610: 
g_settings_schema_source_lookup: assertion 'source != NULL' failed

(evince:17537): GLib-GIO-CRITICAL **: 04:18:22.610: 
g_settings_schema_source_lookup: assertion 'source != NULL' failed

(evince:17537): GLib-GIO-ERROR **: 04:18:22.658: No GSettings schemas are 
installed on the system
Trace/breakpoint trap
$ gedit

(gedit:17585): GLib-GIO-ERROR **: 04:18:35.012: No GSettings schemas are 
installed on the system
Trace/breakpoint trap
$

I suspected a reboot might be needed but after that even the display
manager didn't start anymore.
I saw errors like:
Feb 29 02:51:14 heisenberg kernel: traps: at-spi-bus-laun[17935] trap int3 
ip:7fdceec49587 sp:7ffd0acdade0 error:0 in 
libglib-2.0.so.0.7800.4[7fdceec05000+99000]
Feb 29 02:51:52 heisenberg kernel: traps: at-spi-bus-laun[17941] trap int3 
ip:7f52e53ee587 sp:7ffcc69b0fc0 error:0 in 
libglib-2.0.so.0.7800.4[7f52e53aa000+99000]


My first guess was glib, so I downgraded that (everything from the source
package), but that didn't help.

As you can see from the aptitude log, I then moved on downgrade further
of the previously upgraded packages, several times I've rebooted in-
between (e.g. after downgrading things like *pam* and *systemd*).

Along the way I saw the most weirdest effects:
- logind was apprently in some bogus state, which I think might
  have been the reason, why X/the display manager remained black/hung for
  several minutes:
  Feb 29 03:37:21 heisenberg lightdm[139886]: Failed to get list of logind 
seats: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate 
service 'org.freedesktop.login1': timed out (service_start_timeout=25000ms)

- At some point, when installing packages via aptitude
  # aptitude
  
  Performing actions...
  
  
  And it also hung at the end shortly after finishing the
  upgrade/downgrade.

- When downgrading packages that had a t64 transition, sometimes
  the lib file was gone.
  I.e. I removed the *t64 package and re-installed the old one
  and then the .so file for libapt-pkg6.0 and libpam0g was missing.
  How can that happen?


Eventually I downgraded the gcr/gck stuff, and then it worked again.

From that I went forward and upgrade all the various packages again, to
see where the problem actuall is.

Turns out, it's probably actually libglib.

When I install the first time libglib2.0-0t64 (and purge libglib2.0-0),
things start to break apart.
When I re-install libglib2.0-0t64, things work again (it seems regardless
of the gcr/gck stuff).


Long story short:
@glib maintainers:
- there's something wrong with the transition (unless even that need for
  the re-install is already a sign for some deeper issues)

@d-d:
- How can it happen that purge *t64 packages and at the same time install
  the previous package, and then the so file is missing?
  I mean it's clear that they use the same name, but shouldn't DPKG handle
  the cleanly?

Thanks,
Chris

PS: I'll attach the aptitude log only to the bug and not to d-d, in
order not to spam so many people with it.
It's probably anyway uselesss, but might help to find out why
downgrading gck/gcr stuff helped first, without re-installing the
glib package.

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: 

Bug#1065022: marked as pending in glib2.0

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1065022 in glib2.0 reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/glib/-/commit/451ed4fd133f4cac0b1530cbba2a63a18c6543e1


d/libglib2.0-0t64.preinst: Remove libglib2.0-0 postrm to avoid file loss

During the migration from libglib2.0-0 to libglib2.0-0t64, the package
that is responsible for "owning" /usr/lib/*/gio/modules/giomodule.cache
and /usr/share/glib-2.0/schemas/gschemas.compiled changed from
libglib2.0-0 to libglib2.0-0t64. Because dpkg does not have an equivalent
of RPM's %ghost files, the ownership of these files is managed by social
convention rather than by the package management system.

Unfortunately, libglib2.0-0's postrm as shipped in Debian releases from
2010 to the present is not aware of the possibility that another binary
package might need to take over responsibility for those files, and so
will remove both files during purge (and giomodules.cache also during
remove) in accordance with the requirement that installing and then
removing and purging a package must not leave unowned files behind.
This causes most applications that depend on GSettings schemas to crash
with an assertion failure, until the next time the glib-compile-schemas
trigger happens to be run; it will also cause functionality loss for
applications that depend on GIO modules.

To disarm the problematic maintainer script, delete it during the new
package's preinst. This is (probably) a Policy violation, but seems like
the least-bad exit strategy from the unacceptable situation we have
found ourselves in.

A subsequent commit will improve the postrm so that if we find that we
need to migrate from libglib2.0-0t64 to libglib2.0-0xyz or libglib-2.0-0
at some point in the future, similar efforts will not be needed.

Closes: #1065022


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065022

Processed: Bug#1065022 marked as pending in glib2.0

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065022 [libglib2.0-0t64] libglib2.0-0t64: transition from libglib2.0-0 
breaks GSettings, GIO modules
Added tag(s) pending.

-- 
1065022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065275: mariadb: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Otto Kekäläinen]

> > Could you Sebastian perhaps quickly skim through the commit that
> > implemented this
> > https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/8194544349982990fb2585c2a8c15c4db3904735
> > and say if there might be something else missing as well?
>
> Did you mean
> https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/d2a0784f1e01b6613fefda17199a4e9867a126c3?
>
> At least for now that looks good.

No I meant the original one, but you have now seen the original and
amendment and had no further comments, so seems good.

I see Steven just uploaded curl 8.6.0-3.2 to fix the curl issues. I
will continue to wait a bit for the basic dependencies to stabilize,
for example this seems to affect many packages:

libnsl2 depends on:
- libtirpc3:armel (>= 1.0.2)
libtirpc3t64 conflicts with:
- libtirpc3:armel (< 1.3.4+ds-1.1)

I will upload new MariaDB as soon as I can verify that it is buildable.

Bug#1065331: libhdf5-103-1t64: depends on libcurl4 instead of libcurl4t64

[Vincent Lefevre]

Package: libhdf5-103-1t64
Version: 1.10.10+repack-3.1
Severity: serious

libhdf5-103-1t64 depends on libcurl4 instead of libcurl4t64.
This makes the upgrade of curl impossible.

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
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)
LSM: AppArmor: enabled

Versions of packages libhdf5-103-1t64 depends on:
ii  libc6   2.37-15.1
ii  libcurl48.6.0-3
ii  libssl3t64  3.1.5-1.1
ii  libsz2  1.1.2-1
ii  zlib1g  1:1.3.dfsg-3.1

libhdf5-103-1t64 recommends no packages.

libhdf5-103-1t64 suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1065286: marked as done (mozjs115: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 23:43:12 +
with message-id 
and subject line Bug#1065286: fixed in mozjs115 115.8.0-3
has caused the Debian Bug report #1065286,
regarding mozjs115: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs115
Version: 115.8.0-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: mozjs115
Source-Version: 115.8.0-3
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
mozjs115, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated mozjs115 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 18:02:34 -0500
Source: mozjs115
Built-For-Profiles: noudeb
Architecture: source
Version: 115.8.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1065286
Changes:
 mozjs115 (115.8.0-3) unstable; urgency=medium
 .
   * Build-depend on dpkg-dev (>= 1.22.5) (Closes: #1065286)
Checksums-Sha1:
 bbc2e8a0a07c868dfe3638e1e01e62ded1318bd7 2386 mozjs115_115.8.0-3.dsc
 cfc51851ab2ad2df0060c9643990795e1bbe940c 69696 mozjs115_115.8.0-3.debian.tar.xz
 d7904a2be0ae1bcdec854d1198215727070c7bc6 14643 
mozjs115_115.8.0-3_source.buildinfo
Checksums-Sha256:
 5db3f761acfcac870447d3c9d94621096aec63481966dccb8c505e017afb49e2 2386 
mozjs115_115.8.0-3.dsc
 165cf245b03178e271ef7c0596e57a148f54378ac3cceaa12153559fa820adce 69696 
mozjs115_115.8.0-3.debian.tar.xz
 b6b6a9b3ce10b7ace71345c6ae74520eb1cc6509287c22b01facf8eb5038e2fa 14643 
mozjs115_115.8.0-3_source.buildinfo
Files:
 17cb49745008479f72d98af10885be6f 2386 libs optional mozjs115_115.8.0-3.dsc
 54763fa5e8c846138862012c9073884e 69696 libs optional 
mozjs115_115.8.0-3.debian.tar.xz
 af5820964cb127b46718f62a0bb9ceca 14643 libs optional 
mozjs115_115.8.0-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXjsDUACgkQ5mx3Wuv+
bH1mjxAAv4uhbPCtXWbEJ+G+7M4gOxb2IHQsgXWcFIx4rUt0ev+Ag1jvDDjfzHnh
cQ73pvxFjAGf3hzW2eml/ohpA1hvN++o093Je6iIqNmsqDajArZOYBVXae/cdjlH
WzaofZMryK5OJ3rzPUu1+5H/eh/EDi3tpE6gqDvE1FkL9uiUdaIobEmxE2VN19D1
xiSjvj0rH/r/mjR2yoE88BpWCCR2vX74KXdvRphLk2OrFUuhVkWNqXTrtRc/iOFI
qOVx2hNIf1DibTzeFRZ7HEjrih2QDyoZzLSbzk4ehj77XR5DrWDmR+lpFyPzsNhu
JYZgoc1uuqeC3MzcNUMnsTnWbr10IS886iT+xm7FFFAyJ/RtzC9MA2N4km7d75pe
DtbdPQkc7hkdUgHpebOFS5/9jdB8SidkNc00JLRffzwxGEpTS1If7rfglOnU22T1
Vc8Su2xYBh8ulWQC0wy7mZukG1Khx3JP7qZA8TbkoLcXyz/1LDlVezcqrUOK0OBk
G6ErCkzuuJ8nsXvick1tJNo97DVHUUKci+OEsp2V9lQJKAlLVsxgAjO0aKV3Dmj8
DqL2siOMo65FODs9ZYdpRMhjVvewN7pB/7QXnI82RkFzoTeNcjYCndRVZhQ5r2r0
rcD7xs2udlmifVEohhq4SdhjGH1JQALEr2ZHtCfR7EjrBs3ZULU=
=tvF2
-END PGP SIGNATURE-



pgpfdbQtXDMpG.pgp
Description: PGP signature
--- End Message ---

Bug#1065285: marked as done (mozjs102: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 23:32:40 +
with message-id 
and subject line Bug#1065285: fixed in mozjs102 102.15.1-3
has caused the Debian Bug report #1065285,
regarding mozjs102: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065285: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065285
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mozjs102
Version: 102.15.1-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: mozjs102
Source-Version: 102.15.1-3
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
mozjs102, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated mozjs102 package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 18:08:37 -0500
Source: mozjs102
Built-For-Profiles: noudeb
Architecture: source
Version: 102.15.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1065285
Changes:
 mozjs102 (102.15.1-3) unstable; urgency=medium
 .
   * Build-depend on dpkg-dev (>= 1.22.5) (Closes: #1065285)
   * Stop using debian/control.in and dh-sequence-gnome
Checksums-Sha1:
 e65066f380b3fc996aad23a892a8db681a644e49 2339 mozjs102_102.15.1-3.dsc
 be49718145d3bd3a21e05a1b01e5a0087d3840db 65436 
mozjs102_102.15.1-3.debian.tar.xz
 1e7b0d469ee69d528ef7e883b09f0962b9e38803 14647 
mozjs102_102.15.1-3_source.buildinfo
Checksums-Sha256:
 65b1387fc92f4a2b66f8adef54101d2134c6bb8fa424b221a52e6fef9eff3f58 2339 
mozjs102_102.15.1-3.dsc
 24b2d9d7e80ef9e658783474352f2b67bd2d2131c732ac6eec8fe64381b7187e 65436 
mozjs102_102.15.1-3.debian.tar.xz
 004094f90be9251522ee8f12d2e2c1e7eb2fff8e053fc5d8c01b7d5824e3c3f9 14647 
mozjs102_102.15.1-3_source.buildinfo
Files:
 1335402fc8a700890d32bd7dda149ce8 2339 libs optional mozjs102_102.15.1-3.dsc
 d242b03a81151f2180ea21ef083bbbe0 65436 libs optional 
mozjs102_102.15.1-3.debian.tar.xz
 6577943566fab9d2233adc8a02599f4d 14647 libs optional 
mozjs102_102.15.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXjsagACgkQ5mx3Wuv+
bH1a3Q/9HYuA2dwjKOBKQs8LZY2bWfsQ6Nt6D7zPqAHzN64Te+vo3lN4GSIsPMrv
Sj3NDkRLOWbil7N06dCAxtpVZtiwTLmgBWZYkWC4jkSBfGfhMhyyHTRVKOcoxCD3
ILbesUCrn20HWU4/X2PgL+7U4PfccnnkunJVOXrIZGCCFwROA3LeAQzlpy3CQJZE
c7eNlLhalFNa62AqKk/uD1xkLfR2oLAVzeD032PES6gOFxwzsnqAX2IQXzKQZY3n
jyrZQCGrE0c/UxmGxPyK12G38VHk8QCTRl0nDk+twsltpC1b1IVJJhgJetaPlm+I
u/QFkmzDIsDTUSrHuUUo2YsxN8TS2EO07Wy5RYvuqmrOB4msBH5Vg9/BQPelWdLh
ki/EXKuPbohx16M66OhsoAgxKMvck1h8/aqQU8DE/U074jyFccNnMevg59+3/WO1
6FCli7QkxD+Wagoc30Z9JdZ+xrMU/i5pm7Q0f2KpVlfwnsXZhvTHRWzzF5OAIZ/D
zoprP/45TP4ioD/4yLIVEuVm75Ltr9ypFoWMT8FYRqyhfwZ4c7YRU3T0Q6jFTvha
bJzExTbawITKGXVjXngDvbcdioASrchxvbRan6oo5Zl/QST3vYebvEdrOIHVs2Dw
eIebKqPIX1mY0H8H9CvTeWQw954HA/CuyiOrL5FHsdJ8UDRrLRI=
=6/90
-END PGP SIGNATURE-



pgpu1kZ3F_ryZ.pgp
Description: PGP signature
--- End Message ---

Bug#1065275: mariadb: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Hi Otto

On 2024-03-02 08:19:31 -0800, Otto Kekäläinen wrote:
> Hi Sabastian!
> 
> > * The package is built with the wrong ABI.
> > * The package migrates to testing before the change is enabled in
> >   testing and builds there would be produced against the wrong ABI.
> >
> > Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
> > version ASAP.
> 
> Thanks for following up with builds and transitions. I can do an
> upload quickly but would like to avoid having to do a third one, so:
> 
> Could you Sebastian perhaps quickly skim through the commit that
> implemented this
> https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/8194544349982990fb2585c2a8c15c4db3904735
> and say if there might be something else missing as well?

Did you mean
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/d2a0784f1e01b6613fefda17199a4e9867a126c3?

At least for now that looks good.

Cheers
-- 
Sebastian Ramacher

Bug#1062095: marked as done (colord-gtk: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 23:19:54 +
with message-id 
and subject line Bug#1062095: fixed in colord-gtk 0.3.1-1
has caused the Debian Bug report #1062095,
regarding colord-gtk: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1062095: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062095
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: colord-gtk
Version: 0.3.0-4
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

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
colord-gtk 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 colord-gtk
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-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 colord-gtk-0.3.0/debian/changelog colord-gtk-0.3.0/debian/changelog
--- colord-gtk-0.3.0/debian/changelog   2023-06-15 16:04:11.0 +
+++ colord-gtk-0.3.0/debian/changelog   2024-01-31 10:59:51.0 +
@@ -1,3 +1,10 @@
+colord-gtk (0.3.0-4.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 31 Jan 2024 10:59:51 +
+
 colord-gtk (0.3.0-4) unstable; urgency=medium
 
   * Team upload
diff -Nru colord-gtk-0.3.0/debian/control colord-gtk-0.3.0/debian/control
--- colord-gtk-0.3.0/debian/control 2023-06-15 16:04:11.0 +
+++ colord-gtk-0.3.0/debian/control 2024-01-31 10:59:50.0 +
@@ -20,7 +20,10 @@
 Vcs-Git: https://salsa.debian.org/debian/colord-gtk.git
 Vcs-Browser: https://salsa.debian.org/debian/colord-gtk
 
-Package: libcolord-gtk1
+Package: libcolord-gtk1t64
+Provides: ${t64:Provides}
+Replaces: libcolord-gtk1
+Breaks: libcolord-gtk1 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${shlibs:Depends},
@@ -37,7 +40,10 @@
  .
  This package contains the runtime libraries.
 
-Package: libcolord-gtk4-1
+Package: libcolord-gtk4-1t64
+Provides: ${t64:Provides}
+Replaces: libcolord-gtk4-1
+Breaks: libcolord-gtk4-1 (<< ${source:Version})
 Section: libs
 Architecture: any
 Depends: ${shlibs:Depends},
@@ -58,7 +64,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libcolord-gtk1 (= ${binary:Version}),
+Depends: libcolord-gtk1t64 (= ${binary:Version}),
  libcolord-gtk-headers (= ${binary:Version}),
  libcolord-dev,
  libgtk-3-dev,
@@ -81,7 +87,7 @@
 Section: libdevel
 Architecture: any
 Multi-Arch: same
-Depends: libcolord-gtk4-1 (= ${binary:Version}),
+Depends: libcolord-gtk4-1t64 (= ${binary:Version}),
  libcolord-gtk-headers (= ${binary:Version}),
  libcolord-dev,
  libgtk-4-dev,
diff -Nru colord-gtk-0.3.0/debian/libcolord-gtk1.install 
colord-gtk-0.3.0/debian/libcolord-gtk1.install
--- colord-gtk-0.3.0/debian/libcolord-gtk1.install  

Bug#1062309: marked as done (libgdamm5.0: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 2 Mar 2024 18:14:27 -0500
with message-id 

and subject line Re: libgdamm5.0: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1062309,
regarding libgdamm5.0: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1062309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062309
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgdamm5.0
Version: 4.99.11-3
Severity: serious
Tags: patch pending
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

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
libgdamm5.0 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 libgdamm5.0
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'), (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 libgdamm5.0-4.99.11/debian/changelog 
libgdamm5.0-4.99.11/debian/changelog
--- libgdamm5.0-4.99.11/debian/changelog2018-12-28 14:54:20.0 
+
+++ libgdamm5.0-4.99.11/debian/changelog2024-02-01 01:23:49.0 
+
@@ -1,3 +1,10 @@
+libgdamm5.0 (4.99.11-3.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Thu, 01 Feb 2024 01:23:49 +
+
 libgdamm5.0 (4.99.11-3) unstable; urgency=medium
 
   * Add -Wl,-O1 to our LDFLAGS
diff -Nru libgdamm5.0-4.99.11/debian/control libgdamm5.0-4.99.11/debian/control
--- libgdamm5.0-4.99.11/debian/control  2018-12-28 14:54:20.0 +
+++ libgdamm5.0-4.99.11/debian/control  2024-02-01 01:23:49.0 +
@@ -6,7 +6,7 @@
 Section: libs
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

-Uploaders: Jeremy Bicha 
+Uploaders: 
 Build-Depends: debhelper (>= 11),
gnome-pkg-tools,
libglibmm-2.4-dev (>= 2.46.1),
@@ -22,7 +22,10 @@
 Vcs-Git: https://salsa.debian.org/gnome-team/libgdamm5.0.git
 Homepage: http://www.gtkmm.org/
 
-Package: libgdamm-5.0-13
+Package: libgdamm-5.0-13t64
+Provides: ${t64:Provides}
+Replaces: libgdamm-5.0-13
+Breaks: libgdamm-5.0-13 (<< ${source:Version})
 Architecture: any
 Depends: ${misc:Depends},
  ${shlibs:Depends}
@@ -37,7 +40,7 @@
 Section: libdevel
 Depends: ${misc:Depends},
  ${shlibs:Depends},
- libgdamm-5.0-13 (= ${binary:Version}),
+ libgdamm-5.0-13t64 (= ${binary:Version}),
  libglibmm-2.4-dev (>= 2.27.93),
  libgda-5.0-dev (>= 4.1.7)
 Suggests: libgdamm5.0-doc
diff -Nru libgdamm5.0-4.99.11/debian/control.in 
libgdamm5.0-4.99.11/debian/control.in
--- libgdamm5.0-4.99.11/debian/control.in   2018-12-28 14:54:20.0 
+
+++ libgdamm5.0-4.99.11/debian/control.in   2024-02-01 01:23:49.0 
+
@@ -18,7 +18,10 @@
 Vcs-Git: https://salsa.debian.org/gnome-team/libgdamm5.0.git
 Homepage: http://www.gtkmm.org/
 
-Package: 

Bug#1065287: marked as done (gnome-bluetooth: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 23:04:11 +
with message-id 
and subject line Bug#1065287: fixed in gnome-bluetooth 3.34.5-13
has caused the Debian Bug report #1065287,
regarding gnome-bluetooth: missing dpkg-dev (>= 1.22.5) build dependency for 
time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065287: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065287
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-bluetooth
Version: 3.34.5-12
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gnome-bluetooth
Source-Version: 3.34.5-13
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
gnome-bluetooth, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gnome-bluetooth package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 17:56:28 -0500
Source: gnome-bluetooth
Built-For-Profiles: noudeb
Architecture: source
Version: 3.34.5-13
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1065287
Changes:
 gnome-bluetooth (3.34.5-13) unstable; urgency=medium
 .
   * Build-depend on dpkg-dev (>= 1.22.5) (Closes: #1065287)
Checksums-Sha1:
 5e9be40f49c9417fd942086b7a336095259cae48 2819 gnome-bluetooth_3.34.5-13.dsc
 bca4f1915e9cf67878fa87fcb42fa6ebfdabfed6 12556 
gnome-bluetooth_3.34.5-13.debian.tar.xz
 06c415d19b37a3b73cec7dba5adb7497b0f8d9e5 20306 
gnome-bluetooth_3.34.5-13_source.buildinfo
Checksums-Sha256:
 90317594bc2651ab2548dfb082ab7d14037bac106b80c4f6b92b865013841866 2819 
gnome-bluetooth_3.34.5-13.dsc
 e0b228dcce3e5022629329501360de56add7817043caa47d367a02c701740190 12556 
gnome-bluetooth_3.34.5-13.debian.tar.xz
 04741d9842c6d5ed0d31c45c621e3b3ec6132fc3b827b949c74bda5b08d31884 20306 
gnome-bluetooth_3.34.5-13_source.buildinfo
Files:
 f07f1d8bd9f72077b7929784c97e0eea 2819 gnome optional 
gnome-bluetooth_3.34.5-13.dsc
 1a9c1b28fb3541b6290193e4c5e8fb06 12556 gnome optional 
gnome-bluetooth_3.34.5-13.debian.tar.xz
 fef5592d503e48a60e219ec28d31c45c 20306 gnome optional 
gnome-bluetooth_3.34.5-13_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXjrtQACgkQ5mx3Wuv+
bH3G8BAAmL8aEPIcnKl674SlEGUULVl1WrLUevNzxuZwBcfph/RtSlH4vvJUYg3e
hX7ZHLLTtQCIZKOB6vfYBgR+QLvxLAdKvuJO3c8F/hPYIKPgOn/pmxvRI3tiFdRB
UY9+kvrjlFsgMuYwpQxyrJhgeoCLmmNDty7tVVfFwYQBMQFdQBE/da/YOuQ7ohbl
JQSYQx68wSEssxGDGb76nU4TnAsGHprtzve32p80q/4WHcQrblKFUC8/lPzR/+ay
167qZZU/QoQGQ6qXtTK5DtiNTSU8k2nSpbhQ16NwfmLNgs3sQifu2S8L2vIVdIbr
jCnLZfvVjYYgX8lKHKi5gI17bBqrXvwpLZFqbULO+KO6yc3pcMv20iHHosbqPirv
9xCeqnARNmMRKU2k96AWCB1AJUPfHSxE8k0hGaP25Am3QCl8nFoA3dzfmX5qZbXq
YGVFAFypCmQNiydPV8OQyBPzIvL6aO7ZkftFqgT3Jdy99RkA84XPqc7qs70K8GQ1
vBbsbYtbFvcsnqHHDlViv/d9+/lcqBFP02uoOS7kwRAIsdeoLRBIWrI5mbKmWMjl
2KimG8tABWg8vIgOGeR2oVivM6LG65oXyPVOaDKJOQuHjxFb3FbBSb4oQmJMf8LI
h1MHQwKsO8S1TMBPq/QxIdseoqVDzUYD4IELCzkDR/qL8U99C6A=
=d/D/
-END PGP SIGNATURE-



pgp7zpL5Kz6nZ.pgp
Description: PGP signature
--- End Message ---

Bug#1065288: marked as done (gnome-desktop: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 23:04:24 +
with message-id 
and subject line Bug#1065288: fixed in gnome-desktop 44.0-5
has caused the Debian Bug report #1065288,
regarding gnome-desktop: missing dpkg-dev (>= 1.22.5) build dependency for 
time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnome-desktop
Version: 44.0-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: gnome-desktop
Source-Version: 44.0-5
Done: Jeremy Bícha 

We believe that the bug you reported is fixed in the latest version of
gnome-desktop, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated gnome-desktop package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 17:58:49 -0500
Source: gnome-desktop
Built-For-Profiles: noudeb
Architecture: source
Version: 44.0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1065288
Changes:
 gnome-desktop (44.0-5) unstable; urgency=medium
 .
   * Build-depend on dpkg-dev (>= 1.22.5) (Closes: #1065288)
Checksums-Sha1:
 751ab644f37cbf06c5ad363912d86cd3c33d4df1 4045 gnome-desktop_44.0-5.dsc
 5355c1ed3fb1f74cfd7080178d048f3c02e3a976 34936 
gnome-desktop_44.0-5.debian.tar.xz
 506004b6871670e88c3e2a679057a795baa67cf5 20493 
gnome-desktop_44.0-5_source.buildinfo
Checksums-Sha256:
 34b0801607dfdbc123da63c605548078e7555e8b8772e1129c919bb46c499d56 4045 
gnome-desktop_44.0-5.dsc
 546420fe0f4b6dfafdfc9edb181047a5cb24e25e8ec123791eccd920d8fa6f4c 34936 
gnome-desktop_44.0-5.debian.tar.xz
 5c4f66c8bb023ff388b6907a7cc1c764a4da0525a10e4ceae10bdb1ca0d309c1 20493 
gnome-desktop_44.0-5_source.buildinfo
Files:
 11e7f623c2263fc9fe9afa889a7cd486 4045 gnome optional gnome-desktop_44.0-5.dsc
 87d4686d0fff070f4a26ca80da6f5ece 34936 gnome optional 
gnome-desktop_44.0-5.debian.tar.xz
 0b4ae2bc56c369d8faa5069c36bd0819 20493 gnome optional 
gnome-desktop_44.0-5_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETQvhLw5HdtiqzpaW5mx3Wuv+bH0FAmXjr2gACgkQ5mx3Wuv+
bH1QfhAAg4CobbGG0T2ubYZKVQ0WY4OsQS5r3Mm6IZZKmBNTF8Mxlgb28L02Xb3T
DkVmqPjEN3eO4XRMuPAmxpb+qGBscSO1OqLHpjgbLHEdoM701DQsty2PAMyVKmCW
bDDIFwZtG00NuXdkX/v2M4TpVNP8isLnXqhW3wvSxJmkV6fMT4CPXjFCjS/g2P4n
0m9aNAUbnDiAUKHiTFz0CYF4obQ1ajpGhg8tIYDqvXIyOUflUl3vsacR5NtmOGIV
LTqUMeMDA4/pDCi+ZVfu6kY9XkmCIMWVHglUawaHUQWWzWkIIH5uVuLmwOf/90M+
HdoSndEVr5UJW1jdjcyNPos/q0bleWlidGtCMQsmlHD5qM1r1sIXiX9tI7TEJ3hK
yaEOynYHdA1uHmaEVfwy8kUbSFd8Whc6QY/pCp3XsJv2H85dwW6bEyoz0LD6PMtJ
KJ3jOVFnyiFju3IPDCbIfz5kgNyGV5EaRZrMuAt7fcWLicsB0zT/OZWS3nU8Wwvo
RjORsaMFTqwSHp91tewTtr8PwiOmTdzgtcNqIvj6rdHrMW67DZuxISlr4uADKWGz
JhTn7vzzNkJ5X6EUJljrmJiMiBwAE9XeFfyeCQ31DFW2PiJQLvp/Q6jZ9yhw0AoC
0+H8j5LR+Ll8LwiUDCh8aZikHOwAFUbZwlKnhBO8Kc6BzlMU5wA=
=PGyn
-END PGP SIGNATURE-



pgpX7fU4mTyma.pgp
Description: PGP signature
--- End Message ---

Bug#1065003: marked as done (libhinawa: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 2 Mar 2024 14:59:00 -0800
with message-id 
and subject line Re: libhinawa: NMU diff for 64-bit time_t transition
has caused the Debian Bug report #1065003,
regarding libhinawa: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065003: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhinawa
Version: 4.0.1-2
Severity: serious
Tags: patch pending sid trixie
Justification: library ABI skew on upgrade
User: debian-...@lists.debian.org
Usertags: time-t

Dear maintainer,

Apologies, but it appears that somehow we failed to file a bug report sooner
about libhinawa or upload it to experimental as part of this transition
preparation!  But libhinawa is identified as being affected, so I'm
reporting this now and doing a 0-day NMU to unstable.

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
libhinawa as a source package shipping runtime libraries whose ABI 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 libhinawa which
will be uploaded to unstable.

Please find the patch for this NMU attached.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru libhinawa-4.0.1/debian/changelog libhinawa-4.0.1/debian/changelog
--- libhinawa-4.0.1/debian/changelog2024-02-25 11:52:44.0 +
+++ libhinawa-4.0.1/debian/changelog2024-02-28 20:37:13.0 +
@@ -1,3 +1,10 @@
+libhinawa (4.0.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Steve Langasek   Wed, 28 Feb 2024 20:37:13 +
+
 libhinawa (4.0.1-2) unstable; urgency=medium
 
   [ Takashi Sakamoto ]
diff -Nru libhinawa-4.0.1/debian/control libhinawa-4.0.1/debian/control
--- libhinawa-4.0.1/debian/control  2024-02-25 11:52:44.0 +
+++ libhinawa-4.0.1/debian/control  2024-02-28 20:35:29.0 +
@@ -16,13 +16,14 @@
 Vcs-Browser: https://salsa.debian.org/debian/libhinawa/
 Vcs-Git: https://salsa.debian.org/debian/libhinawa.git
 
-Package: libhinawa4
+Package: libhinawa4t64
+Provides: ${t64:Provides}
 Architecture: linux-any
 Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends},
 libglib2.0-0 (>= 2.44.0)
-Breaks: libhinawa2 (<< 4.0.0)
-Replaces: libhinawa2 (<< 4.0.0)
+Breaks: libhinawa4 (<< ${source:Version}), libhinawa2 (<< 4.0.0)
+Replaces: libhinawa4, libhinawa2 (<< 4.0.0)
 Multi-Arch: same
 Description: I/O library for IEEE 1394 asynchronous transaction
  This is an I/O library to operate 1394 OHCI hardware for asynchronous
@@ -32,11 +33,11 @@
 Section: introspection
 Architecture: linux-any
 Depends: ${misc:Depends}, ${gir:Depends},
-libhinawa4 (= ${binary:Version}),
+libhinawa4t64 (= ${binary:Version}),
 Breaks: gir1.2-hinawa-3.0 (<< 4.0.0)
 Replaces: gir1.2-hinawa-3.0 (<< 4.0.0)
 Multi-Arch: same
-Description: GObjet introspection data for libhinawa4
+Description: GObjet introspection data for libhinawa4t64
  This package contains introspection data for libhinawa4. It can be
  used by packages using the GIRepository format to generate dynamic
  bindings, or it can be used by interpreters understanding the
@@ -46,7 +47,7 @@
 Section: libdevel
 Architecture: linux-any
 Depends: ${misc:Depends},
-libhinawa4 (= ${binary:Version}),
+libhinawa4t64 (= ${binary:Version}),
 libglib2.0-dev (>= 2.44.0),
 libgirepository1.0-dev (>= 1.32.1),
 gir1.2-hinawa-4.0 (= ${binary:Version})
diff -Nru libhinawa-4.0.1/debian/libhinawa4.install 
libhinawa-4.0.1/debian/libhinawa4.install
--- libhinawa-4.0.1/debian/libhinawa4.install   

Bug#1065212: marked as done (asymptote: recent libc6-dev change causes XDR and V3D support to be dropped)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 22:49:22 +
with message-id 
and subject line Bug#1065212: fixed in asymptote 2.87+ds-1
has caused the Debian Bug report #1065212,
regarding asymptote: recent libc6-dev change causes XDR and V3D support to be 
dropped
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065212: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065212
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asymptote
Version: 2.86+ds1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libtirpc-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes XDR and V3D
support in asymptote to be dropped, something which is not recommended
by upstream.

This can be fixed by adding an explicit Build-Depends on libtirpc-dev.
The glibc change will likely be reverted in the short term, but given
its a change we want to do for Trixie, this will only lower the severity
of the bug.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: asymptote
Source-Version: 2.87+ds-1
Done: Hilmar Preusse 

We believe that the bug you reported is fixed in the latest version of
asymptote, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Hilmar Preusse  (supplier of updated asymptote package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 23:29:20 +0100
Source: asymptote
Architecture: source
Version: 2.87+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian TeX Task Force 
Changed-By: Hilmar Preusse 
Closes: 1061151 1065212
Changes:
 asymptote (2.87+ds-1) unstable; urgency=medium
 .
   * New upstream release, refresh patches.
   * Replace freeglut3-dev by libglut-dev in control file of test suite.
   * Remove libboost-dev from control file of test suite.
   * Run test suite during build (Closes: #1061151).
   * Add libtirpc-dev to build depends of asymptote and test suite
 (Closes: #1065212).
Checksums-Sha1:
 9f3eeb99faf4ea996cabb781e9b72b52d9b5c506 3380 asymptote_2.87+ds-1.dsc
 f0091c4ee70c5f670b48c9ba9835f915c68fea49 15046658 asymptote_2.87+ds.orig.tar.gz
 52765528e27999b2f2f0477a4bbe2b484da915d8 27588 
asymptote_2.87+ds-1.debian.tar.xz
 b52f0ff7c9352778d6b124c70d59a8f151de3969 5562 
asymptote_2.87+ds-1_source.buildinfo
Checksums-Sha256:
 68189e8c24b51e518eabacac97f25d8fde2ebc07a1b8cad5c4636555f11b9bbb 3380 
asymptote_2.87+ds-1.dsc
 c6ab88501e55c986a62bb7483076fe9874bbfc26f1c9be94f1313bf97d355005 15046658 
asymptote_2.87+ds.orig.tar.gz
 c401ed46cb28c9487b6e790cc52bbba81020484697ac80ffd69e9a9dcba87b1a 27588 
asymptote_2.87+ds-1.debian.tar.xz
 f8788ba80ac8c492d84564c9fded2dd6e265d24ec82381a41adfe2bbd18eda70 5562 
asymptote_2.87+ds-1_source.buildinfo
Files:
 fcf4f6156fabfb8026810bdc269b6e03 3380 tex optional asymptote_2.87+ds-1.dsc
 27e79b0ce7a0dd434769033d7fe6b3e3 15046658 tex optional 
asymptote_2.87+ds.orig.tar.gz
 54d8d0b3e4a1bf63560c6f5e43e29343 27588 tex optional 
asymptote_2.87+ds-1.debian.tar.xz
 a6f31a6ad59b074cfe7f25fb791442a0 5562 tex optional 
asymptote_2.87+ds-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEaXGmC/nkbIhxf16kxiZYRqvgLIsFAmXjqH5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDY5
NzFBNjBCRjlFNDZDODg3MTdGNUVBNEM2MjY1ODQ2QUJFMDJDOEIACgkQxiZYRqvg
LIupDhAAh99Oe5lPoM+H4dOmhiwkpWlH6eHxvSbWREwoRAqYujt2C7cAOBC54LQt
PriG7xXY6D1q3qKCK4iIKHkrFvRyOGzk61a8e+k7tSX8Cd+O/nlE+vwvHYnrn1Pf
EYttZE7CoL4U+dA66iWHDVf4a8uGkisO43RxT0YrxqXJsdfnyJpmAcjibtx8yEG4
5BR+zmUU+X9QJuhC16p6ZIlWGRIvLpauh1egwHZ0EgBMzZaZckVjviqIZ0nO4+T6
+Fek6fCkJY3hx6cDaK2ErqsHRL+zLZVNb7vMXHPgyq7y9bXUVuUuXNoJ8VfpPK9n

Processed: found 1063324 in 4.6.0.0+ds1-5.1, found 1063403 in 0.2-8.1 ..., notfound 1065330 in 1.26.3-2 ...

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 1063324 4.6.0.0+ds1-5.1
Bug #1063324 [libuhd4.6.0-dpdk] libuhd4.6.0-dpdk has an undeclared file 
conflict on /usr/lib/x86_64-linux-gnu/libuhd.so.4.6.0
Marked as found in versions uhd/4.6.0.0+ds1-5.1.
> found 1063403 0.2-8.1
Bug #1063403 [libeegdev-dev,libeegdev0t64] libeegdev-dev,libeegdev0t64: both 
ship /usr/share/doc/libeegdev0/changelog.gz
Marked as found in versions eegdev/0.2-8.1.
> reassign 1065267 libebook-contacts-1.2-4t64 3.50.3-2
Bug #1065267 [libphonenumber8-protobuf32] libphonenumber8-protobuf32: required 
package missing in repositories
Warning: Unknown package 'libphonenumber8-protobuf32'
Bug reassigned from package 'libphonenumber8-protobuf32' to 
'libebook-contacts-1.2-4t64'.
Ignoring request to alter found versions of bug #1065267 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1065267 to the same values 
previously set
Bug #1065267 [libebook-contacts-1.2-4t64] libphonenumber8-protobuf32: required 
package missing in repositories
Marked as found in versions evolution-data-server/3.50.3-2.
> notfound 1065330 1.26.3-2
Bug #1065330 [src:numpy] numpy_1.26.3-2_ppc64el-buildd.changes REJECTED
The source 'numpy' and version '1.26.3-2' do not appear to match any binary 
packages
No longer marked as found in versions numpy/1.26.3-2.
> found 1065330 1:1.26.3-2
Bug #1065330 [src:numpy] numpy_1.26.3-2_ppc64el-buildd.changes REJECTED
The source 'numpy' and version '1:1.26.3-2' do not appear to match any binary 
packages
Marked as found in versions numpy/1:1.26.3-2.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1063324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063324
1063403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063403
1065267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065267
1065330: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065330
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1064188: mrpt: NMU diff for 64-bit time_t transition

[Steve Langasek]

On Fri, Mar 01, 2024 at 12:03:26PM +0100, José Luis Blanco-Claraco wrote:
> Hi Steve,
> As package and upstream's maintainer, what should I do to ensure the
> library is change safe?

> Would it help to totally remove references to time_t in all public headers?

I don't understand what you mean by "change safe". The API is the API, and
we have uploaded it to pick up the new 64-bit time_t ABI.

> El dom, 18 feb 2024, 9:00, Steve Langasek  escribió:
> 
> > Source: mrpt
> > Version: 1:2.11.9+ds-1
> > Severity: important
> > Tags: patch pending sid trixie
> > 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
> > mrpt 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 mrpt
> > 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)
> >

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org


signature.asc
Description: PGP signature

Processed: Bug#1062125 marked as pending in gimp

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1062125 [src:gimp] gimp: NMU diff for 64-bit time_t transition
Ignoring request to alter tags of bug #1062125 to the same tags previously set

-- 
1062125: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062125
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1062125: marked as pending in gimp

[Jeremy Bicha]

Control: tag -1 pending

Hello,

Bug #1062125 in gimp reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/gnome-team/gimp/-/commit/7e85479a60b0fbd4dfe558dba370cd6b0dd6dc23


Rename libraries for 64-bit time_t transition

Closes: #1062125


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1062125

Bug#1062403: marked as done (freecontact: NMU diff for 64-bit time_t transition)

[Étienne Mollier]

From mwhud...@debian.org:
> This has been uploaded now, but unfortunately I forgot to include the bug
> number in the changelog. Apologies.

No worries, I happen to trip on this carpet from time to time.
NMU is acknowledged in the VCS, thanks for the work on the
64-bit time_t transition!

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

Bug#1065330: numpy_1.26.3-2_ppc64el-buildd.changes REJECTED

[Aurelien Jarno]

Source: numpy
Version: 1.26.3-2
Severity: serious

On 2024-03-02 22:06, Debian FTP Masters wrote:
> 
> 
> python3-numpy_1.26.3-2_ppc64el.deb: has 876 file(s) with a timestamp too far 
> in the past:
>   usr/lib/python3/dist-packages/numpy/LICENSE.txt (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/__init__.cython-30.pxd (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/__init__.pxd (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/__init__.py (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/__init__.pyi (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_core/__init__.py (Thu 
> Jan  1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_core/_dtype.py 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_core/_dtype_ctypes.py (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_core/_internal.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_core/_multiarray_umath.py (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_core/multiarray.py (Thu 
> Jan  1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_core/umath.py 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_distributor_init.py (Thu Jan  1 00:00:00 
> 1970)  usr/lib/python3/dist-packages/numpy/_globals.py (Thu Jan  1 00:00:00 
> 1970)  usr/lib/python3/dist-packages/numpy/_pyinstaller/__init__.py (Thu Jan  
> 1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_pyinstaller/hook-numpy.py (Thu Jan  1 
> 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_pyinstaller/pyinstaller-smoke.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_pyinstaller/test_pyinstaller.py (Thu Jan 
>  1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_pytesttester.py (Thu 
> Jan  1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_pytesttester.pyi 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_typing/__init__.py (Thu Jan  1 00:00:00 
> 1970)  usr/lib/python3/dist-packages/numpy/_typing/_add_docstring.py (Thu Jan 
>  1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_typing/_array_like.py 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_typing/_callable.pyi (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_typing/_char_codes.py 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_typing/_dtype_like.py (Thu Jan  1 
> 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_typing/_extended_precision.py (Thu Jan  
> 1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_typing/_nbit.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_typing/_nested_sequence.py (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_typing/_scalars.py (Thu 
> Jan  1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_typing/_shape.py 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_typing/_ufunc.pyi (Thu Jan  1 00:00:00 
> 1970)  usr/lib/python3/dist-packages/numpy/_typing/setup.py (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_utils/__init__.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/_utils/_convertions.py (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_utils/_inspect.py (Thu 
> Jan  1 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/_utils/_pep440.py 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/__init__.py (Thu Jan  1 
> 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_array_object.py (Thu Jan  1 
> 00:00:00 1970)  usr/lib/python3/dist-packages/numpy/array_api/_constants.py 
> (Thu Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_creation_functions.py (Thu Jan 
>  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_data_type_functions.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_dtypes.py (Thu Jan  1 00:00:00 
> 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_elementwise_functions.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_indexing_functions.py (Thu Jan 
>  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_manipulation_functions.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_searching_functions.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_set_functions.py (Thu Jan  1 
> 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_sorting_functions.py (Thu Jan  
> 1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_statistical_functions.py (Thu 
> Jan  1 00:00:00 1970)  
> usr/lib/python3/dist-packages/numpy/array_api/_typing.py (Thu Jan  1 00:00:00 
> 1970)  usr/lib/python3/dist-packages/numpy/array_api/_utility_functions.py 
> (Thu Jan  1 00:00:00 1970)  
> 

Processed: Re: Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 broadcom-sta-dkms: module build fails for Linux 6.X-rcY (only two 
> version components)
Bug #1057447 [broadcom-sta-dkms] broadcom-sta-dkms: module build fails for 
Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 
'wireless_handlers'
Changed Bug title to 'broadcom-sta-dkms: module build fails for Linux 6.X-rcY 
(only two version components)' from 'broadcom-sta-dkms: module build fails for 
Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 
'wireless_handlers''.

-- 
1057447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

[Andreas Beckmann]

Control: retitle -1 broadcom-sta-dkms: module build fails for Linux 6.X-rcY 
(only two version components)

On 02/03/2024 22.06, Eduard Bloch wrote:

Thanks, and sorry, I overlooked the last message. I guess we should take
it as is.


I should have updated the misleading bug title after finding the real
cause ...  this time it was not a change in the kernel causing the
failure but a the logic flaw leading to usage of the wrong code path.

Attached are updated versions of two more patches that restore
compatibility with older Linux releases. Let's just use the old or new
names depending on the kernel version ...

(With these three applied, broadcom-sta successfully survives my dkms
torture chroot which contains some header packages for most kernels we
had in sid/stable/security/backports since 2.6.32 ;-)

AndreasFrom: Diego Escalante Urrelo 
Date: Sun, 2 Aug 2020 19:54:56 -0500
Subject: wl: Use the right enums for cfg80211_get_bss

---
 amd64/src/wl/sys/wl_cfg80211_hybrid.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

--- a/amd64/src/wl/sys/wl_cfg80211_hybrid.c
+++ b/amd64/src/wl/sys/wl_cfg80211_hybrid.c
@@ -2309,7 +2309,13 @@ static s32 wl_update_bss_info(struct wl_
 
 	ssid = >profile->ssid;
 	bss = cfg80211_get_bss(wl_to_wiphy(wl), NULL, (s8 *)>bssid,
-	  ssid->SSID, ssid->SSID_len, WLAN_CAPABILITY_ESS, WLAN_CAPABILITY_ESS);
+			   ssid->SSID, ssid->SSID_len,
+#if LINUX_VERSION_CODE < KERNEL_VERSION(4, 1, 0)
+			   WLAN_CAPABILITY_ESS, WLAN_CAPABILITY_ESS
+#else
+			   IEEE80211_BSS_TYPE_ESS, IEEE80211_PRIVACY_ANY
+#endif
+			   );
 
 	rtnl_lock();
 	if (!bss) {
From: Felix Yan 
Date: Mon, 20 Jun 2016 11:18:00 +0800
Subject: linux47

Origin: https://github.com/archlinuxcn/repo/tree/f4d6cff1cacf8dad13006fade5f96bc2cf020a9b/broadcom-wl-dkms

Since Linux 4.7, the enum ieee80211_band is no longer used

This shall cause no problem's since both enums ieee80211_band
and nl80211_band were added in the same commit:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=13ae75b103e07304a34ab40c9136e9f53e06475c

This patch refactors the references of IEEE80211_BAND_* to NL80211_BAND_*

Reference:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit?id=57fbcce37be7c1d2622b56587c10ade00e96afa3

This patch is based on
https://github.com/archlinuxcn/repo/tree/f4d6cff1cacf8dad13006fade5f96bc2cf020a9b/broadcom-wl-dkms .
---
 amd64/src/wl/sys/wl_cfg80211_hybrid.c | 24 
 1 file changed, 12 insertions(+), 12 deletions(-)

--- a/amd64/src/wl/sys/wl_cfg80211_hybrid.c
+++ b/amd64/src/wl/sys/wl_cfg80211_hybrid.c
@@ -235,8 +235,13 @@ static s8 wl_dbg_estr[][WL_DBG_ESTR_MAX]
 };
 #endif
 
+#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 34)
+#define NL80211_BAND_2GHZ IEEE80211_BAND_2GHZ
+#define NL80211_BAND_5GHZ IEEE80211_BAND_5GHZ
+#endif
+
 #define CHAN2G(_channel, _freq, _flags) {			\
-	.band			= IEEE80211_BAND_2GHZ,		\
+	.band			= NL80211_BAND_2GHZ,		\
 	.center_freq		= (_freq),			\
 	.hw_value		= (_channel),			\
 	.flags			= (_flags),			\
@@ -245,7 +250,7 @@ static s8 wl_dbg_estr[][WL_DBG_ESTR_MAX]
 }
 
 #define CHAN5G(_channel, _flags) {\
-	.band			= IEEE80211_BAND_5GHZ,		\
+	.band			= NL80211_BAND_5GHZ,		\
 	.center_freq		= 5000 + (5 * (_channel)),	\
 	.hw_value		= (_channel),			\
 	.flags			= (_flags),			\
@@ -379,7 +384,7 @@ static struct ieee80211_channel __wl_5gh
 };
 
 static struct ieee80211_supported_band __wl_band_2ghz = {
-	.band = IEEE80211_BAND_2GHZ,
+	.band = NL80211_BAND_2GHZ,
 	.channels = __wl_2ghz_channels,
 	.n_channels = ARRAY_SIZE(__wl_2ghz_channels),
 	.bitrates = wl_g_rates,
@@ -387,7 +392,7 @@ static struct ieee80211_supported_band _
 };
 
 static struct ieee80211_supported_band __wl_band_5ghz_a = {
-	.band = IEEE80211_BAND_5GHZ,
+	.band = NL80211_BAND_5GHZ,
 	.channels = __wl_5ghz_a_channels,
 	.n_channels = ARRAY_SIZE(__wl_5ghz_a_channels),
 	.bitrates = wl_a_rates,
@@ -395,7 +400,7 @@ static struct ieee80211_supported_band _
 };
 
 static struct ieee80211_supported_band __wl_band_5ghz_n = {
-	.band = IEEE80211_BAND_5GHZ,
+	.band = NL80211_BAND_5GHZ,
 	.channels = __wl_5ghz_n_channels,
 	.n_channels = ARRAY_SIZE(__wl_5ghz_n_channels),
 	.bitrates = wl_a_rates,
@@ -1876,8 +1881,8 @@ static s32 wl_alloc_wdev(struct device *
 	wdev->wiphy->max_num_pmkids = WL_NUM_PMKIDS_MAX;
 #endif
 	wdev->wiphy->interface_modes = BIT(NL80211_IFTYPE_STATION) | BIT(NL80211_IFTYPE_ADHOC);
-	wdev->wiphy->bands[IEEE80211_BAND_2GHZ] = &__wl_band_2ghz;
-	wdev->wiphy->bands[IEEE80211_BAND_5GHZ] = &__wl_band_5ghz_a; 
+	wdev->wiphy->bands[NL80211_BAND_2GHZ] = &__wl_band_2ghz;
+	wdev->wiphy->bands[NL80211_BAND_5GHZ] = &__wl_band_5ghz_a; 
 	wdev->wiphy->signal_type = CFG80211_SIGNAL_TYPE_MBM;
 	wdev->wiphy->cipher_suites = __wl_cipher_suites;
 	wdev->wiphy->n_cipher_suites = ARRAY_SIZE(__wl_cipher_suites);
@@ -2000,7 +2005,7 @@ static s32 wl_inform_single_bss(struct w
 #if LINUX_VERSION_CODE >= KERNEL_VERSION(2, 6, 39)
 	freq = 

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

[Eduard Bloch]

Hallo,
* Andreas Beckmann [Fri, Feb 23 2024, 06:27:26PM]:
> Followup-For: Bug #1057447
> Control: found -1 6.30.223.271-24~exp1
> Control: tag -1 + patch
>
> This issue is caused by
> a) version parsing that expects three numeric components (6.6.1-foo) and
>fails if there are only two (6.7-rc1)
> b) broken version comparison logic
> which turn on APICHOICE=FORCE_WEXT on kernels without
> CONFIG_WIRELESS_EXT
>
> Attached patch fixes that.

Thanks, and sorry, I overlooked the last message. I guess we should take
it as is. Any opinion from Roger or Cyril?

BR,
Eduard.

--
* weasel hatte letztens eine nette idee fuer ein namensschema
 hab's aber leider wieder vergessen :(

Processed: Re: Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1057447 +moreinfo
Bug #1057447 [broadcom-sta-dkms] broadcom-sta-dkms: module build fails for 
Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 
'wireless_handlers'
Added tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1057447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

[Eduard Bloch]

tags 1057447 +moreinfo
thanks

Hi,

which exact kernel version is that? Which exact compiler version is
that?

At the first glance, that looks like some DKMS bug to me (see the
strange shell warning).

I just tested the module-assistant based build with a locally built
6.6.18 on Stable, works like a charm.

"/usr/share/modass/packages/default.sh" build KVERS=6.6.18 
KSRC=/lib/modules/6.6.18/build KDREV=6.6.18-5 kdist_image
Done with /usr/src/broadcom-sta-modules-6.6.18_6.30.223.271-23+6.6.18-5_all.deb 
.
dpkg -Ei /usr/src/broadcom-sta-modules-6.6.18_6.30.223.271-23+6.6.18-5_all.deb
(Reading database ... 464471 files and directories currently installed.)
Preparing to unpack 
.../broadcom-sta-modules-6.6.18_6.30.223.271-23+6.6.18-5_all.deb ...
Unpacking broadcom-sta-modules-6.6.18 (6.30.223.271-23+6.6.18-5) ...
Setting up broadcom-sta-modules-6.6.18 (6.30.223.271-23+6.6.18-5) ...
apt-mark auto broadcom-sta-modules-6.6.18
broadcom-sta-modules-6.6.18 set to automatically installed.

Please elaborate!

Eduard.

* Andreas Beckmann [Tue, Dec 05 2023, 10:33:27AM]:
> Package: broadcom-sta-dkms
> Version: 6.30.223.271-23
> Severity: important
> Tags: sid trixie
>
> Hi,
>
> broadcom-sta-dkms fails to build a module for Linux 6.6 that was just uploaded
> to experimental:
>
> DKMS make.log for broadcom-sta-6.30.223.271 for kernel 6.6-cloud-amd64 
> (x86_64)
> Tue Dec  5 08:33:20 UTC 2023
> /bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
> /bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
> Wireless Extension is the only possible API for this kernel version
> Using Wireless Extension API
> KBUILD_NOPEDANTIC=1 make -C /lib/modules/6.6-cloud-amd64/build M=`pwd`
> make[1]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> make[1]: Entering directory '/usr/src/linux-headers-6.6-cloud-amd64'
> /bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
> /bin/sh: 1: [: Illegal number: 6.6-cloud-amd64
> Wireless Extension is the only possible API for this kernel version
> Using Wireless Extension API
> Kernel architecture is X86_64
>   CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/shared/linux_osl.o
>   CC [M]  /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.o
> In file included from 
> /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:81:
> /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_iw.h:73: warning: 
> "isprint" redefined
>73 | #define isprint(c) bcm_isprint(c)
>   |
> In file included from 
> /usr/src/linux-headers-6.6-common/include/linux/string_helpers.h:6,
>  from 
> /usr/src/linux-headers-6.6-common/include/linux/seq_file.h:7,
>  from 
> /usr/src/linux-headers-6.6-common/include/linux/seq_file_net.h:5,
>  from 
> /usr/src/linux-headers-6.6-common/include/net/net_namespace.h:195,
>  from 
> /usr/src/linux-headers-6.6-common/include/linux/netdevice.h:38,
>  from 
> /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/include/linuxver.h:69,
>  from 
> /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:27:
> /usr/src/linux-headers-6.6-common/include/linux/ctype.h:30: note: this is the 
> location of the previous definition
>30 | #define isprint(c)  ((__ismask(c)&(_P|_U|_L|_D|_SP)) != 0)
>   |
> /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c: In 
> function 'wl_if_setup':
> /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.c:486:12: 
> error: 'struct net_device' has no member named 'wireless_handlers'
>   486 | dev->wireless_handlers = (struct iw_handler_def *) 
> _iw_handler_def;
>   |^~
> make[3]: *** [/usr/src/linux-headers-6.6-common/scripts/Makefile.build:248: 
> /var/lib/dkms/broadcom-sta/6.30.223.271/build/src/wl/sys/wl_linux.o] Error 1
> make[2]: *** [/usr/src/linux-headers-6.6-common/Makefile:1938: 
> /var/lib/dkms/broadcom-sta/6.30.223.271/build] Error 2
> make[1]: *** [/usr/src/linux-headers-6.6-common/Makefile:246: __sub-make] 
> Error 2
> make[1]: Leaving directory '/usr/src/linux-headers-6.6-cloud-amd64'
> make: *** [Makefile:181: all] Error 2
>
>
> Andreas

--
error compiling committee.c: too many arguments to function

Processed: src:glslang: fails to migrate to testing for too long: unresolved RC bug and autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 14.0.0-2
Bug #1065324 [src:glslang] src:glslang: fails to migrate to testing for too 
long: unresolved RC bug and autopkgtest failure
Marked as fixed in versions glslang/14.0.0-2.
Bug #1065324 [src:glslang] src:glslang: fails to migrate to testing for too 
long: unresolved RC bug and autopkgtest failure
Marked Bug as done

-- 
1065324: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065324: src:glslang: fails to migrate to testing for too long: unresolved RC bug and autopkgtest failure

[Paul Gevers]

Source: glslang
Version: 13.1.1-3
Severity: serious
Control: close -1 14.0.0-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:glslang has been trying to migrate for 32 
days [2]. Hence, I am filing this bug. The version in unstable has an 
unresolved RC bug and its own autopkgtest fail (seems related).


If a package is out of sync between unstable and testing for a longer 
period, this usually means that bugs in the package in testing cannot be 
fixed via unstable. Additionally, blocked packages can have impact on 
other packages, which makes preparing for the release more difficult. 
Finally, it often exposes issues with the package and/or
its (reverse-)dependencies. We expect maintainers to fix issues that 
hamper the migration of their package in a timely manner.


This bug will trigger auto-removal when appropriate. As with all new 
bugs, there will be at least 30 days before the package is auto-removed.


I have immediately closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. I have also tagged this bug to only affect sid and trixie, so 
it doesn't affect (old-)stable.


If you believe your package is unable to migrate to testing due to 
issues beyond your control, don't hesitate to contact the Release Team.


Paul

[1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html
[2] https://qa.debian.org/excuses.php?package=glslang



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065315: marked as done (libcurl4t64 Provides libcurl3-gnutls)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 19:04:43 +
with message-id 
and subject line Bug#1065315: fixed in curl 8.6.0-3.2
has caused the Debian Bug report #1065315,
regarding libcurl4t64 Provides libcurl3-gnutls
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065315: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065315
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libcurl4t64
Version: 8.6.0-3.1
Severity: serious
X-Debbugs-Cc: vor...@debian.org, aure...@debian.org

Yet another case of wrong X-Time64-Compat, found by Aurelien.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libcurl4t64 depends on:
ii  libbrotli11.1.0-2+b3
ii  libc6 2.37-15.1
ii  libgssapi-krb5-2  1.20.1-5+b1
ii  libidn2-0 2.3.7-2
ii  libldap-2.5-0 2.5.13+dfsg-5+b3
ii  libnghttp2-14 1.59.0-1
ii  libpsl5   0.21.2-1+b1
pn  libpsl5t64
ii  librtmp1  2.4+20151223.gitfa8646d.1-2+b2
ii  libssh2-1t64 [libssh2-1]  1.11.0-4.1
ii  libssl3t64 [libssl3]  3.1.5-1.1
ii  libzstd1  1.5.5+dfsg2-2
ii  zlib1g1:1.3.dfsg-3.1

Versions of packages libcurl4t64 recommends:
ii  ca-certificates  20240203

libcurl4t64 suggests no packages.
--- End Message ---
--- Begin Message ---
Source: curl
Source-Version: 8.6.0-3.2
Done: Steve Langasek 

We believe that the bug you reported is fixed in the latest version of
curl, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Steve Langasek  (supplier of updated curl package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 18:43:58 +
Source: curl
Architecture: source
Version: 8.6.0-3.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Curl Maintainers 
Changed-By: Steve Langasek 
Closes: 1065315
Changes:
 curl (8.6.0-3.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Fix wrong X-Time64-Compat for libcurl4t64.  Closes: #1065315.
Checksums-Sha1:
 aff5347750c3d23d8205ba2561e09acc7b4c4d12 3120 curl_8.6.0-3.2.dsc
 0fcaa18b10a4d6950d46956d08a10cb6bcf747b1 48632 curl_8.6.0-3.2.debian.tar.xz
 11afaeb7bbc382d336a6873c04e787ee0795aab4 6736 curl_8.6.0-3.2_source.buildinfo
Checksums-Sha256:
 efe974dc618cabd7827112bc5931a72a239054e3f418e1f8e20c016e57a79956 3120 
curl_8.6.0-3.2.dsc
 768babbae1eda7878ae8e81d351ba7edf2760e239695072ca15b1222e3451a47 48632 
curl_8.6.0-3.2.debian.tar.xz
 7a8652e19c07533eb9690f4281608420d43d456573407be1268943a010007eaa 6736 
curl_8.6.0-3.2_source.buildinfo
Files:
 b74aa665d7e49f5b5407d68badd3ffa3 3120 web optional curl_8.6.0-3.2.dsc
 c02236d05b7e4a566b9fa491e65e1230 48632 web optional 
curl_8.6.0-3.2.debian.tar.xz
 ba07ec2a4e8db0873ddbec0eb2b79521 6736 web optional 
curl_8.6.0-3.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEErEg/aN5yj0PyIC/KVo0w8yGyEz0FAmXjc38SHHZvcmxvbkBk
ZWJpYW4ub3JnAAoJEFaNMPMhshM9ugQP/1oSTPLtT3iNxfOhio/x9lrYjX/BP/fZ
rTBPZcM2HHUdXa+QwWxaWgM1THVSfn1lDimY1Iu7tSS0ITcyCLkax45LmPA3vhp4
VsHGz1eG4VAZNI/5qGhKMqRr6x+F/TS2a4AYX+GKbFSIZ3RUKmsneIhh+p5S8ALP
e05iaBvAg35xtU1BrquXqm929mO2DvwQwh5ghiqpx3mJl8l57Q+4rmuOnlimj6Qn
XYBGFoqIVnp/kVvEI9AmqVXW/iT/5ksbIX9WF/EsJbHXDVhyl0bKry5hmSrLzSJM
0dwOj4r/vE8euazYmB6X9AkG/iRXqEM/x6iesQpWPdwx2qJnHNxpjGplu1N2ecjj
Q9mUiVwpwTc19f6T56noRhHs7Gs6KxNQiM7TLcLM/sJ/ZR7hg648ZTOLxa/Tbvj0
yJNYgGeEO3QyaQVErez6QjZCMeg5OTUHzcUkjwVFC9sZAom517EpJPa5nTBZzwVG
+UwpjcrlMdL5XFzol0pfmkH7PKSefzIGft9OIiXxFlGAmCiWkoj7+ZmfCa5xC8sf

Bug#1065323: petsc: bad Provides in libpetsc64-real3.19t64, libpetsc64-complex3.19t64 and libpetsc-real3.19t64

[Daniel Serpell]

Source: petsc
Version: 3.19.6+dfsg1-2.1
Severity: serious
Justification: bad provides

The mentioned packages: libpetsc64-real3.19t64, libpetsc64-complex3.19t64
and libpetsc-real3.19t64 have invalid Provides, affecting the transition.

Regards,
Daniel.

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

Kernel: Linux 6.6.15-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=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Bug#1061992: Bug#1065315: libcurl4t64 Provides libcurl3-gnutls

[Steve Langasek]

I'm sorry, I have not been able to isolate the bug in the NMU scripting that
caused this.  I am uploading a fixed NMU, please find the complete NMU
debdiff attached.

On Sat, Mar 02, 2024 at 08:32:02PM +0500, Andrey Rahmatullin wrote:
> Package: libcurl4t64
> Version: 8.6.0-3.1
> Severity: serious
> X-Debbugs-Cc: vor...@debian.org, aure...@debian.org
> 
> Yet another case of wrong X-Time64-Compat, found by Aurelien.
> 
> 
> -- System Information:
> Debian Release: trixie/sid
>   APT prefers unstable-debug
>   APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
> 'unstable'), (500, 'testing'), (101, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 6.7-amd64 (SMP w/4 CPU threads; PREEMPT)
> Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
> TAINT_UNSIGNED_MODULE
> Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libcurl4t64 depends on:
> ii  libbrotli11.1.0-2+b3
> ii  libc6 2.37-15.1
> ii  libgssapi-krb5-2  1.20.1-5+b1
> ii  libidn2-0 2.3.7-2
> ii  libldap-2.5-0 2.5.13+dfsg-5+b3
> ii  libnghttp2-14 1.59.0-1
> ii  libpsl5   0.21.2-1+b1
> pn  libpsl5t64
> ii  librtmp1  2.4+20151223.gitfa8646d.1-2+b2
> ii  libssh2-1t64 [libssh2-1]  1.11.0-4.1
> ii  libssl3t64 [libssl3]  3.1.5-1.1
> ii  libzstd1  1.5.5+dfsg2-2
> ii  zlib1g1:1.3.dfsg-3.1
> 
> Versions of packages libcurl4t64 recommends:
> ii  ca-certificates  20240203
> 
> libcurl4t64 suggests no packages.
> 

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org
diff -Nru curl-8.6.0/debian/changelog curl-8.6.0/debian/changelog
--- curl-8.6.0/debian/changelog 2024-02-19 22:16:17.0 +
+++ curl-8.6.0/debian/changelog 2024-03-02 18:43:58.0 +
@@ -1,3 +1,17 @@
+curl (8.6.0-3.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix wrong X-Time64-Compat for libcurl4t64.  Closes: #1065315.
+
+ -- Steve Langasek   Sat, 02 Mar 2024 18:43:58 +
+
+curl (8.6.0-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.  Closes: #1061992
+
+ -- Steve Langasek   Sat, 02 Mar 2024 07:11:53 +
+
 curl (8.6.0-3) unstable; urgency=medium
 
   * d/p/vtls_revert_receive_max_buffer_add_test_case.patch: New patch to fix
diff -Nru curl-8.6.0/debian/control curl-8.6.0/debian/control
--- curl-8.6.0/debian/control   2024-02-19 22:16:17.0 +
+++ curl-8.6.0/debian/control   2024-03-02 18:43:46.0 +
@@ -5,7 +5,7 @@
 Uploaders: Carlos Henrique Lima Melara ,
Samuel Henrique ,
Sergio Durigan Junior 
-Build-Depends:
+Build-Depends: dpkg-dev (>= 1.22.5),
  debhelper-compat (= 13),
  autoconf,
  automake,
@@ -42,7 +42,7 @@
 
 Package: curl
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, libcurl4 (= ${binary:Version})
+Depends: ${shlibs:Depends}, ${misc:Depends}, libcurl4t64 (= ${binary:Version})
 Multi-Arch: foreign
 Description: command line tool for transferring data with URL syntax
  curl is a command line tool for transferring data with URL syntax, supporting
@@ -54,14 +54,17 @@
  NTLM, Negotiate, kerberos...), file transfer resume, proxy tunneling and a
  busload of other useful tricks.
 
-Package: libcurl4
+Package: libcurl4t64
+Provides: ${t64:Provides}
+X-Time64-Compat: libcurl4
+Breaks: libcurl4 (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Recommends: ca-certificates
 Pre-Depends: ${misc:Pre-Depends}
 Conflicts: libcurl3
-Replaces: libcurl3
+Replaces: libcurl4, libcurl3
 Multi-Arch: same
 Description: easy-to-use client-side URL transfer library (OpenSSL flavour)
  libcurl is an easy-to-use client-side URL transfer library, supporting DICT,
@@ -79,7 +82,11 @@
  .
  SSL support is provided by OpenSSL.
 
-Package: libcurl3-gnutls
+Package: libcurl3t64-gnutls
+Provides: ${t64:Provides}
+X-Time64-Compat: libcurl3-gnutls
+Replaces: libcurl3-gnutls
+Breaks: libcurl3-gnutls (<< ${source:Version})
 Architecture: any
 Section: libs
 Depends: ${shlibs:Depends}, ${misc:Depends}
@@ -111,7 +118,7 @@
  libcurl4-dev,
  libcurl3-dev
 Conflicts: libcurl4-gnutls-dev, libssl1.0-dev
-Depends: ${misc:Depends}, libcurl4 (= ${binary:Version})
+Depends: ${misc:Depends}, libcurl4t64 (= ${binary:Version})
 Suggests: libcurl4-doc,
  libidn-dev,
  libkrb5-dev,
@@ -149,7 +156,7 @@
  libcurl3-gnutls-dev,
  libcurl4-dev
 Conflicts: libcurl4-openssl-dev

Bug#1065321: marked as done (lasso: unfullfillable Build-Depends (unneeded explicit Build-Depends on libxmlsec1-openssl))

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 18:19:32 +
with message-id 
and subject line Bug#1065321: fixed in lasso 2.8.2-2
has caused the Debian Bug report #1065321,
regarding lasso: unfullfillable Build-Depends (unneeded explicit Build-Depends 
on libxmlsec1-openssl)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Source: lasso
Severity: serious
Version: 2.8.2-1
Tags: patch
User: debian-...@lists.debian.org
Usertags: time-t

Hi,

I just saw lasso has

libxmlsec1-dev,
libxmlsec1-openssl,

in Build-Depends. What for? If this was versioned this could be 
understandable, but it isn't.


And given libxmlsec1-dev pulls in all the variants since

xmlsec1 (1.2.9-2) unstable; urgency=low

  * Add engine libraries to depends of dev package
  * Switch to mozilla libs provided by xulrunner package (Closes: #364382)
  * Confirm Debian standards 3.7.2

 -- John V. Belmonte   Thu, 08 Jun 2006 21:52:55 
-0400


- so for anything relevant - this is not needed.

So as  this library is now libxmlsec1t64-openssl this Build-Depends: is 
now unfullfillable.


Patch is trivial: remove that line :)

Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: lasso
Source-Version: 2.8.2-2
Done: Frederic Peters 

We believe that the bug you reported is fixed in the latest version of
lasso, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Frederic Peters  (supplier of updated lasso package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Mar 2024 18:58:24 +0100
Source: lasso
Architecture: source
Version: 2.8.2-2
Distribution: unstable
Urgency: medium
Maintainer: Frederic Peters 
Changed-By: Frederic Peters 
Closes: 1065321
Changes:
 lasso (2.8.2-2) unstable; urgency=medium
 .
   * Acknowledge NMU.
   * d/control: remove explicit libxmlsec1-openssl from build-depends.
 (closes: #1065321)
Checksums-Sha1:
 b2e1f0b3bd068094ac14895e3f2928ba05af18cd 2147 lasso_2.8.2-2.dsc
 b4ab0e99133a97f93361ca69062e26e7a303f8c3 12780 lasso_2.8.2-2.debian.tar.xz
 a524e752e542f553b085ac5fcf1ff3a6d6860633 9230 lasso_2.8.2-2_source.buildinfo
Checksums-Sha256:
 05d530777301f72c8ee6bc97e8ed6e5d5d0361fc383edfebe85c55adb4567aa3 2147 
lasso_2.8.2-2.dsc
 2158c86d90d333d105ab00c4167b0e6c1f467a1303befe345be816c5d1e3ae83 12780 
lasso_2.8.2-2.debian.tar.xz
 684a0aac0c0ca04eca8db7e92f0ca0b60db36e4d06b751e03750b6862db6671a 9230 
lasso_2.8.2-2_source.buildinfo
Files:
 dacf9f99569543cc3edccc9def41365f 2147 libs optional lasso_2.8.2-2.dsc
 606de5aeb510270010a8834c515e33c9 12780 libs optional 
lasso_2.8.2-2.debian.tar.xz
 58a7c304d9c820af6d46555a668484de 9230 libs optional 
lasso_2.8.2-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEcUkUffL0auA9VW47KukB5ccCGNIFAmXja1EACgkQKukB5ccC
GNLLyw//dIAdhgKkwW6orBDLwNXrZdGYggL8kVjN34p7yoKl2YEOCeXKcOD+4AFD
lu/axcQRWdZ+U8IDbCTLH8Jn/kt/wm6dSEDJrb0rttTg41VlWtSDstLtSUNKe+ao
Es0nIynBkqlUlIz9uzuW6ISXwtJbW8uTCVR6mp6qvpiLS2g56zTmkWmnY6B17sN4
pVEA1uZe6oPSx544R6gvJq0doAFCOlGZSrmtPIesZG2BDJU3IhENRcj02i92CwrC
7yAauVtGgvp2hKCLHfAwDT2jpvcWYyCLS3eXj4X9D/4U/jssQhZ1v+TIdeU0UAdb
VH4wdEBHLpTssdZRkvhPomsqqMIcHloK95qaKXzdfBvMjukcukysi/hfiefvG2NI
8n7WEqdXLf9T/9oLv2uYl6k6ruYJYh0pvNEtL4Kr/xGMzb0ttEfMP8Igin+yBbsS
Dp1mcd4FCyiQXXHtEAmQETicko23HRP8AwTQSGhP8Fa6wDzX+0BUl8hMm+xTPgoL
KnInbq3sGhwmjVZLyD16udOIjc8dLdtTynJJRipIMCKvCumL5FmjagaYKNAdPzF5
2BgfRH7JGji+S1EGDtUHosh1ujMHNjTGFIpZGeksSiYPcYm0t2LcdhKsJwRlnzt6
QPYtKVQxTYm09qoQc5SmQXFrmADGdayw66ZBy7HYlLNgs4xXsh0=
=rEsI
-END PGP SIGNATURE-



pgpEaGcRAjB3W.pgp
Description: PGP signature
--- End Message ---

Bug#1062757: [Debian-med-packaging] Bug#1062757: odil: NMU diff for 64-bit time_t transition

[Étienne Mollier]

Benjamin Drung, on 2024-02-29:
> Please find attached a final version of this patch for the time_t
> transition.  This patch is being uploaded to unstable.

NMU acknowledged, thanks!  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

Bug#1065321: lasso: unfullfillable Build-Depends (unneeded explicit Build-Depends on libxmlsec1-openssl)

[Rene Engelhard]

Hi,

Am 02.03.24 um 18:42 schrieb Rene Engelhard:
So as  this library is now libxmlsec1t64-openssl this Build-Depends: is 
now unfullfillable.


At least for 32bit archs like armel/armhf (which don't have Provides: 
libxmlsec1-openssl) or a future package-named package due to ABI changes 
(like when we ever updated to 1.3.x)


Regards,

Rene

Processed: be less strict about the found version

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # while this is arguably in bug already in 2.8.2-1
> # this is only serious in sid with the t64 renames
> # (and for experimental when we ever upgraded to xmlsec1
> # 1.3.3 since that will change ABI and thus the package name, too
> found 1065321 2.8.2-1.1
Bug #1065321 [src:lasso] lasso: unfullfillable Build-Depends (unneeded explicit 
Build-Depends on libxmlsec1-openssl)
Marked as found in versions lasso/2.8.2-1.1.
> notfound 1065321 2.8.2-1
Bug #1065321 [src:lasso] lasso: unfullfillable Build-Depends (unneeded explicit 
Build-Depends on libxmlsec1-openssl)
No longer marked as found in versions lasso/2.8.2-1.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
1065321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: severity of 1065310 is serious

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # necessary to be useful after t64 transition
> severity 1065310 serious
Bug #1065310 [deborphan] deborphan should take "Provides:" into account
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1062525: [Debian-med-packaging] Bug#1062525: eegdev: NMU diff for 64-bit time_t transition

[Étienne Mollier]

mwhud...@fastmail.fm, on 2024-02-28:
> Please find attached a final version of this patch for the time_t
> transition.  This patch is being uploaded to unstable.

Thanks Michael, your NMU is inlined in Salsa.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

Bug#1065321: lasso: unfullfillable Build-Depends (unneeded explicit Build-Depends on libxmlsec1-openssl)

[Rene Engelhard]

Source: lasso
Severity: serious
Version: 2.8.2-1
Tags: patch
User: debian-...@lists.debian.org
Usertags: time-t

Hi,

I just saw lasso has

libxmlsec1-dev,
libxmlsec1-openssl,

in Build-Depends. What for? If this was versioned this could be 
understandable, but it isn't.


And given libxmlsec1-dev pulls in all the variants since

xmlsec1 (1.2.9-2) unstable; urgency=low

  * Add engine libraries to depends of dev package
  * Switch to mozilla libs provided by xulrunner package (Closes: #364382)
  * Confirm Debian standards 3.7.2

 -- John V. Belmonte   Thu, 08 Jun 2006 21:52:55 
-0400


- so for anything relevant - this is not needed.

So as  this library is now libxmlsec1t64-openssl this Build-Depends: is 
now unfullfillable.


Patch is trivial: remove that line :)

Regards,

Rene

Bug#1065320: linux-image-6.1.0-18-amd64: 6.1.0-18 kernel enters ACPI Error loop during boot & requires power cycle

[Lee Elliott]

Package: src:linux
Version: 6.1.76-1
Severity: critical
Justification: breaks the whole system
X-Debbugs-Cc: leeejobsacco...@mail.co.uk

Dear Maintainer,

   * What led up to the situation?

   Trying to boot the system with the 6.1.0-18 kernel

   * What exactly did you do (or not do) that was effective (or
 ineffective)?

   I tried adding 'boot_delay=1000' boot option to slow the console
   scroll rate, to enable better recording of the error messages.

   I tried rebooting the previous 6.1.0-17 kernel.

   * What was the outcome of this action?

   After adding the 'boot_delay=1000' option the boot process
   progressed no further than "Loading initial ramdisk ..."
   (left for several minutes - required power cycle).

   The system boots sucessfully on the previous 6.1.0-17 kernel

   * What outcome did you expect instead?

   I expected the system to successfully boot.

   * Additional observations

   This system also normally includes 'hpet=disable' and
   'acpi_enforce_resources=lax' boot options but removing these
   made no difference.

   Although I was not able to boot the system with the
   'boot_delay=1000' option and obtain clear photographs of the
   console output - the ones I've attached suffer from
   'overprinting' - it does seem clear that ACPI errors are
   being reported.

   There appear to be two distinct phases to this problem.
   Initially, ACPI seems to be reporting errors for "GPE", as
   shown in the first attached photograph, but after ~10 seconds
   or so, ACPI then switches to continuously reporting an error
   for PM_TIMER, as shown in the second attached photograph. At
   this point a power cycle is required.

   Purging and reinstalling the package made no difference. Atm,
   only three kernels are installed on this system but I have
   had more in the past as I normally compile my own kernels
   from the corresponding Debian source package. My own 6.1.76-1
   kernel also suffers from the same problem, whereas my own
   6.1.69-1 kernel boots and runs Ok.

   Comparing the kernel configs for 6.1.0-17 and 6.1.0-18
   showed just one functional change - an additional
   Compile-time checks and compiler option, which did not seem
   relevant to this problem.


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: ASUSTeK COMPUTER INC.
product_name: E203NA
product_version: 1.0   
chassis_vendor: ASUSTeK COMPUTER INC.
chassis_version: 1.0   
bios_vendor: American Megatrends Inc.
bios_version: E203NA.312
board_vendor: ASUSTeK COMPUTER INC.
board_name: E203NA
board_version: 1.0   

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback


** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Celeron N3350/Pentium N4200/Atom 
E3900 Series Host Bridge [8086:5af0] (rev 0b)
Subsystem: ASUSTeK Computer Inc. Celeron N3350/Pentium N4200/Atom E3900 
Series Host Bridge [1043:1980]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device_pci_legacy

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 500 
[8086:5a85] (rev 0b) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. HD Graphics 500 [1043:1980]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+ FLReset+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- FLReset-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis- 
NROPrPrP- LTR-
 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- 
EETLPPrefix-
 EmergencyPowerReduction Not Supported, 
EmergencyPowerReductionInit-
 FRS-
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR- 
10BitTagReq- OBFF Disabled,
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 

Bug#1062316: libgkarrays: NMU diff for 64-bit time_t transition

[Étienne Mollier]

Benjamin Drung, on 2024-02-29:
> On Wed, 28 Feb 2024 20:12:53 +0100 =?utf-8?Q?=C3=89tienne?= Mollier
>  wrote:
> > Benjamin Drung, on 2024-02-28:
> > > Please find attached a final version of this patch for the time_t
> > > transition.  This patch is being uploaded to unstable.
> > 
> > NMU acknowledged, thank you!  :)
> 
> The upload was rejected, because the the version number 2.1.0+dfsg-4.1
> was used for the experimental upload. So I had to bump the version
> number to 2.1.0+dfsg-4.2.

Thanks for the notice, I updated the VCS tree accordingly.

Have a nice day,  :)
-- 
  .''`.  Étienne Mollier 
 : :' :  pgp: 8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
 `. `'   sent from /dev/pts/1, please excuse my verbosity
   `-


signature.asc
Description: PGP signature

Bug#1065318: marked as done (mplayer: Package is not installable due to dependency on libsmbclient)

[Debian Bug Tracking System]

Your message dated Sat, 2 Mar 2024 17:45:08 +0100
with message-id 
and subject line Re: Bug#1065318: mplayer: Package is not installable due to 
dependency on libsmbclient
has caused the Debian Bug report #1065318,
regarding mplayer: Package is not installable due to dependency on libsmbclient
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mplayer
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: benjamin.poir...@gmail.com

Dear Maintainer,

The mplayer package is currently not installable in Sid:

root@vsid:/tmp# apt install mplayer
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libsmbclient : Depends: samba-libs (= 2:4.19.5+dfsg-1) but 2:4.19.5+dfsg-3 is 
to be installed
 libsmbclient0 : Breaks: libsmbclient (< 2:4.19.5+dfsg-3) but 2:4.19.5+dfsg-1 
is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


I guess this problem is related to this change noted in the samba
changelog:

samba (2:4.19.5+dfsg-2) unstable; urgency=medium

  * rename libsmbclient => libsmbclient0 for 64-bit time_t transition
Closes: #1064337


I rebuilt the mplayer package from source (version 1.5+svn38446) without
any change. The resulting .deb had a dependency on libsmbclient0 (>=
2:4.0.3+dfsg1) and I was able to install it without further effort.

Thank you

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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

Versions of packages mplayer depends on:
ii  liba52-0.7.4  0.7.4-20+b1
ii  libaa11.4p5-51
ii  libasound2t64 [libasound2]1.2.11-1
ii  libass9   1:0.17.1-2
ii  libaudio2 1.9.4-7+b1
ii  libavcodec60  7:6.1.1-2
ii  libavformat60 7:6.1.1-2
ii  libavutil58   7:6.1.1-2
ii  libbluray21:1.3.4-1
ii  libbs2b0  3.1.0+dfsg-7
ii  libc6 2.37-15.1
ii  libcaca0  0.99.beta20-4
ii  libcdio-cdda2 10.2+2.0.1-1
ii  libcdio-paranoia2 10.2+2.0.1-1
ii  libcdio19 2.1.0-4
ii  libdca0   0.0.7-2
ii  libdv41.0.0-17
ii  libdvdnav46.1.1-1
ii  libdvdread8   6.1.3-1
ii  libegl1   1.7.0-1
pn  libenca0  
ii  libfaad2  2.11.1-1+b1
ii  libfontconfig12.15.0-1
ii  libfreetype6  2.13.2+dfsg-1+b1
ii  libfribidi0   1.0.13-3+b1
ii  libgif7   5.2.2-1
ii  libgl11.7.0-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3+b1
ii  libjpeg62-turbo   1:2.1.5-2+b2
ii  liblirc-client0t64 [liblirc-client0]  0.10.2-0.7
ii  libmad0   0.15.1b-10.1+b1
ii  libmng1   1.0.10+dfsg-3.1+b5
ii  libmpeg2-40.5.1-9+b1
ii  libmpg123-0   1.32.5-1
ii  libogg0   1.3.5-3
ii  libopenal11:1.23.1-4+b1
ii  libpng16-16t64 [libpng16-16]  1.6.43-3
ii  libpostproc57 7:6.1.1-2
ii  libpulse0 16.1+dfsg1-3
pn  libsdl1.2debian   
pn  libsmbclient  
ii  libsndio7.0   1.9.0-0.3+b3
ii  libspeex1

Bug#1064950: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in debian/control breaks binNMU builds.

[Sebastian Ramacher]

On 2024-02-28 07:16:07 +, Warlich, Christof wrote:
> Subject: apache2: (Legacy?) "Depends: apache2-data (= ${source:Version})," in 
> debian/control breaks binNMU builds.
> Source: apache2
> X-Debbugs-Cc: christof.warl...@siemens.com
> Version: 2.4.57-2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> Tags: patch ftbfs
> 
> Dear Maintainer,
> 
> (re)building apache2 as binNMU (i.e. with appending "+b to the 
> package version")
> works, but installation of the resulting apache2 package fails due to the 
> following dependency
> in debian/control:
> 
> Depends: apache2-data (= ${source:Version}),
> 
> It causes apt-get to look for the dependency "apache2-data" (= 2.4.57-2) 
> which does not exist
> in the newly built packages. Instead, the dependency should be satisfied by
> "apache2-data (= 2.4.57-2+b)".
> 
> The folliwing patch fixes the issue:
> 
> diff --git a/debian/control b/debian/control
> index 2eddc60..31121fa 100644
> --- a/debian/control
> +++ b/debian/control
> @@ -34,7 +34,7 @@ Rules-Requires-Root: binary-targets
>  Package: apache2
>  Architecture: any
>  Depends: apache2-bin (= ${binary:Version}),
> - apache2-data (= ${source:Version}),
> + apache2-data (= ${binary:Version}),
>   apache2-utils (= ${binary:Version}),
>   lsb-base,
>   media-types,
> 
> Please consider applying the patch.

This is wrong. apache2-data is an Architecture: all package, but apache2
is Architecture: any. So using ${source:Version} here is correct. Note
that Debian does not currently support binNMUs for Architecture: all
packages, so apache2-data will never have a +bX version.

Cheers

> 
> Best regards,
> 
> Christof Warlich
> 
> P.S.: Note that the information below, being produced by "reportbug", is 
> irrelevant as I executed "reportbug"
> on WSL2 on Windows 10. The actual Debian version is "bookworm".
> 
> -- System Information:
> Debian Release: bookworm/sid
>   APT prefers jammy-updates
>   APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 
> 'jammy'), (100, 'jammy-backports')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 5.10.102.1-microsoft-standard-WSL2+ (SMP w/16 CPU threads)
> 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)

-- 
Sebastian Ramacher

Bug#1065275: mariadb: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Otto Kekäläinen]

Currently MariaDB is not building[1] at all due to:

**
mariadb build-depends on:
- libcurl4-openssl-dev:amd64
libcurl4-openssl-dev depends on:
- libcurl4t64:amd64 (= 8.6.0-3.1)
mariadb build-depends on:
- cmake:amd64
cmake depends on:
- libcurl4:amd64 (>= 7.16.2)
libcurl4t64 conflicts with:
- libcurl4:amd64 (< 8.6.0-3.1)
**

I can also see piuparts failing on broken libpam0t64[2] and a bunch of
other tests failing various installability problems but seems they
started before this upload, so they seem to happen only because many
other packages right now during the transition have issues.

Anyway I have the change[3] done in version control and I am ready to
upload once I get some confirmation that this is now final.

[1] https://buildd.debian.org/status/package.php?p=mariadb
[2] https://salsa.debian.org/mariadb-team/mariadb-server/-/jobs/5393728
[3] 
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/d2a0784f1e01b6613fefda17199a4e9867a126c3

Bug#1065318: mplayer: Package is not installable due to dependency on libsmbclient

[Benjamin Poirier]

Package: mplayer
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: benjamin.poir...@gmail.com

Dear Maintainer,

The mplayer package is currently not installable in Sid:

root@vsid:/tmp# apt install mplayer
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libsmbclient : Depends: samba-libs (= 2:4.19.5+dfsg-1) but 2:4.19.5+dfsg-3 is 
to be installed
 libsmbclient0 : Breaks: libsmbclient (< 2:4.19.5+dfsg-3) but 2:4.19.5+dfsg-1 
is to be installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by 
held packages.


I guess this problem is related to this change noted in the samba
changelog:

samba (2:4.19.5+dfsg-2) unstable; urgency=medium

  * rename libsmbclient => libsmbclient0 for 64-bit time_t transition
Closes: #1064337


I rebuilt the mplayer package from source (version 1.5+svn38446) without
any change. The resulting .deb had a dependency on libsmbclient0 (>=
2:4.0.3+dfsg1) and I was able to install it without further effort.

Thank you

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
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

Versions of packages mplayer depends on:
ii  liba52-0.7.4  0.7.4-20+b1
ii  libaa11.4p5-51
ii  libasound2t64 [libasound2]1.2.11-1
ii  libass9   1:0.17.1-2
ii  libaudio2 1.9.4-7+b1
ii  libavcodec60  7:6.1.1-2
ii  libavformat60 7:6.1.1-2
ii  libavutil58   7:6.1.1-2
ii  libbluray21:1.3.4-1
ii  libbs2b0  3.1.0+dfsg-7
ii  libc6 2.37-15.1
ii  libcaca0  0.99.beta20-4
ii  libcdio-cdda2 10.2+2.0.1-1
ii  libcdio-paranoia2 10.2+2.0.1-1
ii  libcdio19 2.1.0-4
ii  libdca0   0.0.7-2
ii  libdv41.0.0-17
ii  libdvdnav46.1.1-1
ii  libdvdread8   6.1.3-1
ii  libegl1   1.7.0-1
pn  libenca0  
ii  libfaad2  2.11.1-1+b1
ii  libfontconfig12.15.0-1
ii  libfreetype6  2.13.2+dfsg-1+b1
ii  libfribidi0   1.0.13-3+b1
ii  libgif7   5.2.2-1
ii  libgl11.7.0-1
ii  libjack-jackd2-0 [libjack-0.125]  1.9.21~dfsg-3+b1
ii  libjpeg62-turbo   1:2.1.5-2+b2
ii  liblirc-client0t64 [liblirc-client0]  0.10.2-0.7
ii  libmad0   0.15.1b-10.1+b1
ii  libmng1   1.0.10+dfsg-3.1+b5
ii  libmpeg2-40.5.1-9+b1
ii  libmpg123-0   1.32.5-1
ii  libogg0   1.3.5-3
ii  libopenal11:1.23.1-4+b1
ii  libpng16-16t64 [libpng16-16]  1.6.43-3
ii  libpostproc57 7:6.1.1-2
ii  libpulse0 16.1+dfsg1-3
pn  libsdl1.2debian   
pn  libsmbclient  
ii  libsndio7.0   1.9.0-0.3+b3
ii  libspeex1 1.2.1-2+b1
ii  libswresample47:6.1.1-2
ii  libswscale7   7:6.1.1-2
ii  libtheora01.1.1+dfsg.1-16.1+b1
ii  libtinfo6 6.4+20240113-1
ii  libvdpau1 1.5-2
pn  libvorbisidec1
ii  libx11-6  2:1.8.7-1
ii  libxext6  2:1.3.4-1+b1
ii  libxinerama1  2:1.1.4-3
ii  libxss1   1:1.2.3-1
ii  libxv12:1.0.11-1.1
ii  libxvidcore4  2:1.3.7-1+b1
ii  libxvmc1  2:1.0.12-2
ii  libxxf86dga1  2:1.1.5-1
ii  libxxf86vm1   1:1.1.4-1+b2
ii  zlib1g1:1.3.dfsg-3.1

mplayer recommends 

Bug#1065275: marked as pending in mariadb

[Otto Kekäläinen]

Control: tag -1 pending

Hello,

Bug #1065275 in mariadb reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/d2a0784f1e01b6613fefda17199a4e9867a126c3


Add 'dpkg-dev (>= 1.22.5)' to Build-Depends (Closes: #1065275)

Extend 81945443 for time_t transition by adding missing dependency to
ensure the package is built with correct ABI.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065275

Processed: Bug#1065275 marked as pending in mariadb

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065275 [src:mariadb] mariadb: missing dpkg-dev (>= 1.22.5) build 
dependency for time_t transition
Added tag(s) pending.

-- 
1065275: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1062841: Bug#1065275: mariadb: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Otto Kekäläinen]

Hi Sabastian!

> * The package is built with the wrong ABI.
> * The package migrates to testing before the change is enabled in
>   testing and builds there would be produced against the wrong ABI.
>
> Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
> version ASAP.

Thanks for following up with builds and transitions. I can do an
upload quickly but would like to avoid having to do a third one, so:

Could you Sebastian perhaps quickly skim through the commit that
implemented this
https://salsa.debian.org/mariadb-team/mariadb-server/-/commit/8194544349982990fb2585c2a8c15c4db3904735
and say if there might be something else missing as well?

Additional background info:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062841
- https://salsa.debian.org/mariadb-team/mariadb-server/-/merge_requests/68

Processed: tagging 1064737

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1064737 + pending
Bug #1064737 [src:python3-defaults] python3-defaults: FTBFS: make: *** 
[debian/rules:64: stamp-doc-policy] Error 1
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1064737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1065129

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1065129 + pending
Bug #1065129 [src:python3.11] python3.11: recent libc6-dev change causes NIS 
support to be dropped
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065129
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: tagging 1065128

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1065128 + pending
Bug #1065128 [src:python3.12] python3.12: recent libc6-dev change causes NIS 
support to be dropped
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065128: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065128
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065315: libcurl4t64 Provides libcurl3-gnutls

[Andrey Rahmatullin]

Package: libcurl4t64
Version: 8.6.0-3.1
Severity: serious
X-Debbugs-Cc: vor...@debian.org, aure...@debian.org

Yet another case of wrong X-Time64-Compat, found by Aurelien.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 
'unstable'), (500, 'testing'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.7-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.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 libcurl4t64 depends on:
ii  libbrotli11.1.0-2+b3
ii  libc6 2.37-15.1
ii  libgssapi-krb5-2  1.20.1-5+b1
ii  libidn2-0 2.3.7-2
ii  libldap-2.5-0 2.5.13+dfsg-5+b3
ii  libnghttp2-14 1.59.0-1
ii  libpsl5   0.21.2-1+b1
pn  libpsl5t64
ii  librtmp1  2.4+20151223.gitfa8646d.1-2+b2
ii  libssh2-1t64 [libssh2-1]  1.11.0-4.1
ii  libssl3t64 [libssl3]  3.1.5-1.1
ii  libzstd1  1.5.5+dfsg2-2
ii  zlib1g1:1.3.dfsg-3.1

Versions of packages libcurl4t64 recommends:
ii  ca-certificates  20240203

libcurl4t64 suggests no packages.

Bug#1065296: marked as done (qgis: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 15:24:48 +
with message-id 
and subject line Bug#1065296: fixed in qgis 3.34.4+dfsg-3
has caused the Debian Bug report #1065296,
regarding qgis: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065296
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qgis
Version: 3.34.4+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: qgis
Source-Version: 3.34.4+dfsg-3
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
qgis, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated qgis package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 14:31:35 +0100
Source: qgis
Architecture: source
Version: 3.34.4+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065296
Changes:
 qgis (3.34.4+dfsg-3) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065296)
Checksums-Sha1:
 516a2e4d6b13a08c988cef5881404f635b6c4f9e 5501 qgis_3.34.4+dfsg-3.dsc
 f4cb5fc8ea39e3950fcb7b57be97b28c3b5014e9 528836 
qgis_3.34.4+dfsg-3.debian.tar.xz
 3e1487ed403c32b9f20926156aceabbcd4c01ae8 43083 
qgis_3.34.4+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 4b19f12e258acaa12a2d5ba647cbeb4f760cc3017fc5299eeabe7c4a3243c06c 5501 
qgis_3.34.4+dfsg-3.dsc
 c5406b89f3816ca2c5085dc1fdbc8538814eff0af673fb89748aa27d5a626012 528836 
qgis_3.34.4+dfsg-3.debian.tar.xz
 9af829863bf77f442e306b083131c444e96f4a8c43236373de7e5b813bccd709 43083 
qgis_3.34.4+dfsg-3_amd64.buildinfo
Files:
 81dec2f67dee4fc786f3c381540c5251 5501 science optional qgis_3.34.4+dfsg-3.dsc
 20d35b941669a835104287fca0a1a90e 528836 science optional 
qgis_3.34.4+dfsg-3.debian.tar.xz
 44b3b71b2bf341c462526c0e515a1320 43083 science optional 
qgis_3.34.4+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIyBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjP48ACgkQZ1DxCuiN
SvE8bg/40p8aG+aKAUvniJ5RbAXyuHGIhh9qiXNfyphwtvdzH+eBQeLM3du/DiDz
XaHCx5zuI0cyCsz+aWsK/okjqY8BPEkGQu/nSGw66C6sOc9y4Rg/NU08znvoVr5F
I7WNVPpZ/cL0rcA+k/moYnmuzPEKQwd4N8/Fc+Hb3QcrLNAjKA9vS0SfoV7vJTpF
5+eKZO6o+ODOooVtYtbZn2yQAs6AudvTpE5kw+633Wjd2+kAydwbTfycjJCXf1AF
PExQDSiVRjJ+VLbv86Ih/aysDdlBfSV4NLGWJNYuKDxOQziR41PJ/GRYCdz76bt6
uYLCwf5qQGPdfxji51M+itPpHz+YOBmq1avtO1oAS7zRGMY4+qHRNgdE6xCuDYxx
O8bx/LPo/XXlR36YVnmI/E4WRXHK+jwWX+/SXAXVOpPxOjwxUX/13Jn3+wF9D2d8
3gY2SNE74wlNfXy5tmIjzw4troA7aR9lzP6K4An2uWGGr0kBDqrP+ic1GzgWSMpK
bK/GU6o1eTr/7JwdRw8NExB+mbDRItmZznrXBXKxHD3vS01m/0I+Uh/M9/crz5nb
Bs8Fj5wQuXzRAuSuOc2Xsy4WdTcPtTBKAHlRs2zDU43DmzAdhcNYBWMJXbu+IHRp
I6d83kYoKVIZ+RmO4nI9iHI0XuByYW+Cu+J3vQD7hCmkGZiopA==
=1Drx
-END PGP SIGNATURE-



pgpYWaUVM_sln.pgp
Description: PGP signature
--- End Message ---

Bug#1065280: marked as done (glib2.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 2 Mar 2024 14:46:18 +
with message-id 
and subject line Re: Bug#1065280: glib2.0: missing dpkg-dev (>= 1.22.5) build 
dependency for time_t transition
has caused the Debian Bug report #1065280,
regarding glib2.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glib2.0
Version: 2.78.4-2.1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 2.79.3-1

On Sat, 02 Mar 2024 at 11:23:35 +, Simon McVittie wrote:
> This is already fixed in git, but we were told not to upload that version
> yet, to avoid interfering with the migration of the NMU currently
> in unstable (which, at the time, was believed to be sufficient and
> desirable). It is also already fixed in experimental (2.79.3-1).

Closing as fixed in experimental. For avoidance of doubt, I am aware
that this leaves the version in unstable with unfixed RC bugs, which I
will resolve as soon as I can, assuming a better developer does not get
there first.

smcv--- End Message ---

Bug#1065299: marked as done (virtualpk: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 14:01:01 +
with message-id 
and subject line Bug#1065299: fixed in virtualpg 2.0.1-4
has caused the Debian Bug report #1065299,
regarding virtualpk: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065299
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: virtualpg
Version: 2.0.1-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: virtualpg
Source-Version: 2.0.1-4
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
virtualpg, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated virtualpg package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 14:22:34 +0100
Source: virtualpg
Architecture: source
Version: 2.0.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065299
Changes:
 virtualpg (2.0.1-4) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065299)
Checksums-Sha1:
 3fe6d8b69702f3e7388af83e2b8e1f4096777804 2143 virtualpg_2.0.1-4.dsc
 3c41f54b0d69c29a4da03f82910213ba503ec3db 11476 virtualpg_2.0.1-4.debian.tar.xz
 a6e9545310577674460652bf3a8b451e0efedebf 9262 virtualpg_2.0.1-4_amd64.buildinfo
Checksums-Sha256:
 388baf333c99821d5b52f521a3d1f06c2b47363cb0b427bdf208a50ab7c1ce51 2143 
virtualpg_2.0.1-4.dsc
 297a91e96d2021ed1e1751ccdacf87f09265d94179eddfd15aad29f1197b2d9f 11476 
virtualpg_2.0.1-4.debian.tar.xz
 f501df7d47d34fce367fbe382a3b4c0ad84c5af3b7bef7d551275dc717d69ec6 9262 
virtualpg_2.0.1-4_amd64.buildinfo
Files:
 2f93b536250920a378b18b2a6a48aead 2143 science optional virtualpg_2.0.1-4.dsc
 b7cf0cd0555fe62c1d9815df433b742a 11476 science optional 
virtualpg_2.0.1-4.debian.tar.xz
 9ea1ecc98b4de39cb18ed32d555d946f 9262 science optional 
virtualpg_2.0.1-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjKeYACgkQZ1DxCuiN
SvFREw//Wcjoa/QlTHFnZAP7z2B2swmIP9nx5TJYyQEVu++rc/WNZlVFi4ADKZjn
bxjB4Qvi+EDk7gvta758zQzE1+2Ei7tOQ3x/OkZ24tpn73THOZqTlhGuNcI+uVtn
nt5sVBuRfNGBrqeM2yDjHQ4tssfwI4IjY2PZ70vwc8RvRrBLyVgQAGLMKTleWT+o
Jt+GZKmUI/hqPcNZw315orcPC6xXah9ATvpT1dTkewJNEGXh/sGveGru24UVm+fb
RJX9OPiKvwYYQxQth96Etv3eB4IPf6HqJ64FNgFtfPSHwPkNK9A74e+5QTA/Rt96
QnhiC76uK6zeICr9HrqCgACefHOPUt5NRh5mBYHHVDf8nJkTvqfTmXPYs4FNoG5N
oItRpFBBo0onqbeMwx/WAkAvZofBYle6Sfzd5xwt3YRO5ZeSLu0VX7iS7QKNSJ47
PLNBXw6bL30AFPG8oqqyBWEbS+4QWSERCXKItg6wv8y/BjdIgeMaQyihlETaDFKy
prI8DFuZKHNB1GxUGskW4V1MsZN5GnqM6TiniNNdcZdZ+zyIS2L20uLgabCrLND3
u3flEdWiGX89ErphA3dFGFUJ8RjiQuxMh3Wu2JlwNkJ7arHRbtgXAp6mvZfprAZS
IslMdmA01ZysBxX53LfAXZeAV/igq6FwKYHDMJjnyF25TMJivKE=
=spx5
-END PGP SIGNATURE-



pgpFU6pHR4uKF.pgp
Description: PGP signature
--- End Message ---

Bug#1065298: marked as done (spatialite: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 13:56:57 +
with message-id 
and subject line Bug#1065298: fixed in spatialite 5.1.0-3
has caused the Debian Bug report #1065298,
regarding spatialite: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065298: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065298
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: spatialite
Version: 5.1.0-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: spatialite
Source-Version: 5.1.0-3
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
spatialite, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated spatialite package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 14:14:07 +0100
Source: spatialite
Architecture: source
Version: 5.1.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065298
Changes:
 spatialite (5.1.0-3) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065298)
Checksums-Sha1:
 16aa54079d04cbff4d1a3ef2272b50ee2fc0996a 2375 spatialite_5.1.0-3.dsc
 4b4fd4a9f23224c62e88077bfc49d8638506bc84 26604 spatialite_5.1.0-3.debian.tar.xz
 535f4d75f470c5e6c747246a6b5cc1db1f06af90 10726 
spatialite_5.1.0-3_amd64.buildinfo
Checksums-Sha256:
 ca9c628c5cd5617308fef6f894b31f2ceddfd335f9ed3aee6714f4d7acaad75c 2375 
spatialite_5.1.0-3.dsc
 edc622e6ed01f75806c7f2b2213ae72330eca8a066ef8902b5989e84b2b16754 26604 
spatialite_5.1.0-3.debian.tar.xz
 e47a0a5de53de968e2e30e8c559a0168d0995418415d2372a7443d01bc89f58a 10726 
spatialite_5.1.0-3_amd64.buildinfo
Files:
 b01d372c9e7132a039c2aab8a459cab9 2375 science optional spatialite_5.1.0-3.dsc
 ac9451474d0a890406d171c32d79b410 26604 science optional 
spatialite_5.1.0-3.debian.tar.xz
 7efce00451cb5a7a62cb6f7ec5ad2824 10726 science optional 
spatialite_5.1.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjJ+4ACgkQZ1DxCuiN
SvFh4xAAvMYfOqZWjAT5Kh6QCabyGp43iiUZbyH2ArxyCAiSMiWYMXIg9N/KzbFi
w4u8vVjES+dnbmWwCx1bn1PDRFoTMZzAbNeakECXYAj1mLMiNPTggPMpO40YjEFI
WR/UeDOdLmQYwMp6SlcFTyr0ZaWE2i+hBG572HFVWbpf42sTEmJJOqbmEmlXtKnt
j/AyKG73Pvm+njOdxl+DeuWpfbxQQYv77cwFxyEycLDgEJp+HgS+Ky1tdOuIr1/N
DRXixeTE2Okyr9QrZLjINTZplv1EU3/WK9p4B89bDV9yVuFCXwrxTLKNwItyGsTn
htmTX8XoXP40r/N6h1dnHy18NnIAg06LDvX6sTCr7Psdfn/zrbf0Llp3VelQKMdJ
LsZeUozYmu7C84HauwYGbfdKmOlcGkbzNJEPEQoxZy1uJGFE6BOmAHh/L0bH3tVM
vZ/Nh7y+Cr1a/0xLJpJmOU0WGTyovZmquav4H7ytxrK/gSFOVFKqTPJ8Y6CrsHHl
o0OD5igfkl/IB7pM12hzFknrTzBMpc8f/OXhU+Ug7StRFnQVynXwsNguntgrX8FA
TgvAgg9irJJicDL8xDX5xB91tUunucXkpiOEOhOtpbuoPMBLmPHC4H2Lv+fvxv60
cJrvVu+jZkepQefR0qyr/DRl2d+L2QV7DUQELEJ0cMvySDHsdvI=
=DaVv
-END PGP SIGNATURE-



pgpRc0dA5f5il.pgp
Description: PGP signature
--- End Message ---

Bug#1065297: marked as done (sfcgal: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 13:40:09 +
with message-id 
and subject line Bug#1065297: fixed in sfcgal 1.5.1-3
has caused the Debian Bug report #1065297,
regarding sfcgal: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065297: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065297
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sfcgal
Version: 1.5.1-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: sfcgal
Source-Version: 1.5.1-3
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
sfcgal, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated sfcgal package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 14:00:48 +0100
Source: sfcgal
Architecture: source
Version: 1.5.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065297
Changes:
 sfcgal (1.5.1-3) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065297)
Checksums-Sha1:
 6f7cd465db8f35c5f85ad857c706e53778e95341 2157 sfcgal_1.5.1-3.dsc
 708735ce6059fa3b59cfa2bee3b3f1f746291025 157516 sfcgal_1.5.1-3.debian.tar.xz
 a44170f1de1155b42b38b3e06241c43bf679d08d 15758 sfcgal_1.5.1-3_amd64.buildinfo
Checksums-Sha256:
 99d0983b790040288999fd8459e9c15ffbae78c3b386cbb0ee11f9994abc428c 2157 
sfcgal_1.5.1-3.dsc
 57e5966807d7179bf47f6b9a44f3c53948e13af0d905b2e6d0f8e939de19a127 157516 
sfcgal_1.5.1-3.debian.tar.xz
 c32fc2f488c894e80b2e223b183e6e5a7c6ada4621c0df6a2782b08fcb2e0294 15758 
sfcgal_1.5.1-3_amd64.buildinfo
Files:
 97fdc04aae3a996edd2ba83fc340b06d 2157 science optional sfcgal_1.5.1-3.dsc
 acbfd905816d5aff3f8d80a502c76b26 157516 science optional 
sfcgal_1.5.1-3.debian.tar.xz
 52b1a38a4c5dfaffb3815e336bc6d895 15758 science optional 
sfcgal_1.5.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjJdQACgkQZ1DxCuiN
SvF9Sw/+Pgx6goiEj+ejy7a/dAenu9Rt8/iNlRuB/b8wX4dwiTJRefQzHpYUivpz
Y7ZcU6EbeZthBgiSg7BikGlSv2JhVgJPwZAjg/mxKQF1NPoWyw58bO5DvgJkPPRS
KI2pgCNj5BvVe0RdTt04wzNFJlF95XyEwpg270XMr36/kjZaJkO7GNajmXOSrWCb
hcbbyuKIokDRNypbFL5V2hlE3WSc2lUBHI/7MSXE4KXjiwMWA3wG8LnXwT7bJP8O
C80RywkxixOMuO0jTywfYLgVjJ9si3VYGtuEJpTvfgUi3XhElU6YDAtB8DqKqo11
ZHecND/oZCzIK6KiE1oUn+XVFb4ptuM7yLeCUjwXoLEWt9H67guPsQt1yj3IPGNm
Dyla6skbheBtKAONQYaQRuo9+Maus9+QD4W4WlQ50jVDZZXrnyzsV+n2pGARYMdj
miLYEXVVO0oJBTpGWYjabDepm8wNuDvDKhrc3nR00v5pTzEdxisxH8Lgs0qbZBkE
0Im65BbyLElZLy+tBwAIrQeVfPl5KPJSXUfBS7Ws+hcKeX73gBYKO5yIPPwhMi+o
iqOha9L7/fSAKOXIK8H8aacwFt3jGZC+urfbpH27uQEuuPqCmZBzkwu5C/ZCHiIm
00aiDzq/vMiv1atlhqy+L4ceYoIIBjdZXL03csMHtFK1WUxP2KI=
=cTKE
-END PGP SIGNATURE-



pgpmwshNVT3aE.pgp
Description: PGP signature
--- End Message ---

Bug#1065295: marked as done (pktools: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 13:39:47 +
with message-id 
and subject line Bug#1065295: fixed in pktools 2.6.7.6+ds-6
has caused the Debian Bug report #1065295,
regarding pktools: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pktools
Version: 2.6.7.6+ds-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pktools
Source-Version: 2.6.7.6+ds-6
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
pktools, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated pktools package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 13:46:02 +0100
Source: pktools
Architecture: source
Version: 2.6.7.6+ds-6
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065295
Changes:
 pktools (2.6.7.6+ds-6) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065295)
Checksums-Sha1:
 3b033777209cbae192a7f143d1e47baa4a41ff60 2535 pktools_2.6.7.6+ds-6.dsc
 cb46704bfa0504d7d027e2d384538512d1c13a43 45540 
pktools_2.6.7.6+ds-6.debian.tar.xz
 f8fb37332cb7bc0dcc9d0748f3b1c72c6e36be5d 18193 
pktools_2.6.7.6+ds-6_amd64.buildinfo
Checksums-Sha256:
 b81dbe06389d2c2e838e3e946f307765568fdb1a483678c83751ca6c3e6fc1e8 2535 
pktools_2.6.7.6+ds-6.dsc
 45c48c7daa4c3a7bbe0da968cf59654328bff29bc367ba000fcbabeb00fa7931 45540 
pktools_2.6.7.6+ds-6.debian.tar.xz
 4af51afa394baedc2700a6989a690fb023621f51e99809c09daff19b5c4222fa 18193 
pktools_2.6.7.6+ds-6_amd64.buildinfo
Files:
 8d05b273ae6fe1e443dfbf8cf4024986 2535 science optional pktools_2.6.7.6+ds-6.dsc
 e709c10ac7c196d924617633459e9e94 45540 science optional 
pktools_2.6.7.6+ds-6.debian.tar.xz
 c27fd0f0d05f13c3c56f347457f688f4 18193 science optional 
pktools_2.6.7.6+ds-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjIpkACgkQZ1DxCuiN
SvEdDQ/+MsOhFWAu8a6hgREknRyiLjxXqqki9sSJxvyR6Afxcb4RyuNTbAe/1grQ
eOF3070lmmZISyPFUaMLdRpZL9BPBHnxOrnMO348vvcrtczH4VT5HCb7oha1iB6J
a43ilWEJo3iFiCLB9C1VGWPsxDOAGSeqgTKpQEs936yRCg5O6LBUyQ8zX5KWDBx6
4F6pdQezPQPPPAAThhXumrgx90DB3LTb5A5h593uS0tEXklSP4PB0/9m54Ajfdfq
xfRiD+2pFqfxk+XOtpy0qugTmlPpaAxKysn3cvJK2mxPZFie/S7QamKt8NUrS1rb
/xR74g8gkOgM5cZt4P1YLup3Gow+6PlpJH7wAJ072ejr7wS01es9XMOkqpbxM3ip
wItn5SgPoz5zcyfWpYLf4LRsVKZd9PUdzoD/exuRZ6sUUyiGqssZW/4sooLQb14h
mSHMhXgEhcWVfCkB9wvbUEjTunYbvZhOnKWAWbaa1yq8ZwvhP9oojEHDIFVlTqB/
oTPecKf0g5joWczru5b+YF8HLfUN6kqhFHvh/PI1/Vcqpu/jS3r2P6HmxY/6U6zz
Wb7cLc0EL6rjKAkdwzo5YTv4kf8Zq5+JKoPyFquIT6ttPS4yX/G3OaFVUDtdQjaW
NFEbFvS5QUoc/hDjrBxrlxwUx/ezIL87F+GpzN0062XxbT2Am3E=
=a8lm
-END PGP SIGNATURE-



pgptG5thA3nOG.pgp
Description: PGP signature
--- End Message ---

Bug#1065294: marked as done (mapnik: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 13:11:15 +
with message-id 
and subject line Bug#1065294: fixed in mapnik 3.1.0+ds-7
has caused the Debian Bug report #1065294,
regarding mapnik: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065294
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mapnik
Version: 3.1.0+ds-6
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: mapnik
Source-Version: 3.1.0+ds-7
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
mapnik, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated mapnik package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 13:14:12 +0100
Source: mapnik
Architecture: source
Version: 3.1.0+ds-7
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065294
Changes:
 mapnik (3.1.0+ds-7) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065294)
Checksums-Sha1:
 97cc4dec0a50cba8bf94a0053ddf85d67db803cd 2640 mapnik_3.1.0+ds-7.dsc
 1a82fd627c0af716a4996ad954edd444f80518e1 37640 mapnik_3.1.0+ds-7.debian.tar.xz
 9f26c454e360fa53e40812a7ff762397f41b6839 17094 
mapnik_3.1.0+ds-7_amd64.buildinfo
Checksums-Sha256:
 dd0056d89b0911320b8582848e9dd3cd6b5bf07bb3979852dea83532c36aa889 2640 
mapnik_3.1.0+ds-7.dsc
 6728f3cea91f5c2a67d64fd1b7ea22b6a66ba99684c5e14473791c36676e94bd 37640 
mapnik_3.1.0+ds-7.debian.tar.xz
 478e0e48401aef6f109b5e29cbcf5b7e7db1c7ba63b603abbea4e55c1a15c458 17094 
mapnik_3.1.0+ds-7_amd64.buildinfo
Files:
 64e35fff3e259e1c3232b2d59f5f0df9 2640 libs optional mapnik_3.1.0+ds-7.dsc
 c5fdcef1701842b33fcf68a07c42a025 37640 libs optional 
mapnik_3.1.0+ds-7.debian.tar.xz
 f3599e0b2c7cd76bca0836d507b8e989 17094 libs optional 
mapnik_3.1.0+ds-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjGkkACgkQZ1DxCuiN
SvEqRg//c9rNItrwlKoRW8razWh0ZH8GfePOFK8sJthnlRhsXlsttuO49w8aI5Wo
uFqkGvLbTuGKRTYjbfPqRxV/Dqi/vhGphkoRDW7kEPtCXQuC99T/GtBtMX08kz5k
HouKPBXDGxj45VVGWY5GF9R0Z9kOcGT5assLnsPtCpWS4wRsiMyRH4XNtAxUxf8t
+PDuxQFLFe6fZ9N520/FFyRulTcYrlhzU2dJgADXX27qQpYSD0v3QA/2t54ue6H6
458itoz7UgswmK6sz0yRYZcBBGhAtu+1q/5BgAqrc/Sl4Di5X6/f3ZANM6G7xrgk
1eEacI5jQV4Nmo2tr9LM5cVw8v8TaXqfy2bMBqEFeS4n4S0//1fr/sQWC+WHgUSG
qQ/YlBRbW1S5/Feu/zIHRC+9Hue/n24uKecZKiZhd7RAnt17rb4g+tr55eqUaBFX
v/w4xcD2C0r1Pm254++yapWQxB+8qXaEMbJtqF6VAvUcELI0gFSciRbqE9HP6vz8
OvWUBhFAF5B8ZuN/XeA6lLfOWhmEhvXDb9z39XOe++pgGLyHIvSXCLeOpeT3Jte4
glXt0/5NAroxavAubDDVkf+kx2yxc3F8s0grI2OBx6Ms8eGBCbNmscnL4g7pxdLa
iG2VIOH6M3Y8lnVgkrmTRdoCU9iXIOxgEpdwf03hCEW0lcf5zSw=
=1VLo
-END PGP SIGNATURE-



pgpIoTKxjKtnn.pgp
Description: PGP signature
--- End Message ---

Bug#1065255: marked as done (netcdf: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 13:11:54 +
with message-id 
and subject line Bug#1065255: fixed in netcdf 1:4.9.2-5
has caused the Debian Bug report #1065255,
regarding netcdf: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065255: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065255
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netcdf
Version: 1:4.9.2-4
Severity: serious
X-Debbugs-Cc: sramac...@debian.org,  vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. Hence, the package was built with an old version of dpkg
not enabling the changes for the time_t transition. Please add dpkg-dev
(>= 1.22.5) to Build-Depends and upload the new version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: netcdf
Source-Version: 1:4.9.2-5
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
netcdf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated netcdf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 13:34:30 +0100
Source: netcdf
Architecture: source
Version: 1:4.9.2-5
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065255
Changes:
 netcdf (1:4.9.2-5) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065255)
Checksums-Sha1:
 ff4de4b69292ab7e8b6dbd07186155bb1c3b8838 2383 netcdf_4.9.2-5.dsc
 c2f6678cdc7e1d4a0802df3113bcb706b611f4d2 35268 netcdf_4.9.2-5.debian.tar.xz
 29c23fa1ae24082b6282c90e7b77dc836ac24ecd 12579 netcdf_4.9.2-5_amd64.buildinfo
Checksums-Sha256:
 02c601b6a10d1dacb6e36cae06b84fcfcc753889ece7e8efd214b402b80cb0f6 2383 
netcdf_4.9.2-5.dsc
 ef210e055ab8944c833f5562138986ed76343d948136869b15f2fce968cc7c7d 35268 
netcdf_4.9.2-5.debian.tar.xz
 69a577b01e63b224d643857ced3dbab067a1d8371295f1d836e9568d43ebbb46 12579 
netcdf_4.9.2-5_amd64.buildinfo
Files:
 fbb0147d0cd49475957df36a74be40ec 2383 science optional netcdf_4.9.2-5.dsc
 4850eff0fec003f0628007be7838f2cd 35268 science optional 
netcdf_4.9.2-5.debian.tar.xz
 5b8a3f122c52a84413075e6278c4bf89 12579 science optional 
netcdf_4.9.2-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjHzAACgkQZ1DxCuiN
SvHuZhAA2uki2vzJgnsC9KlTw0yygLvkRO1mQxjjcL4W30ZR1L9TUd1vt4Rr5UU9
9hdgpNjlT8CvjX3OO0EAZhqk6IcOrWQeZSRh4f3nrIHMY+eJZbzDiqVg94qzJEx9
FicaPK3LHwRXQc5egHde37oJTL+FhiJDKBNgyit1gbCiax0+gspNEXIttD6IzQJi
k1H0v+jcnLVGkp9K/i9fyGkfdatLy9nshQud0Aj4qOZAf8ohk3lQqgWaUSRxogkZ
C4QjYAZPDfmZ8o5dw6QdtROuBnbIwoFvR6dp4ESoDYGoyl4b92efudmCTUZnqLVh
qaDDAdE2XqHWRXu6uUU983PFC7lJj7XMtLcBtArEKLEMIWumYhMFYCNI23IDfjYd
FoyyrntcYlhS7DTL2CjsN0K/Heje13V1UFOLdUTDvaQCaOOfyKvw8JDzUeUPCUG3
zMYyX4LGY46L27Gbznx3VYonXF/UVSlsnOL0KjebbdPjFP6XBpSROtExOsp5tSpX
z35FynO2ZmwCirhs/2P8LlzmNE6+Kxfr+Ibc88hM2Gv6/vQaKLA031l6qOMQT9fL
WNnFux71hBvUGd5uvd6WrULaI/TNBbcwyvJHaMJqwXPTh96jnCGB0eEoHd1Kwfm9
9rXwd7V/tnnSdgvT7i2N2gKag+sH2TBGh8gn8UAqXwLahnJDHvM=
=tBLw
-END PGP SIGNATURE-



pgplNQ8klVtyp.pgp
Description: PGP signature
--- End Message ---

Bug#1065242: marked as done (libuuid1: removing libuuid1t64 leads to file losses)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 13:14:03 +
with message-id 
and subject line Bug#1065242: fixed in util-linux 2.39.3-8
has caused the Debian Bug report #1065242,
regarding libuuid1: removing libuuid1t64 leads to file losses
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libuuid1
Version: 2.39.3-7
Severity: serious

The last upload renamed libuuid1t64 back to libuuid1, but because the
former has an unversioned Replaces: on the latter, it will not take the
library files back.  Removing the libuuid1t64 package will therefore
silently lose the files.

It seems to me that libuuid1 needs a Replaces/Conflicts on libuuid1t64
to prevent this scenario.  Additionally, in order not to break reverse
dependencies of libuuid1t64, the Provides: libuuid1t64 needs to be
versioned.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
--- End Message ---
--- Begin Message ---
Source: util-linux
Source-Version: 2.39.3-8
Done: Chris Hofstaedtler 

We believe that the bug you reported is fixed in the latest version of
util-linux, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated util-linux package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 02 Mar 2024 13:45:06 +0100
Source: util-linux
Architecture: source
Version: 2.39.3-8
Distribution: unstable
Urgency: medium
Maintainer: util-linux packagers 
Changed-By: Chris Hofstaedtler 
Closes: 1063638 1065242
Changes:
 util-linux (2.39.3-8) unstable; urgency=medium
 .
   [ Chris Hofstaedtler ]
   * Break/Replace libuuid1t64 and provide it versioned (Closes: #1065242)
   * Update architecture list for Provides: libuuid1t64
   * d/gbp.conf: update debian-branch
 .
   [ Johannes Schauer Marin Rodrigues ]
   * util-linux.postinst: avoid running uname in maintainer script for
 chrootless hurd support (Closes: #1063638)
Checksums-Sha1:
 1d8af39685f391f2f90002f5b644954d975254ef 4611 util-linux_2.39.3-8.dsc
 4019bf1ec3bf0a4829f17cd4519587f31801e226 100552 
util-linux_2.39.3-8.debian.tar.xz
 b2232db0e4be211f42fc52c065466306b0a15e10 19541 
util-linux_2.39.3-8_arm64.buildinfo
Checksums-Sha256:
 dc00f1cb9d18c7f340dc2f2945be90ee5ccd60583cd8f171c0d457a66c33be51 4611 
util-linux_2.39.3-8.dsc
 12965e15836a1f7f7787b3a87da1aff02c3bada8987b00f3a0ef2ba3045ac966 100552 
util-linux_2.39.3-8.debian.tar.xz
 fa5e3a72b0c54013be293a6470cd978683954f3431ea154bec78f173ec12aae8 19541 
util-linux_2.39.3-8_arm64.buildinfo
Files:
 e24d8d72a83ade01f7213dd7d3acde01 4611 base required util-linux_2.39.3-8.dsc
 94748ec61e4c831ba925c01824feb354 100552 base required 
util-linux_2.39.3-8.debian.tar.xz
 dce29b641a11261c1efb2a186efe2221 19541 base required 
util-linux_2.39.3-8_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmXjIc8ACgkQXBPW25MF
LgNNIg//al990Qynh+qE1m58cHaUFlAXSNBAed1lveI9krVwzfVgslN9bQtrmDeC
4MQLkZAZdtybW51qv5CdaDCJ4905qjYPKVYa09AHaVbFzJ9R7TdWe0fvZ9ahsQeL
h7S/Y9ueA/4wDDSDxpGfoMSByZvrtPd9h4Gp7FqsZFCBXoNQRbUAjzHH9U7I/WiL
Z/Kpie4xG7ymONzNfp5/ikuolJHfA5WywmBK1boxSjSXmTKvhcEUrR2iHF8/dIZ/
NAq736+t6rbThV+2s+re0HSsoh1JOkbzzsvsjMtBvJzSO7/gwpWwsRXnXygT96wX
Ucqnka8SEiFrmiesF+uMNR8Xu/TU83c05AuHBoxyI3Nf4gjgD8lOGffXjznvXeP0
y8Q/xX5Z77GSE8x4/0woobsL7RF9uEI4Qx0AlpT99bLkzNmRMVNj9g5libVhEtkY
fj65J4tckPQTQ108PY3ojtJIFyVvSKOwJDcjWPDbxlzVrnWDdB1QEfKWyydAtDvV
wAEczn+RvogxPdmQpqUwrcIwtDTQ2M8QmVGQnMjgFNrxMCTR6uVajE2/22ncurEN
n6bBLbpWraGltCz7nBTplo5Z5tAyYRHwKhi9gWBKvWEIM6Ub21tEP/cYcU8Qta6D
hKAkJeKX2kyiCCnNLvjFIz1sjx5J1U/zyfd/wufhwN1x8gk9iJc=
=3weF
-END PGP SIGNATURE-



pgpz670o1pOok.pgp
Description: PGP signature
--- End Message ---

Processed: tagging 1065305, tagging 1065282, tagging 1065283, tagging 1065046

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 1065305 + sid trixie
Bug #1065305 [src:brewtarget] brewtarget: switch to boost 1.83
Added tag(s) sid and trixie.
> tags 1065282 + sid trixie
Bug #1065282 [src:dsniff] dsniff: missing build-dep on libtirpc-dev
Added tag(s) sid and trixie.
> tags 1065283 + sid trixie
Bug #1065283 [lsof] lsof: recent libc6-dev change causes the RPC support to be 
dropped
Added tag(s) trixie and sid.
> tags 1065046 + sid trixie
Bug #1065046 [ace-of-penguins] ace-of-penguins: FTBFS on armhf with implicit 
function declaration
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065046
1065282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065282
1065283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065283
1065305: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065305
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065305: brewtarget: switch to boost 1.83

[Sebastian Ramacher]

Source: brewtarget
Version: 3.0.6-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

We'd like to release trixie without boost1.74 (see #1060102). Please
switch to the unversioned build dependencies or to boost1.83.

Cheers
-- 
Sebastian Ramacher

Bug#1065303: dmrgpp: switch to boost 1.83

[Sebastian Ramacher]

Source: dmrgpp
Version: 6.06-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

We'd like to release trixie without boost1.74 (see #1060102). Please
build with the current default version of boost or switch to boost1.83.

Cheers
-- 
Sebastian Ramacher

Bug#1065290: marked as done (libhdf4: missing build-dep on libtirpc-dev)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 12:19:48 +
with message-id 
and subject line Bug#1065290: fixed in libhdf4 4.2.16-4
has caused the Debian Bug report #1065290,
regarding libhdf4: missing build-dep on libtirpc-dev
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libhdf4
Version: 4.2.16-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
User: debian-gl...@lists.debian.org
Usertags: libtirpc-dev

Dear maintainer,

Starting with glibc 2.31, support for NIS (libnsl library) has been
moved to a separate libnsl2 package. In order to allow a smooth
transition, a libnsl-dev, which depends on libtirpc-dev, has been added
to the libc6-dev package.

The libnsl-dev dependency has been temporarily dropped in the 2.37-15.1
NMU, as part of the 64-bit time_t transition. This causes libhdf4 to
FTBFS in sid with:

| dh_auto_configure --sourcedirectory=HDF4 \
|   --builddirectory=debian/build-hdf4 \
|   -- --prefix=/usr \
|  --includedir=/usr/include/hdf \
|  --libdir=/usr/lib \
|  --enable-shared \
|  --enable-fortran \
|  --with-szlib=yes \
|  F77="gfortran" CC="gcc" CXX="g++" \
|  CFLAGS="-g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/tirpc/" LDFLAGS="-Wl,-z,relro -Wl,-z,now -ltirpc"
| cd debian/build-hdf4 && ../../HDF4.2.16/configure 
--build=x86_64-linux-gnu --prefix=/usr --includedir=\${prefix}/include 
--mandir=\${prefix}/share/man --infodir=\${prefix}/share/info --sysconfdir=/etc 
--localstatedir=/var --disable-option-checking --disable-silent-rules 
--libdir=\${prefix}/lib/x86_64-linux-gnu --runstatedir=/run 
--disable-maintainer-mode --disable-dependency-tracking --prefix=/usr 
--includedir=/usr/include/hdf --libdir=/usr/lib --enable-shared 
--enable-fortran --with-szlib=yes F77=gfortran CC=gcc CXX=g\+\+ "CFLAGS=-g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/tirpc/" "LDFLAGS=-Wl,-z,relro 
-Wl,-z,now -ltirpc"
| checking for a BSD-compatible install... /usr/bin/install -c
| checking whether build environment is sane... yes
| checking for a race-free mkdir -p... /usr/bin/mkdir -p
| checking for gawk... no
| checking for mawk... mawk
| checking whether make sets $(MAKE)... yes
| checking whether make supports nested variables... yes
| checking whether make supports nested variables... (cached) yes
| checking whether to enable maintainer-specific portions of Makefiles... no
| checking shell variables initial values... done
| checking build system type... x86_64-pc-linux-gnu
| checking host system type... x86_64-pc-linux-gnu
| checking if basename works... yes
| checking if xargs works... yes
| checking for config x86_64-pc-linux-gnu... no
| checking for config x86_64-pc-linux-gnu... no
| checking for config pc-linux-gnu... no
| checking for config pc-linux-gnu... no
| checking for config x86_64-linux-gnu... no
| checking for config x86_64-linux-gnu... no
| checking for config x86_64-pc... no
| checking for config linux-gnu... found
| compiler 'gcc' is GNU gcc-13.2.0
| gfortran: error: unrecognized command-line option '-V'
| gfortran: fatal error: no input files
| compilation terminated.
| ../../HDF4.2.16/config/gnu-fflags: line 66: test: -ge: unary operator expected
| checking whether make sets $(MAKE)... (cached) yes
| checking for gcc... gcc
| checking whether the C compiler works... no
| configure: error: in `/<>/debian/build-hdf4':
| configure: error: C compiler cannot create executables
| See `config.log' for more details
| cd debian/build-hdf4 && tail -v -n \+0 config.log
| ==> config.log <==
| This file contains any messages produced by compilers while
| running configure, to aid debugging if configure makes a mistake.
 
...
 
| configure:4337: checking whether the C compiler works
| configure:4359: gcc -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/include/tirpc/ -std=c99 -Wall -Wcast-qual -Wconversion -Wextra 
-Wfloat-equal -Wformat=2 

Bug#1065292: marked as done (libkml: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 12:19:58 +
with message-id 
and subject line Bug#1065292: fixed in libkml 1.3.0-12
has caused the Debian Bug report #1065292,
regarding libkml: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libkml
Version: 1.3.0-11
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: libkml
Source-Version: 1.3.0-12
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
libkml, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated libkml package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 12:55:16 +0100
Source: libkml
Architecture: source
Version: 1.3.0-12
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065292
Changes:
 libkml (1.3.0-12) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065292)
Checksums-Sha1:
 4eda5d3af9e588d303ad93bcb5ef01f391c0a55d 2543 libkml_1.3.0-12.dsc
 ce5a7fed82883feb3d17a26dc7822b77e75f3169 26204 libkml_1.3.0-12.debian.tar.xz
 4807efc3a7f7e904536587d2c67cb06f3a48277c 12652 libkml_1.3.0-12_amd64.buildinfo
Checksums-Sha256:
 6ab8306bd9081dd237919bb3db7a3b4cca4fbca0c8475d2723732a01b0d5606b 2543 
libkml_1.3.0-12.dsc
 060d85625d62fcb7750140eac0a8e2f64dd83f5d19601af2865fa832d5dafc72 26204 
libkml_1.3.0-12.debian.tar.xz
 dedfc257e5ae813cc8fa5837bf786c9d536a35b2826367d1b7961390037b7c99 12652 
libkml_1.3.0-12_amd64.buildinfo
Files:
 440635c9eb2dc532dc480fe397b22d1e 2543 science optional libkml_1.3.0-12.dsc
 121598f86ca03e1752ee1f743e615927 26204 science optional 
libkml_1.3.0-12.debian.tar.xz
 ff00015a1700e20bcc727fae65e377c7 12652 science optional 
libkml_1.3.0-12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjFFwACgkQZ1DxCuiN
SvF8jBAAzT534yTm+W+nEPfLS+63z54wf4vsdHkR3sRWhC8xa4QqjcTIFLeUivl9
xRoueW4HzPUaOeeISTv4lVqvweL5TfvRJJArWyEsnrHDtfDco+tLXyeSnaYGDAV8
W8YfSzkM0NOGjrpIZDiZZzc8cjxMBWivviEjeHMu5n6DAc8+Zarlnyz1EqC8gJd6
FOYudlprKh3foVtgywsH1MgZHbHBk11vvBS1dmmrnOWTV75QJnDdk5wjQONL+M8X
A5ajQEhoxHbnlnivgggMyRyp6iuQp6kESnahU9uWqmzh4mlsNDLf+H+BGYv6LaeT
JdMNjHowPiV4gA/fym3yuxFF6lDPKgvWYbKnhd262UbLOGEfd6Pew1vkH1TF5iBD
hQoARxDcIH9NTB8WAAnLpawb8TJ3XMCWtOKexDVf4fCf9YIIFqIGhXLmYMFsmUol
f+FAT83s8STk3sz5mV0/x7PoZSILY63FZF1oL9ANib0/tiN8w0NN2UKcai9bcgmv
/kCReg5mAECgcvx8cE9c1AIjgXcSbIZXnbgViYdAAFO3xziJTGS2X1SSBkiYzD14
JRK4Oj0ccic39sjYndRAmS7Gth2rzj3nIe0ibdX32nSTiBUtN0eU+GAlDVkIzOWH
mAagKYB+qfExmauA0HO6i9doE+MKCvkHN00o1h7QYoRfGAXbV9M=
=Zlug
-END PGP SIGNATURE-



pgpGhmbtoAFMs.pgp
Description: PGP signature
--- End Message ---

Bug#1065280: glib2.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

On 2024-03-02 11:23:33 +, Simon McVittie wrote:
> Control: tags -1 + pending
> 
> On Sat, 02 Mar 2024 at 11:51:26 +0100, Sebastian Ramacher wrote:
> > Please add dpkg-dev (>= 1.22.5) to Build-Depends
> 
> This is already fixed in git, but we were told not to upload that version
> yet, to avoid interfering with the migration of the NMU currently
> in unstable (which, at the time, was believed to be sufficient and
> desirable). It is also already fixed in experimental (2.79.3-1).

Great, thanks!

> > and upload the new version ASAP
> 
> glib2.0 already has a Severity: critical bug related to this transition
> (#1065022) which I am attempting to resolve with a minimum of collateral
> damage (#1065170). I apologise for not having been able to resolve this
> instantaneously; maintaining GLib in Debian is not my only responsibility.
> 
> If it is critically urgent that it must be uploaded to fix the missing
> dpkg-dev dependency as soon as possible, someone is welcome to upload
> what's in gnome-team git, but it takes me 2 hours per attempt to carry
> out the minimal level of testing on GLib that I understand the project
> to require from me (build, autopkgtest, piuparts), so it seems like it
> might be better to combine the upload for this with the upload to fix
> #1065022 when that change is ready.

In this specific case it is not urgent then. The other bugs will block
it already. I will schedule binNMUs to ensure that the current binaries
in the archive are rebuilt with dpkg-dev (>= 1.22.5).

Cheers
-- 
Sebastian Ramacher

Processed: Bug#1065242 marked as pending in util-linux

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065242 [libuuid1] libuuid1: removing libuuid1t64 leads to file losses
Added tag(s) pending.

-- 
1065242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065242
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065242: marked as pending in util-linux

[Chris Hofstaedtler]

Control: tag -1 pending

Hello,

Bug #1065242 in util-linux reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/debian/util-linux/-/commit/e1bd9dfee696d58a942c8dbc2c11ab7c5e001e26


Break/Replace libuuid1t64 and provide it versioned

Closes: #1065242


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065242

Bug#1065262: marked as done (geos: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 12:04:24 +
with message-id 
and subject line Bug#1065262: fixed in geos 3.12.1-3
has caused the Debian Bug report #1065262,
regarding geos: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065262: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065262
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: geos
Version: 3.12.1-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: geos
Source-Version: 3.12.1-3
Done: Bas Couwenberg 

We believe that the bug you reported is fixed in the latest version of
geos, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1065...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bas Couwenberg  (supplier of updated geos package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 02 Mar 2024 12:25:53 +0100
Source: geos
Architecture: source
Version: 3.12.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian GIS Project 
Changed-By: Bas Couwenberg 
Closes: 1065262
Changes:
 geos (3.12.1-3) unstable; urgency=medium
 .
   * Add dpkg-dev (>= 1.22.5) to build dependencies for t64 changes.
 (closes: #1065262)
Checksums-Sha1:
 0040ec85ac777df3d9fb1834b9eb20fab4d45101 2318 geos_3.12.1-3.dsc
 d36a61ccf643da4079962bfb15d79589709296c7 69684 geos_3.12.1-3.debian.tar.xz
 c3a142e5a5eb0df6be0e368f766f775bb4e84273 11217 geos_3.12.1-3_amd64.buildinfo
Checksums-Sha256:
 5dad2e1d4bfaee430bf39cf86a880f02cb583b5a809df4c22b7ea9aa4b4cb3da 2318 
geos_3.12.1-3.dsc
 83822c8942c073f30b390b266ae99136306827acd8ae4def3e1f763ad1932db6 69684 
geos_3.12.1-3.debian.tar.xz
 f63c34b07c5357f56bd5eb73cb2a684223d78b961afdaf4089b92fe452f2410d 11217 
geos_3.12.1-3_amd64.buildinfo
Files:
 643e0456489bd52fc02721ce0625b7af 2318 science optional geos_3.12.1-3.dsc
 ab358affbb748b9f3af60f3627da186d 69684 science optional 
geos_3.12.1-3.debian.tar.xz
 b106139db26c299540f609d0d0eabf28 11217 science optional 
geos_3.12.1-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEgYLeQXBWQI1hRlDRZ1DxCuiNSvEFAmXjERQACgkQZ1DxCuiN
SvHufRAAjk0M0jH8dx/ivKFaYJ5jMVKlEQEYoaubbG7HMfbotMYx6ud6vf8NWNRN
Ej/ln5wWSDHYZ94eNjddjc4KnLfdjVHp9PDONm7sl9yyE+O5L13FPGR6abYS4rMH
428GyGgKYCQIle0lUbXYV1Vgfai3xBfN0cLGrfo4XjgIW2wC1sRVUovvz8FakN0N
J7KI3NEjLjKEK5LNOW1L52zzs0Oe5pR9h+F/7ahnfoyieWs0pZdPuRF/Y7p7dV6h
GSKi+NPkAWHIWYWt1NCQndzD2KbNnRYzA34efDuAdslMs4SyDzLbCWHmnMk+hmny
T/qM6gW5GBhM9lALgnwFbXW4jYrbNl0Ua8hr+EBewHEwrsFOOtwEJEQJkZzuF9Z6
/ha4M2ehhnFMjXhRWTg+MQ5P0G77flLqcII6EUmWN1gAOoIPaXYErCfyMTMFnYLu
MtTCIjY5izsz+2wv/JTsOfy2+wQwimRkvUVgQ53/+YHeEJLhJ1sUeO1tE26Hah4X
bNvnw8JBt6k5PbcHiB1jwplDH/mLyDls+iZ3Mivc+2WgENWJWoxD83s5e6vtrGC4
M4yjzZBWDcU5KEo8ueNdk/aVKJ1Dl4JJy0RvCrWXqMNosol32C9EbwEnYJFJXcBX
KmgZBCEdghQAvWTrrN72t7w9JepJm2mgY1F5CBKygYTQf1uOwR8=
=0DEf
-END PGP SIGNATURE-



pgpYPzuO9rZoZ.pgp
Description: PGP signature
--- End Message ---

Bug#1065293: marked as done (gmt: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 2 Mar 2024 12:53:21 +0100
with message-id <9c8b6ff4-2493-408f-8cc2-2cb2313b8...@xs4all.nl>
and subject line Re: Bug#1065293: gmt: missing dpkg-dev (>= 1.22.5) build 
dependency for time_t transition
has caused the Debian Bug report #1065293,
regarding gmt: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gmt
Version: 6.5.0+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

fixed 1065293 gmt/6.5.0+dfsg-3
thanks

Already fixed.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---

Processed: Re: Bug#1065293: gmt: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 1065293 gmt/6.5.0+dfsg-3
Bug #1065293 [src:gmt] gmt: missing dpkg-dev (>= 1.22.5) build dependency for 
time_t transition
The source gmt and version 6.5.0+dfsg-3 do not appear to match any binary 
packages
Marked as fixed in versions gmt/6.5.0+dfsg-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065293: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065293
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065291: marked as done (gdal: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 2 Mar 2024 12:47:12 +0100
with message-id 
and subject line Re: Bug#1065291: gdal: missing dpkg-dev (>= 1.22.5) build 
dependency for time_t transition
has caused the Debian Bug report #1065291,
regarding gdal: missing dpkg-dev (>= 1.22.5) build dependency for time_t 
transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1065291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gdal
Version: 3.8.4+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---

fixed 1065291 gdal/3.8.4+dfsg-3
thanks

Already fixed.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1--- End Message ---

Processed: Re: Bug#1065291: gdal: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 1065291 gdal/3.8.4+dfsg-3
Bug #1065291 [src:gdal] gdal: missing dpkg-dev (>= 1.22.5) build dependency for 
time_t transition
The source gdal and version 3.8.4+dfsg-3 do not appear to match any binary 
packages
Marked as fixed in versions gdal/3.8.4+dfsg-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1065291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065291
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1065299: virtualpk: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Source: virtualpg
Version: 2.0.1-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher

Bug#1065298: spatialite: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Source: spatialite
Version: 5.1.0-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher

Bug#1065297: sfcgal: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Source: sfcgal
Version: 1.5.1-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher

Bug#1065296: qgis: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Source: qgis
Version: 3.34.4+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher

Bug#1065295: pktools: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Source: pktools
Version: 2.6.7.6+ds-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher

Bug#1065294: mapnik: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Source: mapnik
Version: 3.1.0+ds-6
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher

Bug#1065293: gmt: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Sebastian Ramacher]

Source: gmt
Version: 6.5.0+dfsg-2
Severity: serious
X-Debbugs-Cc: sramac...@debian.org, vor...@debian.org

Thank you for uploading the changes required for the time_t transition.
Unfortunately, the upload was missing dpkg-dev (>= 1.22.5) in
Build-Depends. This leads to two potential issues:

* The package is built with the wrong ABI.
* The package migrates to testing before the change is enabled in
  testing and builds there would be produced against the wrong ABI.

Please add dpkg-dev (>= 1.22.5) to Build-Depends and upload the new
version ASAP.

Cheers
-- 
Sebastian Ramacher

Bug#1062832: marked as done (opencascade: NMU diff for 64-bit time_t transition)

[Debian Bug Tracking System]

Your message dated Sat, 02 Mar 2024 11:24:11 +
with message-id 
and subject line Bug#1062832: fixed in opencascade 7.6.3+dfsg1-7.1
has caused the Debian Bug report #1062832,
regarding opencascade: NMU diff for 64-bit time_t transition
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1062832: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062832
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: opencascade
Version: 7.6.3+dfsg1-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
opencascade 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 opencascade
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 opencascade-7.6.3+dfsg1/debian/changelog 
opencascade-7.6.3+dfsg1/debian/changelog
--- opencascade-7.6.3+dfsg1/debian/changelog2023-05-23 04:45:56.0 
-0300
+++ opencascade-7.6.3+dfsg1/debian/changelog2024-02-03 15:42:50.0 
-0300
@@ -1,3 +1,10 @@
+opencascade (7.6.3+dfsg1-7.1) experimental; urgency=medium
+
+  * Non-maintainer upload.
+  * Rename libraries for 64-bit time_t transition.
+
+ -- Lucas Kanashiro   Sat, 03 Feb 2024 15:42:50 -0300
+
 opencascade (7.6.3+dfsg1-7) unstable; urgency=medium
 
   * Update broken symlink /usr/bin/occt-draw to new version
diff -Nru opencascade-7.6.3+dfsg1/debian/control 
opencascade-7.6.3+dfsg1/debian/control
--- opencascade-7.6.3+dfsg1/debian/control  2023-05-14 06:02:22.0 
-0300
+++ opencascade-7.6.3+dfsg1/debian/control  2024-02-03 15:42:50.0 
-0300
@@ -27,16 +27,17 @@
 Homepage: https://www.opencascade.com/
 Rules-Requires-Root: no
 
-Package: libocct-foundation-7.6
+Package: libocct-foundation-7.6t64
+Provides: ${t64:Provides}
 Architecture: any
 Multi-Arch: same
 Section: libs
 Depends: ${misc:Depends},
  ${shlibs:Depends}
 Pre-Depends: ${misc:Pre-Depends}
-Breaks: libocct-foundation-7.4,
+Breaks: libocct-foundation-7.6 (<< ${source:Version}), libocct-foundation-7.4,
 libocct-foundation-7.5,
-Replaces: libocct-foundation-7.4,
+Replaces: libocct-foundation-7.6, libocct-foundation-7.4,
   libocct-foundation-7.5,
 Description: OCCT module underlying all other OCCT classes
  Open CASCADE Technology is a suite for 3D surface and solid modeling,
@@ -56,8 +57,8 @@
 Architecture: any
 Multi-Arch: same
 Section: libdevel
-Depends: libocct-foundation-7.6 (<< ${binary:Version}+1~),
- libocct-foundation-7.6 (>= ${binary:Version}),
+Depends: libocct-foundation-7.6t64 (<< ${binary:Version}+1~),
+ libocct-foundation-7.6t64 (>= ${binary:Version}),
  ${misc:Depends}
 Conflicts: liboce-foundation-dev
 Breaks: occt-misc (<< 7.6.3+dfsg1-4~)
@@ 

Bug#1065280: glib2.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Simon McVittie]

Control: tags -1 + pending

On Sat, 02 Mar 2024 at 11:51:26 +0100, Sebastian Ramacher wrote:
> Please add dpkg-dev (>= 1.22.5) to Build-Depends

This is already fixed in git, but we were told not to upload that version
yet, to avoid interfering with the migration of the NMU currently
in unstable (which, at the time, was believed to be sufficient and
desirable). It is also already fixed in experimental (2.79.3-1).

> and upload the new version ASAP

glib2.0 already has a Severity: critical bug related to this transition
(#1065022) which I am attempting to resolve with a minimum of collateral
damage (#1065170). I apologise for not having been able to resolve this
instantaneously; maintaining GLib in Debian is not my only responsibility.

If it is critically urgent that it must be uploaded to fix the missing
dpkg-dev dependency as soon as possible, someone is welcome to upload
what's in gnome-team git, but it takes me 2 hours per attempt to carry
out the minimal level of testing on GLib that I understand the project
to require from me (build, autopkgtest, piuparts), so it seems like it
might be better to combine the upload for this with the upload to fix
#1065022 when that change is ready.

smcv

Processed: Re: Bug#1065280: glib2.0: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + pending
Bug #1065280 [src:glib2.0] glib2.0: missing dpkg-dev (>= 1.22.5) build 
dependency for time_t transition
Added tag(s) pending.

-- 
1065280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems