Bug#1023842: rust-criterion - inconsistent dependencies on cast.

[Jonas Smedegaard]

Quoting Peter Green (2022-11-12 01:16:23)
> On 11/11/2022 16:02, Jonas Smedegaard wrote:
> 
> > 
> > My work on other packages (rust-test-case) recently revealed that my
> > approach to embedding crates is broken, so I will do some more poking to
> > get it to not only succeed building on its own but also builds as
> > dependency of other Rust crates.
> 
> Note that criterion-plot is packaged in Debian, so an alternative way
> to fix this would be to stop embedding it and use the packaged version.

Ahhh, *that* is probably why this bug wasn't caught earlier: Other
packages simply pull in the separately packaged version.

Thanks for pointing that out :-)

I do think, however, that the better approach is for rust-criterion to
take over that other binary package, since it is part of same upstream
source project (yes, I am aware that the Rust project has a different
approach...).  I'll think on it and fie a separate bugreport about that
unless I change my mind - i.e. let's not discuss that further here.


 - Jonas

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

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

signature.asc
Description: signature

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Vincent Lefevre]

Hi,

On 2022-11-11 11:32:33 -0700, Sean Whitton wrote:
> On Thu 10 Nov 2022 at 11:23AM +01, Vincent Lefevre wrote:
> > On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
> >> Are you able to test the patch?  Let me know if you need help getting an
> >> installable .deb.  Thanks.
> >
> > Sorry, I couldn't test it yet, first because of an uninstallable
> > package needed for the build because I couldn't upgrade libc6 yet
> > and I couldn't get the previous version from snapshot.debian.org
> > (bug 1023540). Now that I could upgrade libc6, I'll be able to
> > test when I have some time, but perhaps not before the week-end.
> 
> Okay, do let me know if I can help -- this is blocking Emacs from migrating.

I've rebuilt the packages with the patch and couldn't reproduce
the bug yet. So it may be the correct fix.

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

Bug#1021779: orage: eats events

[Nicolas Mora]

Le 2022-11-11 à 14 h 41, Slavko a écrit :


Yes, with current libical3 (in testing) the problem is solved, can be
closed.


Thanks, closing it then

Processed: found 1021753 in 3.0.2-1

[Debian Bug Tracking System]

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

> found 1021753 3.0.2-1
Bug #1021753 [src:ganeti] ganeti: conflicting curl build-depends
Marked as found in versions ganeti/3.0.2-1.
> thanks
Stopping processing here.

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

Bug#1023732: marked as done (xfce4-settings: CVE-2022-45062: argument injection vulnerability in xfce4-mime-helper)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 00:21:15 +
with message-id 
and subject line Bug#1023732: fixed in xfce4-settings 4.16.4-1
has caused the Debian Bug report #1023732,
regarding xfce4-settings: CVE-2022-45062: argument injection vulnerability in 
xfce4-mime-helper
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.)


-- 
1023732: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023732
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: xfce4-settings
Version: 4.16.3-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for xfce4-settings.

CVE-2022-45062[0]:
| In Xfce xfce4-settings before 4.16.4 and 4.17.x before 4.17.1, there
| is an argument injection vulnerability in xfce4-mime-helper.


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-2022-45062
https://www.cve.org/CVERecord?id=CVE-2022-45062
[1] https://gitlab.xfce.org/xfce/xfce4-settings/-/issues/390 (not public)
[2] 
https://gitlab.xfce.org/xfce/xfce4-settings/-/commit/55e3c5fb667e96ad1412cf249879262b369d28d7
 (xfce4-settings-4.16.4)
[3] 
https://gitlab.xfce.org/xfce/xfce4-settings/-/commit/f34a92a84f96268ad24a7a13fd5edc9f1d526110
 (xfce4-settings-4.17.1)

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xfce4-settings
Source-Version: 4.16.4-1
Done: Unit 193 

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

Debian distribution maintenance software
pp.
Unit 193  (supplier of updated xfce4-settings 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: SHA384

Format: 1.8
Date: Fri, 11 Nov 2022 18:43:28 -0500
Source: xfce4-settings
Architecture: source
Version: 4.16.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Xfce Maintainers 
Changed-By: Unit 193 
Closes: 1023732
Changes:
 xfce4-settings (4.16.4-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Debian Janitor ]
   * Remove constraints unnecessary since buster
 .
   [ Unit 193 ]
   * New upstream version 4.16.4.
 - Escape characters which do not belong into an URI/URL.
   Closes: #1023732, CVE-2022-45062.
   * d/control: Drop version constraints no longer needed.
Checksums-Sha1:
 5197bfa89f71c93011f3a3af76d356bbfc316531 2320 xfce4-settings_4.16.4-1.dsc
 7c0b922d808cc71b4446d0e71b0576a3bda10365 1498757 
xfce4-settings_4.16.4.orig.tar.bz2
 7a9d4c3732abc85069b8f560b3774d81dd331bd9 9064 
xfce4-settings_4.16.4-1.debian.tar.xz
 df44068ddaafbfd7274ffdf01d49bd216d98b2e7 16214 
xfce4-settings_4.16.4-1_amd64.buildinfo
Checksums-Sha256:
 6570c8362c47be8e118d366b3b173e0cfcc8246ce826785cff0354e5ebfc59ed 2320 
xfce4-settings_4.16.4-1.dsc
 18aba42fd251406881176b8ded9b3aa5b49f50f2dc6bd447c1cb495f81a0a3ed 1498757 
xfce4-settings_4.16.4.orig.tar.bz2
 b203124854a5a843872c65d9ef46303eb2ec9f8837683cbbba7bab9b81143b45 9064 
xfce4-settings_4.16.4-1.debian.tar.xz
 489ab93f540f8d99400dec5e05a76df44e662cff36977c6a360e64f9f2b79322 16214 
xfce4-settings_4.16.4-1_amd64.buildinfo
Files:
 a29e6d5e4371c13f0cd042bf4cdcdc51 2320 xfce optional xfce4-settings_4.16.4-1.dsc
 c44ce3e5468925c4f107b4fa2cb4591a 1498757 xfce optional 
xfce4-settings_4.16.4.orig.tar.bz2
 cddc00873de1e55950895905c708addf 9064 xfce optional 
xfce4-settings_4.16.4-1.debian.tar.xz
 c6ce37063f22a62dd72f31cbd1f58f14 16214 xfce optional 
xfce4-settings_4.16.4-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCQAdFiEEjbPlhoZdK0orGFpcUAHhsJqjdEsFAmNu4VIACgkQUAHhsJqj
dEtP/A/+P32cotvqMy4xeCNSGEfJDJk4i2+qkcSPQzxn94cyifJl6yba/VG9Gm4O
l6GSFzeJhMPzWxmfJVAlWUSWnpIdIeUICjBX7yaOocJuRycGMpiTGK1/X7m5KRu0
G6rUIQMIANqKs2lzyC0DXpmDqyyUixQfPIF+G3cjfLmMgH1QK2TmDtkP9E2zW5Bv
3Nk3L2BuLC93Pae8YU/XeQkNGtIgt0jTbi+ZSzf7FrT6kqzJhkdXF2bdItE0aG1+
zO5miWTyTTI+Z+ly/aZYlnsJdSJC+MWDsPQ9Ynacr4uiGYKRne3omF7bxB9diB4s

Bug#1020056: marked as done (tango: FTBFS: configure: error: Couldn't find a compatible zmq.hpp)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 00:21:03 +
with message-id 
and subject line Bug#1020056: fixed in tango 9.3.4+dfsg1-2
has caused the Debian Bug report #1020056,
regarding tango: FTBFS: configure: error: Couldn't find a compatible zmq.hpp
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.)


-- 
1020056: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020056
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: tango
Version: 9.3.4+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220917 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> checking for omniORB4 >= 4.1.2... yes
> checking for omniCOS4 >= 4.1.2... yes
> checking whether CORBA modules mapped to namespaces... yes
> checking for libzmq >= 4.0.5... yes
> checking for zmq.hpp... no
> configure: error: Couldn't find a compatible zmq.hpp
>   tail -v -n \+0 config.log


The full build log is available from:
http://qa-logs.debian.net/2022/09/17/tango_9.3.4+dfsg1-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: tango
Source-Version: 9.3.4+dfsg1-2
Done: Utkarsh Gupta 

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

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

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

Debian distribution maintenance software
pp.
Utkarsh Gupta  (supplier of updated tango package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2022 23:29:16 +0530
Source: tango
Architecture: source
Version: 9.3.4+dfsg1-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Science Maintainers 

Changed-By: Utkarsh Gupta 
Closes: 994226 1020056
Changes:
 tango (9.3.4+dfsg1-2) unstable; urgency=medium
 .
   [ Picca Frédéric-Emmanuel ]
   * Bug fix: "tango-starter has an unmet service dependency from some
 other service", thanks to Carlos Falcon (Closes: #994226).
   * Bump debhelper from old 12 to 13.
   * Update standards version to 4.6.0, no changes needed.
 .
   [ Stephan Lachnit, Utkarsh Gupta ]
   * zmq.hpp now in cppzmq-dev (Closes: #1020056)
 .
   [ Utkarsh Gupta ]
   * Revert "Bump debhelper from old 12 to 13".
Checksums-Sha1:
 69f9411d12a2b46db6052c6b9737d06231274144 2787 tango_9.3.4+dfsg1-2.dsc
 a9dcd2f5ef2d81b1d6d480065651d0d7b24ca0aa 60354476 tango_9.3.4+dfsg1.orig.tar.xz
 52aae4c7dcc99f81e575e3024bfdfc72739c90ae 30072 
tango_9.3.4+dfsg1-2.debian.tar.xz
 87e1f184ccfd20bcc8f49ef5a9cf4344b69a14a5 6241 
tango_9.3.4+dfsg1-2_source.buildinfo
Checksums-Sha256:
 01df6f4c03cb27b277906dabb0104c71647cf63317de6abd8f3eec12e1a839be 2787 
tango_9.3.4+dfsg1-2.dsc
 8d66ca336259ee716559f86bc3e11476ee6f4dd3ef2653a2c6402537f9f3b7a8 60354476 
tango_9.3.4+dfsg1.orig.tar.xz
 6e4d3afd443cd1e1cdadccefa83714267b7634b648e6a5d2ee8a474c85c0cefe 30072 
tango_9.3.4+dfsg1-2.debian.tar.xz
 f945c20b98d862f06f10ad29796a656c290ee7843dd21df43fef06a952adba1a 6241 
tango_9.3.4+dfsg1-2_source.buildinfo
Files:
 5d66d2c3c13daf60e8c19cb553e2fd40 2787 science optional tango_9.3.4+dfsg1-2.dsc
 a485e4779e966c70ccfe76a215497d33 60354476 science optional 
tango_9.3.4+dfsg1.orig.tar.xz
 1aae8136153061bec01f7456957ecfc9 30072 science optional 
tango_9.3.4+dfsg1-2.debian.tar.xz
 fd06869460b524c5c90f5db5f6eab957 6241 science optional 
tango_9.3.4+dfsg1-2_source.buildinfo

-BEGIN PGP SIGNATURE-

Processed: Merge duplicates

[Debian Bug Tracking System]

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

> reassign 1022018 ganeti-testsuite
Bug #1022018 [src:ganeti] ganeti: Uses deprecated yaml.load
Bug reassigned from package 'src:ganeti' to 'ganeti-testsuite'.
No longer marked as found in versions ganeti/3.0.2-1.
Ignoring request to alter fixed versions of bug #1022018 to the same values 
previously set
> forcemerge 1023299 1022018
Bug #1023299 [ganeti-testsuite] ganeti-testsuite: yaml.load in testsuite needs 
to specify loader
Bug #1022018 [ganeti-testsuite] ganeti: Uses deprecated yaml.load
Severity set to 'serious' from 'normal'
Marked as found in versions ganeti/3.0.2-1.
Added tag(s) sid, upstream, bookworm, and ftbfs.
Merged 1022018 1023299
> thanks
Stopping processing here.

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

Bug#1023842: rust-criterion - inconsistent dependencies on cast.

[Peter Green]

On 11/11/2022 16:02, Jonas Smedegaard wrote:



My work on other packages (rust-test-case) recently revealed that my
approach to embedding crates is broken, so I will do some more poking to
get it to not only succeed building on its own but also builds as
dependency of other Rust crates.


Note that criterion-plot is packaged in Debian, so an alternative way
to fix this would be to stop embedding it and use the packaged version.

Processed: found 1021779 in 3.0.15-1, notfixed 1022893 in 0.0.0+git.2022.09.25.d0d2a96a6e-3 ..., tagging 855037 ...

[Debian Bug Tracking System]

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

> found 1021779 3.0.15-1
Bug #1021779 [libical3] orage: eats events
Marked as found in versions libical3/3.0.15-1.
> notfixed 1022893 0.0.0+git.2022.09.25.d0d2a96a6e-3
Bug #1022893 {Done: Nilesh Patra } 
[src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: binary-any 
FTBFS
No longer marked as fixed in versions 
golang-github-etcd-io-gofail/0.0.0+git.2022.09.25.d0d2a96a6e-3.
> fixed 1022893 0.0.0+git.2022.09.25.d0d2a96a6e-4
Bug #1022893 {Done: Nilesh Patra } 
[src:golang-github-etcd-io-gofail] golang-github-etcd-io-gofail: binary-any 
FTBFS
Marked as fixed in versions 
golang-github-etcd-io-gofail/0.0.0+git.2022.09.25.d0d2a96a6e-4.
> tags 855037 + bullseye sid
Bug #855037 {Done: Mike Gabriel } 
[mate-applets] mate-panel: org.mate.panel.applet.MultiLoadAppletFactory fills 
the syslog
Added tag(s) bullseye and sid.
> tags 1014851 + bookworm sid
Bug #1014851 {Done: Matthias Klose } [gcc-10] Missing SLS 
mitigation (-mharden-sls) for x86
Added tag(s) bookworm and sid.
> tags 1012787 + bullseye sid
Bug #1012787 {Done: Michael Biebl } [systemd] systemd: 
Sometimes systemd mount check fails
Added tag(s) sid and bullseye.
> tags 971044 + sid bookworm
Bug #971044 {Done: Noah Meyerhans } [iputils-ping] 
iputils-ping: ping reports socket error when IPv6 is disabled
Bug #1004843 {Done: Noah Meyerhans } [iputils-ping] ping 
(from iputils-ping) throwing inappropriate error message if IPv6 is disabled
Added tag(s) bookworm and sid.
Added tag(s) sid and bookworm.
> tags 971640 + bullseye sid
Bug #971640 {Done: Reiner Herrmann } [firejail] firejail: 
Build profile command no longer works
Added tag(s) bullseye and sid.
> tags 1001592 + bookworm sid
Bug #1001592 {Done: Victor Seva } [prosody] prosody: changes 
certs/localhost.{crt,key} back to snakeoil on upgrade
Added tag(s) sid and bookworm.
> tags 991596 + bookworm sid
Bug #991596 {Done: Salvatore Bonaccorso } [bluez] bluez: 
CVE-2021-3658
Added tag(s) sid and bookworm.
> tags 979610 + bookworm sid
Bug #979610 {Done: Gregor Jasny } [src:v4l-utils] 
v4l-utils: vendors ancient version of libbpf
Added tag(s) bookworm and sid.
> tags 945574 + bullseye sid
Bug #945574 {Done: Simon McVittie } [mutter] mutter [buster 
only]: incorrect workspace movement animations for a 2D layout
Added tag(s) bullseye and sid.
> tags 963492 + bullseye sid
Bug #963492 {Done: Christian Göttsche } [logrotate] 
logrotate: Copytruncate breaks rotate 0
Added tag(s) bullseye and sid.
> tags 943692 + bullseye sid
Bug #943692 {Done: Luigi Gangitano } [squid] squid: crash on 
bug #4823 : assertion failed: stmem.cc:98: "lowestOffset () <= target_offset"
Bug #92 {Done: Luigi Gangitano } [squid] squid: Crashes 
when listening to audio stream over the Squid proxy
Added tag(s) bullseye and sid.
Added tag(s) sid and bullseye.
> tags 986418 + bookworm sid
Bug #986418 {Done: Rene Engelhard } [libreoffice-impress] 
libreoffice-impress: Impress cannot reduce table row size
Added tag(s) bookworm and sid.
> tags 985556 + bullseye sid
Bug #985556 {Done: Simon McVittie } [glib2.0] 
flatpak/1.2.5-0+deb10u4 FTBFS on IPv6-only buildds
Added tag(s) bullseye and sid.
> tags 969597 + sid
Bug #969597 {Done: Stephen Kitt } [libzstd] libzstd: Please 
correct version in symbol file
Added tag(s) sid.
> tags 972939 + bullseye sid
Bug #972939 {Done: Laurent Bigonville } [src:libfabric] 
libfabric: Provide libfabric packages for arm64
Added tag(s) bullseye and sid.
> tags 955567 + bullseye sid
Bug #955567 {Done: Norbert Preining } [kalgebra] kalgebra: 
Output is always blank
Added tag(s) sid and bullseye.
> tags 935156 + bullseye sid
Bug #935156 {Done: Thomas Goirand } [ceph] ceph: Multiple mon 
deployment failure on arm64: ms_verfity_authorizer bad authorizer and crc check 
failure
Added tag(s) sid and bullseye.
> tags 947080 + sid
Bug #947080 {Done: Debian FTP Masters } 
[getmail] [getmail] Crashes when not being able to decode encoding of Cc line
Added tag(s) sid.
> tags 953948 + bullseye sid
Bug #953948 {Done: Craig Small } [src:net-snmp] libsnmp30: 
Dependency on libmariadb3
Added tag(s) bullseye and sid.
> tags 964103 + bullseye sid
Bug #964103 {Done: Salvatore Bonaccorso } 
[src:pdns-recursor] pdns-recursor: CVE-2020-14196: Access restriction bypass
Added tag(s) bullseye and sid.
> tags 956179 + bullseye sid
Bug #956179 {Done: Laurent Bigonville } 
[libspice-client-gtk-3.0-5] libspice-client-gtk-3.0-5: Mouse cursor invisible 
in virt-manager on Wayland
Added tag(s) sid and bullseye.
> tags 941745 + bullseye sid
Bug #941745 {Done: Sven Geuer } [tomb] Tomb 2.6 provides 
an important fix
Added tag(s) sid and bullseye.
> fixed 941745 2.6+dfsg1-1
Bug #941745 {Done: Sven Geuer } [tomb] Tomb 2.6 provides 
an important fix
Marked as fixed in versions tomb/2.6+dfsg1-1.
> tags 941745 + bullseye sid
Bug #941745 {Done: Sven Geuer } [tomb] Tomb 2.6 provides 
an important fix
Ignoring request to alter tags of bug #941745 to the same tags previously set
> tags 958721 + 

Processed: tagging 1001643

[Debian Bug Tracking System]

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

> tags 1001643 + bookworm sid
Bug #1001643 [sdaps] sdaps: fails to setup a project with 
texlive-latex-extra/unstable (2021.2021127-1)
Added tag(s) bookworm and sid.
> thanks
Stopping processing here.

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

Bug#1023531: marked as done (utox: autopkgtest regression on s390x: test_chrono fails)

[Debian Bug Tracking System]

Your message dated Sat, 12 Nov 2022 00:33:53 +0100
with message-id 
and subject line Re: Bug#1023531: utox: autopkgtest regression on s390x: 
test_chrono fails
has caused the Debian Bug report #1023531,
regarding utox: autopkgtest regression on s390x: test_chrono 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.)


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

Source: utox
Version: 0.18.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

Your package has an autopkgtest, great. With a recent upload of glibc it 
started to fail on s390x. Looking at the history [1], I noticed that 
apparently the test can flip from passing for a while to failing for a 
while and back. Unfortunately, we don't keep the logs so long to inspect 
if previous (pre August 2022) failures were due to the same reason. 
Unfortunately, the output of the failure is rather limited (it seems 
there is more info logged, but that log file is not echoed to the 
autopkgtest log or stored as an autopkgtest artifact.


Can you please investigate the situation? At least this is a autopkgtest 
regression on a release architecture, but maybe (hopefully?) this points 
at more severe issues.


If you find out that it's really a regression in glibc functionality and 
the upload doesn't "just" trigger faulty behavior in utox, don't 
hesitate to reassign to glibc. Also, don't hesitate to contact the s390x 
porters if you need help figuring out this s390x specific issue.


Paul

[1] https://ci.debian.net/packages/u/utox/testing/s390x/


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: check/0.15.2-2+b1

On 2022-11-09 22:30, Paul Gevers wrote:
> > >    wb nmu check . ANY . -m 'Rebuild against GCC 12 (Closes: #1023531).'
> 
> Scheduled.
> 

Thanks, the utox autopkgtest now pass on s390x in both testing and
unstable. I am therefore closing the bug accordingly.

Regards
Aurelien

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


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

Bug#1023531: utox: autopkgtest regression on s390x: test_chrono fails

[Aurelien Jarno]

On 2022-11-10 08:37, Paul Gevers wrote:
> Hi,
> 
> On 09-11-2022 23:02, Aurelien Jarno wrote:
> > Unfortunately I am not sure we want to do that, as we don't know if this
> > GCC version incompatibility (that seems specific to s390x, at least in
> > the utox context) will also happen for the next GCC version.
> 
> I noticed yesterday that the previous build of check was done with gcc-10,
> so not the previous gcc. Apparently mixing gcc-10 check and gcc-11 glibc was
> "fine".
> 
> > Now if we consider it will break again, the more elegant solution would
> > be to change check to use dynamic linking instead of static linking.
> > Alternatively we can export the GCC version used to compile GLIBC (for
> > instance providing libc6-gcc11 or libc6-gcc12) and add some code in
> > check to add a depends on that. A simpler way would just be to add a
> > depends on the major glibc version (so libc6 (>> 2.36), libc6 (<< 2.37))
> > as we *tend* to change the GCC version used at the same time than the
> > major version (at least for sid, not true for experimental).
> 
> So maybe we (Release Team and glibc maintainers) should ignore this issue
> for now. At least, not create overly complicated solutions outside of check,
> just to accommodate only that package.
> 

That's indeed the best, it just mean we should carefully look at
autopkgtest on new glibc versions, and look for real issues among the
flaky tests.

Regards
Aurelien

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


signature.asc
Description: PGP signature

Processed: unmerging 1003543

[Debian Bug Tracking System]

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

> unmerge 1003543
Bug #1003543 [shush] shush: crontab path not defined
Bug #934664 [shush] shush: fails to send email
Disconnected #1003543 from all other report(s).
> thanks
Stopping processing here.

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

Processed: forcibly merging 1003543 934664

[Debian Bug Tracking System]

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

> forcemerge 1003543 934664
Bug #1003543 [shush] shush: crontab path not defined
Bug #934664 [shush] shush: fails to send email
Severity set to 'grave' from 'important'
Merged 934664 1003543
> thanks
Stopping processing here.

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

Bug#1022449: python-maxminddb: diff for NMU version 2.0.3-1.1

[Faidon Liambotis]

On Fri, Nov 11, 2022 at 11:56:18PM +0200, Stefano Rivera wrote:
> I've prepared an NMU for python-maxminddb (versioned as 2.0.3-1.1) and
> uploaded it to DELAYED/2. Please feel free to tell me if I
> should delay it longer.

Thank you so much Stefano! I've been meaning to update to the latest
upstream release for a while (alongside libmaxminddb itself), but life
has gotten busy -- I'm slowly getting there though for the past couple
of weeks :)

This is currently in the top-3 of my list, and I expect to work on this
in the next week at the latest. I don't mind having an NMU, though,
whether targeted or for the new upstream version itself. If you do make
an upload, I have one small request, which would be to push the changes
to the git repo if you can (it's under the "debian" salsa project). If
you're interested in doing further work in this package, you are also
more than welcome to add yourself to Uploaders and make this a
maintainer upload. If not, totally understandable :)

Best,
Faidon

Bug#1023654:

[Daniel Kamil Kozar]

This also affects mpd. Please see bug #1023872 for the details , but
the gist is the same as the samba situation described here.

Processed: iitalian: diff for NMU version 1:2.3-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 965591 + patch
Bug #965591 [src:iitalian] iitalian: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Ignoring request to alter tags of bug #965591 to the same tags previously set
> tags 965591 + pending
Bug #965591 [src:iitalian] iitalian: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Ignoring request to alter tags of bug #965591 to the same tags previously set
> tags 996361 + patch
Bug #996361 [iitalian] iitalian: Italian hash file not compatible with current 
version of ispell
Ignoring request to alter tags of bug #996361 to the same tags previously set
> tags 996361 + pending
Bug #996361 [iitalian] iitalian: Italian hash file not compatible with current 
version of ispell
Ignoring request to alter tags of bug #996361 to the same tags previously set
> tags 999201 + patch
Bug #999201 [src:iitalian] iitalian: missing required debian/rules targets 
build-arch and/or build-indep
Ignoring request to alter tags of bug #999201 to the same tags previously set
> tags 999201 + pending
Bug #999201 [src:iitalian] iitalian: missing required debian/rules targets 
build-arch and/or build-indep
Ignoring request to alter tags of bug #999201 to the same tags previously set

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

Processed: iitalian: diff for NMU version 1:2.3-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 965591 + patch
Bug #965591 [src:iitalian] iitalian: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Ignoring request to alter tags of bug #965591 to the same tags previously set
> tags 965591 + pending
Bug #965591 [src:iitalian] iitalian: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Ignoring request to alter tags of bug #965591 to the same tags previously set
> tags 996361 + patch
Bug #996361 [iitalian] iitalian: Italian hash file not compatible with current 
version of ispell
Ignoring request to alter tags of bug #996361 to the same tags previously set
> tags 996361 + pending
Bug #996361 [iitalian] iitalian: Italian hash file not compatible with current 
version of ispell
Ignoring request to alter tags of bug #996361 to the same tags previously set
> tags 999201 + patch
Bug #999201 [src:iitalian] iitalian: missing required debian/rules targets 
build-arch and/or build-indep
Ignoring request to alter tags of bug #999201 to the same tags previously set
> tags 999201 + pending
Bug #999201 [src:iitalian] iitalian: missing required debian/rules targets 
build-arch and/or build-indep
Ignoring request to alter tags of bug #999201 to the same tags previously set

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

Processed: iitalian: diff for NMU version 1:2.3-3.1

[Debian Bug Tracking System]

Processing control commands:

> tags 965591 + patch
Bug #965591 [src:iitalian] iitalian: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Added tag(s) patch.
> tags 965591 + pending
Bug #965591 [src:iitalian] iitalian: Removal of obsolete debhelper compat 5 and 
6 in bookworm
Added tag(s) pending.
> tags 996361 + patch
Bug #996361 [iitalian] iitalian: Italian hash file not compatible with current 
version of ispell
Added tag(s) patch.
> tags 996361 + pending
Bug #996361 [iitalian] iitalian: Italian hash file not compatible with current 
version of ispell
Added tag(s) pending.
> tags 999201 + patch
Bug #999201 [src:iitalian] iitalian: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) patch.
> tags 999201 + pending
Bug #999201 [src:iitalian] iitalian: missing required debian/rules targets 
build-arch and/or build-indep
Added tag(s) pending.

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

Bug#965591: iitalian: diff for NMU version 1:2.3-3.1

[Adrian Bunk]

Control: tags 965591 + patch
Control: tags 965591 + pending
Control: tags 996361 + patch
Control: tags 996361 + pending
Control: tags 999201 + patch
Control: tags 999201 + pending

Dear maintainer,

I've prepared an NMU for iitalian (versioned as 1:2.3-3.1) and uploaded 
it to DELAYED/10. Please feel free to tell me if I should cancel it.

cu
Adrian
diff -u iitalian-2.3/debian/rules iitalian-2.3/debian/rules
--- iitalian-2.3/debian/rules
+++ iitalian-2.3/debian/rules
@@ -47 +47,4 @@
-.PHONY: binary binary-arch binary-indep clean checkroot
+build-arch: build
+build-indep: build
+
+.PHONY: binary binary-arch binary-indep build-arch build-indep clean checkroot
diff -u iitalian-2.3/debian/changelog iitalian-2.3/debian/changelog
--- iitalian-2.3/debian/changelog
+++ iitalian-2.3/debian/changelog
@@ -1,3 +1,12 @@
+iitalian (1:2.3-3.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * debian/compat: 5 -> 7. (Closes: #965591)
+  * debian/rules: Add build-{arch,indep}. (Closes: #999201)
+  * Rebuild with new ispell. (Closes: #996361)
+
+ -- Adrian Bunk   Fri, 11 Nov 2022 23:53:01 +0200
+
 iitalian (1:2.3-3) unstable; urgency=low
 
   [ Robert Luberda ]
diff -u iitalian-2.3/debian/compat iitalian-2.3/debian/compat
--- iitalian-2.3/debian/compat
+++ iitalian-2.3/debian/compat
@@ -1 +1 @@
-5
+7

Bug#1022449: python-maxminddb: diff for NMU version 2.0.3-1.1

[Stefano Rivera]

Control: tags 1022449 + patch
Control: tags 1022449 + pending

Dear maintainer,

I've prepared an NMU for python-maxminddb (versioned as 2.0.3-1.1) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should delay it longer.

Regards.

SR
diff -Nru python-maxminddb-2.0.3/debian/changelog python-maxminddb-2.0.3/debian/changelog
--- python-maxminddb-2.0.3/debian/changelog	2020-12-11 06:29:45.0 +0200
+++ python-maxminddb-2.0.3/debian/changelog	2022-11-11 23:49:29.0 +0200
@@ -1,3 +1,10 @@
+python-maxminddb (2.0.3-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Patch: Avoid distutils, supporting setuptools >= 60. (Closes: #1022449)
+
+ -- Stefano Rivera   Fri, 11 Nov 2022 23:49:29 +0200
+
 python-maxminddb (2.0.3-1) unstable; urgency=medium
 
   * New upstream release.
diff -Nru python-maxminddb-2.0.3/debian/patches/avoid-distutils python-maxminddb-2.0.3/debian/patches/avoid-distutils
--- python-maxminddb-2.0.3/debian/patches/avoid-distutils	1970-01-01 02:00:00.0 +0200
+++ python-maxminddb-2.0.3/debian/patches/avoid-distutils	2022-11-11 23:49:29.0 +0200
@@ -0,0 +1,36 @@
+From: Gregory Oschwald 
+Date: Tue, 7 Dec 2021 14:22:04 -0800
+Subject: Do not use distutils
+
+Origin: upstream, https://github.com/maxmind/MaxMind-DB-Reader-python/commit/4ddd4ca604ab0f78f763664b76d7d0eebfdbe6ae
+Bug-Debian: https://bugs.debian.org/1022449
+---
+ setup.py | 14 +++---
+ 1 file changed, 11 insertions(+), 3 deletions(-)
+
+diff --git a/setup.py b/setup.py
+index 8feb869..2596b41 100644
+--- a/setup.py
 b/setup.py
+@@ -5,10 +5,18 @@ import sys
+ # This import is apparently needed for Nose on Red Hat's Python
+ import multiprocessing
+ 
+-from distutils.command.build_ext import build_ext
+-from distutils.errors import CCompilerError, DistutilsExecError, DistutilsPlatformError
+-
+ from setuptools import setup, Extension
++from setuptools.command.build_ext import build_ext
++
++# These were only added to setuptools in 59.0.1.
++try:
++from setuptools.errors import CCompilerError
++from setuptools.errors import DistutilsExecError
++from setuptools.errors import DistutilsPlatformError
++except ImportError:
++from distutils.errors import CCompilerError
++from distutils.errors import DistutilsExecError
++from distutils.errors import DistutilsPlatformError
+ 
+ cmdclass = {}
+ PYPY = hasattr(sys, "pypy_version_info")
diff -Nru python-maxminddb-2.0.3/debian/patches/series python-maxminddb-2.0.3/debian/patches/series
--- python-maxminddb-2.0.3/debian/patches/series	1970-01-01 02:00:00.0 +0200
+++ python-maxminddb-2.0.3/debian/patches/series	2022-11-11 23:49:29.0 +0200
@@ -0,0 +1 @@
+avoid-distutils

Processed: python-maxminddb: diff for NMU version 2.0.3-1.1

[Debian Bug Tracking System]

Processing control commands:

> tags 1022449 + patch
Bug #1022449 [src:python-maxminddb] python-maxminddb: FTBFS: 
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
Added tag(s) patch.
> tags 1022449 + pending
Bug #1022449 [src:python-maxminddb] python-maxminddb: FTBFS: 
distutils.errors.DistutilsSetupError: each element of 'ext_modules' option must 
be an Extension instance or 2-tuple
Added tag(s) pending.

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

Bug#1023361: marked as done (jupyter-core: CVE-2022-39286: Execution with Unnecessary Privileges in JupyterApp)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 21:49:50 +
with message-id 
and subject line Bug#1023361: fixed in jupyter-core 4.11.2-1
has caused the Debian Bug report #1023361,
regarding jupyter-core: CVE-2022-39286: Execution with Unnecessary Privileges 
in JupyterApp
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.)


-- 
1023361: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023361
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: jupyter-core
Version: 4.11.1-1
Severity: grave
Tags: security upstream
X-Debbugs-Cc: car...@debian.org, Debian Security Team 

Hi,

The following vulnerability was published for jupyter-core.

CVE-2022-39286[0]:
| Jupyter Core is a package for the core common functionality of Jupyter
| projects. Jupyter Core prior to version 4.11.2 contains an arbitrary
| code execution vulnerability in `jupyter_core` that stems from
| `jupyter_core` executing untrusted files in CWD. This vulnerability
| allows one user to run code as another. Version 4.11.2 contains a
| patch for this issue. There are no known workarounds.


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-2022-39286
https://www.cve.org/CVERecord?id=CVE-2022-39286
[1] 
https://github.com/jupyter/jupyter_core/security/advisories/GHSA-m678-f26j-3hrp
[2] 
https://github.com/jupyter/jupyter_core/commit/1118c8ce01800cb689d51f655f5ccef19516e283

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: jupyter-core
Source-Version: 4.11.2-1
Done: Gordon Ball 

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

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

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

Debian distribution maintenance software
pp.
Gordon Ball  (supplier of updated jupyter-core package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Nov 2022 21:06:00 +
Source: jupyter-core
Architecture: source
Version: 4.11.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Gordon Ball 
Closes: 1023361
Changes:
 jupyter-core (4.11.2-1) unstable; urgency=medium
 .
   * New upstream version 4.11.2
   * Fixes CVE-2022-39286 (Closes: #1023361)
Checksums-Sha1:
 9f6c5949498bb8ecc84ce96ad7c89bbf788c8a22 2488 jupyter-core_4.11.2-1.dsc
 79c817a1a5a21f655b4ecf5618411c0c64ddb1f6 73776 jupyter-core_4.11.2.orig.tar.gz
 3823e21b7ff3820d3085d6ebe3a6b7c6925de1cb 7128 
jupyter-core_4.11.2-1.debian.tar.xz
 c9653ff4dcfeaa5ed0af631f503687ba2b3b6b1b 9696 
jupyter-core_4.11.2-1_amd64.buildinfo
Checksums-Sha256:
 6970e5ff9a8e27152978f219458d9c66bfebb225ede05d58eba0263df0f00d7f 2488 
jupyter-core_4.11.2-1.dsc
 11aeeb2ab3d84fd91b3016dfeae20ea153bb35df426e955925af3abff2040650 73776 
jupyter-core_4.11.2.orig.tar.gz
 71cb95939c19ec4f562882ba478b3712c3861b19aae3f4a5c4be0e3afbb0e276 7128 
jupyter-core_4.11.2-1.debian.tar.xz
 4f792068bb4350c3e2e7e1e8c7e210d3e536fc7666fb7384c0dce0b04413d43d 9696 
jupyter-core_4.11.2-1_amd64.buildinfo
Files:
 510947aacb2babec5bacec414534c41e 2488 python optional jupyter-core_4.11.2-1.dsc
 fb0d8b7ae857a5ac66fb6ecec438637c 73776 python optional 
jupyter-core_4.11.2.orig.tar.gz
 d01134a2ac2eff2bdfb35e8a9202a346 7128 python optional 
jupyter-core_4.11.2-1.debian.tar.xz
 50c5d9341494ce199aa827c8c8b634ed 9696 python optional 
jupyter-core_4.11.2-1_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEE6PwpXIa418BJ+Xuno12v+60p6N4FAmNuvn4ACgkQo12v+60p
6N4WVxAAjzfxgRGHWIhGIB3RQRtD4wuPgUpLNCa5UGkAIppRPytQHpfNPNx2hD1E
jroqLIuDgH34iqCBzydU7w0PPlSKxBwRn/RPjYxNXf+YA6dgQKHnivEKAlI/JhfL
TJV4TRcdOxkCexJ4OH3ZiwifBczGJazC7OszvJAxhqBI43E8I/v4lyqgO+74GrWf
TbpEyMKHQ80ztDLrUcMOLObUtbid08k+par4Ld+fcoakdZGtdIHYg9zN/NAUN6ta
+LFWBkzqYFDsxRNKVJDnPbgpa/5zkKaygsJQNn5OsaHcHkKVGf7pgAguw9L7OxGz
yqqNV/L2i3cS/POA6YsEHYRSGFPqtfsE6RhbznJJtSnkYkToN0WnWiaZBgjC4A6i
PtNBfNBkq542DuW5OU1EFA1gVpElXLQv78rQa12dAmJIs6qAyFdPaMbulyFSfC+9

Bug#1022446: marked as done (python-ldap3: FTBFS: distutils.errors.DistutilsClassError: command class must subclass Command)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 21:34:52 +
with message-id 
and subject line Bug#1022446: fixed in python-ldap3 2.9.1-2
has caused the Debian Bug report #1022446,
regarding python-ldap3: FTBFS: distutils.errors.DistutilsClassError: command 
class  must subclass Command
to be marked as done.

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

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


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

Hi,

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


Relevant part (hopefully):
>  debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:240: python3.10 setup.py clean 
> /<>/setup.py:29: DeprecationWarning: The distutils package is 
> deprecated and slated for removal in Python 3.12. Use setuptools or check PEP 
> 632 for potential alternatives
>   from distutils.command.clean import clean
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> Traceback (most recent call last):
>   File "/<>/setup.py", line 85, in 
> setup(name=package_name,
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
> 172, in setup
> ok = dist.parse_command_line()
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 474, in parse_command_line
> args = self._parse_command_opts(parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1107, in 
> _parse_command_opts
> nargs = _Distribution._parse_command_opts(self, parser, args)
>   File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
> 540, in _parse_command_opts
> raise DistutilsClassError(
> distutils.errors.DistutilsClassError: command class  
> must subclass Command
> E: pybuild pybuild:379: clean: plugin distutils failed with: exit code=1: 
> python3.10 setup.py clean 
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.10 returned 
> exit code 13
> make: *** [debian/rules:6: clean] Error 25


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-ldap3_2.9.1-1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-ldap3
Source-Version: 2.9.1-2
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated python-ldap3 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#1022446: marked as pending in python-ldap3

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/python-ldap3/-/commit/3edad31a15e0801ff7b7700605b506db680e2a57


Patch: Support setuptools >= 60. (Closes: #1022446)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1022446

Processed: Bug#1022446 marked as pending in python-ldap3

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1022446 [src:python-ldap3] python-ldap3: FTBFS: 
distutils.errors.DistutilsClassError: command class  
must subclass Command
Added tag(s) pending.

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

Processed: reassign 1023799 to wnpp, tagging 1022881, fixed 1022881 in 4.18.0-1, tagging 1023868 ...

[Debian Bug Tracking System]

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

> reassign 1023799 wnpp
Bug #1023799 {Done: Ludovico de Nittis } 
[desync] RFP: desync -- Data Synchronization Tool
Warning: Unknown package 'desync'
Bug reassigned from package 'desync' to 'wnpp'.
Ignoring request to alter found versions of bug #1023799 to the same values 
previously set
Ignoring request to alter fixed versions of bug #1023799 to the same values 
previously set
> tags 1022881 - bullseye
Bug #1022881 [src:swt4-gtk] swt4-gtk FTBFS due to default encoding
Removed tag(s) bullseye.
> fixed 1022881 4.18.0-1
Bug #1022881 [src:swt4-gtk] swt4-gtk FTBFS due to default encoding
Marked as fixed in versions swt4-gtk/4.18.0-1.
> tags 1023868 + sid bookworm
Bug #1023868 [caja-seahorse] caja-seahorse: FTBFS against libgpgme-dev >= 
1.18.0-2 [checking for gpgme-config... failed]
Added tag(s) sid and bookworm.
> found 1021779 3.0.15-2
Bug #1021779 [libical3] orage: eats events
Marked as found in versions libical3/3.0.15-2.
> fixed 1021779 3.0.16-1
Bug #1021779 [libical3] orage: eats events
Marked as fixed in versions libical3/3.0.16-1.
> tags 631280 + sid bookworm
Bug #631280 [libphp-jpgraph] libphp-jpgraph: uses deprecated PHP functions
Added tag(s) bookworm and sid.
> tags 996490 + sid bookworm
Bug #996490 {Done: Sebastian Ramacher } 
[audacious-plugins] audacious-plugins: cannot install last binNMU 4.0.5-1+b1
Added tag(s) sid and bookworm.
> tags 1015783 + sid bookworm
Bug #1015783 {Done: Gordon Ball } [jupyter-notebook] 
Please update jupyter-notebook to 6.4.12
Added tag(s) bookworm and sid.
> tags 1019749 + experimental
Bug #1019749 {Done: Salvatore Bonaccorso } [src:linux] linux 
autopkg tests fail with stderr output, blocking gcc-11
Bug #1020441 {Done: Salvatore Bonaccorso } [src:linux] 
linux: autopkgtest needs update for new version of gcc-11
Added tag(s) experimental.
Added tag(s) experimental.
> fixed 1020894 2.36-2
Bug #1020894 {Done: Aurelien Jarno } [src:glibc] glibc: 
Firefox 88 broken after glibc upgrade
Marked as fixed in versions glibc/2.36-2.
> notfixed 868084 8.20201127
Bug #868084 {Done: Joey Hess } [git-annex] git-annex: 
adjusted-unlocked mode but different
There is no source info for the package 'git-annex' at version '8.20201127' 
with architecture ''
Unable to make a source version for version '8.20201127'
No longer marked as fixed in versions 8.20201127.
> fixed 868084 8.20201127-1
Bug #868084 {Done: Joey Hess } [git-annex] git-annex: 
adjusted-unlocked mode but different
Marked as fixed in versions git-annex/8.20201127-1.
> tags 1020906 + sid bookworm
Bug #1020906 {Done: Salvatore Bonaccorso } [src:libpod] 
libpod: CVE-2022-27649
Added tag(s) bookworm and sid.
> tags 1020907 + sid bookworm
Bug #1020907 {Done: Salvatore Bonaccorso } 
[src:golang-github-containers-psgo] golang-github-containers-psgo: CVE-2022-1227
Added tag(s) sid and bookworm.
> tags 990987 + sid bullseye
Bug #990987 {Done: Bastian Germann } [src:cfengine3] cfengine3 
memory leak(s)
Added tag(s) bullseye and sid.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1015783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015783
1019749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019749
1020441: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020441
1020894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020894
1020906: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020906
1020907: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020907
1021779: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021779
1022881: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022881
1023799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023799
1023868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023868
631280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631280
868084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868084
990987: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990987
996490: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996490
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#1023874: node-readable-stream: FTBFS: Cannot use import statement outside a module

[Andreas Beckmann]

Source: node-readable-stream
Version: 4.1.0+~cs9.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source

Hi,

node-readable-stream/experimental recently started to FTBFS, probably
because some build-dependency became more strict. The version in sid is
not affected.

...
   dh_auto_build --buildsystem=nodejs
Found debian/nodejs/abort-controller/build
cd ./abort-controller && sh -ex ../debian/nodejs/abort-controller/build
+ rollup -c
(node:4756) Warning: To load an ES module, set "type": "module" in the 
package.json or use the .mjs extension.
(Use `node --trace-warnings ...` to show where the warning was created)
ESC[1mESC[31m[!] ESC[1mRollupError: Node tried to load your configuration file 
as CommonJS even though it is likely an ES module. To resolve this, change the 
extension of your configuration to ".mjs", set "type": "module" in your 
package.json file or pass the "--bundleConfigAsCjs" flag.

Original error: Cannot use import statement outside a 
moduleESC[22mESC[1mESC[39mESC[22m
ESC[36mhttps://rollupjs.org/guide/en/#--bundleconfigascjsESC[39m
ESC[2m/build/node-readable-stream-4.1.0+~cs9.0.2/abort-controller/rollup.config.js:1
import babel from "@rollup/plugin-babel"
^^

SyntaxError: Cannot use import statement outside a module
at Object.compileFunction (node:vm:360:18)
at wrapSafe (node:internal/modules/cjs/loader:1088:15)
at Module._compile (node:internal/modules/cjs/loader:1123:27)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
at Module.load (node:internal/modules/cjs/loader:1037:32)
at Function.Module._load (node:internal/modules/cjs/loader:878:12)
at ModuleWrap. (node:internal/modules/esm/translators:169:29)
at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
at async Promise.all (index 0)
at ESMLoader.import (node:internal/modules/esm/loader:530:24)ESC[22m

dh_auto_build: error: cd ./abort-controller && sh -ex 
../debian/nodejs/abort-controller/build returned exit code 1
make: *** [debian/rules:11: binary] Error 25
...

Andreas


node-readable-stream_4.1.0+~cs9.0.2-1.log.gz
Description: application/gzip

Bug#1019812: wxhexeditor: Please transition to wxwidgets3.2

[Scott Talbert]

On Sat, 5 Nov 2022, Paul Wise wrote:


Control: tags -1 + fixed-upstream patch
Control: forwarded -1 
https://github.com/EUA/wxHexEditor/commit/28151fc64cb6d01a08dc80ef750d4bca96c147e7
 
https://github.com/EUA/wxHexEditor/commit/ebe2449fac22089825d124935a215fd1c0739403

On Wed, 14 Sep 2022 15:42:16 -0400 Scott Talbert wrote:


Please transition wxhexeditor from wxwidgets3.0 to wxwidgets3.2.


This causes a build failure due to WX_CLEAR_ARRAY calls not having a
terminating semicolon in the version in Debian. Fixing those makes the
package build and I have tested that the package works afterwards.
The missing semicolons are fixed in the two upstream commits above.


Yep, I had prepared a pull request independently with these fixes (didn't 
check upstream, oops), but it should be ready to go:


https://salsa.debian.org/debian/wxhexeditor/-/merge_requests/2

Regards,
Scott

Bug#1020135: marked as done (numpy: FTBFS: AttributeError: 'UnixCCompiler' object has no attribute 'cxx_compiler')

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 19:19:16 +
with message-id 
and subject line Bug#1020135: fixed in numpy 1:1.21.5-2
has caused the Debian Bug report #1020135,
regarding numpy: FTBFS: AttributeError: 'UnixCCompiler' object has no attribute 
'cxx_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.)


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

Hi,

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


Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> :1: DeprecationWarning: The distutils package is deprecated and 
> slated for removal in Python 3.12. Use setuptools or check PEP 632 for 
> potential alternatives
> py3versions: no X-Python3-Version in control file, using supported versions
> dh_auto_build
>   pybuild --build -i python{version} -p 3.10
> I: pybuild base:240: /usr/bin/python3 setup.py build 
> /<>/setup.py:63: RuntimeWarning: NumPy 1.21.5 may not yet 
> support Python 3.10.
>   warnings.warn(
> Running from numpy source directory.
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:18: UserWarning: 
> Distutils was imported before Setuptools, but importing Setuptools also 
> replaces the `distutils` module in `sys.modules`. This may lead to 
> undesirable behaviors or errors. To avoid these issues, avoid using distutils 
> directly, ensure that setuptools is installed in the traditional way (e.g. 
> not an editable install), and/or make sure that setuptools is always imported 
> before distutils.
>   warnings.warn(
> /usr/lib/python3/dist-packages/_distutils_hack/__init__.py:33: UserWarning: 
> Setuptools is replacing distutils.
>   warnings.warn("Setuptools is replacing distutils.")
> /<>/tools/cythonize.py:69: DeprecationWarning: The distutils 
> package is deprecated and slated for removal in Python 3.12. Use setuptools 
> or check PEP 632 for potential alternatives
>   from distutils.version import LooseVersion
> numpy/random/_bounded_integers.pxd.in has not changed
> numpy/random/_sfc64.pyx has not changed
> numpy/random/_philox.pyx has not changed
> numpy/random/_pcg64.pyx has not changed
> numpy/random/_bounded_integers.pyx.in has not changed
> numpy/random/_generator.pyx has not changed
> Processing numpy/random/_bounded_integers.pyx
> numpy/random/bit_generator.pyx has not changed
> numpy/random/_common.pyx has not changed
> numpy/random/mtrand.pyx has not changed
> numpy/random/_mt19937.pyx has not changed
> /<>/numpy/distutils/system_info.py:2027: UserWarning: 
> Optimized (vendor) Blas libraries are not found.
> Falls back to netlib Blas library which has worse performance.
> A better performance should be easily gained by switching
> Blas library.
>   if self._calc_info(blas):
> Warning: attempted relative import with no known parent package
> /usr/lib/python3/dist-packages/setuptools/_distutils/dist.py:262: 
> UserWarning: Unknown distribution option: 'define_macros'
>   warnings.warn(msg)
> Cythonizing sources
> non-existing path in 'numpy/distutils': 'site.cfg'
> running build
> running config_cc
> running config_fc
> running build_src
> creating build
> creating build/src.linux-x86_64-3.10
> creating build/src.linux-x86_64-3.10/numpy
> creating build/src.linux-x86_64-3.10/numpy/distutils
> x86_64-linux-gnu-gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv 
> -O2 -Wall -g -fstack-protector-strong -Wformat -Werror=format-security -g 
> -fwrapv -O2 -g -O2 -ffile-prefix-map=/<>=. 
> -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
> -D_FORTIFY_SOURCE=2 -fPIC -Inumpy/core/src/common -Inumpy/core/src 
> -Inumpy/core -Inumpy/core/src/npymath -Inumpy/core/src/multiarray 
> -Inumpy/core/src/umath -Inumpy/core/src/npysort -Inumpy/core/src/_simd 
> -I/usr/include/python3.10 -c _configtest.c -o _configtest.o
> x86_64-linux-gnu-gcc _configtest.o -o _configtest
> success!
> removing: _configtest.c _configtest.o _configtest.o.d _configtest
> Traceback (most recent call last):
>   File "/<>/setup.py", line 448, in 
> setup_package()
>   File "/<>/setup.py", line 440, in setup_package
> setup(**metadata)
>   File "/<>/numpy/distutils/core.py", line 169, in setup
> return old_setup(**new_attr)
>   File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 87, in 
> setup
> return distutils.core.setup(**attrs)
>  

Bug#1020135: marked as pending in numpy

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/numpy/-/commit/ff0524bcc8e264c1e6618e42f11d4a1b608316ef


set SETUPTOOLS_USE_DISTUTILS=stdlib to ensure compatibility with setuptools >= 
60.0.0; Thanks to Jochen Sprickerhof; Closes: #1020135


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1020135

Processed: Bug#1020135 marked as pending in numpy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1020135 [src:numpy] numpy: FTBFS: AttributeError: 'UnixCCompiler' object 
has no attribute 'cxx_compiler'
Ignoring request to alter tags of bug #1020135 to the same tags previously set

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

Bug#1022149: ktimetracker total data loss

[Adrian Bunk]

The BTS does not Cc the submitter by default, Cc added.


On Fri, Oct 21, 2022 at 07:39:30AM +0100, David Jarvie wrote:
> This looks of it could be the same issue as bug 1021938, which is due to a 
> regression in libical version 3.0.15.
> --
> David Jarvie
> KAlarm author, KDE developer

Bug#1023800: marked as done (fdroidserver: autopkgtest needs update for new version of git: transport 'file' not allowed)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 18:34:28 +
with message-id 
and subject line Bug#1023800: fixed in fdroidserver 2.1.1-3
has caused the Debian Bug report #1023800,
regarding fdroidserver: autopkgtest needs update for new version of git: 
transport 'file' not allowed
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.)


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

Source: fdroidserver
Version: 2.1.1-2
Severity: serious
X-Debbugs-CC: g...@packages.debian.org
Tags: sid bookworm
User: debian...@lists.debian.org
Usertags: needs-update
Control: affects -1 src:git

Dear maintainer(s),

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


   passfail
gitfrom testing1:2.38.1-1
fdroidserver   from testing2.1.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. This is due to """
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.
"""

This has a nice write up:
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html

Currently this regression is blocking the migration of git to testing 
[1]. Of course, git shouldn't just break your autopkgtest (or even 
worse, your package), but it seems to me that the change in git was 
intended and your package needs to update to the new situation.


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


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

Paul

[0] You can see what packages were added from the second line of the log 
file quoted below. The migration software adds source package from 
unstable to the list if they are needed to install packages from 
git/1:2.38.1-1. I.e. due to versioned dependencies or breaks/conflicts.

[1] https://qa.debian.org/excuses.php?package=git

https://ci.debian.net/data/autopkgtest/testing/amd64/f/fdroidserver/28075853/log.gz

==
Test recovering from from broken git submodules
++ create_test_dir
++ test -e /tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles
++ mktemp -d 
/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.
+ 
ROOT=/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.FZCB
+ cd 
/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.FZCB

+ mkdir foo bar
+ cd foo
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git init
hint: Using 'master' as the name for the initial branch. This default 
branch name
hint: is subject to change. To configure the initial branch name to use 
in all

hint: of your new repositories, which will suppress this warning, call:
hint: hint: git config --global init.defaultBranch 
hint: hint: Names commonly chosen instead of 'master' are 'main', 
'trunk' and
hint: 'development'. The just-created branch can be renamed via this 
command:

hint: hint: git branch -m 
Initialized empty Git repository in 
/tmp/autopkgtest-lxc.7wnh4imd/downtmp/build.qNQ/src/.testfiles/run-tests.FZCB/foo/.git/

+ echo a
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git add a
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 'GIT_COMMITTER_NAME='\''Test'\''' 
'GIT_COMMITTER_EMAIL='\''no@mail'\''' git commit -m a

[master (root-commit) a0c70da] a
 1 file changed, 1 insertion(+)
 create mode 100644 a
+ cd ../bar
+ env HOME= 'GIT_AUTHOR_NAME='\''Test'\''' 
'GIT_AUTHOR_EMAIL='\''no@mail'\''' 

Bug#1017711: bug#58956: mark_object, mark_objects(?) crash

[Sean Whitton]

Hello,

On Thu 10 Nov 2022 at 11:23AM +01, Vincent Lefevre wrote:

> On 2022-11-08 12:44:08 -0700, Sean Whitton wrote:
>> Are you able to test the patch?  Let me know if you need help getting an
>> installable .deb.  Thanks.
>
> Sorry, I couldn't test it yet, first because of an uninstallable
> package needed for the build because I couldn't upgrade libc6 yet
> and I couldn't get the previous version from snapshot.debian.org
> (bug 1023540). Now that I could upgrade libc6, I'll be able to
> test when I have some time, but perhaps not before the week-end.

Okay, do let me know if I can help -- this is blocking Emacs from migrating.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it

[Vincent Lefevre]

Hi Andreas,

On 2022-11-11 18:31:40 +0100, Andreas Metzler wrote:
> We were aware that some breakage was to be expected (a little bit late,
> though), and will provide help/assistance (quoting Daniel 1023601: "this
> might cause knock-on effects for projects that themselves think they
> should be dependent on gpgme-config, but i'll try to sort those through
> as well.")
> 
> I do not think the bug severity is correct. It does not break any binary
> packages, i.e. it fits "a bug which has a major effect on the usability
> of a package, without rendering it completely unusable to everyone."

Well, for anyone that follows the official GPGME documentation, the
libgpgme-dev package (only needed to build GPGME-based software) is
unusable. Something needs to be done before the release. See below.

> One might argue that the combination of this gpgme version with
> unbuildable packages is not releaseable and up with serious.

Remember that libgpgme-dev is not just useful to build Debian
packages, but also to build software that is not part of Debian.

In any case, a decision has to be made: either consider that the
change is too early, and the next Debian release should have this file
(in this case, the RC bug is justified), or consider that it is up to
other software to be updated (or users to find a workaround), in which
case, things should at least properly documented: the GPGME manual
currently says:


2.2 Building the Source
===

If you want to compile a source file including the ‘gpgme.h’ header
file, you must make sure that the compiler can find it in the directory
hierarchy.  This is accomplished by adding the path to the directory in
which the header file is located to the compilers include file search
path (via the ‘-I’ option).

   However, the path to the include file is determined at the time the
source is configured.  To solve this problem, gpgme ships with a small
helper program ‘gpgme-config’ that knows about the path to the include
file and other configuration options.  The options that need to be added
to the compiler invocation at compile time are output by the ‘--cflags’
option to ‘gpgme-config’.  The following example shows how it can be
used at the command line:

 gcc -c foo.c `gpgme-config --cflags`

   Adding the output of ‘gpgme-config --cflags’ to the compiler command
line will ensure that the compiler can find the GPGME header file.

   A similar problem occurs when linking the program with the library.
Again, the compiler has to find the library files.  For this to work,
the path to the library files has to be added to the library search path
(via the ‘-L’ option).  For this, the option ‘--libs’ to ‘gpgme-config’
can be used.  For convenience, this option also outputs all other
options that are required to link the program with GPGME (in particular,
the ‘-lgpgme’ option).  The example shows how to link ‘foo.o’ with the
GPGME library to a program ‘foo’.

 gcc -o foo foo.o `gpgme-config --libs`

   Of course you can also combine both examples to a single command by
specifying both options to ‘gpgme-config’:

 gcc -o foo foo.c `gpgme-config --cflags --libs`

   If you need to detect the installed language bindings you can use
list them using:

 gpgme-config --print-lang

   or test for the availability using

 gpgme-config --have-lang=python && echo 'Bindings for Pythons available'


But in Debian, where gpgme-config is currently missing, this
will *not* work at all.

BTW, after all, the use of gpgrt-config might not be user-friendly
in an interactive shell (as opposed to a configure.ac file). An
alternative solution would be to consider a small gpgme-config script
that will call gpgrt-config with the right arguments. For instance,
on x86_64, I suppose that this could be

  exec gpgrt-config --libdir=/usr/lib/x86_64-linux-gnu gpgme "$@"

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

Bug#1021779: orage: eats events

[Adrian Bunk]

The BTS does not Cc the submitter by default, Cc added.


On Sun, Oct 30, 2022 at 02:21:09PM -0400, Nicolas Mora wrote:
> Hello,
> 
> On Sun, 23 Oct 2022 11:54:52 +0200 Yves-Alexis Perez 
> wrote:
> 
> > 
> > for some reason your reports never reached us so I've just seen this bug and
> > your investigation. My feeling is that this is actually
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1021698 so it might be
> > interesting to check if it's fixed with 3.0.16-1.
> > 
> 
> If the bug comes from libical, I can confirm that it has been fixed in the
> last release 3.0.16-1 which is now on testing.
> 
> Can you check with the last packages if the bug is still present?
> 
> /Nicolas

Bug#1023800: marked as pending in fdroidserver

[Jochen Sprickerhof]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/fdroidserver/-/commit/e601de50f75a099a229ff9fc754f0904af6975be


Add patch for new git behaviour

Closes: #1023800


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1023800

Processed: Bug#1023800 marked as pending in fdroidserver

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1023800 [src:fdroidserver] fdroidserver: autopkgtest needs update for new 
version of git: transport 'file' not allowed
Added tag(s) pending.

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

Bug#948244: marked as done (tracker.debian.org has off-by-one in the releases for packages not in stable)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 20:02:46 +0200
with message-id 
and subject line Re: Bug#948244: tracker.debian.org has off-by-one in the 
releases for packages not in stable
has caused the Debian Bug report #948244,
regarding tracker.debian.org has off-by-one in the releases for packages not in 
stable
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.)


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

Example:
https://tracker.debian.org/pkg/monotone-viz
versions
oldstable:  1.0.2-3
stable:  1.0.2-4
unstable:  1.0.2-4

$ rmadison -a source monotone-viz
monotone-viz | 1.0.2-3   | oldoldstable   | source
monotone-viz | 1.0.2-4   | oldstable  | source
monotone-viz | 1.0.2-4   | unstable   | source
monotone-viz | 1.0.2-4   | unstable-debug | source
$
--- End Message ---
--- Begin Message ---
On Sun, Jan 05, 2020 at 11:49:00PM +0200, Adrian Bunk wrote:
> Package: tracker.debian.org
> Severity: serious
> 
> Example:
> https://tracker.debian.org/pkg/monotone-viz
> versions
> oldstable:  1.0.2-3
> stable:  1.0.2-4
> unstable:  1.0.2-4
> 
> $ rmadison -a source monotone-viz
> monotone-viz | 1.0.2-3   | oldoldstable   | source
> monotone-viz | 1.0.2-4   | oldstable  | source
> monotone-viz | 1.0.2-4   | unstable   | source
> monotone-viz | 1.0.2-4   | unstable-debug | source
> $

It seems this has been fixed.

Example:
https://tracker.debian.org/pkg/wine-development
versions
o-o-stable: 2.0-3
oldstable: 4.2-4
unstable: 7.11~repack-2

wine-development | 1.7.29-4  | oldoldoldstable | source, amd64, i386
wine-development | 2.0-3 | oldoldstable| source, all
wine-development | 4.2-4 | oldstable   | source, all
wine-development | 7.11~repack-2 | unstable| source, all
wine-development | 7.11~repack-2 | unstable-debug  | source

cu
Adrian--- End Message ---

Bug#1023812: marked as done (git: Source package misses dependency to libssl-dev package)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 19:53:38 +0200
with message-id 
and subject line Re: Bug#1023812: git: Source package misses dependency to 
libssl-dev package
has caused the Debian Bug report #1023812,
regarding git: Source package misses dependency to libssl-dev package
to be marked as done.

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

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


-- 
1023812: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023812
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: git
Version: 1:2.30.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
X-Debbugs-Cc: doak+...@posteo.net

Dear Maintainer,

The source package of `git` seems not to specify the dependency to
`libssl-dev`.

Steps to reproduce:
Compiling Git on a Debian live CD fails. These are the steps to
reproduce:
# apt build-dep git
git$ make

Make complains about missing OpenSSL header. Installing `libssl-dev`
fixes this.

Expected:
I would that after installing build dependencies for Git, it is built
successfully.


Best regards,
doak



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

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

Versions of packages git depends on:
ii  git-man  1:2.30.2-1
ii  libc62.31-13+deb11u4
ii  libcurl3-gnutls  7.74.0-1.3+deb11u3
ii  liberror-perl0.17029-1
ii  libexpat12.2.10-2+deb11u3
ii  libpcre2-8-0 10.36-2+deb11u1
ii  perl 5.32.1-4+deb11u2
ii  zlib1g   1:1.2.11.dfsg-2+deb11u2

Versions of packages git recommends:
ii  ca-certificates  20210119
ii  less 551-2
ii  openssh-client [ssh-client]  1:8.4p1-5+deb11u1
ii  patch2.7.6-7

Versions of packages git suggests:
ii  gettext-base  0.21-4
pn  git-cvs   
pn  git-daemon-run | git-daemon-sysvinit  
pn  git-doc   
pn  git-el
pn  git-email 
pn  git-gui   
pn  git-mediawiki 
pn  git-svn   
pn  gitk  
pn  gitweb

-- no debconf information
--- End Message ---
--- Begin Message ---
On Thu, Nov 10, 2022 at 01:57:55PM +, doak wrote:
>...
> The source package of `git` seems not to specify the dependency to
> `libssl-dev`.
> 
> Steps to reproduce:
> Compiling Git on a Debian live CD fails. These are the steps to
> reproduce:
>   # apt build-dep git
>   git$ make
> 
> Make complains about missing OpenSSL header. Installing `libssl-dev`
> fixes this.
> 
> Expected:
> I would that after installing build dependencies for Git, it is built
> successfully.

The build dependencies are for building the package the way the package 
build is defined in debian/rules, building a package manually might or
might not work.

In this case, debian/rules contains "OPTS =NO_OPENSSL=1".

> Best regards,
> doak

cu
Adrian--- End Message ---

Bug#1023868: caja-seahorse: FTBFS against libgpgme-dev >= 1.18.0-2 [checking for gpgme-config... failed]

[Andreas Metzler]

Package: caja-seahorse
Version: 1.18.5-1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source (but built successfully in the past)

Hello,

caja-seahorse FTBFS due to removal of gpgme-config. Since caja-seahorse
already requires pkgconfig you can simply use this for gpgme, too.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
diff -Nru caja-seahorse-1.18.5/debian/changelog caja-seahorse-1.18.5/debian/changelog
--- caja-seahorse-1.18.5/debian/changelog	2020-08-24 10:00:41.0 +0200
+++ caja-seahorse-1.18.5/debian/changelog	2022-11-11 18:45:09.0 +0100
@@ -1,3 +1,11 @@
+caja-seahorse (1.18.5-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * 1010_gpgme_pkgconfig.diff: Use pkgconfig to locate gpgme instead of
+gpgme-config fixing FTBFS with libgpgme-dev >= 1.18.0-2.
+
+ -- Andreas Metzler   Fri, 11 Nov 2022 18:45:09 +0100
+
 caja-seahorse (1.18.5-1) unstable; urgency=medium
 
   [ Simon Quigley ]
diff -Nru caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff
--- caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff	1970-01-01 01:00:00.0 +0100
+++ caja-seahorse-1.18.5/debian/patches/1010_gpgme_pkgconfig.diff	2022-11-11 18:45:09.0 +0100
@@ -0,0 +1,54 @@
+Description: Use pkgconfig to locate gpgme instead of gpgme-config.
+Author: Andreas Metzler 
+Origin: vendor
+Last-Update: 2022-11-11
+
+--- a/configure.ac
 b/configure.ac
+@@ -85,45 +85,11 @@
+ 	else
+ 		AC_MSG_ERROR([Appropriate version of GnuPG not found. Please install one of versions: $accepted_versions])
+ 	fi
+ fi
+ 
+-ok="no"
+-min_gpgme_version=1.0.0
+-AC_PATH_PROG(GPGME_CONFIG, gpgme-config, "failed")
+-if test $GPGME_CONFIG != "failed" ; then
+-	AC_MSG_CHECKING(for GPGME - version >= $min_gpgme_version)
+-	req_major=`echo $min_gpgme_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\1/'`
+-	req_minor=`echo $min_gpgme_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\2/'`
+-	req_micro=`echo $min_gpgme_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\)/\3/'`
+-	gpgme_config_version=`$GPGME_CONFIG --version`
+-	major=`echo $gpgme_config_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\1/'`
+-	minor=`echo $gpgme_config_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\2/'`
+-	micro=`echo $gpgme_config_version | \
+-		sed 's/\([[0-9]]*\)\.\([[0-9]]*\)\.\([[0-9]]*\).*/\3/'`
+-
+-	if test "$major" -eq "$req_major"; then
+-		if test "$minor" -ge "$req_minor"; then
+-			if test "$micro" -ge "$req_micro"; then
+-ok="yes"
+-			fi
+-		fi
+-	fi
+-fi
+-
+-if test $ok = "yes"; then
+-	GPGME_CFLAGS=`$GPGME_CONFIG --cflags`
+-	GPGME_LIBS=`$GPGME_CONFIG --libs`
+-	AC_MSG_RESULT(yes)
+-else
+-	AC_MSG_ERROR(GPGME $min_gpgme_version or later needed)
+-fi
++PKG_CHECK_MODULES([GPGME], [gpgme >= 1.0.0])
+ 
+ SEAHORSE_CFLAGS="$SEAHORSE_CFLAGS $GPGME_CFLAGS"
+ SEAHORSE_LIBS="$SEAHORSE_LIBS $GPGME_LIBS"
+ 
+ # -
diff -Nru caja-seahorse-1.18.5/debian/patches/series caja-seahorse-1.18.5/debian/patches/series
--- caja-seahorse-1.18.5/debian/patches/series	1970-01-01 01:00:00.0 +0100
+++ caja-seahorse-1.18.5/debian/patches/series	2022-11-11 18:43:29.0 +0100
@@ -0,0 +1 @@
+1010_gpgme_pkgconfig.diff

Processed: tagging 1018739

[Debian Bug Tracking System]

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

> tags 1018739 + fixed
Bug #1018739 {Done: Paul Gevers } [src:libowfat] 
src:libowfat: fails to migrate to testing for too long: FTBFS
Added tag(s) fixed.
> thanks
Stopping processing here.

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

Bug#1023848: kodi-pvr-hts: Packet requires kodi-api-pvr but is not available in sid

[Vasyl Gello]

Hi Leela,

To resolve this I will need to upload src:kodi once more to fix an overlooked 
issue breaking builds on non-x86 platforms and then, after it gets built for 
all arches, upload the addons again. Mattia might help me early next week with 
it, because my status (Debian Contributor) does not allow me uploading packages 
directly.
-- 
Vasyl Gello
==
Certified SolidWorks Expert

Mob.:+380 (98) 465 66 77

E-Mail: vasek.ge...@gmail.com
==
호랑이는 죽어서 가죽을 남기고 사람은 죽어서 이름을 남긴다

Bug#1023601: libgpgme-dev: removal of gpgme-config breaks the build of software relying on it

[Andreas Metzler]

On 2022-11-08 Vincent Lefevre  wrote:
> On 2022-11-07 13:36:30 +0100, Vincent Lefevre wrote:
> > The removal of gpgme-config due to
> > 
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348
> > 
> > breaks the build of software relying on it, such as Mutt:
[...]
> Actually gpgrt-config can be used instead of gpgme-config. But
> this requires changes in existing code, possibly non trivial,
> as now done for Mutt:

>   https://gitlab.com/muttmua/mutt/-/issues/430

> (not yet in Debian).

> So before gpgme-config gets removed (which is a *recent* upstream
> change), you should make sure that existing code based on it has
> been updated.

Hello Vincent,

Disclaimer: I am not in uploaders of gpg packaging but follow the list.

We were aware that some breakage was to be expected (a little bit late,
though), and will provide help/assistance (quoting Daniel 1023601: "this
might cause knock-on effects for projects that themselves think they
should be dependent on gpgme-config, but i'll try to sort those through
as well.")

I do not think the bug severity is correct. It does not break any binary
packages, i.e. it fits "a bug which has a major effect on the usability
of a package, without rendering it completely unusable to everyone." One
might argue that the combination of this gpgme version with unbuildable
packages is not releaseable and up with serious.

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

Bug#1005447: marked as done (ola: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 17:05:18 +
with message-id 
and subject line Bug#1005447: fixed in ola 0.10.8.nojsmin.git1b28e794-1
has caused the Debian Bug report #1005447,
regarding ola: FTBFS: dh_auto_test: error: make -j4 check 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.)


-- 
1005447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ola
Version: 0.10.8.nojsmin-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220212 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> make[5]: Entering directory '/<>'
> PASS: common/base/FlagsTester
> PASS: common/base/LoggingTester
> PASS: common/base/CredentialsTester
> PASS: common/dmx/RunLengthEncoderTester
> PASS: common/file/UtilTester
> PASS: common/export_map/ExportMapTester
> PASS: common/io/DescriptorTester
> PASS: common/io/IOQueueTester
> PASS: common/io/IOStackTester
> PASS: common/io/MemoryBlockTester
> PASS: common/io/StreamTester
> PASS: common/io/TimeoutManagerTester
> PASS: common/messaging/DescriptorTester
> PASS: common/network/NetworkTester
> PASS: common/rdm/DiscoveryAgentTester
> PASS: common/rdm/PidStoreTester
> PASS: common/rdm/QueueingRDMControllerTester
> PASS: common/rdm/RDMAPITester
> PASS: common/rdm/RDMCommandSerializerTester
> PASS: common/rdm/RDMCommandTester
> PASS: common/rdm/RDMFrameTester
> PASS: common/rdm/RDMHelperTester
> PASS: common/rdm/RDMMessageTester
> PASS: common/rdm/RDMReplyTester
> PASS: common/rdm/UIDAllocatorTester
> PASS: common/rdm/UIDTester
> PASS: common/rpc/RpcTester
> PASS: common/rpc/RpcServerTester
> PASS: common/strings/UtilsTester
> PASS: common/thread/ExecutorThreadTester
> PASS: common/thread/ThreadTester
> PASS: common/thread/FutureTester
> PASS: common/timecode/TimeCodeTester
> PASS: common/network/TCPConnectorTester
> PASS: common/web/JsonTester
> PASS: common/web/ParserTester
> PASS: common/web/PtchParserTester
> PASS: common/web/PtchTester
> PASS: common/web/PointerTester
> PASS: common/web/PointerTrackerTester
> PASS: common/web/SchemaParserTester
> PASS: common/web/SchemaTester
> PASS: common/web/SectionsTester
> PASS: data/rdm/PidDataTester
> PASS: libs/acn/E131Tester
> PASS: libs/acn/E133Tester
> PASS: libs/acn/TransportTester
> FAIL: libs/usb/LibUsbThreadTester
> FAIL: ola/OlaClientTester
> PASS: olad/plugin_api/ClientTester
> PASS: olad/plugin_api/DeviceTester
> PASS: olad/plugin_api/DmxSourceTester
> PASS: olad/plugin_api/PortTester
> PASS: olad/plugin_api/PreferencesTester
> PASS: olad/plugin_api/UniverseTester
> PASS: plugins/artnet/ArtNetTester
> PASS: plugins/dummy/DummyPluginTester
> PASS: plugins/espnet/EspNetTester
> PASS: plugins/kinet/KiNetTester
> PASS: plugins/openpixelcontrol/OPCClientTester
> PASS: plugins/openpixelcontrol/OPCServerTester
> PASS: plugins/osc/OSCTester
> PASS: plugins/shownet/ShowNetTester
> PASS: plugins/spi/SPITester
> PASS: plugins/usbpro/ArduinoWidgetTester
> PASS: plugins/usbpro/BaseRobeWidgetTester
> PASS: plugins/usbpro/BaseUsbProWidgetTester
> PASS: common/network/HealthCheckedConnectionTester
> PASS: plugins/usbpro/DmxterWidgetTester
> PASS: common/io/SelectServerTester
> PASS: plugins/usbpro/RobeWidgetDetectorTester
> PASS: plugins/usbpro/EnttecUsbProWidgetTester
> PASS: plugins/usbpro/RobeWidgetTester
> PASS: plugins/usbpro/UltraDMXProWidgetTester
> PASS: plugins/usbpro/UsbProWidgetDetectorTester
> PASS: olad/OlaTester
> PASS: tools/ola_trigger/ActionTester
> echo "PYTHONPATH=./python PIDDATA=./data/rdm /usr/bin/python3 
> ./data/rdm/PidDataTest.py; exit \$?" > data/rdm/PidDataTest.sh
> chmod +x data/rdm/PidDataTest.sh
> echo "for FILE in ./examples/testdata/dos_line_endings 
> ./examples/testdata/multiple_unis ./examples/testdata/partial_frames 
> ./examples/testdata/single_uni ./examples/testdata/trailing_timeout; do echo 
> \"Checking \$FILE\"; ./examples/ola_recorder --verify \$FILE; STATUS=\$?; if 
> [ \$STATUS -ne 0 ]; then echo \"FAIL: \$FILE caused ola_recorder to exit with 
> status \$STATUS\"; exit \$STATUS; fi; done; exit 0" > 
> examples/RecorderVerifyTest.sh
> chmod +x examples/RecorderVerifyTest.sh
> mkdir -p ./python/ola/rpc
> echo "PYTHONPATH=./python /usr/bin/python3 
> ./python/ola/rpc/SimpleRpcControllerTest.py; exit \$?" > 
> ./python/ola/rpc/SimpleRpcControllerTest.sh
> chmod +x ./python/ola/rpc/SimpleRpcControllerTest.sh
> PASS: python/ola/DUBDecoderTest.py
> mkdir -p 

Bug#1022308:

[Gard Spreemann]

Hi,

I have verified that adding libglu1-mesa-dev to the build-deps makes the
package again build successfully.


 -- Gard
 


signature.asc
Description: PGP signature

Bug#1023835: marked as done (wolfssl: FTBFS because of amd64-only symbols in symbols file)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 16:47:21 +
with message-id 
and subject line Bug#1023835: fixed in wolfssl 5.5.3-3
has caused the Debian Bug report #1023835,
regarding wolfssl: FTBFS because of amd64-only symbols in symbols file
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.)


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

Source: wolfssl
Version: 5.5.3-1
Severity: serious
Tags: ftbfs

The build fails because of

--- debian/libwolfssl35.symbols (libwolfssl35_5.5.3-2_armhf)
+++ dpkg-gensymbolsjJzBRh   2022-11-10 20:32:48.418173057 +
@@ -48,9 +48,9 @@
  WOLFSSL_ERROR_LINE@Base 5.2.0
  WOLFSSL_ERROR_MSG@Base 5.2.0
  WOLFSSL_EVP_CIPHER_mode@Base 5.2.0
- cpuid_clear_flag@Base 5.5.3
- cpuid_select_flags@Base 5.5.3
- cpuid_set_flag@Base 5.5.3
+#MISSING: 5.5.3-2# cpuid_clear_flag@Base 5.5.3
+#MISSING: 5.5.3-2# cpuid_select_flags@Base 5.5.3
+#MISSING: 5.5.3-2# cpuid_set_flag@Base 5.5.3
  get_digit@Base 5.2.0
  get_digit_count@Base 5.2.0
  get_rand_digit@Base 5.2.0

Please keep the three symbols out of the symbols file or make them optional.
--- End Message ---
--- Begin Message ---
Source: wolfssl
Source-Version: 5.5.3-3
Done: Felix Lechner 

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

Debian distribution maintenance software
pp.
Felix Lechner  (supplier of updated wolfssl package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Nov 2022 06:40:00 -0800
Source: wolfssl
Architecture: source
Version: 5.5.3-3
Distribution: unstable
Urgency: medium
Maintainer: Jacob Barthelmeh 
Changed-By: Felix Lechner 
Closes: 1023835
Changes:
 wolfssl (5.5.3-3) unstable; urgency=medium
 .
   * Mark all three cpuid_* symbols as "optional" per dpkg-gensymbols(1).
 Thanks to Bastian Germann for the suggestion. (Closes: #1023835)
Checksums-Sha1:
 ae63631e7329ba107762785ddbd39d11babc574c 2343 wolfssl_5.5.3-3.dsc
 7af4f4a9a25762e0dc23a3796491ed234c87b781 31572 wolfssl_5.5.3-3.debian.tar.xz
 e442b3382bc4e125911c27eb72ccd4b55ed0a53b 5852 wolfssl_5.5.3-3_source.buildinfo
Checksums-Sha256:
 d34af134fc8853ffc7f967e3d2578445dbb5ccd2c20c656ba74fa859e8868c15 2343 
wolfssl_5.5.3-3.dsc
 887c8bfd46b25c6b72fb881f4f66915444a433833bac4d9c95541e66d7659d78 31572 
wolfssl_5.5.3-3.debian.tar.xz
 18746cfbb5a6ff70de940711e846359e31998ffb3f14e470eca84a465048f4bc 5852 
wolfssl_5.5.3-3_source.buildinfo
Files:
 fa53adb271016d2b20d392f1c8884cf5 2343 libs optional wolfssl_5.5.3-3.dsc
 40da3c1f267854ee313ded5fb098167e 31572 libs optional 
wolfssl_5.5.3-3.debian.tar.xz
 f3f751a1f12cd8a628e786c98bf7efbb 5852 libs optional 
wolfssl_5.5.3-3_source.buildinfo

-BEGIN PGP SIGNATURE-

iQKvBAEBCgCZFiEE8E0cIgLi+g0BiFTarFipTxFhjuAFAmNudwJfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEYw
NEQxQzIyMDJFMkZBMEQwMTg4NTREQUFDNThBOTRGMTE2MThFRTAbHGZlbGl4Lmxl
Y2huZXJAbGVhc2UtdXAuY29tAAoJEKxYqU8RYY7g8A4QANDE9W2MCrE3baCmpBjB
5Fs7ki0LWWFNGQgy8J5y4gFr/pZ87I8C+B3wfVIZLND7crlD4JX+MDCeWxQzBDvP
fW6uC2g3ifeILTGAFN25IXzNlj3uM3RXaWGuiwUdMgc9c3xvIyY8QbxibIT6Hya2
coOCqNN6gV0kx50OtXsd0ac9oDAKpal4Il4vDzcf5hUGXjpmNAP3dB4y3xLwuxZ3
tSuYg/AdL7W/mlmuyWeBN2f4ujXbPjN2i08IqH8vy6gJXRMaJ/xHAbt1AxzIW9dL
GP2NP/4xnnTvaDbB3rnRKL/dUJwFjoeNmLQUPLGxx+6i+pJu2DfmU+Gsbm8JgSDk
NwaIXSIDHjRm2eQWyFV/3dj2UENgFJ1HLOiuqr18fHdIP3Jcwjzu7Cef8xRRe3kj
r3B4wpufW96ydRhDkE9D7zpoEscv85CYvQp1cRy4U7ZYzLic2mafN+DAe3WbjwaJ
1sJfWirII45yU9wcjFhPvTGBJJL6hSkOJTKp68NEvmBm9i9tYZnmwhOIVQzmUCUg
E+cr7Mj4D61R9incZH4xcF5Lvz4T72JV7n7b9yAdiayGx7yubnI5cYz4rG1AYxs/
x3Qm+ctM4kcoHxtQ4n5zcewtcGSsllcqO5R+YdXSM/ZSjB8ziQAtFwDVAh21jMXw
QW9f/UAdOFbBPglb87LqtaHg
=NjRu
-END PGP SIGNATURE End Message ---

Bug#1023842: rust-criterion - inconsistent dependencies on cast.

[Jonas Smedegaard]

Quoting Peter Green (2022-11-11 09:04:34)
> The rust-criterion package has inconsistent dependencies on the cast
> crate, the dependency in the main Cargo.toml is on version 0.3, but
> the dependencies in the debian packaging and in the embedded copy of
> the criterion-plot crate are at 0.2
> 
> I have updated the cast crate in Debian to 0.3, and prepared an update
> for the rust-criterion package to use 0.3 consistently. I tested that
> the package built succesfully and the autopkgtests passed with these
> changes.

Thanks!

I am now applying main parts of your proposed patch to the git repo
(only locally for now - will push when I have it in working shape).

I also extended the embedded patch  to the full original upstream
patch (turns out all of it is relevant for us), and adjusted to properly
use DEP-3 patch headers (helpful that you referenced upstream patch, but
for future sake beware especially to properly credit the author: You are
at most co-author when cherry-picking patched done by others, and in
most cases only reviewer).

My work on other packages (rust-test-case) recently revealed that my
approach to embedding crates is broken, so I will do some more poking to
get it to not only succeed building on its own but also builds as
dependency of other Rust crates.


> While working on the fix, I discovered the clean target wasn't
> cleaning up properly, so I fixed it to do so.

I have left that part out for now, as that sounds like a general flaw in
dh-cargo that I will try identify and fix (instead of papering over it).
Thanks for pointing it out!


 - Jonas

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

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

signature.asc
Description: signature

Bug#965786: pppoeconf: Removal of obsolete debhelper compat 5 and 6 in bookworm

[Michael Prokop]

* Niels Thykier [Mon Jul 20, 2020 at 07:35:34PM +]:
> Source: pppoeconf
> Version: 1.21
> Severity: normal
> Usertags: compat-5-6-removal
> 
> The package pppoeconf uses debhelper with a compat level of 5 or 6,
> which is deprecated and scheduled for removal[1].
[...]

This bug is still present and caused the package to be removed from
testing. Gregory, can you please take of this, so pppoeconf has the
chance to be present in the upcoming bookworm release?

regards
-mika-


signature.asc
Description: PGP signature

Bug#1023758: marked as done (pipewire: calls addgroup without an adduser dependency)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 15:33:37 +
with message-id 
and subject line Bug#1023758: fixed in pipewire 0.3.60-1
has caused the Debian Bug report #1023758,
regarding pipewire: calls addgroup without an adduser 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.)


-- 
1023758: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023758
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pipewire
Version: 0.3.59-1
Severity: serious
Justification: Policy §3.5

pipewire calls addgroup without a dependency on the adduser package,
which can fail if no other package happens to have pulled in adduser.
Until recently, apt hid this bug by depending on adduser, but now the
base-passwd package creates the _apt user and it is entirely feasible to
remove or not install adduser in container environments.

Various packages that are in pipewire's transitive Recommends or otherwise
normally installed on desktop-class systems (like dbus-system-bus-common
and polkitd) will normally also pull in adduser, again hiding this
bug, but polkit now depends on "adduser | systemd-sysusers", and I'm
considering doing the same in dbus-system-bus-common.

To reproduce:

$ podman run --pull=always --rm -it debian:sid-slim
# apt update
# apt upgrade
# apt purge adduser
# apt install --no-install-recommends pipewire

(Or use your favourite minimal container or chroot technology, if not
podman.)

Expected result: successful installation. (It's OK if pipewire is only
partially functional without its Recommends.)

Actual result:

> Setting up pipewire:amd64 (0.3.59-1+b1) ...
> /var/lib/dpkg/info/pipewire:amd64.postinst: 7: addgroup: not found

Options for resolving this include:

1. depend on adduser

2. depend on passwd instead, and use groupadd, like samba does:
   
https://salsa.debian.org/samba-team/samba/-/commit/1eb07efc2fb4d9ed1218e4af367539bcae255b9e
   (note that passwd is Priority: required but not Essential: yes, so it
   gets installed by debootstrap but technically still needs a dependency)

3. install /usr/lib/sysusers.d/pipewire.conf containing something like:

   g pipewire - -

   then use dh_installsysusers (debhelper compat level 14 or
   dh --with=installsysusers), but be prepared to get bug reports similar
   to #1014805, #1016006 from sysvinit users who are upset that debhelper
   has generated a dependency on "systemd | ..."

4. install /usr/lib/sysusers.d/pipewire.conf as above, but do not use
   dh_installsysusers, and instead set up the user from handwritten
   postinst code using systemd-sysusers, adduser and/or groupadd
   (with an appropriate dependency)

I don't think there is yet project consensus on which one of those is best,
unfortunately.

smcv
--- End Message ---
--- Begin Message ---
Source: pipewire
Source-Version: 0.3.60-1
Done: Dylan Aïssi 

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

Debian distribution maintenance software
pp.
Dylan Aïssi  (supplier of updated pipewire package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Nov 2022 14:55:34 +0100
Source: pipewire
Architecture: source
Version: 0.3.60-1
Distribution: unstable
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Dylan Aïssi 
Closes: 1013276 1021179 1023504 1023758
Changes:
 pipewire (0.3.60-1) unstable; urgency=medium
 .
   * New upstream release
   - Improve support of RealTek ALC4080 (Closes: #1021179)
   * Cherry-pick upstream recommended patch:
   - b720da77: pulse-server: also advance read pointer in underrun
   * Add libopus-dev in Build-Deps
   * Add liblc3-dev in Build-Deps
   * Be sure the build option for bluez5 aptx codec is enabled
   * pipewire-pulse: add pulseaudio-utils in Recommends instead
   of Suggests (LP: #1993358)
   * pipewire-alsa: install conf files in the right location
   (Closes: #1023504, LP: #1975823)
   * pipewire-alsa: conflict with pulseaudio. (Closes: #1013276)
   As long as the pulseaudio package is installed, ALSA clients will output
 

Bug#1023709: marked as done (pkwalify: autopkgtest regression: t/pkwalify.t Failed: 22)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 15:34:00 +
with message-id 
and subject line Bug#1023709: fixed in pkwalify 1.23-3
has caused the Debian Bug report #1023709,
regarding pkwalify: autopkgtest regression: t/pkwalify.t Failed: 22
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.)


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

Source: pkwalify
Version: 1.23-2
Severity: serious
X-Debbugs-CC: jel...@debian.org
User: debian...@lists.debian.org
Usertags: regression

Dear maintainer(s),

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


   passfail
pkwalify   from testing1.23-2
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can 
you please investigate the situation and fix it?


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

Paul

[1] https://qa.debian.org/excuses.php?package=pkwalify

https://ci.debian.net/data/autopkgtest/testing/amd64/p/pkwalify/27088725/log.gz

t/Kwalify.t .. 1..100
ok 1 - use Kwalify;
ok 2 - use Schema::Kwalify;
ok 3 - sequence of str
ok 4 - sequence with default type (str)
ok 5 - Non valid data, int in sequence of str
ok 6
ok 7 - mapping
ok 8 - invalid mapping
ok 9
ok 10
ok 11
ok 12 - sequence of mapping
ok 13
ok 14
ok 15
ok 16
ok 17 - mapping of sequence
ok 18
ok 19
ok 20
ok 21 - Many rules
ok 22
ok 23
ok 24
ok 25
ok 26
ok 27
ok 28
ok 29
ok 30
ok 31
ok 32
ok 33 - unique
ok 34
ok 35
ok 36
ok 37
ok 38
ok 39 - valid data against schema with recursive rules (no endless loop)
ok 40 - valid recursive data against schema with recursive rules (no 
endless loop)

ok 41 - valid data against perl schema
ok 42 - invalid data against perl schema
ok 43 - min-ex length pass
ok 44 - min-ex length fail
ok 45 - max-ex length pass
ok 46 - max-ex length fail
ok 47 - min-ex range pass
ok 48 - min-ex range fail
ok 49 - max-ex range pass
ok 50 - max-ex range fail
ok 51 - max length pass
ok 52 - max length fail
ok 53 - max range pass
ok 54 - max range fail
ok 55 - Passing name/classname/desc
ok 56 - Passing name/class/desc
ok 57 - a ref is not a text
ok 58 - undef is not a text
ok 59 - a str is not a text
ok 60 - undef is not a str
ok 61 - a number is not a str
ok 62 - a non-float
ok 63 - a non-number
ok 64 - a non-bool
ok 65 - validate '0' as bool
ok 66 - validate '1' as bool
ok 67 - validate 'yes' as bool
ok 68 - validate 'no' as bool
ok 69 - validate 'true' as bool
ok 70 - validate 'false' as bool
ok 71 - validate float
ok 72 - validate number
ok 73 - validate time
ok 74 - schema must be hash
ok 75 - unknown type
ok 76 - invalid length spec
ok 77 - invalid enum spec
ok 78 - invalid range spec
ok 79 - unknown key in type
ok 80 - unknown key in range
ok 81 - unknown key in length
ok 82 - expected hash in data
ok 83 - wrong seq in schema
ok 84 - wrong seq in schema
ok 85 - wrong seq in schema
ok 86 - wrong data, no sequence
ok 87 - wrong map in schema
ok 88 - wrong map in schema
ok 89 - wrong data, undefined
ok 90 - wrong data, no mapping
ok 91 - An object of class 'Schema::Kwalify' isa 'Schema::Kwalify'
ok 92 - Simple Schema::Kwalify validation
ok 93 - Simple Schema::Kwalify failure
ok 94 - type any with additional check, successful
ok 95 - type any with additional check, failure
ok 96 - enum with defined value
ok 97 - enum with undefined value
ok 98 - legally undefined pattern
ok 99 - legally undefined pattern
ok 100 - No warnings expected
ok
t/compat.t ... 1..2
# Running under perl version 5.034000 for linux
# Current time local: Fri Oct 14 22:02:12 2022
# Current time GMT:   Fri Oct 14 22:02:12 2022
# Using Test.pm version 1.31
ok 1
ok 2
ok
t/pkwalify.t . 1..31
not ok 1 - There are warnings in -f 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/schema05.yaml 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/document05a.yaml


#   Failed test 'There are warnings in -f 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/schema05.yaml 
/tmp/autopkgtest-lxc.ns43i5rp/downtmp/autopkgtest_tmp/smokex78hlS/t/testdata/document05a.yaml'

#   at t/pkwalify.t line 119.
# 

Bug#1013516: marked as done (libcvd: FTBFS: cvd_src/videofilebuffer2.cc:272:33: error: ‘av_register_all’ was not declared in this scope)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 15:24:00 +
with message-id 
and subject line Bug#1013516: fixed in libcvd 
0.0~git20221020150751.30e8cfc+ds1-1
has caused the Debian Bug report #1013516,
regarding libcvd: FTBFS: cvd_src/videofilebuffer2.cc:272:33: error: 
‘av_register_all’ was not declared in this scope
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.)


-- 
1013516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libcvd
Version: 0.0~git20220106103934.34d8e26+ds1-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20220624 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> g++  -I. -I. -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 
> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat 
> -Werror=format-security -Wall -Wextra -Wconversion -pipe -ggdb -fPIC -mmmx 
> -msse -msse -msse2 -msse3 -c cvd_src/tensor_voting.cc -o 
> cvd_src/tensor_voting.o -MMD -MP -MF cvd_src/tensor_voting.d
> cvd_src/videofilebuffer2.cc: In constructor 
> ‘CVD::VFB::RawVideoFileBufferPIMPL::RawVideoFileBufferPIMPL(const string&, 
> const string&, bool, bool, const std::map, 
> std::__cxx11::basic_string >&)’:
> cvd_src/videofilebuffer2.cc:272:33: error: ‘av_register_all’ was not declared 
> in this scope
>   272 | av_register_all();
>   | ^~~
> cvd_src/videofilebuffer2.cc:273:33: error: ‘avcodec_register_all’ was not 
> declared in this scope; did you mean ‘avdevice_register_all’?
>   273 | avcodec_register_all();
>   | ^~~~
>   | avdevice_register_all
> cvd_src/videofilebuffer2.cc:285:67: error: invalid conversion from ‘const 
> AVInputFormat*’ to ‘AVInputFormat*’ [-fpermissive]
>   285 | fmt = 
> av_find_input_format(formatname.c_str());
>   |   
> ^~~~
>   |   |
>   |   
> const AVInputFormat*
> cvd_src/videofilebuffer2.cc:322:91: error: ‘AVStream’ {aka ‘struct AVStream’} 
> has no member named ‘codec’
>   322 | AVMediaType t = 
> input_format_context->streams[i]->codec->codec_type;
>   |   
> ^
> cvd_src/videofilebuffer2.cc:323:96: error: ‘AVStream’ {aka ‘struct AVStream’} 
> has no member named ‘codec’
>   323 | AVCodecContext* vc = 
> input_format_context->streams[i]->codec;
>   |   
>  ^
> cvd_src/videofilebuffer2.cc:342:113: error: ‘AVStream’ {aka ‘struct 
> AVStream’} has no member named ‘codec’
>   342 | 
> video_codec_context = input_format_context->streams[i]->codec;
>   |   
>   ^
> cvd_src/videofilebuffer2.cc:411:67: error: invalid conversion from ‘const 
> AVCodec*’ to ‘AVCodec*’ [-fpermissive]
>   411 | video_codec = 
> avcodec_find_decoder(video_codec_context->codec_id);
>   |   
> ^~~
>   |   |
>   |   
> const AVCodec*
> cvd_src/videofilebuffer2.cc: In member function 
> ‘std::unique_ptr 
> CVD::VFB::RawVideoFileBufferPIMPL::read_frame_from_video()’:
> cvd_src/videofilebuffer2.cc:484:47: warning: ‘void av_init_packet(AVPacket*)’ 
> is deprecated [-Wdeprecated-declarations]
>   484 | av_init_packet();
>   | ~~^
> In file included from /usr/include/x86_64-linux-gnu/libavcodec/avcodec.h:45,
>  from cvd_src/videofilebuffer2.cc:17:
> /usr/include/x86_64-linux-gnu/libavcodec/packet.h:506:6: note: declared here
>   506 | void av_init_packet(AVPacket 

Bug#1022734: marked as done (karabo-bridge: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 15:23:23 +
with message-id 
and subject line Bug#1022734: fixed in karabo-bridge 0.6.2-1
has caused the Debian Bug report #1022734,
regarding karabo-bridge: FTBFS: E: Build killed with signal TERM after 150 
minutes of inactivity
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.)


-- 
1022734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022734
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: karabo-bridge
Version: 0.6.1-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221024 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
> copying karabo_bridge/tests/test_client.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/tests
> copying karabo_bridge/tests/utils.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/tests
> creating 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/__init__.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/monitor.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/glimpse.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
> copying karabo_bridge/cli/simulation.py -> 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build/karabo_bridge/cli
>dh_auto_test -O--buildsystem=pybuild
> I: pybuild base:240: cd 
> /<>/.pybuild/cpython3_3.10_karabo-bridge/build; python3.10 -m 
> pytest 
> = test session starts 
> ==
> platform linux -- Python 3.10.7, pytest-7.1.2, pluggy-1.0.0+repack
> rootdir: /<>
> collected 31 items
> 
> karabo_bridge/tests/test_client.py 
> E: Build killed with signal TERM after 150 minutes of inactivity


The full build log is available from:
http://qa-logs.debian.net/2022/10/24/karabo-bridge_0.6.1-3_unstable.log

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

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

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

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

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

Debian distribution maintenance software
pp.
Roland Mas  (supplier of updated karabo-bridge package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Nov 2022 14:59:18 +0100
Source: karabo-bridge
Architecture: source
Version: 0.6.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team 
Changed-By: Roland Mas 
Closes: 1022734
Changes:
 karabo-bridge (0.6.2-1) unstable; urgency=medium
 .
   * New upstream release that happens to fix the testsuite.
   * Bug fix: "FTBFS: E: Build killed with signal TERM after 150 minutes of
 inactivity", thanks to Lucas Nussbaum (Closes: #1022734).
Checksums-Sha1:
 92d76413a8b37e7ba3d0dd4a2582ef8b1f14e3dd 2155 karabo-bridge_0.6.2-1.dsc
 7d2484414907cad3d96d55fe75aabfb4cf2b7944 16242 karabo-bridge_0.6.2.orig.tar.gz
 e6162fb66c0d4d9bba4ed92a51cf1293bd86f0d7 2512 
karabo-bridge_0.6.2-1.debian.tar.xz
 4e097b488a093810fcf6563d7f62e3f807bb069c 7901 
karabo-bridge_0.6.2-1_amd64.buildinfo
Checksums-Sha256:
 984801e72f5873731cddbbb60b13fa807d2f3d5eaa750286db49ad040a3a31b6 2155 
karabo-bridge_0.6.2-1.dsc
 

Bug#1023621: azure-cli - incomplete dependences: ModuleNotFoundError

[Luca Boccassi]

Control: tags -1 -moreinfo
Control: reassign -1 python3-azure
Control: close -1 20221101+git-1

On Tue, 08 Nov 2022 11:36:56 + Luca Boccassi 
wrote:
> Control: tags -1 moreinfo
> 
> On Mon, 07 Nov 2022 19:36:40 +0100 Bastian Blank 
> wrote:
> > Package: azure-cli
> > Version: 2.42.0-1
> > Severity: serious
> > 
> > Simple VM operations, like start, fail with ModuleNotFoundError. 
So
> some
> > dependencies are incorrect.
> 
> Did you have the new python3-azure that just migrated to testing? If
> not, can you try again and let me know if it helps?

Cannot reproduce this anymore with the new python3-azure, so closing.

-- 
Kind regards,
Luca Boccassi


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

Processed: Re: azure-cli - incomplete dependences: ModuleNotFoundError

[Debian Bug Tracking System]

Processing control commands:

> tags -1 -moreinfo
Bug #1023621 [azure-cli] azure-cli - incomplete dependences: ModuleNotFoundError
Removed tag(s) moreinfo.
> reassign -1 python3-azure
Bug #1023621 [azure-cli] azure-cli - incomplete dependences: ModuleNotFoundError
Bug reassigned from package 'azure-cli' to 'python3-azure'.
No longer marked as found in versions azure-cli/2.42.0-1.
Ignoring request to alter fixed versions of bug #1023621 to the same values 
previously set
> close -1 20221101+git-1
Bug #1023621 [python3-azure] azure-cli - incomplete dependences: 
ModuleNotFoundError
Marked as fixed in versions python-azure/20221101+git-1.
Bug #1023621 [python3-azure] azure-cli - incomplete dependences: 
ModuleNotFoundError
Marked Bug as done

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

Processed: bug 1023576 is forwarded to https://github.com/rakudo/rakudo/issues/5099

[Debian Bug Tracking System]

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

> forwarded 1023576 https://github.com/rakudo/rakudo/issues/5099
Bug #1023576 [raku-json-class] raku-json-class: trying to overwrite 
'/usr/lib/perl6/vendor/precomp/B956FE95EA2D10BBA53021A509C172354487B37C/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC',
 which is also in package raku-json-marshal 0.0.24-1
Set Bug forwarded-to-address to 'https://github.com/rakudo/rakudo/issues/5099'.
> thanks
Stopping processing here.

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

Bug#1023422: FTBFS: test failure

[gregor herrmann]

On Thu, 03 Nov 2022 20:39:02 +0100, gregor herrmann wrote:

> As also seen on ci.debian.net, minilla recently started to fail its
> test suite, which also makes it FTBFS:

> Test Summary Report
> ---
> t/filegatherer.t   (Wstat: 65280 (exited 255) Tests: 
> 2 Failed: 1)
>   Failed test:  2
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> t/filegatherer/submodules-recursive.t  (Wstat: 65280 (exited 255) Tests: 
> 2 Failed: 1)
>   Failed test:  2
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> t/project/in_submodule.t   (Wstat: 65280 (exited 255) Tests: 
> 1 Failed: 1)
>   Failed test:  1
>   Non-zero exit status: 255
>   Parse errors: No plan found in TAP output
> 
> 
> This may or may not be related to recent changes in git:
> 
> git (1:2.38.1-1) unstable; urgency=medium
> 
>   * new upstream release (closes: #1022046; see RelNotes/2.38.0.txt,
> RelNotes/2.38.1.txt).
> * Addresses the security issue CVE-2022-39253: cloning an
>   attacker-controlled local repository could store arbitrary files
>   in the ".git" directory of the destination repository.
> 
>   Thanks to Cory Snider of Mirantis for reporting this
>   vulnerability and Taylor Blau for the mitigation.
> 
> * Addresses CVE-2022-39260: a long command string passed to a `git
>   shell` configured to support custom commands could overflow and
>   run arbitrary code.
> 
>   Thanks to Kevin Backhouse of GitHub for reporting this
>   vulnerability and Kevin Backhouse, Jeff King, and Taylor Blau
>   for mitigating it.

Preliminary patch at
https://salsa.debian.org/perl-team/modules/packages/minilla/-/blob/master/debian/patches/git-2.38.1.patch
(inspired by https://github.com/book/Git-Repository/pull/22 and
https://vielmetti.typepad.com/logbook/2022/10/git-security-fixes-lead-to-fatal-transport-file-not-allowed-error-in-ci-systems-cve-2022-39253.html
), feedback welcome.

Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   


signature.asc
Description: Digital Signature

Bug#1023520: sumo: FTBFS (setuptools missing --install-layout=deb)

[Sebastiaan Couwenberg]

Control: tags -1 patch

On 11/5/22 21:04, Bas Couwenberg wrote:

python3-setuptools no longer defaults to --install-layout=deb, sumo will need a 
patch to add this to the generated setup.py.


The attached patch resolves this issue.

Kind Regards,

Bas

--
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1
diff -Nru sumo-1.12.0+dfsg1/debian/changelog sumo-1.12.0+dfsg1/debian/changelog
--- sumo-1.12.0+dfsg1/debian/changelog  2022-02-11 22:11:11.0 +
+++ sumo-1.12.0+dfsg1/debian/changelog  2022-11-11 13:28:30.0 +
@@ -1,3 +1,11 @@
+sumo (1.12.0+dfsg1-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Add patch to fix installation with setuptools 65.3.0.
+(closes: #1023520)
+
+ -- Bas Couwenberg   Fri, 11 Nov 2022 13:28:30 +
+
 sumo (1.12.0+dfsg1-1) unstable; urgency=medium
 
   * [e174ad9] Fix typo
diff -Nru sumo-1.12.0+dfsg1/debian/patches/series 
sumo-1.12.0+dfsg1/debian/patches/series
--- sumo-1.12.0+dfsg1/debian/patches/series 2022-02-11 22:11:11.0 
+
+++ sumo-1.12.0+dfsg1/debian/patches/series 2022-11-11 13:27:39.0 
+
@@ -1,3 +1,4 @@
 50_python2-rm.patch
 60_fix_tests.patch
 10_fix_python2.patch
+setuptools.patch
diff -Nru sumo-1.12.0+dfsg1/debian/patches/setuptools.patch 
sumo-1.12.0+dfsg1/debian/patches/setuptools.patch
--- sumo-1.12.0+dfsg1/debian/patches/setuptools.patch   1970-01-01 
00:00:00.0 +
+++ sumo-1.12.0+dfsg1/debian/patches/setuptools.patch   2022-11-11 
13:27:39.0 +
@@ -0,0 +1,47 @@
+Description: Fix installation with setuptools 65.3.0.
+Author: Bas Couwenberg 
+Bug-Debian: https://bugs.debian.org/1023520
+Forwarded: not-needed
+
+Index: sumo-1.12.0+dfsg1/src/libsumo/CMakeLists.txt
+===
+--- sumo-1.12.0+dfsg1.orig/src/libsumo/CMakeLists.txt
 sumo-1.12.0+dfsg1/src/libsumo/CMakeLists.txt
+@@ -187,7 +187,7 @@ if(SWIG_FOUND)
+ endif()
+ if (NOT ${SETUPTOOLS_MISSING})
+ install(
+-CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-libsumo.py clean --all install 
--root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} --optimize=1)"
++CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-libsumo.py clean --all install 
--install-layout=deb --root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} 
--optimize=1)"
+ COMPONENT pylibsumo)
+ endif()
+ else()
+Index: sumo-1.12.0+dfsg1/src/libtraci/CMakeLists.txt
+===
+--- sumo-1.12.0+dfsg1.orig/src/libtraci/CMakeLists.txt
 sumo-1.12.0+dfsg1/src/libtraci/CMakeLists.txt
+@@ -159,7 +159,7 @@ if(SWIG_FOUND)
+ endif()
+ if (NOT ${SETUPTOOLS_MISSING})
+ install(
+-CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-libtraci.py clean --all install 
--root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} --optimize=1)"
++CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-libtraci.py clean --all install 
--install-layout=deb --root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} 
--optimize=1)"
+ COMPONENT pylibtraci)
+ endif()
+ else()
+Index: sumo-1.12.0+dfsg1/CMakeLists.txt
+===
+--- sumo-1.12.0+dfsg1.orig/CMakeLists.txt
 sumo-1.12.0+dfsg1/CMakeLists.txt
+@@ -456,9 +456,9 @@ endif ()
+ install(EXPORT SUMOConfig DESTINATION ${DATA_PATH}cmake NAMESPACE SUMO::)
+ 
+ if (NOT ${SETUPTOOLS_MISSING})
+-install(CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-sumolib.py clean --all install 
--root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} --optimize=1)"
++install(CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-sumolib.py clean --all install 
--install-layout=deb --root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} 
--optimize=1)"
+ COMPONENT pysumolib)
+-install(CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-traci.py clean --all install 
--root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} --optimize=1)"
++install(CODE "execute_process(COMMAND ${PYTHON_EXECUTABLE} 
${CMAKE_SOURCE_DIR}/tools/build/setup-traci.py clean --all install 
--install-layout=deb --root=\$ENV{DESTDIR}/ --prefix=${CMAKE_INSTALL_PREFIX} 
--optimize=1)"
+ COMPONENT pytraci)
+ endif ()
+ 

Processed: Re: sumo: FTBFS (setuptools missing --install-layout=deb)

[Debian Bug Tracking System]

Processing control commands:

> tags -1 patch
Bug #1023520 [src:sumo] sumo: FTBFS (setuptools missing --install-layout=deb)
Added tag(s) patch.

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

Bug#1020747: Fwd: Python 3.11 is now a supported release in unstable

[Jerome BENOIT]

Thanks for the reply.

On 11/11/2022 13:49, stefa...@debian.org wrote:

Hi Jerome (2022.11.11_12:23:42_+)

Fixing the #1020747 may avoid FTBFS for some packages.
I proposed a solution to fix it, however I cannot say if it optimal.


That patch looks reasonable to me. I'd have done the [:3] inside the
tuple(), but that's not exactly a problem.


I will try to step forward by the end of the week-end if no one else
do it before.

Cheers,
Jerome



SR



--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D 87E5  A762 3F92 19A6 7F36 C68B


OpenPGP_signature
Description: OpenPGP digital signature

Bug#1023835: wolfssl: FTBFS because of amd64-only symbols in symbols file

[Bastian Germann]

On Thu, 10 Nov 2022 16:12:26 -0800 Felix Lechner  
wrote:

Hi,

On Thu, Nov 10, 2022 at 4:06 PM Bastian Germann  wrote:
>
> Please keep the three symbols out of the symbols file or make them optional.

Thanks. We are aware of the issue.

Unfortunately, your suggestion will likely cause a build failure on
amd64. How do you make the symbols "optional" please? Thanks!


Removing the symbols will result in a dpkg-gensymbols warning but will let the 
build pass.
Prepending with (optional) will make a symbol optional.

Bug#1023597: marked as done (FTBFS: t/21-submodule.t: fatal: transport 'file' not allowed)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 13:35:40 +
with message-id 
and subject line Bug#1023597: fixed in libgit-repository-perl 1.325-2
has caused the Debian Bug report #1023597,
regarding FTBFS: t/21-submodule.t: fatal: transport 'file' not allowed
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.)


-- 
1023597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023597
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgit-repository-perl
Version: 1.325-1
Severity: serious
Tags: ftbfs 
Justification: fails to build from source

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

libgit-repository-perl's test suite started to fail recently:

Cloning into '/tmp/M19xNBDPV8/sub'...
fatal: transport 'file' not allowed
fatal: clone of '/tmp/tC7mgf7E52' into submodule path '/tmp/M19xNBDPV8/sub' 
failed at t/21-submodule.t line 46.
# Looks like your test exited with 128 before it could output anything.
t/21-submodule.t ...
1..1
Dubious, test returned 128 (wstat 32768, 0x8000)
Failed 1/1 subtests


Propably caused by changes in git:

git (1:2.38.1-1) unstable; urgency=medium

  * new upstream release (closes: #1022046; see RelNotes/2.38.0.txt,
RelNotes/2.38.1.txt).
* Addresses the security issue CVE-2022-39253: cloning an
  attacker-controlled local repository could store arbitrary files
  in the ".git" directory of the destination repository.



Cheers,
gregor

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNo7HVfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx
RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ
qgaWbA//Zodx1kLFKEaU9L8rgk545iISZXU8BBU/vdLp7VROP9CvkA2mqa4m9MtU
VwMZuQ0HMbxocdjXIi6HZnyAGgh7goaolQV8qDPpLAp33WHZsuVLDQWC+NGMi87E
8imtl3TbKAlSMxXUvIj0gEAHQ650dchjtLKYeNvP0xMgpKviG1Rzf+Nl/3mcfIYX
zP7avstGrnfGrLEz6CgCdzAoeOI1Fs0B5uase5kuBNv3irj9V2Rvl1LDOiTB4JFB
eSBADjAe5rtiTdRhE7z4IvfOIjLHSTHf3w8LcIfPdhQtUWQBb2jkos1PpOfdN1W8
XeLl8SARf2vNRsCqv4GQuBPGhc8xTbSyMPWf8gZADoQcV6rMkTy//ejUdESPXfE4
JdCQazfPONbq213SWF46pduk7N/heZjWdYDf4geVe0kq4nOSPlkst2S/nakMXV5e
uB+eTb/IwTZ1uc6m+MLwUB8D0jinzgnL3eRoGYCokSNJ55kid3UWJbW9eKGQ69/J
6WbaRjCKbmJAL23djEw65Sj8SbpE2jJyaGQFPbU5Wxl25ukCN0/yoMGp6QOs9l/r
bP64+2iYXJeqrXE06QhFO7iRtv+sPa9Sh/Etc9txtJbutbhMf6ig/DcjBzWYL0xP
LXRG5aYSE94B6bKXnA0NFdtCGB04SuT6AsFLd5VkSb5oNUXIFxU=
=qypE
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libgit-repository-perl
Source-Version: 1.325-2
Done: gregor herrmann 

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

Debian distribution maintenance software
pp.
gregor herrmann  (supplier of updated libgit-repository-perl 
package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 11 Nov 2022 14:18:15 +0100
Source: libgit-repository-perl
Architecture: source
Version: 1.325-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Perl Group 
Changed-By: gregor herrmann 
Closes: 1023597
Changes:
 libgit-repository-perl (1.325-2) unstable; urgency=medium
 .
   * Team upload.
   * Add patch from GitHub pull request to fix test suite with
 Git ≥ 2.38.1. (Closes: #1023597)
   * Declare compliance with Debian Policy 4.6.1.
Checksums-Sha1:
 ac46939fb106dbe5e1479672725f32805afefb7a 2597 
libgit-repository-perl_1.325-2.dsc
 0ca7cf4e0165630e6231bb1309ef43185d51af12 4784 
libgit-repository-perl_1.325-2.debian.tar.xz
Checksums-Sha256:
 f997173484478f297a59d244dcd3405501243168cdae6a704515b6ea4fcdfd51 2597 
libgit-repository-perl_1.325-2.dsc
 b94153090de4894b953a7f46645e6455d78ca3b994ccc79a22fa80420b8bcf86 4784 
libgit-repository-perl_1.325-2.debian.tar.xz
Files:
 2de35eaa0d6e90a19998cd9ee01073da 2597 perl optional 
libgit-repository-perl_1.325-2.dsc
 6c8e2f98d3309bff83ca178ab957f325 4784 perl optional 
libgit-repository-perl_1.325-2.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmNuTGdfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx

Bug#1022418: marked as done (python-whisper: FTBFS: make: *** [debian/rules:5: clean] Error 1)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 13:35:55 +
with message-id 
and subject line Bug#1022418: fixed in python-whisper 1.1.4-2.2
has caused the Debian Bug report #1022418,
regarding python-whisper: FTBFS: make: *** [debian/rules:5: clean] 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.)


-- 
1022418: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022418
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-whisper
Version: 1.1.4-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20221023 ftbfs-bookworm

Hi,

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


Relevant part (hopefully):
>  fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>dh_auto_clean -O--buildsystem=pybuild
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level 
> 9 in use)
> py3versions: No supported python3 versions in version string
> E: py3versions failed at 
> /usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm line 53.
> make: *** [debian/rules:5: clean] Error 1


The full build log is available from:
http://qa-logs.debian.net/2022/10/23/python-whisper_1.1.4-2.1_unstable.log

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

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

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

If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-whisper
Source-Version: 1.1.4-2.2
Done: Stefano Rivera 

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

Debian distribution maintenance software
pp.
Stefano Rivera  (supplier of updated python-whisper 
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, 09 Nov 2022 14:57:05 +0200
Source: python-whisper
Architecture: source
Version: 1.1.4-2.2
Distribution: unstable
Urgency: medium
Maintainer: Debian Graphite Group 
Changed-By: Stefano Rivera 
Closes: 1003823 1022418
Changes:
 python-whisper (1.1.4-2.2) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * Remove X-Python-3-Version: all, no longer supported.
 (Closes: #1003823, #1022418)
Checksums-Sha1:
 4e27a573d6b99bdacdc02758a7abc0b690c76059 1549 python-whisper_1.1.4-2.2.dsc
 bd45a7cd6c8116e56148a0ccede3e53dffc16307 4188 
python-whisper_1.1.4-2.2.debian.tar.xz
 3df4fee385269f3dd7755caaa7a3bd129e7744fd 6055 
python-whisper_1.1.4-2.2_source.buildinfo
Checksums-Sha256:
 d0602da86b3265e8148009683219933a183ca800ceb85dc6ddbbfe55f4e7148b 1549 
python-whisper_1.1.4-2.2.dsc
 583ada3f55bfec0cc89ee39ef0d6f9ca8e8ffbff7448654d0255374a15428725 4188 
python-whisper_1.1.4-2.2.debian.tar.xz
 efcddaf36b3845176109e1b4f953074783fbed588bfbf23f8c4e2eacbed10b76 6055 
python-whisper_1.1.4-2.2_source.buildinfo
Files:
 316e43f0041e1714f3c71e8f4f8ac4f2 1549 python optional 
python-whisper_1.1.4-2.2.dsc
 7a713e4c567097e9f14c83d8df344e64 4188 python optional 
python-whisper_1.1.4-2.2.debian.tar.xz
 332fd1f60eb4bb9df1e478fed345b922 6055 python optional 
python-whisper_1.1.4-2.2_source.buildinfo

-BEGIN PGP SIGNATURE-

iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCY2unIhQcc3RlZmFub3JA
ZGViaWFuLm9yZwAKCRBHew2wJjpU2AJaAQDoObtge+nCGTnTHLyR3wBGFj5Ksid/
xjvIImlGwuva3AD/V5oDFx2XiPIXp98QdykP21Vle+yj2b49AwTIRfUiYgM=
=AeBp
-END PGP SIGNATURE End Message ---

Processed: bug 1023422 is forwarded to https://github.com/tokuhirom/Minilla/issues/322, tagging 1023422

[Debian Bug Tracking System]

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

> forwarded 1023422 https://github.com/tokuhirom/Minilla/issues/322
Bug #1023422 [src:minilla] minilla: FTBFS: test failures with git 1:2.38.1-1 : 
transport 'file' not allowed
Bug #1023689 [src:minilla] minilla: FTBFS: test failures with git 1:2.38.1-1 : 
transport 'file' not allowed
Set Bug forwarded-to-address to 
'https://github.com/tokuhirom/Minilla/issues/322'.
Set Bug forwarded-to-address to 
'https://github.com/tokuhirom/Minilla/issues/322'.
> tags 1023422 + upstream
Bug #1023422 [src:minilla] minilla: FTBFS: test failures with git 1:2.38.1-1 : 
transport 'file' not allowed
Bug #1023689 [src:minilla] minilla: FTBFS: test failures with git 1:2.38.1-1 : 
transport 'file' not allowed
Added tag(s) upstream.
Added tag(s) upstream.
> thanks
Stopping processing here.

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

Processed: bug 1023685 is forwarded to https://github.com/PerlDancer/Dancer/issues/1237

[Debian Bug Tracking System]

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

> forwarded 1023685 https://github.com/PerlDancer/Dancer/issues/1237
Bug #1023685 [src:libdancer-perl] libdancer-perl: FTBFS: 
10_error_dumper_without_clone.t failure
Bug #1023421 [src:libdancer-perl] libdancer-perl: FTBFS: 
t/12_response/10_error_dumper_without_clone.t failure
Set Bug forwarded-to-address to 
'https://github.com/PerlDancer/Dancer/issues/1237'.
Set Bug forwarded-to-address to 
'https://github.com/PerlDancer/Dancer/issues/1237'.
> thanks
Stopping processing here.

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

Processed: bug 1023597 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=144889, tagging 1023597

[Debian Bug Tracking System]

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

> forwarded 1023597 https://rt.cpan.org/Public/Bug/Display.html?id=144889
Bug #1023597 [src:libgit-repository-perl] FTBFS: t/21-submodule.t: fatal: 
transport 'file' not allowed
Set Bug forwarded-to-address to 
'https://rt.cpan.org/Public/Bug/Display.html?id=144889'.
> tags 1023597 + patch
Bug #1023597 [src:libgit-repository-perl] FTBFS: t/21-submodule.t: fatal: 
transport 'file' not allowed
Added tag(s) patch.
> thanks
Stopping processing here.

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

Processed: closing 1011706

[Debian Bug Tracking System]

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

> close 1011706 3.5.3-1
Bug #1011706 [src:veusz] veusz: FTBFS: ImportError: cannot import name 'parse' 
from 'sipbuild.code_generator' 
(/usr/lib/python3/dist-packages/sipbuild/code_generator.abi3.so)
Marked as fixed in versions veusz/3.5.3-1.
Bug #1011706 [src:veusz] veusz: FTBFS: ImportError: cannot import name 'parse' 
from 'sipbuild.code_generator' 
(/usr/lib/python3/dist-packages/sipbuild/code_generator.abi3.so)
Marked Bug as done
> thanks
Stopping processing here.

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

Bug#978287: py-lz4framed: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2

[Adrian Bunk]

On Sat, Dec 26, 2020 at 10:50:26PM +0100, Lucas Nussbaum wrote:
>...
> > running clean
> > removing '/<>/.pybuild/cpython3_3.9_py-lz4framed/build' (and 
> > everything under it)
> > 'build/bdist.linux-x86_64' does not exist -- can't clean it
> > 'build/scripts-3.9' does not exist -- can't clean it
> > rm -rf .pybuild/
> > find . -name \*.pyc -exec rm {} \;
> > rm -rf py_lz4framed.egg-info/
> > rm -f lz4/lz4frame.h
> > cp /usr/include/lz4frame.h lz4/lz4frame.h
>...

override_dh_auto_clean is not the correct place for copying lz4frame.h,
this should be done before configuring.

cu
Adrian

Bug#1023848: kodi-pvr-hts: Packet requires kodi-api-pvr but is not available in sid

[Leela]

Package: kodi-pvr-hts
Version: 20.3.0+ds1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: pleasespamtothis...@gmx.de

Dear Maintainer,


   * What led up to the situation?
-Dist-upgrade to sid
   * What exactly did you do (or not do) that was effective (or
 ineffective)? 
-Dist-Upgrade to sid
   * What was the outcome of this action?
-pvr-hts plugin was no longer installed. Trying to install it required 
kodi-api-pvr but is not available in sid
   * What outcome did you expect instead?
kodi-pvr-hts should still work after upgrading to sid   

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

Kernel: Linux 6.0.0-3-amd64 (SMP w/2 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 kodi-pvr-hts depends on:
ii  kodi [kodi-api-pvr]  2:20.0~beta1+dfsg1-1
ii  libc62.36-4
ii  libgcc-s112.2.0-9
ii  libstdc++6   12.2.0-9

kodi-pvr-hts recommends no packages.

kodi-pvr-hts suggests no packages.

Bug#1016711: marked as done (libthrust: flaky autopkgtest)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 11:49:14 +
with message-id 
and subject line Bug#1016711: fixed in libthrust 1.16.0-2
has caused the Debian Bug report #1016711,
regarding libthrust: flaky autopkgtest
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.)


-- 
1016711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libthrust
Version: 1.16.0-1
Severity: normal

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Dear maintainer,

the autopkgtest suite on amd64 has spurious timeouts:
https://ci.debian.net/data/autopkgtest/testing/amd64/libt/libthrust/24362266/log.gz

> autopkgtest [12:57:19]:  summary
> cmake_find_package_Thrust PASS (superficial)
> run_testsuite_CPP_C++17_g++-12 PASS (superficial)
> run_testsuite_CPP_C++17_g++-11 FLAKY non-zero exit status 8
> run_testsuite_CPP_C++17_g++-10 PASS (superficial)
> run_testsuite_CPP_C++14 FLAKY non-zero exit status 8
> run_testsuite_TBB_C++17 PASS (superficial)
> compile_testsuite_CPP_CUDA_C++17_cuda-g++ FAIL timed out
> compile_testsuite_TBB_CUDA_C++17_cuda-g++ FAIL timed out
> compile_testsuite_CPP_CUDA_C++17_g++-11 FLAKY non-zero exit status 2
> compile_testsuite_TBB_CUDA_C++17_g++-11 FLAKY non-zero exit status 2
> compile_testsuite_CPP_CUDA_C++17_g++-10 SKIP exit status 77 and marked as 
> skippable
> compile_testsuite_TBB_CUDA_C++17_g++-10 SKIP exit status 77 and marked as 
> skippable


Cheers
Timo


-BEGIN PGP SIGNATURE-

iQGzBAEBCgAdFiEEJvtDgpxjkjCIVtam+C8H+466LVkFAmLtbxEACgkQ+C8H+466
LVmrxQv+Ieyzf5slRYzevaK/pzwGhZG7OnXktlG5b97bmjS0Pf1TKr8GTvmpGHYd
7WSM2i8F1BGvhy2aV+IITuCIFow6tn8OXjl/F/xA/Njv9oHyqDJ8bHmCrC4xqdiU
WUyphRLD0BacA1174Dqhj4pt7zJDM/n6RAtWw/ePiIXbU3PGcdjtu9sUMJ3U6501
lv+GbOd1ul4XBF+BXHDRPNP5SgPgLCgr+La7QNDNleroTxsXT/lVlHgWP0jlrDhk
hlHTPw/v84RkmYNVQt439PirhqTQKmhve3ZqtaSw76GwmusJWb3uDpG/7mYxauzK
QXMFR9C6zc2BXbO8Q7Q0fEoNauB4annA23+V7xWsDBQAiYg92kKUgeMwRCKx62XN
lAfGHt/EaSSaHS0tdBe1crEqOo75EFmXZoFw1w4NJ6c/00jYJD2VVeLeOCojOGrR
egVnpT34W1Grn2w4XnQ+wN+faqYbChOJFJ3+bESft4/u5JGUZ7ygOP267q/Rm+JY
frYI6WPo
=tUvq
-END PGP SIGNATURE-
--- End Message ---
--- Begin Message ---
Source: libthrust
Source-Version: 1.16.0-2
Done: Andreas Beckmann 

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

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

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

Debian distribution maintenance software
pp.
Andreas Beckmann  (supplier of updated libthrust package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 11 Nov 2022 12:11:17 +0100
Source: libthrust
Architecture: source
Version: 1.16.0-2
Distribution: unstable
Urgency: medium
Maintainer: Debian NVIDIA Maintainers 
Changed-By: Andreas Beckmann 
Closes: 1016711
Changes:
 libthrust (1.16.0-2) unstable; urgency=medium
 .
   * Mark TBB/CUDA test as flaky.  (Closes: #1016711)
   * Update watch file.
Checksums-Sha1:
 a86446a40cf54dd6b98271ec1cbfb2ddd8042e23 2095 libthrust_1.16.0-2.dsc
 2c2fac6a4cef19f037ab536f385498fe07205405 8028 libthrust_1.16.0-2.debian.tar.xz
 87b653ec234722436845d872834153c1620e5265 6367 
libthrust_1.16.0-2_source.buildinfo
Checksums-Sha256:
 f78e567dc9310995682b83cf4ed96eb4ab1c18a6bdcdb240ba99e536c61ce30a 2095 
libthrust_1.16.0-2.dsc
 6f4500cab7defb5ffddda0e0b552f3b96dac0217d0c912f677b1d3bb2f2fa4ea 8028 
libthrust_1.16.0-2.debian.tar.xz
 27ab3ad4eb476226721e69c3cbc7ab083c34023288d1d65167147a62600526c9 6367 
libthrust_1.16.0-2_source.buildinfo
Files:
 6d4b80c0a9f669329af198d3d1cbf87f 2095 libdevel optional libthrust_1.16.0-2.dsc
 b0133728484a7f5aed86f9ed521672fb 8028 libdevel optional 
libthrust_1.16.0-2.debian.tar.xz
 994396139aa7bf687ac38ab8ed7063ae 6367 libdevel optional 
libthrust_1.16.0-2_source.buildinfo

-BEGIN PGP SIGNATURE-

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAmNuMMQQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCF7DD/9lnPrAxI7kQrzvzgD0kZevsR8KzH0cR0Mn
zlJxEuAlO56KrCZCcbxKYrDgU1TTWdMUQsCqe3TWfJY7X8yoBhm/8OIcKzdIMGSI
gNXaYiCfsOx94Um6DalIHL8NAl4INyvWav/7E/1hXLRAzQAgalmqwUDFCWd508cp
thDTJkRAq2jdFZCv//tLYdPqU7wrFvDPegUoQcaZU6idvhtAuJSyx8O/SCiU6s5F

Processed: transition: gdal

[Debian Bug Tracking System]

Processing control commands:

> forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html
Bug #1023846 [release.debian.org] transition: gdal
Set Bug forwarded-to-address to 
'https://release.debian.org/transitions/html/auto-gdal.html'.
> block -1 by 1023480 1023506 1004795 998833 984398 1023520 1012950
Bug #1023846 [release.debian.org] transition: gdal
1023846 was not blocked by any bugs.
1023846 was not blocking any bugs.
Added blocking bug(s) of 1023846: 1023520, 1023480, 984398, 1023506, 1012950, 
998833, and 1004795

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

Bug#1021704: marked as done (amanda: build dependency missing in testing xfsdump)

[Debian Bug Tracking System]

Your message dated Fri, 11 Nov 2022 12:44:22 +0200
with message-id 
and subject line Re: Bug#1021704: amanda: build dependency missing in testing 
xfsdump
has caused the Debian Bug report #1021704,
regarding amanda: build dependency missing in testing xfsdump
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.)


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

Source: amanda
Version: 1:3.5.1-9
Severity: serious
User: debian...@lists.debian.org
Usertag: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting issues with your packages. Normally your build 
dependencies shouldn't be removed from testing without removal all 
reverse build dependencies too, nor should a package be allowed to 
migrate unless all build dependencies are candidate for migration too. 
However, somehow we ended up in the current state and your source 
package is missing some Build-Depends for some while now. Not being able 
to build from source in a suite is an RC bug in that suite.


Can you please solve the situation by either helping the maintainer of 
your Build-Depends to enable migration to testing, or by working around 
the lack of this build dependency?


Paul

[1] https://qa.debian.org/dose/debcheck/src_testing_main/index.html


OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
On Thu, Oct 13, 2022 at 12:21:24PM +0200, Paul Gevers wrote:
> Source: amanda
> Version: 1:3.5.1-9
> Severity: serious
> User: debian...@lists.debian.org
> Usertag: edos-uninstallable
> 
> Dear maintainer(s),
> 
> Dose [1] is reporting issues with your packages. Normally your build
> dependencies shouldn't be removed from testing without removal all reverse
> build dependencies too, nor should a package be allowed to migrate unless
> all build dependencies are candidate for migration too. However, somehow we
> ended up in the current state and your source package is missing some
> Build-Depends for some while now. Not being able to build from source in a
> suite is an RC bug in that suite.
> 
> Can you please solve the situation by either helping the maintainer of your
> Build-Depends to enable migration to testing, or by working around the lack
> of this build dependency?

In the meantime xfsdump migrated back to testing.

> Paul
>...

cu
Adrian--- End Message ---

Processed: Bug#1020135 marked as pending in numpy

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #1020135 [src:numpy] numpy: FTBFS: AttributeError: 'UnixCCompiler' object 
has no attribute 'cxx_compiler'
Added tag(s) pending.

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

Bug#1020135: marked as pending in numpy

[Stefano Rivera]

Control: tag -1 pending

Hello,

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

https://salsa.debian.org/python-team/packages/numpy/-/commit/ff0524bcc8e264c1e6618e42f11d4a1b608316ef


set SETUPTOOLS_USE_DISTUTILS=stdlib to ensure compatibility with setuptools >= 
60.0.0; Thanks to Jochen Sprickerhof; Closes: #1020135


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1020135

Bug#1023839: ardour: Ardour won't start

[Gianfranco Costamagna]

control: severity -1 normal

Hello, works for me in a sid up-to-date environment

ii  ardour 1:7.0.0+ds0-3 amd64
the digital audio workstation
ii  ardour-data1:7.0.0+ds0-3 all  
digital audio workstation (data)
ii  ardour-lv2-plugins 1:7.0.0+ds0-3 amd64
digital audio workstation - lv2 plugins set
ii  librubberband2:amd64   3.1.0+dfsg0-1 amd64
audio time-stretching and pitch-shifting library


Please double check your librubberband2 library version, the symbol looks an RC 
bug on that package
(a missing soname bump?)

G.

On Fri, 11 Nov 2022 08:31:39 +0100 raffaele morelli 
 wrote:

Package: ardour
Version: 1:7.0.0+ds0-3
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: raffaele.more...@gmail.com

Ardour doesn't start

/usr/lib/ardour7/ardour-7.0.0~ds0: symbol lookup error: 
/usr/lib/ardour7/libardour.so.3: undefined symbol: 
_ZNK10RubberBand19RubberBandStretcher20getPreferredStartPadEv




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

Kernel: Linux 6.0.0-2-rt-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 ardour depends on:
ii  ardour-data  1:7.0.0+ds0-3
ii  ardour-lv2-plugins   1:7.0.0+ds0-3
ii  libarchive13 3.6.0-1
ii  libasound2   1.2.7.2-1
ii  libatkmm-1.6-1v5 2.28.3-1
ii  libaubio50.4.9-4.2+b1
ii  libc62.36-4
ii  libcairo21.16.0-6
ii  libcairomm-1.0-1v5   1.14.4-1
ii  libcurl3-gnutls  7.86.0-1
ii  libcwiid10.6.91-4
ii  libdbus-1-3  1.14.4-1
ii  libfftw3-single3 3.3.8-2
ii  libfluidsynth3   2.3.0-1+b1
ii  libfontconfig1   2.13.1-4.5
ii  libgcc-s112.2.0-9
ii  libgdk-pixbuf-2.0-0  2.42.9+dfsg-1
ii  libglib2.0-0 2.74.1-1
ii  libglibmm-2.4-1v52.66.5-1
ii  libgtk2.0-0  2.24.33-2
ii  libgtkmm-2.4-1v5 1:2.24.5-4+b1
ii  liblilv-0-0  0.24.14-1
ii  liblo7   0.31-1
ii  liblrdf0 0.6.1-3
ii  libltc11 1.3.2-1
ii  libpango-1.0-0   1.50.10+ds-1
ii  libpangocairo-1.0-0  1.50.10+ds-1
ii  libpangoft2-1.0-01.50.10+ds-1
ii  libpangomm-1.4-1v5   2.46.3-1
ii  libpulse016.1+dfsg1-2+b1
ii  libqm-dsp0   1.7.1-5
ii  libreadline8 8.2-1.1
ii  librubberband2   1:2.0.2-dmo1
ii  libsamplerate0   0.2.2-2


OpenPGP_signature
Description: OpenPGP digital signature

Processed: Re: ardour: Ardour won't start

[Debian Bug Tracking System]

Processing control commands:

> severity -1 normal
Bug #1023839 [ardour] ardour: Ardour won't start
Severity set to 'normal' from 'grave'

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

Bug#1023842: rust-criterion - inconsistent dependencies on cast.

[Peter Green]

Package: rust-criterion
Version: 0.3.6-1
Severity: serious
Tags: patch

The rust-criterion package has inconsistent dependencies on the cast crate, the
dependency in the main Cargo.toml is on version 0.3, but the dependencies in the
debian packaging and in the embedded copy of the criterion-plot crate are at 0.2

I have updated the cast crate in Debian to 0.3, and prepared an update for the
rust-criterion package to use 0.3 consistently. I tested that the package built
succesfully and the autopkgtests passed with these changes.

While working on the fix, I discovered the clean target wasn't cleaning up
properly, so I fixed it to do so.

Debdiff attatched, If I get no response I will probablly NMU this in a week or
so.
diff -Nru rust-criterion-0.3.6/debian/changelog 
rust-criterion-0.3.6/debian/changelog
--- rust-criterion-0.3.6/debian/changelog   2022-11-07 07:51:45.0 
+
+++ rust-criterion-0.3.6/debian/changelog   2022-11-10 20:23:39.0 
+
@@ -1,3 +1,13 @@
+rust-criterion (0.3.6-1.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Update inconsistent cast dependencies to a consistent 0.3
++ The cast dependency in the main Cargo.toml was at 0.3 while the Debian
+  Dependency and the cast dependency in the plot subcrate were at 0.2.
+  * Fix clean target.
+
+ -- Peter Michael Green   Thu, 10 Nov 2022 20:23:39 +
+
 rust-criterion (0.3.6-1) unstable; urgency=medium
 
   [ upstream ]
diff -Nru rust-criterion-0.3.6/debian/control 
rust-criterion-0.3.6/debian/control
--- rust-criterion-0.3.6/debian/control 2022-11-07 07:50:12.0 +
+++ rust-criterion-0.3.6/debian/control 2022-11-10 20:23:39.0 +
@@ -7,7 +7,7 @@
  gnuplot-nox ,
  librust-approx-0.5+default-dev ,
  librust-atty-0.2+default-dev ,
- librust-cast-0.2+default-dev ,
+ librust-cast-0.3+default-dev ,
  librust-clap-2-dev (>= 2.33) ,
  librust-criterion-plot-0.4+default-dev (>= 0.4.4) ,
  librust-csv-1+default-dev (>= 1.1) ,
@@ -40,7 +40,7 @@
 Depends:
  gnuplot-nox,
  librust-atty-0.2+default-dev,
- librust-cast-0.2+default-dev,
+ librust-cast-0.3+default-dev,
  librust-clap-2-dev (>= 2.33),
  librust-criterion-plot-0.4+default-dev,
  librust-csv-1+default-dev,
diff -Nru 
rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch 
rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch
--- rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch
1970-01-01 00:00:00.0 +
+++ rust-criterion-0.3.6/debian/patches/-bump-plot-cast-dependency.patch
2022-11-10 20:23:39.0 +
@@ -0,0 +1,28 @@
+Description: Bump cast dependency in plot subcrate.
+ Taken from 
https://github.com/bheisler/criterion.rs/commit/06be43cda0169f5b9c91eb0298545c253ba8830f
+Author: Peter Michael Green 
+
+---
+The information above should follow the Patch Tagging Guidelines, please
+checkout http://dep.debian.net/deps/dep3/ to learn about the format. Here
+are templates for supplementary fields that you might want to add:
+
+Origin: , 
+Bug: 
+Bug-Debian: https://bugs.debian.org/
+Bug-Ubuntu: https://launchpad.net/bugs/
+Forwarded: 
+Reviewed-By: 
+Last-Update: 2022-11-10
+
+--- rust-criterion-0.3.6.orig/plot/Cargo.toml
 rust-criterion-0.3.6/plot/Cargo.toml
+@@ -12,7 +12,7 @@ categories = ["visualization"]
+ license = "MIT/Apache-2.0"
+ 
+ [dependencies]
+-cast = "0.2"
++cast = "0.3"
+ itertools = "0.10"
+ 
+ [dev-dependencies]
diff -Nru rust-criterion-0.3.6/debian/patches/series 
rust-criterion-0.3.6/debian/patches/series
--- rust-criterion-0.3.6/debian/patches/series  2022-11-07 07:45:44.0 
+
+++ rust-criterion-0.3.6/debian/patches/series  2022-11-10 20:23:39.0 
+
@@ -2,3 +2,4 @@
 1002_modernize_macro_syntax.patch
 2001_plotters.patch
 2002_no_unstable_features.patch
+-bump-plot-cast-dependency.patch
diff -Nru rust-criterion-0.3.6/debian/rules rust-criterion-0.3.6/debian/rules
--- rust-criterion-0.3.6/debian/rules   2022-06-22 12:00:18.0 +
+++ rust-criterion-0.3.6/debian/rules   2022-11-10 20:23:39.0 +
@@ -7,3 +7,6 @@
 
 %:
dh $@ --buildsystem cargo
+
+execute_after_dh_auto_clean:
+   rm -rf target