Bug#1041659: marked as done (src:vnlog: fails to migrate to testing for too long: uploader built arch:all binaries)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 05:34:04 +
with message-id 
and subject line Bug#1041659: fixed in vnlog 1.36-2
has caused the Debian Bug report #1041659,
regarding src:vnlog: fails to migrate to testing for too long: uploader built 
arch:all binaries
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.)


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

Source: vnlog
Version: 1.34-2
Severity: serious
Control: close -1 1.35-1
Tags: sid trixie pending
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:vnlog has been trying to migrate for 31 
days [2]. Hence, I am filing this bug.


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.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: vnlog
Source-Version: 1.36-2
Done: Dima Kogan 

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

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

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

Debian distribution maintenance software
pp.
Dima Kogan  (supplier of updated vnlog 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, 29 Jul 2023 21:59:59 -0700
Source: vnlog
Architecture: source
Version: 1.36-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Dima Kogan 
Closes: 1041659
Changes:
 vnlog (1.36-2) unstable; urgency=medium
 .
   * Source-only re-upload to fix bug (Closes: #1041659)
Checksums-Sha1:
 bfedee6549f8b8f154bfda8f8d07b0098a02d33e 2347 vnlog_1.36-2.dsc
 c8e928beea6973a40620a661346521a5bbc2618b 5936 vnlog_1.36-2.debian.tar.xz
 311af1bb059382ae37bf848dcd34df38c7e0fd53 9106 vnlog_1.36-2_amd64.buildinfo
Checksums-Sha256:
 3bf2164ec59019690e3d6c4c2643ff55a0b7c6abbf0157add8fd0fd1619bafaa 2347 
vnlog_1.36-2.dsc
 397ac723c28dd911434bf29d18ae4aca0319efa54123a3c5fd8afeb91016b630 5936 
vnlog_1.36-2.debian.tar.xz
 d53083ce20743252f8fbabb58a3748bf11549865c47c08d29aa1894533fcb7e5 9106 
vnlog_1.36-2_amd64.buildinfo
Files:
 814501ce1e074736aeeea7797fdb6176 2347 devel optional vnlog_1.36-2.dsc
 8890b50cfe30c055e8b689f606100037 5936 devel optional vnlog_1.36-2.debian.tar.xz
 08b140a3acf6f193cb980d070e1068d3 9106 devel optional 
vnlog_1.36-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEteL6GQ/fmv4hiInPrMfCzzCUEYgFAmTF8AIACgkQrMfCzzCU
EYhUBQ//Q/SZEy551L+mVjzL4CC/35m4NEQ4ib3fGSDmqlxFDcMUxVdlAgEitma+
a1tqBiqadH6vVvFMBI15IktHc+N5yNuTHw4M7MyCZBaoKuEWnh6+GYeneb+Xv1/M
toNUF8jwsvLA0/MrloZ2IKWp2jieDuk0pRADTlilXwbZlzYTu2LeTYxfQuvHNL00

Processed: forcibly merging 1037736 1042201

[Debian Bug Tracking System]

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

> forcemerge 1037736 1042201
Bug #1037736 [src:libsass] libsass: ftbfs with GCC-13
Bug #1042201 [src:libsass] libsass: FTBFS: dpkg-gensymbols: error: some symbols 
or patterns disappeared in the symbols file: see diff output below
Merged 1037736 1042201
> thanks
Stopping processing here.

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

Processed: forcibly merging 1037731 1042131

[Debian Bug Tracking System]

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

> forcemerge 1037731 1042131
Bug #1037731 [src:libncl] libncl: ftbfs with GCC-13
Bug #1042131 [src:libncl] libncl: FTBFS: dpkg-gensymbols: error: some symbols 
or patterns disappeared in the symbols file: see diff output below
Merged 1037731 1042131
> thanks
Stopping processing here.

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

Processed: State affects voikko-fi

[Debian Bug Tracking System]

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

> affects 1037663 + src:voikko-fi
Bug #1037663 [src:foma] foma: ftbfs with GCC-13
Added indication that 1037663 affects src:voikko-fi
>
End of message, stopping processing here.

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

Bug#1042295: marked as done (greetd: FTBFS: dh_dwz: error: dwz -mdebian/greetd/usr/lib/debug/.dwz/x86_64-linux-gnu/greetd.debug -M/usr/lib/debug/.dwz/x86_64-linux-gnu/greetd.debug -- debian/greetd/usr

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 10:52:45 +0900
with message-id 
and subject line Re: greetd: FTBFS: dh_dwz: error:…
has caused the Debian Bug report #1042295,
regarding greetd: FTBFS: dh_dwz: error: dwz 
-mdebian/greetd/usr/lib/debug/.dwz/x86_64-linux-gnu/greetd.debug 
-M/usr/lib/debug/.dwz/x86_64-linux-gnu/greetd.debug -- 
debian/greetd/usr/sbin/agreety debian/greetd/usr/sbin/greetd returned exit code 
1
to be marked as done.

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

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


-- 
1042295: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042295
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: greetd
Version: 0.9.0-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 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_installpam --name=greetd
> dh_installpam --name=greetd-greeter
> make[1]: Leaving directory '/<>'
>dh_perl -O--buildsystem=cargo
>dh_link -O--buildsystem=cargo
>dh_strip_nondeterminism -O--buildsystem=cargo
>dh_compress -O--buildsystem=cargo
>dh_fixperms -O--buildsystem=cargo
>dh_missing -O--buildsystem=cargo
>dh_dwz -a -O--buildsystem=cargo
> dwz: debian/greetd/usr/sbin/agreety: Couldn't find DIE at [2c8a] referenced 
> by DW_AT_abstract_origin from DIE at [1ba4d]
> dwz: debian/greetd/usr/sbin/greetd: Couldn't find DIE at [1036] referenced by 
> DW_AT_abstract_origin from DIE at [e12b]
> dwz: Too few files for multifile optimization
> dh_dwz: error: dwz 
> -mdebian/greetd/usr/lib/debug/.dwz/x86_64-linux-gnu/greetd.debug 
> -M/usr/lib/debug/.dwz/x86_64-linux-gnu/greetd.debug -- 
> debian/greetd/usr/sbin/agreety debian/greetd/usr/sbin/greetd returned exit 
> code 1
> dh_dwz: error: Aborting due to earlier error
> make: *** [debian/rules:8: binary] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/greetd_0.9.0-3_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=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 ---

Version: 0.9.0-4

Forgot to close the bug in the changelog, sorry.

--
Marc Dequènes--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1041351 important
Bug #1041351 [convertall] app crashes immediately
Severity set to 'important' from 'serious'
> tag 1041351 moreinfo
Bug #1041351 [convertall] app crashes immediately
Added tag(s) moreinfo.
>
End of message, stopping processing here.

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

Bug#1000077: marked as done (c-icap: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 00:05:07 +
with message-id 
and subject line Bug#177: fixed in c-icap 1:0.5.10-5
has caused the Debian Bug report #177,
regarding c-icap: depends on obsolete pcre3 library
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

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

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Source: c-icap
Source-Version: 1:0.5.10-5
Done: Boyuan Yang 

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

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

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

Debian distribution maintenance software
pp.
Boyuan Yang  (supplier of updated c-icap 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, 29 Jul 2023 19:43:03 -0400
Source: c-icap
Architecture: source
Version: 1:0.5.10-5
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Boyuan Yang 
Closes: 177
Changes:
 c-icap (1:0.5.10-5) unstable; urgency=medium
 .
   * QA upload.
   * debian/patches/0005-Backport-pcre2-support.patch: Backport upstream
 support for pcre2. (Closes: #177)
   * debian/patches/0006-OpenSSL-related-api-fixes.patch: Backport
 upstream misc fixes for OpenSSL deprecation.
   * 0007-Add-missing-_CI_ASSERT-macro-for-pcre2-patch.patch: Backport
 _CI_ASSERT macro, used in pcre2 patch.
   * debian/control: Bump Standards-Version to 4.6.2.
   * debian/control: Update dependency of lsb-base to avoid lintian
 error depends-on-obsolete-package.
   * debian/gbp.conf: Do not use build-area dir. This setup should be in
 user-level gbp conf, not package-level conf file.
   * debian/libicapapi5.symbols: Document added symbols.
Checksums-Sha1:
 3aad4297e75214ec258aadc843fcdf8121f289d3 2064 c-icap_0.5.10-5.dsc
 2901aa19c8c4b09b700164290942290c34132076 695044 c-icap_0.5.10.orig.tar.gz
 2a00e296a54d3d55266169e09974f5c77c759b2a 18356 c-icap_0.5.10-5.debian.tar.xz
 38463ff8b91759fce72cb1ef7f14c28196f1d520 7403 c-icap_0.5.10-5_amd64.buildinfo
Checksums-Sha256:
 5e42a63dba4c67f98329f5d6b77b27e4d49793bc6ad61d7dc51864bf651ea5ee 2064 
c-icap_0.5.10-5.dsc
 541d503354907f06d1d72fa90fffd031002f0f4346150fb7b2203ad5825ae49d 695044 
c-icap_0.5.10.orig.tar.gz
 2ae041c3434b0f47774480b95368bbf9b58c6ffaf5b3949750b544849bdc6473 18356 
c-icap_0.5.10-5.debian.tar.xz
 ff939d228ec050f21c04473286fa563292b11ef9a1fd6a4df205672b6ac197ff 7403 
c-icap_0.5.10-5_amd64.buildinfo
Files:
 a80b5f28eb24562fff3c8014e142a5e9 2064 net optional c-icap_0.5.10-5.dsc
 c8329684588a906d10a687e84ba4a478 695044 net optional c-icap_0.5.10.orig.tar.gz
 9a00900fe345204e9c8093e80e3ddbf7 18356 net optional 
c-icap_0.5.10-5.debian.tar.xz
 fa0a4a72e2cd008c3de1108b83c07672 7403 net optional 
c-icap_0.5.10-5_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmTFpKgACgkQwpPntGGC
Ws4v3RAAhx35P4AqddWMFAt/qWmeby9IAjbA+bI188lLlOz0FBXns/M8KgrNSTXm
r8Ctn5Tv9YPJAHFZppTkPubk4bja6/yzIeZX4uCc+fjJ9t5jGM4CPMtsosndBt/G

Bug#1042266: marked as done (bazel-rules-proto: FTBFS: make[1]: *** [debian/rules:13: execute_before_dh_link-indep] Error 1)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 22:48:56 +
with message-id 
and subject line Bug#1042266: fixed in bazel-rules-proto 4.0.0-3.20.0-3
has caused the Debian Bug report #1042266,
regarding bazel-rules-proto: FTBFS: make[1]: *** [debian/rules:13: 
execute_before_dh_link-indep] Error 1
to be marked as done.

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

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


-- 
1042266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: bazel-rules-proto
Version: 4.0.0-3.20.0-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 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 '/<>'
> jdupes -rl debian//usr
> 
> could not stat dir debian//usr
> No duplicates found.
> make[1]: *** [debian/rules:13: execute_before_dh_link-indep] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/bazel-rules-proto_4.0.0-3.20.0-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=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: bazel-rules-proto
Source-Version: 4.0.0-3.20.0-3
Done: Olek Wojnar 

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

Debian distribution maintenance software
pp.
Olek Wojnar  (supplier of updated bazel-rules-proto 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, 29 Jul 2023 17:56:34 -0400
Source: bazel-rules-proto
Architecture: source
Version: 4.0.0-3.20.0-3
Distribution: unstable
Urgency: high
Maintainer: Debian Bazel Team 
Changed-By: Olek Wojnar 
Closes: 1042266
Changes:
 bazel-rules-proto (4.0.0-3.20.0-3) unstable; urgency=high
 .
   * Correctly reference binary package in d/rules (Closes: #1042266)
Checksums-Sha1:
 53b4c8125d2ba72b12ff1be3e8983269ea513d29 2100 
bazel-rules-proto_4.0.0-3.20.0-3.dsc
 6e00fd970fa50ac3f9b0ace8cdeb195fbd3d97c4 2308 
bazel-rules-proto_4.0.0-3.20.0-3.debian.tar.xz
 d7a435a6b77210c41f634485b33d52f62882b921 6280 
bazel-rules-proto_4.0.0-3.20.0-3_amd64.buildinfo
Checksums-Sha256:
 55ed53b83a88f1eb39fd6a80737ba42798d3cc41ee6ad4eddeff6bc36f873177 2100 
bazel-rules-proto_4.0.0-3.20.0-3.dsc
 a2269ee84ec11dd0892ed20564f0bce2728ccd1e02577b87ae8164933359e97f 2308 
bazel-rules-proto_4.0.0-3.20.0-3.debian.tar.xz
 f2bba9116800c368b87651ef2a2e4f8428528bd32f0a5d9cd1e6dd9dc2e36727 6280 
bazel-rules-proto_4.0.0-3.20.0-3_amd64.buildinfo
Files:
 620415e0765dd9c7e2bfca096121b92f 2100 devel optional 
bazel-rules-proto_4.0.0-3.20.0-3.dsc
 0dc7e92115cf6dbf6fd7a1e91a34e0fe 2308 devel optional 
bazel-rules-proto_4.0.0-3.20.0-3.debian.tar.xz
 03d154024cfae06054b70ed39fcaa6ca 6280 devel optional 
bazel-rules-proto_4.0.0-3.20.0-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEELejiDiSiH9jtG0ynfYPUBqCdweQFAmTFjwMACgkQfYPUBqCd
weTK1w/9FIMtwO4VBUiEanrKzjy8OKZA4sUUjtJp7UCpTBLb012k8JNtuaAO73vD
IPrQL0m0H8Dq5rTUmBh9WeyeMXbQ+k2InrReI316QRn7rS82yUJ/eYkgdn478giq
JOZJSHjayBvxSMV3LIS8y8IHqm3qWmABxg1LZVqwavpPoL2LeqXv2XTGJr1Oyo1B
su2KSAsirDkkkAuRjToZTrnVv9sFSCW+qM6qNy9iPiTcoo0jNo9nnQp2UxRFbCYT
XK1GATjzKzgJ2cdMjgu20fHaVvbYDwdh2rBAHWFeQxcjEhrOna0cMiHj89DuLwUe
aenXAKBI7FBJp7J1Jc5ksUZHMyW45COY+lUqX/AkhHZkXjbnsW8J/3HUlF32Ijae
9f79k2JSz/MJGtaww+SK97FE/wNFnwB0FD1fIHyFPrkfnstr3F16qq64UanH66Us

Bug#1042537: manpages-fr-dev: trying to overwrite '/usr/share/man/fr/man3/uuid_generate_time_safe.3.gz', which is also in package util-linux-locales 2.39.1-3

[Vincent Lefevre]

Package: manpages-fr-dev
Version: 4.19.0-6
Severity: serious

There's still an issue about the move of man pages (and symlinks) to
util-linux-locales (see bugs 1037040 and 1042484 on the subject):

Unpacking manpages-fr-dev (4.19.0-6) over (4.19.0-3) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-McsQDG/8-manpages-fr-dev_4.19.0-6_all.deb (--unpack):
 trying to overwrite '/usr/share/man/fr/man3/uuid_generate_time_safe.3.gz', 
which is also in package util-linux-locales 2.39.1-3

This is also a symlink.

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

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

manpages-fr-dev depends on no packages.

manpages-fr-dev recommends no packages.

Versions of packages manpages-fr-dev suggests:
ii  glibc-doc 2.37-6
ii  man-db [man-browser]  2.11.2-3
ii  manpages-dev  6.03-2

-- no debconf information

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

Bug#1042408: marked as done (pyglet: requires update for ffmpeg 6.0)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 22:23:48 +
with message-id 
and subject line Bug#1042408: fixed in pyglet 2.0.9+ds-1
has caused the Debian Bug report #1042408,
regarding pyglet: requires update for ffmpeg 6.0
to be marked as done.

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

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


-- 
1042408: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042408
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyglet
Version: 1.5.27+ds-2
Severity: serious
Tag: sid trixie
X-Debbugs-Cc: sramac...@debian.org

python3-pyglet hard-codes dependencies of libraries from ffmpeg. As
ffmpeg is currently undergoing a transition due to SONAME bumps, please
update the package accordingly.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: pyglet
Source-Version: 2.0.9+ds-1
Done: Timo Röhling 

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

Debian distribution maintenance software
pp.
Timo Röhling  (supplier of updated pyglet 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, 29 Jul 2023 23:48:56 +0200
Source: pyglet
Architecture: source
Version: 2.0.9+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Timo Röhling 
Closes: 1042408
Changes:
 pyglet (2.0.9+ds-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version 2.0.9+ds
   * Update d/copyright
   * Refresh patches
   * Bump dependencies for ffmpeg 6 (Closes: #1042408)
   * Simplify d/rules and use pybuild-autopkgtest
   * Stop build-depending on obsolete packages
   * Bump Standards-Version to 4.6.2
Checksums-Sha1:
 9e162315b26b5c666ad1d1650d7827ece7daaad8 2274 pyglet_2.0.9+ds-1.dsc
 8ed1f6cce6d0e142cf8bda37c5b209781ad69f94 2786492 pyglet_2.0.9+ds.orig.tar.xz
 47490bc3b462342a1e69140d9105363d7733b3df 8532 pyglet_2.0.9+ds-1.debian.tar.xz
 9ddf6af0ed832e337b326db4c6cc9319887d1a25 12412 
pyglet_2.0.9+ds-1_amd64.buildinfo
Checksums-Sha256:
 29a545be04e7aafed438d8e4c360df005f964fc87c4bc809f3b041ede6b22a05 2274 
pyglet_2.0.9+ds-1.dsc
 62cb763730960264960ca548236855b874bec88f88d1aeb448a26bed3ca21866 2786492 
pyglet_2.0.9+ds.orig.tar.xz
 c0774b0d117974e7ec45ee56a9208ab4571b7d6e41483e4d3170c501aff950a5 8532 
pyglet_2.0.9+ds-1.debian.tar.xz
 25c1679bfde18f48f7daede2b5a58a3f950436704bb8f7ad7a61d694e48f00c6 12412 
pyglet_2.0.9+ds-1_amd64.buildinfo
Files:
 b62a76d7934081e1a3cd46b0d3edac3e 2274 python optional pyglet_2.0.9+ds-1.dsc
 988cf7b13eecc076535cd2b9d4368189 2786492 python optional 
pyglet_2.0.9+ds.orig.tar.xz
 f5e850ff1042aa1a519d16203a7c351c 8532 python optional 
pyglet_2.0.9+ds-1.debian.tar.xz
 09d632b23d5b77d8a39d2466b23c7088 12412 python optional 
pyglet_2.0.9+ds-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQHIBAEBCgAyFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmTFieYUHHJvZWhsaW5n
QGRlYmlhbi5vcmcACgkQ+C8H+466LVnRcQv+PAUIcd59YxCUTgOJriTbpdt9Dsi/
sEJJ+BOJayknVHMBMi635z272LKyyX/jEtHBOFFP5hVDEyi0s39riLidU6A9g9zp
2WKh/xE8PVN+2vcFrqQZC9QqyoOkWjyQyYk8qHLcMKUSexBYFhKDwfemG5V5LaNe
dY8uNL02uSGGhS60jYW0Jz2z10yM011aCWWKmpDqjx2VzWOR3qqsn9GWp80JZxV7
Goa4BamIw1RkGlP0mAImuVJTbZQwtqY5jt4hP0liel7b2XjPyiVKl1VwGvExWqB5
MT+PL7lk6wqU+qzOcQy8zux2YPGqoUYylyBrz4z7ZdoB/sY5uTY7rapl1mFVPD0d
Ys8mYK/ijQIBrU6GAmM1KLjNFuHlhAJdTnf+3AWlLaj7IO2WvlTvmwOiYxcwsD7E
Xpc3Fi3P/vPpeeLbA2nn6kp0ieUNAWlQ8GK9Pt/P7Poz+lA8A4asRMLFARdr+or7
dTY/NmXueF+torbRXqTVJpg//3znfuiVfynR
=AIyt
-END PGP SIGNATURE End Message ---

Bug#1042266: bazel-rules-proto: FTBFS: make[1]: *** [debian/rules:13: execute_before_dh_link-indep] Error 1

[Olek Wojnar]

Control: tag -1 pending


Hi Lucas and thanks for the bug report!


On 7/26/23 16:23, Lucas Nussbaum wrote:

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



Fixed and will be uploading shortly.


-Olek



OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: Bug#1042266: bazel-rules-proto: FTBFS: make[1]: *** [debian/rules:13: execute_before_dh_link-indep] Error 1

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042266 [src:bazel-rules-proto] bazel-rules-proto: FTBFS: make[1]: *** 
[debian/rules:13: execute_before_dh_link-indep] Error 1
Added tag(s) pending.

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

Processed: Bug#1042408 marked as pending in pyglet

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1042408 [src:pyglet] pyglet: requires update for ffmpeg 6.0
Added tag(s) pending.

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

Bug#1042408: marked as pending in pyglet

[Timo Röhling]

Control: tag -1 pending

Hello,

Bug #1042408 in pyglet 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/pyglet/-/commit/573fa24e71f6313ccb7e91a3b8ec8ab85d07b765


Bump dependencies for ffmpeg 6

Closes: #1042408


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1042408

Bug#1026042: trx: License is incompatible with that of up-coming ortp 5.2.0

[Kyle Robbertze]

On 2023/07/29 21:45, Bernhard Schmidt wrote:

Control: severity -1 serious

On 08/02/23 08:55 AM, Kyle Robbertze wrote:

Hi Kyle,


With the recently released version 5.2 ortp has been relicensed to GNU
AGPL-3+.  Since your package is GPL-2 it is my understanding that it
may not link in ortp 5.2 until it is relicensed to either GPL-3 or
AGPL-3.

As there has not been any development upstream in several years, I think we
will need to remove trx from Debian once the new ortp version is released.


ortp 5.2 has now been uploaded to unstable.


I'll file the RM bug shortly.

Cheers
Kyle

--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze
⢿⡄⠘⠷⠚⠋⠀ Debian Developer
⠈⠳⣄ https://wiki.debian.org/KyleRobbertze

Processed: Marking bugs as pending (fix committed to Salsa)

[Debian Bug Tracking System]

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

> tag 1041493 + pending
Bug #1041493 [src:wlroots] wlroots: FTBFFS with ffmpeg 6.0
Added tag(s) pending.
> tag 1027926 + pending
Bug #1027926 [libwlroots-examples] rootston is not included into wlroots 
anymore (package description)
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Re: Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

[Debian Bug Tracking System]

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

> tags 1038422 + pending security
Bug #1038422 [ntpsec] ntpsec: ntpd segmentation fault in 
libcrypto.so[7f6d3ecc5000+278000]
Added tag(s) security and pending.
> --
Stopping processing here.

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

Bug#1041789: RM: unison-2.51+4.13.1 -- RoQA; newer version packaged

[Vincent Lefevre]

On 2023-07-28 18:04:24 +0200, Stéphane Glondu wrote:
> Note that I would like to keep unison-2.52 (even if a newer version
> is packaged) at least in trixie, to allow synchronizing between
> bookworm and trixie.

Is this version really needed?

/usr/share/doc/unison-2.52/NEWS.md.gz says:

## Changes in 2.52.0

Released 2022-03-12

   * Feature negotiation, compatible with 2.51.
   * New archive format (independent of ocaml version, based on umarshal)
 Upgrade is automatic.
   * New wire protocol (independent of ocaml version, based on umarshal)
 New protocol is used if both sides are >= 2.52.0.
[...]

But you could check and decide later.

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

Bug#1042533: netdata: Please use packaged pako

[Bastien Roucariès]

Source: netdata
Severity: serious

Dear Maintainer,

pako is packaged for debian as node-pako and minify now under
/usr/share/javascript/pako

Moreover the first line of your missing source show a webpack line so your
source are not on the prefered form and thus this is a serious bug

You should also review the other js file and ask if needed help from debian
javascript team to package

Thanks

Bastien



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

Processed: Re: Bug#1026042: trx: License is incompatible with that of up-coming ortp 5.2.0

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1026042 [src:trx] trx: License is incompatible with that of up-coming ortp 
5.2.0
Severity set to 'serious' from 'important'

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

Bug#1042532: mediawiki: Vendoring a few javascript library without source

[Bastien Roucariès]

Source: mediawiki
Version: 1:1.39.4-2
Severity: serious
Justification: missing source

Dear Maintainer,

resources/lib/
(https://sources.debian.org/src/mediawiki/1:1.39.4-2/resources/lib/)

include a few library already packaged for debian.

Moreover some source are missing (I have only checked pako).

You could use the packaged library under debian

Bastien



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

Bug#1042531: novnc: Embded copy of node-pako

[Bastien Roucariès]

Source: novnc
Severity: serious
Justification: embed code copy

Dear Maintainer,

Your package include an embded code copy of node-pako (under vendor)

Could you please use the packaged node-pako ?

Thanks

bastien

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

Processed: severity of 1041810 is grave

[Debian Bug Tracking System]

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

> severity 1041810 grave
Bug #1041810 [src:librsvg] librsvg: CVE-2023-38633
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Processed: found 1041810 in 2.50.3+dfsg-1

[Debian Bug Tracking System]

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

> found 1041810 2.50.3+dfsg-1
Bug #1041810 [src:librsvg] librsvg: CVE-2023-38633
Marked as found in versions librsvg/2.50.3+dfsg-1.
> thanks
Stopping processing here.

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

Processed: forcibly merging 1037755 1042035

[Debian Bug Tracking System]

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

> forcemerge 1037755 1042035
Bug #1037755 {Done: Dennis Filder } [src:linphone] linphone: 
ftbfs with GCC-13
Bug #1037755 {Done: Dennis Filder } [src:linphone] linphone: 
ftbfs with GCC-13
Added tag(s) ftbfs.
Bug #1042035 [src:linphone] linphone: FTBFS: cpim-core-headers.cpp:275:16: 
error: identifier ‘requires’ is a keyword in C++20 [-Werror=c++20-compat]
Marked Bug as done
Marked as fixed in versions linphone/5.2.0-3.
Merged 1037755 1042035
> thanks
Stopping processing here.

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

Bug#1037226:

[Daniel Suchy]

Hello,
I can confirm this, this issue can be closed.

- Daniel

On 7/29/23 14:13, Ervin Hegedüs wrote:

Seems like this bug is fixed.

# apt install libnginx-mod-http-modsecurity --default-release bookworm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
   libnginx-mod-http-modsecurity
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 25.4 kB of archives.
After this operation, 196 kB of additional disk space will be used.
Get:1 http://ftp.hu.debian.org/debian  
bookworm/main amd64 libnginx-mod-http-modsecurity amd64 1.0.3-1+b2 [25.4 kB]

Fetched 25.4 kB in 0s (331 kB/s)
Selecting previously unselected package libnginx-mod-http-modsecurity.
(Reading database ... 57140 files and directories currently installed.)
Preparing to unpack 
.../libnginx-mod-http-modsecurity_1.0.3-1+b2_amd64.deb ...

Unpacking libnginx-mod-http-modsecurity (1.0.3-1+b2) ...
Setting up libnginx-mod-http-modsecurity (1.0.3-1+b2) ...
Processing triggers for nginx (1.22.1-9) ...
Triggering nginx reload ...

Jul 29 14:11:10 debian12 systemd[1]: Starting nginx.service - A high 
performance web server and a reverse proxy server...
Jul 29 14:11:10 debian12 nginx[1600]: 2023/07/29 14:11:10 [notice] 
1600#1600: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote: 
0/921/0)


Can we close this issue?


a.

On Sat, Jul 15, 2023 at 2:51 PM Tobias Frost > wrote:


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

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

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


-- 
tobi

Processed: clone

[Debian Bug Tracking System]

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

> clone 1042527 -1
Bug #1042527 [src:request-tracker5] request-tracker5: Include ckeditor 
minimified
Bug 1042527 cloned as bug 1042530
> reassign -1 src:request-tracker4
Bug #1042530 [src:request-tracker5] request-tracker5: Include ckeditor 
minimified
Bug reassigned from package 'src:request-tracker5' to 'src:request-tracker4'.
Ignoring request to alter found versions of bug #1042530 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1042530 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1042529: sogo: Multiple embdeded and minified javascript library

[Bastien Roucariès]

Source: sogo
Severity: serious
Tags: ftbfs security
Justification: FTBFS + security
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

https://sources.debian.org/src/sogo/5.8.4-1/UI/WebServerResources/js/vendor/
inlclude a few library precompiled and that seems outdated (bad from a security
point of view due to recent CVE for ckeditor)

Could you deembed and use packaged library

Thanks

Bastien



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

Bug#1042528: ldap-account-manager: Multiple embeded and minified javascript library

[Bastien Roucariès]

Source: ldap-account-manager
Severity: serious
Tags: ftbfs security
Justification: FTBFS + security

Dear Maintainer,

Ldap-account-manager include a few vendored and outdated (without security
support) javascript library

Could you remove this depends and use packaged library

Thanks

Processed: request-tracker5: Include ckeditor minimified

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + security
Bug #1042527 [src:request-tracker5] request-tracker5: Include ckeditor 
minimified
Added tag(s) security.

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

Bug#1042527: request-tracker5: Include ckeditor minimified

[Bastien Roucariès]

Source: request-tracker5
Severity: serious
Tags: ftbfs
Justification: FTBFS
Control: tags -1 + security

Dear Maintainer,

https://sources.debian.org/src/request-
tracker5/5.0.3+dfsg-3/share/static/RichText/

include ckeditor outdated (with CVE) and moreover minified

Could you use the packaged ckeditor.

Note also that I am going to package ckeditor5 (ckeditor 4 is EOL)

Bastien


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

Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12

[Ricardo Mones]

control: severity -1 important

Hi José Luis,

On Sun, 23 Jul 2023 14:22:34 +0200
José Luis González  wrote:

> control: severity -1 grave
> 
> Hi Ricardo,
> 
> > Right, but that doesn't deserve a 'grave' severity as only gsmtp
> > users are affected and no data is lost or security hole is
> > introduced. I've adjusted this accordingly.  
> 
> The definition of grave severity is:
> 
>   grave
>   makes the package in question unusable or mostly so, or
> causes data loss, or introduces a security hole allowing access to the
>   accounts of users who use the package.
> 
> This bug renders sylpheed unusuable or mostly so for me, so it is
> indeed a grave bug. I am restoring severity accordingly.

No, it's not. That "for me" you added is the part that is not mentioned
in the definition and that's a quite important difference: that the
package is unusable for _you_ doesn't make it unusable for _everybody_,
and that's what the definition mean when it says the package is
unusable.

Anybody not using Gmail can use Sylpheed without problems, for example,
so even if it makes unusable it for you, please keep severity as it
should be.

> > That has been reported on the list that downgrading to 3.7.0 fixes
> > the problem:
> > https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html  
> 
> > Can you check if downgrading fixes it?  
> 
> I wish I could check it but so far the only way I have to do so is
> installing from source. What I can confirm is the bug appeared when
> upgrading from version 3.7.0 to version 3.8.0~beta1-1.

Building Sylpheed 3.7.0 from source in Debian 12 is pretty simple, go to
some empty dir and run:

$ sudo apt install build-essential devscripts
$ sudo apt build-dep sylpheed
$ dget http://deb.debian.org/debian/pool/main/s/sylpheed/sylpheed_3.7.0-8.dsc
$ cd sylpheed-3.7.0/
$ dpkg-buildpackage -us -uc
$ cd ..
$ sudo dpkg -i sylpheed_3.7.0-8_amd64.deb

> I hope you understand this bug is preventing me from using sylpheed
> and so from reading and writing email, unless from gmail's web
> interface. I find of great concern that the bug is in Debian's new
> stable distribution: bookworm. If you know the bug is in version
> 3.8.0~beta1-1 I would suggest downgrading stable to 3.7.0 if you can
> manage to do so.

Yeah, I understand the situation is not funny for you. Fact is upstream
has still not dealt with this bug despite the time passed (months), so
there's no patch I can apply to current version. 

This fact joined with the increased slowness of upstream development
during the past years makes me wonder if it's still worth to maintain
Sylpheed within Debian.

regards,
-- 
 Ricardo Mones
 http://people.debian.org/~mones
 «Bank error in your favor. Collect $200.»

Processed: Re: Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1036799 [sylpheed] sylpheed: unable to send or read email after upgrading 
to Debian 12
Severity set to 'important' from 'grave'

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

Bug#1041162: marked as pending in autopkgtest

[Simon McVittie]

Control: tag -1 pending

Hello,

Bug #1041162 in autopkgtest 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/ci-team/autopkgtest/-/commit/39290ef8c66d4d2362720383643fd32cf88bf2a7


adt_testbed: restructure creation of pin file

$(apt-cache showsrc $pkg) shows all packages available in the source,
including Extra-Source-Only entries. This can lead to unintended
failures.

apt 2.0 and above support a src:$package format, so let's use that as
it also simplifies the logic a lot. Have a fallback for testbeds with
an older apt using dumpavail.

While we at it also generate the preference file on the host system
and copy it over instead of creating it in a shell command.

Closes: #1041162


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041162

Processed: Bug#1041162 marked as pending in autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041162 [autopkgtest] autopkgtest should ignore ESO entries for pinning
Ignoring request to alter tags of bug #1041162 to the same tags previously set

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

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

[Niko Tyni]

On Tue, Jul 18, 2023 at 06:24:32PM +0100, Simon McVittie wrote:

> SDL upstream have clarified that what libsdl-perl is doing here was
> never correct, so actually, this is more a libsdl-perl bug than a
> sdl12-compat bug. The result of SDL_SetVideoMode() is never meant to be
> freed by a library user, only internally by SDL itself.
> 
> I've sent a possible fix to https://github.com/PerlGameDev/SDL/pull/306,
> but I'm intentionally not tagging this bug +patch, because it badly needs
> reviewing by someone who has written XS bindings before (I'd never tried
> writing XS before today).

Hi, many thanks for your work on this.

I fear my expertise is not up to reviewing this properly, and SDL-Perl
upstream seems to be very quiet nowadays.

I'm copying the debian-perl list for some visibility, maybe somebody
there could have a look?

If not, I think I'd be OK just pushing your patch to sid and seeing
how it fares. It would be unfortunate to lose frozen-bubble from the
next release...
-- 
Niko Tyni   nt...@debian.org

Bug#974805: marked as done (beignet: Please upgrade to llvm-toolchain-11)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:25:03 +
with message-id 
and subject line Bug#1041805: Removed package(s) from unstable
has caused the Debian Bug report #974792,
regarding beignet: Please upgrade to llvm-toolchain-11
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.)


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the
archive, please upgrade to -11.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Version: 1.3.2-9+rm

Dear submitter,

as the package beignet 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/1041805

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#974792: marked as done (beignet: Please upgrade to llvm-toolchain-11)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:25:03 +
with message-id 
and subject line Bug#1041805: Removed package(s) from unstable
has caused the Debian Bug report #974792,
regarding beignet: Please upgrade to llvm-toolchain-11
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.)


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

Dear Maintainer,

As part of the effort to limit the number of llvm packages in the 
archive, please upgrade to -11.

Thanks,
Sylvestre
--- End Message ---
--- Begin Message ---
Version: 1.3.2-9+rm

Dear submitter,

as the package beignet 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/1041805

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#958623: marked as done (tcpcrypt: Build-Depends on deprecated dh-systemd which is going away)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:25:31 +
with message-id 
and subject line Bug#1041798: Removed package(s) from unstable
has caused the Debian Bug report #958623,
regarding tcpcrypt: Build-Depends on deprecated dh-systemd which is going away
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.)


-- 
958623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tcpcrypt
Severity: normal
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: dh-systemd-removal

Hi,

your package tcpcrypt declares a build dependency on dh-systemd.
dh-systemd was merged into debhelper in version 9.20160709 [1] and since
stretch, dh-systemd is an empty transitional package.

For bullseye we intend to drop this empty transitional package.

Once we drop dh-systemd, this bug report will become RC.

Please update your package accordingly. The change should be as simple as
replacing the build dependency on dh-systemd with a build dependency on
debhelper (>= 9.20160709).

Regards,
Michael

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670
--- End Message ---
--- Begin Message ---
Version: 0.5-1+rm

Dear submitter,

as the package tcpcrypt 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/1041798

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#1035845: marked as done (tcpcryptd fails to purge without adduser)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:25:31 +
with message-id 
and subject line Bug#1041798: Removed package(s) from unstable
has caused the Debian Bug report #1035845,
regarding tcpcryptd fails to purge without adduser
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.)


-- 
1035845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcpcryptd
Version: 0.5-1+b3
Severity: serious
User: jo...@debian.org
Usertags: adduserpurge
Control: tag -1 + patch
X-Debbugs-CC: jo...@debian.org

Hi,

the packages passwd and adduser are not part of the Essential:yes set.
According to policy §7.2 maintainer scripts cannot assume them being installed
when purging a package.  If one tries to remove this package without adduser
(which depends on passwd) installed, one gets:

--%<-
Purging configuration files for tcpcryptd (0.5-1+b3) ...
/var/lib/dpkg/info/tcpcryptd.postrm: 9: deluser: not found
dpkg: error processing package tcpcryptd (--purge):
 installed tcpcryptd package post-removal script subprocess returned error exit 
status 127
Errors were encountered while processing:
 tcpcryptd
-->%-

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833

For a discussion about use of adduser during purge, see #1035654.

To work around this problem, at least 125 source packages [codesearch] simply
ignore failures of calling the passwd or adduser tools during purge. The
following patch should fix this package by doing the same:

--%<-
diff -Nru tcpcrypt-0.5/debian/tcpcryptd.postrm 
tcpcrypt-0.5/debian/tcpcryptd.postrm
--- tcpcrypt-0.5/debian/tcpcryptd.postrm2016-04-01 23:45:55.0 
+0200
+++ tcpcrypt-0.5/debian/tcpcryptd.postrm2023-05-10 07:54:45.0 
+0200
@@ -6,7 +6,7 @@
 purge)
# add a debian-tcpcryptd user if one does not already exist
if getent passwd "$TCPCRYPT_USER" >/dev/null ; then
-deluser "$TCPCRYPT_USER"
+deluser "$TCPCRYPT_USER" || true
fi
 ;;
 esac
-->%-

If you prefer I can fix this via an NMU.

Thanks!

cheers, josch

[codesearch] 
https://codesearch.debian.net/search?q=del%28user%7Cgroup%29.*%5C%7C%5C%7C+true+path%3Adebian%2F.*%5C.%28pre%7Cpost%29rm%24=0
--- End Message ---
--- Begin Message ---
Version: 0.5-1+rm

Dear submitter,

as the package tcpcrypt 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/1041798

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#1035767: marked as done (gxmms2: Non-working maintainer address)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:24:12 +
with message-id 
and subject line Bug#1041729: Removed package(s) from unstable
has caused the Debian Bug report #1035767,
regarding gxmms2: Non-working maintainer address
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.)


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

Source: gxmms2
Version: 0.7.1-3
Severity: serious
Justification: Policy 3.3
X-Debbugs-Cc: bdr...@debian.org
X-Debbugs-Cc: and...@0x63.nu

Mail delivery failed: returning message to sender

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  r...@debian.org
Unrouteable address


Reporting-MTA: dns; mitropoulos.debian.org

Action: failed
Final-Recipient: rfc822;r...@debian.org
Status: 5.0.0
--- End Message ---
--- Begin Message ---
Version: 0.7.1-3+rm

Dear submitter,

as the package gxmms2 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/1041729

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#1035495: marked as done (tcpcryptd: fails to purge - command deluser in postrm not found)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:25:31 +
with message-id 
and subject line Bug#1041798: Removed package(s) from unstable
has caused the Debian Bug report #1035495,
regarding tcpcryptd: fails to purge - command deluser in postrm not found
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.)


-- 
1035495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035495
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: tcpcryptd
Version: 0.5-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package failed to purge due
to a command not found. According to policy 7.2 you cannot rely on the
depends being available during purge, only the essential packages are
available for sure.

The fix should be easy: your package is using adduser or deluser from
the adduser package, which is only priority important. Using useradd or
userdel from the passwd package (priority required) should fix this
problem.

There is ongoing discussion how to handle system users on package
removal, see https://bugs.debian.org/621833
Consensus seems to be not to remove system users (to avoid reusing UIDs
which could grant access to the wrong files) but to "lock" them (where
"locking"/"unlocking" is not yet precisely defined). Until that has
been decided it should be sufficient to have the postrm script ignore
any errors from deluser:
  deluser ... || true

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

0m17.5s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp8wigy40m', 'dpkg', '--purge', 'tcpcryptd']
0m17.5s DUMP: 
  (Reading database ... 8066 files and directories currently installed.)
  Purging configuration files for tcpcryptd (0.5-1+b3) ...
  /var/lib/dpkg/info/tcpcryptd.postrm: 9: deluser: not found
  dpkg: error processing package tcpcryptd (--purge):
   installed tcpcryptd package post-removal script subprocess returned error 
exit status 127
  Errors were encountered while processing:
   tcpcryptd
0m17.5s ERROR: Command failed (status=1): ['chroot', 
'/srv/piuparts.debian.org/tmp/tmp8wigy40m', 'dpkg', '--purge', 'tcpcryptd']


cheers,

Andreas


tcpcryptd_0.5-1+b3.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Version: 0.5-1+rm

Dear submitter,

as the package tcpcrypt 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/1041798

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#994214: marked as done (nomad FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:18:50 +
with message-id 
and subject line Bug#1041700: Removed package(s) from unstable
has caused the Debian Bug report #994214,
regarding nomad FTBFS in unstable
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.)


-- 
994214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994214
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nomad
Version: 0.12.10+dfsg1-3
Severity: serious
Justification: FTBFS
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu impish

Hi Dmitry,

The nomad package fails to build from source in Ubuntu, so in the process of
investigating this build failure I confirmed that it also fails to build in
Debian unstable:

[...]
# github.com/hashicorp/nomad/drivers/shared/executor
src/github.com/hashicorp/nomad/drivers/shared/executor/executor_universal_linux.go:125:36:
 cannot use groups (type *configs.Cgroup) as type *configs.Resources in 
argument to freezer.Set
src/github.com/hashicorp/nomad/drivers/shared/executor/executor_universal_linux.go:137:37:
 cannot use groups (type *configs.Cgroup) as type *configs.Resources in 
argument to freezer.Set
src/github.com/hashicorp/nomad/drivers/shared/executor/executor_universal_linux.go:159:36:
 cannot use groups (type *configs.Cgroup) as type *configs.Resources in 
argument to freezer.Set
[...]
dh_auto_build: error: cd _build && go install -trimpath -v -p 12 -a -tags 
"release ui nonvidia" github.com/hashicorp/nomad github.com/hashicorp/nomad/acl 
github.com/hashicorp/nomad/api github.com/hashicorp/nomad/api/contexts 
github.com/hashicorp/nomad/api/internal/testutil 
github.com/hashicorp/nomad/api/internal/testutil/discover 
github.com/hashicorp/nomad/api/internal/testutil/freeport 
github.com/hashicorp/nomad/client github.com/hashicorp/nomad/client/allocdir 
github.com/hashicorp/nomad/client/allocdir/input 
github.com/hashicorp/nomad/client/allochealth 
github.com/hashicorp/nomad/client/allocrunner 
github.com/hashicorp/nomad/client/allocrunner/interfaces 
github.com/hashicorp/nomad/client/allocrunner/state 
github.com/hashicorp/nomad/client/allocrunner/taskrunner 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/getter 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/interfaces 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/restarts 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/state 
github.com/hashicorp/nomad/client/allocrunner/taskrunner/template 
github.com/hashicorp/nomad/client/allocwatcher 
github.com/hashicorp/nomad/client/config 
github.com/hashicorp/nomad/client/consul 
github.com/hashicorp/nomad/client/devicemanager 
github.com/hashicorp/nomad/client/devicemanager/state 
github.com/hashicorp/nomad/client/dynamicplugins 
github.com/hashicorp/nomad/client/fingerprint 
github.com/hashicorp/nomad/client/interfaces 
github.com/hashicorp/nomad/client/lib/fifo 
github.com/hashicorp/nomad/client/lib/nsutil 
github.com/hashicorp/nomad/client/lib/streamframer 
github.com/hashicorp/nomad/client/logmon 
github.com/hashicorp/nomad/client/logmon/logging 
github.com/hashicorp/nomad/client/logmon/proto 
github.com/hashicorp/nomad/client/pluginmanager 
github.com/hashicorp/nomad/client/pluginmanager/csimanager 
github.com/hashicorp/nomad/client/pluginmanager/drivermanager 
github.com/hashicorp/nomad/client/pluginmanager/drivermanager/state 
github.com/hashicorp/nomad/client/servers 
github.com/hashicorp/nomad/client/state github.com/hashicorp/nomad/client/stats 
github.com/hashicorp/nomad/client/structs 
github.com/hashicorp/nomad/client/taskenv 
github.com/hashicorp/nomad/client/testutil 
github.com/hashicorp/nomad/client/vaultclient 
github.com/hashicorp/nomad/command github.com/hashicorp/nomad/command/agent 
github.com/hashicorp/nomad/command/agent/consul 
github.com/hashicorp/nomad/command/agent/event 
github.com/hashicorp/nomad/command/agent/host 
github.com/hashicorp/nomad/command/agent/monitor 
github.com/hashicorp/nomad/command/agent/pprof 
github.com/hashicorp/nomad/command/raft_tools 
github.com/hashicorp/nomad/devices/gpu/nvidia 
github.com/hashicorp/nomad/devices/gpu/nvidia/cmd 
github.com/hashicorp/nomad/devices/gpu/nvidia/nvml 
github.com/hashicorp/nomad/drivers/docker 
github.com/hashicorp/nomad/drivers/docker/cmd 
github.com/hashicorp/nomad/drivers/docker/docklog 
github.com/hashicorp/nomad/drivers/docker/docklog/proto 
github.com/hashicorp/nomad/drivers/docker/util 
github.com/hashicorp/nomad/drivers/exec github.com/hashicorp/nomad/drivers/java 
github.com/hashicorp/nomad/drivers/mock 

Bug#982632: marked as done (0.1.0 release is outdated and incompatible with podman 3.0)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:17:36 +
with message-id 
and subject line Bug#1041700: Removed package(s) from unstable
has caused the Debian Bug report #982632,
regarding 0.1.0 release is outdated and incompatible with podman 3.0
to be marked as done.

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

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


-- 
982632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982632
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: nomad-driver-podman
Version: 0.1.0-2
Severity: grave

As discussed recently in debian-devel, nomad-driver-podman 0.1.0 works
with the podman Varlink API, which does not exist anymore in podman 3.0,
making this package unusable for all users (at least AIUI).

A new upstream release of nomad-driver-podman, 0.2.0, however, was
released with its main feature being support for the HTTP API.

Dmitry, I know you know this, but just filing this RC bug to avoid us
collectively forgetting about this and releasing bullseye with a package
combination that isn't functional for users. Hope this is helpful!

Best,
Faidon
--- End Message ---
--- Begin Message ---
Version: 0.1.0-2+rm

Dear submitter,

as the package nomad-driver-podman 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/1041700

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#1021273: marked as done (nomad: CVE-2021-37218 CVE-2021-43415 CVE-2022-24683 CVE-2022-24684 CVE-2022-24685 CVE-2022-24686)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:18:50 +
with message-id 
and subject line Bug#1041700: Removed package(s) from unstable
has caused the Debian Bug report #1021273,
regarding nomad: CVE-2021-37218 CVE-2021-43415 CVE-2022-24683 CVE-2022-24684 
CVE-2022-24685 CVE-2022-24686
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.)


-- 
1021273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021273
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nomad
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerabilities were published for nomad.

CVE-2021-37218[0]:
| HashiCorp Nomad and Nomad Enterprise Raft RPC layer allows non-server
| agents with a valid certificate signed by the same CA to access
| server-only functionality, enabling privilege escalation. Fixed in
| 1.0.10 and 1.1.4.

https://discuss.hashicorp.com/t/hcsec-2021-21-nomad-raft-rpc-privilege-escalation/29023
https://github.com/hashicorp/nomad/pull/11089 (main)
https://github.com/hashicorp/nomad/commit/768d7c72a77e9c0415d92900753fc83e8822145a
 (release-1.1.4)
https://github.com/hashicorp/nomad/commit/61a922afcf12784281757402c8e0b61686ff855d
 (release-1.0.11)

CVE-2021-43415[1]:
| HashiCorp Nomad and Nomad Enterprise up to 1.0.13, 1.1.7, and 1.2.0,
| with the QEMU task driver enabled, allowed authenticated users with
| job submission capabilities to bypass the configured allowed image
| paths. Fixed in 1.0.14, 1.1.8, and 1.2.1.

https://discuss.hashicorp.com/t/hcsec-2021-31-nomad-qemu-task-driver-allowed-paths-bypass-with-job-args/32288
https://github.com/hashicorp/nomad/issues/11542
https://github.com/hashicorp/nomad/pull/11554
https://github.com/hashicorp/nomad/commit/40de248b940eb7babbd4a08ebe9d6874758f5285
 (v1.2.1)

CVE-2022-24683[2]:
| HashiCorp Nomad and Nomad Enterprise 0.9.2 through 1.0.17, 1.1.11, and
| 1.2.5 allow operators with read-fs and alloc-exec (or job-submit)
| capabilities to read arbitrary files on the host filesystem as root.

https://discuss.hashicorp.com/t/hcsec-2022-02-nomad-alloc-filesystem-and-container-escape/35560

CVE-2022-24684[3]:
| HashiCorp Nomad and Nomad Enterprise 0.9.0 through 1.0.16, 1.1.11, and
| 1.2.5 allow operators with job-submit capabilities to use the spread
| stanza to panic server agents. Fixed in 1.0.18, 1.1.12, and 1.2.6.

https://discuss.hashicorp.com/t/hcsec-2022-04-nomad-spread-job-stanza-may-trigger-panic-in-servers/35562
https://github.com/hashicorp/nomad/issues/12039
https://github.com/hashicorp/nomad/commit/c49359ad58f0af18a5697a0b7b9b6cca9656d267
 (v1.2.6)

CVE-2022-24685[4]:
| HashiCorp Nomad and Nomad Enterprise 1.0.17, 1.1.11, and 1.2.5 allow
| invalid HCL for the jobs parse endpoint, which may cause excessive CPU
| usage. Fixed in 1.0.18, 1.1.12, and 1.2.6.

https://discuss.hashicorp.com/t/hcsec-2022-03-nomad-malformed-job-parsing-results-in-excessive-cpu-usage/35561
https://github.com/hashicorp/nomad/issues/12038

CVE-2022-24686[5]:
| HashiCorp Nomad and Nomad Enterprise 0.3.0 through 1.0.17, 1.1.11, and
| 1.2.5 artifact download functionality has a race condition such that
| the Nomad client agent could download the wrong artifact into the
| wrong destination. Fixed in 1.0.18, 1.1.12, and 1.2.6

https://discuss.hashicorp.com/t/hcsec-2022-01-nomad-artifact-download-race-condition/35559

If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2021-37218
https://www.cve.org/CVERecord?id=CVE-2021-37218
[1] https://security-tracker.debian.org/tracker/CVE-2021-43415
https://www.cve.org/CVERecord?id=CVE-2021-43415
[2] https://security-tracker.debian.org/tracker/CVE-2022-24683
https://www.cve.org/CVERecord?id=CVE-2022-24683
[3] https://security-tracker.debian.org/tracker/CVE-2022-24684
https://www.cve.org/CVERecord?id=CVE-2022-24684
[4] https://security-tracker.debian.org/tracker/CVE-2022-24685
https://www.cve.org/CVERecord?id=CVE-2022-24685
[5] https://security-tracker.debian.org/tracker/CVE-2022-24686
https://www.cve.org/CVERecord?id=CVE-2022-24686

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Version: 0.12.10+dfsg1-3+rm

Dear submitter,

as the package nomad 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 

Bug#1027122: marked as done (nomad-driver-podman: FTBFS: unknown error)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:17:36 +
with message-id 
and subject line Bug#1041700: Removed package(s) from unstable
has caused the Debian Bug report #1027122,
regarding nomad-driver-podman: FTBFS: unknown error
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.)


-- 
1027122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1027122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nomad-driver-podman
Version: 0.1.0-2
Severity: serious
Tags: ftbfs sid bookworm
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=nomad-driver-podman=amd64=0.1.0-2%2Bb7=1672122772=0

cd _build && go install -trimpath -v -p 4 
github.com/hashicorp/nomad-driver-podman 
github.com/hashicorp/nomad-driver-podman/iopodman 
github.com/hashicorp/nomad-driver-podman/version
src/github.com/hashicorp/nomad/vendor/github.com/hashicorp/hcl/v2/pos_scanner.go:7:2:
 cannot find package "github.com/apparentlymart/go-textseg/v12/textseg" in any 
of:

/<>/_build/src/github.com/hashicorp/nomad/vendor/github.com/apparentlymart/go-textseg/v12/textseg
 (vendor tree)
/usr/lib/go-1.19/src/github.com/apparentlymart/go-textseg/v12/textseg 
(from $GOROOT)

/<>/_build/src/github.com/apparentlymart/go-textseg/v12/textseg 
(from $GOPATH)
dh_auto_build: error: cd _build && go install -trimpath -v -p 4 
github.com/hashicorp/nomad-driver-podman 
github.com/hashicorp/nomad-driver-podman/iopodman 
github.com/hashicorp/nomad-driver-podman/version returned exit code 1

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 0.1.0-2+rm

Dear submitter,

as the package nomad-driver-podman 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/1041700

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#1017900: marked as done (Ships autogenerated files that can't be renegerated with the code in Debian main)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:19:23 +
with message-id 
and subject line Bug#1041713: Removed package(s) from unstable
has caused the Debian Bug report #1017900,
regarding Ships autogenerated files that can't be renegerated with the code in 
Debian main
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.)


-- 
1017900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gudev-sharp-1.0
Version: 0.1-4.1
Severity: serious
Tags: upstream


See the discussion on the Debian Rust maintainers list for background:
https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2022-August/022857.html

While that discussion is about Rust packages that were rejected, the same
situation also applies to gtk-sharp2 unfortunately. For more details how to 
solve
this in a way that makes ftp-masters happy, please refer to them.


Affected file is gudec/gudev-api.raw. This file were autogenerated from
specific versions of the underlying C libraries and it's not clear which
versions were used.

Debian ships these C libraries but certainly in different versions so it's not
possible to regenerate these files with what is available in Debian.

It will be necessary to either include the source code of the C libraries in
the exact version, or regenerate the files at build time with whatever is
available in Debian.

The latter will probably generate different bindings, potentially even with
different API, so is probably not a useful solution.


-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (500, 'unstable-debug'), (100, 
'experimental'), (1, 'experimental-debug')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Version: 0.1-4.1+rm

Dear submitter,

as the package gudev-sharp-1.0 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/1041713

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#1000441: marked as done (nomad: FTBFS in bullseye: certificate has expired)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:18:50 +
with message-id 
and subject line Bug#1041700: Removed package(s) from unstable
has caused the Debian Bug report #1000441,
regarding nomad: FTBFS in bullseye: certificate has expired
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.)


-- 
1000441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000441
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nomad
Version: 0.12.10+dfsg1-3
Severity: serious
Tags: ftbfs
Justification: ftbfs
X-Debbugs-Cc: z...@debian.org

Rebuilding nomad in bullseye chroot, it FTBFS with:

=== RUN   TestConfig_wrapTLS_OK
config_test.go:560: wrapTLS err: x509: certificate has expired or is not 
yet valid: current time 2021-11-23T09:14:32Z is after 2021-11-09T19:48:00Z
--- FAIL: TestConfig_wrapTLS_OK (0.00s)
FAIL
FAILgithub.com/hashicorp/nomad/helper/tlsutil   0.011s


And

nomad-418 2021-11-23T09:21:37.011Z [ERROR] raft/raft.go:1656: nomad.raft: 
failed to make requestVote RPC: target="{Voter 127.0.0.1:9687 127.0.0.1:9687}" 
error="x509: certificate has expired
 or is not yet valid: current time 2021-11-23T09:21:37Z is after 
2021-11-09T19:48:00Z"
--- End Message ---
--- Begin Message ---
Version: 0.12.10+dfsg1-3+rm

Dear submitter,

as the package nomad 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/1041700

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#1000096: marked as done (cadabra: depends on obsolete pcre3 library)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:12:40 +
with message-id 
and subject line Bug#1041677: Removed package(s) from unstable
has caused the Debian Bug report #196,
regarding cadabra: depends on obsolete pcre3 library
to be marked as done.

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

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


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

Dear maintainer,

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

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

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

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

Regards,

Matthew [0] Historical reasons mean that old PCRE is packaged as
pcre3 in Debian 
--- End Message ---
--- Begin Message ---
Version: 1.46-6+rm

Dear submitter,

as the package cadabra 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/1041677

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#881911: marked as done (monobristol: does not start)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:12:12 +
with message-id 
and subject line Bug#1041663: Removed package(s) from unstable
has caused the Debian Bug report #881911,
regarding monobristol: does not start
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.)


-- 
881911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: monobristol
Version: 0.60.3-3
Severity: grave
Justification: renders package unusable

Dear Maintainer,

when starting monobristol I get this error:

"Cannot open assembly '@expanded_libdir@/monobristol/monoBristol.exe': Datei
oder Verzeichnis nicht gefunden. (File not found.)"

Apparently, @expanded_libdir@ is not expanded by anyone.

As a workaround, changing 'exec mono
"@expanded_libdir@/monobristol/monoBristol.exe" "$@"' to 'exec mono
"/usr/lib/monobristol/monoBristol.exe" "$@"' in /usr/bin/monobristol fixes the
problem.



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

Kernel: Linux 4.9.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), 
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages monobristol depends on:
ii  bristol0.60.11-3+b1
ii  libglib2.0-cil 2.12.40-2
ii  libgtk2.0-cil  2.12.40-2
ii  libmono-corlib4.5-cil  4.6.2.7+dfsg-1
ii  libmono-posix4.0-cil   4.6.2.7+dfsg-1
ii  libmono-system-xml4.0-cil  4.6.2.7+dfsg-1
ii  libmono-system4.0-cil  4.6.2.7+dfsg-1
ii  mono-runtime   4.6.2.7+dfsg-1

Versions of packages monobristol recommends:
ii  jackd  5

monobristol suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.60.3-3+rm

Dear submitter,

as the package monobristol 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/1041663

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#877106: marked as done (pinta: Pinta 1.6-2 crashes on image scaling and other image manipulation.)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:09:47 +
with message-id 
and subject line Bug#1041606: Removed package(s) from unstable
has caused the Debian Bug report #877106,
regarding pinta: Pinta 1.6-2 crashes on image scaling and other image 
manipulation.
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.)


-- 
877106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=877106
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pinta
Version: 1.6-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***



-- System Information:
Debian Release: 9.1
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.2 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=locale: Cannot set 
LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968), LANGUAGE=en_US.utf8 (charmap=locale: Cannot set LC_CTYPE to 
default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages pinta depends on:
ii  gnome-icon-theme3.12.0-2
ii  libc6   2.24-11+deb9u1
ii  libcairo2   1.14.8-1
ii  libgdk-pixbuf2.0-0  2.36.5-2+deb9u1
ii  libglib2.0-cil  2.12.40-2
ii  libgtk2.0-cil   2.12.40-2
ii  libmono-addins-gui0.2-cil   1.0+git20130406.adcd75b-4
ii  libmono-addins0.2-cil   1.0+git20130406.adcd75b-4
ii  libmono-cairo4.0-cil4.6.2.7+dfsg-1
ii  libmono-corlib4.5-cil   4.6.2.7+dfsg-1
ii  libmono-posix4.0-cil4.6.2.7+dfsg-1
ii  libmono-sharpzip4.84-cil4.6.2.7+dfsg-1
ii  libmono-system-core4.0-cil  4.6.2.7+dfsg-1
ii  libmono-system-xml4.0-cil   4.6.2.7+dfsg-1
ii  libmono-system4.0-cil   4.6.2.7+dfsg-1
ii  mono-runtime4.6.2.7+dfsg-1

pinta recommends no packages.

pinta suggests no packages.

-- debconf information excluded
--- End Message ---
--- Begin Message ---
Version: 1.6-2.1+rm

Dear submitter,

as the package pinta 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/1041606

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#1041581: marked as done (gnome-shell-extension-top-icons-plus: needs update for GNOME Shell 44)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:09:16 +
with message-id 
and subject line Bug#1041585: Removed package(s) from unstable
has caused the Debian Bug report #1041581,
regarding gnome-shell-extension-top-icons-plus: needs update for GNOME Shell 44
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.)


-- 
1041581: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041581
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gnome-shell-extension-top-icons-plus
Version: 27-8
Severity: important
Tags: trixie sid
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gnome-shell-44

This extension has not been checked for compatibility with GNOME Shell
44. Depending how compatible it is, it will either need an update to
its metadata.json and debian/control to declare compatibility with the
new version, or code changes to adapt it to the new Shell version.

If not updated, it will have to be removed from testing for the GNOME
Shell 44 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.

If a new upstream version is compatible with Shell 44 but not 43,
please upload to experimental for now.

Thanks,
smcv
--- End Message ---
--- Begin Message ---
Version: 27-8+rm

Dear submitter,

as the package gnome-shell-extension-top-icons-plus 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/1041585

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#1041096: raspi-firmware: kernel removal can render raspi unbootable

[Archi]

Hello, today I've stumbled upon exactly the same issue, running Debian 
testing.



The config.txt was replaced with:

kernel=auto

initramfs


I had to manually fix it to:

kernel=vmlinuz-6.4.0-1-arm64

initramfs initrd.img-6.4.0-1-arm64


Please take a look into this issue, as I consider it a severe problem 
for everyone.


In my case, I just did apt dist-upgrade and apt autoremove --purge. New 
kernel (6.4.0-1 in my case) caused old one to be considered for 
autoremoval, after which rpi was rendered in unbootable state. I had to 
fix it manually editing config.txt. Executing update-initramfs -u 
manually once the system booted after manual fix rendered correct 
config.txt, so it has something to do with removal procedure that at the 
same time does not regenerate initramfs (since there is no need to do so 
since we only remove old kernel and related files).


Regards,

Archi

Bug#1041789: marked as done (RM: unison-2.51+4.13.1 -- RoQA; newer version packaged)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 17:02:47 +
with message-id 
and subject line Bug#1041789: Removed package(s) from unstable
has caused the Debian Bug report #1041789,
regarding RM: unison-2.51+4.13.1 -- RoQA; newer version packaged
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.)


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

Source: unison-2.51+4.13.1
Version: 2.51.5-1
Severity: serious

Why is unison-2.51+4.13.1 not removed yet when unison-2.52 is available?
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

unison-2.51+4.13.1 |   2.51.5-1 | source, arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
unison-2.51+4.13.1 | 2.51.5-1+b1 | amd64
unison-2.51+4.13.1-gtk |   2.51.5-1 | arm64, armel, armhf, i386, mips64el, 
mipsel, ppc64el, s390x
unison-2.51+4.13.1-gtk | 2.51.5-1+b1 | amd64

--- Reason ---
RoQA; newer version packaged
--

Note that the package(s) have simply been removed from the tag
database and may (or may not) still be in the pool; this is not a bug.
The package(s) will be physically removed automatically when no suite
references them (and in the case of source, when no binary references
it).  Please also remember 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.

Packages are usually not removed from testing by hand. Testing tracks
unstable and will automatically remove packages which were removed
from unstable when removing them from testing causes no dependency
problems. The release team can force a removal from testing if it is
really needed, please contact them if this should be the case.

We try to close bugs which have been reported against this package
automatically. But please check all old bugs, if they were closed
correctly or should have been re-assigned to another package.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1041...@bugs.debian.org.

The full log for this bug can be viewed at https://bugs.debian.org/1041789

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#1042520: jabberd2: build dependency missing in testing: libgsasl7-dev

[Paul Gevers]

Source: jabberd2
Version: 2.7.0-4
Severity: serious
Tags: sid trixie
X-Debbugs-CC: hol...@debian.org
User: debian...@lists.debian.org
Usertag: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting issues with your packages. Normally your build 
dependencies shouldn't be removed from testing without removal all 
reverse build dependencies too, nor should a package be allowed to 
migrate unless all build dependencies are candidate for migration too. 
However, somehow we ended up in the current state and your source 
package is missing some Build-Depends for some while now. Not being able 
to build from source in a suite is an RC bug in that suite.


Can you please solve the situation? jabberd2 Build-Depends on a recently 
removed transitional package (bug 1038323), so you should be able to 
just Build-Depend on the non-versioned -dev package.


Paul

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


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Ajust fixed versions

[Debian Bug Tracking System]

Processing control commands:

> fixed -1 0.18.7-1~exp1
Bug #1037568 {Done: Hilko Bengen } [src:actor-framework] 
actor-framework: ftbfs with GCC-13
Marked as fixed in versions actor-framework/0.18.7-1~exp1.

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

Bug#1037568: Ajust fixed versions

[Hilko Bengen]

control: fixed -1 0.18.7-1~exp1

Bug#1042494: marked as done (otb still uses ITK 4)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 16:36:12 +
with message-id 
and subject line Bug#1042496: Removed package(s) from unstable
has caused the Debian Bug report #1042494,
regarding otb still uses ITK 4
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.)


-- 
1042494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: otb
Version: 8.1.2+dfsg-1
Severity: serious
Tags: ftbfs trixie sid
Forwarded: https://gitlab.orfeo-toolbox.org/orfeotoolbox/otb/-/issues/1917
Control: block 1024343 by -1

otb still uses ITK 4 that won't be in trixie.
--- End Message ---
--- Begin Message ---
Version: 8.1.2+dfsg-1+rm

Dear submitter,

as the package otb 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/1042496

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#1037898: marked as done (wreport: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 16:14:17 +
with message-id 
and subject line Bug#1037898: fixed in wreport 3.36-1
has caused the Debian Bug report #1037898,
regarding wreport: ftbfs with GCC-13
to be marked as done.

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

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


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

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
Program python3 found: YES (/usr/bin/python3)
Program sphinx-build found: YES (/usr/bin/sphinx-build)
Program doxygen found: YES (/usr/bin/doxygen)
Configuring version.h using configuration
Program ../runtest found: YES (/<>/wreport/../runtest)
Program ../runtest found: YES (/<>/python/../runtest)
Configuring libwreport.dox using configuration
Configuring build-docs using configuration
Program cp found: YES (/bin/cp)
Program check_btable found: YES (/<>/tables/check_btable)
Build targets in project: 9

wreport 3.34

  User defined options
buildtype: plain
libdir   : lib/x86_64-linux-gnu
localstatedir: /var
prefix   : /usr
sysconfdir   : /etc
wrap_mode: nodownload

Found ninja-1.11.1 at /usr/bin/ninja
   dh_auto_build -O-Smeson
cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 ninja -j8 -v
[1/86] c++ -Iwreport/libwreport.so.3.0.3.p -Iwreport -I../wreport -I. -I.. 
-I/usr/include/lua5.1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -Wextra -Wpedantic -std=c++11 -Wextra -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
wreport/libwreport.so.3.0.3.p/options.cc.o -MF 
wreport/libwreport.so.3.0.3.p/options.cc.o.d -o 
wreport/libwreport.so.3.0.3.p/options.cc.o -c ../wreport/options.cc
[2/86] c++ -Iwreport/libwreport.so.3.0.3.p -Iwreport -I../wreport -I. -I.. 
-I/usr/include/lua5.1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -Wextra -Wpedantic -std=c++11 -Wextra -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
wreport/libwreport.so.3.0.3.p/tableinfo.cc.o -MF 
wreport/libwreport.so.3.0.3.p/tableinfo.cc.o.d -o 
wreport/libwreport.so.3.0.3.p/tableinfo.cc.o -c ../wreport/tableinfo.cc
[3/86] c++ -Iwreport/libwreport.so.3.0.3.p -Iwreport -I../wreport -I. -I.. 
-I/usr/include/lua5.1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -Wextra -Wpedantic -std=c++11 -Wextra -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
wreport/libwreport.so.3.0.3.p/opcodes.cc.o -MF 
wreport/libwreport.so.3.0.3.p/opcodes.cc.o.d -o 
wreport/libwreport.so.3.0.3.p/opcodes.cc.o -c ../wreport/opcodes.cc
[4/86] c++ -Iwreport/libwreport.so.3.0.3.p -Iwreport -I../wreport -I. -I.. 
-I/usr/include/lua5.1 -fdiagnostics-color=always -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -Wextra -Wpedantic -std=c++11 -Wextra -Wno-unused-parameter -g 
-O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MQ 
wreport/libwreport.so.3.0.3.p/notes.cc.o -MF 
wreport/libwreport.so.3.0.3.p/notes.cc.o.d -o 

Processed: bug 1000047 is forwarded to https://gitlab.freedesktop.org/SyncEvolution/libsynthesis/-/issues/22

[Debian Bug Tracking System]

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

> forwarded 147 
> https://gitlab.freedesktop.org/SyncEvolution/libsynthesis/-/issues/22
Bug #147 [src:libsynthesis] libsynthesis: depends on obsolete pcre3 library
Set Bug forwarded-to-address to 
'https://gitlab.freedesktop.org/SyncEvolution/libsynthesis/-/issues/22'.
> thanks
Stopping processing here.

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

Processed: Merge #1042510

[Debian Bug Tracking System]

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

> reassign 1042510 libgprofng0
Bug #1042510 [binutils-x86-64-linux-gnu] Not able to upgrade 
binutils-x86-64-linux-gnu
Bug reassigned from package 'binutils-x86-64-linux-gnu' to 'libgprofng0'.
No longer marked as found in versions binutils/2.40.90.20230729-1.
Ignoring request to alter fixed versions of bug #1042510 to the same values 
previously set
> forcemerge 1042498 1042510
Bug #1042498 {Done: Matthias Klose } [libgprofng0] 
libgprofng0: broken symbols file leads to unsatisfiable dependencies
Bug #1042510 [libgprofng0] Not able to upgrade binutils-x86-64-linux-gnu
Severity set to 'grave' from 'normal'
Marked Bug as done
Added indication that 1042510 affects binutils
Marked as fixed in versions binutils/2.40.90.20230729-2.
Marked as found in versions binutils/2.40.90.20230729-1.
Added tag(s) patch.
Merged 1042498 1042510
> thanks
Stopping processing here.

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

Processed: bug 1000077 is forwarded to https://github.com/c-icap/c-icap-server/commit/888a98ff382d782729f000876b4e81f08d9046d3

[Debian Bug Tracking System]

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

> forwarded 177 
> https://github.com/c-icap/c-icap-server/commit/888a98ff382d782729f000876b4e81f08d9046d3
Bug #177 [src:c-icap] c-icap: depends on obsolete pcre3 library
Set Bug forwarded-to-address to 
'https://github.com/c-icap/c-icap-server/commit/888a98ff382d782729f000876b4e81f08d9046d3'.
> thanks
Stopping processing here.

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

Processed: Tag as pending

[Debian Bug Tracking System]

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

> tag 1042311 pending
Bug #1042311 [src:qt6-quick3dphysics] qt6-quick3dphysics: FTBFS: dh_missing: 
error: missing files, aborting
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tag as pending

[Debian Bug Tracking System]

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

> tag 1042357 pending
Bug #1042357 [src:qt6-quick3d] qt6-quick3d: FTBFS: dh_missing: error: missing 
files, aborting
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1042512: src:python-numpysane: fails to migrate to testing for too long: uploader built arch:all binary

[Paul Gevers]

Source: python-numpysane
Version: 0.36-1
Severity: serious
Control: close -1 0.39-1
Tags: sid trixie pending
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:python-numpysane has been trying to 
migrate for 31 days [2]. Hence, I am filing this bug.


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.


Your package is only blocked because the arch:all binary package(s) 
aren't built on a buildd. Unfortunately the Debian infrastructure 
doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will 
shortly do a no-changes source-only upload to DELAYED/15, closing this 
bug. Please let me know if I should delay or cancel that upload.


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:python-numpysane: fails to migrate to testing for too long: uploader built arch:all binary

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.39-1
Bug #1042512 [src:python-numpysane] src:python-numpysane: fails to migrate to 
testing for too long: uploader built arch:all binary
Marked as fixed in versions python-numpysane/0.39-1.
Bug #1042512 [src:python-numpysane] src:python-numpysane: fails to migrate to 
testing for too long: uploader built arch:all binary
Marked Bug as done

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

Processed (with 1 error): Re: Not able to upgrade binutils-x86-64-linux-gnu

[Debian Bug Tracking System]

Processing control commands:

> forcemerge 1042498 -1
Bug #1042498 {Done: Matthias Klose } [libgprofng0] 
libgprofng0: broken symbols file leads to unsatisfiable dependencies
Unable to merge bugs because:
package of #1042510 is 'binutils-x86-64-linux-gnu' not 'libgprofng0'
Failed to forcibly merge 1042498: Did not alter merged bugs.


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

Processed: Tag as pending

[Debian Bug Tracking System]

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

> tag 1042291 pending
Bug #1042291 [src:qt6-datavis3d] qt6-datavis3d: FTBFS: dh_missing: error: 
missing files, aborting
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1040223: libimage-imlib2-perl: diff for NMU version 2.03-1.2

[gregor herrmann]

Control: tags 1040223 + pending


Dear maintainer,

I've prepared an NMU for libimage-imlib2-perl (versioned as 2.03-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.


-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   
diff -Nru libimage-imlib2-perl-2.03/debian/changelog libimage-imlib2-perl-2.03/debian/changelog
--- libimage-imlib2-perl-2.03/debian/changelog	2022-10-06 18:56:50.0 +0200
+++ libimage-imlib2-perl-2.03/debian/changelog	2023-07-29 16:09:32.0 +0200
@@ -1,3 +1,16 @@
+libimage-imlib2-perl (2.03-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix "Creates empty package on bookworm upwards":
+`imlib2-config' went missing from libimlib2-dev, so use pkgconfig (new
+patch pkg-config.diff and build dependency on libextutils-pkgconfig-perl)
+(Closes: #1040223)
+  * Add patch 0001-Work-around-an-imlib2-bug-with-alpha-channel-cloning.patch
+from Niko Tyni to work around an imlib2 bug with alpha channel cloning
+which makes a test fail.
+
+ -- gregor herrmann   Sat, 29 Jul 2023 16:09:32 +0200
+
 libimage-imlib2-perl (2.03-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru libimage-imlib2-perl-2.03/debian/control libimage-imlib2-perl-2.03/debian/control
--- libimage-imlib2-perl-2.03/debian/control	2011-10-16 02:28:18.0 +0200
+++ libimage-imlib2-perl-2.03/debian/control	2023-07-29 16:00:08.0 +0200
@@ -3,7 +3,7 @@
 Priority: extra
 Section: perl
 Standards-Version: 3.9.2
-Build-Depends: debhelper (>= 8), libmodule-build-perl, libimlib2-dev, libtest-simple-perl, quilt
+Build-Depends: debhelper (>= 8), libmodule-build-perl, libimlib2-dev, libtest-simple-perl, quilt, libextutils-pkgconfig-perl
 
 Package: libimage-imlib2-perl
 Architecture: any
diff -Nru libimage-imlib2-perl-2.03/debian/patches/0001-Work-around-an-imlib2-bug-with-alpha-channel-cloning.patch libimage-imlib2-perl-2.03/debian/patches/0001-Work-around-an-imlib2-bug-with-alpha-channel-cloning.patch
--- libimage-imlib2-perl-2.03/debian/patches/0001-Work-around-an-imlib2-bug-with-alpha-channel-cloning.patch	1970-01-01 01:00:00.0 +0100
+++ libimage-imlib2-perl-2.03/debian/patches/0001-Work-around-an-imlib2-bug-with-alpha-channel-cloning.patch	2023-07-29 16:01:50.0 +0200
@@ -0,0 +1,49 @@
+From c2d646b9fa925ac2a91cb6cfb3fe6dad430c7927 Mon Sep 17 00:00:00 2001
+From: Niko Tyni 
+Date: Tue, 18 Jul 2023 15:16:21 +0100
+Subject: [PATCH] Work around an imlib2 bug with alpha channel cloning
+
+As discussed in https://bugs.debian.org/1041406 imlib2 1.10.0 introduced
+a bug where imlib_clone_image() no longer copies the alpha flag. This
+breaks test 12 of t/simple.t :
+
+  #   Failed test at t/simple.t line 68.
+  #  got: '0'
+  # expected: '1'
+
+Work around this on our side by checking for any difference after
+cloning and copying the alpha flag if necessary.
+
+Bug-Debian: https://bugs.debian.org/1040223
+---
+ lib/Image/Imlib2.xs | 11 +++
+ 1 file changed, 11 insertions(+)
+
+diff --git a/lib/Image/Imlib2.xs b/lib/Image/Imlib2.xs
+index f48d4ec..cc54d2b 100644
+--- a/lib/Image/Imlib2.xs
 b/lib/Image/Imlib2.xs
+@@ -931,9 +931,20 @@ Imlib2_clone(image)
+ CODE:
+ 	{
+ 		Imlib_Image cloned;
++		char alpha_orig;
++		char alpha_cloned;
+ 		
+ 		imlib_context_set_image(image);
+ 		cloned = imlib_clone_image();
++
++		/* imlib2 no longer clones the alpha flag since 1.10 */
++		alpha_orig = imlib_image_has_alpha();
++		imlib_context_set_image(cloned);
++		alpha_cloned = imlib_image_has_alpha();
++		if (alpha_orig != alpha_cloned) {
++			imlib_image_set_has_alpha(alpha_orig);
++		}
++		imlib_context_set_image(image);
+ 		
+ 		RETVAL = cloned;
+ 	}
+-- 
+2.39.1
+
diff -Nru libimage-imlib2-perl-2.03/debian/patches/pkg-config.diff libimage-imlib2-perl-2.03/debian/patches/pkg-config.diff
--- libimage-imlib2-perl-2.03/debian/patches/pkg-config.diff	1970-01-01 01:00:00.0 +0100
+++ libimage-imlib2-perl-2.03/debian/patches/pkg-config.diff	2023-07-29 16:01:16.0 +0200
@@ -0,0 +1,43 @@
+Description: use pkgconfig instead of the discontinued imlib2-config
+Origin: vendor
+Bug-Debian: https://bugs.debian.org/1040223
+Author: gregor herrmann 
+Last-Update: 2023-07-29
+
+--- a/Build.PL
 b/Build.PL
+@@ -1,11 +1,14 @@
+ use Module::Build;
+ use strict;
+ use Cwd;
++use ExtUtils::PkgConfig ;
+ 
+-# We need to find imlib2-config
+-my $CONFIG = "imlib2-config";
++my $pkg = 'imlib2';
++my %info = ExtUtils::PkgConfig->find ($pkg) ;
++my $version = $info{modversion} ;
++my $libs= $info{libs} ;
++my $cflags  = $info{cflags} ;
+ 
+-my $version = `$CONFIG --version`;
+ if (!$version) {
+   warn 'You must install the imlib2 library before you can install
+ Image::Imlib2. You can obtain 

Processed: libimage-imlib2-perl: diff for NMU version 2.03-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1040223 + pending
Bug #1040223 [src:libimage-imlib2-perl] libimage-imlib2-perl: Creates empty 
package on bookworm upwards (maybe because of libimlib2-dev?)
Added tag(s) pending.

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

Processed: your mail

[Debian Bug Tracking System]

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

> tag 1042245 pending
Bug #1042245 [src:qt6-positioning] qt6-positioning: FTBFS: dh_missing: error: 
missing files, aborting
Added tag(s) pending.
>
End of message, stopping processing here.

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

Bug#1042502: marked as done (util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 13:25:02 +
with message-id 
and subject line Bug#1042502: fixed in manpages-l10n 4.19.0-6
has caused the Debian Bug report #1042502,
regarding util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in 
package manpages-fr 4.19.0-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.)


-- 
1042502: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042502
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux-locales
Version: 2.39.1-3
Severity: serious
Justification: 6
X-Debbugs-Cc: jean-m...@6jf.be

Dear Maintainer,

Upgrading util-linux-locales from 2.38.1-6 to 2.39.1-3 failed and returned this 
error message:


Preparing to unpack .../util-linux-locales_2.39.1-3_all.deb ...
Unpacking util-linux-locales (2.39.1-3) over (2.38.1-6) ...
dpkg: error processing archive 
/var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/fr/man1/lastb.1.gz', which is also in 
package manpages-fr 4.19.0-5
Errors were encountered while processing:
 /var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb

Please, fix this problem.

Thank you so much.

Regards,

Jean-Marc

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

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

Versions of packages util-linux-locales depends on:
ii  util-linux  2.39.1-3

util-linux-locales recommends no packages.

util-linux-locales suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: manpages-l10n
Source-Version: 4.19.0-6
Done: Dr. Helge Kreutzmann 

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

Debian distribution maintenance software
pp.
Dr. Helge Kreutzmann  (supplier of updated manpages-l10n 
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, 29 Jul 2023 14:25:17 +0200
Source: manpages-l10n
Architecture: source
Version: 4.19.0-6
Distribution: unstable
Urgency: medium
Maintainer: Dr. Helge Kreutzmann 
Changed-By: Dr. Helge Kreutzmann 
Closes: 1042484 1042502
Changes:
 manpages-l10n (4.19.0-6) unstable; urgency=medium
 .
   * Properly remove the symlinks for util-linux man pages.
 Closes: #1042484, #1042502
Checksums-Sha1:
 a159851318403266b1c94560fcbb6ad951b18303 3773 manpages-l10n_4.19.0-6.dsc
 882b916b98a7139fa476f78346926a7c9280cf63 72288 
manpages-l10n_4.19.0-6.debian.tar.xz
 009d9d5fe5791af9291e59ba4050b2b8087ef1c4 14376 
manpages-l10n_4.19.0-6_amd64.buildinfo
Checksums-Sha256:
 d07a598a9f66de125742c5ad4dfd9d5e73ad717e028aac477b04515f9fd628c8 3773 
manpages-l10n_4.19.0-6.dsc
 7f0dd3848ee215e26e985ef71afe7300a6f2a4a0d8ea1c0b425996db79c8f542 72288 
manpages-l10n_4.19.0-6.debian.tar.xz
 bf697627923d4fc8214957eba9e9483fd35a8767cfb5a9c7617cfc13f4ee5e1c 14376 
manpages-l10n_4.19.0-6_amd64.buildinfo
Files:
 1af764fefe3240f4b6438429f2fe46d1 3773 doc optional manpages-l10n_4.19.0-6.dsc
 c6d5715be139015db044400fc69020b4 72288 doc optional 
manpages-l10n_4.19.0-6.debian.tar.xz
 b9e562267e62c6587f6036b9628d4e39 14376 doc optional 
manpages-l10n_4.19.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbZZfteMW0gNUynuwQbqlJmgq5nAFAmTFCjoACgkQQbqlJmgq
5nDsGRAAgVKCLq8faEUJfct+VtDFfcKjgo8y+NEZqU7dO3k2gVkADOdGlmIzcnWa
mIlj5iqKF92fQLN4vwTUTeGsd/B7X+zBWKeaFc5RuckKj6d4HhGc//PExmAdHRdo
FHbnUFUxoOGXve86qes0DG1K6PNiDQpM0h4okvPLQvzLQfOGOgcz0LzeXJ7gPkOh
aoXzeeCRc7U9KXd4N1gWUdFGH/DHRZrBkIOE8LedzoO4dxHXnlKR05GSxO66mZ8i
oVMu3kG6iZPP885/kV5C7YxiDpcuxrOYFB0cdNWngGbvrvkowj+A0pnZ9EEasi/C
ReeG92scdEwdZDQPKl582zeRtYKJJYDFnU4kEPePWcxOKoLneO1dsSJYhXqKhxa7
MwO3Nial6v1FtfK2kr7pt2DbQN93PbYY9LKb7KSgut4MdfN6YVzqKhn9ezVo3S0A
BdxQvNqTb+LFPz9VXU9HxD5seGs3XOavBodGl2PYCG6hCo0sAJMietqxMeLFzous

Bug#1042484: marked as done (util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 13:25:02 +
with message-id 
and subject line Bug#1042484: fixed in manpages-l10n 4.19.0-6
has caused the Debian Bug report #1042484,
regarding util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in 
package manpages-fr 4.19.0-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.)


-- 
1042484: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042484
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: util-linux-locales
Version: 2.39.1-3
Severity: serious
Justification: 6
X-Debbugs-Cc: jean-m...@6jf.be

Dear Maintainer,

Upgrading util-linux-locales from 2.38.1-6 to 2.39.1-3 failed and returned this 
error message:


Preparing to unpack .../util-linux-locales_2.39.1-3_all.deb ...
Unpacking util-linux-locales (2.39.1-3) over (2.38.1-6) ...
dpkg: error processing archive 
/var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/fr/man1/lastb.1.gz', which is also in 
package manpages-fr 4.19.0-5
Errors were encountered while processing:
 /var/cache/apt/archives/util-linux-locales_2.39.1-3_all.deb

Please, fix this problem.

Thank you so much.

Regards,

Jean-Marc

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

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

Versions of packages util-linux-locales depends on:
ii  util-linux  2.39.1-3

util-linux-locales recommends no packages.

util-linux-locales suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: manpages-l10n
Source-Version: 4.19.0-6
Done: Dr. Helge Kreutzmann 

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

Debian distribution maintenance software
pp.
Dr. Helge Kreutzmann  (supplier of updated manpages-l10n 
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, 29 Jul 2023 14:25:17 +0200
Source: manpages-l10n
Architecture: source
Version: 4.19.0-6
Distribution: unstable
Urgency: medium
Maintainer: Dr. Helge Kreutzmann 
Changed-By: Dr. Helge Kreutzmann 
Closes: 1042484 1042502
Changes:
 manpages-l10n (4.19.0-6) unstable; urgency=medium
 .
   * Properly remove the symlinks for util-linux man pages.
 Closes: #1042484, #1042502
Checksums-Sha1:
 a159851318403266b1c94560fcbb6ad951b18303 3773 manpages-l10n_4.19.0-6.dsc
 882b916b98a7139fa476f78346926a7c9280cf63 72288 
manpages-l10n_4.19.0-6.debian.tar.xz
 009d9d5fe5791af9291e59ba4050b2b8087ef1c4 14376 
manpages-l10n_4.19.0-6_amd64.buildinfo
Checksums-Sha256:
 d07a598a9f66de125742c5ad4dfd9d5e73ad717e028aac477b04515f9fd628c8 3773 
manpages-l10n_4.19.0-6.dsc
 7f0dd3848ee215e26e985ef71afe7300a6f2a4a0d8ea1c0b425996db79c8f542 72288 
manpages-l10n_4.19.0-6.debian.tar.xz
 bf697627923d4fc8214957eba9e9483fd35a8767cfb5a9c7617cfc13f4ee5e1c 14376 
manpages-l10n_4.19.0-6_amd64.buildinfo
Files:
 1af764fefe3240f4b6438429f2fe46d1 3773 doc optional manpages-l10n_4.19.0-6.dsc
 c6d5715be139015db044400fc69020b4 72288 doc optional 
manpages-l10n_4.19.0-6.debian.tar.xz
 b9e562267e62c6587f6036b9628d4e39 14376 doc optional 
manpages-l10n_4.19.0-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbZZfteMW0gNUynuwQbqlJmgq5nAFAmTFCjoACgkQQbqlJmgq
5nDsGRAAgVKCLq8faEUJfct+VtDFfcKjgo8y+NEZqU7dO3k2gVkADOdGlmIzcnWa
mIlj5iqKF92fQLN4vwTUTeGsd/B7X+zBWKeaFc5RuckKj6d4HhGc//PExmAdHRdo
FHbnUFUxoOGXve86qes0DG1K6PNiDQpM0h4okvPLQvzLQfOGOgcz0LzeXJ7gPkOh
aoXzeeCRc7U9KXd4N1gWUdFGH/DHRZrBkIOE8LedzoO4dxHXnlKR05GSxO66mZ8i
oVMu3kG6iZPP885/kV5C7YxiDpcuxrOYFB0cdNWngGbvrvkowj+A0pnZ9EEasi/C
ReeG92scdEwdZDQPKl582zeRtYKJJYDFnU4kEPePWcxOKoLneO1dsSJYhXqKhxa7
MwO3Nial6v1FtfK2kr7pt2DbQN93PbYY9LKb7KSgut4MdfN6YVzqKhn9ezVo3S0A
BdxQvNqTb+LFPz9VXU9HxD5seGs3XOavBodGl2PYCG6hCo0sAJMietqxMeLFzous

Bug#1038935: [DRE-maint] Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='

[Georg Faerber]

Hi,

On 23-06-27 09:05:43, Georg Faerber wrote:
> Regarding the test: I'll seek comments of the Ruby team before filling
> the -pu; I believe the risk of regressions should be fairly low, as
> arel, as described, has been part of activerecord since quite some
> time.  I'll test this especially in combination with schleuder, which
> exposed this issue; to ease future maintenance and increase the
> chances of spotting these issues earlier, ideally before release, I
> added a "piuparts multi distro upgrade" test job to the Salsa CI [1].

I was on the road the last weeks, therefore I was only able to mail the
team by now.

Cheers,
Georg

Bug#1041162: marked as pending in autopkgtest

[Paul Gevers]

Control: tag -1 pending

Hello,

Bug #1041162 in autopkgtest 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/ci-team/autopkgtest/-/commit/3d98501d0d4758590bc178cc4d1650dd9b93f64b


adt_testbed: restructure creation of pin file

$(apt-cache showsrc $pkg) shows all packages available in the source,
including Extra-Source-Only entries. This can lead to unintended
failures.

apt 2.0 and above support a src:$package format, so let's use that as
it also simplifies the logic a lot. Have a fallback for testbeds with
an older apt using dumpavail.

While we at it also generate the preference file on the host system
and copy it over instead of creating it in a shell command.

Closes: #1041162


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041162

Bug#1038870: marked as done (golang-github-grpc-ecosystem-grpc-gateway FTBFS on 32bit)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 12:49:32 +
with message-id 
and subject line Bug#1038870: fixed in 
golang-github-grpc-ecosystem-grpc-gateway 1.16.0-3
has caused the Debian Bug report #1038870,
regarding golang-github-grpc-ecosystem-grpc-gateway FTBFS on 32bit
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.)


-- 
1038870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038870
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-grpc-ecosystem-grpc-gateway
Version: 1.16.0-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=golang-github-grpc-ecosystem-grpc-gateway=1.16.0-2

...
# github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger/genswagger 
[github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger/genswagger.test]
src/github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger/genswagger/template_test.go:1535:15:
 cannot use math.MaxInt32 + 1 (untyped int constant 2147483648) as int value in 
argument to fmt.Sprint (overflows)
src/github.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger/genswagger/template_test.go:1541:15:
 cannot use math.MaxInt64 (untyped int constant 9223372036854775807) as int 
value in argument to fmt.Sprint (overflows)
...
FAILgithub.com/grpc-ecosystem/grpc-gateway/protoc-gen-swagger/genswagger 
[build failed]
...
--- End Message ---
--- Begin Message ---
Source: golang-github-grpc-ecosystem-grpc-gateway
Source-Version: 1.16.0-3
Done: Reinhard Tartler 

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

Debian distribution maintenance software
pp.
Reinhard Tartler  (supplier of updated 
golang-github-grpc-ecosystem-grpc-gateway 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, 29 Jul 2023 07:19:40 -0400
Source: golang-github-grpc-ecosystem-grpc-gateway
Architecture: source
Version: 1.16.0-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Reinhard Tartler 
Closes: 1038870
Changes:
 golang-github-grpc-ecosystem-grpc-gateway (1.16.0-3) unstable; urgency=medium
 .
   * Team upload.
   * Avoid building protoc-gen-swagger, Closes: #1038870
   * revert: Add runtime/internal/examplepb to DH_GOLANG_EXCLUDES.
Checksums-Sha1:
 89d293be7f17fda6d929f41b78969f84e71c17a9 2981 
golang-github-grpc-ecosystem-grpc-gateway_1.16.0-3.dsc
 1648d9151f5f444c66010fbd2878c4ef00514d83 3840 
golang-github-grpc-ecosystem-grpc-gateway_1.16.0-3.debian.tar.xz
Checksums-Sha256:
 3665bd6c41a61354b56fbb94bcffeea7760ca058beea3d8eea026181a8ab7c3b 2981 
golang-github-grpc-ecosystem-grpc-gateway_1.16.0-3.dsc
 c1d026ed6979b564b93912bb126d679735075cd027ac0689da7f20b54a956a73 3840 
golang-github-grpc-ecosystem-grpc-gateway_1.16.0-3.debian.tar.xz
Files:
 23e629e4964a93f21cae3b20ad8f286c 2981 devel optional 
golang-github-grpc-ecosystem-grpc-gateway_1.16.0-3.dsc
 68903cebc9d0c57d07fa434fccac7fdf 3840 devel optional 
golang-github-grpc-ecosystem-grpc-gateway_1.16.0-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEMN59F2OrlFLH4IJQSadpd5QoJssFAmTFA44UHHNpcmV0YXJ0
QHRhdXdhcmUuZGUACgkQSadpd5QoJssosBAAyEv0no35VA0IDowCD45WtyPyS7/+
twZNSjyBlqCR/9hFZMYUhVhzDTtZZ4ODUnqvuc0gAXmH19RFJ7wTQ4w1C9Tp3/YY
P9duPY/xCzpFK5yLfeedxt28NRHwz4aY/vgE8fq+8iCgyjWomGeVuceh2AyfuSH2
JgW6nELf0h2+jcucevI+VXuHZTZxmNVGgZ0UBV/JkuF4eW1rhjf0K73iBSAHXyP5
aMNnah4ffVYcCRP5Ce3QWTlgWWqNcgD3qfCZbdn3Oy1YiHehjoAeWvMVsZgyM6o4
GuTjgq9N3mIGpbgS+NFhorQp2IyePt7C/xKOya9hUg4h+OvqW1pRGchqhU9uxipe
4+hhXvowawdAJNzA2IFvjDlwsr890KRtvb/xJbpW7ntwz2joV7yWOs1dOqpahjWQ
HOJZrA30bxXWYMgGJVRBeCmaC3WaRAUGMw3j8uGiTuDtYlH4neLzGIF9qDk+snnw
7UdvkMDCC7TKvQLQHB7SYg7UHOM6YtVgaDIhHAAK8hhaAfbQC+KbtWM30TL+6Ema
0pCZJLxU6+Hpq2P3CLA6a7vMqYR4DFdahGegeuaigeTwKi3QaKuJL0sq9pshsqpw
gqYYObHFISELj2RpT4D9wdVe5GgQOCVZfUZKn7cigHP+PJIGrJgPlya0qH+P+Skv
lwuTG3a611FIjFE=
=sSYr
-END PGP SIGNATURE End Message ---

Processed: Bug#1041162 marked as pending in autopkgtest

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1041162 [autopkgtest] autopkgtest should ignore ESO entries for pinning
Ignoring request to alter tags of bug #1041162 to the same tags previously set

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

Bug#1037226:

[Ervin Hegedüs]

Seems like this bug is fixed.

# apt install libnginx-mod-http-modsecurity --default-release bookworm
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  libnginx-mod-http-modsecurity
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 25.4 kB of archives.
After this operation, 196 kB of additional disk space will be used.
Get:1 http://ftp.hu.debian.org/debian bookworm/main amd64
libnginx-mod-http-modsecurity amd64 1.0.3-1+b2 [25.4 kB]
Fetched 25.4 kB in 0s (331 kB/s)
Selecting previously unselected package libnginx-mod-http-modsecurity.
(Reading database ... 57140 files and directories currently installed.)
Preparing to unpack .../libnginx-mod-http-modsecurity_1.0.3-1+b2_amd64.deb
...
Unpacking libnginx-mod-http-modsecurity (1.0.3-1+b2) ...
Setting up libnginx-mod-http-modsecurity (1.0.3-1+b2) ...
Processing triggers for nginx (1.22.1-9) ...
Triggering nginx reload ...

Jul 29 14:11:10 debian12 systemd[1]: Starting nginx.service - A high
performance web server and a reverse proxy server...
Jul 29 14:11:10 debian12 nginx[1600]: 2023/07/29 14:11:10 [notice]
1600#1600: ModSecurity-nginx v1.0.3 (rules loaded inline/local/remote:
0/921/0)

Can we close this issue?


a.

On Sat, Jul 15, 2023 at 2:51 PM Tobias Frost  wrote:

> Control: tags -1 pending
> Conrtol: block -1 by 1040799
>
> This bug has been fixed in unstable with the binNMU 1.0.3-1b3, see #1040858
>
> It is also scheduled to be fixed in the next stable-point-release, see
> #1040799
>
>
> --
> tobi
>

Processed: Bug#1038870 marked as pending in golang-github-grpc-ecosystem-grpc-gateway

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1038870 [src:golang-github-grpc-ecosystem-grpc-gateway] 
golang-github-grpc-ecosystem-grpc-gateway FTBFS on 32bit
Added tag(s) pending.

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

Bug#1038870: marked as pending in golang-github-grpc-ecosystem-grpc-gateway

[Reinhard Tartler]

Control: tag -1 pending

Hello,

Bug #1038870 in golang-github-grpc-ecosystem-grpc-gateway 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/go-team/packages/golang-github-grpc-ecosystem-grpc-gateway/-/commit/78518f0f189b37cadfda6e047c1873ad34bbc00e


Avoid building protoc-gen-swagger, Closes: #1038870


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1038870

Bug#967010: marked as done (apache2: last debian 10.4 , last apache avail from repo hangs on install (and start phase))

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 13:45:57 +0200
with message-id <498b57b77752be9de201b362bb64fdf3f641d296.ca...@debian.org>
and subject line Re: apache2: last debian 10.4 , last apache avail from repo 
hangs on install (and start phase)
has caused the Debian Bug report #967010,
regarding apache2: last debian 10.4 , last apache avail from repo hangs on 
install (and start phase)
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.)


-- 
967010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apache2
Version: 2.4.38-3+deb10u3
Severity: grave
Justification: renders package unusable

Dear Maintainer,


   * What led up to the situation?
package installing
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
apt-get install apache2
   * What was the outcome of this action?
packages did not start
   * What outcome did you expect instead?
packages will start ok


I have fresh debian 10 install, OS after full upgrade with:
`apt-get upgrade` and
`apt-get dist-upgrade`

I want to install apache2 packages, it hang on install (on post-install phase 
when apache starts):

(*my findings why is below)

apt-get install apache2  
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  apache2-bin apache2-data apache2-utils libapr1 libaprutil1 
libaprutil1-dbd-sqlite3 libaprutil1-ldap libbrotli1 libjansson4 liblua5.2-0
Suggested packages:
  apache2-doc apache2-suexec-pristine | apache2-suexec-custom
The following NEW packages will be installed:
  apache2 apache2-bin apache2-data apache2-utils libapr1 libaprutil1 
libaprutil1-dbd-sqlite3 libaprutil1-ldap libbrotli1 libjansson4 liblua5.2-0
0 upgraded, 11 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/2,606 kB of archives.
After this operation, 8,885 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Selecting previously unselected package libapr1:amd64.
(Reading database ... 85650 files and directories currently installed.)
Preparing to unpack .../00-libapr1_1.6.5-1+b1_amd64.deb ...
Unpacking libapr1:amd64 (1.6.5-1+b1) ...
Selecting previously unselected package libaprutil1:amd64.
Preparing to unpack .../01-libaprutil1_1.6.1-4_amd64.deb ...
Unpacking libaprutil1:amd64 (1.6.1-4) ...
Selecting previously unselected package libaprutil1-dbd-sqlite3:amd64.
Preparing to unpack .../02-libaprutil1-dbd-sqlite3_1.6.1-4_amd64.deb ...
Unpacking libaprutil1-dbd-sqlite3:amd64 (1.6.1-4) ...
Selecting previously unselected package libaprutil1-ldap:amd64.
Preparing to unpack .../03-libaprutil1-ldap_1.6.1-4_amd64.deb ...
Unpacking libaprutil1-ldap:amd64 (1.6.1-4) ...
Selecting previously unselected package libbrotli1:amd64.
Preparing to unpack .../04-libbrotli1_1.0.7-2_amd64.deb ...
Unpacking libbrotli1:amd64 (1.0.7-2) ...
Selecting previously unselected package libjansson4:amd64.
Preparing to unpack .../05-libjansson4_2.12-1_amd64.deb ...
Unpacking libjansson4:amd64 (2.12-1) ...
Selecting previously unselected package liblua5.2-0:amd64.
Preparing to unpack .../06-liblua5.2-0_5.2.4-1.1+b2_amd64.deb ...
Unpacking liblua5.2-0:amd64 (5.2.4-1.1+b2) ...
Selecting previously unselected package apache2-bin.
Preparing to unpack .../07-apache2-bin_2.4.38-3+deb10u3_amd64.deb ...
Unpacking apache2-bin (2.4.38-3+deb10u3) ...
Selecting previously unselected package apache2-data.
Preparing to unpack .../08-apache2-data_2.4.38-3+deb10u3_all.deb ...
Unpacking apache2-data (2.4.38-3+deb10u3) ...
Selecting previously unselected package apache2-utils.
Preparing to unpack .../09-apache2-utils_2.4.38-3+deb10u3_amd64.deb ...
Unpacking apache2-utils (2.4.38-3+deb10u3) ...
Selecting previously unselected package apache2.
Preparing to unpack .../10-apache2_2.4.38-3+deb10u3_amd64.deb ...
Unpacking apache2 (2.4.38-3+deb10u3) ...
Setting up libbrotli1:amd64 (1.0.7-2) ...
Setting up libapr1:amd64 (1.6.5-1+b1) ...
Setting up libjansson4:amd64 (2.12-1) ...
Setting up liblua5.2-0:amd64 (5.2.4-1.1+b2) ...
Setting up apache2-data (2.4.38-3+deb10u3) ...
Setting up libaprutil1:amd64 (1.6.1-4) ...
Setting up libaprutil1-ldap:amd64 (1.6.1-4) ...
Setting up libaprutil1-dbd-sqlite3:amd64 (1.6.1-4) ...
Setting up apache2-utils (2.4.38-3+deb10u3) ...
Setting up apache2-bin (2.4.38-3+deb10u3) ...
Setting up apache2 (2.4.38-3+deb10u3) ...
Enabling module mpm_event.
Enabling module authz_core.
Enabling module authz_host.
Enabling module authn_core.
Enabling module auth_basic.
Enabling module 

Bug#1042498: marked as done (libgprofng0: broken symbols file leads to unsatisfiable dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 11:23:07 +
with message-id 
and subject line Bug#1042498: fixed in binutils 2.40.90.20230729-2
has caused the Debian Bug report #1042498,
regarding libgprofng0: broken symbols file leads to unsatisfiable 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.)


-- 
1042498: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042498
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgprofng0
Version: 2.40.90.20230729-1
Severity: grave
Tags: patch

The new versions of binutils is not installable:

,
| $ LANG=C apt -s install binutils binutils-x86-64-linux-gnu
| [...]
| 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:
|  binutils-x86-64-linux-gnu : Depends: libgprofng (>= 2.40.90) but it is not 
installable
`

This broken dependency is due to a typo in the libgprofng0 symbols file,
which the attached patch should fix (untested).


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

diff --git a/debian/libgprofng0.symbols b/debian/libgprofng0.symbols
index d790522..08f7ec9 100644
--- a/debian/libgprofng0.symbols
+++ b/debian/libgprofng0.symbols
@@ -1,5 +1,5 @@
 # SymbolsHelper-Confirmed: 2.40.90 amd64 arm64 i386
-libgprofng.so.0 libgprofng #MINVER#
+libgprofng.so.0 libgprofng0 #MINVER#
  ABS_PP_CODES@Base 2.40.90
  ABS_RT_CODES@Base 2.40.90
  DOBJ_ANON@Base 2.40.90
--- End Message ---
--- Begin Message ---
Source: binutils
Source-Version: 2.40.90.20230729-2
Done: Matthias Klose 

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

Debian distribution maintenance software
pp.
Matthias Klose  (supplier of updated binutils 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, 29 Jul 2023 12:47:21 +0200
Source: binutils
Architecture: source
Version: 2.40.90.20230729-2
Distribution: unstable
Urgency: medium
Maintainer: Matthias Klose 
Changed-By: Matthias Klose 
Closes: 1042498
Changes:
 binutils (2.40.90.20230729-2) unstable; urgency=medium
 .
   * Fix typo in libgprofng0 symbols file (Sven Joachim). Closes: #1042498.
Checksums-Sha1:
 59c92188a8f220d44b647287662cc80d7021 12133 binutils_2.40.90.20230729-2.dsc
 ff4121500cf3b989fec781469f13dbe30c618b3d 126240 
binutils_2.40.90.20230729-2.debian.tar.xz
 fe5897548972a7d7a2b3b8f0981e4914eaa43d15 6877 
binutils_2.40.90.20230729-2_source.buildinfo
Checksums-Sha256:
 4039d425904b9514ef4e1543834abe6162287f2f3f6d47e7c809257ebb23dbae 12133 
binutils_2.40.90.20230729-2.dsc
 c53e30ed08e6072e3602ff41ff9415d1a96d699ea0dba28064acac91d10c923a 126240 
binutils_2.40.90.20230729-2.debian.tar.xz
 30312c50e573195c6ace6dccbb4f02548f0deb6fc252028fda89f041da3d4257 6877 
binutils_2.40.90.20230729-2_source.buildinfo
Files:
 d409c828d01de2dfd3605b30962a0521 12133 devel optional 
binutils_2.40.90.20230729-2.dsc
 8b455523da00781a9e9d6c66be8a96ac 126240 devel optional 
binutils_2.40.90.20230729-2.debian.tar.xz
 5f69caf9a19e54db3ff0e60287e1c63b 6877 devel optional 
binutils_2.40.90.20230729-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE1WVxuIqLuvFAv2PWvX6qYHePpvUFAmTE7ocQHGRva29AZGVi
aWFuLm9yZwAKCRC9fqpgd4+m9W7oD/4y18kZh+3wHaE6phxPihvsXn6wXrOtEkO6
m/aHzA2xmmY2AUCpXsN3gB4ymbBy7QAoqWCWDwsMirQkLb3rQ0YBfvBfjWJILX00
UgEZek2+WQavdEJ5PkitPYyD9Njj7gmjKy9NEWggloUIVsJjSJ5REnI4oLkboPcP
3UsUUsEhy0CDiGt9LcvW1j5tZfqkkyzePUCctHCEO58u9K6ppUYnwTeNOIg6AOqN
32TXerwg/Ps1qp4N5ACFG4BSVBQK6/oe6HVmCFes3SOlv1Xpv4hNZxuRadSzh5Zt
favV8adPm/C83Etrj0vnOoRfzJivThqppeZSapT+9KJB9JnwuzkfLpFKDdwU4trF
IKcuL732YMKnaGNAiot9fnxK95n9Bqa+Qoop8qpwfIE67Sq0+WWR/LdeWo1+h20e
mkCskXotFwqd17F9+2QSJ7+E9SmvrtBT9BpppWVcL7ag57SEUH9a5cKoSly7lE6N

Bug#1029411: marked as done (rt-extension-mergeusers: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 11:25:31 +
with message-id 
and subject line Bug#1029411: fixed in rt-extension-mergeusers 1.08-1
has caused the Debian Bug report #1029411,
regarding rt-extension-mergeusers: autopkgtest failure
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.)


-- 
1029411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029411
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rt-extension-mergeusers
Version: 1.06-1
Severity: serious

https://ci.debian.net/packages/r/rt-extension-mergeusers/unstable/amd64/

...
autopkgtest [12:12:08]: test autodep8-perl: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps
autopkgtest [12:12:08]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 
exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 
produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/MergeUsers.pm in @INC (you 
may need to install the RT::Extension::MergeUsers module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::MergeUsers" -e 1 2>&1 exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::MergeUsers" -e 1 2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/MergeUsers.pm in @INC (you 
may need to install the RT::Extension::MergeUsers module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist
# Looks like you failed 4 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# Can't locate RT/Extension/MergeUsers.pm in @INC (you may need to install the 
RT::Extension::MergeUsers module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 1 -  /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 exited 
successfully
not ok 2 -  /usr/bin/perl -w -M"RT::Extension::MergeUsers" -e 1 2>&1 produced 
no (non-whitelisted) output
# Can't locate RT/Extension/MergeUsers.pm in @INC (you may need to install the 
RT::Extension::MergeUsers module) (@INC contains: /etc/perl 
/usr/local/lib/x86_64-linux-gnu/perl/5.36.0 /usr/local/share/perl/5.36.0 
/usr/lib/x86_64-linux-gnu/perl5/5.36 /usr/share/perl5 
/usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.36 
/usr/share/perl/5.36 /usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::MergeUsers" -e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::MergeUsers" -e 1 2>&1 produced no (non-whitelisted) output
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/4 subtests 

Test Summary Report
---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) 
Tests: 4 Failed: 4)
  Failed tests:  1-4
  Non-zero exit status: 4
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.08 cusr  0.00 
csys =  0.10 CPU)
Result: FAIL
autopkgtest [12:12:09]: test autodep8-perl: ---]
autopkgtest [12:12:09]: test autodep8-perl:  - - - - - - - - - - results - - - 
- - - - - - -
autodep8-perlFAIL non-zero exit status 1
autopkgtest [12:12:09]: test autodep8-perl:  - - - - - - - - - - stderr - - - - 
- - - - - -

#   Failed test ' /usr/bin/perl -w 

Processed: Only bookworm is still affected until the next point release

[Debian Bug Tracking System]

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

> tags 1037226 - trixie sid
Bug #1037226 [libnginx-mod-http-modsecurity] libnginx-mod-http-modsecurity 
fails to start after update libmodsecurity3 to v3.0.9
Removed tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1042401: marked as done (sccache FTBFS multiple issues)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 10:59:15 +
with message-id 
and subject line Bug#1042401: fixed in sccache 0.5.4-3
has caused the Debian Bug report #1042401,
regarding sccache FTBFS multiple issues
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.)


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

Package: sccache
Version: 0.5.4
Severity: serious

sccache has a couple of FTBFS issues.

The first is that a couple of dependencies have been updated, dealing
with this is a simple matter of dropping patches and updating
dependencies.

The second is that the build runs out of address space on mipsel.
The workaround seems to be to use "thin" lto rather than full
lto. Unfortunately i'm not aware of a good way to do this other
than editing Cargo.toml. I did so with sed in debian/rules,
conditioned behind architecture conditionals.

Debdiff attatched, I may or may not NMU this later.diff -Nru sccache-0.5.4/debian/changelog sccache-0.5.4/debian/changelog
--- sccache-0.5.4/debian/changelog  2023-07-05 18:31:19.0 +
+++ sccache-0.5.4/debian/changelog  2023-07-25 23:06:38.0 +
@@ -1,3 +1,14 @@
+sccache (0.5.4-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Drop patch 2023 and update debian dependency, directories 5.x is now in
+Debian.
+  * Drop patch 2016 and update debian dependency, daemonise 0.5 is now in
+Debian.
+  * Use thin lto on mipsel to avoid running out of address space.
+
+ -- Peter Michael Green   Tue, 25 Jul 2023 23:06:38 +
+
 sccache (0.5.4-2) unstable; urgency=medium
 
   * drop patch 2019, obsoleted by Debian package updates
diff -Nru sccache-0.5.4/debian/control sccache-0.5.4/debian/control
--- sccache-0.5.4/debian/control2023-06-27 13:20:11.0 +
+++ sccache-0.5.4/debian/control2023-07-25 23:06:38.0 +
@@ -22,8 +22,8 @@
  librust-chrono-0.4+default-dev,
  librust-clap-4+default-dev,
  librust-counted-array-0.1+default-dev,
- librust-daemonize-0.4+default-dev,
- librust-directories-4+default-dev,
+ librust-daemonize-0.5+default-dev,
+ librust-directories-5+default-dev,
  librust-env-logger-0.9+default-dev,
  librust-encoding-0.2+default-dev,
  librust-filetime-0.2+default-dev,
diff -Nru sccache-0.5.4/debian/patches/2016_daemonize.patch 
sccache-0.5.4/debian/patches/2016_daemonize.patch
--- sccache-0.5.4/debian/patches/2016_daemonize.patch   2023-06-27 
13:26:13.0 +
+++ sccache-0.5.4/debian/patches/2016_daemonize.patch   1970-01-01 
00:00:00.0 +
@@ -1,17 +0,0 @@
-Description: relax dependency on crate daemonize
- Needed to match Debian-packaged daemonize v0.4.1.
-Author: Jonas Smedegaard 
-Last-Update: 2023-05-21

-This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 a/Cargo.toml
-+++ b/Cargo.toml
-@@ -108,7 +108,7 @@
- serial_test = ">= 0.9, < 3"
- 
- [target.'cfg(unix)'.dependencies]
--daemonize = "0.5"
-+daemonize = ">= 0.4, < 0.6"
- 
- [features]
- all = [
diff -Nru sccache-0.5.4/debian/patches/2023_directories.patch 
sccache-0.5.4/debian/patches/2023_directories.patch
--- sccache-0.5.4/debian/patches/2023_directories.patch 2023-07-05 
18:31:19.0 +
+++ sccache-0.5.4/debian/patches/2023_directories.patch 1970-01-01 
00:00:00.0 +
@@ -1,17 +0,0 @@
-Description: relax dependency on crate directories
- Needed to match Debian-packaged directories v4.0.1.
-Author: Jonas Smedegaard 
-Last-Update: 2023-05-21

-This patch header follows DEP-3: http://dep.debian.net/deps/dep3/
 a/Cargo.toml
-+++ b/Cargo.toml
-@@ -33,7 +33,7 @@
- byteorder = "1.0"
- bytes = "1"
- clap = { version = "4.1.11", features = ["derive", "env", "wrap_help"] }
--directories = "5.0.0"
-+directories = ">= 4, < 6"
- encoding = "0.2"
- env_logger = ">= 0.9, < 0.11"
- filetime = "0.2"
diff -Nru sccache-0.5.4/debian/patches/series 
sccache-0.5.4/debian/patches/series
--- sccache-0.5.4/debian/patches/series 2023-07-04 08:18:27.0 +
+++ sccache-0.5.4/debian/patches/series 2023-07-25 23:06:38.0 +
@@ -15,9 +15,7 @@
 2013_is-terminal.patch
 2014_hyper.patch
 2015_uuid.patch
-2016_daemonize.patch
 2017_memmap2.patch
 2018_regex.patch
 2021_chrono.patch
 2022_reqwest_trust-dns.patch
-2023_directories.patch
diff -Nru sccache-0.5.4/debian/rules sccache-0.5.4/debian/rules
--- sccache-0.5.4/debian/rules  2023-07-05 18:31:19.0 +
+++ sccache-0.5.4/debian/rules  2023-07-25 23:06:38.0 +
@@ -26,6 +26,10 @@
dh $@ --buildsystem cargo
 
 

Bug#1042225: marked as done (sccache: FTBFS: unsatisfiable build-dependencies: librust-daemonize-0.4+default-dev, librust-directories-4+default-dev)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 10:59:15 +
with message-id 
and subject line Bug#1042225: fixed in sccache 0.5.4-3
has caused the Debian Bug report #1042225,
regarding sccache: FTBFS: unsatisfiable build-dependencies: 
librust-daemonize-0.4+default-dev, librust-directories-4+default-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.)


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

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, 
> librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, 
> librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, 
> librust-async-trait-0.1+default-dev (>= 0.1.52), 
> librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, 
> librust-bincode-1+default-dev, librust-blake3-1+default-dev, 
> librust-byteorder-1+default-dev, librust-bytes-1+default-dev, 
> librust-chrono-0.4+default-dev, librust-clap-4+default-dev, 
> librust-counted-array-0.1+default-dev, librust-daemonize-0.4+default-dev, 
> librust-directories-4+default-dev, librust-env-logger-0.9+default-dev, 
> librust-encoding-0.2+default-dev, librust-filetime-0.2+default-dev, 
> librust-flate2-1+rust-backend-dev, librust-futures-0.3+default-dev, 
> librust-fs-err-2+default-dev, librust-futures-locks-0.7+default-dev, 
> librust-http-0.2+default-dev, librust-hyper-0.14+default-dev, 
> librust-hyper-0.14+server-dev, librust-is-terminal-0.4+default-dev, 
> librust-itertools-0.10+default-dev, librust-jobserver-0.1+default-dev, 
> librust-libc-0.2+default-dev, librust-linked-hash-map-0.5+default-dev, 
> librust-log-0.4+default-dev, librust-memmap2-0.5+default-dev, 
> librust-mime-0.3+default-dev, librust-num-cpus-1+default-dev, 
> librust-number-prefix-0.4+default-dev, librust-object-0.30+default-dev, 
> librust-once-cell-1+default-dev (>= 1.17), librust-predicates-2+default-dev, 
> librust-rand-0.8+default-dev, librust-regex-1+default-dev, 
> librust-reqwest-0.11+blocking-dev, librust-reqwest-0.11+default-dev, 
> librust-reqwest-0.11+json-dev, librust-reqwest-0.11+stream-dev, 
> librust-retry-2+default-dev, librust-semver-1+default-dev, 
> librust-serde-1+default-dev, librust-serde-1+derive-dev, 
> librust-serde-json-1+default-dev, librust-serial-test-0.9+default-dev, 
> librust-sha2-0.10+default-dev, librust-strip-ansi-escapes-0.1+default-dev, 
> librust-tar-0.4+default-dev, librust-tempfile-3+default-dev, 
> librust-tokio-1+default-dev, librust-tokio-1+io-util-dev, 
> librust-tokio-1+macros-dev, librust-tokio-1+net-dev, 
> librust-tokio-1+process-dev, librust-tokio-1+rt-multi-thread-dev, 
> librust-tokio-1+time-dev, librust-tokio-serde-0.8+default-dev, 
> librust-tokio-util-0.7+codec-dev, librust-tokio-util-0.7+default-dev, 
> librust-tokio-util-0.7+io-dev, librust-toml-0.5+default-dev, 
> librust-tower-0.4+default-dev, librust-url-2+default-dev, 
> librust-uuid-1+default-dev, librust-uuid-1+v4-dev, 
> librust-walkdir-2+default-dev, librust-which-4-dev, librust-zip-0.6-dev, 
> librust-zstd-0.12+default-dev, libstring-shellquote-perl, rustc (>= 1.65), 
> build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-cargo, help2man, 
> librust-anyhow-1+backtrace-dev, librust-anyhow-1+default-dev, 
> librust-ar-0.9+default-dev, librust-assert-cmd-2+default-dev, 
> librust-async-trait-0.1+default-dev (>= 0.1.52), 
> librust-atty-0.2+default-dev, librust-base64-0.21+default-dev, 
> librust-bincode-1+default-dev, librust-blake3-1+default-dev, 
> librust-byteorder-1+default-dev, librust-bytes-1+default-dev, 
> librust-chrono-0.4+default-dev, librust-clap-4+default-dev, 
> librust-counted-array-0.1+default-dev, librust-daemonize-0.4+default-dev, 
> librust-directories-4+default-dev, librust-env-logger-0.9+default-dev, 
> librust-encoding-0.2+default-dev, librust-filetime-0.2+default-dev, 
> librust-flate2-1+rust-backend-dev, librust-futures-0.3+default-dev, 
> librust-fs-err-2+default-dev, 

Bug#1029410: marked as done (rt-extension-elapsedbusinesstime: autopkgtest failure)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 10:59:06 +
with message-id 
and subject line Bug#1029410: fixed in rt-extension-elapsedbusinesstime 0.05-5
has caused the Debian Bug report #1029410,
regarding rt-extension-elapsedbusinesstime: autopkgtest failure
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.)


-- 
1029410: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029410
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rt-extension-elapsedbusinesstime
Version: 0.05-1
Severity: serious

https://ci.debian.net/packages/r/rt-extension-elapsedbusinesstime/unstable/amd64/

...
autopkgtest [12:10:28]: test autodep8-perl: 
/usr/share/pkg-perl-autopkgtest/runner runtime-deps
autopkgtest [12:10:28]: test autodep8-perl: [---

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 
2>&1 exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test ' /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 
2>&1 produced no (non-whitelisted) output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/ElapsedBusinessTime.pm in 
@INC (you may need to install the RT::Extension::ElapsedBusinessTime module) 
(@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 exited successfully'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 106.

#   Failed test 'env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 produced no (non-whitelisted) 
output'
#   at /usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t line 110.
# Structures begin differing at:
#  $got->[0] = 'Can't locate RT/Extension/ElapsedBusinessTime.pm in 
@INC (you may need to install the RT::Extension::ElapsedBusinessTime module) 
(@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# '
# $expected->[0] = Does not exist
# Looks like you failed 4 tests of 4.
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t .. 
1..4
# Can't locate RT/Extension/ElapsedBusinessTime.pm in @INC (you may need to 
install the RT::Extension::ElapsedBusinessTime module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 1 -  /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 
exited successfully
not ok 2 -  /usr/bin/perl -w -M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 
produced no (non-whitelisted) output
# Can't locate RT/Extension/ElapsedBusinessTime.pm in @INC (you may need to 
install the RT::Extension::ElapsedBusinessTime module) (@INC contains: 
/etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.36.0 
/usr/local/share/perl/5.36.0 /usr/lib/x86_64-linux-gnu/perl5/5.36 
/usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base 
/usr/lib/x86_64-linux-gnu/perl/5.36 /usr/share/perl/5.36 
/usr/local/lib/site_perl).
# BEGIN failed--compilation aborted.
not ok 3 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 exited successfully
not ok 4 - env PERL_DL_NONLAZY=1  /usr/bin/perl -w 
-M"RT::Extension::ElapsedBusinessTime" -e 1 2>&1 produced no (non-whitelisted) 
output
Dubious, test returned 4 (wstat 1024, 0x400)
Failed 4/4 subtests 

Test Summary Report
---
/usr/share/pkg-perl-autopkgtest/runtime-deps.d/use.t (Wstat: 1024 (exited 4) 
Tests: 4 Failed: 4)
  Failed tests:  1-4
  Non-zero exit status: 4
Files=1, Tests=4,  0 wallclock secs ( 0.02 usr  0.00 sys +  0.07 cusr  0.01 
csys =  0.10 CPU)
Result: FAIL
...
--- End Message ---
--- Begin Message ---
Source: rt-extension-elapsedbusinesstime
Source-Version: 0.05-5
Done: Andrew Ruthven 

We believe that the bug you reported is 

Bug#1042484: util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5

[Vincent Lefevre]

On 2023-07-29 12:06:01 +0200, Helge Kreutzmann wrote:
> Hello Vincent,
> On Sat, Jul 29, 2023 at 11:48:57AM +0200, Vincent Lefevre wrote:
> > So I would say that this is rather a bug in src:manpages-l10n
> > 4.19.0-5 (the new version meant to be compatible with
> > util-linux-locales 2.39.1-3). Or am I missing something?
> 
> It is supposed to be deleted, but retained as broken symlink. I have a
> vague idea what might have happened, but I need to investigate.

The links are added by dh_link, with the .gz extension:

cventin:...pages-l10n-4.19.0> lf **/lastb*
lrwxrwxrwx 1 vlefevre vlefevre 9 2023-07-29 12:29:59 
debian/manpages-de/usr/share/man/de/man1/lastb.1.gz -> last.1.gz
lrwxrwxrwx 1 vlefevre vlefevre 9 2023-07-29 12:33:32 
debian/manpages-es/usr/share/man/es/man1/lastb.1.gz -> last.1.gz
lrwxrwxrwx 1 vlefevre vlefevre 9 2023-07-29 12:37:06 
debian/manpages-fr/usr/share/man/fr/man1/lastb.1.gz -> last.1.gz
[...]

but 
https://salsa.debian.org/debian/manpages-l10n/-/commit/eb4ed081ed33e54228978c68318994e5e6edeb05
("Further removals for util-linux transfer: Also the symlink ones (part 2)")
shows lines like

  rm -f debian/manpages-es/usr/share/man/es/man1/lastb.1

without the .gz extension.

I suspect that this is the problem.

Also I have the impression that these rm are done too early
(before dh_link is called):

[...]
rm -f debian/manpages-uk/usr/share/man/uk/man8/wipefs.8
rm -f debian/manpages-uk/usr/share/man/uk/man8/zramctl.8
make[1]: Leaving directory '/home/vlefevre/tmp/manpages-l10n-4.19.0'
   dh_perl
   dh_link

but I'm not sure (the build is not finished on my machine).

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

Bug#1042484: also affects manpages-de

[Helge Kreutzmann]

Hello all,
On Sat, Jul 29, 2023 at 10:20:40AM +, Holger Levsen wrote:
> this also affects manpages-de:

… and others. I'm already fixing it, no need to file further bugs atm
(i.e. before -6 is uploaded).

Greetings

  Helge


-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Bug#1042484: util-linux-locales: /usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5

[Helge Kreutzmann]

Hello Vincent,
On Sat, Jul 29, 2023 at 12:40:41PM +0200, Vincent Lefevre wrote:
> On 2023-07-29 12:06:01 +0200, Helge Kreutzmann wrote:
> > Hello Vincent,
> > On Sat, Jul 29, 2023 at 11:48:57AM +0200, Vincent Lefevre wrote:
> > > So I would say that this is rather a bug in src:manpages-l10n
> > > 4.19.0-5 (the new version meant to be compatible with
> > > util-linux-locales 2.39.1-3). Or am I missing something?
> > 
> > It is supposed to be deleted, but retained as broken symlink. I have a
> > vague idea what might have happened, but I need to investigate.
> 
> The links are added by dh_link, with the .gz extension:

Yes, I'm already in the process of updating my build rules.

Greetings

Helge
-- 
  Dr. Helge Kreutzmann deb...@helgefjell.de
   Dipl.-Phys.   http://www.helgefjell.de/debian.php
64bit GNU powered gpg signed mail preferred
   Help keep free software "libre": http://www.ffii.de/


signature.asc
Description: PGP signature

Processed: reassign 1042484 to manpages-fr,manpages-fr-extra,manpages-de,manpages-es,manpages-es-extra,manpages-uk,util-linux-locales

[Debian Bug Tracking System]

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

> reassign 1042484 
> manpages-fr,manpages-fr-extra,manpages-de,manpages-es,manpages-es-extra,manpages-uk,util-linux-locales
Bug #1042484 [util-linux-locales,manpages-fr] util-linux-locales: 
/usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Bug reassigned from package 'util-linux-locales,manpages-fr' to 
'manpages-fr,manpages-fr-extra,manpages-de,manpages-es,manpages-es-extra,manpages-uk,util-linux-locales'.
Ignoring request to alter found versions of bug #1042484 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1042484 to the same values 
previously set
> thanks
Stopping processing here.

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

Bug#1042185: marked as done (emacs: FTBFS: configure: error: in `/<>/debian/build-gtk')

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 10:37:11 +
with message-id 
and subject line Bug#1042185: fixed in emacs 1:28.2+1-16
has caused the Debian Bug report #1042185,
regarding emacs: FTBFS: configure: error: in `/<>/debian/build-gtk'
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.)


-- 
1042185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emacs
Version: 1:28.2+1-15
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230726 ftbfs-trixie

Hi,

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

Maybe related to GCC 13?


Relevant part (hopefully):
> checking for xcrun... no
> checking for GNU Make... make
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking whether the C compiler works... no
> configure: error: in `/<>/debian/build-gtk'
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> make[1]: *** [debian/rules:326: debian/stamp-configured] Error 77
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/emacs_28.2+1-15_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=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: emacs
Source-Version: 1:28.2+1-16
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated emacs 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, 29 Jul 2023 10:31:54 +0100
Source: emacs
Architecture: source
Version: 1:28.2+1-16
Distribution: unstable
Urgency: medium
Maintainer: Rob Browning 
Changed-By: Sean Whitton 
Closes: 1042185
Changes:
 emacs (1:28.2+1-16) unstable; urgency=medium
 .
   * Switch to gcc-13 & restore versioned gcc build-dep (Closes: #1042185).
Checksums-Sha1:
 f91252f38f541ef87b28bb2f4fe3980260b78666 3003 emacs_28.2+1-16.dsc
 1d060ca8bba6a5e1c44ecd1de49dfd030e39ea2a 122832 emacs_28.2+1-16.debian.tar.xz
Checksums-Sha256:
 13abfdd79771543ba772243d723d61be084e2f31379aa9d9e239d51cf22e5b74 3003 
emacs_28.2+1-16.dsc
 799969798476b8296d84026f77120a877491bd8bd05fc96feb71c0703cce321b 122832 
emacs_28.2+1-16.debian.tar.xz
Files:
 dff0f4aa77a5147f5c58aed45cc56cff 3003 editors optional emacs_28.2+1-16.dsc
 377da21036b59e522c18430e073cfac9 122832 editors optional 
emacs_28.2+1-16.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmTE5I8ACgkQaVt65L8G
YkAJeQ//VsLfKCkT9fIwmtu4GEIaveOOPyr3P+Jwb/hdG+dUZXypd0/Z+UevZzqJ
RHrvxrSuXfBsNH6bY6cKyRX6QqzqcDNFK2qIllRH1nbF0Hs+sIgVlj6Zie9AwNZo
/IuSWPrOwvfDFK4ksEGocudOhyu3avePcHFWg6t0z95GF/yObhZr9F7xmxynMYg1
C7bY/8bfkU6GsGkh3rr//cKkH1Jp8cNZ5MOBGk3b3d1Q0hK/j7KyDbhxeAvu5mol
TQWvEbLzKpv0OJdF+mNHqoa354wWAPPFNOzb1jaQDTkezZcr+9ABHzr7/f6NaAOI
yvfI55oFIOhRifHjlHWP37CjYZfJ8CkJomaT+Z6RnGm2kWlzLpdaB8WHlSubTfft
JT50L/dD1ShJ76YiqkVdAHJUDNfc+HJ7cgjL+i32Uqi+5y5ijvlHtbs4vKOjO+cT
WhwBkD9KGWbFy9mmEvXKcVkYbkEw0bnKBKQIup0Ew3OGN/19SXO7mJ6rKxwSMEBY
2qX7hj9o1FjI29jBX9530xzj1IqHbaQE4k1zUxO0D610HxaPm47XGgiXCgqFKNFt
Mmb/EwzEDWwzGnl7wDDQ5Cj87xE/V8H/g/qEKrOjdFG/jpUdShM3XT0im4h6WkcU
U27aTJxlmjW/Gsyh6NNpzDYZ9qw6MZ6jxYlx6JKl+NjTumON3IA=
=eKky
-END PGP SIGNATURE End Message ---

Bug#1041876: marked as done (nix FTBFS on !amd64)

[Debian Bug Tracking System]

Your message dated Sat, 29 Jul 2023 10:38:07 +
with message-id 
and subject line Bug#1041876: fixed in nix 2.16.1+dfsg-2
has caused the Debian Bug report #1041876,
regarding nix FTBFS on !amd64
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.)


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

https://buildd.debian.org/status/logs.php?pkg=nix=2.16.1%2Bdfsg-1

...
src/libcmd/repl.cc:18:10: fatal error: editline.h: No such file or directory
   18 | #include 
  |  ^~~~
compilation terminated.
--- End Message ---
--- Begin Message ---
Source: nix
Source-Version: 2.16.1+dfsg-2
Done: Jordan Justen 

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

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

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

Debian distribution maintenance software
pp.
Jordan Justen  (supplier of updated nix 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, 29 Jul 2023 01:41:24 -0700
Source: nix
Architecture: source
Version: 2.16.1+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Jordan Justen 
Changed-By: Jordan Justen 
Closes: 1041876
Changes:
 nix (2.16.1+dfsg-2) unstable; urgency=medium
 .
   * d/patches: Fix build error for !amd64 (Closes: #1041876)
Checksums-Sha1:
 19ac9bfc4f025eb8156cd41cd237e714084480e8 2636 nix_2.16.1+dfsg-2.dsc
 bba7964e8f9383d9d81e97a087d55a5af92174e6 14532 nix_2.16.1+dfsg-2.debian.tar.xz
 bf5448a8faf199db48b3ddb6316fab6664fd61e8 8270 
nix_2.16.1+dfsg-2_source.buildinfo
Checksums-Sha256:
 63d3e941f3e79b1504a3488764dc31a36b0d2a15c40265579d6d2c845dc03a6c 2636 
nix_2.16.1+dfsg-2.dsc
 6d16aa21e7dd0b47f93663ba73478a80ebd94bdb5a57ff867bcdb87e4ce12f65 14532 
nix_2.16.1+dfsg-2.debian.tar.xz
 5a9485ed7683cb73b4c15ad21ad8fb81012881495051295856418f2d445df08e 8270 
nix_2.16.1+dfsg-2_source.buildinfo
Files:
 e4d4e9e937d8df91e9ba6e52b986d8a2 2636 devel optional nix_2.16.1+dfsg-2.dsc
 ae524fd8fbb2bd56f1aaa8693640b62a 14532 devel optional 
nix_2.16.1+dfsg-2.debian.tar.xz
 d876d03107c076b99fe242cbfb4285c7 8270 devel optional 
nix_2.16.1+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwnSFIXQUyd8CMWwuN/mfaMr5kusFAmTE0TYACgkQN/mfaMr5
kuvnnw/9H44816JYTaq9KKetCjxeeJlnF0UE832RMcLbEvbYjZBx13VKCPRfdLVO
m8wrZdppXYUBijMgkdGU/aHOZb7mOec+It17yiNGhXHNH/hb8N1Frbfn01nc5pXA
+iO5aCvxZqgQE9Rap71QA4f3AS5CTHjj6qvlSCzj3HoJt0n9CjuVO+DXz2wZvC4Z
8D3jyybzAl7CFosq9oIDAD4wz4PCWfb5xbXclB7n1dGa6kyA+Bs8Gm3CGD9yKgnu
4AWHhKczFlfSWdTqtOp2l7pTNFO2dY9ARkbcNmHH65+4aPdZT/Ha38sNZAQLx5yz
r2S1oc1Sfepumlvb1dq0XmlBaV4Xo8G7pMPruXvGVKDNBi14H/GUoGrPyk8b5Gq8
bImyxjOHVOesN2rfy9Ay/8Nkp5u0vAZqEzBq+MgyRkZtge5EnInCE496WyKhMwH1
QuyRzZum8+pa4dzSBxx81Fkaai99tu5Fw1Bkl+bfGOTtCqz0nsqFQMbXyYvUq19/
MBeUKY1pb4eCI5rASWqpJ6gBLibkjWnrfzLy2qF8+ztJmsKPM6EtkWgybx+/Ui5W
otqlfaOMmXAtAiliobiD8sJIOtXFW/fKC7Wn4DQg2PmhT9bKSgVw3F3XfgfsklQu
eSBWBNPE0C1K3tHFMQxsmhLPTqry0EeCYGpLsSYe6FBQPjfHlRk=
=jmp9
-END PGP SIGNATURE End Message ---

Bug#1042484: also affects manpages-de

[Holger Levsen]

hi,

this also affects manpages-de:

Unpacking util-linux-locales (2.39.1-3) ...
dpkg: error processing archive 
/tmp/apt-dpkg-install-F9u7fI/693-util-linux-locales_2.39.1-3_all.deb (--unpack):
 trying to overwrite '/usr/share/man/de/man1/lastb.1.gz', which is also in 
package manpages-de 4.19.0-5

from 
https://jenkins.debian.net/job/reproducible_debian_live_build_standard_sid/534/consoleFull


-- 
cheers,
Holger

 ⢀⣴⠾⠻⢶⣦⠀
 ⣾⠁⢠⠒⠀⣿⡁  holger@(debian|reproducible-builds|layer-acht).org
 ⢿⡄⠘⠷⠚⠋⠀  OpenPGP: B8BF54137B09D35CF026FE9D 091AB856069AAA1C
 ⠈⠳⣄

Some of my friends and I overcommit to things, so we made "Saying No to Things"
punch cards. If you say no to 10 things, your friends have to buy you an ice
cream. In a pilot study, we found participants both said no to more things and
got more free ice cream. (@leah_pierson)


signature.asc
Description: PGP signature

Processed: cloning 1042484, reassign -1 to manpages-fr

[Debian Bug Tracking System]

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

> clone 1042484 -1
Bug #1042484 [util-linux-locales,manpages-fr] util-linux-locales: 
/usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Bug 1042484 cloned as bug 1042502
> reassign -1 manpages-fr 4.19.0-3
Bug #1042502 [util-linux-locales,manpages-fr] util-linux-locales: 
/usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Bug reassigned from package 'util-linux-locales,manpages-fr' to 'manpages-fr'.
Ignoring request to alter found versions of bug #1042502 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1042502 to the same values 
previously set
Bug #1042502 [manpages-fr] util-linux-locales: 
/usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Marked as found in versions manpages-l10n/4.19.0-3.
> thanks
Stopping processing here.

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

Processed: reassign 1042484 to util-linux-locales,manpages-fr

[Debian Bug Tracking System]

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

> reassign 1042484 util-linux-locales,manpages-fr
Bug #1042484 [util-linux-locales] util-linux-locales: 
/usr/share/man/fr/man1/lastb.1.gz is also in package manpages-fr 4.19.0-5
Bug reassigned from package 'util-linux-locales' to 
'util-linux-locales,manpages-fr'.
No longer marked as found in versions util-linux/2.39.1-3.
Ignoring request to alter fixed versions of bug #1042484 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: affects 1042498

[Debian Bug Tracking System]

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

> affects 1042498 binutils
Bug #1042498 [libgprofng0] libgprofng0: broken symbols file leads to 
unsatisfiable dependencies
Added indication that 1042498 affects binutils
> thanks
Stopping processing here.

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

Processed: block 1000004 with 1042501

[Debian Bug Tracking System]

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

> block 104 with 1042501
Bug #104 [src:pcre-ocaml] pcre-ocaml: depends on obsolete pcre3 library
104 was blocked by: 1042499
104 was not blocking any bugs.
Added blocking bug(s) of 104: 1042501
> thanks
Stopping processing here.

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

Processed: bug 1042501 is forwarded to https://github.com/ocsigen/ocsigenserver/pull/229

[Debian Bug Tracking System]

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

> forwarded 1042501 https://github.com/ocsigen/ocsigenserver/pull/229
Bug #1042501 [src:ocsigenserver] Depends on obsolete pcre
Set Bug forwarded-to-address to 
'https://github.com/ocsigen/ocsigenserver/pull/229'.
> thanks
Stopping processing here.

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

Processed: block 1000004 with 1042499

[Debian Bug Tracking System]

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

> block 104 with 1042499
Bug #104 [src:pcre-ocaml] pcre-ocaml: depends on obsolete pcre3 library
104 was not blocked by any bugs.
104 was not blocking any bugs.
Added blocking bug(s) of 104: 1042499
> thanks
Stopping processing here.

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