Processed: src:chafa: fails to migrate to testing for too long: FTBFS on i386

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.14.1-1
Bug #1077933 [src:chafa] src:chafa: fails to migrate to testing for too long: 
FTBFS on i386
Marked as fixed in versions chafa/1.14.1-1.
Bug #1077933 [src:chafa] src:chafa: fails to migrate to testing for too long: 
FTBFS on i386
Marked Bug as done

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

Bug#1077933: src:chafa: fails to migrate to testing for too long: FTBFS on i386

[Paul Gevers]

Source: chafa
Version: 1.14.0-1.1
Severity: serious
Control: close -1 1.14.1-1
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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=chafa



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1077932: src:python-mpv: fails to migrate to testing for too long: FTBFS

[Paul Gevers]

Source: python-mpv
Version: 1.0.6-1
Severity: serious
Control: close -1 1.0.7-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1076971

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-mpv has been trying to migrate for 
31 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build as reported in bug 1076971.


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



OpenPGP_signature.asc
Description: OpenPGP digital signature

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

[Debian Bug Tracking System]

Processing control commands:

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

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

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

[Debian Bug Tracking System]

Processing control commands:

> close -1 3.1.0-1
Bug #1077931 [src:colorcet] src:colorcet: fails to migrate to testing for too 
long: autopkgtest regression
Marked as fixed in versions colorcet/3.1.0-1.
Bug #1077931 [src:colorcet] src:colorcet: fails to migrate to testing for too 
long: autopkgtest regression
Marked Bug as done

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

Bug#1077931: src:colorcet: fails to migrate to testing for too long: autopkgtest regression

[Paul Gevers]

Source: colorcet
Version: 3.0.1-1
Severity: serious
Control: close -1 3.1.0-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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=colorcet



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1077930: src:guile-3.0: fails to migrate to testing for too long: FTBFS on armel, armhf, i386, ppc64el and mips64el

[Paul Gevers]

Source: guile-3.0
Version: 3.0.9-1
Severity: serious
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:guile-3.0 has been trying to migrate for 
35 days [2]. Hence, I am filing this bug. The version in unstable failed 
to build on armel, armhf, i386, ppc64el and mips64el.


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


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


Normally I would closed this bug with the version in unstable, so if 
that version or a later version migrates, this bug will no longer affect 
testing. However because this is also reporting the FTBFS, I decided to 
not do that. I have tagged this bug to only affect sid and trixie, so it 
doesn't affect (old-)stable.


Paul

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



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: Bug#1073052 marked as pending in cryptsetup

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1073052 [src:cryptsetup] cryptsetup: autopkgtest cryptroot-lvm is flaky
Added tag(s) pending.

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

Bug#1073052: marked as pending in cryptsetup

[Guilhem Moulin]

Control: tag -1 pending

Hello,

Bug #1073052 in cryptsetup 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/cryptsetup-team/cryptsetup/-/commit/045c989002e6dc38e6900d977dc565b866d7339a


DEP-8: Mark cryptroot-* as flaky.

To be re-evaluated if/when the tests only run on environment where KVM
is available, see #1015966.

Closes: #1073052


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1073052

Processed: severity of 1018425 is serious

[Debian Bug Tracking System]

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

> severity 1018425 serious
Bug #1018425 [src:nrpe-ng] nrpe-ng: build-depends on python3-nose or uses it 
for autopkgtest
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1077929: praat: flaky autopkgtest on several architectures: test_Formant_slopes.praat times out

[Paul Gevers]

Source: praat
Version: 6.4.12+dfsg-3
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it 
showed up on the gcc-14 migration tracker. I noticed that it regularly 
fails on armel and armhf, but I've seen the same failure at least once 
on i386 too. See link below. When the test passes, it immediately 
continues with output. When it times out, nothing in the log until 
autopkgtest aborts the test.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/p/praat/testing/i386/47876838/
https://ci.debian.net/packages/p/praat/testing/armel/49952727/

2701s ### executing test_Formant_slopes.praat:
2701s test_Formant_slopes.praat
10123s autopkgtest [17:56:28]: ERROR: timed out


OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: severity of 1018475 is serious

[Debian Bug Tracking System]

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

> severity 1018475 serious
Bug #1018475 [src:python-csa] python-csa: build-depends on python3-nose or uses 
it for autopkgtest
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1077928: ironseed: flaky autopkgtest on 32 arm: hits internal timeout

[Paul Gevers]

Source: ironseed
Version: 0.4.0-5
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package because it's 
currently blocking the migration of gcc-14. I noticed that it regularly 
fails on at least armel and armhf. Looking at the message in the log 
(see below) you may just want to increase the timeout.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/i/ironseed/testing/armel/49782805/

autopkgtest [06:17:14]: test savegames: [---
344s timeout: sending signal TERM to command ‘xvfb-run’
344s XIO:  fatal IO error 0 (Success) on X server ":99"
344s   after 53285 requests (53285 known processed) with 0 events 
remaining.
344s sha256sum: /home/debci/.local/share/ironseed/save1/CONTACTS.DTA: No 
such file or directory
344s sha256sum: /home/debci/.local/share/ironseed/save1/EVENTS.DTA: No 
such file or directory
344s sha256sum: /home/debci/.local/share/ironseed/save1/LOGS.DTA: No 
such file or directory
344s sha256sum: /home/debci/.local/share/ironseed/save1/PENDING.DTA: No 
such file or directory

344s sha256sum: WARNING: 4 listed files could not be read
344s /home/debci/.local/share/ironseed/save1/CONTACTS.DTA: FAILED open 
or read

344s /home/debci/.local/share/ironseed/save1/EVENTS.DTA: FAILED open or read
344s /home/debci/.local/share/ironseed/save1/LOGS.DTA: FAILED open or read
344s /home/debci/.local/share/ironseed/save1/PENDING.DTA: FAILED open or 
read

344s autopkgtest [06:22:15]: test savegames: ---]


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1077408: marked as done (sendmail: FTBFS: ./debian/./debian/conftest.c:37:(.text.startup+0xb): undefined reference to `__res_query')

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 16:52:50 +
with message-id 
and subject line Bug#1077408: fixed in sendmail 8.18.1-6
has caused the Debian Bug report #1077408,
regarding sendmail: FTBFS: ./debian/./debian/conftest.c:37:(.text.startup+0xb): 
undefined reference to `__res_query'
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.)


-- 
1077408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sendmail
Version: 8.18.1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240728 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /tmp/cc057AAq.o: in function `main':
> ./debian/./debian/conftest.c:37:(.text.startup+0xb): undefined reference to 
> `__res_query'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2024/07/28/sendmail_8.18.1-5_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: sendmail
Source-Version: 8.18.1-6
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated sendmail package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 04 Aug 2024 18:25:02 +0200
Source: sendmail
Architecture: source
Version: 8.18.1-6
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Andreas Beckmann 
Closes: 1077408
Changes:
 sendmail (8.18.1-6) unstable; urgency=medium
 .
   * QA upload.
   * Use fclose() not close() on FILE*.  (Closes: #1077408)
   * Update to Standards-Version: 4.7.0.
Checksums-Sha1:
 479d5831beecaec4f16464a4a1c1462aa2b1ec7f 2819 sendmail_8.18.1-6.dsc
 1785dea6f3b038e7173436198936dceacd3636d0 2401566 sendmail_8.18.1.orig.tar.gz
 c5ba4eb167305249cd22ed4101a0a07b395fd3fb 801 sendmail_8.18.1.orig.tar.gz.asc
 2f02466aa0162d572a096b6debf3b2bb6d759e25 248492 sendmail_8.18.1-6.debian.tar.xz
 64e232bce5eb3e5002cd0ec9de40f5ec93440a08 6436 
sendmail_8.18.1-6_source.buildinfo
Checksums-Sha256:
 e24096e5f8908e73899e63a37c5cd2ed53cd559974ecace66bddadc1b02fbda0 2819 
sendmail_8.18.1-6.dsc
 cbf1f309c38e4806f7cf3ead24260f17d1fe8fb63256d13edb3cdd1a098f0770 2401566 
sendmail_8.18.1.orig.tar.gz
 fbdca1ead34283521a3a1f3ee4169d595672d4e65845b2f70e7da67f7ed8e0ea 801 
sendmail_8.18.1.orig.tar.gz.asc
 17696746411ca98d2a5c1ac3ce43bb56b0667ab9d936ab772e73bb16e9ca14dc 248492 
sendmail_8.18.1-6.debian.tar.xz
 87dde76f59938f77de163059d7493d6911426a98246b0f25a874d5ac1a7486e3 6436 
sendmail_8.18.1-6_source.buildinfo
Files:
 fd6406347cef9b20a6f85415c78f2f44 2819 mail optional sendmail_8.18.1-6.dsc
 b6b332295b5779036d4c9246f96f673c 2401566 mail optional 
sendmail_8.18.1.orig.tar.gz
 0c1fad4cef3ad326a51f3458c6defb04 801 mail optional 
sendmail_8.18.1.orig.tar.gz.asc
 957652cf831a80014b53779e779c704e 248492 mail optional 
sendmail_8.18.1-6.debian.tar.xz
 dfc0fa52ca89ed93fc9e9b291cd6b3b4 6436 mail optional 
sendmail_8.18.1-6_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmavrGAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCLmHD/9nl+cJ3CsPHCuYv+w9mDwm/80c8YxqWG8b

Bug#1077924: FTBFS: src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:224:50: not enough arguments in call to runtime.AnnotateContext

[Reinhard Tartler]

Source: golang-github-backblaze-blazer
Version: 0.6.2-1
Severity: serious
Tags: upstream ftbfs
Justification: FTBFS
X-Debbugs-Cc: debian...@lists.debian.org

Your package currently FTBFS:

# github.com/Backblaze/blazer/internal/pyre/proto
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:195:50: not 
enough arguments in call to runtime.AnnotateContext
have ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request)
want ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request, 
string, 
..."github.com/grpc-ecosystem/grpc-gateway/runtime".AnnotateContextOption)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:207:79: 
cannot use resp (variable of type protoiface.MessageV1) as 
protoreflect.ProtoMessage value in argument to 
forward_PyreService_AuthorizeAccount_0: protoiface.MessageV1 does not implement 
protoreflect.ProtoMessage (missing method ProtoReflect)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:224:50: not 
enough arguments in call to runtime.AnnotateContext
have ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request)
want ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request, 
string, 
..."github.com/grpc-ecosystem/grpc-gateway/runtime".AnnotateContextOption)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:236:74: 
cannot use resp (variable of type protoiface.MessageV1) as 
protoreflect.ProtoMessage value in argument to 
forward_PyreService_ListBuckets_0: protoiface.MessageV1 does not implement 
protoreflect.ProtoMessage (missing method ProtoReflect)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:253:50: not 
enough arguments in call to runtime.AnnotateContext
have ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request)
want ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request, 
string, 
..."github.com/grpc-ecosystem/grpc-gateway/runtime".AnnotateContextOption)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:265:75: 
cannot use resp (variable of type protoiface.MessageV1) as 
protoreflect.ProtoMessage value in argument to 
forward_PyreService_CreateBucket_0: protoiface.MessageV1 does not implement 
protoreflect.ProtoMessage (missing method ProtoReflect)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:282:50: not 
enough arguments in call to runtime.AnnotateContext
have ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request)
want ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request, 
string, 
..."github.com/grpc-ecosystem/grpc-gateway/runtime".AnnotateContextOption)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:294:75: 
cannot use resp (variable of type protoiface.MessageV1) as 
protoreflect.ProtoMessage value in argument to 
forward_PyreService_DeleteBucket_0: protoiface.MessageV1 does not implement 
protoreflect.ProtoMessage (missing method ProtoReflect)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:311:50: not 
enough arguments in call to runtime.AnnotateContext
have ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request)
want ("context".Context, 
*"github.com/grpc-ecosystem/grpc-gateway/runtime".ServeMux, *http.Request, 
string, 
..."github.com/grpc-ecosystem/grpc-gateway/runtime".AnnotateContextOption)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:323:75: 
cannot use resp (variable of type protoiface.MessageV1) as 
protoreflect.ProtoMessage value in argument to 
forward_PyreService_GetUploadUrl_0: protoiface.MessageV1 does not implement 
protoreflect.ProtoMessage (missing method ProtoReflect)
src/github.com/Backblaze/blazer/internal/pyre/proto/pyre.pb.gw.go:323:75: too 
many errors
github.com/Backblaze/blazer/b2


This is likely caused by upgrading the grpc-gateway package v2.

Please work with upstream to get the package upgraded to versions of
grpc-gateway we currently have in Debian.

This upgrade was coordinated with the golang and release teams at
https://lists.debian.org/debian-release/2024/07/msg00188.html
and http://bugs.debian.org/1076109.

Thank you for your cooperation and assistance!

-rt


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

Kernel: Linux 6.9.12-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
sbuild (Debian sbuild) 0.85.10 (30 May 2024) on x1.int.tauware.de

Processed: emmet

[Debian Bug Tracking System]

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

> block 1077430 by 1061609
Bug #1077430 [src:python-emmet-core] python-emmet-core: FTBFS: E   ImportError: 
cannot import name 'datetime' from 'pydantic.datetime_parse' 
(/usr/lib/python3/dist-packages/pydantic/datetime_parse.py)
1077430 was not blocked by any bugs.
1077430 was not blocking any bugs.
Added blocking bug(s) of 1077430: 1061609
>
End of message, stopping processing here.

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

Bug#1077919: pynfft: binary-all FTBFS

[Adrian Bunk]

Source: pynfft
Version: 1.3.2-9
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=pynfft=all=1.3.2-9=1722779107=0

...
   dh_auto_test -i -O--buildsystem=pybuild
I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12_pynfft/build; 
python3.12 -m pytest 
= test session starts ==
platform linux -- Python 3.12.4, pytest-8.3.2, pluggy-1.5.0
rootdir: /<>
collected 0 items

 no tests ran in 0.01s =
E: pybuild pybuild:389: test: plugin distutils failed with: exit code=5: cd 
/<>/.pybuild/cpython3_3.12_pynfft/build; python3.12 -m pytest 
dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.12 
returned exit code 13
make: *** [debian/rules:9: binary-indep] Error 25

Processed: Re: Bug#1072278: scute: FTBFS against libassuan without libassuan-config

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1072278 [src:scute] scute: FTBFS against libassuan without libassuan-config
Severity set to 'serious' from 'important'

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

Processed: Re: Bug#1072277: kleopatra: Searches for libassuan with libassuan-config

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1072277 [src:kleopatra] kleopatra: Searches for libassuan with 
libassuan-config
Severity set to 'serious' from 'important'

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

Bug#1077525: marked as done (osc: FTBFS: PermissionError: [Errno 13] Permission denied: '/home/user42')

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 13:53:16 +
with message-id 
and subject line Bug#1077525: fixed in osc 1.7.0-5
has caused the Debian Bug report #1077525,
regarding osc: FTBFS: PermissionError: [Errno 13] Permission denied: 
'/home/user42'
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.)


-- 
1077525: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077525
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osc
Version: 1.7.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240728 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for d in .pybuild/*/build; do ln -sr doc $d; done
> make[1]: Leaving directory '/<>'
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:311: cd /<>/.pybuild/cpython3_3.12/build; 
> python3.12 -m unittest discover -v 
> test_amp (tests.test__private_api.TestXmlEscape.test_amp) ... ok
> test_apos (tests.test__private_api.TestXmlEscape.test_apos) ... ok
> test_gt (tests.test__private_api.TestXmlEscape.test_gt) ... ok
> test_lt (tests.test__private_api.TestXmlEscape.test_lt) ... ok
> test_quot (tests.test__private_api.TestXmlEscape.test_quot) ... ok
> test_load (tests.test__private_package.TestApiPackage.test_load) ... ok
> test_load (tests.test__private_package.TestLocalPackage.test_load) ... ok
> test_eq (tests.test__private_package.TestPackageBase.test_eq) ... ok
> test_hash (tests.test__private_package.TestPackageBase.test_hash) ... ok
> test_lt (tests.test__private_package.TestPackageBase.test_lt) ... ok
> test_repr (tests.test__private_package.TestPackageBase.test_repr) ... ok
> test_str (tests.test__private_package.TestPackageBase.test_str) ... ok
> testAddNonExistentFile 
> (tests.test_addfiles.TestAddFiles.testAddNonExistentFile)
> add a non existent file ... ok
> testAddUnversionedFileTwice 
> (tests.test_addfiles.TestAddFiles.testAddUnversionedFileTwice)
> add the same file twice ... ok
> testAddVersionedFile (tests.test_addfiles.TestAddFiles.testAddVersionedFile)
> add a versioned file ... ok
> testReplace (tests.test_addfiles.TestAddFiles.testReplace)
> replace a deleted file ('foo') ... ok
> testSimpleAdd (tests.test_addfiles.TestAddFiles.testSimpleAdd)
> add one file ('toadd1') to the wc ... ok
> testSimpleMultipleAdd (tests.test_addfiles.TestAddFiles.testSimpleMultipleAdd)
> add multiple files ('toadd1', 'toadd2') to the wc ... ok
> test_glob (tests.test_build.TestTrustedProjects.test_glob) ... ok
> test_name (tests.test_build.TestTrustedProjects.test_name) ... ok
> test_default_apiurl 
> (tests.test_commandline.TestCommandClasses.test_default_apiurl) ... ok
> test_intermixing (tests.test_commandline.TestCommandClasses.test_intermixing) 
> ... ok
> test_invalid_parent 
> (tests.test_commandline.TestCommandClasses.test_invalid_parent) ... Failed to 
> load command class 'test.osc.commands.Child' because it references parent 
> 'test.osc.commands.DoesNotExist' that doesn't exist
> ok
> test_load_command 
> (tests.test_commandline.TestCommandClasses.test_load_command) ... ok
> test_load_commands 
> (tests.test_commandline.TestCommandClasses.test_load_commands) ... ok
> test_load_twice (tests.test_commandline.TestCommandClasses.test_load_twice) 
> ... ok
> test_parent (tests.test_commandline.TestCommandClasses.test_parent) ... ok
> test_unknown_options 
> (tests.test_commandline.TestCommandClasses.test_unknown_options) ... usage: 
> osc-test [global opts]  [--help] [opts] [args]
> osc-test: error: unrecognized arguments: --unknown-option
> ok
> test_default_package 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_default_package) 
> ... ok
> test_default_project 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_default_project) 
> ... ok
> test_default_project_package 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_default_project_package)
>  ... ok
> test_individual_args 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_individual_args) 
> ... ok
> test_missing_package 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_missing_package) 
> ... ok
> test_missing_project 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_missing_project) 
> ... ok
> test_no_working_copy 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_no_working_copy) 
> ... ok
> test_optional_package 
> (tests.test_commandline.TestPopProjectPackageFromArgs.test_optional_package) 
> ... ok
> test_optional_project 
> 

Bug#1077918: psycopg3: binary-any FTBFS

[Adrian Bunk]

Source: psycopg3
Version: 3.2.1-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=psycopg3=3.2.1-2

...
make[2]: Entering directory '/<>/docs'
/bin/sh: 1: sphinx-build: not found
make[2]: *** [Makefile:30: html] Error 127
...

Bug#1077917: marked as done (libresample: Change to meson made test timeout too short)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 13:19:11 +
with message-id 
and subject line Bug#1077917: fixed in libresample 0.1.3-8
has caused the Debian Bug report #1077917,
regarding libresample: Change to meson made test timeout too short
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.)


-- 
1077917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libresample
Version: 0.1.3-7
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/logs.php?pkg=libresample=0.1.3-7

E.g. on armel (no FPU):
https://buildd.debian.org/status/logs.php?pkg=libresample=armel

-2/2 Test #1: testresample .   Passed  291.04 sec
+2/2 testresampleTIMEOUT30.01s   killed by signal 15 SIGTERM


A factor of 100 still keeps the timeout < 1 hour in the rare case
that the test actually hangs:

--- debian/rules.old2024-08-04 12:39:46.375474948 +
+++ debian/rules2024-08-04 12:40:49.823790855 +
@@ -12,3 +12,6 @@
--movedev "debian/tmp/usr/include/*" usr/include/ \
--movedev 
"debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/*.pc" 
usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/ \
debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.so
+
+override_dh_auto_test:
+   dh_auto_test -- --timeout-multiplier 100
--- End Message ---
--- Begin Message ---
Source: libresample
Source-Version: 0.1.3-8
Done: Jonas Smedegaard 

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

Debian distribution maintenance software
pp.
Jonas Smedegaard  (supplier of updated libresample 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, 04 Aug 2024 15:00:38 +0200
Source: libresample
Architecture: source
Version: 0.1.3-8
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1077917
Changes:
 libresample (0.1.3-8) unstable; urgency=medium
 .
   * fix watch file
   * extend test timeout
 closes: bug#1077917, thanks to Adrian Bunk
Checksums-Sha1:
 de825ec592f93ed8b2dee290b841f87ada8638b1 2859 libresample_0.1.3-8.dsc
 8d2e21c9b23849c3abbcef37be4afa862b9f6267 5832 libresample_0.1.3-8.debian.tar.xz
 8b6d57181029e573c85cd5845f6693bd4aec1bd1 8057 
libresample_0.1.3-8_amd64.buildinfo
Checksums-Sha256:
 af6b69fce40f7b953f097b8e81a17f39fcb5e427c619d2fef8228fc3054e5b24 2859 
libresample_0.1.3-8.dsc
 4477cafd552efc88945ae3c3a9af61316722175e723110919dcf88b9228eaa47 5832 
libresample_0.1.3-8.debian.tar.xz
 d532f6831aea0ee9ca2636ac338c8d58de92ea7fce99588465b38166c376ec3c 8057 
libresample_0.1.3-8_amd64.buildinfo
Files:
 9f8303843deb4959e21c99947127dd79 2859 libs optional libresample_0.1.3-8.dsc
 13caadc9b5f8df91712873211c125315 5832 libs optional 
libresample_0.1.3-8.debian.tar.xz
 df78332d4d56eb3463e4b97d07a19105 8057 libs optional 
libresample_0.1.3-8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJABAEBCgAqFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmave7UMHGRyQGpvbmVz
LmRrAAoJECx8MUbBoAEhCeAP/j0s1B0CiCPVBTsJj6r7yOqga9o5WfSFX2sQIZIe
Ybb8J6Rnjp43y1QhwoK7oJRrjPd0WTXHVJ2rl/9HQtg6D+7V5qxtZnk02KjX4+bo
LCCToX/Ajq8NYchgGaC79mviMr6aAvPqCSyqjU5yfHBtFxZnBB2aQBeWwOLpSuE9
v1mg476ShIurybQzJsKJTp8ch1RYn/XIi2Bi/BcDfUPOuA1tqZbuTElYdHUNLpCD
czE+cP0QkO1GGalXDYpi+DycViZxIJzi63cqSyu+zhOQoqBppsv8nPWb5NCtQC3Q
JYW+CTLfa07ZFpwkSb/RyGV+mdnmhDR1dIItFseU1Ay+hzpLDxQOGtaSmsaJ61zv
1p7Gy7JRYTjVNnn41agFNDUrmjL+Cw3n0IYEGI/6bxL+etSyzyFQBDMx0XXOFDWH
tQvWOL2EzWLPP0IL7xELpztPRwxdgrHCOJv9yy/5w7xc9gqWmqCk4/y+oWQzjO0S
K7e2F/vdvC24qzDoA98Q/3UIx4LejBDUYfy8l4P7vQiTx2sI7Bv2KFTZgosSM21H
CfQti2bSMyXXdWvyPBNcEubYfQyNobgEl6+32X1Bi54a/uKT9Ty09HUl9E7dmS9R
zjUj6aT99gt+maIST9CSkGvJIhMRHfBPC3XLr+9fnZQEs9TdeEsE5ZbH45IplqNl
nJHM
=+hCm
-END PGP SIGNATURE-



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

Bug#1073205: docker-compose: new python3-requests dependency brokes docker-compose

[Emmanuel Arias]

Control: tags -1 + moreinfo

Hi,

Sorry, I'm not able to reproduce this bug. Could you provide a way to
reproduce it?


Cheers,
Emmanuel


signature.asc
Description: PGP signature

Processed: docker-compose: new python3-requests dependency brokes docker-compose

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + moreinfo
Bug #1073205 [docker-compose] docker-compose: new python3-requests dependency 
brokes docker-compose
Added tag(s) moreinfo.

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

Bug#1075772: marked as done (src:openconnect: unsatisfied build dependency in testing: ocserv)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 13:05:16 +
with message-id 
and subject line Bug#1075772: fixed in openconnect 9.12-3
has caused the Debian Bug report #1075772,
regarding src:openconnect: unsatisfied build dependency in testing: ocserv
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.)


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

Source: openconnect
Version: 9.12-2
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

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

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

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

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



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: openconnect
Source-Version: 9.12-3
Done: Luca Boccassi 

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

Debian distribution maintenance software
pp.
Luca Boccassi  (supplier of updated openconnect 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, 04 Aug 2024 13:24:52 +0100
Source: openconnect
Architecture: source
Version: 9.12-3
Distribution: unstable
Urgency: medium
Maintainer: Mike Miller 
Changed-By: Luca Boccassi 
Closes: 1075772
Changes:
 openconnect (9.12-3) unstable; urgency=medium
 .
   * Disable autopkgtest and remove test build dependencies (Closes:
 #1075772)
Checksums-Sha1:
 75b313a3b9ff8309128ca84d404bd14aa2d7bec4 2589 openconnect_9.12-3.dsc
 c22df5fa34ad07455925d3f701f87c70b07b5225 15372 openconnect_9.12-3.debian.tar.xz
 c2be9ce1250e10fce326e629aa2e5d958bc2e1a9 9978 
openconnect_9.12-3_source.buildinfo
Checksums-Sha256:
 2836c36a7d0549d5d521a40a74b121de33fe62c6a39ab578938fd2756542ee66 2589 
openconnect_9.12-3.dsc
 640e179c8709b1fc08fd2292912401651d2f69d572c27a1c7c0e9aef607ef153 15372 
openconnect_9.12-3.debian.tar.xz
 fab2909fa0ed4a012a467a439f2d867e644bb0a37350638ffdb7f84c5a11bcec 9978 
openconnect_9.12-3_source.buildinfo
Files:
 1b9d3d3e7277fdf96462b8ed7cd6a89b 2589 net optional openconnect_9.12-3.dsc
 daf0e43fd35677c0c2b5bdd2199f6cf3 15372 net optional 
openconnect_9.12-3.debian.tar.xz
 cd627ab748b190d052f9321a7dad1d61 9978 net optional 
openconnect_9.12-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmavc08RHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB5oow//Q3qeHJE2VD8sT9NDLiZgbrsLq9s17K9O
N+Rdh/E+USrJQp9cfgH35PUT0kOD7r7gLvnU+NXRr9PjTuyHNXuZXrCOxhHYUMic
nVlPUKD4sT4nHuvmo+9C+Sv0ahySZYyCIZAY5QZ1HJJzvjfe18Ky7MkwTuwhT9F5
6ySMb2e3zbKF1FOHVl0BU1JW+m8dQ7mKj/aRv94DLtXQPi8NvFYQhdxmIyC+gzcY
x47M3SWyVymlZ8gUshTr3bD9OtUfqx2LNNn/wcQg5axTRPxD6rS5xqbHH1ChonAk
84nXWXS0gIPYEEDra0i1sfvp0IoD8Gu42docKB+09NJNUzQtc1lZsnH/D+Dfcgik
iSXeY0agFxdthsoAlwLQi8LJQPynpyPX9GxEVBQL1Z7jjoDdN3Sewzu0iM1sQxZz
N4+x/U1TOeM6jI4YuPmIMGVv6rn+G0PzFzz7fWWj4XyvVJj+oUOUzboJFhKTYuYT
2fv6F2XSbjGcqrcOEVeqqyxthgfQEgVOiLW2Jz09Rch3E94n9IM2HUrLIPI90kV1
klNki1olJfCRivE0KIA1oBn43n/jNQOZj1GrO+MtVOlwFWZry0AIeDOLGQUrkF3a
1b7DvjepJNdR7FBUKxvcVVhUBWBz0pU/eORNUGzcp/vzbkWveY4PPZtkxdoNu/+3
mba+chUMZy8=
=w3js
-END PGP 

Bug#1075406: marked as done (py-radix: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 13:05:23 +
with message-id 
and subject line Bug#1075406: fixed in py-radix 0.10.0-5
has caused the Debian Bug report #1075406,
regarding py-radix: ftbfs with GCC-14
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.)


-- 
1075406: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075406
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:py-radix
Version: 0.10.0-4
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/py-radix_0.10.0-4_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
running clean
removing '/<>/.pybuild/cpython3_3.12_radix/build' (and everything 
under it)
'build/bdist.linux-x86_64' does not exist -- can't clean it
'build/scripts-3.12' does not exist -- can't clean it
   dh_autoreconf_clean -O--buildsystem=pybuild
   dh_clean -O--buildsystem=pybuild
 debian/rules build
dh build --with python3 --buildsystem=pybuild
   dh_update_autotools_config -O--buildsystem=pybuild
   dh_autoreconf -O--buildsystem=pybuild
   dh_auto_configure -O--buildsystem=pybuild
I: pybuild base:311: python3.11 setup.py config 
running config
I: pybuild base:311: python3.12 setup.py config 
running config
   dh_auto_build -O--buildsystem=pybuild
I: pybuild base:311: /usr/bin/python3.11 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.11_radix/build/radix
copying radix/radix.py -> 
/<>/.pybuild/cpython3_3.11_radix/build/radix
copying radix/__init__.py -> 
/<>/.pybuild/cpython3_3.11_radix/build/radix
running build_ext
building 'radix._radix' extension
creating build
creating build/temp.linux-x86_64-cpython-311
creating build/temp.linux-x86_64-cpython-311/radix
creating build/temp.linux-x86_64-cpython-311/radix/_radix
x86_64-linux-gnu-gcc -Wsign-compare -DNDEBUG -g -fwrapv -O2 -Wall -g 
-Werror=implicit-function-declaration -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC 
-I/<>/radix -I/usr/include/python3.11 -c radix/_radix.c -o 
build/temp.linux-x86_64-cpython-311/radix/_radix.o
radix/_radix.c: In function ‘add_node_to_list’:
radix/_radix.c:527:37: error: passing argument 2 of ‘PyList_Append’ from 
incompatible pointer type [-Wincompatible-pointer-types]
  527 | PyList_Append(ret, ((RadixNodeObject *)node->data));
  |~^~
  | |
  | RadixNodeObject *
In file included from /usr/include/python3.11/Python.h:64,
 from radix/_radix.c:17:
/usr/include/python3.11/listobject.h:34:43: note: expected ‘PyObject *’ {aka 
‘struct _object *’} but argument is of type ‘RadixNodeObject *’
   34 | PyAPI_FUNC(int) PyList_Append(PyObject *, PyObject *);
  |   ^~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3.11 setup.py build 
I: pybuild base:311: /usr/bin/python3 setup.py build 
running build
running build_py
creating /<>/.pybuild/cpython3_3.12_radix/build/radix
copying radix/radix.py -> 
/<>/.pybuild/cpython3_3.12_radix/build/radix
copying 

Bug#1077587: marked as done (llvm-18-dev: tries to overwrite '/usr/lib/llvm-18/lib/libLLVM-18.so.1', which is also in libllvm18 1:18.1.8-5)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 12:54:23 +
with message-id 
and subject line Bug#1077587: fixed in llvm-toolchain-18 1:18.1.8-9
has caused the Debian Bug report #1077587,
regarding llvm-18-dev: tries to overwrite 
'/usr/lib/llvm-18/lib/libLLVM-18.so.1', which is also in libllvm18 1:18.1.8-5
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.)


-- 
1077587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: llvm-18-dev
Version: 1:18.1.8-7
Severity: serious

When upgrading the llvm-toolchain-18 packages:

Unpacking llvm-18-dev (1:18.1.8-7) over (1:18.1.8-5) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-LjdMdY/04-llvm-18-dev_1%3a18.1.8-7_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/llvm-18/lib/libLLVM-18.so.1', which is also in 
package libllvm18:amd64 1:18.1.8-5

Similar to bug 1076469 in 1:18.1.8-3 (fixed in 1:18.1.8-4).

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

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

Versions of packages llvm-18-dev depends on:
ii  libclang-cpp18  1:18.1.8-7
ii  libffi-dev  3.4.6-1
ii  libllvm18   1:18.1.8-7
ii  libncurses-dev  6.5-2
ii  libxml2-dev 2.12.7+dfsg-3+b1
ii  libz3-dev   4.8.12-3.1+b2
ii  llvm-18 1:18.1.8-7
ii  llvm-18-tools   1:18.1.8-7

llvm-18-dev recommends no packages.

llvm-18-dev suggests no packages.

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: llvm-toolchain-18
Source-Version: 1:18.1.8-9
Done: Sylvestre Ledru 

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

Debian distribution maintenance software
pp.
Sylvestre Ledru  (supplier of updated llvm-toolchain-18 
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, 03 Aug 2024 20:07:17 +0200
Source: llvm-toolchain-18
Architecture: source
Version: 1:18.1.8-9
Distribution: unstable
Urgency: medium
Maintainer: LLVM Packaging Team 
Changed-By: Sylvestre Ledru 
Closes: 1077587
Changes:
 llvm-toolchain-18 (1:18.1.8-9) unstable; urgency=medium
 .
   [ Gianfranco Costamagna ]
   * Mention in changelog also the SVE fixes from llvm-17
   * Drop mips D154390 patch, already upstream
 .
 .
   [ Sylvestre Ledru ]
   * Really fix breaks/replaces (Closes: #1077587)
Checksums-Sha1:
 f6a5dcc2d7e062d3ff9663b5cfa5080156af934c 8359 llvm-toolchain-18_18.1.8-9.dsc
 66235c35743c30fde6c583ea49b2dee62a5b7afa 166328 
llvm-toolchain-18_18.1.8-9.debian.tar.xz
 26a9fe8d8e64a89cbf4273ad1958172796426a11 37026 
llvm-toolchain-18_18.1.8-9_amd64.buildinfo
Checksums-Sha256:
 04eb133df1d218fbd31e4b65666f18324e6800386a817bab9aff15c5f240e77b 8359 
llvm-toolchain-18_18.1.8-9.dsc
 406db802246ba65f3e0293fad312d3e0bf170182e0d03b442047d16b7fbd3a3a 166328 
llvm-toolchain-18_18.1.8-9.debian.tar.xz
 c82036cb240e4bfe845a22255fa168fda822311266ec56e4ac1004e9f5c44206 37026 
llvm-toolchain-18_18.1.8-9_amd64.buildinfo
Files:
 d4e2b04105dd1f045111a24bc5514de3 8359 devel optional 
llvm-toolchain-18_18.1.8-9.dsc
 1048c56291a5c5b4549610a78d0a2c92 166328 devel optional 
llvm-toolchain-18_18.1.8-9.debian.tar.xz
 a70f90ab13198c47a40bb9fb91237fcf 37026 devel optional 
llvm-toolchain-18_18.1.8-9_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1077917: libresample: Change to meson made test timeout too short

[Adrian Bunk]

Source: libresample
Version: 0.1.3-7
Severity: serious
Tags: ftbfs patch

https://buildd.debian.org/status/logs.php?pkg=libresample=0.1.3-7

E.g. on armel (no FPU):
https://buildd.debian.org/status/logs.php?pkg=libresample=armel

-2/2 Test #1: testresample .   Passed  291.04 sec
+2/2 testresampleTIMEOUT30.01s   killed by signal 15 SIGTERM


A factor of 100 still keeps the timeout < 1 hour in the rare case
that the test actually hangs:

--- debian/rules.old2024-08-04 12:39:46.375474948 +
+++ debian/rules2024-08-04 12:40:49.823790855 +
@@ -12,3 +12,6 @@
--movedev "debian/tmp/usr/include/*" usr/include/ \
--movedev 
"debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/*.pc" 
usr/lib/$(DEB_HOST_MULTIARCH)/pkgconfig/ \
debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH)/*.so
+
+override_dh_auto_test:
+   dh_auto_test -- --timeout-multiplier 100

Bug#1069945: rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io'

[Andreas Beckmann]

Followup-For: Bug #1069945
Control: tag -1 patch

Attached is a patch that I plan to NMU.
It fixes support for recent kernels in stable, testing, sid.
It also fixes some dkms packaging issues (and simplifies the dkms
packaging part even further).

I've submitted some of these changes for bookworm-pu: #1077916


Andreas

PS: if the salsa repository were up-to-date, you could get a merge
request with these changes
diff -Nru rapiddisk-9.1.0/debian/changelog rapiddisk-9.1.0/debian/changelog
--- rapiddisk-9.1.0/debian/changelog2024-07-22 15:57:51.0 +0200
+++ rapiddisk-9.1.0/debian/changelog2024-08-03 21:15:54.0 +0200
@@ -1,3 +1,18 @@
+rapiddisk (9.1.0-3.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop -dkms suffix from dkms module name.
+  * Use dkms.conf from upstream.
+  * dkms.conf: Set BUILD_EXCLUSIVE_KERNEL_MIN="2.6.39" for using kstrto*().
+  * Drop unused obsolete patches.
+  * Fix module build for Linux <4.3.
+  * Fix module build for Linux 6.1.83, 6.6.23, 6.7.11, 6.8.2.
+(Closes: #1069945)
+  * Fix module build for Linux 6.9.
+  * Fix module build for Linux 6.10.
+
+ -- Andreas Beckmann   Sat, 03 Aug 2024 21:15:54 +0200
+
 rapiddisk (9.1.0-3) unstable; urgency=medium
 
   * Bump standards version to 4.7.0.
diff -Nru rapiddisk-9.1.0/debian/dkms rapiddisk-9.1.0/debian/dkms
--- rapiddisk-9.1.0/debian/dkms 2023-01-31 14:28:59.0 +0100
+++ rapiddisk-9.1.0/debian/dkms 1970-01-01 01:00:00.0 +0100
@@ -1,9 +0,0 @@
-PACKAGE_NAME="rapiddisk-dkms"
-PACKAGE_VERSION="#MODULE_VERSION#"
-MAKE[0]="make -C ${kernel_source_dir} 
M=${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build"
-CLEAN="make -C ${kernel_source_dir} 
M=${dkms_tree}/${PACKAGE_NAME}/${PACKAGE_VERSION}/build clean"
-AUTOINSTALL=yes
-BUILT_MODULE_NAME[0]="rapiddisk"
-BUILT_MODULE_NAME[1]="rapiddisk-cache"
-DEST_MODULE_LOCATION[0]=/extra
-DEST_MODULE_LOCATION[1]=/extra
diff -Nru rapiddisk-9.1.0/debian/docs rapiddisk-9.1.0/debian/docs
--- rapiddisk-9.1.0/debian/docs 2023-01-31 14:28:59.0 +0100
+++ rapiddisk-9.1.0/debian/docs 1970-01-01 01:00:00.0 +0100
@@ -1 +0,0 @@
-doc/API.txt
diff -Nru rapiddisk-9.1.0/debian/patches/0001-Support-linux-5.19.patch 
rapiddisk-9.1.0/debian/patches/0001-Support-linux-5.19.patch
--- rapiddisk-9.1.0/debian/patches/0001-Support-linux-5.19.patch
2023-01-31 14:28:59.0 +0100
+++ rapiddisk-9.1.0/debian/patches/0001-Support-linux-5.19.patch
1970-01-01 01:00:00.0 +0100
@@ -1,53 +0,0 @@
-From: Andrea Righi 
-Subject: [PATCH] Support linux 5.19.
-Source: upstream, 
https://github.com/pkoutoupis/rapiddisk/pull/116/commits/48e901f08fc1199d917d15e4c68b8a6fec822e1a
-
-Signed-off-by: Andrea Righi 

- module/rapiddisk.c | 18 +-
- 1 file changed, 17 insertions(+), 1 deletion(-)
-
-Index: rapiddisk-8.2.0/module/rapiddisk.c
-===
 rapiddisk-8.2.0.orig/module/rapiddisk.c
-+++ rapiddisk-8.2.0/module/rapiddisk.c
-@@ -633,6 +633,18 @@ io_error:
- #endif
- }
- 
-+#if LINUX_VERSION_CODE >= KERNEL_VERSION(5,19,0)
-+static inline int bdev_openers(struct block_device *bdev)
-+{
-+  return atomic_read(>bd_openers);
-+}
-+#else
-+static inline int bdev_openers(struct block_device *bdev)
-+{
-+  return bdev->bd_openers;
-+}
-+#endif
-+
- static int rdsk_ioctl(struct block_device *bdev, fmode_t mode,
- unsigned int cmd, unsigned long arg)
- {
-@@ -660,7 +672,7 @@ static int rdsk_ioctl(struct block_devic
-   mutex_lock(>bd_mutex);
- #endif
-   error = -EBUSY;
--  if (bdev->bd_openers <= 1) {
-+  if (bdev_openers(bdev) <= 1) {
- #if LINUX_VERSION_CODE >= KERNEL_VERSION(3,3,0)
- #if LINUX_VERSION_CODE >= KERNEL_VERSION(5,8,0) || (defined(RHEL_MAJOR) && 
RHEL_MAJOR == 8 && RHEL_MINOR >= 4)
-   invalidate_bdev(bdev);
-@@ -805,7 +817,11 @@ static int attach_device(int size)
-   disk->queue->nr_requests = nr_requests;
-   disk->queue->limits.discard_granularity = PAGE_SIZE;
-   disk->queue->limits.max_discard_sectors = UINT_MAX;
-+#if LINUX_VERSION_CODE >= KERNEL_VERSION(5,19,0)
-+  blk_queue_max_discard_sectors(disk->queue, 0);
-+#else
-   blk_queue_flag_set(QUEUE_FLAG_DISCARD, disk->queue);
-+#endif
-   blk_queue_flag_set(QUEUE_FLAG_NONROT, disk->queue);
- #else
-   rdsk->rdsk_queue->limits.max_sectors = (max_sectors * 2);
diff -Nru 
rapiddisk-9.1.0/debian/patches/0002-Adding-Linux-kernel-6.0-support-133.patch 
rapiddisk-9.1.0/debian/patches/0002-Adding-Linux-kernel-6.0-support-133.patch
--- 
rapiddisk-9.1.0/debian/patches/0002-Adding-Linux-kernel-6.0-support-133.patch   
2023-01-31 14:28:59.0 +0100
+++ 
rapiddisk-9.1.0/debian/patches/0002-Adding-Linux-kernel-6.0-support-133.patch   
1970-01-01 01:00:00.0 +0100
@@ -1,26 +0,0 @@
-From: Petros Koutoupis 
-Date: Wed, 5 Oct 2022 12:47:15 +
-Subject: [PATCH] Adding Linux 

Processed: Re: rapiddisk-dkms: module fails to build for Linux 6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 'dm_io'

[Debian Bug Tracking System]

Processing control commands:

> tag -1 patch
Bug #1069945 [rapiddisk-dkms] rapiddisk-dkms: module fails to build for Linux 
6.7.12, 6.1.85: rapiddisk-cache.c:198:16: error: too few arguments to function 
'dm_io'
Added tag(s) patch.

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

Bug#1075772: marked as pending in openconnect

[Luca Boccassi]

Control: tag -1 pending

Hello,

Bug #1075772 in openconnect 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/openconnect/-/commit/42eb7b6b00f6ed1feabfeb0c759c5c33ccdafc4a


Disable autopkgtest and remove test build dependencies

Dependencies for tests have been removed due to various armv7 bugs
so they are no longer available in testing, disable all tests

Closes: #1075772


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1075772

Processed: Bug#1075772 marked as pending in openconnect

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1075772 [src:openconnect] src:openconnect: unsatisfied build dependency in 
testing: ocserv
Added tag(s) pending.

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

Bug#1075406: marked as pending in py-radix

[Alexandre Detiste]

Control: tag -1 pending

Hello,

Bug #1075406 in py-radix 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/py-radix/-/commit/c9a7e136e1fce1dfe97289d064574ee9131c03d3


fix FTBFS with GCC-14 (Closes: #1075406)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1075406

Processed: Bug#1075406 marked as pending in py-radix

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1075406 [src:py-radix] py-radix: ftbfs with GCC-14
Added tag(s) pending.

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

Bug#1071875: marked as done (jupyter-server-terminals: FTBFS: unsatisfiable build-dependencies)

[Debian Bug Tracking System]

Your message dated Sun, 4 Aug 2024 13:15:47 +0100
with message-id 
and subject line Re: Bug#1071875: jupyter-server-terminals: FTBFS: 
unsatisfiable build-dependencies
has caused the Debian Bug report #1071875,
regarding jupyter-server-terminals: FTBFS: unsatisfiable build-dependencies
to be marked as done.

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

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


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

Package: src:jupyter-server-terminals
Version: 0.5.3-2
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-pytest-jupyter : Depends: python3-jupyter-core (>= 5.7) but 5.3.2-1 is 
to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use



The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202405/

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
On Sat, May 25, 2024 at 07:21:28PM +0200, Santiago Vila wrote:
> Package: src:jupyter-server-terminals
> Version: 0.5.3-2
> Severity: serious
> Tags: ftbfs
> 
> Dear maintainer:
> 
> During a rebuild of all packages in unstable, your package failed to build:

jupyter-core has now been updated in unstable and testing, and this
package has now successfully built.

   Julian--- End Message ---

Bug#1077914: surf: flaky autopkgtest on some architectures: Alarm clock

[Paul Gevers]

Source: surf
Version: 2.1+git20221016-6
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package, because it 
was blocking the migration of src:autopkgtest. I noticed that it 
regularly fails, although more on some architectures than others. The 
text suggest it's a timeout problem. Maybe you want to increase it?


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/s/surf/testing/armel/49977036/

254s autopkgtest [09:32:22]: test command2: [---
258s
258s (surf:5695): dbind-WARNING **: 09:32:26.682: AT-SPI: Error 
retrieving accessibility bus address: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.a11y.Bus was not 
provided by any .service files
258s MESA: error: ZINK: vkCreateInstance failed 
(VK_ERROR_INCOMPATIBLE_DRIVER)

258s libEGL warning: egl: failed to create dri2 screen
259s Could not determine the accessibility bus address
261s Could not read style file: /home/debci/.surf/styles/default.css
261s Alarm clock
262s autopkgtest [09:32:30]: test command2: ---]
262s command2 FAIL non-zero exit status 142


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1075329: marked as done (ocaml-lo: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 11:49:30 +
with message-id 
and subject line Bug#1075329: fixed in ocaml-lo 0.2.0.git20240724.0b43bdf-1~exp1
has caused the Debian Bug report #1075329,
regarding ocaml-lo: ftbfs with GCC-14
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.)


-- 
1075329: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075329
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:ocaml-lo
Version: 0.2.0-4
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/ocaml-lo_0.2.0-4_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
gpgv: Signature made Thu Aug 17 06:02:18 2023 UTC
gpgv:using RSA key 6DE24E97ECA886CC56E6250E21B8EEF1B1893081
gpgv:issuer "glo...@debian.org"
gpgv: Can't check signature: No public key
dpkg-source: warning: cannot verify inline signature for 
./ocaml-lo_0.2.0-4.dsc: no acceptable signature found
dpkg-source: info: extracting ocaml-lo in /<>
dpkg-source: info: unpacking ocaml-lo_0.2.0.orig.tar.gz
dpkg-source: info: unpacking ocaml-lo_0.2.0-4.debian.tar.xz

Check disk space


Sufficient free space for build

User Environment


APT_CONFIG=/var/lib/sbuild/apt.conf
HOME=/sbuild-nonexistent
LANG=C.UTF-8
LC_ALL=C.UTF-8
LOGNAME=user42
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
SCHROOT_ALIAS_NAME=unstable
SCHROOT_CHROOT_NAME=sid-amd64-sbuild
SCHROOT_COMMAND=env
SCHROOT_GID=1001
SCHROOT_GROUP=user42
SCHROOT_SESSION_ID=sid-amd64-sbuild-cfa9207e-5c35-4174-a996-03cc273d81c7
SCHROOT_UID=1001
SCHROOT_USER=user42
SHELL=/bin/sh
USER=user42

dpkg-buildpackage
-

Command: dpkg-buildpackage --sanitize-env -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package ocaml-lo
dpkg-buildpackage: info: source version 0.2.0-4
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Stéphane Glondu 
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 debian/rules clean
dh clean --with ocaml --buildsystem ocaml_dune
   dh_auto_clean -O--buildsystem=ocaml_dune
dune clean
   dh_autoreconf_clean -O--buildsystem=ocaml_dune
   dh_ocamlclean -O--buildsystem=ocaml_dune
   dh_clean -O--buildsystem=ocaml_dune
 debian/rules binary
dh binary --with ocaml --buildsystem ocaml_dune
   dh_update_autotools_config -O--buildsystem=ocaml_dune
   dh_autoreconf -O--buildsystem=ocaml_dune
   dh_ocamlinit -O--buildsystem=ocaml_dune
   dh_auto_configure -O--buildsystem=ocaml_dune
   dh_auto_build -O--buildsystem=ocaml_dune
dune build -j 8 -p lo
File "src/dune", line 9, characters 9-17:
9 |   (names lo_stubs)
 
(cd _build/default/src && /usr/bin/x86_64-linux-gnu-gcc -O2 
-fno-strict-aliasing -fwrapv -pthread -fPIC -g -O2 -fstack-protector-strong 
-fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
-D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -g -I /usr/lib/ocaml -I 
/usr/lib/ocaml/threads -o lo_stubs.o -c lo_stubs.c)
lo_stubs.c: In function ‘caml_lo_message_new’:
lo_stubs.c:70:20: error: assignment to ‘lo_address’ {aka ‘struct lo_address_ 
*’} from incompatible pointer type ‘lo_message’ {aka ‘struct lo_message_ *’} 
[-Wincompatible-pointer-types]
   70 |   Address_val(ans) = m;
  |^
dh_auto_build: error: dune build -j 8 -p lo returned exit code 1
make: *** [debian/rules:7: binary] Error 25
dpkg-buildpackage: error: 

Bug#1077804: adduser autopkgtest assumes backslash is a valid char

[Chris Hofstaedtler]

On Sat, Aug 03, 2024 at 05:38:59PM +0200, Chris Hofstaedtler wrote:
> > We allow backslashes in adduser to cater for some samba corner
> > cases where a user named domain\user is needed.
> > 
> > I am kind of concerned that this tightening of src:shadow's allowed usr
> > name character ranges breaks actual use cases.

I've briefly chatted with mjt, and he thinks it is fine to restrict
backslashes.

Chris

Processed: Re: Bug#1074657: accountsservice: FTBFS: AttributeError: 'TestAccountsServicePreExistingUser' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + upstream fixed-upstream pending
Bug #1074657 [src:accountsservice] accountsservice: FTBFS: AttributeError: 
'TestAccountsServicePreExistingUser' object has no attribute 'assertEquals'. 
Did you mean: 'assertEqual'?
Added tag(s) pending, fixed-upstream, and upstream.
> forwarded -1 
> https://gitlab.freedesktop.org/accountsservice/accountsservice/-/merge_requests/142
Bug #1074657 [src:accountsservice] accountsservice: FTBFS: AttributeError: 
'TestAccountsServicePreExistingUser' object has no attribute 'assertEquals'. 
Did you mean: 'assertEqual'?
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/accountsservice/accountsservice/-/merge_requests/142'.

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

Bug#1074657: accountsservice: FTBFS: AttributeError: 'TestAccountsServicePreExistingUser' object has no attribute 'assertEquals'. Did you mean: 'assertEqual'?

[Simon McVittie]

Control: tags -1 + upstream fixed-upstream pending
Control: forwarded -1 
https://gitlab.freedesktop.org/accountsservice/accountsservice/-/merge_requests/142

On Tue, 02 Jul 2024 at 14:40:06 +0200, Lucas Nussbaum wrote:
> >   File 
> > "/<>/obj-x86_64-linux-gnu/../tests/test-libaccountsservice.py",
> >  line 118, in test_multiple_inflight_get_user_by_id_calls
> > self.assertEquals(user.get_user_name(), 'pizza')
> > ^
> > AttributeError: 'TestAccountsServicePreExistingUser' object has no 
> > attribute 'assertEquals'. Did you mean: 'assertEqual'?

This is a regression caused by Python 3.12 becoming the default version.
The deprecated method assertEquals() was removed:
https://docs.python.org/3/whatsnew/3.12.html#unittest-testcase-removed-aliases

This was fixed in upstream git a while ago, and I've pushed that change
to Salsa as a patch.

I didn't do a team upload with that fix, because I don't yet have a
solution to the other RC bugs involving autopkgtest failures (#1033147,
#1034257).

smcv

Bug#1077911: notmuch: Fails to build because of Build-Conflicts: gdb-minimal

[Jeremy Bícha]

Source: notmuch
Version: 0.38.3-2
Severity: serious
Tags: ftbfs

As of gdb 15.1-1, the binary package gdb has Provides: gdb-minimal.
notmuch has Build-Conflicts: gdb-minimal and Build-Depends: gdb.
Because this can't be resolved, notmuch is unable to build.

I suggest removing Build-Conflicts: gdb-minimal.

Thank you,
Jeremy Bícha

Bug#1077910: notmuch: autopkgtest failure with glib 2.81.1

[Jeremy Bícha]

Source: notmuch
Version: 0.38.3-2
Severity: serious
Tags: ftbfs
Control: affects -1 src:glib2.0
X-Debbugs-CC: glib...@packages.debian.org

glib 2.81.1 was recently uploaded to Unstable. notmuch's autopkgtest
(but not the build test) is now failing. Specifically, the T810-tsan
test is failing. The test was passing with glib 2.81.0. This is
preventing glib 2.81.1 from migrating to Testing.

https://ci.debian.net/packages/n/notmuch/testing/amd64/
https://gitlab.gnome.org/GNOME/glib/-/compare/2.81.0...2.81.1

By the way, it appears like this particular test has always failed on
Ubuntu's autopkgtest infrastructure:
https://autopkgtest.ubuntu.com/packages/notmuch


log excerpt


T810-tsan: Testing run code with TSan enabled against the library
 PASS   create
 FAIL   query
--- T810-tsan.2.EXPECTED 2024-08-03 17:25:10.734599354 +
+++ T810-tsan.2.OUTPUT 2024-08-03 17:25:10.734599354 +
@@ -1,2 +1,27 @@
== stdout ==
== stderr ==
+==
+WARNING: ThreadSanitizer: data race (pid=31219)
+  Atomic read of size 1 at 0x72102580 by thread T2:
+#0 pthread_rwlock_rdlock
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:1476
(libtsan.so.2+0x535cc) (BuildId:
4696c58f898e5d5cf4fe08e45868ac4fc5702473)
+#1   (libglib-2.0.so.0+0xb9f0b) (BuildId:
3a7c5b70371ef106debb656a45acbdf6aa91218c)
+
+  Previous write of size 8 at 0x72102580 by thread T1:
+#0 malloc ../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:665
(libtsan.so.2+0x513b6) (BuildId:
4696c58f898e5d5cf4fe08e45868ac4fc5702473)
+#1   (libglib-2.0.so.0+0xb9ee1) (BuildId:
3a7c5b70371ef106debb656a45acbdf6aa91218c)
+
+  Location is heap block of size 56 at 0x72102580 allocated by thread T1:
+#0 malloc ../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:665
(libtsan.so.2+0x513b6) (BuildId:
4696c58f898e5d5cf4fe08e45868ac4fc5702473)
+#1   (libglib-2.0.so.0+0xb9ee1) (BuildId:
3a7c5b70371ef106debb656a45acbdf6aa91218c)
+
+  Thread T2 (tid=31222, running) created by main thread at:
+#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:1022
(libtsan.so.2+0x564a6) (BuildId:
4696c58f898e5d5cf4fe08e45868ac4fc5702473)
+#1 main CWD/test1.c:24 (test1+0x136b) (BuildId:
1832b22acf7f8ab44068867df3e5f3045b88cf92)
+
+  Thread T1 (tid=31221, running) created by main thread at:
+#0 pthread_create
../../../../src/libsanitizer/tsan/tsan_interceptors_posix.cpp:1022
(libtsan.so.2+0x564a6) (BuildId:
4696c58f898e5d5cf4fe08e45868ac4fc5702473)
+#1 main CWD/test1.c:23 (test1+0x1331) (BuildId:
1832b22acf7f8ab44068867df3e5f3045b88cf92)
+
+SUMMARY: ThreadSanitizer: data race
(/lib/x86_64-linux-gnu/libglib-2.0.so.0+0xb9f0b) (BuildId:
3a7c5b70371ef106debb656a45acbdf6aa91218c)
+==
+ThreadSanitizer: reported 1 warnings

Thank you,
Jeremy Bícha

Processed: notmuch: autopkgtest failure with glib 2.81.1

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:glib2.0
Bug #1077910 [src:notmuch] notmuch: autopkgtest failure with glib 2.81.1
Added indication that 1077910 affects src:glib2.0

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

Bug#1077909: meep-openmpi: Does this package still make sense?

[Adrian Bunk]

Source: meep-openmpi
Version: 1.25.0-4
Severity: serious

Situation in bookworm:

OpenMPI:
available everywhere
default everywhere

MPICH:
available everywhere


(Future) situation in trixie:

OpenMPI:
available on 64-bit
default on 64-bit

MPICH:
available everywhere
default on 32-bit



The situation was different 15 years ago,
but with OpenMPI as default everywhere it is available
there is no architecture where meep-openmpi should be
different from meep-mpi-default.

Bug#1075077: marked as done (hypre: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 10:34:35 +
with message-id 
and subject line Bug#1075077: fixed in hypre 2.31.0-1exp2
has caused the Debian Bug report #1075077,
regarding hypre: ftbfs with GCC-14
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.)


-- 
1075077: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075077
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:hypre
Version: 2.29.0-2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/hypre_2.29.0-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
 3150 |   comm_handle = hypre_ParCSRCommHandleCreate (2, comm_pkg, 
x_ext_data, buf_data);
  | 
^~~~
schwarz.c:3014:16: note: ‘buf_data’ was declared here
 3014 |HYPRE_Real *buf_data;
  |^~~~
schwarz.c: In function ‘hypre_ParAMGCreateDomainDof’:
schwarz.c:3686:49: warning: ‘a_ext_i’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3686 | for (j = a_ext_i[i_dof]; j < a_ext_i[i_dof + 1]; j++)
  | ^
schwarz.c:3216:15: note: ‘a_ext_i’ was declared here
 3216 |HYPRE_Int *a_ext_i;
  |   ^~~
schwarz.c:3688:19: warning: ‘a_ext_j’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3688 |jj = a_ext_j[j];
  |~~~^~~~
schwarz.c:3217:18: note: ‘a_ext_j’ was declared here
 3217 |HYPRE_BigInt *a_ext_j;
  |  ^~~
schwarz.c:3703:72: warning: ‘a_ext_data’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3703 |  AE[i_loc + j_loc * local_dof_counter] = 
a_ext_data[j];
  |  
~~^~~
schwarz.c:3218:16: note: ‘a_ext_data’ was declared here
 3218 |HYPRE_Real *a_ext_data;
  |^~
schwarz.c: In function ‘hypre_ParGenerateScale’:
schwarz.c:3797:22: warning: ‘scale_ext’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3797 | scale_ext[j_loc - num_variables] += 1.0;
  | ~^~~
schwarz.c:3762:16: note: ‘scale_ext’ was declared here
 3762 |HYPRE_Real *scale_ext;
  |^
schwarz.c:3763:16: warning: ‘scale_int’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3763 |HYPRE_Real *scale_int;
  |^
schwarz.c: In function ‘hypre_ParGenerateHybridScale’:
schwarz.c:3990:42: warning: ‘send_map_starts’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3990 |   for (j = start; j < send_map_starts[i + 1]; j++)
  |   ~~~^~~
schwarz.c:3859:15: note: ‘send_map_starts’ was declared here
 3859 |HYPRE_Int *send_map_starts;
  |   ^~~
schwarz.c:3992:30: warning: ‘send_map_elmts’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3992 |  scale[send_map_elmts[j]] += scale_int[index++];
  |~~^~~
schwarz.c:3860:15: note: ‘send_map_elmts’ was declared here
 3860 |HYPRE_Int *send_map_elmts;
  |   ^~
schwarz.c:3897:20: warning: ‘index_ext’ may be used uninitialized 
[-Wmaybe-uninitialized]
 3897 |   index_ext[i] = -1;
  |   ~^~~~
schwarz.c:3861:15: note: ‘index_ext’ was declared here
 3861 |HYPRE_Int *index_ext;
  |   

Bug#1074812: marked as done (apr-util: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 10:34:15 +
with message-id 
and subject line Bug#1074812: fixed in apr-util 1.6.3-3
has caused the Debian Bug report #1074812,
regarding apr-util: ftbfs with GCC-14
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.)


-- 
1074812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:apr-util
Version: 1.6.3-2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/apr-util_1.6.3-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
checking for ldap_start_tls_s in -lldap... yes
checking for ldap_sslinit in -lldap... no
checking for ldapssl_init in -lldap... no
checking for ldapssl_install_routines in -lldap... no
  setting LDADD_ldap to "-lldap -llber"
checking for ber_init in -llber... yes
checking for lber.h... yes
checking for ldap.h... yes
checking for ldap_ssl.h... no
checking for LDAP toolkit... OpenLDAP
checking style of ldap_set_rebind_proc routine... three
checking for gdbm.h... yes
checking for gdbm_open in -lgdbm... yes
checking for Berkeley DB 5.3 in the standard places... 
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb-5.3... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb5-5.3... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb53... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb-5... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb5... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb... no
checking for Berkeley DB 5.3 in /usr/local... 
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb-5.3... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb5-5.3... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb53... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb-5... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb5... no
checking for db53/db.h... no
checking for db5/db.h... no
checking for db.h... yes
checking for -ldb... no
checking for Berkeley DB 5.3 in /usr/local/BerkeleyDB.5.3... directory not found
checking for Berkeley DB 5.3 in /boot/home/config... directory not found
configure: error: Berkeley db5 not found
make[1]: *** [debian/rules:66: override_dh_auto_configure] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:24: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: apr-util
Source-Version: 1.6.3-3
Done: Stefan Fritsch 

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

Debian distribution maintenance software
pp.
Stefan Fritsch  

Bug#1077906: meep-mpi-default: autopkgtest failure

[Adrian Bunk]

Source: meep-mpi-default
Version: 1.25.0-4
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/amd64/m/meep-mpi-default/49972657/log.gz

...
277s autopkgtest [03:33:17]: test autodep8-python3: set -e ; for py in 
$(py3versions -r 2>/dev/null) ; do cd "$AUTOPKGTEST_TMP" ; echo "Testing with 
$py:" ; $py -c "import meep_mpi_default; print(meep_mpi_default)" ; done
277s autopkgtest [03:33:17]: test autodep8-python3: [---
277s Testing with python3.12:
277s Traceback (most recent call last):
277s   File "", line 1, in 
277s ModuleNotFoundError: No module named 'meep_mpi_default'
277s autopkgtest [03:33:17]: test autodep8-python3: ---]
277s autopkgtest [03:33:17]: test autodep8-python3:  - - - - - - - - - - 
results - - - - - - - - - -
277s autodep8-python3 FAIL non-zero exit status 1
...


This can be solved with:

$ cat debian/tests/autopkgtest-pkg-python.conf
import_name = meep
$

Bug#1077898: marked as done (zathura: broke plugin ABI)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 09:35:01 +
with message-id 
and subject line Bug#1077898: fixed in zathura 0.5.8-1
has caused the Debian Bug report #1077898,
regarding zathura: broke plugin ABI
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.)


-- 
1077898: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077898
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: zathura
Version: 0.5.7-1
Severity: grave
X-Debbugs-Cc: sramac...@debian.org

Per $subject.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: zathura
Source-Version: 0.5.8-1
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated zathura 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, 04 Aug 2024 11:12:44 +0200
Source: zathura
Architecture: source
Version: 0.5.8-1
Distribution: unstable
Urgency: medium
Maintainer: Sebastian Ramacher 
Changed-By: Sebastian Ramacher 
Closes: 1077898
Changes:
 zathura (0.5.8-1) unstable; urgency=medium
 .
   * New upstream version 0.5.8
   * debian/control: Bump plugin ABI (Closes: #1077898)
Checksums-Sha1:
 26d80c385e10b0519cf24b5d5c7eac4de1f814b4 1559 zathura_0.5.8-1.dsc
 4798fa120f0612c46b73bb338c04ba53d24bfb43 172524 zathura_0.5.8.orig.tar.xz
 e6508cd9c8398ea32e81828da9169d0164dcdac7 12316 zathura_0.5.8-1.debian.tar.xz
 5f53e2b4bc7c7de31533af947c245d4aac153914 17407 zathura_0.5.8-1_source.buildinfo
Checksums-Sha256:
 dd44226e8baf1d637eadd9291be94ac83f6b78c3af7b4c8daccbddbe50e85c65 1559 
zathura_0.5.8-1.dsc
 f2bf8dcb2edff10a8e11f1f981bf8f6a42b997b4f851ab00bfd33a706ad43af8 172524 
zathura_0.5.8.orig.tar.xz
 766e626c98d09716d4691ce8872e4e72e91951a7e136456feda701c278c7d6e0 12316 
zathura_0.5.8-1.debian.tar.xz
 b609261ce41e089f0548400c2dc34378bc0b38772cb06dc8b66fc0952f911ca4 17407 
zathura_0.5.8-1_source.buildinfo
Files:
 b24f96532fd12a019c9c121c4693a048 1559 text optional zathura_0.5.8-1.dsc
 28f5ddb3df3094c506034691c623ff60 172524 text optional zathura_0.5.8.orig.tar.xz
 f2c19e227d82085415c9862af1f971c7 12316 text optional 
zathura_0.5.8-1.debian.tar.xz
 b34d8fb49f5a1e6fd7b7896c1339c7fe 17407 text optional 
zathura_0.5.8-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZq9GMAAKCRAhk2s2YA/N
iReOAP0R/zav9yWy11Hf6EF9vAyMeGvbn47IPJ7NS/blfiaAdAEAxG9Hr2xqew0K
2+knzwnHOFPRR2kcqe6exdJ5T/ZiZAQ=
=tNUy
-END PGP SIGNATURE-



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

Bug#1077904: ledmon FTBFS on 32-bit with gcc 14

[Adrian Bunk]

Source: ledmon
Version: 0.97-1.1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=ledmon=0.97-1.1

...
utils.c: In function ‘get_uint64’:
utils.c:105:18: error: passing argument 1 of ‘str_toul’ from incompatible 
pointer type [-Wincompatible-pointer-types]
  105 | str_toul(, p, NULL, 16);
  |  ^~~
  |  |
  |  uint64_t * {aka long long unsigned int *}
In file included from utils.c:48:
utils.h:368:29: note: expected ‘long unsigned int *’ but argument is of type 
‘uint64_t *’ {aka ‘long long unsigned int *’}
  368 | int str_toul(unsigned long *dest, const char *strptr, char **endptr, 
int base);
  |  ~~~^~~~
...

Bug#1077903: debusine: flaky autopkgtest: SIGKILL is called but processes were already dead

[Paul Gevers]

Source: debusine
Version: 0.4.1
Severity: serious
User: debian...@lists.debian.org
Usertags: flaky

Dear maintainer(s),

I looked at the results of the autopkgtest of your package, because the 
results were blocking the migration of src:autopkgtest. I noticed that 
it regularly fails.


Because the unstable-to-testing migration software now blocks on
regressions in testing, flaky tests, i.e. tests that flip between
passing and failing without changes to the list of installed packages,
are causing people unrelated to your package to spend time on these
tests.

Don't hesitate to reach out if you need help and some more information
from our infrastructure.

Paul

https://ci.debian.net/packages/d/debusine/testing/amd64/49938456/

 53s ==
 53s FAIL: test_execute_cmd_finished_before_killpg_sigkill 
(debusine.tasks.tests.test_task.RunCommandTaskTests.test_execute_cmd_finished_before_killpg_sigkill)

 53s Execute script. SIGKILL is called but processes were already dead.
 53s --
 53s Traceback (most recent call last):
 53s   File 
"/usr/lib/python3/dist-packages/debusine/tasks/tests/test_task.py", line 
1350, in test_execute_cmd_finished_before_killpg_sigkill

 53s self.assertIn(
 53s AssertionError: 'output (contains stdout and stderr):\n\naborted: 
True\nreturncode: -9\n' not found in 'cmd: 
/tmp/debusine-tests-i0k_pvrb/signal-logger.sh 
/tmp/debusine-tests-i0k_pvrb 2091 2 TERM\noutput (contains stdout and 
stderr):\n\nFiles in working 
directory:\n2235.pid\n2236.pid\nsignal-logger.sh


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1075059: marked as done (haskell-hsopenssl: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 09:19:30 +
with message-id 
and subject line Bug#1075059: fixed in haskell-hsopenssl 0.11.7.7-2
has caused the Debian Bug report #1075059,
regarding haskell-hsopenssl: ftbfs with GCC-14
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.)


-- 
1075059: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075059
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-hsopenssl
Version: 0.11.7.6-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/haskell-hsopenssl_0.11.7.6-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
 warning: return discards ‘const’ qualifier from pointer target type 
[-Wdiscarded-qualifiers]
   15 | BIO_METHOD* 
ghczuwrapperZC2ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzuszumem(void)
 {return BIO_s_mem();}
  | 
  ^~~
   |
15 | BIO_METHOD* 
ghczuwrapperZC2ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzuszumem(void)
 {return BIO_s_mem();}
   |
   ^
/tmp/ghc2838709_0/ghc_227.c: In function 
‘ghczuwrapperZC4ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzufzubuffer’:

/tmp/ghc2838709_0/ghc_227.c:21:122: error:
 warning: return discards ‘const’ qualifier from pointer target type 
[-Wdiscarded-qualifiers]
   21 | BIO_METHOD* 
ghczuwrapperZC4ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzufzubuffer(void)
 {return BIO_f_buffer();}
  | 
 ^~
   |
21 | BIO_METHOD* 
ghczuwrapperZC4ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzufzubuffer(void)
 {return BIO_f_buffer();}
   |
  ^
/tmp/ghc2838709_0/ghc_227.c: In function 
‘ghczuwrapperZC6ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzufzubase64’:

/tmp/ghc2838709_0/ghc_227.c:26:122: error:
 warning: return discards ‘const’ qualifier from pointer target type 
[-Wdiscarded-qualifiers]
   26 | BIO_METHOD* 
ghczuwrapperZC6ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzufzubase64(void)
 {return BIO_f_base64();}
  | 
 ^~
   |
26 | BIO_METHOD* 
ghczuwrapperZC6ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziBIOZCBIOzufzubase64(void)
 {return BIO_f_base64();}
   |
  ^
[25 of 33] Compiling OpenSSL.ASN1 ( dist-ghc/build/OpenSSL/ASN1.hs, 
dist-ghc/build/OpenSSL/ASN1.o, dist-ghc/build/OpenSSL/ASN1.dyn_o )
/tmp/ghc2838709_0/ghc_234.c: In function 
‘ghczuwrapperZC8ZCHsOpenSSLzm0zi11zi7zi6zmFdDC6rxnqkzz68J4WQpPUVOZCOpenSSLziASN1ZCOBJzunid2ln’:

/tmp/ghc2838709_0/ghc_234.c:35:120: error:
 warning: return discards ‘const’ qualifier from pointer target type 
[-Wdiscarded-qualifiers]
   35 | char* 

Bug#1077902: rust-input-linux: autopkgtest failure on 32-bit

[Adrian Bunk]

Source: rust-input-linux
Version: 0.6.0-1
Severity: serious

https://ci.debian.net/data/autopkgtest/testing/i386/r/rust-input-linux/49973115/log.gz

...
106s error[E0554]: `#![feature]` may not be used on the stable release channel
106s  --> src/lib.rs:3:30
106s   |
106s 3 | #![cfg_attr(feature = "dox", feature(doc_cfg))]
106s   |  
106s 
108s error[E0308]: mismatched types
108s   --> src/time.rs:19:10
108s|
108s 19 | #[derive(Serialize, Deserialize)]
108s|  ^
108s|  |
108s|  expected ``, found ``
108s|  arguments to this function are incorrect
108s|
108s= note: expected reference ``
108s   found reference ``
108s note: function defined here
108s   --> /usr/share/cargo/registry/serde-1.0.203/src/private/ser.rs:12:8
108s|
108s 12 | pub fn constrain(t: ) ->  {
108s|^
108s= note: this error originates in the derive macro `Serialize` (in 
Nightly builds, run with -Z macro-backtrace for more info)
108s 
108s error[E0308]: mismatched types
108s   --> src/time.rs:19:21
108s|
108s 19 | #[derive(Serialize, Deserialize)]
108s| ^^^ expected `i32`, found `i64`
108s|
108s= note: this error originates in the derive macro `Deserialize` (in 
Nightly builds, run with -Z macro-backtrace for more info)
108s 
111s Some errors have detailed explanations: E0308, E0554.
111s For more information about an error, try `rustc --explain E0308`.
111s error: could not compile `input-linux` (lib test) due to 4 previous errors
...

Bug#1077900: src:chiark-utils: fails to migrate to testing for too long: FTBFS and unresolved RC issue

[Paul Gevers]

Source: chiark-utils
Version: 7.0.0
Severity: serious
Control: close -1 7.0.1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 1075799 1075821

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:chiark-utils has been trying to migrate 
for 31 days [2]. Hence, I am filing this bug. The version in unstable 
failed to build as reported in bug 1075799 and has an RC issue as 
reported in bug 1075821.


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=chiark-utils



OpenPGP_signature.asc
Description: OpenPGP digital signature

Processed: src:chiark-utils: fails to migrate to testing for too long: FTBFS and unresolved RC issue

[Debian Bug Tracking System]

Processing control commands:

> close -1 7.0.1
Bug #1077900 [src:chiark-utils] src:chiark-utils: fails to migrate to testing 
for too long: FTBFS and unresolved RC issue
Marked as fixed in versions chiark-utils/7.0.1.
Bug #1077900 [src:chiark-utils] src:chiark-utils: fails to migrate to testing 
for too long: FTBFS and unresolved RC issue
Marked Bug as done
> block -1 by 1075799 1075821
Bug #1077900 {Done: Paul Gevers } [src:chiark-utils] 
src:chiark-utils: fails to migrate to testing for too long: FTBFS and 
unresolved RC issue
1077900 was not blocked by any bugs.
1077900 was not blocking any bugs.
Added blocking bug(s) of 1077900: 1075799 and 1075821

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

Bug#1077898: zathura: broke plugin ABI

[Sebastian Ramacher]

Package: zathura
Version: 0.5.7-1
Severity: grave
X-Debbugs-Cc: sramac...@debian.org

Per $subject.

Cheers
-- 
Sebastian Ramacher

Processed: Re: sqlalchemy: FTBFS: failing tests

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://github.com/python/mypy/issues/17548
Bug #1076928 [src:sqlalchemy] sqlalchemy: FTBFS: failing tests
Set Bug forwarded-to-address to 'https://github.com/python/mypy/issues/17548'.

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

Bug#1076928: sqlalchemy: FTBFS: failing tests

[Michael R. Crusoe]

Control: forwarded -1 https://github.com/python/mypy/issues/17548

Upstream is aware of the issue ; I've asked if the tests can be safely skipped



OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1077895: spellcast: FTBFS: engine.c:114:5: error: implicit declaration of function 'clear_round'

[Andreas Beckmann]

Package: spellcast
Version: 1.0-22
Severity: serious
Tags: ftbfs sid trixie
Justification: fails to build from source

hi,

spellcast recently started to FTBFS:

   debian/rules override_dh_auto_build
make[1]: Entering directory '/build/spellcast-1.0'
RESOLUTION=RES1024 make
make[2]: Entering directory '/build/spellcast-1.0'
cc -O2 -g -I/usr/X11R6/include -I./bitmaps 
-DBODYFONT=\"-*-times-medium-r-*--14-*\" 
-DBODYFONT_ALT=\"-*-helvetica-medium-r-*--12-*\" -DBODYFONT_ALT2=\"fixed\" 
-DTRANSCRIPTDIR=\"/var/games/spellcast\" -DRES1024 -DCOLOUR 
-DPACKAGE=\"spellcast\" -DLOCALEDIR=\"/
usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2  -c -o engine.o engine.c
engine.c: In function 'InitBeing':
engine.c:114:5: error: implicit declaration of function 'clear_round' 
[-Wimplicit-function-declaration]
  114 | clear_round(fred);
  | ^~~
engine.c: In function 'BeginGame':
engine.c:199:13: warning: cast from pointer to integer of different size 
[-Wpointer-to-int-cast]
  199 | srandom((unsigned int) (getpid() + rock + numplayers));
  | ^
engine.c:210:5: error: implicit declaration of function 'init_transcript'; did 
you mean 'WriteTranscript'? [-Wimplicit-function-declaration]
  210 | init_transcript(self);
  | ^~~
  | WriteTranscript
In file included from engine.c:7:
internal.h:3:26: error: implicit declaration of function 'log_text' 
[-Wimplicit-function-declaration]
3 | #define PrintMsg(msg)   (log_text(self, msg),\
  |  ^~~~
engine.c:213:9: note: in expansion of macro 'PrintMsg'
  213 | PrintMsg(_("Too many players requested.\n"));
  | ^~~~
engine.c: In function 'RunTurn':
engine.c:352:62: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
  352 | add_query(self, kx, Qu_CharmGesture, (char 
*)val);
  |  ^
engine.c:438:5: error: implicit declaration of function 'log_round_header' 
[-Wimplicit-function-declaration]
  438 | log_round_header(self);
  | ^~~~
engine.c: In function 'restrict_gestures':
engine.c:1016:49: warning: cast to pointer from integer of different size 
[-Wint-to-pointer-cast]
 1016 | add_query(self, wiznum, Qu_SetOffDelay, (char 
*)self->wiz[wiznum]->delay_bank);
  | ^
make[2]: *** [: engine.o] Error 1
make[2]: Leaving directory '/build/spellcast-1.0'
make[1]: *** [debian/rules:12: override_dh_auto_build] Error 2
make[1]: Leaving directory '/build/spellcast-1.0'
make: *** [debian/rules:9: build] Error 2


Andreas

Bug#1072453: marked as done (subtitlecomposer: FTBFS with ffmpeg 7.0: streamprocessor.cpp:277:25: error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named ‘channel_layout’; did you me

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 06:07:13 +
with message-id 
and subject line Bug#1072453: fixed in subtitlecomposer 0.8.1-2
has caused the Debian Bug report #1072453,
regarding subtitlecomposer: FTBFS with ffmpeg 7.0: streamprocessor.cpp:277:25: 
error: ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named 
‘channel_layout’; did you mean ‘ch_layout’?
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.)


-- 
1072453: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072453
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: subtitlecomposer
Version: 0.8.0-2
Severity: important
Tags: trixie sid ftbfs
Usertags: ffmpeg-7.0

Hi,

during a rebuild of the reverse dependencies for the transition to
ffmpeg 7.0, your package failed to build


Relevant part (hopefully):
> cd /<>/obj-aarch64-linux-gnu/src && /usr/bin/c++ 
> -DKCOREADDONS_LIB -DQT_CONCURRENT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB 
> -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_QML_LIB -DQT_WIDGETS_LIB 
> -DQT_XML_LIB -D_DEFAULT_SOURCE -D_GNU_SOURCE -D_LARGEFILE64_SOURCE 
> -I/<>/obj-aarch64-linux-gnu/src -I/<>/src 
> -I/<>/obj-aarch64-linux-gnu/src/subtitlecomposer-lib_autogen/include
>  -I/<>/src/widgets -I/usr/include/AL -isystem 
> /usr/include/aarch64-linux-gnu/qt5 -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtCore -isystem 
> /usr/lib/aarch64-linux-gnu/qt5/mkspecs/linux-g++ -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtWidgets -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtGui -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtWidgets/5.15.13 -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtWidgets/5.15.13/QtWidgets -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtGui/5.15.13 -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtGui/5.15.13/QtGui -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtCore/5.15.13 -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtCore/5.15.13/QtCore -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtQml -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtNetwork -isystem 
> /usr/include/KF5/KCoreAddons -isystem /usr/include/KF5 -isystem 
> /usr/include/KF5/KWidgetsAddons -isystem /usr/include/KF5/KTextWidgets 
> -isystem /usr/include/KF5/SonnetUi -isystem /usr/include/KF5/Sonnet -isystem 
> /usr/include/KF5/KI18n -isystem /usr/include/KF5/KCodecs -isystem 
> /usr/include/KF5/SonnetCore -isystem /usr/include/KF5/KIOCore -isystem 
> /usr/include/KF5/KIO -isystem /usr/include/KF5/KService -isystem 
> /usr/include/KF5/KConfig -isystem /usr/include/KF5/KConfigCore -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtDBus -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtConcurrent -isystem 
> /usr/include/KF5/KIOFileWidgets -isystem /usr/include/KF5/KIOWidgets -isystem 
> /usr/include/KF5/KIOGui -isystem /usr/include/KF5/KWindowSystem -isystem 
> /usr/include/KF5/KJobWidgets -isystem /usr/include/KF5/Solid -isystem 
> /usr/include/KF5/KCompletion -isystem /usr/include/KF5/KBookmarks -isystem 
> /usr/include/aarch64-linux-gnu/qt5/QtXml -isystem /usr/include/KF5/KItemViews 
> -isystem /usr/include/KF5/KXmlGui -isystem /usr/include/KF5/KConfigWidgets 
> -isystem /usr/include/KF5/KConfigGui -isystem /usr/include/KF5/KAuthWidgets 
> -isystem /usr/include/KF5/KAuthCore -isystem /usr/include/KF5/KAuth -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security 
> -mbranch-protection=standard -Wdate-time -D_FORTIFY_SOURCE=2 
> -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align 
> -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef 
> -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self 
> -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -std=gnu++11 
> -fvisibility=hidden -fvisibility-inlines-hidden -fPIC -MD -MT 
> src/CMakeFiles/subtitlecomposer-lib.dir/translate/translatedialog.cpp.o -MF 
> CMakeFiles/subtitlecomposer-lib.dir/translate/translatedialog.cpp.o.d -o 
> CMakeFiles/subtitlecomposer-lib.dir/translate/translatedialog.cpp.o -c 
> /<>/src/translate/translatedialog.cpp
> /<>/src/streamprocessor/streamprocessor.cpp: In member function 
> ‘bool SubtitleComposer::StreamProcessor::initAudio(int, const WaveFormat&)’:
> /<>/src/streamprocessor/streamprocessor.cpp:277:25: error: 
> ‘AVCodecContext’ {aka ‘struct AVCodecContext’} has no member named 
> ‘channel_layout’; did you mean ‘ch_layout’?
>   277 | if(!m_codecCtx->channel_layout)
>   | ^~
>   | ch_layout
> /<>/src/streamprocessor/streamprocessor.cpp:278:29: 

Processed: tagging 1072453

[Debian Bug Tracking System]

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

> tags 1072453 + pending
Bug #1072453 [src:subtitlecomposer] subtitlecomposer: FTBFS with ffmpeg 7.0: 
streamprocessor.cpp:277:25: error: ‘AVCodecContext’ {aka ‘struct 
AVCodecContext’} has no member named ‘channel_layout’; did you mean ‘ch_layout’?
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1075061: marked as done (haskell-libxml-sax: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 05:19:18 +
with message-id 
and subject line Bug#1075061: fixed in haskell-libxml-sax 0.7.5-14
has caused the Debian Bug report #1075061,
regarding haskell-libxml-sax: ftbfs with GCC-14
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.)


-- 
1075061: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075061
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:haskell-libxml-sax
Version: 0.7.5-13
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/haskell-libxml-sax_0.7.5-13_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
  +++ |+#include 
9 | 
  |
9 | 
  | ^

cbits/hslibxml-shim.c:44:21: error:
 warning: incompatible implicit declaration of built-in function ‘calloc’ 
[-Wbuiltin-declaration-mismatch]
   44 | user_data = calloc(1, sizeof(UserData));
  | ^~
   |
44 | user_data = calloc(1, sizeof(UserData));
   | ^

cbits/hslibxml-shim.c:44:21: error:
 note: include ‘’ or provide a declaration of ‘calloc’
   |
44 | user_data = calloc(1, sizeof(UserData));
   | ^
cbits/hslibxml-shim.c: In function ‘hslibxml_on_warning’:

cbits/hslibxml-shim.c:395:9: error:
 error: implicit declaration of function ‘free’ 
[-Wimplicit-function-declaration]
  395 | free(msg);
  | ^~~~
|
395 | free(msg);
| ^

cbits/hslibxml-shim.c:395:9: error:
 note: include ‘’ or provide a declaration of ‘free’
|
395 | free(msg);
| ^

cbits/hslibxml-shim.c:395:9: error:
 warning: incompatible implicit declaration of built-in function ‘free’ 
[-Wbuiltin-declaration-mismatch]
|
395 | free(msg);
| ^

cbits/hslibxml-shim.c:395:9: error:
 note: include ‘’ or provide a declaration of ‘free’
|
395 | free(msg);
| ^
cbits/hslibxml-shim.c: In function ‘hslibxml_on_error’:

cbits/hslibxml-shim.c:420:9: error:
 warning: incompatible implicit declaration of built-in function ‘free’ 
[-Wbuiltin-declaration-mismatch]
  420 | free(msg);
  | ^~~~
|
420 | free(msg);
| ^

cbits/hslibxml-shim.c:420:9: error:
 note: include ‘’ or provide a declaration of ‘free’
|
420 | free(msg);
| ^
`x86_64-linux-gnu-gcc' failed in phase `C Compiler'. (Exit code: 1)
-e: error: debian/hlibrary.setup build --builddir=dist-ghc returned exit code 1
 at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 877.
Debian::Debhelper::Dh_Lib::error("debian/hlibrary.setup build 
--builddir=dist-ghc returned exit"...) called at 
/usr/share/perl5/Debian/Debhelper/Dh_Lib.pm line 616
Debian::Debhelper::Dh_Lib::error_exitcode("debian/hlibrary.setup build 
--builddir=dist-ghc") called at /usr/share/perl5/Debian/Debhelper/Dh_Lib.pm 
line 479
Debian::Debhelper::Dh_Lib::doit("debian/hlibrary.setup", "build", 
"--builddir=dist-ghc") called at 
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 656
Debian::Debhelper::Buildsystem::Haskell::Recipes::build_recipe() called 
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--- End Message ---
--- Begin Message ---
Source: haskell-libxml-sax
Source-Version: 0.7.5-14
Done: Picca 

Bug#1061023: marked as done (svtplay-dl: FTBFS: ModuleNotFoundError: No module named 'distutils.core')

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 01:05:08 +
with message-id 
and subject line Bug#1061023: fixed in svtplay-dl 4.97.1-0.1
has caused the Debian Bug report #1061023,
regarding svtplay-dl: FTBFS: ModuleNotFoundError: No module named 
'distutils.core'
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.)


-- 
1061023: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1061023
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: svtplay-dl
Version: 3.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> argparse-manpage \
>   --project-name svtplay-dl \
>   --author 'Johan Andersson' \
>   --author-email 'j...@i19.se' \
>   --pyfile lib/svtplay_dl/utils/parser.py \
>   --function gen_parser \
>   --url https://svtplay-dl.se/ \
>   --output svtplay-dl.1
> Traceback (most recent call last):
>   File "/usr/bin/argparse-manpage", line 5, in 
> from build_manpages.cli import main
>   File "/usr/lib/python3/dist-packages/build_manpages/cli/__init__.py", line 
> 5, in 
> from build_manpages.build_manpage import ManPageWriter, get_parser
>   File "/usr/lib/python3/dist-packages/build_manpages/build_manpage.py", line 
> 10, in 
> from distutils.core import Command
> ModuleNotFoundError: No module named 'distutils.core'
> make[1]: *** [debian/rules:25: svtplay-dl.1] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/01/15/svtplay-dl_3.0-2_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: svtplay-dl
Source-Version: 4.97.1-0.1
Done: Alexandre Detiste 

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated svtplay-dl 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, 04 Aug 2024 02:29:49 +0200
Source: svtplay-dl
Architecture: source
Version: 4.97.1-0.1
Distribution: unstable
Urgency: medium
Maintainer: Olof Johansson 
Changed-By: Alexandre Detiste 
Closes: 1018643 1055578 1061023 1069936
Changes:
 svtplay-dl (4.97.1-0.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * New upstream version 4.97.1 (Closes: #1061023, #1055578)
   * Remove dependency on python3-mock (Closes: #1069936)
   * Replace python3-nose by python3-pytest (Closes: #1018643)
Checksums-Sha1:
 97e124cefabfb6362b820d324795d81442e3a2c2 2072 svtplay-dl_4.97.1-0.1.dsc
 50ce82ad9ae2317789a64ad49ad74c0d3e9f2095 128225 svtplay-dl_4.97.1.orig.tar.gz
 5cee6c4c431e6b2c2ef3bdac264028426d4d4ff3 4232 
svtplay-dl_4.97.1-0.1.debian.tar.xz
 79b6911890405fbee07e7ea5e2bdcf616dc35359 7470 
svtplay-dl_4.97.1-0.1_source.buildinfo
Checksums-Sha256:
 3b44324446c66dbc7d7e5c990839fa8092876fa5737c75f9d586b69866ff21df 2072 
svtplay-dl_4.97.1-0.1.dsc
 713d55f20719d2543360711a7b5b605b6d01b9574c657549c7794b777ab685b8 128225 
svtplay-dl_4.97.1.orig.tar.gz
 ee8c1a7b4ae75150ec3c21cb321a6f786b1586c6feea777a21220da630607217 4232 
svtplay-dl_4.97.1-0.1.debian.tar.xz
 93c7489958d75e458c25cd28cb134d75c73f529dfbca69ab1cce1294f07b90ae 7470 
svtplay-dl_4.97.1-0.1_source.buildinfo
Files:
 

Bug#1074643: marked as done (presets: FTBFS: ModuleNotFoundError: No module named 'imp')

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 00:54:49 +
with message-id 
and subject line Bug#1074643: fixed in presets 0.1.3-5
has caused the Debian Bug report #1074643,
regarding presets: FTBFS: ModuleNotFoundError: No module named 'imp'
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.)


-- 
1074643: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074643
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: presets
Version: 0.1.3-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240702 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_build
> I: pybuild base:311: /usr/bin/python3.11 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.11_presets/build/presets
> copying presets/version.py -> 
> /<>/.pybuild/cpython3_3.11_presets/build/presets
> copying presets/__init__.py -> 
> /<>/.pybuild/cpython3_3.11_presets/build/presets
> I: pybuild base:311: /usr/bin/python3 setup.py build 
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.12_presets/build/presets
> copying presets/version.py -> 
> /<>/.pybuild/cpython3_3.12_presets/build/presets
> copying presets/__init__.py -> 
> /<>/.pybuild/cpython3_3.12_presets/build/presets
> PYTHONPATH=. http_proxy='http://127.0.0.1:9/' python3 -m sphinx -N -bhtml 
> docs/ debian/html
> Running Sphinx v7.2.6
> 
> Configuration error:
> There is a programmable error in your configuration file:
> 
> Traceback (most recent call last):
>   File "/usr/lib/python3/dist-packages/sphinx/config.py", line 358, in 
> eval_config_file
> exec(code, namespace)  # NoQA: S102
> ^
>   File "/<>/docs/conf.py", line 64, in 
> import imp
> ModuleNotFoundError: No module named 'imp'
> 
> make[1]: *** [debian/rules:10: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2024/07/02/presets_0.1.3-4_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: presets
Source-Version: 0.1.3-5
Done: Josenilson Ferreira da Silva 

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

Debian distribution maintenance software
pp.
Josenilson Ferreira da Silva  (supplier of updated 
presets 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, 03 Aug 2024 20:54:04 -0300
Source: presets
Architecture: source
Version: 0.1.3-5
Distribution: unstable
Urgency: medium
Maintainer: Josenilson Ferreira da Silva 
Changed-By: Josenilson Ferreira da Silva 
Closes: 1074643
Changes:
 presets (0.1.3-5) unstable; urgency=medium
 .
   * debian/control: Bumped Standards-Version to 4.7.0
   * debian/patches: Fixed patch name and sphinx-doc build (Closes: #1074643)
   * debian/python-presets-doc.doc-base: Fixed package name in abstract metadata
Checksums-Sha1:
 f8c77c19b9f3d762768cce55de5b45633fb025d6 2092 presets_0.1.3-5.dsc
 41bf45437b8009328c722e93e4a55afc2b0dcce7 3396 presets_0.1.3-5.debian.tar.xz
 5e1c0ae95c7abc3177aca2deab8f71f153a0 9091 presets_0.1.3-5_source.buildinfo
Checksums-Sha256:
 797baeaf0b3bc96136beccf2da37187abfcc6343cf895c5c57f11e0953207d7d 2092 
presets_0.1.3-5.dsc
 

Bug#1039531: marked as done (autoconf2.64: Keep out of testing)

[Debian Bug Tracking System]

Your message dated Sun, 04 Aug 2024 00:44:17 +
with message-id 
and subject line Bug#1057046: Removed package(s) from unstable
has caused the Debian Bug report #1039531,
regarding autoconf2.64: Keep out of testing
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.)


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

Source: autoconf2.64
Version: 2.64+dfsg-1.1
Severity: serious

Please keep the obsolete autoconf2.64 out of testing.
--- End Message ---
--- Begin Message ---
Version: 2.64+dfsg-1.1+rm

Dear submitter,

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

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

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

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

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

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)--- End Message ---

Bug#1075488: scalapack: ftbfs with GCC-14

[Erich Eickmeyer]

reopen 1075488

I'm not entirely convinced this is fixed as 1) I don't see anything 
referencing gcc-14 in the upstream github issue, and 2) there has been 
no new upload of scalapack to actually fix this. Furthermore, we had a 
failed build due to GCC-14 in Ubuntu. Can we shed some light on why this 
was silently closed?

Bug#1075056: marked as done (gutenprint: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 23:50:03 +
with message-id 
and subject line Bug#1075056: fixed in gutenprint 5.3.4.20220624T01008808d602-3
has caused the Debian Bug report #1075056,
regarding gutenprint: ftbfs with GCC-14
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.)


-- 
1075056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gutenprint
Version: 5.3.4.20220624T01008808d602-2
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/gutenprint_5.3.4.20220624T01008808d602-2_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:41:
/usr/include/gimp-2.0/libgimp/gimpdrawable.h:52:16: note: declared here
   52 | GimpDrawable * gimp_drawable_get(gint32 
drawable_ID);
  |^
print.c:254:3: warning: ‘gimp_gamma’ is deprecated [-Wdeprecated-declarations]
  254 |   stp_set_float_parameter(gimp_vars.v, "AppGamma", gimp_gamma());
  |   ^~~
/usr/include/gimp-2.0/libgimp/gimp.h:348:16: note: declared here
  348 | gdoublegimp_gamma(void) G_GNUC_CONST;
  |^~
print.c:514:7: warning: ‘gimp_tile_cache_ntiles’ is deprecated 
[-Wdeprecated-declarations]
  514 |   gimp_tile_cache_ntiles ((drawable->height + gimp_tile_width () - 
1) /
  |   ^~
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:63:
/usr/include/gimp-2.0/libgimp/gimptile.h:60:9: note: declared here
   60 | voidgimp_tile_cache_ntiles (gulong ntiles);
  | ^~
print.c:517:7: warning: ‘gimp_tile_cache_ntiles’ is deprecated 
[-Wdeprecated-declarations]
  517 |   gimp_tile_cache_ntiles ((drawable->width + gimp_tile_width () - 
1) /
  |   ^~
/usr/include/gimp-2.0/libgimp/gimptile.h:60:9: note: declared here
   60 | voidgimp_tile_cache_ntiles (gulong ntiles);
  | ^~
print.c:539:3: warning: ‘gimp_drawable_detach’ is deprecated 
[-Wdeprecated-declarations]
  539 |   gimp_drawable_detach (drawable);
  |   ^~~~
/usr/include/gimp-2.0/libgimp/gimpdrawable.h:54:16: note: declared here
   54 | void   gimp_drawable_detach (GimpDrawable  
*drawable);
  |^~~~
make[4]: *** [Makefile:558: print.o] Error 1
make[4]: *** Waiting for unfinished jobs
print-image-gimp.c: In function ‘Image_GimpDrawable_new’:
print-image-gimp.c:155:3: warning: ‘gimp_pixel_rgn_init’ is deprecated: Use 
'gimp_drawable_get_buffer' instead [-Wdeprecated-declarations]
  155 |   gimp_pixel_rgn_init(&(im->rgn), drawable, 0, 0,
  |   ^~~
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:57,
 from print_gimp.h:41:
/usr/include/gimp-2.0/libgimp/gimppixelrgn.h:48:11: note: declared here
   48 | void  gimp_pixel_rgn_init   (GimpPixelRgn  *pr,
  |   ^~~
print-image-gimp.c:165:7: warning: ‘gimp_image_get_cmap’ is deprecated: Use 
'gimp_image_get_colormap' instead [-Wdeprecated-declarations]
  165 |   im->cmap = gimp_image_get_cmap(image_ID, &(im->ncolors));
  |   ^~
In file included from /usr/include/gimp-2.0/libgimp/gimp.h:47:
/usr/include/gimp-2.0/libgimp/gimpimage.h:49:16: note: declared here
   49 | guchar   

Bug#1071871: marked as done (amberol: FTBFS: unsatisfiable build-dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 22:19:48 +
with message-id 
and subject line Bug#1071871: fixed in amberol 0.10.3-4
has caused the Debian Bug report #1071871,
regarding amberol: FTBFS: unsatisfiable build-dependencies
to be marked as done.

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

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


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

Package: src:amberol
Version: 0.10.3-3
Severity: serious
Tags: ftbfs

Dear maintainer:

During a rebuild of all packages in unstable, your package failed to build:


[...]
Install main build dependencies (apt-based resolver)


Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-main-dummy : Depends: librust-ashpd-0.6+gtk4-dev
   Depends: librust-gstreamer-audio-0.21-dev 
but it is not installable
   Depends: librust-gstreamer-play-0.21-dev but 
it is not installable
   Depends: librust-gdk-pixbuf-0.18+v2-42-dev 
but it is not installable
   Depends: librust-gtk4-0.7+v4-10-dev but it 
is not installable
   Depends: librust-libadwaita-0.5+v1-4-dev but 
it is not installable
E: Unable to correct problems, you have held broken packages.
apt-get failed.
E: Package installation failed
Not removing build depends: cloned chroot in use



The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:

https://people.debian.org/~sanvila/build-logs/202405/

About the archive rebuild: The build was made on virtual machines
of type m6a.large and r6a.large from AWS, using sbuild and a
reduced chroot with only build-essential packages.

If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.

If this is really a bug in one of the build-depends, please use
reassign and affects, so that this is still visible in the BTS web
page for this package.

Thanks.
--- End Message ---
--- Begin Message ---
Source: amberol
Source-Version: 0.10.3-4
Done: Jeremy Bícha 

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

Debian distribution maintenance software
pp.
Jeremy Bícha  (supplier of updated amberol 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, 03 Aug 2024 17:47:45 -0400
Source: amberol
Built-For-Profiles: noudeb
Architecture: source
Version: 0.10.3-4
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME Maintainers 

Changed-By: Jeremy Bícha 
Closes: 1071871
Changes:
 amberol (0.10.3-4) unstable; urgency=medium
 .
   * Team upload
 .
   [ Jeremy Bícha ]
   * Cherry-pick many commits with build & bug fixes (Closes: #1071871)
   * Update Build-Depends
   * Use team standard debian/gbp.conf
   * Update Standards Version to 4.7.0
 .
   [ Arnaud Ferraris ]
   * d/watch: fix after GitLab changes
Checksums-Sha1:
 a7f03eb39724e396bb73982e752b56a4b88f8ead 2712 amberol_0.10.3-4.dsc
 632e3059e2e14558936d0099ed14bf51983d1b5b 42516 amberol_0.10.3-4.debian.tar.xz
 6c059ccc36959417fce3fb9e2b4a934e4dae8856 17045 
amberol_0.10.3-4_source.buildinfo
Checksums-Sha256:
 13b508f2ee714d5c17f60389d5b6717343b66ea90e2dc5b41571b6377288a78b 2712 
amberol_0.10.3-4.dsc
 

Bug#1077805: marked as done (adequate: Unexpected output from /usr/sbin/update-binfmts --display: " mask = ")

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 21:49:00 +
with message-id 
and subject line Bug#1077805: fixed in adequate 0.16.8
has caused the Debian Bug report #1077805,
regarding adequate: Unexpected output from /usr/sbin/update-binfmts --display: 
"mask = "
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.)


-- 
1077805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adequate
Version: 0.16.7
Severity: grave

The current version of adequate fails on any package for me, complaining
about unexpected output from update-binfmts:

,
| $ adequate ncurses-base
| 2024/08/02 17:20:41 Unexpected output from /usr/sbin/update-binfmts 
--display: "mask = "
| $ echo $?
| 1
| $ /usr/sbin/update-binfmts --display
| llvm-16-runtime.binfmt (enabled):
|  package = llvm-16-runtime
| type = magic
|   offset = 0
|magic = BC
| mask =
|  interpreter = /usr/bin/lli-16
| detector =
| python3.12 (enabled):
|  package = python3.12
| type = magic
|   offset = 0
|magic = \xcb\x0d\x0d\x0a
| mask =
|  interpreter = /usr/bin/python3.12
| detector =
| wine (enabled):
|  package = wine
| type = magic
|   offset = 0
|magic = MZ
| mask =
|  interpreter = /usr/bin/wine-auto
| detector =
`

Note the trailing space in the "mask" and "detector" lines, maybe this
is unexpected?


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

Kernel: Linux 6.1.102-nouveau (SMP w/2 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages adequate depends on:
ii  debconf  1.5.87
ii  libc62.39-6

Versions of packages adequate recommends:
ii  pkgconf  1.8.1-3

adequate suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: adequate
Source-Version: 0.16.8
Done: Serafeim Zanikolas 

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

Debian distribution maintenance software
pp.
Serafeim Zanikolas  (supplier of updated adequate 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, 03 Aug 2024 23:19:51 +0200
Source: adequate
Architecture: source
Version: 0.16.8
Distribution: unstable
Urgency: medium
Maintainer: Debian Adequate Maintainers 
Changed-By: Serafeim Zanikolas 
Closes: 1077706 1077805
Changes:
 adequate (0.16.8) unstable; urgency=medium
 .
   * Fix parsing of update-binfmts output (Closes: #1077805).
   * Suppress false positive broken-symlink tags, for files that are either
 missing or cannot be stat'ed (Closes: #1077706).
Checksums-Sha1:
 7902abbd80410d12d67256deb6aeb58c26601724 1893 adequate_0.16.8.dsc
 4fb0d04e0c7d20b0a19fdfbc98cc4a72d477e67f 40060 adequate_0.16.8.tar.xz
 f78d7527fe90d493079ba6578f3f4dc28b37fa7c 6756 adequate_0.16.8_amd64.buildinfo
Checksums-Sha256:
 76eaec142f6f97a291c10ec1aa99fa41ed7c5e12d1ac6cac06abef55d1818e1d 1893 
adequate_0.16.8.dsc
 e69158a5f540b64dfa43f6c4d6daa9b2f0bd7784fa712bb8c1c817aecb6c19c4 40060 
adequate_0.16.8.tar.xz
 c4b92d84639d97c8a6d5f7b4d64abc348f88eda7917fbb43b1f3b91c4eb0299b 6756 
adequate_0.16.8_amd64.buildinfo
Files:
 af17461f95475c0899317dbcd9251683 1893 utils optional adequate_0.16.8.dsc
 b44a40184c634cfbd2c62018c8432884 40060 utils optional adequate_0.16.8.tar.xz
 dab264aec52c91a76971467117e7770a 6756 utils optional 
adequate_0.16.8_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEA2RWqo7IwLCLSFYbT59tVQ7WEioFAmauopMACgkQT59tVQ7W
EirG+hAAs1+1yNK22KVQgiQHjicbmS2e+tbKZnBfR9w+cwGChCCyAJcFN3UpdomO
c4ScFRv3qtEme59+wwWMGZrT/FQUbq22uAMD/iKrJIk03oVvBZgFlo1IPB69tuK0
4L/kRqY+k0wFoq+az5d1Evneny33xHQUYkah82gzblhPYXwWQX4QVWpJMBVVc11g

Processed: Re: Bug#1077805: adequate: Unexpected output from /usr/sbin/update-binfmts --display: " mask = "

[Debian Bug Tracking System]

Processing control commands:

> tags -1 pending
Bug #1077805 [adequate] adequate: Unexpected output from 
/usr/sbin/update-binfmts --display: "mask = "
Added tag(s) pending.

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

Bug#1077805: adequate: Unexpected output from /usr/sbin/update-binfmts --display: " mask = "

[Serafeim Zanikolas]

Control: tags -1 pending

oh dear! thanks to both of you for the report


signature.asc
Description: PGP signature

Bug#1077366: marked as done (FTBFS: protoc-gen-go: unable to determine Go import path for "rpc.proto")

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 16:48:39 -0400
with message-id <134808fdead73d6c61c22e3287129...@tauware.de>
and subject line Fwd: 
mirrorbits_0.5.1+git20240203.4e34d9b+ds1-2.1_source.changes ACCEPTED into 
unstable
has caused the Debian Bug report #1077366,
regarding FTBFS: protoc-gen-go: unable to determine Go import path for 
"rpc.proto"
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.)


-- 
1077366: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077366
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mirrorbits
Version: 0.5.1+git20240203.4e34d9b+ds1-2
Severity: serious
Tags: ftbfs
Justification: FTBFS

The package mirrorbits has uninstallable build-dependencies. I've tried to work
around this by building it against golang-github-golang-protobuf-1-5-dev 
instead.

This is causing this error:

make[1]: Entering directory '/<>'
cd _build/src/github.com/etix/mirrorbits && \
find -name "*.pb.go" -delete -printf "removed %p\n" && \
protoc -I rpc 
--go_out=plugins=grpc,Mgoogle/protobuf/empty.proto=github.com/golang/protobuf/ptypes/empty,Mgoogle/protobuf/timestamp.proto=github.com/golang/protobuf/ptypes/timestamp:rpc
 rpc/rpc.proto
removed ./rpc/rpc.pb.go
protoc-gen-go: unable to determine Go import path for "rpc.proto"

Please specify either:
• a "go_package" option in the .proto source file, or
• a "M" argument on the command line.

See https://protobuf.dev/reference/go/go-generated#package for more information.

--go_out: protoc-gen-go: Plugin failed with status code 1.



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

Kernel: Linux 6.9.10-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
sbuild (Debian sbuild) 0.85.10 (30 May 2024) on x1.int.tauware.de

+==+
| mirrorbits 0.5.1+git20240203.4e34d9b+ds1-2.1 (amd64) Sun, 28 Jul 2024 
18:24:58 + |
+==+

Package: mirrorbits
Version: 0.5.1+git20240203.4e34d9b+ds1-2.1
Source Version: 0.5.1+git20240203.4e34d9b+ds1-2.1
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-bd552f0d-4ac4-4246-ae4a-30dd48c10751'
 with '<>'
I: NOTICE: Log filtering will replace 'build/mirrorbits-EhYJ94/resolver-m3SCyH' 
with '<>'

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

Get:1 http://127.0.0.1:3142/deb.debian.org/debian unstable InRelease [198 kB]
Get:2 http://127.0.0.1:3142/deb.debian.org/debian unstable/main 
Sources.diff/Index [63.6 kB]
Get:3 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 
Packages.diff/Index [63.6 kB]
Get:4 http://127.0.0.1:3142/deb.debian.org/debian unstable/main Sources 
T-2024-07-28-1404.33-F-2024-07-28-1404.33.pdiff [35.5 kB]
Get:4 http://127.0.0.1:3142/deb.debian.org/debian unstable/main Sources 
T-2024-07-28-1404.33-F-2024-07-28-1404.33.pdiff [35.5 kB]
Get:5 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 Packages 
T-2024-07-28-1404.33-F-2024-07-28-1404.33.pdiff [22.7 kB]
Get:5 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 Packages 
T-2024-07-28-1404.33-F-2024-07-28-1404.33.pdiff [22.7 kB]
Fetched 384 kB in 1s (370 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages will be upgraded:
  libgcrypt20 linux-libc-dev
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3197 kB of archives.
After this operation, 24.6 kB of additional disk space will be used.
Get:1 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 
libgcrypt20 amd64 1.11.0-5 [842 kB]
Get:2 http://127.0.0.1:3142/deb.debian.org/debian unstable/main amd64 
linux-libc-dev all 6.9.12-1 [2355 kB]
debconf: delaying package configuration, since apt-utils is not installed
Fetched 3197 kB in 0s (125 MB/s)
(Reading database ... 
(Reading database ... 5%
(Reading 

Bug#1072428: marked as done (lebiniou: FTBFS with ffmpeg 7.0: video.c:228:5: error: ‘avcodec_close’ is deprecated [-Werror=deprecated-declarations])

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 20:50:26 +
with message-id 
and subject line Bug#1072428: fixed in lebiniou 3.66.0-3
has caused the Debian Bug report #1072428,
regarding lebiniou: FTBFS with ffmpeg 7.0: video.c:228:5: error: 
‘avcodec_close’ is deprecated [-Werror=deprecated-declarations]
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.)


-- 
1072428: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1072428
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: lebiniou
Version: 3.66.0-2
Severity: important
Tags: trixie sid ftbfs
Usertags: ffmpeg-7.0

Hi,

during a rebuild of the reverse dependencies for the transition to
ffmpeg 7.0, your package failed to build


Relevant part (hopefully):
> gcc -DHAVE_CONFIG_H -I. -I../../..   -DWITH_WEBCAM -Wdate-time 
> -D_FORTIFY_SOURCE=2 -DNDEBUG -D_GNU_SOURCE -Wdate-time -D_FORTIFY_SOURCE=2 
> -fPIC -I../../../src -I../../../plugins/main/include -g -O2 
> -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -mbranch-protection=standard -Wextra 
> -Wno-unused-parameter -Wall -Werror -fomit-frame-pointer -std=c11 
> -fsigned-char -I/usr/include/glib-2.0 
> -I/usr/lib/aarch64-linux-gnu/glib-2.0/include -I/usr/include/sysprof-6 
> -pthread  -g -O2 -Werror=implicit-function-declaration 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security 
> -mbranch-protection=standard -c -o video_so-video.o `test -f 'video.c' || 
> echo './'`video.c
> video.c: In function ‘free_allocated’:
> video.c:228:5: error: ‘avcodec_close’ is deprecated 
> [-Werror=deprecated-declarations]
>   228 | avcodec_close(codec_ctx);
>   | ^
> In file included from video.c:20:
> /usr/include/aarch64-linux-gnu/libavcodec/avcodec.h:2387:5: note: declared 
> here
>  2387 | int avcodec_close(AVCodecContext *avctx);
>   | ^
> cc1: all warnings being treated as errors
> make[5]: *** [Makefile:453: video_so-video.o] Error 1


The full build log is available from:
https://people.debian.org/~sramacher/ffmpeg-7.0/lebiniou_arm64.build

ffmpeg 7.0 is available in experimental.

Cheers

-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: lebiniou
Source-Version: 3.66.0-3
Done: Sebastian Ramacher 

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

Debian distribution maintenance software
pp.
Sebastian Ramacher  (supplier of updated lebiniou 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, 03 Aug 2024 22:19:54 +0200
Source: lebiniou
Architecture: source
Version: 3.66.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Sebastian Ramacher 
Closes: 1072428
Changes:
 lebiniou (3.66.0-3) unstable; urgency=medium
 .
   * QA upload.
   * debian/patches: Build without -Werror (Closes: #1072428)
Checksums-Sha1:
 013feb83ac9f40d503f657dad3fd58618fbf1c69 1526 lebiniou_3.66.0-3.dsc
 de739e86c76fbfb93d2ce32db8ec5da2e0d2fbaf 6544 lebiniou_3.66.0-3.debian.tar.xz
 e9ec6591294a1ad1f888a96ff912cd8b881f624c 17735 
lebiniou_3.66.0-3_amd64.buildinfo
Checksums-Sha256:
 9f6e648e43eb4558959cd200b11ef27d469c0475537f801d1fe0e9321c708259 1526 
lebiniou_3.66.0-3.dsc
 00f9cc18656d91b0c8ef1ffaa96d00412c7e2f326f1b1434a18236eff42964bf 6544 
lebiniou_3.66.0-3.debian.tar.xz
 d3c85f1979251022fa8f12849c773aeb6bc3ef4f954bed2a98a0f9558544588c 17735 
lebiniou_3.66.0-3_amd64.buildinfo
Files:
 4b0be373b4ea3a468c0415b88da2187f 1526 graphics optional lebiniou_3.66.0-3.dsc
 38fdc3c39d9fc6f5169339e555f754df 6544 graphics optional 
lebiniou_3.66.0-3.debian.tar.xz
 8a3276234bed03c8ab046a16aa86c968 17735 graphics optional 
lebiniou_3.66.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYKAB0WIQRCYn6EHZln2oPh+pAhk2s2YA/NiQUCZq6R1gAKCRAhk2s2YA/N
iZ5VAP43xW1E6uk9mcjq4UEAZdmT9I7ydl/Qm37SfGJ2z+LQWAEAiT+4PmRNkH5+
EIg36qBNWJ6DtgQABpTfb5oFIPjzPgM=
=RnaV
-END PGP SIGNATURE-



pgphvwRDRfBlS.pgp

Processed: forw

[Debian Bug Tracking System]

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

> forwarded 1075675 https://github.com/xmrig/xmrig/issues/3526
Bug #1075675 [src:xmrig] xmrig: ftbfs with GCC-14
Set Bug forwarded-to-address to 'https://github.com/xmrig/xmrig/issues/3526'.
>
End of message, stopping processing here.

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

Bug#1077038: ipwatchd: introduces aliased file /lib/systemd/system/ipwatchd.service (DEP17)

[Michael Biebl]

[adding back #1077038 to CC]
Am 03.08.24 um 17:29 schrieb YunQiang Su:

在 2024-08-03星期六的 13:31 +0200，Michael Biebl写道：

On Thu, 25 Jul 2024 14:05:44 +0200 Helmut Grohne 
wrote:

Package: ipwatchd
Version: 1.3.0-1+nmu1
Severity: serious
Justification: do not introduce aliased files into trixie
X-Debbugs-Cc: YunQiang Su 
User: helm...@debian.org
Usertags: dep17m2
Filename: /lib/systemd/system/ipwatchd.service

Hi,



I am planing to upload a new version with this debdiff.
Any idea?


Looks ok to me.

Keep in mind that dh-sequence-movetousr is not a permanent solution.

Ideally upstream would use pkg-config as outlined by Helmut instead of 
hard-coding /lib/system in src/Makefile
diff -Nru ipwatchd-1.3.0/debian/changelog ipwatchd-1.3.0/debian/changelog
--- ipwatchd-1.3.0/debian/changelog 2024-07-14 17:59:30.0 +0800
+++ ipwatchd-1.3.0/debian/changelog 2024-08-03 23:10:58.0 +0800
@@ -1,3 +1,14 @@
+ipwatchd (1.3.0-1+nmu2) unstable; urgency=medium
+
+  * Build-depends on dh-sequence-movetousr to install systemd service to
+/usr/lib instead of /lib.  Closes: #1077038.
+  * Rewrite debian/rules with debhelper 7 override style.
+  * Pre-Depends on ${misc:Pre-Depends} instead of hardcoded
+init-system-helpers (>= 1.66).
+  * Refresh patch with -p ab --no-timestamps --no-index. 
+
+ -- YunQiang Su   Sat, 03 Aug 2024 23:10:58 +0800
+
 ipwatchd (1.3.0-1+nmu1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ipwatchd-1.3.0/debian/control ipwatchd-1.3.0/debian/control
--- ipwatchd-1.3.0/debian/control   2024-07-14 17:59:30.0 +0800
+++ ipwatchd-1.3.0/debian/control   2024-08-03 23:07:12.0 +0800
@@ -2,13 +2,13 @@
 Section: net
 Priority: optional
 Maintainer: Jaroslav Imrich 
-Build-Depends: debhelper-compat (= 13), libpcap-dev, libnet1-dev
+Build-Depends: debhelper-compat (= 13), dh-sequence-movetousr, libpcap-dev, 
libnet1-dev
 Standards-Version: 3.9.2
 Homepage: http://ipwatchd.sf.net
 
 Package: ipwatchd
 Architecture: linux-any
-Pre-Depends: init-system-helpers (>= 1.66)
+Pre-Depends: ${misc:Pre-Depends}
 Depends: ${shlibs:Depends}, ${misc:Depends}
 Description: IP conflict detection tool
  IPwatchD is a simple daemon that analyses all incoming ARP packets in order
diff -Nru ipwatchd-1.3.0/debian/patches/fix-cflags.diff 
ipwatchd-1.3.0/debian/patches/fix-cflags.diff
--- ipwatchd-1.3.0/debian/patches/fix-cflags.diff   2024-07-14 
17:59:30.0 +0800
+++ ipwatchd-1.3.0/debian/patches/fix-cflags.diff   2024-08-03 
23:10:58.0 +0800
@@ -1,7 +1,5 @@
-Index: ipwatchd-1.3.0/src/Makefile
-===
 ipwatchd-1.3.0.orig/src/Makefile
-+++ ipwatchd-1.3.0/src/Makefile
+--- a/src/Makefile
 b/src/Makefile
 @@ -1,8 +1,8 @@
  # IPwatchD - IP conflict detection tool for Linux
  # Copyright (C) 2007-2018 Jaroslav Imrich 
diff -Nru ipwatchd-1.3.0/debian/rules ipwatchd-1.3.0/debian/rules
--- ipwatchd-1.3.0/debian/rules 2024-07-14 17:59:30.0 +0800
+++ ipwatchd-1.3.0/debian/rules 2024-08-03 23:03:12.0 +0800
@@ -1,60 +1,19 @@
 #!/usr/bin/make -f
-# -*- makefile -*-
+include /usr/share/dpkg/buildtools.mk
 
-# Uncomment this to turn on verbose mode.
-#export DH_VERBOSE=1
-export DEB_BUILD_MAINT_OPTIONS=hardening=+all
-
-build: build-stamp
-
-build-stamp: 
-   dh_testdir
-   CPPFLAGS=`dpkg-buildflags --get CPPFLAGS` \
-   CFLAGS="`dpkg-buildflags --get CFLAGS` $$CPPFLAGS" \
-   LDFLAGS=`dpkg-buildflags --get LDFLAGS` \
-   CC=$(DEB_HOST_GNU_TYPE)-gcc \
-  $(MAKE) -C src
-   touch $@
-
-# Added just to remove lintian warning debian-rules-missing-recommended-target
-build-arch build-indep: build
-
-clean: 
-   dh_testdir
-   dh_testroot
-   rm -f build-stamp configure-stamp
+export DH_VERBOSE = 1
+export DEB_BUILD_MAINT_OPTIONS = hardening=+all
+export CC
+
+%:
+   dh $@
+
+override_dh_auto_clean:
$(MAKE) -C src distclean
-   dh_clean 
 
-install: build
-   dh_testdir
-   dh_testroot
-   dh_prep  
-   dh_installdirs
+override_dh_auto_build:
+   CFLAGS="$(CFLAGS) $(CPPFLAGS)" $(MAKE) -C src
+
+override_dh_auto_install:
$(MAKE) -C src DESTDIR=$(CURDIR)/debian/ipwatchd install
-   # Remove upstream manpages causing lintian error 
manpage-not-compressed-with-max-compression
-   rm $(CURDIR)/debian/ipwatchd/usr/share/man/man1/ipwatchd-script.1.gz
-   rm $(CURDIR)/debian/ipwatchd/usr/share/man/man5/ipwatchd.conf.5.gz
-   rm $(CURDIR)/debian/ipwatchd/usr/share/man/man8/ipwatchd.8.gz
-
-binary-indep: install
-
-binary-arch: install
-   dh_testdir
-   dh_testroot
-   dh_installchangelogs 
-   dh_installdocs
-   dh_installman debian/ipwatchd.8 debian/ipwatchd.conf.5 
debian/ipwatchd-script.1
-   dh_installinit
-   dh_link
-   dh_strip
-   dh_compress
-   dh_fixperms
-   dh_installdeb
-   dh_shlibdeps
-   dh_gencontrol
-   

Processed: minidlna: diff for NMU version 1.3.3+dfsg-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1072435 + pending
Bug #1072435 [src:minidlna] minidlna: FTBFS with ffmpeg 7.0: libav.h:177:36: 
error: ‘AVCodecParameters’ has no member named ‘channels’
Added tag(s) pending.

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

Bug#1072435: minidlna: diff for NMU version 1.3.3+dfsg-1.1

[Sebastian Ramacher]

Control: tags 1072435 + pending


Dear maintainer,

I've prepared an NMU for minidlna (versioned as 1.3.3+dfsg-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Cheers
-- 
Sebastian Ramacher
diff -Nru minidlna-1.3.3+dfsg/debian/changelog minidlna-1.3.3+dfsg/debian/changelog
--- minidlna-1.3.3+dfsg/debian/changelog	2024-01-28 14:30:31.0 +0100
+++ minidlna-1.3.3+dfsg/debian/changelog	2024-08-03 21:19:29.0 +0200
@@ -1,3 +1,13 @@
+minidlna (1.3.3+dfsg-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+
+  [ Diederik de Haas ]
+  * d/patches: Add 16-Add-compatibility-with-FFMPEG-7.0.patch to fix build
+with ffmpeg 7.0 (Closes: #1072435)
+
+ -- Sebastian Ramacher   Sat, 03 Aug 2024 21:19:29 +0200
+
 minidlna (1.3.3+dfsg-1) unstable; urgency=medium
 
   [ Barak A. Pearlmutter ]
diff -Nru minidlna-1.3.3+dfsg/debian/patches/16-Add-compatibility-with-FFMPEG-7.0.patch minidlna-1.3.3+dfsg/debian/patches/16-Add-compatibility-with-FFMPEG-7.0.patch
--- minidlna-1.3.3+dfsg/debian/patches/16-Add-compatibility-with-FFMPEG-7.0.patch	1970-01-01 01:00:00.0 +0100
+++ minidlna-1.3.3+dfsg/debian/patches/16-Add-compatibility-with-FFMPEG-7.0.patch	2024-08-03 21:14:04.0 +0200
@@ -0,0 +1,40 @@
+From 243cf2dd27ebcaf4ef1093c79b96077378d52018 Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Robert-Andr=C3=A9=20Mauchin?= 
+Date: Sat, 4 May 2024 18:36:58 +0200
+Subject: [PATCH] Add compatibility with FFMPEG 7.0
+Origin: other, https://sourceforge.net/u/eclipseo/minidlna/ci/243cf2dd27ebcaf4ef1093c79b96077378d52018/
+Bug-Debian: https://bugs.debian.org/1072435
+
+channel_layout has been replaced with ch_layout
+---
+ libav.h | 6 ++
+ 1 file changed, 6 insertions(+)
+
+diff --git a/libav.h b/libav.h
+index b69752c..fae094b 100644
+--- a/libav.h
 b/libav.h
+@@ -117,6 +117,8 @@ typedef AVMetadataTag AVDictionaryEntry;
+ # endif
+ #endif
+ 
++#define HAVE_CH_LAYOUT (LIBAVUTIL_VERSION_INT >= ((57<<16)+(28<<8)+100))
++
+ static inline int
+ lav_open(AVFormatContext **ctx, const char *filename)
+ {
+@@ -174,7 +176,11 @@ lav_get_interlaced(AVStream *s)
+ #define lav_codec_tag(s) s->codecpar->codec_tag
+ #define lav_sample_rate(s) s->codecpar->sample_rate
+ #define lav_bit_rate(s) s->codecpar->bit_rate
++#if HAVE_CH_LAYOUT
++#define lav_channels(s) s->codecpar->ch_layout.nb_channels
++#else
+ #define lav_channels(s) s->codecpar->channels
++#endif
+ #define lav_width(s) s->codecpar->width
+ #define lav_height(s) s->codecpar->height
+ #define lav_profile(s) s->codecpar->profile
+-- 
+2.45.2
+
diff -Nru minidlna-1.3.3+dfsg/debian/patches/series minidlna-1.3.3+dfsg/debian/patches/series
--- minidlna-1.3.3+dfsg/debian/patches/series	2024-01-28 14:25:31.0 +0100
+++ minidlna-1.3.3+dfsg/debian/patches/series	2024-08-03 21:14:04.0 +0200
@@ -6,3 +6,4 @@
 13-spelling-and-typos.patch
 14-autoupdate.patch
 15-thumbnails.patch
+16-Add-compatibility-with-FFMPEG-7.0.patch

Bug#1060587: marked as done (ledmon: Please switch Build-Depends to systemd-dev)

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 19:19:03 +
with message-id 
and subject line Bug#1060587: fixed in ledmon 0.97-1.1
has caused the Debian Bug report #1060587,
regarding ledmon: Please switch Build-Depends to systemd-dev
to be marked as done.

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

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


-- 
1060587: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060587
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ledmon
Version: 0.95-2
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: systemd-dev

Hi,

your package ledmon declares a Build-Depends on systemd and/or udev.

In most cases, this build dependency is added to get the paths that
are defined in udev.pc or systemd.pc (via pkgconfig).

Since systemd_253-2 [1], these two pkgconfig files have been split
into a separate package named systemd-dev. This package is arch:all,
so even available on non-Linux architectures, which will simplify the
installation of upstream provided service files / udev rules.

To not make existing source packages FTBFS, the systemd and udev
package have a Depends: systemd-dev. This dependency will be removed
at some point though before trixie is released. Once this happens,
this issue will be bumped to RC.

Please update your build dependencies accordingly at your earliest
convenience.

If all you need is the systemd.pc or udev.pc pkgconfig file, please
replace any systemd or udev Build-Depends with systemd-dev. In most
cases that should be sufficient. If your package needs further
resources from systemd or udev to build successfully, it's fine to
keep those Build-Depends in addition to systemd-dev.

To ease stable backports, a version of systemd with those changes is
provided via bookworm-backports.

In case you have further questions, please contact the systemd team
at .

On behalf of the systemd team, Michael

[1]
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/196 
--- End Message ---
--- Begin Message ---
Source: ledmon
Source-Version: 0.97-1.1
Done: Michael Biebl 

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

Debian distribution maintenance software
pp.
Michael Biebl  (supplier of updated ledmon 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: Wed, 17 Jul 2024 16:29:18 +0200
Source: ledmon
Architecture: source
Version: 0.97-1.1
Distribution: unstable
Urgency: medium
Maintainer: Hsieh-Tseng Shen 
Changed-By: Michael Biebl 
Closes: 1060587
Changes:
 ledmon (0.97-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Replace systemd Build-Depends with systemd-dev. (Closes: #1060587)
Checksums-Sha1:
 f4b018b2498c0651ea1527926436c62681679883 1906 ledmon_0.97-1.1.dsc
 25aa5bafb096e99fa5aaa67a0f8fd395ed014bc3 6680 ledmon_0.97-1.1.debian.tar.xz
 41333daf8bd0c6664033e063eab457fb29723c4d 5670 ledmon_0.97-1.1_source.buildinfo
Checksums-Sha256:
 48edbc942cf666e4c8e0354e1c8e7cabd0b58ac988dab8aefc8515574d1b0da1 1906 
ledmon_0.97-1.1.dsc
 e2d5a0f81f840c97f4c0464b1dca01d8d4c9b513681eacaa958549401490caa0 6680 
ledmon_0.97-1.1.debian.tar.xz
 38f48c194f5b793d477107bb633d39af9b420a9d6485ea848b85b1a96224eba6 5670 
ledmon_0.97-1.1_source.buildinfo
Files:
 2993f4e99384ebc34c84b7a86b9c9a0d 1906 admin optional ledmon_0.97-1.1.dsc
 585ea086779b0a46aeebf77d0154798f 6680 admin optional 
ledmon_0.97-1.1.debian.tar.xz
 6a4d945681a4071fcd0af52a6feada77 5670 admin optional 
ledmon_0.97-1.1_source.buildinfo
-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEECbOsLssWnJBDRcxUauHfDWCPItwFAmaugCMRHGJpZWJsQGRl
Ymlhbi5vcmcACgkQauHfDWCPItyMQQ/+N4Q7B/jNq68xZ5wpKGQfUsIkkqoOUmPH
HriGXXh+eeydWFcxxdrzuVKfmhVk5nLyb69FdNOtFSJ16ds120FCcBKNPD0ohC3g
G2gytQAyLCxgfnxkKh5MqmlV0YQ8lR+dbDZBrLtm4ZQYCO5Gti+SMMKWexIWWBbN
jB3oT9o4DlgwFIOjIK8izBFm5vcF2ROFiqov/6/g0V8WBAeFyRHVJrY00XFRNPPO
a1k6/8EW7zUmeGGmkboEBI7ag52ZfNw6Dh1oE1U19ueD09hudJe2pVW4XqMSAgax
H2/ZZfiN0f1Jkk5dnKAbgaymIkcjteRU6yGT6HfA7vPOCxMFeatsTsqkSBm1Pz0Y
iJd6dBwi6gO5OPjtE/AD3rdEgtmgEmG4H4gxHtZYOa4FZKdF5ClK5FIHDejA9F8D
4Xh13QZMhe9715rjDY9UIM1SE4ZbwIq4znWOrZqiPzIdGZzDK2amWL2cPUY60JiL

Processed: fixed 1060492 in 4.11.1-2.1, closing 1060492

[Debian Bug Tracking System]

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

> fixed 1060492 4.11.1-2.1
Bug #1060492 [src:freeipa] freeipa: Please switch Build-Depends to systemd-dev
Marked as fixed in versions freeipa/4.11.1-2.1.
> close 1060492
Bug #1060492 [src:freeipa] freeipa: Please switch Build-Depends to systemd-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: notfixed 1060469 in 4.11.1-2.1

[Debian Bug Tracking System]

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

> notfixed 1060469 4.11.1-2.1
Bug #1060469 {Done: Michael Biebl } [src:intel-hdcp] 
intel-hdcp: Please switch Build-Depends to systemd-dev
The source 'intel-hdcp' and version '4.11.1-2.1' do not appear to match any 
binary packages
No longer marked as fixed in versions freeipa/4.11.1-2.1.
> thanks
Stopping processing here.

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

Bug#1060570: fixed 1060570 in 0.0.99.3+git20230118+446d7bfdef6a-2.1, closing 1060570

[Michael Biebl]

fixed 1060570 0.0.99.3+git20230118+446d7bfdef6a-2.1
close 1060570 
thanks

Processed: notfixed 1065386 in 0.0.99.3+git20230118+446d7bfdef6a-2.1

[Debian Bug Tracking System]

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

> notfixed 1065386 0.0.99.3+git20230118+446d7bfdef6a-2.1
Bug #1065386 {Done: Michael Biebl } [src:anytun] anytun: 
Please switch Build-Depends to systemd-dev
The source 'anytun' and version '0.0.99.3+git20230118+446d7bfdef6a-2.1' do not 
appear to match any binary packages
No longer marked as fixed in versions 
golang-github-containers-toolbox/0.0.99.3+git20230118+446d7bfdef6a-2.1.
> thanks
Stopping processing here.

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

Processed: fixed 1060570 in 0.0.99.3+git20230118+446d7bfdef6a-2.1, closing 1060570

[Debian Bug Tracking System]

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

> fixed 1060570 0.0.99.3+git20230118+446d7bfdef6a-2.1
Bug #1060570 [src:golang-github-containers-toolbox] 
golang-github-containers-toolbox: Please switch Build-Depends to systemd-dev
Marked as fixed in versions 
golang-github-containers-toolbox/0.0.99.3+git20230118+446d7bfdef6a-2.1.
> close 1060570
Bug #1060570 [src:golang-github-containers-toolbox] 
golang-github-containers-toolbox: Please switch Build-Depends to systemd-dev
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: limit source to linux, tagging 1039883, tagging 1041893

[Debian Bug Tracking System]

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

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

> tags 1039883 + pending
Bug #1039883 [src:linux] linux: ext4 corruption with symlinks
Added tag(s) pending.
> tags 1041893 + pending
Bug #1041893 [src:linux] linux-config: Enable CONFIG_IONIC
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1077038: ipwatchd: introduces aliased file /lib/systemd/system/ipwatchd.service (DEP17)

[Michael Biebl]

Am 03.08.24 um 16:25 schrieb YunQiang Su:

在 2024-08-03星期六的 13:31 +0200，Michael Biebl写道：



I also noticed, that the package added a Pre-Depends on
init-system-helpers (>= 1.66) without a proper explanation why.



lintian warned about that when I didn't add it.


Can you quote the exact lintian warning?
Which version of lintian did you use?


Regards,
Michael


OpenPGP_signature.asc
Description: OpenPGP digital signature

Bug#1070184: marked as done (gnome-maps: Unable to start gnome-maps)

[Debian Bug Tracking System]

Your message dated Sat, 3 Aug 2024 19:25:00 +0100
with message-id 
and subject line Re: Bug#1070184: gnome-maps: Unable to start gnome-maps
has caused the Debian Bug report #1070184,
regarding gnome-maps: Unable to start gnome-maps
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.)


-- 
1070184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-maps
Version: 46.0-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: cqu...@arcor.de

I have recently upgraded my Debian testing and it comes with gnome-46.0-1. I am
using XFCE 4 desktop and when I try to start gnome-maps nothing happens. From
the command line nothing happens, it seems like frozen and after exactly 10
seconds the prompt returns but no window has appeared.


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

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

Versions of packages gnome-maps depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.40.0-4+b2
ii  geoclue-2.0  2.7.1-2+b1
ii  gir1.2-adw-1 1.5.0-1
ii  gir1.2-gdkpixbuf-2.0 2.42.10+dfsg-3+b3
ii  gir1.2-geoclue-2.0   2.7.1-2+b1
ii  gir1.2-geocodeglib-2.0   3.26.3-6+b2
ii  gir1.2-glib-2.0 [gir1.2-gobject-2.0] 1.78.1-15
ii  gir1.2-gtk-4.0   4.12.5+ds-3
ii  gir1.2-gweather-4.0  4.4.0-1
ii  gir1.2-pango-1.0 1.52.1+ds-1
ii  gir1.2-rest-1.0  0.9.1-6+b1
ii  gir1.2-secret-1  0.21.4-1+b1
ii  gir1.2-shumate-1.0   1.2~beta-3+b1
ii  gir1.2-soup-3.0  3.4.4-5+b1
ii  gir1.2-xdp-1.0   0.7.1-5+b1
ii  gjs  1.79.3-1
ii  libc62.37-18
ii  libcairo21.18.0-1+b1
ii  libglib2.0-0t64  2.78.4-7
ii  libglib2.0-bin   2.78.4-7
ii  libgtk-4-1   4.12.5+ds-3
ii  libjson-glib-1.0-0   1.8.0-2+b1
ii  libpango-1.0-0   1.52.1+ds-1
ii  libpangocairo-1.0-0  1.52.1+ds-1
ii  librsvg2-2   2.58.0+dfsg-1
ii  libshumate-1.0-1 1.2~beta-3+b1
ii  libxml2  2.9.14+dfsg-1.3+b3

gnome-maps recommends no packages.

gnome-maps suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 46.11-1

On Thu, 02 May 2024 at 02:48:02 +0200, Cesar Enrique Garcia Dabo wrote:
>  After further  investigation it turns out that my places.json which is
> under $HOME/.local/share/gnome-maps/places.json is the responsible for
> issue. If I remove that file then gnome-maps starts without problem. However
> that file has been written by gnome-maps in the first place.

This sounds like the fix was probably this change in 46.11 upstream:

Changes since 46.10
 - Fix crash on startup when unnamed favorites [were] previously saved

On Wed, 22 May 2024 at 00:03:31 +0200, Cesar Enrique Garcia Dabo wrote:
> I see that gnome-maps is now in version 46.11 in testing. I have tried that
> version and the bug is now fixed.
> 
> So as far as I am concern this bug can be closed.

Thanks, doing so now.

smcv--- End Message ---

Bug#1077587: still occurs (reply to Sylvestre Ledru ) (Bug#1077587: fixed in llvm-toolchain-18 1:18.1.8-8)

[Sylvestre Ledru]

Le 02/08/2024 à 12:40, Vincent Lefevre a écrit :
> On 2024-08-01 14:02:15 +0200, Vincent Lefevre wrote:
>> On 2024-07-30 09:39:08 +, Debian Bug Tracking System wrote:
>>> Changes:
>>>   llvm-toolchain-18 (1:18.1.8-8) unstable; urgency=medium
>>>   .
>>> * Fix breaks/replaces (Closes: #1077587)
>> Package: llvm-18-dev
>> Source: llvm-toolchain-18
>> Version: 1:18.1.8-8
>> Installed-Size: 334825
>> Maintainer: LLVM Packaging Team 
>> Architecture: amd64
>> Depends: libffi-dev, llvm-18 (= 1:18.1.8-8), libllvm18 (= 1:18.1.8-8), 
>> libncurses-dev, llvm-18-tools (= 1:18.1.8-8), libclang-cpp18 (= 1:18.1.8-8), 
>> libz3-dev, libxml2-dev
>> [...]
>>
>> There are no breaks/replaces. So, still the same error:
>>
>> Unpacking llvm-18-dev (1:18.1.8-8) over (1:18.1.8-5) ...
>> dpkg: error processing archive 
>> /tmp/apt-dpkg-install-fbXaHi/14-llvm-18-dev_1%3a18.1.8-8_amd64.deb 
>> (--unpack):
>>   trying to overwrite '/usr/lib/llvm-18/lib/libLLVM-18.so.1', which is also 
>> in package libllvm18:amd64 1:18.1.8-5
> The breaks/replaces have been added on libllvm18, while the issue
> is for llvm-18-dev (assuming that libLLVM-18.so.1 is now intended
> to be in llvm-18-dev).

pff, shame on me. I will fix it.


S

Bug#1077858: marked as done (rust-debian-analyzer FTBFS: error[E0277]: the trait bound `Result: Tree` is not satisfied)

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 17:51:40 +
with message-id 
and subject line Bug#1077858: fixed in rust-debian-analyzer 0.158.7-1
has caused the Debian Bug report #1077858,
regarding rust-debian-analyzer FTBFS: error[E0277]: the trait bound 
`Result: Tree` is not satisfied
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.)


-- 
1077858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-debian-analyzer
Version: 0.158.3-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=rust-debian-analyzer=0.158.3-1

...
error[E0277]: the trait bound `Result: 
Tree` is not satisfied
  --> src/publish.rs:72:26
   |
72 | check_clean_tree(wt, _tree(), subpath).unwrap();
   |   the trait `Tree` is not 
implemented for `Result`
   |
   = help: the following other types implement trait `Tree`:
 AppliedPatches
 MemoryTree
 PreviewTree
 RevisionTree
 WorkingTree
   = note: required for the cast from `` to ` Tree`
...
--- End Message ---
--- Begin Message ---
Source: rust-debian-analyzer
Source-Version: 0.158.7-1
Done: Peter Michael Green 

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

Debian distribution maintenance software
pp.
Peter Michael Green  (supplier of updated 
rust-debian-analyzer 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, 03 Aug 2024 17:28:08 +
Source: rust-debian-analyzer
Architecture: source
Version: 0.158.7-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1077858
Changes:
 rust-debian-analyzer (0.158.7-1) unstable; urgency=medium
 .
   * Team upload.
   * Package debian-analyzer 0.158.7 from crates.io using debcargo 2.6.1 
(Closes: #1077858)
   * Bump dependency on debian-control crate, older versions cause
 infinite recursion in debian_analyzer::vcs::{impl#0}::vcs_svn.
Checksums-Sha1:
 39a689db13735804bbfa054276e45f058d542733 3781 
rust-debian-analyzer_0.158.7-1.dsc
 a5851b27cb12580faa28a80b866c3b4c51039d77 40328 
rust-debian-analyzer_0.158.7.orig.tar.gz
 e1a85c69ea7af34a488c3c352e0953d853ec14ed 4096 
rust-debian-analyzer_0.158.7-1.debian.tar.xz
 e416c5e0ce5af9e5ce2f6e934a4c18eaf3918f53 33908 
rust-debian-analyzer_0.158.7-1_source.buildinfo
Checksums-Sha256:
 eb4415d0c5d8207a67046d219706dbf54d8aef55e6a31214a5da765ee7d0859e 3781 
rust-debian-analyzer_0.158.7-1.dsc
 d9e1a293def727c819af5616cd60603dc69191d3e0323860395051936dd6325b 40328 
rust-debian-analyzer_0.158.7.orig.tar.gz
 ed02ae49094874a3176aaa69178a701ed5bf1a92563ba945716e32fa83aa388f 4096 
rust-debian-analyzer_0.158.7-1.debian.tar.xz
 30b0d4ba2a81e320aa3320194d9e6ab2ab6e531b8992573d4ea08660cf18f454 33908 
rust-debian-analyzer_0.158.7-1_source.buildinfo
Files:
 46b3855537c13045b7aca25eb7175e92 3781 rust optional 
rust-debian-analyzer_0.158.7-1.dsc
 86feedd56e1f054fd2308b497547768a 40328 rust optional 
rust-debian-analyzer_0.158.7.orig.tar.gz
 44433d25a46a7de85116a94b222304ea 4096 rust optional 
rust-debian-analyzer_0.158.7-1.debian.tar.xz
 b97620babb0c6885b9888dea35a530cf 33908 rust optional 
rust-debian-analyzer_0.158.7-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmauavcUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/XsilA//RIujmPNrQXfF7nUQ7rxnbHbzCota
2B/iir5MFHno6X1Uc5WSv+Ck6Ma4V0yCjybpTacgelxKluwYQBJw+QEMD229ltbg
kSufPhNHSy46EKWZY1zVXFUtgfjVqEGVGyySwY4IV0/7Wp17vjAXZ5sO0ULc5MXU
xGUNZYYPchKfeYRn0Er5ROVgWkH8jtVXM0Ke8VcW+QEiM4LOk0Fl7Z5pXNb7f9lo
bVqRZhETI6+IwJPSAW/0d1E5pYnbQsy8x5gWfmNd8pqPtj6WGTm5GWu7ZFloWEWg
sQM4ME3PbW3D/1TbeXZt+NwcOpmhddmSIDKfEs1paDM95JOwU3Hg2UJT/opkTrK0
CK/LWaCN/vgByopCJPT7sLl9xN0JxUZ0TzkyblSPcKyUbyBioc583LDo7OHYV2Td
jhEPFDOWY/uzAdk4UGUm0dgghF5NxSHn1qtY7FQgrvUaqphzpxuvR54uzJpCff95
bLthsw+1P7RY8YzKROCiR0fsBXBAM5phmSl85jDNt8j1G7Jubs0Ir+9iR6nXnMXb

Bug#1077437: marked as done (photocollage: FTBFS: AttributeError: module 'distutils' has no attribute 'dep_util'. Did you mean: 'dir_util'?)

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 17:51:20 +
with message-id 
and subject line Bug#1077437: fixed in photocollage 1.4.7-0.1
has caused the Debian Bug report #1077437,
regarding photocollage: FTBFS: AttributeError: module 'distutils' has no 
attribute 'dep_util'. Did you mean: 'dir_util'?
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.)


-- 
1077437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077437
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: photocollage
Version: 1.4.5-0.2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240728 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=pybuild
>dh_update_autotools_config -O--buildsystem=pybuild
>dh_autoreconf -O--buildsystem=pybuild
>dh_auto_configure -O--buildsystem=pybuild
> I: pybuild base:311: python3.12 setup.py config 
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:311: /usr/bin/python3 setup.py build 
> /<>/setup.py:34: DeprecationWarning: Use shutil.which instead of 
> find_executable
>   if not distutils.spawn.find_executable("msgfmt"):
> Traceback (most recent call last):
>   File "/<>/setup.py", line 67, in 
> distutils.core.setup(
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 184, in setup
> return run_commands(dist)
>^^
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 200, in run_commands
> dist.run_commands()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 970, in run_commands
> self.run_command(cmd)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 974, in 
> run_command
> super().run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 989, in run_command
> cmd_obj.run()
>   File 
> "/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 
> 135, in run
> self.run_command(cmd_name)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
> 316, in run_command
> self.distribution.run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 974, in 
> run_command
> super().run_command(command)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 989, in run_command
> cmd_obj.run()
>   File "/<>/setup.py", line 49, in run
> if distutils.dep_util.newer(po, mo):
>^^
> AttributeError: module 'distutils' has no attribute 'dep_util'. Did you mean: 
> 'dir_util'?
> E: pybuild pybuild:389: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p 3.12 returned 
> exit code 13
> make: *** [debian/rules:4: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/07/28/photocollage_1.4.5-0.2_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: photocollage
Source-Version: 1.4.7-0.1
Done: Alexandre Detiste 

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated photocollage package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the 

Bug#1052108: marked as done (gnome-shell-extension-system-monitor: needs update for GNOME Shell 46)

[Debian Bug Tracking System]

Your message dated Sat, 3 Aug 2024 13:46:15 -0400
with message-id 

and subject line Re: gnome-shell-extension-system-monitor: needs update for 
GNOME Shell 45
has caused the Debian Bug report #1052108,
regarding gnome-shell-extension-system-monitor: needs update for GNOME Shell 46
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.)


-- 
1052108: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052108
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-system-monitor
Version: 40-6
Severity: important
Tags: trixie sid upstream
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-45

As with every 6-month GNOME Shell release cycle, extensions will need to
be updated for GNOME Shell 45, which is currently being prepared in
experimental. A porting guide is available here:
https://gjs.guide/extensions/upgrading/gnome-shell-45.html

For the 44 -> 45 transition, most or all extensions will need
incompatible code changes, because GNOME Shell has switched from
non-standard gjs modules ("const Foo = imports.gi.Foo") to ECMAScript
modules ("import Foo from 'gi://Foo'") and all extensions need to do
the same. This means most or all extensions will split into a branch
for Shell <= 44 (which might not be maintained upstream any more) and
a branch for Shell >= 45.

If not updated, this extension will have to be removed from testing for
the GNOME Shell 45 transition (I don't know when that will be). This
bug will be raised to serious severity when the transition is ready to
go ahead.

The upstream developer might already have made this change (I haven't
checked). If a new upstream version is compatible with Shell 45 but not
44, please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 40-7

Because gnome-shell-extensions now includes a system monitor
extension, I have turned this package into a transitional package. If
someone wants to package an alternate version, they will need to use a
separate source and binary package for it.

See https://bugs.debian.org/1077752

See also https://github.com/mgalgs/gnome-shell-system-monitor-applet/issues/89

Thank you,
Jeremy Bícha--- End Message ---

Bug#1075708: zsh: FTBFS with GCC-14

[Simon McVittie]

Control: tags -1 + patch

On Sat, 03 Aug 2024 at 17:56:30 +0100, Simon McVittie wrote:
> Unfortunately, while [the patch I sent earlier] fixes the issue that
> Matthias reported, it
> doesn't seem to be a complete solution to making zsh build successfully:
> there are at least two other reasons why it fails to build from source
> with `debuild -B`, described below.

> Hang during build-time tests

> missing files: obj/Src/Modules/*.h

Applying the attached patch, in addition to the one I sent earlier, seems
to be enough to get a successful build on a porterbox by fixing both of
the new issues that I mentioned.

This is from upstream, but I found it by looking at Arch Linux's patchset;
thanks are due to Christian Hesse, one of Arch's zsh maintainers.

I believe both
52383-Avoid-incompatible-pointer-types-in-terminfo-global.patch
(commit ab4d62eb975a4c4c51dd35822665050e2ddc6918 upstream) and
50641-use-int-main-in-test-C-codes-in-configure.patch
(commit 4c89849c98172c951a9def3690e8647dae76308f upstream)
are necessary.

smcv
From: Nicholas Vinson 
Date: Wed, 21 Sep 2022 09:22:11 +0900
Subject: 50641: use 'int main()' in test C-codes in configure

Origin: upstream, commit:ab4d62eb975a4c4c51dd35822665050e2ddc6918
Bug-Debian: https://bugs.debian.org/1075708
---
 aczsh.m4 | 64 -
 configure.ac | 94 ++--
 2 files changed, 72 insertions(+), 86 deletions(-)

diff --git a/aczsh.m4 b/aczsh.m4
index d2a47ba..27cc260 100644
--- a/aczsh.m4
+++ b/aczsh.m4
@@ -44,6 +44,7 @@ AC_DEFUN(zsh_64_BIT_TYPE,
 #include 
 #endif
 
+int
 main()
 {
   $1 foo = 0; 
@@ -118,7 +119,6 @@ AC_TRY_COMMAND($DLLD -o conftest1.$DL_EXT $LDFLAGS $DLLDFLAGS conftest1.o $LIBS
 AC_TRY_COMMAND($CC -c $CFLAGS $CPPFLAGS $DLCFLAGS conftest2.c 1>_MESSAGE_LOG_FD) &&
 AC_TRY_COMMAND($DLLD -o conftest2.$DL_EXT $LDFLAGS $DLLDFLAGS conftest2.o $LIBS 1>_MESSAGE_LOG_FD); then
 AC_RUN_IFELSE([AC_LANG_SOURCE([[
-#include 
 #ifdef HPUX10DYNAMIC
 #include 
 #define RTLD_LAZY BIND_DEFERRED
@@ -146,29 +146,30 @@ char *zsh_gl_sym_addr ;
 #define RTLD_GLOBAL 0
 #endif
 
+int
 main()
 {
 void *handle1, *handle2;
 void *(*zsh_getaddr1)(), *(*zsh_getaddr2)();
 void *sym1, *sym2;
 handle1 = dlopen("./conftest1.$DL_EXT", RTLD_LAZY | RTLD_GLOBAL);
-if(!handle1) exit(1);
+if(!handle1) return(1);
 handle2 = dlopen("./conftest2.$DL_EXT", RTLD_LAZY | RTLD_GLOBAL);
-if(!handle2) exit(1);
+if(!handle2) return(1);
 zsh_getaddr1 = (void *(*)()) dlsym(handle1, "${us}zsh_getaddr1");
 zsh_getaddr2 = (void *(*)()) dlsym(handle2, "${us}zsh_getaddr2");
 sym1 = zsh_getaddr1();
 sym2 = zsh_getaddr2();
-if(!sym1 || !sym2) exit(1);
-if(sym1 != sym2) exit(1);
+if(!sym1 || !sym2) return(1);
+if(sym1 != sym2) return(1);
 dlclose(handle1);
 handle1 = dlopen("./conftest1.$DL_EXT", RTLD_LAZY | RTLD_GLOBAL);
-if(!handle1) exit(1);
+if(!handle1) return(1);
 zsh_getaddr1 = (void *(*)()) dlsym(handle1, "${us}zsh_getaddr1");
 sym1 = zsh_getaddr1();
-if(!sym1) exit(1);
-if(sym1 != sym2) exit(1);
-exit(0);
+if(!sym1) return(1);
+if(sym1 != sym2) return(1);
+return(0);
 }
 ]])],[zsh_cv_shared_$1=yes],
 [zsh_cv_shared_$1=no],
@@ -200,7 +201,6 @@ AC_TRY_COMMAND($DLLD -o conftest1.$DL_EXT $LDFLAGS $DLLDFLAGS conftest1.o $LIBS
 AC_TRY_COMMAND($CC -c $CFLAGS $CPPFLAGS $DLCFLAGS conftest2.c 1>_MESSAGE_LOG_FD) &&
 AC_TRY_COMMAND($DLLD -o conftest2.$DL_EXT $LDFLAGS $DLLDFLAGS conftest2.o $LIBS 1>_MESSAGE_LOG_FD); then
 AC_RUN_IFELSE([AC_LANG_SOURCE([[
-#include 
 #ifdef HPUX10DYNAMIC
 #include 
 #define RTLD_LAZY BIND_DEFERRED
@@ -228,19 +228,19 @@ char *zsh_gl_sym_addr ;
 #define RTLD_GLOBAL 0
 #endif
 
-
+int
 main()
 {
 void *handle1, *handle2;
 int (*fred1)(), (*fred2)();
 handle1 = dlopen("./conftest1.$DL_EXT", RTLD_LAZY | RTLD_GLOBAL);
-if(!handle1) exit(1);
+if(!handle1) return(1);
 handle2 = dlopen("./conftest2.$DL_EXT", RTLD_LAZY | RTLD_GLOBAL);
-if(!handle2) exit(1);
+if(!handle2) return(1);
 fred1 = (int (*)()) dlsym(handle1, "${us}fred");
 fred2 = (int (*)()) dlsym(handle2, "${us}fred");
-if(!fred1 || !fred2) exit(1);
-exit((*fred1)() != 42 || (*fred2)() != 69);
+if(!fred1 || !fred2) return(1);
+return((*fred1)() != 42 || (*fred2)() != 69);
 }
 ]])],[zsh_cv_sys_dynamic_clash_ok=yes],
 [zsh_cv_sys_dynamic_clash_ok=no],
@@ -276,7 +276,6 @@ AC_TRY_COMMAND($DLLD -o conftest1.$DL_EXT $LDFLAGS $DLLDFLAGS conftest1.o $LIBS
 AC_TRY_COMMAND($CC -c $CFLAGS $CPPFLAGS $DLCFLAGS conftest2.c 1>_MESSAGE_LOG_FD) &&
 AC_TRY_COMMAND($DLLD -o conftest2.$DL_EXT $LDFLAGS $DLLDFLAGS conftest2.o $LIBS 1>_MESSAGE_LOG_FD); then
 AC_RUN_IFELSE([AC_LANG_SOURCE([[
-#include 
 #ifdef HPUX10DYNAMIC
 #include 
 #define RTLD_LAZY BIND_DEFERRED
@@ -304,17 +303,18 @@ char *zsh_gl_sym_addr ;
 #define RTLD_GLOBAL 0
 #endif
 
+int
 main()
 {
 void 

Processed: Re: Bug#1075708: zsh: FTBFS with GCC-14

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + patch
Bug #1075708 [src:zsh] zsh: ftbfs with GCC-14
Added tag(s) patch.

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

Bug#1074873: marked as done (cdogs-sdl: ftbfs with GCC-14)

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 17:19:21 +
with message-id 
and subject line Bug#1074873: fixed in cdogs-sdl 2.1.0+dfsg-2
has caused the Debian Bug report #1074873,
regarding cdogs-sdl: ftbfs with GCC-14
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.)


-- 
1074873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074873
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:cdogs-sdl
Version: 2.1.0+dfsg-1
Severity: important
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-14

[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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/cdogs-sdl_2.1.0+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.

To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html

[...]
cd /<>/obj-x86_64-linux-gnu/src/cdogs/yajl && /usr/bin/cc -DSTATIC 
-DYAJL_BUILD -I/<>/src -I/<>/src/cdogs 
-I/<>/src/. -I/<>/src/proto/nanopb 
-I/usr/include/SDL2 -I/<>/src/cdogs/.. 
-I/<>/obj-x86_64-linux-gnu/src/cdogs/yajl/../include/yajl/.. -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -finline-limit=1000 
-Wno-stringop-truncation -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/nanopb 
-g   -fsigned-char -Wall -W -Wstrict-prototypes -Wpointer-arith -Wcast-qual -g 
-freg-struct-return -std=gnu99 -Wshadow -C -Wno-error=format-overflow 
-Wno-error=stringop-overflow -Winline -Werror -MD -MT 
src/cdogs/yajl/CMakeFiles/yajl_s.dir/yajl_gen.c.o -MF 
CMakeFiles/yajl_s.dir/yajl_gen.c.o.d -o CMakeFiles/yajl_s.dir/yajl_gen.c.o -c 
/<>/src/cdogs/yajl/yajl_gen.c
[ 13%] Building C object src/cdogs/yajl/CMakeFiles/yajl.dir/yajl_buf.c.o
cd /<>/obj-x86_64-linux-gnu/src/cdogs/yajl && /usr/bin/cc -DSTATIC 
-DYAJL_BUILD -DYAJL_SHARED -I/<>/src -I/<>/src/cdogs 
-I/<>/src/. -I/<>/src/proto/nanopb 
-I/usr/include/SDL2 -I/<>/src/cdogs/.. 
-I/<>/obj-x86_64-linux-gnu/src/cdogs/yajl/../include/yajl/.. -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -finline-limit=1000 
-Wno-stringop-truncation -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/nanopb 
-g -fPIC   -fsigned-char -Wall -W -Wstrict-prototypes -Wpointer-arith 
-Wcast-qual -g -freg-struct-return -std=gnu99 -Wshadow -C 
-Wno-error=format-overflow -Wno-error=stringop-overflow -Winline -Werror -MD 
-MT src/cdogs/yajl/CMakeFiles/yajl.dir/yajl_buf.c.o -MF 
CMakeFiles/yajl.dir/yajl_buf.c.o.d -o CMakeFiles/yajl.dir/yajl_buf.c.o -c 
/<>/src/cdogs/yajl/yajl_
 buf.c
[ 14%] Building C object src/cdogs/yajl/CMakeFiles/yajl.dir/yajl_encode.c.o
cd /<>/obj-x86_64-linux-gnu/src/cdogs/yajl && /usr/bin/cc -DSTATIC 
-DYAJL_BUILD -DYAJL_SHARED -I/<>/src -I/<>/src/cdogs 
-I/<>/src/. -I/<>/src/proto/nanopb 
-I/usr/include/SDL2 -I/<>/src/cdogs/.. 
-I/<>/obj-x86_64-linux-gnu/src/cdogs/yajl/../include/yajl/.. -g 
-O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. 
-fstack-protector-strong -fstack-clash-protection -Wformat 
-Werror=format-security -fcf-protection -finline-limit=1000 
-Wno-stringop-truncation -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/nanopb 
-g -fPIC   -fsigned-char -Wall -W -Wstrict-prototypes -Wpointer-arith 
-Wcast-qual -g -freg-struct-return -std=gnu99 -Wshadow -C 
-Wno-error=format-overflow -Wno-error=stringop-overflow -Winline -Werror -MD 
-MT src/cdogs/yajl/CMakeFiles/yajl.dir/yajl_encode.c.o -MF 
CMakeFiles/yajl.dir/yajl_encode.c.o.d -o CMakeFiles/yajl.dir/yajl_encode.c.o -c 
/<>/src/cdogs/y
 ajl/yajl_encode.c
[ 14%] Building C object 

Processed: closing 1076441

[Debian Bug Tracking System]

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

> close 1076441
Bug #1076441 [python3-flasgger] python3-flasgger: syntax error while comparing 
versions
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1077022: marked as done (php-dompdf is no longer installable)

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 17:04:14 +
with message-id 
and subject line Bug#1077022: fixed in php-dompdf 3.0.0+dfsg-1
has caused the Debian Bug report #1077022,
regarding php-dompdf is no longer 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.)


-- 
1077022: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077022
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: php-dompdf
Version: 2.0.7+dfsg-1
Severity: serious

The following packages have unmet dependencies:
 php-dompdf : Depends: php-font-lib (< 1.0.0~~) but 1.0.0-1 is to be installed
  Depends: php-dompdf-svg-lib (< 1.0.0~~) but 1.0.0-1 is to be 
installed
--- End Message ---
--- Begin Message ---
Source: php-dompdf
Source-Version: 3.0.0+dfsg-1
Done: William Desportes 

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

Debian distribution maintenance software
pp.
William Desportes  (supplier of updated php-dompdf 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, 03 Aug 2024 18:36:12 +0200
Source: php-dompdf
Architecture: source
Version: 3.0.0+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PHP PEAR Maintainers 
Changed-By: William Desportes 
Closes: 1077022 1077445
Changes:
 php-dompdf (3.0.0+dfsg-1) unstable; urgency=medium
 .
   * New upstream version 3.0.0 (Closes: #1077022, Closes: #1077445)
   * Remove "gitmode=full" from d/watch
   * Update d/control version restrictions
   * Add a patch for PHPUnit 11
   * Add more depends for DEP-8 tests
   * No more need to re-build afm linked files: ttf2afm
   * Refresh patches for tests and runtime
Checksums-Sha1:
 addaf5468d1dc3a477567e50cc9d6db4addbbda3 2464 php-dompdf_3.0.0+dfsg-1.dsc
 bb3b6ebcba47456a12fdd8bb8aa4241585ff5433 1701960 
php-dompdf_3.0.0+dfsg.orig.tar.xz
 1f4864ce0374aa5968c604a5f06546f937e36dd2 17572 
php-dompdf_3.0.0+dfsg-1.debian.tar.xz
 70a737cc04a16822bb7f7c243090153135ec141d 13429 
php-dompdf_3.0.0+dfsg-1_source.buildinfo
Checksums-Sha256:
 3d8c992fef4d91fcfd52cd7d6f0f0e8c99ccf8af27a6f85e15eb5a6f5b41fb78 2464 
php-dompdf_3.0.0+dfsg-1.dsc
 9631318c5dc6c27fbc07bde61ad0890acc28e0b69398bd010435b0921ac19a9a 1701960 
php-dompdf_3.0.0+dfsg.orig.tar.xz
 9593ef333af929989eb8bf995d04d97a438d2d0907758d7279ea490090859d33 17572 
php-dompdf_3.0.0+dfsg-1.debian.tar.xz
 f89aa1bd85fb3dc7f497fe5b94241e16fcd15373422d84806eb4539228c56135 13429 
php-dompdf_3.0.0+dfsg-1_source.buildinfo
Files:
 4f1e06c1b0c66811678f89f4aeb5ae2d 2464 php optional php-dompdf_3.0.0+dfsg-1.dsc
 51525716855fed5eaf83b1793b137ee3 1701960 php optional 
php-dompdf_3.0.0+dfsg.orig.tar.xz
 fc1a1cb3b607d9ae88bed0fb63f238f7 17572 php optional 
php-dompdf_3.0.0+dfsg-1.debian.tar.xz
 b222c090200374288677b3dd2550f8e3 13429 php optional 
php-dompdf_3.0.0+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEExNkf3872tKPGU/14kKDvG4JRqIkFAmauXVcACgkQkKDvG4JR
qIlURg//RzuFVHSZrYdcaj66CoSIwFX0RiYXm+P5rtg9kec4RSi8e9wj+sX7EkHl
fkV1yLMzhd/gifzx/X8URdJY0njFczUU1gmiDfa8xZKsnt22bn5Y+fCLyfPyohcK
K/DcJfZreyu4LCgv2CP1bpY4noB8lWXEc5OM1/vaFYIyRyTw/qmozbatLVm+C03e
QYsatAelKWo6mNrfD9xWgwiJDj4I8ONFRTpO+s+Gl6IFNP2u6HnRYzPgg0hMhFCj
5NudirQBWObxFbzFQEAoi+AwLFYBQiWk64jH9tBvqdrulA/DoSFdmVsGrecCInjW
ZjrncI5YpESHt+UkeX+ABKycxIqTxNRzW9omIaFIsRKiAYwFWNM8QOUjap1YFVLK
yGOMHCaVXD4rMb0HnuqcOco1w7GO396CmLXiJXSDx5gyW9/pYGbZK0JYC7CAJ9MX
M24WsdP273ODc+4f87oc28tFbu9qyj87XV3n0gD/T18ZDEayWo2VYnsLedVHYAUH
31jlpY7X+R7Wd30ZnWDNdpdOX7yXlpgxUzazEbK4VF9VMgwFZrUZUjrYR3GaeDk8
c6gFeD5jdIPiibK55OuZKBcoXLArivu0rckps5I8Rnbj51LsMrJ5WC4Vg64X8Zzh
jo/fOFKxXMxOuAQ19GAnxkHpX8QcDduCLxcMJBupKJ3HUhZsD7c=
=xAO7
-END PGP SIGNATURE-



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

Bug#1077445: marked as done (php-dompdf: FTBFS: PHP Warning: require_once(/usr/share/php/Phenx/PhpFontLib/autoload.php): Failed to open stream: No such file or directory in /<>/vendor/aut

[Debian Bug Tracking System]

Your message dated Sat, 03 Aug 2024 17:04:14 +
with message-id 
and subject line Bug#1077445: fixed in php-dompdf 3.0.0+dfsg-1
has caused the Debian Bug report #1077445,
regarding php-dompdf: FTBFS: PHP Warning: 
require_once(/usr/share/php/Phenx/PhpFontLib/autoload.php): Failed to open 
stream: No such file or directory in /<>/vendor/autoload.php on 
line 5
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.)


-- 
1077445: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077445
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: php-dompdf
Version: 2.0.7+dfsg-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240728 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> phpabtpl --require-file ../lib/Cpdf.php composer.json > 
> debian/autoload.php.tpl
> mkdir -p vendor
> phpab --output vendor/autoload.php \
>   --template debian/autoload.php.tpl \
>   src/
> phpab %development% - Copyright (C) 2009 - 2024 by Arne Blankerts and 
> Contributors
> 
> Scanning directory src/
> 
> Autoload file vendor/autoload.php generated.
> 
> phpabtpl --require mockery/mockery --require-file ../vendor/autoload.php > 
> debian/autoload.tests.php.tpl
> Proceeding without a composer.json file.phpab --output tests/autoload.php \
>   --template debian/autoload.tests.php.tpl \
>   tests/
> phpab %development% - Copyright (C) 2009 - 2024 by Arne Blankerts and 
> Contributors
> 
> Scanning directory tests/
> 
> Autoload file tests/autoload.php generated.
> 
> phpunit --no-coverage --bootstrap tests/autoload.php
> PHP Warning:  require_once(/usr/share/php/Phenx/PhpFontLib/autoload.php): 
> Failed to open stream: No such file or directory in 
> /<>/vendor/autoload.php on line 5
> PHPUnit 9.6.20 by Sebastian Bergmann and contributors.
> 
> Error in bootstrap script: Error:
> Failed opening required '/usr/share/php/Phenx/PhpFontLib/autoload.php' 
> (include_path='.:/usr/share/php')
> #0 /<>/tests/autoload.php(44): require_once()
> #1 /usr/share/php/PHPUnit/Util/FileLoader.php(66): include_once('...')
> #2 /usr/share/php/PHPUnit/Util/FileLoader.php(49): 
> PHPUnit\Util\FileLoader::load()
> #3 /usr/share/php/PHPUnit/TextUI/Command.php(567): 
> PHPUnit\Util\FileLoader::checkAndLoad()
> #4 /usr/share/php/PHPUnit/TextUI/Command.php(345): 
> PHPUnit\TextUI\Command->handleBootstrap()
> #5 /usr/share/php/PHPUnit/TextUI/Command.php(114): 
> PHPUnit\TextUI\Command->handleArguments()
> #6 /usr/share/php/PHPUnit/TextUI/Command.php(99): 
> PHPUnit\TextUI\Command->run()
> #7 /usr/bin/phpunit(107): PHPUnit\TextUI\Command::main()
> #8 {main}
> make[1]: *** [debian/rules:60: override_dh_auto_test] Error 1


The full build log is available from:
http://qa-logs.debian.net/2024/07/28/php-dompdf_2.0.7+dfsg-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: php-dompdf
Source-Version: 3.0.0+dfsg-1
Done: William Desportes 

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

Debian distribution maintenance software
pp.
William Desportes  (supplier of updated php-dompdf 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, 03 Aug 2024 18:36:12 +0200
Source: php-dompdf

Processed: affects 1077854

[Debian Bug Tracking System]

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

> affects 1077854 transmission-gtk
Bug #1077854 [libcurl4t64] libcurl4t64: SIGPIPE leaks in some cases
Added indication that 1077854 affects transmission-gtk
> thanks
Stopping processing here.

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

Processed: affects 1077854

[Debian Bug Tracking System]

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

> affects 1077854 transmission-qt
Bug #1077854 [libcurl4t64] libcurl4t64: SIGPIPE leaks in some cases
Added indication that 1077854 affects transmission-qt
> thanks
Stopping processing here.

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

Processed: affects 1077854

[Debian Bug Tracking System]

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

> affects 1077854 transmission-daemon
Bug #1077854 [libcurl4t64] libcurl4t64: SIGPIPE leaks in some cases
Added indication that 1077854 affects transmission-daemon
> thanks
Stopping processing here.

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

Processed: bug 1077854 is forwarded to https://github.com/curl/curl/issues/14344

[Debian Bug Tracking System]

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

> forwarded 1077854 https://github.com/curl/curl/issues/14344
Bug #1077854 [libcurl4t64] libcurl4t64: SIGPIPE leaks in some cases
Set Bug forwarded-to-address to 'https://github.com/curl/curl/issues/14344'.
> thanks
Stopping processing here.

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

Bug#1075708: zsh: FTBFS with GCC-14

[Simon McVittie]

On Wed, 03 Jul 2024 at 12:50:04 +, Matthias Klose wrote:
> The package fails to build in a test rebuild on at least amd64 with
> gcc-14/g++-14, but succeeds to build with gcc-13/g++-13.
...
> ../../../Src/Modules/termcap.c:45:14: error: conflicting types for 
> ‘boolcodes’; have ‘char *[]’
>45 | static char *boolcodes[] = {
>   |  ^
> In file included from ../../Src/zshterm.h:1,
>  from ../../../Src/zsh_system.h:932,
>  from ./../../Src/zsh.mdh:15,
>  from ./termcap.mdh:15,
>  from ../../../Src/Modules/termcap.c:38:
> /usr/include/term.h:783:56: note: previous declaration of ‘boolcodes’ with 
> type ‘const char * const[]’
>   783 | extern NCURSES_EXPORT_VAR(NCURSES_CONST char * const ) boolcodes[];
>   |^

Please consider applying the attached patch, taken from upstream git.
gcc 14 also produces several compiler warnings which I think would be
useful to look into, but those don't break the build and hopefully don't
indicate serious bugs.

I tried compiling this in my usual build environment (sbuild inside
an amd64 Debian 12 VM) and on the amd64 porterbox barriere, and the
dh_auto_build step finishes successfully.

Unfortunately, while this patch fixes the issue that Matthias reported, it
doesn't seem to be a complete solution to making zsh build successfully:
there are at least two other reasons why it fails to build from source
with `debuild -B`, described below.

`debuild -A` (Architecture: all only) does succeed with the attached
patch.

Hang during build-time tests


During dh_auto_test, the test hangs for a significant time, with no
obvious CPU load, and this output:

>debian/rules override_dh_auto_test-arch
> make[1]: Entering directory '/home/smcv/zsh'
> if dpkg-architecture -qDEB_BUILD_ARCH_OS | grep -qv hurd; then \
> HOME="/home/smcv/zsh/obj/testhome" ZTST_verbose=1 dh_auto_test -B 
> obj; \
> fi
> cd obj && make -j4 test "TESTSUITEFLAGS=-j4 --verbose" VERBOSE=1
> make[2]: Entering directory '/home/smcv/zsh/obj'
> cd Test ; make check
> make[3]: Entering directory '/home/smcv/zsh/obj/Test'
> if test -n "ld"; then \
>   cd .. && DESTDIR= \
>   make MODDIR=`pwd`/Test/Modules install.modules > /dev/null; \
> fi
> if test -z "$ZTST_handler"; then \
>   ZTST_handler=runtests.zsh; \
> fi; \
> if ZTST_testlist="`for f in ../../Test/*.ztst; \
>do echo $f; done`" \
>  ZTST_srcdir="../../Test" \
>  ZTST_exe=../Src/zsh \
>  ../Src/zsh +Z -f ../../Test/$ZTST_handler; then \
>  stat=0; \
> else \
>  stat=1; \
> fi; \
> sleep 1; \
> rm -rf Modules .zcompdump; \
> exit $stat
> ../../Test/A01grammar.ztst: starting.
> Running test: Test skipping if ZTST_test_skip is set

This is reproducible on barriere.

I see that there is already a patch applied,
debian/patches/further-mitigate-test-suite-hangs.patch.
Perhaps it will be necessary to further further mitigate test-suite hangs...

Or perhaps the affected tests could be skipped without harming coverage
too much?

missing files: obj/Src/Modules/*.h
==

If I skip the build-time tests with DEB_BUILD_OPTIONS=nocheck, instead
I get this build failure:

>dh_install
> dh_install: warning: Cannot find (any matches for) "obj/Src/Modules/*.h" 
> (tried in ., debian/tmp)
>
> dh_install: warning: zsh-dev missing files: obj/Src/Modules/*.h
> dh_install: error: missing files, aborting

This is also reproducible on barriere. I don't know what has changed to
stop these headers from being generated.

I'm sorry I couldn't fully fix the build of this package, but I hope the
patch I attached is a useful step in the right direction.

smcv
From: Florian Weimer 
Date: Fri, 8 Dec 2023 21:58:07 +0100
Subject: 52383: Avoid incompatible pointer types in terminfo global variable
 checks

Origin: upstream, commit:https://sourceforge.net/p/zsh/code/ci/4c89849c98172c951a9def3690e8647dae76308f/
Bug-Debian: https://bugs.debian.org/1075708
---
 configure.ac | 12 ++--
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/configure.ac b/configure.ac
index f810052..928b467 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1771,27 +1771,27 @@ if test x$zsh_cv_path_term_header != xnone; then
   fi
 
   AC_MSG_CHECKING(if boolcodes is available)
-  AC_LINK_IFELSE([AC_LANG_PROGRAM([[$term_includes]], [[char **test = boolcodes; puts(*test);]])],[AC_DEFINE(HAVE_BOOLCODES) boolcodes=yes],[boolcodes=no])
+  AC_LINK_IFELSE([AC_LANG_PROGRAM([[$term_includes]], [[char **test = (char **)boolcodes; puts(*test);]])],[AC_DEFINE(HAVE_BOOLCODES) boolcodes=yes],[boolcodes=no])
   AC_MSG_RESULT($boolcodes)
 
   AC_MSG_CHECKING(if numcodes is available)
-  AC_LINK_IFELSE([AC_LANG_PROGRAM([[$term_includes]], [[char **test = numcodes; puts(*test);]])],[AC_DEFINE(HAVE_NUMCODES) numcodes=yes],[numcodes=no])
+