Bug#1055060: marked as done (wxwidgets3.2: accessing network during dh_auto_test)

[Debian Bug Tracking System]

Your message dated Tue, 31 Oct 2023 03:04:39 +
with message-id 
and subject line Bug#1055060: fixed in wxwidgets3.2 3.2.3+dfsg-3
has caused the Debian Bug report #1055060,
regarding wxwidgets3.2: accessing network during dh_auto_test
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.)


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

Source: wxwidgets3.2
Version: 3.2.3+dfsg-2
Severity: serious

Hello, looks like the code is trying to reach some external websites during 
dh_auto_test.

Look e.g. at the Ubuntu build log

/usr/bin/ld: /tmp/cc6Gj1qH.ltrans32.ltrans.o: in function 
`C_A_T_C_HT_E_S_T41()':
/<>/tests/./filename/filenametest.cpp:797:(.text+0x4406): warning: 
the use of `tempnam' is dangerous, better use `mkstemp'
make[2]: Leaving directory '/<>/tests'
cd tests && ./test ~[.]
Test program for wxWidgets non-GUI features
build: 3.2 (wchar_t,compiler with C++ ABI compatible with gcc 4,wx 
containers,compatible with 3.0)
compiled using gcc 13.2
running under Linux 5.4.0-164-generic x86_64 as buildd

~~~
test is a Catch v1.12.2 host application.
Run with -? for options

---
URLTestCase
  GetInputStream
---
./uris/url.cpp:37
...

./uris/url.cpp:68:
warning:
  No network connectivity; skipping the URLTestCase::GetInputStream test unit.

---
WebRequest::Get::Bytes
---
./net/webrequest.cpp:181
...

./net/webrequest.cpp:149:
warning:
  Error: Could not resolve host: nghttp2.org

./net/webrequest.cpp:152: FAILED:
  REQUIRE( stateFromEvent == requiredState )
with expansion:
  4 == 3

---
WebRequest::Get::Simple
---
./net/webrequest.cpp:194
...

./net/webrequest.cpp:217: FAILED:
  CHECK( request.GetState() == wxWebRequest::State_Completed )
with expansion:
  4 == 3

./net/webrequest.cpp:218: FAILED:
  CHECK( request.GetResponse().GetStatus() == 200 )
with expansion:
  0 == 200

---
WebRequest::Get::String
---
./net/webrequest.cpp:221
...

./net/webrequest.cpp:149:
warning:
  Error: Could not resolve host: nghttp2.org

./net/webrequest.cpp:152: FAILED:
  REQUIRE( stateFromEvent == requiredState )
with expansion:
  4 == 3

---
WebRequest::Get::Header
---
./net/webrequest.cpp:232
...

./net/webrequest.cpp:149:
warning:
  Error: Could not resolve host: nghttp2.org

./net/webrequest.cpp:152: FAILED:
  REQUIRE( stateFromEvent == requiredState )
with expansion:
  4 == 3

---
WebRequest::Get::Param
---
./net/webrequest.cpp:243
...

./net/webrequest.cpp:149:
warning:
  Error: Could not resolve host: nghttp2.org

./net/webrequest.cpp:152: FAILED:
  REQUIRE( stateFromEvent == requiredState )
with expansion:
  4 == 3

---
WebRequest::Get::File
---
./net/webrequest.cpp:271
...

./net/webrequest.cpp:149:
warning:
  Error: Could not resolve host: nghttp2.org

./net/webrequest.cpp:152: FAILED:
  REQUIRE( stateFromEvent == requiredState )
with expansion:
  4 == 3

Bug#1054292: marked as done (gpsim: Build-Depends unnecessarily on gtkextra)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 23:19:24 +
with message-id 
and subject line Bug#1054292: fixed in gpsim 0.31.0-2.1
has caused the Debian Bug report #1054292,
regarding gpsim: Build-Depends unnecessarily on gtkextra
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.)


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

Source: gpsim
Version: 0.31.0-2
Control: unblock 967489 by 967454

Please drop the unnecessary build dependency libgtkextra-dev.
--- End Message ---
--- Begin Message ---
Source: gpsim
Source-Version: 0.31.0-2.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated gpsim 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, 21 Oct 2023 00:06:02 +0200
Source: gpsim
Architecture: source
Version: 0.31.0-2.1
Distribution: unstable
Urgency: medium
Maintainer: Georges Khaznadar 
Changed-By: Bastian Germann 
Closes: 1054292
Changes:
 gpsim (0.31.0-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop unnecessary Build-Depends: quilt, libgtkextra-dev. Closes: #1054292
Checksums-Sha1:
 e7ab2ec29aebe68e5adf30dc400e3029fbb24435 1831 gpsim_0.31.0-2.1.dsc
 3d073ecefad4209b70d7163ba6b485197aedf924 10132 gpsim_0.31.0-2.1.debian.tar.xz
 e418b2d1b737d4769214f769b093f18ffed17e3b 11447 
gpsim_0.31.0-2.1_source.buildinfo
Checksums-Sha256:
 0ac08bb77c54c13cd318b601505f1f2d004caf8cf797a0dbcf5aa81bd0c6ebe4 1831 
gpsim_0.31.0-2.1.dsc
 4fa1f5e0d72623b69f2268d4aa655bad8fa3c5571b0b173064f7ce0dd7b52ba8 10132 
gpsim_0.31.0-2.1.debian.tar.xz
 e1a86d4259c9b4fed49f3f3e58550e7549290971592b08c6468e07893d997136 11447 
gpsim_0.31.0-2.1_source.buildinfo
Files:
 6de4aa297ac4c0b6a910ed9a1dd125ad 1831 electronics optional gpsim_0.31.0-2.1.dsc
 764136364a41b2801ba2ae0a7c75fc38 10132 electronics optional 
gpsim_0.31.0-2.1.debian.tar.xz
 14dee40bd9a5a4279a342942d8a0bbb2 11447 electronics optional 
gpsim_0.31.0-2.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUy/MQQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHJEDADS/NkuMGo1AfUYRK+0+1LqnqxPSJ7B0PQe
Ar0UH80gaUxA5RV7QWiNK2P9dzoPR6lISVz0IzgvY3ngWAWpk1Clk0QCVlxeY2NF
t4cbrfG0TQ7b3q4YoCr1HmuqnqhoA8bYUTt0nbb+UuLh1VH62RRvrawDYIAUlgIJ
3m2O9KKL9mpVhGuKRCjLbp/wbTwDwb80oJD1nT+B3TvCnFDyjZzeh4ugow9u9N2H
EvPNPdLiEoD3R1AywuvDvcLgsgzM9gWuAHLVwYvgKlK2bICNUVwVbWQKhsIXxbD9
WwEMeFbAJJm+5TXTWlyScbP0X2GwzSBptvN/GABNx/g5aKVY+RM55ZrWK+NzNQFi
5To128H3OmnJ/0IAxoyFTharNXJe9v4nRwR7XAiXZHEAZnRtP6883YVWTtI0FtK1
kUoMBZEELbMFPel250nS0dPt72Qnmz0UbWl4ygmVAUkPjhdIanr/6R+iFVV3PsUD
Q8ylWuvM4tmVxM3SbGmJAh6BdGPgsQM=
=+9Qr
-END PGP SIGNATURE End Message ---

Bug#967874: marked as done (libgnomecanvas: depends on deprecated libglade2)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 22:35:04 +
with message-id 
and subject line Bug#967874: fixed in libgnomecanvas 2.30.3-4.1
has caused the Debian Bug report #967874,
regarding libgnomecanvas: depends on deprecated libglade2
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.)


-- 
967874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967874
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgnomecanvas
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: libglade oldlibs
Control: block 895517 by -1

This package has Build-Depends on libglade2-dev or produces binary
packages with a Depends on libglade2-0.

libglade was superseded by GtkBuilder in GTK 2.12, released in 2007.
Moving from libglade to GtkBuilder would be a good first step towards
replacing GTK 2 with GTK 3.

A porting guide is provided in the GTK 2 documentation:
https://developer.gnome.org/gtk2/stable/gtk-migrating-GtkBuilder.html

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: libgnomecanvas
Source-Version: 2.30.3-4.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated libgnomecanvas 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: Fri, 20 Oct 2023 22:44:18 +0200
Source: libgnomecanvas
Architecture: source
Version: 2.30.3-4.1
Distribution: unstable
Urgency: medium
Maintainer: Adrian Bunk 
Changed-By: Bastian Germann 
Closes: 967874
Changes:
 libgnomecanvas (2.30.3-4.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Drop glade support. (Closes: #967874)
Checksums-Sha1:
 fb02641367b2bb8fbfac6a10a5313a9b48227906 2064 libgnomecanvas_2.30.3-4.1.dsc
 0eea7b16647a42ec3433b0c20b5b36d090f363c0 7108 
libgnomecanvas_2.30.3-4.1.debian.tar.xz
 1dc2cd346201c3edf66b96094003ed6390440e58 13741 
libgnomecanvas_2.30.3-4.1_source.buildinfo
Checksums-Sha256:
 fdb5d1508c80b116fbf49093a90a7f5ccea28c9e7bf9e1fc46c6d61795bbd31b 2064 
libgnomecanvas_2.30.3-4.1.dsc
 6ab5d05081b60c84cd5465afdadaac5e965cc8f9476eeb98e2300dccfd0ee2fb 7108 
libgnomecanvas_2.30.3-4.1.debian.tar.xz
 1f1a93ed980a11dec994372f992e7c3dcf899cb26bf945166198575dc626d91a 13741 
libgnomecanvas_2.30.3-4.1_source.buildinfo
Files:
 d0834db84a177c4955668a417de9bb9c 2064 oldlibs optional 
libgnomecanvas_2.30.3-4.1.dsc
 98d27efa871169c4c4ea14ded8d6105e 7108 oldlibs optional 
libgnomecanvas_2.30.3-4.1.debian.tar.xz
 8e0b4c76d7826374334adbb541dd81a2 13741 oldlibs optional 
libgnomecanvas_2.30.3-4.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUy6jYQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFAj3DADLJeSChgMmnr6mz7K1ZAS+ZgXskRpewxJO
tcJZl5VpQmMwKVB/+C8oRBM+42vNHHHEz7ZovXVkdq7VVtjTpdp13k8yrYdypnNw
AZ82XOy+LuFJlZlZHX83J1DOir+eAa2TlCfpf1Bid7XaI7z6gdG+9ltvNx7DdEUV
hyWMHB9eMQcy4XC2fY1/6NngYuv4Q+Mtk0K9a4W3zQ1gyCKIHAwSOxOsiJt+zEPB
qs2nEbJZqMxeQFFviItM2FiA21YBYlJsAcq6ojc/ueU4dwhzOlSt1sQgmbScmliB
1D1PmlVxfSYFUrv4I0t04w3DDO45vw5diN1LClJGjBRojK2WXYspZ73x2xi+9ld2
QS7WBzUAooTOToOf967cNZKFGmbcOSa5p3yHajaTICLuNPcYXrRfMbDLUBhpI1EN
5Ja31uGvrqevAt3HFtQNpQ8B3VkhEqVx6y/nlNEgV+aT4IpqqKL1WUKPOprz05J+
C1MrI2CH6oCXoa3oAlM0LfrJFO3suVY=
=Q/No
-END PGP SIGNATURE End Message ---

Bug#1054845: marked as done (golang-github-deanthompson-ginpprof: FTBFS: make: *** [debian/rules:4: build] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 22:34:55 +
with message-id 
and subject line Bug#1054845: fixed in golang-github-gin-gonic-gin 1.8.1-2
has caused the Debian Bug report #1054845,
regarding golang-github-deanthompson-ginpprof: FTBFS: make: *** 
[debian/rules:4: build] Error 25
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.)


-- 
1054845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: golang-github-deanthompson-ginpprof
Version: 0.0~git20201112.007b1e5-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules build
> dh build --buildsystem=golang --with=golang
>dh_update_autotools_config -O--buildsystem=golang
>dh_autoreconf -O--buildsystem=golang
>dh_auto_configure -O--buildsystem=golang
>dh_auto_build -O--buildsystem=golang
>   cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/DeanThompson/ginpprof github.com/DeanThompson/ginpprof/example
> src/github.com/gin-gonic/gin/gin.go:19:2: cannot find package 
> "golang.org/x/net/http2" in any of:
>   /usr/lib/go-1.21/src/golang.org/x/net/http2 (from $GOROOT)
>   /<>/obj-x86_64-linux-gnu/src/golang.org/x/net/http2 (from 
> $GOPATH)
> src/github.com/gin-gonic/gin/gin.go:20:2: cannot find package 
> "golang.org/x/net/http2/h2c" in any of:
>   /usr/lib/go-1.21/src/golang.org/x/net/http2/h2c (from $GOROOT)
>   /<>/obj-x86_64-linux-gnu/src/golang.org/x/net/http2/h2c 
> (from $GOPATH)
> dh_auto_build: error: cd obj-x86_64-linux-gnu && go install -trimpath -v -p 8 
> github.com/DeanThompson/ginpprof github.com/DeanThompson/ginpprof/example 
> returned exit code 1
> make: *** [debian/rules:4: build] Error 25


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/golang-github-deanthompson-ginpprof_0.0~git20201112.007b1e5-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: golang-github-gin-gonic-gin
Source-Version: 1.8.1-2
Done: Nilesh Patra 

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

Debian distribution maintenance software
pp.
Nilesh Patra  (supplier of updated 
golang-github-gin-gonic-gin 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: Tue, 31 Oct 2023 03:58:21 +0530
Source: golang-github-gin-gonic-gin
Architecture: source
Version: 1.8.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Go Packaging Team 
Changed-By: Nilesh Patra 
Closes: 1054845
Changes:
 golang-github-gin-gonic-gin (1.8.1-2) unstable; urgency=medium
 .
   * Team Upload.
   * Add golang-golang-x-net-dev to Depends (Closes: #1054845)
Checksums-Sha1:
 b1df04d232b7e8e2ef9e2824fadd9a3c95a5cd94 1957 
golang-github-gin-gonic-gin_1.8.1-2.dsc
 0cb35f1de3603961b64be9035ed233726d35048b 5512 
golang-github-gin-gonic-gin_1.8.1-2.debian.tar.xz
 dd37f5ecbb4eaa89df7e896e57ed2a70b847b89a 6446 
golang-github-gin-gonic-gin_1.8.1-2_amd64.buildinfo
Checksums-Sha256:
 b034d44980e1a4e1a94c7aa880f2cf62f287b8b3ebb0bb3dd93427f5f26f 1957 
golang-github-gin-gonic-gin_1.8.1-2.dsc
 d089da0fdc96d5a71f76e3845194ab3c03fc1e69e8058c2c442735bb18436ce8 

Bug#967725: marked as done (rfdump: depends on deprecated GTK 2)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 21:19:42 +
with message-id 
and subject line Bug#967725: fixed in rfdump 1.6-9.1
has caused the Debian Bug report #967725,
regarding rfdump: depends on deprecated GTK 2
to be marked as done.

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

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


-- 
967725: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967725
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rfdump
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1

This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.

GTK 2 was superseded by GTK 3 in 2011 (see
). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.

GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.

A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html

Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.

A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: rfdump
Source-Version: 1.6-9.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated rfdump 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: Fri, 20 Oct 2023 22:04:44 +0200
Source: rfdump
Architecture: source
Version: 1.6-9.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Bastian Germann 
Closes: 967725 967885
Changes:
 rfdump (1.6-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove libglade dependency, build with gtk3. (Closes: #967885, #967725)
Checksums-Sha1:
 0d1b523fdbe9ba2df1705ce67617003852ea5935 1764 rfdump_1.6-9.1.dsc
 35327da187442acc74833bc0907a6290977b1a88 13808 rfdump_1.6-9.1.debian.tar.xz
 fea9beaf316cef20dbc6bef92b3f38073374eef2 13835 rfdump_1.6-9.1_source.buildinfo
Checksums-Sha256:
 0021d62a318490aa5a8a99660e9e167cac74bd40e65a3b1be9a1abea428bdd97 1764 
rfdump_1.6-9.1.dsc
 fa786387b39b3fcaa5cdf4fa63e5879f3c09526caf7bec5527824268f0a9f0d7 13808 
rfdump_1.6-9.1.debian.tar.xz
 eda20743cb8ef61948be304de343d7105bc4bb2e5208911b7852a469c99b52b9 13835 
rfdump_1.6-9.1_source.buildinfo
Files:
 de44035029cd6c7aa413fe992e4f4bae 1764 electronics 

Bug#967885: marked as done (rfdump: depends on deprecated libglade2)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 21:19:42 +
with message-id 
and subject line Bug#967885: fixed in rfdump 1.6-9.1
has caused the Debian Bug report #967885,
regarding rfdump: depends on deprecated libglade2
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.)


-- 
967885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967885
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rfdump
Severity: normal
User: pkg-gnome-maintain...@lists.alioth.debian.org
Usertags: libglade oldlibs
Control: block 895517 by -1

This package has Build-Depends on libglade2-dev or produces binary
packages with a Depends on libglade2-0.

libglade was superseded by GtkBuilder in GTK 2.12, released in 2007.
Moving from libglade to GtkBuilder would be a good first step towards
replacing GTK 2 with GTK 3.

A porting guide is provided in the GTK 2 documentation:
https://developer.gnome.org/gtk2/stable/gtk-migrating-GtkBuilder.html

Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: rfdump
Source-Version: 1.6-9.1
Done: Bastian Germann 

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

Debian distribution maintenance software
pp.
Bastian Germann  (supplier of updated rfdump 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: Fri, 20 Oct 2023 22:04:44 +0200
Source: rfdump
Architecture: source
Version: 1.6-9.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Bastian Germann 
Closes: 967725 967885
Changes:
 rfdump (1.6-9.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove libglade dependency, build with gtk3. (Closes: #967885, #967725)
Checksums-Sha1:
 0d1b523fdbe9ba2df1705ce67617003852ea5935 1764 rfdump_1.6-9.1.dsc
 35327da187442acc74833bc0907a6290977b1a88 13808 rfdump_1.6-9.1.debian.tar.xz
 fea9beaf316cef20dbc6bef92b3f38073374eef2 13835 rfdump_1.6-9.1_source.buildinfo
Checksums-Sha256:
 0021d62a318490aa5a8a99660e9e167cac74bd40e65a3b1be9a1abea428bdd97 1764 
rfdump_1.6-9.1.dsc
 fa786387b39b3fcaa5cdf4fa63e5879f3c09526caf7bec5527824268f0a9f0d7 13808 
rfdump_1.6-9.1.debian.tar.xz
 eda20743cb8ef61948be304de343d7105bc4bb2e5208911b7852a469c99b52b9 13835 
rfdump_1.6-9.1_source.buildinfo
Files:
 de44035029cd6c7aa413fe992e4f4bae 1764 electronics optional rfdump_1.6-9.1.dsc
 527ae4156cbc82996eeb3614dec9b44c 13808 electronics optional 
rfdump_1.6-9.1.debian.tar.xz
 7ce99731fa91f2a8d4077746212fe43a 13835 electronics optional 
rfdump_1.6-9.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUy3jMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPKHC/0SAC/KdY4PaPlKzvqhOt6OiOmKxPlsN2Q8
paSvr1DIJsTragtr0P7YYgrnYWHez+1bh1AgoIyVuQCfudi180UvTXM4cgznRpDP
2AUfVHgSVPbMbE9D27nqRSG7a20/Gx69e7YfISVunKIhUM9xA5+iRigZtcWT6tH6
0hn+D0AN80DU4IkEPxskILWQ//PdWRsEKLSY/BYerI5Y09mfV4LK9EQLOC3UrrcM
jFpZ/HrIcaOWIUznnBlV7RmIqV6y7T7k9xWzUB6Jx/oHjNmxs6yYpmlaijT2uZ+8
j19q1FYIQCOXLVjMcGWhIkkVUsCrGElmA3SxPH02ruisVcUNnyxV8ow67fSV6zWs
gGhLwkbYT63b3sFs6Y6W2btATuj7OJVNhlS6U1f9XH8nnoq6LQ6Qbuu3Fnd8oVDH
1bAIe7KipQl56zsOLsrnYAHYg+VoBiRclLrWrcS9GMMU1ks9mEVWad2M/vcKW7+Y
X06Uq0gUKbBC4tyxxUtA9euESgc3n/I=
=mR0T
-END PGP SIGNATURE End Message ---

Bug#1055058: marked as done (handbrake-cli: Encoding with svt_av1 or svt_av1_10bit fails)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 21:05:30 +
with message-id 
and subject line Bug#1055058: fixed in ffmpeg 7:6.0-8
has caused the Debian Bug report #1055058,
regarding handbrake-cli: Encoding with svt_av1 or svt_av1_10bit fails
to be marked as done.

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

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


-- 
1055058: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055058
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: handbrake-cli
Version: 1.6.1+ds1-2
Severity: normal

Dear Maintainer,


trying to encode a video with svt_av1 or svt_av1_10bit fails.
Steps to reproduce:
- Download a video like this one from the Blender Foundation
  `wget 
https://video.blender.org/download/videos/42b7eb01-6cc0-403a-a623-b2a530ad24bb-1080.mp4`
- Try reencoding it to AV1
  `HandBrakeCLI -i 42b7eb01-6cc0-403a-a623-b2a530ad24bb-1080.mp4 -o 
svt_av1_10bit_test.webm -f av_webm -O -e svt_av1_10bit`

This also happens on the GUI version of Handbrake.

For reference, I am running an Intel A770 16GB graphics card which is supposed 
to have AV1 hardware accelerated encoding; I am wondering if that has something 
to do with it.
Output of vainfo is attached.

The full log of the error is attached.


Greetings from Germany
Julian Groß


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

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

Versions of packages handbrake-cli depends on:
ii  libass9 1:0.17.1-1
ii  libavcodec607:6.0-7+b1
ii  libavfilter97:6.0-7+b1
ii  libavformat60   7:6.0-7+b1
ii  libavutil58 7:6.0-7+b1
ii  libbluray2  1:1.3.4-1
ii  libc6   2.37-12
ii  libdvdnav4  6.1.1-1
ii  libdvdread8 6.1.3-1
ii  libjansson4 2.14-2
ii  libswresample4  7:6.0-7+b1
ii  libswscale7 7:6.0-7+b1
ii  libtheora0  1.1.1+dfsg.1-16.1+b1
ii  libturbojpeg0   1:2.1.5-2
ii  libva-drm2  2.20.0-2
ii  libva2  2.20.0-2
ii  libvorbis0a 1.3.7-1
ii  libvorbisenc2   1.3.7-1
ii  libvpl2 2023.3.0-1
ii  libx264-164 2:0.164.3095+gitbaee400-3+b1
ii  libx265-199 3.5-2+b1
ii  libxml2 2.9.14+dfsg-1.3

handbrake-cli recommends no packages.

handbrake-cli suggests no packages.

-- no debconf information
$ HandBrakeCLI -i 42b7eb01-6cc0-403a-a623-b2a530ad24bb-1080.mp4 -o 
svt_av1_10bit_test.webm -f av_webm -O -e svt_av1_10bit
[13:21:56] Compile-time hardening features are enabled
[13:21:56] hb_display_init: attempting VA driver 'iHD'
libva info: VA-API version 1.20.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
[13:21:56] hb_display_init: using VA driver 'iHD'
libva info: VA-API version 1.20.0
libva info: User environment variable requested driver 'iHD'
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so
libva info: Found init function __vaDriverInit_1_20
libva info: va_openDriver() returns 0
[13:21:56] qsv: is available on this system
[13:21:56] nvenc: version 12.0 is available
[13:21:56] nvdec: is not compiled into this build
[13:21:56] hb_init: starting libhb thread
[13:21:56] thread 7f6c3bfff6c0 started ("libhb")
HandBrake 1.6.1 (2023082100) - Linux x86_64 - https://handbrake.fr
12 CPUs detected
Opening 42b7eb01-6cc0-403a-a623-b2a530ad24bb-1080.mp4...
[13:21:56] CPU: Intel(R) Core(TM) i7-7800X CPU @ 3.50GHz
[13:21:56]  - logical processor count: 12
[13:21:56] Intel Quick Sync Video support: yes
[13:21:56] Intel Quick Sync Video unknown adapter with index 0
[13:21:56] Impl mfxhw64 library path: 
/usr/lib/x86_64-linux-gnu/libmfxhw64.so.1.35
[13:21:56]  - Intel Media SDK hardware: API 1.35 (minimum: 1.3)
[13:21:56]  - Decode support:  h264 hevc (8bit: yes, 10bit: yes) av1 (8bit: 
yes, 10bit: yes)
[13:21:56]  - H.264 encoder: yes
[13:21:56] - preferred implementation: hardware (any) via ANY
[13:21:56] - capabilities (hardware):  lowpower breftype vsinfo 
chromalocinfo opt1 opt2+mbbrc+extbrc+trellis+repeatpps+ib_adapt+nmpslice
[13:21:56]  - H.265 encoder: no
[13:21:56]  - AV1 encoder: no
[13:21:56] hb_scan: path=42b7eb01-6cc0-403a-a623-b2a530ad24bb-1080.mp4, 
title_index=1
udfread ERROR: ECMA 167 Volume 

Bug#1054646: marked as done (gammapy: test_binary_dilate fails on i386, s390x)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 21:05:40 +
with message-id 
and subject line Bug#1054646: fixed in gammapy 1.1-2
has caused the Debian Bug report #1054646,
regarding gammapy: test_binary_dilate fails on i386, s390x
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.)


-- 
1054646: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054646
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gammapy
Version: 1.1-1
Severity: serious
Justification: debci

scipy 1.10.1-4 is triggering errors in test_ndmap.py
test_binary_dilate and test_binary_dilate_erode_3d
on both i386 and s390x.

The error looks a little like
https://github.com/gammapy/gammapy/issues/3662 which was solved by
adding error tolerance, https://github.com/gammapy/gammapy/pull/3907

Perhaps that tolerance needs to be increased a little. The failing
difference here is 23 not 20. 

test_binary_dilate_erode_3d isn't using a tolerance like that, should
it add it?

Not entirely clear why scipy 1.10.1-4 is giving failures now. The tests were
passing with scipy 1.10.1-2.  scipy 1.10.1-4 now builds with pythran
0.14, so perhaps some pythran 0.11 functions had gotten built into the
scipy 1.10.1-2 libraries that gammapy uses.
--- End Message ---
--- Begin Message ---
Source: gammapy
Source-Version: 1.1-2
Done: Ole Streicher 

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

Debian distribution maintenance software
pp.
Ole Streicher  (supplier of updated gammapy package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 21:22:39 +0100
Source: gammapy
Architecture: source
Version: 1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Astro Team 
Changed-By: Ole Streicher 
Closes: 1054646
Changes:
 gammapy (1.1-2) unstable; urgency=medium
 .
   * Increase tolerances in test_ndmap.py (Closes: #1054646)
Checksums-Sha1:
 1be5aaa2c2a1eb3fb6b48d79d4d07b8da4847d83 2445 gammapy_1.1-2.dsc
 9cddf690bbe15a82b6a186a008703b2c7dc6e418 8008 gammapy_1.1-2.debian.tar.xz
Checksums-Sha256:
 58c5f258872dd8a0b3c593fe4b8f328b30568c149cd88769362eadaef9700c04 2445 
gammapy_1.1-2.dsc
 56121c5fec824fbe046f295a1ac7b02d74723f4de0bd2c48a0b6f5b25fc835eb 8008 
gammapy_1.1-2.debian.tar.xz
Files:
 b785ca4af1073a2a33aac23f72888625 2445 python optional gammapy_1.1-2.dsc
 b2247eebff21907fac572de03ca0d696 8008 python optional 
gammapy_1.1-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAmVAE4UACgkQmk9WvbkO
GL0zOg//Qps3CJZNpwuMDLEo/IrO/y/cPZU2QXH7REeM4/nWZpmIbnXwrXS4NHGL
scKD7Lbd2HgyLTP391qHogCRgDIJYYCTL3/YiJViFxNi08X73GnZmUdSrWa5+A6p
V4XLwRxTEiHQBtX40pUCvK2n/+OhJZ+bJTPmoH7QJRrgsujpkxmYs9GfRcBAPvyB
fkVYgxapW9LQ4ynYTRSHWihsjVB7HDQL9DKvjVqUe9q+1p98JqoarmXsBQeL/f9X
6Hhso2PkhfONzTPulLq4NRBGGTkxTi92Dn5nhedqZSvHwC6chpnohHrZXB2fJzgb
uzpESg/qgGBCm6cjyY+pwodZHp2nE0TsoWXj1elssiRsOv9P8maMYo3IgzNW6yex
/Th713Mn0BpUhzFg799lhjYa8kSHvQDV7cb54M3rabwvBXp+dTQLN2f1Dos57jtZ
DnuhVGC7RAzzABIyE9FQeqJBaeX2wTd6IHgqeLMrziXyqA6N4yA/gD0L0DN9nIsM
ax/QBn3nY28DjYR6VUpVjZHpW9R/e+ZEHn0IhCozgBVYxV8YCXOGCtXUVYm5DhrU
gdeztKg6ZEwtkbKNa0BwEMuhStht5dYdyTZK8Y42teRlsRSM/NA8TQ/I5fvmBOdv
a70I3Ca8Pb+IvLOiiFqJyw+NIqlZeUPN4V6otDu3KfWt21Z8yXM=
=aIOW
-END PGP SIGNATURE End Message ---

Bug#1042465: marked as done (python3-hypercorn: Aioquic now in the archive, so please update Recommends/Suggests)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 21:05:50 +
with message-id 
and subject line Bug#1042465: fixed in hypercorn 0.15.0-1
has caused the Debian Bug report #1042465,
regarding python3-hypercorn: Aioquic now in the archive, so please update 
Recommends/Suggests
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.)


-- 
1042465: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042465
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-hypercorn
Version: 0.14.4-1
Severity: normal

As of today, aioquic (python3-aioquic) is in the archive, so it might be
good to update either the package Recommends or Suggests to take
advantage of this.  I seen it's already mentioned in the package
description.

Scott K
--- End Message ---
--- Begin Message ---
Source: hypercorn
Source-Version: 0.15.0-1
Done: Michael Fladischer 

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

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

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

Debian distribution maintenance software
pp.
Michael Fladischer  (supplier of updated hypercorn package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 20:12:16 +
Source: hypercorn
Architecture: source
Version: 0.15.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Michael Fladischer 
Closes: 1042465
Changes:
 hypercorn (0.15.0-1) unstable; urgency=medium
 .
   * Add python3-aioquic to Suggests (Closes: #1042465).
   * New upstream version 0.15.0
   * Refresh patches.
   * Use local mermaid.js file instead of the CDN one to prevent a privacy
 breach.
Checksums-Sha1:
 e972b756f0ee418196dce29ac47bb72db4cf6f4d 2342 hypercorn_0.15.0-1.dsc
 1261e352b6cacc42740c7db721d813f217652ce8 156271 hypercorn_0.15.0.orig.tar.gz
 a38d25ac7d8a05f458eb11175d7b7de4e08d0c52 4884 hypercorn_0.15.0-1.debian.tar.xz
 1313b6ba58e48493feebbf56b9169e3f4c38927b 9462 
hypercorn_0.15.0-1_arm64.buildinfo
Checksums-Sha256:
 c01b2221052bd9e8cfc0e79338f15e762fcb55267df7984b0aab9290cfb2b7ba 2342 
hypercorn_0.15.0-1.dsc
 e088ac4ce330bc83d4e223cd1fa875f4fd527065b0cb60d571aedc12f2370f07 156271 
hypercorn_0.15.0.orig.tar.gz
 994c4332121472b3e2d0110fb7a17e16e11235fbf31949f8ca542112d0cf60f9 4884 
hypercorn_0.15.0-1.debian.tar.xz
 f7c915b8f19ffc2bde7129840c36573b1ccd248a27670b88bbafbbd2d98d0b3a 9462 
hypercorn_0.15.0-1_arm64.buildinfo
Files:
 cb590b7d2cf9b33ae277861696cf8f14 2342 python optional hypercorn_0.15.0-1.dsc
 8a5f02005c2bb8971bbfffad9b2e30ea 156271 python optional 
hypercorn_0.15.0.orig.tar.gz
 c64d2bdd17d4dae851cf47eead66510c 4884 python optional 
hypercorn_0.15.0-1.debian.tar.xz
 4b62797f69aa0fa4737988c421d0f200 9462 python optional 
hypercorn_0.15.0-1_arm64.buildinfo

-BEGIN PGP SIGNATURE-

iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAmVAD6UACgkQ/9PIi5l9
0WoTKAgAg/1N+WpGleLTtpZABTxWZkwCPC09QnXvdKRwcQqDJySlxtOQsNYe2zNb
lpRrORFVfjc+O+IrooVN47KHnvotkOZKETpCevFmZSlO+s10TPe3rUlIxtVGfMB9
Xe58a7iwB6+uoa2fqkeln10XFLcUn9o6RUk1ns7mwWS8QlQMhVNEXnL2Yc3Xqiic
uyo0a2SLK9NNngjGZyXgyOwIOjqN+E2oVWYmppKDrOEnIMD68y2NzuhCCZZ6KceA
yu/llK8tOXguIxIJGV4FYDDoFyEdMnUw4qv6xTgbat+ATQxFKe6H0pKIxrVIWf4t
JBbl/6pdSRFtxCGf8qX/GGu4K/zD1Q==
=TNn8
-END PGP SIGNATURE End Message ---

Bug#1042600: marked as done (imexam: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** [debian/rules:14: override_dh_installdocs-indep] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 20:36:01 +
with message-id 
and subject line Bug#1042600: fixed in imexam 0.9.1-5
has caused the Debian Bug report #1042600,
regarding imexam: FTBFS with Sphinx 7.1, docutils 0.20: make[1]: *** 
[debian/rules:14: override_dh_installdocs-indep] Error 25
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.)


-- 
1042600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042600
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imexam
Version: 0.9.1-4
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

imexam fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> python3 setup.py build_sphinx
> /usr/lib/python3/dist-packages/pythran/tables.py:4530: FutureWarning: In the 
> future `np.bool` will be defined as the corresponding NumPy scalar.
>   if not hasattr(numpy, method):
> /usr/lib/python3/dist-packages/pythran/tables.py:4563: FutureWarning: In the 
> future `np.bytes` will be defined as the corresponding NumPy scalar.
>   obj = getattr(themodule, elem)
> Sphinx is not installed, can't build documents!!
> 
> Cython found
> /usr/lib/python3/dist-packages/setuptools/dist.py:745: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'description-file' will not be supported in 
> future
> versions. Please use the underscore name 'description_file' instead.
> 
> By 2023-Sep-26, you need to update your project and remove deprecated 
> calls
> or your builds will no longer be supported.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/dist.py:745: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'upload-dir' will not be supported in future
> versions. Please use the underscore name 'upload_dir' instead.
> 
> By 2023-Sep-26, you need to update your project and remove deprecated 
> calls
> or your builds will no longer be supported.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/dist.py:745: 
> SetuptoolsDeprecationWarning: Invalid dash-separated options
> !!
> 
> 
> 
> Usage of dash-separated 'show-response' will not be supported in 
> future
> versions. Please use the underscore name 'show_response' instead.
> 
> By 2023-Sep-26, you need to update your project and remove deprecated 
> calls
> or your builds will no longer be supported.
> 
> See 
> https://setuptools.pypa.io/en/latest/userguide/declarative_config.html for 
> details.
> 
> 
> 
> !!
>   opt = self.warn_dash_deprecation(opt, section)
> /usr/lib/python3/dist-packages/setuptools/__init__.py:84: 
> _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are 
> deprecated.
> !!
> 
> 
> 
> Requirements should be satisfied by a PEP 517 installer.
> If you are using pip, you can try `pip install --use-pep517`.
> 
> 
> 
> !!
>   dist.fetch_build_eggs(dist.setup_requires)
> WARNING: The wheel package is not available.
> /usr/lib/python3/dist-packages/setuptools/dist.py:945: 
> DistDeprecationWarning: use_2to3 is ignored.
>   ep.load()(self, ep.name, value)
> running build_sphinx
> error: error in setup.cfg: command 'BuildSphinx' has no such option 
> 'source_dir'
> make[1]: [debian/rules:13: override_dh_installdocs-indep] Error 1 (ignored)
> dh_installdocs
> dh_installdocs: error: 

Bug#1027381: marked as done (siridb-server: FTBFS (missing build-depends on tzdata))

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 19:59:26 +
with message-id 
and subject line Bug#1027381: fixed in siridb-server 2.0.51-2
has caused the Debian Bug report #1027381,
regarding siridb-server: FTBFS (missing build-depends on tzdata)
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.)


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

Package: src:siridb-server
Version: 2.0.43-1
Severity: serious
Tags: ftbfs patch

Dear maintainer:

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


[...]
 debian/rules binary-arch
dh binary-arch
   dh_update_autotools_config -a
   dh_autoreconf -a
   debian/rules override_dh_auto_build-arch
make[1]: Entering directory '/<>'
dh_auto_build --sourcedirectory=Release
cd Release && make -j2 "INSTALL=install --strip-program=true"
make[2]: Entering directory '/<>/Release'
Building file: ../src/xpath/xpath.c
Building file: ../src/base64/base64.c
Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xpath/xpath.d" 
-MT"src/xpath/xpath.o" -o "src/xpath/xpath.o" "../src/xpath/xpath.c"
Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/base64/base64.d" 
-MT"src/base64/base64.o" -o "src/base64/base64.o" "../src/base64/base64.c"
Finished building: ../src/base64/base64.c
 
Building file: ../src/xmath/xmath.c

Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xmath/xmath.d" 
-MT"src/xmath/xmath.o" -o "src/xmath/xmath.o" "../src/xmath/xmath.c"
Finished building: ../src/xpath/xpath.c
 
Building file: ../src/timeit/timeit.c

Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/timeit/timeit.d" 
-MT"src/timeit/timeit.o" -o "src/timeit/timeit.o" "../src/timeit/timeit.c"
Finished building: ../src/xmath/xmath.c
Finished building: ../src/timeit/timeit.c
 
 
Building file: ../src/xstr/xstr.c

Building file: ../src/vec/vec.c
Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/xstr/xstr.d" 
-MT"src/xstr/xstr.o" -o "src/xstr/xstr.o" "../src/xstr/xstr.c"
Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/vec/vec.d" 
-MT"src/vec/vec.o" -o "src/vec/vec.o" "../src/vec/vec.c"
Finished building: ../src/vec/vec.c
 
Building file: ../src/siri/service/account.c

Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/account.d" 
-MT"src/siri/service/account.o" -o "src/siri/service/account.o" "../src/siri/service/account.c"
Finished building: ../src/xstr/xstr.c
 
Building file: ../src/siri/service/client.c

Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/client.d" 
-MT"src/siri/service/client.o" -o "src/siri/service/client.o" "../src/siri/service/client.c"
Finished building: ../src/siri/service/account.c
 
Building file: ../src/siri/service/request.c

Invoking: GCC C Compiler
cc -DNDEBUG -I../include -O3 -Wall -Wextra -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -c -fmessage-length=0 -MMD -MP -MF"src/siri/service/request.d" 
-MT"src/siri/service/request.o" -o "src/siri/service/request.o" "../src/siri/service/request.c"

Bug#1031335: marked as done (lintian: Please backport 2.116.3 to bullseye)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 20:21:49 +0100
with message-id <5687eb3bd2d7fc5a668bbbfe9348d5bb221a3c75.ca...@debian.org>
and subject line Re: lintian: Please backport 2.116.3 to bullseye
has caused the Debian Bug report #1031335,
regarding lintian: Please backport 2.116.3 to bullseye
to be marked as done.

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

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


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

Dear maintainer,



At mentors.debian.net, we use the bpo version of lintian to run on
uploaded packages. But this 2.115.1 version report the latest
standards-version as unknown.


Could we please have a bpo build for 2.116.3?


Thanks,
-- 
Baptiste Beauplat - lyknode
--- End Message ---
--- Begin Message ---
Dear maintainer,

On Wed, 15 Feb 2023 08:46:40 +0100 Baptiste Beauplat
 wrote:
> At mentors.debian.net, we use the bpo version of lintian to run on
> uploaded packages. But this 2.115.1 version report the latest
> standards-version as unknown.
> 
> Could we please have a bpo build for 2.116.3?

Mentors has been upgraded to bookworm and we no longer have the need
for a backport to bullseye.

Thus closing this bug report.

Best,
-- 
Baptiste Beauplat



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

Bug#1054140: marked as done (python-refurb: FTBFS with mypy 1.6.0)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 20:20:21 +0100
with message-id 
and subject line Re: python-refurb: FTBFS with mypy 1.6.0
has caused the Debian Bug report #1054140,
regarding python-refurb: FTBFS with mypy 1.6.0
to be marked as done.

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

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


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

Source: python-refurb
Version: 1.21.0-1
Severity: normal
Tags: patch ftbfs upstream

Dear Maintainer,

Mypy 1.6.0-1 is in unstable, an unfortunately it causes a build-type 
test for python-refurb to fail[0]. I reported this upstream[1] and they 
maintainer provided a fix[2]. Would you please apply this as a patch to 
unblock the migration of mypy 1.6.0-1 to testing. Or, if you wish, I can 
do a team-upload of python-refurb for you.


Thanks,

[0] 
https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-refurb/39057922/log.gz


[1] https://github.com/dosisod/refurb/issues/295

[2] https://github.com/dosisod/refurb/pull/296

--
Michael R. Crusoe



OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---

Version:  1.22.1-1


OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---

Bug#1052701: marked as done (owfs FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 17:50:36 +
with message-id 
and subject line Bug#1052701: fixed in owfs 3.2p4+dfsg1-4.2
has caused the Debian Bug report #1052701,
regarding owfs FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052701: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052701
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: owfs
Version: 3.2p4+dfsg1-4.1
Severity: normal
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. owfs' upstream build system consumes this variable
while the packaging hard codes its current value. As we change it, owfs
will FTBFS. Consider applying the attached patch to avoid that failure.

Helmut
diff -Nru owfs-3.2p4+dfsg1/debian/changelog owfs-3.2p4+dfsg1/debian/changelog
--- owfs-3.2p4+dfsg1/debian/changelog   2022-10-31 22:48:27.0 +0100
+++ owfs-3.2p4+dfsg1/debian/changelog   2023-09-26 09:57:55.0 +0200
@@ -1,3 +1,10 @@
+owfs (3.2p4+dfsg1-4.2) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 26 Sep 2023 09:57:55 +0200
+
 owfs (3.2p4+dfsg1-4.1) unstable; urgency=medium
 
   * Non-maintainer upload
diff -Nru owfs-3.2p4+dfsg1/debian/owfs-fuse.install 
owfs-3.2p4+dfsg1/debian/owfs-fuse.install
--- owfs-3.2p4+dfsg1/debian/owfs-fuse.install   2022-10-31 22:34:45.0 
+0100
+++ owfs-3.2p4+dfsg1/debian/owfs-fuse.install   2023-09-26 09:57:10.0 
+0200
@@ -1,4 +1,4 @@
 usr/bin/owfs   usr/libexec/owfs
 debian/wrappers/owfs   usr/bin
 usr/share/man/man1/owfs.1
-lib/systemd/system/owfs.service
+${env:systemdsystemunitdir}/owfs.service
diff -Nru owfs-3.2p4+dfsg1/debian/owftpd.install 
owfs-3.2p4+dfsg1/debian/owftpd.install
--- owfs-3.2p4+dfsg1/debian/owftpd.install  2022-10-31 22:34:45.0 
+0100
+++ owfs-3.2p4+dfsg1/debian/owftpd.install  2023-09-26 09:57:21.0 
+0200
@@ -1,3 +1,3 @@
 usr/bin/owftpd
 usr/share/man/man1/owftpd.1
-lib/systemd/system/owftpd.service
+${env:systemdsystemunitdir}/owftpd.service
diff -Nru owfs-3.2p4+dfsg1/debian/owhttpd.install 
owfs-3.2p4+dfsg1/debian/owhttpd.install
--- owfs-3.2p4+dfsg1/debian/owhttpd.install 2022-10-31 22:34:45.0 
+0100
+++ owfs-3.2p4+dfsg1/debian/owhttpd.install 2023-09-26 09:57:31.0 
+0200
@@ -1,3 +1,3 @@
 usr/bin/owhttpd
 usr/share/man/man1/owhttpd.1
-lib/systemd/system/owhttpd.service
+${env:systemdsystemunitdir}/owhttpd.service
diff -Nru owfs-3.2p4+dfsg1/debian/owserver.install 
owfs-3.2p4+dfsg1/debian/owserver.install
--- owfs-3.2p4+dfsg1/debian/owserver.install2022-10-31 22:34:45.0 
+0100
+++ owfs-3.2p4+dfsg1/debian/owserver.install2023-09-26 09:57:48.0 
+0200
@@ -1,5 +1,5 @@
 usr/bin/owserver
 usr/bin/owexternal
 usr/share/man/man1/owserver.1
-lib/systemd/system/owserver.service
-lib/systemd/system/owserver.socket
+${env:systemdsystemunitdir}/owserver.service
+${env:systemdsystemunitdir}/owserver.socket
diff -Nru owfs-3.2p4+dfsg1/debian/rules owfs-3.2p4+dfsg1/debian/rules
--- owfs-3.2p4+dfsg1/debian/rules   2022-10-31 22:34:45.0 +0100
+++ owfs-3.2p4+dfsg1/debian/rules   2023-09-26 09:55:33.0 +0200
@@ -26,6 +26,8 @@
 DEB_LDFLAGS = `dpkg-buildflags --get LDFLAGS`
 export DEB_CPPFLAGS DEB_CFLAGS DEB_LDFLAGS
 
+export systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
+
 CONFIGURE_OPTIONS=\
--enable-debian   \
--enable-debug\
--- End Message ---
--- Begin Message ---
Source: owfs
Source-Version: 3.2p4+dfsg1-4.2
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated owfs package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 18:27:35 +0100
Source: 

Bug#1052703: marked as done (tuned FTBFS when systemd.pc changes systemdsystemunitdir)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 17:37:15 +
with message-id 
and subject line Bug#1052703: fixed in tuned 2.20.0-1.1
has caused the Debian Bug report #1052703,
regarding tuned FTBFS when systemd.pc changes systemdsystemunitdir
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.)


-- 
1052703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052703
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tuned
Version: 2.20.0-1
Tags: ftbfs patch
User: helm...@debian.org
Usertags: dep17m2

We want to change the value of systemdsystemunitdir in systemd.pc to
point below /usr. tuned's upstream build system consumes this variable
while its packaging hard codes its current value. As we change it, tuned
will FTBFS. Consider applying the attached patch to avoid this failure.

Helmut
diff -Nru tuned-2.20.0/debian/changelog tuned-2.20.0/debian/changelog
--- tuned-2.20.0/debian/changelog   2023-02-19 14:22:27.0 +0100
+++ tuned-2.20.0/debian/changelog   2023-09-26 11:32:49.0 +0200
@@ -1,3 +1,10 @@
+tuned (2.20.0-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTBFS when systemd.pc changes systemdsystemunitdir. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 26 Sep 2023 11:32:49 +0200
+
 tuned (2.20.0-1) unstable; urgency=medium
 
   * New upstream release
diff -Nru tuned-2.20.0/debian/control tuned-2.20.0/debian/control
--- tuned-2.20.0/debian/control 2023-02-19 14:22:10.0 +0100
+++ tuned-2.20.0/debian/control 2023-09-26 11:31:57.0 +0200
@@ -12,7 +12,8 @@
python3-dbus,
python3-gi,
python3-pyudev,
-   systemd
+   systemd,
+   systemd-dev,
 Standards-Version: 4.6.2
 Homepage: https://tuned-project.org/
 Vcs-Git: https://salsa.debian.org/debian/tuned.git
diff -Nru tuned-2.20.0/debian/rules tuned-2.20.0/debian/rules
--- tuned-2.20.0/debian/rules   2023-02-19 14:22:10.0 +0100
+++ tuned-2.20.0/debian/rules   2023-09-26 11:32:23.0 +0200
@@ -4,6 +4,7 @@
 #export DH_VERBOSE = 1
 
 export DEB_PYTHON_INSTALL_LAYOUT=deb_system
+export deb_systemdsystemunitdir = $(shell pkg-config 
--variable=systemdsystemunitdir systemd | sed s,^/,,)
 
 %:
dh $@ --with python3
diff -Nru tuned-2.20.0/debian/tuned.install tuned-2.20.0/debian/tuned.install
--- tuned-2.20.0/debian/tuned.install   2023-02-19 14:22:10.0 +0100
+++ tuned-2.20.0/debian/tuned.install   2023-09-26 11:32:46.0 +0200
@@ -11,7 +11,7 @@
 etc/tuned/realtime-virtual-guest-variables.conf
 etc/tuned/realtime-virtual-host-variables.conf
 etc/tuned/tuned-main.conf
-lib/systemd/system/tuned.service
+${env:deb_systemdsystemunitdir}/tuned.service
 usr/lib/python*/dist-packages/tuned/__init__.py
 usr/lib/python*/dist-packages/tuned/admin/
 usr/lib/python*/dist-packages/tuned/consts.py
--- End Message ---
--- Begin Message ---
Source: tuned
Source-Version: 2.20.0-1.1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated tuned package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 18:17:33 +0100
Source: tuned
Architecture: source
Version: 2.20.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Evgeni Golov 
Changed-By: Jochen Sprickerhof 
Closes: 1052703
Changes:
 tuned (2.20.0-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Fix FTBFS when systemd.pc changes systemdsystemunitdir (Closes: #1052703)
Checksums-Sha1:
 c49cf783fecd934d8ccfcd6bf5c63377531b494b 2133 tuned_2.20.0-1.1.dsc
 fc4659ac13e3743f826fb2bc0eba608fc6ae00ba 6860 tuned_2.20.0-1.1.debian.tar.xz
 d4fdac30b4af24f086628af4b13d62ed19c5ec7c 7175 tuned_2.20.0-1.1_source.buildinfo
Checksums-Sha256:
 1597a1c7f4f33833678252d1b86bb137097d1d95a90962388d11c573de18af99 2133 
tuned_2.20.0-1.1.dsc
 9c65331a384dfc0276ed94604f1b1f13ef2074890d53b9196fca68601ff39556 6860 
tuned_2.20.0-1.1.debian.tar.xz
 

Bug#1054476: marked as done (yaskkserv: will install yaskkserv.service twice once dh_installsystemd installs to /usr)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 17:21:55 +
with message-id 
and subject line Bug#1054476: fixed in yaskkserv 1.1.1-3
has caused the Debian Bug report #1054476,
regarding yaskkserv: will install yaskkserv.service twice once 
dh_installsystemd installs to /usr
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.)


-- 
1054476: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054476
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yaskkserv
Version: 1.1.1-2
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to modify dh_installsystemd such that units are installed below
/usr in order to finalize the /usr-merge transition via DEP17. When
doing so, yaskkserv.service will be installed to both /lib (via
dh_install) and /usr/lib (via dh_installsystemd). Such behaviour
constitutes a policy violation and therefore this bug will become
release-critical once I upload debhelper. I'm attaching a patch for your
convenience.

Helmut
diff -Nru yaskkserv-1.1.1/debian/changelog yaskkserv-1.1.1/debian/changelog
--- yaskkserv-1.1.1/debian/changelog2023-10-03 10:19:38.0 +0200
+++ yaskkserv-1.1.1/debian/changelog2023-10-24 13:36:09.0 +0200
@@ -1,3 +1,9 @@
+yaskkserv (1.1.1-3) UNRELEASED; urgency=medium
+
+  * Install yaskkserv.service only once. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 24 Oct 2023 13:36:09 +0200
+
 yaskkserv (1.1.1-2) unstable; urgency=medium
 
   * QA upload.
diff -Nru yaskkserv-1.1.1/debian/yaskkserv.install 
yaskkserv-1.1.1/debian/yaskkserv.install
--- yaskkserv-1.1.1/debian/yaskkserv.install2023-10-03 10:17:47.0 
+0200
+++ yaskkserv-1.1.1/debian/yaskkserv.install2023-10-24 13:36:06.0 
+0200
@@ -1,2 +1 @@
 debian/update-skkdic-yaskkserv usr/sbin
-debian/yaskkserv.socket lib/systemd/system
--- End Message ---
--- Begin Message ---
Source: yaskkserv
Source-Version: 1.1.1-3
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated yaskkserv package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 18:13:55 +0100
Source: yaskkserv
Architecture: source
Version: 1.1.1-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Jochen Sprickerhof 
Closes: 1054476
Changes:
 yaskkserv (1.1.1-3) unstable; urgency=medium
 .
   * QA upload.
 .
   [ Helmut Grohne ]
   * Install yaskkserv.service only once (Closes: #1054476)
Checksums-Sha1:
 4500978428f8808ab6b61018345df1eb241c4aa7 1888 yaskkserv_1.1.1-3.dsc
 084b4d6eec0ae5afc5a673dc520547e4b99595fe 11860 yaskkserv_1.1.1-3.debian.tar.xz
 74ec41263e33271d6c2c927835593f494ad07aa6 6075 
yaskkserv_1.1.1-3_source.buildinfo
Checksums-Sha256:
 f50659efc71958886c7246fd5cc3cc02bafe2e9d1198a0d09b9805915fe3758e 1888 
yaskkserv_1.1.1-3.dsc
 771974950bc6e50f7a68f7bca618658a38812a9d91c040960a6dceddcc225b93 11860 
yaskkserv_1.1.1-3.debian.tar.xz
 7e3fd9427b5dd8bfd68719ebe56f063480d40806b3017a19acdd3b99b505f9e2 6075 
yaskkserv_1.1.1-3_source.buildinfo
Files:
 101df247185bb4a3f3a8de132f44f467 1888 utils optional yaskkserv_1.1.1-3.dsc
 4ad1f1ac4fc566b86ebb0056d276e6ac 11860 utils optional 
yaskkserv_1.1.1-3.debian.tar.xz
 bf4d6adb16c069cc5d2855ba20997673 6075 utils optional 
yaskkserv_1.1.1-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmU/5GoACgkQW//cwljm
lDOnORAAidmP7s/4HFRJQdGOr/pc0pVNm4N0357yTvq2mUkQsiPByXEZdjAQV3DA
MXflGVnYmEGYTrhGeDKNc5MsajtF/1ojCEn0aMg5UhBMpeTsCyzwGdHGn53ckS0O
Ma1brFhkwnTsG2uSJ69R+NblP4TwusDUz4PEnvWyTzpJYeeP+lBsGYejZ22uVIXL
eD0rrmXdvschHxxzKRMHYCiHLmSiscvHG38JiCWhOjzqDBNXDT59kX7aEns4/DQ1
9/AFMgU6+mgQvu4t9z7elFzwEgJv/FmJvTme+ft1/H54g27ghMvLuMXRBEZQnwtx
Zj5cPQC6LKLb4DTyXmLZkbKgn6CAezju+ErrgxQhevjlesjVhScQ71hvWIsykxlK
e7QxySUSLZh21QFEL+NrqloCXSnHUhGZxCHVDKRwUKEFO4ylEFWHrd4FxhsXRww+
gZNTozL+a1ajZ2rnuRvpi+XE9lo2hHiY1aI2jxFOoWRp0Msp/hoURU/NmGG9APuZ

Bug#1054482: marked as done (gearman-job-server: installs systemd unit twice when dh_installsystemd installs to /usr)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 17:20:55 +
with message-id 
and subject line Bug#1054482: fixed in gearmand 1.1.20+ds-1.1
has caused the Debian Bug report #1054482,
regarding gearman-job-server: installs systemd unit twice when 
dh_installsystemd installs to /usr
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.)


-- 
1054482: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054482
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gearmand
Version: 1.1.20+ds-1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

We want to change dh_installsystemd such that it installs units below
/usr in order to finalize the /usr-merge transition via DEP17. When
doing that, a unit is installed in both /lib (via dh_install) and
/usr/lib (via dh_installsystemd). Doing so is a policy violation and
this bug will become release critical once I upload debhelper. I'm
attaching a patch for your convenience.

Helmut
diff -Nru gearmand-1.1.20+ds/debian/changelog 
gearmand-1.1.20+ds/debian/changelog
--- gearmand-1.1.20+ds/debian/changelog 2023-03-11 16:29:56.0 +0100
+++ gearmand-1.1.20+ds/debian/changelog 2023-10-24 10:16:36.0 +0200
@@ -1,3 +1,10 @@
+gearmand (1.1.20+ds-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Install systemd units only once. (Closes: #-1)
+
+ -- Helmut Grohne   Tue, 24 Oct 2023 10:16:36 +0200
+
 gearmand (1.1.20+ds-1) unstable; urgency=medium
 
   [ Jenkins ]
diff -Nru gearmand-1.1.20+ds/debian/gearman-job-server.dirs 
gearmand-1.1.20+ds/debian/gearman-job-server.dirs
--- gearmand-1.1.20+ds/debian/gearman-job-server.dirs   2023-03-11 
16:29:56.0 +0100
+++ gearmand-1.1.20+ds/debian/gearman-job-server.dirs   2023-10-24 
10:16:36.0 +0200
@@ -1,2 +1 @@
 /var/log/gearman-job-server
-lib/systemd/system
diff -Nru gearmand-1.1.20+ds/debian/gearman-job-server.install 
gearmand-1.1.20+ds/debian/gearman-job-server.install
--- gearmand-1.1.20+ds/debian/gearman-job-server.install2023-03-11 
16:29:56.0 +0100
+++ gearmand-1.1.20+ds/debian/gearman-job-server.install2023-10-24 
10:16:21.0 +0200
@@ -1,3 +1,2 @@
-debian/gearman-job-server.service lib/systemd/system
 usr/sbin
 usr/share/man/man8/gearmand.8
--- End Message ---
--- Begin Message ---
Source: gearmand
Source-Version: 1.1.20+ds-1.1
Done: Jochen Sprickerhof 

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

Debian distribution maintenance software
pp.
Jochen Sprickerhof  (supplier of updated gearmand package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 18:00:00 +0100
Source: gearmand
Architecture: source
Version: 1.1.20+ds-1.1
Distribution: unstable
Urgency: medium
Maintainer: Alexandre Mestiashvili 
Changed-By: Jochen Sprickerhof 
Closes: 1054482
Changes:
 gearmand (1.1.20+ds-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
 .
   [ Helmut Grohne ]
   * Install systemd units only once (Closes: #1054482)
Checksums-Sha1:
 d1011cc2f9a422b66d5805793a973d2d5daa775e 2712 gearmand_1.1.20+ds-1.1.dsc
 75d7bec6c69f0a2bebbfa93d178ea1b5ded8a559 21144 
gearmand_1.1.20+ds-1.1.debian.tar.xz
 dc8cdb06bdd21063e5fa90f58f3b570d61ab7b58 6179 
gearmand_1.1.20+ds-1.1_source.buildinfo
Checksums-Sha256:
 3ed931d41f1c8077131a0b124da708e53f0c073f97fb2b0450fb72b6239edca1 2712 
gearmand_1.1.20+ds-1.1.dsc
 5dc9c0a3fb95a723314e4204a6345cc73af6cc955f6f2824c09305ada6528a01 21144 
gearmand_1.1.20+ds-1.1.debian.tar.xz
 4750b71e44bf4f481d515a30cb98bcab2763bae8e0ba6b682ebff8807aceadff 6179 
gearmand_1.1.20+ds-1.1_source.buildinfo
Files:
 fbf0664bbdac98fb249d5164d448b9e5 2712 misc optional gearmand_1.1.20+ds-1.1.dsc
 150d8d2d460a82ea1fa768f58c0dacd0 21144 misc optional 
gearmand_1.1.20+ds-1.1.debian.tar.xz
 433b7245975249e68799290661d46e7a 6179 misc optional 
gearmand_1.1.20+ds-1.1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmU/4ugACgkQW//cwljm
lDMEGQ//fjjSZN/Pm0Iuqk1IIEPNKaUN5jsE3cpZN4V1zPDEA8s8dY3Zoovy45Lr

Bug#1052920: marked as done (gnuplot-mode: FTBFS: mkdir: cannot create directory ‘././sbuild-nonexistent’: Permission denied)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 18:16:47 +0100
with message-id <871qdcc9og.fsf@EBx360>
and subject line Re: FTBFS gnuplot-mode
has caused the Debian Bug report #1052920,
regarding gnuplot-mode: FTBFS: mkdir: cannot create directory 
‘././sbuild-nonexistent’: Permission denied
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.)


-- 
1052920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1052920
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gnuplot-mode
Version: 1:0.8.0+git20230101.1.b57caf8-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20230925 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> pdflatex -interaction=batchmode gpelcard.tex
> This is pdfTeX, Version 3.141592653-2.6-1.40.25 (TeX Live 2023/Debian) 
> (preloaded format=pdflatex)
>  restricted \write18 enabled.
> entering extended mode
> 
> kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 
> tcrm0800
> mkdir: cannot create directory ‘././sbuild-nonexistent’: Permission denied
> mktexpk: Running mf-nowin -progname=mf \mode:=ljfour; mag:=1+0/600; 
> nonstopmode; input tcrm0800
> This is METAFONT, Version 2.71828182 (TeX Live 2023/Debian) (preloaded 
> base=mf)
> 
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/tcrm0800.mf
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exbase.mf)
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/tcrm.mf
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txsymb.mf
>  Ok (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/exaccess.mf
>  Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txpseudo.mf
>  Ok) (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txaccent.mf
>  Ok [0] [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [27] [29])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txgen.mf
>  Ok [100] [109] [98] [99] [108])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txsymbol.mf
>  Ok [13] [18] [21] [22] [23] [24] [25] [26] [28] [31] [32] [36] [39] [44]
> [45] [46] [42] [47] [60] [61] [62] [77] [79] [87] [110] [91] [93] [94] [95]
> [96] [126] [127] [128] [129] [130] [131] [132] [133] [134] [135] [136] [137]
> [138] [139] [140] [141] [142] [143] [144] [145] [146] [147] [148] [149]
> [150] [151] [152] [153] [154] [155] [156] [157] [158] [159] [160] [161]
> [162] [163] [164] [165] [166] [167] [168] [169] [171] [172] [173] [174]
> [175] [177] [176] [180] [181] [182] [183] [184] [187] [191] [214] [246])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txromod.mf
>  Ok [48] [49] [50] [51] [52] [53] [54] [55] [56] [57])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txrsuper.mf
>  Ok [185] [178] [179] [170] [186])
> (/usr/share/texlive/texmf-dist/fonts/source/jknappen/ec/txrfract.mf
>  Ok [188] [189] [190]) ) ) )
> Font metrics written on tcrm0800.tfm.
> Output written on tcrm0800.600gf (128 characters, 19132 bytes).
> Transcript written on tcrm0800.log.
> mktexpk: /tmp/texfonts/pk/ljfour/jknappen/ec/tcrm0800.600pk: successfully 
> generated.
> make[1]: Leaving directory '/<>'
>dh_elpa_test
>   emacs -batch -Q -l package --eval "(add-to-list 'package-directory-list 
> \"/usr/share/emacs/site-lisp/elpa\")" --eval "(add-to-list 
> 'package-directory-list \"/usr/share/emacs/site-lisp/elpa-src\")" -f 
> package-initialize -L . -l gnuplot-tests.el -l gnuplot-test-context.el --eval 
> \(ert-run-tests-batch-and-exit\)
> 
> Error: error ("Test ‘gnuplot-comment-with-single-quotes’ redefined")
>   mapbacktrace(#f(compiled-function (evald func args flags) # 0x294a995ebae857c>))
>   debug-early-backtrace()
>   debug-early(error (error "Test ‘gnuplot-comment-with-single-quotes’ 
> redefined"))
>   error("Test `%s' redefined" gnuplot-comment-with-single-quotes)
>   ert-set-test(gnuplot-comment-with-single-quotes #s(ert-test :name 
> gnuplot-comment-with-single-quotes :documentation "# a comment \"containing a 
> double-quoted string\"" :body (closure (t) nil (let* ((fn-2097 
> #'gnuplot-test-comment-in-context) (args-2098 (condition-case err (let 
> ((signal-hook-function #'ert--should-signal-hook)) (list "# a comment 
> \"containing a double-quoted string\"" "%s")) (error (progn (setq fn-2097 
> #'signal) (list (car err) (cdr err))) (let ((value-2099 
> 'ert-form-evaluation-aborted-2100)) (let (form-description-2101) (if 
> (unwind-protect (setq value-2099 (apply fn-2097 args-2098)) (setq 
> 

Bug#1045729: marked as done (qrtr: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 16:50:04 +
with message-id 
and subject line Bug#1045729: fixed in qrtr 1.0-3~exp1
has caused the Debian Bug report #1045729,
regarding qrtr: Fails to build source after successful build
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.)


-- 
1045729: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045729
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: qrtr
Version: 1.0-2
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> -
> 
> dpkg-buildpackage: info: source package qrtr
> dpkg-buildpackage: info: source version 1.0-2
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Arnaud Ferraris 
> 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>dh_auto_clean
>   make -j8 clean
> make[1]: Entering directory '/<>'
> CLEAN
> rm -f -r out qrtr-ns qrtr-cfg qrtr-lookup libqrtr.so
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building qrtr using existing ./qrtr_1.0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  qrtr-1.0/qrtr-ns.service
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/qrtr_1.0-2.diff.8hs6DV
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/qrtr_1.0-2_unstable.log

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: qrtr
Source-Version: 1.0-3~exp1
Done: Arnaud Ferraris 

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

Debian distribution maintenance software
pp.
Arnaud Ferraris  (supplier of updated qrtr package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 17:19:45 +0100
Source: qrtr
Architecture: source
Version: 1.0-3~exp1
Distribution: experimental
Urgency: medium
Maintainer: DebianOnMobile Maintainers 

Changed-By: Arnaud Ferraris 
Closes: 1045729
Changes:
 qrtr (1.0-3~exp1) experimental; urgency=medium
 .
   * d/patches: add missing service file to the `clean` target (Closes: 
#1045729)
   * d/gbp.conf: use 'debian/experimental' as debian branch
   * debian: keep systemd service under /usr.
 In the current state of the Debian "/usr merge", we are allowed to move
 systemd services under `/usr/lib/systemd` when relying on
 `dh_installsystemd`. This requires adding a 

Bug#1054650: marked as done (dbus: makes the machine extremely slow, freezes on shutdown)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 16:49:09 +
with message-id 
and subject line Bug#1054650: fixed in dbus 1.14.10-3
has caused the Debian Bug report #1054650,
regarding dbus: makes the machine extremely slow, freezes on shutdown
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.)


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

dbus 1.14.10-2 makes the machine extremely slow (this affects the
boot, login, the su command, and package installation at least),
and it freezes on shutdown. This is reproducible (I've tested on
2 successive reboots).

Downgrading to dbus 1.14.10-1 solves the problem.

"systemd-analyze blame" gives

25.157s lightdm.service
25.049s plymouth-quit-wait.service
11.123s NetworkManager-wait-online.service
 3.410s loadcpufreq.service
 2.522s systemd-modules-load.service
 1.392s nvidia-persistenced.service
 1.306s gpm.service
 1.224s accounts-daemon.service
 1.143s networking.service
 1.041s udisks2.service
  997ms atopacct.service
  964ms cups.service
  936ms avahi-daemon.service
  724ms alsa-restore.service
  719ms atd.service
  700ms dev-sda5.device
  695ms NetworkManager.service
  644ms polkit.service
  588ms lm-sensors.service
  540ms e2scrub_reap.service
  500ms rtkit-daemon.service
  498ms ssh.service
  478ms systemd-udev-trigger.service
  435ms ModemManager.service
  413ms exim4.service
  401ms cpufrequtils.service
  395ms dbus.service
  357ms dictd.service
  345ms apache-htcacheclean.service
  317ms colord.service
  262ms wpa_supplicant.service
  238ms apache2.service
  226ms atop.service
  217ms systemd-journald.service
  181ms lvm2-monitor.service
  176ms systemd-udevd.service
  151ms rsyslog.service
  122ms systemd-user-sessions.service
  115ms systemd-journal-flush.service
  107ms keyboard-setup.service
  102ms apparmor.service
   77ms systemd-tmpfiles-setup.service
   70ms systemd-timesyncd.service
   54ms 
dev-disk-by\x2duuid-3a31982a\x2d76fe\x2d493b\x2da6b0\x2da627706c26c7.swap
   52ms systemd-tmpfiles-setup-dev-early.service
   44ms systemd-binfmt.service
   35ms binfmt-support.service
   31ms dev-hugepages.mount
   30ms dev-mqueue.mount
   29ms modprobe@fuse.service
   29ms sys-kernel-debug.mount
   28ms sys-kernel-tracing.mount
   26ms plymouth-start.service
   24ms systemd-random-seed.service
   24ms kmod-static-nodes.service
   22ms modprobe@configfs.service
   21ms systemd-remount-fs.service
   20ms systemd-update-utmp.service
   19ms plymouth-read-write.service
   16ms systemd-sysctl.service
   16ms systemd-tmpfiles-setup-dev.service
   15ms systemd-update-utmp-runlevel.service
   10ms proc-sys-fs-binfmt_misc.mount
   10ms console-setup.service
7ms modprobe@loop.service
6ms modprobe@efi_pstore.service
5ms modprobe@drm.service
5ms modprobe@dm_mod.service
4ms ifupdown-pre.service
4ms sys-fs-fuse-connections.mount
4ms sys-kernel-config.mount
   35us blk-availability.service

With dbus 1.14.10-1:

10.967s NetworkManager-wait-online.service
 2.872s loadcpufreq.service
 2.525s systemd-modules-load.service
 1.593s accounts-daemon.service
 1.527s networking.service
 1.380s nvidia-persistenced.service
 1.274s atopacct.service
 1.115s gpm.service
 1.013s polkit.service
[...]

In the journalctl output:

Oct 27 13:18:04 cventin kernel: microcode: updated early: 0x2e -> 0x49, date = 
2021-08-11
Oct 27 13:18:04 cventin kernel: Linux version 6.5.0-3-amd64 
(debian-ker...@lists.debian.org) (gcc-13 (Debian 13.2.0-5) 13.2.0, GNU ld (GNU 
Binutils for Debian) 2.41) #1 SMP PREEMPT_DYNAMIC Debian 6.5.8-1 (2023-10-22)
Oct 27 13:18:04 cventin kernel: Command line: 
BOOT_IMAGE=/boot/vmlinuz-6.5.0-3-amd64 
root=UUID=4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0 ro quiet
[...]
Oct 27 13:18:21 cventin systemd[1]: Starting exim4.service - exim Mail 
Transport Agent...
Oct 27 13:18:21 cventin dictd[1085]: Starting dictionary server: dictd.
Oct 27 13:18:21 cventin systemd[1]: Started dictd.service - LSB: Start and stop 
dictionary server daemon.
Oct 27 13:18:21 cventin systemd[1]: Started exim4.service - exim Mail Transport 
Agent.
Oct 27 13:18:31 cventin systemd[1]: NetworkManager-dispatcher.service: 
Deactivated successfully.
Oct 27 13:18:35 cventin systemd-timesyncd[563]: Contacted time server 
162.159.200.123:123 (2.debian.pool.ntp.org).
Oct 27 13:18:35 cventin systemd-timesyncd[563]: Initial clock synchronization 
to Fri 2023-10-27 13:18:35.336765 CEST.
Oct 27 13:18:36 cventin dbus-daemon[749]: 

Processed: your mail

[Debian Bug Tracking System]

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

> close #1054611
Bug #1054611 [kwin] kde-spectacle: Dropping a screencast frame because the 
compositor is slow
Marked Bug as done
> # problem is no longer occur
> stop
Stopping processing here.

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

Bug#1043075: marked as done (python3-openstackdocstheme: Incompatible with Sphinx 7)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 16:35:22 +0100
with message-id 
and subject line Package builds fine
has caused the Debian Bug report #1043075,
regarding python3-openstackdocstheme: Incompatible with Sphinx 7
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.)


-- 
1043075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043075
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-openstackdocstheme
Version: 1.20.0-5
Severity: important
Tags: upstream

Dear Maintainer,

When doing a rebuild of all reverse-dependencies against Sphinx 7.1 (which is
currently available in experimental), we noticed that 104 packages FTBFS with
"dh_sphinxdoc: error: .../_static/underscore.js is missing" error [1].

All of these packages build-depend on python3-openstackdocstheme (except for
masakari, which build-depends implicitly via python3-os-api-ref).

The problem is that openstackdocstheme lists Sphinx' own JS files explicitly,
which may change from release to release. To fix this, please:

1. Upgrade to the latest upstream release (at least >= 2.3.0), that inherits
   from basic/layout.html instead of doing an own HTML template from scratch.

2. Cherry-pick the change [2] that I have just submitted upstream, to stop
   listing Sphinx JS files explicitly.

Please let me know if you need my help with this.

Another note: if you symlink jquery-3.2.1.js and jquery-3.2.1.min.js to the
respective files in libjs-jquery package, dh_sphinxdoc should do the same in
all reverse dependencies and generate a dependency on libjs-jquery.

[1]: http://qa-logs.debian.net/2023/07/30/diff.txt
[2]: https://review.opendev.org/c/openstack/openstackdocstheme/+/890587

--
Dmitry Shachnev


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---

I tried rebuilding, and it works. Closing this bug.--- End Message ---

Bug#1042673: marked as done (python-oslo.versionedobjects: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 16:31:31 +0100
with message-id <2af1c949-85ca-44ae-a6ee-79357291c...@debian.org>
and subject line Closing: no bug
has caused the Debian Bug report #1042673,
regarding python-oslo.versionedobjects: FTBFS with Sphinx 7.1, docutils 0.20: 
TypeError: not all arguments converted during string formatting
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.)


-- 
1042673: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042673
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.versionedobjects
Version: 3.1.0-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-oslo.versionedobjects fails to build with Sphinx 7.1 and docutils 0.20, 
both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> python3 -m sphinx -b html doc/source 
> debian/python-oslo.versionedobjects-doc/usr/share/doc/python-oslo.versionedobjects-doc/html
> Running Sphinx v7.1.1
> connecting events for openstackdocstheme
> making output directory... done
> Using openstackdocstheme Sphinx theme from 
> /usr/lib/python3/dist-packages/openstackdocstheme/theme
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 13 source files that are out of date
> updating environment: [new config] 13 added, 0 changed, 0 removed
> reading sources... [  8%] configuration/index
> reading sources... [ 15%] contributor/index
> reading sources... [ 23%] index
> reading sources... [ 31%] install/index
> reading sources... [ 38%] reference/base
> reading sources... [ 46%] reference/exception
> reading sources... [ 54%] reference/fields
> reading sources... [ 62%] reference/fixture
> reading sources... [ 69%] reference/index
> reading sources... [ 77%] user/examples
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-rwzfpf_7.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:25: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-oslo.versionedobjects_3.1.0-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

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

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
--- End Message ---
--- Begin Message ---

THe package builds fine: closing.--- End Message ---

Bug#1042655: marked as done (python-oslo.policy: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 16:23:33 +0100
with message-id <4ac6914a-5a91-4c9a-b002-56f52fadc...@debian.org>
and subject line Package builds fine
has caused the Debian Bug report #1042655,
regarding python-oslo.policy: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: 
not all arguments converted during string formatting
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.)


-- 
1042655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042655
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.policy
Version: 4.1.1-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-oslo.policy fails to build with Sphinx 7.1 and docutils 0.20, both of 
which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> PYTHONPATH=. PYTHON=python3 python3 -m sphinx -b html doc/source 
> debian/python-oslo.policy-doc/usr/share/doc/python-oslo.policy-doc/html
> Running Sphinx v7.1.1
> connecting events for openstackdocstheme
> making output directory... done
> Creating file /<>/doc/source/reference/api/oslo_policy.rst.
> Creating file /<>/doc/source/reference/api/modules.rst.
> Using openstackdocstheme Sphinx theme from 
> /usr/lib/python3/dist-packages/openstackdocstheme/theme
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 25 source files that are out of date
> updating environment: [new config] 27 added, 0 changed, 0 removed
> reading sources... [  4%] admin/index
> reading sources... [  7%] admin/policy-json-file
> reading sources... [ 11%] admin/policy-yaml-file
> reading sources... [ 15%] cli/common/convert-opts
> reading sources... [ 19%] cli/common/default-opts
> reading sources... [ 22%] cli/common/enforcer-opts
> reading sources... [ 26%] cli/common/generator-opts
> reading sources... [ 30%] cli/common/rule-opts
> reading sources... [ 33%] cli/index
> reading sources... [ 37%] cli/oslopolicy-checker
> reading sources... [ 41%] cli/oslopolicy-convert-json-to-yaml
> reading sources... [ 44%] cli/oslopolicy-list-redundant
> reading sources... [ 48%] cli/oslopolicy-policy-generator
> reading sources... [ 52%] cli/oslopolicy-sample-generator
> reading sources... [ 56%] cli/oslopolicy-validator
> reading sources... [ 59%] configuration/index
> reading sources... [ 63%] contributor/index
> reading sources... [ 67%] index
> reading sources... [ 70%] install/index
> reading sources... [ 74%] reference/api/modules
> reading sources... [ 78%] reference/api/oslo_policy
> reading sources... [ 81%] reference/index
> reading sources... [ 85%] user/history
> reading sources... [ 89%] user/index
> reading sources... [ 93%] user/plugins
> /<>/doc/source/user/history.rst:5: CRITICAL: Problems with 
> "include" directive path:
> InputError: [Errno 2] No such file or directory: 'ChangeLog'.
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-3jerllzb.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:28: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-oslo.policy_4.1.1-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have 

Bug#1054543: marked as done (ITP: golang-github-microsoft-go-winio -- Win32 IO-related utilities for Go)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 20:51:49 +0530
with message-id <20231030152149.synr75ke4ursz...@office.mailbox.org>
and subject line Re: ITP: golang-github-microsoft-go-winio -- Win32 IO-related 
utilities for Go
has caused the Debian Bug report #1054543,
regarding ITP: golang-github-microsoft-go-winio -- Win32 IO-related utilities 
for Go
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.)


-- 
1054543: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054543
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: wishlist
Owner: Ramunas Keliuotis 

* Package name: golang-github-microsoft-go-winio
  Version : 0.6.1-1
  Upstream Author : Microsoft
* URL : https://github.com/Microsoft/go-winio
* License : Expat
  Programming Lang: Go
  Description : Win32 IO-related utilities for Go



I am not an owner nor a maintainer of this golang library.
This golang package is dependency to my program I am packaging for Debian.
Need to wrap this golang library into a Debian package and upload it to SID.

I am not sure about the golang packaging into Debian, I submitted a
request to get
access to go-team Salsa area. Then I can work with `dh-make-golang` and upload
to salsa. But again - what is the sequence of how to proceed?



Best regards,
Ramunas Keliuotis

-- 
The content of this email, including all attachments, is confidential. If 
you are not the intended recipient of this e-mail, please notify us 
immediately and delete this email. Any disclosure, copying, distribution or 
any other use of its content is strictly prohibited.
--- End Message ---
--- Begin Message ---
On Mon, Oct 30, 2023 at 04:09:51PM +0200, Ramūnas Keliuotis wrote:
> Hello,
> 
> Nilesh, yes, my apologies, first I have to clean up my dependency list.
> This ITP should be disregarded. How can I close it?

It can be done by mailing #bugnumber-d...@bugs.debian.org

I just did so on your behalf with this mail! \o/

Best,
Nilesh


signature.asc
Description: PGP signature
--- End Message ---

Bug#1042645: marked as done (python-taskflow: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 16:19:59 +0100
with message-id <2f0c7681-b0d0-4c52-8669-3da9a5d2c...@debian.org>
and subject line Package builds fine
has caused the Debian Bug report #1042645,
regarding python-taskflow: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not 
all arguments converted during string formatting
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.)


-- 
1042645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042645
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-taskflow
Version: 5.1.0-2
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

python-taskflow fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> PYTHONPATH=. PYTHON=python3 python3 -m sphinx -b html doc/source 
> /<>/debian/python-taskflow-doc/usr/share/doc/python-taskflow-doc/html
> Running Sphinx v7.1.1
> connecting events for openstackdocstheme
> making output directory... done
> Using openstackdocstheme Sphinx theme from 
> /usr/lib/python3/dist-packages/openstackdocstheme/theme
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 20 source files that are out of date
> updating environment: [new config] 20 added, 0 changed, 0 removed
> reading sources... [  5%] index
> reading sources... [ 10%] user/arguments_and_results
> reading sources... [ 15%] user/atoms
> reading sources... [ 20%] user/conductors
> reading sources... [ 25%] user/engines
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-0c4p2269.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:29: override_dh_sphinxdoc] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/python-taskflow_5.1.0-2_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

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

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
--- End Message ---
--- Begin Message ---

I tried rebuilding and it works. Closing this old bug.--- End Message ---

Bug#1042623: marked as done (horizon: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 16:13:19 +0100
with message-id <9133c40f-4868-4830-9263-79c0988a3...@debian.org>
and subject line This package builds fine
has caused the Debian Bug report #1042623,
regarding horizon: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all 
arguments converted during string formatting
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.)


-- 
1042623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042623
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: horizon
Version: 3:23.1.0-3
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

horizon fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> python3 -m sphinx -b html doc/source 
> debian/horizon-doc/usr/share/doc/horizon-doc/html
> Running Sphinx v7.1.1
> connecting events for openstackdocstheme
> making output directory... done
> Using openstackdocstheme Sphinx theme from 
> /usr/lib/python3/dist-packages/openstackdocstheme/theme
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [html]: targets for 91 source files that are out of date
> updating environment: [new config] 91 added, 0 changed, 0 removed
> reading sources... [  1%] admin/admin-manage-roles
> reading sources... [  2%] admin/customize-configure
> reading sources... [  3%] admin/index
> reading sources... [  4%] admin/manage-flavors
> reading sources... [  5%] admin/manage-host-aggregates
> reading sources... [  7%] admin/manage-images
> reading sources... [  8%] admin/manage-instances
> reading sources... [  9%] admin/manage-projects-and-users
> reading sources... [ 10%] admin/manage-services
> reading sources... [ 11%] admin/manage-volumes
> reading sources... [ 12%] admin/sessions
> reading sources... [ 13%] admin/set-quotas
> reading sources... [ 14%] configuration/branding
> reading sources... [ 15%] configuration/customizing
> reading sources... [ 16%] configuration/index
> reading sources... [ 18%] configuration/pluggable_panels
> reading sources... [ 19%] configuration/settings
> reading sources... [ 20%] configuration/themes
> reading sources... [ 21%] contributor/contributing
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-bxw6fyoq.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[1]: *** [debian/rules:30: override_dh_auto_build] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/horizon_23.1.0-3_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

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

If you reassign this bug to another package, please marking it as 

Bug#1054677: marked as done (ableton-link: FTBFS: CatchWrapper.hpp:38:10: fatal error: catch.hpp: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 15:04:04 +
with message-id 
and subject line Bug#1054677: fixed in ableton-link 3.1.0+dfsg-2
has caused the Debian Bug report #1054677,
regarding ableton-link: FTBFS: CatchWrapper.hpp:38:10: fatal error: catch.hpp: 
No such file or directory
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.)


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

Hi,

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


Relevant part (hopefully):
> cd /<>/obj-x86_64-linux-gnu/examples && /usr/bin/c++ 
> -DLINKHUT_AUDIO_PLATFORM_JACK=1 -DLINK_PLATFORM_LINUX=1 
> -DLINK_PLATFORM_UNIX=1 -I/<>/examples/linkaudio -isystem 
> /<>/include -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 
> -I/usr/include/catch2 -Werror -Wno-multichar -O2 -g -DNDEBUG -MD -MT 
> examples/CMakeFiles/LinkHut.dir/linkaudio/AudioEngine.cpp.o -MF 
> CMakeFiles/LinkHut.dir/linkaudio/AudioEngine.cpp.o.d -o 
> CMakeFiles/LinkHut.dir/linkaudio/AudioEngine.cpp.o -c 
> /<>/examples/linkaudio/AudioEngine.cpp
> In file included from 
> /<>/src/ableton/discovery/tst_Payload.cpp:22:
> /<>/include/ableton/test/CatchWrapper.hpp:38:10: fatal error: 
> catch.hpp: No such file or directory
>38 | #include 
>   |  ^~~
> compilation terminated.
> make[3]: *** [src/CMakeFiles/LinkDiscoveryTest.dir/build.make:93: 
> src/CMakeFiles/LinkDiscoveryTest.dir/ableton/discovery/tst_Payload.cpp.o] 
> Error 1


The full build log is available from:
http://qa-logs.debian.net/2023/10/27/ableton-link_3.1.0+dfsg-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ableton-link
Source-Version: 3.1.0+dfsg-2
Done: IOhannes m zmölnig (Debian/GNU) 

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

Debian distribution maintenance software
pp.
IOhannes m zmölnig (Debian/GNU)  (supplier of updated 
ableton-link 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, 30 Oct 2023 15:40:19 +0100
Source: ableton-link
Architecture: source
Version: 3.1.0+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers 
Changed-By: IOhannes m zmölnig (Debian/GNU) 
Closes: 1054677
Changes:
 ableton-link (3.1.0+dfsg-2) unstable; urgency=medium
 .
   * Fix FTBFS with catch3 (Closes: #1054677)
Checksums-Sha1:
 43052139a5c8ff26fa1344fe5f798a6a024ceeaf 2393 ableton-link_3.1.0+dfsg-2.dsc
 4fb063707b74b7c04e5e58d6d631fc219801b76b 7972 
ableton-link_3.1.0+dfsg-2.debian.tar.xz
Checksums-Sha256:
 0d6147afa086e743091b17aec7074fd6b53e6529a2e94211a4ebdbba68b83d26 2393 
ableton-link_3.1.0+dfsg-2.dsc
 0aa28eab059794793018798c119da73d61b99a1ca31bcfbc11b2b66dae727865 7972 
ableton-link_3.1.0+dfsg-2.debian.tar.xz
Files:
 2bce355ed89340e08ab5a9a16ac86942 2393 sound optional 
ableton-link_3.1.0+dfsg-2.dsc
 8da1378b81580d0a62896c359bc40adb 7972 sound optional 
ableton-link_3.1.0+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

Bug#1045016: marked as done (fenics-ufl: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 15:04:58 +
with message-id 
and subject line Bug#1045016: fixed in fenics-ufl 2023.2.0-2
has caused the Debian Bug report #1045016,
regarding fenics-ufl: Fails to build source after successful build
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.)


-- 
1045016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fenics-ufl
Version: 2023.1.1.post0-6
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> 
> 
> dpkg-buildpackage: info: source package fenics-ufl
> dpkg-buildpackage: info: source version 2023.1.1.post0-6
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Drew Parsons 
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
>debian/rules execute_after_dh_auto_clean
> make[1]: Entering directory '/<>'
> /usr/bin/make -C doc/sphinx clean
> make[2]: Entering directory '/<>/doc/sphinx'
> rm -rf build/*
> make[2]: Leaving directory '/<>/doc/sphinx'
> make[1]: Leaving directory '/<>'
>dh_autoreconf_clean -O--buildsystem=pybuild
>debian/rules override_dh_clean
> make[1]: Entering directory '/<>'
> dh_clean
> rm -rf *.egg-info
> make[1]: Leaving directory '/<>'
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building fenics-ufl using existing 
> ./fenics-ufl_2023.1.1.post0.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  fenics-ufl-2023.1.1.post0/doc/sphinx/source/api-doc/ufl.algorithms.rst
>  fenics-ufl-2023.1.1.post0/doc/sphinx/source/api-doc/ufl.core.rst
>  fenics-ufl-2023.1.1.post0/doc/sphinx/source/api-doc/ufl.corealg.rst
>  fenics-ufl-2023.1.1.post0/doc/sphinx/source/api-doc/ufl.finiteelement.rst
>  fenics-ufl-2023.1.1.post0/doc/sphinx/source/api-doc/ufl.formatting.rst
>  fenics-ufl-2023.1.1.post0/doc/sphinx/source/api-doc/ufl.rst
>  fenics-ufl-2023.1.1.post0/doc/sphinx/source/api-doc/ufl.utils.rst
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/fenics-ufl_2023.1.1.post0-6.diff.ZuwChs
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/fenics-ufl_2023.1.1.post0-6_unstable.log

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: fenics-ufl
Source-Version: 2023.2.0-2
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew 

Bug#1054805: marked as done (Please update crash to 8.0.3)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 14:49:09 +
with message-id 
and subject line Bug#1054805: fixed in crash 8.0.3-1
has caused the Debian Bug report #1054805,
regarding Please update crash to 8.0.3
to be marked as done.

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

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


-- 
1054805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054805
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:crash
Version: 8.0.2-1
Severity: wishlist

Hi Troy,

If at all possible, could you please update Debian sid to crash 8.0.3?

I'm happy to try helping prepare it, although I don't have upload rights.

Thanks,

-- 
Mauricio Faria de Oliveira
--- End Message ---
--- Begin Message ---
Source: crash
Source-Version: 8.0.3-1
Done: Troy Heber 

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

Debian distribution maintenance software
pp.
Troy Heber  (supplier of updated crash 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, 28 Oct 2023 12:21:36 -0600
Source: crash
Architecture: source
Version: 8.0.3-1
Distribution: unstable
Urgency: medium
Maintainer: Troy Heber 
Changed-By: Troy Heber 
Closes: 1054805
Changes:
 crash (8.0.3-1) unstable; urgency=medium
 .
   * New upstream (Closes: #1054805)
   * https://github.com/crash-utility/crash/compare/8.0.2...8.0.3
Checksums-Sha1:
 7699401b2809850e5be80531f6fe89d60d978baf 1948 crash_8.0.3-1.dsc
 d154d57291952baea7929b706d76a91edd07552e 1330456 crash_8.0.3.orig.tar.gz
 086d3f305a65d17f73fa3e3a5452629bca778a26 150084 crash_8.0.3-1.debian.tar.xz
 f8aa34863259a1cc3b02f8d6803d1f9d945d0e2b 6677 crash_8.0.3-1_source.buildinfo
Checksums-Sha256:
 a736b3ca1b607575f1125a2893eea024ee08db4924c8074428f28b770d83 1948 
crash_8.0.3-1.dsc
 22750c927286296e574991edfa9e7bf43bfe4bf9f1163615f08b210854bcb2bd 1330456 
crash_8.0.3.orig.tar.gz
 56d2a76e0be6e5114331de9cbcedfd7e256ab5f5f0a96f4a8dd89e7a5f8a25ff 150084 
crash_8.0.3-1.debian.tar.xz
 d94351ad913e38925800cbf35364d858fd7dde98b857de848a963f4a7fcf7335 6677 
crash_8.0.3-1_source.buildinfo
Files:
 269ad126571ec8efb77ed430e364115e 1948 utils optional crash_8.0.3-1.dsc
 c89a2db64fb3527473dad1a2bd366c02 1330456 utils optional crash_8.0.3.orig.tar.gz
 50291c7d31f0f9f2a385a56f5ae022fb 150084 utils optional 
crash_8.0.3-1.debian.tar.xz
 401b30b3ec00164e3d6684002e3cf136 6677 utils optional 
crash_8.0.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEPdPUPs0+tNeF/HYE23wDYLLLZZcFAmU/sqQACgkQ23wDYLLL
ZZe1WQ/+PpUd29dMVmmJtGhQrPDH1jc98g0Rl0c7iHrTxbpw0Bzk8F1F+9anHI18
VF9JD2e4TjuByrvCt0KQ0Pi+sjsWvzvSn3SpE7t2HfrcIaXBT513ZcfNStdyaASM
XcA3rsqz+UTAFDML3gooFUukhKEhtprVJQKTvZBGWZKMzI5D5gEz0RiS2Z0pjG3k
TQPT39AZHoaO7VRDvGTocLt+sNR8bDU3tVPDD6SBghzE4UB+wDKqRshPmU/1mqVz
shBoTOWJkoVrQyvelxBxVLa0Ooz5dBXcsOef0FMW89ROczo++mvkeQlqFrSJgZNJ
Qe3LFbZNsXDzM4mqN53z9AqHICEGAEeUf0LgRC1kMD3RK9HjY2RbQAgyTbVjLUbh
wC1S51H9Q5ZTmvyRS0NTkZuUzi5TtASJoZ2s+AFLJjIWF9WlDhZJ2TY9CTDOuDZ0
dgbC55QJkeEiuHN6RUP4RJpFJF2drZZpreTgZjM5AZ9QwJJSD62JWZMggh9tIYNA
tvYfhdvRhDWm89mlLvtZXy/VixZoLsF41y+K9u5/AQs9Hfdbq24bdZC9pGykBVlM
B5doqttlOgkZrnqq5bOkU5roYekDIuEdBGG57KrBq+LRV60lxeymF53O99nQmT+C
wS8+sF+akNLBo/XjbRnxdtZTEtmJ1to0aGLO9hgd0wSs+oFfKKw=
=tFWh
-END PGP SIGNATURE End Message ---

Bug#1054696: marked as done (gdcm: FTBFS: gdcm_charls.h:21:11: fatal error: CharLS/charls.h: No such file or directory)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 14:49:28 +
with message-id 
and subject line Bug#1054696: fixed in gdcm 3.0.22-1
has caused the Debian Bug report #1054696,
regarding gdcm: FTBFS: gdcm_charls.h:21:11: fatal error: CharLS/charls.h: No 
such file or directory
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.)


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

Hi,

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


Relevant part (hopefully):
> /usr/bin/c++ -DgdcmMSFF_EXPORTS -I/<>/Source/Common 
> -I/<>/obj-x86_64-linux-gnu/Source/Common 
> -I/<>/Source/DataStructureAndEncodingDefinition 
> -I/<>/Source/DataDictionary 
> -I/<>/Source/InformationObjectDefinition 
> -I/<>/Source/MediaStorageAndFileFormat 
> -I/<>/Utilities 
> -I/<>/obj-x86_64-linux-gnu/Utilities -I/usr/include/openjpeg-2.5 
> -I/usr/include/json-c -I/usr/include/json -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DCHARLS_DLL -MD -MT 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o
>  -MF 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o.d
>  -o 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o
>  -c /<>/Source/MediaStorageAndFileFormat/gdcmJPEGLSCodec.cxx
> In file included from 
> /<>/Source/MediaStorageAndFileFormat/gdcmJPEGLSCodec.cxx:24:
> /<>/Utilities/gdcm_charls.h:21:11: fatal error: CharLS/charls.h: 
> No such file or directory
>21 | # include 
>   |   ^
> compilation terminated.
> [374/607] /usr/bin/c++ -DgdcmMSFF_EXPORTS -I/<>/Source/Common 
> -I/<>/obj-x86_64-linux-gnu/Source/Common 
> -I/<>/Source/DataStructureAndEncodingDefinition 
> -I/<>/Source/DataDictionary 
> -I/<>/Source/InformationObjectDefinition 
> -I/<>/Source/MediaStorageAndFileFormat 
> -I/<>/Utilities 
> -I/<>/obj-x86_64-linux-gnu/Utilities -I/usr/include/openjpeg-2.5 
> -I/usr/include/json-c -I/usr/include/json -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MT 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmAudioCodec.cxx.o 
> -MF 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmAudioCodec.cxx.o.d
>  -o 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmAudioCodec.cxx.o 
> -c /<>/Source/MediaStorageAndFileFormat/gdcmAudioCodec.cxx
> [375/607] /usr/bin/c++ -DgdcmMSFF_EXPORTS -I/<>/Source/Common 
> -I/<>/obj-x86_64-linux-gnu/Source/Common 
> -I/<>/Source/DataStructureAndEncodingDefinition 
> -I/<>/Source/DataDictionary 
> -I/<>/Source/InformationObjectDefinition 
> -I/<>/Source/MediaStorageAndFileFormat 
> -I/<>/Utilities 
> -I/<>/obj-x86_64-linux-gnu/Utilities -I/usr/include/openjpeg-2.5 
> -I/usr/include/json-c -I/usr/include/json -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MT 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEG16Codec.cxx.o
>  -MF 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEG16Codec.cxx.o.d
>  -o 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEG16Codec.cxx.o
>  -c /<>/Source/MediaStorageAndFileFormat/gdcmJPEG16Codec.cxx
> [376/607] /usr/bin/c++ -DgdcmMSFF_EXPORTS -I/<>/Source/Common 
> -I/<>/obj-x86_64-linux-gnu/Source/Common 
> -I/<>/Source/DataStructureAndEncodingDefinition 
> -I/<>/Source/DataDictionary 
> -I/<>/Source/InformationObjectDefinition 
> -I/<>/Source/MediaStorageAndFileFormat 
> -I/<>/Utilities 
> -I/<>/obj-x86_64-linux-gnu/Utilities -I/usr/include/openjpeg-2.5 
> -I/usr/include/json-c -I/usr/include/json -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -MD -MT 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmPixmapWriter.cxx.o
>  -MF 
> Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmPixmapWriter.cxx.o.d
>  -o 
> 

Bug#1054338: marked as done (debian-edu-artwork: fails to remove, update-debian-edu-artwork-emerald: not found)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 14:34:20 +
with message-id 
and subject line Bug#1054338: fixed in debian-edu-artwork 2.12.3-2
has caused the Debian Bug report #1054338,
regarding debian-edu-artwork: fails to remove, 
update-debian-edu-artwork-emerald: not found
to be marked as done.

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

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


-- 
1054338: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054338
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-edu-artwork
Version: 2.12.3-1
Severity: serious

Dear Maintainer,

debian-edu-artwork-emerald fails to remove,
quoting https://piuparts.debian.org/sid/fail/debian-edu-artwork_2.12.3-1.log

0m32.5s DEBUG: Starting command: ['chroot', 
'/srv/piuparts.debian.org/tmp/tmpsyd_96oo', 'apt-get', 'remove', 'adduser', 
'dbus', 'dbus-bin', 'dbus-daemon', 'dbus-session-bus-common', 
'dbus-system-bus-common', 'dbus-user-session', 'dconf-gsettings-backend:amd64', 
'dconf-service', 'debian-edu-artwork-emerald', 'desktop-base', 'dmsetup', 
'fontconfig', 'fontconfig-config', 'fonts-dejavu-core', 'fonts-dejavu-mono', 
'fonts-quicksand', 'libapparmor1:amd64', 'libargon2-1:amd64', 
'libbrotli1:amd64', 'libbsd0:amd64', 'libcairo-gobject2:amd64', 
'libcairo2:amd64', 'libconfig-inifiles-perl', 'libcryptsetup12:amd64', 
'libdatrie1:amd64', 'libdbus-1-3:amd64', 'libdconf1:amd64', 
'libdeflate0:amd64', 'libdevmapper1.02.1:amd64', 'libexpat1:amd64', 
'libfdisk1:amd64', 'libfontconfig1:amd64', 'libfreetype6:amd64', 
'libfribidi0:amd64', 'libgdk-pixbuf-2.0-0:amd64', 'libgdk-pixbuf2.0-common', 
'libglib2.0-0:amd64', 'libgraphite2-3:amd64', 'libharfbuzz0b:amd64', 
'libicu72:amd64', 'libip4tc2:amd64', 'libjbig0:amd64', 'libjpeg62-turbo:amd64', 
'libjson-c5:amd64', 'libkmod2:amd64', 'liblerc4:amd64', 'libncursesw6:amd64', 
'libpam-systemd:amd64', 'libpango-1.0-0:amd64', 'libpangocairo-1.0-0:amd64', 
'libpangoft2-1.0-0:amd64', 'libpixman-1-0:amd64', 'libpng16-16:amd64', 
'libproc2-0:amd64', 'librsvg2-2:amd64', 'librsvg2-common:amd64', 
'libsharpyuv0:amd64', 'libssl3:amd64', 'libsystemd-shared:amd64', 
'libthai-data', 'libthai0:amd64', 'libtiff6:amd64', 'libwebp7:amd64', 
'libx11-6:amd64', 'libx11-data', 'libxau6:amd64', 'libxcb-render0:amd64', 
'libxcb-shm0:amd64', 'libxcb1:amd64', 'libxdmcp6:amd64', 'libxext6:amd64', 
'libxml2:amd64', 'libxrender1:amd64', 'procps', 'shared-mime-info', 'systemd', 
'systemd-dev', 'systemd-sysv', 'debian-edu-artwork']
0m33.9s DUMP: 
  Reading package lists...
  Building dependency tree...
  Reading state information...
  The following packages will be REMOVED:
adduser dbus dbus-bin dbus-daemon dbus-session-bus-common
dbus-system-bus-common dbus-user-session dconf-gsettings-backend
dconf-service debian-edu-artwork debian-edu-artwork-emerald desktop-base
dmsetup fontconfig fontconfig-config fonts-dejavu-core fonts-dejavu-mono
fonts-quicksand libapparmor1 libargon2-1 libbrotli1 libbsd0
libcairo-gobject2 libcairo2 libconfig-inifiles-perl libcryptsetup12
libdatrie1 libdbus-1-3 libdconf1 libdeflate0 libdevmapper1.02.1 libexpat1
libfdisk1 libfontconfig1 libfreetype6 libfribidi0 libgdk-pixbuf-2.0-0
libgdk-pixbuf2.0-common libglib2.0-0 libgraphite2-3 libharfbuzz0b libicu72
libip4tc2 libjbig0 libjpeg62-turbo libjson-c5 libkmod2 liblerc4 libncursesw6
libpam-systemd libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0
libpixman-1-0 libpng16-16 libproc2-0 librsvg2-2 librsvg2-common libsharpyuv0
libssl3 libsystemd-shared libthai-data libthai0 libtiff6 libwebp7 libx11-6
libx11-data libxau6 libxcb-render0 libxcb-shm0 libxcb1 libxdmcp6 libxext6
libxml2 libxrender1 procps shared-mime-info systemd systemd-dev systemd-sysv
  0 upgraded, 0 newly installed, 80 to remove and 0 not upgraded.
  After this operation, 141 MB disk space will be freed.
  (Reading database ... 
  (Reading database ... 100%
  (Reading database ... 8324 files and directories currently installed.)
  Removing debian-edu-artwork (2.12.3-1) ...
  update-alternatives: warning: forcing reinstallation of alternative 
/usr/share/desktop-base/active-theme/login/background.svg because link group 
desktop-login-background is broken
  Removing dconf-gsettings-backend:amd64 (0.40.0-4) ...
  Removing dconf-service (0.40.0-4) ...
  Removing dbus-user-session (1.14.10-1) ...
  Removing libpam-systemd:amd64 (254.5-1) ...
  Removing dbus (1.14.10-1) ...
  Running in chroot, ignoring request.
  invoke-rc.d: policy-rc.d denied execution of stop.
  Removing dbus-system-bus-common (1.14.10-1) ...
  Removing adduser (3.137) ...
  Removing dbus-daemon 

Bug#1053714: marked as done (haskell-yi-core: ghc 9.4.6: unrecognised flag: -XNoMonadFailDesugaring)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 13:49:12 +
with message-id 
and subject line Bug#1053714: fixed in haskell-yi-core 0.19.2-3
has caused the Debian Bug report #1053714,
regarding haskell-yi-core: ghc 9.4.6: unrecognised flag: -XNoMonadFailDesugaring
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.)


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

Source: haskell-yi-core
Version: 0.19.2-2
Severity: wishlist
Tags: ftbfs
User: debian-de...@lists.debian.org
Usertags: loongarch64

Dear maintainers,

When compiling the package haskell-yi-core for loong64 in the Debian 
Package Auto-Building environment [1], The error message is as follows:

..Omit
Building library for yi-core-0.19.2..
ghc: unrecognised flag: -XNoMonadFailDesugaring
..Omit
# ghc --version
The Glorious Glasgow Haskell Compilation System, version 9.4.6
The full compilation log can be found at [2].

Other architectures use ghc version 9.0.2 to compile haskell-yi-core 
properly, refer to riscv64's compilation log [3].

Please stay tuned for our feedback on this phenomenon.
If you have any questions, you can contact me at any time.

[1]:https://buildd.debian.org/status/package.php?p=haskell-yi-core=sid
[2]:https://buildd.debian.org/status/logs.php?pkg=haskell-yi-core=0.19.2-2=loong64
[3]:https://buildd.debian.org/status/fetch.php?pkg=haskell-yi-core=riscv64=0.19.2-2=1692487915=0

thanks,
Dandan Zhang
--- End Message ---
--- Begin Message ---
Source: haskell-yi-core
Source-Version: 0.19.2-3
Done: Ilias Tsitsimpis 

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

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

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-yi-core 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 15:20:22 +0200
Source: haskell-yi-core
Architecture: source
Version: 0.19.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1053633 1053714 1054848
Changes:
 haskell-yi-core (0.19.2-3) unstable; urgency=medium
 .
   [ Ilias Tsitsimpis ]
   * Declare compliance with Debian policy 4.6.2
 .
   [ Marcel Fourné ]
   * Add 0002-update-for-unix-compat-0.7.patch, applied upstream (Closes: 
#1053633)
   * Remove 0001-add-nomonadfaildesugaring.patch (Closes: #1054848, #1053714)
Checksums-Sha1:
 f8f2c0bf9ecb28450f8fd2ec5443d8f2c8b38652 3912 haskell-yi-core_0.19.2-3.dsc
 420f487b709101264634b977afefa4ec7d14da13 5448 
haskell-yi-core_0.19.2-3.debian.tar.xz
 ed756747700b991d20a5568c0004ea43959ac9e7 6145 
haskell-yi-core_0.19.2-3_source.buildinfo
Checksums-Sha256:
 a44bc8af0007bc522d46725b2f16bd078179f908b542b9b43dc45c00295a6fd0 3912 
haskell-yi-core_0.19.2-3.dsc
 d71a45bfa11ec849e20c1cb925e7f3f4cc3d1f63329bcf3ced3c99e609754025 5448 
haskell-yi-core_0.19.2-3.debian.tar.xz
 68feb943852a837326e7c26e5c53bc2714c374877a9236a85ed8406425b82bb9 6145 
haskell-yi-core_0.19.2-3_source.buildinfo
Files:
 90428e7c7ad2bbc40033176c319370e1 3912 haskell optional 
haskell-yi-core_0.19.2-3.dsc
 cfb252b51f0ac4e6097e7e0c3ff1a132 5448 haskell optional 
haskell-yi-core_0.19.2-3.debian.tar.xz
 b8a3443611beb3c6cc659e956f566257 6145 haskell optional 
haskell-yi-core_0.19.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmU/sCsUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzHORAApYLmkJ9hWjacLoRwGBXudgU+Stm7
34yZ/lZl+QjhfPeM6bzCePlKVPTxcqLSPjxvGa6GT3LtPSTVHvMi9GmAePY9iFCG
fkwYXd/lEg71x6EiJ3zb8Lx6H9VGG9US/fpcZVT5R9qcIFHomxdlkwPV8u3F9zqT
fEiAkPxcDk0Ym5kCgwKSLjVwNS/H3TerhxXViHWmeT5CSIHsaeCCXsLP+l/SQV6O
ek2NF8NUR0O5RhbM3WKFhjLKLCOx9hn1xSO4j6GDL5zW7M2edlaIVMelOsbdoXj7
KstDbMyYjxuYTN4eg+Zy204CzM7YMQEZVH5y/zWUvN1zj2CrGEX0u1KTm2KxR+gl
6b1Ag+Z//haZW6ULTbMhuyYEKYsnIDEXgPuP+BvW7SKH/M/gRhAwhD+6gjN0MR0F
zzmTMo9dpE5Vn+ocVaXkDL7AF2Hs23smeIf1ZFnVmdWksGB7h/QoEtYAYpX0VjHT
PSVuexG1h4mjEtP4fXp3NpdrcTTcs7KW2eUmpY0z68My6KnmlYv54oR0jpztgBoK

Bug#1054848: marked as done (haskell-yi-core: FTBFS: make: *** [/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 13:49:12 +
with message-id 
and subject line Bug#1054848: fixed in haskell-yi-core 0.19.2-3
has caused the Debian Bug report #1054848,
regarding haskell-yi-core: FTBFS: make: *** 
[/usr/share/cdbs/1/class/hlibrary.mk:158: build-ghc-stamp] Error 25
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.)


-- 
1054848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054848
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-yi-core
Version: 0.19.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20231027 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> test -x debian/rules
> dh_testroot
> dh_prep 
> dh_installdirs -A 
> mkdir -p "."
> CDBS WARNING:DEB_DH_STRIP_ARGS is deprecated since 0.4.85
> CDBS WARNING:DEB_COMPRESS_EXCLUDE is deprecated since 0.4.85
> Adding cdbs dependencies to debian/libghc-yi-core-doc.substvars
> dh_installdirs -plibghc-yi-core-doc \
>   
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'make_setup_recipe'
> Running ghc --make Setup.hs -o debian/hlibrary.setup
> [1 of 2] Compiling Main ( Setup.hs, Setup.o )
> [2 of 2] Linking debian/hlibrary.setup
> perl -d:Confess -MDebian::Debhelper::Buildsystem::Haskell::Recipes=/.*/ \
>   -E 'configure_recipe'
> Running find . ! -newer /tmp/ljJz8gddW_ -exec touch -d 1998-01-01 UTC {} ;
> Running dh_listpackages
> libghc-yi-core-dev
> libghc-yi-core-prof
> libghc-yi-core-doc
> Running dh_listpackages
> libghc-yi-core-dev
> libghc-yi-core-prof
> libghc-yi-core-doc
> Running dpkg-buildflags --get LDFLAGS
> -Wl,-z,relro
> Running debian/hlibrary.setup configure --ghc -v2 
> --package-db=/var/lib/ghc/package.conf.d --prefix=/usr 
> --libdir=/usr/lib/haskell-packages/ghc/lib --libexecdir=/usr/lib 
> --builddir=dist-ghc --ghc-option=-optl-Wl,-z,relro 
> --haddockdir=/usr/lib/ghc-doc/haddock/yi-core-0.19.2/ --datasubdir=yi-core 
> --htmldir=/usr/share/doc/libghc-yi-core-doc/html/ --enable-library-profiling
> Using Parsec parser
> Configuring yi-core-0.19.2...
> Flags chosen: hint=False
> Dependency ListLike >=4.5: using ListLike-4.7.8.2
> Dependency array: using array-0.5.4.0
> Dependency attoparsec: using attoparsec-0.14.4
> Dependency base >=4.8 && <5: using base-4.17.2.0
> Dependency binary >=0.7: using binary-0.8.9.1
> Dependency bytestring >=0.9.1: using bytestring-0.11.5.2
> Dependency containers: using containers-0.6.7
> Dependency data-default: using data-default-0.7.1.1
> Dependency directory: using directory-1.3.7.1
> Dependency dlist >=0.4.1: using dlist-1.0
> Dependency dynamic-state >=0.1.0.5: using dynamic-state-0.3.1
> Dependency exceptions: using exceptions-0.10.5
> Dependency filepath >=1.1: using filepath-1.4.2.2
> Dependency hashable >=1.1.2.5: using hashable-1.4.3.0
> Dependency microlens-platform: using microlens-platform-0.4.3.4
> Dependency mtl >=0.1.0.1: using mtl-2.2.2
> Dependency old-locale: using old-locale-1.0.0.7
> Dependency oo-prototypes: using oo-prototypes-0.1.0.0
> Dependency parsec >=3.0: using parsec-3.1.16.1
> Dependency pointedlist >=0.5: using pointedlist-0.6.1
> Dependency process >=1.0.1.1: using process-1.6.17.0
> Dependency process-extras >=0.3.3.8: using process-extras-0.7.4
> Dependency split >=0.2: using split-0.2.3.5
> Dependency text >=1.1.1.3: using text-2.0.2
> Dependency time >=1.1: using time-1.12.2
> Dependency transformers-base: using transformers-base-0.4.6
> Dependency unix: using unix-2.7.3
> Dependency unix-compat >=0.1: using unix-compat-0.7
> Dependency unordered-containers >=0.1.3: using unordered-containers-0.2.19.1
> Dependency xdg-basedir >=0.2.1: using xdg-basedir-0.2.2
> Dependency yi-language >=0.19: using yi-language-0.19.0
> Dependency yi-rope >=0.10: using yi-rope-0.11
> Source component graph: component lib
> Configured component graph:
> component yi-core-0.19.2-E1UEJ8UPYmGRHaW9PNDrO
> include ListLike-4.7.8.2-32jeCueTi8eFESqDxYHStH
> include array-0.5.4.0
> include attoparsec-0.14.4-X3HtT4hfTY2sKaBlyGkhp
> include base-4.17.2.0
> include binary-0.8.9.1
> include bytestring-0.11.5.2
> include containers-0.6.7
> include data-default-0.7.1.1-4TeAZDN81Uu1IorgFaPMOc
> include directory-1.3.7.1
> include dlist-1.0-9arrzQ6gBJAKO2k1FjXdTZ
> include dynamic-state-0.3.1-8rCKNEuxgP5391Xha970eh
> include 

Bug#1053633: marked as done (haskell-yi-core: FTBFS with haskell-unix-compat >= 0.7)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 13:49:12 +
with message-id 
and subject line Bug#1053633: fixed in haskell-yi-core 0.19.2-3
has caused the Debian Bug report #1053633,
regarding haskell-yi-core: FTBFS with haskell-unix-compat >= 0.7
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.)


-- 
1053633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1053633
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: haskell-yi-core
Version: 0.19.2-2
Severity: serious
Tags: ftbfs
Justification: ftbfs
Forwarded: https://github.com/yi-editor/yi/issues/1133

This package FTBFS with the latest version of haskell-unix-compat, which
is part of Stackage LTS 21 and available in Debian unstable.

-- 
Ilias
--- End Message ---
--- Begin Message ---
Source: haskell-yi-core
Source-Version: 0.19.2-3
Done: Ilias Tsitsimpis 

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

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

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-yi-core 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 15:20:22 +0200
Source: haskell-yi-core
Architecture: source
Version: 0.19.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1053633 1053714 1054848
Changes:
 haskell-yi-core (0.19.2-3) unstable; urgency=medium
 .
   [ Ilias Tsitsimpis ]
   * Declare compliance with Debian policy 4.6.2
 .
   [ Marcel Fourné ]
   * Add 0002-update-for-unix-compat-0.7.patch, applied upstream (Closes: 
#1053633)
   * Remove 0001-add-nomonadfaildesugaring.patch (Closes: #1054848, #1053714)
Checksums-Sha1:
 f8f2c0bf9ecb28450f8fd2ec5443d8f2c8b38652 3912 haskell-yi-core_0.19.2-3.dsc
 420f487b709101264634b977afefa4ec7d14da13 5448 
haskell-yi-core_0.19.2-3.debian.tar.xz
 ed756747700b991d20a5568c0004ea43959ac9e7 6145 
haskell-yi-core_0.19.2-3_source.buildinfo
Checksums-Sha256:
 a44bc8af0007bc522d46725b2f16bd078179f908b542b9b43dc45c00295a6fd0 3912 
haskell-yi-core_0.19.2-3.dsc
 d71a45bfa11ec849e20c1cb925e7f3f4cc3d1f63329bcf3ced3c99e609754025 5448 
haskell-yi-core_0.19.2-3.debian.tar.xz
 68feb943852a837326e7c26e5c53bc2714c374877a9236a85ed8406425b82bb9 6145 
haskell-yi-core_0.19.2-3_source.buildinfo
Files:
 90428e7c7ad2bbc40033176c319370e1 3912 haskell optional 
haskell-yi-core_0.19.2-3.dsc
 cfb252b51f0ac4e6097e7e0c3ff1a132 5448 haskell optional 
haskell-yi-core_0.19.2-3.debian.tar.xz
 b8a3443611beb3c6cc659e956f566257 6145 haskell optional 
haskell-yi-core_0.19.2-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmU/sCsUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDzHORAApYLmkJ9hWjacLoRwGBXudgU+Stm7
34yZ/lZl+QjhfPeM6bzCePlKVPTxcqLSPjxvGa6GT3LtPSTVHvMi9GmAePY9iFCG
fkwYXd/lEg71x6EiJ3zb8Lx6H9VGG9US/fpcZVT5R9qcIFHomxdlkwPV8u3F9zqT
fEiAkPxcDk0Ym5kCgwKSLjVwNS/H3TerhxXViHWmeT5CSIHsaeCCXsLP+l/SQV6O
ek2NF8NUR0O5RhbM3WKFhjLKLCOx9hn1xSO4j6GDL5zW7M2edlaIVMelOsbdoXj7
KstDbMyYjxuYTN4eg+Zy204CzM7YMQEZVH5y/zWUvN1zj2CrGEX0u1KTm2KxR+gl
6b1Ag+Z//haZW6ULTbMhuyYEKYsnIDEXgPuP+BvW7SKH/M/gRhAwhD+6gjN0MR0F
zzmTMo9dpE5Vn+ocVaXkDL7AF2Hs23smeIf1ZFnVmdWksGB7h/QoEtYAYpX0VjHT
PSVuexG1h4mjEtP4fXp3NpdrcTTcs7KW2eUmpY0z68My6KnmlYv54oR0jpztgBoK
svKjJtlRgoK1cDixY2poPoGYRPhF9/Gj6/EN4JNuhZDD2z60qQ+2fX4f7uH+E/Oh
rhdKTIfvQPiLurIAoERw441STDMtRshj/kuRJ6F5+M+ciXGbqL7TQCatfzETRqk7
+Xdzw/GEwdcfDTA=
=efW3
-END PGP SIGNATURE End Message ---

Bug#1052305: marked as done (haskell-libbf: FTBFS on 32 bit architectures)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 13:34:02 +
with message-id 
and subject line Bug#1052305: fixed in haskell-libbf 0.6.6-2
has caused the Debian Bug report #1052305,
regarding haskell-libbf: FTBFS on 32 bit architectures
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.)


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

https://buildd.debian.org/status/fetch.php?pkg=haskell-libbf=i386=0.6.6-1=1693660180=0

libghc-libbf-dev
libghc-libbf-prof
libghc-libbf-doc
Running 1 test suites...
Test suite libBF-tests: RUNNING...
E: Build killed with signal TERM after 150 minutes of inactivity

Cheers
-- 
Sebastian Ramacher
--- End Message ---
--- Begin Message ---
Source: haskell-libbf
Source-Version: 0.6.6-2
Done: Ilias Tsitsimpis 

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

Debian distribution maintenance software
pp.
Ilias Tsitsimpis  (supplier of updated haskell-libbf 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 15:23:40 +0200
Source: haskell-libbf
Architecture: source
Version: 0.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Haskell Group 

Changed-By: Ilias Tsitsimpis 
Closes: 1052305
Changes:
 haskell-libbf (0.6.6-2) unstable; urgency=medium
 .
   * Disable tests that fail on 32bit systems (Closes: #1052305)
Checksums-Sha1:
 dc1d74b1082b8be08320c4cd2bbd5bd283ed00ff 2372 haskell-libbf_0.6.6-2.dsc
 ab506f20ac410a32bb8fe1004f7543a13a63abdb 3060 
haskell-libbf_0.6.6-2.debian.tar.xz
 ba4c3c2c4f123bd45e7c1395116eeb16694c0825 6133 
haskell-libbf_0.6.6-2_source.buildinfo
Checksums-Sha256:
 a9eb4dd64fd2eb9e79969306ce2cc7d993435b84cedeaf48aab569a1f76be970 2372 
haskell-libbf_0.6.6-2.dsc
 5ddcde4dd0e12e63081780352c575382b5ccc8675fbebf665466eb6ca7c434db 3060 
haskell-libbf_0.6.6-2.debian.tar.xz
 ba62bad842d2de93da06fe3290eb6289880679c5f6b3ed951e51e2139f7907a1 6133 
haskell-libbf_0.6.6-2_source.buildinfo
Files:
 0f847eae647235bda82ac8af47aaabfc 2372 haskell optional 
haskell-libbf_0.6.6-2.dsc
 53e66b5b533fdd087506b234995db4f2 3060 haskell optional 
haskell-libbf_0.6.6-2.debian.tar.xz
 c30d169a689eb155cfdbd70ae00385aa 6133 haskell optional 
haskell-libbf_0.6.6-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEEJ9c8pfW11+AaUTb116hngMxkQDwFAmU/sCMUHGlsaWFzdHNp
QGRlYmlhbi5vcmcACgkQ16hngMxkQDz1OA/+P486ZNv6LcjcIxj5AtK7z+/iemUZ
TnqxUNfYhaWQi9UwqCN/iIl1AxZJ9q9Kc0SSnO48vb22NpLK3vCdQyALyIWn5Kfn
zNTgiqYigAqTEumhion16Ri29jeAFl93O0/LGAMiKZuLp7xUkTeJ+zo2gmD9xXMl
9ZBXHuT/i/6qGwG6C7lw3RZKneHVW7Gw/DRIN0PBcHgWaWnFi4MDWLcXmGPEjllU
GZLDYLLpVqO+hzIitZ8hfprZ5NwPkotc+XvPZvDYolaYOPAWYVU3ItFZu4Vhokc2
Y8CWPirLg2XTziUUaKMJ8//EZ+dDp5LHUscCy7qF8/764naJpiYXsRfdo4hW239W
4/4Xyr7v2ofjEr/5uQ7EaxY8ybC04GQW91lKLBHI3I2J1Jtdiig5u+WxDKmB5Zo8
V3DRLX1hUhBximgwT1cs5eO2LlMSaW6O+24BxMPcAaUDQoYNBuk0sB3t6FWFn61B
6UgBHTH10Ge4n9TiM50VZsOj6ae7dxFqVFnIPF3J7mpG7oUpyLRkvW8wG7+F0z1D
o5O8+baYAcdzKaqdh0JvWXgcJ0HixMv3/l31gb/lCEvUzz28yKlr+RKpf4yQqG6M
xMK3YLiTWPhe0KoQj9ZTIyJvCkM4N+v+MBzz2wMr9rhWisbaqZ+I02PMlLHzSYwg
hAq3Xv7BDR3aIXA=
=bQ4t
-END PGP SIGNATURE End Message ---

Bug#1054921: marked as done (quantlib-swig: FTBFS on mips64el)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 12:49:55 +
with message-id 
and subject line Bug#1054921: fixed in quantlib-swig 1.32-2
has caused the Debian Bug report #1054921,
regarding quantlib-swig: FTBFS on mips64el
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.)


-- 
1054921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054921
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: quantlib-swig
Version: 1.32-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=quantlib-swig=mips64el=1.32-1=1698321785=0

g++ -shared -Wl,-O1 -Wl,-Bsymbolic-functions -O0 -g0 -mxgot --param 
ggc-min-expand=20 -DBOOST_NO_AUTO_PTR 
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o 
-L/usr/lib/mips64el-linux-gnuabi64 -L/usr/lib -lQuantLib -o 
build/lib.linux-mips64-cpython-311/QuantLib/_QuantLib.cpython-311-mips64el-linux-gnuabi64.so
 -fopenmp
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`virtual thunk to QuantLib::HimalayaOption::arguments::~arguments()':
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption9argumentsD1Ev[_ZN8QuantLib14HimalayaOption9argumentsD1Ev]+0x104):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption9argumentsD1Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`non-virtual thunk to QuantLib::HimalayaOption::results::~results()':
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption7resultsD1Ev[_ZN8QuantLib14HimalayaOption7resultsD1Ev]+0xf0):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption7resultsD1Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`virtual thunk to QuantLib::HimalayaOption::results::~results()':
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption7resultsD1Ev[_ZN8QuantLib14HimalayaOption7resultsD1Ev]+0x118):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption7resultsD1Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`non-virtual thunk to QuantLib::HimalayaOption::results::~results()':
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption7resultsD0Ev[_ZN8QuantLib14HimalayaOption7resultsD0Ev]+0x8c):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption7resultsD0Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`virtual thunk to QuantLib::HimalayaOption::results::~results()':
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption7resultsD0Ev[_ZN8QuantLib14HimalayaOption7resultsD0Ev]+0xb4):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption7resultsD0Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`non-virtual thunk to 
QuantLib::GenericEngine::~GenericEngine()':
quantlib_wrap.cpp:(.text._ZN8QuantLib13GenericEngineINS_14HimalayaOption9argumentsENS1_7resultsEED2Ev[_ZN8QuantLib13GenericEngineINS_14HimalayaOption9argumentsENS1_7resultsEED5Ev]+0x110):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib13GenericEngineINS_14HimalayaOption9argumentsENS1_7resultsEED2Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`non-virtual thunk to 
QuantLib::GenericEngine::~GenericEngine()':
quantlib_wrap.cpp:(.text._ZN8QuantLib13GenericEngineINS_14HimalayaOption9argumentsENS1_7resultsEED0Ev[_ZN8QuantLib13GenericEngineINS_14HimalayaOption9argumentsENS1_7resultsEED5Ev]+0x8c):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib13GenericEngineINS_14HimalayaOption9argumentsENS1_7resultsEED0Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`non-virtual thunk to QuantLib::HimalayaOption::engine::~engine()':
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption6engineD2Ev[_ZN8QuantLib14HimalayaOption6engineD5Ev]+0xa4):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption6engineD2Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`non-virtual thunk to QuantLib::HimalayaOption::engine::~engine()':
quantlib_wrap.cpp:(.text._ZN8QuantLib14HimalayaOption6engineD0Ev[_ZN8QuantLib14HimalayaOption6engineD5Ev]+0x8c):
 relocation truncated to fit: R_MIPS_GOT_PAGE against 
`.text._ZN8QuantLib14HimalayaOption6engineD0Ev'
build/temp.linux-mips64-cpython-311/QuantLib/quantlib_wrap.o: in function 
`virtual thunk to 

Bug#1054760: marked as done (dqlite: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:49:05 +
with message-id 
and subject line Bug#1054542: fixed in dqlite 1.16.0-1
has caused the Debian Bug report #1054542,
regarding dqlite: FTBFS: dh_auto_test: error: make -j8 check 
"TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
> make[3]: Entering directory '/<>'
> FAIL: unit-test
> FAIL: integration-test
> 
>libdqlite 1.11.1: ./test-suite.log
> 
> 
> # TOTAL: 2
> # PASS:  0
> # SKIP:  0
> # XFAIL: 0
> # FAIL:  2
> # XPASS: 0
> # ERROR: 0
> 
> .. contents:: :depth: 2
> 
> FAIL: unit-test
> ===
> 
> Running test suite with seed 0x5a7e0f63...
> replication/exec[ ERROR ]
> Error: test/unit/test_replication.c:361: assertion failed: f->invoked is not 
> true
> Error: child killed by signal 6 (Aborted)
> replication/checkpoint  [ ERROR ]
> Error: test/unit/test_replication.c:414: assertion failed: rc2 == 0 (1 == 0)
> Error: child killed by signal 6 (Aborted)
> VfsOpen/exclusive   [ OK] [ 
> 0.0506 / 0.0453 CPU ]
> VfsOpen/again   [ OK] [ 
> 0.0634 / 0.0549 CPU ]
> VfsOpen/noent   [ OK] [ 
> 0.1826 / 0.1506 CPU ]
> VfsOpen/walBeforeDb [ OK] [ 
> 0.0578 / 0.0497 CPU ]
> VfsOpen/synchronous [ OK] [ 
> 0.00027372 / 0.00027378 CPU ]
> VfsOpen/oom [ OK] [ 
> 0.0458 / 0.0428 CPU ]
> VfsOpen/oomFilename [ OK] [ 
> 0.0417 / 0.0401 CPU ]
> VfsOpen/tmp [ OK] [ 
> 0.9895 / 0.9862 CPU ]
> VfsDelete/success   [ OK] [ 
> 0.0501 / 0.0476 CPU ]
> VfsDelete/enoent[ OK] [ 
> 0.0360 / 0.0337 CPU ]
> VfsAccess/success   [ OK] [ 
> 0.0571 / 0.0495 CPU ]
> VfsAccess/noent [ OK] [ 
> 0.0348 / 0.0326 CPU ]
> VfsFullPathname/success [ OK] [ 
> 0.1132 / 0.1089 CPU ]
> VfsClose/thenDelete [ OK] [ 
> 0.0511 / 0.0483 CPU ]
> VfsRead/neverWritten[ OK] [ 
> 0.0605 / 0.0539 CPU ]
> VfsWrite/dbHeader   [ OK] [ 
> 0.0513 / 0.0481 CPU ]
> VfsWrite/andReadPages   [ OK] [ 
> 0.0767 / 0.0675 CPU ]
> VfsWrite/oomPage[ OK] [ 
> 0.0555 / 0.0506 CPU ]
> VfsWrite/oomPageArray   [ OK] [ 
> 0.0584 / 0.0534 CPU ]
> VfsWrite/oomPageBuf [ OK] [ 
> 0.0465 / 0.0442 CPU ]
> VfsWrite/beyondLast [ OK] [ 
> 0.0544 / 0.0513 CPU ]
> VfsTruncate/database[ OK] [ 
> 0.0759 / 0.0724 CPU ]
> VfsTruncate/unexpected  [ OK] [ 
> 0.0538 / 0.0494 CPU ]
> VfsTruncate/empty   [ OK] [ 
> 0.0526 / 0.0480 CPU ]
> VfsTruncate/emptyGrow   [ OK] [ 
> 0.0485 / 0.0455 CPU ]
> VfsTruncate/misaligned  [ OK] [ 
> 0.0510 / 0.0494 CPU ]
> VfsShmMap/oom   
>   mem-fault-delay=0, mem-fault-repeat=1 [ OK] [ 
> 0.0323 / 0.0275 CPU ]
>   mem-fault-delay=1, mem-fault-repeat=1 [ OK] [ 
> 

Bug#1054542: marked as done (dqlite FTBFS with raft 0.17.7)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:49:05 +
with message-id 
and subject line Bug#1054542: fixed in dqlite 1.16.0-1
has caused the Debian Bug report #1054542,
regarding dqlite FTBFS with raft 0.17.7
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.)


-- 
1054542: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054542
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dqlite
Version: 1.11.1-1
Severity: serious
Tags: ftbfs trixie sid
X-Debbugs-Cc: Free Ekanayaka 

https://buildd.debian.org/status/logs.php?pkg=dqlite=1.11.1-1%2Bb1

...
171 of 186 (92%) tests successful, 4 (2%) test skipped.
FAIL unit-test (exit status: 1)

FAIL: integration-test
==

Running test suite with seed 0xac33d156...
client/exec [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
client/query[ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
cluster/restart 
  num_records=0 [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=1 [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=256   [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=993   [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=2200  [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
cluster/dataOnNewNode   
  num_records=0 [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=1 [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=256   [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=993   [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=2200  [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
fsm/snapshotFreshDb [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
fsm/snapshotWrittenDb   [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
fsm/snapshotHeapFaultSingleDB   [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
fsm/snapshotHeapFaultTwoDB  [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
fsm/snapshotNewDbAddedBeforeFinalize[ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
fsm/snapshotWritesBeforeFinalize[ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
fsm/snapshotRestore 
  num_records=0 [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=1 [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: child killed by signal 6 (Aborted)
  num_records=256   [ ERROR ]
Error: test/lib/server.c:58: assertion failed: rv == 0 (1 == 0)
Error: 

Bug#1030320: marked as done (Upstream version 9.4.2-rc2 available)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 08:48:39 -0300
with message-id 
and subject line Re: tango: New version 9.4.1 available
has caused the Debian Bug report #1030320,
regarding Upstream version 9.4.2-rc2 available
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.)


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

We would really like to have 9.4.1 [0] in upcoming debian bookworm
instead of the old 9.3.x.

I've already tested if our tests pass on debian testing on amd64, yes
they do [1].

The changes compared to 9.3.x are listed at [2]. Packaging wise the
biggest change is that we now only support cmake.

As you are using the TangoSourceDistribution we have some info posted
at [3] wrt to the cmake options.

Thanks,
Thomas

[0]: https://gitlab.com/tango-controls/cppTango/-/releases/9.4.1
[1]: https://gitlab.com/tango-controls/cppTango/-/merge_requests/1044
[2]:
https://gitlab.com/tango-controls/cppTango/-/blob/main/RELEASE_NOTES.md
[3]:
https://gitlab.com/tango-controls/TangoSourceDistribution/-/tree/main/assets#installation
--- End Message ---
--- Begin Message ---
Version: tango/9.4.2+dfsg1-1

This was fixed in unstable with 9.4.2+dfsg1-1. changes files attached.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 10 Aug 2023 13:40:09 -0300
Source: tango
Architecture: source
Version: 9.4.2+dfsg1-1
Distribution: unstable
Urgency: low
Maintainer: Debian Science Maintainers 

Changed-By: Santiago Ruano Rincón 
Closes: 1039389
Changes:
 tango (9.4.2+dfsg1-1) unstable; urgency=low
 .
   * Team Upload
 .
   * New upstream version 9.4.2+dfsg1
   * Remove RELEASE: experimental in d/gitlab-ci.yml
   * Update Files-Excluded in d/copyright
   * Add d/patches/set-default-date-current_date-table-script.patch
   * Initial systemd support (Closes: #1039389). Thanks to Picca
 Frédéric-Emmanuel for the review!
   * Comment out Suggests: omninotify in tango-starter. omninotify is not found 
in debian
   * Add initial d/test/starter-basic autopkgtest
Checksums-Sha1:
 0aa8b69bb1358ea6bebba4b60df0f8f8ec294175 2045 tango_9.4.2+dfsg1-1.dsc
 00c5416d6237b218576f2d7dfa0b043981e5e87e 54912764 tango_9.4.2+dfsg1.orig.tar.xz
 8a4b762590742a9ed6b52f0512225a4b7e55d212 32916 
tango_9.4.2+dfsg1-1.debian.tar.xz
 be3f986c3b3c9f4767083d6c6de71b8d1e7ed6c0 13930 
tango_9.4.2+dfsg1-1_amd64.buildinfo
Checksums-Sha256:
 c236104ef3f0ce381415b2b549c3680e0de77edd3c6ebb49c84db528c4667f9d 2045 
tango_9.4.2+dfsg1-1.dsc
 e643fd6f04f214b6080b4d8e16cd0beb0147a969a0531589be327d3c4f7204db 54912764 
tango_9.4.2+dfsg1.orig.tar.xz
 893a5af427e53fcab97c6a04fed1ef7d2d0693fdd100b6bfb5685d45c8f6538e 32916 
tango_9.4.2+dfsg1-1.debian.tar.xz
 aef72c7dd4ac53c2003ae928a3d304ca0fd7a673605cbccac024239f153dcaa7 13930 
tango_9.4.2+dfsg1-1_amd64.buildinfo
Files:
 baa3c607962e8a4fa4001a1e46bcca31 2045 science optional tango_9.4.2+dfsg1-1.dsc
 aa6a57bccec5f6bc937b4aea9a74f580 54912764 science optional 
tango_9.4.2+dfsg1.orig.tar.xz
 5ee1da8da06e297ddea3615d451d241a 32916 science optional 
tango_9.4.2+dfsg1-1.debian.tar.xz
 49a9f46be080ea8044665da72b7db9eb 13930 science optional 
tango_9.4.2+dfsg1-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iHUEARYIAB0WIQRZVjztY8b+Ty43oH1itBCJKh26HQUCZNUVbQAKCRBitBCJKh26
HdZOAP9mYv65aPRsg/hXlat2zrq0++9sSnzv6qnCdDegPCujiAD/XXwnwAkNirV4
YO9gPJE8Z9dqdlsdl/6jnmfqtKP1QQQ=
=Gxa4
-END PGP SIGNATURE-


signature.asc
Description: PGP signature
--- End Message ---

Bug#1051516: marked as done (dqlite: New version available)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:49:05 +
with message-id 
and subject line Bug#1051516: fixed in dqlite 1.16.0-1
has caused the Debian Bug report #1051516,
regarding dqlite: New version available
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.)


-- 
1051516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: dqlite
Version: 1.11.1-1
Severity: wishlist

  I'd like to update golang-github-canonical-go-dqlite to its latest
release, but it depends on dqlite >= 1.13. When able, could you please
update dqlite to the latest version in sid?

  Also, if you'd like I would be happy to help co-maintain this package
as an uploader, since it's a dependency of lxd.

Thanks,
Mathias


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: dqlite
Source-Version: 1.16.0-1
Done: Mathias Gibbens 

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

Debian distribution maintenance software
pp.
Mathias Gibbens  (supplier of updated dqlite 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, 28 Oct 2023 22:05:39 +
Source: dqlite
Architecture: source
Version: 1.16.0-1
Distribution: unstable
Urgency: medium
Maintainer: Free Ekanayaka 
Changed-By: Mathias Gibbens 
Closes: 1051516 1054542
Changes:
 dqlite (1.16.0-1) unstable; urgency=medium
 .
   * New upstream release (Closes: #1054542, #1051516)
 .
   [ Free Ekanayaka ]
   * Set myself as Maintainer and Laszlo as Uploader
   * Bump Build-Depends on libraft-dev to version 0.17
   * Fix Description, which was mentioning raft instead of dqlite
   * Add Vcs fields pointing to the salsa repository
 .
   [ Mathias Gibbens ]
   * Add d/gbp.conf
   * d/copyright: Add Free and myself to debian/* stanza
   * d/control: Standards-Version 4.6.2, add myself as an uploader, and
 differentiate package descriptions
Checksums-Sha1:
 d7696a80b066ae4b657acd88c9655bda1d621d7d 2089 dqlite_1.16.0-1.dsc
 0caa97631ae62073af01f7bfb9882a35dcd93683 216783 dqlite_1.16.0.orig.tar.gz
 f8ce9decce374a65d029bc8abd8b23e929cd96ee 4540 dqlite_1.16.0-1.debian.tar.xz
 ed01d0a30b520a5edd73459a7a969e4befdf1514 6385 dqlite_1.16.0-1_amd64.buildinfo
Checksums-Sha256:
 bfff2fc1e23b9940bff8027ad49e67803721774d9a1a8de2e218a4839e0571b7 2089 
dqlite_1.16.0-1.dsc
 beb37049b766a2396d81b6128bf386a1f10c5f90b9be64b3fc200902fc59af13 216783 
dqlite_1.16.0.orig.tar.gz
 8db02ed7750f1b4eadebbac93a78e077c39a0ae017123b351c944d07d0165844 4540 
dqlite_1.16.0-1.debian.tar.xz
 26e2d31cd0606fc93ffb8878c67e9edaaab19b4b9d6e54127a99f321e5d87898 6385 
dqlite_1.16.0-1_amd64.buildinfo
Files:
 a7ee4bb56e535b21b457f3e4bc8c30fa 2089 devel optional dqlite_1.16.0-1.dsc
 cb250210678bef686f89cbadfb7952e6 216783 devel optional 
dqlite_1.16.0.orig.tar.gz
 55c506cc943083ed624cf3d4819c1f65 4540 devel optional 
dqlite_1.16.0-1.debian.tar.xz
 eea26bfdb78ef91aaadd4398d378e9ce 6385 devel optional 
dqlite_1.16.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEEduexRx7o0Oelk+iWIMqg5+qIVncFAmU/lbcRHGZyZWVlQGRl
Ymlhbi5vcmcACgkQIMqg5+qIVneBBg/9HKJbzv3IhZsLiKb3fISidqLm3aJQIXn3
vROoE5fU1APhTdMbtfYKYzH8NzYGvMqQEqohWgjj23kxZZ3FQExDCf06YElHiqo/
1MI1/L537hkRHrFZ/6Gsgqm+J4O2/CN7GbAf9+WVGLCLGl00oSEpLK4N5B8HxnwL
rWyWNW4ObI/qMpCL4dRGX4eFNggkSAvCAOs2kZrpOsBq1M33yakjn8ztStzkMbWV
9ZNPC57gAX/6XIww2ou8xsjL4zT73zJn/+SftTiEndLT9UzaFet/7I1Ej17MHjsg
Ll+Rx2BUeGG/yQEyIhhueor2nHimKdLfLSmKWoq5smo3D9K1k67qPPuMQ5XMdg+E
Y9+6uEClvK80QLPklfFuf/vx0NeIBSYpFOkpzOJ0lf00P+mmffp1vvt/6yKX7sJZ
UT665AP9L4EhGcgOilxTmvfBvDvAs9xkgGAKMIISDwB286AqhFc6b/DzVjkp0Nd8
i9PEKgXNYcBToRMq+i/a07g+CqcGlgB4MXac0lrODGamdX81fRCaaVuOrx5+Rjy+
1dHO56d6e58YK7WwgCYJZ9UHg9WzKShm3z755JAU1yDtoYO11/CwMffLpQeLobOj
osttv+vbTBvlKkof9EQraLXJglJ1RDV0OGoWDVmAuGe6nNfw3Ex6312mtKKu81sU
qKEypuOyLqE=
=BGUL
-END PGP SIGNATURE End Message ---

Bug#1054580: marked as done (libimage-magick-perl: broken symlink: Generic.ttf -> tuffy_regular.ttf)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:19:11 +
with message-id 
and subject line Bug#1054580: fixed in imagemagick 8:6.9.12.98+dfsg1-4
has caused the Debian Bug report #1054580,
regarding libimage-magick-perl: broken symlink: Generic.ttf -> tuffy_regular.ttf
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.)


-- 
1054580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054580
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libimage-magick-perl
Version: 8:6.9.12.98+dfsg1-2
Severity: minor
File: /usr/share/doc/imagemagick-6-common/examples/demo/Generic.ttf
User: debian...@lists.debian.org
Usertags: adequate broken-symlink

libimage-magick-perl introduced a broken symlink:

   /usr/share/doc/imagemagick-6-common/examples/demo/Generic.ttf -> 
../../../../fonts/truetype/tuffy/tuffy_regular.ttf

This appears to be because a dependency on fonts-tuffy was forgotten.
Several of the example demo programs use Generic.ttf, but since they
are only example demo programs and they work fine when fonts-tuffy is
not installed, but their output is slightly different, maybe Suggests
is appropriate, or perhaps the examples could be split out into another
package with fonts-tuffy in recommends. You could also close this bug
without fixing the issue since it is very very minor.

Here is some information about the symlink:

   $ adequate libimage-magick-perl
   libimage-magick-perl: broken-symlink 
/usr/share/doc/imagemagick-6-common/examples/demo/Generic.ttf -> 
../../../../fonts/truetype/tuffy/tuffy_regular.ttf
   
   $ readlink /usr/share/doc/imagemagick-6-common/examples/demo/Generic.ttf
   ../../../../fonts/truetype/tuffy/tuffy_regular.ttf
   
   $ chase /usr/share/doc/imagemagick-6-common/examples/demo/Generic.ttf
   chase: ../../../../fonts/truetype/tuffy: No such file or directory
   
   $ apt-file search tuffy_regular.ttf
   fonts-tuffy: /usr/share/fonts/truetype/tuffy/tuffy_regular.ttf
   
   $ grep -r Generic.ttf /usr/share/doc/imagemagick-6-common/examples/demo/
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate_words.pl:  
$image->Annotate(font=>'Generic.ttf',
   
/usr/share/doc/imagemagick-6-common/examples/demo/shadow-text.pl:$image->Annotate(font=>'Generic.ttf',fill=>'rgba(100,100,100,0.8)',
   
/usr/share/doc/imagemagick-6-common/examples/demo/shadow-text.pl:$image->Annotate(font=>'Generic.ttf',fill=>'red',stroke=>'blue',pointsize=>60,
   
/usr/share/doc/imagemagick-6-common/examples/demo/shapes.pl:$image->Annotate(font=>'Generic.ttf',fill=>'red',geometry=>'+150+20',
   
/usr/share/doc/imagemagick-6-common/examples/demo/shapes.pl:$image->Annotate(font=>'Generic.ttf',fill=>'blue',geometry=>'+150+38',
   
/usr/share/doc/imagemagick-6-common/examples/demo/shapes.pl:$image->Annotate(font=>'Generic.ttf',fill=>'black',geometry=>'+280+120',
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"North West",gravity=>"NorthWest",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"North",gravity=>"North",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"North East",gravity=>"NorthEast",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"West",gravity=>"West",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"Center",gravity=>"Center",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"East",gravity=>"East",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"South West",gravity=>"SouthWest",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"South",gravity=>"South",
   /usr/share/doc/imagemagick-6-common/examples/demo/annotate.pl:  
$label->Annotate(font=>'Generic.ttf',text=>"South East",gravity=>"SouthEast",
   
/usr/share/doc/imagemagick-6-common/examples/demo/piddle.pl:$image->Annotate(font=>'Generic.ttf',text=>'This
 is a test!',
   
/usr/share/doc/imagemagick-6-common/examples/demo/button.pl:$q->Annotate(font=>'Generic.ttf',text=>'Push
 Me',fill=>'black',
   
-- System Information:
Debian Release: trixie/sid
  APT prefers testing-debug
  APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 
'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 
'experimental-debug'), (700, 

Bug#1054506: marked as done (imagemagick: typo in debian/patches/0030-Add-a-debian-policy.patch)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:19:11 +
with message-id 
and subject line Bug#1054506: fixed in imagemagick 8:6.9.12.98+dfsg1-4
has caused the Debian Bug report #1054506,
regarding imagemagick: typo in debian/patches/0030-Add-a-debian-policy.patch
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.)


-- 
1054506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054506
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: imagemagick
Version: 8:6.9.12.98+dfsg1-2
Severity: normal

In the debian/patches/0030-Add-a-debian-policy.patch file:

--- a/config/Makefile.am
+++ b/config/Makefile.am
@@ -1,4 +1,4 @@
-#  Copyright 1999 ImageMagick Studio LLC, a non-profit organization
+#  Copyrght 1999 ImageMagick Studio LLC, a non-profit organization
 #  dedicated to making software imaging solutions freely available.
 #
 #  You may not use this file except in compliance with the License.  You may

I'm wondering why/how the "i" has been removed...

-- Package-specific info:
ImageMagick program version
---
animate:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
compare:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
convert:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
composite:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
conjure:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
display:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
identify:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
import:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
mogrify:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
montage:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org
stream:  ImageMagick 6.9.11-60 Q16 x86_64 2021-01-25 https://imagemagick.org

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

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

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.12.98+dfsg1-4
Done: Bastien Roucariès 

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 09:26:06 +
Source: imagemagick
Architecture: source
Version: 8:6.9.12.98+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Closes: 1020355 1020358 1020363 1020370 1038637 1054506 1054580
Changes:
 imagemagick (8:6.9.12.98+dfsg1-4) unstable; urgency=medium
 .
   * Replace ufraw-batch suggest by libraw-bin
 (Closes: #1038637)
   * Update changelog entry for CVE fixed.
   * Move from gsfonts to fonts-urw-base35. Thanks to Vincent Lefevre
 (Closes: #1020358, #1020355, #1020363, #1020370)
   * Recommends fonts-tuffy (Closes: #1054580)
   * Fix a typo in debian patch (Closes: #1054506)
Checksums-Sha1:
 1d7e215d25896ae028cb69991d3aa0b58b43d64b 5073 imagemagick_6.9.12.98+dfsg1-4.dsc
 1d9cc8c0327cec78ec8eb983ef9c8c1e6d9ec71b 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 

Bug#1020363: marked as done (libmagickcore-6.q16-6: transition gsfonts/gsfonts-x11 --> fonts-urw-base35)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:19:11 +
with message-id 
and subject line Bug#1020363: fixed in imagemagick 8:6.9.12.98+dfsg1-4
has caused the Debian Bug report #1020363,
regarding libmagickcore-6.q16-6: transition gsfonts/gsfonts-x11 --> 
fonts-urw-base35
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.)


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

Hi,

you are receiving this bug report, because your package declares a
relationship with the gsfonts and/or gsfonts-x11 packages. Both
packages have been replaced by fonts-urw-base35 since version
20200910-2 and are now merely transitional dummy packages. In order
to make it possible to remove these transitional packages, please
adjust the relationships for your package accordingly.

In the worst case, you will have to adjust some hard-coded font file
paths since the font files have been renamed between the gsfonts and
fonts-urw-base35 packages. Users of fontconfig to locate the font
files will most probably not notice any difference.

Cheers,

- Fabian 
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.12.98+dfsg1-4
Done: Bastien Roucariès 

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 09:26:06 +
Source: imagemagick
Architecture: source
Version: 8:6.9.12.98+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Closes: 1020355 1020358 1020363 1020370 1038637 1054506 1054580
Changes:
 imagemagick (8:6.9.12.98+dfsg1-4) unstable; urgency=medium
 .
   * Replace ufraw-batch suggest by libraw-bin
 (Closes: #1038637)
   * Update changelog entry for CVE fixed.
   * Move from gsfonts to fonts-urw-base35. Thanks to Vincent Lefevre
 (Closes: #1020358, #1020355, #1020363, #1020370)
   * Recommends fonts-tuffy (Closes: #1054580)
   * Fix a typo in debian patch (Closes: #1054506)
Checksums-Sha1:
 1d7e215d25896ae028cb69991d3aa0b58b43d64b 5073 imagemagick_6.9.12.98+dfsg1-4.dsc
 1d9cc8c0327cec78ec8eb983ef9c8c1e6d9ec71b 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 7476dc4fd6269280488ccdba11cea5c899de03b1 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Checksums-Sha256:
 6de5f707c784bc044422fe219e249bab6983f7de0a525102d3d9d68cab381245 5073 
imagemagick_6.9.12.98+dfsg1-4.dsc
 b5acd306a48c296ccd86496c49f27a654ca08812dd36ef9a084f7c77fa2a244c 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 f304831df5466be1168e33eff726d13f160152ed9519a90de2553a813e4c1d06 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Files:
 9a2d447a818484103b9c0bc072d6aef9 5073 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.dsc
 bb4b026739844b75d90991503d977e8d 260080 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 fd8d46d343d8a7ffcfda36b001fd6183 13834 graphics optional 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmU/jKYRHHJvdWNhQGRl
Ymlhbi5vcmcACgkQADoaLapBCF8ZJA//VDhMY1hn6b0TL1ciPEJQblmC9nJCMKdw
pPzoeJXC+Vg+wcnXRXR+Y7ilq4BH3A+KhBF7FEzhhvo/FZA+0iutc2bowG6BlOre
R4rCzkFUeccH99oOrTfWM3tV0NRmjpEFqi3y78PHLfmZZk3bNJ66Rr/egqYOoJ7P
7+UoQsV0U8N79IHgW6zPwNjGazyniXQ1c1qXx3QAynupT0ft8QTy/2T72PTx6nKo
xqc/RH5URs99s6wC52ujilTXxfJE7YhsUfSAX+0pUZa19+yLTsNoljktsBR49lH7
18MGaMMpZCWG16xblNgiwYPdtptYJpQf/w4CUAFoyPh3Jjm57SwMl/USt/In8/HI
Pw4P2Eb0/ekrAESohYUn70f+Ait8iu2HW+OLkVI1fPquaxbFAz9zhAr/f4TaQRD+
iyrOKMWCJTIBqP+uWRfNw/DO2baXw2XFNE9I2POby/cam3bl3XlI+WNsEtEveNGL
QWtKzGLAA7FatlMHNWpEeqHYwNIL46NULe2fJjPCtbN0J6iofHu/oxhPvF1UcYa9
eVO3Joaxc4wGDkjoTi9ZkcL0kFmiEFznCnTQ2V9F8Fu9Qfy6Bm8vdh932bL1vOOD
BeW3Psmu382Xvmg/xN9NKeKhJS/7Wylp/JfmOz9zrhLfm9Klj195QENTWhfLdzNQ
1aEOj5afPXY=
=g3rn
-END PGP SIGNATURE End 

Bug#1038637: marked as done (Recompile imagemagick with libraw)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:19:11 +
with message-id 
and subject line Bug#1038637: fixed in imagemagick 8:6.9.12.98+dfsg1-4
has caused the Debian Bug report #1038637,
regarding Recompile imagemagick with libraw
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.)


-- 
1038637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: imagemagick
Version: 8:6.9.11.60+dfsg-1.6

imagemagick is compiled with ufraw, which has been removed
 in recent Debian
releases. The official recommendation

is to use libraw instead, but does not work because imagemagick isn't
compiled with libraw on Debian.

root@5bbf0837ecff:/mnt# identify _DSC0194.ARW
identify-im6.q16: delegate failed `'ufraw-batch' --silent --create-id=also
--out-type=png --out-depth=16 --output='%u.png' '%i'' @
error/delegate.c/InvokeDelegate/1966.
identify-im6.q16: unable to open image
`/tmp/magick-HSCzyObOIY1tysbOED60Hadxjg9ZuXoc.ppm': No such file or
directory @ error/blob.c/OpenBlob/2924.

See also: https://gitlab.alpinelinux.org/alpine/aports/-/issues/14957
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.12.98+dfsg1-4
Done: Bastien Roucariès 

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

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

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 09:26:06 +
Source: imagemagick
Architecture: source
Version: 8:6.9.12.98+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Closes: 1020355 1020358 1020363 1020370 1038637 1054506 1054580
Changes:
 imagemagick (8:6.9.12.98+dfsg1-4) unstable; urgency=medium
 .
   * Replace ufraw-batch suggest by libraw-bin
 (Closes: #1038637)
   * Update changelog entry for CVE fixed.
   * Move from gsfonts to fonts-urw-base35. Thanks to Vincent Lefevre
 (Closes: #1020358, #1020355, #1020363, #1020370)
   * Recommends fonts-tuffy (Closes: #1054580)
   * Fix a typo in debian patch (Closes: #1054506)
Checksums-Sha1:
 1d7e215d25896ae028cb69991d3aa0b58b43d64b 5073 imagemagick_6.9.12.98+dfsg1-4.dsc
 1d9cc8c0327cec78ec8eb983ef9c8c1e6d9ec71b 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 7476dc4fd6269280488ccdba11cea5c899de03b1 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Checksums-Sha256:
 6de5f707c784bc044422fe219e249bab6983f7de0a525102d3d9d68cab381245 5073 
imagemagick_6.9.12.98+dfsg1-4.dsc
 b5acd306a48c296ccd86496c49f27a654ca08812dd36ef9a084f7c77fa2a244c 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 f304831df5466be1168e33eff726d13f160152ed9519a90de2553a813e4c1d06 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Files:
 9a2d447a818484103b9c0bc072d6aef9 5073 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.dsc
 bb4b026739844b75d90991503d977e8d 260080 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 fd8d46d343d8a7ffcfda36b001fd6183 13834 graphics optional 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmU/jKYRHHJvdWNhQGRl
Ymlhbi5vcmcACgkQADoaLapBCF8ZJA//VDhMY1hn6b0TL1ciPEJQblmC9nJCMKdw
pPzoeJXC+Vg+wcnXRXR+Y7ilq4BH3A+KhBF7FEzhhvo/FZA+0iutc2bowG6BlOre
R4rCzkFUeccH99oOrTfWM3tV0NRmjpEFqi3y78PHLfmZZk3bNJ66Rr/egqYOoJ7P
7+UoQsV0U8N79IHgW6zPwNjGazyniXQ1c1qXx3QAynupT0ft8QTy/2T72PTx6nKo
xqc/RH5URs99s6wC52ujilTXxfJE7YhsUfSAX+0pUZa19+yLTsNoljktsBR49lH7
18MGaMMpZCWG16xblNgiwYPdtptYJpQf/w4CUAFoyPh3Jjm57SwMl/USt/In8/HI
Pw4P2Eb0/ekrAESohYUn70f+Ait8iu2HW+OLkVI1fPquaxbFAz9zhAr/f4TaQRD+
iyrOKMWCJTIBqP+uWRfNw/DO2baXw2XFNE9I2POby/cam3bl3XlI+WNsEtEveNGL
QWtKzGLAA7FatlMHNWpEeqHYwNIL46NULe2fJjPCtbN0J6iofHu/oxhPvF1UcYa9
eVO3Joaxc4wGDkjoTi9ZkcL0kFmiEFznCnTQ2V9F8Fu9Qfy6Bm8vdh932bL1vOOD

Bug#1020370: marked as done (libmagickcore-6.q16hdri-7: transition gsfonts/gsfonts-x11 --> fonts-urw-base35)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:19:11 +
with message-id 
and subject line Bug#1020370: fixed in imagemagick 8:6.9.12.98+dfsg1-4
has caused the Debian Bug report #1020370,
regarding libmagickcore-6.q16hdri-7: transition gsfonts/gsfonts-x11 --> 
fonts-urw-base35
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.)


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

Hi,

you are receiving this bug report, because your package declares a
relationship with the gsfonts and/or gsfonts-x11 packages. Both
packages have been replaced by fonts-urw-base35 since version
20200910-2 and are now merely transitional dummy packages. In order
to make it possible to remove these transitional packages, please
adjust the relationships for your package accordingly.

In the worst case, you will have to adjust some hard-coded font file
paths since the font files have been renamed between the gsfonts and
fonts-urw-base35 packages. Users of fontconfig to locate the font
files will most probably not notice any difference.

Cheers,

- Fabian 
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.12.98+dfsg1-4
Done: Bastien Roucariès 

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 09:26:06 +
Source: imagemagick
Architecture: source
Version: 8:6.9.12.98+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Closes: 1020355 1020358 1020363 1020370 1038637 1054506 1054580
Changes:
 imagemagick (8:6.9.12.98+dfsg1-4) unstable; urgency=medium
 .
   * Replace ufraw-batch suggest by libraw-bin
 (Closes: #1038637)
   * Update changelog entry for CVE fixed.
   * Move from gsfonts to fonts-urw-base35. Thanks to Vincent Lefevre
 (Closes: #1020358, #1020355, #1020363, #1020370)
   * Recommends fonts-tuffy (Closes: #1054580)
   * Fix a typo in debian patch (Closes: #1054506)
Checksums-Sha1:
 1d7e215d25896ae028cb69991d3aa0b58b43d64b 5073 imagemagick_6.9.12.98+dfsg1-4.dsc
 1d9cc8c0327cec78ec8eb983ef9c8c1e6d9ec71b 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 7476dc4fd6269280488ccdba11cea5c899de03b1 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Checksums-Sha256:
 6de5f707c784bc044422fe219e249bab6983f7de0a525102d3d9d68cab381245 5073 
imagemagick_6.9.12.98+dfsg1-4.dsc
 b5acd306a48c296ccd86496c49f27a654ca08812dd36ef9a084f7c77fa2a244c 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 f304831df5466be1168e33eff726d13f160152ed9519a90de2553a813e4c1d06 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Files:
 9a2d447a818484103b9c0bc072d6aef9 5073 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.dsc
 bb4b026739844b75d90991503d977e8d 260080 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 fd8d46d343d8a7ffcfda36b001fd6183 13834 graphics optional 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmU/jKYRHHJvdWNhQGRl
Ymlhbi5vcmcACgkQADoaLapBCF8ZJA//VDhMY1hn6b0TL1ciPEJQblmC9nJCMKdw
pPzoeJXC+Vg+wcnXRXR+Y7ilq4BH3A+KhBF7FEzhhvo/FZA+0iutc2bowG6BlOre
R4rCzkFUeccH99oOrTfWM3tV0NRmjpEFqi3y78PHLfmZZk3bNJ66Rr/egqYOoJ7P
7+UoQsV0U8N79IHgW6zPwNjGazyniXQ1c1qXx3QAynupT0ft8QTy/2T72PTx6nKo
xqc/RH5URs99s6wC52ujilTXxfJE7YhsUfSAX+0pUZa19+yLTsNoljktsBR49lH7
18MGaMMpZCWG16xblNgiwYPdtptYJpQf/w4CUAFoyPh3Jjm57SwMl/USt/In8/HI
Pw4P2Eb0/ekrAESohYUn70f+Ait8iu2HW+OLkVI1fPquaxbFAz9zhAr/f4TaQRD+
iyrOKMWCJTIBqP+uWRfNw/DO2baXw2XFNE9I2POby/cam3bl3XlI+WNsEtEveNGL
QWtKzGLAA7FatlMHNWpEeqHYwNIL46NULe2fJjPCtbN0J6iofHu/oxhPvF1UcYa9
eVO3Joaxc4wGDkjoTi9ZkcL0kFmiEFznCnTQ2V9F8Fu9Qfy6Bm8vdh932bL1vOOD
BeW3Psmu382Xvmg/xN9NKeKhJS/7Wylp/JfmOz9zrhLfm9Klj195QENTWhfLdzNQ
1aEOj5afPXY=
=g3rn
-END PGP 

Bug#1020358: marked as done (libmagickcore-6.q16-7: transition gsfonts/gsfonts-x11 --> fonts-urw-base35)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:19:11 +
with message-id 
and subject line Bug#1020358: fixed in imagemagick 8:6.9.12.98+dfsg1-4
has caused the Debian Bug report #1020358,
regarding libmagickcore-6.q16-7: transition gsfonts/gsfonts-x11 --> 
fonts-urw-base35
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.)


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

Hi,

you are receiving this bug report, because your package declares a
relationship with the gsfonts and/or gsfonts-x11 packages. Both
packages have been replaced by fonts-urw-base35 since version
20200910-2 and are now merely transitional dummy packages. In order
to make it possible to remove these transitional packages, please
adjust the relationships for your package accordingly.

In the worst case, you will have to adjust some hard-coded font file
paths since the font files have been renamed between the gsfonts and
fonts-urw-base35 packages. Users of fontconfig to locate the font
files will most probably not notice any difference.

Cheers,

- Fabian 
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.12.98+dfsg1-4
Done: Bastien Roucariès 

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 09:26:06 +
Source: imagemagick
Architecture: source
Version: 8:6.9.12.98+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Closes: 1020355 1020358 1020363 1020370 1038637 1054506 1054580
Changes:
 imagemagick (8:6.9.12.98+dfsg1-4) unstable; urgency=medium
 .
   * Replace ufraw-batch suggest by libraw-bin
 (Closes: #1038637)
   * Update changelog entry for CVE fixed.
   * Move from gsfonts to fonts-urw-base35. Thanks to Vincent Lefevre
 (Closes: #1020358, #1020355, #1020363, #1020370)
   * Recommends fonts-tuffy (Closes: #1054580)
   * Fix a typo in debian patch (Closes: #1054506)
Checksums-Sha1:
 1d7e215d25896ae028cb69991d3aa0b58b43d64b 5073 imagemagick_6.9.12.98+dfsg1-4.dsc
 1d9cc8c0327cec78ec8eb983ef9c8c1e6d9ec71b 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 7476dc4fd6269280488ccdba11cea5c899de03b1 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Checksums-Sha256:
 6de5f707c784bc044422fe219e249bab6983f7de0a525102d3d9d68cab381245 5073 
imagemagick_6.9.12.98+dfsg1-4.dsc
 b5acd306a48c296ccd86496c49f27a654ca08812dd36ef9a084f7c77fa2a244c 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 f304831df5466be1168e33eff726d13f160152ed9519a90de2553a813e4c1d06 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Files:
 9a2d447a818484103b9c0bc072d6aef9 5073 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.dsc
 bb4b026739844b75d90991503d977e8d 260080 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 fd8d46d343d8a7ffcfda36b001fd6183 13834 graphics optional 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmU/jKYRHHJvdWNhQGRl
Ymlhbi5vcmcACgkQADoaLapBCF8ZJA//VDhMY1hn6b0TL1ciPEJQblmC9nJCMKdw
pPzoeJXC+Vg+wcnXRXR+Y7ilq4BH3A+KhBF7FEzhhvo/FZA+0iutc2bowG6BlOre
R4rCzkFUeccH99oOrTfWM3tV0NRmjpEFqi3y78PHLfmZZk3bNJ66Rr/egqYOoJ7P
7+UoQsV0U8N79IHgW6zPwNjGazyniXQ1c1qXx3QAynupT0ft8QTy/2T72PTx6nKo
xqc/RH5URs99s6wC52ujilTXxfJE7YhsUfSAX+0pUZa19+yLTsNoljktsBR49lH7
18MGaMMpZCWG16xblNgiwYPdtptYJpQf/w4CUAFoyPh3Jjm57SwMl/USt/In8/HI
Pw4P2Eb0/ekrAESohYUn70f+Ait8iu2HW+OLkVI1fPquaxbFAz9zhAr/f4TaQRD+
iyrOKMWCJTIBqP+uWRfNw/DO2baXw2XFNE9I2POby/cam3bl3XlI+WNsEtEveNGL
QWtKzGLAA7FatlMHNWpEeqHYwNIL46NULe2fJjPCtbN0J6iofHu/oxhPvF1UcYa9
eVO3Joaxc4wGDkjoTi9ZkcL0kFmiEFznCnTQ2V9F8Fu9Qfy6Bm8vdh932bL1vOOD
BeW3Psmu382Xvmg/xN9NKeKhJS/7Wylp/JfmOz9zrhLfm9Klj195QENTWhfLdzNQ
1aEOj5afPXY=
=g3rn
-END PGP SIGNATURE End 

Bug#1020355: marked as done (libmagickcore-6.q16hdri-6: transition gsfonts/gsfonts-x11 --> fonts-urw-base35)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:19:11 +
with message-id 
and subject line Bug#1020355: fixed in imagemagick 8:6.9.12.98+dfsg1-4
has caused the Debian Bug report #1020355,
regarding libmagickcore-6.q16hdri-6: transition gsfonts/gsfonts-x11 --> 
fonts-urw-base35
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.)


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

Hi,

you are receiving this bug report, because your package declares a
relationship with the gsfonts and/or gsfonts-x11 packages. Both
packages have been replaced by fonts-urw-base35 since version
20200910-2 and are now merely transitional dummy packages. In order
to make it possible to remove these transitional packages, please
adjust the relationships for your package accordingly.

In the worst case, you will have to adjust some hard-coded font file
paths since the font files have been renamed between the gsfonts and
fonts-urw-base35 packages. Users of fontconfig to locate the font
files will most probably not notice any difference.

Cheers,

- Fabian 
--- End Message ---
--- Begin Message ---
Source: imagemagick
Source-Version: 8:6.9.12.98+dfsg1-4
Done: Bastien Roucariès 

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

Debian distribution maintenance software
pp.
Bastien Roucariès  (supplier of updated imagemagick package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 09:26:06 +
Source: imagemagick
Architecture: source
Version: 8:6.9.12.98+dfsg1-4
Distribution: unstable
Urgency: medium
Maintainer: ImageMagick Packaging Team 

Changed-By: Bastien Roucariès 
Closes: 1020355 1020358 1020363 1020370 1038637 1054506 1054580
Changes:
 imagemagick (8:6.9.12.98+dfsg1-4) unstable; urgency=medium
 .
   * Replace ufraw-batch suggest by libraw-bin
 (Closes: #1038637)
   * Update changelog entry for CVE fixed.
   * Move from gsfonts to fonts-urw-base35. Thanks to Vincent Lefevre
 (Closes: #1020358, #1020355, #1020363, #1020370)
   * Recommends fonts-tuffy (Closes: #1054580)
   * Fix a typo in debian patch (Closes: #1054506)
Checksums-Sha1:
 1d7e215d25896ae028cb69991d3aa0b58b43d64b 5073 imagemagick_6.9.12.98+dfsg1-4.dsc
 1d9cc8c0327cec78ec8eb983ef9c8c1e6d9ec71b 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 7476dc4fd6269280488ccdba11cea5c899de03b1 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Checksums-Sha256:
 6de5f707c784bc044422fe219e249bab6983f7de0a525102d3d9d68cab381245 5073 
imagemagick_6.9.12.98+dfsg1-4.dsc
 b5acd306a48c296ccd86496c49f27a654ca08812dd36ef9a084f7c77fa2a244c 260080 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 f304831df5466be1168e33eff726d13f160152ed9519a90de2553a813e4c1d06 13834 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo
Files:
 9a2d447a818484103b9c0bc072d6aef9 5073 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.dsc
 bb4b026739844b75d90991503d977e8d 260080 graphics optional 
imagemagick_6.9.12.98+dfsg1-4.debian.tar.xz
 fd8d46d343d8a7ffcfda36b001fd6183 13834 graphics optional 
imagemagick_6.9.12.98+dfsg1-4_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAmU/jKYRHHJvdWNhQGRl
Ymlhbi5vcmcACgkQADoaLapBCF8ZJA//VDhMY1hn6b0TL1ciPEJQblmC9nJCMKdw
pPzoeJXC+Vg+wcnXRXR+Y7ilq4BH3A+KhBF7FEzhhvo/FZA+0iutc2bowG6BlOre
R4rCzkFUeccH99oOrTfWM3tV0NRmjpEFqi3y78PHLfmZZk3bNJ66Rr/egqYOoJ7P
7+UoQsV0U8N79IHgW6zPwNjGazyniXQ1c1qXx3QAynupT0ft8QTy/2T72PTx6nKo
xqc/RH5URs99s6wC52ujilTXxfJE7YhsUfSAX+0pUZa19+yLTsNoljktsBR49lH7
18MGaMMpZCWG16xblNgiwYPdtptYJpQf/w4CUAFoyPh3Jjm57SwMl/USt/In8/HI
Pw4P2Eb0/ekrAESohYUn70f+Ait8iu2HW+OLkVI1fPquaxbFAz9zhAr/f4TaQRD+
iyrOKMWCJTIBqP+uWRfNw/DO2baXw2XFNE9I2POby/cam3bl3XlI+WNsEtEveNGL
QWtKzGLAA7FatlMHNWpEeqHYwNIL46NULe2fJjPCtbN0J6iofHu/oxhPvF1UcYa9
eVO3Joaxc4wGDkjoTi9ZkcL0kFmiEFznCnTQ2V9F8Fu9Qfy6Bm8vdh932bL1vOOD
BeW3Psmu382Xvmg/xN9NKeKhJS/7Wylp/JfmOz9zrhLfm9Klj195QENTWhfLdzNQ
1aEOj5afPXY=
=g3rn
-END PGP 

Bug#1054615: marked as done ([INTL:sv] Swedish strings for tasksel debconf)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 11:59:07 +0100
with message-id <20231030115907.bfaf235171886f465009a...@mailbox.org>
and subject line Re: Bug#1054615: [INTL:sv] Swedish strings for tasksel debconf
has caused the Debian Bug report #1054615,
regarding [INTL:sv] Swedish strings for tasksel debconf
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.)


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

package: tasksel
severity: wishlist
tags: patch l10n

Please consider to add this file to translation of debconf.
--
brother# Translation of tasksel debconf template to Swedish
# Copyright (C) 2023 Martin Bagge 
# This file is distributed under the same license as the tasksel package.
#
# Daniel Nylander , 2006
# Martin Bagge , 2023
msgid ""
msgstr ""
"Project-Id-Version: tasksel 2.07 debconf\n"
"Report-Msgid-Bugs-To: task...@packages.debian.org\n"
"POT-Creation-Date: 2018-05-23 01:37+0200\n"
"PO-Revision-Date: 2023-10-26 22:30+0200\n"
"Last-Translator: Martin Bagge / brother \n"
"Language-Team: Swedish \n"
"Language: sv\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"

#. Type: multiselect
#. Description
#. Type: multiselect
#. Description
#: ../templates:1001 ../templates:2001
msgid "Choose software to install:"
msgstr "Välj programvara att installera:"

#. Type: multiselect
#. Description
#: ../templates:1001
msgid ""
"At the moment, only the core of the system is installed. To tune the system "
"to your needs, you can choose to install one or more of the following "
"predefined collections of software."
msgstr ""
"För närvarande är endast grunden av systemet installerat. För att anpassa "
"systemet efter dina behov kan du välja att installera en eller flera av "
"följande fördefinierade programvarusamlingar."

#. Type: multiselect
#. Description
#: ../templates:2001
msgid ""
"You can choose to install one or more of the following predefined "
"collections of software."
msgstr ""
"Du kan välja att installera en eller flera av följande fördefinierade "
"programvarusamlingar."

#. Type: multiselect
#. Description
#: ../templates:3001
msgid "This can be preseeded to override the default desktop."
msgstr ""
"Detta kan förkonfigureras för att ange annan skrivbordsmiljö som standard."

#. Type: title
#. Description
#: ../templates:4001
msgid "Software selection"
msgstr "Programvaruväljare"

#~ msgid "${ORIGCHOICES}"
#~ msgstr "${CHOICES}"

#~ msgid "${CHOICES}, manual package selection"
#~ msgstr "${CHOICES}, manuellt paketval"
--- End Message ---
--- Begin Message ---
Hi,

Martin Bagge / brother  wrote (Thu, 26 Oct 2023 22:40:32 
+0200):
> package: tasksel
> severity: wishlist
> tags: patch l10n
> 
> Please consider to add this file to translation of debconf.

This file has already been updated ~1 month ago:
https://salsa.debian.org/installer-team/tasksel/-/commit/e7a3e305fa67582e4a44a2e547976ceaa7725f3a


So closing this bug
Thanks anyway for your time


Holger


-- 
Holger Wansing 
PGP-Fingerprint: 496A C6E8 1442 4B34 8508  3529 59F1 87CA 156E B076--- End Message ---

Bug#1042705: marked as done (sqlite-utils: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 10:35:44 +
with message-id 
and subject line Bug#1042705: fixed in sqlite-utils 3.35.1-1
has caused the Debian Bug report #1042705,
regarding sqlite-utils: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not 
all arguments converted during string formatting
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.)


-- 
1042705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042705
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: sqlite-utils
Version: 3.30-1
Severity: important
Tags: ftbfs
User: python-modules-t...@lists.alioth.debian.org
Usertags: sphinx7.1

Hi,

sqlite-utils fails to build with Sphinx 7.1 and docutils 0.20, both of which
are currently available in experimental.

Relevant part (hopefully):
> make[2]: Entering directory '/<>/docs'
> Running Sphinx v7.1.1
> /bin/sh: 1: git: not found
> making output directory... done
> building [mo]: targets for 0 po files that are out of date
> writing output... 
> building [man]: all manpages
> updating environment: [new config] 8 added, 0 changed, 0 removed
> reading sources... [ 12%] changelog
> 
> Exception occurred:
>   File "/usr/lib/python3/dist-packages/sphinx/ext/extlinks.py", line 103, in 
> role
> title = caption % part
> ^~
> TypeError: not all arguments converted during string formatting
> The full traceback has been saved in /tmp/sphinx-err-szpo4ypd.log, if you 
> want to report the issue to the developers.
> Please also report this if it was a user error, so that a better error 
> message can be provided next time.
> A bug report can be filed in the tracker at 
> . Thanks!
> make[2]: *** [Makefile:20: man] Error 2


The full build log is available from:
http://qa-logs.debian.net/2023/07/30/exp/sqlite-utils_3.30-1_unstable_sphinx-exp.log

Please see [1] for Sphinx changelog and [2] for Docutils changelog.

Also see [3] for the list of deprecated/removed APIs in Sphinx and possible
alternatives to them.

Some notable changes in Sphinx 6 and Sphinx 7:

- Sphinx no longer includes jquery.js and underscore.js by default.
  Please use python3-sphinxcontrib.jquery package if you are using a custom
  template and it still needs jquery.

- The setup.py build_sphinx command was removed. Please instead call
  sphinx-build or "python3 -m sphinx" directly.

- For packages using the extlinks extension, the caption should contain
  exactly one "%s" placeholder (if caption is not None).

In case you have questions, please Cc sph...@packages.debian.org on reply.

[1]: https://www.sphinx-doc.org/en/master/changes.html
[2]: 
https://repo.or.cz/docutils.git/blob/refs/tags/docutils-0.20.1:/RELEASE-NOTES.txt
[3]: 
https://www.sphinx-doc.org/en/master/extdev/deprecated.html#dev-deprecated-apis

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

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
--- End Message ---
--- Begin Message ---
Source: sqlite-utils
Source-Version: 3.35.1-1
Done: Edward Betts 

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

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

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

Debian distribution maintenance software
pp.
Edward Betts  (supplier of updated sqlite-utils package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 08:53:50 +
Source: sqlite-utils
Architecture: source
Version: 3.35.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Edward Betts 
Closes: 1042705
Changes:
 sqlite-utils (3.35.1-1) unstable; urgency=medium
 .
   * New upstream release.
   * Update 0001-fix-documentation-privacy-breach.patch to remove plausible.io
 script from documentation.
   * Documentation 

Processed: RFS: streamlink/6.3.1-1 -- CLI for extracting video streams from various websites to a video player

[Debian Bug Tracking System]

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

> close 1055014
Bug #1055014 [sponsorship-requests] RFS: streamlink/6.3.1-1 -- CLI for 
extracting video streams from various websites to a video player
Marked Bug as done
> stop
Stopping processing here.

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

Bug#847621: marked as done (mpi4py: FTBFS on !linux: tests fail in MPI_INIT)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 10:38:02 +0100
with message-id 
and subject line Re: Bug#847621 mpi4py: FTBFS on !linux: tests fail in MPI_INIT
has caused the Debian Bug report #847621,
regarding mpi4py: FTBFS on !linux: tests fail in MPI_INIT
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.)


-- 
847621: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847621
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mpi4py
Version: 2.0.0-2
Severity: important

Hi,

mpi4py FTBFS on hurd and kfreebsd, blocking building of
several packages dependent packages.

https://buildd.debian.org/status/fetch.php?pkg=mpi4py=hurd-i386=2.0.0-2%2Bb1=1473623691
https://buildd.debian.org/status/fetch.php?pkg=mpi4py=kfreebsd-i386=2.0.0-2=1473761554
https://buildd.debian.org/status/fetch.php?pkg=mpi4py=kfreebsd-amd64=2.0.0-2=1473761937

[...]
   debian/rules override_dh_auto_test
make[1]: Entering directory '/«PKGBUILDDIR»'
pyversions: missing X(S)-Python-Version in control file, fall back to 
debian/pyversions
pyversions: missing debian/pyversions file, fall back to supported versions
py3versions: no X-Python3-Version in control file, using supported versions
set -e; for v in 2.7 3.5; do \
 echo "I: testing using python$v"; \
 PYTHONPATH=`/bin/ls -d /«PKGBUILDDIR»/build/lib.*-$v` \
  /usr/bin/python$v /usr/bin/nosetests -v --exclude='testPackUnpackExternal' -A 
"not network" ; \
done
I: testing using python2.7
[fano:75254] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c at line 
983
[fano:75255] PMIX ERROR: NOT-SUPPORTED in file 
src/server/pmix_server_listener.c at line 540
[fano:75254] PMIX ERROR: UNREACHABLE in file src/client/pmix_client.c at line 
199
--
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  init pmix failed
  --> Returned value Unreachable (-12) instead of ORTE_SUCCESS
--
--
It looks like orte_init failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during orte_init; some of which are due to configuration or
environment problems.  This failure appears to be an internal failure;
here's some additional information (which may only be relevant to an
Open MPI developer):

  orte_ess_init failed
  --> Returned value Unreachable (-12) instead of ORTE_SUCCESS
--
--
It looks like MPI_INIT failed for some reason; your parallel process is
likely to abort.  There are many reasons that a parallel process can
fail during MPI_INIT; some of which are due to configuration or environment
problems.  This failure appears to be an internal failure; here's some
additional information (which may only be relevant to an Open MPI
developer):

  ompi_mpi_init: ompi_rte_init failed
  --> Returned "Unreachable" (-12) instead of "Success" (0)
--
*** An error occurred in MPI_Init_thread
*** on a NULL communicator
*** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort,
***and potentially your MPI job)
[fano:75254] Local abort before MPI_INIT completed completed successfully, but 
am not able to aggregate error messages, and not able to guarantee that all 
other processes were killed!
debian/rules:89: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/«PKGBUILDDIR»'
debian/rules:22: recipe for target 'build-arch' failed
make: *** [build-arch] Error 2


Andreas
--- End Message ---
--- Begin Message ---

fixed 847621 3.0.2-8
thanks

mpi4py has built without fail for hurd-i386 since 3.0.2-8
and we no longer support freebsd, so closing this bug now.--- End Message ---

Bug#1032462: marked as done (ITA: argon2 -- memory-hard hashing function software)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 09:35:02 +
with message-id 
and subject line Bug#1032462: fixed in argon2 0~20190702+dfsg-4
has caused the Debian Bug report #1032462,
regarding ITA: argon2 -- memory-hard hashing function software
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.)


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

Source: argon2
Version: 0~20190702-0.1

There have been 4 NMUs since the last maintainer upload.
I am filing this ITS in order to orphan the package after three weeks.
--- End Message ---
--- Begin Message ---
Source: argon2
Source-Version: 0~20190702+dfsg-4
Done: Sven Geuer 

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

Debian distribution maintenance software
pp.
Sven Geuer  (supplier of updated argon2 package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 10:09:28 +0100
Source: argon2
Architecture: source
Version: 0~20190702+dfsg-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Sven Geuer 
Closes: 1032462
Changes:
 argon2 (0~20190702+dfsg-4) unstable; urgency=medium
 .
   * New maintainer and add myself as uploader (Closes: #1032462).
 - Update d/control.
   * Switch to DH compat format and raise level
 - Replace Build-Depends debhelper (>= 9) by debhelper-compat (= 13)
   in d/control.
 - Remove file d/compat.
   * d/rules: Disable dh_auto_install as dh_install picks files from where they
 have been built to anyway. Also prevents dh_missing from erroring out what
 happens with debhelper level 13.
   * Introduce autopkgtest per d/tests/*.
 - A secret is hashed via the command line tool and via a python script
   using the library. The results are compared to a pre-defined hash.
   * d/patches/*
 - Provide all patches with DEP-3 compliant headers.
 - Append .patch to all patch file names.
   * Drop the out-dated maintainer provided manual page, upstream's manual page
 has been introduced quite a while ago.
   * d/u/metadata: Add further information about the upstream project.
   * d/watch: Update to version 4.
   * d/libargon2-1.symbols: Add Build-Depends-Package field.
   * d/rules: Enable all hardening options available for ELF binaries.
   * d/copyright: Add missing email addresses, add missing debian/* authors.
   * d/control
 - Update Vcs-Browser and Vcs-Git.
 - Introduce Rules-Requires-Root with value 'no'.
 - Bump Standards-Version to 4.6.2.
   * Introduce d/p/relative-paths.patch to make sure libargon2.pc is generated
 with the correct content.
   * Drop unused file d/libargon2.pc.
   * Make use of the optimized source code available for the x86_64 architecture
 when (cross-)building for this architecture.
   * d/rules: Drop not needed exports and includes, checked by diffoscope.
   * d/s/linitian-overrides: Override lintian's
 override_dh_auto_test-does-not-check-DEB_BUILD_OPTIONS, it is not
 applicable due to Debhelper compat level 13.
   * Introduce d/salsa-ci.yml.
Checksums-Sha1:
 f7253a424a30c01ba941c6ed99238156b1e79c79 2263 argon2_0~20190702+dfsg-4.dsc
 f9af9ba5963c726bc07da0ee7565e267450d59b1 9248 
argon2_0~20190702+dfsg-4.debian.tar.xz
 87cb190ada1f3ebab9f505bac1e55404125ae45e 7567 
argon2_0~20190702+dfsg-4_amd64.buildinfo
Checksums-Sha256:
 7a5d5d761d69404d6602321671b77a5cb7a1b81b6ed64592116a432868e2b624 2263 
argon2_0~20190702+dfsg-4.dsc
 f9d4922b02e64cbb4bc10b0ad0ff283b2711702de593087205e273254af1998e 9248 
argon2_0~20190702+dfsg-4.debian.tar.xz
 37418dc9f99f16621e0f0552ee7fc2d07e1b5f0d727accc48f7f671ba885 7567 
argon2_0~20190702+dfsg-4_amd64.buildinfo
Files:
 c4f005912acfd64bcfc305a3a5df5615 2263 libs optional 
argon2_0~20190702+dfsg-4.dsc
 a726c05fe65d65d96fb2d16cb6e9090c 9248 libs optional 
argon2_0~20190702+dfsg-4.debian.tar.xz
 2c306f0d668a41cbc8fff9a95e5a053f 7567 libs optional 
argon2_0~20190702+dfsg-4_amd64.buildinfo

-BEGIN PGP SIGNATURE-

Processed: closing 1032998

[Debian Bug Tracking System]

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

> close 1032998 8:6.9.12.98+dfsg1-1
Bug #1032998 [imagemagick] imagemagick: font issue since 
8:6.9.10.23+dfsg-2.1+deb10u2
Marked as fixed in versions imagemagick/8:6.9.12.98+dfsg1-1.
Bug #1032998 [imagemagick] imagemagick: font issue since 
8:6.9.10.23+dfsg-2.1+deb10u2
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1033254

[Debian Bug Tracking System]

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

> close 1033254 8:6.9.12.98+dfsg1-1
Bug #1033254 [src:imagemagick] imagemagick: CVE-2023-1289
Marked as fixed in versions imagemagick/8:6.9.12.98+dfsg1-1.
Bug #1033254 [src:imagemagick] imagemagick: CVE-2023-1289
Marked Bug as done
> thanks
Stopping processing here.

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

Processed: closing 1005229

[Debian Bug Tracking System]

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

> close 1005229 8:6.9.12.98+dfsg1-1
Bug #1005229 [libmagickcore-6.q16-6-extra] libmagickcore-6.q16-6-extra: Depends 
on transitional libwmf0.2-7
There is no source info for the package 'libmagickcore-6.q16-6-extra' at 
version '8:6.9.12.98+dfsg1-1' with architecture ''
Unable to make a source version for version '8:6.9.12.98+dfsg1-1'
Marked as fixed in versions 8:6.9.12.98+dfsg1-1.
Bug #1005229 [libmagickcore-6.q16-6-extra] libmagickcore-6.q16-6-extra: Depends 
on transitional libwmf0.2-7
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#1047616: marked as done (yavta: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 09:58:40 +0100
with message-id 

and subject line 
has caused the Debian Bug report #1047616,
regarding yavta: Fails to build source after successful build
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.)


-- 
1047616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047616
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: yavta
Version: 0.0+git20220328.c7b5b75-1
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-sab-20230813 ftbfs-source-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to build a source package after a successful build
(dpkg-buildpackage ; dpkg-buildpackage -S).

This is probably a clear violation of Debian Policy section 4.9 (clean target),
but this is filed as severity:minor for now, because a discussion on
debian-devel showed that we might want to revisit the requirement of a working
'clean' target.

More information about this class of issues, included common problems and
solutions, is available at
https://wiki.debian.org/qa.debian.org/FTBFS/SourceAfterBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -S
> ---
> 
> dpkg-buildpackage: info: source package yavta
> dpkg-buildpackage: info: source version 0.0+git20220328.c7b5b75-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Ricardo Ribalda Delgado 
> 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean
>dh_auto_clean
>   make -j8 clean
> make[1]: Entering directory '/<>'
> Makefile:8: WARNING: Makefile support is deprecated, please switch to meson
> rm -f *.o
> rm -f yavta
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building yavta using existing 
> ./yavta_0.0+git20220328.c7b5b75.orig.tar.gz
> dpkg-source: info: local changes detected, the modified files are:
>  yavta-0.0+git20220328.c7b5b75/yavta.1
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/yavta_0.0+git20220328.c7b5b75-1.diff.L__wKs
> dpkg-source: info: Hint: make sure the version in debian/changelog matches 
> the unpacked source tree
> dpkg-source: info: you can integrate the local changes with dpkg-source 
> --commit
> dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -S' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/13/yavta_0.0+git20220328.c7b5b75-1_unstable.log

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Tested on the last version and it works fine. Probably fixed with the
transition to meson--- End Message ---

Processed: reassign 1046086 to dh-raku, forcibly merging 1045217 1046086

[Debian Bug Tracking System]

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

> reassign 1046086 dh-raku
Bug #1046086 [src:raku-tap-harness] raku-tap-harness: Fails to build source 
after successful build
Bug reassigned from package 'src:raku-tap-harness' to 'dh-raku'.
No longer marked as found in versions raku-tap-harness/0.3.8-2.
Ignoring request to alter fixed versions of bug #1046086 to the same values 
previously set
> forcemerge 1045217 1046086
Bug #1045217 {Done: Dominique Dumont } [dh-raku] 
raku-file-find: Fails to build source after successful build
Bug #1045323 {Done: Dominique Dumont } [dh-raku] 
raku-json-optin: Fails to build source after successful build
Bug #1045492 {Done: Dominique Dumont } [dh-raku] 
raku-license-spdx: Fails to build source after successful build
Bug #1045623 {Done: Dominique Dumont } [dh-raku] 
raku-librarycheck: Fails to build source after successful build
Bug #1045670 {Done: Dominique Dumont } [dh-raku] 
raku-json-name: Fails to build source after successful build
Bug #1045921 {Done: Dominique Dumont } [dh-raku] raku-zef: 
Fails to build source after successful build
Bug #1046178 {Done: Dominique Dumont } [dh-raku] 
raku-json-marshal: Fails to build source after successful build
Bug #1046598 {Done: Dominique Dumont } [dh-raku] 
raku-json-unmarshal: Fails to build source after successful build
Bug #1046941 {Done: Dominique Dumont } [dh-raku] 
raku-json-fast: Fails to build source after successful build
Bug #1047461 {Done: Dominique Dumont } [dh-raku] prove6: Fails 
to build source after successful build
Bug #1047625 {Done: Dominique Dumont } [dh-raku] 
raku-json-class: Fails to build source after successful build
Bug #1048022 {Done: Dominique Dumont } [dh-raku] 
raku-test-meta: Fails to build source after successful build
Bug #1048293 {Done: Dominique Dumont } [dh-raku] raku-meta6: 
Fails to build source after successful build
Bug #1048451 {Done: Dominique Dumont } [dh-raku] 
raku-readline: Fails to build source after successful build
Bug #1048603 {Done: Dominique Dumont } [dh-raku] 
raku-hash-merge: Fails to build source after successful build
Bug #1048691 {Done: Dominique Dumont } [dh-raku] raku-uri: 
Fails to build source after successful build
Bug #1049104 {Done: Dominique Dumont } [dh-raku] 
raku-getopt-long: Fails to build source after successful build
Bug #1046086 [dh-raku] raku-tap-harness: Fails to build source after successful 
build
Marked Bug as done
Marked as fixed in versions dh-raku/0.16.
Marked as found in versions dh-raku/0.15.
Bug #1045323 {Done: Dominique Dumont } [dh-raku] 
raku-json-optin: Fails to build source after successful build
Bug #1045492 {Done: Dominique Dumont } [dh-raku] 
raku-license-spdx: Fails to build source after successful build
Bug #1045623 {Done: Dominique Dumont } [dh-raku] 
raku-librarycheck: Fails to build source after successful build
Bug #1045670 {Done: Dominique Dumont } [dh-raku] 
raku-json-name: Fails to build source after successful build
Bug #1045921 {Done: Dominique Dumont } [dh-raku] raku-zef: 
Fails to build source after successful build
Bug #1046178 {Done: Dominique Dumont } [dh-raku] 
raku-json-marshal: Fails to build source after successful build
Bug #1046598 {Done: Dominique Dumont } [dh-raku] 
raku-json-unmarshal: Fails to build source after successful build
Bug #1046941 {Done: Dominique Dumont } [dh-raku] 
raku-json-fast: Fails to build source after successful build
Bug #1047461 {Done: Dominique Dumont } [dh-raku] prove6: Fails 
to build source after successful build
Bug #1047625 {Done: Dominique Dumont } [dh-raku] 
raku-json-class: Fails to build source after successful build
Bug #1048022 {Done: Dominique Dumont } [dh-raku] 
raku-test-meta: Fails to build source after successful build
Bug #1048293 {Done: Dominique Dumont } [dh-raku] raku-meta6: 
Fails to build source after successful build
Bug #1048451 {Done: Dominique Dumont } [dh-raku] 
raku-readline: Fails to build source after successful build
Bug #1048603 {Done: Dominique Dumont } [dh-raku] 
raku-hash-merge: Fails to build source after successful build
Bug #1048691 {Done: Dominique Dumont } [dh-raku] raku-uri: 
Fails to build source after successful build
Bug #1049104 {Done: Dominique Dumont } [dh-raku] 
raku-getopt-long: Fails to build source after successful build
Merged 1045217 1045323 1045492 1045623 1045670 1045921 1046086 1046178 1046598 
1046941 1047461 1047625 1048022 1048293 1048451 1048603 1048691 1049104
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1045217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045217
1045323: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045323
1045492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045492
1045623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045623
1045670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045670
1045921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045921
1046086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1046086
1046178: 

Bug#1028347: marked as done (dh-exec: dh-exec-install-rename does not look in debian/tmp for files to move)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 07:04:00 +
with message-id 
and subject line Bug#1028347: fixed in dh-exec 0.28
has caused the Debian Bug report #1028347,
regarding dh-exec: dh-exec-install-rename does not look in debian/tmp for files 
to move
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.)


-- 
1028347: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028347
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-exec
Version: 0.27
Severity: important

Looking for solutions to bug #1028202 (install the ncurses-base terminfo
files into /usr/share/terminfo), the dh-exec documentation seemed
promising to me, according to its README.md

,
| Additionally, assuming we have two binary packages: `foo-gtk` and `foo-utils`,
| and we want to include `/usr/bin/foo-gtk` in the former package, the rest of
| `/usr/bin` in the latter. Our install files would look like these, for 
`foo-gtk`
| and `foo-utils` respectively:
|
| #! /usr/bin/dh-exec
| => /usr/bin/foo-gtk
|
| #! /usr/bin/dh-exec
| /usr/bin/*
`

as well as the dh-exec-install manpage:

,
| The second extension follows a simpler syntax: any filename
| prefixed with "=>" will be moved instead of copied to the package.
| This allows one to move a file out of a directory to a package,
| and install the rest of the files in the same dir into another
| package.
`

So I figured out I would use these ncurses-{base,term}.install files:

,ncurses-base.install
| #! /usr/bin/dh-exec
| usr/share/tabset
| etc/terminfo
| => usr/share/terminfo/E/Eterm
| => usr/share/terminfo/E/Eterm-color
| [...] etc.
`---

,ncurses-term.install---
| usr/share/terminfo
`

Unfortunately this did not quite work as expected:

,
| dh_install -i
| Failed to move 'usr/share/terminfo/E/Eterm': No such file or directory at 
/usr/share/dh-exec/dh-exec-install-rename line 65, <> line 3.
| dh_install: error: debian/ncurses-base.install (executable config) returned 
exit code 127
`

The file in question, usr/share/terminfo/E/Eterm, exists in debian/tmp,
but dh-exec-install-rename does not look there in line 65.  Prefixing
all the usr/terminfo/*/* files in ncurses-base.install with a leading
debian/tmp lets the build complete, but then this leading debian/tmp
also ends up in the resulting ncurses-base*.deb. :-(

The attached patch works for me, but I have not checked whether it
passes the tests yet.  Writing a new regression test would probably also
be desirable.

An ncurses branch for testing (only a binary-indep build is required)
can be found at
https://salsa.debian.org/joachim-guest/ncurses/-/tree/wip/dh-exec.


diff --git a/lib/dh-exec-install-rename b/lib/dh-exec-install-rename
index 7d4d993..d8b0355 100755
--- a/lib/dh-exec-install-rename
+++ b/lib/dh-exec-install-rename
@@ -63,6 +63,8 @@ if (/([^\s]*)\s+=>\s+([^\s]*)/ || /^=>\s+([^\s]*)/) {

 if ($move_this) {
 move ($src, File::Spec->catfile ($debpath, $dstfile)) or
+		move (File::Spec->catfile ("debian/tmp", $src),
+		  File::Spec->catfile ($debpath, $dstfile)) or
 die "Failed to move '$src': $!";
 } else {
 cp ($src, File::Spec->catfile ($debpath, $dstfile)) or
--- End Message ---
--- Begin Message ---
Source: dh-exec
Source-Version: 0.28
Done: Craig Small 

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated dh-exec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 17:33:45 +1100
Source: dh-exec
Architecture: source
Version: 0.28
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 840682 1028347
Changes:
 dh-exec (0.28) unstable; urgency=medium
 .
   [Debian Janitor]
   * Remove constraints unnecessary since buster (oldstable):
 + Build-Depends: Drop versioned constraint on perl:any (>= 5.14.2~).
 + Build-Depends: Drop versioned constraint on libdpkg-perl (>= 1.17.14~).
 .
   

Bug#840682: marked as done (dh-exec --with=subst run also strip and filter command)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 07:04:00 +
with message-id 
and subject line Bug#840682: fixed in dh-exec 0.28
has caused the Debian Bug report #840682,
regarding dh-exec --with=subst run also strip and filter command
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.)


-- 
840682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840682
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: dh-exec
Version: 0.23
Severity: important

dh-exec --with=subst --no-act
/usr/lib/dh-exec/dh-exec-filter | /usr/lib/dh-exec/dh-exec-subst |
/usr/lib/dh-exec/dh-exec-strip [input: {0, NULL}, output: {0, NULL}]

instead of
/usr/lib/dh-exec/dh-exec-subst  [input: {0, NULL}, output: {0, NULL}]
--- End Message ---
--- Begin Message ---
Source: dh-exec
Source-Version: 0.28
Done: Craig Small 

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

Debian distribution maintenance software
pp.
Craig Small  (supplier of updated dh-exec package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Mon, 30 Oct 2023 17:33:45 +1100
Source: dh-exec
Architecture: source
Version: 0.28
Distribution: unstable
Urgency: medium
Maintainer: Craig Small 
Changed-By: Craig Small 
Closes: 840682 1028347
Changes:
 dh-exec (0.28) unstable; urgency=medium
 .
   [Debian Janitor]
   * Remove constraints unnecessary since buster (oldstable):
 + Build-Depends: Drop versioned constraint on perl:any (>= 5.14.2~).
 + Build-Depends: Drop versioned constraint on libdpkg-perl (>= 1.17.14~).
 .
   [Craig Small]
   * install-rename: Look in debian/tmp for files to move Closes: #1028347
   * dh-exec: Add no-defaults to not run filter and strip.
 Closes: #840682
   * Update to standards 4.6.2, no changes required.
Checksums-Sha1:
 c627cc976b75f756e182158549328685db49ca77 1624 dh-exec_0.28.dsc
 2622355c741f9ca45f46a80a36e8003f363d69bc 35952 dh-exec_0.28.tar.xz
 8c6ea41da080ad82b967e06c94132d133ddfcfbc 6357 dh-exec_0.28_amd64.buildinfo
Checksums-Sha256:
 db06800ffe6e87d6bde84d216446bbf17cf8b53c291a393d1a3144882cf6fcf1 1624 
dh-exec_0.28.dsc
 5b789230838ed0d066440073b841784d37a70fbe86530255e0668b87f733222c 35952 
dh-exec_0.28.tar.xz
 506b5ea145fc5d3c04d0bab1762fe555c6b4bc8e2ed98a84190c829c022a1c0b 6357 
dh-exec_0.28_amd64.buildinfo
Files:
 0e9a287885a3f14478d4323c6f8d19b3 1624 devel optional dh-exec_0.28.dsc
 206f4c0bb3150b9480212b902ed4fddb 35952 devel optional dh-exec_0.28.tar.xz
 31e4abec5feefb8134f0cb805eb08059 6357 devel optional 
dh-exec_0.28_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAmU/TrwACgkQAiFmwP88
hOPB+Q/9FfIigXUjDgZyo0MgTeawjy5WEH/9VzUTvc/t9luNfRK+72NGRKygopVZ
YQt+WJkxjmY1bl0BInqLzD0ImQ7k0rFjxVIIIy+fTDL6asJ7ucio4txgXZv74UcD
hF7JRNT2hMTRQEKEqk6QEZf2D+nPidzznoALDNG9XPUV18mdYC/Tox7I4nc528OG
wE5bKm9uK8DG6QVSmHCU1hHs6QEYYN6TEcURDaCsEStqwNDBKSwDFDbzOa/AMKv5
ktdac83hKhV39E/AKA2pG99/P/L7B32VZI7iwE8RM1Wmv7253fK9lVF2DUbbd4H+
/F2A2uy1Ul/vxYvz6w0nAo7lCmMX/B/AX3L7KedTucO4/9VuI5zzIqnVqrbKMms3
HZMPZmHKtC3iOZR4mq5+wTK6AZZ8FbXrnr2+3V90eoCaueUxF85c0/uj3cZ+18k6
VBrUQw+w95jLWujWgAGphctGgKMY/ijm0hzx7vS9VpVB0Yh4AMpL1E2n7JXdgmXT
YxNx1oVnjcaN9cm9OjddZ2uOKRO6Exmcg9m16D9molm7m/e2+Mi4A+EH5P0ujPWI
5hqs6/Ith0Ou5T/iZJ4pt8USdnaoeqiX8956kV8Du/8dVjMN6sRhHKu4akVvwT3O
1eMlR+ICeGsjACvpPF6ULNS9EPFuwJP9QEnZ2xXiKFi/ieqorjc=
=5bV/
-END PGP SIGNATURE End Message ---

Bug#498067: marked as done (dh_install wildcard exception mechanism request)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 17:24:39 +1100
with message-id 

and subject line Fixed in dh-exec 0.24
has caused the Debian Bug report #498067,
regarding dh_install wildcard exception mechanism request
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.)


-- 
498067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498067
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debhelper
Version: 7.0.15
Severity: wishlist

I'm switching a package from dh_movefiles to dh_install and there is
one facility that I really miss.

The way the package works is that after "make install" there are a
whole bunch of files in debian/tmp/usr/bin/.  Of these, file djview3
should go in package djview3, and the remaining dozen should go in
djvulibre-bin.

With dh_movefiles this was easy to accomplish:

 - list djvulibre-bin after djview3 in debian/control
 - put usr/bin/djview3 in djview3.files
 - put usr/bin/* in djvulibre-bin.files

But this doesn't work with dh_install, as the analogous setup with
djview3.install and djvulibre-bin.install results in two copies of
djview3, one in each binary package.

The can be worked around by expanding out the wildcard, sans djview3,
in djvulibre-bin.install.  But that is a very fragile, as it requires
a line to be added each time a new executable is added upstream.

It seems to me that *either* some exception mechanism, like

  $ cat others-bin.install

  :EXCEPT usr/bin/foo
  :EXCEPT usr/share/man/man1/foo.1
  usr/bin/*
  usr/share/man/man1/*

or some precedence mechanism, like

  $ cat others-bin.install

  :NOREPEAT foo-bin
  usr/bin/*
  usr/share/man/man1/*

would solve the problem and be easy to explain, and straightforward to
implement.

(I suppose
 dh_install -p djvulibre-bin --exclude=djview3
would work, or
 dh_install
 rm libdjvulibre-bin/usr/bin/djview3
but that also gets ugly and brittle quite quickly, and also makes
eventual migration to "dh binary-arch" and friends trickier.)

--Barak.
--
Barak A. Pearlmutter
 Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland
 http://www.bcl.hamilton.ie/~barak/


--- End Message ---
--- Begin Message ---
Package: dh-exec
Version: 0.24

I'm not sure why this bug was not automatically closed when dh-exec 0.24
was uploaded but the changelog entry is:
  * Add support for moving files to a package, instead of copying. Thanks
to Barak A. Pearlmutter and Niels Thykier for the report and bringing
the request to my attention. (Closes: #498067)
--- End Message ---

Bug#831786: marked as done (dh-exec: breaks dh_install --fail-missing)

[Debian Bug Tracking System]

Your message dated Mon, 30 Oct 2023 17:25:41 +1100
with message-id 

and subject line Fixed in dh-exec 0.24
has caused the Debian Bug report #831786,
regarding dh-exec: breaks dh_install --fail-missing
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.)


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

Hi,

dh_install --fail-missing seems to break with dh-exec in sid, while it
works in jessie. I suspect it was broken by DH_CONFIG_ACT_ON_PACKAGES
support in dh-exec.  The demo package at http://apt.niif.hu/dh-test/
does not build with dpkg-buildpackage -A in sid with the message:

dh_install --fail-missing
install -d debian/dh-test-data//usr/share
cp --reflink=auto -a debian/tmp/usr/share/dh-test 
debian/dh-test-data//usr/share/
dh_install: usr/bin/dh-test exists in debian/tmp but is not installed to 
anywhere
dh_install: missing files, aborting

Please advise, thanks.
Feri.
--- End Message ---
--- Begin Message ---
Another bug fix in 0.24 that wasn't closed, changelog is:

  * Fix the combination of dh_install --fail-missing, dh-exec and
arch-only/arch-indep builds. Thanks to Ferenc Wágner for the report.
(Closes: #831786)
--- End Message ---