Bug#1060972: marked as done (telepathy-farstream: FTBFS: make[3]: *** [/usr/share/gobject-introspection-1.0/Makefile.introspection:156: TelepathyFarstream-0.6.gir] Error 1)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 07:11:57 +
with message-id 
and subject line Bug#1060972: fixed in telepathy-farstream 0.6.2-1.2
has caused the Debian Bug report #1060972,
regarding telepathy-farstream: FTBFS: make[3]: *** 
[/usr/share/gobject-introspection-1.0/Makefile.introspection:156: 
TelepathyFarstream-0.6.gir] Error 1
to be marked as done.

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

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


-- 
1060972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: telepathy-farstream
Version: 0.6.2-1.1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240115 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 '/<>/telepathy-farstream'
> /bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I..  
> -I.. -I.. -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount 
> -I/usr/include/blkid  -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -I/usr/include/farstream-0.2 
> -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu 
> -pthread  -I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount 
> -I/usr/include/blkid  -Wdate-time -D_FORTIFY_SOURCE=2 
> -DG_LOG_DOMAIN=\"tp-fs\" -Wall -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -fstack-clash-protection -Wformat 
> -Werror=format-security -fcf-protection -c -o content.lo content.c
> libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I.. 
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread 
> -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/farstream-0.2 
> -I/usr/include/gstreamer-1.0 -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu 
> -pthread -I/usr/include/telepathy-1.0 -I/usr/include/dbus-1.0 
> -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/glib-2.0 
> -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -pthread -I/usr/include/libmount 
> -I/usr/include/blkid -Wdate-time -D_FORTIFY_SOURCE=2 -DG_LOG_DOMAIN=\"tp-fs\" 
> -Wall -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -c 
> content.c  -fPIC -DPIC -o .libs/content.o
> In file included from /usr/include/gstreamer-1.0/gst/gstbuffer.h:30,
>  from /usr/include/gstreamer-1.0/gst/gstpad.h:70,
>  from /usr/include/gstreamer-1.0/gst/gstelement.h:223,
>  from /usr/include/gstreamer-1.0/gst/gstbin.h:27,
>  from /usr/include/gstreamer-1.0/gst/gst.h:35,
>  from /usr/include/farstream-0.2/farstream/fs-conference.h:28,
>  from content.h:5,
>  from content.c:3:
> /usr/include/gstreamer-1.0/gst/gstcaps.h: In function ‘gst_clear_caps’:
> /usr/include/gstreamer-1.0/gst/gstcaps.h:209:13: warning: Not available 
> before 2.34
>   209 |   gst_clear_mini_object ((GstMiniObject **) caps_ptr);
>   | ^~~
> /usr/include/gstreamer-1.0/gst/gstbuffer.h: In function ‘gst_clear_buffer’:
> /usr/include/gstreamer-1.0/gst/gstbuffer.h:452:13: warning: Not available 
> before 2.34
>   452 |   gst_clear_mini_object ((GstMiniObject **) buf_ptr);
>   | ^~~
> In file included from /usr/include/gstreamer-1.0/gst/gstpad.h:71:
> /usr/include/gstreamer-1.0/gst/gstbufferlist.h: In function 
> ‘gst_clear_buffer_list’:
> /usr/include/gstreamer-1.0/gst/gstbufferlist.h:79:13: warning: Not available 
> before 2.34
>79 |   gst_clear_mini_object ((GstMiniObject **) list_ptr);
>   | ^~~
> In file included from /usr/include/gstreamer-1.0/gst/gstevent.h:225,
>  from /usr/include/gstreamer-1.0/gst/gstpadtemplate.h:36,
>  from /usr/include/gstreamer-1.0/gst/gstpad.h:73:
> /usr/include/gstreamer-1.0/gst/gsttaglist.h: In function ‘gst_clear_tag_list’:
> 

Bug#1064665: marked as done (ukui-media has an undeclared file conflict on /usr/lib/x86_64-linux-gnu/ukui-control-center/libaudio.so)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 06:46:43 +
with message-id 
and subject line Bug#1064665: fixed in ukui-media 3.1.1.1-2
has caused the Debian Bug report #1064665,
regarding ukui-media has an undeclared file conflict on 
/usr/lib/x86_64-linux-gnu/ukui-control-center/libaudio.so
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.)


-- 
1064665: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064665
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ukui-media
Version: 3.1.1.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: fileconflict
Control: affects -1 + ukui-control-center

ukui-media has an undeclared file conflict. This may result in an unpack
error from dpkg.

The file /usr/lib/x86_64-linux-gnu/ukui-control-center/libaudio.so is
contained in the packages
 * ukui-control-center
   * 3.0.2-2 as present in bullseye
   * 3.0.5.1-2 as present in bookworm|trixie
 * ukui-media/3.1.1.1-1 as present in unstable

These packages can be unpacked concurrently, because there is no
relevant Replaces or Conflicts relation. Attempting to unpack these
packages concurrently results in an unpack error from dpkg, because none
of the packages installs a diversion for the affected file.

Kind regards

The Debian Usr Merge Analysis Tool

This bug report has been automatically filed with no human intervention.
The source code is available at https://salsa.debian.org/helmutg/dumat.
If the filing is unclear or in error, don't hesitate to contact
hel...@subdivi.de for assistance.
--- End Message ---
--- Begin Message ---
Source: ukui-media
Source-Version: 3.1.1.1-2
Done: handsome_feng 

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

Debian distribution maintenance software
pp.
handsome_feng  (supplier of updated ukui-media 
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, 26 Feb 2024 14:09:46 +0800
Source: ukui-media
Architecture: source
Version: 3.1.1.1-2
Distribution: unstable
Urgency: medium
Maintainer: Kylin Team 
Changed-By: handsome_feng 
Closes: 1064665
Changes:
 ukui-media (3.1.1.1-2) unstable; urgency=medium
 .
   * Fix the fileconflict with ukui-control-center. (Closes: #1064665)
Checksums-Sha1:
 00f0e8b36257f2355366ea012d4840efaca7ee48 2442 ukui-media_3.1.1.1-2.dsc
 3ca9f59f64771f364969e8b281b23401ab9ae223 444108 ukui-media_3.1.1.1.orig.tar.gz
 2c36b96ccf437d2fc29f97b7176760ad95f75c04 4100 
ukui-media_3.1.1.1-2.debian.tar.xz
 15ae075bcfe69c6691e1b773801f746d4b6655cf 18373 
ukui-media_3.1.1.1-2_source.buildinfo
Checksums-Sha256:
 c116959ebdda4bb51ac43fe228331d275efd501eadde7904d0d5651720b8779d 2442 
ukui-media_3.1.1.1-2.dsc
 343198efc272e40ecca8c2bb257cd30c5a4305e115a0461c1c401efd16e49d8a 444108 
ukui-media_3.1.1.1.orig.tar.gz
 3414e718854f55056de439e5ff162d635587a659923b0cef3df146f6c37c7252 4100 
ukui-media_3.1.1.1-2.debian.tar.xz
 e04f569181799385930a8b858d4b6ecab42a89f199e36c16d99c0d2d1bc9de66 18373 
ukui-media_3.1.1.1-2_source.buildinfo
Files:
 0472a73bf2af80cfacf27357b6f86dc1 2442 x11 optional ukui-media_3.1.1.1-2.dsc
 f2c9fb10be10cbe5258eda46728c6efd 444108 x11 optional 
ukui-media_3.1.1.1.orig.tar.gz
 bf4a1340c97be9aa8a87a8b013389c45 4100 x11 optional 
ukui-media_3.1.1.1-2.debian.tar.xz
 c6cd816dd84507db591cc62b37730c80 18373 x11 optional 
ukui-media_3.1.1.1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJPBAEBCAA5FiEEhsgAHpUwnacZWWSCm7hQwBMRHwwFAmXcK/YbHGppYW5mZW5n
bGlAdWJ1bnR1a3lsaW4uY29tAAoJEJu4UMATER8M8PwQAIZMss7IQfRPBosYft0x
U8EFp/eT05W4VG82qULerkpr2dsG5qGMPCI3ATNHWp8dyYwkLTEGU0Btbxl42CxB
RL2EaEuZRm1By5wYXFE/mk5i96gdytaFgHzFwz0W/XjTPBsKvvGb4K20PRdHjFAM
Mwg9QD6X1BVtpmeU4hi+s+KsjOHM3CrfdKlfzh91h2Hil4crrzvljSifMkGoHnJG
I47OKfziHEMKxlfPEzS63lFoXzNOVH5ayGN8U7J8YmtJHSOOTsxSRHb0HZ2yHHP5
NVOolUiTLQhQKCqV1sAJgdfFYn9zX7/Ojhyfa5dJysn3oxAe+ED5n+OlL+kh1zk4
8AIteUfhHOuhfvZcdcaujAlhNW9+EUMQdQsBN1vQlGTWeozVDE0FgRsU7lCEnZCG
eccbBRFd71m3Chdh+7aHAUQx9aOA/fuD0q748KtX5rLk+E2E48nIwafUqL/77qG3
Bqzgnwx7hezBFFP3lbZEDPGRNP1kRLBQePJGM0V696133MJRnCPj6m9MoKJssLOm

Bug#1060268: marked as done (zxcvbn-c FTCBFS: passes host compiler flags to build compiler)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 03:49:43 +
with message-id 
and subject line Bug#1060268: fixed in zxcvbn-c 2.5+dfsg-2
has caused the Debian Bug report #1060268,
regarding zxcvbn-c FTCBFS: passes host compiler flags to build compiler
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.)


-- 
1060268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060268
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zxcvbn-c
Version: 2.5+dfsg-1
User: debian-cr...@lists.debian.org
Usertags: ftcbfs

zxcvbn-c fails to cross build from source. The failure is rooted in
changes to the default build flags that have now become
architecture-dependent. Passing -mbranch-protection=standard (arm64) to
an amd64 compiler doesn't go well. As a consequence, we need to add the
_FOR_BUILD suffix to compiler flags as well. I'm attaching a patch for
your convenience.

Helmut
--- zxcvbn-c-2.5+dfsg.orig/makefile
+++ zxcvbn-c-2.5+dfsg/makefile
@@ -10,6 +10,9 @@
 # need zxcvbn.h prior to package installation
 CPPFLAGS += -I.
 
+CPPFLAGS_FOR_BUILD ?= $(CPPFLAGS)
+CXXFLAGS_FOR_BUILD ?= $(CXXFLAGS)
+
 # library metadata
 TARGET_LIB = libzxcvbn.so.0.0.0
 SONAME = libzxcvbn.so.0
@@ -62,7 +65,7 @@
 	./dictgen -b -o zxcvbn.dict -h dict-crc.h $(WORDS)
 
 dictgen: dict-generate.cpp makefile
-	$(CXX_FOR_BUILD) $(CPPFLAGS) -std=c++11 $(CXXFLAGS) \
+	$(CXX_FOR_BUILD) $(CPPFLAGS_FOR_BUILD) -std=c++11 $(CXXFLAGS_FOR_BUILD) \
 		-o dictgen dict-generate.cpp $(LDFLAGS)
 
 test-c++inline: test.c zxcvbn-c++inline.o
--- End Message ---
--- Begin Message ---
Source: zxcvbn-c
Source-Version: 2.5+dfsg-2
Done: Sean Whitton 

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

Debian distribution maintenance software
pp.
Sean Whitton  (supplier of updated zxcvbn-c 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, 26 Feb 2024 11:22:14 +0800
Source: zxcvbn-c
Architecture: source
Version: 2.5+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Sean Whitton 
Changed-By: Sean Whitton 
Closes: 1060268
Changes:
 zxcvbn-c (2.5+dfsg-2) unstable; urgency=medium
 .
   * makefile: Use CPPFLAGS_FOR_BUILD & CXXFLAGS_FOR_BUILD (Closes: #1060268).
 Thanks to Helmut Grohne for the patch.
Checksums-Sha1:
 7d89451d3588264ecf522e29e041daa8550c5024 2036 zxcvbn-c_2.5+dfsg-2.dsc
 b8b38c6f7fb141ce37605d8f88fcc102888535dd 428716 
zxcvbn-c_2.5+dfsg-2.debian.tar.xz
Checksums-Sha256:
 151b9619bd0976f1676548e308ff522fdfe1090b569ffb543bddb6692f2c36aa 2036 
zxcvbn-c_2.5+dfsg-2.dsc
 3a0d886600a229001f8ed541f251c50f179001654083e86d4e75ce4a47e9bb4a 428716 
zxcvbn-c_2.5+dfsg-2.debian.tar.xz
Files:
 1156c0e8491e6126a09f99d8a38596bd 2036 libs optional zxcvbn-c_2.5+dfsg-2.dsc
 8878a2442a0ef5b716c631db5057701b 428716 libs optional 
zxcvbn-c_2.5+dfsg-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEm5FwB64DDjbk/CSLaVt65L8GYkAFAmXcBdAACgkQaVt65L8G
YkDRiBAAhBmr1Hjq1Jjq0UFmsM9Su5CQS6TK6jrZIqKD4irjgd4DSDKAJTOJ8SUM
MJSZj8dmEES/0wxoVA5BJUhoDy9Iq2YQxJO/GFxVjD6P6SnB623YutHnUmVsyihc
tWgDZjnT9CsLFFvpPgnzY6kg2tfb3AcvZGphCoi5PRP6Tq5sJjZzm0dA0hDAM3JP
leBbmweFbjW19K3JTKWfYlr3X1UeEF70Lb2NEZgAiwv9yaexv5IB2ZH3tdkX2usE
/PZGctH72uCyWFsHw8l9LZBpK00xVBVjCVjONSYlTSEgJHDTzpZZ/7aGLpfDZBtW
DBHMmitYZQpLG6vBhFVQQ6qp5oXpLMXC9pZFGCOqcyIMHQDeYNgwFLnbFoklLuA1
04TZ45XzHxar1XMy3h7Qh/7pXf1kzZqKRiIp0Nvf/vVEdHUjbCZ9hQrRJrOT+gMP
5Mwd79nu62WkOFXoBB0jYZnItkup4LhJHDrRfsD8ASjvfrmp1Tqp7J0usnRV5eb6
Jm9PY0CJNQEi269/dd+JAwLtrRN8bbuBe4TXS+wCFrDjWqn6hLCWUe1DaKJul0dU
vXDZbe1U0DL38m9UPE6N6KcahrOoqJ/NZyN5nKp5R7D0lsHpEWYoP+kWKaYmW2fN
04YeHP83fbFjw7GbcFLWMCLy4uzRkooLzgKlF+vfC0ulQX/T8gA=
=HPGN
-END PGP SIGNATURE-



pgpZCjZN1VRZE.pgp
Description: PGP signature
--- End Message ---

Bug#1064683: marked as done (cadaver: FTBFS: configure: error: could not find neon)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 03:34:04 +
with message-id 
and subject line Bug#1064683: fixed in cadaver 0.24+dfsg-3
has caused the Debian Bug report #1064683,
regarding cadaver: FTBFS: configure: error: could not find neon
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.)


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

Hi,

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


Relevant part (hopefully):
> checking whether strerror_r returns char *... yes
> checking how to run the C preprocessor... x86_64-linux-gnu-gcc -E
> checking for neon-config... /usr/bin/neon-config
> checking linking against neon... yes
> configure: incompatible neon library version 0.33.0: wanted 0.27 28 29 30 31 
> 32
> configure: error: could not find neon
> make[1]: *** [debian/rules:21: override_dh_auto_configure] Error 1
> make[1]: Leaving directory '/<>'


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/cadaver_0.24+dfsg-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=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: cadaver
Source-Version: 0.24+dfsg-3
Done: Arnaud Rebillout 

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

Debian distribution maintenance software
pp.
Arnaud Rebillout  (supplier of updated cadaver 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, 26 Feb 2024 10:12:56 +0700
Source: cadaver
Architecture: source
Version: 0.24+dfsg-3
Distribution: unstable
Urgency: medium
Maintainer: Arnaud Rebillout 
Changed-By: Arnaud Rebillout 
Closes: 1064683
Changes:
 cadaver (0.24+dfsg-3) unstable; urgency=medium
 .
   * Revert "Drop the patch on the man page"
   * Add patch to support neon 33 (Closes: #1064683)
Checksums-Sha1:
 d0b3673ca4722ac3f88a64a5dfcdb3a858d55e72 1983 cadaver_0.24+dfsg-3.dsc
 8ac40a0c6f474802f476dcfd789acdc2d1cdb9f3 8036 cadaver_0.24+dfsg-3.debian.tar.xz
 f1a24a60c214e3255129c932fe25773ad9db9a95 6681 
cadaver_0.24+dfsg-3_source.buildinfo
Checksums-Sha256:
 ad554d901a0e9ddafcd868e108d483f5636348a00125fc948bfc7919bc753bc6 1983 
cadaver_0.24+dfsg-3.dsc
 6f088689f051459790f69ad8870b56ae4a2fab44399d28bcd43b727bc565de72 8036 
cadaver_0.24+dfsg-3.debian.tar.xz
 341aee60d916d69e41f72799cbeaa099c41da1b3c08577936a04963b5ca1388d 6681 
cadaver_0.24+dfsg-3_source.buildinfo
Files:
 14e7f42f6752ac35c88fa27be6effaf0 1983 web optional cadaver_0.24+dfsg-3.dsc
 469a36b02abc14eb7b85b4b1cbacf0bb 8036 web optional 
cadaver_0.24+dfsg-3.debian.tar.xz
 512a8d71ba6cb29d358514b2d4a1e2ad 6681 web optional 
cadaver_0.24+dfsg-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEE0Kl7ndbut+9n4bYs5yXoeRRgAhYFAmXcBBsRHGFybmF1ZHJA
a2FsaS5vcmcACgkQ5yXoeRRgAhZokxAAhC0QgHkZDXGzjTCQPrcL95Z9P80WsTIE
LBm2rdIgBGRJBUqKPZSMjBD/tXTzOp1RVtwpvQXXggLpdGs6FNM8UL1i7SzKupmY
DwRdo+Ii3kk2zNIF54a+TLLzHXe8gVFo7kv90qcAOOMZn2PHkczCB/lx1d9wFADn
O/NvRovH77xJOkUQuVNfEKpLAxmuWcc22GsT1fD2YlASOEvAVAQdQOG/LonKRjlu
fNz7K0A3CV16RYktjNBZhUAoo1MkFt+c+7bgxdYfrzYKUQkjhDWWHppWBj23KAkr
tBeyfK7rk1DEdff9tFDe2PzwM0lziTkgF6PzkvWfOrlQ8EeoLizf/5NQ7tPX+1B2

Bug#1064756: marked as done (xelb: FTBFS: make[1]: *** [Makefile:16: xcb-screensaver.el] Error 255)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 03:20:24 +
with message-id 
and subject line Bug#1064756: fixed in xelb 0.18+git20240212.67ae522-1
has caused the Debian Bug report #1064756,
regarding xelb: FTBFS: make[1]: *** [Makefile:16: xcb-screensaver.el] Error 255
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.)


-- 
1064756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xelb
Version: 0.18-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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 '/<>'
> 
> Generating xcb-xproto.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-bigreq.el...
> Generating xcb-render.el...
> Generating xcb-shape.el...
> Generating xcb-dpms.el...
> Generating xcb-dri2.el...
> Generating xcb-dri3.el...
> Generating xcb-ge.el...
> Generating xcb-glx.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Using vacuous schema
> 
> Using vacuous schema
> 
> Generating xcb-sync.el...
> Generating xcb-record.el...
> Using vacuous schema
> 
> Generating xcb-res.el...
> Using vacuous schema
> 
> Using vacuous schema
> 
> Generating xcb-screensaver.el...
> Generating xcb-shm.el...
> Using vacuous schema
> 
> Generating xcb-xc_misc.el...
> Using vacuous schema
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Generating xcb-xevie.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xf86dri.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xf86vidmode.el...xcb-types.el: Warning: Non-symbol arguments 
> to cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xinerama.el...
> Using vacuous schema
> 
> Generating xcb-xkb.el...
> Using vacuous schema
> xcb-types.el: Warning: Non-symbol arguments to cl-defgeneric: (obj 
> xcb:connection)
> 
> Generating xcb-xprint.el...
> Using vacuous schema
> 
> Using vacuous schema
> 
> Generating xcb-xselinux.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Generating xcb-xtest.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Using vacuous schema
> 
> Generating xcb-xv.el...xcb-types.el: Warning: Non-symbol arguments to 
> cl-defgeneric: (obj xcb:connection)
> 
> Debugger entered--Lisp error: (void-variable 
> xcb:screensaver:xproto:CW:BackPixmap)
>   symbol-value(xcb:screensaver:xproto:CW:BackPixmap)
>   (let ((name (concat (xelb-node-attr node 'ref) ":" (xelb-node-subnode 
> node (symbol-value (or (intern-soft (concat xelb-prefix name)) 
> (intern-soft (concat "xcb:" name)) (intern (concat xelb-prefix name)
>   xelb-parse-enumref((enumref ((ref . "xproto:CW")) "BackPixmap"))
>   (list (xelb-parse-enumref j))
>   (nconc condition (list (xelb-parse-enumref j)))
>   (setq condition (nconc condition (list (xelb-parse-enumref j
>   (let nil (setq condition (nconc condition (list (xelb-parse-enumref j)
>   (if (eq val 'enumref) (let nil (setq condition (nconc condition (list 
> (xelb-parse-enumref j) (let nil (setq tmp (xelb-parse-structure-content 
> j)) (setq fields (nconc fields tmp)) (setq name-list (nconc name-list (list 
> (car (car tmp)))
>   (let* ((val (xelb-node-name 

Bug#1033461: marked as done ([INTL:ro] Romanian debconf templates translation of rkhunter)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 02:49:35 +
with message-id 
and subject line Bug#1033461: fixed in rkhunter 1.4.6-12
has caused the Debian Bug report #1033461,
regarding [INTL:ro] Romanian debconf templates translation of rkhunter
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.)


-- 
1033461: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033461
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: rkhunter
Version: N/A
Severity: wishlist
Tags: l10n, patch

Dear Maintainer,

Please find attached the Romanian translation of the «rkhunter» file.

Thanks,
Remus-Gabriel

rkhunter_debconf_ro.po
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: rkhunter
Source-Version: 1.4.6-12
Done: Francois Marier 

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

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

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

Debian distribution maintenance software
pp.
Francois Marier  (supplier of updated rkhunter package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 18 Jun 2023 00:05:31 -0700
Source: rkhunter
Architecture: source
Version: 1.4.6-12
Distribution: unstable
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Francois Marier 
Closes: 1033461
Changes:
 rkhunter (1.4.6-12) unstable; urgency=medium
 .
   * Add Romanian debconf templates translation (closes: #1033461).
 Thanks to Remus-Gabriel Chelu.
   * Use correct field names in debian/patches/*.diff.
   * Expand logcheck rules to cover rsyslog and journald.
Checksums-Sha1:
 6bfabcdfd1439795d6da1acbf0eb3b4855fbdf04 2069 rkhunter_1.4.6-12.dsc
 2d02bfb27fc419b0a7f99755f591912e07509206 29548 rkhunter_1.4.6-12.debian.tar.xz
 ee6c6ad43cd7a4f854ad97369bed884b7cbfb289 6103 
rkhunter_1.4.6-12_source.buildinfo
Checksums-Sha256:
 16d260f5b648aaa9168f9e55ae6c27742ab4f471b33b46106420b13fb9de7ef7 2069 
rkhunter_1.4.6-12.dsc
 693cf5ff86337d8a2b9a76d95fe6c149e6e1ebef873d7e0fd27962dc46d3feca 29548 
rkhunter_1.4.6-12.debian.tar.xz
 07ef525623daa266737062ae9f925eedc551641d3abeb04b55282c654c2fb5b1 6103 
rkhunter_1.4.6-12_source.buildinfo
Files:
 6f87bddc4f2d0adc92c5ad6bb0aa520e 2069 admin optional rkhunter_1.4.6-12.dsc
 43f49bebd1f212c0510f9c051d3e13a0 29548 admin optional 
rkhunter_1.4.6-12.debian.tar.xz
 bbd00df0ac9242f80c14d94fc5591261 6103 admin optional 
rkhunter_1.4.6-12_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEEjEcLKgsxVo4RDUMlFigfLgB8mNEFAmXb+W5fFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDhD
NDcwQjJBMEIzMTU2OEUxMTBENDMyNTE2MjgxRjJFMDA3Qzk4RDEACgkQFigfLgB8
mNFvPg/5Abe70ySG/iQ5Fo/YFmpgNm5vDUsKUXZIZxmZnAfPm899dSWFasHw2tVg
DMguA1hKJ5InckoqPoNectQJGP3Z8RSomxGqevSN55/tm3MSWFJ+0a/VlCWE/fr4
hYDbrzTybRwEuXeizVzbqiJi8mfsP8bvl4QUyHwfcBBvF4lNXDDZaB/PeAfF/ZJo
wIdyILqoSleoggnTU+Uj6MA/r6COCqXuhu4QokWlvkOfhOq49aqZiUFZ6vQUQzHa
JQKKjx0/Pg0jRQngVkn/noh6QfN8wnpk1ej/icpwY5Sl+epXT5ESXBClFNh3zNej
vErq7vuwMGh7wkmxFnGFeT4kOP2ZViFHVYo6VcHqqKYbrJBnlqMx7QTs4O5WFXrz
fIFD0vCuTOrQHrN9eBT8jgZT+FR+XWKkoq07VvJ7mBnscOJ7BFETFaOd9mu84/uj
klnfvwjve4RLRKrBQcgtubSODJhsdUh/YpXwMi4LsS1HmFI7K05030fAc4zyO6ES
iGGv9Vy5nFOBS2dtM8gObY/Hv3fcPcTN9Oh+RnmndDqo3mXAzjhM/DVQpBMU6z2K
/WdG8G4j911YEitAAqq8P7fgSRTeFxWpRxMEI1FkQVan+Q5xDNXgCZ/56K2dLlsi
VdH+7wFdL5Vg4NHdEqMarFOZtLPEtSbZ/Heq8JaGQZ4UyCpT5Q0=
=nkkP
-END PGP SIGNATURE-



pgpO89ouapxk_.pgp
Description: PGP signature
--- End Message ---

Bug#1064693: marked as done (slepc4py: FTBFS: make[1]: *** [debian/rules:69: override_dh_auto_build-arch] Error 25)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 02:36:24 +
with message-id 
and subject line Bug#1064693: fixed in slepc4py 3.19.2-3
has caused the Debian Bug report #1064693,
regarding slepc4py: FTBFS: make[1]: *** [debian/rules:69: 
override_dh_auto_build-arch] 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.)


-- 
1064693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064693
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: slepc4py
Version: 3.19.2-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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 '/<>'
> debian/rules:80: warning: overriding recipe for target 
> 'override_dh_auto_build-indep'
> debian/rules:59: warning: ignoring old recipe for target 
> 'override_dh_auto_build-indep'
> PYBUILD_NAME=slepc4py_real 
> SLEPC_DIR=/usr/lib/slepcdir/slepc3.19/x86_64-linux-gnu-real  
> PETSC_DIR=/usr/lib/petscdir/petsc3.19/x86_64-linux-gnu-real  dh_auto_build 
> -ppython3-slepc4py-real3.19
> I: pybuild base:305: /usr/bin/python3.12 setup.py build 
> running build
> running build_src
> removing Cython 0.29.37 from sys.modules
> fetching build requirement 'Cython == 0.29.36'
> WARNING: The wheel package is not available.
> /usr/bin/python3.12: No module named pip
> failed to fetch build requirement 'Cython == 0.29.36'
> 
>  
> 
>   You need Cython == 0.29.36 (you have version 0.29.37) 
> 
> $ /usr/bin/python3.12 -m pip install --upgrade cython 
> 
> 
> error: unsatisfied build requirement 'Cython == 0.29.36'
> E: pybuild pybuild:391: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3.12 setup.py build 
> I: pybuild base:305: /usr/bin/python3 setup.py build 
> running build
> running build_src
> removing Cython 0.29.37 from sys.modules
> fetching build requirement 'Cython == 0.29.36'
> WARNING: The wheel package is not available.
> /usr/bin/python3: No module named pip
> failed to fetch build requirement 'Cython == 0.29.36'
> 
>  
> 
>   You need Cython == 0.29.36 (you have version 0.29.37) 
> 
> $ /usr/bin/python3 -m pip install --upgrade cython 
> 
> 
> error: unsatisfied build requirement 'Cython == 0.29.36'
> E: pybuild pybuild:391: build: plugin distutils failed with: exit code=1: 
> /usr/bin/python3 setup.py build 
> dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11" 
> returned exit code 13
> make[1]: *** [debian/rules:69: override_dh_auto_build-arch] Error 25


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/slepc4py_3.19.2-2_unstable.log

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

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated slepc4py 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

Bug#1064514: marked as done (pymatgen: CVE-2024-23346)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 01:49:41 +
with message-id 
and subject line Bug#1064514: fixed in pymatgen 2024.1.27+dfsg1-6
has caused the Debian Bug report #1064514,
regarding pymatgen: CVE-2024-23346
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.)


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

Hi,

The following vulnerability was published for pymatgen.

CVE-2024-23346[0]:
| Pymatgen (Python Materials Genomics) is an open-source Python
| library for materials analysis. A critical security vulnerability
| exists in the
| `JonesFaithfulTransformation.from_transformation_str()` method
| within the `pymatgen` library prior to version 2024.2.20. This
| method insecurely utilizes `eval()` for processing input, enabling
| execution of arbitrary code when parsing untrusted input. Version
| 2024.2.20 fixes this issue.

https://github.com/materialsproject/pymatgen/security/advisories/GHSA-vgv8-5cpj-qj2f
https://github.com/materialsproject/pymatgen/commit/c231cbd3d5147ee920a37b6ee9dd236b376bcf5a


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: pymatgen
Source-Version: 2024.1.27+dfsg1-6
Done: Drew Parsons 

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

Debian distribution maintenance software
pp.
Drew Parsons  (supplier of updated pymatgen 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, 26 Feb 2024 00:56:58 +0100
Source: pymatgen
Architecture: source
Version: 2024.1.27+dfsg1-6
Distribution: unstable
Urgency: medium
Maintainer: Debichem Team 
Changed-By: Drew Parsons 
Closes: 1064514
Changes:
 pymatgen (2024.1.27+dfsg1-6) unstable; urgency=medium
 .
   * debian/tests test-pymatgen Depends: packmol
 for io/test_packmol.py. Also Build-Depends.
   * debian patch for CVE-2024-23346
 CVE-2024-23346_JonesFaithfulTransformation_sympy-c231cbd.patch
 applies upstream commit c231cbd to fix security vulnerability in
 JonesFaithfulTransformation. Closes: #1064514.
Checksums-Sha1:
 20c1bb46f631694cdceb1fa4853889d7b2e48c25 3148 pymatgen_2024.1.27+dfsg1-6.dsc
 769d9934975c8bb9ebc47d808ab0e3d487d9ad93 15184 
pymatgen_2024.1.27+dfsg1-6.debian.tar.xz
Checksums-Sha256:
 ec6ca3d267889b246fcce48dcff92c660fd423fa7d243a6af72673f297da09ca 3148 
pymatgen_2024.1.27+dfsg1-6.dsc
 4b33521c0873f0e416606692fe330df99cb7f58fbc3376918128b872ab3dda5d 15184 
pymatgen_2024.1.27+dfsg1-6.debian.tar.xz
Files:
 4d9240fa6334e2438da97841c9023d2e 3148 python optional 
pymatgen_2024.1.27+dfsg1-6.dsc
 6e6acf5f6db33bcfc8a3c84098fc8fd6 15184 python optional 
pymatgen_2024.1.27+dfsg1-6.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmXb6UwACgkQVz7x5L1a
AfrcRw//YN/1cobJNSZvb7PEtgiJ2J+9OpGY9E29KqBCrC69RTz9DFlzV4QqA2pu
ewmNycI4gabAWOKuPQJ1o2CHbgwhCvc40QUicQXFRS7Y2EYRD5b8eslbcOWWVyNh
Vs2WHPIanKIlhcUZW2pAvynj04e7yCqJBBDCfpFpo7YkfKP/aSmoeHQnLbZkF0oa
AdpPAS9G5sIBxWjSe6n2js3zAoSQYdiO7whoJ1ofoalo1biBCUK736JnezMTyPAY
gCNBsEeLZIhzz0/OsI01/IhTkmVH/3SU/fmUBMbL2K8WR25oFRWhZ2BlmKdq1YrN
wDthsR2V2nONoOP+tKZj6uLEaD/gE2TAbeJisuo9wLU51sUiFNHeP1G5POgv6qMM
+zqFAZ8m5bChN7YrImExhzxhs7aY4SgNw3Huhmud8I/JCcHto84tbwujndWMAxLO
KJA4izGlbdsSU1jjKwS/4QMKHXC32dRilVCp5mlUu7KesclboKZCcPqgArzpmK+l
XnUUFA+cALWhEDCKDUTVJ6xCj48L/SZJIDl7P22DLAT2ATan/l3532PecVcKCUKK
sqtn9oyWtdemW8cvX7ybKzdv+rv+9Ok0sWPPjkmMWDzmA2/ProlGf1xoGSXkwtPJ
pO2cJhP7E9ZWkRcgPMaa5cartooEBwyOx4IvWYHS/sklXOdEoHU=
=2Dbj
-END PGP SIGNATURE-



pgpBul32VYmA8.pgp
Description: PGP signature
--- End Message ---

Bug#1055088: marked as done (game-data-packager: jazz_jackrabbit_collection information outdated)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 01:18:19 +0100
with message-id 

and subject line done
has caused the Debian Bug report #1055088,
regarding game-data-packager: jazz_jackrabbit_collection information outdated
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.)


-- 
1055088: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055088
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: game-data-packager
Version: 77
Severity: normal
X-Debbugs-Cc: openj...@packages.debian.org

Hi,

the packaging information for the jazz_jackrabbit_collection package
from GOG.com is outdated. Thre is a new package available for download
called 'setup_jazz_jackrabbit_collection_2.0_csv2_(51327).exe' now,
and some of the file contents have changed.

What is the best way to update g-d-p in this regard? Manually, file by
file? Or is there a better way?

Cheers,

 - Fabian


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

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 game-data-packager depends on:
ii  python3 3.11.4-5+b1
ii  python3-debian  0.1.49
ii  python3-yaml6.0.1-1

Versions of packages game-data-packager recommends:
ii  game-data-packager-runtime  77

Versions of packages game-data-packager suggests:
pn  arj   
ii  binutils  2.41-6
pn  cabextract
pn  cdparanoia
pn  dynamite  
ii  gcc   4:13.2.0-1
pn  gdebi | gdebi-kde 
ii  gir1.2-gdkpixbuf-2.0  2.42.10+dfsg-1+b1
ii  innoextract   1.9-0.1
pn  lgc-pg
ii  lgogdownloader3.11-2
ii  lhasa [lzh-archiver]  0.4.0-1
ii  make  4.3-4.1
ii  p7zip-full16.02+dfsg-8
ii  pkexec123-3
ii  python3-gi3.46.0-1
ii  python3-omg   0.5.1-1
ii  python3-pil   10.0.0-1
pn  steam 
pn  steamcmd  
pn  unace-nonfree 
ii  unar  1.10.7+ds1+really1.10.1-2+b3
pn  unrar 
pn  unshield  
ii  unzip 6.0-28
pn  vorbis-tools  
ii  xdelta1.1.3-10.4
ii  xdelta3   3.0.11-dfsg-1.2
pn  xorriso   

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 77--- End Message ---

Bug#1044828: marked as done (fiat: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:49:02 +
with message-id 
and subject line Bug#1044828: fixed in fiat 2019.2.0~git20210419.7d418fa-4
has caused the Debian Bug report #1044828,
regarding fiat: 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.)


-- 
1044828: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044828
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fiat
Version: 2019.2.0~git20210419.7d418fa-3
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 fiat
> dpkg-buildpackage: info: source version 2019.2.0~git20210419.7d418fa-3
> 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
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> I: pybuild base:275: python3.11 setup.py clean 
> running clean
> removing '/<>/.pybuild/cpython3_3.11_fiat/build' (and everything 
> under it)
> 'build/bdist.linux-x86_64' does not exist -- can't clean it
> 'build/scripts-3.11' does not exist -- can't clean it
> /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: warning: upstream signing key but no upstream tarball signature
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building fiat using existing 
> ./fiat_2019.2.0~git20210419.7d418fa.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: info: local changes detected, the modified files are:
>  fiat-2019.2.0~git20210419.7d418fa/doc/sphinx/source/api-doc/FIAT.rst
>  fiat-2019.2.0~git20210419.7d418fa/doc/sphinx/source/api-doc/modules.rst
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/fiat_2019.2.0~git20210419.7d418fa-3.diff.J0s7zd
> 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/fiat_2019.2.0~git20210419.7d418fa-3_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: fiat
Source-Version: 2019.2.0~git20210419.7d418fa-4
Done: Drew Parsons 

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

Debian distribution maintenance software

Bug#1064631: marked as done (python-oslo.log: please remove the obsolete dependency on python3-six)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:49:26 +
with message-id 
and subject line Bug#1064631: fixed in python-oslo.log 5.5.0-2
has caused the Debian Bug report #1064631,
regarding python-oslo.log: please remove the obsolete dependency on python3-six
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.)


-- 
1064631: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064631
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-oslo.log
Version: 5.5.0
Severity: normal

Hi,

It's not used anymore

tchet@brix /tmp/python-oslo.log $ grep six -r
debian/control: python3-six,
debian/control: python3-six,
tchet@brix /tmp/python-oslo.log $
--- End Message ---
--- Begin Message ---
Source: python-oslo.log
Source-Version: 5.5.0-2
Done: Thomas Goirand 

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

Debian distribution maintenance software
pp.
Thomas Goirand  (supplier of updated python-oslo.log 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, 26 Feb 2024 00:24:23 +0100
Source: python-oslo.log
Architecture: source
Version: 5.5.0-2
Distribution: experimental
Urgency: medium
Maintainer: Debian OpenStack 
Changed-By: Thomas Goirand 
Closes: 1064631
Changes:
 python-oslo.log (5.5.0-2) experimental; urgency=medium
 .
   * Removed obsolete dependency on python3-six (Closes: #1064631).
Checksums-Sha1:
 8856fd275f463dd05c99b2cc001551340937712c 2657 python-oslo.log_5.5.0-2.dsc
 add199cf4e80395820847b3e8959cb40981edd4f 4960 
python-oslo.log_5.5.0-2.debian.tar.xz
 0bb4ba2f3b9c82d2dd8036b01580be81837997a6 12096 
python-oslo.log_5.5.0-2_amd64.buildinfo
Checksums-Sha256:
 55e9a77c37c1ba2185fb37f09a2ed7fdbd2138e260e5a81f9d5abb1b949138c3 2657 
python-oslo.log_5.5.0-2.dsc
 1f26a5a478b691282c23c73b247b09887d40562fab5701ff51bbb67dc690b994 4960 
python-oslo.log_5.5.0-2.debian.tar.xz
 c63674fd6f5dae4766972ec6ef236e13c8199f1da6c7192569e451a7a6a4 12096 
python-oslo.log_5.5.0-2_amd64.buildinfo
Files:
 5fcd0cf4aa199b20fa5813653f81dfdd 2657 python optional 
python-oslo.log_5.5.0-2.dsc
 d025155aacc4e952a8548314ab6f62b0 4960 python optional 
python-oslo.log_5.5.0-2.debian.tar.xz
 b5f284ef753b12acc85ef00c61640073 12096 python optional 
python-oslo.log_5.5.0-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEoLGp81CJVhMOekJc1BatFaxrQ/4FAmXbzRcACgkQ1BatFaxr
Q/6Ijw/+MnzFu/B+72Vj9vb1mo7Q8ihaMjikEH569BFZLN61YwgdVlA7mHMeCJ3Y
T37upx9sA6nq2HNQlDzzjFTBeP8nKruEU/YPn0mLCuI4Ez8cYpqaLzgRbRMiy6RC
Mz0Y9G1O/HKj/m4nRs0Z2nSh+GPS3Y2FEZwX9PFydqcrB2CmORT0HJJcuZoK2jsX
hkyR0ZhUwBIsoh8Sepv823idXKHvESsSG5nc4wT9OTD+e4VU0UIMRaY6CR3dtj9V
eC4WdlhXsiHa6sTHrBovHF67qjLjENHlGcIB6zz5QtSHBNy5DGcU/6TWO+AXKBof
COmxUcVxfRWryLb0YcV9jX0s8suAU12WlXq3RPHPmPNXehGcjLqBgpwGmxJYRFeB
3udUh6twbxpeOZjWaDuBymmK4L7Lo49GlTT0/8SoTVViAJYAdWh3lNs7DA+0hSzO
3cNs9no7k4MWGV5c15P6UvtIhEDq/m5EmCMCkKD36Safh4nKf8CnexFBd4dD63QD
aiPxspPaYX/AvagPeMZSXkD4AJL8fHh8WyIduNKZfyOEAocQflt7IKpj1ALOw23O
p2jMhbzfceMEVolU4Rvd1K2gP0HR0aWr+zibxtUpKP9md5UZsA0wyIZO9PXbZQzv
NAnbyVxVtvNtSyTtIHXZpuY04qkVLkaDL0C+NbKM7g7eu96T1Hs=
=IrLl
-END PGP SIGNATURE-



pgplxlrw48jIi.pgp
Description: PGP signature
--- End Message ---

Bug#1064755: marked as done (libflickr-api-perl: FTBFS: dh_auto_test: error: make -j8 test TEST_VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:35:09 +
with message-id 
and subject line Bug#1064755: fixed in libflickr-api-perl 1.28-4
has caused the Debian Bug report #1064755,
regarding libflickr-api-perl: FTBFS: dh_auto_test: error: make -j8 test 
TEST_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.)


-- 
1064755: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064755
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libflickr-api-perl
Version: 1.28-3
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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 '/<>'
> PERL_DL_NONLAZY=1 "/usr/bin/perl" "-MExtUtils::Command::MM" "-MTest::Harness" 
> "-e" "undef *Test::Harness::Switches; test_harness(1, 'blib/lib', 
> 'blib/arch')" t/*.t
> 
> #   Failed test 'checking the error code for "method not found"'
> #   at t/01-test.t line 32.
> #  got: '212'
> # expected: '112'
> 
> The 'perms' parameter must be one of: read, write, delete
>  at t/01-test.t line 77.
> # Looks like you failed 1 test of 26.
> t/01-test.t .. 
> 1..26
> ok 1 - An object of class 'Flickr::API' isa 'Flickr::API'
> ok 2 - An object of class 'Flickr::API::Response' isa 'Flickr::API::Response'
> not ok 3 - checking the error code for "method not found"
> ok 4 - checking the error code for "format not found"
> ok 5 - checking that http response code propagated
> ok 6 - checking that success flag propagated
> ok 7 - checking that error code propagated
> ok 8 - Signing test 1
> ok 9 - Signing test 2
> ok 10 - Signing test 3 (unicode=0)
> ok 11 - Signing test 4 (unicode=1)
> ok 12 - Did request_auth_url object to invalid permission
> ok 13 - did request_auth_url accept write permissions
> ok 14 - did request_auth_url accept delete permissions
> ok 15 - Checking that the api_key item in the query matches
> ok 16 - Checking that the perms item in the query matches
> ok 17 - Checking that the api_sig item in the query matches
> ok 18 - Checking that the frob item in the query matches
> ok 19 - Checking that the api_key item in the query matches in reverse
> ok 20 - Checking that the perms item in the query matches in reverse
> ok 21 - Checking that the frob item in the query matches in reverse
> ok 22 - Checking that the api_sig item in the query matches in reverse
> ok 23 - Checking correct return path
> ok 24 - Checking return domain
> ok 25 - Checking return protocol
> ok 26 - Checking URL generation without a secret
> Dubious, test returned 1 (wstat 256, 0x100)
> Failed 1/26 subtests 
> t/02-flickr_api.t  
> 1..15
> ok 1 - An object of class 'Flickr::API' isa 'Flickr::API'
> ok 2 - Does Flickr::API object identify as Flickr authentication
> ok 3 - Does Flickr::API object correctly specify its type as flickr
> ok 4 - Did export_config return the api_key
> ok 5 - Did constructor remove the older key in favor of api_key
> ok 6 - Did export_config return the api secret
> ok 7 - Did constructor remove the older secret in favor of api_secret
> ok 8 - Did export_config return undef for undefined frob
> ok 9 - Did export_config return undef for undefined token
> ok 10 - Did export_storable_config produce a readable config
> ok 11 - An object of class 'Flickr::API' isa 'Flickr::API'
> ok 12 - were we able to import our api key
> ok 13 - did we sucessfully shake deprecated 'key' argument
> ok 14 - were we able to import our api secret
> ok 15 - did we sucessfully shake deprecated 'secret' argument
> ok
> t/02-oauth_api.t . 
> 1..32
> ok 1 - An object of class 'Flickr::API' isa 'Flickr::API'
> ok 2 - Does Flickr::API object identify as OAuth
> ok 3 - Does Flickr::API object identify as consumer request
> ok 4 - Does Flickr::API object correctly specify its type as oauth
> ok 5 - Did export_config return the consumer_key in consumer/message request
> ok 6 - Did export_config return the correct signature_method in 
> consumer/message request
> ok 7 - Did export_config return a nonce in consumer/message request
> ok 8 - Did export_config return a timestamp in consumer/message request
> ok 9 - Did export_config return the consumer_secret in consumer/api request
> ok 10 - Did export_config return the correct request_method in consumer/api 
> request
> ok 11 - Did export_config return the correct request_url in consumer/api 
> request
> ok 12 - An object of class 'Flickr::API' 

Bug#1047281: marked as done (install-mimic: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:35:02 +
with message-id 
and subject line Bug#1047281: fixed in install-mimic 0.4.1-1
has caused the Debian Bug report #1047281,
regarding install-mimic: 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.)


-- 
1047281: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047281
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: install-mimic
Version: 0.4.0-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 install-mimic
> dpkg-buildpackage: info: source version 0.4.0-6
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Peter Pentchev 
>  dpkg-source --before-build .
>  debian/rules clean
> dh 'clean'
>dh_auto_clean
>   make -j8 distclean
> make[1]: Entering directory '/<>'
> rm -f install-mimic install-mimic.o install-mimic.1.gz
> [ ! -d "target" ] || cargo clean
> rm -f Cargo.lock
> make[1]: Leaving directory '/<>'
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: verifying ./install-mimic_0.4.0.orig.tar.xz.asc
> dpkg-source: info: building install-mimic using existing 
> ./install-mimic_0.4.0.orig.tar.xz
> dpkg-source: info: building install-mimic using existing 
> ./install-mimic_0.4.0.orig.tar.xz.asc
> dpkg-source: info: local changes detected, the modified files are:
>  install-mimic-0.4.0/NEWS.md
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/install-mimic_0.4.0-6.diff.iYSfV6
> 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/install-mimic_0.4.0-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: install-mimic
Source-Version: 0.4.1-1
Done: Peter Pentchev 

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

Debian distribution maintenance software
pp.
Peter Pentchev  (supplier of updated install-mimic 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, 26 Feb 2024 01:04:57 +0200
Source: install-mimic
Architecture: source
Version: 0.4.1-1
Distribution: unstable
Urgency: medium
Maintainer: Peter Pentchev 
Changed-By: Peter Pentchev 
Closes: 1047281
Changes:
 install-mimic (0.4.1-1) unstable; urgency=medium
 .
   * Declare compliance with Debian Policy 4.6.2 with no changes.
 Note that the 0.4.0-6 upload actually 

Bug#1064775: marked as done (python-pycdlib: FTBFS: failed tests)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 00:20:32 +0100
with message-id <63a9793b-6056-4137-909f-e879465a7...@goirand.fr>
and subject line Re: Bug#1064775: python-pycdlib: FTBFS: failed tests
has caused the Debian Bug report #1064775,
regarding python-pycdlib: FTBFS: failed tests
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.)


-- 
1064775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064775
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-pycdlib
Version: 1.12.0+ds1-5
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> pkgos-dh_auto_install --no-py2 --in-tmp
> + PKGOS_IN_TMP=no
> + echo WARNING: --no-py2 is deprecated and always on.
> WARNING: --no-py2 is deprecated and always on.
> + shift
> + PKGOS_IN_TMP=yes
> + shift
> + dpkg-parsechangelog -SSource
> + SRC_PKG_NAME=python-pycdlib
> + + sed s/python-//
> echo python-pycdlib
> + PY_MODULE_NAME=pycdlib
> + py3versions -vr
> + PYTHON3S=3.12 3.11
> + [ yes = yes ]
> + TARGET_DIR=tmp
> + pwd
> + python3.12 setup.py install --install-layout=deb --root 
> /<>/debian/tmp
> running install
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/pycdlib
> copying pycdlib/utils.py -> build/lib/pycdlib
> copying pycdlib/__init__.py -> build/lib/pycdlib
> copying pycdlib/rockridge.py -> build/lib/pycdlib
> copying pycdlib/backport_functools.py -> build/lib/pycdlib
> copying pycdlib/path_table_record.py -> build/lib/pycdlib
> copying pycdlib/eltorito.py -> build/lib/pycdlib
> copying pycdlib/pycdlibexception.py -> build/lib/pycdlib
> copying pycdlib/inode.py -> build/lib/pycdlib
> copying pycdlib/dates.py -> build/lib/pycdlib
> copying pycdlib/pycdlib.py -> build/lib/pycdlib
> copying pycdlib/isohybrid.py -> build/lib/pycdlib
> copying pycdlib/udf.py -> build/lib/pycdlib
> copying pycdlib/facade.py -> build/lib/pycdlib
> copying pycdlib/pycdlibio.py -> build/lib/pycdlib
> copying pycdlib/headervd.py -> build/lib/pycdlib
> copying pycdlib/dr.py -> build/lib/pycdlib
> running build_scripts
> creating build/scripts-3.12
> copying and adjusting tools/pycdlib-explorer -> build/scripts-3.12
> copying and adjusting tools/pycdlib-extract-files -> build/scripts-3.12
> copying and adjusting tools/pycdlib-genisoimage -> build/scripts-3.12
> changing mode of build/scripts-3.12/pycdlib-explorer from 644 to 755
> changing mode of build/scripts-3.12/pycdlib-extract-files from 644 to 755
> changing mode of build/scripts-3.12/pycdlib-genisoimage from 644 to 755
> running install_lib
> creating /<>/debian/tmp
> creating /<>/debian/tmp/usr
> creating /<>/debian/tmp/usr/lib
> creating /<>/debian/tmp/usr/lib/python3
> creating /<>/debian/tmp/usr/lib/python3/dist-packages
> creating /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/utils.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/__init__.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/rockridge.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/backport_functools.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/path_table_record.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/eltorito.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/pycdlibexception.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/inode.py -> 
> /<>/debian/tmp/usr/lib/python3/dist-packages/pycdlib
> copying build/lib/pycdlib/dates.py -> 
> 

Bug#1064774: marked as done (jenkins-job-builder: FTBFS: stestr fails directory)

[Debian Bug Tracking System]

Your message dated Mon, 26 Feb 2024 00:14:41 +0100
with message-id <9b5a1b03-8b05-4256-a9d7-686d8c727...@goirand.fr>
and subject line Re: Bug#1064774: jenkins-job-builder: FTBFS: stestr fails 
directory
has caused the Debian Bug report #1064774,
regarding jenkins-job-builder: FTBFS: stestr fails 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.)


-- 
1064774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jenkins-job-builder
Version: 3.11.0-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> PYBUILD_SYSTEM=custom dh_auto_test
> I: pybuild base:305: PYTHON=python3.12 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> stestr: 'run --subunit 
> tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
>  is not a stestr command. See 'stestr --help'.
> Did you mean one of these?
>   help
> E: pybuild pybuild:391: test: plugin custom failed with: exit code=2: 
> PYTHON=python3.12 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> I: pybuild base:305: PYTHON=python3.11 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> stestr: 'run --subunit 
> tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
>  is not a stestr command. See 'stestr --help'.
> Did you mean one of these?
>   help
> E: pybuild pybuild:391: test: plugin custom failed with: exit code=2: 
> PYTHON=python3.11 stestr run --subunit 
> 'tests\.(?!cmd\.test_config\.TestConfigs\.test_use_global_config|cmd\.test_config\.TestConfigs\.test_use_config_in_user_home|moduleregistry\.test_moduleregistry\.ModuleRegistryPluginInfoTestsWithScenarios\.test_plugin_version_comparison)'
> dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/jenkins-job-builder_3.11.0-6_unstable.log

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

On 2/25/24 20:46, Lucas Nussbaum wrote:

Source: jenkins-job-builder
Version: 3.11.0-6
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Can't reproduce. Maybe a false positive due to the bad version of 
python3-testtools.


Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#1064780: marked as done (pgpainless: fails to build from source with Java 21 due to SecurityManager UnsupportedException)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:19:37 +
with message-id 
and subject line Bug#1064780: fixed in pgpainless 1.6.6-2
has caused the Debian Bug report #1064780,
regarding pgpainless: fails to build from source with Java 21 due to 
SecurityManager UnsupportedException
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.)


-- 
1064780: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064780
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgpainless
Version: 1.6.6-1
Severity: important
Tags: ftbfs
User: debian-j...@lists.debian.org
Usertags: default-java21
X-Debbugs-Cc: vladimir.pe...@canonical.com

Dear Maintainer,

The package fails to build from source due to the exception during tests:

   JUnit
Jupiter:SignUsingPublicKeyBehaviorTest:testSignatureCreationAndVerification()
 MethodSource [className =
'org.pgpainless.cli.misc.SignUsingPublicKeyBehaviorTest', methodName =
'testSignatureCreationAndVerification', methodParameterTypes = '']
 => java.lang.UnsupportedOperationException: The Security Manager is
deprecated and will be removed in a future release
java.base/java.lang.System.setSecurityManager(System.java:430)
com.ginsberg.junit.exit.SystemExitExtension.beforeEach(SystemExitExtension.java:95)
java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
java.base/java.util.ArrayList.forEach(ArrayList.java:1596)
Suppressed: org.opentest4j.AssertionFailedError: Expected
System.exit(79) to be called, but it was not. ==> expected: <79> but was:

com.ginsberg.junit.exit.SystemExitExtension.afterEach(SystemExitExtension.java:67)
  [...]

The tests need to run with -Djava.security.manager=allow for the junit
SystemExit extension to work.




-- System Information:
Debian Release: trixie/sid
  APT prefers mantic-updates
  APT policy: (500, 'mantic-updates'), (500, 'mantic-security'), (500, 
'mantic'), (100, 'mantic-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.5.0-21-generic (SMP w/32 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
Source: pgpainless
Source-Version: 1.6.6-2
Done: Vladimir Petko 

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

Debian distribution maintenance software
pp.
Vladimir Petko  (supplier of updated pgpainless 
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, 26 Feb 2024 09:33:56 +1300
Source: pgpainless
Architecture: source
Version: 1.6.6-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Java Maintainers 

Changed-By: Vladimir Petko 
Closes: 1064780
Changes:
 pgpainless (1.6.6-2) unstable; urgency=medium
 .
   * Team upload
   * d/t/upstream-sop, d/t/upstream-cli, d/rules: Java 21 throws
 UnsupportedOperationException when trying to set SecurityManager.
 JUnit SystemExit extension tries to set SecurityManager. Pass
 -Djava.security.manager=allow so that extension works
 (Closes: #1064780).
Checksums-Sha1:
 5ac5ab3b145731bafebad9f32c99a4dfe8be16dd 2872 pgpainless_1.6.6-2.dsc
 db93ed0fcf5cd4a0857034cc20055bf7a365c0b7 39088 pgpainless_1.6.6-2.debian.tar.xz
 062a6abcbe28c7e4fc3ad042c899cca664b729c4 20559 
pgpainless_1.6.6-2_amd64.buildinfo
Checksums-Sha256:
 2e868533b9b8438cec574beca25a6ad90035e5bb860f65ba293d09b373d72670 2872 
pgpainless_1.6.6-2.dsc
 89acd37fc76611f579f90fe5cd1bf5fa60d8a661160de4ec1874f47a68c74605 39088 
pgpainless_1.6.6-2.debian.tar.xz
 2389535df12228749a2dea5d79227282171197ec812ef6b6136cbd6936a18d77 20559 
pgpainless_1.6.6-2_amd64.buildinfo
Files:
 2d1132ae4889827bc204f3d2a3a58e42 2872 java optional pgpainless_1.6.6-2.dsc
 af05bc782474a2c9c214498502aa862d 39088 java optional 
pgpainless_1.6.6-2.debian.tar.xz
 636886f066faaf5b5987067e0efab4d0 20559 java optional 

Bug#1064723: marked as done (libio-async-loop-epoll-perl: FTBFS: Can't locate Test2/V0.pm in @INC)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:04:37 +
with message-id 
and subject line Bug#1064723: fixed in libio-async-loop-epoll-perl 0.22-2
has caused the Debian Bug report #1064723,
regarding libio-async-loop-epoll-perl: FTBFS: Can't locate Test2/V0.pm in @INC
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.)


-- 
1064723: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064723
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libio-async-loop-epoll-perl
Version: 0.22-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   /usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wl,-z,relro"
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'IO-Async-Loop-Epoll' version '0.22'
>dh_auto_build
>   /usr/bin/perl Build
> Building IO-Async-Loop-Epoll
>dh_auto_test
>   /usr/bin/perl Build test --verbose 1
> t/00use.t ... 
> 1..1
> ok 1 - use IO::Async::Loop::Epoll;
> ok
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/01loop-io.t line 6.
> BEGIN failed--compilation aborted at t/01loop-io.t line 6.
> t/01loop-io.t ... 
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/02loop-timer.t line 6.
> BEGIN failed--compilation aborted at t/02loop-timer.t line 6.
> t/02loop-timer.t  
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/03loop-signal.t line 6.
> BEGIN failed--compilation aborted at t/03loop-signal.t line 6.
> t/03loop-signal.t ... 
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/04loop-idle.t line 6.
> BEGIN failed--compilation aborted at t/04loop-idle.t line 6.
> t/04loop-idle.t 

Bug#1064709: marked as done (libio-async-loop-glib-perl: FTBFS: Can't locate Test2/V0.pm in @INC)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:04:43 +
with message-id 
and subject line Bug#1064709: fixed in libio-async-loop-glib-perl 0.22-2
has caused the Debian Bug report #1064709,
regarding libio-async-loop-glib-perl: FTBFS: Can't locate Test2/V0.pm in @INC
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.)


-- 
1064709: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064709
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libio-async-loop-glib-perl
Version: 0.22-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   /usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wl,-z,relro"
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'IO-Async-Loop-Glib' version '0.22'
>dh_auto_build
>   /usr/bin/perl Build
> Building IO-Async-Loop-Glib
>dh_auto_test
>   /usr/bin/perl Build test --verbose 1
> t/00use.t  
> ok 1 - use IO::Async::Loop::Glib;
> 1..1
> ok
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/01loop-io.t line 6.
> BEGIN failed--compilation aborted at t/01loop-io.t line 6.
> t/01loop-io.t  
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/02loop-timer.t line 6.
> BEGIN failed--compilation aborted at t/02loop-timer.t line 6.
> t/02loop-timer.t . 
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/03loop-signal.t line 6.
> BEGIN failed--compilation aborted at t/03loop-signal.t line 6.
> t/03loop-signal.t  
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/04loop-idle.t line 6.
> BEGIN failed--compilation aborted at t/04loop-idle.t line 6.
> t/04loop-idle.t .. 

Bug#1064700: marked as done (python-stestr: FTBFS: stestr fails)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:56:48 +0100
with message-id 
and subject line Re: Bug#1064700: python-stestr: FTBFS: stestr fails
has caused the Debian Bug report #1064700,
regarding python-stestr: FTBFS: stestr 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.)


-- 
1064700: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064700
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-stestr
Version: 4.1.0-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> for i in 3.12 3.11 ; do \
>   python3 setup.py install -f --install-layout=deb 
> --root=/<>/debian/tmp ; \
> done
> /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)
> /usr/lib/python3/dist-packages/setuptools/command/develop.py:40: 
> EasyInstallDeprecationWarning: easy_install command is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` and ``easy_install``.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://github.com/pypa/setuptools/issues/917 for details.
> 
> 
> 
> !!
>   easy_install.initialize_options(self)
> /usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py:66: 
> SetuptoolsDeprecationWarning: setup.py install is deprecated.
> !!
> 
> 
> 
> Please avoid running ``setup.py`` directly.
> Instead, use pypa/build, pypa/installer or other
> standards-based tools.
> 
> See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html 
> for details.
> 
> 
> 
> !!
>   self.initialize_options()
> running install
> [pbr] Generating AUTHORS
> [pbr] AUTHORS complete (0.0s)
> running build
> running build_py
> creating build
> creating build/lib
> creating build/lib/stestr
> creating build/lib/stestr/tests
> creating build/lib/stestr/tests/repository
> copying stestr/tests/repository/__init__.py -> 
> build/lib/stestr/tests/repository
> copying stestr/tests/repository/test_util.py -> 
> build/lib/stestr/tests/repository
> copying stestr/tests/repository/test_file.py -> 
> build/lib/stestr/tests/repository
> creating build/lib/stestr/repository
> copying stestr/repository/__init__.py -> build/lib/stestr/repository
> copying stestr/repository/memory.py -> build/lib/stestr/repository
> copying stestr/repository/abstract.py -> build/lib/stestr/repository
> copying stestr/repository/util.py -> build/lib/stestr/repository
> copying stestr/repository/file.py -> build/lib/stestr/repository
> creating build/lib/stestr/tests/files
> copying stestr/tests/files/__init__.py -> build/lib/stestr/tests/files
> creating build/lib/stestr/subunit_runner
> copying stestr/subunit_runner/run.py -> build/lib/stestr/subunit_runner
> copying stestr/subunit_runner/__init__.py -> build/lib/stestr/subunit_runner
> copying stestr/subunit_runner/program.py -> build/lib/stestr/subunit_runner
> copying stestr/tests/test_scheduler.py -> build/lib/stestr/tests
> copying stestr/tests/test_user_config.py -> build/lib/stestr/tests
> copying stestr/tests/test_bisect_tests.py -> build/lib/stestr/tests
> copying stestr/tests/test_user_config_return_codes.py -> 
> build/lib/stestr/tests
> copying stestr/tests/__init__.py -> build/lib/stestr/tests
> copying stestr/tests/test_bisect_return_codes.py -> build/lib/stestr/tests
> copying stestr/tests/test_config_file.py -> build/lib/stestr/tests
> copying stestr/tests/base.py -> build/lib/stestr/tests
> copying 

Bug#1064757: marked as done (python-swiftclient: FTBFS: stestr fails)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 23:58:00 +0100
with message-id <354cfcca-3290-4f82-8a08-757971247...@goirand.fr>
and subject line Re: Bug#1064757: python-swiftclient: FTBFS: stestr fails
has caused the Debian Bug report #1064757,
regarding python-swiftclient: FTBFS: stestr 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.)


-- 
1064757: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064757
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-swiftclient
Version: 1:4.4.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 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 '/<>'
> make[1]: pyversions: No such file or directory
> py3versions: no X-Python3-Version in control file, using supported versions
> PYBUILD_SYSTEM=custom \
>   PYBUILD_TEST_ARGS="cd {build_dir} ; {interpreter} -m stestr run" \
>   dh_auto_test
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.12_swiftclient/build ; python3.12 -m 
> stestr run
> stestr: 'run' is not a stestr command. See 'stestr --help'.
> Did you mean one of these?
>   help
> E: pybuild pybuild:391: test: plugin custom failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.12_swiftclient/build ; python3.12 -m 
> stestr run
> I: pybuild base:305: cd 
> /<>/.pybuild/cpython3_3.11_swiftclient/build ; python3.11 -m 
> stestr run
> stestr: 'run' is not a stestr command. See 'stestr --help'.
> Did you mean one of these?
>   help
> E: pybuild pybuild:391: test: plugin custom failed with: exit code=2: cd 
> /<>/.pybuild/cpython3_3.11_swiftclient/build ; python3.11 -m 
> stestr run
> dh_auto_test: error: pybuild --test -i python{version} -p "3.12 3.11" 
> returned exit code 13


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/python-swiftclient_4.4.0-4_unstable.log

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

On 2/25/24 20:48, Lucas Nussbaum wrote:

Source: python-swiftclient
Version: 1:4.4.0-4
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


False positive (can't reproduce) probably due to python3-testtools 2.7.1-1.

Cheers,

Thomas Goirand (zigo)--- End Message ---

Bug#1064684: marked as done (libio-async-loop-mojo-perl: FTBFS: Can't locate Test2/V0.pm in @INC)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 22:51:01 +
with message-id 
and subject line Bug#1064684: fixed in libio-async-loop-mojo-perl 0.07-2
has caused the Debian Bug report #1064684,
regarding libio-async-loop-mojo-perl: FTBFS: Can't locate Test2/V0.pm in @INC
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.)


-- 
1064684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064684
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libio-async-loop-mojo-perl
Version: 0.07-1
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>   /usr/bin/perl Build.PL --installdirs vendor --config "optimize=-g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wdate-time -D_FORTIFY_SOURCE=2" --config "ld=x86_64-linux-gnu-gcc -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong 
> -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection 
> -Wl,-z,relro"
> Created MYMETA.yml and MYMETA.json
> Creating new 'Build' script for 'IO-Async-Loop-Mojo' version '0.07'
>dh_auto_build
>   /usr/bin/perl Build
> Building IO-Async-Loop-Mojo
>dh_auto_test
>   /usr/bin/perl Build test --verbose 1
> # Using Mojo::Reactor::Poll
> t/00use.t ... 
> ok 1 - use IO::Async::Loop::Mojo;
> 1..1
> ok
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/01loop-io.t line 6.
> BEGIN failed--compilation aborted at t/01loop-io.t line 6.
> t/01loop-io.t ... 
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/02loop-timer.t line 6.
> BEGIN failed--compilation aborted at t/02loop-timer.t line 6.
> t/02loop-timer.t  
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/03loop-signal.t line 6.
> BEGIN failed--compilation aborted at t/03loop-signal.t line 6.
> t/03loop-signal.t ... 
> Dubious, test returned 2 (wstat 512, 0x200)
> No subtests run 
> Can't locate Test2/V0.pm in @INC (you may need to install the Test2::V0 
> module) (@INC entries checked: /<>/blib/lib 
> /<>/blib/arch /etc/perl 
> /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 
> /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 
> /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 
> /usr/share/perl/5.38 /usr/local/lib/site_perl .) at 
> /usr/share/perl5/IO/Async/LoopTests.pm line 16.
> BEGIN failed--compilation aborted at /usr/share/perl5/IO/Async/LoopTests.pm 
> line 16.
> Compilation failed in require at t/04loop-idle.t line 6.
> BEGIN failed--compilation aborted at t/04loop-idle.t line 

Bug#989706: marked as done (csvkit: DeprecationWarning from csvclean)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 14:37:14 -0800
with message-id 
and subject line Re: Bug#989706: csvkit: DeprecationWarning from csvclean
has caused the Debian Bug report #989706,
regarding csvkit: DeprecationWarning from csvclean
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.)


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

Dear Maintainer,

Thank you very much for sharing your valuable time
and skill to maintain Debian's csvkit package.

Here's a one-liner that causes its "csvclean"
command to complain, at least on my computer.

bash$ echo -e "1,2,3\n4,5,6\n7,8" | csvclean 
/usr/lib/python3/dist-packages/unittest2/compatibility.py:143: 
DeprecationWarning: Using or importing the ABCs from 'collections' instead of 
from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will stop 
working
1 error logged to stdin_err.csv

I'd like to think eliminating the warning is as
easy as importing the ABCs from 'collections.abc'.

Maybe you'd like to use my little one liner to
test fixes for csvkit and python3-csvkit.

Thanks again,
Kingsley

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 4.4.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)

Versions of packages csvkit depends on:
ii  python3-csvkit  1.0.5-2
pn  python3:any 

csvkit recommends no packages.

Versions of packages csvkit suggests:
ii  csvkit-doc  1.0.2-1

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Jun 10, 2021 at 04:08:09PM -0700, Kingsley G. Morse Jr. wrote:
> Here's a one-liner that causes its "csvclean"
> command to complain, at least on my computer.
> 
> bash$ echo -e "1,2,3\n4,5,6\n7,8" | csvclean 
> /usr/lib/python3/dist-packages/unittest2/compatibility.py:143: 
> DeprecationWarning: Using or importing the ABCs from 'collections' instead of 
> from 'collections.abc' is deprecated since Python 3.3, and in 3.10 it will 
> stop working
> 1 error logged to stdin_err.csv

I can't reproduce the reported behavior on Debian bullseye, bookwork, 
trixie, or unstable.  I suspect it was resolved during the bullseye
release cycle.

Therefore, I am closing the bug.  Feel free to either reopen or file a
new bug if you detect any problems with csvkit.

Thank you,
tony--- End Message ---

Bug#1064614: marked as done (csvkit: please drop obsolete python3-six build-dependency)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 22:34:16 +
with message-id 
and subject line Bug#1064614: fixed in csvkit 1.4.0-1
has caused the Debian Bug report #1064614,
regarding csvkit: please drop obsolete python3-six build-dependency
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.)


-- 
1064614: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: csvkit
Version: 1.1.1-2
Severity: normal

"six" is not used anymore by csvkit,
please remove it from the build-dependencies.

Greetings
--- End Message ---
--- Begin Message ---
Source: csvkit
Source-Version: 1.4.0-1
Done: tony mancill 

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

Debian distribution maintenance software
pp.
tony mancill  (supplier of updated csvkit package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 14:07:55 -0800
Source: csvkit
Architecture: source
Version: 1.4.0-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: tony mancill 
Closes: 1064614
Changes:
 csvkit (1.4.0-1) unstable; urgency=medium
 .
   * Team upload.
   * Refresh patches for new upstream release
   * Remove build-dep on python3-six (Closes: #1064614)
   * Add build-dep on furo
   * Freshen years in debian/copyright
Checksums-Sha1:
 305de17f4db4052a4ead79a14e1ea61847c7192d 2475 csvkit_1.4.0-1.dsc
 e96ca0ad8e086f1904260b9c5e9fbc845787541a 3982921 csvkit_1.4.0.orig.tar.gz
 d3e6f8927c67c125df849a3c96dbe794f2aa5ca6 5272 csvkit_1.4.0-1.debian.tar.xz
 120af515cb0da12fd8002ef40eb4556dd21edf3c 9466 csvkit_1.4.0-1_amd64.buildinfo
Checksums-Sha256:
 4d030774de4abcd4aa24c54eb1f30ac6571ea1b71fa726f2f5e91dcaf92152db 2475 
csvkit_1.4.0-1.dsc
 b618ce339260ce0922966e13a9a3c0bbc2b73f6f5dfce3c29865ec212ef9c6b6 3982921 
csvkit_1.4.0.orig.tar.gz
 72f1003d1c40c309ddebff650d89756ad78cc6af9530a29c1ba3a92db3f172ea 5272 
csvkit_1.4.0-1.debian.tar.xz
 30842ad2fadd6af109ac24c59d2998d9ae9f99fcc4443218d6b44f0d5e9017b7 9466 
csvkit_1.4.0-1_amd64.buildinfo
Files:
 864790fae4d593391406a9ef17c2c79c 2475 utils optional csvkit_1.4.0-1.dsc
 db42090443d8cf39bdfa35fbf7e0b9f6 3982921 utils optional 
csvkit_1.4.0.orig.tar.gz
 aaa0b5304118485d44b9e4e4fc04e443 5272 utils optional 
csvkit_1.4.0-1.debian.tar.xz
 c30cd6bbcfbdbe08314f68f7e781f37a 9466 utils optional 
csvkit_1.4.0-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmXbvYcUHHRtYW5jaWxs
QGRlYmlhbi5vcmcACgkQIdIFiZdLPpa4UxAAzEtLRC6389+sBlws0FLtExg1rgIL
DsXXmDqDUP4RNjw8y8fEEoRWiXJC4hUZQ0vDp/NDU5qCVmCGrufws7L94YHfa2V1
sibJ6LGUeTAurJ+PkChNSdvfq53J3HDnsmm+Wd8szXn5xdxsqzGwZ4acMFFC7NIi
eFkZ9RCiWqS5yndr4ZhdLGmDDP5T9qN5FVeUS0wqzL6tyLmqTkE53bVLu1vxs+wZ
pm7r64tYFm/kXpJ4WssxbCcawk9dhXO6vU9womwUE2FjPbvKtnQ18iw9eATlN866
muOvfjxhSqdxv1twijF0+9K38Q2mBsDatlo7IlqNCYIIi9KvEc4a7FXFRwGxLeVu
G7e2GePDGhSLAyXlzBuulZR3MOdaEJIbN8tBZv35ORyXVbf4yHJLnTpf/MjXV16M
p6zRDckbTmT657IvdlXaAu6zX2yfr3Y1xTS+28X6BcPJPM2vNi991wGxa3s/l6W6
RFWfWp8P2SlgBraPhugWhe9tcXSLHjw0whf96zQrCzpZhHWlwzmE3vZIYMV0dWyJ
/3lhNs6J8/cy4mAe8HRGNvF2T7Ex6iN5nb+pEF4qGttYC7B4rZXHwVBFMVOLPocJ
PFLg6HfsvPy6FanWsOIoUfoEAVA7nnDZzuylYjm9phiJig+BUbYFPgFdzae++c2A
dmkp4AVWKLyHSAw=
=MC3A
-END PGP SIGNATURE-



pgppPjKqSzoya.pgp
Description: PGP signature
--- End Message ---

Bug#933756: marked as done (ITS: conman)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 22:55:07 +0100
with message-id <874jdw5hvo.fsf@fin.soreny>
and subject line Re: ITS: conman
has caused the Debian Bug report #933756,
regarding ITS: conman
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.)


-- 
933756: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=933756
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: conman
Version: 0.2.7-1
Severity: important

Dear Maintainer,

  I intend to salvage package conman, which has note been updated since 2015, 
first upload, despite BTS requests to release updated version.
  My plan is to add myself as comaintainer and release newer upstream version.

Regards
--- End Message ---
--- Begin Message ---
On Sat, 03 Aug 2019 00:26:49 +0200 
"=?utf-8?b?SMOpY3RvciBPcsOzbiBNYXJ0w61uZXo=?="  wrote:

> I intend to salvage package conman, which has note been updated since
> 2015, first upload, despite BTS requests to release updated version.
> My plan is to add myself as comaintainer and release newer upstream
> version.

Hi Héctor,

Since conman is in the debian (alias collab-maint) namespace, I simply
added myself and uploaded the latest upstream version.  Hope it was not
against your plans.  If I broke something for you, I'm absolutely
willing to fix it.  If you feel like adding something, please go on!
-- 
Regards,
Feri.--- End Message ---

Bug#841957: marked as done (libgs9-common: URW fonts: Missing glyphs for uk language)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 14:47:37 -0600
with message-id <2208071.NgBsaNRSFp@riemann>
and subject line Re: libgs9-common: URW fonts: Missing glyphs for uk language
has caused the Debian Bug report #841957,
regarding libgs9-common: URW fonts: Missing glyphs for uk language
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.)


-- 
841957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=841957
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgs9-common 
Version: 9.06~dfsg-2+deb8u3 
Severity: normal 

Dear Maintainer, 

In ghostscript-9.06 present in Jessie repository there are no Ukrainian and 
Russian glyphs in a number of fonts. Namely, in all the URW family. 

These fonts are invisible in LibreOffice, for example. 

I checked it using the following command: 

$ fc-validate -l uk /usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-Ligh 
/usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-Ligh:0 Missing 72 
glyph(s) to satisfy the coverage for uk language 

$ fc-validate -l ru /usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-Ligh 
/usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-Ligh:0 Missing 66 
glyph(s) to satisfy the coverage for ru language 

I reported this bug upstream: 
http://bugs.ghostscript.com/show_bug.cgi?id=697224 

however, they answered that everything is allright in the newer Ghostscript 
version, and the only way to get this working is to upgrade to the lates 
version. 




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

Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/4 CPU cores) 
Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8) 
Shell: /bin/sh linked to /bin/dash 
Init: systemd (via /run/systemd/system) 

libgs9-common depends on no packages. 

Versions of packages libgs9-common recommends: 
ii  fonts-droid  1:4.4.4r2-6 

libgs9-common suggests no packages. 

-- no debconf information 
--- End Message ---
--- Begin Message ---
Hello,

I am sorry that no timely action was taken on your report.  However, as of 
2024, the oldest version shipping in Debian is 9.27 and the upstream bug you 
opened indicates things were fixed in 9.20.

Moreover, I checked the coverage remains present in ghostscript 10.02.1 
(below), so closing this bug.

$ fc-validate -l uk  /usr/share/ghostscript/10.02.1/Resource/Font/URWBookman-
Light
/usr/share/ghostscript/10.02.1/Resource/Font/URWBookman-Light:0 Satisfy the 
coverage for uk language

$ fc-validate -l ru  /usr/share/ghostscript/10.02.1/Resource/Font/URWBookman-
Light
/usr/share/ghostscript/10.02.1/Resource/Font/URWBookman-Light:0 Satisfy the 
coverage for ru language

-Steve

On Mon, 24 Oct 2016 22:33:04 +0300 v...@ukr.net wrote:
> Package: libgs9-common 
> Version: 9.06~dfsg-2+deb8u3 
> Severity: normal 
> 
> Dear Maintainer, 
> 
> In ghostscript-9.06 present in Jessie repository there are no Ukrainian and 
> Russian glyphs in a number of fonts. Namely, in all the URW family. 
> 
> These fonts are invisible in LibreOffice, for example. 
> 
> I checked it using the following command: 
> 
> $ fc-validate -l uk /usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-
Ligh 
> /usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-Ligh:0 Missing 72 
> glyph(s) to satisfy the coverage for uk language 
> 
> $ fc-validate -l ru /usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-
Ligh 
> /usr/share/ghostscript/9.06/Resource/Font/URWBookmanL-Ligh:0 Missing 66 
> glyph(s) to satisfy the coverage for ru language 
> 
> I reported this bug upstream: 
> http://bugs.ghostscript.com/show_bug.cgi?id=697224 
> 
> however, they answered that everything is allright in the newer Ghostscript 
> version, and the only way to get this working is to upgrade to the lates 
> version. 
> 
> 
> 
> 
> -- System Information: 
> Debian Release: 8.6 
>   APT prefers stable 
>   APT policy: (500, 'stable') 
> Architecture: amd64 (x86_64) 
> 
> Kernel: Linux 4.2.0-0.bpo.1-amd64 (SMP w/4 CPU cores) 
> Locale: LANG=uk_UA.utf8, LC_CTYPE=uk_UA.utf8 (charmap=UTF-8) 
> Shell: /bin/sh linked to /bin/dash 
> Init: systemd (via /run/systemd/system) 
> 
> libgs9-common depends on no packages. 
> 
> Versions of packages libgs9-common recommends: 
> ii  fonts-droid  1:4.4.4r2-6 
> 
> libgs9-common suggests no packages. 
> 
> -- no debconf information 
> 
> 


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

Processed: your mail

[Debian Bug Tracking System]

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

> fixed 1050677 122.0.6261.57-1
Bug #1050677 [chromium] chromium: VAAPI acceleration not working on Chromium 116
Marked as fixed in versions chromium/122.0.6261.57-1.
> close 1050677
Bug #1050677 [chromium] chromium: VAAPI acceleration not working on Chromium 116
Marked Bug as done
> stop
Stopping processing here.

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

Bug#1049079: marked as done (hipsparse: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 21:49:05 +
with message-id 
and subject line Bug#1049079: fixed in hipsparse 5.7.1-1~exp1
has caused the Debian Bug report #1049079,
regarding hipsparse: 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.)


-- 
1049079: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049079
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: hipsparse
Version: 5.5.1-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 hipsparse
> dpkg-buildpackage: info: source version 5.5.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Cordell Bloor 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean -Scmake
>dh_auto_clean -O-Scmake
>dh_clean -O-Scmake
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building hipsparse using existing 
> ./hipsparse_5.5.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: error: cannot represent change to docs/docBin/html/bc_s.png: 
> binary file contents changed
> dpkg-source: error: add docs/docBin/html/bc_s.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to docs/docBin/html/bdwn.png: 
> binary file contents changed
> dpkg-source: error: add docs/docBin/html/bdwn.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to docs/docBin/html/closed.png: 
> binary file contents changed
> dpkg-source: error: add docs/docBin/html/closed.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: warning: file 
> hipsparse-5.5.1/docs/docBin/html/dir_9bb0cdb2fc6936e925cffa69d90b0c80_dep.md5 
> has no final newline (either original or modified version)
> dpkg-source: error: cannot represent change to 
> docs/docBin/html/dir_9bb0cdb2fc6936e925cffa69d90b0c80_dep.png: binary file 
> contents changed
> dpkg-source: error: add 
> docs/docBin/html/dir_9bb0cdb2fc6936e925cffa69d90b0c80_dep.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to docs/docBin/html/doc.png: 
> binary file contents changed
> dpkg-source: error: add docs/docBin/html/doc.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> docs/docBin/html/folderclosed.png: binary file contents changed
> dpkg-source: error: add docs/docBin/html/folderclosed.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: error: cannot represent change to 
> docs/docBin/html/folderopen.png: binary file contents changed
> dpkg-source: error: add docs/docBin/html/folderopen.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: warning: file hipsparse-5.5.1/docs/docBin/html/graph_legend.md5 
> has no final newline (either original or modified version)
> dpkg-source: error: cannot represent change to 
> docs/docBin/html/graph_legend.png: binary file contents changed
> dpkg-source: error: add docs/docBin/html/graph_legend.png in 
> debian/source/include-binaries if you want to store the modified binary in 
> the debian tarball
> dpkg-source: warning: file 
> 

Bug#1064746: marked as done (rust-async-executor: FTBFS: build-dependency not installable: librust-async-io-1+default-dev)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 21:11:07 +
with message-id 
and subject line Bug#1064746: fixed in rust-async-executor 1.5.4-3
has caused the Debian Bug report #1064746,
regarding rust-async-executor: FTBFS: build-dependency not installable: 
librust-async-io-1+default-dev
to be marked as done.

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

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


-- 
1064746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064746
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: rust-async-executor
Version: 1.5.4-2
Severity: serious
Justification: FTBFS
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20240224 ftbfs-trixie

Hi,

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


Relevant part (hopefully):
> +--+
> | Install package build dependencies  
>  |
> +--+
> 
> 
> Setup apt archive
> -
> 
> Merged Build-Depends: debhelper-compat (= 13), dh-cargo, 
> librust-async-channel-1+default-dev, librust-async-io-1+default-dev, 
> librust-async-lock-2+default-dev, librust-async-task-4+default-dev, 
> librust-concurrent-queue-2+default-dev, librust-easy-parallel-3+default-dev, 
> librust-fastrand-1+default-dev, librust-futures-lite-1-dev, 
> librust-once-cell-1+default-dev, librust-slab-0.4+default-dev (>= 0.4.4), 
> libstring-shellquote-perl, build-essential, fakeroot
> Filtered Build-Depends: debhelper-compat (= 13), dh-cargo, 
> librust-async-channel-1+default-dev, librust-async-io-1+default-dev, 
> librust-async-lock-2+default-dev, librust-async-task-4+default-dev, 
> librust-concurrent-queue-2+default-dev, librust-easy-parallel-3+default-dev, 
> librust-fastrand-1+default-dev, librust-futures-lite-1-dev, 
> librust-once-cell-1+default-dev, librust-slab-0.4+default-dev (>= 0.4.4), 
> libstring-shellquote-perl, build-essential, fakeroot
> dpkg-deb: building package 'sbuild-build-depends-main-dummy' in 
> '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'.
> Ign:1 copy:/<>/apt_archive ./ InRelease
> Get:2 copy:/<>/apt_archive ./ Release [615 B]
> Ign:3 copy:/<>/apt_archive ./ Release.gpg
> Get:4 copy:/<>/apt_archive ./ Sources [1112 B]
> Get:5 copy:/<>/apt_archive ./ Packages [1035 B]
> Fetched 2762 B in 0s (0 B/s)
> Reading package lists...
> Reading package lists...
> 
> Install main build dependencies (apt-based resolver)
> 
> 
> Installing build dependencies
> Reading package lists...
> Building dependency tree...
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
> 
> The following packages have unmet dependencies:
>  sbuild-build-depends-main-dummy : Depends: librust-async-io-1+default-dev 
> but it is not installable
> E: Unable to correct problems, you have held broken packages.
> apt-get failed.


The full build log is available from:
http://qa-logs.debian.net/2024/02/24/rust-async-executor_1.5.4-2_unstable.log

All bugs filed during this archive rebuild are listed at:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20240224;users=lu...@debian.org
or:
https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20240224=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: rust-async-executor
Source-Version: 1.5.4-3
Done: Jonas Smedegaard 

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

Debian distribution 

Bug#892235: marked as done (conman: Please update Conman to the latest version)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 21:34:15 +
with message-id 
and subject line Bug#892235: fixed in conman 0.3.1-1
has caused the Debian Bug report #892235,
regarding conman: Please update Conman to the latest version
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.)


-- 
892235: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: conman
Version: 0.2.7-1+b1
Severity: wishlist
Tags: upstream

Dear Maintainer,

Report is to request an upgrade to latest version, package functionality is ok 
currently.

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

Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set 
to en_US.UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages conman depends on:
ii  libc62.26-6
pn  libipmiconsole2  
ii  libwrap0 7.6.q-27

conman recommends no packages.

Versions of packages conman suggests:
pn  expect  
--- End Message ---
--- Begin Message ---
Source: conman
Source-Version: 0.3.1-1
Done: Ferenc Wágner 

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

Debian distribution maintenance software
pp.
Ferenc Wágner  (supplier of updated conman package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 21:54:41 +0100
Source: conman
Architecture: source
Version: 0.3.1-1
Distribution: unstable
Urgency: medium
Maintainer: Yao-Po Wang 
Changed-By: Ferenc Wágner 
Closes: 892235
Changes:
 conman (0.3.1-1) unstable; urgency=medium
 .
   * [dfc64c2] Upgrade watch file to version 4 and enable signature checking
   * [dcdf658] Add gbp.conf and switch to DEP-14 branch names
   * [fc4647d] Update upstream source from tag 'upstream/0.3.1' (Closes: 892235)
   * [471aaf5] Drop our patches.
 The hyphen fix went upstream, while the expect shebang was deemed
 unnecessary in https://github.com/dun/conman/issues/23.
   * [de2137a] Upgrade to Debhelper compat level 13
   * [f6ea8b5] Upgrade Standards-Version to 4.6.2 (no changes required)
   * [6be26b9] Our toolchain defaults to linking with --as-needed since bullseye
   * [537c3b6] Two patches fixing Lintian issues
   * [5a5e6c2] Add Pre-Depends substitution required by invoke-rc.d --skip-
 systemd-native
   * [abbc1ce] Add Perl dependency for the conmen wrapper script
   * [a1401de] Enable hardening
   * [22b8ff2] Advertise Rules-Requires-Root: no
   * [a5830f4] New patch: Fix font name typo in man page
   * [d91c33d] Lintian override for the directory-specific README files
   * [23b9bf4] Override Lintian tag about not installing examples
   * [ad7cb90] Subscribe to basic Salsa CI
   * [a36b2e2] Add myself to Uploaders
   * [3ca6773] Add my copyright to the packaging
Checksums-Sha1:
 03c01c9e6803bdbaf616a681f8d37bf6fe98a008 2145 conman_0.3.1-1.dsc
 60df1709b550e88f8363b9bee4def0195a29d2ae 201832 conman_0.3.1.orig.tar.xz
 76d03afb64bda40f7c614d2687d21de8258f11f5 833 conman_0.3.1.orig.tar.xz.asc
 4069eeb641e87e2495f69d777e63f17b3d4fa907 12312 conman_0.3.1-1.debian.tar.xz
 6ced9e54c1f4480aecf600ab0db07c70cd018083 6690 conman_0.3.1-1_amd64.buildinfo
Checksums-Sha256:
 79b0efc6822ffa1e6c2fcc21acd6f60ce7988245c70a265dde9b06fbe0d7f605 2145 
conman_0.3.1-1.dsc
 69b449e4a9e992f7e1c6becfb3689be723cefaf94c75226a0bae685df3bc4cb3 201832 
conman_0.3.1.orig.tar.xz
 fab6effd6332f4daef156e981517597e0ae0e75c57abbb8c717add113a93e1b0 833 
conman_0.3.1.orig.tar.xz.asc
 75a142a3c4575e951cd63ae3062f66f617b173b52027aca7dc12a4c14672796c 12312 
conman_0.3.1-1.debian.tar.xz
 16d9bb72778679190fbd6583f6a3937f3995310f896e091476bc74c65162dfac 6690 
conman_0.3.1-1_amd64.buildinfo
Files:
 734a904fa3813dab47bb3854a358e026 2145 comm optional conman_0.3.1-1.dsc
 

Bug#683641: marked as done (gs: -dDuplex ignored for pswrite/psmono/pdfwrite output devices)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 14:20:59 -0600
with message-id <46192170.fMDQidcC6G@riemann>
and subject line Re: gs: -dDuplex ignored for pswrite/psmono/pdfwrite output 
devices
has caused the Debian Bug report #683641,
regarding gs: -dDuplex ignored for pswrite/psmono/pdfwrite output devices
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.)


-- 
683641: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683641
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gs
Version: 8.62.dfsg.1-3.2lenny5
Severity: normal


Hello,

gs ignores -dDuplex option when using
pswrite/psmono/pdfwrite output drivers, i.e. it
doesn't insert /Duplex true pagedevice entry:
> xrgtn@ux230p:/tmp$ cat hello.ps world.ps 
> %!PS
> /Courier 30 selectfont
> 100 400 moveto
> (|-|3110, ) show
> showpage
> %!PS
> /Courier 30 selectfont
> 100 400 moveto
> (\\/\\/0R1d!) show
> showpage
> xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pswrite -dDuplex 
> -sOutputFile=o.ps hello.ps world.ps 
> GPL Ghostscript 8.71 (2010-02-10)
> Copyright (C) 2010 Artifex Software, Inc.  All rights reserved.
> This software comes with NO WARRANTY: see the file PUBLIC for details.
> Loading NimbusMonL-Regu font from 
> /usr/share/fonts/type1/gsfonts/n022003l.pfb... 2528792 1197912 1920356 624719 
> 1 done.
> xrgtn@ux230p:/tmp$ grep -i duplex o.ps 
> xrgtn@ux230p:/tmp$ 

So when I need /Duplex, I'm forced to generate
.pdf instead of .ps and then convert .pdf back
to .ps via pstopdf (libpoppler):
> xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -sOutputFile=o.pdf 
> -q hello.ps world.ps
> xrgtn@ux230p:/tmp$ pdftops -duplex o.pdf o.ps
> xrgtn@ux230p:/tmp$ grep -i duplex o.ps
>   { /Duplex true def } if
> xrgtn@ux230p:/tmp$ 

-- System Information:
Debian Release: 6.0.5
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'), 
(500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gs depends on:
ii  ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF
ii  ghostscript-x   8.71~dfsg2-9 The GPL Ghostscript PostScript/PDF

gs recommends no packages.

gs suggests no packages.

-- no debconf information

-- 
With best regards,
xrgtn
--- End Message ---
--- Begin Message ---
On Thu, 2 Aug 2012 16:09:43 +0300 Alexander Gattin  wrote:
> Package: gs
> Version: 8.62.dfsg.1-3.2lenny5
> Severity: normal
> 
> 
> Hello,
> 
> gs ignores -dDuplex option when using
> pswrite/psmono/pdfwrite output drivers, i.e. it
> doesn't insert /Duplex true pagedevice entry:

I believe that is by design, as the docs [1] only cover -dDuplex for IJS and 
Windows output devices.


[1] https://ghostscript.com/docs/9.54.0/Devices.htm

> > xrgtn@ux230p:/tmp$ cat hello.ps world.ps 
> > %!PS
> > /Courier 30 selectfont
> > 100 400 moveto
> > (|-|3110, ) show
> > showpage
> > %!PS
> > /Courier 30 selectfont
> > 100 400 moveto
> > (\\/\\/0R1d!) show
> > showpage
> > xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pswrite -dDuplex -
sOutputFile=o.ps hello.ps world.ps 
> > GPL Ghostscript 8.71 (2010-02-10)
> > Copyright (C) 2010 Artifex Software, Inc.  All rights reserved.
> > This software comes with NO WARRANTY: see the file PUBLIC for details.
> > Loading NimbusMonL-Regu font from /usr/share/fonts/type1/gsfonts/
n022003l.pfb... 2528792 1197912 1920356 624719 1 done.
> > xrgtn@ux230p:/tmp$ grep -i duplex o.ps 
> > xrgtn@ux230p:/tmp$ 
> 
> So when I need /Duplex, I'm forced to generate
> .pdf instead of .ps and then convert .pdf back
> to .ps via pstopdf (libpoppler):
> > xrgtn@ux230p:/tmp$ gs -dNOPAUSE -dBATCH -sDEVICE=pdfwrite -
sOutputFile=o.pdf -q hello.ps world.ps
> > xrgtn@ux230p:/tmp$ pdftops -duplex o.pdf o.ps
> > xrgtn@ux230p:/tmp$ grep -i duplex o.ps
> >   { /Duplex true def } if
> > xrgtn@ux230p:/tmp$ 
> 
> -- System Information:
> Debian Release: 6.0.5
>   APT prefers stable
>   APT policy: (990, 'stable'), (500, 'stable-updates'), (500, 'oldstable'), 
(500, 'testing')
> Architecture: i386 (i686)
> 
> Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages gs depends on:
> ii  ghostscript 8.71~dfsg2-9 The GPL Ghostscript PostScript/
PDF
> ii  ghostscript-x   8.71~dfsg2-9 The GPL Ghostscript PostScript/
PDF
> 
> gs recommends no packages.
> 
> gs suggests no packages.
> 
> -- no 

Bug#1064776: marked as done (bogusly redirects Bugs to debian-openoff...@lists.debian.org instead of the BTS)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 21:21:53 +0100
with message-id 
and subject line 
has caused the Debian Bug report #1064776,
regarding bogusly redirects Bugs to debian-openoff...@lists.debian.org instead 
of the BTS
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.)


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

Source: libreoffice

Version: 4:24.2.0-1

Severity: serious

Control: close -1 4:24.2.0-3


Am 23.02.24 um 17:14 schrieb Rene Engelhard:

Hi,

Am 23.02.24 um 08:02 schrieb HIGUCHI Daisuke (VDR dai):

Sorry, resending to BTS, not to debian-openoffice.


No problem, that -1 redirects the bug reports to debian-openoffice is 
a bug.


(Fixed in later versions but those are stuck after the t64 transition.)


Making a (RC) bug out of this.


Regards,


Rene
--- End Message ---
--- Begin Message ---

Version: 4:24.2.0-3--- End Message ---

Bug#1064666: marked as done (Errors were encountered while processing: initramfs-tools)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 20:22:52 +0100
with message-id <20240225192252.ggj3e4t3s7sza...@shell.thinkmo.de>
and subject line Re: Bug#1064666: Errors were encountered while processing:  
initramfs-tools
has caused the Debian Bug report #1064666,
regarding Errors were encountered while processing:  initramfs-tools
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.)


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

Package: initramfs-tools
Version: 0.142

Sequence:

$ sudo apt-get update && sudo apt-get upgrade

The original output, now lost, said that subcommand dpkg had failed.

Try again:

alison@remerge:~/gitsrc/SCALE2024$ sudo apt-get install initramfs-tools
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
initramfs-tools is already the newest version (0.142).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] Y
Setting up initramfs-tools (0.142) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.7.0
W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module 
i915
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for 
module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for 
module i915

cpio: write error: No space left on device
E: mkinitramfs failure cpio 2
update-initramfs: failed for /boot/initrd.img-6.7.0 with 1.
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess 
returned error exit status 1

Errors were encountered while processing:
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

alison@remerge:~/gitsrc/SCALE2024$ apt-cache show initramfs-tools
Package: initramfs-tools
Version: 0.142
Installed-Size: 113
Maintainer: Debian kernel team 
Architecture: all
Provides: linux-initramfs-tool
Depends: initramfs-tools-core (= 0.142), linux-base
Suggests: bash-completion
Conflicts: linux-initramfs-tool, usplash (<< 0.5.50)
Breaks: e2fsprogs (<< 1.42.13), initscripts (<< 2.88dsf-59.3~), upstart
Description-en: generic modular initramfs generator (automation)
 This package builds a bootable initramfs for Linux kernel packages.  
The

 initramfs is loaded along with the kernel and is responsible for
 mounting the root filesystem and starting the main init system.
Description-md5: f406a6ad4452bdc36e9957a711143c2e
Multi-Arch: foreign
Tag: admin::boot, admin::filesystem, admin::install, admin::kernel,
 devel::lang:c, devel::library, implemented-in::c,
 implemented-in::shell, interface::commandline, role::devel-lib,
 role::program, scope::application, scope::utility, works-with::archive
Section: utils
Priority: optional
Filename: pool/main/i/initramfs-tools/initramfs-tools_0.142_all.deb
Size: 72864
MD5sum: b00b1c4ad31046ed1f80852bf20161f2
SHA256: dd1b867fd967471b0f775fdb3b4a534d4ae70bdb56a93b1ffcf60965813b

alison@remerge:~/gitsrc/SCALE2024$ apt-cache show linux-base
Package: linux-base
Version: 4.9
Installed-Size: 77
Maintainer: Debian Kernel Team 
Architecture: all
Replaces: kernel-common (<= 13.018+nmu1)
Depends: debconf (>= 0.5) | debconf-2.0
Breaks: kernel-common (<= 13.018+nmu1), linux-perf (<< 5.16.2-1~exp1)
Description-en: Linux image base package
 This package contains files and support scripts for all Linux
 images.
Description-md5: 441643227abc8006d7ae05aa2312ff51
Multi-Arch: foreign
Tag: admin::boot, devel::lang:perl, devel::library, implemented-in::c,
 implemented-in::perl, implemented-in::shell, role::devel-lib,
 role::metapackage, role::program
Section: kernel
Priority: optional
Filename: pool/main/l/linux-base/linux-base_4.9_all.deb
Size: 31784
MD5sum: 85b95cf515416ea18c856b37f7d41971
SHA256: 98be49c7067b058535496222a03a559b0fc205befa5b4e7ca5e1043ce708109a

alison@remerge:~/gitsrc/SCALE2024$ ls -l /lib/*/libc.so.6
-rwxr-xr-x 1 root root 2225144 Jan 30 10:20 
/lib/i386-linux-gnu/libc.so.6
-rwxr-xr-x 1 root root 1926256 Jan 30 10:20 
/lib/x86_64-linux-gnu/libc.so.6


Initramfs was NOT updated:

alison@remerge:~/gitsrc/SCALE2024$ ls -lt /boot/initrd*
-rw-r--r-- 1 root root 528349886 Feb 11 08:49 /boot/initrd.img-6.7.0
-rw-r--r-- 1 root root  80783160 Jan 18 18:21 
/boot/initrd.img-6.5.0-5-amd64
-rw-r--r-- 1 root root  80789463 Jan 18 18:21 

Bug#1063443: marked as done (pysimplesoap: not compatible with Python 3.12)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 18:22:23 +
with message-id 
and subject line Bug#1063443: fixed in pysimplesoap 1.16.2-6
has caused the Debian Bug report #1063443,
regarding pysimplesoap: not compatible with Python 3.12
to be marked as done.

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

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


-- 
1063443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063443
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysimplesoap
Version: 1.16.2-5
Severity: serious
Tags: sid trixie patch
User: debian-pyt...@lists.debian.org
Usertags: python3.12

Hi Maintainer

pysimplesoap uses distutils.version.LooseVersion which is deprecated
in Python3.12.  This can be seen in the autopkgtest failure of
reportbug (#1061837).

I attach the patch applied in Ubuntu.

Regards
Graham


pysimplesoap-python3.12.debdiff
Description: Binary data
--- End Message ---
--- Begin Message ---
Source: pysimplesoap
Source-Version: 1.16.2-6
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated pysimplesoap package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Feb 2024 18:56:20 +0100
Source: pysimplesoap
Architecture: source
Version: 1.16.2-6
Distribution: unstable
Urgency: medium
Maintainer: Sandro Tosi 
Changed-By: Andreas Tille 
Closes: 1063443
Changes:
 pysimplesoap (1.16.2-6) unstable; urgency=medium
 .
   * Team upload.
   * Replace distutils by setuptools
 Replace distutils in Debian patch
 Closes: #1063443
   * Standards-Version: 4.6.2 (routine-update)
   * Testsuite: autopkgtest-pkg-python (routine-update)
   * Build-Depends: s/dh-python/dh-sequence-python3/ (routine-update)
   * Rules-Requires-Root: no (routine-update)
   * watch file standard 4 (routine-update)
Checksums-Sha1:
 7c96a2ce40d2a4a263e55820087e825835dc23eb 2115 pysimplesoap_1.16.2-6.dsc
 7094005762b212420ff998b82d1357ddbdb16a55 6516 
pysimplesoap_1.16.2-6.debian.tar.xz
 a6ac1bff64524da9ffb132538d4740568e347ab7 6982 
pysimplesoap_1.16.2-6_amd64.buildinfo
Checksums-Sha256:
 996d8b70de52fb6c382a37520433677c6e48f16a5fa67908ca53628ff26c46b8 2115 
pysimplesoap_1.16.2-6.dsc
 268cb4c4498778f014c97d003d827a0f37e73e2e7125e94100da0c141173aa9a 6516 
pysimplesoap_1.16.2-6.debian.tar.xz
 4b66e31b25a8f6105168ef21857d8033516f2c62309dd5a68cad1fb5006d1ee3 6982 
pysimplesoap_1.16.2-6_amd64.buildinfo
Files:
 938fbeb59125db27ae86b28337dabd8e 2115 python optional pysimplesoap_1.16.2-6.dsc
 199c5f70d34c463b6be61aa53b294130 6516 python optional 
pysimplesoap_1.16.2-6.debian.tar.xz
 85eda8cbbb504dacc2629cb6113011a2 6982 python optional 
pysimplesoap_1.16.2-6_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXbgHgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFCGQ//RnFtnqLqAxSyV8UviepbWcC0YVdxK8d+
HFcxkPxxsmdwT+JmGcna6Vm7oT68TgJQc/b16vYZxn3corIRdw0E1bhsYlK0XZyN
n5XFpgEYeALqsZylzBliWD6+kUqY9HIsdTGFEOKdA6oPZA2yyiVu8SK8sQ4PmxqI
tUPsqHWOtGgzkoxihfhSRQSRf3wh33KYf3KG5reeWE6GwgAuEuoBTXqPGXovk3MT
agcp8/WzWl+6cjhe5x+xIdOqYyYzo2NGRlSGMqlCJCvGIKxFkOANtJHuJsY/0CTJ
aJNp6kpZAy712ODBkH/COUCFp8vq3Z0/OyCa0alg0N3sQ2EzvHvDNyxl6D6T+X9P
RmKzu+IkOt9A7q7hOEK3XWyR8mbC8FrdQrWlrdlOjUz/wSN9NF73vTY2/FTnfuXx
ywIsKFTpGzVBI0X/ekp6Et8Qee8eMBaQouA2Ey2NWic/8Q4hpTogInV0YfQavNms
lyM5doNJWC9IIcvxRW9Ii7VjWe+kwBtFSiXftpHKDM2vev7I+Auc5FDo0UlyAB+t
OIrJaNjTAY4uT2bEc+5ZcD+IpgK7pa4Zsy/b6qx/Mk86H102Mw4TdoS4CkqiBb0N
gfJQ6OG4M18QRp7QV4IX4pO0a8GRbkLcYwSQnt63W2+AaxuZpPtVOO9jSFgxw6w3
aU+qjdJ9bbI=
=Pd5l
-END PGP SIGNATURE-



pgpoTjSfehWwh.pgp
Description: PGP signature
--- End Message ---

Bug#1043959: marked as done (as31: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 18:19:18 +
with message-id 
and subject line Bug#1043959: fixed in as31 2.3.1-10
has caused the Debian Bug report #1043959,
regarding as31: 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.)


-- 
1043959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: as31
Version: 2.3.1-9
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 as31
> dpkg-buildpackage: info: source version 2.3.1-9
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Bdale Garbee 
>  dpkg-source --before-build .
>  fakeroot debian/rules clean
> dh_testdir
> dh_testroot
> rm -f build-stamp configure-stamp
> [ ! -f Makefile ] || /usr/bin/make clean
> make[1]: Entering directory '/<>'
> Making clean in .
> make[2]: Entering directory '/<>'
> make[2]: Nothing to be done for 'clean-am'.
> make[2]: Leaving directory '/<>'
> Making clean in examples
> make[2]: Entering directory '/<>/examples'
> make[2]: Nothing to be done for 'clean'.
> make[2]: Leaving directory '/<>/examples'
> Making clean in as31
> make[2]: Entering directory '/<>/as31'
> test -z "as31 " || rm -f as31 
> test -z "as31gtk" || rm -f as31gtk
> rm -f *.o core *.core
> make[2]: Leaving directory '/<>/as31'
> make[1]: Leaving directory '/<>'
> dh_clean 
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building as31 using existing ./as31_2.3.1.orig.tar.gz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: executable mode 0755 of 'config.status' will not be 
> represented in diff
> dpkg-source: info: local changes detected, the modified files are:
>  as31-2.3.1/Makefile
>  as31-2.3.1/as31/Makefile
>  as31-2.3.1/config.log
>  as31-2.3.1/config.status
>  as31-2.3.1/configure
>  as31-2.3.1/examples/Makefile
> dpkg-source: error: aborting due to unexpected upstream changes, see 
> /tmp/as31_2.3.1-9.diff.Xt5MQZ
> 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/as31_2.3.1-9_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: as31
Source-Version: 2.3.1-10
Done: Bdale Garbee 

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

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

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

Debian distribution maintenance software
pp.
Bdale Garbee  (supplier of updated as31 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 

Bug#1031189: marked as done (libogre-dev: Does not automatically derive plugin path)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 19:02:40 +0100
with message-id 
and subject line Re: libogre-dev: Does not automatically derive plugin path
has caused the Debian Bug report #1031189,
regarding libogre-dev: Does not automatically derive plugin path
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.)


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

Dear Maintainer,

libogre-1.12-dev installs Ogre plugins to /usr/lib/x86_64-linux-gnu/OGRE -
however, by default, Ogre is not searching in this directory when loading
plugins at run time.

matthew@matthew-laptop:~$ ls 
/usr/lib/x86_64-linux-gnu/OGRE/RenderSystem_GL.so.1.12.10
/usr/lib/x86_64-linux-gnu/OGRE/RenderSystem_GL.so.1.12.10

When I try and load RenderSystem_GL using:

root.getRenderSystemByName("OpenGL Rendering Subsystem");

I see that Ogre searches the following locations:

Loading library RenderSystem_GL.so.1.12.10
  8615: find library=RenderSystem_GL.so.1.12.10 [0]; searching
  8615:  search cache=/etc/ld.so.cache
  8615:  search 
path=/lib/x86_64-linux-gnu/tls/haswell/x86_64:/lib/x86_64-linux-gnu/tls/haswell:/lib/x86_64-linux-gnu/tls/x86_64:/lib/x86_64-linux-gnu/tls:/lib/x86_64-linux-gnu/haswell/x86_64:/lib/x86_64-linux-gnu/haswell:/lib/x86_64-linux-gnu/x86_64:/lib/x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu/tls/haswell/x86_64:/usr/lib/x86_64-linux-gnu/tls/haswell:/usr/lib/x86_64-linux-gnu/tls/x86_64:/usr/lib/x86_64-linux-gnu/tls:/usr/lib/x86_64-linux-gnu/haswell/x86_64:/usr/lib/x86_64-linux-gnu/haswell:/usr/lib/x86_64-linux-gnu/x86_64:/usr/lib/x86_64-linux-gnu:/lib/tls/haswell/x86_64:/lib/tls/haswell:/lib/tls/x86_64:/lib/tls:/lib/haswell/x86_64:/lib/haswell:/lib/x86_64:/lib:/usr/lib/tls/haswell/x86_64:/usr/lib/tls/haswell:/usr/lib/tls/x86_64:/usr/lib/tls:/usr/lib/haswell/x86_64:/usr/lib/haswell:/usr/lib/x86_64:/usr/lib
(system search path)
  8615:   trying 
file=/lib/x86_64-linux-gnu/tls/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/lib/x86_64-linux-gnu/tls/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/lib/x86_64-linux-gnu/tls/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/lib/x86_64-linux-gnu/tls/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/lib/x86_64-linux-gnu/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/lib/x86_64-linux-gnu/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/lib/x86_64-linux-gnu/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/x86_64-linux-gnu/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/tls/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/x86_64-linux-gnu/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/tls/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/tls/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/tls/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/tls/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/lib/RenderSystem_GL.so.1.12.10
  8615:   trying 
file=/usr/lib/tls/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/usr/lib/tls/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying file=/usr/lib/tls/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/usr/lib/tls/RenderSystem_GL.so.1.12.10
  8615:   trying file=/usr/lib/haswell/x86_64/RenderSystem_GL.so.1.12.10
  8615:   trying file=/usr/lib/haswell/RenderSystem_GL.so.1.12.10
  8615:   trying file=/usr/lib/x86_64/RenderSystem_GL.so.1.12.10
  

Bug#1039114: marked as done (python3-zstd uses a vendored copy of libzstd)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 16:07:25 +
with message-id 
and subject line Bug#1039114: fixed in python-zstd 1.5.5.1-1
has caused the Debian Bug report #1039114,
regarding python3-zstd uses a vendored copy of libzstd
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.)


-- 
1039114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039114
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python3-zstd
Severity: normal
X-Debbugs-Cc: t...@security.debian.org

python3-zstd uses a vendored copy of libzstd, and might
therefore have unfixed CVEs:
https://security-tracker.debian.org/tracker/source-package/libzstd

Linking with the system libzstd (as is supported by the upstream
build system) works for me, please consider doing that so that
python3-zstd will benefit from security fixes to src:libzstd.
--- End Message ---
--- Begin Message ---
Source: python-zstd
Source-Version: 1.5.5.1-1
Done: Alexandre Detiste 

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

Debian distribution maintenance software
pp.
Alexandre Detiste  (supplier of updated python-zstd package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 16:26:24 +0100
Source: python-zstd
Architecture: source
Version: 1.5.5.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Alexandre Detiste 
Closes: 1039114
Changes:
 python-zstd (1.5.5.1-1) unstable; urgency=medium
 .
   * Team Upload
   * New upstream version 1.5.5.1
   * use new dh-sequence-python3
   * build with external libzstd (Closes: #1039114)
   * remove extraneous build dep on python3-mock
   * clean cache files
 .
   [ Debian Janitor ]
   * Trim trailing whitespace.
   * Update standards version to 4.6.1, no changes needed.
Checksums-Sha1:
 fc2acab2a44fecbe37210b11edd885b738718d3e 2145 python-zstd_1.5.5.1-1.dsc
 f97f7cbba46eb3d5c20166e3e3d67ddbce0dd36f 1106585 
python-zstd_1.5.5.1.orig.tar.gz
 786987bff8ba731daed2bd76779550be77e1acdb 3024 
python-zstd_1.5.5.1-1.debian.tar.xz
 363f1b61b313b1c3fea9ba1463bbb93ceafda757 7789 
python-zstd_1.5.5.1-1_source.buildinfo
Checksums-Sha256:
 e9c370f16fd6cbd3738b4838e38599f294243e7a1bcfad21af63d19edbb4eefe 2145 
python-zstd_1.5.5.1-1.dsc
 1ef980abf0e1e072b028d2d76ef95b476632651c96225cf30b619c6eef625672 1106585 
python-zstd_1.5.5.1.orig.tar.gz
 911b6234905779663aed49e3868a11bb24e13a6509a0d95b4bc5afa9dbdcfdcf 3024 
python-zstd_1.5.5.1-1.debian.tar.xz
 60d3cf2e0c944e0102755fcc7f419611ba33e8191575171f8a8ac24598d1c257 7789 
python-zstd_1.5.5.1-1_source.buildinfo
Files:
 d3b8314cab7441a94e4f2616b5e0a12d 2145 python optional python-zstd_1.5.5.1-1.dsc
 479b302e5e269ced1efadad51dc3b399 1106585 python optional 
python-zstd_1.5.5.1.orig.tar.gz
 c157dd40738433ff2f073804af0c591c 3024 python optional 
python-zstd_1.5.5.1-1.debian.tar.xz
 8436ca9a9904946cb7bae94f3cc3ab04 7789 python optional 
python-zstd_1.5.5.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmXbXg0RHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBqAmRAAnO2G9M8/FfrjNzLMVZFkgDc0842tPyyU
0zrQaWznBlLL5eMZr7jiOESikeIg0t6ugkuQuPgNWw0Xtl8xAh5RxQecpAQ20L1G
oThRe8+exCSQjBu/8Yktda/e7RIviKOKF2Z1ubSnk1GI6V1b4jX7/gioQPon+USC
GxnzChDVM7lGh+EU79ZQTYUGuDG8RY5BLF6822lbcHZH2C7QDuQmtgTfzb2N8k8z
0qD9sV8kQYtbkiDfw4Y8Xo3nKjy833jasp9ayzRLc1Oudxyv2v5KFDOnhc7BuRLa
pORPFH7m44giLAj/iX5pjpL/oLKvZfATQDvlQ8C6TsVWt2hi6biw22jytZ4oCuUt
X0FzoZBNW0V2nGrs25qSMl/KPI8+NXyhbaUnuhPzF3JVx5qHD2+1CUvrJCaoo8x9
E6bbS4jQ3P/N5sPUlL/b+gmfQIoEXWjAO/u+NukAZgCDTOd8uqoLf6hRIqkEyRYC
NBWeI2NneAcCAvazEmgx5gyniZ8QfWoyCS2QMRtVkWRro66XrjsMFTcKdYSRzcaX
SI6MOhtCsk5DBs5sVNgQFY69RI7CeUfHEF5l34ikBmLlxQlSfJXOuRfyfmCcVALa
/b56Jwwh3ha2CDe9QeT+uBJdgr8Jks27Vf4PdEJRlaBlXFmZEYG78SCdwoZUr2Ph
20r+VDHSwTA=
=VoRQ
-END PGP SIGNATURE-



pgpLckI_nDVVb.pgp
Description: PGP signature
--- End Message ---

Bug#1059579: marked as done (unicode: Package does not use standard dh sequence/dh-sequence-python3)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 15:49:23 +
with message-id 
and subject line Bug#1059579: fixed in unicode 3.1-1
has caused the Debian Bug report #1059579,
regarding unicode: Package does not use standard dh sequence/dh-sequence-python3
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.)


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

Package: src:unicode
Tags: patch

Dear unicode maintainer,

this package currently uses debhelper with an ad-hoc sequence of steps 
in d/rules. This long list of steps can be shortened and greatly 
simplified by using the standard dh sequence and the modern 
dh-sequence-python3, as recommended by Debian policy section 4.9.


You can find a series of patches that update the packaging of `unicode` 
to debhelper 13 and to the standard dh sequence at


https://salsa.debian.org/gioele/unicode/-/compare/upstream-info...dh-13

Regards,

--
Gioele Barabucci
--- End Message ---
--- Begin Message ---
Source: unicode
Source-Version: 3.1-1
Done: Radovan Garabík 

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

Debian distribution maintenance software
pp.
Radovan Garabík  (supplier of updated unicode 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Feb 2024 09:50:19 +0100
Source: unicode
Architecture: source
Version: 3.1-1
Distribution: unstable
Urgency: low
Maintainer: Radovan Garabík 
Changed-By: Radovan Garabík 
Closes: 1033348 1059579
Changes:
 unicode (3.1-1) unstable; urgency=low
 .
   * better error handling sometimes
   * python2 support is officially deprecated
   * catch BrokenPipeError (closes: #1033348)
   * use dh-sequence-python3 (closes: #1059579)
Checksums-Sha1:
 f0b466486ab82adc4b93e1c9a414260b76c99631 1764 unicode_3.1-1.dsc
 273515967f8e97ecb8d86387f31e9a3e4242b8f1 22475 unicode_3.1.orig.tar.gz
 85de202b1a2321dc08d383b42d63b3d790e2e2ba 4336 unicode_3.1-1.debian.tar.xz
 b1ab948be2fecac95f81669c3b2359046cdebd06 6846 unicode_3.1-1_source.buildinfo
Checksums-Sha256:
 11523d1a879bee39416f010559ae80e0f9c60107b9e41fc7bd6ee2d217427c1e 1764 
unicode_3.1-1.dsc
 1c7323545d43955fcbb94c6c20c7268e349298925b650ee3f40bc08bbd7881e6 22475 
unicode_3.1.orig.tar.gz
 1ff1b72c9034c01a6c2c2a9d6bb8b0bbccb4e0d1192d5b9d50bb579d7ae5ee52 4336 
unicode_3.1-1.debian.tar.xz
 e94f77bf55e11db03a5cdadaa1a0cbf4b88d168fca9d30b9f92d47a16b98516d 6846 
unicode_3.1-1_source.buildinfo
Files:
 5e67b955a8ba7d0843aa473c08b374f9 1764 utils optional unicode_3.1-1.dsc
 a154aa6345a36d1658a54e1935d53d13 22475 utils optional unicode_3.1.orig.tar.gz
 ec22431f2b37a1e3104073cd07f9e987 4336 utils optional 
unicode_3.1-1.debian.tar.xz
 60fb313f333830b7a4ea635c00f1b545 6846 utils optional 
unicode_3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwbjRPT3132UMRk7uaFakpkCvP9MFAmXbXSAACgkQaFakpkCv
P9Mb6A/9GZOOuYB2HXWn38fav4zGFpqve795Md7fE87b2QLL6aMpQpp7PrCynOV6
lDhAF28AetBVubEzqFP1ykFqnN3WH3QS+TjE4AdTWXG5xQZRGlsG+6GsAuy7pwsT
wH2eSCZ3mK848318TRht5civo1PoYSPk+995IZeUoeNQ6i6F17VM+9FAScUf7YiC
EaXniyZ1ShiZv4xAsZUqEcEqwy/Ek9MN5bFd2Vz9Ui98cd/sJcnHVtPKIwtEiVFR
0/R6Jp8MKSQhrLo8GmkCfnvGtXM+9cytGn+GZsdb28bq5UXyOvAe88l5xhnCZBg0
Lr9zyVciZFfz5GL4Rnb0bHiVTFFQvNlitWGuu+YR0JrKLU03FYh6gBu5g382xmIr
4C8uowKB4w1ulS+rSjB54fN833jfGuVjShq0PY94rZOqCfUofk0DadA0qjO+TQcZ
am7lwQJv0/ihxU6oy7pwIJcl3TwKed+EfEnY9010Qf9xbqnobZVyCMV3qimjlIfu
QMPJMH8Pds33kYkFgRqHdbkQU2KbnKXm+74tKR/fHNlPaP3QrVpb676qUrHUygYz
wOlUd7gq2WQO79/d4ekOOMuHmF9CUd0V5Gkpfeu+qwbp78WPLQEIsanRC7P3lWcY
VsCVwrgpGmzJV1zBij+nULpQ+lVsWXpQzmvetPDSPO9eH7gnbhU=
=yRWL
-END PGP SIGNATURE-



pgpnYy106rKJm.pgp
Description: PGP signature
--- End Message ---

Bug#1033348: marked as done (Tracebacks triggered too easily, and inconsistently, when chopping short output)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 15:49:23 +
with message-id 
and subject line Bug#1033348: fixed in unicode 3.1-1
has caused the Debian Bug report #1033348,
regarding Tracebacks triggered too easily, and inconsistently, when chopping 
short output
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.)


-- 
1033348: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033348
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: unicode
Version: 2.9-1

Sometimes, even for the same command(!), limiting the output causes a
traceback.

Certainly using head(1), sed(1), etc. should be a legitimate use, and
not cause errors.

Here, the first try works fine.
Trying it again just for fun, causes an error.

But other times the error might be on the first time, not second, or
both, or none.

There should be no error ever.

$ unicode --max 22 -r per|sed q
U+0025 PERCENT SIGN

Too many characters to display, more than 22, use --max 0 (or other value) 
option to change it
$ unicode --max 22 -r per|sed q
U+0025 PERCENT SIGN
Traceback (most recent call last):
  File "/usr/bin/unicode", line 1066, in 
main()
  File "/usr/bin/unicode", line 1063, in main
print_characters(processed_args, options.maxcount, format_string, 
options.query_wikipedia, options.query_wiktionary)
  File "/usr/bin/unicode", line 683, in print_characters
sys.stdout.flush()
BrokenPipeError: [Errno 32] Broken pipe
Exception ignored in: <_io.TextIOWrapper name='' mode='w' 
encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
--- End Message ---
--- Begin Message ---
Source: unicode
Source-Version: 3.1-1
Done: Radovan Garabík 

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

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

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

Debian distribution maintenance software
pp.
Radovan Garabík  (supplier of updated unicode 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Feb 2024 09:50:19 +0100
Source: unicode
Architecture: source
Version: 3.1-1
Distribution: unstable
Urgency: low
Maintainer: Radovan Garabík 
Changed-By: Radovan Garabík 
Closes: 1033348 1059579
Changes:
 unicode (3.1-1) unstable; urgency=low
 .
   * better error handling sometimes
   * python2 support is officially deprecated
   * catch BrokenPipeError (closes: #1033348)
   * use dh-sequence-python3 (closes: #1059579)
Checksums-Sha1:
 f0b466486ab82adc4b93e1c9a414260b76c99631 1764 unicode_3.1-1.dsc
 273515967f8e97ecb8d86387f31e9a3e4242b8f1 22475 unicode_3.1.orig.tar.gz
 85de202b1a2321dc08d383b42d63b3d790e2e2ba 4336 unicode_3.1-1.debian.tar.xz
 b1ab948be2fecac95f81669c3b2359046cdebd06 6846 unicode_3.1-1_source.buildinfo
Checksums-Sha256:
 11523d1a879bee39416f010559ae80e0f9c60107b9e41fc7bd6ee2d217427c1e 1764 
unicode_3.1-1.dsc
 1c7323545d43955fcbb94c6c20c7268e349298925b650ee3f40bc08bbd7881e6 22475 
unicode_3.1.orig.tar.gz
 1ff1b72c9034c01a6c2c2a9d6bb8b0bbccb4e0d1192d5b9d50bb579d7ae5ee52 4336 
unicode_3.1-1.debian.tar.xz
 e94f77bf55e11db03a5cdadaa1a0cbf4b88d168fca9d30b9f92d47a16b98516d 6846 
unicode_3.1-1_source.buildinfo
Files:
 5e67b955a8ba7d0843aa473c08b374f9 1764 utils optional unicode_3.1-1.dsc
 a154aa6345a36d1658a54e1935d53d13 22475 utils optional unicode_3.1.orig.tar.gz
 ec22431f2b37a1e3104073cd07f9e987 4336 utils optional 
unicode_3.1-1.debian.tar.xz
 60fb313f333830b7a4ea635c00f1b545 6846 utils optional 
unicode_3.1-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEwbjRPT3132UMRk7uaFakpkCvP9MFAmXbXSAACgkQaFakpkCv
P9Mb6A/9GZOOuYB2HXWn38fav4zGFpqve795Md7fE87b2QLL6aMpQpp7PrCynOV6
lDhAF28AetBVubEzqFP1ykFqnN3WH3QS+TjE4AdTWXG5xQZRGlsG+6GsAuy7pwsT
wH2eSCZ3mK848318TRht5civo1PoYSPk+995IZeUoeNQ6i6F17VM+9FAScUf7YiC
EaXniyZ1ShiZv4xAsZUqEcEqwy/Ek9MN5bFd2Vz9Ui98cd/sJcnHVtPKIwtEiVFR
0/R6Jp8MKSQhrLo8GmkCfnvGtXM+9cytGn+GZsdb28bq5UXyOvAe88l5xhnCZBg0
Lr9zyVciZFfz5GL4Rnb0bHiVTFFQvNlitWGuu+YR0JrKLU03FYh6gBu5g382xmIr
4C8uowKB4w1ulS+rSjB54fN833jfGuVjShq0PY94rZOqCfUofk0DadA0qjO+TQcZ
am7lwQJv0/ihxU6oy7pwIJcl3TwKed+EfEnY9010Qf9xbqnobZVyCMV3qimjlIfu
QMPJMH8Pds33kYkFgRqHdbkQU2KbnKXm+74tKR/fHNlPaP3QrVpb676qUrHUygYz

Bug#1057016: marked as done (adjtimex: Move files from /lib, /sbin to /usr/lib, /usr/sbin)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 15:19:06 +
with message-id 
and subject line Bug#1057016: fixed in adjtimex 1.29-11.1
has caused the Debian Bug report #1057016,
regarding adjtimex: Move files from /lib, /sbin to /usr/lib, /usr/sbin
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.)


-- 
1057016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: adjtimex
Version: 1.29-11+b1
Severity: normal
Tags: patch
User: helm...@debian.org
Usertags: dep17m2

Dear Maintainer,

your package adjtimex ships files in /lib and /sbin. For the ongoing
UsrMerge effort [1] these directories should become "empty", IOW
packages should not install files there, but instead into the respective
directories in /usr.

It seems to me that adjtimex could move these files now. I'm attaching a
patch, that seems to work for me. However, please read the linked wiki
page and upload to experimental first, to receive info about problems
from "dumat" (also see [1]).

Also note, any backports to bookworm or earlier should undo these
changes.

Thanks for considering,
Chris

1. https://wiki.debian.org/UsrMerge
diff -Nru adjtimex-1.29/debian/adjtimex.init adjtimex-1.29/debian/adjtimex.init
--- adjtimex-1.29/debian/adjtimex.init  2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/adjtimex.init  2023-11-28 00:11:28.0 +0100
@@ -16,7 +16,7 @@
 
 . /lib/lsb/init-functions
 
-test -x /sbin/adjtimex  || exit 0
+test -x /usr/sbin/adjtimex  || exit 0
 
 # default values
 TICK=1
@@ -31,7 +31,7 @@
 case "$1" in
   start|restart|force-reload)
 echo -n "Regulating system clock..."
-/sbin/adjtimex -tick "$TICK" -frequency "$FREQ"
+/usr/sbin/adjtimex -tick "$TICK" -frequency "$FREQ"
 echo "done."
 ;;
   stop|status)
diff -Nru adjtimex-1.29/debian/adjtimex.install 
adjtimex-1.29/debian/adjtimex.install
--- adjtimex-1.29/debian/adjtimex.install   2021-04-27 17:11:49.0 
+0200
+++ adjtimex-1.29/debian/adjtimex.install   2023-11-28 00:11:43.0 
+0100
@@ -1,3 +1,3 @@
-adjtimex sbin
+adjtimex usr/sbin
 debian/adjtimexconfig usr/sbin
 debian/contrib/ntp-drift_to_freq.sh usr/share/doc/adjtimex/contrib
diff -Nru adjtimex-1.29/debian/adjtimex.service 
adjtimex-1.29/debian/adjtimex.service
--- adjtimex-1.29/debian/adjtimex.service   2021-04-27 17:11:49.0 
+0200
+++ adjtimex-1.29/debian/adjtimex.service   2023-11-28 00:11:16.0 
+0100
@@ -10,7 +10,7 @@
 Type=oneshot
 Environment="TICK=1" "FREQ=0"
 EnvironmentFile=-/etc/default/adjtimex
-ExecStart=/sbin/adjtimex -tick ${TICK} -frequency ${FREQ}
+ExecStart=/usr/sbin/adjtimex -tick ${TICK} -frequency ${FREQ}
 
 [Install]
 WantedBy=sysinit.target
diff -Nru adjtimex-1.29/debian/changelog adjtimex-1.29/debian/changelog
--- adjtimex-1.29/debian/changelog  2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/changelog  2023-11-28 00:11:43.0 +0100
@@ -1,3 +1,10 @@
+adjtimex (1.29-11.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Move files from /lib, /sbin to /usr/lib, /usr/sbin. (Closes: #-1)
+
+ -- Chris Hofstaedtler   Tue, 28 Nov 2023 00:11:43 +0100
+
 adjtimex (1.29-11) unstable; urgency=medium
 
   * debian/patches:
diff -Nru adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch 
adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch
--- adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch1970-01-01 
01:00:00.0 +0100
+++ adjtimex-1.29/debian/patches/12-makefile.in-bindir.patch2023-11-28 
00:11:43.0 +0100
@@ -0,0 +1,13 @@
+Index: adjtimex-1.29/Makefile.in
+===
+--- adjtimex-1.29.orig/Makefile.in
 adjtimex-1.29/Makefile.in
+@@ -9,7 +9,7 @@ CFLAGS += @CFLAGS@ -Wall
+ prefix = @prefix@
+ man1dir=@mandir@/man1
+ exec_prefix = @exec_prefix@
+-bindir=/sbin
++bindir= @exec_prefix@/sbin
+ datadir = @datadir@
+ datarootdir = @datarootdir@
+ 
diff -Nru adjtimex-1.29/debian/patches/series 
adjtimex-1.29/debian/patches/series
--- adjtimex-1.29/debian/patches/series 2021-04-27 17:11:49.0 +0200
+++ adjtimex-1.29/debian/patches/series 2023-11-28 00:10:09.0 +0100
@@ -9,3 +9,4 @@
 09-adjtimex.8-Some-fixes-to-the-manual.patch
 10-STA_NANO-confuses-adjtimex-8.patch
 11-Fix-ntpdate-command.patch
+12-makefile.in-bindir.patch
--- End Message ---
--- Begin Message ---
Source: adjtimex
Source-Version: 1.29-11.1
Done: Chris Hofstaedtler 

We believe that the bug you reported is fixed in the latest version of
adjtimex, which is 

Bug#1051223: marked as done (rpm: add RPM_FORCE_DEBIAN= env var as alternative to --force-debian)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 13:50:37 +
with message-id 
and subject line Bug#1051223: fixed in rpm 4.18.2+dfsg-2
has caused the Debian Bug report #1051223,
regarding rpm: add RPM_FORCE_DEBIAN= env var as alternative to --force-debian
to be marked as done.

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

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


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

Command line parameters cannot be passed to dnf, so add support for an
env var to bypass the warning on package install.

In mkosi we use the local dnf package to bootstrap new chroots, which
uses the local rpm package, and shows this warning on every package
being installed, despite the fact that it is perfectly safe to do so
as it is not installing on the host, but in the chroot.

MR on Salsa:

https://salsa.debian.org/pkg-rpm-team/rpm/-/merge_requests/5

-- 
Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
Source: rpm
Source-Version: 4.18.2+dfsg-2
Done: Luca Boccassi 

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 13:29:45 +
Source: rpm
Architecture: source
Version: 4.18.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: RPM packaging team 
Changed-By: Luca Boccassi 
Closes: 1051223
Changes:
 rpm (4.18.2+dfsg-2) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Luca Boccassi ]
   * Add d/salsa-ci.yml
   * rpm: add RPM_FORCE_DEBIAN= env var as alternative to --force-debian
 (Closes: #1051223)
   * Install D-Bus conf file in /usr/ instead of /etc/
 .
   [ Michel Lind ]
   * Enable NDB backend
   * Replace pkg-config with pkgconf
   * Trim trailing whitespace
   * Set field Upstream-Name in debian/copyright
Checksums-Sha1:
 46e4912782ba81ea07ec3d803df6b6454871d290 3014 rpm_4.18.2+dfsg-2.dsc
 bc8bc9adf99246b3b0d116946c4006842cbcba44 47132 rpm_4.18.2+dfsg-2.debian.tar.xz
 251659099ecb23f1e0ba9ec2eef7aaf28ddd44b4 13381 
rpm_4.18.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 b4c0f80816b2a93f959c4ee09425cf9578e0e82d4effdef67e57f61d277cbd19 3014 
rpm_4.18.2+dfsg-2.dsc
 1d8c5ee3a6681c433ed937a3000521d237382aebe6a5a5faa71ac8e08950f55d 47132 
rpm_4.18.2+dfsg-2.debian.tar.xz
 a661d5b50f52ac93961c53f0b1edc1bc1420601204fe2fa9ccb7c1436083f1ea 13381 
rpm_4.18.2+dfsg-2_source.buildinfo
Files:
 a98975bb074296c389666d6b6120b275 3014 admin optional rpm_4.18.2+dfsg-2.dsc
 d3030f3651a8f6be79d791013a98c030 47132 admin optional 
rpm_4.18.2+dfsg-2.debian.tar.xz
 b8ffccff6b1379687a56673a5771aacc 13381 admin optional 
rpm_4.18.2+dfsg-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEErCSqx93EIPGOymuRKGv37813JB4FAmXbQWoRHGJsdWNhQGRl
Ymlhbi5vcmcACgkQKGv37813JB5Bfw//RYVaEFC+UtzBMZDPhQ4pllGfXSho7QBF
us4PbHcn9Ax+zIYcsNt6PXKcW/GYdSWyBgL3tuvMBs1XwejWDG1QIrA+MLYsA9rO
OEaII+tBebml4shDV9lqLeJaTw1wJIob/UNtv9UDAfjX7lyBp8GPyplNRUgyvktJ
dkuIRtP+YQQewhxuhzpeFP9eZsl04Z42GjZi080cf7MEvkd0DgE8HlmLRTBf970P
Fj9ZK36XepfWic3u3vNFeN//WohYX8pUckPTNObtORlVNXI6XGfkUuNY3ET/rvyt
ENrvEDwBq8zXYJpt9RwEa7tYdXRFmYpYGMgRVmU8QUcmVlF4SWtplEz3rYVcKGIP
MlpzTlS7SCSaa3CZFl0dx7pP3FrWwMiI4+qSN0CowaEPEdWnoFzmLsjTPUdGQpjN
sKDHHAmRx8HCpA56XnbdfyGjLjm09UPkjtwnVqd/gV4dOlZdl7sR7KEDPXcCsklP
ThPGawnaqZD6m8kYZll0HBFLq34xbc8LS1ca5Z1RJSh54izPEzN7DWpZ/dhXElqb
9ax/IUQqxBqFrfJU+SwI685Y3fizWBQeGd8s10C1MDs5zp4EtwgzgVD3l/f956Hc
1JKAgqwtWUAkxngeIuBLyNvTMWFj725jyrROB73IOUqig97pLd9RKbAjLwI50dHE
DS643oTLGgw=
=CIcg
-END PGP SIGNATURE-



pgpkcNavrQ6Ib.pgp
Description: PGP signature
--- End Message ---

Bug#990343: marked as done (backintime 1.1.24 - unhandled exception)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 13:49:51 +
with message-id 
and subject line Bug#990343: fixed in backintime 1.4.3-1
has caused the Debian Bug report #990343,
regarding backintime 1.1.24 - unhandled exception
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.)


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

I have recently received a notification in my system mail related to
an unhandled exception in a backintime Python script.

Here is the transcript:

-

Unhandled exception in thread started by 
Traceback (most recent call last):
File "/usr/share/backintime/common/tools.py", line 1458, in 
__log_keyring_warning
TypeError: 'NoneType' object is not callable

-

This is the first time I have seen (or noticed) such a message.
It has not happened again since.

The notification was sent by the cron daemon on date Mon, 21 Jun
2021 11:00:02 -0300.

The last backintime log entry was for a snapshot taken at Mon Jun 21
07:15:01 2021 local time and does not show any errors.

The crontab script is a system entry generated by the GUI and the 
python script is part of the application's installation.

[code]
#Back In Time system entry, this will be edited by the gui:
60 */15 * * * * /usr/bin/nice -n 19 /usr/bin/ionice -c2 -n7 
/usr/bin/backintime backup-job >/dev/null
[/code]

Python installed version is 2.7.16 (default, Oct 10 2019, 22:02:15).

I have reported this issue to 
https://github.com/bit-team/backintime/issues:

[url]https://github.com/bit-team/backintime/issues/1169[/url]

Later on I found that it had *also* been reported back in 10/2017:

[url]https://github.com/bit-team/backintime/issues/820[/url]

The OP's report is virtually identical to the one I filed and 
included messages from --debug:

[code]
Unhandled exception in thread started by 
Traceback (most recent call last):
File "/usr/share/backintime/common/tools.py", line 1463, in 
__log_keyring_warning
File "", line 2237, in _find_and_load
File "", line , in _find_and_load_unlocked
File "", line 2150, in _find_spec
TypeError: 'NoneType' object is not callable
[/code]

The OP's report did not have any subsequent follow-up from the 
maintainers of the backintime package.

Thanks in advance,

sawbona
--- End Message ---
--- Begin Message ---
Source: backintime
Source-Version: 1.4.3-1
Done: Fabio Fantoni 

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

Debian distribution maintenance software
pp.
Fabio Fantoni  (supplier of updated backintime package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 13:30:41 +
Source: backintime
Architecture: source
Version: 1.4.3-1
Distribution: unstable
Urgency: medium
Maintainer: Jonathan Wiltshire 
Changed-By: Fabio Fantoni 
Closes: 990343
Changes:
 backintime (1.4.3-1) unstable; urgency=medium
 .
   * New upstream version 1.4.3 (Closes: #990343)
   * d/patches/dbus-in-usr-share.patch: remove (applied upstream)
   * Update d/copyright
Checksums-Sha1:
 992300290b6d6f9d979b9d3091017b0135d21aac 1451 backintime_1.4.3-1.dsc
 d7228823ea7cf579e21c67e8c91a906ad0e9b536 1924227 backintime_1.4.3.orig.tar.gz
 641535ecc0b9bda0497e122744247ee136fbd05f 7468 backintime_1.4.3-1.debian.tar.xz
 0e68496058f6b5d49afabfd26c363c956c24b171 6001 
backintime_1.4.3-1_source.buildinfo
Checksums-Sha256:
 ca806756bf3def186b1c5e81c38a59d02de79c9479ecbce90208557564172e33 1451 
backintime_1.4.3-1.dsc
 89a1d9f1b766025d0219b7978e77ee91a5e25ef99ade164c1d8b5a9a3d273e65 1924227 
backintime_1.4.3.orig.tar.gz
 334178d52531517d4e35305482cb7d4dbd291b1fb233a190c69e7f9b5e2d6a0c 7468 
backintime_1.4.3-1.debian.tar.xz
 ada1ae006416ae57d8b9584e4c8af0a09d5b0cd717b09a50e71157791f9615b4 6001 
backintime_1.4.3-1_source.buildinfo
Files:
 0973e2651694b350b702ac44e479f712 1451 utils optional backintime_1.4.3-1.dsc
 8c68f62b919e29712405e641b04fed22 1924227 utils optional 
backintime_1.4.3.orig.tar.gz
 

Bug#1064062: marked as done (iwd: CVE-2023-52161)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 13:47:19 +
with message-id 
and subject line Bug#1064062: fixed in iwd 2.3-1+deb12u1
has caused the Debian Bug report #1064062,
regarding iwd: CVE-2023-52161
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.)


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

Hi,

The following vulnerability was published for iwd.

CVE-2023-52161[0]:
https://www.top10vpn.com/research/wifi-vulnerabilities/

While this mentions a patch for wpasupplication, it's not obvious
if this was reported/fixed in iwd.


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: iwd
Source-Version: 2.3-1+deb12u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated iwd 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: Wed, 21 Feb 2024 15:39:34 +0100
Source: iwd
Architecture: source
Version: 2.3-1+deb12u1
Distribution: bookworm-security
Urgency: high
Maintainer: Jonas Smedegaard 
Changed-By: Salvatore Bonaccorso 
Closes: 1064062
Changes:
 iwd (2.3-1+deb12u1) bookworm-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * ap: only accept ptk 4/4 after receiving ptk 2/4 (CVE-2023-52161)
 (Closes: #1064062)
Checksums-Sha1: 
 2842c2d12c081f5dfe1409ee8ea3bab51d446aca 2129 iwd_2.3-1+deb12u1.dsc
 d55f950d856fef7687459c5f8bbc05b1d61f7233 1061732 iwd_2.3.orig.tar.xz
 d6b5941e56d1a20763651f4faa19abf072e079d8 17328 iwd_2.3-1+deb12u1.debian.tar.xz
Checksums-Sha256: 
 ae05a60f4732232d6dc7cb5bd354e8423c675febf97f853402acc86e96702615 2129 
iwd_2.3-1+deb12u1.dsc
 b0506d797a8bfb88f3c3eeea5e49dcf4ee8e6cef118f57c118e587eeb377ac64 1061732 
iwd_2.3.orig.tar.xz
 113b848c7d7e33f4a975d89c02cac2834f87b80ae76a4a1000a0f11f2f4d2066 17328 
iwd_2.3-1+deb12u1.debian.tar.xz
Files: 
 54c10c5707cce240e9428f00a6d9a883 2129 net optional iwd_2.3-1+deb12u1.dsc
 8faf7a552ba4cb4747567409e14887ac 1061732 net optional iwd_2.3.orig.tar.xz
 c08cb9e201f6a8e3c2ce82cbb6d3c0c3 17328 net optional 
iwd_2.3-1+deb12u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKlBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmXWC8VfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89E1loP+M/opDE8LqrmWOcXBs/ZaH0WZ0w974MR
leha1KdLYyCJoLItajAluKiA0BHFSRjKQY5aG+WJkSJHy7/vD1y6QaElSYFrvoPT
ljbHYUq5cNqYxUSOz+McfIWBqWT9msg8JLHLTV4+b07bU+9mmdSaJQAg//DP/A1c
iBmXF6F3RWsbKdxC8iVI7FGUpM77tQbBkn/SrcMfKOL7bB7Dmu0RMam2gJKE7kBR
6sQPaREIZz6nyITl2F+xkzDxzae+eX9WzegYRPZh+uyYTbSTkG45mYIApY3gbpAn
TH+VimeJWcdzYhbtlqT2ldXABN7joYDV8po4+WQDaSu+r5yuHoT5+5ylTgl2tATa
tILFZ5AnDKg1woABERx1pBQvx59KADif0mH0bexmWG4keMo6LNaKAHmKKtKttbDi
gxqyFQyLOkRqM7v9AUxvxem8w4e3UNUK8edzKnV8UF2HVv8vS4nLSOOaDX39VieC
xrEStDXb7kBlZXsOMGh5KW9L0FjGA3p8hLdku9JRwBUplc+YwrsFO059e2Vnbb5K
7bNDpwd2N+74cnbwIHVCOcRh4APkMiXzgLPXEPRu80DXJAETL4cH6ycnCZ4MoV1x
pW4GromMhe0p/ZdyOWaNHhArEMzYg/cXQxWrBwJTfB/SAhM3uPnbQ5Ls27yj2hD9
gGoTZmR+qYQ=
=locU
-END PGP SIGNATURE-



pgpT73thky7jf.pgp
Description: PGP signature
--- End Message ---

Bug#1064062: marked as done (iwd: CVE-2023-52161)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 13:48:02 +
with message-id 
and subject line Bug#1064062: fixed in iwd 1.14-3+deb11u1
has caused the Debian Bug report #1064062,
regarding iwd: CVE-2023-52161
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.)


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

Hi,

The following vulnerability was published for iwd.

CVE-2023-52161[0]:
https://www.top10vpn.com/research/wifi-vulnerabilities/

While this mentions a patch for wpasupplication, it's not obvious
if this was reported/fixed in iwd.


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

For further information see:

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

Please adjust the affected versions in the BTS as needed.
--- End Message ---
--- Begin Message ---
Source: iwd
Source-Version: 1.14-3+deb11u1
Done: Salvatore Bonaccorso 

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated iwd 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: Wed, 21 Feb 2024 15:43:48 +0100
Source: iwd
Architecture: source
Version: 1.14-3+deb11u1
Distribution: bullseye-security
Urgency: high
Maintainer: Jonas Smedegaard 
Changed-By: Salvatore Bonaccorso 
Closes: 1064062
Changes:
 iwd (1.14-3+deb11u1) bullseye-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * ap: only accept ptk 4/4 after receiving ptk 2/4 (CVE-2023-52161)
 (Closes: #1064062)
Checksums-Sha1: 
 d1f7a2458fa779178d118f2789496e1feb680645 2072 iwd_1.14-3+deb11u1.dsc
 c3d66ab927e8a24f4350a3d8facc87f785e70bfd 933764 iwd_1.14.orig.tar.xz
 94b92f4a7fe5041c174c7a645262917755d21eff 13796 iwd_1.14-3+deb11u1.debian.tar.xz
Checksums-Sha256: 
 2818a0d410945aa7929a85aff6aa372ec003a400445edff7c405f22817a438d8 2072 
iwd_1.14-3+deb11u1.dsc
 21be6ad59ba666ba1e50e01889d647472b9b2f96f4941123db036fd33c257f0b 933764 
iwd_1.14.orig.tar.xz
 6c1e2116dba26e833f48cea677859f36450c555794cfa038314e462faa512b05 13796 
iwd_1.14-3+deb11u1.debian.tar.xz
Files: 
 6b8aba7f910900371cda7c19bc09f99b 2072 net optional iwd_1.14-3+deb11u1.dsc
 2b16265e9f1315a377418c22479144cd 933764 net optional iwd_1.14.orig.tar.xz
 7d81801ae3f3a52013919bc13bb48b8b 13796 net optional 
iwd_1.14-3+deb11u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmXWDJtfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EFrIP/0FSUAhpADLjruZRweDsbsEf1PsjcISN
8ExXY1l8iDzPDZZP/txTgFqA++cmecLe+ku4DkZDFqyhVtr49MyHM5BPldRpJCbL
Xn1eUh9dMH7ULVykLhW1MEBZRwE83VjizIBqOfDkQ9cHIWH5nMGzmq1mnMfIlVgd
AIGtdimcxKkItwZk/l4CUclrFMW/KWoXOP5UsrNQ/aCiaIRfQm7fYSzyG2ufLEx1
z3IVg2ypVy4kJ3L3Y33VMfHZc/gdICFZMXhGguXM5EURA14lhaW8FyRVqBy45Xzl
HauqbZ5/vmuy/2MB1XEwenRyG7HG+28VF/5nm+8fG9AI98NVdIZgoQE7Moq5xbND
+OUeZRYOCvvuMrUriYcaGCrWQNeFj2mRg+WxPps0h8U1a9Hlg+hXC5wBJ0MdKwnq
MTbgVMNO+mLtTcoByZoJ2XCStrTM5WlDNW/7+q+51cly/9DRXNcgX2m4KViSmLCv
vKJTkkPeblvIaok5INSu6kxArjvIx2+RpRSE8+Er4Rw6c/9xgMrHFp+6jrGZ3vo0
Ppx3Ovjv+g3slMIHdVtpX1LglYuJg8oxgSbUAMZ0B5W4TLsfLAGj+bpxQHlNjBzn
WHjWorqIHfWijbzDvFl+0CjIdF/i/CtmZ3kFqfQrBOr+G8is/uqxgDFV+6GJZGom
PFD60F1XtxTj
=0JQX
-END PGP SIGNATURE-



pgpKwelyz5iqw.pgp
Description: PGP signature
--- End Message ---

Processed: RFS: bluraybackup/1.0-1 [ITP] -- Backup BDMV from the command line

[Debian Bug Tracking System]

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

> close 1055213
Bug #1055213 [sponsorship-requests] RFS: bluraybackup/1.0-1 [ITP] -- Backup 
BDMV from the command line
Marked Bug as done
> stop
Stopping processing here.

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

Bug#1049733: marked as done (emboss-explorer: Fails to build binary packages again after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 11:49:13 +
with message-id 
and subject line Bug#1049733: fixed in emboss-explorer 2.2.0-12
has caused the Debian Bug report #1049733,
regarding emboss-explorer: Fails to build binary packages again 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.)


-- 
1049733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049733
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emboss-explorer
Version: 2.2.0-11
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).

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/DoubleBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -b
> -
> 
> dpkg-buildpackage: info: source package emboss-explorer
> dpkg-buildpackage: info: source version 2.2.0-11
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean --with apache2
>dh_auto_clean
>   make -j8 distclean
> make[1]: Entering directory '/<>'
> rm -f \
>   blib/script/acdcheck blib/script/mkstatic 
> "/usr/bin/perl" "-MExtUtils::Manifest=fullcheck" -e fullcheck
> rm -f \
>   GUI.bso GUI.def \
>   GUI.exp GUI.x \
>blib/arch/auto/EMBOSS/GUI/extralibs.all \
>   blib/arch/auto/EMBOSS/GUI/extralibs.ld Makefile.aperl \
>   *.a *.o \
>   *perl.core MYMETA.json \
>   MYMETA.yml blibdirs.ts \
>   core core.*perl.*.? \
>   core.[0-9] core.[0-9][0-9] \
>   core.[0-9][0-9][0-9] core.[0-9][0-9][0-9][0-9] \
>   core.[0-9][0-9][0-9][0-9][0-9] libGUI.def \
>   mon.out perl \
>   perl perl.exe \
>   perlmain.c pm_to_blib \
>   pm_to_blib.ts so_locations \
>   tmon.out 
> rm -rf \
>   blib 
> mv Makefile Makefile.old > /dev/null 2>&1
> rm -f \
>   Makefile Makefile.old 
> rm -rf \
>   EMBOSS-GUI-2.1 
> /<>/debian/emboss-explorer/usr/share/emboss-explorer/html/style 
> is encountered a second time at /usr/share/perl/5.36/File/Find.pm line 78.
> make[1]: *** [Makefile:611: distcheck] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_clean: error: make -j8 distclean returned exit code 2
> make: *** [debian/rules:6: clean] Error 25
> dpkg-buildpackage: error: debian/rules clean subprocess returned exit status 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -b' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/16/emboss-explorer_2.2.0-11_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: emboss-explorer
Source-Version: 2.2.0-12
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated emboss-explorer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 12:11:22 +0100
Source: emboss-explorer

Bug#1044407: marked as done (emboss-explorer: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 11:49:13 +
with message-id 
and subject line Bug#1044407: fixed in emboss-explorer 2.2.0-12
has caused the Debian Bug report #1044407,
regarding emboss-explorer: 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.)


-- 
1044407: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1044407
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: emboss-explorer
Version: 2.2.0-11
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 emboss-explorer
> dpkg-buildpackage: info: source version 2.2.0-11
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --with apache2
>dh_auto_clean
>   make -j8 distclean
> make[1]: Entering directory '/<>'
> rm -f \
>   blib/script/acdcheck blib/script/mkstatic 
> "/usr/bin/perl" "-MExtUtils::Manifest=fullcheck" -e fullcheck
> rm -f \
>   GUI.bso GUI.def \
>   GUI.exp GUI.x \
>blib/arch/auto/EMBOSS/GUI/extralibs.all \
>   blib/arch/auto/EMBOSS/GUI/extralibs.ld Makefile.aperl \
>   *.a *.o \
>   *perl.core MYMETA.json \
>   MYMETA.yml blibdirs.ts \
>   core core.*perl.*.? \
>   core.[0-9] core.[0-9][0-9] \
>   core.[0-9][0-9][0-9] core.[0-9][0-9][0-9][0-9] \
>   core.[0-9][0-9][0-9][0-9][0-9] libGUI.def \
>   mon.out perl \
>   perl perl.exe \
>   perlmain.c pm_to_blib \
>   pm_to_blib.ts so_locations \
>   tmon.out 
> rm -rf \
>   blib 
> mv Makefile Makefile.old > /dev/null 2>&1
> rm -f \
>   Makefile Makefile.old 
> rm -rf \
>   EMBOSS-GUI-2.1 
> /<>/debian/emboss-explorer/usr/share/emboss-explorer/html/style 
> is encountered a second time at /usr/share/perl/5.36/File/Find.pm line 78.
> make[1]: *** [Makefile:611: distcheck] Error 2
> make[1]: Leaving directory '/<>'
> dh_auto_clean: error: make -j8 distclean returned exit code 2
> make: *** [debian/rules:6: clean] Error 25
> dpkg-buildpackage: error: debian/rules clean 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/emboss-explorer_2.2.0-11_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: emboss-explorer
Source-Version: 2.2.0-12
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated emboss-explorer 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 12:11:22 +0100
Source: emboss-explorer
Architecture: source
Version: 2.2.0-12
Distribution: unstable
Urgency: medium

Bug#1056117: marked as done (meson: generates non-determinstic .pkgconfig files)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 12:28:07 +0100
with message-id 

and subject line meson: generates non-determinstic .pkgconfig files
has caused the Debian Bug report #1056117,
regarding meson: generates non-determinstic .pkgconfig files
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.)


-- 
1056117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056117
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: meson
Version: 1.2.3-1
Severity: wishlist
Tags: patch
User: reproducible-bui...@lists.alioth.debian.org
Usertags: randomness toolchain
X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org

Hi,

Whilst working on the Reproducible Builds effort, we noticed that
meson was generates .pkgconfig files that are not reproducible.

For example, here is neatvnc's pkgconfig file:

   Name: neatvnc
   Description: A Neat VNC server library
   Version: 0.7.0
  -Requires.private: pixman-1, aml < 0.4.0, aml >= 0.3.0, zlib, libdrm, 
libturbojpeg, gnutls, nettle, hogweed, gmp, gbm, libavcodec, libavfilter, 
libavutil
  +Requires.private: pixman-1, aml >= 0.3.0, aml < 0.4.0, zlib, libdrm, 
libturbojpeg, gnutls, nettle, hogweed, gmp, gbm, libavcodec, libavfilter, 
libavutil
   Libs: -L${libdir} -lneatvnc
   Libs.private: -lm
   Cflags: -I${includedir}

A patch is attached that sorts the output, resulting in:

   Requires.private: aml < 0.4.0, aml >= 0.3.0, gbm, gmp, gnutls, hogweed, 
libavcodec, libavfilter, libavutil, libdrm, libturbojpeg, nettle, pixman-1, zlib


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
diff --git a/mesonbuild/modules/pkgconfig.py b/mesonbuild/modules/pkgconfig.py
index 63025a5..2a0e577 100644
--- a/mesonbuild/modules/pkgconfig.py
+++ b/mesonbuild/modules/pkgconfig.py
@@ -310,7 +310,7 @@ class DependenciesHelper:
 result += [name + ' ' + self.format_vreq(vreq) for vreq in 
vreqs]
 else:
 result += [name]
-return ', '.join(result)
+return ', '.join(sorted(result))
 
 def remove_dups(self) -> None:
 # Set of ids that have already been handled and should not be added 
any more
--- End Message ---
--- Begin Message ---
Source-Version: 1.3.1-1

Fixed upstream in 1.3.1.--- End Message ---

Processed: RFS: winff/1.6.3+dfsg-1 -- graphical video and audio batch converter using ffmpeg or avconv

[Debian Bug Tracking System]

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

> close 1064287
Bug #1064287 [sponsorship-requests] RFS: winff/1.6.3+dfsg-1 -- graphical video 
and audio batch converter using ffmpeg or avconv
Marked Bug as done
> stop
Stopping processing here.

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

Bug#1049738: marked as done (biosyntax: Fails to build binary packages again after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 10:34:29 +
with message-id 
and subject line Bug#1049738: fixed in biosyntax 1.0.0b-6
has caused the Debian Bug report #1049738,
regarding biosyntax: Fails to build binary packages again 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.)


-- 
1049738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: biosyntax
Version: 1.0.0b-4
Severity: minor
Tags: trixie sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-binary-20230816 ftbfs-binary-after-build
User: debian...@lists.debian.org
Usertags: qa-doublebuild

Hi,

This package fails to do build a binary-only build (not source) after a
successful build (dpkg-buildpackage ; dpkg-buildpackage -b).

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/DoubleBuild

Relevant part of the build log:
> cd /<> && runuser -u user42 -- dpkg-buildpackage --sanitize-env 
> -us -uc -rfakeroot -b
> --
> 
> dpkg-buildpackage: info: source package biosyntax
> dpkg-buildpackage: info: source version 1.0.0b-4
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Andreas Tille 
>  dpkg-source --before-build .
> dpkg-buildpackage: info: host architecture amd64
>  debian/rules clean
> dh clean
>dh_auto_clean
>dh_clean
>  debian/rules binary
> dh binary
>dh_update_autotools_config
>dh_autoreconf
>dh_auto_configure
>debian/rules override_dh_auto_build
> make[1]: Entering directory '/<>'
> # Upstream provides a makefile only to generate the released tarball
> mv less/src-hilite-lesspipe-bio-LINUX.sh less/src-hilite-lesspipe-bio.sh
> mv: cannot stat 'less/src-hilite-lesspipe-bio-LINUX.sh': No such file or 
> directory
> make[1]: *** [debian/rules:8: override_dh_auto_build] Error 1
> make[1]: Leaving directory '/<>'
> make: *** [debian/rules:4: binary] Error 2
> dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
> 2
> 
> E: Command 'cd /<> && runuser -u user42 -- dpkg-buildpackage 
> --sanitize-env -us -uc -rfakeroot -b' failed to run.


The full build log is available from:
http://qa-logs.debian.net/2023/08/16/biosyntax_1.0.0b-4_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: biosyntax
Source-Version: 1.0.0b-6
Done: Étienne Mollier 

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

Debian distribution maintenance software
pp.
Étienne Mollier  (supplier of updated biosyntax package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Sun, 25 Feb 2024 11:20:09 +0100
Source: biosyntax
Architecture: source
Version: 1.0.0b-6
Distribution: unstable
Urgency: medium
Maintainer: Debian Med Packaging Team 

Changed-By: Étienne Mollier 
Closes: 1049738
Changes:
 biosyntax (1.0.0b-6) unstable; urgency=medium
 .
   * Team upload.
   * d/rules: preserve less/src-hilite-lesspipe-bio-LINUX.sh. (Closes: #1049738)
   * d/copyright: document appstream's CC0 license.
Checksums-Sha1:
 1434b0aa8e624ac5409e1b660fb15be2b28fd638 2382 biosyntax_1.0.0b-6.dsc
 35f4854e9c5c5bf86e7f95e986511466a595c2a5 7884 biosyntax_1.0.0b-6.debian.tar.xz
Checksums-Sha256:
 9a57b435ed04902881b46d105ff1385ccadda8302177847e3403f58da7a6b269 2382 
biosyntax_1.0.0b-6.dsc
 

Bug#1061586: marked as done (~/.winff/*.sh are world-writable)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 10:04:49 +
with message-id 
and subject line Bug#1061586: fixed in winff 1.6.3+dfsg-1
has caused the Debian Bug report #1061586,
regarding ~/.winff/*.sh are world-writable
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.)


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

Package: winff
Version: 1.5.5-9
Tags: security patch

As it was noted in , WinFF 
changes permissions of ~/.winff/*.sh files to 0777, which is 
world-writable!


Assuming default permissions of the home directory and the .winff 
subdir, this can be exploited by local users to execute arbitrary code 
with the context of the user running WinFF.


I've attached a proof-of-concept exploit. (It's not 100% reliable.)

I've also attached an untested patch.

--
Jakub Wilk
#!/bin/sh
while true
do
for file in /home/*/.winff/*.sh
do
echo 'cowsay pwned >&2; sleep inf' | tee "$file" > /dev/null
done
done
diff --git a/winff/unit1.pas b/winff/unit1.pas
index 71689a6..6a77b02 100644
--- a/winff/unit1.pas
+++ b/winff/unit1.pas
@@ -1354,7 +1354,7 @@ begin
 
  script.SaveToFile(presetspath+batfile);
  {$ifdef unix}
- fpchmod(presetspath + batfile,&777);
+ fpchmod(presetspath + batfile,&700);
  {$endif}
 
 scriptprocess.ShowWindow := swoNone;
@@ -2494,7 +2494,7 @@ begin // get setup
  begin
 
{$ifdef unix}
-   fpchmod(presetspath + batfile,&777);
+   fpchmod(presetspath + batfile,&700);
{$endif}
 
 // do it
--- End Message ---
--- Begin Message ---
Source: winff
Source-Version: 1.6.3+dfsg-1
Done: Peter Blackman 

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

Debian distribution maintenance software
pp.
Peter Blackman  (supplier of updated winff 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, 19 Feb 2024 13:00:00 +
Source: winff
Built-For-Profiles: noudeb
Architecture: source
Version: 1.6.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Peter Blackman 
Closes: 1053373 1061586
Changes:
 winff (1.6.3+dfsg-1) unstable; urgency=medium
 .
   * New Upstream release (Closes: #1053373) (Closes: #1061586)
   * Drop patch adopted upstream
   * Update copyright date
Checksums-Sha1:
 d55265c3de46b30ee868b3cf9ca6ef3583488913 2242 winff_1.6.3+dfsg-1.dsc
 96844a0e3cdc6ec1789d7455974eb9dbb00fb826 2687816 winff_1.6.3+dfsg.orig.tar.xz
 649c90126b561265b6d5ec59332ad3a4e6bb7bd9 83080 winff_1.6.3+dfsg-1.debian.tar.xz
 136c7f2e07fd1aacf3e9d9f7dd7f482e4efce5f9 14274 
winff_1.6.3+dfsg-1_source.buildinfo
Checksums-Sha256:
 3d1e1b6bcdedf1c4ab8a480714de0f7ab92cf376121151db04b71ca8876465b0 2242 
winff_1.6.3+dfsg-1.dsc
 786e410b8ef24138700d64d250233738bf2a0b8809a0f20c2efe0f628dd43ae1 2687816 
winff_1.6.3+dfsg.orig.tar.xz
 3bac0a7627d979b684375e974a9468440f324ff47868e1bdec149c951dfd6e67 83080 
winff_1.6.3+dfsg-1.debian.tar.xz
 3e60ca7441351a1910ba99f681b68d0287af217446b9a421399e35a8200a4abf 14274 
winff_1.6.3+dfsg-1_source.buildinfo
Files:
 050235e0ca913e7c18b3716d4286ef09 2242 video optional winff_1.6.3+dfsg-1.dsc
 6867fb322626d5df2067d8bc5ae8fa19 2687816 video optional 
winff_1.6.3+dfsg.orig.tar.xz
 4b9f0f15fa7f4c0ad9c8506eeb1ea0ff 83080 video optional 
winff_1.6.3+dfsg-1.debian.tar.xz
 a807a6885643cf0d3bcbb612069394e2 14274 video optional 
winff_1.6.3+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmXbDpEACgkQ808JdE6f
XdmpCQ/+Od00cEalnyCxN+E5OpUn4EB0gnxQcUQsHMpJVhphMds4EEzxK/vecC48
REOVolyD+LwbEkWniRDeW2E0LCDdYbi7SuUX79Vr3aaequHt0O6l71Ii4KMglgyV
rNRTOwckMQ2esMFOhsiWcmfPPyBKJoJoWLr9PDkskX+iEYVmyqJ91tdL5cflHc+Q
kaIY1TEkPZ4xWU1UCEisNni6booOMxha7HGFfbtJh6TEchLEhW/gztHxlNvJNJeR
HYLcbvq2calb54IV91Ix0bx/VVZS0kavk3zPD46En77sZNgGU+TavKgce+tGml4K

Bug#1053373: marked as done (winff: shell injection)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 10:04:49 +
with message-id 
and subject line Bug#1053373: fixed in winff 1.6.3+dfsg-1
has caused the Debian Bug report #1053373,
regarding winff: shell injection
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.)


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

Package: winff
Version: 1.5.5-9
Tags: security

WinFF doesn't correctly escape filenames that it passes to shell. If the 
user is tricked to convert files with malicious names, this could result 
in execution of arbitrary code.


To reproduce, try converting the file created by this command:

  touch '$(cowsay pwned >&2; sleep inf).mp3'

--
Jakub Wilk
--- End Message ---
--- Begin Message ---
Source: winff
Source-Version: 1.6.3+dfsg-1
Done: Peter Blackman 

We believe that the bug you reported is fixed in the latest version of
winff, 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.
Peter Blackman  (supplier of updated winff 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, 19 Feb 2024 13:00:00 +
Source: winff
Built-For-Profiles: noudeb
Architecture: source
Version: 1.6.3+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Pascal Packaging Team 
Changed-By: Peter Blackman 
Closes: 1053373 1061586
Changes:
 winff (1.6.3+dfsg-1) unstable; urgency=medium
 .
   * New Upstream release (Closes: #1053373) (Closes: #1061586)
   * Drop patch adopted upstream
   * Update copyright date
Checksums-Sha1:
 d55265c3de46b30ee868b3cf9ca6ef3583488913 2242 winff_1.6.3+dfsg-1.dsc
 96844a0e3cdc6ec1789d7455974eb9dbb00fb826 2687816 winff_1.6.3+dfsg.orig.tar.xz
 649c90126b561265b6d5ec59332ad3a4e6bb7bd9 83080 winff_1.6.3+dfsg-1.debian.tar.xz
 136c7f2e07fd1aacf3e9d9f7dd7f482e4efce5f9 14274 
winff_1.6.3+dfsg-1_source.buildinfo
Checksums-Sha256:
 3d1e1b6bcdedf1c4ab8a480714de0f7ab92cf376121151db04b71ca8876465b0 2242 
winff_1.6.3+dfsg-1.dsc
 786e410b8ef24138700d64d250233738bf2a0b8809a0f20c2efe0f628dd43ae1 2687816 
winff_1.6.3+dfsg.orig.tar.xz
 3bac0a7627d979b684375e974a9468440f324ff47868e1bdec149c951dfd6e67 83080 
winff_1.6.3+dfsg-1.debian.tar.xz
 3e60ca7441351a1910ba99f681b68d0287af217446b9a421399e35a8200a4abf 14274 
winff_1.6.3+dfsg-1_source.buildinfo
Files:
 050235e0ca913e7c18b3716d4286ef09 2242 video optional winff_1.6.3+dfsg-1.dsc
 6867fb322626d5df2067d8bc5ae8fa19 2687816 video optional 
winff_1.6.3+dfsg.orig.tar.xz
 4b9f0f15fa7f4c0ad9c8506eeb1ea0ff 83080 video optional 
winff_1.6.3+dfsg-1.debian.tar.xz
 a807a6885643cf0d3bcbb612069394e2 14274 video optional 
winff_1.6.3+dfsg-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmXbDpEACgkQ808JdE6f
XdmpCQ/+Od00cEalnyCxN+E5OpUn4EB0gnxQcUQsHMpJVhphMds4EEzxK/vecC48
REOVolyD+LwbEkWniRDeW2E0LCDdYbi7SuUX79Vr3aaequHt0O6l71Ii4KMglgyV
rNRTOwckMQ2esMFOhsiWcmfPPyBKJoJoWLr9PDkskX+iEYVmyqJ91tdL5cflHc+Q
kaIY1TEkPZ4xWU1UCEisNni6booOMxha7HGFfbtJh6TEchLEhW/gztHxlNvJNJeR
HYLcbvq2calb54IV91Ix0bx/VVZS0kavk3zPD46En77sZNgGU+TavKgce+tGml4K
6tp8T7NX18/sPgJ73iRn9Qw0wiH/uiUo1XfCtPBbGLXsO57AmoEayDYqyd8FYcyG
/+zmytcbqJZKNSXw+0exzc0B0OS5xibMNEwLdWCQoJqBMJtYwUOT1Jr2qaFNEGfT
V1NCmO1iqDoZWXeLPx8Hp0SwTA5jSNys7k106urgJz0sz9gZVTIF8LYSRY1W9qXs
QxiZ/z6PUWhByiejMdy2NAd/mHK2tyV1u7pWnT6wm7xRoipxvOJhtcw/jWYNJpSE
pUrtOqkBP7vHGvYQE/1hMiQkEjKOwqU9ikxIXnMu8cy4qWo9NF5eR7K406GaAvg/
Qp6H2KyMAxNbqIH1bUexmEcC9/zN+O2NK1O5v3/z/y9E7SRQgqc=
=iDJk
-END PGP SIGNATURE-



pgpE9bz7SZjHx.pgp
Description: PGP signature
--- End Message ---

Bug#1047001: marked as done (timew: Fails to build source after successful build)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 09:49:12 +
with message-id 
and subject line Bug#1047001: fixed in timew 1.7.1+ds.1-2
has caused the Debian Bug report #1047001,
regarding timew: 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.)


-- 
1047001: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1047001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: timew
Version: 1.5.0+ds.1-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 timew
> dpkg-buildpackage: info: source version 1.5.0+ds.1-1
> dpkg-buildpackage: info: source distribution unstable
> dpkg-buildpackage: info: source changed by Sebastien Badia 
>  dpkg-source --before-build .
>  debian/rules clean
> dh clean --with bash-completion
>dh_auto_clean
>dh_clean
>  dpkg-source -b .
> dpkg-source: info: using source format '3.0 (quilt)'
> dpkg-source: info: building timew using existing 
> ./timew_1.5.0+ds.1.orig.tar.xz
> dpkg-source: info: using patch list from debian/patches/series
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-annotate.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-cancel.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-chart.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-config.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-continue.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-delete.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-diagnostics.1 has 
> no final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-export.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-extensions.1 has 
> no final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-fill.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-gaps.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-get.1 has no final 
> newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-help.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-join.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-lengthen.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-modify.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-move.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-report.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-resize.1 has no 
> final newline (either original or modified version)
> dpkg-source: warning: file timew-1.5.0+ds.1/doc/man1/timew-shorten.1 has no 
> final newline (either original 

Bug#1061850: marked as done (timew fails its autopkg tests with Python 3.12)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 09:49:12 +
with message-id 
and subject line Bug#1061850: fixed in timew 1.7.1+ds.1-2
has caused the Debian Bug report #1061850,
regarding timew fails its autopkg tests with Python 3.12
to be marked as done.

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

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


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

Package: src:timew
Version: 1.5.0+ds.1-2
Severity: important
Tags: sid trixie ftbfs
User: debian-pyt...@lists.debian.org
Usertags: python3.12

With python3-defaults from experimental, the package fails its autopkg 
tests:


[...]
621s 'continue.t' failed to run all tests.
621s Passed:   323
621s Failed:21
621s Unexpected successes:   0
621s Skipped:   11
621s Expected failures:  0
621s Runtime:18.10 seconds
622s autopkgtest [14:27:26]: test timewarrior: ---]
622s autopkgtest [14:27:26]: test timewarrior:  - - - - - - - - - - 
results - - - - - - - - - -

622s timewarrior  FAIL non-zero exit status 1

complete build log at
https://autopkgtest.ubuntu.com/results/autopkgtest-noble/noble/amd64/t/timew/20240126_142736_bcfc0@/log.gz
--- End Message ---
--- Begin Message ---
Source: timew
Source-Version: 1.7.1+ds.1-2
Done: Andreas Tille 

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

Debian distribution maintenance software
pp.
Andreas Tille  (supplier of updated timew package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Feb 2024 10:25:40 +0100
Source: timew
Architecture: source
Version: 1.7.1+ds.1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Tasktools Team 
Changed-By: Andreas Tille 
Closes: 1047001 1061850
Changes:
 timew (1.7.1+ds.1-2) unstable; urgency=medium
 .
   * Team upload.
   * Run tests with all supported Python3 versions to verify problems with
 non-default Python3 versions
   * Autopkgtest: Restrictions: allow-stderr
 Closes: #1061850
   * Stop changing shebang in Python3 scripts and add debian/clean to fix
 dh_clean target
 Closes: #1047001
Checksums-Sha1:
 86b28a410e6c520551c2eba21dcd279af4e8de57 2106 timew_1.7.1+ds.1-2.dsc
 f74cb06faba42b41bdc141ef46ea4c33fcc560f2 7028 timew_1.7.1+ds.1-2.debian.tar.xz
 1d46aa907517e0800a3f354b8f4383571131159f 8367 
timew_1.7.1+ds.1-2_amd64.buildinfo
Checksums-Sha256:
 48aebcc75ae33f982362761843a6be787ce767327e43a108425074c6a830b744 2106 
timew_1.7.1+ds.1-2.dsc
 c4ac0210d9875b758548472fe76f90b9af47ee16e9b4c96a17f79bedfe6b2000 7028 
timew_1.7.1+ds.1-2.debian.tar.xz
 1432c6240a634ef90d7b31a3da830e77f997e14a40eb873f5b5302107ebbe3af 8367 
timew_1.7.1+ds.1-2_amd64.buildinfo
Files:
 0a7eba38a09bb76db9fea5156815b921 2106 utils optional timew_1.7.1+ds.1-2.dsc
 cc3c85e68dca72cd155656de6f1b00c6 7028 utils optional 
timew_1.7.1+ds.1-2.debian.tar.xz
 8f177f719d4da1bd9db7738dfa32e556 8367 utils optional 
timew_1.7.1+ds.1-2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmXbCOgRHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtFsEQ/9GLbD+gJNHS7s31Qw12oojEAqKOYgZELx
v/3dRmHY8b7eE7004GdUqAaQAl99Bn52yYK8+Dj1ZtIRqcxYc7EiWQigPQ/o87/C
8iRXO0rEw55wN+tfQL9YuAUyOJ4yqKhG5QCEHlhxVnZi5CT/8fOe/FQ4PS8O9rmo
1yqtv5zBbbkqFZIDqHwkil037oLl7DIPkMxIRinerntut6YhUREpnTRSqJxdGM5A
m0b/9qdSEVIrI1zwu/RhLpnLGi4bMGjalJ51ed2UmsIlIbVnCHG9ZzBkQbotnN3s
KB8bP3DVkeW/x9MOoyA2rVl2a4vI6EQ1Gf6l18S3jHdobUQiqg5+0rKdSnCUzuHU
TBzVEZMHPM0wSvsPUPsg4Ym/0P/7SgsbLkS2AO6r8xZldXNxpzIld0pV4QzvNod3
IXw5L6n2N0n/W+gyWeD/AEa9A77r9g1xCA8+/WIofy6sBRu4s+IWhJ1DlSniiAI4
07Y5utf8VfBIC+bPdQuSR8e741B9/I/EbwKxeD/dIuX7ZdN14DNCI2X8xxYASd/Q
+oehQppx3x4esAI3gIc4kc9G/JvJK7oj02xTD6sFO4MbkV1pHnJEDwvkSEZNO5lX
xamEP1fbxiRuVt/pV37+C7HMLA1S4bSfLUS2Nu6kno9Fufj5DHdZ2WAALV5XqswZ
UubfxSlNu1c=
=phh2
-END PGP SIGNATURE-



pgpXUehKtmVg0.pgp
Description: PGP signature
--- End Message ---

Bug#1064570: marked as done (fparser: please remove extraneous dependency on python3-six)

[Debian Bug Tracking System]

Your message dated Sun, 25 Feb 2024 08:34:43 +
with message-id 
and subject line Bug#1064570: fixed in fparser 0.1.4-3
has caused the Debian Bug report #1064570,
regarding fparser: please remove extraneous dependency on python3-six
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.)


-- 
1064570: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064570
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: fparser
Version: 0.1.4-2
Severity: normal

Hi,

Please remove from debian/control the stale reference to python3-six.

Please also push the packaging tree to Salsa.
(or remove the old Vcs- tags)

Greetings,

Alexandre
--- End Message ---
--- Begin Message ---
Source: fparser
Source-Version: 0.1.4-3
Done: Alastair McKinstry 

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

Debian distribution maintenance software
pp.
Alastair McKinstry  (supplier of updated fparser package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Sun, 25 Feb 2024 06:54:57 +
Source: fparser
Architecture: source
Version: 0.1.4-3
Distribution: unstable
Urgency: medium
Maintainer: Alastair McKinstry 
Changed-By: Alastair McKinstry 
Closes: 1064570
Changes:
 fparser (0.1.4-3) unstable; urgency=medium
 .
   * Remove obsolete dep. on python-six. Closes: #1064570
Checksums-Sha1:
 8d88c1a6ee6acd0dd41b978e32132f74317e4c27 1970 fparser_0.1.4-3.dsc
 0f3ed98998ee64e2b4462bdb13a42e06c10ae429 4496 fparser_0.1.4-3.debian.tar.xz
Checksums-Sha256:
 ba2d005a6bd6b4984a8d60606ea68ae4e0b8af2e3eae172c2547771cb6bfea76 1970 
fparser_0.1.4-3.dsc
 5d8e449953ee9f832dbdccb54f97827a00600401af2e8feaa07e525fdc5d4c5f 4496 
fparser_0.1.4-3.debian.tar.xz
Files:
 a1d528df1059ba4218dedec07de5a2cb 1970 python optional fparser_0.1.4-3.dsc
 e2e941311f201ece50a1b8a320a09bd1 4496 python optional 
fparser_0.1.4-3.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEgjg86RZbNHx4cIGiy+a7Tl2a06UFAmXa7YMACgkQy+a7Tl2a
06Xm3xAAlGiiGTB6rcoXBKzA1rhd4FdZsZn/9IYNaZVxRC+Kk6/vCNRhnnWbhLKa
/kSjuZLur/qL9p5MZlVenddIGKrUb+jPF/P9IuYzc+iamoZpPZkNE7x8Nch0Jeez
RmCp64hVwLO+9PbSWIUw7SPf04kW3ccZC2VwEv3YCy3K4i1n4o+wJLnmkZ72iTcl
g+IzIjtHeAp0SAZeNRQKqd2aKXULDQMKb12ti3xctzxqVxwM95+qK5rbJFQogKgI
H2uT641u1xsvX0c+uzik2ffsY+n2GV9uW4K90K3iYvp3jkuIq6FAbNdY9CavLZWV
Vvct79/v8or5T+TQ3n6htmKT02DcqRSJ79nifWOi7Hnqxc6QK/BwdQl9CPe9WSl1
UNzk4W3+lcv8Me3uFQdDeLFVU+aN6WwMCeeYeI6X2MWJ6J3IZoTBqssG7mHV57DN
HW7Ec6J9b/Iu6kTMT68K3swhbuTdy94t2POXB+siT/nndUCypgjdOwOHaN+Nt85z
LBXqdPyHnYRzzUNlIhTaJXcd2yTxEmLZV/Xt4o9E5TzK/EcglVMNELbhQqt7N32Y
pgA42E2+Y2CwnZ2KU+F0dB7TEdGp95wp+GKqPIQUwWLlr91XqAnwBF0mBp15W6jY
pcgXOzqB5f8BKNtGHADd+MyOGJbscd8TrnNcPALXK5+jhr+B+7E=
=lmvl
-END PGP SIGNATURE-



pgpzTzzEuI8SS.pgp
Description: PGP signature
--- End Message ---