Bug#1018922: kbibtex crashes on startup

[Arnout Boelens]

Looks like it might be a QT bug:

https://bugs.kde.org/show_bug.cgi?id=433084

Bug#1018956: marked as done (kitty: Kitty has broken python 3.9 dependencies)

[Debian Bug Tracking System]

Your message dated Sat, 3 Sep 2022 21:33:36 -0400
with message-id <20220904013336.yohx25q6aoqxoapb@localhost>
and subject line Re: Bug#1018956: kitty: Kitty has broken python 3.9 
dependencies
has caused the Debian Bug report #1018956,
regarding kitty: Kitty has broken python 3.9 dependencies
to be marked as done.

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

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


-- 
1018956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: kitty
Version: 0.21.2-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
kitty does not start because of a missing shared library / wrong
dependency:

$ kitty
kitty: error while loading shared libraries: libpython3.9.so.1.0: cannot open 
shared object file: No such file or directory

It should probably be linked against libpython3.10


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

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

Versions of packages kitty depends on:
ii  kitty-terminfo  0.21.2-1
ii  libc6   2.34-4
ii  libdbus-1-3 1.14.0-2
ii  libfontconfig1  2.13.1-4.4
ii  libfreetype62.12.1+dfsg-3
ii  libharfbuzz0b   2.7.4-1+b1
ii  liblcms2-2  2.13.1-1
ii  libpng16-16 1.6.37-5
ii  libpython3.10   3.10.6-1
ii  libwayland-client0  1.21.0-1
ii  libx11-62:1.8.1-2
ii  libx11-xcb1 2:1.8.1-2
ii  libxkbcommon-x11-0  1.4.1-1
ii  libxkbcommon0   1.4.1-1
ii  python3 3.10.6-1
ii  python3.10  3.10.6-1
ii  zlib1g  1:1.2.11.dfsg-4.1

Versions of packages kitty recommends:
ii  kitty-doc 0.21.2-1
ii  libcanberra0  0.30-10

Versions of packages kitty suggests:
ii  imagemagick  8:6.9.11.60+dfsg-1.3+b3
ii  imagemagick-6.q16 [imagemagick]  8:6.9.11.60+dfsg-1.3+b3

-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Sep 02, 2022 at 04:03:49PM +0200, Alex wrote:
> Dear Maintainer,
> kitty does not start because of a missing shared library / wrong
> dependency:
> 
> $ kitty
> kitty: error while loading shared libraries: libpython3.9.so.1.0: cannot open 
> shared object file: No such file or directory
> 
> It should probably be linked against libpython3.10

It does.

$ ldd /usr/bin/kitty
linux-vdso.so.1 (0x7ffc789d8000)
libpython3.10.so.1.0 => /lib/x86_64-linux-gnu/libpython3.10.so.1.0 
(0x7f433dc0)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7f433d80)
libexpat.so.1 => /lib/x86_64-linux-gnu/libexpat.so.1 
(0x7f433e1e5000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x7f433dbe3000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7f433db08000)
/lib64/ld-linux-x86-64.so.2 (0x7f433e236000)
$ apt-cache show kitty | grep -o '[^ ]*python3[^ ]*'
python3
python3
python3.10,
python3:any,
libpython3.10

At a guess, you have some other install of kitty which hasn't been
rebuilt against the new Python.  "which kitty" whould clarify that.

Cheers,
-- 
James
GPG Key: 4096R/91BF BF4D 6956 BD5D F7B7  2D23 DFE6 91AE 331B A3DB--- End Message ---

Processed: add more tags to gnome-initial-setup bug

[Debian Bug Tracking System]

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

> tags 1019106 bookworm sid ftbfs pending
Bug #1019106 [src:gnome-initial-setup] gnome-initial-setup: Needs updating for 
evolution-data-server 3.46
Added tag(s) pending, ftbfs, sid, and bookworm.
>
End of message, stopping processing here.

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

Processed: Re: gnome-initial-setup: Needs updating for evolution-data-server 3.46

[Debian Bug Tracking System]

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

> fixed 1019106 43~beta-1
Bug #1019106 [src:gnome-initial-setup] gnome-initial-setup: Needs updating for 
evolution-data-server 3.46
Marked as fixed in versions gnome-initial-setup/43~beta-1.
>
End of message, stopping processing here.

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

Processed: Re: gnome-initial-setup: Needs updating for evolution-data-server 3.46

[Debian Bug Tracking System]

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

> block 1019106 by 1016765
Bug #1019106 [src:gnome-initial-setup] gnome-initial-setup: Needs updating for 
evolution-data-server 3.46
1019106 was not blocked by any bugs.
1019106 was not blocking any bugs.
Added blocking bug(s) of 1019106: 1016765
>
End of message, stopping processing here.

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

Bug#1019106: gnome-initial-setup: Needs updating for evolution-data-server 3.46

[Jeremy Bicha]

Source: gnome-initial-setup
Version: 42.2-1
Severity: serious
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: evolution-3.46

gnome-initial-setup needs to be updated for the big
evolution-data-server transition (which switches to libsoup3 and
librest 0.9).

This is done in the 43 version but the 43 version also requires the
GTK4 version of webkit2gtk (the 5.0 API) which is only built in
Experimental currently.

Therefore, my plan is for gnome-initial-setup to become temporarily
uninstallable in Unstable and removed from Testing until webkit2gtk
2.38 is uploaded to Unstable later this month. This allows us to
complete the rest of the transition.

Thank you,
Jeremy Bicha

Bug#1019090: librust-petgraph-dev: impossible to satisfy dependency

[Peter Michael Green]

There is a new upstream version of petgraph that uses the new version of 
fixedbitset, I suspect the most sensible way to fix this bug is 
uploading it and it has been prepared in debcargo-conf (initially 
byBlair Noctis with some further tweaking by myself)


However before I upload it, I wanted to check the reverse dependencies, 
I go started on doing so but rust-cargo-lock proved to be a fair bit of 
effort to update. I'll probablly look at the remaining packages soon, 
but if others want to take a look that is fine too.


rust-cargo-lock - update prepared in debcargo-conf (along with updates 
for gumdrop and gumdrop-derive which it depends on)

rust-lalrpop -update prepared in debcargo-conf
rust-rust-code-analysis - already broken and not in testing.
rust-tree-magic - update prepared in debcargo-conf
rust-tree-magic-mini - fixed upstream, but Debian packaging not 
investigated yet.

librust-ena+congruence-closure-dev - not investigated yet
librust-parking-lot-core+petgraph-dev - already depends on new version 
of petgraph

librust-parking-lot-core-0.4+petgraph-dev - not investigated yet
rust-code-analysis-cli - indirect depedency/built-using, already broken 
and not in testing.

Processed: Re: Bug#1019061: gnuplot-data not available

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 gnuplot and gnuplot-data not available
Bug #1019061 [gnuplot] gnuplot-data not available
Changed Bug title to 'gnuplot and gnuplot-data not available' from 
'gnuplot-data not available'.
> reassign -1 src:gnuplot 5.4.4+dfsg1-1
Bug #1019061 [gnuplot] gnuplot and gnuplot-data not available
Bug reassigned from package 'gnuplot' to 'src:gnuplot'.
No longer marked as found in versions 5.4.4+dfsg1-1.
Ignoring request to alter fixed versions of bug #1019061 to the same values 
previously set
Bug #1019061 [src:gnuplot] gnuplot and gnuplot-data not available
Marked as found in versions gnuplot/5.4.4+dfsg1-1.

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

Bug#1019061: gnuplot-data not available

[Vincent Lefevre]

Control: retitle -1 gnuplot and gnuplot-data not available
Control: reassign -1 src:gnuplot 5.4.4+dfsg1-1

This is actually a problem for the binary packages gnuplot-qt,
gnuplot-x11 and gnuplot-nox. The gnuplot metapackage is not
available either, while it is still mentioned at

  https://packages.debian.org/source/unstable/gnuplot

(but this one would not alone prevent an upgrade).

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

Processed: Re: Bug#1019061: gnuplot-data not available

[Debian Bug Tracking System]

Processing control commands:

> severity -1 serious
Bug #1019061 [gnuplot] gnuplot-data not available
Severity set to 'serious' from 'important'

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

Processed: nextepc: diff for NMU version 0.3.10+nods-4.2

[Debian Bug Tracking System]

Processing control commands:

> tags 984256 + pending
Bug #984256 [src:nextepc] nextepc: ftbfs with GCC-11
Added tag(s) pending.

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

Bug#984256: nextepc: diff for NMU version 0.3.10+nods-4.2

[Sudip Mukherjee]

Control: tags 984256 + pending
--

Dear maintainer,

I've prepared an NMU for nextepc (versioned as 0.3.10+nods-4.2) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

--
Regards
Sudip

diff -Nru nextepc-0.3.10+nods/debian/changelog 
nextepc-0.3.10+nods/debian/changelog
--- nextepc-0.3.10+nods/debian/changelog2021-02-06 16:02:21.0 
+
+++ nextepc-0.3.10+nods/debian/changelog2022-09-04 00:29:25.0 
+0100
@@ -1,3 +1,11 @@
+nextepc (0.3.10+nods-4.2) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix ftbfs with GCC-11. (Closes: #984256)
+- Thanks Steve for the patch.
+
+ -- Sudip Mukherjee   Sun, 04 Sep 2022 00:29:25 
+0100
+
 nextepc (0.3.10+nods-4.1) unstable; urgency=medium
 
   * Non-maintainer upload.
diff -Nru nextepc-0.3.10+nods/debian/patches/gcc-11.patch 
nextepc-0.3.10+nods/debian/patches/gcc-11.patch
--- nextepc-0.3.10+nods/debian/patches/gcc-11.patch 1970-01-01 
01:00:00.0 +0100
+++ nextepc-0.3.10+nods/debian/patches/gcc-11.patch 2022-09-04 
00:23:48.0 +0100
@@ -0,0 +1,27 @@
+Description: fix build failure with gcc-11.
+Author: Steve Langasek 
+Bug-Debian: https://bugs.debian.org/984256
+Last-Update: 2021-11-18
+
+Index: nextepc-0.3.10+nods/lib/core/test/testatomic.c
+===
+--- nextepc-0.3.10+nods.orig/lib/core/test/testatomic.c
 nextepc-0.3.10+nods/lib/core/test/testatomic.c
+@@ -100,7 +100,7 @@
+ 
+ static void test_casptr_equal_nonnull(abts_case *tc, void *data)
+ {
+-int a, b;
++int a = 0, b = 0;
+ void *target_ptr = 
+ void *old_ptr;
+ 
+@@ -111,7 +111,7 @@
+ 
+ static void test_casptr_notequal(abts_case *tc, void *data)
+ {
+-int a, b;
++int a = 0, b = 0;
+ void *target_ptr = 
+ void *old_ptr;
+ 
diff -Nru nextepc-0.3.10+nods/debian/patches/series 
nextepc-0.3.10+nods/debian/patches/series
--- nextepc-0.3.10+nods/debian/patches/series   2021-01-23 22:35:09.0 
+
+++ nextepc-0.3.10+nods/debian/patches/series   2022-09-04 00:23:48.0 
+0100
@@ -5,3 +5,4 @@
 0005-Set-install-dir-for-freediameter-libs.patch
 0006-Fix-big-endian-bug.patch
 0007-Patch-deprecated-sys-sysctl.h-problem.patch
+gcc-11.patch

Processed: Re: Bug#1018717: orage: extra informations

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1018717 [orage] orage: Segmentation fault
Severity set to 'normal' from 'grave'
> forwarded -1 https://gitlab.xfce.org/apps/orage/-/issues/2
Bug #1018717 [orage] orage: Segmentation fault
Set Bug forwarded-to-address to 'https://gitlab.xfce.org/apps/orage/-/issues/2'.

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

Bug#1018717: orage: extra informations

[Unit 193]

Control: severity -1 normal
Control: forwarded -1 https://gitlab.xfce.org/apps/orage/-/issues/2

Howdy,

Thanks for providing some information and testing on unstable, I was about 
to close the bug report as it lacked any information and was clearly a 
FrankenDebian[0].


What you're seeing is due to the fact that orage doesn't yet support 
Wayland.  As orage's target is the Xfce desktop (as shown by being an Xfce 
app, and the description has it all over) this is somewhat to be expected 
as Xfce itself doesn't have support for Wayland.


This bug will likely be fixed in due time as different aspects of Xfce 
gain support for Wayland, and can be tracked on the upstream bug 
report[1].



[0]: https://wiki.debian.org/DontBreakDebian
[1]: https://gitlab.xfce.org/apps/orage/-/issues/2

~Unit 193
Unit193 @ Libera
Unit193 @ OFTC

Bug#1011732: marked as done (gtk-d: FTBFS: build-dependency not installable: libphobos2-ldc-shared98 (>= 1:1.28.0))

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 22:19:39 +
with message-id 
and subject line Bug#1011732: fixed in gtk-d 3.10.0-2
has caused the Debian Bug report #1011732,
regarding gtk-d: FTBFS: build-dependency not installable: 
libphobos2-ldc-shared98 (>= 1:1.28.0)
to be marked as done.

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

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


-- 
1011732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtk-d
Version: 3.10.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220525 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper (>= 12), dh-dlang (>= 0.6.5), gir-to-d, 
> gnome-pkg-tools (>= 0.10), libgstreamer-plugins-base1.0-dev, 
> libgstreamer1.0-dev, libgtk-3-dev, libgtksourceview-3.0-dev, libpeas-dev, 
> libvte-2.91-dev, build-essential, fakeroot
> Filtered Build-Depends: debhelper (>= 12), dh-dlang (>= 0.6.5), gir-to-d, 
> gnome-pkg-tools (>= 0.10), libgstreamer-plugins-base1.0-dev, 
> libgstreamer1.0-dev, libgtk-3-dev, libgtksourceview-3.0-dev, libpeas-dev, 
> libvte-2.91-dev, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [957 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [449 B]
> Get:5 copy:/<>/apt_archive ./ Packages [534 B]
> Fetched 1940 B in 0s (136 kB/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  gir-to-d : Depends: libphobos2-ldc-shared98 (>= 1:1.28.0) but it is not 
> installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2022/05/25/gtk-d_3.10.0-1_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220525;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220525=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 marking 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: gtk-d
Source-Version: 3.10.0-2
Done: Jeremy Bicha 

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

Debian distribution maintenance software
pp.
Jeremy Bicha  (supplier of updated gtk-d 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: Tue, 30 Aug 2022 18:21:39 -0400
Source: gtk-d
Built-For-Profiles: noudeb
Architecture: source
Version: 3.10.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian GNOME 

Processed: tagging 1018796

[Debian Bug Tracking System]

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

> tags 1018796 + ftbfs
Bug #1018796 [mir-core] mir-core: FTBFS with gdc: unrecognized commandline 
option -preview=dip1008
Added tag(s) ftbfs.
> thanks
Stopping processing here.

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

Bug#1012219: marked as done (r-cran-rstan: FTBFS with onetbb/2021.5.0-9 in experimental)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 21:54:45 +
with message-id 
and subject line Bug#1012219: fixed in r-cran-rstan 2.21.5-2
has caused the Debian Bug report #1012219,
regarding r-cran-rstan: FTBFS with onetbb/2021.5.0-9 in experimental
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.)


-- 
1012219: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012219
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-rstan
Version: 2.21.5-1
Severity: normal
Tags: ftbfs

Hello,

tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-9
in experimental, current source failed to build with the following:

** testing if installed package can be loaded from temporary location
Error: package or namespace load failed for 'rstan' in dyn.load(file,
DLLpath = DLLpath, ...):
 unable to load shared object
'/home/merkys/r-cran-rstan-2.21.5/debian/r-cran-rstan/usr/lib/R/site-library/00LOCK-r-cran-rstan-2.21.5/00new/rstan/libs/rstan.so':

/home/merkys/r-cran-rstan-2.21.5/debian/r-cran-rstan/usr/lib/R/site-library/00LOCK-r-cran-rstan-2.21.5/00new/rstan/libs/rstan.so:
undefined symbol: _ZN3tbb8internal26task_scheduler_observer_v37observeEb
Error: loading failed
Execution halted

Andrius
--- End Message ---
--- Begin Message ---
Source: r-cran-rstan
Source-Version: 2.21.5-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated r-cran-rstan package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Sep 2022 02:36:28 +0530
Source: r-cran-rstan
Architecture: source
Version: 2.21.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Nilesh Patra 
Closes: 1011218 1012144 1012219
Changes:
 r-cran-rstan (2.21.5-2) unstable; urgency=medium
 .
   * Team Upload.
   [ Andreas Tille ]
   * Rebuild
 .
   [ Nilesh Patra ]
   * Add in versioned B-D and dep on r-cran-stanheaders to
 ease rebuilding/transition
 (Closes: #1011218, #1012144, #1012219)
Checksums-Sha1:
 e852be9f564acdf06bfd4c2fc684346d7eabf977 2285 r-cran-rstan_2.21.5-2.dsc
 db28bbe8b82589a3fde1187e26bdc5c3a96c36a1 4372 
r-cran-rstan_2.21.5-2.debian.tar.xz
 4a0c91dd79cbe3fa9ce740280f6c236080528488 12726 
r-cran-rstan_2.21.5-2_amd64.buildinfo
Checksums-Sha256:
 f31881cbb25a1bc3946979fa5da5e6af2fcf1ed1803d7ab8bb5cddf5fba96af5 2285 
r-cran-rstan_2.21.5-2.dsc
 fc8cad781b1d34bf8f952a50ca52c331812857ae73a0d7017be87e03b4104b87 4372 
r-cran-rstan_2.21.5-2.debian.tar.xz
 f667ee6e475753c991b279ae38121eb4fda4ddb34d74c413f414d1533a570ac4 12726 
r-cran-rstan_2.21.5-2_amd64.buildinfo
Files:
 21e9e0cc2c8fa1cd3fc9fc19ec4be536 2285 gnu-r optional r-cran-rstan_2.21.5-2.dsc
 4642f742542854add62d50d127dc19d8 4372 gnu-r optional 
r-cran-rstan_2.21.5-2.debian.tar.xz
 1f2f98615386badeda2da7ed57dc4be2 12726 gnu-r optional 
r-cran-rstan_2.21.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmMTxJ0SHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxwHAP/R75wToZGNQOjctPAQ6LnTgivhMHYFzt
DpHnXT8HGVnGxuowVV7F83NvEcZN6EJQmCvfqIBLm+W4/KJ6l0VW6R7d4wSqDnLk
DYajBguhMILMeQ1VlIOG7jOz/nc6yOTPIqjZc10BxxCJ0hdbyUqcLONd4OoEINFX
Jch3H0KLkkf3LL+QrXOF3bapg+KWiufA07/4NjTXofqKP0KzO6fNmboNt9Ge44g9
fren9ofa4jTBT/GP7ziUL0/SlsTMsGQMMJjB4bSR9l/hbBp/hjJg+r7Ah6uNs7WH
bMfhm73gnylEDvNijUlYetfJQQH3tA5z1jDrkCISH1TfEMF1OU2DfGC0KKE+ZZQZ
9AP/W0I4/5D1UFv8L6NNval357oQKymFLhm69mvd5C/e2bZvAC3QIPvkqenfNsxX
kqj7fIP/yhhlKLA/LzN/NYpC/c8AS17UOUz1od2QnypuwfzFUaq1sMy/5klGKDd7
/daKVYl67JvX76gC+vJh+RAtQniQoiT7K5OaPHk3n+62E1yLosKjyd6QGTvBquhW
EEUjrfmHeRQM1VGFKtWQb5xwxAS1QUI6HGvDil4OAxFIhU2rxNd8f18CUk1JKeLR
xY6hqRnHPVdQiMWuuyFCSZ27CFAsFRumn/8dXE50XGm1wysz3Sm50BsMW4b+0bh0
PG9aJA0AC+Yb
=Mpd5
-END PGP SIGNATURE End Message ---

Bug#1012144: marked as done (r-cran-shinystan: FTBFS with onetbb/2021.5.0-8 in experimental)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 21:54:45 +
with message-id 
and subject line Bug#1012144: fixed in r-cran-rstan 2.21.5-2
has caused the Debian Bug report #1012144,
regarding r-cran-shinystan: FTBFS with onetbb/2021.5.0-8 in experimental
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.)


-- 
1012144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012144
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-shinystan
Version: 2.6.0-1
Severity: normal
Tags: ftbfs

Hello,

tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-8
in experimental, current source failed to build with the following:

** byte-compile and prepare package for lazy loading
Error in dyn.load(file, DLLpath = DLLpath, ...) :
  unable to load shared object
'/usr/lib/R/site-library/rstan/libs/rstan.so':
  /usr/lib/R/site-library/rstan/libs/rstan.so: undefined symbol:
_ZN3tbb8internal26task_scheduler_observer_v37observeEb
Error: unable to load R code in package ‘shinystan’
Execution halted

Andrius
--- End Message ---
--- Begin Message ---
Source: r-cran-rstan
Source-Version: 2.21.5-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated r-cran-rstan package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Sep 2022 02:36:28 +0530
Source: r-cran-rstan
Architecture: source
Version: 2.21.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Nilesh Patra 
Closes: 1011218 1012144 1012219
Changes:
 r-cran-rstan (2.21.5-2) unstable; urgency=medium
 .
   * Team Upload.
   [ Andreas Tille ]
   * Rebuild
 .
   [ Nilesh Patra ]
   * Add in versioned B-D and dep on r-cran-stanheaders to
 ease rebuilding/transition
 (Closes: #1011218, #1012144, #1012219)
Checksums-Sha1:
 e852be9f564acdf06bfd4c2fc684346d7eabf977 2285 r-cran-rstan_2.21.5-2.dsc
 db28bbe8b82589a3fde1187e26bdc5c3a96c36a1 4372 
r-cran-rstan_2.21.5-2.debian.tar.xz
 4a0c91dd79cbe3fa9ce740280f6c236080528488 12726 
r-cran-rstan_2.21.5-2_amd64.buildinfo
Checksums-Sha256:
 f31881cbb25a1bc3946979fa5da5e6af2fcf1ed1803d7ab8bb5cddf5fba96af5 2285 
r-cran-rstan_2.21.5-2.dsc
 fc8cad781b1d34bf8f952a50ca52c331812857ae73a0d7017be87e03b4104b87 4372 
r-cran-rstan_2.21.5-2.debian.tar.xz
 f667ee6e475753c991b279ae38121eb4fda4ddb34d74c413f414d1533a570ac4 12726 
r-cran-rstan_2.21.5-2_amd64.buildinfo
Files:
 21e9e0cc2c8fa1cd3fc9fc19ec4be536 2285 gnu-r optional r-cran-rstan_2.21.5-2.dsc
 4642f742542854add62d50d127dc19d8 4372 gnu-r optional 
r-cran-rstan_2.21.5-2.debian.tar.xz
 1f2f98615386badeda2da7ed57dc4be2 12726 gnu-r optional 
r-cran-rstan_2.21.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmMTxJ0SHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxwHAP/R75wToZGNQOjctPAQ6LnTgivhMHYFzt
DpHnXT8HGVnGxuowVV7F83NvEcZN6EJQmCvfqIBLm+W4/KJ6l0VW6R7d4wSqDnLk
DYajBguhMILMeQ1VlIOG7jOz/nc6yOTPIqjZc10BxxCJ0hdbyUqcLONd4OoEINFX
Jch3H0KLkkf3LL+QrXOF3bapg+KWiufA07/4NjTXofqKP0KzO6fNmboNt9Ge44g9
fren9ofa4jTBT/GP7ziUL0/SlsTMsGQMMJjB4bSR9l/hbBp/hjJg+r7Ah6uNs7WH
bMfhm73gnylEDvNijUlYetfJQQH3tA5z1jDrkCISH1TfEMF1OU2DfGC0KKE+ZZQZ
9AP/W0I4/5D1UFv8L6NNval357oQKymFLhm69mvd5C/e2bZvAC3QIPvkqenfNsxX
kqj7fIP/yhhlKLA/LzN/NYpC/c8AS17UOUz1od2QnypuwfzFUaq1sMy/5klGKDd7
/daKVYl67JvX76gC+vJh+RAtQniQoiT7K5OaPHk3n+62E1yLosKjyd6QGTvBquhW
EEUjrfmHeRQM1VGFKtWQb5xwxAS1QUI6HGvDil4OAxFIhU2rxNd8f18CUk1JKeLR
xY6hqRnHPVdQiMWuuyFCSZ27CFAsFRumn/8dXE50XGm1wysz3Sm50BsMW4b+0bh0
PG9aJA0AC+Yb
=Mpd5
-END PGP SIGNATURE End Message ---

Bug#1011218: marked as done (r-cran-brms: FTBFS with onetbb/2021.5.0-8 in experimental)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 21:54:45 +
with message-id 
and subject line Bug#1011218: fixed in r-cran-rstan 2.21.5-2
has caused the Debian Bug report #1011218,
regarding r-cran-brms: FTBFS with onetbb/2021.5.0-8 in experimental
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.)


-- 
1011218: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011218
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-brms
Version: 2.17.0-1
Severity: normal
Tags: ftbfs

Hello,

tbb/onetbb transition (#1007222) is currently in the planning. During
test rebuild of libtbb-dev reverse dependencies with onetbb/2021.5.0-8
in experimental, current source failed to build with the following:

** inst
** byte-compile and prepare package for lazy loading
Error in dyn.load(file, DLLpath = DLLpath, ...) :
  unable to load shared object
'/usr/lib/R/site-library/rstan/libs/rstan.so':
  /usr/lib/R/site-library/rstan/libs/rstan.so: undefined symbol:
_ZN3tbb8internal26task_scheduler_observer_v37observeEb
Calls:  ...  -> loadNamespace -> library.dynam ->
dyn.load
Execution halted
ERROR: lazy loading failed for package ‘brms’

Andrius
--- End Message ---
--- Begin Message ---
Source: r-cran-rstan
Source-Version: 2.21.5-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated r-cran-rstan package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 04 Sep 2022 02:36:28 +0530
Source: r-cran-rstan
Architecture: source
Version: 2.21.5-2
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers 
Changed-By: Nilesh Patra 
Closes: 1011218 1012144 1012219
Changes:
 r-cran-rstan (2.21.5-2) unstable; urgency=medium
 .
   * Team Upload.
   [ Andreas Tille ]
   * Rebuild
 .
   [ Nilesh Patra ]
   * Add in versioned B-D and dep on r-cran-stanheaders to
 ease rebuilding/transition
 (Closes: #1011218, #1012144, #1012219)
Checksums-Sha1:
 e852be9f564acdf06bfd4c2fc684346d7eabf977 2285 r-cran-rstan_2.21.5-2.dsc
 db28bbe8b82589a3fde1187e26bdc5c3a96c36a1 4372 
r-cran-rstan_2.21.5-2.debian.tar.xz
 4a0c91dd79cbe3fa9ce740280f6c236080528488 12726 
r-cran-rstan_2.21.5-2_amd64.buildinfo
Checksums-Sha256:
 f31881cbb25a1bc3946979fa5da5e6af2fcf1ed1803d7ab8bb5cddf5fba96af5 2285 
r-cran-rstan_2.21.5-2.dsc
 fc8cad781b1d34bf8f952a50ca52c331812857ae73a0d7017be87e03b4104b87 4372 
r-cran-rstan_2.21.5-2.debian.tar.xz
 f667ee6e475753c991b279ae38121eb4fda4ddb34d74c413f414d1533a570ac4 12726 
r-cran-rstan_2.21.5-2_amd64.buildinfo
Files:
 21e9e0cc2c8fa1cd3fc9fc19ec4be536 2285 gnu-r optional r-cran-rstan_2.21.5-2.dsc
 4642f742542854add62d50d127dc19d8 4372 gnu-r optional 
r-cran-rstan_2.21.5-2.debian.tar.xz
 1f2f98615386badeda2da7ed57dc4be2 12726 gnu-r optional 
r-cran-rstan_2.21.5-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmMTxJ0SHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxwHAP/R75wToZGNQOjctPAQ6LnTgivhMHYFzt
DpHnXT8HGVnGxuowVV7F83NvEcZN6EJQmCvfqIBLm+W4/KJ6l0VW6R7d4wSqDnLk
DYajBguhMILMeQ1VlIOG7jOz/nc6yOTPIqjZc10BxxCJ0hdbyUqcLONd4OoEINFX
Jch3H0KLkkf3LL+QrXOF3bapg+KWiufA07/4NjTXofqKP0KzO6fNmboNt9Ge44g9
fren9ofa4jTBT/GP7ziUL0/SlsTMsGQMMJjB4bSR9l/hbBp/hjJg+r7Ah6uNs7WH
bMfhm73gnylEDvNijUlYetfJQQH3tA5z1jDrkCISH1TfEMF1OU2DfGC0KKE+ZZQZ
9AP/W0I4/5D1UFv8L6NNval357oQKymFLhm69mvd5C/e2bZvAC3QIPvkqenfNsxX
kqj7fIP/yhhlKLA/LzN/NYpC/c8AS17UOUz1od2QnypuwfzFUaq1sMy/5klGKDd7
/daKVYl67JvX76gC+vJh+RAtQniQoiT7K5OaPHk3n+62E1yLosKjyd6QGTvBquhW
EEUjrfmHeRQM1VGFKtWQb5xwxAS1QUI6HGvDil4OAxFIhU2rxNd8f18CUk1JKeLR
xY6hqRnHPVdQiMWuuyFCSZ27CFAsFRumn/8dXE50XGm1wysz3Sm50BsMW4b+0bh0
PG9aJA0AC+Yb
=Mpd5
-END PGP SIGNATURE End Message ---

Bug#1015224: marked as done (Illegal instruction (SIGILL) on arm64)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 21:17:08 +
with message-id 
and subject line Bug#1015224: fixed in rocksdb 6.11.4-3+deb11u1
has caused the Debian Bug report #1015224,
regarding Illegal instruction (SIGILL) on arm64
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.)


-- 
1015224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015224
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librocksdb6.11
Version: 6.11.4-3
Severity: grave
Tags: bullseye, patch

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

I got just hit by https://github.com/facebook/rocksdb/pull/7233 on my RPI 400
running Debian Bullseye. I rebuilt the librocksdb6.11 package with the patch
from
https://github.com/facebook/rocksdb/commit/29f7bbef995bdf83098963799c66af742e95373f
and I can confirm that this patch fixes the SIGILL issue.

Is there any chance to push that fix into Bullseye? Without it, librocksdb is
not working for me on my Raspberry PI.

Regards, Daniel


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

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

Versions of packages librocksdb6.11 depends on:
ii  libbz2-1.01.0.8-5
ii  libc6 2.33-8
ii  libgcc-s1 12.1.0-5
pn  libgflags2.2  
ii  liblz4-1  1.9.3-2
ii  libsnappy1v5  1.1.9-2
ii  libstdc++612.1.0-5
ii  libzstd1  1.5.2+dfsg-1
ii  zlib1g1:1.2.11.dfsg-4

librocksdb6.11 recommends no packages.

librocksdb6.11 suggests no packages.

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEIB9kcJqmmF4VguFXclr8JZgo7DMFAmLUhqkACgkQclr8JZgo
7DPsPRAAtqU9d0WaXdqYIfrjyMNnJkvcCzGTM211mRIq5tFk9PqiyRAWZqjhCwn3
7QNA4uYQbECXgd6Bgc+hP+GDoPlbwPYRe6VeNIzPc87LpAVh2BR2jG2D4tzCtG1/
hHqolpGbDsMmTyr1hSQwfZWwCZJ5uIsIk60Of3O1TD/PM2dFpSqwFb/dwKJ2B/v+
oqqaZDLOxeh87vqEmFmCxubstk9giNWtID9tMXfE8c5ot9naAViNBlHzRyj9L2PC
xJ7dPSmS4qqWouZUSOM/PaIYjmK2oFB2OVJ/w1isao0SNkQIePRMg43R8x5TGKI+
x3pUvPyBe5lekq2yVD/wigOSFF2fLh+FhM/5+Noq+c6aEIRAU16pa0iMA5SF/w9C
5l0tapF/T0RYM8zaAfZe95hqCgq4OtUwHry1OEEL/r0ngEPnLkjUwHaOVPr0PGNh
ZZhmBrpg23NR17m+4H4OksyGB3D8w8I5X2EiljKBiIXZzOVUO5ATGedZOM2nWXH7
EYCZqhbjVWCYuGZtNBuzlFaeK5bGA0UWTj+LG1LQcaAXIWLnWJQ7vKeXDiDeJ+m/
hposcBS9yR3ndCX0Wp418EvgQVYgnmCABbeH/o2PJ1JgvpFDLajUHeWOhSSU7iGu
yAvryTvY/Hc/4uXRr7V0F+YKoBCbNOVKrnS/ypZbxBHSt/p9Yu4=
=GH1z
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: rocksdb
Source-Version: 6.11.4-3+deb11u1
Done: Laszlo Boszormenyi (GCS) 

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

Debian distribution maintenance software
pp.
Laszlo Boszormenyi (GCS)  (supplier of updated rocksdb package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 27 Aug 2022 08:59:02 +0200
Source: rocksdb
Architecture: source
Version: 6.11.4-3+deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Laszlo Boszormenyi (GCS) 
Changed-By: Laszlo Boszormenyi (GCS) 
Closes: 1015224
Changes:
 rocksdb (6.11.4-3+deb11u1) bullseye; urgency=medium
 .
   [ Daniel Leidert  ]
   * Fix illegal instruction on arm64 (closes: #1015224).
Checksums-Sha1:
 1d3bc86984f55947e36eccf0cfedaa5306673cf7 2261 rocksdb_6.11.4-3+deb11u1.dsc
 06a80b639683fe2215faf0a62ce9fd7b63d0c19c 8032 
rocksdb_6.11.4-3+deb11u1.debian.tar.xz
Checksums-Sha256:
 fbbdaf6df865b0148c0e8b5452856e64030a3d38f2e716bccc454cdda0c0cb46 2261 
rocksdb_6.11.4-3+deb11u1.dsc
 8c91597759003f18097bb6be0e0698a5c377e570f75a2729316f57fe24d53a85 8032 
rocksdb_6.11.4-3+deb11u1.debian.tar.xz
Files:
 943a55fedf6761339fd308d40f2de99e 2261 database optional 
rocksdb_6.11.4-3+deb11u1.dsc
 

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 1013415 r-cran-rstantools 2.2.0-1
Bug #1013415 [src:r-cran-rstan] r-cran-rstantools: r-cran-rstan needs 
recompilation autopkgtest regression with r-cran-rcppparallel
Bug reassigned from package 'src:r-cran-rstan' to 'r-cran-rstantools'.
Ignoring request to alter found versions of bug #1013415 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1013415 to the same values 
previously set
Bug #1013415 [r-cran-rstantools] r-cran-rstantools: r-cran-rstan needs 
recompilation autopkgtest regression with r-cran-rcppparallel
Marked as found in versions r-cran-rstantools/2.2.0-1.
> thanks
Stopping processing here.

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

Bug#1017063: fixed in gjs 1.73.1-2

[Paul Gevers]

Hi Jeremy,

On Sat, 13 Aug 2022 01:48:54 + Debian FTP Masters 
 wrote:

 gjs (1.73.1-2) unstable; urgency=medium
 .
   * Rebuild against latest mozjs91 (Closes: #1017063)


You forgot to enforce this with a *versioned* build dependency and now 
armhf got build with the old version.


But anyways. This smells a bit like an ABI breakage. Did something go 
wrong with mozjs91? And maybe we want to prevent issues during partial 
upgrades, then mozjs91 should break the old version of gjs.


Normally no-change rebuilds are handled as binNMU's by the Release Team, 
is there any particular reason why you didn't do that?


Paul


OpenPGP_signature
Description: OpenPGP digital signature

Processed: reassign

[Debian Bug Tracking System]

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

> reassign 1012144 r-cran-rstan 2.21.5-1
Bug #1012144 [src:r-cran-shinystan] r-cran-shinystan: FTBFS with 
onetbb/2021.5.0-8 in experimental
Bug reassigned from package 'src:r-cran-shinystan' to 'r-cran-rstan'.
No longer marked as found in versions r-cran-shinystan/2.6.0-1.
Ignoring request to alter fixed versions of bug #1012144 to the same values 
previously set
Bug #1012144 [r-cran-rstan] r-cran-shinystan: FTBFS with onetbb/2021.5.0-8 in 
experimental
Marked as found in versions r-cran-rstan/2.21.5-1.
> reassign 1011218 r-cran-rstan 2.21.5-1
Bug #1011218 [src:r-cran-brms] r-cran-brms: FTBFS with onetbb/2021.5.0-8 in 
experimental
Bug reassigned from package 'src:r-cran-brms' to 'r-cran-rstan'.
No longer marked as found in versions r-cran-brms/2.17.0-1.
Ignoring request to alter fixed versions of bug #1011218 to the same values 
previously set
Bug #1011218 [r-cran-rstan] r-cran-brms: FTBFS with onetbb/2021.5.0-8 in 
experimental
Marked as found in versions r-cran-rstan/2.21.5-1.
> thanks
Stopping processing here.

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

Processed: currently FTBFS

[Debian Bug Tracking System]

Processing control commands:

> severity 1010578 serious
Bug #1010578 [osmo-mgw] osmo-mgw: FTBFS if systemd is in build environment
Severity set to 'serious' from 'normal'

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

Bug#1012219: Please adjust StanHeaders to new version of (one)tbb

[Nilesh Patra]

Hi all,

On 9/3/22 22:06, Benjamin K Goodrich wrote:

Sorry for the late reply. I am told that StanHeaders can be built
successfully with oneTBB by setting environmental variables like
TBB_INC and TBB_LIB. On CRAN, we would like to use the version of TBB
that comes with the RcppParallel package
[...]


Thanks for the pointers, but
we are able to build cppparallel and stanheaders without problems as is. But 
the built package is
unusable as it uses "#include" statements that try to include files available 
in older tbb but
not in new onetbb, as observed in rstan compilation.

The problematic #include statment (and corresponding removed APIs) seems to be 
stemming from
"inst/include/stan/math/prim/core/init_threadpool_tbb.hpp"

On taking a deeper look, I observed that this is directly embedded from 
stan/math[1]
The current release of stanheaders contains an older copy of the math lib.
Going fwd, a patch had been added to stan/math to make it compatible with 
onetbb[2]
On cherry-picking a couple of changes from there, I am able to get rstan to 
compile.

I am not very sure if everything is good/works as expected (autopkgtests / CRAN 
tests seem
to pass, so that's a good indication), but I'd be thrilled to believe so.

[1]: https://github.com/stan-dev/math
[2]: 
https://github.com/stan-dev/math/commit/6f94b2a70d11276a53e5b5bc4100d3ffa524b96c

--
Best,
Nilesh


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1018971: poppler: diff for NMU version 22.08.0-2.1

[Salvatore Bonaccorso]

Control: tags 1018971 + patch
Control: tags 1018971 + pending

Dear maintainer,

I've prepared an NMU for poppler (versioned as 22.08.0-2.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should delay it longer.

Regards,
Salvatore
diff -Nru poppler-22.08.0/debian/changelog poppler-22.08.0/debian/changelog
--- poppler-22.08.0/debian/changelog	2022-08-21 19:13:33.0 +0200
+++ poppler-22.08.0/debian/changelog	2022-09-03 21:30:51.0 +0200
@@ -1,3 +1,10 @@
+poppler (22.08.0-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * JBIG2Stream: Fix crash on broken file (CVE-2022-38784) (Closes: #1018971)
+
+ -- Salvatore Bonaccorso   Sat, 03 Sep 2022 21:30:51 +0200
+
 poppler (22.08.0-2) unstable; urgency=medium
 
   * Team upload
diff -Nru poppler-22.08.0/debian/patches/JBIG2Stream-Fix-crash-on-broken-file.patch poppler-22.08.0/debian/patches/JBIG2Stream-Fix-crash-on-broken-file.patch
--- poppler-22.08.0/debian/patches/JBIG2Stream-Fix-crash-on-broken-file.patch	1970-01-01 01:00:00.0 +0100
+++ poppler-22.08.0/debian/patches/JBIG2Stream-Fix-crash-on-broken-file.patch	2022-09-03 21:29:13.0 +0200
@@ -0,0 +1,34 @@
+From: Albert Astals Cid 
+Date: Thu, 25 Aug 2022 00:14:22 +0200
+Subject: JBIG2Stream: Fix crash on broken file
+Origin: https://gitlab.freedesktop.org/poppler/poppler/-/commit/27354e9d9696ee2bc063910a6c9a6b27c5184a52
+Bug-Debian: https://bugs.debian.org/1018971
+Bug-Debian-Security: https://security-tracker.debian.org/tracker/CVE-2022-38784
+
+https://github.com/jeffssh/CVE-2021-30860
+
+Thanks to David Warren for the heads up
+---
+ poppler/JBIG2Stream.cc | 6 +-
+ 1 file changed, 5 insertions(+), 1 deletion(-)
+
+diff --git a/poppler/JBIG2Stream.cc b/poppler/JBIG2Stream.cc
+index 662276e547eb..9f70431de49e 100644
+--- a/poppler/JBIG2Stream.cc
 b/poppler/JBIG2Stream.cc
+@@ -1976,7 +1976,11 @@ void JBIG2Stream::readTextRegionSeg(unsigned int segNum, bool imm, bool lossless
+ for (i = 0; i < nRefSegs; ++i) {
+ if ((seg = findSegment(refSegs[i]))) {
+ if (seg->getType() == jbig2SegSymbolDict) {
+-numSyms += ((JBIG2SymbolDict *)seg)->getSize();
++const unsigned int segSize = ((JBIG2SymbolDict *)seg)->getSize();
++if (unlikely(checkedAdd(numSyms, segSize, ))) {
++error(errSyntaxError, getPos(), "Too many symbols in JBIG2 text region");
++return;
++}
+ } else if (seg->getType() == jbig2SegCodeTable) {
+ codeTables.push_back(seg);
+ }
+-- 
+2.37.2
+
diff -Nru poppler-22.08.0/debian/patches/series poppler-22.08.0/debian/patches/series
--- poppler-22.08.0/debian/patches/series	2022-08-21 19:13:33.0 +0200
+++ poppler-22.08.0/debian/patches/series	2022-09-03 21:29:22.0 +0200
@@ -1 +1,2 @@
 segfault-on-unset-catalog.patch
+JBIG2Stream-Fix-crash-on-broken-file.patch

Processed: poppler: diff for NMU version 22.08.0-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1018971 + patch
Bug #1018971 [src:poppler] poppler: CVE-2022-38784
Added tag(s) patch.
> tags 1018971 + pending
Bug #1018971 [src:poppler] poppler: CVE-2022-38784
Added tag(s) pending.

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

Bug#1019044: marked as done (librust-once-cell-dev: impossible to satisfy dependency on librust-parking-lot-core-0.8-dev)

[Debian Bug Tracking System]

Your message dated Sat, 3 Sep 2022 20:40:47 +0100
with message-id <05750882-de1f-757a-6810-4173bf599...@debian.org>
and subject line re: librust-once-cell-dev: impossible to satidfy dependency on 
librust-parking-lot-core-0.8-dev
has caused the Debian Bug report #1019044,
regarding librust-once-cell-dev: impossible to satisfy dependency on 
librust-parking-lot-core-0.8-dev
to be marked as done.

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

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


-- 
1019044: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019044
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: librust-once-cell-dev
Version: 1.12.0-2
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMTJ/kACgkQLHwxRsGg
ASH7NRAAlDk2BN7/TqeH4DBzhYojHpf9JGnaYcfB1jpL8Vr7s/eo27zzSAJuNHux
sUGhDavQD8zPz84ax4a9yjNeL0er+61K1TJ/V00KmIJWQOrdisn2aauvN9TuA40s
3U1BoopG6Ro349J0sLJQl/xIdc3uogAjnIQkZibu6qwymPXnpF8aSsfVSipRzBMt
BivRx3qCo03QZm0twN5pzf7UNflPh4OZdRXAMidQs/NQxe55BUzme/wlQKlXEGyr
CZd3F3LJouv59v7/hhKgm4kv9uNdVt+9eC9jcU4kFwuoYt3RdOsBsunFhtWUp388
pon9ZAz95bdjFcPApSrTjnN5qSQTJeRH+EL2T/US4lJRRljGt1wwfE7nGeQPeOdC
lBseXdNkG2eUBTgP3D+z56baqZ7mQqCMiW91XmKGkPpArdqV+Q/PqSSQ6CMdwAGH
74qtgo2v9ZV4rryAA4uOQwU8dnaf9ygl+hskb+2NlQjTjVwilOS4Il1jfRX5jlam
L9h1zuxNSxzmtwIqqjWmCK8HyjYBuINuREVceIHlGUnd3NtrfVobVkooLFBa/xAd
tmn/MqFbAAjP7Ftzayjmum8NRhdsnNTh0+ewBQcQECMq3orl0vm3j7hHUhmYw9aU
SPdP3FybeOIQJGUp4+S18JmNwNYULfuHC200aYZfpWpADgaSfEw=
=wXfh
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---

Version: 1.14.0-1

Fixed in 1.14.0-1--- End Message ---

Processed: found 1018971 in 20.09.0-3.1

[Debian Bug Tracking System]

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

> found 1018971 20.09.0-3.1
Bug #1018971 [src:poppler] poppler: CVE-2022-38784
Marked as found in versions poppler/20.09.0-3.1.
> thanks
Stopping processing here.

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

Bug#1019099: rust-ahash - autopkgtest failure

[Peter Michael Green]

Package: rust-ahash
Version: 0.7.6-4
Severity: serious

The autopkgtest of rust-ahash is failing

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


Testing aeshash/u8
thread 'main' panicked at 'aes must be enabled', tests/bench.rs:20:5
stack backtrace:
0: std::panicking::begin_panic
  at /usr/src/rustc-1.59.0/library/std/src/panicking.rs:525:12
1: ahash::aeshash
  at ./tests/bench.rs:20:5
2: ahash::bench_ahash::{{closure}}::{{closure}}
  at ./tests/bench.rs:92:81
3: criterion::bencher::Bencher::iter
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/bencher.rs:88:23
4: ahash::bench_ahash::{{closure}}
  at ./tests/bench.rs:89:54
5:  as 
criterion::routine::Routine>::bench::{{closure}}
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/routine.rs:209:17
6: core::iter::adapters::map::map_fold::{{closure}}
  at 
/usr/src/rustc-1.59.0/library/core/src/iter/adapters/map.rs:84:28
7: core::iter::traits::iterator::Iterator::fold
  at 
/usr/src/rustc-1.59.0/library/core/src/iter/traits/iterator.rs:2171:21
8:  as 
core::iter::traits::iterator::Iterator>::fold
  at 
/usr/src/rustc-1.59.0/library/core/src/iter/adapters/map.rs:124:9
9: core::iter::traits::iterator::Iterator::for_each
  at 
/usr/src/rustc-1.59.0/library/core/src/iter/traits/iterator.rs:736:9
   10:  as 
alloc::vec::spec_extend::SpecExtend>::spec_extend
  at 
/usr/src/rustc-1.59.0/library/alloc/src/vec/spec_extend.rs:40:17
   11:  as 
alloc::vec::spec_from_iter_nested::SpecFromIterNested>::from_iter
  at 
/usr/src/rustc-1.59.0/library/alloc/src/vec/spec_from_iter_nested.rs:56:9
   12:  as 
alloc::vec::spec_from_iter::SpecFromIter>::from_iter
  at 
/usr/src/rustc-1.59.0/library/alloc/src/vec/spec_from_iter.rs:33:9
   13:  as 
core::iter::traits::collect::FromIterator>::from_iter
  at /usr/src/rustc-1.59.0/library/alloc/src/vec/mod.rs:2541:9
   14: core::iter::traits::iterator::Iterator::collect
  at 
/usr/src/rustc-1.59.0/library/core/src/iter/traits/iterator.rs:1745:9
   15:  as 
criterion::routine::Routine>::bench
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/routine.rs:205:9
   16: criterion::routine::Routine::test
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/routine.rs:18:9
   17: criterion::benchmark_group::BenchmarkGroup::run_bench
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/benchmark_group.rs:339:21
   18: criterion::benchmark_group::BenchmarkGroup::bench_with_input
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/benchmark_group.rs:269:9
   19: ahash::bench_ahash
  at ./tests/bench.rs:87:5
   20: ahash::benches
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/macros.rs:71:17
   21: ahash::main
  at 
/tmp/tmp.wNUW0kfuKe/registry/criterion-0.3.5/src/macros.rs:127:17
   22: core::ops::function::FnOnce::call_once
  at /usr/src/rustc-1.59.0/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose 
backtrace.

error: test failed, to rerun pass '--bench ahash'
autopkgtest [16:38:41]: test 
librust-ahash+compile-time-rng-dev:compile-time-rng: ---]
autopkgtest [16:38:41]: test 
librust-ahash+compile-time-rng-dev:compile-time-rng:  - - - - - - - - - - 
results - - - - - - - - - -
librust-ahash+compile-time-rng-dev:compile-time-rng FAIL non-zero exit status 
101
autopkgtest [16:38:41]:  summary
rust-ahash:@ FAIL non-zero exit status 101
librust-ahash-dev:default FAIL non-zero exit status 101
librust-ahash-dev:std FAIL non-zero exit status 101
librust-ahash-dev:   FAIL non-zero exit status 101
librust-ahash+compile-time-rng-dev:compile-time-rng FAIL non-zero exit status 
101


Thanks to an annoyance with the way testing migration autopkgtests 
interact with skip-not-installable this is blocking the migration of the 
new version of rust-once-cell to testing. So we would appreciate a quick 
fix.

Bug#1019098: src:tbb: do not migrate. this source is deprecated in favor of src:onetbb

[M. Zhou]

Source: tbb
Version: 2020.3-2.1
Severity: serious

src:tbb: do not migrate. this source is deprecated in favor of
src:onetbb. The RM bug of src:tbb is filed at
https://bugs.debian.org/1014990

Processed: Re: Bug#1006818: eye: (autopkgtest) failure on non-amd64

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 swi-prolog-core
Bug #1006818 [eye] eye fails to work on !amd64
Bug reassigned from package 'eye' to 'swi-prolog-core'.
No longer marked as found in versions eye/19.0221.2026~ds-1.
Ignoring request to alter fixed versions of bug #1006818 to the same values 
previously set
> retitle -1 intermediary files embed arch-specific path
Bug #1006818 [swi-prolog-core] eye fails to work on !amd64
Changed Bug title to 'intermediary files embed arch-specific path' from 'eye 
fails to work on !amd64'.
> affects -1 eye
Bug #1006818 [swi-prolog-core] intermediary files embed arch-specific path
Added indication that 1006818 affects eye

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

Bug#1006818: eye: (autopkgtest) failure on non-amd64

[Jonas Smedegaard]

Control: reassign -1 swi-prolog-core
Control: retitle -1 intermediary files embed arch-specific path
Control: affects -1 eye

Quoting Adrian Bunk (2022-08-20 23:16:06)
> On Sat, Mar 05, 2022 at 08:41:47PM +0100, Paul Gevers wrote:
> > Source: eye
> > Version: 19.0221.2026~ds-1
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: fails-always
> > 
> > Dear maintainer(s),
> > 
> > You package has an autopkgtest, great. However, it fails on all
> > architectures but amd64. Can you please investigate the situation and fix
> > it?
> >...
> > #   Failed test 'bare command, stderr'
> > #   at debian/tests/eye.pvm.t line 11.
> > #   '/usr/bin/eye.pvm: 3: exec:
> > /usr/lib/swi-prolog/bin/x86_64-linux/swipl: not found
> >...
> 
> The autopkgtest caught that the package is not functional on !amd64:
> 
> (buster_arm64-dchroot)bunk@amdahl:/tmp$ eye.pvm 
> /usr/bin/eye.pvm: 3: exec: /usr/lib/swi-prolog/bin/x86_64-linux/swipl: not 
> found
> (buster_arm64-dchroot)bunk@amdahl:/tmp$ 
> 
> Changing Architecture: from "all" to "any" might be a reasonable option.

In my understanding, this is a bug in SWI Prolog, in that when
generating a so-called "intermediate code file" it embeds an
arch-specific path to the interpreter instead of the arch-independent
symlink in PATH: /usr/bin/swipl

@Lev: What do you think?  Is it possible to patch SWI Prolog to embed an
architecture-agnostic path for executing intermediary files?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

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

signature.asc
Description: signature

Bug#1019095: promod3 FTBFS with multiarchified openstructure

[Adrian Bunk]

Source: promod3
Version: 3.2.1+ds-4
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=promod3=amd64=3.2.1%2Bds-4%2Bb1=1662229682=0

...
CMake Error at cmake_support/FindOPENSTRUCTURE.cmake:37 (message):
  Could not find library ost_io.  Please specify the location of your
  OpenStructure installation with OST_ROOT
Call Stack (most recent call first):
  cmake_support/FindOPENSTRUCTURE.cmake:98 (find_OPENSTRUCTURE)
  CMakeLists.txt:106 (find_package)


-- Configuring incomplete, errors occurred!

Bug#1018732: marked as done (mir-core: FTBFS: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmpq8z68wht.d -Wl,-z,relro -O -g -release -wi`)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id 
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding mir-core: FTBFS: ERROR: Unable to detect linker for compiler `ldc2 
-L=--version /tmp/tmpq8z68wht.d -Wl,-z,relro -O -g -release -wi`
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.)


-- 
1017087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mir-core
Version: 1.1.111-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: sramac...@debian.org

https://buildd.debian.org/status/fetch.php?pkg=mir-core=arm64=1.1.111-1=1661205784=0

Source dir: /<>
Build dir: /<>/obj-aarch64-linux-gnu
Build type: native build
Project name: mir-core
Project version: 1.1.1

../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 
-L=--version /tmp/tmpq8z68wht.d -Wl,-z,relro -O -g -release -wi`
stdout: 
stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 --help'
ldc2: Did you mean '--icp-lto'?


A full log can be found at 
/<>/obj-aarch64-linux-gnu/meson-logs/meson-log.txt
cd obj-aarch64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
==> meson-logs/meson-log.txt <==
Build started at 2022-08-22T22:02:57.759199
Main binary: /usr/bin/python3
Build Options: -Dprefix=/usr -Dlibdir=lib/aarch64-linux-gnu 
-Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain -Ddefault_library=both 
-Dwrap_mode=nodownload
Python system: Linux
The Meson build system
Version: 0.63.1
Source dir: /<>
Build dir: /<>/obj-aarch64-linux-gnu
Build type: native build
Project name: mir-core
Project version: 1.1.1
-
Detecting compiler via: cc --version
compiler returned 
compiler stdout:
cc (Debian 12.1.0-8) 12.1.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


compiler stderr:

Running command: cc -E -dM -
-
Detecting linker via: cc -Wl,--version -Wl,-z,relro -g -O2 
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
linker returned 
linker stdout:
GNU ld (GNU Binutils for Debian) 2.38.90.20220713
Copyright (C) 2022 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.

linker stderr:
collect2 version 12.1.0
/usr/bin/ld -plugin /usr/lib/gcc/aarch64-linux-gnu/12/liblto_plugin.so 
-plugin-opt=/usr/lib/gcc/aarch64-linux-gnu/12/lto-wrapper 
-plugin-opt=-fresolution=/tmp/cchsFxXu.res -plugin-opt=-pass-through=-lgcc 
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
--eh-frame-hdr --hash-style=gnu --as-needed -dynamic-linker 
/lib/ld-linux-aarch64.so.1 -X -EL -maarch64linux --fix-cortex-a53-843419 -pie 
/usr/lib/gcc/aarch64-linux-gnu/12/../../../aarch64-linux-gnu/Scrt1.o 
/usr/lib/gcc/aarch64-linux-gnu/12/../../../aarch64-linux-gnu/crti.o 
/usr/lib/gcc/aarch64-linux-gnu/12/crtbeginS.o 
-L/usr/lib/gcc/aarch64-linux-gnu/12 
-L/usr/lib/gcc/aarch64-linux-gnu/12/../../../aarch64-linux-gnu 
-L/usr/lib/gcc/aarch64-linux-gnu/12/../../../../lib -L/lib/aarch64-linux-gnu 
-L/lib/../lib -L/usr/lib/aarch64-linux-gnu -L/usr/lib/../lib 
-L/usr/lib/gcc/aarch64-linux-gnu/12/../../.. --version -z relro -lgcc 
--push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed 
-lgcc_s --pop-state /usr/lib/gcc/aarch64-linux-gnu/12/crtendS.o 
/usr/lib/gcc/aarch64-linux-gnu/12/../../../aarch64-linux-gnu/crtn.o

-
Detecting linker via: ldc2 -L=--version /tmp/tmpq8z68wht.d -Wl,-z,relro -O -g 
-release -wi
linker returned 
linker stdout:

linker stderr:
ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 --help'
ldc2: Did you mean '--icp-lto'?


../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 
-L=--version /tmp/tmpq8z68wht.d -Wl,-z,relro -O -g -release -wi`
stdout: 
stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 --help'
ldc2: Did you mean '--icp-lto'?

dh_auto_configure: error: cd obj-aarch64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/aarch64-linux-gnu 

Bug#1017303: marked as done (stdx-allocator: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmpa3ats9za.d -Wl,-z,relro -O -g -release -wi`)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id 
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding stdx-allocator: FTBFS: ../meson.build:1:0: ERROR: Unable to detect 
linker for compiler `ldc2 -L=--version /tmp/tmpa3ats9za.d -Wl,-z,relro -O -g 
-release -wi`
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.)


-- 
1017087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: stdx-allocator
Version: 3.1.0~beta.2-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: stdx-allocator
> Project version: 3.0.1
> 
> ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 
> -L=--version /tmp/tmpa3ats9za.d -Wl,-z,relro -O -g -release -wi`
> stdout: 
> stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 
> --help'
> ldc2: Did you mean '--icp-lto'?
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-08-14T03:15:33.240383
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: stdx-allocator
> Project version: 3.0.1
> -
> Detecting compiler via: cc --version
> compiler returned 
> compiler stdout:
> cc (Debian 12.1.0-8) 12.1.0
> Copyright (C) 2022 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> compiler stderr:
> 
> Running command: cc -E -dM -
> -
> Detecting linker via: cc -Wl,--version -Wl,-z,relro -g -O2 
> '-ffile-prefix-map=/<>=.' -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> linker returned  '-Wl,-z,relro', '-g', '-...>
> linker stdout:
> GNU ld (GNU Binutils for Debian) 2.38.90.20220713
> Copyright (C) 2022 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later version.
> This program has absolutely no warranty.
> 
> linker stderr:
> collect2 version 12.1.0
> /usr/bin/ld -plugin /usr/lib/gcc/x86_64-linux-gnu/12/liblto_plugin.so 
> -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper 
> -plugin-opt=-fresolution=/tmp/ccmn9Lmu.res -plugin-opt=-pass-through=-lgcc 
> -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
> -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
> --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker 
> /lib64/ld-linux-x86-64.so.2 -pie 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o 
> -L/usr/lib/gcc/x86_64-linux-gnu/12 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../.. --version -z relro -lgcc 
> --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state 
> --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/12/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crtn.o
> 
> -
> Detecting linker via: ldc2 -L=--version /tmp/tmpa3ats9za.d -Wl,-z,relro -O -g 
> -release -wi
> linker returned  '/tmp/tmpa3ats9za.d', '...>
> linker stdout:
> 
> linker stderr:
> ldc2: Unknown command line 

Bug#1017296: marked as done (mir-core: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp22xmb4p4.d -Wl,-z,relro -O -g -release -wi`)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id 
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding mir-core: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker 
for compiler `ldc2 -L=--version /tmp/tmp22xmb4p4.d -Wl,-z,relro -O -g -release 
-wi`
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.)


-- 
1017087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mir-core
Version: 1.0.2-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: mir-core
> Project version: 0.3.0
> 
> ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 
> -L=--version /tmp/tmp22xmb4p4.d -Wl,-z,relro -O -g -release -wi`
> stdout: 
> stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 
> --help'
> ldc2: Did you mean '--icp-lto'?
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-08-14T03:16:31.991137
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: mir-core
> Project version: 0.3.0
> -
> Detecting compiler via: cc --version
> compiler returned 
> compiler stdout:
> cc (Debian 12.1.0-8) 12.1.0
> Copyright (C) 2022 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> compiler stderr:
> 
> Running command: cc -E -dM -
> -
> Detecting linker via: cc -Wl,--version -Wl,-z,relro -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> linker returned  '-Wl,-z,relro', '-g', '-...>
> linker stdout:
> GNU ld (GNU Binutils for Debian) 2.38.90.20220713
> Copyright (C) 2022 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later version.
> This program has absolutely no warranty.
> 
> linker stderr:
> collect2 version 12.1.0
> /usr/bin/ld -plugin /usr/lib/gcc/x86_64-linux-gnu/12/liblto_plugin.so 
> -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper 
> -plugin-opt=-fresolution=/tmp/cc17g6Rt.res -plugin-opt=-pass-through=-lgcc 
> -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
> -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
> --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker 
> /lib64/ld-linux-x86-64.so.2 -pie 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o 
> -L/usr/lib/gcc/x86_64-linux-gnu/12 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../.. --version -z relro -lgcc 
> --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state 
> --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/12/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crtn.o
> 
> -
> Detecting linker via: ldc2 -L=--version /tmp/tmp22xmb4p4.d -Wl,-z,relro -O -g 
> -release -wi
> linker returned  '/tmp/tmp22xmb4p4.d', '...>
> linker stdout:
> 
> linker stderr:
> ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 

Bug#1017273: marked as done (mustache-d: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp0m23tkec.d -Wl,-z,relro -O -g -release -wi`)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id 
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding mustache-d: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker 
for compiler `ldc2 -L=--version /tmp/tmp0m23tkec.d -Wl,-z,relro -O -g -release 
-wi`
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.)


-- 
1017087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: mustache-d
Version: 0.1.4-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: mustache-d
> Project version: 0.1.4
> 
> ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 
> -L=--version /tmp/tmp0m23tkec.d -Wl,-z,relro -O -g -release -wi`
> stdout: 
> stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 
> --help'
> ldc2: Did you mean '--icp-lto'?
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-08-14T03:10:43.668679
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: mustache-d
> Project version: 0.1.4
> -
> Detecting compiler via: cc --version
> compiler returned 
> compiler stdout:
> cc (Debian 12.1.0-8) 12.1.0
> Copyright (C) 2022 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> compiler stderr:
> 
> Running command: cc -E -dM -
> -
> Detecting linker via: cc -Wl,--version -Wl,-z,relro -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> linker returned  '-Wl,-z,relro', '-g', '-...>
> linker stdout:
> GNU ld (GNU Binutils for Debian) 2.38.90.20220713
> Copyright (C) 2022 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later version.
> This program has absolutely no warranty.
> 
> linker stderr:
> collect2 version 12.1.0
> /usr/bin/ld -plugin /usr/lib/gcc/x86_64-linux-gnu/12/liblto_plugin.so 
> -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper 
> -plugin-opt=-fresolution=/tmp/cc7h5ykC.res -plugin-opt=-pass-through=-lgcc 
> -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
> -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
> --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker 
> /lib64/ld-linux-x86-64.so.2 -pie 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o 
> -L/usr/lib/gcc/x86_64-linux-gnu/12 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../.. --version -z relro -lgcc 
> --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state 
> --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/12/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crtn.o
> 
> -
> Detecting linker via: ldc2 -L=--version /tmp/tmp0m23tkec.d -Wl,-z,relro -O -g 
> -release -wi
> linker returned  '/tmp/tmp0m23tkec.d', '...>
> linker stdout:
> 
> linker stderr:
> ldc2: Unknown command line argument '-Wl,-z,relro'.  

Bug#1017243: marked as done (gir-to-d: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp7wgoqpvv.d -Wl,-z,relro -O -g -release -wi --allinst`)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id 
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding gir-to-d: FTBFS: ../meson.build:1:0: ERROR: Unable to detect linker 
for compiler `ldc2 -L=--version /tmp/tmp7wgoqpvv.d -Wl,-z,relro -O -g -release 
-wi --allinst`
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.)


-- 
1017087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gir-to-d
Version: 0.22.0-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary --buildsystem=meson
>dh_update_autotools_config -O--buildsystem=meson
>dh_autoreconf -O--buildsystem=meson
>dh_auto_configure -O--buildsystem=meson
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: GIR-to-D
> Project version: 0.19.1
> 
> ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 
> -L=--version /tmp/tmp7wgoqpvv.d -Wl,-z,relro -O -g -release -wi --allinst`
> stdout: 
> stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 
> --help'
> ldc2: Did you mean '--icp-lto'?
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-08-14T02:41:50.667299
> Main binary: /usr/bin/python3
> Build Options: -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: GIR-to-D
> Project version: 0.19.1
> -
> Detecting compiler via: cc --version
> compiler returned 
> compiler stdout:
> cc (Debian 12.1.0-8) 12.1.0
> Copyright (C) 2022 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> compiler stderr:
> 
> Running command: cc -E -dM -
> -
> Detecting linker via: cc -Wl,--version -Wl,-z,relro -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> linker returned  '-Wl,-z,relro', '-g', '-...>
> linker stdout:
> GNU ld (GNU Binutils for Debian) 2.38.90.20220713
> Copyright (C) 2022 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later version.
> This program has absolutely no warranty.
> 
> linker stderr:
> collect2 version 12.1.0
> /usr/bin/ld -plugin /usr/lib/gcc/x86_64-linux-gnu/12/liblto_plugin.so 
> -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper 
> -plugin-opt=-fresolution=/tmp/ccjcrOLo.res -plugin-opt=-pass-through=-lgcc 
> -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
> -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
> --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker 
> /lib64/ld-linux-x86-64.so.2 -pie 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o 
> -L/usr/lib/gcc/x86_64-linux-gnu/12 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib -L/lib/x86_64-linux-gnu 
> -L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../.. --version -z relro -lgcc 
> --push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state 
> --as-needed -lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/12/crtendS.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crtn.o
> 
> -
> Detecting linker via: ldc2 -L=--version /tmp/tmp7wgoqpvv.d -Wl,-z,relro -O -g 
> -release -wi --allinst
> linker returned  

Bug#1017237: marked as done (sambamba: FTBFS: ../meson.build:9:0: ERROR: Unable to detect linker for compiler `ldc2 -L=--version /tmp/tmp1izbdod0.d -Wl,-z,relro -O -g -release -wi`)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id 
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding sambamba: FTBFS: ../meson.build:9:0: ERROR: Unable to detect linker 
for compiler `ldc2 -L=--version /tmp/tmp1izbdod0.d -Wl,-z,relro -O -g -release 
-wi`
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.)


-- 
1017087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sambamba
Version: 0.8.2+dfsg-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_configure -- -Doptimize_strong=true -Dcpp_link_args="-wi -L=-z 
> -L=relro /usr/lib/x86_64-linux-gnu/libhts.a -L=-lz -L=-lcrypto -L=-lcurl 
> -L=-llzma -L=-lbz2 -L=-ldeflate -L=-llz4"
>   cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
> --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
> --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Doptimize_strong=true 
> "-Dcpp_link_args=-wi -L=-z -L=relro /usr/lib/x86_64-linux-gnu/libhts.a -L=-lz 
> -L=-lcrypto -L=-lcurl -L=-llzma -L=-lbz2 -L=-ldeflate -L=-llz4"
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: Sambamba
> Project version: 0.8.2
> C compiler for the host machine: cc (gcc 12.1.0 "cc (Debian 12.1.0-8) 12.1.0")
> C linker for the host machine: cc ld.bfd 2.38.90.20220713
> 
> ../meson.build:9:0: ERROR: Unable to detect linker for compiler `ldc2 
> -L=--version /tmp/tmp1izbdod0.d -Wl,-z,relro -O -g -release -wi`
> stdout: 
> stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 
> --help'
> ldc2: Did you mean '--icp-lto'?
> 
> 
> A full log can be found at 
> /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt
>   cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt
> ==> meson-logs/meson-log.txt <==
> Build started at 2022-08-14T03:13:25.149842
> Main binary: /usr/bin/python3
> Build Options: -Doptimize_strong=true '-Dcpp_link_args=-wi -L=-z -L=relro 
> /usr/lib/x86_64-linux-gnu/libhts.a -L=-lz -L=-lcrypto -L=-lcurl -L=-llzma 
> -L=-lbz2 -L=-ldeflate -L=-llz4' -Dprefix=/usr -Dlibdir=lib/x86_64-linux-gnu 
> -Dlocalstatedir=/var -Dsysconfdir=/etc -Dbuildtype=plain 
> -Dwrap_mode=nodownload
> Python system: Linux
> The Meson build system
> Version: 0.63.1
> Source dir: /<>
> Build dir: /<>/obj-x86_64-linux-gnu
> Build type: native build
> Project name: Sambamba
> Project version: 0.8.2
> -
> Detecting compiler via: cc --version
> compiler returned 
> compiler stdout:
> cc (Debian 12.1.0-8) 12.1.0
> Copyright (C) 2022 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
> 
> 
> compiler stderr:
> 
> Running command: cc -E -dM -
> -
> Detecting linker via: cc -Wl,--version -Wl,-z,relro -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2
> linker returned  '-Wl,-z,relro', '-g', '-...>
> linker stdout:
> GNU ld (GNU Binutils for Debian) 2.38.90.20220713
> Copyright (C) 2022 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later version.
> This program has absolutely no warranty.
> 
> linker stderr:
> collect2 version 12.1.0
> /usr/bin/ld -plugin /usr/lib/gcc/x86_64-linux-gnu/12/liblto_plugin.so 
> -plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/12/lto-wrapper 
> -plugin-opt=-fresolution=/tmp/ccdOa83Q.res -plugin-opt=-pass-through=-lgcc 
> -plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc 
> -plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --build-id 
> --eh-frame-hdr -m elf_x86_64 --hash-style=gnu --as-needed -dynamic-linker 
> /lib64/ld-linux-x86-64.so.2 -pie 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/crti.o 
> /usr/lib/gcc/x86_64-linux-gnu/12/crtbeginS.o 
> -L/usr/lib/gcc/x86_64-linux-gnu/12 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu 
> -L/usr/lib/gcc/x86_64-linux-gnu/12/../../../../lib -L/lib/x86_64-linux-gnu 

Bug#1017087: marked as done (meson: All ldc related packages FTBFS with 0.63.1-1)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 19:05:08 +
with message-id 
and subject line Bug#1017087: fixed in meson 0.63.2-1
has caused the Debian Bug report #1017087,
regarding meson: All ldc related packages FTBFS with 0.63.1-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.)


-- 
1017087: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017087
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: meson
Version: 0.63.1-1
Severity: serious
X-Debbugs-Cc: jpakk...@gmail.com

Hi,

On building any d-lang package (which uses ldc in build) with new meson, it
goes FTBFS with errors similar to the one pasted below.
This was working fine just minutes before (with meson 0.63.0)

Tried with packages: gir-to-d, diet-ng, sambamba

Seems meson is enforcing some flags?

| cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. 
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc 
--localstatedir=/var --libdir=lib/x86_64-linux-gnu
| The Meson build system
| Version: 0.63.1
| Source dir: /<>
| Build dir: /<>/obj-x86_64-linux-gnu
| Build type: native build
| Project name: GIR-to-D
| Project version: 0.19.1
| 
| ../meson.build:1:0: ERROR: Unable to detect linker for compiler `ldc2 
-L=--version /tmp/tmp9o4k_f0e.d -Wl,-z,relro -O -g -release -wi --allinst`
| stdout: 
| stderr: ldc2: Unknown command line argument '-Wl,-z,relro'.  Try: 'ldc2 
--help'
| ldc2: Did you mean '--icp-lto'?

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

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

Versions of packages meson depends on:
pn  ninja-build
ii  python33.10.5-3
ii  python3-pkg-resources  59.6.0-1.2
ii  python3-setuptools 59.6.0-1.2

Versions of packages meson recommends:
ii  dpkg-dev  1.21.9

meson suggests no packages.
--- End Message ---
--- Begin Message ---
Source: meson
Source-Version: 0.63.2-1
Done: Jussi Pakkanen 

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

Debian distribution maintenance software
pp.
Jussi Pakkanen  (supplier of updated meson package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sat, 03 Sep 2022 19:33:44 +0300
Source: meson
Architecture: source
Version: 0.63.2-1
Distribution: unstable
Urgency: medium
Maintainer: Jussi Pakkanen 
Changed-By: Jussi Pakkanen 
Closes: 1017087
Changes:
 meson (0.63.2-1) unstable; urgency=medium
 .
   * New upstream release. Closes: #1017087.
Checksums-Sha1:
 cce29220098483cd01c6160644bdfa6625036268 3483 meson_0.63.2-1.dsc
 575aafbf84f97039e786db3e0672c801590b6b97 2063397 meson_0.63.2.orig.tar.gz
 1188c98e5367c957022187f3b62bef6d963eb0cc 14804 meson_0.63.2-1.debian.tar.xz
 0655ee97be05e269bf9983aff451c888109324d1 34940 meson_0.63.2-1_source.buildinfo
Checksums-Sha256:
 6da861160d8d698696d3ea57c3b05c07afd854e8e1a39c44a58fd0dd21fae35d 3483 
meson_0.63.2-1.dsc
 16222f17ef76be0542c91c07994f9676ae879f46fc21c0c786a21ef2cb518bbf 2063397 
meson_0.63.2.orig.tar.gz
 83f16c4244caf12f22fd3429eb55f6f53f9608827c6f014ef55693d45cd02081 14804 
meson_0.63.2-1.debian.tar.xz
 ef5472540338eb735ae5625d066148df3da2138317b66032811c2ae7931b35ca 34940 
meson_0.63.2-1_source.buildinfo
Files:
 6331e360e947490044f060eaa1d5425e 3483 devel optional meson_0.63.2-1.dsc
 12ae3150982645790a4f8a8e8795173c 2063397 devel optional 
meson_0.63.2.orig.tar.gz
 cc99da8d8214f53d5b64dbef4948e0fc 14804 devel optional 
meson_0.63.2-1.debian.tar.xz
 087bef8df0ae04914437c5a6291fbfa5 34940 devel optional 
meson_0.63.2-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCgAxFiEEGeLW2bRtjapiiPh3wk5jG6ux/nAFAmMTgmkTHGpwYWtrYW5l
QGdtYWlsLmNvbQAKCRDCTmMbq7H+cBhAEACYn8NBMer+hx/Pdc+/6IPHIgXiMQnS

Bug#1012219: Please adjust StanHeaders to new version of (one)tbb

[Benjamin K Goodrich]

Sorry for the late reply. I am told that StanHeaders can be built
successfully with oneTBB by setting environmental variables like
TBB_INC and TBB_LIB. On CRAN, we would like to use the version of TBB
that comes with the RcppParallel package

https://github.com/RcppCore/RcppParallel/pull/144

Although with the next release of StanHeaders we will not be able to
achieve that because not all packages are LinkingTo RcppParallel so we
have to build a similar TBB in the StanHeaders shared object. But on
Debian, if r-cran-rcppparallel switches to oneTBB, then it would be
fine if r-cran-stanheaders, r-cran-rstan, etc. depends on
r-cran-rcppparallel.

Bug#1012928: marked as done (flatbuffers: ftbfs with GCC-12)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 18:49:15 +
with message-id 
and subject line Bug#1012928: fixed in flatbuffers 2.0.6+dfsg1-2
has caused the Debian Bug report #1012928,
regarding flatbuffers: ftbfs with GCC-12
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.)


-- 
1012928: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012928
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flatbuffers
Version: 1.12.1~git20200711.33e2d80+dfsg1-0.6
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12

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

The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/flatbuffers_1.12.1~git20200711.33e2d80+dfsg1-0.6_unstable_gcc12.log
The last lines of the build log are at the end of this report.

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

  apt-get -t=experimental install g++ 

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

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

[...]
 from /<>/tests/test_builder.h:7,
 from /<>/tests/test_builder.cpp:1:
In constructor ‘std::_Sp_ebo_helper<_Nm, _Tp, false>::_Sp_ebo_helper(_Tp&&) 
[with int _Nm = 0; _Tp = 
builder_move_assign_after_releaseraw_test(flatbuffers::FlatBufferBuilder)::]’,
inlined from ‘std::_Sp_counted_deleter<_Ptr, _Deleter, _Alloc, 
_Lp>::_Impl::_Impl(_Ptr, _Deleter, const _Alloc&) [with _Ptr = unsigned char*; 
_Deleter = 
builder_move_assign_after_releaseraw_test(flatbuffers::FlatBufferBuilder)::;
 _Alloc = std::allocator; __gnu_cxx::_Lock_policy _Lp = 
__gnu_cxx::_S_atomic]’ at /usr/include/c++/12/bits/shared_ptr_base.h:503:59,
inlined from ‘std::_Sp_counted_deleter<_Ptr, _Deleter, _Alloc, 
_Lp>::_Sp_counted_deleter(_Ptr, _Deleter, const _Alloc&) [with _Ptr = unsigned 
char*; _Deleter = 
builder_move_assign_after_releaseraw_test(flatbuffers::FlatBufferBuilder)::;
 _Alloc = std::allocator; __gnu_cxx::_Lock_policy _Lp = 
__gnu_cxx::_S_atomic]’ at /usr/include/c++/12/bits/shared_ptr_base.h:521:9,
inlined from ‘std::__shared_count<_Lp>::__shared_count(_Ptr, _Deleter, 
_Alloc) [with _Ptr = unsigned char*; _Deleter = 
builder_move_assign_after_releaseraw_test(flatbuffers::FlatBufferBuilder)::;
 _Alloc = std::allocator;  = void; 
__gnu_cxx::_Lock_policy _Lp = __gnu_cxx::_S_atomic]’ at 
/usr/include/c++/12/bits/shared_ptr_base.h:952:8,
inlined from ‘std::__shared_count<_Lp>::__shared_count(_Ptr, _Deleter) 
[with _Ptr = unsigned char*; _Deleter = 
builder_move_assign_after_releaseraw_test(flatbuffers::FlatBufferBuilder)::;
  = void; __gnu_cxx::_Lock_policy _Lp = 
__gnu_cxx::_S_atomic]’ at /usr/include/c++/12/bits/shared_ptr_base.h:939:57,
inlined from ‘std::__shared_ptr<_Tp, _Lp>::__shared_ptr(_Yp*, _Deleter) 
[with _Yp = unsigned char; _Deleter = 
builder_move_assign_after_releaseraw_test(flatbuffers::FlatBufferBuilder)::;
  = void; _Tp = unsigned char; __gnu_cxx::_Lock_policy 
_Lp = __gnu_cxx::_S_atomic]’ at 
/usr/include/c++/12/bits/shared_ptr_base.h:1478:17,
inlined from ‘std::shared_ptr<_Tp>::shared_ptr(_Yp*, _Deleter) [with _Yp = 
unsigned char; _Deleter = 
builder_move_assign_after_releaseraw_test(flatbuffers::FlatBufferBuilder)::;
  = void; _Tp = unsigned char]’ at 
/usr/include/c++/12/bits/shared_ptr.h:232:48,
inlined from ‘void builder_move_assign_after_releaseraw_test(Builder) [with 
Builder = flatbuffers::FlatBufferBuilder]’ at 
/<>/tests/test_builder.h:67:28:
/usr/include/c++/12/bits/shared_ptr_base.h:482:45: error: ‘size’ may be used 
uninitialized [-Werror=maybe-uninitialized]
  482 |   

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

[Thorsten Glaser]

On Sat, 3 Sep 2022, Helge Kreutzmann wrote:

> The upload of manpages-l10n (manpages-fr) was just accepted in
> unstable.

OK, thanks.

AIUI we now need another upload of src:sysvinit in which bin:bootlogd
gets a Replaces and Breaks on manpages-fr (<< 4.15.0-9~), correct?

I can do that this weekend, ceteris paribus, unless anyone shouts.

Where, though, are the other Replaces/Breaks? I cannot find any on
the 3.05-1 binary packages? These are needed for upgrade ordering…
… oh, the manpages for the other packages are just diverted? That
will do, I suppose?

bye,
//mirabilos
-- 
Infrastrukturexperte • tarent solutions GmbH
Am Dickobskreuz 10, D-53121 Bonn • http://www.tarent.de/
Telephon +49 228 54881-393 • Fax: +49 228 54881-235
HRB AG Bonn 5168 • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg


/⁀\ The UTF-8 Ribbon
╲ ╱ Campaign against  Mit dem tarent-Newsletter nichts mehr verpassen:
 ╳  HTML eMail! Also, https://www.tarent.de/newsletter
╱ ╲ header encryption!

Bug#1019093: python-pgmagick FTBFS: error: no matches converting function ‘colorMapSize’ to type ‘unsigned int (class Magick::Image::*)()’

[Adrian Bunk]

Source: python-pgmagick
Version: 0.7.6-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-pgmagick=amd64=0.7.6-1%2Bb3=1662226834=0

...
./src/_Image.cpp: In function ‘void __Image()’:
./src/_Image.cpp:385:82: error: no matches converting function ‘colorMapSize’ 
to type ‘unsigned int (class Magick::Image::*)()’
  385 | .def("colorMapSize", (unsigned int (Magick::Image::*)() 
)::Image::colorMapSize)
  | 
 ^~~~
In file included from ./src/_Image.cpp:6:
/usr/include/GraphicsMagick/Magick++/Image.h:908:21: note: candidates are: 
‘unsigned int Magick::Image::colorMapSize() const’
  908 | unsigned intcolorMapSize ( void ) const;
  | ^~~~
/usr/include/GraphicsMagick/Magick++/Image.h:907:21: note: 
‘void Magick::Image::colorMapSize(unsigned int)’
  907 | voidcolorMapSize ( const unsigned int entries_ );
  | ^~~~
error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1
E: pybuild pybuild:379: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build 
dh_auto_build: error: pybuild --build -i python{version} -p 3.10 returned exit 
code 13
make: *** [debian/rules:8: binary-arch] Error 25

Bug#1019091: pytango must now build depend on cppzmq-dev

[Adrian Bunk]

On Sat, Sep 03, 2022 at 08:22:12PM +0300, Adrian Bunk wrote:
> Source: pytango
> Version: 9.3.4-2
> Severity: serious
> Tags: ftbfs
> 
> See #972785 for background.

I forgot to include the error message:

https://buildd.debian.org/status/fetch.php?pkg=pytango=amd64=9.3.4-2%2Bb2=1662225534=0

...
In file included from /usr/include/tango/tango.h:146,
 from /<>/ext/attribute_event_info.cpp:13:
/usr/include/tango/event.h:41:10: fatal error: zmq.hpp: No such file or 
directory
   41 | #include 
  |  ^
compilation terminated.
...


cu
Adrian

Bug#1000482: marked as done (neomutt: license conflict with libsasl2)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 17:21:50 +
with message-id 
and subject line Bug#1000482: fixed in neomutt 20220429+dfsg1-2
has caused the Debian Bug report #1000482,
regarding neomutt: license conflict with libsasl2
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.)


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

Package: neomutt
Version: 20201127+dfsg.1-1.2
Severity: important

Hi,

neomutt depends on libsasl2-2, which is licensed under CMU's BSD-4-clause 
license and covered by the RSA-MD and OpenSSL
licenses. All of them have an advertisement clause in place, which is known to 
be incompatible with GPL.
There are several possible solutions to this problem:

1) Build without SASL support.

2) Support my request at #996892.

3) Ask upstream to add a license exception for libsasl2-2, similar to the one 
that was required by Debian for OpenSSL
for a long time.

Thanks for your consideration,
Bastian
--- End Message ---
--- Begin Message ---
Source: neomutt
Source-Version: 20220429+dfsg1-2
Done: Antonio Radici 

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

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

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

Debian distribution maintenance software
pp.
Antonio Radici  (supplier of updated neomutt package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Sep 2022 18:48:57 +0200
Source: neomutt
Architecture: source
Version: 20220429+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Mutt maintainers 
Changed-By: Antonio Radici 
Closes: 1000482
Changes:
 neomutt (20220429+dfsg1-2) unstable; urgency=medium
 .
   * Removed SASL support from neomutt (Closes: 1000482).
 + this prevents the removal from Debian due to licensing issues.
 + once gsasl support is available, SASL support will be re-enabled.
 + see also upstream bug https://github.com/neomutt/neomutt/issues/3514
Checksums-Sha1:
 ae66ef2922f272f1d82913d453080ebcace1cabf 2279 neomutt_20220429+dfsg1-2.dsc
 12a097e340fc867d74dc8d42a5bf942abc4d71be 26108 
neomutt_20220429+dfsg1-2.debian.tar.xz
 77ab9e8a9cdcc8f5948e466343ddba0e18112fd7 9459 
neomutt_20220429+dfsg1-2_amd64.buildinfo
Checksums-Sha256:
 4571fa7a6117f5716d6ea5b1ffb029237826c45fe30daeb67fdd997c11f4a899 2279 
neomutt_20220429+dfsg1-2.dsc
 2e75b2101dc980c3adf6bc03ca92f115444d324bf9e842139e0c6489d0db0984 26108 
neomutt_20220429+dfsg1-2.debian.tar.xz
 b845b3e6afa7fca350c40528380c327835992f9be810c96682ecf3e72bfbd059 9459 
neomutt_20220429+dfsg1-2_amd64.buildinfo
Files:
 f4a89e043d6b54cd6f4c91c87e761001 2279 mail optional 
neomutt_20220429+dfsg1-2.dsc
 078465ea0703edcf355946b5fb3a0145 26108 mail optional 
neomutt_20220429+dfsg1-2.debian.tar.xz
 f783f14982b8f9cdebb0e1fb452c5e9b 9459 mail optional 
neomutt_20220429+dfsg1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJHBAEBCAAxFiEEQObYrBkA1SRrfOa1NcjIiHLLHu0FAmMTiZQTHGFudG9uaW9A
ZGViaWFuLm9yZwAKCRA1yMiIcsse7e1LEAC3MSfiaDKKKH31U/NWrD+GdRJirD28
nEMn3+M/SKhERrFH4ms+yGEwlH6GFLeDb8FfQbBMFB6aDTWvl1KF185eDMNq1kNv
0qdL3kqWONMrC7io50wFDwABm+QDVs7GciDJkf3spxTdskfvHI3E4z8TQ+MfGNZT
RsMqHQ2qMlQUKEyw2Dq3U65UYEBSI0+u2QK4+JIdMR4yEOhgW2QHzK0uQ7d3xIq3
DNCDP9ZKzBAbetzNE+DyNTWXyFvB7I4uSbpsDq3RxxeycsAg5eQqghq2SZoCWd57
O6Pc5ou6cyJXeBnCK+x8Zxurb1xDyhdEh+zwpdFoV5dHtd8gaon5iFdqAbY6odSx
dgc6zrFsrgPdcug8RykErXjergRFQltVYEdliNl8eAiruoNZYM6cCRAPPuA3jPe4
y7R28Eo62RO0UChSEaq0STsrFATIkVwKbHN+P8H5Ece0Y7KRc1Q3EQeihml8FLGE
BTRV7oTY2XUZ4fUd31QwJagarV1MmLPIjTxDqo2L2qBtGIOJ06l4jWG4MmHrDQcr
4Af0dRMVyAT6AhY6G9+QT1ySOektB8ErcdMb5NiIi9/Lht/n6wvPCrSLhYQ47BpQ
Zp8teGhiLAEedFklxrDmt9itvzOLIOLJi4yjuOkn9L+g3X4EMlY4x3WEpRserPll
azZ1lhp+tQivqQ==
=1Mfe
-END PGP SIGNATURE End Message ---

Bug#1019091: pytango must now build depend on cppzmq-dev

[Adrian Bunk]

Source: pytango
Version: 9.3.4-2
Severity: serious
Tags: ftbfs

See #972785 for background.

Bug#1018191: libapreq2: CVE-2022-22728: multipart form parse memory corruption

[Salvatore Bonaccorso]

Hi,

On Sat, Sep 03, 2022 at 03:31:15PM +0200, Steinar H. Gunderson wrote:
> On Fri, Aug 26, 2022 at 09:07:06PM +0200, Salvatore Bonaccorso wrote:
> > The following vulnerability was published for libapreq2.
> > 
> > CVE-2022-22728[0]:
> > | A flaw in Apache libapreq2 versions 2.16 and earlier could cause a
> > | buffer overflow while processing multipart form uploads. A remote
> > | attacker could send a request causing a process crash which could lead
> > | to a denial of service attack.
> 
> Based on the description, I assume it is this one:
> 
> http://svn.apache.org/viewvc?view=revision=1866760
> 
> I'm not sure if it counts as “buffer overflow”, but given that it only
> mentions DoS and not arbitrary code execution, NULL pointer dereference
> looks a lot like it. 2.13 appears vulnerable to me, given the description.
> 
> I don't use libapreq2 anymore, so anyone wanting to pick up the package
> would be more than welcome. Upstream homepage is now seemingly at:
> 
>   https://httpd.apache.org/apreq/

Thanks for having investigated this further. This is puzzling and
upstream has not yet answered on queries about isolating the fix. The
above would be already a couple of years old. And
https://bugs.gentoo.org/show_bug.cgi?id=CVE-2022-22728#c1 seems to
indicate there must be something in recent days about it. A diff
between libapreq2-2.16 and libapreq2-2.17 has in fact:

diff -urN libapreq2-2.16/CHANGES libapreq2-2.17/CHANGES
--- libapreq2-2.16/CHANGES  2021-03-10 14:46:30.0 +0100
+++ libapreq2-2.17/CHANGES  2022-08-18 11:19:04.0 +0200
@@ -1,6 +1,11 @@
 /** @page apreq_changes CHANGES
 //! brief List of major changes.

+@section v2_17 Changes with libapreq2-2.17 (released 25 August, 2022)
+
+- Multipart header parser [Yann Ylavic]
+  Rework apreq_parse_headers() to discard CRLF of folded values.
+
 @section v2_16 Changes with libapreq2-2.16 (released 17 March, 2021)

But maybe as you suggest we have to go back . Though it should be
something which still affects 2.16 upstream. and likely so not the
newley released 2.17.

Regards,
Salvatore

Processed: juman: ftbfs with GCC-10

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #957392 [src:juman] juman: ftbfs with GCC-10
Severity set to 'important' from 'serious'

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

Bug#957392: juman: ftbfs with GCC-10

[Graham Inggs]

Control: severity -1 important

juman 7.0-3.5 build successfully on the buildds with GCC 12.
Therefore I am lowering the severity of this bug.

Processed: block 898400 with 1019044

[Debian Bug Tracking System]

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

> block 898400 with 1019044
Bug #898400 [wnpp] ITP: sccache -- compiler cache for fast recompilation of 
C/C++/Rust code
898400 was blocked by: 1014217 1014216 969609 1019090
898400 was not blocking any bugs.
Added blocking bug(s) of 898400: 1019044
> thanks
Stopping processing here.

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

Processed: block 898400 with 1019090

[Debian Bug Tracking System]

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

> block 898400 with 1019090
Bug #898400 [wnpp] ITP: sccache -- compiler cache for fast recompilation of 
C/C++/Rust code
898400 was blocked by: 1014217 1014216 969609
898400 was not blocking any bugs.
Added blocking bug(s) of 898400: 1019090
> thanks
Stopping processing here.

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

Processed: block 1008016 with 1019090

[Debian Bug Tracking System]

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

> block 1008016 with 1019090
Bug #1008016 [wnpp] ITP: safe-network -- network routing and service daemon for 
the Safe Network
1008016 was blocked by: 1013106 1013109 1010099 1013139 1010083 1013115 1013136 
1013137 984864 1016409 974118 1010212 1013144 1017918 1013108 1010075 1013138 
1013142 1010275 1019044 1013117 1009888
1008016 was not blocking any bugs.
Added blocking bug(s) of 1008016: 1019090
> thanks
Stopping processing here.

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

Processed: Re: librust-once-cell-dev: impossible to satidfy dependency on librust-parking-lot-core-0.8-dev

[Debian Bug Tracking System]

Processing control commands:

> severity -1 grave
Bug #1019044 [librust-once-cell-dev] librust-once-cell-dev: impossible to 
satisfy dependency on librust-parking-lot-core-0.8-dev
Severity set to 'grave' from 'normal'

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

Bug#1019090: librust-petgraph-dev: impossible to satisfy dependency

[Jonas Smedegaard]

Package: librust-petgraph-dev
Version: 0.5.1-2
Severity: grave
Justification: renders package unusable

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512


nary package librust-petgraph-dev cannoy be installed, as it depends on
missing package librust-fixedbitset-0.2-dev.


-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAmMTdHYACgkQLHwxRsGg
ASFgBhAAnr1YrSm7uazC0cXPfvvkUocVqWZxvJHuhSTUnoLNhkGKFEhc2xKwLeTy
oVUUzKaNc44YGtUBXJHgU2gXJ7FdR///PG/oXwJoIEILtlsRwBXCdDTgWXmFHn/Z
2NG6J+deddRYKNG7+B4V360e00t946W9CnWluy/ugk0xVnlzL+v5T4skQeOvGcBr
H6D6nNmAGqmre/IwB8q/PbSxEctKgqw4H5MiM0gVYwd7xCzpkqmsFwHOl2J3eMCJ
mFJDqYaaVwx3v4VW+zk5GDJvXAf8wSrz9sOcySkERSwVTiTQYAYW/21nFDv6x551
VXUW786hhbp+FAK0lJLMkDnKcS+Tl/VfnxIiebo60TdSPlX3iJYcrzvYSenmK2jp
S6obupY94cEYvaA+1Ae5wdc5rr0IylMwVPyII95fX5mp21gLvzzHHvF0Edi6AAhs
oYFFYdWMaQxKmLd6sWOPhDHa5kjYtfstk1T3uINutQWVH+KWFSpogyx+XG9VVE+k
mz6U6qKqhlhFd+bEBRJDdRa3k0JXROx7aYUOqzB963uH+49X4VD9z6Ng7j8PJIWk
BIgxxmdJCChStJa3qHRJHfB0nILg5dDQOFYYvgzS3mooOLnya6NVJN3tzhwEpHAt
HNO4VtaNBj6jcOSKaUgTzMKVsNoO2bXuD2Oa39a5Kky+EovXTe8=
=3XsI
-END PGP SIGNATURE-

Bug#1017240: marked as done (silo-llnl: FTBFS: ./conftest.c:27: undefined reference to `foobar')

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 15:02:50 +
with message-id 
and subject line Bug#1017240: fixed in silo-llnl 4.11-3
has caused the Debian Bug report #1017240,
regarding silo-llnl: FTBFS: ./conftest.c:27: undefined reference to `foobar'
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.)


-- 
1017240: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017240
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: silo-llnl
Version: 4.11-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> /usr/bin/ld: /tmp/ccbMnnee.o: in function `main':
> ./conftest.c:27: undefined reference to `foobar'
> collect2: error: ld returned 1 exit status


The full build log is available from:
http://qa-logs.debian.net/2022/08/13/silo-llnl_4.11-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220813;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20220813=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 marking 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: silo-llnl
Source-Version: 4.11-3
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated silo-llnl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Sep 2022 15:09:57 +0100
Source: silo-llnl
Architecture: source
Version: 4.11-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1017240
Changes:
 silo-llnl (4.11-3) unstable; urgency=medium
 .
   * Fix for FTBFS with g++12. Closes: #1017240
   * Standards-Version: 4.6.1
Checksums-Sha1:
 e58ff6eb587febfc6d8669bd68bfba82b0d9476a 2387 silo-llnl_4.11-3.dsc
 5e68acc773041adc27897838862f557e31efa4c7 14136 silo-llnl_4.11-3.debian.tar.xz
Checksums-Sha256:
 f39c9192e351acacc75165c2a8dc613280839338b2d3acf61e0c8c60374a1569 2387 
silo-llnl_4.11-3.dsc
 b6e40adf3e48443072d9491fd9ad1cce47477abbdaffcd7d266cb6faa226bf8d 14136 
silo-llnl_4.11-3.debian.tar.xz
Files:
 b5b0f5e2816bf17ca44baef824310c3d 2387 science optional silo-llnl_4.11-3.dsc
 4cd4be206e5dc381705ff992d82e9a1d 14136 science optional 
silo-llnl_4.11-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmMTYUAACgkQy+a7Tl2a
06WhHg/+P4+aCo84mQHRx4be6nu5bDzRsSNmKTdrTn6NbvWxyFCMQR0j+CW6p7J3
S6Ch96yf75unJMW6Jyh683sU1UcNqE4XY6hRaGzyZ7lnfzXzTFZe+BHxLhYska4M
l1g3GKpbSLAPQuBaNDaHGpNx+dYnCnQvcYc8R0aBFKpNnRYXUsQqNFAV7/j4glD8
Rsm1hLfv+mk+vh0LuxP5yxkL6SmLv9cy+y8+yo63Ni4lVDP9heDKVW4070cm9jps
RMVbAgbLf9Wlcl2PDsXZZdXqrLjQ7XcpC7n+d6NNcEp5p9OyV2Hg4hoV0OhEec1k
ErSei4oa/PjZv2YN/ExZD6413o2ZK4cm6w2id4qxPx1DgBGzBla6rjrTBDORtLDW
baP0NHDWmwdzUDrCCjCDkM49fNG92veRTQVBaepJiF9GkfICX5aGXTQzjnwoUitx
lFtA8egKh7L4L/jEFfQfQRHUrP9QGN5dnjmNB0SZEWiSXCg/57m1Mpsb/prMYY1b
m5x02avTqrABnj5wL2e/Rnemh2FnTm2zoj01aZNV6kkamzm0UWHhoKdvo1/UcHXY
8vDKZiPwcGAzqQZU09y/sHiMe8l/PxvS8AiDcIeO8giqrbs1tdVjw5TV/5tfopEv
lLKQbaEF9nGQYpm9td01LKeRTAuFP3EPNFCm+Pd8Po9rMK7ERg8=
=SPt4
-END PGP SIGNATURE End Message ---

Bug#1015758: ocaml-odoc: autopkgtests failures

[Gianfranco Costamagna]

Hello, ping?

G.

On Wed, 20 Jul 2022 18:42:32 +0200 Gianfranco Costamagna 
 wrote:

Source: ocaml-odoc
Version: 2.1.0+dfsg-1
Severity: serious

Hello, as said, the autopkgtests are now failing due to new ocaml or new ocaml 
libraries.

https://ci.debian.net/data/autopkgtest/unstable/amd64/o/ocaml-odoc/23587053/log.gz

Please have a look if the new upstream version is enough to fix it.


autopkgtest [04:42:43]: test odoc-on-odoc: [---
File series fully applied, ends at patch debian/patches/no-vendored-js-highlight
File "src/odoc/bin/main.ml", line 9, characters 51-64:
9 | let convert_syntax : Odoc_document.Renderer.syntax Arg.converter =
^
Error (alert deprecated): Cmdliner.Arg.converter
Use Arg.conv' function instead.
File "src/odoc/bin/main.ml", line 9, characters 51-64:
9 | let convert_syntax : Odoc_document.Renderer.syntax Arg.converter =
^
Error (alert deprecated): Cmdliner.Arg.converter
Use Arg.conv' function instead.
File "src/odoc/bin/main.ml", line 21, characters 60-73:
21 | let convert_directory ?(create = false) () : Fs.Directory.t Arg.converter =
  ^
Error (alert deprecated): Cmdliner.Arg.converter
Use Arg.conv' function instead.
File "src/odoc/bin/main.ml", line 73, characters 6-17:
73 |   Arg.env_var "ODOC_WARN_ERROR" ~doc:(doc ^ " See option $(opt).")
^^^
Error (alert deprecated): Cmdliner.Arg.env_var
Use Cmd.Env.info instead.
File "src/odoc/bin/main.ml", line 82, characters 14-25:
82 | let env = Arg.env_var "ODOC_PRINT_WARNINGS" ~doc in
^^^
Error (alert deprecated): Cmdliner.Arg.env_var
Use Cmd.Env.info instead.
File "src/odoc/bin/main.ml", line 217, characters 4-13:
217 | Term.info "compile"
   ^
Error (alert deprecated): Cmdliner.Term.info
Use Cmd.info instead.
File "src/odoc/bin/main.ml", line 113, characters 13-22:
113 |   val info : Term.info
^
Error (alert deprecated): Cmdliner.Term.info
Use Cmd.info instead.
File "src/odoc/bin/main.ml", line 236, characters 4-13:
236 | Term.info ~doc "support-files"
   ^
Error (alert deprecated): Cmdliner.Term.info
Use Cmd.info instead.
File "src/odoc/bin/main.ml", line 247, characters 4-13:
247 | Term.info ~doc "css"
   ^
Error (alert deprecated): Cmdliner.Term.info
Use Cmd.info instead.
File "src/odoc/bin/main.ml", line 288, characters 13-22:
288 |   let info = Term.info ~doc:"Link odoc files together" "link"

Processed: tagging 1017131

[Debian Bug Tracking System]

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

> tags 1017131 + fixed-upstream
Bug #1017131 [src:aspcud] aspcud: FTBFS: catch.hpp:10822:58: error: call to 
non-‘constexpr’ function ‘long int sysconf(int)’
Added tag(s) fixed-upstream.
> thanks
Stopping processing here.

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

Bug#1008355: marked as done (python-ldap: _slaptest.py fails with "slapd exited before opening port", breaking other package builds)

[Debian Bug Tracking System]

Your message dated Sat, 3 Sep 2022 16:27:33 +0200
with message-id 
and subject line python-ldap 1008355 fixed in 3.4.0-1
has caused the Debian Bug report #1008355,
regarding python-ldap: _slaptest.py fails with "slapd exited before opening 
port", breaking other package builds
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.)


-- 
1008355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008355
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-auth-ldap
Version: 3.0.0-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220326 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> dh_auto_test -- --system=custom --test-args="PYTHONPATH=. {interpreter} 
> /usr/bin/django-admin test --settings tests.settings"
> I: pybuild pybuild:298: cp -r /<>/tests 
> /<>/.pybuild/cpython3_3.10_django-auth-ldap/build
> I: pybuild base:237: PYTHONPATH=. python3.10 /usr/bin/django-admin test 
> --settings tests.settings
> Creating test database for alias 'default'...
> System check identified no issues (0 silenced).
> E
> ==
> ERROR: setUpClass (tests.tests.LDAPTest)
> --
> Traceback (most recent call last):
>   File "/<>/tests/tests.py", line 140, in setUpClass
> cls.server.start()
>   File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line 445, in 
> start
> self._start_slapd()
>   File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line 420, in 
> _start_slapd
> raise RuntimeError("slapd exited before opening port")
> RuntimeError: slapd exited before opening port
> 
> --
> Ran 0 tests in 1.517s
> 
> FAILED (errors=1)
> Destroying test database for alias 'default'...
> E: pybuild pybuild:367: test: plugin custom failed with: exit code=1: 
> PYTHONPATH=. python3.10 /usr/bin/django-admin test --settings tests.settings
> I: pybuild pybuild:298: cp -r /<>/tests 
> /<>/.pybuild/cpython3_3.9_django-auth-ldap/build
> I: pybuild base:237: PYTHONPATH=. python3.9 /usr/bin/django-admin test 
> --settings tests.settings
> Creating test database for alias 'default'...
> System check identified no issues (0 silenced).
> E
> ==
> ERROR: setUpClass (tests.tests.LDAPTest)
> --
> Traceback (most recent call last):
>   File "/<>/tests/tests.py", line 140, in setUpClass
> cls.server.start()
>   File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line 445, in 
> start
> self._start_slapd()
>   File "/usr/lib/python3/dist-packages/slapdtest/_slapdtest.py", line 420, in 
> _start_slapd
> raise RuntimeError("slapd exited before opening port")
> RuntimeError: slapd exited before opening port
> 
> --
> Ran 0 tests in 1.524s
> 
> FAILED (errors=1)
> Destroying test database for alias 'default'...
> E: pybuild pybuild:367: test: plugin custom failed with: exit code=1: 
> PYTHONPATH=. python3.9 /usr/bin/django-admin test --settings tests.settings
> dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" 
> --system=custom "--test-args=PYTHONPATH=. {interpreter} /usr/bin/django-admin 
> test --settings tests.settings" returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2022/03/26/django-auth-ldap_3.0.0-1_unstable.log

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 marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects

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

This issue was fixed in python-ldap upstream release 3.4.0.

I added an autopkgtest to verify that a server can be started properly
and it passes, see:
https://salsa.debian.org/python-team/packages/python-ldap/-/commit/0f5726905bfd5e3d287896489ae15344667ffed7--- End Message ---

Processed: merging 1017314 1017151

[Debian Bug Tracking System]

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

> merge 1017314 1017151
Bug #1017314 [src:handbrake] handbrake: FTBFS: ../libhb/decsrtsub.c:223:39: 
error: ‘AV_NOPTS_VALUE’ undeclared (first use in this function)
Bug #1017314 [src:handbrake] handbrake: FTBFS: ../libhb/decsrtsub.c:223:39: 
error: ‘AV_NOPTS_VALUE’ undeclared (first use in this function)
Added tag(s) patch.
Bug #1017151 [src:handbrake] handbrake: FTBFS: ../libhb/decsrtsub.c:223:39: 
error: ‘AV_NOPTS_VALUE’ undeclared (first use in this function)
Merged 1017151 1017314
> thanks
Stopping processing here.

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

Bug#1018191: libapreq2: CVE-2022-22728: multipart form parse memory corruption

[Steinar H. Gunderson]

On Fri, Aug 26, 2022 at 09:07:06PM +0200, Salvatore Bonaccorso wrote:
> The following vulnerability was published for libapreq2.
> 
> CVE-2022-22728[0]:
> | A flaw in Apache libapreq2 versions 2.16 and earlier could cause a
> | buffer overflow while processing multipart form uploads. A remote
> | attacker could send a request causing a process crash which could lead
> | to a denial of service attack.

Based on the description, I assume it is this one:

http://svn.apache.org/viewvc?view=revision=1866760

I'm not sure if it counts as “buffer overflow”, but given that it only
mentions DoS and not arbitrary code execution, NULL pointer dereference
looks a lot like it. 2.13 appears vulnerable to me, given the description.

I don't use libapreq2 anymore, so anyone wanting to pick up the package
would be more than welcome. Upstream homepage is now seemingly at:

  https://httpd.apache.org/apreq/

/* Steinar */
-- 
Homepage: https://www.sesse.net/

Bug#1017257: marked as done (cfgrib: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_test] Error 13)

[Debian Bug Tracking System]

Your message dated Sat, 3 Sep 2022 14:05:45 +0100
with message-id 
and subject line Closing
has caused the Debian Bug report #1017257,
regarding cfgrib: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_test] 
Error 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.)


-- 
1017257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cfgrib
Version: 0.9.10.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220813 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> for p in python3.10; do \
> PY3VERNUM=`echo $p | sed -e 's/python//' `; \
>   pybuild --test --test-pytest -i $p -p $PY3VERNUM  ;  \
> done
> I: pybuild base:239: cd /<>/.pybuild/cpython3_3.10_cfgrib/build; 
> python3.10 -m pytest tests
> = test session starts 
> ==
> platform linux -- Python 3.10.6, pytest-7.1.2, pluggy-1.0.0+repack
> rootdir: /<>, configfile: pyproject.toml
> collected 113 items / 1 skipped
> 
> tests/test_10_cfunits.py .   [  
> 0%]
> tests/test_20_cfcoords.py .  [  
> 5%]
> tests/test_20_main.py .  [  
> 6%]
> tests/test_20_messages.py .  [ 
> 14%]
> tests/test_25_cfmessage.py . [ 
> 18%]
> tests/test_30_dataset.py ..  [ 
> 41%]
> tests/test_40_xarray_store.py .x..   [ 
> 48%]
> tests/test_40_xarray_to_grib_regular_ll.py . [ 
> 53%]
> tests/test_50_datamodels.py ..   [ 
> 54%]
> tests/test_50_sample_data.py .X.xx.X.x.xx[ 
> 86%]
> tests/test_50_xarray_getitem.py ..   [ 
> 95%]
> tests/test_50_xarray_plugin.py F.FF. 
> [100%]
> 
> === FAILURES 
> ===
> _ test_plugin 
> __
> 
> def test_plugin() -> None:
> engines = xr.backends.list_engines()
> cfgrib_entrypoint = engines["cfgrib"]
> >   assert cfgrib_entrypoint.__module__ == "cfgrib.xarray_plugin"
> E   AssertionError: assert 'xarray.backends.cfgrib_' == 
> 'cfgrib.xarray_plugin'
> E - cfgrib.xarray_plugin
> E + xarray.backends.cfgrib_
> 
> tests/test_50_xarray_plugin.py:16: AssertionError
> __ test_xr_open_dataset_dict 
> ___
> 
> def test_xr_open_dataset_dict() -> None:
> fieldset = {
> -10: {
> "gridType": "regular_ll",
> "Nx": 2,
> "Ny": 3,
> "distinctLatitudes": [-10.0, 0.0, 10.0],
> "distinctLongitudes": [0.0, 10.0],
> "paramId": 167,
> "shortName": "2t",
> "values": [[1, 2], [3, 4], [5, 6]],
> }
> }
> 
> >   ds = xr.open_dataset(fieldset, engine="cfgrib")
> 
> tests/test_50_xarray_plugin.py:44: 
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> /usr/lib/python3/dist-packages/xarray/backends/api.py:531: in open_dataset
> backend_ds = backend.open_dataset(
> /usr/lib/python3/dist-packages/xarray/backends/cfgrib_.py:129: in open_dataset
> store = CfGribDataStore(
> /usr/lib/python3/dist-packages/xarray/backends/cfgrib_.py:68: in __init__
> self.ds = cfgrib.open_file(filename, **backend_kwargs)
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ 
> _ 
> 
> path = {-10: {'Nx': 2, 'Ny': 3, 'distinctLatitudes': [-10.0, 0.0, 10.0], 
> 'distinctLongitudes': [0.0, 10.0], ...}}
> grib_errors = 'warn', indexpath = '{path}.{short_hash}.idx', filter_by_keys = 
> {}
> read_keys = [], time_dims = ('time', 'step'), extra_coords = {}
> kwargs = {'encode_cf': ('parameter', 'time', 'geography', 'vertical'), 
> 'squeeze': True}
> 
> def open_file(
> path: T.Union[str, "os.PathLike[str]"],
> grib_errors: str = "warn",
> indexpath: str = messages.DEFAULT_INDEXPATH,
> filter_by_keys: T.Dict[str, 

Bug#1009915: sysvinit: Please align with manpages-l10n and afterwards activate man page translations

[Helge Kreutzmann]

Hello Thorsten,
On Thu, Sep 01, 2022 at 06:39:18PM +0200, Thorsten Glaser wrote:
> > For Debian, as stated above, I can do another upload removing this
> > file as well.
> 
> Thanks. Feel free to reassign/close this bug at will then… or do we
> need another sysvinit upload with updated Replaces/Breaks/… as well,
> Andreas?

The upload of manpages-l10n (manpages-fr) was just accepted in
unstable.

Greetings

 Helge

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


signature.asc
Description: PGP signature

Bug#995387: marked as done (dpkg: remove-on-upgrade deletes symlink targets owned by another package)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id 
and subject line Bug#995387: fixed in dpkg 1.20.12
has caused the Debian Bug report #995387,
regarding dpkg: remove-on-upgrade deletes symlink targets owned by another 
package
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.)


-- 
995387: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995387
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.20.6
Severity: grave
Justification: breaks unrelated packages by removing their conffiles

Hi Guillem,

attached is a small package demonstrating the misbehavior of
remove-on-upgrade which may delete symlink targets. It builds foo.deb
(which has 'remove-on-upgrade /etc/old-conffile') and bar.deb (which
has /etc/old-conffile -> /etc/new-conffile).

# dpkg -i /tmp/bar_1_all.deb
Selecting previously unselected package bar.
(Reading database ... 14303 files and directories currently installed.)
Preparing to unpack /tmp/bar_1_all.deb ...
Unpacking bar (1) ...
Setting up bar (1) ...
# dpkg --verify bar
# dpkg -i /tmp/foo_1_all.deb
Selecting previously unselected package foo.
(Reading database ... 14307 files and directories currently installed.)
Preparing to unpack /tmp/foo_1_all.deb ...
Unpacking foo (1) ...
Setting up foo (1) ...
Obsolete conffile '/etc/new-conffile' has been modified by you.
Saving as /etc/new-conffile.dpkg-old ...
# dpkg --verify bar
??5?? c /etc/new-conffile


The actual bug where I encountered this misbehavior is
  #994971: OpenCL not working with latest Nvidia driver
and it was an error of debhelper converting rm_conffile to remove-on-upgrade
but dpkg played its part by deleting the symlink target instead of the
symlink itself, but it should rather do nothing (or print a diagnostic) if
the to-be-removed file is not a plain file.

At least there is an error if it is a directory:

# mkdir /etc/old-conffile
# dpkg -i /tmp/foo_1_all.deb
Selecting previously unselected package foo.
(Reading database ... 14304 files and directories currently installed.)
Preparing to unpack /tmp/foo_1_all.deb ...
Unpacking foo (1) ...
Setting up foo (1) ...
dpkg: warning: foo: conffile '/etc/old-conffile' is not a plain file or symlink 
(= '/etc/old-conffile')


Simplified, the nvidia use case the following:

Long ago, /etc/conffile was a conffile
That was later removed with rm_conffile
and since then the different co-installable drivers ship 
/etc/conffile-$driver_version instead
and a slave alternative exists as /etc/conffile pointing to the corresponding 
file of
the activated driver variant.
(The different drivers may require slightly different conffile content.)

Andreas


dpkg-bug-remove-on-upgrade.tar.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.20.12
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Sep 2022 05:38:12 +0200
Source: dpkg
Architecture: source
Version: 1.20.12
Distribution: bullseye
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Closes: 980963 991190 995387 1000421 1008316 1008478 1008764
Changes:
 dpkg (1.20.12) bullseye; urgency=medium
 .
   [ Guillem Jover ]
   * dpkg: Fix conffile removal-on-upgrade handling. Closes: #995387
   * dpkg: Fix memory leak in remove-on-upgrade handling.
   * dpkg-fsys-usrunmess: Move forced reconfiguration to the last step.
 See #991190.
   * dpkg-fsys-usrunmess: Install a local policy-rc.d to ignore service
 restarts. Closes: #991190
   * dpkg-fsys-usrunmess: Do not fail when removing lingering directories.
   * dpkg-fsys-usrunmess: Fix typo in debug message.
   * dpkg-fsys-usrunmess: Explicitly set user/group and mode for created dirs.
 Closes: #1008478
   * dpkg-fsys-usrunmess: Set a known umask before starting.
 See #1008478.
   * dpkg-fsys-usrunmess: Special case 

Bug#1016620: marked as done (nvidia-graphics-drivers-tesla-470: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:15 +
with message-id 
and subject line Bug#1016620: fixed in nvidia-graphics-drivers-tesla-470 
470.141.03-1~deb11u1
has caused the Debian Bug report #1016620,
regarding nvidia-graphics-drivers-tesla-470: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

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

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.141.03-1~deb11u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Sep 2022 11:49:52 +0200
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.141.03-1~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016614 1016620 1016736
Changes:
 nvidia-graphics-drivers-tesla-470 (470.141.03-1~deb11u1) bullseye; 
urgency=medium
 .
   * Rebuild for bullseye.
 .
 nvidia-graphics-drivers-tesla-470 

Bug#1016618: marked as done (nvidia-graphics-drivers-tesla-450: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:14 +
with message-id 
and subject line Bug#1016618: fixed in nvidia-graphics-drivers-tesla-450 
450.203.03-1~deb11u1
has caused the Debian Bug report #1016618,
regarding nvidia-graphics-drivers-tesla-450: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

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

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-450
Source-Version: 450.203.03-1~deb11u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-450 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Sep 2022 09:58:52 +0200
Source: nvidia-graphics-drivers-tesla-450
Architecture: source
Version: 450.203.03-1~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016618
Changes:
 nvidia-graphics-drivers-tesla-450 (450.203.03-1~deb11u1) bullseye; 
urgency=medium
 .
   * Rebuild for bullseye.
 .
 nvidia-graphics-drivers-tesla-450 (450.203.03-1) 

Bug#1016616: marked as done (nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:13 +
with message-id 
and subject line Bug#1016616: fixed in nvidia-graphics-drivers-legacy-390xx 
390.154-1~deb11u1
has caused the Debian Bug report #1016616,
regarding nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

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

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-legacy-390xx
Source-Version: 390.154-1~deb11u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-legacy-390xx 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: Mon, 29 Aug 2022 11:50:39 +0200
Source: nvidia-graphics-drivers-legacy-390xx
Architecture: source
Version: 390.154-1~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1012618 1012700 1016616
Changes:
 nvidia-graphics-drivers-legacy-390xx (390.154-1~deb11u1) bullseye; 
urgency=medium
 .
   * Rebuild for bullseye.
 .
 

Bug#1016614: marked as done (nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:15 +
with message-id 
and subject line Bug#1016614: fixed in nvidia-graphics-drivers-tesla-470 
470.141.03-1~deb11u1
has caused the Debian Bug report #1016614,
regarding nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

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

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers-tesla-470
Source-Version: 470.141.03-1~deb11u1
Done: Andreas Beckmann 

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated 
nvidia-graphics-drivers-tesla-470 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Sep 2022 11:49:52 +0200
Source: nvidia-graphics-drivers-tesla-470
Architecture: source
Version: 470.141.03-1~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016614 1016620 1016736
Changes:
 nvidia-graphics-drivers-tesla-470 (470.141.03-1~deb11u1) bullseye; 
urgency=medium
 .
   * Rebuild for bullseye.
 .
 nvidia-graphics-drivers-tesla-470 (470.141.03-1) 

Bug#1016614: marked as done (nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, CVE-2022-31615)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:12 +
with message-id 
and subject line Bug#1016614: fixed in nvidia-graphics-drivers 
470.141.03-1~deb11u1
has caused the Debian Bug report #1016614,
regarding nvidia-graphics-drivers: CVE-2022-31607, CVE-2022-31608, 
CVE-2022-31615
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.)


-- 
1016614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: nvidia-graphics-drivers
Severity: serious
Tags: security upstream
Control: clone -1 -2 -3 -4 -5 -6 -7 -8
Control: reassign -2 src:nvidia-graphics-drivers-legacy-340xx 340.76-6
Control: retitle -2 nvidia-graphics-drivers-legacy-340xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -2 + wontfix
Control: reassign -3 src:nvidia-graphics-drivers-legacy-390xx 390.48-4
Control: retitle -3 nvidia-graphics-drivers-legacy-390xx: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -4 src:nvidia-graphics-drivers-tesla-418 418.87.01-1
Control: retitle -4 nvidia-graphics-drivers-tesla-418: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -4 + wontfix
Control: reassign -5 src:nvidia-graphics-drivers-tesla-450 450.51.05-1
Control: retitle -5 nvidia-graphics-drivers-tesla-450: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -6 src:nvidia-graphics-drivers-tesla-460 460.32.03-1
Control: retitle -6 nvidia-graphics-drivers-tesla-460: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: tag -6 + wontfix
Control: close -6 460.106.00-3
Control: reassign -7 src:nvidia-graphics-drivers-tesla-470 470.57.02-1
Control: retitle -7 nvidia-graphics-drivers-tesla-470: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: reassign -8 src:nvidia-graphics-drivers-tesla-510 510.47.03-1
Control: retitle -8 nvidia-graphics-drivers-tesla-510: CVE-2022-31607, 
CVE-2022-31608, CVE-2022-31615
Control: found -1 340.24-1
Control: found -1 343.22-1
Control: found -1 396.18-1
Control: found -1 430.14-1
Control: found -1 455.23.04-1
Control: found -1 465.24.02-1
Control: found -1 495.44-1

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

CVE-2022-31607  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer (nvidia.ko), where a local user
with basic capabilities can cause improper input validation, which may
lead to denial of service, escalation of privileges, data tampering, and
limited information disclosure.

CVE-2022-31608  NVIDIA GPU Display Driver for Linux contains a
vulnerability in an optional D-Bus configuration file, where a local
user with basic capabilities can impact protected D-Bus endpoints, which
may lead to code execution, denial of service, escalation of privileges,
information disclosure, and data tampering.

CVE-2022-31615  NVIDIA GPU Display Driver for Linux contains a
vulnerability in the kernel mode layer, where a local user with basic
capabilities can cause a null-pointer dereference, which may lead to
denial of service.

Linux Driver Branch CVE IDs Addressed
R515, R510, R470, R450, R390CVE-2022-31607, CVE-2022-31608, CVE-2022-31615


Andreas
--- End Message ---
--- Begin Message ---
Source: nvidia-graphics-drivers
Source-Version: 470.141.03-1~deb11u1
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated nvidia-graphics-drivers 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 02 Sep 2022 10:57:14 +0200
Source: nvidia-graphics-drivers
Architecture: source
Version: 470.141.03-1~deb11u1
Distribution: bullseye
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016614 1016736
Changes:
 nvidia-graphics-drivers (470.141.03-1~deb11u1) bullseye; urgency=medium
 .
   * Rebuild for bullseye.
 .
 nvidia-graphics-drivers (470.141.03-1) unstable; urgency=medium
 .
   * New upstream production branch release 

Bug#1016420: marked as done (libreoffice-evolution: Evolution address source indefinitely freezes UI)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:11 +
with message-id 
and subject line Bug#1016420: fixed in libreoffice 1:7.0.4-4+deb11u3
has caused the Debian Bug report #1016420,
regarding libreoffice-evolution: Evolution address source indefinitely freezes 
UI
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.)


-- 
1016420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libreoffice-evolution
Severity: grave
Justification: renders package unusable
Control: forwarded -1 https://bugs.documentfoundation.org/show_bug.cgi?id=137101
Control: tag -1 + upstream
Control: tag -1 + fixed-upstream
Control: fixed -1 1:7.3.0~rc1-1
Control: block -1 by 1016413

Hi,

filing for documentation purposes. Sparing a version since it should
affect anything back to stretch and even earlier.

LibreOffice hangs indefinitely when connecting to an evolution address
book, blocking the UI.

See upstream bug
https://bugs.documentfoundation.org/show_bug.cgi?id=137101; this is
because of an ABI change in evolution no one really noticed until years
after it (and LO is not linking against libebook but dynamically loading it)

This is already upstream and a stable update is requested in #1016413

Regards,

Rene
--- End Message ---
--- Begin Message ---
Source: libreoffice
Source-Version: 1:7.0.4-4+deb11u3
Done: Rene Engelhard 

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

Debian distribution maintenance software
pp.
Rene Engelhard  (supplier of updated libreoffice 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, 28 Aug 2022 19:22:27 +0200
Source: libreoffice
Architecture: source
Version: 1:7.0.4-4+deb11u3
Distribution: bullseye
Urgency: medium
Maintainer: Debian LibreOffice Maintainers 
Changed-By: Rene Engelhard 
Closes: 1016420
Changes:
 libreoffice (1:7.0.4-4+deb11u3) bullseye; urgency=medium
 .
   * debian/patches/fix-e_book_client_connect_direct_sync-sig.diff:
 as name says (closes: #1016420)
Checksums-Sha1:
 d357ad2be16351f983d45dd0642168cbe627f671 31345 libreoffice_7.0.4-4+deb11u3.dsc
 ad7c60be3f5b1efec1c268e0c73d9832fc28311c 19517276 
libreoffice_7.0.4-4+deb11u3.debian.tar.xz
 3f8dfd886f70251d52f470613fedc8eee40b4f29 36998 
libreoffice_7.0.4-4+deb11u3_source.buildinfo
Checksums-Sha256:
 da98bc32a9e47b0e7fc5ab9087722db684662cabca662bb5db9fa7dfadb74135 31345 
libreoffice_7.0.4-4+deb11u3.dsc
 54ab7832d04bf74cbafd05140214c8f215d5da2b47ccb718ec3b082965101af5 19517276 
libreoffice_7.0.4-4+deb11u3.debian.tar.xz
 dc327fa9c416d5b89f175593e89472ae376fb63450d556aacfbedb1b1c7f99d3 36998 
libreoffice_7.0.4-4+deb11u3_source.buildinfo
Files:
 200047649689e0075d785eec9c04 31345 editors optional 
libreoffice_7.0.4-4+deb11u3.dsc
 2679ab65d23a2575bce8f4f812bc53d6 19517276 editors optional 
libreoffice_7.0.4-4+deb11u3.debian.tar.xz
 60b2445a15d532638b8f2601bd301d16 36998 editors optional 
libreoffice_7.0.4-4+deb11u3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCgAuFiEE4S3qRnUGcM+pYIAdCqBFcdA+PnAFAmMLv0oQHHJlbmVAZGVi
aWFuLm9yZwAKCRAKoEVx0D4+cKNZD/41nh13utlLiHbxHAlLQ2fvuXNlou8dFw/U
EVKjsRJRnpv44zGdDhP1tOwuUbiJknYc2dA1gfF963KIgQXgG207/BBRu868n7z9
YQmFzaUde+8qs66qK3j4iqZvQI3UlTZCsEgtbxI70vHahyFGlYPmfmsY2YwD/CjZ
WriBv9Lm8n+p0Kyd2MG+V90NVNCIJXE/C6tWBg6k1fsJwbshC90AyhIobWbJU2fE
3LZPjB/kEG3vWmZRS4a5Uc9V9V1MtM0Cr/ZJs9V1m4nBRjNglp7/wX3ccAUFIbbj
ICLUVWIS2Rir7ohR6IRjeya/00iSQld05Kg4VpJV40Vn63ExslgdmZBA3vYGrTyw
rGqu8+MCky5slYofFvVajQzKtFizC7FhxnuqqmQFx3BwitWSqh9YLGCEKhddqZmO
7zRWZfcV+fY9E0Hg8WvuBUf1xf97zYO0KEGABA+EaU3fT2FuPhGaalvBRn9iT6pi
xXloDi/uqV63uPk8ocKbYFlDYZKWzuMZGrsrej0O0VyfQex0Whv9lCptP1VGSlui
eIMbCrLYDlj8sYcJjnMjAqmMigQly0L23CeUNTNhBOUho+XI8bOZOCq1LXQOt9xs
ZxefHBPzi9gTowiVnS91J9NQuMskp5GusodqQXymmGMWHton+0sza0wB/kzplD+I
c1gsnLAsyQ==
=CNJh
-END PGP SIGNATURE End Message ---

Bug#1008478: marked as done (dpkg-fsys-usrunmess depends on umask 022)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id 
and subject line Bug#1008478: fixed in dpkg 1.20.12
has caused the Debian Bug report #1008478,
regarding dpkg-fsys-usrunmess depends on umask 022
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.)


-- 
1008478: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008478
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.21.4
Severity: critical
Justification: breaks the whole system

I ran dpkg-fsys-usrunmess using sudo under umask 077.  Several
directories including /bin /sbin /lib64 /lib32 /libx32 became mode 700.
I had to boot with rw init=/bin/bash to chmod them back to 755.

-- Package-specific info:

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-5-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5
ii  libc62.33-7
ii  liblzma5 5.2.5-2
ii  libselinux1  3.3-1+b2
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.4.3
pn  debsig-verify  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.20.12
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Sep 2022 05:38:12 +0200
Source: dpkg
Architecture: source
Version: 1.20.12
Distribution: bullseye
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Closes: 980963 991190 995387 1000421 1008316 1008478 1008764
Changes:
 dpkg (1.20.12) bullseye; urgency=medium
 .
   [ Guillem Jover ]
   * dpkg: Fix conffile removal-on-upgrade handling. Closes: #995387
   * dpkg: Fix memory leak in remove-on-upgrade handling.
   * dpkg-fsys-usrunmess: Move forced reconfiguration to the last step.
 See #991190.
   * dpkg-fsys-usrunmess: Install a local policy-rc.d to ignore service
 restarts. Closes: #991190
   * dpkg-fsys-usrunmess: Do not fail when removing lingering directories.
   * dpkg-fsys-usrunmess: Fix typo in debug message.
   * dpkg-fsys-usrunmess: Explicitly set user/group and mode for created dirs.
 Closes: #1008478
   * dpkg-fsys-usrunmess: Set a known umask before starting.
 See #1008478.
   * dpkg-fsys-usrunmess: Special case untracked kernel module files.
 Closes: #1008316
   * dpkg-fsys-usrunmess: Handle /lib/modules itself also being untracked.
 Closes: #1008764
   * Architecture support:
 - Add support for ARCv2 CPU.
   Based on a patch by Alexey Brodkin .
   Closes: #980963
   * Perl modules:
 - Dpkg::Shlibs::Objdump: Fix apply_relocations to work with versioned
   symbols. Closes: #1000421
   * Localization:
 - Fix missing newline in Dutch man pages translation.
Checksums-Sha1:
 bb9cd777963153c712029c1ae9f5b9a01ab0a7a8 2124 dpkg_1.20.12.dsc
 be23ca81df915e7cbf3382e6d2eed605b8dc9065 5009108 dpkg_1.20.12.tar.xz
 5703bcb4bcd726bf48b14eaf594a579ff52c73e0 8013 dpkg_1.20.12_amd64.buildinfo
Checksums-Sha256:
 fe919a7491472bab59362fab8da0c89cf59cd2eea4a8714db58f9f169fc62bf4 2124 
dpkg_1.20.12.dsc
 1428610305d00dffa9c35543fc3096bb1ce3293b53ed4ddad847a3d822eafbf0 5009108 
dpkg_1.20.12.tar.xz
 e07a6834207cefe0a7301a473691c1ab8e3e6008b8d147c5d6fa397dd8860dab 8013 
dpkg_1.20.12_amd64.buildinfo
Files:
 97223cdcafcfabf61ecd2f89a2f2bc50 2124 admin required dpkg_1.20.12.dsc
 985a0caceb5f54bb9bb7eb14c0358c22 5009108 admin required dpkg_1.20.12.tar.xz
 8a5bf2586dab77e89233809cfe420b19 8013 admin required 
dpkg_1.20.12_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Bug#1008316: marked as done (dpkg-fsys-usrunmess: Does not deal with untracked kernel modules)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id 
and subject line Bug#1008316: fixed in dpkg 1.20.12
has caused the Debian Bug report #1008316,
regarding dpkg-fsys-usrunmess: Does not deal with untracked kernel modules
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.)


-- 
1008316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg
Version: 1.21.4
Severity: critical
Justification: breaks the whole system

Gobally the scripts does a very good job but it missed to copy /usr/lib/modules 
to
/lib/modules on a self generated kernel that has modules build via dkms and a
few native kernel modules.

Invoquing the dkms postinstall script fails because it does not find 
/lib/modules/x.y.z
directories and rebooting without graphic drivers and other stff does not work.

So you probably should copy /usr/lib/modules to /lib/modules before the calling 
the
postinstall.

To fix i did:
   1) boot in recovery mode,
   2) copy /usr/lib/modules to /lib/modules
   3) dkms autoinstall
   4) update-grub

and it wworked.


-- Package-specific info:

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

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

Versions of packages dpkg depends on:
ii  libbz2-1.0   1.0.8-5
ii  libc62.34-0experimental3
ii  liblzma5 5.2.5-2
ii  libselinux1  3.3-1+b2
ii  tar  1.34+dfsg-1
ii  zlib1g   1:1.2.11.dfsg-4

dpkg recommends no packages.

Versions of packages dpkg suggests:
ii  apt2.4.3
pn  debsig-verify  

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.20.12
Done: Guillem Jover 

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Sep 2022 05:38:12 +0200
Source: dpkg
Architecture: source
Version: 1.20.12
Distribution: bullseye
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Closes: 980963 991190 995387 1000421 1008316 1008478 1008764
Changes:
 dpkg (1.20.12) bullseye; urgency=medium
 .
   [ Guillem Jover ]
   * dpkg: Fix conffile removal-on-upgrade handling. Closes: #995387
   * dpkg: Fix memory leak in remove-on-upgrade handling.
   * dpkg-fsys-usrunmess: Move forced reconfiguration to the last step.
 See #991190.
   * dpkg-fsys-usrunmess: Install a local policy-rc.d to ignore service
 restarts. Closes: #991190
   * dpkg-fsys-usrunmess: Do not fail when removing lingering directories.
   * dpkg-fsys-usrunmess: Fix typo in debug message.
   * dpkg-fsys-usrunmess: Explicitly set user/group and mode for created dirs.
 Closes: #1008478
   * dpkg-fsys-usrunmess: Set a known umask before starting.
 See #1008478.
   * dpkg-fsys-usrunmess: Special case untracked kernel module files.
 Closes: #1008316
   * dpkg-fsys-usrunmess: Handle /lib/modules itself also being untracked.
 Closes: #1008764
   * Architecture support:
 - Add support for ARCv2 CPU.
   Based on a patch by Alexey Brodkin .
   Closes: #980963
   * Perl modules:
 - Dpkg::Shlibs::Objdump: Fix apply_relocations to work with versioned
   symbols. Closes: #1000421
   * Localization:
 - Fix missing newline in Dutch man pages translation.
Checksums-Sha1:
 bb9cd777963153c712029c1ae9f5b9a01ab0a7a8 2124 dpkg_1.20.12.dsc
 be23ca81df915e7cbf3382e6d2eed605b8dc9065 5009108 dpkg_1.20.12.tar.xz
 5703bcb4bcd726bf48b14eaf594a579ff52c73e0 8013 dpkg_1.20.12_amd64.buildinfo
Checksums-Sha256:
 

Bug#1000421: marked as done (dpkg-shlibdeps: Wrong minimum version requirement on libc6)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 12:49:09 +
with message-id 
and subject line Bug#1000421: fixed in dpkg 1.20.12
has caused the Debian Bug report #1000421,
regarding dpkg-shlibdeps: Wrong minimum version requirement on libc6
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.)


-- 
1000421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000421
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dpkg-dev
Version: 1.20.9
Severity: serious
Control: affects -1 cppcheck

Hi,

dpkg-shlibdeps calculates too low minimum version requirements for cppcheck on 
libc6 (see bug 1000146).

To reproduce, build cppcheck 2.6-1 in unstable chroot without cleaning up, 
e.g., "dpkg-buildpackage -rfakeroot -us -uc".

$ grep Depends debian/cppcheck/DEBIAN/control
Depends: libc6 (>= 2.29), [...]

But running the binary with libc6 2.31 fails with

cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by cppcheck)
cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by 
/usr/lib/x86_64-linux-gnu/libstdc++.so.6)
cppcheck: ./libc.so.6: version `GLIBC_2.32' not found (required by 
/lib/x86_64-linux-gnu/libpthread.so.0)

I believe that is the case because a certain symbol in the .bss section is 
ignored (this is the only symbol with 2.32 suffix):

$ objdump -w -T ./debian/cppcheck/usr/bin/cppcheck | grep __libc_single_threaded
004670e0 gDO .bss   0001  GLIBC_2.32  
__libc_single_threaded

$ nm -D ./debian/cppcheck/usr/bin/cppcheck | grep __libc_single_threaded
004670e0 B __libc_single_threaded@@GLIBC_2.32

$ dpkg-shlibdeps ./debian/cppcheck/usr/bin/cppcheck; cat debian/substvars
shlibs:Depends=libc6 (>= 2.29), [...]

After hacking /usr/share/perl5/Dpkg/Shlibs/Objdump.pm:462 to read
"defined => ($sect ne '*UND*') && ($sect ne '.bss')"
(maybe not the right solution, just for demonstration):

$ dpkg-shlibdeps ./debian/cppcheck/usr/bin/cppcheck; cat debian/substvars
shlibs:Depends=libc6 (>= 2.32), [...]

(Not really sure about the severity. I believe the resulting bugs in packagage 
using dpkg-shlipdeps are "serious".)

Best regards,
  Joachim

-- Package-specific info:
System tainted due to merged-usr-via-aliased-dirs.

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

Kernel: Linux 5.10.0-9-amd64 (SMP w/16 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages dpkg-dev depends on:
ii  binutils  2.35.2-2
ii  bzip2 1.0.8-4
ii  libdpkg-perl  1.20.9
ii  make  4.3-4.1
ii  patch 2.7.6-7
ii  perl  5.32.1-4+deb11u2
ii  tar   1.34+dfsg-1
ii  xz-utils  5.2.5-2

Versions of packages dpkg-dev recommends:
ii  build-essential  12.9
ii  clang-11 [c-compiler]1:11.0.1-2
ii  fakeroot 1.25.3-1.1
ii  gcc [c-compiler] 4:10.2.1-1
ii  gcc-10 [c-compiler]  10.2.1-6
ii  gnupg2.2.27-2
ii  gpgv 2.2.27-2
ii  libalgorithm-merge-perl  0.08-3

Versions of packages dpkg-dev suggests:
ii  debian-keyring  2021.07.26

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: dpkg
Source-Version: 1.20.12
Done: Guillem Jover 

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

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

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

Debian distribution maintenance software
pp.
Guillem Jover  (supplier of updated dpkg package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Thu, 01 Sep 2022 05:38:12 +0200
Source: dpkg
Architecture: source
Version: 1.20.12
Distribution: bullseye
Urgency: medium
Maintainer: Dpkg Developers 
Changed-By: Guillem Jover 
Closes: 980963 991190 995387 1000421 1008316 1008478 1008764
Changes:
 dpkg (1.20.12) 

Bug#919697: arcanist: file conflict with arc

[Christoph Biedl]

Guillem Jover wrote...

> On Fri, 2022-09-02 at 12:12:06 +0200, Christoph Biedl wrote:
> > Sylvestre Ledru wrote...
> > > I don't think renaming is the right approach against an MS-DOS
> > > software (and I still think that Debian's policy is too binary for
> > > this).
> >
> > As there is a very small chance users would want to install *both*
> > packages, can't we just resolve this with a Breaks: on both sides, or
> > anything else that prevents co-installation from happening?
>
> See Adrian's reply.



On the plus side, I understand Sylvestre's statement now.

> I think this would make the program match the package name, and at the
> same time make it possible for willing users to simply modify their
> pathname or add a symlink say under ~/bin/arc pointing to the actual
> program.

Haven't fully decided on this yet, but I tend to stop shipping the symlink. And
while on it, handle the collision on /usr/share/man/man1/arc.1.gz as well.

> I can take a stab at this (as gratitude :), and propose a patch during
> the weekend or something, if you want.

Thanks for your offer and all the other kind words. Still I guess this
creates more work for you than for me, as I have more things to do for
this package anyway. Therefore I can take care of this particular story
en passant.

Regards,

Christoph


signature.asc
Description: PGP signature

Processed: Working on phabricator

[Debian Bug Tracking System]

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

> tags 919697 pending
Bug #919697 [arcanist] arcanist: file conflict with arc
Bug #930722 [arcanist] arc, arcanist: Both ship arc binary
Added tag(s) pending.
Added tag(s) pending.
> tags 1003463 pending
Bug #1003463 [arcanist] Functionally broken with current PHP
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#1018717: orage: extra informations

[WhilelM]

Package: orage
Version: 4.16.0-1
Followup-For: Bug #1018717

Get to reproduce same bug from unstable (instance upgrade from bullseye).

Here a gdb output:
(gdb) bt
#0  0x in ?? ()
#1  0x7711f5f6 in g_hash_table_lookup () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x77d10b90 in gdk_x11_atom_to_xatom_for_display () from 
/lib/x86_64-linux-gnu/libgdk-3.so.0
#3  0x555654db in ?? ()
#4  0x76e2920a in __libc_start_call_main 
(main=main@entry=0x55565480, argc=argc@entry=1, 
argv=argv@entry=0x7fffe258)
at ../sysdeps/nptl/libc_start_call_main.h:58
#5  0x76e292bc in __libc_start_main_impl (main=0x55565480, argc=1, 
argv=0x7fffe258, init=, 
fini=, rtld_fini=, stack_end=0x7fffe248) 
at ../csu/libc-start.c:389
#6  0x555656ba in ?? ()

The original bug was obtained with the unstable executable of orage under a 
bullseye installation.
The desktop for both is a default Gnome one (Wayland).

Feel free to ask for more informations

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

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

Versions of packages orage depends on:
ii  libc62.34-7
ii  libcairo21.16.0-6
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.73.3-3
ii  libgtk-3-0   3.24.34-3
ii  libical3 3.0.14-1+b1
ii  libnotify4   0.8.1-1
ii  libpango-1.0-0   1.50.9+ds-1
ii  libpangocairo-1.0-0  1.50.9+ds-1
ii  libx11-6 2:1.8.1-2
ii  libxfce4panel-2.0-4  4.16.5-1
ii  libxfce4ui-2-0   4.16.1-1
ii  libxfce4util74.16.0-1
ii  orage-data   4.16.0-1

Versions of packages orage recommends:
ii  dbus-user-session [default-dbus-session-bus]  1.14.0-2
ii  dbus-x11 [dbus-session-bus]   1.14.0-2

Versions of packages orage suggests:
pn  sox  

-- no debconf information

Bug#1019051: ffmpeg: Repackaging with pipewire: dpkg-shlibdeps: error: no dependency information found for libjack.so.0 used by libavdevice.so.59.7.100

[Braiam Peguero]

Package: ffmpeg
Version: 7:5.1-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)

Dear Maintainer,

Repackaging FFMPEG on a Pipewire enabled host, while fulfilling
all dependencies fails on the shlibdeps step with the following message:

set -e && for pkg in libavcodec-extra59 libavfilter-extra8 libavformat-extra59; 
do \
mainpkg=`echo $pkg | sed 's/-extra//'`; \
cp -f debian/$mainpkg.symbols debian/$pkg.symbols; \
dh_shlibdeps -p$pkg; \
rm -f debian/$pkg.symbols; \
done
dh_shlibdeps --remaining-packages
dpkg-shlibdeps: error: no dependency information found for 
/usr/lib/x86_64-linux-gnu/pipewire-0.3/jack/libjack.so.0 (used by 
debian/libavdevice59/usr/lib/x86_64-linux-gnu/libavdevice.so.59.7.100)
Hint: check if the library actually comes from a package.
dh_shlibdeps: error: dpkg-shlibdeps -Tdebian/libavdevice59.substvars 
debian/libavdevice59/usr/lib/x86_64-linux-gnu/libavdevice.so.59.7.100 returned 
exit code 25
dh_shlibdeps: error: Aborting due to earlier error


I'm unsure if ffmpeg dependencies needs to be more tighter wtr jack
or if a change should be done to pipewire so that it correctly
declares the shared library.

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

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

Versions of packages ffmpeg depends on:
ii  libavcodec597:5.1-3
ii  libavdevice59   7:5.1-3
ii  libavfilter87:5.1-3
ii  libavformat59   7:5.1-3
ii  libavutil57 7:5.1-3
ii  libc6   2.34-4
ii  libpostproc56   7:5.1-3
ii  libsdl2-2.0-0   2.24.0+dfsg-1
ii  libswresample4  7:5.1-3
ii  libswscale6 7:5.1-3

ffmpeg recommends no packages.

Versions of packages ffmpeg suggests:
pn  ffmpeg-doc  

-- no debconf information

Bug#1019050: libsuperlu-dist-dev: postrm failure

[Adrian Bunk]

Package: libsuperlu-dist-dev
Version: 8.1.0+dfsg1-2
Severity: serious

https://piuparts.debian.org/sid/fail/libsuperlu-dist-dev_8.1.0+dfsg1-2.log

...
  Removing libsuperlu-dist-dev:amd64 (8.1.0+dfsg1-2) ...
  rmdir: failed to remove '/usr/lib/x86_64-linux-gnu/fortran/gfortran': No such 
file or directory
  dpkg: error processing package libsuperlu-dist-dev:amd64 (--remove):
   installed libsuperlu-dist-dev:amd64 package post-removal script subprocess 
returned error exit status 1

Bug#1018867: luajit2: stop building on ppc64el

[Paul Gevers]

Hi all,

On Thu, 01 Sep 2022 09:31:33 +0200 Paul Gevers  wrote:

If you can't (or don't want to) do this soon, I'll upload luajit2 with
only ppc64el dropped from the Architectures field (well, convert `any`
to the list where it builds). Please let me know if you want me to do
that.


I have uploaded the attached debdiff to DELAYED/5.

Paul
diff -Nru luajit2-2.1-20220411/debian/changelog 
luajit2-2.1-20220411/debian/changelog
--- luajit2-2.1-20220411/debian/changelog   2022-06-08 15:57:03.0 
+0200
+++ luajit2-2.1-20220411/debian/changelog   2022-09-03 13:17:37.0 
+0200
@@ -1,3 +1,12 @@
+luajit2 (2.1-20220411-5.1) unstable; urgency=medium
+
+  * Non-maintainer upload
+
+  [ Mo Zhou ]
+  * No longer build on ppc64el.
+
+ -- Paul Gevers   Sat, 03 Sep 2022 13:17:37 +0200
+
 luajit2 (2.1-20220411-5) unstable; urgency=medium
 
   * No Conflicts+Replaces against src:luajit on IBM Architectures.
diff -Nru luajit2-2.1-20220411/debian/control 
luajit2-2.1-20220411/debian/control
--- luajit2-2.1-20220411/debian/control 2022-06-08 15:55:25.0 +0200
+++ luajit2-2.1-20220411/debian/control 2022-09-03 13:17:37.0 +0200
@@ -10,7 +10,7 @@
 Build-Depends: debhelper-compat (= 13)
 
 Package: luajit2
-Architecture: any
+Architecture: amd64 arm64 armel armhf i386 mips64el mipsel s390x
 Multi-Arch: foreign
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libluajit2-5.1-2 (= ${binary:Version}),
@@ -39,7 +39,7 @@
  by its embeddable (i.e. library) version.
 
 Package: libluajit2-5.1-2
-Architecture: any
+Architecture: amd64 arm64 armel armhf i386 mips64el mipsel s390x
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
 Depends: libluajit2-5.1-common (= ${source:Version}),
@@ -60,7 +60,7 @@
 Section: libdevel
 Multi-Arch: same
 Pre-Depends: ${misc:Pre-Depends}
-Architecture: any 
+Architecture: amd64 arm64 armel armhf i386 mips64el mipsel s390x
 Depends: libluajit2-5.1-2 (= ${binary:Version}),
  ${misc:Depends},
  ${shlibs:Depends}


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1014100: marked as done (qiime: autopkgtest needs update for new version of python-decorator)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 11:05:00 +
with message-id 
and subject line Bug#1014100: fixed in qiime 2022.8.1-1
has caused the Debian Bug report #1014100,
regarding qiime: autopkgtest needs update for new version of python-decorator
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.)


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

Source: qiime
Version: 2021.8.0-2
Severity: serious
X-Debbugs-CC: python-decora...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:python-decorator

Dear maintainer(s),

With a recent upload of python-decorator the autopkgtest of qiime fails 
in testing when that autopkgtest is run with the binary packages of 
python-decorator from unstable. It passes when run with only packages 
from testing. In tabular form:


   passfail
python-decorator   from testing5.1.1-2
qiime  from testing2021.8.0-2
all others from testingfrom testing

I copied some of the output at the bottom of this report.

Currently this regression is blocking the migration of python-decorator 
to testing [1]. Of course, python-decorator shouldn't just break your 
autopkgtest (or even worse, your package), but it seems to me that the 
change in python-decorator was intended and your package needs to update 
to the new situation. To me it looks like the references need updating 
for the new version but I might be wrong.


If this is a real problem in your package (and not only in your 
autopkgtest), the right binary package(s) from python-decorator should 
really add a versioned Breaks on the unfixed version of (one of your) 
package(s). Note: the Breaks is nice even if the issue is only in the 
autopkgtest as it helps the migration software to figure out the right 
versions to combine in the tests.


More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation

Paul

[1] https://qa.debian.org/excuses.php?package=python-decorator

https://ci.debian.net/data/autopkgtest/testing/amd64/q/qiime/23173367/log.gz

FF.FFF..
==
FAIL: test_callable_and_async_signature_with_artifacts_and_parameters 
(qiime2.sdk.tests.test_method.TestMethod)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py", 
line 223, in test_callable_and_async_signature_with_artifacts_and_parameters

self.assertEqual(parameters, exp_parameters)
AssertionError: Lists differ: [('in[20 chars]ts1: list">), ('ints2', 
)] != [('in[20 chars]ts1: 
IntSequence1 | IntSequence2">), ('ints2',[147 chars]t">)]


First differing element 0:
('ints1', )
('ints1', )

Diff is 735 characters long. Set self.maxDiff to None to see it.

==
FAIL: test_callable_and_async_signature_with_no_parameters 
(qiime2.sdk.tests.test_method.TestMethod)

--
Traceback (most recent call last):
  File 
"/tmp/autopkgtest-lxc.t_q3d0jx/downtmp/autopkgtest_tmp/qiime2/sdk/tests/test_method.py", 
line 242, in test_callable_and_async_signature_with_no_parameters

self.assertEqual(parameters, exp_parameters)
AssertionError: Lists differ: [('ma[26 chars]ng1: dict">), ('mapping2', 
)] != [('ma[26 chars]ng1: 

Bug#1018017: marked as done (ukui-greeter: FTBFS in unstable)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 09:12:03 +
with message-id 
and subject line Bug#1018017: fixed in ukui-greeter 3.0.3.1-1
has caused the Debian Bug report #1018017,
regarding ukui-greeter: FTBFS in unstable
to be marked as done.

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

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


-- 
1018017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ukui-greeter
Version: 3.0.3-1
Severity: serious
X-Debbugs-Cc: a...@debian.org

Dear maintainer,

ukui-greeter currently fails to build from source in unstable.

BiometricAuth/giodbus.cpp:22:10: fatal error: gio-unix-2.0/gio/gunixfdlist.h: 
No such file or directory
   22 | #include 
  |  ^~~~
compilation terminated.

If you fix this problem, please also check if the new version of
imlib2 in experimental works for you. I intend to upload it in one or
two months.

Regards,

Markus


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

Kernel: Linux 5.10.0-17-amd64 (SMP w/8 CPU threads)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ukui-greeter depends on:
ii  libc6   2.31-13+deb11u3
ii  libgcc-s1 [libgcc1] 10.2.1-6
ii  libgl1  1.3.2-1
ii  libglib2.0-02.66.8-1
pn  libimlib2   
pn  liblightdm-qt5-3-0  
pn  libopencv-core406   
pn  libopencv-imgcodecs406  
pn  libopencv-imgproc406
ii  libqt5core5a5.15.2+dfsg-9
ii  libqt5dbus5 5.15.2+dfsg-9
ii  libqt5gui5  5.15.2+dfsg-9
ii  libqt5svg5  5.15.2-3
ii  libqt5widgets5  5.15.2+dfsg-9
ii  libqt5x11extras55.15.2-2
ii  libstdc++6  10.2.1-6
ii  libx11-62:1.7.2-1
ii  libxi6  2:1.7.10-1
ii  libxrandr2  2:1.5.1-1
ii  libxtst62:1.2.3-1

ukui-greeter recommends no packages.

Versions of packages ukui-greeter suggests:
pn  biometric-auth  
--- End Message ---
--- Begin Message ---
Source: ukui-greeter
Source-Version: 3.0.3.1-1
Done: handsome_feng 

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

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated ukui-greeter 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sat, 03 Sep 2022 15:53:06 +0800
Source: ukui-greeter
Architecture: source
Version: 3.0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Closes: 1018017
Changes:
 ukui-greeter (3.0.3.1-1) unstable; urgency=medium
 .
   * Change the gunixfdlist header path. (Closes: 1018017)
Checksums-Sha1:
 86c0c723f6e45aad65472c6fc4e243e13cc801c7 2150 ukui-greeter_3.0.3.1-1.dsc
 a24ea3d5a4b3339e31c72381222b7fb23e769e11 715539 
ukui-greeter_3.0.3.1.orig.tar.gz
 dc3f24bfb2c623a1c04e98b1da2dc4dbe0b4af7e 2772 
ukui-greeter_3.0.3.1-1.debian.tar.xz
 ef7873abf76bb04f9321f99bfe9d471137af99ca 20973 
ukui-greeter_3.0.3.1-1_source.buildinfo
Checksums-Sha256:
 3b6ea2f729eabb49e80ce935cf2d058009aeaad47d58296464f131b70dae6080 2150 
ukui-greeter_3.0.3.1-1.dsc
 2c2bbb3931243b83e0d379568df8beaf9c8d5633d4b69d7a045d6dbe9012ea5b 715539 
ukui-greeter_3.0.3.1.orig.tar.gz
 54607f13073da6da3fef3497344d4439fdc05a6a5ac8dfeaf565654b25ecce8a 2772 
ukui-greeter_3.0.3.1-1.debian.tar.xz
 446f079742bd7b42a58fc0bb7638f739bbd8e489fef9a58c5132a0a8e518d430 20973 
ukui-greeter_3.0.3.1-1_source.buildinfo
Files:
 8be2078f06a375e51f388af599283d5b 2150 x11 optional ukui-greeter_3.0.3.1-1.dsc
 de87b7ef4d5cb471080a73f759501821 715539 x11 optional 
ukui-greeter_3.0.3.1.orig.tar.gz
 195744efea1c815c51496ba1979bb5bc 2772 x11 optional 
ukui-greeter_3.0.3.1-1.debian.tar.xz
 72458c8428150195f7365d1c7734fae5 20973 x11 optional 
ukui-greeter_3.0.3.1-1_source.buildinfo

Bug#694320: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id 
and subject line closing again with source package version
has caused the Debian Bug report #694321,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)


-- 
694321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308

This package include copyrighted font hinting from adobe. 

For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10  adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug  2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright:  Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright:  2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments

--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[  {}
 {}
 {}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known

Thanks
--- End Message ---
--- Begin Message ---
Version: 20200910-2

Once again without the epoch. Does the BTS track source or binary
package versions?

 - Fabian



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

Bug#694321: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id 
and subject line closing again with source package version
has caused the Debian Bug report #694321,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)


-- 
694321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694321
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308

This package include copyrighted font hinting from adobe. 

For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10  adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug  2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright:  Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright:  2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments

--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[  {}
 {}
 {}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known

Thanks
--- End Message ---
--- Begin Message ---
Version: 20200910-2

Once again without the epoch. Does the BTS track source or binary
package versions?

 - Fabian



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

Bug#694321: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id 
and subject line closing again with source package version
has caused the Debian Bug report #694320,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)


-- 
694320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308

This package include copyrighted font hinting from adobe. 

For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10  adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug  2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright:  Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright:  2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments

--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[  {}
 {}
 {}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known

Thanks
--- End Message ---
--- Begin Message ---
Version: 20200910-2

Once again without the epoch. Does the BTS track source or binary
package versions?

 - Fabian



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

Bug#694320: marked as done ([gsfonts] Fonts include copyrighted adobe fragment all right reserved)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 10:56:41 +0200
with message-id 
and subject line closing again with source package version
has caused the Debian Bug report #694320,
regarding [gsfonts] Fonts include copyrighted adobe fragment all right reserved
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.)


-- 
694320: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694320
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gsfonts
Version: 1:8.11+urwcyr1.0.7~pre44-4.2
Severity: serious
control: block -1 by 694308

This package include copyrighted font hinting from adobe. 

For instance
t1disasm /usr/share/fonts/type1/gsfonts/n019024l.pfb | grep -i -A 10  adobe
%!PS-AdobeFont-1.0: NimbusSanL-BoldItal 1.06
%%Title: NimbusSanL-BoldItal
%Version: 1.06
%%CreationDate: Thu Aug  2 14:36:47 2007
%%Creator: frob
%Copyright: Copyright (URW)++,Copyright 1999 by (URW)++ Design &
%Copyright:  Development; Cyrillic glyphs added by Valek Filippov (C)
%Copyright:  2001-2005
% Generated by FontForge 20070723 (http://fontforge.sf.net/)
%%EndComments

--
% Copyright (c) 1987-1990 Adobe Systems Incorporated.
% All Rights Reserved.
% This code to be used for Flex and hint replacement.
% Version 1.1
[  {}
 {}
 {}
{systemdict /internaldict known not
{pop 3}
{1183615869 systemdict /internaldict get exec
dup /startlock known

Thanks
--- End Message ---
--- Begin Message ---
Version: 20200910-2

Once again without the epoch. Does the BTS track source or binary
package versions?

 - Fabian



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

Bug#1013461: marked as done (kylin-video FTBFS with ffmpeg 5.0.1)

[Debian Bug Tracking System]

Your message dated Sat, 03 Sep 2022 07:19:29 +
with message-id 
and subject line Bug#1013461: fixed in kylin-video 3.1.3-3
has caused the Debian Bug report #1013461,
regarding kylin-video FTBFS with ffmpeg 5.0.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.)


-- 
1013461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kylin-video
Version: 3.1.3-2
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/logs.php?pkg=kylin-video=3.1.3-2%2Bb1

...
ffutil.cpp: In constructor ‘FFUtil::FFUtil(QObject*)’:
ffutil.cpp:47:5: error: ‘av_register_all’ was not declared in this scope
   47 | av_register_all();
  | ^~~
ffutil.cpp: In member function ‘int FFUtil::open(QString)’:
ffutil.cpp:99:42: error: invalid conversion from ‘const AVCodec*’ to ‘AVCodec*’ 
[-fpermissive]
   99 | pCodec = 
avcodec_find_decoder_by_name(avcodec_get_name(pFormatCtx->streams[videoStream]->codecpar->codec_id));
  |  
^~~~
  |  |
  |  const AVCodec*
ffutil.cpp:101:38: error: invalid conversion from ‘const AVCodec*’ to 
‘AVCodec*’ [-fpermissive]
  101 | pCodec = 
avcodec_find_decoder(pFormatCtx->streams[videoStream]->codecpar->codec_id);
  |  
^~
  |  |
  |  const AVCodec*
ffutil.cpp: In member function ‘void FFUtil::saveIFrame(QString)’:
ffutil.cpp:163:12: warning: ‘void QProcess::start(const QString&, 
QIODevice::OpenMode)’ is deprecated: Use QProcess::start(const QString 
, const QStringList ,OpenMode mode = ReadWrite) instead 
[-Wdeprecated-declarations]
  163 | p.start(QString("ffmpegthumbnailer -i %1 -o %2").arg("\"" + 
m_fileName + "\"").arg(_savePath));
  | 
~~~^~~
In file included from /usr/include/x86_64-linux-gnu/qt5/QtCore/QProcess:1,
 from ffutil.cpp:26:
/usr/include/x86_64-linux-gnu/qt5/QtCore/qprocess.h:168:10: note: declared here
  168 | void start(const QString , OpenMode mode = ReadWrite);
  |  ^
ffutil.cpp:184:19: error: ‘avpicture_get_size’ was not declared in this scope
  184 | numBytes= avpicture_get_size(AV_PIX_FMT_RGB32, 
pCodecCtx->width,pCodecCtx->height);
  |   ^~
ffutil.cpp:187:21: error: ‘AVPicture’ was not declared in this scope; did you 
mean ‘QPicture’?
  187 | avpicture_fill((AVPicture *) pFrameRGB, outBuffer, 
AV_PIX_FMT_RGB32, pCodecCtx->width, pCodecCtx->height);
  | ^
  | QPicture
ffutil.cpp:187:32: error: expected primary-expression before ‘)’ token
  187 | avpicture_fill((AVPicture *) pFrameRGB, outBuffer, 
AV_PIX_FMT_RGB32, pCodecCtx->width, pCodecCtx->height);
  |^
ffutil.cpp:187:5: error: ‘avpicture_fill’ was not declared in this scope
  187 | avpicture_fill((AVPicture *) pFrameRGB, outBuffer, 
AV_PIX_FMT_RGB32, pCodecCtx->width, pCodecCtx->height);
  | ^~
ffutil.cpp:190:19: warning: ‘void av_init_packet(AVPacket*)’ is deprecated 
[-Wdeprecated-declarations]
  190 | av_init_packet(packet);
  | ~~^~~~
In file included from /usr/include/x86_64-linux-gnu/libavformat/avformat.h:316,
 from ffutil.cpp:34:
/usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
  506 | void av_init_packet(AVPacket *pkt);
  |  ^~
make[3]: *** [Makefile:1389: ffutil.o] Error 1
--- End Message ---
--- Begin Message ---
Source: kylin-video
Source-Version: 3.1.3-3
Done: handsome_feng 

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

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated kylin-video 
package)

(This message was generated automatically at their 

Processed: src:missingh: fails to migrate to testing for too long: part of unfinshed ghc transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 1.5.0.1-1
Bug #1019003 [src:missingh] src:missingh: fails to migrate to testing for too 
long: part of unfinshed ghc transition
Marked as fixed in versions missingh/1.5.0.1-1.
Bug #1019003 [src:missingh] src:missingh: fails to migrate to testing for too 
long: part of unfinshed ghc transition
Marked Bug as done

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

Bug#1019003: src:missingh: fails to migrate to testing for too long: part of unfinshed ghc transition

[Paul Gevers]

Source: missingh
Version: 1.4.3.0-2
Severity: serious
Control: close -1 1.5.0.1-1
Tags: sid bookworm
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:missingh has been trying to migrate for 61 
days [2]. Hence, I am filing this bug. Your package is part of the 
unfinished ghc transition.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=missingh



OpenPGP_signature
Description: OpenPGP digital signature

Processed: src:ldap-haskell: fails to migrate to testing for too long: part of unfinshed ghc transition

[Debian Bug Tracking System]

Processing control commands:

> close -1 0.6.11-6
Bug #1019002 [src:ldap-haskell] src:ldap-haskell: fails to migrate to testing 
for too long: part of unfinshed ghc transition
Marked as fixed in versions ldap-haskell/0.6.11-6.
Bug #1019002 [src:ldap-haskell] src:ldap-haskell: fails to migrate to testing 
for too long: part of unfinshed ghc transition
Marked Bug as done

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

Bug#1019002: src:ldap-haskell: fails to migrate to testing for too long: part of unfinshed ghc transition

[Paul Gevers]

Source: ldap-haskell
Version: 0.6.11-4
Severity: serious
Control: close -1 0.6.11-6
Tags: sid bookworm
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 60 days as having a Release Critical bug in 
testing [1]. Your package src:ldap-haskell has been trying to migrate 
for 62 days [2]. Hence, I am filing this bug. Your package is part of 
the unfinished ghc transition.


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 bookworm, 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/2020/02/msg5.html
[2] https://qa.debian.org/excuses.php?package=ldap-haskell



OpenPGP_signature
Description: OpenPGP digital signature