Bug#1067813: nmu: spatialite_5.1.0-3

2024-03-27 Thread Sebastiaan Couwenberg
Control: merge 1067812 1067813 I already requested this a little earlier. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1

Processed: Re: Bug#1067813: nmu: spatialite_5.1.0-3

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > merge 1067812 1067813 Bug #1067812 [release.debian.org] nmu: spatialite_5.1.0-3 Bug #1067813 [release.debian.org] nmu: spatialite_5.1.0-3 Merged 1067812 1067813 -- 1067812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067812 1067813: https://bugs.debian.org/c

Processed: nmu: netcdf_1:4.9.2-5

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:netcdf Bug #1067818 [release.debian.org] nmu: netcdf_1:4.9.2-5 Added indication that 1067818 affects src:netcdf -- 1067818: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067818 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#1067818: nmu: netcdf_1:4.9.2-5

2024-03-27 Thread Andrey Rakhmatullin
Package: release.debian.org Severity: normal X-Debbugs-Cc: net...@packages.debian.org Control: affects -1 + src:netcdf User: release.debian@packages.debian.org Usertags: binnmu nmu netcdf_1:4.9.2-5 . armhf . unstable . -m "Rebuild for time_t" https://packages.debian.org/sid/libnetcdf19t64

Processed: nmu: mpi4py_3.1.5-5

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:mpi4py Bug #1067820 [release.debian.org] nmu: mpi4py_3.1.5-5 Added indication that 1067820 affects src:mpi4py -- 1067820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067820 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Bug#1067820: nmu: mpi4py_3.1.5-5

2024-03-27 Thread Andrey Rakhmatullin
Package: release.debian.org Severity: normal X-Debbugs-Cc: mpi...@packages.debian.org Control: affects -1 + src:mpi4py User: release.debian@packages.debian.org Usertags: binnmu nmu mpi4py_3.1.5-5 . ANY . unstable . -m "Rebuild for time_t" There is a FTBFS bug open (#1066449), but it built fin

Bug#1036884: transition: time64_t -> sphinxbase

2024-03-27 Thread Sebastian Ramacher
On 2024-03-26 13:56:26 +, Simon McVittie wrote: > I think binNMUs for packages involved in > https://release.debian.org/transitions/html/auto-sphinxbase.html > would be useful. If I'm reading correctly, that would unblock ffmpeg > on armel/armhf (or at least get some way towards it), and ffmpeg

Bug#1036884: libgpgme11t64 binNMUs

2024-03-27 Thread Sebastian Ramacher
On 2024-03-26 20:30:12 +0500, Andrey Rakhmatullin wrote: > The next good target for binNMUs that wasn't done yet (AFAICS) is > https://release.debian.org/transitions/html/auto-gpgme1.0.html Scheduled Cheers -- Sebastian Ramacher

Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1

2024-03-27 Thread Andreas Beckmann
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] In order to receive further upstream support (i.e. CVE fixes), we need to switch src:nvidia-graphics-drivers from the 525 series (EoL 12/2023) to the 535 series, a new L

Bug#1067065: marked as done (nmu: gringo_5.6.2-1)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 09:55:34 +0100 with message-id and subject line Re: Bug#1067065: nmu: gringo_5.6.2-1 has caused the Debian Bug report #1067065, regarding nmu: gringo_5.6.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#1067118: marked as done (nmu: hdf5_1.10.10+repack-3.1)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 09:56:30 +0100 with message-id and subject line Re: Bug#1067118: nmu: hdf5_1.10.10+repack-3.1 has caused the Debian Bug report #1067118, regarding nmu: hdf5_1.10.10+repack-3.1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1067120: marked as done (nmu: apache2_2.4.58-1)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 09:57:50 +0100 with message-id and subject line Re: Bug#1067120: nmu: apache2_2.4.58-1 has caused the Debian Bug report #1067120, regarding nmu: apache2_2.4.58-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1067812: marked as done (nmu: spatialite_5.1.0-3)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 09:59:53 +0100 with message-id and subject line Re: Bug#1067812: nmu: spatialite_5.1.0-3 has caused the Debian Bug report #1067812, regarding nmu: spatialite_5.1.0-3 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1067813: marked as done (nmu: spatialite_5.1.0-3)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 09:59:53 +0100 with message-id and subject line Re: Bug#1067812: nmu: spatialite_5.1.0-3 has caused the Debian Bug report #1067812, regarding nmu: spatialite_5.1.0-3 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1067818: marked as done (nmu: netcdf_1:4.9.2-5)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 10:05:50 +0100 with message-id and subject line Re: Bug#1067818: nmu: netcdf_1:4.9.2-5 has caused the Debian Bug report #1067818, regarding nmu: netcdf_1:4.9.2-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1067820: marked as done (nmu: mpi4py_3.1.5-5)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 10:06:29 +0100 with message-id and subject line Re: Bug#1067820: nmu: mpi4py_3.1.5-5 has caused the Debian Bug report #1067820, regarding nmu: mpi4py_3.1.5-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#1067729: marked as done (nmu: exim4_4.97-5)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 10:15:09 +0100 with message-id and subject line Re: Bug#1067729: nmu: exim4_4.97-5 has caused the Debian Bug report #1067729, regarding nmu: exim4_4.97-5 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#1067769: marked as done (nmu: libjcat_0.2.0-2+b1)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 10:16:53 +0100 with message-id and subject line Re: Bug#1067769: nmu: libjcat_0.2.0-2+b1 has caused the Debian Bug report #1067769, regarding nmu: libjcat_0.2.0-2+b1 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1067762: marked as done (nmu: xmlrpc-c_1.33.14-11)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 10:16:13 +0100 with message-id and subject line Re: Bug#1067762: nmu: xmlrpc-c_1.33.14-11 has caused the Debian Bug report #1067762, regarding nmu: xmlrpc-c_1.33.14-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1067840: nmu: gsound_1.0.3-3.2

2024-03-27 Thread Simon McVittie
Package: release.debian.org Severity: normal X-Debbugs-Cc: gso...@packages.debian.org Control: affects -1 + src:gsound User: release.debian@packages.debian.org Usertags: binnmu nmu gsound_1.0.3-3.2 . armhf . unstable . -m "rebuild against libcanberra0t64" This should unblock gnome-bluetooth3,

Processed: nmu: gsound_1.0.3-3.2

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:gsound Bug #1067840 [release.debian.org] nmu: gsound_1.0.3-3.2 Added indication that 1067840 affects src:gsound -- 1067840: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067840 Debian Bug Tracking System Contact ow...@bugs.debian.org with prob

Bug#1067842: transition: octave-9

2024-03-27 Thread Sébastien Villemot
Package: release.debian.org Severity: normal X-Debbugs-Cc: debian-oct...@lists.debian.org User: release.debian@packages.debian.org Usertags: transition Dear Release Team, Please schedule a transition for the latest major upstream version of Octave, version 9. All the arch:any Octave addons ne

Bug#1067840: marked as done (nmu: gsound_1.0.3-3.2)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 14:36:55 +0100 with message-id and subject line Re: Bug#1067840: nmu: gsound_1.0.3-3.2 has caused the Debian Bug report #1067840, regarding nmu: gsound_1.0.3-3.2 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1067843: bookworm-pu: package nvidia-open-gpu-kernel-modules/535.161.08-1~deb12u1

2024-03-27 Thread Andreas Beckmann
Package: release.debian.org Severity: normal Tags: bookworm User: release.debian@packages.debian.org Usertags: pu [ Reason ] We need to update src:nvidia-open-gpu-kernel-modules to a new upstream version to stay in sync with src:nvidia-graphics-drivers (for a matching firmware-nvidia-gsp upstr

Should I upload 0ad involved in wxwidgets3.2 migration?

2024-03-27 Thread Ludovic Rousseau
Hello Debian Release team, 0ad has a FTBFS bug #1064726. I have a new version with the fix ready for upload. But when trying to upload I get: - $ dupload --to debian-ssh *_source.changes --no dupload note: no announcement will be sent. Checking OpenPGP signatures before uploa

Re: Should I upload 0ad involved in wxwidgets3.2 migration?

2024-03-27 Thread Sebastian Ramacher
On 2024-03-27 15:51:22 +0100, Ludovic Rousseau wrote: > Hello Debian Release team, > > 0ad has a FTBFS bug #1064726. > I have a new version with the fix ready for upload. > > But when trying to upload I get: > - > $ dupload --to debian-ssh *_source.changes --no > dupload note:

Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf

2024-03-27 Thread Wookey
On 2024-03-26 22:28 +, Thorsten Glaser wrote: > I hacked that, and I tried to do armel and armhf as well but > dak stopped me, whereas mini-dak was not as strict. What was the actual problem with uploading the images you built? Just not having any corresponding source? Or something more compl

Bug#1067846: nmu: librist_0.2.10+dfsg-1

2024-03-27 Thread Andrey Rakhmatullin
Package: release.debian.org Severity: normal X-Debbugs-Cc: libr...@packages.debian.org Control: affects -1 + src:librist User: release.debian@packages.debian.org Usertags: binnmu nmu librist_0.2.10+dfsg-1 . armel armhf . unstable . -m "Rebuild for time_t" https://packages.debian.org/sid/rist-

Processed: nmu: librist_0.2.10+dfsg-1

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:librist Bug #1067846 [release.debian.org] nmu: librist_0.2.10+dfsg-1 Added indication that 1067846 affects src:librist -- 1067846: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067846 Debian Bug Tracking System Contact ow...@bugs.debian.org wi

Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf

2024-03-27 Thread Wookey
On 2024-03-27 15:27 +, Wookey wrote: > On 2024-03-26 22:28 +, Thorsten Glaser wrote: > > > I hacked that, and I tried to do armel and armhf as well but > > dak stopped me, whereas mini-dak was not as strict. > > What was the actual problem with uploading the images you built? Just > not h

Bug#1067852: nmu: gdal_3.8.4+dfsg-3

2024-03-27 Thread Bas Couwenberg
Package: release.debian.org Severity: normal X-Debbugs-Cc: g...@packages.debian.org Control: affects -1 + src:gdal User: release.debian@packages.debian.org Usertags: binnmu nmu gdal_3.8.4+dfsg-3 . ANY . unstable . -m "Rebuild with libfyba0t64" gdal needs to be built with libfyba-dev (>= 4.1.1

Processed: nmu: gdal_3.8.4+dfsg-3

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:gdal Bug #1067852 [release.debian.org] nmu: gdal_3.8.4+dfsg-3 Added indication that 1067852 affects src:gdal -- 1067852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem

Bug#1067856: nmu: castxml_0.6.3-1

2024-03-27 Thread Andrey Rakhmatullin
Package: release.debian.org Severity: normal X-Debbugs-Cc: cast...@packages.debian.org Control: affects -1 + src:castxml User: release.debian@packages.debian.org Usertags: binnmu nmu castxml_0.6.3-1 . amd64 arm64 armel armhf i386 ppc64el riscv64 s390x . unstable . -m "Rebuild for time_t" All

Processed: nmu: castxml_0.6.3-1

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:castxml Bug #1067856 [release.debian.org] nmu: castxml_0.6.3-1 Added indication that 1067856 affects src:castxml -- 1067856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067856 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#1067846: marked as done (nmu: librist_0.2.10+dfsg-1)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 19:50:52 +0100 with message-id and subject line Re: Bug#1067846: nmu: librist_0.2.10+dfsg-1 has caused the Debian Bug report #1067846, regarding nmu: librist_0.2.10+dfsg-1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1067856: marked as done (nmu: castxml_0.6.3-1)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 19:51:58 +0100 with message-id and subject line Re: Bug#1067856: nmu: castxml_0.6.3-1 has caused the Debian Bug report #1067856, regarding nmu: castxml_0.6.3-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1067852: marked as done (nmu: gdal_3.8.4+dfsg-3)

2024-03-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Mar 2024 19:54:54 +0100 with message-id and subject line Re: Bug#1067852: nmu: gdal_3.8.4+dfsg-3 has caused the Debian Bug report #1067852, regarding nmu: gdal_3.8.4+dfsg-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1

2024-03-27 Thread Adam D. Barratt
Control: tags -1 + confirmed On Wed, 2024-03-27 at 09:51 +0100, Andreas Beckmann wrote: > In order to receive further upstream support (i.e. CVE fixes), we > need > to switch src:nvidia-graphics-drivers from the 525 series (EoL > 12/2023) > to the 535 series, a new LTSB branch sufficient for the l

Processed: Re: Bug#1067821: bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed Bug #1067821 [release.debian.org] bookworm-pu: package nvidia-graphics-drivers/535.161.08-1~deb12u1 Added tag(s) confirmed. -- 1067821: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067821 Debian Bug Tracking System Contact ow...@bugs.debi

Bug#1067843: bookworm-pu: package nvidia-open-gpu-kernel-modules/535.161.08-1~deb12u1

2024-03-27 Thread Adam D. Barratt
Control: tags -1 + confirmed On Wed, 2024-03-27 at 14:43 +0100, Andreas Beckmann wrote: > We need to update src:nvidia-open-gpu-kernel-modules to a new > upstream > version to stay in sync with src:nvidia-graphics-drivers (for a > matching > firmware-nvidia-gsp upstream version) and to fix some CV

Processed: Re: Bug#1067843: bookworm-pu: package nvidia-open-gpu-kernel-modules/535.161.08-1~deb12u1

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + confirmed Bug #1067843 [release.debian.org] bookworm-pu: package nvidia-open-gpu-kernel-modules/535.161.08-1~deb12u1 Added tag(s) confirmed. -- 1067843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067843 Debian Bug Tracking System Contact ow...@bu

Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf

2024-03-27 Thread Thorsten Glaser
Hi Wookey, >OK, got those. but that's just binaries. It was the source changes I >was looking for (or did I misunderstand and you didn't actually make >any of those?), Yes, I did not make any source changes. These were the last binaries from before the t64 transition (I downloaded the .deb files

Bug#1063371: nmu: golang-github-tinylib-msgp

2024-03-27 Thread Mathias Gibbens
Control: retitle -1 nmu: golang-github-tinylib-msgp Control: affects -1 - src:golang-github-go-jose-go-jose I've backported a newer version of golang-github-go-jose-go-jose, which resolves the need for a binNMU of that package. A binNMU is still requested for golang-github-tinylib-msgp in boo

Processed: Re: nmu: golang-github-tinylib-msgp

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 nmu: golang-github-tinylib-msgp Bug #1063371 [release.debian.org] nmu: golang-github-go-jose-go-jose, golang-github-tinylib-msgp Changed Bug title to 'nmu: golang-github-tinylib-msgp' from 'nmu: golang-github-go-jose-go-jose, golang-github-tinylib-msgp'.

Bug#1067872: transition: netcdf

2024-03-27 Thread Bas Couwenberg
Package: release.debian.org Severity: normal X-Debbugs-Cc: net...@packages.debian.org Control: affects -1 + src:netcdf User: release.debian@packages.debian.org Usertags: transition There is no auto-netcdf tracker because libnetcdf19t64 already migrated to testing because it didn't build depen

Processed: transition: netcdf

2024-03-27 Thread Debian Bug Tracking System
Processing control commands: > affects -1 + src:netcdf Bug #1067872 [release.debian.org] transition: netcdf Added indication that 1067872 affects src:netcdf -- 1067872: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067872 Debian Bug Tracking System Contact ow...@bugs.debian.org with problem