Bug#1042722: src:rust-crdts: fails to migrate to testing for too long: new autopkgtest failure

[Paul Gevers]

Source: rust-crdts
Version: 7.2.0+dfsg-4
Severity: serious
Control: close -1 7.3.0+dfsg-1
Tags: sid trixie
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:rust-crdts: fails to migrate to testing for too long: new autopkgtest failure

[Debian Bug Tracking System]

Processing control commands:

> close -1 7.3.0+dfsg-1
Bug #1042722 [src:rust-crdts] src:rust-crdts: fails to migrate to testing for 
too long: new autopkgtest failure
Marked as fixed in versions rust-crdts/7.3.0+dfsg-1.
Bug #1042722 [src:rust-crdts] src:rust-crdts: fails to migrate to testing for 
too long: new autopkgtest failure
Marked Bug as done

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

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

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.23.2.13.2-1
Bug #1042721 [src:trash-cli] src:trash-cli: fails to migrate to testing for too 
long: uploader built arch:all binary
Marked as fixed in versions trash-cli/0.23.2.13.2-1.
Bug #1042721 [src:trash-cli] src:trash-cli: fails to migrate to testing for too 
long: uploader built arch:all binary
Marked Bug as done

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

Bug#1042721: src:trash-cli: fails to migrate to testing for too long: uploader built arch:all binary

[Paul Gevers]

Source: trash-cli
Version: 0.17.1.14-5
Severity: serious
Control: close -1 0.23.2.13.2-1
Tags: sid trixie pending
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Bug#1042720: src:xtb: fails to migrate to testing for too long: FTBFS on mips64el

[Paul Gevers]

Source: xtb
Version: 6.5.1-3
Severity: serious
Control: close -1 6.6.0-2
Tags: sid trixie ftbfs
User: release.debian@packages.debian.org
Usertags: out-of-sync

Dear maintainer(s),

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


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


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


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


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


Paul

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



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:xtb: fails to migrate to testing for too long: FTBFS on mips64el

[Debian Bug Tracking System]

Processing control commands:

> close -1 6.6.0-2
Bug #1042720 [src:xtb] src:xtb: fails to migrate to testing for too long: FTBFS 
on mips64el
Marked as fixed in versions xtb/6.6.0-2.
Bug #1042720 [src:xtb] src:xtb: fails to migrate to testing for too long: FTBFS 
on mips64el
Marked Bug as done

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

Bug#999977: qxw: depends on obsolete pcre3 library

[Nick Morrott]

On 2023/07/22 at 08:43, Stephen Kitt wrote:
>aOn Sat, 22 Jul 2023 16:14:06 +0200, Bastian Germann  wrote:
> > I suggest to remove the package. I do not think upstream will deal with 
> > this.
> 
> qxw’s usage of pcre seems simple enough, I’ll try to come up with a patch.
> 
> Regards,
> 
> Stephen

Bastian/Stephen,

In my last contact with upstream I discussed the use of the obsolete pcre3
library. The development team told me that a new GTK3/Qt GUI is under
development which will resolve the pcre3 issue in addition to the
proposed UI improvements.

In the meantime, I will look to spend some time understanding the
pcre3->pcre2 migration and patching qxw in the short term, if Stephen does
not have time to do so.

I'd like to keep qxw in the archive, given the time spent getting it
reintroduced in time for bookworm following the RFP.

Thanks,
Nick

Bug#1036256: golang-github-pin-tftp: FTBFS in testing

[Shengjing Zhu]

On Mon, Jul 31, 2023 at 3:31 AM Thiago Andrade  wrote:
>
> I tested this package on an amd64 PorterBox and the bug seems to have
> been resolved by disabling two tests.
> I've attached this diff, feel free to test it and upload it as soon as
> possible.

This doesn't make sense. Could you elaborate why these tests fail and
should be skipped?
Just disabling tests without explanation doesn't make this package less buggy.

-- 
Shengjing Zhu

Bug#1042322: marked as done (cutefish-core: FTBFS: make[3]: *** [polkit-agent/CMakeFiles/polkit-agent-translations.dir/build.make:310: polkit-agent/.lupdate/ar_AA.ts.stamp] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2023 02:39:05 +
with message-id 
and subject line Bug#1042322: fixed in cutefish-core 0.8-2
has caused the Debian Bug report #1042322,
regarding cutefish-core: FTBFS: make[3]: *** 
[polkit-agent/CMakeFiles/polkit-agent-translations.dir/build.make:310: 
polkit-agent/.lupdate/ar_AA.ts.stamp] Error 1
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> QFSFileEngine::open: No file name specified
> lupdate error: List file '' is not readable.
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: Entering directory '/<>/obj-x86_64-linux-gnu'
> make[3]: *** 
> [polkit-agent/CMakeFiles/polkit-agent-translations.dir/build.make:310: 
> polkit-agent/.lupdate/ar_AA.ts.stamp] Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/07/26/cutefish-core_0.8-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: cutefish-core
Source-Version: 0.8-2
Done: Arun Kumar Pariyar 

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

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

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

Debian distribution maintenance software
pp.
Arun Kumar Pariyar  (supplier of updated cutefish-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 31 Jul 2023 05:48:57 +0545
Source: cutefish-core
Architecture: source
Version: 0.8-2
Distribution: unstable
Urgency: medium
Maintainer: Arun Kumar Pariyar 
Changed-By: Arun Kumar Pariyar 
Closes: 1042322
Changes:
 cutefish-core (0.8-2) unstable; urgency=medium
 .
   * debian/patches:
 + Add 001-fix-ftbfs-qt5_create_translation. (Closes: #1042322)
   * debian/control: Update my debian email address.
Checksums-Sha1:
 afa9816db6575762c545d2a8756def65abc810b6 2584 cutefish-core_0.8-2.dsc
 4817790399d037f5275a222fed67ece40dc9d4c4 6328 cutefish-core_0.8-2.debian.tar.xz
 0a1bfd32f702d716390b23216bc53791479837aa 16392 
cutefish-core_0.8-2_amd64.buildinfo
Checksums-Sha256:
 59690c976340bb5fa5f75e3d523a8740a51fd1398239bfb106cd0f419ab43b5e 2584 
cutefish-core_0.8-2.dsc
 aa012f04ad39fb15ba1372ddd84bc86510a9e4d408e06324200a04ecaff62f94 6328 
cutefish-core_0.8-2.debian.tar.xz
 1b80d029f5ca66b210ca8528d754628405c0cc117245f287a0e5dd7df7fb5258 16392 
cutefish-core_0.8-2_amd64.buildinfo
Files:
 c6cfd66d691c673399f1b8129c1848f3 2584 devel optional cutefish-core_0.8-2.dsc
 fd1721ee9d540d8cae8055df3817d41a 6328 devel optional 
cutefish-core_0.8-2.debian.tar.xz
 cff72d8229cbbfe7ea263ec003af6ff1 16392 devel optional 
cutefish-core_0.8-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE2lMFjb4VS9/L8WutS1Qq9wT3RRYFAmTHE/8ACgkQS1Qq9wT3
RRabcw/8CNmpT/sS4KIE9CslNwGLPPB87comHHdQFmgbpNsr+wQo+0RDuy5hvQQR
2560R45Zgv/seAe1xPV0L0t9AcxM2Teeu5xtRsvX2poBKYAX18ZbwTeY0voKPB87
t8jLOjZcw72V39BNyvDblLVunZZ3eqQw3iJ8+Hmf7a0hea40Xn4B8v8MBqMNlGcJ
ekBIUtL3LuxRNprXCYjZWVQOxpKxtH+u/nJNePgGQC8LC6TRR/g5HlUZkjoBxLfV

Bug#1037577: marked as done (antpm: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2023 01:07:15 +
with message-id 
and subject line Bug#1037577: fixed in antpm 1.21-1
has caused the Debian Bug report #1037577,
regarding antpm: 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.)


-- 
1037577: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037577
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:antpm
Version: 1.20-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/antpm_1.20-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

[...]
[ 54%] Building CXX object CMakeFiles/antpm.dir/GPX.cpp.o
[ 58%] Building CXX object CMakeFiles/antpm.dir/GarminConvert.cpp.o
[ 62%] Building CXX object CMakeFiles/antpm.dir/GarminPacketIntf.cpp.o
[ 66%] Building CXX object CMakeFiles/antpm.dir/DeviceSettings.cpp.o
[ 70%] Building CXX object CMakeFiles/antpm.dir/SerialTty.cpp.o
In file included from /<>/src/DeviceSettings.cpp:20:
/<>/src/DeviceSettings.hpp:36:23: error: ‘uint16_t’ was not 
declared in this scope
   36 | typedef std::multimap Database;
  |   ^~~~
/<>/src/DeviceSettings.hpp:24:1: note: ‘uint16_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
   23 | #include 
  +++ |+#include 
   24 | 
/<>/src/DeviceSettings.hpp:36:42: error: template argument 1 is 
invalid
   36 | typedef std::multimap Database;
  |  ^
/<>/src/DeviceSettings.hpp:36:42: error: template argument 3 is 
invalid
/<>/src/DeviceSettings.hpp:36:42: error: template argument 4 is 
invalid
/<>/src/DeviceSettings.hpp:37:19: error: ‘uint16_t’ was not 
declared in this scope
   37 | typedef std::pair DatabaseEntity;
  |   ^~~~
/<>/src/DeviceSettings.hpp:37:19: note: ‘uint16_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
/<>/src/DeviceSettings.hpp:37:38: error: template argument 1 is 
invalid
   37 | typedef std::pair DatabaseEntity;
  |  ^
/<>/src/DeviceSettings.cpp: In member function ‘antpm::Database 
antpm::DeviceSettings::getDatabaseFiles(size_t) const’:
/<>/src/DeviceSettings.cpp:118:15: error: request for member 
‘insert’ in ‘files’, which is of non-class type ‘antpm::Database’ {aka ‘int’}
  118 | files.insert(DatabaseEntity(static_cast(value),
  |   ^~
/<>/src/DeviceSettings.cpp:119:94: warning: expression list 
treated as compound expression in functional cast [-fpermissive]
  119 | FITEntity(fit.path().string(), 
fs::file_size(fit.path();
  | 
 ^
/<>/src/DeviceSettings.cpp:118:37: warning: left operand of comma 
operator has no effect [-Wunused-value]
  118 | files.insert(DatabaseEntity(static_cast(value),
  | ^~~~
/<>/src/DeviceSettings.cpp:118:22: error: invalid cast from type 
‘antpm::FITEntity’ {aka ‘std::pair, long 
unsigned int>’} to type ‘antpm::DatabaseEntity’ {aka ‘int’}
  118 | files.insert(DatabaseEntity(static_cast(value),
  |  ^~~~
  119 | FITEntity(fit.path().string(), 
fs::file_size(fit.path();
  | 
~~
/<>/src/SerialTty.cpp:341:31: warning: 

Processed: severity of 1041307 is serious, forcibly merging 1038207 1042569, severity of 1038207 is serious

[Debian Bug Tracking System]

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

> severity 1041307 serious
Bug #1041307 [xtrx-dkms] xtrx-dkms: module fails to build for Linux 6.4: error: 
too many arguments to function 'class_create'
Severity set to 'serious' from 'important'
> forcemerge 1038207 1042569
Bug #1038207 [tp-smapi-dkms] tp-smapi-dkms: module fails to build for Linux 
6.4: error: macro "DEFINE_SEMAPHORE" requires 2 arguments, but only 1 given
Bug #1040898 [tp-smapi-dkms] tp-smapi-dkms: Update to support Kernel 6.4+
Bug #1042569 [tp-smapi-dkms] tp-smapi-dkms: Kernel 6.4 not supported
Added tag(s) trixie and sid.
Bug #1040898 [tp-smapi-dkms] tp-smapi-dkms: Update to support Kernel 6.4+
Merged 1038207 1040898 1042569
> severity 1038207 serious
Bug #1038207 [tp-smapi-dkms] tp-smapi-dkms: module fails to build for Linux 
6.4: error: macro "DEFINE_SEMAPHORE" requires 2 arguments, but only 1 given
Bug #1040898 [tp-smapi-dkms] tp-smapi-dkms: Update to support Kernel 6.4+
Bug #1042569 [tp-smapi-dkms] tp-smapi-dkms: Kernel 6.4 not supported
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.

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

Bug#1037663: marked as done (foma: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2023 00:19:06 +
with message-id 
and subject line Bug#1037663: fixed in foma 1:0.10.0+s311-1.1
has caused the Debian Bug report #1037663,
regarding foma: 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.)


-- 
1037663: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037663
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:foma
Version: 1:0.10.0+s311-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/foma_0.10.0+s311-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

[...]
[ 15%] Building C object CMakeFiles/foma-static.dir/extract.c.o
/usr/bin/cc -D_GNU_SOURCE -I/<> -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wno-missing-field-initializers -Wno-deprecated -Wno-unused-parameter 
-fvisibility=hidden -fPIC -std=c2x -fPIC -MD -MT 
CMakeFiles/foma-static.dir/extract.c.o -MF 
CMakeFiles/foma-static.dir/extract.c.o.d -o 
CMakeFiles/foma-static.dir/extract.c.o -c /<>/extract.c
[ 16%] Building C object CMakeFiles/foma-static.dir/flags.c.o
/usr/bin/cc -D_GNU_SOURCE -I/<> -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wno-missing-field-initializers -Wno-deprecated -Wno-unused-parameter 
-fvisibility=hidden -fPIC -std=c2x -fPIC -MD -MT 
CMakeFiles/foma-static.dir/flags.c.o -MF CMakeFiles/foma-static.dir/flags.c.o.d 
-o CMakeFiles/foma-static.dir/flags.c.o -c /<>/flags.c
[ 18%] Building C object CMakeFiles/foma-static.dir/int_stack.c.o
/usr/bin/cc -D_GNU_SOURCE -I/<> -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wno-missing-field-initializers -Wno-deprecated -Wno-unused-parameter 
-fvisibility=hidden -fPIC -std=c2x -fPIC -MD -MT 
CMakeFiles/foma-static.dir/int_stack.c.o -MF 
CMakeFiles/foma-static.dir/int_stack.c.o.d -o 
CMakeFiles/foma-static.dir/int_stack.c.o -c /<>/int_stack.c
[ 19%] Building C object CMakeFiles/foma-static.dir/io.c.o
/usr/bin/cc -D_GNU_SOURCE -I/<> -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wextra 
-Wno-missing-field-initializers -Wno-deprecated -Wno-unused-parameter 
-fvisibility=hidden -fPIC -std=c2x -fPIC -MD -MT 
CMakeFiles/foma-static.dir/io.c.o -MF CMakeFiles/foma-static.dir/io.c.o.d -o 
CMakeFiles/foma-static.dir/io.c.o -c /<>/io.c
/<>/io.c:1002:7: warning: initialization of ‘char’ from ‘void *’ 
makes integer from pointer without a cast [-Wint-conversion]
 1002 | { NULL, 0, NULL },
  |   ^~~~
/<>/io.c:1002:7: note: (near initialization for 
‘BOM_codes[5].code[0]’)
/<>/io.c:1002:16: warning: initialization of ‘char’ from ‘void *’ 
makes integer from pointer without a cast [-Wint-conversion]
 1002 | { NULL, 0, NULL },
  |^~~~
/<>/io.c:1002:16: note: (near initialization for 
‘BOM_codes[5].code[2]’)
/<>/io.c:996:26: warning: missing braces around initializer 
[-Wmissing-braces]
  996 | static BOM BOM_codes[] = {
  |  ^
/<>/io.c:996:26: warning: missing braces around initializer 
[-Wmissing-braces]
/<>/io.c: In function ‘io_get_gz_file_size’:
/<>/io.c:933:5: warning: ignoring return value of ‘fread’ declared 
with attribute ‘warn_unused_result’ [-Wunused-result]
  933 | fread(, 1, 4, 

Bug#1037904: marked as done (xournalpp: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Mon, 31 Jul 2023 00:06:32 +
with message-id 
and subject line Bug#1037904: fixed in xournalpp 1.2.0-1
has caused the Debian Bug report #1037904,
regarding xournalpp: 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.)


-- 
1037904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:xournalpp
Version: 1.1.3-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/xournalpp_1.1.3-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

[...]
   28 | bool loadValueHex(const std::string& key, uint32_t& value) const;
  |   ^~~~
/<>/src/view/background/BackgroundConfig.h:28:10: error: ‘bool 
BackgroundConfig::loadValueHex(const std::string&, int&) const’ cannot be 
overloaded with ‘bool BackgroundConfig::loadValueHex(const std::string&, int&) 
const’
   28 | bool loadValueHex(const std::string& key, uint32_t& value) const;
  |  ^~~~
/<>/src/view/background/BackgroundConfig.h:27:10: note: previous 
declaration ‘bool BackgroundConfig::loadValueHex(const std::string&, int&) 
const’
   27 | bool loadValueHex(const std::string& key, int& value) const;
  |  ^~~~
/<>/src/view/background/BackgroundConfig.cpp: In member function 
‘bool BackgroundConfig::loadValue(const std::string&, int&) const’:
/<>/src/view/background/BackgroundConfig.cpp:35:27: warning: 
conversion from ‘long unsigned int’ to ‘int’ may change value [-Wconversion]
   35 | value = std::stoul(str, nullptr, 10);
  | ~~^~
/<>/src/view/background/BackgroundConfig.cpp: In member function 
‘bool BackgroundConfig::loadValue(const std::string&, double&) const’:
/<>/src/view/background/BackgroundConfig.cpp:45:27: warning: 
conversion from ‘long unsigned int’ to ‘double’ may change value [-Wconversion]
   45 | value = std::stoul(str, nullptr, 10);
  | ~~^~
/<>/src/view/background/BackgroundConfig.cpp: In member function 
‘bool BackgroundConfig::loadValueHex(const std::string&, int&) const’:
/<>/src/view/background/BackgroundConfig.cpp:55:27: warning: 
conversion from ‘long unsigned int’ to ‘int’ may change value [-Wconversion]
   55 | value = std::stoul(str, nullptr, 16);
  | ~~^~
/<>/src/view/background/BackgroundConfig.cpp: At global scope:
/<>/src/view/background/BackgroundConfig.cpp:62:56: error: 
‘uint32_t’ has not been declared
   62 | auto BackgroundConfig::loadValueHex(const string& key, uint32_t& value) 
const -> bool {
  |^~~~
/<>/src/view/background/BackgroundConfig.cpp:62:6: error: 
redefinition of ‘bool BackgroundConfig::loadValueHex(const std::string&, int&) 
const’
   62 | auto BackgroundConfig::loadValueHex(const string& key, uint32_t& value) 
const -> bool {
  |  ^~~~
/<>/src/view/background/BackgroundConfig.cpp:52:6: note: ‘bool 
BackgroundConfig::loadValueHex(const std::string&, int&) const’ previously 
defined here
   52 | auto BackgroundConfig::loadValueHex(const string& key, int& value) 
const -> bool {
  |  ^~~~
[ 93%] Building CXX object 
src/CMakeFiles/xournalpp-core.dir/view/background/DottedBackgroundPainter.cpp.o
cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/c++ 

Processed: tagging 1042250 ...

[Debian Bug Tracking System]

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

> tags 1042250 + upstream
Bug #1042250 [src:bup] bup: FTBFS: dh_auto_test: error: make -j8 test 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Added tag(s) upstream.
> forwarded 1042250 
> https://groups.google.com/g/bup-list/c/kmvgPx2wZfY/m/fSEAzewtAgAJ
Bug #1042250 [src:bup] bup: FTBFS: dh_auto_test: error: make -j8 test 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
Set Bug forwarded-to-address to 
'https://groups.google.com/g/bup-list/c/kmvgPx2wZfY/m/fSEAzewtAgAJ'.
> thanks
Stopping processing here.

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

Processed: forcibly merging 1041203 1042180

[Debian Bug Tracking System]

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

> forcemerge 1041203 1042180
Bug #1041203 [src:macs] FTBFS: InvalidRequirement: Expected end or semicolon
Bug #1042180 [src:macs] macs: FTBFS: dpkg-buildpackage: error: dpkg-source -b . 
subprocess returned exit status 2
Merged 1041203 1042180
> thanks
Stopping processing here.

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

Bug#1042250: bup: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

[Robert Edmonds]

It looks like this is a brittle unit test.

Lucas Nussbaum wrote:
> > Failures:
> > ! /<>/test/ext/test-help:35  '1' = '0'  FAILED

This line is:

WVPASSEQ 1 $(bup help save | head -1 | grep -cF 'bup-save(1)')

The hyphen in the grep expression "bup-save(1)" in the unit test is the
ordinary ASCII character 45:

ASCII 2/13 is decimal 045, hex 2d, octal 055, bits 00101101: prints as `-'
Official name: Hyphen
Other names: Dash, Minus, Worm

That matches the output of "bup help save | head -1" in the C locale:

root@8f8c3e4ea090:/# LC_ALL=C LANG=C bup help save | head -1 | hd
troff::5: warning: cannot select font 'CB'
troff::152: warning: cannot select font 'C'
   vv
  62 75 70 2d 73 61 76 65  28 31 29 20 20 20 20 20  |bup-save(1)
 |
   ^^
0010  20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20  |   
 |
*
0070  20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 62  |   
b|
0080  75 70 2d 73 61 76 65 28  31 29 0a |up-save(1).|
008b
root@8f8c3e4ea090:/#

> The full build log is available from:
> http://qa-logs.debian.net/2023/07/26/bup_0.33.2-1_unstable.log

User Environment


[…]
LANG=C.UTF-8
LC_ALL=C.UTF-8
[…]

However, with a UTF-8 locale I see the hyphen being encoded as the byte
sequence 0xE2 0x80 0x90:

root@8f8c3e4ea090:/# LC_ALL=C.UTF-8 LANG=C.UTF-8 bup help save | head -1 | 
hd
troff::5: warning: cannot select font 'CB'
troff::152: warning: cannot select font 'C'
   
  62 75 70 e2 80 90 73 61  76 65 28 31 29 20 20 20  |bup...save(1)  
 |
   
0010  20 20 20 20 20 20 20 20  20 20 20 20 20 20 20 20  |   
 |
*
0080  20 62 75 70 e2 80 90 73  61 76 65 28 31 29 0a | 
bup...save(1).|
008f
root@8f8c3e4ea090:/#

Which is the UTF-8 encoding of the Unicode character U+2010 'HYPHEN'.

So I guess the bup unit tests should probably set LANG/LC_ALL explicitly.

Thanks!

-- 
Robert Edmonds
edmo...@debian.org

Bug#1042715: php-horde-editor: Please drop ckeditor3

[Bastien Roucariès]

Source: php-horde-editor
Severity: serious
Tags: security
Justification: security reason EOL
X-Debbugs-Cc: Debian Security Team 

Dear Maintainer,

ckeditor4 go to EOL since June by upstream.

You use ckeditor3. With my javascript hat maint of ckeditor I think we could
migrate your software to ckeditor4

I believe the first change is the following patch:
diff --git a/Horde_Editor-2.0.5/lib/Horde/Editor/Ckeditor.php
b/Horde_Editor-2.0.5/lib/Horde/Editor/Ckeditor.php
index 3a58ccd..33e8564 100644
--- a/Horde_Editor-2.0.5/lib/Horde/Editor/Ckeditor.php
+++ b/Horde_Editor-2.0.5/lib/Horde/Editor/Ckeditor.php
@@ -40,9 +40,7 @@ class Horde_Editor_Ckeditor extends Horde_Editor
 return;
 }

-$ck_file = empty($params['basic'])
-? 'ckeditor/ckeditor.js'
-: 'ckeditor/ckeditor_basic.js';
+$ck_file = 'ckeditor/ckeditor.js';

 if (isset($params['config'])) {
 if (is_array($params['config'])) {
@@ -84,6 +82,7 @@ class Horde_Editor_Ckeditor extends Horde_Editor
 case 'msie':
 case 'mozilla':
 case 'opera':
+case 'edge':
 // MSIE: 5.5+
 // Firefox: 1.5+
 // Opera: 9.5+


After it will need to change if needed the config here in order to remove
plugins
https://sources.debian.org/src/php-horde-
imp/6.2.27-3/imp-6.2.27/lib/Script/Package/Editor.php/?hl=33#L33

I could help if needed but I need a means to test the modification

Bastien



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

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1037873 src:libpwizlite
Bug #1037873 [src:toppic] toppic: ftbfs with GCC-13
Bug reassigned from package 'src:toppic' to 'src:libpwizlite'.
No longer marked as found in versions toppic/1.5.3+dfsg1-1.
Ignoring request to alter fixed versions of bug #1037873 to the same values 
previously set
> unarchive 1037733
Bug #1037733 {Done: Filippo Rusconi } [src:libpwizlite] 
libpwizlite: ftbfs with GCC-13
Unarchived Bug 1037733
> forcemerge 1037733 1037873
Bug #1037733 {Done: Filippo Rusconi } [src:libpwizlite] 
libpwizlite: ftbfs with GCC-13
Bug #1037733 {Done: Filippo Rusconi } [src:libpwizlite] 
libpwizlite: ftbfs with GCC-13
Added tag(s) ftbfs.
Bug #1037873 [src:libpwizlite] toppic: ftbfs with GCC-13
Severity set to 'normal' from 'serious'
Marked Bug as done
Marked as fixed in versions libpwizlite/3.0.5-1.
Marked as found in versions libpwizlite/3.0.4-1.
Merged 1037733 1037873
> affects 1037733 src:toppic
Bug #1037733 {Done: Filippo Rusconi } [src:libpwizlite] 
libpwizlite: ftbfs with GCC-13
Bug #1037873 {Done: Filippo Rusconi } [src:libpwizlite] 
toppic: ftbfs with GCC-13
Added indication that 1037733 affects src:toppic
Added indication that 1037873 affects src:toppic
> thanks
Stopping processing here.

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

Processed: found 1037874 in 13.4.1-1

[Debian Bug Tracking System]

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

> found 1037874 13.4.1-1
Bug #1037874 [src:trilinos] trilinos: ftbfs with GCC-13
Marked as found in versions trilinos/13.4.1-1.
> thanks
Stopping processing here.

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

Processed: tagging 1037874

[Debian Bug Tracking System]

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

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

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

Processed: forcibly merging 1037843 1042125

[Debian Bug Tracking System]

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

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

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

Processed: tagging 1037852

[Debian Bug Tracking System]

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

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

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

Processed: tagging 1037850

[Debian Bug Tracking System]

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

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

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

Processed: tagging 1037855

[Debian Bug Tracking System]

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

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

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

Processed: forcibly merging 1037817 1042032

[Debian Bug Tracking System]

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

> forcemerge 1037817 1042032
Bug #1037817 [src:phyx] phyx: ftbfs with GCC-13
Bug #1042032 [src:phyx] phyx: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
Merged 1037817 1042032
> thanks
Stopping processing here.

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

Processed: forcibly merging 1037718 1042137

[Debian Bug Tracking System]

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

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

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

Processed: forcibly merging 1037719 1042144

[Debian Bug Tracking System]

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

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

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

Processed: forcibly merging 1037720 1042143

[Debian Bug Tracking System]

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

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

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

Processed: forcibly merging 1037721 1042204

[Debian Bug Tracking System]

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

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

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

Processed: forcibly merging 1037722 1042139

[Debian Bug Tracking System]

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

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

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

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

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 20:58:31 +
with message-id 
and subject line Bug#1038422: fixed in ntpsec 1.2.2+dfsg1-2
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-2
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: Sun, 30 Jul 2023 14:04:02 -0500
Source: ntpsec
Architecture: source
Version: 1.2.2+dfsg1-2
Distribution: unstable
Urgency: high
Maintainer: Richard Laager 
Changed-By: Richard Laager 
Closes: 1036443 1038422 1038876 1040354 1040355
Changes:
 ntpsec (1.2.2+dfsg1-2) unstable; urgency=high
 .
   * copyright: Update libjsmn comment
   * copyright: Add minor details from upstream
   * Drop dependency on lsb-base
   * Fix file cleanup (Closes: 1036443, 1040354, 1040355)
   * Backport fix to restore blank lines in ntpq (Closes: 1038876)
   * apparmor: leap-seconds.list doesn't need "w"
 Thanks to Hal Murray
   * Fix IGNORE_DHCP comments.
 Thanks to Hal Murray
   * Fix cookie crash.
 Thanks to Hal Murray (Closes: 1038422)
Checksums-Sha1:
 3a62113d24d7071f3d3b0dda93ffcf17b0922b9b 2593 ntpsec_1.2.2+dfsg1-2.dsc
 8584303f5ff0e9ea6405aa18b4654a288300bf78 58724 
ntpsec_1.2.2+dfsg1-2.debian.tar.xz
 2e08a367e45c2c97a896ca4d61ed31c8f3a3a896 8928 
ntpsec_1.2.2+dfsg1-2_source.buildinfo
Checksums-Sha256:
 dc5ca584765fedcd1b79cc7afcae8fa9fb0892c72448f166e444192c2a8eef10 2593 
ntpsec_1.2.2+dfsg1-2.dsc
 

Processed: forcibly merging 1037729 1042149

[Debian Bug Tracking System]

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

> forcemerge 1037729 1042149
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
Merged 1037729 1042149
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
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

Processed: forcibly merging 1037742 1042114

[Debian Bug Tracking System]

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

> forcemerge 1037742 1042114
Bug #1037742 [src:libssw] libssw: ftbfs with GCC-13
Bug #1042114 [src:libssw] libssw: FTBFS: dpkg-gensymbols: error: some symbols 
or patterns disappeared in the symbols file: see diff output below
Marked as found in versions libssw/1.2.4-1.
Merged 1037742 1042114
> thanks
Stopping processing here.

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

Processed: tagging 1037689

[Debian Bug Tracking System]

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

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

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

Processed: bug 1037566 is forwarded to https://github.com/abinit/abinit/commit/9b4e55e8076491eda426167cc1b69859cd7e4cc5

[Debian Bug Tracking System]

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

> forwarded 1037566 
> https://github.com/abinit/abinit/commit/9b4e55e8076491eda426167cc1b69859cd7e4cc5
Bug #1037566 [src:abinit] abinit: ftbfs with GCC-13
Set Bug forwarded-to-address to 
'https://github.com/abinit/abinit/commit/9b4e55e8076491eda426167cc1b69859cd7e4cc5'.
> thanks
Stopping processing here.

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

Processed: forcibly merging 1037758 1042138

[Debian Bug Tracking System]

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

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

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

Bug#1041810: librsvg: CVE-2023-38633

[Simon McVittie]

On Sun, 30 Jul 2023 at 22:04:24 +0200, Salvatore Bonaccorso wrote:
> For bullseye I think we should simply pick the upstream commit?

Yes: we didn't keep up with upstream 2.50.x so there are a bunch of
unrelated fixes (2.50.4 up to .7) which would be out of scope for a
security update. If it was a package I knew better then I might be
advocating the new upstream release, but I can't really assess risk vs
benefit for librsvg, so cherry-picking the equivalent of .8 and .9 seems
more conservative.


compiles successfully, I'll try it in a bullseye VM next.

smcv

Bug#1035820: marked as done (9base: leaves entries in /etc/shells after upgrade from bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 20:07:51 +
with message-id 
and subject line Bug#1035820: fixed in debianutils 5.7-0.5~deb12u1
has caused the Debian Bug report #1035820,
regarding 9base: leaves entries in /etc/shells after upgrade from bullseye
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.)


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

Hi,

during a test with piuparts I noticed your package leaves modifications
in /etc/shells after upgrading from bullseye to bookworm and purging the
package.

9base/bullseye called add-shell/remove-shell in its postinst/postrm.
9base/bookworm no longer does that, but it also does not clean up the
leftover entries from bullseye in its postinst.

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

0m45.2s ERROR: FAIL: After purging files have been modified:
  /etc/shellsnot owned


The following (untested) snippet for the postinst should perform the
neccessary cleanup:

if [ "$1" = "install" ] || [ "$1" = "upgrade" ]; then
if dpkg --compare-versions "$2" lt-nl "1:6-14~" ; then
remove-shell /bin/rc
remove-shell /usr/lib/plan9/bin/rc
fi
fi


cheers,

Andreas


9base_1:6-13.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: debianutils
Source-Version: 5.7-0.5~deb12u1
Done: Andreas Beckmann 

We believe that the bug you reported is fixed in the latest version of
debianutils, 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.
Andreas Beckmann  (supplier of updated debianutils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 29 Jul 2023 01:46:35 +0200
Source: debianutils
Architecture: source
Version: 5.7-0.5~deb12u1
Distribution: bookworm
Urgency: medium
Maintainer: Clint Adams 
Changed-By: Andreas Beckmann 
Closes: 1035820
Changes:
 debianutils (5.7-0.5~deb12u1) bookworm; urgency=medium
 .
   * Rebuild for bookworm.
 .
 debianutils (5.7-0.5) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * update-shells: Do not create duplicate entries in /etc/shells.
   * update-shells: Manage (/usr)/bin/sh in the state file.
   * update-shells: Fix canonicalization of shells in aliased locations.
 (Closes: #1035820)
Checksums-Sha1:
 c9548f5807bcc1c76841edc0202fd5e291455775 1944 debianutils_5.7-0.5~deb12u1.dsc
 769e1bc1e8f84e9bf609206b27e4d5f9e737719b 23108 
debianutils_5.7-0.5~deb12u1.debian.tar.xz
 502180cfc26fc3f19cd2c9baeb2c4ed4a8ab5b52 4692 
debianutils_5.7-0.5~deb12u1_source.buildinfo
Checksums-Sha256:
 b4340ffd82994d910f625236183d732a7407876cba127d4c824ea82db8ccb400 1944 
debianutils_5.7-0.5~deb12u1.dsc
 977c601503f76eda4da17db9a1ba6f2c26484b106aaa64dbe3649cc6978b3edb 23108 
debianutils_5.7-0.5~deb12u1.debian.tar.xz
 3213811fd9673e3e7114ea0ebc024f4308f2b34366f9719faae188f2d5b60d2d 4692 
debianutils_5.7-0.5~deb12u1_source.buildinfo
Files:
 33376718033a6f41ba5ef25c0d3df6ac 1944 utils required 
debianutils_5.7-0.5~deb12u1.dsc
 f2ea302d938dc97726b4bb5011ed4107 23108 utils required 
debianutils_5.7-0.5~deb12u1.debian.tar.xz
 620571b8663229d73d3966c54a8d10fa 4692 utils required 
debianutils_5.7-0.5~deb12u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmTEVYwQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCIV8D/43YG4ol7eHC6E4BNLf/VUGkVeDkTvw89vZ
DDcCELqMH9ex9gnWlLikmsF45vTy1+2RQ0EH+OrrAcLYvmgIqErbS9sxO9ZYDm3M
C3Q23DueOVHQDQwvKKbm3UPhfY+zKFo0n5UviYjfdiTKugyQkh3Feq3eoBYyg3Gj
kz+3MZMbX2JGk/uHsx7txEcqYQibmV7tzuxVouCgL20Qr9iKb0vF+FaImnUOIzYL
oDaP6ooNhsDiucQrwiypAJKjFzSfGlCUjhBd6MszWrFzOaGW3OsfPdfCx5Ex+eUd
JmPt6xihZvodJyQrRVmLM0HU5N9J0s7l/gHf6UxkcP0aKGk8wHaUuPkUIvAWTMjQ
5nWBkAlyCI+PyAdMkYWqg85dXnA2ZXNDGxM3iH+JStVEzNbZ5K1tG3CkdnPkCrVq
7fk+L6s8o809jc5bYsmNluW/3tZpA2LzcdQnhxo99EPOvM8VJv1b9Hh5BZy07mOK
qqqj8tXwPlDU5kmIJ7vDHM4VcqZcV8/R2ZaJGqwSL13H77LUD+K59R6lDID/gnJ6
vK/LKnWA9LdSluZNUehrytFL8jvFlM/9JWyEDfHVjcDRN4vCSNRNp4atgGw68Wj6

Bug#1041810: librsvg: CVE-2023-38633

[Salvatore Bonaccorso]

Hi Simon,

On Sun, Jul 30, 2023 at 04:07:50PM +0100, Simon McVittie wrote:
> On Sun, 23 Jul 2023 at 21:13:38 +0200, Salvatore Bonaccorso wrote:
> > The following vulnerability was published for librsvg.
> > 
> > CVE-2023-38633[0]:
> > | A directory traversal problem in the URL decoder of librsvg before
> > | 2.56.3 could be used by local or remote attackers to disclose files
> > | (on the local filesystem outside of the expected area), as
> > | demonstrated by href=".?../../../../../../../../../../etc/passwd" in
> > | an xi:include element.
> 
> I'm testing
> 
> to fix this in unstable. In addition to importing the new upstream
> release, we need to work around #1038447, otherwise there will be no
> fixed version for s390x and the package will be unable to migrate -
> I asked the porting teams for the big-endian architectures to debbisect
> this and find out which package triggered #1038447, but it appears this
> has not yet happened.

Ok thanks for this background information.

> 
> For stable, since librsvg has hardly changed since bookworm, I think
> the best route will be a 2.54.7+dfsg-1~deb12u1 rather than backporting
> individual changes (because we would have to backport the vast majority
> of the delta between bookworm and unstable to fix #1041810 and avoid
> FTBFSs anyway). #1038447 affects bookworm on s390x, so if the big-endian
> architectures' porting teams cannot help to diagnose it, we will have
> to work around it by skipping those tests and accepting that some SVGs
> will be mis-rendered on BE architectures. Similarly, #1038252 affects
> bookworm on i386, so we will have to work around that by skipping a
> couple of tests.
> 
> One change that happened between bookworm's 2.54.5+dfsg-1 and trixie's
> 2.54.5+dfsg-3 is that Sebastien Bacher did the trip through NEW to add a
> librsvg2-tests binary package and an autopkgtest that runs it:
> ,
> .
> This doesn't affect the contents of existing binary packages, it only
> adds a new binary package. Would the security team be OK with including
> that change for the sake of better test coverage and minimizing delta,
> or do we need to revert it for a bookworm update?

Sounds good with your plan to backport the unstable version to
bookworm, and no need to revert the librsvg2-tests additionas this
actually will help for running the autopkgtests.

Let's expose the version in unstable a bit, then move on to the lower
suites. 

For bullseye I think we should simply pick the upstream commit?

Regards,
Salvatore

Bug#1042710: medialibrary FTBFS with gcc 13

[Adrian Bunk]

Source: medialibrary
Version: 0.12.3-1
Severity: serious
Tags: ftbfs

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/medialibrary.html
https://buildd.debian.org/status/fetch.php?pkg=medialibrary=riscv64=0.12.3-1=1690744091=0

...
c++ -Isrc/libmedialibrary.so.0.0.0.p -Isrc -I../src -I. -I.. -Iinclude 
-I../include -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall 
-Winvalid-pch -Wextra -Wpedantic -std=c++14 -DHAVE_CONFIG_H=1 -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -pthread -MD -MQ 
src/libmedialibrary.so.0.0.0.p/Metadata.cpp.o -MF 
src/libmedialibrary.so.0.0.0.p/Metadata.cpp.o.d -o 
src/libmedialibrary.so.0.0.0.p/Metadata.cpp.o -c ../src/Metadata.cpp
In file included from ../src/Metadata.h:25,
 from ../src/Metadata.cpp:27:
../include/medialibrary/IMetadata.h:33:10: warning: elaborated-type-specifier 
for a scoped enum must not use the ‘class’ keyword
   33 | enum class EntityType : uint8_t
  |  ^
  |  -
../include/medialibrary/IMetadata.h:33:16: error: use of enum ‘EntityType’ 
without previous declaration
   33 | enum class EntityType : uint8_t
  |^~
...

Bug#1036256: golang-github-pin-tftp: FTBFS in testing

[Thiago Andrade]

I tested this package on an amd64 PorterBox and the bug seems to have 
been resolved by disabling two tests.
I've attached this diff, feel free to test it and upload it as soon as 
possible.


Regards

--
...
⢀⣴⠾⠻⢶⣦⠀ Thiago Andrade Marques
⣾⠁⢰⠒⠀⣿⡁ GPG: 4096R/F8CDB08B
⢿⡄⠘⠷⠚⠋⠀ GPG Fingerprint: 1D38 EE3C 624F 955C E1FA  3C85 5A30 3591 F8CD B08B
⠈⠳⣄
diff -Nru golang-github-pin-tftp-2.2.0/debian/changelog golang-github-pin-tftp-2.2.0/debian/changelog
--- golang-github-pin-tftp-2.2.0/debian/changelog	2022-05-19 10:01:45.0 -0300
+++ golang-github-pin-tftp-2.2.0/debian/changelog	2023-07-30 16:12:59.0 -0300
@@ -1,3 +1,14 @@
+golang-github-pin-tftp (2.2.0-4) unstable; urgency=medium
+
+  * Team upload.
+
+  [ Thiago Andrade Marques ]
+  * debian/patches/single_port_test.go.patch: removed
+TestSendReceiveSinglePortWithBlockSize and
+TestServerReceiveTimeoutSinglePort. (Closes: #1036256)
+
+ -- Thiago Andrade Marques   Sun, 30 Jul 2023 16:12:59 -0300
+
 golang-github-pin-tftp (2.2.0-3) unstable; urgency=medium
 
   * Team upload.
diff -Nru golang-github-pin-tftp-2.2.0/debian/patches/single_port_test.go.patch golang-github-pin-tftp-2.2.0/debian/patches/single_port_test.go.patch
--- golang-github-pin-tftp-2.2.0/debian/patches/single_port_test.go.patch	2022-05-19 09:48:59.0 -0300
+++ golang-github-pin-tftp-2.2.0/debian/patches/single_port_test.go.patch	2023-07-30 16:12:59.0 -0300
@@ -1,11 +1,17 @@
 Subject: remove test that timeout during build
-
 golang-github-pin-tftp-2.2.0/single_port_test.go
-+++ golang-github-pin-tftp-2.2.0/single_port_test.go
-@@ -10,14 +10,6 @@
+Author: Thiago Andrade Marques 
+Last-Update: 2023-07-30
+Bug-Debian: http://bugs.debian.org/1036256
+===
+Index: golang-github-pin-tftp-2.2.0/single_port_test.go
+===
+--- golang-github-pin-tftp.orig/single_port_test.go
 golang-github-pin-tftp/single_port_test.go
+@@ -9,30 +9,3 @@ func TestZeroLengthSinglePort(t *testing
+ 	defer s.Shutdown()
  	testSendReceive(t, c, 0)
  }
- 
+-
 -func TestSendReceiveSinglePort(t *testing.T) {
 -	s, c := makeTestServer(true)
 -	defer s.Shutdown()
@@ -14,18 +20,21 @@
 -	}
 -}
 -
- func TestSendReceiveSinglePortWithBlockSize(t *testing.T) {
- 	s, c := makeTestServer(true)
- 	defer s.Shutdown()
-@@ -27,11 +19,6 @@
- 	}
- }
- 
+-func TestSendReceiveSinglePortWithBlockSize(t *testing.T) {
+-	s, c := makeTestServer(true)
+-	defer s.Shutdown()
+-	for i := 600; i < 1000; i++ {
+-		c.blksize = i
+-		testSendReceive(t, c, 5000+int64(i))
+-	}
+-}
+-
 -func TestServerSendTimeoutSinglePort(t *testing.T) {
 -	s, c := makeTestServer(true)
 -	serverTimeoutSendTest(s, c, t)
 -}
 -
- func TestServerReceiveTimeoutSinglePort(t *testing.T) {
- 	s, c := makeTestServer(true)
- 	serverReceiveTimeoutTest(s, c, t)
+-func TestServerReceiveTimeoutSinglePort(t *testing.T) {
+-	s, c := makeTestServer(true)
+-	serverReceiveTimeoutTest(s, c, t)
+-}

Bug#1037736: marked as done (libsass: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 18:25:31 +
with message-id 
and subject line Bug#1042201: fixed in libsass 3.6.5+20220909-2
has caused the Debian Bug report #1042201,
regarding libsass: 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.)


-- 
1042201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042201
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsass
Version: 3.6.5+20220909-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/libsass_3.6.5+20220909-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

[...]
  
(optional=templinst)_ZNSt6vectorIP13Sass_FunctionSaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 3.5.5-4~
+ _ZNSt6vectorIP13Sass_FunctionSaIS1_EED1Ev@Base 3.6.5+20220909-1
+ _ZNSt6vectorIP13Sass_FunctionSaIS1_EED2Ev@Base 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIP13Sass_ImporterSaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 3.5.5-4~
+ _ZNSt6vectorIP13Sass_ImporterSaIS1_EED1Ev@Base 3.6.5+20220909-1
+ _ZNSt6vectorIP13Sass_ImporterSaIS1_EED2Ev@Base 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIPKN4Sass14SimpleSelectorESaIS3_EE17_M_realloc_insertIJRKS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIPN4Sass11EnvironmentINS0_10SharedImplINS0_8AST_NodeESaIS6_EE17_M_realloc_insertIJRKS6_EEEvN9__gnu_cxx17__normal_iteratorIPS6_S8_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIPN4Sass11EnvironmentINS0_10SharedImplINS0_8AST_NodeESaIS6_EE17_M_realloc_insertIJS6_EEEvN9__gnu_cxx17__normal_iteratorIPS6_S8_EEDpOT_@Base
 3.5.5-4~
@@ -4586,9 +4624,12 @@
  
(optional=templinst)_ZNSt6vectorIPN4Sass8AST_NodeESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIPN4Sass9StatementESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIPN4Sass9StatementESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.5.5-4~
+ _ZNSt6vectorIPN4Sass9StatementESaIS2_EED1Ev@Base 3.6.5+20220909-1
+ _ZNSt6vectorIPN4Sass9StatementESaIS2_EED2Ev@Base 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIPcSaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 3.6.5+2021
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 3.6.4-2~
+ 
_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EE9push_backERKS5_@Base
 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EED1Ev@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EED2Ev@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 3.6.4-2~
@@ -4620,6 +4661,9 @@
  
(optional=templinst)_ZNSt6vectorISt4pairIbN4Sass10SharedImplINS1_5BlockSaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 3.5.5-4~
  

Bug#1042201: marked as done (libsass: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 18:25:31 +
with message-id 
and subject line Bug#1042201: fixed in libsass 3.6.5+20220909-2
has caused the Debian Bug report #1042201,
regarding libsass: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> d-shlibmove --commit \
>   --devunversioned \
>   --exclude-la \
>   --multiarch \
>   --movedev "debian/tmp/usr/include/*" usr/include/ \
>   --movedev "debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/*" \
>   usr/lib/x86_64-linux-gnu/pkgconfig \
>   debian/tmp/usr/lib/x86_64-linux-gnu/*.so
> Library package automatic movement utility
> set -e
> install -d -m 755 debian/libsass-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libsass1/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libsass.a 
> debian/libsass-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libsass.so 
> debian/libsass-dev/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libsass.so.1 
> debian/libsass1/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libsass.so.1.0.0 
> debian/libsass1/usr/lib/x86_64-linux-gnu
> PKGDEV=libsass-dev
> PKGSHL=libsass1
> install -d -m 755 debian/libsass-dev/usr/include/
> mv debian/tmp/usr/include/* debian/libsass-dev/usr/include/
> install -d -m 755 debian/libsass-dev/usr/lib/x86_64-linux-gnu/pkgconfig
> mv debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/* 
> debian/libsass-dev/usr/lib/x86_64-linux-gnu/pkgconfig
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libsass1/DEBIAN/symbols doesn't match 
> completely debian/libsass1.symbols
> --- debian/libsass1.symbols (libsass1_3.6.5+20220909-1_amd64)
> +++ dpkg-gensymbolsvUhLHH 2023-07-26 19:15:49.447598237 +
> @@ -557,8 +557,8 @@
>   _ZN4Sass12File_ContextD2Ev@Base 3.5.5-4~
>   _ZN4Sass12OutputBufferC1ERKS0_@Base 3.6.4-4~
>   _ZN4Sass12OutputBufferC2ERKS0_@Base 3.6.4-4~
> - _ZN4Sass12OutputBufferD1Ev@Base 3.5.5-4~
> - _ZN4Sass12OutputBufferD2Ev@Base 3.5.5-4~
> +#MISSING: 3.6.5+20220909-1# _ZN4Sass12OutputBufferD1Ev@Base 3.5.5-4~
> +#MISSING: 3.6.5+20220909-1# _ZN4Sass12OutputBufferD2Ev@Base 3.5.5-4~
>   _ZN4Sass12SelectorList13cloneChildrenEv@Base 3.6.4-2~
>   
> _ZN4Sass12SelectorList19resolve_parent_refsESt6vectorINS_10SharedImplIS0_EESaIS3_EERS1_INS_9BacktraceESaIS6_EEb@Base
>  3.6.4-2~
>   
> _ZN4Sass12SelectorList7performEPNS_9OperationINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base
>  3.6.4-2~
> @@ -751,7 +751,7 @@
>   _ZN4Sass13color_to_nameERKNS_10Color_RGBAE@Base 3.6.4
>   _ZN4Sass13color_to_nameEd@Base 3.5.5-4~
>   _ZN4Sass13color_to_nameEi@Base 3.5.5-4~
> - _ZN4Sass13compatibilityEPKc@Base 3.6.4-4~
> +#MISSING: 3.6.5+20220909-1# _ZN4Sass13compatibilityEPKc@Base 3.6.4-4~
>   
> _ZN4Sass13convert_unitsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_RiS8_@Base
>  3.5.5-4~
>   
> _ZN4Sass13escape_stringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  3.5.5-4~
>   _ZN4Sass13get_main_unitENS_9UnitClassE@Base 3.5.5-4~
> @@ -1539,7 +1539,7 @@
>   _ZN4Sass16Parent_ReferenceD0Ev@Base 3.6.4
>   _ZN4Sass16Parent_ReferenceD1Ev@Base 3.6.4
>   _ZN4Sass16Parent_ReferenceD2Ev@Base 3.6.4
> - (optional=templinst|arch=!hurd-i386 !i386 
> !m68k)_ZN4Sass16PtrObjEqualityFnINS_6StringEEEbPKT_S4_@Base 3.6.4-4~
> +#MISSING: 3.6.5+20220909-1# (optional=templinst|arch=!hurd-i386 !i386 
> !m68k)_ZN4Sass16PtrObjEqualityFnINS_6StringEEEbPKT_S4_@Base 3.6.4-4~
>   
> _ZN4Sass16SupportsNegation7performEPNS_9OperationINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base
>  3.6.4-2~
>   

Bug#1042201: marked as done (libsass: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 18:25:31 +
with message-id 
and subject line Bug#1037736: fixed in libsass 3.6.5+20220909-2
has caused the Debian Bug report #1037736,
regarding libsass: FTBFS: dpkg-gensymbols: error: some symbols or patterns 
disappeared in the symbols file: see diff output below
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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> d-shlibmove --commit \
>   --devunversioned \
>   --exclude-la \
>   --multiarch \
>   --movedev "debian/tmp/usr/include/*" usr/include/ \
>   --movedev "debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/*" \
>   usr/lib/x86_64-linux-gnu/pkgconfig \
>   debian/tmp/usr/lib/x86_64-linux-gnu/*.so
> Library package automatic movement utility
> set -e
> install -d -m 755 debian/libsass-dev/usr/lib/x86_64-linux-gnu
> install -d -m 755 debian/libsass1/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libsass.a 
> debian/libsass-dev/usr/lib/x86_64-linux-gnu
> mv debian/tmp/usr/lib/x86_64-linux-gnu/libsass.so 
> debian/libsass-dev/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libsass.so.1 
> debian/libsass1/usr/lib/x86_64-linux-gnu
> mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libsass.so.1.0.0 
> debian/libsass1/usr/lib/x86_64-linux-gnu
> PKGDEV=libsass-dev
> PKGSHL=libsass1
> install -d -m 755 debian/libsass-dev/usr/include/
> mv debian/tmp/usr/include/* debian/libsass-dev/usr/include/
> install -d -m 755 debian/libsass-dev/usr/lib/x86_64-linux-gnu/pkgconfig
> mv debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/* 
> debian/libsass-dev/usr/lib/x86_64-linux-gnu/pkgconfig
> make[1]: Leaving directory '/<>'
>dh_installdocs
>dh_installchangelogs
>dh_perl
>dh_link
>dh_strip_nondeterminism
>dh_compress
>dh_fixperms
>dh_missing
>dh_dwz -a
>dh_strip -a
>dh_makeshlibs -a
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see 
> diff output below
> dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols 
> file: see diff output below
> dpkg-gensymbols: warning: debian/libsass1/DEBIAN/symbols doesn't match 
> completely debian/libsass1.symbols
> --- debian/libsass1.symbols (libsass1_3.6.5+20220909-1_amd64)
> +++ dpkg-gensymbolsvUhLHH 2023-07-26 19:15:49.447598237 +
> @@ -557,8 +557,8 @@
>   _ZN4Sass12File_ContextD2Ev@Base 3.5.5-4~
>   _ZN4Sass12OutputBufferC1ERKS0_@Base 3.6.4-4~
>   _ZN4Sass12OutputBufferC2ERKS0_@Base 3.6.4-4~
> - _ZN4Sass12OutputBufferD1Ev@Base 3.5.5-4~
> - _ZN4Sass12OutputBufferD2Ev@Base 3.5.5-4~
> +#MISSING: 3.6.5+20220909-1# _ZN4Sass12OutputBufferD1Ev@Base 3.5.5-4~
> +#MISSING: 3.6.5+20220909-1# _ZN4Sass12OutputBufferD2Ev@Base 3.5.5-4~
>   _ZN4Sass12SelectorList13cloneChildrenEv@Base 3.6.4-2~
>   
> _ZN4Sass12SelectorList19resolve_parent_refsESt6vectorINS_10SharedImplIS0_EESaIS3_EERS1_INS_9BacktraceESaIS6_EEb@Base
>  3.6.4-2~
>   
> _ZN4Sass12SelectorList7performEPNS_9OperationINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base
>  3.6.4-2~
> @@ -751,7 +751,7 @@
>   _ZN4Sass13color_to_nameERKNS_10Color_RGBAE@Base 3.6.4
>   _ZN4Sass13color_to_nameEd@Base 3.5.5-4~
>   _ZN4Sass13color_to_nameEi@Base 3.5.5-4~
> - _ZN4Sass13compatibilityEPKc@Base 3.6.4-4~
> +#MISSING: 3.6.5+20220909-1# _ZN4Sass13compatibilityEPKc@Base 3.6.4-4~
>   
> _ZN4Sass13convert_unitsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_RiS8_@Base
>  3.5.5-4~
>   
> _ZN4Sass13escape_stringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
>  3.5.5-4~
>   _ZN4Sass13get_main_unitENS_9UnitClassE@Base 3.5.5-4~
> @@ -1539,7 +1539,7 @@
>   _ZN4Sass16Parent_ReferenceD0Ev@Base 3.6.4
>   _ZN4Sass16Parent_ReferenceD1Ev@Base 3.6.4
>   _ZN4Sass16Parent_ReferenceD2Ev@Base 3.6.4
> - (optional=templinst|arch=!hurd-i386 !i386 
> !m68k)_ZN4Sass16PtrObjEqualityFnINS_6StringEEEbPKT_S4_@Base 3.6.4-4~
> +#MISSING: 3.6.5+20220909-1# (optional=templinst|arch=!hurd-i386 !i386 
> !m68k)_ZN4Sass16PtrObjEqualityFnINS_6StringEEEbPKT_S4_@Base 3.6.4-4~
>   
> _ZN4Sass16SupportsNegation7performEPNS_9OperationINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base
>  3.6.4-2~
>   

Bug#1037736: marked as done (libsass: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 18:25:31 +
with message-id 
and subject line Bug#1037736: fixed in libsass 3.6.5+20220909-2
has caused the Debian Bug report #1037736,
regarding libsass: 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.)


-- 
1037736: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037736
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:libsass
Version: 3.6.5+20220909-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/libsass_3.6.5+20220909-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

[...]
  
(optional=templinst)_ZNSt6vectorIP13Sass_FunctionSaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 3.5.5-4~
+ _ZNSt6vectorIP13Sass_FunctionSaIS1_EED1Ev@Base 3.6.5+20220909-1
+ _ZNSt6vectorIP13Sass_FunctionSaIS1_EED2Ev@Base 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIP13Sass_ImporterSaIS1_EE17_M_realloc_insertIJRKS1_EEEvN9__gnu_cxx17__normal_iteratorIPS1_S3_EEDpOT_@Base
 3.5.5-4~
+ _ZNSt6vectorIP13Sass_ImporterSaIS1_EED1Ev@Base 3.6.5+20220909-1
+ _ZNSt6vectorIP13Sass_ImporterSaIS1_EED2Ev@Base 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIPKN4Sass14SimpleSelectorESaIS3_EE17_M_realloc_insertIJRKS3_EEEvN9__gnu_cxx17__normal_iteratorIPS3_S5_EEDpOT_@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIPN4Sass11EnvironmentINS0_10SharedImplINS0_8AST_NodeESaIS6_EE17_M_realloc_insertIJRKS6_EEEvN9__gnu_cxx17__normal_iteratorIPS6_S8_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIPN4Sass11EnvironmentINS0_10SharedImplINS0_8AST_NodeESaIS6_EE17_M_realloc_insertIJS6_EEEvN9__gnu_cxx17__normal_iteratorIPS6_S8_EEDpOT_@Base
 3.5.5-4~
@@ -4586,9 +4624,12 @@
  
(optional=templinst)_ZNSt6vectorIPN4Sass8AST_NodeESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIPN4Sass9StatementESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIPN4Sass9StatementESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base
 3.5.5-4~
+ _ZNSt6vectorIPN4Sass9StatementESaIS2_EED1Ev@Base 3.6.5+20220909-1
+ _ZNSt6vectorIPN4Sass9StatementESaIS2_EED2Ev@Base 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIPcSaIS0_EE17_M_realloc_insertIJRKS0_EEEvN9__gnu_cxx17__normal_iteratorIPS0_S2_EEDpOT_@Base
 3.5.5-4~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 3.6.5+2021
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 3.6.4-2~
+ 
_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EE9push_backERKS5_@Base
 3.6.5+20220909-1
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EED1Ev@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_15ComplexSelectorEEESaIS3_EESaIS5_EED2Ev@Base
 3.6.4-2~
  
(optional=templinst)_ZNSt6vectorIS_IN4Sass10SharedImplINS0_17SelectorComponentEEESaIS3_EESaIS5_EE12emplace_backIJS5_EEEvDpOT_@Base
 3.6.4-2~
@@ -4620,6 +4661,9 @@
  
(optional=templinst)_ZNSt6vectorISt4pairIbN4Sass10SharedImplINS1_5BlockSaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base
 3.5.5-4~
  

Bug#1037698: marked as done (j4-dmenu-desktop: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 18:24:37 +
with message-id 
and subject line Bug#1037698: fixed in j4-dmenu-desktop 2.16-1.1
has caused the Debian Bug report #1037698,
regarding j4-dmenu-desktop: 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.)


-- 
1037698: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037698
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:j4-dmenu-desktop
Version: 2.16-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/j4-dmenu-desktop_2.16-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

[...]
  |  ^~~
/<>/src/Application.hh:149:22: error: unable to find string 
literal operator ‘operator""_istr’ with ‘const char [11]’, ‘long unsigned int’ 
arguments
  149 | case "OnlyShowIn"_istr:
  |  ^
/<>/src/Application.hh:161:22: error: unable to find string 
literal operator ‘operator""_istr’ with ‘const char [10]’, ‘long unsigned int’ 
arguments
  161 | case "NotShowIn"_istr:
  |  ^~~~
/<>/src/Application.hh:173:22: error: unable to find string 
literal operator ‘operator""_istr’ with ‘const char [7]’, ‘long unsigned int’ 
arguments
  173 | case "Hidden"_istr:
  |  ^
/<>/src/Application.hh:174:22: error: unable to find string 
literal operator ‘operator""_istr’ with ‘const char [10]’, ‘long unsigned int’ 
arguments
  174 | case "NoDisplay"_istr:
  |  ^~~~
/<>/src/Application.hh:182:22: error: unable to find string 
literal operator ‘operator""_istr’ with ‘const char [9]’, ‘long unsigned int’ 
arguments
  182 | case "Terminal"_istr:
  |  ^~~
/<>/src/Application.hh:183:61: error: unable to find string 
literal operator ‘operator""_istr’ with ‘const char [5]’, ‘long unsigned int’ 
arguments
  183 | this->terminal = make_istring(value) == "true"_istr;
  | ^~~
In file included from /<>/src/TestFormatters.cc:8:
/<>/src/Application.hh: In member function ‘bool 
Application::read(const char*, char**, size_t*)’:
/<>/src/Application.hh:94:19: warning: ignoring return value of 
‘char* getcwd(char*, size_t)’ declared with attribute ‘warn_unused_result’ 
[-Wunused-result]
   94 | getcwd(pwd, 100);
  | ~~^~
/<>/src/Main.hh: In member function ‘bool Main::read_args(int, 
char**)’:
/<>/src/Main.hh:167:33: warning: this statement may fall through 
[-Wimplicit-fallthrough=]
  167 | exclude_generic = true;
  | ^~
/<>/src/Main.hh:168:13: note: here
  168 | case 'l':
  | ^~~~
/<>/src/Main.hh: In member function ‘void Main::collect_files()’:
/<>/src/Main.hh:187:15: warning: ignoring return value of ‘char* 
getcwd(char*, size_t)’ declared with attribute ‘warn_unused_result’ 
[-Wunused-result]
  187 | getcwd(original_wd, 384);
  | ~~^~
/<>/src/Main.hh:195:18: warning: ignoring return value of ‘int 
chdir(const char*)’ declared with attribute ‘warn_unused_result’ 
[-Wunused-result]
  195 | chdir(path.c_str());
  | ~^~
/<>/src/Main.hh:204:14: warning: ignoring return value 

Bug#1036950: marked as done (schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6))

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 17:32:40 +
with message-id 
and subject line Bug#1036950: fixed in schleuder 3.6.0-3+deb11u2
has caused the Debian Bug report #1036950,
regarding schleuder: fails to upgrade from 'buster': insufficient dependency on 
ruby-activerecord (>= 2: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.)


-- 
1036950: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036950
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: schleuder
Version: 3.6.0-3+deb11u1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts

Hi,

during a test with piuparts I noticed your package fails to upgrade from
'buster'.
It installed fine in 'buster', then the upgrade to 'bullseye' fails.

Note that this failure only occurs during a 2-stage upgrade
(apt-get upgrade && apt-get distupgrade) in the apt-get upgrade step,
while a single-stage upgrade (only apt-get dist-upgrade) works fine.

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

  Setting up schleuder (3.6.0-3+deb11u1) ...
  Installing new version of config file /etc/schleuder/list-defaults.yml ...
  dpkg: error processing package schleuder (--configure):
   installed schleuder package post-installation script subprocess returned 
error exit status 1

I tried injecting 'set -x' into the postinst, but the output is not very
helpful:

Setting up schleuder (3.6.0-3+deb11u1) ...
+ set -e
+ id schleuder
+ chown schleuder /etc/schleuder
+ chown root:schleuder /etc/schleuder/schleuder.yml 
/etc/schleuder/list-defaults.yml
+ chmod 0640 /etc/schleuder/schleuder.yml /etc/schleuder/list-defaults.yml
+ chmod 0750 /var/lib/schleuder /var/log/schleuder
+ chown schleuder:schleuder /var/lib/schleuder /var/log/schleuder
+ [ -z 3.4.0-2+deb10u3 ]
+ dpkg --compare-versions 3.4.0-2+deb10u3 lt 3.0
+ SCHEMA=SCHEMA=/dev/null
+ runuser -u schleuder -- sh -c SCHEMA=/dev/null schleuder install >/dev/null
dpkg: error processing package schleuder (--configure):
 installed schleuder package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 schleuder

Entering the chroot after the failure and runnign 
  runuser -u schleuder -- sh -c 'SCHEMA=/dev/null schleuder install'
does not give any output either.

My guess is that there is some insufficiently versioned dependency that
has not yet been upgraded during 'apt-get upgrade' is required for this
comand to succeed.


cheers,

Andreas


schleuder_3.6.0-3+deb11u1.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: schleuder
Source-Version: 3.6.0-3+deb11u2
Done: Georg Faerber 

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

Debian distribution maintenance software
pp.
Georg Faerber  (supplier of updated schleuder 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, 24 Jun 2023 15:02:25 +
Source: schleuder
Architecture: source
Version: 3.6.0-3+deb11u2
Distribution: bullseye
Urgency: medium
Maintainer: Debian Ruby Team 

Changed-By: Georg Faerber 
Closes: 1036950
Changes:
 schleuder (3.6.0-3+deb11u2) bullseye; urgency=medium
 .
   * debian/control:
 - Add missing versioning on ruby-activerecord dependency. Before, upgrades
   from buster to bullseye might have failed if done in two stages, in
   contrast to only one stage, which worked as expected. Thanks to
   Hendrik Jäger and Andreas Beckmann for reporting this issue.
   (Closes: #1036950)
Checksums-Sha1:
 896a858b590b1f660708a8c2451fbae08d0e0aef 1686 schleuder_3.6.0-3+deb11u2.dsc
 13459afcfdd8928fc5aa53425683ebb7538828fa 294051 schleuder_3.6.0.orig.tar.gz
 e16c186deb9f64aef20bdb24c780dd5523b9b483 38208 
schleuder_3.6.0-3+deb11u2.debian.tar.xz
 b7c2f374dcd095996fffa91e43dbfb90e54f0ca9 10252 
schleuder_3.6.0-3+deb11u2_amd64.buildinfo
Checksums-Sha256:
 01f0bd5c4f7d7bc34445ccdab465469c6e875419ec4f5e2c04450f347d614072 1686 
schleuder_3.6.0-3+deb11u2.dsc
 f4077f30182335daf75897a35abe28e156fd9d78718dd7fed7a31fcb434b5cac 294051 

Bug#1037736: [Pkg-sass-devel] Bug#1037736: libsass: ftbfs with GCC-13

[Jonas Smedegaard]

Hi Bo,

Quoting Bo YU (2023-07-30 18:40:01)
> I have updated the symbols file to fix the issue, could you apply it on
> next upload?

Thanks a lot.  I will apply now.

If you are generally interested in SASS tools and want to help maintain
them in Debian, then you are very welcome to join the team (which is
effectively only me at the moment).

If you just wanted to help fix this one issue, then that is fine too, of
course.


> BTW, The issue should be the same with #1042201

Agreed, that is same issue.


Kind regards,

 - Jonas

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

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

signature.asc
Description: signature

Bug#1041810: marked as done (librsvg: CVE-2023-38633)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 16:46:00 +
with message-id 
and subject line Bug#1041810: fixed in librsvg 2.54.7+dfsg-1
has caused the Debian Bug report #1041810,
regarding librsvg: CVE-2023-38633
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.)


-- 
1041810: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041810
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: librsvg
Version: 2.54.5+dfsg-3
Severity: important
Tags: security upstream
Forwarded: https://gitlab.gnome.org/GNOME/librsvg/-/issues/996
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for librsvg.

CVE-2023-38633[0]:
| A directory traversal problem in the URL decoder of librsvg before
| 2.56.3 could be used by local or remote attackers to disclose files
| (on the local filesystem outside of the expected area), as
| demonstrated by href=".?../../../../../../../../../../etc/passwd" in
| an xi:include element.


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-38633
https://www.cve.org/CVERecord?id=CVE-2023-38633
[1] https://gitlab.gnome.org/GNOME/librsvg/-/issues/996

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: librsvg
Source-Version: 2.54.7+dfsg-1
Done: Simon McVittie 

We believe that the bug you reported is fixed in the latest version of
librsvg, 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.
Simon McVittie  (supplier of updated librsvg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Jul 2023 15:13:38 +0100
Source: librsvg
Architecture: source
Version: 2.54.7+dfsg-1
Distribution: unstable
Urgency: high
Maintainer: Debian GNOME Maintainers 

Changed-By: Simon McVittie 
Closes: 1041810
Changes:
 librsvg (2.54.7+dfsg-1) unstable; urgency=high
 .
   * Team upload
   * New upstream stable release 2.54.6
 - Fix a directory traversal vulnerability
   (Closes: #1041810, CVE-2023-38633)
 - Drop a redundant test-case that frequently regressed as a result of
   non-problematic font rendering changes
   * New upstream stable release 2.54.7
 - Fix compilation of 2.54.6 on rustc < 1.58
   * d/rules: Skip several known-failing reftests on big-endian architectures.
 These succeeded when librsvg_2.54.5+dfsg-1 was uploaded in September
 2022, but regressed sometime between then and the bookworm release,
 presumably as a result of changes in some other package.
 (Mitigates: #1038447)
Checksums-Sha1:
 c6645f9d5d3082f3a393b96d1fba9a842beab053 3080 librsvg_2.54.7+dfsg-1.dsc
 a9b696f80b361e4a6318edcd7e1a652676302171 14342756 
librsvg_2.54.7+dfsg.orig.tar.xz
 823a921914bf08cb3adb993a50ced7aeef3fd624 35024 
librsvg_2.54.7+dfsg-1.debian.tar.xz
 03262321dd4db8b653e2f09a1d8eba0393cda6db 11221 
librsvg_2.54.7+dfsg-1_source.buildinfo
Checksums-Sha256:
 88bb8664f3e434442f3330fad399e311bf022958f0e2130eebdc167da443a3f1 3080 
librsvg_2.54.7+dfsg-1.dsc
 799f93b73ed24c03efda1c707d8c40630fdee18c7e7532dda4ad1ce9671e98c2 14342756 
librsvg_2.54.7+dfsg.orig.tar.xz
 5fd18db125927059b9dee4ffb5aade9ddb77557429c3ea97c857f08250be2a21 35024 
librsvg_2.54.7+dfsg-1.debian.tar.xz
 a8b54de0fccaf5ad6cea0aab8065ab9c5e11c12e7b7e71a6701aa8544ab98921 11221 
librsvg_2.54.7+dfsg-1_source.buildinfo
Files:
 557a6f1c29ff8ba865caf33ac89689d8 3080 libs optional librsvg_2.54.7+dfsg-1.dsc
 4b6ba4f19da0a7859eaad6461246aa91 14342756 libs optional 
librsvg_2.54.7+dfsg.orig.tar.xz
 70a5621ffe4df3dad0429530fae2c975 35024 libs optional 
librsvg_2.54.7+dfsg-1.debian.tar.xz
 33bc153a6df925befb5043f4a8f3e04e 11221 libs optional 
librsvg_2.54.7+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAmTGinsACgkQ4FrhR4+B
TE+B6Q//daBbfbX0WINSpDsVuy/x4obZBc1Tg8WDby0NT+A+5NMS1sMWyNqKIGu0

Bug#1037736: libsass: ftbfs with GCC-13

[Bo YU]

Source: libsass
Version: 3.6.5+20220909-1
Followup-For: Bug #1037736
Tags: patch

Dear Maintainer,

I have updated the symbols file to fix the issue, could you apply it on
next upload?

BTW, The issue should be the same with #1042201

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


-- 
Regards,
--
  Bo YU

diff -Nru libsass-3.6.5+20220909/debian/changelog 
libsass-3.6.5+20220909/debian/changelog
--- libsass-3.6.5+20220909/debian/changelog 2022-12-12 22:05:31.0 
+0800
+++ libsass-3.6.5+20220909/debian/changelog 2023-07-31 00:22:41.0 
+0800
@@ -1,3 +1,10 @@
+libsass (3.6.5+20220909-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Updated libsass1.symbols. (Closes: #1037736)
+
+ -- Bo YU   Mon, 31 Jul 2023 00:22:41 +0800
+
 libsass (3.6.5+20220909-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru libsass-3.6.5+20220909/debian/libsass1.symbols 
libsass-3.6.5+20220909/debian/libsass1.symbols
--- libsass-3.6.5+20220909/debian/libsass1.symbols  2022-12-12 
22:01:19.0 +0800
+++ libsass-3.6.5+20220909/debian/libsass1.symbols  2023-07-31 
00:17:16.0 +0800
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 3.6.5+2021 amd64 arm64 armel armhf hppa 
hurd-i386 i386 ia64 m68k mips64el mipsel powerpc ppc64 ppc64el riscv64 s390x 
sh4 sparc64 x32
+# SymbolsHelper-Confirmed: 3.6.5+20220909 alpha amd64 riscv64
 libsass.so.1 libsass1 #MINVER#
  _Z10json_checkPK8JsonNodePc@Base 3.5.5-4~
  _Z11json_decodePKc@Base 3.5.5-4~
@@ -558,8 +558,8 @@
  _ZN4Sass12File_ContextD2Ev@Base 3.5.5-4~
  _ZN4Sass12OutputBufferC1ERKS0_@Base 3.6.4-4~
  _ZN4Sass12OutputBufferC2ERKS0_@Base 3.6.4-4~
- _ZN4Sass12OutputBufferD1Ev@Base 3.5.5-4~
- _ZN4Sass12OutputBufferD2Ev@Base 3.5.5-4~
+ (arch=alpha)_ZN4Sass12OutputBufferD1Ev@Base 3.6.5+20220909
+ (arch=alpha)_ZN4Sass12OutputBufferD2Ev@Base 3.6.5+20220909
  _ZN4Sass12SelectorList13cloneChildrenEv@Base 3.6.4-2~
  
_ZN4Sass12SelectorList19resolve_parent_refsESt6vectorINS_10SharedImplIS0_EESaIS3_EERS1_INS_9BacktraceESaIS6_EEb@Base
 3.6.4-2~
  
_ZN4Sass12SelectorList7performEPNS_9OperationINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base
 3.6.4-2~
@@ -752,7 +752,7 @@
  _ZN4Sass13color_to_nameERKNS_10Color_RGBAE@Base 3.6.4
  _ZN4Sass13color_to_nameEd@Base 3.5.5-4~
  _ZN4Sass13color_to_nameEi@Base 3.5.5-4~
- _ZN4Sass13compatibilityEPKc@Base 3.6.4-4~
+ (arch=alpha)_ZN4Sass13compatibilityEPKc@Base 3.6.5+20220909
  
_ZN4Sass13convert_unitsERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_RiS8_@Base
 3.5.5-4~
  
_ZN4Sass13escape_stringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
 3.5.5-4~
  _ZN4Sass13get_main_unitENS_9UnitClassE@Base 3.5.5-4~
@@ -1540,7 +1540,7 @@
  _ZN4Sass16Parent_ReferenceD0Ev@Base 3.6.4
  _ZN4Sass16Parent_ReferenceD1Ev@Base 3.6.4
  _ZN4Sass16Parent_ReferenceD2Ev@Base 3.6.4
- (optional=templinst|arch=!hurd-i386 !i386 
!m68k)_ZN4Sass16PtrObjEqualityFnINS_6StringEEEbPKT_S4_@Base 3.6.4-4~
+ (optional=templinst|arch=!amd64 !hurd-i386 !i386 !m68k 
!riscv64)_ZN4Sass16PtrObjEqualityFnINS_6StringEEEbPKT_S4_@Base 3.6.4-4~
  
_ZN4Sass16SupportsNegation7performEPNS_9OperationINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcE@Base
 3.6.4-2~
  _ZN4Sass16SupportsNegation7performEPNS_9OperationIP10Sass_ValueEE@Base 
3.6.4-2~
  _ZN4Sass16SupportsNegation7performEPNS_9OperationIPNS_10ExpressionEEE@Base 
3.6.4-2~
@@ -2527,14 +2527,14 @@
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer7exactlyILc58EEEPKcS5_S5_bb@Base
 3.6.4-2~
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer7exactlyILc91EEEPKcS5_S5_bb@Base
 3.6.4-2~
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer7exactlyIXadL_ZNS_9Constants8ellipsisEPKcS6_S6_bb@Base
 3.6.4-2~
- (optional=templinst|arch=!armel !armhf !hurd-i386 !i386 !mipsel !powerpc 
!ppc64 
!s390x)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer7exactlyIXadL_ZNS_9Constants8else_kwdEPKcS6_S6_bb@Base
 3.6.4-4~
+ (optional=templinst|arch=!alpha !armel !armhf !hurd-i386 !i386 !mipsel 
!powerpc !ppc64 
!s390x)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer7exactlyIXadL_ZNS_9Constants8else_kwdEPKcS6_S6_bb@Base
 3.6.4-4~
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer7kwd_andEPKcS4_bb@Base
 3.6.4-2~
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer8kwd_nullEPKcS4_bb@Base
 3.6.4-2~
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer8sequenceIXadL_ZNS2_12alternativesIXadL_ZNS2_3hexEPKcEEXadL_ZNS2_4hex0ES6_EEJEEES6_S6_EEXadL_ZNS2_6negateIXadL_ZNS2_7exactlyILc45EEES6_S6_S6_S6_EEJEEES6_S6_S6_bb@Base
 3.6.4-2~
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer8sequenceIXadL_ZNS2_16static_componentEPKcEEXadL_ZNS2_8one_plusIXadL_ZNS2_17strict_identifierES5_S5_S5_EEJEEES5_S5_S5_bb@Base
 3.6.4-4~
  
(optional=templinst)_ZN4Sass6Parser3lexIXadL_ZNS_8Prelexer8sequenceIXadL_ZNS2_7exactlyILc35EEEPKcS6_EEXadL_ZNS2_10identifierES6_EEJEEES6_S6_S6_bb@Base
 3.5.5-4~
  

Bug#1042582: openjdk-19 build depends on removed openjdk-18-jdk-headless

[Adrian Bunk]

Source: openjdk-19
Version: 19.0.2+7-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/package.php?p=openjdk-19

openjdk-19 build-depends on missing:
- openjdk-18-jdk-headless:mipsel

Processed: notfound 999935 in 7.1.1-1.1

[Debian Bug Tracking System]

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

> notfound 35 7.1.1-1.1
Bug #35 {Done: Bastian Germann } [src:varnish] varnish: 
depends on obsolete pcre3 library
No longer marked as found in versions varnish/7.1.1-1.1.
> thanks
Stopping processing here.

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

Processed: tagging 1037819

[Debian Bug Tracking System]

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

> tags 1037819 + ftbfs
Bug #1037819 {Done: Andrea Pappacoda } [src:pistache] 
pistache: ftbfs with GCC-13
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1037605: closed by Debian FTP Masters (reply to Ricardo Mones ) (Bug#1037605: fixed in claws-mail 4.1.1-3)

[Adrian Bunk]

On Sat, Jul 15, 2023 at 05:12:05PM +, Debian Bug Tracking System wrote:
>...
> Architecture: source amd64 all
>...
>  claws-mail (4.1.1-3) unstable; urgency=high
>...

Can you make an additional source-only upload for testing migration?

Thanks
Adrian

Processed: bug 1000020 is forwarded to https://salsa.debian.org/android-tools-team/android-platform-external-libselinux/-/merge_requests/13

[Debian Bug Tracking System]

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

> forwarded 120 
> https://salsa.debian.org/android-tools-team/android-platform-external-libselinux/-/merge_requests/13
Bug #120 [src:android-platform-external-libselinux] 
android-platform-external-libselinux: depends on obsolete pcre3 library
Set Bug forwarded-to-address to 
'https://salsa.debian.org/android-tools-team/android-platform-external-libselinux/-/merge_requests/13'.
> thanks
Stopping processing here.

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

Processed: block 999922 with 1037902

[Debian Bug Tracking System]

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

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

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

Processed: bug 999962 is forwarded to https://github.com/ggreer/the_silver_searcher/issues/1257

[Debian Bug Tracking System]

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

> forwarded 62 https://github.com/ggreer/the_silver_searcher/issues/1257
Bug #62 [src:silversearcher-ag] silversearcher-ag: depends on obsolete 
pcre3 library
Set Bug forwarded-to-address to 
'https://github.com/ggreer/the_silver_searcher/issues/1257'.
> thanks
Stopping processing here.

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

Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022

[Simon McVittie]

Control: severity -1 important

On Sun, 18 Jun 2023 at 14:52:18 +0100, Simon McVittie wrote:
> On Sun, 18 Jun 2023 at 14:47:00 +0100, Simon McVittie wrote:
> > I rebuilt librsvg in bookworm on the s390x porterbox zelenka, and can
> > confirm that 2.54.5+dfsg-1 now fails in bookworm too. So something must
> > have triggered a regression between September 2022 and now.
> 
> It would be helpful if someone with suitable hardware could put this
> through debbisect or similar to find out which build-dependency triggered
> this.

Since nobody seems to have had a chance to do this, and this FTBFS is now
blocking a fix for a security vulnerability (#1041810, CVE-2023-38633),
I'm going to disable the relevant tests, which lowers the severity of
this bug to important (verified to be sufficient to avoid the FTBFS on
the s390x porterbox, zelenka).

The result is that there are known mis-renderings for certain SVG
files on s390x, powerpc, ppc64 and other big-endian architectures,
some of which could be highly visible in desktop enviroments like GNOME
if icons happen to use of the relevant features. This is unfortunate,
but seems less of a disservice to our users than preventing a security
fix on the more widely-used little-endian architectures.

Help would still be appreciated from the porting teams for big-endian
architectures. This is probably not actually a librsvg bug, because the
same librsvg source code worked in September 2022 but failed in June 2023,
which would point to this being a regression in some other component (but
I don't know which one, and I don't have the hardware to run debbisect).

Thanks,
smcv

Processed: RM: theano, keras, deepnano -- RoM (theano), broken by numpy 1.24, theano mostly abandoned upstream

[Debian Bug Tracking System]

Processing control commands:

> affects -1 src:theano src:deepnano src:keras
Bug #1042574 [ftp.debian.org] RM: theano, keras, deepnano -- RoM (theano), 
broken by numpy 1.24, theano mostly abandoned upstream
Added indication that 1042574 affects src:theano, src:deepnano, and src:keras
> reopen 1026539
Bug #1026539 {Done: Andreas Tille } [src:theano] theano: 
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 
3.10 returned exit code 13
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions theano/1.1.2+dfsg-4.
> reopen 1027215
Bug #1027215 {Done: Andreas Tille } [src:theano] theano: 
autopkgtest fail with numpy/1.24.1
'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 theano/1.1.2+dfsg-4.

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

Processed: Re: Bug#1038447: librsvg: FTBFS on big-endian architectures: multiple test regressions since September 2022

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #1038447 [src:librsvg] librsvg: FTBFS on big-endian architectures: multiple 
test regressions since September 2022
Severity set to 'important' from 'serious'

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

Bug#1041810: librsvg: CVE-2023-38633

[Simon McVittie]

On Sun, 23 Jul 2023 at 21:13:38 +0200, Salvatore Bonaccorso wrote:
> The following vulnerability was published for librsvg.
> 
> CVE-2023-38633[0]:
> | A directory traversal problem in the URL decoder of librsvg before
> | 2.56.3 could be used by local or remote attackers to disclose files
> | (on the local filesystem outside of the expected area), as
> | demonstrated by href=".?../../../../../../../../../../etc/passwd" in
> | an xi:include element.

I'm testing

to fix this in unstable. In addition to importing the new upstream
release, we need to work around #1038447, otherwise there will be no
fixed version for s390x and the package will be unable to migrate -
I asked the porting teams for the big-endian architectures to debbisect
this and find out which package triggered #1038447, but it appears this
has not yet happened.

For stable, since librsvg has hardly changed since bookworm, I think
the best route will be a 2.54.7+dfsg-1~deb12u1 rather than backporting
individual changes (because we would have to backport the vast majority
of the delta between bookworm and unstable to fix #1041810 and avoid
FTBFSs anyway). #1038447 affects bookworm on s390x, so if the big-endian
architectures' porting teams cannot help to diagnose it, we will have
to work around it by skipping those tests and accepting that some SVGs
will be mis-rendered on BE architectures. Similarly, #1038252 affects
bookworm on i386, so we will have to work around that by skipping a
couple of tests.

One change that happened between bookworm's 2.54.5+dfsg-1 and trixie's
2.54.5+dfsg-3 is that Sebastien Bacher did the trip through NEW to add a
librsvg2-tests binary package and an autopkgtest that runs it:
,
.
This doesn't affect the contents of existing binary packages, it only
adds a new binary package. Would the security team be OK with including
that change for the sake of better test coverage and minimizing delta,
or do we need to revert it for a bookworm update?

Thanks,
smcv

Bug#1037703: marked as done (jsonnet: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 14:59:37 +
with message-id 
and subject line Bug#1037703: fixed in jsonnet 0.20.0+ds-1
has caused the Debian Bug report #1037703,
regarding jsonnet: 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.)


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

[This bug is targeted to the upcoming trixie release]

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

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

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

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

  apt-get -t=experimental install g++ 

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

[...]
/<>/cpp/libjsonnet++.cpp:46:31: error: ‘uint32_t’ was not declared 
in this scope
   46 | void Jsonnet::setGcMinObjects(uint32_t objects)
  |   ^~~~
/<>/cpp/libjsonnet++.cpp:46:31: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
/<>/cpp/libjsonnet++.cpp:66:6: error: variable or field 
‘setMaxTrace’ declared void
   66 | void Jsonnet::setMaxTrace(uint32_t lines)
  |  ^~~
/<>/cpp/libjsonnet++.cpp:66:27: error: ‘uint32_t’ was not declared 
in this scope
   66 | void Jsonnet::setMaxTrace(uint32_t lines)
  |   ^~~~
/<>/cpp/libjsonnet++.cpp:66:27: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
In file included from /<>/cpp/libjsonnet++.cpp:17:
/<>/include/libjsonnet++.h:49:22: error: ‘uint32_t’ has not been 
declared
   49 | void setMaxStack(uint32_t depth);
  |  ^~~~
/<>/include/libjsonnet++.h:53:26: error: ‘uint32_t’ has not been 
declared
   53 | void setGcMinObjects(uint32_t objects);
  |  ^~~~
/<>/include/libjsonnet++.h:63:22: error: ‘uint32_t’ has not been 
declared
   63 | void setMaxTrace(uint32_t lines);
  |  ^~~~
/<>/cpp/libjsonnet++.cpp:41:6: error: variable or field 
‘setMaxStack’ declared void
   41 | void Jsonnet::setMaxStack(uint32_t depth)
  |  ^~~
/<>/cpp/libjsonnet++.cpp:41:27: error: ‘uint32_t’ was not declared 
in this scope
   41 | void Jsonnet::setMaxStack(uint32_t depth)
  |   ^~~~
/<>/cpp/libjsonnet++.cpp:18:1: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
   17 | #include "libjsonnet++.h"
  +++ |+#include 
   18 | 
/<>/cpp/libjsonnet++.cpp:46:6: error: variable or field 
‘setGcMinObjects’ declared void
   46 | void Jsonnet::setGcMinObjects(uint32_t objects)
  |  ^~~
/<>/cpp/libjsonnet++.cpp:46:31: error: ‘uint32_t’ was not declared 
in this scope
   46 | void Jsonnet::setGcMinObjects(uint32_t objects)
  |   ^~~~
/<>/cpp/libjsonnet++.cpp:46:31: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
/<>/cpp/libjsonnet++.cpp:66:6: error: variable or field 
‘setMaxTrace’ declared void
   66 | void Jsonnet::setMaxTrace(uint32_t lines)
  |  ^~~
/<>/cpp/libjsonnet++.cpp:66:27: error: ‘uint32_t’ was not declared 
in this scope
   66 | void Jsonnet::setMaxTrace(uint32_t lines)
  |   ^~~~
/<>/cpp/libjsonnet++.cpp:66:27: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
make[4]: *** [cpp/CMakeFiles/libjsonnet++.dir/build.make:79: 
cpp/CMakeFiles/libjsonnet++.dir/libjsonnet++.cpp.o] Error 1
make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu'
make[3]: *** [CMakeFiles/Makefile2:641: cpp/CMakeFiles/libjsonnet++.dir/all] 

Bug#1037698: j4-dmenu-desktop: diff for NMU version 2.16-1.1

[Jochen Sprickerhof]

Control: tags 1037698 + patch


Dear maintainer,

I've prepared an NMU for j4-dmenu-desktop (versioned as 2.16-1.1). The diff
is attached to this message.

Regards.

Jochen
diff -Nru j4-dmenu-desktop-2.16/debian/changelog j4-dmenu-desktop-2.16/debian/changelog
--- j4-dmenu-desktop-2.16/debian/changelog	2018-09-10 21:26:15.0 +0200
+++ j4-dmenu-desktop-2.16/debian/changelog	2023-07-30 16:19:24.0 +0200
@@ -1,3 +1,10 @@
+j4-dmenu-desktop (2.16-1.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix build with GCC 13 (Closes: #1037698)
+
+ -- Jochen Sprickerhof   Sun, 30 Jul 2023 16:19:24 +0200
+
 j4-dmenu-desktop (2.16-1) unstable; urgency=medium
 
   * New upstream release 
diff -Nru j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch
--- j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch	1970-01-01 01:00:00.0 +0100
+++ j4-dmenu-desktop-2.16/debian/patches/0003-Fix-build-with-GCC-13.patch	2023-07-30 16:18:44.0 +0200
@@ -0,0 +1,28 @@
+From: Sam James 
+Date: Tue, 18 Apr 2023 11:08:53 +0100
+Subject: Fix build with GCC 13
+
+GCC 13 (as usual for new compiler releases) shuffles around some internal includes so some
+are no longer transitively included.
+
+See https://gnu.org/software/gcc/gcc-13/porting_to.html.
+
+Bug: https://bugs.gentoo.org/895200
+---
+ src/Application.hh | 3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+diff --git a/src/Application.hh b/src/Application.hh
+index 355be9b..d24ff1c 100644
+--- a/src/Application.hh
 b/src/Application.hh
+@@ -19,7 +19,8 @@
+ #define APPLICATION_DEF
+ 
+ #include 
+-#include 
++#include 
++#include 
+ #include 
+ 
+ #include "Utilities.hh"
diff -Nru j4-dmenu-desktop-2.16/debian/patches/series j4-dmenu-desktop-2.16/debian/patches/series
--- j4-dmenu-desktop-2.16/debian/patches/series	2018-09-10 21:26:15.0 +0200
+++ j4-dmenu-desktop-2.16/debian/patches/series	2023-07-30 16:18:48.0 +0200
@@ -1,2 +1,3 @@
 0001-remove-catch-download.patch
 0002-remove-testcase-for-desktop-systems.patch
+0003-Fix-build-with-GCC-13.patch


signature.asc
Description: PGP signature

Processed: j4-dmenu-desktop: diff for NMU version 2.16-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1037698 + patch
Bug #1037698 [src:j4-dmenu-desktop] j4-dmenu-desktop: ftbfs with GCC-13
Added tag(s) patch.

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

Bug#1033671: marked as done (MD5File() goes into an unconditional infinite loop on bullseye)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 14:06:10 +
with message-id 
and subject line Bug#1033671: fixed in libbsd 0.11.3-1+deb11u1
has caused the Debian Bug report #1033671,
regarding MD5File() goes into an unconditional infinite loop on bullseye
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.)


-- 
1033671: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033671
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libbsd0
Version: 0.11.3-1
Tags: patch,upstream,fixed-upstream,bullseye

MD5File in bullseye is essentially an infinite loop. It just calls
itself.

The simplest fix is

--- a/src/md5.c
+++ b/src/md5.c
@@ -105,7 +105,7 @@
 MD5File(const char *filename, char *buf)
 {
libmd_wrapper(MD5File);
-   return MD5File(filename, buf);
+   return libmd_MD5File(filename, buf);
 }
 
 char *

This was fixed upstream by 
https://gitlab.freedesktop.org/libbsd/libbsd/-/commit/e7cf8c5785b14fc8fbd37bb665a5f9a4f28c7888

-- 
Guillaume Morin 
--- End Message ---
--- Begin Message ---
Source: libbsd
Source-Version: 0.11.3-1+deb11u1
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated libbsd 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, 07 May 2023 19:13:23 +0200
Source: libbsd
Architecture: source
Version: 0.11.3-1+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Guillem Jover 
Changed-By: Guillem Jover 
Closes: 1033671
Changes:
 libbsd (0.11.3-1+deb11u1) bullseye; urgency=medium
 .
   * Fix infinite loop when using MD5File() symbol due to missing symbol
 redirection. Thanks to Guillaume Morin .
 Closes: #1033671
Checksums-Sha1:
 23bc12a94c049a61b0499e6a62994393672e4a2d 2324 libbsd_0.11.3-1+deb11u1.dsc
 14fdae710d8062e838c68936179c56a50857acd8 17980 
libbsd_0.11.3-1+deb11u1.debian.tar.xz
 865ee8ccbad11747197a5956542197b2727af184 6862 
libbsd_0.11.3-1+deb11u1_amd64.buildinfo
Checksums-Sha256:
 c5c817a1c86a7821c76e6e73d54fd018de8b022a0177da670b90a4f8d8dfbfb0 2324 
libbsd_0.11.3-1+deb11u1.dsc
 9745c6b40e3d719da54ed3da6a266a5e6c58ff823e70ba87244a5cf9c44cb9b9 17980 
libbsd_0.11.3-1+deb11u1.debian.tar.xz
 4de2f69f26a14a91626bbf32c0481ef70189b6b055a5c200de61f46d8231ae6b 6862 
libbsd_0.11.3-1+deb11u1_amd64.buildinfo
Files:
 8659dd1bbc48a26e0293d4e4621d2884 2324 libs optional libbsd_0.11.3-1+deb11u1.dsc
 8b263bbc00d5b7e8e1b05cf02fca0974 17980 libs optional 
libbsd_0.11.3-1+deb11u1.debian.tar.xz
 76caf24b26144902bc6af0d05ecf80e0 6862 libs optional 
libbsd_0.11.3-1+deb11u1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEETz509DYFDBD1aWV0uXK/PqSuV6MFAmRdeSsACgkQuXK/PqSu
V6PYDg//cBunu6nusyxTzmzdEfsFutjb+VUtF3rh+V6ZsjTRMy6Y7TWcm9b9lz0Y
VWo1NKRKYrUpJecY1pykym2UFj35Ji4I567It8CYqyX+ottLWyUVBrYFqGI3leie
dZ/xWhhHR6ukRcpn7Yh15xScdIUGQY8h+6aeDnqT5emhoBiCG9jilac/OqlIa/Pl
iexbTUAAQkpYGdMoC+AdXqNGrVzaTQeHx+xf9zbRok2MdttfW4ixTn+p24B0zGxY
NNLdAgaOL5mB6nsYgUVeEkOqptE5ddVh1Htj4VoarAQDT5rlgV8ZM4rEpzZ2RlF4
ovrv6Jfrh74DFiSNSuHPBMeWN8B8GpOnH3GttZyCLNeSFgiivVh/ZxSq1wMj/tmn
ktBm1I48UPPLmEduEfRtaXx5CVhZHaxRU8jK1ed6yB4Y6h8UpmyGNsOY4elFj/z/
7C9zGqKuI6sRf9iLasw9BFYiefZpO48/YGOkghHBBVRW3gdey3a68TW1SuIgtHNN
8duqD5pGI20cOcDav+9DYp7Flbip0JvMBDTp4MnpeEmCIWBmNOebqL0lJAT9gzGN
iSiguPLzmILK0nl2bMFbezR1ov73eY5/ecBkGrw/xQHGWmDxyvZt6uZzPoyD4Rto
fja65CABWISBIA8OBSklbLSF3xZf++7GgOy4znpGQdSz7mvtW1o=
=wV4k
-END PGP SIGNATURE End Message ---

Bug#1042570: ippsample: ippserver and ippfind are non-functional

[Brian Potkin]

Package: ippsample
Version: 0.0~git20220607.72f89b3
Severity: grave
Justification: renders package unusable


In spite of having the printing system wiped out (Bug#1040699) I installed
this package to try out ippserver.

brian@test-new:~$ /usr/sbin/ippserver -c $HOME/pdfsave -f application/pdf 
"Print to PDF"
/usr/sbin/ippserver: error while loading shared libraries: libcups.so.3: cannot 
open shared object file: No such file or directory
brian@test-new:~$

ippfind produces the same output.

Regards,

Brian.

Bug#1037779: marked as done (mmseqs2: ftbfs with GCC-13)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 12:42:08 +
with message-id 
and subject line Bug#1037779: fixed in mmseqs2 14-7e284+ds-2
has caused the Debian Bug report #1037779,
regarding mmseqs2: 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.)


-- 
1037779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037779
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:mmseqs2
Version: 14-7e284+ds-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/mmseqs2_14-7e284+ds-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

[...]
  |  ^~~~
/<>/src/commons/Parameters.h:16:1: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
   15 | #include "MultiParam.h"
  +++ |+#include 
   16 | 
/<>/src/commons/Debug.h:218:34: error: ‘SIZE_MAX’ was not declared 
in this scope
  218 | if(totalEntries==SIZE_MAX){
  |  ^~~~
/<>/src/commons/Debug.h:218:34: note: ‘SIZE_MAX’ is defined in 
header ‘’; did you forget to ‘#include ’?
/<>/src/commons/Parameters.h: In static member function ‘static 
bool Parameters::isEqualDbtype(int, int)’:
/<>/src/commons/Parameters.h:1135:26: error: ‘DBTYPE_MASK’ was not 
declared in this scope; did you mean ‘DBTYPE_MSA_DB’?
 1135 | return ((type1 & DBTYPE_MASK) == (type2 & DBTYPE_MASK));
  |  ^~~
  |  DBTYPE_MSA_DB
/<>/src/commons/Parameters.h: In static member function ‘static 
bool Parameters::isEqualDbtype(int, int)’:
/<>/src/commons/Parameters.h:1135:26: error: ‘DBTYPE_MASK’ was not 
declared in this scope; did you mean ‘DBTYPE_MSA_DB’?
 1135 | return ((type1 & DBTYPE_MASK) == (type2 & DBTYPE_MASK));
  |  ^~~
  |  DBTYPE_MSA_DB
/<>/src/commons/Parameters.h: In static member function ‘static 
const char* Parameters::getDbTypeName(int)’:
/<>/src/commons/Parameters.h:1139:26: error: ‘DBTYPE_MASK’ was not 
declared in this scope; did you mean ‘DBTYPE_MSA_DB’?
 1139 | switch (dbtype & DBTYPE_MASK) {
  |  ^~~
  |  DBTYPE_MSA_DB
/<>/src/commons/Parameters.h: In static member function ‘static 
const char* Parameters::getDbTypeName(int)’:
/<>/src/commons/Parameters.h:1139:26: error: ‘DBTYPE_MASK’ was not 
declared in this scope; did you mean ‘DBTYPE_MSA_DB’?
 1139 | switch (dbtype & DBTYPE_MASK) {
  |  ^~~
  |  DBTYPE_MSA_DB
In file included from /<>/src/commons/Sequence.h:10,
 from /<>/src/commons/ProfileStates.h:11,
 from /<>/src/commons/SubstitutionMatrix.h:13,
 from /<>/src/alignment/MsaFilter.h:9,
 from /<>/src/alignment/MsaFilter.cpp:7:
/<>/src/commons/Parameters.h: At global scope:
/<>/src/commons/Parameters.h:1132:18: error: ‘uint32_t’ does not 
name a type
 1132 | static const uint32_t DBTYPE_MASK = 0x;
  |  ^~~~
/<>/src/commons/Parameters.h:16:1: note: ‘uint32_t’ is defined in 
header ‘’; did you forget to ‘#include ’?
   15 | #include "MultiParam.h"
  +++ |+#include 
   16 | 
/<>/src/commons/Parameters.h: In static member function ‘static 
bool Parameters::isEqualDbtype(int, int)’:
/<>/src/commons/Parameters.h:1135:26: error: ‘DBTYPE_MASK’ was not 
declared in this scope; did 

Processed: mark as fixed

[Debian Bug Tracking System]

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

> fixed 1037541 libguestfs/1:1.50.1-4
Bug #1037541 {Done: Hilko Bengen } [src:libguestfs] 
libguestfs: FTBFS: supermin: error: lstat: Value too large for defined data 
type: /var/tmp/supermin2b73c8.tmpdir/base.d/init
Marked as fixed in versions libguestfs/1:1.50.1-4.
>
End of message, stopping processing here.

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

Bug#1042431: marked as done (libmedia-convert-perl: autopkgtest fails)

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 13:03:41 +0200
with message-id 
and subject line Done in 1.0.5-3
has caused the Debian Bug report #1042431,
regarding libmedia-convert-perl: autopkgtest fails
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.)


-- 
1042431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libmedia-convert-perl
Version: 1.0.4-3
Severity: serious
Tags: sid trixie
X-Debbugs-Cc: sramac...@debian.org

libmedia-convert-perl's autopkgtest fail with ffmpeg 6.0:

https://ci.debian.net/data/autopkgtest/testing/amd64/libm/libmedia-convert-perl/36194915/log.gz

166s Test Summary Report
166s ---
166s t/avsync.t   (Wstat: 256 (exited 1) Tests: 15 Failed: 1)
166s   Failed test:  15
166s   Non-zero exit status: 1
166s t/probe.t(Wstat: 256 (exited 1) Tests: 11 Failed: 1)
166s   Failed test:  3
166s   Non-zero exit status: 1
166s Files=11, Tests=126, 92 wallclock secs ( 0.04 usr  0.02 sys + 90.55 cusr  
2.94 csys = 93.55 CPU)
166s Result: FAIL

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Version: 1.0.5-3

This bug was fixed for real in 1.0.5-3, but it helps if you don't typo
the bug number :-)

-- 
 w@uter.{be,co.za}
wouter@{grep.be,fosdem.org,debian.org}

I will have a Tin-Actinium-Potassium mixture, thanks.--- End Message ---

Processed: your mail

[Debian Bug Tracking System]

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

> severity 1039859 important
Bug #1039859 [mixxx] mixxx: Mixxx GUI is broken / elements not rendered
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Processed: Forwarded

[Debian Bug Tracking System]

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

> forwarded 1040988 https://github.com/yshui/picom/issues/1104
Bug #1040988 [picom] Clashes with existing composite manager
Set Bug forwarded-to-address to 'https://github.com/yshui/picom/issues/1104'.
> thanks
Stopping processing here.

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

Bug#1039859: mixxx: Mixxx GUI is broken / elements not rendered

[Gregor Riepl]

Package: mixxx
Version: 2.3.5+dfsg-1+b1
Severity: important
Followup-For: Bug #1039859
X-Debbugs-Cc: onit...@gmail.com

This issue does not occur for me on X.org.

While the rendering of album covers and the waveforms is suboptimal (lack of
interpolation, movement jitter, transparency issues at the edges), it works
without issue for me. There was no change in rendering in bookworm, or even
trixie/sid.


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

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

Versions of packages mixxx depends on:
ii  libavcodec607:6.0-4
ii  libavformat60   7:6.0-4
ii  libavutil58 7:6.0-4
ii  libc6   2.37-6
ii  libchromaprint1 1.5.1-3
ii  libebur128-11.2.6-1+b1
ii  libflac12   1.4.3+ds-2
ii  libgcc-s1   13.1.0-9
ii  libglib2.0-02.76.4-4
ii  libhidapi-libusb0   0.14.0-1
ii  libid3tag0  0.15.1b-14
ii  liblilv-0-0 0.24.14-1
ii  libmad0 0.15.1b-10.1+b1
ii  libmodplug1 1:0.8.9.0-3
ii  libmp3lame0 3.100-6
ii  libogg0 1.3.5-3
ii  libopus01.4-1
ii  libopusfile00.12-4
ii  libportaudio2   19.6.0-1.2
ii  libportmidi01:217-6.1
ii  libprotobuf-lite32  3.21.12-6
ii  libqt5core5a5.15.10+dfsg-2
ii  libqt5dbus5 5.15.10+dfsg-2
ii  libqt5gui5  5.15.10+dfsg-2
ii  libqt5keychain1 0.14.1-1
ii  libqt5network5  5.15.10+dfsg-2
ii  libqt5opengl5   5.15.10+dfsg-2
ii  libqt5script5   5.15.10+dfsg-2
ii  libqt5scripttools5  5.15.10+dfsg-2
ii  libqt5sql5  5.15.10+dfsg-2
ii  libqt5sql5-sqlite   5.15.10+dfsg-2
ii  libqt5svg5  5.15.10-2
ii  libqt5widgets5  5.15.10+dfsg-2
ii  libqt5x11extras55.15.10-2
ii  libqt5xml5  5.15.10+dfsg-2
ii  librubberband2  3.2.1+dfsg-6
ii  libsndfile1 1.2.0-1
ii  libsoundtouch1  2.3.2+ds1-1
ii  libsqlite3-03.42.0-1
ii  libssl3 3.0.9-1
ii  libstdc++6  13.1.0-9
ii  libswresample4  7:6.0-4
ii  libtag1v5   1.13.1-1
ii  libupower-glib3 0.99.20-2
ii  libusb-1.0-02:1.0.26-1
ii  libvorbis0a 1.3.7-1
ii  libvorbisenc2   1.3.7-1
ii  libvorbisfile3  1.3.7-1
ii  libwavpack1 5.6.0-1
ii  libx11-62:1.8.6-1
ii  mixxx-data  2.3.5+dfsg-1

mixxx recommends no packages.

Versions of packages mixxx suggests:
ii  okular [pdf-viewer]  4:22.12.3-1

-- no debconf information

Bug#1031046: Asterisk packaging

[Jonas Smedegaard]

Hi Olivier,

Quoting Olivier (2023-06-02 11:24:44)
> I volunteer to help to package Asterisk either in current official
> Debian repo or in an alternative repository.

Great!

Please subscribe to our mailinglist and discuss more there.
And please consider joining our IRC/Matrix chat room/channel for more
casual hangout.
Info on both is listed at https://wiki.debian.org/Teams/VoIP/


> The perspectives of Asterisk Deb packaging is talked about in [1] (I'm
> the original author of this thread).
> 
> One thing that comes to mind reading [1] is that several people
> recommend packaging from scratch while it seems to me, that
> contributing in coordinated activities may lower the amount of work
> (no need to build a repo, to configure host to use a custom repo, ...)
> and increase the outcome quality as Debian standards are quite high.
> 
> If having Asterisk distributed with Bookwom is a lost cause, maybe we
> can try to have latest Asterisk 20.3 be packaged "the Debian way" in
> unstable repo and self assign the goal that this build would done by
> new contributors, under the control of experienced mainteners ?
> 
> Then, what could be the best media to read or add doc about Asterisk 
> packaging ?
> 
> [1] 
> https://community.asterisk.org/t/status-and-perspectives-of-asterisk-package-on-debian-bookworm/97087/11

I see 4 approaches:

1) Use what the Asterisk project officially offers.

2) Use what Debian project officially offers.

3) Use what Debian semi-officially offers as "backports".

4) DIY.

Each of those 4 approaches can be done either with least possible effort
on your own part, or through more active collaboration.

Option 1 is good for some users.  Evidently it isn't for me, or I would
not have spent the past 20 years adding patches and build routines on
top of what upstream projects could offer: I firmly believe that it is
benificial to have a "second stage development" focusing on integration
across upstream projects, and I firmly believe that Debian is the best
for doing that.  For those disagreeing, use option 1 or 4 :-)

Option 2 is currently off the table, because for Debian to be
officially "stable" the work has to be done *before* the distribution is
released as "stable", and not enough work was done for that to happen
for the current stable release.

Option 3 is still valid.  It requires help, not on climbing the whole
mountain of building a package, but on concrete narrow tasks of checking
for security bugs, isolating (or writing from scratch if you are really
cool) patches to fix those bugs, and (when baked into a package) testing
that the bugs are indeed fixed.  Only with *both* packaging *and*
maintenance (which includes security sheparding) of that packaging can
the work become semi-officially available in Debian backport.

Option 4 is always an option.  And for me personally is always a big
waste of time, compared to the more efficient collaboration possible
using Debian as a platform for it.  Feel free to disagree, but then
discuss those non-Debian approaches elsewhere than in Debian :-)


Hope to see a lot of you enthusiasts in the Debian VoIP team mailinglist
soon.  More info at https://wiki.debian.org/Teams/VoIP/


Kind regards,

 - Jonas

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

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

signature.asc
Description: signature

Bug#1031046: Error while trying to create asterisk-20.3.0 deb file

[Jonas Smedegaard]

Hi Daniel,

Quoting Daniel Huhardeaux via Pkg-voip-maintainers (2023-05-29 14:40:09)
> I try to create a deb file using dh_make
[...]
> Base package is asterisk-20-current.tar.gz
> 
> Any clue?

Sorry, but this is a bugreport for tracking the general health of
packaging Asterisk officially for Debian.

Official Debian packaging does not need someone starting over from
scratch (and such duplicate work is unlikely to succeed using dh_make
which was intended for small simple packages).

If you are interested in helping out improving the state of official
Debian packaging, then please join the VoIP team mailinglist and let's
discuss there how you can best help out - which (as posted in this
bugreport already) is more likely to be work related to composing and
testing patches for security bugs than it is work related to repackaging
Asterisk from scratch).

The team mailinglist and other related info is here:
https://wiki.debian.org/Teams/VoIP/


Kind regards,

 - Jonas

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

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

signature.asc
Description: signature

Processed: Re: Bug#1041349: transition: linphone-stack

[Debian Bug Tracking System]

Processing control commands:

> block -1 by 1026042
Bug #1041349 [release.debian.org] transition: linphone-stack
1041349 was not blocked by any bugs.
1041349 was not blocking any bugs.
Added blocking bug(s) of 1041349: 1026042

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

Bug#1031046: Asterisk removed from Debian Bookworm

[Jonas Smedegaard]

Hi Daniel (and others following along),

Quoting Devel via Pkg-voip-maintainers (2023-05-26 23:07:04)
> I'm ready to help to keep asterisk in the Debian project.
> 
> At this time I'm compiling from scratch on each new version (18 as well 
> as 20), I know nothing about creating packages but able to understand 
> the mechanism with a little help.

I don't see how Debian is helped by your packaging from scratch - but
obviously it can help *help* gain more knowledge on the codebase and
experience with tooling involved in packaging.

What is most urgently needed is someone looking at CVEs and other severe
bugs reported against Asterisk versions now in Debian unstable and
oldstable (and in a bright future also in testing and stable).

I am pretty fluent in packaging new upstream releases of Asterisk, but
do not have time for inspecting, fixing and testing bugs.


> I'm too on community list.

Not sure what you mean here.  The mailinglist used for Debian packaging
is pkg-voip-maintain...@lists.alioth.debian.org - as listed here:
https://wiki.debian.org/Teams/VoIP/


Kind regards,

 - Jonas

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

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

signature.asc
Description: signature

Bug#1031046: Asterisk removed from Debian Bookworm

[Jonas Smedegaard]

Quoting Antony Stone (2023-05-26 22:09:06)
> I am indeed interested in finding out what would be involved / required / 
> expected in order to help keep Asterisk as a package in a future release of 
> Debian Stable - and in the meantime, to ensure that it remains available in 
> Backports.

Backports is an *extension* to core package maintenance in Debian.

First the package needs to be in good shape in "unstable", then it gets
accepted into "testing", and only then can it (when released, every 2
years) enter "stable" and optionally ahead of that also "backports".

> I have asked on the Asterisk community list / forum to find out
> whether anyone else would be willing to join in, but I think the
> starting point for anyone agreeing to this needs to be - what would
> you want someone to do, if they have the time and interest to help in
> keeping Asterisk in Debian?

The VoIP team currently only have enough man power (me) to roll out
regular releases, and needs more people willing to check for and prepare
and test patches fixing severe bugs reported against any of the official
Debian branches where Asterisk is included - i.e. unstable, testing,
stable, and oldstable.
(Backports is only "officially unofficial" in that it comes without
security support, and oldoldstable only borrows infrastructure from
Debian but is maintained by a commercially driven coop).

Debian work is coordinated through the team mailinglist and in the
Debian bugreports (which act as tiny ad-hoc mailinglists as well), and
optionally the team also socializes and does casual chit-chat on irc
(bridged with Matrix): https://wiki.debian.org/Teams/VoIP/

Hope to welcome a lot of you on our mailinglist :-)


 - Jonas

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

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

signature.asc
Description: signature

Bug#1042557: xtensor builds with -march=native

[Matthias Klose]

Package: src:xtensor
Version: 0.24.3-2
Severity: serious
Tags: sid trixie

xtensor builds with -march=native.  I didn't check if there are code paths that 
work with the default baseline on amd64.  If there isn't such a code path, then 
it is another bug report.


However building -march=native is not deterministic, you never can say if the 
package works on your machine or, because it's just dependent on the buildd. 
From my point of view, no package should be built with -march=native.


At least GCC has -march=x86-64-v[1-4] for such settings, so please use that 
instead, and look for other appropriate settings on the other architectures.

Bug#1037226:

[Tobias Frost]

Control: fixed 1037226 1.0.3-1+b3
Control: close 1037226

Yes, this can be closed.
(Let me try again if the BTS now knows about the binNMU version)

-- 
tobi


signature.asc
Description: PGP signature

Processed: Re: Bug#1037226:

[Debian Bug Tracking System]

Processing control commands:

> fixed 1037226 1.0.3-1+b3
Bug #1037226 [libnginx-mod-http-modsecurity] libnginx-mod-http-modsecurity 
fails to start after update libmodsecurity3 to v3.0.9
Marked as fixed in versions libnginx-mod-http-modsecurity/1.0.3-1.
> close 1037226
Bug #1037226 [libnginx-mod-http-modsecurity] libnginx-mod-http-modsecurity 
fails to start after update libmodsecurity3 to v3.0.9
Marked Bug as done

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

Processed: tagging 1038126

[Debian Bug Tracking System]

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

> tags 1038126 + pending
Bug #1038126 {Done: Paul Gevers } [src:python-pyo] 
src:python-pyo: fails to migrate to testing for too long: FTBFS on i386
Added tag(s) pending.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Sun, 30 Jul 2023 06:25:54 +
with message-id 
and subject line Bug#1042537: fixed in manpages-l10n 4.19.0-7
has caused the Debian Bug report #1042537,
regarding manpages-fr-dev: trying to overwrite 
'/usr/share/man/fr/man3/uuid_generate_time_safe.3.gz', which is also in package 
util-linux-locales 2.39.1-3
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.)


-- 
1042537: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042537
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: manpages-fr-dev
Version: 4.19.0-6
Severity: serious

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

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

This is also a symlink.

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

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

manpages-fr-dev depends on no packages.

manpages-fr-dev recommends no packages.

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

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: manpages-l10n
Source-Version: 4.19.0-7
Done: Dr. Helge Kreutzmann 

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

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

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

Debian distribution maintenance software
pp.
Dr. Helge Kreutzmann  (supplier of updated manpages-l10n 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 30 Jul 2023 07:15:09 +0200
Source: manpages-l10n
Architecture: source
Version: 4.19.0-7
Distribution: unstable
Urgency: medium
Maintainer: Dr. Helge Kreutzmann 
Changed-By: Dr. Helge Kreutzmann 
Closes: 1042537
Changes:
 manpages-l10n (4.19.0-7) unstable; urgency=medium
 .
   * Missed another file remove due to a typo. Closes: #1042537
Checksums-Sha1:
 e6fda42af5156722c88f5bc0e291ea42b39881b9 3773 manpages-l10n_4.19.0-7.dsc
 b9a2924b25db7d2255d8322cf1d478c0b71654b7 72352 
manpages-l10n_4.19.0-7.debian.tar.xz
 d48fc3874be60703141262cf1d06baae4e252cc8 14376 
manpages-l10n_4.19.0-7_amd64.buildinfo
Checksums-Sha256:
 d80a6fc8ceb58ce087a834e43e2f76282c41fff3259a301818aead47f46473e9 3773 
manpages-l10n_4.19.0-7.dsc
 499731aec9246b4c23b7402427b06dba2a0cabc5b628a2d85beffc3a6783814e 72352 
manpages-l10n_4.19.0-7.debian.tar.xz
 abc62a5d1e4176d1c83e4aa49b4752115e697c848d0cac892f0d4c9066fbc39e 14376 
manpages-l10n_4.19.0-7_amd64.buildinfo
Files:
 26f1c2ce0e725bc6ca9987267c9af6c2 3773 doc optional manpages-l10n_4.19.0-7.dsc
 baa0431e0007b1f58e789a41ab5b845a 72352 doc optional 
manpages-l10n_4.19.0-7.debian.tar.xz
 fc970b4da5d31ed41080a57622c7b1f1 14376 doc optional 
manpages-l10n_4.19.0-7_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEbZZfteMW0gNUynuwQbqlJmgq5nAFAmTF/ZQACgkQQbqlJmgq
5nBTUw/9ET/HnNIX2l0O9dJysLVAenSwcmflCWOuVWJefXfyAZGij02B4GDYAPRq
CrCfNFmAuxN1zybt19nClDnTIhaCOx8sZW3st6ZNekmc37viN7roPnWHzJc08jxw
0tZsopiMEcguOp99NMktgGhMAT4vsfrRsJi/gOaHRMXZlMvnlZnP2ivsfvCuT/p+
d66dFFNHp/+4ZeE2N/6ZQMRDJKFPJXChb42y9qgcyMmU/a4yws25nH2Si7Bfr+dD

Bug#1041162: marked as pending in autopkgtest

[Paul Gevers]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/ci-team/autopkgtest/-/commit/39290ef8c66d4d2362720383643fd32cf88bf2a7


adt_testbed: restructure creation of pin file

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

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

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

Closes: #1041162


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1041162

Processed: Bug#1041162 marked as pending in autopkgtest

[Debian Bug Tracking System]

Processing control commands:

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

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