Bug#1043102: libflatbuffers-dev: Try to overwrite flatbuffers.pc already in package libflatbuffers2

[Christian Marillat]

Package: libflatbuffers-dev
Version: 2.0.8+dfsg1-5
Severity: serious

Dear Maintainer,

Error message in French.

,
| Dépaquetage de libflatbuffers-dev:amd64 (2.0.8+dfsg1-5) sur (2.0.8+dfsg1-4) 
...
| dpkg: erreur de traitement de l'archive 
/tmp/apt-dpkg-install-Qf2whY/01-libflatbuffers-dev_2.0.8+dfsg1-5_amd64.deb 
(--unpack) :
|  tentative de remplacement de « 
/usr/lib/x86_64-linux-gnu/pkgconfig/flatbuffers.pc », qui appartient aussi au 
paquet libflatbuffers2:amd64 2.0.8+dfsg1-4
`

Christian

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

Kernel: Linux 6.4.8-1-custom (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libflatbuffers-dev depends on:
ii  flatbuffers-compiler-dev  2.0.8+dfsg1-5
ii  libflatbuffers2   2.0.8+dfsg1-5

libflatbuffers-dev recommends no packages.

libflatbuffers-dev suggests no packages.

-- no debconf information

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Nicholas D Steeves]

Hi,

Reply follows inline.  Can we move this discussion to #1016558 to not
bother Axel with our discussion?

Manphiz  writes:

> Nicholas D Steeves  writes:
 Nicholas D Steeves  writes:

> Thanks!  Though I'm not really a user of muse-el, I'd like to keep it in
> a good shape as an exercise as an Emacs addon maintainer.  It looks like
> there is not too much work thanks to Elisp being a fairly stable
> language :)

That's fine, thank you once again for adopting it, and yes, generally
everything is ok :)

>>> [1] https://salsa.debian.org/emacsen-team/muse-el/-/merge_requests/3
>>
> Thanks for the tips!  I checked the Debian Policy Upgrading Checklist[1]
> and agreed with Debian Janitor on the "no changes are needed" bit.  And
> to avoid having to wait for the bot to do the rebase I've manually
> resolved the conflicts and rebased my MR on top of it as well.
>

You're welcome, and good call.

>> Let me know when your done, and we can talk about the next steps.
>
> Now all MRs are merged.  Please advise the next steps.  Thanks!
>

Wonderful!  I also see you have a GPG key now.  Have you generated
revocations certificates yet?

  https://wiki.debian.org/Keysigning#Step_2:_Generate_a_revocation_certificate

Next, where can I find your key?  I'm assuming that you're committed to
maintaining this identity for the foreseeable future, and that you'd
like to build reputation for future involvement in Debian.  It's not
required at the stage you're at, but it's recommended.

  https://wiki.debian.org/Keysigning#Step_3:_Make_your_public_key_public

The subkey that I was able to download didn't include any identities.

Other than that, this package isn't quite ready to upload, because there
are three unaddressed lintian warnings.

  https://wiki.debian.org/Lintian

Best,
Nicholas


signature.asc
Description: PGP signature

Bug#1037729: libmygpo-qt: diff for NMU version 1.1.0-4.1

[Boyuan Yang]

Control: tags 1037729 + patch
Control: tags 1037729 + pending
X-Debbugs-CC: cont...@thomaspierson.fr lu...@debian.org

Dear maintainer,

I've prepared an NMU for libmygpo-qt (versioned as 1.1.0-4.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

The full debdiff is provided in the attachment.

Regards.

diff -Nru libmygpo-qt-1.1.0/debian/changelog libmygpo-qt-
1.1.0/debian/changelog
--- libmygpo-qt-1.1.0/debian/changelog  2020-10-05 03:03:40.0 -0400
+++ libmygpo-qt-1.1.0/debian/changelog  2023-08-05 21:43:16.0 -0400
@@ -1,3 +1,19 @@
+libmygpo-qt (1.1.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild against Qt5 5.15.10.
+  * debian/libmygpo-qt5-1.symbols: Review symbols:
++ Drop commented missing symbols. They are from standard c++ library and
Qt5
+  library that should not be tracked here.
++ Drop disappeared symbols in Qt 5.15.10 rebuild (Closes: #1037729). The
+  newly-disappeared symbols are all Qt5 symbols that are meaningless
here.
+  * debian/patches:
++ Re-generate patches using "gbp pq" for unified format.
++ fix-tests-because-qt-isodate-behavior-change.patch: Fix patch format to
+  avoid dpkg-source warning "unexpected end of diff".
+
+ -- Boyuan Yang   Sat, 05 Aug 2023 21:43:16 -0400
diff -Nru libmygpo-qt-1.1.0/debian/changelog libmygpo-qt-1.1.0/debian/changelog
--- libmygpo-qt-1.1.0/debian/changelog	2020-10-05 03:03:40.0 -0400
+++ libmygpo-qt-1.1.0/debian/changelog	2023-08-05 21:43:16.0 -0400
@@ -1,3 +1,19 @@
+libmygpo-qt (1.1.0-4.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Rebuild against Qt5 5.15.10.
+  * debian/libmygpo-qt5-1.symbols: Review symbols:
++ Drop commented missing symbols. They are from standard c++ library and Qt5
+  library that should not be tracked here.
++ Drop disappeared symbols in Qt 5.15.10 rebuild (Closes: #1037729). The
+  newly-disappeared symbols are all Qt5 symbols that are meaningless here.
+  * debian/patches:
++ Re-generate patches using "gbp pq" for unified format.
++ fix-tests-because-qt-isodate-behavior-change.patch: Fix patch format to
+  avoid dpkg-source warning "unexpected end of diff".
+
+ -- Boyuan Yang   Sat, 05 Aug 2023 21:43:16 -0400
+
 libmygpo-qt (1.1.0-4) unstable; urgency=medium
 
   * Bump standard version to 4.5.0, no changes needed.
diff -Nru libmygpo-qt-1.1.0/debian/libmygpo-qt5-1.symbols libmygpo-qt-1.1.0/debian/libmygpo-qt5-1.symbols
--- libmygpo-qt-1.1.0/debian/libmygpo-qt5-1.symbols	2020-10-05 03:03:40.0 -0400
+++ libmygpo-qt-1.1.0/debian/libmygpo-qt5-1.symbols	2023-08-05 21:43:16.0 -0400
@@ -8,13 +8,11 @@
  _ZN10QByteArrayC2Ev@Base 1.0.9
  _ZN10QByteArrayD1Ev@Base 1.0.9
  _ZN10QByteArrayD2Ev@Base 1.0.9
-#MISSING: 1.1.0-4# _ZN10QByteArrayaSEOS_@Base 1.0.9
  _ZN10QByteArraypLERKS_@Base 1.0.9
  (optional=templinst)_ZN12QMapNodeBase25callDestructorIfNecessaryI7QStringEENSt9enable_ifIXsr9QTypeInfoIT_E9isComplexEvE4typeERS4_@Base 1.0.9
  (optional=templinst)_ZN12QMapNodeBase25callDestructorIfNecessaryI8QVariantEENSt9enable_ifIXsr9QTypeInfoIT_E9isComplexEvE4typeERS4_@Base 1.0.9
  _ZN12QMapNodeBase8setColorENS_5ColorE@Base 1.1.0
  _ZN12QMapNodeBase9setParentEPS_@Base 1.1.0
-#MISSING: 1.1.0-4# _ZN4QUrlaSEOS_@Base 1.0.9
  _ZN5QCharC1E11QLatin1Char@Base 1.0.9
  _ZN5QCharC2E11QLatin1Char@Base 1.0.9
  _ZN5mygpo10ApiRequest10searchOpmlERK7QString@Base 1.0.9
@@ -235,13 +233,10 @@
  _ZN7QStringC2Ev@Base 1.0.9
  _ZN7QStringD1Ev@Base 1.0.9
  _ZN7QStringD2Ev@Base 1.0.9
-#MISSING: 1.1.0-4# _ZN7QStringaSEOS_@Base 1.0.9
-#MISSING: 1.1.0-4# _ZN7QStringpLERKS_@Base 1.0.9
  _ZN8QVariant7PrivateC1ERKS0_@Base 1.0.9
  _ZN8QVariant7PrivateC1Ev@Base 1.0.9
  _ZN8QVariant7PrivateC2ERKS0_@Base 1.0.9
  _ZN8QVariant7PrivateC2Ev@Base 1.0.9
-#MISSING: 1.1.0-4# _ZN8QVariant8data_ptrEv@Base 1.0.9
  (optional=templinst)_ZN8QVariant8setValueI14QSharedPointerIN5mygpo13EpisodeActionvRKT_@Base 1.0.9
  (optional=templinst)_ZN8QVariant8setValueI14QSharedPointerIN5mygpo3TagvRKT_@Base 1.0.9
  (optional=templinst)_ZN8QVariant8setValueI14QSharedPointerIN5mygpo6DevicevRKT_@Base 1.0.9
@@ -249,11 +244,7 @@
  (optional=templinst)_ZN8QVariant8setValueI14QSharedPointerIN5mygpo7PodcastvRKT_@Base 1.0.9
  _ZN8QVariantC1Ev@Base 1.0.9
  _ZN8QVariantC2Ev@Base 1.0.9
-#MISSING: 1.1.0-4# _ZN8QVariantaSEOS_@Base 1.0.9
  _ZN9QDateTime4swapERS_@Base 1.0.9
-#MISSING: 1.1.0-4# _ZN9QDateTimeaSEOS_@Base 1.0.9
-#MISSING: 1.1.0-3# _ZN9QListData7disposeEv@Base 1.0.9
-#MISSING: 1.1.0-3# _ZNK10QByteArraycvPKcEv@Base 1.0.9
  _ZNK5mygpo10DeviceList10metaObjectEv@Base 1.0.9
  _ZNK5mygpo10DeviceList11devicesListEv@Base 1.0.9
  _ZNK5mygpo10DeviceList7devicesEv@Base 1.0.9
@@ -333,10 +324,6 @@
  _ZNK5mygpo8Settings10metaObjectEv@Base 1.0.9
  _ZNK5mygpo8Settings8settingsEv@Base 1.0.9
  _ZNK7QString3argEiii5QChar@Base 1.0.9
-#MISSING: 1.1.0-3# _ZNK7QString4sizeEv@Base 1.0.9
-#MISSING: 1.1.0-3# _ZNK7QString6isNullEv@Base 

Processed: libmygpo-qt: diff for NMU version 1.1.0-4.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1037729 + patch
Bug #1037729 [src:libmygpo-qt] libmygpo-qt: ftbfs with GCC-13
Bug #1042149 [src:libmygpo-qt] libmygpo-qt: FTBFS: dpkg-gensymbols: error: some 
symbols or patterns disappeared in the symbols file: see diff output below
Added tag(s) patch.
Added tag(s) patch.
> tags 1037729 + pending
Bug #1037729 [src:libmygpo-qt] libmygpo-qt: ftbfs with GCC-13
Bug #1042149 [src:libmygpo-qt] libmygpo-qt: FTBFS: dpkg-gensymbols: error: some 
symbols or patterns disappeared in the symbols file: see diff output below
Added tag(s) pending.
Added tag(s) pending.

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

Bug#1043051: marked as done (rust-rustls-webpki: Fails to build without internet access)

[Debian Bug Tracking System]

Your message dated Sun, 06 Aug 2023 00:21:45 +
with message-id 
and subject line Bug#1043051: fixed in rust-rustls-webpki 0.101.2-2
has caused the Debian Bug report #1043051,
regarding rust-rustls-webpki: Fails to build without internet access
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.)


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

rust-rustls-webpki fails to build without internet access

Full build log
==
https://launchpad.net/ubuntu/+source/rust-rustls-webpki/0.101.2-1/+latestbuild/amd64

Build log excerpt
=
   dh_auto_test -O--buildsystem=cargo
/<>/debian/dh-cargo/bin/cargo test
debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose',
'--verbose', '-j8', '--target', 'x86_64-unknown-linux-gnu',
'--release'],) {}
Updating git repository `https://github.com/est31/rcgen.git`
warning: spurious network error (2 tries remaining): failed to resolve
address for github.com: Temporary failure in name resolution;
class=Net (12)
warning: spurious network error (1 tries remaining): failed to resolve
address for github.com: Temporary failure in name resolution;
class=Net (12)
error: failed to load source for dependency `rcgen`

Caused by:
  Unable to update https://github.com/est31/rcgen.git

Caused by:
  failed to clone into:
/<>/debian/cargo_home/git/db/rcgen-8bc4158ba396894b

Caused by:
  network failure seems to have happened
  if a proxy or similar is necessary `net.git-fetch-with-cli` may help here
  https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli

Caused by:
  failed to resolve address for github.com: Temporary failure in name
resolution; class=Net (12)
dh_auto_test: error: /<>/debian/dh-cargo/bin/cargo test
returned exit code 101

Thank you,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Source: rust-rustls-webpki
Source-Version: 0.101.2-2
Done: Jonas Smedegaard 

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 06 Aug 2023 01:21:20 +0200
Source: rust-rustls-webpki
Architecture: source
Version: 0.101.2-2
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard 
Changed-By: Jonas Smedegaard 
Closes: 1043051
Changes:
 rust-rustls-webpki (0.101.2-2) unstable; urgency=medium
 .
   * add patch to avoid Cargo patch;
 build- and autopkgtest-depend on package for crate rcgen;
 closes: bug#1043051, thanks to Jeremy Bícha
Checksums-Sha1:
 6f2b1c121e3282e55f98dcb36d97d74e0ce49b17 2649 rust-rustls-webpki_0.101.2-2.dsc
 69d45d1597f9ab3b1653e874f4fbf9f2dd012514 14052 
rust-rustls-webpki_0.101.2-2.debian.tar.xz
 709f4d3c1b97f9efcc25f07fb33eb8cabbf00b29 10963 
rust-rustls-webpki_0.101.2-2_amd64.buildinfo
Checksums-Sha256:
 5f435420f60b62eecd82bd1043765b3d290d2437500734913621d9f649b9 2649 
rust-rustls-webpki_0.101.2-2.dsc
 cef1dae901e9566e6ef44f2f4db787411cd67b22a0a5d4b0cec2e1a75f9e1c55 14052 
rust-rustls-webpki_0.101.2-2.debian.tar.xz
 9bd8920e0487945c81dfe806b9b2f1593fb3cd82177f3bfd60b9d2018d7a4ffc 10963 
rust-rustls-webpki_0.101.2-2_amd64.buildinfo
Files:
 40ac5b82f36d5a0051d68f7dd8e9e486 2649 rust optional 
rust-rustls-webpki_0.101.2-2.dsc
 5cd1fe5edbae605d3c2c750121a60a81 14052 rust optional 
rust-rustls-webpki_0.101.2-2.debian.tar.xz
 d93b5edb765591f45f415a6a32f12ca3 10963 rust optional 
rust-rustls-webpki_0.101.2-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmTO2gsACgkQLHwxRsGg

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Manphiz]

Nicholas D Steeves  writes:

> Hello,
>
> Manphiz  writes:
>
>>> Nicholas D Steeves  writes:
>>>
>>
>> Hi Nicholas,
>>
>> I have now prepared a merge request to migrate away from assoc.el[1] and
>> also forwarded the patch upstream.  Also set the package as team
>> maintained and add myself as an upload.  PTAL.  Thanks!
>
> Wow, that was fast!  LTGM, with one caveat: You are an Uploader for this
> package now, so please drop the "Team upload" line entirely.  This makes
> you the human maintainer for the package, so I have sent you an invitation
> for salsa/gitlab maintainer permissions for muse-el.

Thanks!  Though I'm not really a user of muse-el, I'd like to keep it in
a good shape as an exercise as an Emacs addon maintainer.  It looks like
there is not too much work thanks to Elisp being a fairly stable
language :)

>
>> [1] https://salsa.debian.org/emacsen-team/muse-el/-/merge_requests/3
>
> You will notice that there are two other MRs.  Please double-check that
> the bot did its work correctly, and please manually go through the
> Debian Policy upgrade checklist, starting with the version muse-el uses,
> and each version up to and including the one the bot proposed.  If you
> would like to take credit for this work, I recommend adding "and your
> name" to the changelog entries the bot proposes.
>
>  [ The name of the bot and your name ]
>
> In other words, I would like to give you permission to write to this
> repo!  Bots will often rebase their MRs to save you time, and I will
> leave the decision of what gets merged first, and what gets rebased up
> to you.

Thanks for the tips!  I checked the Debian Policy Upgrading Checklist[1]
and agreed with Debian Janitor on the "no changes are needed" bit.  And
to avoid having to wait for the bot to do the rebase I've manually
resolved the conflicts and rebased my MR on top of it as well.

>
> Let me know when your done, and we can talk about the next steps.

Now all MRs are merged.  Please advise the next steps.  Thanks!

>
> Cheers,
> Nicholas
>

[1] https://www.debian.org/doc/debian-policy/upgrading-checklist.html

-- 
Manphiz


signature.asc
Description: PGP signature

Bug#1038422: marked as done (ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000])

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 22:04:02 +
with message-id 
and subject line Bug#1038422: fixed in ntpsec 1.2.2+dfsg1-1+deb12u1
has caused the Debian Bug report #1038422,
regarding ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]
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.)


-- 
1038422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038422
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ntpsec
Version: 1.2.2+dfsg1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: forest.ow...@riseup.net

Dear Maintainer,

I updated the Debian release from bullseye to bookworm.  With that update
the ntp package (ntpd 4.2.8p15) was replaced by ntpsec.  The ntpsec version
of ntpd starts as expected, but randomly crashes in a few hours.  It reports
the following information to the kern.log file:
2023-06-17T01:12:52.873519+00:00 karita kernel: [258683.650167] ntpd[23269]: 
segfault at 10 ip 7f6d3ece0ab3 sp 7ffc9c364830 error 4 in 
libcrypto.so.3[7f6d3ecc5000+278000] likely on CPU 1 (core 0, socket 1)
2023-06-17T01:12:52.873554+00:00 karita kernel: [258683.650185] Code: 1f 84 00 
00 00 00 00 48 83 ec 08 48 c7 c0 ff ff ff ff 48 85 ff 0f 84 63 04 00 00 48 85 
d2 0f 84 5a 04 00 00 41 ba 00 08 00 10 <0f> 10 07 0f 57 e4 44 23 15 e4 fa 39 00 
48 8d 42 10 81 fe 00 01 00

Obviously, once the software crashes it stops functioning.

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

Kernel: Linux 6.1.0-9-amd64 (SMP w/2 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 /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ntpsec depends on:
ii  adduser3.134
ii  init-system-helpers1.65.2
ii  libbsd00.11.7-2
ii  libc6  2.36-9
ii  libcap21:2.66-4
ii  libssl33.0.9-1
ii  lsb-base   11.6
ii  netbase6.4
ii  python33.11.2-1+b1
ii  python3-ntp1.2.2+dfsg1-1
ii  sysvinit-utils [lsb-base]  3.06-4
ii  tzdata 2023c-5

Versions of packages ntpsec recommends:
ii  cron [cron-daemon]  3.0pl1-162
ii  systemd 252.6-1

Versions of packages ntpsec suggests:
ii  apparmor   3.0.8-3
pn  certbot
pn  ntpsec-doc 
pn  ntpsec-ntpviz  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: ntpsec
Source-Version: 1.2.2+dfsg1-1+deb12u1
Done: Richard Laager 

We believe that the bug you reported is fixed in the latest version of
ntpsec, 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.
Richard Laager  (supplier of updated ntpsec 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 15:52:36 -0500
Source: ntpsec
Architecture: source
Version: 1.2.2+dfsg1-1+deb12u1
Distribution: bookworm-security
Urgency: high
Maintainer: Richard Laager 
Changed-By: Richard Laager 
Closes: 1038422
Changes:
 ntpsec (1.2.2+dfsg1-1+deb12u1) bookworm-security; urgency=high
 .
   * Fix cookie crash.
 Thanks to Hal Murray (Closes: 1038422)
Checksums-Sha1:
 d9293079d6c8901204d874fbd4ec20f34dd0dfab 2654 ntpsec_1.2.2+dfsg1-1+deb12u1.dsc
 bc8d5a18dcebc470360a640df530849f7d58461e 2317956 ntpsec_1.2.2+dfsg1.orig.tar.xz
 112aba0694f9dec70723acafdee171efc020c41f 57944 
ntpsec_1.2.2+dfsg1-1+deb12u1.debian.tar.xz
 7e5f76bbb55dd14cd01fa78d16cc74006a28abd3 8781 
ntpsec_1.2.2+dfsg1-1+deb12u1_source.buildinfo
Checksums-Sha256:
 27e51bc1203b1dfc945bf7f3298840709e1731984a078461b5a8e58cde917b91 2654 
ntpsec_1.2.2+dfsg1-1+deb12u1.dsc
 53e527e3d04d551d41af2d359c2715c2de5f5bfa2a695d4ec1a811b3e9137f63 2317956 
ntpsec_1.2.2+dfsg1.orig.tar.xz
 4f3ffb5ce6d93a257ffe4c145ea781b946772ca8394f85e924b830488c1323d2 57944 
ntpsec_1.2.2+dfsg1-1+deb12u1.debian.tar.xz
 

Bug#1040225: marked as done (python-django: CVE-2023-36053)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 22:04:10 +
with message-id 
and subject line Bug#1040225: fixed in python-django 3:3.2.19-1+deb12u1
has caused the Debian Bug report #1040225,
regarding python-django: CVE-2023-36053
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.)


-- 
1040225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.10.7-2+deb9u17
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2023-36053[0]:
| In Django 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3,
| EmailValidator and URLValidator are subject to a potential ReDoS
| (regular expression denial of service) attack via a very large
| number of domain name labels of emails and URLs.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-36053
https://www.cve.org/CVERecord?id=CVE-2023-36053


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 3:3.2.19-1+deb12u1
Done: Chris Lamb 

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Jul 2023 14:24:04 +0100
Source: python-django
Binary: python-django-doc python3-django
Built-For-Profiles: nocheck
Architecture: source all
Version: 3:3.2.19-1+deb12u1
Distribution: bookworm-security
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Description:
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework
Closes: 1040225
Changes:
 python-django (3:3.2.19-1+deb12u1) bookworm-security; urgency=high
 .
   * CVE-2023-36053: Potential regular expression denial of service
 vulnerability in EmailValidator/URLValidator.
 .
 EmailValidator and URLValidator were subject to potential regular
 expression denial of service attack via a very large number of domain name
 labels of emails and URLs. (Closes: #1040225)
 .
   * Add/apply the URLValidator patch from sid.
Checksums-Sha1:
 09c5f6d18db38a947afba98160a378177f51c5a6 2839 
python-django_3.2.19-1+deb12u1.dsc
 42f62327acc78f37f69cba058232fbfd7d8c77cd 9832772 
python-django_3.2.19.orig.tar.gz
 2dd63ab49ea36d669433c06fca3401de370b9e08 41392 
python-django_3.2.19-1+deb12u1.debian.tar.xz
 940d0d823598fa391cffee670fabd51ed5c0c788 2926288 
python-django-doc_3.2.19-1+deb12u1_all.deb
 33b04f9a4c2c523b5e11268c7ac06abc8ee34c87 8096 
python-django_3.2.19-1+deb12u1_amd64.buildinfo
 3e3865dffa81d5c3f6ff0ee4412c2156787e24c4 2824248 
python3-django_3.2.19-1+deb12u1_all.deb
Checksums-Sha256:
 6e758c03a8beeef4d4e2e3f55790da7bd1303c8d27f3250690f3f9200fe6d53f 2839 
python-django_3.2.19-1+deb12u1.dsc
 031365bae96814da19c10706218c44dff3b654cc4de20a98bd2d29b9bde469f0 9832772 
python-django_3.2.19.orig.tar.gz
 834c695665965af1433467ed67a60be1b201b16573e745275f764a2fd314accf 41392 
python-django_3.2.19-1+deb12u1.debian.tar.xz
 9178e37263bab1a84129c15e03ed1c66c4acb1e1156189527bb64772f9b528f9 2926288 
python-django-doc_3.2.19-1+deb12u1_all.deb
 57a18360c0e48eec8d6118620ba927105662e0df7f32b1127f4a8d021a224a34 8096 
python-django_3.2.19-1+deb12u1_amd64.buildinfo
 6a16d41810c1efeb013f72275df9e88033461888c873e5470eb032fadf4d9078 2824248 
python3-django_3.2.19-1+deb12u1_all.deb
Files:
 ca5d2af0394a80ec710e352e4fdef0d7 2839 python optional 
python-django_3.2.19-1+deb12u1.dsc
 d84f0b8669678fea14579d7400a521e2 9832772 python optional 
python-django_3.2.19.orig.tar.gz
 57c2fba6730c6882408feafdb848de57 41392 python optional 

Bug#1040521: tpm2-tss: FTBFS (test failures)

[Ying-Chun Liu (PaulLiu)]

Hi.

Some updates.

I fixed one of the failed test on s390x.
https://github.com/tpm2-software/tpm2-tss/pull/2675
So now libtpms tests passed. (test/unit/tcti-libtpms).

The problem here is that it tries to make a call to libtpms but passing (size_t 
*) to (uint32_t *).
That works in little-endian (if the memory are cleared to zero and alignment are padded) but not 
working on bit-endian (the value will be changed).


The patch is as attachment.

But there are 3 more test that needed to be fixed.
1. test/unit/fapi-eventlog
2. test/unit/tcti-spi-helper
3. test/unit/fapi-ima-eventlog

I'll find some time to fix the rest of the failure and do a single upload that fixes every s390x 
test failure.


Yours,
Paul
From 9ae85535d6383a50731ad9e70c16b55622e126ae Mon Sep 17 00:00:00 2001
From: "Ying-Chun Liu (PaulLiu)" 
Date: Sun, 6 Aug 2023 05:24:02 +0800
Subject: [PATCH] tss2-tcti: tcti-libtpms: fix test failure on big-endian
 platform

Due to tcti_libtpms->response_len and tcti_libtpms->response_buffer_len
are size_t. We cannot convert the (size_t *) to (uint32_t *) on big-endian
platforms. Thus we create temp uint32_t variables. Make the call and
then assign it back to size_t variables.

This commit partially fix the test failure on big-endian platforms.

Signed-off-by: Ying-Chun Liu (PaulLiu) 
---
 src/tss2-tcti/tcti-libtpms.c | 11 +--
 1 file changed, 9 insertions(+), 2 deletions(-)

diff --git a/src/tss2-tcti/tcti-libtpms.c b/src/tss2-tcti/tcti-libtpms.c
index 922a4402..10ed913d 100644
--- a/src/tss2-tcti/tcti-libtpms.c
+++ b/src/tss2-tcti/tcti-libtpms.c
@@ -370,6 +370,8 @@ tcti_libtpms_transmit(
 tpm_header_t header;
 TSS2_RC rc;
 TPM_RESULT ret;
+uint32_t resp_size;
+uint32_t respbufsize;
 
 rc = tcti_common_transmit_checks(tcti_common, cmd_buf, TCTI_LIBTPMS_MAGIC);
 if (rc != TSS2_RC_SUCCESS) {
@@ -386,11 +388,16 @@ tcti_libtpms_transmit(
 }
 
 LOGBLOB_DEBUG(cmd_buf, size, "Sending command with TPM_CC 0x%" PRIx32, header.size);
+resp_size = (uint32_t) tcti_libtpms->response_len;
+respbufsize = (uint32_t) tcti_libtpms->response_buffer_len;
 LIBTPMS_API_CALL(fail, tcti_libtpms, TPMLIB_Process, _libtpms->response_buffer,
- (uint32_t *) _libtpms->response_len,
- (uint32_t *) _libtpms->response_buffer_len,
+ (uint32_t *) _size,
+ (uint32_t *) ,
  (uint8_t *) cmd_buf,
  size);
+tcti_libtpms->response_len = resp_size;
+tcti_libtpms->response_buffer_len = respbufsize;
+
 rc = tcti_libtpms_store_state(tcti_libtpms);
 if (rc != TSS2_RC_SUCCESS) {
 LOG_ERROR("Failed to store state file");
-- 
2.40.1



OpenPGP_0x44173FA13D05.asc
Description: OpenPGP public key


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1043066: marked as done (python-pyepics: hard-coded dependencies on libca4.13.5 and libcom3.17.6)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 21:24:04 +
with message-id 
and subject line Bug#1043066: fixed in python-pyepics 3.5.1+ds-1
has caused the Debian Bug report #1043066,
regarding python-pyepics: hard-coded dependencies on libca4.13.5 and 
libcom3.17.6
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.)


-- 
1043066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pyepics
Version: 3.4.1+ds-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

epics-base is currently transitioning away from libca4.13.5 and
libcom3.17.6. python-pyepics hard-codes dependencies on those packages,
though.

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: python-pyepics
Source-Version: 3.5.1+ds-1
Done: Picca Frédéric-Emmanuel 

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

Debian distribution maintenance software
pp.
Picca Frédéric-Emmanuel  (supplier of updated python-pyepics 
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, 05 Aug 2023 21:01:18 +0200
Source: python-pyepics
Architecture: source
Version: 3.5.1+ds-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PaN Maintainers 

Changed-By: Picca Frédéric-Emmanuel 
Closes: 1043066
Changes:
 python-pyepics (3.5.1+ds-1) unstable; urgency=medium
 .
   [ Neil Williams ]
   * Update control to remove myself from Uploaders
 .
   [ Picca Frédéric-Emmanuel ]
   * New upstream version 3.5.1+ds
   * Bug fix: "hard-coded dependencies on libca4.13.5 and libcom3.17.6",
 thanks to Sebastian Ramacher (Closes: #1043066).
Checksums-Sha1:
 fcb13d3442ab1b59ad649a5d07424cb59666edad 2606 python-pyepics_3.5.1+ds-1.dsc
 fa516841994cf7164a5f52fda6169e3d1dccce83 865504 
python-pyepics_3.5.1+ds.orig.tar.xz
 67ad1a44c760d0ebdf62bb8577b2e007595fd555 9264 
python-pyepics_3.5.1+ds-1.debian.tar.xz
Checksums-Sha256:
 7785cf4ffa1897a08cad30a7fcbba7b123d511070264a9b83caff58d4e554d87 2606 
python-pyepics_3.5.1+ds-1.dsc
 b167eb91e8a31b470756671261cc280f58356841804e9e1b84250eb1fede2a59 865504 
python-pyepics_3.5.1+ds.orig.tar.xz
 67bda7c92561df0e90d72743f5233e27710678358a77d0092c70dfa1ec7b2941 9264 
python-pyepics_3.5.1+ds-1.debian.tar.xz
Files:
 bddc25726f075dbcc58449abe70bd04f 2606 python optional 
python-pyepics_3.5.1+ds-1.dsc
 26b903fad9f784cdf5539eb0be867093 865504 python optional 
python-pyepics_3.5.1+ds.orig.tar.xz
 b60ccf009aafa8e800c77f9a2a3c687d 9264 python optional 
python-pyepics_3.5.1+ds-1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE2bRTt5m4gw2UXmoKW/VOXhK5ALsFAmTOnWoRHHBpY2NhQGRl
Ymlhbi5vcmcACgkQW/VOXhK5ALuIrhAArMJyK2b9tUmcW0Jz0oi3RHZlFJv8ke97
SmxA2GbDksNLtLAMFawOJEQ7T/Sh6YE0k5pgj9XitFQeFB2ahCu85TZlmL6BxvF0
eSdsJCdEgA/pwQsWx+66LYNEU+Y3Gq5opkj4uBH1mMaSMebAuArmNEa788HeECht
MFt+oQ+psm5Fxgqogdh2Cb8GSBp6nHUbrG7HXMsBYYMY9l2G5QhPKxgpWqnvbdxW
+7pp5XufCZZCbCP9CEwT5Qz09+coXnDEM5/tJcnLH3WXZgAlDMTBKgBmD+Y61spY
R+2/cBpXyXIPPIFBoomT5U4BEAs2x7I8/5NoOVbWAz17apXH9WYMLj8EtwtG8I6H
10vcQH+jVZFokd1ZClfEL4VXuyKH7P/ydsMSEVWEpXKZc67oEDav2OcjgmAO0qc4
1/s28Bu8lX6CQ9HelKwXceckaJeuN97yU1cwMOuW2xJiW9iZkjUlX0M8tJyl+Wd4
6n7UpwDkSDyRgdMd4WRjjkge8hQGD6hmBImUn0ljUa6ptW1pl5hqGl0yFKc3uzyJ
/5NpWI4utSxWMe2uY2kI9j1NflwjWpEwXRW84+UZ7O56jhh/Sq+Qy34lNRqCoqW6
BRlOA8Nny8LgjWbWl5kXRirvRVZ0eb2mpmgUGZegUA40M+Egx122aXSNp/5xvsHR
xD4PEbZtH8U=
=vIxL
-END PGP SIGNATURE End Message ---

Bug#943578: marked as done (fluxbox: FTBFS due to undefined references)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:49:53 +
with message-id 
and subject line Bug#943578: fixed in fluxbox 1.3.7-1
has caused the Debian Bug report #943578,
regarding fluxbox: FTBFS due to undefined references
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.)


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

Hi,

fluxbox/experimental FTBFS in a current sid/experimental pbuilder
environment:

g++  -g -O2 -fdebug-prefix-map=/build/fluxbox-1.3.7=. -fstack-protector-strong 
-Wformat -Werror=format-security  -lfontconfig -lfreetype -lfribidi -lXft 
-lXrender -lX11 -Wl,-z,relro -o testDemandAttention src/test
s/testDemandAttention-testDemandAttention.o libFbTk.a src/defaults.o -lX11  
-lrt  -lm
/usr/bin/ld: libFbTk.a(libFbTk_a-FbString.o): in function 
`makeVisualFromLogical':
./src/FbTk/FbString.cc:91: undefined reference to `fribidi_charset_to_unicode'
/usr/bin/ld: ./src/FbTk/FbString.cc:96: undefined reference to `fribidi_log2vis'
/usr/bin/ld: ./src/FbTk/FbString.cc:99: undefined reference to 
`fribidi_unicode_to_charset'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function 
`FbTk::Transparent::freeDest()':
./src/FbTk/Transparent.cc:213: undefined reference to `XRenderFreePicture'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function 
`FbTk::Transparent::setDest(unsigned long, int)':
./src/FbTk/Transparent.cc:232: undefined reference to `XRenderFindVisualFormat'
/usr/bin/ld: ./src/FbTk/Transparent.cc:245: undefined reference to 
`XRenderCreatePicture'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function 
`FbTk::Transparent::render(int, int, int, int, unsigned int, unsigned int) 
const':
./src/FbTk/Transparent.cc:306: undefined reference to `XRenderComposite'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function 
`FbTk::Transparent::freeAlpha()':
./src/FbTk/Transparent.cc:334: undefined reference to `XRenderFreePicture'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function 
`FbTk::Transparent::~Transparent()':
./src/FbTk/Transparent.cc:194: undefined reference to `XRenderFreePicture'
/usr/bin/ld: ./src/FbTk/Transparent.cc:197: undefined reference to 
`XRenderFreePicture'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function `createAlphaPic':
./src/FbTk/Transparent.cc:49: undefined reference to `XRenderFindFormat'
/usr/bin/ld: ./src/FbTk/Transparent.cc:72: undefined reference to 
`XRenderCreatePicture'
/usr/bin/ld: ./src/FbTk/Transparent.cc:92: undefined reference to 
`XRenderFillRectangle'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function 
`FbTk::Transparent::Transparent(unsigned long, unsigned long, int, int)':
./src/FbTk/Transparent.cc:171: undefined reference to `XRenderFindVisualFormat'
/usr/bin/ld: ./src/FbTk/Transparent.cc:175: undefined reference to 
`XRenderCreatePicture'
/usr/bin/ld: ./src/FbTk/Transparent.cc:180: undefined reference to 
`XRenderCreatePicture'
/usr/bin/ld: libFbTk.a(libFbTk_a-Transparent.o): in function 
`FbTk::Transparent::setSource(unsigned long, int)':
./src/FbTk/Transparent.cc:276: undefined reference to `XRenderFindVisualFormat'
/usr/bin/ld: ./src/FbTk/Transparent.cc:287: undefined reference to 
`XRenderCreatePicture'
/usr/bin/ld: ./src/FbTk/Transparent.cc:266: undefined reference to 
`XRenderFreePicture'
/usr/bin/ld: libFbTk.a(libFbTk_a-XftFontImp.o): in function 
`FbTk::XftFontImp::~XftFontImp()':
./src/FbTk/XftFontImp.cc:47: undefined reference to `XftFontClose'
/usr/bin/ld: libFbTk.a(libFbTk_a-XftFontImp.o): in function 
`FbTk::XftFontImp::load(std::__cxx11::basic_string, std::allocator > const&)':
./src/FbTk/XftFontImp.cc:55: undefined reference to `XftFontOpenXlfd'
/usr/bin/ld: ./src/FbTk/XftFontImp.cc:66: undefined reference to `XftFontClose'
/usr/bin/ld: ./src/FbTk/XftFontImp.cc:57: undefined reference to 
`XftFontOpenName'
/usr/bin/ld: libFbTk.a(libFbTk_a-XftFontImp.o): in function 
`FbTk::XftFontImp::drawText(FbTk::FbDrawable const&, int, _XGC*, char const*, 
unsigned long, int, int, FbTk::Orientation)':
./src/FbTk/XftFontImp.cc:115: undefined reference to `XftDrawCreate'
/usr/bin/ld: ./src/FbTk/XftFontImp.cc:135: undefined reference to 
`XftColorAllocValue'
/usr/bin/ld: ./src/FbTk/XftFontImp.cc:153: undefined reference to 
`XftDrawString8'
/usr/bin/ld: ./src/FbTk/XftFontImp.cc:156: undefined reference to `XftColorFree'
/usr/bin/ld: ./src/FbTk/XftFontImp.cc:157: undefined reference 

Bug#1037012: marked as done (gconf: Intent to remove from Debian)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:48:39 +
with message-id 
and subject line Bug#1043068: Removed package(s) from unstable
has caused the Debian Bug report #1037012,
regarding gconf: Intent to remove from Debian
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.)


-- 
1037012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037012
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gconf
Version: 3.2.6-8
Severity: serious
Tags: unstable trixie

I intend to file a bug requesting that ftpmasters remove gconf from
Debian Unstable soon after the Debian 12 release.

gconf is only included in Debian 12 to provide the migration utility
away from gconf for alarm-clock-applet and mssh. Since that migration
will be complete in Debian 12, there is no need for future Debian
releases to include gconf.

On behalf of the Debian GNOME team,
Jeremy Bícha
--- End Message ---
--- Begin Message ---
Version: 3.2.6-8+rm

Dear submitter,

as the package gconf 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/1043068

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#999175: marked as done (asterisk-prompt-fr-proformatique: missing required debian/rules targets build-arch and/or build-indep)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:47:12 +
with message-id 
and subject line Bug#1043038: Removed package(s) from unstable
has caused the Debian Bug report #999175,
regarding asterisk-prompt-fr-proformatique: missing required debian/rules 
targets build-arch and/or build-indep
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.)


-- 
999175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=999175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk-prompt-fr-proformatique
Version: 20070706-1.4-2.1
Severity: important
Justification: Debian Policy section 4.9
Tags: bookworm sid
User: debian...@lists.debian.org
Usertags: missing-build-arch-indep

Dear maintainer,

Your package does not include build-arch and/or build-indep targets in
debian/rules. This is required by Debian Policy section 4.9, since 2012.
https://www.debian.org/doc/debian-policy/ch-source.html#main-building-script-debian-rules

Please note that this is also a sign that the packaging of this software
could benefit from a refresh. For example, packages using 'dh' cannot be
affected by this issue.

This mass bug filing was discussed on debian-devel@ in
https://lists.debian.org/debian-devel/2021/11/msg00052.html .
The severity of this bug will be changed to 'serious' after a month.

Best,

Lucas
--- End Message ---
--- Begin Message ---
Version: 20070706-1.4-2.1+rm

Dear submitter,

as the package asterisk-prompt-fr-proformatique 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/1043038

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#984286: marked as done (pcb2gcode: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:46:45 +
with message-id 
and subject line Bug#1043012: Removed package(s) from unstable
has caused the Debian Bug report #984286,
regarding pcb2gcode: ftbfs with GCC-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.)


-- 
984286: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984286
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pcb2gcode
Version: 1.1.4-git20120902-1.1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/pcb2gcode_1.1.4-git20120902-1.1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
 from svg_exporter.cpp:25:
/usr/include/gtk-2.0/gtk/gtktypeutils.h:236:64: warning: ‘GTypeDebugFlags’ is 
deprecated [-Wdeprecated-declarations]
  236 | voidgtk_type_init   (GTypeDebugFlagsdebug_flags);
  |^
In file included from /usr/include/glib-2.0/gobject/gobject.h:24,
 from /usr/include/glib-2.0/gobject/gbinding.h:29,
 from /usr/include/glib-2.0/glib-object.h:22,
 from /usr/include/glib-2.0/gio/gioenums.h:28,
 from /usr/include/glib-2.0/gio/giotypes.h:28,
 from /usr/include/glib-2.0/gio/gio.h:26,
 from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30,
 from /usr/include/gtk-2.0/gdk/gdk.h:32,
 from /usr/include/gtk-2.0/gtk/gtk.h:32,
 from /usr/include/gerbv-2.7.0/gerbv.h:77,
 from svg_exporter.hpp:36,
 from svg_exporter.cpp:25:
/usr/include/glib-2.0/gobject/gtype.h:685:3: note: declared here
  685 | } GTypeDebugFlags GLIB_DEPRECATED_TYPE_IN_2_36;
  |   ^~~
In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31,
 from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30,
 from /usr/include/gtk-2.0/gtk/gtk.h:126,
 from /usr/include/gerbv-2.7.0/gerbv.h:77,
 from svg_exporter.hpp:36,
 from svg_exporter.cpp:25:
/usr/include/gtk-2.0/gtk/gtktooltips.h:73:12: warning: ‘GTimeVal’ is 
deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations]
   73 |   GTimeVal last_popdown;
  |^~~~
In file included from /usr/include/glib-2.0/glib/galloca.h:32,
 from /usr/include/glib-2.0/glib.h:30,
 from /usr/include/gerbv-2.7.0/gerbv.h:76,
 from svg_exporter.hpp:36,
 from svg_exporter.cpp:25:
/usr/include/glib-2.0/glib/gtypes.h:545:26: note: declared here
  545 | typedef struct _GTimeVal GTimeVal 
GLIB_DEPRECATED_TYPE_IN_2_62_FOR(GDateTime);
  |  ^~~~
In file included from gerberimporter.hpp:27,
 from surface.hpp:39,
 from board.hpp:46,
 from exporter.hpp:38,
 from svg_exporter.hpp:46,
 from svg_exporter.cpp:25:
importer.hpp:48:17: error: ISO C++17 does not allow dynamic exception 
specifications

Bug#965421: marked as done (asterisk-prompt-fr-proformatique: Removal of obsolete debhelper compat 5 and 6 in bookworm)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:47:12 +
with message-id 
and subject line Bug#1043038: Removed package(s) from unstable
has caused the Debian Bug report #965421,
regarding asterisk-prompt-fr-proformatique: Removal of obsolete debhelper 
compat 5 and 6 in bookworm
to be marked as done.

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

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


-- 
965421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: asterisk-prompt-fr-proformatique
Version: 20070706-1.4-2
Severity: normal
Usertags: compat-5-6-removal

Hi,

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

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

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

  * Compat 7 is the bare minimum


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

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


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


Thanks,
~Niels


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

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

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

Mind you, it is still your responsibility to ensure that the upload
makes it into testing even if you upload before that date.
--- End Message ---
--- Begin Message ---
Version: 20070706-1.4-2.1+rm

Dear submitter,

as the package asterisk-prompt-fr-proformatique 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/1043038

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#825098: marked as done (pcb2gcode: new upstream homepage and new release (1.2.3))

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:46:45 +
with message-id 
and subject line Bug#1043012: Removed package(s) from unstable
has caused the Debian Bug report #825098,
regarding pcb2gcode: new upstream homepage and new release (1.2.3)
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.)


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

Source: pcb2gcode
Version: 1.1.4-git20120902-1
Severity: wishlist

Hi Maintainer

The upstream pcb2gcode project has relocated to GitHub [1].

There is also a new upstream release (1.2.3) [2].

Regards
Graham


[1] https://github.com/pcb2gcode/pcb2gcode
[2] https://github.com/pcb2gcode/pcb2gcode/releases/tag/v1.2.3
--- End Message ---
--- Begin Message ---
Version: 1.1.4-git20120902-1.1+rm

Dear submitter,

as the package pcb2gcode 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/1043012

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#1040225: marked as done (python-django: CVE-2023-36053)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:36:33 +
with message-id 
and subject line Bug#1040225: fixed in python-django 2:2.2.28-1~deb11u2
has caused the Debian Bug report #1040225,
regarding python-django: CVE-2023-36053
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.)


-- 
1040225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040225
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.10.7-2+deb9u17
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2023-36053[0]:
| In Django 3.2 before 3.2.20, 4 before 4.1.10, and 4.2 before 4.2.3,
| EmailValidator and URLValidator are subject to a potential ReDoS
| (regular expression denial of service) attack via a very large
| number of domain name labels of emails and URLs.


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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-36053
https://www.cve.org/CVERecord?id=CVE-2023-36053


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.2.28-1~deb11u2
Done: Chris Lamb 

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Jul 2023 14:19:58 +0100
Source: python-django
Binary: python-django-doc python3-django
Built-For-Profiles: nocheck
Architecture: source all
Version: 2:2.2.28-1~deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Description:
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework
Closes: 1030251 1031290 1035467 1040225
Changes:
 python-django (2:2.2.28-1~deb11u2) bullseye-security; urgency=high
 .
   * CVE-2023-23969: Potential denial-of-service via Accept-Language headers.
 .
 The parsed values of Accept-Language headers are cached in order to avoid
 repetitive parsing. This leads to a potential denial-of-service vector via
 excessive memory usage if large header values are sent.
 .
 In order to avoid this vulnerability, the Accept-Language header is now
 parsed up to a maximum length. (Closes: #1030251)
 .
   * CVE-2023-36053: Potential regular expression denial of service
 vulnerability in EmailValidator/URLValidator.
 .
 EmailValidator and URLValidator were subject to potential regular
 expression denial of service attack via a very large number of domain name
 labels of emails and URLs. (Closes: #1040225)
 .
   * CVE-2023-31047: Prevent a potential bypass of validation when uploading
 multiple files using one form field.
 .
 Uploading multiple files using one form field has never been supported by
 forms.FileField or forms.ImageField as only the last uploaded file was
 validated. Unfortunately, Uploading multiple files topic suggested
 otherwise. In order to avoid the vulnerability, the ClearableFileInput and
 FileInput form widgets now raise ValueError when the multiple HTML
 attribute is set on them. To prevent the exception and keep the old
 behavior, set the allow_multiple_selected attribute to True.
 (Closes: #1035467)
 .
   * CVE-2023-24580: Potential denial-of-service vulnerability in file uploads
 .
 Passing certain inputs to multipart forms could result in too many open
 files or memory exhaustion, and provided a potential vector for a
 denial-of-service attack. The number of files parts parsed is now limited
 via the new DATA_UPLOAD_MAX_NUMBER_FILES setting. (Closes: #1031290)
 .
   * Add/apply the URLValidator patch 

Bug#1035467: marked as done (python-django: CVE-2023-31047)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:36:33 +
with message-id 
and subject line Bug#1035467: fixed in python-django 2:2.2.28-1~deb11u2
has caused the Debian Bug report #1035467,
regarding python-django: CVE-2023-31047
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.)


-- 
1035467: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035467
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.11.29-1+deb10u7
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django:

  CVE-2023-31047: Potential bypass of validation when uploading
  multiple files using one form field

  Uploading multiple files using one form field has never been
  supported by forms.FileField or forms.ImageField as only the last
  uploaded file was validated. Unfortunately, Uploading multiple files
  topic suggested otherwise.

  In order to avoid the vulnerability, ClearableFileInput and
  FileInput` form widgets now raise ValueError when the multiple HTML
  attribute is set on them. To prevent the exception and keep the old
  behavior, set allow_multiple_selected to True.

  For more details on using the new attribute and handling of multiple
  files through a single field, see Uploading multiple files.

— 


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.2.28-1~deb11u2
Done: Chris Lamb 

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Jul 2023 14:19:58 +0100
Source: python-django
Binary: python-django-doc python3-django
Built-For-Profiles: nocheck
Architecture: source all
Version: 2:2.2.28-1~deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Description:
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework
Closes: 1030251 1031290 1035467 1040225
Changes:
 python-django (2:2.2.28-1~deb11u2) bullseye-security; urgency=high
 .
   * CVE-2023-23969: Potential denial-of-service via Accept-Language headers.
 .
 The parsed values of Accept-Language headers are cached in order to avoid
 repetitive parsing. This leads to a potential denial-of-service vector via
 excessive memory usage if large header values are sent.
 .
 In order to avoid this vulnerability, the Accept-Language header is now
 parsed up to a maximum length. (Closes: #1030251)
 .
   * CVE-2023-36053: Potential regular expression denial of service
 vulnerability in EmailValidator/URLValidator.
 .
 EmailValidator and URLValidator were subject to potential regular
 expression denial of service attack via a very large number of domain name
 labels of emails and URLs. (Closes: #1040225)
 .
   * CVE-2023-31047: Prevent a potential bypass of validation when uploading
 multiple files using one form field.
 .
 Uploading multiple files using one form field has never been supported by
 forms.FileField or forms.ImageField as only the last uploaded file was
 validated. Unfortunately, Uploading multiple files topic suggested
 otherwise. In order to avoid the vulnerability, the ClearableFileInput and
 FileInput form widgets now raise ValueError when the multiple HTML
 attribute is set on them. To prevent the exception and keep the old
 behavior, set the allow_multiple_selected attribute to True.
 (Closes: #1035467)
 .
   * CVE-2023-24580: Potential denial-of-service vulnerability in file uploads
 .
 Passing certain inputs to multipart forms could result in too many open
 files or memory 

Bug#1031290: marked as done (python-django: CVE-2023-24580 (denial-of-service vulnerability in file uploads))

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 20:36:33 +
with message-id 
and subject line Bug#1031290: fixed in python-django 2:2.2.28-1~deb11u2
has caused the Debian Bug report #1031290,
regarding python-django: CVE-2023-24580 (denial-of-service vulnerability in 
file uploads)
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.)


-- 
1031290: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031290
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.11.29-1+deb10u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2023-24580[0]:

  Potential denial-of-service vulnerability in file uploads

  Passing certain inputs to multipart forms could result in too many
  open files or memory exhaustion, and provided a potential vector for
  a denial-of-service attack.

  The number of files parts parsed is now limited via the new
  DATA_UPLOAD_MAX_NUMBER_FILES setting.

  

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

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2023-24580
https://www.cve.org/CVERecord?id=CVE-2023-24580


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 2:2.2.28-1~deb11u2
Done: Chris Lamb 

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

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

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

Debian distribution maintenance software
pp.
Chris Lamb  (supplier of updated python-django package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 28 Jul 2023 14:19:58 +0100
Source: python-django
Binary: python-django-doc python3-django
Built-For-Profiles: nocheck
Architecture: source all
Version: 2:2.2.28-1~deb11u2
Distribution: bullseye-security
Urgency: high
Maintainer: Debian Python Team 
Changed-By: Chris Lamb 
Description:
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework
Closes: 1030251 1031290 1035467 1040225
Changes:
 python-django (2:2.2.28-1~deb11u2) bullseye-security; urgency=high
 .
   * CVE-2023-23969: Potential denial-of-service via Accept-Language headers.
 .
 The parsed values of Accept-Language headers are cached in order to avoid
 repetitive parsing. This leads to a potential denial-of-service vector via
 excessive memory usage if large header values are sent.
 .
 In order to avoid this vulnerability, the Accept-Language header is now
 parsed up to a maximum length. (Closes: #1030251)
 .
   * CVE-2023-36053: Potential regular expression denial of service
 vulnerability in EmailValidator/URLValidator.
 .
 EmailValidator and URLValidator were subject to potential regular
 expression denial of service attack via a very large number of domain name
 labels of emails and URLs. (Closes: #1040225)
 .
   * CVE-2023-31047: Prevent a potential bypass of validation when uploading
 multiple files using one form field.
 .
 Uploading multiple files using one form field has never been supported by
 forms.FileField or forms.ImageField as only the last uploaded file was
 validated. Unfortunately, Uploading multiple files topic suggested
 otherwise. In order to avoid the vulnerability, the ClearableFileInput and
 FileInput form widgets now raise ValueError when the multiple HTML
 attribute is set on them. To prevent the exception and keep the old
 behavior, set the allow_multiple_selected attribute to True.
 (Closes: #1035467)
 .
   * CVE-2023-24580: Potential denial-of-service vulnerability in file uploads
 .
 Passing certain inputs to multipart forms could result in too many open
 files or memory exhaustion, and provided a potential 

Bug#1033808: ImportError: cannot import name 'Markup' from 'jinja2'

[supersonic]

Hi there,

this bug currently also prevents the salt-minion service (and possibly 
salt-master) from starting on Debian 12. The patch below to the file 
`/usr/lib/python3/dist-packages/salt/utils/jinja.py` allows the salt-minion to 
run and for its basic functions to work again. These Changes are already 
upstream in Salt v3004.2 (Debian 12 has v3004.1), see 
https://github.com/saltstack/salt/blob/v3004.2/salt/utils/jinja.py#L37  and 
https://github.com/saltstack/salt/blob/v3004.2/salt/utils/jinja.py#L715 .


I don't know if that's all, so I'll be testing for the next couple of weeks to 
see if any further things are broken during regular operation, but the basic 
functions I tested with the patch below all worked, so the patch could probably 
still be applied to restore basic functionality.



```
28c28
< from jinja2 import BaseLoader, Markup, TemplateNotFound, nodes
---
> from jinja2 import BaseLoader, TemplateNotFound, nodes
36a37,42
> try:
> from markupsafe import Markup
> except ImportError:
> # jinja < 3.1
> from jinja2 import Markup  # pylint: disable=no-name-in-module
>
707a714,717
> try:
> contextfunction = jinja2.contextfunction
> except AttributeError:
> contextfunction = jinja2.pass_context
709c719
< @jinja2.contextfunction
---
> @contextfunction
```


I don't know if I will find the time to become an official Debian contributor 
right now, so if anybody else can apply the patch, feel free to do so.



Best regards
Supersonic

Bug#1042911: Breaks Emacs 29.1 upgrade: muse-split.el:41:2: Error: Cannot open load file: No such file or directory, assoc

[Nicholas D Steeves]

Hello,

Manphiz  writes:

>> Nicholas D Steeves  writes:
>>
>
> Hi Nicholas,
>
> I have now prepared a merge request to migrate away from assoc.el[1] and
> also forwarded the patch upstream.  Also set the package as team
> maintained and add myself as an upload.  PTAL.  Thanks!

Wow, that was fast!  LTGM, with one caveat: You are an Uploader for this
package now, so please drop the "Team upload" line entirely.  This makes
you the human maintainer for the package, so I have sent you an invitation
for salsa/gitlab maintainer permissions for muse-el.

> [1] https://salsa.debian.org/emacsen-team/muse-el/-/merge_requests/3

You will notice that there are two other MRs.  Please double-check that
the bot did its work correctly, and please manually go through the
Debian Policy upgrade checklist, starting with the version muse-el uses,
and each version up to and including the one the bot proposed.  If you
would like to take credit for this work, I recommend adding "and your
name" to the changelog entries the bot proposes.

 [ The name of the bot and your name ]

In other words, I would like to give you permission to write to this
repo!  Bots will often rebase their MRs to save you time, and I will
leave the decision of what gets merged first, and what gets rebased up
to you.

Let me know when your done, and we can talk about the next steps.

Cheers,
Nicholas


signature.asc
Description: PGP signature

Bug#1040748: ftbfs in pycairo with meson 1.2.0 rc2

[Aurelien Jarno]

Hi,

On 2023-07-10 10:09, Simon McVittie wrote:
> On Sun, 09 Jul 2023 at 23:00:01 -0400, Eli Schwartz wrote:
> > The underlying cause is an additional feature
> > of meson:
> > 
> > https://mesonbuild.com/Release-notes-for-1-2-0.html#python-module-can-now-compile-bytecode
> > 
> > If this file is not desired in the debian package, please specify your
> > preferred value for this meson setting. For example, to avoid compiling
> > bytecode as part of `meson install`, you could setup the build system
> > with the `-Dpython.bytecompile=-1` option.
> 
> I think we probably want debhelper's meson build system backend
> (/usr/share/perl5/Debian/Debhelper/Buildsystem/meson.pm) to do this
> globally for all Meson-built packages, the same way it already handles
> cross-compilation, --prefix, --sysconfdir and so on, instead of having to
> do it per-package.

I understand the need to fix the issue globally on the debhelper or
meson side, and I have seen the bug #1042398. From my understanding we
won't have a solution soon, and in the meantime pycairo is not
buildable. This affects the riscv64 bootstrap, many packages are blocked
behind this.

Therefore I wonder if it should be possible to temporarily address the
issue directly in pycairo by passing -Dpython.bytecompile=-1 at the
configure step. I can offer to do a NMU if it can spare you some work.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net

Bug#1037869: marked as done (tcpflow: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 18:34:48 +
with message-id 
and subject line Bug#1037869: fixed in tcpflow 1.6.1-3
has caused the Debian Bug report #1037869,
regarding tcpflow: 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.)


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

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
../../../src/be13_api/dfxml/src/dfxml_writer.cpp:690:92: warning: macro 
"__TIME__" might prevent reproducible builds [-Wdate-time]
  690 | 
snprintf(buf,sizeof(buf),"%4d-%02d-%02dT%s",tm.tm_year+1900,tm.tm_mon+1,tm.tm_mday,__TIME__);
  | 
   ^~~~
g++ -std=c++17 -DHAVE_CONFIG_H -I. -I../../../src -I..  -I../../../src/be13_api 
-I../../../src/wifipcap -I/usr/local/include -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -DUTC_OFFSET=+  -g -g -O3 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -MD -D_FORTIFY_SOURCE=2 -Wpointer-arith -Wshadow 
-Wwrite-strings -Wcast-align -Wredundant-decls -Wdisabled-optimization 
-Wfloat-equal -Wmultichar -Wmissing-noreturn -Woverloaded-virtual -Wsign-promo 
-funit-at-a-time -Weffc++ -Wno-address-of-packed-member -c -o 
netviz/plot_view.o ../../../src/netviz/plot_view.cpp
In file included from ../../../src/be13_api/utf8.h:32,
 from ../../../src/be13_api/bulk_extractor_i.h:85,
 from ../../../src/tcpflow.h:255,
 from ../../../src/netviz/plot_view.cpp:12:
../../../src/be13_api/utf8/checked.h:268:34: warning: ‘template struct 
std::iterator’ is deprecated [-Wdeprecated-declarations]
  268 | class iterator : public std::iterator 
 {
  |  ^~~~
In file included from /usr/include/c++/13/bits/stl_iterator_base_funcs.h:66,
 from /usr/include/c++/13/string:47,
 from /usr/include/c++/13/bits/locale_classes.h:40,
 from /usr/include/c++/13/bits/ios_base.h:41,
 from /usr/include/c++/13/ios:44,
 from /usr/include/c++/13/ostream:40,
 from /usr/include/c++/13/iostream:41,
 from ../../../src/tcpflow.h:75:
/usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here
  127 | struct _GLIBCXX17_DEPRECATED iterator
  |  ^~~~
In file included from ../../../src/be13_api/utf8.h:33:
../../../src/be13_api/utf8/unchecked.h:179:40: warning: ‘template struct 
std::iterator’ is deprecated [-Wdeprecated-declarations]
  179 |   class iterator : public std::iterator 
 {
  |^~~~
/usr/include/c++/13/bits/stl_iterator_base_types.h:127:34: note: declared here
  127 | struct _GLIBCXX17_DEPRECATED iterator
  |  ^~~~
g++ -std=c++17 -DHAVE_CONFIG_H -I. -I../../../src -I..  -I../../../src/be13_api 
-I../../../src/wifipcap -I/usr/local/include -Wdate-time -D_FORTIFY_SOURCE=2 
-I/usr/local/include -DUTC_OFFSET=+  -g -g -O3 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wall -MD -D_FORTIFY_SOURCE=2 -Wpointer-arith -Wshadow 

Processed: tagging 1043071, tagging 1043070, tagging 1043067

[Debian Bug Tracking System]

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

> tags 1043071 + sid trixie
Bug #1043071 [src:crowdsec] crowdsec: FTBFS on amd64: test failure
Added tag(s) trixie and sid.
> tags 1043070 + sid trixie
Bug #1043070 [src:dh-make-golang] dh-make-golang: FTBFS
Added tag(s) trixie and sid.
> tags 1043067 + sid trixie
Bug #1043067 [src:x2gokdrive] FTBFS: This X2Go KDrive version does not support 
building against X.Org version 21.1.8.
Added tag(s) sid and trixie.
> thanks
Stopping processing here.

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

Bug#1043074: golang-v2ray-core: FTBFS

[Sebastian Ramacher]

Source: golang-v2ray-core
Version: 4.34.0+ds-1
Severity: serious
Tags: ftbfs sid trixie
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=golang-v2ray-core=amd64=4.34.0%2Bds-1%2Bb1=1691257483=0

dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 4 
-ldflags "-s -w -buildid= -X v2ray.com/core.codename=user -X 
v2ray.com/core.build=20230805-174417 -X v2ray.com/core.version=4.34.0" 
v2ray.com/core/main v2ray.com/core/main/confloader 
v2ray.com/core/main/confloader/external v2ray.com/core/main/distro/all 
v2ray.com/core/main/distro/debug v2ray.com/core/main/json 
v2ray.com/core/main/jsonem returned exit code 1
make[1]: *** [debian/rules:29: override_dh_auto_build] Error 25
make[1]: Leaving directory '/<>'

Cheers
-- 
Sebastian Ramacher

Processed: beaker: diff for NMU version 1.12.1-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1037035 + pending
Bug #1037035 [src:beaker] FTBFS due to tests relying on running redis server
Added tag(s) pending.

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

Bug#1037035: beaker: diff for NMU version 1.12.1-1.1

[Adrian Bunk]

Control: tags 1037035 + pending

Dear maintainer,

I've prepared an NMU for beaker (versioned as 1.12.1-1.1) and uploaded 
it to DELAYED/15. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru beaker-1.12.1/debian/changelog beaker-1.12.1/debian/changelog
--- beaker-1.12.1/debian/changelog	2023-02-09 20:37:53.0 +0200
+++ beaker-1.12.1/debian/changelog	2023-08-05 20:34:16.0 +0300
@@ -1,3 +1,11 @@
+beaker (1.12.1-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Apply patch from Shengjing Zhu to exclude tests relying on running
+redis server. (Closes: #1037035)
+
+ -- Adrian Bunk   Sat, 05 Aug 2023 20:34:16 +0300
+
 beaker (1.12.1-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru beaker-1.12.1/debian/rules beaker-1.12.1/debian/rules
--- beaker-1.12.1/debian/rules	2023-02-09 20:37:53.0 +0200
+++ beaker-1.12.1/debian/rules	2023-08-05 20:34:16.0 +0300
@@ -1,6 +1,6 @@
 #! /usr/bin/make -f
 
 export PYBUILD_NAME=beaker
-export PYBUILD_TEST_ARGS=--ignore=tests/test_memcached.py --ignore=tests/test_managers/test_ext_mongodb.py -k 'not test_cookie_expires_different_locale'
+export PYBUILD_TEST_ARGS=--ignore=tests/test_memcached.py --ignore-glob=tests/test_managers/test_ext_*.py -k 'not test_cookie_expires_different_locale'
 %:
 	dh $@ --with python3 --buildsystem=pybuild

Bug#1037594: Fixes for the gcc-13 ftbfs

[Andreas Hasenack]

attached fixes for the gcc-13 FTBFS
From e8d1d1486e3d9d8495af4c0903d6eb3e24a92094 Mon Sep 17 00:00:00 2001
From: Brecht Van Lommel 
Date: Wed, 18 Jan 2023 13:42:55 +0100
Subject: [PATCH] Fix T103960: build issue with GCC 13 in Cycles thread code

---
 intern/cycles/util/thread.cpp | 2 ++
 1 file changed, 2 insertions(+)

Origin: upstream, https://projects.blender.org/blender/blender/commit/e8d1d1486e3d9d8495af4c0903d6eb3e24a92094
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/2029503
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043014
Last-Update: 2023-08-05

diff --git a/intern/cycles/util/thread.cpp b/intern/cycles/util/thread.cpp
index f4949aa2b44..7f1e8eb4159 100644
--- a/intern/cycles/util/thread.cpp
+++ b/intern/cycles/util/thread.cpp
@@ -6,6 +6,8 @@
 #include "util/system.h"
 #include "util/windows.h"
 
+#include 
+
 CCL_NAMESPACE_BEGIN
 
 thread::thread(function run_cb) : run_cb_(run_cb), joined_(false)
From fea567651b5dadb71c830b17cbca31ed3f5b733e Mon Sep 17 00:00:00 2001
From: Bastien Montagne 
Date: Mon, 27 Mar 2023 18:29:39 +0200
Subject: [PATCH] Fix building Blender with some versions of gcc.

Seems like quadriflow was missing a header, which somehow made the build
fails on Suse Tumbleweed (gcc 13).
---
 extern/quadriflow/src/loader.cpp | 1 +
 1 file changed, 1 insertion(+)

Origin: upstream, https://projects.blender.org/blender/blender/commit/fea567651b5dadb71c830b17cbca31ed3f5b733e
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/blender/+bug/2029503
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043014
Last-Update: 2023-08-05

diff --git a/extern/quadriflow/src/loader.cpp b/extern/quadriflow/src/loader.cpp
index a1596eeff9a..5b9d717db71 100644
--- a/extern/quadriflow/src/loader.cpp
+++ b/extern/quadriflow/src/loader.cpp
@@ -8,6 +8,7 @@
 
 #include "loader.hpp"
 
+#include 
 #include 
 #include 
 

Bug#1043071: crowdsec: FTBFS on amd64: test failure

[Sebastian Ramacher]

Source: crowdsec
Version: 1.4.6-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=crowdsec=amd64=1.4.6-6%2Bb1=1691250195=0

panic: test timed out after 10m0s
running tests:
TestPluginWatcherInterval (9m21s)

goroutine 1446 [running]:
testing.(*M).startAlarm.func1()
/usr/lib/go-1.20/src/testing/testing.go:2241 +0x3c5
created by time.goFunc
/usr/lib/go-1.20/src/time/sleep.go:176 +0x32

goroutine 1 [chan receive, 9 minutes]:
testing.(*T).Run(0xc0003649c0, {0xbc3e75?, 0x5282e5?}, 0xc04718)
/usr/lib/go-1.20/src/testing/testing.go:1630 +0x405
testing.runTests.func1(0x10f5680?)
/usr/lib/go-1.20/src/testing/testing.go:2036 +0x45
testing.tRunner(0xc0003649c0, 0xc00029fc88)
/usr/lib/go-1.20/src/testing/testing.go:1576 +0x10b
testing.runTests(0xc000372b40?, {0x109db80, 0xb, 0xb}, {0xc00035c190?, 
0x100c00029fd10?, 0x10f4c60?})
/usr/lib/go-1.20/src/testing/testing.go:2034 +0x489
testing.(*M).Run(0xc000372b40)
/usr/lib/go-1.20/src/testing/testing.go:1906 +0x63a
main.main()
_testmain.go:67 +0x1aa

goroutine 194 [chan receive, 9 minutes]:
gopkg.in/tomb%2ev2.(*Tomb).Wait(0xc0004927d0)
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:126 +0x35
github.com/crowdsecurity/crowdsec/pkg/csplugin.resetTestTomb(0xcba2e0?, 
0xc7eb40)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher_test.go:20
 +0x45
github.com/crowdsecurity/crowdsec/pkg/csplugin.TestPluginWatcherInterval(0xc00036be00?)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher_test.go:76
 +0x2b4
testing.tRunner(0xc00041fd40, 0xc04718)
/usr/lib/go-1.20/src/testing/testing.go:1576 +0x10b
created by testing.(*T).Run
/usr/lib/go-1.20/src/testing/testing.go:1629 +0x3ea

goroutine 163 [select]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginBroker).Run(0xc000278640,
 0xc0004139f0)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker.go:104
 +0x12f
created by 
github.com/crowdsecurity/crowdsec/pkg/csplugin.TestBrokerRunTimeThreshold

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker_test.go:499
 +0x45b

goroutine 164 [select]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).watchPluginTicker(0xc000278688,
 {0xcc05e0, 0xd})

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:113
 +0x1a5
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).Start.func1()

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:72
 +0x25
gopkg.in/tomb%2ev2.(*Tomb).run(0xc000413a40, 0xc0003b0380?)
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:163 +0x36
created by gopkg.in/tomb%2ev2.(*Tomb).Go
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:159 +0xee

goroutine 32 [select, 9 minutes]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginBroker).Run(0xc000372460,
 0xc0004932c0)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker.go:104
 +0x12f
created by github.com/crowdsecurity/crowdsec/pkg/csplugin.TestBrokerNoThreshold

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/broker_test.go:282
 +0x30d

goroutine 175 [select]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).watchPluginTicker(0xc000372fe8,
 {0xc3b6f0, 0xd})

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:113
 +0x1a5
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).Start.func1()

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:72
 +0x25
gopkg.in/tomb%2ev2.(*Tomb).run(0xc0004925a0, 0xc000486288?)
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:163 +0x36
created by gopkg.in/tomb%2ev2.(*Tomb).Go
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:159 +0xee

goroutine 176 [select, 9 minutes]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).watchPluginAlertCounts(0xc000372fe8)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:152
 +0xad
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).Start.func2()

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:78
 +0x1d
gopkg.in/tomb%2ev2.(*Tomb).run(0xc0004925a0, 0xc00036b6c0?)
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:163 +0x36
created by gopkg.in/tomb%2ev2.(*Tomb).Go
/<>/_build/src/gopkg.in/tomb.v2/tomb.go:159 +0xee

goroutine 165 [select, 9 minutes]:
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).watchPluginAlertCounts(0xc000278688)

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:152
 +0xad
github.com/crowdsecurity/crowdsec/pkg/csplugin.(*PluginWatcher).Start.func2()

/<>/_build/src/github.com/crowdsecurity/crowdsec/pkg/csplugin/watcher.go:78
 +0x1d

Bug#1043070: dh-make-golang: FTBFS

[Sebastian Ramacher]

Source: dh-make-golang
Version: 0.6.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=dh-make-golang=amd64=0.6.0-2%2Bb6=1691250713=0

   dh_auto_build -a -O--builddirectory=_build -O--buildsystem=golang
cd _build && go install -trimpath -v -p 4 
github.com/Debian/dh-make-golang
src/github.com/Debian/dh-make-golang/check_depends.go:6:2: cannot find package 
"golang.org/x/tools/go/vcs" in any of:
/usr/lib/go-1.20/src/golang.org/x/tools/go/vcs (from $GOROOT)
/<>/_build/src/golang.org/x/tools/go/vcs (from $GOPATH)
dh_auto_build: error: cd _build && go install -trimpath -v -p 4 
github.com/Debian/dh-make-golang returned exit code 1
make: *** [debian/rules:6: binary-arch] Error 25
-- 
Sebastian Ramacher

Bug#1043067: FTBFS: This X2Go KDrive version does not support building against X.Org version 21.1.8.

[Aurelien Jarno]

Source: x2gokdrive
Version: 0.0.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear maintainer,

x2gokdrive fails to build from source on amd64 with the following error:


| + sed -r s/^AC_INIT[^,]*, ([^,]+),.*/\1/
| + export XORG_UPSTREAM_VERSION=21.1.8
| + cd /<>/BUILD/xorg-server
| + [ -d ../../patches.xorg/21.1.8 ]
| + set +x
| 
| ##
| ERROR: This X2Go KDrive version does not support
| building against X.Org version 21.1.8.
| ##
| make[1]: *** [debian/rules:26: override_dh_auto_configure] Error 1
| make[1]: Leaving directory '/<>'
| make: *** [debian/rules:15: binary] Error 2
| dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
| 

| Build finished at 2023-08-05T15:10:49Z 


The full build log on riscv64 is also available here:
https://buildd.debian.org/status/fetch.php?pkg=x2gokdrive=riscv64=0.0.0.1-1=1691247408=0

This is very likely due to the upload of xorg-server 2:21.1.8-1 to the
archive.

Regards
Aurelien

Processed: Re: Bug#1041258 closed by Debian FTP Masters (reply to Peter Michael Green ) (Bug#1041258: fixed in rust-fs-extra 1.3.0-2)

[Debian Bug Tracking System]

Processing control commands:

> reopen -1
Bug #1041258 {Done: Peter Michael Green } 
[src:rust-fs-extra] rust-fs-extra: FTBFS: test failures
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions rust-fs-extra/1.3.0-2.

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

Bug#1041258: closed by Debian FTP Masters (reply to Peter Michael Green ) (Bug#1041258: fixed in rust-fs-extra 1.3.0-2)

[Sebastian Ramacher]

Control: reopen -1

It still fails to build:
https://buildd.debian.org/status/fetch.php?pkg=rust-fs-extra=amd64=1.3.0-2=1691227199=0

Cheers
-- 
Sebastian Ramacher

Bug#1037618: marked as done (ddnet: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 14:41:13 +
with message-id 
and subject line Bug#1037618: fixed in ddnet 16.4-1.2
has caused the Debian Bug report #1037618,
regarding ddnet: 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.)


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

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
/usr/bin/c++ -DCONF_BACKEND_VULKAN -DCONF_INFORM_UPDATE -DCONF_MYSQL 
-DCONF_OPENSSL -DCONF_VIDEORECORDER -DCONF_WAVPACK_CLOSE_FILE 
-DCONF_WAVPACK_OPEN_FILE_INPUT_EX -DGAME_RELEASE_VERSION=\"16.4\" -DGLEW_STATIC 
-D_FORTIFY_SOURCE=2 -I/<>/obj-x86_64-linux-gnu/src 
-I/<>/src -isystem /usr/include/freetype2 -isystem 
/usr/include/opus -isystem /usr/include/SDL2 -isystem /usr/include/wavpack 
-isystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/glib-2.0 -isystem 
/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/libpng16 
-isystem /usr/include/libmount -isystem /usr/include/blkid -isystem 
/usr/include/mariadb -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -O3 
-Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-all -fno-exceptions -Wall 
-Wextra -Wno-unused-parameter -Wno-missing-field-initializers -Wformat=2 
-Wno-nullability-completeness -Wduplicated-cond -Wduplicated-branches -Wl
 ogical-op -Wrestrict -Wshadow=global -Wsuggest-override -std=c++17 -MD -MT 
CMakeFiles/DDNet.dir/src/game/client/ui_scrollregion.cpp.o -MF 
CMakeFiles/DDNet.dir/src/game/client/ui_scrollregion.cpp.o.d -o 
CMakeFiles/DDNet.dir/src/game/client/ui_scrollregion.cpp.o -c 
/<>/src/game/client/ui_scrollregion.cpp
In file included from /<>/src/engine/shared/config.h:20,
 from /<>/src/game/client/ui.cpp:12:
/<>/src/engine/shared/config_variables.h:406:122: warning: extra 
‘;’ [-Wpedantic]
  406 | MACRO_CONFIG_INT(ClChatOld, cl_chat_old, 0, 0, 1, CFGFLAG_CLIENT | 
CFGFLAG_SAVE, "Old chat style: No tee, no background");
  | 
 ^
  | 
 -
cc1plus: note: unrecognized command-line option ‘-Wno-nullability-completeness’ 
may have been intended to silence earlier diagnostics
[ 89%] Building CXX object CMakeFiles/DDNet.dir/src/game/editor/auto_map.cpp.o
/usr/bin/c++ -DCONF_BACKEND_VULKAN -DCONF_INFORM_UPDATE -DCONF_MYSQL 
-DCONF_OPENSSL -DCONF_VIDEORECORDER -DCONF_WAVPACK_CLOSE_FILE 
-DCONF_WAVPACK_OPEN_FILE_INPUT_EX -DGAME_RELEASE_VERSION=\"16.4\" -DGLEW_STATIC 
-D_FORTIFY_SOURCE=2 -I/<>/obj-x86_64-linux-gnu/src 
-I/<>/src -isystem /usr/include/freetype2 -isystem 
/usr/include/opus -isystem /usr/include/SDL2 -isystem /usr/include/wavpack 
-isystem /usr/include/gdk-pixbuf-2.0 -isystem /usr/include/glib-2.0 -isystem 
/usr/lib/x86_64-linux-gnu/glib-2.0/include -isystem /usr/include/libpng16 
-isystem /usr/include/libmount -isystem /usr/include/blkid -isystem 
/usr/include/mariadb -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -pedantic -O3 
-Wdate-time -D_FORTIFY_SOURCE=2 -fstack-protector-all -fno-exceptions -Wall 
-Wextra 

Processed: rmlint: diff for NMU version 2.9.0-2.5

[Debian Bug Tracking System]

Processing control commands:

> tags 1040940 + patch
Bug #1040940 [rmlint-gui] rmlint-gui fails to start: SyntaxError: source code 
cannot contain null bytes
Added tag(s) patch.
> tags 1040940 + pending
Bug #1040940 [rmlint-gui] rmlint-gui fails to start: SyntaxError: source code 
cannot contain null bytes
Added tag(s) pending.

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

Bug#1040940: rmlint: diff for NMU version 2.9.0-2.5

[Adrian Bunk]

Control: tags 1040940 + patch
Control: tags 1040940 + pending

Dear maintainer,

I've prepared an NMU for rmlint (versioned as 2.9.0-2.5) and uploaded
it to DELAYED/2. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -Nru rmlint-2.9.0/debian/changelog rmlint-2.9.0/debian/changelog
--- rmlint-2.9.0/debian/changelog	2023-07-05 11:31:46.0 +0300
+++ rmlint-2.9.0/debian/changelog	2023-08-05 17:16:05.0 +0300
@@ -1,3 +1,11 @@
+rmlint (2.9.0-2.5) unstable; urgency=high
+
+  * Non-maintainer upload.
+  * Add upstream fix for GUI startup failure with recent python3.11.
+(Closes: #1040940)
+
+ -- Adrian Bunk   Sat, 05 Aug 2023 17:16:05 +0300
+
 rmlint (2.9.0-2.4) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru rmlint-2.9.0/debian/patches/0001-cmdline-do-not-write-NUL-byte-to-GUI-bootstrap-scrip.patch rmlint-2.9.0/debian/patches/0001-cmdline-do-not-write-NUL-byte-to-GUI-bootstrap-scrip.patch
--- rmlint-2.9.0/debian/patches/0001-cmdline-do-not-write-NUL-byte-to-GUI-bootstrap-scrip.patch	1970-01-01 02:00:00.0 +0200
+++ rmlint-2.9.0/debian/patches/0001-cmdline-do-not-write-NUL-byte-to-GUI-bootstrap-scrip.patch	2023-08-05 17:13:47.0 +0300
@@ -0,0 +1,26 @@
+From e811a34bdf81f0f5366b07077432f8ab9c776ddd Mon Sep 17 00:00:00 2001
+From: Cebtenzzre 
+Date: Wed, 2 Aug 2023 21:29:15 -0400
+Subject: cmdline: do not write NUL byte to GUI bootstrap script
+
+Fixes #628
+---
+ lib/cmdline.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/lib/cmdline.c b/lib/cmdline.c
+index d5b1338c..07ba104a 100644
+--- a/lib/cmdline.c
 b/lib/cmdline.c
+@@ -176,7 +176,7 @@ static void rm_cmd_start_gui(int argc, const char **argv) {
+ return;
+ }
+ 
+-if(write(bootstrap_fd, RM_PY_BOOTSTRAP, sizeof(RM_PY_BOOTSTRAP)) < 0) {
++if(write(bootstrap_fd, RM_PY_BOOTSTRAP, strlen(RM_PY_BOOTSTRAP)) < 0) {
+ rm_log_warning_line("Could not bootstrap gui: Unable to write to tempfile: %s",
+ g_strerror(errno));
+ return;
+-- 
+2.30.2
+
diff -Nru rmlint-2.9.0/debian/patches/series rmlint-2.9.0/debian/patches/series
--- rmlint-2.9.0/debian/patches/series	2023-07-05 11:31:46.0 +0300
+++ rmlint-2.9.0/debian/patches/series	2023-08-05 17:15:59.0 +0300
@@ -9,3 +9,4 @@
 0001-fix-link-error-on-compilers-with-fno-common-enabled.patch
 0010-apply-upstream-fix-for-data-loss-bug.patch
 python-version-number.patch
+0001-cmdline-do-not-write-NUL-byte-to-GUI-bootstrap-scrip.patch

Bug#1037567: abseil: ftbfs with GCC-13

[Aurelien Jarno]

On 2023-08-04 08:53, Aurelien Jarno wrote:
> On 2023-08-03 21:33, Aurelien Jarno wrote:
> > Hi,
> > 
> > On 2023-08-02 14:27, Benjamin Barenblat wrote:
> > > I’ve been procrastinating on starting the transition because of some
> > > lingering MIPS issues. I think they’ve all been sorted out, and I just
> > > uploaded my latest work to experimental. If that passes the buildds,
> > > I’ll request a transition slot and do the transition as quickly as
> > > possible.
> > > 
> > > If waiting on the transition is going to unacceptably delay the riscv64
> > > bootstrap, please let me know. I think I know which patches I would have
> > > to backport to 20220623 to get it to build with GCC 13, so I may be able
> > > to fix this in unstable before the transition completes.
> > 
> > It was not clear when we're going to need abseil when sending the
> > initial mail, but it's not clear that we'll need to really soon for
> 
> After reading my email again, I noticed a typo that could lead to a
> misunderstanding: "it's now clear that we'll need it really soon"

The easiest and less risky way to make it build is probably to go back
to using gcc-12. This is what the attached patch does.

Regards
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
diff -Nru abseil-20220623.1/debian/control abseil-20220623.1/debian/control
--- abseil-20220623.1/debian/control	2022-10-18 14:31:29.0 +0200
+++ abseil-20220623.1/debian/control	2023-08-05 11:20:36.0 +0200
@@ -18,7 +18,8 @@
 Build-Depends:
  cmake (>= 3.5),
  debhelper-compat (= 12),
- googletest (>= 1.12) [!mipsel !ppc64] 
+ googletest (>= 1.12) [!mipsel !ppc64] ,
+ g++-12
 Rules-Requires-Root: no
 Standards-Version: 4.6.1
 Section: libs
diff -Nru abseil-20220623.1/debian/rules abseil-20220623.1/debian/rules
--- abseil-20220623.1/debian/rules	2022-10-18 14:37:10.0 +0200
+++ abseil-20220623.1/debian/rules	2023-08-05 11:20:36.0 +0200
@@ -38,11 +38,11 @@
 	$(RM) -r $(CURDIR)/shared
 
 override_dh_auto_configure:
-	dh_auto_configure -Bstatic -- -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=OFF
+	dh_auto_configure -Bstatic -- -DCMAKE_C_COMPILER=$(DEB_HOST_GNU_TYPE)-gcc-12 -DCMAKE_CXX_COMPILER=$(DEB_HOST_GNU_TYPE)-g++-12 -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=OFF
 ifeq ($(ABSL_RUN_TESTS),ON)
-	dh_auto_configure -Bshared -- -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=ON -DBUILD_TESTING=ON -DABSL_BUILD_TESTING=ON -DABSL_USE_GOOGLETEST_HEAD=OFF
+	dh_auto_configure -Bshared -- -DCMAKE_C_COMPILER=$(DEB_HOST_GNU_TYPE)-gcc-12 -DCMAKE_CXX_COMPILER=$(DEB_HOST_GNU_TYPE)-g++-12 -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=ON -DBUILD_TESTING=ON -DABSL_BUILD_TESTING=ON -DABSL_USE_GOOGLETEST_HEAD=OFF
 else
-	dh_auto_configure -Bshared -- -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=ON
+	dh_auto_configure -Bshared -- -DCMAKE_C_COMPILER=$(DEB_HOST_GNU_TYPE)-gcc-12 -DCMAKE_CXX_COMPILER=$(DEB_HOST_GNU_TYPE)-g++-12 -DCMAKE_CXX_STANDARD=17 -DBUILD_SHARED_LIBS=ON
 endif
 
 override_dh_auto_build:

Processed: Depends on the python3.11 version

[Debian Bug Tracking System]

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

> found 1040940 2.9.0-2.3
Bug #1040940 [rmlint-gui] rmlint-gui fails to start: SyntaxError: source code 
cannot contain null bytes
Marked as found in versions rmlint/2.9.0-2.3.
> tags 1040940 trixie sid
Bug #1040940 [rmlint-gui] rmlint-gui fails to start: SyntaxError: source code 
cannot contain null bytes
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Processed: tagging 1043065, tagging 1042956, tagging 1042957

[Debian Bug Tracking System]

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

> tags 1043065 + sid trixie
Bug #1043065 [src:gr-limesdr] gr-limesdr: autopkgtest regression with gnuradio 
3.10.7
Added tag(s) sid and trixie.
> tags 1042956 + sid trixie
Bug #1042956 {Done: Ole Streicher } [src:iraf-fitsutil] 
iraf-fitsutil: FTBFS with iraf 2.17.1
Added tag(s) trixie and sid.
> tags 1042957 + sid trixie
Bug #1042957 {Done: Ole Streicher } [src:iraf-mscred] 
iraf-mscred: FTBFS with iraf 2.17.1
Added tag(s) trixie and sid.
> thanks
Stopping processing here.

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

Bug#1043066: python-pyepics: hard-coded dependencies on libca4.13.5 and libcom3.17.6

[Sebastian Ramacher]

Source: python-pyepics
Version: 3.4.1+ds-3
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

epics-base is currently transitioning away from libca4.13.5 and
libcom3.17.6. python-pyepics hard-codes dependencies on those packages,
though.

Cheers
-- 
Sebastian Ramacher

Bug#1043065: gr-limesdr: autopkgtest regression with gnuradio 3.10.7

[Sebastian Ramacher]

Source: gr-limesdr
Version: 3.0.1-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

https://ci.debian.net/data/autopkgtest/testing/amd64/g/gr-limesdr/36447655/log.gz

117s Testing python3.11 ...
117s Traceback (most recent call last):
117s   File "", line 1, in 
117s   File "/usr/lib/python3/dist-packages/limesdr/__init__.py", line 18, in 

117s from .limesdr_python import *
117s ImportError: generic_type: type "sink" referenced unknown base type 
"gr::block"
118s autopkgtest [17:12:35]: test python: ---]
118s python   FAIL non-zero exit status 1

Cheers
-- 
Sebastian Ramacher

Bug#1043064: libpappsomspp: requires source-only upload for testing migration

[Sebastian Ramacher]

Source: libpappsomspp
Version: 0.9.12-1
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Issues preventing migration:
∙ ∙ Not built on buildd: arch amd64 binaries uploaded by lopippo
∙ ∙ Not built on buildd: arch all binaries uploaded by lopippo, a new 
source-only upload is needed to allow migration

Cheers
-- 
Sebastian Ramacher

Processed: ddnet: diff for NMU version 16.4-1.2

[Debian Bug Tracking System]

Processing control commands:

> tags 1037618 + patch
Bug #1037618 [src:ddnet] ddnet: ftbfs with GCC-13
Added tag(s) patch.

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

Bug#1037618: ddnet: diff for NMU version 16.4-1.2

[Sebastian Ramacher]

Control: tags 1037618 + patch


Dear maintainer,

I've prepared an NMU for ddnet (versioned as 16.4-1.2). The diff
is attached to this message.

Cheers
-- 
Sebastian Ramacher
diff -Nru ddnet-16.4/debian/changelog ddnet-16.4/debian/changelog
--- ddnet-16.4/debian/changelog	2023-02-12 16:42:25.0 +0100
+++ ddnet-16.4/debian/changelog	2023-08-05 15:40:19.0 +0200
@@ -1,3 +1,10 @@
+ddnet (16.4-1.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Fix build with GCC-13. (Closes: #1037618)
+
+ -- Sebastian Ramacher   Sat, 05 Aug 2023 15:40:19 +0200
+
 ddnet (16.4-1.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru ddnet-16.4/debian/patches/series ddnet-16.4/debian/patches/series
--- ddnet-16.4/debian/patches/series	2022-10-10 23:55:07.0 +0200
+++ ddnet-16.4/debian/patches/series	2023-08-05 15:39:54.0 +0200
@@ -1,3 +1,4 @@
 # even that ddnet won't render this system font
 # match-fonts-materialdesignicons-webfont-codepoints.patch
 use-system-libjsonparser.patch
+use-str-copy-instead-of-snprintf-to-copy-strings.patch
diff -Nru ddnet-16.4/debian/patches/use-str-copy-instead-of-snprintf-to-copy-strings.patch ddnet-16.4/debian/patches/use-str-copy-instead-of-snprintf-to-copy-strings.patch
--- ddnet-16.4/debian/patches/use-str-copy-instead-of-snprintf-to-copy-strings.patch	1970-01-01 01:00:00.0 +0100
+++ ddnet-16.4/debian/patches/use-str-copy-instead-of-snprintf-to-copy-strings.patch	2023-08-05 15:40:19.0 +0200
@@ -0,0 +1,52 @@
+From 73fe4e6ed43e6044d12cf5a97272f651d48df71d Mon Sep 17 00:00:00 2001
+From: =?UTF-8?q?Robert=20M=C3=BCller?= 
+Date: Wed, 19 Oct 2022 23:31:07 +0200
+Subject: [PATCH] Use `str_copy` instead of `snprintf` to copy strings
+
+---
+ src/tools/map_create_pixelart.cpp | 6 +++---
+ src/tools/map_find_env.cpp| 2 +-
+ src/tools/map_replace_area.cpp| 6 +++---
+ 3 files changed, 7 insertions(+), 7 deletions(-)
+
+--- a/src/tools/map_create_pixelart.cpp
 b/src/tools/map_create_pixelart.cpp
+@@ -46,9 +46,9 @@
+ 	}
+ 
+ 	char aFilenames[3][64];
+-	snprintf(aFilenames[0], 64, "%s", argv[3]); //input_map
+-	snprintf(aFilenames[1], 64, "%s", argv[9]); //output_map
+-	snprintf(aFilenames[2], 64, "%s", argv[1]); //image_file
++	str_copy(aFilenames[0], argv[3]); //input_map
++	str_copy(aFilenames[1], argv[9]); //output_map
++	str_copy(aFilenames[2], argv[1]); //image_file
+ 
+ 	int aLayerID[2] = {atoi(argv[4]), atoi(argv[5])}; //layergroup_id, layer_id
+ 	int aStartingPos[2] = {atoi(argv[6]) * 32, atoi(argv[7]) * 32}; //pos_x, pos_y
+--- a/src/tools/map_find_env.cpp
 b/src/tools/map_find_env.cpp
+@@ -130,7 +130,7 @@
+ 	}
+ 
+ 	char aFilename[64];
+-	snprintf(aFilename, 64, "%s", argv[1]);
++	str_copy(aFilename, argv[1]);
+ 	int EnvID = atoi(argv[2]) - 1;
+ 	dbg_msg("map_find_env", "input_map='%s'; env_number='#%d';", aFilename, EnvID + 1);
+ 
+--- a/src/tools/map_replace_area.cpp
 b/src/tools/map_replace_area.cpp
+@@ -72,9 +72,9 @@
+ 	}
+ 
+ 	char aaMapNames[3][64];
+-	snprintf(aaMapNames[0], 64, "%s", argv[1]); //from_map
+-	snprintf(aaMapNames[1], 64, "%s", argv[4]); //to_map
+-	snprintf(aaMapNames[2], 64, "%s", argv[9]); //output_map
++	str_copy(aaMapNames[0], argv[1]); //from_map
++	str_copy(aaMapNames[1], argv[4]); //to_map
++	str_copy(aaMapNames[2], argv[9]); //output_map
+ 
+ 	float aaaGameAreas[2][2][2];
+ 

Bug#1041400: closing 1041400

[Sebastian Ramacher]

close 1041400 2:20.2+dfsg-3
thanks

Processed: closing 1041400

[Debian Bug Tracking System]

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

> close 1041400 2:20.2+dfsg-3
Bug #1041400 {Done: Vasyl Gello } [src:kodi] kodi: FTBFS 
with ffmpeg 6.0
Ignoring request to alter fixed versions of bug #1041400 to the same values 
previously set
Bug #1041400 {Done: Vasyl Gello } [src:kodi] kodi: FTBFS 
with ffmpeg 6.0
Bug 1041400 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

Bug#1043055: marked as done (libbellesip2: missing Breaks+Replaces: libbellesip1 (<< 5.2))

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 13:34:12 +
with message-id 
and subject line Bug#1043055: fixed in belle-sip 5.2.0+dfsg-3
has caused the Debian Bug report #1043055,
regarding libbellesip2: missing Breaks+Replaces: libbellesip1 (<< 5.2)
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.)


-- 
1043055: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043055
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbellesip2
Version: 5.2.0+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libbellesip2:amd64.
  Preparing to unpack .../25-libbellesip2_5.2.0+dfsg-2_amd64.deb ...
  Unpacking libbellesip2:amd64 (5.2.0+dfsg-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-FWGR51/25-libbellesip2_5.2.0+dfsg-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/belr/grammars/sdp_grammar', which is also in 
package libbellesip1:amd64 5.1.64+dfsg-2


cheers,

andreas
--- End Message ---
--- Begin Message ---
Source: belle-sip
Source-Version: 5.2.0+dfsg-3
Done: Bernhard Schmidt 

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

Debian distribution maintenance software
pp.
Bernhard Schmidt  (supplier of updated belle-sip 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, 05 Aug 2023 15:18:08 +0200
Source: belle-sip
Architecture: source
Version: 5.2.0+dfsg-3
Distribution: unstable
Urgency: high
Maintainer: Debian VoIP Team 
Changed-By: Bernhard Schmidt 
Closes: 1043055
Changes:
 belle-sip (5.2.0+dfsg-3) unstable; urgency=high
 .
   * Add Breaks+Replaces against libbellesip1 (Closes: #1043055)
Checksums-Sha1:
 325b390942be94d08d09bfe4ec8aea561f7249f5 2326 belle-sip_5.2.0+dfsg-3.dsc
 019bd45f7860cb41dd30329f2d29a914f84eb5a2 9944 
belle-sip_5.2.0+dfsg-3.debian.tar.xz
 72a6ef8ffea44107ea9ea866910c39ed7b15331b 8246 
belle-sip_5.2.0+dfsg-3_amd64.buildinfo
Checksums-Sha256:
 1174564b31b17f0b72586a3f3b4f1cd12ff141f4039153f057f5d90618f63747 2326 
belle-sip_5.2.0+dfsg-3.dsc
 fff51cd5c0fd261665d6bc0e59ac3d402ffa13975d0e17a6d2dd658e259a2362 9944 
belle-sip_5.2.0+dfsg-3.debian.tar.xz
 c7bdc66024f5475e2127828166bfb316e21b7104cbd67b314d3a9e2779e42437 8246 
belle-sip_5.2.0+dfsg-3_amd64.buildinfo
Files:
 7c7cb47e5e4f78ff9c3913cf55d53194 2326 libs optional belle-sip_5.2.0+dfsg-3.dsc
 bcea137e04e422b4c3d93ccb30596115 9944 libs optional 
belle-sip_5.2.0+dfsg-3.debian.tar.xz
 8f8f7a6d00e2f46641ae095bc565aed2 8246 libs optional 
belle-sip_5.2.0+dfsg-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE1uAexRal3873GVbTd1B55bhQvJMFAmTOTUMRHGJlcm5pQGRl
Ymlhbi5vcmcACgkQd1B55bhQvJM2+Q//ZtxjE0V3Wcr+hjTCcJTfS50lmBrD7CcO
ozq6O5/GJNGhn0WXfo6cZMUvPmD3p5nale0CMdBCjX4lDLa14QychzLoni2nsCeW
DEzx+VjqAWem5+1t5iiEU7l6WeqQIDSQDx7b+KQJ6lcycfy/SRcZJcPgPSY6DqMH
YsOPQB7qerx+eWyDC8Enrbc7mdH1NJj57URLH+vySQbSXOKM53qe+GpbhPwuHRn/
9HbWhT9QifUJ9/bYP7P9VPD3QgJVwZTqEAEwQXCfX3Ey3VU4AfpswokA0iPWKxAL
u16utWQNsGtVrEDYioqCgNA9z9zaf102tRkJ7HzuiTpLEO7HWaQdPaAlW3IiEnI1
UNpBq9yRlzQWRlUngOPu4I/9FkBhFGUlUuOxS+fWLlO+FXUk75x6t2I0bKMmOgNP
P4YSco121HNc5UdoqG9lGDidTiGV0mzQ8KbiBdrzi/CUsgupRdtITSpNHN8xCOg3
390ERwkIZAMMNXJZTqAT+krSPXiVKj3kGhqrxNkGnvr97YYP6Uab+3BY9NHXOlSL
fETSX8QaRC8dkvlCTcTaLjIfQ2F3mEVffwcnFSkl9HByx/v/HykFlNafrpRQEW+3
wNGGBe0XmOzrEr4kY5dlOOw1gxDTKYhhW2roYrQli7rmxBnuTiBNdtV0iVMIbuOL
lYhVNp11rns=
=QqPi
-END PGP SIGNATURE End Message ---

Bug#1043061: fenics-dolfinx: requires source-only upload for testing migration

[Sebastian Ramacher]

Source: fenics-dolfinx
Version: 1:0.6.0-6
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Issues preventing migration:
∙ ∙ Not built on buildd: arch all binaries uploaded by dparsons, a new 
source-only upload is needed to allow migration

Cheers
-- 
Sebastian Ramacher

Bug#1043062: fenics-basix: requires source-only upload for testing migration

[Sebastian Ramacher]

Source: fenics-basix
Version: 0.6.0-5
Severity: serious
X-Debbugs-Cc: sramac...@debian.org

Issues preventing migration:
∙ ∙ Not built on buildd: arch all binaries uploaded by dparsons, a new 
source-only upload is needed to allow migration

Cheers
-- 
Sebastian Ramacher

Bug#1041377: [patch] freerdp2: FTBFS with ffmpeg 6.0

[Héctor Orón Martínez]

Dear maintainer,

  I have uploaded this package to delayed/2 queue.

Regards

On Fri, 4 Aug 2023 at 11:51, Héctor Orón Martínez  wrote:
>
> Hello,
>
>   I have prepared a new package with a backported upstream fix for this issue.
>
>   This is submitted in salsa as:
>   https://salsa.debian.org/debian-remote-team/freerdp2/-/merge_requests/11
>
>   Find this patch attached here for completion.
>
> Regards
> --
>  Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.



-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.

Processed: python-av: diff for NMU version 10.0.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1041506 + patch
Bug #1041506 [src:python-av] python-av: FTBFS with ffmpeg 6.0
Ignoring request to alter tags of bug #1041506 to the same tags previously set
> tags 1043015 + patch
Bug #1043015 [python-av] Add support for ffmpeg 6.0 for python-av
Ignoring request to alter tags of bug #1043015 to the same tags previously set

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

Processed: python-av: diff for NMU version 10.0.0-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1041506 + patch
Bug #1041506 [src:python-av] python-av: FTBFS with ffmpeg 6.0
Added tag(s) patch.
> tags 1043015 + patch
Bug #1043015 [python-av] Add support for ffmpeg 6.0 for python-av
Added tag(s) patch.

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

Bug#1041506: python-av: diff for NMU version 10.0.0-1.1

[Sebastian Ramacher]

Control: tags 1041506 + patch
Control: tags 1043015 + patch

Dear maintainer,

I've prepared an NMU for python-av (versioned as 10.0.0-1.1). The diff
is attached to this message. The changes are pushed to the packaging
repository.

Cheers
-- 
Sebastian Ramacher
diff -Nru python-av-10.0.0/debian/changelog python-av-10.0.0/debian/changelog
--- python-av-10.0.0/debian/changelog	2022-11-27 16:54:06.0 +0100
+++ python-av-10.0.0/debian/changelog	2023-08-05 14:05:17.0 +0200
@@ -1,3 +1,10 @@
+python-av (10.0.0-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/patches: Build with ffmpeg 6.0 (Closes: #1041506, #1043015)
+
+ -- Sebastian Ramacher   Sat, 05 Aug 2023 14:05:17 +0200
+
 python-av (10.0.0-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru python-av-10.0.0/debian/patches/series python-av-10.0.0/debian/patches/series
--- python-av-10.0.0/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ python-av-10.0.0/debian/patches/series	2023-08-05 14:04:34.0 +0200
@@ -0,0 +1 @@
+Update-to-ffmpeg-6.0.patch
diff -Nru python-av-10.0.0/debian/patches/Update-to-ffmpeg-6.0.patch python-av-10.0.0/debian/patches/Update-to-ffmpeg-6.0.patch
--- python-av-10.0.0/debian/patches/Update-to-ffmpeg-6.0.patch	1970-01-01 01:00:00.0 +0100
+++ python-av-10.0.0/debian/patches/Update-to-ffmpeg-6.0.patch	2023-08-05 14:04:18.0 +0200
@@ -0,0 +1,250 @@
+From 8871e13848cbf78615ba7b429d301adc071841ea Mon Sep 17 00:00:00 2001
+From: Mattias Wadman 
+Date: Tue, 21 Mar 2023 17:01:22 +0100
+Subject: [PATCH] Update to ffmpeg 6.0
+
+Removed and renamed constants with entry from API changes
+https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/doc/APIchanges
+
+Remove use of AVCodecContext.sub_text_format
+  2021-09-20 - 176b8d785bf - lavc 59.9.100 - avcodec.h
+Deprecate AVCodecContext.sub_text_format and the corresponding
+AVOptions. It is unused since the last major bump.
+
+AV_CODEC_CAP_TRUNCATED removed:
+  2021-09-20 - dd846bc4a91 - lavc 59.8.100 - avcodec.h codec.h
+Deprecate AV_CODEC_FLAG_TRUNCATED and AV_CODEC_CAP_TRUNCATED,
+as they are redundant with parsers.
+
+AV_CODEC_CAP_AUTO_THREADS renamed to AV_CODEC_CAP_AUTO_THREADS
+  2021-03-16 - 7d09579190 - lavc 58.132.100 - codec.h
+Add AV_CODEC_CAP_OTHER_THREADS as a new name for
+AV_CODEC_CAP_AUTO_THREADS. AV_CODEC_CAP_AUTO_THREADS
+is now deprecated.
+
+AV_CODEC_CAP_INTRA_ONLY removed (use AV_CODEC_PROP_INTRA_ONLY instead):
+AV_CODEC_CAP_LOSSLESS removed (use AV_CODEC_PROP_LOESSNES instead):
+  2020-05-21 - 13b1bbff0b - lavc 58.86.101 - avcodec.h
+Deprecated AV_CODEC_CAP_INTRA_ONLY and AV_CODEC_CAP_LOSSLESS.
+
+AV_CODEC_FLAG_TRUNCATED removed:
+AV_CODEC_CAP_TRUNCATED removed:
+  2021-09-20 - dd846bc4a91 - lavc 59.8.100 - avcodec.h codec.h
+Deprecate AV_CODEC_FLAG_TRUNCATED and AV_CODEC_CAP_TRUNCATED,
+as they are redundant with parsers.
+
+AV_CODEC_FLAG2_DROP_FRAME_TIMECODE removed:
+  Not API changelog but was removed in f843460eb790d37e444e5946628f228421916537:
+  avcodec/avcodec: Remove AV_CODEC_FLAG2_DROP_FRAME_TIMECODE
+
+  It has been deprecated in 94d68a4
+  and can't be set via AVOptions. The only codecs that use it
+  (the MPEG-1/2 encoders) have private options for this.
+  So remove it.
+
+AVFMT_FLAG_PRIV_OPT removed:
+  2021-03-03 - 2ff40b98ec - lavf 58.70.100 - avformat.h
+Deprecate AVFMT_FLAG_PRIV_OPT. It will do nothing
+as soon as av_demuxer_open() is removed.
+
+Related to #1106
+---
+ av/codec/codec.pyx   | 12 
+ av/codec/context.pyx | 11 ---
+ av/container/core.pyx|  3 ---
+ include/libavcodec/avcodec.pxd   | 10 +-
+ include/libavformat/avformat.pxd |  1 -
+ scripts/activate.sh  |  2 +-
+ 6 files changed, 6 insertions(+), 33 deletions(-)
+
+diff --git a/av/codec/codec.pyx b/av/codec/codec.pyx
+index ad3198fd..978d4277 100644
+--- a/av/codec/codec.pyx
 b/av/codec/codec.pyx
+@@ -52,7 +52,6 @@ Capabilities = define_enum('Capabilities', 'av.codec', (
+ """Codec uses get_buffer() for allocating buffers and supports custom allocators.
+ If not set, it might not use get_buffer() at all or use operations that
+ assume the buffer was allocated by avcodec_default_get_buffer."""),
+-('TRUNCATED', lib.AV_CODEC_CAP_TRUNCATED),
+ ('HWACCEL', 1 << 4),
+ ('DELAY', lib.AV_CODEC_CAP_DELAY,
+ """Encoder or decoder requires flushing with NULL input at the end in order to
+@@ -102,8 +101,10 @@ Capabilities = define_enum('Capabilities', 'av.codec', (
+ """Codec supports slice-based (or partition-based) multithreading."""),
+ ('PARAM_CHANGE', lib.AV_CODEC_CAP_PARAM_CHANGE,
+ """Codec supports changed parameters at any point."""),
+-('AUTO_THREADS', lib.AV_CODEC_CAP_AUTO_THREADS,
+-"""Codec supports avctx->thread_count == 0 (auto)."""),
++('AUTO_THREADS', lib.AV_CODEC_CAP_OTHER_THREADS,
++"""Codec supports 

Bug#1043059: abseil/experimental FTBFS on mipsel

[Adrian Bunk]

Source: abseil
Version: 20230125.3-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=abseil=mipsel=20230125.3-2=1691047974=0

...
virtual memory exhausted: Cannot allocate memory
make[4]: *** [absl/container/CMakeFiles/absl_btree_test.dir/build.make:79: 
absl/container/CMakeFiles/absl_btree_test.dir/btree_test.cc.o] Error 1


The patch below works around the address space issue, but later there is a test 
failure:

...
86: ./absl/log/scoped_mock_log.cc:39: Failure
86: Mock function called more times than expected - returning directly.
86: Function call: Log(INFO, @0x7f9b9b2c "./absl/log/log_format_test.cc", 
@0x7f9b9b14 "nan")
86:  Expected: to be never called
86:Actual: called once - over-saturated and active
86: ./absl/log/log_format_test.cc:611: Failure
86: Actual function call count doesn't match EXPECT_CALL(test_sink, Send(AllOf( 
TextMessage(MatchesOstream(comparison_stream)), TextMessage(AnyOf(Eq("-nan"), 
Eq("nan"), Eq("NaN"), Eq("-nan(ind)"))), ::testing::_)))...
86:  Expected: to be called once
86:Actual: never called - unsatisfied and active
86: [  FAILED  ] FloatingPointLogFormatTest/0.NegativeNaN, where TypeParam = 
float (0 ms)
...
99% tests passed, 1 tests failed out of 208

Total Test time (real) = 235.11 sec

The following tests FAILED:
 86 - absl_log_format_test (Failed)
Errors while running CTest
make[2]: *** [Makefile:74: test] Error 8


Full log is in eller:~bunk/build/LOG.abseil


The test failure is obviously triggered by my enabling of the unit tests,
keeping them disabled would of course "fix" the problem (this might also
be an option for some ports architectures).



--- debian/rules.old2023-08-04 22:56:54.349545220 +
+++ debian/rules2023-08-05 09:40:50.315873020 +
@@ -17,12 +17,8 @@
 
 export DEB_BUILD_MAINT_OPTIONS = hardening=+bindnow reproducible=+fixfilepath
 
-# Unit tests require more than 2 GB of RAM, so disable them on mipsel.
-#
-# Disable unit tests unconditionally if nocheck is set.
-ifeq ($(DEB_HOST_ARCH),mipsel)
-ABSL_RUN_TESTS=OFF
-else ifneq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
+# Disable unit tests if nocheck is set.
+ifneq ($(filter nocheck,$(DEB_BUILD_OPTIONS)),)
 ABSL_RUN_TESTS=OFF
 else
 ABSL_RUN_TESTS=ON
@@ -34,6 +30,12 @@
 ABSL_TEST_EXTRA_ARGS=--no-parallel
 endif
 
+# Reduce debug info on architectures with only 2 GB address space
+ifneq (,$(filter $(DEB_HOST_ARCH), mipsel sh4))
+export DEB_CXXFLAGS_MAINT_APPEND += -g1
+endif
+
+
 %:
dh $@
 

Processed: Re: Bug#1043048: openblas: gives wrong results on mips64el, ignores test failures

[Debian Bug Tracking System]

Processing control commands:

> tags -1 upstream
Bug #1043048 [libopenblas0-pthread] openblas: gives wrong results on mips64el, 
ignores test failures
Added tag(s) upstream.

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

Bug#1043048: openblas: gives wrong results on mips64el, ignores test failures

[Rebecca N. Palmer]

Control: tags -1 upstream

Upstream CI's mips64 qemu test has what look like the same FATAL ERRORs, 
in MIPS64_GENERIC but not SICORTEX, but is still listed as passing.


Which suggests that they also have both parts of this bug (wrong answers 
on mips64el, and errors not actually failing the build), and that 
switching back to SICORTEX will probably work.

Bug#1043058: libesmtp6: missing Breaks: libesmtp5

[Andreas Beckmann]

Package: libesmtp6
Version: 1.1.0-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks

Hi,

during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces without corresponding Breaks.

This leaves a crippled libesmtp5 package installed on certain upgrade
paths.

This is a serious bug violating policy 7.6, see
https://www.debian.org/doc/debian-policy/ch-relationships.html#overwriting-files-and-replacing-packages-replaces
and also see the footnote that describes this incorrect behavior:
https://www.debian.org/doc/debian-policy/ch-relationships.html#id13

The libesmtp6 package has the following relationships with libesmtp5:

  Conflicts: n/a
  Breaks:n/a
  Replaces:  libesmtp5

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

3m29.5s ERROR: FAIL: debsums reports modifications inside the chroot:
  debsums: missing file /usr/lib/esmtp/sasl-cram-md5.so (from libesmtp5 package)
  debsums: missing file /usr/lib/esmtp/sasl-login.so (from libesmtp5 package)
  debsums: missing file /usr/lib/esmtp/sasl-plain.so (from libesmtp5 package)

This wasn't noticed as long as libesmtp6 still provided the files, but
that no longer seems to be the case.


cheers,

Andreas


libesmtp-dev_1.1.0-3+b1.log.gz
Description: application/gzip

Bug#1043055: libbellesip2: missing Breaks+Replaces: libbellesip1 (<< 5.2)

[Andreas Beckmann]

Package: libbellesip2
Version: 5.2.0+dfsg-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

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

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

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

  Selecting previously unselected package libbellesip2:amd64.
  Preparing to unpack .../25-libbellesip2_5.2.0+dfsg-2_amd64.deb ...
  Unpacking libbellesip2:amd64 (5.2.0+dfsg-2) ...
  dpkg: error processing archive 
/tmp/apt-dpkg-install-FWGR51/25-libbellesip2_5.2.0+dfsg-2_amd64.deb (--unpack):
   trying to overwrite '/usr/share/belr/grammars/sdp_grammar', which is also in 
package libbellesip1:amd64 5.1.64+dfsg-2


cheers,

andreas

Processed: block 1043051 with 1043054

[Debian Bug Tracking System]

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

> block 1043051 with 1043054
Bug #1043051 [src:rust-rustls-webpki] rust-rustls-webpki: Fails to build 
without internet access
1043051 was not blocked by any bugs.
1043051 was not blocking any bugs.
Added blocking bug(s) of 1043051: 1043054
> thanks
Stopping processing here.

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

Bug#984010: marked as done (chkservice: ftbfs with GCC-11)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 11:34:25 +
with message-id 
and subject line Bug#984010: fixed in chkservice 0.3-1.1
has caused the Debian Bug report #984010,
regarding chkservice: ftbfs with GCC-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.)


-- 
984010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984010
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:chkservice
Version: 0.3-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-11

[This bug is not targeted to the upcoming bullseye 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-11/g++-11, but succeeds to build with gcc-10/g++-10. The
severity of this report will be raised before the bookworm release,
so nothing has to be done for the bullseye release.

The full build log can be found at:
http://people.debian.org/~doko/logs/20210228/filtered/gcc11/chkservice_0.3-1_unstable_gcc11.log
The last lines of the build log are at the end of this report.

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

GCC 11 defaults to the GNU++17 standard.  If your package installs
header files in /usr/include, please don't work around C++17 issues
by choosing a lower C++ standard for the package build, but fix these
issues to build with the C++17 standard.

[...]
   dh_update_autotools_config
   dh_autoreconf
   dh_auto_configure
cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr 
-DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc 
-DCMAKE_INSTALL_LOCALSTATEDIR=/var -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON 
-DCMAKE_FIND_PACKAGE_NO_PACKAGE_REGISTRY=ON -DCMAKE_INSTALL_RUNSTATEDIR=/run 
"-GUnix Makefiles" -DCMAKE_VERBOSE_MAKEFILE=ON 
-DCMAKE_INSTALL_LIBDIR=lib/x86_64-linux-gnu ..
-- The C compiler identification is GNU 11.0.1
-- The CXX compiler identification is GNU 11.0.1
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- DEBUG mode enabled
-- Local build
-- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") 
-- Checking for module 'libsystemd'
--   Found libsystemd, version 247
-- Checking for module 'ncurses'
--   Found ncurses, version 6.2.20201114
-- Build testing support
-- Configuring done
-- Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

CMAKE_EXPORT_NO_PACKAGE_REGISTRY
CMAKE_INSTALL_LIBDIR
CMAKE_INSTALL_LOCALSTATEDIR
CMAKE_INSTALL_RUNSTATEDIR
CMAKE_INSTALL_SYSCONFDIR


-- Build files have been written to: /<>/obj-x86_64-linux-gnu
   dh_auto_build
cd obj-x86_64-linux-gnu && make -j4 "INSTALL=install 
--strip-program=true" VERBOSE=1
make[1]: Entering directory '/<>/obj-x86_64-linux-gnu'
/usr/bin/cmake -S/<> -B/<>/obj-x86_64-linux-gnu 
--check-build-system CMakeFiles/Makefile.cmake 0
/usr/bin/cmake -E cmake_progress_start 
/<>/obj-x86_64-linux-gnu/CMakeFiles 
/<>/obj-x86_64-linux-gnu//CMakeFiles/progress.marks
make  -f CMakeFiles/Makefile2 all
make[2]: Entering directory '/<>/obj-x86_64-linux-gnu'
make  -f src/CMakeFiles/CHKSYSTEMD.dir/build.make 
src/CMakeFiles/CHKSYSTEMD.dir/depend
make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends 
"Unix Makefiles" /<> /<>/src 
/<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src 
/<>/obj-x86_64-linux-gnu/src/CMakeFiles/CHKSYSTEMD.dir/DependInfo.cmake
 --color=
Dependee 
"/<>/obj-x86_64-linux-gnu/src/CMakeFiles/CHKSYSTEMD.dir/DependInfo.cmake"
 is newer than depender 
"/<>/obj-x86_64-linux-gnu/src/CMakeFiles/CHKSYSTEMD.dir/depend.internal".

Processed: notfound 1040478 in multipath-tools/0.8.5-2+deb11u1

[Debian Bug Tracking System]

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

> notfound 1040478 multipath-tools/0.8.5-2+deb11u1
Bug #1040478 {Done: Chris Hofstaedtler } [multipath-tools] 
multipath-tools: devices from extern FC-Raid only map if the have no partitions
Bug #1040479 {Done: Chris Hofstaedtler } [multipath-tools] 
multipath-tools: devices from extern FC-Raid only map if the have no partitions
No longer marked as found in versions multipath-tools/0.8.5-2+deb11u1.
No longer marked as found in versions multipath-tools/0.8.5-2+deb11u1.
> thanks
Stopping processing here.

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

Bug#1043048: openblas: gives wrong results on mips64el, ignores test failures

[Rebecca N. Palmer]

The most obviously relevant
change between those is that the installed BLAS changed from atlas to
openblas.


It looks like this wasn't a change of default, but that experimental 
uses libatlas and unstable uses libopenblas.


(I don't know why, as the obvious dependency chain is src:statsmodels -> 
python3-scipy -> python3-pythran -> libopenblas-dev | libatlas-base-dev 
on both, and libopenblas is installable in experimental.)



It looks like version 0.3.21+ds-4 is not affected by this issue and
passes its testsuite. Can you possibly check whether statsmodels builds
against that version?


It did (successfully) in statsmodels version 0.13.5+dfsg-7.  The 
openblas build logs also show the issue starting between .21 and .22.

Processed: fixed 1040478 in multipath-tools/0.9.4-5

[Debian Bug Tracking System]

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

> fixed 1040478 multipath-tools/0.9.4-5
Bug #1040478 {Done: Chris Hofstaedtler } [multipath-tools] 
multipath-tools: devices from extern FC-Raid only map if the have no partitions
Bug #1040479 {Done: Chris Hofstaedtler } [multipath-tools] 
multipath-tools: devices from extern FC-Raid only map if the have no partitions
Marked as fixed in versions multipath-tools/0.9.4-5.
Marked as fixed in versions multipath-tools/0.9.4-5.
> thanks
Stopping processing here.

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

Processed: bug 1037714 is forwarded to https://github.com/xbmc/inputstream.ffmpegdirect/pull/238

[Debian Bug Tracking System]

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

> forwarded 1037714 https://github.com/xbmc/inputstream.ffmpegdirect/pull/238
Bug #1037714 [src:kodi-inputstream-ffmpegdirect] kodi-inputstream-ffmpegdirect: 
ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/xbmc/inputstream.ffmpegdirect/pull/238'.
> thanks
Stopping processing here.

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

Processed: bug 1037712 is forwarded to https://github.com/xbmc/inputstream.adaptive/pull/1240

[Debian Bug Tracking System]

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

> forwarded 1037712 https://github.com/xbmc/inputstream.adaptive/pull/1240
Bug #1037712 [src:kodi-inputstream-adaptive] kodi-inputstream-adaptive: ftbfs 
with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/xbmc/inputstream.adaptive/pull/1240'.
> thanks
Stopping processing here.

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

Processed: bug 1037711 is forwarded to https://github.com/xbmc/imagedecoder.heif/commit/47dcb3843e02abb69c52d6f0021bd2816b8317a5

[Debian Bug Tracking System]

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

> forwarded 1037711 
> https://github.com/xbmc/imagedecoder.heif/commit/47dcb3843e02abb69c52d6f0021bd2816b8317a5
Bug #1037711 [src:kodi-imagedecoder-heif] kodi-imagedecoder-heif: ftbfs with 
GCC-13
Set Bug forwarded-to-address to 
'https://github.com/xbmc/imagedecoder.heif/commit/47dcb3843e02abb69c52d6f0021bd2816b8317a5'.
> thanks
Stopping processing here.

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

Processed: notfound 1040478 in multipath-tools/0.9.4-5

[Debian Bug Tracking System]

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

> notfound 1040478 multipath-tools/0.9.4-5
Bug #1040478 {Done: Chris Hofstaedtler } [multipath-tools] 
multipath-tools: devices from extern FC-Raid only map if the have no partitions
Bug #1040479 {Done: Chris Hofstaedtler } [multipath-tools] 
multipath-tools: devices from extern FC-Raid only map if the have no partitions
Ignoring request to alter found versions of bug #1040478 to the same values 
previously set
Ignoring request to alter found versions of bug #1040479 to the same values 
previously set
> thanks
Stopping processing here.

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

Processed: user debian...@lists.debian.org, usertagging 1041832 ...

[Debian Bug Tracking System]

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

> user debian...@lists.debian.org
Setting user to debian...@lists.debian.org (was a...@debian.org).
> usertags 1041832 piuparts
Usertags were: fileconflict.
Usertags are now: piuparts fileconflict.
> retitle 1041832 libsequoia-octopus-librnp: undeclared file conflict with 
> thunderbird
Bug #1041832 [libsequoia-octopus-librnp] libsequoia-octopus-librnp: undeclared 
file conflict with thunerbird
Changed Bug title to 'libsequoia-octopus-librnp: undeclared file conflict with 
thunderbird' from 'libsequoia-octopus-librnp: undeclared file conflict with 
thunerbird'.
> thanks
Stopping processing here.

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

Bug#1043048: openblas: gives wrong results on mips64el, ignores test failures

[Sébastien Villemot]

Dear Rebecca,

Thanks for your report.

Le samedi 05 août 2023 à 09:25 +0100, Rebecca N. Palmer a écrit :
> Package: libopenblas0-pthread
> Version: 0.3.23+ds-2
> Control: affects -1 src:statsmodels
> Severity: serious
> Justification: the default BLAS should NOT silently give wrong answers
> (i.e. if there's no easy way to actually fix this, please switch the 
> default on mips64el back to atlas, and consider removing this package 
> from mips64el)
> 
> statsmodels recently (between 0.14.0+dfsg-1 and -2) started to FTBFS on 
> mips64el with multiple wrong test results.  The most obviously relevant 
> change between those is that the installed BLAS changed from atlas to 
> openblas.
> 
> openblas' own tests on mips64el ( 
> https://buildd.debian.org/status/fetch.php?pkg=openblas=mips64el=0.3.23%2Bds-2=1686760279=0
>  
> ) have 64 instances of "FATAL ERROR - COMPUTED RESULT IS LESS THAN HALF 
> ACCURATE".  (I don't know why this isn't failing the build, which is 
> possibly a bug in itself.)
> 
> openblas upstream are not _obviously_ aware of this.  Given the 
> existence of .github/workflows/mips64.yml, this suggests it _may_ be 
> nontrivial to reproduce in qemu.

It looks like version 0.3.21+ds-4 is not affected by this issue and
passes its testsuite. Can you possibly check whether statsmodels builds
against that version?

My guess is that this bug is caused by the switch to the MIPS64_GENERIC
kernel that I made in version 0.3.22+ds-1. If this is indeed the cause,
then an easy short term fix is to roll back this change and go back to
the SICORTEX kernel. For a longer term fix, I would need to work with
upstream to determine why the MIPS64_GENERIC kernel is broken.

Also note that in any case, using ATLAS is not a good solution because
we are considering its removal, see the thread on debian-science@.¹
BLIS is a better alternative to OpenBLAS.

I also agree that the fact that the OpenBLAS testsuite fails without
triggering an FTBFS is abnormal. I’m surprised by this, and this should
be investigated.

Cheers,


¹
https://lists.debian.org/msgid-search/4311acc16afb473599c79bd5b17a8b734c2f8d2b.ca...@debian.org
-- 
⢀⣴⠾⠻⢶⣦⠀  Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁  Debian Developer
⢿⡄⠘⠷⠚⠋⠀  https://sebastien.villemot.name
⠈⠳⣄  https://www.debian.org




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

Processed: bug 1037862 is forwarded to https://github.com/astro-informatics/sopt/pull/417

[Debian Bug Tracking System]

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

> forwarded 1037862 https://github.com/astro-informatics/sopt/pull/417
Bug #1037862 [src:sopt] sopt: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/astro-informatics/sopt/pull/417'.
> thanks
Stopping processing here.

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

Bug#1043051: rust-rustls-webpki: Fails to build without internet access

[Jeremy Bícha]

Source: rust-rustls-webpki
Version: 0.101.2-1
Severity: serious
Tags: ftbfs

rust-rustls-webpki fails to build without internet access

Full build log
==
https://launchpad.net/ubuntu/+source/rust-rustls-webpki/0.101.2-1/+latestbuild/amd64

Build log excerpt
=
   dh_auto_test -O--buildsystem=cargo
/<>/debian/dh-cargo/bin/cargo test
debian cargo wrapper: options, profiles, parallel: ['parallel=8'] [] ['-j8']
debian cargo wrapper: rust_type, gnu_type: x86_64-unknown-linux-gnu,
x86_64-linux-gnu
debian cargo wrapper: running subprocess (['env', 'RUST_BACKTRACE=1',
'/usr/bin/cargo', '-Zavoid-dev-deps', 'test', '--verbose',
'--verbose', '-j8', '--target', 'x86_64-unknown-linux-gnu',
'--release'],) {}
Updating git repository `https://github.com/est31/rcgen.git`
warning: spurious network error (2 tries remaining): failed to resolve
address for github.com: Temporary failure in name resolution;
class=Net (12)
warning: spurious network error (1 tries remaining): failed to resolve
address for github.com: Temporary failure in name resolution;
class=Net (12)
error: failed to load source for dependency `rcgen`

Caused by:
  Unable to update https://github.com/est31/rcgen.git

Caused by:
  failed to clone into:
/<>/debian/cargo_home/git/db/rcgen-8bc4158ba396894b

Caused by:
  network failure seems to have happened
  if a proxy or similar is necessary `net.git-fetch-with-cli` may help here
  https://doc.rust-lang.org/cargo/reference/config.html#netgit-fetch-with-cli

Caused by:
  failed to resolve address for github.com: Temporary failure in name
resolution; class=Net (12)
dh_auto_test: error: /<>/debian/dh-cargo/bin/cargo test
returned exit code 101

Thank you,
Jeremy Bícha

Bug#1000113: kodi: depends on obsolete pcre3 library

[Adrian Bunk]

On Thu, Jul 06, 2023 at 08:47:59AM +0100, Matthew Vernon wrote:
> Hi,
> 
> On 06/07/2023 06:33, Vasyl Gello wrote:
> 
> > Yes I definitely see the bug. However, Kodi extensively uses pcrecpp and
> > the only replacement I see for pcre2 is jpcre2 [1]
> > There is an ITP bug about it since 2017 but no package.
> > 
> > Matthew, from your experience, is jpcre2 the only C++ wrapper for pcre2
> > or there is something more recommended / maintainable?
> > I did the search but found only jpcre2.
> 
> I should say that I'm not C++ expert; jpcre2 is the only wrapper I find by
> web-searching. I think, though, that it should be possible to use the pcre2
> libraries from C++ in the usual way that you can call C libraries from C++
> (and the headers have the usual extern "C" magic)...

Another option would be to use the vendored copy of PCRE until upstream 
supports PCRE2.

Using a vendored copy of a library is usually not an RC bug.

We do have a package that added and builds a copy of Python 2.7 before 
building itself after to the Python2 removal, so that would be a rather
minor vendoring in comparison.

> Regards,
> 
> Matthew

cu
Adrian

Bug#1037668: closed by Debian FTP Masters (reply to Stephan Lachnit ) (Bug#1037668: fixed in gamescope 3.11.51-1)

[Adrian Bunk]

On Fri, Jul 21, 2023 at 12:54:04AM +, Debian Bug Tracking System wrote:
>...
>  gamescope (3.11.51-1) experimental; urgency=medium
>...
>* Upload to experimental due to wlroots 0.16.0
>* Fix compilation with GCC-13 (Closes: #1037668)
>...

Could you upload to unstable now that wlroots 0.16.2 is there?

Thanks
Adrian

Processed: bug 1037878 is forwarded to https://github.com/alphaonex86/Ultracopier/commit/b438ee89f4137695de2529756f340facdeb5874e

[Debian Bug Tracking System]

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

> forwarded 1037878 
> https://github.com/alphaonex86/Ultracopier/commit/b438ee89f4137695de2529756f340facdeb5874e
Bug #1037878 [src:ultracopier] ultracopier: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/alphaonex86/Ultracopier/commit/b438ee89f4137695de2529756f340facdeb5874e'.
> thanks
Stopping processing here.

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

Processed: tagging 1037913

[Debian Bug Tracking System]

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

> tags 1037913 + patch
Bug #1037913 [src:zytrax] zytrax: ftbfs with GCC-13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: openblas: gives wrong results on mips64el, ignores test failures

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:statsmodels
Bug #1043048 [libopenblas0-pthread] openblas: gives wrong results on mips64el, 
ignores test failures
Added indication that 1043048 affects src:statsmodels

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

Bug#1043048: openblas: gives wrong results on mips64el, ignores test failures

[Rebecca N. Palmer]

Package: libopenblas0-pthread
Version: 0.3.23+ds-2
Control: affects -1 src:statsmodels
Severity: serious
Justification: the default BLAS should NOT silently give wrong answers
(i.e. if there's no easy way to actually fix this, please switch the 
default on mips64el back to atlas, and consider removing this package 
from mips64el)


statsmodels recently (between 0.14.0+dfsg-1 and -2) started to FTBFS on 
mips64el with multiple wrong test results.  The most obviously relevant 
change between those is that the installed BLAS changed from atlas to 
openblas.


openblas' own tests on mips64el ( 
https://buildd.debian.org/status/fetch.php?pkg=openblas=mips64el=0.3.23%2Bds-2=1686760279=0 
) have 64 instances of "FATAL ERROR - COMPUTED RESULT IS LESS THAN HALF 
ACCURATE".  (I don't know why this isn't failing the build, which is 
possibly a bug in itself.)


openblas upstream are not _obviously_ aware of this.  Given the 
existence of .github/workflows/mips64.yml, this suggests it _may_ be 
nontrivial to reproduce in qemu.

Processed: bug 1037802 is forwarded to https://github.com/trabucayre/openFPGALoader/commit/933ed793

[Debian Bug Tracking System]

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

> forwarded 1037802 https://github.com/trabucayre/openFPGALoader/commit/933ed793
Bug #1037802 [src:openfpgaloader] openfpgaloader: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/trabucayre/openFPGALoader/commit/933ed793'.
> thanks
Stopping processing here.

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

Processed: bug 1037908 is forwarded to https://github.com/avast/yaramod/commit/b8a4cddb4b89b7e6928c56c3805434960371e308

[Debian Bug Tracking System]

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

> forwarded 1037908 
> https://github.com/avast/yaramod/commit/b8a4cddb4b89b7e6928c56c3805434960371e308
Bug #1037908 [src:yaramod] yaramod: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/avast/yaramod/commit/b8a4cddb4b89b7e6928c56c3805434960371e308'.
> thanks
Stopping processing here.

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

Processed: block 1037909 with 1041907

[Debian Bug Tracking System]

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

> block 1037909 with 1041907
Bug #1037909 [src:yubioath-desktop] yubioath-desktop: ftbfs with GCC-13
1037909 was not blocked by any bugs.
1037909 was not blocking any bugs.
Added blocking bug(s) of 1037909: 1041907
> thanks
Stopping processing here.

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

Processed: tagging 1037883

[Debian Bug Tracking System]

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

> tags 1037883 + experimental
Bug #1037883 [src:vimix] vimix: ftbfs with GCC-13
Added tag(s) experimental.
> thanks
Stopping processing here.

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

Processed: tagging 1037883

[Debian Bug Tracking System]

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

> tags 1037883 + patch
Bug #1037883 [src:vimix] vimix: ftbfs with GCC-13
Added tag(s) patch.
> thanks
Stopping processing here.

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

Bug#1039722: marked as done (pyfai is failing autopkg tests with python 3.11.4)

[Debian Bug Tracking System]

Your message dated Sat, 5 Aug 2023 09:08:16 +0200 (CEST)
with message-id 
<1816614957.58849636.1691219296077.javamail.zim...@synchrotron-soleil.fr>
and subject line pyfai is failing autopkg tests with python 3.11.4
has caused the Debian Bug report #1039722,
regarding pyfai is failing autopkg tests with python 3.11.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.)


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

Package: src:pyfai
Version: 0.21.3+dfsg1-4
Severity: serious
Tags: sid trixie

pyfai is failing it's autopkg tests on amd64 with python 3.11.4:

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pyfai/34908607/log.gz

442s ==
442s FAIL: test_count_csr 
(pyFAI.test.test_histogram.TestHistogram2d.test_count_csr)
442s Test that the pixel count and the total intensity is conserved
442s --
442s Traceback (most recent call last):
442s   File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py", line 
340, in test_count_csr

442s self.assertTrue(delta == 0, msg="check all pixels were counted")
442s AssertionError: False is not true : check all pixels were counted
442s
442s ==
442s FAIL: test_numpy_vs_cython_vs_csr_2d 
(pyFAI.test.test_histogram.TestHistogram2d.test_numpy_vs_cython_vs_csr_2d)

442s Compare numpy histogram with cython simple implementation
442s --
442s Traceback (most recent call last):
442s   File "/usr/lib/python3/dist-packages/pyFAI/test/test_histogram.py", line 
375, in test_numpy_vs_cython_vs_csr_2d
442s self.assertTrue(delta_max <= self.err_max_cnt, "pixel count difference 
numpy/csr : max delta=%s" % delta_max)
442s AssertionError: False is not true : pixel count difference numpy/csr : max 
delta=8.0

442s
442s --
442s Ran 376 tests in 272.476s
442s
442s FAILED (failures=2, skipped=9)
442s 92
442s 61
442s 33
442s autopkgtest [15:28:03]: test command1: ---]
443s command1 FAIL non-zero exit status 1
443s autopkgtest [15:28:04]: test command1:  - - - - - - - - - - results - - - - 
- - - - - -

443s autopkgtest [15:28:04]:  summary
443s command1 FAIL non-zero exit status 1
--- End Message ---
--- Begin Message ---
I changed the autopkgtests, and not I test essentially the CPU code instead of 
the OpenCL code which rely on pocl.
The real use case in synchrotron, is to use the NVIDIA implementation.

So for now mark the test at flaky since it is not that a problem if it fails.

I nevertheless wan to have the OpenCL log to investigate problems.--- End Message ---

Bug#1041258: marked as done (rust-fs-extra: FTBFS: test failures)

[Debian Bug Tracking System]

Your message dated Sat, 05 Aug 2023 06:43:20 +
with message-id 
and subject line Bug#1041258: fixed in rust-fs-extra 1.3.0-2
has caused the Debian Bug report #1041258,
regarding rust-fs-extra: FTBFS: test failures
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=rust-fs-extra=amd64=1.3.0-1=1688994742=0


failures:
it_copy_progress_work

it_copy_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_copy_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_copy_with_progress_inside_work_target_dir_not_exist
it_copy_with_progress_work_dif_buf_size
it_get_dir_content
it_get_dir_content_many_levels

it_move_dir_with_progress_inside_no_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_overwrite_work_target_dir_exist_with_source_dir_exist

it_move_dir_with_progress_inside_work_target_dir_exist_with_no_source_dir_named_sub_dir
it_move_dir_with_progress_inside_work_target_dir_not_exist
it_move_progress_work
it_move_with_progress_work_dif_buf_size

test result: FAILED. 68 passed; 14 failed; 0 ignored; 0 measured; 0 filtered 
out; finished in 0.05s

error: test failed, to rerun pass `--test dir`
dh_auto_test: error: /usr/share/cargo/bin/cargo test --all returned exit code 
101
make[1]: *** [debian/rules:7: override_dh_auto_test] Error 25


Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: rust-fs-extra
Source-Version: 1.3.0-2
Done: Peter Michael Green 

We believe that the bug you reported is fixed in the latest version of
rust-fs-extra, 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.
Peter Michael Green  (supplier of updated rust-fs-extra 
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, 05 Aug 2023 05:34:45 +
Source: rust-fs-extra
Architecture: source
Version: 1.3.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Rust Maintainers 

Changed-By: Peter Michael Green 
Closes: 1041258
Changes:
 rust-fs-extra (1.3.0-2) unstable; urgency=medium
 .
   * Team upload.
   * Package fs_extra 1.3.0 from crates.io using debcargo 2.6.0
   * Skip tests that seem sensitive to the particular filesystem they are
 run on (Closes: #1041258)
Checksums-Sha1:
 f1cb5cafaf11c40b11e07dc3a0782ed271e0b43d 2175 rust-fs-extra_1.3.0-2.dsc
 731ca30e659813ad64aacff29e8082e2e191de27 4076 
rust-fs-extra_1.3.0-2.debian.tar.xz
 2d659c05ffaed39b54e514dc16f949504a5bc481 7377 
rust-fs-extra_1.3.0-2_source.buildinfo
Checksums-Sha256:
 3c2ea9ca48c92494c2c06c170c3ac9eb18fe5a9b854b533ef549fc0cf0be47b2 2175 
rust-fs-extra_1.3.0-2.dsc
 4e971744f6917900ffa38039d36c311d9a6bcb3d1ea9543434972272caaf6ec8 4076 
rust-fs-extra_1.3.0-2.debian.tar.xz
 265867248b108833804583472066073b57189f4ec65ab11ef870bc08cc43ad9c 7377 
rust-fs-extra_1.3.0-2_source.buildinfo
Files:
 76d0066e850137ee1dc219bb0e0cd929 2175 rust optional rust-fs-extra_1.3.0-2.dsc
 ce866ba15cbbca374db7ee531ab3ea34 4076 rust optional 
rust-fs-extra_1.3.0-2.debian.tar.xz
 427a2368ee2c4f8dc79c95068d2ab5d7 7377 rust optional 
rust-fs-extra_1.3.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCAAyFiEEU0DQATYMplbjSX63DEjqKnqP/XsFAmTN4NIUHHBsdWd3YXNo
QGRlYmlhbi5vcmcACgkQDEjqKnqP/Xtlag//Ti4a3HsTNLbtV0jpuEwdW7hx5ktC
djvLbhhM4wxkleFe0dAs21Ovd+pwJukYgvqpBVyXe7vj8aIo1gIfYb3owkGtBWZx
s8DN7bftLPGyzpAcoZKcLhBZDN/yshmSkLH4NzVJgObPHxEjnRVPjjkjCJxOdh+L
OGY8vgaWwBHpBwwZci6B5bte5GGkTm/nComjpkk0PdV2G58hlJsfrcjPx8sjRLJP
8siGm55VxbHSUZcgWbJ0wl/izUJCjz5NOuB55CDyo0E16lroI0i60yRtpUcmNuuP
D5jJ5rFgUxJmeGE/bdplFhqRcha2opU/KvippORB/YSPAYzs3I9JZmcwBo34Gg11