Bug#1065469: marked as done (Can't upgrade: trying to overwrite '/usr/share/doc/qemu-system-common/system/arm/aspeed.html')

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 07:52:17 +
with message-id 
and subject line Bug#1065469: fixed in qemu 1:8.2.2+ds-2
has caused the Debian Bug report #1065469,
regarding Can't upgrade: trying to overwrite 
'/usr/share/doc/qemu-system-common/system/arm/aspeed.html'
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.)


-- 
1065469: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065469
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: qemu-system-data
Version: 1:8.2.2+ds-1
Severity: serious


Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive /var/cache/apt/archives/qemu-system-
data_1%3a8.2.2+ds-1_all.deb (--unpack):
 trying to overwrite '/usr/share/doc/qemu-system-
common/system/arm/aspeed.html', which is also in package qemu-system-common
1:8.2.1+ds-2


-- 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.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

-- debconf-show failed
--- End Message ---
--- Begin Message ---
Source: qemu
Source-Version: 1:8.2.2+ds-2
Done: Michael Tokarev 

We believe that the bug you reported is fixed in the latest version of
qemu, 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.
Michael Tokarev  (supplier of updated qemu 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: Tue, 05 Mar 2024 10:27:47 +0300
Source: qemu
Architecture: source
Version: 1:8.2.2+ds-2
Distribution: unstable
Urgency: medium
Maintainer: Debian QEMU Team 
Changed-By: Michael Tokarev 
Closes: 1065469
Changes:
 qemu (1:8.2.2+ds-2) unstable; urgency=medium
 .
   * d/control: fix qemu version in Breaks: to include the missing epoch
 (Closes: #1065469)
   * d/rules: remove x32 from qemu-user host arch list and add it to tools
Checksums-Sha1:
 79f6c76f21353cc3aaa1ed30105724c34bf8121d 8343 qemu_8.2.2+ds-2.dsc
 530a224d72cd718ca8863f06c2ee0b89c626f524 109524 qemu_8.2.2+ds-2.debian.tar.xz
 668194cd575266db823d2999ee1253cebc9f42c1 8087 qemu_8.2.2+ds-2_source.buildinfo
Checksums-Sha256:
 4dc9eae77a35d4dbdcf9e47f1ed08d50c86de876af75b1f4b6ab524d0fa44ea0 8343 
qemu_8.2.2+ds-2.dsc
 d706da4ff3113239dfa6ac5abd8ad9db74b151d26ae0ba09de41388a55ebd4e9 109524 
qemu_8.2.2+ds-2.debian.tar.xz
 279b89330207076fd7210fe1f65b11e55ef26691839e5bcec4d4cbcd4f692e14 8087 
qemu_8.2.2+ds-2_source.buildinfo
Files:
 0cdbc59ffbaa7590054e3df48052f4e5 8343 otherosfs optional qemu_8.2.2+ds-2.dsc
 a91fbfa64dfc97cc24988e9089c95036 109524 otherosfs optional 
qemu_8.2.2+ds-2.debian.tar.xz
 841a5997f5ec0846647c6dcb835c0e46 8087 otherosfs optional 
qemu_8.2.2+ds-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQFDBAEBCgAtFiEEe3O61ovnosKJMUsicBtPaxppPlkFAmXmyYcPHG1qdEB0bHMu
bXNrLnJ1AAoJEHAbT2saaT5ZE4sIAJ//q/vIQ9wG7/BPwLFyP9kgYL6s8DgEelyS
88esjIr6RCZJe8RtgouIuVvvaXt0kt87QroDkJ5/GWYeL+iKEaMzX+7DAO89NJ4W
NvulxFeBfPeY4vo5flv7pw8r1jCu8HrzLbyyq6anN7Ke7ksBQJ17NK/V9NMtQsD6
R0cQLPpMMNO82I5KwYj3wxZiGRQOcu3FRShjpw/SSP1QuUV79VaIi5UrYE3D5R7B
DFW+evacO7mpb5knEP5xRpiqlXAUPoxiu/qpj/tDZNu0K9kgoJrcFag5jUITO+vp
dGvje1T0HWbVkWtkzb+MuAxdsPvdZAtxpA+dEvfxPvenHXced2U=
=5vPa
-END PGP SIGNATURE-



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

Processed: Re: Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1061902 [src:consolekit2] consolekit2: NMU diff for 64-bit time_t 
transition
Severity set to 'normal' from 'serious'

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

Bug#1065469: Can't upgrade: trying to overwrite '/usr/share/doc/qemu-system-common/system/arm/aspeed.html'

[Andrey Rahmatullin]

On Tue, Mar 05, 2024 at 09:22:37AM +0300, Michael Tokarev wrote:
> > Package: qemu-system-data
> > Version: 1:8.2.2+ds-1
> > Severity: serious
> > 
> > 
> > Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
> > Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
> > dpkg: error processing archive /var/cache/apt/archives/qemu-system-
> > data_1%3a8.2.2+ds-1_all.deb (--unpack):
> >   trying to overwrite '/usr/share/doc/qemu-system-
> > common/system/arm/aspeed.html', which is also in package qemu-system-common
> > 1:8.2.1+ds-2
> 
> Hmm.
> 
> In 8.2.2 I moved common docs from arch-dependent package qemu-system-common
> to arch-indep package qemu-system-data.  Current control fields for the
> latter, among others, has:
> 
>  Breaks: qemu-system-common (<< 8.2.1+ds-3~),
>  Replaces: qemu-system-common (<< 8.2.1+ds-3~),
> 
> so... what's going on here?  q-s-d 8.2.2 replaces files from q-s-c 8.2.1
Can it be simply because the package has an epoch and relations should
include it?

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#1061902: consolekit2: NMU diff for 64-bit time_t transition

[Mark Hindley]

Control: severity -1 normal

On Tue, Feb 06, 2024 at 05:43:41PM +, Mark Hindley wrote:
> Whilst I am not an expert on this transition or the abi-compliance-checker, a
> quick look at the logs[1] suggests this is a tool configuration issue and
> src:consolekit2 may not require t64 migration.
> 
> Can you clarify?

I would appreciate some help here. Your patch FTBFS and I need to be convinced
it is actually required before spending time on it.

In the meantime, downgrading severity to prevent autoremoval.

Thanks

Mark

Bug#1065469: Can't upgrade: trying to overwrite '/usr/share/doc/qemu-system-common/system/arm/aspeed.html'

[Michael Tokarev]

05.03.2024 10:03, Andrey Rahmatullin wrote:


  Breaks: qemu-system-common (<< 8.2.1+ds-3~),
  Replaces: qemu-system-common (<< 8.2.1+ds-3~),

so... what's going on here?  q-s-d 8.2.2 replaces files from q-s-c 8.2.1

Can it be simply because the package has an epoch and relations should
include it?


AAARGH!  Yes, you're exactly right.  Sigh :)

Fixing it now, thank you!

/mjt

Bug#1065461: marked as done (libreoffice-common: disabling libreoffice-evolution has moved evolocal.odb to libreoffice-common)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 06:47:09 +
with message-id 
and subject line Bug#1065461: fixed in libreoffice 4:24.2.1-4
has caused the Debian Bug report #1065461,
regarding libreoffice-common: disabling libreoffice-evolution has moved 
evolocal.odb to libreoffice-common
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.)


-- 
1065461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-common
Version: 4:24.2.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libreoffice-common_4%3a24.2.1-3_all.deb ...
  Unpacking libreoffice-common (4:24.2.1-3) over (4:24.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb (--unpack):
   trying to overwrite '/usr/lib/libreoffice/presets/database/evolocal.odb', 
which is also in package libreoffice-evolution 4:24.2.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or 
directory
  rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or 
directory
  rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or 
directory
  rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
  rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
  Errors were encountered while processing:
   /var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb

I'm not sure whether Breaks+Replaces are the correct solution here, or
whether -common should rather not ship the file regardless of (not)
building -evolution ...
If you add B+R now, you will also need to add them in the opposite
direction once -evolutions gets reenabled.


cheers,

Andreas


libreoffice-evolution=4:24.2.0-1_libreoffice-common=4:24.2.1-3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 4:24.2.1-4
Done: Rene Engelhard 

We believe that the bug you reported is fixed in the latest version of
libreoffice, 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.
Rene Engelhard  (supplier of updated libreoffice 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: Tue, 05 Mar 2024 07:05:44 +0100
Source: libreoffice
Architecture: source
Version: 4:24.2.1-4
Distribution: unstable
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 1065461
Changes:
 libreoffice (4:24.2.1-4) unstable; urgency=medium
 .
   * debian/rules:
 - re-enable libreoffice-evolution; rm evolocal.odb if evolution is
   disabled, though (otherwise ends up in -common) (closes: #1065461)
   * debian/control.evolution.in:
 - add Replaces: libreoffice-common (= 4:24.2.1-3)
Checksums-Sha1:
 3dc2f491773d19f10d8bd29de4db339af0ae89d3 36522 libreoffice_24.2.1-4.dsc
 80f6e8d2829ce2cc234c7c1ae04a04220718b114 24868604 
libreoffice_24.2.1-4.debian.tar.xz
 bf034f4d6d0846be5e6a1baeaf5aff0afc3aa1bf 37040 
libreoffice_24.2.1-4_source.buildinfo
Checksums-Sha256:
 8e6d52169bb6f9fd6dc4678678ecda0f3e95e444a7166207a94a6a4ea657e22f 36522 
libreoffice_24.2.1-4.dsc
 80c4a8623ecb5dd1982cf0d5fe22eccbcd327938b20ad12564f028ba2252dc39 24868604 
libreoffice_24.2.1-4.debian.tar.xz
 45f37442b5064d81c1e2a2ed24381fa398c50441ff253a0d4571dd382a25dcef 37040 
libreoffice_24.2.1-4_source.buildinfo
Files:
 24c1cfc494ac13ed1837757904333c43 36522 editors optional 
libreoffice_24.2.1-4.dsc
 7faa1310fe844ba50689c43a1ee6efed 24868604 editors optional 

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Paul Gevers]

Hi Andreas,

Thanks for the upload.

On 04-03-2024 12:26 p.m., Andreas Beckmann wrote:
Control: forwarded -1 
https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2397


On 03/03/2024 20.52, Paul Gevers wrote:

Source: spirv-llvm-translator-14
Version: 14.0.0-10


In the upstream report you mention it's the same across all versions and 
yesterday we had the same problem with -15. Will you fix the other 
versions too? Do you want me to clone this bug for that?


Paul


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Bastian Blank]

On Mon, Mar 04, 2024 at 11:04:23PM +0100, Bastian Blank wrote:
> At least to show where it breaks.

And I actually tried it and can not show the expected breakage from
missing /usr/include in the search path.  gcc-13-cross builds fine with
only linux-libc-dev/6.7.7-1.

| -rw-r--r-- 1 bastian bastian 38157 Mar  5 06:40 
../gcc-13-cross_14_amd64.changes

Bastian

-- 
You're too beautiful to ignore.  Too much woman.
-- Kirk to Yeoman Rand, "The Enemy Within", stardate unknown

Bug#1065469: Can't upgrade: trying to overwrite '/usr/share/doc/qemu-system-common/system/arm/aspeed.html'

[Michael Tokarev]

05.03.2024 09:10, Andrey Rahmatullin wrote:

Package: qemu-system-data
Version: 1:8.2.2+ds-1
Severity: serious


Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive /var/cache/apt/archives/qemu-system-
data_1%3a8.2.2+ds-1_all.deb (--unpack):
  trying to overwrite '/usr/share/doc/qemu-system-
common/system/arm/aspeed.html', which is also in package qemu-system-common
1:8.2.1+ds-2


Hmm.

In 8.2.2 I moved common docs from arch-dependent package qemu-system-common
to arch-indep package qemu-system-data.  Current control fields for the
latter, among others, has:

 Breaks: qemu-system-common (<< 8.2.1+ds-3~),
 Replaces: qemu-system-common (<< 8.2.1+ds-3~),

so... what's going on here?  q-s-d 8.2.2 replaces files from q-s-c 8.2.1

Yes, the version it replaces is a bit off (I planned to upload another
8.2.1 but uploaded 8.2.2 instead), but it should work.

WTF?

/mjt

Bug#1065469: Can't upgrade: trying to overwrite '/usr/share/doc/qemu-system-common/system/arm/aspeed.html'

[Andrey Rahmatullin]

Package: qemu-system-data
Version: 1:8.2.2+ds-1
Severity: serious


Preparing to unpack .../qemu-system-data_1%3a8.2.2+ds-1_all.deb ...
Unpacking qemu-system-data (1:8.2.2+ds-1) over (1:8.2.1+ds-2) ...
dpkg: error processing archive /var/cache/apt/archives/qemu-system-
data_1%3a8.2.2+ds-1_all.deb (--unpack):
 trying to overwrite '/usr/share/doc/qemu-system-
common/system/arm/aspeed.html', which is also in package qemu-system-common
1:8.2.1+ds-2


-- 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.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

-- debconf-show failed

Bug#1065461: marked as pending in libreoffice

[Rene Engelhard]

Control: tag -1 pending

Hello,

Bug #1065461 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/6bf7040a13e3693e23a356f5aeff0121620c2ac0


rm -f $(PKGDIR)-common/$(OODIR)/presets/database/evolocal.odb id 
ENABLE_EVOAB!=y (closes: #1065461)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1065461

Processed: Bug#1065461 marked as pending in libreoffice

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1065461 [libreoffice-common] libreoffice-common: disabling 
libreoffice-evolution has moved evolocal.odb to libreoffice-common
Added tag(s) pending.

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

Bug#1065461: libreoffice-common: disabling libreoffice-evolution has moved evolocal.odb to libreoffice-common

[Rene Engelhard]

Hi,

Am 05.03.24 um 00:47 schrieb Andreas Beckmann:

   Preparing to unpack .../libreoffice-common_4%3a24.2.1-3_all.deb ...
   Unpacking libreoffice-common (4:24.2.1-3) over (4:24.2.0-1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb (--unpack):
trying to overwrite '/usr/lib/libreoffice/presets/database/evolocal.odb', 
which is also in package libreoffice-evolution 4:24.2.0-1
   dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
   rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file 
or directory
   rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or 
directory
   rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or 
directory
   rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
   rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
   Errors were encountered while processing:
/var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb

I'm not sure whether Breaks+Replaces are the correct solution here, or
whether -common should rather not ship the file regardless of (not)
building -evolution ...


The latter, imho.

ifeq "$(ENABLE_EVO2)" "y"
    mkdir -p $(PKGDIR)-evolution/$(OODIR)/presets/database
    mkdir -p $(PKGDIR)-evolution/$(OODIR)/share/registry
    mv $(PKGDIR)-common/$(OODIR)/presets/database/evolocal.odb \
    $(PKGDIR)-evolution/$(OODIR)/presets/database
else
    rm -f $(PKGDIR)-common/$(OODIR)/presets/database/evolocal.odb
endif

Added the else part just now.


If you add B+R now, you will also need to add them in the opposite
direction once -evolutions gets reenabled.


libphonenumber is fixed now, so I can re-enable it now and not have it 
blocking builds.



But I need to do the Replaces: libreoffice-common in -evolution anyways now?


Regards,


Rene

Bug#1065395: marked as done (spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space)

[Debian Bug Tracking System]

Your message dated Tue, 05 Mar 2024 04:35:30 +
with message-id 
and subject line Bug#1065395: fixed in spirv-llvm-translator-14 14.0.0-11
has caused the Debian Bug report #1065395,
regarding spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of 
disk space
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.)


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

Source: spirv-llvm-translator-14
Version: 14.0.0-10
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: issue

Dear maintainers,

Since a couple of days, our workers on s390x are dying because some test
is filling up all disk space. Several days ago, I wrongly suspected 
src:fenics-dolfinx (bug #1064995) and added it to our reject-list. It 
didn't solve the issue, so today I spend more time on finding the 
culprit. Basically every spike above 40% in the graph [1] is a moment 
that we see issues like:


Feb 28 05:38:18 ci-worker-s390x-01 debci[1738391]: gzip:
/tmp/debci-worker-43383540-cNnbLE372K/autopkgtest-incoming/testing/s390x/f/fenics-dolfinx/43383540/log.gz: 


No space left on device
Feb 28 05:38:18 ci-worker-s390x-01 debci[1424101]: E: Test for package
fenics-dolfinx produced no exit code, aborting

One of the suspects started to be spirv-llvm-translator-14, so I ran its 
autopkgtest manually, while logging disk use every 10 seconds (I started 
slightly delayed because I monitored the wrong partition first). As you 
can see below, during the test it grows from 17 GB (at the end) to its 
peak at 179 GB. That's not acceptable on our infrastructure. One file I 
happened to spot on the way was 
build/test/test_output/DebugInfo/Generic/Output/two-cus-from-same-file.ll.tmp:

-rw-r--r-- 1 root root  41G Mar  3 19:18 two-cus-from-same-file.ll.tmp

I have added spirv-llvm-translator-14 to our reject-list on s390x.

As this seems to be a rather new issue, I'm wondering if it's due to:
* Add build-needed autopkgtest for spirv-headers compat check.

Or maybe something in the toolchain that broke on s390x?

Paul

[1]
https://ci.debian.net/munin/ci-worker-s390x-01/ci-worker-s390x-01/df.html

/dev/mapper/3600507630affd250004a  196G   40G  146G  22% 
/scratch
/dev/mapper/3600507630affd250004a  196G   49G  138G  27% 
/scratch
/dev/mapper/3600507630affd250004a  196G   57G  130G  31% 
/scratch
/dev/mapper/3600507630affd250004a  196G   65G  122G  35% 
/scratch
/dev/mapper/3600507630affd250004a  196G   66G  121G  36% 
/scratch
/dev/mapper/3600507630affd250004a  196G   67G  120G  36% 
/scratch
/dev/mapper/3600507630affd250004a  196G   70G  117G  38% 
/scratch
/dev/mapper/3600507630affd250004a  196G   73G  114G  40% 
/scratch
/dev/mapper/3600507630affd250004a  196G   76G  111G  41% 
/scratch
/dev/mapper/3600507630affd250004a  196G   79G  108G  43% 
/scratch
/dev/mapper/3600507630affd250004a  196G   83G  104G  45% 
/scratch
/dev/mapper/3600507630affd250004a  196G   85G  101G  46% 
/scratch
/dev/mapper/3600507630affd250004a  196G   88G   98G  48% 
/scratch
/dev/mapper/3600507630affd250004a  196G   92G   95G  50% 
/scratch
/dev/mapper/3600507630affd250004a  196G   95G   92G  51% 
/scratch
/dev/mapper/3600507630affd250004a  196G   98G   89G  53% 
/scratch
/dev/mapper/3600507630affd250004a  196G  101G   86G  54% 
/scratch
/dev/mapper/3600507630affd250004a  196G  104G   83G  56% 
/scratch
/dev/mapper/3600507630affd250004a  196G  107G   80G  58% 
/scratch
/dev/mapper/3600507630affd250004a  196G   65G  122G  35% 
/scratch
/dev/mapper/3600507630affd250004a  196G   65G  122G  35% 
/scratch
/dev/mapper/3600507630affd250004a  196G   66G  121G  36% 
/scratch
/dev/mapper/3600507630affd250004a  196G   68G  118G  37% 
/scratch
/dev/mapper/3600507630affd250004a  196G   72G  115G  39% 
/scratch
/dev/mapper/3600507630affd250004a  196G   75G  112G  41% 
/scratch
/dev/mapper/3600507630affd250004a  196G   78G  109G  42% 
/scratch
/dev/mapper/3600507630affd250004a  196G   81G  106G  44% 
/scratch
/dev/mapper/3600507630affd250004a  196G   85G  102G  46% 
/scratch
/dev/mapper/3600507630affd250004a  196G   87G   99G  47% 
/scratch
/dev/mapper/3600507630affd250004a  196G   90G   96G  49% 

Processed: Re: Breaks autopkgtest suite of systemd and multipath-tools

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1064981 [src:lvm2] Breaks autopkgtest suite of systemd and multipath-tools
Severity set to 'important' from 'serious'

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

Bug#1064981: Breaks autopkgtest suite of systemd and multipath-tools

[Michael Biebl]

Control: severity -1 important


Hi

On Wed, 28 Feb 2024 18:49:00 +0100 Michael Biebl  wrote:

Source: lvm2
Version: 2.03.22-1
Severity: serious

Hi,

filing this issue with severity RC to prevent testing migration.

It appears the new LVM release breaks both systemd and multipath-tools's
autopkgtest suite

https://ci.debian.net/packages/m/multipath-tools/testing/amd64/43382441/
https://github.com/systemd/systemd/issues/31517


After further investigation, the failure in multipath-tools turned out 
to be a result of

https://salsa.debian.org/linux-blocks-team/multipath-tools/-/blob/master/debian/patches/0002-11-dm-mpath-fix-DM_UDEV_RULES_VSN-check.patch?ref_type=heads
So far this patch had been necessary, since lvm2 itself had modified the 
udev rules downstream, but no longer does that thankfully with the 
latest update.
See the remarks in 
https://github.com/systemd/systemd/issues/31517#issuecomment-1971788035


Chris updated multipath-tools accordingly:
https://salsa.debian.org/linux-blocks-team/multipath-tools/-/commit/902a13b2c628d2cfde74cb78fd1ba4425af3d7d4
and uploaded it as 0.9.7-6. With that, multipath-tools and systemd's 
autopkgtest are unbroken again.


I'm still keeping the bug report open, as you might consider adding a 
versioned breaks against multipath-tools to dmsetup.

Downgrading to non-RC now though.

Regards,
Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1062218: libaio: NMU diff for 64-bit time_t transition

[Guillem Jover]

Hi!

On Mon, 2024-03-04 at 13:51:19 +0100, Guillem Jover wrote:
> I've got all the upstream changes now ready, except that there's still
> one test case failing, something wrong with the sigset_t type. I've run
> out of time trying to track this down, but I've pushed what I have on
> the pu/time64 branch, and will continue later today.

In the end this looks like Linux has a broken io_pgetevents_tiem64()
syscall on 32-bit userland running on 64-bit kernels. The syscall
works fine on 32-bit kernels though. I've disabled this for now given
that the time_t usage is for relative timeouts anyway, and because
the library ABI now will use proper types, and the underlying
implementation can be fixed after a while once I've looked into
fixing the compat syscall in Linux.

I'm preparing an upload right now with a SONAME bump.

Thanks,
Guillem

Processed: Re: tracker-miners: bmp-basic-1 test fails on big-endian

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1064548 [src:tracker-miners] tracker-miners: bmp-basic-1 test fails on 
big-endian
Severity set to 'important' from 'serious'

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

Bug#1064548: tracker-miners: bmp-basic-1 test fails on big-endian

[Jeremy Bícha]

Control: severity -1 important

I have skipped this test on big-endian, but this issue still ought to
be investigated.

Also, we already are skipping audio tests on these architectures.

Thank you,
Jeremy Bícha

Processed: tracker: 3.7 failing autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:tracker-miners
Bug #1065464 [src:tracker] tracker: 3.7 failing autopkgtest
Added indication that 1065464 affects src:tracker-miners

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

Bug#1065464: tracker: 3.7 failing autopkgtest

[Jeremy Bícha]

Source: tracker
Version: 3.5.3-1
Severity: serious
Tags: experimental
Control: affects -1 src:tracker-miners

I believe I have fixed all the blocking issues to update tracker and
tracker-miners in Unstable except for its failing autopkgtest. Its
autopkgtest has apparently been failing since at least 3.5.3.

I am confused because the autopkgtest appears to be nearly identical
to what is run during the build by dh_auto_test which does pass.

https://ci.debian.net/packages/t/tracker/unstable/amd64/

https://salsa.debian.org/gnome-team/tracker/-/pipelines

Thank you,
Jeremy Bícha

Bug#1065461: libreoffice-common: disabling libreoffice-evolution has moved evolocal.odb to libreoffice-common

[Andreas Beckmann]

Package: libreoffice-common
Version: 4:24.2.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts fileconflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../libreoffice-common_4%3a24.2.1-3_all.deb ...
  Unpacking libreoffice-common (4:24.2.1-3) over (4:24.2.0-1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb (--unpack):
   trying to overwrite '/usr/lib/libreoffice/presets/database/evolocal.odb', 
which is also in package libreoffice-evolution 4:24.2.0-1
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  rmdir: failed to remove '/var/lib/libreoffice/share/prereg/': No such file or 
directory
  rmdir: failed to remove '/var/lib/libreoffice/share/': No such file or 
directory
  rmdir: failed to remove '/var/lib/libreoffice/program/': No such file or 
directory
  rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
  rmdir: failed to remove '/var/lib/libreoffice': No such file or directory
  Errors were encountered while processing:
   /var/cache/apt/archives/libreoffice-common_4%3a24.2.1-3_all.deb

I'm not sure whether Breaks+Replaces are the correct solution here, or
whether -common should rather not ship the file regardless of (not)
building -evolution ...
If you add B+R now, you will also need to add them in the opposite
direction once -evolutions gets reenabled.


cheers,

Andreas


libreoffice-evolution=4:24.2.0-1_libreoffice-common=4:24.2.1-3.log.gz
Description: application/gzip

Bug#1065460: uwsgi: the package fails to build from source due to missing 'plugins/rack_ruby32'

[Vladimir Petko]

Source: uwsgi
Version: 2.0.22-4
Severity: serious
Tags: ftbfs

Dear Maintainer,

The package fails to build in sid chroot with the following error:

--
*** uWSGI building and linking plugin plugins/rack_ruby32 ***
Error: unable to find directory 'plugins/rack_ruby32'
make: *** [debian/rules:429: debian/stamp-uwsgi-plugin-rack-ruby3.2] Error 1
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2

Build finished at 2024-03-04T23:36:17Z

Finished





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

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

Bug#1065457: openzwave: FTBFS: dh_install: error: missing files, aborting

[Sebastian Ramacher]

Source: openzwave
Version: 1.6.1914+ds-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org, bdr...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=openzwave=amd64=1.6.1914%2Bds-1.1=1709295262=0

# install docs in /usr/share/doc/openzwave/, not openzwave-VERSION
install -d debian/libopenzwave-doc/usr/share/doc
make[1]: Leaving directory '/<>'
   dh_install -a
install -m0755 -d debian/libopenzwave1.6t64//etc/openzwave
cp --reflink=auto -a debian/tmp/etc/openzwave/2gig 
debian/tmp/etc/openzwave/BeNext debian/tmp/etc/openzwave/Localization.xml 
debian/tmp/etc/openzwave/Localization.xsd 
debian/tmp/etc/openzwave/NotificationCCTypes.xml 
debian/tmp/etc/openzwave/NotificationCCTypes.xsd 
debian/tmp/etc/openzwave/SensorMultiLevelCCTypes.xml 
debian/tmp/etc/openzwave/SensorMultiLevelCCTypes.xsd 
debian/tmp/etc/openzwave/abus debian/tmp/etc/openzwave/act 
debian/tmp/etc/openzwave/aeotec debian/tmp/etc/openzwave/airlinemechanical 
debian/tmp/etc/openzwave/alfred debian/tmp/etc/openzwave/assa_abloy 
debian/tmp/etc/openzwave/august debian/tmp/etc/openzwave/buffalo 
debian/tmp/etc/openzwave/building36 debian/tmp/etc/openzwave/comfort 
debian/tmp/etc/openzwave/config-template.xml 
debian/tmp/etc/openzwave/connecthome debian/tmp/etc/openzwave/cooper 
debian/tmp/etc/openzwave/danfoss debian/tmp/etc/openzwave/device_classes.xml 
debian/tmp/etc/openzwave/device_classes.xsd 
debian/tmp/etc/openzwave/device_configuration.xsd 
debian/tmp/etc/openzwave/devolo debian/tmp/etc/openzwave/diehlcontrols 
debian/tmp/etc/openzwave/dlink debian/tmp/etc/openzwave/dome 
debian/tmp/etc/openzwave/domitech debian/tmp/etc/openzwave/domux 
debian/tmp/etc/openzwave/dragontech debian/tmp/etc/openzwave/duco 
debian/tmp/etc/openzwave/duwi debian/tmp/etc/openzwave/ecodim 
debian/tmp/etc/openzwave/ecolink debian/tmp/etc/openzwave/econet 
debian/tmp/etc/openzwave/electronicsolutions debian/tmp/etc/openzwave/enblink 
debian/tmp/etc/openzwave/enerwave debian/tmp/etc/openzwave/eurotronic 
debian/tmp/etc/openzwave/everspring debian/tmp/etc/openzwave/everspringct 
debian/tmp/etc/openzwave/evolve debian/tmp/etc/openzwave/fakro 
debian/tmp/etc/openzwave/fibaro debian/tmp/etc/openzwave/firstalert 
debian/tmp/etc/openzwave/followgood debian/tmp/etc/openzwave/forest 
debian/tmp/etc/openzwave/fortrezz debian/tmp/etc/openzwave/frostdale 
debian/tmp/etc/openzwave/ge debian/tmp/etc/openzwave/gocontrol 
debian/tmp/etc/openzwave/goodway debian/tmp/etc/openzwave/gr 
debian/tmp/etc/openzwave/graber debian/tmp/etc/openzwave/greenwave 
debian/tmp/etc/openzwave/guardtec debian/tmp/etc/openzwave/hab 
debian/tmp/etc/openzwave/hank debian/tmp/etc/openzwave/heiman 
debian/tmp/etc/openzwave/heltun debian/tmp/etc/openzwave/homeseer 
debian/tmp/etc/openzwave/honeywell debian/tmp/etc/openzwave/horstmann 
debian/tmp/etc/openzwave/icare debian/tmp/etc/openzwave/idlock 
debian/tmp/etc/openzwave/images debian/tmp/etc/openzwave/ingersoll 
debian/tmp/etc/openzwave/inovelli debian/tmp/etc/openzwave/intermatic 
debian/tmp/etc/openzwave/iris debian/tmp/etc/openzwave/iwatsu 
debian/tmp/etc/openzwave/jasco debian/tmp/etc/openzwave/kaipule 
debian/tmp/etc/openzwave/kwikset debian/tmp/etc/openzwave/leviton 
debian/tmp/etc/openzwave/linear debian/tmp/etc/openzwave/logicsoft 
debian/tmp/etc/openzwave/manufacturer_specific.xml 
debian/tmp/etc/openzwave/manufacturer_specific.xsd 
debian/tmp/etc/openzwave/mcohome debian/tmp/etc/openzwave/merten 
debian/tmp/etc/openzwave/miyakawaelectric debian/tmp/etc/openzwave/namron 
debian/tmp/etc/openzwave/nei debian/tmp/etc/openzwave/nexia 
debian/tmp/etc/openzwave/nodon debian/tmp/etc/openzwave/northq 
debian/tmp/etc/openzwave/oomi debian/tmp/etc/openzwave/options.xml 
debian/tmp/etc/openzwave/options.xsd debian/tmp/etc/openzwave/permundo 
debian/tmp/etc/openzwave/philio debian/tmp/etc/openzwave/polycontrol 
debian/tmp/etc/openzwave/popp debian/tmp/etc/openzwave/prowell 
debian/tmp/etc/openzwave/q-light debian/tmp/etc/openzwave/qees 
debian/tmp/etc/openzwave/qolsys debian/tmp/etc/openzwave/qubino 
debian/tmp/etc/openzwave/quby debian/tmp/etc/openzwave/rcs 
debian/tmp/etc/openzwave/remotec debian/tmp/etc/openzwave/ring 
debian/tmp/etc/openzwave/schlage debian/tmp/etc/openzwave/schlagelink 
debian/tmp/etc/openzwave/sensative debian/tmp/etc/openzwave/sercomm 
debian/tmp/etc/openzwave/shenzen_neo debian/tmp/etc/openzwave/shenzen_saykey 
debian/tmp/etc/openzwave/simon debian/tmp/etc/openzwave/smartthings 
debian/tmp/etc/openzwave/somfy debian/tmp/etc/openzwave/steinel 
debian/tmp/etc/openzwave/stelpro debian/tmp/etc/openzwave/sunricher 
debian/tmp/etc/openzwave/swiid debian/tmp/etc/openzwave/technisat 
debian/tmp/etc/openzwave/telldus debian/tmp/etc/openzwave/there 
debian/tmp/etc/openzwave/thermofloor debian/tmp/etc/openzwave/trane 
debian/tmp/etc/openzwave/vera debian/tmp/etc/openzwave/vision 
debian/tmp/etc/openzwave/vitrum 

Processed: tagging 1064128

[Debian Bug Tracking System]

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

> tags 1064128 + ftbfs
Bug #1064128 [liquidsoap] liquidsoap: FTBFS: Error: Unbound module Pcre
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Processed: closing 1056522

[Debian Bug Tracking System]

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

> close 1056522 13.7.0-1
Bug #1056522 [src:rich] rich's autopkg tests fail with Python 3.12
Marked as fixed in versions rich/13.7.0-1.
Bug #1056522 [src:rich] rich's autopkg tests fail with Python 3.12
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1058314

[Debian Bug Tracking System]

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

> close 1058314 13.7.0-1
Bug #1058314 [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Marked as fixed in versions rich/13.7.0-1.
Bug #1058314 [src:rich] rich: FTBFS: dh_auto_test: error: pybuild --test 
--test-pytest -i python{version} -p "3.12 3.11" returned exit code 13
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1064563: marked as done (libstd-rust-1.70 has an undeclared file conflict)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 22:04:00 +
with message-id 
and subject line Bug#1064563: fixed in rustc-web 1.70.0+dfsg1-7~deb12u2
has caused the Debian Bug report #1064563,
regarding libstd-rust-1.70 has an undeclared file conflict
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.)


-- 
1064563: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064563
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libstd-rust-1.70
Version: 1.70.0+dfsg1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libstd-rust-web-1.70

libstd-rust-1.70 has an undeclared file conflict. This may result in an
unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/librustc_driver-fccd0c47598ec70b.so
 * /usr/lib/x86_64-linux-gnu/libstd-5aee28526a69a514.so
 * /usr/lib/x86_64-linux-gnu/libtest-ce8cb46549a60304.so
are contained in the packages
 * libstd-rust-1.70/1.70.0+dfsg1-7 as present in trixie|unstable
 * libstd-rust-web-1.70/1.70.0+dfsg1-7~deb12u1 as present in 
bookworm-proposed-updates

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: rustc-web
Source-Version: 1.70.0+dfsg1-7~deb12u2
Done: Andres Salomon 

We believe that the bug you reported is fixed in the latest version of
rustc-web, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andres Salomon  (supplier of updated rustc-web 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 07:23:15 +
Source: rustc-web
Architecture: source
Version: 1.70.0+dfsg1-7~deb12u2
Distribution: bookworm
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Andres Salomon 
Closes: 1064562 1064563
Changes:
 rustc-web (1.70.0+dfsg1-7~deb12u2) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Increase allowed test failures on armhf and ppc64el to fix FTBFS.
   * Provide Conflicts/Replaces for rust*-mozilla*, which could still be
 installed from oldstable (closes: #1064562).
   * Add Provides/Conflicts/Replaces for libstd-rust-1.70 (closes: #1064563).
Checksums-Sha1:
 1f45d0901c511971208228c2c37933df3c799169 3645 
rustc-web_1.70.0+dfsg1-7~deb12u2.dsc
 42a1f0bb22ac96de75003788e8b093b6f929852a 101752 
rustc-web_1.70.0+dfsg1-7~deb12u2.debian.tar.xz
 8bca1531b87b35a277a82df3334388a400a038f8 8937 
rustc-web_1.70.0+dfsg1-7~deb12u2_source.buildinfo
Checksums-Sha256:
 18ebc3aef9516a44f11e4bcd17246bd65dc69a16af38df74f4a23a29381ef1c4 3645 
rustc-web_1.70.0+dfsg1-7~deb12u2.dsc
 c9bcf26e3e2cce86d9736c1789fbb9e3a73f6a0c1105dcb91c20ca7b97c423ad 101752 
rustc-web_1.70.0+dfsg1-7~deb12u2.debian.tar.xz
 bcbda4945d0440ba5d5b619dd3622a90b1466ef005854cfd3ad916ce2a34cb75 8937 
rustc-web_1.70.0+dfsg1-7~deb12u2_source.buildinfo
Files:
 03a80f6310e55cdf66731344dd2034f4 3645 devel optional 
rustc-web_1.70.0+dfsg1-7~deb12u2.dsc
 25f98f51dc0cc73bf97ed0745c9bde8c 101752 devel optional 
rustc-web_1.70.0+dfsg1-7~deb12u2.debian.tar.xz
 8c5f1b948817fd12c5cdf6d7ed30458e 8937 devel optional 
rustc-web_1.70.0+dfsg1-7~deb12u2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEUAUk+X1YiTIjs19qZF0CR8NudjcFAmXkyrYUHGRpbGluZ2Vy
QGRlYmlhbi5vcmcACgkQZF0CR8Nudjdttw/9GnkErAZrcVYTjxvgUU9vFAVZn/zI
DiMJejh4nkXjUPGEqnCm58dWGymSXAPXlVEhXc3GtxPgQleKRe0g0/zpre0W851i
1PK/xiJDQfobYaiwKZysaTEbkzqB4D8n/3O6Ez9J0l2y70hkb1bT3q5JHDBYyk4y
Q9wvfRaQRMaG18tXBZ1hOnlmZBQWpJNNIctdeVg3sHyRyIvoPoo/JjD4+V+x1cqa
0oCVQ1R7fwx2iMpAfIh7N3aNPhzNC7s9WHFXT0XTRjDe+EiH4RZV18qpeUhPqK0u

Bug#1064562: marked as done (4 packages from rustc-web have an undeclared file conflict)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 22:04:00 +
with message-id 
and subject line Bug#1064562: fixed in rustc-web 1.70.0+dfsg1-7~deb12u2
has caused the Debian Bug report #1064562,
regarding 4 packages from rustc-web have an undeclared file conflict
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.)


-- 
1064562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064562
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rust-web-gdb,libstd-rust-web-dev-windows,rust-web-src,rust-web-lldb
Version: 1.70.0+dfsg1-7~deb12u1
Severity: serious
Tags: bookworm
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libstd-rust-mozilla-dev-windows rust-mozilla-gdb 
rust-mozilla-lldb rust-mozilla-src

4 packages from rustc-web have an undeclared file conflict. This may
result in an unpack error from dpkg.

The files
 * /usr/lib/rustlib/x86_64-pc-windows-gnu/lib/rsbegin.o
 * /usr/lib/rustlib/x86_64-pc-windows-gnu/lib/rsend.o
 * /usr/lib/rustlib/x86_64-pc-windows-gnu/lib/self-contained/crt2.o
 * /usr/lib/rustlib/x86_64-pc-windows-gnu/lib/self-contained/dllcrt2.o
are contained in the packages
 * libstd-rust-mozilla-dev-windows/1.63.0+dfsg1-2~deb11u1 as present in bullseye
 * libstd-rust-web-dev-windows/1.70.0+dfsg1-7~deb12u1 as present in 
bookworm-proposed-updates

The files
 * /usr/bin/rust-gdb
 * /usr/bin/rust-gdbgui
 * /usr/lib/rustlib/etc/gdb_load_rust_pretty_printers.py
 * /usr/lib/rustlib/etc/gdb_lookup.py
 * /usr/lib/rustlib/etc/gdb_providers.py
are contained in the packages
 * rust-mozilla-gdb/1.63.0+dfsg1-2~deb11u1 as present in bullseye
 * rust-web-gdb/1.70.0+dfsg1-7~deb12u1 as present in bookworm-proposed-updates

The files
 * /usr/bin/rust-lldb
 * /usr/lib/rustlib/etc/lldb_commands
 * /usr/lib/rustlib/etc/lldb_lookup.py
 * /usr/lib/rustlib/etc/lldb_providers.py
are contained in the packages
 * rust-mozilla-lldb/1.63.0+dfsg1-2~deb11u1 as present in bullseye
 * rust-web-lldb/1.70.0+dfsg1-7~deb12u1 as present in bookworm-proposed-updates

The file /usr/lib/rustlib/src/rust is contained in the packages
 * rust-mozilla-src/1.63.0+dfsg1-2~deb11u1 as present in bullseye
 * rust-web-src/1.70.0+dfsg1-7~deb12u1 as present in bookworm-proposed-updates

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: rustc-web
Source-Version: 1.70.0+dfsg1-7~deb12u2
Done: Andres Salomon 

We believe that the bug you reported is fixed in the latest version of
rustc-web, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andres Salomon  (supplier of updated rustc-web 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 07:23:15 +
Source: rustc-web
Architecture: source
Version: 1.70.0+dfsg1-7~deb12u2
Distribution: bookworm
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Andres Salomon 
Closes: 1064562 1064563
Changes:
 rustc-web (1.70.0+dfsg1-7~deb12u2) bookworm; urgency=medium
 .
   * Non-maintainer upload.
   * Increase allowed test failures on armhf and ppc64el to fix FTBFS.
   * Provide Conflicts/Replaces for rust*-mozilla*, which could still be
 installed from oldstable (closes: #1064562).
   * Add Provides/Conflicts/Replaces for libstd-rust-1.70 (closes: #1064563).
Checksums-Sha1:
 1f45d0901c511971208228c2c37933df3c799169 3645 
rustc-web_1.70.0+dfsg1-7~deb12u2.dsc
 42a1f0bb22ac96de75003788e8b093b6f929852a 101752 
rustc-web_1.70.0+dfsg1-7~deb12u2.debian.tar.xz
 8bca1531b87b35a277a82df3334388a400a038f8 8937 
rustc-web_1.70.0+dfsg1-7~deb12u2_source.buildinfo

Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Bastian Blank]

On Mon, Mar 04, 2024 at 01:49:24PM +0100, Helmut Grohne wrote:
> The packaged gcc cross toolchain uses a sysroot during its own build
> still. As it is implemented now, it searches /usr//include, but
> not /usr/include/. So quite fundamentally, the Provides that
> we two agreed do break the build of cross toolchains right now.

Okay, so this problem is about the build of the toolchain, _not_ for
everything that comes after.

> Arguably, a cross toolchain build should probably search
> /usr/include/. I went back and forth a bit with Matthias
> about whether we could add this and did not fully understand his
> reasons, but there is one technical reason we want to avoid it for now.
> We can have both libc6-dev:TARGET and libc6-dev-TARGET-cross installed
> and these packages can have differing versions. When that happens and we
> search both /usr//include and /usr/include/, we'd
> mix two glibc versions with usually bad results (been there).

But this is a search path.  If a file exists in one, the second one is
not found.  So nothing can happen even from version skew.

> The other aspect here is that it is not sufficient to add
> /usr/include/ to the search path as you also need
> /usr/include to get a complete linux kernel headers experience. We
> definitely do not want to add /usr/include, because that is known to
> misguide configure tests performed for the target architecture.

We are talking about the toolchain itself.  What configure tests could
that be?  Or is that premature optimization of the gcc build?

> So at least for now, I am convinced that we will need
> /usr//include to be provided by the package providing
> linux-libc-dev-arch-cross.

You just said that the search path used during the build of the
toolchain and the one for everything else are unrelated.  So you are
free to create $BUILD/tmp-include with symlinks for asm, asm-generic,
linux.

The toolchain as installed already finds all headers.  So I still don't
see why we need this in the final system.

> That still leaves the question of which package would have to build that
> new linux-libc-dev-cross. The two obvious answers are linux and
> cross-toolchain-base. Do you have a preference here?

No, the gcc build itself, because it is the only part that needs it from
what you said here.

> I hope this all makes more sense now.

At least to show where it breaks.

Bastian

-- 
Each kiss is as the first.
-- Miramanee, Kirk's wife, "The Paradise Syndrome",
   stardate 4842.6

Bug#1064824: node-d3: fails to export map and other functions

[Julian Gilbey]

On Mon, Mar 04, 2024 at 09:18:01PM +, Julian Gilbey wrote:
> [...]
> So it's specifically "map" that is problematic, and I just happen to
> have stumbled upon it: d3 v5 depends on d3-array version 1, but the
> version of node-d3-array in unstable is 3.2.0+~cs5.0.6-2, and this is
> causing the conflict.
> 
> I don't know the best way to fix this.  node-d3-array version was
> upgraded from 1.2.4 to 3.x about two years ago, so d3 would have had
> this bug since then, but I'm the first one to stumble upon it :-/
> 
> Perhaps we could package node-d3-array-1 (version 1.2.4) and have
> node-d3 build-depends on that?

I was just wondering if there's a simpler way than having a new
package: have d3-array 1.2.4 being an unexported component of the
node-d3 source package, and instead of Build-Depends: node-d3-array,
have a Build-Conflicts: node-d3-array.  But then I discovered that the
binary package node-d3 depends on node-d3-array, as do 7 other
packages in testing (I haven't checked unstable).  I'm guessing that
most of those dependencies probably need version 1.x of d3-array, so
it may be that having a node-d3-array-1 (or -v1) package is actually
the way forward in this situation.

Best wishes,

   Julian

Bug#1064824: node-d3: fails to export map and other functions

[Julian Gilbey]

Hi Nilesh,

On Tue, Mar 05, 2024 at 02:06:08AM +0530, Nilesh Patra wrote:
> > This gives lots of differences still; stripping down to just the
> > differences still has many, many differences: some new exports not in
> > the original d3, and some lost exports; the list begins:
> > $ diff -u /tmp/d3-npm.exports.trimmed /tmp/d3-debian.exports.trimmed
> >
> > +exports.Adder = Adder;
> > -exports.bisect = bisectRight;
> > +exports.bin = bin;
> > +exports.bisect = bisect;
> > +exports.bisectCenter = bisectCenter;
> > +exports.blur2 = blur2;
> > +exports.blur = blur;
> > +exports.blurImage = blurImage;
> > +exports.count = count;
> > -exports.csvFormatRow = csvFormatRow;
> > -exports.csvFormatValue = csvFormatValue;
> 
> $ cat /tmp/d3-debian.exports.trimmed | egrep --color 
> '(bisectRight|csvFormatRow|csvFormatValue)'
> exports.bisectRight = bisectRight;
> exports.csvFormatRows = csvFormatRows;
> 
> Some of the diff entries are false positive -- it is just that entries are 
> not identical across these
> files and despite sorting them, you do not get the exact picture of the diff 
> in exports.

Well spotted, thanks!  I'll snip the discussion of csvFormatValue...

> [...]
> Which is why. Seems the versions of dev dependencies have not been 
> appropriately tightened by the upstream
> so we are running into weird surprises like these. Re-compiling node-d3 again 
> now should fixup this export however.

Great!

> These minor deltas in exports are more or less due to
> version differences in different d3 plugins.

> > ...
> > Background to this: I'm trying to package a new package which provides
> > a web server to visualise some data.  The package includes a few
> > precompiled JavaScript libraries obtained from npmjs.com, and the
> > server works fine with them.  But following Debian policy, I need to
> > replace those with the source packages.  And the server then doesn't
> > work.
> >
> > The JavaScript libraries which the package uses are: d3 v5.16.0,
> > d3-tip, apparently v0.9.1, along with jQuery and bootstrap4.  I have
> > replaced all of these with the versions in the corresponding Debian
> > packages (and I've just uploaded a new version of d3-tip, thinking
> > that that was the cause of the bug).
> >
> > When visiting the served web page, the console log gives the error
> > message:
> >
> > Uncaught (in promise) TypeError: t.map is not a function
> >n http://localhost:8080/js/d3/d3-tip.min.js:1
> >main http://localhost:8080/js/index.js:848
> >async* http://localhost:8080/js/index.js:993
> >
> > (This has changed from the original bug report as the minimised new
> > version of d3-tip has t.map instead of h.map.)
> >
> > d3-tip.js requires d3-collection, from which it calls a map function.
> > I tried replacing d3-tip.min.js with the pre-packaged version rather
> > than the (newly built) Debian version, but that did not help.  I
> > reverted that change and instead replaced d3.v5.min.js (which is a
> > copy of /usr/share/nodejs/d3/dist/d3.min.js) with the version provided
> > by upstream, which is a verbatim copy of the npmjs.com d3.min.js, and
> > the server then worked perfectly.  So this told me that it is the
> > Debian compiled d3 which is not working correctly.
> 
> Julian, I am very confused by that wording - from what I could gauge, your
> target package does not work with debian libs but it does work with npmjs, 
> yes?

I'm sorry I wasn't clear.

Yes, that's it: I'm trying to package taskflow for Debian (it's a
dependency of something else that I'm trying to package), and it
provides a profiler visualisation tool in the form of a webserver.

The upstream package (https://github.com/taskflow/taskflow) has
d3.v5.min.js and d3-tip.min.js included (in tfprof/js/d3), and these
are bitwise identical to the npmjs versions (versions 5.16.0 and
0.9.1).  The webserver works using these versions.  To satisfy Debian
policy, I replaced these with the versions found in libjs-d3-tip and
node-d3, but then the webserver fails to produce a usuable
visualisation.

My exploration, described above, was that "map" was not exported from
d3-collection, and that led me to explore whether this was a unique
missing export or not; I discovered that it was not.

> In that case linking your target package and listing the exact steps to
> that error can help someone debug it in more detail as to what might be 
> missing.

I've just rebuilt node-d3 locally from (Debian) source on an unstable
schroot, and I think I may have found the source of the bug: the build
reads:

-
   dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known files
Found debian/nodejs/d3-sankey/build
cd ./d3-sankey && sh -ex ../debian/nodejs/d3-sankey/build
+ rollup -c

src/index.js → dist/d3-sankey.js...
created dist/d3-sankey.js in 120ms

src/index.js → dist/d3-sankey.min.js...
created dist/d3-sankey.min.js in 561ms
Found debian/nodejs/./build
cd ./. && sh 

Bug#1063721: marked as done (spip: has stopped working, complains about PHP version being ‘too recent’)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 20:46:45 +
with message-id 
and subject line Bug#1063721: fixed in spip 4.1.15+dfsg-2
has caused the Debian Bug report #1063721,
regarding spip: has stopped working, complains about PHP version being ‘too 
recent’
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.)


-- 
1063721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063721
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: spip
Version: 4.1.9+dfsg-1+deb12u4
Severity: important
X-Debbugs-Cc: a...@users.sourceforge.net

Dear Maintainer,

after the upgrade, I could not log in to my site anymore. After making a backup 
of my
files, I first tried reinstalling, then purging + installing. a2ensite and 
spip_add_site
do not complain but …/ecrire shows:

“This installation will probably fail, or damage your site. PHP version 8.2.7 
too recent (maximum = 8.1.99)”

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

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

Versions of packages spip depends on:
ii  fonts-dustin20030517-14
ii  libjs-jquery3.6.1+dfsg+~3.5.14-1
ii  libjs-jquery-form   12-4
ii  libjs-jquery-jstree 3.3.12+dfsg1-2
ii  libjs-mediaelement  2.15.1+dfsg-3
ii  libjs-prefix-free   1.0.10+repack-5
ii  libjs-twitter-bootstrap-datepicker  1.3.1+dfsg1-4.1
ii  node-js-cookie  3.0.1+~3.0.0-3
ii  php-common  2:93
ii  php-getid3  1.9.22+dfsg-1
ii  php-mysql   2:8.2+93
ii  php-pgsql   2:8.2+93
ii  php-sqlite3 2:8.2+93
ii  php-xml 2:8.2+93
ii  php8.2-pgsql [php-pgsql]8.2.7-1~deb12u1
ii  php8.2-sqlite3 [php-sqlite3]8.2.7-1~deb12u1
ii  php8.2-xml [php-xml]8.2.7-1~deb12u1

Versions of packages spip recommends:
ii  apache2 [httpd]2.4.57-2
ii  default-mysql-server   1.1.0
ii  imagemagick8:6.9.11.60+dfsg-1.6
ii  imagemagick-6.q16 [imagemagick]8:6.9.11.60+dfsg-1.6
ii  mariadb-server [virtual-mysql-server]  1:10.11.6-0+deb12u1
ii  netpbm 2:11.01.00-2
ii  php-sqlite32:8.2+93
ii  php8.2-sqlite3 [php-sqlite3]   8.2.7-1~deb12u1
ii  postgresql 15+248

spip suggests no packages.

-- debconf information:
  spip/webserver: apache2
--- End Message ---
--- Begin Message ---
Source: spip
Source-Version: 4.1.15+dfsg-2
Done: David Prévot 

We believe that the bug you reported is fixed in the latest version of
spip, 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.
David Prévot  (supplier of updated spip 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: Mon, 04 Mar 2024 20:36:43 +0100
Source: spip
Architecture: source
Version: 4.1.15+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: David Prévot 
Changed-By: David Prévot 
Closes: 1063721
Changes:
 spip (4.1.15+dfsg-2) unstable; urgency=medium
 .
   * Allow current version of PHP (Closes: #1063721)
Checksums-Sha1:
 7a84cf0ef8e6ccb4447363ccf455d7ede1438cc8 1537 spip_4.1.15+dfsg-2.dsc
 2581dfba24aa7ee2fc7103e7d439d24eaa1d7782 68364 spip_4.1.15+dfsg-2.debian.tar.xz
 78ac021a7f08724f68a459ab5a7dc75e2af1b7fb 6858 
spip_4.1.15+dfsg-2_amd64.buildinfo
Checksums-Sha256:
 047d91de9c8b8f3ea5ab19a8671aefdd7af0ed0b9687cb308594425768a62ac5 1537 
spip_4.1.15+dfsg-2.dsc
 fd130de392e125e252fd78910cd00619a80289f0c0b52398bc3040eefeba55d1 68364 
spip_4.1.15+dfsg-2.debian.tar.xz
 0c5b0bd21657e88b8d711575e75b4ea7fccb2d4262296d232eb9ad59d1e0ca26 6858 

Bug#1062611: marked as done (libiv-unidraw2t64 has an undeclared file conflict)

[Debian Bug Tracking System]

Your message dated Mon, 4 Mar 2024 08:02:23 +0100
with message-id <20240304070223.ga1502...@subdivi.de>
and subject line Re: Bug#1062611: libiv-unidraw2t64 has an undeclared file 
conflict
has caused the Debian Bug report #1062611,
regarding libiv-unidraw2t64 has an undeclared file conflict
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.)


-- 
1062611: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062611
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libiv-unidraw2t64
Version: 2.0.11d.a1-1.1~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + libiv2 libiv2t64
X-Debbugs-Cc: Graham Inggs , vor...@debian.org

libiv-unidraw2t64 has an undeclared file conflict. This may result in an
unpack error from dpkg.

The files
 * /usr/lib/x86_64-linux-gnu/libIV.so.2
 * /usr/lib/x86_64-linux-gnu/libIV.so.2.0.0
are contained in the packages
 * libiv-unidraw2t64/2.0.11d.a1-1.1~exp1 as present in experimental
 * libiv2
   * 2.0.11d.a1-1+b4 as present in bookworm
   * 2.0.11d.a1-1+b5 as present in trixie|unstable
   * 2.0.4a1-2 as present in bullseye
 * libiv2t64/2.0.11d.a1-1.1~exp1 as present in experimental

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected files.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Version: 2.0.11d.a1-1.1

On Mon, Mar 04, 2024 at 12:39:21AM +0100, Agustin Martin wrote:
> I wonder if this is still an issue. Some uploads happened in the
> meantime and seems that  those files are currently shipped by a
> different package

Thank you for reaching out.

> $ dpkg -S libIV.so.2
> libiv2t64:amd64: /usr/lib/x86_64-linux-gnu/libIV.so.2.0.0
> libiv2t64:amd64: /usr/lib/x86_64-linux-gnu/libIV.so.2
> 
> which apparently handles things well
> 
> Package: libiv2t64
> Replaces: libiv2
> Provides: libiv2 (= 2.0.11d.a1-1.1)
> Breaks: libiv2 (<< 2.0.11d.a1-1.1)

I double checked with what dumat thinks about this and it does not see
any issue anymore and thnks libiv2t64 has version 2.0.11d.a1-1.1. I
guess that Lukas fixed the bug in his upload without adding it to the
changelog.

Helmut--- End Message ---

Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Helmut Grohne]

Hi Bastian,

On Mon, Mar 04, 2024 at 12:30:09PM +0100, Bastian Blank wrote:
> On Mon, Mar 04, 2024 at 12:07:15PM +0100, Matthias Klose wrote:
> > On 04.03.24 11:29, Bastian Blank wrote:
> > > On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> > > > However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.
> > > 
> > > Please be a bit more precise, there are no symlinks in this directory.
> > > | # dpkg -S /usr/alpha-linux-gnu/include/asm/a.out.h
> > > | linux-libc-dev-alpha-cross: /usr/alpha-linux-gnu/include/asm/a.out.h
> > > | # find /usr/alpha-linux-gnu/include/ -type l
> > > | #
> > yes, that is the problem. the cross gcc expects these headers in
> > /usr/alpha-linux-gnu/include, not in the header location for the host.
> 
> Please show your problem with a log, my crystal ball is broken.

This very much was not obvious to me either. I've now talked to Matthias
and believe I can explain the problem.

The packaged gcc cross toolchain uses a sysroot during its own build
still. As it is implemented now, it searches /usr//include, but
not /usr/include/. So quite fundamentally, the Provides that
we two agreed do break the build of cross toolchains right now.

Arguably, a cross toolchain build should probably search
/usr/include/. I went back and forth a bit with Matthias
about whether we could add this and did not fully understand his
reasons, but there is one technical reason we want to avoid it for now.
We can have both libc6-dev:TARGET and libc6-dev-TARGET-cross installed
and these packages can have differing versions. When that happens and we
search both /usr//include and /usr/include/, we'd
mix two glibc versions with usually bad results (been there).

While we might consider adding /usr/include/ to the cross
toolchain build search path later, it is not something we can do now and
before doing that, we need to better understand Matthias' reasons for
keeping these separate as well.

The other aspect here is that it is not sufficient to add
/usr/include/ to the search path as you also need
/usr/include to get a complete linux kernel headers experience. We
definitely do not want to add /usr/include, because that is known to
misguide configure tests performed for the target architecture. In
principle, we could extend the symlink farm in linux-libc-dev to also
have a lot of /usr/include//linux -> ../linux symlinks
(assuming that no other package ever installs to /usr/include/linux,
which is a property violated by aufs-dev and oss4-dev).

So at least for now, I am convinced that we will need
/usr//include to be provided by the package providing
linux-libc-dev-arch-cross.

As these are only necessary for building the cross toolchains, we
probably don't want these in the main linux-libc-dev package. So how
about adding a linux-libc-dev-cross package with yet more symlinks? Then
we can move the provides over to the linux-libc-dev-cross package and
that way repair the cross toolchain builds.

I requested that linux-libc-dev provides these for bootstrapping to know
which architectures linux-libc-dev actually supports. I don't need these
provides exactly, I just need a mechanism to answer the question "Does
linux-libc-dev work for a particular architecture?" from the binary
package metadata, so we might just change the Provides there to
linux-libc-dev-arch dropping the -cross suffix that traditionally
identified packages putting stuff into /usr/. Does that sound
reasonable to you?

That still leaves the question of which package would have to build that
new linux-libc-dev-cross. The two obvious answers are linux and
cross-toolchain-base. Do you have a preference here?

I hope this all makes more sense now.

Helmut

Bug#1063597: marked as done (giac: FTBFS on amd64: tests seg fault)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 20:35:50 +
with message-id 
and subject line Bug#1063597: fixed in giac 1.9.0.93+dfsg2-1
has caused the Debian Bug report #1063597,
regarding giac: FTBFS on amd64: tests seg fault
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.)


-- 
1063597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: giac
Version: 1.9.0.69+dfsg2-1
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=giac=amd64=1.9.0.69%2Bdfsg2-1%2Bb1=1707503131=0

FAIL: chk_factor


// Using locale /usr/share/locale/
// C.UTF-8
// /usr/share/locale/
// giac
// UTF-8
// Maximum number of parallel threads 4
// Unable to find keyword file doc/en/keywords
Added 0 synonyms
// Time 0
// Time 0
// Time 0
// Time 0.01
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0.01
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0
// Time 0.01
// Time 0
// Time 0
// Time 0.01
// Time 0
// Time 0
// Time 0
Segmentation fault
28a29,32
> (5*x+11)*(8*x+1)*(12*x-13)*(15*x+8)*(30*x-31)*(120*x-209),
> (x^20-x^15+x^10-x^5+1)*(x^20+x^15+x^10+x^5+1),
> (x^2-x+1)*(x^2+x+1)*(x^8-x^7+x^5-x^4+x^3-x+1)*(x^8+x^7-x^5-x^4-x^3+x+1)*(x^40-x^35+x^25-x^20+x^15-x^5+1)*(x^40+x^35-x^25-x^20-x^15+x^5+1),
> x^200-x^199+x^197-x^196+x^194-x^193+x^191-x^190+x^188-x^187+x^185-x^184+x^182-x^181+x^179-x^178+x^176-x^175+x^173-x^172+x^170-x^169+x^167-x^166+x^164-x^163+x^161-x^160+x^158-x^157+x^155-x^154+x^152-x^151+x^149-x^148+x^146-x^145+x^143-x^142+x^140-x^139+x^137-x^136+x^134-x^133+x^131-x^130+x^128-x^127+x^125-x^124+x^122-x^121+x^119-x^118+x^116-x^115+x^113-x^112+x^110-x^109+x^107-x^106+x^104-x^103+x^101-x^100+x^99-x^97+x^96-x^94+x^93-x^91+x^90-x^88+x^87-x^85+x^84-x^82+x^81-x^79+x^78-x^76+x^75-x^73+x^72-x^70+x^69-x^67+x^66-x^64+x^63-x^61+x^60-x^58+x^57-x^55+x^54-x^52+x^51-x^49+x^48-x^46+x^45-x^43+x^42-x^40+x^39-x^37+x^36-x^34+x^33-x^31+x^30-x^28+x^27-x^25+x^24-x^22+x^21-x^19+x^18-x^16+x^15-x^13+x^12-x^10+x^9-x^7+x^6-x^4+x^3-x+1
FAIL chk_factor (exit status: 1)


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: giac
Source-Version: 1.9.0.93+dfsg2-1
Done: Ileana Dumitrescu 

We believe that the bug you reported is fixed in the latest version of
giac, 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.
Ileana Dumitrescu  (supplier of updated giac 
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: Mon, 04 Mar 2024 21:43:04 +0200
Source: giac
Architecture: source
Version: 1.9.0.93+dfsg2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Ileana Dumitrescu 
Closes: 1063597
Changes:
 giac (1.9.0.93+dfsg2-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1063597).
   * d/copyright: src/mkjs removed from source and updated the copyright year
 for debian files from 2023 to 2024.
   * d/patches: Refresh patches.
   * d/source/lintian-overrides: Remove unused overrides.
Checksums-Sha1:
 0f0d82da0cfc5ad66258367803fd750b551a59a9 3067 giac_1.9.0.93+dfsg2-1.dsc
 3f5af2971722f08b65f4f830c577cc328ff9ae05 32805536 
giac_1.9.0.93+dfsg2.orig.tar.xz
 8a01dea626b59a4364b99e2b75fdab8046e117ad 23692 
giac_1.9.0.93+dfsg2-1.debian.tar.xz
 68ebe2d87fcdc3dc9941865900ed4c64340fac3e 17161 
giac_1.9.0.93+dfsg2-1_amd64.buildinfo
Checksums-Sha256:
 1532e590f895928369c5f07b20db038b323a4b818e5a887a7585b9a5a733d41b 3067 
giac_1.9.0.93+dfsg2-1.dsc
 ab2c547ff04244409922ea66ab79df05c70a130f92c69d020b221e14a7d300e2 32805536 
giac_1.9.0.93+dfsg2.orig.tar.xz
 8aa3a8054791a60f2aa8180214b5a07d47d50e2fc7b37f023d8504cb6ce2ae53 23692 
giac_1.9.0.93+dfsg2-1.debian.tar.xz
 b3bdb966108f7cfac1f98027fa71b25210269a256016b52d59eb9f675c234e2a 17161 
giac_1.9.0.93+dfsg2-1_amd64.buildinfo
Files:
 00a4d1827019551a604c69b3a4072eb5 3067 science optional 
giac_1.9.0.93+dfsg2-1.dsc
 

Bug#1064824: node-d3: fails to export map and other functions

[Nilesh Patra]

> This gives lots of differences still; stripping down to just the
> differences still has many, many differences: some new exports not in
> the original d3, and some lost exports; the list begins:
> $ diff -u /tmp/d3-npm.exports.trimmed /tmp/d3-debian.exports.trimmed
>
> +exports.Adder = Adder;
> -exports.bisect = bisectRight;
> +exports.bin = bin;
> +exports.bisect = bisect;
> +exports.bisectCenter = bisectCenter;
> +exports.blur2 = blur2;
> +exports.blur = blur;
> +exports.blurImage = blurImage;
> +exports.count = count;
> -exports.csvFormatRow = csvFormatRow;
> -exports.csvFormatValue = csvFormatValue;

$ cat /tmp/d3-debian.exports.trimmed | egrep --color 
'(bisectRight|csvFormatRow|csvFormatValue)'
exports.bisectRight = bisectRight;
exports.csvFormatRows = csvFormatRows;

Some of the diff entries are false positive -- it is just that entries are not 
identical across these
files and despite sorting them, you do not get the exact picture of the diff in 
exports.

However I did not find csvFormatValue and I dug a little bit into it. Seems 
this is sourced from node-d3-dsv
and exported with index.js: https://github.com/d3/d3/blob/v5.16.0/index.js

And checking on current unstable

| [/tmp/node-d3-dsv]$ git checkout debian/1.2.0+_1.2.3-1
| HEAD is now at 76229a9 releasing package node-d3-dsv version 1.2.0+~1.2.3-1
| [76229a9][/tmp/node-d3-dsv]$ grep -irn csvFormatValue
| types-d3-dsv/index.d.ts:195:// csvFormatValue(...) 

| types-d3-dsv/index.d.ts:202:export function csvFormatValue(value: string): 
string;
| src/csv.js:11:export var csvFormatValue = csv.formatValue;
| src/index.js:2:export {csvParse, csvParseRows, csvFormat, csvFormatBody, 
csvFormatRows, csvFormatRow, csvFormatValue} from "./csv.js";

So this should work, weird. I wanted to dig in, as per the build log: 
https://buildd.debian.org/status/fetch.php?pkg=node-d3=all=5.16.0%2B%7Ecs5.28.10-1=1693715544=0

| Selecting previously unselected package node-d3-dsv.
| Preparing to unpack .../317-node-d3-dsv_1.1.1-9_all.deb ...
| Unpacking node-d3-dsv (1.1.1-9) ...
| Selecting previously unselected packa

And

| [76229a9][/tmp/node-d3-dsv]$ git checkout debian/1.1.1-9   
| Previous HEAD position was 76229a9 releasing package node-d3-dsv version 
1.2.0+~1.2.3-1
| HEAD is now at 84fbfce releasing package node-d3-dsv version 1.1.1-9
| [84fbfce][/tmp/node-d3-dsv]$ grep -irn csvFormatValue | wc -l
| 0

Which is why. Seems the versions of dev dependencies have not been 
appropriately tightened by the upstream
so we are running into weird surprises like these. Re-compiling node-d3 again 
now should fixup this export however.

:-(

These minor deltas in exports are more or less due to
version differences in different d3 plugins.

> ...
> Background to this: I'm trying to package a new package which provides
> a web server to visualise some data.  The package includes a few
> precompiled JavaScript libraries obtained from npmjs.com, and the
> server works fine with them.  But following Debian policy, I need to
> replace those with the source packages.  And the server then doesn't
> work.
>
> The JavaScript libraries which the package uses are: d3 v5.16.0,
> d3-tip, apparently v0.9.1, along with jQuery and bootstrap4.  I have
> replaced all of these with the versions in the corresponding Debian
> packages (and I've just uploaded a new version of d3-tip, thinking
> that that was the cause of the bug).
>
> When visiting the served web page, the console log gives the error
> message:
>
> Uncaught (in promise) TypeError: t.map is not a function
>n http://localhost:8080/js/d3/d3-tip.min.js:1
>main http://localhost:8080/js/index.js:848
>async* http://localhost:8080/js/index.js:993
>
> (This has changed from the original bug report as the minimised new
> version of d3-tip has t.map instead of h.map.)
>
> d3-tip.js requires d3-collection, from which it calls a map function.
> I tried replacing d3-tip.min.js with the pre-packaged version rather
> than the (newly built) Debian version, but that did not help.  I
> reverted that change and instead replaced d3.v5.min.js (which is a
> copy of /usr/share/nodejs/d3/dist/d3.min.js) with the version provided
> by upstream, which is a verbatim copy of the npmjs.com d3.min.js, and
> the server then worked perfectly.  So this told me that it is the
> Debian compiled d3 which is not working correctly.

Julian, I am very confused by that wording - from what I could gauge, your
target package does not work with debian libs but it does work with npmjs, yes?

In that case linking your target package and listing the exact steps to
that error can help someone debug it in more detail as to what might be missing.

Best,
Nilesh


signature.asc
Description: PGP signature

Processed: fixed 1063721 in 4.2.2+dfsg-1

[Debian Bug Tracking System]

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

> fixed 1063721 4.2.2+dfsg-1
Bug #1063721 [spip] spip: has stopped working, complains about PHP version 
being ‘too recent’
Marked as fixed in versions spip/4.2.2+dfsg-1.
> thanks
Stopping processing here.

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

Processed: limit source to spip, tagging 1063721

[Debian Bug Tracking System]

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

> limit source spip
Limiting to bugs with field 'source' containing at least one of 'spip'
Limit currently set to 'source':'spip'

> tags 1063721 + pending
Bug #1063721 [spip] spip: has stopped working, complains about PHP version 
being ‘too recent’
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1056793: marked as done (ceph: ftbfs with cython 3.0.x)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 19:25:15 +
with message-id 
and subject line Bug#1056793: fixed in ceph 18.2.1+ds-1
has caused the Debian Bug report #1056793,
regarding ceph: ftbfs with cython 3.0.x
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.)


-- 
1056793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ceph
Version: 16.2.11+ds-5
Severity: important
Tags: sid trixie
User: debian-pyt...@lists.debian.org
Usertags: cython3

[This bug is targeted to the upcoming trixie release]

The package fails to build in a test rebuild on at least arm64 with
cython 3.0.5, but succeeds to build with cython 0.29.36.  Please
update the package to build with cython 3.0.5 (available in experimental).

If the package cannot be built with cython 3.0.5, please change the
build dependency from cython3 to cython3-legacy (available now in
unstable).  There is no replacement for cython3-dbg.

Build logs building with cython 3.0.5 can be found at
https://people.debian.org/~stefanor/cython3/cython-3.0.5/

See also https://lists.debian.org/debian-python/2023/11/msg00034.html
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 18.2.1+ds-1
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
ceph, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ceph 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: Mon, 19 Feb 2024 08:55:30 +0100
Source: ceph
Architecture: source
Version: 18.2.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 1056085 1056793 1058543
Changes:
 ceph (18.2.1+ds-1) unstable; urgency=medium
 .
   * Uploading to unstable.
   * New upstream release:
 - Fixes FTBFS (Closes: #1058543, #1056085).
   * Add pybind-rbd-make-cdef-functions-not-propagate-excepti.patch from
 upstream master branch to fix FTBFS of rbd.pyx with Cython 3.0.
 (Closes: #1056793).
   * Manually install systemd services in each package.
Checksums-Sha1:
 101aa477384c429a6e21a0f0ec1fbae9a859d081 8631 ceph_18.2.1+ds-1.dsc
 264f7b6bc58adaa46c653ef2f66926a93e6c4b59 141471372 ceph_18.2.1+ds.orig.tar.xz
 7f20989bcd4d4c35ba9242d2190ed92009c37b80 120516 ceph_18.2.1+ds-1.debian.tar.xz
 d0d9b55f5a51da1c28c518a6e988ef9937737414 45061 ceph_18.2.1+ds-1_amd64.buildinfo
Checksums-Sha256:
 386800d6207382a3bf71ee5ab2277209095180b77fd074c6f2778e62d44ecea1 8631 
ceph_18.2.1+ds-1.dsc
 056dd35560b94ee11e337d09f1b1e96f7348d58f188ad07eefa05183877f7e5c 141471372 
ceph_18.2.1+ds.orig.tar.xz
 250f250ecc4358f2ebc7378bf8f72aba7f1219a11751728ee878cdf171c4a051 120516 
ceph_18.2.1+ds-1.debian.tar.xz
 0c4b5a4d1aa1255e8dd6a52ef2c7c6a2d2306736329c737629c7dab6fc94708d 45061 
ceph_18.2.1+ds-1_amd64.buildinfo
Files:
 8d8a4749a2f7005ae9d10c43857778b6 8631 admin optional ceph_18.2.1+ds-1.dsc
 58762f61ae31a317075eda58b14ead07 141471372 admin optional 
ceph_18.2.1+ds.orig.tar.xz
 6c3fcc3df120ec0d6bc55a0362f029ea 120516 admin optional 
ceph_18.2.1+ds-1.debian.tar.xz
 44a64fa808390f8d95733d4c9c596003 45061 admin optional 
ceph_18.2.1+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmXmGbUACgkQ1BatFaxr
Q/490hAAoe/YfPjDCDIEswe3varBDHGbkdJhf4iBeN2IXgVxKOyAUNnWxc4Qyjbc
E006xGbhyRw4hmFHlBXmOQCnLYP4i0xS9zwldI/P6W9CtpEBQf5wVDUw0dVl3feE
OlsDK7yohAwat+a+nyXYH1ZBlqIx/cnkuj2mIAUgZLKgCk2c/sVCBzSLuZJs/mwC
oZfvz1uBXp5+HXXponB5jxRnFbaEqmeb/d2n6nE20xAKIhZZNpljaHVYXB0tsii+
Pta76bq+xiIcnDessuBSPYLNHs07xgmUmwRx0GDEeqenLP+WXuH8Uy2gMCHskmVn
gWxgyXsABlYMC8cMYKdlxO3YBiTvWBJ8NILXUYJH9WqbJmZzE99Unj0ESRlXH+G8
OJPY2TdSFkoPlzEQbmdZTMcHtnTWnAEPVIwizyPAk2G6ZAe4MEoYQ1vo3XGShp6p
xHe0739nmEd6aawwESWrKqbe0f2KUgEHQCo9Jjr1gu2Mb2ZLGuqA/Tv3BYmC3EjB
XLJuaa12hil47v7NsEroyuRBeI/6OPC0vaMiIvygzhxJyu+RqyZ+I6i8pHUe6yJ4
BwDcuFxe4KcIpLe1+Ai38hNUcHDb/aKgCSF7FefRkDQMDKKXjtjp/3Jna+64N+lR
Q2bQCkE6vwjxhUW3N0Vq9Vc7NJ5JkhphdFWygVzw/1avdLOxnUc=
=XvMc
-END PGP SIGNATURE-

Bug#1056085: marked as done (ceph: FTBFS: boost1.83 transition)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 19:25:15 +
with message-id 
and subject line Bug#1056085: fixed in ceph 18.2.1+ds-1
has caused the Debian Bug report #1056085,
regarding ceph: FTBFS: boost1.83 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.)


-- 
1056085: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056085
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ceph
Version: 16.2.11+ds-5
Severity: normal
User: gl...@debian.org
Usertags: boost183 ftbfs-boost183-transition

Hi,

we are preparing the transition of all libs on the new boost 1.83. During the
rebuild of packages against this library it was identified that probably your
package fails to build.

Relevant part (hopefully):

-

  |  ^~~~
/<>/src/rgw/rgw_asio_client.cc: In member function ‘virtual int 
rgw::asio::ClientIO::init_env(ceph::common::CephContext*)’:
/<>/src/rgw/rgw_asio_client.cc:42:39: error: ‘const class 
boost::core::basic_string_view’ has no member named ‘to_string’
   42 |   env.set("CONTENT_LENGTH", value.to_string());
  |   ^
/<>/src/rgw/rgw_asio_client.cc:46:37: error: ‘const class 
boost::core::basic_string_view’ has no member named ‘to_string’
   46 |   env.set("CONTENT_TYPE", value.to_string());
  | ^



-

To reproduce this behavior, you can install  -dev Boost packages from the
experimental repository, as shown in the following command:

  apt install libboost-dev -t experimental


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/ceph_16.2.11+ds-5_unstable_boost181.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-boost183-transition;users=gl...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-boost183-transition=gl...@debian.org=1=1=1=1#results

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you are unable to reproduce this, please provide a build log and diff it
so that we can identify any relevant changes that may have occurred in the 
meantime.
--- End Message ---
--- Begin Message ---
Source: ceph
Source-Version: 18.2.1+ds-1
Done: Thomas Goirand 

We believe that the bug you reported is fixed in the latest version of
ceph, 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 1056...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated ceph 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: Mon, 19 Feb 2024 08:55:30 +0100
Source: ceph
Architecture: source
Version: 18.2.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Ceph Packaging Team 
Changed-By: Thomas Goirand 
Closes: 1056085 1056793 1058543
Changes:
 ceph (18.2.1+ds-1) unstable; urgency=medium
 .
   * Uploading to unstable.
   * New upstream release:
 - Fixes FTBFS (Closes: #1058543, #1056085).
   * Add pybind-rbd-make-cdef-functions-not-propagate-excepti.patch from
 upstream master branch to fix FTBFS of rbd.pyx with Cython 3.0.
 (Closes: #1056793).
   * Manually install systemd services in each package.
Checksums-Sha1:
 101aa477384c429a6e21a0f0ec1fbae9a859d081 8631 ceph_18.2.1+ds-1.dsc
 264f7b6bc58adaa46c653ef2f66926a93e6c4b59 141471372 ceph_18.2.1+ds.orig.tar.xz
 7f20989bcd4d4c35ba9242d2190ed92009c37b80 120516 ceph_18.2.1+ds-1.debian.tar.xz
 d0d9b55f5a51da1c28c518a6e988ef9937737414 45061 ceph_18.2.1+ds-1_amd64.buildinfo
Checksums-Sha256:
 386800d6207382a3bf71ee5ab2277209095180b77fd074c6f2778e62d44ecea1 8631 
ceph_18.2.1+ds-1.dsc
 056dd35560b94ee11e337d09f1b1e96f7348d58f188ad07eefa05183877f7e5c 141471372 
ceph_18.2.1+ds.orig.tar.xz
 250f250ecc4358f2ebc7378bf8f72aba7f1219a11751728ee878cdf171c4a051 120516 
ceph_18.2.1+ds-1.debian.tar.xz
 0c4b5a4d1aa1255e8dd6a52ef2c7c6a2d2306736329c737629c7dab6fc94708d 45061 
ceph_18.2.1+ds-1_amd64.buildinfo
Files:
 8d8a4749a2f7005ae9d10c43857778b6 8631 admin optional 

Bug#1064737: marked as done (python3-defaults: FTBFS: make: *** [debian/rules:64: stamp-doc-policy] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 19:08:30 +
with message-id 
and subject line Bug#1064737: fixed in python3-defaults 3.11.8-1
has caused the Debian Bug report #1064737,
regarding python3-defaults: FTBFS: make: *** [debian/rules:64: 
stamp-doc-policy] Error 1
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.)


-- 
1064737: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064737
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python3-defaults
Version: 3.11.6-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[1]: Entering directory '/<>/policy'
> Running Sphinx v7.2.6
> making output directory... done
> WARNING: html_static_path entry '_static' does not exist
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [singlehtml]: all documents
> updating environment: [new config] 12 added, 0 changed, 0 removed
> reading sources... [  8%] build-dependencies
> reading sources... [ 17%] copyright
> reading sources... [ 25%] embedded-python
> reading sources... [ 33%] index
> reading sources... [ 42%] interpreter
> reading sources... [ 50%] locally-installed-python
> reading sources... [ 58%] packaged-modules
> reading sources... [ 67%] packaging-tools
> reading sources... [ 75%] python-programs
> reading sources... [ 83%] python3
> reading sources... [ 92%] this-document
> reading sources... [100%] upgrade-procedure
> 
> looking for now-outdated files... none found
> pickling environment... done
> checking consistency... done
> preparing documents... done
> assembling single document... copyright python3 interpreter packaged-modules 
> python-programs embedded-python locally-installed-python build-dependencies 
> packaging-tools upgrade-procedure this-document done
> writing... done
> writing additional files... done
> copying static files... done
> copying extra files... done
> dumping object inventory... done
> build succeeded, 1 warning.
> 
> The HTML page is in _build/singlehtml.
> make[1]: Leaving directory '/<>/policy'
> ( \
> echo 'The HTML version of the Debian Python Policy can be found in the 
> python3-dev package'; \
> html2text -utf8 -style pretty policy/_build/singlehtml/index.html; \
> ) > policy/_build/python-policy.txt
> Unrecognized command line option "-style", try "-help".
> make: *** [debian/rules:64: stamp-doc-policy] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/python3-defaults_3.11.6-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python3-defaults
Source-Version: 3.11.8-1
Done: Matthias Klose 

We believe that the bug you reported is fixed in the latest version of
python3-defaults, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated python3-defaults 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: Mon, 04 Mar 2024 19:43:37 +0100
Source: python3-defaults
Architecture: source
Version: 3.11.8-1
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 1064737
Changes:
 python3-defaults (3.11.8-1) unstable; 

Bug#1064410: marked as done (cpdb-backend-file build depends on cruft libcpdb-libs-backend-dev)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 18:48:15 +
with message-id 
and subject line Bug#1064522: Removed package(s) from unstable
has caused the Debian Bug report #1064410,
regarding cpdb-backend-file build depends on cruft libcpdb-libs-backend-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.)


-- 
1064410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cpdb-backend-file
Version: 1.0.1-1
Severity: serious
Tags: ftbfs trixie sid

libcpdb-libs-backend-dev is no longer built by src:cpdb-libs
--- End Message ---
--- Begin Message ---
Version: 1.0.1-1+rm

Dear submitter,

as the package cpdb-backend-file has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/1064522

The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.

Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.

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

Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)--- End Message ---

Bug#1065435: aptitude: FTBFS on armhf and armel (probably -Werror=implicit-function-declaration related)

[Sven Joachim]

On 2024-03-04 16:01 +0100, Axel Beckert wrote:

> Source: aptitude
> Version: 0.8.13-5
> Severity: serious
> Tags: ftbfs
> X-Debbugs-Cc: a...@debian.org, z...@debian.org
>
> Citing from https://buildd.debian.org/status/package.php?p=aptitude:
>
> BinNMU changelog for aptitude on amd64, arm64, armel, armhf, i386,
> mips64el, ppc64el, riscv64, s390x, alpha, hppa, hurd-i386, ia64,
> loong64, m68k, powerpc, ppc64, sh4, sparc64 and x32:
>
> Rebuild for time_t
>
> Tail of log for aptitude on armel:
>
> /usr/include/cppunit/TestAssert.h:161:6: note: candidate:
> ‘template void CppUnit::assertEquals(const T&, const T&,
> SourceLine, const std::string&)’
>   161 | void assertEquals( const T& expected,
>   |  ^~~~
> /usr/include/cppunit/TestAssert.h:161:6: note:   template argument 
> deduction/substitution failed:
> ../../tests/test_misc.cc:187:5: note: deduced conflicting types for
> parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long
> int’})
>   187 | CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
>   | ^
> make[3]: *** [Makefile:869: test_misc.o] Error 1
> make[3]: Leaving directory '/<>/build/tests'
> make[2]: *** [Makefile:1169: check-am] Error 2
> make[2]: Leaving directory '/<>/build/tests'
> /bin/sh: 1: ./cppunit_test: not found
> make[1]: *** [debian/rules:39: override_dh_auto_test-arch] Error 127
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:22: binary-arch] Error 2
>
> Tail of log for aptitude on armhf:
>
> /usr/include/cppunit/TestAssert.h:161:6: note: candidate:
> ‘template void CppUnit::assertEquals(const T&, const T&,
> SourceLine, const std::string&)’
>   161 | void assertEquals( const T& expected,
>   |  ^~~~
> /usr/include/cppunit/TestAssert.h:161:6: note:   template argument 
> deduction/substitution failed:
> ../../tests/test_misc.cc:187:5: note: deduced conflicting types for
> parameter ‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long
> int’})
>   187 | CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
>   | ^
> make[3]: *** [Makefile:869: test_misc.o] Error 1
> make[3]: Leaving directory '/<>/build/tests'
> make[2]: *** [Makefile:1169: check-am] Error 2
> make[2]: Leaving directory '/<>/build/tests'
> /bin/sh: 1: ./cppunit_test: not found
> make[1]: *** [debian/rules:39: override_dh_auto_test-arch] Error 127
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:22: binary-arch] Error 2
>
> Given the time and the architectures failing, this is probably related
> to dpkg switching on -Werror=implicit-function-declaration on these
> architectures (see https://bugs.debian.org/1065371 and a good summary
> of a similar case in https://bugs.debian.org/1065431 against lintian).

Not really, these arches now default to a 64-bit time_t and therefore
you get the conflicting types (suseconds_t is a long int,
__suseconds64_t a long long int).  This has nothing to do with implicit
function declarations.

Cheers,
   Sven

Bug#1061880: marked as done (s-tui: Selecting Graphs raises a ValueError exception)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 18:22:27 +
with message-id 
and subject line Bug#1061880: fixed in s-tui 1.1.6-1
has caused the Debian Bug report #1061880,
regarding s-tui: Selecting Graphs raises a ValueError exception
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.)


-- 
1061880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: s-tui
Version: 1.1.4-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: genpfa...@threadpitch.net

Dear Maintainer,

Selecting the 'Graphs' option in s-tui causes a ValueError exception:


Traceback (most recent call last):
  File "/usr/bin/s-tui", line 33, in 
sys.exit(load_entry_point('s-tui==1.1.4', 'console_scripts', 's-tui')())
 ^^
  File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 913, in main
graph_controller.main()
  File "/usr/lib/python3/dist-packages/s_tui/s_tui.py", line 758, in main
loop.run()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
343, in run
self._run()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
445, in _run
self.event_loop.run()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/select_loop.py", line 
182, in run
self._loop()
  File "/usr/lib/python3/dist-packages/urwid/event_loop/select_loop.py", line 
229, in _loop
record.data()
  File "/usr/lib/python3/dist-packages/urwid/display/_posix_raw_display.py", 
line 273, in wrapper
return self.parse_input(event_loop, callback, 
self.get_available_raw_input())
   
^^
  File "/usr/lib/python3/dist-packages/urwid/display/_raw_display_base.py", 
line 493, in parse_input
callback(decoded_codes, raw_codes)
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
472, in _update
self.process_input(keys)
  File "/usr/lib/python3/dist-packages/urwid/event_loop/main_loop.py", line 
573, in process_input
k = self._topmost_widget.keypress(self.screen_size, k)  # noqa: PLW2901
^^
  File "/usr/lib/python3/dist-packages/urwid/widget/widget.py", line 798, in 
keypress
return get_delegate(self).keypress(size, key)
   ^^
  File "/usr/lib/python3/dist-packages/urwid/widget/padding.py", line 418, in 
keypress
return self._original_widget.keypress(maxvals, key)
   
  File "/usr/lib/python3/dist-packages/urwid/widget/columns.py", line 1121, in 
keypress
key = w.keypress(size_args[i], key)
  ^
  File "/usr/lib/python3/dist-packages/s_tui/sturwid/ui_elements.py", line 92, 
in keypress
return super(ViListBox, self).keypress(size, key)
   ^^
  File "/usr/lib/python3/dist-packages/urwid/listbox.py", line 1102, in keypress
key = focus_widget.keypress((maxcol,), key)
  ^
  File "/usr/lib/python3/dist-packages/urwid/widget/grid_flow.py", line 494, in 
keypress
key = super().keypress(size, key)
  ^^^
  File "/usr/lib/python3/dist-packages/urwid/widget/widget.py", line 798, in 
keypress
return get_delegate(self).keypress(size, key)
   ^^
  File "/usr/lib/python3/dist-packages/urwid/widget/pile.py", line 862, in 
keypress
key = self.focus.keypress(size_args[i], key)
  ^^
  File "/usr/lib/python3/dist-packages/urwid/widget/padding.py", line 418, in 
keypress
return self._original_widget.keypress(maxvals, key)
   
  File "/usr/lib/python3/dist-packages/urwid/widget/columns.py", line 1121, in 
keypress
key = w.keypress(size_args[i], key)
  ^
  File "/usr/lib/python3/dist-packages/urwid/widget/widget.py", line 798, in 
keypress
return get_delegate(self).keypress(size, key)
   ^^
  File "/usr/lib/python3/dist-packages/urwid/widget/wimp.py", line 762, in 
keypress
self._emit("click")
  File "/usr/lib/python3/dist-packages/urwid/widget/widget.py", line 428, in 
_emit
signals.emit_signal(self, name, self, *args)
  File "/usr/lib/python3/dist-packages/urwid/signals.py", 

Processed: Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Debian Bug Tracking System]

Processing control commands:

> tags -1 moreinfo
Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Bug #1059786 [linux-libc-dev] cross-toolchain-base: Migrating linux-libc-dev
Added tag(s) moreinfo.
Added tag(s) moreinfo.

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

Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Bastian Blank]

Control: tags -1 moreinfo

On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't
> do that completely
> However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.

So you claim that /usr/DEB_HOST_GNU_TYPE/include is critical part of the
API for this package name?  If you think so, please provide evidence.

This path is in violation of the Debian policy, so can't be provided by
linux-libc-dev.

Bastian

-- 
You canna change the laws of physics, Captain; I've got to have thirty minutes!

Bug#1065216: marked as done (r-base: recent libc6-dev change causes the xdr feature to be dropped)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 15:54:55 +
with message-id 
and subject line Bug#1065216: fixed in r-base 4.3.3-2
has caused the Debian Bug report #1065216,
regarding r-base: recent libc6-dev change causes the xdr feature 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.)


-- 
1065216: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065216
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-base
Version: 4.3.3-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 the xdr
feature of r-base to be dropped, I am not sure it is something to care
about.

Therefore please either:
- Add libtirpc-dev as build dependency
- Disable the xdr feature support explicitly so that it does not depend
  on the packages installed on the system.

Regards
Aurelien
--- End Message ---
--- Begin Message ---
Source: r-base
Source-Version: 4.3.3-2
Done: Dirk Eddelbuettel 

We believe that the bug you reported is fixed in the latest version of
r-base, 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.
Dirk Eddelbuettel  (supplier of updated r-base 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: Mon, 04 Mar 2024 08:54:45 -0600
Source: r-base
Architecture: source
Version: 4.3.3-2
Distribution: unstable
Urgency: medium
Maintainer: Dirk Eddelbuettel 
Changed-By: Dirk Eddelbuettel 
Closes: 1065216
Changes:
 r-base (4.3.3-2) unstable; urgency=medium
 .
   * debian/control: Add libtirpc-dev to Build-Depends to fix build issue
 from side effects of t64 transition(Closes: 
#1065216)
Checksums-Sha1:
 dec1dfc1d23221207661b9e6efd98768855e3ca6 2939 r-base_4.3.3-2.dsc
 c284a93877b9b6860c8996ebe6544a2438c31a76 99664 r-base_4.3.3-2.debian.tar.xz
 49dd0be57873e339dda6f3bca46e6721e79f366a 18740 r-base_4.3.3-2_amd64.buildinfo
Checksums-Sha256:
 52cbd7a5c15f523d20077415dd2667fe7bd3c9813adaacc3f3c616c6b6ea0948 2939 
r-base_4.3.3-2.dsc
 103d3e509956fe82619f6988864efa728fb5e06f5fc19b411bd3c0cb9ff7e68a 99664 
r-base_4.3.3-2.debian.tar.xz
 b09e212f0a8b59c96713ce7b5edef505d3e18a8b1be3ef087e8611c721900b7b 18740 
r-base_4.3.3-2_amd64.buildinfo
Files:
 70030ccc55b835ccf0405393ebc5f9fb 2939 gnu-r optional r-base_4.3.3-2.dsc
 a6d1048d380b4b7bc64e84834c378cb6 99664 gnu-r optional 
r-base_4.3.3-2.debian.tar.xz
 a54a3bc0426d17452b5abc232b8c6eec 18740 gnu-r optional 
r-base_4.3.3-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIVAwUBZeXjXKFIn+KrmaIaAQj7IQ/+K9KxtvrnmHN+Iv7HD4aHyy4vYB8th8F4
a8COT83+6H2n8qDAH22T+md0dSD/7vrRn8JFPB49DImhzYZz+GKHTI6Ls8ImuzxA
PcqWR9t6RGBMvqv1dwgE/bD0nqQMB9KjHmfA5EyAVoCxtInBWkuB9NL53QpP1LD4
swIByA3snbbTv80+ECtpYxMgk0F1jGFeP8QHrthmAbYVUs2YICuLwr+AiHfMMGUh
w/YM0WmbPg3Ys2pD/bcKHi6Eyw3Lu+srvAwP7WhmdY9ZkZ1GCqmB6MZ1RWVgeRUu
nh8Eb/Qfx8R+6nfmb5VhFzC9N5TOV03XfJJof4YgpTUr1nOtV6ntyO++W3a2XEp1
9YZVbbMHI6bFrNdpfIlVnoOLUh6oqzGOWuowZhwKWQ+P5Mrh9HGL/JlNa0z1y5g/
lAB5CW7Pa5r7SPaVvth9Q8TQyTLcDYMw7RfQx9LTQ0WfiQHwjswlx5FY21ndZm75
7RI/OA1ZjSNGRGRd94puke/iZ+wQbxlVfV4L5fdfaZvCi0FBNTYkYxKNY6woJNg8
UYZzQIC/VLbJob+FwFGV5bIT9moC/qQ7lQ1aG/C418X6d+KDVNTBrIAPn0/ETDxb
PNlaZuk0CHRNSuezr4f5faBJcT4kvnQSdv8fMneAZOnG/OJA8pbOtH4csKlK8bC8
kAd9BjbQVCg=
=dge0
-END PGP SIGNATURE-



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

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

[Drew Parsons]

Source: petsc
Followup-For: Bug #1065323

petsc has a complex set of symlink farms since it needs to enable
multiple alternative build profiles.

I'll implement the patch in a way that doesn't let t64 get in the way
of updating subsequently (to 3.20 in the near future).

Drew

Bug#1065436: cyrus-sasl2 accesses resources from the network during the build

[Matthias Klose]

Package: src:cyrus-sasl2
Version: 2.1.28+dfsg1-4
Severity: serious
Tags: sid trixie

cyrus-sasl2 accesses resources from the network during the build, as 
seen on the Ubuntu buildds:


https://launchpadlibrarian.net/717319176/buildlog_ubuntu-noble-amd64.cyrus-sasl2_2.1.28+dfsg1-4ubuntu1_BUILDING.txt.gz

make[4]: Entering directory '/<>/build-heimdal'
test x".." = x"." || \
(cd .. && tar cf - --mode=gu+w docsrc) | tar xf -
/usr/bin/sphinx-build -d docsrc/.doctrees -n -q -D today=2024-03-03 -b 
cyrman ./docsrc ./man

WARNING: failed to reach any of the inventories with the following issues:
intersphinx inventory 'https://www.cyrusimap.org/objects.inv' not 
fetchable due to : 
HTTPSConnectionPool(host='www.cyrusimap.org', port=443): Max retries 
exceeded with url: /objects.inv (Caused by 
NameResolutionError("0x7feab01de450>: Failed to resolve 'www.cyrusimap.org' ([Errno -2] Name 
or service not known)"))



the Debian build log doesn't show this error message, so this sphinx 
inventory is fetched from the website during the build.

Processed: Re: Bug#1063721: spip: has stopped working, complains about PHP version being ‘too recent’

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1063721 [spip] spip: has stopped working, complains about PHP version 
being ‘too recent’
Severity set to 'serious' from 'important'
> found -1 4.1.15+dfsg-1
Bug #1063721 [spip] spip: has stopped working, complains about PHP version 
being ‘too recent’
Marked as found in versions spip/4.1.15+dfsg-1.

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

Bug#1065435: aptitude: FTBFS on armhf and armel (probably -Werror=implicit-function-declaration related)

[Axel Beckert]

Source: aptitude
Version: 0.8.13-5
Severity: serious
Tags: ftbfs
X-Debbugs-Cc: a...@debian.org, z...@debian.org

Citing from https://buildd.debian.org/status/package.php?p=aptitude:

BinNMU changelog for aptitude on amd64, arm64, armel, armhf, i386, mips64el, 
ppc64el, riscv64, s390x, alpha, hppa, hurd-i386, ia64, loong64, m68k, powerpc, 
ppc64, sh4, sparc64 and x32:

Rebuild for time_t

Tail of log for aptitude on armel:

/usr/include/cppunit/TestAssert.h:161:6: note: candidate: ‘template 
void CppUnit::assertEquals(const T&, const T&, SourceLine, const std::string&)’
  161 | void assertEquals( const T& expected,
  |  ^~~~
/usr/include/cppunit/TestAssert.h:161:6: note:   template argument 
deduction/substitution failed:
../../tests/test_misc.cc:187:5: note:   deduced conflicting types for parameter 
‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’})
  187 | CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
  | ^
make[3]: *** [Makefile:869: test_misc.o] Error 1
make[3]: Leaving directory '/<>/build/tests'
make[2]: *** [Makefile:1169: check-am] Error 2
make[2]: Leaving directory '/<>/build/tests'
/bin/sh: 1: ./cppunit_test: not found
make[1]: *** [debian/rules:39: override_dh_auto_test-arch] Error 127
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2

Tail of log for aptitude on armhf:

/usr/include/cppunit/TestAssert.h:161:6: note: candidate: ‘template 
void CppUnit::assertEquals(const T&, const T&, SourceLine, const std::string&)’
  161 | void assertEquals( const T& expected,
  |  ^~~~
/usr/include/cppunit/TestAssert.h:161:6: note:   template argument 
deduction/substitution failed:
../../tests/test_misc.cc:187:5: note:   deduced conflicting types for parameter 
‘const T’ (‘long int’ and ‘__suseconds64_t’ {aka ‘long long int’})
  187 | CPPUNIT_ASSERT_EQUAL(static_cast(99), c.tv_usec);
  | ^
make[3]: *** [Makefile:869: test_misc.o] Error 1
make[3]: Leaving directory '/<>/build/tests'
make[2]: *** [Makefile:1169: check-am] Error 2
make[2]: Leaving directory '/<>/build/tests'
/bin/sh: 1: ./cppunit_test: not found
make[1]: *** [debian/rules:39: override_dh_auto_test-arch] Error 127
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary-arch] Error 2

Given the time and the architectures failing, this is probably related
to dpkg switching on -Werror=implicit-function-declaration on these
architectures (see https://bugs.debian.org/1065371 and a good summary
of a similar case in https://bugs.debian.org/1065431 against lintian).

-- Package-specific info:
Terminal: xterm-256color
$DISPLAY is set.
which aptitude: /usr/bin/aptitude

aptitude version information:
aptitude 0.8.13
Compiler: g++ 13.2.0
Compiled against:
  apt version 6.0.0
  NCurses version 6.4
  libsigc++ version: 2.12.1
  Gtk+ support disabled.
  Qt support disabled.

Current library versions:
  NCurses version: ncurses 6.4.20240113
  cwidget version: 0.5.18
  Apt version: 6.0.0

aptitude linkage:
linux-vdso.so.1 (0x7ffc0a3eb000)
libgtk3-nocsd.so.0 => /lib/x86_64-linux-gnu/libgtk3-nocsd.so.0 
(0x7f8fca645000)
libapt-pkg.so.6.0 => /lib/x86_64-linux-gnu/libapt-pkg.so.6.0 
(0x7f8fc9e0)
libncursesw.so.6 => /lib/x86_64-linux-gnu/libncursesw.so.6 
(0x7f8fca1c6000)
libtinfo.so.6 => /lib/x86_64-linux-gnu/libtinfo.so.6 
(0x7f8fca191000)
libsigc-2.0.so.0 => /lib/x86_64-linux-gnu/libsigc-2.0.so.0 
(0x7f8fca188000)
libcwidget.so.4 => /lib/x86_64-linux-gnu/libcwidget.so.4 
(0x7f8fca084000)
libsqlite3.so.0 => /lib/x86_64-linux-gnu/libsqlite3.so.0 
(0x7f8fc9c8a000)
libboost_iostreams.so.1.83.0 => 
/lib/x86_64-linux-gnu/libboost_iostreams.so.1.83.0 (0x7f8fca06a000)
libxapian.so.30 => /lib/x86_64-linux-gnu/libxapian.so.30 
(0x7f8fc9a0)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 
(0x7f8fc960)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f8fc9921000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 
(0x7f8fca03b000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f8fc941e000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x7f8fc9c85000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7f8fc9c8)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f8fc9c61000)
libbz2.so.1.0 => /lib/x86_64-linux-gnu/libbz2.so.1.0 
(0x7f8fc990e000)
liblzma.so.5 => /lib/x86_64-linux-gnu/liblzma.so.5 (0x7f8fc98d1000)
liblz4.so.1 => /lib/x86_64-linux-gnu/liblz4.so.1 (0x7f8fc98ab000)
libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1 (0x7f8fc935d000)
libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x7f8fc9878000)
libsystemd.so.0 => /lib/x86_64-linux-gnu/libsystemd.so.0 
(0x7f8fc927b000)
libgcrypt.so.20 => 

Bug#1065216: r-base: recent libc6-dev change causes the xdr feature to be dropped

[Dirk Eddelbuettel]

On 1 March 2024 at 23:36, Aurelien Jarno wrote:
| Source: r-base
| Version: 4.3.3-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 the xdr
| feature of r-base to be dropped, I am not sure it is something to care
| about.
| 
| Therefore please either:
| - Add libtirpc-dev as build dependency

I'll do that. We don't have that much little vs big endian out there anymore
but it is a feature that was long supported so it should remain supported.

Dirk

| - Disable the xdr feature support explicitly so that it does not depend
|   on the packages installed on the system.
| 
| Regards
| Aurelien

-- 
dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org

Bug#999931: virtuoso-opensource: depends on obsolete pcre3 library

[Yavor Doganov]

Hi Andreas,

On Wed, 28 Feb 2024 18:36:04 +0200,
Andreas Beckmann wrote:
> On Wed, 20 Dec 2023 21:18:20 +0200 Yavor Doganov  wrote:
> > Please find attached a patch;
> 
> Thanks for the patch, I uploaded it to Debian and so far noone
> complained ;-)

Thanks!  Complaints usually come a bit later...
 
> But the patch doesn't apply cleanly on newer virtuoso-opensource
> versions, there are actually changes in pcre usage in
> libsrc/Wi/sqlbif.h that require adjustments.

Right; there's a new function.

> Could you take a look again and update the patch?

Attached is a patch (commit made to the try-7.2.12 branch) that
updates pcre2.patch so that it applies cleanly and restores the
build-dependency on libpcre2-dev.

> I've never worked with (any version of) pcre (from the programmer
> persepective,

Likewise, I'm a complete novice here.  It would be nice to finish this
transition, though.
>From 82b97264413540aa72d96297a93a6fd24f56adc2 Mon Sep 17 00:00:00 2001
From: Yavor Doganov 
Date: Mon, 4 Mar 2024 16:29:34 +0200
Subject: [PATCH] pcre2.patch: Update for the new upstream release

---
 debian/changelog   |   4 +
 debian/control |   2 +-
 debian/patches/pcre2.patch | 152 -
 debian/patches/series  |   2 +-
 4 files changed, 107 insertions(+), 53 deletions(-)

diff --git a/debian/changelog b/debian/changelog
index 907e89fc6..a566f67f2 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,8 +1,12 @@
 virtuoso-opensource (7.2.12+dfsg-0.1) UNRELEASED; urgency=medium
 
+  [ Andreas Beckmann ]
   * Non-maintainer upload.
   * New upstream release.
 
+  [ Yavor Doganov ]
+  * debian/patches/pcre2.patch: Update for the new upstream release.
+
  -- Andreas Beckmann   Wed, 28 Feb 2024 15:19:59 +0100
 
 virtuoso-opensource (7.2.5.1+dfsg1-0.6) unstable; urgency=medium
diff --git a/debian/control b/debian/control
index 5fd05fab9..db9b573c4 100644
--- a/debian/control
+++ b/debian/control
@@ -14,7 +14,7 @@ Build-Depends: debhelper-compat (= 13),
gperf,
libldap2-dev,
libmagickwand-dev,
-   libpcre3-dev,
+   libpcre2-dev,
libreadline-dev,
libssl-dev,
libtirpc-dev,
diff --git a/debian/patches/pcre2.patch b/debian/patches/pcre2.patch
index 98c06be51..104c1abc9 100644
--- a/debian/patches/pcre2.patch
+++ b/debian/patches/pcre2.patch
@@ -2,12 +2,12 @@ Description: Port to PCRE2.
 Bug-Debian: https://bugs.debian.org/31
 Author: Yavor Doganov 
 Forwarded: no
-Last-Update: 2023-12-20
+Last-Update: 2024-03-04
 ---
 
 --- virtuoso-opensource.orig/libsrc/Wi/Makefile.am
 +++ virtuoso-opensource/libsrc/Wi/Makefile.am
-@@ -559,7 +559,7 @@
+@@ -563,7 +563,7 @@
$(libwi_base_la_sources)
  
  libwi_la_CFLAGS  = $(libwi_base_la_cflags)
@@ -18,7 +18,7 @@ Last-Update: 2023-12-20
  libwi_odbc_la_SOURCES += \
 --- virtuoso-opensource.orig/libsrc/Wi/bif_regexp.c
 +++ virtuoso-opensource/libsrc/Wi/bif_regexp.c
-@@ -30,7 +30,8 @@
+@@ -31,7 +31,8 @@
  
  // Debian maintainer: replaced by external PCRE
  // #include "util/pcrelib/pcre.h"
@@ -28,7 +28,7 @@ Last-Update: 2023-12-20
  
  /*
 typedef struct rx_query_s {
-@@ -66,15 +67,16 @@
+@@ -65,16 +66,17 @@
  typedef struct compiled_regexp_s
  {
int refctr;
@@ -42,14 +42,16 @@ Last-Update: 2023-12-20
  
 -int32 c_pcre_match_limit_recursion = 500;
 -int32 c_pcre_match_limit = 10;
+-int32 pcre_max_cache_sz = 2;
 +static pcre2_match_context *match_ctxt = NULL;
 +
 +uint32 c_pcre_match_limit_recursion = 500;
 +uint32 c_pcre_match_limit = 10;
- int32 pcre_max_cache_sz = 2;
++uint32 pcre_max_cache_sz = 2;
  int32 pcre_rnd_seed;
  
-@@ -97,6 +99,23 @@
+ id_hashed_key_t
+@@ -96,6 +98,23 @@
  }
  
  void
@@ -73,7 +75,7 @@ Last-Update: 2023-12-20
  release_compiled_regexp (id_hash_t *c_r, compiled_regexp_t *data)
  {
int delete_data;
-@@ -112,9 +131,7 @@
+@@ -111,9 +130,7 @@
if (!delete_data)
  return;
if (NULL != data->code)
@@ -84,7 +86,7 @@ Last-Update: 2023-12-20
dk_free (data, sizeof (compiled_regexp_t));
  }
  
-@@ -137,10 +154,11 @@
+@@ -136,10 +153,11 @@
  }
  
  static compiled_regexp_t *
@@ -99,9 +101,9 @@ Last-Update: 2023-12-20
regexp_key_t key;
compiled_regexp_t **val = NULL;
compiled_regexp_t tmp, *new_val;
-@@ -156,46 +174,18 @@
+@@ -155,46 +173,18 @@
  }
-   HT_LEAVE (c_r);
+   HT_UNLOCK (c_r);
dbg_printf (("regex compiling (%s) with options %x ...\n", pattern, 
options));
 -  tmp.code = pcre_compile (pattern, options, , , 0);
 +  tmp.code = pcre2_compile ((PCRE2_SPTR) pattern, strlen (pattern),
@@ -149,9 +151,9 @@ Last-Update: 2023-12-20
new_val->code = tmp.code;
 -  new_val->code_x = tmp.code_x;
new_val->refctr = 1;
-   HT_ENTER (c_r);
+   HT_WRLOCK (c_r);
pcre_cache_check (c_r);
-@@ -302,18 +292,18 @@
+@@ -301,18 +291,18 @@
  }
  
  
@@ -175,7 +177,7 @@ Last-Update: 2023-12-20
  /*
  #define PCRE_EXTENDED   0x0008
  

Bug#1065431: lintian: autopkgtests fail due to implicit definition of memcpy

[Chris Hofstaedtler]

Source: lintian
Version: 2.117.0
Severity: serious

dpkg has turned on -Werror=implicit-function-declaration on some
archs (compare #1065371 and the earlier bug requesting this). This
in turn causes lintian's autopkgtests to fail on armel, armhf and
maybe others, like this:

https://ci.debian.net/packages/l/lintian/testing/armel/43531737/

gcc -g -O2 -Werror=implicit-function-declaration 
-ffile-prefix-map=/tmp/autopkgtest-lxc.kznc_8xn/downtmp/autopkgtest_tmp/build-and-evaluate-test-packages/packages/checks/libraries/embedded/binaries-embedded-libs/binaries-embedded-libs-1.0=.
 -fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 
-D_TIME_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now -o 
libbz2 libbz2.c
In file included from libpng.c:2:
hardening-trigger.h: In function 'e':
hardening-trigger.h:3:3: error: implicit declaration of function 'memcpy' 
[-Werror=implicit-function-declaration]

Indeed hardening-trigger.h has a call to memcpy but neglects to
include .

Please fix this.

If dpkg reverts turning on the option, this bug obviously becomes
less severe, but its still a bug.

Chris

Bug#1062218: libaio: NMU diff for 64-bit time_t transition

[Guillem Jover]

Hi!

On Sun, 2024-03-03 at 23:00:00 +0100, Guillem Jover wrote:
> On Thu, 2024-02-29 at 02:35:16 +0100, Guillem Jover wrote:
> > Control: tags -1 - pending
> 
> > On Wed, 2024-01-31 at 19:36:09 +, Steve Langasek wrote:
> > > Source: libaio
> > > Version: 0.3.113-5
> > > Severity: serious
> > > Tags: patch pending
> > > Justification: library ABI skew on upgrade
> > > User: debian-...@lists.debian.org
> > > Usertags: time-t
> > 
> > > 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.
> > 
> > Unfortunately I just realized this patch is not enough. :/ This library
> > emits direct syscalls, so these are going to be broken with the time_t
> > size change, the syscalls need to be updated. I'm checking how to best
> > fix this, perhaps even via dual-ABI, to avoid the transition
> > altogether, but let's see.
> > 
> > I guess this might have been missed for other packages that that emit
> > direct syscalls and are not using the time64 variants for those
> > already.
> 
> Just as a status update, I've got most of this working, but upstream
> does not tend to be very responsive, so I think I'll do a proper
> SONAME bump with my proposed changes for the dual-ABI, to avoid any
> potential clashes with anything that gets upstream, and to make a
> revert easier, by reusing the t64 library names. And then once/if this
> gets merged upstream I can revert that and simply do the proper
> dual-ABI on the old SONAME and package names, as if nothing had
> happened (except for the required rebuilds).
> 
> Hopefully I can have something for upload today or tomorrow, hoping
> that this delay up to now, does not block too many things. :/

I've got all the upstream changes now ready, except that there's still
one test case failing, something wrong with the sigset_t type. I've run
out of time trying to track this down, but I've pushed what I have on
the pu/time64 branch, and will continue later today.

Thanks,
Guillem

Processed: Re: Bug#1065428: librocsolver-doc: missing Breaks+Replaces: librocsolver-dev (<< 5.5.1-5~)

[Debian Bug Tracking System]

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

> tag 1065428 pending
Bug #1065428 [librocsolver-doc] librocsolver-doc: missing Breaks+Replaces: 
librocsolver-dev (<< 5.5.1-5~)
Added tag(s) pending.
> thanks
Stopping processing here.

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

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

[Warlich, Christof]

Sebastian Ramacher wrote:
> Christof Warlich wrote:
> > If this assumption is true, then why is the Debian build system (i.e. 
> > dpkg-buildpackage) not smart enough to simply ignore an existing +bX 
> > extension for Architecture: all binary packages? IMHO, this would simplify 
> > matters, as it would have avoided the pitfall that I stumbled into 
> > altogether.
> 
> binNMUs are handled a layer above. sbuild will pass the correct options to 
> dpkg-buildpackage to build binNMUs. If you are interested in having binNMU 
> builds for your own infrastructure, you'll probably need to take a look at 
> the sbuild source to see how it is implemented.

Ok, so I'd better start using sbuild instead. Again, thanks for the valuable 
info and your time.

Bug#1060318: [Pkg-opencl-devel] The right bug is this one #1060318

[Andreas Beckmann]

On 04/03/2024 11.21, Picca Frédéric-Emmanuel wrote:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060318#10


Unfortunately I cannot reproduce that by rebuilding 2.0.0+dfsg-1 from 
sid (git has nothing newer) in sid or testing pbuilder chroots on amd64.


Andreas

Bug#1064680: marked as done (SWIG_snprintf not defined for ruby/tcl bindings)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 12:22:01 +
with message-id 
and subject line Bug#1064680: fixed in swig 4.2.1-1
has caused the Debian Bug report #1064680,
regarding SWIG_snprintf not defined for ruby/tcl bindings
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.)


-- 
1064680: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064680
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: subversion
Version: 1.14.3-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> make[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make 
> rule.
> if [ "LD_LIBRARY_PATH" = "DYLD_LIBRARY_PATH" ]; then for d in 
> /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby 
> /<>/BUILD/subversion/bindings/swig/ruby/../../../libsvn_*; do if 
> [ -n "$DYLD_LIBRARY_PATH" ]; then 
> LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$d/.libs"; else LD_LIBRARY_PATH="$d/.libs"; 
> fi; done; export LD_LIBRARY_PATH; fi; \
> cd /<>/BUILD/subversion/bindings/swig/ruby; \
>   check_rb() { \
> /usr/bin/ruby -I /<>/BUILD/../subversion/bindings/swig/ruby 
> /<>/BUILD/../subversion/bindings/swig/ruby/test/run-test.rb 
> "$@"; \
>   }; \
>   if check_rb --help 2>&1 | grep -q -- --collector; then \
> check_rb --collector=dir --verbose=normal; \
>   elif [ "3" -eq 1 -a "1" -lt 9 ] ; then \
> check_rb --verbose=normal; \
>   else \
> check_rb; \
>   fi
> :86:in
>  `require': 
> /<>/BUILD/subversion/bindings/swig/ruby/libsvn_swig_ruby/.libs/libsvn_swig_ruby-1.so.1:
>  undefined symbol: SWIG_snprintf - 
> /<>/BUILD/subversion/bindings/swig/ruby/.ext/svn/ext/core.so 
> (LoadError)
>   from 
> :86:in
>  `require'
>   from /<>/subversion/bindings/swig/ruby/svn/error.rb:21:in 
> `'
>   from 
> :86:in
>  `require'
>   from 
> :86:in
>  `require'
>   from /<>/subversion/bindings/swig/ruby/svn/core.rb:25:in 
> `'
>   from 
> :86:in
>  `require'
>   from 
> :86:in
>  `require'
>   from 
> /<>/BUILD/../subversion/bindings/swig/ruby/test/run-test.rb:47:in
>  `'
> make[3]: *** [Makefile:973: check-swig-rb] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/subversion_1.14.3-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=lu...@debian.org=1=1=1=1#results

A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!

If you reassign this bug to another package, please mark it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: swig
Source-Version: 4.2.1-1
Done: Rafael Laboissière 

We believe that the bug you reported is fixed in the latest version of
swig, 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 1064...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rafael Laboissière  (supplier of updated swig 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: Mon, 04 Mar 2024 07:26:01 -0300
Source: swig
Architecture: source
Version: 4.2.1-1
Distribution: unstable
Urgency: medium
Maintainer: Torsten Landschoff 
Changed-By: Rafael Laboissière 
Closes: 1064680
Changes:
 swig (4.2.1-1) unstable; urgency=medium
 .
   [ Rafael Laboissière ]
   * New upstream version 4.2.1 (Closes: #1064680)
   * d/p/octave-9.patch: Drop patch (applied upstream)
   * Use the dh command sequencer
 + d/rules: Revamp the file, keeping only target "%:" and
   "override_dh_autoreconf"
 + d/swig-doc.doc-base: Add ".gz" as sufix of the PDF file
 + 

Bug#1065428: librocsolver-doc: missing Breaks+Replaces: librocsolver-dev (<< 5.5.1-5~)

[Andreas Beckmann]

Package: librocsolver-doc
Version: 5.5.1-5~exp1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts file-conflict

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation.
This error may also be triggered by having a predecessor package from
'sid' installed while installing the package from 'experimental'.

See policy 7.6 at
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces

>From the attached log (scroll to the bottom...):

  Preparing to unpack .../librocsolver-doc_5.5.1-5~exp1_all.deb ...
  Unpacking librocsolver-doc (5.5.1-5~exp1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/librocsolver-doc_5.5.1-5~exp1_all.deb (--unpack):
   trying to overwrite 
'/usr/share/doc/librocsolver-dev/examples/example_basic.c', which is also in 
package librocsolver-dev 5.5.1-4
  Errors were encountered while processing:
   /var/cache/apt/archives/librocsolver-doc_5.5.1-5~exp1_all.deb


cheers,

Andreas


librocsolver-dev=5.5.1-4_librocsolver-doc=5.5.1-5~exp1.log.gz
Description: application/gzip

Processed: bug 1065395 is forwarded to https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2397

[Debian Bug Tracking System]

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

> forwarded 1065395 
> https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2397
Bug #1065395 [src:spirv-llvm-translator-14] spirv-llvm-translator-14: 
autopkgtest on s390x uses huge amount of disk space
Set Bug forwarded-to-address to 
'https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2397'.
> thanks
Stopping processing here.

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

Bug#1065416: [Cross-toolchain-base-devs] Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Bastian Blank]

On Mon, Mar 04, 2024 at 12:07:15PM +0100, Matthias Klose wrote:
> On 04.03.24 11:29, Bastian Blank wrote:
> > On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> > > However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.
> > 
> > Please be a bit more precise, there are no symlinks in this directory.
> > | # dpkg -S /usr/alpha-linux-gnu/include/asm/a.out.h
> > | linux-libc-dev-alpha-cross: /usr/alpha-linux-gnu/include/asm/a.out.h
> > | # find /usr/alpha-linux-gnu/include/ -type l
> > | #
> yes, that is the problem. the cross gcc expects these headers in
> /usr/alpha-linux-gnu/include, not in the header location for the host.

Please show your problem with a log, my crystal ball is broken.

arm-linux-gnueabihf-cpp-13 tells me:

| #include <...> search starts here:
|  /usr/lib/gcc-cross/arm-linux-gnueabihf/13/include
|  
/usr/lib/gcc-cross/arm-linux-gnueabihf/13/../../../../arm-linux-gnueabihf/include
|  /usr/include/arm-linux-gnueabihf
|  /usr/include
| End of search list.

So clearly /usr/include/arm-linux-gnueabihf is used.

Regards,
Bastian

-- 
It would be illogical to assume that all conditions remain stable.
-- Spock, "The Enterprise Incident", stardate 5027.3

Bug#1065395: spirv-llvm-translator-14: autopkgtest on s390x uses huge amount of disk space

[Andreas Beckmann]

Control: forwarded -1 
https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/2397


On 03/03/2024 20.52, Paul Gevers wrote:

Source: spirv-llvm-translator-14
Version: 14.0.0-10



Since a couple of days, our workers on s390x are dying because some test
is filling up all disk space. Several days ago, I wrongly suspected 

One of the suspects started to be spirv-llvm-translator-14, so I ran its 
autopkgtest manually, while logging disk use every 10 seconds (I started 
slightly delayed because I monitored the wrong partition first). As you 
can see below, during the test it grows from 17 GB (at the end) to its 
peak at 179 GB. That's not acceptable on our infrastructure. One file I 
happened to spot on the way was 
build/test/test_output/DebugInfo/Generic/Output/two-cus-from-same-file.ll.tmp:

-rw-r--r-- 1 root root  41G Mar  3 19:18 two-cus-from-same-file.ll.tmp

I have added spirv-llvm-translator-14 to our reject-list on s390x.

As this seems to be a rather new issue, I'm wondering if it's due to:
* Add build-needed autopkgtest for spirv-headers compat check.


Probably.

The buildds report disk usage when building spirv-llvm-translator-* 
between 400MB and 600MB on all architectures except s390x, ppc64, 
sparc64, i.e. all the big-endian ones, where it's slightly above 40GB 
(which very vell corresponds to the file you spotted).
This started with 14.0.0-2 (i.e. 14.0.0-1 was around 500MB on s390x, 
too) which had "* Enable build-time tests, ignore failures on !amd64."


So maybe I should skip the build-time tests on big-endian altogether.

Failure rates:
amd64: 0%
i386: <1%
ppc64el: <2%
most: <10%
s390x: >60%
ppc64: >60%

(Upstream seems to test the testsuite only on amd64, 
https://github.com/KhronosGroup/SPIRV-LLVM-Translator/issues/1964)


Andreas

Processed: Re: cross-toolchain-base: Migrating linux-libc-dev

[Debian Bug Tracking System]

Processing control commands:

> tags -1 - patch
Bug #1059786 [linux-libc-dev] cross-toolchain-base: Migrating linux-libc-dev
Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Removed tag(s) patch.
Removed tag(s) patch.

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

Bug#1059786: cross-toolchain-base: Migrating linux-libc-dev

[Matthias Klose]

Control: tags -1 - patch

The headers have to be provided in the /usr//include location.

Currently, that is not possible, because linux-libc-dev provides the 
linux-libc-dev-cross-* packages, without providing these headers in the 
old locations.


The assumption to include the headers for the target from the header 
location of the host is wrong.

Processed (with 1 error): Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Debian Bug Tracking System]

Processing control commands:

> unmerge 1059786 -1
Unknown command or malformed arguments to command.

> reassign -1 linux-libc-dev
Bug #1065416 [cross-toolchain-base] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Bug #1059786 [cross-toolchain-base] cross-toolchain-base: Migrating 
linux-libc-dev
Bug reassigned from package 'cross-toolchain-base' to 'linux-libc-dev'.
Bug reassigned from package 'cross-toolchain-base' to 'linux-libc-dev'.
Ignoring request to alter found versions of bug #1065416 to the same values 
previously set
Ignoring request to alter found versions of bug #1059786 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1065416 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1059786 to the same values 
previously set
> found -1 6.7.7-1
Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Bug #1059786 [linux-libc-dev] cross-toolchain-base: Migrating linux-libc-dev
Marked as found in versions linux/6.7.7-1.
Marked as found in versions linux/6.7.7-1.
> severity -1 serious
Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Bug #1059786 [linux-libc-dev] cross-toolchain-base: Migrating linux-libc-dev
Severity set to 'serious' from 'normal'
Severity set to 'serious' from 'normal'

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

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

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:08:39 +
with message-id 
and subject line Bug#1065272: fixed in orc 1:0.4.34-4.1
has caused the Debian Bug report #1065272,
regarding orc: 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.)


-- 
1065272: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065272
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: orc
Version: 1:0.4.34-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: orc
Source-Version: 1:0.4.34-4.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
orc, 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.
Michael Hudson-Doyle  (supplier of updated orc 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: Mon, 04 Mar 2024 23:40:36 +1300
Source: orc
Built-For-Profiles: noudeb
Architecture: source
Version: 1:0.4.34-4.1
Distribution: unstable
Urgency: medium
Maintainer: Maintainers of GStreamer packages 
Changed-By: Michael Hudson-Doyle 
Closes: 1065272
Changes:
 orc (1:0.4.34-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065272)
Checksums-Sha1:
 0560a096612c2b386cbd7a8d2232a2a95b57f029 2430 orc_0.4.34-4.1.dsc
 460a135c057886fe00fb409b66d573567e0a75ba 12764 orc_0.4.34-4.1.debian.tar.xz
 528702895f8a943b0878774a725513c6d2c72e0d 8597 orc_0.4.34-4.1_source.buildinfo
Checksums-Sha256:
 d8525eb87f0c61193c67b5eb6989cfcd4b77f4ded15440917a0a32400ad9cb4d 2430 
orc_0.4.34-4.1.dsc
 5e432221b45a7fd7f3e94e134a5ceaec7b96ff059828a4c280d1e2d5091304cc 12764 
orc_0.4.34-4.1.debian.tar.xz
 7c92faadeb07c4a4aa0799a1e42b3d72b4657a3adc4abe10652c497d397c43a2 8597 
orc_0.4.34-4.1_source.buildinfo
Files:
 8f2a9af4b04a92609ef77fb344d90702 2430 devel optional orc_0.4.34-4.1.dsc
 4da59edaec26c198868e696ba0fe6cd1 12764 devel optional 
orc_0.4.34-4.1.debian.tar.xz
 3a4fcc179590e894723c83e5c3ae263f 8597 devel optional 
orc_0.4.34-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpTIACgkQEd9ClMyj
mJN0ZA/+PkQT9BhbufFGVisTkqY+tU6RIlv4t+rd9TCpC9qwCLgISdVoYiXFzb1X
DEDZOhmIPO4c/QAUJ3bKETd1KJmKpeMI2AmQcldnDPNWted3QkzfWRFTeYJr4D67
HVeY6G1OkNNEq2soou6fJR6VHewwpbBY539Wlqs5ZncWMTZEV410g4IdwxKc3MY9
/TM+3P6GEfmaQR4XbyB66a+5L3pf+ZFPCs7YAz/lpoEHow74tSim+805QcQohJ6Q
tK/yPJCD/jzdX6OqllUzcCL/vJ6iYXv+8y2KDWvslXkyMr7ZMXoHaTc7nSgcwW9O
O0JvNRhiMD0am6ath3eU1/tcGPn/wfpyNBuvQTwrVziKkUIjKDhbixSOyYjwkICV
B4lNbuRnimOwzmfcPUzL0Rjt7oa5n0b/1h+dcssGx69ebg8FyPhdsIm9QnhghwvI
LXlX1mMxiBGFkecqG7xWEAY+eAdDeWcywUfr6FuyiCHSSeNWlM6kclBHD0G1w0S5
FfmyrFDtEAB2xCsQBRJ7m+j9Jdud8Xxe70PyQlS54hbihP+1Bk3pU0SNuANPrOts
6VEU8mQlKK3Vmm6Go7hXSBTTgoG0gxII/yJPC+2lbgaSEbjY+ok5t2qFanTMGE2m
7pGdZysNPgnRwWKN7eXD3kbBjyfPP8LAr6Iz3ME59XcyLowVCBs=
=LvWN
-END PGP SIGNATURE-



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

Bug#1065277: marked as done (gtkmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:07:06 +
with message-id 
and subject line Bug#1065277: fixed in gtkmm2.4 1:2.24.5-5.1
has caused the Debian Bug report #1065277,
regarding gtkmm2.4: 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.)


-- 
1065277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkmm2.4
Version: 1:2.24.5-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: gtkmm2.4
Source-Version: 1:2.24.5-5.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
gtkmm2.4, 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.
Michael Hudson-Doyle  (supplier of updated gtkmm2.4 
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: Mon, 04 Mar 2024 23:40:46 +1300
Source: gtkmm2.4
Built-For-Profiles: noudeb
Architecture: source
Version: 1:2.24.5-5.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065277
Changes:
 gtkmm2.4 (1:2.24.5-5.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065277)
Checksums-Sha1:
 4cff7a6abf230415389bb5bea6cb1c2335f7731c 2360 gtkmm2.4_2.24.5-5.1.dsc
 12344699e6fc622fa4c6e8962759cc26fad7a69d 22860 
gtkmm2.4_2.24.5-5.1.debian.tar.xz
 ac62c3b7edb30799fe41fb967738ce30ed42fa68 14156 
gtkmm2.4_2.24.5-5.1_source.buildinfo
Checksums-Sha256:
 988e78cc56d9bab3611561a0a1d7ab5eb96abc454f4813efc3e043f21129acf0 2360 
gtkmm2.4_2.24.5-5.1.dsc
 da974f2fcf69f97fcecf519cf28f4d5aafd3ee435f6e2bc4ea7bb0f33fa37497 22860 
gtkmm2.4_2.24.5-5.1.debian.tar.xz
 217096f3c272686ff60bd2f6d5370cc5d270bb37bb07ae28327082e66a9696e0 14156 
gtkmm2.4_2.24.5-5.1_source.buildinfo
Files:
 b88c7a22dc5bdda6d24c87c03f8017dc 2360 oldlibs optional gtkmm2.4_2.24.5-5.1.dsc
 f1be3ab00119f2cc06fd2c864b4740a6 22860 oldlibs optional 
gtkmm2.4_2.24.5-5.1.debian.tar.xz
 945ef5573552530fc660ef4bfa893d19 14156 oldlibs optional 
gtkmm2.4_2.24.5-5.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpUAACgkQEd9ClMyj
mJPIFg//ZcEo5Hq92ZfR/CKJ2hawN+oBQLTRs/lET8PqFz9iJBJIHnaruMZY0GNW
GKkH19iTrxIL2tDaxELbwRilpM9t0uBFkWgBcXhJcQQ7EG+s43kaOYcYcaQpHcR+
ee20KeBphc+oZfUw0//2EAeTAh8iuvNzqpAZcVQwvtIuJYnQsfc+vDFUOirNyQjt
cy5zxNKE1JNTHCCdO0NOozUIuFlH3MCmXIAtJRFC1Lmr/SoavXArQK25SLc2v74G
Hz2wlgwdO8TxPxonLvcp3T/DUyKXprRX8wNd65jVc2j3tKn6LwYyN1bN6B51CpoH
cX3LO3cA0L2tkmrM6QOanv8ERnTaNctrrPkw97HS/fnpzr3SeS0Vfe0iblAZbGPX
lG9OJA5XNUOQ/Sjgl5DytaKYKpigk8wVMxHvB7jGfhxBehP5n8KB2sBOvCY9Uto5
on0tpjBzg39uejF5M+ENoomKvBP3uEpcbRXKQpnyt7u4z0GcBRi5UjOGwu57Cq0m
3/CmqlR9vveB0z7eXCYrVgO4aYAG5KoNWETyHQ02OMOyrhakL6AdPC0dkVMMqDWn
PuFyUFERWxkBQgwlEC9sUPyf6gtA3JU06vidguUhf4gF4Lk/VIfTczJ8Rb+1UFDb
cTfkf5OaT6KXP0T0k9YQuYqxX6i1t0nl082zVN+HWxgkF3tLhwM=
=FXrU
-END PGP SIGNATURE-



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

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

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:08:27 +
with message-id 
and subject line Bug#1065284: fixed in lucene++ 3.0.9-3.1
has caused the Debian Bug report #1065284,
regarding lucene++: 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.)


-- 
1065284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065284
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lucene++
Version: 3.0.9-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: lucene++
Source-Version: 3.0.9-3.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
lucene++, 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.
Michael Hudson-Doyle  (supplier of updated lucene++ 
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: Mon, 04 Mar 2024 23:42:22 +1300
Source: lucene++
Built-For-Profiles: noudeb
Architecture: source
Version: 3.0.9-3.1
Distribution: unstable
Urgency: medium
Maintainer: Łukasz 'sil2100' Zemczak 
Changed-By: Michael Hudson-Doyle 
Closes: 1065284
Changes:
 lucene++ (3.0.9-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065284)
Checksums-Sha1:
 16e1d14d0d3cd929160463dd5f2910c35f6b0407 2475 lucene++_3.0.9-3.1.dsc
 eb323b2b2051d2c69a24f6b3254b9f06eff22da2 8560 lucene++_3.0.9-3.1.debian.tar.xz
 31331e03e7ac9375b62af09be415bf978248c69d 9056 
lucene++_3.0.9-3.1_source.buildinfo
Checksums-Sha256:
 32fed34885e86f770a1f9d1f7ee49d5c1093b6dfa0bd83bd0ec4f685bb284a96 2475 
lucene++_3.0.9-3.1.dsc
 4d0442afd3c818319642596c76e49e2be700fb0d6ef0398331c9de4dd9f5f211 8560 
lucene++_3.0.9-3.1.debian.tar.xz
 19eb266546307043736219e094976f1eeb184460b06c8d4af35ba1680396bc68 9056 
lucene++_3.0.9-3.1_source.buildinfo
Files:
 e63d2ef1614de9aee61645c3e352bef6 2475 libs optional lucene++_3.0.9-3.1.dsc
 a25e992353ff6271afcfcdb665700b47 8560 libs optional 
lucene++_3.0.9-3.1.debian.tar.xz
 27650b8b7185ccf905715bb48eb6f23e 9056 libs optional 
lucene++_3.0.9-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpZsACgkQEd9ClMyj
mJMAzxAAk0QV+5Y83sS1Jpmh0PvKk6Q+AdMOC8cJsUh4IDCOSY5HTkBLGRnjRoO6
dhguX7C+mp8NxsMqQpH0p7AwC1GPJ8BySy3KqvmMx0R4TJQgwKIz+xYgondtnDEV
4RI/oZZMTRvqinkZcYC1a61X0C8/AkW+QiYK8xd1zzwq+6mR3s82TWN7iIiK8w3m
O6anKwOnFDhkRjtKJnLLWWZyEKUVCXE+dItXaoC5KFaEOGuvqCN5jI/7HOkNEaac
9ixIlMNfKoeyk3wr1hHqAKuZAPSC/pguKRIKi/nu14ahYmBm+gKgh0CtRSIxV/ZI
XU7AE+7bBQhLK6nwPFDijMEj3N79elRhK4Hpn30DlU3Fy7kKYpAin9Dak12g9k01
1B5VKPLAkmcvpcjN3kk9PdxJb2IqwCtSULyNAW9unxzIlFQI+5AHlaDJt3SA8E+b
oRCTTZ/FokpjsWc+AJfsvT2nxiXaPkDWRDFZQVUF6AniTWZ5ULirUrbiSSrDenXW
N1waiPvcMIaxUzWb3J70p1iX0yyDpEtdgDiDre7Dy2kJtr5J4uXxYY8kPPQKSBKU
uqb/QmFsZWxINVHXyK0q+5rdZbddu0Dnau3fVTAwvPdDEhfw5rIsdCOtXLEI1d9S
BYxlZt79WD42XfWsmN1agZTraS1f8M6n1+DGZV84CYbAY1kTomw=
=L91h
-END PGP SIGNATURE-



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

Bug#1065281: marked as done (evolution-data-server: missing dpkg-dev (>= 1.22.5) build dependnecy for time_t transition)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:06:24 +
with message-id 
and subject line Bug#1065281: fixed in evolution-data-server 3.50.3-2.1
has caused the Debian Bug report #1065281,
regarding evolution-data-server: missing dpkg-dev (>= 1.22.5) build dependnecy 
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.)


-- 
1065281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: evolution-data-server
Version: 3.51.2-1
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: evolution-data-server
Source-Version: 3.50.3-2.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
evolution-data-server, 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.
Michael Hudson-Doyle  (supplier of updated 
evolution-data-server 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: Mon, 04 Mar 2024 23:42:02 +1300
Source: evolution-data-server
Built-For-Profiles: noudeb
Architecture: source
Version: 3.50.3-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065281
Changes:
 evolution-data-server (3.50.3-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065281)
Checksums-Sha1:
 af655a18d20884ecf8e4871903552e081862cd11 5718 
evolution-data-server_3.50.3-2.1.dsc
 5b27d038de513ead3e764466ea4f521595bfa5dd 59436 
evolution-data-server_3.50.3-2.1.debian.tar.xz
 be57d4575c164763fbb30f23f5ee093766ea1fa1 19773 
evolution-data-server_3.50.3-2.1_source.buildinfo
Checksums-Sha256:
 ba17969f75ecbe3a14459515a0694744c51857e3853dd95cbbaf7eb97a3103e3 5718 
evolution-data-server_3.50.3-2.1.dsc
 3296bfe22cdb46a263c06a9370c0ad446ec5d5ec68fe9ab626068e27b017ef4c 59436 
evolution-data-server_3.50.3-2.1.debian.tar.xz
 98c15c9be60797010c39b01ff5c28580847997bb130f710cd5fc9450da98adf1 19773 
evolution-data-server_3.50.3-2.1_source.buildinfo
Files:
 1cb8120dfe0462ec8eb4a33e8b143a69 5718 gnome optional 
evolution-data-server_3.50.3-2.1.dsc
 3df5f4eb042ba7a421aa9ff3727e7849 59436 gnome optional 
evolution-data-server_3.50.3-2.1.debian.tar.xz
 ff80e3454f1b8fac59dda4fdfc51b0c3 19773 gnome optional 
evolution-data-server_3.50.3-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpYEACgkQEd9ClMyj
mJPA7RAAm0yK4VI22xTnnmGfKhYptbMpaXf3NT+924d4D2YLoBJgS6A5Q2SvekV8
6IUB1euWEENfBUAb2h7h+BS+G6EzY5veJ+JA+rgc1ycpWaZTVk8JNHPTQFS8+FvJ
ydPB4Mf7SNLHpYNePQKgsFjDJvVh9CLZEdK45ualwodSkwUeLFcTJgN5qLyw6ody
bh0JMnrRALvK+S9d6w+Kqb8ZUOSEnhYavhgguQDvgSPI0qEQUl7+huBHEuSfY/aP
Gj3jV9M8GdXBCdPKIZ6m9KDkC3SCM51lZ9vczGB+lVwwnfze2fTcsOXdxzatM2g2
TO+tSTValxX6W7aTiPJeWCCZfM7W59ACV1gLH2QlCRjMVXx8Qw7lhKs603fCkBnq
uENTFQ4nHYsBv42tOXdeMGYM9cXAeF+2igEPcwu2p1ch3jTr2y8rxWr7k8BHlW7H
AEQZJdWMwAgt3dQrGLZfbYoIi/qFm1bL3GBW4n2eEdMeaVh9sG94r9a9miqa6pJp
+wNPTjLNEB/uPKk9Y9ce4CuGaRkZB4/+f1wIHdGHx4xRRIbBBSXdAXZptFt4g2Wo
4FALMwjGuRBShHLcYQ3oM6ohImiK/e5hPPcQrnyCDmBBjLfRImxGVrKKeoeSmNt+
KMgkUDXLj99iXa+alV5B8NMmquBFovJMfEWuYqA8mFDzGBR2Eug=
=IapY
-END PGP SIGNATURE-



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

Bug#1065278: marked as done (gtkmm3.00: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:07:18 +
with message-id 
and subject line Bug#1065278: fixed in gtkmm3.0 3.24.8-3.1
has caused the Debian Bug report #1065278,
regarding gtkmm3.00: 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.)


-- 
1065278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065278
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtkmm3.0
Version: 3.24.8-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: gtkmm3.0
Source-Version: 3.24.8-3.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
gtkmm3.0, 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.
Michael Hudson-Doyle  (supplier of updated gtkmm3.0 
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: Mon, 04 Mar 2024 23:41:24 +1300
Source: gtkmm3.0
Built-For-Profiles: noudeb
Architecture: source
Version: 3.24.8-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065278
Changes:
 gtkmm3.0 (3.24.8-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065278)
Checksums-Sha1:
 8ebb735a45fde89510bfc7ad188e89468780b536 2514 gtkmm3.0_3.24.8-3.1.dsc
 090461b1d62a4caf34e40f00b8812ca22042a7bc 11172 
gtkmm3.0_3.24.8-3.1.debian.tar.xz
 3607448184b065069c87ea76991b84b6d2293689 18818 
gtkmm3.0_3.24.8-3.1_source.buildinfo
Checksums-Sha256:
 602abc72ad31e708638df4f444af7d7c1e5e0449ff61e6e0c61d9b8bcf330792 2514 
gtkmm3.0_3.24.8-3.1.dsc
 5c53555c2372e084df1f98f6e87357338aa106d47fe982862501dc4d1312debe 11172 
gtkmm3.0_3.24.8-3.1.debian.tar.xz
 4c517c89df145cd03789e4a963e4a0b55d715b9698f6ba5160bf55dedf1ffdf9 18818 
gtkmm3.0_3.24.8-3.1_source.buildinfo
Files:
 1ceb39b296c91c5be921d95032bcb291 2514 libs optional gtkmm3.0_3.24.8-3.1.dsc
 a6941ad745f7dca661a0bebcf0b739a4 11172 libs optional 
gtkmm3.0_3.24.8-3.1.debian.tar.xz
 de0b1fa9724a9e603fe6327e997c8dd5 18818 libs optional 
gtkmm3.0_3.24.8-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpV8ACgkQEd9ClMyj
mJM4uw/9GKYhc4JpuwOGP4+67MYLYjkAqkkNimtQeVHdv8r5gSbUEOuec0x0yB74
b1bgQ1GZKu4j5an4hjIHqk+2Lwzy735/eOqKG7ZRu51s0Vb6ZlOeZmsuFlW1v1fC
LxXoVbEyGkB6jChoh8aZL0fwiUTTxx6LocwpBWIosDxU6lanFjjFXt9f5tLewv+s
JoZW4D9qEIKdsR44X1j7RuovqqAD51BT0keTyMMHe4ylvwXKzpHkXxxZIQifQt1i
vJ4UsuGsTWoFqzbbFmyMV4vXkR3cFzbqdacJjJZvUyVPAO57dVvIvIiMNIyM6VtM
jjFdYWbQcUZGjzUzms0N1uA7FRQ1W29JmbgEkGL1wABffC/J9Nx3ky76oehiwO6W
2mpRR4C9m0h2am25Dzlzzs2xOz/h1D/IejpR8YNvom6OwPJw5+BevWiKggfPDeFd
4UH9hoJ3BV90by1od9eztMREgzLVuxYSngExA2q2puTN/Flk5EfREAyGcE3MFJ2K
GuW+3tq5tYluR4be40AXN5A3skm3olK7OgRrrULYN3WRflq4t7xKKbbmMzs5A0XQ
3KO11LO1JRL51TijQpPHXuXIRQ5UlqrnnkkMEuHW1k8d0hKibVl3QR0BRapiZr72
v+m4FDhAv+dDeINizVvV30KYl8fK9eytu5HKVjfd0x8DdEcOb/Y=
=D7Fz
-END PGP SIGNATURE-



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

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

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:08:12 +
with message-id 
and subject line Bug#1065279: fixed in libcanberra 0.30-12.1
has caused the Debian Bug report #1065279,
regarding libcanberra: 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.)


-- 
1065279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065279
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcanberra
Version: 0.30-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: libcanberra
Source-Version: 0.30-12.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
libcanberra, 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.
Michael Hudson-Doyle  (supplier of updated libcanberra 
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: Mon, 04 Mar 2024 23:41:54 +1300
Source: libcanberra
Built-For-Profiles: noudeb
Architecture: source
Version: 0.30-12.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065279
Changes:
 libcanberra (0.30-12.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065279)
Checksums-Sha1:
 9a1c9b746ecd0b203ea777b7cf4dc004d634a919 3012 libcanberra_0.30-12.1.dsc
 ef219af3fbb1855f4257dc4cca80dc43da085050 14568 
libcanberra_0.30-12.1.debian.tar.xz
 15618c2c08ec49f60215599b2c8ad15a99d45198 17692 
libcanberra_0.30-12.1_source.buildinfo
Checksums-Sha256:
 f38b25ebc16599b3ff87f619b9048d748c3a0ddfb85291d3a632f85605ddfc85 3012 
libcanberra_0.30-12.1.dsc
 4a7d66949bf2926b35bcdc24b7213a979c28855a2e1a80a9fe37a328eedc54d5 14568 
libcanberra_0.30-12.1.debian.tar.xz
 827de93f15d9258b3170dae6e067b2f811e8d224cec1bda81572959876ecdcdc 17692 
libcanberra_0.30-12.1_source.buildinfo
Files:
 448635a85ad9f5355035a16f841802cb 3012 libs optional libcanberra_0.30-12.1.dsc
 ae62eabfcbfcefd8058808da884e0db9 14568 libs optional 
libcanberra_0.30-12.1.debian.tar.xz
 19ccdf274ebc477d6d3c4b489c447d6f 17692 libs optional 
libcanberra_0.30-12.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpXoACgkQEd9ClMyj
mJNLLg/9FibavC5TCNfOnJfqtxh69OFdENQ3MjTRjf7f2mJOJYchw7TlCpTc3JNa
oU//Vd4vWYNMl2zeaIAyZ/UoQX9vW7dml6r4pbdqrPi+3rQK6RsctyVYOqhAfDOc
an6yGTzqYbxr1ffFnhO4U+6w1eLQBg6XJFDFrsvBsPnSTz2CBR72ulqeISQdHX1G
kfzwOrMKtlpCyKknQViNVCarjs9q/7oeQCe81yG/OEwXN9VCoLMdyAUd/I6r07QE
+zrJMChFBF5UdEaPb9ZFiUN6dsXBGR4y2VGNSaw/R23QS+uasupmBLOOhILp7jNu
ciWnU5etwyXXHtD8Fr9iyJlE7YiQGm061uXkF6m4vsfGFNegkVFs9k4bYGQGe5hh
w0OA2uc4+o5XN5Tjzfslwhc7L133TnDADZ2B20lmhpWNvEX0/xvw+AgZaNJiOOQL
Biy/AgZRb6bz8Naj941Vf+mlJhihZ9tcL1GPlEfbg0/ahuZsvdjyQNicTJl18QfG
ei35hqM0KYfSsTkedkiVFTw4vuA947iVxh10bsJrvFS0ee+QLXslPmZN3Vpcrovw
ELR6fbziIDtWZBMJv1kuvuAWwQL0uEeaE8D183e4jSRLRh3j4RR7tUifPW9dQMf2
rwpKwYTpJjG6aTuklUdRRN9pcJnjbnVUMO7uixIhbdX6qh4sYMw=
=tHPK
-END PGP SIGNATURE-



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

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

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:06:43 +
with message-id 
and subject line Bug#1065271: fixed in gsound 1.0.3-3.1
has caused the Debian Bug report #1065271,
regarding gsound: 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.)


-- 
1065271: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065271
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gsound
Version: 1.0.3-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: gsound
Source-Version: 1.0.3-3.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
gsound, 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.
Michael Hudson-Doyle  (supplier of updated gsound 
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: Mon, 04 Mar 2024 23:40:14 +1300
Source: gsound
Built-For-Profiles: noudeb
Architecture: source
Version: 1.0.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065271
Changes:
 gsound (1.0.3-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065271)
Checksums-Sha1:
 66d6815ced5c740dd3786155d914bbb937f37fad 2348 gsound_1.0.3-3.1.dsc
 d70affae390a0658fae5864d2b68a3c413819214 4080 gsound_1.0.3-3.1.debian.tar.xz
 26847c10a6ed4414bd817fe8b0c29ccef2d6f4c0 10597 
gsound_1.0.3-3.1_source.buildinfo
Checksums-Sha256:
 c8e395807d05b87e8f26501b768e06d21b2fb6bc64c398bbb3d993f84a609cf8 2348 
gsound_1.0.3-3.1.dsc
 33e7bf9b7a32ecef3346f8fbb2c8347a37fd1963676b3ebb33e84e49831c89f7 4080 
gsound_1.0.3-3.1.debian.tar.xz
 7ad1e9911d4a08b09b54610873118cd0b8eda9fa7d3094f04d62c727bc2a0abc 10597 
gsound_1.0.3-3.1_source.buildinfo
Files:
 57328727202a98c114f2c4e3039dc6f2 2348 gnome optional gsound_1.0.3-3.1.dsc
 fffe8cbdf22e49a35e4be774c2b4f6c7 4080 gnome optional 
gsound_1.0.3-3.1.debian.tar.xz
 73cc1571323eb2e6bc790135b26e05ca 10597 gnome optional 
gsound_1.0.3-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpRMACgkQEd9ClMyj
mJN79w/8DTLh13C7XUZZFRC5678TeQOnGpQHla+pPbWIrLXKWYGctbH8qgte/rwG
ASf3E65S29YmY9mHwyPZiWbbIkzq84cV+zTpPPeFPb42vzvpbtzT3ifnDQSkA6vB
4RmS+nP7HuRjfJQ5vvDNS/jeySGLcHYoGHgM1nmsMz3ORh6fHaKTO8+ffTgYaryt
nQKr6MwGrYhG65tMPKn256lt5C3PGbemu9e5tyh5y2RtLvUFTe0aJ4YReslGD4Hb
HRDGXrdQjaRa3ZC5yqDzgE8jK9PP1hIK6x1zPyKZ4e6HsFlJYXoi8lZ5f3yaWAjD
Aa5gnOWAVeT+/yjr4uTAltDQBtbtB0P/X76jtdewB6ccCrnLBtolhOyWl35ZOvY/
aZnRKiRJAEtWCOFnCoFPqtHxIUcJ4jjQh7v8tqq/u9q+JwdV3rkopZd4765gJqZX
U7g0Y+GlcTAqqolenH+CGpZv+h8zBYPE1Egg39jusz95e4hQRDbpbBHyUbhvoK8B
P8b71z1qxsK4uQfnYYLCR7c7CNC3cxDeW5WmdrKjT5h3DeTgXtkOLSSsA2v4Swur
220jsWuOvZbvla4ZjKcgmFrDWxyLvnWTn3+FqKmyzLygsEvLuyG0MqnKObKBuDVs
GDqe5lOX7I99l7shLPsClUBcsSpmWKhSofhB86DNqGqg30bbxeA=
=N1I4
-END PGP SIGNATURE-



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

Bug#1065269: marked as done (glibmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 11:06:35 +
with message-id 
and subject line Bug#1065269: fixed in glibmm2.4 2.66.6-3.1
has caused the Debian Bug report #1065269,
regarding glibmm2.4: 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.)


-- 
1065269: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065269
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glibmm2.4
Version: 2.66.6-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: glibmm2.4
Source-Version: 2.66.6-3.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
glibmm2.4, 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.
Michael Hudson-Doyle  (supplier of updated glibmm2.4 
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: Mon, 04 Mar 2024 23:39:52 +1300
Source: glibmm2.4
Built-For-Profiles: noudeb
Architecture: source
Version: 2.66.6-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065269
Changes:
 glibmm2.4 (2.66.6-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065269)
Checksums-Sha1:
 8387e2b5100e36e25407681185855d041a94c8a9 2302 glibmm2.4_2.66.6-3.1.dsc
 024e017f1fda3d6ed1c3ee5ca6b859e44a67186d 10356 
glibmm2.4_2.66.6-3.1.debian.tar.xz
 9216f803c930a9abc15793fb4b4dbfd94004ea63 13144 
glibmm2.4_2.66.6-3.1_source.buildinfo
Checksums-Sha256:
 66a449b1ccab1440b0d69cf2e00b97faad43e513dbbf09ab97449ca6a4ed960b 2302 
glibmm2.4_2.66.6-3.1.dsc
 99f084bc1f3af849b4b15d52bd963710251bf650fb710ca3e0542dd92fb4b55f 10356 
glibmm2.4_2.66.6-3.1.debian.tar.xz
 3eaa718d6ac7590c8e7497a6969cdab4bd690f2d4fe25b12bb3bf7f3498ef639 13144 
glibmm2.4_2.66.6-3.1_source.buildinfo
Files:
 2410deff0eb5b846e1e7512346464b4d 2302 libs optional glibmm2.4_2.66.6-3.1.dsc
 466d7cb6728da4e73020759d45c95ab3 10356 libs optional 
glibmm2.4_2.66.6-3.1.debian.tar.xz
 5a1148440a94df4db27cfaa4bf1ad7f3 13144 libs optional 
glibmm2.4_2.66.6-3.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpQEACgkQEd9ClMyj
mJNVBA/8DyI7v+oebvTr9j0FFUVYQb4Ky71Gcyn8/LDt+KEBm31pCKBLFOaxvtkk
hFQbAcs5wD/SBqnXOvShAkg7HT/wZXE0NrM0NBvZaKgNEx26PAjK9WkbQwn4oT6W
evYgrPIfr+ry4mg5KWseDYXguqTEkydsQA+Hv87zGpHa2i+9Dhuz7GtZ4U0SKYd3
m5iWxmMmYpb84RV6eeMkz2jwbEL8iR3VaRKFVwAjF5N2ilbN3ptDNuzA4LSaO+vq
Q9ZowNeZ/uvILwxogg7EfJgT27MD+9pwp7yg3WU5Wae3GNANVtBaQ/HjMBsQcMw1
bvg1xWX1n0UaPd5uYwQZJ2iSbCaf669zzHzVPSmVC5DuK9kHgIAp2YR0WWt0CMON
OmMqCNcaYS+YRDbStEi3ZfP+kqjUvtsJleQTHPVk6bBDuTw7ZnmUHfJSDFlOOuyj
//Yc1fXu1+APrJ7NRDCfZL9QtszQ+kxFqXdWCMPmCkeeXSrB1dNKpaQvwVqBXGBe
3sp8jVen8pAF8wYPJW+daixfcXSecqi16CJJ43Bjfaovjyy0Hhwb3zS9MvJqOHPY
7fEERSJobtoFWtsXOVUR+SeRq8UO5FgDSXQqabU8gj/wGqr26KSFamcarXHm7AYJ
RmT7sN6prkFcCZXle4NHtlw3vxhgLwl2ws5pWYhpDFU2QSZxYdc=
=7n7y
-END PGP SIGNATURE-



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

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

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 10:51:04 +
with message-id 
and subject line Bug#1065265: fixed in glade 3.40.0-4.1
has caused the Debian Bug report #1065265,
regarding glade: 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.)


-- 
1065265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: glade
Version: 3.40.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: glade
Source-Version: 3.40.0-4.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
glade, 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.
Michael Hudson-Doyle  (supplier of updated glade 
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: Mon, 04 Mar 2024 23:38:30 +1300
Source: glade
Built-For-Profiles: noudeb
Architecture: source
Version: 3.40.0-4.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065265
Changes:
 glade (3.40.0-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065265)
Checksums-Sha1:
 e6e6ee21f3a2743860a7b31300f5733c1b6f9e7f 3066 glade_3.40.0-4.1.dsc
 3c0b4d67176b4faa4ac89244235aa8233088e774 23484 glade_3.40.0-4.1.debian.tar.xz
 2a0e11982fa12115a01fd067dddae73101845670 19493 
glade_3.40.0-4.1_source.buildinfo
Checksums-Sha256:
 ad0f891d6ee3801e32b42d918549a8420cb9bf89bf5f00b5476328747bd88bbf 3066 
glade_3.40.0-4.1.dsc
 3e00ab95756246e735972ec07b38ca8f35ca7861eabdeba8fd2b85dcf6b5c8ef 23484 
glade_3.40.0-4.1.debian.tar.xz
 9c5f2e51802bf97c402e6aaa0592d3e5e0e06cba1973c986af8126fff1f2288a 19493 
glade_3.40.0-4.1_source.buildinfo
Files:
 c19e1883abbedd76cd4de984ad3c2922 3066 gnome optional glade_3.40.0-4.1.dsc
 f835e0f35ae8601692ef98440420af0b 23484 gnome optional 
glade_3.40.0-4.1.debian.tar.xz
 191136f9b75eb0a0d0cff3bfd64546fb 19493 gnome optional 
glade_3.40.0-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpMUACgkQEd9ClMyj
mJN/2A/+L9YQzu9X5d+8k10b0ympzdkXH7KRoGuvbNkL58LiEFmFKbBuWasut+C/
KWmTkm/7FNPJthcIID0agY6Of8DCuajdzyk4ItgvCE+wzeFH6HQ612SoKhI35pD2
qcVdm0tKr5GedchY3m/SJ7x9fDR2Ugb3PIAjMYLWAnOZ4qAxzqaS00EgFFDbXrj1
pr95Sg2IhJY/HBo6+d717H5wnoTKEwFCTJWB+dQaP45U15V9Lzb2PV8PG38UCyQn
PiBZU0XZGOQ2Db0gMKmiHih/58F/5NC85gFFrtsIrPLSPicPyc+2D5psaIMIwvnL
eVYeJiygMWAbHeyvZm+mTv39e0Dd1oPp5BKMbgYlEf8AebLwbU68drEpByr9oqFz
HHzoA8gxvThCD7E+kn8AB3cZMo+XkOHVtouK5Mnp5TATVh/v3+z8qfIA3fuEcl4n
taNKd8f002LSoIrY3W5dtTU8PzEqMaJUBQg9lQzQFuC7yYknfIJT5ZLxEzLHNvjh
c12L/YLNsZn3HVHZbosmImR4bLB2UKbEpm2488ott91y1wChkOSls0wzTulkle91
yeXZIpNIXVS9cgNGCko4OQcfbLI/DGf9d/J1DDrQJA1lOc0Ev4hIYaDFtxHVU6Ee
CdH7/YljKJ+tyIqirTdnYAEc6rIwjWULtvev0QiFkQMkSNVfVnE=
=JOOR
-END PGP SIGNATURE-



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

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

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gtkmm3.0-3.24.8/debian/changelog gtkmm3.0-3.24.8/debian/changelog
--- gtkmm3.0-3.24.8/debian/changelog2024-02-29 09:04:43.0 +1300
+++ gtkmm3.0-3.24.8/debian/changelog2024-03-04 23:41:24.0 +1300
@@ -1,3 +1,11 @@
+gtkmm3.0 (3.24.8-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065278)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 23:41:24 +1300
+
 gtkmm3.0 (3.24.8-3) unstable; urgency=medium
 
   * Use upstream patch to fix GdkRGBA test on i386
diff -Nru gtkmm3.0-3.24.8/debian/control gtkmm3.0-3.24.8/debian/control
--- gtkmm3.0-3.24.8/debian/control  2024-02-29 09:04:43.0 +1300
+++ gtkmm3.0-3.24.8/debian/control  2024-03-04 23:41:24.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: Jeremy Bícha 
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
doxygen,
graphviz,
libgtk-3-dev (>= 3.24.0),

Bug#1065252: marked as done (glibmm2.68: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 10:51:15 +
with message-id 
and subject line Bug#1065252: fixed in glibmm2.68 2.78.1-2.1
has caused the Debian Bug report #1065252,
regarding glibmm2.68: 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.)


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

Thank you for uploading the changes required for time_t transition.
Unfortunately, the upload missed adding dpkg-dev (>= 1.22.5) to
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
to Build-Depends and upload the new version ASAP.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: glibmm2.68
Source-Version: 2.78.1-2.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
glibmm2.68, 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.
Michael Hudson-Doyle  (supplier of updated glibmm2.68 
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: Mon, 04 Mar 2024 23:35:03 +1300
Source: glibmm2.68
Built-For-Profiles: noudeb
Architecture: source
Version: 2.78.1-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065252
Changes:
 glibmm2.68 (2.78.1-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065252)
Checksums-Sha1:
 ac199a1c18859346d000d3eaaf2fa1090cfed70f 2403 glibmm2.68_2.78.1-2.1.dsc
 3dad7f135a15dde350131b9b136d08e8342cb714 54672 
glibmm2.68_2.78.1-2.1.debian.tar.xz
 ad8d2424dc995130c9e60be3b94f5b849b3f4eee 13082 
glibmm2.68_2.78.1-2.1_source.buildinfo
Checksums-Sha256:
 71fc1c725d367cb7ba5ff159e2f79e2e8406418742f6a5bca9fd6567df434a04 2403 
glibmm2.68_2.78.1-2.1.dsc
 fb53e09434a47f21191a71de23e8a186cdddf544d904ce3fc527192f3479cdf3 54672 
glibmm2.68_2.78.1-2.1.debian.tar.xz
 3c233ae8bd8fdbdefcce82059b5547990e41cccd0240508842a9e079aa662c5e 13082 
glibmm2.68_2.78.1-2.1_source.buildinfo
Files:
 52cceaa2ff86a982655aaa2c812fbcd2 2403 libs optional glibmm2.68_2.78.1-2.1.dsc
 bb1a2b0101afa39a0a8901255d6d2333 54672 libs optional 
glibmm2.68_2.78.1-2.1.debian.tar.xz
 5a4fbdc6125c92559d1b23d703174375 13082 libs optional 
glibmm2.68_2.78.1-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpAUACgkQEd9ClMyj
mJOj0RAAj/QVCLroH1agvvn49gIyRlLbmY7ZjZkShbYPDhun8yO6H7aKkolNFrjs
w6Ik9/n7Cq0rEYdRa9yHF/ze7zyB3e1nZekshM9R5WXVYqFCr9/HZOVopKfn2sK1
akaYEBXZEZ+0Nv+eLnK/ST1/jbSiiZKuOIK25tbeUsSzknUosjpmQGRmOyXLuQvO
s2qe0ExUPRurYb4AQ4fAqL0MpOhBSd6/WfXFu7fMqMYgHlZyqmlSojMXqY84+NN6
lm7tO4w7PTX4kAR6Y/O7aXAZtdqr5kyatx9NRxzERqJQB6wqfRat26BWURy12FxS
aOxePzIgqC8cyiXKnTyWZuhBKkAWJ/gJi/1e/w/ZpQCUiFJ9vMQ4D0qvS5WEkmld
TnXoI8H4pJtahtNF/Q29EG1pbj0UW+iXFPozH6iDzeiX0Q+/OL52AQWgEzbSJ2S3
Yb3RTctPG5Y7Vh/FOy3vm090ieej7hY/qxo/lX/mVZaOWL+YpDiJ37M9gLzgMzMg
PeI8pAW5B3em1x+nRQOPJUxmYrmsD8+pbgYvVipVQJBahr1etFZiCdax5dRyGpBb
tvg09odq+9q0TAcvsffagr0ZhXGuIrm2oMliiKXpuRHm5XkPptI7u90TSa6fIafo
cIGEULFphnE9vYzQoEUTVuUTF7p9Ae/AWyYr5gzjAToV0yNaHqU=
=dqnR
-END PGP SIGNATURE-



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

Bug#1065284: lucene++: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru lucene++-3.0.9/debian/changelog lucene++-3.0.9/debian/changelog
--- lucene++-3.0.9/debian/changelog 2024-02-29 00:10:42.0 +1300
+++ lucene++-3.0.9/debian/changelog 2024-03-04 23:42:22.0 +1300
@@ -1,3 +1,11 @@
+lucene++ (3.0.9-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065284)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 23:42:22 +1300
+
 lucene++ (3.0.9-3) unstable; urgency=medium
 
   * Upload to sid
diff -Nru lucene++-3.0.9/debian/control lucene++-3.0.9/debian/control
--- lucene++-3.0.9/debian/control   2024-02-29 00:09:37.0 +1300
+++ lucene++-3.0.9/debian/control   2024-03-04 23:42:21.0 +1300
@@ -2,7 +2,8 @@
 Priority: optional
 Maintainer: Łukasz 'sil2100' Zemczak 
 Uploaders: Gianfranco Costamagna 
-Build-Depends: cmake,
+Build-Depends: dpkg-dev (>> 1.22.5),
+   cmake,
debhelper-compat (= 13),
libboost-date-time-dev,
libboost-filesystem-dev,

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

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru libcanberra-0.30/debian/changelog libcanberra-0.30/debian/changelog
--- libcanberra-0.30/debian/changelog   2024-02-29 09:08:28.0 +1300
+++ libcanberra-0.30/debian/changelog   2024-03-04 23:41:54.0 +1300
@@ -1,3 +1,11 @@
+libcanberra (0.30-12.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065279)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 23:41:54 +1300
+
 libcanberra (0.30-12) unstable; urgency=medium
 
   * Stop using debian/control.in and dh-sequence-gnome
diff -Nru libcanberra-0.30/debian/control libcanberra-0.30/debian/control
--- libcanberra-0.30/debian/control 2024-02-29 09:08:28.0 +1300
+++ libcanberra-0.30/debian/control 2024-03-04 23:41:54.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: Jeremy Bícha , Josselin Mouette 
, Laurent Bigonville , Marco Trevisan 
(Treviño) , Sjoerd Simons 
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
libltdl-dev | libltdl7-dev (>= 2.2.6),
libasound2-dev [linux-any],
libvorbis-dev,

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

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru glade-3.40.0/debian/changelog glade-3.40.0/debian/changelog
--- glade-3.40.0/debian/changelog   2024-02-28 15:41:41.0 +1300
+++ glade-3.40.0/debian/changelog   2024-03-04 23:38:30.0 +1300
@@ -1,3 +1,11 @@
+glade (3.40.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065265)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 
23:38:30 +1300
+
 glade (3.40.0-4) unstable; urgency=medium
 
   * Release to unstable (Closes: #1062127)
diff -Nru glade-3.40.0/debian/control glade-3.40.0/debian/control
--- glade-3.40.0/debian/control 2024-02-28 15:41:41.0 +1300
+++ glade-3.40.0/debian/control 2024-03-04 23:38:30.0 +1300
@@ -6,8 +6,9 @@
 Section: gnome
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

-Uploaders: Emilio Pozuelo Monfort , Laurent Bigonville 
, Marco Trevisan (Treviño) , Michael Biebl 

-Build-Depends: at-spi2-core ,
+Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha 
, Laurent Bigonville , Marco Trevisan 
(Treviño) , Michael Biebl 
+Build-Depends: dpkg-dev (>> 1.22.5),
+   at-spi2-core ,
dbus ,
debhelper-compat (= 13),
dh-sequence-gir,
diff -Nru glade-3.40.0/debian/control.in glade-3.40.0/debian/control.in
--- glade-3.40.0/debian/control.in  2024-02-28 15:41:41.0 +1300
+++ glade-3.40.0/debian/control.in  2024-03-04 23:38:30.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: @GNOME_TEAM@
-Build-Depends: at-spi2-core ,
+Build-Depends: dpkg-dev (>> 1.22.5),
+   at-spi2-core ,
dbus ,
debhelper-compat (= 13),
dh-sequence-gir,

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

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 10:50:50 +
with message-id 
and subject line Bug#1065260: fixed in gegl 1:0.4.48-2.1
has caused the Debian Bug report #1065260,
regarding gegl: 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.)


-- 
1065260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065260
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gegl
Version: 1:0.4.48-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: gegl
Source-Version: 1:0.4.48-2.1
Done: Michael Hudson-Doyle 

We believe that the bug you reported is fixed in the latest version of
gegl, 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.
Michael Hudson-Doyle  (supplier of updated gegl 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: Mon, 04 Mar 2024 23:38:29 +1300
Source: gegl
Built-For-Profiles: noudeb
Architecture: source
Version: 1:0.4.48-2.1
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Michael Hudson-Doyle 
Closes: 1065260
Changes:
 gegl (1:0.4.48-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
 (Closes: #1065260)
Checksums-Sha1:
 448e68899fa668caf8cf763e793497c5c1abdfb4 3197 gegl_0.4.48-2.1.dsc
 b0202b286858d2df57aa3a6a60aa62319ab4d3e9 25368 gegl_0.4.48-2.1.debian.tar.xz
 0baab0f2682ff15066a66afa843fbf49c1e1 18108 gegl_0.4.48-2.1_source.buildinfo
Checksums-Sha256:
 20c528e0c1468a7ba9d97f8474cc030b9f125261dce0baa5920501f8fd9939a0 3197 
gegl_0.4.48-2.1.dsc
 05a101e6c14f54f7ef95c6b57191673a82e117bedb15830b0d45006e63de 25368 
gegl_0.4.48-2.1.debian.tar.xz
 bcc75c45ac1daec2b503bbb24d7662c6738f0a67fc4b1a1dd6e9255b38d3df8c 18108 
gegl_0.4.48-2.1_source.buildinfo
Files:
 17f80e34fbb46e331b6ffe2e0ce5bb4d 3197 devel optional gegl_0.4.48-2.1.dsc
 b788c58721451a9cb1d3669c4930a277 25368 devel optional 
gegl_0.4.48-2.1.debian.tar.xz
 c35e8220f553003d6a62a1ba6a5efb32 18108 devel optional 
gegl_0.4.48-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEiiBE+E9xaoW3f/djEd9ClMyjmJMFAmXlpMkACgkQEd9ClMyj
mJPbGQ//S3PvvNFvFNmmy7CFFWclRaBvnXlIk+Ar3yDy9VBqec0qFSvelDLy+wZn
VR4hBwJAFQLGe4hqR7dm+38vRD3Ji0ES1SfOsbpOg7xaglisD54OGJ/SdfWo6ZV0
x+HhB0KnbkN/+oqx0PRFTyS3DNgtxvlIwy6u5pr/AaKS7Yi+tJJCTaejGgWodSmF
1ZSwFdyakNAV2woRcrs/mdRZ7H/+5o2NPmnPJK05GE7ShCq0K1rXXpTfjYNJW30B
iY7ceLcWdeNO3dLfZ4cbtnRcld2CnbXo2AxXN3/smb0E4lD6rqPCrPwD6VqgvghQ
aizbTfQPX3WMRobKjkfh/DEaWeZ5icsE48bOPmE78YXSrrXvoJy4otaL1g4DGoA+
/FfYW6HX7MYs8Ya7Mc5QVo1lbRtlBkS3JLbU/fUhzEjQnh27uZmhXY6LxfTmGEB5
h+wIAPzrnlQNHVDxbLFXr+JhaX0lduv8oauIrhAksmGX/m59xYhrUjQAx/0xn7ZP
qxdOQJt8baIwI41+pyoh59HrECCSWk2Ir9gzYK6G5fZe6GK+2sDTvha/Gxr4RvUj
lRk4foaEu56MjmbmoQSNP4QkmVzIYZ6XkML/kURzS0IiWq1I9/WREhPBMg6KYPvL
MAXuhZKTMyY6xF8jZkSfENkB1qqQapeUK4qiyHYIZC4CrSi4F4c=
=WEUz
-END PGP SIGNATURE-



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

Bug#1065252: glibmm2.68: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru glibmm2.68-2.78.1/debian/changelog glibmm2.68-2.78.1/debian/changelog
--- glibmm2.68-2.78.1/debian/changelog  2024-02-28 15:49:12.0 +1300
+++ glibmm2.68-2.78.1/debian/changelog  2024-03-04 23:35:03.0 +1300
@@ -1,3 +1,11 @@
+glibmm2.68 (2.78.1-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065252)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 23:35:03 +1300
+
 glibmm2.68 (2.78.1-2) unstable; urgency=medium
 
   * Release to unstable (Closes: #1062137)
diff -Nru glibmm2.68-2.78.1/debian/control glibmm2.68-2.78.1/debian/control
--- glibmm2.68-2.78.1/debian/control2024-02-28 15:49:12.0 +1300
+++ glibmm2.68-2.78.1/debian/control2024-03-04 23:35:03.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: Jeremy Bícha , Michael Biebl 
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
doxygen,
glib-networking ,
graphviz,

Bug#1065277: gtkmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gtkmm2.4-2.24.5/debian/changelog gtkmm2.4-2.24.5/debian/changelog
--- gtkmm2.4-2.24.5/debian/changelog2024-02-29 04:22:27.0 +1300
+++ gtkmm2.4-2.24.5/debian/changelog2024-03-04 23:40:46.0 +1300
@@ -1,3 +1,11 @@
+gtkmm2.4 (1:2.24.5-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065277)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 
23:40:46 +1300
+
 gtkmm2.4 (1:2.24.5-5) unstable; urgency=medium
 
   [ Jeremy Bícha ]
diff -Nru gtkmm2.4-2.24.5/debian/control gtkmm2.4-2.24.5/debian/control
--- gtkmm2.4-2.24.5/debian/control  2024-02-29 04:22:27.0 +1300
+++ gtkmm2.4-2.24.5/debian/control  2024-03-04 23:40:46.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha 

-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
libgtk2.0-dev (>= 2.24.0),
libglibmm-2.4-dev (>= 2.27.93),
libpangomm-1.4-dev (>= 2.27.1),

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

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru orc-0.4.34/debian/changelog orc-0.4.34/debian/changelog
--- orc-0.4.34/debian/changelog 2024-02-29 01:51:27.0 +1300
+++ orc-0.4.34/debian/changelog 2024-03-04 23:40:36.0 +1300
@@ -1,3 +1,11 @@
+orc (1:0.4.34-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065272)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 23:40:36 +1300
+
 orc (1:0.4.34-4) unstable; urgency=medium
 
   * Team upload
diff -Nru orc-0.4.34/debian/control orc-0.4.34/debian/control
--- orc-0.4.34/debian/control   2024-02-29 01:51:27.0 +1300
+++ orc-0.4.34/debian/control   2024-03-04 23:40:36.0 +1300
@@ -4,7 +4,8 @@
 Maintainer: Maintainers of GStreamer packages 
 Uploaders: Sebastian Dröge ,
Sjoerd Simons 
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
meson,
pkg-config,
gtk-doc-tools

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

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gsound-1.0.3/debian/changelog gsound-1.0.3/debian/changelog
--- gsound-1.0.3/debian/changelog   2024-02-29 03:29:46.0 +1300
+++ gsound-1.0.3/debian/changelog   2024-03-04 23:40:14.0 +1300
@@ -1,3 +1,11 @@
+gsound (1.0.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065271)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 
23:40:14 +1300
+
 gsound (1.0.3-3) unstable; urgency=medium
 
   * Stop using debian/control.in and dh-sequence-gnome
diff -Nru gsound-1.0.3/debian/control gsound-1.0.3/debian/control
--- gsound-1.0.3/debian/control 2024-02-29 03:29:46.0 +1300
+++ gsound-1.0.3/debian/control 2024-03-04 23:40:14.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: Jeremy Bícha , Laurent Bigonville 

-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
dh-sequence-gir,
gtk-doc-tools,
libcanberra-dev,

Bug#1065425: Does not upgrade from libpam0t64

[Christoph Berg]

Package: libpam0g
Version: 1.5.3-6
Severity: serious

On my sid system, libpam0g doesn't get upgraded because apt thinks the
libpam0t64 package is good enough:

$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

$ apt-cache policy libpam0t64
libpam0t64:
  Installed: 1.5.3-4
  Candidate: 1.5.3-4
  Version table:
 *** 1.5.3-4 100
100 /var/lib/dpkg/status

$ apt-cache policy libpam0g
libpam0g:
  Installed: (none)
  Candidate: 1.5.3-6
  Version table:
 1.5.3-6 500
500 http://deb.debian.org/debian sid/main amd64 Packages
 1.5.2-9.1+b1 -1
100 /var/lib/dpkg/status

Christoph

Bug#1065269: glibmm2.4: missing dpkg-dev (>= 1.22.5) build dependency for time_t transition

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru glibmm2.4-2.66.6/debian/changelog glibmm2.4-2.66.6/debian/changelog
--- glibmm2.4-2.66.6/debian/changelog   2024-02-28 15:45:03.0 +1300
+++ glibmm2.4-2.66.6/debian/changelog   2024-03-04 23:39:52.0 +1300
@@ -1,3 +1,11 @@
+glibmm2.4 (2.66.6-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065269)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 23:39:52 +1300
+
 glibmm2.4 (2.66.6-3) unstable; urgency=medium
 
   * Stop using debian/control.in and dh-sequence-gnome
diff -Nru glibmm2.4-2.66.6/debian/control glibmm2.4-2.66.6/debian/control
--- glibmm2.4-2.66.6/debian/control 2024-02-28 15:45:03.0 +1300
+++ glibmm2.4-2.66.6/debian/control 2024-03-04 23:39:52.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: Jeremy Bícha 
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
doxygen,
glib-networking ,
graphviz,

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

[Michael Hudson-Doyle]

Dear maintainer,

Please find attached a patch to add the dependency on dpkg-dev for the
time_t transition.  This patch is being uploaded to unstable.

Thanks!


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

Kernel: Linux 6.5.0-21-generic (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_NZ.UTF-8:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru gegl-0.4.48/debian/changelog gegl-0.4.48/debian/changelog
--- gegl-0.4.48/debian/changelog2024-02-28 15:37:42.0 +1300
+++ gegl-0.4.48/debian/changelog2024-03-04 23:38:29.0 +1300
@@ -1,3 +1,11 @@
+gegl (1:0.4.48-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Add build depedency on dpkg-dev (>= 1.22.5) for time_t transition.
+(Closes: #1065260)
+
+ -- Michael Hudson-Doyle   Mon, 04 Mar 2024 23:38:29 +1300
+
 gegl (1:0.4.48-2) unstable; urgency=medium
 
   * Release to unstable (Closes: #1062066)
diff -Nru gegl-0.4.48/debian/control gegl-0.4.48/debian/control
--- gegl-0.4.48/debian/control  2024-02-28 15:37:42.0 +1300
+++ gegl-0.4.48/debian/control  2024-03-04 23:38:29.0 +1300
@@ -3,7 +3,8 @@
 Priority: optional
 Maintainer: Debian GNOME Maintainers 

 Uploaders: Emilio Pozuelo Monfort , Jeremy Bícha 
, Josselin Mouette 
-Build-Depends: debhelper-compat (= 13),
+Build-Depends: dpkg-dev (>> 1.22.5),
+   debhelper-compat (= 13),
dh-sequence-gir,
dh-sequence-gnome,
gir1.2-babl-0.1-dev,

Processed: tagging 1065416, tagging 1065373, tagging 1065341, tagging 1064673 ..., tagging 1063345 ...

[Debian Bug Tracking System]

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

> tags 1065416 + experimental
Bug #1065416 [cross-toolchain-base] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Bug #1059786 [cross-toolchain-base] cross-toolchain-base: Migrating 
linux-libc-dev
Added tag(s) experimental.
Added tag(s) experimental.
> tags 1065373 + experimental
Bug #1065373 [src:heimdal] fix heimdal build with abi=time64
Added tag(s) experimental.
> tags 1065341 + experimental
Bug #1065341 [src:openstructure] src:openstructure: unsatisfied build 
dependency in testing: sip-dev
Added tag(s) experimental.
> tags 1064673 + experimental
Bug #1064673 {Done: Samuel Thibault } 
[python3-sphinxbase] pocketsphinx-python: FTBFS: ImportError: 
/usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.cpython-311-x86_64-linux-gnu.so:
 undefined symbol: SWIG_Python_str_AsChar
Added tag(s) experimental.
> found 1064673 0.8+5prealpha+1-16
Bug #1064673 {Done: Samuel Thibault } 
[python3-sphinxbase] pocketsphinx-python: FTBFS: ImportError: 
/usr/lib/python3/dist-packages/sphinxbase/_sphinxbase.cpython-311-x86_64-linux-gnu.so:
 undefined symbol: SWIG_Python_str_AsChar
Marked as found in versions sphinxbase/0.8+5prealpha+1-16.
> tags 1063345 + experimental
Bug #1063345 {Done: Stefano Rivera } [python3.12] 
python3.12: Segmentation fault in get_module_state_by_cls at 
../Modules/itertoolsmodule.c
Added tag(s) experimental.
> found 1063345 3.12.1-2
Bug #1063345 {Done: Stefano Rivera } [python3.12] 
python3.12: Segmentation fault in get_module_state_by_cls at 
../Modules/itertoolsmodule.c
Marked as found in versions python3.12/3.12.1-2.
> tags 1064753 - sid trixie
Bug #1064753 [src:dolphin-emu] dolphin-emu: FTBFS: Spirv.cpp:243:17: error: 
invalid use of incomplete type ‘class glslang::TIntermediate’
Removed tag(s) trixie and sid.
> tags 1064375 + sid trixie
Bug #1064375 [src:rust-gtk] rust-gtk: Unmaintained library should not be 
included in Trixie
Added tag(s) trixie and sid.
> found 1065336 0.10.1-4
Bug #1065336 [lxpanel] lxpanel: Depends: libfm-modules but is not installable
Marked as found in versions lxpanel/0.10.1-4.
> notfixed 1065258 starpu/1.4.3+dfsg-4
Bug #1065258 {Done: Samuel Thibault } 
[libstarpu-contribrm-1.4-1t64,libstarpu-contribfft-1.4-1t64,libstarpu-contribmpi-1.4-3t64,libstarpu-contrib-openmp-llvm-1.4-1t64,libsocl-contrib-1.4-1t64,libstarpu-contrib-1.4-4t64]
 6 packages from starpu-contrib have an undeclared file conflict
No longer marked as fixed in versions starpu/1.4.3+dfsg-4.
> severity 1060896 serious
Bug #1060896 [openafs-modules-dkms] openafs-modules-dkms: module build fails 
for Linux 6.7: osi_file.c:178:42: error: 'struct inode' has no member named 
'i_mtime'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1059786: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1059786
1060896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060896
1063345: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063345
1064375: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064375
1064673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064673
1064753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064753
1065258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065258
1065336: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065336
1065341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065341
1065373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065373
1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 cross-toolchain-base
Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Bug reassigned from package 'linux-libc-dev' to 'cross-toolchain-base'.
No longer marked as found in versions linux/6.7.7-1.
Ignoring request to alter fixed versions of bug #1065416 to the same values 
previously set
> forcemerge 1059786 -1
Bug #1059786 [cross-toolchain-base] cross-toolchain-base: Migrating 
linux-libc-dev
Bug #1059786 [cross-toolchain-base] cross-toolchain-base: Migrating 
linux-libc-dev
Added tag(s) sid and trixie.
Bug #1065416 [cross-toolchain-base] linux-libc-dev claims to provide 
linux-libc-dev-ARCH-cross, but it doesn't do that completely
Severity set to 'normal' from 'serious'
Added tag(s) patch.
Merged 1059786 1065416

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

Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely

[Bastian Blank]

Control: reassign -1 cross-toolchain-base
Control: forcemerge 1059786 -1

On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote:
> linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't
> do that completely

This is #1059786.  This lacks a response from you.  So I'm merging
those.

Bastian

-- 
There are always alternatives.
-- Spock, "The Galileo Seven", stardate 2822.3

Processed: closing 1065423

[Debian Bug Tracking System]

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

> close 1065423
Bug #1065423 [vlc-plugin-pipewire] vlc-plugin-pipewire uninstallable in 
unstable after vlc time_t transition
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1065423

[Debian Bug Tracking System]

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

> # no action from the maintainer required
> close 1065423
Bug #1065423 {Done: Sebastian Ramacher } 
[vlc-plugin-pipewire] vlc-plugin-pipewire uninstallable in unstable after vlc 
time_t transition
Bug 1065423 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1065423: vlc-plugin-pipewire uninstallable in unstable after vlc time_t transition

[Sebastian Ramacher]

On 2024-03-04 11:06:53 +0100, Christian Klein wrote:
> Package: vlc-plugin-pipewire
> Version: 3-3
> Severity: grave
> Justification: renders package unusable
> X-Debbugs-Cc: dvl...@gmail.com
> 
> vlc-plugin-pipewire depends on vlc-plugin-abi-3-0-0f. However, after the 
> time_t
> transition, the libvlccore9 package provides vlc-plugin-abi-3-0-0ft64.
> Due to this, the package can no longer be installed.
> 
> A simple rebuild of the package will likely already fix the problem.
> I wonder why this didn't happen automatically during the transition without 
> any
> manual intervention. Maybe the fact that the package depends on libvlccore9
> twice - once directly and once via vlc-plugin-abi-3-0-0f - causes this.

We are not yet there to schedule the archive wide rebuilds. The time_t
transition will take some time to complete. Please have some patience.

Closing as this bug does not require an action from the maintainer.

Cheers
-- 
Sebastian Ramacher

Bug#1065423: vlc-plugin-pipewire uninstallable in unstable after vlc time_t transition

[Christian Klein]

Package: vlc-plugin-pipewire
Version: 3-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: dvl...@gmail.com

vlc-plugin-pipewire depends on vlc-plugin-abi-3-0-0f. However, after the time_t
transition, the libvlccore9 package provides vlc-plugin-abi-3-0-0ft64.
Due to this, the package can no longer be installed.

A simple rebuild of the package will likely already fix the problem.
I wonder why this didn't happen automatically during the transition without any
manual intervention. Maybe the fact that the package depends on libvlccore9
twice - once directly and once via vlc-plugin-abi-3-0-0f - causes this.


-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (999, 'unstable'), (998, 'testing'), (990, 'stable'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'proposed-updates'), (350, 
'experimental'), (1, 'experimental-debug')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

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

Versions of packages vlc-plugin-pipewire depends on:
ii  libc6 2.38-6
ii  libpipewire-0.3-0t64 [libpipewire-0.3-0]  1.0.3-1.1
ii  libvlccore9 [vlc-plugin-abi-3-0-0f]   3.0.20-1+b2

vlc-plugin-pipewire recommends no packages.

vlc-plugin-pipewire suggests no packages.

-- no debconf information

Bug#1002148: marked as done (qwertone: FTBFS: unsatisfiable build-dependencies)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 09:01:05 +
with message-id 
and subject line Bug#1002148: fixed in qwertone 0.4.0-1
has caused the Debian Bug report #1002148,
regarding qwertone: FTBFS: unsatisfiable build-dependencies
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.)


-- 
1002148: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002148
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qwertone
Version: 0.3.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211220 ftbfs-bookworm

Hi,

During a rebuild of all packages in sid, your package failed to build
on amd64.


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 12), dh-cargo (>= 18), cargo, 
> rustc, libstd-rust-dev, librust-cairo-rs-0+default-dev (>= 0.7-~~), 
> librust-cpal-0+default-dev (>= 0.10.0-~~), librust-lazy-static-1+default-dev 
> (>= 1.3.0-~~), librust-crossbeam-channel-0+default-dev (>= 0.3-~~), 
> librust-crossbeam-utils-0+default-dev (>= 0.6-~~), librust-gio-0+default-dev 
> (>= 0.7-~~), librust-gtk-0.7+v3-22-dev (>= 0.7-~~), librust-gdk-0+default-dev 
> (>= 0.11-~~), build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 12), dh-cargo (>= 18), cargo, 
> rustc, libstd-rust-dev, librust-cairo-rs-0+default-dev (>= 0.7-~~), 
> librust-cpal-0+default-dev (>= 0.10.0-~~), librust-lazy-static-1+default-dev 
> (>= 1.3.0-~~), librust-crossbeam-channel-0+default-dev (>= 0.3-~~), 
> librust-crossbeam-utils-0+default-dev (>= 0.6-~~), librust-gio-0+default-dev 
> (>= 0.7-~~), librust-gtk-0.7+v3-22-dev (>= 0.7-~~), librust-gdk-0+default-dev 
> (>= 0.11-~~), build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [963 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [499 B]
> Get:5 copy:/<>/apt_archive ./ Packages [587 B]
> Fetched 2049 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> 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:
>  librust-cairo-rs+use-glib-dev : Depends: librust-cairo-rs-dev (= 0.7.1-1+b1) 
> but it is not going to be installed
>  Depends: 
> librust-cairo-sys-rs-0.9+use-glib-dev but it is not installable
>  Depends: librust-glib-0.8+default-dev
>  Depends: librust-glib-sys-0.9+default-dev 
> but it is not installable
>  Depends: librust-gobject-sys-0.9+default-dev 
> but it is not installable
>  librust-gdk-dev : Depends: librust-cairo-sys-rs-0.9+default-dev but it is 
> not installable
>Depends: librust-gdk-pixbuf-0.7+default-dev
>Depends: librust-gio-sys-0.9+default-dev but it is not 
> installable
>Depends: librust-glib-0.8+default-dev
>Depends: librust-glib-sys-0.9+default-dev but it is not 
> installable
>Depends: librust-gobject-sys-0.9+default-dev but it is not 
> installable
>Depends: librust-pango-0.7+default-dev
>  librust-gdk-sys-dev : Depends: librust-cairo-sys-rs-0.9+default-dev but it 
> is not installable
>Depends: librust-gdk-pixbuf-sys-0.9+default-dev but it 
> is not installable
>Depends: librust-gio-sys-0.9+default-dev but it is not 
> installable
>Depends: librust-glib-sys-0.9+default-dev but it is 
> not installable
>Depends: librust-gobject-sys-0.9+default-dev but it is 
> not installable
>

Processed: your mail

[Debian Bug Tracking System]

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

> forwarded 1064598 https://github.com/jonathanwin/yagv/issues/25
Bug #1064598 [yagv] yagv: crashes with "module 'pyglet.graphics' has no 
attribute 'vertex_list'"
Set Bug forwarded-to-address to 'https://github.com/jonathanwin/yagv/issues/25'.
> thanks
Stopping processing here.

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

Bug#1065388: marked as done (libqt5core5t64: control files are wrong for all t64 qt libraries)

[Debian Bug Tracking System]

Your message dated Mon, 04 Mar 2024 09:00:26 +0100
with message-id <2317368.ElGaqSPkdT@dabney>
and subject line Re: Bug#1065388: libqt5core5t64: control files are wrong for 
all t64 qt libraries
has caused the Debian Bug report #1065388,
regarding libqt5core5t64: control files are wrong for all t64 qt libraries
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.)


-- 
1065388: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065388
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libqt5core5t64
Version: 5.15.10+dfsg-7.1
Severity: grave
Justification: renders package unusable

Package: libqt5core5t64
Source: qtbase-opensource-src
Version: 5.15.10+dfsg-7.1
Architecture: amd64
Maintainer: Debian Qt/KDE Maintainers 
Installed-Size: 6061
Depends: shared-mime-info, libc6 (>= 2.35), libdouble-conversion3 (>= 2.0.0), 
libgcc-s1 (>= 3.4), libglib2.0-0t64 (>= 2.22.0), libicu72 (>= 72.1~rc-1~), 
libpcre2-16-0 (>= 10.22), libstdc++6 (>= 11), libzstd1 (>= 1.5.5), zlib1g (>= 
1:1.1.4)
Recommends: qttranslations5-l10n
Suggests: libthai0
Breaks: libqt5core5a (<< 5.15.10+dfsg-7.1)
Replaces: libqt5core5a
Provides: libqt5core5a (= 5.15.10+dfsg-7.1), qtbase-abi-5-15-10
Section: libs
Priority: optional
Multi-Arch: same
Homepage: https://www.qt.io/developers/
Description: Qt 5 core module
 Qt is a cross-platform C++ application framework. Qt's primary feature
 is its rich set of widgets that provide standard GUI functionality.
 .
 The QtCore module contains core non-GUI functionality.


The Breaks: makes apt to search for a  libqt5core5a >=  5.15.10+dfsg-7.1 but it
will never exist as long as the package is not FIRST replaced by the t64 
version.

Removing the Breaks: make it installable and the provides expose the 
libqt5core5a
as present.

It has been stuck for 5 days already and I do not think this is due to the 
transition
(except many package are uninstalable due to various error in control files).

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

Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF8, LC_CTYPE=fr_FR.UTF8 (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 libqt5core5t64 depends on:
ii  libc6  2.38-6
ii  libdouble-conversion3  3.3.0-1+b1
ii  libgcc-s1  14-20240221-2.1
ii  libglib2.0-0t642.78.4-2.1+b1
ii  libicu72   72.1-4+b1
ii  libpcre2-16-0  10.42-4+b1
ii  libstdc++6 14-20240221-2.1
ii  libzstd1   1.5.5+dfsg2-2
ii  shared-mime-info   2.4-1
ii  zlib1g 1:1.3.dfsg-3.1

Versions of packages libqt5core5t64 recommends:
ii  qttranslations5-l10n  5.15.10-2

Versions of packages libqt5core5t64 suggests:
ii  libthai0  0.1.29-2
--- End Message ---
--- Begin Message ---
On Sunday, March 3, 2024 6:31:20 PM CET Eric Valette wrote:
> Package: libqt5core5t64
> Version: 5.15.10+dfsg-7.1
> Severity: grave
> Justification: renders package unusable

The t64 transition is still in progress. This should settle without maintainer 
interaction within a couple of weeks. Until then, please be careful with 
upgrades on unstable.

Given this doesn't require maintainer interaction, I'm closing this report.

/Sune
-- 
I didn’t stop pretending when I became an adult, it’s just that when I was a 
kid I was pretending that I fit into the rules and structures of this world. 
And now that I’m an adult, I pretend that those rules and structures exist.
   - zefrank--- End Message ---