Bug#1021894: marked as done (openjfx: FTBFS on arm64 and armhf)

[Debian Bug Tracking System]

Your message dated Sun, 16 Jul 2023 05:51:46 +
with message-id 
and subject line Bug#1021894: fixed in openjfx 11.0.11+1-3.1
has caused the Debian Bug report #1021894,
regarding openjfx: FTBFS on arm64 and armhf
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.)


-- 
1021894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openjfx
Version: 11.0.11+1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

openjfx FTBFS on arm64 and armhf for some time now. Let's record that in
the BTS.

https://buildd.debian.org/status/fetch.php?pkg=openjfx&arch=arm64&ver=11.0.11%2B1-1&stamp=1651592229&raw=0

:web:compileNativeLinux FAILED
:web:compileNativeLinux (Thread[Task worker for ':' Thread 3,5,main]) 
completed. Took 10 mins 30.851 secs.

FAILURE: Build failed with an exception.

* Where:
Build file '/<>/build.gradle' line: 3922

* What went wrong:
Execution failed for task ':web:compileNativeLinux'.
> Process 'command 'perl'' finished with non-zero exit value 2

* Try:
Run with --debug option to get more log output. Run with --scan to get full 
insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task 
':web:compileNativeLinux'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:100)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:70)
at 
org.gradle.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:62)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:60)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:97)
at 
org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:87)
at 
org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)
at 
org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)
at 
org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker$1.run(DefaultTaskGraphExecuter.java:248)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:336)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:328)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:199)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:110)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:241)
at 
org.gradle.execution.taskgraph.DefaultTaskGraphExecuter$EventFiringTaskWorker.execute(DefaultTaskGraphExecuter.java:230)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.processTask(DefaultTaskPlanExecutor.java:123)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker.access$200(DefaultTaskPlanExecutor.java:79)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:104)
at 
org.gradle.execution.taskgraph.DefaultTaskPlanExecutor$TaskExecutorWorker$1.execute(DefaultTaskPlanExecutor.java:98)
at 
org.gradle.execution.taskgraph.DefaultTaskExecutionPlan.execute(DefaultTaskExecutionPlan.java:626)
at 
org.gradle.execution.taskgraph

Bug#1021894: openjfx: FTBFS on arm64 and armhf

[tony mancill]

On Sat, Jul 15, 2023 at 01:46:02PM -0700, tony mancill wrote:
> I intend to build and upload in the next few days, but you are welcome
> to NMU if you would prefer.

Uploaded as 11.0.11+1-3.1.  (The version number was a slight mistake on
my part; I meant to remove the NMU suffix in the changelog before the
upload.  I will fix it on the next upload.)

Processed: Bug#1021894 marked as pending in openjfx

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1021894 [src:openjfx] openjfx: FTBFS on arm64 and armhf
Added tag(s) pending.

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

Bug#1021894: marked as pending in openjfx

[Tony Mancill]

Control: tag -1 pending

Hello,

Bug #1021894 in openjfx 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/java-team/openjfx/-/commit/f2d3ac36ed45d414a8b7751588a5f02ec9358680


Add patch for FTBFS on arm64 and armhf (Closes: #1021894)

Thank you to Wookey for identifying the issue and a temporary
workaround.


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1021894

Bug#1037685: guitarix: ftbfs with GCC-13

[Hermann Meyer]

Hi

This bug is already fixed in upstream, here is the related patch:

https://github.com/brummer10/guitarix/commit/b52736180b6966f24398f8a5ad179a58173473ec


regards

hermann

Processed: Bug#1038486 marked as pending in devscripts

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1038486 {Done: Paul Gevers } [src:devscripts] 
devscripts: FTBFS + autopkgtest failure with libgitlab-api-v4-perl 0.27-1
Bug #1041220 {Done: Paul Gevers } [src:devscripts] 
src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers 
autopkgtest regression in devscripts
Added tag(s) pending.
Added tag(s) pending.

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

Processed: reassign 1041220 to src:devscripts, forcibly merging 1041220 1038486

[Debian Bug Tracking System]

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

> reassign 1041220 src:devscripts
Bug #1041220 {Done: Paul Gevers } [devscripts] 
src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers 
autopkgtest regression in devscripts
Bug reassigned from package 'devscripts' to 'src:devscripts'.
Ignoring request to alter found versions of bug #1041220 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1041220 to the same values 
previously set
> forcemerge 1041220 1038486
Bug #1041220 {Done: Paul Gevers } [src:devscripts] 
src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers 
autopkgtest regression in devscripts
Bug #1038486 [src:devscripts] devscripts: FTBFS + autopkgtest failure with 
libgitlab-api-v4-perl 0.27-1
1041220 was blocked by: 1038486
1041220 was not blocking any bugs.
Removed blocking bug(s) of 1041220: 1038486
Marked Bug as done
Bug #1041220 {Done: Paul Gevers } [src:devscripts] 
src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers 
autopkgtest regression in devscripts
Marked as found in versions devscripts/2.23.5.
Added tag(s) ftbfs and patch.
Merged 1038486 1041220
> thanks
Stopping processing here.

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

Bug#1038486: marked as pending in devscripts

[Yadd]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian/devscripts/-/commit/27510296e4159b8b9f2369054e8322bcce80c158


Update changelog

Closes: #1038486


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1038486

Processed (with 1 error): reassign 1041220 to devscripts, forcibly merging 1041220 1038486

[Debian Bug Tracking System]

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

> reassign 1041220 devscripts
Bug #1041220 {Done: Paul Gevers } 
[src:libgitlab-api-v4-perl] src:libgitlab-api-v4-perl: fails to migrate to 
testing for too long: triggers autopkgtest regression in devscripts
Bug reassigned from package 'src:libgitlab-api-v4-perl' to 'devscripts'.
No longer marked as found in versions libgitlab-api-v4-perl/0.26-3.
No longer marked as fixed in versions libgitlab-api-v4-perl/0.27-1.
> forcemerge 1041220 1038486
Bug #1041220 {Done: Paul Gevers } [devscripts] 
src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers 
autopkgtest regression in devscripts
Unable to merge bugs because:
package of #1038486 is 'src:devscripts' not 'devscripts'
Failed to forcibly merge 1041220: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Bug#1041220: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

[Yadd]

On 7/15/23 22:46, Paul Gevers wrote:

Source: libgitlab-api-v4-perl
Version: 0.26-3
Severity: serious
Control: close -1 0.27-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038486

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:libgitlab-api-v4-perl has been trying to 
migrate for 32 days [2]. Hence, I am filing this bug. The package in 
unstable triggers an autopkgtest issue in devscripts, which is reported 
in bug 1038486.


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


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


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


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


Paul


Hi,

the error looks to be:

 55s t/salsa-config.t .. ok
 56s Undefined subroutine &JSON::to_json called at ./t/salsa.pm line 49.
 56s # Tests were run but no plan was declared and done_testing() was 
not seen.

 56s # Looks like your test exited with 255 just after 1.
 56s t/salsa.t .

Gitlab::API::v4 uses JSON::MaybeXS which may use a different JSON stack. 
I just added a "use JSON" in t/salsa.pm. Maybe this is enough to fix 
this issue


https://salsa.debian.org/debian/devscripts/-/commit/5bbc8778

Regards,
Yadd

Bug#1041230: onetbb 2021.9.0-1 FTBFS on multiple release architectures

[M. Zhou]

Source: onetbb
Version: 2021.9.0-1
Severity: serious

I'm aware of this issue. I'm slightly faster than buildd for toolchain
upgrades. The issue will automatically disappear once our amd64 buildd
migrates to gcc-13. The gcc-12 will lead to the FTBFS you see now.

Local sbuild with gcc-13 has no issue.

Bug#965826: marked as done (stalonetray: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 23:21:48 +
with message-id 
and subject line Bug#965826: fixed in stalonetray 0.8.3-1
has caused the Debian Bug report #965826,
regarding stalonetray: Removal of obsolete debhelper compat 5 and 6 in bookworm
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.)


-- 
965826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stalonetray
Version: 0.8.1-1
Severity: normal
Usertags: compat-5-6-removal

Hi,

The package stalonetray uses debhelper with a compat level of 5 or 6,
which is deprecated and scheduled for removal[1].

Please bump the debhelper compat at your earliest convenience
/outside the freeze/!

  * Compat 13 is recommended (supported in stable-backports)

  * Compat 7 is the bare minimum


PLEASE KEEP IN MIND THAT the release team *DOES NOT* accept uploads
with compat bumps during the freeze.

If there is any risk that the fix for this bug might not migrate to
testing before 2021-01-01[3] then please postpone the fix until after
the freeze.


At the time of filing this bug, compat 5 and 6 are expected to be
removed "some time during the development cycle of bookworm".


Thanks,
~Niels


[1] https://lists.debian.org/debian-devel/2020/07/msg00065.html

[2] https://release.debian.org/bullseye/FAQ.html

[3] The choice of 2021-01-01 as a "deadline" is set before the actual
freeze deadline to provide a safe cut off point for most people.

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Source: stalonetray
Source-Version: 0.8.3-1
Done: Varun Hiremath 

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

Debian distribution maintenance software
pp.
Varun Hiremath  (supplier of updated stalonetray 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: Sun, 09 Jul 2023 20:20:08 -0700
Source: stalonetray
Architecture: source
Version: 0.8.3-1
Distribution: unstable
Urgency: medium
Maintainer: Roman Dubtsov 
Changed-By: Varun Hiremath 
Closes: 802789 965826
Changes:
 stalonetray (0.8.3-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #802789)
   * Update debian/rules to use dh for build
   * Remove debain/orig-tar.sh
   * Remove debian/compat, update to version 13 (Closes: #965826)
   * Remove debian/patches no longer needed
   * Update debian/watch version
   * Update debian/copyright file to new dep5 version
   * Update Standards-Version to 4.6.2
Checksums-Sha1:
 c50c2c116508915db5230080b0957b828dce068c 1946 stalonetray_0.8.3-1.dsc
 b552b0f7c099e12b6b3f82991b0f749eac7a2825 200349 stalonetray_0.8.3.orig.tar.gz
 38482e2a18a714ffcb645a8312c114f0d3cedcd2 2612 stalonetray_0.8.3-1.debian.tar.xz
 77a26fe49bc00db078cb8270a87ee27be8238b56 6872 
stalonetray_0.8.3-1_amd64.buildinfo
Checksums-Sha256:
 b2bc04dc1c99b4701671769ed51ec0a57a07dcd2631f6161acb126bcde3d3890 1946 
stalonetray_0.8.3-1.dsc
 9f630464ef9ac1419c7e1808aaf37529d6a18a9df6ef81c9b89b2fad31c6311b 200349 
stalonetray_0.8.3.orig.tar.gz
 025af9536737dfde4d6a8214d143706d812c6d84095eae24b8a07514a7b7a6fa 2612 
stalonetray_0.8.3-1.debian.tar.xz
 1e882149bd9703cc5f3e2d9e6422e3d117ebeaae60c55d8953bf453e5e77e542 6872 
stalonetray_0.8.3-1_amd64.buildinfo
Files:
 c10ee76a8c4df9a8cd7f51b09f3afa1d 1946 x11 optional stalonetray_0.8.3-1.dsc
 28b7472c5ced61a74181a3249eed19f4 200349 x11 optional 
stalonetray_0.8.3.orig.tar.gz
 479f7e1482e16c790755f00b2167c288 2612 x11 optional 
stalonetray_0.8.3-1.debian.tar.xz
 d4efa07fd712071cdfac2b59698212e4 6872 x11 optional 
stalonetray_0.8.3-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEDBnIgiN9JdQ7ikG+cDc88SkNuc4FAmSzISwACgkQcDc88SkN
uc5PdhAAgBx7glNI0XZCmSGm/eNAOrwlk2og3Ro5o5GFBWfOcvb5KaFHj0sB9z7y
67VXHZM1D9+S5ardeJrpCnfZu9d925DOT5QCxRd7vZEv29d9x+nBVePtWHTZToF/
pKtXiNyIGUbT6ntRSpiLqpanO90Ehc1m1qGFfjHpFJBzr0zxG5cEjz3LsceVsz7N
rsdEQMjiBV/s31NUNxOWkp9ITY+GcuB2skwZFW8v++flvYM1tVk6NA9lXKtgLltY
MXCt

Bug#1041162: bogus test triggers with unused compilers

[Andreas Beckmann]

On 15/07/2023 12.11, Matthias Klose wrote:

Package: src:dkms
Version: 3.0.11-3



seen with
https://ci.debian.net/data/autopkgtest/testing/amd64/d/dkms/35776414/log.gz


That's an autopkgtest pinning problem:

autopkgtest uses this command to build the list of binary packages to 
pin for these flags:

  --add-apt-release=unstable --pin-packages=unstable=src:gcc-12

apt-cache showsrc gcc-12 | awk '/^Package-List:/ { show=1; next } (/^ / 
&& show==1) { print $1; next } { show=0 }' |sort -u | tr '\n' ' '


Unfortunately that includes obsolete information from Extra-Source-Only 
packges, e.g.


Package: gcc-12
Binary: gcc-12-base, libgcc-s1, libgcc-s2, libgcc-s4, libgcc-12-dev, 
lib64gcc-s1, lib64gcc-12-dev, lib32gcc-s1, lib32gcc-12-dev, 
libn32gcc-s1, libn32gcc-12-dev, libx32gcc-s1, libx32gcc-12-dev, gcc-12, 
gcc-12-multilib, gcc-12-test-results, gcc-12-plugin-dev,,
 libx32objc4, gfortran-12, gfortran-12-multilib, libgfortran-12-dev, 
lib64gfortran-12-dev, lib32gfortran-12-dev, libn32gfortran-12-dev, 
libx32gfortran-12-dev, libgfortran5, lib64gfortran5, lib32gfortran5, 
libn32gfortran5, libx32gfortran5, gccgo-12, gccgo-12,
 gm2-12-doc, gcc-12-offload-nvptx, libgomp-plugin-nvptx1, 
gcc-12-offload-amdgcn, libgomp-plugin-amdgcn1,

 gcc-12-source
Version: 12.2.0-14
...
Homepage: http://gcc.gnu.org/
Package-List:
...
 libasan8 deb libs optional arch=any
...
Extra-Source-Only: yes


So it pins libasan8 to sid because it believes that is built from 
src:gcc-12, but that is now built from src:gcc-13 and all binary 
packages built by src:gcc-13 that were never built by src:gcc-12 are 
pinned to testing ... and that makes some packages uninstallable ...


Andreas

Bug#1039583: libltdl-dev: missing Breaks+Replaces: libltdl3-dev

[Vincent Lefevre]

Hi,

On 2023-06-27 14:50:30 +0200, Andreas Beckmann wrote:
> during a test with piuparts I noticed your package fails to upgrade from
> 'lenny' to 'squeeze' to 'wheezy' to 'jessie' to 'stretch' to 'buster'.
> It installed fine in 'lenny', and upgraded to 'squeeze', 'wheezy',
> 'jessie', 'stretch', 'buster', and 'bullseye'  successfully,
> but then the upgrade to 'bookworm' failed,
> because it tries to overwrite other packages files without declaring a
> Breaks+Replaces relation.

The added Breaks+Replaces is incorrect as it yields a fatal error
in dpkg, which cannot configure libltdl-dev 2.4.7-6:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041229

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

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

[Timo Röhling]

Hi Adam,

On Sat, 15 Jul 2023 18:27:24 +0200 Adam Borowski  wrote:

Packages built in an usrmerged chroot place such files under /usr while
built without usrmerge into whatever place they were installed to -- which
is a direct breach of the ruling.

Packages stage their files in debian/tmp or debian/PACKAGE, not in /
of the builder chroot, so the usr-merge state of the chroot has no
effect on the package file locations.


Cheers
Timo

--
⢀⣴⠾⠻⢶⣦⠀   ╭╮
⣾⠁⢠⠒⠀⣿⡁   │ Timo Röhling   │
⢿⡄⠘⠷⠚⠋⠀   │ 9B03 EBB9 8300 DF97 C2B1  23BF CC8C 6BDD 1403 F4CA │
⠈⠳⣄   ╰╯


signature.asc
Description: PGP signature

Bug#1041229: dependency problems prevent configuration of libltdl-dev

[Vincent Lefevre]

And "apt install -f" cannot fix the error.

I could downgrade the packages to testing (2.4.7-5), though.

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

Bug#1037819: marked as done (pistache: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 22:26:12 +
with message-id 
and subject line Bug#1037819: fixed in pistache 0.0.5+ds-5
has caused the Debian Bug report #1037819,
regarding pistache: ftbfs with GCC-13
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.)


-- 
1037819: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037819
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pistache
Version: 0.0.5+ds-3
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/pistache_0.0.5+ds-3_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
   52 | typedef typename TypeStorage::Type Type;
  |   ^~~~
../include/pistache/flags.h:26:16: note: declaration of ‘struct 
Pistache::detail::TypeStorage<4>’
   26 | struct TypeStorage;
  |^~~
../include/pistache/os.h: In function ‘Pistache::Polling::NotifyOn 
Pistache::Polling::operator&(NotifyOn, NotifyOn)’:
../include/pistache/flags.h:149:43: error: ‘UnderlyingType’ does not name a 
type; did you mean ‘__underlying_type’?
  149 | return static_cast(static_cast(lhs)  
  \
  |   ^~
../include/pistache/flags.h:154:5: note: in expansion of macro 
‘DEFINE_BITWISE_OP’
  154 | DEFINE_BITWISE_OP(&, T)\
  | ^
../include/pistache/os.h:76:9: note: in expansion of macro 
‘DECLARE_FLAGS_OPERATORS’
   76 | DECLARE_FLAGS_OPERATORS(NotifyOn)
  | ^~~
../include/pistache/flags.h:150:50: error: ‘UnderlyingType’ does not name a 
type; did you mean ‘__underlying_type’?
  150 |   Op static_cast(rhs)); 
  \
  |  ^~
../include/pistache/flags.h:154:5: note: in expansion of macro 
‘DEFINE_BITWISE_OP’
  154 | DEFINE_BITWISE_OP(&, T)\
  | ^
../include/pistache/os.h:76:9: note: in expansion of macro 
‘DECLARE_FLAGS_OPERATORS’
   76 | DECLARE_FLAGS_OPERATORS(NotifyOn)
  | ^~~
../include/pistache/os.h: In function ‘Pistache::Polling::NotifyOn 
Pistache::Polling::operator|(NotifyOn, NotifyOn)’:
../include/pistache/flags.h:149:43: error: ‘UnderlyingType’ does not name a 
type; did you mean ‘__underlying_type’?
  149 | return static_cast(static_cast(lhs)  
  \
  |   ^~
../include/pistache/flags.h:155:5: note: in expansion of macro 
‘DEFINE_BITWISE_OP’
  155 | DEFINE_BITWISE_OP(|, T)
  | ^
../include/pistache/os.h:76:9: note: in expansion of macro 
‘DECLARE_FLAGS_OPERATORS’
   76 | DECLARE_FLAGS_OPERATORS(NotifyOn)
  | ^~~
../include/pistache/flags.h:150:50: error: ‘UnderlyingType’ does not name a 
type; did you mean ‘__underlying_type’?
  150 |   Op static_cast(rhs)); 
  \
  |  ^~
../include/pistache/flags.h:155:5: note: in expansion of macro 
‘DEFINE_BITWISE_OP’
  155 | DEFINE_BITWISE_OP(|, T)
  | ^
../include/pistache/os.h:76:9: note: in expansion of macro 
‘DECLARE_FLAGS_OPERATORS’
   76 | DECLARE_FLAGS_OPERATORS(NotifyOn)
  | ^~~
[11/79] c++ -Isrc/libpistache.so.0.0

Bug#1041207: marked as done (debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 22:22:00 +
with message-id 
and subject line Bug#1041207: fixed in debootstrap 1.0.128+nmu4
has caused the Debian Bug report #1041207,
regarding debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE
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.)


-- 
1041207: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041207
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debootstrap
Version: 1.0.128+nmu3
Severity: grave

bluca's NMU on 2023-07-15 makes debootstrap produce chroots using the
aliased-dirs scheme.  While it's currently the default scheme for non-buildd
systems, it is both not supported by dpkg (with no solution in sight), but
is also likely to produce packages that are explicitely forbidden by a
recent CTTE ruling that disallows moving files between directories aliased
by the current usrmerge scheme.

Quoting the still unsolving issues is pointless (you can read about them
in massive threads in a number of places) as bluca seems to be ignoring
them completely.

But, what matters here is the CTTE ruling in #1035831 -- for the time being,
packages must not move files between locations affected by the aliasing.

Packages built in an usrmerged chroot place such files under /usr while
built without usrmerge into whatever place they were installed to -- which
is a direct breach of the ruling.

Thus, that change needs to be reverted for now, and all packages built
with 1.0.128+nmu3 need to be either rebuilt or at least checked for such
a violation (as most are unaffected).


Meow!
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-rc1-00036-gc493f11e457d (SMP w/64 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debootstrap depends on:
ii  wget  1.21.3-1+b2

Versions of packages debootstrap recommends:
ii  arch-test   0.21-1
ii  debian-archive-keyring  2023.3
ii  gnupg   2.2.40-1.1

Versions of packages debootstrap suggests:
ii  binutils 2.40.90.20230705-1
pn  squid-deb-proxy-client   
ii  ubuntu-archive-keyring   2020.06.17.1-1
ii  ubuntu-keyring [ubuntu-archive-keyring]  2020.06.17.1-1
ii  xz-utils 5.4.1-0.2
ii  zstd 1.5.5+dfsg2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: debootstrap
Source-Version: 1.0.128+nmu4
Done: Adam Borowski 

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

Debian distribution maintenance software
pp.
Adam Borowski  (supplier of updated debootstrap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 15 Jul 2023 23:32:31 +0200
Source: debootstrap
Architecture: source
Version: 1.0.128+nmu4
Distribution: unstable
Urgency: medium
Maintainer: Debian Install System Team 
Changed-By: Adam Borowski 
Closes: 1041207
Changes:
 debootstrap (1.0.128+nmu4) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Revert defaulting buildds to usrmerge, as this makes packages move
 files in aliased dirs contrary to CTTE#1035831.  Closes: #1041207
 NB1: such a change was very very inappropriate for a NMU.
 NB2: looking for packages needing a rebuild due to this will be "fun".
Checksums-Sha1:
 78c9a3b0b7e1807e1332d03cefe1bba440a67cc6 1988 debootstrap_1.0.128+nmu4.dsc
 3512c3d632d410c1987da33eec11fa7a2f5722c0 85199 debootstrap_1.0.128+nmu4.tar.gz
 28183cf8d6b5a822364b5cf4685d5dc28dcbdf57 5794 
debootstrap_1.0.128+nmu4_source.buildinfo
Checksums-Sha256:
 b6c3983dda30f237b6f1d259e2f55ae633e3036ca95b82c360b078e806b4826a 1988 
debootstrap_1.0.128+nmu4.dsc

Bug#1041229: dependency problems prevent configuration of libltdl-dev

[Vincent Lefevre]

Package: libltdl-dev
Version: 2.4.7-6
Severity: grave
Justification: renders package unusable

When upgrading, I got:

E: Sub-process /usr/bin/dpkg returned an error code (1)
dpkg: dependency problems prevent configuration of libltdl-dev:amd64:
 libltdl-dev:i386 (2.4.7-6) breaks libltdl3-dev and is unpacked but not 
configured.
  libltdl-dev:amd64 (2.4.7-6) provides libltdl3-dev.

dpkg: error processing package libltdl-dev:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libltdl-dev:i386:
 libltdl-dev:amd64 (2.4.7-6) breaks libltdl3-dev and is unpacked but not 
configured.
  libltdl-dev:i386 (2.4.7-6) provides libltdl3-dev.

dpkg: error processing package libltdl-dev:i386 (--configure):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 libltdl-dev:amd64
 libltdl-dev:i386

In the /var/log/dpkg.log file, about libltdl*:

2023-07-16 00:13:59 upgrade libltdl-dev:i386 2.4.7-5 2.4.7-6
2023-07-16 00:13:59 status half-configured libltdl-dev:i386 2.4.7-5
2023-07-16 00:13:59 status unpacked libltdl-dev:i386 2.4.7-5
2023-07-16 00:13:59 status half-configured libltdl-dev:amd64 2.4.7-5
2023-07-16 00:13:59 status half-installed libltdl-dev:i386 2.4.7-5
2023-07-16 00:13:59 status unpacked libltdl-dev:i386 2.4.7-6
2023-07-16 00:13:59 upgrade libltdl-dev:amd64 2.4.7-5 2.4.7-6
2023-07-16 00:13:59 status unpacked libltdl-dev:amd64 2.4.7-5
2023-07-16 00:13:59 status half-installed libltdl-dev:amd64 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl-dev:amd64 2.4.7-6
2023-07-16 00:14:00 upgrade libltdl7:amd64 2.4.7-5 2.4.7-6
2023-07-16 00:14:00 status half-configured libltdl7:amd64 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl7:amd64 2.4.7-5
2023-07-16 00:14:00 status half-configured libltdl7:i386 2.4.7-5
2023-07-16 00:14:00 status half-installed libltdl7:amd64 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl7:amd64 2.4.7-6
2023-07-16 00:14:00 upgrade libltdl7:i386 2.4.7-5 2.4.7-6
2023-07-16 00:14:00 status unpacked libltdl7:i386 2.4.7-5
2023-07-16 00:14:00 status half-installed libltdl7:i386 2.4.7-5
2023-07-16 00:14:00 status unpacked libltdl7:i386 2.4.7-6
[...]
2023-07-16 00:14:23 configure libltdl7:amd64 2.4.7-6 
2023-07-16 00:14:23 status unpacked libltdl7:amd64 2.4.7-6
2023-07-16 00:14:23 status half-configured libltdl7:amd64 2.4.7-6
2023-07-16 00:14:23 status installed libltdl7:amd64 2.4.7-6
2023-07-16 00:14:23 configure libltdl7:i386 2.4.7-6 
2023-07-16 00:14:23 status unpacked libltdl7:i386 2.4.7-6
2023-07-16 00:14:23 status half-configured libltdl7:i386 2.4.7-6
2023-07-16 00:14:23 status installed libltdl7:i386 2.4.7-6

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

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

Versions of packages libltdl-dev:amd64 depends on:
ii  automake [automake-1.16]  1:1.16.5-1.3
ii  libltdl7  2.4.7-6

Versions of packages libltdl-dev:amd64 recommends:
ii  libtool  2.4.7-6

Versions of packages libltdl-dev:amd64 suggests:
ii  libtool-doc  2.4.7-6

-- no debconf information

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

Processed: transition: suitesparse

[Debian Bug Tracking System]

Processing control commands:

> affects -1 + src:suitesparse
Bug #1041227 [release.debian.org] transition: suitesparse
Added indication that 1041227 affects src:suitesparse
> forwarded -1 https://release.debian.org/transitions/html/auto-suitesparse.html
Bug #1041227 [release.debian.org] transition: suitesparse
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-suitesparse.html'.
> block -1 by 1041059 1037905 1037622 1040694 1041225 1037858
Bug #1041227 [release.debian.org] transition: suitesparse
1041227 was not blocked by any bugs.
1041227 was not blocking any bugs.
Added blocking bug(s) of 1041227: 1041059, 1041225, 1037622, 1040694, 1037905, 
and 1037858

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

Bug#1037896: marked as done (widelands: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 21:10:05 +
with message-id 
and subject line Bug#1037896: fixed in widelands 2:1.1-4
has caused the Debian Bug report #1037896,
regarding widelands: ftbfs with GCC-13
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.)


-- 
1037896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037896
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:widelands
Version: 2:1.1-3
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/widelands_1.1-3_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
[  0%] Building C object 
src/third_party/CMakeFiles/third_party_eris.dir/eris/ldo.c.o
cd /<>/obj-x86_64-linux-gnu/src/third_party && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/third_party_sha1.dir/link.txt --verbose=1
cd /<>/obj-x86_64-linux-gnu/src/third_party && /usr/bin/cc 
-DASIO_STANDALONE -DUSE_XDG -DWL_USE_GLVND  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -g -O2 -DNDEBUG -DNOPARACHUTE -w -MD -MT 
src/third_party/CMakeFiles/third_party_eris.dir/eris/ldo.c.o -MF 
CMakeFiles/third_party_eris.dir/eris/ldo.c.o.d -o 
CMakeFiles/third_party_eris.dir/eris/ldo.c.o -c 
/<>/src/third_party/eris/ldo.c
/usr/bin/ar qc libthird_party_sha1.a 
CMakeFiles/third_party_sha1.dir/sha1/sha1.cc.o
/usr/bin/ranlib libthird_party_sha1.a
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
[  0%] Built target third_party_sha1
[  0%] Building C object 
src/third_party/CMakeFiles/third_party_eris.dir/eris/ldump.c.o
cd /<>/obj-x86_64-linux-gnu/src/third_party && /usr/bin/cc 
-DASIO_STANDALONE -DUSE_XDG -DWL_USE_GLVND  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -g -O2 -DNDEBUG -DNOPARACHUTE -w -MD -MT 
src/third_party/CMakeFiles/third_party_eris.dir/eris/ldump.c.o -MF 
CMakeFiles/third_party_eris.dir/eris/ldump.c.o.d -o 
CMakeFiles/third_party_eris.dir/eris/ldump.c.o -c 
/<>/src/third_party/eris/ldump.c
[  0%] Building C object 
src/third_party/CMakeFiles/third_party_eris.dir/eris/lfunc.c.o
cd /<>/obj-x86_64-linux-gnu/src/third_party && /usr/bin/cc 
-DASIO_STANDALONE -DUSE_XDG -DWL_USE_GLVND  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -g -O2 -DNDEBUG -DNOPARACHUTE -w -MD -MT 
src/third_party/CMakeFiles/third_party_eris.dir/eris/lfunc.c.o -MF 
CMakeFiles/third_party_eris.dir/eris/lfunc.c.o.d -o 
CMakeFiles/third_party_eris.dir/eris/lfunc.c.o -c 
/<>/src/third_party/eris/lfunc.c
[  0%] Building C object 
src/third_party/CMakeFiles/third_party_eris.dir/eris/lgc.c.o
cd /<>/obj-x86_64-linux-gnu/src/third_party && /usr/bin/cc 
-DASIO_STANDALONE -DUSE_XDG -DWL_USE_GLVND  -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wdate-time 
-D_FORTIFY_SOURCE=2 -O3 -DNDEBUG  -g -O2 -DNDEBUG -DNOPARACHUTE -w -MD -MT 
src/third_party/CMakeFiles/third_party_eris.dir/eris/lgc.c.o -MF 
CMakeFiles/third_party_eris.dir/eris/lgc.c.o.d -o 
CMakeFiles/third_party_eris.dir/eris/lgc.c.o -c 
/<>/src/third_party/eris/lgc.c
[  0%] Building C object 
src/third_party/CMakeFiles/third_party_eris.dir/eris/linit.c.o
cd /<>/obj-x86_64-linux-gnu/src/third_party && /usr/bin/c

Bug#1037754: marked as done (limesuite: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 21:02:12 +
with message-id 
and subject line Bug#1037754: fixed in limesuite 22.09.1+dfsg-2
has caused the Debian Bug report #1037754,
regarding limesuite: ftbfs with GCC-13
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.)


-- 
1037754: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037754
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:limesuite
Version: 22.09.1+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/limesuite_22.09.1+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/LimeSuite.dir/build.make 
src/CMakeFiles/LimeSuite.dir/depend
make  -f src/oglGraph/CMakeFiles/oglGraph.dir/build.make 
src/oglGraph/CMakeFiles/oglGraph.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src/oglGraph 
/<>/obj-x86_64-linux-gnu 
/<>/obj-x86_64-linux-gnu/src/oglGraph 
/<>/obj-x86_64-linux-gnu/src/oglGraph/CMakeFiles/oglGraph.dir/DependInfo.cmake
 --color=
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src 
/<>/obj-x86_64-linux-gnu/src/CMakeFiles/LimeSuite.dir/DependInfo.cmake
 --color=
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f src/oglGraph/CMakeFiles/oglGraph.dir/build.make 
src/oglGraph/CMakeFiles/oglGraph.dir/build
make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/LimeSuite.dir/build.make 
src/CMakeFiles/LimeSuite.dir/build
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
[  2%] Building CXX object 
src/oglGraph/CMakeFiles/oglGraph.dir/OpenGLGraph.cpp.o
[  2%] Building CXX object src/oglGraph/CMakeFiles/oglGraph.dir/dlgMarkers.cpp.o
[  2%] Building CXX object src/oglGraph/CMakeFiles/oglGraph.dir/GLFont.cpp.o
[  2%] Building CXX object src/CMakeFiles/LimeSuite.dir/Logger.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/oglGraph && /usr/bin/c++ 
-DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-I/<>/src/lms7002_wxgui -I/<>/src/LMS_Programing 
-I/<>/src/utilities_gui -I/<>/src/RFSpark 
-I/<>/src/FPGAcontrols_wxgui -I/<>/src/numericSlider 
-I/<>/src/fftviewer_wxgui -I/<>/src/lms7suiteEvents 
-I/<>/src/boards_wxgui -I/<>/src/limeRFE 
-I/<>/src/oglGraph -isystem 
/usr/lib/x86_64-linux-gnu/wx/include/gtk3-unicode-3.2 -isystem 
/usr/include/wx-3.2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -fvisibility-inlines-hidden -pthread -O3 -DNDEBUG   
-Wno-narrowing -fvisibility=hidden -fno-caller-saves -std=gnu++11 -MD -MT 
src/oglGraph/CMakeFiles/oglGraph.dir/dlgMarkers.cpp.o -MF 
CMakeFiles/oglGraph.dir/dlgMarkers.cpp.o.d -o CMakeFiles/oglGraph.dir/d
 lgMarkers.cpp.o -c /<>/src/oglGraph/dlgMarkers.cpp
[  3%] Building CXX object src/CMakeFiles/LimeSuite.dir/ADF4002/ADF4002.cpp.o
cd /<>/obj-x86_64-linux-gnu/src/oglGraph && /usr/bin/c++ 
-DWXUSINGDLL -D_FILE_OFFSET_BITS=64 -D__WXGTK__ 
-I/<>/src/lms7002_wxgui -I/<>/src/LMS_Programing 
-I/<>/src/utilities_gui -I/<>/src/RFSpark 
-I/<>/src/FPGAcontrols_wxgui -I/<>/src/numericSlider 
-I/<>/src/fftviewer_wxgui -I/<>/src/lms7suiteEvents 
-I/<>/src/boards_wxgui -I

Bug#1037598: marked as done (capnproto: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 20:58:32 +
with message-id 
and subject line Bug#1037598: fixed in capnproto 0.9.2-3
has caused the Debian Bug report #1037598,
regarding capnproto: ftbfs with GCC-13
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.)


-- 
1037598: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037598
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:capnproto
Version: 0.9.2-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/capnproto_0.9.2-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
  |^~~
./src/kj/compat/../test.h:74:52: note: in definition of macro ‘KJ_EXPECT’
   74 |   if (auto _kjCondition = ::kj::_::MAGIC_ASSERT << cond); \
  |^~~~
src/kj/string-test.c++:151:3: note: in expansion of macro ‘EXPECT_EQ’
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  |   ^
src/kj/string-test.c++:151:36: note: ‘uint8_t’ is defined in header 
‘’; did you forget to ‘#include ’?
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  |^~~
./src/kj/compat/../test.h:74:52: note: in definition of macro ‘KJ_EXPECT’
   74 |   if (auto _kjCondition = ::kj::_::MAGIC_ASSERT << cond); \
  |^~~~
src/kj/string-test.c++:151:3: note: in expansion of macro ‘EXPECT_EQ’
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  |   ^
src/kj/string-test.c++:151:44: error: no matching function for call to 
‘kj::StringPtr::parseAs< >()’
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  | ~~~^~
./src/kj/compat/../test.h:74:52: note: in definition of macro ‘KJ_EXPECT’
   74 |   if (auto _kjCondition = ::kj::_::MAGIC_ASSERT << cond); \
  |^~~~
src/kj/string-test.c++:151:3: note: in expansion of macro ‘EXPECT_EQ’
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  |   ^
src/kj/string.h:146:5: note: candidate: ‘template T 
kj::StringPtr::parseAs() const’
  146 |   T parseAs() const;
  | ^~~
src/kj/string.h:146:5: note:   template argument deduction/substitution failed:
src/kj/string-test.c++:151:44: error: template argument 1 is invalid
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  | ~~~^~
./src/kj/compat/../test.h:74:52: note: in definition of macro ‘KJ_EXPECT’
   74 |   if (auto _kjCondition = ::kj::_::MAGIC_ASSERT << cond); \
  |^~~~
src/kj/string-test.c++:151:3: note: in expansion of macro ‘EXPECT_EQ’
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  |   ^
src/kj/string-test.c++:151:44: error: no matching function for call to 
‘kj::StringPtr::parseAs()’
  151 |   EXPECT_EQ(StringPtr("1").parseAs(), 1);
  | ~~~^~
./src/kj/compat/../debug.h:215:41: note: in definition of macro ‘KJ_LOG’
  215 | #__VA_ARGS__, ##__VA_ARGS__)
  | ^~~
./src/kj/compat/../test.h:75:8: note: in expansion of macro ‘KJ_FAIL_EXPECT’
   75 |   else KJ_FAIL_EXPECT("failed: expected " #cond, _kjCondition, 
##__VA_ARGS__)
  |^~
./src/kj/compat/gtest.h:54:25: note: in expansion of macro ‘KJ_EXPECT’
   54 | #define EXPE

Bug#1021894: openjfx: FTBFS on arm64 and armhf

[tony mancill]

Hi Wookey,

Thank you for the investigation and the patch!

I intend to build and upload in the next few days, but you are welcome
to NMU if you would prefer.

Cheers,
tony

On Fri, Jul 14, 2023 at 02:28:14PM +0100, Wookey wrote:
> Source: openjfx
> Followup-For: Bug #1021894
> 
> I was surprised to find that this package was missing on arm64 (making josm 
> uninstallable) so I investigated. 
> 
> 11.0.11+0-1 built OK on 2021-02-03. But 11.0.11+1-3 FTBFS.
> 
> 11.0.11+0-1 no longer builds either. Failing in:
> Execution failed for task ':media:buildAVPlugin'
> ../../../plugins/av/decoder.c:79:5: error: implicit declaration of function 
> 'avcodec_register_all'
> which seems to be a problem with ffmpeg, but lets ignore that for now - it 
> seems to be fixed with a patch in +1-3
> 
> 11.0.11+1-3 fails with:
> [ 28%] Building CXX object 
> Source/JavaScriptCore/CMakeFiles/LLIntOffsetsExtractor.dir/llint/LLIntOffsetsExtractor.cpp.o
>   Gradle is still running, please be patient...
> In file included from 
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/MacroAssemblerARM64.h:30,
>  from 
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/MacroAssembler.h:46,
>  from 
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/jit/GPRInfo.h:28,
>  from 
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/bytecode/ArithProfile.h:28,
>  from 
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/llint/LLIntOffsetsExtractor.cpp:28:
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/ARM64Assembler.h:
>  In static member function ‘static void 
> JSC::ARM64Assembler::replaceWithJump(void*, void*)’:
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/ARM64Assembler.h:2576:51:
>  error: ‘class JSC::ExecutableAllocator’ has no member named ‘getJumpIslandTo’
>  2576 | to = 
> ExecutableAllocator::singleton().getJumpIslandTo(where, to);
>   |   ^~~
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/ARM64Assembler.h:
>  In static member function ‘static void* 
> JSC::ARM64Assembler::prepareForAtomicRelinkJumpConcurrently(void*, void*)’:
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/ARM64Assembler.h:2781:49:
>  error: ‘class JSC::ExecutableAllocator’ has no member named 
> ‘getJumpIslandToConcurrently’
>  2781 | return 
> ExecutableAllocator::singleton().getJumpIslandToConcurrently(from, to);
>   | 
> ^~~
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/ARM64Assembler.h:
>  In static member function ‘static void 
> JSC::ARM64Assembler::linkJumpOrCall(int*, const int*, void*)’:
> /<>/modules/javafx.web/src/main/native/Source/JavaScriptCore/assembler/ARM64Assembler.h:3024:51:
>  error: ‘class JSC::ExecutableAllocator’ has no member named ‘getJumpIslandTo’
>  3024 | to = 
> ExecutableAllocator::singleton().getJumpIslandTo(bitwise_cast(fromInstruction),
>  to);
>   |   ^~~
> 
> (Which is actually a different failure point from the one Sebastian posted in 
> this bug)
> 
> So all this jumpisland stuff comes from webkit's JavaScript JIT.
> 
> It turns out that this upstream Webkit bug explains what's going on:
> https://bugs.webkit.org/show_bug.cgi?id=217079
> jumpislands allow +-128MB jumps to get to the whole 1GB executable space by 
> having a particular memory layout.
> And the build should use _either_ the JIT or 'CLOOP', but not both.
> 
> Applying the patch in that bug (which gates JUMP_ISLANDS on the JIT
> being enabled, and avoids compiling in a call to dumpJITMemory if JIT
> is disabled) allows everything to get compiled. However it then fails
> to link:
>  
> [100%] Linking CXX shared library ../../lib/libjfxwebkit.so
> /usr/include/c++/11/ext/new_allocator.h:116: error: undefined reference to 
> 'std::__throw_bad_array_new_length()'
> collect2: error: ld returned 1 exit status
> gmake[4]: *** 
> [Source/WebKitLegacy/CMakeFiles/WebKitLegacy.dir/build.make:2237: 
> lib/libjfxwebkit.so] Error 1
> 
> Which seems to be a problem with compiling with gcc11/12, but then trying
> to link to the gcc-libstd++ from gcc10.  Removing all the gcc-10
> packages from the build environment fixed this. I think this means
> the package should get a build-conflict on libstdc++-10-dev
> 
> Also the discussion in the above bug suggests that the JIT should in fact be 
> enabled on debian arm64.
> It only needs to be turned off on iOS and 64k aarch64 kernel (RHEL). I will 
> test that next.
> 
> Attached is the debdiff that at least makes the build work again for now. 
> Happy to do an NMU if that's helpful

> diff -Nru openjfx-11.0.11+1/debian/changelog 
> openj

Bug#1040694: Proposing a way to solve #1040694

[Pierre Gruet]

Hello Julien,

I am writing to you in addition to the sole bug report as you are the 
uploader of coinor-cbc.


Because we saw an ABI breakage between versions 2.10.8 and 2.10.10 which 
affects rdeps, I propose to:
- Revert the version in unstable to 2.10.8, with upstream version number 
being 2.10.10+really2.10.8+ds1;
- Upload 2.10.10+really2.10.10+ds1 (containing upstream 2.10.10) to 
experimental with a SOVERSION raised to 3.1 and renaming the shared lib 
package to coinor-libcbc3.1, hereby using a SOVERSION higher than the 
upstream one but still being lower than the "4" they could adopt in the 
future;

- Lead a classic library transition so that rdeps are rebuilt.

I volunteer to do this if you want, as this is a blocker for my workflows.

Please kindly raise concerns if you need to :)

Cheers,

--
Pierre


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1037754: marked as pending in limesuite

[Tony Mancill]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/debian-hamradio-team/limesuite/-/commit/5856ba8001d2e9c3278d7ac20709935822631bac


Fix FTBFS with GCC-13 (Closes: #1037754)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1037754

Processed: Bug#1037754 marked as pending in limesuite

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1037754 [src:limesuite] limesuite: ftbfs with GCC-13
Added tag(s) pending.

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

Bug#1041161: dkms autopkg test fails on arm64

[Andreas Beckmann]

On 15/07/2023 12.00, Matthias Klose wrote:

179s The following packages have unmet dependencies:
179s  libhwasan0 : Depends: gcc-13-base (= 13.1.0-8) but 13.1.0-6 is to 
be installed

179s E: Unable to correct problems, you have held broken packages.
179s E: Linux headers failed to install.

there seems to be something wrong with the setup of the test. why isn't 
the same version taken for the two packages?


My guess is that is on the autopkgtest side ...

This is a test in testing with --pin-packages=unstable=src:gcc-11
dkms-autopkgtest does
  apt-get install linux-headers-6.3.0-1-arm64 \
linux-headers-6.3.0-1-cloud-arm64 \
linux-headers-6.3.0-1-rt-arm64
(these are from testing) - why does that want to install libhwasan0 from 
sid?


Andreas

Processed: Xournal++ GCC 13 FTBFS fixed upstream

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 
> https://github.com/xournalpp/xournalpp/commit/9172ee831f4dfbb88dfeb13b66862e80e64a0d3f
Bug #1037904 [src:xournalpp] xournalpp: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/xournalpp/xournalpp/commit/9172ee831f4dfbb88dfeb13b66862e80e64a0d3f'.
> tags -1 fixed-upstream
Bug #1037904 [src:xournalpp] xournalpp: ftbfs with GCC-13
Added tag(s) fixed-upstream.

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

Bug#1037904: Xournal++ GCC 13 FTBFS fixed upstream

[John Scott]

Control: forwarded -1 
https://github.com/xournalpp/xournalpp/commit/9172ee831f4dfbb88dfeb13b66862e80e64a0d3f
Control: tags -1 fixed-upstream

It looks like this has been fixed upstream, so I'm setting the bug metadata as 
such.


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


smime.p7s
Description: S/MIME cryptographic signature

Processed: notfixed 1037598 in 15.02.00-1

[Debian Bug Tracking System]

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

> notfixed 1037598 15.02.00-1
Bug #1037598 [src:capnproto] capnproto: ftbfs with GCC-13
The source 'capnproto' and version '15.02.00-1' do not appear to match any 
binary packages
Ignoring request to alter fixed versions of bug #1037598 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1037857: closing 1037857

[tony mancill]

close 1037857 15.02.00-1
thanks

Upstream 15.02.00 addressed the FTBFS with GCC-13.

Processed: closing 1037857

[Debian Bug Tracking System]

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

> close 1037857 15.02.00-1
Bug #1037857 [src:simrisc] simrisc: ftbfs with GCC-13
Marked as fixed in versions simrisc/15.02.00-1.
Bug #1037857 [src:simrisc] simrisc: ftbfs with GCC-13
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: reopening 1037598

[Debian Bug Tracking System]

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

> reopen 1037598
Bug #1037598 {Done: tony mancill } [src:capnproto] 
capnproto: ftbfs with GCC-13
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions capnproto/15.02.00-1.
> thanks
Stopping processing here.

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

Bug#981869: marked as done (librust-tcmalloc-dev: Depends: librust-tcmalloc-sys-0.3+default-dev but it is not installable)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 19:09:04 +
with message-id 
and subject line Bug#981869: fixed in rust-tcmalloc-sys 0.3.0-1
has caused the Debian Bug report #981869,
regarding librust-tcmalloc-dev: Depends: librust-tcmalloc-sys-0.3+default-dev 
but it is not installable
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.)


-- 
981869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=981869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-tcmalloc-dev
Version: 0.3.0-2
Severity: serious

The following packages have unmet dependencies:
 librust-tcmalloc-dev : Depends: librust-tcmalloc-sys-0.3+default-dev but it is 
not installable
--- End Message ---
--- Begin Message ---
Source: rust-tcmalloc-sys
Source-Version: 0.3.0-1
Done: Alexander Kjäll 

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

Debian distribution maintenance software
pp.
Alexander Kjäll  (supplier of updated 
rust-tcmalloc-sys 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, 15 Jul 2023 13:44:35 CEST
Source: rust-tcmalloc-sys
Binary: librust-tcmalloc-sys-dev
Architecture: amd64 source
Version: 0.3.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Alexander Kjäll 
Description: 
 librust-tcmalloc-sys-dev - Drop-in global allocator using tcmalloc - Rust 
source code
Closes: 981869
Changes:
 rust-tcmalloc-sys (0.3.0-1) unstable; urgency=medium
 .
   * Package tcmalloc-sys 0.3.0 from crates.io using debcargo 2.6.0 (Closes: 
981869)
Checksums-Sha256: 
 c817233d173f11a563248f499457228f0c1b250ce0f310ddbb45f657cdb37591 4524 
librust-tcmalloc-sys-dev_0.3.0-1_amd64.deb
 941a2c9696562b2a7cc5e9404d1bcd92c8f7aff51def5366bbb7d1b124cd3997 7249 
rust-tcmalloc-sys_0.3.0-1_amd64.buildinfo
 b580dc684de97f305781a7b46aa49fee8ca2ce3be531258503594b2a9536f745 2201 
rust-tcmalloc-sys_0.3.0-1.dsc
 3b7ad73e635dd232c2c2106d59269f59a61de421cc6b95252d2d932094ff1f40 1981 
rust-tcmalloc-sys_0.3.0.orig.tar.gz
 c8d8fa1b896fb0a90377088ed932b5a2f81421c02c00706a2f62e24ab6620d12 2940 
rust-tcmalloc-sys_0.3.0-1.debian.tar.xz
Checksums-Sha1: 
 fdd757f198d498922e13770ace56a9c2074e7eab 4524 
librust-tcmalloc-sys-dev_0.3.0-1_amd64.deb
 65e76ea1fa3ad2cbbfb8d863ef5a131fa077a5d9 7249 
rust-tcmalloc-sys_0.3.0-1_amd64.buildinfo
 d60b487d70e7a8368c316e22c8e905d3a25a0551 2201 rust-tcmalloc-sys_0.3.0-1.dsc
 f58bec6b286094d3563744aa8be2273e95901e37 1981 
rust-tcmalloc-sys_0.3.0.orig.tar.gz
 98b86fa6280201967c65a46621eed19ddf77a601 2940 
rust-tcmalloc-sys_0.3.0-1.debian.tar.xz
Files: 
 d9434e475e980726675c68f610385316 4524 rust optional 
librust-tcmalloc-sys-dev_0.3.0-1_amd64.deb
 b63edb041bbf5ba7aabac051545d6d8d 7249 rust optional 
rust-tcmalloc-sys_0.3.0-1_amd64.buildinfo
 6289083dd11fca98dccd6dd448d2abfe 2201 rust optional 
rust-tcmalloc-sys_0.3.0-1.dsc
 78506d4d74fb1bc90e1df90e009a221c 1981 - - rust-tcmalloc-sys_0.3.0.orig.tar.gz
 cab133995fb62ef39a0f780aad32d36c 2940 - - 
rust-tcmalloc-sys_0.3.0-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEtg21mU05vsTRqVzPfmUo2nUvG+EFAmSyhqMACgkQfmUo2nUv
G+FtfQ/+LpvCJ1m80f5MrI8kbGuLIiUvZy25gUw5jjoO2lNlehvOixeqObmQldNe
7HxkvSjYFlQ15lezrJg2o76JEabvBoiT+kvF95xNWHeSe4vseMoTmIKnRo1vddax
R3kl11ElJLHXztlis+DmdRP2o/0PMM0xVxKolTvJTi46G3KgBI+F0dg+VOcRwBZO
gW4Es+6I84w3slAi6ZqyZkxkkLxINchZ3uc+wsofMTiVTBFkkCCoLYbuKnVmPRby
bkS19ico+oclBq6xX0rqlTTtV/Vuar6S9bxND6SvENMg+hnUh5hl4uVhS3W9VHBX
ipux6ynaR1VLHUnBIljX7x5KMhanWycGsKaAST99KtHeR9W+9y3VmIMNwTXtnKNo
StN+s8qYXMSa1z5zTJfBQwa6huM5yrVSpfa4RZ9+xCBm6pKYQ/zNPaJhcANKPpQ/
qcyn99mZzB0UUaTtQJ3tZxlcLk9pgaplg8Q8pO/sqiNJOoogIFCDyirJahZRODhL
nsCI8T9//qIp8dyvZtbjrgL0cw5/iMuS0uWVdaquhxU7APSy1cgjwL6s4FCH0R5a
umkva5tFsD28q0QMF8uT6E27fngrUKWpPXiGPX7rIWnNEcOODctZe8TC9tnz/hnZ
GstoVTAnJUABepp0jdDP+4U1xEeNFcavwOVuIzYX6Eni/samqB0=
=hcks
-END PGP SIGNATURE End Message ---

Bug#1037598: closing 1037598

[tony mancill]

close 1037598 15.02.00-1
thanks

Upstream release 15.02.00 addressed the FTBFS with GCC-13.

Processed: closing 1037598

[Debian Bug Tracking System]

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

> close 1037598 15.02.00-1
Bug #1037598 [src:capnproto] capnproto: ftbfs with GCC-13
The source 'capnproto' and version '15.02.00-1' do not appear to match any 
binary packages
Marked as fixed in versions capnproto/15.02.00-1.
Bug #1037598 [src:capnproto] capnproto: ftbfs with GCC-13
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1040855: marked as done (setuptools-scm autopkg test fail with setuptools 68)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 19:03:21 +
with message-id 
and subject line Bug#1040855: fixed in setuptools-scm 7.1.0-4
has caused the Debian Bug report #1040855,
regarding setuptools-scm autopkg test fail with setuptools 68
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.)


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

Package: src:setuptools-scm
Version: 7.1.0-3
Severity: serious
Tags: sid trixie

see
https://ci.debian.net/data/autopkgtest/testing/amd64/s/setuptools-scm/35654873/log.gz

[...]
 86s === FAILURES 
===
 86s __ test_pyproject_support_with_git[pyproject.project] 
__

 86s
 86s wd = 
 86s metadata_in = 'pyproject.project'
 86s
 86s @with_metadata_in
 86s def test_pyproject_support_with_git(wd: WorkDir, metadata_in: str) -> 
None:

 86s if sys.version_info <= (3, 10):
 86s pytest.importorskip("tomli")
 86s wd.write("pyproject.toml", PYPROJECT_FILES[metadata_in])
 86s wd.write("setup.py", SETUP_PY_FILES[metadata_in])
 86s wd.write("setup.cfg", SETUP_CFG_FILES[metadata_in])
 86s res = wd([sys.executable, "setup.py", "--version"])
 86s >   assert res.endswith("0.1.dev0")
 86s E   AssertionError: assert False
 86s E+  where False = 0xa5de20>('0.1.dev0')
 86s E+where  = 
''.endswith

 86s
 86s testing/test_integration.py:94: AssertionError
--- End Message ---
--- Begin Message ---
Source: setuptools-scm
Source-Version: 7.1.0-4
Done: Scott Talbert 

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

Debian distribution maintenance software
pp.
Scott Talbert  (supplier of updated setuptools-scm package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 15 Jul 2023 14:22:32 -0400
Source: setuptools-scm
Architecture: source
Version: 7.1.0-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Scott Talbert 
Closes: 1040855
Changes:
 setuptools-scm (7.1.0-4) unstable; urgency=medium
 .
   * Team upload.
   * Fix autopkgtests with setuptools 68 (Closes: #1040855)
Checksums-Sha1:
 c3823c0c7c09d5be94401d24039d004e480be656 2323 setuptools-scm_7.1.0-4.dsc
 74dfbe09741ee3b61cfee3190b04ab51afdb3820 6304 
setuptools-scm_7.1.0-4.debian.tar.xz
 0e9e4a599e6a0818b5da3e16826ccf07d2ab1ecb 8224 
setuptools-scm_7.1.0-4_amd64.buildinfo
Checksums-Sha256:
 8e95a2a0548bd908d2a053c61b5ae81a930107cab47560cc260e5ac62bd18d19 2323 
setuptools-scm_7.1.0-4.dsc
 51b710d07d63c358a4d160ad251c236828c64e8e748982e1a046acafbf4bd349 6304 
setuptools-scm_7.1.0-4.debian.tar.xz
 93fbd8a6ff12661a138272d9bf91959f06641ee869e0e0147f10581bc0ae1758 8224 
setuptools-scm_7.1.0-4_amd64.buildinfo
Files:
 1bd2da954e9c597f814437c41479407b 2323 python optional 
setuptools-scm_7.1.0-4.dsc
 056620f63a90128c15c8782e565b1549 6304 python optional 
setuptools-scm_7.1.0-4.debian.tar.xz
 ec108209e12b00dbf21709106336c2c1 8224 python optional 
setuptools-scm_7.1.0-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJDBAEBCgAtFiEEbnQ09Yl9Q7F/zVe3U9W8ZLUjeKIFAmSy5xMPHHN3dEB0ZWNo
aWUubmV0AAoJEFPVvGS1I3iiiP4P/39Xh+mxQz1HLG0xYAtmuXjIZSCw8pzJZXlt
lIwBsGWZR/r5Tdkuux5DRVsBJRcxGQUxWQHbTziAvJn+CvOfL0AWi69gQR2Gy94G
MwGl3oKa3+KaXVPaZxcoYRBJXK/GoK+L5qeKRY1odafMioU6Ki83YWH4spApHhLH
qQzXWnp8MT2uhFbKUzNmYtqkSgK1k78CWI6A6gRuK1bfQxFBcUsv+fNUYKN5Ihc6
R/RKK7NzOCj5vgRdrzfLgGkZ3KcXr2EIdzpG9CPf4kbPBylDlla5bueZbuaWUDYx
cGkkWf3jjX1RVSXSjeb4A/DSFDwLm1scr0W/RrCdAhfO7uKxxqwItl7iVLvd8Qa8
UUKIeD7cvMa7mMFdZnRHqEsHJkHhrEPaQdXP8Yfpm4Hz92lYbQkdcgsxQXRN3/zw
vy6pdWriNLrBLBHLwzWAQm4I+/PnECEwLf2xx6zWULiT51Q116In75NvP1o7YzmU
lqCMlaqxnqNI60kf15mRtpbWOr/w7Lx3YOY2UvL43jriXUVO838q7z+rwB9h6QJH
uXSB+9pgIgnN2fB6C3A8PT0Xb60KLGHhPmME6qKJE09afCF6ahFiBwwij0EzVoxi
u3oijtUEEPwvogv/zr3hFeFslxo6/zFKryEogKZVqL6YGFu1kFCpLs7PzaMqtZNY
hyvOUEL6
=iPqq
-END PGP SIGNATURE End Message ---

Bug#1041223: src:icingaweb2-module-graphite: fails to migrate to testing for too long: unresolved issues

[Paul Gevers]

Source: icingaweb2-module-graphite
Version: 1.2.2-1
Severity: serious
Control: close -1 1.2.2-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038929

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:icingaweb2-module-graphite has been trying 
to migrate for 31 days [2]. Hence, I am filing this bug. The version of 
this package in unstable has installability issues as reported in bug 
1038929.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:icingaweb2-module-graphite: fails to migrate to testing for too long: unresolved issues

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.2.2-2
Bug #1041223 [src:icingaweb2-module-graphite] src:icingaweb2-module-graphite: 
fails to migrate to testing for too long: unresolved issues
Marked as fixed in versions icingaweb2-module-graphite/1.2.2-2.
Bug #1041223 [src:icingaweb2-module-graphite] src:icingaweb2-module-graphite: 
fails to migrate to testing for too long: unresolved issues
Marked Bug as done
> block -1 by 1038929
Bug #1041223 {Done: Paul Gevers } 
[src:icingaweb2-module-graphite] src:icingaweb2-module-graphite: fails to 
migrate to testing for too long: unresolved issues
1041223 was not blocked by any bugs.
1041223 was not blocking any bugs.
Added blocking bug(s) of 1041223: 1038929

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

Processed: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.27-1
Bug #1041220 [src:libgitlab-api-v4-perl] src:libgitlab-api-v4-perl: fails to 
migrate to testing for too long: triggers autopkgtest regression in devscripts
Marked as fixed in versions libgitlab-api-v4-perl/0.27-1.
Bug #1041220 [src:libgitlab-api-v4-perl] src:libgitlab-api-v4-perl: fails to 
migrate to testing for too long: triggers autopkgtest regression in devscripts
Marked Bug as done
> block -1 by 1038486
Bug #1041220 {Done: Paul Gevers } 
[src:libgitlab-api-v4-perl] src:libgitlab-api-v4-perl: fails to migrate to 
testing for too long: triggers autopkgtest regression in devscripts
1041220 was not blocked by any bugs.
1041220 was not blocking any bugs.
Added blocking bug(s) of 1041220: 1038486

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

Bug#1041220: src:libgitlab-api-v4-perl: fails to migrate to testing for too long: triggers autopkgtest regression in devscripts

[Paul Gevers]

Source: libgitlab-api-v4-perl
Version: 0.26-3
Severity: serious
Control: close -1 0.27-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1038486

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:libgitlab-api-v4-perl has been trying to 
migrate for 32 days [2]. Hence, I am filing this bug. The package in 
unstable triggers an autopkgtest issue in devscripts, which is reported 
in bug 1038486.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1041219: src:basilisk2: fails to migrate to testing for too long: FTBFS on arm*

[Paul Gevers]

Source: basilisk2
Version: 0.9.20220710-1
Severity: serious
Control: close -1 0.9.20230516-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:basilisk2 has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The package in unstable fails 
to build on arm64, armel and armhf, while it built there successfully in 
the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:basilisk2: fails to migrate to testing for too long: FTBFS on arm*

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.9.20230516-1
Bug #1041219 [src:basilisk2] src:basilisk2: fails to migrate to testing for too 
long: FTBFS on arm*
Marked as fixed in versions basilisk2/0.9.20230516-1.
Bug #1041219 [src:basilisk2] src:basilisk2: fails to migrate to testing for too 
long: FTBFS on arm*
Marked Bug as done

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

Bug#1041218: src:ardour: fails to migrate to testing for too long: FTBFS on mips*el

[Paul Gevers]

Source: ardour
Version: 1:7.3.0+ds0-1
Severity: serious
Control: close -1 1:7.4.0+ds-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ardour has been trying to migrate for 32 
days [2]. Hence, I am filing this bug. The package in unstable fails to 
build on mips64el and mipsel, while it built there successfully in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:ardour: fails to migrate to testing for too long: FTBFS on mips*el

[Debian Bug Tracking System]

Processing control commands:

> close -1 1:7.4.0+ds-1
Bug #1041218 [src:ardour] src:ardour: fails to migrate to testing for too long: 
FTBFS on mips*el
Marked as fixed in versions ardour/1:7.4.0+ds-1.
Bug #1041218 [src:ardour] src:ardour: fails to migrate to testing for too long: 
FTBFS on mips*el
Marked Bug as done

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

Processed: Re: pylint: Regression with tomlkit 0.11.8, Fixed in 2.17.4

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1038258 [src:pylint] pylint: Regression with tomlkit 0.11.8, Fixed in 
2.17.4
Severity set to 'serious' from 'important'

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

Processed: Bug#1040855 marked as pending in setuptools-scm

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1040855 [src:setuptools-scm] setuptools-scm autopkg test fail with 
setuptools 68
Added tag(s) pending.

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

Bug#1040855: marked as pending in setuptools-scm

[Scott Talbert]

Control: tag -1 pending

Hello,

Bug #1040855 in setuptools-scm 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/python-team/packages/setuptools-scm/-/commit/c8e8906c5da25e8c497a17116c4bad33b172fb01


Fix autopkgtests with setuptools 68 (Closes: #1040855)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1040855

Processed: src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.9.1+~cs3.1.2-2
Bug #1041217 [src:node-chart.js] src:node-chart.js: fails to migrate to testing 
for too long: autopkgtest failure
Marked as fixed in versions node-chart.js/3.9.1+~cs3.1.2-2.
Bug #1041217 [src:node-chart.js] src:node-chart.js: fails to migrate to testing 
for too long: autopkgtest failure
Marked Bug as done
> block -1 by 1039918
Bug #1041217 {Done: Paul Gevers } [src:node-chart.js] 
src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure
1041217 was not blocked by any bugs.
1041217 was not blocking any bugs.
Added blocking bug(s) of 1041217: 1039918

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

Bug#1041217: src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure

[Paul Gevers]

Source: node-chart.js
Version: 3.9.1+~0.2.1-2
Severity: serious
Control: close -1 3.9.1+~cs3.1.2-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1039918

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:node-chart.js has been trying to migrate 
for 32 days [2]. Hence, I am filing this bug. The version of this 
package in unstable has issues with its autopkgtest as reported in bug 
1039918.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed (with 1 error): src:ruby-sidekiq: fails to migrate to testing for too long: autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 6.5.7+dfsg3-2
Bug #1041216 [src:ruby-sidekiq] src:ruby-sidekiq: fails to migrate to testing 
for too long: autopkgtest failure
Marked as fixed in versions ruby-sidekiq/6.5.7+dfsg3-2.
Bug #1041216 [src:ruby-sidekiq] src:ruby-sidekiq: fails to migrate to testing 
for too long: autopkgtest failure
Marked Bug as done
> tags -1 by 1039921
Unknown tag/s: by, 1039921.
Recognized are: patch wontfix moreinfo unreproducible help security upstream 
pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed 
fixed-in-experimental sid experimental potato woody sarge sarge-ignore etch 
etch-ignore lenny lenny-ignore squeeze squeeze-ignore wheezy wheezy-ignore 
jessie jessie-ignore stretch stretch-ignore buster buster-ignore bullseye 
bullseye-ignore bookworm bookworm-ignore trixie trixie-ignore forky 
forky-ignore.


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

Bug#1041216: src:ruby-sidekiq: fails to migrate to testing for too long: autopkgtest failure

[Paul Gevers]

Source: ruby-sidekiq
Version: 6.4.1+dfsg-1
Severity: serious
Control: close -1 6.5.7+dfsg3-2
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: tags -1 by 1039921

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:ruby-sidekiq has been trying to migrate 
for 32 days [2]. Hence, I am filing this bug. The version of this 
package in unstable has issues with its autopkgtest as reported in bug 
1039921.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:squeekboard: fails to migrate to testing for too long: FTBFS on mipsel

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.22.0-3
Bug #1041215 [src:squeekboard] src:squeekboard: fails to migrate to testing for 
too long: FTBFS on mipsel
Marked as fixed in versions squeekboard/1.22.0-3.
Bug #1041215 [src:squeekboard] src:squeekboard: fails to migrate to testing for 
too long: FTBFS on mipsel
Marked Bug as done

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

Bug#1041215: src:squeekboard: fails to migrate to testing for too long: FTBFS on mipsel

[Paul Gevers]

Source: squeekboard
Version: 1.21.0-1
Severity: serious
Control: close -1 1.22.0-3
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:squeekboard has been trying to migrate for 
32 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on mipsel while if built there successfully in the past.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:mesa: fails to migrate to testing for too long: causes autopkgtest regression

[Debian Bug Tracking System]

Processing control commands:

> close -1 23.1.3-1
Bug #1041214 [src:mesa] src:mesa: fails to migrate to testing for too long: 
causes autopkgtest regression
Marked as fixed in versions mesa/23.1.3-1.
Bug #1041214 [src:mesa] src:mesa: fails to migrate to testing for too long: 
causes autopkgtest regression
Marked Bug as done
> block -1 by 1039922
Bug #1041214 {Done: Paul Gevers } [src:mesa] src:mesa: fails 
to migrate to testing for too long: causes autopkgtest regression
1041214 was not blocked by any bugs.
1041214 was not blocking any bugs.
Added blocking bug(s) of 1041214: 1039922

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

Bug#1041214: src:mesa: fails to migrate to testing for too long: causes autopkgtest regression

[Paul Gevers]

Source: mesa
Version: 22.3.6-1+deb12u1
Severity: serious
Control: close -1 23.1.3-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1039922

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:mesa has been trying to migrate for 33 
days [2]. Hence, I am filing this bug. The version in testing causes an 
autopkgtest regression as reported in bug 1039922.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1031306: marked as done (rust-criterion: autopkgtest regression)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 18:21:50 +
with message-id 
and subject line Bug#1031306: fixed in rust-criterion 0.5.1-1
has caused the Debian Bug report #1031306,
regarding rust-criterion: autopkgtest regression
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.)


-- 
1031306: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031306
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-criterion
Version: 0.4.0-2
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/r/rust-criterion/31329906/log.gz

...
error[E0004]: non-exhaustive patterns: `Some(BytesDecimal(_))` not covered
  --> src/csv_report.rs:36:55
   |
36 | let (throughput_num, throughput_type) = match id.throughput {
   |   ^ 
pattern `Some(BytesDecimal(_))` not covered
   |
note: `std::option::Option` defined here
   = note: the matched value is of type `std::option::Option`
help: ensure that all possible cases are being handled by adding a match arm 
with a wildcard pattern or an explicit pattern as shown
   |
39 ~ None => (None, None),
40 ~ Some(BytesDecimal(_)) => todo!(),
   |

For more information about this error, try `rustc --explain E0004`.
error: could not compile `criterion` due to previous error
...
autopkgtest [01:29:46]:  summary
rust-criterion-0.4:@ FAIL non-zero exit status 101
rust-criterion-0.4:cargo_bench_support PASS
rust-criterion-0.4:csv_output FAIL non-zero exit status 101
rust-criterion-0.4:default PASS
rust-criterion-0.4:html_reports PASS
rust-criterion-0.4:  PASS
rust-criterion-0.4:async_futures PASS
rust-criterion-0.4:async_smol PASS
rust-criterion-0.4:async_std PASS
rust-criterion-0.4:async_tokio PASS
rust-criterion-0.4:stable FAIL non-zero exit status 101
--- End Message ---
--- Begin Message ---
Source: rust-criterion
Source-Version: 0.5.1-1
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated rust-criterion package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 15 Jul 2023 19:12:50 +0200
Source: rust-criterion
Architecture: source
Version: 0.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1031306
Changes:
 rust-criterion (0.5.1-1) unstable; urgency=medium
 .
   [ upstream ]
   * new release(s)
 + add test case for BytesDecimal;
   closes: bug#1031306, thanks to Adrian Bunk
 .
   [ Jonas Smedegaard ]
   * update DEP-3 headers for patch 2001
   * mention patched-away feature real_blackbox as TODO
   * unfuzz patch 2001
   * (build-)depend on package for crates
 is-terminal once_cell (not atty lazy_static);
 tighten (build-)dependencies for crates clap tempfile
   * bump version for provided virtual packages and autopkgtest hints
   * add patch 1001
 to relax dependency to match packaged crate tempfile 3.6.0
Checksums-Sha1:
 da23eb52c3149f2bc5830186ae415c0fee82190e 3792 rust-criterion_0.5.1-1.dsc
 8ddf8df02375e20e1236ab3cf1d037b3a3ef267b 787039 
rust-criterion_0.5.1.orig.tar.gz
 39e487f2c82324f3d0e1308111d0262fe94fbfbf 16292 
rust-criterion_0.5.1-1.debian.tar.xz
 f3c118571db11b64c5ecf2979af4e1f7e2a2b80c 16972 
rust-criterion_0.5.1-1_amd64.buildinfo
Checksums-Sha256:
 44a978466edb1d90c4497c5913892d7234fb2362f2cdc1e80883262c64e44514 3792 
rust-criterion_0.5.1-1.dsc
 561cb44801936262b69a4688929329f9ac7ca03eef956feb164e9dc79ebe3dc0 787039 
rust-criterion_0.5.1.orig.tar.gz
 da13dd2ac3e73ee4d87e1cade1f2364b120fdc570d151355d32c2d0067a07ef2 16292 
rust-criterion_0.5.1-1.debian.tar.xz
 58667fe386de8e42fcafd1e888482a0e283e7b34b9ead9832d4e297b899f4f03 16972 
rust-criterion_0.5.1-1_amd64.buildinfo
Files:
 145f5e71fc333ba86f6a547ec4a53f64 3792 rust optional rust-criterion_0.5.1-1.dsc
 5f827b5e59b44e777433294d196f4e8b 787039 rust optional 
rust-criterion_0.5.1.orig.tar.gz
 c06594c777fecfec61c57f3b71b

Processed: src:python-xarray: fails to migrate to testing for too long: FTBFS

[Debian Bug Tracking System]

Processing control commands:

> close -1 2023.06.0-1
Bug #1041213 [src:python-xarray] src:python-xarray: fails to migrate to testing 
for too long: FTBFS
The source 'python-xarray' and version '2023.06.0-1' do not appear to match any 
binary packages
Marked as fixed in versions python-xarray/2023.06.0-1.
Bug #1041213 [src:python-xarray] src:python-xarray: fails to migrate to testing 
for too long: FTBFS
Marked Bug as done
> block -1 by 1039871
Bug #1041213 {Done: Paul Gevers } [src:python-xarray] 
src:python-xarray: fails to migrate to testing for too long: FTBFS
1041213 was not blocked by any bugs.
1041213 was not blocking any bugs.
Added blocking bug(s) of 1041213: 1039871

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

Bug#1041213: src:python-xarray: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: python-xarray
Version: 2023.01.0-1.1
Severity: serious
Control: close -1 2023.06.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1039871

Dear maintainer(s),

The Release Team considers packages that are out-of-sync between testing 
and unstable for more than 30 days as having a Release Critical bug in 
testing [1]. Your package src:python-xarray has been trying to migrate 
for 34 days [2]. Hence, I am filing this bug. The package fails to build 
from source as reported in bug 1039871.


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: forwarded 1040628 https://github.com/elceef/dnstwist/issues/194

[Debian Bug Tracking System]

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

> forwarded 1040628 https://github.com/elceef/dnstwist/issues/194
Bug #1040628 [src:dnstwist] dnstwist autopkg tests fail with pillow 10.0.0
Set Bug forwarded-to-address to 'https://github.com/elceef/dnstwist/issues/194'.
>
End of message, stopping processing here.

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

Bug#1041211: libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit

[Simon McVittie]

Source: libsdl-perl, sdl12-compat
Control: found -1 libsdl-perl/2.548-3
Control: found -1 sdl12-compat/1.2.64-5
Control: block 1039911 by -1
Severity: serious
Tags: trixie sid ftbfs
User: debian...@lists.debian.org
Usertags: breaks needs-update

Since sdl12-compat took over the libsdl1.2debian and libsdl1.2-dev
packages from the old libsdl1.2, the test suite from libsdl-perl is
sometimes crashing in t/core_video.t. It seems to be failing consistently
on 32-bit architectures, and intermittently on some 64-bit architectures
(arm64 and s390x). I didn't see this before starting the transition
because I had used amd64 for my test-rebuilds, and amd64 seems to be
consistently unaffected.

I originally saw this in the autopkgtest runs on ci.debian.net, but I was
able to reproduce a similar failure during build-time testing on i386.
I didn't see a similar crash when testing real games, so I don't know
whether this is a crash that can affect games in practice, or just a
test issue.

It is not yet clear to me whether this is a libsdl-perl bug or a
sdl12-compat bug, so for now the bug is reported as affecting both
packages. It can be reassigned to either libsdl-perl or sdl12-compat
when a root cause is found.

In the cases where it fails, there are two failure modes that I've seen.
One failure mode is that t/core_video.t crashes with signal 11 (SIGSEGV)
during testing, usually (perhaps always?) after test point 65, for
example in
:


147s t/core_video.t ..
147s ok 1 - SDL::Video->can(...)
147s ok 2 - SDL_SWSURFACE should be imported

...

147s ok 63 - '[get_video_surface] Checking if we get a surface ref back' isa 
'SDL::Surface'
147s ok 64 - [video_driver_name] This is your driver name: dummy
147s ok 65 - [video_mode_ok] Checking if an integer was return
147s All 65 subtests passed
147s(2 TODO tests unexpectedly succeeded)

...

289s t/core_video.t(Wstat: 11 (Signal: SEGV) Tests: 65 Failed: 
0)
289s   TODO passed:   57, 59
289s   Non-zero wait status: 11
289s   Parse errors: No plan found in TAP output


The other failure mode is that t/core_video.t completes testing and calls
done_testing(), but then crashes with SIGSEGV during exit, for example in
:


369s t/core_video.t ..
369s ok 1 - SDL::Video->can(...)
369s ok 2 - SDL_SWSURFACE should be imported
...
369s ok 108 # skip No window manager available
369s ok 109 # skip No window manager available
369s ok 110 - Are we still alive? Checking for segfaults
369s 1..110
369s All 110 subtests passed
369s(less 39 skipped subtests: 71 okay)
369s(2 TODO tests unexpectedly succeeded)

...

499s t/core_video.t(Wstat: 11 (Signal: SEGV) Tests: 110 Failed: 
0)
499s   TODO passed:   57, 59
499s   Non-zero wait status: 11


In the s390x log

we can also see an error message from glibc's malloc implementation
indicating memory corruption, perhaps a double-free or something like
that:


130s ok 64 - [video_driver_name] This is your driver name: dummy
130s ok 65 - [video_mode_ok] Checking if an integer was return
130s corrupted size vs. prev_size


This is blocking migration of sdl12-compat to testing (#1039911).

smcv

Processed: libsdl-perl: FTBFS and autopkgtest failure with sdl12-compat, especially on 32-bit

[Debian Bug Tracking System]

Processing control commands:

> found -1 libsdl-perl/2.548-3
Bug #1041211 [src:libsdl-perl, src:sdl12-compat] libsdl-perl: FTBFS and 
autopkgtest failure with sdl12-compat, especially on 32-bit
Marked as found in versions libsdl-perl/2.548-3.
> found -1 sdl12-compat/1.2.64-5
Bug #1041211 [src:libsdl-perl, src:sdl12-compat] libsdl-perl: FTBFS and 
autopkgtest failure with sdl12-compat, especially on 32-bit
Marked as found in versions sdl12-compat/1.2.64-5.
> block 1039911 by -1
Bug #1039911 [release.debian.org] transition: sdl12-compat taking over 
libsdl1.2-dev
1039911 was not blocked by any bugs.
1039911 was not blocking any bugs.
Added blocking bug(s) of 1039911: 1041211

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

Bug#1041022: marked as done (easyloggingpp FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 17:35:44 +
with message-id 
and subject line Bug#1041022: fixed in easyloggingpp 9.97.0+dfsg-2
has caused the Debian Bug report #1041022,
regarding easyloggingpp FTBFS with googletest 1.13.0
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.)


-- 
1041022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: easyloggingpp
Version: 9.97.0+dfsg-1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/easyloggingpp.html

...
In file included from /usr/include/gtest/gtest-message.h:57,
 from /usr/include/gtest/gtest-assertion-result.h:46,
 from /usr/include/gtest/gtest.h:64,
 from /build/1st/easyloggingpp-9.97.0+dfsg/test/test.h:11,
 from /build/1st/easyloggingpp-9.97.0+dfsg/test/main.cc:3:
/usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less 
than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


Setting CMAKE_CXX_STANDARD to 14 in CMakeLists.txt fixes the build.
--- End Message ---
--- Begin Message ---
Source: easyloggingpp
Source-Version: 9.97.0+dfsg-2
Done: Stephen Kitt 

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

Debian distribution maintenance software
pp.
Stephen Kitt  (supplier of updated easyloggingpp package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 15 Jul 2023 18:47:35 +0200
Source: easyloggingpp
Architecture: source
Version: 9.97.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Stephen Kitt 
Changed-By: Stephen Kitt 
Closes: 1041022
Changes:
 easyloggingpp (9.97.0+dfsg-2) unstable; urgency=medium
 .
   * Require C++14, as specified by googletest 1.13.0. Thanks to Adrian
 Bunk for the hint! Closes: #1041022.
   * Update homepage.
   * Standards-Version 4.6.2, no further change required.
Checksums-Sha1:
 3237299ed067911e3b5f0c84cab0df62de4e6b7c 1959 easyloggingpp_9.97.0+dfsg-2.dsc
 21e94f21f9f09cc3125cdc80b96d404834ae4d82 5804 
easyloggingpp_9.97.0+dfsg-2.debian.tar.xz
 ccf8bcc868bb9250a4a394ab452beae1fe57fdcd 7297 
easyloggingpp_9.97.0+dfsg-2_source.buildinfo
Checksums-Sha256:
 bce90e104d0e1fb0b9b61de1c422847f9afc2f766210bf7c1d7ae7ad1f975404 1959 
easyloggingpp_9.97.0+dfsg-2.dsc
 9f993e9579e5e6dba3a77fac82cbcf174571c7f93d59541120168ab2c73d9b72 5804 
easyloggingpp_9.97.0+dfsg-2.debian.tar.xz
 8a0f388d989193fc832e3fdfe55f9686d95481a9c8075d7f4a1a5fb0fa7baf2d 7297 
easyloggingpp_9.97.0+dfsg-2_source.buildinfo
Files:
 73e0e00059e76b9852cfe75af1df6fda 1959 libs optional 
easyloggingpp_9.97.0+dfsg-2.dsc
 933a0b1f8c7e0f2ec83a1df2cdff2a2c 5804 libs optional 
easyloggingpp_9.97.0+dfsg-2.debian.tar.xz
 2f23b2217539c20820fb46938148196f 7297 libs optional 
easyloggingpp_9.97.0+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEnPVX/hPLkMoq7x0ggNMC9Yhtg5wFAmSyzbUACgkQgNMC9Yht
g5xUJw//cVpZ2RxBjru9P5qq4mmAAW5wLC4dZtKpqICEcspXYrlDUBI7vjdcdo6H
KL6xOS+erUwqM6iHCVPJpRLAQj+pfB0340c1PiICEes5XenHkc2Te39r+ClsfGUl
OR4Lkw9PhBL355V2w8J7u9v6OA1vhKVjvtXNYv6Svs/Nh7TIOcepQD8R09Yq9bRE
TeY8TExocgqt93e25VdU1veeBPrnMFNocnlIgZ6pRuPuFlM/UlQsqqbzTTw9Tn9l
qRsxGeiiCLYQFb2aW7sZ642EzdgjES7Qfe7N/vATW2+oTJGzErKBLinM61DuoJt4
zbwzQ0wmyqeF4fS7Idl02bYTW8qPrrPxu8NmGJmKNwtCHCxGzqLnoqEyQj5QrHqi
Btm1J1nMbyBe7xnjk6A7bG3A5jUADgbUG0tupfhFcWRajHNjVt/S7JF1ZkYoPdnw
3zd6ZSVbVJMUoYmqObNidwCoyoNp/fss9vC4FrGZOciIQgeoIKH2NSeFGdiwjVrP
w0KxGAKgPKG2/jCJQG1DKsTBQ+UoKLxLmES7H83qZIVZXq3LTEsEJc6HavsgKoZu
i70kWidpGup/Rp4m653Q+eNdqSG/nUdXAHwXcWKot7G46XQNojAa89pACJM6QK9s
Km0iRnHxkXsLsiJAi/BSCRFCCr3HpMNGYTDE7ELCCHVX/+N1+cY=
=RK8Q
-END PGP SIGNATURE End Message ---

Bug#1037646: marked as done (falcosecurity-libs: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 17:36:12 +
with message-id 
and subject line Bug#1037646: fixed in falcosecurity-libs 0.11.3+repack-1
has caused the Debian Bug report #1037646,
regarding falcosecurity-libs: ftbfs with GCC-13
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.)


-- 
1037646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:falcosecurity-libs
Version: 0.1.1dev+git20220316.e5c53d64-5.1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/falcosecurity-libs_0.1.1dev+git20220316.e5c53d64-5.1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
  |   ^~
/<>/userspace/libsinsp/prefix_search.cpp:87:80: error: request for 
member ‘first’ in ‘path’, which is of non-class type ‘const filter_value_t’ 
{aka ‘const int’}
   87 | components.emplace_back(pos, path.second - (pos 
- path.first));
  | 
   ^
/<>/userspace/libsinsp/prefix_search.cpp:88:36: error: request for 
member ‘first’ in ‘path’, which is of non-class type ‘const filter_value_t’ 
{aka ‘const int’}
   88 | pos = path.first + path.second + 1;
  |^
/<>/userspace/libsinsp/prefix_search.cpp:88:49: error: request for 
member ‘second’ in ‘path’, which is of non-class type ‘const filter_value_t’ 
{aka ‘const int’}
   88 | pos = path.first + path.second + 1;
  | ^~
/<>/userspace/libsinsp/prefix_search.h: In instantiation of 
‘std::string path_prefix_map::as_string(const std::string&, bool) [with 
Value = bool; std::string = std::__cxx11::basic_string]’:
/<>/userspace/libsinsp/prefix_search.h:293:18:   required from 
‘std::string path_prefix_map::as_string(bool) [with Value = bool; 
std::string = std::__cxx11::basic_string]’
/<>/userspace/libsinsp/prefix_search.cpp:64:41:   required from 
here
/<>/userspace/libsinsp/prefix_search.h:304:60: error: request for 
member ‘first’ in ‘it.std::pair*, 
bool*> >::first’, which is of non-class type ‘const int’
  304 | std::string dirent((const char *) it.first.first, 
it.first.second);
  |   ~^
make[3]: *** [libsinsp/CMakeFiles/sinsp.dir/build.make:457: 
libsinsp/CMakeFiles/sinsp.dir/prefix_search.cpp.o] Error 1
make[3]: *** Waiting for unfinished jobs
/<>/userspace/libsinsp/logger.cpp: In member function ‘void 
sinsp_logger::log(std::string, severity)’:
/<>/userspace/libsinsp/logger.cpp:167:59: warning: ‘.’ directive 
output may be truncated writing 1 byte into a region of size between 0 and 9 
[-Wformat-truncation=]
  167 |  "%.2d-%.2d %.2d:%.2d:%.2d.%.6d ",
  |   ^
In member function ‘void sinsp_logger::log(std::string, severity)’,
inlined from ‘void sinsp_logger::log(std::string, severity)’ at 
/<>/userspace/libsinsp/logger.cpp:138:6:
/<>/userspace/libsinsp/logger.cpp:167:34: note: using the range 
[-2147483648, 2147483647] for directive argument
  167 |  "%.2d-%.2d %.2d:%.2d:%.2d.%.6d ",
  |  ^~~~
In file included from /usr/include/s

Bug#1034881: marked as done (falcosecurity-scap-dkms: Cannot compile linux kernel 6.2.12 due to failure with scap dkms)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 17:36:12 +
with message-id 
and subject line Bug#1034881: fixed in falcosecurity-libs 0.11.3+repack-1
has caused the Debian Bug report #1034881,
regarding falcosecurity-scap-dkms: Cannot compile linux kernel 6.2.12 due to 
failure with scap dkms
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.)


-- 
1034881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1034881
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: falcosecurity-scap-dkms
Version: 0.1.1dev+git20220316.e5c53d64-5.1
Severity: important
Tags: patch upstream

Dear Maintainer,

I've tried to compile linux kernel 6.2.12, but when I wanted to install
it I had the following errors:

root@warpcore:/usr/src/linux-6.2.12# make install
  INSTALL /boot
run-parts: executing /etc/kernel/postinst.d/dkms 6.2.12 /boot/vmlinuz-6.2.12
dkms: running auto installation service for kernel 6.2.12.
Sign command: /lib/modules/6.2.12/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Building module:
Cleaning build area...
make -j16 KERNELRELEASE=6.2.12 -C /lib/modules/6.2.12/build 
M=/var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.2.12 (x86_64)
Consult /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/make.log for 
more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.2.12 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
make: *** [arch/x86/Makefile:292: install] Error 1
root@warpcore:/usr/src/linux-6.2.12#

The log shows:

root@warpcore:/usr/src/linux-6.2.12# cat  
/var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/make.log
DKMS make.log for scap-0.1.1dev+git20220316.e5c53d64 for kernel 6.2.12 (x86_64)
Wed Apr 26 12:35:26 PM -03 2023
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/main.o
  CC [M]  
/var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/dynamic_params_table.o
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/fillers_table.o
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/flags_table.o
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/ppm_events.o
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/ppm_fillers.o
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/event_table.o
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/syscall_table.o
  CC [M]  /var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/ppm_cputime.o
/var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/main.c: In function 
‘scap_init’:
/var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/main.c:2501:30: error: 
assignment to ‘char * (*)(const struct device *, umode_t *)’ {aka ‘char * 
(*)(const struct device *, short unsigned int *)’} from incompatible pointer 
type ‘char * (*)(struct device *, umode_t *)’ {aka ‘char * (*)(struct device *, 
short unsigned int *)’} [-Werror=incompatible-pointer-types]
 2501 | g_ppm_class->devnode = ppm_devnode;
  |  ^
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:252: 
/var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build/main.o] Error 1
make[2]: *** Waiting for unfinished jobs
make[1]: *** [Makefile:2021: 
/var/lib/dkms/scap/0.1.1dev+git20220316.e5c53d64/build] Error 2

I've found patches on two sources:

https://bugs.launchpad.net/ubuntu/+source/falcosecurity-libs/+bug/2009505
https://github.com/falcosecurity/libs/issues/918

Patch in https://github.com/falcosecurity/libs/issues/918 seems to have
worked and compiled just fine.

I believe the debian package just needs to be updated since it's
already been updated in upstream several times.

Thank you!

Best regards,
Dario Susman

-- System Information:
Debian Release: 12.0
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-7-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=locale: Cannot set 
LC_ALL to default locale: No such file or directory
UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages falcosecurity-scap-dkms depends on:
ii  dkms  3.0.10-8

Versions of packages falcosecurity-scap-dkms recommends:
ii  sysdig  0.29.3-1+b1

falcosecurity-scap-dkms sugge

Bug#1037605: marked as done (claws-mail: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 17:10:15 +
with message-id 
and subject line Bug#1037605: fixed in claws-mail 4.1.1-3
has caused the Debian Bug report #1037605,
regarding claws-mail: ftbfs with GCC-13
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.)


-- 
1037605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037605
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:claws-mail
Version: 4.1.1-2
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/claws-mail_4.1.1-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
document.h:79:78: error: ‘uint_ptr’ has not been declared
   79 | void
draw(uint_ptr hdc, int x, int y, const position* clip);
  | 
 ^~~~
document.h:109:27: error: ‘uint_ptr’ in namespace ‘litehtml’ does not name a 
type
  109 | litehtml::uint_ptr  add_font(const tchar_t* name, 
int size, const tchar_t* weight, const tchar_t* style, const tchar_t* 
decoration, font_metrics* fm);
  |   ^~~~
In file included from document.cpp:5:
el_text.h:25:62: error: ‘uint_ptr’ has not been declared
   25 | virtual voiddraw(uint_ptr 
hdc, int x, int y, const position* clip) override;
  |  ^~~~
el_text.h:27:25: error: ‘uint_ptr’ does not name a type; did you mean 
‘const_ptr’?
   27 | virtual uint_ptr
get_font(font_metrics* fm = 0) override;
  | ^~~~
  | const_ptr
In file included from document.cpp:9:
el_image.h:21:38: error: ‘uint_ptr’ has not been declared
   21 | virtual voiddraw(uint_ptr hdc, int x, int y, const 
position* clip) override;
  |  ^~~~
document.cpp: In destructor ‘virtual litehtml::document::~document()’:
document.cpp:44:60: error: ‘struct litehtml::font_item’ has no member named 
‘font’
   44 | m_container->delete_font(f->second.font);
  |^~~~
document.cpp: At global scope:
document.cpp:130:11: error: ‘uint_ptr’ in namespace ‘litehtml’ does not name a 
type
  130 | litehtml::uint_ptr litehtml::document::add_font( const tchar_t* name, 
int size, const tchar_t* weight, const tchar_t* style, const tchar_t* 
decoration, font_metrics* fm )
  |   ^~~~
document.cpp:221:11: error: ‘uint_ptr’ in namespace ‘litehtml’ does not name a 
type
  221 | litehtml::uint_ptr litehtml::document::get_font( const tchar_t* name, 
int size, const tchar_t* weight, const tchar_t* style, const tchar_t* 
decoration, font_metrics* fm )
  |   ^~~~
document.cpp:284:6: error: variable or field ‘draw’ declared void
  284 | void litehtml::document::draw( uint_ptr hdc, int x, int y, const 
position* clip )
  |  ^~~~
document.cpp:284:32: error: ‘uint_ptr’ was not declared in this scope; did you 
mean ‘wint_t’?
  284 | void litehtml::document::draw( uint_ptr hdc, int x, int y, const 
position* clip )
  |^~~~
  |wint_t
document.cpp:284:46: error: expected primary-expression before ‘int’
  284 | void litehtml::document::dra

Bug#1041024: marked as done (movit FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 16:41:20 +
with message-id 
and subject line Bug#1041024: fixed in movit 1.7.0-1
has caused the Debian Bug report #1041024,
regarding movit FTBFS with googletest 1.13.0
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.)


-- 
1041024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041024
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: movit
Version: 1.6.3-5
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/movit.html

...
In file included from /usr/src/gtest/include/gtest/gtest-message.h:57,
 from /usr/src/gtest/include/gtest/gtest-assertion-result.h:46,
 from /usr/src/gtest/include/gtest/gtest.h:64,
 from /usr/src/gtest/src/gtest-all.cc:38:
/usr/src/gtest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ 
versions less than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...


Removing the line
  CXXFLAGS="$CXXFLAGS -std=gnu++11"
from configure.ac fixes the build.
--- End Message ---
--- Begin Message ---
Source: movit
Source-Version: 1.7.0-1
Done: Steinar H. Gunderson 

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

Debian distribution maintenance software
pp.
Steinar H. Gunderson  (supplier of updated movit 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, 15 Jul 2023 17:42:03 +0200
Source: movit
Architecture: source
Version: 1.7.0-1
Distribution: unstable
Urgency: medium
Maintainer: Steinar H. Gunderson 
Changed-By: Steinar H. Gunderson 
Closes: 917021 1041024
Changes:
 movit (1.7.0-1) unstable; urgency=medium
 .
   * New upstream release.
 * Fixes compile error with newer Google Test. (Closes: #1041024)
 * No longer installs shaders, so Conflicts: with differently-versioned
   packages are no longer needed. (Closes: #917021)
Checksums-Sha1:
 98784259303afcd2ebf8e7c409f010cb171302ed 1831 movit_1.7.0-1.dsc
 59a578a0bcd028fcce7252e058b0a900ec0dfe21 606989 movit_1.7.0.orig.tar.gz
 226bbf51c082045080df01af87607c3ef0e71394 4024 movit_1.7.0-1.debian.tar.xz
 1430df41978275722699ebe4bfd21bb536b3019b 11482 movit_1.7.0-1_amd64.buildinfo
Checksums-Sha256:
 8b37505864bcf70c3501704930d0feaf87ca8ed0bbe4e82f3c6db30f89f10c4a 1831 
movit_1.7.0-1.dsc
 23597b93ea53762d44df763ecc2b702308f76fc17382099e9385220081ce6610 606989 
movit_1.7.0.orig.tar.gz
 316b5a7ee9c2a709d7e5ac91bbc562af004e56626df940396ab487918610e981 4024 
movit_1.7.0-1.debian.tar.xz
 16e892c37699c430c9c72443071510a6751a9b634b569fd059b0d05d583e508c 11482 
movit_1.7.0-1_amd64.buildinfo
Files:
 b26b9ef008ebf4eb4c13d9f7caa84d49 1831 libs optional movit_1.7.0-1.dsc
 edc3bd3444e3ac3c7e63273df71e6bcc 606989 libs optional movit_1.7.0.orig.tar.gz
 3c5094ce3c161212b82c23e586a3d2d9 4024 libs optional movit_1.7.0-1.debian.tar.xz
 6c682ffc044da2c99480aa54766c02bd 11482 libs optional 
movit_1.7.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwukAT/AowY5OrduDf2F1YXeXj3YFAmSywHMACgkQf2F1YXeX
j3bnog//W9vgaQajPNjyvCUvr2P9v/Z9QVkOoSVMVk/QuyPulCkIbgw2SxfbkpJJ
syZddvzcx6Alv9ps7pIBYVQnO/5YvmtEQQs28B+bb6mjo3wEYCbl7d02ELTxxnUu
x5OlpCJAztNZqGZT2XptV5DPlHzsCdO3lBM+EEFdjmNlHaDbUfgbaAkhgL2iOtLw
HBx/FCM0dCLYMp0JQHQc1XgDdKSP4epnfnTTeHvc5ImdJxbZIWSf+ncbIokGkmrH
PLVUu7sWVmXksdYH+SkE0YzesCDEYzWW4XD19PKBV+NFUR3INyS/OS4FlzrgX1qk
9pRB2/Lw45hmFrWvULqYv6SGYNUSJyvra7/mum7P7CUncO/xBGpWx7rXuV2mbmHX
KRPEVexIVT7ptr/D32e1tOUSnSjk8hwaXsmwlo2w4TVi7HuDbeWhlkLwZA1FohGT
aasCoMPptGohbDF1lxHgAX+/Webaqcu/B4/baoyY4J5BLEXnFSxpf7L/8joRh8kc
ZDw+vu3D+aAQkcLgQFBXPCbRRiRHftHDxZfiNGbJb5b2HyPcQqqh5bBQpUfbMSsU
kCEn9idNIAPYSRmbZAfE/S30lKMfQiIbX559UJ6Bxh5/sTGX2uFZts3kif8GoM6p
3Q09MDuvTmsl1We34RdWcaUCiZh0WThpqdl+WzQ0IAvWbciguFo=
=LmOt
-END PGP SIGNATURE End Message ---

Bug#1037785: marked as done (nageru: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 16:41:29 +
with message-id 
and subject line Bug#1037785: fixed in nageru 2.2.2-1
has caused the Debian Bug report #1037785,
regarding nageru: ftbfs with GCC-13
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.)


-- 
1037785: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037785
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:nageru
Version: 2.2.1-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/nageru_2.2.1-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
   12 | fprintf(stderr, "%s:%d (%s) failed: %s\n", __func__, 
__LINE__, func, vaErrorStr(va_status)); \
  | ^~
../shared/va_resource_pool.cpp:82:17: note: in expansion of macro 
‘CHECK_VASTATUS’
   82 | CHECK_VASTATUS(va_status, "vaDestroySurfaces");
  | ^~
../shared/va_resource_pool.h:12:25: note: ‘stderr’ is defined in header 
‘’; did you forget to ‘#include ’?
   12 | fprintf(stderr, "%s:%d (%s) failed: %s\n", __func__, 
__LINE__, func, vaErrorStr(va_status)); \
  | ^~
../shared/va_resource_pool.cpp:82:17: note: in expansion of macro 
‘CHECK_VASTATUS’
   82 | CHECK_VASTATUS(va_status, "vaDestroySurfaces");
  | ^~
../shared/va_resource_pool.h:12:17: error: ‘fprintf’ was not declared in this 
scope
   12 | fprintf(stderr, "%s:%d (%s) failed: %s\n", __func__, 
__LINE__, func, vaErrorStr(va_status)); \
  | ^~~
../shared/va_resource_pool.cpp:82:17: note: in expansion of macro 
‘CHECK_VASTATUS’
   82 | CHECK_VASTATUS(va_status, "vaDestroySurfaces");
  | ^~
../shared/va_resource_pool.h:13:17: error: ‘exit’ was not declared in this scope
   13 | exit(1); \
  | ^~~~
../shared/va_resource_pool.cpp:82:17: note: in expansion of macro 
‘CHECK_VASTATUS’
   82 | CHECK_VASTATUS(va_status, "vaDestroySurfaces");
  | ^~
../shared/va_resource_pool.h:13:17: note: ‘exit’ is defined in header 
‘’; did you forget to ‘#include ’?
   13 | exit(1); \
  | ^~~~
../shared/va_resource_pool.cpp:82:17: note: in expansion of macro 
‘CHECK_VASTATUS’
   82 | CHECK_VASTATUS(va_status, "vaDestroySurfaces");
  | ^~
../shared/va_resource_pool.h:12:25: error: ‘stderr’ was not declared in this 
scope
   12 | fprintf(stderr, "%s:%d (%s) failed: %s\n", __func__, 
__LINE__, func, vaErrorStr(va_status)); \
  | ^~
../shared/va_resource_pool.cpp:85:17: note: in expansion of macro 
‘CHECK_VASTATUS’
   85 | CHECK_VASTATUS(va_status, "vaDestroyImage");
  | ^~
../shared/va_resource_pool.h:12:25: note: ‘stderr’ is defined in header 
‘’; did you forget to ‘#include ’?
   12 | fprintf(stderr, "%s:%d (%s) failed: %s\n", __func__, 
__LINE__, func, vaErrorStr(va_status)); \
  | ^~
../shared/va_resource_pool.cpp:85:17: note: in expansion of macro 
‘CHECK_VASTATUS’
   85 | CHECK_VASTATUS(va_status, "vaDestroyImage");
  | ^~
../shared/va_resource_pool.h:12:17: error: ‘fprintf’ was not declared in this 
s

Bug#1039686: marked as done (nvidia-open-gpu-kernel-modules: CVE-2023-25515, CVE-2023-25516)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 16:32:11 +
with message-id 
and subject line Bug#1039686: fixed in nvidia-open-gpu-kernel-modules 
525.125.06-1~deb12u1
has caused the Debian Bug report #1039686,
regarding nvidia-open-gpu-kernel-modules: CVE-2023-25515, CVE-2023-25516
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.)


-- 
1039686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-25515, 
CVE-2023-25516
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-25515, 
CVE-2023-25516
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-25515, 
CVE-2023-25516
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-25515, 
CVE-2023-25516
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5468

CVE-2023-25515  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where unexpected untrusted data is parsed, which may
lead to code execution, denial of service, escalation of privileges,
data tampering, or information disclosure.

CVE-2023-25516  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged user can
cause an integer overflow, which may lead to information disclosure and
denial of service.

Linux Driver Branch CVE IDs Addressed
R535, R525, R470, R450  CVE-2023-25515, CVE-2023-25516

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R535All driver versions prior to 535.54.03  535.54.03
R525All driver versions prior to 525.125.06 525.125.06
R470All driver versions prior to 470.199.02 470.199.02
R450All driver versions prior to 450.248.02 450.248.02

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-open-gpu-kernel-modules
Source-Version: 525.125.06-1~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-open-gpu-kernel-modules 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: Fri, 14 Jul 2023 12:17:23 +0200
Source: nvidia-open-gpu-kernel-modules
Architecture: source
Version: 525.125.06-1~deb12

Bug#1039685: marked as done (nvidia-graphics-drivers-tesla: CVE-2023-25515, CVE-2023-25516)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 16:32:11 +
with message-id 
and subject line Bug#1039685: fixed in nvidia-graphics-drivers-tesla 
525.125.06-1~deb12u1
has caused the Debian Bug report #1039685,
regarding nvidia-graphics-drivers-tesla: CVE-2023-25515, CVE-2023-25516
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.)


-- 
1039685: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039685
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-25515, 
CVE-2023-25516
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-25515, 
CVE-2023-25516
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-25515, 
CVE-2023-25516
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-25515, 
CVE-2023-25516
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5468

CVE-2023-25515  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where unexpected untrusted data is parsed, which may
lead to code execution, denial of service, escalation of privileges,
data tampering, or information disclosure.

CVE-2023-25516  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged user can
cause an integer overflow, which may lead to information disclosure and
denial of service.

Linux Driver Branch CVE IDs Addressed
R535, R525, R470, R450  CVE-2023-25515, CVE-2023-25516

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R535All driver versions prior to 535.54.03  535.54.03
R525All driver versions prior to 525.125.06 525.125.06
R470All driver versions prior to 470.199.02 470.199.02
R450All driver versions prior to 450.248.02 450.248.02

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla
Source-Version: 525.125.06-1~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla 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: Wed, 12 Jul 2023 18:07:03 +0200
Source: nvidia-graphics-drivers-tesla
Architecture: source
Version: 525.125.06-1~deb12u1
Dis

Bug#1039678: marked as done (nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 16:32:11 +
with message-id 
and subject line Bug#1039678: fixed in nvidia-graphics-drivers-tesla 
525.125.06-1~deb12u1
has caused the Debian Bug report #1039678,
regarding nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516
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.)


-- 
1039678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-25515, 
CVE-2023-25516
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-25515, 
CVE-2023-25516
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-25515, 
CVE-2023-25516
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-25515, 
CVE-2023-25516
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5468

CVE-2023-25515  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where unexpected untrusted data is parsed, which may
lead to code execution, denial of service, escalation of privileges,
data tampering, or information disclosure.

CVE-2023-25516  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged user can
cause an integer overflow, which may lead to information disclosure and
denial of service.

Linux Driver Branch CVE IDs Addressed
R535, R525, R470, R450  CVE-2023-25515, CVE-2023-25516

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R535All driver versions prior to 535.54.03  535.54.03
R525All driver versions prior to 525.125.06 525.125.06
R470All driver versions prior to 470.199.02 470.199.02
R450All driver versions prior to 450.248.02 450.248.02

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla
Source-Version: 525.125.06-1~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla 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: Wed, 12 Jul 2023 18:07:03 +0200
Source: nvidia-graphics-drivers-tesla
Architecture: source
Version: 525.125.06-1~deb12u1
Distribut

Bug#1039678: marked as done (nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 16:32:10 +
with message-id 
and subject line Bug#1039678: fixed in nvidia-graphics-drivers 
525.125.06-1~deb12u1
has caused the Debian Bug report #1039678,
regarding nvidia-graphics-drivers: CVE-2023-25515, CVE-2023-25516
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.)


-- 
1039678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039678
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
X-Debbugs-Cc: Debian Security Team 
Control: clone -1 -2 -3 -4 -5 -6 -7 -8 -9
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2023-25515, 
CVE-2023-25516
Control: tag -3 + wontfix
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2023-25515, 
CVE-2023-25516
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2023-25515, 
CVE-2023-25516
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2023-25515, 
CVE-2023-25516
Control: reassign -8 src:nvidia-graphics-drivers-tesla 510.85.02-1
Control: retitle -8 nvidia-graphics-drivers-tesla: CVE-2023-25515, 
CVE-2023-25516
Control: found -8 515.48.07-1
Control: found -8 525.60.13-1
Control: reassign -9 src:nvidia-open-gpu-kernel-modules 515.43.04-1
Control: retitle -9 nvidia-open-gpu-kernel-modules: CVE-2023-25515, 
CVE-2023-25516
Control: found -9 520.56.06-1
Control: found -9 525.85.12-1
Control: found -9 530.30.02-1
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1
Control: found -1 515.48.07-1
Control: found -1 520.56.06-1
Control: found -1 525.53-1
Control: found -1 530.30.02-1

https://nvidia.custhelp.com/app/answers/detail/a_id/5468

CVE-2023-25515  NVIDIA GPU Display Driver for Windows and Linux contains
a vulnerability where unexpected untrusted data is parsed, which may
lead to code execution, denial of service, escalation of privileges,
data tampering, or information disclosure.

CVE-2023-25516  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where an unprivileged user can
cause an integer overflow, which may lead to information disclosure and
denial of service.

Linux Driver Branch CVE IDs Addressed
R535, R525, R470, R450  CVE-2023-25515, CVE-2023-25516

Driver Branch   Affected Driver VersionsUpdated Driver 
Version
R535All driver versions prior to 535.54.03  535.54.03
R525All driver versions prior to 525.125.06 525.125.06
R470All driver versions prior to 470.199.02 470.199.02
R450All driver versions prior to 450.248.02 450.248.02

Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 525.125.06-1~deb12u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
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: Wed, 12 Jul 2023 16:16:16 +0200
Source: nvidia-graphics-drivers
Architecture: source
Version: 525.125.06-1~deb12u1
Distribution: bookworm
Urgency: medium
M

Processed: reassign 1040835 to src:rust-log, reassign 1040995 to src:rust-log ..., affects 1040837

[Debian Bug Tracking System]

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

> reassign 1040835 src:rust-log
Bug #1040835 [librust-async-std-dev] librust-async-std-dev: impossible to 
install: missing dependency librust-log-0.4+kv-unstable-dev
Bug reassigned from package 'librust-async-std-dev' to 'src:rust-log'.
No longer marked as found in versions rust-async-std/1.12.0-12.
Ignoring request to alter fixed versions of bug #1040835 to the same values 
previously set
> reassign 1040995 src:rust-log
Bug #1040995 [librust-kv-log-macro-dev] librust-kv-log-macro-dev is no longer 
installable
Bug reassigned from package 'librust-kv-log-macro-dev' to 'src:rust-log'.
No longer marked as found in versions rust-kv-log-macro/1.0.8-2.
Ignoring request to alter fixed versions of bug #1040995 to the same values 
previously set
> forcemerge 1040837 1040835 1040995
Bug #1040837 [src:rust-log] rust-log: breaks API without coordination
Bug #1040995 [src:rust-log] librust-kv-log-macro-dev is no longer installable
Added indication that 1040995 affects 
rust-async-attributes,rust-ahash,rust-flume,rust-async-tar,rust-oxilangtag,rust-trust-dns-client,rust-trust-dns-server,rust-ahash-0.7,rust-async-std-resolver,aardvark-dns,rust-oxiri,rust-trust-dns-resolver,rust-ashpd,rust-sequoia-net,rust-rustls,rust-futures-timer,rust-erbium
Marked as found in versions rust-log/0.4.19-2.
Bug #1040837 [src:rust-log] rust-log: breaks API without coordination
1040835 was blocked by: 1040837
1040835 was not blocking any bugs.
Removed blocking bug(s) of 1040835: 1040837
Added tag(s) trixie and sid.
Bug #1040835 [src:rust-log] librust-async-std-dev: impossible to install: 
missing dependency librust-log-0.4+kv-unstable-dev
Severity set to 'serious' from 'grave'
Added indication that 1040835 affects 
rust-async-attributes,rust-ahash,rust-flume,rust-async-tar,rust-oxilangtag,rust-trust-dns-client,rust-trust-dns-server,rust-ahash-0.7,rust-async-std-resolver,aardvark-dns,rust-oxiri,rust-trust-dns-resolver,rust-ashpd,rust-sequoia-net,rust-rustls,rust-futures-timer,rust-erbium
Marked as found in versions rust-log/0.4.19-2.
Merged 1040835 1040837 1040995
> affects 1040837 librust-kv-log-macro-dev
Bug #1040837 [src:rust-log] rust-log: breaks API without coordination
Bug #1040835 [src:rust-log] librust-async-std-dev: impossible to install: 
missing dependency librust-log-0.4+kv-unstable-dev
Bug #1040995 [src:rust-log] librust-kv-log-macro-dev is no longer installable
Added indication that 1040837 affects librust-kv-log-macro-dev
Added indication that 1040835 affects librust-kv-log-macro-dev
Added indication that 1040995 affects librust-kv-log-macro-dev
> thanks
Stopping processing here.

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

Bug#1041207: debootstrap: bad NMU produces buildds not supported by dpkg _and_ CTTE

[Adam Borowski]

Package: debootstrap
Version: 1.0.128+nmu3
Severity: grave

bluca's NMU on 2023-07-15 makes debootstrap produce chroots using the
aliased-dirs scheme.  While it's currently the default scheme for non-buildd
systems, it is both not supported by dpkg (with no solution in sight), but
is also likely to produce packages that are explicitely forbidden by a
recent CTTE ruling that disallows moving files between directories aliased
by the current usrmerge scheme.

Quoting the still unsolving issues is pointless (you can read about them
in massive threads in a number of places) as bluca seems to be ignoring
them completely.

But, what matters here is the CTTE ruling in #1035831 -- for the time being,
packages must not move files between locations affected by the aliasing.

Packages built in an usrmerged chroot place such files under /usr while
built without usrmerge into whatever place they were installed to -- which
is a direct breach of the ruling.

Thus, that change needs to be reverted for now, and all packages built
with 1.0.128+nmu3 need to be either rebuilt or at least checked for such
a violation (as most are unaffected).


Meow!
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-rc1-00036-gc493f11e457d (SMP w/64 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages debootstrap depends on:
ii  wget  1.21.3-1+b2

Versions of packages debootstrap recommends:
ii  arch-test   0.21-1
ii  debian-archive-keyring  2023.3
ii  gnupg   2.2.40-1.1

Versions of packages debootstrap suggests:
ii  binutils 2.40.90.20230705-1
pn  squid-deb-proxy-client   
ii  ubuntu-archive-keyring   2020.06.17.1-1
ii  ubuntu-keyring [ubuntu-archive-keyring]  2020.06.17.1-1
ii  xz-utils 5.4.1-0.2
ii  zstd 1.5.5+dfsg2-1

-- no debconf information

Processed (with 1 error): forcibly merging 1040837 1040835 1040995

[Debian Bug Tracking System]

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

> forcemerge 1040837 1040835 1040995
Bug #1040837 [src:rust-log] rust-log: breaks API without coordination
Unable to merge bugs because:
package of #1040995 is 'librust-kv-log-macro-dev' not 'src:rust-log'
package of #1040835 is 'librust-async-std-dev' not 'src:rust-log'
Failed to forcibly merge 1040837: Did not alter merged bugs.

> thanks
Stopping processing here.

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

Processed: tagging 1037605

[Debian Bug Tracking System]

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

> tags 1037605 + pending
Bug #1037605 [src:claws-mail] claws-mail: ftbfs with GCC-13
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1037603: marked as done (civetweb: ftbfs with GCC-13)

[Andreas Tille]

Hi Sebastien,

seems you closed the wrong bug with your upload.  The package you
uploaded is orthanc-postgresql but the bug concerns civetweb.

Kind regards
Andreas.

Am Sat, Jul 15, 2023 at 12:09:18PM + schrieb Debian Bug Tracking System:
> Your message dated Sat, 15 Jul 2023 12:07:17 +
> with message-id 
> and subject line Bug#1037603: fixed in orthanc-postgresql 5.0+dfsg-1
> has caused the Debian Bug report #1037603,
> regarding civetweb: ftbfs with GCC-13
> 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.)
> 
> 
> -- 
> 1037603: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037603
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

> Date: Wed, 14 Jun 2023 09:22:26 +
> From: Matthias Klose 
> To: mainto...@bugs.debian.org
> Subject: civetweb: ftbfs with GCC-13
> 
> Package: src:civetweb
> Version: 1.15+dfsg-4
> Severity: normal
> Tags: sid trixie
> User: debian-...@lists.debian.org
> Usertags: ftbfs-gcc-13
> 
> [This bug is targeted to the upcoming trixie release]
> 
> Please keep this issue open in the bug tracker for the package it
> was filed for.  If a fix in another package is required, please
> file a bug for the other package (or clone), and add a block in this
> package. Please keep the issue open until the package can be built in
> a follow-up test rebuild.
> 
> The package fails to build in a test rebuild on at least amd64 with
> gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
> severity of this report will be raised before the trixie release.
> 
> The full build log can be found at:
> http://qa-logs.debian.net/2023/05/22/logs/civetweb_1.15+dfsg-4_unstable_gccexp.log
> The last lines of the build log are at the end of this report.
> 
> To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
> or install the gcc, g++, gfortran, ... packages from experimental.
> 
>   apt-get -t=experimental install g++ 
> 
> Common build failures are new warnings resulting in build failures with
> -Werror turned on, or new/dropped symbols in Debian symbols files.
> For other C/C++ related build failures see the porting guide at
> http://gcc.gnu.org/gcc-13/porting_to.html
> 
> [...]
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-targets.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-targets-none.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-config.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/civetweb-config-version.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/FindLibDl.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/FindLibRt.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/cmake/civetweb/FindWinSock.cmake
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb.so.1.15.0
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb.so.1
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb.so
> -- Installing: /<>/debian/tmp/usr/include/civetweb.h
> -- Installing: /<>/debian/tmp/usr/bin/civetweb
> -- Set runtime path of "/<>/debian/tmp/usr/bin/civetweb" to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1.15.0
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1
> -- Set runtime path of 
> "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1.15.0"
>  to ""
> -- Installing: 
> /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so
> -- Installing: /<>/debian/tmp/usr/include/CivetServer.h
> make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu'
>dh_install -O--buildsystem=cmake
>dh_installdocs -O--buildsystem=cmake
>dh_installchangelogs -O--buildsystem=cmake
>dh_installman -O--buildsystem=cmake
>dh_installsystemduser -O--buildsystem=cmake
>dh_perl -O--buildsystem=cmake
>dh_link -O--buildsystem=cmake
>dh_strip_nondeterminism -O--buildsystem=cmake
>dh_compress -O--buildsystem=cmake
>dh_fixperms -O--buildsystem=cmake
>dh_missing -O--buildsystem=cmake
>dh_dwz -a -O--buildsystem=cmake
> dwz: debian/libcivetweb1/usr/lib/x86_64-linux-gnu/libcivetweb.so.1.15.0: 
> DWARF compression not beneficial - old size 164499 new size 167095
> dwz: debian/libcivetweb1/usr/lib/x86_64-linux-gnu/libcivetweb-cpp.so.1.15.0: 
> DWARF compression not beneficial - old size 297647 new size 300459
>dh_strip -a -O--buildsystem=cmake
>dh_makeshlibs -a -O--buildsystem=cmake
> dpkg-g

Bug#1041206: python-clickhouse-driver: FTBFS if source is included: aborting due to unexpected upstream changes

[Adam Borowski]

Source: python-clickhouse-driver
Version: 0.2.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi!
With any build type that includes the source, your package fails with:

dpkg-source: info: local changes detected, the modified files are:
 python-clickhouse-driver-0.2.5/clickhouse_driver/bufferedreader.c
 python-clickhouse-driver-0.2.5/clickhouse_driver/bufferedwriter.c
 python-clickhouse-driver-0.2.5/clickhouse_driver/columns/largeint.c
 python-clickhouse-driver-0.2.5/clickhouse_driver/varint.c
dpkg-source: error: aborting due to unexpected upstream changes, see 
/tmp/python-clickhouse-driver_0.2.5-1.diff.aYpmik
dpkg-source: info: Hint: make sure the version in debian/changelog matches the 
unpacked source tree


Full build log attached.


Meow!
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-rc1-00036-gc493f11e457d (SMP w/64 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
sbuild (Debian sbuild) 0.85.2 (11 March 2023) on valinor.angband.pl

+==+
| python-clickhouse-driver (amd64) Sat, 15 Jul 2023 16:07:40 + |
+==+

Package: python-clickhouse-driver
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: full

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-2168482a-634b-4d8e-b5d4-42b1136edf8b'
 with '<>'
I: NOTICE: Log filtering will replace 
'build/python-clickhouse-driver-QFihkK/resolver-njOJ3X' with '<>'

+--+
| Update chroot|
+--+

Hit:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

+--+
| Fetch source files   |
+--+


Check APT
-

Checking available source versions...

Download source files with APT
--

Reading package lists...
NOTICE: 'python-clickhouse-driver' packaging is maintained in the 'Git' version 
control system at:
https://salsa.debian.org/debian/python-clickhouse-driver.git
Please use:
git clone https://salsa.debian.org/debian/python-clickhouse-driver.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 297 kB of source archives.
Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main 
python-clickhouse-driver 0.2.5-1 (dsc) [2200 B]
Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main 
python-clickhouse-driver 0.2.5-1 (tar) [292 kB]
Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main 
python-clickhouse-driver 0.2.5-1 (diff) [3228 B]
Fetched 297 kB in 0s (4024 kB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 
'build/python-clickhouse-driver-QFihkK/python-clickhouse-driver-0.2.5' with 
'<>'
I: NOTICE: Log filtering will replace 'build/python-clickhouse-driver-QFihkK' 
with '<>'

+--+
| Install package build dependencies   |
+--+


Setup apt archive
-

Merged Build-Depends: debhelper-compat (= 13), dh-python, cython3, 
python3-all-dev, python3-setuptools, python3-sphinx, python3-tzlocal, 
build-essential, fakeroot
Filtered Build-Depends: debhelper-compat (= 13), dh-python, cython3, 
python3-all-dev, python3-setuptools, python3-sphinx, python3-tzlocal, 
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 [609 B]
Ign:3 copy:/<>/apt_archive ./ Release.gpg
Get:4 copy:/<>/apt_archive ./ Sources [707 B]
Get:5 copy:/<>/apt_archive ./ Packages [739 B]
Fetched 2055 B in 0s (0 B/s)
Reading package lists...
Reading package lists...

Install main build dependencies (apt-based resolver)
--

Bug#1041203: FTBFS: InvalidRequirement: Expected end or semicolon

[Adam Borowski]

Source: macs
Version: 2.2.7.1-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Hi!
I'm afraid your package fails to build, with:
pkg_resources.extern.packaging._tokenizer.ParserSyntaxError: Expected end or 
semicolon (after name and no valid version specifier)
numpy>=>=1.17

Full log attached.


Meow!
-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), 
(120, 'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-rc1-00036-gc493f11e457d (SMP w/64 CPU threads; PREEMPT)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
sbuild (Debian sbuild) 0.85.2 (11 March 2023) on valinor.angband.pl

+==+
| macs (amd64) Sat, 15 Jul 2023 15:59:52 + |
+==+

Package: macs
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary

I: NOTICE: Log filtering will replace 
'var/run/schroot/mount/unstable-amd64-sbuild-6c3ec2b5-ebd2-4821-9c2c-b590aa40ebd9'
 with '<>'
I: NOTICE: Log filtering will replace 'build/macs-QwMUa0/resolver-kV6wWG' with 
'<>'

+--+
| Update chroot|
+--+

Get:1 http://apt-rosy.angband.pl:3142/debian unstable InRelease [199 kB]
Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main Sources.diff/Index 
[63.6 kB]
Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 
Packages.diff/Index [63.6 kB]
Get:4 http://apt-rosy.angband.pl:3142/debian unstable/main Sources 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [38.2 kB]
Get:4 http://apt-rosy.angband.pl:3142/debian unstable/main Sources 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [38.2 kB]
Get:5 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 Packages 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [14.4 kB]
Get:5 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 Packages 
T-2023-07-15-1409.27-F-2023-07-15-1409.27.pdiff [14.4 kB]
Fetched 379 kB in 1s (275 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  libtool
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 517 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main amd64 libtool all 
2.4.7-6 [517 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 517 kB in 0s (16.6 MB/s)
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14595 files and directories currently installed.)
Preparing to unpack .../libtool_2.4.7-6_all.deb ...
Unpacking libtool (2.4.7-6) over (2.4.7-5) ...
Setting up libtool (2.4.7-6) ...
Processing triggers for man-db (2.11.2-2) ...

+--+
| Fetch source files   |
+--+


Check APT
-

Checking available source versions...

Download source files with APT
--

Reading package lists...
NOTICE: 'macs' packaging is maintained in the 'Git' version control system at:
https://salsa.debian.org/med-team/macs.git
Please use:
git clone https://salsa.debian.org/med-team/macs.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 136 MB of source archives.
Get:1 http://apt-rosy.angband.pl:3142/debian unstable/main macs 2.2.7.1-6 (dsc) 
[2102 B]
Get:2 http://apt-rosy.angband.pl:3142/debian unstable/main macs 2.2.7.1-6 (tar) 
[135 MB]
Get:3 http://apt-rosy.angband.pl:3142/debian unstable/main macs 2.2.7.1-6 
(diff) [1268 kB]
Fetched 136 MB in 0s (336 MB/s)
Download complete and in download only mode
I: NOTICE: Log filtering will replace 'bui

Bug#1017619: nautilus-wipe not present in bookworm

[Fabio Follin]

Dear nautilus-wipe maintainers and uploaders,

I recently upgraded my system to debian 12 and I was surprised that
nautilus-wipe was not present in bookworm and not even in testing.

It is planned to add it back in testing from sid and maybe also add it
to bookworm-backports?

Thanks a lot for your work.
Best regards,
Fabio Follin

Bug#1041138: marked as done (memtailor FTBFS with googletest 1.13.0)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 15:38:05 +
with message-id 
and subject line Bug#1041138: fixed in memtailor 1.0~git20220104-2
has caused the Debian Bug report #1041138,
regarding memtailor FTBFS with googletest 1.13.0
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.)


-- 
1041138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041138
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: memtailor
Version: 1.0~git20220104-1
Severity: serious
Tags: ftbfs trixie sid

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/memtailor.html

...
In file included from /usr/src/gtest/include/gtest/gtest-message.h:57,
 from /usr/src/gtest/include/gtest/gtest-assertion-result.h:46,
 from /usr/src/gtest/include/gtest/gtest.h:64,
 from src/test/ArenaTest.cpp:19:
/usr/src/gtest/include/gtest/internal/gtest-port.h:270:2: error: #error C++ 
versions less than C++14 are not supported.
  270 | #error C++ versions less than C++14 are not supported.
  |  ^
...



This can be fixed by removing the -std=gnu++0x
from unittest_CXXFLAGS in Makefile.am
--- End Message ---
--- Begin Message ---
Source: memtailor
Source-Version: 1.0~git20220104-2
Done: Doug Torrance 

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

Debian distribution maintenance software
pp.
Doug Torrance  (supplier of updated memtailor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 15 Jul 2023 10:38:37 -0400
Source: memtailor
Built-For-Profiles: noudeb
Architecture: source
Version: 1.0~git20220104-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Math Team 
Changed-By: Doug Torrance 
Closes: 1041138
Changes:
 memtailor (1.0~git20220104-2) unstable; urgency=medium
 .
   * debian/control
 - Bump Standards-Version to 4.6.2.
   * debian/patches/c++17.patch
 - New patch; set C++ standard version to 17 for GoogleTest 1.13.0
   compatibility (Closes: #1041138).
Checksums-Sha1:
 7e51b3656cef70a502df87afff0d1b7d163dd8f1 2174 memtailor_1.0~git20220104-2.dsc
 dbb374f5c7f9ed1ff4052cc500f4cf4625320249 5100 
memtailor_1.0~git20220104-2.debian.tar.xz
 f23f90f1ca6b69437bdaea43c4b2e417e4167359 8694 
memtailor_1.0~git20220104-2_source.buildinfo
Checksums-Sha256:
 2ec81bd5e9b6e401e8a8bbc14731521d3f399e0adbb42a65fa73d5bbf0b221c8 2174 
memtailor_1.0~git20220104-2.dsc
 82cf3ae845bc7ac47473931ec1c99658eaf8fc9de42812a6b75fafd35a2dd40d 5100 
memtailor_1.0~git20220104-2.debian.tar.xz
 96d5488523fb9bbdfb60a1f6eae520f00b96fc8adc50383b872c4653a5ea3528 8694 
memtailor_1.0~git20220104-2_source.buildinfo
Files:
 9691b98a2fd548e020c1e6e8f1b8f7d4 2174 libs optional 
memtailor_1.0~git20220104-2.dsc
 cf6e1c6e7790718ce74bcbdf88991012 5100 libs optional 
memtailor_1.0~git20220104-2.debian.tar.xz
 8bdbe4c5cf3574f51342a9b759cb4587 8694 libs optional 
memtailor_1.0~git20220104-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJJBAEBCgAzFiEEupghwS4HiU+y5K0AkdxKd57FyRAFAmSyr5YVHGR0b3JyYW5j
ZUBkZWJpYW4ub3JnAAoJEJHcSneexckQXc8P/ig+qaH7vrxDVY3I1hGcGOaypJwZ
hIweb/aUepJixLpLq/vPhu4tdcvzy2CIpmM4l6/3Q165YzGUbYUd3gAzpBP6NF8h
3SKJIkzUejKLx5ZsbtI5YpUevqIODkTIK18/wLPygk8khF1qPohSsx8sTWAMkHKB
Q7zpzMAkGlfCdL+E/bSNx2cbX7WIyCZvKqkyWbe3c9A4P7QgB+fqxP2NZApcAyOi
s6jeRI48f8otR/mHAHOIgWz4FuV/7lnd/xq0ARkiIyc2XykBXsJXwFpHhYu0julx
aEFR+35L8+2pQp+LyO+k+F04U80xlddKXXRDDp13wu6YG97043LpL/qoJCaPXGuf
MVIiEXvBTSWMW1fJwe+iV4HfFuGBet+IqibDXU0rt3PkfjII2J1gTs+OadRMiDZV
7h3l6izo/yX1vYkBwVGpVVMJzXoGS2KMubilZmKCBslDOmwKwyCCbJ9tZ8VC3unR
uvbaJ7pUUDP8RyprBdMO6jXNpBU/gCvGPfj6jr/aQTpLZUId1ZroOMf4vNRFiX82
1K8t9qVgS4J0DrZTlFSg+qDVkRsYvMW+4HswlnRkKnxRRHKotol9GekS5W/JekRU
cVQDtE+fSZ4i2jWOes4xaCYH70wiA4e0L1jvsVfDFg5GM8u72DvSP3zpfi4gS4jb
uUMXP5idb18KDf3O
=OSKC
-END PGP SIGNATURE End Message ---

Bug#1037565: marked as done (4ti2: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 15:21:32 +
with message-id 
and subject line Bug#1037565: fixed in 4ti2 1.6.10+ds-1
has caused the Debian Bug report #1037565,
regarding 4ti2: ftbfs with GCC-13
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.)


-- 
1037565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:4ti2
Version: 1.6.9+ds-8
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/4ti2_1.6.9+ds-8_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/zsolve -I../../src 
-I../../src/4ti2 -Wdate-time -D_FORTIFY_SOURCE=2 -I../../../src/zsolve/.. 
-D__STDC_LIMIT_MACROS -Wall -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -c 
../../../src/zsolve/SignAPI.cpp  -fPIC -DPIC -o .libs/libzsolve_la-SignAPI.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/zsolve -I../../src 
-I../../src/4ti2 -Wdate-time -D_FORTIFY_SOURCE=2 -I../../../src/zsolve/.. 
-D__STDC_LIMIT_MACROS -Wall -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -c 
../../../src/zsolve/4ti2API.cpp  -fPIC -DPIC -o .libs/libzsolve_la-4ti2API.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/zsolve -I../../src 
-I../../src/4ti2 -Wdate-time -D_FORTIFY_SOURCE=2 -I../../../src/zsolve/.. 
-D__STDC_LIMIT_MACROS -Wall -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -c 
../../../src/zsolve/BitSet.cpp  -fPIC -DPIC -o .libs/libzsolve_la-BitSet.o
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/zsolve -I../../src 
-I../../src/4ti2 -Wdate-time -D_FORTIFY_SOURCE=2 -I../../../src/zsolve/.. 
-D__STDC_LIMIT_MACROS -Wall -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -c 
../../../src/zsolve/Timer.cpp -o libzsolve_la-Timer.o >/dev/null 2>&1
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../../../src/zsolve -I../../src 
-I../../src/4ti2 -Wdate-time -D_FORTIFY_SOURCE=2 -I../../../src/zsolve/.. 
-D__STDC_LIMIT_MACROS -Wall -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -std=c++0x -c 
../../../src/zsolve/BitSet.cpp -o libzsolve_la-BitSet.o >/dev/null 2>&1
In file included from ../../../src/zsolve/../zsolve/SignAPI.h:26,
 from ../../../src/zsolve/SignAPI.cpp:23:
../../../src/zsolve/../zsolve/VectorArrayAPI.hpp: In function ‘void 
_4ti2_zsolve_::convert(const T1&, T2&) [with T1 = long int; T2 = int]’:
../../../src/zsolve/../zsolve/VectorArrayAPI.hpp:79:14: error: ‘INT32_MIN’ was 
not declared in this scope; did you mean ‘INT_MIN’?
   79 | if (v1 < INT32_MIN || v2 > INT32_MAX) {
  |  ^
  |  INT_MIN
../../../src/zsolve/../zsolve/VectorArrayAPI.hpp:79:32: error: ‘INT32_MAX’ was 
not declared in this scope
   79 | if (v1 < INT32_MIN || v2 > INT32_MAX) {
  |^
../../../src/zsolve/../zsolve/VectorArrayAPI.hpp:31:1: note: ‘INT32_MAX’ is 
defined in header ‘’; did you forget to ‘#include ’?
   30 | #include 
  +++ |+#include 
   31 | 
make[5]: *** [Makefile:730: libzsolve_la-SignAPI.lo] Error 1
make[5]: *** Waiting for unfinished jobs
In file included from ../../../src/zsolve/main.cpp:37:
../../../src/zsolve/../zsolve/DefaultController.hpp: In member function

Bug#1040837: [Pkg-rust-maintainers] Bug#1040837: rust-log: breaks API without coordination

[Jonas Smedegaard]

Quoting Jonas Smedegaard (2023-07-15 09:55:04)
> Quoting Fabian Grünbichler (2023-07-12 19:53:08)
> > The feature in question is probably not a good candidate for packaging
> > though, given the lack of stability guarantees provided by upstream[0]:
> > 
> > > This module is unstable and breaking changes may be made at any time.
> > > See the tracking issue for more details.
> > 
> > The referenced tracking issue can be found here[1].
> > 
> > While the required crates (multiple ones from sval-rs/value-bag) are
> > being packaged (mostly done, pending a re-upload to NEW and review
> > there), I wonder whether enabling the feature was not a
> > mistake/premature in the first place.
> > 
> > I did a quick test with ratt with the attached diff applied, and except
> > for rust-sequoia-net (which fails for other reasons which are already
> > fixed in experimental and just need a re-upload of the version there to
> > unstable), building at least worked fine. I am not too familiar with
> > either async-std, nor the kv feature of log to say whether this approach
> > would be feasible - I'd be happy to hear your thoughts though! IMHO
> > keeping this unstable aspect out of the archive for the time being would
> > save us all from periodic breakage, with log itself (without the KV
> > feature) being rather widely used.
> 
> Makes sense.
> 
> I will go through those of the reverse dependencies that I am involved
> in maintaining, to see if th unstable feature can be avoided - and might
> reach out for help if I cannot figure it out on my own.

While I appreciate your suggested patch for rust-async-std, the main
obstacle to getting rid of the feature seems to not be rust-async-std
but instead rust-kv-log-macro which has 19 reverse dependencies:

aardvark-dns
rust-ahash
rust-ahash-0.7
rust-ashpd
rust-async-attributes
rust-async-std
rust-async-std-resolver
rust-async-tar
rust-erbium
rust-femme
rust-flume
rust-futures-timer
rust-oxilangtag
rust-oxiri
rust-rustls
rust-sequoia-net
rust-trust-dns-client
rust-trust-dns-resolver
rust-trust-dns-server

I am not happy to create Debian-specific patches to somehow replace
rust-kv-log-macro, and even if you were kind enough to initially create
such patches there is still the headache of maintaining them.

If the feature in rust-log really is considered too unstable for use in
Debian, then it seems to me that we need to convince upstream projects
to acknowledge that and themselves avoid the feature.


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/
 * Sponsorship: https://ko-fi.com/drjones

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

signature.asc
Description: signature

Processed: owner 1041075

[Debian Bug Tracking System]

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

> owner 1041075 !
Bug #1041075 [src:libphonenumber] libphonenumber FTBFS with googletest 1.13.0
Owner recorded as tony mancill .
> thanks
Stopping processing here.

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

Bug#1037717: marked as done (libbpp-core: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 14:41:17 +
with message-id 
and subject line Bug#1037717: fixed in libbpp-core 2.4.1-10
has caused the Debian Bug report #1037717,
regarding libbpp-core: ftbfs with GCC-13
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.)


-- 
1037717: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037717
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libbpp-core
Version: 2.4.1-9
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/libbpp-core_2.4.1-9_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
- 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
- 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
- 
(optional)_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE8_M_eraseEPSt13_Rb_tree_nodeIjE@Base
 2.4.1
- 
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
- 
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base
 2.4.1
- 
(optional)_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE7_M_copyILb0ENSB_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS5_ESG_PSt18_Rb_tree_node_baseRT0_@Base
 2.4.1
- 
(optional)_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 2.4.1
- 
_ZNSt8_Rb_treeIsSt4pairIKsNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIsESaIS8_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
- 
_ZNSt8_Rb_treeIsSt4pairIKsNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIsESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base
 2.4.1
- 
(optional)_ZNSt8_Rb_treeIsSt4pairIKsNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIsESaIS8_EE7_M_copyILb0ENSE_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS8_ESJ_PSt18_Rb_tree_node_baseRT0_@Base
 2.4.1
- 
(optional)_ZNSt8_Rb_treeIsSt4pairIKsNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIsESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base
 2.4.1
+#MISSING: 2.4.1-9# 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
+#MISSING: 2.4.1-9# 
_ZNSt8_Rb_treeIjSt4pairIKjjESt10_Select1stIS2_ESt4lessIjESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base
 2.4.1
+#MISSING: 2.4.1-9# 
(optional)_ZNSt8_Rb_treeIjjSt9_IdentityIjESt4lessIjESaIjEE8_M_eraseEPSt13_Rb_tree_nodeIjE@Base
 2.4.1
+#MISSING: 2.4.1-9# 
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base
 2.4.1
+#MISSING: 2.4.1-9# 
_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base
 2.4.1
+#MISSING: 2.4.1-9# 
(optional)_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE7_M_copyILb0ENSB_20_Reuse_or_alloc_nodeEEEPSt13_Rb_tree_nodeIS5_ESG_PSt18_Rb_tree_node_baseRT0_@Base
 2.4.1
+#MISSING: 2.4.1-9# 
(optional)_ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE8_M_eraseEPSt13_Rb_tree_nodeIS5_E@Base
 2.4.1
+#M

Processed: Re: ca-certificates-java: openjdk-17 update caused install regressions

[Debian Bug Tracking System]

Processing control commands:

> severity -1 critical
Bug #1039472 [ca-certificates-java] ca-certificates-java: openjdk-17 update 
caused install regressions
Severity set to 'critical' from 'serious'

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

Bug#1039472: ca-certificates-java: openjdk-17 update caused install regressions

[some]

Package: ca-certificates-java
Followup-For: Bug #1039472
Control: severity -1 critical

This makes unrelated software on the system break, making unrelated packages 
unusable without guidance on how to fix it.

Bug#1037740: marked as done (libsigc++-3.0: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 09:51:46 -0400
with message-id 

and subject line Re: libsigc++-3.0: ftbfs with GCC-13
has caused the Debian Bug report #1037740,
regarding libsigc++-3.0: ftbfs with GCC-13
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.)


-- 
1037740: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037740
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsigc++-3.0
Version: 3.4.0-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/libsigc++-3.0_3.4.0-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
file: see diff output below
dpkg-gensymbols: warning: debian/libsigc++-3.0-0/DEBIAN/symbols doesn't match 
completely debian/libsigc++-3.0-0.symbols
--- debian/libsigc++-3.0-0.symbols (libsigc++-3.0-0_3.4.0-1_amd64)
+++ dpkg-gensymbolsH2q9zb   2023-05-22 00:59:40.932688489 +
@@ -107,22 +107,29 @@
  _ZNK4sigc9trackable30remove_destroy_notify_callbackEPNS_10notifiableE@Base 
3.2.0
  (optional=templist|arch=armel 
riscv64)_ZNK9__gnu_cxx24__concurrence_lock_error4whatEv@Base 3.2.0
  (optional=templist|arch=armel 
riscv64)_ZNK9__gnu_cxx26__concurrence_unlock_error4whatEv@Base 3.2.0
- _ZNSt15__allocated_ptrISaISt10_List_nodeIN4sigc9slot_baseD1Ev@Base 3.2.0
- _ZNSt15__allocated_ptrISaISt10_List_nodeIN4sigc9slot_baseD2Ev@Base 3.2.0
+#MISSING: 3.4.0-1# 
_ZNSt15__allocated_ptrISaISt10_List_nodeIN4sigc9slot_baseD1Ev@Base 3.2.0
+#MISSING: 3.4.0-1# 
_ZNSt15__allocated_ptrISaISt10_List_nodeIN4sigc9slot_baseD2Ev@Base 3.2.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE1EE10_M_releaseEv@Base
 3.2.0
  (optional=templist|arch=amd64 
armhf)_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE10_M_releaseEv@Base 
3.2.0
+ 
_ZNSt16_Sp_counted_baseILN9__gnu_cxx12_Lock_policyE2EE24_M_release_last_use_coldEv@Base
 3.4.0-1
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE1EE10_M_destroyEv@Base
 3.2.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE1EE10_M_disposeEv@Base
 3.2.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE1EE14_M_get_deleterERKSt9type_info@Base
 3.2.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE1EED0Ev@Base
 3.2.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE1EED1Ev@Base
 3.2.0
  (optional=templinst|arch=armel 
riscv64)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE1EED2Ev@Base
 3.2.0
- (optional=templist|arch=amd64 
armhf)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE10_M_destroyEv@Base
 3.2.0
- (optional=templist|arch=amd64 
armhf)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE10_M_disposeEv@Base
 3.2.0
- (optional=templist|arch=amd64 
armhf)_ZNSt23_Sp_counted_ptr_inplaceIN4sigc8internal11signal_implESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE14_M_get_deleterERKSt9type_info@Base
 3.2.0
- (optional=templist|arch=amd64 
armhf)_ZNSt23_Sp_

Bug#1037702: marked as done (jellyfish: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 13:36:00 +
with message-id 
and subject line Bug#1037702: fixed in jellyfish 2.3.0-16
has caused the Debian Bug report #1037702,
regarding jellyfish: ftbfs with GCC-13
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.)


-- 
1037702: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037702
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:jellyfish
Version: 2.3.0-15
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13

[This bug is targeted to the upcoming trixie release]

Please keep this issue open in the bug tracker for the package it
was filed for.  If a fix in another package is required, please
file a bug for the other package (or clone), and add a block in this
package. Please keep the issue open until the package can be built in
a follow-up test rebuild.

The package fails to build in a test rebuild on at least amd64 with
gcc-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.

The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/jellyfish_2.3.0-15_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 13, either set CC=gcc-13 CXX=g++-13 explicitly,
or install the gcc, g++, gfortran, ... packages from experimental.

  apt-get -t=experimental install g++ 

Common build failures are new warnings resulting in build failures with
-Werror turned on, or new/dropped symbols in Debian symbols files.
For other C/C++ related build failures see the porting guide at
http://gcc.gnu.org/gcc-13/porting_to.html

[...]
# SKIP:  2
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

.. contents:: :depth: 2

SKIP: tests/big
===

Skip big test
SKIP tests/big.sh (exit status: 77)

SKIP: tests/swig_ruby
=

SKIP tests/swig_ruby.sh (exit status: 77)

FAIL: tests/swig_perl
=

Test test_mer_file.t
ok 1 - require jellyfish;
ok 2 - Histogram
ok 3 - Dump
ok 4 - Query identical to read
1..4
Test test_hash_counter.t
ok 1 - require jellyfish;
ok 2 - mer_dna k
ok 3 - Hash size
ok 4 - Hash value length
not ok 5 - Adding to new mer
#   Failed test 'Adding to new mer'
#   at /<>/swig/perl5/t/test_hash_counter.t line 31.
not ok 6 - Adding mer to hash
#   Failed test 'Adding mer to hash'
#   at /<>/swig/perl5/t/test_hash_counter.t line 48.
1..6
# Looks like you failed 2 tests of 6.
FAIL tests/swig_perl.sh (exit status: 2)


Testsuite summary for jellyfish 2.3.0

# TOTAL: 15
# PASS:  12
# SKIP:  2
# XFAIL: 0
# FAIL:  1
# XPASS: 0
# ERROR: 0

See ./test-suite.log
Please report to gmarc...@umd.edu

make[5]: *** [Makefile:2348: test-suite.log] Error 1
make[5]: Leaving directory '/<>'
make[4]: *** [Makefile:2456: check-TESTS] Error 2
make[4]: Leaving directory '/<>'
make[3]: *** [Makefile:2661: check-am] Error 2
make[3]: Leaving directory '/<>'
make[2]: *** [Makefile:2663: check] Error 2
make[2]: Leaving directory '/<>'
dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 
returned exit code 2
make[1]: *** [debian/rules:103: override_dh_auto_test] Error 25
make[1]: Leaving directory '/<>'
make: *** [debian/rules:22: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: jellyfish
Source-Version: 2.3.0-16
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated jellyfish 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, 15 Jul 2023 15:11:33 +0200
Source: jellyfish
Arc

Bug#1000133: marked as done (kannel: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 13:36:12 +
with message-id 
and subject line Bug#1000133: fixed in kannel 1.4.5-13
has caused the Debian Bug report #1000133,
regarding kannel: depends on obsolete pcre3 library
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.)


-- 
1000133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000133
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kannel
Severity: important
User: matthew-pcre...@debian.org
Usertags: obsolete-pcre3

Dear maintainer,

Your package still depends on the old, obsolete PCRE3[0] libraries
(i.e. libpcre3-dev). This has been end of life for a while now, and
upstream do not intend to fix any further bugs in it. Accordingly, I
would like to remove the pcre3 libraries from Debian, preferably in
time for the release of Bookworm.

The newer PCRE2 library was first released in 2015, and has been in
Debian since stretch. Upstream's documentation for PCRE2 is available
here: https://pcre.org/current/doc/html/

Many large projects that use PCRE have made the switch now (e.g. git,
php); it does involve some work, but we are now at the stage where
PCRE3 should not be used, particularly if it might ever be exposed to
untrusted input.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00176.html

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: kannel
Source-Version: 1.4.5-13
Done: Chris Hofstaedtler 

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

Debian distribution maintenance software
pp.
Chris Hofstaedtler  (supplier of updated kannel 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, 15 Jul 2023 14:43:40 +0200
Source: kannel
Architecture: source
Version: 1.4.5-13
Distribution: unstable
Urgency: medium
Maintainer: Chris Hofstaedtler 
Changed-By: Chris Hofstaedtler 
Closes: 1000133
Changes:
 kannel (1.4.5-13) unstable; urgency=medium
 .
   * Disable PCRE support, as PCRE3 will go away from Debian (Closes: #1000133)
Checksums-Sha1:
 89e70b6bfe5c31aa9df5182afc0e77457d07d086 2252 kannel_1.4.5-13.dsc
 d35ec88c2d587f4803bf5c9350b1248f6f7c2072 27356 kannel_1.4.5-13.debian.tar.xz
 142aae2f540035373bc42b0ee26c18448bb88c7c 12087 kannel_1.4.5-13_arm64.buildinfo
Checksums-Sha256:
 001ab5d5e8bc35b259a828239c5d621151c2cf799c1f31addd3b33db7c25c166 2252 
kannel_1.4.5-13.dsc
 a416cb0b9b675dacb25442cfaac456c956408da3dfdf4a69c5fc6ff5d5db2853 27356 
kannel_1.4.5-13.debian.tar.xz
 bcd78bfc0452224ab2238d5109dfbf7b2fea21056fc7e7365263a07e990c8c12 12087 
kannel_1.4.5-13_arm64.buildinfo
Files:
 32c9c368281c7d50636341306b414cde 2252 net optional kannel_1.4.5-13.dsc
 c27d061759548e9cc0253c900c847490 27356 net optional 
kannel_1.4.5-13.debian.tar.xz
 db9f28ef3be3f829b1fe680580c2a05c 12087 net optional 
kannel_1.4.5-13_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmSylzsACgkQXBPW25MF
LgPk9A//X7qf3dNpTzewBdkQj4+mzjM/httQk4pJszcZ91JBnAr/PykS2yUtzolb
iBLZg0p6MTt3Sa0akleicsff3VxKX74jm674XcVs83L+iuR6L556CB2DZFJXzhHi
bBHy/mdRDPjhGN+54luJY2UKqBeyvB1Yvr74S+gEHX/GLFxtNedrqDPuET4gOosB
YrkKlU9ygefYcLkyld5udttqIXSAcgWTC732oIgZhSZprAkA2Ow89WIqJ5TNDiV8
gijGJjTEWSJ4ZF8FCZzxfSsPzVx/WHN7k9aXRdTox3+uZqjTczqk0qPtj86Elpbk
1w1beJzOHvE5b/iuzWLsBkBtmyAoGIMPgxwJO9HQOVICLS/u/k3EKP3KCpPDyfYp
3A9FtNDInpI6owMYuF6IYQEzJWaaeG0i7npLIdJXUzKSM1CkSPfgM7U/4MYkPjUx
W2oT1M+bpqYzzKsJCEMnFhDxtenkeB1TvrO3SFB0ExLn58z/lo6NjYmvrHvL0SL8
0/LwB9NBbUijHEW4iDHyd/Y6WgUx6wbe+17KRBsFNz5vAXWN2hKmYRCWdzIUdUTR
uAo3aA2cVMsXsyQRxSLzWAq5csvFlr1haeEl8VHUie403Rj98wqwFoLIrJW3Vzpc
dFta83ZpArNce3jLDBdMTkgYf43F0aUn9j5OmqSWYt2EpfNBGY8=
=PqDb
-END PGP SIGNATURE End Message ---

Bug#1037765: maildir-utils: ftbfs with GCC-13

[Jeremy Sowden]

On 2023-07-15, at 12:19:47 +0100, Jeremy Sowden wrote:
> On 2023-07-15, at 07:29:54 -0300, David Bremner wrote:
> > Matthias Klose writes:
> > > Package: src:maildir-utils
> > > Version: 1.8.14-1
> > > Severity: normal
> > > Tags: sid trixie
> > > User: debian-...@lists.debian.org
> > > Usertags: ftbfs-gcc-13
> > >
> > > [This bug is targeted to the upcoming trixie release]
> > >
> > > Please keep this issue open in the bug tracker for the package it
> > > was filed for.  If a fix in another package is required, please
> > > file a bug for the other package (or clone), and add a block in
> > > this package. Please keep the issue open until the package can be
> > > built in a follow-up test rebuild.
> > 
> > I suspect we should probably move to a new upstream version rather
> > than adding yet another patch.
> 
> I did start looking at what would be involved and the new upstream
> version 1.10 has removed the deprecated autootools-based
> [build-system] which is used in the 1.8 package, so I decided to leave
> alone. :)
> 
> > However, if for some reason we want to stay with 1.8.14, it looks
> > like this specific issue is fixed by upstream commit
> > 
> >ce9446465260bd108bcf554cf503f72304f4276b
> 
> The diff in that commit is:
> 
>   diff --git a/lib/utils/mu-error.hh b/lib/utils/mu-error.hh
>   index 55a8002c71e2..6472ce83b4d4 100644
>   --- a/lib/utils/mu-error.hh
>   +++ b/lib/utils/mu-error.hh
>   @@ -22,6 +22,7 @@
>
>#include 
>#include 
>   +#include 
>
>#include "mu-utils-format.hh"
>#include 
>   
> which is all that is needed to fix the FTBFS.
> 
> > I attach a version with conflicts resolved (although I don't know the
> > codebase well enough to say if my resolution is correct). With that
> > patch the code builds, but the build still fails with mu4e.info and
> > mu4e-guile.info not being installed.
> > 
> > dh_missing: warning: usr/share/info/mu-guile.info exists in debian/tmp 
> > but is not installed to anywhere 
> > dh_missing: warning: usr/share/info/mu4e.info exists in debian/tmp but 
> > is not installed to anywhere 
> > dh_missing: error: missing files, aborting
> > The following debhelper tools have reported what they installed 
> > (with files per package)
> >  * dh_elpa: maildir-utils (0), mu4e (25)
> >  * dh_install: maildir-utils (6), mu4e (0)
> >  * dh_installdocs: maildir-utils (3), mu4e (0)
> >  * dh_installman: maildir-utils (0), mu4e (0)
> 
> The source package in the archive contains a couple of files which are
> missing from the Salsa repo:
> 
>   [azazel@ulthar:/space/azazel/tmp/maildir-utils-1.8.14] $ cat 
> debian/maildir-utils.info 
>   usr/share/info/mu-*
>   [azazel@ulthar:/space/azazel/tmp/maildir-utils-1.8.14] $ cat 
> debian/mu4e.info 
>   usr/share/info/mu4e*
> 
> I'll create a PR to add a patch and the missing .info files.

https://salsa.debian.org/emacsen-team/maildir-utils/-/merge_requests/2

J.


signature.asc
Description: PGP signature

Bug#1039621: marked as done (libngs-jni: Installs shared object in wrong directory)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 13:02:08 +
with message-id 
and subject line Bug#1039621: fixed in sra-sdk 3.0.3+dfsg-6~deb12u1
has caused the Debian Bug report #1039621,
regarding libngs-jni: Installs shared object in wrong directory
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.)


-- 
1039621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libngs-jni
Version: 3.0.3+dfsg-5
Severity: serious

Hi

This package installs the shared object in the following _literal_
pathname:

  /usr/lib/$(DEB_HOST_MULTIARCH)/jni/libncbi-ngs.so

Where the variable has not been expanded and appears as is. So the
shared object will not be found.

Thanks,
Guillem
--- End Message ---
--- Begin Message ---
Source: sra-sdk
Source-Version: 3.0.3+dfsg-6~deb12u1
Done: Aaron M. Ucko 

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

Debian distribution maintenance software
pp.
Aaron M. Ucko  (supplier of updated sra-sdk 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: Thu, 13 Jul 2023 23:08:59 -0400
Source: sra-sdk
Architecture: source
Version: 3.0.3+dfsg-6~deb12u1
Distribution: bookworm
Urgency: high
Maintainer: Debian Med Packaging Team 

Changed-By: Aaron M. Ucko 
Closes: 1039621
Changes:
 sra-sdk (3.0.3+dfsg-6~deb12u1) bookworm; urgency=medium
 .
   * Reupload to bookworm (stable).
 .
 sra-sdk (3.0.3+dfsg-6) unstable; urgency=high
 .
   * debian/rules: Expand $(DEB_HOST_MULTIARCH) in libngs-java.links.in.
 (Closes: #1039621.)
Checksums-Sha1:
 4a12dc87eae8a32bf94a45e65f4f9de5bd0050b8 2921 sra-sdk_3.0.3+dfsg-6~deb12u1.dsc
 1648299c151b6812936f2d4b5d7421a00a898dae 3785284 
sra-sdk_3.0.3+dfsg-6~deb12u1.debian.tar.xz
 c873fd8bb052f62500ed22d5fd6931648d478917 16981 
sra-sdk_3.0.3+dfsg-6~deb12u1_source.buildinfo
Checksums-Sha256:
 fb57725beb4fa444c6db2389ea123419d31f3320a5deffaf35bb6c2c4de8 2921 
sra-sdk_3.0.3+dfsg-6~deb12u1.dsc
 15a9824a6dfe5c2e1cd64465d31aa98eb2fe996d1aa818f51bf281b23563 3785284 
sra-sdk_3.0.3+dfsg-6~deb12u1.debian.tar.xz
 a57dc357c2f7192796bd6adb727a91057a430290ba656c65d20b29075aeb60e2 16981 
sra-sdk_3.0.3+dfsg-6~deb12u1_source.buildinfo
Files:
 8bacc1a95135081cd4f7a6c84d367409 2921 science optional 
sra-sdk_3.0.3+dfsg-6~deb12u1.dsc
 3177d4e136c6cc091c0fbc7915f79994 3785284 science optional 
sra-sdk_3.0.3+dfsg-6~deb12u1.debian.tar.xz
 9488ebf8d7f9af033f9bb234ed4c61da 16981 science optional 
sra-sdk_3.0.3+dfsg-6~deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfDq5z9IwvTDdAJxZHnCRsfFKZKIFAmSxwUAACgkQHnCRsfFK
ZKKsgw//aISERqQbuqP3ZjCyk+hGA/3ORFMnEHwcQhvJyZEgf0hDP+jN9+tWhSj2
kzonsJwbxMLfIINFqXIa8EhBr6vBteQQAAC9uVdoHXGOCQ6sZ+0jgW9Yh1uUfT4S
QHfmnSpdj+g/Ube38HT68cpY88sTPUO9RPEAcUtXU67H5xdYIdQKGdr+rz0M1Z0g
H5vm1ajBOUs8547nWDLXBauYFx3z5QEUl7Y4+RsgOwH9D7R6MZ/tNQy7kT4NMRjp
K22ST7ThA9NdVlIsIC5wBCyc20Mqe3alrfK8QHS3jnCZxohp1zkqAs4+/RvMsuoV
r4BXWhoEnaSn6c82D4KDsaA/7+DylVGznw+mK+pIrJzcFtIkaMC0wvOHBLE0WgOm
quwHxj4fFvpml56PjDXV3ZhNMcin+moM/CZWQLgECqvg0MWOypiL7V3fBdVTqzoC
nODvo4+PR/IoaHT5gZQhoD2Lv5eZ4OJg+nC7w7t6WZf7caZ8STtpy3xX9oiI9Oj8
N0bVCG6R+eUlRqNM3KCrc5tl4TDcT3ZKxzr3WDRRmfBYm/22d9B5TBDpmJPSmPXt
8sRuyF+Unf5xmqaY0BCYHyMqFoffa9hlajelmW+JQqIq1xnFEe/wb2YdJx08HPx3
ueBQcNX2+psXLR8FSTOYVJ6j2Y0d7i3fcxq3b4x9eqzul59oWGs=
=pQw0
-END PGP SIGNATURE End Message ---

Bug#1037226:

[Tobias Frost]

Control: tags -1 pending
Conrtol: block -1 by 1040799

This bug has been fixed in unstable with the binNMU 1.0.3-1b3, see #1040858

It is also scheduled to be fixed in the next stable-point-release, see #1040799


-- 
tobi

Processed: Re: Bug#1037226:

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1037226 [libnginx-mod-http-modsecurity] libnginx-mod-http-modsecurity 
fails to start after update libmodsecurity3 to v3.0.9
Added tag(s) pending.

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

Processed: notfixed 1037226 in 1.0.3-1

[Debian Bug Tracking System]

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

> notfixed 1037226 1.0.3-1
Bug #1037226 [libnginx-mod-http-modsecurity] libnginx-mod-http-modsecurity 
fails to start after update libmodsecurity3 to v3.0.9
No longer marked as fixed in versions libnginx-mod-http-modsecurity/1.0.3-1.
> thanks
Stopping processing here.

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

Bug#1037917: marked as done (gnutls28: leaves processes running after build: gnutls-serv, openssl s_server)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 12:36:31 +
with message-id 
and subject line Bug#1037917: fixed in gnutls28 3.8.0+git20230713-1
has caused the Debian Bug report #1037917,
regarding gnutls28: leaves processes running after build: gnutls-serv, openssl 
s_server
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.)


-- 
1037917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnutls28
Version: 3.8.0+git20230529-1
Severity: serious

Hi,

after building gnutls28/experimental with pbuilder, there are a lot of
gnutls-serv and a few openssl s_server processes running, preventing
pbuilder to cleanup the chroot.


Andreas
--- End Message ---
--- Begin Message ---
Source: gnutls28
Source-Version: 3.8.0+git20230713-1
Done: Andreas Metzler 

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

Debian distribution maintenance software
pp.
Andreas Metzler  (supplier of updated gnutls28 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 15 Jul 2023 13:40:58 +0200
Source: gnutls28
Architecture: source
Version: 3.8.0+git20230713-1
Distribution: experimental
Urgency: medium
Maintainer: Debian GnuTLS Maintainers 
Changed-By: Andreas Metzler 
Closes: 1037917
Changes:
 gnutls28 (3.8.0+git20230713-1) experimental; urgency=medium
 .
   * New upstream git snapshot c4023afde53241aedbb94108aa10fda9bd05ee82.
 + Update copyright file.
 + Switch back to datefudge. faketime using fork() instead of exex() breaks
   the cleanup scripting in the testsuite. This together with upstream
   changes Closes: #1037917
   Most tests do not rely on datefudge/faketime anymore but use -attime so
   we would still have meaningful testsuite coverage without datefudge.
 + Update autopkgtest for new upstream.
Checksums-Sha1: 
 cdc281fca7770fa17eb964aac9804c10f903eb46 3067 gnutls28_3.8.0+git20230713-1.dsc
 b0f6d93ec1348bab31ad4f445c002dcaa836c847 6445104 
gnutls28_3.8.0+git20230713.orig.tar.xz
 6a2d320aefce83a41bd7f9342d5c9176dcad0c45 67752 
gnutls28_3.8.0+git20230713-1.debian.tar.xz
Checksums-Sha256: 
 bae6d58622d16d8f66c5357efa9df53e7079b3821b9829402d92d036e0ddcfe1 3067 
gnutls28_3.8.0+git20230713-1.dsc
 157cfa0b1b44cb2189906045a097ee802622e4598611ba68d46a97d82ab2cc33 6445104 
gnutls28_3.8.0+git20230713.orig.tar.xz
 32cbf36da6228034a586e7b2ed0777fd0afcf2c7499ffaff717230226cb57a36 67752 
gnutls28_3.8.0+git20230713-1.debian.tar.xz
Files: 
 6ea92c28be727203dde98d097a8cdc55 3067 libs optional 
gnutls28_3.8.0+git20230713-1.dsc
 9dae51c0adf95e4530031052aa646967 6445104 libs optional 
gnutls28_3.8.0+git20230713.orig.tar.xz
 98401eeeb80dfad41aef859719e63a17 67752 libs optional 
gnutls28_3.8.0+git20230713-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmSyi8oACgkQpU8BhUOC
FIT1mhAAgAYz1rdX8r5wnLstU2gzoV+jpWGhWt74aQ1hVULNxVZOkGEoGKDsVTK+
/hlmQbqkDXEFiGW9Qq7ltkcPkSvHGw564YOLMMSDbCl94o4EBcLyZdbywANP6T3X
56iKL4qvSWYwI2hs/zYd/0aKthzRt59h0RTGZ8JsqVngP+ojIZRsVQ34lOx7aZdH
kIm/gzM+fXPPLp6CAXPOo3KetONxFw4JZ3l/v02Hvdd26CZkYItBTEAVjHyGhhAW
ajPuco9JknCKOYXVyGVm83EcLYTbNvLacXfcpwHAluVoYDCIZA7W1apVVvKacD20
yvjLRnW17QDfpKYmaHH+5At5+Kd2s1uToS4pOdKkhQk/G9jLS2gfsb4Zt2sNMPJ6
VkZvZvhTT4g0oahH51GajYItPVENSGD8hxmoJB5YezugnbqZD4O0MIz2/w5pzQGi
ckO6AD233rcrUkGiysAjzMZuC6zEQEoWKckTC8xRqVyFUE/QtgdiSJFhDxWrLgiI
CEo/E9ruzN/AuvjG8RBJyUd4HLWsfxztBppQV3SDa/uLeRzHC0QEx37biDie3DwJ
dPZBae6dE//jSqoXeg8uM2dIcwFS/ZNejxC/pKGVVoSfNibREPqYnf/KHqsZYD2s
l4dFkeSb6Cf8CUtHQWvnNr1PqW/6dyNB9sj674u6OFKLEBuRFSk=
=rfOQ
-END PGP SIGNATURE End Message ---

Bug#1000100: Would configuring with -DPERL_REGEX=OFF be an option?

[Adrian Bunk]

Would configuring with -DPERL_REGEX=OFF be an option,
or does that cost too much functionality?

cu
Adrian

Processed: tagging 1000074

[Debian Bug Tracking System]

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

> tags 174 + upstream
Bug #174 [src:gsmartcontrol] gsmartcontrol: depends on obsolete pcre3 
library
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Bug#1026635: marked as done (rust-packed-simd: FTBFS: dh_auto_test: error: /usr/share/cargo/bin/cargo build returned exit code 101)

[Debian Bug Tracking System]

Your message dated Sat, 15 Jul 2023 12:08:41 +
with message-id 
and subject line Bug#1026635: fixed in rust-packed-simd 0.3.8-1
has caused the Debian Bug report #1026635,
regarding rust-packed-simd: FTBFS: dh_auto_test: error: 
/usr/share/cargo/bin/cargo build returned exit code 101
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.)


-- 
1026635: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026635
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-packed-simd
Version: 0.3.3-8
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221220 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> export RUSTC_BOOTSTRAP=1; \
> dh_auto_test
> debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
> debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu, 
> x86_64-linux-gnu
> debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1', 
> '/usr/bin/cargo', '-Zavoid-dev-deps', 'build', '--verbose', '--verbose', 
> '-j8', '--target', 'x86_64-unknown-linux-gnu'],) {}
>Compiling packed_simd v0.3.3 (/<>)
>Compiling cfg-if v0.1.10
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=build_script_build 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Gonzalo Brito Gadeschi 
> ' CARGO_PKG_DESCRIPTION='Portable Packed SIMD vectors' 
> CARGO_PKG_HOMEPAGE='https://github.com/rust-lang-nursery/packed_simd' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=packed_simd 
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang-nursery/packed_simd' 
> CARGO_PKG_VERSION=0.3.3 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=3 
> CARGO_PKG_VERSION_PATCH=3 CARGO_PKG_VERSION_PRE='' CARGO_PRIMARY_PACKAGE=1 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name build_script_build --edition=2018 build.rs --error-format=json 
> --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type bin 
> --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --cfg 
> 'feature="default"' -C metadata=5ccf70716b37ffcc -C 
> extra-filename=-5ccf70716b37ffcc --out-dir 
> /<>/target/debug/build/packed_simd-5ccf70716b37ffcc -C 
> incremental=/<>/target/debug/incremental -L 
> dependency=/<>/target/debug/deps`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=cfg_if 
> CARGO_MANIFEST_DIR=/<>/debian/cargo_registry/cfg-if-0.1.10 
> CARGO_PKG_AUTHORS='Alex Crichton ' 
> CARGO_PKG_DESCRIPTION='A macro to ergonomically define an item depending on a 
> large number of #[cfg]
> parameters. Structured like an if-else chain, the first matching branch is the
> item that gets emitted.
> ' CARGO_PKG_HOMEPAGE='https://github.com/alexcrichton/cfg-if' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=cfg-if 
> CARGO_PKG_REPOSITORY='https://github.com/alexcrichton/cfg-if' 
> CARGO_PKG_VERSION=0.1.10 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=1 
> CARGO_PKG_VERSION_PATCH=10 CARGO_PKG_VERSION_PRE='' 
> LD_LIBRARY_PATH='/<>/target/debug/deps:/usr/lib' rustc 
> --crate-name cfg_if --edition=2018 
> /<>/debian/cargo_registry/cfg-if-0.1.10/src/lib.rs 
> --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat 
> --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C 
> debuginfo=2 -C metadata=ec7ab5d579c0e83f -C extra-filename=-ec7ab5d579c0e83f 
> --out-dir /<>/target/x86_64-unknown-linux-gnu/debug/deps 
> --target x86_64-unknown-linux-gnu -L 
> dependency=/<>/target/x86_64-unknown-linux-gnu/debug/deps -L 
> dependency=/<>/target/debug/deps --cap-lints warn -C debuginfo=2 
> --cap-lints warn -C linker=x86_64-linux-gnu-gcc -C link-arg=-Wl,-z,relro 
> --remap-path-prefix 
> /<>=/usr/share/cargo/registry/packed-simd-0.3.3 
> --remap-path-prefix 
> /<>/debian/cargo_registry=/usr/share/cargo/registry`
>  Running 
> `/<>/target/debug/build/packed_simd-5ccf70716b37ffcc/build-script-build`
>  Running `CARGO=/usr/bin/cargo CARGO_CRATE_NAME=packed_simd 
> CARGO_MANIFEST_DIR=/<> CARGO_PKG_AUTHORS='Gonzalo Brito Gadeschi 
> ' CARGO_PKG_DESCRIPTION='Portable Packed SIMD vectors' 
> CARGO_PKG_HOMEPAGE='https://github.com/rust-lang-nursery/packed_simd' 
> CARGO_PKG_LICENSE=MIT/Apache-2.0 CARGO_PKG_LICENSE_FILE='' 
> CARGO_PKG_NAME=packed_simd 
> CARGO_PKG_REPOSITORY='https://github.com/rust-lang-nursery/packed_simd' 
> CARGO_PKG_VERSION=0.3.3 CARGO_PKG_VERSION_MAJOR=0 CARGO_PKG_VERSION_MINOR=3 
> CARGO_PKG_VERSIO